Using profiles to monitor and optimize DB2 for z/OS® subsystems

Profile tables enable you to monitor the use of system resources, control performance-related subsystem parameters in particular contexts on your DB2® subsystem. Each monitored context is defined by a set of criteria called a profile.

About this task

A profile is a set of criteria that identifies a particular context on a DB2 subsystem. Examples include threads, connections, or SQL statements that have particular attributes.
  • Profiles for monitoring and controlling DB2 for z/OS subsystems
    A profile is a set of criteria that identifies a particular context on a DB2 subsystem. Examples include threads, connections, or SQL statements that have particular attributes.
  • Creating profiles
    You can create profiles to define filtering scopes for processes within DB2. The filtering for each profile is controlled by the column values in the DSN_PROFILE_TABLE. You can also specify actions for DB2 to take when a process, such as a SQL statement, thread, or connection meets the criteria of the profile. The actions are specified by the column values in the DSN_PROFILE_ATTRIBUTES table.
  • Starting and stopping profiles
    You must enable and start profiles before DB2 can use the information in the profile tables. When you apply changes to an existing started profile, you must stop the profile and start it again before the changes are applied.
  • Modifying existing profiles
    You must take certain actions to apply changes to profiles.
Parent topic: Monitoring performance
Related tasks:
Monitoring threads and connections by using profiles
Modeling a production environment on a test subsystem
Optimizing subsystem parameters for SQL statements by using profiles
Related reference:
Profile tables