On Fri, 2008-05-30 at 15:50 -0500, Johnston, Robert E wrote: > > So, from the same work IODF, I created a prod SYS1.IODF05 and a prod > SYS0.IODF05 and wrote them to 2 different IOCDS's in the z9. I did a > hardware > and software activate on Prod using SYS1.IODF05. Activate was > successful and > HCD says I can still make h/w and s/w changes. > > Next I IPLed Test using the shared SYS0.IODF05. I expected to only be > able to > make s/w changes but HCD now says I can make h/w and s/w changes. (If > I did > make any changes from Test I don't think I could activate them on > Prod.) > > To straighten things out, I'm going to need to POR with the IOCDS created > from SYS0 and IPL both Prod and Test with SYS0. Right?
To keep in sync you only need to maintain the TOKEN in the IODF file with the IOCDS. THe **NAME** of the IODF file itself does not matter. We run multiple Sysplexes on a single CEC and use common IODF files, but a seperate physical copy for each one. The procedure is: 1) Create Production IODF (doesn't matter which system builds it) 2) Export IODF file using the unattended method (6.5 from primary hcd menu) to each sysplex (each one has their own HLQ and IODF pack) 3) Write IOCDS to appropriate IOCDS slot 4) Dynamically activate new IODF as required. So you can continue to use whatever HLQ the TEST system is IPL'd on and get back in sync as you have found. If you want to change to use the other HLQ you only need to create the IODF that matches, update LOADxx and IPL the system that is out of sync. There is no relationship on the HLQ between different systems and/or the IOCDS -- Jerry Whitteridge <[EMAIL PROTECTED]> Safeway Inc. "Email Firewall" made the following annotations. ------------------------------------------------------------------------------ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ============================================================================== ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
