NonStop Operating System Event Management Programming Manual

Complex Manager Auxiliary Process (CMAP) Event
Messages (ZCMP)
HP NonStop Operating System Event Management Programming Manual—520372-020
25-68
Messages
Cause. Not all PEs that have the same NonStop Blade Element tracking ID are
connected to the same port on each LSU NonStop Blade Complex; therefore, the PEs’
node names and node numbers do not match.
Effect. The NonStop Blade Complex is invalid; therefore, CMAP cannot reintegrate its
PEs or reset its NonStop Blade Elements.
Recovery. Correct the PE/LSU cabling problem.
203: ZCMP-EVT-COMPLEX-INVALID-3
A NonStop Blade Complex is invalid because its CPUs have different NonStop Blade
Elements. (This event can be generated for each processor in the NonStop Blade
Complex.)
Potentially critical event: No
Action event: No
Message sender: CMAP
$ZLOG: Yes
$0: No
Unconditional Tokens
ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT
ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-
BOOLEAN
ZEMS-TKN-ISO-SEVERITY token-type ZSPI-TYP-ISO-
SEVERITY
ZCMP-TKN-COMPLEX-ID <1> token-type ZSPI-TYP-INT
ZCPU-TKN-CPU <2> token-type ZSPI-TYP-INT
ZCPU-TKN-LID <3> token-type ZSPI-TYP-BYTE
ZCMP-TKN-LSU-TRACKING-ID <4> token-type ZSPI-TYP-STRING
ZCMP-TKN-LSU-TRACKING-ID1 <5> token-type ZSPI-TYP-STRING
ZCPU-TKN-SLICEID token-type ZSPI-TYP-BYTE
ZCPU-TKN-SLICE-TRACKING-ID <7> token-type ZSPI-TYP-STRING
ZCPU-TKN-SLICEID1 token-type ZSPI-TYP-BYTE
ZCPU-TKN-SLICE-TRACKING-ID1 <12> token-type ZSPI-TYP-STRING
ZCPU-TKN-SLICEID2 token-type ZSPI-TYP-BYTE
ZCPU-TKN-SLICE-TRACKING-ID2 <22> token-type ZSPI-TYP-STRING
Token Interpretations
ZCMP-TKN-SLICEID1 <> %HFF <10>
ZCMP-TKN-SLICEID2 <> %HFF <20>