Page 1 of 1
Use of logical names
Posted: Mon Sep 23, 2019 4:17 am
by brianreiter
Hi Folks,
Would it be possible to use logical names to reference source directories etc. rather than relative to the login directory?
Our build environment relies heavily on logical names, especially useful where we have to work on several different versions of an application.
No great worries if it can't be done but it would make it easier to persuade engineers to use the IDE if it could use logical names.
cheers
Brian
Re: Use of logical names
Posted: Tue Sep 24, 2019 7:19 am
by sergey_vorfolomeev
you can use concealed logical names, just start root folder with "/", for example
root: "/MY$DISK/source"
but we have no particular folders for output files, all of them inside the root folder
Re: Use of logical names
Posted: Tue Oct 01, 2019 4:38 am
by brianreiter
I can get logical names to work if they're in the group table but not otherwise. So for example /BUILD_ROOT/SOURCE (i.e. BUILD_ROOT:[SOURCE]) works if BUILD_ROOT is in the group table, but not if its in the process or job table (i.e. setup as part of login.com).
Does the IDE SSH client somehow manage to avoid completing login.com? Things seem to be fine when using SSH via putty, in that the logical name I'd expect to be configured are present.
Re: Use of logical names
Posted: Thu Oct 03, 2019 6:20 am
by brianreiter
OK, not sure if it helps matters much but I was interested in why I got different results between an interactive SSH login and what the IDE is doing. Turning on SSH debug gave a big file but showed the following:
For the IDE login we get:
Code: Select all
debug( 2-OCT-2019 15:37:15.48): Ssh2ChannelSession/SSHCHSESSION.C:2922: session request 'subsystem' received
For an interactive login (via putty) we get:
Code: Select all
debug( 2-OCT-2019 15:34:16.96): Ssh2ChannelSession/SSHCHSESSION.C:2922: session request 'pty-req' received
debug( 2-OCT-2019 15:34:16.97): Ssh2ChannelSession/SSHCHSESSION.C:2922: session request 'shell' received
Which is followed some time later by:
Code: Select all
debug( 2-OCT-2019 15:34:16.97): openvms_emulation_server/OPENVMS_EMULATION_SERVER.C:1542: ovms_start_login entered
debug( 2-OCT-2019 15:34:16.97): wait_for_loginoutexe entered at 2-OCT-2019 15:34:16.97
debug( 2-OCT-2019 15:34:16.97): wait_for_loginoutexe sees child running image
debug( 2-OCT-2019 15:34:17.07): wait_for_loginoutexe sees child running image DEVSYS$DKA0:[SYS0.SYSCOMMON.][SYSEXE]SET.EXE
debug( 2-OCT-2019 15:34:17.07): wait_for_loginoutexe exiting at 2-OCT-2019 15:34:17.07, after 1 waits of 1/10 second
debug( 2-OCT-2019 15:34:17.07): openvms_specific/OPENVMS_SPECIFIC.C:905: add to uai_list: UAI$_LASTLOGIN_I=2-OCT-2019 15:34:17.07
debug( 2-OCT-2019 15:34:17.07): openvms_specific/OPENVMS_SPECIFIC.C:911: add to uai_list: UAI$_LASTLOGIN_N=2-OCT-2019 15:05:21.03
debug( 2-OCT-2019 15:34:17.37): 00000030: 662f 7072 6f63 2073 7973 246c 6f67 696e f/proc sys$login
The IDE variant doesn't show any calls to loginout.exe so presumably skipping anything which would be setup in login.com.
No wiser, but using group wide logical names is the easy workaround for now.
Re: Use of logical names
Posted: Fri Oct 04, 2019 12:45 am
by sergey_vorfolomeev
VMS IDE has two types of SSH connections: SFTP for synchronization and SSH SHELL for building. May be first case doesn't call login...
Re: Use of logical names
Posted: Tue Oct 08, 2019 8:42 am
by brianreiter
OK, so it looks as though this:
https://community.hpe.com/t5/Operating- ... ZyAKVVKios
is still the case.
Does this still occur with the new VSI TCPIP stack?