UNIX Systems - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
15.00
Language
English (United States)
Last Update
2018-09-27
dita:id
B035-2436
lifecycle
previous
Product Category
Teradata Tools and Utilities

UNIX Systems

Solaris Running on a SPARC System

Use the following syntax to compile source files into a shared object module for notify exit routines on Solaris running on SPARC systems:

where:

 

Table 51: UNIX Operating System Syntax for Notify Exit Routines 

Syntax Element

Description

cc

Call to the program that invokes the native UNIX C compiler.

-G

Linker option that generates a shared object file.

-KPIC

Compiler option that generates Position Independent Code (PIC) for all notify exit routines.

-o

Switch to the linker.

shared-object-name

Name of your shared object file. The shared-object-name can be any valid UNIX file name.

This is the name you specify in the NotifyExit attribute value supplied in the operator definition section of a job script.

Note: When creating a shared object module for a notify exit routine, if the notify exit routine uses functions from an external library, then that library must be statically linked with the notify exit routine so that Teradata PT can resolve the external references.

sourcefile

UNIX file name(s) of the source file(s) for your notify exit routine.

HP-UX

Use the following syntax to compile and link source files into a shared object module for notify exit routines on HP-UX client systems:

Compile Syntax

Link Syntax

where:

 

Table 52: HP-UX Syntax for Notify Exit Routines 

Syntax Element

Description

-Aa

Compiler option which enables compiler to conform to the ANSI standard.

-b

Linker option that generates a shared object file.

-c

Compile-only option (does not link).

cc

Call to the program that invokes the native UNIX C compiler.

-D_HPUX_
SOURCE

Symbol that enables the compiler to access macros and typedefs that are not defined by the ANSI Standard but are provided by the HPUX Operating System.

ld

Call to the program that invokes the native UNIX linker.

objectfile

File that the compiler generates and linker uses to generate shared-object-name.

-o

Switch to the linker.

shared-object-name

Name of your shared object file. The shared-object-name can be any valid UNIX file name.

This is the name you specify in the NotifyExit attribute value supplied in the operator definition section of a job script.

Note: When creating a shared object module for a notify exit routine, if the notify exit routine uses functions from an external library, then that library must be statically linked with the notify exit routine so that Teradata PT can resolve the external references.

+z

Compiler option that generates Position Independent Code for all notify exit routines.

sourcefile

UNIX file name(s) of the source file(s) for your notify exit routine.

+ul

Compiler option that allows pointers to access non-natively aligned data.

Linux

Use the following syntax to compile source files into a shared object module for notify exit routines on Linux client systems:

where:

 

Table 53: Linux Syntax for Notify Exit Routines 

Syntax Element

Description

gcc

Call to the program that invokes the gcc compiler.

-shared

Link option that generates a shared object file.

-o

Switch to the link option.

shared-object-name

Any valid file name to serve as the name of the shared object file.

Specify this name in the NotifyExit attribute value supplied in the operator definition section of a job script.

Note: When creating a shared object module for a notify exit routine, if the notify exit routine uses functions from an external library, then that library must be statically linked with the notify exit routine so that Teradata PT can resolve the external references.

sourcefile

File name(s) of the source file(s) for a notify exit routine.

IBM AIX

Use the following syntax to compile and link source files into a shared object module for notify exit routines on IBM AIX client systems:

Compile Syntax

Link Syntax

where:

 

Table 54: IBM AIX Syntax for Notify Exit Routines 

Syntax Element

Description

-be:
export_dynamn.txt

Linker option that exports the symbol "_dynamn" explicitly and the file export-dynamn.txt contains the symbol.

-bexpall

Option that exports all global symbols, except imported symbols, un-referenced symbols defined in archive members, and symbols beginning with an underscore (_).

-brtl

Option that tells the linkage editor to accept both .so and .a library file types.

-c

Compiler option specifying to not send object files to the linkage editor.

cc

Call to the program that invokes the native UNIX C compiler.

-e_dynamn

Option that sets the entry point of the notify exit routine to _dynamn.

-fPIC

Compiler option that generates Position Independent Code for all notify exit routines.

-G

Option that produces a shared object-enabled for use with the runtime linker.

-lc

Link with the /lib/libc.a library.

ld

Call to the program that invokes the native UNIX linker.

-lm

Link with the /lib/libc.a library.

-o

Switch to the linker.

objectfile

File that the compiler generates and linker uses to generate shared-object-name.

shared-object-name

The shared-object-name can be any valid UNIX file name.

This is the name you specify in the NotifyExit attribute value supplied in the operator definition section of a job script.

When creating a shared object module for a notify exit routine, if the notify exit routine uses functions from an external library, then that library must be statically linked with the notify exit routine so that Teradata PT can resolve the external references.

sourcefile

UNIX file name(s) of the source file(s) for your notify exit routine.

IBM OS z/OS

Use:

  • JCL member PT$NTFYX in SAMPLIB to compile and link the Notify Exits, or
  • The following syntax from the shell or OMVS to compile and link source files to a DLL:
  • cc -o "//'MVS.PDSE.LOAD(module_name)' " 
          "//'MVS.PDSE.C(source_name.c)' " -W c,dll,expo -W l,dll

    where:

     

    Table 55: z/OS Syntax for Notify Exit Routines 

    Syntax Element

    Description

    -o

    Name of the executable load module that is produced during the link-edit phase.

    In the following example, a load module named INMOD is placed in a z/OS PDSE named PDSE.LOAD, and the source code, INMOD, is compiled as a member of a z/OS PDSE named TEST.C:

    cc -o "//'PDSE.LOAD(IMNMOD)" "//'TEST.C(INMOD)" -W c,dll,expo -W l,dll

    Member names are limited to eight characters.

    -W c,dll,expo

    Options passed to the compiler phase to indicate that the source is to be compiled as a dll with all functions exported.

    -W l,dll

    Options passed to the link-edit phase to indicate that the module are linked as a dll.