× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On the target system, I believe I have options.
But in any case, needs to be done prior to final IPL.

1) Prior to Step 8: Update System Name in BRMS Media Information of BRMS recovery report
https://www-01.ibm.com/support/docview.wss?uid=nas8N1013153

2) or prior to Step 32: Perform IPL, of BRMS recovery report.

A concern, if I'm going to test multiple, concurrent BRMS restores using multiples devices.
From one of Jim's earlier related posts
< Using multiple drives for multiple BRMS recoveries, You can't be in a restricted state but you can have the system severely restricted.

You can only have one HMC console session, correct.
So in order to start additional interactive sessions for BRMS restores, minimum network connectivity would need to be created/started.
With that said, system name, ip, etc would have to be changed.

Paul




-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, November 05, 2018 11:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS test recovery - should test recovered system name be changed before or after the recovery

How does one change it "before the restore"? Does one change it prior to
the save on the live system? If so, I would NOT do that as the risk of
executing the MAKEAMESS command is too great. Do it on the target system,
prior to bringing it out of restricted state.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.