Record format - fixed segment

TARECLEN

RECORD DESCRIPTOR WORD (RDW)

Length of the record

Binary

4

000

000

TARECID

RECORD IDENTIFICATION

Code that identifies this record as a transaction accounting record (value T)

Display

1

004

004

--

RESERVED AREA

Display

1

005

005

TARCDVER

RECORD VERSION

MainView for IMS product IRUF record version code:

• C'01'=MainView for IMS version 3.2.00 or earlier
• C'02'=MainView for IMS version 3.3.00 to 4.5.00
• C'03'=MainView for IMS version 4.6.00 or later

Display

2

006

006

TAID

TRANSACTION IDENTIFICATION

Group

32

008

008

TACUST

CUSTOMER ID

User-specified identification that relates this transaction to a specific user

This field is built by the Log Edit user exit routine. The default value is LTERM.

Display

18

008

008

TATRAN

TRANSACTION CODE

Transaction code that identifies this message

If *LINECHG, this value is a dummy transaction record created during IRUF summarization per MainView for IMS to contain terminal connect time charges.

For SAP transactions (SAP EXIT USED is Y), this field contains the SAP report ID, if available, or the SAP transaction code.

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

Display

8

026

01A

TAAPPC

APPC/IMS FLAG

• N=Non-APPC/IMS transaction
• Y=APPC/IMS transaction
• O=OTMA transaction

Display

1

034

022

TASYSID

SYSTEM IDENTIFICATION

Identification code for the IMS system on which this transaction was processed (specified as a parameter to BBPARM member IMFECP00)

Display

1

035

023

TAIMSLEV

IMS LEVEL

IMS release level under which this transaction was processed

Display

4

036

024

TATRANC

TRANSACTION CHARACTERISTICS

Group

24

040

028

TAPSBNAM

PROGRAM NAME

Name of the program (PSB) that processed this transaction

Display

8

040

028

TAREGID

REGION ID

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

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

Display

8

048

030

TACLASS

INPUT CLASS

Class used to assign the program to a specific message region by an initiator

Display

3

056

038

TARECTYP

RECORD TYPE

Type of information stored in this record:

• D=Detail level data
• S=Summary level data

Display

1

059

03B

TATRANT

TRANSACTION TYPE

Transaction processing mode:

• Blank=Standard - message processing transaction (MPP)
• B=Batch message processing transaction (BMP)
• C=Conversational (MPP or JMP)
• D=DBCTL CICS thread
• E=CPI-C driven program transaction (TPI)
• F=Fast Path message-driven transaction (MDP)
• N=Fast Path non-message-driven transaction (NDP)
• U=Fast Path utility transaction (FPU)

Display

1

060

03C

TARSPOPT

R OPTION

Response option flag

If equal to R, the record was created with the response option in effect and the other R fields are used.

Display

1

061

03D

TADTRCAT

DET TRANS CATEGORY (detail)

Category code assigned to transaction through user exit routine IMFCEXIT in Log Edit

This code is used to determine which set of response time thresholds is to be used in building the summary response segment in this record.

Binary

2

062

03E

TATIMEST

TIMESTAMPS

Timestamps are either detail or summarized as specified in TARECTYP (RECORD TYPE)

• For a detail record, the timestamps contain the dates and times for the time of arrival, start, and stop of a single transaction.

• For a summarized record, the timestamps identify a time range.

  Data is collected for the number of transactions processed (NO TRANSACTIONS) and summarized for the time range. The arrival timestamp contains the earliest date and time encountered. The stop timestamp contains the latest date and time encountered. The termination timestamp, reflecting transaction purge time, is not a currently supported data element.

Group

32

064

040

TAARVDT

TRANSACTION ARRIVAL DATE

Julian date (yyyyddd) when this transaction was submitted

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

Binary

4

064

040

TAARVTM

TRANSACTION ARRIVAL TIME

Time of day, in hundredths of seconds, when a transaction completes communication and message format processing and is placed in the input message queue or BALG

This timestamp is the arrival time of the original transaction for message switch transactions for which the original input came from a terminal.

This timestamp is set to the transaction start time for message switch transactions submitted by a non-message-driven BMP or JBP and for the pseudo transaction created for such a BMP, JBP, NDP, or FPU.

For transactions submitted from another system in an MSC environment, this timestamp is the arrival time in the processing system with the response option in effect; otherwise, it is the arrival time in the originating system.

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

Binary

4

068

044

TADATE

TRANSACTION START DATE

Julian date (yyyyddd) when processing for this transaction started

Binary

4

072

048

TASTRTM

TRANSACTION START TIME

Time of day, in hundredths of seconds, when processing for this transaction started

Binary

4

076

04C

TAENDDT

TRANSACTION STOP DATE

Julian date (yyyyddd) when processing of this transaction ended

Binary

4

080

050

TAENDTM

TRANSACTION STOP TIME

Time of day, in hundredths of seconds, when processing for this transaction ended

Binary

4

084

054

TATRMDT

TRANSACTION TERM DATE

Julian date (yyyyddd) when this transaction was purged

This field is currently not supported and is set to the TRANSACTION STOP date.

Binary

4

088

058

TATRMTM

TRANSACTION TERM TIME

Time of day, in hundredths of seconds, when processing on this transaction was purged

This field is currently not supported and is set to the TRANSACTION STOP time.

Binary

4

092

05C

TASECU

SECURITY IDS

Group

68

096

060

TALGTRNM

LOGICAL TERMINAL NAME

Name of the LTERM that submitted the transaction

A special LTERM name of ??-BLANK is supplied when no terminal input occurs. This value is in the pseudo transaction record that MainView for IMS creates for:

• A non-message-driven BMP or JBP (NDP - non-message-driven program)
• FPU (Fast Path utility)
• Any message switch transactions originating from a non-message-driven BMP or JBP

For DBCTL CICS threads, this field contains the four-byte CICS terminal identifier.

For APPC/IMS programs, this field contains the partner LU name.

Display

8

096

060

TAUSERID

SECURITY USER ID

User ID field, usually from the I/O PCB

The ID is used in connection with signon security. The 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 are true

For APPC/IMS transactions, the user ID is passed to IMS from APPC.

This field is equivalent to DB2 AUTHID.

For DBCTL CICS threads, this field contains the CICS user ID.

Display

8

104

068

TAAGN

AGN

Application group name assigned by the security system

Display

8

112

070

TAASID

ADDRESS SPACE ID

ASID for the region in which this transaction was processed

Binary

2

120

078

TAPG

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.

Display

2

122

07A

TARIMSID

IMS SYSTEM IDENTIFICATION

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

Display

4

124

07C

TARSMFID

SMF SYSTEM IDENTIFICATION

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

Display

4

128

080

TARVTAM

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

132

084

TARFLAG1

SPECIAL PROCESSING FLAG

Special LSO processing characteristics in effect for this transaction

This flag is one of the four IMS LSO options (N, Y, X, or S).

Display

1

140

08C

TAOSCODE

OS CODE

Operating system under which this transaction was processed

Display

3

141

08D

TAUSER

USER AREA

MainView for IMS uses the first 16 bytes of the user area to store the extra data items listed below

This data is not used in any Performance Reporter or Transaction Accountant offline processing, so it can be modified by the user without consequence. If a user exit places user data in the transaction log record, the data will be transferred to this user area.

Display

20

144

090

TASUMM

SUMMARY DATA

Group

128

164

09C

TATRNSN

NO TRANSACTIONS

Number of transactions processed

The field is set to a value of 1 for a detail record and contains a count of the number of times this transaction was processed during the summary time span.

Binary

4

164

0A4

TAINQTM

INPUT Q TIME

Amount of time, in hundredths of seconds, between arrival of the transaction in the input queue or BALG and the start time of processing

This field contains the sum of all queue wait times for the summary version record.

Binary

4

168

0A8

TAELAPSE

ELAPSED TIME

Amount of time, in hundredths of seconds, during which this transaction was actively being processed

This field contains the sum of all elapsed times for the summary version record.

Binary

4

172

0AC

TAMPROCP

MESSAGE REGION PROGRAM CPU TIME

Amount of CPU time, in thousandths of seconds, used by the application program in the message region to process this transaction

For DBCTL threads, the normal IMS message CPU time is replaced with the DRA THREAD CREATE and processing time. This time is not the normal TCB time from CICS or ODBA. It is the TCB created to attach to the IMS control region and process the CICS or ODBA work. It does not include the control region CPU time.

Since CICS does not report CPU time, there is no duplication of timings for CICS threads.

Binary

8

176

0B0

TAMDLICP

MESSAGE DL1 CPU TIME

Amount of message region CPU time, in thousandths of seconds, used by the DL/I analyzer to process database requests for this transaction

Binary

8

184

0B8

TAMBUFCP

MESSAGE BUFFER CPU TIME

Amount of message region CPU time, in thousandths of seconds, used by the IMS buffer handler during the processing of this transaction

If BHTO=OFF, this field is zero; CPU time is included in DL/I CPU.

Binary

8

