7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.1 DB2GENIN Customization
7.2.1 DB2GENIN Customization
This section discusses customizing DB2GENIN using the OPTION
and COMPRESS statements.
The OPTION Statement
--------------------
To define DB2 Analyzer file processing options, code the
OPTION statement, specifying one term from each pair of
keywords.
OPTION <NODDF/DDF> <NOSERV/SERV> <NOPKG/PKG> <NOSHARE/SHARE>
<NOBUFFER/BUFFER> <BPELEMENT/NOBPELEMENT>
where:
NODDF/DDF controls whether the Analyzer processes
data for the distributed data facility (DDF)
information contained in the DB2 SMF records.
The default is DDF.
When NODDF is set, the following CA MICS
files are deactivated:
DB2DDY--System DDF Statistics
DB2_SH--System DDF Suspend
DB2DDU--DB2 User DDF Activity
DB2DDP--DB2 Plan DDF Activity
and all DDF-related elements, identified
with cluster code 10, are turned off in
the following files:
DB2DSY--DB2 System Activity
DB2DSD--DB2 Database Activity
DB2DSU--DB2 User Activity
DB2DSP--DB2 Plan Activity
The NODDF option overrides FILE statement
specifications for the DDF files and NAME
statement specifications for the DDF elements in
the other CA MICS DB2 files. See the notes
below for more information about coordinating
the DDF and non-DDF CA MICS files.
NOSERV/SERV controls whether the Analyzer populates
elements whose data comes from fields that IBM
has labeled serviceability fields.
Serviceability fields are used at IBM's request
for problem determination. The only information
provided about these fields comes from the
DSECTs (dummy control sections).
The default is NOSERV, which saves space in the
CA MICS database by not populating the elements
that come from serviceability fields.
Note: The sequence/summary elements for the
following pairs of files should match. If you
tailor the sequence/summary elements in the
Primary File, you should tailor the Associated
DDF File the same way.
Primary Associated Activity
File DDF File Captured
------- ---------- --------
DB2DSY DB2DDY System
DB2DSU DB2DDU User
DB2DSP DB2DDP Plan
Note: The DB2DSP and DB2DDP Plan Activity files
are required for Plan Performance reporting.
These plan activity files are generated by
renaming, at the WORK file level, the DB2DSU and
DB2DDU User Activity file elements.
Because CA MICS WORK files are built using KEEP
lists at the DETAIL timespan, you must ensure
that the DB2DSP and DB2DDP elements are defined
at the DETAIL timespan in the associated DB2DSU
and DB2DDU files.
The DB2DSU and DB2DDU files do NOT have to be
activated at the DETAIL timespan to define
elements in the KEEP list for the DETAIL
timespan. See chapter 4 of the System
Modification Guide for detailed information
about activating CA MICS elements at various
timespans.
NOPKG/PKG controls whether the Analyzer processes
data for packages and database request modules
contained in the SMF type 101 record. The
default, NOPKG, deactivates the DB2DPP file
(Package/DBRM Activity File) and turns off all
related elements, identified with cluster code
13.
NOSHARE/ controls whether the Analyzer processes
SHARE data sharing information. The default, NOSHARE,
turns off elements with cluster code 12 in the
following files:
DB2DSY--DB2 System Activity
DB2DSD--DB2 Database Activity
DB2DSU--DB2 User Activity
DB2DSP--DB2 Plan Activity
NOBUFFER/ controls whether the Analyzer processes
BUFFER Expanded Buffer Pool files. The default,
NOBUFFER, turns off the following files:
DBPDSB--DB2 Buffer Pool Activity
DBPDBU--DB2 User Buffer Pool Activity
DBPDBP--DB2 Plan Buffer Pool Activity
NOBPELEMENT/ controls whether unique data elements for
BPELEMENT buffer pools 0, 1, 2, and 80 are kept in the
DB2DSU, DB2DBU, and DB2DSD files. If
NOBPELEMENT is set, only totals for buffer pool
elements are kept. BPELEMENT is the default.
Each of the above keywords controls the activation of data
elements that are associated with a cluster code. The
following table summarizes the cluster codes used in the DB2
Analyzer.
DB2 Analyzer Cluster Codes
Code Keyword Description
---- --------- --------------------------
10 DDF Distributed Database
Facility
11 SERV Serviceability Fields
12 SHARE Data Sharing
13 PKG Package and DBRM
14 BUFFER Buffer Files
15 BPELEMENT Individual Buffer 0 - 3
Elements
The COMPRESS Statement
----------------------
The SAS system gives you the option to create variable-length
or fixed-length observations in a SAS data set.
Variable-length observations differ from fixed-length
observations in that the former are usually smaller because
the blank spaces used to pad fixed-length observations are
removed.
You instruct SAS to create variable length observations by
specifying the COMPRESS= option. SAS data set compression
can be implemented for individual data sets or across the
entire SAS System. Compression is controlled by the
placement of the COMPRESS= option on either an OPTIONS
statement (for the entire system) or on a DATA statement (for
an individual data set named on the DATA statement).
For more information about the COMPRESS= option, see the SAS
Institute documentation.
Do not compress the DB2 Analyzer's interim work files:
DB2_DS, the System Activity Suspend File
DB2_DD, the Database Activity Suspend File
DB2_SH, the System DDF Suspend File
DB2_DB, the System DBP Suspend File
