5. MICF Administration › 5.1 Tasks Performed During Installation › 5.1.6 Production Reporting › 5.1.6.3 Executing a Production Reporting Job Stream

5.1.6.3 Executing a Production Reporting Job Stream

You can use the G (Generate) line command for on-demand
production reporting execution, or to generate execution JCL
that you can save for later submission by your data center's
production batch scheduling facilities.  You can also tie
MICF production reporting directly to CA MICS production jobs
(see MICF Inquiry Production Interface).

MICF production reporting job stream execution JCL is quite
simple.  The most basic form (use the G line command for a
sample) consists of a job statement, an execute statement for
the MICSRPTS cataloged procedure, and a DD statement to
allocate the catalog table data set associated with the
production job stream.  Printed report and color graphics
catalog data sets are dynamically allocated.

     //jobname JOB (........
     //MICF    EXEC MICSRPTS
     //SYSTSIN DD DISP=SHR,
     // DSN=sharedprefix.MICS.SOURCE(ICFJ100)
     //ICFRPT1 DD DISP=SHR,
     // DSN=sharedprefix.DAILY.MICS.CATALOG

You can execute multiple production reporting job streams
with a single batch job by including multiple catalog table
allocations in the execution JCL.  For example, the following
batch job generates three sets of independently securable
daily reports and graphics:

     //jobname JOB (........
     //MICF    EXEC MICSRPTS
     //SYSTSIN DD DISP=SHR,
     // DSN=sharedprefix.MICS.SOURCE(ICFJ100)
     //ICFRPT1 DD DISP=SHR,
     // DSN=sharedprefix.DAILY.MICS.CATALOG
     //ICFRPT2 DD DISP=SHR,
     // DSN=acctprefix.ACTDAILY.MICS.CATALOG
     //ICFRPT3 DD DISP=SHR,
     // DSN=techprefix.DAILY.TECH.SUPPORT.MICS.CATALOG

Remember that the batch job must have UPDATE authority for
all data sets associated with the production reporting job
streams.  MICF will scan the execution JCL and process any
production reporting catalog table data set allocated to an
ICFRPTnn DD, where nn is 1-99 (to make the DDNAMEs unique).


Note:  MICF inquiry production reporting is a batch terminal
monitor program (TMP).  That is, to run MICF inquiry
production reports, you execute TSO and ISPF in batch mode.
This makes the process sensitive to maintenance levels of TSO
and ISPF.  You can encounter problems if your TSO or ISPF
product maintenance is out-of-date.

By default, this job will record the return code from each
MICF inquiry execution, as well as any internal processing
errors, and post the highest return code as the completion
code for the batch job step.  If you prefer to have the job
end with a U0998 termination code when any errors are
encountered, you can override the MAXRC symbolic parameter on
the EXEC statement as shown below:

     //jobname JOB (........
     //MICF    EXEC MICSRPTS,MAXRC='N'