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

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-13
Descriptions of Pathsend Errors
930
Cause. A call to SERVERCLASS_DIALOG_SEND_,
SERVERCLASS_DIALOG_END_, or SERVERCLASS_DIALOG_ABORT_ was done
under a different transaction identifier than the previous call to
SERVERCLASS_DIALOG_BEGIN_ (which had specified flags.<14> = 0). This is
a programming error.
Typical file-system error: 0 (FEOK)
Effect. The operation fails with an error.
Recovery. Use RESUMETRANSACTION to make the correct transaction identifier
current, and reissue the call that failed.
931
Cause. A call to SERVERCLASS_DIALOG_SEND_ failed because the server had
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 the following:
•
The dialog has been aborted.
•
The previous call to SERVERCLASS_DIALOG_BEGIN_ or
SERVERCLASS_DIALOG_SEND_ failed with an error that indicated an abort,
but the requester has not yet aborted the dialog.
Effect. The procedure initiation fails with an error.
Recovery. None. Use SERVERCLASS_DIALOG_END_ to end the specified dialog or
SERVERCLASS_DIALOG_ABORT_ to abort it.
933
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.
FEScChangedTransid
FEScDialogEnded
FEScDialogOutstanding