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

6 Pathsend Errors
This section describes the error codes that can be returned by the 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 NonStop Tuxedo system.
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” (page 75).
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 section. 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 section in the descriptions of the associated Pathsend errors.
Descriptions of Pathsend Errors
The Pathsend error codes are described in numeric order on these pages. Each description includes:
• 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
These errors can be returned to Pathsend requesters. They can also be returned to NonStop Tuxedo
clients that invoke NonStop Tuxedo request and response services or conversational services. When
Pathsend errors are returned to a NonStop Tuxedo client, the necessary recovery actions might
differ from those listed here; for information about recovery from errors in the NonStop Tuxedo
environment, refer to the NonStop TUXEDO System Messages Manual.
For examples of how errors are returned to a Pathsend program, refer to the example programs
in “Examples” (page 129). The error literals that follow the error numbers— for example, 233
(FEScError)—are used in the example programs.
You can recover from some errors by retrying the Pathsend procedure call; the errors you should
retry depend on the requirements of your application. The programming examples in “Examples”
(page 129), illustrate retrying the call for certain errors. You can use those examples and the error
descriptions in this section to decide how to program for retrying errors.
Types of Errors Returned by the Pathsend Procedures 109