Check with the the DBA' s if DB2 statistical, accounting, and audit trace data are being collected
When you install DB2, you can specify if DB2 statistical, accounting, and audit trace data are to be collected. To have DB2 collect:
* Statistical information, accept the default (YES class 1) for the SMF STATISTICS option on installation panel DSNTIPN. To collect statistical information for deadlock or timeout, specify class 3. To collect information about DDF error conditions, specify class 4.
* Accounting information, accept the default (1) or specify * (all classes) for the SMF ACCOUNTING option on installation panel DSNTIPN.
* Auditing information, specify * (all classes) for the AUDIT TRACE option on installation panel DSNTIPN.
In all cases, DB2 invokes a trace, passing the data it collects to the System Management Facility (SMF) of z/OS?. For more information about the START TRACE command, see DB2 Command Reference.
DB2 also passes performance data to SMF whenever an accounting, statistics, or audit trace is successfully started or stopped. DB2 can also record other performance data. After you complete the installation process, you can use commands to have DB2 record performance data for over 230 different subsystem events.
See DB2 Command Reference to see what kind of data DB2 can collect and pass to SMF.
You must make some additional updates if, during installation, you requested that DB2 pass accounting and statistics data to SMF. Specifically, you must update the SMFPRMxx member of SYS1.PARMLIB as follows:
* Specify the ACTIVE parameter.
* Specify the proper TYPE subparameter of SYS and SUBSYS.
During DB2 execution, you can use the SMF SET or SS command to alter the SMF parameters. For example, you can record the statistics trace class 1 IFCIDs 0001, 0002, and 0202 (SMF record type 100); accounting trace class 1 IFCIDs 0003 and 0239 (SMF record type 101); and all other DB2 trace records (SMF record type 102) to SMF. To record this information, issue the following command:
For DB2 to pass data to SMF, you must allocate an adequate supply of SMF buffers. The default buffer settings are probably insufficient.
You can specify SMF buffering on the VSAM BUFSP parameter of the Access Method Services DEFINE CLUSTER statement. Do not use the default settings if DB2 data is sent to SMF. Specify CISZ(4096) and BUFSP(81920) on the DEFINE CLUSTER statement for each SMF VSAM data set. These values for CISZ and BUFSP are the minimum requirement for DB2. You might need higher values for CISZ and BUFSP, depending on the requirements of all your z/OS subsystems.
You can also code an IEFU84 SMF exit routine to process the records that are produced.
Detailed information about starting and stopping DB2 traces for performance, accounting, audit, and statistics data is provided in DB2 Administration Guide.