6. Database Tailoring and Retrofitting Techniques › 6.2 Tailoring the Database › 6.2.3 Tailoring Archive Files › 6.2.3.3 Add File to Weekly History Archive Tape
6.2.3.3 Add File to Weekly History Archive Tape
CA MICS includes a facility to copy a file's data to offline
storage (a tape generation data group) every week. Such data
may be useful for maintaining long periods of data for large
volume historical analyses without using undue amounts of
online storage. A file eligible for weekly history archiving
must exist in the WEEKS time-span.
To add a file to the weekly history archive tape, which is
generated by the CA MICS WEEKLY or the standalone HISTW
operational job, do the following:
1. Edit the FILE statement in
sharedprefix.MICS.GENLIB(cccGENIN). Change the "N" in
the the file's weekly history archive position to "Y".
Refer to Section 6.2.3 for more information on the
GENIN FILES statement.
2. Submit the sharedprefix.MICS.CNTL(cccCGEN) job to
regenerate the component.
3. Edit prefix.MICS.PARMS(DBMODEL) for all database units
in which the component is installed.
To add the file, the FILE statement for that file must
have a cutoff limit greater than zero in the weekly
history archive position. Define a zero cutoff limit in
units where you don't want to create this file.
Refer to Section 2.3.4.1.2 in the PIOM for more
information on the FILE statement in DBMODEL.
4. Submit the prefix.MICS.CNTL(CYCLEGEN) job for all
database units in which the component is installed.
This job changes the component's executable code in the
prefix.MICS.USER.SOURCE libraries and affects only the
database units in which the component is installed.
5. Review prefix.MICS.PARMS(JCLDEF) NULLSER keyword.
If you have EXISTING history archive tapes for this
unit in an automatic tape loader (ATL), you may need to
change the NULLSER value to the volume serial number of
the existing history archive tape.
For JES2 customers -- if left unchanged, you may see a
tape mount for volume serial NULSER; however, the
WEEKLY job will complete normally, regardless of the
unsatisfied tape mount request.
For JES3 customers -- if left unchanged, the WEEKLY job
will not continue because the tape mount cannot be
satisfied. The job waits.
Refer to Section 2.3.3.2.1.5 of the PIOM for more
information on the use of the NULLSER keyword.
To determine the volume serial number of an existing
history archive tape, under TSO option 6, issue the
command:
LISTC EN('tapeprefix.HISTW.iiifff') ALL
for a file which is currently active for history
archive. You may refer to the WEEKLY job WEEK300 step
(or the standalone HISTW job if you activated the
standalone archive weekly history job option) and
choose any one of the HIiiifff DDs.
Repeat this step for every unit which has this
component installed.
6. Edit prefix.MICS.PARMS(JCLGENU) for all database units
in which the component is installed. Specify:
WEEKLY HISTW
If you made a change to the NULLSER value as stated in
the previous step, specify:
WEEKLY HISTW GDGSGEN
instead.
7. Submit the prefix.MICS.CNTL(JCLGENU) job(s).
This generates the WEEKLY and/or HISTW job JCL that
contains DD statements for the new weekly history tape
files, as well as recreates the GDGSGEN job with the
volume serial number that the first generation of the
new file is cataloged to (with the NULLSER value you
chose).
8. Submit prefix.MICS.CNTL(GDGSGEN) for all database units
in which the component is installed.
This creates weekly history tape generation data groups
for the new archive file(s), if necessary.
For example, assume the NPANCP file appeared in the following
archives:
WEEKLY WEEKLY MONTHLY
AUDIT HISTORY HISTORY
-------- -------- --------
NO NO YES
Assume the desired configuration is:
WEEKLY WEEKLY MONTHLY
AUDIT HISTORY HISTORY
-------- -------- --------
NO YES YES
The initial definition of the NPANCP file statement in
sharedprefix.MICS.GENLIB(NPAGENIN) would be:
FILE NCP 00 1 Y Y Y Y N N N Y NCP Activity File
| | |
no WEEKLY audit -----+ | |
no WEEKLY history-------+ |
MONTHLY history ---------+
Change this statement to:
FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File
|
+- WEEKLY history produced
The number of cycles of the file that CA MICS will use as
input to the weekly history archive is fixed at 1. This
means the last cycle of WEEKS time-span data will be copied
to the new generation of the weekly history archive tape when
the weekly history is generated in the CA MICS WEEKLY or
standalone HISTW operational job. The data from the
database is added to the previous generation of the file's
weekly history tape.
The test of what observations to put on the archive file is:
any observation from a date later than the specified cutoff
date will be copied to the archive file. No observations
from the current week will be included in the input.
The cutoff date is determined by the user specification of
the weekly history retention limit in the DBMODEL member of
the prefix.MICS.PARMS library.
For example, assume the retention limit was 010. The
previous ten weeks of weekly history would be available on
any generation of the weekly history tape. Also, assume the
week just processed by the current CA MICS WEEKLY or HISTW
run (now cycle NPANCP01) is for week 26 of the year.
Contents Last Week's Contents
of Last Activity of New
Weekly From Online Weekly
History Database History
---------- ---------- ----------
week 16-(dropped, too old)
week 17------------------>week 17
week 18------------------>week 18
week 19------------------>week 19
week 20------------------>week 20
week 21------------------>week 21
week 22------------------>week 22
week 23------------------>week 23
week 24------------------>week 24
week 25------------------>week 25
week 26----->week 26
