Good point Rob. I'm too used to *ALLOBJ authority.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, April 05, 2012 12:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: ILE PGM getting authority error when it does have authority
Possibly a duplicate object that you are not seeing in the library list?
Do NOT use WRKOBJ! That simply won't show you objects you are not authorized to. Perform a DSPOBJD instead. That will tell you if you are not authorized to the first object it finds in the library list.
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
Kendallville, IN 46755
From: Jeffrey Tickner <jtickner@xxxxxxxxxxxxxxxxx>
Date: 04/05/2012 03:09 PM
Subject: ILE PGM getting authority error when it does have
Sent by: midrange-l-bounces@xxxxxxxxxxxx
This makes no sense so I'm thinking there is another attribute that is
causing this authority error as a red herring.
There is an ILE program object, 29 modules bound in, that has an owner of
FILEUSER and it adopts *OWNER authority.
It was recently recompiled and now when it goes to update a file it gets a
CPF4269 not authorized to object.
The file it is trying to update is secured by an AUTL that has *PUBLIC
*EXCLUDE and FILEUSER *ALL.
As a test the program object was compiled again in a temporary library,
that library moved to the top of the library list and it works fine with
the same settings.
I'm think there is something different in how the 2 objects were compiled
but I don't have a compile listing anymore for the first program so I
don't know the exact create parms.
Is there any other attribute that can cause an authority error?
They both have the same activation group, QILE.
I searched the archives for CPF4269 and didn't find anything helpful