Distributed Activity - Server

This topic shows detailed information about Accounting - Distributed Activity - Server.

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

In the following example both layouts are shown, the report layout followed by the trace layout. SH12-7070 IBM Db2 Analytics Accelerator for z/OS

Accounting - Distributed Activity - Server

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


Report:

---- DISTRIBUTED ACTIVITY ----------------------------------------------------------------------------------------------------------
SERVER             : *ROLSUM*            CONVERSATIONS INITIATED:    1.00    #COMMT(1)SENT:       0   MESSAGES SENT    :       3.00
PRODUCT ID         : DB2                 #CONVERSATIONS QUEUED  :       0    #ROLLB(1)SENT:       0   MESSAGES RECEIVED:       3.00
PRODUCT VERSION    :                     CONVERSATION TERMINATED:    0.00    SQL SENT     :    2.00   BYTES SENT       :    1314.00
METHOD             : DB2 PRIV            #RLUP THREADS          :      10    ROWS RECEIVED:   20.00   BYTES RECEIVED   :    2076.00
REQUESTER ELAP.TIME:        10.776739                                                                 BLOCKS RECEIVED  :       1.00                                                   
DBAT WAITING TIME  :         0.010000                                                   
#DDF ACCESSES      :                1                                            


Trace:

---- DISTRIBUTED ACTIVITY -----------------------------------------------------------------------------------                       
SERVER                 : PMODA11             CONVERSATION TERMINATED:     N/A    NBR RLUP THREADS :         1                       
PRODUCT ID             : DB2                 COMMT(1)SENT           :       1    MESSAGES SENT    :         5                       
PRODUCT VERSION        : V10R1 M5            ROLLB(1)SENT           :       0    MESSAGES RECEIVED:         5                       
METHOD                 : N/P                 SQL SENT               :       2    BYTES SENT       :      1170                       
REQUESTER ELAP.TIME    :         0.154750    ROWS RECEIVED          :    1095    BYTES RECEIVED   :     21201                       
DBAT WAITING TIME      :              N/A                                        BLOCKS RECEIVED  :         1                       
CONVERSATIONS INITIATED:                1                                                                                           
CONVERSATIONS QUEUED   :                0
Report - SERVER

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

Report - PRODUCT VERSION
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

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 - REQUESTER ELAP.TIME

The elapsed time at the requester. It includes the total of Db2 and network time.

Field Name: ADDSELRQ

Report - DBAT WAITING TIME

Total elapsed time spent waiting for an available database access agent slot.

Field Name: QLACMDWT

Report - #DDF ACCESSES

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

Field Name: ASDDF

Report - CONVERSATIONS INITIATED

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

Report - #CONVERSATIONS QUEUED

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.

Report - CONVERSATION TERMINATED

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.

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

Report - #COMMT(1)SENT

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.

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

Report - SQL SENT

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.

Report - ROWS RECEIVED

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.

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 - BLOCKS RECEIVED

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

Field Name: QLACBRBF

This is an exception field.

Trace - SERVER

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

Trace - PRODUCT VERSION
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

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 - REQUESTER ELAP.TIME

The elapsed time at the requester. It includes the total of Db2 and network time.

Field Name: ADDSELRQ

Trace - DBAT WAITING TIME

Total elapsed time spent waiting for an available database access agent slot.

Field Name: QLACMDWT

Trace - CONVERSATIONS INITIATED

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

Trace - CONVERSATIONS QUEUED

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.

Trace - CONVERSATION TERMINATED

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.

Trace - COMMT(1)SENT

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.

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

Trace - SQL SENT

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.

Trace - ROWS RECEIVED

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.

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

Trace - MESSAGES SENT

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

Field Name: QLACMSGS

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

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

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

Trace - BLOCKS RECEIVED

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

Field Name: QLACBRBF