+---------+---------+---------+---------+---------+---*** Exiting BTEQ...

Ending BTEQ Thu Jan 18 15:03:42 1996

The JES2 LOG output follows. Note the second, third and fourth lines. The three
messages are
written when a queue is used:
TRDF0001I, indicates that the job is waiting for a queue whose QNAME is TRDFEQUE
and whose RNAME is sighsighsighsigh .
TRDF0002I, indicates that the queue is now held by the job. It is possible that
the job
might block for an indefinite period of time between the TRDF000 and TRDF0002I
messages.
TDRF0003I, indicates that the job is releasing the queue. These messages can hel
p users of
the QUEUE feature debug their jobs.
J E S 2 J O B L O G -- S Y S T E M M V S 2 -- N O D E T E R M V S 2
15.03.29 JOB 3207 $HASP373 BTEQTEST STARTED - INIT 42 - CLASS A - SYS
MVS2
15.03.41 JOB 3207 +TRDF0001I BTEQTEST ENQ - Q=TRDFEQUE
R=sighsighsighsigh
15.03.41 JOB 3207 +TRDF0002I BTEQTEST ENQ - Q=TRDFEQUE
R=sighsighsighsigh
15.03.42 JOB 3207 +TRDF0003I BTEQTEST DEQ - Q=TRDFEQUE
R=sighsighsighsigh
15.03.42 JOB 3207 BTEQTEST.STEP01 . RC=ZERO T=0000 D=0210
MT=.17S ET=012S
15.03.42 JOB 3207 BTEQTEST ENDED. NAME=CHARLES EUBANKS TOTAL
MT=.17S ET=012S
15.03.42 JOB 3207 $HASP395 BTEQTEST ENDED
------ JES2 JOB STATISTICS -----18 JAN 96 JOB EXECUTION DATE
38 CARDS READ
163 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
9 SYSOUT SPOOL KBYTES
0.21 MINUTES EXECUTION TIME
*** Query completed. 5 rows found. 24 columns returned.
Example 2 - MVS
This example uses the MSG option.
The SYSPRINT is as follows:
TERADATA CORPORATION BTEQ 5.3.0 Thu Jan 18 15:05:11 1996
+---------+---------+---------+---------+---------+---/***************************************/
/* just a little test program... */
/***************************************/
.WIDTH 80
+---------+---------+---------+---------+---------+---.LOGON tdri/cme,
Chapter 5: BTEQ Commands
NOTIFY
Basic Teradata Query Reference 195
*** Logon successfully completed.
*** Total elapsed time was 0.65 seconds.
+---------+---------+---------+---------+---------+---.set notify low msg this is a test ;
+---------+---------+---------+---------+---------+---.if errorcode <> 0 then .quit errorcode;
+---------+---------+---------+---------+---------+---sel * from cme.foo;
*** Query completed. 4 rows found. One column returned.

*** Total elapsed time was 0.17 seconds.

96/01/18 sel * from cme.foo; Page
1
a
----------2
4
1
3
+---------+---------+---------+---------+---------+---.LOGOFF
*** You are now logged off from the DBC.
+---------+---------+---------+---------+---------+---*** Exiting BTEQ...
Ending BTEQ Thu Jan 18 15:05:12 1996
The JES2 LOG output follows. The TRDF0010I message is the MSG output, thus it co
ntains
the user-provided string this is a test :
J E S 2 J O B L O G -- S Y S T E M M V S 2 -- N O D E T E R M V S 2
15.05.06 JOB 3214 $HASP373 BTEQTEST STARTED - INIT 42 - CLASS A - SYS
MVS2
15.05.11 JOB 3214 +TRDF0010I this is a test - BTEQ request complete.
15.05.12 JOB 3214 BTEQTEST.STEP01 . RC=ZERO T=0000 D=0214
MT=.16S ET=5.5S
15.05.12 JOB 3214 BTEQTEST ENDED. NAME=CHARLES EUBANKS TOTAL
MT=.16S ET=5.6S
15.05.12 JOB 3214 $HASP395 BTEQTEST ENDED
------ JES2 JOB STATISTICS -----18 JAN 96 JOB EXECUTION DATE
38 CARDS READ
182 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
9 SYSOUT SPOOL KBYTES
0.10 MINUTES EXECUTION TIME
Example 3 - Windows
This example uses a user-loadable module called btnfyext.dll. The module is buil
t from
btnfyext.c, which is included with a makefile in the BTEQ distribution as an exa
mple.
c:\teradata\bin>bteq
Teradata BTEQ 04.00.01.00 for WIN32. Enter your logon or BTEQ command:
.logon weekly
Chapter 5: BTEQ Commands
NOTIFY
196 Basic Teradata Query Reference
.logon weekly
Password:
***Logon successfully completed.
***Transaction Semantics are BTET.
***Character Set Name is ASCII.
***Total elapsed time was 32 seconds.
BTEQ -- Enter your DBC/SQL request or BTEQ command:
.set notify low exit btnftext.dll
BTEQ -- Enter your DBC/SQL request or BTEQ command:
sel * from dbc.sessioninfo;
***Query completed. 7 rows found. 15 columns returned.
***Total elapsed time was 1 second.
UserName AccountName Session
WEEKLY DBC 1,2
WEEKLY DBC 1,2

WEEKLY DBC 1,2

WEEKLY DBC 1,0
WEEKLY DBC 1,2
WEEKLY DBC 1,2
WEEKLY DBC 1,2
This user-loadable module writes the parameters it passed to a file called NFYEX
IT.OUT.
After the parameter sequence, the file contains one line:
exit called @ bteq init.
Example 4 - Windows
This example uses the MEDIUM option. The BTEQ output is not included because it
is
similar to the output from EXAMPLE 7.
The NFYEXIT.OUT output file contains two lines:
exit called @ bteq request complete
exit called @ bteq notify out of scope: return code 0
Example 5 - Windows
This example uses the HIGH option, and every event that can be used. The exit is
called six
times:
exit called @ bteq init.
exit called @ bteq start request: sel * from dbc.sessioninfo; .
exit called @ bteq request complete.
exit called @ bteq fetch: statement 1, request 1 activity 7.
exit called @ bteq request processing complete: 1 requests.
exit called @ bteq notify out of scope: return code 0.
Example 6 - Windows
This example uses the MSG option. The STDOUT from BTEQ is as follows:
c:\teradata\bin>bteq
Teradata BTEQ 04.00.01.00 for WIN32. Enter your logon or BTEQ command:
.logon weekly
.logon weekly
Password:
***Logon successfully completed.
***Transaction Semantics are BTET.
***Character Set Name is ASCII.
Chapter 5: BTEQ Commands
NOTIFY
Basic Teradata Query Reference 197
***Total elapsed