5. Maintenance › 5.9 Moving CA MICS Products to a Different Unit › 5.9.2 Install the Product in the Target Unit
5.9.2 Install the Product in the Target Unit
__ 1. (CONDITIONAL) Add a New Product
Complete the "Add a New Product to an Existing
Database Unit" checklist, Section 3.8.2
OR
Complete the "Add a New Product to a New Database
Unit" checklist, Section 3.8.3.
__ 2. Incorporate Parameters
Incorporate parameters from the original_unit as
appropriate. Review each of the product parameter
members for changes during the installation process.
__ 3. (CONDITIONAL) Reenter Journal Files' Information
If this product interfaces with the CA MICS Accounting
and Chargeback product, then you must REENTER the
product's journal file rates, algorithms, and
qualifications in the target_unit. The existing
accounting specifications CANNOT be copied from the
original_unit.
+-----------------------------------------------------------+
| Reference(s): Section 7.6, Accounting and Chargeback |
| User Guide |
+-----------------------------------------------------------+
__ 4. Verify Timespans
Use the printout from the PROC DATASETS in the
Advanced Preparation Checklist to verify that each
timespan in the target_unit has enough space to
accommodate the product that you are moving.
Reallocate space as required.
__ 5. Review User Modifications
Review any unit-level user modifications that apply to
the product. These may include (but are not limited
to) exception processing code, accounting journal file
exits, or user-defined formats in
prefix.MICS.USER.LOAD. Make changes as required and
incorporate your modifications into the structure of
the target_unit.
__ 6. Update Administrator-written Report
Change any existing administrator-written report
programs, to specify the target_prefix,
target_tapeprefix, or database ID, as required.
__ 7. Regenerate MICF Production Inquiries
Use the MICF Catalog Administration function under MWF
to regenerate any MICF production jobstream inquiries
so that they reference the target_unit.
__ 8. Back Up Libraries (Target Unit)
After completing the installation of the product in
the target_unit, back up the complex and the
target_unit's system libraries (e.g., CNTL, PARMS,
ASM, USER.SOURCE, USER.LOAD).
__ 9. Transfer Files and Checkpoint Information
Complete the "Transfer Data Files and Checkpoint
Information to the Target_Unit" checklist in Section
5.9.3.