4. Operation › 4.2 Operational Guidelines › 4.2.2 Production Operations › 4.2.2.1 Production Job Scheduler
4.2.2.1 Production Job Scheduler
Using a production job scheduler (a vendor package or timed
job submission) with CA MICS enables you to automatically
execute the Database update processing according to a pre-
established schedule. The advantage to using a production
job scheduler is that it adheres to your installation
standards and is familiar to your staff.
If you have activated incremental update for one or more
products in the unit database, you will probably use a
production job scheduler to schedule the SPLITSMF job (if
used) and the INCRccc job 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 (i.e., DAILY, WEEKLY,
MONTHLY, and BACKUP operational jobs), you can use a
production job scheduler to either schedule each operational
job individually, or you can use the CA MICS SCHEDULE job.
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 item
is defined to the production scheduler 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 If you use the CA MICS SCHEDULE job, then restart and
recovery processes within CA MICS would most likely be
controlled outside of the production scheduler.
o Some organizations restrict the use of the internal
reader or may have standards requiring that the
production scheduling facility control ALL production
processing. In this situation, you must implement the
SCHEDULE algorithm in the production scheduler
definitions.
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
your installation's production batch scheduling facilities.
USING THE CA MICS SCHEDULE JOB
Define the CA MICS SCHEDULE job to your production batch
scheduling system.
o Submit the SCHEDULE 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
SCHEDULE job should NOT be submitted until after
completing all INCRccc processing for the day.
o SCHEDULE will automatically submit DAILY, WEEKLY,
MONTHLY, YEARLY, and BACKUP processing as required.
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. (These RPT jobs
execute MICF inquiry production reporting and produce MBO and
exception reports for the products in the unit.)
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. Therefore, MICF inquiry
production processing will not execute. (The MBO and
exception reports are produced by the DAILY, WEEKLY, and
MONTHLY jobs, so those reports will be available.)
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 SCHEDULING
Define the CA MICS processing schedule to your production
batch scheduling system for each unit database. Primary
considerations/tasks 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 Schedule 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
SCHEDULE job should NOT be submitted until after
completing all INCRccc processing for the day.
o Schedule DAILYRPT after DAILY completes successfully.
o Schedule 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 Schedule WEEKRPT after WEEKLY completes successfully.
o Schedule 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 Schedule MONTHRPT after MONTHLY completes successfully.
o Schedule YEARLY after MONTHLY completes successfully at
the beginning of a new year.
o Schedule 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
define DAILY, WEEKLY, MONTHLY, YEARLY, and BACKUP to your
production scheduler.
o Schedule 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
SCHEDULE job should NOT be submitted until after
completing all INCRccc processing for the day.
o Schedule 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 Schedule 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 Schedule YEARLY after MONTHLY completes successfully at
the beginning of a new year.
o Schedule BACKUP processing as required. Backups should
occur after DAILY, WEEKLY, MONTHLY, and YEARLY processing
completes for the day.
