Location | Meaning | Action |
|
|
|
INPRO received an error | No action is necessary because | |
| indication in the DVT status | the HP protocols can retransmit |
| word returned along with the | lost messages. However, if |
| write completion of a Class I/O | enough messages are dropped |
| request. The xx field of the log | in this way so that network |
| record header contains the error | functioning is impaired, a |
| code field from the DVT status | shutdown and restart of |
| word and the yy field contains | NSARPA, or a reboot of the |
| the entire DVT status word. This | system, may be necessary to |
| is an NSARPA internal error. | clear the condition. If these |
|
| actions do not solve the |
|
| problem, notify your HP field |
|
| office. |
|
|
|
INPRO was unable to allocate | If too many messages are lost in | |
| space in DSAM for an incoming | this way, more space should be |
| message. If the transport is | allocated for DSAM at |
| TCP, HPPXP, or the DS/1000IV | initialization time. |
| Compatible Services transport |
|
| with Message Accounting, the |
|
| message will be retransmitted |
|
| and will probably be accepted. |
|
| A Memory Manager error code |
|
| is printed in xx field of the log |
|
| record header. |
|
|
|
|
INPRO tried to requeue a | If this problem repeats, shutting | |
| message to the message tracing | down tracing with BRTRC and |
| program, NSTRC, or to the | then restarting NSTRC may |
| interface protocol monitor, IFPM, | correct it. If not, this error |
| but the class number used was | requires HP notification. |
| rejected by the Class I/O |
|
| system. The xx field of the log |
|
| record header contains the class |
|
| number and the yy field |
|
| contains the error indication |
|
| from REQUE. This is an |
|
| NSARPA internal error. |
|
|
|
|
INPRO received a message | Verify that all software is of the | |
| which appeared to be from a | same revision. Especially check |
| link type not supported by | revisions of datacomm drivers |
| NSARPA/1000. May represent | and the NSARPA/1000 code |
| data corruption in SAM, or | appended to INPRO (check load |
| mismatched version of INPRO | map). You may check the |
| and one of the drivers. INPRO | update time stamps on |
| dropped the affected message. | nssys_cds.lib, |
| The xx field of the log record | nslib_cds.lib, inpro.rel |
| header contains the link type | and the relocatable for the driver |
| code from the message. The | affected. If all software is same |
| log message contains the event | revision, the problem may be |
| message that INPRO would | corruption in SAM or in the |
| have sent to the link interface. | driver. Reboot. If versions |
| The first word is meaningless. | match and rebooting does not |
|
| solve the problem, this log is an |
|
| internal error and requires HP |
|
| notification. |
|
|
|
648 Logging Codes and Messages