We hear a lot about technical debt in the IBM i industry publications, especially as it pertains to modernization and bringing businesses into the 21st century.
Upon reviewing many articles IBM i technical debt and performing our own discussions with IBM i shops, it’s clear that technical debt is a big concern, impacting business growth and revenue and talent acquisition. Among the many articles written about IBM i technical debt is imPower Technologies’ article “Resolving Technical Debt with Education.”
The top technical debt concerns for IBM i:
- Outdated systems and skills: Many IBM i shops are running on older versions of the IBM i operating system. This can lead to security vulnerabilities, compatibility issues with newer technologies, and a shrinking pool of developers with expertise in these older systems.
- Legacy code and applications: Over time, code can become complex, be hard to maintain, and lack proper documentation. This makes it difficult and expensive to make changes or add new features.
- Integration challenges: Modern applications often rely on APIs and other integration methods that may not be readily available on older IBM i systems. This can make it difficult to connect IBM i applications with newer systems and data sources.
- Lack of agility: Technical debt can make it slow and expensive to respond to changing business needs. Adding new features or adapting to new regulations can become a major undertaking.
- Security risks: Outdated systems and unpatched vulnerabilities can leave IBM i shops exposed to cyberattacks.
To further showcase the extent that technical debt has impacted business, some companies have conducted industry surveys around the topic. Here are some of the results of recent surveys:
McKinsey Digital’s survey estimated that technical debt can account for 20-40% of the value of an entire technology stack.
In their white paper, CodeScene shares that data suggests that organizations waste 23-42% of their development time on technical debt.
DXC Technology’s survey of 750 C-suite information and technology executives found that:
- 99% of them say that technical debt is on their corporate risk register;
- 46% say that technical debt is closely linked to their ability to pursue digital initiatives;
- and there’s a 39% cost savings from technical debt reduction.
A global survey by Protiviti of over 1,000 technology executives found that “organizations are spending an average of 30%” of their IT budgets on technical debt management.
Why Is Technical Debt a Significant Challenge for IBM i Shops?
Despite the wealth of data and ongoing discussions about technical debt, many IBM i shops continue to struggle with resolving their technical debt. This resistance can often be attributed to several prevalent myths surrounding IBM i application modernization. Common justifications such as "If it ain't broke, don't fix it," "We've always done it this way," "Taking our system offline for changes is too difficult," or "It's just too expensive right now," hinder progress.
These are all reasonable explanations of why many, especially smaller, IBM i shops don’t resolve technical debt or modernize. In fact, the backward compatibility of the IBM i has helped many shops continue down a path of technical debt without the need to upgrade or update code. It’s a double-edged sword as backward compatibility has enabled companies to reduce risk and extensive rewrites as well as protect their investments. Though the other side of that sword is perpetuating legacy code with limited room for modernization and increased costs.
Technical Debt and Backward Compatibility of IBM i
Regular upgrades can be easy to put off, but for IBM i shops, technical debt accumulates rapidly when regular upgrades are neglected, posing a significant challenge for businesses. This issue is particularly pronounced for those still operating on outdated platforms like System/36 and using old languages like RPG 2. Despite the stability and familiarity these older systems offer, their continued use can lead to increased maintenance costs, challenges finding talent, security vulnerabilities, and a stifling of innovation.
Understanding the implications of this technical debt is crucial in order for organizations to remain competitive and efficient in the ever-evolving technological landscape. Let’s delve into the consequences of not upgrading IBM i systems regularly and explore strategies to mitigate the risks associated with lingering on legacy platforms like System/36.
Increased Maintenance Costs
Technical debt in IBM i systems significantly drives up maintenance costs, particularly for those still running software in System/36 mode on new hardware. As these outdated systems age, they demand specialized knowledge, which can be both hard to find and expensive. Moreover, integrating these old systems with modern technologies often requires custom solutions and patches, leading to higher labor costs and increased downtime. This relentless financial drain diverts resources that could otherwise be invested in growth and innovation.
Challenges Finding Talent
“Technical debt is a talent issue, too. The more antiquated code that a company struggles to maintain, the more it inhibits the modern tooling and services that developers want to use to build applications,” states John Duigenan, the global chief technology officer for financial services at IBM in a 2021 interview about technical debt and its impacts on banks.
This is exactly the challenge many IBM i shops are facing with the increase of retiring developers. If you are looking for new developers to join your team, they’re less likely to join if your system has antiquated code they can’t read or doesn’t allow them the ability to get innovative and grow in their career. Plus, IBM no longer supports RPG 2, making this a big deterrent for developers.
Security Vulnerabilities
One of the most critical risks of not regularly upgrading IBM i systems is the heightened vulnerability to security threats. Legacy applications running in System/36 mode lack modern security features and updates, making them prime targets for cyber attacks. Without the latest security patches and enhancements, these applications are exposed to a multitude of risks, from data breaches to ransomware attacks. This can result in not only financial losses but also severe reputational damage, eroding customer trust, and regulatory compliance.
Stifling of Innovation
Running current hardware or software in System/36 mode stifles innovation, as these platforms are incompatible with contemporary technologies and software development practices. The rigidity and limited functionality of older systems restrict the ability to adopt new tools and methodologies, hindering business agility. This technological stagnation prevents organizations from leveraging advancements such as cloud computing, AI, and big data analytics, ultimately impeding their capacity to compete effectively in a fast-paced, digital-first market.
A Couple Manageable Ways to Tackle Technical Debt Right Now
1. Easily Convert RPG 2 to ILE RPG with TARGET/400
For companies running code in the System/36 environment, there will come a day when IBM will pull the plug on the System/36 environment and no developers will even be able to help you recode the applications. Luckily, there’s still hope. Converting RPG 2 to ILE RPG (aka RPGLE) can be done easily with almost 100% accuracy using a tool called TARGET/400.
In the 1980s, John Caine and a partner developed TARGET/400, originally created to complement the 36 migration assistant Caine wrote for IBM Rochester, enabling IBM i shops to go from System/36 to the System/36 environment. If you’re not familiar, the System/36 environment made it possible for System/36 shops to run on AS/400 without converting code to native mode. So far, over 1,200 IBM i shops have used TARGET/400 to convert their RPG 2 to ILE RPG.
“You don’t need to buy new software or update all code by hand,” states Caine. “TARGET/400 is fast and cost-effective, enabling IBM i shops to easily move into the 21st century.”
Caine is the architect and author of the IBM Migration Assistant, which was distributed as an IBM licensed program with the OS/400 operating system. He shares, “Many shops running in the System/36 environment on AS/400 have already used our software, probably without knowing.”
This solution enables IBM i shops to quickly resolve technical debt. With the ease of use, even your new talent or less-experienced RPG developers can convert old code to RPG ILE to bring your system into the 21st century.
2. Training the Next Generation of IBM i Professionals to Resolve Debt
As Duigenan pointed out in his 2021 interview, talent goes hand in hand with addressing technical debt. As we stated earlier, it will get harder and harder to attract talented professionals if you are still running on old systems. The talent market is very competitive, and to keep up, it’s now more important than ever to modernize so you don’t get left behind.
A big part of the talent issue is lack of training.
Training Your Existing Team to Help Resolve Technical Debt
Your seasoned developers will need training on the latest ILE RPG, RDi and modular programming, and SQL to pay your technical debt. As we shared in our article on technical debt in 2021, “Old or poorly done code can be a huge problem for your business. Sending your seasoned programmers through new RPG and RDi programming classes will help them understand the newest technologies and bring your business applications into the 21st century.”
imPower Technologies offers self-paced, instructor-led, online courses in these topics so you can get your team up to speed fast to begin resolving technical debt this year. In fact, our Programming in ILE RPG course can be completed in less than 10 weeks, and our RDi and SQL workshops are 2-3 weeks maximum. Every imPower course includes full accountability for employers along with graded assignments and quizzes, so you know your staff is retaining the knowledge and skills. Also, all courses can be enrolled in at any time, enabling you to plan out your staff’s professional development however it suits your company needs.
A Two-Pronged Approach to Your Technical Debt and Talent Problems
As many IBM i shops face looming retirements, there may be an immediate need to fill vacancies on your team. If you are using an old system, are using old code, or just want to start modernizing to resolve technical debt, having to both hire new talent and accomplish your goals can feel daunting.
We’re here to tell you, it doesn't have to. We’ve worked with many IBM i shops in the same situation and found a great solution! We suggest you either promote from within your company or hire new talent— recent IT college graduates or professionals looking to upskill. Next, send them through training, such as our IBM i Concepts and Operations and Programming in ILE RPG courses for starters. While they are in the training, teach them your business operations and IBM i applications. When they are done with the training, they can use TARGET/400 to convert your old RPG to RPGLE and upgrade your system so you can begin resolving that debt. As they get more proficient, they will be able to help you document your system and modernize to increase efficiency and revenue. This is a great way to improve employee retention and empower them to optimize your business through career development.
It’s Time to Tackle Technical Debt and There Are Solutions at Your Fingertips
Addressing technical debt in IBM i systems is crucial for modernizing your business and maintaining competitiveness in the digital age. To effectively tackle this issue, it's essential to invest in upgrading outdated code, converting legacy systems, and most importantly, training your team on modern tools and techniques like ILE RPG and RDi. By equipping your developers with up-to-date skills, you not only enhance their ability to manage and reduce technical debt but also pave the way for greater innovation and efficiency. imPower Technologies offers online courses that provide comprehensive training for your staff, ensuring they are well-prepared to handle modern development challenges and contribute to the overall improvement of your business operations. Don't let technical debt hold your organization back; take proactive steps to train your team and modernize your systems today.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online