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

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-5
Descriptions of Pathsend Errors
•
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
Cause. The LINKMON process had no links to the server class and was unable to get a
link from the PATHMON process to satisfy this request. For example, MAXLINKS
links for each server class are already allocated to other LINKMON processes and
TCPs. This is a PATHMON configuration problem.
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. 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 NonStop TS/MP System
Management Manual.
906
Cause. The SERVERCLASS_SEND_INFO_ procedure was called before
SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ was ever 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_.
FEScNoServerLinkAvailable
FEScNoSendEverCalled
Note. Error 907, FEScInvalidSegmentId, and error 908, FEScNoSegmentInUse, are not
returned on D-series systems. Error 908 has been replaced by error 912,
FEScParameterBoundsError.