Monitoring threads and connections by using profiles

You can monitor threads and connections for remote TCP/IP access to Db2 servers. You can use the resulting information to analyze the use of system resources by particular clients, applications, and users. You can also create exception thresholds to prioritize resources accordingly.

Before you begin

Create a complete set of profile tables on the Db2 subsystem.

The profile tables and related indexes are created when you run job DSNTIJSG during Db2 installation or migration.

A complete set of profile tables and related indexes includes the following objects:
  • SYSIBM.DSN_PROFILE_TABLE
  • SYSIBM.DSN_PROFILE_HISTORY
  • SYSIBM.DSN_PROFILE_ATTRIBUTES
  • SYSIBM.DSN_PROFILE_ATTRIBUTES_HISTORY
  • SYSIBM.DSN_PROFILE_TABLE_IX_ALL
  • SYSIBM.DSN_PROFILE_TABLE_IX2_ALL
  • SYSIBM.DSN_PROFILE_ATTRIBUTES_IX_ALL

Procedure

  1. Populate the profile table rows with values that specify the monitoring function, the type of monitoring (warning or exception), and the thresholds:
  2. Issue the START PROFILE command to load or reload the profile tables into memory and start the specified monitoring functions.

What to do next

When you are finished monitoring threads and remote connections, stop the profile by taking one of the following actions:
  • To disable monitoring for a specific profile:
    1. Delete the row for the profile from the SYSIBM.DSN_PROFILE_TABLE table, or change the value of the PROFILE_ENABLED column to 'N'.
    2. Reload the profile table into memory by issuing the START PROFILE command.
  • To disable all monitoring, issue the STOP PROFILE command.