TS/MP Supplement for Limits Relief (G06.26+)

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 had already
ended the dialog, either by replying with FEOK or FEEOF or by terminating while a send was
still outstanding.
This error can also occur when the ACS subsystem processes in a CPU fail and the Pathsend
requesters on that CPU continue running. When ACS subsystem processes fail, TSMP 2.1 does
not automatically terminate the Pathsend requesters in the CPU. Therefore, some of the
requesters may be in an inconsistent state and may continue to receive this error for
dialog-based send initiations. This can occur even after the ACS subsystem processes are
restarted on the CPU.
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.
If ACS subsystem processes have failed, stop the Pathsend requesters, then restart the ACS
subsystem processes, then start the Pathsend requesters.
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.