Using System State Manager › Desired Table States

Desired Table States

A resource table has a table-relative UP state of RUN, and a table-relative DOWN state of STOP. The desired state is RUNPEND and the current state is STOPPED. This transition is considered to be a DOWN-to-UP transition because the first three characters of desired state RUNPEND match the table-relative UP state of RUN, and the first four characters of current state STOPPED match the table-relative DOWN state. This transition matches the STOPPED/RUNPEND entry in the action table, and prerequisite checking also completes.

Consider a VTAM resource table, for which the table-relative UP state is defined as ACTIVE and the table-relative DOWN state is defined as INACTIVE. If the desired state changes to ACTIVE or the current state is INACTIVE, then prerequisite checking occurs. Likewise, if the desired state changes to INACTIVE and the current state is ACTIVE, then subrequisite checking occurs. However, if the desired state changes to ACTIVE and the current state changes to STARTING, then neither prerequisite or subrequisite checking occurs; however, an action is still asserted.

For example, suppose that you have a directory table containing the following columns and values:

Also suppose that you have the following entries in the STCTBL resource table (not all columns shown):

Finally, suppose that you have the following entries in the VTAM_NODES resource table (not all columns shown):

The resource PRODCICSA in the STCTBL resource table has a desired state value of UP, which is defined as its table-relative UP state in the directory table. However, SSM does not execute the automation procedure to set the current state of PRODCICSA to UP because the prerequisites for PRODCICSA are not in their defined UP states. As you can see in the examples, PRODCICSA has prerequisites of VTAM, whose current state is STARTING, and CICSA in the VTAM_NODES table, whose current state is INACTIVE.

Note: These unsatisfied prerequisites are also listed in the MISSING_PREREQ column of the STCTBL resource table.

Once the current state of VTAM is set to UP and the current state of CICSA is set to ACTIVE, SSM can take the necessary action to place PRODCICSA in its defined UP_STATE.

A resource that is a prerequisite for another resource can exist in any SSM table. When a resource and its prerequisites are defined in different monitored tables, the prerequisite resource must be defined as tablename.resourcename, as shown with VTAM_NODES.CICSA in the preceding examples.