7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.4 Analyzer Definition Statements (SMFGENIN)
7.2.4 Analyzer Definition Statements (SMFGENIN)
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. The Batch and Operations generation
definition member is SMFGENIN.
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
The OPTION statement indicates which groups of data elements
are to be kept in the database. Check the default
definition and change it as appropriate to meet your needs.
Note: The SMFGENIN member contains uppercase and lowercase
characters. The keywords for the OPTION statement should be
entered in uppercase.
The statement format is:
OPTION keyword keyword ...
where the valid keywords are:
JES2/NOJES2 - JES2 data elements
JES3/NOJES3 - JES3 data elements
DVCT/NODVCT - Derived device count data elements
ALC /NOALC - JES3 allocation count data elements
APPC/NOAPPC - APPC/MVS Transaction Program activity data
elements
OE /NOOE - UNIX Systems Services (formerly Open
Edition/MVS) data elements
Keywords are described in detail below. You must specify one
keyword from each pair. The keywords can be specified in any
order and are separated by one or more blanks.
EXAMPLES
The recommended OPTION for SMF in a JES2 shop is:
OPTION JES2 NOJES3 NODVCT NONJE NOAPPC
The recommended OPTION for SMF in a JES3 shop is:
OPTION NOJES2 JES3 NODVCT NONJE ALC
KEYWORD DESCRIPTIONS
o JES2/NOJES2 keyword (Data Element Cluster 02)
JES3/NOJES3 keyword (Data Element Cluster 03)
The JES2 and JES3 keywords specify whether fields that
hold JES2-specific data and/or JES3-specific data
should be kept in the records of the BATJOB, BAT_JS,
and BATSPL files. These options were added to save
space in the database, especially for users of JES2.
They can also prevent use of data elements that are
not meaningful in your environment.
Depending on the type of JES that you run, you should
specify JES2 and NOJES3, or NOJES2 and JES3. You will
only specify both JES2 and JES3 in the unusual
circumstance that you are running data from both JES2
and JES3 systems into the same CA MICS update run.
Note that the presence of fields derived from the type
25 (JES3 Main Device Setup) record in files of the
Batch Information Area is controlled by the JES3/NOJES3
keyword. See the description of the ALC/NOALC keyword
below.
o DVCT/NODVCT Keyword (Data Element Cluster 06)
The DVCT option specifies whether to calculate and
maintain I/O device allocation counts for DASD,
Magnetic Tape, VIO, Communications, and Unit Record
devices. Due to the large counters that must be
maintained for each of these classes (as well as a
total value), a significant amount of DASD storage
space is required to carry these fields in the
database.
Specify DVCT to include these fields in the database,
or NODVCT to have them excluded. This option allows
you to delete these data elements from the step-level
(BATPGM, BAT_TS, BAT_ST, BAT_TP, BAT_OE, BAT_SA) and
job-level (BATJOB, BAT_JS) files if you do not have a
requirement for them.
o ALC/NOALC Keyword (Data Element Cluster 07)
If the JES3 option is selected, the information from
the JES3 Device Allocation Records (type 25) will be
included in the BATJOB file of the database. Specify
ALC to cause these fields to exist in the database, or
NOALC to have them excluded. This data may be very
useful in the analysis of bottlenecks in setup
processing.
Note that if the Device Allocation data is used, it
will cause a significant increase in the amount of
space required for the BATJOB files.
IMPORTANT! Note that if option NOJES3 is selected,
data elements controlled by ALC/NOALC option will be
deactivated even though ALC is specified.
o APPC/NOAPPC Keyword (Data Element Cluster 09)
If the APPC option is selected, the data elements that
quantify APPC/MVS Transaction Program activity are
included in both the step-level (BATPGM, BAT_TS,
BAT_ST, BAT_TP, BAT_OE, BAT_SA) and job-level (BATJOB,
BAT_JS) files.
Select NOAPPC to exclude the APPC/MVS Transaction file
data elements.
Specifying the APPC keyword results in a significant
increase in the amount of space required for the Batch
Information Area files named above.
o OE/NOOE Keyword (Data Element Cluster 10)
If the OE option is selected, the data elements that
quantify UNIX System Services (formerly Open
Edition/MVS) activity are included in both the step-
level (BATPGM, BAT_TS, BAT_ST, BAT_TP, BAT_OE, BAT_SA)
and job-level (BATJOB, BAT_JS) files. The data
elements activated with the OE option are primarily
associated with Hierarchical File System (HFS)
activity.
Specifying the OE keyword results in a significant
increase in the amount of space required for the Batch
Information Area files named above.
Note: Elements that are designated as "cluster code" elements
have a common data source. For the Batch and Operations
Analyzer, the cluster codes are as follows:
Code Keyword Description
---- ------- -----------
02 JES2 JES 2
03 JES3 JES 3
06 DVCT Device allocation counts
07 ALC JES3 device alloc. stats
09 APPC APPC elements
10 OE Open Edition/MVS elements
If you want to change the current designation, modify
the OPTION statement in
sharedprefix.MICS.GENLIB(SMFGENIN) and run
sharedprefix.MICS.CNTL(SMFCGEN).
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.