192

0C0

TAMOPNCP

MESSAGE OPEN-CLOSE CPU TIME

Amount of dependent region CPU time, in thousandths of seconds, used to open or close databases for this transaction. Only Fast Path DEDBs are opened in the dependent region

Binary

8

200

0C8

TACDLICP

Control DL1 CPU TIME

Amount of control region CPU time, in thousandths of seconds, used by the DL/I analyzer to process the database requests for this transaction

If LSO =S, this field can contain CPU accumulated in DLISAS.

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

Binary

8

208

0D0

TACBUFCP

Control BUFFER CPU TIME

Amount of control region CPU time, in thousandths of seconds, used by the buffer handler module during the processing of this transaction

If BHTO=OFF or CPU=DEP or NONE, this field is zero.

Binary

8

216

0D8

TACOPNCP

CONTROL OPEN-CLOSE CPU TIME

Amount of control region CPU time, in thousandths of seconds, used by the DL/I analyzer to open and close required database while processing requests issued for this transaction

If LSO =S, this field can contain CPU accumulated in DLISAS.

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

Binary

8

224

0E0

TARUSER2

USER AREA 2

Field that can be modified by the user

Display

4

232

0E8

TATRNDB2

NUMBER DB2 TRANSACTIONS

Number of transactions that accessed DB2

This field is set to 1 for a detail record if any SQL calls were performed.

Binary

4

236

0EC

TAAKCORE

ALLOCATED KSTORAGE MINUTES

Number of KSTORAGE minutes, in thousandths of KSTORAGE minutes, consumed during transaction processing

KSTORAGE MINUTE = (ELAPSED TIME × STORAGE ALLOCATED)

Binary

8

240

0F0

TAUKCORE

USED KSTORAGE MINUTES

Number of KSTORAGE minutes, in thousandths of KSTORAGE minutes, used during transaction processing

KSTORAGE MINUTE = (ELAPSED TIME × STORAGE USED)

Binary

8

248

0F8

TACRALOC

STORAGE AVAILABLE

For IMS, this field contains the amount of free storage available after IMS initialization and program preloading (if used)

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

Binary

2

256

100

TACRUSED

STORAGE USED

Link-edited length of the program in 1 KB units

For DBCTL threads, this field is zero.

Binary

2

258

102

TARESSID

DB2 SUBSYSTEM ID

Subsystem ID of the DB2 system that the transaction accessed

Display

4

260

104

TASPRC

SYNC POINT RETURN CODE

For a transaction that accessed Fast Path databases, this value is the result of SYNC point processing

Binary

2

264

108

TABGQCT

BALANCING GROUP Q COUNT

For a message-driven transaction, this value is the number of transactions queued on the same balancing group when this transaction went through SYNC point processing

For a summarized IRUF, this field is summed for like transactions.

Binary

2

266

10A

TANBA

NORMAL BUFFER ALLOCATION

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

For a summarized IRUF, this field is summed for like transactions.

Binary

2

268

10C

TAOBA

OVERFLOW BUFFER ALLOCATION

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

For a summarized IRUF, this field is summed for like transactions.

Binary

2

270

10E

TABUSED

FAST PATH BUFFERS USED

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

For a summarized IRUF, this field is summed for like transactions.

Binary

2

272

110

TANCIC

FAST PATH CI CONTENTIONS

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

For a summarized IRUF, this field is summed for like transactions.

Binary

2

274

112

TANWFB

FAST PATH WAIT FOR BUFFERS

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

For a summarized IRUF, this field is summed for like transactions.

Binary

2

276

114

TARC

ROUTING CODE

For a Fast Path message-driven region, this field is the routing code used to schedule this transaction

Display

8

278

116

TAFLAG

FAST PATH FLAG

Fast Path characteristics of this transaction if it accessed Fast Path database:

• W=Transaction waited for the OBA latch

For a summarized IRUF, a counter from 0 to 9 that indicates the number of OBA latch waits

Display

1

286

11E

TAFLAG0

SPECIAL PROCESSING FLAG

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

Display

1

287

11F

TASUBID

SUBSYS ID FOR SYSEVENT

Display

4

288

120

TARESOPT

RESPONSE OPTION DATA

Group

68

292

124

TARSWCNT

R MSGSW COUNT

Number of message switches used to create this transaction (equals zero for transactions input from a terminal)

Available only with the response option in effect.

Binary

2

292

124

TARSENCT

R MSGSENT COUNT

Number of response messages sent to the originating terminal

For a detailed IRUF, if R MSGSENT DATE > 0, this field is 1. For a summarized IRUF, field is summed for like transactions. Available only with the response option in effect.

