TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

904: FEScServerLinkConnect
Cause. An error has occurred with the link to the server. For example, an open operation has failed
or there is an I/O problem. This error could occur on a call to SERVERCLASS_SEND_,
SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_.
Typical file-system errors: 14, 40, 48, 201, or one of the path errors between 240 and 255.
Effect. The call is completed with an error. The message might or might not have been sent to the
server process, depending upon the file-system error.
If the file-system error is a path error, any transaction associated with the call is aborted.
If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_,
the dialog is ended on the server side.
Recovery. If this error is returned from SERVERCLASS_SEND_, recovery depends on the file-system
error:
• Error 14 (FENoSuchDev) indicates that the server process does not exist. Retry the
SERVERCLASS_SEND_ call to cause the ACS subsystem process broker to use a different link
to the server process or to receive additional links from the PATHMON process. The success
of the retry depends on why the server process stopped.
• Error 40 (FETimedout) indicates that the I/O to the server process timed out because it exceeded
the configured SERVER TIMEOUT value for the server class.
• Error 48 (FESecViol) indicates there was a security violation.
• Error 201 (FEPathDown) or error 240 through 255 indicates that a path error occurred (for
example, the processor where the server process was running has failed).
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.
122 Pathsend Errors for ACS Subsystem