Previous Topic: 4.3.4.4.8 REFRESH Command

Next Topic: 4.3.4.4.10 RESTORE Command

4.3.4.4.9 RESTART Command

-------------------------- RESTART Database Update --------------------------

Command ===>


Database: P (PRIMARY) - CA MICS PRIMARY DATABASE The status information was recorded at: 10OCT01 08:10 The Database update job that failed: DAILY The job will be restarted at step: DAY030 Edit the job stream before batch submit ===> YES (YES/NO) Rebuild DAYSMF step temporary work files ===> NO (YES/NO) Press END (or enter the END command) to generate and submit the RESTART job. Enter CANCEL to terminate RESTART processing for this unit Database.



. . . . . . . . . . . . . . . . . . . . . . . . . .



Use the RESTART command to restart CA MICS database update
processing after a processing failure.

RESTART generates and submits a batch job to restart database
update processing that failed.  RESTART also saves a copy of
the generated batch job in the prefix.MICS.RESTART.CNTL data
set for the unit database.

Note:  The RESTART command does NOT support the incremental
       update INCRccc job.  You must restart INCRccc
       processing through your installation's production
       batch job scheduling facility or manually submitting
       prefix.MICS.CNTL(INCRccc).

The RESTART Database Update panel displays the name of the
CA MICS database update job that failed and the job step
where CA MICS processing will resume.  If internal step
restart is enabled for this job step, then processing will
automatically resume at the last completed processing phase
in this job step.  Review the information on this panel
carefully.

If the restart job and/or step are incorrect --  that is, if
the information on this panel does NOT match your
expectations -- enter the CANCEL command to terminate RESTART
processing.  You should enter the STATUS command before
invoking RESTART processing to review and analyze CA MICS
operational job status.

The data entry fields on the Database Update panel will vary
based on unit database contents and the failing job step.

  o The Edit the job stream before batch submit option is
    always present.

  o The Rebuild DAYSMF step temporary work files option
    appears if you specified DAYSMF FILES TEMPORARY in
    prefix.MICS.PARMS(JCLDEF) for this unit database AND if
    the failure occurred during DAILY processing.

    When you specify DAYSMF FILES TEMPORARY in JCLDEF,
    CA MICS deletes the DAYSMF work files after daily
    processing completes.  The DAYSMF work files are kept
    when a failure occurs during daily processing and are
    normally available for RESTART processing.

    If the DAYSMF work files are accidentally scratched, the
    Operational Status and Tracking RESTART command can
    recreate the DAYSMF work files as part of RESTART
    processing.  Operational Status and Tracking adds the
    prefix.MICS.CNTL(DAYSMFR) batch job to the front of the
    generated RESTART job stream.

  o The Restore Accounting and Chargeback audit file option
    appears if the failure occurred during the DAY199 step --
    that is, if Daily Accounting and Chargeback processing
    failed.

    The Accounting and Chargeback audit tapes provide a
    detailed audit of daily processing.  Each daily update
    adds to the end of the ACTAUDIT DAY1 file (i.e.,
    DISP=MOD).  After daily processing, a new generation of
    the ACTAUDIT DAY2 tape is created from the DAY1 file.  If
    you restart daily Accounting and Chargeback processing
    without restoring the ACTAUDIT DAY1 file, the audit files
    WILL contain duplicate data.  See the Accounting and
    Chargeback User Guide for more information on the
    ACTAUDIT files.

    Operational Status and Tracking adds the
    prefix.MICS.CNTL(ACTDAY1R) batch job to the front of the
    generated RESTART job stream.

The RESTART Database Update panel also gives you the option
to review and/or modify the generated batch job before it is
submitted for execution.  You can cancel job submission
processing after reviewing the generated JCL.

If you need to override automatic internal step restart and
force the step to start from the beginning,

  o Specify YES to edit the job stream before execution.

  o When the job stream edit panel appears, scroll to the JCL
    EXEC statement for the job step where execution will
    resume and specify SYSPARM=NORESTART on this EXEC
    statement.

Refer to the online tutorials for detailed data entry
instructions.