Our rules consider the length of variable names (not constrained to 8 character puzzle boxes anymore). We consider the proper declaration of parameters to protect them from unintended changes. We consider the use of qualified names for things like variables and data structures, monitor blocks, variable length fields, and more. ARCAD not only laid these out in an easy to follow document, but implemented all of the rules and rule sets in Code Checker, so you can stack these rules up to your own code with a few clicks.
No solution is one-size-fits-all, of course. ARCAD recognizes that. That’s why, with the flexibility of Code Checker, you can selectively apply these rules to your code any way you want. They can (and should) apply only to RPGLE. They may only point to specified libraries, and be disabled or enabled at any severity level you want. We give you the suggestions, but you’re in control.
We also continue to look to expand these rules. RPG is a changing language, after all.
Finally, in being state of the art, Code Checker is fully compatible with ILE based, Git solutions. This includes compatibility with Git’s new Delta Mode. Our rules aid anything from traditional source members to the bleeding edge in iSeries development. This is a tool that can grow with you.
As business continues to evolve, so does the need for more powerful, simpler code that’s well written and easy to maintain. ARCAD’s Code Checker helps your business realize those goals by doing the heavy lifting of defining best practices and helping you to identify them in your code. Code written to good, modern practices will be more easily maintained in the future, making your business more agile and your developers more able to quickly make changes and diagnose issues.
We provide you these rules and put this power in your hands.