ACCOUNTING command with FILE subcommand

This section describes the ACCOUNTING command with the FILE subcommand.

Usage

Use the FILE subcommand to format unreduced DB2® data and store it in sequential data sets suitable for use by the DB2 load utility.

Usage notes

  • In the case of CP parallelism, the logical Accounting record (aggregation of all the activity within the thread) is stored in the data set.
  • The records can be placed in DB2 tables, and you can produce reports by using a reporting facility such as Query Management Facility (QMF).
  • You can also use the FILE data sets to generate CSV (comma-separated value) input-data. This CSV data can then be transferred to workstations and imported into spreadsheets to improve DB2 performance analysis using graphical representations or pivot tables. For more information refer to Reporting User's Guide.

Syntax of the FILE subcommand

Read syntax diagramSkip visual syntax diagramFILEFROM/TO blockNOEXCEPTIONEXCEPTIONDATATYPE(GENERAL,BP,GBP,DDF,PACKAGE,ACCEL)DATATYPE(GENERAL,BP,GBP,DDF,PACKAGE,ACCEL)INCLUDE/EXCLUDE blockDDNAME(ACFILDD1ddname)

Subcommand options

The syntax diagram shows the options that are available with this subcommand. See Subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.

FROM/TO
Limits the range of records included in the data set by date and time.

For details, see FROM/TO subcommand options.

If you are reducing data, the times specified in REDUCE affect the data available for filing.

EXCEPTION
NOEXCEPTION
Specify EXCEPTION if you want to include only those file entries with values outside the user-specified limits. Otherwise, all records are included.

If you use this option, your JCL must contain a valid DD definition for the ddname EXCPTDD. For more information about required ddnames, see Figure 1.

DATATYPE
Specifies which data types are to be written to the FILE data set specified in the DDNAME subcommand option. By default, if DATATYPE is not specified, or if DATATYPE() is specified (without keywords), all data types are written.

This subcommand option lets you improve the system performance while the data set is generated by explicitly specifying only the required data types. If performance is not critical, you can safely ignore this subcommand option. Use one or more of the following keywords to specify the required data types.

GENERAL
General performance data
BP
Buffer pool performance data
GBP
Group buffer pool performance data
DDF
Distributed Data Facility (DDF) data
PACKAGE
Package execution data
ACCEL
Accelerator data
DDNAME
Specifies the ddname where the file data set is written. The default ddname is ACFILDD1 for the first file instance, ACFILDD2 for the second file instance, and so on.
INCLUDE/EXCLUDE
Includes or excludes data associated with specific OMEGAMON® for DB2 PE identifiers.

For details, see INCLUDE and EXCLUDE subcommand options, which lists other identifiers allowed with this command and subcommand combination, and OMEGAMON for Db2 PE identifiers.

Example using FILE with EXCEPTION and INCLUDE options

This example specifies a file that includes only exception records for User10, User11, and User12. The file is generated on ddname ACFILDD1 by default.

⋮
FILE
   EXCEPTION
   INCLUDE (PRIMAUTH(USER10 USER11 USER12))
⋮