I don't know if anyone has pointed it out, but if this is a brand new, vanilla CEC, before you even have to worry about an IODF, you need an IOCDS. Generally you create that deck from an IODF, and I can't imagine you would choose not to. All of our CECs are defined in one IODF. For a new machine across the state, we sent the IOCDS deck for the target CEC (and common ICC configs) to the CE, and he put them on a thumb drive; we then ran stand-alone IOCP to load the HSA. Then with any (I would hope) form of replication you use, the IODF needed for all the recovery LPARs is "just already there" on your recovery SYS1.IPLPARM/IODF volume.
Our DASD CUs and device addresses are different (I'm thinking they had to be for either flavor of replication), but we don't have that many, so we don't have to worry about running out. Our LPAR numbers are the same on all CECs, and our OS configs are defined only once and are used on all respective LPARs. There's nothing to it, and I don't know of a single reason not to have one common IODF. First Horizon Bank Mainframe Technical Support Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
