Re: Question on BRMS *SYSTEM Backup Control Group....

< I think of a migration is a completely different operation to a recovery.

+1 totally correct.

And what the BP was attempting was probably not supported by IBM.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Evan Harris
Sent: Thursday, October 25, 2018 2:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: Question on BRMS *SYSTEM Backup Control Group....

Sounds to me like they did a mixed release migration in which case trying
to use a BRMS save would have been a bit off the beaten path. It seems to
me that using BRMS in this scenario would be at least a bit problematic as
the BRMS product itself would be upgraded as part of the migration; the
BRMS products would likely show as *BACKLEVEL until the OS Upgrade steps
were performed.

I can understand a preference for a 21 save during a migration as that
would be my preference also. I think of a migration is a completely
different operation to a recovery.


On Fri, Oct 26, 2018 at 5:25 AM Andrew Lopez (SXS US) <
Andrew.Lopez@xxxxxxxxxxxxxxxxxx> wrote:

Sounds like they were following this:

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzamc/rzamc1.htm

Took me a while to read through that, but it does look like the process
that was used.

Based on the responses, it would seem like I'm wasting my time trying to
make BRMS work like a manual 21 save. If they're willing to use BRMS, a
*SYSTEM is fine. If we're in an upgrade and they want to follow a

special

process, it's back to a manual save.

I'm thankful I only face that once every 5 years. Of course, the IBM
directions say to have two backups (something I agree with

wholeheartedly,

and did as well), which means doing two manual system saves, back to

back.

Like I said, I'm glad it only happens occasionally.








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

--

Regards
Evan Harris
--
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