Be careful an IODF is different than the IOCDS for HSA. An IODF is a file that gets put on your PARM disk and is referenced in your SYSTEM CONFIG file. There are people here that can fill in the blanks, but if you have a z/OS LPAR on the same box as the z/VM LPAR let z/OS handle changes and z/VM will automatically pick them up with Restrictions when it comes to deleting devices, Control Units, and Channels
Larry Davis From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Michael Coffin Sent: Tuesday, June 07, 2011 11:15 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Dynamic Activation of New IODF Hi Folks, For many (many) years, when it comes to managing the IOCDS I simply hand-create an IOCP file, use IOCP with WRTAx to store it, and do a POR to load it. If the changes are needed immediately, I use CP commands to manually define the new hardware. Our z/OS guys want to manage the IOCDS and be able to dynamically activate an entirely new IODF file (created either on their system or using VM's HCM/HCD). I'm unclear as to when/how the changed IODF file becomes dynamically available to the running z/VM system. Let's say I store the new IODF using IOCP with WRTAx to store it, and then execute SET IOCDS_Active to mark it as the active IOCDS - according to the doc for SET IOCDS_Active this simply marks the IOCDS as active for the NEXT POR (and write-protects it) - but it doesn't look like the changes in the new IOCDS are reflected to the running z/VM system until a POR occurs. What am I missing here? Is it even possible to store a new IOCDS, mark it as active for the next POR AND have CP add/change/delete IO definitions by comparing the prior IOCDS with the newly activated one? -Mike
