IBM Power11 processor performance boost and energy savings; Izzi’s acquisition of CNX and its impact on IBM i and IBM Z ecosystems; AI tools reducing vendor lock‑in and aiding migration; technical debt challenges and the need for better developer experience; rebranding IBM i away from “green screen” perception and modernizing development practices; SQL techniques for IBM i data handling; importance of human expertise in modernization projects and strategies for managing institutional knowledge.
Welcome to another edition of Talsco Weekly
- IBM i Brief: 🔋 Power11 processors boost performance as Izzi acquires CNX.
- AI: 🔓 Artificial intelligence dismantles vendor lock-in while technical debt challenges arise.
- Development: 🖥️ IBM i faces “green screen” perception issues as SQL transforms data.
- Modernization: 🔄 Human element critical in transformation while clearing technical debt fuels growth.
IBM i Brief
🔋 IBM’s Power11 boosts efficiency and performance
IBM’s July 8 announcement of Power11 processors delivers 55% better core performance than Power9 and adds a novel “spare tire” 16th core for failover protection.
All three server tiers—high-end, mid-range, and entry-level—will ship July 25, with PowerVS cloud availability on July 15. The new processors feature energy-efficient mode saving 28% power consumption, enhanced DDR5 memory with 3X bandwidth over Power10, and backward compatibility with DDR4 memory cards to protect customer investments.
To sum it all up, Power11 raises the bar for Enterprise IT.
For an in-depth look at Power11, check out Andrew Nicholson’s analysis, or if technical documentation is your thing, you can find all the links here.
🏢 Izzi acquires Valence maker CNX
Izzi Software has acquired Chicago-based CNX Corp., creator of the Valence Web development tools for IBM i. The July 7 deal marks Izzi’s strategic entry into the IBM Power ecosystem, where CNX serves over 1,000 customers. Founded by Richard Milone and Robert Swanson in 1996, CNX needed capital to grow but will retain all employees. Milone will focus on technical projects including porting Valence to System Z, while Izzi CEO Jennifer Nelson plans to formalize support processes while preserving CNX’s product direction.
Izzi, founded by M&A experts and owned by Big Band Software, previously focused on IBM Z systems with its 2024 acquisition of ColeSoft, a Virginia-based mainframe debugging tools provider.
Takeaway: We have seen many acquisitions over the years within the IBM i ecosystem. This one, I find very interesting because not only are they looking to add product offerings to the IBM i space, but also potentially IBM Z systems.
AI
🔓 AI is breaking down vendor lock-in
The rapid evolution of AI tools is significantly reducing traditional vendor lock-in across enterprise software. Open-source models like Llama, Mistral, and Orca are providing viable alternatives to proprietary systems, while AI-powered migration tools are simplifying transitions between platforms. As LLMs become increasingly capable of translating between languages and frameworks, the technical barriers that previously kept organizations trapped with legacy vendors are weakening.
This shift is especially relevant for IBM i shops considering modernization, as AI tools can now help bridge proprietary technologies with modern platforms without complete rewrites. Similarly, open source technologies like PHP, Python, Node.js, and modern APIs have already been transforming the IBM i ecosystem, further reducing dependency on proprietary solutions.
🔧 Technical debt needs developer experience focus
Gartner reports 40% of infrastructure systems struggle with technical debt, while McKinsey found CIOs spend over 20% of new product budgets fixing debt-related issues. This isn’t just about code—it’s about developer experience.
The rise of AI tooling is supposed to make developers and engineers more productive and products ship faster, but technical debt slows this down.
Poor architecture, outdated tools, and subpar workflows hurt productivity and morale.
Development
Developer George VanEaton argues that calling IBM i the “green screen” is a damaging label that misrepresents the platform’s capabilities. The outdated nickname ignores modern features like DB2 integration, free-form RPG, open-source support, and enterprise-grade security.
VanEaton also suggests rebranding how we refer to IBM i professionals as Platform Engineers and Integration Specialists to accurately reflect their work with APIs, microservices, and modern architecture.
Commentary:
This article is sparking the discussion on LinkedIn. Here are some of what people are saying:
What’s called “Green Screen” today is literally the same as a “Command Prompt” or a “Console Window” on other platforms. Nobody is bashing other platforms like Linux oder Windows for having a Command Prompt or Console Window.
Its a perception problem. The IBM i OS on Power is NOT Legacy, and NOT limited by it’s green command line, which ALL other platforms have.
For the interface, green screen is a misnomer…but for the past several years I’ve just referred to it as a “terminal”, no different than a puTTY or MobaXterm interface to Linux or AIX.
If you would like to join the discussion, you can join now.
🔧 SQL transforms IBM i spool files into structured data Marius le Roux demonstrates how to parse IBM i spool files using SQL with ROW_NUMBER() and regex, creating custom QSYS2-like services for the WRKSRVTBLE command.
Modernization
🔄 The overlooked human element in modernization projects
When organizations consider modernization or ERP migrations, they often focus on technical capabilities—comparing the limitations of current systems against the promises of new platforms. What’s frequently overlooked is the human dimension essential for successful transformation.
While we frequently discuss the approaching retirement of RPG developers, less attention is paid to the business users—those with decades of institutional knowledge about processes, exceptions, and workarounds that keep operations running smoothly. These subject matter experts are critical to any transformation, yet their potential retirement poses significant risk to modernization projects.
Consider the scenario: you’re halfway through a multi-year ERP migration when your manufacturing floor’s key SME announces retirement. The documentation doesn’t capture their tacit knowledge, and suddenly critical process details are at risk of being lost forever.
Takeaway: Technology is just one piece of the modernization puzzle. Executives must recognize that successful transformation requires preserving institutional knowledge, comprehensive training programs, and succession planning for business users—not just IT staff. The most sophisticated ERP system will fail without the human expertise to properly implement and utilize it.
This human-centric perspective raises important strategic questions: Is an iterative approach to modernization better than a complete system overhaul? Would a best-of-breed solution that preserves institutional knowledge while gradually introducing new capabilities reduce transformation risk?
🧹 Clearing technical debt to fuel business growth With 91% of CTOs considering technical debt more concerning than cybersecurity or employee turnover, companies must address fragmented tech stacks to maintain their impressive 43% annual revenue growth—double the OECD average.
Join
Sign up for Talsco Weekly to get the latest news, insight and job openings for the IBM i professional.
Contact us
If you are an RPG programmer looking to explore opportunities or a client who is looking for a talented IBM i professional, please contact us. We look forward to assisting you.
Share
Do you know of someone who could benefit from Talsco Weekly? If so, please use the social media buttons to spread the word. Thank you!