Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Db2 13.1 image-2024-5-19_8-5-1.png .

DOMBRPT1 utility


The DOMBRPT1 utility is the Data Collector utility that produces printed reports from a batch job.

DOMBRPT1 uses external data sets or active data sets as input. An external sort utility named SORT is required. If no program is named SORT in the z/OS LINKLIST, you might need to add a DD statement to your STEPLIB that identifies the load library that contains the sort utility. When processing large amounts of data, your sort utility might need additional SORTWKnn DD statements (consult your sort utility documentation for details).

Member #DOMRPRT in the BBSAMP data set contains sample JCL to run the Data Collector report utility. #DOMRPRT is provided with the BMC AMI Ops Monitor for Db2 Data Collector.

The following table describes the data sets that are processed by DOMBRPT1 .

DDNAME

Description

DCB Attributes

DB2LOAD

Db2 load format data will be written to this data set, which can be passed to the #DOMLOAD utility in another step to load the data.

  • RECFM=VB
  • LRECL = 32752
  • BLKSIZE = 32756

R0001VFG (optional)

Data set used to hold group records for each report if there are too many records to fit in the internal buffers

This value can be adjusted according to the number of selected records, and the degree to which the data is reduced. For example, a report containing accounting information grouped by hour requires fewer group records than a report containing the same information grouped by thread. If not specified, the file is dynamically allocated by using the space allocation that is specified in your User Profile and the unit that is specified in your installation options.

Default values are generally sufficient, but can be customized in the Data Collector administration panels. To size the data set:

  • Multiply 32 KB (maximum size of each record) with the number of records to come up with a total size of the input records.
  • Adjust this figure to the track size and approximate sizes of the initial allocation.

Not applicable

R0001VFL (optional)

Data set used to hold selected records for each report if there are too many records to fit in the internal buffers

This value can be adjusted according to the number of selected records. If not specified, the file is dynamically allocated by using the space allocation that is specified in your User Profile and the unit that is specified in your installation options.

Default values are generally sufficient, but can be customized in the Data Collector administration panels. To size the data set:

  • Multiply 32 KB (maximum size of each record) with the number of records to come up with a total size of the input records.
  • Adjust this figure to the track size and approximate sizes of the initial allocation.

Not applicable

REPORT

DOMBRPT1 report output and record trace output, if requested

  • RECFM = FBA
  • LRECL = 133
  • BLKSIZE = any multiple of LRECL

SORTWKnn (optional)

Interim data sets for the Sort utility working storage

This data set might be required by a sort program if large amounts of trace data are being processed. Refer to your site’s sort program documentation for details about the specification of this DD statement.

Not applicable

SRCTRACE (optional)

Data set containing a listing of all records found in the TRACEIN file

A single line is generated for each valid record, including an indication of whether the record is used by a report.

  • RECFM = FBA
  • LRECL = 121
  • BLKSIZE = any multiple of LRECL

STEPLIB

Data Collector load library

Not applicable

SYSIN

DOMBRPT1 control statements

Not applicable

SYSOUT

SORT messages

Not applicable

SYSPRINT

DOMBRPT1 messages and statistics

  • RECFM = FBA
  • LRECL = 121
  • BLKSIZE = any multiple of LRECL

TRACEIN

Trace input data sets

The input data sets can be any of the following data sets: NGL archive output, SMF (compressed or not), SMF Logstream dataset, GTF, or EXPORT data sets.

Not applicable

TRACEWRK

Interim data set for holding the records that were selected and sorted for reporting

The amount of required space increases as the amount of selected data increases. Data is selected if any report requires the record, based on IFCID type, date and time, and qualifiers.

  • RECFM = VBS
  • LRECL = 32760
  • BLKSIZE = 8192

 Report generation requires that input data is sorted by Db2 subsystem ID (QHSSSID) and internal timestamp (QWHSSTCK). These fields are found in the standard header section of Db2 records.

The batch report program expects to read input data from DD TRACEIN, sort it appropriately, and stage it to DD TRACEWRK for subsequent input to each requested report.

When the data source is a data set and you expect to run multiple report jobs against the same data, you can avoid repeating the pre-sort process by making the TRACEWRK DD a permanent file and using it as the TRACEIN DD on subsequent runs. Where the TRACEIN file is pre-sorted, omit the TRACEWRK DD or code it as DD DUMMY.

When the data source is the active Data Collector, the TRACEWRK file is not used (that is, there is no I/O operation to the TRACEWRK file). When the data source is the active Data Collector, you must specify the Data Collector as the data source for each of the reports.

If you try to process data that is not in the proper order, and no TRACEWRK file is specified, message BMC24636 is issued ( Normalization processing error, input data not in sequence), and report output is not produced.

Note

A Data Collector report execution with TRACEWRK missing or dummied will not produce output on the SRCTRACE DD, because the SRCTRACE output is produced during the processing that is eliminated. If you want SRCTRACE output, produce it on the initial run when the TRACEWRK DD is specified and pointing to an actual data set.

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*