XBR1YD14@DDATHD21.BITNET (YD14@BR1.THDNET) (02/02/86)
I've got two answers. Thanks. They both suggested to translate SYS$SYSTEM.
But that doesn't fix the problem. I'll get something like
DRA0:[SYS0.SYSEXE]LOGINOUT.EXE
or SYS$SYSDEVICE:[SYS0.SYSEXE]LOGINOUT.EXE
and instead of SYS$SYSTEM someone will redefine DRA0 or SYS$SYSDEVICE in
the job table and he has got me ...
Regards Reinhardinfo-vax@ucbvax.UUCP (02/07/86)
In answer to your SYS$SYSTEM:LOGINOUT.EXE problem, it seems to me that your original V3.x should still work. I know that the underbar still causes logical translation to be supressed, so you should be able to use something like _DRA1:[SYS0.SYSEXE]LOGINOUT.EXE even in version 4.x. You claim that this doesn't work; how does it fail? I have not tried it in a create process system service call, but from most DCL commands, the underbar still works like it used to. If it doesn't work for you, you could try translating SYS$SYSTEM (or DRA1, etc.) to see whether they have the value you expect BEFORE you create the process, and exit the program if the user has changed their values. Another posibility is to check the logical name table where the logical name was found. The version 4 calls allow much more flexibility here, and I know that certain utilities ignore non-SYSTEM EXECutive-mode logicals, but I'm not sure how they do it. I read about it once, but I can't find the information any more. If I come across it again, I'll let you know. Good luck with your problem. DPVC
info-vax@ucbvax.UUCP (02/07/86)
So use the /TRANSLATE=TERMINAL feature....
$ DEFINE SYS$SYSTEM DRA0:[SYS0.SYSEXE]LOGINOUT.EXE/TRANS=TERMINAL
This will redefine SYS$SYSTEM and the TRANS=TERMINAL will prevent the
name from being translated any further.
-------------------------------------------------------------------
John Owens
john%odu.csnet@csnet-relay.arpa
General Electric Company Phone: (804) 978-5726
Factory Automation Products Division Compuserve: 76317,2354
ihnp4!houxm
...!{ decvax!mcnc!ncsu!uvacs }!edison!jso
gatech!allegra!uvacs