How it works: Resource modifications

Stabilized feature: CICSPlex® SM Real-Time Analysis (RTA) is stabilized. Consider moving to Policy system rules or to a dedicated monitoring product such as IBM OMEGAMON for z/OS. See also Stabilization notices and discontinued functions.

Resource modifications are defined as part of the evaluation definitions (EVALDEFs) associated with this analysis definition (RTADEF).

If the modification executes without a CICS® exception condition or CICSPlex SM error, and the condition generates a CICSPlex SM event, the event is canceled. If the modification does not cause the condition to become false for any other reason (for example, the resource is in use or is not available, or the modification was not designed to modify the resource to cause a false condition), it is retried. The retry will occur at the next analysis interval, and will continue until the condition described by the evaluation definition is false.

If the modification executes with a CICS exception condition or CICSPlex SM error, it is not retried. If the condition generates a CICSPlex SM event and the modification cannot be made, the event remains displayed on the EVENT view.

For the Execute evaluation modification string field, the Always option should be used where the modification string includes an expression that will cause the evaluated condition to become false, for example:

                Resource table: LOCTRAN           
                Evaluation    : STATUS NE ENABLED 
                Modification  : STATUS=ENABLED

The Always option would work well with this example because the modification will cause the evaluation to become false. The Always option should not be used if that is not the case, for example:

               Resource table: LOCTRAN           
               Evaluation    : STATUS NE ENABLED 
               Modification  : PRIORITY=255

The Always option would not work well with this example because the modification will not cause the evaluation to become false.

The actions requested in an action definition (such as events or external messages) are always performed, regardless of whether any resource modification is requested.