The SA z/OS monitoring agent provides a set of predefined situations that monitor the status and health of automation resources within the SA z/OS subplex. These situations check for specified conditions and can trigger
Critical,
Warning,
or
Informational situation event indicators
(also called alerts) in the Navigator. When a situation triggers an alert,
you can investigate the situation event by opening its workspace. If both
a warning and a critical condition occur for the same workspace, the indicator
always shows the highest-level situation event (the critical one).
You can use the Situation Editor to examine the conditions or values being monitored and, if necessary, change them to ones better suited to your environment. You can also use the predefined situations as models for creating your own situations, using SA z/OS monitoring agent attributes. Before your new situations can take effect, you must distribute them to the systems you want to monitor.
Tip: Rather than editing a predefined situation, copy it with Create Another and then edit the copy. This practice prevents your edited situations from being overwritten during installation and configuration of future versions of the product. For instructions, see the Tivoli Enterprise Portal online help.
Situations are expressions embedded in IF-TRUE statements of system conditions that you want to monitor. This means that if the specified condition exists, then the situation is true and triggers an alert.
A condition consists of an attribute, a value, and a comparison operator. When a situation is activated, the value of the attribute is compared with the value set for the condition to determine whether the condition is met. For example, the Kah_Rsrc_NotSatisfactory_Crit situation is true when the value of the Compound_Status attribute is Problem. This is the formula:
If Resource_List.Compound_Status equals Problem then the situation Kah_Rsrc_NotSatisfactory_Crit is true.
All the predefined situations are started automatically. This means that they are set to run on startup of the Tivoli Enterprise Monitoring Server.
If you define situations that use a counter or a range of numbers, always provide positive values. For example, use a greater-than-or-equal-to-zero expression, as shown in some of the predefined situations described below. This practice prevents a situation from falsely tripping when the monitoring agent encounters an undefined attribute value. Undefined attribute values are interpreted as negative numbers and might erroneously raise alerts for a situation that specifies a negative number.