To test whether SSM checks prerequisites (if any are defined) for your started tasks, follow a procedure like the one after the example table.
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.
Follow these steps:
The desired state for TESTTASK2 changes to UP, and the MISSING_PREREQ column value changes 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 stops TESTTASK2 first, then TESTTASK1.
Step 6 (Test the SSM Operation) completes when you have tested the SSMSTART and SSMSTOP rules and the following SSM operations successfully:
Copyright © 2014 CA.
All rights reserved.
|
|