Skip navigation
1 2 Previous Next


28 Posts authored by: Martin Beasley Moderator
Share This:


MainView for CICS 6.6.00 supports the following releases of the IBM CICS system:  

  • CICS Transaction Server Version 3.1
  • CICS Transaction Server Version 3.2
  • CICS Transaction Server Version 4.1
  • CICS Transaction Server Version 4.2
  • CICS Transaction Server Version 5.1
  • CICS Transaction Server Version 5.2

If you continue to use CICS releases that are no longer supported, you must exclude those CICS regions from the new MainView for CICS . You can continue to use earlier supported releases of MainView for CICS to manage unsupported regions.   

MainView for CICS 6.6.00 also provides support for the IBM CICS Transaction Server Version 5.2 product. All MainView for CICS functions have been enhanced to work with CICS Transaction Server Version 5.2.


MainView for CICS 6.6.00 provides new sets of resources views in three areas:  

  • Application management views

    • CAPPL for CICS applications
    • CBUNDLE for CICS bundles
    • CBUNDLP for CICS bundle parts
  • Event-related views
    • CCAPSPC for event capture specifications
    • CEVTBIN for event bindings
    • CEVTPRC for event processing
  • Java/Web views
    • COSGBDL for OSGi bundles
    • COSGSRV for OSGi services


This version of MainView for CICS includes enhancements and changes to components of response time (CORT) views. MainView for CICS workloads track the performance of transactions matching the criteria in the workload definitions. This data is significantly enhanced to provide all facets of transaction response time data and is now available in a set of CORT* views that are similar to the TASK, CHIST, and CHINT families of views. You can access the new views through the original workload-related (CORT) views (CFLOW, CFLOWS, CWOVER, and CWOVERS). For more information about the CORT* views, see the MainView for CICS Online Services Reference Manual.  

Note - The original CORT views are updated. These views and the new CORT* views are not compatible between this version and earlier versions of MainView for CICS. BMC recommends that you initialize new MVI history files for this version to avoid problems with earlier versions of CORT records in the interval recorder data.


In addition, the CWOVERD and CWOVERDS views are no longer available in version 6.6 of the MainView for CICS product. Customized CFLOW, CFLOWS, CWOVER, and CWOVERS views will not work in version 6.6.


MainView for CICS provides support for monitoring the performance of the CICS applications running on your system. This support is provided through the following enhancements:


  • A new set of views displaying the CICS applications that are installed on your CICS regions
  • Navigation aids that help you locate the various resources related to your CICS applications that are installed on your CICS regions
  • An enhancement to the MainView for CICS Workload Monitor Definitions (CWKLDDEF) that allows you to collect and aggregate response time data for transactions executing as part of a CICS application or platform


MainView for CICS 6.6.00 allows you to specify generic target names when specifying monitors to be automatically started with the TARGET and BLK statements in BBPARM member BBIISPxx. You can specify the wildcard character asterisk (*) or plus sign when specifying targets that use AUTOBLK statements to automatically start low-level monitors when their targets initialize.


This version of MainView for CICS introduces the following new and enhanced views to replace earlier views:


  • The PASINFO view is enhanced with a new version that provides more information about the state of the BBI-SS PAS.
  • The PASINFO view now includes storage and CPU utilization information, information about other active MainView products in the BBI-SS PAS, and includes the new PASSUM and PASSUM views.
  • The PASSUM and PASSUMR views provide a summary of monitors that are running on your systems. The PASSUM view summarizes the monitors by the BBI-SS PAS and only runs in SSI mode. The PASSUMR breaks the monitor requests down by the targets that are managed by an individual BBI-SS PAS.
  • The PASPARM view is a new view that provides a list of the parameter members located in the BBI-SS PAS BBPARM data set. The view provides highlighting that indicates which of the parameter members are currently active for the BBI-SS PAS. It also provides hyperlinks that allow you to edit the parameter members either through dialogs within the products or direct text editing.


MainView for CICS 6.6.00 provides enhancement to security options for CICS actions, it checks the authority of a user to perform actions that would modify CICS or CICS resources. To do so, MainView for CICS uses standard System Authorization Facility (SAF) calls to external security managers (ESMs) when basic or enhanced security is active on the BBI-SS PAS.

