25.09.2015 Views

Teradata Parallel Data Pump

Teradata Parallel Data Pump Reference - Teradata Developer ...

Teradata Parallel Data Pump Reference - Teradata Developer ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3: <strong>Teradata</strong> T<strong>Pump</strong> Commands<br />

IMPORT<br />

Syntax Element<br />

INFILE filename<br />

HOLD<br />

FREE<br />

INMOD<br />

modulename<br />

Description<br />

Fully qualified UNIX or Windows path name for an input file on networkattached<br />

client systems<br />

If the path name has embedded white space characters, the entire path name<br />

must be enclosed in single or double quotes.<br />

To specify the INFILE filename, the data is read from the specified source. To<br />

specify the INMOD modulename, the data is passed to the specified module.<br />

Default condition to not deallocate the input tape device specified by ddname<br />

when the import operation completes on channel-attached client systems<br />

Instead, the HOLD specification deallocates the device when the entire<br />

<strong>Teradata</strong> T<strong>Pump</strong> operation completes.<br />

Deallocation of the tape input device specified by ddname when the import<br />

operation completes on channel-attached client systems<br />

When de-allocated, any attempt to open the input device, either in the same<br />

<strong>Teradata</strong> T<strong>Pump</strong> utility task or in another task within the same script,<br />

produces an undefined ddname error.<br />

The default is to not deallocate the device.<br />

Optional user-written routine for preprocessing the input data<br />

In z/OS, the modulename is the name of a load module. In UNIX and<br />

Windows, it is the pathname for the INMOD executable code file.<br />

The modulename must obey the applicable rules of the external system.<br />

A modulename must obey the same construction rules as <strong>Teradata</strong> SQL<br />

column names except that on channel-attached client systems:<br />

• The “at” character (@) is allowed as an alphabetic character<br />

• The underscore character (_) is not allowed<br />

When both the INFILE fileid and the INMOD modulename parameters are<br />

specified, the input file is read and the data is passed to the INMOD routine<br />

for preprocessing.<br />

If the INFILE fileid parameter is not specified, the INMOD routine must<br />

provide the input data record.<br />

Note: When an INMOD routine is used with the INFILE specification,<br />

<strong>Teradata</strong> T<strong>Pump</strong> performs the file read operation, and the INMOD routine<br />

acts as a pass-through filter.<br />

Because the FDL-compatible INMOD routine must always perform the file<br />

read operation, an FDL-compatible INMOD routine cannot be used with the<br />

INFILE specification of a <strong>Teradata</strong> T<strong>Pump</strong> IMPORT command.<br />

Note: On some versions of UNIX, ./ prefix characters may have to be added<br />

to the modulename specification if the module is in the current directory.<br />

<strong>Teradata</strong> <strong>Parallel</strong> <strong>Data</strong> <strong>Pump</strong> Reference 149

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!