This may seem an odd question but are you sure the failing program and file in question are the ones you think they are?
When you do WRKOBJ OBJ(*ALL/programName) OBJTYPE(*PGM) how many copies do you find?
When you do WRKOBJ OBJ(*ALL/fileName) OBJTYPE(*FILE) how many copies do you find?
Maybe a library list issue?
Gary Monnier
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeffrey Tickner
Sent: Thursday, April 05, 2012 12:09 PM
To: midrange-l@xxxxxxxxxxxx
Subject: ILE PGM getting authority error when it does have authority
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
Jeff Tickner
Arcad Software
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
