RE: rstaut 7.3 -- MIDRANGE-L

Thanks.

I'll check that out. It looks like it might be set to *NO

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Steinmetz, Paul
Sent: Wednesday, April 25, 2018 11:39 AM
To: 'Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)' <midrange-l@xxxxxxxxxxxx>
Subject: RE: rstaut 7.3

Mike,

I ran into a similar issue a while back.
The issue wasn't the restore, but the private authorities were not being saved.
The default is *NO, not to save private authorities.
Recheck your save.

Private authorities . . . . . . *NO *NO, *YES

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Wednesday, April 25, 2018 11:30 AM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: rstaut 7.3

We do periodic data refreshes from our production machine to our development machine. We have been doing it the same way for a decade or better and have not encountered this before.

After I performed a refresh after our upgrade to 7.3, I noticed that data authorities didn't seem to restore properly

Files that are QSECOFR owned, but have authority granted to a group profile didn't get the group profile authority restored.

However files that are QSECOFR owned, but have an authorization list attached, seem to have restored properly.

I've run this twice, just in case I somehow messed it up myself.

Any idea if there are any changes I need to be aware of, or why this might be happening.

We restore profiles, then restore files, then restore authority.

Thanks

Mike
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.