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: 2 rules found
obsolete
    Impact
      Clean code attribute
        1. Prototypes should be used

           Code Smell
        2. Subprocedures should be used instead of subroutines

           Code Smell

        Subprocedures should be used instead of subroutines

        consistency - conventional
        maintainability
        Code Smell
        • obsolete

        Why is this an issue?

        Subprocedures and subroutines are both mechanisms to segregate logic, but subprocedures are preferred for three reasons:

        • their local files and variables make maintenance faster and cleaner. They allow you to create variables without worrying about name clashes, and to change fields without worrying about negatively impacting other parts of the program.
        • their local files and variables make code reuse easy.
        • they can be called with parameters as functions, yielding clearer more readable code.

        Noncompliant code example

             D  FirstName      S             20A
             D  Initial        S              1A
             D  LastName       S             20A
             D  FullName       S             43A
        
              /free
               FirstName = 'John';
               Initial = 'A';
               LastName = 'Smith';
               EXSR SPFullName;
               DSPLY FullName;
               ...
        
               begsr SPFullName;
                 FullName = FirstName + ' ' + Initial + ' ' + LastName;
               endsr;
              /end-free
        

        Compliant solution

              /free
               DSPLY FullName('John':'A':'Smith');
               ...
              /end-free
        
             P FullName        B
             D FullName        PI            43A
             D  FirstName                    20A   Const
             D  Initial                       1A   Const
             D  LastName                     20A   Const
              /free
               return FirstName + ' ' + Initial + ' ' + LastName;
              /end-Free
             P                 E
        
          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