Viewing thread history

Use the Thread History Timespan Selection panel (KDPHFIL1) and related tabs to refine your view of thread history data.

Procedure

  1. Select the Db2 tab on the OMEGAMON Products panel to show the All Active Db2 Subsystems workspace.
  2. Type a / in the line command field next to the Db2 subsystem of interest and press Enter.
  3. In the option menu, select option 12 (R Thread History) and press Enter.
    Figure 1. Thread History Timespan Selection tab (KDPHFIL1)
    KDPHFIL1 panel showing columns and fields
    The Thread History Timespan Selection panel shows the following tabs:
    Timespan (KDPHFIL1)
    Refine your view of thread history information by specifying timespan criteria.
    Counts/Times (KDPHFIL2)
    Refine your view of thread history information by specifying counts and time based criteria.
    Thread ID (KDPHFIL3)
    Refine your view of thread history information by specifying thread ID selection criteria.
    End User (KDPHFIL4)
    Refine your view of thread history information by specifying end user selection criteria.
    COPT (KDPHCOPT)
    View thread history data collection options for the Db2 subsystem.
    Data Set (KDPHDSET)
    View thread history data set status for the Db2 subsystem.
  4. To refine your view of thread history information based on a selected timespan, select the Timespan tab and enter one of the following options:
    1. Specify the appropriate option for your selection criteria.
      Valid options are:
      1 M Historical Last ___ Minute(s)
      Type 1 in the selection field and adjust the desired number of minutes as appropriate (default 030) to specify the number of minutes before the current time to set the beginning of the reporting period. Leading zeros are required.
      2 H Historical Last ___ Hour(s)
      Type 2 in the selection field and adjust the desired number of hours as appropriate (default 002) to specify the number of hours before the current time to set the beginning of the reporting period. Leading zeros are required.
      3. T Historical Time Range
      Type 3 in the selection field and adjust the desired time range as appropriate (start time/date and end time/date) to specify the start and end time for the reporting period. The date is in the format MM/DD/YYYY and the time is in the format.
    2. Click OK to apply your selection criteria.
  5. To refine your view of thread history information based on counts and time criteria, select the Counts/Times tab:
    Figure 2. Thread History Counts/Times Selection tab (KDPHFIL2)
    KDPHFIL2 panel showing columns and fields
    1. Specify the appropriate operator for your selection criteria.
      Valid operators are EQ (Equal) and NE (Not Equal). The wild cards * and ? are supported. Use ? to match a single character. Use * to match the rest of the string.
    2. Specify the appropriate values for your selection criteria:
      Getpages
      The number of getpage requests.
      Sync Read I/O
      The number of synchronous read I/Os performed.
      Deadlock/Timeout
      The number of deadlocks and timeouts that occurred.
      Aborts
      The number of aborts performed by the thread.
      Lock Requests
      The number of IRLM lock requests.
      Commit
      The number of commits performed by the thread.
      Db2 CPU Time
      The IN-DB2 CPU time in the format HH:MM:SS.MMMMMM.
      Db2 Elapsed
      The IN-DB2 elapsed time in the format HH:MM:SS.MMMMMM.
      I/O Wait Time
      The I/O wait time in the format HH:MM:SS.MMMMMM.
      SQL Count
      The total number of DCL, DDL, and DML SQL calls issued.
      DML Count
      The total number of DML SQL calls issued by the thread.
      DCL Count
      The total number of DCL SQL calls issued by the thread.
      DDL Count
      The total number of DDL SQL calls issued by the thread.
    3. Click OK to apply your selection criteria.
  6. To refine your view of thread history information based on thread ID criteria, select the Thread ID tab:
    Figure 3. Thread History Thread ID Selection tab (KDPHFIL3)
    KDPHFIL3 panel showing columns and fields
    1. Specify the appropriate operator for your selection criteria.
      Valid operators are EQ (Equal) and NE (Not Equal). The wild cards * and ? are supported. Use ? to match a single character. Use * to match the rest of the string.
    2. Specify the appropriate values for your selection criteria:
      Plan Name
      The the plan names.
      Auth ID
      The authorization identifiers.
      Connect
      The connection identifiers. Not valid on end-of-memory. Reflects the z/OS home ASID connection name. Valid values are:
      Batch
      BATCH
      TSO
      TSO
      QMF
      DB2CALL
      Utility
      UTILITY
      Db2 Internal
      DB2 SUBSYSTEM ID
      IMS
      IMS-ID
      CICS
      CICS-ID
      RRSAF
      RRSAF
      Distributed database access threads
      For threads from a Db2 requester, this field contains the connection name of the thread at the requesting location.
      Con Type
      The connection types. Possible connection types include: TSO, CALLATCH, DLI, CICS, IMSBMP, IMSMPP, DRDA (Distributed), IMSCTRL, IMSTBMP, UTILITY, RRSAF. The supported operators for this field are EQ and NE. Wild cards are not supported.
      Corr ID
      The correlation ID up to 12 bytes in length. This field is case sensitive.
      CICS TX
      The CICS transaction ID.
      IMS PSB
      The IMS PSB name. The supported operators for this field are EQ and NE. The wild cards * and ? are supported. Use ? to match a single character. Use * to match the rest of the string.
    3. Click OK to apply your selection criteria.
  7. To refine your view of thread history information based on end user criteria, select the End User tab:
    Figure 4. Thread History End User Selection tab (KDPHFIL4)
    KDPHFIL4 panel showing columns and fields
    1. Specify the appropriate operator for your selection criteria.
      Valid operators are EQ (Equal) and NE (Not Equal). The wild cards * and ? are supported. Use ? to match a single character. Use * to match the rest of the string.
    2. Specify the appropriate values for your selection criteria:
      End User ID
      The end user's userid, up to 56 bytes.
      Workstation
      The end user's workstation name, up to 56 bytes.
      Transaction
      The end user's transaction, up to 56 bytes.
      Role
      The role name, up to 56 bytes, that is associated with the authorization ID, if running in a trusted context.
      Trusted Ctx
      The trusted context name, up to 56 bytes, if running in a trusted context.
      Accounting
      The accounting string up to 56 bytes for the agent. For DSN type, it is the first 56 bytes of QMDAACT. For JCC/SQL types, it is the first 56 bytes of QMDASUFX. For other types, it is the first 56 bytes of QMDAASTR.
    3. Click OK to apply your selection criteria.
  8. To view data collection options information, select the COPT tab:
    Figure 5. Thread History Data Collection Options tab (KDPHCOPT)
    KDPHCOPT panel showing columns and fields
    The following information is shown:
    Date of Oldest Record
    The date of the oldest record in the thread history.
    Time of Oldest Record
    The time of the oldest record in the thread history.
    Date of Newest Record
    The date of the newest record in the thread history.
    Time of Newest Record
    The time of the newest record in the thread history.
    Number of Records
    The number of records in the thread history
    Accounting Class n
    Indicates the accounting classes associated with the thread history.
    TH Sort
    Indicates whether thread history is collecting sort data. Valid values are:
    NO
    (Default) Thread history is not collecting sort data.
    Note: This field is not yet implemented. The only valid value at this time is NO.
    YES
    Thread history is collecting sort data.
    TH Scan
    Indicates whether thread history is collecting scan data. Valid values are:
    NO
    (Default) Thread history is not collecting scan data.
    Note: This field is not yet implemented. The only valid value at this time is NO.
    YES
    Thread history is collecting scan data.
    TH Lock Contention
    Indicates whether thread history is collecting lock contention data. Valid values are:
    NO
    (Default) Thread history is not collecting lock contention data.
    Note: This field is not yet implemented. The only valid value at this time is NO.
    YES
    Thread history is collecting lock contention data.
    TH Lock Suspension
    Indicates whether thread history is collecting lock suspension data. Valid values are:
    NO
    (Default) Thread history is not collecting lock suspension data.
    Note: This field is not yet implemented. The only valid value at this time is NO.
    YES
    Thread history is collecting lock suspension data.
    TH Dynamic SQL
    Indicates whether thread history is collecting dynamic SQL text data (short, up to 5000 characters).Valid values are:
    NO
    (Default) Thread history is not collecting dynamic SQL text data (short).
    Note: This field is not yet implemented. The only valid value at this time is NO.
    YES
    Thread history is collecting dynamic SQL text data (short).
    TH Dynamic SQL 350
    Indicates whether thread history is collecting dynamic SQL text data (long, full text).Valid values are:
    NO
    (Default) Thread history is not collecting dynamic SQL text data (long).
    Note: This field is not yet implemented. The only valid value at this time is NO.
    YES
    Thread history is collecting dynamic SQL text data (long).
  9. To view data set status information, select the Data Set tab:
    Figure 6. Thread History Data Collection Options tab (KDPHDSET)
    KDPHCOPT panel showing columns and fields
    The following information is shown:
    THVSAM Dataset
    The thread history VSAM data set.
    Status
    The status of the thread history VSAM data set.
    %Full
    The percentage full the thread history VSAM data set is.