7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.2 CICS Processing Options (CICOPS) › 7.3.2.1 CICOPTS Statement
7.3.2.1 CICOPTS Statement
The CICOPTS statement identifies a CICS region whose data
should be processed by the CA MICS Analyzer Option for CICS.
One CICOPTS statement is required for each CICS region. Any
region found in input that is not defined by a CICOPTS
statement is excluded during input processing.
If the same CICS region can be executed on multiple systems,
use the generic SYSID feature to define the regions using a
single CICOPTS statement. Otherwise, you must specify one
CICOPTS statement for each unique combination of CICS region
ID and SMF system ID. For example, if CICSPROD can be run on
either SYSA or SYSB and you do not use generic SYSID support,
you must define two CICOPTS statements: one for CICSPROD on
SYSA and another for CICSPROD on SYSB. Details on generic
SYSID support are given below in the discussion of the
ORGSYSID parameter.
The CICOPTS statement format is:
CICOPTS orgsysid cicsid ddname mon gmt-ofs applid_or_sysidnt
int selcode
Note: The parameters are positional and are separated by one
or more blanks.
where:
orgsysid = Original system ID. This is the one- to four-
character SMF system identification. This
identifies the system on which this CICS system
is executed. The value of this identifier must
match an ORGSYSID value defined in
prefix.MICS.PARMS(SYSID).
A generic SYSID is defined as four question
marks (????). By specifying a value of ????, the
actual SMF system ID is obtained from the input
data. This option cannot be used with CMF
journal data, which does not contain the SMF
system ID. The SMF system ID obtained from the
input data must match an ORGSYSID defined by
prefix.MICS.PARMS(SYSID). By using the generic
SYSID feature, you can use one CICOPTS statement
to associate a CICS region with multiple SMF
system ID values.
cicsid = One- to four-byte CICS identifier that you assign
to identify a CICS region to CA MICS. The CICSID
must start with a letter. It may contain
letters, digits, and underscores. Special
characters are not allowed.
CA MICS combines CICSID and ORGSYSID (SMF system
ID) to uniquely identify the CICS region. That
is, two CICS regions executing on two different
systems may have the same CICS ID, because the
combination of ORGSYSID and CICSID would be
unique. (The SMF systems are different.) Two
CICS regions running on the same system must have
different CICSIDs to ensure the uniqueness of the
ORGSYSID/CICSID combination.
Note that the value chosen for CICSID cannot be
the same as a value chosen for CTGID in a GATEWAY
APPLID statement.
The maximum number of system, subsystem, and
combined entries cannot exceed the limit of the
prefix.MICS.CHECKPT.DATA data set. The default
maximum number of entries is 100. This number is
adequate for most data centers; however you can
reconfigure a unit's checkpoint size to allow a
maximum of 1000 entries.
Note: For more information about the checkpoint
file size and changing the default, see Section
2.3.2.4 of the PIOM, Site Characteristics (SITE).
ddname = Input ddname. This parameter specifies the
ddname from which the CA MICS Analyzer Option for
CICS is to read the input data. Values for this
parameter must be either SMF, MON, TCE or a one-
to eight-byte ddname. The names INPUTSMF and
INPUTMON are both reserved and cannot be
specified on the CICOPTS statement.
SMF - The measurement data for this CICS region
is found on the SMF log. If you specify
SMF here, then you should modify
prefix.MICS.PARMS(INPUTSMF) and specify the
JCL for the SMF data set under the ddname
INPUTSMF. Multiple data sets can be
concatenated under the ddname INPUTSMF.
Notes:
1. If you specify SMF for this parameter,
you should specify SMFRECORDING CIC
in prefix.MICS.PARMS(JCLDEF).
2. Normally, the INPUTCIC member of the
prefix.MICS.PARMS library should not
contain any JCL with the ddname
INPUTSMF. However, if you have
modified CA MICS to remove the DAYSMF
step, you can code the ddname INPUTSMF
in prefix.MICS.PARMS(INPUTCIC) and
remove the SMFRECORDING CIC statement
from prefix.MICS.PARMS(JCLDEF).
3. Do not specify SMF for this parameter
if you are using ASG-TMON since it does
not write to SMF.
4. Specify SMF for this parameter if the
input data contains CMF type 110 look-
alike records that are written to SMF,
such as those created by OMEGAMON II
for CICS.
MON - The measurement data is from ASG-TMON
release 7.1 or higher. If you specify MON
here, then you must modify
prefix.MICS.PARMS(INPUTCIC) and specify JCL
for the input data under the ddname
INPUTMON. Multiple data sets can be
concatenated under the ddname INPUTMON.
TCE - The measurement data is from ASG-TMON
release 2.0 or higher. If you specify TCE
here, then you must modify
prefix.MICS.PARMS(INPUTCIC) and specify JCL
for the input data under the ddname
INPUTTCE. Multiple data sets can be
concatenated under the ddname INPUTTCE.
ddname - The measurement data is either written
on a data set other than the SMF log, such
as CMF journal. You must modify
prefix.MICS.PARMS(INPUTCIC) and specify JCL
for the input data set under this ddname.
The names INPUTSMF and INPUTMON and
INPUTTCE are reserved and cannot be used
here.
Notes:
1. You may code the same ddname on
multiple CICOPTS statements to specify
that data for multiple regions is read
from the same input. You must code the
JCL for this ddname in
prefix.MICS.PARMS(INPUTCIC). Multiple
data sets can be concatenated under the
same ddname.
2. You may define each CICS region under
a separate ddname. This method
requires a unique ddname for each
region. It is not normally used unless
you want to specify NULL for the CICS
APPLID or system identification. More
details on NULL APPLID are given below.
mon CICS monitor identification. This parameter
specifies the CICS monitor that collected data
for this CICS system. This parameter must be one
of the following:
CMF - The data is collected by the CICS
Monitoring Facility (CMF) or other CICS
monitors that produce CMF type 110
look-alike records.
MON - The data is collected by ASG-TMON.
TCE - The data is collected by ASG-TMON 2.0+
gmt-ofs Time offset from Greenwich Mean Time. For
ASG-TMON, specify 0. For CMF input at CICS/ESA
release 4.1 and higher, specify 0. Otherwise,
specify the offset (time difference) from
Greenwich Mean Time (GMT) as recorded at
Greenwich, Great Britain. Note that the GMT
offset, even if specified as non-zero, is ignored
for all CICS systems that are V4.1 or later.
If your systems are set to local time instead of
GMT, specify 0. The MVS specification for this
offset is found in SYS1.PARMLIB(CLOCKxx). If
this member is empty or does not exist, your
system is running at local time.
If your system is running at GMT time and your
CMF input is pre-CICS/ESA 4.1, then you must
specify the GMT offset to adjust the CMF
transaction timestamps from GMT to local time.
The GMT offset must be specified in whole hours
ranging from 13 to -13. Since CA MICS subtracts
the GMT offset from CMF timestamps, you should
specify a positive value for North American
countries and a negative value for European
countries east of Great Britain. For example,
you should specify 5 for gmt-ofs if you are in
the United States at Eastern Standard time, since
you are 5 hours behind GMT time. (GMT time is 11
a.m.; local time is 6 a.m.)
Note: This offset is affected by daylight savings
time. In order for the database to remain
accurate, you must update this parameter and run
the CICPGEN job if you change to or from daylight
savings time.
applid VTAM application identifier or the CICS system
or identifier (SYSIDNT).
sysidnt
For CMF and ASG-TMON/ESA (TCE) 2.0 and higher,
you should specify the VTAM application
identifier (APPLID) as defined in the CICS system
initialization table DFHSIT or the CICS terminal
control table DFHTCT.
An exception to the rule is when your input data
contains data for only one CICS region. In this
case, you can use the word NULL in place of the
APPLID on each CICOPTS statement that references
a unique ddname.
Note: If you do not specify NULL and the APPLID
is incorrect, the data will be excluded.
For ASG-TMON, you should specify the four-byte
CICS system identification (SYSIDNT) as defined
in the CICS system initialization table DFHSIT or
the CICS terminal control table DFHTCT.
An exception to the rule is when your input data
contains data for only one CICS region. In this
case, you can use the word NULL in place of the
SYSIDNT on each CICOPTS statement that references
a unique ddname.
Note: If you do not specify NULL and the SYSIDNT
is incorrect, the data will be excluded.
You may need to ask your CICS system programmer
for assistance in determining the correct APPLID
or SYSIDNT for your CICS regions.
int = Default CICS system sample interval. This
parameter is not used for CMF (3.1 and higher) or
ASG-TMON. Specify two questions marks (??) for
any of these input sources. For CMF 2.1 and
prior releases, specify either the number of
minutes for the system recording interval (see
FREQ option in the CICS monitoring control table
DFHMCT), or two question marks (??) if you do not
know what the recording interval is.
For CMF 2.1, the two question marks cause the CA
MICS Analyzer Option for CICS to derive duration
from the input data without validating it against
the expected interval value specified here.
selcode = Optional parameter to selectively input CMF
accounting and exception class data. Its values
are 0, 2, 4, or 6, which mean the following:
0 - Do not input accounting and exception data.
2 - Input accounting data (CMF 2.1).
4 - Input exception data.
6 - Input both accounting and exception data.
The default value is 0. Do not code this
parameter for ASG-TMON input.
CMF performance class data is always processed by
the CA MICS Analyzer Option for CICS. This
parameter does not affect CMF performance class
data.
If you want to input accounting or exception
class data, you are responsible for coding the
USRSCMF user exit to output the data to the
appropriate CICS files.
Examples:
Sample CICOPTS statements are shown below.
1. CICOPTS ???? CIC1 SMF CMF 0 CICSPROD ??
CICOPTS ???? CIC2 SMF CMF 0 CICSTEST ??
CICOPTS ???? CIM1 MON MON 0 CIMP ??
CICOPTS S090 CIM2 MON MON 0 CIMT ??
CICOPTS ???? D40X TCE TCE 0 D40XCICS ??
The above statements define five CICS regions. The first
two regions input CMF data (including CMF look-alike data
produced by OMEGAMON for CICS/ESA) written to SMF, and
the next two input data from ASG-TMON. Regions CIC1 and
CIC2 are defined using the generic SYSID feature. The
APPLIDs are required for each region, since they are
concatenated to the same ddname (in JCL the ddname is
INPUTSMF).
Regions CIM1 and CIM2 are from ASG-TMON. CIM1 is defined
using the generic SYSID feature while CIM2 is not.
Note: For each of the ASG-TMON regions, a four-byte
system identification is specified in place of the
eight-byte APPLID.
Region D40X is from ASG-TMON for CICS/ESA 2.0. D40X is
defined using the generic SYSID feature.
Note: For each TCE region, the eight-byte VTAM
application ID is used.
2. CICOPTS R033 CICP INCMFA CMF 5 NULL ??
CICOPTS R033 CICT INCMFB CMF 5 NULL ??
The above statements define two CICS regions with an SMF
system ID of R033. Both regions are recording to CICS
journal and are input to CA MICS through separate ddnames
(INCMFA and INCMFB). The APPLIDs are both NULL, since
the ddnames are unique. The interval value is ??, which
means the CA MICS Analyzer Option for CICS will not
validate the calculated duration value.
A complete CICOPS member follows.
Sample CICOPS member
--------------------
RESP 1 2 5 10 15 30 60
TRANSLATE PF1 -----PF1
WORK 3
CICOPTS ???? CIC1 SMF CMF 0 CICSPROD ??
CICOPTS ???? CIC2 SMF CMF 0 CICSTEST ??
CICOPTS R033 CICP INCMFA CMF 5 NULL ??
CICOPTS R032 CICT INCMFB CMF 5 NULL ??
CICOPTS ???? CIMN MON MON 0 CIMN ??
CICOPTS S090 CITX INMON1 MON 0 CITX ??
CICOPTS S084 CITX INMON1 MON 0 CITX ??
CICOPTS ???? ROCK TCE TCE 0 ROCKVILL ??
GATEWAY ACTIVE
GATEWAY APPLID CTGPROD1 TGP1
GATEWAY APPLID CTGPROD2 TGP2
