5. Maintenance › 5.12 Remove a Component from a Unit
5.12 Remove a Component from a Unit
************************************************************
* Note: The use of 'prefix' in this checklist is the *
* high-level qualifier of the unit from which the *
* CA MICS component will be removed. *
* *
* The use of original_unit in this checklist is the *
* same as the unit from which you are removing the *
* components. *
************************************************************
Several steps must be performed in order to successfully
remove a component from a unit. These steps include editing
some members, deleting members that are associated with the
component and executing generation jobs for the unit.
The steps in this checklist should be completed only after
all monthly processing has been completed for the unit. 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 this component well in
advance of the actual day. This notification will alert your
users to the fact that the complex will be undergoing changes
on a certain date and that this unit may be found unavailable
during this process.
If the unit database contains only the component that is
being removed (or it contains only the component and ACT)
then you may want to complete the "Delete a Unit from a
Complex" checklist in section 5.11 instead of this checklist.
__ 1. Edit JCLDEF
Edit prefix.MICS.PARMS(JCLDEF) in the original_unit.
Remove the identifier of the component from the
COMPONENT statement and also from the SMFRECORDING
statement (if coded).
__ 2. (CONDITIONAL) Edit JCLDEF
If this component is the only component that
interfaces with Accounting and Chargeback, and the
accounting months-end processing has occurred, edit
JCLDEF. Remove the ACT identifier from the COMPONENT
statement.
__ 3. (CONDITIONAL) Edit DBMODEL
If the original_unit is not a special database unit,
edit prefix.MICS.PARMS(DBMODEL). Delete all FILE and
DATA statements associated with the component.
__ 4. Edit COMPRESS
Edit prefix.MICS.PARMS(COMPRESS). Delete all FILE and
DATA statements associated with the component.
__ 5. Execute JCLGENB
Regenerate the CA MICS unit installation Jobs. Submit
the following job:
'prefix.MICS.CNTL(JCLGENB)'
+---------------------------------------------------+
| Reference(s): Section 3.5.3.3 |
+---------------------------------------------------+
__ 6. (CONDITIONAL) Execute JCLGENF
If the original_unit is a special database unit,
generate the special database installation jobs by
submitting the following job:
'prefix.MICS.CNTL(JCLGENF)'
__ 7. (CONDITIONAL) Execute SELFILES
If the original_unit is a special database unit, edit
prefix.MICS.PARMS(SELFILES). Delete all FILE and
DATA statements associated with the component. Submit
the following job:
'prefix.MICS.CNTL(SELFILES)'
__ 8. (CONDITIONAL) Edit EXECDEF
If the original_unit is a special database unit, edit
prefix.MICS.PARMS(EXECDEF). Delete any identifier of
the component.
__ 9. Review UNITGEN Options
Review sharedprefix.MICS.PARMS(UNITGEN) for the
options in effect.
+---------------------------------------------------+
| Reference(s): Section 5.6.1 |
+---------------------------------------------------+
__ 10. Execute UNITGEN
Submit the following job:
'prefix.MICS.CNTL(UNITGEN)'
Ensure that there are no error messages in MICSLOG or
SYSTSPRT and that the MICSLOG contains the normal
termination messages, BAS10999I or BAS11999I.
If the UNITGEN NOAUTOSUBMIT, or UNITGEN AUTOSUBMIT and
NOOPJCL parameters have been specified, UNITGEN will
complete with a normal return code of 4. Otherwise,
UNITGEN and UNITGEN1 should complete with a return
code of 0.
__ 11. (CONDITIONAL) Execute UNITGEN1
Perform this step only if your installation has
specified
UNITGEN NOAUTOSUBMIT
You must manually submit the UNITGEN1 job to perform
the required JCL and parameter generations.
After the UNITGEN job from the previous step
completes successfully, submit the following job:
'prefix.MICS.CNTL(UNITGEN1)'
__ 12. Verify UNITGEN1 Results
Verify that the UNITGEN1 job executed successfully.
The UNITGEN1 job contains multiple steps that perform
COPYLIBU, CYCLEGEN, JCLGEN, cccPGEN, and GDGSGEN
processing or part of it.
Ensure that there are no error messages in MICSLOG or
SYSTSPRT and that the MICSLOG contains the normal
termination messages, BAS10999I or BAS11999I.
All steps should complete with a return code of zero.
If errors are encountered during UNITGEN1 job
execution, correct the errors and rerun UNITGEN and
UNITGEN1 jobs respectively.
+--------------------------------------------------+
| Reference(s): Sections 5.6 and 5.6.1 |
+--------------------------------------------------+
__ 13. (CONDITIONAL) Execute JCLGEND
Perform this step only if your installation has
specified
UNITGEN NOOPJCL
If NOOPJCL is specified, UNITGEN1 did not generate the
CA MICS operational jobs.
To generate these jobs, submit the following job:
'prefix.MICS.CNTL(JCLGEND)'
Ensure that there are no error messages in MICSLOG or
SYSTSPRT and that the MICSLOG contains the normal
termination messages, BAS10999I or BAS11999I.
All steps should complete with a return code of zero.
+---------------------------------------------------+
| Reference(s): Section 5.6.1 |
+---------------------------------------------------+
__ 14. Update JCL in Production Library
Ensure that the JCL for the regenerated jobs is moved
to the appropriate production library.
__ 15. Identify Component Files
Create a SAS PROC DATASETS job in the original_unit to
identify the MICS component's files in each timespan
(including any split timespans). 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 statement (and PROCLIB statement,
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 the next step of this checklist.
__ 16. Delete All Online Database Files
Delete all of the online database files for the
component in the original_unit, as follows:
__ Reference the output of the DATASETS job that was
executed previously in this checklist. Indicate
the component files that need to be deleted from
each timespan.
__ When all timespans have been reviewed, create a job
in the original_unit that deletes the files
associated with the component. Use the following
job as an example and code PROC DATASETS statements
for each timespan in which the component is active.
NOTE: If the component has an accounting interface,
also delete the component journal files in the
original_unit. For more information about the
Accounting Journal Files (ACTJxx), see the
Accounting and Chargeback User Guide, section
7.1.
//DATASETS EXEC MICSDBx
//SYSIN DD *
PROC DATASETS DDNAME=timespan MEMTYPE=DATA
NOWARN;
DELETE iiifff01-iiifffnn iiifff01-iiifffnn
iiifff01-iiifffnn iiifff01-iiifffnn
ACTJff01-ACTJffnn; (if required)
PROC DATASETS DDNAME=timespan MEMTYPE=DATA
NOWARN;
DELETE iiifff01-iiifffnn iiifff01-iiifffnn
iiifff01-iiifffnn iiifff01-iiifffnn;
where:
x is the database identifier of the
original_unit
timespan equals DETAIL, DAYS, WEEKS, MONTHS,
or YEARS (if active), and the DD
name of any split timespan (e.g.,
DETAIL2)
iiifff is the information area and file
identifier for the component that is
being moved
ff is the file identifier
nn is the highest cycle number of the
file
__ Add a valid JOB statement (and PROCLIB statement,
if required) to the JCL and submit the job. Ensure
that the job completes with a condition code of
zero.
__ 17. Edit CHECKPT DATA (Original Unit)
Edit prefix.MICS.CHECKPT.DATA in the original_unit.
Delete the lines that contain checkpoint information
for the component that is being moved. ADD the same
number of blank lines to the member.
__ 18. Suspend Operations
Suspend production operations for the unit database by
using the Operational Status and Tracking SUSPEND
command in MWF to deactivate production scheduling.
__ 19. Back Up Libraries (Original Unit)
Back up the original_unit's libraries (e.g., CNTL,
PARMS, USER.SOURCE, USER.LOAD) by submitting the
following job:
'prefix.MICS.CNTL(BACKUP)'
Ensure that the job completes with a condition code of
zero and that all timespans have been successfully
copied.
__ 20. Resume Operations
Resume normal operations in this unit. Reactivate
production processing in the original_unit.
