RE: how to determine authority & lock level required for CLRPFM

Absolutely perfect, Richard!  

I had searched my v4r5 softcopy, forgetting that the CL Reference was not 
included in that version
(@#$%*!!!).

Thanks, Richard!

- Dan

--- Richard Casey <casey_r@xxxxxxxxxxxxxxxx> wrote:
> Dan,
> 
> Check out the CL Reference Manual. The info for CLRPFM lists the following
> restrictions.
> 
> Restrictions:
> 
> 1. The user must have object operational, object management or alter, and
> delete authority for the physical file that contains the member and execute
> authority to the library.
> 2. If any of the access paths to the member are in use when this command is
> entered, or if the physical file member is in use, the command is not run.
> 3. An *EXCL lock is required on the member to clear it.
> 4. In multithreaded jobs, this command is not threadsafe for distributed
> files. This command is also not threadsafe and fails for Distributed Data
> Management (DDM) files of type *SNA.
> 
> >From restriction #3, the ALCOBJ command could look like
> 
>       ALCOBJ OBJ((library/file *FILE *EXCL))
> 
> >From restriction #1, the CHKOBJ commands could look like
> 
>       CHKOBJ OBJ(library/file) OBJTYPE(*FILE) AUT(*OBJOPR *OBJMGT *DLT)
>       CHKOBJ OBJ(library) OBJTYPE(*LIB) AUT(*EXECUTE)
> 
> If you are going after a specific member of the file, you'll need to add the
> member name to the ALCOBJ command.
> 
> Hope this helps!
> Richard


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com