TS/MP 2.5 Pathsend and Server Programming Manual

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 NonStop TS/MP 2.5 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.
Recovery. Correct the PATHMON name syntax. See chapter 5, “Pathsend Procedure Call Reference”
(page 74), for details about the correct syntax for PATHMON process names.
902
FEScPathmonConnect
Cause. An error has occurred in the communication of the requestor with the PATHMON process.
For example, an open operation has failed, an I/O error has occurred, or the PATHMON process
has failed.
Typical file-system errors: 12, 14, 40, 48, 201, or one of the path errors between 240 and 255.
Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an
error. The message is not sent to the server process.
Recovery. Recovery depends on the file-system error:
• Error 12 (FEInUse) indicates that the PATHMON process is unable to open the ACS Subsystem
ROUT process. Specific causes of this situation include (but are not limited to):
◦ The maximum number of ACS Subsystem ROUT processes that the PATHMON process
can communicate with has exceeded. See the NonStop TS/MP 2.5 System Management
Manual for information about setting the MAXLINKMONS parameter.
◦ The remote password on the system where the SERVERCLASS_SEND_ request originated
is not set for the system where the server-class is running. The PATHMON process receives
a file-system error 48 but converts this error into a file-system error 12. To recover, ensure
that all remote passwords are properly set, as described in the Expand Network
Management Guide.
• Error 14 (FENoSuchDev) indicates the PATHMON process does not exist. Start the PATHMON
process or use an existing PATHMON process.
• Error 40 (FETimeout) indicates that a timeout error occurred, possibly because a server was
in debug mode. See “Considerations for Debugging Pathway Servers” (page 68) in chapter
4 for more information about timeout errors for servers in debug mode.
116 Pathsend Errors