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

If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or
SERVERCLASS_DIALOG_SEND_, use SERVERCLASS_DIALOG_END_ or
SERVERCLASS_DIALOG_ABORT_ to terminate the requester's portion of the dialog.
905
FEScNoServerLinkAvailable
Cause. The ACS subsystem process broker had no links to the server class and was unable to
get a link from a PATHMON process to satisfy this request. This is most likely caused by
PATHMON configuration problems.
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 the call; links are always being made available. Increase the maximum number
of servers in the server class (with the PATHCOM MAXSERVERS parameter) or increase the
number of links available to the server (with the PATHCOM MAXLINKS parameter). For
details about the MAXSERVERS and MAXLINKS parameters, see the TS/MP System
Management Manual.
906
FEScNoSendEverCalled
Cause. The SERVERCLASS_SEND_INFO_ procedure was called before
SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ was called by this program.
This is a programming error.
Typical file-system error: 0 (FEOK).
Effect. The SERVERCLASS_SEND_INFO_ call is completed with return error 0, Pathsend
error 906, and file-system error 0.
Recovery. Ensure that your application program does not call SERVERCLASS_SEND_INFO_
before it calls SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_.
Note: Error 907, FEScInvalidSegmentId, and error 908, FEScNoSegmentInUse, are not
returned on D-series systems. Error 908 has been replaced by error 912,
FEScParameterBoundsError.
909
FEScInvalidFlagsValue