The name of the job.
Note: This information is required if you want to save to a repository.
| | **Job filename** | The file name of the job if it is not stored in the repository. | | **Description** | A user-defined short description of the job which is shown in the repository explorer. | | **Extended description** | A user-defined longer description of the job. | | **Status** | The status of the job. The values are **draft** and **production**. | | **Version** | A description of the version. | | **Directory** | The directory in the repository where the job is kept. | | **Created by** | The original creator of the job. | | **Created at** | The date and time when the job was created. | | **Last modified by** | The name of the last user who modified the job. | | **Last modified at** | The date and time when the job was last modified. | ## Parameters tab You can use the **Parameters** tab to define parameters for your jobs.  This table describes all of the general job properties found on the **Parameters** tab: | Option | Description | | ----------------- | ------------------------------------------------ | | **Parameter** | A user-defined parameter. | | **Default value** | The default value of the user-defined parameter. | | **Description** | A description of the parameter. | ## Settings tab The following options are available on the **Settings** tab:  | Option | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Pass batch ID?** | Select to pass the identification number of the batch to the transformation. | | **Shared objects file** | PDI uses a single shared objects file for each user. The default filename is `shared.xml` and is located in the `.kettle` directory in the user’s home directory. You can define a different shared objects file, location, and name. | ## Log tab Use the **Log** tab to specify logging settings.  This table describes all of the general job properties found on the **Log** tab: | Option | Description | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Log connection** | Specify the database connection you are using for logging. You can configure a new connection by clicking **New**. | | **Log Schema** | Specify the schema name, if supported by your database. | | **Log table** | Specify the name of the log table. f you are also using transformation logging, you must use a different table name for job logging. | | **Logging interval (seconds)** | Specify the interval in which logs are written to the table. This property only applies to Transformation and Performance logging types. | | **Log line timeout (days)** |Specify the number of days to keep log entries in the table before they are deleted. This property only applies to Transformation and Performance logging types.
If you find that data in the log table is not deleted as expected, see Log table data is not deleted for best practice information.
| | **Log size limit in lines** | Enter the limit for the number of lines that are stored in the `LOG_FIELD`. PDI stores logging for the transformation in a long text field (CLOB). This property only applies to Transformation and Performance logging types. | | **SQL button** | Generates the SQL needed to create the logging table and allows you to execute this SQL statement. | ## Transactions tab The **Transaction** tab has one option:  | Option | Description | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Make the job database transactional** |You can use this property to open one unique connection per defined and used database connection in the job. Enabling this option is required to allow a failed job to be completely rolled back. See also the option within Work with transformations.
Further information can be found in Database transactions in jobs and transformations.
| --- # Agent Instructions: 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: ``` GET https://docs.pentaho.com/pdia-data-integration/archived-merged-pages/transforming-data-with-pdi-archive/work-with-jobs/configure-job-properties.md?ask=