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

        Prototypes should be used

        intentionality - clear
        maintainability
        Code Smell
        • convention
        • obsolete

        Why is this an issue?

        Specifying the parameters to a procedure with a PLIST makes that procedure unusable from free-format code. Instead, prototypes should be used - both when defining a procedure and when calling it. They have the additional benefit of allowing you to use keywords such as Const to better-specify how parameters are passed to a procedure. Further, the use of a prototype instead of a PLIST is cleaner and more consistent with the code required for subprocedures.

        Noncompliant code example

              * Noncompliant; PLIST specified
             C     *ENTRY        PLIST
             C                   PARM                    ZipCode           5 0
             C                   PARM                    City             20
        ...
              * Noncompliant; PLIST used in call
             C                   CALL      'OTHERPROG'
             C                   PARM                    ZipCode
             C                   PARM                    City
        

        Compliant solution

             D MYPROG          PR
             D  ZipCode                       5I   Const
             D  City                         20A   Const
             D MYPROG          PI
             D  ZipCode                       5I   Const
             D  City                         20A   Const
        ...
             D OTHERPROG       PR                  ExtPgm('OtherProgram')
             D  ZipCode                       5I   Const
             D  City                         20A   Const
              /free
                OTHERPROG(ZipCode:City);
              /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