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-64
Messages
201: ZCMP-EVT-COMPLEX-INVALID-1
A NonStop Blade Complex is invalid because PEs with the same NonStop Blade
Element tracking ID have different NonStop Blade Element IDs. (This event can be
generated for each NonStop Blade Element 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
ZCPU-TKN-SLICE-TRACKING-ID <1> token-type ZSPI-TYP-
STRING
ZCMP-TKN-SLICE-ARRAY.CPU(0) <11> token-type ZSPI-TYP-INT
ZCMP-TKN-SLICE-ARRAY.LID(0) <12> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.SLICEID(0) <13> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.CPU(1) <21> token-type ZSPI-TYP-INT
ZCMP-TKN-SLICE-ARRAY.LID(1) <22> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.SLICEID(1) <23> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.CPU(2) <26> token-type ZSPI-TYP-INT
ZCMP-TKN-SLICE-ARRAY.LID(2) <27> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.SLICEID(2) <28> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.CPU(3) <31> token-type ZSPI-TYP-INT
ZCMP-TKN-SLICE-ARRAY.LID(3) <32> token-type ZSPI-TYP-BYTE
ZCMP-TKN-SLICE-ARRAY.SLICEID(3) <33> token-type ZSPI-TYP-BYTE
Token Interpretations
ZCMP-TKN-SLICE-ARRAY.NUMLIDS > 1 <20>
ZCMP-TKN-SLICE-ARRAY.NUMLIDS > 2 <25>
ZCMP-TKN-SLICE-ARRAY.NUMLIDS > 3 <30>
Event-Message Text
All PEs on a slice are not reporting the same slice ID
Slice module tracking ID : <1>
CPU : <11>, LID : <12>, Slice ID : <13>
< IF 20 > CPU : <21>, LID : <22>, Slice ID : <23><*ENDIF>
< IF 25 > CPU : <26>, LID : <27>, Slice ID : <28><*ENDIF>
< IF 30 > CPU : <31>, LID : <32>, Slice ID : <33><*ENDIF>