7. PARAMETERS › 7.3 Unit-Level Parameters › 7.3.4 IMS Processing Options (IMSOPS) › 7.3.4.2 OPTIONS Statement
7.3.4.2 OPTIONS Statement
The OPTIONS statement is required and contains information
that describes each IMS system the IMS Analyzer is to
process. Below is an overview of all required and optional
parameters associated with this statement.
+-----------------------------------------------------------+
| OPTIONS osysid imsid rel ddn int mon fp {optional parms } |
| {BMP | NOBMP } |
| {LDE | NOLDE } |
| {FSCHED | NOFSCHED } |
| {SQFE | NOSQFE } |
| {WFI(n) | NOWFI } |
| {FASTWFI | NOFASTWFI } |
| {FOLDUID | NOFOLDUID } |
| {IMSPLEX(xxxx) } |
| {USECPUOLD } |
| {+ } |
+-----------------------------------------------------------+
The following parameters are REQUIRED:
osysid = This is the 1-4 character original SYSID as
specified in prefix.MICS.PARMS(SYSID). It
identifies the computer system on which this IMS
system executed. The value of this identifier
must match an ORGSYSID defined in
prefix.MICS.PARMS(SYSID), but not all ORGSYSIDs in
the SYSID member are required to have associated
IMS systems. The IMS Analyzer ignores IMS log
data that is not defined through the OPTIONS and
monitor statements.
The IMS Analyzer AutoDetect Facility (ADF)
can provide for automatic detection of the
ORGSYSID parameter when the user is processing BMC
MAINVIEW for IMS Online transaction log data. By
specifying the ORGSYSID parameter value as ????
(4 question marks), the IMS Analyzer will extract
the actual ORGSYSID value from the BMC MAINVIEW
for IMS Online transaction log data. This
eliminates the need to modify the corresponding
OPTIONS statement and run an IMSPGEN in the event
the IMS region is relocated to a different
operating system image. If an IMS region is
relocated, the requirement still exists that the
ORGSYSID have a valid entry in the
prefix.MICS.PARMS(SYSID) member; however, no
changes would be required to the
prefix.MICS.PARMS(IMSOPS) member.
imsid = This value is used to uniquely identify an IMS
system among all other IMS systems defined to the
IMS Analyzer. The uniqueness of the definition is
obtained by the combination of ORGSYSID and IMSID.
That is, two IMS systems executing on two
different computers may have the same IMSID, but
the combination of the ORGSYSID and IMSID would be
unique (the ORGSYSIDs are unique). Two IMS
systems running on the same computer must have
unique IMSIDs if the ORGSYSID/IMSID combinations
are to be different. The value specified for
IMSID may be any 1-4 character identifier.
The IMS Analyzer AutoDetect Facility (ADF) can
provide for automatic detection of the IMSID
parameter whether you are processing BMC MAINVIEW
for IMS Online transaction log data or not. By
specifying the IMSID parameter value as ???? (4
question marks), the IMS Analyzer will extract the
ORGIMSID value from the BMC MAINVIEW for IMS
Online transaction log data or IMS log records.
The ORGIMSID extracted value is then assigned to
the IMSID data element. This eliminates the need
to modify the OPTIONS statement and run an IMSPGEN
in the event the IMS region ID is changed. If the
IMS region ID is changed and the user wants to
maintain the existing IMSID for database
continuity, the ORGIMSID can be mapped to the
previous logical IMSID by using the IMSALIAS
statement.
rel = IMS data collection record formats may change from
version to version of IMS. Specify the IMS version
number in the form x.x. Currently supported
versions are 6.1 through 13.1
The IMS Analyzer AutoDetect Facility (ADF) can
provide for automatic detection of the IMS release
parameter whether you are processing BMC MAINVIEW
for IMS Online transaction log data or not. By
specifying the IMS release parameter value as ???
(3 question marks), the IMS Analyzer will extract
the IMS release value from the BMC MAINVIEW for
IMS Online transaction log data or IMS log
records. This eliminates the need to modify the
OPTIONS statement and run an IMSPGEN when
upgrading IMS regions to a new release of IMS.
ddn = You must specify the source of the monitor data
for this IMS system. Specify:
ddname - The log data for this IMS system has been
recorded on a sequential file medium.
This ddname must match a ddname defined
in the INPUTIMS member of the
prefix.MICS.PARMS library used for JCL
generation, and must be unique among all
IMS systems defined (regardless of SMF
SYSID). IMSDUMMY is a ddname reserved
for internal use and cannot be coded on
any OPTIONS statement.
int = The default IMS checkpoint interval is the average
number of minutes between IMS system checkpoints.
The value specified here must be integer minutes:
60 or less. To find the value for your site,
divide 1440 (the number of minutes in 24 hours) by
the number of IMS system checkpoints taken per
day.
mon = You must specify the monitor that has collected
data for this IMS system. This parameter must be
of the following form:
IMF2 - BMC MAINVIEW for IMS Online is monitoring
this IMS system.
NOCIMS - BMC MAINVIEW for IMS Online is either not
present, or, if present and active, is to
be ignored. IMS data will be extracted
only from standard IMS log records.
Notes: If any OPTIONS statement specifies NOCIMS
and does not specify LDE, the IMSSUS1 and
IMSSUS2 DD statements will be required in
the DAY060 step of the DAILY job JCL.
You must regenerate the DAILY job JCL for
the DAY060 step after the IMSPGEN has been
run if any OPTIONS statements have been
included as specified in the preceding
condition.
fp = This parameter indicates whether Fastpath
transactions from this IMS system are to be
included in the CA MICS IMS database. Code NOFP
to exclude Fastpath database transaction
statistics, FP to include transactions performing
Fastpath database calls scheduled via the EMHB
method or standard message scheduler, and MM to
include all Fastpath database statistics for
transactions scheduled via the standard message
scheduling. Note that mixed mode statistics will
be included in the IMSISU and IMSIAU files, while
statistics for those transactions scheduled by the
expedited message handler will be included in the
IMS_IS and IMS_IA files.
Use the following table to determine this setting
based on type of message queuing used and type of
DB calls.
+-----------------+-------------------------------+-------+
| | Types of DB calls used | Code |
| Message queuing +----------------+--------------+ |
| is done via | Full Function | Fastpath | |
+----------------------+-------------------+--------------+
| EMH only | not supported | yes | FP |
+-----------------+----------------+--------------+-------+
| Normal only | yes | yes | MM |
+-----------------+----------------+--------------+-------+
| Both | yes | no | NOFP |
| +----------------+--------------+-------+
| | no | yes | MM |
| +----------------+--------------+-------+
| | yes | yes | MM |
+-----------------+----------------+--------------+-------+
The following parameters are NOT positional and
can be specified in any order. If a parameter
value is omitted, the default value will be used.
The following parameters are OPTIONAL:
BMP | NOBMP = This parameter indicates whether BMP
transactions in this system are to be
presummarized (collapsed) by the Log Data
Reduction programs. Code BMP to activate
presummarization only if the monitor
specified is NOCIMS. Code NOBMP to prevent
presummarization.
Coding NOBMP causes one transaction to be
processed for each message that a
message-driven BMP has executed. Specify BMP
to collapse or presummarize message-driven
BMP transactions, which summarize
message-driven BMP activity by the unique
combination of LTERM of the message
terminal, transaction code, PSB name, and
hour of day. Presummarizing such BMP
transactions improves the performance of the
IMS Analyzer's daily update.
DEFAULT: NOBMP
LDE | NOLDE = This parameter indicates if the input data
came from an LDE source. If a value of LDE
is specified, the IMS Analyzer assumes that
the data has already been processed through
the CA MICS IMS Log Data Extractor Option
(LDE), a separate option. The CA MICS IMS
Log Data Extractor Option Guide asks you to
code LDE on the IMSOPS OPTIONS statement as
part of the LDE installation procedure.
NOLDE may be specified on the OPTIONS
statement to indicate that the data has not
been processed through LDE; however, this is
not required since NOLDE is the default
setting.
DEFAULT: NOLDE
FSCHED | NOFSCHED = This parameter indicates whether
transaction records that are the result
of "False Schedules" are to be output
by the Log Data Reduction program.
Specifying FSCHED will result in the
output of False Schedule transactions
to DAY060 processing. These
transactions contain a CPU Time value
even though there were no messages
processed by the transaction.
Specifying NOFSCHED will prevent the
outputting of the False Schedule
transactions.
DEFAULT: FSCHED
SQFE | NOSQFE = This parameter indicates whether Shared
Queue "front-end" records are to be output
by the Log Data Reduction programs. These
records can be created when processing data
from an IMS Shared Queues environment. This
is a new transaction record type denoted by
the presence of an x'FE' in byte one of the
record. Specifying SQFE will result in the
output of front-end transactions to DAY060
processing. Specifying NOSQFE will prevent
the outputting of the front-end transaction
records.
DEFAULT: NOSQFE
WFI(n) | NOWFI = This parameter on the OPTIONS statement
indicates whether WFI AutoFlush will be
activated; omitting this parameter from
the IMSOPS member prevents WFI AutoFlush
processing. This is a local (region
specific) option that can be specified as
either of the following:
OPTIONS ... WFI
OPTIONS ... WFI(n)
where n = a value from 1 to 65535
The WFI option is used to activate WFI
AutoFlush processing. Adding an (n) after
this parameter allows you to artificially
lower the WFI AutoFlush horizon. For
example, assume that there are no other
"non-never ending" WFI transactions that
have a PROCLIM greater than 10,000. By
changing the AutoFlush Horizon to 10,000,
transactions will be identified as being
"never ending" at a much earlier point in
time during processing.
Note: Since these transactions are now
written to DAY060 more frequently, it may
be necessary to increase the space
requirements for the DAY060 WORK files.
DEFAULT: NOWFI
FASTWFI | NOFASTWFI = This parameter specifies whether the
immediate flushing of completed WFI
transactions will (FASTWFI) or will
not (NOFASTWFI) be enabled during
processing. The FASTWFI feature is
for the benefit of users that process
large numbers of never-ending WFI
transactions which can cause serious
virtual storage constraints.
DEFAULT: NOFASTWFI
FOLDUID | NOFOLDUID = This parameter specifies whether the
RACFUSID will (FOLDUID) or will not
(NOFOLDUID) be translated to upper
case characters.
DEFAULT: FOLDUID
IMSPLEX(xxxx) = This parameter in the OPTIONS statement is
used to provide the IMSplex Identification
Name for the IMS region being defined. The
value of this parameter can be used to
group logically related IMS data together.
Although the most common usage for this
value is to group IMS regions participating
in an IMSplex, any type of logical grouping
would be appropriate. The value supplied
by this parameter can be from 1 to 8
characters in length.
DEFAULT: None
USECPUOLD = This parameter forces DAY060 to read and use
the pre-IMS V10.1 CPU time from the non-IMF
transaction records. IMS V10.1 introduced the
Transaction Level Statistics (TLS) collection
to provide more accurate data for IMS
transactions, particularly for WFI
transactions. Prior to the TLS data, CPU time
was only captured when the STIMER= option was
set for IMS transactions. In addition, most
users did not specify the STIMER= option for
BMP type transactions which meant that no CPU
time was collected for BMP transactions.
The pre-IMS V10.1 CPU time was captured in
timer values (where 1 timer value equals
approximately 26 microseconds.) With the
introduction of the TLS records CPU time is now
measured from the start of a transaction to the
end of the transaction and is represented as a
TOD clock value. The result of this is that the
CPU time collection is much more granular and
more accurate. The one draw back is that
empirical observation shows the CPU time under
the new method tends to reflect higher CPU
times for transactions. Some users may want to
continue utilizing the old CPU time collection
method which can be accomplished by specifying
the USEOLDCPU parameter on the OPTION statement
for an IMS region.
DEFAULT: None
+ = Use the plus sign (+) as the last parameter on an
OPTIONS statement set, in order to continue parameters
onto successive input lines. The continuation
character MUST be the last entry on a statement line.
As many continuation lines can be specified as
necessary.
Note: The continuation character may NOT be used to
split and continue an individual parameter. All
parameters prior to the continuation character must be
completely specified.
DEFAULT: None
Copyright © 2014 CA.
All rights reserved.
|
|