I belong to 'hard-last' school because once HSA is updated, all systems want to
IPL next with the new IODF. z/OS itself has no 'recollection' of what IODF it
was using previously. If a soft activate needs to be backed out, the next IPL
will come up matching HSA as long as you use the appropriate wild card
characters in LOADxx.
Changing a device from one type to another is actually accomplished by deleting
the old device and adding the new one. Deletion generally requires 'FORCE' on
the activate command. If the new IODF is wrong for any of the LPARs on the CEC,
you may find yourself having to POR to set things right. 'TEST' is the right
first step, but depending on what you're changing, you're usually instructed to
specify FORCE on the hard activate, so you need to proceed with caution.
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Elaine Beal
Sent: Monday, September 19, 2016 10:16 AM
Subject: (External):Re: IODF Dynamic Activation Reversion
Thanks for the responses.
Of course our change process will not allow saying it's never happened before
as justification for not having a reversion plan.
I always do a TEST before activations
I've debated HARD first or SOFT first but doing HARD first is really contrary
to our change procedures- that being changes should be rolled out
DEV-->QA-->PRE-PROD-->PROD so it makes more sense to me (and is somewhat
required for change management) to do SOFT until the last PROD and then do a
Sometimes I hate change management!
These particular changes are two fold
1) allowing some additional LPARs to some existing OSAs
2) redefining two OSAs from OSD to OSE
I had the two options to
1 - continue through until changes are activated on all LPARs (SOFT on all
except one HARD on the last PROD LPAR)
2 - POR
from Jesse I see a (better) 3rd option
3 - IPL back to the old IODF
If I'm understanding correctly, IPL is the only way for me to revert
immediately without impact to other systems.
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN