HP NSARPA/1000 Entity: OUTPRO

Entity: OUTPRO

The following codes are printed to the Location field of the log record header when the event class is Warning (Class 3), Error (Class 4), Disaster (Class 5), or RsrceLim (Class 6), and the Entity printed to the Entity field is OUTPRO.

Location	Meaning	Action
1	OUTPRO was unable to	No action is necessary unless
	dequeue an outgoing message	enough messages are dropped
	from its socket in order to pass it	in this way to impact system
	on the transport protocol	functions. If this is the case, a
	handler concerned. The xx field	shutdown and restart of
	of the log record header	NSARPA may clear the
	contains the global socket	problem. If it does not, this error
	descriptor of the socket that	requires HP notification.
	encountered the problem and
	the yy field contains the error
	number indicating the problem
	that prevented dequeueing of
	the message. This is an
	NSARPA internal error.
2	OUTPRO received a signal	This error requires HP
	indicating that a call socket had	notification.
	a control message on it, and yet
	the socket was not in a state
	that permitted these messages.
	The xx field of the log record
	header contains the global
	socket descriptor of the socket
	that encountered the problem
	and the yy field contains the
	state (so_b.state) the socket
	was in. This is an NSARPA
	internal error.
3	OUTPRO received a signal	This error requires HP
	indicating that a call socket had	notification.
	an exception message on it, and
	yet the socket was not in a state
	that permitted these messages.
	The xx field of the log record
	header contains the global
	socket descriptor of the socket
	that encountered the problem
	and the yy field contains the
	state (so_b.state) the socket
	was in. This is an NSARPA
	internal error.
4	OUTPRO received a signal	This error requires HP
	indicating that a call socket had	notification.
	some undefined message on it.
	The xx field of the log record
	header contains the global
	socket descriptor of the socket
	that encountered the problem.
	This is an NSARPA internal
	error.

Logging Codes and Messages 649