4. Operation › 4.2 Operational Guidelines › 4.2.2 Production Operations › 4.2.2.2 Operational Status and Tracking Facility
4.2.2.2 Operational Status and Tracking Facility
Operational Status and Tracking is an online tool for
initiating and monitoring CA MICS database operational
processing. This online tool is available to authorized
users from the CA MICS Administrator Facility (MAF) option of
the CA MICS Workstation Facility (MWF).
If you have activated incremental update for one or more
products in the unit database, you will probably use a
production job scheduler or 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 data center. Operational Status and Tracking does
not provide facilities for scheduling either the SPLITSMF job
or the INCRccc jobs, however they can still be manually
submitted and tracked using Operational Status and Tracking.
For the CA MICS end-of-day processing, 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 to "manually" submit DAILY, WEEKLY,
MONTHLY, or YEARLY processing, and it will prompt you when
the WEEKLY, MONTHLY, or YEARLY processing is due.
The remainder of this section provides more information about
implementing CA MICS end-of-day production operation with
Operational Status and Tracking. See the reference section
and the online tutorials for detailed documentation on
Operational Status and Tracking facilities, panel data entry
instructions, and commands.
USING THE SCHEDULE COMMAND
Specify the correct overdue time-of-day for each CA MICS unit
database on the Operational Status and Tracking display.
Authorize production control personnel to access CA MICS
Operational Status and Tracking.
Authorize production control personnel to update the
prefix.MICS.RESTART.CNTL data set.
Train production control personnel to use Operational Status
and Tracking to control and monitor production CA MICS
processing. The information in section 4.2.1 is a good
starting point for training people to use the facility.
Each Day:
o Enter the SCHEDULE command for each CA MICS unit database
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, do NOT enter the SCHEDULE
command until after completing all INCRccc processing for
the day.
o Use the Operational Status and Tracking display to
monitor CA MICS production processing. Initiate problem
determination, correction, and restart if necessary.
If you specified AUTOSUBMIT YES in prefix.MICS.PARMS(JCLDEF),
CA MICS automatically submits the DAILYRPT, WEEKRPT, and
MONTHRPT jobs using the JES internal reader.
If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF),
reconsider your decision to use Operational Status and
Tracking to schedule production CA MICS processing because CA
MICS does NOT automatically submit DAILYRPT, WEEKRPT, and
MONTHRPT to perform daily/weekly/monthly MICF inquiry
production processing. You must manually submit the
DAILYRPT, WEEKRPT, and MONTHRPT jobs from prefix.MICS.CNTL.
o Submit DAILYRPT after the Operational Status and Tracking
display shows DAILY processing is completed.
o Submit DAILYRPT and WEEKRPT after the Operational Status
and Tracking display shows WEEKLY processing is completed.
o Submit DAILYRPT and MONTHRPT after the Operational Status
and Tracking display shows MONTHLY processing is
completed.
o Submit DAILYRPT after the Operational Status and Tracking
display shows YEARLY processing is completed.
MANUAL SCHEDULING
Specify the correct overdue time-of-day for each CA MICS unit
database on the Operational Status and Tracking display.
Authorize production control personnel to access CA MICS
Operational Status and Tracking.
Authorize production control personnel to update the
prefix.MICS.RESTART.CNTL data set.
Train production control personnel to use Operational Status
and Tracking to control and monitor production CA MICS
processing. The information in section 4.2.1 is a good
starting point for training people to use the facility.
Each Day:
o Enter the DAILY, WEEKLY, MONTHLY, or YEARLY command as
noted in the Current Operation column for each CA MICS
unit database 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 do NOT enter the
DAILY, WEEKLY, MONTHLY, or YEARLY command until after
completing all INCRccc processing for the day.
- The current operation should have a status of DUE TODAY
or OVERDUE.
- The WEEKLY, MONTHLY, and YEARLY commands execute the
DAILY job in addition to the WEEKLY, MONTHLY, or YEARLY
job.
- The DAILY, WEEKLY, and MONTHLY commands include BACKUP
processing. If you want to defer BACKUP processing,
enter the NOBACKUP operand on the command line (that
is, DAILY p NOBACKUP where p is the unit database ID).
- If WEEKLY, MONTHLY, or YEARLY processing is due but you
wish to defer this processing to the next day, enter
the DAILY command. Tomorrow, Operational Status and
Tracking will once again request WEEKLY, MONTHLY, or
YEARLY processing.
o Use the Operational Status and Tracking display to
monitor CA MICS production processing. Initiate problem
determination, correction, and restart if necessary.
If you specified AUTOSUBMIT YES in prefix.MICS.PARMS(JCLDEF),
CA MICS automatically submits the DAILYRPT, WEEKRPT, and
MONTHRPT jobs using the JES internal reader.
If you specified AUTOSUBMIT NO in prefix.MICS.PARMS(JCLDEF),
reconsider your decision to use Operational Status and
Tracking for production CA MICS processing because CA MICS
does 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.
o Submit DAILYRPT after the Operational Status and Tracking
display shows DAILY processing is completed.
o Submit DAILYRPT and WEEKRPT after the Operational Status
and Tracking display shows WEEKLY processing is completed.
o Submit DAILYRPT and MONTHRPT after the Operational Status
and Tracking display shows MONTHLY processing is
completed.
o Submit DAILYRPT after the Operational Status and Tracking
display shows YEARLY processing is completed.
If you specified the YES, JOB, and AUTOSUBMIT options for any
of the ARCHIVE AUDIT, HISTW or HISTM parameters in
prefix.MICS.PARMS(JCLDEF), CA MICS automatically submits the
corresponding AUDIT, HISTW, or HISTM job using the JES
internal reader. (This job offloads archive tape processing
from the WEEKLY or MONTHLY operational job to increase
database availability. This processing can alternatively be
executed within the WEEKLY or MONTHLY operational jobs.)
If you specified the YES and JOB options for any of the
ARCHIVE AUDIT, HISTW or HISTM parameters in
prefix.MICS.PARMS(JCLDEF) BUT did NOT include the AUTOSUBMIT
option on the parameter statement, reconsider your decision
to use the CA MICS SCHEDULE job because CA MICS will NOT
automatically submit AUDIT, HISTW, or HISTM to perform weekly
and monthly archive tape processing. You must manually
submit the AUDIT, HISTW or HISTM job (often called
stand-alone job).
o Submit AUDIT, HISTW, or both (if activated) after the
Operational Status and Tracking display shows WEEKLY
processing has completed.
o Submit HISTM (if activated) after the Operational Status
and Tracking display shows that MONTHLY processing has
completed.
Note: If you submit a stand-alone audit archive job that is
not required because a recent audit archive job has already
archived the targeted database files, the job's MICSLOG
contains messages warning you of this situation. However,
the job proceeds to create a new audit tape that is
essentially a duplicate of the one previously created. The
JOBLOG display of Operational Status and Tracking indicates
that the job has completed, but it does not alert you to the
situation that you have run an unnecessary audit archive job.
If you submit a stand-alone HISTW/M archive job that is not
required because a WEEKLY or MONTHLY history tape has already
been created for the most recently completed week or month,
the job's MICSLOG contains messages warning you about this
situation, and the job aborts with ABEND code U0998. There
is no facility in place to alert Operational Status and
Tracking that an attempt was made to create a duplicate
history tape, so in this case, the JOBLOG entry indicates a
successful execution even though the job actually aborted.
MONITORING CA MICS PRODUCTION PROCESSING
The primary Operational Status and Tracking display lists the
current status for each unit database. Overdue processing
and database update failures are noted.
o The STATUS command provides more details relating to unit
database status and error conditions.
o The HISTORY command displays the database update audit
trail (ADMIHL file).
o The CHECKPT command displays the checkpoint database
update time range records.
o The JOBLOG command displays a processing audit log.
o You can override the default overdue time-of-day (8:00
a.m.) for each CA MICS unit database on the Operational
Status and Tracking display by scrolling RIGHT MAX and
changing the 8 a.m. default deadline.
Copyright © 2014 CA.
All rights reserved.
|
|