Best Practice Report

Q&A: New Workload Adoption On System z Mainframe

Why Linux, Why Mainframe, What "Best Fit" Workloads?

Brad Day
 and  two contributors
Nov 13, 2009

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.

Log in to continue reading
Client log in
Welcome back. Log in to your account to continue reading this research.
Become a client
Become a client today for these benefits:
  • Stay ahead of changing market and customer dynamics with the latest insights.
  • Partner with expert analysts to make progress on your top initiatives.
  • Get answers from trusted research using Izola, Forrester's genAI tool.
Purchase this report
This report is available for individual purchase ($1495).