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
PL/I

PL/I static code analysis

Unique rules to find Bugs and Code Smells in your PL/I code

  • All rules 25
  • Bug1
  • Code Smell24
Filtered: 2 rules found
pitfall
    Impact
      Clean code attribute
        1. Keywords should not be used as variable names

           Code Smell
        2. "IF / ELSE" statements should use "DO ... END" structures

           Code Smell

        Keywords should not be used as variable names

        intentionality - clear
        maintainability
        Code Smell
        • pitfall

        Why is this an issue?

        PL/I, unlike many other programming languages, does not reserve any word’s usage.

        This implies that it is syntaxically valid to use the keyword IF as variable names for instance.

        But doing so results in confusing code which is hard to read, especially in editors without proper PL/I syntax highlighting support.

        Noncompliant code example

        foo: proc options(main);
          declare if fixed decimal init (42); /* Non-Compliant */
        
          if if = 42 then do; /* Cconfusing */
            put list ('if = 42');
          end;
        
          go to goto; /* Confusing */
        
          goto: /* Non-Compliant */
          ;
        end;
        
          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