Setting monitoring conditions (CMRSOPT)

The CMRSOPT options table adapts MainView for CICS operations and monitoring to your specific CICS environment.

This options table is multipurpose and it specifies:

  • Transactions excluded from monitoring

  • Start up of agent functions (extractor, task kill, program timing, and so on)

  • Monitored resources (terminals, transactions, files, and so on)

  • Data collection intervals control how often CICS statistics are written to SMF where data can be converted to CMRSTATS records by the CMRSTATS utility

  • Thresholds of system-wide response time service levels

  • Data collection routines for supported fourth generation languages (4GLs) and database management systems

  • Graphing resources (terminals, transactions, files, and so on)

    Note that selective resource level graphing is only available on an assembled/linked CMRSOPT.

Default settings for the CMRSOPT options table are specified in BBSAMP member CMRUSOPT and are assembled and linked into the distributed load module CMRSOPT. No modifications are required, but you should review the settings to make sure they work for your environment.


By default, MainView for CICS monitoring begins at PLT or manual startup. If you want to manually start MainView for CICS monitoring, refer to Controlling functions manually.

The CMRSOPT can be maintained with an online administrative function from the CMRSOPT view, or it can be assembled and loaded based on the parameters that are provided by the CMRSOPT macro. For greater ease of use, BMC recommends using the CMRSOPT view instead of using the CMRSOPT macro.

When the CMRSOPT is maintained with the online administrative function, data is stored in the BBIPARM data set with the member name of CMRSOPxx, and you can access the data through the CMRSOPT view. No user modifications are required because the earlier assembled CMRSOPT modules are also supported. To use the administrative function, you must first use the CMRSOPT views to add the default entry in the BBIPARM data set. For more information, see the MainView for CICS Online Services Reference Manual.

When a target CICS connects to the BBI-SS PAS for the first time, the CMRSOPT is loaded into ECSA. MainView for CICS looks for CMRSOPT in the following sequence:

  • Attempts to locate a CMRSOPxx member in the BBI-SS PAS BBIPARM concatenation; if one is found, MainView for CICS uses it.

CMRSOP00 is the default member name. The BBCFG facility can be used to specify a different suffix, as described in the MainView Customization Reference.

If MainView for CICS does not find a definition for the current target in the member, processing continues to the following steps to locate the appropriate load module:

  • Attempts to load a module with the target name; if one is found, MainView for CICS uses it

  • Attempts to load module CMRSOPT (default in BBLINK)

When a CMRSOPxx is found in BBIPARM, MainView for CICS builds a CMRSOPT load module from the data. MainView for CICS uses the created module to build the internal CMRSOPT data areas.

The CMRSOPT is refreshed when:

  • the BBI-SS PAS is recycled

  • CICS is recycled

  • FST2 INIT is processed after a FST2 TERM

  • one of the RESET commands is issued

See Resetting the CMRSOPT for information about the RESET commands.

All features that are provided by the CMRSOPT macro are supported in the administrative views with the exception of selective resource graphing (TYPE=resource). Although global graphing is supported (system, storage, and so on), you cannot perform selective file, transaction, program, terminal, PSB or BMS resource graphing through the PARMLIB CMRSOPT.

To use the CMRSOPT administrative views, see the MainView for CICS Online Services Reference Manual. For information about the individual parameters, see CMRSOPT parameters. For more information about the CMRSOPT macro, see Modifying the CMRSOPT with the macro.

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