Test SSM

Using System State Manager › How to Use the Full Capabilities of SSM › Step 6: Test the SSM Operation › Test SSM

Test SSM

To determine whether SSM correctly starts and stops your started tasks, complete the following tasks:

Issue z/OS commands to stop the tasks.
Verify that both the current state and desired state are set to down.
On the System State Manager Control panel, enter ACTIVE in the Stateman field to change the SSM resource monitoring mode to ACTIVE. ACTIVE mode causes the SSMBEGIN request rule to execute, prompting you with the messages shown in Setting the Desired State. Because you have already set the desired state, select option 5 in response to these messages.

Note: The WTOR message from the SSMBEGIN request rule is not sent to your TSO session.
Start one of your started tasks by issuing the following z/OS command:
```
S taskname
```
This step causes the SSMSTART rule to capture the S taskname command and update the desired state to UP for that resource. SSM then initiates the action that is defined in the STCTBL_ACT table to get the task started.
Verify that the task starts correctly. Once it has initialized fully, verify that both the current state and desired state for the task are set to UP.
While SSM restarts the task, you can check its progress by locating these messages in the SYSLOG or in the OPSLOG. In this sample, SSMSTART changes the desired state of a job to up.
```
S taskname
SSMSTART: DESIRED_STATE OF taskname CHANGED TO UP
OPS7902H STATEMAN ACTION FOR STCTBL.taskname:
DOWN_UP=OPSCMD COMMAND('START taskname') NOOUTPUT
OPSCMD COMMAND('START taskname') NOOUTPUT
START taskname
```
Issue this command:
```
P taskname
```
Verify that SSM correctly stops the started task and that both the current state and desired state are set to DOWN after the task has ended. The process SSM uses to stop the task is much the same as the process that executes when you issued the S taskname command, except that the messages in the SYSLOG or OPSLOG reflects the stopping actions.