Allowing previously prevented DFSMShsm functions to run

You can use the RELEASE command to allow DFSMShsm to run functions that you previously prevented from running, and to allow activity logs to be closed and produced as output.

To allow all held DFSMShsm functions except logging to run, issue the following command. This command does not restart writing in the DFSMShsm log and does not cause the activity logs to be closed and processed.

Note: RELEASE ALL does not control the releasing of holds on the common recall queue. You must instead specify RELEASE COMMONQUEUE, with its optional subparameters.

RELEASE ALL

To allow the ABACKUP command to be processed, issue the following command. Any queued ABACKUP commands are allowed to process.

RELEASE ABACKUP

To allow the ARECOVER command to be processed, issue the following command. Any queued ARECOVER commands are allowed to process.

RELEASE ARECOVER

To allow the AUDIT command to be processed, issue the following command. Any queued AUDIT commands are allowed to process. Any AUDIT command that was interrupted by a HOLD command does not restart.

RELEASE AUDIT

To release all held backup functions, issue the following command. All backup processing is allowed to start. 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.

RELEASE BACKUP

To allow automatic backup processing that was prevented by a HOLD BACKUP(AUTO) command, issue the following command. This command does not release automatic backup processing if automatic backup is prevented by a HOLD BACKUP command that prevents any backup processing. If the time is still within the backup start window, automatic backup starts processing any functions that had not been processed when backup was held or interrupted. 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.

Note: 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 not scheduled to run if you have specified SETSYS AUTOBACKUPSTART(0) or if you have specified N for this day in the backup cycle.

RELEASE BACKUP(AUTO)

To allow processing of data set backups to both tape and ML1 DASD that were prevented by a HOLD BACKUP(DSCOMMAND) command, issue the following command.

Note: Use of the BACKUP(DSCOMMAND) parameter allows data set backup by command processing. This command will not affect automatic backup processing.

RELEASE BACKUP(DSCOMMAND)

To allow processing of data set backups that are directed to ML1 DASD that were prevented by a HOLD BACKUP(DSCOMMAND(DASD)) command, issue the following command:

RELEASE BACKUP(DSCOMMAND(DASD))

To allow processing of data set backups that were directed to tape that were prevented by a HOLD BACKUP(DSCOMMAND(TAPE)) command, issue the following command:

RELEASE BACKUP(DSCOMMAND(TAPE))

To allow processing of data set backups that were directed to DASD that were prevented by a HOLD BACKUP(AUTO DSCOMMAND(DASD)) command, issue the following command:

RELEASE BACKUP(AUTO DSCOMMAND(DASD))

To allow processing of data set backups that were directed to tape if they were prevented by a HOLD BACKUP(AUTO DSCOMMAND(TAPE)) command, issue the following command.

Note: If you release a particular category, you will release the hold on that category’s subcategory, as well. However, you cannot release a subcategory if the initial HOLD function occurred at a higher level. In contrast, you can release the higher level and then hold the complementary subcategory.

RELEASE BACKUP(AUTO DSCOMMAND(TAPE))

To release a common recall queue hold at the COMMONQUEUE level, holds at the RECALL level, and holds at the PLACEMENT and SELECTION level, issue the following command.

Note: When RELEASE COMMONQUEUE is issued, all unselected requests on the local queue move to the CRQ.

RELEASE COMMONQUEUE

If there is not a CRQ hold at the COMMONQUEUE level, to release a hold at the COMMONQUEUE(RECALL) level and a hold at the PLACEMENT and SELECTION level, issue the following command.

Note: When RELEASE COMMONQUEUE(RECALL) is issued, all unselected requests on the local queue move to the CRQ.

RELEASE COMMONQUEUE(RECALL)

To release a CRQ hold at the PLACEMENT level only if a hold is not at a higher level also, issue the following command.

Note: When RELEASE COMMONQUEUE(RECALL(PLACEMENT)) is issued, all unselected requests on the local queue move to the CRQ.

RELEASE COMMONQUEUE(RECALL(PLACEMENT))

To release a CRQ hold at the SELECTION level only if a hold is not at a higher level also, issue the following command:

RELEASE COMMONQUEUE(RECALL(SELECTION))

To allow dump processing to run, issue the following command. Any queued dump commands are allowed to process. If the time is still within the dump window, automatic dump starts processing any functions that had not been completed when the dump function was held.

