Filter Options For Thread Activity Displays
Use this panel to save filter criteria to a specified profile, to activate a different profile, or to specify filter criteria that you want to use in the thread activity panels for the remainder of the session. You can use these filtering options together with the thread commands. If more than one parameter is specified, the requests are connected using a logical AND operator. To specify a reset, type character R in column 1 in front of THFL.
________________ ZPFLT VTM O2 V540.#P DA41 11/06/13 11:37:11 1
> Help PF1 Back PF3
> P.L
> Thread Filtering Specification
===============================================================================
> Filter Options For Threads
> To save filters in the user profile remove the > from the PPRF commmand and
> optionally add a 2 character profile suffix. Use IPRF for install profile
>PPRF SAVE
> To change profiles remove the > from the CPRF command and enter the 2
> character suffix. Use CPFI to switch to installation profile
>CPRF xx
THFL
+
+ Specify the values to be used as filtering criteria for Thread
+ Activity displays. Wildcard values * (multiple characters) or
+ ? (single character) may be specified for character values.
+
+ Specify the following filters to be applied within DB2
+
: PLAN = ________ (plan name)
: AUTHID = ________ (authorization id)
: CONNID = ________ (connection id)
: LOCATION = ________________ (location)
: PARENTACE = ________ (parent ace for parallel tasks)
: CORRID = ____________ (correlation id)
: ENDUSERID = ________________ (end user id)
: WORKSTATION = __________________ (workstation)
: TRANSACTIONID = ________________________________ (transaction id)
+ Specify the following filters to be applied within OMEGAMON
+
: PACKAGE/DBRM = ________ (name )
: COLLECTION = __________________ (collect id)
: DB2STAT = ____________ (db2 status)
: GETPAGES > _________ (number of getpages)
: UPDATES > _________ (number of page updates)
: COMMITS > _________ (number of commits)
: ELAPTIME > _________ (elapsed time - in seconds)
: ELAPTIME/COMMIT > _________ (elapsed time per commit)
: DB2TIME > _________ (In DB2 time - in seconds)
: DB2TIME/COMMIT > _________ (In DB2 time per commit)
: PROCESSINGINDB2 = ___ (Status Active in DB2)
: THREADLIM = _________ (Limit on number of threads returned)
===============================================================================
Fields
The
following fields enable OMEGAMON XE
for Db2 PE to send filters to DB2 as well as to apply post-filtering
of
data returned from Db2. These
filters can improve the performance in your environment.
- PLAN
- The Db2 plan name of the active thread. You can specify up to 8 characters.
- AUTHID
- The Db2 thread authorization identifier of the active thread. You can specify up to 8 characters.
- CONNID
- The Db2 connection identifier of the active thread. You can specify up to 8 characters.
- LOCATION
- The name of the location requesting information. You can specify up to 16 characters. The field will either filter on the requesting location (QW01488L, for example, for distributed database access threads), or the Db2 location (QW0148LN) if the requesting location field is not filled by DB2.
- PARENTACE
- The agent control element (ACE) token. Specify the
parent ACE for the parallel task. You can specify up to 8 digits.
A value of
0
filters out child parallel tasks from the Thread Activity displays. - CORRID
- The correlation identifier. You can specify up to
12 characters. If the application requestor is a DB2 system, this is the same correlation ID assigned
at the requestor. If the application requestor is not DB2, this is the name of the job, task, or process
that is being serviced.Note: This field is case sensitive. It is not converted to uppercase.
- ENDUSERID
- The end user's work station user ID. You can specify
up to 16 characters. This can be different from the authorization
ID used to connect to Db2. It
contains blanks if the client does not supply this information.Note: This field is case sensitive. It is not converted to uppercase.
- WORKSTATION
- The workstation identifier. You can specify up to 18
characters. It contains blanks if the client does not supply this
information.Note: This field is case sensitive. It is not converted to uppercase.
- TRANSACTIONID
- The name of the transaction or application that the
end user is running. It identifies the application that is currently
running, not the product that is used to run the application. You
can specify up to 32 characters. This field contains blanks if the
client does not supply this information.Note: This field is case sensitive. It is not converted to uppercase.
- PACKAGE/DBRM
- The Db2 package name or DBRM name of the active thread. You can specify up to 8 characters.
- COLLECTION
- The package collection identifier of the active thread. You can specify up to 18 characters.
- DB2STAT
- The Db2 status. You can specify up to 12 characters.
- GETPAGES
- The number of Getpage requests issued by the active thread since thread creation. You can specify up to 9 digits.
- UPDATES
- The number of DB2 page updates made by the thread since thread creation. This value is incremented each time a row in a page is updated, not just once for each page updated. DB2 might update pages when it creates intermediate result tables because of a qualified SELECT statement, even though SELECT statements are generally thought of as read only operations. Pages that have been updated are written asynchronously by DB2, according to DB2's internal Deferred Write algorithm, not immediately after update or commit. DB2 resets the page update count at Create Thread and Signon. If Signon is not driven, the page update count is cumulative. This file is applicable for active threads only. You can specify up to 9 digits.
- COMMITS
- The number of times the thread successfully completed commit processing. Db2 resets the commit count at thread create and signon. If signon is not driven, the count is cumulative. You can specify up to 9 digits.
- ELAPTIME
- The elapsed time since thread creation. You can specify up to 9 digits.
- ELAPTIME/COMMIT
- Average elapsed time between commits. If the number of commits is zero this field is the same as ELAPTIME. You can specify up to 9 digits.
- DB2TIME
- The total In-DB2 elapsed time in seconds for an active thread. You can specify up to 9 digits.
- DB2TIME/COMMIT
- Average In-DB2 elapsed time between commits. If the number of commits is zero this field is the same as DB2TIME. You can specify up to 9 digits.
- PROCESSING-IN-DB2
- Values YES, NO or blank.
- YES
- Only threads that are in a status that is active in Db2
are shown. If a thread is executing in the application it is not shown. The following thread
statuses are processing in Db2:
- IN-DB2
- IN-TRIGGER
- IN-COMMAND
- IN-STOR-PROC
- IN-USER-FUNC
- IN-TERM-THRD
- WAIT-LOCK
- WAIT-GLBLOCK
- WAIT-MSGSEND
- WAIT-ARCHIVE
- WAIT-REMSQL
- WAIT-CONVLIM
- WAIT-TERM-TH
- WAIT-SP-STOP
- WAIT-SP-SCHD
- SP/UDF-INACT
- WAIT-SYNC-IO
- WAIT-SERVICE
- WAIT-ASYNCRD
- WAIT-ASYNCWR
- WAIT-LOGQSCE
- WAIT-PGLATCH
- WAIT-DRNLOCK
- WAIT-CLAIMER
- WAIT-ARCREAD
- WAIT-LOCKPIP
- WAIT-LOCKPQS
- WAIT-SWITCH
- WAIT-ACCEL
- WAIT-LOB
- WAIT-COMMIT
- WAIT-CL3LOCK
- IN-SQL-SORT
- IN-SQL-CALL
- WAIT-REMREQ
- IN-BIND-DYNM
- IN-ACCEL
- IN-AUTO-PROC
- NO
- Only threads that are not in an active status in Db2 are shown.
- Blank
- This filter is not used.
Threads accelerated by the IBM® Db2 Analytics Accelerator for z/OS® are considered as being processed in DB2.
- THREADLIM
- A numeric value causing OMEGAMON XE for Db2 PE to stop retrieving instrumentation records from Db2. This field can have a positive impact on realtime and system performance, but can also result in an incomplete thread list if it is less than the number of threads actually running in DB2 at the time the list is retrieved. The default setting (blank or 0) allows all records retrieved by DB2 to flow to OMEGAMON XE for Db2 PE. You can specify up to 9 digits.