Code Quality Check Solution

Code Quality on IBM i

Monitor the health of your RPG or COBOL application

Eliminate technical debt

Test Data Management Expert

Ask for your personalized demo!

Speak with our IBM i experts

Book a demo

What causes technical debt on IBM i?

Many legacy IBM i applications are burdened by areas of code that are over-complex or monolithic and difficult to maintain. At the same time, areas of ‘dead code’ – sometimes as much as 30% of a code base in volume – occupy valuable developer time and add to overall complexity of the system. These ‘hotspots’ generate unnecessary technical debt that can negatively impact the long-term viability of software and drain the revenue of your business.

Over time, neglected applications become brittle, making them increasingly more expensive to support. In turn, enhancements become cost prohibitive, creating a vicious cycle.

Vicious Cycle Of Technical Debt

How to recognize brittle code?

IBM i business applications have proven so secure and reliable over the years that they are often considered too valuable or too risky to replace. Yet their RPG or COBOL code may have been maintained by multiple developers over 20-30 years, escalating the risk of technical debt.

Common characteristics include:

  • Monolithic programs in older RPG variants (2, 3 or 400)

  • Use of ‘fixed format’ RPG, unfamiliar to a new generation of developers

  • Bugs that have been there for years, in code that is ‘too important to touch’

  • Dead Code’ – never executed, yet sometimes as high as 30%-40% of your application

  • Over-complex code preventing the move to a Web services architecture

  • Little or no documentation

In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.

Consequences of technical debt

If coding defects reach production, they can cause costly downtime and damage the reputation of your business. Unaddressed technical debt can impact an IBM i organization in multiple ways:

  • Increased cost of maintenance & technical support

  • Challenges in onboarding new development staff

  • Loss of business due to outages & downtime

  • Integration challenges

  • Loss of Agility

  • Hindered innovation

  • Poor user experience

Growing Cost of Technical Debt

How to eliminate technical debt on IBM i?

Get ARCAD CodeChecker!

  • Over 100 customizable rules for code quality checking on IBM i

  • Reduce code complexity and the risk of downtime

  • Keep maintenance cost and timescales under control

  • Ease the onboarding of new developers

  • Supports code audit and continuous quality monitoring

  • Standalone solution that can be used with any DevOps tools on IBM i

  • Integrates with RDi, automation tools such as Jenkins and SonarQube for dashboarding

  • DevSecOps: detects security vulnerabilities (SQL injection, vulnerable APIs, dynamic SQL,..)

Contact Us

Request a demo

Let’s talk about your project!

Speak with an expert

Customized Demo

Contact our experts