Default monitoring conditions

This section describes parameters that set the global default monitoring environment for MainView for CICS. The default values for the parameters are underlined.

START= YES | NO

This parameter specifies whether data collection begins when a PLT entry activates MainView for CICS at CICS startup (see Step 4: Modify the PLT).

  • YES starts data collection and establishes communication with the BBI-SS PAS.

  • NO specifies that data collection does not start when communication to the BBI-SS PAS is established. Data collection can be started through the QON line command from the CREGAGT view; the FST2 transaction from a CICS console; or the FST2 transaction from a CICS terminal.

SHTDLY=( 0-10, 0-10)

On the CMRSOPT view (not available in the CMRSOPT macro), this parameter specifies how many seconds to delay the MainView for CICS agents shutdown at CICS termination and the number of times MainView for CICS agents will wait for this interval before shutting down at CICS termination.

  • The first value represents the shutdown delay which is the number of seconds to delay shutting down MainView for CICS agents at CICS termination before checking to determine if all tasks are complete. Valid values are 0 to 10 seconds. Specifying zero means MainView for CICS will not delay shutting down.

  • The second value represents the number of attempts MainView for CICS waits for transactions to complete before MainView for CICS agents will shutdown at CICS termination. Valid values are 0 to 10 attempts. Specifying zero means MainView for CICS will not wait.

Note

This parameter affects only MainView for CICS agents shutdown at CICS termination. It does not effect any other time MainView for CICS shuts down its agents, such as when the PAS shuts down when a command is entered. Also be aware that specifying values for this parameter will delay CICS termination.

CMRDETL= YES | NO | SEL

This parameter specifies whether detail transaction records are stored on the CMRDETL data set or data space.

  • YES specifies that detail transaction records are to be recorded.

  • NO specifies that detail transaction records are not to be recorded. Data is still collected for online access to data in views and displays.

  • SEL specifies selective CMRDETL recording is active.  This option is not available in the CMRSOPT macro.  For more information, see Implementing Selective CMRDETL Recording.

CRGRESPLOG= YES | NO

This parameter determines whether MainView for CICS generates the FT1010W message when average response time exceeds the value defined for the @RESP CREGION monitor, which is automatically started by MainView for CICS for each connected CICS region.

  • YES enables message generation.

  • NO specifies that message generation is suppressed.

DLOGPROC= DEFAULT | TRSIZE

This parameter defines the detail trace log block size for application tracing.

  • DEFAULT means 48K block size is used.

  • TRSIZE specifies that block size is determined by the TRSIZE parameter for the detail trace startup.

DTRACSIZ= 25 | nnn

This parameter specifies the maximum number of megabytes (MB) in the CICS data space to be used for detail tracing.

Valid values are 0 to 1024. A value of 0 means no detail tracing will be performed.

The sum of the DTRACSIZ and STRACSIZ values cannot exceed 1024 MB.

DYNAMIC= 0 | nnnn

This parameter specifies the maximum z/OS high private storage (non-DSA) used by MainView for CICS in kilobytes (KB).

The storage holds statistical data for DB2 plan activity. The PLAN display, (replaced with the CDB2ENT and CDB2TRN views) uses the data. When you use the default value of 0, data collection for the PLAN display is suppressed. If you are using the PLAN display, MainView for CICS collects an average of 24 KB of recorded data for every 100 DB2 plans. For better system performance, BMC recommends that you specify at least 1000 KB.

Specifying DYNAMIC=0 does not affect the collection of statistics for DB2 plan access for each transaction.

Note

MainView for CICS will round up to the nearest multiple of 8 any value that is greater than 0 and is not a multiple of 8.

BMC plans to withdraw support for the PLAN display in a future release of MainView for CICS.

EXCLUDE=YES | NO

This parameter specifies whether a CICS transaction should be excluded from monitoring.

  • YES specifies that specified CICS transactions in the TYPE=EXCLUDE statement will not be monitored.

  • NO specifies that all transactions are monitored.

If you specify YES, an entry must be made in the CMRSOPT table that identifies the transactions to be excluded from monitoring:

TYPE=EXCLUDE,NAME=(FIC2, CE+F, CSA*)

Note

Excluded transactions cannot be monitored, traced, or graphed.

FIC2= YES | NO

On the CMRSOPT view (not available in the CMRSOPT macro), this parameter specifies whether the MainView for CICS agent starts the FIC2 transaction in CICS to collect CICS and MainView for CICS statistics.

The CICS statistics are the ones you selected under section SMF Data Recording Periods in CMRSOPT. The following list describes where MainView for CICS statistics are used:

  • All full-screen graphic displays

  • In the threshold messages FT046, FT047, FT048, FT049, and FT522. These messages are monitored by @PRB4 (FT046-FT049), @GLBT (FT046), @GLBU (FT522) and the  CREGPRB view (FT046-FT049).

If FIC2 is not started, the data is not collected. If you do not need both SMF statistics and CMR statistics, you can set this value to NO. 

FILEOUT= YES | NO

This parameter specifies whether CICS resource usage are included in a transaction detail record.

  • YES specifies that detail records include CICS file and database usage for each transaction.

  • NO specifies that detail records do not include a transaction’s CICS file and database usage. NO uses less DASD space, but data is not collected for individual file activity.

FILEXPND= NO | YES

This parameter specifies whether expanded resources should be collected and written to the CMRDETL history data set. Expanded information includes individual function counts and timings based on type. It also includes volume serial numbers for files and the complete 48-byte IBM WebSphere MQ queue name if MQFILE=YES.

GPERIOD= 15 | nn

This parameter defines the cycle interval for graph frames (bars) in minutes.

