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

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-11
Descriptions of Pathsend Errors
924
Cause. The maximum number of concurrent server-class send operations allowed has
been exceeded. The maximum number is 255 per requester and 512 for all requesters
running in a processor. This error can occur on a call to SERVERCLASS_SEND_,
SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_.
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 on the design and operating environment of your application.
For more information about LINKMON limits, refer to LINKMON Limit Errors
on
page 3-4 and also to the NonStop TS/MP System Management Manual.
925
Cause. The LINKMON process is already communicating with the maximum number
of requesters allowed. The maximum number of concurrently active Pathsend
requesters per processor is 256. This error can occur only on the requester’s first call to
SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_.
Typical file-system error: 0 (FEOK)
Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is
completed with an error. The message is not sent to the server process.
Recovery. Retry if the number of Pathsend requesters fluctuates in this processor.
926
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.
FEScTooManySendRequests
FEScTooManyRequesters
FEScDialogInvalid