SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
RPG

RPG static code analysis

Unique rules to find Bugs, Security Hotspots, and Code Smells in your RPG code

  • All rules 58
  • Vulnerability1
  • Bug7
  • Security Hotspot1
  • Code Smell49
 
Tags
    Impact
      Clean code attribute
        1. Record formats should be cleared before each use

           Bug
        2. Related "IF/ELSEIF" statements and "WHEN" clauses in a "SELECT" should not have the same condition

           Bug
        3. Identical expressions should not be used on both sides of a binary operator

           Bug
        4. Variables should not be self-assigned

           Bug
        5. Non-input files should be accessed with the no lock option

           Bug
        6. All opened "USROPN" files should be explicitly closed

           Bug
        7. Line count data should be retrieved from the file information data structure

           Bug

        Non-input files should be accessed with the no lock option

        intentionality - complete
        reliability
        Bug

          Why is this an issue?

          When accessing a non-input-only file with a CHAIN/READx operation, the record is locked and becomes inaccessible to the system, and unreadable other programs. This is fine if you are about to update the record immediately, but if you have data processing to do following the read, it can leave the record unavailable for too long. Therefore, non-input files using the CHAIN, READ, READE, READP, and READPE operation codes should always be accessed with the no lock option, (N).

          Noncompliant code example

          FDDDLJNL7  UF   E           K DISK    INFSR(*PSSR)
          ...
          C                   READ      DDDLJNL7
          
          FDDDLJNL7  UF   E           K DISK    INFSR(*PSSR)
          ...
           /free
              read DDDLJNL7;
           /end-free
          

          Compliant solution

          FDDDLJNL7  UF   E           K DISK    INFSR(*PSSR)
          ...
          C                   READ(N)   DDDLJNL7
          
          FDDDLJNL7  UF   E           K DISK    INFSR(*PSSR)
          ...
           /free
              read(n) DDDLJNL7;
           /end-free
          
            Available In:
          • SonarQube IdeCatch issues on the fly,
            in your IDE
          • SonarQube ServerAnalyze code in your
            on-premise CI
            Enterprise
            Edition
            Available Since
            9.1

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use