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

7 Pathsend Errors for ACS Subsystem
This chapter describes the error codes that can be returned by the TS/MP Pathsend procedure
calls. These errors can be returned by processes that call the Pathsend procedures directly and
also by software that uses these procedures internally, such as the ACS subsystem.
Types of Errors Returned by the Pathsend Procedures
Three errors are associated with each call to a Pathsend procedure (except
SERVERCLASS_SEND_INFO_):
• A return error
• A Pathsend error
• A file-system error
The return error is the error returned by the Pathsend procedure or by AWAITIOX. For details about
the return errors for a particular procedure call, see the error parameter in the syntax description
for that call in Section 5, Pathsend Procedure Call Reference, in the TS/MP Pathsend and Server
Programming Manual.
For waited send operations, the return error is returned from the Pathsend procedure call.
For nowait send operations, the return error is returned from the Pathsend procedure call if it is a
send-initiation error. For errors other than send-initiation errors, the return error is returned by the
AWAITIOX procedure and can be retrieved by calling the FILEINFO procedure.
If the return error is error 233 (FEScError), you can call SERVERCLASS_SEND_INFO_ to retrieve
the Pathsend error and the file-system error. (If the return error is 0 (FEOK), both the Pathsend error
and the file-system error are always 0, so you do not need to call SERVERCLASS_SEND_INFO_.)
The Pathsend errors are described in this chapter. The file-system errors are described in the
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 these:
• 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.
120 Pathsend Errors for ACS Subsystem