Valid values are 2 to 30.

INCLUDE=YES | NO

This parameter is not supported in the CMRSOPT macro. On the CMRSOPT view, you can use this parameter to specify whether the CICS system transactions CSNC, CSNE, and CSSY should be included for monitoring.

  • YES specifies that the system transactions CSNC, CSNE, and CSSY will be monitored.

  • NO specifies that they will not be monitored (the default).

MAXFILE= 20 | nnn

This parameter specifies the maximum number of resource entries that can be included in a single CMRDETL record. Resources include DB2, DBCTL and other databases, file names, MQ queue names, CPU timing program names, and session and connection data.

Valid values are 1 to 255 if FILEXPND=NO (the default) is specified. Valid values are 1 to 75 if FILEXPND=YES is specified.

When you specify the MAXFILE parameter, you must also specify FILEOUT=YES (the default).

Increasing the potential number of resources that can be included in a 6E or 6D transaction detail record might affect the amount of required DASD storage allocated for the CMRDETL data set. Each resource entry increases the size of a detail record by 16-22 bytes (FILEXPND=NO) or 220-298 bytes (FILEXPND=YES). The record size of a CMRDETL data set should be increased to accommodate larger average sized 6D and 6E detail records. Sample member CMRDDTL of your BBSAMP data set contains the following statement as part of an IDCAMS command to define the CMRDETL data set.

RECORDSIZE(380 32736)-

The first number within the parentheses, 380, is the default average size of a detail record. The second number reflects the maximum size of a CMRDETL data set record.

With experience, you should be able to estimate the average number of files included in a typical transaction detail record. You may want to change the default average record size to more accurately reflect your site’s conditions. You can avoid frequent CMRDETL set switching when the average is too small. You can avoid infrequent switching when the average record size is too large also.

Step 8: Specify CMRDETL data sets describes the procedure to define CMRDETL data sets.

MAXLOST= 256 | nnnnn

This parameter specifies the number of detail transaction records that can be lost before MainView for CICS stops collecting data because of insufficient queue space.

Valid values are 1 to 32767.

MAXLOSTT= 256 | nnnnn

This parameter specifies the number of detail trace records that can be lost before application tracing is quiesced because of insufficient queue space.

Valid values are 1 to 32767.

MAXRESP=null | 20 | nnn

This parameter defines the maximum acceptable transaction response time service level in tenths of a second. This value is the default for all transactions.

Valid values are 1 to 999.

MQFILE= NO | YES

This parameter determines whether WebSphere MQ detail information is collected.

  • NO specifies that WebSphere MQ detail information is not collected; information is combined into one resource called MQSERIES.

  • YES specifies that extended function count and timing data is to be collected for all WebSphere MQ queues, and that a detail trace of a transaction that accesses WebSphere MQ resources will provide information about various function calls, including the OPEN, CLOSE, GET, PUT, and PUT1 calls, for each queue.

    If YES is specified, FILEXPND=YES must also be specified. See FILEXPND=NO | YES. See also the MQFOFF parameter.

MQFOFF= 0 | nn

This parameter specifies the displacement into the 48-byte WebSphere MQ queue name that begins the 8-byte name to be used by MainView for CICS, if MQFILE=YES is also specified.

This number is relative to zero. The default setting of 0 means the 8-byte file name is the first 8 bytes.

nn is any number between 1 and 40.

Tip

Specify a value for MQFOFF that ensures unique 8-byte queue names are used by MainView for CICS. For example, for the following queue names, you could specify MQFOFF=13 to use the last 8-bytes of the names:

MQ.MQSYSA.CICS1.Q1LOG

MQ.MQSYSA.CICS1.Q2LOG

MQ.MQSYSA.CICS1.Q2MSG

MQ.MQSYSA.CICS2.Q1LOG

MQ.MQSYSA.CICS2.Q2LOG

MQ.MQSYSA.CICS2.Q2MSG

NTGRAPH= NO | YES

This parameter specifies whether non terminal attached transactions are included in the Graph Global System display and LTX (Service Level Response) CMRSTATS records.

  • NO specifies that only terminal attached transactions are included.

  • YES specifies that terminal-attached and non terminal-attached transactions are included.

STRACSIZ= 25 | nnn

This parameter specifies the maximum number of megabytes (MB) in the CICS data space to be used for summary tracing.

Valid values are 0 to 1024. A value of 0 means no summary tracing will be performed.

The sum of the STRACSIZ and DTRACSIZ values cannot exceed 1024 MB.

TASKKILL= NO | YES

This parameter specifies whether the task kill function is to be initiated.

This option is checked only at PLTPI time or on the first INIT request and is ignored on subsequent INIT requests.

The task kill function can be controlled by using the FST2 transaction KON, KOFF and KRLD commands, or from the CREGAGT view by using the KON, KOF and KRL line commands.

USENETNM= NO | YES

This parameter specifies whether the netname should be used in MainView for CICS displays and tracing.

  • NO specifies that the netname is not used in displays and tracing.

  • YES specifies that the netname appears in the History Summary and CICS Trace Entries displays. In addition, CICS traces can be initiated based upon the netname.

WAITINT= 100| nnn

This parameter specifies the frequency, in hundredths of a second, with which MainView for CICS checks for:

  • CICS regions that have started or stopped

  • BBI-SS PAS termination requests

Valid values are 010 to 999.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Matthias Rabast

    for the parameter "DYNAMIC= 0 | nnnn" you give a recommendation of 1000, but you should also explain, what is a maximum and what is the impact of a high value for the storage consumption of the cics region and MV-4-CICS PAS

    Nov 28, 2019 11:56