TS/MP 2.5 Management Programming Manual

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series

171

172

173

174

175

176

177

178

179

180

ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT.

TOKENS FOR NESTED MESSAGE are described in “Nested Messages” (page 169).

Effect. The Pathsend statement or SEND operation fails.

Recovery. For additional information, see the description associated with the nested message.

1011: ZPWY-EVT-PM-DELINKFAIL

An error occurred during while a link manager was trying to return a link to a server class. The

nested message indicates the reason for the failure.

For a description of tokens that are present in this event message but are not listed or described

below, see “Event Management” (page 163).

Unconditional Tokens

ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN.

ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT.

ZEMS-TKN-SUBJECT-MARK token-type ZSPI-TYP-SSCTL.

ZPWY-TKN-nnnNAME token-type ZPWY-TYP-nnnNAME.

ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-ENUM.

Conditional Tokens

TOKENS FOR NESTED MESSAGE

Event-Message Text

*1011* link manager-name, DELINK FAILURE:< nested-message

Token Descriptions

ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE.

ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-DELINKFAIL (1011).

ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-TCPNAME or ZPWY-TKN-LMNAME,

which contains the name of the link manager that is the

subject of this event message.

ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT.

TOKENS FOR NESTED MESSAGE are described in “Nested Messages” (page 169).

Effect. The effect depends on the reason for the failure.

Recovery. For additional information, see the description associated with the nested message.

1012: ZPWY-EVT-PM-DUPNAME

Either the PATHMON process tried to add an object having a name that already exists, or the

PATHMON process tried to start a Pathway/iTS TCP or server process using a process name that

is already active within this Pathway subsystem.

This message usually indicates that there was an attempt to use an object name or a process name

twice. For example, if this is a nested message in a CAN’T GRANT LINK error (for more information,

see the description of event 1007), the process name for a dynamic server already exists in the

list of active server processes and TCPs.