MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » April 2012

ILE PGM getting authority error when it does have authority



fixed


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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact