In this topic, we described about the Loading/Copying from Unload Data Sets with detailed example.
IEBCOPY can be used to re-create a PDS from an unloaded copy of a PDS by copying the sequential (unloaded) data set to a PDS. A PDScan be loaded from an unloaded PDSE if it does not contain program objects.
PDSE may be loaded from an unloaded PDS if it does not contain load modules. A single PDS can be created from multiple input sequential (unloaded) data sets.
A PDS in the unload format will have a variable spanned record format. For unload and load operations, requests are handled in the same way as a copy operation.
A sequential data set that was created by an IEBCOPY unload operation is loaded.
//LOAD JOB ... //STEPA EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=A //SYSUT1 DD DSNAME=UNLOADSET,UNIT=tape,LABEL=(,SL), // VOL=SER=TAPE01,DISP=OLD //SYSUT2 DD DSNAME=DATASET4,UNIT=disk,VOL=SER=2222222, // DISP=(NEW,KEEP),SPACE=(CYL,(10,5,10)) //SYSIN DD DUMMY /*
Let’s discuss the example in detail.
- SYSUT1 DD defines a sequential data set that was previously created by an IEBCOPY unload operation. The data set contains 30 members.
- SYSUT2 DD defines a new PDS on a disk volume. This data set is to be kept after the load operation.
- SYSIN DD defines the control data set and is dummied.