Record format: fixed segment

TRNRDW

RECORD DESCRIPTOR WORD (RDW)

Length of the record

Group

4

000

000

TRNLL

Record descriptor word

Binary

2

000

000

TRNZZ

Record descriptor word

Binary

2

002

002

TRNRECID

LOG RECORD ID

Code that identifies this record as a transaction record with a default value of X'FA'

Display

1

004

004

TRNRCTYP

RECORD TYPE

Code that identifies the type of transaction as a single record

Display

1

005

005

TRNPSTNR

PST NUMBER

PST associated with the region in which the transaction was executed

Binary

2

006

006

TRNOPSYS

OPERATING SYSTEM PRODUCT

IBM operating system product version and release number in the format vrr:

• v represents the version number
• rr represents the release number

Display

3

008

008

TRNSMQFL

FLAG

The following settings apply:

• X'01' indicates a shared message queue environment

• X'80' indicates some DL/I or ESS calls were not included in the detail trace

  The calls are filtered based on the DFILTER, DFDBCODE, DFDCCODE, DFESCODE, and DFTIME parameter settings in IMFECP00.

• X'40' indicates PGM WAS PRELOADED (DFSMPLXX)

Binary

1

011

00B

TRNIMS

IMS LEVEL

IMS release number and mod level number

Display

4

012

00C

TRNIMF

MVIMS LEVEL

MainView for IMS version and release level

Display

4

016

010

TRNIMSID

IMS SYSTEM IDENTIFICATION

Identification code for the IMS system on which this transaction was processed (IMSID)

Display

4

020

014

TRNSMFID

SMF SYSTEM IDENTIFICATION

ID code from SMCA for the computing system on which this program executed.

Display

4

024

018

TRNSYSID

MVIMS SYSTEM IDENTIFICATION

Identification code for the IMS system on which this transaction was processed (specified as a parameter to MainView for IMS - SYSID in IMFECP00)

Display

1

028

01C

TRNFLAG1

LSO FLAG

LSO processing option in effect when this transaction was processed

The values correspond to the IMS LSO parameter values (N, Y, X, and S).

Display

1

029

01D

TRNTMERR

TIMER ERROR FLAG

Flag that indicates when an error is detected in the CPU timing services

Binary

1

030

01E

TRNTMEDT

TIMER ERROR DISPATCHER TYPE

IMS dispatcher type code when the timing error occurred

Binary

1

031

01F

TRNJOBNM

REGION ID

Name assigned to the initiator used to schedule the program into a message region (jobname)

For DBCTL threads, this field contains the CICS or ODBA address space jobname.

Display

8

032

020

TRNASID

ADDRESS SPACE ID

ASID for the region in which this transaction was processed

Binary

2

040

028

TRNPG

PERFORMANCE GROUP

Operating system SRM performance group for the region in which this transaction was processed

If Goal Mode is active, this field contains a hexadecimal value of 0000.

Binary

2

042

02A

TRNCAVAL

STORAGE AVAILABLE

Number of unused 2 KB blocks available in the region after initial scheduling

For DBCTL threads, this field contains the amount of storage available in the CICS or ODBA address space at the time the PSB is allocated.

Binary

2

044

02C

TRNDBTOF

OFFSET OF DBD SEGMENT

Offset of the start of the variable length DBD segments

Binary

2

046

02E

TRNAGN

APPLICATION GROUP NAME

Application group name assigned by the security system

Display

8

048

030

TRNPSBNM

PSB NAME

Name of the PSB that was scheduled for this transaction

Display

8

056

038

TRNCODE

TRANSACTION CODE

Transaction code identifying this message

This field is blank for a program that does not process an input transaction (for example, some BMPs).

For DBCTL CICS threads, this field contains the four-byte CICS transaction code.

For SAP transactions, this field contains the SAP report ID, if available, or the SAP transaction code if the SAP exit is installed.

Display

8

064

040

TRNESSID

EXTERNAL SUBSYSTEM ID

One- to four-character DB2 subsystem ID accessed by this transaction

Display

4

072

048

TRNOTMCL

OTMA CLIENT TYPE

Where the transaction came from:

• C'M'=OTMA IBM WebSphere MQ client
• C'I'=OTMA IMS Connect client
• C'P'=OTMA Synchronous Program Switch client
• C'C'=OTMA IMS Connect client, without Energizer for IMS Connect

Binary

1

076

04C

--

RESERVED

Display

2

077

04D

TRNCLAS

INPUT CLASS

Class used to assign the transaction to a specific message region by the IMS scheduler (for IMS 9.1 and later)

Binary

2

079

04F

TRNCLASS

INPUT CLASS

Class used to assign the transaction to a specific message region by the IMS scheduler (for IMS 8.1 and earlier)

Binary

1

080

050

TRNPTYPE

PROGRAM TYPE

Type of program that processed this transaction:

• B=batch message processing program (BMP)
• C=conversational (MPP or JMP)
• D=DBCTL CICS thread
• E=CPI-C driven program (TPI)
• F=Fast Path message-driven program (MDP)
• M=message processing program (MPP)
• N=Fast Path non-message-driven program (NDP)
• U=Fast Path utility program (FP)
• X=DB management utility (DMU)

