Use DB2 Connect Server attributes to create situations that monitor all active and inactive gateways.
Agents Assigned from Pool The number of agents assigned by an agent pool.
Agents Created Due to Empty Pool The number of agents created because the agent pool was empty.
Agents Registered The number of agents registered in the database manager instance that is being monitored.
You can use this counter in conjunction with the Agents - Agents waiting for token counter to determine the percentage of agents waiting for a token so they can perform a transaction in the database manager. If the percentage is high, you can improve the concurrency in the database manager by increasing the MAXCAGENTS (maximum number of concurrent agents) database manager configuration parameter. This number is always greater than, or equal to, the number of local databases with current connects.
Agents Waiting for Token The number of agents waiting for a token so they can perform a transaction in the database manager.
You can use this counter in conjunction with the Agents - Agents registered counter to determine the percentage of "sleeping" agents. If the percentage is high, you can you can improve the concurrency in the database manager by increasing the MAXCAGENTS (maximum number of concurrent agents) database manager configuration parameter.
Attempted Connections for DB2 Connect The total number of current connections initiated from remote clients to the instance of the database manager that is being monitored. It also shows the level of activity between this instance and other instances of the database manager.
Committed Private Memory The amount of private memory that the instance of the database manager has committed at the time of the snapshot.
You can use this counter to set the MIN_PRIV_MEM (minimum committed private memory) database manager configuration parameter to ensure you have enough private memory available. This counter is only applicable to platforms containing an agent pool, such as OS/2.
Connection Switches The number of the times that an agent from the agent pool was primed with a connection and was stolen for use with a different DRDA database.
Connection Waiting for Client to Send Request The current number of connections to the host databases that are handled by the DB2 Connect gateway and are waiting for the client to send a request.
Connection Waiting for Host Reply The current number of connections to the host databases that are handled by the DB2 Connect gateway and are waiting for a reply from the host.
Current Connections The number of applications that are currently connected to the database
You can use this counter to understand the level of activity within a database and the amount of system resource being used. It can help you adjust the setting of the MAXAPPLS (maximum number of applications) database configuration parameter and the MAXAGENTS (maximum number of agents) database manager configuration parameter. If its value is always the same as MAXAPPLS, you may want to increase the value of MAXAPPLS. If it is always less than MAXAPPLS, you may want to increase the value of MAXAGENTS.
DB2 Subsystem Identifier The DB2 subsystem ID.
Gateway Snapshot Time The date and time at which the database system monitor information was collected.
Idle Agents The number of agents in the agent pool that are currently unassigned to an application and are, therefore, idle.
IP Address The current IP address.
Maximum Agent Overflows The number of times a request to create a new agent was received when the MAXAGENTS (maximum number of agents) database manager configuration parameter had already been reached.
Maximum Agents Registered The maximum number of agents that the database manager has registered at the same time since it was started.
You can use this counter to evaluate your setting of the MAXAGENTS (maximum number of agents) database manager configuration parameter. The number of agents registered at the time the snapshot was taken is recorded in the Agents - Agents Registered counter.
Maximum Agents Waiting The maximum number of agents that have been waiting for a token at the same time since the database manager was started.
You can use this counter to evaluate your setting of the MAXCAGENTS (maximum number of concurrent agents) database manager configuration parameter. If MAXCAGENTS is set to its default value, which is -1, no agents should wait for a token and the value for this counter should be zero.
The number of agents waiting for a token at the time the snapshot was taken is recorded in the Agents Waiting for Token counter.
Maximum Coordinating Agents The maximum number of coordinating agents working at one time.
Name The name in the database manager configuration file at the client node. It identifies the client node that is running the application.
Node Name The name of the node being monitored by the database system monitor. It identifies the database server node you are monitoring.
This information can be useful if you are saving your monitor output in a file or database for later analysis and you need to differentiate the data from different database server nodes. This node name is determined based on the NNAME configuration parameter.
Node Number The number assigned to the node in the db2nodes.cfg file.
Origin Node A concatenation of the MVS system ID (SMFID) and DB2 subsystem name.
Remote Connections The current number of connections initiated from remote clients to the instance of the database manager that is being monitored.
Remote Connections Executing in the DBM 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.
Server Instance Name The name of the database manager instance for which the snapshot was taken. If a system contains more than one instance of the database manager, this name is used to uniquely identify the instance for which the snapshot call was issued. Along with configuration NNAME at monitoring (server) node, this information can be useful if you are saving your monitor output in a file or database for later analysis, and you need to differentiate the data from different instances of the database manager.
Server Product Version ID The product and version that is running on the server in the form pppvvrrm, where
ppp stands for SQL
vv identifies a 2-digit version number (with high-order 0 in the case of a 1-digit version)
rr identifies a 2-digit release number (with high-order 0 in the case of a 1-digit release)
m identifies a 1-digit modification level
Server Status Shows whether the server is active or inactive.
Server Version The version of the server returning the information.
Sort Heap Allocated The total number of allocated pages of sort heap space for all sorts at the level chosen and at the time the snapshot was taken.
The amount of memory allocated for each sort can be part of or the entire sort heap size available. Sort heap size is the amount of memory available for each sort as defined in the SORTHEAP database configuration parameter. It is possible for a single application to have concurrent sorts active. For example, in some cases a SELECT statement with a subquery can cause concurrent sorts. Information can be collected at two levels:
At the database manager level, it represents the sum of sort heap space allocated for all sorts in all active databases in the database manager.
At the database level, it represents the sum of the sort heap space allocated for all sorts in a database.
Stolen Agents The number of times that agents are stolen from an application. Agents are stolen when an idle agent associated with an application is reassigned to work on a different application.
Time in DB2 Connect For a DCS statement, this counter shows the elapsed time for processing an SQL request at a host database server. This value is reported by this server. In contrast to the Times for sample SQL statement - Total statement time counter, this counter does not include the network elapsed time between DB2 Connect and the host database server.
Time in Network Connection The total time, in seconds and microseconds, at the DB2 Connect gateway to process an application request (since the connection was established), or to process a single statement.
Time on DB2 Host The total time, in seconds and microseconds, that was spent executing a particular statement in the SQL cache.
Timestamp The start time of this interval.
Time Zone Displacement The number of hours that the local time zone is displaced from Greenwich Mean Time (GMT).
Total Inactive DRDA agents The number of connections made by a subagent to the database at the node.
Total Statement Time For a DCS statement, this counter shows the elapsed time between the time the statement was sent from the DB2 Connect gateway to the host for processing and the time at which the result was received from the host.
For a DCS database or application, this counter shows the sum of the elapsed times for all the statements that were executed for a particular application or database.
This counter shows the sum of the values for the Times for sample SQL statement - Time in DB2 Connect and Times for sample SQL statement - Time in network connection counters.