Blog Feed Post

Three Perspectives on Mainstreaming the Mainframe

As the next generation of professionals advance, they work alongside the mainframe experts who have been keeping host-based systems running since the 1970s or earlier. As a result, perspectives on mainframes must necessarily evolve as well.

This evolution of mainframe thinking, of course, does not happen in a vacuum. The enterprises that depend on such technology also struggle with digital transformation initiatives, while change comes to their application development shops in the form of Agile approaches and more recently, the cultural and organizational shift to DevOps.

Lost in this shuffle, perhaps, are the changing perspectives of categories of professionals, as new technologies, new priorities, and new generations of people come to dominate the IT organization.

From the perspective of management, understanding these dynamic perspectives is essential for identifying and hiring candidates, motivating the new generation of mainframe professional, and advancing the appdev organization and the IT shop overall as business priorities drive disruption and change across the organization.

Three Core Roles and their Perspectives on the Mainframe

In this article I’ll consider the roles of the software developer, the software engineer, and the architect. To be sure, many individuals would consider themselves as occupying more than one of these roles, and each of them – the architect in particular – actually consists of multiple, related roles.

When it comes to shifting mainframe perceptions, however, these three roles define important contexts for the overall discussion of mainstreaming the mainframe.

The Software Developer

Modern professionals may never need to work with traditional Mainframe UIs.

Modern professionals may never need to work with traditional Mainframe UIs.

The developer lives to write code. While each coder has their own preference for language, as they get more senior, they tend to have skills in more than one language, coding in the one that is most appropriate for the task at hand. The choice of, say, Java vs. COBOL, therefore, is really one of the best tool for the job.

More important to the developer than the choice of language is the ability to work with modern tools that behave in modern ways. In the mainframe world, little things like archaic file name formats can slow down a coder – and the last thing they want is for a trivial issue like file names to slow them down.

Once such niggling headaches are resolved, the developer maintains a high level of productivity coding on mainframe applications by sticking with their tools of choice – text editors such as Sublime and advanced IDEs such as Eclipse, Visual Studio, and IntelliJ. There’s no reason to use a green screen unless a particular developer prefers such an interface.

The Software Engineer

While engineers are generally coders themselves and thus share perspectives with developers, they also focus on the full application lifecycle – ensuring it follows established practices while achieving the goals of the business.

Modern software engineers, therefore, are focused on the details of DevOps, from the tools in the toolchain to the API-based integrations connecting them to the manifests and recipes that constitute the DevOps representation of each phase of the lifecycle.

For the engineer, integrating mainframe as a full-fledged participant in this lifecycle represents a significant step of achieving the DevOps way across a hybrid-IT architecture. Every tool on the lifecycle, from source code management to build management to testing to deployment, should work together, regardless of whether it be on the mainframe, in an on-premises distributed environment, or in the cloud.

Furthermore, how each of these tools works should be consistent across environments and operating systems. For example, creating a package should work the same way on a mainframe or in a Java or .Net environment.

Connecting such tools should also be seamless. RESTful APIs are now the established standard, and engineers expect mainframe tools to support them just as any other tool would.

The Architect

True, there are many types of architects, and the perspectives of software architects, solution architects, data architects, systems architects, and enterprise architects will necessarily vary.

That being said, there are certain ways of thinking that all good architects share. Just as developers approach their choice of programming language as the right tool for the job, the architect takes this attitude to a broader level.

In particular, the choice of mainframe vs. some alternative is essentially an architectural decision, as is the choice of modernization approach generally. Whether to retire a legacy asset, modernize in place, or integrate old with new is a decision the architect is best suited, either to make or support.

Today, IT is inherently distributed, and the mainframe must play on this ball field. The choice is no longer host-based vs. distributed, but rather whether a mainframe is the right server for given applications or workloads.

In their role as advisors of IT management, architects must be able to separate reality from hype. The unfortunate truth is that anti-mainframe hype has been leading IT executives to poor decisions for many years, to the detriment of their organizations and in the final analysis, to their customers.

The architect is in the best position to counteract this hype with factual information about the role the mainframe can and should play in modern IT environments. This person must be fully versed on the platform’s strengths as well as its weaknesses, in order to make or support decisions in the best interest of the organization and its customers.

The Intellyx Take

