TS/MP 2.5 Pathsend and Server Programming Manual

• Error 48 (FESecViol) indicates there is a security violation. For information about network and
server-class security, see chapter 3, “Writing Pathsend Requestors” (page 50),.
• 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
FEScPathmonMessage
Cause. The ACS Subsystem process broker (PB) received an unrecognizable message from the
PATHMON process while processing a SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_
request. You might be using incompatible versions of the ACS Subsystem PB and PATHMON
processes, or this could be a ACS Subsystem PB or PATHMON process internal error.
Typical file-system error: 0 (FEOK).
Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an
error. The message is not sent to the server process.
Recovery. This error is nonrecoverable.
904
FEScServerLinkConnect
Cause. An error has occurred with the link to the server. For example, an open operation has failed
or there is an I/O problem. This error could occur on a call to SERVERCLASS_SEND_,
SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_.
Typical file-system errors: 14, 40, 48, 201, or one of the path errors between 240 and 255.
Effect. The call is completed with an error. The message might have been sent to the server process,
depending on the file-system error.
If the file-system error is a path error, any transaction associated with the call is aborted.
If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_,
the dialog is ended on the server side.
Recovery. If this error is returned from SERVERCLASS_SEND_, recovery depends on the following
file-system errors:
• Error 14 (FENoSuchDev) indicates that the server process does not exist. Retry the
SERVERCLASS_SEND_ to cause the ACS Subsystem ROUT process to use a different link to
the server process or to receive additional links from the PATHMON process. The success of
the retry depends on why the server process stopped.
• Error 40 (FETimedout) indicates that the I/O to the server process timed out because it exceeded
the configured SERVER TIMEOUT value for the server-class.
• Error 48 (FESecViol) indicates there is a security violation. chapter 3, “Writing Pathsend
Requestors” (page 50), 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 processor where the server process is running has failed).
If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_,
use SERVERCLASS_DIALOG_END_ or SERVERCLASS_DIALOG_ABORT_ to terminate the portion
of the dialog of the requestor.
905
FEScNoServerLinkAvailable
Descriptions of Pathsend Errors 117