1. Introduction › 1.1 Modification Philosophy › 1.1.2 Tailoring CA MICS to the User's Special Needs › 1.1.2.3 Adding User Components to the Database

1.1.2.3 Adding User Components to the Database

CA MICS products process data from the commonly used z/OS and
distributed system measurement data sources.  However, there
are many subsystems implemented at user sites that, while of
intense local interest, are not treated by CA MICS products.
This category of data sources may be included in your CA MICS
system by developing a CA MICS user component.

Chapter 7 of this manual describes the methods a user can
employ in writing a CA MICS component. There are many
advantages to implementing a user reporting system under the
CA MICS structure, within the existing CA MICS database
complex.  For one thing, CA MICS provides almost all of the
database manipulation and maintenance functions.  The user
does not have to code functions such as backup jobs,
scheduling subsystems, archiving programs, and online
database aging techniques.

Also, the CA MICS method of component generation requires
the user to generate the least possible code to develop the
component.  Several debugging aids are provided to make the
development process even easier.

The existing CA MICS operational framework includes full
checkpointing of the database, update run audit history
files, and a run status reporting mechanism.

Undertaking to write a CA MICS user component is not a
trivial matter.  However, the guidelines and checklists
contained in chapter 7 of this manual make the process much
more attractive than implementing a stand-alone system.