Display

1

081

051

TRNFLAG0

SPECIAL PROCESSING FLAG

Special processing characteristics:

• J=Java message processing transaction (JMP)
• K=Java batch message processing transaction (JBP)
• O=DBCTL ODBA thread
• Q=pseudo WFI transaction (pseudo wait for input)
• W=WFI transaction (wait for input)

Display

1

082

052

TRNXFLAG

FLAG

Type of transaction:

• X'80' indicates that the IMRUTRNx (user exit) was called
• X'40' indicates that the SQL call was issued
• X'20' indicates that the DL/I database accessed
• X'10' indicates that the Fast Path database accessed
• X'08' indicates that the APPC/IMS transaction
• X'04' indicates that the SAP exit pass 1
• X'02' indicates that the SAP exit pass 2

Binary

1

083

053

TRNCUSED

STORAGE USED

Amount, in 2 KB units, of available message region storage used by this program (link-edit length)

For DBCTL threads, this field is zero.

Binary

2

084

054

TRNCOMP

TRANSACTION COMPLETION CODE

Transaction completion code in the format xxsssuuu:

• xx=flags
• sss=system abend code
• uuu=user abend code

Binary

4

086

056

TRNTOKEN

PLEXUS TRANSACTION TOKEN

Binary

4

090

05A

TRNDBTLR

NUMBER OF DBD SEGMENTS

Number of DBD segments in the variable portion of this record

Binary

2

094

05E

TRNSTTDT

TRANSACTION START DATE/TIME OVERLAY

Group

8

096

060

TRNSTRDT

TRANSACTION START DATE

Julian date when processing of this transaction was started; format is packed yyyydddF

Packed

4

096

060

TRNSTRTT

TRANSACTION START TIME

Time of day when processing of this transaction was started

The time is expressed in hours, minutes, seconds, tenths of a second, and hundredths of a second (hhmmssth). When this field is viewed, it might appear as binary.

Packed unsigned

4

100

064

TRNSTPDT

TRANSACTION END DATE/TIME OVERLAY

Group

8

104

068

TRNSTOPD

TRANSACTION END DATE

Julian date when processing of this transaction was completed; format is packed yyyydddF

Packed

4

104

068

TRNSTOPT

TRANSACTION END TIME

Time of day when processing of this transaction was completed

The time is expressed in hours, minutes, seconds, tenths of a second, and hundredths of a second (hhmmssth). When this field is viewed, it might appear as binary.

Packed unsigned

4

108

06C

TRNARVDT

TRANSACTION ARRIVAL DATE/TIME OVERLAY

Group

8

112

070

TRNARIVD

TRANSACTION ARRIVAL DATE

Julian date when this transaction was submitted for processing

For a non-Fast Path transaction, the format is packed yyyydddC. For a Fast Path transaction, the format is packed decimal 0099999C.

For DBCTL CICS threads, this field contains a zero, because arrival date of the input message is available only to CICS. For DBCTL ODBA threads, there is no input arrival date.

Packed

4

112

070

TRNARIVT

TRANSACTION ARRIVAL TIME

Time of day when this transaction was submitted for processing

The time is expressed as packed decimal hhmmsstC. (Arrival time is set by IMS and is the time when a transaction is put in the IMS input message queue or BALG after communications and MFS processing are complete.)

• For message switch transactions submitted by a non-message-driven BMP or JBP or an explicit CPI-C driven program , this timestamp is zero.
• For message switch transactions for which the original input came from a terminal, this timestamp is the arrival time of the original transaction.
• For transactions that originate in another system in an MSC environment, this timestamp is set to the transaction start time, unless the clock of the MSC system is synchronized with the clock of the local IMS. The MSCCLOCK parameter in BBPARM member IMFECP00 is used to specify whether or not MSC systems clocks are synchronized with local time.
• For Fast Path transactions, this timestamp is the input queue time in milliseconds.
• For DBCTL CICS threads, this field contains a zero, because arrival time of the input message is available only to CICS. For DBCTL ODBA threads, there is no input arrival time.

Packed

4

116

074

TRNLTERM

LOGICAL TERMINAL NAME

Name of the logical terminal used to submit this transaction:

• For DBCTL CICS threads, this field contains the four-byte CICS terminal identifier.
• For APPC/IMS programs, this field contains the partner LU name.

For transactions from OTMA this is the Tpipe name.

Display

8

120

078

TRNUSID

SECURITY USER ID

User ID field, usually from the I/O PCB

The ID is used in connection with signon security. This field contains one of the following values:

• User's identification from the source terminal if signon is active
• LTERM name of the source terminal if signon is not active for that terminal
• ID of the user who submitted a BMP or JBP if user ID or LTERM information is not available in the I/O PCB
• Blanks if none of the above is true
• For DBCTL CICS threads, contains the CICS user ID
• For APPC/IMS programs, passed to IMS by APPC

Display

8

128

080

TRNVNODE

VTAM NODE NAME

Name of the node of the physical terminal from which this transaction was submitted if it is a VTAM terminal

This field is not filled in for Fast Path message-driven transactions. For APPC/IMS transactions, it contains the partner LU name.

Display

8

136

088

TRNPLT 

PHYSICAL LINE/TERMINAL NUMBER OVERLAY

Group

8

144

090

TRNPLINE

PHYSICAL LINE NUMBER

Line number of the physical terminal from which this transaction was submitted

Binary

4

144

090

TRNPTERM

PHYSICAL TERMINAL NUMBER

Terminal number of the physical terminal from which this transaction was submitted

Binary

4

148

094

TRNPGMNM

PROGRAM NAME

For a:

• BMP or JBP, a CPI-C driven program (TPI) or DBCTL thread
• TPI, the program name is the same as the transaction name

This field can be different from the PSB name.

Display

8

152

098

TRNRCODE

ROUTING CODE

Routing code used to schedule this transaction to a BALG (balancing group) for a Fast Path message-driven region

Display

8

160

0A0

TRNFLAG2

FAST PATH FLAG

Fast Path characteristics of this transaction if it accessed Fast Path databases

A W indicates that this transaction waited for the OBA buffer latch.

Display

1

168

0A8

TRNFLAG3

OTMA FLAG

X'80' indicates an OTMA transaction

Binary

1

169

0A9

TRNBUSED

FAST PATH BUFFERS USED

If this transaction accessed Fast Path databases, shows how many Fast Path buffers were actually used

Binary

2

170

0AA

TRNNBA

NORMAL BUFFER ALLOCATION

If this transaction ran in a region that supported Fast Path database access, the NBA value from the JCL

Binary

2

172

0AC

TRNOBA

OVERFLOW BUFFER ALLOCATION

If this transaction ran in a region that supported Fast Path database access, the OBA value from the JCL

Binary

2

174

0AE

TRNNCIC

FAST PATH CI CONTENTIONS

Number of Fast Path CI contentions that occurred in the transaction sync interval

Binary

2

176

0B0

TRNNWFB

FAST PATH WAIT FOR BUFFERS

Number of times this transaction had to wait for a Fast Path buffer to become available

Binary

2

178

0B2

TRNSPRC

SYNC POINT RETURN CODE

Result of sync point processing for a transaction that accessed Fast Path databases

Binary

2

180

0B4

TRNBGQCT

BALANCING GROUP Q COUNT

For a Fast Path message-driven transaction, the number of transactions queued on the same balancing group when this transaction went through sync point processing

Binary

2

182

0B6

TRNMDRRN

MESSAGE QUEUE RELATIVE RECORD NUMBER

Input message DRRN

Display

4

184

0B8

TRNMST

MSC TRACE

For an MSC transaction, the last two bytes of PSTMST, tracing the system IDs

Binary

2

188

0BC

TRNCSW

MSC INPUT SOURCE

Code that identifies MSC origin:

• X'80'=message switch
• X'40'=arrival date/time are set to arrival date/time from originating MSC system due to clock synchronization
• X'20'=terminal input
• X'08'=inserted response message

Display

2

190

0BE

TRNUINID

MSC INPUT SYSID

In an MSC environment, the system ID of the system where this transaction was entered

Binary

1

192

0C0

TRNUOTID

MSC DESTINATION SYSID - I/O PCB

In an MSC environment, the system ID of the system to which output is sent through the I/O PCB

Binary

1

193

0C1

TRNUSWID

MSC DESTINATION SYSID - MESSAGE SWITCH

In an MSC environment, the system ID of the system to which a message switch transaction was inserted (the last one if more than one)

Binary

1

194

0C2

TRNUALID

MSC DESTINATION SYSID - ALTERNATE PCB

In an MSC environment, the system ID of the system to which output to an LTERM was inserted through an alternate PCB (the last one if more than one)

Binary

1

195

0C3

TRNUMSWT

One of the following elements:

• ALTERNATE PCB DESTINATION TRANSACTION

  Transaction code of the last message switch transaction inserted by this transaction, if any

• CICS UNIT OF WORK ID

  For DBCTL CICS threads only; the first six bytes of the CICS UOW (unit of work) ID can be used to match the first six bytes of the UOWID in the CICS SMF 110 record

Display

8

196

0C4

TRNUALTN

ALTERNATE PCB DESTINATION LTERM

LTERM name of the destination of an alternate PCB message inserted by this transaction, if any

Display

8

204

0CC

TRNMSCDT

MSC ARRIVAL DATE/TIME IN ORIGINAL SYSTEM OVERLAY

Group

8

212

0D4

TRNMSCAD

MSC ARRIVAL DATE

Julian date when this MSC transaction was submitted for processing in the originating system; format is packed decimal yyyydddF

Clocks cannot be synchronized with the processing system. Note that MSC arrival date is not affected by the MSCCLOCK parameter in BBPARM member IMFECP00.

Packed

4

212

0D4

TRNMSCAT

MSC ARRIVAL TIME

Time of day when this MSC transaction was submitted for processing in the originating system; format is packed decimal hhmmsstC

Clocks cannot be synchronized with the processing system. Note that MSC arrival time is not affected by the MSCCLOCK parameter in BBPARM member IMFECP00.

Packed Unsigned

4

216

0D8

TRNLOGID

TRANSACTION LOGGING IDENTIFIER

