Re: COMMAND AUTHORITY LOGIC

[John Earl <johnearl@xxxxxxxxxxxxxxx>]

I believe this issue arises when you modify a system domain object
(the CHGLIBL command).  When you modify it, the command becomes
"user domain" and is no longer eligble to directly reference a
system state program.

You can verify this if you have QAUDJRN turned on.  Look for
Journal Code "T" and journal type "AF".  Then scan the first byte
of the data structure for the violation code of either "C" or
"D".  If you find these litter uglies, then I've correctly
diagnosed the problem.

However, all of this assumes that you're at QSECURITY level 40 or
50.  If you're not, then I'm dead wrong.  :)

jte

oludare wrote:

> Hey guys, I am on OS400 V4R3M0 Current CUM. I ran into a problem
> this morning when I changed an IBM object CHGLIBL command. I
> change the parameter call "program to process the command", by
> mistake, and change it back to what it was but users ran into
> problem with "Not authorized to QLICHLIB program".  The program
> authority for users is *EXCLUDE before and after the change.  In
> the end, I had to change QLICHLIB to PUBLIC *USE for them to
> have access again. Question: How did user gain access to
> QLICHLIB prior to the change.

--
John Earl                    johnearl@400security.com
The PowerTech Group      --> new number --> 253-872-7788
PowerLock Network Security   www.400security.com
--


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---