5. Maintenance › 5.13 Remove a Component from a Complex

5.13 Remove a Component from a Complex

Several steps must be performed in order to successfully
remove a component from a complex. These steps include
deleting members that are associated with the component and
executing generation jobs to remove the component from all of
the unit databases where it was installed.
 
This checklist comprises instructions for removing a
component in accordance with contractual agreements with CA.
Read this checklist in its entirety before proceeding with
any of the steps.  Note that completion of this checklist
will permanently disable the component at your site; it is
NOT intended as a temporary bypass to processing.
The steps in this checklist should be completed only after
all monthly processing has been completed for each unit
database that is affected.  This includes MICF Production
Reporting and User Reporting jobstreams.  It ensures that all
valid accounting and capacity data for the month has been
processed right up to the removal event.  We recommend that
you inform all CA MICS users that you will be removing the
component well in advance of the actual day. This
notification will also alert your users to the fact that the
complex will be undergoing changes on a certain date and that
some units may be unavailable during this process.
 
If a unit database contains only the component that is being
removed (or it contains only the component and ACT) then you
may also want to complete the "Delete a Unit from a Complex"
checklist in section 5.11 for that unit.  If you want a
current list of modules that may be deleted, contact CA
Technical Support.
Perform the following steps to remove an installed CA MICS
component from a CA MICS complex and all of its associated
unit databases.  If the component is installed in more than
one complex, repeat the entire checklist for each complex
that is affected.
 
__  1. Backup All Libraries

       The code and text for the products on the PSP
       distribution medium are copied directly to your
       sharedprefix.MICS and sharedprefix.MICS.PSP libraries.
       To avoid potential space problems, compress your
       sharedprefix.MICS and PSP libraries before loading the
       new product.
 
__  2. (CONDITIONAL) Delete the CAP Data Set
 
       If the CAP component is being removed, delete the
       sharedprefix.MICS.CAPACITY data set.
__  3. Remove Component(s)
 
       Complete the "Remove a Component from a Unit"
       checklist, Section 5.12 for each unit database that
       contains the component that is being removed.
 
__  4. Execute DOCAGEN1
 
       In order to regenerate the document tables for
       Document Access, submit the following job:
 
         'sharedprefix.MICS.CNTL(DOCAGEN1)'
 
       This process may take some time and is dependent on
       the number of CA MICS components installed in the
       complex.
 
       +---------------------------------------------------+
       | Reference(s): Section 3.3.7 (Valid Return Codes)  |
       +---------------------------------------------------+
__  5. (CONDITIONAL) Update PSP Online Product Change Panels
 
       If PSP Online has been previously activated, update
       the PSP libraries to reflect that the product has been
       removed from PSP Online as follows:
 
       __ Delete @@ccc from sharedprefix.MICS.PSP.PC.TEXT.
 
       __ Enter the CA MICS Workstation Facility.  Select
          option 5, CA MICS System Administrator Functions
          (MAF).  Select option 2;4 from the CA MICS
          Administrator Facility Panel.
 
       __ Select option 1 (Receive PSP Tables) on the PSP
          Utilities Menu.  Press END to re-receive the PSP
          tables.  This process will remove product changes
          for the deleted component from the following
          PSP Online Product Change panels:
 
          Apply Product Changes; Select Product Changes
 
          The panels will retain information for all other
          installed components. This process will take some
          time; the length depends on the number of
          components licensed to your site.
 
       __ When the receive process is completed, press ENTER
          to accept the new tables.
 
       __ Exit PSP Online and MWF.
 
       Note: The Status of Component panel will retain any
             historical information for the deleted
             component.
__  6. Backup All Libraries

       The code and text for the products on the PSP
       distribution medium are copied directly to your
       sharedprefix.MICS and sharedprefix.MICS.PSP libraries.
       To avoid potential space problems, compress your
       sharedprefix.MICS and PSP libraries before loading the
       new product.
 
__  7. Notify CA MICS Users
 
       Notify CA MICS users that information for the
       component is no longer available.