Exception Handling
Use
The following UML diagram shows all the exception classes that are automatically used by the new API if a problem or exception occurs. The exceptions must be caught by the application program to prevent the system for crashing.
The following table contains the possible causes of an exception:
Exception |
Cause |
CX_QRFC_DUPLICATE_LOCK |
Duplicate lock in background RFC |
CX_QRFC_DUPLICATE_QUEUE_NAME |
Duplicate queue name of a unit in qRFC |
CX_QRFC_INVALID_QUEUE_NAME |
Queue name is invalid |
CX_BGRFC_INVALID_DESTINATION |
Destination error in background RFC |
CX_BGRFC_INVALID_UNIT |
Invalid unit of background RFC |
CX_QRFC_NO_FAILED_UNIT |
Queue does not contain any incorrect units |
CX_QRFC_NO_SINGLE_QUEUE_NAME |
Only one queue name is allowed |
CX_BGRFC_WRONG_EXEC_CONTEXT |
The function cannot be run in the current context |
CX_BGRFC_ILLEGAL_PERMUTATION |
Invalid permutation |
CX_BGRFC_INVALID_RETRY_KEY |
Invalid reason for retry |
CX_BGRFC_INVALID_TIME_SPEC |
Invalid date specifications |
CX_QRFC_NO_QUEUE_NAME |
Missing queue name |
Result
Some exceptions output detailed information about the cause of the error using the class attribute TEXTID. The relevant details about the TEXTIDs can be taken from the stored long texts for the respective exception classes.