RELEASE DUMP

To allow automatic dump processing to run if automatic dump was held by a HOLD DUMP(AUTO) command, issue the following command. If the time is still within the dump start window, automatic dump starts processing any functions that had not been completed when the dump function was held.

RELEASE DUMP(AUTO)

To allow expiration of backup versions if EXPIREBV was held by a HOLD EXPIREBV command, issue the following command. New EXPIREBV commands are processed. Any EXPIREBV processing that was interrupted by the HOLD EXPIREBV command is not restarted.

RELEASE EXPIREBV

To release the fast replication process by the FRBACKUP command, issue the following command.

RELEASE FRBACKUP

To release the fast replication process by the FRRECOV command, issue the following command.

RELEASE FRRECOV

To close the activity log data sets and process them, issue the following command. This command causes one of two actions.

If the activity logs are directed to a SYSOUT data set, the activity logs are closed and printed.
If the activity logs are directed to DASD data sets, the current DASD data sets are closed and new activity log data sets are allocated.

RELEASE HARDCOPY

To allow LIST command processing, issue the following command. Any queued LIST commands are allowed to process. Any list operation that was in process when list was held is not restarted.

RELEASE LIST

To allow entries to the DFSMShsm log after the entries have been prevented, issue the following command:

RELEASE LOG

To allow all migration processing, issue the following command. Any queued MIGRATION commands are allowed to begin processing. If the time is still within the automatic primary space management or automatic secondary space management processing windows, any automatic primary space management or automatic secondary space management functions that were not completed when migration was held begin processing.

RELEASE MIGRATION

To allow automatic primary space management or automatic secondary space management processing if they were prevented by a HOLD MIGRATION(AUTO) command, issue the following command. If the time is still within the automatic primary space management or automatic secondary space management processing windows, any automatic primary space management or automatic secondary space management functions that were not completed when automatic primary space management or automatic secondary space management was held are started.

RELEASE MIGRATION(AUTO)

When DFSMShsm is migrating data sets to both DASD and tape devices, an error condition can end migration to either of the device types without ending migration to the other. After the error is corrected, you can restart migration to the device that had the error by issuing one of the following commands:

RELEASE MIGRATION(AUTO)
RELEASE MIGRATION

To allow all recall processing, issue the following command. Any queued RECALL commands are allowed to process. In a common recall queue (CRQ) environment, RELEASE RECALL makes the host eligible to select requests from the CRQ.

RELEASE RECALL

To allow recall from tape data sets if recall was held by a HOLD RECALL(TAPE) command, issue the following command:

RELEASE RECALL(TAPE)

To allow recall from tape data sets that were requested by TSO users (if the recall was held by a HOLD RECALL(TAPE(TSO)) command, issue the following command:

RELEASE RECALL(TAPE(TSO))

To release the hold on recalls from DASD volumes, issue the following command:

RELEASE RECALL(DASD)

Note that there is no accompanying HOLD RECALL(DASD) command; instead, the RELEASE RECALL(DASD) command essentially converts a HOLD RECALL state to a HOLD RECALL(TAPE) state.

To allow all recover processing, issue the following command. Any queued RECOVER commands are allowed to process.

RELEASE RECOVER

To allow data sets to be recovered from tape volumes if recover processing was held by a HOLD RECOVER(TAPEDATASET) command, issue the following command:

RELEASE RECOVER(TAPEDATASET)

To allow recycle processing, issue the following command. Any queued recycle requests begin processing. Any volumes that were being recycled when recycle was held are not restarted.

RELEASE RECYCLE

To allow REPORT commands to be processed, issue the following command. Any queued report requests begin processing. Any report that was in process when reporting was held is not restarted.

Note: If DFSMShsm functions are being held because of a journal-inhibited condition and that condition cannot be resolved at that time, the following DFSMShsm commands can be issued to bypass journaling.

SETSYS NOJOURNAL
RELEASE XXX (for whatever function you want to release)
SETSYS JOURNAL (after a successful CONTROLDATASET BACKUP and the journal reset is completed)

RELEASE REPORT

Attention: If journaling is bypassed, you cannot perform a CONTROLDATASET RECOVERY for that period of time the journal was inhibited. The journal updates are lost for that period of time.