Stopping DFSMShsm

You can also issue the MVS™ STOP DFSMSHSM command. When DFSMShsm is stopped, the normal job-log information is spooled to the printer along with the DFSMShsm log and activity logs that DFSMShsm maintains. Either one of the STOP commands causes an orderly shutdown of the DFSMShsm address space and an orderly closing of the DFSMShsm control data sets.

F DFSMSHSM,STOP PROMOTE makes the host eligible to have its unique functions taken over by a promotable host. You can issue a STOP PROMOTE command on a primary host, or a host that runs secondary space management, in sysplex environment with secondary host promotion enabled. This causes an orderly shutdown, and allows another host to take over the unique functions of the stopped primary host, or the secondary space management functions of the stopped host running secondary space management.

F DFSMSHSM,STOP DUMP issues a dump and makes the host eligible to have its unique functions taken over by a promotable host.

In a sysplex, a manual shutdown of the primary or secondary space management host, without using the PROMOTE or DUMP parameters, does not automatically cause promotion of another host, because it is assumed that there is a reason for the shutdown, such as for routine maintenance or because all systems in the sysplex are being shut down.

An orderly shutdown means that each attached subtask ends and all DFSMShsm secondary address spaces must complete processing. Because many DFSMShsm commands and automatic functions are potentially long-running, DFSMShsm periodically checks whether shutdown has been requested, to prevent a delay in the shutdown process. If DEFERMOUNT is used, or the correct tape was not mounted during end volume processing, and the timer was set by the MOUNTWAITTIME parameter of the SETSYS command, the timer expires and checks for shutdown. Volume functions check for shutdown before processing the next data set. After all subtasks have been detached and all secondary address spaces have completed processing, DFSMShsm issues a message (ARC0002I) to notify the operator that shutdown is complete and returns control to the system.

When DFSMShsm is shut down and restarted but MVS has not been reloaded at initial program load, user and HSENDCMD commands that did not complete are restarted as part of the DFSMShsm initialization process. Commands entered from the system console that have not been processed are lost, and any request that exceeds the extended common service area (ECSA) limit per address space is also lost.