Thread Resource Limit Statistics
This panel shows information about the parameters that control and administer the thread resource limit facility (governor). This Db2 governor facility applies to dynamic SQL calls only.
________________ ZRLMS VTM O2 V550.#P SN12 11/04/13 17:54:07 2 > Help PF1 Back PF3 > THREAD INFORMATION: Enter a selection letter on the top line. > A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS D-LOCKS OWNED E-GLOBAL LOCKS > F-CURRENT SQL G-SQL COUNTS H-DISTRIBUTED I-BUFFER POOL J-GROUP BP > K-PACKAGES *-RES LIMIT M-PARALLEL TASKS N-UTILITY O-OBJECTS > P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY S-APPL TRACE T-ENCLAVE > U-LONG NAMES W-ACCEL ACTIVITY =============================================================================== > THREAD RESOURCE LIMIT STATISTICS PLAN + Thread: Plan=KO2PLAN Connid=RRSAF Corrid= Authid=OMPEUSER + Attach: RRSAF JOB Name=D843DMGS JOB Asid= 248 + Package: FPE@WR2C Collection=KO2OM520 + Luwid=DEIBMIPS.IPSATN12.CC36D06C8094=6107 rlms + Resource Limit Table Name In Use = DSNRLST96 + Resource Limit Origin = Auth Any Pkg/Coll + Resource Limit In Effect (SUs) = 2147483K + Resource Limit CPU time per SU = .000014 + Resource Limit In Effect (CPU secs) = 30064.771 + Resource Limit High Water Mark (CPU) = .001 + Ratio Of HWM To Resource Limit (CPU) = % + + Predictive Cost Estimate (Service Units) = 7523 + Predictive Cost Estimate (Seconds ) = 106 + Predictive Cost Estimate Category = B + + Predictive Error Threshold (RLFASUERR ) = 0 + Predictive Warning Threshold (RLFASUWARN) = 0 + Predictive Action (RLF_CATEGORY_B) = N/A ===============================================================================
|Plan||ARCM||Backout requires an archive tape log mount.|
|GETP||The Getpage to Read I/O ratio indicates poor read efficiency.|
|INDB||The thread is indoubt and terminated.|
|PREF||The Sequential Prefetch rate is high.|
|RIO||The synchronous Read I/O rate is high.|
|ETIM||This thread has reached the Elapsed Time threshold value.|
|PGUP||The rate for system page updates is high.|
|Resource Limit High Water Mark (CPU)||RELM||The ratio of CPU consumption to the resource limit indicates a high resource usage.|
- related topics, select one of the options on the top of the panel.
- other topics, use the PF keys.
- The Db2 plan name of the active thread.
- The Db2 connection identifier of the active thread.
- The Db2 correlation identifier of the active thread. If the correlation is not set, N/A is displayed.
- The Db2 authorization identifier of the active thread.
- Depending on the type of connection, the appropriate information is displayed.
- Attach information is displayed only if the thread is a distributed allied thread (not for distributed database access threads).
- Connection Type
- The MVS™ jobname and ASID.Note: For threads from remote Db2, the MVS job name is N/A.
- The CICS jobname, task name, task number, terminal ID,
and thread type. The thread type is:
- The thread in use is a pool thread.
- The thread in use is a nonprotected entry thread.
- The thread in use is a protected thread. Protected threads are defined in an RCT entry definition using the THRDS operand.
- The IMS region number, transaction name, region name, and terminal ID (LTERM).
- The MVS job name and ASID.Note: For threads from remote Db2, the MVS job name is N/A.
- The originating Db2 job name and the resource manager that is the source of the thread. An additional line below the Attach line identifies the user thread, if any, being served by the system thread.
- The TSO user ID and region ASID.
- No additional information.
- The Db2 subsystem identifier.
- The MVS system identifier.
- The original (primary) Db2 authorization identifier of the thread. This field displays only when the original identifier is different from the Authid.
- The distributed thread type.
- Distributed Allied
- A requesting thread; one that has issued an SQL call to a remote DB2 location.
- Database Access
- A responding thread; one that is serving a remote DB2 location by responding to an SQL call.
- This value consists of two parts: the logical unit
of work ID (luw-id) and a token. The token can be used in place of
the luw-id in any Db2 command
that accepts luw-id as input. Format:
The luw-id consists of the network name, the originating VTAM® LUNAME, and a unique identifier (separated by periods). Thus, the Luwid field displays data such as the following:
- Resource Limit Table Name in Use
- The name of the Db2 resource limit specification table (RLST) currently in use by the DB2 subsystem.
- Resource Limit Origin
- The origin of the resource limit in effect for this thread, if resource limiting is active. The
origin is determined by the hierarchical precedence order within the resource limit specification
table (RLST). The possible origins are:
- Table entry containing matching authid and plan name.
- Table entry containing matching authid, and plan name was blank.
- Table entry containing matching plan name, and authid was blank.
- Blank Entry
- Table entry containing blank plan name and authid.
- No table entry exists; the value in effect was determined from the RLFERR/RLFERRD parameter of the DSNZPARM module.
- I/O Error
- Resource limit table I/O error; the value in effect was determined from the RLFERR/RLFERRD parameter of the DSNZPARM module.
- Table entry is install SYSADM or SYSOPR. No limits apply to these authorization groups.
- Table entry containing matching authid, collection and package.
- Auth Any Pkg
- Table entry containing matching authid and collection, and blank package.
- Auth any Coll
- Table entry containing matching authid and package, and blank collection.
- Auth Any Pkg/Coll
- Table entry containing matching authid and blank collection and package.
- Pkg/Coll Any Auth
- Table entry containing matching package and collection.
- Any Auth/Pkg
- Table entry containing matching collection and blank authid and package.
- Any Auth/Coll
- Table entry containing matching package and blank authid and collection.
- Any Auth/Coll/Pkg
- Table entry containing blank authid, collection and package.
- Resource Limit in Effect (SUs)
- The resource limit in MVS service units for the thread. Express® DB2 limits in service units. If the origin is Sysadm/Sysopr or the ASUTIME parameter is NULL, no limits apply.
- Resource Limit CPU Time per SU
- The number of CPU seconds per service unit. The number of CPU seconds per service unit depends upon the CPU model in use. This is helpful in understanding the actual CPU time allowed by the resource limit specified (in SUs). This value is expressed in seconds.
- Resource Limit in Effect (CPU secs)
- The resource limit in effect in CPU seconds. This is the actual CPU time allowed, based on the service units limit specified in the Db2 resource limit table. This value is expressed in seconds. If the origin is Sysadm/Sysopr or the ASUTIME parameter is NULL, no limits apply.
- Resource Limit High Water Mark (CPU)
- The highest CPU time used for a single dynamic request since thread creation. This value is expressed in seconds. This value can be higher than the value of Resource Limit in Effect (CPU secs) because of the logic for checking the high- water mark of the DB2 subsystem. This field will display a high- water mark value even if the thread is not governed by the Resource Limit Facility. (In that case, the Ratio of HWM to Resource Limit will be No Limit.)
- Ratio of HWM to Resource Limit (CPU)
- The ratio/percentage of the CPU high- water mark (HWM) to the CPU resource limit in effect. This value can be higher than 100% because of the logic for checking the high- water mark of the Db2 subsystem.