Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 5: Using INMOD and Notify Exit Routines Overview Table 37: Events Passed to the Notify Exit Routine (continued) Event Event Code Event Description Data Passed to the Notify Exit Routine Interim run statistics 12 Teradata TPump is updating the Monitor Interface table, has just completed a checkpoint, or has read the last record for an import task. The returned data is the statistics for the current load • Import number—4-byte unsigned integer • Statements sent to Teradata Database—4-byte unsigned integer • Requests sent to Teradata Database—4-byte unsigned integer • Records read—4-byte unsigned integer • Records skipped—4-byte unsigned integer • Records rejected—4-byte unsigned integer • Records sent to Teradata Database—4-byte unsigned integer • Data errors—4-byte unsigned integer DML error 13 Teradata TPump received a Teradata Database error that was caused by DML and will introduce an error-row insert to the error table • Import number—4-byte unsigned integer • Error code—4-byte unsigned integer • Error message—256-character (maximum) array • Record number—4-byte unsigned integer • Apply number—1-byte unsigned char • DML number—1-byte unsigned char • Statement number—1-byte unsigned char • Record data—64,004-character (maximum) array • Record data length—4-byte unsigned integer • Feedback—a pointer to 4-byte unsigned integer “Feedback” always points to integer 0 when it is passed to the user exit routine. The user may change the value of this integer to 1 to instruct Teradata TPump not to log the error to the error table. In this case, Teradata TPump will not log the error, but continue other regular process on this error. 210 Teradata Parallel Data Pump Reference
Chapter 5: Using INMOD and Notify Exit Routines Overview Rules and Restrictions for Using Routines The following sections describe the operational rules and restrictions for using INMOD and notify exit routines in Teradata TPump jobs. Specifying Routines INMOD and notify exit routine names must be unique within the system. A Teradata TPump job can specify one INMOD routine with each IMPORT command. These specifications can be to the same or different INMOD routines. In addition to the multiple INMOD routines, each Teradata TPump job can specify an exit routine with the NOTIFY... EXIT option of the BEGIN LOAD command. Compiling and Linking Routines The methods for compiling and linking routines vary with the operating system. The following sections describe the methods for z/OS, UNIX, and Windows. Using z/OS On channel-attached z/OS client systems, INMOD and notify exit routines must be compiled under IBM C. Using UNIX On network-attached UNIX client systems, INMOD and notify exit routines must: • Be compiled with the MetaWare High C compiler • Be linked into a shared object module • Use an entry point named _dynamn Using Windows On network-attached Windows client systems, INMOD and notify exit routines must: • Be written in C • Have a dynamn entry point that is a _declspec • Be saved as a Dynamic Link Library (DLL) file For more information, see the examples in Appendix C: “INMOD and Notify Exit Routine Examples” for sample programs and procedures that compile and link INMOD and notify exit routines for the operating system environment. Addressing Mode on z/OS Systems Either 31-bit or 24-bit addressing for INMOD routines can be used on channel-attached systems. The 31-bit mode provides access to more memory, which enhances performance for Teradata TPump jobs with a large number of sessions. Use the following linkage parameters to specify the addressing mode when building INMOD routines for z/OS systems: • For 31-bit addressing: AMODE(31) RMODE(24) • For 24-bit addressing: AMODE(24) RMODE(24) Teradata Parallel Data Pump Reference 211
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:
Page 157 and 158:
Page 159 and 160: 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 and 206: Chapter 5: Using INMOD and Notify E
Page 209: 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?