IBM Workload Scheduler for z/OS, Version 9.3 SPE

Syntax to define event rules

This section describes the syntax to edit the EVLIB.XML data set, that is referenced as SYSIN in the EQQTRBLS skeleton (produced when running EQQJOBS).

While editing the EVLIB.XML data set, consider using the HILITE ON XML or HILITE LOGIC XML editor commands. They require a record length equal to 255, as specified in the EQQPCS01 sample.

The following is a list of all the language elements used for defining an event rule. Table 1 explains the meaning of the notation that follows each language element. n represents an unbounded number.

Table 1. Valid number of occurrences for a language element
Notation	Meaning
(0, 1)	0 indicates that the language element is optional. 1 indicates that if coded, only 1 occurrence is allowed.
(0, n)	0 indicates that the language element is optional. n indicates that if coded, multiple occurrences are allowed.
(1, 1)	The first 1 indicates that the language element is required. The second 1 indicates that only 1 occurrence is allowed.
(1, n)	1 indicates that the language element is required. n indicates that multiple occurrences are allowed.

eventRule name=" " ruleType=" " isDraft=" " (1, 1)
- description (0, 1)
- eventCondition eventProvider=" " eventType=" " (1, 1)
  - filteringPredicate (1,1)
    - attributeFilter name=" " operator="eq" (1, n)
      - value (1, 15)
- action actionProvider=" " actionType=" " responseType=" " (1,1)
  - description (0, 1)
  - parameter name=" "(0, n)
    - value (0, 1)

Event rule definitions are grouped into event rule sets.

eventRuleSet (1, 1)
- eventRule (1, n)

Use the eventRuleSet language element also if you have to enclose a single rule definition.

To include comments in the XML file, use the form .