Identifier of the MainView for IMS module that logged this transaction record

Display

4

220

0DC

TRNCDCPU

Control REGION DLI TIME

Amount of control region CPU time, expressed in microseconds, used by the DL/I Analyzer to process the transaction

Does not include database open/close time. Bit 51 is equal to one microsecond.

If the buffer handler option is turned off, this time also includes buffer handler CPU time.

For all Event Collector CPU data collection parameter options except ALL, this field is zero.

Binary

8

224

0E0

TRNCBCPU

Control REGION BUFFER HANDLER TIME

Amount of control region CPU time, expressed in microseconds, used by the buffer handler module during the processing of the transaction

Bit 51 is equal to one microsecond.

The amount is zero if the buffer handler option (BHTO) is turned off.

For all Event Collector CPU data collection parameter options except ALL, this field is zero.

Binary

8

232

0E8

TRNOCCPU

Control REGION OPEN CLOSE CPU TIME

Amount of control region CPU time, expressed in microseconds, used by the DL/I Analyzer to open and close required databases while processing this transaction

Bit 51 is equal to one microsecond.

For all Event Collector CPU data collection parameter options except ALL, this field is zero.

Binary

8

240

0F0

TRNDDCPU

DEPENDENT REGION DL/I TIME

Amount of dependent region CPU time, expressed in microseconds, used by the DL/I analyzer to process the transaction

Bit 51 is equal to one microsecond.

If the buffer handler option is turned off, this time also includes buffer handler CPU time.

Binary

8

248

0F8

TRNDBCPU

DEPENDENT REGION BUFFER HANDLER TIME

Amount of dependent region CPU time, expressed in microseconds, used by the buffer handler module during the processing of this transaction

The amount is zero if the buffer handler option (BHTO) is turned off.

Binary

8

256

100

TRNDOCPU

DEPENDENT REGION OPEN CLOSE CPU TIME

Amount of dependent region CPU time, expressed in microseconds, used by the DL/I Analyzer to open and close databases for this transaction

Only Fast Path DEDBs are opened from the dependent region.

Binary

8

264

108

TRNPGCPU

DEPENDENT REGION APPLICATION CPU TIME

Amount of CPU time, expressed in microseconds, used by the application program to process this transaction

Bit 51 is equal to one microsecond. The amount includes DB2 CPU time if the parameter FEATURE=NODB2 is specified in PARMLIB member IMFSYS00 (see PARMLIB member IMFSYSBB for more information).

Binary

8

272

110

TRNSDCPU

DLISAS REGION DL/I TIME

If LSO=S, the amount of DLISAS region CPU time, expressed in microseconds, used by the DL/I Analyzer to process the transaction

Does not include database open/close time. Bit 51 is equal to one microsecond.

If the buffer handler option (BHTO) is turned off, this time also includes buffer handler CPU time.

For all Event Collector CPU data collection parameter options except ALL, this field is zero.

Binary

8

280

118

TRNSBCPU

DLISAS BUFFER HANDLER CPU TIME

If LSO=S, the amount of DLISAS region CPU time, expressed in microseconds, used by the Buffer Handler module during the processing of the transaction

Bit 51 is equal to one microsecond.

The amount is zero if the buffer handler option (BHTO) is turned off.

For all Event Collector CPU data collection parameter options except ALL, this field is zero.

Binary

8

288

120

TRNSOCPU

DLISAS OPEN CLOSE CPU TIME

If LSO=S, the amount of DLISAS region CPU time, expressed in microseconds, used by the DL/I Analyzer to open and close required databases while processing this transaction

Bit 51 is equal to one microsecond.

For all Event Collector CPU data collection parameter options except ALL, this field is zero.

Binary

8

296

128

TRNESCPU

DEPENDENT REGION DB2 CPU TIME

Amount of CPU time, expressed in microseconds, used in the dependent region to process normal and service calls to DB2

Binary

8

304

130

TRNMGU

MESSAGE GET UNIQUE COUNT

Number of message get unique calls issued by the transaction

Binary

4

312

138

TRNMGN

MESSAGE GET NEXT COUNT

Number of message get next calls issued by the transaction

Binary

4

316

13C

TRNMISRT

MESSAGE INSERT COUNT

Number of message insert calls issued by the transaction

Binary

4

320

140

TRNMPURG

MESSAGE PURGE COUNT

Number of message purge calls issued by the transaction

Binary

4

324

144

TRNMOTHR

MESSAGE OTHER COUNT

Number of other-type calls (checkpoint, statistics, System Service, and so on) issued by the transaction

Binary

4

328

148

TRNIMCHR

INPUT CHARACTER COUNT

Number of characters in this input transaction (after MFS formatting)

Binary

4

332

14C

TRNISPAC

SPA INPUT CHARACTER COUNT

Number of input characters from a scratch pad area during transaction processing

Binary

4

336

150

TRNOMCHR

OUTPUT CHARACTER COUNT

Number of output characters to the originating logical terminal during transaction processing (before MFS formatting)

Binary

4

340

154

TRNOSPAC

SPA OUTPUT CHARACTER COUNT

Number of output characters to a scratch pad area during transaction processing

Binary

4

344

158

TRNATCHR

MESSAGE SWITCH OUTPUT CHARACTER COUNT

Number of output characters to the message input queue as a result of message switches by this transaction

Binary

4

348

15C

TRNALCHR

ALTERNATE TERM OUTPUT CHARACTER COUNT

Number of output characters for this transaction to an LTERM other than the originating logical terminal (before MFS formatting)

Binary

4

352

160

TRNSYNCW

SYNC BUFFER FLUSH WRITE COUNT OVERLAY

Group

4

356

164

TRNSKW

SYNC BUFFER FLUSH KEY WRITE

Binary

2

356

164

TRNSNKW

SYNC BUFFER FLUSH NONKEY WRITE

Binary

2

358

166

TRNUSER

RESERVED USER

Area reserved for user functions or additions

Display

16

360

168

TRNXUTCA

UTC ADJUSTMENT VALUE

IMS Universal Time Clock (UTC) adjustment value

This element is a UTC-to-local time adjustment value.

Packed

2

376

178

TRNXCODE

IMS TRANSACTION CODE

IMS transaction code for SAP applications if the SAP exit pass 1 (TRNSAP1) flag is on (at displacement 083 053)

Display

8

378

17A

TRNMSCUT

MSC MESSAGE ARRIVAL TIME

Arrival time of the MSC message (in local or UTC time)

Packed

2

386

182

TRNSTCK

TRANSACTION START TIME

Start time of the transaction (in operating system time-of-day format)

Binary

8

388

184

TRNETFLG

OPTIONAL TIMING OPTIONS FLAG

Flag that indicates whether elapsed and IWAIT times are collected:

• X'80'=elapsed times are collected
• X'40'=IWAIT times are collected

Binary

1

396

18C

TRNEF2 

TRIWAITS SETTINGS
• X'80'=Latch
• X'40'=Lock
• X'20'=Logical logger
• X'10'=Dynamic Allocation
• X'08'=Queue Buffer
• X'04'=DBRC
• X'02'=Miscellaneous

Binary

3

397

18D

TRNW1OTH

UNCLASSIFIED IWAIT TIME

Amount of time the transaction spent in unclassified IWAIT, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

400

190

TRNW2OTH

UNCLASSIFIED IWAIT TIME DURING SYNC POINT

Amount of time the transaction spent in unclassified IWAIT during sync point, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

404

194

TRNW2LCH

LATCH IWAIT TIME DURING SYNC POINT

Amount of time the transaction spent in latch IWAIT during sync point, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

408

198

TRNW2IOV

VSAM IWAIT TIME DURING SYNC POINT

Amount of time the transaction spent in VSAM IWAIT during sync point, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

412

19C

TRNW2IOO

OSAM IWAIT TIME DURING SYNC POINT

Amount of time the transaction spent in OSAM IWAIT during sync point, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

416

1A0

TRNW3OTH

UNCLASSIFIED IWAIT TIME DURING DL/I TM CALLS

Amount of time the transaction spent in unclassified IWAIT during DL/I TM calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

420

1A4

TRNW3LCH

LATCH IWAIT TIME DURING DL/I TM CALLS

Amount of time the transaction spent in latch IWAIT during DL/I TM calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

424

1A8

TRNW4OTH

UNCLASSIFIED IWAIT TIME DURING DATABASE OPEN/CLOSE

Amount of time the transaction spent in unclassified IWAIT during database open/close, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

428

1AC

TRNW4DBR

DBRC IWAIT TIME DURING DATABASE OPEN/CLOSE

Amount of time the transaction spent in DBRC IWAIT during database open/close, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

432

1B0

TRNW4IO

I/O IWAIT TIME DURING DATABASE OPEN/CLOSE

Amount of time the transaction spent in I/O IWAIT during database open/close, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

436

1B4

TRNW5OTH

UNCLASSIFIED IWAIT TIME DURING DL/I DB CALLS

Amount of time the transaction spent in unclassified IWAIT during DL/I DB calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

440

1B8

TRNW5LCH

LATCH IWAIT TIME DURING DL/I DB CALLS

Amount of time the transaction spent in latch IWAIT during DL/I DB calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

444

1BC

TRNW5LCK

IRLM OR PI LOCK IWAIT TIME DURING DL/I DB CALLS

Amount of time the transaction spent in IRLM or PI lock IWAIT during DL/I DB calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

448

1C0

TRNW5IOV

VSAM IWAIT TIME DURING DL/I DB CALLS

Amount of time the transaction spent in VSAM IWAIT during DL/I DB calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

452

1C4

TRNW5IOO

OSAM IWAIT TIME DURING DL/I DB CALLS

Amount of time the transaction spent in OSAM IWAIT during DL/I DB calls, expressed in microseconds

The time is collected if the IWAIT times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

456

1C8

TRNW5IOD

DEDB IWAIT TIME DURING DL/I DB CALLS

Amount of time the transaction spent in DEDB IWAIT during DL/I DB calls, expressed in microseconds

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

460

1CC

TRNEAPPL

APPLICATION ELAPSED TIME

Amount of application elapsed time for the transaction, expressed in microseconds

The time includes the elapsed time recorded in TRNE1STD, schedule-to-first DL/I call time

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Binary

