TS/MP 2.5 Pathsend and Server Programming Manual

This error can also occur when the ACS subsystem processes in a CPU fail and the Pathsend
requestors on that CPU continue running. When ACS subsystem processes fail, the Pathsend
requestors in the CPU does not terminate automatically. Therefore, some of the requestors might
be in an inconsistent state and might 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 requestors, then restart the ACS subsystem
processes and then start the Pathsend requestors.
929: FEScDialogAborted
Cause. The dialog is 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> is 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 portion of the dialog of the requestor.
930: FEScChangedTransid
Cause. A call to SERVERCLASS_DIALOG_SEND_, SERVERCLASS_DIALOG_END_, or
SERVERCLASS_DIALOG_ABORT_ is 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: 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.
This error can also occur when the ACS subsystem processes in a CPU fail and the Pathsend
requestors on that CPU continue running. When ACS subsystem processes fail, the Pathsend
requestors in the CPU do not terminate automatically. Therefore, some of the requestors might be
in an inconsistent state and might 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 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. 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 requestors, then restart the ACS subsystem
processes and then start the Pathsend requestors.
132 Pathsend Errors for ACS Subsystem