|
Practical experience, just what I was
hoping for. Thx, will trust the statement now (with Richard’s proviso “Any device in
the Offline_at_ipl category will be left offline with one possible exception -
if you IPL a device in that range, it will be left online.”). Regards,
From: We use Offline_at_IPL for
exactly that purpose: to tell CP to leave some dasd devices offline during
IPL so CP won’t look at their volids and possibly find they’re
duplicates of other online volids. Your AUTOLOG1 PROFILE EXEC can do a CP VARY ON xxxx-yyyy to
put the offline devices online shortly after IPL. This e-mail, including any attachments,
may be confidential, privileged or otherwise legally protected. It is intended
only for the addressee. If you received this e-mail in error or from someone
who was not authorized to send it to you, do not disseminate, copy or otherwise
use this e-mail or its attachments. Please notify the sender immediately
by reply e-mail and delete the e-mail from your system. From: Looks safe, but… In our plan to test a new
release of VSE (3.1) we plan to isolate a copy of our production VM system as a
2nd level system, then install the new VSE on this system. This
scenario would give us duplicate volsers for all the volumes in the System
Config. If we specify the address range of the ‘restored’ dasd as
‘Offline_at_IPL’ are we assured that this statement will be
processed/respected before the Ipl proceeds so we will not encounter CP picking
up our ‘restored’ volume instead of the real production volume? Thanks in advance,
|
- Offline_at_ipl Richard Feldman (WFF)
- Re: Offline_at_ipl Romanowski, John (OFT)
- Re: Offline_at_ipl Richard Feldman (WFF)
- Re: Offline_at_ipl Adam Thornton
- Re: Offline_at_ipl Schuh, Richard
- Re: Offline_at_ipl Schuh, Richard
