When you edit the loader connection in a session, you can override the control file. You might want to override the control file to change some loader properties that you cannot edit in the loader connection. For example, you can specify the tracing option in the control file.
When you override the control file, the Workflow Manager saves the control file to the repository. The Integration Service uses the saved control file when you run the session and for each subsequent session run until you clear the control file attribute. If you change a target or loader connection setting after you edit the control file, the control file does not include those changes. To include those changes, you must generate the control file again and edit it.
If you do not override the control file, the Integration Service generates a new control file based on the session and loader properties each time you run a session. The Integration Service generates the control file in the output file directory. It overwrites each time you run the session.
The Workflow Manager does not validate the control file syntax. Teradata verifies the control file syntax when you run a session. If the control file is invalid, the session fails.
You can view the edited control file by opening the Control File Editor.
To override a control file:
In the Workflow Manager, open the session properties.
Click the Mapping tab and open the Transformations view.
Click the Targets node.
In the Connections settings, in the Value field, click Change.
In the Control File Content Override field, click Open.
The Control File Editor dialog box appears.
The Workflow Manager generates the control file based on the session and loader properties.
Edit the generated control file and click OK to save the changes.