TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

915: FEScPathmonShutDown
Cause. The send operation has been denied for one of these reasons:
• The PATHMON process for the server class is shutting down.
• A timeout occurred on an I/O operation to a server in debug mode.
Typical file-system error: 0 (FEOK).
Effect. The SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, or
SERVERCLASS_DIALOG_SEND_ call is completed with an error. The message is not sent to the
server class.
Recovery. If the PATHMON process is shutting down, determine the reasons for the shutdown and
perform appropriate recovery actions.
• If a server process is in debug mode and a timeout error (file-system error 40) occurred:
• 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.
• Use the TACL STOP command to stop these processes.
For more information about timeout errors for servers in debug mode, refer to Considerations for
Debugging pathway Servers in Section 4 of the TS/MP Pathsend and Server Programming Manual.
916: FEScServerCreationFailure
Cause. The ACS subsystem process broker 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: FEScServerClassTmfViolation
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.
918: FEScSendOperationAborted
Cause. The send operation was terminated at an indeterminate point.
Typical file-system error: 40 (FETimedOut).
Effect. The send fails. A message might or might not have been sent to the server process, depending
on when the send was aborted.
Recovery. The recovery action depends on which file-system error occurred. If error 40 (FETimedOut)
occurred, you might want to try a larger timeout value.
124 Pathsend Errors for ACS Subsystem