UrbanCode Deploy for z Systems
How is it possible that the server known as mainframe developed over 50 years ago is still so vitally important in today’s cloud-based, mobile, connected, Internet of Things world?
While some believe that smaller distributed servers provide the agility needed in today’s fast-moving cognitive era, the IBM mainframe is the preferred solution for many of the world’s most competitive businesses, including:
- 92 of the top 100 banks worldwide
- 70%+ of the world’s largest retailers
- 23 of the world’s 25 largest airlines
What’s the value of the connected mainframe to digital transformation?
As organizations adopt DevOps tools and methods, they also change their culture to integrate, automate, and provide transparency and visibility. A DevOps transformation includes bringing z/OS into the current century for development practices. Think about it: mobile applications make hundreds of millions of z Systems backend calls every day (for example, calls to COBOL and PL/1). The mainframe must be part of the modern development and operations practices. Using DevOps tools and methods, the development and deployment of backend code is kept in sync with that of the mobile front end, allowing faster time to market, and continuous improvement.
The mainframe has a unique set of challenges compared to distributed platforms. For starters, the technology used for deployment to mainframes was designed and built for a different time and a different type of deployment that existed before the sysplexes and the multiple environments that customers now have. So legacy deployment tooling is somewhat out-dated vis-a-vis today’s development, test and production environments. Another challenge is that most mainframe deployments require many different people to participate in the process, each person making changes to their part of the system. Because these changes are done outside of the deployment system, it is impossible to see all the changes for any single application. Consequently, it is required to have everyone available and on call at deployment time, which increases the complexity of the process and the possibility for deployment errors, not to mention ruined weekends and low employee satisfaction. On top of these unique challenges related to complex mainfame deployment processes, skilled people who understand legacy deployment tools are retiring.
IBM UrbanCode Deploy for z Systems
UrbanCode Deploy covers all your deployment needs by deploying complex applications to distributed platforms, cloud and virtualized environments, container platforms and of course, the mainframe.
An example of success
Within many IBM development teams, UrbanCode Deploy is a standard tool that has been exercised and refined for deployments to z/OS. Below is feedback from a team using UrbanCode Deploy for deployments to z/OS.
For a mainframe application, a mainframe team invested two weeks of one person’s time to set up the UrbanCode Deploy infrastructure including the 30+ steps necessary to deploy the application. The team now enjoys these benefits:
Why UrbanCode Deploy for z Systems matters to DevOps teams
UrbanCode Deploy matters to DevOps teams with a System z environment because:
View the following videos for additional information.