|
Just found that the rstusrprf command being used is doing
RSTUSRPRF DEV(TAP01) USRPRF(*NEW) ENDOPT(*REWIND) +
SECDTA(*PWDGRP) OUTPUT(*OUTFILE) +
OUTFILE(DISASTER/RSTUSRPRF) OUTMBR(*FIRST +
*REPLACE)
I wonder if I should be using SECDTA(*USRPRF) instead.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Friday, June 18, 2010 2:14 PM
To: Midrange Systems Technical Discussion
Subject: RE: Authorities not reset properly on restore
Jack,
I double checked and I do run savsecdta on our daily save, which is
then used to do the restore. I actually delete the libraries prior to
the restore.
Thanks
Mike
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Friday, June 18, 2010 1:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: Authorities not reset properly on restore
Shouldn't you run the savsecdta first, what about clearing your
libraries prior to the restore, may not be necessary though.
On Fri, Jun 18, 2010 at 1:48 PM, <rob@xxxxxxxxx> wrote:
Then I would have thought there would be something in the joblog<midrange-l@xxxxxxxxxxxx>
like authority not restore because... or something like that.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
Date: 06/18/2010 01:36 PM
Subject: RE: Authorities not reset properly on restore
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Yes, I'm using ALWOBJDIF(*ALL)
Here is my command
RSTLIB SAVLIB(&RSTLIB) DEV(TAP01) ENDOPT(*REWIND) +
MBROPT(*ALL) ALWOBJDIF(*ALL)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, June 18, 2010 12:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: Authorities not reset properly on restore
Are you specifying ALWOBJDIF(*ALL) ?
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 06/18/2010 11:11 AM
Subject: Authorities not reset properly on restore
Sent by: midrange-l-bounces@xxxxxxxxxxxx
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.
--
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.
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.
--
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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,http://archive.midrange.com/midrange-l.
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
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,http://archive.midrange.com/midrange-l.
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
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
