Filtering thread history by end user

You can filter your thread history by end user, workstation, transaction, role, trusted context, or accounting string, from the End User tab.

About this task

This task assumes the thread history data collector is running.

Procedure

  1. From the KOBSEVTS panel, which appears when you log in, select DB2. This displays the active DB2 subsystems.
  2. From KOBSTART or KDPSTART, enter R next to the DB2 subsystem you want to use.
  3. Select the End User tab. From this tab, you can specify that you want to select threads based on any of several case sensitive criteria:
    • End User ID (up to 56 bytes)
    • Workstation name (up to 56 bytes)
    • Transaction Name (up to 56 bytes)
    • Role Name (up to 56 bytes if running in a trusted context)
    • Trusted Context (up to 56 bytes if running in a trusted context)
    • Accounting String: up to 56 bytes for the agent. For DSN type, it is the first 56 bytes of QMDAACCT. For JCC/SQL types, it is the first 56 bytes of QMDASUFX. For other types, it is the first 56 bytes of AMDAASTR.

      You can use the EQ ("equal") or NE ("not equal") operators to specify that you want to see results that match, or results that do not match, the string you enter. The question mark (?) wildcard can be used to represent one character in a string. For example, you might specify John?Smith to see threads with End User IDs such as JohnBSmith or JohnQSmith.

      The asterisk (*) wildcard can be used to specify that you want to see any string. For example, you might specify John* to see threads with End User IDs such at JohnSmith or JohnJones. When you use the asterisk wildcard, any characters you enter after the asterisk will be ignored. For example, John*Smith would be treated the same as John*.

  4. When you have specified the selection criteria you want to use, select OK. The thread history summary is displayed.