OSI/MHS Management Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

501

502

503

504

505

506

507

508

509

510

Event Messages

OSI/MHS Management Programming Manual—424824-001

6-99

25: ZMHS-EVT-FTL-OSI-RESOURCE

ZMHS-TKN-FIRST-SUBCODE

further describes ZMHS-TKN-FIRST-ERROR. It is only present if the token

ZMHS-TKN-ERROR-DATA has the value ZSPI-VAL-TRUE.

ZMHS-TKN-DEVICE-DATA

has the value ZSPI-VAL-TRUE if the device information is present, ZSPI-VAL-

FALSE if the device info is not present.

ZMHS-TKN-FSYS-ERROR

is only present if the token ZMHS-TKN-DEVICE-DATA has a value of ZSPI-VAL-

TRUE. It is the file system error code that was received by X25AM or TLAM,

whichever is being used to provide the lower comm layers.

ZMHS-TKN-CONNECT-INFO

is only present if the token ZMHS-TKN-DEVICE-DATA has a value of ZSPI-VAL-

TRUE. It has the value ZMHS-VAL-CONNECT-INFO-X25 if the error occurred on

an X25 connection, ZMHS-VAL-CONNECT-INFO-LAN if the error occurred on a

LAN connection.

ZMHS-TKN-X25-DATA

has the value ZSPI-VAL-TRUE if the X25 error information is present, ZSPI-VAL-

FALSE if the X25 error information is not present. It is only true if the lower

comms level is provided by X25AM.

ZMHS-TKN-X25-DISC-REASON1 ... 4

are only present if ZMHS-TKN-X25-DATA has a value of ZSPI-VAL-TRUE. They

are the reasons for the circuit disconnection as returned by APS_STATUS in the

structure ZAPS-DDL-LL-BUFFER. For further details see the OSI/AS

Programming Manual.

ZMHS-TKN-X25-CLEAR-CAUSE

is only present if ZMHS-TKN-X25-DATA has a value of ZSPI-VAL-TRUE. It

species the clear cause. For further details see the OSI/AS Programming Manual.

ZMHS-TKN-X25-DIAG-CODE

The ZMHS-TKN-DIAG-CODE token is only present if ZMHS-TKN-X25-DATA

has a value of ZSPI-VAL-TRUE. It specifies the diagnostic code. For further details

see the OSI/AS Programming Manual.

Cause. This event indicates that a resource problem exists for the named device or the

OSI services as a whole at the start up of an OSI/MHS GROUP. No retry attempts are

made and the process stops.

Recovery. Ensure that the device name specified in the event message is correctly

configured. Restart the group.