Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 5: Using INMOD and Notify Exit Routines Overview Table 34: NOTIFY EXIT Routine Notify Exit Routine Language IBM C on z/OS platforms z/OS platform C on UNIX and Windows platforms Entry Point _dynamn DYNAMN _dynamn The Teradata TPump/INMOD Routine Interface Teradata TPump exchanges information with an INMOD routine by using the conventional parameter register to point to a parameter list of two 32-bit addresses. The first 32-bit address points to a three-value structure consisting of status code, length, and body. The second 32-bit address points to a data structure containing a sequence number and a parameter list. Status Code Status Code is a 32-bit signed binary value that carries information in both directions. Table 35 lists Teradata TPump-to-INMOD interface uses eight status codes, as defined in the table. Table 35: Teradata TPump-to-INMOD Status Codes Value Description 0 Teradata TPump is calling for the first time and expects the INMOD routine to return a record. At this point, the INMOD routine should perform its initialization tasks before sending a data record to Teradata TPump. 1 Teradata TPump is calling, not for the first time and expects the INMOD routine to return a record. 2 The client system has been restarted, the INMOD routine should reposition to the last checkpoint, and Teradata TPump is not expecting the INMOD routine to return a data record. Note: If the client system restarts before the first checkpoint, Teradata TPump sends entry code 0 to re-initialize. Repositioning information, provided by the INMOD after a code 3, is read from the restart log table and returned in the buffer normally used for the data record. 3 A checkpoint has been written, the INMOD routine should remember the checkpoint position, and Teradata TPump does not expect the INMOD routine to return a data record. In the buffer normally used to return data, the INMOD should return any information (up to 100 bytes) needed to reposition to this checkpoint. The utility saves this information in the restart log table. 206 Teradata Parallel Data Pump Reference
Chapter 5: Using INMOD and Notify Exit Routines Overview Table 35: Teradata TPump-to-INMOD Status Codes (continued) Value Description 4 Teradata Database has failed, the INMOD routine should reposition to the last checkpoint, and Teradata TPump is not expecting the INMOD routine to return a data record. Note: If the database restarts before the first checkpoint, Teradata TPump sends entry code 5 for cleanup, and then it sends entry code 0 to re-initialize. Teradata TPump reads the repositioning information, provided by the INMOD after a code 3, from the restart log table and returned to the INMOD in the buffer normally used for the data record. 5 The Teradata TPump job has ended and the INMOD routine should perform any required cleanup tasks. 6 The INMOD should initialize and prepare to receive records. 7 The next record is available for the INMOD. Table 36 explains the two status codes used by the INMOD-to-Teradata TPump interface. Table 36: INMOD-to-Teradata TPump Interface Status Codes Value Description 0 A record is being returned as the body value for a read call (code 1). For calls other than read, a value of 0 indicates successful completion. Any nonzero value The INMOD routine is at an end-of-file condition for a read call (code 1). For calls other than read, a nonzero value indicates a processing error that terminates Teradata TPump. Length Length is the 32-bit binary value that the INMOD routine uses to specify the length, in bytes, of the data record. The INMOD routine can use a length value of zero to indicate an end-offile condition. Body Body is the area where the INMOD routine places the data record. Maximum record length is 31K or 31,744 bytes for Teradata for Windows. Maximum record length for Teradata Database for UNIX is 62K or 63,488 bytes. Sequence Number Sequence number is a 4-byte integer record counter portion of the source sequence number. Parameter List The parameter list in the second 32-bit address consists of the following: • VARCHAR specification Teradata Parallel Data Pump Reference 207
Page 1 and 2:
Teradata Parallel Data Pump Referen
Page 3 and 4:
Preface Purpose This book provides
Page 5 and 6:
Preface Additional Information Date
Page 7 and 8:
Table of Contents Preface. . . . .
Page 9 and 10:
Table of Contents Teradata TPump St
Page 11 and 12:
Table of Contents Teradata TPump/No
Page 13 and 14:
List of Tables Table 1: Teradata TP
Page 15 and 16:
CHAPTER 1 Overview This chapter pro
Page 17 and 18:
Chapter 1: Overview Teradata TPump
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Chapter 1: Overview Operating Featu
Page 25 and 26:
Chapter 1: Overview Operating Featu
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Chapter 1: Overview The Teradata TP
Page 35 and 36:
Chapter 1: Overview The Teradata TP
Page 37 and 38:
CHAPTER 2 Using Teradata TPump This
Page 39 and 40:
Chapter 2: Using Teradata TPump Inv
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Chapter 2: Using Teradata TPump Ter
Page 53 and 54:
Chapter 2: Using Teradata TPump Res
Page 55 and 56:
Chapter 2: Using Teradata TPump Res
Page 57 and 58:
Chapter 2: Using Teradata TPump Pro
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Chapter 2: Using Teradata TPump Wri
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Chapter 2: Using Teradata TPump Vie
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Chapter 2: Using Teradata TPump Mon
Page 83 and 84:
Chapter 2: Using Teradata TPump Mon
Page 85 and 86:
Chapter 2: Using Teradata TPump Est
Page 87 and 88:
Chapter 2: Using Teradata TPump Est
Page 89 and 90:
CHAPTER 3 Teradata TPump Commands T
Page 91 and 92:
Chapter 3: Teradata TPump Commands
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156: Chapter 3: Teradata TPump Commands
Page 195 and 196: CHAPTER 4 Troubleshooting This chap
Page 197 and 198: Chapter 4: Troubleshooting Error Me
Page 199 and 200: Chapter 4: Troubleshooting Reading
Page 201 and 202: Chapter 4: Troubleshooting Reading
Page 203 and 204: CHAPTER 5 Using INMOD and Notify Ex
Page 205: Chapter 5: Using INMOD and Notify E
Page 209 and 210: Chapter 5: Using INMOD and Notify E
Page 229 and 230: APPENDIX A How to Read Syntax Diagr
Page 231 and 232: Appendix A: How to Read Syntax Diag
Page 233 and 234: Appendix A: How to Read Syntax Diag
Page 235 and 236: APPENDIX B Teradata TPump Examples
Page 237 and 238: Appendix B: Teradata TPump Examples
Page 247 and 248: APPENDIX C INMOD and Notify Exit Ro
Page 249 and 250: Appendix C: INMOD and Notify Exit R
Page 257 and 258:
APPENDIX D User-Defined-Types and U
Page 259 and 260:
Appendix D: User-Defined-Types and
Page 261 and 262:
Glossary A abend: Abnormal END of a
Page 263 and 264:
Glossary data loading: The process
Page 265 and 266:
Glossary join: result. A SELECT ope
Page 267 and 268:
Glossary script: or job. A file tha
Page 269 and 270:
Glossary z/OS (MVS (Multiple Virtua
Page 271 and 272:
Index Symbols - 46 &SYSAPLYCNT syst
Page 273 and 274:
Index function 30 syntax 186 usage
Page 275 and 276:
Index FastLoad 215 IBM interface 21
Page 277 and 278:
Index reduced print output runtime
Page 279 and 280:
Index THRU keyword IMPORT command 1
show all

Teradata Parallel Data Pump

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?