15.10 - Specifying an Access Module - Parallel Transporter

Teradata Parallel Transporter User Guide

Parallel Transporter
User Guide

Specifying an Access Module

Use the following attributes in the DataConnector operator definition to specify the optional use of an access module:

  • AccessModuleName
  • Each access module has a pre-assigned name depending on the operating system on which it is installed. For instance, the JMS access module running on HP-UX is named libjmsam.sl.

  • AccessModuleInitStr
  • Specifies the access module initialization string.

    For detailed information about configuring and using access modules with Teradata PT, see Teradata Tools and Utilities Access Module Reference.

    For information about creating custom access modules, see Teradata Tools and Utilities Access Module Programmer Guide

    z/OS Considerations

    When using access modules residing within a z/OS program library, either a PDS or a PDSE, the access module name provided to the producer operator using the AccessModuleName attribute is the member name within the library. It may be a system library, private library, or even a temporary library.

    If a system library contains the access module, no further JCL is required. However when a private or temporary library houses the access module, a JOBLIB DD statement or a STEPLIB DD statement is required within the jobstream to designate the library containing the access module. The following example shows a typical JOBLIB DD statement for a private library in a Teradata PT jobstream:



  • STV.TI70APP.TWB.LOAD is the Teradata PT installation library.
  • STV.TI70APP.APP.L is the CLI installation library.
  • PROD.TERADATA.LOAD is a private library that contains all Teradata related access modules.
  • The above is the recommended concatenation order for these libraries.