info held Command | Command-line Debugging for UDFs | Teradata Vantage - info held - 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 displays the current hold status. If no threads are held then no status is returned.

Syntax

info held [ long ]

Syntax Elements

long
Appends a list of threads that are being held from execution.

Examples: Using the info held Command

This example shows using info held after hold all and the difference between info held and info held long:

(gdb) hold all
(gdb) i held
all
(gdb) i held long
all ->   1//6441  0//6457

This example shows using info held after a hold of specific threads:

(gdb) hold 1//6441  0//6457
(gdb) i held
( 1//6441 0//6457 )
(gdb) i held long
( 1//6441 0//6457 ) ->   1//6441  0//6457

When changes to a hold are made using the unhold command, info held long displays the original hold command parameters followed by a minus sign and a list of released threads. It also displays the resulting threads that are still held.

(gdb) hold 1//6441  0//6457
(gdb) i held long
( 1//6441 0//6457 ) ->   1//6441  0//6457
(gdb) unhold 0//6457
(gdb) i held long
( 1//6441 0//6457 ) - ( 0//6457 ) ->   1//6441