Hey Paul

Yeah, the "private" authorities in this case are for group profiles - is that what you mean by group authorities?

I'm not the guy who is tasked with this - just a messenger this time!!


On 9/15/2015 2:28 PM, Steinmetz, Paul wrote:

I've also had this issue.
By default, private authorities are not saved, so they cannot be restored.

Private authorities (PVTAUT) - Help
Specifies whether to save private authorities with the objects that are
saved. Saving private authorities will increase the amount of time it
takes to save the objects, but it can simplify the recovery of an object
or a group of objects. It will not simplify the recovery of an entire
No private authorities are saved.
Private authorities are saved for each object that is saved.
Note: You must have save system (*SAVSYS) or all object
(*ALLOBJ) special authority to specify this value.

I've changed my philosophy to use all group authorities, have been removing all private authories.

If you really need the private authorities, read the help text for Print Private Authorities (PRTPVTAUT)
I've used this a few times, doable but ugly.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, September 15, 2015 3:12 PM
To: Midrange Systems Technical Discussion
Subject: Applying authorities after restore

We've a situation here - looking for ideas.

New LPAR that is to have the same objects but in different library.

Files in library LIB01 on LPAR01 saved and then restored to LIB02 on
LPAR02 with PVTAUT(*NO).

There were private authorities on all these files on LPAR01. There are NO private authorities on these files on LPAR02 - makes sense, I know.

We need the private authorities to be the same as they were on LPAR01 - all users ARE present on both partitions.

So question I was asked, is there a way to apply the private authorities after the restore, where there is now only the owner's and a *PUBLIC on the objects?

There have been changes to the data already since the restore - that just complicates things, I'd say.

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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.