Kevin Dooley - http://www.flickr.com/photos/pagedooley/ Beat the Bashers!

Being the Mainframe Junkie that I am, I’ve been in a lot of situations where my platform has been under severe attack.

No, I’m not talking DDoS-attacks, but more of an ideological attack rooted in the (false) belief that the mainframe sucks, is old and will not continue to be among us for very much longer.

I have been working on The Mainframe (yes double capitals) since 1998 and have always heard them say my precious Mainframe will be made redundant within the next 5 years.

As of today, The Mainframe is still here and it’s getting bigger and bigger, not smaller and smaller. The Mainframe is still the dominant architecture in most of the Fortune-500 companies, a lot of governmental institutes and as of lately is growing out to be the number one platform when it comes to Large Linux Infrastructures.

Seeing as I’ve been invited to join the (ever growing ranks) of The Millennial Mainframer I’d deemed it fit to share some of my experiences where the unknowing started bashing The Mainframe and how I have ‘retorted’ to these blasphemies.

For my first post I will rant about Cost and Legacy……

Cost: “It’s too expensive

Expensive is a relative term to start with. Yes you have to dish out large amounts of money to acquire a machine packed to the rim with all the awesomeness that makes up a Mainframe. But when you take a step backwards and realize this is one machine to host a multitude of workloads, with the capability of being managed with a small amount of FTE’s ( Full-Time Equivalents) it’s a whole different ball game all of a sudden!

There’s no ‘let’s buy another server for this application’-approach. There’s no linear growth in the ‘workloads-to-manpower’-graph and due to the sheer fact utilization rates on Mainframes are a multitude of the rates on platforms of a lesser order there’s a much more economically viable picture to be drawn.

Set aside from plain acquirement and personnel costs there is the ‘software licensing cost’. My advice : get down to the bottom of the figures when it comes to cost.  For one I am pretty sure the PVU Pricing Model for WebSphere will turn out to be cheaper on a Mainframe Platform.

  [EDITOR ~ Paul Gamble:  If any readers could comment and walk me through this I would be eternally grateful…and smarter!!!] .

The Mainframe can host a variety of different workloads it’s a dead give away that it will be cheaper to bring extra workload to The Mainframe than to offload workload elsewhere…..

Legacy: “It’s Dinosaur stuff

This must be the biggest frustrations on my end. The similarity between Dino’s and The Mainframe is only true when you look at their awesomeness. For the rest the comparison goes completely bust.

I shall be the last to disagree with the fact that Mainframes date back from ‘ancient times’ (much like dinosaurs). But where at one stage T-Rex and his friends became extinct (possibly due to changing environments) The Mainframe has shown us that it is capable of continuing it’s evolution to keep sustainable.

The Mainframe has been virtualizing since like forever. From before I was born it was capable of running multiple workloads, in multiple ‘ADDRESS SPACES’ (images they say) on hardware less powerful than the CPU’s today. 

But my …….. (insert any X86 argument) has a gazillion virtualization instructions.

Yeah I know, sorry for ya, we’ve got one on The Mainframe, it’s called SIE (Start Interpretive Execution) and we don’t pronounce it ‘sigh’ for nothing 🙂

[Follow Henri Kuiper @  http://zdevops.tumblr.com/

Henri KuiperAbout Henri:

I’m a level 76 Fire Mage.
Oh noes, born in 1976, computer junkie since I was like 7 (BBC Micro) and moved up from Commodore to MSX then Amiga then Linux. Been a Mainframe Junkie since 1998 and consider myself a full-fledged systems programmer. I understand (and work on) the mainframe from the IO drawerr all the way up to the end-user application.

Proud member of the Millennial Mainframer 🙂

One thought on “Mainframe Rant: Cost and Legacy

Leave a reply

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> 

required