ABCs of z/OS System Programming Volume 3 - IBM Redbooks

4.26 PDSE: Conversion
Using DFSMSdss
COPY DATASET(INCLUDE -
(MYTEST.**) -
BY(DSORG = PDS)) -
INDY(SMS001) -
OUTDY(SMS002) -
CONVERT(PDSE(**))-
RENAMEU(MYTEST2) -
DELETE
Figure 4-36 Converting PDS to PDSE
Converting a PDS data set to a PDSE
You can use IEBCOPY or DFSMSdss COPY to convert PDS to PDSE, as shown in Figure 4-36.
We recommend using DFSMSdss.
You can convert the entire data set or individual members, and also back up and restore
PDSEs. By using the DFSMSdss COPY function with the CONVERT and PDS keywords, you
can convert a PDSE back to a PDS. This is especially useful if you need to prepare a PDSE
for migration to a site that does not support PDSEs. When copying members from a PDS load
module library into a PDSE program library, or vice versa, the system invokes the program
management binder component.
Many types of libraries are candidates for conversion to PDSE, including:
► PDSs that are updated often, and that require frequent and regular reorganization
► Large PDSs that require specific device types because of the size of allocation
Converting PDSs to PDSEs is beneficial, but be aware that certain data sets are unsuitable
for conversion to, or allocation as, PDSEs because the system does not retain the original
block boundaries.
Using DFSMSdss
In Figure 4-36, the DFSMSdss COPY example converts all PDSs with the high-level qualifier
of “MYTEST” on volume SMS001 to PDSEs with the high-level qualifier of “MYTEST2” on
150 ABCs of z/OS System Programming Volume 3
Using IEBCOPY
//INPDS DD DISP=SHR,
DSN=USER.PDS.LIBRARY
//PDSE DD DSN=USER.PDSE.LIBRARY,
DISP=OLD
//SYSIN DD *
COPY OUTDD=OUTPDSE
INDD=INPDS
SELECT MEMBER=(A,B,C)