Ah yes, I remember seeing that advice during our latest GDPS upgrade. Unless (again) I'm missing something, that statement in its short form is misleading. In practice, we mirror (XRC, not PPRC) from one data center to another. GDPS runs in the remote data center to 'pull' data from production. The GDPS 'K system' runs there but does not perform any IPLs except to bring up DR systems for the first time. That's not what AUTOIPL impacts anyway until after DR IPL, by which time GDPS is totally out of the picture.
I'm dimly aware that GDPS can be set up differently for other purposes. In our case, I cannot imagine how GDPS would even know about AUTOIPL, much less be inconvenienced by 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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Bruce Hewson Sent: Sunday, May 14, 2017 9:24 PM To: [email protected] Subject: (External):Re: AUTOIPL SADUMP LOADPARM flag value Hello Skip, GDPS-PPRC - doesn't like any IPL activity that is not performed via the GDPS panels. extract from:- https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieag300/wsat.htm Note: AutoIPL is not appropriate in a GDPS® environment. Regards Bruce ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
