Re: QTEMP objects and Different Users on the Same Job

Hi, Brad:

If you prompt the CRTPF command (for example), and press F10=Additional
parameters, and page all the way down, you will see that the last parameter
is "Authority ..." (AUT). It defaults to *LIBCRTAUT. That is, it inherits
the default *PUBLIC authority from the containing library. That is also
true for most, if not all, "create" commands ... they all have an AUT
parameter to assign the default *PUBLIC authority.

When the system creates a QTEMP library for a job, it is created with
AUT(*SYSVAL), so it inherits from the system value QCRTAUT. When I issue:
DSPLIBD QTEMP

I see:
Create authority . . . . : *SYSVAL

Rather than having to find and change every occurance of a create command
within your entire web application, you could just run the following CL
command, somewhere "early" during the initialization (start-up) of your web
job(s):

CHGLIB LIB(QTEMP) CRTAUT(*ALL)

or issue this somewhere prior to when your job is about to create any
objects in QTEMP. That way, the default AUT(*LIBCRTAUT) will inherit *ALL
from the QTEMP library.

NOTE: if some objects have already been created in QTEMP, prior to issuing
the above CHGLIB command, it will be "too late" for those objects, as
changing this attribute only changes the *LIB itself, and not any objects
that already exist within that library.

You could call a program that adopts authority of a "powerful" profile, to
do any "clean up" or "deleting" of pre-existing objects, where that profile
has *ALLOBJ authority, and that way, you can ensure that it will be able to
delete any objects in QTEMP, no matter what userID created them.

Hope that helps,

Mark S. Waterbury