The 2 Linux on z POC's I have seen have been pushed by IBM to the z/OS Systems Programmers. Naturally they /we are all too happy to learn z/VM to extend our skillset and extend the life of the z platform.
In each case, the POC had little support from the CIO or application architects. So successfully running a WAS, HATS or Oracle application on z/Linux received a lacklustre response from senior decision makers necessary to justify migration to this platform. The best story I heard from a senior IBM-er visiting from New York about IBM themselves being the largest SUN Solaris customer due to their outsourcing business. A senior accountant was told IBM could slash their infrastructure costs by migrating their Solaris workload to z/Linux, but the Outsource business managers still resisted. So the accountants slashed the budget anyway, apparently forcing the z/Linux migration. The relatively high entry cost of z/VM and an IFL or two (compared to commodity servers) makes the 'toe in the water' approach limited. The key audience should be the CIO and Infrastructure financiers in the business, who need to look at the big picture of hosting z/Linux-capable applications. My metaphor is an open cut mine. Is it more efficient to run 300 1t utes (pick-ups for our North American colleagues), or a single massive dumper that can take 300t in one load? Moreso, if one is already running a z/OS 'dumper', then the relatively less expensive z/VM environment is like a trailer on the dumper. In this light, z/Linux is a no brainer, but only upon committing a large scale of applications. Cheers, MARK DOUGLAS -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gabe Goldberg Sent: Thursday, 31 May 2012 12:02 AM To: [email protected] Subject: Destination z article query: Fun with proof-of-concept projects Major mainframe changes often begin with small proof-of-concept (POC) projects. Sometimes they're even off-radar skunkworks efforts, hidden until results are irrefutable and leading to game-changing successes. Linux on System z is frequently introduced with this toe-in-water approach, then scaled for huge server consolidation. Tell me about what's been learned from your POC projects -- specifically, what's the best way to conceive, plan, implement, evaluate, and report on work expected to introduce new technologies, tools, products, processes, etc. Have they been done with management support or as unsanctioned technology bright ideas? Either way, were they formal projects or seat-of-pants fun? What's been evaluated? And, of course, mention why some things didn't pan out. Were ideas flawed or could POCs have been done better? As usual, extra credit for copying replies to me directly so they're not buried in list digests. As usual, thanks... -- Gabriel Goldberg, Computers and Publishing, Inc. [email protected] 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegold Twitter: GabeG0 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ***************************** Disclaimer ***************************** The contents of this electronic message and any attachments are intended only for the addressee and may contain privileged or confidential information. They may only be used for the purposes for which they were supplied. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. The privilege of confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of mistaken delivery to you. If you receive this message in error please notify the sender by return e-mail or telephone. Please note: the Department of Science, Information Technology, Innovation and the Arts carries out automatic software scanning, filtering and blocking of E-mails and attachments (including emails of a personal nature) for detection of viruses, malicious code, SPAM, executable programs or content it deems unacceptable. All reasonable precautions will be taken to respect the privacy of individuals in accordance with the Information Privacy Act 2009 (Qld). Personal information will only be used for official purposes, e.g. monitoring Departmental Personnel's compliance with Departmental Policies. Personal information will not be divulged or disclosed to others, unless authorised or required by Departmental Policy and/or law. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
