Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!lll-tis!lll-lcc!ptsfa!ihnp4!cbosgd!clyde!burl!codas!ufcsv!ufcsg!jdc
From: jdc@ufcsg.cis.ufl.EDU (Jeff Capehart)
Newsgroups: comp.os.vms
Subject: Re: ACL's again
Message-ID: <867@ufcsg.cis.ufl.EDU>
Date: Fri, 30-Oct-87 23:43:28 EST
Article-I.D.: ufcsg.867
Posted: Fri Oct 30 23:43:28 1987
Date-Received: Thu, 5-Nov-87 06:51:07 EST
References: <8710231441.AA02608@ncsc.ARPA> <2752@batcomputer.tn.cornell.edu>
Organization: UF CIS Department
Lines: 7
Summary: Another question on ACL object types


	I was looking at the different types of objects that an ACL can be placed on, when I tried /object=process and I got an error BAD PARAMETER.  After searching through the DCLTABLES I did come across process as being a valid qualifier for the SET ACL command.  My problem is that I do not know what object to specify.  $ SET ACL/OBJ=PROCESS/ACL=(id=*,acc=r)    will then prompt for $_Object
	Now what do you enter?  I tried process names, process id's , and even UIC's and usernames.  All gave BAD PARAMETER VALUE.  I am assuming that DEC put this in as a future upgrade to ACL's, included the CLD for it but did not implement it.  If anyone has gotten this to work I would be much appreciative.
	The SET ACL/obj=logical LNM$JOB  is another neat feature.  If you are another process and do SHOW LOG/STRUCTURE you will see all the tables you have access to.  I am also curious as to find out these logical table names through a SYSTEM SERVICE or some call so that a program can make use of the access.

		Jeff Capehart
		Gainesville, FL