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

["Richard Casey" <casey_r@xxxxxxxxxxxxxxxx>]

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


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan
Sent: Tuesday, April 08, 2003 10:35 AM
To: midrange-l@xxxxxxxxxxxx
Subject: how to determine authority & lock level required for CLRPFM


I need to clear a file in CL and check for specific conditions:
  1) If there are any locks on the file that would prevent a CLRPFM to
complete.
  2) If the user has the appropriate authority to clear this file.

I know I need ALCOBJ for #1 and CHKOBJ for #2.  What I need to determine is
parameter values to
specify for them.  Specifically, the Lock State for ALCOBJ, and the
Authority for CHKOBJ.  If
someone can answer these for me, that'd be great.  But I'd really like to
know where/how to
determine this information, as I'm sure I'll run across this again in the
future.

(FWIW, we're at v5r2.)

TIA, Dan