This section lists the TMS/Engine message route codes. Messages
can be routed to different console groupings. Routing is based on
the type coded internally with the message. The routing types are:
Table 1. TMS/Engine message route codes| Code |
Description |
|---|
| ABEND |
Abend messages are routed to the system console. |
| ALERT |
Alert messages are routed to all consoles. |
| ERROR |
Error messages are routed to the console that
made the request that caused the error. |
| INFO |
Information messages are routed to all consoles. |
| LOG |
Log messages are recorded in the TMS/Engine
log data set. |
| REPLY |
Reply messages are routed to the console that
made the request. |
| USER |
Reserved. |
| VIEW |
View messages are written to the VIEWLOG cluster. |
| WARN |
Warning messages are routed to all consoles. |
Initial defaults are for all consoles to accept ALERT, ERROR,
INFO, REPLY, and WARNING messages addressed to the console. The master
console receives all ALERT, INFO, and WARNING messages, regardless
of the message origin, as well as ERROR and REPLY messages in response
to commands issued from the master console.
The defaults for the VIEWLOG cluster are ALERT, ERROR, INFO, VIEW,
and WARNING. These can be changed with the AS *SYSVLG* MONITOR command.
Defaults for the system log are ALERT, ERROR, INFO, REPLY, and
WARNING.
Note: Although you can change message routing, you
are strongly encouraged to accept the initial defaults.