|
|
|
At times, additional system customizing is needed to tailor
CA MICS to your installation. Many user exit points are
provided within CA MICS. Each of these points corresponds to
a position in the CA MICS logic where user modification:
o Is likely to occur, based on customer experience with
the product.
o Presents only a slight possibility of compromising
CA MICS database or operational integrity.
o Is relatively easy to document and understand.
Using the CA MICS exit facilities to augment CA MICS
processing logic is the safest method of system modification.
Generally, the CA MICS System Administrator has four levels
or methods by which CA MICS can be augmented, changed, and
enhanced:
o CA MICS Standard Option and Parameter Definitions
The diverse installation and definition options
provide most users with adequate provisions for
customizing CA MICS.
o Modification Through User Exits
Often, installation-dependent requirements are not
adequately addressed through the standard options and
parameters. In these cases, you can use one or more
of the user exits provided with CA MICS to insert
user-written routines that satisfy the requirements.
o Extension Through User-Written Components
Although most users do not at first consider this as a
way of modifying CA MICS, the development of
user-written products may be the most advantageous way
of addressing the need to modify a standard CA MICS
product. For example, many times it may be better to
write a user product to handle additional SMF data
than to attempt to modify the logic of the MVS Batch
and Operations Analyzer.
o System Code Modification
Finally, if all else fails, you may be able to satisfy
your installation's requirements by implementing a
source code change.
This chapter explains the user exits that are provided with
the TSO Analyzer. You must carefully explore whether it is
necessary to develop a user exit routine. You should first
ensure that the requirement cannot be satisfied through one
of the standard options or definitions. To help you decide
which process to use, contact the CA MICS Product Support
Group.
BEFORE ATTEMPTING TO ACTIVATE AN EXIT, you should read and
fully understand the information contained in Section 4.3 of
the CA MICS System Modification Guide, User Exit Facilities.
The following material is intended to supplement, not
replace, that discussion.
The design, coding, testing, and implementation of CA MICS
user exit routines should be approached with caution because
errors may result that can corrupt the data. You should
meticulously define and validate the exit routines to ensure
that the system integrity and performance will not be
adversely affected.
The following sections identify the user exits available for
TSO Analyzer processing, provide a general overview of
product processing logic, and describe in detail each of the
user exits.
This section contains the following topics:
10.3 File and Data Element Customization
10.4 Change the Number of Work Files for DAY010
10.5 Enable Internal Step Restart
10.6 Implement Incremental Update
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |