4. Operation › 4.3 Operations Reference › 4.3.2 Implementing the Processing Schedule
4.3.2 Implementing the Processing Schedule
CA MICS provides two automated processes to implement the
processing schedule.
o Operational Status and Tracking's SCHEDULE command.
o The SCHEDULE job--see prefix.MICS.CNTL(SCHEDULE).
NOTE: If you enable incremental update for one or more
products in a unit database, you must schedule the
optional SPLITSMF job and associated INCRccc job
executions separately, either manually or with your
installations production batch job scheduling
facility. The CA MICS automated scheduling facilities
do not handle INCRccc job scheduling.
The following diagram summarizes Operational Status and
Tracking's SCHEDULE command.
+-----------------------------------------------------------+
| |
| CA MICS Job Control Library (prefix.MICS.CNTL) |
| |
| DAILY |
| BACKUP |
| WEEKLY |
| Checkpoint MONTHLY Today's Date |
| File YEARLY (From MVS) |
| | | | |
| | | | |
| V______________V_______________V |
| | |
| V |
| +----------+ +---------+ |
| User Enters | | | Online | |
| SCHEDULE ------>| SCHEDULE |------>| Control | |
| Command Daily | | | Tables | |
| +----------+ +---------+ |
| | |
| V |
| Today's Tailored |
| Job Stream |
| | |
| +------------------+------------------+ |
| | | | |
| V V V |
| Checkpoint Job Schedule |
| File Input Restart |
| Queue File |
| |
+-----------------------------------------------------------+
The following diagram summarizes the SCHEDULE job.
+-----------------------------------------------------------+
| |
| CA MICS Job Control Library (prefix.MICS.CNTL) |
| |
| DAILY |
| BACKUP |
| WEEKLY |
| Checkpoint MONTHLY Today's Date |
| File YEARLY (From MVS) |
| | | | |
| | | | |
| V______________V_______________V |
| | |
| V |
| +----------+ +--------+ |
| User | | | Run | |
| Submits------>| SCHEDULE |------>| Status | |
| SCHEDULE | | | Report | |
| Daily +----------+ +--------+ |
| | (only produced on |
| V SCHEDULE abnormal |
| Today's termination) |
| Tailored |
| Job Stream |
| | |
| +------------------+------------------+ |
| | | | |
| V V V |
| Checkpoint System Schedule |
| File Internal Restart |
| Reader File |
| | |
| | |
| | |
| V |
| Job Input Queue |
| |
+-----------------------------------------------------------+
Inputs to SCHEDULE are:
o The Checkpoint File - contains the dates on which each of
the operational jobs last completed
o The CA MICS job control library - contains the JCL for
each of the operational jobs
o Today's date - maintained and made available through the
operating system
Outputs from SCHEDULE are:
o A tailored job stream containing the jobs that need to be
run for the day's processing.
- The SCHEDULE command submits the generated job stream.
- The SCHEDULE job writes the job stream to the internal
reader (the internal reader will submit the job for
execution).
o The Checkpoint File - contains the flags indicating the
operational jobs scheduled for today.
o The Schedule Restart File - contains a copy of the job
stream that was submitted to the internal reader. You
will use this file to manually restart the system if
processing abends.
o Updated Operational Status and Tracking control tables
(SCHEDULE command) or the Run Status Report containing
job status information on each operational job (SCHEDULE
job).
PRODUCTION OPERATIONS
There are a number of ways to operate CA MICS in a production
mode. If use of a production scheduler, either proprietary
or internally developed, is widely accepted at your
installation, you should place the CA MICS operational jobs
under its control.
If a production scheduler is not available, you can use
either the Operational Status and Tracking facility or you
can operate CA MICS in a manual mode.
In either case, you have the choice of using the automated
facilities CA MICS provides to implement the processing
schedule (SCHEDULE command and SCHEDULE job) or manually
implementing the processing schedule. Remember that the
INCRccc jobs for incremental update processing are scheduled
separately and are not supported by the CA MICS automated
scheduling facilities.
Refer to the Operational Guidelines section for the steps you
will perform to implement the CA MICS processing schedule.
The remainder of this section discusses:
o Production Job Scheduler
o Operational Status and Tracking Facility
o Manual Operation
o Reporting
PRODUCTION JOB SCHEDULER
You can use a production job scheduler to either schedule
each operational job individually or schedule the CA MICS
SCHEDULE job. The approach you choose depends on your
installation's production processing standards and
procedures. Consult your installation's operations or
production control group to find out what they will require
to manage CA MICS production processing.
If you enabled incremental update for one or more products in
this unit database, then define the individual INCRccc jobs
to your installation's production job scheduler. Each
INCRccc job will execute one or more times each day to
process a subset of the total day's input data according to
your predefined schedule of data availability and system
workloads.
If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF),
you will need to define the CA MICS DAILY, WEEKLY, MONTHLY,
YEARLY, and BACKUP operational jobs to your production
scheduling system.
o Do not use the SCHEDULE job when you specify AUTOSUBMIT NO
because CA MICS will NOT automatically submit DAILYRPT,
WEEKRPT, and MONTHRPT to perform daily/weekly/monthly MICF
inquiry production processing. CA MICS depends on the
AUTOSUBMIT YES option to automatically schedule MICF
production processing.
o Likewise, do not use the SCHEDULE job when you specify the
ARCHIVE AUDIT, ARCHIVE HISTW, and/or ARCHIVE HISTM
prefix.MICS.PARMS(JCLDEF) parameters with the JOB option
but without the corresponding AUTOSUBMIT option. CA MICS
depends on the JOB AUTOSUBMIT option to automatically
schedule stand-alone archive tape processing.
o You will replicate the CA MICS processing schedule in your
production control system's definition syntax. Refer to
the Processing Schedule section for the scheduling
algorithm.
o You must also define DAILYRPT, WEEKRPT, and MONTHRPT to
your production scheduling system.
- Schedule DAILYRPT after DAILY completes successfully.
- Schedule WEEKRPT after WEEKLY completes successfully.
- Schedule MONTHRPT after MONTHLY completes successfully.
o You must also define AUDIT, HISTW, and/or HISTM to your
production scheduling system if the corresponding ARCHIVE
option is active (YES) and you specified the JOB option to
perform archive tape processing in a stand-alone batch
job.
- Schedule AUDIT after WEEKLY completes successfully.
- Schedule HISTW after WEEKLY completes successfully.
- Schedule HISTM after MONTHLY completes successfully.
If you specified AUTOSUBMIT YES in prefix.MICS.PARMS(JCLDEF),
and also specified the AUDIT ARCHIVE, HISTW, and/or HISTM
AUTOSUBMIT option if you specified the JOB option for active
archive tape processing, then choose one of the following
methods to define CA MICS DAILY, WEEKLY, MONTHLY, YEARLY, and
BACKUP job processing to the production job scheduling
system.
o Define the CA MICS SCHEDULE job to the system
- This option submits most CA MICS processing via the JES
internal reader.
- The production scheduler should submit the SCHEDULE job
each day as soon as practical after CA MICS input data
is available and, IF you enabled incremental update for
one or more products in the unit database, ALL
scheduled INCRccc jobs complete execution.
- SCHEDULE will automatically submit DAILY, WEEKLY,
MONTHLY, YEARLY, and BACKUP processing as required.
- The DAY400, WEEK400, and MONTH400 steps of the
respective DAILY, WEEKLY, and MONTHLY operational jobs
will submit the DAILYRPT, WEEKRPT, and MONTHRPT jobs
for daily/weekly/monthly reporting.
- The WEEKLY job will submit the AUDIT and HISTW jobs as
required for Archive Audit and Archive Weekly History
processing (if active with the JOB option).
- The MONTHLY job will submit the HISTM job as required
for Archive Monthly History processing (if active with
the JOB option).
o Define the DAILY, WEEKLY, MONTHLY, YEARLY, and BACKUP
jobs to the system.
- The DAY400, WEEK400, and MONTH400 steps of the
respective DAILY, WEEKLY, and MONTHLY operational jobs
will submit the DAILYRPT, WEEKRPT, and MONTHRPT jobs
through the JES internal reader.
- The WEEK300 step of the WEEKLY job will submit the
AUDIT and HISTW jobs through the JES internal reader as
required for Archive Audit and Archive Weekly History
processing (if active with the JOB option).
- The MONTH300 step of the MONTHLY job will submit the
HISTM job through the JES internal reader as required
for Archive Monthly History processing (if active with
the JOB option).
OPERATIONAL STATUS AND TRACKING
The Operational Status and Tracking facility is an online
tool for initiating and monitoring CA MICS Database
operational processing in the DAILY, WEEKLY, MONTHLY, YEARLY,
and BACKUP jobs. It is available to authorized users from
the CA MICS Administrator Facility (MAF) option of the
CA MICS Workstation Facility (MWF). See the online tutorials
and the Operational Status and Tracking section (4.3.4) of
this guide for detailed data entry instructions and command
descriptions.
NOTE: If you activated incremental update for one or more
products in the unit database, you will need to
schedule the optional SPLITSMF job and the associated
INCRccc jobs manually or using your installation's
production batch job scheduling facilities. The
online Operational Status and Tracking Facility does
NOT support SPLITSMF or INCRccc job submission.
You can use the SCHEDULE command to automatically submit
DAILY, WEEKLY, MONTHLY, or YEARLY processing according to the
CA MICS processing schedule.
Alternatively, you can use Operational Status and Tracking
DAILY, WEEKLY, MONTHLY, and YEARLY commands to "manually"
submit DAILY, WEEKLY, MONTHLY, and YEARLY processing.
Operational Status and Tracking will prompt you when WEEKLY,
MONTHLY, or YEARLY processing is due--Current Operation
will be DAILY, WEEKLY, MONTHLY, or YEARLY and status will be
DUE TODAY or OVERDUE.
Operational Status and Tracking considers scheduled
processing to be late (OVERDUE) if not completed by 8:00 AM
You can override the default Overdue time-of-day on the
Operational Status and Tracking panel. Scroll RIGHT MAX to
display the Overdue option and specify the appropriate
deadline for each unit database. Operational Status and
Tracking will report status as DUE TODAY until the specified
time-of-day.
Reporting considerations:
o 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.
o If you specified AUTOSUBMIT NO in
prefix.MICS.PARMS(JCLDEF), you should reconsider your
decision to use Operational Status and Tracking to
schedule production CA MICS processing because CA MICS
will NOT automatically submit DAILYRPT, WEEKRPT, and
MONTHRPT to perform daily/weekly/monthly MICF inquiry
production processing. You must manually submit, from
prefix.MICS.CNTL, the DAILYRPT, WEEKRPT, and MONTHRPT
jobs after DAILY/WEEKLY/MONTHLY processing completes.
Archive tape processing considerations:
o 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.)
o 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 Operational
Status and Tracking to schedule production CA MICS
processing because CA MICS will NOT automatically submit
AUDIT, HISTW, or HISTM.
MANUAL OPERATION
If you choose not to use a production batch scheduling
facility or the CA MICS Operational Status and Tracking
facility for production CA MICS processing, then you can
manually submit the CA MICS production jobs as required.
All CA MICS production jobs are submitted from the
prefix.MICS.CNTL data set.
If you enabled incremental update for one or more products in
the unit, you will manually submit the SPLITSMF job (if used)
and the associated INCRccc jobs as required. The optional
SPLITSMF job and each INCRccc job will execute one or more
times each day to process a subset of the total day's input
data according to your predefined schedule of data
availability and system workloads.
You can use the CA MICS SCHEDULE job or you can submit the
DAILY, WEEKLY, MONTHLY, and BACKUP operational jobs
individually. The approach you choose depends on your
installation's production processing standards and
procedures. Consult your installation's operations or
production control group to find out what they will require
to manage CA MICS production processing.
If you specified AUTOSUBMIT YES in prefix.MICS.PARMS(JCLDEF),
and also specified the AUDIT ARCHIVE, HISTW, and/or HISTM
AUTOSUBMIT option if you specified the JOB option for active
archive tape processing, then you can simply submit the
CA MICS SCHEDULE job each day as soon as practical after
CA MICS input data is available and, IF you enabled
incremental update for one or more products in the unit
database, ALL scheduled INCRccc jobs complete execution.
o This option submits CA MICS processing via the JES
internal reader.
o SCHEDULE will automatically submit DAILY, WEEKLY, MONTHLY,
YEARLY, and BACKUP processing as required.
o The DAY400, WEEK400, and MONTH400 steps of the respective
DAILY, WEEKLY, and MONTHLY operational jobs will submit
the DAILYRPT, WEEKRPT, and MONTHRPT jobs for
daily/weekly/monthly reporting.
o The WEEKLY job will submit the AUDIT and HISTW jobs as
required for Archive Audit and Archive Weekly History
processing (if active with the JOB option).
o The MONTHLY job will submit the HISTM job as required for
Archive Monthly History processing (if active with the JOB
option).
If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF),
you will need to submit each CA MICS operational job
individually.
o Do not use the SCHEDULE job when you specify AUTOSUBMIT NO
because CA MICS will NOT automatically submit DAILYRPT,
WEEKRPT, and MONTHRPT to perform daily/weekly/monthly MICF
inquiry production processing. CA MICS depends on the
AUTOSUBMIT YES option to automatically schedule MICF
production processing.
o Likewise, do not use the SCHEDULE job when you specify the
ARCHIVE AUDIT, ARCHIVE HISTW, and/or ARCHIVE HISTM
prefix.MICS.PARMS(JCLDEF) parameters with the JOB option
but without the corresponding AUTOSUBMIT option. CA MICS
depends on the JOB AUTOSUBMIT option to automatically
schedule stand-alone archive tape processing.
o You will manually replicate the CA MICS processing
schedule. Refer to the Processing Schedule section for
the scheduling algorithm.
o You must also submit DAILYRPT, WEEKRPT, and MONTHRPT for
MICF production reporting.
- Submit DAILYRPT after DAILY completes successfully.
- Submit WEEKRPT after WEEKLY completes successfully.
- Submit MONTHRPT after MONTHLY completes successfully.
o You must also define AUDIT, HISTW, and/or HISTM to your
production scheduling system if the corresponding ARCHIVE
option is active (YES) and you specified the JOB option to
perform archive tape processing in a stand-alone batch
job.
- Schedule AUDIT after WEEKLY completes successfully.
- Schedule HISTW after WEEKLY completes successfully.
- Schedule HISTM after MONTHLY completes successfully.
REPORTING
The DAILY, WEEKLY, and MONTHLY processes include two types of
standard CA MICS reporting:
o MICF inquiry production reporting
o Management objective (MBO) and exception reports
MICF inquiry production reporting occurs in the DAILYRPT,
WEEKRPT, and MONTHRPT jobs. If you specified AUTOSUBMIT YES
in prefix.MICS.PARMS(JCLDEF), then the DAILY, WEEKLY, and
MONTHLY jobs automatically submit the corresponding DAILYRPT,
WEEKRPT, and MONTHRPT jobs. The DAILYRPT, WEEKRPT, and
MONTHRPT jobs also generate management objective (MBO) and
exception reports.
If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF),
the MBO and exception reports are generated in the DAY400,
WEEK400, and MONTH400 steps of the DAILY, WEEKLY, and MONTHLY
jobs. If you also schedule the DAILYRPT, WEEKRPT, and
MONTHRPT jobs to execute MICF inquiry production reporting,
CA MICS will generate duplicate MBO and exception reports.
For example, daily MBO and exception reports will be
generated from both the DAILY job and the DAILYRPT job.
To solve the potential for duplicate MBO and exception
reports:
o If you are NOT using MICF inquiry production reporting AND
you specified AUTOSUBMIT NO in the JCLDEF member of
prefix.MICS.PARMS, then do NOT schedule the DAILYRPT,
WEEKRPT, and MONTHRPT jobs. DAILYRPT, WEEKRPT, and
MONTHRPT will simply duplicate the MBO and exception
reports generated by the DAILY, WEEKLY, and MONTHLY jobs.
o If you ARE using MICF inquiry production reporting AND you
specified AUTOSUBMIT NO in the JCLDEF member of
prefix.MICS.PARMS, then use the distributed MICF inquiries
for MBO and exception reports. That is, you should turn
off MBO and exception reporting in
prefix.MICS.PARMS(EXECDEF) and include the MBO and
exception report inquiries distributed with CA MICS in
your MICF production reporting definitions.
See section 2.3.5 of this guide for details on EXECDEF
parameters. See the Standard Reports Guide for more
information on MBO and exception reports. See MICF
Administration in the MICF Reference Guide for more
information on inquiry production reporting.
ARCHIVE TAPE PROCESSING
The CA MICS Archive Database facility provides optional
long-term retention for both detail level (audit) data and
summarized (history) data. Archive Audit processing normally
occurs weekly and provides long-term retention of DETAIL
and/or DAYS level data to meet audit and/or detail analysis
requirements. Archive History processing optionally occurs
weekly and/or monthly and provides long-term retention of
WEEKS and/or MONTHS level (summarized) data to address
long-term reporting, capacity planning, and historical
analysis requirements.
Archive tape processing can occur within the WEEKLY and/or
MONTHLY operational jobs, or you can optionally offload this
processing to the stand-alone AUDIT, HISTW, and HISTM jobs
which access the database DISP=SHR, thereby freeing the
database for concurrent execution of reporting jobs and/or
online end-user inquiry and analysis, or any other
"read-only" processing. See Section 2.3.3.2.1.3 for more
information on parameters controlling archive tape
processing.
