GDSX (Extended General Device Support) Manual

Operations and Support
Extended General Device Support (GDSX) Manual—529931-001
3-17
Types of Messages Generated
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-79.) 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
°
Abend messages
°
Trap messages
•
EMS messages (at EMS terminal)
°
EMS event messages
°
Fault messages
An abnormal condition within GDSX can generate a number of different messages.
For example, a trap can generate a fault message at the EMS terminal, and a trap
message and an abend message at the home terminal.
EMS messages generated by converted GDSX processes always show the PIN with a
value of 255.
Startup Configuration Error Messages
These messages may be generated by GDSX during data space initialization. At
GDSX process startup, TSCODE calculates the space required in extended memory
for each type of control block. Only after all calculations have been completed are
allocations done for the control block pools. Equations for these calculations are given
in Figure 2-2 on page 2-22. Calculations are made in the following order:
TCB Task control block
IOCB I/O control block
RCV Receive control block
RCB Requester control block