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

FEScOutstandingSend
Cause. The requester has an outstanding send operation on this dialog. This error can occur on
a call to SERVERCLASS_DIALOG_SEND_.
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 might 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.
Typical file-system error: 0 (FEOK).
Effect. The send initiation fails with an error.
Recovery. Complete the current send before starting another.
If ACS subsystem processes have failed, stop the Pathsend requesters, then restart the ACS
subsystem processes, then start the Pathsend requesters.
929
FEScDialogAborted
Cause. The dialog was aborted because the server requested a dialog abort.
Typical file-system error: if the server requested the abort, 1 (FEEOF); if the server terminated,
the file-system error returned by the ROUT process.
Effect. The dialog is aborted. If flags.<14> was not set to 1 on the call to
SERVERCLASS_DIALOG_BEGIN_, the transaction is also aborted. The procedure (if waited)
or AWAITIOX (if nowait) returns with an error.
Recovery. Use SERVERCLASS_DIALOG_END_ to terminate the requester's portion of the
dialog.
930
FEScChangedTransid
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).