Skip navigation
1 2 3 Previous Next


75 posts

I am delighted to let you know that MainView Infrastructure (MVI) 6.2 is now available.  It includes all of the Small Programming Enhancements (SPE) that have been released since MVI 6.1 including:

  • Long Phrase Password support
  • Threshold Advisor
    • Use of context
    • Calendar Management
    • Addition of MV IP and MVUSS metrics
  • MainView Explorer Improvements(MVE)
    • Ability to add user defined nodes to navigation
    • Combining Column and Line Charts
    • High Availability for MVE Viewer
    • SSL Support
  • Logger Modernization

In addition, MVI 6.2 provides two new features -  IPV6 support for MainView Explorer (MVE) connections and a data dictionary which has been requested by many customers. 

IPv6 provides support for the next addressing protocol since the older addressing scheme IPv4 has run out of addresses.  MainView will support you as you move forward with the latest communication protocol.

The data dictionary, (which is a set of tables) contains every element available from your installed MainView products. The table and views will contain the following kind of information:

  • The name of the element
  • The data type of the element
  • The number of views in which the element can be found
    • With the ability to get more details of the product provided views
  • Element information
    • The beginning of the help narrative
    • How the value is calculated (in most cases)
    • In depth data, for example, whether a dynamic threshold is in use

For more information about the release follow this link


I am delighted to let you know that MainView for JAVA Environments V2.1 is now available.  This new release of this solution includes many features requested by our customers including:

  • History and Interval recording
    • This provides the ability to trend data over time for important metrics such as Garbage Collection, Heap Usage and CPU Utilization
    • And detailed views showing recent, current interval and total values
    • Sample MainView Explorer configurations with graphs
  • Support for SMF Type 29 Records
    • This allows the reporting of IMS Garbage Collection statistics without having to set up JMX
  • JMX Configuration Assistance Utility
    • This Batch utility allows the fast setup for JMX ports for detailed monitoring
  • Extended JMX Data
    • Such as CPU by thread type
    • Other JVM Usage statistics
  • Ease of upgradability
    • A command to be able to start/stop the MainView JVM has been added so that components can be changed and upgraded without bringing down the entire product.

MainView for Java Environments (MVJE) provides a comprehensive solution for managing Java running on the mainframe, including auto discovery of JVMs and extensive data on JVM performance, memory usage and thread activity.  Although no other MainView monitors are required for implementing MVJE, existing MainView users will also see all the MainView unique benefits of centralized architecture, smart alarms and alerts, guided navigation for root cause identification, and analysis.  For more information about MVJE, visit the website.


For more information about the release follow this link


Have you starting taking advantage of IBM® MQ continuous delivery releases?


The second continuous delivery release (CDR) from IBM® MQ is now available.  If you are using BMC MainView solutions to monitor and manage your mainframe systems, you can rest easy, because MainView for MQ 5.3.0 provides day 1 support for IBM® MQ 9.0.02.


In addition, we have also delivered two new enhancements via PTF.


The first allows you to use System Symbols in the parameter files.  This makes it easy to customize trace and exit options.  To find out how to get this support please follow this link.


The second feature is a usability enhancement as well (one of many that have been and will be rolled out). It makes navigation through MQITrace much easier as you can select the number of records you want to be displayed. Please follow this link for information about this new function.


Learn about a complete, digital business-ready, central management solution of IBM® MQ resources.


Shared Memory Communications – Direct Memory Access (SMC-D) capability was added to Communication Server 2.2 via PTF.  This capability eliminates the TCP/IP processing in the data path by using shared memory instead of a wired connection.  This can result in faster connection and better efficiency for system to system communications. 

Today MainView for IP is making available full support for SMC-D including packet trace, and data associated with connections, ports and configurations.  For more information, please follow this link.


As customers embrace continuous delivery of IBM MQ™, MainView for MQ has risen to the challenge. As we stated earlier we had day 1 support for IBM MQ™ V9.0.01 and today we have delivered two new features within the maintenance stream.


The first feature is to help you understand which of your queue managers are running continuous delivery versions of IBM MQ™.  Since it is possible to run the Long Term Support level on some queue managers and different continuous delivery versions on others, this enhancement will allow at-a-glance understanding of version levels providing valuable information when trying to resolve issues in your IBM MQ™ environment.  Find more information about this enhancement here.


