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
 
Tags
    Impact
      Clean code attribute
        1. "GO TO" statements should not be used

           Code Smell
        2. DFHRESP should be used to check EIBRESP values

           Code Smell
        3. "FIXED BIN" should be preferred to "INT"

           Code Smell
        4. "INONLY" or "NONASSIGNABLE" parameters should not be written to

           Code Smell
        5. "END;" statements should have the same indentation level as their matching "PROCEDURE", "SELECT", and "DO" statements

           Code Smell
        6. The "DCL" abbreviation should not be used

           Code Smell
        7. Track parsing failures

           Code Smell
        8. Keywords should not be used as variable names

           Code Smell
        9. FIXED DECIMAL declarations should be defined with odd length

           Code Smell
        10. File names should comply with a naming convention

           Code Smell
        11. Variable names should comply with a naming convention

           Code Smell
        12. Procedure names should comply with a naming convention

           Code Smell
        13. String constants should not span multiple lines

           Code Smell
        14. Columns to be read with a "SELECT" statement should be clearly defined

           Code Smell
        15. Track breaches of an XPath rule

           Code Smell
        16. "if" statements should not be nested too deeply

           Code Smell
        17. "SELECT" statements should end with "OTHERWISE" statements

           Code Smell
        18. Track comments matching a regular expression

           Code Smell
        19. Statements should be on separate lines

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

           Code Smell
        21. "STOP" statements should not be called

           Code Smell
        22. Comments should not be nested

           Code Smell
        23. Procedures should not have too many parameters

           Code Smell
        24. Lines should not be too long

           Code Smell

        DFHRESP should be used to check EIBRESP values

        intentionality - complete
        maintainability
        Code Smell

          Why is this an issue?

          More Info

          Whenever a CICS command is used with a NOHANDE or RESP option, the default CICS exception handling is disabled. The correct approach then is to ensure that every possible exception is handled correctly directly in the code and to do this, you need to examine the RESP value or the EIBRESP field value.

          It is possible to compare the RESP and EIBRESP field values to hard-coded numbers or variables containing numeric values; however, this makes the code difficult to read and maintain. It is recommended to use instead the DFHRESP built-in translator function, which enables the use of the equivalent symbolic values.

          This rule raises an issue when the EIBRESP field is compared directly to a variable or hard-coded numeric value that is not wrapped in the DFHRESP function.

          This rule does not handle RESP values for now.

          Noncompliant code example

          if EIBRESP=36 then /* Noncompliant */
          end;
          
          if EIBRESP=MAPFAIL then /* Noncompliant */
          end;
          
          select (EIBRESP);
              when(36) ...;  /* Noncompliant */
          end;
          

          Compliant solution

          if EIBRESP=DFHRESP(36) then
          end;
          
          if EIBRESP=DFHRESP(MAPFAIL) then
          end;
          
          select (EIBRESP);
              when(DFHRESP(MAPFAIL)) ...;
          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.8

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use