The GetMessage method sets the Glb.Status built-in segment attribute to "*****" when the external automatic entry is unsuccessful, due to one of the reasons listed below.
The Glb.HubStatus built-in segment attribute is set to one of the values listed in the following table.
Glb.HubStatus Value | Description |
---|---|
2PC.NOT.AVAIL | The external automatic entry uses two-phase commit, but the destination application does not support two-phase commit. |
BAD USE OF OVI | Client attempted to perform an external Automatic Entry using an OLTP View Ispec |
COMS SYSTEM ERR | System interface error when receiving control information from the CRM (MCP environment only) |
CYCLE.ERROR | Two or more external automatic entries have attempted to create a closed cycle (deadlock). In a cycle, an application sends an external automatic entry to a destination application, and waits for acknowledgment from that application. However, the destination application might itself send an external automatic entry to another application before it sends this acknowledgment, and so on, creating a chain of automatic entries for one transaction. A closed cycle is formed if this chain tries to include the same application more than once; that is, an originating application (waiting for acknowledgment) is itself sent an automatic entry as part of the same transaction. This application will never be able to handle the incoming transaction, as it will never receive the acknowledgment it is waiting for. For example, suppose application A sends an external automatic entry to application B, which needs to send an external automatic entry to application C before the transaction is complete. If application C then tries to send an external automatic entry to application A as part of this transaction, a closed cycle is created, and the attempted external automatic entry from application C will receive this error notification. |
DATABASE.ERROR | An unrecoverable database error occurred in the receiving application. |
DEST.AMBIGUOUS | (This Glb.Hubstatus value does not occur on applications deployed to Windows.) |
DM.DEADLOCK | (This Glb.Hubstatus value does not occur on applications deployed to Windows.) |
FATAL.ERROR | An unrecoverable error occurred at the destination application. |
INVALID ISPEC | The ispec in the destination application does not exist or is persistent, but has no user interface. |
INVALID | An entirely invalid action has been attempted. |
INVALID.RECALL | An ispec in the destination application executed a Recall logic statement. |
NO CONV. MODE | Client attempted to use Conversational Mode |
NON-2PC SERVER | Addressed Service Ispec not Two-Phase commit-capable when Two-Phase commit was requested |
NON-OLTP Ispec | Addressed Service Ispec not OLTP-capable |
OLTP SVC ERR | Zero-length reply unexpectedly received |
OLTP TP | Error prevented OLTP transaction being processed |
OLTP TX | Unable to communicate with OLTP TM while initiating OLTP transaction |
RC; UNKNOWN | Transaction attempted to Recall an unknown Ispec, or BYE or EXIT |
SECURITY.ERROR | The username/usercode of the originating application does not have sufficient security access to perform the automatic entry on the destination application. |
SWITCH CMD. | Transaction attempted to perform a SWITCH; command |
TIMEOUT | OLTP timed out waiting for response from server |
TRAN.ERROR | Processing of the external automatic entry in the destination server has set the Glb.Errorbuilt-in segment attribute to "*****" and no data was returned For example, this occurs if attempts are made to insert using an existing key value, or to update using a non-existent key value. |