6. DATA SOURCES › 6.5 ACCUMACC Roll-up Records › 6.5.2 ACCUMACC and Transaction Level Files

6.5.2 ACCUMACC and Transaction Level Files

FILE: DB2 User DDF Activity (DB2DDU)

The DB2 User DDF Activity (DB2DDU) file will not contain
observations for ACCUMACC roll-up records.  In DB2 Version 8,
the DB2 DSNDQLAC DDF metrics are not rolled-up for DDF
transactions.  Normally, the SMF type 101 subtype 0
transaction accounting record for DDF activity contains a
record segment containing the DDF metrics defined in the DB2
DSNDQLAC macro.  This SMF record yields a DB2DSU file user
activity record and a corresponding DB2DDU file DDF activity
record in your CA MICS database.  With ACCUMACC, you will no
longer have DB2DDU file observations for rolled-up DDF
transaction records.

FILES: DB2 User Activity (DB2DSU)
       DB2 Plan Activity (DB2DSP)

The DB2 User Activity (DB2DSU) and DB2 Plan Activity (DB2DSP)
files are built from SMF type 101 subtype 0 transaction
accounting records.  At the DETAIL timespan, these two files
are virtually identical.  The difference in these files is
found in the DAYS and higher timespans.  The DB2 Account Code
data elements are used as summarization keys in the DB2DSU
file, allowing the file to be summarized by user related
metrics.  The DB2DSP file, on the other hand, includes DB2
Plan Name (DB2PLAN) and Connection Identifier (DB2CONN) in
the summarization keys providing for a more technical
summarization of transaction activity.

In the DETAIL timespan, you can identify DB2DSU and DB2DSP
file observations representing ACCUMACC roll-up records by
examining the value of the Special Transaction Type
Identifier (DB2PTASK) data element.  DB2PTASK='ACUMAC' for
ACCUMACC roll-up records.

Data elements in these files are adjusted as described below
for observations created from ACCUMACC roll-up records (note
that fff represents both DSP and DSU):

o Modified data elements:

  fffNTHRD - Count of Threads Initiated

  For non-ACCUMACC records, fffNTHRD is set to 1 in each
  DETAIL timespan DB2fff file observation.  For ACCUMACC
  roll-up records, however, fffNTHRD is set to the value of
  field QWACPCNT, which contains the number of individual
  accounting records summarized in the roll-up record.

o Unavailable data elements:

  fffBGTCB - Beginning TCB Timer
  fffENTCB - Ending TCB Timer
  fffENTEX - No. of Entry/Exit Events Processed
  DB2NETID - Network Identifier

  For ACCUMACC records, the raw data fields from which these
  data elements are unavailable or redefined.  The CA MICS
  DB2 Analyzer sets these elements to missing values for
  ACCUMACC roll-up records.

o Data elements reflecting the value of the last accounting
  record to be rolled up:

  DB2AUTH  - Authorization Identifier
  DB2CORR  - Correlation Identifier
  DB2CONN  - Connection Identifier
  DB2PLAN  - Plan Name
  DB2OPID  - Original Operator ID
  fffCATYP - Connecting System Type Code
  fffCICLU - CICS Terminal LU Name
  fffCICNT - CICS Network Identifier
  fffCICUW - CICS Logical Unit of Work ID

  These data elements are all included, unmodified, in the
  DB2DSU file observations for ACCUMACC roll-up records.
  Note that the value represented may not reflect the value
  encountered in all records summarized in the roll-up.  Per
  IBM, the value stored in the SMF roll-up record represents
  the value encountered in the last record rolled-up.

The following data elements are provided to assist in
understanding ACCUMACC activity:

  fffACNT  - No. ACCUMACC Records Encountered
  fffACUTR - ACCUMACC Count: Threshold Exceeded
  fffACSTR - ACCUMACC Count: Storage Exceeded
  fffACSTL - ACCUMACC Count: Staleness

  fffACNT is set to 1 for observations created from ACCUMACC
  roll-up records.  In the same observation, one of the other
  three data elements is set to 1 based on the reason that
  the roll-up record was written.

  fffNATHD - Count of ACCUMACC Roll-up Threads

  fffNATHD is set equal to the number of individual
  accounting records rolled-up in an ACCUMACC roll-up record.
  By dividing fffNATHD by fffACNT, you can determine the
  number of individual records rolled-up, on average, into
  ACCUMACC roll-up records.

FILE: DB2 Package/DBRM Activity (DB2DPP)

The DB2 Package/DBRM Activity (DB2DPP) file is built from SMF
type 101 subtype 1 package records.  This file is the most
impacted by ACCUMACC because a major summarization key data
element in this file, Package/DBRM Name (DB2PKNM) is not
available.

For DDF and RRSAF transaction records rolled-up with
ACCUMACC, the rolled-up SMF type 101 subtype 1 record
contains a single package segment where all package activity
for all rolled-up transactions is summarized.  The raw data
fields that comprise Package/DBRM Name are set to binary
zeros.

The primary purpose of the DB2DPP file is to permit analysis
of DB2 package activity, by Package/DBRM Name.  With ACCUMACC
summarization masking package name, DB2DPP file observations
for rolled-up DDF and RRSAF transactions are of dubious
value.  In addition, there is no indication of the number of
individual package segments represented by the accumulated
numeric data elements.

Rather than storing binary zeros in the DB2PKNM data element,
the Analyzer Option for DB2 stores the value 'ACCUMACC 
ROLLUP RECORD' in observations created from ACCUMACC 
roll-up records.

In the DETAIL timespan, you can identify DB2DPP file
observations representing ACCUMACC roll-up records by
examining the value of the Special Transaction Type
Identifier (DB2PTASK) data element, DB2PTASK='ACUMAC' for
ACCUMACC roll-up records.  Additionally, the DB2PKNM data
element will always contain 'ACCUMACC ROLLUP RECORD'.

Data elements in the DB2DPP file are adjusted as described
below for observations created from ACCUMACC roll-up records:

o Unavailable data elements:

  DPPAAFG  - Activity Flag
  DPPAANM  - Name of Activity
  DPPASCH  - Nested Activity Schema Name
  DPPBEGSC - Package/DBRM Beginning Store Clock
  DPPBGTCB - Package/DBRM TCB Time At Entry To DB2
  DPPDBRM  - Number of DBRMs
  DPPELRTM - Elapsed Time for Most Recent Execution
  DPPENDSC - Package/DBRM Ending Store Clock
  DPPENTCB - Package/DBRM TCB Time At Exit From DB2
  DPPENTEX - Entry/Exit Events Processed
  DPPINSP  - No. Packages Loaded by Stored Proc.
  DPPNSTP  - Number of Native SQL Procedure
  DPPPACK  - Number of Packages
  DPPSPNS  - No. Stored Procedures Executed
  DPPSQLC  - SQL Stmts Issued
  DPPSUAC  - No. Successful Authorization Checks
  DPPTCRTM - TCB Time for Most Recent Execution
  DPPUDNU  - No. User-Defined Functions Scheduled

  For ACCUMACC records, the raw data fields from which these
  data elements are derived are unavailable or redefined.
  The CA MICS Analyzer Option for DB2 sets these elements 
  to missing values for ACCUMACC roll-up records.