3. REPORTS › 3.3 Management Objective Reports › 3.3.4 Running the Management Objective Reports

3.3.4 Running the Management Objective Reports

Management Objective Reports are normally produced as a
standard part of the CA MICS daily, weekly, and monthly jobs.
This section describes the options available for controlling
the report selection and scheduling.

SELECTING THE REPORTS TO BE PRODUCED

The production of the Management Objective Reports is under
the control of the REPORT MBODAILY, REPORT MBOWEEKLY, and
REPORT MBOMONTHLY statements in member EXECDEF of
prefix.MICS.PARMS.

Each report option must be specified as NONE for no reports,
ALL for MBO reports from all installed products, or as a list
of one or more CA MICS product names for which the respective
Management Objective Reports should be produced.  For
instance:

    REPORT MBODAILY ALL
    REPORT MBOWEEKLY ALL
    REPORT MBOMONTHLY ALL

You specify these parameters by changing the EXECDEF member
of prefix.MICS.PARMS.  Changes made to EXECDEF take effect
With the next CA MICS job and do not require any generation
process.  See the PIOM, Section 2.3.5, Dynamic Execution
Options (EXECDEF), for information on modifying EXECDEF.

USING THE CA MICS UPDATE JOBS

The Daily Management Objective Reports are produced as a
standard process in the CA MICS daily job stream during the
DAY400 step.  Each of the four reports is produced from the
Batch User Job Activity Files (DETAIL.BATJOB01 and
DETAIL.BAT_JS01) maintained in the database's DETAIL
timespan.

The Weekly Management Objective Reports are produced as a
standard process in the CA MICS weekly job stream during the
WEEK400 step.  Each of the four reports is produced from the
Batch User Job Activity Files (DETAIL.BATJOBnn), maintained
in the database's DETAIL timespan.

The Monthly Management Objective Reports are produced as a
standard process in the CA MICS monthly job stream during the
MONTH400 step.  Each of the four reports is produced from
the Batch User Job Activity Files (MONTHS.BATJOBnn),
maintained in the database's MONTHS timespan.


USING SPIN-OFF REPORTING JOBS

The daily, weekly, and monthly reports can optionally be run
as spin-off jobs from the CA MICS DAILY, WEEKLY, and MONTHLY
operational jobs by using the AUTOSUBMIT parameter in JCLDEF.


USING SEPARATE REPORTING JOBS

Separate reporting jobs exist for producing the Daily,
Weekly, and Monthly Management Objective reports.  You can
run the DAILYRPT, WEEKRPT, and MONTHRPT jobs in stand-alone
fashion by submitting the appropriate member from
prefix.MICS.CNTL.  Producing the reports in this manner will
result in the same reports as produced by the standard
CA MICS operational jobs.

The Management Objective Reports assume that a set of
objectives related to the batch operation have been
determined by your installation.  However, this may not be
the case.  This section describes how you may specify the
management objectives to the reporting process once they have
been defined by management.  First, however, a discussion of
how the objectives may be established might prove useful.

Numbers that will be used as management objectives should not
be defined without some analysis of your installation's
historical batch performance and an input of user
requirements.

The CA MICS database provides a most useful information base
for analyzing historical performance.  We suggest that you
use one or more of the following analysis steps to study
study past performance.

STATISTICAL ANALYSIS

You may use the same data sources as mentioned above to
analyze in-depth the measures around which the management
objectives are to be determined.  Specifically, you may use
the SAS UNIVARIATE and FREQ procedures to provide a
reasonable statistical analysis of an individual measure,
which gives you mean, standard deviation, and percentile
values.  We believe that the percentile values may be the
most applicable to the process of determining the management
objectives target values.


DATABASE FILES FOR ANALYZING BATCH ACTIVITY

The database files that you should use in analyzing the
batch activity for purposes of establishing the Batch Report
Options are listed according to the reports to which they
apply.

  Daily   - DETAIL.BATJOB01  DETAIL.BAT_JS01  DETAIL.BATPGM01
  Weekly  - DETAIL.BATJOB01-10 DETAIL.BAT_JS01
            DETAIL.BATPGM01-10 (last week only)
  Monthly - DETAIL.BATJOB01-12

The last, and certainly not the least important, essential
input in defining management objectives for batch rests with
the perspective of batch users as to what minimum level of
service and throughput they require.

The integration of this information with data processing
management's own priorities and requirements will establish
the base for defining the management objectives for batch.

The following sections describe how an installation specifies
the numerical values used in these reports.

    1 - Batch Management Objective Report Options
    2 - Report Options MACRO Example