Determining the values for the monitoring options in IBM Z OMEGAMON for CICS

Enables you to include or exclude terminal I/O and/or IRC wait time in calculating the total response times for conversational transactions. This value enables MRO users to more completely isolate total transaction response times from I/O-related wait time.

CONVERSE_TIME accepts one or two parameters. The default values for the parameters are indicated.

IOWAIT

Specifies that CICS monitoring include the time that conversational tasks wait for terminal input when reporting the total response time for that task.

NOIOWAIT

Removes the I/O wait time from the transaction response time, including output wait time.

IRWAIT

Specifies that CICS monitoring include the time that tasks wait for IRC-link-related processing.

NOIRWAIT

Removes the IRC wait time from the transaction response time.

Specifies whether IBM Z OMEGAMON for CICS will purge conversational tasks waiting on terminal I/O when a non-immediate shutdown of CICS is performed. KOCOME00 must be present in the PLT as a shutdown entry.

Possible values are:

PURGE

Causes IBM Z OMEGAMON for CICS to purge conversational tasks waiting on terminal I/O when a non-immediate shutdown of CICS is performed. KOCOME00 must be present in the PLT as a shutdown entry.

NOPURGE

Does not purge any tasks

OPER

Indicates that the console operator specifies PURGE or NOPURGE in response to a WTO.

You can control the purging of tasks during CICS shutdown through the CICS Shutdown Purge Option of the IBM Z OMEGAMON for CICS Classic (3270) interface (fastpath O.Q).

Specifies whether or not internal bottleneck collection starts automatically.

Determines whether or not the MAXR exception is tripped when CPU consumption exceeds the MAXCPU threshold. The MAXR exception takes effect only if you use MAXCPU to specify a CPU consumption threshold greater than 0. In addition, CICS version 3.x users must specify CPU=YES in the MCT to instruct CICS to monitor CPU consumption.

Specifies whether the DB2® data collector starts up automatically. DB2 collector accumulates elapsed times and counts of DB2 commands for each CICS transaction.

If you specify NOAUTO, you can dynamically start and stop DB2 collection through the Control Database Collectors panel of the OMEGAMON for CICS (3270) interface (fastpath O.P).

Specifies whether the DL/I data collector starts automatically. The DL/I collector accumulates elapsed times and counts of DL/I commands for each CICS transaction.

Specifying AUTO or NOAUTO enables the XDLIPRE and XDLIPOST global user exits. You can dynamically start and stop DL/I collection through the Control Database Collectors panel of the OMEGAMON for CICS (3270) interface (fastpath O.P).

If you specify NO, however, you cannot activate DL/I collection dynamically.

Specifies whether the interval record collector starts automatically.

You can start the interval record collector through the Control Interval Recording Collector panel of the OMEGAMON for CICS (3270) interface (fastpath O.K).

Specifies whether the task history collector starts up automatically.

You can start the task history collector through the Start Online Historical Transaction Viewing Collector panel in the OMEGAMON for CICS (3270) interface (fastpath O.F).

Specifies whether OMEGAMON for CICS automatically monitors tasks for resource limiting once it is initialized.

You can start resource limiting through the START RESOURCE LIMITING panel of the OMEGAMON for CICS (3270) interface (fastpath O.R).

Specifies the destination for RLIM messages OC8902 and OC8903. Following is a list of possible resource message destination values:

TDQ

Specifies that RLIM messages OC8902 and OC8903 are only written to transient data destination CSSL.

LOG

Specifies that RLIM messages OC8902 and OC8903 are written to the System Console. No messages will be written to transient data.

TDL

Specifies that RLIM messages OC8902 and OC8903 are written to the transient data destination CSSL and the System Console.

(LOG,WARN)

Specifies that RLIM message OC8902 is written to the System Console. No messages will be written to the transient data destination CSSL.

(TDL,WARN)

Specifies that RLIM messages OC8902 and OC8903 are written to the transient data destination CSSL. RLIM message OC8902 is also written to the System Console.

