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
JCL

JCL static code analysis

Unique rules to write Clean JCL Code

  • All rules 20
  • Bug7
  • Code Smell13
 
Tags
    Impact
      Clean code attribute
        1. RLSE should be used in SPACE directive

           Bug
        2. Track uses of forbidden data set names

           Code Smell
        3. Track uses of forbidden statement parameters

           Code Smell
        4. Jobs and procedures should not have too many steps

           Code Smell
        5. Incompatible parameters should not be used

           Bug
        6. COND code should be set after a certain step

           Code Smell
        7. Avoid the use of in-stream data in procedures

           Code Smell
        8. Names should not be too long

           Bug
        9. Positional parameters must precede keyword parameters

           Bug
        10. DD DATA statements should be delimited

           Code Smell
        11. The number of steps in a job should be below 255

           Bug
        12. Missing mandatory statement name

           Bug
        13. Do not use implicit SYSIN DD * statements

           Code Smell
        14. All branches in a conditional structure should not have exactly the same implementation

           Bug
        15. Track uses of disallowed programs and procedures

           Code Smell
        16. JCL parser failure

           Code Smell
        17. Job names should comply with a naming convention

           Code Smell
        18. Procedures should not be empty

           Code Smell
        19. Unused function parameters should be removed

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

           Code Smell

        Names should not be too long

        intentionality - logical
        reliability
        Bug

          Why is this an issue?

          How can I fix it?

          More Info

          If a statement name exceeds the maximum size, it will trigger an error and prevent the program from being executed.

            Available In:
          • SonarQube IdeCatch issues on the fly,
            in your IDE
          • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
          • SonarQube ServerAnalyze code in your
            on-premise CI
            Enterprise
            Edition
            Available Since
            10.5

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use