• Subject: Re: COMMAND AUTHORITY LOGIC
  • From: "oludare" <oludare@xxxxxxxxxxxxx>
  • Date: Mon, 11 Dec 2000 13:06:36 -0500

Neil,

How do I change the parameter "State used to call program" from *USER to
*SYSTEM.  The parm only shows when a DSPOBJ is issue on QLICHLIB.

Thanks

Oludare

----- Original Message -----
From: "John Earl" <johnearl@400security.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, December 08, 2000 3:56 PM
Subject: Re: COMMAND AUTHORITY LOGIC


> 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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.