4. Operation › 4.2 Operational Guidelines › 4.2.2 Production Operations › 4.2.2.3 Manual Operation

4.2.2.3 Manual Operation

If you choose not to use a production batch scheduling
facility or the CA MICS Operational Status and Tracking
application for production CA MICS processing, then you can
manually submit the CA MICS production jobs as required for
each unit database.  All CA MICS production jobs mentioned
in this section are submitted from the prefix.MICS.CNTL data
set.

If you have activated incremental update for one or more
products in the unit database, you will probably use a manual
procedure to schedule the optional SPLITSMF job and the
INCRccc jobs (one for each product using incremental update).
SPLITSMF and INCRccc job scheduling is dependent upon the
availability of the input data and on day-time batch
processing considerations unique to your installation.

For the CA MICS end-of-day processing, you can use the
CA MICS SCHEDULE job or you can submit each operational job
individually.  The approach you choose depends on your
installation's production processing standards and
procedures.

o  If you use the CA MICS SCHEDULE job, then only one job is
   submitted each day for the CA MICS end-of-day processing.
   The SCHEDULE job determines what needs to be done, builds
   a job stream to do it, and submits the job stream to the
   internal reader.

o  Some organizations restrict the use of the internal
   reader or may have standards requiring that the
   production control group submit each production job.  In
   this situation, you must implement the SCHEDULE algorithm
   manually.

In either case, you can still monitor CA MICS processing with
the Operational Status and Tracking facility.

Consult your installation's operations or production control
group to find out what they will require to manage CA MICS
production processing.

The remainder of this section provides more information on
implementing CA MICS end-of-day production operation with
manual job submission.


USING THE CA MICS SCHEDULE JOB

Submit the SCHEDULE job each day for each unit database as
soon as practical after CA MICS input data is available.
SCHEDULE will automatically submit a single batch job stream
for DAILY, WEEKLY, MONTHLY, YEARLY, and BACKUP processing as
required.

NOTE:  If you activated Incremental Update for one or more
       products in this unit database, then the SCHEDULE job
       should NOT be submitted until after completing all
       INCRccc processing for the day.

If you specified AUTOSUBMIT YES in prefix.MICS.PARMS(JCLDEF),
CA MICS will automatically submit the DAILYRPT, WEEKRPT, and
MONTHRPT jobs using the JES internal reader.

If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF),
you should reconsider your decision to use the CA MICS
SCHEDULE job because CA MICS will NOT automatically submit
DAILYRPT, WEEKRPT, and MONTHRPT to perform
daily/weekly/monthly MICF inquiry production processing.

If you specified the YES, JOB, and AUTOSUBMIT options for the
ARCHIVE AUDIT, HISTW, and/or HISTM parameters in
prefix.MICS.PARMS(JCLDEF), CA MICS will automatically submit
the AUDIT, HISTW, and/or HISTM jobs using the JES internal
reader.  (These jobs offload archive tape processing from the
WEEKLY and/or MONTHLY operational jobs to increase database
availability.  This processing can alternatively be executed
within the WEEKLY and/or MONTHLY operational jobs.)

If you specified the YES and JOB options for the ARCHIVE
AUDIT, HISTW, and/or HISTM parameters in
prefix.MICS.PARMS(JCLDEF) BUT did NOT include the AUTOSUBMIT
option on these parameter statements, you should reconsider
your decision to use the CA MICS SCHEDULE job because CA MICS
will NOT automatically submit AUDIT, HISTW, or HISTM.


DETAIL CA MICS JOB SUBMISSION

Primary considerations/tasks for implementing the CA MICS
scheduling algorithms manually are noted below.  The
CA MICS processing schedule is documented in the Reference
section.

If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF):

o  Submit the DAILY job each day as soon as practical after
   CA MICS input data is available.

   NOTE:  If you activated Incremental Update for one or
          more products in this unit database, then the
          DAILY job should NOT be submitted until after
          completing all INCRccc processing for the day.

o  Submit DAILYRPT after DAILY completes successfully.

o  Submit WEEKLY after DAILY completes successfully at the
   beginning of a new week.

o  If you specified

        ARCHIVE AUDIT YES JOB

   in prefix.MICS.PARMS(JCLDEF) without including the
   AUTOSUBMIT option, then schedule AUDIT after WEEKLY
   completes successfully.

   If you included the AUTOSUBMIT option, the WEEK300 step
   automatically submits AUDIT using the JES internal reader.

   If you did not specify the JOB option, then Archive Audit
   processing is performed in the WEEK300 step within the
   WEEKLY operational job.

o  If you specified

        ARCHIVE HISTW YES JOB

   in prefix.MICS.PARMS(JCLDEF) without including the
   AUTOSUBMIT option, then schedule HISTW after WEEKLY
   completes successfully.

   If you included the AUTOSUBMIT option, the WEEK300 step
   automatically submits HISTW using the JES internal reader.

   If you did not specify the JOB option, then Archive Weekly
   History processing is performed in the WEEK300 step within
   the WEEKLY operational job.

o  Submit WEEKRPT after WEEKLY completes successfully.

o  Submit MONTHLY after DAILY completes successfully at the
   beginning of a new month.

o  If you specified

        ARCHIVE HISTM YES JOB

   in prefix.MICS.PARMS(JCLDEF) without including the
   AUTOSUBMIT option, then schedule HISTM after MONTHLY
   completes successfully.

   If you included the AUTOSUBMIT option, the MONTH300 step
   automatically submits HISTM using the JES internal reader.

   If you did not specify the JOB option, then Archive
   Monthly History processing is performed in the MONTH300
   step within the MONTHLY operational job.

o  Submit MONTHRPT after MONTHLY completes successfully.

o  Submit YEARLY after MONTHLY completes successfully at the
   beginning of a new year.

o  Submit BACKUP processing as required.  Backups should
   occur after DAILY, WEEKLY, MONTHLY, and YEARLY processing
   completes for the day.

If you specified AUTOSUBMIT YES in prefix.MICS.PARMS(JCLDEF),
CA MICS will automatically submit the DAILYRPT, WEEKRPT, and
MONTHRPT jobs using the JES internal reader.  You must still
submit the DAILY, WEEKLY, MONTHLY, YEARLY, and BACKUP jobs as
required.

o  Submit the DAILY job each day as soon as practical after
   CA MICS input data is available.

o  Submit WEEKLY after DAILY completes successfully at the
   beginning of a new week.

   NOTE:  Archive Audit and Archive Weekly History processing
          considerations (the AUDIT and HISTW jobs) are the
          same as described above (under AUTOSUBMIT NO).

o  Submit MONTHLY after DAILY completes successfully at the
   beginning of a new month.

   NOTE:  Archive Monthly History processing considerations
          (the HISTM job) is the same as described above
          (under AUTOSUBMIT NO).

o  Submit YEARLY after MONTHLY completes successfully at the
   beginning of a new year.

o  Submit BACKUP processing as required.  Backups should
   occur after DAILY, WEEKLY, MONTHLY, and YEARLY processing
   completes for the day.