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

A.3 SPECIAL Database Execution Definitions

The components processed by a SPECIAL database may be varied
from run to run.  Also, the data selection or forcing of data
into the database may be varied from run to run.  This is
accomplished by user specifications in a parameter library
member called EXECDEF.

Parameters normally specified in EXECDEF are those which can
easily be varied from run to run, such as the selection of
management objective reports to be produced. Four statements
that are not allowed in the EXECDEF member of a regular
database unit are supported in a SPECIAL database.  These
are:

COMPONENTS  -  Specify the components that are to be treated
    by the current input processing run (DAILY job).

SELECT  -  Performs input data selection according to a
    window of time stamps.

FORCE  -  Forces data into the database (regardless of normal
    date/time duplicate data elimination criteria) according
    to a specified time stamp window.

ORGSYSID  -  Selects data from a specified system or systems,
    and automatically discards data from systems not listed.
    Note that the SYSID(s) specified here are the original
    (SMF) SYSIDs.

A sample prefix.MICS.PARMS(EXECDEF) is shown next.  The
statements in this parameter member that relate to special
database processing are indicated by "--->" in the margin.

    *
    * EXECUTION TIME DEFINITIONS
    *
    CREATE    EXCEPTIONFILES ALL
    REPORT    EXCEPTIONS     NONE
    REPORT    MBODAILY       ALL
    REPORT    MBOWEEKLY      ALL
    REPORT    MBOMONTHLY     ALL
    SCHEDULE  WEEKEND        NO
    INPUTLOGLIMIT 99
    TITLE     SPECIAL RUN
    TITLE     FOR OPERATIONS DEPARTMENT
    *
    * SPECIAL PROCESSING PARAMETERS
    * (ALLOWED ONLY FOR SPECIAL PROCESSING)
    *
--->COMPONENTS CIC IMS
--->SELECT     05AUG82:05:00:00.00   05AUG82:05:59:59.99
--->FORCE      05AUG82:05:00:00.00   05AUG82:05:59:59.99
--->ORGSYSIDS  1500

If necessary, statements in EXECDEF that apply to all
components are automatically adjusted to the special
database.  For example, if the user has

    REPORT    MBOMONTHLY     SMF RMF TSO
    ...
    COMPONENTS CIC IMS

coded for component selection, the executed components
conflict with the intended monthly management objective
report list.  In this case, no monthly management objective
reports would be produced.

Also, it may be appropriate to change the TITLE statement
periodically, certainly more often than for a regular
database.  Different backloading operations or ad hoc studies
would have the TITLE in each operational job's output.  An
accurate and descriptive TITLE aids in identifying the
configuration under which the run was made.  Note that it is
not always possible to tell the configuration under which the
run was made simply by the prefix of the database unit.

A detailed explanation of each of the EXECDEF statements for
SPECIAL databases is contained in the sections that follow.