z/OS DFSMSdss Storage Administration
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Moving data sets with utilities

z/OS DFSMSdss Storage Administration
SC23-6868-01

In some cases, DFSMSdss invokes a utility to move a data set. Table 1 shows when DFSMSdss invokes a utility for a data set copy operation.

When you move a data set and a utility is used, the data set must be cataloged in the standard order of search.

DFSMSdss cannot use fast replication methods to move data if a utility must be used. When FASTREPLICATION(REQUIRED) is specified in such a case, DFSMSdss will not use traditional I/O movement methods and therefore will not call the utility.

When DFSMSdss invokes IEBCOPY to copy a LOADMOD, message IEC507D is issued requesting operator authorization to overwrite an unexpired area when the source data set has an incorrect RLD count and an unexpired date.

When DFSMSdss invokes IEHMOVE to copy data sets, IEHMOVE has DD statement requirements that DFSMSdss cannot always satisfy. To avoid potential abnormal ends, do one or both of the following:
  • Specify the source and target volumes as PRIVATE.
  • Ensure that the source and target volumes are not in the list of default volumes for dynamic allocation.

When DFSMSdss invokes IDCAMS to copy a KSDS, the data set is automatically reorganized to optimize it for VSAM processing. A large KSDS may require extensive reorganization that could result in greater processing time for the copy operation. If IDCAMS was selected because multiple output volumes were specified, performance may be improved by specifying a single output volume for the data set.

Table 1. Data Mover Selection Matrix for Data Set Copy
Data Set Type Like Devices Unlike Devices
Sequential DFSMSdss DFSMSdss
Partitioned (not PDSE) DFSMSdss (1, 2) DFSMSdss (1, 2)
Partitioned (not PDSE) load modules DFSMSdss (3) IEBCOPY
Partitioned data set extended (PDSE) DFSMSdss (4) DFSMSdss (4)
Direct nonrelative block address mode DFSMSdss DFSMSdss (5)
Direct relative block address mode (6) DFSMSdss DFSMSdss
ESDS DFSMSdss (7) DFSMSdss (7, 8)
RRDS DFSMSdss (7) IDCAMS (REPRO)
LDS DFSMSdss (7) IDCAMS (REPRO)
KSDS or VRRDS DFSMSdss (9) IDCAMS (REPRO)
Key range data set DFSMSdss (10) IDCAMS (REPRO)
Extended-format VSAM DFSMSdss (7) IDCAMS (REPRO)
Integrated catalog facility user catalogs IDCAMS (EXPORT/IMPORT) IDCAMS (EXPORT/IMPORT)
Undefined DSORG DFSMSdss DFSMSdss
Note:
  1. All partitioned data sets that are not load modules are compressed during a copy to a like or unlike device.
  2. DFSMSdss calls the IGWFAMS utility when you are converting a PDS to a PDSE.
  3. If copying partitioned load modules with REBLOCK, DFSMSdss calls IEBCOPY to copy the data set to a like device.
  4. DFSMSdss calls the IGWFAMS utility when you are converting a PDSE to a PDS. DFSMSdss also calls IGWFAMS when all of the following conditions are met:
    • Fast replication methods cannot be used and FASTREPLICATION(REQUIRED) is not specified.
    • Concurrent copy cannot be used.
  5. The source data set is not copied if the target data set is preallocated or if the target device has a smaller track capacity than the source.
  6. Specify the DFSMSdss RELBLOCKADDRESS parameter.
  7. DFSMSdss calls IDCAMS if the target CISIZE, CASIZE, physical record size, or physical block size of the target is different from that of the source.
  8. DFSMSdss calls IDCAMS if the calculated number of blocks per control area is different from the calculated number of usable blocks per control area.
  9. DFSMSdss calls IDCAMS if any of the following is true:
    • The CISIZE, CASIZE, physical record size, physical block size, imbed, or span attributes of the target are different from that of the source.
    • The target data set is SMS and has an imbedded index or has key ranges, and the target volume count is greater than one. For help in determining the volume count, VOLCOUNT.
    • The target data set is non-SMS, the source component or components span multiple volumes, and there is not enough space on one target volume to contain the entire data set.
  10. DFSMSdss calls IDCAMS if the source and target CASIZE, physical record size, or physical block size are different; if the components span multiple volumes; for a KSDS with IMBED and either the source HURBA=HARBA or it has extended indexes.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014