There is a tool around somewhere, called FTPB (FTP in Batch). It does this in batch, surrounded by an ISPF application which lets you selects datasets/groups and destinations. We adapted it to our needs and send everything forth and back over the big walls separating our sysplexes.
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of J O Skip Robinson Sent: 18 February, 2015 17:34 To: [email protected] Subject: Re: Parallel Sysplex split DSS/FTP is a perfectly respectable way to migrate an IODF around the enterprise. We happen to use the 'native' mechanism described in SAMPLIB member CBDSEXPU. This entails a batch job that sends the IODF from the source system to the target system. All you need is NJE. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Wednesday, February 18, 2015 8:00 AM To: [email protected] Subject: Re: Parallel Sysplex split Same here. No reason to share that stuff. Just use DFDSS, dump the IODF, FTP it to the other locations, and restore it. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of J O Skip Robinson Sent: Wednesday, February 18, 2015 10:58 AM To: [email protected] Subject: Re: Parallel Sysplex split Catalog is not an issue (except that IODF should be cataloged somewhere), but location is. The PDS containing LOADxx must be on the same volume as the IODF. Let's call that IPLPARM. Sharing IODF means also sharing IPLPARM. It does not get edited very often, but putting it outside of GRS introduces some risk. If IPLPARM gets damaged, you're pretty much SOL for every system that shares it. We have seven sysplexes. Almost nothing is shared across boundaries, including IODF and IPLPARM. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: Tuesday, February 17, 2015 11:03 PM To: [email protected] Subject: AW: Re: Parallel Sysplex split >That's not true in our case. We share the IODF between two sysplexes, it is >cataloged in a user catalog that is connected to the master catalogs of all >systems in both sysplexes. For the purpose of the IPL, the IODF does not need to be cataloged at all. You designate the IODF volume via its unit address in the LOADPARM (pos. 1-4). The DSN of the IODF to be used is then specified in the LOADxx member (suffix specified via LOADPARM, pos. 5-6). The LOADxx member is searched in SYSx.IPLPARM (x=0, 1, ..., 9) or SYS1.PARMLIB on the IODF volume and finally in SYS1.PARMLIB on the IPL volume. No catalog is involved in all of this. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
