To test whether SSM checks prerequisites (if any are defined) for your started tasks, follow a procedure like the one described below.
Suppose that your STCTBL table contains rows defining these tasks:
|
NAME |
DESIRED_STATE |
CURRENT_STATE |
PREREQ |
MISSING_PREREQ |
|---|---|---|---|---|
|
TESTTASK1 |
DOWN |
DOWN |
NULL |
NULL |
|
TESTTASK2 |
DOWN |
DOWN |
TESTTASK1 |
NULL |
TESTTASK1 has no prerequisites but is itself a prerequisite for TESTTASK2, so TESTTASK1 must be active before TESTTASK2 can start.
To verify this
The desired state for TESTTASK2 will change to UP, and the MISSING_PREREQ column value will change to TESTTASK1, indicating that TESTTASK2 cannot start until this prerequisite is satisfied.
The desired state for TESTTASK1 changes to DOWN and the MISSING_PREREQ value for the task changes to TESTTASK2, indicating that SSM cannot stop TESTTASK1 until the task that requires it. TESTTASK2 is also stopped.
SSM will stop TESTTASK2 first, then TESTTASK1.
Step 6 is complete when you have successfully tested the SSMSTART and SSMSTOP rules and the following SSM operations:
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |