Re: Authorities not reset properly on restore

Mike,
Can you clarify something from your orig note.
It says "Mercury is deleted" then "...restored".
Is your pgm actually doing a delete?
Is the Mercury profile on the system before the restore?
There are things that happen to profiles and groups when restoring
to a "different system" and the profiles have differences (between whats on tape & what's on disk".
I don't have quick access to the Backup/Recovery manual and the Security Reference, but I think you answer will be in there.
Also, file is owned by QSECOFR.
Are you restoring as QSECOFR?
Jim Franz
----- Original Message ----- From: "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, June 18, 2010 10:42 AM
Subject: Authorities not reset properly on restore

I'm doing some DR testing, refreshing data from our production machine
to our DR/Test machine.
I'm running into an issue where some files are not having authority
restored properly on the DR machine.
For Example

File BILLING
Owned by QSECOFR
No authorization list
*PUBLIC has *CHANGE
*GROUP QSECOFR has *ALL
*GROUP MERCURY has *ALL

When I perform restore
User Mercury is deleted
User Mercury is restored
Files are restored
RSTAUT is run

However *GROUP MERCURY doesn't show under dspobjaut for file BILLING


Any idea why this is occuring.

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: 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.