NET/MASTER Messages Manual

NNM2301
Messages
106159 Tandem Computers Incorporated 2–405
NNM2209 OCS MESSAGES LOST
Cause. Messages were inserted into the OCS message flow when the size of the
internal OCS waiting queue was exhausted. This may happen if OCS scrolling is
disabled for a long time, either because of HOLD or AUTOHOLD, or because a panel
has taken over OCS. When the queue becomes full, the earliest messages are lost.
The size of the OCS internal queue is set by the HELDMSG system parameter and the
PROFILE HOLD command.
A nonzero integer value of the LMSGWARN system parameter defines the frequency
of this warning message. For example, if LMSGWARN=10, then the message is issued
for every tenth message lost. If LMSGWARN=0, then the message is issued each time
messages start to be lost.
Effect. The earliest messages in the OCS queue are lost.
Recovery. If necessary, enable scrolling so that the messages are displayed instead of
being held in the OCS queue. You can use Log Browse to retrieve the lost messages.
NNM2300 NCL nclid NOW WRITING TO LOG
Cause. A DEBUG LOG command was issued, and the NCL process specified by
nclid started logging messages.
Effect. The NCL process now logs debug messages.
Recovery. This message is informational only; no recovery action is necessary.
NNM2301 NCL nclid NOW NOT WRITING TO LOG
Cause. A DEBUG NOLOG command was issued, and the NCL process specified by
nclid stopped logging messages.
Effect. The NCL process is not logging any debug messages.
Recovery. This message is informational only; no recovery action is necessary.