5. Maintenance › 5.11 Delete a Unit Database from a Complex
5.11 Delete a Unit Database from a Complex
If you need to transfer components that were installed in
this unit prior to its deletion, complete the "Moving CA MICS
Products to a Different Unit" checklists in section 5.9.
__ 1. Establish Time Frame
Establish a schedule and time frame for accomplishing
the deletion. If CA MICS Accounting and Chargeback is
installed in the unit, we strongly recommend that you
wait until monthly processing has been completed in
the unit before proceeding.
__ 2. Determine Reporting Affects
Determine how the removal of the unit will affect the
following reporting mechanisms:
o Shared/Private MICF inquiries
o MICF production reporting jobstreams
o JCL for batch reporting jobs
o Adhoc SAS reporting programs
Any references to the deleted unit database must be
removed from these reporting mechanisms.
Note: Existing shared and private inquiries and
standard applications also include those
affiliated with the Management Support
Application components.
__ 3. Alert All CA MICS Users
Alert all CA MICS users that you will be deleting the
unit database well in advance of the actual day and
inform them of the changes that need to be made. The
CA MICS System Administrator is responsible for the
changes to the Shared MICF inquiries and MICF
reporting jobstreams.
__ 4. Back Up 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.
__ 5. Edit DBTABLE
Edit sharedprefix.MICS.GENLIB(DBTABLE) as follows:
__ Delete the line for the unit database that you are
removing from the complex.
__ SAVE the changes that you have made to DBTABLE.
__ 6. (CONDITIONAL) Designate Primary Unit
Review the DATABASE statement in member
prefix.MICS.PARMS(JCLDEF) for the unit that you are
removing. If the DATABASE statement at the top of
this member contains the word "PRIMARY," then you must
designate one of your other unit databases as the new
primary unit in this step.
You have the option to install a new unit database to
become your new primary unit database; see section
3.8.4. If you choose this option, install the new
unit at this point, that is, before continuing in this
checklist. On the new unit's DATABASE statement,
specify "UNIT" as the database type at this time.
The primary unit manages the backup and restoration of
the following sharedprefix data sets:
sharedprefix.MICS.ISPTLIB
sharedprefix.MICS.SCREENS
sharedprefix.MICS.TABLES
sharedprefix.MICS.CAPACITY (if CAP installed)
Complete this step ONLY if you are deleting the
primary unit you need to designate an existing (that
is, installed and active) unit database as the new
primary.
Designate the new primary unit by completing the
following steps:
+----------------------------------------------------+
| Reference(s): Section 2.3.3.2.1 (JCLDEF) |
+----------------------------------------------------+
__ Delete the first line in DBTABLE, which should read
as follows:
*: d
where 'd' is the primary unit database identifier.
__ Delete the line that references the replacement
unit. That line will be regenerated in the next
step.
__ Designate a new primary unit by editing the
prefix.MICS.PARMS(JCLDEF) member of any remaining
production-level unit (i.e., contains the word
"UNIT" in the DATABASE statement). Do NOT
designate a SPECIAL or TEST unit as your new
primary unit. These unit types cannot support the
processing and data retention requirements of a
production-level unit. Change the word "UNIT" in
the DATABASE statement to "PRIMARY" and then SAVE
the JCLDEF member.
__ Edit prefix.MICS.PARMS(JCLGENU) in the new primary
unit. Replace the member with a line that reads:
BACKUP RESTORE
__ Submit prefix.MICS.CNTL(JCLGENU) in the new primary
unit to regenerate the BACKUP and RESTORE jobs.
The RSTRTBLS and RSTRTLIB jobs will also be
regenerated during this process.
Ensure that there are no error messages in MICSLOG
and that the last message is the normal termination
message, BAS10999.
__ 7. Activate the Removal of the Unit
Regenerate a jobstream at the complex-level to
activate the removal of the unit database as follows:
__ Edit sharedprefix.MICS.PARMS(JCLGENUC) and replace
the member with a line that reads:
JCLGENUC
__ Submit sharedprefix.MICS.CNTL(JCLGENUC) to
reconfigure CA MICS and to remove the unit.
Ensure that there are no error messages in the
MICSLOG and that the last message is the normal
termination message, BAS10999.
__ 8. Invoke MWF
Invoke the CA MICS Workstation Facility (MWF) and
perform the following steps. Note that your TSO
userid must be authorized to make changes in Options
2, 4, and 5 of the workstation.
__ Select option 5, MICS Administrator Facility
(MICF). Type the word DBCLEAN on the command line
and press ENTER.
__ The Database Table Clean panel will be presented.
CAREFULLY type an 'S' next to the unit that you
want to delete. Press ENTER. This command will
remove MWF references to the deleted unit.
__ Return to the MWF Primary options panel when the
DBCLEAN command has completed.
__ Verify that the unit was deleted. Type the word
CONFIG on the command line and press ENTER. The
CONFIG command will produce a list of active units
at your installation. Ensure that there are no
references to the deleted unit.
Note: If the unit you were trying to delete is
still listed, STOP. Contact Technical
Support for assistance.
__ Exit MWF.
__ 9. (CONDITIONAL) Determine if ARCHIVE is Active
Review the ARCHIVE statement in
prefix.MICS.PARMS(JCLDEF) member for the unit that you
are removing. If ARCHIVE YES is specified for either
the AUDIT, HISTW, or HISTM keywords then complete this
step.
__ Determine what will be done with the audit and
history archive files. If you do not want to
retain these tapes, uncatalog the following
unit-level data sets:
tapeprefix.MICS.AUDIT.iiifff.GnnnnV00
tapeprefix.MICS.HISTW.iiifff.GnnnnV00
tapeprefix.MICS.HISTM.iiifff.GnnnnV00
where 'iiifff' is each CA MICS information area
file that was selected for audit or history
archive. ISPF option 3.4 can be used to uncatalog
the tape files. You may also want to update your
tape management system to expire these tape files.
__ 10. Delete Unit-Level Data Sets
Delete the following unit-level data sets for the
unit if they exist:
prefix.MICS.ccc.DATA (DAYSMF files are PERMANENT)
prefix.MICS.CHECKPT.DATA
prefix.MICS.CNTL
prefix.MICS.DAYS
prefix.MICS.DAYSn (DBSPLIT)
prefix.MICS.DETAIL
prefix.MICS.DETAILn (DBSPLIT)
prefix.MICS.IMSSUS1 (IMS)
prefix.MICS.IMSSUS2 (IMS)
prefix.MICS.MODEL (allocated)
prefix.MICS.MONTHS
prefix.MICS.MONTHSn (DBSPLIT)
prefix.MICS.MUOLIB
prefix.MICS.PARMS
prefix.MICS.RESTART.CNTL
prefix.MICS.SPECIAL.SOURCE (SPECIAL DB)
prefix.MICS.USER.LOAD
prefix.MICS.USER.SOURCE
prefix.MICS.WEEKS
prefix.MICS.WEEKSn (DBSPLIT)
prefix.MICS.YEARS
prefix.MICS.YEARSn (DBSPLIT)
where 'ccc' is the component identifier and 'n'
represents a hexadecimal value from 0 to z.
__ 11. (CONDITIONAL) If Accounting and Chargeback Installed
If the CA MICS Accounting and Chargeback component was
installed in the unit that you are deleting, perform
the following steps; otherwise proceed to the next
step.
__ Delete all members in sharedprefix.MICS.ISPTLIB
with names ACTJffx, where ff is any journal file
identifier and x is the database identifier of the
original_unit.
__ Edit prefix.MICS.PARMS(JCLGENU) IN ONE OF YOUR
REMAINING UNITS. Replace the member with a line
that reads:
JCLGENU
__ Submit prefix.MICS.CNTL(JCLGENU) from the same
unit. Ensure that there are no error messages in
the MICSLOG and that the last message is the normal
termination message, BAS10999.
__ Determine what will be done with the daily and
monthly accounting audit tapes from this unit.
The data set names are:
tapeprefix.MICS.ACCT.DAY1.GnnnnV00
tapeprefix.MICS.ACCT.DAY2.GnnnnV00
tapeprefix.MICS.ACCT.MONTH.GnnnnV00
Even though they are not used in the chargeback
process, it may be necessary to retain these tapes
for audit purposes depending on your site's
business requirements. The DAY2 tape is a copy of
the last DAY1 tape so it should not be needed. The
latest generation of the DAY1 tape contains the
month-to-date charges for the month up until the
time the unit ceased operation; the latest
generation of this tape may need to be retained for
audit purposes. Each generation of the MONTH tape
contains charges for one accounting month. These
generations may also need to be retained for audit
purposes.
__ 12. (CONDITIONAL) Delete User PROCLIB
If a user PROCLIB existed for the deleted unit, it can
now be deleted. If a common PROCLIB is used, delete
the procedures for the deleted unit from the common
procedure library.
__ 13. Back Up 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.
