7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.1 Definition Statements (CICGENIN)
7.2.1 Definition Statements (CICGENIN)
Each CA MICS component has a member that defines component
generation statements in sharedprefix.MICS.GENLIB. The
member's name is cccGENIN, where ccc is the three-character
component identifier. For the CA MICS Analyzer Option for
CICS, this member is CICGENIN.
Chapter 4 of the System Modification Guide describes the
statements that comprise the GENIN members. Statements
specific to this component are described below.
THE OPTION STATEMENT
CICGENIN provides the OPTION statement to indicate which
groups of data elements are to be kept in the database. The
CA MICS Analyzer Option for CICS provides a default OPTION
statement that specifies that response distribution elements
such as count and percent distributions are kept and that
only data elements from the CMF data source are kept. You
should change the default definition to match your
organization's requirements.
Note: CICGENIN contains both uppercase and lowercase
characters. The keywords for the OPTION statement should be
entered in uppercase.
The statement format is:
OPTION keyword keyword keyword keyword keyword keyword
The valid keywords are:
CMF - Keep CMF data elements
MON - Keep ASG-TMON data elements
EPLDB2 - Keep OMEGAMON II DB2 data elements
RESP - Keep response distribution elements (RESPONSE
is also valid)
OMEGU - Keep OMEGAMON II user area data elements
(OMEGUSER is also valid)
DBCTL - Keep DB2 Data Base Control (DBCTL) data
elements
NOCMF - Do not keep CMF data elements
NOMON - Do not keep ASG-TMON data elements
NOEPLDB2 - Do not keep OMEGAMON II DB2 data elements
NORESP - Do not keep response distribution elements
(NORESPONSE is also valid)
NOOMEGU - Do not keep OMEGAMON II user area data elements
(NOOMEGUSER is also valid)
NODBCTL - Do not keep DB2 Data Base Control (DBCTL) data
elements (For new install, NODBCTL is the
default)
You must use the keyword CMF if you are processing type 110
look-alike records such as those produced by OMEGAMON II for
CICS.
You must specify one keyword for each data source. The
keywords can be specified in any order and are separated by
one or more blanks.
Each of the above keywords controls the activation of data
elements that are associated with a cluster code. The
following table describes the cluster codes used in the CA
MICS Analyzer Option for CICS.
CA MICS Analyzer Option for CICS Cluster Codes
Code Keyword Description
---- -------- --------------------------
09 MON ASG-TMON for CICS
11 CMF CMF
15 CMF MON CMF and ASG-TMON for CICS
16 CMF CMF
17 MON ASG-TMON for CICS
18 EPLDB2 OMEGAMON
19 MON ASG-TMON for CICS
20 RESPONSE Response distribution
21 OMEGU OMEGAMON
25 CMF MON CMF and MON DBCTL
26 CMF CMF DBCTL
29 MON MON DBCTL
Note: For CICS, because a data element can be derived from
multiple monitor data sources, each monitor option (CMF, MON)
may be associated with multiple cluster codes. For example,
if you specified OPTION CMF RESP NOMON NOEPLDB2, the data
elements with cluster codes 11, 15, 16, and 20 are activated,
while elements with cluster codes 9, 17, and 18 are
deactivated.
Examples:
The OPTION statement for data centers using only CMF as
input data source is:
OPTION CMF NOMON RESP NOOMEGU DBCTL
The OPTION statement for data centers using only ASG-TMON
as input data source is:
OPTION NOCMF MON RESP NOOMEGU DBCTL
The OPTION statement for data centers using CMF and ASG-TMON
as input data sources is:
OPTION CMF MON RESP NOOMEGU DBCTL
In addition to controlling the content of your database
through the OPTION statement, you can also manually activate
or deactivate data elements by modifying
sharedprefix.MICS.GENLIB(CICGENIN). The CA MICS Analyzer
Option for CICS provides data element definitions for most of
the data fields in the input records. However, a small
percentage of the data elements are shipped as inactive. You
may want to review the CICGENIN member to determine if any of
the inactive fields should be activated.
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.
Files that should not be compressed are:
- CICCDC, the CICS Dictionary file
- the CICCSY parallel files (CICGDP, CICGSM, CICCSM,
CICCSX, CICGLD, CICGTS, CICGTD, and CICGST)