I use the same LOAD member in SYS1.IPLPARM and use LPARNAME to set the correct parameters ,
I use the IEASYM member to do the rest - just a snip of what I have, there's more to it but it works well all I do is shutdown and deactivate the LPAR's on one CEC and ACTIVATE and IPL the DR images on the other CEC only difference is the UCB's they are replicated using hyperswap + PPRC volumes so my IPL profile is 3xxx not 2xxx for the sysres and iodf volume LOADxx IEASYM (00,L) NUCLEUS 1 NUCLST 00 INITSQA 0020K 0001M SYSPLEX PLEX1 * prod --- LPARNAME APROD1 PARMLIB SYS1.user.PARMLIB IODF ** HCD SYSA00 FOR DR LPARNAME KPROD1 IODF ** HCD SYSK00 PARMLIB SYS1.user.PARMLIB HWNAME to decide what parms to use. IEASYMxx SYSDEF HWNAME(CWY1) LPARNAME(APROD1) set the normal prod parms SYSDEF HWNAME(Z13K) LPARNAME(KPROD1) set the DR parms and options Carmen Vitullo ----- Original Message ----- From: "Gilson Cesar de Oliveira" <[email protected]> To: [email protected] Sent: Thursday, May 21, 2020 3:59:28 AM Subject: How to configure LOADxx in DR Hello: We have the following situation when trying to activate and IPL 3 lpars from site A into site B. Both sites are distant about 450 Km and the storage replication is made by Global Metro Mirror. The issue we have faced last weekend is related to match the IODF we have received from the team which is responsible for the box in site B. We have the SYS1.IODFE0 with all the definitions for the box in site B where they have more lpars than just our 3 defined there. In site A where my team is responsible for the SYS1.IODFxx we have pointed in LOADxx with **. When trying to IPL the same lpars in site B we are configuring in LOADyy with IODF = E0. There was something wrong with this configuration because in the VOLUME where the SYS1.IODFE0 is located, it didn't match with the configuration in HSA. Perhaps someone from the site B have validated new IODF for other lpars than the 3 we have defined and the IPL didn't came up returning an error which wait state code is 0F indicating a mismatch in the volume or with the dataset (it looks like it didn't found the dataset or the configuration). Does anyone here could give us tips on how to have the configuration working for both sites without worrying about changes in terms of IO configuration not related to our lpars ?? Thanks in advance for any help. Regards, Gilson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
