Mainframe modernization is often discussed in broad strategic terms, but for the teams responsible for keeping core systems running, the challenge is much more practical:
How do you make change faster, safer, and more repeatable without disrupting critical environments?
That question was at the center of the first session in the PopUp Mainframe Persona Webinar Series, focused on system programmers and DBAs. The session featured:
- Derek Britton, Head of Marketing at PopUp Mainframe
- Stuart Ashby, Practice Head at PopUp Mainframe
- Stephen Morgan, Technical Lead for PopUp Mainframe
- Mark Wilson, Technical Director of RSM Partners and editor of Cheryl Watson’s Tuning Letter
Britton opened the discussion by highlighting the continued pressure on mainframe teams to support modernization, improve delivery speed, reduce risk, and make better use of existing resources. PopUp Mainframe’s research, conducted with Vanson Bourne, found that many organizations are still struggling to get access to the right mainframe environments at the right time.
More than one-third of respondents identified a critical need for greater mainframe environment access. The research also showed strong demand for improvements in flexibility, sustainability, cost efficiency, delivery speed, risk management, and skills development.
Speed and Coordination are Essential
For SysProgs and DBAs, those challenges are familiar. Mainframe environments are complex, highly controlled, and often shared across teams. That stability is essential for production, but it can slow down testing, upgrades, problem resolution, and modernization work.
Ashby explained that mainframe teams are often managing multiple technologies, lines of business, regulatory requirements, and carefully controlled test data. DBAs may be preparing new database versions for adoption, while SysProgs are handling system maintenance, software updates, patches, and product installations. In that environment, even a straightforward change can involve significant coordination.
Wilson reinforced the point from a practitioner’s perspective. With decades of mainframe experience, he described the difficulty of making changes in systems where institutional knowledge may have disappeared over time. Software may have been installed years earlier, and teams may not fully know what will happen if something is removed, changed, or restarted.
That makes safe testing essential.
What Is Safe Testing
Wilson emphasized the value of being able to take a copy of an environment, make changes, test them, roll back, and try again. Whether the work involves a security database cleanup, a software migration, a configuration change, or a major maintenance update, teams need a way to test thoroughly before moving into production.
Ashby connected that need to PopUp Mainframe’s FastTrack facility. Because PopUp Mainframe uses IBM emulation on Linux, teams can take a snapshot of an entire LPAR environment and restore it when needed. That gives teams a known starting point for testing. If the test fails, the environment can be rolled back. If the test succeeds, another snapshot can be taken and used as the next baseline.
The discussion pointed to a different model for mainframe development and test environments. Instead of waiting for access to a shared system or requesting a new LPAR, teams can provision realistic environments more quickly and use them for repeatable testing.
Don't miss these other great articles
Stephen Morgan demonstrated that capability during the demonstration. Using the FastTrack interface, he showed how a PopUp instance could be managed with snapshot and branch controls. In the demo, a Db2 version 13 environment was switched to a branch running Db2 version 12, allowing a DBA or SysProg to compare versions, troubleshoot issues, or validate behavior.
The speakers were careful to clarify that this is not a production replacement or an MSU reduction story. The IBM software used to virtualize the hardware is for development and test use. The speakers described the value as flexibility: giving teams right-sized environments that can run on Linux on Z, LinuxONE, IFLs, on-premises platforms, x86, or cloud virtual machines depending on the organization’s needs.
Audits, Data Protection, and Validation
The Q&A also addressed questions around auditability, data protection, and validation. The speakers emphasized that PopUp Mainframe does not replace an organization’s existing testing or security processes. Instead, it gives teams another place to run them. Existing validation steps, logs, SMF data, syslog records, and other artifacts can still be used to support internal controls and audit requirements.
Data protection was another key concern. Ashby noted that organizations can move data into a PopUp environment in multiple ways, including FTP, Connect where licensed, IBM migration utilities, whole-volume approaches, and other site-specific methods. For sensitive data, teams can use existing masking, obfuscation, and subsetting tools before moving data into development and test environments.
The session closed with a practical theme: flexible mainframe environments can help reduce uncertainty before production changes.
SysProgs and DBAs are being asked to support faster delivery, security improvement, modernization, sustainability, and skills development while continuing to protect the reliability of core systems. The speakers positioned realistic, restorable test environments as one way to reduce bottlenecks, support more complete testing, and help teams enter production change windows with fewer unknowns.
Join in July – More to Come
The conversation continues on July 28 at 10:00 a.m. EDT with the next session in the PopUp Mainframe Persona Webinar Series, “Accelerating Mainframe Efficiency: Training and Onboarding.”
Featuring Geoffrey Decker of Northern Illinois University, the session will focus on training bottlenecks and onboarding considerations for both new-to-z professionals and experienced practitioners working in modern mainframe environments.
0 Comments