Chapter 31 EMSTEXT Messages

When EMSTEXT is not able to properly display an event message, one of the messages in this chapter is displayed. Because one of these messages is displayed only when there is a problem displaying the proper event message text, these message texts can appear with any subsystem ID and event number.

EMSTEXT -- Bad event buffer: word1 word2 word3 . . .

wordn

is a hexadecimal dump of up to 60 words of the invalid event message.

Cause The event message to be displayed was not a valid SPI event message buffer.

Effect The above message is displayed instead of the appropriate text for the event message.

Recovery Check that the program generating this message is properly obtaining event messages and passing them to EMSTEXT.

EMSTEXT error (e1,e2) prevented display of event. SSID = ssid Event number = number [ Subject = first-subject-value ]

`e1` and `e2`	are the two parts of the EMSTEXT extended status code for the problem encountered.
`first-subject-value`	is the first subject of the event.

Cause EMSTEXT encountered some error other than a missing template or a file error when attempting to produce display text for event number of the ssid subsystem.

Effect The above message is displayed instead of the appropriate text for the event message.

Recovery Consult the description of the EMSTEXT status codes in the EMS Manual to determine the exact meaning of the status code displayed.

EMSTEXT -- No template and no TEXT token for event. SSID = ssid Event number = number [ Subject = first-subject-value ]

first-subject-value

is the first subject of the event.

Cause The event message (identified by ssid and number) has no formatting template for it in the current template file, and the event message does not contain a TEXT token.

Effect The above message is displayed instead of the appropriate text for the event message.

Recovery If the event is supposed to have a formatting template, be sure that the program which displayed this message is using the proper template file and that the template file contains a formatting template for the indicated subsystem and event number. If the event is supposed to have a TEXT token, be sure that the program generating the event adds the TEXT token to the event. Also, be sure that the EMS subsystem ID is used to qualify the TEXT token when it is added to the event.

EMSTEXT -- Template file problem (e1,e2): File [open] error - filename - msg. SSID = ssid Event number = number [ Subject = first-subject-value ]

`e1` and `e2`	are the two parts of the EMSTEXT extended status code for the problem encountered.
`filename`	is the name of the template file with which there is a problem.
`msg`	is an English description of the status code.
`first-subject-value`	is the first subject of the event.

Cause The program trying to display events had a problem opening or reading the template file when it attempted to produce display text for event number of the ssid subsystem.

Effect The above message is displayed instead of the appropriate text for the event message.

Recovery Recovery depends on the exact error. For file‑system errors, see Appendix B, for a description of the error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For other errors, see the description of EMSTEXT in the EMS Manual.