Perform the IPL using your newly created COMMNDnn member. Once CA OPS/MVS initializes and SSM becomes active, the SSMBEGIN request rule executes and prompts you to choose a startup option.
Note: Remember that you must use a startup option to initiate SSM at IPL time.
At this point, both the CURRENT_STATE and DESIRED_STATE columns in the STCTBL table are set to the table-relative UNKNOWN state. Your STCTBL entries will resemble the following example (not all columns are shown):
NAME |
CURRENT_STATE |
DESIRED_STATE |
IPL_STATE |
TASK1 |
UNKNOWN |
UNKNOWN |
UP |
TASK2 |
UNKNOWN |
UNKNOWN |
IPL |
TASK3 |
UNKNOWN |
UNKNOWN |
DOWN |
Reply 3 to the WTOR to initiate the startup process. The following occurs:
RULE("SSMSTATE TABLE(&SSMTABLE) NAME(&NAME) JOBNAME(&JOBNAME)...")
The entries in the STCTBL table now look like this:
NAME |
CURRENT_STATE |
DESIRED_STATE |
IPL_STATE |
TASK1 |
DOWN |
UP |
UP |
TASK2 |
UP |
IPL |
IPL |
TASK3 |
DOWN |
DOWN |
DOWN |
Note: As long as TSO is available, use OPSVIEW option 4.3 to view server activity. This data can help you diagnose any problems you may encounter during system shutdown or IPL by showing server commands in progress and any excessive queue delay times. You can also use OPSVIEW option 4.11.2 (System State Manager Resource Control) to watch the states of resources change.
Copyright © 2014 CA.
All rights reserved.
|
|