GLOP Mappings | Global and Persistent Data | Teradata Vantage - GLOP Mappings - Teradata Vantage - Analytics Database

SQL External Routine Programming

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2025-03-30
dita:mapPath
iiv1628111441820.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
qnu1472247494689
lifecycle
latest
Product Category
Teradata Vantageā„¢

You define GLOP mappings to map specific types of GLOP data, for example role type data or user type data. The system uses the context in which an external routine runs to map the actual data that the external routine can access.

For example, you can define a GLOP mapping for role type data. The actual GLOP data that the system maps for a specific external routine invocation depends on the current role for the user that runs the external routine. If the user does not have a role, or if there is no GLOP data for the current role for the user, the external routine has no access to role type data.

The following diagram illustrates how three different GLOP mappings can potentially map to actual data that you store in the system table.


Three GLOP mapping possibilities