TS/MP Pathsend and Server Programming Manual (G06.24+, H06.03+)

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-8
Descriptions of Pathsend Errors
If a server process is in debug mode and a timeout error (file-system error 40) occurred,
do the following:
•
Use the PATHCOM STATUS PATHMON command to find the server classes that
are 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 by using the TACL STOP command.
For more information about timeout errors for servers in debug mode, refer to
Considerations for Debugging Pathway Servers
in Section 4.
916
Cause. The LINKMON process was unable to get a link to the server class due to a
server creation failure. This is usually a server-class configuration problem, or a server
might have a problem that causes it to fail.
Typical file-system error: 0 (FEOK)
Effect. The send initiation fails with an error.
Recovery. Verify that the server class has been configured correctly. If the problem is
not in the configuration, correct the error in the server.
917
Cause. The transaction mode of the Pathsend program does not match that of the server
class. The process has a current transaction ID at the time of the send, and the server
class is configured with the TMF parameter set to OFF. This is a programming error or
a server-class configuration error.
Typical file-system error: 0 (FEOK)
Effect. The call is completed with an error. The message is not sent to the server class.
Recovery. Correct your program or change the server-class configuration setting to
TMF ON.
FEScServerCreationFailure
FEScServerClassTmfViolation