Not authorized to Object

[mguske]

We have two different instances with two different library lists.
The file in question in both instances has *PUBLIC *EXCLUDE.
Yet, when a field is updated in instance #1, it updates fine (this is the desired behavior).
However, for instance #2, we get "SQLERROR. Checking Statement handle... SQLSTATE = 42501 Native Error = -551 Message = "Not authorized to object WNPXSPSDL in MD_TEST20 type *FILE."".
There has to be some behind-the-scenes setting which allows an update against a *PUBLIC *EXCLUDE file in instance #1 but not in #2....
Where do I need to look?
Thanks!
Matt

[sean.lanktree]

We spoke to somebody else at your office about this and determined this is related to a custom authority process run against the objects in each instance.

[mguske]

That is what I suspect, but I'm trying to track down where that happens. Is there some sort of logging in Valence that would point me in the right direction?

[robert.swanson]

Not for something like this, other than what you see in the Errors application. It has to do with program object authorities. Talk to your colleague - I believe he found a CL program that applies overrides.

[mguske]

So, you think the CL program was something my colleague created versus him utilizing a Valence program to implement the file override?

[mguske]

PS. The reason I am inquiring is because this colleague is no longer with the Company.

[robert.swanson]

Yes, I believe he created a CL program to (re)adjust certain program object authorities after each upgrade.

[mguske]

Thank you.