I see some crossed wires here. First of all, writing an IOCDS to the support element is totally independent of dynamic changes. Writing the IOCDS prepares for the next POR; it has nothing to do with dynamic changes. Until the next POR, contents of the Ax slots are irrelevant.
Second, in the ACTIVATE command, the xx in IODF=xx must match the suffix of your new IODF cluster, as in SYS1.IODFxx. Unless the IODF happens to be named IODFA2--pretty improbable--then the command as coded will not work. In a dynamic change, the currently active OS IODF is compared with the current HSA IODF. If the tokens match, the new IODF will be written into HSA for the next activate. If the tokens do not match, you get the error shown. The only time the HSA IODF/token changes is at POR or successful dynamic activate. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of August Carideo/RYE/US > Sent: Thursday, January 7, 2016 11:10 PM > To: [email protected] > Subject: [Bulk] FW: IODF Dynamic Changes > > I think you had a step out of sequence > Are you getting that message during activate? > You may want to look at this if you a sure they in fact do match > > activate iodf=a2,soft=novalidate > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Mainframe Mainframe > Sent: Thursday, January 07, 2016 11:23 PM > To: [email protected] > Subject: IODF Dynamic Changes > > Hello, > We have z/OS and z/VM both in our Mainframe in diff LPAR. We recently > added few more CHPID and devices and provided access to z/VM LPAR by > coping the current IODF into new IODF and created production IODF from this > new IODF. After this, > > 1) I used UPDATE option while built IOCDS and wrote in A2 profile. > > 2) Now, I would wanted to switch this new IODF dynamically using this IOCDS > option but didnot allowed me saying > > Error > Action for A2.ZEC12 failed. The IOCDS token does not match the HSA token. > > 3) Then I realized, I should use option 6 to activate or verify configuration > but in > the option 6 , which one we should be using it not sure. > > Can anyone help me to activate this new changes. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