This version of MainView for CICS converts the full-screen DUMP display and Storage options panels now run in windows mode. The new DUMP (or PK) view replaces these full-screen options. The new windows mode view supports hyperlinks from various MainView for CICS views to display storage information in MainView Explorer or through a 3270 MainView session. In the DUMP view, you can use the hyperlinks to examine CICS storage, and you can display the unformatted content of many CICS control blocks.

This version has changed some default settings for CMRSOPT parameters, which affect various data collection settings for the CICS region.


This version of MainView for CICS includes the following features that were introduced with PTFs in version 6.5 of MainView for CICS:


  • Support in the Task Kill Exit for TS and TD queues
    The MainView for CICS Task Kill Exit provides support for warning about, orterminating tasks, based upon TS or TD queue utilization.
  • Enhancement to the Detail Trace Facility
    The MainView for CICS Detail Trace Facility provides additional information about the responses to CICS commands and various CSD-related commands. It also allowsfor greater user flexibility in recording traces started against active tasks.
  • Enhancements to the IDCT and SDCT low level monitors
    The MainView for CICS IDCS and SDCT monitors support more granular monitoring of different types of dumps (taken, suppressed, system, or transaction) on your CICS regions.
  • New RES action added to FST2 transaction
    The MainView for CICS FST2 transaction supports a RES (restart) action. The RES action allows you to use a single command to restart the MainView for CICS and MainView AutoOPERATOR for CICS agents. You can use the FST2 RES command instead of having to use both the FST2 TERM and FST2 INIT commands.
  • Enhancement to CMRDATA
    The SMF110 segment (CMRDATA) is expanded to contain the 64-byte UDAT2 field from the T6E record.


This version includes the following changes and enhancements to views:


  • The CREGDSAS view provides additional data that you can use to set alarms for storage utilization.
  • The CREGION view provides statistics about region Max Tasks for use in setting alarms.
  • The CCONN* view provides additional information and 14 new SET actions.
  • The CTASKD and CHISTD views display the name of the last abended program. The CMRDETL record also includes this new field.


For more and complete information on MainView for CICS 6.6.00 please refer to the release notes.


Share This:


MainView for WebSphere MQ 5.2.00 supports Version 8 of the IBM WebSphere MQ software.  This release also provides significant performance improvements. You can take advantage of IBM System z Integrated Information Processors (zIIPs) for BMC Software Extensions for WebSphere MQ (MQE) data collection. 

You can control zIIP processing by using the following new EXITOPT parameters: 

  • ZIIP=[YES | NO]
  • ZIIPPCT=nnn


For additional performance improvements, you can now collect and aggregate data asynchronously in the Product Address Space; this significantly reduces the impact on performance. You can control asynchronous data collection by using the new EXITOPT parameter called PASDATA.


This release includes updated views:


  • AUTH views to support WebSphere MQ Version 8. Version 8 introduced new TYPE values and parameters for the authentication information object. MainView for WebSphere MQ displays the new values in the AUTH, AUTHD, and AUTHZ views and enables you to modify some of those values. For more information, see the online Help for these views.

    QMGR views to support WebSphere MQ Version 8. Version 8 added new queue manager attributes and changed the properties of some existing attributes. MainView for WebSphere MQ displays the new and changed attributes in the QMMVSD and QMD views. For more information, see the online Help for these views.
  • Miscellaneous view updates to support WebSphere MQ Version 8. The following views have been updated: Buffer pools (BP), Channel attributes (CHATTR), Channel authentication (CHLAUTHD), Page sets (PS), Publish/subscribe connections (PUBSUBST, TOPIC, TOPICD), Queues (LQD), and Queue manager system parameters (ZPARMSD)


This release fully supports changes that WebSphere MQ Version 8 made to SMF data control blocks. Version 8 restructured some SMF data and moved some SMF data control blocks to storage locations above the bar.


With this release, the Next Generation Logger (NGL) replaces the MainView Logger for trace record offloading.


The release also has end of support for:


  • MainView for WebSphere MQ Integrator feature is no longer available. As a result, the product no longer provides specialized message broker views.
  • BMC plans to discontinue support for the MainView for WebSphere MQ alternate statistics (MQMD) feature in a future release. 


