Control-O Rule Definitions

A Control-O rule is a set of parameters that define actions to be performed upon the detection of specified message, command and event criteria. When message, command and event criteria are detected, the rule is triggered (that is, the actions specified in the rule are performed).

Each rule definition contains the sections shown in Table 2:

Table 2 Rule Definition Sections

Section	Description
Message/Event Selection Criteria	The message, command, or event that, when detected, triggers the rule.
General Parameters	General information about the rule, such as its description and security mode.
Action Parameters	Actions to be performed when the rule is triggered.
Basic Scheduling Parameters	Days and dates on which a Control-O rule is eligible for triggering.
Runtime Scheduling Parameters	Conditions that must exist before a Control-O rule is eligible for triggering.

Each rule only needs to be defined once. (The mechanism used to define Control-O rules is discussed later in this chapter.) Once defined, the rule definition is saved. It can be modified later on as required, and the changes saved.

Rule definitions are stored in members in partitioned data sets (libraries) as follows:

Multiple rule libraries can be defined.
Multiple rule tables are stored together in partitioned data sets called rule libraries.
Rule definitions for related topics (for example, IPL or CICS) are generally stored together in a single member called a "rule table."

Parent Topic

Main Components