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
Filtered: 11 rules found
brain-overload
    Impact
      Clean code attribute
        1. "GOTO" statements should not be used

           Code Smell
        2. Subprocedures should not reference global variables

           Code Smell
        3. "IF" blocks should not have too many lines of code

           Code Smell
        4. "DO" blocks should not have too many lines of code

           Code Smell
        5. SQL statements should not join too many tables

           Code Smell
        6. Subroutines should not be too complex

           Code Smell
        7. Subroutines should not have too many lines of code

           Code Smell
        8. Control flow statements "IF", "FOR", "DO", ... should not be nested too deeply

           Code Smell
        9. "SELECT WHEN" clauses should not have too many lines of code

           Code Smell
        10. Expressions should not be too complex

           Code Smell
        11. Files should not have too many lines of code

           Code Smell

        "IF" blocks should not have too many lines of code

        adaptability - focused
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        IF blocks that contain too many lines of code are difficult to read and understand.

        Above a specific threshold, it is strongly advised to refactor the contents of the IF block into multiple, well-named subroutines or subfunctions, each of which focuses on a well-defined task. Those smaller subroutines will not only be easier to understand, but probably also easier to test.

          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