Chapter 54 MSGSYS Messages

The messages in this chapter are sent by the message subsystem. The subsystem ID displayed by these messages includes MSGSYS as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

100

External Receiver Link Control Block Allocation Failure, Cluster cluster, CPU cpu, PIN pin

`cluster`	is the receiving cluster.
`cpu`	identifies the receiving processor.
`pin`	is the process ID.

Cause The system could not allocate the link control block (LCB) for the receiver of a message over the Fiber Optic Extension (FOX) interprocessor bus. The message is issued at the sending cluster.

Effect The message transfer fails.

Recovery Run SYSGEN again to allocate more LCBs, or redistribute the applications among the processors.

101

Link Control Block Allocation Wait Warning, CPU cpu

Cause Processes are awaiting allocation of link control blocks (LCBs) or extended link control blocks (LCBXs) on the specified processor.

Effect The system reports the problem and continues processing.

Recovery Informational message only; no corrective action is needed unless related messages appear.

102

Link Control Block Shortage Warning, CPU cpu, PIN pin

Cause Less than 10 percent of the configured link control blocks (LCBs) remain unallocated on the specified processor for the specified PIN.

Effect The system reports the situation and continues processing.

Recovery Informational message only; no corrective action is needed unless other related messages appear.

103

Local Receiver Link Control Block Allocation Failure, CPU cpu, PIN pin

Cause The system could not allocate the link control block (LCB) for the specified PIN on the specified processor. The receiving processor issues the message.

Effect The message is not sent. The system reports the problem and continues processing.

Recovery If this message appears frequently, configure additional LCBs into the system or redistribute the processes among the processors.

If adding LCBs to the system does not solve the problem, thoroughly examine how the application message is used to determine how to solve the problem.

104

Receive Queue for CPU cpu, PIN pin Greater Than 10 LCBs

Cause The specified PIN on the specified processor accumulated 11 messages on $RECEIVE. This message appears when:

The process hasn't performed a READ or READUPDATE operation for the accumulated messages.
The process hasn't suppressed this message through a call to CONTROLMESSAGESYSTEM.

Effect The system reports the problem and continues processing.

Recovery This is a warning message that indicates that either the process is unable to keep pace with incoming requests or is not reading its $RECEIVE queue. Contact the application programmer.

Some application designs may warrant having more than 10 messages on the $RECEIVE queue. The application process can suppress this message by calling CONTROLMESSAGESYSTEM with an action code value of 2.

105

Sender Link Control Block Allocation Failure, CPU cpu, PIN pin

Cause The system could not allocate the link control block (LCB) or an extended link control block (LCBX) for the specified PIN on the specified processor.

Effect The message is not sent. The system reports the problem and continues processing.

Recovery Use the PEEK utility to determine if the problem is caused by an LCB shortage. If it is, run SYSGEN again to allocate more LCBs, or redistribute the applications among the processors.

If the problem is not caused by an LCB shortage, then check for a time-limit element (TLE) shortage. (LCBXs are allocated from the pool of TLEs.) If there is a TLE shortage, run SYSGEN again to allocate more TLEs, or redistribute applications among the processors.

If these steps fail, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

106

SENDVIAMESSENGER Error, CPU cpu, PIN pin

Cause The input/output the specified PIN on the specified processor made an improper call to the privileged procedure SENDVIAMESSANGER.

Effect The improper call is ignored.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.