2. System Overview › 2.2 CA MICS Naming Conventions › 2.2.2 SOURCE Modules

2.2.2 SOURCE Modules

The CA MICS SOURCE library contains the SAS logic executed
by CA MICS. This library is used at execution time, when
executing any CA MICS process. SAS modifications to this
library take effect with the execution of the next job that
uses the module.

The modules in this library are sequenced in statement
columns 73-80.  It is necessary for distributed sequence
numbers to remain intact for future CA MICS standard
maintenance.

Members in the CA MICS SOURCE library are generally named
according the following conventions.

    $cccxxxx - contains SAS macros or logic to relate to the
 or #cccxxxx   'ccc' component's execution in all database
               units.

    $xxxxxxx - contains generic SAS macros that apply to all
 or #xxxxxxx   CA MICS components in all database units.

    #ffftSUM - contains SAS code that creates specific time
               span summarization of a CA MICS file, where
               "t" is D for the DAYS time span, W for the
               WEEKS time span, M for the MONTHS time span,
               and Y for the YEARS time span.

    #DBMccc  - contains SAS code that produces database
               models for specific components.

    xxxxxxxx - contains general purpose CA MICS SAS logic.
               The name of the member is usually an
               abbreviation of the module's function.  One
               example is "CHECK", the routine that reads the
               CA MICS daily update checkpoint file and
               abends the update step if the required
               predecessor step was not the last step run.

    xxxxxGEN - contains CA MICS SAS logic which is executed
               in a parameter generation process.

    GENxxxxx - contains CA MICS SAS logic which is executed
               in a CA MICS Component Generator process.

    cccxxxxx - contains support logic for a specific CA MICS
               component.

    ttcccxxx - contains source code for component modules
               that are executed in CA MICS operational jobs.
               These modules are named according to the
               job in which they are used, where the 'tt'
               part of the name takes the values:

               DY - module is used in the DAILY job
               WK - module is used in the WEEKLY job
               MN - module is used in the MONTHLY job
               YR - module is used in the YEARLY job

Legend:
   ccc      - a component identifier
   fff      - a file identifier
   xxx to
   xxxxxxxx - some label describing the function of the
              module.