5. Maintenance › 5.9 Moving CA MICS Products to a Different Unit › 5.9.4 Transfer Tape Files to the Target Unit
5.9.4 Transfer Tape Files to the Target Unit
************************************************************
* Note: Ensure that the "Remove a Component From a Unit" *
* checklist, section 5.12, has been completed. *
************************************************************
Determine if HISTW or HISTM has been specified in the
prefix.MICS.PARMS(JCLDEF) member. Complete this checklist
only if YES is specified for audit, weekly, or monthly
archiving in the JCLDEF member of target_prefix.MICS.PARMS;
otherwise, move to the checklist in section 5.9.6, Finalize
the Process. Whatever you have defined for HISTW and HISTM
will be replicated in the target_unit (unless you change them
before completing the checklist).
The original_tapeprefix data sets for the product cannot be
changed by simply renaming the catalogued data sets; the
internal tape label will still carry the original_tapeprefix
name. Therefore, you must modify your CA MICS operational
JCL in order to copy the original_tapeprefix tape files to
target_prefix tape files.
NOTE: The timing of this process is CRITICAL.
If the WEEKLY or MONTHLY job will run in the original_unit
AFTER the jobs in the target_unit, point to the current (0)
GDG level.
If the jobs in the original_unit will run BEFORE the jobs in
the target_unit, change the GDG level to (-1) in the WEEKLYX
and MONTHLYX jobs, since the current level of the history
files in the original_unit will no longer contain data for
the product that you have moved.
__ 1. If weekly history archive is active in the
target_unit:
__ Create target_prefix.MICS.CNTL(WEEKLYX). Copy in
the JCL of the target_prefix.MICS.CNTL(WEEKLY)
member.
__ Modify the DD statements in the WEEKLYX member that
begin with "//HIiiifff" in the WEEK300 step, where
iii is the information area and fff is the file
name. Change the DSN parameter to the
original_tapeprefix.HISTW.iiifff(n) name for each
of the product's files, where n is GDG level -1 or
zero.
NOTE: Change only the DD statements that are
associated with the product that you are
moving.
WEEKLYX should be used for only the FIRST execution
of the weekly job in the target_unit.
NOTE: Execution of this job after the first week
will result in a loss of data!
Make sure that the normal WEEKLY job is executed in
subsequent weeks.
__ 2. If monthly history archive is active in the target
unit:
__ Create target_prefix.MICS.CNTL(MONTHLYX). Copy in
the JCL of the target_prefix.MICS.CNTL(MONTHLY)
member.
__ Modify the DD statements in the MONTHLYX member
that begin with "//HIiiifff" in the MONTH300 step,
where iii is the information area and fff is the
file name. Change the DSN parameter to the
original_tapeprefix.HISTM.iiifff(n) name for each
of the product's files, where n is GDG level -1 or
zero.
NOTE: Change only the DD statements that are
associated with the product that you are
moving.
MONTHLYX should be used for only the FIRST
execution of the monthly job in the target_unit.
NOTE: Execution of this job after the first month
will result in a loss of data!
Make sure that the normal MONTHLY job is executed
in subsequent months.
__ 3. If audit archiving is performed for the product:
__ Consider copying the weekly audit tapes, named
original_tapeprefix.MICS.AUDIT.iiifff(n), to the
target unit, where n is GDG level -1 or zero.
NOTE: No retrofit logic is required in order to copy
the tapes.
+----------------------------------------------------------+
| Reference(s): Section 2.3.3.3.2.1.5, Database Unit Tape |
| Specifications |
+----------------------------------------------------------+
__ If you choose NOT to copy these files, inform your
users that the audit archive files for the product
that were created prior to the transfer will remain
under the original_tapeprefix name.
__ 4. Finalize Process
Complete the "Finalize the Process" checklist in
Section 5.9.5.