join Command | Command-line Debugging for UDFs | Teradata Vantage - join - Analytics Database - Teradata Vantage

SQL External Routine Programming

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
iiv1628111441820.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1147
lifecycle
latest
Product Category
Teradata Vantageā„¢

This command joins a UDF to a debugging session.

Syntax

join sessno[/udfname] [ wait ]

Syntax Elements

sessno
The session number of the UDF to be debugged. This is typically taken from the output of a prior info udf command, but UDFs can be joined without a prior info udf command if the user already knows the number for the session to debug.
udfname
The name of a UDF waiting to be debugged. This is optional.
wait
The optional wait parameter requests that this command not complete until there is at least one UDF available to debug.

Joining a session number without specifying udfname joins any UDF debugged by that session. Joining a specific udfname only joins that UDF.

Usage Notes

At least one UDF that matches the join criteria must be waiting to be debugged when the command is entered. However, once joined, all current and future instances of the named UDF (or all UDFs) from the specified session are caught by this debugging session.

Multiple join commands can be issued to debug multiple UDFs, or even multiple database sessions. Once something is joined, though, it can only be unjoined by terminating the debugger session. Anything joined to one debugger session cannot be joined to another one until you exit the first session.