IFCID 003 - DDF Data by Location

This topic shows detailed information about Record Trace - IFCID 003 - DDF Data by Location.

Record trace - IFCID 003 - DDF Data by Location

The field labels shown in the following sample layout of Record Trace - IFCID 003 - DDF Data by Location are described in the following section. 


DDF DATA BY LOCATION

TYPE.......................: PACKAGE                        ROLLED NBR THREADS.........:          1
LOCATION NAME (LONG):        ::FFFF:9.65.12.94
LOCATION NAME (SHORT)......: ::FFFF:9.65.12.9               FLAGS......................: X'00'

ABORT REQUESTS RECEIVED....:                     0          ABORT REQUESTS SENT........:                     0
BLKS RECV USING BLK FETCH..:                     0          BLKS TRANS USING BLK FETCH.:                     2
BYTES RECV FROM REMOTE ....:                   819          BYTES SENT TO REMOTE.......:                   752
CONV REQS QUEUED BY DDF....:                     0          CONV INITIATED FR REMOTE...:                     1
CONV INITIATED FR LOCAL....:                     0          CONV TERMINATED FR LOCAL...:                     0
COMMIT REQS RECV FR REQ/COO:                     1          COMMIT REQS SENT TO SRV/PAR:                     0
MSGS RECV FR REMOTE........:                     8          MSGS SENT TO REMOTE........:                     8
ROWS OF DATA RETR FR REMOTE:                     0          ROWS OF DATA SENT TO REMOTE:                     1
SQL STMT RECEIVED FR REMOTE:                     3          SQL STMT SENT TO REMOTE....:                     0
LOCAL ELAPSED TIME.........:              0.000000          INDOUBT THREADS ...........:                     0
TYPE.......................: ROLLUP                         ROLLED NBR THREADS.........:          9
LOCATION NAME (LONG):        PMODA11                                                               
LOCATION NAME (SHORT)......: PMODA11                        FLAGS......................: X'10'
TYPE (Either ROLLUP, ROLSUM OR PACKAGE)
The flag byte:
X'20'
This value is shown if DRDA is used to communicate with the server.
X'40'
This value is shown if DB2 private protocol is used to communicate with the server.

All other values shown in this field are serviceability.

Field Name: QLACFLGS

LOCATION NAME (LONG)

The name of the remote location with which this information is associated. If the local location is the requester, this field is a server location. If the local location is a server location, this field is the requester location. An allied thread is created at a DB2 requester, and a database access thread is created at a DB2 server. An accounting record is for either a requester or a server, but not for both.

This field is invalid if summary rollup data is present. In Accounting this field is set to *ROLSUM*.

Field Name: QLACLOCN

This is an exception field.

LOCATION NAME (SHORT)

The name of the remote location with which this information is associated. If the local location is the requester, this field is a server location. If the local location is a server location, this field is the requester location. An allied thread is created at a DB2 requester, and a database access thread is created at a DB2 server. An accounting record is for either a requester or a server, but not for both.

This field is invalid if summary rollup data is present. In Accounting this field is set to *ROLSUM*.

Field Name: QLACLOCN

This is an exception field.

ABORT REQUESTS RECEIVED

The number of abort requests received from the requester (single-phase commit protocol) and backout requests received from the coordinator (two-phase commit protocol).

Field Name: QLACABRR

This is an exception field.

BLKS RECV USING BLK FETCH

The number of blocks received using block fetch. This value is maintained at the requester location.

Field Name: QLACBRBF

This is an exception field.

BYTES RECV FROM REMOTE

The number of bytes the server location received from the requester location.

More bytes of data might be sent from the server location than are received by the requester, because of the way in which distributed SQL statements are processed internally.

Field Name: QLACBYTR

This is an exception field.

CONV REQS QUEUED BY DDF

A number of conversation requests queued by DDF that are waiting for allocation. This value is maintained at the requester location.

If the value is a large number, you might want to increase the limit for the number of conversations.

Field Name: QLACCNVQ

This is an exception field.

CONV INITIATED FR LOCAL

The number of conversations (both successful and unsuccessful) initiated by the requester location to be executed at the server location. This number is maintained at the requester.

Field Name: QLACCNVS

This is an exception field.

COMMIT REQS RECV FR REQ/COO

The number of commit requests received from the requester (single-phase commit protocol) and committed requests received from the coordinator (two-phase commit protocol).

Field Name: QLACCOMR

This is an exception field.

MSGS RECV FR REMOTE

The number of messages received from the location. This value is maintained at the location where the messages were received.

More messages might be sent from the server location than are received by the requester because of the way in which distributed SQL statements are processed internally.

