Diagnostic information in the DB-DIAGAREA of openUTM

The DB-DIAGAREA is a task-specific trace area into which openUTM cyclically writes trace records. You can find more details on the DB-DIAGAREA in the openUTM manual “ Messages, Debugging and Diagnostics”.

At each call, SESAM/SQL supplies return information to openUTM which is transferred to a trace record in the DB-DIAGAREA. This return information is stored as “DB trace information” in bytes 20-51 of the trace record.

Layout of the DB trace information for SQL requests

Byte in the trace record DB-DIAGAREA	Byte in the DB trace information	Length	Meaning
20	0	1	Identifier “S” for SQL request
21	1	2	Representation of the SQL request (coded)
22	3	1	UTM operation code: 0x00 = start parameter input 0x04 = connection 0x08 = disconnection 0x0C = asynchronous disconnection 0x10 = user call 0x14 = finish DB transaction 0x18 = cancel transaction 0x1C = interrupt transaction 0x20 = continue transaction 0x24 = status of transaction 0x28 = preliminary end of transaction 0x2C = end of process 0x30 = interrupt process 0x34 = continue process 0x38 = restart process
24	4	2	SQL state: 00 = successful completion 01 = warning 02 = no data 07 = error in dynamic SQL 21 = cardinality violation 22 = data exception 23 = integrity constraint violation 24 = invalid cursor state 25 = invalid transaction state 26 = invalid SQL statement name 28 = invalid authorization specification 2C = invalid transaction termination 33 = invalid SQL descriptor name 34 = invalid cursor name 3D = invalid catalog name 3F = invalid schema name 40 = transaction rollback 42 = syntax error or access rule violation 51 = recovery errors 52 = errors concerning HSMS archive 55 = errors reported by BS2000 56 = BS2000 limits exceeded 57 = status information 58 = syntax error in input file 59 = errors found by check utility 81 = error in SQL environment 91 = resource limit exceeded 95 = invalid foreign transaction state SB = CLI specific condition
26	6	1	reserved
27	8	1	type of SESAM connection: 0x01 = with distributed processing 0x02 = local processing
28	12	4	Message number
32	16	4	transaction serial number
36	20	4	pointer to actual UTAB
40	24	3	target as per distribution rule
43	27	1	DBH configuration name
44	28	4	TSN of the DBH
48	32	1	last digit of the serial number in the CO-LOG file
49	33	3	block number in the CO-LOG file

Table 38: Layout of the DB trace information for SQL requests

Layout ot the DB trace information for CALL-DM requests

Byte in the trace record DB-DIAGAREA	Byte in the DB trace information	Length	Meaning
20	0	3	begin of CALL DML statement
23	3	1	UTM operation code: as in the table on "Diagnostic information in the DB-DIAGAREA of openUTM"
24	4	2	CALL DML state
26	6	1	status subcode
27	8	1	type of SESAM connection: 0x01 = with distributed processing 0x02 = local processing
28	12	4	Message number
32	16	4	transaction serial number
36	20	4	pointer to actual UTAB
40	24	3	target as per distribution rule
43	27	1	DBH configuration name
44	28	4	TSN of the DBH
48	32	1	last digit of the serial number in the CO-LOG file
49	33	3	block number in the CO-LOG file

Table 39: Layout ot the DB trace information for CALL-DM requests

Layout of the DB trace information for UTM system requests

Byte in the trace record DB-DIAGAREA	Byte in the DB trace information	Length	Meaning
20	0	3	identifier “UTM” for UTM system order
23	3	1	UTM operation code: as in the table on "Diagnostic information in the DB-DIAGAREA of openUTM"
24	4	2	CALL DML state
26	6	1	status subcode
27	8	1	type of SESAM connection: 0x01 = with distributed processing 0x02 = local processing
28	12	4	Message number
32	16	4	transaction serial number
36	20	4	pointer to actual UTAB
40	24	3	target as per distribution rule
43	27	1	DBH configuration name
44	28	4	TSN of the DBH
48	32	1	last digit of the serial number in the CO-LOG file
49	33	3	block number in the CO-LOG file

Table 40: Layout of the DB trace information for UTM system requests