![\"Solution](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/06\/picto-solution-ci-cd-1.png\" "\\"Solution")
<\/span><\/div>Code Quality on IBM i (aka AS\/400 or AS400)<\/span><\/h1><\/div>Monitor the health of your RPG or COBOL application<\/h2><\/div>Eliminate technical debt<\/h3><\/div><\/div><\/div><\/div><\/div>What causes technical debt on IBM i?<\/h3><\/div>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 \u2018dead code\u2019 \u2013 sometimes as much as 30% of a code base in volume \u2013 occupy valuable developer time and add to overall complexity of the system. These \u2018hotspots\u2019 generate unnecessary technical debt that can negatively impact the long-term viability of software and drain the revenue of your business.<\/p>\n
Over time, neglected applications become brittle, making them increasingly more expensive to support. In turn, enhancements become cost prohibitive, creating a vicious cycle.<\/p>\n<\/div>
![\"Vicious](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/06\/code-quality-check-technical-debt.png\" "\\"code-quality-check-technical-debt\\"")
<\/span><\/div>How to recognize brittle code?<\/h3><\/div>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.<\/p>\n
Common characteristics include:<\/p>\n<\/div>
- <\/i><\/span>\n
Monolithic programs in older RPG variants (2, 3 or 400)<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Use of \u2018fixed format\u2019 RPG, unfamiliar to a new generation of developers<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Bugs that have been there for years, in code that is \u2018too important to touch\u2019<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Dead Code: Up to 40% of your application never executed<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Over-complex code preventing the move to a Web services architecture<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Little or no documentation<\/p>\n<\/div><\/li><\/ul>
In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.<\/p>\n<\/div>
Consequences of technical debt<\/h3><\/div>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:<\/p>\n<\/div>
- <\/i><\/span>\n
Increased cost of maintenance & technical support<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Challenges in onboarding new development staff<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of business due to outages & downtime<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Integration challenges<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of Agility<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Hindered innovation<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Poor user experience<\/p>\n<\/div><\/li><\/ul>
![\"Growing](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/06\/growing-cost-of-technical-debt.png\" "\\"Growing")
<\/span><\/div><\/div><\/div><\/div><\/div>Get ARCAD CodeChecker!<\/h2><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Monitor the health of your RPG or COBOL application<\/h2><\/div>Eliminate technical debt<\/h3><\/div><\/div><\/div><\/div><\/div>What causes technical debt on IBM i?<\/h3><\/div>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 \u2018dead code\u2019 \u2013 sometimes as much as 30% of a code base in volume \u2013 occupy valuable developer time and add to overall complexity of the system. These \u2018hotspots\u2019 generate unnecessary technical debt that can negatively impact the long-term viability of software and drain the revenue of your business.<\/p>\n
Over time, neglected applications become brittle, making them increasingly more expensive to support. In turn, enhancements become cost prohibitive, creating a vicious cycle.<\/p>\n<\/div>
<\/span><\/div>How to recognize brittle code?<\/h3><\/div>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.<\/p>\n
Common characteristics include:<\/p>\n<\/div>
- <\/i><\/span>\n
Monolithic programs in older RPG variants (2, 3 or 400)<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Use of \u2018fixed format\u2019 RPG, unfamiliar to a new generation of developers<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Bugs that have been there for years, in code that is \u2018too important to touch\u2019<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Dead Code: Up to 40% of your application never executed<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Over-complex code preventing the move to a Web services architecture<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Little or no documentation<\/p>\n<\/div><\/li><\/ul>
In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.<\/p>\n<\/div>
Consequences of technical debt<\/h3><\/div>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:<\/p>\n<\/div>
- <\/i><\/span>\n
Increased cost of maintenance & technical support<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Challenges in onboarding new development staff<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of business due to outages & downtime<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Integration challenges<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of Agility<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Hindered innovation<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Poor user experience<\/p>\n<\/div><\/li><\/ul>
<\/span><\/div><\/div><\/div><\/div><\/div>Get ARCAD CodeChecker!<\/h2><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Eliminate technical debt<\/h3><\/div><\/div><\/div><\/div><\/div>What causes technical debt on IBM i?<\/h3><\/div>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 \u2018dead code\u2019 \u2013 sometimes as much as 30% of a code base in volume \u2013 occupy valuable developer time and add to overall complexity of the system. These \u2018hotspots\u2019 generate unnecessary technical debt that can negatively impact the long-term viability of software and drain the revenue of your business.<\/p>\n
Over time, neglected applications become brittle, making them increasingly more expensive to support. In turn, enhancements become cost prohibitive, creating a vicious cycle.<\/p>\n<\/div>
<\/span><\/div>How to recognize brittle code?<\/h3><\/div>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.<\/p>\n
Common characteristics include:<\/p>\n<\/div>
- <\/i><\/span>\n
Monolithic programs in older RPG variants (2, 3 or 400)<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Use of \u2018fixed format\u2019 RPG, unfamiliar to a new generation of developers<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Bugs that have been there for years, in code that is \u2018too important to touch\u2019<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Dead Code: Up to 40% of your application never executed<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Over-complex code preventing the move to a Web services architecture<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Little or no documentation<\/p>\n<\/div><\/li><\/ul>
In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.<\/p>\n<\/div>
Consequences of technical debt<\/h3><\/div>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:<\/p>\n<\/div>
- <\/i><\/span>\n
Increased cost of maintenance & technical support<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Challenges in onboarding new development staff<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of business due to outages & downtime<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Integration challenges<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of Agility<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Hindered innovation<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Poor user experience<\/p>\n<\/div><\/li><\/ul>
<\/span><\/div><\/div><\/div><\/div><\/div>Get ARCAD CodeChecker!<\/h2><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
What causes technical debt on IBM i?<\/h3><\/div>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 \u2018dead code\u2019 \u2013 sometimes as much as 30% of a code base in volume \u2013 occupy valuable developer time and add to overall complexity of the system. These \u2018hotspots\u2019 generate unnecessary technical debt that can negatively impact the long-term viability of software and drain the revenue of your business.<\/p>\n
Over time, neglected applications become brittle, making them increasingly more expensive to support. In turn, enhancements become cost prohibitive, creating a vicious cycle.<\/p>\n<\/div>
<\/span><\/div>How to recognize brittle code?<\/h3><\/div>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.<\/p>\n
Common characteristics include:<\/p>\n<\/div>
- <\/i><\/span>\n
Monolithic programs in older RPG variants (2, 3 or 400)<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Use of \u2018fixed format\u2019 RPG, unfamiliar to a new generation of developers<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Bugs that have been there for years, in code that is \u2018too important to touch\u2019<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Dead Code: Up to 40% of your application never executed<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Over-complex code preventing the move to a Web services architecture<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Little or no documentation<\/p>\n<\/div><\/li><\/ul>
In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.<\/p>\n<\/div>
Consequences of technical debt<\/h3><\/div>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:<\/p>\n<\/div>
- <\/i><\/span>\n
Increased cost of maintenance & technical support<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Challenges in onboarding new development staff<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of business due to outages & downtime<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Integration challenges<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of Agility<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Hindered innovation<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Poor user experience<\/p>\n<\/div><\/li><\/ul>
<\/span><\/div><\/div><\/div><\/div><\/div>Get ARCAD CodeChecker!<\/h2><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
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 \u2018dead code\u2019 \u2013 sometimes as much as 30% of a code base in volume \u2013 occupy valuable developer time and add to overall complexity of the system. These \u2018hotspots\u2019 generate unnecessary technical debt that can negatively impact the long-term viability of software and drain the revenue of your business.<\/p>\n
Over time, neglected applications become brittle, making them increasingly more expensive to support. In turn, enhancements become cost prohibitive, creating a vicious cycle.<\/p>\n<\/div>
<\/span><\/div>How to recognize brittle code?<\/h3><\/div>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.<\/p>\n
Common characteristics include:<\/p>\n<\/div>
- <\/i><\/span>\n
Monolithic programs in older RPG variants (2, 3 or 400)<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Use of \u2018fixed format\u2019 RPG, unfamiliar to a new generation of developers<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Bugs that have been there for years, in code that is \u2018too important to touch\u2019<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Dead Code: Up to 40% of your application never executed<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Over-complex code preventing the move to a Web services architecture<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Little or no documentation<\/p>\n<\/div><\/li><\/ul>
In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.<\/p>\n<\/div>
Consequences of technical debt<\/h3><\/div>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:<\/p>\n<\/div>
- <\/i><\/span>\n
Increased cost of maintenance & technical support<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Challenges in onboarding new development staff<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of business due to outages & downtime<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Integration challenges<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Loss of Agility<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Hindered innovation<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Poor user experience<\/p>\n<\/div><\/li><\/ul>
<\/span><\/div><\/div><\/div><\/div><\/div>Get ARCAD CodeChecker!<\/h2><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
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.<\/p>\n
Common characteristics include:<\/p>\n<\/div>
- <\/i><\/span>\n
Monolithic programs in older RPG variants (2, 3 or 400)<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nUse of \u2018fixed format\u2019 RPG, unfamiliar to a new generation of developers<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nBugs that have been there for years, in code that is \u2018too important to touch\u2019<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nDead Code: Up to 40% of your application never executed<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nOver-complex code preventing the move to a Web services architecture<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nLittle or no documentation<\/p>\n<\/div><\/li><\/ul>
In addition, security vulnerabilities can creep into source code as IBM i database logic is exposed to external applications and devices.<\/p>\n<\/div>
Consequences of technical debt<\/h3><\/div>
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:<\/p>\n<\/div>
- <\/i><\/span>\n
Increased cost of maintenance & technical support<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nChallenges in onboarding new development staff<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nLoss of business due to outages & downtime<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nIntegration challenges<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nLoss of Agility<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nHindered innovation<\/p>\n<\/div><\/li>
- <\/i><\/span>
\nPoor user experience<\/p>\n<\/div><\/li><\/ul>
<\/span><\/div><\/div><\/div><\/div><\/div>Get ARCAD CodeChecker!<\/h2><\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div> - <\/i><\/span>
- <\/i><\/span>
![\"Picto](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/05\/pictos-modules-code-checker.png\" "\\"Picto")
<\/span><\/div>![\"Contact](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/03\/contact-us.png\")
<\/span><\/div>