Executing Production Reporting Job Streams and User Reporting Job Streams

This section describes how to execute a User reporting job stream and a Production reporting job stream.
micsrm140cd
This section describes how to execute a User reporting job stream and a Production reporting job stream.
Use the G (Generate) line command for on-demand production and job 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
MICS
production jobs (see MICF Inquiry Production Interface).
MICF user and production reporting job stream execution JCL is simple. The most basic form (use the G line command for a sample) consists of the following statements:
  • Job statement
  • Execute statement for the MICSRPTS cataloged procedure
  • DD statement to allocate the catalog table data set associated with the production or the user job stream.
  • (user reporting job stream only) DD statement to allocate your User ISPF Tables data set, which is where your private catalogs reside.
Printed report and color graphics catalog data sets are dynamically allocated.
Example of a production reporting job stream
//jobname JOB (........ //MICF    EXEC MICSRPTS //SYSTSIN DD DISP=SHR, // DSN=sharedprefix.MICS.SOURCE(ICFJ100) //ICFRPT1 DD DISP=SHR, // DSN=sharedprefix.DAILY.MICS.CATALOG
Example of a user reporting job stream
//jobname JOB (........ //MICF    EXEC MICSRPTS //SYSTSIN  DD DISP=SHR, // DSN=sharedprefix.MICS.SOURCE(ICFU100) //ICFRPT1  DD DISP=SHR, // DSN=userid.RMFUJOB.CATALOG //MWFUTABL DD DISP=SHR, // DSN=userid.MICS.USER.TABLES 
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 scans 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/user 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 records the return code from each MICF inquiry execution, and any internal processing errors, and posts 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 here:
//jobname JOB (........ //MICF    EXEC MICSRPTS,MAXRC='N'