If this field overflows during summarization, the additional counts are kept in an overflow field.

Binary

2

294

126

TARDEQCT

R MSGDEQ COUNT

Number of response messages dequeued

For detailed IRUF, if R MSGDEQ DATE > 0, this field is 1. For summarized IRUF, field is summed for like transactions. Available only with the response option in effect.

If this field overflows during summarization, the additional counts are kept in an overflow field.

Binary

2

296

128

TARPRGDT

R ORIGINAL DATE

Julian date yyyyddd) when this message switch was submitted (same as transaction arrival date)

For MSC transactions, this value is the arrival time in the originating system.

Binary

4

298

12A

TARORGTM

R ORIGINAL TIME

Time of day, in hundredths of seconds, when this message switch was submitted (same as transaction arrival time)

For MSC transactions, this value is the arrival time in the originating system.

Binary

4

302

12E

TARARVDT

R ARRIVAL DATE

Julian date (yyyyddd) when this transaction arrived or the date of the message switch

Available only with the response option in effect and only in a detail record.

Binary

4

306

132

TARARVTM

R ARRIVAL TIME

Time of day, in hundredths of seconds, when this transaction arrived in the queue

For message switch transactions, it is the time the actual switched transaction was put in the message input queue; otherwise, this time is the transaction arrival time. Available only with the response option in effect and only in a detail record.

Binary

4

310

136

TARISRDT

R MSGISRT DATE

Julian date (yyyyddd) when a response message was inserted into the queue

If no response was made, this field is zero. Available only with the response option in effect and only in a detail record.

Binary

4

314

13A

TARISRTM

R MSGISRT TIME

Time of day, in hundredths of seconds, when a response message was inserted into the queue

If no response was made, this field is zero. Available only with the response option in effect and only in a detail record.

Binary

4

318

13E

TARSNTDT

R MSGSENT DATE

Julian date (yyyyddd) when a response message was sent to the originating terminal

If no response was made, this field is zero. Available only with the response option in effect and only in a detail record.

Binary

4

322

142

TARSNTTM

R MSGSENT TIME

Time of day, in hundredths of seconds, when a response message was sent to the originating terminal (first attempt to transmit)

If no response was made, this field is zero. Available only with the response option in effect and only in a detail record.

Binary

4

326

146

TARDEQDT

R MSGDEQ DATE

Julian date (yyyyddd) a response message was dequeued

If no response was made, the field is zero. Available only in a detail record.

Binary

4

330

14A

TARDEQTM

R MSGDEQ TIME

Time of day, in hundredths of seconds, when a response message was dequeued (after completion of transmission)

If no response was made, this field is zero. Available only with the response option in effect and only in a detail record.

Binary

4

334

14E

TALINE

R INPUT LINE

Input line number

Binary

2

338

152

TAPTERM

R INPUT PTERM

Input physical terminal

Binary

2

340

154

TARINQ

R INPUT Q

Amount of time, in hundredths of seconds, during which this transaction waited in the input queue for processing

It differs from INPUT Q TIME only in the case of message switches, where it is measured from the arrival of the message switch transaction on the queue. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

4

342

156

TAROUTQ

R OUTPUT Q

Amount of time, in hundredths of seconds, during which this transaction waited in the output queue for processing

Output queue time is measured from R MSGISRT TIME to R MSGSENT TIME. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

4

346

15A

TARDEQ

R DEQ

Amount of time, in hundredths of seconds, during which this transaction waited to be dequeued

Dequeue time is measured as R MSGDEQ TIME minus R MSGSENT TIME. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

4

350

15E

TARRSP

R RESPONSE

Amount of time, in hundredths of seconds, from the transaction arrival time (of the original transaction) to the first attempt to transmit an output message to the originating terminal

If no response was made, this field is set to zero. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

4

354

162

TARMSGLV

R MSGSW LEVEL

Level of message switching to reach this transaction

A value of 1 indicates that the program processing the originating transaction from the terminal created this transaction as a message switch. A value of 2 indicates that another program was also invoked. Reported only in response reports and only with the response option in effect.

Binary

2

358

166

TACSW

LTERM/SMQ/RESP flag

Binary

1

360

168

TAMSFI2

PSTMSFI2

Binary

1

361

169

TAPSTNO

PST NUMBER

Binary

2

362

16A

--

RESERVED

Binary

2

364

16C

TABASCHG

BASIC RESOURCE CHARGES

Charges for use of the basic resources

Group

24

366

16E

TACRACHG

STORAGE ALOC CHG

