15.10 - Step 3 – Launch a Script - Access Module

Teradata Tools and Utilities Access Module Reference

prodname
Access Module
vrm_release
15.10
category
Programming Reference
featnum
B035-2425-035K

Step 3 – Launch a Script

Scripts create tables and provide the commands necessary to run a job.

To launch a script

1 [Optional] Select File > Change Default Folder to change the location of the default folder for saved .amj files. The default location is C:\ My Documents.

2 After selecting a destination and at least one column of data in a source table, click File > Save As to save the file.

Notice:

Failure to save the job will result in a failed operation. (You can tell a job is saved if the .amj file name appears in the title bar of the dialog box.) Also, if you try select additional columns from a table that was already used in a successful job, an error results unless you save the newly selected columns as a new, separate .amj file.

You can save the .amj file anywhere you have write access, but it is recommended that all .amj files be stored in a single location for easy access. The default storage location of the .amj files is the local My Documents directory.

3 Click Launch, then click one of the utility options in the Launch submenu.

Selecting a utility option opens the Teradata OleLoad – <utility name> job script dialog box (basically, a text editor), which displays a script generated in response to the selections in the previous dialog box. Scripts are created as Unicode text, then converted to the session character set specified in the Advanced Settings dialog box before being passed to the Teradata utility.

4 Edit the script as needed to meet job requirements.

Note: Use CtrlC and CtrlV to copy and paste a job script to another application, if needed.

5 Click OK to run the job.

Note: Click Cancel in the progress dialog box to stop the job. The cancellation, terminates the job without completing it. All modifications to the job script are lost.

Notice:

For bulk load operations, the number of rows displayed in the progress dialog box might not be the same as the number of rows returned to the utility if a restart occurs. In this case, the progress dialog box might display a larger number of row retrievals than the number of rows actually retrieved from the data source.