4. Operation › 4.3 Operations Reference › 4.3.4 Operational Status and Tracking › 4.3.4.4 Operational Status and Tracking Commands › 4.3.4.4.10 RESTORE Command
4.3.4.4.10 RESTORE Command
--------------------------- RESTORE Unit Database ------------- ROW 1 OF 27
Command ===> Scroll ===> CSR
Database: C (CICS) - CA MICS CICS DATABASE
Edit the job stream before batch submit ===> YES (YES/NO)
Line Cmds: S Select
Cmd Date Time Generation Description
- --------- ----- ---------- ---------------------------------------------
_ 10OCT2001 4:41 BACKUP 0 BACKUP Completed (after Monthly)
_ 10OCT2001 4:09 MBACK 0 MONTHLY BACKUP Completed
_ 10OCT2001 4:06 MONTHLY Completed
_ 10OCT2001 3:58 DAILY Completed (Monthly in progress)
_ 10OCT2001 0:01 DAILY, Monthly, Backup submitted by OPRUSR1
_ 09OCT2001 7:15 BACKUP -1 BACKUP Completed (after Weekly)
_ 09OCT2001 7:02 WEEKLY Completed
_ 09OCT2001 6:24 DAILY Completed (Weekly in progress)
_ 09OCT2001 4:25 DAILY, Weekly, Backup submitted by OPRUSR1
_ 09OCT2001 4:15 0 RESTORE from BACKUP 08OCT2001 02:46
_ 09OCT2001 3:42 DAILY FAILED U101 in DAY040
_ 09OCT2001 0:15 DAILY, Weekly, Backup submitted by OPRUSR1
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Use the RESTORE command to restore unit database contents
from a selected unit database backup.
RESTORE generates and submits a batch job to restore unit
database files. RESTORE also saves a copy of the generated
batch job in the prefix.MICS.RESTART.CNTL data set for the
unit database.
The RESTORE Unit Database panel displays an audit trail of
your unit Database update, BACKUP, and RESTORE processing.
Note: The display does NOT reflect incremental update
(INCRccc job) processing.
Select a BACKUP entry from this display to RESTORE the
Database or enter CANCEL to terminate RESTORE processing.
If you specified YES for the RESTORE BACKUP parameter in the
JCLDEF member of prefix.MICS.PARMS, CA MICS will take a unit
database backup before beginning the restore. This option
gives you the opportunity to return the Database to the
condition that it was in prior to the restore.
o If you specify NOBACKUP when you enter the RESTORE
command on the Operational Status and Tracking panel,
CA MICS will bypass the pre-restore backup.
o CA MICS will also bypass the pre-restore backup if the
Database is not updatable--that is, if prior CA MICS
processing failed. CA MICS will NOT backup a bad
Database.
o See the RESTORE Operational Job section (4.3.3) of this
guide for more information on pre-restore backups.
The RESTORE Unit Database 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.
The rows of the RESTORE Unit Database panel describe your
Database update, BACKUP, and RESTORE processing.
o Both the standard and special backups taken for this
CA MICS unit database are listed.
o Unit database update processing is listed (incremental
update processing is not included).
o Operational jobs submitted by Operational Status and
Tracking are listed.
o Checkpoint changes made by Operational Status and
Tracking are listed.
The display is sorted with the most recent processing first
and in the order that processing/changes occurred. The most
recent Database and/or checkpoint updates appear first.
Backup generations are identified by the date and time the
backup was taken, the generation number, and a description.
Standard CA MICS daily and monthly backups are identified by
name -- BACKUP (after Daily), MONTHLY BACKUP, etc. Special
backup generations are identified by the description you
entered on the BACKUP Unit Database panel.
BACKUP entries are dropped from the audit log when the
corresponding tape GDG entry expires -- you specified BACKUP
retention in the prefix.MICS.PARMS(JCLGEN) using the BCKUPGDG
parameter. Entries for Database update processing, job
submission, and checkpoint changes that occurred prior to an
expired backup are also dropped from the display. That is,
once the backup tapes begin to expire (the BCKUPGDG limit is
reached), the Database update processing, job submission,
and checkpoint change entries older than the oldest backup
entry are dropped.
CA MICS retains six monthly backup (MBACK) generations in the
audit log.
Refer to the online tutorials for detailed data entry
instructions and for information on using CA MICS commands
(e.g., FIND, LOCATE, SHOW, SORT, etc.) on this panel.
Information reported by the example above includes:
o The most recent backup was created on October 10, 2001.
o The MONTHLY process executed on October 10. DAILY,
MONTHLY, Monthly backup (MBACK), and BACKUP processing
completed successfully.
o The WEEKLY process was submitted through Operational
Status and Tracking on October 9.
- The DAILY portion of this processing failed with a
U101 abend in step DAY040.
- The Database was restored and WEEKLY processing was
resubmitted. WEEKLY completed successfully.
