DUMP command for DFSMSdss

With the DUMP command, you can dump DASD data to a sequential data set, which can be a generation in a generation data group (GDG), or as objects in an object storage cloud. The storage medium for the sequential data set can be tape or DASD. When the output resides on DASD, it may be a basic, large or extended format sequential data set. When the output resides in cloud storage, data is stored as a set of objects.

Restriction: When using the DUMP command to create a backup in an object storage cloud, DFSMSdss only supports logical and full volume processing.

The FULL keyword for the DUMP command specifies that an entire DASD volume is to be dumped. The TRACKS keyword with the DUMP command specifies ranges of tracks to be dumped.

SHARE
Do not use the SHARE keyword during a physical dump of HFS or zFS data sets.

For an HFS data set, DFSMSdss obtains both an ADRDSN enqueue and a SYSZDSN enqueue. SHARE determines only whether the ADRDSN enqueue is shared or exclusive.

For a zFS data set, DFSMSdss obtains an ADRDSN enqueue, a SYSDSN enqueue, and a number of SYSVSAM enqueues. SHARE determines only whether the ADRDSN enqueue is shared or exclusive. When specifying DELETE, DFSMSdss attempts to obtain exclusive SYSDSN and SYSVSAM enqueues. If you do not specify DELETE, DFSMSdss attempts to obtain shared SYSDSN and SYSVSAM enqueues.

TOLERATE
ENQFailure specifies that data sets are to be processed even though shared or exclusive access fails. TOL(ENQF) and FULL or TRACKS are mutually exclusive; you cannot specify these keywords together.

Unlike PDS data sets, PDSE data sets that are open for update cannot be dumped even if TOL(ENQF) is specified.

If you must dump a PDSE data set and it must be open for update, process the data set with concurrent copy (specify CONCURRENT). If you cannot use concurrent copy, convert the PDSE back to PDS and then dump the PDS data set with TOL(ENQF).

TOL(ENQF) is not honored when processing a logical dump of HFS or zFS data sets.

Exercise caution if you use TOL(ENQF) during a physical dump of HFS data sets. Unlike other types of data sets, if an HFS data set is updated during a physical dump with TOL(ENQF), a subsequent restore can likely result in an unusable data set.

DFSMSdss offers several ways to process DUMP commands:
  • Logical processing is data set-oriented, which means it operates against data sets independently of physical device format.
  • Physical processing can operate against data sets, volumes, and tracks, but is oriented toward moving data at the track-image level.
  • File processing is z/OS UNIX-oriented and can process individual UNIX files that are specified as absolute paths.

    The processing method is determined by the keywords specified on the command.

DFSMSdss logical dump processing cannot be used to process partitioned data sets containing location-dependent information that does not reside in note lists or in the directory. Furthermore, DFSMSdss cannot be used to dump migrated data sets.

DFSMSdss file processing can only be performed on files that are known to z/OS UNIX and that reside within a zFS physical file system.

Integrated catalog facility catalogs should not have a high-level qualifier of SYSCTLG because this causes DFSMSdss to treat them as a control volume (CVOL).

For more information about options and keywords