×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi, David,
It all starts with the system value QCRTAUT. Prompt CHGSYSVAL, type
QCRTAUT in the system value name, and then with the cursor in that
field, press F1=Help, and page down to read the help text for "QCRTAUT."
Next, prompt the CRTLIB command, and press F10=Additional parameters,
and there are two parameters you want to look at, AUT and CRTAUT ...
place the cursor in each field and press F1=Help to read about each one.
AUT controls the default *PUBLIC authority for the *LIB itself. If
*LIBCRTAUT is used, it "inherits" from the containing library, and since
all *LIBs exist in QSYS, it inherits from QSYS. DSPLIBD QSYS will show
you those attributes. Note that if Create Authority (CRTAUT) is set to
*SYSVAL, it uses the value from QCRTAUT (see above).
When you create any object in a library, its "owner" is the current user
profile, unless that user has a primary group profiule and the user
profile OWNER attribute is set to *GRPPRF, in which case it is owned by
the primary group profile. But the *PUBLIC authority for that object is
determined based on the CRTAUT parameter of the containing library.
And, if you want to get "fancy" you can create an authorization list,
and then assign that to CRTAUT for a library, and then, any objects you
create in that library will be "attached to" that *AUTL, and so any
users or groups who are given authority via that authorization list will
have authority to this new object.
Does that help?
Mark S. Waterbury
> On 3/2/2018 11:00 AM, David Gibbs wrote:
Folks:
I feel like this is something I should know ... but for the life of me
I can't figure out.
I've got a situation where a library is being created and it
immediately has an authorization list attached to it.
On another system, however, a newly created library has no
authorization list attached.
Both systems are 7.3.
The CRTLIB commands on both system have OS default parameters. The
authority on QSYS is normal.
Any suggestions on what attribute (system value, user profile
attribute, etc) controls default authorities on a newly created library?
Thanks!
david
midrange.com
