Some of us wrote about so called rescue system.
Usually it is small ("one pack") z/OS system, which can be IPLed as a last resort. Update RACF db? Yes, but ...no, because some changes can make the system un-IPLable.
Test it? Yes, frequently. But... it happen to be not frequent.
A lot of risks related to possible human errors, oversights, etc.
Other mention ZZSA or stand-alone ADRDSSU&ICKDSF.

However we have LPARs.
I'm pretty sure everyone is running a machine with LPARs. (not talking about museum, zPDT or Hercules)
So, what's the problem with keeping some tech LPAR up and running?
It does consume very few CPU cycles, few memory, same disk space.
The only possible case when the tech system would not help is Power On Reset. Which is quite rare. Rare enough to prepare for that by testing tech system - re-IPL before POR. And of course when you have more than one CPC (DR, sysplex, etc.) even POR will not shut down some your tech system. Besides the risk of IPL failure, the advantages of having up and ready z/OS is quite obvious IMHO. I use such LPAR since times of OS/390. And yes, I fixed a lot of small and few big errors during IPL of prod systems.

--
Radoslaw Skorupka
Lodz, Poland

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to