Using System State Manager › How to Use the Full Capabilities of SSM › Step 7: Perform an IPL with SSM › Perform a System Shutdown

Perform a System Shutdown

With SSM, system shutdown is nothing more than setting the DESIRED_STATE to DOWN for all active started tasks that SSM controls. The OPS.CCLXSAMP data set contains a member called SSMSHUT, which provides various options you can tailor to meet your shutdown requirements.

If you intend to use the SSMSHUT program when you implement SSM on your production system, see The SSMSHUT Program in this chapter to understand how it works. For now, invoke SSMSHUT by issuing the following console command:

!OI SSMSHUT

Note: In the console command above, the ! represents the OSF command character.

In response, you will see the following message:

002 SSMSHUT MVS System shutdown requested at 12:20. Reply
  within 00:01 'A' to abort or 'N' to shutdown now.

Reply N to initiate the shutdown process. The following occurs:

• The SSMSHUT program sets the DESIRED_STATE column for all started tasks in the STCTBL table to DOWN.
• SSM responds to the mismatch of current state (UP) and desired state (DOWN) by invoking the correct shutdown command or procedure specified in the STCTBL_ACT table.
• The started tasks end and the appropriate rules packets set the current state to DOWN.
• SSMSHUT will enable the SSMSHUTM rule, which will display all resources that have not terminated due to prerequisite constraints every 60 seconds. The SSMSHUTM rule must be present in the active rule sets.

Once you start a system shutdown or IPL, you can invoke the SSMDISP OPS/REXX program. By using this command periodically, you can keep track of what the current state is and what the desired state is as time lapses.

The following variables can help you diagnose any problems with SSM that may occur during your initial system shutdown or IPL.

OI SSMDISP

Displays resources where the current state does not equal the desired state.

!OI SSMDISP ALL

Displays all resources.

For more information, see The SSMDISP Program in this chapter.

The SSMDISP REXX program should display all started tasks that do not have both their current state and desired state set to DOWN. If you have any tasks that do not have a current state of DOWN, then one of the following is true:

• The task ended but the rule did not execute correctly and set the CURRENT_STATE to DOWN. To correct the problem, invoke the STATESET OPS/REXX program using this command:

  !OI STATESET STCTBL.taskname CURRENT(DOWN)
  

• The task has a dependent resource and the MISSING_PREREQ column for the task lists a task that has not ended. SSM will not stop the task until the current state is DOWN for the prerequisite task. Check the actual status of the prerequisite task, or issue the following command to bypass prerequisite checking for the task:

  !OI STATESET STCTBL.taskname MODE(NOPREREQ)
  

• SSM initiated the action to stop the task, but the task is hung.

Proceed with your shutdown of the system and note any tasks that needed special attention.