IFCID 002 - Service Controller Data

This topic shows detailed information about Record Trace - IFCID 002 - Service Controller Data.

Record Trace - IFCID 002 - Service Controller Data

The field labels shown in the following sample layout of Record Trace - IFCID 002 - Service Controller Data are described in the following section.


SERVICE CONTROLLER DATA
PLAN ALLOC.ATTMP        142  PACK.ALLOC.ATTMP          6  OPEN DATASETS - HWM           102  AUTHORIZ.ATTEMPTS       1034
PLAN ALLOC.SUCC.        142  PACK.ALLOC.SUCC.          6  OPEN DATASETS - CURR.         101  AUTHORIZ.SUCCESS.       1034
PLANS BOUND              30  PACKAGES BOUND           67  DS NOUSE,NOCLOSE-HWM          101  AUTH.SUCC-NO CAT.         37
BIND PLAN (ADD)           0  BIND PACK (ADD)           0  DS NOUSE,NOCLOSE-CURR.        100  AUTH.SUCC-PUBLIC           0
BIND PLAN (REPL)         30  BIND PACK (REPL)         67  DS CLOSED-THRESH.REACH          0  PKG-AUTH.SUCC              0
AUTOB.PLAN ATTMP          1  AUTOB.PACK ATTMP          0  DS CLOSED-INFRQ ACCESS          2  PKG-AUTH.SUCC-PUB          0
AUTOB.PLAN SUCC.          1  AUTOB.PACK SUCC.          0  DS CLOSE-UTIL ACC ONLY          3  PKG-AUTH.UNSUCC            3
AUTOB.PLAN ATTMP          1  AUTOB.PACK ATTMP          0  R/W TO R/O CONVERSIONS         97  PKG-AUTH.SUCC-PUB          0
AUTOB.PLAN SUCC.          1  AUTOB.PACK SUCC.          0                                     PKG-AUTH.UNSUCC            3
REBIND PLAN COMM          0  REBIND PACK COMM          0                                     PKG-AUTHID OWRTN           0
REBIND PLAN ATTM          0  REBIND PACK ATTM          0                                     PKG-ENTRY OWRTN            0
PLANS REBOUND             0  PACKAGES REBOUND          0                                     RTN-AUTH.SUCC              2
FREE PLAN COMMND          0  FREE PACKAGE COM          0                                     RTN-AUTH.SUCC-PUB          0
FREE PLAN ATTMPT          0  FREE PACK ATTMPT          0                                     RTN-AUTH.UNSUCC            6
PLANS FREED               0  PACKAGES FREED            0                                     RTN-AUTHID OWRTN           0
TEST BINDS                0  AUTOB.INV.RES.ID          0                                     RTN-ENTRY OWRTN            0
QTREOPN                2346                                                                  RTN-CACHE NO ADD           0
                                                                                             PLN-AUTH.UNSUCC            0
                                                                                             PLN-AUTHID OWRTN           0
PLAN ALLOC.ATTMP

The number of times a request was made to allocate a bound plan for an agent.

It represents the number of times DB2 was requested to create a thread by the attachment facility for the user. This does not include allocations for DB2 system agents.

Field Name: QTALLOCA

PACK.ALLOC.ATTMP

The number of attempts to allocate a package.

Field Name: QTPKALLA

OPEN DATASETS - HWM

The maximum number of data sets concurrently open since the last time DB2 was started. This is a high-water mark (HWM).

Background and Tuning Information

Monitor this field to see whether you are reaching the maximum number of open data sets permissible.

Note: The maximum number of open data sets is 200,000. The default is 20,000.

Field Name: QTMAXDS

AUTHORIZ.ATTEMPTS

The number of authorization checks performed for plans, packages, and stored procedures since DB2 was started. This includes successful and failed checks.

Field Name: QTAUCHK

PLAN ALLOC.SUCC.

The number of successful plan allocation attempts.

The cause of plan allocation failure could be plan unavailability or attempting to allocate a nonexistent plan.

Field Name: QTALLOC

PACK.ALLOC.SUCC.

The number of successful package allocation attempts.

Background and Tuning Information

Package allocation failure can occur when a package is unavailable or does not exist.

A high count of the number of packages unsuccessfully allocated (QTPKALLA - QTPKALL) typically occurs when a package list with multiple collections is used and frequently-used packages are found in the back end rather than in the front end of a package list. For example, when a package is found in the tenth collection, QTPKALLA is incremented by 10, one for each collection searched, but QTPKALL is incremented by 1.

A high number of packages unsuccessfully allocated can be accompanied by a high count of the number of unsuccessful checks for package execute authority made using the package authorization check because an application entry was not found in the cache (QTPACNOT). In this case, placing frequently used packages in the front end of a package list would reduce the number of Buffer Manager Getpages to the catalog/directory tablespaces.

Field Name: QTPKALL

OPEN DATASETS - CURR.
The number of data sets concurrently open (snapshot).

