NonStop Operating System Event Management Programming Manual

Configuration Services Event Messages (ZDSC)
HP NonStop Operating System Event Management Programming Manual520372-020
24-17
Messages
If the event is followed by a TNet CRU configured event from SP, there could be a
mismatch in the Group, Module Slot information contained in the event and the
information in the TNT maintained by $ZCNF.
Effect. If the event packet for which $ZCNF generated a bad maintenance event
contains any events for which there are registered clients, the clients will not be able to
receive the registered events.
Recovery. This problem could be caused by a miscommunication between SP, MIOP
and ZCNF. See Recovery Action Requiring Vendor Support on page 24-10
1032: ZDSC-EVT-UNXPCTD-CRU-CNF
An unexpected Customer Replaceable Unit (CRU) configured event was received for
an unknown CRU.
Unconditional Tokens
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-GROUP token-type ZSPI-TYP-UINT
ZDSC-TKN-MODULE token-type ZSPI-TYP-UINT
ZDSC-TKN-SLOT token-type ZSPI-TYP-UINT
Event-Message Text
A Customer Replaceable Unit (CRU)configured event has been
received for an unknown CRU.
Group: group
Module: module
Slot: slot
Token Description
ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVT-
UNXPCTD-CRU-CNF (1032).
ZDSC-TKN-GROUP Group to which the unknown CRU belonged. Value is
ZDSC-TNM-GROUP.
ZDSC-TKN-MODULE Module to which the unknown CRU belonged. Value is
ZDSC-TNM-MODULE.
ZDSC-TKN-SLOT Slot to which the unknown CRU belonged. Value is ZDSC-
TNM-SLOT.