NOTIFY | Syntax | Teradata FastLoad - Syntax - FastLoad

Teradata® FastLoad Reference

Product
FastLoad
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-06-18
dita:mapPath
ije1544831946874.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2411
lifecycle
previous
Product Category
Teradata Tools and Utilities

NOTIFY command syntax diagram

where the following is true:

OFF
Default. No notification of events is to be provided.
LOW
Notification is to be provided for those events signified by “Yes” in the Low Notification Level column of the following table.
MEDIUM
Notification is to be provided for those events signified by “Yes” in the Medium Notification Level column of the following table.
HIGH
Notification is to be provided for those events signified by “Yes” in the High Notification Level column of the following table.
EXIT
A user-written exit is to be called at the appropriate time.
name
The name of a user-supplied library with an entry point named
_dynamn.
The default library names are:
  • libnotfyext.dllfor Windows
  • libnotfyext.so for UNIX platforms
  • NOTFYEXT for z/OS platforms.
TEXT "string"
A user-supplied string of up to 80 characters that Teradata FastLoad passes to the named exit routine
The string specification must be enclosed in double-quote characters (").
MSG "string"
A user-supplied string of up to 16 characters that Teradata FastLoad logs on to:
  • The operator console on mainframe-attached z/OS client systems
  • The system log or EventLog service on workstation-attached UNIX or Windows systems
The string specification must be enclosed in double quote characters. This service is not available on Windows 98.
QUEUE
Specifies that a queue is to be manipulated via ENQ or DEQ
For more information, see Usage Notes.
This option is valid only for z/OS.
option
One of the following:
RNAME defines a quoted string of up to 255 characters. The default is TRDUSER.
SCOPE defines one of the following:
  • JOB specifies that the QUEUE is local to the job (including all of the job steps). This is the default.
  • SYSTEMS specifies that the QUEUE is global to all computers in the complex.
  • SYSTEM specifies that the QUEUE is global to the computer on which it is running.
NOBLOCK specifies that if the ENQ blocks for any reason, it must return an error instead. This is a fatal error for the job.
The default, an implied BLOCK (there is no BLOCK keyword), means that the ENQ will wait for the QUEUE.
EXIT64
A user-written exit is to be called at the appropriate time.
EXITEON
A user-written exit is to be called at the appropriate time.

The following table lists events that create notification.

Events that Create Notifications  
Event Notification Level Signifies
Low Medium High
Initialize Yes Yes Yes Successful processing of the NOTIFY command
File or INMOD open No No Yes Successful processing of the DEFINE command
Phase 1 being No Yes Yes Beginning of the insert phase, as specified by the INSERT statement
Checkpoint No No Yes Checkpoint information has been written to the restart log table
Phase 1 end No Yes Yes Successful processing of the CHECKPOINT LOADING END request after the end of the insert phase
Phase 2 begin No Yes Yes The END LOADING command is about to be sent to the database
Phase 2 end No Yes Yes Successful processing of the END LOADING command
Error table 1 No No Yes Successful processing of the SEL COUNT(*) request for the first error table
Error table 2 No No Yes Successful processing of the SEL COUNT(*) request for the second error table
Database Restart No Yes Yes A crash error from the database or CLIv2
CLIv2 error Yes Yes Yes A CLIv2 error
Database error Yes Yes Yes A database error that terminates FastLoad
Exit Yes Yes Yes FastExport is terminating