Client-Server External Procedure Code Specification - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

You must specify whether the external procedure code for include files, object files, and source files is located on the client system or on the Teradata platform system. To do this, you specify C for client or S for server.

External procedure code for library and package files is always located on the Teradata platform, but you still must specify the S location code for any library or package file paths you specify.

The character used to separate entities in the path specification is platform-specific when the file is stored on a client system, but not when the file is on the Teradata platform.

The following table provides more information about writing the client and server location specifications for include, object, or source files.

IF you specify this location code … THEN you …
C must format the specification in the form required by the client application, for example, BTEQ.

Refer to the appropriate client documentation for information about the required form of presentation.

S can use either the SOLIDUS character (/) or the REVERSE SOLIDUS character (\) as the separator in the path specification for all platform operating systems.