TR_ENABLE_INTERRUPT= LIBNAME Statement Option

Allows interruption of any long-running SQL processes that are involved in creating the result set or spool file.

Valid in:	SAS/ACCESS LIBNAME statement
Category:	Data Set Control
Default:	NO
Restriction:	Valid for only Windows and UNIX platforms
Data source:	Teradata

Table of Contents

Syntax

TR_ENABLE_INTERRUPT=YES | NO

Syntax Description

YES

allows interruption of long-running SQL processes that are involved in creating the result set or spool file.

NO

disables the interrupt processing code path.

Details

When set to YES, here is how you can use this option:

to interrupt any SELECT SQL statement that was submitted by using the SELECT * FROM CONNECTION as a pass-through statement
by using the Interrupt/Attention button to interrupt a query that you submitted through a DATA STEP, through PROC SQL implicit pass-through, or through explicit pass-through

Once the result set or spool file forms on the Teradata server and SAS is fetching the results, it is likely that the interrupt might no longer be available. You must wait until all results are fetched. The interrupt works in only one of these cases:

when the Teradata server is building the result set or spool file
if the Teradata server is in a wait state before building the result set or spool file because of locking

Example

libname x teradata user=myusr1 pass=mypwd1
  TR_ENABLE_INTERRUPT=YES server=mysrv1;

data _NULL_; set x.paul_test; run;

proc datasets lib=x; quit;

proc sql;
create table work.a as select * from x.td_cancel, x.td_cancel;
quit;

proc sql; connect to teradata (user=myusr1 pass=mypwd1
  TR_ENABLE_INTERRUPT=YES server=mysrv1);
select * from connection to teradata
  ( select * From td_cancel a , td_cancel b );
quit;

Last updated: February 3, 2026