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/uninstall 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.
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.
Perform the following steps to remove/uninstall a 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
Create a backup of all sharedprefix, prefix, and
sharedprefix.MICS.PSP libraries.
__ 2. Remove Component from Unit(s)
Complete the "Remove a Component from a Unit"
checklist in section 5.12 for each unit database that
contains the component that is being removed.
__ 3. Delete Members
Below is a list of generic members that must be
deleted (or modified) in order to effectively make a
MICS component inoperable, unmaintainable, and not
visible to a new user. A specific member name list
would be thousands of entries in length. It varies by
MICS component and the maintenance level of the
complex. If you wish to delete more members than are
listed below, contact Technical Support to obtain a
current list of all modules related to a specific MICS
component.
In this list, substitution for the following characters
is needed:
ccc is the MICS component identifier
fff is the file identifier
iii is the information area
n represents any numeric character
x represents any alphanumeric character
Use a PDS maintenance utility such as ISPF option 3.1
or 3.4, the TSO DELETE command, or SAS PROC PDS to
delete the following sharedprefix (complex level)
library members that are associated with a MICS
component. DELETE ONLY THE MEMBERS THAT ARE
ASSOCIATED WITH THE MICS COMPONENT THAT YOU ARE
REMOVING!
The libraries and generic members follow:
sharedprefix.MICS.DOC.TEXT
VOL@ccc
PICxx
where xx is the manual code associated with the
component. See section 3.6.1 of the PIOM for
these codes.
sharedprefix.MICS.ISPTLIB
ACTMFT (if ACT)
CAPMFT (if CAP)
PERMFT (if PER)
sharedprefix.MICS.LOAD:
@$CICDEP, CICMONUT (if CIC)
CICVMAM, CICEPLUT (if CIC)
IMSLOGUT (if IMS)
MALDEXIT, MALDEDRV (if LDE)
VCCxxxxx (if VCC)
VMCxxxxx, VMTxxxxx (if VMC)
Note: Also delete VCCxxxxx modules from the system
authorized (APF) library, if installed there.
sharedprefix.MICS.PSP.CNTL
cccnnnn
sharedprefix.MICS.PSP.PC.TEXT
@@ccc
sharedprefix.MICS.SOURCE
DYcccxxx, #cccxxxx (for all)
MNACTxxx, GNACTxxx, ACTxxxxx (if ACT)
SNTxxxxx, GNSNTRPT, xxcccMBO (if SNT)
VMCxxxxx, VMTxxxxx, xxcccMBO (if VMC)
cccxxxxx, xxcccMBO (for all others)
__ 4. Stop access to the removed component's data elements
by means of Documentation Access option 2.
Copy the following JCL and edit it to correspond to
the complex, provide a valid JOB statement, and
replace 'ccc' with the ID of the component being
removed. (Note that the Space Analyzer Option and the
Tape Analyzer Option have multiple components.)
Submit the job and confirm from the MICS LOG that it
ran successfully. If not, you might need to contact
Technical Support.
// JOB
//MICS JCLLIB ORDER=sharedprefix.MICS.PROCLIB
//REMCOMP EXEC MICSDM
//MWFTABL DD DISP=OLD
//SYSTSIN DD *
PROFILE MSGID
ISPSTART PGM(MACTL) NEWAPPL(L5D) +
PARM(MADA LIBRARY=MWFTLIBR,NOESTAE,COMPT=ccc,+
ADDLOGIC=L5DMFT,LOGON,NF=L5D1)
//
__ 5. (CONDITIONAL) Delete the CAP Data Set
If the CAP component is being removed, delete the
sharedprefix.MICS.CAPACITY data set and any existing
userid.MICS.CAPACITY data sets.
__ 6. (CONDITIONAL) Delete Accounting Tables
If the ACT component is being removed, delete the
ACTxxxx members from the complex's
sharedprefix.MICS.TABLES data set by running a delete
job such as the following, specifying all the ACT
members:
// JOB
//STEP1 EXEC SAS92,REGION=4M
//TABS DD DISP=OLD,DSN=sharedprefix.MICS.TABLES
//SYSIN DD *
PROC DATASETS LIBRARY=TABS;
DELETE ACTxxxx ACTxxxx ACTxxxx ... ;
//
__ 7. If PSP Online has been previously activated, update
the PSP libraries to reflect that the component has
been removed from the complex as follows:
a __ Enter the MICS Workstation Facility. Select
option 5, MICS System Administrator Functions
(MAF). Select option 2;4 from the MICS
Administrator Facility panel.
b __ 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 component being removed 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.
c __ When the receive process is completed, press
ENTER to accept the new tables.
d __ Exit PSP Online and MWF.
Note: The Status of Component panel will retain any
historical information for the component being
removed.
__ 8. 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) |
+---------------------------------------------------+
__ 9. Prepare for Next PSP Deliverable
The PSP deliverable is created and customized based on
the MICS components that are licensed to your site.
The next PSP deliverable will reload the PSP members
that you have deleted unless you do one of the following:
- Prepare to exclude the removed component from the
next PSP refresh process by editing
sharedprefix.MICS.TAPELOAD.CNTL(PSPOVER) and adding
the following statement:
PRODEXCL = ccc
- Contact Technical Support and notify CA Technologies
that you do not want delivery of a particular
component.
__ 10. Backup All Libraries
Create a backup of all sharedprefix, prefix, and
sharedprefix.MICS.PSP libraries.
__ 11. Notify CA MICS Users
Notify CA MICS users that information for the
component is no longer available.
Copyright © 2014 CA.
All rights reserved.
|
|