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

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-2
Descriptions of Pathsend Errors
•
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/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 Appendix B, Examples
. 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 Appendix B, Examples
, 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.
900
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 NonStop TS/MP System
Management Manual for a description of the correct syntax for server-class names.
901
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.
Recovery. Correct the PATHMON name syntax. Refer to Section 5, Pathsend
Procedure Call Reference, for details about the correct syntax for PATHMON process
names.
FEScInvalidServerClassName
FEScInvalidPathmonName