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

Guardian Procedures Errors and Messages Manual; however, specific Pathsend considerations
for some of the file-system errors are given in this chapter in the descriptions of the associated
Pathsend errors.
Descriptions of Pathsend Errors
The Pathsend error codes are described in numeric order. Each description includes the
following:
The error number and corresponding error literal●
The cause of the error●
Typical file-system errors that can be encountered with the Pathsend error●
The effect of the error●
How to recover from the error●
You can recover from some errors by retrying the Pathsend procedure call; the errors you
should retry depend on the requirements of your application.
900
FEScInvalidServerClassName
Cause. The server-class name specified in a call to SERVERCLASS_SEND_ or
SERVERCLASS_DIALOG_BEGIN_ is not syntactically correct. This is a programming error.
Typical file-system error: 2 (FEInvalOp)
Effect. The send initiation fails with an error.
Recovery. Correct the server-class name syntax. See the TS/MP System Management Manual
for a description of the correct syntax for server-class names.
901
FEScInvalidPathmonName
Cause. The PATHMON process name specified in a call to SERVERCLASS_SEND_ or
SERVERCLASS_DIALOG_BEGIN_ is not syntactically correct. This name must be a valid
external process name. This is a programming error.
Typical file-system error: 2 (FEInvalOp).
Effect. The send initiation fails with an error.