DB Diagarea

Each time a user call is issued to the DB system, a DB record is written to the DB Diagarea. In the same way as UTM Diagarea, this area is cyclically written with trace records.
Two cycles are separated by a dividing line comprising '=' characters. The record above the line is the most recent and the one below the line the oldest. 

Byte 32-Bit		Byte: 64-Bit **)		Meaning
dec.	hexadec.	dec.	hexadec.
0-1	00-01	0-1	00-01	Counter for the current entries in the DIAGAREAs (UTM and DB)
2-5	02-05	2-5	02-05	"DBCL"= ID for DB record
6-7	06-07	6-7	06-07	Unused at present (preset to ’= =’)
8-15	08-0F	8-15	08-0F	Timestamp
16-19	10-13	16-19	10-13	Status of DB transaction1 prior to DB call, see table "Status of the database transaction"
20-23	14-17	20-23	14-17	Status of DB transaction1 following DB call, see table "Status of the database transaction"
24	18	24	18	DB operation code, see table "DB operation codes"
25	19	25	19	DB secondary opcode
26	1A	26	1A	DB error code, see table "DB error codes"
27	1B	27	1B	Identifier for DB system (hexadecimal): 02=XA interface
28-31	1C-1F	28-31	1C-1F	DB trace information of last XA call: 28: RM number, 29-30: XA function code, 31: XA return code
32-63	20-3F	32-63	20-3F	DB trace information for XA calls of this DB operation
64-67	40-43	64-67	40-43	Combined status info TAM (further diagnostic information, relevant only for multiinstance mode)
68-71	44-47	68-71	44-47	not usedcombined status info VGM (further diagnostic informationen, relevant only when using the multi-DB functionality)
72-73	48-49	72-73	48-49	Transaction counter within the service
74	4A	74	4A	Number of the UTM application run (starts at 1 after KDCDEF generation)
75	4A	75	4A	Code for table index, =' T '
76-77	4C-4D	76-77	4C-4D	UTM table index that caused the database call
78-79	4E-4F	78-79	4E-4F	Action index within this table
80-83	50-53	80-87	50-57	Service counter (unique within the UTM application run)
84-87	54-57	88-95	58-5F	Address used internally
88-91	58-5B	96-103	60-67	Return address in the program unit. The address points to a location after the CALL-DB-SYSTEM call.
92	5C	104	68	* to draw attention to the end of the diagnostics record

DB record in the DB Diagarea

¹For operation codes which refer to DB conversations the status of the VGM is shown here.

**) only valid for Unix, Linux and Windows systems

If the database system is connected to openUTM via the XA interface and a "dynamic XA switch" is included (for Oracle, for example, the module "oraswd"), the following diagnostic record is written when a common transaction signs on or off (32-Bit and 64-Bit coincide):

Byte		Meaning
dec.	hexadec.
16-23	10-17	Printable "ax_reg" when the transaction signs on Printable "ax_unreg" when the transaction signs off
24-27	18-1B	Number of the RM instance
28-31	1C-1F	not used
32-47	20-2F	Printable return code for the call
48	30	Internal status of the transaction
49	31	Internal status of the sign-on/sign-off
50-51	32-33	not used
52-54	34-36	Is the call within an openUTM transaction? (printable, "yes" or "no")
55	37	not used
56	38	* to draw attention to the end of the diagnostics record

Diagnostic record

Status of the database transaction:

Contents (hex)	Meaning of the DB status
04	DB transaction was set to the preliminary end of transaction (PTC)
08	Updates were made within a DB transaction
10	DB transaction has been rolled back
20	DB transaction was closed
40	The program unit run issued a call CLOSE DB transaction; DB transaction is terminated from viewpoint of program unit run
80	DB transaction is open

Status of the DB transaction. These values can also occur in combination, e.g. "88".

DB operation codes:

Contents (hex)	DB op. codes	Meaning
00	STPA	DB connection module is to check DB-specific start parameters. The call takes place at start of UTM application program
04	CONC	Connection setup between UTM process and connection module of DB system. Takes place at start of UTM application program
08	DCON	Connection cleardown between UTM process and DB system. Call takes place in end handling of openUTM application program
10	USRC	Execute DB call of application program (user call).
14	FITA	Terminate DB transaction. openUTM issues this call at the end of a joint DB/DC transaction
18	CATA	Terminate DB transaction abnormally, i.e. the DB transaction is rolled back to the last synchronization point
1C	BKTA	The call is used with PEND KP or PEND PA/PR with process switch (due to TAC classes); the UTM process breaks off from DB/DC transaction processing.
20	COTA	The call takes place whenever a multi-step transaction is continued, i.e. following a PEND KP or PEND PA/PR with process switch (due to TAC classes)
24	STAT	Display status of a DB transaction or delete all DB states. The DB system maintains status information on DB transactions as a means for coordinated restarts in openUTM and the DB system.
28	PETA	Request preliminary end of DB transaction
2C	EDVG	End of UTM conversation; DB conversation still open
30	BKVG	Interrupt of an open DB conversation
34	COVG	Continuation of an interrupted DB conversation following BKVG
38	RSVG	Display of restart of a DB conversation to last synchronization point
3C	CNFPTC	DB connection module confirms the status of the precommitted transactions to the DB system via the XA interface and deletes these from the internal list.
40	STRT	DB connection module notifies the DB system of the start of a DB transaction via the XA interface.
44	PEND	DB connection module notifies the DB system of the preliminary end of the transaction via the XA interface and initiates the first commitment phase.

DB operation codes

DB error codes:

Contents (hex)	Meaning of the DB error codes
00	Job performed
04	DB transaction had to be rolled back. openUTM then also rolls back the UTM transaction. With a DB call (user call), control is restored to the application program unit
08	Causes conversation to abort with PEND ER when openUTM is used
0C	DB system is not available, not activated
10	DB system not available for another reason
14	Job not carried out, retry later!
18	A (possibly) recoverable system error occurred. openUTM creates a process dump and tries to terminate the open DB transaction
1C	An unrecoverable error occurred. Any further work with the DB system is pointless in this DB session
20	DB system detected a user error, e.g. during checking of the DB start parameters
24	DB system detected an interface error

DB error codes