Db2 DPF Connections Test

The Db2 Connections test reports key statistics pertaining to the local and remote connections to the DB2 database manager.

Target of the test : A DB2 database server with DPF enabled

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every DB2 database server being monitored

Configurable parameters for the test
TEST PERIOD – How often should the test be executed Host – The IP address of the DB2 server Port – The port number through which the DB2 server communicates. The default port is 50000. user - Specify the name of the user who has any of the following privileges to the specified DATABASE: SYSADM or SYSCTRL or SYSMAINT or SYSMON. You can create a separate user on the OS hosting the DB2 server for this purpose, and assign any of the aforesaid privileges to that user. The steps for the same are detailed in the Creating a Special User for Monitoring DB2. password - Enter the password of the specified USER in the PASSWORD text box. confirm password – Confirm the password by retyping it here. database - Specify the name of the database on the monitored DB2 server to be used by this test. SSL- If the target database server is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No. Trust Store file name- The trust store file contains certificates from trusted Certificate Authorities (CAs). These certificates are used by eG agent to verify the authenticity of servers hosting DB2 UDB and establish a secure connection with the server using SSL. Specify the filename for Trust store file in Trust Store file name text box. Trust Store Password- The trust store password is the passphrase or key used to encrypt and decrypt the trust store file. This password is required by the eG Agent when it needs to access the trust store file to establish secure connections. Specify the password in Trust Store password text box.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total Connections:	Indicates the totalnumber of local and remote connections that are currently present in the database manager.	Number
Local Connections:	Indicates the number of local applications that are currently connected to a database within the database manager instance being monitored.	Number	This number can help you determine the level of concurrent processing occurring in the database manager. This number only includes applications that were initiated from the same instance as the database manager. The applications are connected, but may or may not be executing a unit of work in the database. When used in conjunction with the Remote connections measurement, this measure can help you adjust the setting of the MAXAGENTS configuration parameter.
Remote Connections:	Indicates the percentage of agents waiting for a token so they can execute a transaction in the database manager.	Number	This number does not include applications that were initiated from the same instance as the database manager. When used in conjunction with the Local connections measure, this measure can help you adjust the setting of the MAX_COORDAGENTS configuration parameter.
Local connections in exec:	Indicates the number of local applications that are currently connected to a database within the database manager instance being monitored and are currently processing a unit of work.	Number	This number can help you determine the level of concurrent processing occurring in the database manager. This number only includes applications that were initiated from the same instance as the database manager. When used in conjunction with the Remote connections in exec measure, this measure can help you adjust the setting of the MAXCAGENTS configuration parameter.
Remote connections in exec:	Indicates the number of remote applications that are currently connected to a database and are currently processing a unit of work within the database manager instance being monitored.	Number	This number can help you determine the level of concurrent processing occurring on the database manager. This number does not include applications that were initiated from the same instance as the database manager. When used in conjunction with the Local connections in exec measure, this metric can help you adjust the setting of the MAXCAGENTS configuration parameter.