I found the issue.
The userprofile restoring the libraries only had *ALLOBJ special authority.
Needed to have *ALLOBJ and *SECADM
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Voris, John
Sent: Thursday, September 12, 2013 5:25 PM
Subject: Restore lib results with public *exlude authority
Recently noticed that a 20,000 object R&D program library had majority of its objects set to *public *exclude following a RSTLIB on 5/29.
As a test, I restored the same library again, to a different library, *public is now *change, which are normal results.
Any ideas on what might cause a RSTLIB to result with *public *exclude?
Isn't there a setting to use the authority settings that the library itself has when restoring objects into it with certain keywords on ALWDIFF etc . .
If the library is first created with *public *exclude, the objects in it are set the same.
Or am I thinking of the IFS and Windows . . . ?
- John Voris
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l