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. Track uses of forbidden data set names

           Code Smell
        2. Track uses of forbidden statement parameters

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

           Code Smell
        4. COND code should be set after a certain step

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

           Code Smell
        6. DD DATA statements should be delimited

           Code Smell
        7. Do not use implicit SYSIN DD * statements

           Code Smell
        8. Track uses of disallowed programs and procedures

           Code Smell
        9. JCL parser failure

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

           Code Smell
        11. Procedures should not be empty

           Code Smell
        12. Unused function parameters should be removed

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

           Code Smell

        Do not use implicit SYSIN DD * statements

        intentionality - complete
        maintainability
        reliability
        Code Smell
        • bad-practice

        Input data that is not a JCL statement implicitly generate a DD * statement with the name SYSIN.

        Why is this an issue?

        How can I fix it?

        More Info

        This behavior is implicit and may lead to confusion or unexpected behavior.

        For example, this code:

        //MYDD DD DSN=TEST
        Some in-stream data
        // DD DSN=CONCAT-DD
        

        Gets implicitly transformed into:

        //MYDD DD DSN=TEST
        //SYSIN DD *
        Some in-stream data
        // DD DSN=CONCAT-DD
        

        So the last DD statement is a concatenation of the implicit //SYSIN DD * statement instead of the explicit //MYDD DD statement.

          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