> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/languages/jcl.md).

# 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](/sonarqube-cloud/administering-sonarcloud/managing-subscription/subscription-plans.md) and [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-eclipse/connect-your-ide/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](/sonarqube-cloud/analyzing-source-code/connected-mode.md). Connected mode lets the IDE use the JCL quality profile and analysis settings configured in SonarQube Cloud.

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

To discover and update the JCL-specific properties, navigate in SonarQube Cloud to *Your Project* > **Administration** > **General Settings** > **Languages** > **JCL**. See [Configuration overview](/sonarqube-cloud/analyzing-source-code/analysis-parameters/configuration-overview.md) for more information about setting properties.

## Source code extraction <a href="#source-code-extraction" id="source-code-extraction"></a>

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 <a href="#jcl-source-format" id="jcl-source-format"></a>

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/languages/jcl.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.