Enterprise Class Innovation: System z Perspectives
systemzblogger 2700017BYR 1,953 Views
After seeing the news about IBM scientists (working with Caltech) using DNA molecules as scaffolding with carbon nano tubes as part of new sub 22 nm lithography processes, I found myself thinking about progress on the storage side as well.
Remembering how storage, back in 1956 with the 5 MB and 50 platter devices, has evolved in 50 years to multiple TB sizes, or how with solid-state storage now can completely eliminate seek and set sector activity, it does all blow one's mind. (here's a nice white paper on SSD performance) Still, I guess we need these kinds of improvements when data doubles every year and a half, or there are estimates that is growing at 60% compound growth rates which are depicted as seemingly relatable examples as how many libraries of Congress per day we add.
Fortunately, at least in System z land, we have decades of evolution in management systems which can help government, control, and manage the scale of technical resources we use. Whether that storage is in the mainframe or on the floor, or it is memory, specialty processors, programs, tasks, or workloads... it's not version 1 approaches we have helping us. (A example of continued platform simplification is the recent announcement of the z/OS management facility -- announcement letter here)
By the way, this month's z/OS statement of direction notes IBM intends to use DVDs to deliver systems, adding the latest V2 Internet Key IKEv2 support, pulling DCE (technologies come and go!), and based upon customer feedback, not dropping support for VSAM IMBED, REPLICATE, and KEYRANGE attributes. for all the details just see the link above.
systemzblogger 2700017BYR 2,617 Views
The new Solution Edition offerings make a pretty big statement. Designed as integrated hardware, software and services packages that help customers deploy new enterprise workloads, they also make a great compliment to the zRewards and the Mainframe Charter. Building on the kind of packaging IBM has done for SAP, there are workloads for Data Warehouse, Application Development, Disaster Recovery, Security, ACI Payments, and SOA. So, without belaboring the point, some of the barriers to migration of key enterprise applications to z/OS are being lowered and made even more attractive for consolidation, performance, management, and fiscal effectiveness. Take a look at the detail page here.
Now, like every third person I have tried to work with this summer, I'm going to get out of here, take some of my vacation days, and keep this blog post short. If you're reading this, and it is still August, please get your rear end out to the car, airport, or backyard and make sure you get your days in too!
systemzblogger 2700017BYR 2,769 Views
The Mainframe Executive site has so many good postings, Iwas tempted to refer to a recent (July 16) entry that reviews some of the overwhelmingbenefits of System z in an interview with IBM Fellow, Gururaj Rao, Ph.D.. While I still encourage you to read it,since there some enticing discussion of futures including extremevirtualization and expanding the platform to even more architectures, I wantedinstead to share an interesting experience I had.
I happened to be looking at some of the System z benefitmetrics in the same day I was looking at some of the new presentations onbenefits of the evolving cloud environments. Some of these included studies on the kinds ofresources dedicated to test environments, and the parallels you can draw themwere intriguing.
For instance, how about going from server utilization ofless than 10% to up to 90? Would youlike to provision a test system in minutes rather than weeks? Or improve your release management by thesame kinds of numbers? Would you like toreduce software costs, reduce configuration errors, and reduced labor cost byover 50%? How about increasing yourUtilization by over 75%, and drastically reducing defects through automation? Did you know that distributed serverproliferation also includes a large chunk dedicated to the testing environment,like 1/3 to 1/2, of all the servers in a typical IT shop?
These sound a whole lot like the System z platformcharacteristics don’t they? So, forexisting System z shops looking for workloads to fit on System z, it might be agood idea to ask the question: Should we be making our capabilities more visible to upper management as they look at future sourcing decisions? (Oh yeah, and what are we doing with test across our wholeenterprise?)