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

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-9
Descriptions of Pathsend Errors
918
Cause. The send operation has been terminated at an indeterminate point.
Typical file-system error: 40 (FETimedOut)
Effect. The send fails. A message might or might not have been sent to the server
process, depending on when the send was aborted.
Recovery. The recovery action depends on which file-system error has occurred. With
error 40 (FETimedOut), you might want to try a larger timeout value.
919
Cause. The caller supplied an invalid timeout value in a call to
SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, or
SERVERCLASS_DIALOG_SEND_. This is a programming error.
Typical file-system error: 2 (FEInvalOp)
Effect. The send initiation fails with an error.
Recovery. Specify a valid timeout value. See the procedure call syntax description for
details about valid timeout values.
920
Cause. The caller’s process file segment (PFS) could not be accessed.
Typical file-system error: 31 (FENoBufSpace)
Effect. The send initiation fails with an error.
Recovery. Code the process to stop itself if this error occurs.
921
Cause. A call to SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_
specifies a PATHMON process not known to the LINKMON process, and the
LINKMON process is already communicating with the maximum number of
PATHMON processes allowed. The maximum number is 256.
Typical file-system error: 0 (FEOK)
FEScSendOperationAborted
FEScInvalidTimeoutValue
FEScPFSUseError
FEScTooManyPathmons