I use SymbolicRelate to overcome (some) naming collisions:
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE ALIAS -
(NAME('SYS3.SA.ACF') -
SYM('SYS3.SA.&GDPSTYPE..ACF'))
"&GDPSTYPE" resolves to either "KSYS" or "PROD". The same JCL on KSYS or
PROD systems can reference "SYS3.SA.ACF", but actually use unique datasets
for the system type. We'll be setting up our 4th GDPS Sysplex over the next
couple months, and this approach has worked well.
In the case of datasets that do share the same name but reside on different
volumes, I'll use a TSO TRANSMIT dataset as an interim "container".
TRANSMIT PDS members into a "temp" (cataloged) XMIT dataset, FTP that
dataset to KSYS, RECEIVE into same named PDS on KSYS. The JCL that performs
the RECEIVE on KSYS does the housekeeping of deleting the "temp" XMIT
dataset afterwards.
On Wed, Nov 19, 2014 at 12:25 PM, Mark Regan <
[email protected]> wrote:
> Duh, just realized that I was actually FTPing between two LPARS within the
> same plex. So of course you can not use the same DSN name for the source
> and destination. Now between PDS libs of the same name you can as long as
> the member names are different.
> Since this new LPAR is a KLPAR, we don't share its volumes with the other
> LPARs in the same plex. But since the data set names are the same, just on
> different volume names, that does get noticed at the plex level. Thanks,
>
> Mark Regan, USNR-Ret, 1969-1991
>
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
