• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • ARCAD Debuts RPG Code Checker

    October 3, 2018 Alex Woodie

    If you write RPG, or know somebody who does, then you realize that mistakes can and will happen. However, beyond the obvious syntax errors, which should be detected immediately by the code editor, are instances where the code is sloppy or just poorly written. Those are the instances where ARCAD Software hopes to help with its new CodeChecker offering.

    ARCAD-CodeChecker, as the product is officially called, does just that: Detect poor quality RPG code before it makes it into production. If you’ve coded a bug into the program, made a design error, or taken 1,000 lines to write something that should have taken just 10 lines, it may not be automatically flagged by the code editor, but it’s something that ARCAD Software says can detected with CodeChecker.

    ARCAD says the new offering will use a variety of metrics to measure the quality of free-form RPG (other languages will come later). It does this, ARCAD says, by using techniques such as cyclomatic complexity which is a testing regimen devised in 1976 by Thomas McCabe Sr. to detect the linear path that each independent chunk of code takes through a program, against a backdrop of a generic control flow graph.

    Another technique used to spot bad code is to calculate the percentage of comment lines that are in the code, which could be an indication of unneeded complexity. The vendor says users can add or create other rules and metrics to detect bad code as needed, and it can all be integrated with a developer operations tool, like ARCAD’s DevOps suite, to ensure the code checks are run on a consistent basis.

    If the code is good, then the CodeChecker will log an “OK” flag. However, if there are problems with the code, then CodeChecker will use one of three flags: notice, warning, and fatal, ARCAD tells IT Jungle. (Editor’s note: You definitely don’t want to be the RPG code-slinger known for writing “fatal” flaws.)

    It’s all about utilizing DevOps processes to get cleaner code, according to Michel Mouchon, ARCAD CTO. “DevOps is all about delivering small code increments more frequently, to shorten the user feedback loop, and detect errors as early as possible in the cycle,” he in a press release. “The rule is to ‘shift left’: the earlier a software error is detected, the lower the cost of the error.”

    ARCAD’s new CodeChecker can detect poor design and overly complex code in free-format RPG.

    The focus on early detection applies not just to bugs and design errors, but also to general quality defects, Mouchon. “It explains why we attempt to automate all tasks after coding through to deployment, including continuous regression test,” he continues. “With ARCAD-CodeChecker, we are going one step further by automatically detecting poor quality code before it is even submitted for peer review.”

    CodeChecker is part of ARCAD’s DevOps Suite, and only supports IBM i languages at the moment. Eventually, it will support RPG IV (non free-form), as well as Control Language (CL) and Structured Query Language (SQL) for IBM i. The product will maintain repositories and libraries to track the data quality rules set up by the user, ARCAD says.

    Like most ARCAD products, CodeChecker can be plugged into Rational Developer for IBM i (RDi) so it can be accessed by developers without leaving their favorite integrated development environment (IDE). CodeChecker also works with version control systems, such as Jenkins, to automatically check the quality of code before the build phase begins. The software also integrates with standard Git repositories, such as GitHub, GitLab and BitBucket, which ARCAD says can increase the efficiency of the ‘pull request’ or ‘merge request.’

    “This way,” the company says, “automated code quality checking becomes part of the standard workflow. Using ARCAD-CodeChecker, developers reduce time spent in a peer review by one-third on average. Poor quality code is rejected even before a ‘commit’ operation.”

    While there’s nothing new about bad code, today’s fast-paced DevOps environment has the potential to magnify the problems posed by bad code. By nipping any problems in the bud at the code intervals defined by DevOps, IBM i shops can keep their development projects on track, according to Mouchon.

    “Careless coding increases the risk of side-effects that cause costly downtime in production,” he states. “By detecting poor quality code before it even reaches the build stage, we prevent the escalation of ‘technical debt’. Automated quality control this early in the development cycle actually secures application availability and reduces IT costs overall. This is why we see ARCAD-CodeChecker as a strategic piece of any DevOps implementation on IBM i.”

    RELATED STORIES

    Git Started With GitHub And ARCAD On IBM i (Sponsored Content)

    ARCAD Procures Funding To Fuel Expansion

    ARCAD Magnifies The i In Its Multi-Platform Array

    ARCAD And GitHub Prepare For A Paradigm Shift

    ARCAD Strengthens IBM i Modernization Portfolio

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags: Tags: CL, Control Language, DevOps, Git, GitHub, IBM i, Rational Developer for IBM i, RDi, RPG, RPG IV, SQL, Structured Query Language

    Sponsored by
    DRV Tech

    Get More Out of Your IBM i

    With soaring costs, operational data is more critical than ever. IBM shops need faster, easier ways to distribute IBM applications-based data to users more efficiently, no matter where they are.

    The Problem:

    For Users, IBM Data Can Be Difficult to Get To

    IBM Applications generate reports as spooled files, originally designed to be printed. Often those reports are packed together with so much data it makes them difficult to read. Add to that hardcopy is a pain to distribute. User-friendly formats like Excel and PDF are better, offering sorting, searching, and easy portability but getting IBM reports into these formats can be tricky without the right tools.

    The Solution:

    IBM i Reports can easily be converted to easy to read and share formats like Excel and PDF and Delivered by Email

    Converting IBM i, iSeries, and AS400 reports into Excel and PDF is now a lot easier with SpoolFlex software by DRV Tech.  If you or your users are still doing this manually, think how much time is wasted dragging and reformatting to make a report readable. How much time would be saved if they were automatically formatted correctly and delivered to one or multiple recipients.

    SpoolFlex converts spooled files to Excel and PDF, automatically emailing them, and saving copies to network shared folders. SpoolFlex converts complex reports to Excel, removing unwanted headers, splitting large reports out for individual recipients, and delivering to users whether they are at the office or working from home.

    Watch our 2-minute video and see DRV’s powerful SpoolFlex software can solve your file conversion challenges.

    Watch Video

    DRV Tech

    www.drvtech.com

    866.378.3366

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Inking A Solution To Sticky Warehouse Dilemma The Cloud Changes Things, But Not Everything

    Leave a Reply Cancel reply

TFH Volume: 28 Issue: 66

This Issue Sponsored By

  • Rocket Software
  • WorksRight Software
  • Seiden Group
  • COMMON
  • ML Software

Table of Contents

  • ARCAD Debuts RPG Code Checker
  • Inking A Solution To Sticky Warehouse Dilemma
  • Cloud Data Migration Service Launched For IBM i
  • Four Hundred Monitor, October 3
  • IBM i PTF Guide, Volume 20, Number 39

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • Meet The Next Gen Of IBMers Helping To Build IBM i
  • Looks Like IBM Is Building A Linux-Like PASE For IBM i After All
  • Will Independent IBM i Clouds Survive PowerVS?
  • Now, IBM Is Jacking Up Hardware Maintenance Prices
  • IBM i PTF Guide, Volume 27, Number 24
  • Big Blue Raises IBM i License Transfer Fees, Other Prices
  • Keep The IBM i Youth Movement Going With More Training, Better Tools
  • Remain Begins Migrating DevOps Tools To VS Code
  • IBM Readies LTO-10 Tape Drives And Libraries
  • IBM i PTF Guide, Volume 27, Number 23

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle