Location | Meaning | Action |
|
|
|
9 | OUTPRO received a signal | This error requires HP |
| indicating that a VC socket had | notification. |
| data on it, but the socket was |
|
| not in a state that permitted that |
|
| kind of signal. The signal was |
|
| ignored. 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 socket_b.state |
|
| field of the socket. This is an |
|
| NSARPA internal error. |
|
|
|
|
10 | OUTPRO received a signal | This error requires HP |
| indicating that a VC socket had | notification. |
| an undefined signal on it. The |
|
| signal was ignored. The xx field |
|
| of the log record header |
|
| contains the global socket |
|
| descriptor of the socket that |
|
| encountered the error and the |
|
| yy field contains the |
|
| socket_b.state field of the |
|
| socket. This is an NSARPA |
|
| internal error. |
|
|
|
|
11 | OUTPRO was unable to | This error requires HP |
| dequeue outbound | notification. |
| connectionless data for |
|
| transmission. The message |
|
| affected was lost. However, if |
|
| the message was for a |
|
| DS/1000IV Compatible Service, |
|
| Message Accounting will |
|
| probably retransmit it. 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 |
|
| socket_b.state field of the |
|
| socket. This is an NSARPA |
|
| internal error. |
|
|
|
|
Logging Codes and Messages 651