Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!hao!ames!ucbcad!ucbvax!GRIN2.BITNET!MCGUIRE From: MCGUIRE@GRIN2.BITNET Newsgroups: comp.os.vms Subject: Re: Definition of LNM$JOB Message-ID: <8712151255.AA08185@ucbvax.Berkeley.EDU> Date: 15 Dec 87 06:27:00 GMT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 25 > Date: 11 Dec 87 03:09:58 GMT > From: Jeff Capehart> Subject: Re: Definition of LNM$JOB > > You may be able to create an alias, but LNM$JOB is an [exec] mode logical > name and there is no way a user can override this if the translations are > done properly. Therefore it is silly to say that the user might redefine > what LNM$JOB is supposed to be. On the contrary: The executive mode logical name need not be deleted at all. The user can define LNM$JOB in supervisor mode. The result is that LNM$JOB is defined twice, once flagged EXEC and once flagged SUPER. Supervisor mode logical names are translated before executive mode ones. Of course, you can tell the $TRNLNM translation service to start the search with executive mode logical names, skipping the redefined name. The image activator is particularly careful to do this when activating images installed with privilege. I realize that the above discussion does not relate to your problem of finding another user's job table, but I thought a point of confusion should be cleared up. Good luck! Ed