UTILITY command with REPORT subcommand

This section describes the UTILITY 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 UTILITY command.

Syntax of the REPORT subcommand

Read syntax diagramSkip visual syntax diagramREPORTFROM/TO blockTYPE(BIND - UTILITYBINDUTILITY)ORDER blockDDNAME(UTRPTDDddname)INCLUDE/EXCLUDE block

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.

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.

TYPE
Specifies the activity types. You can select one or both of these activity types with each REPORT subcommand:
BIND
Gives the elapsed time for each occurrence of a bind event. This includes information on the number of bound and nonbound events and the distribution of the bind into various bind subevents.
UTILITY
Gives the elapsed time for each occurrence of a utility event. Also provides information on the performance and resource usage of the various utility events.

If the TYPE subcommand option is omitted, both activity types are reported.

ORDER
Specifies the OMEGAMON® for DB2® PE identifiers and their sequence for sorting the report, and in summary reports, the identifiers are used for aggregation.

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

In the following example ORDER specifies that three Utility reports are to be produced. 
 
REPORT
   TYPE  (UTILITY)
   ORDER (PRIMAUTH-PLANNAME-REQLOC
          CONNECT-PLANNAME REQLOC-PRIMAUTH)
  • 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 primary authorization ID within requesting location.
DDNAME
Specifies the data set where the report is written.
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, ORDER, and EXCLUDE options

This example specifies the following:
  • A 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 1999 to noon on 19 March 1999
  • Data is excluded that is associated with the following locations:
    • LOCN10
    • LOCN12
    • LOCN15
    • LOCN20
 
UTILITY
   REPORT
      FROM    (03/18/02,10:00:00.00)
      TO      (03/19/02,12:00:00.00)
      ORDER   (CORRNAME-PRIMAUTH-PLANNAME)
      EXCLUDE (LOCATION(LOCN10 LOCN12 LOCN15 LOCN20))