IOACTIVITY command with REPORT subcommand

This section describes the IOACTIVITY command with the REPORT subcommand.

Usage

Use the REPORT subcommand to generate reports from records.

Usage notes

  • Up to five REPORT subcommands can be specified within each IOACTIVITY command.

Syntax of the REPORT subcommand

Read syntax diagramSkip visual syntax diagramREPORTFROM/TO blockLEVEL(,SUMMARYACTLOGARCLOGBUFFEREDMXI)DDNAME(IORPTDDddname)ORDER blockINCLUDE/EXCLUDE block

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 reporting process by date and time.

For details, see FROM/TO subcommand options.

LEVEL
Specifies the level of the report. The following keywords can be used with LEVEL:
SUMMARY
Gives a summary of all I/O activity for the following categories:
  • Buffer pool
  • EDM pool
  • Active log
  • Archive log and BSDS
  • Cross invalidation
SUMMARY also gives the grand totals of all the I/O statistics for the reporting interval for each category. It provides a quick overview of system-wide I/O activity to help monitor trends and identify potential problem areas.
The following levels generate detail reports. See the ORDER subcommand option for default ordering of detail reports.
ACTLOG
The active log report presents counts and average elapsed time for reads, writes, and other I/O activity.
ARCLOG
The archive log/BSDS report presents the archive log and BSDS read and write requests.
BUFFER
The buffer pool report presents successful and unsuccessful asynchronous and synchronous (prefetch) read requests and write requests.
EDM
The environmental descriptor manager pool report presents cursor table (CT), package table (PT), and database descriptor (DBD) references, loads from a hard disk drive, elapsed time for each load, and average section lengths.
XI
The cross-invalidation report presents buffer refresh events caused by aggregated cross invalidation.

The default for LEVEL is SUMMARY.

DDNAME
Specifies the data set where the report is written. You can specify any valid ddname including the default, provided that your JCL contains a DD statement for it. If a DD statement is omitted, it will be dynamically allocated to the SYSOUT message class of the job. The default ddname for report is IORPTDD.
ORDER
Specifies the OMEGAMON for Db2 PE identifiers and their sequence for sorting detail reports. Note that ORDER cannot be used with LEVEL(SUMMARY), which is the default. To use ORDER, you must specify LEVEL with one or more of the detail levels.

For details, see ORDER subcommand option and OMEGAMON for Db2 PE identifiers.

The default for ORDER (if not explicitly specified) depends on the specification of LEVEL:
  • LEVEL(ACTLOG) orders by DATASET.
  • LEVEL(ARCLOG) orders by DATASET.
  • LEVEL(BUFFER) orders by PRIMAUTH-PLANNAME-BPID.
  • LEVEL(EDM) orders by PRIMAUTH-PLANNAME.
  • LEVEL(XI) orders by PRIMAUTH-PLANNAME.
  • If LEVEL specifies multiple detail reports, default ordering is by PRIMAUTH-PLANNAME.

If ORDER is used once, and if LEVEL specifies multiple detail reports, each detail report is ordered by the OMEGAMON for Db2 PE identifiers specified with ORDER.

If ORDER is used multiple times, and if LEVEL specifies one or more detail reports, each detail report is repeated for each specified ordering.

Note: The EDM pool report contains the plan name and the database name. Ordering by these identifiers results in repetitious information.
In the following example ORDER specifies that three EDM pool reports are produced. 
 
REPORT
   LEVEL (EDM)
   ORDER (PRIMAUTH-PLANNAME-REQLOC
          CONNECT-PLANNAME INTERVAL-PRIMAUTH-PLANNAME)
  • The first report is ordered by requesting location within plan name within primary authorization ID.
  • The second report is ordered by plan name within connection ID.
  • The third report is ordered by requesting location within primary authorization ID within interval.
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 REPORT with FROM, TO, LEVEL, and INCLUDE options

This example specifies the following:
  • A summary report
  • Using records with the time and date range of 10:00 a.m. on 22 November 2002 to noon on 23 November 2002
  • Data is included that is only associated with the location in the range of LOCN01 to LOCN05
REPORT
   FROM    (11/22/02,10:00:00.00)
   TO      (11/23/02,12:00:00.00)
   LEVEL   (SUMMARY)
   INCLUDE (LOCATION(R(LOCN01 LOCN05)))

Example using REPORT with FROM, TO, LEVEL, ORDER, and EXCLUDE options

This example specifies the following:
  • A buffer pool report
  • Sorted by plan name within primary authorization ID within correlation name
  • Records are used with the time and date range of 10:00 a.m. on 18 March 2002 to noon on 19 March 2002
  • Data is excluded that is associated with the following locations:
    • LOCN10
    • LOCN12
    • LOCN15
    • LOCN20
REPORT
   FROM    (03/18/02,10:00:00.00)
   TO      (03/19/02,12:00:00.00)
   LEVEL   (BUFFER)
   ORDER   (CORRNAME-PRIMAUTH-PLANNAME)
   EXCLUDE (LOCATION(LOCN10 LOCN12 LOCN15 LOCN20))

Example using IOACTIVITY with REDUCE and REPORT subcommands

This example requests the following:
  • Reduce only input data with a timestamp within the time range of 10:30 to 11:00 on 14 May 2002.
  • Create a summary report (the default) with the default order of PLANNAME within PRIMAUTH.
  • Write the report to the data set defined by the default ddname IORPTDD.
IOACTIVITY
   REDUCE
   FROM (05/14/02,10:30:00.00)
   TO   (,11:00:00.00)
   REPORT