For complete information on MainView for WebSphere MQ 5.2.00 please refer to the release notes.  


A “What’s new for MainView for WebSphere MQ 5.2.00” video is also available please click here (BMC customer support login required)


Share This:

A new Patch is available for MainView Infrastructure (MVI) Threshold Advisor product, this Patch adds installation support for Windows 2003 Server R2 64-bit and Windows 2008 Server 64-bit. The Patch also provides the ability to define and manage MainView recording requests by their defined MVI Single System Image (SSI) Contexts, as well as better calendar period naming/management for the push to the MainView Infrastructure side, and provides performance improvements on the Started Tasks (STCs) running on the mainframe when Context is used.


The Patch is located on the BMC Software EPD site (  Support Login Id required) and is identified by the "Threshold Advisor 1.0.00 Patch 1 Full Install" designation. This Patch is a complete installation and will install over the existing production version. When downloading from EPD, ensure you select the "Product Patch" Tab as per image below.



Share This:

On January 30, 2104 - MainView for IMS v5.1 became Generally Available, this release provides compatibility with and can exploit features of Version 13.1 of the IBM IMS system. The release adds support for:

  • An increased number of regions, BMPSs, and CICS threads
  • Database versioning
  • Displaying IMS ALTER option usage when a database reorganization starts
  • IMS Connect command enhancements
  • Synchronous program switch descriptors
  • MQ descriptors
  • OTMA Synchronous Program Switch clients
  • ISC over TCP/IP


This release also provide performance enhancements:

  • The Workflow samplers can now run on zIIPs.
  • Reduce the total IMS transaction and IMS BMP CPU usage by reducing the amount of CPU used by the MainView for IMS Event Collector. Internal test indicate about a 4% reduction in transactions, and a 7% reduction for BMPs. These results may vary at your installation due to differences in your environment and in your applications. Note: The larger reduction in BMPs is due to the higher number of DL/I calls that they typically make.


Other enhancements:

  • The transaction log record (X'FA') and the program log record (X'F9') have been updated and has change the length.
  • You can now record data for multiple IBM DB2 and IBM MQSeries subsystems in the log record.
  • IRUF record layout has been updated for the transaction accounting record(TAR), program accounting record (PAR), and terminal (LTERM) account record (LAR). Also the record lengths have changed.
  • All functionality is now only available through Windows mode.


For detailed information on these enhancements, please refer to the release notes on Product Support Status at (Note: support Login required)

Share This:

On January 30th, 2014 - MainView SRM v7.8 became Generally Available. This release provides:

  • A comprehensive view of an application's dataset usage, including historical trends. This will provide insight to potential cost saving measures to eliminate waste.
  • A view of datasets and whether they have a backup, when the last backup  was taken, and how many backups have been retained. Knowing which datasets have not been backed up or have not been recently backed up can highlight potential issues when looking at recovering datasets. Datasets that are being backed up too often can lead to unnecessary processing.
  • The option to offload eligible processing to zIIPs for internal sorts within the SVOS and Storage Guard Perform address spaces, and for compressing and decompressing VTOC Scan and Storage Guard Perform records.


For detailed information of these enhancements, please refer to the MainView SRM release notes in Product Support Status at (Note: support login id required).

Share This:

By applying PTF BQO1216 to MainView AutoOPERATOR version 7.3.xx you will have 2 new solutions:

1. MainView AutoOPERATOR zAware LPAR data solution provides summary zAware interval data. 


The MainView AutoOPERATOR zAware LPAR data solution provides summary data obtained from the IBM® System z® Advanced Workload Analysis Reporter (IBM zAware) appliance that analyzes data from the OPERLOG. 


2. MainView AutoOPERATOR zAware Interval data solution provides detailed zAware interval data.


The MainView AutoOPERATOR zAware Interval data solution provides detailed data obtained from the IBM zAware appliance that analyzes data from the OPERLOG.


You can use these solutions with any of the MainView AutoOPERATOR products to check either interval or detailed data returned from zAware, looking for anomaly count based on rarity of the message or changes to the message traffic.  To continually monitor the zAware appliance, you can schedule these solutions to execute via a Time-event-Rule with an interval frequency.  If an exception is discovered MainView AutoOPERATOR can take action such as generate an email, open a Remedy ticket, or take other action.


If you have IBM zAware appliance and any of the MainView AutoOPERATOR products, please install the PTF and take advantage of these new solutions.


For detailed information on these 2 new solutions, please refer to the Technical Bulletin at (login required), then “A – Z Supported Product List”, search for MainView AutoOPERATOR 7.3.xx 








Share This:

I am pleased to announce BMC MainView Console Management for zEnterprise 3.1.00 is now generally available (GA). There are two License Add-ons to this License Product, BMC MainView Console Automation for zEnterprise and BMC MainView SecureHMC

These are some cool new features and enhanements to these new release, they are:

  • Increase compliance by providing Login History. Login history can optionally be displayed to end-users, it show previous login attempts, also shows the login history log.
  • Launch viewers – now you can launch viewers from an Icon on your desktop, the end-user can optional save a desktop icon for a specific view, this is done via Java web-start. Note: nothing is installed on the desktop.
  • Color customization – has been added to the viewers to differentiate viewers, for example different color for production and for test. This allows a better visual check to ensure you are entering commands to the correct console and system.
  • Viewer Alerts – these have been added to display alert information to user similar to outlook email notification, an RDL2 (Rules Definition Language) rule can be triggered on a message and the resulting alert can be sent to the user’s desktop.
  • Enhancements for configuration and deployment– now the configuration database includes tables identifying all computers running MainView Console Management and which services should be run on which computers. Configuration changes made on one computer maybe replicated to all of the computers in the cluster.
  • Provide support for IBM zSystems interface zManager - Unified Resource Manager (URM) by supporting the new REST(Representational State Transfer) API as well as existing SMNP API. This will be used to provide Energy Management information from the Ensemble composition area, as well Storage Management from the Virtualization Management area.

For more general information of BMC MainView Console Management for zEnterprise visit


To down load this new release please visit Product Downloads, Patches and Fixes at Note: Support Login id required. 

Share This:

I am pleased to announce the release of BMC MainView for IP 3.3. This release enhances the monitoring and diagnostic capability for network monitoring and management. Enhanced trace analysis and packet trace improvements will provide better diagnostics and formatting for unwanted events. You will have more confidence to isolate problems with these new Trace enhancements, being able to pinpoint more issues like dropped packets and retransmits in a formatted and easy to read display.


New features and functions are:

-    -   The packet traces enhancements are:

     o   Start packet traces at a specific time.

     o   Save packet headers in the MainView for IP history files.

     o   Write packet traces in sniffer format, making the file accessible to sniffer products like Wireshark from Wireshark Foundation.

     o   Save packet traces when the MainView for IP product address space is recycled. 


-     MainView for IP now acquires two sessions with ISTPDCLU, one for the VTAM session data, and now a second session for the VTAM PIU Tracing. The VTAM PIU tracing enhancements allows the user to specify global traces for LU’s and SSCP’s, as well as PIU traces for specific named LU’s. PIU Trace data can be displayed by the VTAM session and also saved to the MainView history files when the VTAM session ends. You will be able to customize which VTAM/LU sessions are traced, and how many PIUs are kept for each session, and if they are logged to MainView history.

A VTAM PIU trace on a specific LU can be displayed, started, and stopped on any of the VTAM session views.


  1 .jpg


          The ‘DT’ command will display the VTAM PIU Trace for the VTAM session


2 .jpg


     Global PIU tracing can be started from the MVIPSAWD view. This will start PIU tracing for all VTAM sessions that have tracing enabled in the SAW Filters (The SAW Filters can be hyperlinked from the MVIPSAWD view). Note: The definition for the MainView IP VTAM application must be defined with EAS=2 and PARSESS=YES, and must be active to enable SAW data collection and PIU tracing.








-    The new Sysplex views show all Dynamic virtual IP addresses (VIPAs) for all the TCP/IP stacks in a sysplex. You can then drill down on each Dynamic VIPA to get more detailed information. 


-    MainView for IP will retrieve both OMPRoute RTTABLE and RIP data via the D TCPIP,,OMPROUTE,RIP and D TPCIP,,OMPROUTE,RTTABLE commands. The OMPRTT (and OMPRTTD) view display all of the routes in the OMPRoute main routing table.



   The OMPRIP and OMPRIPD views display the RIP-related configuration information.




