The TIBCO Object Service Broker runtime environment signals system exceptions, permitting an application to recover from an error. A three-level hierarchy of exceptions exists. The ERROR exception is the top of the hierarchy and is intended to be a catchall exception. Each exception traps the exceptions that appear below it in the hierarchy. All errors encountered when accessing external data through the Gateways are trapped under one of the TIBCO Object Service Broker exceptions listed below.
|
|
|
Permission for the requested action on the TIBCO Object Service Broker object is denied. This occurs if the connection ID does not have permission to perform the requested action on the specified object in TIBCO Object Service Broker. This can also occur if SECLEVEL=1 and the EXTERNALUSERID parameter is set to GROUP and the group name is greater than eight characters long.
|
|
A new transaction requested a Gateway and no Gateway is available. Control is passed back to the rule, so that the rule can try the transaction again. If this exception is raised too often, consider requesting more Gateways or reviewing the amount of work being done in your transactions.
|
|
The Gateways made a request to the external DBMS and got an error code that does not map to one of the specific TIBCO Object Service Broker exceptions. The ON SERVERERROR handler can call @SERVERERROR to parse the error message (contained in ENDMSG). You must pass @SERVERERROR the contents of RETURN_MESSAGE, which is in the following format:
pppSL nnnx serverid serveruserid: Message
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A transaction is in progress when the connection to a Gateway breaks or the Gateway fails. Control is passed back to the rule for transaction cleanup.
|