4

464

1D0

TRNEDLTM

DL/I TM CALL ELAPSED TIME

Amount of DL/I TM call elapsed time for the transaction, expressed in microseconds

The time includes the elapsed time recorded in TRNESYNC, synchronization point time. ESS phase 1 and phase 2 commit time that occurs as the result of a DL/I TM call is also included in this field, and not in the ESS elapsed time fields.

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

468

1D4

TRNEDLDB

DL/I DB CALL ELAPSED TIME

Amount of DL/I DB call elapsed time for the transaction, expressed in microseconds

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

472

1D8

TRNEDB2

DB2 CALL ELAPSED TIME

Amount of DB2 call elapsed time for the transaction, expressed in microseconds

DB2 activity that results from DL/I TM calls (such as phase 1 and phase 2 commits) is not included in this field time.

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

476

1DC

TRNEMQS

MQSERIES CALL ELAPSED TIME

Amount of IBM MQSeries call elapsed time for the transaction, expressed in microseconds

MQSeries activity that results from DL/I TM calls (such as phase 1 and phase 2 commits) is not included in this time.

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

480

1E0

TRNEOESS

OTHER ESS CALL ELAPSED TIME

Amount of other ESS call elapsed time for the transaction, expressed in microseconds

Other ESS activity that results from DL/I TM calls (such as phase 1 and phase 2 commits) is not included in this field.

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

484

1E4

TRNEOPCL

DATABASE OPEN/CLOSE ELAPSED TIME

Amount of database open/close elapsed time for the transaction, expressed in microseconds

This time is included in the elapsed time recorded in TRNEDLDB, DLI/DB call time.

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

488

1E8

TRNESYNC

SYNC POINT ELAPSED TIME

Amount of sync point elapsed time for the transaction, expressed in microseconds

This time is included in TRNEDLTM field and the ESS elapsed time fields. Some ESS synchronization point time may not be included in the ESS elapsed time fields.

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Floating point (HFP)

4

492

1EC

TRNE1STD

SCHEDULE-TO-FIRST DL/I CALL ELAPSED TIME

Amount of schedule-to-first DL/I call elapsed time for the transaction, expressed in microseconds

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Binary

4

496

1F0

TRNELDLI

DURATION OF LAST DL/I CALL

Elapsed time of the transaction’s last DL/I call, expressed in microseconds

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Binary

4

500

1F4

TRNTCPU

TOTAL CPU TIME

Total amount of CPU time used by the transaction, expressed in microseconds

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).  This value is based on the setting of the CPU parameter in BBPARM member IMFECP00 and is provided in TOD STCK-format (Unsigned 64-bit binary number). For example: x'0000000000110FBE' converts to 00:00:00.000272 or 272 microseconds.

Binary

8

504

1F8

TRNSTCKE

TOD CLOCK SETTING AT TRANSACTION END TIME

TOD clock value for the transaction end time

Binary

8

512

200

TRNOTMAM

OTMA MEMBER NAME

Name of the OTMA TMEMBER that sent this transaction

Display

16

520

208

TRNFALSC

TRNFALSC

Number of false schedules

Binary

2

536

218

TRNRSENM

RSENAME

Recoverable Service Element name for the XRF complex

The active and alternate IMS systems in an XRF complex share this RSENAME.

Character

8

538

21A

TRNOTMAP

OTMA Map name

OTMA formatting map name for messages that came through OTMA

This element is used by the server to map output data streams. It is optional.

Character

8

546

222

TRNSTRTU

TRANSACTION START TIME, MIJU PORTION

Transaction start time MIJU portion

When this value is appended to the start time stored as element TRNSTRTD at displacement 100 064, it forms a timestamp that is expressed in microsecond granularity.

Binary

2

554

22A

TRNSTRTA

TRANSACTION START TIME, AQQS ADJUSTMENT

IMS Universal Time Clock (UTC) time adjustment value in quarters (AQQS)

This element is used to convert local time to UTC time. (The value for this element can be 0000 if IMETIME abends.)

Binary

2

556

22C

TRNSTOPU

TRANSACTION STOP TIME, MIJU PORTION

Transaction stop time MIJU portion

When this value is appended to the stop time stored as element TRNSTOPD at displacement 104 068, it forms a timestamp that is expressed in microsecond granularity.

Binary

2

558

22E

TRNSTOPA

TRANSACTION STOP TIME, AQQS ADJUSTMENT

IMS Universal Time Clock (UTC) time adjustment value in quarters (AQQS)

This element is used to convert local time to UTC time. (The value for this element can be 0000 if IMETIME abends.)

Binary

2

560

230

TRNNUOWP

NETWORK UOW ID

Display

20

562

232

TRNARVTH

TRANSACTION ARRIVAL TIME

Time of day when the transaction was submitted for processing, expressed in hours, minutes, seconds, tenths of a second, and hundredths of a second (hhmmssth)

When the MIJU element (TRNARVTJ at displacement 586 24A) is appended to this value, it forms a timestamp that is expressed in microsecond granularity, which provides a more precise timestamp than the transaction arrival time stored as TRNARIVT at displacement 116 074. (See the TRNARIVT transaction arrival time description in this table or more information about the value in this field).