-      The Availability Monitoring (AMON) view now uses an MPD wizard to add resources, making the process easier. The existing MPD to add an AMON resource was complicated and not straightforward as to which fields needed to be entered for each type of AMON resource. The new ‘ADD’ command will no longer be entered from column 1, but must be entered from the command line.


     The ‘Add’ command will prompt the user for the Resource Type:



      Then after selecting ‘Next’, the required fields for that Resource Type will be requested. For example, for resource type ‘PORT’:




-     MainView for IP can now act as the Primary Program Operator, and all VTAM messages will be routed to MainView for IP that were destined for the system console. The user can specify filters that will determine whether VTAM message is discarded, written to system console, or logged to MainView for IP (and logged to history). 


The MVIPPPOD view allows the user to configure the PPO application. The PPO interface requires a VTAM application for MainView for IP and must be active. The PPO Filters determine which VTAM messages are filtered and what action is taken. 




The PPO Filter table determines if the VTAM Message is logged to MainView (Log), or written to the System Console (WTO) by matching the VTAM Message number. If there is no match, the default on the MVIPPOD view is taken. The valid values are ALL (every message), NO (none), or a number 1-200 (every nth message to be processed).




The VTAM Messages that are logged to MainView can be displayed on the VTAMMSG view. The messages will be written to MainView history at interval time.




- The VTAM Session Configuration view (VTMSESSD) now shows a topology for the VTAM session.


For further information on MainView for IP 3.3, please visit us at

Share This:


Oracle is now prompting Java users to upgrade the JRE to 1.7.0_21. After upgrading, and then accessing MainView Explorer, you will see this Security Warning:


java warning.jpg

If you press "Don’t Block" you will be fine.



If you press "Block" you will be fine also, except that when you terminate MainView Explorer by closing the tab or the browser, you won’t get the prompt "Are you sure you want to leave this page? This will terminate MainView Explorer"; it’ll just close.


Oracle has added additional security checks with JRE 1.7.0_21. Research showed that it has to do with MainView Explorer’s unsigned JavaScript in the html member (DEFAULT) updating variables in the signed MVE jar; never a problem till now.


To resolve this, per Oracle’s suggestion, the manifest for MVE’s jar file has been updatedto add:


Trusted-Library: true

which will eliminate this Security Warning pop-up.


This is available as a MainView Explorer client PTF - BQY0176 (MVI 60) / BQY0177 (MVI 61) - which will be on eFix Thursday April 25.


There is also this work-around:

In the Java Control Panel/Advanced tab - in the "Mixed code" section check:

Enable - hide warning and run with protections






Share This:

I am pleased to announce that MainView for CICS V6.5.00 went Generally Available on Friday March 8th, 2013. This release of MainView for CICS provides a number of new and improved functions and features:


Ø Support for IBM® CICS Transaction Server v5.1. that provides additional new task performance data, this information is available in CMRDETL data as well as the TASK and CHIST views.


Ø Support for IBM CICS Transaction Gateway (CTG) v9.0. that provides new gateway performance data, this information is available in the CTGSERV and CTGCICS views.


Ø New CTGSERVM view – additional statistical information about the performance of your non z/OS CTG Servers - New CTGHSTRY prompter dialog allows you to set selection criteria for processing CTG task performance data. New CTG history dictionary, CTGDETL, is available for batch processing


Ø New detailed trace activation for an active task. You can now get a detailed trace without having to set it up before the tasks become active. This gives you the ability to debug at the task level which will give faster mean time to resolution. 


Ø The CREGSYS View has been enhanced with new data and divided into 3 new view sets that provide information about region-wide settings and attributes. These new view sets are CREGSYT for Dispatcher and Timing Settings, CREGSYA for Storage and Facility Settings, and CREGSYM for Monitoring and Statistics settings.


Ø Continue zIIP (System z Integrated Information Processor) exploitation, now MainView for CICS low level monitors. A new option USEZIIP was added to the BBISSP00 parameter (also via PTF to MainView for CICS V6.4).


Ø Provide Transient Data (TD) queues and Temporary Storage (TS) queues detail by task. The Temporary Storage Queue resource usage metrics provide data for both real-time and historical values.


