Document Controls
For Infrastructure & Operations Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
 |
November 13, 2009 Q&A: New Workload Adoption On System z MainframeWhy Linux, Why Mainframe, What "Best Fit" Workloads?by Brad Day with Simon Yates, Lauren E Nelson |
|
This is an excerpt
Executive Summary
Over the past six quarters, IBM has been very busy turning out a raft of customer case studies on new workload adoption on its System z mainframe, letting customers tell their feature/function/benefit impetus for deciding on the System z mainframe as their choice among enterprise computing alternatives for the deployment of select new software workloads. But take note — transitioning "select" new software workloads is the catch phrase here. To the credit of the System z enterprise architect and operations professional who influenced this decision, there was a common theme in the due diligence process each company went through. At first blush, every IT organization had to create a strong business case for moving new workloads at all. Then, an application stack "fit for purpose" had to tightly match the differentiated value of System z over other systems alternatives. Finally, a lower life-cycle cost argument had to be met — and often, completed — as the first order of proof point before these workloads could pass muster.
TABLE OF CONTENTS
- 1. What evidence is there today that the overall health of the mainframe computing footprint justifies the platform as a strong target for new workload adoption?
- 2. Why has the adoption of a Linux operating system environment been a core driver for attracting new ISVs, and consequently, new workload adoption on System z?
- 3. How do Red Hat and Novell SUSE characterize their investments and best fit traction on System z?
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
