Preparing the Teradata Environment

To configure and use the ODBC or CLI Adapter for Teradata, the Teradata Client components must be installed and configured according to the Teradata Tools and Utilities Installation Guide. TeraGSS, ICU, and ODBC and/or CLI are required. The path to the ODBC or CLI libraries directory must be added to SYSTEM LIBRARY PATH prior to starting the server.

If you are using the z/OS server, the Teradata Channel-Attached CLI needs to be installed. Use the WebFOCUS Reporting Server browser interface to configure the Teradata Adapter.

Before starting the server, it is necessary to perform the following pre-configuration procedures when preparing the environment on z/OS.

Customize the LKEDDBTF JCL

To relink the Adapter for Teradata with Teradata libraries, relink the load module DBTFOC with the Teradata library and replace the following entry points:

• DBCHINI
• DBCHCL
• DBCHCLN
• DBCHQE

To accomplish this, edit qualif.HOME.DATA(LKEDDBTF) and then submit it. Editing instructions are provided in the same file. 

//*        Job Card Goes Here                                         
//*                                                                   
//* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
//*Purpose: Linkedit TERADATA API routines into TERADATA Adapter    * 
//*         This is required if you run applications that connect   * 
//*         to TERADATA databases.                                  * 
//*                                                                 * 
//*Substitutions:                                                   * 
//*         In the SET statements for TERAD, TARGET and HOME,       * 
//*         replace bracketed descriptions with actual values.      * 
//*                                                                 * 
//*    TARGET library must be placed ahead of HOME library in       * 
//*    STEPLIB concatenation of IRUNJCL.                            * 
//* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
//        SET  TERAD=<TERADATA PROD.CLIENT.EXP library>                   
//        SET  TARGET=<Library to receive relinked modules>             
//        SET  HOME=<Installation HOME.LOAD library>                  
//LKED    EXEC PGM=IEWL,PARM='DYNAM=DLL,CASE=MIXED,MAP,LIST=NOIMP'                               
//TERAD   DD   DISP=SHR,DSN=&TERAD                                    
//SYSLMIN DD   DISP=SHR,DSN=&HOME             
//SYSLMOD DD   DISP=SHR,DSN=&TARGET           
//SYSUT1   DD   UNIT=SYSDA,SPACE=(100,(50,50))
//SYSPRINT DD   SYSOUT=*                      
//SYSLIN   DD   *                             
  INCLUDE TERAD(DBCINI)                      
  INCLUDE TERAD(DBCHCL)
  INCLUDE TERAD(DBCHCLN) 
  INCLUDE TERAD(HSHSPB)
  INCLUDE TERAD(DBCHMODS)
  REPLACE DBCHINI 
  REPLACE DBCHCL  
  REPLACE DBCHCLN 
  REPLACE DBCHQE 
  INCLUDE SYSLMIN(DBTFOC)
  MODE AMODE(64),RMODE(ANY)
  ENTRY   CELQSTRT 
  NAME DBTFOC(R)                          
/*

where:

SET TERAD=<TERADATA PROD.CLIENT.EXP library>

Specifies the fully qualified name of the TERADATA product client library.

SET TARGET=<Library to receive relinked modules>

Specifies the fully qualified name of the load library receiving the relinked module.

SET HOME=<Installation HOME.LOAD library>

Specifies the fully qualified name of the server installation HOME.LOAD load library.

Set Up the Environment on Microsoft Windows Using ODBC or CLI

On Microsoft Windows, the Teradata environment is set up during the installation of the product.

Set Up the Environment on UNIX

You can access Teradata using the optional UNIX environment variable, ODBCINI. The ODBCINI variable points to the absolute path of the .odbc.ini file.

For example:

ODBCINI=/usr/odbc/.odbc.ini
export ODBCINI
Note: You must not use ODBCINI, if the $HOME directory contains the .odbc.ini file.

Configuring Teradata CLI and ODBC Wide API Adapters for Unicode

The Teradata CLI and ODBC Wide API adapters support Unicode UTF8 format if:

  • The Teradata client components are part of release TTU12.0 or higher.
  • The Teradata database is release 12.0 or higher and appropriate language support was enabled during the sysinit process.
  • The Teradata client components are part of release TTU14.0 or higher.
  • The Teradata database is release 14.0 or higher and appropriate language support was enabled during the sysinit process.

Contact your DBA to determine whether international language support has been enabled in your Teradata system and/or consult the Teradata documentation for details about International Character Set Support.

Note that, at the present time, when Unicode is enabled the length of a Teradata Column Name and/or TITLE cannot exceed 21 characters.