1. Introduction › 1.1 Modification Philosophy › 1.1.2 Tailoring CA MICS to the User's Special Needs › 1.1.2.4 System Modification Using Standard EXITs

1.1.2.4 System Modification Using Standard EXITs

There is a large number of standard exit points within the
CA MICS complex. These exit points exist for the sole purpose
of allowing the user to make effective changes to the CA MICS
processing logic without requiring that user to modify
CA MICS source code. While modification of source code is
possible, and is discussed in this manual, such modifications
reduce the release independence of the user's system
definition.

The points at which user exits are available can be
grouped into these categories:

    - Standard CA MICS exits. These exit routines are
      required for all CA MICS users, and are used to provide
      code that MUST be included for CA MICS user-dependent
      functions.  For example, these exits provide for the
      determination of cost center identifiers and the
      grouping of batch data into categories suitable for
      summarization.  These exits reside in the database
      complex or unit parameter libraries, as separate
      members in the library.  See the CA MICS Planning,
      Installation, Operation and Maintenance Guide for
      information on these standard exits.

    - File exits.  There is an exit in CA MICS that is taken
      before an observation is written to the database file.
      This type of exit exists for every file of every
      component in the CA MICS complex. It is possible to use
      these exits to do such things as implementing
      accounting algorithms or changing the values of
      CA MICS-calculated data elements in the files.

    - Operational exits.  There are several points within the
      CA MICS complex at which operational decisions are
      likely to need installation-dependent logic.  These
      points have been determined on the basis of experience
      at many CA MICS sites. Code which affects the criteria
      for input record selection and logic for unusual file
      manipulation may be implemented in these exits.

Chapter 4 of this manual describes the exit types noted
above, and gives guidelines for using them.