GDSX Manual

Operations and Support
Extended General Device Support (GDSX) Manual–134303
3-16
Interpreting Console and EMS Messages
Interpreting Console and EMS Messages
Messages generated by GDSX can be classified according to severity:
Where Messages Are Displayed
GDSX can generate console messages to the home terminal and EMS messages to an
EMS display terminal. These terminals can be configured to be the same device or
different devices.
Home Terminal
At process initialization time, all messages from TSCODE are sent to the home
terminal, because the monitor task, which handles messages sent to EMS, is not yet
active. To ensure that all messages are seen, you can change the home terminal to a
paused terminal. For example, the following RUN command changes the home terminal
to device $TF2.#F22:
> RUN GDSE /NAME $GDSX, NOWAIT, TERM $TF2.#F22/
Make sure you pause such a terminal.
EMS Terminal
GDSX processes send tokenized event messages to the Event Management Service
(EMS) primary collector ($0) process. The collector stores these messages in the
current EMS log file. EMS distributor processes select messages from the log file and
deliver them to consumers.
A distributor process can use a filter to limit the types of events passed to a consumer.
(For instructions on how to program and run a filter with GDSX, see “EMS Filters and
GDSX” on page 2-75.) The distributor process will direct output to a designated
terminal, called the EMS terminal.
Types of Messages Generated
GDSX generates the following types of messages. For listings of the messages in each
type see the following headings.
•
Console messages (at home terminal)
°
Startup configuration error messages
Status messages Report a state change within a GDSX process. Some examples
of status messages are startup, open, and close messages.
Warning messages Report an unexpected state change within a GDSX process. An
example is a message reporting that the backup stopped.
Error messages Report that an error occurred within a GDSX process. Two
examples of conditions that cause the generation of error
messages are a checkpoint failure and a memory pool error.