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


DELETE

z/OS DFSMSdss Storage Administration
SC23-6868-01

Read syntax diagramSkip visual syntax diagram
>>-+--------+--------------------------------------------------><
   '-DELete-'   

DELETE specifies that for a data set copy DFSMSdss deletes VSAM and non-VSAM data sets from the source volume after a successful copy. This moves, in effect, a data set from one volume to another. The data sets are scratched and uncataloged.
Note:
  1. Specify DELETE when you are copying cataloged data sets. If you do not specify DELETE when you are copying cataloged data sets, the target data set must either be cataloged in a different catalog (using the RECATALOG keyword) or renamed (using the RENAMEU keyword).
  2. If you copy a data set with DFM attributes to a non-SMS-managed target, the new data set will not have the DFM attributes.
  3. Unexpired source data sets are deleted only if you also specify PURGE.
  4. Even if PROCESS (SYS1) is specified, SYS1.VVDS and SYS1.VTOCIX data sets cannot be copied and deleted.
  5. Do not specify SHARE if you specify DELETE.
  6. If DFSMSdss encounters a damaged PDS during logical data set copy, it displays messages indicating the nature and relative location of the problem. In order to maintain complete data integrity, DFSMSdss does not delete the source data set. The copy of the data set fails, and the target is deleted. In order to copy and delete a damaged PDS, use the NOPACKING keyword.
  7. Do not specify DELETE with CONCURRENT, because after the concurrent copy operation has begun, the original data can still be updated.
  8. Do not specify DELETE with CICSVRBACKUP.
  9. Specify DELETE to preserve aliases that are associated with non-VSAM data sets. The following criteria must be met for this to work:
    • RENAMEU cannot be specified at the same time.
    • The data set must be SMS-managed and remain SMS-managed during the copy operation.
  10. For physical data set copy processing, only a single-volume non-VSAM data set may be deleted from a volume that is not a dump conditioned volume. If the DELETE keyword is specified and the input volume specified on the PHYSINDD keyword is a dump conditioned volume, then the DELETE keyword will be ignored while processing all data sets from that volume. If the DELETE keyword is specified and the target data set is single volume and the target volume is SMS managed and the target is not preallocated, the target data set will be cataloged.
  11. If the data set being processed is a generation data set (GDS), an exclusive enqueue on the GDG BASE is required in addition to the exclusive enqueue on the GDS.

For more information about copying non-VSAM data sets that have aliases, see Moving data sets with special requirements.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014