NonStop Operating System Event Management Programming Manual

Configuration Services Event Messages (ZDSC)
HP NonStop Operating System Event Management Programming Manual—520372-020
24-16
Messages
Cause. After $ZCNF received a CRU Insertion or TNet CRU Configured event, it tried
to add CRU information to the Physical CRU Table (PCT) or the TNet Node Table
(TNT) respectively, but found that the tables were full.
Effect. The CRU information does not get stored into the PCT or TNT and, therefore,
is unavailable for later queries.
Recovery. See Recovery Action Requiring Vendor Support on page 24-10.
1031: ZDSC-EVT-BAD-MAINTENANCE-EVENT
Inconsistent or bad event data has been received from the service processor.
Unconditional Tokens
Cause. This event occurs whenever $ZCNF receives incorrect or inconsistent
information in event packets received from MIOP. The incorrect information could be
one of:

The domain (group) number passed in the event is zero or greater than the
maximum value of 99.

The event length is greater than the size of the event structure defined by SP.

If the event is followed by a CRU insertion event from SP, there could be a
mismatch in the Group, Module Slot information contained in the event and the
information in the PCT maintained by $ZCNF.
Potentially critical event: No
Action event: No
Message sender: $ZCNF
TMDS collector: No
OSM/TSM collector: Yes
Unconditional Tokens
ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT
ZDSC-TKN-SP-EVENT-DATA token-type ZSPI-TYP-STRING
Event-Message Text
Inconsistent or bad event data received from the service
processor.
Received message: sp-event-data
Token Description
ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVT-BAD-
MAINTENANCE-EVENT (1031).
ZDSC-TKN-SP-EVENT-DATA Bad event data received from the service processor. Value
is ZDSC-TNM-SP-EVENT-DATA.