Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!burl!codas!ufcsv!beach.cis.ufl.edu!jdc
From: jdc@beach.cis.ufl.edu.UUCP
Newsgroups: comp.os.vms
Subject: lnm tables
Message-ID: <9297@ufcsv.cis.ufl.EDU>
Date: Mon, 23-Nov-87 16:53:22 EST
Article-I.D.: ufcsv.9297
Posted: Mon Nov 23 16:53:22 1987
Date-Received: Thu, 26-Nov-87 23:35:36 EST
Sender: news@ufcsv.cis.ufl.EDU
Reply-To: jdc@beach.cis.ufl.edu (Jeff Capehart)
Distribution: world
Organization: UF CIS Department
Lines: 19


     I have been trying to use logical names in separate job tables and this
     works fine for the processes that use that job table.  Any other process
     which has access to the LNM$JOB_xxxxxxxx table cannot translate the
     logical name unless it knows what the name of the table is.  The only
     way I can think of finding out the "logical name table tree" for a given
     process is to use SHOW LOGICAL/Structure and route the output to a file
     and then scan it for job tables.  Is there an easier way to do this?
     I can't even use the $TRNLNM service to use a wildcard in the field for
     logical name.  Wildcards can be used on $GETJPI but not on log names.

     If anyone has any suggestions I would greatly appreciate it.  Please
     don't tell me to use the system table because this has to be done from
     a regular user account.  It would be nice to have SYSNAM... but...

     Thanks in advance...
--
Jeff Capehart 		Internet: micronaut%oak.decnet@pine.circa.ufl.edu
University of Florida	UUCP:	  ..!ihnp4!codas!ufcsv!beach.cis.ufl.edu!jdc