Charge for the number of ALLOCATED KSTORAGE MINUTES

The charge is expressed in dollars and tenths of a cent (999,999.999).

Binary

4

366

16E

TACRUCHG

STORAGE USED CHG

Charge for the number of USED KSTORAGE MINUTES used

The charge is expressed in dollars and tenths of a cent (999,999.999).

Binary

4

370

172

TAMSPCHG

MSG PROG CPU CHG

Charge for the number of message region CPU seconds used

The charge is expressed in dollars and tenths of a cent (999,999.999).

Binary

4

374

176

TAMSDCHG

MSG DL1 CPU CHG

Charge for the number of message region DL/I CPU seconds used

The charge is expressed in dollars and tenths of a cent (999,999.999).

Binary

4

378

17A

TAMSCCHG

CTL DL1 CPU CHG

Charge for the number of control region DL/I CPU seconds used

The charge is expressed in dollars and tenths of a cent (999,999.999).

Binary

4

382

17E

TACDCHG

MINIMUM CHARGE

Minimum transaction charge, expressed in dollars and tenths of a cent (999,999.999)

Binary

4

386

182

--

RESERVED

Display

4

390

186

TACHGSUM

TRANSACTION CHARGE AREA

Total charges for the processing requirements for this transaction

Group

20

394

18A

TARESCHG

RESOURCE CHARGE

Sum charge for all basic resource uses including storage, CPU times, database usage, and terminal activity

The charge is expressed in dollars and tenths of a cent (999,999.999).

Binary

4

394

18A

TAUNTCHG

UNIT CHARGE

Charge applied when the transaction has a special charged based on a charge per execution, as opposed to a charge based on resource usage

This field is zero if a special unit charge is not specified for this transaction.

Binary

4

398

18E

TAPROCHG

PRORATE CHARGE

Marginal increase or decrease in the base charge as a result of a discount or mark-up associated with a specified customer

This field is zero if a prorated charge is not specified for this customer's transactions.

Binary

4

402

192

TABILCHG

BILLABLE CHARGE

Final charge applied to this transaction

If this transaction is charged a per execution charge (for example, a unit charge of $.12 per execution), this field equals the sum of the UNIT CHARGE and PRORATE CHARGE fields. If this transaction is charged on the resource usage incurred, this field equals the sum of the RESOURCE CHARGE, MINIMUM CHARGE, and PRORATE CHARGE fields.

Binary

4

406

196

TAVARCHG

CHARGE VARIANCE

Difference between the RESOURCE CHARGE and UNIT CHARGE fields when the transaction is charged on a unit-charge basis

This field is zero if a unit charge option is not invoked.

Binary

4

410

19A

TAFLG1

R MSGSENT COUNT OVERFLOW FLAG

If Y, the halfword MSGSENT count at offset X'122' overflowed

Display

1

414

19E

TAOSENCT

R MSGSENT OVERFLOW COUNT

Overflowed value

The total of MSGSENT count is the sum of the fullword counter and the halfword counter.

Binary

4

415

19F

TAFLG2

R MSGDEQ COUNT OVERFLOW FLAG

if Y, the halfword MSGDEQ count at offset X'124' overflowed

Display

1

419

1A3

TAODEQCT

R MSGDEQ OVERFLOW COUNT

Overflowed value

The total of MSGDEQ count is the sum of the fullword counter and the halfword counter.

Binary

4

420

1A4

TARESSCP

DEPENDENT REGION DB2 CPU TIME

Amount of dependent region CPU time, in thousandths of seconds, used by the transaction to process DB2 requests

Binary

8

424

1A8

TAESSCHG

DB2 CPU CHARGE

Charge for the number of dependent region DB2 seconds used

The charge is in dollars and tenths of a cent (999,999.999).

Binary

4

432

1B0

TASAPX

SAP EXIT USED

• Y=SAP exit used
• N=SAP exit not used

Display

1

436

1B4

TASQUOW

SHARED Q UOW (IMSID/STCK)

Group

16

437

1B5

TASQOIMS

TASQOIMS

Originating IMS ID for shared queue unit of work (UOW)

Display

8

437

1B5

TASQOSTC

TASQOSTC

Originating STCK value for shared queue UOW

Binary

8

445

1BD

--

RESERVED AREA

Display

1

453

1C5

TANOSEGS

NUMBER OF VARIABLE SEGMENTS

The number of variable segments for the transaction

This number is dependent on Event Collector data collection parameter options set in IMFECP00 that are in effect during processing.

The value indicates different information for different types of variable segments:

