Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 5: Using INMOD and Notify Exit Routines Using INMOD and Notify Exit Routines Teradata TPump/INMOD Interface This section discusses the Teradata TPump/INMOD Interface for different client operating systems: Teradata TPump/INMOD Interface on IBM Client-based Systems The use of an INMOD is specified on the IMPORT command. On IBM client-based systems, Teradata Database interfaces with INMODs written in C. Examples of these INMODs are presented in Appendix C: “INMOD and Notify Exit Routine Examples”. An optional parms string to be passed to the INMOD may also be specified on the IMPORT command. Teradata TPump imposes the following syntax rules for this string: • The parms string may include one or more character strings, each delimited on either end by apostrophes or quotation marks. The maximum size of the parms string is 1 KB. • If a FastLoad INMOD is used, the parms string of the IMPORT command must be FDLINMOD. • The parms string passed to an INMOD includes the parentheses used to specify the parm. Thus, if the IMPORT specifies USING ('5'), the entire expression ('5') is passed to the INMOD. • Parentheses within delimited character strings or comments have the same syntactical significance as alphabetic characters. • In the parms string that Teradata TPump passes to the INMOD routine, each comment is replaced by a single blank character. • In the parms string that Teradata TPump passes to the INMOD routine, each consecutive sequence of whitespace characters, such as blank, tab, and so on, that appears outside of delimited strings, is replaced by a single blank character. • FDLINMOD is used for compatibility by pointing to a data structure that is the same for BDL and FDL INMODs. Teradata TPump/INMOD Interface on UNIX-based Systems On UNIX-based client platforms, Teradata TPump is written in C and, therefore, the INMOD procedure is dynamically loaded at runtime, rather than link-edited into the Teradata TPump module or operated as a separate executable program. The runtime loader requires that the INMOD module be compiled and linked as a shared object, and that the entry point for the procedure be named _dynamn. The use of an INMOD is specified in the IMPORT command. On UNIX-based systems, Teradata Database interfaces only with INMODs written in C. An example of a C INMOD is presented in Appendix C: “INMOD and Notify Exit Routine Examples”. An optional parms string to be passed to the INMOD may also be specified on the IMPORT command. Teradata TPump imposes these syntax rules: • One INMOD is allowed for each IMPORT command. Multiple IMPORTs are allowed; these may use the same or different INMODs. • The input filename parameter specified on the IMPORT command must be the fully qualified UNIX pathname for the input file. 214 Teradata Parallel Data Pump Reference
Chapter 5: Using INMOD and Notify Exit Routines Using INMOD and Notify Exit Routines • The INMOD filename parameter specified on the IMPORT command must be the fully qualified UNIX pathname of the INMOD shared object file. • The parms string may include one or more character strings, each delimited on either end by an apostrophe, or delimited on either end by a quotation mark. The maximum size of the parms string is 1k bytes. • If a FastLoad INMOD is used, the parms string of the IMPORT command must be “FDLINMOD”. • The parms string as a whole must be enclosed in parentheses. • Parentheses within delimited character strings or comments have the same syntactical significance as alphabetic characters. • In the parms string that Teradata TPump passes to the INMOD routine, each comment is replaced by a single blank character. • In the parms string that Teradata TPump passes to the INMOD routine, each consecutive sequence of whitespace characters, such as blank, tab, and so on, that appears outside of delimited strings, is replaced by a single blank character. • FDLINMOD is used for compatibility by pointing to a data structure that is the same for FDL INMODs. Teradata TPump/INMOD Interface on Windows Systems On Windows client platforms, Teradata TPump is written in C and, therefore, the INMOD procedure is dynamically loaded at runtime, rather than link-edited into the Teradata TPump module or run as a separate executable program. The runtime loader requires that the INMOD module be compiled and linked as a Dynamic- Link Library (DLL) file, and that the point for the procedure be named _dynamn. The use of an INMOD is specified in the IMPORT command. On systems, Teradata Database interfaces only with written in C. An optional parms string to be passed to INMOD may also be specified on the IMPORT command. Teradata TPump imposes the following syntax rules: • One INMOD is allowed for each IMPORT command. Multiple are allowed; these may use the same or different INMODs. • The input filename parameter specified on the IMPORT command must be the fully qualified Windows pathname for the input file. • The INMOD filename parameter specified on the IMPORT command must be the fully qualified Windows pathname of the INMOD DLL file. • The parms string may include one or more character strings, each delimited on either end by an apostrophe, or delimited on either end by a quotation mark. The maximum size of the parms string is 1k bytes. • If a FastLoad INMOD is used, the parms string of the IMPORT command must be “FDLINMOD”. • The parms string as a whole must be enclosed in parentheses. • Parentheses within delimited character strings or comments have the same syntactical significance as alphabetic characters. Teradata Parallel Data Pump Reference 215
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:
Page 161 and 162:
Page 163 and 164: 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 213: 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

Create successful ePaper yourself

Delete template?

Save as template?