Summary of AOF Coding Guidelines › OPS/REXX Host Environment Rule Characteristics › SAY Output

SAY Output

The following describes the SAY output rule types and where the SAY output is sent for each rule:

API, ARM, DOM, EOJ, EOM, EOS, MSG, OMG, SCR, TLM, TOD, USS

Sent as a WTO with OPS1000I as a default message ID, which may result in it being broadcasted to physical consoles.

CMD

Sent as a WTO with OPS1000I as a default message ID and is directed to the console that triggered the event.

GLV

Destination is that of the SAY destination for the event that initiated the GLV rule.

REQ

Sent as a PUTLINE with OPS1000I as a default message ID to a TSO user. It is sent as a WTO with OPS3092H as a default message ID (prefixed in front of the OPS1000I) to the hardcopy log if the request originated in any class of OSF TSO server.

SEC

Sent as a PUTLINE with OPS1000I as a default message ID to a TSO user. Otherwise, it is sent as a WTO with OPS1000I as a default message ID, which may result in it being broadcasted to physical consoles.

Note: With the exception of REQ and SEC rules, the SAY instruction should only be used for debugging purposes. Use the ADDRESS WTO OPS/REXX host environment when WTO generation is needed in your automation.