The HOLD command prevents all or some DFSMShsm functions from running. For example, you specify HOLD when a temporary software or hardware problem occurs that can be compounded if data movement continues in DFSMShsm.
Migration, backup, dump, recovery, and restore have an optional keyword related to stopping volume processing after the current data set (EOD) or delaying until the end of processing the user volume (EOV).
The WAIT and NOWAIT parameters of the HSENDCMD command have implications to HOLD command processing that are function specific. Refer to the specific processing function for an explanation.
All nonWAIT-type requests remain on the processing queue when the appropriate HOLD command is in effect.
If the HOLD command is issued while the TAPECOPY or TAPEREPL commands are processing more than one volume, either from a volume list from the command or from an input data set, processing stops after the current volume.
You can issue the RELEASE command to release for processing all or some of the DFSMShsm functions held with the HOLD command.
Functions held from processing by the HOLD command are no longer prevented from processing if DFSMShsm is reinitialized.