DevOps-ing the Mainframe

Editor's Notes

• #4: Today’s discussion is based in part on DevOps.com’s latest ebook, which is now available via download on DevOps.com. Attendees also will receive a copy via a download link following the webinar.
• #5: Mainframes have been around seemingly forever, but there’s a renewed interest in them, especially in the DevOps space. The reason is simple: Mainframes provide economy of scale that can’t be duplicated by other technologies. We’ll discuss what’s driving that interest, some of the benefits mainframes provide when it comes to DevOps, and what’s changed in the industry to drive that interest around mainframes.
• #6: Powerful - the IBM z13 mainframe can handle 2.5 billion transactions a day. Mainframes are the backbone of transactional data, which means a large number of mobile and/or web-based apps rely on mainframes to handle back-end processing. Mainframes connect those systems of record with systems of engagement – allowing businesses to be more agile and more nimble in all their transactions, both web-based and on-premises. Skills shortage – Mainframes aren’t sexy. And older developers who ruled the mainframe world are hitting retirement age and not being replaced quickly enough. Meanwhile, developers in other countries are flocking to learn COBOL because they know they’ll always have a job. Along with more training, modernization of development tools for the mainframe and automation of processes play a role in stemming the shortage. Mainstays – Mainframes aren’t going anywhere. Companies that made huge investments in their mainframes aren’t about to forsake the technology, especially if it still does what they need it to do. Mainframes may be perceived to be old and stodgy, but they’re not going the way of the dinosaur anytime soon.
• #8: There are four things companies can do to bring DevOps and mainframes together. Take advantage of the latest hardware improvements Make changes faster with lower risk in an open and modern environment Create and optimize APIs for new workloads and refactor monolithic applications Automate delivery pipeline and shift left testing (Let the panelists do the talking)
• #9: 1. DETERMINE WHAT NEEDS TO BE AGILE AND/OR DEVOPS. Choose only applications for which you are seeing a lot of change or demand for a high volume of change. From there, you can then look at future development. There will be more future development that fits the agile/DevOps mold than existing, because future development is likely to support a fast-paced online or mobile system. 2. DETERMINE WHAT TOOLS SUIT YOUR ORGANIZATION THE BEST. Asking your preferred vendor what it recommends for the parts you want to bring into DevOps. Obviously, get a second opinion or recommendations from another vendor as well. 3. MOVE ONE PROJECT/TEAM. Don’t start by trying to boil the ocean. Instead, start with a pilot to gain experience and learn some best practices. Going slow also will show those more recalcitrant team members that it can be done. Choose a team of people who are interested in making the mainframe more responsive to business needs and let them break the ground for the organization. 4. OVER TIME, EXPAND THE PROJECTS/TEAMS DOING DEVOPS. Gradually, move more targeted projects into the DevOps fold, but don’t go too quickly. Make sure the pace isn’t so fast that information is lost or new team members are poorly onboarded. 5. START TALKING ABOUT THE MAINFRAME AS WHAT IT IS: a powerhouse processing tool available to projects. And stress that it is now available to DevOps and agile projects also, and won’t be the bottleneck.
• #10: We mentioned APIs as one of the four things companies can do to bring DevOps to the mainframe. APIs have done much to foment digital transformation across multiple industries, and they’re just as important in DevOps-ing the mainframe. However, there are a few approaches to APIs that are worth mentioning. (Lead-in to vendor ”pitches”)
• #11: (Zeev talks to the first point) (Rosalind talks to the second point) (Dana talks to the third point)
• #13: As we said before, mainframes aren’t going anywhere. Companies still using mainframes are doing so mainly to maintain existing projects. So unless those projects go away, their mainframes won’t. However, those companies will get more out of their mainframe by making it more accessible. The mainframe needs to have a modern development environment and the tools to integrate mainframe backends into modern app development timelines. Companies that DevOps their mainframes also will realize more value from their current DevOps tools. As these tools are used in more places, they provide more value. Perhaps most importantly, there is real ROI to opening the mainframe—the most powerful processing platform in the industry—to a larger set of applications
• #18: Thanks to our panelists, thanks to the audience for their questions (and for attending). Reminder this has been recorded Reminder attendees will receive a download link to the ebook Check DevOps.com for upcoming webinars. Fade to black.