Format Requirements for the IMS Transaction Information Interface

Administration of the IMS Feature › Processing IMS Transaction Information Data › Format Requirements for the IMS Transaction Information Interface

Format Requirements for the IMS Transaction Information Interface

The input data for the IMS Transaction Information Interface must meet the following format requirements:

The IMS transaction execution must be provided as a sequential input data set.
The execution information for each transaction call must be in a separate line.
The execution information in each line must be placed in a required order and separated by a comma delimiter, as follows:
```
field1,field2,field3,...
field1,field2,field3,...
```

The execution information that you need to provide for each IMS transaction call is listedfollowing.


Required fields:
Field:	TRANSACTION
Description:	transaction name
Relative position in data line:	1
Format:	alphanumeric
Length:	1 - 8 characters
Range:	valid transaction name
Example:	DAT1, TRAN0001

Field:	IMS REGION
Description:	IMS region name where the transaction was executed
Relative position in data line:	2
Format:	alphanumeric
Length:	1 - 8 characters
Range:	valid region name
Example:	IMS1, IR01
Field:	START DATE
Description:	date the transaction was started
Relative position in data line:	3
Format:	numeric, date format YYYYMMDD
Length:	8 characters
Range:	valid date value
Example:	20081121

Field:	START TIME
Description:	time the transaction was started
Relative position in data line:	4
Format:	numeric, time format HHMMSS.nn to HHMMSS.nnnn
Length:	6 to 11 characters, including the decimal point
Range:	valid clock time, with up to 4 decimal places for ten thousandth of a second
Example:	123118, 123118.12, 123118.1256

Field:	END DATE
Description:	date the transaction has ended
Relative position in data line:	5
Format:	numeric, date format YYYYMMDD
Length:	8 characters
Range:	valid date value
Example:	20081121

Field:	END TIME
Description:	time the transaction has ended
Relative position in data line:	6
Format:	numeric, time format HHMMSS.nn to HHMMSS.nnnn
Length:	6 to 11 characters, including the decimal point
Range:	valid clock time, with up to 4 decimal places for ten thousandth of a second
Example:	123118, 123118.12, 123118.1256
Field:	ELAPSED TIME
Description:	elapsed time of the transaction
Relative position in data line:	7
Format:	decimal, from N to NNNNNNNNN.nnnnnn
Length:	1 to 16 characters, including the decimal point
Range:	0 - 999999999.999999
Example:	9, 15.2374, 145.873922

Field:	CPU TIME
Description:	CPU time consumed during the transaction execution
Relative position in data line:	8
Format:	decimal, from N to NNNNNNNNN.nnnnnn
Length:	1 to 16 characters, including the decimal point
Range:	0 - 999999999.999999
Example:	9, 15.2374, 145.873922

Field:	WAIT TIME
Description:	time the transaction was in a wait state
Relative position in data line:	9
Format:	decimal, from N to NNNNNNNNN.nnnnnn
Length:	1 to 16 characters, including the decimal point
Range:	0 - 999999999.999999
Example:	9, 15.2374, 145.873922
Optional fields:
Field:	DB2 REQUESTS
Description:	number of DB2 (EXEC SQL or IFI) requests issued by the transaction
Relative position in data line:	10
Format:	numeric, from N to NNNNNNNNN
Length:	1 to 9 characters
Range:	0 - 999999999
Example:	0, 356823, 5923456

Field:	IMS REQUESTS
Description:	number of IMS (DBCTL) requests issued by the transaction
Relative position in data line:	11
Format:	numeric, from N to NNNNNNNNN
Length:	1 to 9 characters
Range:	0 - 999999999
Example:	0, 356823, 5923456