BACKUP: Releasing backup

Explanation

BACKUP is an optional parameter specifying whether DFSMShsm should release all backup processing or release only:

BACKUP by itself specifies that DFSMShsm releases all backup processing. The parameters of the BACKUP parameter are explained:

AUTO

Releases automatic backup processing only.

DSCOMMAND

Releases data set backups for both tape and ML1 DASD requests.

None.

Usage notes:

You cannot release a subfunction if the initial HOLD was done at a higher level. For example, you cannot release the subfunction BACKUP(AUTO) if the main function BACKUP is held.
For another example: If you issue HOLD BACKUP(DSCOMMAND(TAPE), DFSMShsm holds only the data set backup by command to tape subfunction. Then, if you issue RELEASE BACKUP(DSCOMMAND), DFSMShsm releases data set backup by command to tape because TAPE is a subfunction of DSCOMMAND. However, if you issue HOLD BACKUP, DFSMShsm holds all backup processing. Then, if you issue RELEASE BACKUP(DSCOMMAND(TAPE)), DFSMShsm still holds data set backup by command to tape because all backup to tape was held at the BACKUP level.
Releasing a particular function releases the hold on that function's subfunctions, as well.
If the time is still within the backup start window, automatic backup starts processing any functions that have not already been processed. Any volumes that were not already fully processed are candidates for processing if less than 24 hours has passed since automatic backup was last started from the beginning and if the time is still within the backup window.
If automatic backup is not scheduled to run on a particular day, you can use the BACKUP parameter of the RELEASE command to move backup versions (and backup migrated data sets). Automatic backup is scheduled not to run if you specified SETSYS AUTOBACKUPSTART(0) or specified N for this day in the backup cycle.