Pathway/XM System Management Manual

PXMCOM, PB, and LCS Messages
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
13-3
LCS Messages (Messages 6000-6199)
LCS Messages (Messages 6000-6199)
The following messages are generated by LCS processes.
6000
Cause. The LCS process stopped or terminated abnormally due to the condition
specified in the message. If the LCS process terminated abnormally (abended), the most
likely cause is an internal program error.
If the LCS process stopped, the most likely cause is a condition external to the LCS
process, identified in the message. The fields have the following meaning:
*6000* LCS termination c: error-class, f: function,
ID: error-condition, Detail: error-detail
When the Values of
error-class and
function are…
And the value of
error-
condition is… The Error is Caused by…
c: ActionManager
f: execute
3
23
9, 11, 13, or 16
10, 12, 14, 17,
19, or 30
18
25
Cannot connect to the PB
Communication to the PB is lost
Error in reply to requester
Error in executing READUPDATE on
$RECEIVE
Error in a reply to a system message
Error in resetting the transaction ID
c: ActionManager
f: execLCS
1 Error in reply to LCS command requester
c: CMON
f: comReq
1 Lost communication with $CMON
c: Config
f: process_startup_
sequence
1
2
Node name missing during LCS startup
Server class name missing LCS startup
c: Config
f: updateFromDB
1
2
3
4
Super Control object failure
Open error on SuperCTL file
Error retrieving node date
Error retrieving server class data
c: Config
f: update
2
3
5
Error in IN file name. Possible
configuration error.
Error in OUT file name. Possible
configuration error.
Error in PARAM definition. Value of
parameter missing.
c: Config
f: volume-name
1 Error in volume volume-name. Possible
configuration error. (error-detail
contains the length of the name.)