TS/MP Supplement for Limits Relief (G06.26+)
Recovery. Correct the PATHMON name syntax. Refer to Section 5, Pathsend Procedure Call
Reference, in the TS/MP Pathsend and Server Programming Manual for details about the
correct syntax for PATHMON process names.
902
FEScPathmonConnect
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 upon the file-system error:
Error 12 (FEInUse) indicates that the PATHMON process was unable to open the ACS
subsystem process broker. Specific causes of this situation include (but are not limited to)
the following:
The maximum number of processes that the PATHMON process can communicate
with has been exceeded.
❍
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 of
the TS/MP Pathsend and Server Programming Manual 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, in the TS/MP Pathsend and Server Programming Manual 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.
●
903