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: 3 rules found
error-handling
    Impact
      Clean code attribute
        1. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        2. Indicators should be used on "CHAIN" statements

           Code Smell
        3. Error handling should be defined in F specs

           Code Smell

        Error handling should be defined in F specs

        intentionality - complete
        maintainability
        Code Smell
        • error-handling

        Why is this an issue?

        Error handling should be defined on file operations to ensure correct processing of program failures rather than defaulting to an abnormal program end. This rule checks two things:

        • INFSR error handling is defined on file operations.
        • error handling is delegated to an appropriately named routine.

        Noncompliant code example

        Given the default parameter value, ^*PSSR$:

             F* Noncompliant
             FIPBDCCP   IF   E           K DISK
        
             FEP210     CF   E             WORKSTN
             F                                     SFILE(EP21003S:RELN03)
        
             FEP471R1   O    E             PRINTER
             F                                     USROPN
             F                                     INFDS(W1SF01)
        

        Compliant solution

             FIPBDCCP   IF   E           K DISK    INFSR(*PSSR)
        
             FEP210     CF   E             WORKSTN INFSR(*PSSR)
             F                                     SFILE(EP21003S:RELN03)
        
             FEP471R1   O    E             PRINTER INFSR(*PSSR)
             F                                     USROPN
             F                                     INFDS(W1SF01)
        
          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