The second feature is delivering a customer enhancement request to be able to see the percentage of active channels from the available channel pool.  This will help with the creation of proactive notifications so action can be taken before the maximum channel used state is reached.  Managing channel capacity proactively will increase application availability and reduce the possibility of delays.  This enhancement continues the MainView strategy of delivering more actionable information so your system management solution can do more for you.  Find more information about this enhancement here.


Are you considering taking advantage of IBM® MQ continuous delivery releases for MQ?

The first continuous delivery release (CDR) from IBM® MQ availability has been announced.  If you are using BMC MainView solutions to monitor and manage your mainframe systems, you can rest easy, because MainView for MQ 5.3.0 provides day 1 support for IBM® MQ 9.0.01.

BMC MainView Message Management provides critical visibility and rule-based automation to help system programmers manage their IBM MQ environment. With this solution, you will:

  • Reduce the risk of disruption by keeping your MQ environment free of obstacles.
  • Provide a clear view of MQ objects across multiple MQ environments.
  • Set up automatic actions to resolve drops in performance or availability.

Learn about a complete, digital business-ready, central management solution of IBM® MQ resources.


In August 2016, I posted a blog with a video ‘MainView for IP and MainView for Network Focus on Features: What’s New.  One of the highlights was the capability to have a packet trace automatically start up when a connection hit an alarm condition and have the trace automatically stop once the alarm clears. This capability will provide First Failure Data capture so you no longer have to try and recreate network problems to gather the necessary data to resolve the issue.  This leads to less time and resources wasted debugging network issues and leads to faster resolution.   


We have created a Quick Course video to give you step by step instructions on how to setup this new function. You can access it with your support id at this link.


Recently BMC Introduced a new solution for monitoring the Java environments on z/OS called MainView for Java Environments (MVJE). This solution was introduced because of the growth of Java on the mainframe as customers enhance the backend for the digital economy.  We found that a monitor was needed to help Systems Management be aware of all the Java running on their systems and quickly identify problems in this new environment.  MVJE will auto discover all the JVMs that are running on your system and provides information on resources being used by the JVM such as Heap (Storage) and CPU Utilization. This includes showing the amount of CPU being offloaded to a specialty engine and the amount that could be if the capacity was available. 


Another area of importance is how well Garbage Collection (Memory Management) is working and how often it runs as this function of JVMs can have large performance implications if not properly tuned.


For your important workloads we allow you to decide if you want to go deeper by turning on JMX monitoring.  JMX data provides you with more detail about the memory managers, garbage collection and thread information.  MVJE will definitely provide the information a system management team will need to open a ticket to the application group using Java on z/OS.


To give you more technical information on MVJE, we have created a Quick Course video which provides a technical introduction to MainView for Java Environments. You can access it with your support id at this link.


Recently new releases of the MainView for Networks Solution and the MainView for IP product were delivered.  For the MainView for Networks Solution we have added the ability to collect trace information automatically based on your business criteria, giving you the ability to automatically capture first failure data.   For further “hands-off” operation, we provide the ability to automatically restart VTAM resources.

Within the MainView for IP product we have added many enhancements including Availability monitoring for VTAM resources, support for IBM's Network Management Interface (NMI) for Packet Trace including IPSEC data to support those customers that need to have secure IP connections.  For those customers who must use encryption we support SNMPv3 which is the latest release of SNMP.  These are just a few of the highlights available in the latest MainView for IP version.



For a more complete overview of all the features and function added please watch the following quick course video.


Are you ready for IBM® MQ 9.0.0?



Coming soon we will deliver version 5.3.00 of BMC MainView for MQ. It provides day one support for IBM® MQ 9.0.00.


BMC MainView for MQ (formerly BMC MainView for WebSphere ® MQ) also provides:

  • Capped Expiry (CAPEPRY) option- limits the expiry time of any message put to a queue or topic. Numerous views display the Capped Expiry value and let you change the value dynamically.
  • Use of MQ filters for queue views - helps improve the performance of views by limiting the amount of data that the MVS queue manager returns. Inclusion and exclusion filters are also provided to further limit the displayed data
  • Support for increased active logs - IBM MQ 9.0.00 has increased the ring of active logs from a maximum of 31 to maximum of 310 in order to allow it to capture longer peak rate activity and increase the availability of the queue manager in failure scenarios.


Learn about a complete, digital business-ready, central management solution of IBM® MQ resources.


Are you planning to upgrade to V9?   If so – would you like to comment on the top benefits you expect?


