Pathway/iTS TCP and Terminal Programming Guide

Handling Errors
Compaq NonStop™ Pathway/iTS TCP and Terminal Programming Guide—426751-001
10-3
Responding to SEND Errors
Other causes, such as a security violation, could also result in error 4.
Error 12 could be caused by a timeout error (termination substatus 40) when a server is
in debug mode. If this situation occurs, the operator should do the following:
Use the PATHCOM STATUS PATHMON command to find server classes in the
LOCKED state.
Identify the server program file for each locked server class.
Issue the TACL command STATUS *, PROG object-file-name to list all running
processes.
Stop these processes from TACL.
For more information about timeout errors for servers in debug mode, refer to the
NonStop™ TS/MP Pathsend and Server Programming Manual.
The codes in Table 10-1
reflect programming errors that are essentially nonrecoverable.
These errors typically occur only during application debugging. After the application
modules have been thoroughly tested, these codes do not normally occur in a production
environment.
Note that for error code 10 no data is available, even though a reply message is received.
If your application cannot anticipate all valid reply codes, use the REPLY CODE
OTHER syntax in the SEND statement to prevent error code 10.
Upon detecting any of these error conditions, your ON ERROR code should send a
message to the terminal telling the operator what is happening (such as FATAL
CONFIGURATION PROBLEM, TERMINATING EXECUTION), log an error record
to an appropriate server, and then perform a STOP RUN statement.
The codes in Table 10-1
reflect configuration errors that are essentially nonrecoverable.
Table 10-2. Requester SEND Errors for Nonrecoverable Programming Problems
Numeric Value Meaning
5 Server class undefined
6 Invalid server-class name
10 Undefined reply code
15 Undefined system name
16 Invalid system name
17 Invalid PATHMON process name