TS/MP 2.5 Pathsend and Server Programming Manual

Effect. The operation fails with an error.
Recovery. Use RESUMETRANSACTION to make the correct transaction identifier current, and
reissue the call that failed.
931
FEScDialogEnded
Cause. A call to SERVERCLASS_DIALOG_SEND_ failed because the server has already ended the
dialog, either by replying with FEOK or FEEOF or by terminating while a send was still outstanding.
Typical file-system error: the file-system error of the last server response. Any number other than 0
(FEOK) indicates one of these:
• The dialog is aborted.
• The previous call to SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_
failed with an error that indicated an abort, but the requestor has not yet aborted the dialog.
Effect. The procedure initiation fails with an error.
Recovery. Use SERVERCLASS_DIALOG_END_ to end the specified dialog or
SERVERCLASS_DIALOG_ABORT_ to abort it.
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. Have the server end the dialog by replying FEOK, or use
SERVERCLASS_DIALOG_ABORT_ to abort the dialog.
934
FEScTransactionAborted
Cause. The transaction associated with The dialog is aborted.
Typical file-system error: 0 (FEOK).
Effect. The procedure initiation fails with an error. The dialog is now aborted.
Recovery. Use SERVERCLASS_DIALOG_END_ or SERVERCLASS_DIALOG_ABORT_ to terminate
the portion of the dialog of the requestor.
947
FEScLinkmonConnect
Cause. A communication problem exists with the LINKMON process in this processor.
Typical file-system errors: 14 (FENOSUCHDEV) and 43 (FENODISCSPACE).
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 ACS Subsystem ROUT process executing in the
processor.
124 Pathsend Errors