Share: |

The University of Alabama recently won another college football national championship by beating Louisiana State University in the 2012 BCS championship game in New Orleans. This is their second championship in three years; they beat the University of Texas in the BCS game in Pasadena in 2010. All told, Alabama has won 14 national championships, 21 Southeastern Conference (SEC) championships, and 4 conference championships before the SEC was formed. It is easy to make a case that the Alabama football program understands and lives by a code of sustained excellence.


It’s not easy to achieve excellence, and it’s even tougher to sustain it. If you have ever written an application program, you know that writing the program is the easy part – maintaining it over the long haul is much tougher. Every time a new version of an operating system, database management system, or transaction manager is release, you must revisit the application program and make the necessary changes. Then you must test the program at multiple levels before implementing it into production. Even then, you keep your fingers crossed, hoping that you've covered all of the bases and that nothing goes wrong in production.


At BMC, our goal is to sustain excellence. We know that it’s not enough to deliver a new product; we update the products with new functionality – based on customer input and feedback – and we integrate changes to operating systems, databases, and transaction managers into the products. We don’t want you to have any unpleasant surprises when you implement BMC products into production.


I am proud of the reputation that BMC has achieved over the years of delivering great products and providing excellent support.  True, it is difficult for us to sustain that level of excellence, particularly in an economic environment that requires austerity from all of us. Yet, sustaining excellence is a challenge that we accept readily, and we expect to continue to earn your respect and trust for years to come.


The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
Jonathan Adams


Posted by Jonathan Adams Jan 19, 2012
Share: |

BMC has acquired I/O Concepts, with its industry-leading ioEnterprise line of mainframe console security, automation and consolidation solutions. These solutions, now known as BMC MainView Console Management for zEnterprise, help you consolidate, monitor and manage your mainframe hardware consoles. They enable you to efficiently manage complex and geographically dispersed operations from a consolidated and secure point of control.


In fact, before this acquisition BMC was already familiar with the quality of I/O Concepts' products. We worked with them for several years as development partners, and in 2010 we implemented their software while moving our data center from Houston to Phoenix.


By consolidating data center management into a single point of control, you can quickly and easily navigate multiple console displays,search information, and scroll through HMC messages from dozens of consoles – located anywhere – to diagnose and fix problems.


We welcome the I/O Concepts team and customers to BMC.


Click here to learn how you can manage HMC easily.


The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
Share: |

Guest post from Al de Moya, Consulting Brand Manager


Have you moved to DB2 10 yet? If not, put these steps into your migration plan.


Benchmark the performance from your current version of DB2.

One of your primary reasons for moving to DB2 10 may be to obtain CPU savings. Be sure to capture current DB2 CPU resource consumption to prove to management that the investment of time, machine resources, and costs justifies the migration.


Plan for a multi-step migration.

When you migrate to DB2 10, you will move first to conversion mode, then to enable new function mode, and finally to new function mode. IBM has enabled a migration from DB2 V8 directly to DB2 10. If you are still using DB2 8, consider moving directly to DB2 10 because eliminate the migration from DB2 9 to DB2 10, and you will benefit from the CPU savings in DB2 10. But don’t wait too long to start your migration; IBM drops support for DB2 V8 support on April 30, 2012.


IBM provides excellent documentation on planning the migration to DB2 v10.

Beware of access path changes that can hurt performance.

If you have migrated to a new version of DB2 before, you may have seen performance degradation as a result of access path changes. For DB2 10, IBM documentation states that you can get significantly better performance by rebinding your plans. 

To adequately test the impact of DB2 10 on existing plans, you need to explain the SQL statements on a DB2 10 subsystem with object statistics that match your production environment.

Create a baseline from your current DB2 version by EXPLAINing both static and dynamic SQL statements from your production workload, and then compare the access paths with those from the EXPLAINs run on DB2 10. Tools can help with this exercise.

Coordinate your DB2 management product migration with your DB2 system migration.

Check with your vendors to determine what version of their management products support DB2 10. You may find that one version of the products supports both your current DB2 version and DB2 10. You may need to migrate to the latest version of your management tools before migrating to DB2 10, but the payback would be a dramatic reduction in the time and effort to migrate to DB2 v10.

The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
Share: |

Guest post by Kathy Klimpel, Information Developer


Change is inevitable. In the IT world, we continually implement changes, and we have structured plans for doing so. These plans include extensive testing. But what happens when you introduce changes into production without thorough testing? The results are usually not good.


Just ask the NBA champion Dallas Mavericks. They lost several key players, and they added new players. The lockout-shortened season necessitated a shortened preseason and fewer practice sessions, and the Mavs started the season with two embarrassing losses. After six games, they are still struggling to find their rhythm.


The different players represented the change, and the lack of practice and preseason games represented the lack of testing. Whether we are talking about basketball or IT, the issues are the same:


Significant changes + inadequate testing = performance problems and system failures


You can minimize and even eliminate problems in production by testing thoroughly and by using tools that predict the impact of changes. For example, you can predict the cost of changed SQL workloads before moving from one version of DB2 to another when you use the right tools.


What kinds of problems have you been able to prevent bytesting?


The postings in this blog are my own and don't necessarily represent BMC's opinion or position.

Filter Blog

By date:
By tag:
It's amazing what I.T. was meant to be.