Previous Topic: 5.8 Add New System ID or LPAR to an Existing Database

Next Topic: 5.9.1 Make Advanced Preparations

5.9 Moving CA MICS Products to a Different Unit


Several processes MUST be performed in order to transfer an
installed and operational CA MICS product and its data files
to another unit.  The following checklists provide directions
for accomplishing the transfer:

  1 - Make Advanced Preparations
  2 - Install the Product in the Target Unit
  3 - Transfer Data Files and Checkpoint Information to the
      Target Unit
  4 - Transfer Tape Files to the Target Unit
  5 - Finalize the Process

The following conventions will be used throughout these
checklists:

original_unit       = The unit from which the CA MICS product
                      will be moved

original_prefix     = The high-level qualifier of the
                      original unit

original_tapeprefix = The high-level qualifier of the tape
                      files in the original unit

target_unit         = Destination for the product. This can
                      be a new or an existing unit

target_prefix       = The high-level qualifier of the
                      destination unit

target_tapeprefix   = The high-level qualifier of the tape
                      files in the destination unit

CONSIDERATIONS
--------------

This chapter considers Date Integration Applications only. It
does not apply to the Management Support Application
products.

All associated Accounting journal files will also need to be
moved with the appropriate Date Integration Application.

If you are going to transfer products from this unit to
another unit then these reporting mechanisms must be updated
to reflect the identifier of the new unit.  These changes
include PROC names (e.g., MICSSHRu) and DD name macros (e.g.,
&uBATX for the detail time-span), where "u" is the identifier
of the unit database.