AOF Rule Structure › Structure of an AOF Rule › )eventtype eventspec—Event Definition Section (Required)

)eventtype eventspec—Event Definition Section (Required)

The event definition section of a rule identifies the system event that causes the rule to execute. CA OPS/MVS uses the information in the event definition section to determine when to run the processing section of the rule.

The event definition section is required and is always the first section of a rule.

Use this format for coding the event definition section:

)eventtype eventspec

Following is a description of the two parts (eventtype and eventspec) that make up the event definition section.

• The eventtype Value

  The following eventtype values represent events that the AOF can recognize:

  API

  Application Program Interface

  ARM

  Automatic Restart Management event

  CMD

  Operator command event

  DOM

  Delete-operator-message event

  EOJ

  End-of-job event

  EOM

  End-of-memory event

  EOS

  End-of-step event

  GLV

  Global variable event

  MSG

  Message event

  OMG

  OMEGAMON exception event

  REQ

  End user request event

  SCR

  Screen event

  SEC

  Security event

  TLM

  Time limit-exceeded event

  TOD

  Time-of-day event

  USS

  UNIX System Services event

  For more information about the types of system events that the AOF recognizes, see the chapter “Using the AOF.”

• The eventspec Value

  The eventspec value is a character string template matching some event identifier (such as message IDs for MSG events, system commands for CMD events, and time specifications for TOD events).

  Each AOF rule type has a different eventspec template.

Examples: Event Definition Section

• Example 1: Identifies $HASP100 messages

  )MSG $HASP100
  

• Example 2: Identifies VARY commands

  )CMD VARY
  

• Example 3: Identifies an hourly time event

  )TOD ,1 HOUR