BRMS can completely back up a system, but the concept of the *NONSYS does
not exist in BRMS. It does:
*SAVSYS
*IBM
*ALLUSR
*ALLDLO
*LINK
So if you recover manually just use those special recovery items in that
order and it will work fine. I pointed that out earlier last week.
Restore LIC and OS from D mode IPL
RSTLIB *IBM RSTLIB SAVLIB(*IBM) DEV(MYTAPEDEV) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)
RSTLIB *IBM RSTLIB SAVLIB(*ALLUSR) DEV(MYTAPEDEV) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)
RSTDLO DLO(*ALL) DEV(MYTAPDEV) ALWOBJDIF(*ALL) OUTPUT(*PRINT)
RST DEV('/QSYS.LIB/MYTAPEDEV.DEVD') OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS'
*OMIT))
RSTAUT
Your done.
ALL business partners should be able to deal with that..........
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Andrew Lopez
(SXS US)
Sent: Thursday, November 01, 2018 2:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: P7 V7R3 to P9 V7R3 migration recommendations / suggestions
I plan on re-attempting the BRMS recovery.
A lot has changed and improved since 2012.
I asked a similar question in the last 30 days for a very similar situation,
though we don't have multiple tape drives. I received differing responses
from people who were waaaay more qualified than me. One said that BRMS will
never be able to duplicate the portion of a manual save 21 where *NONSYS
libraries are saved, while the other believed it was possible to create a
policy that did so.
It was fairly evident that the problem with a BRMS *SYSSAV backup isn't
_what_ it saves, but how it labels the various objects backed up. Most
migration outlines assume that you have labels on the tape that match a
manual 21 save, and without them a user is required to have more in depth
knowledge of how to restore to the new system.
I haven't had a chance to validate either viewpoint (you can or cannot
create an exact copy of a manual 21 save in BRMS).
You may want to review the mailing list to find that conversation.
--
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:
https://amazon.midrange.com
midrange.com
