Path: utzoo!mnetor!uunet!husc6!rutgers!super.upenn.edu!eecae!nancy!umix!umich!mibte!gamma!pyuxp!pyuxww!sabre!faline!bellcore!clyde!burl!codas!ufcsv!beach.cis.ufl.edu!jdc From: jdc@beach.cis.ufl.edu (Jeff Capehart) Newsgroups: comp.os.vms Subject: Re: Definition of LNM$JOB Message-ID: <9731@ufcsv.cis.ufl.EDU> Date: 11 Dec 87 03:09:58 GMT References: <8712080924.AA13169@ucbvax.Berkeley.EDU> Sender: news@ufcsv.cis.ufl.EDU Reply-To: jdc@beach.cis.ufl.edu (Jeff Capehart) Organization: UF CIS Department Lines: 37 In article <8712080924.AA13169@ucbvax.Berkeley.EDU> NELSONJE@VTVAX5.BITNET (Where am I?) writes: > >Now that you know, you should forget it. There are several reasons why. >First, because users (like me) may decide that they want to redefine LNM$JOB. >Note that it doesn't take any special privileges to create a logical name >table in the LNM$PROCESS_DIRECTORY table; I do it all the time, and stick my >mail aliases in the table. The table (JEN$MAIL_NAMES) is search-listed with >the former definition of LNM$JOB thusly: > >$ define/table=lnm$process_directory lnm$job - > 'f$trnlnm("lnm$job","lnm$process_directory")', JEN$MAIL_NAMES 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. >The point is this: the user has much more control over his logical name >tables, and which ones get searched. You shouldn't depend on a specific >definition of LNM$JOB because you might be wrong. In fact, it's conceivable >that the user decides *never* to include LNM$JOB in LNM$FILE_DEV, etc. Again, how would the user delete [exec] mode logical names? Anyways, I am not really worried about my own job table. I have a situation where user1 creates a mailbox to converse with user2, send back stats and that sort of info. The logical name for the mailbox is put in LNM$JOB for user1. User2 would like to translate the logical name so it can open the proper mailbox. User1 sets an acl on his job table so that User2 can read from it. User2 now has access but has no idea what the name of the table is. Aside from dumping output from "show logical" to a file, since I could just as easily dump the mailbox name to a file, how is user2 supposed to figure out what the name of user1's job table is? -- Jeff Capehart Internet: micronaut%oak.decnet@pine.circa.ufl.edu University of Florida UUCP: ..!ihnp4!codas!ufcsv!beach.cis.ufl.edu!jdc