|
|
|
---------------------- Operational Status and Tracking --------- ROW 1 OF 6
Command ===> Scroll ===> CSR
Commands: Schedule, Daily, Weekly, Monthly, Yearly, Backup, Restore, Restart, Status/History/Checkpt/Joblog, Suspend/Resume, Force
Database Current Operation Last Completed Edit Suspend Cmd ID Label Type as of 10 OCT 2001 Job/Step Date JCL Updates -------- -- -------- - ------------------- ------------------ --- --- ________ C CICS U MONTHLY Completed MONTHLY 10OCT2001 NO NO ________ D DASD U MONTHLY DUE TODAY WEEKLY 09OCT2001 NO NO ________ I IMS U MONTHLY Completed MONTHLY 10OCT2001 NO NO ________ P PRIMARY P MONTHLY FAILED DAY020 10OCT2001 NO NO ________ R REMOTE U MONTHLY FAILED DAYALL 10OCT2001 NO NO ________ T TEST T DAILY OVERDUE DAILY 19SEP2001 NO NO ****************************** BOTTOM OF DATA ********************************
. . . . . . . . . . . . . . . . . . . . . . . . . .
Operational Status and Tracking presents a scrollable display
of the unit databases in your CA MICS complex. There is one
line on the display for each unit database.
o The primary display shows the current status of each unit
database update.
o Secondary displays, accessed by scrolling RIGHT, show the
CA MICS processing schedule and Operational Status and
Tracking parameters:
- Use the RIGHT primary command to access the secondary
displays. Scroll right once for the schedule forecast
display and scroll right again for the parameter
display.
- Use the LEFT primary command to return to the primary
(status) display. LEFT MAX returns immediately to the
primary display.
Note: Operational Status and Tracking does not fully support
CA MICS incremental update facilities. The JOBLOG command
will report on INCRccc and SPLITSMF executions. However, the
SCHEDULE command cannot be used to schedule the INCRccc and
SPLITSMF jobs because their scheduling is dependent on the
availability of the input data and on day-time batch
processing considerations unique to your data center. You
can use the primary and/or line commands for INCRUPDT and
SPLITSMF to manually submit these jobs.
This section describes the content of the three Operational
Status and Tracking displays.
o Database Status Display
o Schedule Forecast Display
o Parameter Display
The Database Status, Schedule Forecast, and Parameter
displays begin with a database heading that consists of three
columns of database identification.
o ID - The CA MICS unit database (DB) ID you specified
when you defined the unit database.
o Label - The 1-8 character unit DB label you specified
when you defined the unit database.
o Type - The type of unit database.
P is the PRIMARY database.
U is a standard production UNIT database.
T is a TEST database.
S is a SPECIAL database.
DATABASE STATUS DISPLAY
The Database Status display presents information on the
current operation, last completed processing, and the
database update status. It is the default display when you
access Operational Status and Tracking.
Current Operation as of - The date of the CA MICS database
update process and status. (Two
columns of information are
displayed.)
o The panel initially lists the processing scheduled for
today. If you enter the DAILY, WEEKLY, MONTHLY, YEARLY,
BACKUP, RESTORE, or RSTATUS commands, then Current
Operation becomes the processing you requested. The
display also reacts to processing scheduled outside of
Operational Status and Tracking. Once database update
processing begins, Current Operation is changed to
reflect the processing that is in progress or completed.
o Current operation includes:
DAILY - Daily CA MICS database update.
INCRUPDT - Daily CA MICS database update.
WEEKLY - Daily database update and weekly cycle
closeout.
MONTHLY - Daily database update and monthly cycle
closeout.
YEARLY - Daily database update and yearly cycle
closeout.
BACKUP - Database backup was explicitly requested or
failed.
RESTORE - Database restore was explicitly requested or
failed.
RSTATUS - Database run status processing was
explicitly requested.
o Processing status includes:
Completed - Processing executed today has completed
successfully.
DUE TODAY - Scheduled processing has not yet occurred.
OVERDUE - Scheduled processing is late.
Today's processing is OVERDUE if not
complete by the user-specified deadline
(hh:mm). The default is 8 a.m.
Submitted - Scheduled or requested processing has been
submitted for execution but is not yet
complete.
INCOMPLETE - Database update processing began execution
but has not finished.
If the job is NOT still executing, then it
may have been canceled by the operator,
failed with a JCL error, or terminated by
an MVS system crash. RESTART may be
required.
FAILED - Scheduled or requested processing
terminated abnormally.
Use the STATUS command for more
information. Use the RESTART command to
restart database update processing.
You can enter the BACKUP or RESTORE
command to restart backup/restore
processing that failed.
Last Completed - The last CA MICS process completed for this
unit database. Two columns of information
are displayed.
o Job/Step - The last production job (DAILY, INCRUPDT,
WEEKLY, MONTHLY, YEARLY, BACKUP, or RESTORE)
completed if no errors occurred.
If database update processing failed or is
still in progress, the last completed step
name is displayed.
For example, if daily processing failed
updating the SMF product files, then DAY020
would appear to show that CA MICS completed
the DAY020 (update RMF product files) step.
In this situation, restart would be at the
DAY030 step.
If BACKUP or RESTORE processing failed,
Job/Step is not changed. That is, Last
Completed still reflects the last completed
processing before BACKUP or RESTORE began.
o Date - The date that Job/Step completed.
Edit JCL - Use this column to specify whether you want to
edit generated production job JCL before the job
is submitted for processing.
Suspend Updates - The database update status.
YES - Database update processing has been suspended.
This generally means that maintenance is being
applied. CA MICS will NOT allow you to execute any
database update processing.
Enter the RESUME command to activate database
update processing.
NO - Database update processing is available. This is
the normal status.
Enter the SUSPEND command to block database update
processing.
The Operational Status and Tracking display is refreshed when
you execute any Operational Status and Tracking command. Use
the REFRESH command to update the display without invoking
other functions.
---------------------- Operational Status and Tracking --------- ROW 1 OF 6
Command ===> Scroll ===> CSR
Commands: Schedule, Daily, Weekly, Monthly, Yearly, Backup, Restore, Restart, Status/History/Checkpt/Joblog, Suspend/Resume, Force
Database Cmd ID Label Type Seven Day Schedule Forecast -------- -- -------- - --------------------------------------------------- ________ C CICS U 10OCT2001 D.M.B D...B D...B D...B D...B D...B D...B ________ D DASD U 09OCT2001 DW..B D.M.B D...B D...B D...B D...B D...B ________ I IMS U 10OCT2001 D.M.B D...B D...B D...B D...B D...B D...B ________ P PRIMARY P 10OCT2001 D.M.B D...B D...B D...B D...B D...B D...B ________ R REMOTE P 10OCT2001 D.M.B D...B D...B D...B D...B D...B D...B ________ T TEST T 19SEP2001 D...B D.... D...B D.... D...B DW..B D...B ****************************** BOTTOM OF DATA ********************************
. . . . . . . . . . . . . . . . . . . . . . . . . .
Access the Seven Day Schedule Forecast by scrolling RIGHT from the Database Status display. This panel displays the CA MICS processing schedule for a seven day period. The first column is the schedule beginning date. This is the date of the first schedule forecast entry. Seven schedule forecast entries follow the schedule beginning date. Each forecast entry has the format dwmyb for DAILY, WEEKLY, MONTHLY, YEARLY, and BACKUP, respectively. The schedule forecast entries indicate which CA MICS process is scheduled for a specific day (the beginning date and the next six days): DAILY, DAILY/BACKUP, DAILY/WEEKLY/BACKUP, and so on. A period (.) indicates that the corresponding job is NOT scheduled. In the example above, the following processing is scheduled for the D (DASD) unit: o October 9 - WEEKLY process (DAILY/WEEKLY/BACKUP) o October 10 - MONTHLY process (DAILY/MONTHLY/BACKUP) o October 11 through 15 - DAILY process (DAILY/BACKUP) PARAMETER DISPLAY
---------------------- Operational Status and Tracking --------- ROW 1 OF 6
Command ===> Scroll ===> CSR
Commands: Schedule, Daily, Weekly, Monthly, Yearly, Backup, Restore, Restart, Status/History/Checkpt/Joblog, Suspend/Resume, Force
Database Overdue Cmd ID Label Type (hh mm) -------- -- -------- - -- -- ________ C CICS U 08 00 ________ D DASD U 08 00 ________ I IMS U 08 00 ________ P PRIMARY P 08 00 ________ R REMOTE P 08 00 ________ T TEST T 08 00 ****************************** BOTTOM OF DATA ********************************
. . . . . . . . . . . . . . . . . . . . . . . . . .
Access the Parameter display by scrolling RIGHT from the
Schedule Forecast display.
This panel lists the overdue time for each unit database.
Use the Overdue column to override the 08:00 default daily
A MICS database update processing deadline.
o Daily processing is considered late and status is set to
OVERDUE if not completed before this user-specified time-
of-day.
o Status is DUE TODAY until the overdue time.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |