Distributed Activity - Requester

This topic shows detailed information about "Accounting - Distributed Activity - Requester".

This block shows the information provided for the requester of the distributed activity.

In the following example both layouts are shown, the report layout followed by the trace layout.

Accounting - Distributed Activity - Requester

The field labels shown in the following sample layout of "Accounting - Distributed Activity - Requester" are described in the following section.

Report:

---- DISTRIBUTED ACTIVITY -------------------------------------------------------------------------------------------------          
REQUESTER      : ::FFFF#1            #COMMIT(1) RECEIVED:       2    MESSAGES SENT    :     10.50    ROWS SENT    :    0.00          
PRODUCT ID     : JDBC DRIVER         #ROLLBK(1) RECEIVED:       0    MESSAGES RECEIVED:     10.50    BLOCKS SENT  :    0.00          
PRODUCT VERSION: V3 R65M0            SQL RECEIVED       :    5.50    BYTES SENT       :    576.50    #DDF ACCESSES:       2          
METHOD         : DRDA PROTOCOL                                       BYTES RECEIVED   :   2287.50    #RLUP THREADS:       2          
CONV.INITIATED :             1.00                                    #THREADS INDOUBT :         0                                    

Trace:

---- DISTRIBUTED ACTIVITY -----------------------------------------------------------------------------                             
REQUESTER          : ::FFFF#1            ROLLBCK(1) RECEIVED:         0    THREADS INDOUBT    :       0                             
PRODUCT ID         : JDBC DRIVER         SQL RECEIVED       :         4    ROWS SENT          :       0                             
PRODUCT VERSION    : V3 R65M0            MESSAGES SENT      :         9    BLOCKS SENT        :       0                             
METHOD             : DRDA PROTOCOL       MESSAGES RECEIVED  :         9    CONVERSAT.INITIATED:       1                             
COMMITS(1) RECEIVED:                1    BYTES SENT         :       516    NBR RLUP THREADS   :       1                             
                                         BYTES RECEIVED     :      2122
Report - REQUESTER

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.

Report - PRODUCT ID
Start of changeThe 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.
End of change

Field Name: QLACPRID

Report - PRODUCT VERSION
Start of changeThe 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.
End of change

Field Name: QLACPRID

Report - METHOD

The method of access: DB2 private protocol, DRDA protocol, or both.

This field is invalid if unique or summary rollup data is present. It can have the following value in:
  • Accounting Trace and Report: N/P
  • The Accounting FILE and SAVE PROGRAM table: blank

Field Name: ADPROTOC

Report - CONV.INITIATED

A count of conversations initiated by the requester.

This number is updated at the server location.

Field Name: QLACCNVR

Report - #COMMIT(1) RECEIVED

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.

Report - #ROLLBK(1) 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.

Report - SQL RECEIVED

The number of SQL statements received from the requester location.

Field Name: QLACSQLR

This is an exception field.

Report - MESSAGES SENT

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.

Report - MESSAGES RECEIVED

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.

Report - BYTES SENT

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.

Report - BYTES RECEIVED

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.

Report - #THREADS INDOUBT

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.

Report - ROWS SENT

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.

Report - BLOCKS SENT

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

Field Name: QLACBTBF

This is an exception field.

Report - #DDF ACCESSES

The number of occurrences of the remote location and method pair.

Field Name: ASDDF

This is an exception field.

Report - #RLUP 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

Trace - REQUESTER

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.

Trace - PRODUCT ID
Start of changeThe 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.
End of change

Field Name: QLACPRID

Trace - PRODUCT VERSION
Start of changeThe 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.
End of change

Field Name: QLACPRID

Trace - METHOD

The method of access: DB2 private protocol, DRDA protocol, or both.

This field is invalid if unique or summary rollup data is present. It can have the following value in:
  • Accounting Trace and Report: N/P
  • The Accounting FILE and SAVE PROGRAM table: blank

Field Name: ADPROTOC

Trace - COMMITS(1) RECEIVED

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.

Trace - ROLLBCK(1) 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.

Trace - SQL RECEIVED

The number of SQL statements received from the requester location.

Field Name: QLACSQLR

This is an exception field.

Trace - MESSAGES SENT

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.

Trace - MESSAGES RECEIVED

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.

Trace - BYTES SENT

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.

Trace - BYTES RECEIVED

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.

Trace - THREADS INDOUBT

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.

Trace - ROWS SENT

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.

Trace - BLOCKS SENT

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

Field Name: QLACBTBF

This is an exception field.

Trace - CONVERSAT.INITIATED

A count of conversations initiated by the requester.

This number is updated at the server location.

Field Name: QLACCNVR

This is an exception field.

Trace - NBR RLUP 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

Parent topic: Accounting Report and Trace Blocks

Feedback