PAM Management Programming Manual

Event Messages

PAM Management Programming Manual—142481

6-6

Event Message Descriptions

The remainder of this section explains in detail each event message that can be issued by

the PAM subsystem.

Each description includes a syntax box that lists all the tokens that the PAM subsystem

can place in the message buffer. The common tokens are listed in Table 6-3

. Tokens

appear in the box if they are present in all PAM event messages or if their values differ

from one event message to another. Header tokens are also listed, because an application

can filter on event message header tokens as well as on other tokens.

Tokens can be unconditional or conditional. In the event-message descriptions in this

section, all tokens are unconditional unless otherwise noted. An unconditional token is a

token that is always present in a particular event message. A conditional token is one

that is sometimes but not always present in a particular event message.

The notation used in the box for simple tokens is a shorthand version of the essential

information given in the DDL TOKEN-CODE statement.

With the exception of the ZEMS-TKN-SUBJECT-MARK token and the subject token

listed immediately after it, the order of the tokens in the box is not necessarily the order

in which they appear in an event message. The ZEMS-TKN-SUBJECT-MARK token

always immediately precedes the subject token of an event message. For more

information on the subject token, refer to the EMS Manual.

The event message text box is followed by descriptions of the event-message tokens,

which are defined in the same order as they appear in the box. The descriptions of

simple tokens in this section do not identify the token numbers of the tokens. However,

the symbolic names of the token numbers can be derived from the token names by

simply replacing -TKN- with -TNM-. For example, the token number of the ZPAM-

TKN-FNAME token is ZPAM-TNM-FNAME.

The event message text appears in a separate box, as it would appear if you used the

EMSTEXT procedure and viewed it from the Tandem Service Management (TSM)

EMS Event Viewer application. The text version of an event message is available

through the EMSTEXT procedure. It contains a standard header that includes the

subsystem name, reporting process, and other information. The text shown in the box

follows this standard header. For further information on the standard header, refer to the

EMS Manual.