10. MODIFICATION › 10.1 Parameter Modification › 10.1.1 Add or Delete a System in a Unit

10.1.1 Add or Delete a System in a Unit

If you are adding a system (a SYSID with CA MICS Space
Collector data), to a unit, there are certain requirements
imposed by the CA MICS base architecture that may need to be
performed once.


Scenario 1: SMF/RMF Already Defined in Unit

Let's assume you already have a production unit database that
processes SMF and RMF data from two MVS systems -- that is,
from hypothetical SYSIDs defined as S001 and S002.  You are
planning the implementation of the CA MICS DASD products to
collect and process data from either S001 or S002 (or both --
refer to the CA MICS Space Collector Guide for Shared DASD
considerations).

Because you have already defined S001 and S002 as systems to
be controlled in the unit, you can proceed directly to the
parameter generation process for VCAPGEN and HSMPGEN as
discussed in Chapter 7 of this guide.


Scenario 2: DASD Data from Remote SYSID

To build on scenario 1 above, let's now assume you want to
process some VCC data that was collected from a new data
center you have acquired.  For discussion purposes, let's
refer to this "remote" data center by it's SYSID - R003.

Unlike scenario 1 where CA MICS Base software already "knew"
about S001 and S002 as systems to be processed in this unit,
you must define the SYSID called R003 and you must perform
some housekeeping steps to satisfy the validation functions
of CA MICS Base.

a.  Update prefix.MICS.PARMS(SYSID) with the new SYSID.

    Section 2.3.2.2 in the PIOM describes this process.

b.  Update prefix.MICS.PARMS(PRFGP) with a dummy performance
    group for the new SYSID.

    Section 2.3.2.5 in the PIOM describes this process.

c.  Submit the BASPGEN job in prefix.MICS.CNTL.

    Section 3.5.5 in the PIOM describes this process.

After you complete these steps, you can proceed to the
parameter generation processes for VCA and HSM described in
detail in Section 7.3 of this guide.


Scenario 3: Deleting a SYSID

To remove a system from the CA MICS Space Analyzer processing
within a unit, you must determine if you are reversing the
situation described in scenarios 1 or 2 above.  Continuing
with our hypothetical SYSIDs, you need to determine if any CA
MICS product will be processing data with the SYSID value:

a. If R003 is to be removed, simply delete the lines in
   members SYSID and PRFGP in prefix.MICS.PARMS that define
   R003, and run another BASPGEN job.

   You may need to revisit Section 7.3 and delete data set
   references to data from R001 in prefix.MICS.PARMS member
   INPUTVCA and/or INPUTHSM.

b. If S001 and/or S002 will no longer be generating VCC data
   (for example, perhaps a third SYSID called S003 has been
   added to scan all common DASD only), then you should do
   nothing because the assumption is S001 and S002 will still
   give off SMF and RMF data that needs to be processed and
   therefore, the SYSID and PRFGP definitions must remain
   intact.