Rules Structure

The following tables describe the structures of the OMEGAMON Exceptions solution rules, as well as the following KOA script:

• Log onto OMEGAMON and Analyze Exceptions KOA Script.

  Table 102 Start OMEGAMON Exceptions KOA Script Rule Structure

  Item	Description
  Title	Start OMEGAMON Exceptions KOA Script
  Name	STRTEXCP
  Table	OMEGAMON
  Event	STRTEXCP
  Event Description	This Event rule activates a KOA script that logs onto OMEGAMON, performs OMEGAMON command LEXSY and analyzes the results of the command. The rule is usually triggered only once, immediately following IPL, but the KOA script remains logged onto OMEGAMON and continues analyzing exceptions until the next IPL.
  Basic Scheduling Parameters	Always schedule this rule.
  Runtime Scheduling Parameters	IN CTO-KOAOM-GO STAT
  Global Variables	%%CTO_KOAOM_STOP
  Rule Logic	This rule is usually triggered automatically, immediately following IPL. The rule starts KOA script OMLEXSY, which logs onto OMEGAMON and issues OMEGAMON command LEXSY with automatic refresh. The KOA script remains logged onto OMEGAMON until the next IPL, or until the user manually terminates the script (using rule STOPEXCP in this solution). The rule deletes its own prerequisite IN condition CTO-KOAOM-GO STAT so that the rule can be re-invoked (by adding this condition again).
  Rule Actions	Sets Control-O Global variable %%CTO-KOAOM-STOP to NO. Activates KOA script OMLEXSY. Deletes condition CTO-KOAOM-GO STAT.
  Activating the Rule	The rule is triggered when its prerequisite IN condition CTO-KOAOM-GO STAT is set. For details about how to stop KOA script OMLEXSY, see the following section.
  Recommended Mode or Category	During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare category for this rule is 2—some customization of the KOA script is required before implementation.
  Customization	The rule itself requires little or no customization, but KOA script OMLEXSY must be carefully examined and adapted to site requirements.

  Table 103 Terminate OMEGAMON Exceptions KOA Script Rule Structure

  Item	Description
  Title	Terminate OMEGAMON Exceptions KOA Script
  Name	STOPEXCP
  Table	OMEGAMON
  Event	STOPEXCP
  Event Description	This Event rule terminates the KOA script that detects OMEGAMON exceptions, by setting Global Control-O variable %%CTO_KOAOM_STOP to YES.
  Basic Scheduling Parameters	Always schedule this rule.
  Runtime Scheduling Parameters	IN CTO-KOAOM-STOP STAT
  Global Variables	%%CTO_KOAOM_STOP
  Rule Logic	This rule must be triggered in order to terminate KOA script OMLEXSY. The rule sets Control-O Global variable %%CTO_KOAOM_STOP to YES, which indicates that a user wants to terminate the KOA script. KOA script OMLEXSY periodically checks if Global variable %%CTO_KOAOM_STOP is set to YES; if it is, the script immediately logs off of OMEGAMON. The rule deletes its own prerequisite IN condition CTO-KOAOM-STOP STAT so that the rule can be re-invoked (by adding this condition again).
  Rule Actions	Sets Control-O Global variable %%CTO-KOAOM-STOP to YES. Deletes its own prerequisite IN condition CTO-KOAOM-STOP STAT. Issues a WRITEGLOBAL command to the Control-O Monitor.
  Activating the Rule	The rule is triggered by manually setting its prerequisite IN condition CTO-KOAOM-STOP STAT.
  Recommended Mode or Category	During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare category for this rule is 1—little or no customization is required before implementation.

  Table 104 Log onto OMEGAMON and Analyze Exceptions Script Structure

  Item	Description
  Title	Log onto OMEGAMON and Analyze Exceptions
  Name	OMLEXSY
  KOA Script Description	This KOA script logs onto OMEGAMON, enters auto-refresh mode, and performs OMEGAMON command LEXSY (which displays exceptions detected by OMEGAMON). The script "shouts" a message to the responsible user when certain OMEGAMON exceptions are detected.
  Activating the KOA Script	The KOA script is activated by rule STRTEXCP in this solution.
  Parameters	None.
  Global Variables	%%CTO_KOAOM_STOP
  KOA Script Logic	The KOA script logs onto OMEGAMON and issues OMEGAMON command LEXSY with automatic refresh. In response, OMEGAMON displays a list of current system-wide exceptions, which is periodically refreshed. (For further details, see the OMEGAMON/OS/390 User Guide.) Exceptions considered of special interest are specified within the KOA script. The list of OMEGAMON exceptions is analyzed by the KOA script and when a specified exception is detected, the script "shouts" a message to the responsible user. The script periodically checks if Global variable %%CTO_KOAOM_STOP is set to YES; if it is, the script immediately logs off from OMEGAMON. As long as Global variable %%CTO_KOAOM_STOP is set to NO, the script periodically checks the refreshed exception list for new exceptions of interest.
  	Note: Although an exception reappears in each refresh until the problem is corrected, KOA shouts the message for that exception only once – for that occurrence of the problem. (This is controlled through Control-O variables %%CTO_%%EXCPID_FOUND and %%CTO_%%EXCPID_SENT.)
  Recommended Category	The SolveWare category for this KOA script is 3—the script is provided as an example. Some customization is needed if the script is to be implemented.
  Customization	New exceptions of interest can be added to, or existing exceptions deleted from, the sample KOA scripts. SHOUT message destinations can be changed. Locate the SHOUT messages in the KOA scripts and determine, for each kind of exception, the TSO-user who is to receive this type of message. Command PAUSE specifies the number of seconds to wait between analyses of the (refreshed) list. The default value provided in the script is one minute. This value can be modified according to site requirements. You can use command MAXCOMMAND during the test period; however, remember to remove this limitation before implementing this solution to enable it to be active 24 hours a day.