DRDA Remote Locations
This topic shows detailed information about Statistics - DRDA Remote
Locations
.
This block shows information about remote locations of Distributed Relational Database Architecture (DRDA).
Statistics - DRDA Remote Locations
The field labels shown in the following sample layout of Statistics - DRDA Remote
Locations
are described in the following section.
REMOTE LOCATION STATISTICS VALUE
-------------------------- ----------------------------------------------------------------
LOCATION NAME ::FFFF:10.32.248.183
PRODUCT ID JCC04310
PRODUCT LEVEL 10
INTERVAL START 01/31/23 15:30:00.68
INTERVAL END 01/31/23 17:00:00.64
INTERVAL ELAPSED 1:29:59.959740
REMOTE LOCATION STATISTICS SENT RECEIVED REMOTE LOCATION STATISTICS QUANTITY
--------------------------- -------- -------- -------------------------------- --------
CONNECTIONS 0.00 6.00 ACTIVE CONNS FROM LOC - SNAP 0.00
CONNECTIONS QUEUED 0.00 ACTIVE CONNS FROM LOC - INT. HWM 1.00
CONNECTIONS DEALLOCATED 0.00 ACTIVE DBATS FOR LOC - SNAP 0.00
ACTIVE DBATS FOR LOC - INT. HWM 0.00
SQL STATEMENTS 0.00 6.00 REST SERVICE REQUESTS 0.00
COMMITS 0.00 6.00 PROFILE SET SPECIAL REGS 0.00
ROLLBACKS 0.00 0.00 PROFILE SET GLOBAL VARS 0.00
ROWS 18.00 0.00 SYSPLEX WKLD BAL. USED 0.00
MESSAGES 36.00 36.00 TLS/SSL USED 0.00
BYTES 19556.00 4734.00 TRUSTED CONTEXT USED 0.00
BLOCKS 24.00 0.00 AES ENCRYPTION USED 0.00
XA GLOBAL TRANSACTION USED 0.00
THREAD INDOUBT-REM.L.COORD. 0.00 DRDA ENCRYPTION USED 0.00
UID/PWD USED 6.00
KERBEROS USED 0.00
MFA USED 0.00
CLIENT CERTIFICATE USED 0.00
FAILED SECURITY AUTH 0.00
JWT/IDT USED 0.00
REMOTE LOCATION STATISTICS QUANTITY REMOTE LOCATION STATISTICS QUANTITY REMOTE LOCATION STATISTICS QUANTITY
--------------------------- -------- ---------------------------- -------- ------------------------------- --------
WITH HOLD CURSOR NOT CLOSED 0.00 REQ TERM - CONDBAT REACHED 0.00 THRD QUEUED - PROFILE EXCEPTION 0.00
DGTT NOT DROPPED 0.00 REQ TERM - PROFILE EXCEPTION 0.00 THRD TERM - PROFILE EXCEPTION 0.00
KEEPDYNAMIC PACKAGES USED 0.00 REQ TERM - MAXCONQN REACHED 0.00 THRD TERM - ABENDED 0.00
HIGH PERF DBATS USED 0.00 REQ TERM - MAXCONQW REACHED 0.00 THRD TERM - CANCELED 0.00
HELD LOB LOCATORS EXIST 0.00 THRD TERM - POOLINAC TIME N/P
SP COMMIT PERFORMED 0.00 THRD TERM - SOCKET CLOSED N/P
- LOCATION NAME
-
The name of the remote location.
- PRODUCT ID
-
The product ID and version of the remote location.
- PRODUCT LEVEL
-
Product level of the remote location, if reported.
- INTERVAL START
-
Timestamp of the start of the reporting interval for this remote location record.
- INTERVAL END
-
Timestamp of the end of the reporting interval for this remote location record.
- INTERVAL ELAPSED
-
Elapsed time of the reporting interval for this remote location record.
- GENERAL - SENT - CONNECTIONS
The number of connections that were initiated from the requester site to the remote site. This value is maintained at the requester site.
A connection is a specific instance of using TCP/IP or SNA LU 6.2 to transfer information between a requester and a server. It is a logical connection between a requester and a server.
- GENERAL - SENT - CONNECTIONS QUEUED
-
The number of connection requests queued by the distributed data facility that were waiting for allocation or waiting for a DBAT because MAXDBAT was exceeded. This value is maintained at the requester location.
Note: When this value is high, increase the limit for the number of connections. - GENERAL - SENT - CONNECTIONS DEALLOCATED
-
The number of connections that were deallocated from this site to the remote site if Db2 was requester. Otherwise, the number of connections received by Db2 from the remote site which were terminated as incomplete.
- GENERAL - SENT - SQL STATEMENTS
-
The number of SQL statements sent to the remote server. This value is updated at the requester location.
- GENERAL - SENT - COMMITS
-
The number of commit requests sent to the server (single-phase commit protocol) and the committed requests sent to the participant (two-phase commit protocol).
- GENERAL - SENT - ROLLBACKS
-
The number of abort requests sent to the server (single-phase commit protocol) and backout requests sent to the participant (two-phase commit protocol).
- GENERAL - SENT - ROWS
-
The number of data rows sent to the requester location (includes SQLDA). This value is updated at the server location.
- GENERAL - SENT - MESSAGES
-
The number of messages sent to the remote location. A message is a group of characters and control bit sequences transferred on a single TCP/IP or SNA API call. This value is maintained at the location where the messages originated.
- GENERAL - SENT - BYTES
-
The number of bytes of data sent to the requester location. This value is maintained at the server location.
- GENERAL - SENT - BLOCKS
-
The number of blocks transmitted using block fetch. This value is maintained at the server location.
- GENERAL - SENT - THREAD INDOUBT-REM.L.COORD.
-
The number of threads that became indoubt with the remote location as the coordinator (two-phase commit operations only). A large value might indicate network problems.
- GENERAL - RECEIVED - CONNECTIONS
-
The number of connections that were initiated from the requester to the server location. This value is updated at the server location.
- GENERAL - RECEIVED - SQL STATEMENTS
-
The number of SQL statements received from the requester location. This value is updated at the server location.
- GENERAL - RECEIVED - COMMITS
-
The number of commit requests received from the requester (single-phase commit protocol) and committed requests received from the coordinator (two-phase commit protocol).
- GENERAL - RECEIVED - ROLLBACKS
-
The number of abort requests received from the requester (single-phase commit protocol) and backout requests received from the coordinator (two-phase commit protocol).
- GENERAL - RECEIVED - ROWS
The number of data rows received from the server location. This value is maintained at the requester location.
- This value does not include any SQLDA or SQLCA transmitted.
- Block fetch can significantly affect the number of rows sent across the network. When used with nonupdate cursors, block fetch groups as many rows as possible into the message buffer, and transmits the buffer over the network without requiring a VTAM message. Consequently, more rows of data might be sent from the server location than are received by the 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 from the requester.
- GENERAL - RECEIVED - MESSAGES
The number of messages received by VTAM from the remote 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 due to the manner in which distributed SQL statements are processed internally.
- GENERAL - RECEIVED - BYTES
The number of bytes of data received from the server location. This value is maintained at the requester location.
More bytes of data might be sent from the server location than are received by the requester due to the manner in which distributed SQL statements are processed internally.
- GENERAL - RECEIVED - BLOCKS
-
The number of blocks received from the remote location using block fetch. This value is maintained at the requester location.
- DDF CONN. DETAILS - ACTIVE CONNS FROM LOC - SNAP
-
Current number of active connections from this location.
- DDF CONN. DETAILS - ACTIVE CONNS FROM LOC - INT. HWM
-
Highest number of active connections from this location since the last statistics trace interval for a statistics trace request. For a READS request, highest number of active connections from this location since DDF was started.
- DDF CONN. DETAILS - ACTIVE DBATS FOR LOC - SNAP
-
Current number of active threads in use by this location.
- DDF CONN. DETAILS - ACTIVE DBATS FOR LOC - INT. HWM
-
Highest number of active threads in use by this location since the last statistics trace interval for a statistics trace request. For a READS request, highest number of active threads in use by this location since DDF was started.
- DDF CONN. DETAILS - REST SERVICE REQUESTS
-
Number of times that a connection from the remote site invoked a rest service.
- DDF CONN. DETAILS - PROFILE SET SPECIAL REGS
-
Number of times that a connection from the remote site caused a system monitoring profile to set special registers.
- DDF CONN. DETAILS - PROFILE SET GLOBAL VARS
-
Number of times that a connection from the remote site caused a system monitoring profile to set global variables.
- DDF CONN. DETAILS - SYSPLEX WKLD BAL. USED
-
Number of connections from the remote site using sysplex workload balancing.
- DDF CONN. DETAILS - TLS/SSL USED
-
Number of connections from the remote site configured with SSL and AT/TLS support.
- DDF CONN. DETAILS - TRUSTED CONTEXT USED
-
Number of connections from the remote site under control of a trusted context.
- DDF CONN. DETAILS - AES ENCRYPTION USED
-
Number of connections from the remote site using AES encryption.
- DDF CONN. DETAILS - XA GLOBAL TRANSACTION USED
-
Number of connections from the remote site under control of an XA global transaction.
- DDF CONN. DETAILS - DRDA ENCRYPTION USED
-
Number of connections from the remote site using DRDA data encryption.
- DDF CONN. DETAILS - UID/PWD USED
-
Number of connections from the remote site using userid and/or password authentication.
- DDF CONN. DETAILS - KERBEROS USED
-
Number of connections from the remote site using kerberos authentication.
- DDF CONN. DETAILS - MFA USED
-
Number of connections from the remote site using multifactor authentication.
- DDF CONN. DETAILS - CLIENT CERTIFICATE USED
-
Number of connections from the remote site using client certificate authentication.
- DDF CONN. DETAILS - FAILED SECURITY AUTH
-
Number of times that a connection from the remote site had security authentication failures.
- DDF CONN. DETAILS - JWT/IDT USED
-
The number of connections from the remote site that used an authentication token such as a JSON Web Token (JWT) or RACF Identity Token (IDT). This value is meaningful only at the server.
Field Name: QLSTNATK
- CLIENT CONDITIONS - WITH HOLD CURSOR NOT CLOSED
-
Number of times that cursors defined with HOLD prevented thread pooling.
- CLIENT CONDITIONS - DGTT NOT DROPPED
-
Number of times where the existence of active declared global temp tables prevented thread pooling.
- CLIENT CONDITIONS - KEEPDYNAMIC PACKAGES USED
-
Number of times where the usage of keepdynamic packages prevented thread pooling.
- CLIENT CONDITIONS - HIGH PERF DBATS USED
-
Number of times where the usage of high performance DBATs prevented thread pooling.
- CLIENT CONDITIONS - HELD LOB LOCATORS EXIST
-
Number of times where the existence of active held lob locators prevented thread pooling.
- CLIENT CONDITIONS - SP COMMIT PERFORMED
-
Number of times where a stored procedure issued commit prevented thread pooling.
- REQ TERM - CONDBAT REACHED
-
Number of connections from the remote site that were terminated due to CONDBAT being reached.
- REQ TERM - PROFILE EXCEPTION
-
Number of connections from the remote site that were terminated due to system monitoring profile exception.
- REQ TERM - MAXCONQN REACHED
-
Number of connections from the remote site that were terminated due to MAXCONQN being reached.
- REQ TERM - MAXCONQW REACHED
-
Number of connections from the remote site that were terminated due to MAXCONQW being reached.
- THRD QUEUED - PROFILE EXCEPTION
-
Number of times where threads used by connections from the remote site were queued due to a system monitoring profile exception.
- THRD TERM - PROFILE EXCPTION
-
Number of times where threads used by connections from the remote site were terminated due to a system monitoring profile exception.
- THRD TERM - ABENDED
-
Number of times where threads used by connections from the remote site abended.
- THRD TERM - CANCELLED
-
Number of times where threads used by connections from the remote site were canceled.
- THRD TERM - POOLINAC TIME
-
The number of times that threads used by connections from the remote site were terminated after remaining in pool longer than POOLINAC.
- THRD TERM - SOCKET CLOSED
-
Number of times that threads used by connections from the remote site were terminated after TCP socket closed due to connection loss. This value is meaningful only at the server.