7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.1 Generation Definition Statements (IMSGENIN)

7.2.1 Generation Definition Statements (IMSGENIN)

The IMS Analyzer's generation definition statement member
resides in sharedprefix.MICS.GENLIB(IMSGENIN).  You should
review the OPTION and COMPRESS statement definitions.

The OPTION Statement
--------------------

The OPTION statement defines which data element clusters are
included or excluded when generating the data element
contents.  You should change the definition to meet your
needs, as described below.

OPTION statement keywords for the IMS Analyzer are:

    CIMS/NOCIMS - BMC MAINVIEW for IMS Online data elements
    ILOG/NOILOG - IMS log data elements

You must specify one keyword from each set.

The recommended OPTION for IMS in an installation using BMC
MAINVIEW for IMS Online is:

    OPTION CIMS ILOG

The recommended OPTION for IMS in an installation that is not
using BMC MAINVIEW for IMS Online is:

    OPTION NOCIMS ILOG


    Note:  The IMSGENIN member contains uppercase and
           lowercase characters.  The keywords for the OPTION
           statement must be entered in uppercase.


The COMPRESS Statement
----------------------


The SAS system gives you the option to create variable-length
or fixed-length observations in a SAS data set.
Variable-length observations differ from fixed-length
observations in that the former are usually smaller because
the blank spaces used to pad fixed-length observations are
removed.
 
You instruct SAS to create variable length observations by
specifying the COMPRESS= option.  SAS data set compression
can be implemented for individual data sets or across the
entire SAS system by specifying COMPRESS= on either a DATA
statement (for the individual data set named on the DATA
statement) or an OPTIONS statement (for the entire system).
 
For more information on the COMPRESS= option, see the SAS
Institute documentation.


All files in the IMS Analyzer are candidates for compression.
Before compressing work files, be sure to read Section 2.1 of
this guide, which explains the potential impacts of
compressing work files.


Optional File for Event Collector Data
------------------------------------------

If you want to maintain database activity data as measured
by the BMC MAINVIEW for IMS Online Event Collector, you
should consider activating the Data Base Activity (IMSIDB)
file.

If you elect to activate this file, understand the following:

 o  This file is only populated by BMC MAINVIEW for IMS
    Online data.  Do not activate the file if you do not have
    the BMC MAINVIEW for IMS Online Event Collector active.

 o  A great number of observations will be written to this
    file.  The DETAIL timespan does not have to be active to
    produce a DAYS timespan.  If the DETAIL timespan is
    activated, each cycle on that timespan may be very
    large.

 o  Always test activating this file in an isolated
    environment BEFORE activating the file in your production
    IMS unit.

To activate the file in a timespan, see the instructions for
the general topic in the CA MICS System Modification Guide.
To activate the file in the DAYS timespan only, change the
file statement to:

  FILE IDB 00 1 N E N N N N N N Data Base Activity File

We do NOT recommend activating the DETAIL timespan due to
data volume.  If you want to keep IMSIDB file data from
DETAIL granularity, write the output to an independent SAS
data set as illustrated in the sample _USRXIDB exit in
Section 10.2.4 of this guide.