• For databases, the usage and cost statistics for processing of this transaction accessing any DL/I database
• For DB2, the usage and cost statistics for processing of this transaction accessing any DB2 subsystem
• For responses, the statistics quantifying the various response time groupings experienced in processing this transaction (this segment type exists only in the summary version record)

Binary

2

454

1C6

TASMQGPN

SMQ GROUP NAME

Shared message queues group name

Display

8

456

1C8

TAABNCOD

TRANSACTION ABEND CODE

The abend code for a transaction abend

The value is:

• Sxxx for a system abend
• Uyyy for a user abend
• Blank if the transaction did not abend

Display

4

464

1D0

--

RESERVED

Display

8

468

1D4

TAWLMSC

WORKLOAD MANAGER SERVICE CLASS

Workload manager service class of the transaction

Display

8

476

1DC

--

RESERVED

Display

4

484

1E4

TAXORGSW

R-ORIGINAL MSGSW - STCK (higher precision than R ARRIVAL TIME)

Time of day, in microseconds, when this transaction arrived in the queue

For message switch transactions, it is the time the actual switched transaction was put in the message input queue; otherwise, this time is the transaction arrival time. Available only with the response option in effect and only in a detail record.

Binary

8

488

1E8

TAXORGAR

R-ORIGINAL MSC - STCK (higher precision than R ORIGINAL TIME)

Time of day, in microseconds, when this message switch was submitted (same as transaction arrival time)

For MSC transactions, this value is the arrival time in the originating system.

Binary

8

496

1F0

TAXMSCAR

R-DESTINATION MSC - STCK

arrival time of this MSC transaction, expressed in STCK value

Binary

8

504

1F8

TAXARVD1

R-ARRIVAL FROM IMETRN - STCK

Arrival time for BMP, DBT, NDP, and MDP transactions, which is usually the same as the transaction start time

Binary

8

512

200

TAXARVDT

R-ARRIVAL DATE TIME - STCK (higher precision than R ARRIVAL TIME)

Time of day, expressed in STCK value, when this transaction arrived in the queue

For message switch transactions, it is the time the actual switched transaction was put in the message input queue; otherwise, this time is the transaction arrival time. Available only with the response option in effect and only in a detail record.

Binary

8

520

208

TAXISRDT

R-MSG INSERT DATE TIME - STCK

Output message insert time, expressed in STCK value

Binary

8

528

210

TAXSNTDT

R-MSG SENT DATE TIME - STCK

Output message sent time, expressed in STCK value

Binary

8

536

218

TAXDEQDT

R-MSG DEQUEUE DATE TIME - STCK

Message dequeue time, expressed in STCK value

Binary

8

544

220

TAXINQTM

RESPONSE OPTION INPUT QUEUE TIME

Input queue time for the message switch using destination arrival time, expressed in microseconds

Binary

8

552

228

TAXINQ

RESPONSE OPTION INPUT QUEUE TIME (higher precision than R INPUT Q)

Amount of time, in microseconds, during which this transaction waited in the input queue for processing

It differs from INPUT Q TIME only in the case of message switches, where it is measured from the arrival of the message switch transaction on the queue. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

8

560

230

TAXOUTQ

RESPONSE OPTION OUTPUT QUEUE TIME (higher precision than R OUTPUT Q)

Amount of time, in hundredths of seconds, during which this transaction waited in the output queue for processing

Output queue time is measured from R MSGISRT TIME to R MSGSENT TIME. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

8

568

238

TAXDEQ

RESPONSE OPTION DEQUEUE TIME (higher precision than R DEQ)

Amount of time, in microseconds, during which this transaction waited to be dequeued

Dequeue time is measured as R MSGDEQ TIME minus R MSGSENT TIME. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

8

576

240

TAXRSP

RESPONSE OPTION RESPONSE TIME (higher precision than R RESPONSE)

Amount of time, in microseconds, from the transaction arrival time (of the original transaction) to the first attempt to transmit an output message to the originating terminal

If no response was made, this field is set to zero. Available only with the response option in effect. This time is summarized if all records were created with this option.

Binary

8

584

248

TAXTCPU

TOTAL CPU BY TRAN

Application program CPU time, expressed in microseconds

Binary

8

592

250

TAXSTART

TRAN START - TRNSTCK - STCK

Transaction start time in STCK value

Binary

8

600

258

TAXENDTM

TRAN END - TRNSTCKE - STCK

Transaction stop time in STCK value

Binary

8

608

260

TARW1OTH

MISC IWAIT MICS

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

616

268

TARW2OTH

SYNC MISC IWAIT MICS

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

620

26C

