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

933: FEScDialogOutstanding
Cause. A call to SERVERCLASS_DIALOG_END_ was made, but the server has not ended the dialog.
Typical file-system error: 0 (FEOK).
Effect. The procedure initiation fails with an error.
Recovery. Reply FEOK to cause the server to end the dialog or use SERVERCLASS_DIALOG_ABORT_
to abort the dialog.
934: FEScTransactionAborted
Cause. The transaction associated with the dialog was aborted.
Typical file-system error: 0 (FEOK).
Effect. The procedure initiation fails with an error. The dialog is aborted.
Recovery. Use SERVERCLASS_DIALOG_END_ or SERVERCLASS_DIALOG_ABORT_ to terminate
the requester's portion of the dialog.
947: FEScRoutConnect
Cause. There is a problem communicating with the ROUT process in this processor.
Typical file-system errors: 14 (FENoSuchDev), 30 (FENOLCB), and 201 (FEPATHDOWN).
Effect. The send initiation fails with an error.
Recovery. Recovery depends on the file-system error.
File-system error 14 indicates that there is no ROUT process executing in the processor.
File-system error 30 indicates that the ROUT message queue is full. Retry the send; the status of the
ROUT message queue continually changes.
File-system error 201 indicates that the ROUT process has failed. The ACS subsystem will
automatically restart all the core processes on that processor. If you need to contact your support
organization, collect the ABEND files for the ACS subsystem redirector, configuration subscriber,
and process broker processes.
960: FEScProtocolConflict
Cause. The send operation protocol is invalid on the link to the selected server process due to an
internal failure.
Effect. The operation is not performed.
Recovery. None; contact your HP analyst.
963: FEScNonPathsend
Cause. The server process is not accepting Pathsend messages due to an internal failure.
Effect. The operation is not performed.
Recovery. None; contact your HP analyst.
Descriptions of Pathsend Errors 127