EMERGENCY and NOEMERGENCY: Specifying no data set movement

Explanation: EMERGENCY | NOEMERGENCY are mutually exclusive, optional parameters specifying whether emergency mode is in effect. Emergency mode stops all DFSMShsm automatic and command data set processing in both SMS and non-SMS environments and in both primary and secondary address spaces, including functions like aggregate backup, aggregate recovery, audit, migration, backup, recall, recovery and recycle.

EMERGENCY specifies that emergency mode is in effect, and no new DFSMShsm data set processing can be performed. DFSMShsm allows any operation in process to finish the currently selected data set and it allows any currently running ABACKUP and ARECOVER commands to continue until completion. However, DFSMShsm also allows commands that correct or set up options to run. For example, you can issue FIXCDS, QUERY, or SETSYS commands while running in EMERGENCY mode.

NOEMERGENCY specifies that emergency mode is not in effect.

Note:

If DFSMShsm does not resume processing for all functions after you specify SETSYS EMERGENCY and then SETSYS NOEMERGENCY, you may need to issue a RELEASE command, assuming a HOLD command was issued previously.
You can start DFSMShsm in emergency mode by specifying EMERG=YES on the START command.
Emergency mode does not prevent a host from placing recall requests in the common recall queue (CRQ), where those requests are then processed by other active hosts. To prevent a host from placing requests in the CRQ, specify HOLD COMMONQUEUE(RECALL(PLACEMENT)).
A SETSYS xxEMERENCY command in the ARCCMDxx startup member would override any EMERG=xxx parameter.

SMS relationship: Parameter differs in meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets.

SETSYS default: None.

DFSMShsm default: If you do not specify either parameter on any SETSYS command, the DFSMShsm default is NOEMERGENCY.