EMS Manual

EMS Procedures
EMS Manual—426909-005
15-22
EMSTEXT Procedure
if present, is the key of a format template. EMSTEXT uses the template to format
the headers of all event messages for display as text.
With the header template key, you can customize the header information for all the
event messages of an application. The header is the first part of the event
message. It includes such information as the ID of the process that gave rise to the
event and the date and time when it occurred.
If header-template-key is missing or all zeros, EMSTEXT has its own header
template to provide the process ID, date, and time in text form.
The text describing the event, usually produced from a template indicated by the
message number, follows the header text.
header-template-key is structured like:
STRUCT TEMPLATE^KEY
BEGIN
STRUCT SSID(ZSPI^DDL^SSID^DEF);
INT(32) TOKENCODE;
INT(32) TOKENVALUE;
END;
The value in the SSID field comes from the SSID: (subsystem ID) statement in the
template file that defines the format template—except that the version part of the
subsystem ID is not used. The values in TOKENCODE and TOKENVALUE come
from the first two parameters of the MSG: statement in the template file. (For
information about template files and format templates, see the DSM Template
Services Manual.)
indent
INT:value
if present, is a hanging indent value; it defines how many blanks precede the text
in every logical line of displayable-text-buffer except the first. This number
is referred to as i, described previously.
If you do not want the displayed message text indented, set indent to 0. If
indent is omitted or -1, EMSTEXT uses a default value.
< RESERVED > This parameter is reserved for future use.
extended-status
INT(32) .EXT:ref:1
is a pair of 16-bit-integer status codes, as described in Table 15-5. Compare to
status, described previously. The value of extended-status is undefined if the
returned value of EMSTEXT (the simple status) is (0, x) and x >0.