5. Maintenance › 5.9 Moving CA MICS Products to a Different Unit › 5.9.1 Make Advanced Preparations

5.9.1 Make Advanced Preparations

__  1. Establish Time Frame

       Establish a schedule and time frame for accomplishing
       the transfer.  We strongly recommend the following:

       __ Wait until monthly processing has been completed in
          the affected units before executing the transfer
          (particularly if the CA MICS product has an
          accounting interface)

       __ Execute a DAILY as the first operational job in
          both units after the transfer has been completed,
          since week-to-date and month-to-date files are
          built during the daily process.

__  2. Notify Users

       Alert all CA MICS users that you will be moving the
       product well in advance of the actual day.

       __ Inform all affected personnel that the
          original_unit will be undergoing changes on a
          certain date and may be unavailable for use.

       __ Notify your users that the database identifier and
          the data set names that are used in their JCL,
          report code, user-level MICF inquiries, and
          database macros must be changed for the product.

__  3. Determine DASD Amount

       Immediately, prior to installing the product in the
       target_unit, determine the amount of DASD space
       allocated to the product in the original_unit, as
       follows:

       __ Print the prefix.MICS.PARMS(DBMODEL) member.

       __ Review prefix.MICS.PARMS(DBSPLIT) to determine if
          any of the product's information area files are
          included in a split timespan.

       __ Create a SAS PROC DATASETS job in the original_unit
          to determine the total number of tracks used by the
          CA MICS product's files in each timespan
          (including any split timespans).   Use the printout
          of the DBMODEL member to assist you in identifying
          the information areas and file names for the
          product.

          Use the following job as a example:
             //DATASETS EXEC MICSSHRx
             //SYSIN    DD *
               PROC DATASETS DD=timespan;
               PROC DATASETS DD=timespan;
               PROC DATASETS DD=timespan;

          where x is the database identifier of the
          original_unit, and timespan equals DETAIL, DAYS,
          WEEKS, MONTHS, YEARS (if active) or the DD name of
          any split timespan (e.g., DETAIL2).

       __ Add a valid job card (and PROCLIB card, if
          required) and submit the job.  Ensure that the job
          completes with a condition code of zero.

       __ Print and save the output of the  DATASETS job for
          use in later steps of this checklist.

__  4. Install the Products

       Complete the "Install the Products in the Target_Unit"
       checklist in section 5.9.2.