Using the Product in a DB2 Environment › Background DB2 Catalog Extraction › Synchronous Data Gatherer › DB2 Harvester and Data Collection Settings

DB2 Harvester and Data Collection Settings

Following lists the DB2 Harvester and data collection settings in TUNSSP00 that are used by CA MAT.

DB2HRVST

Synchronous Data Gatherer activation.

During initialization of the Server, this parameter prepares the environment for the Harvester to accept START and STOP exit commands.

When the DB2 Harvesters are in place, absolute DB2 counts, CPU time, and elapsed times are gathered.

The following are valid responses:

• YES activates the DB2 Harvester facility and allows CA MAT to gather data.
• NO prevents the activation of the DB2 Harvester facility and CA MAT does not gather data.

The default is DB2HRVST=NO (for no DB2 support).

Recommendation: When customizing for DB2 support, set this value to YES.

DB2HVEXT

Exit name.

Specify the name of the exit to be used when a Harvester is started during a monitor session.

The following are valid values:

• DB2E1 — harvest non-COMMIT SQL calls to DB2
  (see also DB2HVSE1)
• DB2E2 — harvest only COMMIT calls to DB2
  (see also DB2HVSE2)
• DB2E3 — harvest both COMMIT and other SQL calls to DB2
  (see also DB2HVSE3)

Recommendation:

Use the default parameter, DB2E3, to collect the most complete data.

When using the default, you should also review DB2HVSE3 to define the DB2 subsystems where you would like CA MAT to implant the DB2 Harvester during startup processing.

The default is DB2HVEXT=DB2E3.

DB2HVSE1

Plant DB2 Harvester exit DB2E1 at server start.

Use this parameter to avoid losing some data related to the first call to DB2. This parameter allows the Server initialization process to implement the Harvester exit during startup.

Specify a list up to 12 DB2 subsystems that a Harvester START command can issue for the DB2E1 exit.

The format is DB2HVSE1=ssid,ssid,ssid,...

This parameter should only be used when DB2HVEXT=DB2E1 is specified.

There is no default.

DB2HVSE2

Plant DB2 Harvester exit DB2E2 at server start.

Use this parameter to avoid losing some data related to the first call to DB2. This parameter allows the Server initialization process to implement the Harvester exit during startup.

Specify a list up to 12 DB2 subsystems that a Harvester START command can issue for the DB2E2 exit.

The format is DB2HVSE2=ssid,ssid,ssid,...

This parameter should only be used when DB2HVEXT=DB2E2 is specified.

There is no default.

DB2HVSE3

Plant DB2 Harvester exit DB2E3 at server start.

Use this parameter to avoid losing some data related to the first call to DB2. This parameter allows the Server initialization process to implement the Harvester exit during startup.

Specify a list up to 12 DB2 subsystems that a Harvester START command can issue for the DB2E3 exit.

The format is DB2HVSE3=ssid,ssid,ssid,...

This parameter should only be used when DB2HVEXT=DB2E3 is specified.
Note: DB2HVEXT=DB2E3 is the default.

There is no default.

DB2HVLOC

Harvest the requesting location.

The requesting location name is generally of importance for distributed DB2 threads. The name can help to identify where the SQL originated from.

Most other threads originate from the local location.

The following are valid responses:

• YES - Use LOCATION as part of the key to gather information.
• NO - Do not add LOCATION to the key.

The default is DB2HVLOC=YES.

DB2HVCOR

Use correlation ID as part of the key.

Collect the DB2 correlation ID for the DB2 data in both the Harvester and the sampling process.

This option adds a higher level of granularity to the DB2 data being collected.

• For IMS, the correlation ID is the PSB name.
• For CICS, the correlation ID is the transaction name.
• For Batch type threads, the correlation ID is the job name.
• For remote and RRSAF threads, the value in this field is dependent on the requesting application.

The following are valid responses:

• YES - Use the DB2 correlation ID in building the key.
• NO - Do not add correlation ID to the key.

The default is DB2HVCOR=YES.

DB2HVIID

Use operator ID as part of the key.

Collect the DB2 primary operator ID for the DB2 data in both the Harvester and the sampling process.

This option adds a higher level of granularity to the DB2 data being collected.

The following are valid responses:

• YES - Use the DB2 operator ID in building the key.
• NO - Do not add operator ID to the key.

The default is DB2HVIID=YES.

DB2HVTHD

Use thread address as part of the key.

Add the DB2 Thread Agent Control Element address to the data being collected by the Harvester and the sampling process.

The following are valid responses:

• YES - Use the DB2 thread address in building the key.
• NO - Do not add the DB2 thread address to the key.

The default is DB2HVTHD=YES.

CAFSTALL

DB2 CAF interface timeout value.

Specify a timeout value in seconds.

When CA MAT issues calls to DB2 to obtain Explain data, CA MAT sets a timer. If the timer expires before the Explain data is returned, CA MAT assumes the DB2 region is stalled. For large DB2 systems, the default of 90 seconds might not be sufficient to return DB2 Explain data. For these cases, CAFSTALL allows the site to specify the timer amount in seconds.

Default is 90.

DB2LIBS

DB2 parameter member suffix.

Specify a TUNDB2xx member with this keyword.

The CAF Interface loads DB2 interface modules to obtain the SQL statement text from the DB2 catalog. For each version of DB2 you have installed at your site, you need to specify a load library where DSNHLI is located. These load libraries are in the parameter library member of TUNDB2xx, where xx is a two-character suffix or &SYSCLONE.

Default is xx, where xx is the release number of CA MAT.

DB2PACK

DB2 package name.

Specify the name of the DB2 package assigned during the DB2 BIND job during customization.

This job must be run against every DB2 subsystem against which monitors are run.

The default is MATnn, where nn is the value specified for the DB2LIBS keyword (usually the release number of CA MAT).

DB2PLAN

DB2 plan name.

Specify the name of the DB2 plan assigned during the DB2 BIND job during customization.

This job must be run against every DB2 subsystem against which monitors is run.

The default is MATnnDB2, where nn is the value specified for the DB2LIBS keyword (usually the release number of CA MAT).