TARW2LCH

SYNC LATCH IWAIT MICS

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

624

270

TARW2IOV

SYNC VSAM I/O IWAIT MICS

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

628

274

TARW2IOO

SYNC OSAM I/O IWAIT MICS

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

632

278

TARW3OTH

DLI/TM MISC IWAIT MICS

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

636

27C

TARW3LCH

DLI/TM LATCH IWAIT MICS

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

640

280

TARW4OTH

OPN/CLS MISC IWAIT MICS

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

644

284

TARW4DBR

OPN/CLS DBRC IWAIT MICS

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

648

288

TARW4IO

OPN/CLS I/O IWAIT MICS

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

652

28C

TARW5OTH

DLI/DB MISC IWAIT MICS

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

656

290

TARW5LCH

DLI/DB LATCH IWAIT MICS

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

660

294

TARW5LCK

DLI/DB LOCK IWAIT MICS

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

664

298

TARW5IOV

DLI/DB VSAM IWAIT MICS

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

668

29C

TARW5IOO

DLI/DB OSAM IWAIT MICS

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

672

2A0

TARW5IOD

DLI/DB DEDB IWAIT MICS

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

676

2A4

TAREAPPL

APPL ELAPSED TIME MICS

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

680

2A8

TAREDLTM

DLI/TM ELAPSED TIME MICS

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

684

2AC

TAREDLDB

DLI/DB ELAPSED TIME MICS

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

688

2B0

TAREDB2

DB2 ELAPSED TIME MICS

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

692

2B4

TAREMQS

MQS ELAPSED TIME MICS

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

696

2B8

TAREOESS

ESS ELAPSED TIME MICS

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

700

2BC

TAREOPCL

OP/CL ELAPSED TIME MICS

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

704

2C0

TARESYNC

SYNC ELAPSED TIME MICS

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

708

2C4

TARE1STD

SCHD TO 1ST DLI MICS

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

712

2C8

TARELDLI

DLI LAST CALL ELAP MICS

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

716

2CC

TARFALST

FALSE SCHED ELAP MICS

Time at which IMS unsuccessfully scheduled the transaction in the shared message queue environment

Binary

4

720

2D0

TARXCPU

CPU AFTER TRN STOP IS SET

Total amount of CPU time, expressed in microseconds, used by the transaction after the transaction stop flag is set

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.

Binary

4

724

2D4

TARXCKPC

COUNT OF CPK/SYNCPOINTS

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

Binary

4

728

2D8

TARXCKPM

MAX LOCKS HELD (HWMRK)

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

Binary

4

732

2DC

TARXCKPT

TOTAL LOCKS HELD, ALL CHKPT XCHKPT/XCKPC=AVG LOCKS PER

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

736

2E0

TAROTCON

IMS CONNECT START TIME

STCK 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

740

2E4

TAROTSTC

IMS CONNECT STC/JOBN

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.

Display

8

748

2EC

TAROTPRT

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

756

2F4

TAROTMCL

OTMA CLIENT TYPE

• C'M' indicates that the transaction came from an OTMA IBM WebSphere MQ client.
• C'I' indicates that the transaction came from an OTMA IMS Connect client.
• C'P' indicates that the transaction came from an OTMA Synchronous Program Switch client.

Display

1

758

2F6

TARFLAG0

FLAG BYTE 0

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

759

2F7

TAROTIP

IMS CON CLIENT IP ADDR

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

760

2F8

TAROTCLN

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.

Display

8

764

2FC

TAROTUSR

OTMA SECURITY USER ID

OTMA security user ID used by OTMA for a message

Display

8

772

304

TAROTSTF

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

780

30C

TAROTSYF

OTMA SYNCH FLAG

Copy of the OTMA synchronization flag, OMHDRSYN

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

Binary

1

781

30D

TAROTSLF

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

782

30E

TAROTCLF

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

783

30F

TAROTSCF

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

784

310

TAROTCOR

OTMA CORRELATOR

OTMA correlator

Display

16

785

311

TAROTCLP

IMS CON 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

801

321

TAROTMAM

OTMA TMEMBER NAME

Name of the OTMA TMEMBER that sent this transaction

Display

16

803

323

TARFALSC

NUMBER OF FALSE SCHEDULES

Number of times IMS unsuccessfully scheduled the transaction in the shared message queue environment

Binary

2

819

333

TARRSENM

RSE NAME

Recoverable Service Element name for the XRF complex

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

Display

8

821

335

TAROTMAP

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.

Display

8

829

33D

TARSTRTU

TRAN. START TIME- MIJU

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

