RSC/MP Programming Manual

Message Handling

Error Types and Severity

The RSC.ERR file is searched each time the RscErrorInfo function is called.

Applications can use the return va lue from this function to recommend corrective

actions.

The return va lue (defined in the RSC.H file) is the result of the bitwise OR operation

between the error type and the error severity. If the result is zero, the operation

terminates successfully. If the result is nonzero, an error code appears.

These are the error types and their meanings:

Error Types Meaning

RSC_CONNECT_ERROR The communications subsystem that processed the request

reported the error. The connection being attempted or

currently in use was abnormally terminated.

RSC_IO_ERROR The NonStop subsystem that processed the request reported

the error. The attempted I/O operation was unsuccessful.

RSC_PROGRAM_ERROR An application programming error caused the error.

To identify the error type, the application performs a bitwise AND operation with the

RscErrorInfo return code and one of the error type DEFINEs:

RSC_CONNECT_ERROR

RSC_IO_ERROR

RSC_PROGRAM_ERROR

RSC_SESSION_ERROR

If the result of the AND operation is zero, the error is not of the type identified by the

error type define. The bitwise AND operation of the return code and the

RSC_UNCLASSIFIED_ERROR always returns a zero value. The

RSC_UNCLASSIFIED_ERROR DEFINE cannot be used in the same manner as other

error type DEFINEs.

These are the error severities and their corrective actions:

Error Types Corrective Action

RSC_ERROR_CONFIG A serious error occurred, caused by an RSC/MP

configuration problem. Modify the appropriate configuration

parameter.

RSC_ERROR_FATAL A connection or session was terminated abnormally.

Reconnect or begin a new session.

RSC_ERROR_RETRY An error occurred which might not occur again. Retry the

operation. If the operation continues to fail, it should be

considered fatal.

HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006

7- 4