The current settings may be viewed on the OMEGAMON for CICS (3270) system's RESOURCE LIMITING STATUS panel (fastpath O.T).

This parameter allows you to use the WARN thresholds specified in Resource Limiting to alert you to any system tasks which exceed the WARN threshold. It also allows you to KILL tasks using IBM-provided programs, these might include CEMT or CICS mirror transactions. CICS transaction manager determines which transactions are system tasks.

Specifies whether the CANCEL option is used by RLIM when KILLing a transaction

Specifies whether transactions that are warned by RLIM will have Application Trace activated for the task automatically

Specifies whether OMEGAMON for CICS will be able to record Application Trace for transactions running in CICS.

You can enable Application Trace through the Application Trace Facility Status panel of the OMEGAMON for CICS (3270) interface (fastpath O.W).

Specifies whether global user exits XFCFRIN and XFCFROUT will be initialized. These exits enable OMEGAMON for CICS to collect file level data for transactions which access VSAM files.

Specifies whether the response time collector starts up automatically.

You can start the response time collector during a session using the START RESPONSE TIME MONITOR panel of the OMEGAMON for CICS (3270) interface (fastpath O.A).

Specifies whether, after the OMEGAMON for CICS address space is restarted, OMEGAMON for CICS is not restarted in the CICS region

Specifies whether the Transaction Tracking API will be initialized when the OMEGAMON for CICSaddress space is started.

Specifies (in tenths of a second) the sample interval for internal bottleneck collection (1-99).

Specifies the maximum number of variable buckets that internal bottleneck collection can allocate. The value can range from 0-32767. Whenever the allocated storage overflows, the Bottlenecks panel in the OMEGAMON for CICS (3270) interface displays a new line that shows the wait reason sub-ID of *OVERFLW* and also the percentage of waits that used the overflow area.

(12*X) + 92

Specifies whether system tasks waiting on resources are excluded from Bottleneck Analysis.

Specifies transactions to be excluded from Bottleneck Analysis. This can be the actual 1- to 4-character transaction ID(s) or a generic specification using wildcard characters. You can use the question mark (?) wildcard character for single-character substitution and the asterisk character (*) as a trailing character only.

Specifies whether internal bottleneck collection starts automatically.

The transactions you want to exclude from situations.

The exclude list may contain the actual 1- to 4-character transaction ID(s) or a generic specification using wildcard characters. You can use the question mark (?) wildcard character for single-character substitution and the asterisk (*) as a trailing character only. The following are examples of wildcarding:

EXCLUDED_TRANS=(ABCD,E*)

Excludes the ABCD transaction(s) and all transaction IDs that begin with E.

EXCLUDED_TRANS=F?

Excludes all 2-character transaction IDs where the first character is F.

EXCLUDED_TRANS=G??H

Suppresses startup CMF performance monitoring only if not already active.

Possible values are:

YES

Allows CMF performance monitoring and XMNOUT CICS global user exit.

NO

Monitoring status inactive

Determines whether CMF is allowed to generate and write SMF type 110 records.

Possible values are:

YES

Allows CMF to write SMF type 110 records. Be sure that the SMF data sets are large enough for these records.

NO

CMF is not allowed to write SMF type 110 records.

Controls the compression of the OMEGAMON for CICS SMF 112 (database) records during XMNOUT processing.

Possible values are:

NO

OMEGAMON for CICS will write uncompressed SMF records.

YES

Allows OMEGAMON for CICS to compress the SMF buffer before it is written to SMF.

You can optionally write database performance data to SMF.

The OMEGAMON for CICS SMF buffers may contain data for multiple CICS transactions, and will be written to SMF when the buffer fills. Optionally the data can be compressed before the write to SMF occurs. This compression is performed using a standard compression utility, CSRCESRV.

OMEGAMON EMPs are required if data is to be written to SMF. This field specifies whether the MCT scan routine will display messages.

Possible values are:

NO