Field Name: QLACMSGR

This is an exception field.

ROWS OF DATA RETR FR REMOTE

The number of rows of data retrieved from the server location. This value is maintained at the requester location.

Special Considerations:
  1. The number of rows received from the server location does not include either the SQLDA or SQLCA.
  2. Block fetch can significantly affect the number of rows sent across the network. When used with non-UPDATE cursors, block fetch puts as many rows as possible into the message buffer, and transmits the buffer across the network without requiring a VTAM® message. Consequently, more rows of data might be sent from the server location than are received by the reporting (requester) location. This is especially true when DB2 private protocol is used because multiple blocks can be transmitted from the server with no intervening messages sent by the requester.

Field Name: QLACROWR

This is an exception field.

SQL STMT RECEIVED FR REMOTE

The number of SQL statements received from the requester location.

Field Name: QLACSQLR

This is an exception field.

LOCAL ELAPSED TIME

The elapsed time at the requester location until the database access agent completed its work, including DB2 processing time and network time. This value is maintained at the requester location and is calculated by accumulating the difference between the store clock values obtained before and after each network request.

Field Name: QLACCPUL

ROLLED NBR THREADS

The number of threads to roll data into this QLAC data section. Non-rollup QLACs have a value of 1 and rollup QLACs have a value of 1 or more.

Field Name: QLACRLNU

FLAGS
The flag byte:
X'20'
This value is shown if DRDA is used to communicate with the server.
X'40'
This value is shown if DB2 private protocol is used to communicate with the server.

All other values shown in this field are serviceability.

Field Name: QLACFLGS

ABORT REQUESTS SENT

The number of abort requests sent to the server (single-phase commit protocol) and backout requests sent to the participant (two-phase commit protocol).

Field Name: QLACABRS

This is an exception field.

BLKS TRANS USING BLK FETCH

The number of blocks transmitted using block fetch. This value is maintained at the server location.

Field Name: QLACBTBF

This is an exception field.

BYTES SENT TO REMOTE

The number of bytes the server location sent to the requester location. This value is maintained at the server location.

More bytes of data might be sent from the server location than are received by the requester due to the way in which distributed SQL statements are processed internally.

Field Name: QLACBYTS

This is an exception field.

CONV INITIATED FR REMOTE

A count of conversations initiated by the requester.

This number is updated at the server location.

Field Name: QLACCNVR

This is an exception field.

CONV TERMINATED FR LOCAL

The number of terminated conversations in the server block (DB2 private protocol only). It is maintained at the requester location.

This number can be different from the number of successful conversation allocations, because some conversations might not have been terminated when the accounting record was written.

Field Name: QLACCNVT

This is an exception field.

COMMIT REQS SENT TO SRV/PAR

The number of commit requests sent to the server (single-phase commit protocol) and committed requests sent to the participant (two-phase commit protocol).

Field Name: QLACCOMS

This is an exception field.

MSGS SENT TO REMOTE

The number of messages sent to the location. It is maintained at the location where the messages originated.

Field Name: QLACMSGS

This is an exception field.

ROWS OF DATA SENT TO REMOTE

The number of rows sent from the server location to the requester location. The value includes SQLDA and is maintained at the server location.

Field Name: QLACROWS

This is an exception field.

SQL STMT SENT TO REMOTE

The number of SQL statements sent to the server location. This value is maintained at the requesting location.

Field Name: QLACSQLS

This is an exception field.

INDOUBT THREADS

The number of threads that went indoubt with the remote location as coordinator (two-phase commit operations only). It is maintained at the participant and indicates that the communication with the coordinator was lost.

Field Name: QLACINDT

This is an exception field.

PRID REMOTE SITE
The original DB2® field specifies the information in the following field names of the remote requester or server location:
PRODUCT ID
It consists of 3 characters and can have the following values:
Original ID from DB2 Shown as
DSN DB2
ARI SQL/DS
QSQ DB2/400
SQL COMMON SERV
JCC JDBC DRIVER
'000000'X, '404040'X N/P
Other Original ID from DB2
Note:
  • If the record is written at the application requester location, or if summary rollup data is available, N/P is shown in Accounting TRACE and REPORT.
  • In Accounting FILE and SAVE DDF tables, BLANK is shown.
PRODUCT VERSION (PROD VERSION)
It consists of 5 digits and is shown as VvvRrrMm , where:
vv
Version level
rr
Release level
m
Modification level
Note: For DDF/RRSAF rollup records, the product ID and product version contain a value derived from the last thread to rollup. For query parallelism rollup threads, the value is derived from the parent record.

Field Name: QLACPRID