6. Database Tailoring and Retrofitting Techniques › 6.1 Tailoring Guidelines
6.1 Tailoring Guidelines
The first step in tailoring your CA MICS system is to ensure
that you clearly understand your data center's data
requirements. Knowing your requirements, the following
questions and answers should help you plan your tailoring
strategy.
When should database tailoring be performed?
---------------------------------------------------------
o Use the product for at least six months to ensure that
you have enough experience to determine what kinds of
changes should be made to the database to achieve your
objectives.
If implementing compression is a consideration, one
month's data is sufficient if you use the Administrator
Utilities provided for analyzing and recommending
compression settings.
o If installing a new product requires a
disproportionately large amount of DASD space, such
that it may not be practical or even feasible to
install, evaluate the use of the DBSPLIT facility and
ultimately the database tailoring facility to reduce
the number of data elements and possibly files that are
to be maintained in the database.
Can a product be tailored differently in different
database units?
---------------------------------------------------------
o A product is generated at the database complex level
and therefore its files are identical in all database
units. You can tailor file compression by unit,
however, using the prefix.MICS.PARMS(COMPRESS) member.
What other dependencies must be considered when tailoring
the CA MICS database?
---------------------------------------------------------
o If a change is made that adds or deletes a file in any
of the three archiving systems (audit, weekly history,
or monthly history), you must regenerate the database
unit's operational jobs by running a JCLGEND in each
unit in which the product is installed.
o If compression is activated for a file by adding
COMPRESS statements to the cccGENIN member of
sharedprefix.MICS.GENLIB, run a COPYLIBU to add FILE
statements to prefix.MICS.PARMS(COMPRESS).
o If a change is made to the sort order of a file in the
WEEKS, MONTHS, or YEARS timespans (by changing the
timespan status definition on the NAME or NAMX
statement), retrofit the sequence change in the files
already present in the online and archive databases.
(Each requires a sort and summarization.) A component
generation (cccCGEN) is required to implement the
change.
o Review the use of elements before deactivating them
from the database. For example, if a data element is
marked inactive (deleted) and that data element is used
in a critical SAS statement (such as a BY statement) in
a dependent program, the SAS compilation will not
complete successfully. If the data element is
referenced in any other manner, the SAS Log will show
that the variable was not initialized, and dependent
elements, if any, may be incorrect.
o To add a data element to the database, define it to the
Component Generator (sharedprefix.MICS.GENLIB member
cccGENIN) and add source code to the DYcccFMT input
format routine in sharedprefix.MICS.SOURCE. Then edit
sharedprefix.MICS.SOURCE(#cccEXIT)'s USRFMT2 and
USRFMT3 macros to ensure that the source data used to
provide values to the new data element is available.
Evaluate any change in the generation control statements in
light of the information provided in the rest of this
chapter. For example, you may not be able to directly
activate the DETAIL timespan for files that do not normally
exist in the DETAIL timespan. Check the specific
instructions in the following sections for details, as well
as the modification documentation in specific product guides.
Read this chapter before performing any file tailoring.
File tailoring can be performed easily by following the
guidelines in this section. The approximate effort involved
for file tailoring is illustrated below.
Tailoring action Required operations
------------------------------- ----------------------------
To add, change, or delete a data element:
- The data element is not - Component generation
in the sequence key of - User modification to the
the file. component format routine
DYcccFMT
- Test/implement/check
- The data element is in - Component generation
the sequence key of the - User modification to the
file. component format routine
DYcccFMT
- Database retrofit for
modified key structure
- Test/implement/check
To add a file to an online
database timespan: - Component generation
- User modification to the
component format routine
DYcccFMT
- Test/implement/check
To delete a file from an online
database timespan: - Component generation
- Delete unused cycles
- Test/implement/check
To add or delete a file from - Component generation
archiving: - JCLGEND for WEEKLY,
MONTHLY, and GDGSGEN JCL
- Run GDGSGEN
- Test/implement/check
To compress or uncompress - Edit the COMPRESS member
a file's data: in prefix.MICS.PARMS
- Run CYCLEGEN
- Run BACKUP
- Run RESTORE