JCL

Language-specific information about the way that SonarQube Cloud supports the analysis of JCL.

JCL analysis is available starting with the Enterprise plan and is supported by SonarQube for Eclipse when running in connected mode. See the Subscription plans and Connected mode pages for more details.

For in-IDE feedback on JCL issues, install SonarQube for Eclipse and bind the project with SonarQube for IDE. Connected mode lets the IDE use the JCL quality profile and analysis settings configured in SonarQube Cloud.

Language-specific properties

To discover and update the JCL-specific properties, navigate in SonarQube Cloud to Your Project > Administration > General Settings > Languages > JCL. See Configuration overview for more information about setting properties.

Source code extraction

To analyze your source code with SonarQube Cloud, you first need to extract it onto a filesystem. You can use your own tool or an open-source tool; Sonar does not provide any connectors or source code extraction tools.

JCL source format

Depending on your extraction process, your JCL source files may include extra characters beyond the 72nd columns, and include the 8 additional characters up to column 80, or even go beyond that column.

When that happens, the parser will:

• consider everything up to the 71st column as valid JCL code,

• look at the character in the 72nd column, to determine whether a continuation is present or not,

• consider everything beyond the 72nd column as an inline comment, even when the text goes beyond the 80th column.