Field Name: QTDSOPN

AUTHORIZ.SUCCESS.

The number of successful authorization checks performed on plans, packages, and stored procedures, since DB2 was started.

Field Name: QTAUSUC

PLANS BOUND

The number of plans successfully bound and kept for future agent allocations.

This field represents the sum of successful BIND ADD (QTBINDA) and successful BIND REPLACE (QTBINDR) commands. This counter is not incremented for BIND subcommands with no plan ID specified, as identified by QTTESTB. Note that QTBINDA + QTBINDR is not necessarily equal to this field. It is equal only if all BIND ADD and BIND REPLACE subcommands issued are successful.

Field Name: QTPLNBD

PACKAGES BOUND

The number of packages bound and kept for future package allocations.

It is the sum of successful BIND ADD PACKAGE and BIND REPLACE PACKAGE subcommands, but only if all these commands are really issued successfully.

Field Name: QTPKGBD

DS NOUSE,NOCLOSE-HWM

The maximum number of data sets on the deferred close queue. It is a high-water mark representing the maximum number of data sets that are not in use but have not been physically closed yet.

Field Name: QTMAXPB

AUTH.SUCC-NO CAT.

The number of successful authorization checks that do not use the DB2 catalog (including plan cache checks and public checks).

Background and Tuning Information

For transaction level security, ENABLE and DISABLE on BIND PACKAGE should be used to ensure adequate security. Granting execute authority on the plan to public should be adequate.

Field Name: QTAUCCH

BIND PLAN (ADD)

The number of successful and unsuccessful BIND ADD subcommands issued.

The sum of QTBINDA, QTBINDR, and QTTESTB equals the total number of BIND subcommands.

Field Name: QTBINDA

BIND PACK (ADD)

The number of successful and unsuccessful BIND ADD PACKAGE subcommands issued.

Field Name: QTBINDPA

DS NOUSE,NOCLOSE-CURR.

The number of data sets that are not currently used, but are not closed due to a deferred close (snapshot).

Field Name: QTSLWDD

AUTH.SUCC-PUBLIC

The number of successful authorization checks based on EXECUTE authority granted to PUBLIC.

Field Name: QTAUPUB

BIND PLAN (REPL)

The number of successful and unsuccessful BIND REPLACE subcommands issued.

Field Name: QTBINDR

BIND PACK (REPL)

The number of successful and unsuccessful BIND REPLACE PACKAGE subcommands issued.

Field Name: QTBINDPR

DS CLOSED-THRESH.REACH

The number of data sets that were closed because the total number of open data sets reached the deferred close threshold value. The deferred close value is based on the value of DSMAX or the MVS DD limit (whichever is smaller).

Field Name: QTDSDRN

PKG-AUTH.SUCC

The number of successful package EXECUTE authorization checks without accessing the DB2 catalog.

Field Name: QTPACAUT

AUTOB.PLAN ATTMP

The number of attempts to autobind a plan. This occurs when the plan was invalidated by modifications to the declarations of the data referenced by the programs bound as part of the plan. For example, dropping an index when it is used in the plan results in automatic bind.

Field Name: QTABINDA

AUTOB.PACK ATTMP

The number of attempts to autobind a package.

Background and Tuning Information

If YES was specified, or defaulted, for autobind on DB2 install panel DSNTIPB, an autobind occurs when a plan or package:
  • Is invalid because declarations of the data referenced by the program or package were modified. For example, when an index used in a package is dropped, an automatic bind occurs when the package is run for the first time after the index was dropped.
  • Was bound in a later release and is used in a previous release for the first time.
  • Was used in a previous release but is later remigrated and used in a later release for the first time.

Field Name: QTAUTOBA

DS CLOSED-INFRQ ACCESS

The number of infrequently accessed data sets that are physically closed.

Field Name: QTPCGBP

R/W TO R/O CONVERSIONS

The number of infrequently updated data sets that are converted from R/W to R/O state. An updated data set is considered infrequently updated when it has not been updated for either 5 consecutive DB2 checkpoints or 60 minutes. For tablespace data sets, the switching from R/W to R/O state means the SYSLGRNG entry is closed.

Field Name: QTPCCT

PKG-AUTH.SUCC-PUB

The number of successful package EXECUTE authorization checks without accessing the DB2 catalog. Package EXECUTE authority was granted to PUBLIC in the package authorization cache.

Field Name: QTPACPUB

AUTOB.PLAN SUCC.

The number of plans successfully autobound.

Field Name: QTABIND

AUTOB.PACK SUCC.

The number of packages successfully autobound.

Field Name: QTPKABND

DS CLOSE-UTIL ACC ONLY

The number of utility-access-only data sets that are physically closed.

Field Name: QTPCUT

PKG-AUTH.UNSUCC

The number of unsuccessful package EXECUTE authorization checks in the package authorization cache. No applicable entry was found in the cache and DB2 catalog access was used.

