> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-job-entries-reference-overview/job-job-entry/options-job-job-entry/parameters-tab.md).

# Parameters tab

![Job entry parameters tab](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-f14eb1e19ef7f8d81ff644ee6f45106bca42d639%2Fpdi_Job_Job_%20parameters_tab_w523_no_border.png?alt=media)

Enter the following information to pass parameters to the job:

| Option                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Copy results to parameters**       | Copies the results from a previous job as parameters of the job using the [Copy rows to result](http://wiki.pentaho.com/display/EAI/Copy+rows+to+result) step.                                                                                                                                                                                                                                                                                                                                                                                  |
| **Pass parameter values to sub-job** | Passes all parameters of the job down to the sub-job.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| **Parameter**                        | Specify the parameter name passed to the job.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| **Parameter to use**                 | Specify the field of an incoming record from a previous job as the parameter.If you enter a field in **Parameter to use** then **Static input value / variable** is disabled.                                                                                                                                                                                                                                                                                                                                                                   |
| **Static input value / variable**    | <p>Specify the values for the job's parameters by using one of the following methods: - Manually enter a value, for example <code>ETL Job</code>.</p><ul><li>Use a parameter to set the value, for example <strong>${Internal.Job.Name}</strong>.</li><li>Use a combination of manually specified values and parameter values, for example <code>**${FILE\_PREFIX}**\_**${FILE\_DATE}**.txt.</code></li></ul><p>If you enter a value in <strong>Static input value / variable</strong>, then <strong>Parameter to use</strong> is disabled.</p> |
| **Get Parameters**                   | Get the existing parameters associated with 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://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-job-entries-reference-overview/job-job-entry/options-job-job-entry/parameters-tab.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.