You can use the DFSMShsm HOLD command to prevent all dump processing or to prevent only automatic dump processing.
HOLD DUMPHOLD DUMP(AUTO)HOLD DUMP(FRBACKUP)You can specify whether you want the holding action to occur immediately at the end of processing each data set currently being dumped or to occur at the end of each volume being dumped. If you hold dump at end of volume, it can take a long time for all of the volumes that are being processed by the different dump tasks to be completed and the hold to take full effect. If you hold dump at the end of data sets, DFSMShsm resumes command dump with the next queued entry when the hold is released. However, for automatic dump, the volume that was being processed when the HOLD at end of data set occurred remains eligible for processing if automatic dump is restarted.
The holding action begins when an MWE is selected for processing, not when the HOLD command is entered. If you use an HSENDCMD command to enter a wait-type dump request and the dump function is held, DFSMShsm fails the wait-type dump request because the hold dump function gives no indication of when the dump function is available.
When a non-wait-type dump request is issued and the dump function is held, the request remains on the queue and is processed when the dump function is released. The held dump function is released with the RELEASE DUMP command.
For more information about other ways to prevent DFSMShsm from processing a dump function, see Preventing the processing of data sets during space management.