The MCT scan routine will not display messages regarding OMEGAMON EMPs.

YES

The MCT scan routine will display messages regarding OMEGAMON EMPs

Specifies average response time thresholds for this group (1-999 tenths of a second) for the interval record collector and the response time displays.

Defines the way that data is saved.

Possible values are:

DSPACE

Indicates that data for task history collection is saved in a data space owned by the OMEGAMON for CICS (3270) interface. This data is saved until the task history collector terminates.

FILEOCMP

Indicates that task history data is saved in a VSAM linear dataset. No z/OS® data space is used. FILEOCMP is required if you have a very large number of CICS transaction records that you wish to access through the ONDV command in OMEGAMON for CICS (3270) interface.

The size of the VSAM file does not have an impact on the amount of virtual storage used in the OMEGAMON for CICS or CICS address spaces. FILEOCMP causes data to be compressed before it is written to the data store.

The file should be allocated prior to restarting the CICS address space using this FILEOCMP monitoring option. Refer to the planning and configuration guide for further information.

Auto

Indicates that the value of DATA_STORE_TYPE could automatically be switched between DSPACE and FILEOCMP. The value FILEOCMP is used if the file which is specified for a CICS region exists. If no file matches the definition then the value DSPACE is used.

Whether you use a data space or linear dataset, the task history collector writes records using a wraparound format. Once the data space or dataset is full, the task history collector resumes writing records from the beginning, overlaying the previous data.

Specifies the portion of the data space (from 0 to 50 percent) reserved for file, database clock and counter statistics, and Application Trace records. See the Application Trace feature in the OMEGAMON for CICS.

You must specify a number greater than 0 or statistics by filename and/or Application Trace records will not be available from the task history collector.

The RESERVED_SIZE operand is not needed when the DATA_STORE_TYPE=FILEOCMP is specified. It will be ignored if it is supplied. File and database clock and counter statistics are always available in the FILEOCMP data store when they are being collected in the CICS region (through use of the DATABASE_COLLECTION component).

Specifies the name of a VSAM linear dataset when the DATA_STORE_TYPE=FILEOCMP or DATA_STORE_TYPE=AUTO is specified.

You can share global data area modules (but not VSAM data sets) across different CICS regions even though a dataset name is specified in the global data area module. To do this, you must insert one wildcard character (*) somewhere in the VSAM dataset name on this operand. When the task history collector is running, the wildcard character is replaced by the job name of the CICS region being monitored. The wildcard character may appear anywhere in the dataset name and should occur only once.

Indicates transactions to exclude from analysis. The list of transactions is limited to 63 transaction IDs. Transactions that start before phase 3 of the PLTPI or end after phase 1 of the PLTSD are not excluded. Any CICS-generated transactions that initiate without going through TRUE processing are not excluded either.

EXCLUDED_TRANS=(ABCD,E*)

EXCLUDED_TRANS=F?

EXCLUDED_TRANS=G??H

Specifies a resource for limiting usage:

VSAM

EXEC-level file control requests.

DSA

HWM of storage from the DSA.

EDSA

HWM of storage from the UDSA and EUDSA.

GDSA

HWM of storage from the GUDSA.

CPU

CPU time limit.

ELAPSED

Elapsed time limit.

CONTAINR

HWM of Container storage used by the task.

CPUGP

Time spent on a General Processor CPU.

CPUQR

Time spent on the QR TCB.

DLI

EXEC DL/I and CALL DL/I requests.

ADABAS

ADABAS requests.

IDMS

IDMS requests.

DATACOM

DATACOM requests.

SUPRA

SUPRA requests.

DB2

DB2 requests.

MQ

Message queuing requests

RUNTIME

Time for tasks held due to MXT or Class maximum. This is the time the task actually ran excluding time spent waiting for MXT or Class max tasks.

USREVNT1

Any user-defined requests.

