The ACTMODE column in a resource table provides a way for the automation designer to specify different actions for the same mismatch event that is based on any relevant criteria. For example, a DOWN/UP mismatch might be responded to differently immediately following an IPL when some subsystems are not ready, than it would after the system has reached full production.
The ACTMODE column strongly influences the action selection process when SSM responds to a resource state change.
When the value of the ACTMODE column of a resource is changed, the SSM engine immediately selects that resource for processing, even if there is no state mismatch. This selection occurs regardless of what caused the value of the ACTMODE column to change. For example, the following actions all cause selection to occur:
The purpose of the ACTMODE column is to define special actions. For example, consider the relationship between CICS and IMS, where IMS is a prerequisite of CICS and CICS is a subrequisite of IMS. Suppose you want to restart IMS without shutting down CICS. To do this action, you could cause the IMS resource to be selected for processing by SSM by setting ACTMODE='BOUNCE' for IMS, and then supplying the following action to your action table:
ACTION_PROCESS ACTION_CURRENT ACTION_DESIRED ACTION_MODE ACTION_RES_TYPE ACTION_TEXT 1 ACTION UP UP BOUNCE RULE("BOUNCE &JOBNAME")
The rule BOUNCE ignores the subrequisite relationship between CICS and IMS and cycles IMS as requested.
|
Copyright © 2014 CA.
All rights reserved.
|
|