Packed unsigned

4

582

246

TRNARVTJ

TRANSACTION ARRIVAL TIME, MIJU PORTION

Transaction arrival time MIJU portion

When this value is appended to the arrival time stored as element TRNARVTH at displacement 582 246, it forms a timestamp that is expressed in microsecond granularity.

Binary

2

586

24A

TRNMSCTH

MSC TRANSACTION ARRIVAL TIME

Binary

4

588

24C

TRNMSCTJ

MSC TRANSACTION ARRIVAL TIME, MIJU PORTION

For transactions that:

• Originate in another system in an MSC environment, set to the transaction arrival time (TRNARVTH at displacement 582 246), then the timestamp is adjusted according to the setting of the MSCCLOCK parameter in BBPARM member IMFECP00

• Originate in another system in an MSC environment, set to the MIJU portion of the transaction arrival time (TRNARVTJ at displacement 586 24A), then the timestamp is adjusted according to the setting of the MSCCLOCK parameter in BBPARM member IMFECP00

  When this value is appended to the arrival time stored as element TRNMSCTH at displacement 588 24C, it forms a timestamp that is expressed in microsecond granularity.

• Do not originate in an MSC environment, the value is zero

  UTC adjustment value (AQQS) for this element is stored as TRNXUTCA at displacement 376 178.

Binary

2

592

250

TRNWLMSC

WORKLOAD MANAGER SERVICE CLASS

Workload manager service class of the transaction

Display

8

594

252

TRNSMQGN

SMQ GROUP NAME

Shared message queues group name

Display

8

602

25A

TRNUOW

UOW FOR TRANSACTION

Display

34

610

262

TRNDLCMX

MAX DC CALL TIME

Maximum DC call time for this transaction or BMP

Binary

4

644

284

TRNDLDMX

MAX DB CALL TIME

Maximum DB call time for this transaction or BMP

Binary

4

648

288

TRNESSMX

MAX ESS CALL TIME

Maximum ESS call time for this transaction or BMP

Binary

4

652

28C

TRNDLWMX

MAX WAIT TIME (NOT FOR I/O)

Maximum wait time (not for I/O) for this transaction or BMP

Binary

4

656

290

TRNDLDTH

DLI DB OR ESS CALLS GREATER THAN OR EQUAL TO THRESHOLD

Number of DL/I DB or ESS calls greater than or equal to the value specified by DFTIME parameter

Binary

2

660

294

TRNDLCTH

DLI DC GREATER THAN OR EQUAL TO THRESHOLD

The number of DL/I DC calls greater than or equal to the value specified by DFTIME parameter

Binary

2

662

296

TRNDLDER

DLI CALL ERRORS

Number of DL/I calls with bad status codes, based on the DFDBCODE and DFDCCODE parameters in IMFECP00

Binary

2

664

298

TRNESSER

ESS CALL ERRORS

Number of ESS calls with bad return codes, based on the DFESCODE parameter in IMFECP00

Binary

2

666

29A

TRN1STCP

TRNE1STD SCHEDULE-TO-FIRST DL/I CALL CPU TIME

Amount of schedule-to-first DL/I call CPU time for the transaction, expressed in microseconds

The time is collected if the elapsed times flag (TRNETFLG) is on (at displacement 396 18C).

Binary

4

668

29C

TRNCAPPL

CICS APPLID

APPLID of a CICS system is the name by which it is known in the intercommunication network

Binary

8

740

2E4

TRNFALST

FALSE SCHED ELAPSED

Elapsed time of False Schedule transactions in microseconds

Binary

4

748

2EC

TRNXCPU

CPU AFTER TRN STOP IS SET

Binary

4

752

2F0

TRNDL3E 

DL3E MOD TRACE

Binary

2

756

2F4

TRNDBTSZ

TRNDBTSZ

Length of each DBD or DB2 variable segment

Binary

2

758

2F6

TRNEXTEN

FA extension

The offset from the start of the FA to the TRN extension prefix (see TRNEXTLN for the length of the extension)

Possible values are:

• 0, no FA extension exists
• Binary number, an extension exists starting at the offset indicated by the binary number

The extension is mapped by DSECTS TRXP, TRX1, TRX2, and TRXZ, which are in BBSAMP member IMETRNX. The extension starts with a prefix mapped by TRXP. The prefix indicates which of the extension subareas exist. Refer to the subarea DSECTs for detail about these areas. Users interested in IBM System z Integrated Information Processor (zIIP) and IBM System z Application Assist Processor (zAAP) usage should review the TRXZ DSECT. BMC recommends using the $TRNEXT macro to locate the extension and the sections within it. $TRNEXT is in BBSAMP.

Binary

2

760

2F8

TRNEXTLN

FA extension length

Length of the FA extension (see also TRNEXTEN)

Possible values are:

• 0, no FA extension exists
• Binary number, an extension exists and its length is indicated by the binary number

Binary

2

762

2FA

TRNXCKPC

COUNT OF CHECK POINTS AND SYNC POINTS

Number of check points and sync points taken during the execution of this transaction

Binary

4

764

2FC

TRNXCKPM

MAXIMUM LOCKS HELD

