3. Installation › 3.7 Production System Implementation › 3.7.1 System Activation

3.7.1 System Activation

This section recommends a series of actions to ensure a full
system check-out and successful pre-production activation.

    1.  List the JCL streams in the job control library
(MICS.CNTL) named DAILY, WEEKLY, MONTHLY, and YEARLY.  Read
the Operations chapter thoroughly and review the JCL streams
just listed to gain a good understanding of the operational
processes.  Verify in this review that the streams are in
full accordance with installation standards.

    2.  Verify that the Checkpoint File is correctly
initialized for system activation.  Use the Operational
Status and Tracking STATUS command to display Checkpoint File
status line information.  Last Completed Step should be 900
for all CA MICS jobs (DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP,
and RESTORE).  Last Completed Date should be the date
CKPTINIT was executed, the first date of the current week,
the first date of the current month, and the first date of
the current year respectively for the DAILY, WEEKLY, MONTHLY,
and YEARLY jobs.

    3.  List the catalog for the prefix(es) to which all of
the CA MICS data sets were appended.  Ensure that all of the
data sets that are referenced in the JCL procedures listed in
step 1 are allocated and cataloged.

    4.  Determine how the installation's normal SMF dumping
and accumulation process can be used to provide the files
necessary for the DAILY process.

    5.  Use the Operational Status and Tracking DAILY command
to execute the DAILY process for the next three evenings and
check for correct operation.

    6.  Each morning check Operational Status and Tracking
for CA MICS DAILY processing results, review report outputs
to gain familiarity with the data, monitor the run times and
archive process, and in general look for possible problems.

    7.  Using the documentation in chapter 4, "Operations",
and listings of the JCL streams, work through how a restart
would be handled.  Also, test the restoring of the database
from the backup files.

    8.  After several nights of running experience, begin
using CA MICS facilities for automatic scheduling of DAILY,
WEEKLY, MONTHLY, and YEARLY processing.  Use the SCHEDULE
command instead of DAILY from the fourth day on.

    9.  Plan on running the system in this pre-production
mode, under close monitoring and supervision, at least until
you have scheduled and executed (successfully) both a WEEKLY
and MONTHLY job stream at the required times.

   10.  During the pre-production period, begin implementing
full production operation for the CA MICS system.  See
section 4.2.2, Production Operations, for guidelines on
implementing CA MICS production processing with your
installation's production batch processing facilities.