If you’re in an IT management role, you may be in a position of hiring developers, engineers, or architects – and if you have a mainframe, your hiring and retention challenges have just tripled.

Don’t approach mainframe hiring as a separate exercise. Instead, think about the perspectives and attitudes each role you are looking to fill must have in order to help your organization move forward with mainstreaming the mainframe.

Regardless of the specifics of your modernization strategy, you want people who can leave behind dogmatic or adversarial points of view. Instead, hire for open-mindedness, empathy, and people who see technology choices as a question of the right tool for the job.

Join Jason Bloomberg February 13th at 11:00am EST for an informative discussion on tactical approaches that help facilitate the cultural change required to unlock the full potential of mainframe as a driver of digital transformation.

Copyright © Intellyx LLC. CA Technologies and Microsoft are Intellyx clients. At the time of writing, none of the other organizations mentioned in this article are Intellyx clients. Intellyx retains full editorial control over the content of this paper. Image credit: CA Technologies.

Read the original blog entry...

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

Latest Stories
Sometimes I write a blog just to formulate and organize a point of view, and I think it’s time that I pull together the bounty of excellent information about Machine Learning. This is a topic with which business leaders must become comfortable, especially tomorrow’s business leaders (tip for my next semester University of San Francisco business students!). Machine learning is a key capability that will help organizations drive optimization and monetization opportunities, and there have been some...
"Storpool does only block-level storage so we do one thing extremely well. The growth in data is what drives the move to software-defined technologies in general and software-defined storage," explained Boyan Ivanov, CEO and co-founder at StorPool, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, whic...
The question before companies today is not whether to become intelligent, it’s a question of how and how fast. The key is to adopt and deploy an intelligent application strategy while simultaneously preparing to scale that intelligence. In her session at 21st Cloud Expo, Sangeeta Chakraborty, Chief Customer Officer at Ayasdi, provided a tactical framework to become a truly intelligent enterprise, including how to identify the right applications for AI, how to build a Center of Excellence to oper...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
ChatOps is an emerging topic that has led to the wide availability of integrations between group chat and various other tools/platforms. Currently, HipChat is an extremely powerful collaboration platform due to the various ChatOps integrations that are available. However, DevOps automation can involve orchestration and complex workflows. In his session at @DevOpsSummit at 20th Cloud Expo, Himanshu Chhetri, CTO at Addteq, will cover practical examples and use cases such as self-provisioning infra...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
As Marc Andreessen says software is eating the world. Everything is rapidly moving toward being software-defined – from our phones and cars through our washing machines to the datacenter. However, there are larger challenges when implementing software defined on a larger scale - when building software defined infrastructure. In his session at 16th Cloud Expo, Boyan Ivanov, CEO of StorPool, provided some practical insights on what, how and why when implementing "software-defined" in the datacent...
Blockchain. A day doesn’t seem to go by without seeing articles and discussions about the technology. According to PwC executive Seamus Cushley, approximately $1.4B has been invested in blockchain just last year. In Gartner’s recent hype cycle for emerging technologies, blockchain is approaching the peak. It is considered by Gartner as one of the ‘Key platform-enabling technologies to track.’ While there is a lot of ‘hype vs reality’ discussions going on, there is no arguing that blockchain is b...
Blockchain is a shared, secure record of exchange that establishes trust, accountability and transparency across business networks. Supported by the Linux Foundation's open source, open-standards based Hyperledger Project, Blockchain has the potential to improve regulatory compliance, reduce cost as well as advance trade. Are you curious about how Blockchain is built for business? In her session at 21st Cloud Expo, René Bostic, Technical VP of the IBM Cloud Unit in North America, discussed the b...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The use of containers by developers -- and now increasingly IT operators -- has grown from infatuation to deep and abiding love. But as with any long-term affair, the honeymoon soon leads to needing to live well together ... and maybe even getting some relationship help along the way. And so it goes with container orchestration and automation solutions, which are rapidly emerging as the means to maintain the bliss between rapid container adoption and broad container use among multiple cloud host...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
Imagine if you will, a retail floor so densely packed with sensors that they can pick up the movements of insects scurrying across a store aisle. Or a component of a piece of factory equipment so well-instrumented that its digital twin provides resolution down to the micrometer.