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

Pathsend Errors
NonStop TS/MP Pathsend and Server Programming Manual–132500
6-3
Descriptions of Pathsend Errors
902
Cause. An error has occurred in the requester’s communication 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 was unable to open the
LINKMON process. Specific causes of this situation include (but are not limited to)
the following:
•
The maximum number of LINKMON processes that the PATHMON process
can communicate with has been exceeded. See the NonStop TS/MP System
Management Manual for information about setting the MAXLINKMONS
parameter.
•
The remote password on the system where the SERVERCLASS_SEND_
request originated was not set for the system where the server class was 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
in
Section 4 for more information about timeout errors for servers in debug mode.
•
Error 48 (FESecViol) indicates there was a security violation. See Section 3, Writing
Pathsend Requesters, for information about network and server-class security.
•
Error 201 (FEPathDown) or error 240 through 255 indicates that a path error
occurred (for example, the PATHMON process failed). Restart the PATHMON
process.
FEScPathmonConnect