DataConnector Operator Events

Teradata Parallel Transporter Reference

Product

Parallel Transporter

Release Number

15.00

Language

English (United States)

Last Update

2018-09-27

dita:id

B035-2436

lifecycle

Product Category

Teradata Tools and Utilities

The following table lists the event codes and describes the data that the Data Connector operator passes to the notify exit routine for each event. The information in this table is also sent to the system log.

Note: To support future enhancements, always verify that your notify exit routines ignore invalid or undefined event codes, and that they do not cause the operator to terminate abnormally.

Table 49: DataConnector Operator Event Codes
		Notification Level
Event Code	Event	Low	Med	High	Event Description
0	Initialize	Yes			Signifies successful processing of the notify feature. Operator handle ‑ 4-byte unsigned integer Operator number ‑ 4-byte unsigned integer Operator count ‑ 4-byte unsigned integer Utility ID - 4 byte unsigned integer Task ID - 32-character (maximum) array Time stamp - 26-character (fixed size) array with the format YYYY‑MM‑DDbHH:MM:SS.SSSSSS The following offset fields contain the byte offsets to data items in the event record that are null terminated strings. Given the address of the event record, the address of each data item's string can be obtained from its offset. Job ID offset - 4-byte unsigned integer Version ID offset - 4-byte unsigned integer Utility name offset - 4-byte unsigned integer User string offset - 4-byte unsigned integer
1	Directory Scan Complete			Yes	Signifies successful processing of a scan for file names in a directory. Operator number - 4-byte unsigned integer Task name - 32-character (maximum) array File count - 4-byte unsigned integer Time stamp - 26-character (fixed size) array with the format YYYY-MM-DDbHH:MM:SS.SSSSSS The following offset fields contain the byte offsets to data items in the event record that are null terminated strings. Given the address of the event record, the address of such a string can be obtained from the offset. Script name offset - 4-byte unsigned integer Job name offset - 4-byte unsigned integer Job ID offset - 4-byte unsigned integer File list offset - 4-byte unsigned integer (Note: there are “File Count” NULL terminated file name strings arranged end-to-end in the file list)
2	File Read Complete			Yes	Signifies successful processing of a file in the file list. Operator number - 4-byte unsigned integer Task ID - 32-character (maximum) array Record count - 4-byte unsigned integer File size - 4-byte unsigned integer The following offset fields contain the byte offsets to data items in the event record that are null terminated strings. Given the address of the event record, the address of such a string can be obtained from the offset. Script name offset - 4-byte unsigned integer Job name offset - 4-byte unsigned integer Job ID offset - 4-byte unsigned integer File name offset - 4-byte unsigned integer
3	Checkpoint			Yes	Signifies successful processing of a checkpoint. Operator number - 4-byte unsigned integer Task ID - 32-character (maximum) array The following offset fields contain the byte offsets to data items in the event record that are null terminated strings. Given the address of the event record, the address of such a string can be obtained from the offset. Script name offset - 4-byte unsigned integer Job name offset - 4-byte unsigned integer Job ID offset - 4-byte unsigned integer
4	Terminate	Yes			Signifies successful termination of the notify feature. Operator number - 4-byte unsigned integer Task ID - 32-character (maximum) array Return code - 4-byte unsigned integer Time stamp - 26-character (fixed size) array with the format YYYY-MM-DDbHH:MM:SS.SSSSSS