TS/MP Supplement for Limits Relief (H06.05+, J06.03+)

Note: This error is no longer returned when the limit of concurrent send operations is
exceeded; instead error 947 (FEScRoutConnect) is returned with file-system error
30.
Typical file-system error: 0 (FEOK).
Effect. The call is completed with an error. The message is not sent to the server process.
Recovery. In some cases, you can recover from this error by retrying the call. Whether a retry
will work depends upon the design and operating environment of your application.
926
FEScDialogInvalid
Cause. The specified dialog identifier is not valid. This error can occur on a call to
SERVERCLASS_DIALOG_SEND_, SERVERCLASS_DIALOG_END_, or
SERVERCLASS_DIALOG_ABORT_.
Typical file-system error: 0 (FEOK).
Effect. The send initiation fails with an error.
Recovery. Use a valid dialog identifier.
927
FEScTooManyDialogs
Cause. The requester cannot start a new dialog because it already has the maximum number of
dialogs open. The maximum number of dialogs per requester is 255; the maximum number for
all requesters in a CPU is 4094. This error can occur on a call to
SERVERCLASS_DIALOG_BEGIN_.
Typical file-system error: 0 (FEOK).
Effect. The send initiation fails with an error.
Recovery. Reduce the number of dialogs.
928
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