info held Command | Command-line Debugging for UDFs | Teradata Vantage - info held - Advanced SQL Engine - Teradata Database

SQL External Routine Programming

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
qwr1571437338192.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1147
lifecycle
previous
Product Category
Teradata Vantage™

Purpose

This command displays the current hold status. If no threads are held then no status is returned.

Syntax

info held [ long ]

The long option 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