Re: The best practice of IODF in big system
We have three CECs residing in two data centers. Counting both production and DR LPARs, we have upwards of two dozen altogether. All disk and tape are cross connected locally or via DWDM, so that every LPAR is connectable to every device. The whole enterprise is mapped by a single IODF where geographic boundaries are entirely invisible. We know where such and such CEC or DASD device is located, but IOS has no idea. Every LPAR must have a copy of the current IODF in order for this to work. For redundancy and backup, we supply all sysplexes (some mono) with a shared copy of SYS1.IODFxx. The IODF is created and maintained on one sysplex and propagated to every other sysplex using the standard HCD utility CBDMGHCP. LOADxx in IPLPARM is set to '--' for IODF number, so once a new IODF is activated dynamically or via POR, it will be found on the next IPL without any sysprog intervention. The IOCDS in each CEC is updated from 'system zero' via HCD Option 2.11 ' Build and manage System z cluster IOCDSs, IPL attributes and dynamic I/O changes'. In previous discussions on IBM-Main, others have indicated different strategies for accomplishing the same goal. There is not one right way to do this, but of course there is one best way. This is it. ;-) . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mohamed Juma Sent: Sunday, January 15, 2017 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: The best practice of IODF in big system Dear Alan, PROD CEC 1: Two LPARs one Z/OS, and one ICF. PROD CEC 2 : Two LPARs Z/OS CF CEC any z/OS lpars? No TEST CEC: Three LPARs, one ICF, two Z/OS DR CEC how many lpars? Two ICF one TEST, one PROD- Three Z/OS one TEST and two PROD. Do the lpars share DASD? Yes all of them sharing two DASD in both HO and DR. Are the lpars in a SYSPLEX? two SYSPLEX one for TEST includes all TEST LPARS in both Sites. One SYSPLEX for all PROD LPARs in the two sites. How do you update the DR DASD? via PPRC Do you have real time replication? Yes Thanks Mohamed Gomaa From: "Field, Alan" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Sunday, January 15, 2017 1:18 PM Subject: Re: The best practice of IODF in big system Mohamed, more questions: PROD CEC 1 how many lpars PROD CEC 2 how many lpars CF CEC any z/OS lpars? TEST CEC how many lpars DR CEC how many lpars? Do the lpars share DASD? Are the lpars in a SYSPLEX? How do you update the DR DASD? Do you have real time replication? Alan -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mohamed Juma Sent: Sunday, January 15, 2017 4:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: The best practice of IODF in big system Hi, We have 3 CECs in PROD System (two Z/OS and one External CF), one TEST and one more CEC in DR site, I combined them in one IODF.I want to know the best practice to copy the IODF to each CEC, and also the IOCDs without suffering from H/W and S/W mismatch. Mohamed Gomaa -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The best practice of IODF in big system
In our environment we have four CECs. 1 - CF only 3 - running z/OS & z/VM - three different sysplexs We have one parallel sysplex that crosses all three CECs, the other two base sysplex each one a different CEC. We have several DASD volumes that are setup for limited sharing across all three sysplexs. I say limited because we can’t share the GRS environment across the different sysplex. We do device reserves for a limited enqueue setup. With all that said I will use DFDSS to copy the IODF to the shared DASD and then do a DFDSS restore on the other systems. We use the same IODF name across all the lpars. We do data replication to our DR environment so the new IODF gets to DR by default. Before the shared DASD setup I would have FTP the DFDSS copied file to the other lpars and then do the restore. I don't know if this qualifies as best practice, but this is how I move the IODF around. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mohamed Juma Sent: Sunday, January 15, 2017 05:36 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: The best practice of IODF in big system Dear Alan, PROD CEC 1: Two LPARs one Z/OS, and one ICF. PROD CEC 2 : Two LPARs Z/OS CF CEC any z/OS lpars? No TEST CEC: Three LPARs, one ICF, two Z/OS DR CEC how many lpars? Two ICF one TEST, one PROD- Three Z/OS one TEST and two PROD. Do the lpars share DASD? Yes all of them sharing two DASD in both HO and DR. Are the lpars in a SYSPLEX? two SYSPLEX one for TEST includes all TEST LPARS in both Sites. One SYSPLEX for all PROD LPARs in the two sites. How do you update the DR DASD? via PPRC Do you have real time replication? Yes Thanks Mohamed Gomaa From: "Field, Alan" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Sunday, January 15, 2017 1:18 PM Subject: Re: The best practice of IODF in big system Mohamed, more questions: PROD CEC 1 how many lpars PROD CEC 2 how many lpars CF CEC any z/OS lpars? TEST CEC how many lpars DR CEC how many lpars? Do the lpars share DASD? Are the lpars in a SYSPLEX? How do you update the DR DASD? Do you have real time replication? Alan -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mohamed Juma Sent: Sunday, January 15, 2017 4:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: The best practice of IODF in big system Hi, We have 3 CECs in PROD System (two Z/OS and one External CF), one TEST and one more CEC in DR site, I combined them in one IODF.I want to know the best practice to copy the IODF to each CEC, and also the IOCDs without suffering from H/W and S/W mismatch. Mohamed Gomaa -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you must not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The best practice of IODF in big system
Dear Alan, PROD CEC 1: Two LPARs one Z/OS, and one ICF. PROD CEC 2 : Two LPARs Z/OS CF CEC any z/OS lpars? No TEST CEC: Three LPARs, one ICF, two Z/OS DR CEC how many lpars? Two ICF one TEST, one PROD- Three Z/OS one TEST and two PROD. Do the lpars share DASD? Yes all of them sharing two DASD in both HO and DR. Are the lpars in a SYSPLEX? two SYSPLEX one for TEST includes all TEST LPARS in both Sites. One SYSPLEX for all PROD LPARs in the two sites. How do you update the DR DASD? via PPRC Do you have real time replication? Yes Thanks Mohamed Gomaa From: "Field, Alan" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Sunday, January 15, 2017 1:18 PM Subject: Re: The best practice of IODF in big system Mohamed, more questions: PROD CEC 1 how many lpars PROD CEC 2 how many lpars CF CEC any z/OS lpars? TEST CEC how many lpars DR CEC how many lpars? Do the lpars share DASD? Are the lpars in a SYSPLEX? How do you update the DR DASD? Do you have real time replication? Alan -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mohamed Juma Sent: Sunday, January 15, 2017 4:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: The best practice of IODF in big system Hi, We have 3 CECs in PROD System (two Z/OS and one External CF), one TEST and one more CEC in DR site, I combined them in one IODF.I want to know the best practice to copy the IODF to each CEC, and also the IOCDs without suffering from H/W and S/W mismatch. Mohamed Gomaa -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you must not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The best practice of IODF in big system
Mohamed, more questions: PROD CEC 1 how many lpars PROD CEC 2 how many lpars CF CEC any z/OS lpars? TEST CEC how many lpars DR CEC how many lpars? Do the lpars share DASD? Are the lpars in a SYSPLEX? How do you update the DR DASD? Do you have real time replication? Alan -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mohamed Juma Sent: Sunday, January 15, 2017 4:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: The best practice of IODF in big system Hi, We have 3 CECs in PROD System (two Z/OS and one External CF), one TEST and one more CEC in DR site, I combined them in one IODF.I want to know the best practice to copy the IODF to each CEC, and also the IOCDs without suffering from H/W and S/W mismatch. Mohamed Gomaa -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you must not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The best practice of IODF in big system
By the way, we are running two different sysplex, one for PROD and one for TEST. Each Sysplex has members in the main data Centre and also DR site including Control systems for GDPS and System automation. Mohamed Gomaa From: Mohamed Juma <00cefc9a9b79-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Sunday, January 15, 2017 12:31 PM Subject: The best practice of IODF in big system Hi, We have 3 CECs in PROD System (two Z/OS and one External CF), one TEST and one more CEC in DR site, I combined them in one IODF.I want to know the best practice to copy the IODF to each CEC, and also the IOCDs without suffering from H/W and S/W mismatch. Mohamed Gomaa -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
