To improve the speed with which you can begin monitoring, Tivoli OMEGAMON
XE for z/OS provides predefined situations. These situations check for
system conditions that are generally considered to be problematic or noteworthy
and can trigger Critical or
Warning event
indicators in the Navigator.
You can examine the conditions or values being monitored using the Situation editor, 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 Tivoli OMEGAMON XE for z/OS attributes.
Note: If you choose to make changes to a predefined situation, you should change a copy and preserve the original situation in the form in which it was shipped.
Activating predefined situations
Some situations are shipped with very high or very low values, which essentially disable these situations by default. You should examine these situations and customize them with values that are meaningful for your installation.
Several of the sysplex-level predefined situations shipped with the product are auto-started. This means that they are set to run at Candle Management Server startup and are distributed to the MVS_SYSPLEX managed system list. The Candle Management Server populates this managed system list with each online sysplex proxy node automatically and these situations begin monitoring when the Candle Management Server starts.
The predefined sysplex level situations that are auto-started are:
MVS_ CFStruct_ Status_ Crit
MVS_ CFStructUsers_ Connect_ Crit
MVS_ CFSystems_ Performance_ Crit
MVS_ XCFGroupMembers_ Status_ Crit
Sysplex_ DASD_ Dev_ ContIndx_ Warn
Sysplex_ Workloads_ PerfIdx_ Crit
Sysplex_ XCFSystems_ Status_ Crit
All of the Crypto situations are also auto-started. They are distributed to the MVS_SYS managed system list. The other predefined situations are neither set to auto-start nor assigned to managed systems. You must activate these situations to use them.
To activate a situation:
Distribute (assign) the situation to one or more managed systems (or managed system lists).
Start the situation.
Note: If you want the situation to continue running across Candle Management Server restarts, you should also check the Run at startup option.
For more instructions for activating situations, see Using IBM Tivoli OMEGAMON XE for z/OS. See also: Situations and Events Overview; Associate or Disassociate Situations; Start, Stop or Delete a Situation.