17.10 - Using the Teradata Access Module for Named Pipes with Teradata Parallel Transporter on UNIX - Access Module

Teradata® Tools and Utilities Access Module Reference

Access Module
Release Number
October 2021
English (United States)
Last Update
  1. Create a named pipe (for example /tmp/mypipe).
  2. Create a Teradata PT script that specifies /tmp/mypipe as the filename opened by the module. For example, the script tbuild.txt contains a statement similar to the following, defining the Teradata PT Data Connector Operator:
    DEFINE OPERATOR DataConnector ()
      OUTPUT SCHEMA Tab3schema
        VARCHAR FileName                = '/tmp/mypipe',
        VARCHAR PrivateLogName          = 'DcImport.log',
        VARCHAR AccessModuleName        = 'np_axsmod.so',
        VARCHAR AccessModuleInitStr     = 'ld=. fd=.',
        VARCHAR IndicatorMode           = 'N',
        VARCHAR OpenMode                = 'Read',
        VARCHAR Format                  = 'Formatted'

    The following attributes are relevant to the Teradata Access Module for Named Pipes:

    • FileName specifies the name of the named pipe.
    • AccessModuleName specifies the Teradata Access Module for Named Pipes. For example, on SPARC systems, the AccessModuleName is np_axsmod.so.
    • AccessModuleInitStr specifies the access module’s initialization string.

    All other Teradata PT Data Connector Operator attributes are transparent to the access module.

  3. Code an Export Operator script named fexp.coms containing a statement similar to the following:
    .EXPORT OUTFILE /tmp/mypipe ;
  4. Launch Export Operator and Teradata Parallel Transporter with shell commands similar to the following:
    fexp < fexp.cmds > fexp.out & tbuild -f tbuild.txt &

    In this example, UNIX connects both processes through the named pipe /tmp/mypipe.

    The Load operator can direct the access module to save a checkpoint in case the job must be restarted.