Thursday May 22, 2008
Thursday May 22, 2008
Well what I do is write my blogs when I get an inspiration, this most often is not while I am in the office. Most of it is while I am travelling in trains, planes, automobiles. So 3 blogs today, however, they were stored for weeks and months when I wrote the draft in some airplane or remote location.
3 blogs in a day, I am catching up to my lost quota of 1 blog per week. I still have 10 saved up over the months.
The marketplace and hollywood have very restrictive views and impressions of the mainframe and many believe that IBM are the only ones that can supply such a thing. Well in reality the mainframe does not exist only in the minds of marketing and fiction. As many suppliers nowadays have equivalent and/or superior mainframe systems to IBM's.
Everyone who has not worked with mainframes has this impression; they are large, expensive, fast, complex, special, adaptable, reliable.
Everyone who has worked with mainframes knows the following; they are large, expensive but will be discounted on the hardware to make them look competitive, but software charges and maintenance will be expensive, they are not fast anymore or no faster than any other large system, you can only run zOS (MVS), they are not complex just totally proprietary. Not really adaptable, everything needs to run on the zOS instruction set need hypervisors (read overhead) to do conversions to run other interesting OSes like Linux, really good for the old stuff like CICS and old batch programs that no-one understands as the people who wrote the retired. They are special as a whole load of emotional baggage goes with them, companies cannot migrate from them as no-one understand the apps, so companies are held hostage, costs are often hidden in various ways (s/w, maint, service) so you can never get to the bottom of the TCO. As for reliability no different than any other major large system where you have good change control. Mainframes have good reliability records as no-one is allowed to change them. If you have other high end systems that you do not change they will be as reliable as a "mainframe". The mainframe hardware is not special compared to other high end systems. Historically they were better about 10yrs ago, but this myth continues.
So we either stop calling the z10 server a mainframe or we call every high-end server a mainframe. Sun and IBM high end Unix mainframes (servers), (not sure about HP, SGI etc) high end servers have better or equivalent features to the z10 servers.
Mainframe acid test, ask IBM what is the best plaform for every application that you want to run, what is the difference between their Linux actually Red Hat, AIX and zOS offerings. Is AIX inferior to zOS (aka MVS), is Red Hat not as good as AIX. Is Red had better than zOS. When should we use what.
Can I run Red Hat on a p-series
Can I run AIX on a z10 mainframe server (apparently it uses the same CPUs)
Can I run zOS on a p-series.
I get really confused with the positioning and confusion of AIX, Red Hat and z/OS. When do I do what with what. Or do I just do everything with everything and make a real mess. Good fun for the techies.
So with HP recently they came up with some logical partitioning with something called Dynamic LPARs, well that is old established technology, nothing new here. Available from others and established technology for a long time. However, HP engineering was always good, HP used to be a engineering company initially. So their high end UNIX servers can also be looked upon as mainframes.
Now Sun M-series servers have instruction retry, whole memory DIMM mirroring, crossbar ECC, more dynamic replacement of CPU's, RAM than any other supplier while the system is running and more. So you not get get more reliable than that and mainframes may not even have the reliability of some high end Unix servers.
Mainframe has been around since 1960's so the name is familiar but missused. Like many things in life, understanding, education and knowledge helps dispell these myths when once upon a time long ago they were something special. Now I like the mainframe, love to tune the assembler code, patch and zap modules, good for your old apps that no-one understands and your company is too scared to migrate to a new lower cost system. But as with everything technology moves forward and other high end systems especially large Unix servers are just as good or better and can be understood by more people.
We had a customer using an application on a customer platform, the supplier wanted funding from the customer to re-write the application to another Unix. Sun recommended to use Dtrace to find the areas that could be improved and help the ISV move from Solaris 8 to Solaris 10. However, the application supplier said that it would take too much work/money etc, it would cost less to re-write to another unix.
However, the OEM wanted the binary compatability value offered by Sun and to exploit Sun's multi-core chip technologies. So when the customer officially requested that the ISV work with Sun to determine if the application could be moved to Solaris 10, we discovered some interesting hidden agendas. Sun together with the supplier very quickly found areas in the application code for improvement at a fraction of the time and cost of a port to another platform. Application performance was improved by an order of magnitude, 10 x faster and qualification onto Solaris 10 was not a problem. Costs of taking the Solaris 8 binary compatible code, tuning it with Dtrace and moving to Solaris 10 were a fraction of re-writing to another platform. So beware, people may want funding to move applications to platforms, then ask for more money later to support a myriad of kernels. However, with Dtrace they can improve performance dramatically and shorten the time to qualify Solaris 8 & 9 apps onto Solaris 10. Buyer beware, the reason for not moving to the latest release of Solaris may not be technical.
By the way we also consolidated several servers runing this application onto one M5000 using Solaris containers to run many virtualised instances of the application. Ended up with nearly 100's of applications running on one server. The customer could now reduce the number or racks that they needed to.
Carzy world, moving applications from Solaris 8 to Solaris 10 is easy and you can consolidate your servers at the same time. Madness where will it all end. One big computer.
Make sure that all ISV's and application providers know the benefits of a faster time to market and reduced development costs that Solaris and Dtrace can bring them. Costs too much to qualify on Solaris 10, what a red herring. Make your application faster with minimum investment, use those Dtrace features. It is the developers best friend, I wish I had such a tool when I was a programmer.
The moral of the story is; All end users, ask your application suppliers or Sun to validate application qualification to the latest release of Solaris with Dtrace.
Why does this remind me of some builders when you are renovating your house. When they say "that will cost you", in reality it is a much simpler job. Maybe that is why the DIY business is so profitable.
Monday Mar 17, 2008
While looking into all the mainframe claims we (Jeff Savitt) discovered,