Coding Each AOF Rule Type › Request Rules › AOF Variables Available in REQ Rules

AOF Variables Available in REQ Rules

You can use all AOF variable types in REQ rules, as described in the chapter “AOF Rule Tools.” You can use the following unique AOF event variables in the )PROC section of a REQ rule, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.

REQ.CODE

The current OPSREQ event specifier, taken from the CODE keyword of the OPSREQ command

Data Type: Character, read-only

Sample Value: CANTSO

Note: You can enter the CODE value of OPSREQ either as a keyword (for example, CODE(CANTSO)) or as a positional parameter. The CODE value determines which request rules execute for the current event.

OPSLOG Browse Column: MSGID

REQ.TEXT

A description of the current request

Data Type: Character, read-only

Sample Value: CANTSO USERA

Note: CA OPS/MVS creates the REQ.TEXT variable by concatenating the value of the CODE clause and the value of the TEXT clause in an OPSREQ command. A blank separates the two values.

OPSLOG Browse Column: Text is always displayed.

REQ.USER

An 8-byte variable providing communication between rules that execute for the same request event. The variable can contain any installation data that these rules need, and it can store a character string displayable through OPSLOG Browse.

Data Type: User-defined, read/write

Note: Before AOF processing, this variable is initialized to binary zeros. It is then passed to each rule that executes for the same request event; each rule can look at or change the variable contents before passing the variable to the next rule for the request event.

OPSLOG Browse Column: USER