We used to have z/VM-only boxes here. The z/OS people maintained the IOCP using HCD on z/OS. They exported the gens to the z/VM CEC's through the HMC. I don't know the details on how they did it. I know that they maintained our gen, and it did not involve them sending files or logging on to z/VM.
Dennis O'Brien "If man does find the solution for world peace it will be the most revolutionary reversal of his record we have ever known." -- General George C. Marshall From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Michael Coffin Sent: Tuesday, June 07, 2011 08:47 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] 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 ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.
