Do you have mainframes?
Yes
11%
No
89%
Do you have a mainframe or midrange modernization effort underway?
Yes, we have migrated multiple applications or data
39%
Yes, we’ve started our initial application or data migration
10%
Yes, we’re planning to migrate an application in the next 6 months
10%
No, we plan to, but we haven’t started
22%
No, we have no intention of migrating off the mainframe or midrange
20%
Do you have a timeframe for when you want to decommission the mainframe or midrange?
Within the next year
2%
1-3 years
2%
4-5 years
1%
More than five years
1%
What is the catalyst for the mainframe/midrange modernization effort?
Improve agility (access mainframe/midrange data more easily)
33%
Cost (mainframe/midrange costs too much to run)
14%
Lack of skills (there aren’t enough skilled mainframe/midrange pros)
19%
Risk reduction (reduce the likelihood of application failures)
10%
Integration challenges (difficulty integrating mainframe/midrange apps/data with modern platforms, like mobile devices, cloud services, web applications
24%
Do you agree with the following statement?: The ability to migrate mainframe/midrange data and business logic to cloud workloads reduces the risk of mainframe modernization.
Strongly agree
38%
Agree
33%
Neutral
14%
Disagree
5%
Strongly disagree
10%
How do you currently access mainframe/midrange data from within your DevOps environment?
Direct access (via z/OS Connect or Apache Kafka)
50%
Data replication
0%
Data virtualization
30%
Provide an API to the mainframe/midrange data
20%
How will you migrate business logic from the mainframe/midrange as part of a modernization effort?
Re-architect the application(s)
3%
Refactor the application(s) using cloud-native capabilities
1%
Re-write the application(s)
1%
Replatform the application(s) (“lift ans shift”)
1%
Replace the application(s) with a packaged (COTS) solution
1%
Other
0%