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

        All opened "USROPN" files should be explicitly closed

        intentionality - complete
        reliability
        Bug
        • cwe

        Why is this an issue?

        More Info

        If a file is defined without the USROPN statement then the natural RPG logic will deal with opening and closing it. However, files defined with USROPN, must be both explicitly OPENed and CLOSEd.

        Noncompliant code example

        FEWPCCR1   O    E             PRINTER USROPN
        F                                     INFDS(WSFD01)
        F                                     INFSR(*PSSR)
        
        C                   OPEN      EWPCCR1
        
        C                   CLOSE     *ALL
        
        FEWPCCR1   O    E             PRINTER USROPN
        F                                     INFDS(WSFD01)
        F                                     INFSR(*PSSR)
        
         /free
          open  EWPCCR1;
          close *ALL;
         /end-free
        

        Compliant solution

        FEWPCCR1   O    E             PRINTER USROPN
        F                                     INFDS(WSFD01)
        F                                     INFSR(*PSSR)
        
        C                   OPEN      EWPCCR1
        
        C                   CLOSE     EWPCCR1
        
        FEWPCCR1   O    E             PRINTER USROPN
        F                                     INFDS(WSFD01)
        F                                     INFSR(*PSSR)
        
         /free
          open  EWPCCR1;
          close EWPCCR1;
         /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