4. CA MICS Facilities › 4.3 User Exit Facilities › 4.3.2 Types of CA MICS Exits › 4.3.2.2 Standard File and Accounting Exits
4.3.2.2 Standard File and Accounting Exits
Exits that apply to only one file in a single CA MICS product
can be used to modify the contents of records on that file
immediately before the current observation is output.
Standard file exits can serve any purpose that could be
fulfilled at the individual file level. Some of the
possibilities are:
- Calculating values for new data elements that are to be
added to the file.
- Scaling data elements that are currently on the CA MICS
file in question according to some user algorithm.
- Performing the calculations necessary to implement an
installation algorithm.
These exits can be used to install a user-written accounting
subsystem into CA MICS.
Installing user code to apply to all database units in the
CA MICS database complex is a matter of adding the code
directly into the exit macro in the #cccEXIT member on
sharedprefix.MICS.SOURCE.
Installing user code to apply to a single database unit is a
matter of redefining the macro and adding the code directly
into the exit macro in the #cccEXIT member on
prefix.MICS.USER.SOURCE.
The exit described here resides on the CA MICS source code
library sharedprefix.MICS.SOURCE in several different
members, which are denoted by fff, a three-character file
identifier. A general description of the USRSfff exit and
its functions follows.
Exit Name: _USRSfff, where fff is a three-character file
identifier.
For example, the CA MICS Hardware and SCP
Analyzer (RMF) has an information area called the
Hardware Information Area (HAR). The CPU
Information File in the Hardware Information Area
is called HARCPU and exists in the CA MICS
database in timespans and cycles such as
DETAIL.HARCPU01. The standard file exit for this
file is _USRSCPU, which is located in the
#RMFEXIT member of sharedprefix.MICS.SOURCE.
Purpose: Perform calculations immediately prior to file
output.
Method: The macro is referenced in code that processes
input data immediately before the SAS OUTPUT
statement for the associated file. If the file
exists on the CA MICS database in the DAYS
timespan but not in the DETAIL timespan (such
as the CICCSU file), this exit is taken
immediately before what would have been the
DETAIL observation is summarized to the DAYS
level. The routines that reference these exit
macros are daily component format routines
(DYcccFMT).
Before invocation, all data elements on the file
have been valued by CA MICS. That is, any data
element generated to be on the DETAIL timespan
or that is summarized to the DAYS timespan of
the file can be referenced by the exit.
These exits are invoked in one place each. There
may be more than one such exit invoked in any
single SAS DATA statement, because some data
statements build more than one CA MICS file.
Usage These macros give you great flexibility in
Notes: changing the contents of CA MICS files. Such
changes may be very desirable at your
installation. However, modifications also
increase the degree of maintenance work you must
perform for CA MICS.
Coding these exits assumes more than just a brief
introduction to CA MICS. It would be a good idea
to study the code in the format routine from
which the exit will be invoked. Such items as
the choice of names for "temporary" program
variables can be absolutely critical to the
normal operation of the rest of the component's
format routine. Inappropriate choices of
variable names can destroy data elements in other
files, disturb the CA MICS checkpoint mechanism,
and generally delay CA MICS data availability.
Thorough testing is essential.
Invoked Locations: These macros are referenced in a single
location by a single component. See the
individual product guides for more information on
_USRSfff exits.
