You can use the HOLD BACKUP command to prevent all backup processing,
prevent only automatic backup processing, or prevent fast replication
backup processing. If you do not want any backup processing at all
(for volume, data sets, and auto backups), issue the HOLD BACKUP command
by itself. You can specify the AUTO subparameter to prevent only automatic
backups from running. You can specify the DSCOMMAND subparameter to
prevents only data set backups from running.
Note: - The DSCOMMAND option applies to the BACKDS, HBACKDS, ARCHBACK,
and ARCINBAK data set backup requests and to backups that are performed
as INUSE RETRY from automatic backup.
- The HOLD ALL command prevents all DFSMShsm functions (except logging)
from running.
- If you are using SETSYS BACKUP parameters or a data set backup
installation exit (ARCBDEXT) to direct DFSMShsm to retry backup requests
that fail because data sets are in use (see Specifying how DFSMShsm should respond to a data set in use),
and if DFSMShsm has scheduled any such retries during automatic backup,
those backup retries will not be affected by the HOLD BACKUP(AUTO)
command. You will need to use HOLD BACKUP(DSCOMMAND).
The following command prevents processing of all data set backups
(BACKDS, HBACKDS, ARCHBACK, and ARCINBAK), and it prevents the processing
of all backups that would be the result of INUSE RETRY from automatic
backup. All WAIT requests fail, and control returns to the requester.
HOLD BACKUP(DSCOMMAND)
The following command prevents processing of data set backups that
are directed to ML1 DASD. All WAIT requests that target DASD fail,
and control returns to the requester.
HOLD BACKUP(DSCOMMAND(DASD))
The following command prevents processing of data set backups that
are directed to tape. All WAIT requests that target tape and all WAIT
requests for large data sets that do not specify a target fail. Control
returns to the requester.
HOLD BACKUP(DSCOMMAND(TAPE))
The following command prevents processing of automatic backups,
data set backups that are directed to tape, and all WAIT requests
for large data sets that do not specify a target. However, data set
backups to ML1 DASD are not affected.
HOLD BACKUP(AUTO DSCOMMAND(TAPE))
The following command prevents processing of automatic backups
and data set backups that are directed to ML1 DASD. Data set backups
to tape are not affected.
HOLD BACKUP(AUTO DSCOMMAND(DASD))
During automatic or volume backup, you can specify whether the
holding action occurs immediately at the end of processing each data
set or at the end of processing each volume currently being backed
up. If you hold backup at end of volume, it can take some time for
all of the volumes that are being processed by the different backup
tasks to complete and the hold to take full effect. If you hold backup
at the end of data sets, DFSMShsm resumes data set backup with the
next queued entry when the hold is released. However, for automatic
backup, the volume interrupted by the HOLD at end of data set remains
eligible for processing if automatic backup is restarted.
The holding action begins when an MWE is selected for processing,
not when the HOLD command is entered. If you enter a wait-type backup
request and the backup function is held, DFSMShsm fails the wait-type
backup request because the hold backup function gives no indication
when the backup function will be available.
When a non-wait-type backup request is issued and the appropriate
backup function is held, the request remains on the queue and is processed
when the appropriate backup request function is released. The held
backup processing function can be released with the RELEASE BACKUP
command.