On a Windows system, use the following procedure to the Teradata Access Module for Named Pipes with client load and unload utilities, such as FastLoad or FastExport.
Named pipes follow the Microsoft Universal Naming Convention (UNC) for networked entities:
\\system_name\pipe_name
Specifying the system name as part of the pipe name enables data transfer between networked systems. Using a period character (.) as the system_name specifies the local system. Unlike UNIX, named pipes on Windows are not persistent. The access module creates them automatically, and they are destroyed when the access module closes them.
- Program the reader process to specify the Teradata Access Module for Named Pipes, as in the following FastLoad script example:
axsmod np_AXSMOD.dll “fallback_directory=...”; define file=\\.\pipe\mypipe...; - Program the writer process to send its output stream to the named pipe, as in the following Fast Export script example:
.EXPORT OUTFILE \\.\pipe\mypipe;
- Launch the reader and writer process from two different command windows (CMD.EXE).On Windows systems, the reader process must be running and in the wait mode for a pipe read operation before you launch the writer process. The FastLoad utility, for example, indicates this status by displaying: Starting to send to RDBMS with record 1.
- To launch FastLoad in one command window, enter the following, where flod.cmd is the name of your FastLoad job script file:fastload <flod.cmd
- Wait until FastLoad has initialized and is ready for a pipe read operation.
- To launch FastExport in another command window, enter the following:fexp <fexp.cmd
- To launch FastLoad in one command window, enter the following, where flod.cmd is the name of your FastLoad job script file: