Search BMC.com
Search

1 2 3 Previous Next

MainView

40 Posts
Share: |


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 ( http://www.bmc.com/support/downloads-patches/BMC-Support-Product-Downloads-and-Patches.html  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.

 

Patch.jpg

Share: |


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 http://www.bmc.com/support/ (Note: support Login required)

Share: |


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 http://www.bmc.com/support/ (Note: support login id required).

Share: |


One of the strengths of Total Object Manager is the flexibility it provides users to define objects that need to be monitored and managed in a system.  There are many ways to define a given object.  From time to time the TOM Support and Development team has been asked for their recommendations for the best way to define an object.

 

Recently there have been questions on the best way to define a DB2 subsystem to TOM.  After much discussion and testing the Support and Development team has written a Knowledge Article on this subject.  This article illustrates the recommended manner for defining a DB2 subsystem to TOM.  This recommendation has been tested on a development system where a DB2 subsystem is being monitored and managed by TOM.

 

Readers interested in this Knowledge Article who have a BMC support id can view it at https://kb.bmc.com/infocenter/index?page=content&id=S:KA403405.

Share: |


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 http://www.bmc.com/support (login required), then “A – Z Supported Product List”, search for MainView AutoOPERATOR 7.3.xx 

 

 

 

 

 

 

 

Share: |


If you have, the resolution to your issue may be just a little bit of VIEW customization.   I'll have a few screen shots to hopefully make my points as clear as possible and allow you to complete the changes at your shop.    So first what fields are defined as COUNT fields and how would I know?   COUNT field types are almost always, if not always, on summary VIEWS.    To find out if the field you are setting an ALARM on is a COUNT field we need to check the format of the field.

In MainView Explorer this is done by right clicking on the column header and selecting Format data.    When you do this you will get this pop-up:

Notice under Summarization type the count button is selected.    And more importantly the Condition box has a condition specified.   THIS IS IMPORTANT!!

Blog1.JPG
On the 3270 we enter CUST on the command line of the VIEW we are on and then F column-identifier.  You should see a display like this.   Summarization type = C says this is a COUNT field and again the important piece is the Condition (for C) has something coded in it.

 

Blog 2.JPG

 

So if you are using a summary view and a count field to set an ALARM and the ALARM is not firing the problem is probably the condition statement.     But you can not simply clear the field because it will impact the COUNT field.

 

Here is how you resolve the issue.  First replicate the COUNT field.

 

In MainView Explorer you right click on the column header of the field you what to replicate and select Duplicate field.   After you do this you want to change the format.   Same process we used to find out about the COUNT settings.   Right click and Format data.    Change the new replicated field formats to look like the original field, BUT delete everything out of the Condition Box if there is anything there.

 

In the 3270 interface use the CUST command, and then R column-identifier to replicate the COUNT field.    Again same procedure as described above for the 3270 to view the format.    We want to make the replicated field again look like the original without the condition being filled in.

 

Next exclude the original field/column.

 

In MainView Explorer you right click on the column and select Exclude field.

In the 3270 interface you use the CUST command, and then X column-identifier to exclude the column from the view.

 

Then Save the view to your site library for VIEWS and set your ALARM on the new column/field.

Your ALARM should now work just like you expected.

Share: |


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 www.bmc.com/consolemanagement

 

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

Share: |


A survey was conducted through TechValidate of BMC’s customers who have deployed BMC MainView monitoring.  The research data presents the real-world experiences of more than 400 verified users of BMC MainView monitoring solutions. TechValidate publishes only factual data – statistics, deployment facts, and the unfiltered voice of the customer without any editorial commentary.  31C-8EC-2B3.png

 

Survey responses validate that BMC MainView offers great overall value, is easy to use, and demonstrates BMC's commitment to the mainframe!:

 

Top 5 reasons why customers chose BMC MainView:

  1. Overall value
  2. Ease of use
  3. Relationship with BMC
  4. BMC’s commitment to the mainframe
  5. Customer support

 

If you are a user of BMC MainView and would like to participate in the survey, please visit TechValidate by clicking here.

Share: |


Gilles Robert just posted a really neat blog about an under reported feature of MVI 6.1.   It is the JOBSTAT view which provides an SDSF-like interface for information about jobs, TSO users and STC's in the JES queues.    If you are not already following Gilles in MV Communities, check out his post at; https://communities.bmc.com/people/grobert/blog/2013/07/17/a-golden-nugget-of-the-mainview-infrastructure-v61

Share: |


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.

 

 

3.jpg

 

4.jpg

 

 

-    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.

 

     5.jpg

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

 

     6.jpg

      8.jpg

-      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:

9.jpg

 


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

 

  10.jpg

 

-     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. 

 

11.jpg

 

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).

 

12.jpg

 

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.

 

13.jpg

 

- 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 www.bmc.com/mainview

Share: |


 

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

jcp.jpg

 

 

 

 

Share: |


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

http://documents.bmc.com/supportu/documents/07/02/440702/440702.pdf (support login id required).

Share: |


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 www.mainframemonitor.com or via the MainView page at www.bmc.com/mainview and try out our interactive tool. Check out the interface, set thresholds, and select date ranges. 

Threshold Advisor.jpg

Share: |


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: |


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 http://enterprisesystemsmedia.com/article/business-perspective-managing-the-impact-of-mobility

It's amazing what I.T. was meant to be.