837

345

TARSTRTA

TRAN. START TIME- AQQS

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

839

347

TARSTOPU

TRAN. STOP TIME- MIJU

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

841

349

TARSTOPA

TRAN. STOP TIME- AQQS

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

843

34B

TARCAPPL

CICS APPLID

CICS application ID of the MRO/AOR that connected to IMS DBCTL

Display

8

845

34D

TARFLAG3

OTMA FLAG

X'80' indicates an OTMA transaction

Binary

1

853

355

--

RESERVED

Display

1

853

355

TARMISCF

MISC FLAG • X'80'=BMC SUBZERO INDICATION • X'40'=BMC SUBZERO DATA ERROR

Binary

1

854

356

TARMISCF

TXMPROCP

MSG PROGRAM CPU TIME

Amount of CPU time attributed to the program for the transaction, expressed in microseconds

Binary

8

856

358

TXMDLICP

MSG DLI CPU TIME

Amount of CPU time attributed to DLI for the transaction, expressed in microseconds

Binary

8

864

360

TXMBUFCP

MSG BUFFER HANDLER CPU TIME

Amount of CPU time attributed to IMS buffer handling for the transaction, expressed in microseconds

Binary

8

872

368

TXMOPNCP

MSG OPEN/CLOSE CPU TIME

Amount of CPU time attributed to IMS OPEN/CLOSE processing for the transaction, expressed in microseconds

Binary

8

880

370

TXCDLICP

CTL DLI CPU TIME

Amount of CPU time attributed to IMS DLI for the transaction, expressed in microseconds

Binary

8

888

378

TXCBUFCP

CTL BUFFER HANDLER CPU TIME

Amount of CPU time attributed to IMS buffer handling for the transaction, expressed in microseconds

Binary

8

896

380

TXCOPNCP

CTL OPEN/CLOSE CPU TIME

Amount of CPU time attributed to IMS OPEN/CLOSE activities for the transaction, expressed in microseconds

Binary

8

904

388

TAXESSCP

DB2 CPU TIME

Amount of CPU time attributed to DB2 for the transaction, expressed in microseconds

Binary

8

912

390

TAXZTCPU

TOTAL DEP RGN APPL CPU + NORMOALIZED TIME ON ZAAP & ZIIP

Total dependent region application CPU time including normalized time on zAAP or zIIP

Binary

8

920

398

TAXZONCP

TOTAL DEP RGN APPL CPU TIME EXCLUDING TIME ON ZAAP & ZIIP

Total dependent region application CPU time excluding any time on a zIIP or zAAP

Binary

8

928

3A0

TAXZAOCP

ZAAP ON CP TIME

Amount of dependent region zAAP eligible time that ran on a standard CP

Binary

8

936

3A8

TAXZIOCP

ZIIP ON CP TIME

Amount of dependent region zIIP eligible time that ran on a standard CP

Binary

8

944

3B0

TARSDCPU

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

The following conditions apply:

• The time 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

952

3B8

TARSBCPU

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

The following conditions apply:

• 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

960

3C0

TARSOCPU

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.

The following conditions apply:

• Bit 51 is equal to one microsecond
• For all Event Collector CPU data collection parameter options except ALL, this field is zero

Binary

8

968

3C8

TARDLCMX

MAX DC CALL TIME

Maximum DC call time for this transaction or BMP

Binary

4

976

3D0

TARDLDMX

MAX DB CALL TIME

Maximum DB call time for this transaction or BMP

Binary

4

980

3D4

TARESSMX

MAX ESS CALL TIME

Maximum ESS call time for this transaction or BMP

Binary

4

984

3D8

TARDLWMX

MAX WAIT TIME (NOT FOR I/O)

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

Binary

4

988

3DC

TARDLDTH

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

992

3E0

TARDLCTH

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

994

3E2

TARDLDER

DLI CALL ERRORS

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

Binary

2

996

3E4

TARESSER

ESS CALL ERRORS

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

Binary

2

998

3E6

TAR1STCP

TARE1STD 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) in X'FA' (IMETRN).

Binary

4

1000

3E8

TAROT_MQMID

TAROT_MQMID

MQ Series message ID

Display

24

1004

3EC

TAROTEIP

TAROTEIP

Energizer for IMS Connect IP address

Binary

4

1028

404

TARW5GSP

HD get space IWAIT time in microseconds

Binary

4

1032

408

TARPCBA

PCB (TERMINAL) SEGMENT AREA

Usage and cost statistics for the logical terminals used to submit this transaction

See Record-format-terminal-segment for storage description.

Group

192

1152

480