Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 5: Using INMOD and Notify Exit Routines Preparing the INMOD Program • 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. Preparing the INMOD Program This section describes the protocol used between Teradata TPump and an INMOD written for Teradata TPump. The protocols are applicable to all client platforms running Teradata TPump. Considerations applicable exclusively to UNIX-based clients are contained in “Programming INMODs for UNIX-based Clients” on page 218. On entry to an INMOD user exit routine for Teradata TPump, the conventional parameter register points to a parameter list of two 32-bit addresses. The first 32-bit address points to a data structure containing the following fields: • Return Code/Function Code, 4-byte integer. • Length, 4-byte integer, Length of the data record. • Data Record, Input data record buffer. The maximum length is: • 31K or 31,744 bytes for Teradata for Windows • 62K or 63,488 bytes for Teradata Database for UNIX INMOD Input Values Table 38 lists valid values of the Return Code/Function Code field and their meanings As input to the INMOD routine, as input to the INMOD routine. Table 38: INMOD Input Return Code Values Code Description 0 Request for INMOD to initialize and return first record. 1 Request for INMOD to return a record. 2 Request for INMOD to reposition to last checkpoint because of client restart. Repositioning information, provided by the INMOD after a code 3, is read from the restart logtable and returned to the INMOD in the buffer normally used for the data record. 3 Request for INMOD to take a checkpoint. In the buffer normally used to return data, the INMOD should return any information (up to 100 bytes) that it may need to reposition to this checkpoint. Teradata TPump then saves this information in its restart log table. 216 Teradata Parallel Data Pump Reference
Chapter 5: Using INMOD and Notify Exit Routines INMOD Output Values Table 38: INMOD Input Return Code Values (continued) Code Description 4 Request for INMOD to reposition to last checkpoint because of a Teradata Database failure. Repositioning information, provided by the INMOD after a code 3, is read from the restart log table and returned to the INMOD in the buffer normally used for the data record. 5 Request for INMOD to wrap up at termination. 6 Request for INMOD to initialize. 7 Request for INMOD to receive first (next) record. INMOD Output Values Table 39 lists valid values of the Return Code field and their meanings, as output to the INMOD routine. Table 39: INMOD Output Return Code Values Code Description 0 on read call (code 1) Indicates End Of File not reached. The length field should be set to the length of the output record. If an input record was supplied to the INMOD and it is to be skipped, set the length field to zero. If no input record was supplied, setting the length to zero acts as an End Of File. Non-0 on read call (code 1) Indicates End Of File. 0 on non-read call (not code 1) Indicates successful operation. Non-0 on non-read call (not code 1) Indicates a processing error. Teradata TPump terminates. The second 32-bit address points to a data structure containing the following fields: • Sequence Number, 4-byte integer, Integer record counter portion of the source sequence number. • Parameter List, Varchar, 2-byte length, m, followed by the m-byte parms string as parsed and presented by Teradata TPump. INMODs that cannot comply with these protocols should terminate if a Restart Code 2, Code 3, or Code 4 is encountered. Otherwise, data might become corrupted. In order to be restartable, INMODs must make use of Teradata TPump to save and restore checkpoint information as described above. If the INMOD saves its checkpointing information privately, recovery might result in data corruption. Note: On z/OS, the module must reside in the steplib/joblib (for JCL), task library (for clist/ exec), or the system linklist (for any). Teradata Parallel Data Pump Reference 217
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:
Page 165 and 166: 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 215: 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?