Mike, I use XEDIT to maintain the IOCP file. There is a HCM application distributed with the z/VM HCD, but I find it difficult to use.
I then run the following commands from userid CBDIODS. CBDSIODF to create a HCD skeleton file. CBDSMIGR to create a work IODF by loading the IOCP source into the skeleton file. CBDSPROD to create a production IODF file, filetype PRODIODF. CBDSIOCP write the IOCDS. CBDSACT to active the IOCDS without a POR. The PRODIODF file needs to be copied to all CP parm disks. "IODF *" is specified in the SYSTEM CONFIG on the CP parm disk. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Michael Coffin Sent: Tuesday, June 07, 2011 9:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: EXTERNAL: Re: Dynamic Activation of New IODF z/OS is not on the same box, this particular z/10 only houses VM and TPF LPARs. We have CBDIODSP and HCM all set up and configured so the z/OS guys COULD use the VM-based HCM to build their files. I'm just still unclear how CP picks up the changes in the new IOCDS and makes them available dynamically on a running z/VM system. Apparently, on z/OS systems they "activate" a new IODF - but I don't see anything like that on z/VM except the SET IOCDS_Active command (which I don't believe, based on the documentation, will alter the running CP - please correct me if I'm mistaken). :) -Mike From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Marcy Cortes Sent: Tuesday, June 07, 2011 11:18 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Dynamic Activation of New IODF Is z/OS in another LPAR on the same box? If so, it's easiest just to let them do it and VM will just see the changes. Marcy From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Michael Coffin Sent: Tuesday, June 07, 2011 8:15 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] 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
