4. Operation › 4.2 Operational Guidelines › 4.2.1 Getting Started
4.2.1 Getting Started
When you first install CA MICS, you should execute the system
manually for a period of time before implementing full
production operation. This "break-in" period may vary from a
few days to a month or two depending on your installation's
unique requirements and production batch facilities.
o You should use the "break-in" period to familiarize
yourself with CA MICS production operation and especially
problem diagnosis and restart/recovery facilities.
o You should also defer exploiting incremental update
facilities until you gain experience with standard CA MICS
database update processing. Incremental update processing
introduces additional operational complexity and
scheduling considerations that are better avoided when
first integrating CA MICS into your daily production
operations.
The steps described in this section provide a good
introduction for the new CA MICS administrator. Remember to
limit your "Getting Started" activities to a TEST unit
database. These procedures are NOT appropriate for a
production database containing valid information.
Getting started guidelines assume CA MICS is installed and
ready to run. (See Chapters 2 and 3 for installation
parameters and instructions.) Though there are many
operational functions, these guidelines help you become
familiar with the system before moving it into production
mode.
INITIAL CA MICS OPERATIONAL PROCESSING
Use the CA MICS Operational Status and Tracking facility of
MWF to schedule, submit, and monitor CA MICS operational
processing.
o Each day, when input data is available, use the SCHEDULE
command to initiate CA MICS processing.
o Review the Operational Status and Tracking display to
monitor the status of today's processing.
o Resolve any problem conditions and restart if necessary.
o After processing completes successfully, review Database
status (STATUS command), Database update audit trail
(HISTORY command), CA MICS checkpoint contents (CHECKPT
command), and printed outputs (JCL log, MICSLOG, and SAS
log).
CA MICS DATABASE UPDATE TEST
WARNING: The following should be performed ONLY on a TEST
unit database. DO NOT PERFORM THIS PROCEDURE ON A
PRODUCTION CA MICS UNIT DATABASE.
Use CA MICS Operational Status and Tracking to perform DAILY,
WEEKLY, and MONTHLY processing.
o DAILY Process
- When input data is available, use the DAILY command to
initiate CA MICS processing.
- Review the Operational Status and Tracking display to
monitor the status of today's processing.
- Resolve any problem conditions and restart if
necessary.
- After processing completes successfully, review
Database status (STATUS command), Database update audit
trail (HISTORY command), CA MICS checkpoint contents,
and printed outputs (JCL log, MICSLOG, and SAS log).
o WEEKLY Process
- When a new day's input data is available, use the
WEEKLY command to initiate CA MICS processing.
- Review the Operational Status and Tracking display to
monitor the status of today's processing.
- Resolve any problem conditions and restart if
necessary.
- If you activated the optional Archive Audit and/or
Archive Weekly History facilities and chose the option
to offload this processing to the stand-alone AUDIT
and/or HISTW jobs, you will need to ensure that these
jobs are submitted and execute successfully. If you
enabled the AUTOSUBMIT option for the selected archive
processing, then the WEEKLY job WEEK300 step will have
automatically submitted the AUDIT and/or HISTW job for
execution.
- After processing completes successfully, review
Database status (STATUS command), Database update
audit trail (HISTORY command), CA MICS checkpoint
contents, and printed outputs (JCL log, MICSLOG, and
SAS log).
o MONTHLY Process
- When a new day's input data is available, use the
MONTHLY command to initiate CA MICS processing.
- Review the Operational Status and Tracking display to
monitor the status of today's processing.
- Resolve any problem conditions and restart if
necessary.
- If you activated the optional Archive Monthly History
facility and chose the option to offload this
processing to the stand-alone HISTM job, you will need
to ensure that this job is submitted and executes
successfully. If you enabled the ARCHIVE HISTM JOB
AUTOSUBMIT option, then the MONTHLY job MONTH300 step
will have automatically submitted the HISTM job for
execution.
- After processing completes successfully, review
Database status (STATUS command), Database update
audit trail (HISTORY command), CA MICS checkpoint
contents, and printed outputs (JCL log, MICSLOG,
and SAS log).
o RESTORE Job
- Restore the Database from the backup tape created by
the WEEKLY process.
- After processing completes successfully, review
Database status (STATUS command), Database update
audit trail (HISTORY command), CA MICS checkpoint
contents, and printed outputs (JCL log, MICSLOG, and
SAS log).
- Database status and contents should be the same as it
was at the completion of the WEEKLY processing.
- Restore the Database from the monthly backup (MBACK)
tape created by the MONTHLY process.
- After processing completes successfully, review
Database status (STATUS command), Database update audit
trail (HISTORY command), CA MICS checkpoint contents,
and printed outputs (JCL log, MICSLOG, and SAS log).
- Database status and contents should be the same as it
was at the completion of the MONTHLY processing.
If the unit database contains the Batch and Operations
Analyzer, you may optionally update the Operations
Information Area IPL Outage Times and Reason Codes File. See
the Data Entry section (4.2.6) for more information on manual
update of Operations Information Area files.
CA MICS PROCESSING ABEND, RESTART, and FORCE/SELECT
WARNING: The following should be performed ONLY on a TEST
unit database. DO NOT PERFORM THIS PROCEDURE ON A
PRODUCTION CA MICS UNIT DATABASE.
This procedure uses two files of input data.
o TAPE 1: Input data for one day (or part of a day).
o TAPE 2: Input data for a day (or part of a day) after
the TAPE 1 data. Date/times on TAPE 2 must be
greater than date/times on TAPE 1.
Use the CA MICS Operational Status and Tracking to perform
DAILY processing for the TAPE 2 input data.
o Use the DAILY EDIT command to submit the CA MICS DAILY
job with TAPE 2 as input.
o After processing completes successfully, review Database
status (STATUS command), Database update audit trail
(HISTORY command), CA MICS checkpoint contents, and
printed outputs (JCL log, MICSLOG, and SAS log).
Next, use CA MICS Operational Status and Tracking to perform
DAILY processing for the TAPE 1 input data.
o Use the DAILY EDIT command to submit the CA MICS DAILY
job with TAPE 1 as input.
o CA MICS processing should fail with a U300 abend because
the data from TAPE 1 is older than (date/time is less
than) data already input to the Database.
o Use the FORCE command to select and force the TAPE 1 data
into the Database.
o Use the RESTART command to restart processing for TAPE 1.
o After processing completes successfully, review Database
status (STATUS command), Database update audit trail
(HISTORY command), CA MICS checkpoint contents, and
printed outputs (JCL log, MICSLOG, and SAS log).