Specifies one or more transactions to exclude from resource limiting. This can be the actual 1- to 4-character transaction ID(s) or a generic specification using wildcard characters. You can use the question mark (?) wildcard character for single-character substitution and the asterisk character (*) as a trailing character only.

EXCLUDED_TRANS=(ABCD,E*)

EXCLUDED_TRANS=F?

EXCLUDED_TRANS=G??H

#PAnPA keys (n = 1-3).
#FnnPF keys (nn = 01-36).
#LPALight pen attention.
#MAGMagnetic stripe reader.
#OCDOperator ID card

Exclude CICS system transactions by specifying EXCLUDED_TRANS=C*.

If the list of transactions will not fit on one line, use additional EXCLUDED_TRANS statements.

Specifies one or more transactions for resource limiting. This can be the actual 1- to 4-character transaction ID(s) or a generic specification using wildcard characters. You can use the question mark (?) wildcard character for single-character substitution and the asterisk character (*) as a trailing character only.

The following are examples of wildcarding:

INCLUDED_TRANS=(ABCD,E*)

INCLUDED_TRANS=F?

INCLUDED_TRANS=G??H

#PAnPA keys (n = 1-3).
#FnnPF keys (nn = 01-36).
#LPALight pen attention.
#MAGMagnetic stripe reader.
#OCDOperator ID card

If the list of transactions will not fit on one line, use additional INCLUDED_TRANS statements.

Specifies a threshold for limiting resource usage. Transactions that exceed this value are abended. Thresholds can be set at the following values:

Resource           Threshold
CPU and ELAPSED    1-32768 seconds
DSA                1-9999999 bytes
EDSA               1-999999999 bytes
File and DataBase  1-99999999 number 
                   of requests 
GDSA and CONTAINR  1-99999999 kilobytes

Specifies a threshold for limiting resource usage. OMEGAMON for CICS issues a warning message for transactions that exceed this value. The value must be lower than the KILL_LIMIT if specified.

Specifies the time intervals for the Average Response Times display. You must enter three values:

short,mid,long

These are the three intervals for reporting RTA data. In order to roll the values from one interval to the other, OMEGAMON for CICS requires that "long" be an integer multiple of "mid" and that "mid" be an integer multiple of "short". The values are in minutes within the range 1-999.

Specifies transactions to exclude from analysis. The list of transactions is limited to 63 transaction IDs. Transactions that start before phase 3 of the PLTPI or end after phase 1 of the PLTSD are not excluded. Any CICS-generated transactions that initiate without going through TRUE processing are not excluded either.

The exclude list may contain the actual 1- to 4-character transaction ID(s) or a generic specification using wildcard characters. You can use the question mark (?) wildcard character for single-character substitution and the asterisk character (*) as a trailing character only.

The following are examples of wildcarding:

EXCLUDED_TRANS=(ABCD,E*)

EXCLUDED_TRANS=F?

EXCLUDED_TRANS=G??H

If the list of transactions will not fit on one line, use additional EXCLUDED_TRANS statements.

Specifies the time slot definitions (1-48 slots) for the Today's Response Times display. It specifies the start time (first entry) and end time (second entry) of the slot. Enter the values in 24-hour clock format using this syntax:

(hhmm,hhmm)

Where hh (hours) is a 2-digit number from 00 through 24 and mm (minutes) is a 2-digit number from 00 through 59.

At least one slot must be defined; if more than one slot is defined, the slots must be in ascending order. The ending time value on one slot may be the same as the beginning time value on the next slot, but overlaps are not allowed. (A shared minute is not an overlap.) The default RTA TIME_SLOTs daily configuration is one slot from 0000 to 0800, then contiguous hourly slots until 1700, and one more slot from 1700 to 2400.

0000,0800
0800,0900
0900,1000
1000,1100
1100,1200
1200,1300
1300,1400
1400,1500
1500,1600
1600,1700
1700,2400

Specifies whether performance data collected by OMEGAMON is sent to the SLA summarization routines running in the OMEGAMON for CICS agent address space and displayed in the Service Level Analysis reports.