Copyright © Cloud Software Group, Inc. All Rights Reserved |
COMMIT and ROLLBACK statements have no effect on MAP tables; data in storage is read or written directly by the GET, REPLACE, and FORALL statements.The TIBCO Object Service Broker runtime environment signals system exceptions to permit 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 MAP server are trapped under one of the following exceptions:
•
• An ERROR exception indicates that an error is detected and no lower-level exception exists in the application.An ACCESSFAIL exception indicates that a table access error is detected. The following exceptions are valid under an ACCESSFAIL exception:
An INTEGRITYFAIL exception indicates an attempt to violate data integrity is detected. The following exceptions are valid under an INTEGRITYFAIL exception:
Indicates that permission for the requested action on the object is deniedA RULEFAIL exception indicates that an error is provoked by incorrect rules language coding. The following exceptions are valid under a RULEFAIL exception:
TIBCO Object Service Broker is unable to convert between the internal and external data An attempt is being made to access unregistered storage, that is, there is no row in @MAP to match the address referencedTIBCO Object Service Broker Programming in Rules for more information on exceptions.
Copyright © Cloud Software Group, Inc. All Rights Reserved |