Maximum number of locks held between any two check points or sync points

Binary

4

768

300

TRNXCKPT

TOTAL LOCKS

Total number of locks held for all checkpoints

Divide this value by the number of check points and sync points to obtain the average number of locks per checkpoint.

Binary

4

772

304

TRNEWLMC

EWLM CORRELATOR

Enterprise Workload Management correlator

Binary

64

776

308

TRNOTCON

IMS CONNECT START TIME

TOD clock value when a message arrived to IMS Connect

This value is only available if the BMC Energizer for IMS Connect product is installed in the IMS Connect.

Binary

8

840

348

TRNCSYS

Z/OS SYSTEM NAME

The z/OS system name for CICS transactions

Binary

8

840

348

TRNOTSTC

IMS CONNECT STC OR JOB NAME

Name of the started task or job of the IMS Connect used for a message

This value is only available if Energizer for IMS Connect is installed in the IMS Connect.

Character

8

848

350

TRNOTIPT

DS XL2 PORT USED FOR INPUT MSG

Port used for input messages

Binary

2

856

358

TRNOTPRT

IMS CONNECT PORT ID

Port ID used by IMS Connect

This value is only available if Energizer for IMS Connect is installed in the IMS Connect.

Binary

2

858

35A

TRNOTIP

IMS CONNECT CLIENT IP ADDRESS

Client IP address used by IMS Connect for a message

This value is only available if Energizer for IMS Connect is installed in the IMS Connect.

Binary

4

860

35C

TRNOTCLN

IMS CONNECT CLIENT ID

Client ID used by IMS Connect for a message

This value is only available if Energizer for IMS Connect is installed in the IMS Connect.

Character

8

864

360

TRNOTUSR

OTMA SECURITY USER NAME

OTMA security user ID used by OTMA for a message

Character

8

872

368

TRNOTSTF

OTMA IMS STATE FLAG

Copy of the OTMA state flag, OMHDRIST

For more information about this flag byte, refer to the mapping supplied by IBM.

Binary

1

880

370

TRNOTSYF

OTMA SYNCHRONIZATION FLAG

Copy of the OTMA synchronization flag, OMHDRSYN

For more information about this flag byte, refer to the mapping supplied by IBM.

Binary

1

881

371

TRNOTSLF

OTMA SYNCH LEVEL FLAG

Copy of the OTMA synchronization level flag, OMHDRSLV

For more information about this flag byte, refer to the mapping supplied by IBM.

Binary

1

882

372

TRNOTCLF

OTMA CLIENT FLAG

Copy of the OTMA client flag, OMHDRCFL

For more information about this flag byte, refer to the mapping supplied by IBM.

Binary

1

883

373

TRNOTSCF

OTMA SECURITY FLAG

Copy of the OTMA security flag, OMSECFLN

For more information about this flag byte, refer to the mapping supplied by IBM.

Binary

1

884

374

TRNOTCOR

OTMA CORRELATOR

OTMA correlator

Character

16

885

375

TRNOTCLP

IMS CONNECT CLIENT PORT ID

Client port ID used by IMS Connect for a message

This value is only available if Energizer for IMS Connect is installed in the IMS Connect.

Binary

2

901

385

TRNMISCF

MISCELLANEOUS FLAG
• X'80'=BMC SUBZERO INDICATION
• X'40'=BMC SUBZERO DATA ERROR
• X'20'=TRNDSYS OR TRNMSYS SET

Binary

1

903

387

TRNOT_MQMID

TRN_MQMID

MQ Series message ID

Character

24

904

388

TRNOTEIP

TRNOTEIP

Energizer for IMS Connect IP address

Binary

4

928

3A0

--

RESERVED

Binary

4

932

3A4

TRNOVHD

TRNOVHD

Region overhead CPU in time-of-day (TOD) format

Binary

8

936

3A8

TRNW5GSP

TRN5GSP

HD get space IWAIT time in microseconds

Binary

4

944

3B0

TRNETERR

$ETIME ERROR

Binary

8

948

3B4

TRNDIAGC

CPU DIAGNOSTIC DATA AREA

Binary

11

956

3BC

TRNOVFL1

ITASTRAC FLAG

Indicates whether a schedule or an ACBLIB I/O occurred for the transaction, or if BILLOVHD=YES or BILLOVHD=SCHEDDLI

Type of transaction:

• TRNOVFL1 DS    X=BILLOVHD FLAGS               
• TRNOVACB EQU   X'80'=ACB I/O OCCURRED            
• TRNOVSCH EQU   X'40'=SCHEDULE OCCURRED

 Binary

1 

967

3C7 

--

Reserved

Binary

4

968

38C

TRNMSYS

MQ REMOTE SYSTEM NAME

Character

8

972

3CC

TRNDSYS

DB2 REMOTE SYSTEM NAME

Character

8

980

3D4

--

FIXED RECORD LENGTH

End of the fixed portion of the record

The fixed length portion of the record is followed by 0 to 500 database segments. Since the fixed length of the record could be increased by a PTF, the correct way to find the start of the first database segment is it to add the offset provided in element TRNDBTOF to the starting address or offset of the FA record.

--

--

988

3DC