Appendix A. Special CA MICS Processing › A.3 SPECIAL Database Execution Definitions › A.3.1 Execution Components List

A.3.1 Execution Components List

The components processed by a SPECIAL database may be varied
from run to run.  This is accomplished by user specification
of the COMPONENTS statement in the SPECIAL database unit's
parameter library member EXECDEF.

Only one COMPONENTS statement is allowed in EXECDEF.  The
components listed on the statement must have been defined as
generated into the database unit, by the COMPONENTS
statement in prefix.MICS.PARMS(JCLDEF).  For example,

prefix.MICS.PARMS(JCLDEF):
    ...
    COMPONENTS TSO SMF RMF CIC IMS

prefix.MICS.PARMS(EXECDEF):
    ...
    COMPONENTS CIC IMS

is allowed.  The execution components are the CICS and IMS
components, and they have been used from the JCLDEF member
to create the SPECIAL database unit's JCL by the JCLGEN
process.  However,

prefix.MICS.PARMS(JCLDEF):
    ...
    COMPONENTS TSO SMF RMF CIC IMS

prefix.MICS.PARMS(EXECDEF):
    ...
    COMPONENTS NPA

is not allowed, and will cause an execution time message with
an abnormal termination of the step in which the
inconsistency was found.  The execution component NPA has not
been used from the JCLDEF member to create the SPECIAL
database unit's JCL by the JCLGEN process.

The effect of limiting execution components on database
unit DAILY update run time and logic is dramatic.  If the
backload or ad hoc study needs only a few components, only
those components need be processed.  DAILY update routines,
exception processing, file aging, and management objective
report modules for components not selected are not executed.