3. REPORTS › 3.3 Running Reports in Batch › 3.3.2 JCL Requirements

3.3.2 JCL Requirements

For selected CICS Analyzer inquiries, which were first
shipped as batch summary reports, you can execute them using
your own JCL external to MICF.  The inquiries that can be
executed in this manner include:

    o CICLD4 - Daily Activity Overview Report
    o CICLD5 - Application Limit Summary Report
    o CICLD6 - Daily User Activity Summary Report
    o CICLD7 - FILE/DBD Activity Summary Report
    o CICLD8 - DB2 Call Summary Report

To code your own JCL, simply create a member in a PDS that
contains the following:

    //jobname JOB ...
    //S1      EXEC MICSSHRi
    //MICS.SYSIN DD DSN=sharedprefix.MICS.SOURCE(CICRPTnn),
    //        DISP=SHR

The MICSSHRi procedure is used to execute the CICS summary
reports, where i is the single-character identifier for the
CA MICS unit data base that contains the CIC Information Area
files.  A SYSIN DD statement is required to select the
requested CICS report program source member, which are named
CICRPTnn, where nn is 01 through 05.

The reports and their corresponding program source members
are:

    o CICRPT01 - Daily Activity Overview Report
    o CICRPT02 - Application Limit Summary Report
    o CICRPT03 - Daily User Activity Summary Report
    o CICRPT04 - FILE/DBD Activity Summary Report
    o CICRPT05 - DB2 Call Summary Report - CICRPT05

Once you have coded the JCL, you can submit it upon
completion of the CA MICS DAILY job to produce the reports.
However, since the reports are available through MICF, the
alternative and the recommended method to generate them in
batch is through MICF production interface, which
automatically creates the reports after the CA MICS DAILY,
WEEKLY, or MONTHLY job has completed.  See Section 3.3.1 for
more information on MICF production interface.