Field Name: QTPACNOT

REBIND PLAN COMM

The number of REBIND subcommands issued. More than one plan can be rebound with a single REBIND subcommand. If the value in this field is 1, the number of plans you are attempting to rebind is shown in the Rebind - plan attempts field.

Field Name: QTREBIND

REBIND PACK COMM

The number of REBIND PACKAGE subcommands issued. More than one package can be rebound with a single subcommand. If the value in this field is 1, Rebind - package attempts shows the number of packages you are attempting to rebind.

Field Name: QTRBINDP

PKG-AUTHID OWRTN

The number of times an authorization ID was overwritten to add another one to the package authorization cache.

Field Name: QTPACOW1

REBIND PLAN ATTM

The number of attempts to rebind a plan. This number can be larger than the value shown in the Rebind - plan subcommands field because you can specify more than one plan in a single REBIND subcommand.

Field Name: QTRBINDA

REBIND PACK ATTM

The number of attempts to rebind a package. This can be larger than the value shown in Rebind package subcommands because you can rebind more than one package with a single command.

Field Name: QTRBNDPA

PKG-ENTRY OWRTN

The number of times an entry for a collection-ID or package-ID was overwritten to add another one to the package authorization cache.

Field Name: QTPACOW2

PLANS REBOUND

The number of rebind attempts that completed successfully. This field is equal to the Rebind - Plan attempts field if all specified plans rebound successfully.

Field Name: QTPLNRBD

PACKAGES REBOUND

The number of packages successfully rebound. If all specified packages were rebound successfully, this field is equal to Rebind package attempts.

Field Name: QTPKGRBD

RTN-AUTH.SUCC

The number of times the routine authorization cache was checked successfully of EXECUTE authority on a stored procedure or user-defined function. The DB2 catalog was not accessed. This counter includes the number of PUBLIC authorization checks.

Field Name: QTRACAUT

FREE PLAN COMMND

The number of FREE subcommands issued.

More than one plan can be freed with a single FREE subcommand. If this field is 1, then the number of plans you are trying to free is shown in ATTEMPTS TO FREE A PLAN.

Field Name: QTFREE

FREE PACKAGE COM

The number of FREE PACKAGE subcommands issued.

More than one package can be freed with a single FREE subcommand. If the value in this field is 1, then the number of packages you are attempting to free is shown in ATTEMPTS TO FREE A PACKAGE.

Field Name: QTFREEP

RTN-AUTH.SUCC-PUB

Number of successful authorization checks for user-defined function or stored procedure execution authority when that authority is held by PUBLIC. The DB2 catalog was not checked.

Field Name: QTRACPUB

FREE PLAN ATTMPT

The number of attempts to free a plan.

This value can be larger than FREE PLAN SUBCOMMANDS because multiple plan IDs can be specified in a single FREE subcommand.

Field Name: QTFREEA

FREE PACK ATTMPT

The number of attempts to free a package. This number can be larger than FREE PACKAGE SUBCOMMANDS because you can free several packages with a single command.

Field Name: QTFREEAP

RTN-AUTH.UNSUCC

Number of unsuccessful authorization checks for user-defined function or stored procedure EXECUTE authority because no applicable entry was found in the routine authorization cache.

Field Name: QTRACNOT

PLANS FREED

The number of times a plan was successfully freed.

Freeing a plan can fail if someone else is using the plan and holds a lock on it.

Field Name: QTPLNFRD

PACKAGES FREED

The number of times a package was successfully freed. If all the specified packages were freed successfully, the value of this field is equal to ATTEMPTS TO FREE A PACKAGE.

Field Name: QTPKGFRD

RTN-AUTHID OWRTN

Number of times an individual authorization ID was overwritten in an entry of the routine authorization cache.

Field Name: QTACOW1

TEST BINDS

The number of BIND subcommands issued without a plan ID.

Field Name: QTTESTB

AUTOB.INV.RES.ID

The number of requests to allocate a nonexistent plan or package. This is the number of all plan and package allocation attempts that failed because the resource was unavailable or the object did not exist.

Field Name: QTINVRID

RTN-ENTRY OWRTN

Number of times that DB2 overwrote a routine entry in the routine authorization cache.

An entry in the routine authorization cache can refer to a function or procedure or to all functions or procedures within a specific schema.

Field Name: QTRACOW2

RTN-CACHE NO ADD

Number of times that DB2 could not add an entry to the routine authorization cache.

An entry in the routine authorization cache can refer to a function or procedure or to all functions or procedures within a specific schema.

Field Name: QTRACNAC

PLN-AUTH.UNSUCC

Number of unsuccessful checks for plan EXECUTE privilege made using the plan authorization cache because an applicable entry was not found in the cache.

Field Name: QTAUCNOT

PLN-AUTHID OWRTN

Number of times Db2 overwrote an authorization ID in the plan authorization cache.

Field Name: QTAUCOW1