> For the complete documentation index, see [llms.txt](https://open-mainframe-project.gitbook.io/mainframe-open-education-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-mainframe-project.gitbook.io/mainframe-open-education-project/chapter-2-mainframe-101-foundational-technology/job-control-language-and-system-display-and-search-facility/understanding-the-jcl-job-control-language/understanding-the-exec-statement.md).

# Understanding the EXEC Statement

**Understanding the EXEC Statement**

The **EXEC statement** serves as the starting point for each individual step within a job or procedure. Its primary role is to specify the program or procedure—whether cataloged or in-stream that the step will execute. Additionally, it provides instructions to the system on how to handle the execution of that step. A single job can include up to 255 steps

**Syntax**

//STEPNAME EXEC PGM=program-name

* **STEPNAME**: A unique label for the step.
* **PGM**: The name of the program or utility to execute.

**Example**

`//STEP1 EXEC PGM=SORT`

Here, the SORT utility is executed in the first step of the job.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://open-mainframe-project.gitbook.io/mainframe-open-education-project/chapter-2-mainframe-101-foundational-technology/job-control-language-and-system-display-and-search-facility/understanding-the-jcl-job-control-language/understanding-the-exec-statement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.