6. Database Tailoring and Retrofitting Techniques › 6.2 Tailoring the Database › 6.2.3 Tailoring Archive Files › 6.2.3.5 Add File to Monthly History Archive Tape
6.2.3.5 Add File to Monthly History Archive Tape
CA MICS includes a facility to copy a file's data to offline
storage (a tape generation data group) every month. 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 monthly history
archiving must exist in the MONTHS time-span.
To add a file to the monthly history archive tape, which is
generated by the CA MICS MONTHLY or the standalone HISTM
operational job, do the following:
1. Edit the FILE statement in
sharedprefix.MICS.GENLIB(cccGENIN). Change the "N" in
the the file's monthly 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 monthly
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
MONTHLY job will complete normally, regardless of the
unsatisfied tape mount request.
For JES3 customers -- if left unchanged, the MONTHLY
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.HISTM.iiifff') ALL
for a file which is currently active for history
archive. You may refer to the MONTHLY job MONTH300
step (or the standalone HISTM job if you activated the
standalone archive monthly 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:
MONTHLY HISTM
If you made a change to the NULLSER value as stated in
the previous step, specify:
MONTHLY HISTM GDGSGEN
instead.
7. Submit the prefix.MICS.CNTL(JCLGENU) job(s).
This generates the MONTHLY and/or HISTM job JCL that
contains DD statements for the new monthly 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 monthly history tape generation data
groups for the new archive file(s), if necessary.
For example, assume the NPANCP file appears in the following
archives:
WEEKLY WEEKLY MONTHLY
AUDIT HISTORY HISTORY
-------- -------- --------
NO YES NO
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 have been:
FILE NCP 00 1 Y Y Y Y N N Y N NCP Activity File
| | |
no WEEKLY audit ----+ | |
WEEKLY history ------+ |
no MONTHLY history--------+
Change this statement to:
FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File
|
+- MONTHLY history produced
The number of cycles of the file that CA MICS will use as
input to the monthly history archive is fixed at 1. This
means the last cycle of MONTHS time-span data will be copied
to the new generation of the monthly history archive tape
when the monthly history is generated in the CA MICS MONTHLY
or standalone HISTM operational job. The data from the
database is added to data on the previous generation of the
file's monthly 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 month will be included in the input.
The cutoff date is determined by the user specification of
the monthly history retention limit in the DBMODEL member of
the prefix.MICS.PARMS library.
For example, assume the retention limit was 010. The
previous ten months of monthly history would be available on
any generation of the monthly history tape. Also, assume the
month just processed by the current CA MICS MONTHLY or HISTM
run (now cycle NPANCP01) is for month 11 of the year.
Contents Last Month's Contents
of Last Activity of New
Monthly From Online Monthly
History Database History
---------- ---------- ----------
month 01-(dropped, too old)
month 02----------------->month 02
month 03----------------->month 03
month 04----------------->month 04
month 05----------------->month 05
month 06----------------->month 06
month 07----------------->month 07
month 08----------------->month 08
month 09----------------->month 09
month 10----------------->month 10
month 11---->month 11