Use the Break key to perform the following functions:
Function |
Result |
Single-break |
Interrupts BTEQ. Enter either EXIT or QUIT to abort the transaction and terminate BTEQ. |
Double-break |
Aborts the previous request |
Triple-break |
Terminates BTEQ |
The break function has the following syntax:
where
<break> represents pressing the CTRL+C keys on your workstation keyboard.
Single-Break
The single-break function interrupts BTEQ while it is processing a previous request. BTEQ displays:
BREAK Received. Input command:
Note: For Windows BTEQ and BTEQWIN, users may need to wait for up to one minute after pressing
CTRL+C
before the BTEQ prompt "BREAK Received. Input command:
" is displayed. BTEQ displays a message "BREAK event detected. Please wait.
" when it is necessary to wait.
Double-Break
At the input command prompt, either press the Break
key again (the double-break function), or enter CONTINUE or ABORT.
Enter CONTINUE to recover from the interrupt and resume with BTEQ as if the interrupt never occurred.
Either enter ABORT or press the Break key again to abort the previous request.
Note: For Linux, Mac OS X, and BTEQWIN platforms, at the BTEQ prompt "BREAK Received. Input command:
", after pressing the second CTRL+C
, <ENTER>
may need to be pressed for the BREAK to get recognized. BTEQ displays a message "BREAK event detected. Press <ENTER>.
" when it is necessary to press the <ENTER>
key.
Triple-Break
Enter a third break to terminate BTEQ. Alternatively, entering either EXIT or QUIT after the first break also terminates BTEQ.
Note: The behavior above is for console BTEQ only. Interrupt and Abort functions are available
in BTEQWIN on the Sessions menu; CTRL+C
is undefined in BTEQWIN.
Triple-breaks can be used to end batch more or interactive mode BTEQ execution. However,
for BTEQ to recognize a triple-break scenario, the breaks (pressing CTRL+C
key) need to happen fairly quickly, or else BTEQ may recognizing them as single breaks.
So, pressing and holding down CTRL+C
can be used to effectively simulate the triple-break scenario.