Use a parameter file to define parameter values that you want to update without having to edit the task.

You can create a parameter file using one of the following methods:

Use a text editor such as Notepad to create a parameter file from scratch.
For
mapping
tasks, download a parameter file template from the
Runtime Options
page.

You can use a separate parameter file for each task or maintain a single parameter file with section headings that tell

Data Integration

the scope of each parameter value.

Depending on the task type, you save the parameter file on a local machine or in a cloud hosted directory. You specify the parameter file name and directory when you configure the task.

Data Integration

reads the parameter file at the start of each task run and applies the parameter values.

You can use a parameter file to define parameter values in the following tasks:

Mapping

tasks

Define parameter values for connections in the following transformations:

Source
Target
Lookup
SQL

Define parameter values for objects in the following transformations:

Source
Target
Lookup

Also, define values for parameters in data filters, expressions, and lookup expressions.

Not all connectors support parameter files. To see if a connector supports runtime override of connections and data objects, see the help for the appropriate connector.

Data transfer

tasks

Define values for parameters in data filters, expressions, and lookup expressions.

Synchronization

tasks

Define values for parameters in data filters, expressions, and lookup expressions.

PowerCenter tasks

Define values for parameters and variables in data filters, expressions, and lookup expressions.

You can't use a parameter file in a mapping task that is based on a mapping in SQL ELT mode.