Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Logical Names (again)
Message-ID: <8602062218.AA20443@ur-tut.UUCP>
Date: Thu, 6-Feb-86 17:18:46 EST
Article-I.D.: ur-tut.8602062218.AA20443
Posted: Thu Feb  6 17:18:46 1986
Date-Received: Sun, 9-Feb-86 07:41:44 EST
References: <8602021401.AA04216@ucbvax.berkeley.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: U. of Rochester Computing Center
Lines: 21
Approved: info-vax@sri-kl.arpa

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