Pathway/iTS System Management Manual (H06.03, J06.03+)

TCP Messages (Numbers 3000-3999)
HP NonStop Pathway/iTS System Management Manual—426748-005
13-57
TCP Messages
3248
Cause. A retryable LINKMON connect error occurred on primary CPU of the TCP. The
associated file error gives the file-system error occurred with the LINKMON process.
Typical file-system errors are 100 (FENOTRDY), 28(FETOOMANY) and 30
(FENOLCB). Here are the possible causes for this error.
•
The LINKMON process on the CPU is just started and is not yet initialized (Error
#100).
•
More than 255 sends are being attempted by the same TCP process (Error #28).
•
More than 4K sends are being attempted on the same CPU (Error #30).
Effect. The operation fails. If ON ERROR clause is mentioned, then error is reported
against the term but the term continues to run depending on the error-handling logic in
the SCREEN COBOL program. If ON ERROR clause is not mentioned, then TCP
suspends the terminal after logging the error against the term; however, the term can
be resumed to restart processing at the last verb.
Recovery. If the associated file-system error is 100 then it means that the LINKMON
process is just started on the CPU and is not yet ready to accept the Pathsend
requests. The term should retry the operation after a time delay. If associated file-
system error is 30, then it means that the outstanding incoming requests to the
LINKMON process have been reached. This is also a transient error and the term
should retry the operation.
3249
Cause. TCP abended while a SEND or a DIALOG I/O to server process was
outstanding and the term was not under transaction.
Effect. The operation fails. The server might or might not have received the message.
If ON ERROR clause is mentioned, then error is reported against the term but the term
continues to run depending on the error-handling logic in the SCREEN COBOL
*3248* A RETRYABLE LINKMON CONNECT ERROR OCCURRED (errnum)
Note. This error does not appear in the RETCODE token or in an error list; it appears
only in response to the STATUS TCP or STATUS TERM command.
*3249* TCP FAILED WHEN A SEND/DIALOG TO SERVER WAS
OUTSTANDING
Note. This error does not appear in the RETCODE token or in an error list; it appears
only in response to the STATUS TCP or STATUS TERM command.