How long has it been since you considered your program preload list in IMS?  Are you taking advantage of the Wait for Input (WFI) designation for your transactions, or the Pseudo Wait for Input (PWFI) for your regions? Do you know where to start tuning your IMS Scheduler?


It is amazing how a small change in designation of a transaction or region can influence the amount of throughput and processor used by and IMS region or transaction. Exclusively available with the latest release of the MainView for IMS Management solution BMC provides the information to help you tune the IMS Scheduler.  BMC provides insight into the elapsed and CPU time to the schedule to first DL/I call.  This will help you to identify the largest users of CPU just to get to the first call, pointing out potential candidates for addition to the preload list.  BMC also provides the ratio of transaction executed per program schedule improving this ratio may help with CPU utilization and throughput utilizing the WFI for a transaction or PWFI for a region and isolating the transaction can cause major improvements to your IMS ecosystem and reduce your overall cost of running IMS in your datacenter.


For more information on how this new feature works please watch the quick course video.


As mobile and server connected environments grow, more and more applications within CICS TS face lag-time issues associated with networks.  This has led to customers writing more applications that use native TCP/IP sockets rather than web services or Communication server callable routines.  These socket resources need to be monitored as they can be the source of underlying task delays.  With the latest release of MainView for CICS 6.7 we have added the ability to monitor native TCP/IP resources and accumulate their usage across the life of the task.  This can help to pinpoint issues with network delays among the active tasks running within CICS TS.  This enhances your ability to isolate problems that were difficult to identify in the past leading to a shorter mean time to their resolution.


For more information on how this new feature works please watch this quick course video.


How many times have you had buffer overruns and missed the pertinent data being recorded to the trace or had to look through thousands of transactions to find the ones with issues? Now available in MainView users can utilize our capability Easy Trace Analysis to filter and analyze IMS detail traces.


This feature helps you get the diagnostic data you need and points out the DL/I and ESS calls that are having performance issues based on your criteria.


Detail traces contain thousands of record and if you run out of space you miss valuable data, this feature will allow you to choose the criteria identifying the records should be written to the trace dataset based on the information you need to collect.  This will reduce the amount of data that is being gathered and reducing the chances of missing the records needed for diagnosis.


The filtering capability can also be used to analyze the trace pointing directly to the problem DL/I and ESS calls.  So as an example it will only show data in programs that used more than a certain amount of CPU time.  Reducing the amount of data you have to read through to identify problem transactions. Reducing the time to problem identification and resolution.


This new capability is exclusively available in BMC’s December release of the BMC MainView for IMS Management solution. 

For more information on how this new feature works please watch the quick course video


The BMC MainView for Java Environments beta program has been very active. We are now expanding this program for additional applicants to partner with us in shaping the leading mainframe monitoring solution. As a member of the beta program, you can take part by test-driving an evolving version of MainView for Java Environments. Sharing your feedback with BMC will help create next-generation system performance management solutions.

MainView for Java Environments was designed to deliver valuable insights to unlock the full potential of your Java environments. This provides a single-system view across your mainframe subsystems. The offering will be a simple solution that lets you manage Java Runtime Environments to quickly and automatically identify abnormalities before they impact your business.


This is an exceptional opportunity for your team to gain working knowledge of the industry’s first Java monitoring solution.


To apply for our beta, please contact your BMC sales representative or


In the last couple of releases of MainView for CICS BMC has made quite a few changes to the Task Kill exit.  Prior to release 5.3, which became available in December of 2015, BMC added the capability to kill tasks based on the Temp Storage usage and number of File I/Os.  BMC also added the ability to take these values into consideration even if they are in a remote CICS region.  In the latest release, BMC has provided the ability to have dual thresholds.  A set to provide a warning that a transaction is getting close to the kill threshold and then the standard kill thresholds.  This new feature answers many customer request for enhancement.


The capability to have warning thresholds provides the ability to test kill thresholds before implementing them as well as providing the capability to proactively take action before transactions are terminated.  The warning thresholds can provide messages in the journal or the log that can allow automation to take a specific action prior to the transaction being killed that may allow the transaction to continue avoiding a potential failed customer interaction.  In this day of digital transactions many mobile applications are really interacting with CICS in the background. We all know if there are response-time issues or failures, customer can switch to the next online shopping application to make their purchase or to get a quote from a different insurance company.


Transaction throughput is still a critical component of all businesses today and MainView for CICS has added even more capability to help you proactively monitor and manage your environment.



For more information on how this new feature works please watch the quick course video.

Filter Blog

By date:
By tag: