What change are you making? Until you activate hardware, would expect all your software activations to be reversible.
You shouldn’t have to POR until you lose the ability to dynamically get to where you want to be. Which more likely be due to lack of maintenance time, frustration, etc. and convenience of instant resolution. For example, bad change to your only OSA. You can’t logon to fix and go forward and you’re out of sync/unable to go backward. Have you tested the activation on all your systems and/or tested the software only change on a test system? The prior will highlight the changes and give you a better idea of the risk. For example, some changes to an existing definition actually result in a delete then add of the definition. So the respective definition would need to offline, not in use, etc. Regards, Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elaine Beal Sent: Thursday, September 15, 2016 12:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IODF Dynamic Activation Reversion I'm rolling out IODF changes dynamically, all SOFT and HARD on the final LPAR. Our change management rules have gotten more stringent and I need to define a reversion plan. If on say, the third LPAR something goes awry and we need to back out, are there options besides 1) POR or 2) continue on to HARD activate and then perform the process across all LPARs with the old IODF (soft on all except HARD on last) I have an old ETR that says I can back out on a SOFT activate but at that point dynamic activation is disabled. Thanks, Elaine ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
