---------------------------- CA MICS Processing Log ---------------------------- Command ===> Scroll ===> CSR Database: C (CICS) - CA MICS CICS DATABASE Date Time Description Generation --------- ----- --------------------------------------------- ---------- 10OCT2001 4:41 BACKUP Completed (after Monthly) BACKUP 0 10OCT2001 4:09 MONTHLY BACKUP Completed MBACK 0 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 Completed (after Weekly) BACKUP -1 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 RESTORE from BACKUP 08OCT2001 03:34 09OCT2001 3:42 DAILY FAILED U101 in DAY040 09OCT2001 0:15 DAILY, Weekly, Backup submitted by OPRUSR1 08OCT2001 3:34 BACKUP Completed (after Daily) BACKUP -2 08OCT2001 3:15 DAILY Completed 07OCT2001 2:56 BACKUP Completed (after Daily) BACKUP -3 07OCT2001 2:32 DAILY Completed . . . . . . . . . . . . . . . . . . . . . . . . . . .
JOBLOG displays the CA MICS processing audit log.
The rows of the CA MICS Processing Log 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 Database update processing is listed.
o Operational jobs submitted by Operational Status and
Tracking are listed.
o Checkpoint changes made by Operational Status and
Tracking are also 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 prefix.MICS.PARMS(JCLGEN) with 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 MONTHLY process submitted by OPRUSR1 executed on
October 10, 2001. DAILY, MONTHLY, Monthly backup
(MBACK), and BACKUP processing completed successfully.
o The WEEKLY process was submitted by OPRUSR1 on October 9,
2001 using the Operational Status and Tracking facility.
- 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.
|
Copyright © 2014 CA.
All rights reserved.
|
|