Ø New views for DB2 Connection information is now available on the CDB2CON View which replaces the CREGDB2* set of views providing a simplified visualization of the data as well as the ability to take actions to modify the state and attributes of the DB2 connections providing a single location for managing DB2 Connections associated with CICS.

-          DB2 Entries View CDB2ENT has been added to provide visibility into and the ability to manage the attributes of DB2 Entry Resources.

-          DB2 Transaction View CDB2TRN has been added to provide visibility into the attributes and resource usage of DB2 Transaction Resources. This view also provides the ability to modify the state and attributes of these transactions.


Ø New JVMServer View - CJVMSRV – Provides Status and usage information about JVM Server Resources  - Currently the actions for this View Set have been disabled pending resolution of a couple of IBM APARs related to the JVMSERVER.


Ø New “Out of the box” – usability enhancements for Alarms, MainView Explorer Containers and View Dashboard for CICS. 

-   “ADD” command from the ALRMDIST View to active libraries.  The following alarms are now distributed with MainView for CICS:

§  CICSTASKCPU – Detects CPU usage by a task.  This is useful for identifying runaway tasks

§  CICSTASELAP – High Elapsed time for a task.

§  CICSREGNCPU – Excessive CICS region CPU Utilization

§  CICSREGMAXT – Percentage of maximum task value

§  CICSAVGRESP – High Average transaction response times

§  CICSTRANRATE – Low transaction rates

-      A new Dashboard View for IBM CICS Regions – CRGMDASH – provides key performance indicators and the ability for Threshold colors to vary according to defined thresholds.  This is a View that can provide a list CICS regions and performance metrics in a single view.

-      New configuration templates have been provided to display MainView for CICS Containers in MainView Explorer.  There are configuration template for Single CICS regions and templates for multiple CICS Regions.

Please refer to the attachment - "What is new MVCICS 6.5 details" for more details as well as screen shots of new Views.


For further information on MainView for CICS V6.5 please refer to the release notes (support login id required).

Share This:

If you’re like most organizations, you’re probably monitoring your mainframe environment with old static thresholds. The problem? Workloads and systems are rarely static. Fortunately, we’ve come up with a solution. Threshold Advisor, a new feature of BMC MainView, uses proactive analytics to analyze performance metrics and set dynamic thresholds based on those metrics at a given time period.

So no matter what time of day, you’ll get more accurate alerts, no false alarms, and a reliable, more self-sufficient mainframe.


Visit or via the MainView page at and try out our interactive tool. Check out the interface, set thresholds, and select date ranges. 

Threshold Advisor.jpg

Share This:

When was the last time you actually went into a bank to check your account balance, pay a bill, or get cash out? We all know how convenient mobile devices are when it comes to banking, or booking flight or hotels, or even tracking a parcel delivery. But have you considered how all of these transactions happening at all different times of day have affected the business. 


Take a look at an article Paul Mathie – SC Manager for EMEA and I authored called "Managing the Chaos of Mobility" that was published in the latest edition of Enterprise Executive. We discuss a few things you should consider when you are trying to manage unpredictable workloads driven by mobile device access to your applications. 


Share This:

Very good article by Mark Rasoce - Product Manager at BMC Software  - in the Enterprise System Journal  on 5 steps to help you manage the impact on Mobile device activity on your mainframe environment. View the article at

Share This:

Are you going to CMG next week in Las Vegas? Are you interested in Capacity Management? Come by booth #103 and meet our mainframe capacity management specialist - Greg Scriba and learn about what is new with BMC Capacity Optimization for Mainframes. See how this standalone product can work with our BMC Capacity Optimization solutions to give you Enterprise Wide Capacity Management. Greg can also discuss our existing solution - Capacity Management for Mainframes that continues to provide in-depth modeling and predictive capabilities.


We will also have technical specialist available if you are interested to hear more about BMC Capacity Optimization solutions for distributed systems.



Share This:

Here is a link to an artcle on the business benefits of consolidating your System z consoles with a console management solution, this has been published by Enterprise Executive


The article is by Mark Rasoce - Lead Product Manager at BMC Software and myself. I hope you find the article interesting.

Filter Blog

By date:
By tag: