AM3270 Management Programming Manual

EVENT MANAGEMENT
Event-Message Descriptions
If the event is for a controller that uses the I/O addressing
that does not allow conversion from the physical I/O address
to the subchannel CU address format, then the event message
buffer will contain the ZEMS-MAP-EXIOADDR token only. Use of the
ZEMS-MAP-EXIOADDR token results because the physical I/O address
without conversion will not fit into the ZEMS-TKN-CU token; the
AM3270 subsystem will not place the ZEMS-TKN-CU into the event
message buffer because the token would be meaningless.
The formatting for the display is done using display-text
procedures which are the application interface to the DSM
Template Services. Refer to the DSM Template Services Manual for
details on these procedures. The difference between the displays
of the I/O addresses is that one of the display fields for a
subchannel-type I/O address will be zero.
The box also contains a portion of the text version of the event
message. The text version of an event message is available
through the EMSTEXT procedure, and it contains a standard header
that includes the date, time, system name, and other information.
(For further information on the standard header, refer to the
Event Management Service (EMS) Manual ). The text shown in the
box follows this standard header.
When you use the EMSTEXT procedure to get the text version of
an event message, you request either the display-format version
or the console-compatible-format version, as described in the
Event Management Service (EMS) Manual . In the case of AM3270
event messages, there is no difference between the two versions
(except possibly the standard header). The two versions are
also identical to the corresponding console message, with the
exception of the event message with event number ZAM3-EVT-INTL-
ERR (74).
The notation used in the box for simple tokens is a shorthand
version of the essential information given in the DDL TOKEN-CODE
statement.
Following the box, the event-message tokens are described in the
same order in which they appeared in the box. However, because
Tandem internal tokens are intended for Tandem use only, they are
not described.
7-5