Skip to Content

Use and interpretation of reports

You can use the information in the BMC AMI Ops Monitor for CMF reports to define thresholds for key system resources.

The reports summarize performance data by job class or service class periods; they also report on DASD head movement activity, CPU usage, link pack area activity, and TSO usage data.

Some reports are produced automatically, such as the System Resources Manager (SRM) Constants Report. Automatically produced reports are found in the Collection Phase Log of the Analyzer output.

Related topic

Preliminary-reporting-information

Understanding-Analyzer-reports

Determination of which reports you need

The reports that Analyzer statements produce fall into different categories. Some reports belong to more than one category.

The following topics show the categories of reports and the Analyzer control statements that produce reports belonging to each category.

WORKLOAD reports

The following reports are included:

Name

Type

OMVS

TSOUSER

TSOPERF

WLMGL

CPU reports

The following reports are included:

Name

Type

CPU

PROTKEY

CPUCON


SYSTEM RESOURCE reports

The following reports are included:

Name

Type

AUXSTOR

SRM

COMMSTOR

STORAGE

ENQUEUE

TRACE

LINKPACK

VIRTSTOR

PCIE

XCF

SERDELAY


DEVICE reports

The following reports are included:

Name

Type

AUXSTOR

ESS

CACHEACT

FICONSW

DEVACT

IOQ

DASD

SHARDEV

Web-related reports

The following reports are included:

Name

Type

DOMINO

HTTP

Miscellaneous reports

The following reports are included:

Name

Type

CMFSTAT

HFS

CMFSUM

TABULAR

DATASET

TRACE

EXCEPTS

WLMGRAPH

GRAPH


To see an example of each report, field descriptions, and calculations, see Analyzer-reports.

Interpretation of report field information

Data field results can vary due to environmental factors such as the version of MVS running in your environment or the configuration of your system resources.

In some cases, report fields contain data presented using one of the following conventions:

  • dashes (---)
    If a report requires input from more than one Extractor record and one of them is not present, dashes (---) appear in the fields that need data from the missing record.

  • scientific notation
    If a number is too large to be displayed in the space provided in a report field, the number is displayed in scientific notation. Scientific notation is provided only for nine-character or longer field values. The format for numeric values displayed in scientific notation is
    sn.n{.nnn}Eyxx

    Variable

    Description

    s

    is the sign, either + or –

    n.nnn

    is a real number greater than zero (0) and less than ten (10)

    y

    is the sign of the exponent, either + or –

    xx

    is the exponent

    The precision of the real number varies depending on the size of the field; for example, the number 9.37E+07 is

    9.37x10 7 = 93,700,000

  • E’s (EEEEE...)
    If a value is too large to be displayed, even in scientific notation, it is represented as a string of Es.

Report headings

A report heading is printed automatically at the top of each report page. Each heading includes the product name and version number, a report title, page number, current report date and time, user-defined title and subtitle, and report sequence number.

All requested reports receive the following heading:

PRODUCED BY CMF ANALYZER (v.r.mm  RSL yymm )                     WORKLOAD MANAGER MAP REPORT                      RPTSEQ     7 PAGE    181
BMC SOFTWARE, INC.                                            XYZ COMPANY                              REPORT DATE: DD MMM YY 13.26
ACTL 10 JUN YY 17.00.00  11 JUN YY 17.00.00             WORLDWIDE HEADQUARTERS                         SYSTEM ID: **ALL**  COMB-MVS

 BASED ON REC TYPE/# RECS/# SAMPLES/REC HOURS:  72-3/7,896/0/46.64

Descriptions of report headings fields

The following table describes the fields in a report heading:

Field name

Description

PRODUCED BY

name and version number of the product

REQD

requested beginning and ending date-time range

SHFT

day and time based on SHIFT control statement

ACTL

actual beginning and ending date-time range encountered

  • The first date-time pair under ACTL is the date and time of the first record encountered in the input data set that contained information for the report (see the figure in Report headings).
  • The second or end date-time pair is the date and time of the last record encountered in the input data set that contained information for that report; the end date-time also includes the interval time for the last record.
  • For the Extractor Characteristics Subreport of the Collection Phase Log, the date-time of the first record is in effect from begin date-time and the end date-time is thedate-time of the last record encountered; however, the end date-time does not include the interval time for the last record.
  • When using these date-times for DATETIME or CYCLE selection, selection criteria are based on the record start date-time.

BASED ON

Records used for this report, in the format REC TYPE/# RECS/# SAMPLES/REC HOURS, where

REC TYPE = record type and subtype

# RECS = number of records

# SAMPLES = number of samples

REC HOURS = duration of recording period (to nearest hundredth of an hour)

(report title)

title of report, followed by user-generated data from title and location fields, as specified on the optional HEADERS control statement

RPTSEQ

sequence number of the report and page number

REPORT DATE

date and time control statements were processed

SYSTEM ID

system identifier

  • If the report contains data from a single MVS image, the sysname or the sysid appears in the SYSTEM ID field of the report heading.
  • If the report contains data from multiple MVS images, *MULTI* or **ALL** is printed in the SYSTEM ID field of each report heading.

(MVS system release number)

appears to the right of the SYSTEM ID field

  • If the report contains data from a single MVS release, the release number appears in this area.
  • If the report contains data from multiple MVS releases, COMB-MVS appears in this area.

REPORT CYCLE

report cycle based on CYCLE control statement

 

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

BMC AMI Ops Monitor for CMF 6.3