PowerExchange Interfaces for PowerCenter

Informatica® PowerExchange®
(Version 8.5)

Informatica® PowerExchange® Interfaces for PowerCenter
Version 8.5 October 2007 Copyright (c) 1998–2007 Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software is protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica Complex Data Exchange and Informatica On Demand Data Replicator are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

Part Number: PWX-IPC-850-0017

Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . xiii Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . xiii Obtaining Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1: PowerExchange Interfaces for PowerCenter . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 PowerExchange Client for PowerCenter (PWXPC) . . . . . . . . . . . . . . . . . . . . 3 Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Change Data Capture - Change Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Change Data Capture - Real Time Mode . . . . . . . . . . . . . . . . . . . . . . . . 6 PowerExchange ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: PWXPC - Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Installing PowerExchange Client for PowerCenter (PWXPC) . . . . . . . . . . . . 13 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Modify the PowerExchange Configuration Files . . . . . . . . . . . . . . . . . . . . . 14 Adding PowerExchange Nodes on the PowerCenter Client Machine . . . . 14 Adding PowerExchange Nodes on the Integration Service Machine . . . . 14 Adding PowerExchange Nodes in the dbmover.cfg File . . . . . . . . . . . . . 14 PowerExchange and PowerExchange Client for PowerCenter Coexistence . . . 16

Table of Contents

iii

Chapter 3: PWXPC - Working with Mappings . . . . . . . . . . . . . . . . . . . 17
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Source and Target Definitions in Designer . . . . . . . . . . . . . . . . . . . . . . . . . 19 Working with Relational Source and Target Definitions . . . . . . . . . . . . . . . . 21 Working with DB2 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Working with Microsoft SQL Server Definitions . . . . . . . . . . . . . . . . . . 26 Working with Oracle Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Working with Sybase Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Editing Relational Source and Target Definitions . . . . . . . . . . . . . . . . . 37 Working with Non-Relational Source and Target Definitions . . . . . . . . . . . . 39 Importing Non-Relational Source Definitions . . . . . . . . . . . . . . . . . . . . 40 Importing Non-Relational Target Definitions . . . . . . . . . . . . . . . . . . . . 44 Viewing Non-Relational Source and Target Definition Details . . . . . . . . 48 Editing Non-Relational Source and Target Definitions . . . . . . . . . . . . . . 50 Working with Extraction Map Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 53 Viewing Extraction Map Definition Details . . . . . . . . . . . . . . . . . . . . . 57 Editing a Extraction Map Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Previewing PowerExchange Data in Designer . . . . . . . . . . . . . . . . . . . . . . . . 60 Previewing PowerExchange Relational Data . . . . . . . . . . . . . . . . . . . . . . 60 Previewing PowerExchange Non-Relational Data . . . . . . . . . . . . . . . . . . 62 Previewing PowerExchange Changed Data . . . . . . . . . . . . . . . . . . . . . . . 64 PowerExchange Group Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Using Group Source with Non-Relational Sources . . . . . . . . . . . . . . . . . 68 Using Group Source with CDC Sources . . . . . . . . . . . . . . . . . . . . . . . . 69 Working with Source Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Creating Source Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Editing Source Qualifier Transformations . . . . . . . . . . . . . . . . . . . . . . . 72 Using Lookup Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Usage Considerations for PowerExchange Sources and Targets . . . . . . . . 73 Configuring Lookups for IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Configuring Lookups for CDC Data . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 4: PWXPC - Configuring Connections . . . . . . . . . . . . . . . . . 77
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Connection Types for Extracting Source Data . . . . . . . . . . . . . . . . . . . . 78 Connection Types for Loading Target Data . . . . . . . . . . . . . . . . . . . . . . 79
iv Table of Contents

Configuring Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 DB2 Batch Mode Relational Database Connections . . . . . . . . . . . . . . . . . . . 84 DB2 CDC Mode Application Connections . . . . . . . . . . . . . . . . . . . . . . . . . 87 NRDB Batch Mode Application Connections . . . . . . . . . . . . . . . . . . . . . . . 90 NRDB CDC Mode Application Connections . . . . . . . . . . . . . . . . . . . . . . . 91 NRDB Lookup Relational Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 MSSQL Batch Mode Relational Connections . . . . . . . . . . . . . . . . . . . . . . . 95 MSSQL CDC Mode Application Connections . . . . . . . . . . . . . . . . . . . . . . 97 Oracle Batch Mode Relational Connections . . . . . . . . . . . . . . . . . . . . . . . 100 Oracle CDC Mode Application Connections . . . . . . . . . . . . . . . . . . . . . . 102 Sybase Batch Mode Relational Connections . . . . . . . . . . . . . . . . . . . . . . . 105 Configuring Connections Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Common Connection Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Batch Application and Relational Connection Attributes . . . . . . . . . . . 108 CDC-Specific Connection Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 110 Understanding Commit Processing with PWXPC . . . . . . . . . . . . . . . . . . . 121

Chapter 5: PWXPC - Working with Sessions and Workflows . . . . . 125
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Pipeline Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Real-time Session Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . 126 Extracting Data in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Extracting Data from Multiple Files . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Constraint-Based Loading for Relational Targets . . . . . . . . . . . . . . . . . 127 Session Properties for Non-Relational Batch Mode Sessions . . . . . . . . . 127 Session Properties for Relational Batch Mode Sessions . . . . . . . . . . . . . 130 Extracting CDC Data in Change and Real-time Modes . . . . . . . . . . . . . . . 133 PowerExchange Extraction Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Extracting CDC Data from Multiple Sources in a Session . . . . . . . . . . 134 Constraint-Based Loading for Relational Targets . . . . . . . . . . . . . . . . . 134 Session Properties for Change and Real-Time Mode Sessions . . . . . . . . 135 Loading Data to PowerExchange Targets . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Loading Data to Relational Targets . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Loading Data to Non-Relational Targets . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 6: PWXPC - Restart and Recovery . . . . . . . . . . . . . . . . . . . 147
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Table of Contents

v

. . . . . . . . . . . . . . . 159 Configuring the Restart Token File . . . . . . . . . . . . . . . . . . . . . . . . . 150 Recovery State File . . . 185 Chapter 8: PowerExchange ODBC . . . . . . . . 156 Ending CDC Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Application Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Chapter 7: Flexible Key Custom Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Recovery State Table . .Understanding PWXPC Restart and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . 151 The Restart Token File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Stopping CDC Sessions . . . . . . . . . . . 189 Overview . . . 163 Enabling Session Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Target Key Transformations .Installation . . . . . . . . . . . . 160 Restart Token File Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Configuring the PowerExchange Extraction Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Statement Syntax Format . . . . . 149 Recovery Tables . 153 Initializing and Running CDC Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Recovering from CDC Session Failures . . . . . . . . . . . . . . . . . . . . . . 158 Creating the Recovery Tables Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Configuring PowerCenter . . . . . . . . . . . . 158 Recovery Table Creation with PowerExchange Targets . . . . . . . . . . . . . . . . . . . . . . . 171 Managing Session Log and Restart Token File History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 PWXPC Restart and Recovery Operation . . . . . . . . . . 190 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Group Source and Flexible Transformations . . . . . . . . . . . . . . . . . . . . . . . 157 Creating Recovery Tables . . . . . . . . . . 152 Determining the Restart Point . . . . . . . . . . . . . . . . 168 Changing CDC Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Session Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Configuring CDC Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Using DTLUAPPL with CDC Sessions . . . . . . . . . . . . . . . . 190 vi Table of Contents . . . . . . . . . . . . . . . 165 Starting CDC Sessions . . . . . . . . . . 160 Restart Token File Statements . . . . . . . . . . . . . . 160 Syntax Rules . . . . . . . . . . .

. . . . . . . . . . . . . 195 Importing a Source or Target Definition . . . . . . . . . . . . 194 Working with Source and Target Definitions for PowerExchange Batch . . . . . . . . . . . . . . . . . . . . . 221 Organizing Sources by Map Type in Designer . . . . . . . . . . . .Configuring Connections . . . . . . .Restart and Recovery . . . . . . . . . . . . . . 219 Appendix A: Usage Tips and Tricks . . . . . . . . . . 217 Overview . . . . . . . . . . . . . . . . . . . . 193 Overview . . . . . . . . . . . . 215 Chapter 12: PowerExchange ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Sessions and Workflows . 191 Creating ODBC Data Sources on the PowerCenter Client Machine . . . . . . 219 Managing Restart Tokens Using PowerExchange ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Overview . . .Installation Requirements . . . . . . . . . . . . . . . . . . . . . . 203 Connection Types for Loading Target Data . . . . . 203 Connection Types for Extracting Source Data . . . . . . . . . . 208 Pipeline Partitioning . . . . . . 211 Extracting Data from PowerExchange in Change and Real-Time Mode . . . . . . . . . . 213 Loading Data to PowerExchange Targets . . . . . . . . . 209 Session Properties for Relational Batch Mode Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Working with Mappings . . . . . . . . . . . . . . . . . . . . . . . . 190 Creating ODBC Data Sources . . 191 Chapter 9: PowerExchange ODBC . . 222 Table of Contents vii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Working with Source Definitions for PowerExchange Change or Real-Time 198 Importing a Change Data Capture Source Definition . . . . . . . . . . . . . 207 Overview . . . . . . . . . . . . 203 Configuring Attributes for Connections . . . . . . . . . . . . . . . . . 204 Chapter 11: PowerExchange ODBC . . . . . . . . . . . . . 218 Restart and Recovery Using PowerExchange ODBC . . . . . . . . . . 209 Session Properties for Non-Relational Batch Mode Sessions . . . 202 Working with Connections for PowerExchange ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Creating ODBC Data Sources on the Integration Service Machine . . 213 Session Properties for Change and Real-Time Mode Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Extracting Data from PowerExchange in Batch Mode . . . . . . . . . . . . . . . 198 Chapter 10: PowerExchange ODBC . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Creating Sequential and GDG Data Sets . . . . . . . . . 256 Messages 12000 through 12099 . . . . . . . . . . . . . . . . . . . . . . 259 viii Table of Contents . . . . . . . . . . . 258 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 PowerExchange and Transformation Datatypes . . . . . . . . . . 247 Overview . 230 Using Event Table Processing to Shutdown Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Reading and Writing Binary Data in PowerExchange Client for PowerCenter 240 Using Code Pages . . . . . . . . . . . . . . . . . . . . 237 Relational Datatypes . .Messages . . . . 241 Appendix C: Troubleshooting . . 233 Appendix B: Datatypes and Code Page Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Using DTLREXE to Submit MVS Batch Jobs . . . . . . 235 Overview . . . . . . . . . . . . . . . . . . . . . . . . . .Filtering Source Data using PWXPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Messages 10000 through 10099 . . . . . . . . . . . . . . . . . . . . 244 Chapter D: PWXPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Messages 11000 through 11099 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 5-4. . . . . . . . . . 4-3. .List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1-1. . . . . . . . . . . . . Import from PowerExchange . Session Mapping Tab . Import from PowerExchange . . . . . Import from PowerExchange . . . . 33 . . . . . . . . . . Import from PowerExchange . . . Import from PowerExchange . . . . . . . . . . . . . . . . . . . . . . . 57 . . . . . . . Application Connection .. . 20 . . . . . . .. . 5-5. . Relational Connection Browser . . 3-2. . ... . . . . . .Sybase Select Datamaps List . . .Metadata Extensions . . Extraction Map Table . 55 . . . . . . . . . .. . . . . . . . . . . .. . . .Non-Relational Target Select Datamaps List 3-18. . . . . . . . . . . . . . . 22 . . . . . . .Oracle source . . . . . . .. . . . . . . . . . . . . . .Number of Restart Token Files . . . . .. . . . . . . . . . . . . . . . .CDC Select Datamaps List . 49 . . . 3-14. . . . . . . . . . . . . . . . . 48 . . Import from PowerExchange . . . . Import from PowerExchange .. . Session Mapping Tab . . .Extraction Map Source . . . 5-3. . . 3-19. . . . Group Source Mapping Example . . . . . 3-6. . .. . . . . . . . . . . . . . . . . 41 . . . 1-3. . . . . . . . .DB2390 Select Datamaps List . Import from PowerExchange . . 3-20. . . 3-23. 5-2. . . .. . . . . . . . . . . 83 128 131 135 136 138 141 143 173 176 List of Figures ix . .. . . . . . .. . . . . . Import from PowerExchange . . 3-13. . . . . . . . Import from PowerExchange . . . 3-9.. . .Non-Relational Targets . . . . .. PWXPC Change Mode Extraction Data Flow . 1-2. . 37 . . . . . . . . . . . . . . . . . . . . . .. . Non-Relational Table . . . . . . . . . .Attributes . . . . . . . . . . . . . . . . . . . . .. 70 . . 3-5. . . . 81 . . . . . . . 3-17. 58 . . . . .Multiple Record Source Data Maps . . . . . . . . . . . . 29 . 5-1. . . . . . . . . . . . . Import from PowerExchange . . 39 . . . . . . .Source .. . . . . . . . . . . . . . . . Application Connection Browser . .. . . . . . . . . . . . . . . Import from PowerExchange . . .DB2/400 or DB2/UDB source . . . . . . .. . . . . . . . . . 7 . . . . . .Batch VSAM Reader . . . . . . . . . . . . . 5-7. . . .. . . . . 35 . . 3-24. . . . . . . . . . . . . 5 . . . . .DB2/390 source . . . . . . . . 54 . . 5-6. . . . . . . .. . Multi-record Non-Relational Source Definition . . . . . .. . . . . . 27 . . . . . . 6 . . . . . . . . . . . . . . . .Relational Targets . . 45 .. . . . .. . .Attributes . . .. . . . . Application Connection Editor . . . . . . . . . . .. . . . . . ... . . . . . . . . . . . .. .. . . . . . . . . . . . . . . . 3-15.Relational Source . .. . . . . . .. . . . . . . . .. . . . . . . . . . . . . . . 44 . Import from PowerExchange . . 7-1. 3-16. . .. . 6-1. . . . . . . Import from PowerExchange . . .DB2 Readers . . . . . . . . . . . 3-4. . . 3-7. . . . . . . . . . . . . . . . . . . . . . Session Mapping Tab . . . . Primary key updates from a source relational table . . . . . . . . Non-Relational Source Definition with Multiple Records .CDC Datamaps . . . . 4-1. . . . 3-21. . . . . PWXPC Batch Mode Extraction Data Flow .. . . . . . . 69 . . . . 25 . . . . . . . . . . . . .Oracle Select Datamaps List . .Microsoft SQL Server source . 3-1. . . . . . 3-22. . . . . . . . .Single Record Source Data Maps . . 31 . .. . . . . . . . . . . . . . . 82 . . . . PWXPC Real Time Mode Extraction Data Flow . Extraction Map Table . . . .Non-Relational Source . . . . . .. . . . . . . . 3-8. . . . . . 3-3. 3-10. . . . . . . . . 3-12. . . . . . . 3-11. . . . . . . . 19 . . . . . . . . . 4-2. Import from PowerExchange . . . . . . . Import from PowerExchange . . .. . . . . . . . . . . . . 47 . . . . ..MSSQL Select Datamaps List .. . . . . . . 3-25. . . . . . .Non-Relational Target . . . Session Mapping Tab . . .Metadata Extensions . . . . . . . .. . Session Mapping Tab . . . . 23 . . . . . . . . . . . . . . . . . . . . . . Session Properties Tab . . Import from PowerExchange . . . . Non-Relational Table . . .Sybase source . . . . . . Import from PowerExchange . . . . 43 . . . . . . . Session Mapping Tab . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Filter Overrides: Multi-Record Filter . . . . . . . . . . . . .Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 7-2. . . . ODBC . . . . Workflow Link Condition . . A-5. . . . DB2 Extraction Map Source Mapping . . . . . A-1. . . . . . . . . .229 . . . .229 . . . . .181 . . .182 . . . . . . . . . . . . . . . DB2 Target Table Mapping . . . . . . . . . . . . 7-4. A-6. . . . . . . . . . . . . . .Connection Object Definition . . . . . . . .File Create Pre-SQL Command . A-2. . . 10-1.DTLREXE .DTLREXE . . . . . . . . . . . . . .181 . . .231 x List of Figures . . . . . . . . . . . . . . . . Pre-Session Command . . . . . . . Session Mapping Tab . . . . . . A-3. . . . . . . . . . . . . . . . DB2 Source to DB2 Target CDC mapping . . . . . . . . . . . . . . . .225 . . . . A-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226 . . . . . . . .228 . . . . . . . . . . . . . . . . . . . Filter Overrides: Single-Record Filter . . . . . . . . . . . . .DTLREXE . .204 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3. . . . . Command Task Expression Editor . . . . .

. . . . . . . Image Type Connection Attribute . . . . . . . . . . . . CDC Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4-8. . . . . . 57 3-4. . 156 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Starting Extraction Points for Sources . . . . . . . . . Convert Character Data Connection Attribute . . . . . . . . . . . 116 4-24. . . . . . . . . . . . . . . . . . . . 203 List of Tables xi . . . . . . . . . . . . . . . Pacing Size Connection Attributes . . . 117 4-25. . . 102 4-12. . . . . . Encryption and Compression Connection Attributes . . . . . . . . . . . . . . . 50 3-3. . . . . . . . . . . . . . 100 4-11. . . . . . . . . . . . Sybase Batch Mode Relational Connection Attributes . . . . . . 16 3-1. . . . . . . 112 4-20. . . 107 4-14. . . . . . . Connection Types for Loading Target Data . . . . . . . . . . . . . . . . . . . . . 95 4-9. Oracle CDC Mode Application Connection Attributes . . . . 164 10-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . MSSQL CDC Mode Application Connection Attributes . . . . . . . 3 1-3. . . . . . . . . . . . . . . . . . . . PWX DB2390. 8 2-1. Connection Types for Extracting Source Data . . . . . . . . . and DB2UDB CDC Mode Application Connection Attributes . . . . . . . . . . . 119 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 4-23. PowerExchange and PWXPC Coexistence Matrix . . . . . . . . . . NRDB CDC Mode Application Connection Attributes . . Session Properties for Non-Relational Targets . . . NRDB Batch Mode Application Connection Attributes . . . . . . . . . . 144 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . PowerExchange ODBC Extract and Load Capabilities . . . . . Recovery Table SQL Scripts . . . . Write Mode Connection Attribute . . . . . . . Change and Real-time Mode Restart Connection Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retrieve PWX Log Entries Connection Attribute . . . .List of Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 1-1. 58 4-1. . Target Database Types . . Attributes of Fields in a Non-Relational Source Definition . . . . . . . . . . . . . . . . . Non-Relational Source Definition Metadata Extensions . . . . . . . . . . . . . . 2 1-2. 107 4-15. . .Recommended Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and DB2UDB Relational Database Connection Attributes 84 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commit Threshold Connection Attribute . . . . . . . . . Connection Types for Extracting Source Data . . . . . . . . . . Real-Time Flush Latency Connection Attribute . . . . . . . . . . . . . . . . . . . . DB2390. . . . 110 4-18. Functional Comparison between PWXPC and PowerExchange ODBC . . . . . . . . . . . . . Extraction Map Definition Metadata Extensions . . 4 1-4. . . 87 4-5. . . . . . DB2400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 10-2. . . . Idle Time Connection Attribute . . . . . . . . . . . . . . . . . . . . . . . PowerExchange Client for PowerCenter Extract and Load Capabilities . . . . . . . . . . . . . CAPI Connection Override Connection Attribute . . . . . . . . . . . . . . . . . 159 6-3. . . . . . . . . . . 48 3-2. . . . . . . . . . . . . 109 4-17. . . . . . . . . . . . . 91 4-7. Oracle Batch Mode Relational Connection Attributes . . . . . . . . . . MSSQL Batch Mode Relational Connection Attributes . . . . PowerExchange Database Types Supporting Group Source . . . . . . . . . . . . . . . . . DB2400. . . 111 4-19. . . . . 78 4-2. . . . . 113 4-21. . . . . . . . . . . . . . . . . . . . . 97 4-10. . . . . 108 4-16. . . . . . . . . . . . . . Event Table Connection Attribute . . . . . . . . . . . . . Attributes of Fields in a Extraction Map Definition . . . . . . 113 4-22. UOW Count Connection Attribute . . . . . . . . . . . . . . . . 105 4-13. . . . 90 4-6. . . . . . . . . . . . 79 4-3. . . . . . . . . . . . . . . . . . . . . NRDB Lookup Relational Connection Attributes . . . . . . .

. . . . . . . . Partition Types for Partitioning Points for Sources . . . . . . . . . . . . . . .Table 10-3. . . . . . . . .205 Table 11-1. . . . . . ODBC Connection Object Definition Table . . . . . . . . . . . . . . . . PowerExchange and Transformation Datatypes . . . . . . . . . . . . . .208 Table B-1. . .237 xii List of Tables . . . . . . . . .

PowerExchange Change supports capture of changed data on a wide variety of platforms and databases and does not require a separate set of database tables as a staging area. PowerExchange Real-time provides real-time access to changes streamed from transactional databases. Changes can be sourced in relational format and can be distributed to message queues or applied to targets through PowerCenter. Changes are available at separate intervals. demonstrating excellent performance. scalability. you can now update your data warehouse on a more regular basis without overloading your IT infrastructure. greatly enhancing flexibility and performance. PowerExchange has become the standard in this area. PowerExchange Change provides the ability to capture changes from transactional databases and make them available at user-defined intervals. productivity and ease-of-use. By capturing changes in source data. to different targets. PowerExchange Real-time requires no additional programming to complete the integration picture. Change data captured by PowerExchange Change and PowerExchange Real-time is available to PowerCenter.Preface PowerExchange Batch provides the extract and apply functionality required to support data warehouse and migration initiatives. xi . providing just the net change over the specified interval. Changes can be presented in condensed form.

running. This is a code example. This manual assumes you have knowledge of your operating systems. and administering workflows and sessions interfacing with PowerExchange. The following paragraph notes situations where you can overwrite or corrupt data. This is generic text that should be replaced with user-supplied values.About this Book PowerExchange Interfaces for PowerCenter describes the Informatica interface between PowerExchange and PowerCenter. This manual also assumes you are familiar with the basic operation of PowerExchange and PowerCenter This manual discusses: ♦ ♦ the PowerExchange Client for PowerCenter (PWXPC) interface the Power Exchange ODBC interface with PowerCenter Document Conventions This guide uses the following formatting conventions: If you see… It means… The word or set of words are especially emphasized. italicized text boldfaced text italicized monospaced text Note: Tip: Warning: monospaced text bold monospaced text xii Preface . It is written for developers and administrators who are responsible for creating. The following paragraph provides additional facts. The following paragraph provides suggested uses. This is the variable name for a value you enter as part of an operating system command. unless you follow the specified procedure. This is an operating system command you enter from a prompt to run a task. Emphasized subjects. and the database engines and non-relational files in your environment. relational database concepts.

informatica. you can access the Informatica Knowledge Base at http://my. You will also find product and partner information.com for technical inquiries support_admin@informatica. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products.Other Informatica Resources In addition to the product manuals. user group information. you can access the Informatica Customer Portal site at http://my. Informatica provides these other resources: ♦ ♦ ♦ ♦ Informatica Customer Portal Informatica web site Informatica Knowledge Base Informatica Global Customer Support Visiting Informatica Customer Portal As an Informatica customer.com.com. and technical tips. and access to the Informatica user community.com for general customer service requests WebSupport requires a user name and password.informatica. The site contains product information. You can contact a Customer Support Center through telephone. and implementation services.informatica. technical white papers. Preface xiii . newsletters. The services area of the site includes important information about technical support. upcoming events.informatica. Visiting the Informatica Knowledge Base As an Informatica customer. You can also find answers to frequently asked questions. You can request a user name and password at http://my. access to the Informatica customer support case management system (ATLAS). or the WebSupport Service. Visiting the Informatica Web Site You can access the Informatica corporate web site at http://www. email. its background.com. The site contains information about Informatica. the Informatica Knowledge Base. training and education. Use the following email addresses to contact Informatica Global Customer Support: ♦ ♦ support@informatica. and sales offices. Informatica Documentation Center. Obtaining Customer Support There are many ways to access Informatica Global Customer Support.com.

Diamond District Tower B. Berkshire SL6 3TN United Kingdom Asia / Australia Informatica Business Solutions Pvt. White Waltham Maidenhead.Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Informatica Corporation Headquarters 100 Cardinal Way Redwood City. Ltd. California 94063 United States Europe / Middle East / Africa Informatica Software Ltd. 3rd Floor 150 Airport Road Bangalore 560 008 India Toll Free Australia: 1 800 151 830 Singapore: 001 800 4632 4357 Standard Rate India: +91 80 4112 5738 Toll Free 877 463 2435 Toll Free 00 800 4632 4357 Standard Rate United States: 650 385 5800 Standard Rate Belgium: +32 15 281 702 France: +33 1 41 38 92 26 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511 445 xiv Preface . 6 Waltham Park Waltham Road.

3 PowerExchange ODBC. 8 1 .Chapter 1 PowerExchange Interfaces for PowerCenter This chapter covers the following topics: ♦ ♦ ♦ Overview. 2 PowerExchange Client for PowerCenter (PWXPC).

The following table compares the interface functionality of the PowerExchange Client for PowerCenter and PowerExchange ODBC: Table 1-1. You can use PowerExchange ODBC connections with PowerCenter to extract and load data through PowerExchange for a variety of data types on a variety of platforms. PowerExchange normally uses the file name from the PowerExchange data map. see the PowerExchange Getting Started manual. PowerCenter stops real time sessions after all data in the pipeline is written to the targets. PWXPC provides additional functionality that is not available with ODBC. Changing the file name in the PowerCenter source definition overrides the PowerExchange data map. You must use an Update Strategy transformation to process inserts. PowerExchange extraction maps contain change capture-specific columns minimizing modification of the source definition. CDC restart information is stored in the same database as the relational target table in a single commit providing guaranteed CDC restart and recovery. For a complete list. Yes No Save target data and CDC restart information in a single commit Yes Yes No No PowerCenter graceful stop support for real time sessions Automatically process change indicator Yes No Create source definitions from PowerExchange extraction maps Modify the PowerExchange file name in the source definition Yes No 2 Chapter 1: PowerExchange Interfaces for PowerCenter . see Table 1-2 on page 3. update. PowerExchange Client for PowerCenter is fully integrated into PowerCenter as a native plug-in. see Table 1-4 on page 8. Chapters 8-12 describe the PowerExchange ODBC interface. For a complete list. Functional Comparison between PWXPC and PowerExchange ODBC PWXPC Yes ODBC No Function Group Source Description PowerExchange Group Source functionality processes changes for multiple sources or multiple record types in a VSAM or sequential file in a single pass. For an overview of PowerCenter. You can use it to extract and load data through PowerExchange for a variety of data types on a variety of platforms. updates. PowerExchange ODBC. Chapters 2-6 describe the PowerExchange Client for PowerCenter. ♦ For an overview of PowerExchange. Each changed data record indicates whether it is an insert. see the PowerCenter Getting Started manual. or deletes.Overview You can use the following interfaces to extract and load data through PowerExchange when using PowerCenter: ♦ PowerExchange Client for PowerCenter (PWXPC). and deletes if the change indictor is not used automatically.

PowerExchange Client for PowerCenter (PWXPC) 3 . PWXPC also uses Group Source to extract data from VSAM data sets and sequential files containing multiple record types. For detailed information about Group Source. Group Source reads all data from the same physical source in a single pass. As a result. The PowerExchange Client for PowerCenter integrates PowerExchange and PowerCenter to extract relational and non-relational data. PWXPC connects to PowerExchange locally or remotely in order to extract or load data.PowerExchange Client for PowerCenter (PWXPC) The PowerExchange Client for PowerCenter is a native PowerCenter plug-in installed with PowerCenter. see “PowerExchange Group Source” on page 68. PowerExchange Client for PowerCenter Extract and Load Capabilities Database Type Adabas Datacom DB2/390 DB2/400 DB2/UDB IDMS IMS MSSQL Oracle SEQ (sequential files) Sybase VSAM Batch Mode Extract Yes Yes Yes Yes Yes Yes Yes n/a n/a Yes Yes Yes CDC Change Mode Yes Yes Yes Yes n/a Yes Yes n/a Yes n/a n/a Yes CDC Real Time Mode Yes Yes Yes Yes Yes Yes Yes Yes Yes n/a n/a Yes Batch Mode Load Yes No Yes Yes Yes No Yes Yes Yes Yes Yes Yes PWXPC uses PowerExchange Group Source functionality to extract changed data from the change stream. Table 1-2 lists the database types the PowerExchange Client for PowerCenter can access to extract data or load data: Table 1-2. PWXPC also loads relational and non-relational data. PWXPC connections also reduce PowerExchange resource consumption on the source or extraction platform. PWXPC connections provides enhanced performance over ODBC connections by using Group Source to eliminate multiple passes of the source data. Note: Some PowerExchange sources do not support Group Source.

PWXPC uses PowerExchange Group Source functionality to do this.Table 1-3 indicates which PowerExchange database types support Group Source: Table 1-3. PowerExchange Database Types Supporting Group Source Database Type Adabas Datacom DB2/390 DB2/400 DB2/UDB IDMS IDMSX IMS MSSQL Oracle SEQ (sequential files) Sybase VSAM Batch Mode No No No No No No No No No No Yes No Yes CDC Change Mode Yes Yes Yes Yes n/a Yes n/a Yes n/a Yes n/a n/a Yes CDC Real Time Mode Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes n/a n/a Yes The PowerExchange Client for PowerCenter extracts relational and non-relational data in the following modes: ♦ ♦ ♦ Batch Change Data Capture (CDC) .Real Time Batch Mode Use PWX Batch application and relational connections to extract and load data for relational databases and non-relational data sets and files through PowerExchange. You can extract all records in multiple record type VSAM and sequential (flat) data sets with a single pass of the data. 4 Chapter 1: PowerExchange Interfaces for PowerCenter . ODBC connections read a single record type at a time requiring multiple passes of the data.Change Change Data Capture (CDC) . PWXPC connects to PowerExchange using the PowerExchange Call Level Interface (SCLI). In contrast.

As a result. PWXPC uses PowerExchange Group Source functionality to read the changed data from the condense file. See the PowerExchange Oracle Adapter Guide for more information about Oracle changed data extraction options. The UOW Cleanser PowerExchange Client for PowerCenter (PWXPC) 5 . the changes in a single unit of work (UOW) are not contiguous in the change stream. The change stream contains source data changes in time sequence order. PWXPC ends the extraction once the data from all condense files is read when you use CDC Change application connections. Use PWX CDC Change application connections to extract changed data from the PowerExchange condense files. As a result. PWXPC Batch Mode Extraction Data Flow Change Data Capture . PowerExchange Condense reads captured changed data from the change stream. PWXPC connects to PowerExchange using the PowerExchange Call Level Interface (SCLI).Change Mode PowerExchange Condense captures changes for relational tables and non-relational data sets and files in condense files.The following diagram shows the data flow of source data from PowerExchange through PWXPC and PowerCenter to the target tables: Figure 1-1. PowerExchange reads each condense file only once for all sources in the mapping. Your extraction runs continuously when you use CDC Real Time applications connections to extract Oracle changed data. You can also use PWX CDC Real Time application connections to extract changed data for Oracle sources from the PowerExchange condense files.

The UOW Cleanser reconstructs 6 Chapter 1: PowerExchange Interfaces for PowerCenter . PWXPC Change Mode Extraction Data Flow Change Data Capture . PWXPC uses PowerExchange Group Source functionality to read the changed data from the change stream. PowerExchange Condense then writes these UOWs to condense files. As a result. The following diagram shows the data flow of condensed changed data from PowerExchange through PWXPC and PowerCenter to the target tables: Figure 1-2. PowerExchange reads captured changed data from the change stream. The change stream contains source data changes in time sequence order. PowerExchange reads each condense file only once for all sources in the mapping. PWXPC uses the PowerExchange Capture Extraction Real-Time (CAPXRT) Access Method to extract changes when you use PWX CDC Real Time connections. PWXPC connects to PowerExchange using the PowerExchange Call Level Interface (SCLI).Real Time Mode Use PWX CDC Real Time application connections to extract changed data for relational tables or non-relational data sets and files directly from the change stream. PWXPC uses the PowerExchange Capture Extraction (CAPX) Access Method to extract changes from the condense files when you use PWX CDC Change connections. As a result. the changes in a single unit of work (UOW) are not contiguous in the change stream. PWXPC real-time sessions run for a specified period or continuously until stopped.reconstructs the units of work (UOW) into complete and consecutive UOWs.

PWXPC uses the PowerExchange Capture Extraction Real-Time (CAPXRT) Access Method when you use PWX CDC Real Time connections. The UOW Cleanser is incorporated into PowerExchange UDB and SQL Server CDC. The following diagram shows the data flow of source changed data from PowerExchange through PWXPC and PowerCenter to the target tables: Figure 1-3. PWXPC Real Time Mode Extraction Data Flow PowerExchange Client for PowerCenter (PWXPC) 7 .the units of work (UOW) into complete and consecutive UOWs.

The PowerExchange ODBC interface does not support Group Source. You can also extract changed data. The PowerExchange ODBC interface has limited restart capability. The PowerExchange ODBC interface extracts relational and non-relational data in the following modes: ♦ Batch The Integration Service extracts and loads data from a relational table or non-relational file through PowerExchange. PowerExchange maintains restart information in the change information (CDEP) file on the source PowerExchange platform. Table 1-4 shows the PowerExchange ODBC extract and load capabilities: Table 1-4.PowerExchange ODBC PowerExchange provides a thin ODBC driver that you can use with PowerCenter. The Integration Service connects to PowerExchange locally or remotely to extract or load data through the PowerExchange ODBC interface. You run real time extractions run for a specified time period.Change The Integration Service extracts changed data from condense files through PowerExchange. PowerExchange maintains restart information in the change information (CDEP) file on the source PowerExchange platform. ♦ Change Data Capture (CDC) . You can extract and load relational and nonrelational data. ♦ Change Data Capture . The extraction session ends after all of the captured changes are read. The PowerExchange ODBC interface has limited restart capability. PowerExchange ODBC Extract and Load Capabilities Database Type Adabas Datacom DB2/390 DB2/400 DB2/UDB IDMS IDMSX IMS MSSQL Batch Yes Yes Yes Yes Yes Yes Yes Yes n/a Change Yes Yes Yes Yes n/a Yes n/a Yes n/a Real-Time Yes Yes Yes Yes Yes Yes Yes Yes Yes Load Yes n/a Yes Yes Yes n/a n/a Yes Yes 8 Chapter 1: PowerExchange Interfaces for PowerCenter .Real Time The Integration Service extracts changed data in real time from the change stream. The PowerExchange ODBC interface reads a single type in multiple record type VSAM and sequential files requiring multiple passes of the data to read all record types. The PowerExchange ODBC interface reads all of the changes captured in condense files since the last extraction session.

Table 1-4. PowerExchange ODBC Extract and Load Capabilities Database Type Oracle SEQ (sequential files) VSAM Batch n/a Yes Yes Change Yes n/a Yes Real-Time Yes n/a Yes Load Yes Yes Yes PowerExchange ODBC 9 .

10 Chapter 1: PowerExchange Interfaces for PowerCenter .

Chapter 2 PWXPC . 13 Modify the PowerExchange Configuration Files. 14 PowerExchange and PowerExchange Client for PowerCenter Coexistence.Installation This chapter covers the following topics: ♦ ♦ ♦ ♦ Overview. 16 11 . 12 Installing PowerExchange Client for PowerCenter (PWXPC).

0. PowerExchange 8. Note: If the appropriate version of PowerExchange is not installed and available on the PowerCenter Client platform. you must install the 32-bit version of PowerExchange. Install PowerExchange on the PowerCenter Client and Integration Service machines.Installation . Before You Begin The PowerExchange Client for PowerCenter (PWXPC) is a native PowerCenter plug-in that is installed with PowerCenter.0. To use PWXPC. you must install the 64-bit version of PowerExchange on the Integration Service platform. You can use a 32bit PowerCenter Client and PowerExchange Navigator with a 64-bit version of either product. This includes the PWXPC plug-in. If you installed the PowerCenter Integration Service on a 32-bit platform. the Import from PowerExchange dialog box will not function. you must install the following products: ♦ ♦ PowerCenter 8. For more information about installing PowerExchange see the PowerExchange Installation Guide.5. For more information about installing PowerCenter.Overview This chapter describes how to install and configure PowerExchange Client for PowerCenter (PWXPC). 12 Chapter 2: PWXPC .5. see the PowerCenter Installation Guide. If you have installed the Integration Service on a 64-bit platform. The PowerExchange Navigator is only provided in 32-bit format.

To configure PowerExchange Client for PowerCenter for use on the PowerCenter Integration Service and Client. This process registers the PWXPC plug-in. Also backup the PowerCenter recovery tables. Cold start the session so PWXPC uses only the newly populated restart token file to restart the CDC session. You must still configure PowerExchange configuration files on the Integration Service node.1. you must add NODE statements in the PowerExchange dbmover.1) and are using enhanced restart for CDC session. Installation Steps The PowerExchange Client for PowerCenter (PWXPC) is installed when you install PowerCenter on the client and Integration Service machines. See “Modify the PowerExchange Configuration Files” on page 14.Installing PowerExchange Client for PowerCenter (PWXPC) To use PWXPC. This ensures that the restart token files contain the restart points from the point of interruption on the previous release. As a precaution. 2. Upgrading If you are upgrading from a previous release of PowerCenter. PowerExchange must be installed on the node where the PowerCenter Integration Service executes as well as on PowerCenter Client platforms. you must perform a repository upgrade. After completing the migration to PowerCenter V8. PWXPC creates a backup restart token file with a timestamp appended. Save this file. cleanly shutdown all CDC sessions and run recovery on all CDC sessions. Prior to migrating to PowerCenter V8.1 SP2 (or any higher Service Pack on V8. Read the Release Notes and PowerExchange Migration Guide for any changes to installation or connectivity. copy the backup restart token files PWXPC created to the appropriate restart token file for each CDC session. Installing PowerExchange Client for PowerCenter (PWXPC) 13 . you must do the following: Upgrading for PWXPC enhanced restart users: 1.5. 4. If you are upgrading from PowerCenter V8. backup the relational tables which are targets in the CDC sessions.cfg file on the PowerCenter Client and Integration Service machines for those PowerExchange Listeners to which you wish to connect.1. 3.5.

14 Chapter 2: PWXPC . Update the dbmover.cfg File Use the following procedure to add PowerExchange nodes in the dbmover.cfg file. Adding PowerExchange Nodes on the PowerCenter Client Machine PWXPC connects to a PowerExchange Listener to import source and target definitions.cfg file in the PowerExchange root directory.cfg file on the Integration Service machine to provide the appropriate NODE= statements for the PowerExchange Listeners to which you need to connect.cfg file are specified in the Location field in “Import from PowerExchange” dialog box. 2. Adding PowerExchange Nodes on the Integration Service Machine PWXPC connects to the appropriate PowerExchange Listener to extract data from a source or load data to a target. Locate the dbmover. If local mode is used. See “Configuration File Parameters” in the PowerExchange Reference Manual for information about how to specify the NODE statement in the dbmover.cfg file. Open the file with a text editor.Installation . The nodes you add to the dbmover. The nodes you add to the dbmover. PWXPC retrieves the metadata from the machine indicated in the NODE statement.cfg file on the PowerCenter Client machine to provide the appropriate NODE statements for the PowerExchange Listeners to which you need to connect.cfg file: 1. there is no need to update to the PowerExchange dbmover.cfg file. or locally if using local mode. For information about how to specify the NODE statement in dbmover.cfg. In local mode. Note: You can also use PowerExchange local mode if the data resides on the same machine as the Integration Service. Specify “local” in the Location attribute in PWXPC connections. a PowerExchange Listener is not required.Modify the PowerExchange Configuration Files You must define nodes for the PowerExchange Listeners in the PowerExchange configuration file (dbmover. see the “Configuration File Parameters” chapter in PowerExchange Reference Manual. The NODE statements specify the communication information that PowerExchange uses to communicate with Listeners that access the source or target databases or files.cfg file on the Integration Service machine are specified in the Location value of the PWXPC connections. Adding PowerExchange Nodes in the dbmover. Update the dbmover.cfg) on the Integration Service and Client machines. To add PowerExchange nodes in the dbmover.

Save your changes.4.TCPIP.TCPIP.<port_number>) where <node name> is a logical name used to reference the PowerExchange Listener and <hostname> and <port_number> are the host name (or IP address) and port number of the PowerExchange Listener. 4.3.TCPIP.MVS1. see “Configuration File Parameters” in the PowerExchange Reference Manual.<hostname>.AS400_1.cfg file: /********************************************************************/ /* PowerExchange Configuration File /********************************************************************/ NODE=(AS400_DB2.5538) For more information.2480) NODE=(MVS1_VSAM.TCPIP. Modify the PowerExchange Configuration Files 15 .5. Create a node for each PowerExchange Listener you want to register using the following guidelines: NODE=(<node name>.5539) NODE=(MVS2_DB2.10.3. The following example shows several nodes in a dbmover.

2.0 Patch 02 2.0 No No No No No No Yes Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 Yes 4 1.2.0 No No No No Yes Yes Yes 8.Installation .x” in the PowerExchange Migration manual.0.2 Patch 02 is the minimum level required for V71.0 5.4 and V7.1.3 No No Yes 3 7.1.2.1.1 Yes 1 Yes Yes No No No No 7.1. PowerExchange and PWXPC Coexistence Matrix PowerCenter / PowerExchange Client for PowerCenter 7.x with PowerExchange v8.1.2 was introduced with PowerExchange V5. Support for PWXPC V7.1. Support for PWXPC V7. 4.3 was introduced with PowerExchange V5.4 No No Yes 3 7.1. Support for PWXPC V7.1.0 8.0.1.2 8.0 No No No No No No No 7.1.2.1.PowerExchange and PowerExchange Client for PowerCenter Coexistence Different versions of PowerExchange and PWXPC coexist provided that the PowerExchange version and release are equal to or higher than that of PowerCenter.0 5.2. exploitation of new functionality is limited but existing functionality continues to operate.1 PowerExchange 5. See “Using Versions of PowerCenter Earlier than v8.5.0 8. The matrix in Table 2-1 indicates the combinations of PowerCenter and PWXPC that coexist with PowerExchange for migration purposes: Table 2-1.2 No No Yes 2 No No No No 7.1 No No No No No Yes Yes 8.0 No No No Yes Yes Yes Yes 8.2.5 No No Yes 3 8.1 8. 16 Chapter 2: PWXPC .1.1 was introduced with PowerExchange V5.1.5.2 Patch 01 3.1. In this environment.5.

Chapter 3 PWXPC . 39 Working with Extraction Map Definitions. 72 Using Lookup Transformations. 53 PowerExchange Group Source. 73 17 . 18 Source and Target Definitions in Designer. 19 Working with Relational Source and Target Definitions.Working with Mappings This chapter covers the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 21 Working with Non-Relational Source and Target Definitions. 68 Working with Source Qualifiers.

You can extract source data in batch. Nonrelational sources require a multi-group source definition. When you create a source definition. or real-time mode.Working with Mappings .Overview A mapping is a set of source and target definitions linked by transformation objects that define the rules for data transformation. change. After you create a source or target definition. For a list of sources and targets that PowerExchange Client for PowerCenter supports. 18 Chapter 3: PWXPC . see Table 1-2 on page 3. The source qualifier for a source definition also differs in structure depending on type of source definition. you can include it in a mapping to extract data from the source or load data to the target. create any business rules applicable to both the batch and CDC sessions in Mapplets. its structure differs depending on the type of source it represents. change. Source and target definitions represent metadata for sources and targets. Mappings represent the data flow between sources and targets. or real-time mode. Relational sources use a singlegroup source definition. see the PowerCenter Designer Guide. it is generally necessary to have multiple mappings: a batch mapping to materialize the target tables from the source tables in preparation for CDC and the CDC mapping itself which then uses extraction map sources for the source tables. To minimize the effort in creating these mappings. With CDC mappings. For more information about Mapplets. This table also lists whether the Integration Service can read the source data in batch.

Source and Target Definitions in Designer Both relational and non-relational sources and targets can be imported using the PowerCenter Designer. Figure 3-1. Import from PowerExchange This displays the Import from PowerExchange dialog box. Source and Target Definitions in Designer 19 . The process and the dialog box displayed is the same for targets.

Import from PowerExchange . PowerExchange data maps. This information is used. you can edit it.Figure 3-2 shows the dialog box used to import all PowerExchange sources and targets. when the source or target is accessed from the Integration Service node. This eliminates the need to provide the “Owner Name” attribute in the Session Properties for all source types and “Table Name Prefix” attribute in the Session Properties for non-relational PowerExchange targets. Note: The Owner name is included in the source definitions for relational metadata and in the source and target definitions for PowerExchange data maps imported using this dialog. After you create a source or target definition. including relational metadata. 20 Chapter 3: PWXPC . and PowerExchange capture extraction maps: Figure 3-2. You create the source and target definitions differently depending on the database type. unless overridden.Working with Mappings .Source Additional input fields appear depending upon the “Source Type” chosen.

Create a DB2 target definition from a DB2 source definition. the metadata definition must match the table structure of the DB2 table. UNIX. Importing a DB2 Relational Source or Target Definition You can connect to a DB2 database through a PowerExchange Listener. see “Importing Non-Relational Source Definitions” on page 40. For more information. Manually create a DB2 definition. Import extraction map definitions for PowerExchange. you can use them to extract data from or load data to a DB2 table. In the Target Designer. When you connect to the database. When you import a DB2 (390. see “Working with Extraction Map Definitions” on page 53. the Designer displays database schemas and tables. Tip: If your repository already contains DB2 definitions. 400. drag a DB2 source definition to the workspace. Working with Relational Source and Target Definitions 21 . or locally without a Listener. the following relational databases: ♦ ♦ ♦ ♦ ♦ ♦ DB2 UDB for z/OS (DB2/390) DB2 UDB for iSeries (DB2/400) DB2 for Linux. the Designer imports the primary keys.Working with Relational Source and Target Definitions With PowerExchange Client for PowerCenter. you can create source definitions to read from. to import DB2 metadata. Before you connect to the database. Import table definitions from the DB2 catalog using PowerExchange. You can create a DB2 target definition in the following ways: ♦ ♦ ♦ See the PowerCenter Designer Guide for more information about using PowerCenter to create source and target definitions. and target definitions to write to. For more information. Import DB2 or DB2 unload (DB2UNLD) data map definitions from PowerExchange. you can filter the metadata the Designer displays by schema and/or table name. Manually create a DB2 definition. Select a table to create the source or target definition. or UDB) source or target definition through a PowerExchange Listener (or locally). and Windows (DB2/UDB) Microsoft SQL Server Oracle Sybase Working with DB2 Definitions You can create a DB2 source definition in the following ways: ♦ ♦ ♦ ♦ Import table definitions from the DB2 catalog using PowerExchange. However.

DB2/400. Use the following procedure to import DB2/390. DB2400. or DB2UDB. DB2/400 or DB2/UDB source or target definition: 1. select Targets > Import from PowerExchange and select a source type of DB2390. To import a DB2 source definition.DB2 tables that are mapped in PowerExchange as either DB2 data maps or DB2UNLD (DB2 database unload data set) data maps (DB2/390 only) are imported in the same manner as non-relational data map sources. and DB2/UDB source or target definitions. 22 Chapter 3: PWXPC . Import from PowerExchange . select Sources > Import from PowerExchange and select a source type of DB2390. The dialog box for a DB2/390 source definition import looks as follows: Figure 3-3. DB2400. or DB2UDB.Working with Mappings .DB2/390 source The target dialog box looks similar but does not contain the Multi-Record Datamaps and CDC Datamaps options. To import a DB2/390. see “Importing Non-Relational Source Definitions” on page 40. For more information on how to import these sources. To import a DB2 target definition.

Import from PowerExchange .source only Name of the subsystem for connection. DB2390 only. 2. SEQ or VSAM sources only.cfg) on the system on which the database resides. Select to list multi-record data maps. User name for the database you want to connect to.DB2/400 or DB2/UDB source The target dialog box looks similar but does not contain the Multi-Record Datamaps and CDC Datamaps options.The dialog box for a DB2/400 or a DB2/UDB source looks as follows: Figure 3-4. DB2400. Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover. User Name Password Multi-Record Datamaps Source Type CDC Datamaps Subsystem Id Required Required N/a Required N/a Required Working with Relational Source and Target Definitions 23 . or DB2UDB Select to list CDC extraction maps . Password associated with the User name. DB2390.

Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). enter A* to display schemas and/or tables that begin with an A. enter *cust* to display schemas and/or tables that contain “cust. Enter a schema and/or table name. “No Data Found” will appear in the Selected Datamaps list. Required/ Optional Required Optional Optional Description Name of the database for connection. Optionally. will appear in the Selected Datamaps list. ? (question mark).Attribute Database Name Schema Map name 3.” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive. Represents one or more characters. enter a filter condition to display schemas and/or tables that meet the filter condition. Or. based on the values specified in the dialog box.Working with Mappings . Enter the filter condition as a suffix. Represents one character. 4. The available tables. If no tables are found. For example. Enter a table name to filter the resulting data maps. For example. 24 Chapter 3: PWXPC . For example. enter a filter to view particular schemas and tables from the database. Enter the filter condition as a prefix. Enter a schema name to filter the resulting data maps. enter *A to display schemas and/or tables that end with an A. DB2400 and DB2UDB only. Enter the filter condition as a substring. Click Connect.

Use the Select all button to select all tables. Select the table you want to import. Import from PowerExchange . Hold down the Ctrl key to make non-contiguous selections within a schema. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. 6. Working with Relational Source and Target Definitions 25 .DB2390 Select Datamaps List Schema Table 5. The source or target definition appears in the workspace. Use the Select none button to clear all highlighted selections. Click OK. Figure 3-5.The Designer displays metadata to import.

You can create a Microsoft SQL Server target definition in the following ways: ♦ ♦ ♦ See the PowerCenter Designer Guide for more information about using PowerCenter to create source and target definitions. you can use them to extract data from or load data to a Microsoft SQL Server table. Import table definitions from Microsoft SQL Server using the PowerCenter ODBC interface. Use the following procedure to import Microsoft SQL Server source or target definitions. Manually create a Microsoft SQL definition. Manually create a Microsoft SQL definition. or locally without a Listener. To import a Microsoft SQL Server source definition. Import table definitions from Microsoft SQL Server using the PowerCenter ODBC interface. Import table definitions from Microsoft SQL Server using PowerExchange. see “Working with Extraction Map Definitions” on page 53. Import extraction map definitions from PowerExchange. to import SQL Server metadata. To import a Microsoft SQL Server source or target definition: 1. For more information.Working with Mappings . However. When you connect to the database. When you import a Microsoft SQL Server definition through a PowerExchange Listener or locally. To import a Microsoft SQL Server target definition.Working with Microsoft SQL Server Definitions You can create a Microsoft SQL Server source definition in the following ways: ♦ ♦ ♦ ♦ Import table definitions from Microsoft SQL Server using PowerExchange. select Sources > Import from PowerExchange and select a source type of MSSQL. you can filter the metadata the Designer displays by schema and/or table name. 26 Chapter 3: PWXPC . the Designer displays database schemas and tables. the Designer imports the primary keys. Before you connect to the database. the metadata definition must match the table structure of the Microsoft SQL Server table. select Targets > Import from PowerExchange and select a source type of MSSQL. Importing a Microsoft SQL Server Relational Source or Target Definition You can connect to a Microsoft SQL Server database through a PowerExchange Listener. Tip: If your repository contains Microsoft SQL Server definitions. Select a table to create the source or target definition.

User ID for connection to the database. SEQ or VSAM sources only.Microsoft SQL Server source The target dialog box looks similar but does not contain the Multi-Record Datamaps and CDC Datamaps options. MSSQL Select to list CDC extraction maps . User Name Password Multi-Record Datamaps Source Type CDC Datamaps Server Name Required Required N/a Required N/a Required Working with Relational Source and Target Definitions 27 . Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover. 2.The dialog box for the Microsoft SQL Server source definition input looks as follows: Figure 3-6.cfg) on the system on which the database resides. Select to list multi-record data maps.source only SQL Server instance name. Password associated with the User ID. Import from PowerExchange .

“No Data Found” will appear in the Selected Datamaps list. For example. based on the values specified in the dialog box. enter a filter to view particular schemas and tables from the database. enter *cust* to display schemas and/or tables that contain “cust. Enter the filter condition as a substring.Working with Mappings . The available tables. Enter the filter condition as a suffix. Required/ Optional Required Optional Optional Description Database name in the SQL instance specified. 28 Chapter 3: PWXPC . Represents one character. 4. enter A* to display schemas and/or tables that begin with an A. Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). Enter a schema name to filter the resulting data maps. will appear in the Selected Datamaps list.Attribute Database Name Schema Map name 3. Enter a table name to filter the resulting data maps. enter a filter condition to display schemas and/or tables that meet the filter condition. enter *A to display schemas and/or tables that end with an A. Or. For example. ? (question mark). Click Connect. For example. Enter a schema and/or table name. Enter the filter condition as a prefix. Represents one or more characters. Optionally.” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive. If no tables are found.

Select the table you want to import. Use the Select none button to clear all highlighted selections. Import from PowerExchange . ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. Hold down the Ctrl key to make non-contiguous selections within a schema. Figure 3-7.The Designer displays metadata to import. The source or target definition appears in the workspace. Working with Relational Source and Target Definitions 29 . Use the Select all button to select all tables.MSSQL Select Datamaps List Schema Table 5. 6. Click OK.

Use the following procedure to import Oracle source or target definitions.Working with Mappings . Import table definitions from Oracle using the PowerCenter ODBC interface. to import Oracle metadata. the metadata definition must match the table structure of the Oracle table. Before you connect to the database. see “Working with Extraction Map Definitions” on page 53. Import extraction map definitions from PowerExchange. select Targets > Import from PowerExchange and select a source type of Oracle. or locally without a Listener. Tip: If your repository contains Oracle definitions. 30 Chapter 3: PWXPC . To import an Oracle source definition. Import table definitions from Oracle using the PowerCenter ODBC interface. the Designer imports the primary keys. F You can create an Oracle target definition in the following ways: ♦ ♦ ♦ See the PowerCenter Designer Guide for more information about using PowerCenter to create source and target definitions. When you import an Oracle source definition through a PowerExchange Listener. select Sources > Import from PowerExchange and select a source type of Oracle. the Designer displays database schemas and tables. To import an Oracle source or target definition: 1. For more information.Working with Oracle Definitions You can create an Oracle source definition in the following ways: ♦ ♦ ♦ ♦ Import table definitions from Oracle using PowerExchange. Manually create an Oracle source definition. Manually create an Oracle source definition. you can filter the metadata the Designer displays by schema and/or table name. When you connect to the database. Import table definitions from Oracle using PowerExchange. However. To import an Oracle target definition. you can use them to extract data from or load data to an Oracle table. Importing a Oracle Relational Source or Target Definition You can connect to an Oracle database through a PowerExchange Listener. Select a table to create the source or target definition.

source only. Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover. Password associated with the user name. User Name Password Multi-Record Datamaps Source Type CDC Datamaps TNS Name Required Required N/a Required N/a Required Working with Relational Source and Target Definitions 31 .The Import from PowerExchange > Oracle dialog box looks as follows: Figure 3-8. SEQ or VSAM sources only. Select to list multi-record data maps.Oracle source The target dialog box looks similar but does not contain the Multi-Record Datamaps and CDC Datamaps options. Oracle SID (instance name). Select to list CDC extraction maps . User name for the database connecting to. ORACLE. Import from PowerExchange .cfg) on the system on which the database resides. 2.

Represents one character. 32 Chapter 3: PWXPC . Represents one or more characters. Enter the filter condition as a substring. If no tables are found. enter a filter to view particular schemas and tables from the database.Working with Mappings . The available tables. Optionally. Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). Required/ Optional Optional Optional Description Enter a schema name to filter the resulting data maps. enter a filter condition to display schemas and/or tables that meet the filter condition. Enter the filter condition as a suffix. For example. Enter the filter condition as a prefix. based on the values specified in the dialog box. Enter a schema and/or table name. Or. enter A* to display schemas and/or tables that begin with an A. For example. For example. enter *cust* to display schemas and/or tables that contain “cust.” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive. ? (question mark). enter *A to display schemas and/or tables that end with an A. “No Data Found” will appear in the Selected Datamaps list. Enter a table name to filter the resulting data maps. 4. Click Connect. will appear in the Selected Datamaps list.Attribute Schema Map name 3.

6. The source or target definition appears in the workspace. Use the Select none button to clear all highlighted selections. Select the table you want to import.The Designer displays metadata to import. Import from PowerExchange . Click OK.Oracle Select Datamaps List Schema Table 5. Use the Select all button to select all tables. Figure 3-9. Hold down the Ctrl key to make non-contiguous selections within a schema. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. Working with Relational Source and Target Definitions 33 .

To import an Sybase source definition. you can use them to extract data from a Sybase source. Before you connect to the database. the Designer displays database schemas and tables. Select a table to create the source or target definition. or locally without a Listener. To import an Sybase target definition. Use the following procedure to import Sybase source or target definitions. To import an Sybase source or target definition: 1. you can filter the metadata the Designer displays by schema and/or table name. select Targets > Import from PowerExchange and select a source type of Sybase. Manually create an Sybase target definition. Importing a Sybase Relational Source or Target Definition You can connect to an Sybase database through a PowerExchange Listener. When you connect to the database. to import Sybase metadata.Working with Sybase Definitions You can create a Sybase source definition in the following ways: ♦ ♦ ♦ Import table definitions from Sybase using PowerExchange. When you import an Sybase source definition through a PowerExchange Listener. 34 Chapter 3: PWXPC . Tip: If your repository already contains Sybase definitions. Manually create an Sybase source definition. You can create an Sybase target definition in the following ways: ♦ ♦ ♦ See the PowerCenter Designer Guide for more information about using PowerCenter to create source and target definitions. the metadata definition must match the table structure of the Sybase table.Working with Mappings . select Sources > Import from PowerExchange and select a source type of Sybase. However. the Designer imports the primary keys. Import table definitions from Sybase using PowerExchange. Import table definitions from Sybase using the PowerCenter ODBC interface. Import table definitions from Sybase using the PowerCenter ODBC interface.

Password associated with the user name.The Import from PowerExchange > Sybase dialog box looks as follows: Figure 3-10. Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover. Select to list multi-record data maps. N/A for Sybase Sybase Server Name.cfg) on the system on which the database resides. Sybase Database Name.Sybase source 2. Import from PowerExchange . SEQ or VSAM sources only. SYBASE. User name for the database connecting to. Select to list CDC extraction maps. User Name Password Multi-Record Datamaps Source Type CDC Datamaps Server Name Database Name Required Required N/A Required N/A Required Required Working with Relational Source and Target Definitions 35 .

enter a filter condition to display schemas and/or tables that meet the filter condition. “No Data Found” will appear in the Selected Datamaps list.Attribute Schema Map name 3. Enter the filter condition as a suffix. enter *A to display schemas and/or tables that end with an A. ? (question mark). Enter a schema and/or table name. The available tables. For example. For example. enter A* to display schemas and/or tables that begin with an A. Enter the filter condition as a substring.Working with Mappings . Optionally. Represents one character. Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). Enter the filter condition as a prefix. Or. enter *cust* to display schemas and/or tables that contain “cust. Represents one or more characters. will appear in the Selected Datamaps list. 4. 36 Chapter 3: PWXPC .” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive. Click Connect. enter a filter to view particular schemas and tables from the database. For example. Enter a table name to filter the resulting data maps. Required/ Optional Optional Optional Description Enter a schema name to filter the resulting data maps. based on the values specified in the dialog box. If no tables are found.

♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. Hold down the Ctrl key to make non-contiguous selections within a schema. Editing Relational Source and Target Definitions You can edit relational source and target definition to make minor changes to the definition. Click OK. Add or delete columns. Modify column data types. Working with Relational Source and Target Definitions 37 . you can: ♦ ♦ ♦ Modify column names. Use the Select none button to clear all highlighted selections. Figure 3-11.Sybase Select Datamaps List Schema Table 5. Select the table you want to import. 6.The Designer displays metadata to import. Import from PowerExchange . For example. Use the Select all button to select all tables. The source or target definition appears in the workspace.

It then uses the value of the DTL__CAPXACTION to construct the appropriate SQL statement (INSERT. see the PowerCenter Designer Guide. Add a description of the definition.♦ ♦ Modify column key relationships. 38 Chapter 3: PWXPC . UPDATE. or DELETE). For more information about editing source and target definitions.Working with Mappings . PWXPC will automatically include the DTL__CAPXACTION column in its SELECT statement for CDC sources. Note: If using the relational source in a CDC session you do not need to add the DTL__CAPXACTION field nor do you need to include an Update Strategy.

Non-relational definitions represent the data map metadata in groups. you can create source definitions to read from. and target definitions to write to.source only IDMS . Group name Working with Non-Relational Source and Target Definitions 39 . Each group represents a table in the data map. the following non-relational data types: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Adabas Datacom .source only DB2 data maps (DB2MAP) .source only DB2/390 unload files (DB2UNLD) .source only IMS SEQ VSAM You can create a non-relational source and target definitions by importing a data map from a PowerExchange Listener. Non-Relational Source Definition with Multiple Records A group represents a table in the PowerExchange data map. The tables in the VSAM data map are represented as groups in the source definition: Figure 3-12. The following diagram shows a non-relational source definition for a VSAM data map that contains multiple tables representing multiple records in the VSAM file.Working with Non-Relational Source and Target Definitions With PowerExchange Client for PowerCenter. Each group also contains metadata for the fields in the table.

Working with Mappings .In this example. When you connect to PowerExchange. Before you connect to PowerExchange. V07C_RECORD_LAYOUT and V07D_RECORD_LAYOUT. you can filter the metadata the Designer displays by schema and/or data map name. You can use the following procedure to import multi-record (VSAM and sequential only) or single record data map source definitions. the Designer imports the data map as a single group. Importing Non-Relational Source Definitions You can connect to PowerExchange locally or to a PowerExchange Listener to import a nonrelational source definition or a data mapped DB2 definition. Some data maps contain records that have hierarchical relationships with each other. Select a data map to create the source definition. V07B_RECORD_LAYOUT. The same procedure is used to import multi-record data maps (VSAM and sequential). the source definition contains four groups: V07A_RECORD_LAYOUT. the Designer displays data map schemas and tables for the source type specified. These groups are tables in the data map. The groups contain metadata for the fields in the tables. When you import data maps with hierarchies. records can have a parent/child relationships. For example. 40 Chapter 3: PWXPC . Select the Multi-Record Datamaps box on the Import dialog box to import multi-record data maps.

Non-Relational Source 2. or VSAM. IDMS. User Name Password Multi-Record Datamaps Source Type Required Required Optional Required Working with Non-Relational Source and Target Definitions 41 . SEQ. The Import from PowerExchange dialog box looks as follows: Figure 3-13. IMS. Select one of the following source types: ADABAS. Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover.cfg) on the system on which the database resides. select Sources > Import from PowerExchange and select the desired source type. SEQ or VSAM sources only. DATACOM. Import from PowerExchange . User name for the database to connect to.To import a non-relational source definition: 1. DB2UNLD. To import a non-relational source definition. Password associated with the User name. The dialog box and parameters displayed are the same for each non-relational source type. Select to list multi-record data maps. DB2MAP.

Represents one character. Click Connect. Each record in a multi-record data map is effectively a single record data map. 42 Chapter 3: PWXPC . The following two examples show the results when single record VSAM data maps and multi-record VSAM data maps are selected.source only. Or. Enter a schema name to filter the resulting data maps. enter *A to display schemas and/or tables that end with an A. For example.Working with Mappings .Attribute CDC Datamaps Schema Map name Selected Datamaps Required/ Optional n/a Optional Optional n/a Description Select to list CDC extraction maps . Optionally. Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). Enter a schema and/or table name. Enter the filter condition as a prefix. enter A* to display schemas and/or tables that begin with an A. Each record in the multi-record data map will display in Selected Datamaps list when importing single record data maps. Enter the filter condition as a suffix. enter a filter to view particular schemas and tables from the database. It is possible to import only a single record within a multi-record data map as a source. The Designer displays metadata to import. enter a filter condition to display schemas and/or tables that meet the filter condition. For example. Lists the available data maps for the connection. enter *cust* to display schemas and/or tables that contain “cust. Enter a data map name to filter the resulting data maps. For example. ? (question mark). The available data maps appear in the Selected Datamaps list. Enter the filter condition as a substring.” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive. 4. database and filter details that you entered. 3. Represents one or more characters.

This example shows the results for single record VSAM data maps: Figure 3-14.Single Record Source Data Maps Schema Table Working with Non-Relational Source and Target Definitions 43 . Import from PowerExchange .

Import from PowerExchange . 44 Chapter 3: PWXPC .Multiple Record Source Data Maps Schema Table 5. Select the data map you want to import. The Designer uses the data map name as the name of the source definition. Use the Select none button to clear all highlighted selections. Select a data map to create the source definition.This example shows the results for multi-record VSAM data maps: Figure 3-15. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. When you connect to PowerExchange. The source definitions appear. Importing Non-Relational Target Definitions You can connect to PowerExchange locally or to a PowerExchange Listener to import a nonrelational target definition. you can filter the metadata the Designer displays by schema and/or data map name. 6. Use the Select all button to select all tables. the Designer displays data map schemas and tables for the target type specified.Working with Mappings . Click OK. Before you connect to PowerExchange. Hold down the Ctrl key to make non-contiguous selections within a data map.

To import a non-relational target definition: 1. or VSAM Enter a schema name to filter the resulting data maps. User name for the database to connect to. Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover.cfg) on the system on which the database resides. User Name Password Source Type Schema Required Required Required Optional Working with Non-Relational Source and Target Definitions 45 . The dialog box and parameters displayed are the same for each non-relational source type. select Targets > Import from PowerExchange and select the desired target type. SEQ. Select one of the following source types: ADABAS. Password associated with the User name. To import a non-relational target definition. The Import from PowerExchange dialog box for targets looks as follows: Figure 3-16. IMS. Import from PowerExchange .Non-Relational Target 2.

Enter the filter condition as a prefix. Or.” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive. Represents one character. 46 Chapter 3: PWXPC . Optionally. Lists the available data maps for the connection. Enter a schema and/or table name. enter a filter to view particular schemas and tables from the database. Enter the filter condition as a suffix. For example. 3. database and filter details that you entered. Represents one or more characters. Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). enter *cust* to display schemas and/or tables that contain “cust. Enter the filter condition as a substring. The Designer displays metadata to import. ? (question mark). enter a filter condition to display schemas and/or tables that meet the filter condition.Working with Mappings . Click Connect. For example.Attribute Map name Selected Datamaps Required/ Optional Optional n/a Description Enter a data map name to filter the resulting data maps. enter A* to display schemas and/or tables that begin with an A. enter *A to display schemas and/or tables that end with an A. For example. 4. The available data maps appear in the Selected Datamaps list.

Use the Select none button to clear all highlighted selections. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. Hold down the Ctrl key to make non-contiguous selections within a data map. 6. Working with Non-Relational Source and Target Definitions 47 . Use the Select all button to select all tables. Import from PowerExchange . Select the data map you want to import. Click OK.Non-Relational Target Select Datamaps List Schema Table 5. The Designer uses the data map name as the name of the source definition.The following example shows the results when a Source Type of VSAM is selected: Figure 3-17. The source definitions appear.

Attributes Table 3-1 describes the attributes the Attributes tab displays for each field in the nonrelational definition: Table 3-1. Name of the record to which the field belongs. Attributes of Fields in a Non-Relational Source Definition Attribute Name column_name base_rec base_fld Description Name of the field in the data map. Figure 3-18 shows the Attributes information for a non-relational VSAM definition: Figure 3-18.Viewing Non-Relational Source and Target Definition Details Non-relational source and target definitions contain information about the data map structure on the Attributes tab. Viewing Data Map Information The Attributes tab of a non-relational source or target definition lists each field in the definition. Additional metadata information is included on the Metadata Extensions tab. It also lists the attributes of each field and their values from the data map used to create the definition. Name of the base record and table field name in the following format: <Base_Field_Name>:<Table_Field_Name> 48 Chapter 3: PWXPC . Non-Relational Table .Working with Mappings . This corresponds to name of the group the field belongs to in the source definition. The attributes include information such as the name of the base record to which the field belongs.

You determine the offset value of each field based on the order of fields in the data map. Offset value from which the field starts.Table 3-1. You can override the data map name and schema name in the session properties. See “Editing Metadata Extensions” on page 50. For example. The following example shows the Metadata Extensions information for a VSAM definition: Figure 3-19. the field starts at the fifth position. if the value is 5. See “Session Properties for Non-Relational Batch Mode Sessions” on page 127. Non-Relational Table . Attributes of Fields in a Non-Relational Source Definition Attribute Name base_fld_tpe base_fld_offset Description PowerExchange data type of the field.Metadata Extensions Working with Non-Relational Source and Target Definitions 49 . the File Name extension field can be modified. Viewing Metadata Extensions Non-relational source and target definitions have metadata extensions that displays additional information from the data map used to create the definition. With VSAM and sequential definitions.

Editing Metadata Extensions With VSAM and sequential definitions.The following table describes the extensions on the Metadata Extensions tab for a nonrelational definition: Table 3-2.X = Datacom . Non-Relational Source Definition Metadata Extensions Extension Name Access Method Description Method you specified in the data map to access the source database: . Name of the schema on which you based the data map.W = DB2 unload file (DB2UNLD) . the File Name extension field can be modified. comments File Name Map Name Schema Name Editing Non-Relational Source and Target Definitions You can edit non-relational source and target definitions to make minor changes to the definition. All other field populated by PWXPC when a data map is imported cannot be changed.K = VSAM KSDS . 50 Chapter 3: PWXPC .Z = DB2 data map Any comments. see the PowerCenter Designer Guide. UPDATE.D =IMS DL1 .A = Adabas . Name of the data set (sequential or VSAM only) Name of the data map.O = IMS ODBA . For more information about editing source definitions. or DELETE).Working with Mappings . you can: ♦ ♦ ♦ ♦ ♦ ♦ modify a column data type modify the owner name modify column key relationships add or delete columns add a description of the definition create metadata extensions Note: If using the non-relational source in a CDC session you do not need to add the DTL__CAPXACTION field nor do you need to include an Update Strategy. For example.S = sequential (SEQ) . PWXPC will automatically include the DTL__CAPXACTION column in its SELECT statement for CDC sources.I = IDMS .N = VSAM RRDS . It then uses the value of the DTL__CAPXACTION to construct the appropriate SQL statement (INSERT.E = VSAM ESDS .

Double click on the source or target definition in the workspace.By default. The VSAM was created prior to PowerCenter V8. Select the Metadata Extensions tab. 3. Click on the Value field and select the down arrow.5: The following procedure explains how to manually update the File Name field to add or change the file name in a VSAM or sequential definition: Manually updating the file name field: 1. The following example shows the metadata extensions for a VSAM definition which was created prior to PowerCenter V8. The following example shows the metadata extensions for a VSAM definition.5 so the File Name field is blank. this field can be populated manually or by re-importing the data map. the File Name field contains the value from the PowerExchange data map File Name field which contains the VSAM data set name or the sequential file name. Note: Any VSAM and sequential definitions created prior to PowerCenter V8. If desired. PWXPC populates the File Name field with the File Name for the PowerExchange data map. 2. Working with Non-Relational Source and Target Definitions 51 .5 will have a blank File Name.

You can also re-import the PowerExchange data map to automatically populate the File Name field with the information contained in the data map. Click OK when done. 4.Working with Mappings .The Edit Metadata Extension Value panel displays allowing you to enter or change the file name. 52 Chapter 3: PWXPC . Click OK to end Edit Tables.

select Sources > Import from PowerExchange and select the CDC Datamaps box and then select the desired source type. Select an extraction map to create the source definition. When you connect to PowerExchange. you can filter the metadata the Designer displays by schema and/or data map name. Extraction maps are imported using the Import from PowerExchange dialog box and are uniquely suited for the following cases: ♦ ♦ The extraction map for the source contains a subset of the actual columns defined for the source. the Designer displays the extraction map schemas and tables. Working with Extraction Map Definitions 53 . You can connect to PowerExchange locally or to a PowerExchange Listener to import an extraction map definition. To import an extraction map as a source definition 1. The PowerExchange generated columns like DTL__CAPXTIMESTAMP. and DTL__BI before image columns are needed. The dialog box and parameters displayed are the same for each non-relational source type. DTL__CAPXACTION. import the extraction map rather than the source table metadata. To import an extraction map source definition.Working with Extraction Map Definitions When creating mappings for Change Data Capture (CDC). Before you connect to PowerExchange. Connect to the capture source platform location where the extraction maps are stored.

Select to list multi-record data maps. Import from PowerExchange . User Name Password Multi-Record Datamaps Source Type CDC Datamaps Schema Map name Required Required N/a Required Required Optional Optional 54 Chapter 3: PWXPC . DB2400. Select to list CDC extraction maps . ORACLE or VSAM. IDMS. DB2390. Enter a data map name to filter the resulting data maps. DB2UDB. SEQ or VSAM sources only. DATACOM.CDC Datamaps Enter the following connection information: Attribute Location Required/ Optional Required Description Name of the PowerExchange Listener (Node name from PowerExchange dbmover.The Import from PowerExchange dialog box looks as follows: Figure 3-20. Select one of the following source types: ADABAS.source only. User name for the database connecting to. Password associated with the User name.cfg) on the system on which the database resides. IMS. MSSQL.Working with Mappings . Enter a schema name to filter the resulting data maps.

Figure 3-21.” Use the following syntax when entering a wildcard character: ♦ ♦ ♦ Note: Schema and table names are not case sensitive.2. For example. enter *A to display schemas and/or tables that end with an A. ? (question mark). Represents one character. Import from PowerExchange . Represents one or more characters. Or. Enter the filter condition as a substring. Enter the filter condition as a suffix.CDC Select Datamaps List Schema Table Working with Extraction Map Definitions 55 . Enter the filter condition as a prefix. Optionally. Use one of the following wildcard characters in the filter condition: ♦ ♦ * (asterisk). The Designer displays the metadata to import. 3. For example. For example. The extraction maps shown will be filtered based on the source type specified. enter a filter condition to display schemas and/or tables that meet the filter condition. Click Connect. enter *cust* to display schemas and/or tables that contain “cust. enter A* to display schemas and/or tables that begin with an A. Enter a schema and/or table name. enter a filter to view particular schemas and tables from the database.

Use the Select all button to select all tables. 4. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. Hold down the Ctrl key to make non-contiguous selections within a data map. only extraction maps for a specific Schema and Map name appear in the Designer. 5.Working with Mappings . Select the data map you want to import. The Designer uses the data map name as the name of the source definition. The source definition appears in the workspace. Click OK.In this example. 56 Chapter 3: PWXPC . Use the Select none button to clear all highlighted selections.

They also contain metadata extensions on the Metadata Extensions tab. Viewing Extraction Map Information The Attributes tab of a extraction map definition lists each field in the source definition. The attributes include information such as the name of the base record to which the field belongs. blank Working with Extraction Map Definitions 57 . blank blank. Attributes of Fields in a Extraction Map Definition Attribute Name column_name base_rec base_fld base_fld_tpe base_fld_offset Description Name of the field in the extraction map.Viewing Extraction Map Definition Details Extraction map definitions contain information about the data map structure on the Attributes tab. Figure 3-22 shows the Attributes tab of a extraction map definition: Figure 3-22. Extraction Map Table .Attributes Table 3-3 describes the attributes the Attributes tab displays for each field in the source definition: Table 3-3. It also lists the attributes of each field and their values based on the extraction map from which you imported the source definition. blank.

However. Original table name in relational database or PowerExchange data map comments Map Name Original Name 58 Chapter 3: PWXPC .Metadata Extensions The following table describes the extensions on the Metadata Extensions tab for an extraction map definition: Table 3-4. Name of the extraction map.L = MSSQL .V = DB2/UDB .Viewing Metadata Extensions Extraction map definitions have metadata extensions that display information about the data map on which you based the source definition.Working with Mappings .N = VSAM RRDS .I = IDMS .P = Oracle .E = VSAM ESDS . You cannot modify these metadata extensions.D =IMS .K = VSAM KSDS . you can override the data map name and schema name in the session properties. Extraction Map Table .X = Datacom Any comments. The following example shows the Metadata Extensions tab of a extraction map definition: Figure 3-23. Extraction Map Definition Metadata Extensions Extension Name Access Method Description Method you specified in the data map to access the source database: .A = Adabas .B = DB2/390 and DB2/400 .

Warning: Changing column information in the extraction map could result in failures in the session or workflow during the extraction process. UPDATE. Add or delete columns. PWXPC will automatically include the DTL__CAPXACTION column in its SELECT statement for CDC sources. see the PowerCenter Designer Guide. It then uses the value of the DTL__CAPXACTION to construct the appropriate SQL statement (INSERT. For example. Create metadata extensions. Extraction Map Definition Metadata Extensions Extension Name Original Schema Schema Name Description Original schema or owner name in relational database or PowerExchange data map Name of the schema for the extraction map. Add a description of the definition. Note: When using extraction maps. you do not need to add the DTL__CAPXACTION field nor do you need to include an Update Strategy. or DELETE). For more information about editing source definitions. you can: ♦ ♦ ♦ ♦ ♦ Modify a column data type. Working with Extraction Map Definitions 59 . Modify the owner name. Editing a Extraction Map Definition You can edit extraction map definitions to make minor changes to the definition.Table 3-4.

Preview source and target data in the Mapping Designer while creating a mapping. You must be able to connect to PowerExchange on the source or target database platform to preview data. Mapping Designer. Note: This process uses an ODBC data source to connect to PowerExchange. 2.Working with Mappings . Non-relational. Preview source data in the Mapplet Designer while creating a mapplet. You can preview source or target data in the following Designer tools: For sources and targets other than those accessed through PowerExchange. ♦ ♦ ♦ ♦ Relational. There are three database types for PowerExchange source and target definitions: 1. To preview relational source or target data: 1. Target Designer. You can also preview changed data for extraction map source definitions. 3. Previewing data allows you to see the source or target data. Extraction Maps. see the PowerCenter Designer Guide. The data that is shown depends upon the database type of the source or target definition. Select a relational source or target definition in the workspace. Right-click the source or target definition in the workspace and choose Preview Data.Previewing PowerExchange Data in Designer You can preview data in the Designer for any valid relational and non-relational source or target definitions. Preview target data in the Target Designer after you import a target. such as PWX_VSAM_NRDB2 for VSAM data maps. You cannot preview data for multi-record data map source definitions. Preview source data in the Source Analyzer after you import the source. such as DB2 for DB2 metadata. such as PWX_DB2390_CDC for DB2 CDC data maps. Mapplet Designer. 2. Previewing PowerExchange Relational Data Previewing data for source or target relational definitions displays data from the relational table. Source Analyzer. 60 Chapter 3: PWXPC .

Click Connect. For PowerExchange sources and targets on MVS and AS/400. 6. Select an ODBC data source name. 4.. 3.. 5. You can add a new ODBC data source using the . Enter the number of rows you want to preview. 7. this is only necessary if connecting to a PowerExchange Listener configured with security (SECURITY=1 or SECURITY=2 in DBMOVER).000 columns. Previewing PowerExchange Data in Designer 61 . button. The Preview Data dialog box can display up to 500 rows and up to 65.The Preview Data dialog box appears. Enter the database table owner name. enter the Username and Password. If necessary. The default is 100.

The contents of the table appear in the Preview Data dialog box. Select a non-relational source or target definition in the workspace. 62 Chapter 3: PWXPC . 8. In the case of DB2 data maps. Previewing data for non-relational definitions uses PWXPC to connect to PowerExchange. To preview non-relational source or target data: 1. enter a new number and click Refresh. Click Close to exit. 2. 9. You must be able to connect to PowerExchange on the source or target platform to preview data. Right-click the source or target definition in the workspace and choose Preview Data. To change the number of rows you want to preview.Working with Mappings . Previewing PowerExchange Non-Relational Data Previewing data for source or target non-relational definitions displays data from the nonrelational file. data from the source DB2 table displays.

For PowerExchange sources and targets on MVS and AS/400.cfg file on the Designer platform. edit this file and add additional NODE statements. 5. Select a Location name. enter the Username and Password. The Schema field is automatically populated with the PowerExchange data map schema name. Click Connect. The default is 10. If necessary. The Location names are retrieved from the NODE statements in the dbmover. 6. To add additional Locations. 3.000 columns. Enter the number of rows you want to preview. The Preview Data dialog box can display up to 500 rows and up to 65. This can be changed if desired. 4.The Preview Data dialog box appears. 7. Previewing PowerExchange Data in Designer 63 . this is only necessary if connecting to a PowerExchange Listener configured with security (SECURITY=1 or SECURITY=2 in DBMOVER).

10. Right-click the source definition in the workspace and choose Preview Data. Select an extraction map source definition in the workspace. To preview non-relational source or target data: 1. 64 Chapter 3: PWXPC . enter a new number and click Connect. Click Close to exit. 2. To change the number of rows you want to preview. click More. Previewing PowerExchange Changed Data Previewing data for extraction map (CDC datamaps) definitions displays changed data from the change stream. To return more data.The contents of the table appear in the Preview Data dialog box.Working with Mappings . Previewing data for extraction maps uses PWXPC to connect to PowerExchange. You must be able to connect to PowerExchange on the source platform to preview data. 9. 8.

Select a Location name. To add additional Locations. 6.The Preview Data dialog box appears. If desired. For PowerExchange sources and targets on MVS and AS/400. change the Time Out value. this is only necessary if connecting to a PowerExchange Listener configured with security (SECURITY=1 or SECURITY=2 in DBMOVER).cfg file on the Designer platform. enter the Username and Password. Real Time extracts data in real-time from the change stream using the earliest starting restart point. The Schema field is automatically populated with the PowerExchange extraction map schema name. 3. edit this file and add additional NODE statements. 4. This can be changed if desired. Change extracts data from condense files using the earliest starting restart point. Select either Real Time or Change. If necessary. 7. See “Default Restart Points” on page 155 for more information about default restart points. Previewing PowerExchange Data in Designer 65 . The Location names are retrieved from the NODE statements in the dbmover. 5.

The time out value indicates the maximum time (in seconds) to wait for additional data at the end of log. 10. the More button is greyed out. Returning EOF terminates any further retrieval of data from the change stream. The Preview Data dialog box can display up to 500 rows and up to 65. The value can be any number between 0 and 86400.000 columns. Enter the number of rows you want to preview. Do not specify 86400 as no data is displayed and the Preview Data session hangs until the extraction task in PowerExchange Listener is stopped. click More. When the end of log is reached. The default is 10 seconds. 9. EOF is returned and the number of rows requested is displayed. To return more data. The default is 10.Working with Mappings . After this time period expires. The contents of the table appear in the Preview Data dialog box. A value of 0 indicates that EOF is returned as soon as the end of log is reached whereas 86400 indicates that EOF is never returned. 66 Chapter 3: PWXPC . 8. Click Connect.

enter a new number and click Connect. Previewing PowerExchange Data in Designer 67 . 12. To change the number of rows you want to preview. Click Close to exit.11.

Traditionally. For more information on how to do this. a sequential data set containing three different record layouts would be read. Using Group Source with Non-Relational Sources VSAM and sequential datasets that contain multiple record types with physically different record layouts in a single data set are candidates for Group Source.PowerExchange Group Source PowerExchange Client for PowerCenter uses PowerExchange Group Source functionality. the data set would be read in its entirety for each of the different record types imported. To exploit this functionality. For CDC data. Each group represents a table in the data map. Records are then provided to the appropriate source in the mapping. For multi-record VSAM or sequential data sets. This provides enhanced performance by eliminating multiple passes of the data. This is done by selecting the “Multi-record Datamaps” box on the Import dialog box. three times to provide the data to each record type. see “Importing Non-Relational Source Definitions” on page 40. This results in separate tables to represent the relational view of each record. For example. the Group Source functionality of PowerExchange can be used for multirecord VSAM and sequential datasets resulting in the data set/file being read only once regardless of the number of unique record types that exist. in its entirety. As a result. Each group also contains metadata for the fields in the table. With PWXPC. Group Source is used when reading Changed Data Capture (CDC) data. the table for each record type would be imported into PowerCenter Designer thereby decoupling the relational view of the data from the physical data set. Within PowerExchange each record type is separately defined as a unique record in the data map.Working with Mappings . It also reduces the resource consumption of PowerExchange on the platform from which the data is being extracted. It can also be used when processing VSAM and sequential datasets or files that have multiple record types. the metadata must be imported as a multi-record data map in Designer. 68 Chapter 3: PWXPC . Non-relational source definitions represent the data map metadata in groups. Group Source allows PowerExchange to read all data from the same physical source in a single pass. the file needs only be read once to acquire all of the record types. this means that changes for all tables defined in the mapping can be read from the change stream in a single pass.

You can create a CDC source definition that can use group source in the following ways: ♦ ♦ Import table definitions from the relational database using PowerExchange. Import extraction map definitions from PowerExchange for all source types. see “Working with Extraction Map Definitions” on page 53. For more information. Import data map table definitions from PowerExchange (non-relational and DB2/390 sources). see “Working with Non-Relational Source and Target Definitions” on page 39. PowerExchange Group Source 69 ♦ ♦ . For more information. the Group Source functionality of PowerExchange can be used for all CDC sources resulting in the change stream for the CDC source being read only once. Each source definition in a mapping will result in a connection to PowerExchange to read the source data. Using Group Source with CDC Sources With PWXPC. see the PowerCenter Designer Guide.Figure 3-24 shows a non-relational source definition with multiple groups: Figure 3-24. For more information. see “Working with Relational Source and Target Definitions” on page 21. It is possible to have multiple multirecord source definitions in a mapping and each one can use Group Source processing. Multi-record Non-Relational Source Definition PowerExchange map name PowerExchange data map table name The PowerExchange NRDB Batch application connection is used to read the data and uses Group Source functionality. Group Source processing for multi-record non-relational data maps is done for each source definition. For more information. for each unique source type. regardless of the number of source tables included in the mapping. Import relational table definitions using the PowerCenter ODBC interface.

group source is invoked at a mapping level for all source definitions rather than at an individual source definition level. It also eliminates the need to add any of the special DTL columns: the DTL__CAPX fields. If these two mappings are included in two sessions in the same workflow. for CDC sources as this eliminates the need to specify the extraction map name in the Session Properties. they result in separate Group Source connections to the change stream: one for VSAM and one for IMS. the DTL__CI change indicator fields. The invocation of Group Source occurs automatically when a PWX Change or Real-Time connection is used in a session. will fail with: PWXPC_10080 [ERROR] All the readers should be of one database type only For example. even if the same change stream is being read.Working with Mappings . This can significantly simplify the mapping design process. Two separate mappings should be made: one for the VSAM sources and one for the IMS sources. a mapping containing both VSAM and IMS sources will fail with the 10080 message. the source metadata must be imported using PWXPC. Sessions with a mappings containing multiple source types. or CDC Datamaps. It also occurs automatically if a multi-record source definition exists in a mapping. and the DTL__BI before image fields. Group Source functionality is invoked for each source type.For non-relational CDC sources. regardless of the number of sources included in the session. With CDC access. A mapping should contain only a specific source type. Tip: Use extraction maps. Group Source Mapping Example 70 Chapter 3: PWXPC . The following diagram shows an example of a mapping for three DB2 sources: Figure 3-25. Group Source for batch access to non-relational sources requires that the source be imported as a multi-record data map and is used for an individual source definition.

using Group Source.When you include this mapping in a session that uses the PowerExchange DB2 CDC application connection. PowerExchange Group Source 71 . When you include this mapping in a session that uses a PowerExchange DB2 relational connection. The changes for each source are provided to the source qualifier in the chronological order in which each unit of work (UOW) completed. A unique pipeline is created for each source which results in three unique tasks in the PowerExchange Listener. PowerExchange reads through the change stream a single time. to extract the changes for all three source tables. PowerExchange reads each source table separately.

see the PowerCenter Transformation Guide. For more information about Source Qualifier transformations. the Integration Service converts the data based on the datatypes in the target definition. the Integration Service performs transformations based on the transformation datatypes. see the PowerCenter Transformation Guide.Working with Mappings . For more information about transformation datatypes. Transformation Datatypes The transformation datatypes in Source Qualifier and Application Multi-Group Source Qualifier transformations are internal datatypes based on ANSI SQL-92 generic datatypes. You cannot change the data type for any of the fields in the Application Multi-Group Source Qualifier transformations. The transformation data type for all ports in the Application Multi-Group Source Qualifier transformation are predefined. Non-relational source definitions use an Application Multi-Group Source Qualifier transformation. When you run a session.Working with Source Qualifiers Source qualifiers determine how the Integration Service reads data from the source. You connect a source qualifier to a source instance in a mapping. see the PowerCenter Designer Guide. You cannot edit an Application Multi-Group Source Qualifier transformation. you can edit the transformation. Similarly. When the Integration Service reads data from a source. When writing data to a target. Creating Source Qualifiers By default. For more information about source qualifiers. The type of source qualifier you use depends on the source definition: ♦ ♦ Relational source definitions use a Source Qualifier transformation. which PowerCenter uses to move data across platforms. 72 Chapter 3: PWXPC . you must manually connect the source qualifier to the source definition. it converts the data from the PowerExchange data type to the transformation data type. If you configure the PowerCenter Designer to manually create a source qualifier when you add a source definition to a mapping. Editing Source Qualifier Transformations After you create a Source Qualifier transformation. the PowerCenter Designer creates an Application Multi-Group Source Qualifier transformation when you add a non-relational source definition to a mapping. it creates a Source Qualifier transformation when you add a relational source definition to a mapping.

Concatenated keys (CCK) fields achieve the best performance with the least impact on the IMS database. For more information. PWX Oracle. see “Configuring Lookups for IMS” on page 73. Usage Considerations for PowerExchange Sources and Targets There are a number of unique usage considerations for using Lookup transformations with PowerExchange sources and targets. PWX DB2UDB. careful consideration needs to be given to the fields used to perform the search of the IMS database. select the “Lookup source is static” transformation attribute to avoid failures during session execution. ♦ Configuring Lookups for IMS Using keys is a fast and efficient method of retrieving data from IMS databases. See “Configuring Connections” on page 81 for connection configuration information. through PowerExchange.Using Lookup Transformations This section discusses considerations for using lookup transformations with PWXPC for PowerExchange sources and targets. − ♦ ♦ When using Lookup transformations with a resume recovery strategy. See the PowerCenter Transformation Guide for more information about Lookup transformations and lookup caching. Using Lookup Transformations 73 . PowerExchange allows you to build Concatenated Key (CCK) fields in the data map. select the appropriate PWXPC relational connection for the database type. first import the definitions using the Import from PowerExchange dialog box in either the Source Analyzer or Target Designer prior to configuring the lookup in the mapping. use special custom properties to ensure change stream data is accessible across pipelines. For non-relational files. or synonym. These are listed below: ♦ The Lookup transformation import process uses ODBC for non-relational files and relational tables. or relational table to which both the PowerCenter Client and Integration Service can connect. PWX NRDB Lookup. PWX Microsoft SQL Server. ♦ You can use PWXPC connections for lookup both non-relational files and relational tables: − For relational tables. When using Lookup transformations with IMS databases. non-relational file. see “Configuring Lookups for CDC Data” on page 74. When using Lookup transformations for targets being updated with CDC data in the same mapping. in a non-relational file or a relational table. Use a Lookup transformation in a mapping to look up data. You can import a lookup definition for any flat file. For more information about search fields for IMS lookups. To use PWXPC to import definitions for non-relational files or relational tables. or PWX Sybase. such as PWX DB2390. See “NRDB Lookup Relational Connections” on page 94 for connection configuration information. view. PWX DB2400. select the PWXPC relational connection for NRDB lookups.

Search fields defined in the IMS Database Definition (DBD). the order of the changes read from the change 74 Chapter 3: PWXPC . If using Search fields. You can specify either the CCK field or the key field for the desired segment as both will exist in the IMS source or target definition. at minimum. To provide search keys for IMS database lookups. the root CCK field. This causes a scan of the IMS database to be done in order to find a match. Configuring Lookups for CDC Data Lookup transformations can be used in mappings extracting data from CDC sources including tables to which the CDC data is being applied. Only use non-key or non-search fields as a last resort. it must be marked as a key in the IMS source or target definition in Designer. use the following types of fields in the Lookup condition transformation attribute: ♦ Concatenated Key (CCK) fields. Key fields. specify both of the following custom properties in the session Custom Properties attribute field on the Config Object tab: ♦ ♦ MergeCDCReaders=Yes SingleThreadExecutionModel=Yes These custom properties remove any partition points from the PWXPC CDC Reader through the transformations to the Writer. Non-key or non-search fields. Specify these as keys in the IMS source or target definition and use them in the Lookup condition attribute. Specify these fields as key in the IMS source or target definition and use them in the Lookup condition attribute. Fields specified in the Lookup condition transformation attribute are used by PowerExchange to create the Segment Search Argument (SSA). Using CCK fields results in the most efficient search of the IMS database. a combination of both CCK fields and key fields will likely be needed in the Lookup condition.Working with Mappings . IMS can still scan the IMS segments using an IMS search field. This type of search call is not as efficient as a keyed search with CCK fields or key fields. Specify these fields as keys in the IMS source or target definition and use them in the Lookup condition attribute. See the PowerExchange IMS Adapter Guide for more information about creating CCK fields. In order for a field to be used in the SSA. include its CCK field with the search fields to limit the amount of data IMS scans and therefore the impact on the database. As a result. If the segment is not the root. If the segment does not have a key. ♦ ♦ ♦ Tip: You can limit the amount of the database that will be scanned by specifying as many CCK and key fields as possible. If you are using dynamic lookups for CDC data and sharing the lookup cache with other static lookups in the same mapping. include as many CCK fields as possible and. The least efficient search method is to mark non-key fields or non-search fields as keys in the IMS source or target definition and in the Lookup condition attribute.Concatenated Key (CCK) fields allows PowerExchange to construct a fully-qualified Segment Search Argument (SSA) thereby improving IMS database search efficiency. Assuming the root segment is keyed. This can adversely affect your IMS operational system and therefore should be avoided.

Warning: The use of these custom properties will impact session throughput as it will singlethread all source data from the Reader through to the Writer. Using Lookup Transformations 75 . As a result. This then ensures that any CDC data placed into a dynamic lookup cache is accessible to lookups sharing that cache in other pipelines.stream is maintained until the changes reach the Writer. these custom properties should only be specified when there is a need to share CDC data stored in a dynamic cache across pipeline.

76 Chapter 3: PWXPC .Working with Mappings .

Chapter 4 PWXPC . 102 Sybase Batch Mode Relational Connections. 78 DB2 Batch Mode Relational Database Connections.Configuring Connections This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 84 DB2 CDC Mode Application Connections. 105 Configuring Connections Attributes. 87 NRDB Batch Mode Application Connections. 97 Oracle Batch Mode Relational Connections. 90 NRDB CDC Mode Application Connections. 91 NRDB Lookup Relational Connections. 100 Oracle CDC Mode Application Connections. 94 MSSQL Batch Mode Relational Connections. 121 77 . 95 MSSQL CDC Mode Application Connections. 106 Understanding Commit Processing with PWXPC.

you configure relational database or application connections. you must configure connections in the Workflow Manager. For PowerExchange Client for PowerCenter. Connection Types for Extracting Source Data Source Type Adabas Extraction Mode Batch Change Real-Time Datacom Batch Change Real-Time DB2/390 Batch Change Real-Time DB2/400 Batch Change Real-Time DB2/UDB Batch Change Real-Time IDMS Batch Change Real-Time Connection Type Application Application Application Application Application Application Relational Application Application Relational Application Application Relational n/a Application Application Application Application Connection Name PWX NRDB Batch PWX NRDB CDC Change PWX NRDB CDC Real Time PWX NRDB Batch PWX NRDB CDC Change PWX NRDB CDC Real Time PWX DB2390 PWX DB2390 CDC Change PWX DB2390 CDC Real Time PWX DB2400 PWX DB2400 CDC Change PWX DB2400 CDC Real Time PWX DB2UDB n/a PWX DB2UDB CDC Real Time PWX NRDB Batch PWX NRDB CDC Change PWX NRDB CDC Real Time 78 Chapter 4: PWXPC . When you create or modify a session that reads from or writes to a database of file. you can select only configured source and target databases.Configuring Connections . depending upon the source or the target type. Connection Types for Extracting Source Data The connection you configure depends on the type of source data you want to extract and the extraction mode. Connections are saved in the repository. Table 4-1 describes the connections you create for data extraction based on the data source and the extraction mode: Table 4-1.Overview Before the Integration Service can access a source or target in a session.

Table 4-1. Connection Types for Loading Target Data Target Type Adabas DB2/390 DB2/400 DB2 UDB IMS MSSQL Server Connection Type Application Relational Relational Relational Application Relational Comments PWX NRDB Batch PWX DB2390 PWX DB2400 PWX DB2UDB PWX NRDB Batch PWX MSSQLServer Overview 79 . Connection Types for Extracting Source Data Source Type IMS Extraction Mode Batch Change Real-Time MSSQL Batch Change Real-Time Oracle Batch Change Real-Time SEQ Batch Change Real-Time Sybase Batch Change Real-Time VSAM Batch Change Real-Time Connection Type Application Application Application Relational n/a Application Relational Application Application Application n/a n/a Relational n/a n/a Application Application Application Connection Name PWX NRDB Batch PWX NRDB CDC Change PWX NRDB CDC Real Time PWX MSSQLServer n/a PWX MSSQL CDC Real Time PWX Oracle PWX Oracle CDC Change PWX Oracle CDC Real Time PWX NRDB Batch n/a n/a PWX Sybase n/a n/a PWX NRDB Batch PWX NRDB CDC Change PWX NRDB CDC Real Time Connection Types for Loading Target Data The connection you configure depends on the type of target data you want to load. Table 4-2 describes the relational database connections you create to load data to supported PowerExchange targets: Table 4-2.

Table 4-2.Configuring Connections . Connection Types for Loading Target Data Target Type Oracle SEQ (sequential) Sybase VSAM Connection Type Relational Application Relational Application Comments PWX Oracle PWX NRDB Batch PWX Sybase PWX NRDB Batch 80 Chapter 4: PWXPC .

Configuring Connections The connection you configure depends upon the database or data structure. To configure connections: 1. 2. For more information about available connection types. Relational Connection Browser Configuring Connections 81 . see Table 4-1 on page 78 and Table 4-2 on page 79. The Relational Connection Browser dialog box appears: Figure 4-1. Loading data (Batch) to a relational target. In the Workflow Manager. Extracting changed data (Change or Real-Time) from non-relational or relational sources. Loading data (Batch) to a non-relational target. To configure a PowerExchange Batch relational database connection. click Connections > Relational. connect to a PowerCenter repository. Source and target connections can be configured for: ♦ ♦ ♦ ♦ Extracting data (Batch) from relational or non-relational sources.

see Table 42 on page 79. Application Connection Browser In the Select Type field. 3. For a list of connections to configure according to data source and extraction mode. click Connections > Application.To configure a PowerExchange application connection. Click New. 82 Chapter 4: PWXPC . select the type of connection you want to create.Configuring Connections . see Table 4-1 on page 78. The Application Connection Browser dialog box appears: Figure 4-2. For a list of connections to configure according to target data type.

select the connection from the list and click the appropriate button. Application Connection Editor 4. Click OK. The new connection appears in the Application or Relational Object Browser. The relational and application dialog boxes are very similar. The various connection types are described in subsequent sections in this chapter. Enter the values for the connection attributes. To edit or delete a relational database or application connections. An application dialog box is shown here: Figure 4-3. Configuring Connections 83 . 5.The Connection Object Definition dialog box appears.

Delete Or Update statements. and DB2UDB relational database connections: Table 4-3.Configuring Connections . Separate libraries with semicolons. the Database file overrides takes precedence. Table 4-3 describes the connection attributes you configure for PWX DB2390. DB2 subsystem or database instance name. Select to compress source data during the PowerCenter session. Separate libraries with semicolons. regardless of whether the file is qualified or not. Select the code page for the Integration Server to use to extract data from the source database. the Database file overrides takes precedence. and DB2UDB Relational Database Connection Attributes Connection Attribute Name Code Page Required Yes Yes DB2390 DB2400 DB2UDB All All Description Name of the relational database connection. and DB2/UDB to extract data and load data in batch mode to DB2 sources and targets. Location Database Name User Name Password Isolation Level Database file overrides Yes Yes Yes Yes Yes No All All All All DB2400 DB2400 84 Chapter 4: PWXPC . Note: If both Library List and Database file overrides are specified and a table exists both.cfg.DB2 Batch Mode Relational Database Connections Configure relational database connections for DB2/390. Environment SQL Compression No No All All SQL commands run in the database environment. DB2400. Commit scope of the transaction. DB2/400. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. This includes any files qualified using Library List. Note: If both Library List and Database file overrides are specified and a table exists both. Library List No DB2400 List of libraries that PowerExchange searches to qualify the table name for Select. Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. User name for the database connected to. Note: In Unicode mode. Insert. PWX DB2390. Overrides any occurrence of the specified filename (in any SQL statement) with the library/filename/member specified. DB2400. See “Configuring Encryption and Compression” on page 106. PowerExchange searches the list if the table name is unqualified. Default is CS. Password for the user name.

Select to cause PowerExchange to load data to DB2/390 targets using the DB2 bulk loader.INSERT .AFTER SUCCESS ONLY . pacing size is in number of rows. the PowerExchange ignores these attributes. Value for the primary space on MVS. Default is DB2LDCTL.Table 4-3. Name of the Control file template on the target system.NO . See “Configuring Pacing” on page 107. If using this connection for a DB2 Bulk Load may load DB2 partitions. Select the encryption level. Enter the pacing size. Default is 0. When loading partitions it is easiest to use a single connection but to change the file name in the targets. If you select this option. Select one of the following values: .REPLACE Default is INSERT. and DB2UDB Relational Database Connection Attributes Connection Attribute Encryption Type Encryption Level Pacing Size Interpret as Rows Bulk Load* Required Yes No Yes No No DB2390 DB2400 DB2UDB All All All All DB2/390 Description Select the encryption type.BEFORE . PWX DB2390. Name of the JCL file template on the target system. See “Configuring Encryption and Compression” on page 106. See “Configuring Encryption and Compression” on page 106. you can configure the remaining connection attributes. Filename* No DB2/390 Space* Yes DB2/390 Primary Space* Secondary Space* Delete Temporary Files* Yes Yes Yes DB2/390 DB2/390 DB2/390 JCL Template* CTL Template* Load Options* Yes Yes Yes DB2/390 DB2/390 DB2/390 DB2 Batch Mode Relational Database Connections 85 . Specifies whether.TRACK .CYLINDER Default is TRACK. Enter one of the following values to allocate MVS space in tracks or cylinders: . or not. DB2400. Default is DB2LDJCL. Otherwise. Value for the secondary space on MVS. Default is 0. Enter a file name to use as a stem for files created on the host machine. This can be overridden in the Workflow.AFTER Default is NO. See “Configuring Pacing” on page 107. Select one of the following values: .

Select one of the following values: . Default is Confirm Write On.DATAONLY Default is WAIT. PWX DB2390. and DB2UDB Relational Database Connection Attributes Connection Attribute Mode Type* Required Yes DB2390 DB2400 DB2UDB DB2/390 Description Select one of the following values: . See “Configuring Write Mode” on page 109.Table 4-3.Configuring Connections . See “Converting Character Data to Strings” on page 108. Default is no. Value from 1 to 99998 to specify the wait time in seconds when you select JOB for the Mode Type and TIMED for Mode Time. Select the write mode. see the PowerExchange Reference Manual.JOB .NOSUBMIT Default is TASK.TASK .TIMED . *For more information. See the PowerExchange Reference Manual for further information. Convert embedded nulls in character fields to spaces. Note: Specifying PWXDISABLE will prevent creation of the reject files. Mode Time* Yes DB2/390 Time* Yes DB2/390 Convert character data to string Write Mode Reject File No All No No All All 86 Chapter 4: PWXPC . Default is 0. PowerExchange creates the reject file on the target machine when the Write Mode is Asynchronous with Fault Tolerance. DB2400.WAIT . Overrides the default prefix of PWXR for the reject file.NO WAIT .

For a list of connections to configure according to data source and extraction mode. See “Configuring CDC Restart Attributes” on page 115. Specifies whether. pacing size is in number of rows. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. See “Configuring Encryption and Compression” on page 106. See “Configuring Image Type” on page 111. DB2/400 and DB2/UDB in real-time or change (except DB2/UDB) modes. Password for the user name.DB2 CDC Mode Application Connections Configure application connections to extract data from DB2/390. See “Configuring Pacing” on page 107. Specify the Restart token folder. Note: In Unicode mode. Select the code page for the Integration Service to use to extract data from the source database. See “Configuring Encryption and Compression” on page 106. Location User Name Password Compression Yes Yes Yes No Both Both Both Both Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. Select the encryption type. Default is the first 20 characters of the workflow name. see Table 4-1 on page 78. Default is $PMRootDir/Restart. and DB2UDB CDC Mode Application Connection Attributes Connection Attribute Name Code Page Required Yes Yes Change or Real-time Both Both Description Name of the relational database connection. or not. Default is BA. See “Configuring CDC Restart Attributes” on page 115. Select the image type. DB2400. User name for DB2. Select to compress source data during the PowerCenter session. Enter the pacing size. Table 4-4 describes the connection attributes you configure for DB2/390. Specify the Application Name. See “Configuring Pacing” on page 107. DB2390.cfg. Encryption Type Encryption Level Pacing Size Interpret as Rows Image Type Yes No Yes No No Both Both Both Both Both Application Name No Both RestartToken File Folder Yes Both DB2 CDC Mode Application Connections 87 . See “Configuring Encryption and Compression” on page 106. Select the encryption level. DB2/400 and DB2/UDB application connections: Table 4-4.

0 = EOF is returned at the end of log. Reader Time Limit does not limit the reader time. Specifies the number of seconds the PowerExchange Listener remains idle after reaching the end of the change log (as indicated by message PWX-09967) before returning an end-offile (EOF). n = n is the number of seconds. Default is 0. If you enter: -1 = UOW count is not used 0 = UOW count is not used n = n is the count of UOWs See “Configuring UOW Count” on page 116 and “Understanding Commit Processing with PWXPC” on page 121. See “Managing Session Log and Restart Token File History” on page 172.Configuring Connections . This attribute is intended for testing purposes only. Specifies the number of units of work (UOWs) you want the PWXPC to read from the source before flushing data to the target. and DB2UDB CDC Mode Application Connection Attributes Connection Attribute RestartToken File Name Required No Change or Real-time Both Description Specify the Restart token file. the session terminates successfully.Table 4-4. See “Configuring CDC Restart Attributes” on page 115. If you enter: -1 = EOF is never retuned. See “Enabling Session Recovery” on page 163. Default is the Application Name if specified or the workflow name if Application Name is not specified. Default is 0. Tip: Use Idle Time instead of Reader Time Limit. Default is $PMRootDir/Cache. Default is -1. See “Configuring Idle Time” on page 113. Reader Time Limit No Real Time Specifies the number of seconds that Integration Service reads data from the source before stopping. DB2400. DB2390. If you enter 0. Number of Runs to Keep RestartToken File No Both Recovery Cache Folder UOW Count No Both No Both Idle Time No Real Time 88 Chapter 4: PWXPC . Specify file cache folder to enable recovery for the session. Default is 1. Specify the maximum number of backup copies to keep of the Restart Token File. the session runs continuously.

DB2400. Default is no. Overrides the default CAPI connection name. Includes all related PowerExchange log entries in the session log.. Specify complete library and journal names in the format: library/journal Library/File Override* No Both Overrides the library and file name in the extraction map. DB2 CDC Mode Application Connections 89 . PWXPC sets values between 0 and 2000 to 2000. See “Configuring Real-Time Flush Latency” on page 117. Overrides the library and journal name in the PowerExchange CAPI_CONNECTION. Specifies the PowerExchange extraction map name used for event processing. See “Retrieving PWX Log Entries” on page 110. Warning: Do not specify an asterisk for library name if using PWXPC restart. Valid values are between 0 and 86400 milliseconds. See “Configuring Event Table Processing” on page 112. Default is 0. Commit Threshold No Real Time Journal Name* No Both No Real Time CAPI Connection Name Override Retrieve PWX Log Entries No Real Time No Both * These attributes only apply to PWX CDC DB2400 Real Time application connections. and DB2UDB CDC Mode Application Connection Attributes Connection Attribute Real-time Flush Latency Required No Change or Real-time Real Time Description Specifies the milliseconds between buffer flushes. See “Converting Character Data to Strings” on page 108.Table 4-4. Default is 0. See “Configuring Commit Threshold” on page 119. Specifies the number of change records (not UOWs) after which a commit should be inserted into the change stream. See “Configuring the CAPI Connection Name Override” on page 113. Specify complete library and file names in the format: library/file This attribute overrides the Library/File Override value on the application connection. Convert character data to string Event Table No Both Converts embedded nulls in character fields to spaces. DB2390.

See “Configuring Encryption and Compression” on page 106. Select the code page for the Integration Service to use to extract data from the source database. Default is Confirm Write On. User name for the database being connected to. Location User Name Password Compression Encryption Type Encryption Level Pacing Size Interpret as Rows Confirm Write Convert character data to string Retrieve PWX Log Entries Yes Yes Yes No No No No No No No Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. See “Configuring Write Mode” on page 109. Default is no. or not. See “Converting Character Data to Strings” on page 108. Select to compress source data during the PowerCenter session. Convert embedded nulls in character fields to spaces. Enter the pacing size. Table 4-5 describes the connection attributes you configure for non-relational batch mode application connections: Table 4-5. See “Configuring Pacing” on page 107. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. See “Configuring Pacing” on page 107. see Table 4-1 on page 78. NRDB Batch Mode Application Connection Attributes Connection Attribute Name Code Page Required Yes Yes Description Name of the relational database connection. Select the encryption level.NRDB Batch Mode Application Connections Configure application connections to extract data from non-relational databases (NRDB) in batch mode. For a list of connections to configure according to data source and extraction mode. See “Configuring Encryption and Compression” on page 106. Password for the user name. Include all related PowerExchange log entries in the session log. Note: In Unicode mode.cfg. pacing size is in number of rows. Selects the write mode. Select the encryption type. No 90 Chapter 4: PWXPC . Specifies whether.Configuring Connections . See “Configuring Encryption and Compression” on page 106.

PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. See “Configuring CDC Restart Attributes” on page 115. Specify the Application Name. or not. Select the encryption type. Enter the pacing size. See “Configuring Encryption and Compression” on page 106. Encryption Type Encryption Level Pacing Size Interpret as Rows Image Type Yes No Yes No No Both Both Both Both Both Application Name No Both RestartToken File Folder Yes Both NRDB CDC Mode Application Connections 91 . See “Configuring Pacing” on page 107. See “Configuring CDC Restart Attributes” on page 115. Specify the Restart token folder. Select the encryption level. see Table 4-1 on page 78. Default is $PMRootDir/Restart.cfg. For a list of connections to configure according to data source and extraction mode. NRDB CDC Mode Application Connection Attributes Connection Attribute Name Code Page Required Yes Yes Change or Real-time Both Both Description Name of the application connection. Note: In Unicode mode. pacing size is in number of rows. See “Configuring Encryption and Compression” on page 106. See “Configuring Pacing” on page 107.NRDB CDC Mode Application Connections Configure application connections to extract data from non-relational databases in change mode or real-time mode. Password for the user name. Table 4-6 describes the connection attributes you configure for non-relational database change and real-time mode application connections: Table 4-6. See “Configuring Encryption and Compression” on page 106. Select to compress source data during the PowerCenter session. Specifies whether. Default is the first 20 characters of the workflow name. Select the image type. See “Configuring Image Type” on page 111. Select the code page for the Integration Service to use to extract data from the source database. User name for the database being connected to. Default is BA. Location User Name Password Compression Yes Yes Yes No Both Both Both Both Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover.

the session terminates successfully. This attribute is intended for testing purposes only. If you enter: -1 = UOW count is not used 0 = UOW count is not used n = n is the count of UOWs See “Configuring UOW Count” on page 116 and “Understanding Commit Processing with PWXPC” on page 121. See “Managing Session Log and Restart Token File History” on page 172. Default is 0. Default is the Application Name if specified or the workflow name if Application Name is not specified.Configuring Connections . See “Configuring Idle Time” on page 113. See “Configuring CDC Restart Attributes” on page 115. Specifies the number of units of work (UOWs) you want the PWXPC to read from the source before flushing data to the target. Reader Time Limit does not limit the reader time.Table 4-6. See “Enabling Session Recovery” on page 163. Number of Runs to Keep RestartToken File No Both Recovery Cache Folder UOW Count No Both No Both Idle Time No Real Time 92 Chapter 4: PWXPC . Default is $PMRootDir/Cache. the session runs continuously. If you enter: -1 = EOF is never retuned. NRDB CDC Mode Application Connection Attributes Connection Attribute RestartToken File Name Required No Change or Real-time Both Description Specify the Restart token file. 0 = EOF is returned at the end of log. Specifies the number of seconds the PowerExchange Listener remains idle after reaching the end of the change log (as indicated by message PWX-09967) before returning an end-offile (EOF). Specify the maximum number of backup copies to keep of the Restart Token File. Tip: Use Idle Time instead of Reader Time Limit. Default is 1. If you enter 0. Reader Time Limit No Real Time Specifies the number of seconds that Integration Service reads data from the source before stopping. Default is 0. n = n is the number of seconds. Specify file cache folder to enable recovery for the session. Default is -1.

Default is 0. See “Configuring the CAPI Connection Name Override” on page 113 Include all related PowerExchange log entries in the session log.Table 4-6. See “Converting Character Data to Strings” on page 108. Overrides the default CAPI connection name. See “Configuring Commit Threshold” on page 119. PWXPC sets values between 0 and 2000 to 2000. NRDB CDC Mode Application Connection Attributes Connection Attribute Real-time Flush Latency Required No Change or Real-time Real Time Description Specifies the milliseconds between buffer flushes. Commit Threshold No Real Time Convert character data to string Event Table No Both No Real Time CAPI Connection Name Override Retrieve PWX Log Entries No Real Time No Both NRDB CDC Mode Application Connections 93 . See “Configuring Event Table Processing” on page 112. Valid values are between 0 and 86400 milliseconds. Convert embedded nulls in character fields to spaces. Default is 0. See “Configuring Real-Time Flush Latency” on page 117. Specifies the PowerExchange extraction map name used for event processing. Specifies the number of change records (not UOWs) after which a commit should be inserted into the change stream. Default is no.

Note: In Unicode mode. See “Configuring Pacing” on page 107. See “Converting Character Data to Strings” on page 108. User name for the Listener being connected to. Default is no. Select the encryption level.Configuring Connections . Table 4-7 describes the connection attributes you configure for NRDB Lookup relational database connections: Table 4-7. pacing size is in number of rows. Password for the user name. See “Configuring Encryption and Compression” on page 106. For more information about using lookups for non-relational definitions.cfg. Convert embedded nulls in character fields to spaces. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. Location User Name Password Environment SQL Compression Encryption Type Encryption Level Pacing Size Interpret as Rows Convert character data to string Yes Yes Yes No No No No No No No Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. Enter the pacing size. SQL commands run in the database environment. Select the encryption type. See “Configuring Encryption and Compression” on page 106. NRDB Lookup Relational Connection Attributes Connection Attribute Name Code Page Required Yes Yes Description Name of the relational database connection. Select the code page for the Integration Service to use to extract data from the source database. 94 Chapter 4: PWXPC . See “Configuring Pacing” on page 107. Select to compress source data during the PowerCenter session. Specifies whether. or not. See “Configuring Encryption and Compression” on page 106. see “Using Lookup Transformations” on page 73.NRDB Lookup Relational Connections Configure NRDB Lookup relational database connections when using lookups to extract data from PowerExchange non-relational source and target definitions.

Name of the database in the SQL Server instance. Enter the pacing size. see “Configuring Encryption and Compression” on page 106. Encryption Type No Encryption Level No Pacing Size No Interpret as Rows No MSSQL Batch Mode Relational Connections 95 . PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. Table 4-8 describes the connection attributes you configure for Microsoft SQL Server relational database connections: Table 4-8. Default is 0. Name of the SQL Server instance. Select the encryption level. Location Server Name Database Name User Name Password Environment SQL Compression Yes Yes Yes Yes Yes No No Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. or not.cfg. For more information. SQL commands run in the database environment. pacing size is in number of rows. For more information. For more information. see “Configuring Encryption and Compression” on page 106. Default is 1. Select the code page for the Integration Service to use to extract data from the source database. Select the encryption type. Default is None.MSSQL Batch Mode Relational Connections Configure relational database connections for Microsoft SQL Server to extract data and load data in batch mode to SQL Server sources and targets. Select to compress source data during the PowerCenter session. see “Configuring Encryption and Compression” on page 106. For more information. Note: In Unicode mode. User name for the database being connected to. Specifies whether. see “Configuring Pacing” on page 107. see “Configuring Pacing” on page 107. Password for the user name. MSSQL Batch Mode Relational Connection Attributes Connection Attribute Name Code Page Required Yes Yes Description Name of the relational database connection. For more information.

Table 4-8. No 96 Chapter 4: PWXPC . MSSQL Batch Mode Relational Connection Attributes Connection Attribute Convert character data to string Write Mode Required No Description Convert embedded nulls in character fields to spaces. Default is Confirm Write On. Default is no. See “Converting Character Data to Strings” on page 108. See “Configuring Write Mode” on page 109.Configuring Connections . Select the write mode.

Specifies whether. See “Configuring Encryption and Compression” on page 106. or not. Specify the Application Name. See “Configuring CDC Restart Attributes” on page 115. See “Configuring Pacing” on page 107. See “Configuring CDC Restart Attributes” on page 115. User name for the Microsoft SQL Server database. See “Configuring Encryption and Compression” on page 106. pacing size is in number of rows. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. See “Configuring Image Type” on page 111. Specify the Restart token file. Default is $PMRootDir/Restart. Enter the pacing size. Select the encryption type. Table 4-9 describes the connection attributes you configure for Microsoft SQL Server realtime mode application connections: Table 4-9. See “Configuring CDC Restart Attributes” on page 115. Select the encryption level. Default is the first 20 characters of the workflow name. Password for the user name. MSSQL CDC Mode Application Connection Attributes Connection Attribute Name Code Page Required Yes Yes Description Name of the application connection. Specify the Restart token folder. Application Name No RestartToken File Folder RestartToken File Name Yes No MSSQL CDC Mode Application Connections 97 .cfg. Default is BA. Default is the Application Name if specified or the workflow name if Application Name is not specified. Location User Name Password Compression Encryption Type Encryption Level Pacing Size Interpret as Rows Image Type Yes Yes Yes No Yes No Yes No No Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. See “Configuring Pacing” on page 107. Select the image type. Select to compress source data during the PowerCenter session. Select the code page for the Integration Service to use to extract data from the source database. Note: In Unicode mode.MSSQL CDC Mode Application Connections Configure a PWX MSSQL CDC Real Time application connection to extract data from Microsoft SQL Server in real-time mode. See “Configuring Encryption and Compression” on page 106.

If you enter: -1 = UOW count is not used 0 = UOW count is not used n = n is the count of UOWs See “Configuring UOW Count” on page 116 and “Understanding Commit Processing with PWXPC” on page 121. Reader Time Limit No Specifies the number of seconds that Integration Service reads data from the source before stopping. Default is 1. See “Enabling Session Recovery” on page 163. No No Idle Time No Commit Threshold No 98 Chapter 4: PWXPC . Default is 0. Specifies the number of change records (not UOWs) after which a commit should be inserted into the change stream. the session terminates successfully. If you enter 0. Tip: Use Idle Time instead of Reader Time Limit. Specifies the number of seconds the PowerExchange Listener remains idle after reaching the end of the change log (as indicated by message PWX09967) before returning an end-of-file (EOF). See “Configuring Real-Time Flush Latency” on page 117. Specifies the number of units of work (UOWs) you want the PWXPC to read from the source before flushing data to the target. Real-time Flush Latency No Specifies the milliseconds between buffer flushes. This attribute is intended for testing purposes only. If you enter: -1 = EOF is never retuned. See “Configuring Commit Threshold” on page 119. Default is 0. n = n is the number of seconds.Table 4-9. the session runs continuously. MSSQL CDC Mode Application Connection Attributes Connection Attribute Number of Runs to Keep RestartToken File Recovery Cache Folder UOW Count Required No Description Specify the maximum number of backup copies to keep of the Restart Token File. Specify file cache folder to enable recovery for the session.Configuring Connections . Default is 0. Reader Time Limit does not limit the reader time. Valid values are between 0 and 86400 milliseconds. See “Configuring Idle Time” on page 113. See “Managing Session Log and Restart Token File History” on page 172. 0 = EOF is returned at the end of log. Default is -1. PWXPC sets values between 0 and 2000 to 2000. Default is 0. Default is $PMRootDir/Cache.

Overrides the default CAPI connection name. No No No MSSQL CDC Mode Application Connections 99 . See “Configuring the CAPI Connection Name Override” on page 113. Include all related PowerExchange log entries in the session log. Specifies the PowerExchange extraction map name used for event processing. MSSQL CDC Mode Application Connection Attributes Connection Attribute Convert character data to string Event Table CAPI Connection Name Override Retrieve PWX Log Entries Required No Description Convert embedded nulls in character fields to spaces. See “Converting Character Data to Strings” on page 108. See“Configuring Event Table Processing” on page 112.Table 4-9. Default is no.

SQL commands run in the database environment. See “Configuring Encryption and Compression” on page 106. Note: In Unicode mode.Oracle Batch Mode Relational Connections Configure relational database connections for Oracle to extract data and load data in batch mode to Oracle sources and targets. See “Configuring Encryption and Compression” on page 106. User name for the database being connected to. Net Service Name of the Oracle instance. Default is no. Select the encryption type.Configuring Connections . Oracle Batch Mode Relational Connection Attributes Connection Attribute Name Code Page Required Yes Yes Description Name of the relational database connection. Select the encryption level. Convert embedded nulls in character fields to spaces. See “Configuring Pacing” on page 107. Select to compress source data during the PowerCenter session. Specifies whether.cfg. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. Table 4-10 describes the connection attributes you configure for Oracle relational database connections: Table 4-10. Enter the pacing size. Password for the user name. 100 Chapter 4: PWXPC . See “Configuring Pacing” on page 107. See “Configuring Encryption and Compression” on page 106. pacing size is in number of rows. Select the code page for the Integration Service to use to extract data from the source database. Location TNS Name User Name Password Environment SQL Compression Encryption Type Encryption Level Pacing Size Interpret as Rows Convert character data to string Yes Yes Yes Yes No No No No No No No Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. See “Converting Character Data to Strings” on page 108. or not.

Table 4-10. See the PowerExchange Reference Manual for further information. Oracle Batch Mode Relational Connection Attributes Connection Attribute Write Mode Reject File Required No No Description Select the write mode. See “Configuring Write Mode” on page 109. Note: Specifying PWXDISABLE will prevent creation of the reject files. Default is Confirm Write On. Oracle Batch Mode Relational Connections 101 . Overrides the default prefix of PWXR for the reject file. PowerExchange creates the reject file on the target machine when the Write Mode is Asynchronous with Fault Tolerance.

Specify the Application Name. Select the image type. See “Configuring Encryption and Compression” on page 106. Table 4-11 describes the connection attributes you configure for Oracle real-time mode application connections: Table 4-11. See “Configuring Encryption and Compression” on page 106. Select to compress source data during the PowerCenter session. Specifies whether. See “Configuring Pacing” on page 107.Oracle CDC Mode Application Connections Configure a PWX Oracle Change Capture Real Time application connection to extract data from Oracle in real-time mode. Enter the pacing size.Configuring Connections . pacing size is in number of rows. Note: In Unicode mode. See “Configuring Pacing” on page 107. Default is the first 20 characters of the workflow name. Select the encryption level. See “Configuring CDC Restart Attributes” on page 115. Oracle CDC Mode Application Connection Attributes Connection Attribute Name Code Page Required Yes Yes Change or Real-time Both Both Description Name of the application connection. Location User Name Password Compression Yes Yes Yes No Both Both Both Both Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. Default is $PMRootDir/Restart.cfg. See “Configuring Image Type” on page 111. Select the code page for the Integration Service to use to extract data from the source database. Default is BA. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. User name for Oracle. Select the encryption type. Specify the Restart token folder. Encryption Type Encryption Level Pacing Size Interpret as Rows Image Type Yes No Yes No No Both Both Both Both Both Application Name No Both RestartToken File Folder Yes Both 102 Chapter 4: PWXPC . See “Configuring Encryption and Compression” on page 106. or not. See “Configuring CDC Restart Attributes” on page 115. Password for the user name.

Default is -1. Specify file cache folder to enable recovery for the session. Specifies the number of seconds the PowerExchange Listener remains idle after reaching the end of the change log (as indicated by message PWX-09967) before returning an end-offile (EOF). Default is 1. See “Enabling Session Recovery” on page 163. Number of Runs to Keep RestartToken File No Both Recovery Cache Folder UOW Count No Both No Both Idle Time No Real Time Oracle CDC Mode Application Connections 103 . If you enter 0. Specify the maximum number of backup copies to keep of the Restart Token File. Default is the Application Name if specified or the workflow name if Application Name is not specified. See “Configuring CDC Restart Attributes” on page 115. Specifies the number of units of work (UOWs) you want the PWXPC to read from the source before flushing data to the target. If you enter: -1 = UOW count is not used 0 = UOW count is not used n = n is the count of UOWs See “Configuring UOW Count” on page 116 and “Understanding Commit Processing with PWXPC” on page 121.Table 4-11. Default is $PMRootDir/Cache. Default is 0. See “Managing Session Log and Restart Token File History” on page 172. Tip: Use Idle Time instead of Reader Time Limit. the session runs continuously. See “Configuring Idle Time” on page 113. This attribute is intended for testing purposes only. 0 = EOF is returned at the end of log. n = n is the number of seconds. Reader Time Limit does not limit the reader time. Default is 0. the session terminates successfully. Oracle CDC Mode Application Connection Attributes Connection Attribute RestartToken File Name Required No Change or Real-time Both Description Specify the Restart token file. Reader Time Limit No Real Time Specifies the number of seconds that Integration Service reads data from the source before stopping. If you enter: -1 = EOF is never retuned.

Default is 0. Overrides the instance information in the ORACLEID statement in the PowerExchange configuration file (dbmover. see the PowerExchange Oracle Adapter Guide. Overrides the default CAPI connection name. Valid values are between 0 and 86400 milliseconds. Specifies the PowerExchange extraction map name used for event processing. See “Configuring Event Table Processing” on page 112. See “Configuring Commit Threshold” on page 119. For more information. Commit Threshold No Real Time Instance Name No Real Time Connect String No Real Time Source Schema Name Convert character data to string Event Table No Both No Both No Real Time CAPI Connection Name Override Retrieve PWX Log Entries No Real Time No Both 104 Chapter 4: PWXPC . See “Configuring Real-Time Flush Latency” on page 117. see the PowerExchange Oracle Adapter Guide. Overrides the connection value in the ORACLEID statement in the PowerExchange configuration file (dbmover.cfg).. Overrides the schema name for a group of registrations. For more information. See “Configuring the CAPI Connection Name Override” on page 113 Include all related PowerExchange log entries in the session log. Specifies the number of change records (not UOWs) after which a commit should be inserted into the change stream. Default is 0. PWXPC sets values between 0 and 2000 to 2000.cfg).Table 4-11.Configuring Connections . Default is no. Convert embedded nulls in character fields to spaces. For more information. See “Converting Character Data to Strings” on page 108. see the PowerExchange Oracle Adapter Guide. Oracle CDC Mode Application Connection Attributes Connection Attribute Real-time Flush Latency Required No Change or Real-time Real Time Description Specifies the milliseconds between buffer flushes.

Password for the user name. See “Configuring Encryption and Compression” on page 106. Select the code page for the Integration Service to use to extract data from the source database.cfg. Select the write mode. Specifies whether. Default is Confirm Write On. No Sybase Batch Mode Relational Connections 105 . Name of the Sybase instance. See “Configuring Encryption and Compression” on page 106.Sybase Batch Mode Relational Connections Configure relational database connections for Sybase to extract data and load data in batch mode to Oracle sources and targets. Name of the database in the Sybase instance. Table 4-12 describes the connection attributes you configure for Sybase relational database connections: Table 4-12. See “Configuring Pacing” on page 107. See “Configuring Encryption and Compression” on page 106. Sybase Batch Mode Relational Connection Attributes Connection Attribute Name Code Page Required Yes Yes Description Name of the relational database connection. User name for the database being connected to. pacing size is in number of rows. Select the encryption type. Default is no. Note: In Unicode mode. PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. Select to compress source data during the PowerCenter session. See “Converting Character Data to Strings” on page 108. Enter the pacing size. Location Server Name Database Name User Name Password Environment SQL Compression Encryption Type Encryption Level Pacing Size Interpret as Rows Convert character data to string Write Mode Yes Yes Yes Yes Yes No No No No No No No Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover. Select the encryption level. SQL commands run in the database environment. or not. Convert embedded nulls in character fields to spaces. See “Configuring Write Mode” on page 109. See “Configuring Pacing” on page 107.

Configuring Encryption and Compression When you configure connections to extract and load data from PowerExchange. 106 Chapter 4: PWXPC .Configuring Connections . Some of the connection attributes that you can choose are: ♦ Common connection attributes: − − − Encryption and compression Pacing Convert character data to string Write Mode Retrieve PWX log entries Image type Event Table CAPI Connection Name Idle time CDC Restart UOW Count Real-time Flush Latency Commit Threshold ♦ Batch application and relational connection attributes: − − ♦ CDC-specific connection attributes: − − − − − − − − Common Connection Attributes The attributes discussed in this section are common to both the PWXPC relational and application connection types. you can set encryption and compression values to encrypt and compress data during the PowerCenter session. This is not the complete list of all attributes that can be configured. See the PowerExchange Reference Manual for additional information.Configuring Connections Attributes The connection attributes you configure depend on how you want to run the PowerCenter session to extract data from the source. The complete list of attributes for all connections is documented in preceding sections of this chapter under the various connection types.

Default is 1. 64 bit key encryption. If you select RC2 or DES for Encrypt. Pacing Size Connection Attributes Connection Attribute Pacing Size Required No Description Enter the amount of data the source system can pass to the PowerExchange Listener. Table 4-14 describes the pacing attributes: Table 4-14. Enter 0 for maximum performance. 64 bit key encryption. For more information about pacing size. Configuring Connections Attributes 107 . If you clear this option. Configure the pacing size if an external application.RC2 . This option is selected by default. Triple DES 164 bit key encryption For RC2. the pacing size represents kilobytes. The pacing size determines the amount of data the PowerExchange Listener passes to the source or target. For RC2. Configuring Pacing You can configure the pacing size to slow the data transfer rate from the PowerExchange Listener. database.None . then PowerExchange ignores this value.Table 4-13 describes the compression and encryption attributes: Table 4-13. see the PowerExchange Reference Manual. enter one of the following values for the encryption level: 1 = 56-bit key encryption. Triple DES 164 bit key encryption. Interpret as Rows No Select to represent the pacing size in number of rows. Minimum value is 0. Default is 0. The lower the value.DES Default is None. 3 = For DES. or the Integration Service node is a bottleneck during the session. Encryption Level Yes If you select None for Encryption Type. Select one of the following values for the encryption type: . Encryption and Compression Connection Attributes Connection Attribute Compression Encryption Type Required No Yes Description Select to compress source data during the PowerCenter session. the faster the session performance. 2 = For DES.

specifically a null or low value (x’00’). As a result. So. Default is to leave embedded nulls as-is. the result be only the string ABC. a character field contains the following hexadecimal EBCDIC data: C1C2C300C4C5C6C700C8C9 The application that processes this field uses the x’00’ as a delimiter and parses the field into three strings: ♦ ♦ ♦ x’C1C2C3’ (ABC) x’C4C5C6C7’ (DEFG) x’C8C9’ (HI) If this field is read from PowerExchange by PowerCenter. If selected. Batch Application and Relational Connection Attributes These attributes are available in both PWXPC batch application and relational connection types unless otherwise noted. it is truncated when the first null indicator (x’00’) is detected. the entire contents of the field cannot be extracted and then manipulated in PowerCenter. there is no explicit mapping of the sub-field other than in the application reading the data. embedded null indicators (x’00’) are converted to spaces (x’40’). When this data is extracted by PowerCenter.Configuring Connections . For example. Nulls (x’00’) are used as delimiters between the sub-field values. Convert Character Data Connection Attribute Connection Attribute Convert character data to string Required No Description Select to convert embedded nulls in character fields to spaces. However. the example above would result in the field containing the following hexadecimal EBCDIC data: C1C2C340C4C5C6C740C8C9 which when read by PowerCenter results in string ‘ABC DEFG HI’. Table 4-15 describes the Convert character data to string attribute: Table 4-15. 108 Chapter 4: PWXPC . This connection attributes exists to allow these types of fields to be extracted. The rest of the field would be truncated when the first null indicator is detected in the data.Converting Character Data to Strings Some data fields that are mapped as character fields actually contain non-character data in the field. This usually occurs when a single field is usually a collection of sub-fields.

Write Mode Connection Attribute Connection Attribute Write Mode Required No Description . specify a value larger than 0 in the Session Error handling option “Stop on errors” on the Config Object tab. PWX DB2400. Note: The PowerCenter statistics are unreliable when using Confirm Write Off.Asynchronous with Fault Tolerance sends data to the PowerExchange Listener asynchronously similar to Confirm Write Off but with the ability to detect errors. Confirm Write On ensures that data is sent synchronously to the PowerExchange Listener (rather than buffered). This provides the speed of Confirm Write Off with the data integrity of Confirm Write On. only use this option when the target table can be reloaded if an error occurs. PWX DB2UDB and PWX Oracle relational connections. This is important if good error recovery is a priority. As a result. . Default is Confirm Write On. 3. See the PowerExchange Reference Manual for further information. While faster than Confirm Write On. the sender then waits for the response from PowerExchange before the next SQL request is sent.Confirm Write On sends data to the PowerExchange Listener and waits for a success/no success response before sending more data. Configuring Connections Attributes 109 . .Configuring Write Mode Table 4-16 describes the Write Mode attributes: Table 4-16. it removes the ability to determine exactly which SQL statement failed in error situations. Confirm Write Off sends data asynchronously to the PowerExchange Listener by buffering the data. Reject File No Overrides the default prefix of PWXR for the reject file. PowerExchange creates the reject file on the target machine when the Write Mode is Asynchronous with Fault Tolerance. After a SQL request is sent. There are three possible settings for Write Mode: 1. This is important if good error recovery is a priority. Use this setting only when loading tables. 2. Confirm Write On Confirm Write Off Asynchronous with Fault Tolerance Asynchronous with Fault Tolerance is only available for PWX DB2390. It has the drawback of slowing data transfer rates. In order to stop session execution when errors are encountered. you must reload the entire table if an error occurs to ensure data integrity. While this method provides greater speed compared to Confirm Write On. NOTE: Specifying PWXDISABLE will prevent creation of the reject files.Confirm Write Off sends data to the PowerExchange Listener without waiting for a success/no success response (asynchronously). It has the drawback of slowing data transfer rates.

Default is no PowerExchange messages in the session log. specify a value larger than 0 in the Session Error handling option “Stop on errors” on the Config Object tab. be sure to review the following information: ♦ ♦ ♦ ♦ ♦ “CDC-Specific Connection Attributes” on page 110 “Extracting CDC Data in Change and Real-time Modes” on page 133 “Understanding PWXPC Restart and Recovery” on page 149 “Enabling Session Recovery” on page 163 “Configuring CDC Sessions” on page 164 110 Chapter 4: PWXPC . The PowerExchange messages related to the session are returned in the session log as a part of message PWXPC_10091. Data is buffered and sent asynchronously to the PowerExchange Listener.Asynchronous (write) with Fault Tolerance combines the speed of Confirm Write Off with error detection of Confirm Write One. Retrieve PWX Log Entries Connection Attribute Connection Attribute Retrieve PWX Log Entries Required No Description Include all related PowerExchange log entries in the session log. In order to properly configure CDC sessions. speeding diagnosis when errors occur.Configuring Connections . Table 4-17 describes the Retrieve PWX Log Entries attribute: Table 4-17. A reject file is created on the target machine when SQL errors occur allowing any errors to be corrected without reloading the entire table. This allows a single log to provide a view of both PowerCenter and PowerExchange processing. In order to stop session execution when errors are encountered. CDC-Specific Connection Attributes The attributes discussed in this section are specific to the PWXPC CDC application connection types. Retrieving PowerExchange log entries will include into the PowerCenter session log messages related to the session that are normally found only in the PowerExchange log. You can also specify how to handle specific SQL return codes. Retrieving PWX Log Entries This attribute is specific to the PWXPC application connection types. See the PowerExchange Reference Manual for a complete description of Asynchronous Write with Fault Tolerance.

it is possible to do an update to the primary key (thereby changing the key value). When you use embedded before-image columns. In order to request that the before-image of the column be embedded into the update row. Default is BA.Configuring Image Type Table 4-18 describes the Image Type attribute: Table 4-18. You can configure whether before-image data is extracted for update operations using the Image Type specification. See the appropriate PowerExchange Adapter Guide for the source type for additional information the change Condense process. Including the before-image data for key columns will allow this type of activity to be detected. One possible use for embedded before-image data is to handle update records where the primary key has been updated. In some circumstances this may causes problems when attempting to apply this update to the target database as some relational databases does not allow primary key values to be updated. you should specify AI for Image Type. the before-image and after-image data of the entire row that was updated are presented as two separate rows: a delete with the before-image data and an insert with the after-image data. In change mode. The before-image data can always be extracted in real-time mode. With AI processing. you must alter the PowerExchange extraction map. This will create before-image columns (DTL__BI_columnname) within the extraction map for those columns selected. In the PowerExchange Navigator. Configuring Connections Attributes 111 . Image Type Connection Attribute Connection Attribute Image Type Required No Description Select one of the following types: AI = Extract after images only. regardless of source type. When this form of before-image data is used. select the columns for which you would like before-image data. then only after-image data is provided for update records (unless you explicitly request before-image data). In some relational databases (such as DB2/390). selectively by column. it is possible that only after-image data is available if the changes have been specifically condensed with only after-images. BA = Extract before and after images. to request that before-image column data be embedded within the after-image update record. PowerExchange captures before and after image data for all updates. This allows the before-image data to be easily manipulated in your mapping as it is contained in the same update record as the after-image data. It is possible. the change remains an update (as opposed to being changed into a delete/insert pair). updates are passed as update records and not changed to a delete/insert pair as occurs in BA processing.If you specify Image Type=BA. The RDBMS understands that this operation is equivalent to deleting the row and then re-adding it with a new primary key. If you specify Image Type=AI. The Flexible Key Custom Transformation will allow this to be properly handled at the target. This activity is logged as an update and so will be passed as an update record when extracted.

it places an end-of-file (EOF) in the change stream. Using an event table. then the event table must be a DB2 table in the same DB2 subsystem as the DB2 changes. When PowerExchange processes the change for the event table. For additional information about configuring before-image columns. For example. To use event table processing.Configuring Connections . it will stop reading changes at that point and shutdown the extraction. 4. 2. 3. 5. passes it along to the Integration Service and shuts down the reader. For more information on the Flexible Key Custom Transformations. Event Table Connection Attribute Connection Attribute Event Table Required No Change Real Time Real Time Description Specifies the PowerExchange extraction map name used for event table processing. For example. PWXPC processes the EOF. The event table must be the same source type and on the same machine as the CDC data being extracted. Configuring Event Table Processing Table 4-19 describes the Event Table attribute: Table 4-19. you can stop real-time CDC sessions based on an external event. 112 Chapter 4: PWXPC . When PowerExchange reads the change to the event table. Register the event table for CDC. you want to stop a CDC extraction every night after all of the day’s changes have been processed. make a change to the event table. complete the following tasks: 1. You can use an event table to do this by making a change to that table at midnight. Specify the extraction map name for the event table in the connection Event Table attribute for the CDC sessions you wish to stop based on an event. When the event occurs. you must configure before-image columns in the PowerExchange extraction map. 6. see the PowerExchange Adapter Guide for the source type. if you are extracting DB2 changes from MVS. see “Flexible Key Custom Transformation” on page 175.Note: To use the Flexible Key Custom Transformation. The Integration Service completes writing all of the data currently in the pipeline and ends the session.

You can specify the default CAPI_CONNECTION statement by coding the CAPI_SRC_DFLT statement in the PowerExchange configuration file. Configuring Idle Time Idle Time is only applicable to Real Time connections. Default is -1.Configuring the CAPI Connection Name Override Table 4-20 describes the CAPI Connection Name Override attribute: Table 4-20. You use multiple CAPI_CONNECTION statements to capture changes from more than one database type through a single PowerExchange Listener on a single machine. 0 = EOF is returned at the end of log. Table 4-21 describes the Idle Time attribute: Table 4-21. the session terminates successfully. the session ends. You request other CAPI_CONNECTION statements by specifying the CAPI Connection Name Override attribute. If you enter: -1 = EOF is never retuned. you can capture changes for Oracle and UDB using a single PowerExchange Listener using multiple CAPI_CONNECTION statements. Use the Idle Time session condition to indicate whether the real-time session should run continuously (forever) or shutdown after a specified period of time. Idle Time Connection Attribute Connection Attribute Idle Time Required No Change Real-time Real Time Description Specifies the number of seconds the PowerExchange Listener remains idle after reaching the end of the change log (as indicated by message PWX-09967) before returning an end-of-file (EOF). Configuring Connections Attributes 113 . PowerExchange allows a maximum of eight CAPI_CONNECTION statements in the PowerExchange DBMOVER configuration file. See the PowerExchange Reference Manual for additional information about CAPI_CONNECTION statements. n = EOF is returned after no data for n seconds. This parameter requires a valid value and has a valid default value. the session runs continuously. CAPI Connection Override Connection Attribute Connection Attribute CAPI Connection Name Override Required No Change Real Time Real Time Description Overrides the default CAPI connection name. For example.

The Idle Time timing starts when the PowerExchange Listener begins reading changed data for the source(s). If -1 is entered for Idle Time, PowerExchange will never return an end-of-file (EOF) to the Integration Server thereby causing the session to run forever. This is generally how a real-time session is setup. It is the default value primed for Idle Time in all of the real-time connections. Continuous extraction sessions must be stopped using either the PowerExchange STOPTASK command or through PowerCenter using Workflow Monitor Stop/Abort or the pmcmd commands to stop and abort tasks and workflows.

If you stop the session or workflow using the PowerCenter Workflow Monitor or using pmcmd, this is considered a normal termination. PowerCenter will perform a graceful stop, instructing the CDC reader and the writers to shutdown and waiting until all data currently in the pipeline is processed. For more information about stopping real-time sessions and workflows, see the PowerCenterWorkflow Administration Guide. If you abort the session or workflow using the PowerCenter Workflow Monitor or using pmcmd, this is considered an abnormal termination since PowerCenter does not wait for the reader and writer to shutdown or until all data in the pipeline is processed. For more information about aborting sessions and workflows, see the PowerCenterWorkflow Administration Guide. The PowerExchange STOPTASK command will stop the extraction task in the PowerExchange Listener and pass an EOF to the Integration Server which will terminate the session successfully. For more information on the PowerExchange STOPTASK command, see the Task Utility (DTLUTSK) documented in the PowerExchange Utilities manual.

Warning: Ensure that you have switched the Session Properties “Commit Type” attribute to Source and unchecked the “Commit at End of File” attribute. By default, “Commit at End of File” is on and it will cause data to be committed after the CDC reader has shutdown and committed the restart tokens. As a result, when the session is restarted, duplicate data will be sent to the target.

If 0 is entered for Idle Time, PowerExchange will return an EOF to the Integration Service when the end-of-log (EOL) is reached. After the EOF is received, the Integration Service will terminate the session successfully, meaning that all data will be committed and the restart token file will be updated. The end-of-log is determined by what was the current end of the change stream at the point that PowerExchange started to read the change stream. This concept of EOL is required because the change stream is generally not static so the actual “end-of ’-log” is continually moving forward. PowerExchange issues the following message when EOL is reached:
PWX-09967 CAPI i/f: End of log for time <yy/mm/dd> <hh:mm:ss> reached

For example, if a session starts reading a change stream at 10:00 a.m., the EOL at that point is determined. After PowerExchange reaches that point in the change stream, it will return EOF to the Integration Service. This means that changes recorded in the change stream after 10:00 a.m. will not be processed. Specifying 0 for Idle time is a useful in situations where you want to extract changed data for sources periodically as opposed to continuously.
114 Chapter 4: PWXPC - Configuring Connections

If a positive number is specified for Idle Time, then the session will run until no data is returned for the period of time specified. After Idle Time is reached, PowerExchange will send an end-of-file (EOF) to the Integration Service and the session will terminate successfully. Specifying a low Idle Time (1 for example) can result in this time being reached before all available data in the change stream has been read. The following message is issued to indicate that the Idle Time has been reached:
[PWXPC_10072] [INFO] [CDCDispatcher] session ended after waiting for [idle_time] seconds. Idle Time limit is reached

This message is also issued when a continuous extraction is stopped using the PowerExchange STOPTASK command. In this case, the idle_time variable in the message will show 86400 which is the “never expire” time limit used when an Idle Time of -1 is specified.
Tip: In highly active systems, a positive value for Idle Time may never match. Use 0 if you do

not want the session to run continuously. For example, if you specify an Idle Time of 10 seconds and PowerExchange finds no data for the source(s) in the change stream for a 10 second period, PowerExchange will return an EOF to the Integration Service which will cause it to terminate successfully. If you specify values for Reader Time Limit and Idle Time, the Integration Service stops reading data from the source at the point based on whichever one of these session conditions is reached first. So, if the Reader Time Limit is reached prior to the Idle Time limit, the session will stop at that point regardless of the fact that Idle Time has not yet been reached.
Warning: Reader Time Limit does not result in normal termination of a CDC session. Use Idle Time instead of Reader Time Limit.

Configuring CDC Restart Attributes
Table 4-22 describes the restart attributes you must configure for CDC sessions:
Table 4-22. Change and Real-time Mode Restart Connection Attributes
Connection Attribute Application Name Required No Description Application name for the extraction. It is part of the audit trail for data extractions by the PowerExchange Listener. The name must be unique for each session. The application name is case sensitive and cannot exceed 20 characters. Default is the first 20 characters of the workflow name.

Configuring Connections Attributes

115

Table 4-22. Change and Real-time Mode Restart Connection Attributes
Connection Attribute RestartToken File Folder Required No Description Folder name that contains the restart token override file on the Integration Service node. Default is $PMRootDir/Restart. RestartToken File Name No File name in the Restart Token File Folder that contains the restart token override file. PWXPC uses the contents of this file, if any, in conjunction with the state information to determine the restart point for the session. Default is the Application Name if specified or the workflow name if Application Name is not specified.

All of these parameters require a valid value and all have valid default values. There are numerous CDC reader application connection attributes that specify restart information. PWXPC uses the restart information to tell PowerExchange from which point to start reading the captured changed data.
Warning: Care must be taken when using the Application Name default as it may not result in a unique name for the application name. It is imperative that the Application Name value and the Restart Token File Name be unique for every session. Results are unpredictable and include session failures and potential data loss if a non-unique name is used for either of these attributes.

For more information about restart token files, see “Configuring the Restart Token File” on page 160.

Configuring UOW Count
Table 4-23describes the UOW Count attribute:
Table 4-23. UOW Count Connection Attribute
Connection Attribute UOW Count Required No Change Real-time Both Description Specifies the number of units of work (UOWs) you want the PWXPC to read from the source before flushing data to the target. If you enter: -1 = UOW count is not used 0 = UOW count is not used n = n is the count of UOWs Default is 1.

A unit of work (UOW) is a collection of changes within a single commit scope made by a transaction on the source system. Each unit of work may consist of a different number of changes. This parameter requires a valid value and has a valid default value.

116

Chapter 4: PWXPC - Configuring Connections

When the session runs, the PWXPC reader begins to read data from the PowerExchange Listener. After data is provided to the source qualifier, the UOW Count begins. When you use a non-zero value for the UOW Count session attribute, PWXPC issues a commit to the target when it reaches the number of units of work specified in this session condition. When the UOW Count is reached, a real-time flush will be triggered to flush the buffers so that the changed data is committed to the target. The following message appears in the session log to indicate that this has occurred:
[PWXPC_10081] [INFO] [CDCDispatcher] raising real-time flush with restart tokens [restart1_token], [restart2_token] because UOW Count [uow_count] is reached

The commit to the target when reading CDC data is not strictly controlled by the UOW Count specification. The Real-Time Flush Latency and the Commit Threshold values also determine the commit frequency. To understand the affect that all of these values have on commit processing, see “Understanding Commit Processing with PWXPC” on page 121. For example, if the value for UOW Count is 10, the Integration Service commits all data read from the source to its target after the 10th unit of work is processed (assuming the Real-Time Flush Latency period has not expired first). The lower you set the value, the faster the Integration Service commits data to the target. Therefore, if you require the lowest possible latency for the apply of changes to the target, you should specify a UOW Count of 1.
Warning: When you specify a low UOW Count value, the session might consume more system resources on the target platform. This is because it will commit to the target more frequently. You need to balance performance and resource consumption with latency requirements when choosing the UOW Count and Real-Time Flush Latency values.

Configuring Real-Time Flush Latency
Table 4-24 describes the Real-Time Flush Latency attribute:
Table 4-24. Real-Time Flush Latency Connection Attribute
Connection Attribute Real-time Flush Latency in milliseconds Required No Change Real-time Real Time Description Value in milliseconds between buffer flushes. If you enter: 0 to 2000 = PWXPC sets the value to 2000 n = The value specified for n is used if larger than 2000 Valid values are between 0 and 86400000 milliseconds. Default is 0 (2000 milliseconds/2 seconds).

Use the Real-time Flush Latency session condition to control the target commit latency when running in real-time mode. PWXPC commits source data to the target at the end of the specified maximum latency period. This parameter requires a valid value and has a valid default value.

Configuring Connections Attributes

117

When the session runs, PWXPC begins to read data from the source. After data is provided to the source qualifier, the Real-Time Flush Latency interval begins. At the end of each RealTime Flush Latency interval and an end-UOW boundary is reached, PWXPC issues a commit to the target. The following message appears in the session log to indicate that this has occurred:
[PWXPC_10082] [INFO] [CDCDispatcher] raising real-time flush with restart tokens [restart1_token], [restart2_token] because Real-time Flush Latency [RTF_millisecs] occurred

Only complete UOWs are committed during real-time flush processing. The commit to the target when reading CDC data is not strictly controlled by the Real-Time Flush Latency specification. The UOW Count and the Commit Threshold values also determine the commit frequency. To understand the affect that all of these values have on commit processing, see “Understanding Commit Processing with PWXPC” on page 121. The value specified for Real-Time Flush Latency also controls the PowerExchange Consumer API (CAPI) interface timeout value (PowerExchange latency) on the source platform. The CAPI interface timeout value is displayed in the following PowerExchange message on the source platform (and in the session log if “Retrieve PWX Log Entries” is specified in the Connection Attributes):
PWX-09957 CAPI i/f: Read times out after <n> seconds

The CAPI interface timeout also affects latency as it will affect how quickly changes are returned to the PWXPC reader by PowerExchange. PowerExchange will ensure that it returns control back to PWXPC at least once every CAPI interface timeout period. This allows the PWXPC to regain control and, if necessary, perform the real-time flush of data returned. A high RTF Latency specification will also impact the speed with which stop requests from PowerCenter are handled as the PWXPC CDC Reader must wait for PowerExchange to return control before it can handle the stop request.
Tip: Use the PowerExchange STOPTASK command to shutdown more quickly when using a

high RTF Latency value. For example, if the value for Real-Time Flush Latency is 10 seconds, PWXPC will issue a commit for all data read after 10 seconds have elapsed and the next end-UOW boundary is received. The lower you set the value, the faster the data commits data to the target. Therefore, if you require the lowest possible latency for the apply of changes to the target, you should specify a low Real-Time Flush Latency value.
Warning: When you specify a low Real-Time Flush Latency interval, the session might consume more system resources on the source and target platforms. This is because:
♦ ♦

The session will commit to the target more frequently therefore consuming more target resources. PowerExchange will return more frequently to the PWXPC reader thereby passing fewer rows on each iteration and consuming more resources on the source PowerExchange platform.

You need to balance performance and resource consumption with latency requirements when choosing the UOW Count and Real-Time Flush Latency values.

118

Chapter 4: PWXPC - Configuring Connections

Commit Threshold Connection Attribute Connection Attribute Commit Threshold Required No Change Real-time Real Time Description Enter the number of change records to process before a commit is inserted into the change stream. Default is 0. This parameter requires a valid value and has a valid default value Commit Threshold can be used to cause a commit before the end of a UOW is received. The value specified in the Commit Threshold is the number of records within a source UOW to process before inserting a commit into the change stream. The target commit is still controlled by the UOW Count and Real-time Flush Latency specification. where applicable. Commit Threshold is only applicable to Real-Time CDC sessions. a process also referred to as sub-packet commit. This may then result in target commit failures. Using Commit Threshold can cause commits to be generated at points in the change stream where the relationship between these tables is inconsistent. The Commit Threshold count is cumulative across all sources in the group. Use the Commit Threshold session condition to cause commits before reaching the end of the UOW when processing large UOWs. see the PowerExchange Reference Manual. If you set the Commit Threshold to 1000. For more information on this PowerExchange parameter. Configuring Connections Attributes 119 . The Commit Threshold counter is reset when either the number of records specified or the end of the UOW is reached. commits will occur on UOW boundaries only. Otherwise. the commit record is inserted after the 1000th change record which is after the 100 changes for the second source. the value specified is used to insert commit records into the change stream between UOW boundaries. If 0 or no value is specified.Configuring Commit Threshold Table 4-25 describes the Commit Threshold attribute: Table 4-25. This means that sub-packet commits are inserted into the change stream when the count specified is reached regardless of the number of sources to which the changes actually apply. a UOW contains 900 changes for one source followed by 100 changes for a second source and then 500 changes for the first source. This attribute is different from the UOW Count attribute in that it is a count records within a UOW rather than complete UOWs. The value of this attribute overrides the value specified in the PowerExchange DBMOVER configuration file parameter SUBCOMMIT_THRESHOLD. Warning: A UOW may contain changes for multiple source tables. For example. This attribute is useful when there are extremely large UOWs in the change stream that might cause locking issues on the target database or resource issues on the PowerCenter Integration Server. Note: This parameter puts a commit record into the change stream after the specified number of records.

Configuring Connections . see “Understanding Commit Processing with PWXPC” on page 121. then a commit record will be inserted after each 100 records and a target commit will be issued after every 500 records. The UOW Count and the RealTime Flush Latency values determine the target commit frequency. The commit records inserted into the change stream as a result of the Commit Threshold value affect the UOW Count counter. and deletes).The commit to the target when reading CDC data is not strictly controlled by the Commit Threshold specification. To understand the affect that all of these values have on commit processing.000 change records (any combination of inserts. For example. a UOW contains 1. updates. If you specify 100 for Commit Threshold and 5 for UOW Count. 120 Chapter 4: PWXPC .

If the Commit Type in the Session Properties is set to Target. it commits data to the target and continues to read data from the source. Commit Threshold Real-Time Flush Latency UOW Count Note: When using PWXPC CDC Change connections. At which point. A final commit is also done by PWXPC during reader termination to ensure that all buffered and complete UOWs are committed. see the PowerCenterWorkflow Administration Guide. Warning: Duplicate data on targets can occur if the Commit On End Of File option in the Session Properties is enabled. This will ensure that the only PWXPC issues commits thereby keeping the target data and restart tokens in-sync. PowerExchange Understanding Commit Processing with PWXPC 121 . Commits inserted into the change stream as a result of the Commit Threshold specification are counted in the UOW Count counter.When the commit is issued both the Real-Time Flush (RTF) Latency period and the UOW Count counter are reset. the only connection attribute that affects commit processing is UOW Count. Idle Time can impact the commit process by causing the real-time session to terminate. Only UOW Count and Real-Time Flush Latency will cause that to happen. to commit data after a specified number of records within a single UOW. whichever occurs first. There are three connection attributes which affect commit processing when running real-time CDC sessions: 1. If the Idle Time is then reached. like all real-time readers. For example. you set the Idle Time value to 10 seconds and the UOW Count to five units of work.Understanding Commit Processing with PWXPC The PowerExchange Client for PowerCenter (PWXPC). Target based commit is switched to source based commit and target based commit interval is used as source based commit interval. Integration Service will automatically change it to source when the session is run. always uses source-based commit. PWXPC continues to read data from the source until either the RTF Latency period matches or the UOW Count matches. Source-based commit sessions have partitioning restrictions. 2. then PWXPC issues commits to the target when it reaches the UOW Count or when the Real-Time Flush Latency period expires. When the PWXPC reaches the UOW Count. all source-based commits with PWXPC are done on end-UOW boundaries. If you specify values for UOW Count and Real-Time Flush Latency. Commit Threshold itself does not result in PWXPC issuing a commit to the target. change the Commit Type to Source and then disable the Commit On End Of File option in the Session Properties. that is. To prevent this. For more information. With the exception of Commit Threshold. it issues another commit. The following message is issued in the session log to indicate that this has been done: WRT_8226 Target Load Order Group [1] is set for real-time flushing. 3. Commit Threshold exists to provide sub-packet commit capability. This processing continues until the session terminates.

Configuring Connections .000 The PWXPC reader receives 900 complete UOWs in five seconds after the first change row enters the source qualifier. The PWXPC CDC Reader must wait for PowerExchange to return control before it can handle the stop request. Commits will always be done on a UOW boundary based (except when Commit Threshold is specified) on whichever attribute matches first. assume the following settings: ♦ ♦ ♦ ♦ Idle Time is -1 (“never timeout”) Commit Threshold is 0 (no sub-packet commit) RTF Latency is 5000 (5 seconds) UOW Count is 1.stops reading from the source and sends an EOF to the Integration Service which terminates the session. The value necessary to do this is customer-dependent. The next 1. Again. Because the RTF Latency value has matched. Since the RTF Latency will only commit on a UOW boundary and a UOW Count of 1 causes a commit after each complete UOW is received. Tip: Use the PowerExchange STOPTASK command to shutdown more quickly when using a high RTF Latency value. To illustrate the interaction of all of the values affecting commit processing. in this example. then ensure that Real-Time Flush Latency is set sufficiently high so as not to be a factor. high values for RTF Latency will impact the speed with which stop requests from PowerCenter are handled. commits were issued after the first 900 UOWs because RTF Latency matched first and then again after the 1. It is therefore possible to have both the Real-Time Flush Latency period and the UOW Count control commits of the data.000 UOW is read. More changed data is read and commits continue based on whichever attributes matches first. So. these will be committed when the session terminates due to the final commit done by PWXPC.000 UOWs because the UOW Count matched. a source-based commit is issued at this point. Both the UOW Count and RTF Latency period are then reset. If only 3 complete UOWs have been read since the previous UOW count-based commit. a commit is issued after these 1.000 UOWs are read in 4 seconds. So. use an RTF Latency of 2000 (the default) and a UOW Count of 1. the RTF Latency period and the UOW Count are reset at this point. The RTF Latency specification controls: ♦ ♦ the commit latency for the target table(s) the PowerExchange Consumer API (CAPI) interface timeout value (PowerExchange latency) on the source platform. another commit will not be issued when the 1. This will cause a commit at each commit point in the source data. If you want to use less resources on the target system and want only UOW Count to control the commit process. For the lowest latency in getting changed data to the target. The size of the 122 Chapter 4: PWXPC . the effect is to have only UOW Count control the commit process. So.900th UOW because the UOW Count then matched first. this is the most-resource intensive setting from the target DBMS perspective. Of course. In addition to impacting the target latency.

Understanding Commit Processing with PWXPC 123 .UOWs and the speed at which they are read will affect what value represents a high enough RTF Latency period to eliminate it as a factor.

124 Chapter 4: PWXPC .Configuring Connections .

127 Extracting CDC Data in Change and Real-time Modes. 140 125 .Working with Sessions and Workflows This chapter includes the following topics: ♦ ♦ ♦ ♦ Overview. 133 Loading Data to Relational Targets.Chapter 5 PWXPC . 126 Extracting Data in Batch Mode.

You can create a session in a workflow to extract data in batch. see the PowerCenter Workflow Administration Guide. and scheduling workflows. Pipeline Partitioning Pipeline partitioning cannot be used for sources in CDC sessions.Working with Sessions and Workflows . You create sessions and workflows in the Workflow Manager. and load data.Overview After you create mappings in the PowerCenter Designer. configuring. You can also create a session to load data to a target. 126 Chapter 5: PWXPC . transform. Real-time Session Rules and Guidelines For the list of limitations with real-time mode. you can create a session and use the session in a workflow to extract. see the PowerCenter Workflow Administration Guide. For more information about creating. change. You can use it for targets in CDC sessions. You determine how you want the Integration Service to extract the data when you configure the session. For more information about partitioning and a list of all partitioning restrictions. or real-time mode. see the “Real-time Processing” chapter of the PowerCenter Workflow Administration Guide.

See the PowerExchange Navigator User Guide for additional information about File List Processing. When you select this option. See “Session Properties for Non-Relational Batch Mode Sessions” on page 127. Constraint-Based Loading for Relational Targets In the Workflow Manager.Extracting Data in Batch Mode To extract data in batch mode. Click the Sources view on the Mapping tab. you must select a connection for batch mode and configure session properties. Configuring a batch mode session for non-relational sources: 1. you can specify constraint-based loading for a session. In the Task Developer. double-click a session with a non-relational source to open the session properties. You can also override a Sequential or VSAM ESDS source and request File List Processing by specifying the file list file name in the File List Name and ticking the Filelist File box in the session properties. The Reader names for non-relational batch sources have one of the following formats: PowerExchange Batch Reader for <database_type> Extracting Data in Batch Mode 127 . PWXPC and PowerExchange use this information to extract the source data. 3. the Integration Service orders the target load on a row-by-row basis. Extracting Data from Multiple Files You can extract data from multiple Sequential or VSAM ESDS files with the same record layout using the File List Processing feature of PowerExchange. PowerCenter Workflow Administration Guide. see: ♦ ♦ “Constraint-Based Loading for Relational Targets” on page 127. In the Reader field of the Readers settings. For every row generated by an active source. you can override data map information for the source. The connection you select and the session properties you configure differ depending on the type of source data. Session Properties for Non-Relational Batch Mode Sessions When you configure a session to extract data from a non-relational source in batch mode. The PowerExchange Listener extracts data from the files listed in the file list file. then to any foreign key tables. 2. Use a file list file to provide the names of the files from which you want to extract source data. the PowerExchange Batch Reader for the specific source type will be shown. the Integration Service loads the corresponding transformed row first to the primary key table. For more information.

In the Connection Value field.Batch VSAM Reader 4. 128 Chapter 5: PWXPC .PowerExchange Reader for <database_type> The <database_type> is the one of the following: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ADABAS ADABAS Unload Files DB2 Datamaps DB2 Unload Datasets DATACOM IDMS IMS Sequential Files VSAM Files The name of the reader cannot be altered.Working with Sessions and Workflows . For example. Session Mapping Tab . Click the Sources view on the Mapping tab. select the application connection from the available PWX NRDB Batch connections. 5. a VSAM source looks as follows: Figure 5-1. The only exception to this is Adabas where you can choose between ADABAS and ADABAS Unload Files.

Extracting Data in Batch Mode 129 . Specifies the file name of the unloaded Adabas database.. Overrides the unload file name in PowerExchange data map.6. Enter a filter override using the following syntax: <filter condition1>. Overrides the Adabas file id in the PowerExchange data map. ADABAS Unload DB2 Datamaps DB2 Datamaps DB2 Unload Datasets All Description Overrides the source PowerExchange data map schema name.. Required for ADABAS Unload. Overrides the source PowerExchange data map name. or <group name1>=<filter condition1>. Use the <group name> syntax to limit the application of the filter to a specific record. In the Properties settings. Overrides the ADABAS Database Id in the PowerExchange data map.. Overrides the DB2 Table name in PowerExchange data map.. ADABAS Unload ADABAS. IMS Unload File Name IMS IMS database unload file name. you can select only records with ID column values that contain DBA for a multi-record source with two records called USER1 and USER by specifying either: USER1=ID=’DBA’. Password for the ADABAS database.USER2=ID=’DBA’ or ID=’DBA’ See “Filtering Source Data using PWXPC” on page 224. configure the following attributes (all fields are optional except where noted): Attribute Name Schema Name Override Map Name Override File Name ADABAS Password Database Id Override File Id Override DB2 Sub System Id DB2 Table name Unload File Name Filter Overrides Source Type All All ADABAS Unload ADABAS ADABAS. If you do not specify <group name> and the source mapping is a multi-record source.. Overrides the DB2 instance name in the PowerExchange data map. then the filter condition applies to all records in the source mapping.<filter condition2>.. Allows data to be filtered at the source by PowerExchange. For example.<group name2>=<filter condition2>. Required if you want to read source data from the backup file instead of the IMS database.

3. 130 Chapter 5: PWXPC . Session properties unique for PowerExchange are noted. Overrides the SQL query sent to PowerExchange. In the Reader field of the Readers settings. select a PWXPC relational database connection. SQL Query Override All For information about other session properties. 7. enter the filelist file name in the File Name Override. Only select this option if you have entered a filelist file for File Name Override. For the AS400. you can also select PowerExchange Reader for DB2 Image Copy. 2. including any Filter Overrides. If you selected the Filelist File check box.Working with Sessions and Workflows . Configuring a relational source batch mode session: 1.Attribute Name File Name Override Source Type VSAM. SEQ Select if the File Name Override field contains the data set name of a list of files. Enter enter the complete data set or file name. this name should be: library_name/file_name. see the PowerCenter Workflow Administration Guide. Click the Sources view on the Mapping tab. double-click a session with a relational source to open the session properties. Session Properties for Relational Batch Mode Sessions To extract data from a relational source in batch mode. SEQ Description Overrides the data set or file name in the PowerExchange data map. Click OK. Filelist File VSAM. You can then configure the session properties. For DB2 on z/OS. select Relational Reader. In the Task Developer.

Overrides the source table name. It cannot be used for DB2 sources on other platforms. In the Connection Value field.DB2 Readers Note: The PowerExchange Reader for DB2 Image Copy is only applicable to DB2 for z/OS sources. the available readers for a DB2 source looks as follows: Figure 5-2. and Windows PWX Oracle for Oracle PWX MSSQLServer for SQL Server PWX Sybase for Sybase 5. Session Mapping Tab . Extracting Data in Batch Mode 131 . Select the appropriate PWX relational database connection if using the relational reader: ♦ ♦ ♦ ♦ ♦ ♦ PWX DB2390 for DB2 for z/OS PWX DB2400 for DB2 for i5/OS PWX DB2UDB for DB2 for Linux.For example. You can configure the following attributes for the PowerExchange Reader for DB2 Image Copy: Attribute Name Schema Name Override Map Name Override Description Overrides the source schema name. select PWX NRDB Batch application connection if using the DB2 Image Copy reader. UNIX. 4.

132 Chapter 5: PWXPC .<filter condition2>. Provides the image copy data set name. see the PowerCenter Workflow Administration Guide. Click OK.Attribute Name DB2 Sub System Id Image Copy Dataset Disable Consistency Checking Filter Overrides Description Overrides the DB2 instance name in the PowerExchange data map..Working with Sessions and Workflows . If not specified. Enter a filter override using the following syntax: <filter condition1>. Overrides the unload file name in PowerExchange data map. the most current image copy data set is used. 6. For information about other session properties.. Allows data to be filtered at the source by PowerExchange. including any filter overrides. For example. SQL Query Override Overrides the SQL query sent to PowerExchange. you can select only records with ID column values that contain DBA by specifying: ID=’DBA’ See “Filtering Source Data using PWXPC” on page 224..

Import CDC sources using the CDC Datamaps option to minimize the customization required both in Designer and Workflow Manager. To extract data in real-time mode (CAPXRT).x can still select either Batch or CDC readers and application connections. Note: For compatibility purposes. In order to properly configure CDC sessions. extraction maps are the only choice if you want to use a CDC reader. you select a real-time mode application connection. Extraction maps are created by the PowerExchange Navigator when the source is initially registered for Change Data Capture. sources with Database Type of PWX_source_NRDB2). Non-relational source definitions imported in PowerCenter 8. review the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ “CDC-Specific Connection Attributes” on page 110 “Understanding Commit Processing with PWXPC” on page 121 “Extracting CDC Data in Change and Real-time Modes” on page 133 “Understanding PWXPC Restart and Recovery” on page 149 “Configuring the Restart Token File” on page 160 “Enabling Session Recovery” on page 163 “Configuring CDC Sessions” on page 164 PowerExchange Extraction Maps The metadata that is used for sessions with Change Data Capture (CDC) sources is taken from the PowerExchange extraction maps. It is no longer possible to select a CDC reader with sources created from PowerExchange data maps in PowerCenter V8. non-relational source definitions imported in PowerCenter 7. you select a change mode application connection.x automatically have the appropriate Batch Reader selected for the source type.Extracting CDC Data in Change and Real-time Modes To extract change capture data in change mode (CAPX). When importing source definitions with PowerCenter Designer.x or later.x (that is. Extracting CDC Data in Change and Real-time Modes 133 . Note: With non-relational sources imported in PowerCenter V8.x using the “Import from PowerExchange” dialog box with the CDC Datamap option ticked do not require the specification of the extraction map name. Source definitions created from extraction maps contain the extraction map schema and map name in the Metadata Extensions. These can be manually modified at a later date. This eliminates the need to specify the extraction map name in the session properties. Source definitions created in PowerCenter V8. This reader selection cannot be changed. You can also create new extraction maps using an existing capture registration. Source definitions created from relational database metadata require that you specify the extraction map name in the Session Properties if you want to use a CDC reader and application connection. you can specify the CDC Datamaps option (requesting extraction maps) in the Import from PowerExchange dialog box.

With changed data. all sources must use the same application connection. updates. you must create a PowerExchange capture registration for every table in the data map. Sessions with mappings that include sources with multiple data types will fail when executed. Constraint-Based Loading for Relational Targets In the Workflow Manager. As a result. For every row generated by an active source. All other transformations can be used. data is applied to the targets in the same order in which it was applied to the sources. This creates an extraction map for each table. Joiner. only applies to insert operations. see the PowerCenter Workflow Administration Guide.Working with Sessions and Workflows . Custom (configured as active). see the PowerCenter Workflow Administration Guide. then your mapping must not contain active transformations which change the Row Id generated by the CDC Readers. In order to obtain complete constraint-based loading. and Sorter Transformations. Constraint based load ordering. Normalizer. If you are using full constraint-based loading. For more information about constraint-based loading. Rank. and deletes. You need only specify the application connection on the first source in the mapping. the Integration Service orders the target load on a row-by-row basis. The constraint-based loading session attribute. 134 Chapter 5: PWXPC . you must also set Custom Property FullCBLOSupport=Yes. The transformations that change the Row Id are: Aggregator. This causes changed data to be loaded to targets in the same Transaction Control Unit (TCU) using the Row Id assigned to the data by the CDC Reader. you can specify constraint-based loading for a session. The Custom Property can be set in the session Config Object tab in the Custom Properties attribute. This property can also be set in the Integration Service making it applicable to all workflows and sessions that use that Integration Service. Extracting CDC Data from Multiple Sources in a Session If the mapping contains multiple sources from which you want to extract CDC data in change mode or real-time mode. Note: All of the sources must be the same source data type. You can then either import the data map as a multi-record non-relational source (for batch usage) or import the extraction maps for each table (for CDC usage). there will usually be a mixture of inserts. See Knowledge Base Article #18015 for information about how to set Custom Properties in the Integration Service. All other connections can have a Type of None. the Integration Service loads the corresponding transformed row first to the primary key table. For additional real-time mode limitations.If you want to extract change data from a multi-record non-relational source using extraction maps. The following message will be issued in the session log to indicate that this support is enabled: WRT_8417 Complete Constraint-Based Load Ordering is enabled. When you select this option. then to any foreign key tables.

Source definitions for CDC sources can be created using extraction maps (CDC Datamaps in the Import dialog box) or by importing metadata from the relational database. Configuring a change or real-time mode sessions (extraction map sources): 1. Click the Properties tab and change the following: ♦ ♦ Commit Type field to Source Commit on End of File . change the Recovery Strategy attribute to Resume from last checkpoint. the reader is automatically chosen based on the source type Extracting CDC Data in Change and Real-time Modes 135 . PWXPC uses the extraction map to extract the source data. see “PWXPC . you will have to choose the desired CDC Reader (see page 137). For more information. 2. The session properties will differ based upon how the source metadata was imported. For relational sources. In the Task Developer.remove the tick to turn this off Figure 5-3.Session Properties for Change and Real-Time Mode Sessions When you configure a session to extract data in change or real-time mode. 3. Click the Sources view on the Mapping tab. With extraction map sources. double-click the session to edit it.Restart and Recovery” on page 147. Session Properties Tab To enable recovery for the session. Enabling recovery for CDC sessions is important to ensure that data and restart tokens are properly handled.

Extraction Map Source In the Connection Value field. 136 Chapter 5: PWXPC . In the Session Properties settings.Working with Sessions and Workflows . Session Mapping Tab . In this example. the extraction map used in the mapping is for a DB2/390 source so the PowerExchange CDC Reader for DB2/390 is chosen: Figure 5-4. 5. Overrides the source PowerExchange extraction map name. select CDC Real Time or CDC Change application connection types. Overrides the ADABAS Database Id in the PowerExchange data map.Configuring Connections” on page 77. Overrides the Adabas file id in the PowerExchange data map. 4. See “PWXPC . Optionally.of the extraction map. PWXPC displays the valid connections for the source type in the Application Connection Browser. configure the following optional attributes: Attribute Name Schema Name Override Map Name Override Database Id Override File Id Override Source Type All All ADABAS ADABAS Description Overrides the source PowerExchange extraction map schema name. open the application connection to override any connection values.

Allows data to be filtered at the source by PowerExchange. change the Recovery Strategy attribute to Resume from last checkpoint. Enter a filter override using the following syntax: <filter condition1>. For example. Extracting CDC Data in Change and Real-time Modes 137 . Enabling recovery for CDC sessions is important to ensure that data and restart tokens are properly handled.Restart and Recovery” on page 147. Source Schema Override Filter Overrides Oracle Overrides the source schema name. Specify complete library and file names in the format: library/file This attribute overrides the Library/File Override value on the application connection. 2. In the Task Developer. Click the Properties tab and change the following: ♦ ♦ Commit Type field to Source Commit on End of File .<filter condition2>. you can ask PowerExchange to filter change records so that only ones where columns ID and ACCOUNT have changed are passed by specifying: DTL__CI_ID=‘Y’. including any Filter Overrides. Warning: Do not specify an asterisk for library name if using PWXPC restart. To enable recovery for the session.Attribute Name Library/File Override Source Type DB2400 Description Overrides the library and file name in the extraction map. For more information. Configuring a change or real-time mode session (relational sources): 1.remove the tick to turn this off See Figure 5-3 on page 135 for an example of the Properties tab. double-click the session to edit it. SQL Query Override Overrides the SQL query sent to PowerExchange. For information about other properties settings. see the PowerCenter Workflow Administration Guide..DTL__CI_ACCOUNT=’Y’ See “Filtering Source Data using PWXPC” on page 224.. see “PWXPC ..

PowerExchange group source processing only uses the information on the first application connection. For subsequent CDC sources. 5.Working with Sessions and Workflows . DB2390: PowerExchange CDC Change or PowerExchange CDC Real Time DB2400: PowerExchange CDC Change or PowerExchange CDC Real Time DB2UDB: PowerExchange Real Time Oracle: PowerExchange CDC Change or PowerExchange CDC Real Time MSSQL: PowerExchange Real Time In the Connection Value field. select an application connection.Relational Source In the Reader field of the Readers settings. Subsequent application connection specifications are not required and may cause session failures. open the application connection to override any connection values. See “PWXPC . select a CDC Reader from those available based on the source type: ♦ ♦ ♦ ♦ ♦ 4.Configuring Connections” on page 77. Tip: For CDC Change and Real Time Readers. 138 Chapter 5: PWXPC . Optionally. choose a Connection Type of None. Figure 5-5.3. Session Mapping Tab . Click the Sources view on the Mapping tab. only choose an application connection for the first CDC source.

see the PowerCenter Workflow Administration Guide. All fields are optional except where noted: Attribute Name Extraction Map Name Source Type All Description The PowerExchange extraction map name for the CDC source. Library/File Override DB2400 Real Time For information about other properties settings. configure the following attributes.6. Click OK. In the Properties settings. 7. Overrides the library and file name in the extraction map. Warning: Do not specify an asterisk for library name if using PWXPC restart. Extracting CDC Data in Change and Real-time Modes 139 . You must specify the extraction map name for the relational source. Specify complete library and file names in the format: library/file This attribute overrides the Library/File Override value on the application connection. Required if using a CDC Change or Real Time Reader. Source Schema Override Oracle Change and Real Time Overrides the source schema name.

you can use a PWX NRDB Batch application connection to write to it. 3. See Table 1-2 on page 3 for the list of relational and non-relational targets for which PowerExchange provides write support. Configuring sessions to load data to relational targets: 1. select relational writer to run sessions with relational targets. 140 Chapter 5: PWXPC .Working with Sessions and Workflows . If the table has been imported into PowerExchange as a sequential data map. In the Task Developer. You can then configure properties for session as you would any other relational target. select a relational database connection. Note: DB2 for i5/OS (DB2/400) tables can also be accessed as flat files. In the writers setting. Loading Data to Relational Targets To load data to a relational target. Click the Targets view on the Mapping tab. 2.Loading Data to PowerExchange Targets You can load data to relational targets as well as to non-relational targets. double-click the session to edit it.

For information about properties settings. Loading Data to PowerExchange Targets 141 . and Windows PWX Oracle for Oracle PWX MSSQLServer for SQL Server PWX Sybase for Sybase 5.Relational Targets 4. In the Connections Value field. select a relational database connection from one of the following types: ♦ ♦ ♦ ♦ ♦ ♦ PWX DB2390 for DB2 for z/OS PWX DB2400 for DB2 for i5/OS PWX DB2UDB for DB2 for Linux. see the PowerCenter Workflow Administration Guide. UNIX. Click OK. Configure any other session properties. 6. Session Mapping Tab .The following example shows a DB2/390 target: Figure 5-6.

double-click the session to edit it.Working with Sessions and Workflows . UNIX. You must select a PWX NRDB Batch application connection. The writer value is set based on the target type. Linux. including flat files on AS/400.Loading Data to Non-Relational Targets PWXPC allows you to load data to the following non-relational targets: ♦ ♦ ♦ ♦ Adabas IMS Sequential. and Windows VSAM The writer is set to the correct PowerExchange Writer based on the target type. 142 Chapter 5: PWXPC . 2. You can then configure properties for session as you would any other target. Click the Targets view on the Mapping tab. In the Task Developer. Configuring sessions to load data to non-relational targets: 1.

In the Connections Value field. 5.The following example shows a sequential target: Figure 5-7. For information about other Properties settings. 6.Non-Relational Targets 3. Loading Data to PowerExchange Targets 143 . select a PWX NRDB Batch application connection. see the PowerCenter Workflow Administration Guide. Click OK. Session Mapping Tab . 4. configure the PWXPC session properties. Configure any other session properties. See Table 5-1 on page 144. In the Properties settings.

CYLINDER . MVS Secondary space allocations. VSAM Description Adabas file password. VU.TRACK Default is TRACK. The following table contains the optional Session Properties for all PWXPC non-relational targets. in alphabetical order: Table 5-1. FB.Session Properties for Non-Relational Targets PowerExchange and PWXPC support a variety of non-relational targets. SMS management class name. FBA. IMS. MVS data set block size. V. VB. Default is 1. Default is 0 (best possible block size). Overrides the default Insert SQL sent to PowerExchange. For the AS400. VSAM All SEQ (MVS only) All SEQ (MVS only) SEQ (MVS only) All All SEQ (MVS only) SEQ (MVS only) All SEQ (MVS only) SEQ (MVS only) Processes updates and deletes as inserts. IMS. Overrides the target PowerExchange data map schema name. MVS data set space units. MVS Record format. Default is 256. MVS Primary space allocation. this name should be: library_name/file_name. Enter enter the complete data set or file name. Overrides the data set or file name in the PowerExchange data map. in the units specified in Space. MVS Data set disposition.Working with Sessions and Workflows . See Table 1-2 on page 3 for the complete list. in the units specified in Space. Overrides default Delete SQL sent to PowerExchange. Values are: . VBA. 144 Chapter 5: PWXPC . MVS data set logical record length. Overrides the target PowerExchange data map name. SQL statement(s) executed before the session is run using the target database connection. Insert Only Insert SQL Override LRECL Map Name Override MGMTCLAS MODELDSCB Post SQL Pre SQL Primary Space RECFM Schema Name Override Secondary Space Space ADABAS. Default is 1. MVS SMS data class name. Session Properties for Non-Relational Targets Attribute Name ADABAS Password BLKSIZE DATACLAS Delete SQL Override Disp File Name Override Source Type ADABAS SEQ (MVS only) SEQ (MVS only) ADABAS. FU. MVS Model DSCB for non-SMS-managed GDG data sets. Values are: F. SQL statement(s) executed after the session is run using the target database connection. VSAM SEQ (MVS only) SEQ.

VSAM ADABAS. Processes failed inserts as updates and updates as inserts. SEQ (MVS only) ADABAS. MVS volume serial number. IMS. Session Properties for Non-Relational Targets Attribute Name STORCLAS Truncate Table Option UNIT Update SQL Override Upsert VOLSER Source Type SEQ (MVS only) IMS. MVS unit type. Default is SYSDA.Table 5-1. Overrides the default Update SQL that is sent to PowerExchange. Truncates table (deletes contents) before loading new data. VSAM Description SMS storage class name. Note: VSAM data sets must be defined with the REUSE option for truncate to function correctly. IMS. VSAM SEQ (MVS only) Loading Data to PowerExchange Targets 145 .

Working with Sessions and Workflows .146 Chapter 5: PWXPC .

160 PWXPC Restart and Recovery Operation.Chapter 6 PWXPC . 149 Creating Recovery Tables. 148 Understanding PWXPC Restart and Recovery. 158 Configuring the Restart Token File.Restart and Recovery This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ Overview. 163 147 .

Using the commit interval information specified in the CDC session connection.Overview This chapter describes PWXPC restart and recovery processing as well as how to configure your CDC sessions to use this processing. also referred to as restart tokens. Target recovery and restart information is stored as the target tables and files are updated by the Integration Service. PWXPC manages the CDC restart information. In order to properly configure CDC sessions. PWXPC provides restart information for the CDC sources to PowerExchange. PWXPC periodically flushes complete UOWs to the Integration Service. A unit of work (UOW) is a collection of changes within a single commit scope made by a transaction on the source system.Restart and Recovery . The Integration Service provides recovery for the target files and tables in CDC sessions. PowerExchange reads the change stream on the CDC source platform and provides complete units of work to PWXPC. In order to extract change data from the change stream. review “PWXPC Restart and Recovery Operation” on page 163. Each source in a CDC session has unique restart information. 148 Chapter 6: PWXPC . review the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ “CDC-Specific Connection Attributes” on page 110 “Understanding Commit Processing with PWXPC” on page 121 “Extracting CDC Data in Change and Real-time Modes” on page 133 “Understanding PWXPC Restart and Recovery” on page 149 “Configuring the Restart Token File” on page 160 “Enabling Session Recovery” on page 163 “Configuring CDC Sessions” on page 164 In order to manage CDC sessions. The Integration Service and PWXPC use this information to recover and restart stopped or failed sessions from the point of interruption.

Data loss or duplication may occur. PWXPC issues the following message indicating that recovery is in effect: PWXPC_12094 [INFO] [CDCRestart] Advanced GMD recovery in affect. This table contains information the Integration Service uses to identify each target on the database. If you manually create this table. it restores the state of operation to recover the session from the point of interruption. This table contains target load information for the session run. For relational targets. Understanding PWXPC Restart and Recovery 149 ♦ . When the Integration Service performs recovery.Understanding PWXPC Restart and Recovery Session Recovery PowerCenter and PWXPC restart and recovery functionality are utilized when you configure the Recovery Strategy Resume from the last checkpoint. the Integration Service creates the following recovery tables in the target database: ♦ PM_RECOVERY. It uses the target recovery data to determine how to recover the target tables. Warning: Do not enable recovery processing if any of the targets in the CDC session use the File Writer to write CDC data to flat files. The restart tokens for all targets in the session. including relational targets. PM_TGT_RUN_ID. also called restart tokens. the Integration Service provides recovery for the target tables and files and PWXPC provides recovery for the CDC restart information. The information remains in the table between session runs. originates from PowerExchange on the CDC source platform. $PMStorageDir. $PMStorageDir. will be compromised if there is a flat file target in the same session. in state files on the Integration Service platform. The Integration Service removes the information from this table after each successful session and initializes the information at the beginning of subsequent sessions. CDC restart information. PWXPC and PowerExchange use the CDC restart information to determine the correct point in the change stream from which to restart the extraction. PWXPC stores the CDC restart information in the shared location. you must create a row and enter a value other than zero for LAST_TGT_RUN_ID to ensure that the session recovers successfully. PWXPC stores the CDC restart information in state tables in the target database. Recovery Tables For relational targets. The Integration Service saves relational target recovery in the target database. When you enable a resume recovery strategy. PWXPC stores CDC restart information in different locations based upon the target type: ♦ ♦ For non-relational targets. Enabling a resume recovery strategy ensures that both the target data and CDC restart information can be recovered in the event of session failure. Recovery is automatic The Integration Service stores the session state of operation in the shared location.

PM_REC_STATE. This table contains restart information for CDC sessions. The restart information recorded in the table contains the application name and restart tokens for the session. The restart information remains in the table permanently. The Integration Service updates it with each commit to the target tables.

If you edit or drop the recovery tables before you recover a session, the Integration Service cannot recover the session. If you disable recovery, the Integration Service does not remove the recovery tables from the target database. You must manually remove the recovery tables. If you want the Integration Service to create the recovery tables, grant table creation privilege to the database user name for the target database connection. For the database user name used with PowerExchange relational targets, see “Recovery Table Creation with PowerExchange Targets” on page 158. If you do not want the Integration Service to create the recovery tables, create the recovery tables manually.
Tip: If you are using PowerExchange relational target connections, manually create these

tables so you can assign the desired database attributes. See “Creating the Recovery Tables Manually” on page 159. For more information about the PM_RECOVERY and PM_TGT_RUN_ID tables, see the PowerCenterWorkflow Administration Guide.

Recovery State Table
The recovery state table contains the state and CDC restart information for a CDC session. The table resides in the same target database as target tables. The Integration Service creates the state table automatically if it does not exist. See “Creating Recovery Tables” on page 158. The Integration Service creates an entry in the state table for each CDC session. These entries may comprise more than one row. CDC sessions with heterogeneous relational target tables have entries in the state table in each unique target database. For example, a CDC session which targets Oracle and UDB tables has an entry in the state table in the target Oracle database and in the target UDB database. Each session entry in the state table contains a number of repository identifiers as well as execution state data like the checkpoint number and the CDC restart information. The columns in the state table are:
♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦

OWNER_TYPE_ID - PowerCenter-defined identifier REP_GID - Global unique identifier of the repository FOLDER_ID - Folder identifier WFLOW_ID - Workflow identifier to which the session belongs WLET_ID - Worklet identifier TASK_INST_ID - Session (task) instance identifier WID_INST_ID - Reader widget instance identifier GROUP_ID - Partition group Identifier

150

Chapter 6: PWXPC - Restart and Recovery

♦ ♦ ♦ ♦ ♦ ♦ ♦

PART_ID - Partition identifier PLUGIN_ID - Application connection plug-in subtype identifier APPL_ID - Application name from the source application connection SEQ_NUM - Entry sequence number VERSION - Session version number CHKPT_NUM - Session checkpoint number STATE_DATA - Restart state data for the session The APPL_ID column contains the application name specified in the source application connection. The STATE_DATA column, which contains the restart tokens for the session, is a variable 1024 byte binary column. If the number of restart tokens for a session causes the data to exceed 1024 in length, additional rows are added to accommodate the remainder of the restart information. The SEQ_NUM field is increased by one, starting from zero, for each additional row added for a session entry.

The following columns contain PWXPC-specific restart information:
♦ ♦

The majority of the columns in the table are task and workflow repository attributes. These repository attributes remain static unless the task or workflow is altered. The following examples are actions that alter these repository attributes:
♦ ♦ ♦

adding or removing sources or targets from the mapping used by the session moving the workflow or session to a different folder moving the session to a different workflow

See “Changing CDC Sessions” on page 169 for additional information. During session initialization, the Integration Service reads the state table looking for an entry that matches the session data. All column data (with the exception of VERSION, CHKPT_NUM, and STATE_DATA) must match the task and workflow repository attributes for the Integration Service to use an entry. If a match is found, the Integration Service uses that entry for target recovery processing. PWXPC uses the CDC restart information stored in the STATE_DATA column to perform restart and recovery processing.

Recovery State File
The recovery state file is similar to the state table. PWXPC uses the state file to store the CDC restart information for non-relational target files. Non-relational target files include MQ Series message queues, PowerExchange non-relational targets, and other PowerCenter non-relational targets. The Integration Service automatically creates the recovery state file in the shared location, $PMStorageDir, if it does not exist. The file name for the recovery state file is prefixed with:
pm_rec_state_<application_name>

The Integration Service uses the application name from the source CDC connection for the application name value in the state file name prefix. The Integration Service includes the complete file name in message CMN_65003. The remainder of the fields in the file name are
Understanding PWXPC Restart and Recovery 151

task and workflow repository attributes. These repository attributes remain static unless the task or workflow is altered. The following examples are actions that alter these repository attributes:
♦ ♦ ♦

adding or removing sources or targets from the mapping used by the session moving the workflow or session to a different folder moving the session to a different workflow

See “Changing CDC Sessions” on page 169 for additional information.

The Restart Token File
PWXPC stores the restart tokens in the state table in the target database for relational targets and in the state file on the Integration Service platform for non-relational targets. The restart token file provides:
♦ ♦

initial restart tokens for new CDC sessions overrides for the restart tokens in the state table or file for existing CDC sessions

PWXPC uses the restart token file in the folder specified in the RestartToken File Folder attribute of the source CDC connection. PWXPC automatically creates this folder, if it does not exist, when the attribute contains the default value of $PMRootDir/Restart. PWXPC does not automatically create any other restart token folder name. During session initialization, PWXPC:
♦ ♦

uses the name specified in the RestartToken File Name attribute to create an empty restart token file, if one does not already exist. creates a merged view of the restart tokens by reconciling the restart tokens specified in the restart token file with those in state tables and the state file for all relational and nonrelations targets, respectively. For more information on the reconciliation process, see “Determining the Restart Point” on page 153.

places the results of the restart token reconciliation process into an initialization file in the restart token file directory and empties out the restart token file. Emptying the restart token file ensures that it does not override the state table or state file restart tokens with the same restart information the next time the session is run.

During normal termination, PWXPC writes the ending restart tokens into a termination file in the restart token file directory. The restart token files containing the initialization and termination restart tokens have the following names:
<restart_token_file_name>yyyymmddhhmmss_init <restart_token_file_name>yyyymmddhhmmss_term

where:
♦ ♦ ♦ 152

restart_token_file_name is the restart token file name from the CDC connection yyyymmddhhmmss is the initialization file creation timestamp init or term is for initialization and termination files, respectively

Chapter 6: PWXPC - Restart and Recovery

For example, a CDC source application connection specifies a restart token file name of my.app.txt, which does not exist. PWXPC creates the following files on the Integration Service platform in the restart token file folder specified in the connection:
♦ ♦ ♦

my.app.txt my.app.txtyyyymmddhhmmss_init my.app.txtyyyymmddhhmmss_term

The restart token file, my.app.txt, is empty. The timestamps on both the initialization and termination files are the same to indicate that they are related to the same run. The termination file may not exist or may be empty if the session fails. If you are using the default value of zero for the connection attribute Number of Runs to Keep RestartToken File, PWXPC keeps only one copy of the paired initialization and termination files. Otherwise, PWXPC uses the value specified in that attribute to determine the number of backup copies of these paired files to keep. During termination, PWXPC removes any additional pairs of the backup files beyond the Number of Runs to Keep RestartToken File value.

Determining the Restart Point
Start CDC sessions in one of the following ways:

Cold start. When you cold start a CDC session, PWXPC reads only the restart token file to acquire restart tokens for all sources and makes no attempt to recover the session. The session continues to run until stopped or interrupted. Warm Start. When you warm start a CDC session, PWXPC reconciles the restart tokens provided in the restart token file, if any, with any restart tokens that exist in the state file or state tables. If necessary, PWXPC performs recovery processing. The session continues to run until stopped or interrupted. Recover. When you recover a CDC session, PWXPC reads the restart tokens from the state file and state tables and writes them into the restart token file. If necessary, PWXPC performs recovery processing. After PWXPC finishes updating the restart token file and doing any necessary recovery, the session ends.

See “Starting CDC Sessions” on page 167 for more details. Each CDC source in the CDC session has its own unique restart point. You should create and populate the restart token file with restart points for each source prior to running a CDC session for the first time. If you do not provide restart tokens in the restart token file and no existing entry exists for the session in the state tables or the state file, then PWXPC passes null restart tokens to PowerExchange for all sources in the session. See “Default Restart Points” on page 155 for further information about null restart tokens. The restart tokens PWXPC uses varies based on whether you warm or cold start the CDC session and whether you provide any overriding restart tokens in the restart token file.

Understanding PWXPC Restart and Recovery

153

Cold Start Processing
Cold start workflows and sessions using the cold start command from Workflow Manager, Workflow Monitor, or pmcmd. PWXPC uses the restart tokens provided in the restart token file, disregarding the state file and state tables, as follows:

Restart Token file empty or does not exist. PWXPC assigns null restart tokens to all sources in the session. See “Default Restart Points” on page 155 for further information about null restart tokens. Restart token file contains explicit override statements. PWXPC assigns the restart tokens supplied in the restart token file to the specified sources. PWXPC assigns the oldest restart point of the restart tokens specified to all remaining sources. See “Configuring the Restart Token File” on page 160 for further information about explicit override statements. Restart token file contains special override statement. PWXPC assigns the restart tokens supplied in the restart token file to all sources. See “Configuring the Restart Token File” on page 160 for further information about the special override statement. Restart token file contains special override statement and explicit override statements. PWXPC assigns the restart tokens supplied in the restart token file in the explicit override statements to the specified sources. PWXPC assigns the restart tokens supplied in the special override statement to all remaining sources.

Warm Start Processing
Warm start workflows and sessions using the start or restart commands from Workflow Manager, Workflow Monitor, or pmcmd. PWXPC merges the restart tokens provided in the restart token file with any restart information that exists in the state file and the state tables as follows:

Restart token file empty or does not exist.

If no state file (non-relational target) or no entry in a state table (relational target) for the session: PWXPC assigns null restart tokens to all sources in the session. See “Default Restart Points” on page 155 for further information about null restart tokens.

If state file (non-relational target) or entry in a state table (relational target) exists for some but not all sources in the session: PWXPC assigns the restart tokens found in the state file or state tables to the appropriate sources. PWXPC assigns the oldest restart point of the restart tokens available to all remaining source without restart tokens.

If state file (non-relational target) or entry in a state table (relational target) exists for all sources in the session: PWXPC uses the restart tokens from the state file or state tables.

154

Chapter 6: PWXPC - Restart and Recovery

Restart token file contains explicit override statements.

If no state file (non-relational target) or no entry in a state table (relational target) for the session: PWXPC assigns the restart tokens supplied in the restart token file to the specified sources. PWXPC assigns the oldest restart point of the restart tokens specified in the restart token file to all remaining sources without restart tokens. See “Configuring the Restart Token File” on page 160 for further information about explicit override statements.

If state file (non-relational target) or entry in a state table (relational target) exists for some but not all sources in the session: PWXPC assigns the restart tokens supplied in the restart token file to the specified sources. PWXPC assigns the restart tokens found in the state file or state tables to the appropriate sources provided they have not been supplied in the restart token file. PWXPC assigns the oldest restart point of the restart tokens available to all remaining sources without restart tokens.

If state file (non-relational target) or entry in a state table (relational target) exists for all sources in the session: PWXPC assigns the restart tokens supplied in the restart token file to the specified sources in the session. PWXPC assigns the restart tokens from the state file or state tables to all remaining sources without restart tokens.

Restart token file contains special override statement. PWXPC assigns the restart tokens supplied in the special override statement in the restart token file to all sources. See “Configuring the Restart Token File” on page 160 for further information about the special override statement.

Restart token file contains special override statement and explicit override statements. PWXPC assigns the restart tokens supplied in the restart token file in the explicit override statements to the specified sources. PWXPC assigns the restart tokens supplied in the special override statement to all remaining sources without restart tokens.

Default Restart Points
If you start a new CDC session and no restart token file exists, the Integration Service still runs the session. Because no specific restart point has been provided, PWXPC passes null restart tokens for all sources to PowerExchange. PWXPC issues message PWXPC_12060 indicating that the restart tokens for each source are NULL. PowerExchange, because it receives null restart tokens from PWXPC, assigns the earliest possible restart point to each source.
Warning: Using null restart tokens may not produce the desired results. Valid restart tokens should always be supplied.

Start your extraction for a new CDC session at a point in the change stream where the source and its target are in a consistent state. You do this by placing the restart tokens that match that point in the change stream in the restart token file and doing a cold start of the CDC session.
Understanding PWXPC Restart and Recovery 155

PowerExchange extracts changes from the change stream from that restart point forward. After you have run DTLUAPPL. Oldest Condense file recorded in the CDCT. n/a n/a PowerExchange only uses the default starting extraction point if all sources have null restart tokens. PWXPC assigned the oldest restart point of the restart tokens available if there are some sources without restart tokens. and C. Default Starting Extraction Points for Sources Source Platform/ Database MVS (all sources) CDC Change Connection Oldest Condense file recorded in the CDCT. Now you need to establish a starting extraction. a target table has been materialized from its source data and no new changes have been made to the source data. AS400 Oracle MSSQL Server UDB Oldest Condense file recorded in the CDCT. This is the oldest restart point for which an archive log is available.For example.Restart and Recovery . The restart point for source A is older than source B. CDC Real Time Connection Logger selects the best available restart point. Most current Oracle catalog dump. PWXPC passes the restart tokens from the restart token file to PowerExchange. Table 6-1 describes earliest starting extraction (restart) points PowerExchange uses if null restart tokens are supplied for all sources: Table 6-1. Initializing and Running CDC Sessions After the restart information for every source is determined. PWXPC does not assign the default starting extraction point discussed in Table 6-1 to source C because some sources have restart points. When you run the session. a new CDC session contains three sources called A. You do this by using DTLUAPPL. Oldest data available in the Publication database. Current log position at the time the capture catalog was created. PWXPC assigns source C the same restart point as source A since it is the oldest supplied restart point. For example. point in the change stream. or restart. or active log if there are no available archive logs. PWXPC: ♦ ♦ Flushes the restart tokens to the state tables for relational targets and to the state file for non-relational targets Writes an empty restart token file 156 Chapter 6: PWXPC . place the generated restart tokens in the restart token file specified in the source CDC connection and cold start the CDC session. DTLUAPPL is a PowerExchange utility that generates restart points. The restart token file contains restart points for sources A and B. Source C has no existing or supplied restart point. Oldest journal receiver still on the journal receiver chain. B.

After the Integration Service writes the flushed data to any nonrelational targets. This prevents targets from being updated with records processed in previous extraction runs. Understanding PWXPC Restart and Recovery 157 . You should account for this in your CDC session design. This leaves only the last successfully committed UOW data and restart tokens in the relational target tables. PWXPC re-sends data which has already been applied to the non-relational targets. the Integration Service updates the targets and the state file in separate operations. Ending CDC Sessions Stop CDC sessions using PowerCenter and PowerExchange commands. PWXPC writes the termination restart token file with the final restart tokens and issues the following message: PWXPC_12075 [INFO] [CDCRestart] Session complete. With relational target tables in the same database. PowerExchange does not pass data for a source until its restart point is reached. On warm start. targets may receive duplicate data when restarted. When you stop a CDC session. If the session fails after the Integration Service commits data to the target but before it updates the restart tokens in the state file. including the restart tokens for relational targets. PWXPC continually updates the restart tokens for each source in the state table or the state file as it issues flushes target data. See “Stopping CDC Sessions” on page 168 for more information. The Integration Service does separate commits for each unique relational database. the Integration Service rolls back any uncommitted data and the related restart tokens for relational targets. As a result. duplicate data can occur on restart. The Integration Service does not do rollback processing for non-relational targets. Sessions can also fail or terminate unexpectedly. the state file and the targets likely exist on completely different machines.♦ Creates the initialization restart token file containing the reconciled restart information PWXPC passes the restart tokens for all sources to PowerExchange. PWXPC then waits for confirmation from the Integration Service that the flushed data has been written to the targets. With non-relational targets. The Integration Service uses relational database rollback capabilities to ensure that uncommitted data is removed during session termination. PWXPC flushes any complete units of work that remain in its buffer. the restart tokens in one relational database may differ from those in another relational database at specific points in time. then design your CDC sessions to use only relational targets. Consistency between the restart tokens and the relational target data is guaranteed because they are both committed within the same commit scope. Tip: If the possibility of duplicate data is unacceptable to your application. the Integration Service updates both the target tables and the restart tokens within a single commit. PowerExchange uses the oldest restart token passed by PWXPC to start extracting data from the change stream. As a result. If the session fails. If it has. With heterogeneous target. Next session will restart at: : Restart 1 [restart1] : Restart 2 [restart2] The Integration Service commits the flushed data to the targets. PWXPC uses the last restart tokens written prior to the failure. When using non-relational targets. it updates the state file with the restart tokens.

PWX DB2390 (DB2 for z/OS) Relational Connections When PowerExchange creates the recovery tables for PWX DB2390 connections. it uses: ♦ ♦ The default tablespace for user-defined tables The database user name in the target connection and so this user must be granted the appropriate table creation privilege PWX MSSQLServer (Microsoft SQL Server) Relational Connections When PowerExchange creates the recovery tables for PWX MSSQLServer connections. it uses the database user name in the target connection.Restart and Recovery . it uses: ♦ ♦ ♦ The default DB2 database (DSNDB04) The PowerExchange Listener userid if it is running with SECURITY=0 or SECURITY=1 and so this user must be granted the appropriate table creation privilege The PowerExchange Listener userid if it is running with SECURITY=2 and MVSDB2AF=CAF and so this user must be granted the appropriate table creation privilege The database user name in the target connection if the PowerExchange Listener is running with SECURITY=2 and MVSDB2AF=RRSAF and so this user must be granted the appropriate table creation privilege ♦ PWX DB2400 (DB2 for i5/OS) Relational Connections When PowerExchange creates the recovery tables for PWX DB2400 connections. This user must be granted the appropriate table creation privilege. 158 Chapter 6: PWXPC .Creating Recovery Tables Recovery Table Creation with PowerExchange Targets The database user name PowerExchange uses to create the recovery tables varies based on the PWXPC connection. it uses: ♦ ♦ The PowerExchange Listener userid if it is running with SECURITY=0 or SECURITY=1 and so this user must be granted the appropriate table creation privilege The database user name in the target connection is if the PowerExchange Listener is running with SECURITY=2 and so this user must be granted the appropriate table creation privilege The default journal so it must be enabled for the user name ♦ PWX DB2UDB (DB2 for Linux/UNIX/Windows) Relational Connections When PowerExchange creates the recovery tables for PWX DB2UDB connections.

PWX Oracle Relational Connections When PowerExchange creates the recovery tables for PWX Oracle connections. You can manually create the target recovery tables. Informatica provides SQL scripts in the following directory: <PowerCenter installation_dir>\server\bin\RecoverySQL Run one of the following scripts to create the recovery tables in the target database: Table 6-2.sql create_schema_ora.sql create_schema_inf. Creating the Recovery Tables Manually The Integration Service creates the recovery tables if they do not exist. This user must be granted the appropriate table creation privilege. PWX Sybase Relational Connections When PowerExchange creates the recovery tables for PWX Sybase connections. it uses the database user name in the target connection. consider manually creating the recovery tables so you can specify table attributes. PWX DB2400. Creating Recovery Tables 159 . See “Recovery Table Creation with PowerExchange Targets” on page 158 for more information.sql create_schema_syb. If using PWX DB2390. Make the appropriate changes for your environment. This user must be granted the appropriate table creation privilege. it uses the database user name in the target connection.sql create_schema_ter.sql create_schema_sql. Recovery Table SQL Scripts Script create_schema_db2.sql Database DB2 Informix Oracle SQL Server Sybase Teradata This is generic DDL. or PWX DB2UDB connections.

PWXPC includes the restart token file folder and the restart token file name in this message. The application connection contains the restart token file name and folder location. If the restart token file name is not specified in the application connection.comment text Use the comment statement anywhere in the restart token file. Comment lines begin with: <!-- ♦ Statements begin in any column. use one of the following options: ♦ ♦ Look at the PWXPC_12057 message in the session log. Using non-unique names causes unpredictable results including session failures and potential data loss.. ♦ Warning: The Restart Token File Name must be unique for every session. extraction_map_namen=restart1_token extraction_map_namen=restart2_token Restart Token File Statements The restart token file allows the following statements: Comment Statement <!-. PWXPC uses the workflow name. Syntax Rules The restart token file has these syntax rules: ♦ ♦ No blank lines between statements.Restart and Recovery .comment text RESTART1=restart1_token RESTART2=restart2_token extraction_map_name=restart1_token extraction_map_name=restart2_token .Configuring the Restart Token File You can configure the restart token file to specify the point from which you want to extract source data. if specified. PWXPC uses the application name. If you do not know the restart token file name and location. The “<!--” is required. Statement Syntax Format <!-. This file name overrides the file name you specified in the application connection. 160 Chapter 6: PWXPC . Otherwise.. Open the application connection associated with the source.

PWXPC_12060. PWXPC_12069) Restart= value in the DTLUAPPL PRINT output DTL__CAPXRESTART2 value when extracting data Logger token in PowerExchange messages (e.g. If used. Sources can have multiple extraction mappings and therefore multiple extraction map names. Check the Schema Name and Map Name values in the source Metadata Extensions in Designer if using CDC datamap sources.. Each source specification must be a pair of lines with: ♦ ♦ The source extraction map name (extraction_map_name) specified with the restart1_token value The source extraction map name (extraction_map_name) specified with the restart2_token The extraction map name specified in the restart token file must match what is defined in the CDC session. Configuring the Restart Token File 161 . PWX-09959) Restart Token 2 in PWXPC messages (e. PWXPC_12060. See Figure 5-4 on page 136. Sequence= value. PWX-04564.Explicit Override Statement extraction_map_name=restart1_token extraction_map_name=restart2_token The explicit override statement specifies restart tokens for a specific source. See “Default Restart Points” on page 155 for an explanation of what restart tokens PWXPC and PowerExchange use in this case. See Figure 3-23 on page 58. To determine the extraction map name: ♦ ♦ Check the Extraction Map Name attribute in the Session Properties for relational sources Check the Schema Name Override and Map Name Override attributes in the Session Properties if using CDC datamap sources. PWX-04564. The source is defined by specifying the extraction map name. The restart token values (restart1_token and restart2_token) are described in detail in the Explicit Override Statement. both RESTART1= and RESTART2= must be specified. in the DTLUAPPL PRINT output DTL__CAPXRESTART1 value when extracting data Sequence token in PowerExchange messages (e.g.. These attributes override the source name in the CDC datamap source. then the session executes without error.g.g. PWXPC_12069) ♦ The restart1_token value varies based on capture source and is found in the following: ♦ ♦ ♦ ♦ The restart2_token value varies based on the capture source and is found in the following: ♦ ♦ ♦ ♦ If the session includes source extraction maps that do not have entries in the existing restart token file. PWX-09959) Restart Token 1 in PWXPC messages (e. minus the trailing 8 zeros. Special Override Statement RESTART1=restart1_token RESTART2=restart2_token The special override statement allows specifies for all sources in a session.

rrtb0006_RRTB_SRC_006 000000AD775600000000000000AD77560000000000000000 d1dsn7. the session contains 7 source tables.This override can be used in conjunction with explicit override statements to provide restart tokens for sources which do not have explicit override statements.rrtb0001_RRTB_SRC_001=C1E4E2D340400000013FF36200000000 <!-.rrtb0004_RRTB_SRC_004=000006D84E7800000000000006D84E780000000000000000 d1dsn7.Restart Tokens for the Table: rrtb0001_RRTB_SRC_004 --> d1dsn7.Restart Tokens for the Table: rrtb0001_RRTB_SRC_002 --> d1dsn7.Restart Tokens for existing tables --> restart1=000000AD775600000000000000AD77560000000000000000 Restart2=C1E4E2D34040000000AD5F2C00000000 <!-.rrtb0003_RRTB_SRC_003 000000AD775600000000000000AD77560000000000000000 d1dsn7.Restart and Recovery . 162 Chapter 6: PWXPC .rrtb0005_RRTB_SRC_005 000000AD775600000000000000AD77560000000000000000 d1dsn7. RRTB_SRC_002. Restart Token File Example <!-.rrtb0002_RRTB_SRC_002=C1E4E2D34040000000968FC600000000 <!-. and RRTB_SRC_004.rrtb0001_RRTB_SRC_001 0000060D1DB2000000000000060D1DB20000000000000000 d1dsn7.rrtb0004_RRTB_SRC_004=C1E4E2D340400000060D1E6100000000 In the example. It also contains the special override statement to provide the restart tokens for the remainder of the sources in the session.rrtb0002_RRTB_SRC_002 000000A3719500000000000000A371950000000000000000 d1dsn7. An explicit override statement for a source takes precedence over the special override statement for that source. The restart token file contains explicit override statements for 3 sources: RRTB_SRC_001. PWXPC issues message PWXPC_12060 as follows: =============================== Session restart information: =============================== Extraction Map Name Restart Token 1 d1dsn7.Restart Tokens for the Table: rrtb0001_RRTB_SRC_001 --> d1dsn7. The sources to which PWXPC assigns the special override restart tokens have “special override” in parentheses. When the session executes.rrtb0002_RRTB_SRC_002=000000A3719500000000000000A371950000000000000000 d1dsn7.rrtb0004_RRTB_SRC_004 000006D84E7800000000000006D84E780000000000000000 d1dsn7.rrtb0001_RRTB_SRC_001=0000060D1DB2000000000000060D1DB20000000000000000 d1dsn7.rrtb0007_RRTB_SRC_007 000000AD775600000000000000AD77560000000000000000 Restart Token 2 C1E4E2D340400000013FF36200000000 C1E4E2D34040000000968FC600000000 C1E4E2D34040000000AD5F2C00000000 C1E4E2D340400000060D1E6100000000 C1E4E2D34040000000AD5F2C00000000 C1E4E2D34040000000AD5F2C00000000 C1E4E2D34040000000AD5F2C00000000 Source Restart Restart Restart Restart Restart Restart Restart file file file file file file file (special override) (special override) (special override) (special override) PWXPC displays the sources with explicit overrides with “Restart file” under the Source column.

determines how much of the source data it needs to reprocess. see “Understanding PWXPC Restart and Recovery” on page 149. Data written to the targets after PWXPC shuts down is not reflected in the restart tokens. For additional information about the Integration Service recovery processing. the Integration Service provides recovery for the target table data and PWXPC provides recovery for the CDC restart information. Change the Commit Type attribute from Target to Source. This is the only recovery strategy that enables PWXPC and the Integration Service to recover CDC sessions. PWXPC issues the following message when you specify a resume recovery strategy: PWXPC_12094 [INFO] [CDCRestart] Advanced GMD recovery in affect. which consists of restart tokens describing a specific start point in the change stream. are compromised if there is a flat file target in the same session. issues a commit when the session ends. When you enable a resume recovery strategy. PWXPC Restart and Recovery Operation 163 . after PWXPC has shutdown. When the Integration Service resumes a session. For nonrelational targets. The Integration Service. in conjunction with PWXPC. PowerExchange on the source platform provides the CDC restart information. See “Recovering from CDC Session Failures” on page 171. see the PowerCenterWorkflow Administration Guide. it restores the session state of operation.PWXPC Restart and Recovery Operation Enable a resume recovery strategy for CDC sessions. PWXPC stores the restart tokens for relational targets in recovery state tables in the target databases. 2. including relational targets. and transformation. Select “Resume from last checkpoint” for the Recovery Strategy in the Properties tab. Warning: If you are using the File Writer to write CDC data to flat files. do not edit the mapping or session’s the state table entry or file before you restart the session. do not enable recovery processing. Disable the Commit at End of File attribute in the Properties tab. CDC sessions always use source-based commit processing regardless of the Commit Type attribute setting. Data loss or duplication may occur since the restart tokens for all targets. Enabling Session Recovery Enabling recovery for a CDC session: 1. Disabling this flag ensures that PWXPC issues all commits. PWXPC stores the restart tokens in the recovery state file on the Integration Service machine. including the state of each source. For additional information about restart token processing. If you run a session with resume recovery strategy and the session fails. Recovery is automatic PWXPC automatically recovers warm started sessions when a resume recovery strategy is specified. target. The Integration Service. 3. Recovery is compromised if changes are made.

See “Application Names” on page 165. You cannot change Commit On End Of File unless you change Commit Type to Source. Commit On End Of File Properties Tab Disabled. The Integration Service performs a commit when the session ends. PWXPC is unaware that the writer has not applied the data to the target and so advances the restart tokens. Application Name Application Connection Unique name. Writer threshold errors can include key constraint violations. 164 Chapter 6: PWXPC . The following table summarizes the options and attributes with defaults that must be changed for CDC sessions: Table 6-3. The default value is 0. Errors encountered by the Integration Service while writing to the target database or target files are not counted by default. Specify a unique name. The Integration Service automatically overrides it to Source.The default may not result in a unique name. This commit occurs after PWXPC commits the restart tokens. Stop on errors Config Object Tab 1. The default value is Fail task and continue workflow. loading nulls into a not null field. CDC Sessions . The default is enabled. See the PowerCenter Workflow Administration Guide. Recovery Strategy Properties Tab Resume from last checkpoint. and database trigger responses. Duplicate data can occur on restart if this default is enabled. The default is the first 20 characters of the WorkFlow Name.Configuring CDC Sessions You control PWXPC restart processing with session options and attributes. PWXPC requires Resume from last checkpoint. Set this value to 1 to ensure target data and restart token integrity is maintained.Recommended Settings Option / Attribute Commit Type Location Properties Tab Recommended Value and Explanation Source. The default is Target. Ensure that all of the appropriate session configuration is done. See “Enabling Session Recovery” on page 163.Restart and Recovery .

regardless of whether the CDEP is being used to maintain restart tokens or not.the Application Name The default may not result in a unique name. With PWXPC the CDEP file is used for history only.Recommended Settings Option / Attribute Restart Token File Name Location Application Connection Recommended Value and Explanation Unique name. Using the same application name as a PWXPC CDC session in another CDC session. Specify a unique name. See “The Restart Token File” on page 152. Application names cannot be shared with other CDC sessions. stores the restart tokens in the PowerExchange CDEP file on the extraction platform. Each CDC session must use a unique application name in order to prevent failures due to conflicts in the CDEP. An application name is required when using PWXPC. The default is 0. CDC Sessions . Warning: Do not use a PWXPC CDC session application name when performing a Database Row Test in PowerExchange Navigator or when using the DTLUAPPL utility. PWXPC keeps only one backup copy of the restart token initialization and termination files. PWXPC Restart and Recovery Operation 165 . Number of Runs to Keep RestartToken File Application Connection Value greater than 0. when using ODBC connections. Specify a value greater than 0 so a history is available for recovery purposes. Update the restart token file with the generated restart tokens to establish the starting extraction point in the change stream.the WorkFlow Name if no Application Name is specified . for relational sources PowerExchange always stores extraction history information in the CDEP file for each application name. for non-relational sources The state table in the target database. Application Names PowerExchange. a Navigator row test. or in DTLUAPPL fails with message: PWX-04553 Error restart tokens [required | not allowed] for application "application name" Using DTLUAPPL with CDC Sessions Use the PowerExchange DTLUAPPL utility to generate restart tokens for CDC sessions instead of using the default restart point. PWXPC stores the restart tokens in: ♦ ♦ The state file on the Integration Service platform. See “The Restart Token File” on page 152.Table 6-3. The default is either: .

Tip: You can use same restart tokens for multiple source tables in the restart token file to start extracting changes from the same point in the change stream. You only need to run DTLUAPPL multiple times if you want to start extracting changes from different locations in the change stream for different sources.Restart and Recovery . Example: Using DTLUAPPL The registration on the ADD RSTTKN statement must exist. DTLUAPPL does generate the complete restart_token2 value in the Restart= token. You can use either ADD APPL or MOD APPL for a new application name. Using the tokens in this example.1> tag=<DB2DSN7db2demo11> Sequence=<000007248B9600000000000007248B9600000000> Restart =<D2D1D4D34040000007248B0E00000000> DTLUAPPL does not generate the complete restart1_token value which is shown in the SEQUENCE token. DTLUAPPL creates the application name if it does not exist when MOD APPL is used. see the PowerExchange Utilities Guide. the restart token file looks as follows: D1DSN7.Use a unique application name when generating restart tokens with DTLUAPPL so you avoid any conflicts with existing application names used for CDC sessions. You must be add the trailing four bytes (eight digits) of zeros manually when you update the restart token file.db2demo1=000007248B9600000000000007248B960000000000000000 D1DSN7. see “Configuring the Restart Token File” on page 160.db2demo1=D2D1D4D34040000007248B0E00000000 166 Chapter 6: PWXPC . You can copy this value to the restart token file. This registration must be associated with the instance name specified on the MOD APPL statement. The following example generates restart tokens for source registration DB2DEMO1 using an application name of tokens and then prints those restart tokens: MOD APPL tokens DSN7 RSTTKN GENERATE ADD RSTTKN db2demo1 END APPL tokens PRINT APPL tokens The DTLUAPPL prints the generated tokens because the PRINT APPL statement is specified: Application name=<tokens> Rsttkn=<1> Ainseq=<0> Preconfig=<N> FirstTkn =<> LastTkn =<> CurrentTkn=<> Registration name=<db2demo1. For more information on DTLUAPPL. For more information on configuring the restart token file. Tip: Select an application name and use it only with DTLUAPPL when generating restart tokens.

See “Determining the Restart Point” on page 153. PWXPC skips recovery processing.Starting CDC Sessions Use the Workflow Manager. Note: PWXPC does not read the restart token file if recovery is required. You can choose to run the entire workflow. recover. 3. Workflow Monitor. If all targets in the session are at the same commit level. Workflow Monitor. Cold Start Processing Cold start workflows and tasks by selecting the cold start command in Workflow Manager. Targets will be resynchronized automatically if required PWXPC automatically performs recovery when a workflow or task is warm started. PWXPC continues processing and committing data and restart tokens until the session ends or is stopped. PWXPC reconciles the restart tokens from the restart token file and from the recovery state tables and file. PWXPC re-reads the data for the last UOW committed to higher-level targets and flushes it to those targets with the lower commit level. 3. PWXPC queries the Integration Service about the commit levels of all targets. or cold start workflows and tasks. Warm Start Processing Warm start workflows and tasks by selecting the start or restart command in Workflow Manager. PWXPC Restart and Recovery Operation 167 . For heterogeneous targets. You can choose to warm start. PWXPC performs the following tasks for warm start: 1. Workflow Monitor. or a task in the workflow. part of a workflow. PWXPC issues the following message: PWXPC_12092 [INFO] [CDCRestart] Warm start requested. PWXPC commits the restart tokens to the state tables and file and issues message PWXPC_12104. See “Determining the Restart Point” on page 153. The Integration Service commits any flushed data and restart tokens to any relational targets and updates any non-relational files. PWXPC reads the restart tokens from the restart token file only. or pmcmd to run a workflow or task. PWXPC issues the following message: PWXPC_12091 [INFO] [CDCRestart] Cold start requested PWXPC performs the following tasks for cold start: 1. When you request cold start. 2. If recovery is required for heterogeneous targets. You do not need to recover workflows and tasks before you restart them. or pmcmd. When you request warm start. or pmcmd. 2.

Note: PWXPC does not read the restart token file if recovery is required. When you request recovery. 5. For heterogeneous targets. Stopping CDC Sessions Stop CDC sessions through PowerCenter by issuing the stop command from Workflow Monitor or pmcmd. 4. PWXPC continues processing and committing data and restart tokens until the session ends or is stopped. If all targets in the session are at the same commit level. Recovery Processing Recover workflows and tasks by selecting the recover command in Workflow Manager. If recovery is not required and the reconciled restart tokens differ from those in the state tables and file. 5. and ends. see the description of DTLUTSK in the PowerExchange Utilities Guide. For information about the STOPTASK command and the syntax of the DTLUTSK utility. PWXPC skips recovery processing. Targets will be resynchronized if required and processing will terminate Select Recover to populate the restart token file with the restart tokens for all sources in the CDC session so that you can cold start. You can now warm start or cold start the workflow or task to process changed data from the point of interruption. PWXPC updates the restart token file with the final restart tokens. You do not need to recover workflows and tasks before you restart them. If recovery is required for heterogeneous targets. PWXPC automatically performs recovery when a workflow or task is warm started. 3. 2. or pmcmd. The Integration Service commits any flushed data and restart tokens to any relational targets and updates any non-relational files. 168 Chapter 6: PWXPC .4. PWXPC performs the following tasks for recovery: 1. PWXPC creates the initialization restart token file with the reconciled restart tokens. PWXPC queries the Integration Service about the commit levels of all targets. creates the termination restart token file. PWXPC issues the following message: PWXPC_12093 [INFO] [CDCRestart] Recovery run requested. You can also stop CDC sessions through PowerExchange by issuing the STOPTASK command or by running the DTLUTSK utility. PWXPC reads the restart tokens from the recovery state tables and file. PWXPC re-reads the data for the last UOW committed to higher-level targets and flushes it to those targets with the lower commit level. PWXPC commits the reconciled restart tokens and issues message PWXPC_12104. You can also use recovery to ensure the targets and restart tokens are in a consistent state. Workflow Monitor.Restart and Recovery .

The Integration Service sends an acknowledgement to PWXPC indicating that the targets have been updated. You then execute the changed CDC session. Use Idle Time=0 in the PWX CDC Real Time connection which instructs PowerExchange to stop processing at end of log. see the PowerCenterWorkflow Administration Guide. Use a PWX CDC Change connection to extract changes from condense files. PWXPC issues message PWXPC_12075. 3. the following action occurs: 1. Because the Integration Service creates new state information for your session. You can also stop a workflow or task using the abort command in Workflow Monitor or pmcmd. If you issue the PowerExchange stop command. Your target tables and files are now out-of-sync with their source tables and files. you add a new relational source and target to an existing CDC session that includes relational and non-relational targets. PWXPC also commits the restart tokens and issues message PWXPC_12068. PWXPC performs end of file processing to flush the remaining uncommitted complete units of work to the targets and issues message PWXPC_12101. The Integration Service requests PWXPC to stop if you issue the PowerCenter stop command. The Integration Service ends the session successfully. PWXPC begins reading from a different location in the change stream. Consider this when you change CDC sessions. For example. For information about the abort command. 2. The Integration Service processes all of data in the pipeline and writes it to the targets. it sends an end of file to PWXPC. The Integration Service does not use the existing entry in the state table or the existing state file because some repository attributes are now different from the previous run. See “Configuring Idle Time” on page 113. the Integration Service creates a new entry in the state table and a new state file. Instead. ♦ ♦ You can also stop CDC sessions gracefully if you: Changing CDC Sessions The state table entry and state file name for CDC sessions contains numerous repository attributes. When you use PowerExchange batch change extraction mode for condense files. PWXPC Restart and Recovery Operation 169 . writes the termination restart token file. 5. and shuts down. See “Understanding PWXPC Restart and Recovery” on page 149. the extraction automatically ends when all condensed data is read. 6.When you stop a workflow or task gracefully by issuing the stop command through PowerCenter or PowerExchange. 4.

Cold start the CDC session. session. When you recover tasks. 2. See “Stopping CDC Sessions” on page 168. a new source (RRTB_SRC_004) is added to an existing CDC session containing three sources. use the Workflow Monitor and issue the Recover Task command from Workflow Monitor to run a recovery session. DTLUAPPL is used to generate a restart token representing the current end-of-log in the change stream: 1. Gracefully stop the workflow. The restart points for the existing sources are maintained.rrtb0002_RRTB_SRC_002 000000AD220F00000000000000AD220F0000000000000000 d1dsn7. The session log shows the following: CDCDispatcher> PWXPC_12060 [INFO] [CDCRestart] =============================== Session restart information: =============================== Extraction Map Name Restart Token 1 d1dsn7. Change the session or workflow as desired. RRTB_SRC_004. 2. 3. 5. and workflow to add the new source. update the restart token file to add or remove sources.rrtb0001_RRTB_SRC_001 000000AD220F00000000000000AD220F0000000000000000 d1dsn7.rrtb0003_RRTB_SRC_003 000000AD220F00000000000000AD220F0000000000000000 Restart Token 2 C1E4E2D34040000000AD0D9C00000000 C1E4E2D34040000000AD0D9C00000000 C1E4E2D34040000000AD0D9C00000000 Source GMD storage GMD storage GMD storage PWXPC places the restart tokens in the restart token file specified in the CDC application connection. Stop the workflow by issuing the Stop command in Workflow Monitor. Run DTLUAPPL with RSTTKN GENERATE to generate restart tokens for the current end-of-log.To change a CDC session and then restart it from the point of interruption. After the workflow stops. Use the following DTLUAPPL control cards to do this: mod APPL dummy DSN7 rsttkn generate mod rsttkn rrtb004 end appl dummy print appl dummy The PRINT command produces the following output: Registration name=<rrtb004. Make any necessary changes to the mapping. 3. This displays the current restart points.1> tag=<DB2DSN7rrtb0041> Sequence=<00000DBF240A0000000000000DBF240A00000000> Restart =<C1E4E2D3404000000DBF238200000000> 170 Chapter 6: PWXPC . issue the Recover command for the CDC session. 6. Optionally. 4. PWXPC writes the ending restart tokens for the session into the restart token file. 4. Ensure that the restart token file specified in the source CDC connection specifies the restart token file updated in the recovery session. perform the following tasks: 1. After the workflow stops successfully. Example: Adding a New Source to an Existing Session In this example.Restart and Recovery .

The updated file looks as follows: <!-. PWXPC passes these restart tokens to PowerExchange to recommence extracting changes from the change stream. Update the restart token file to add the new source and its tokens. and network availability issues.rrtb0004_RRTB_SRC_004=C1E4E2D3404000000DBF238200000000 6.rrtb0002_RRTB_SRC_002=000000AD220F00000000000000AD220F0000000000000000 d1dsn7. For additional information. PWXPC Restart and Recovery Operation 171 . do not edit the state information or the mapping for the session before you restart the session. see: ♦ ♦ “Configuring the Restart Token File” on page 160 “Using DTLUAPPL with CDC Sessions” on page 165 Recovering from CDC Session Failures If you run a session with a resume recovery strategy and the session fails. Cold start the session.new source d1dsn7. If the session fails because of transitory errors.rrtb0003_RRTB_SRC_003=C1E4E2D34040000000AD0D9C00000000 <!-.rrtb0002_RRTB_SRC_002=C1E4E2D34040000000AD0D9C00000000 d1dsn7. You must correct permanent errors before restarting the CDC session. If you re-materialize the target table.rrtb0003_RRTB_SRC_003=000000AD220F00000000000000AD220F0000000000000000 d1dsn7. CDC sessions also fail because of permanent errors. you can correct the error and then restart the CDC session. See “Recovery Processing” on page 168. restart the session after the source of the transitory error is corrected. 5. such as: ♦ ♦ Permanent errors such as source or target data errors Transitory errors such as infrastructure problems. PWXPC automatically recovers warm started sessions. The new source does not receive any changes until the first change following its restart point is encountered. you need to re-materialize the target table from the source table before you recommence applying changes to it.rrtb0001_RRTB_SRC_001=C1E4E2D34040000000AD0D9C00000000 d1dsn7. Note: You cannot override the restart point if recovery processing is required. PWXPC does not read the restart token file if you warm start and recovery is required or if you run a recovery session. server crashes. Note that this restart point is earlier than the one just generated for the new source. In other cases.existing sources d1dsn7.rrtb0001_RRTB_SRC_001=000000AD220F00000000000000AD220F0000000000000000 d1dsn7.rrtb0004_RRTB_SRC_004=00000DBF240A0000000000000DBF240A0000000000000000 d1dsn7. such as SQL failures or other database errors. if required although you can also run a recovery session. CDC sessions fail for a number of reasons.Add eight zeroes to the end of the Sequence= value to create the restart token file value. With some failures. you need to provide restart tokens matching the new restart point in the change stream and the cold start the CDC session.

Example: Session Recovery In this example.rrtb0005_RRTB_SRC_005 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. Managing Session Log and Restart Token File History When you run CDC sessions.rrtb0006_RRTB_SRC_006 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. PWXPC stores endUOW restart tokens in the state table and file unless sub-packet commit is used. The from restart tokens are the same as those displayed in the PWXPC_12060 messages for all sources. PWXPC and the Integration Service continue to read and write data and restart tokens until the session ends or is stopped. session log and restart token file history is often useful for recovery situations. CDCDispatcher> PWXPC_12069 [INFO] [CDCRestart] Running in recovery mode. This restart token represents the start point in the change stream for the oldest uncommitted UOW. The Restart 1 values represent the start and end change records in the Restart 2 UOW. Reader will resend the the oldest uncommitted UOW to resync targets: from: Restart 1 [00000FCA65840000000000000D2E004A00000000FFFFFFFF] : Restart 2 [C1E4E2D3404000000D21B1A500000000] to: Restart 1 [00000FCA65840000000000000D300D8000000000FFFFFFFF] : Restart 2 [C1E4E2D3404000000D21B1A500000000].rrtb0007_RRTB_SRC_007 00000FCA65840000000000000D2E004A00000000FFFFFFFF Restart Token 2 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 C1E4E2D3404000000D21B1A500000000 Source GMD storage GMD storage GMD storage GMD storage GMD storage GMD storage GMD storage GMD storage GMD storage PWXPC issues the PWXPC_12069 message when it detects that recovery is required.rrtb0008_RRTB_SRC_008 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. You can also change the 172 Chapter 6: PWXPC . The to restart tokens represent the end of the oldest uncommitted UOW.rrtb0003_RRTB_SRC_003 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. The 12069 message usually includes the begin-UOW (from) and end-UOW (to) restart tokens for the oldest uncommitted UOW that PWXPC re-reads during recovery. Since the application connection for this session specifies sub-packet commit.rrtb0001_RRTB_SRC_001 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. Change the Save session log for these runs in either the session or Session Configuration properties to specify the number or runs to keep the session logs. You can use these historical files to find previous restart points when data needs to be re-extracted.Restart and Recovery . By default. a CDC session with relational targets is aborted using the Workflow Monitor. PWXPC rereads the changes between the two restart token values in the 12069 message and issues a commit for the data and the restart tokens. The Restart Task command is issued from the Workflow Monitor for the CDC session.rrtb0002_RRTB_SRC_002 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. the Restart 2 value is the begin-UOW value in both cases. The Integration Service writes the data to the target tables and the restart tokens to the state table.rrtb0009_RRTB_SRC_009 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. PWXPC issues the following messages displaying the restart tokens found for the session and its sources: CDCDispatcher> PWXPC_12060 [INFO] [CDCRestart] =============================== Session restart information: =============================== Extraction Map Name Restart Token 1 d1dsn8. See “Configuring Commit Threshold” on page 119. PWXPC issues the following message: PWXPC_12092 [INFO] [CDCRestart] Warm start requested. Targets will be resynchronized automatically if required PWXPC automatically recovers when the session is warm started.rrtb0004_RRTB_SRC_004 00000FCA65840000000000000D2E004A00000000FFFFFFFF d1dsn8. the Integration Service keeps a single session log for each workflow or session.

PWXPC keeps a single pair of initialization and termination restart token files.> | <because Real-time Flush Latency [<n>] occurred. In the source CDC connection. Application Connection . use the restart tokens in the appropriate 10081 message to populate the restart token file and cold start the CDC session. When PWXPC issues a real-time flush to commit data to the targets.Save session log by attribute to keep session logs by timestamp instead of number of runs.Number of Restart Token Files You can determine starting and ending restart points for each extraction using historical copies of the restart token file. PWXPC passes the restart token file values to PowerExchange to extract the data from that point forward. PWXPC Restart and Recovery Operation 173 . For more information about archiving session logs. This message contains the restart tokens at that point in time: PWXPC_10081 [INFO] [CDCDispatcher] raising real-time flush with restart tokens [<restart1_token>]. You need historical copies of the session logs to re-extract changes at any point in between the session start and end. see the PowerCenterWorkflow Administration Guide. it issues message PWXPC_10081. request more than a single copy by specifying a value larger than 1 in the Number of Runs to Keep RestartToken File attribute.> To restart an extraction from a specific commit point. Figure 6-1 shows an example of an Application Connection that specifies that 10 copies of the restart token file be maintained in the Restart Token File Folder: Figure 6-1. [<restart2_token>] <because UOW Count [<n>] is reached.

174 Chapter 6: PWXPC .Restart and Recovery .

185 175 .Chapter 7 Flexible Key Custom Transformation This section covers the following topics: ♦ ♦ Target Key Transformations. 176 Group Source and Flexible Transformations.

Target Key Transformations The Flexible Target Key Custom Transformation has been developed to address the case where a data target has its Primary Key mapped to a column in a PowerExchange Change Data Capture source. For sessions involving large amounts of data this overhead could be significant. and comprise both a “before image” field and a “change indicator” for any given field. From this information a delete/insert pair can then be generated for the target. Prior to the implementation of the Flexible Target Key facility. Figure 7-1 illustrates the process: Figure 7-1. For those wishing to keep network traffic to a minimum. COL1 is marked as the primary key for the target table and is therefore treated as a delete of row A and an insert of row C. Primary key updates from a source relational table Here we see the that COL1 is updated from an A to a C. These indicators identify instances where that field has changed. the only way to identify these changes to a key field was to pass the full record before and after image in the change stream. which may be subject to update. PowerExchange has been enhanced to allow indicators to be added to specific fields. 176 Chapter 7: Flexible Key Custom Transformation .

Open the group as shown below: Target Key Transformations 177 .Configuring the PowerExchange Extraction Map To ensure enough information is passed through to PowerCenter for a column. intended for use as a target primary key. a “change indicator” and “before image” field must be associated with the PowerExchange extraction map. To add the before image and change indicator right click on the required extraction group. 2. or columns. Configuring an extraction map: 1.

178 Chapter 7: Flexible Key Custom Transformation . Right-click on the column which requires the before image and change indicator to be set. Open the required extraction map by either right-clicking and selecting open . or by double-clicking on the required extraction map. 4.3.

Select Amend Control Indicator/Before Image Extensions Target Key Transformations 179 .5.

This must be done through the Import from PowerExchange option under Source Analyzer in the PowerCenter Designer. For more information on importing a CDC source see “Working with Extraction Map Definitions” on page 53. For more information about importing a target see “Source and Target Definitions in Designer” on page 19. Repeat the process for columns which will require the before image to be included with the change capture data. Configuring PowerCenter The PowerExchange Change Data Capture (CDC) source will now need to be imported. Import them using the Target Designer in the PowerCenter Designer. Select and add (by double-clicking or highlighting and then using the “Add >>” button) the required column to set the change indicator. select the Before Images tab. 180 Chapter 7: Flexible Key Custom Transformation . After the CDC source has been imported. Note: The BI and CI column names can be changed on these screens by single-clicking and editing. 7. The following sections in this chapter will refer to the default names. When all the required change indicators have been set up. the target definitions will be required.6.

The DTL__CAPX columns are PowerExchange capture columns. and the PARTNER_CUST_ID is an attribute of the table. DB2 Target Table Mapping The source table has a primary key of CUSTOMER_ID. if the PARTNER_CUST_ID changes in the source table. In this case. The transformation will load the data into the target table where the PARTNER_CUST_ID is the primary key. The structure of the source CDC table is: Figure 7-2. DB2 Extraction Map Source Mapping Note: The columns prefixed DTL_CI and DTL_BI are the change indicator and before image respectively which are vital for this flexible transformation. a delete and insert will be required for the target. The target is a DB2 table of the following structure: Figure 7-3. Target Key Transformations 181 . and the CUSTOMER_ID is an attribute of that table.The following example will work with a DB2 data capture source and a DB2 target table.

Create the Flexible Transformation 1. DB2 Source to DB2 Target CDC mapping Note: Any of the control information including BI and CI columns could. be defined in the target definition.Now drag the PowerExchange CDC source. if required. This create will cause a transformation to appear. and the target into the mapping as below: Figure 7-4. From the Transformation option select Create and then select a transformation type of FLXKEYTRANS. In addition the transformation will require the BI and CI indicators which were assigned 182 Chapter 7: Flexible Key Custom Transformation . Now link into the transformation the required columns from the source for the target. 2.

Link the transformation to the target. No links will exist from the transformation to the target for Target Key Transformations 183 .earlier in PowerExchange (see “Configuring the PowerExchange Extraction Map” on page 177). Multiple columns can be added here when the target primary key demands. 4. Note: The example above shows a single column primary key. 3. Right-click on the transformation you have just created and select “Edit”. Only link the required data columns from the transformation to the target. From within the edit dialog box select the Source Column Map tab and add the columns to which the relevant before images and change indicators are assigned. The BI and CI columns need to be linked to the Flexible Transformation. A final column DTL__CAPXACTION should also be added to the transformation.

This will result in the following mapping: 5. nor for the DTL__CAPXACTION column unless required in the target. 184 Chapter 7: Flexible Key Custom Transformation . Now create the workflow from the mapping as normal.the CI and BI columns.

ksdsm2 respectively. 1. These data maps are ksdss1. This process is described in the relevant PowerExchange Adapter Guide. Note: In this example a datamap has been created for records with a REC_TYPE of “A” in the example above.ksdsm1 and ksdss2. 2. Now register each of these data maps for PowerExchange capture. can be processed through a single Flexible Transformation and applied to two output DB2 tables. For an NRDB source create a data map as defined in the relevant PowerExchange Adapter Guide. See “PowerExchange Group Source” on page 68. split into two different record types. 4. Assign the BI and CI PowerExchange fields to the extraction map as shown above in “Configuring the PowerExchange Extraction Map” on page 177. The Flexible Target Key Custom Transformation also supports this functionality.. 3. and for REC_TYPE of “B”. The following example shows how data changes captured from a VSAM file. Group Source and Flexible Transformations 185 .Group Source and Flexible Transformations The PowerExchange Group Source functionality allows changed data for multiple sources or multiple records in a single source to be read during a single pass. Amend the data map to assign the relevant record id value test as shown in the dialog box below.

Import the relevant data targets. These are added when you “Edit” the 186 Chapter 7: Flexible Key Custom Transformation . and that they are linked to their own individual output tables. When the mapping is created it will look similar to the following:.5. In this example the two input capture streams will be written to two separate DB2 tables. Note how the Flexible Transformation here contains the columns for both of the PowerExchange change data input sources. 6. but subsequent input/ output groups will be required for each source. Now import these two extraction maps as data sources into the PowerCenter Designer using Import from PowerExchange. 7. An input and output group is added when the flexible transformation is created. In step 7 on page 186 the Flexible Transaction includes Input and Output Groups.

transformation and select the “Ports” tab shown below and then use the Create Input Group and Output Group buttons (the Create Input Group button is highlighted here): Before validating the mapping the before imaged and change indicators will need to be assigned to ports as shown in step 4 on page 185. Group Source and Flexible Transformations 187 .

188 Chapter 7: Flexible Key Custom Transformation .

191 189 .Chapter 8 PowerExchange ODBC Installation This chapter covers the following topics: ♦ ♦ Overview. 190 Creating ODBC Data Sources.

The PowerExchange software needs to be installed on the same PowerCenter Client and Server machines. the following products must be installed: ♦ ♦ PowerCenter 8. 190 Chapter 8: PowerExchange ODBC . Install PowerExchange on the PowerCenter Client and Integration Service machines. See “Functional Comparison between PWXPC and PowerExchange ODBC” on page 2. you must install and configure PowerCenter and PowerExchange.5. Note: PWXPC provides additional functionality that is not available with ODBC. Integration Service and Repository Server software needs to be installed on the appropriate platforms. If you have installed the 64-bit version of Integration Service. you must install and configure PowerCenter and PowerExchange. Installation Requirements To use the PowerExchange ODBC connection with PowerCenter. For more information about installing PowerCenter see the PowerCenter Installation Guide.5.Installation . PowerExchange 8. If you have installed the 32-bit version of Integration Service.Overview Before installing and configuring the PowerExchange ODBC connection. The PowerCenter Client. For more information about installing PowerExchange see the PowerExchange Installation Guide. you must install the 32-bit version of PWXPC and of PowerExchange. you must install the 64-bit version of PWXPC and of PowerExchange. Prerequisites Before installing and configuring the PowerExchange ODBC connection.

Creating ODBC Data Sources on the PowerCenter Client Machine On the PowerCenter client machine. The ODBC data source is created. 3. 2. 4. For more information about creating ODBC data sources. 5. Select the location from the Location pull-down list. 7. 9. Enter a name for the data source in the Name box.cfg). 6. you need to define ODBC data sources so that the workflow accessing PowerExchange sources and targets can connect to the PowerExchange Listener to extract the data. To create an ODBC data source: 1. Click Finish. Click the Add button. 8. Creating ODBC Data Sources on the Integration Service Machine On the machine running the Integration Service. see "Using ODBC with PowerExchange" in the PowerExchange Reference Manual. Creating a PowerExchange ODBC Data Source on Windows Follow the instructions in “Creating ODBC Data Sources on the PowerCenter Client Machine” on page 191. Click Control Panel > Administrative Tools >Data Sources (ODBC). Select the Informatica PowerExchange driver from the list of available drivers. you need to define ODBC data sources so that the metadata for PowerExchange sources and targets can be imported. Creating ODBC Data Sources 191 . Select the data source type from the Type pull-down list. Complete all properties parameters. Depending on the data source selected you will be presented with other specific properties that you can set.Creating ODBC Data Sources You can create ODBC Data Sources on the PowerCenter Client and Integration Service machines. Click the System DSN tab. and click OK. This is name defined on a NODE= statement defined within the PowerExchange configuration file (dbmover.

Creating a PowerExchange ODBC Data Source on UNIX or Linux
Update the appropriate ODBC.INI file to define the ODBC data sources for PowerExchange. The data source entries in the ODBC.INI file have the following format:
[<data source name>] DRIVER=/<PowerExchange full install path>/libdtlodbc.sl DESCRIPTION='<Descriptive Text for Data Source>' LOCATION=<data source node from dbmover.cfg> DBTYPE=< Access method for file or database> … (other ODBC parameters as appropriate)

For more information about ODBC data source parameters (both mandatory and optional) for a specific DBTYPE, see "Using ODBC with PowerExchange" in the PowerExchange Reference Manual. The <data source name> defined in the odbc.ini is specified in the Connect String value of the ODBC Connection in PowerCenter. This connect string causes the PowerExchange ODBC driver to be loaded and the specified location to be contacted to extract or load the data. For more information on ODBC connectivity with PowerCenter, see the PowerCenter Configuration Guide.

192

Chapter 8: PowerExchange ODBC - Installation

Chapter 9

PowerExchange ODBC Working with Mappings
This chapter covers the following topics:
♦ ♦ ♦

Overview, 194 Working with Source and Target Definitions for PowerExchange Batch, 195 Working with Source Definitions for PowerExchange Change or Real-Time, 198

193

Overview
A mapping is a set of source and target definitions linked by transformation objects that define the rules for data transformation. Mappings represent the data flow between sources and targets. Source and target definitions represent metadata for sources and targets. When you create a source definition, its structure differs depending on the type of source it represents:
♦ ♦

Non-relational sources require a multi-group source definition. Relational sources use a single-group source definition.

The source qualifier for a source definition also differs in structure depending on the type of source definition. After you create a source or target definition, you can include it in a mapping to extract data from the source or load data to the target. You can extract source data in batch, change, or real-time mode. You can use one source definition and one mapping for all modes. For a list of sources and targets that PowerExchange ODBC Interface supports, see Table 1-4 on page 8. This table also lists whether the Integration Service can read the source data in batch, change, or real-time mode.

194

Chapter 9: PowerExchange ODBC - Working with Mappings

Working with Source and Target Definitions for PowerExchange Batch
With PowerExchange ODBC, you can create source or target definitions to access VSAM and sequential datasets (flat files), Adabas, DataCom, DB2, IDMS, IDMSX, or IMS databases. You create the source and target definitions identically regardless of the database type. After you create a source or target definition, you can edit it. For non-relational sources, the metadata imported is from the PowerExchange data map created through the PowerExchange Navigator. In the case of DB2/390 and DB2/400, the metadata is obtained either directly from the DB2 catalog or from a PowerExchange data map.

Importing a Source or Target Definition
You connect to a PowerExchange Listener to import a source or target definition using ODBC. Therefore, the data map must be sent to the PowerExchange Listener before it can be imported using an ODBC connection in Designer. When you connect to the PowerExchange Listener, the Designer displays a list of schemas and tables. Before you connect, you can filter the metadata the Designer displays by schema name. Select a table from the displayed list to create the source or target definition. When you import a DB2/390 or DB2/400 source definition through a PowerExchange Listener, the Designer imports the primary keys.

Working with Source and Target Definitions for PowerExchange Batch

195

To import a source or target definition: 1.

Click Sources > Import from Database … in the Source Analyzer if importing a source definition. Click Targets>Import from Database … in the Target Designer if importing a target definition. The following Import Tables dialog box appears.

Use the Owner name field to restrict the objects retrieved. When you import PowerExchange data maps, the Owner is the Schema Name of the data map and the ODBC data source must have a DB Type of NRDB or NRDB2. When the DB2 catalog is used for DB2/390 or DB2/400, the Owner is the owner of the DB2 tables and the DB Type must be either DB2 or DB2400C. If the Listener pointed to by the ODBC data source is running with PowerExchange Security (either SECURITY=(1,x) or SECURITY=(2,x) in the PowerExchange configuration file), then a valid userid and password must be provided. The only difference between NRDB and NRDB2 is whether a three or two tier naming conventions is used in the SQL statements to extract or load data. Non-relational sources and targets mapped in PowerExchange can be referred to using either NRDB or NRDB2. The format is as follows:
schema.mapname.table for NRDB or schema.mapname_table for NRDB2

196

Chapter 9: PowerExchange ODBC - Working with Mappings

3. Use the Select All button to select all tables.2. Click Repository > Save. Select the table you want to import. The source or target definition appears. Working with Source and Target Definitions for PowerExchange Batch 197 . Hold down the Ctrl key to make non-contiguous selections within a schema. Click Connect. Click OK. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. 4. Use the Select None button to clear all highlighted selections. 5.

you can edit it. Extraction maps are created by the PowerExchange Navigator when the source is initially registered for Change Data Capture. The Import Tables dialog box appears. and Oracle databases. To import a Change Data Capture Source Definition 1. Click Sources > Import from Database in the Source Analyzer. The entire extraction map name has the following format: <D><N><instance>.Working with Mappings . When you import PowerExchange extraction maps the Owner is the first qualifier of the extract map name. IDMS. you can create source definitions to access changed data for VSAM datasets (including CICS/VSAM). Importing a Change Data Capture Source Definition You initially create the source definitions in a similar way regardless of the database type.<regname>_TABLENAME where: 198 Chapter 9: PowerExchange ODBC . Datacom. The metadata that is imported for all change data sources is taken from the PowerExchange extraction maps.Working with Source Definitions for PowerExchange Change or Real-Time With PowerExchange ODBC. When you have created the source or target definition. and Adabas. DB2. These can be manually modified at a later date. Use the Owner name field to restrict the objects retrieved. MSSQL Server. IMS.

Database-specific identifier (e.g. Working with Source Definitions for PowerExchange Change or Real-Time 199 . 1 for DB2/390.x) or SECURITY=(2. 4. Click Connect. Click Repository > Save.) instance .♦ ♦ ♦ ♦ D . If the Listener pointed to by the ODBC data source is running with PowerExchange Security (either SECURITY=(1. then a valid user name and password must be provided. Use the Select None button to clear all highlighted selections. 2 for IMS.the registration name chosen for the source registration.. For example. 3 for DB2/400. DB2/390 extraction map name might be: d1dsn7. These DB Types instruct the Listener to select extraction maps rather than data maps. 2.x) in the DBMOVER configuration). Click OK. Hold down the Ctrl key to make non-contiguous selections within a schema.testdb2_KJM723TB. Select the table you want to import. Use the Select All button to select all tables. When you import Change Data Capture source definitions. 3. etc.the default entry starts with D (any user-modified maps start with U) N .instance name chosen for the source registration regname . The source definition appears. the ODBC data source must have a DB Type of CAPX or CAPXRT. ♦ ♦ ♦ ♦ Hold down the Shift key to select blocks of tables. 5.

200 Chapter 9: PowerExchange ODBC .Working with Mappings .

202 Working with Connections for PowerExchange ODBC. 203 201 .Chapter 10 PowerExchange ODBC Configuring Connections This chapter covers the following topics: ♦ ♦ Overview.

When you create or modify a session that reads from or writes to a database. Connections are saved in the repository. 202 Chapter 10: PowerExchange ODBC . you must configure connections in the Workflow Manager. you configure relational database connections.Overview Before PowerCenter can access a source or target in a session.Configuring Connections . For PowerExchange ODBC. you can select only configured source and target databases.

DB2400C. Table 10-1 describes the connections you create for data extraction based on the extraction mode: Table 10-1.Working with Connections for PowerExchange ODBC This section describes the connection types used for extracting and loading data as well as how to configure connection attributes. see the PowerExchange Reference Manual. Connection Types for Loading Target Data All target connections are Relational Database Connection when loading data to PowerExchange targets. Connection Types for Extracting Source Data Application Connection/ Relational Database Connection Relational Connection Relational Connection Extraction Mode Batch mode (non-relational data map) Batch mode (relational) Connection Type ODBC with NRDB and NRDB2 Data Source ODBC with Data Source of appropriate database type (DB2. Connection Types for Extracting Source Data The connection you configure depends on the extraction mode. Table 10-2 describes the target database types and their capability: Table 10-2. etc. ADAUNLD. Target Database Types Database Type (Access Method) Adabas Datacom DB2 (DB2) Insert Yes No Yes Update Yes No Yes Delete Yes No Yes Working with Connections for PowerExchange ODBC 203 . The type of source data you want to extract does not affect the connection type although it will affect which ODBC data source is used in the Connect String as there may be multiple different Listeners and platform-specific parameters.) ODBC with CAPX Data Source ODBC with CAPXRT Data Source Change mode Real-time mode Relational Database Connection Relational Database Connection Note: For more information about the full range of database types that can be specified in ODBC Data Sources.

Configuring Connections . Source and target ODBC connections in Workflow Manager are defined as Relational connections with a subtype of ODBC.Connection Object Definition 204 Chapter 10: PowerExchange ODBC . For more information about ODBC data sources. The ODBC connection definition process is the same for Batch. ODBC . and Real-Time. Figure 10-1 shows the Connection Object Definition dialog box for an ODBC relational connection: Figure 10-1. the majority of the attributes are specified in the ODBC data source rather than in the connection in PowerCenter. see “Using ODBC with PowerExchange” in the PowerExchange Reference Manual.Database Type (Access Method) DB2 (DB2400C) IDMS IMS Sequential (NRDB/NRDB2) VSAM. The only difference in these connections is the ODBC data source to which they point. Change.KSDS (NRDB/NRDB2) VSAM-ESDS (NRDB/NRDB2) VSAM-RRDS (NRDB/NRDB2) Insert No No No Yes Yes Yes Yes Update No No No No Yes No No Delete No No No No Yes No No Configuring Attributes for Connections When using ODBC connections.

Name of the ODBC data source. Number of seconds the Integration Service attempts to reconnect to the database if the connection fails. Default is disabled. the session fails. Default is disabled. Password for the User Name. If the Integration Service cannot connect to the database in the retry period.Table 10-3 shows the Connection Object Definition dialog box for an ODBC relational connection and describes the connection attributes to configure for an ODBC relational database connection: Table 10-3. ODBC Connection Object Definition Table Connection Attribute Name User Name Password Connect String Code Page Connection Environment SQL Transaction Environment SQL Connection Retry Period Required/ Optional Required Required Required Required Required Optional Optional Optional Description Name for the relational database connection. Code page for the Integration Service to use to extract the data from the data source. Executes an SQL command before the initiation of each transaction. Username for the data source. Executes an SQL command with each database connection. Working with Connections for PowerExchange ODBC 205 .

206 Chapter 10: PowerExchange ODBC .Configuring Connections .

208 Extracting Data from PowerExchange in Batch Mode.Chapter 11 PowerExchange ODBC Sessions and Workflows This chapter covers the following topics: ♦ ♦ ♦ ♦ Overview. 215 207 . 209 Extracting Data from PowerExchange in Change and Real-Time Mode. 213 Loading Data to PowerExchange Targets.

While processing data.Sessions and Workflows . or real-time mode. you can create a session and use the session in a workflow to extract. you can increase the number of partitions in a pipeline to improve session performance. You can specify multiple partitions in a pipeline if the Integration Service can maintain data consistency when it processes the partitioned data. and scheduling workflows. the Integration Service may process data out of sequence due to the varying rates at which the partitions process data. Partition Types for Partitioning Points for Sources Source Type Non-relational Relational Partitioning Point Application Multi-Group Source Qualifier Source Qualifier Partition Type Pass-through Key range Pass-through Partition Types for Loading Target Data If you are configuring a session to write data to DB2/390 and DB2/400 targets. you can specify all partition types. Increasing the number of partitions allows the Integration Service to create multiple connections to sources and targets and process partitions of data concurrently. see the PowerCenterWorkflow Administration Guide. Table 11-1 describes the partition types for partitioning points when extracting source data in batch mode: Table 11-1. For more information about creating.Overview After you create mappings in the PowerCenter Designer. configuring. You can also create a session to load data to a target. you must schedule the workflow. see the PowerCenterWorkflow Administration Guide. Partition Types for Extracting Source Data If you are configuring a session to read source data. For more information about partitioning and a list of all partitioning restrictions. change. Pipeline Partitioning Depending on your source or target database. 208 Chapter 11: PowerExchange ODBC . transform. When you create a session in a workflow. you can use partitioning if the session mode is batch. the Workflow Manager validates each pipeline in the mapping for partitioning. You determine how you want the Integration Service to extract the data when you configure the session. and load data. You can create a session in a workflow to extract data in batch. After you configure the workflow. You create sessions and workflows in the Workflow Manager.

The connection you select and the session properties you configure differ depending on the type of source data.datamapname. You should use a connection with the same DBType as used when the source was imported. That is. you must select the appropriate ODBC relational connection and configure session properties. Non-relational sources and targets mapped in PowerExchange can be referred to using either NRDB or NRDB2.table NRDB2: schema.Extracting Data from PowerExchange in Batch Mode To extract data in batch mode. Session Properties for Non-Relational Batch Mode Sessions The relational connection for non-relational sources should point to an ODBC data source that has a DBType of either NRDB or NRDB2. if you imported the source mapping using NRDB. The format is as follows: ♦ ♦ NRDB: schema.datamapname_table Extracting Data from PowerExchange in Batch Mode 209 . then use an NRDB ODBC connection in the session connection as opposed to an NRDB2. Note: The only difference between NRDB and NRDB2 is whether a three or two tier naming conventions is used in the SQL statements to extract or load data.

3.name} 210 Chapter 11: PowerExchange ODBC . In the Reader field of the Readers settings. In the Task Developer. For more information about other Properties attributes. see the PowerCenter Workflow Administration Guide. 4. select the non-relational ODBC connection (NRDB or NRDB2). 2. Relational Reader is automatically selected.To configure a batch mode session for non-relational sources: 1. In the Connections Value field. see the PowerExchange Reference Manual. Click the Sources view on the Mapping tab. the schema name of the PowerExchange data map (or the Owner name displayed when the source mapping is edited) must be specified in order to correct construct the SQL statement during execution. The following example indicates how the Owner Name attribute can be configured to provide the schema name for the source (seq) as well as an override for the physical file name in the data map (dtldsn=new. PowerExchange SQL Escape Sequences can also be specified in this attribute field to override specifications in the data map. For a complete list of the SQL Escape Sequences available.name): seq{dtldsn=new. double-click a session with a non-relational source to open the session properties. configure the Owner Name attribute. At minimum.dataset. In the Properties settings.Sessions and Workflows .dataset. 5.

configure the Owner Name attribute. DB2UDB. 3. see the PowerCenter Workflow Administration Guide. you must select the appropriate ODBC relational connection and configure session properties. Relational Reader is selected. In the Reader field of the Readers settings. In the Connections Value field. You can then configure the session properties as you would any other PowerExchange ODBC source.Note: SQL escape sequences and the Owner Name can be specified in any order in the attribute field. In the Task Developer. 2. MSSQL or Oracle). Click the Sources view on the Mapping tab. In the Properties settings. The relational connection should point to an ODBC data source that has the DBType of the source (DB2. 4. double-click a session with a relational source to open the session properties. Click OK. Session Properties for Relational Batch Mode Sessions To extract data from a relational source in batch mode. 6. DB2400C. Extracting Data from PowerExchange in Batch Mode 211 . select the appropriate relational ODBC connection. For more information about other Properties attributes. To configure a batch mode session for relational sources: 1.

would not be required here. Click OK. Alternatively. 5. 212 Chapter 11: PowerExchange ODBC . if done.At minimum. the owner name of the source table must be specified in order to correct construct the SQL statement during execution. the Owner Name can be specified in the source mapping and.Sessions and Workflows .

restart is handled from within PowerExchange. In the Reader field of the Readers settings. double-click a session with a relational source to open the session properties. The connection you select for change mode should refer to an ODBC data source with a DBType of CAPX whereas a real-time mode connection should refer to an ODBC data source with a DBType of CAPXRT. Extracting Data from PowerExchange in Change and Real-Time Mode 213 . Session Properties for Change and Real-Time Mode Sessions Use the following procedure to configure a session for change or real-time mode.Extracting Data from PowerExchange in Change and Real-Time Mode To extract data in change and real-time mode. When using ODBC to extract data from PowerExchange in either Change or Real-Time mode. Click the Sources view on the Mapping tab. 3. Relational Reader is automatically selected. you must select an ODBC relational connection and configure session properties. In the Task Developer. 2. To configure a change or real-time mode session: 1.

For more information about other Properties attributes. Click OK.4. see the PowerCenter Workflow Administration Guide. It can also be determined by checking the Owner Name in the source mapping. For a complete list of the SQL Escape Sequences available. select a connection which points to an ODBC data source with DBType CAPX (for Change) or CAPXRT (for Real-Time) and the appropriate Location value. PowerExchange SQL Escape Sequences can also be specified in this attribute field to override specifications in the data map. 214 Chapter 11: PowerExchange ODBC . configure the Owner Name attribute. This name is the first qualifier of extraction map name shown in the PowerExchange Navigator. At minimum. Note: SQL escape sequences and the Owner Name can be specified in any order in the attribute field. 6. the schema name of the source extraction map must be specified in order to correct construct the SQL statement during execution. The following example indicates the manner in which the Owner Name attribute can be configured to provide the schema name for the source (d6vsam) as well as an override for the application name specified in the DBQual2/Application Name field in the ODBC data source (dtlapp=new_appname): {dtlapp=new_appname}d6vsam 5.Sessions and Workflows . In the Properties settings. In the Connections Value field. see the PowerExchange Reference Manual.

see the PowerCenter Workflow Administration Guide. Click the Targets view on the Mapping tab. select a connection which points to an ODBC data source with appropriate DBType and Location value.Loading Data to PowerExchange Targets To load data to a PowerExchange target. For more information about configuring sessions for relational sources. 3. In the Connections Value field. ensure that Relational Writer is selected. you must select a relational database connection. configure the Table Name Prefix attribute. 6. To configure a session to load data to a PowerExchange target: 1. In the Writers settings. 4. 2. In the Properties settings. double-click a session with a relational source to open the session properties. Loading Data to PowerExchange Targets 215 . the schema name of the target table (if relational) or the PowerExchange data map (if non-relational) must be specified in order to correct construct the SQL statement during execution. In the Task Developer. Click OK. 5. Then configure properties for the session as you would any other relational target. At minimum.

216 Chapter 11: PowerExchange ODBC .Sessions and Workflows .

Restart and Recovery This chapter covers the following topics: ♦ ♦ Overview. 218 Restart and Recovery Using PowerExchange ODBC.Chapter 12 PowerExchange ODBC . 219 217 .

With PowerExchange ODBC. The considerations differ depending upon whether the session uses PowerExchange Client for PowerCenter (PWXPC) or PowerExchange ODBC.Restart and Recovery . This is primarily due to the differences in where the restart information is maintained. the restart information is controlled and maintained on the PowerExchange Listener platform in the internal change information file (CDEP) using the application name specified in the connection. 218 Chapter 12: PowerExchange ODBC .Overview Recovery and restart need to be considered when designing and configuring sessions and workflows using either PowerExchange Change or Real-Time.

Warning: Failed sessions that are restarted will extract data from the last successful session (based on CAPXTYPE specified). The CDEP file used is the one maintained by PowerExchange on the platform targeted by the extraction. Note: Unique application names should be used for each for each session to prevent any conflict in the CDEP between multiple sessions. they will not be provided any records from the change stream until their restart points have been reached. If there are sources included that have newer restart points. Managing Restart Tokens Using PowerExchange ODBC PowerExchange on the source platform reads the restart tokens from the CDEP for each source included in the session. then those tokens will be used regardless of the extraction type. The first time a session is run with a new application name. The CDEP file contains both begin and end restart tokens for each extraction. This means that there is the possibility that duplicated changes will be sent to the target. This can be overridden at the session level by using the SQL Escape Sequence DTLXTYPE. For more information about ODBC parameters and SQL Escape Sequences see the PowerExchange Reference Manual. In the event of a failure. Restart and Recovery Using PowerExchange ODBC 219 . The extraction type is specified in the ODBC connection in the CAPXTYPE parameter. The restart tokens determine the baseline point from which to extract the changed data for the source database.Restart and Recovery Using PowerExchange ODBC PowerExchange ODBC uses the restart tokens associated with application names in the CDEP file to determine the starting extraction point for a session. This prevents sources from being passed records that they processed in the previous extraction run. the extraction type decides which ones will be used for restart. If new tokens have been supplied by DTLUAPPL. Failed sessions do not update the restart token information in the CDEP with the progress so far. you must either restore the targets to match the restart point prior to restarting the session or design your PowerCenter session to handle the possibility of duplicate records. If the application name already exists in the CDEP. Which restart tokens are used depends upon the extraction type (SL or RS) and whether new tokens have been supplied by DTLUAPPL since the last run. Since both start and end restart tokens are available when using ODBC. PowerExchange will use the appropriate restart tokens to commence extraction from the change stream. This differs from PWXPC where only the end restart tokens are maintained in the restart token file. If the extraction type specified is Since Last (SL) then the extraction will commence at the last successful ending point. an entry for it will be automatically created in the CDEP if it does not already exist. The CDEP information for an extraction is only updated when a session ends successfully. If it is Restart (RS) then it will commence at the starting point of either the last successful extraction that was run or the one that is specified with the Reset Start Point in the extraction application dialog box in the PowerExchange Navigator.

1> tag=<DB2DSN7db2demo21> Sequence=<000007337D8A00000000000007337D8A00000000> Restart =<D2D1D4D34040000007337D0200000000> Registration name=<db2demo3. CDEP Restart Tokens Example The following example shows the contents of restart tokens in the CDEP for an application that contains a restart token file for the DB2 sources DB2DEMO1.1> tag=<DB2DSN7db2demo31> Sequence=<000007337D8A00000000000007337D8A00000000> Restart =<D2D1D4D34040000007337D0200000000> The application name odbc_db2demo13ac was created using DTLUAPPL with RSTTKN GENERATE.Restart and Recovery . DB2DEMO2. An example of the control cards that were used is given below: mod APPL odbc_db2demo13ac DSN7 RSTTKN GENERATE add rsttkn db2demo1 add rsttkn db2demo2 add rsttkn db2demo3 end APPL odbc_db2demo13ac print appl odbc_db2demo13ac You can use either ADD APPL or MOD APPL for a new application name as with MOD APPL DTLUAPPL will create the application name if it does not already exist.1> tag=<DB2DSN7db2demo11> Sequence=<000007337D8A00000000000007337D8A00000000> Restart =<D2D1D4D34040000007337D0200000000> Registration name=<db2demo2. 220 Chapter 12: PowerExchange ODBC . the session using this application name can be started and it will use this restart tokens. After the new restart tokens are provided through DTLUAPPL. PowerExchange updates the CDEP with the ending restart tokens. and DB2DEMO3: Application name=<odbc_db2demo13ac> Rsttkn=<3> Ainseq=<0> Preconfig=< > FirstTkn =<D2D1D4D340400000003ED5D600000000> LastTkn =<D2D1D4D340400000003ED5D600000000> CurrentTkn=<> Registration name=<db2demo1.After a session completes successfully.

Appendix A Usage Tips and Tricks This appendix provides details about the following: ♦ ♦ ♦ ♦ ♦ Organizing Sources by Map Type in Designer. 222 Filtering Source Data using PWXPC. 233 221 . 227 Creating Sequential and GDG Data Sets. 224 Using DTLREXE to Submit MVS Batch Jobs. 230 Using Event Table Processing to Shutdown Sessions.

there are two choices: 1.IMS1T01_IMSSEG1. You can use the name you assign for the location as a method of organizing your source metadata in Designer.IMS1T01_IMSSEG1.cfg file. To illustrate. 2. So. The map name for both the data map and extraction map are the same.cfg that indicate the type of data you are retrieving. these folder names have the following format: <source_type_location>. For example. Use a different name for the capture registration so that a unique extraction map name is created. The user cannot choose the subfolder name and the table names within those sub-folders must be unique.If you use the IMS database name for the Capture Registration Name as well. All IMS sources imported from that location will be stored into that folder. With the PWXPC Import from PowerExchange dialog box.Organizing Sources by Map Type in Designer Source metadata imported in Source Analyzer in the PowerCenter Designer using PWXPC is stored into sub-folders based on source type and location. only one will be able to be imported from the same Location. use location names in the PowerExchange dbmover. Since the schema name is not used in the source definition table name. The location value equates to the Location specified in the Import from PowerExchange dialog box and is a user-specified name in the PowerExchange dbmover. Use a different Location name to import data maps and extraction maps If you want to use the same names for both the data map name and the capture registration name. The source_type value equates to the Source Type specified in the Import from PowerExchange dialog box. the PowerEchange data map name is IMS. the resulting extraction map name will be d2reconid. There are some non-relational source types where the schema name is different but map name can be the same for both PowerExchange data map and extraction map (CDC Datamap) created from that data map. then the folder will be called IMS_MVS2.<datamap_name>_<table_name> In this example. Creating multiple NODE= statements 222 Appendix A: Usage Tips and Tricks . if the Location is MVS2 and the Source Type is IMS. To help organize sources in Designer. As a result. the names will be exactly the same when imported in Designer. then you will need to use a different location name in the Import from PowerExchange to place these two source definitions in different folders. lets assume the following are used to create the PowerExchange data map for an IMS database: ♦ ♦ ♦ The IMS database is called IMS1T01 and this is used as the PowerExhange Data Map Name A segment in that database results in a table in the data map called IMSSEG1 The PowerExchange Schema Name used when creating the data map is IMS The PowerExchange map name (in the NRDB2 form) is constructed as follows: <schema_name>.

cfg and use this as the Location when importing the IMS extraction map. This strategy of separating extraction maps from regular relational and non-relational source metadata can be a useful way of organizing source metadata in Designer. In this example.(location names) for the same listener is perfectly acceptable. it will be stored in a sub.folder called IMS_CDCMAPS. if you create a NODE called CDCMAPS in the dbmover. Organizing Sources by Map Type in Designer 223 .

and Real-Time connection. if the RDBMS logs are used directly for extraction and they does not support this selective column capture.. You can also use the simple form with multi-record source data maps which then causes that filter to be applied to all records. This includes regular data columns and PowerExchange-generated columns such as DTL__CAPX columns.<group name2>=<filter condition2>. However. This more complex form of the syntax allows you to use different filters for different record types or the same filter for only some of the record types in a multi-record source. change indicator columns (DTL__CI) and before image columns (DTL__BI). it is possible to filter data at the source so only the relevant rows are sent from PowerExchange to the PowerCenter session. For example. for certain source types.. The filters specified are then included in the WHERE clause sent to PowerExchange.<filter condition2>.. you want to read all of the columns in a table for a specific customer. For multi-record non-relational data map sources. then the row will be extracted even if none of the columns of interest have changed (e. there is a more complex form of the syntax: <group name1>=<filter condition1>. relational tables. additional or all columns are registered for capture because other extractions require them.g. ♦ ♦ In these types of cases. There are two forms of the filter syntax. The source type is one where either PowerExchange itself or the RDBMS will only capture changes based on columns of interest. 224 Appendix A: Usage Tips and Tricks . Proper SQL syntax should be followed for these overrides to prevent SQL failures. There are many reasons why you might want to do this. or single record non-relational data maps: <filter condition1>. VSAM and IMS). You only want to extract columns with a specific value. It is possible.. Change.. Some examples of scenarios in which this capability is useful are: ♦ ♦ With some source types you cannot limit change capture changes based on only certain columns changing (e. This can be done with sources using a PWXPC Batch.Filtering Source Data using PWXPC Using PWXPC... The simplest form is for single record sources such as CDC data maps. The SQL filter specified can specify any type of column that exists in the source mapping.g. However.. DB2/400). you can use the source Filter Override attribute in the Session Properties to filter the source data. to create capture registrations in PowerExchange which only register specific columns (as opposed to all of them).

the change indicator for the ACCOUNT field which is called DTL__CI_ACCOUNT: Figure A-1. V07C_RECORD_LAYOUT. The filter contains the group-name filter syntax in order to filter data records for the first two records.The following example shows how to use the PowerExchange Change indicator columns (DTL__CI_column) to filter changed data specifically. The SELECT statements for the two records specified in the Filter Overrides attribute will also have WHERE clauses for their specific filters. there will be four SELECT statements created by PWXPC. Filtering Source Data using PWXPC 225 . and V07D_RECORD_LAYOUT. No filtering is done on the other two records. The group names for the four records are: V07A_RECORD_LAYOUT. Filter Overrides: Single-Record Filter In the following example. V07B_RECORD_LAYOUT. The filter specified is in the Filter Overrides attribute is: V07A_RECORD_LAYOUT=V07A_RECORD_KEY=1.V07B_RECORD_LAYOUT=V07B_RECORD_KEY=2 Because there are four records in the multi-record data. the multi-record VSAM source contains four records which each have unique field names.

Filter Overrides: Multi-Record Filter Records for V07A_RECORD_LAYOUT and V07B_RECORD_LAYOUT will be filtered whereas the other two records in the file will not be. 226 Appendix A: Usage Tips and Tricks .The Mapping tab for this example is as follows: Figure A-2.

Submit any type of MBS Batch JOB for which waiting for the completion and returning a set of messages is required. refer to the PowerExchange Utilities Guide. Which you choose depends upon what you want to do. Command tasks can either be stand-alone tasks or pre/post session commands. There are advantages in using a stand-alone command task for repeatable functions as it only needs to be coded once and can then be used by numerous workflows. Notify a MVS-based job scheduler that the workflow is starting or ending. One option of this utility is the SUBMIT option which provides the ability to submit a MVS batch job remotely. see the PowerCenter Workflow Administration Guide. This is useful for database types for which PowerCenter does not support truncate. On the other hand. This utility can be invoked in PowerCenter workflows using PowerCenter Command Tasks. such as Adabas. Some job schedulers provide batch posting utilities and they can be utilized using DTLREXE to submit a batch job. For detailed information on the syntax of the DTLREXE utility PROG=SUBMIT statements. Unload a database to a flat file so it can then be used in a session to load another database. ♦ ♦ ♦ Using DTLREXE to Submit MVS Batch Jobs 227 . it is possible to easily configure a session to fail if a pre-session command task fails.Using DTLREXE to Submit MVS Batch Jobs PowerExchange provides a utility program called DTLREXE which can be used to cause remote execution of a program on another platform running PowerExchange. Cleanup DB2 bulk load files when the session completes successfully. Some examples of the type of tasks that can be performed using DTLREXE PROG=SUBMIT are: ♦ ♦ Truncate a database table prior to loading data into it in a session. For more information about commands tasks and preand post-session commands.

wait) which means that the DTLREXE will wait for the job to complete. in member DTLREXE.DTLREXE In this example.The following example shows how to setup a DTLREXE PROG=SUBMIT command as a pre-session command: Figure A-3. In the “Error Handling” section of the Config Object. will cause the session to wait until this pre-session command completes. Note: Ensure that the JOB submitted through DTLREXE includes the appropriate DTLNTS steps if WAIT mode is requested. in turn. The PowerExchange RUNLIB. either PrevTaskStatus 228 Appendix A: Usage Tips and Tricks . that is. then there are no session configuration options to check for success or failure. you will need to use one of the taskspecific workflow variables available in the Workflow Manager. If you are using a stand-alone command task to submit a batch JOB using DTLREXE. the DTLREXE command specifies mode=(job. This. If you want to test the status of the command task in the following session. contains sample JCL to be used with DTLREXE that includes the required DTLNTS steps. you can specify how to handle errors for pre-session commands in the On Pre-session command task error field. Pre-Session Command .

DTLREXE For additional information on link conditions and the expression editor. refer to the “Working with Workflows” chapter in the PowerCenter Workflow Administration Guide. as shown below: Figure A-5.DTLREXE Link Condition The link condition is created by double-clicking on the link between the DTLREXE command task and the s_bulk_db2demo123_db2demoabc session to which it is connected. Command Task Expression Editor . These variables can be used in link conditions to test the status of tasks in a workflow.or Status. For example: Figure A-4. Workflow Link Condition . Using DTLREXE to Submit MVS Batch Jobs 229 . This will invoke the Expression Editor which allows you to add the test to ensure that the DTLREXE command task succeeded.

To pre-allocate a sequential or GDG data set in a session: 1.Creating Sequential and GDG Data Sets When writing to a sequential or Generation Data Group (GDG) data set using PowerExchange. 4. right-click on the appropriate task in either Task Developer or in your workflow in Workflow Designer. Select the Mappings tab. Some applications require that a new sequential data set or generation of a GDG data set be created each time a session or workflow runs. you can ensure that a new generation is created each time you run a session (task) in a workflow by following the procedure below. even if that data set is empty. 3. Click OK. the data set is created when the first record to be written is received. In the Pre SQL attribute in the Session Level Properties for the target. If there is no data written to the target. In Workflow Manager. then the data_set_name should be gdg_base_name(+1) to create a new generation. If you are using sequential or GDG data sets on MVS with PowerExchange and have this requirement. 5. then PowerExchange will not created the new data set. The Edit Tasks dialog box is displayed. Select Tasks > Edit. 230 Appendix A: Usage Tips and Tricks . enter the following: <CMD>CREATEFILE FN=“data_set_name” If this is a GDG data set. 2.

the new generation of the GDG is created in addition to the normal processing of the workflow. The allocation parameters used to create the data set are specified in the DBMOVER configuration used by the PowerExchange Listener. Creating Sequential and GDG Data Sets 231 .gdg: Figure A-6.File Create Pre-SQL Command Note: When using this procedure for GDG data sets. Session Mapping Tab .The following example show a CREATEFILE command for a new generation of GDG data set my. When you run the workflow. the GDG base name specified must exist and GDGLOCATE=Y must be specified in your PowerExchange DBMOVER configuration file on the MVS platform.

AS400 These value override the equivalent parameters specified in the DBMOVER configuration file. Refer to the “Configuration File Parameters” chapter of PowerExchange Reference Manual for further information on these parameters. Any values not specified use either those specified in DBMOVER or the standard PowerExchange defaults. The parameters are: Parameter FN Platform All Description File name to be created. 232 Appendix A: Usage Tips and Tricks . Space allocation parameters in the format: SPACE=(u. Generally. Unit type.The CREATEFILE command has a number of parameters. Only one of PWD or EPWD is required. Any number of these can be specified. Release unused allocated space on CLOSE. the file name must be in double quotes (“). This parameter is required if your Listener is running with user security (SECURITY=1 or 2).s is secondary space allocation value Block size.u is units (T for tracks and C for cylinders) .p. Encrypted password for the userid specified in UID.s) where: .p is primary space allocation value . Record format. If specifying a relative GDG data set name. Password for the userid specified in UID. Valid value is Y. This parameter is required. AS400 only MVS. Logical record length. this is only required for GDG data sets which are not SMS-managed. The parameters and their values are separated with a space in the command. Userid. Model DSCB to be used for the file creation. UID PWD EPWD MODELDCB SPACE MVS / AS400 only MVS / AS400 only MVS / AS400 only MVS only MVS only BS RELEASE VOLSER UNIT LRECL RECFM MVS only MVS only MVS only MVS only MVS. Volume serial.

Using Event Table Processing to Shutdown Sessions 233 .Using Event Table Processing to Shutdown Sessions PowerExchange provides the capability to terminate real time sessions when an update is made to a specific table called an event table.

234 Appendix A: Usage Tips and Tricks .

240 Using Code Pages. 239 Reading and Writing Binary Data in PowerExchange Client for PowerCenter. 241 235 . 237 Relational Datatypes.Appendix B Datatypes and Code Page Reference This appendix covers the following topics: ♦ ♦ ♦ ♦ ♦ Overview. 236 PowerExchange and Transformation Datatypes.

see the PowerCenter Designer Guide.Overview PowerCenter uses the following datatypes when reading source data. For more information about transformation datatypes. Native datatypes appear in source and target definitions. Transformation datatypes. Generic datatypes that appear in transformations. transforming the data. The PowerCenter Server uses the datatypes to move data across platforms. and writing target data: ♦ ♦ Native datatypes. Specific to the source and target databases or PowerExchange. 236 Appendix B: Datatypes and Code Page Reference .

but you cannot perform transformations on binary data. see the PowerExchange documentation. CHAR DATE DOUBLE FLOAT NUM8 NUM8U NUM16 NUM16U NUM32 NUM32U 10 10 18 7 3 3 5 5 10 10 String Date/Time Double Double Small Integer Small Integer Small Integer Integer Integer Double PowerExchange and Transformation Datatypes 237 . with precision to the second. Precision of 10 and scale of 0 Integer value. Precision of 15 digits Double-precision floating-point numeric value. Jan 1.600 characters Fixed-length or varying-length string. PowerCenter does not support binary data for COBOL or flat file sources. 9999 AD Combined date/time value.600 bytes You can pass binary data from a source to a target. PowerExchange and Transformation Datatypes PowerExchange BIN Precision 10 Transformation Binary Range 1 to 104. Precision of 5 and scale of 0 Integer value. 1753 AD to Dec 31.PowerExchange and Transformation Datatypes PowerExchange datatypes display for non-relational source definitions. The datatypes of the fields in the source definition match the datatype for the corresponding field in the data map. Precision of 10 and scale of 0 Integer value. Table B-1 compares PowerExchange datatypes and the transformation datatypes that display in the Application Multi-Group Source Qualifier transformation: Table B-1. Precision of 5 and scale of 0 Integer value. For information about how native non-relational database datatypes map to PowerExchange datatypes. Precision of 5 and scale of 0 Integer value. 1 to 104.857. which display in the Application Multi-Group Source Qualifier for the non-relational source and other transformations in a mapping. You import nonrelational source definitions from a PowerExchange data map. These datatypes map to PowerCenter transformation datatypes. Precision of 15 digits Double-precision floating-point numeric value. Precision of 15 digits Double-precision floating-point numeric value.857.

If you pass a value with negative scale or declared precision greater than 28. Precision 1 to 28 digits.857. If you pass a value with negative scale or declared precision greater than 28. If you pass a value with negative scale or declared precision greater than 28. Scale must be less than or equal to precision. the PowerCenter Server converts it to a double. Scale must be less than or equal to precision. If you pass a value with negative scale or declared precision greater than 28. NUM64U 19 Decimal NUMCHAR PACKED 15 String Decimal TIME TIMESTAMP UPACKED 5 5 15 Date/Time Date/Time Decimal UZONED 15 Decimal VARBIN 10 Binary VARCHAR ZONED 10 15 String Decimal 238 Appendix B: Datatypes and Code Page Reference . scale 0 to 28 Decimal value with declared precision and scale. the PowerCenter Server converts it to a double. with precision to the second. Scale must be less than or equal to precision. 9999 AD Combined date/time value. 1753 AD to Dec 31. scale 0 to 28 Decimal value with declared precision and scale. scale 0 to 28 Decimal value with declared precision and scale.600 characters Fixed-length or varying-length string.857. with precision to the second. 1 to 104. Precision 1 to 28 digits. If you pass a value with negative scale or declared precision greater than 28. the PowerCenter Server converts it to a double. If you pass a value with negative scale or declared precision greater than 28. Precision 1 to 28 digits. the PowerCenter Server converts it to a double. Precision 1 to 28 digits. the PowerCenter Server converts it to a double. Precision 1 to 28 digits. Jan 1.857. scale 0 to 28 Decimal value with declared precision and scale.600 bytes You can pass binary data from a source to a target. 9999 AD Combined date/time value. Scale must be less than or equal to precision. PowerExchange and Transformation Datatypes PowerExchange NUM64 Precision 19 Transformation Decimal Range Precision 1 to 28 digits. PowerCenter does not support binary data for COBOL or flat file sources. 1 to 104. Jan 1. Scale must be less than or equal to precision. 1753 AD to Dec 31. scale 0 to 28 Decimal value with declared precision and scale.Table B-1.600 characters Fixed-length or varying-length string. 1 to 104. Scale must be less than or equal to precision. scale 0 to 28 Decimal value with declared precision and scale. but you cannot perform transformations on binary data. the PowerCenter Server converts it to a double.

DB2/400. It also supports the same Oracle datatypes that PowerCenter supports and the same SQL Server datatypes that PowerCenter supports. and DB2/UDB that PowerCenter supports for DB2.Relational Datatypes PowerExchange Client for PowerCenter supports the same datatypes for DB2/390. Relational Datatypes 239 . see the PowerCenter Designer Guide. For more information about PowerCenter datatypes.

Reading and Writing Binary Data in PowerExchange Client for PowerCenter If you read binary data from any source. the data cannot be larger than 32 KB. 240 Appendix B: Datatypes and Code Page Reference . Otherwise. or if you write binary data to a DB2/390 or DB2/400 target using PowerExchange Client for PowerCenter. the PowerCenter Server truncates the data.

see the PowerCenter Administrator Guide. If you configure the PowerCenter Server for relaxed code page validation this is not the case. For more information about code pages. If you configure the PowerCenter Server for code page validation. You can select any code page supported by PowerCenter for the target. For more information about configuring the code page in connection objects.Using Code Pages When you configure a connection object in the Workflow Manager. the source code page must be a code page that is a subset of the target code page. refer to Table 4-11 on page 102 which describes the connection attributes you configure for Oracle real-time mode application connections. select a code page for the connection. Using Code Pages 241 .

242 Appendix B: Datatypes and Code Page Reference .

Appendix C Troubleshooting This chapter covers the following topics: ♦ Troubleshooting. 244 243 .

I want to import a DB2/400 source definition.cfg) CAPI_CONNECTION statement. When you rerun the session. For more information. Clear the PMServer 6. This can occur if EOF=Y is specified in the PowerExchange configuration file (dbmover.X Joiner Source Order Compatibility option on the Compatibility and Database tab in the Informatica Server Setup. When you set EOF=Y. As a result. As a result.0. My session seems to be processing the pipelines serially. If there are no other error messages in the session log. The Integration Service may be configured to process master and detail pipelines sequentially as it did in versions prior to 7. However. the Integration Service will process pipelines concurrently. The session failed with a plug-in error: MAPPING> SDKS_38007 Error occurred during [initializing] reader plug-in #30nnnn. PowerExchange returns an EOF (which stops the session) when it reaches the end of the change stream as determined at the time the session starts reading from it.Troubleshooting When I go into Designer. I set the Idle Time session condition to -1. You can receive this error on UNIX when there is no PWX_HOME environment variable set to the PowerExchange installation directory. the session completed with the following message: Idle Time limit is reached. The session failed with an error stating that the PowerExchange message repository cannot be loaded. Set the PWX_HOME environment variable to the PowerExchange installation directory. Use the AS400 DSPRDBDIRE command to see a list of databases on the AS/400 machine. see KnowledgeBase Article # 15346. This is a generic message indicating the PWXPC encountered an error. This message can also occur if the connection with PowerExchange is stopped using the PowerExchange STOPTASK command. Review the session log for other messages indicating what the problem is. but need to determine the name of the DB2/400 database on the AS/400 machine. This can happen when PowerExchange Client for PowerCenter plug-ins are installed but cannot be loaded for various reasons like incorrect releases of PowerExchange installed or PATH problems. it reads data from each source in change and realtime modes sequentially. the PowerCenter session completes instead of continuing to run. check the PowerExchange logs on both the Integration Service platform and the Listener platform. 244 Appendix C: Troubleshooting . I get messages about failures to load DLLs.

or DELETE). INSERT is the default operation.'D'. If you want to have all changes processed as INSERTs regardless of the DTL__CAPXACTION field. you must code an Update Strategy specifying DD_INSERT in the Update Strategy Expression field. the DTL__CAPXACTION field is automatically acted upon when processing changed data. you would code: DECODE(DTL__CAPXACTION.DD_REJECT) When using PWXPC.I want to read all of the changes I've captured and have them be inserts into a staging area.'U'. If you want to apply the changes to the target using the same operation as done on the source (INSERT.DD_INSERT.DD_DELETE.'I'. In the Update Strategy Expression field. you need to explicitly include an Update Strategy in the mapping to make this happen by testing the DTL__CAPXACTION field. How do I do this? When using PowerExchange ODBC to read captured changes. UPDATE.DD_UPDATE. Troubleshooting 245 .

246 Appendix C: Troubleshooting .

248 Messages 10000 through 10099. 258 247 . 249 Messages 11000 through 11099.Appendix D PWXPC .Messages This appendix includes the following topics: ♦ ♦ ♦ ♦ Overview. 256 Messages 12000 through 12099.

see PowerExchange Message Reference. Messages from PowerExchange and PowerCenter also display in conjunction with these messages. For information about PowerCenter messages.Overview The PowerExchange Client for PowerCenter issues informational messages about setup and operation as well as messages when errors are detected. All of the PWXPC messages are prefixed with PWXPC_ followed by a 5 digit message number. For information about PowerExchange messages. 248 Appendix D: PWXPC .Messages . see PowerCenter Troubleshooting Guide.

Return code: return_code Cause: Action: Internal error. PWXPC_10002 reader cannot get connection reference for the Source Qualifier instance qualifier_name. PWXPC_10003 reader failed to initialize the source for the Source Qualifier instance qualifier_name. Contact Informatica Global Customer Support. Error message(s): additional_messages Cause: Action: Internal error. PWXPC_10005 PowerExchange AllocEnv failed Cause: Action: Internal error. Contact Informatica Global Customer Support. Messages 10000 through 10099 249 . Cause: Action: Internal error. PWXPC_10010 Cannot get metadata extension extension_name. Cause: Action: Internal error. Return code: return_code. Contact Informatica Global Customer Support. PWXPC_10004 Cannot get connection property attribute_name.Messages 10000 through 10099 PWXPC_10001 reader cannot get the Source Qualifier instances from the mapping. PWXPC_10008 Cannot connect to the PowerExchange Listener. Cause: Action: Internal error. Contact Informatica Global Customer Support. Cause: Action: The Integration Service could not initialize the session. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. PWXPC_10006 PowerExchange AllocConnect failed. Contact Informatica Global Customer Support. PWXPC_10007 PowerExchange AllocConnect failed. See the additional error message for more information. See the additional error message for more information. Cause: Action: Internal error. Cause: Action: The Integration Service could not connect to the PowerExchange Listener.

Cause: Action: PowerExchange Listener error. PWXPC_10013 PowerExchange Execute failed. PWXPC_10016 PowerExchange Group Fetch failed. Contact Informatica Global Customer Support. PWXPC_10015 PowerExchange Bind Col failed. Check the additional error message for more information. Cause: Action: The specified connection attribute does not contain a value. PWXPC_10020 Connected to the PowerExchange Listener at location [location]. PWXPC_10017 PowerExchange Fetch failed.PWXPC_10011 PowerExchange AllocStmt failed. Return code: return_code. PWXPC_10012 PowerExchange Prepare failed. Return code: return_code. Check the additional error message for more information. Cause: Action: PowerExchange Listener error. Return code: return_code. PWXPC_10014 PowerExchange SetRow count failed. Check the additional error message for more information.Messages . with User name [user]. Return code: return_code. Check the additional error message for more information. compression [Y|N]. Return code: return_code. Cause: Action: PowerExchange Listener error. encryption type [encryption]. Check the additional error message for more information. Check the additional error message for more information. Cause: Action: PowerExchange Listener error. Cause: Action: Internal error. pacing Size [value] and interpreting rows as [Y|N] Cause: 250 Connection established with PowerExchange Listener. Cause: Action: PowerExchange Listener error. PWXPC_10018 Reader encountered an error during buffer flush. Appendix D: PWXPC . PWXPC_10019 Connection parameter connection_attribute is missing. encryption level [level]. Return code: return_code. Specify a value for the connection attribute. Check the additional error message for more information. Cause: Action: PowerExchange Listener error. Cause: Action: PowerExchange Listener error. Return code: return_code.

Contact Informatica Global Customer Support.Action: Informational. Cause: Action: Internal error. PWXPC_10022 The data map is overwritten to [map_name] in the session properties for the Source Qualifier [qualifier_name] Cause: Action: The data map name in the source definition Metadata Extensions has been overridden in the session properties to the value shown. PWXPC_10021 The schema is overwritten to [schema] in the session properties for the Source Qualifier [qualifier_name] Cause: Action: The source schema in the source definition Metadata Extensions has been overridden in the session properties to the value shown. PWXPC_10028 reader cannot get the value of the attribute attribute_name for the Source Qualifier qualifier_name. PWXPC_10025 Cannot get the field projection information for the source source_name. Informational. Informational. Contact Informatica Global Customer Support. PWXPC_10024 Partition [partition_number] initialized successfully Cause: Action: The partition has successfully initialized. Cause: Action: Internal error. Associate only one source definition with a source qualifier. Contact Informatica Global Customer Support. Messages 10000 through 10099 251 . Informational. PWXPC_10023 reader prepared SQL statement [SQL_statement] for the group [group] in Source Qualifier [qualifier_name] for partition partition_number Cause: Action: The prepared SQL statement for the source qualifier is shown. PWXPC_10027 The Source Qualifier [qualifier_name] has more than one source instance associated with it Cause: Action: Multiple source definitions are connected to the same source qualifier. Informational. Cause: Action: Internal error. PWXPC_10026 reader cannot get the source list for the Source Qualifier qualifier_name.

PWXPC_10032 An invalid extraction map name was provided for the source source_name of Source Qualifier qualifier_name. Error code: return_code. Error code: return_code. Specify a valid extraction map name. 252 Appendix D: PWXPC . Cause: Action: The Integration Service could not extract data from the PowerExchange Listener. Cause: Action: Internal error. PWXPC_10034 dispatcher cannot fetch changed data from the PowerExchange Listener. PWXPC_10042 The metadata extension attribute 'AccessMethod' [access_method_value] is not valid for the source source_name. Contact Informatica Global Customer Support. See the additional error message for more information. Cause: Action: The Integration Service could not connect to the PowerExchange Listener. Specify an extraction map in the session properties. Cause: Action: Internal error. PWXPC_10036 dispatcher cannot connect to the PowerExchange Listener. Cause: Action: The extraction map in the session properties for the specified source is missing. Error code return_code. The XML file may have been modified. access_method_value.Messages . or Cause: Action: The extraction map name is not a valid extraction map name or is not the correct name for the source.PWXPC_10029 reader cannot get the fields for the source source_name. See the additional error message for more information. Cause: Action: Internal error. Contact Informatica Global Customer Support. Cause: The value for the metadata extension attribute ‘AccessMethod’. is invalid in the XML file. Contact Informatica Global Customer Support. PWXPC_10039 dispatcher cannot bind the columns for the transaction statement. Error code: return_code. PWXPC_10037 dispatcher cannot create the transaction statement.

Cause: The Integration Service could not extract changed data from the source because it could not read the restart tokens from the specified restart token file. Cause: The connection attribute values for the connections you specified for the sources in the session properties are not the same. Messages 10000 through 10099 253 . the connection attribute values of these connections must be identical to run a session in change or real-time mode. Cause: Action: Internal error. In the PowerExchange Navigator. Specify an extraction map for the source in the mapping. Contact Informatica Global Customer Support. Action: PWXPC_10055 dispatcher cannot write restart tokens to the restart token file file_name. Action: PWXPC_10049 Unable to find connection for CDC Change/Live reader. See the additional error message for more information. Specify a group name that matches a group name in the source. PWXPC_10045 The Extraction Map Name map_name is not valid for source source_name. Multiple connections are not required when running in change or real-time mode. ensure that each registration for each extraction map specified uses the same condense method. Cause: The Integration Service could not extract changed data from the source because it could not read the restart tokens from the specified restart token file. Cause: Action: The specified extraction map is not an extraction map for the source in the mapping.Action: Import the repository object from a new XML file. Cause: Action: The group does not match any group names in the source. PWXPC_10048 Connection parameters for different sources don't match. Cause: Action: The mapping has multiple sources but their capture registrations do not all specify the same condense method. PWXPC_10054 dispatcher cannot read restart tokens from the restart token file file_name. PWXPC_10046 Condense method method_name1 doesn't match with condense method method_name2. If you specify connections for each source. PWXPC_10053 The group name group_name in the filter filter is invalid. Specify a connection for the first source and specify None for the rest of the sources. Avoid editing the XML file before importing.

PWXPC_10064 Reader partition partition_name failed to cache the restart token. Contact Informatica Global Customer Support. Error code error_code. Contact Informatica Global Customer Support. Cause: Action: The Integration Service could not open the restart token file. PWXPC_10057 dispatcher cannot bind the restart token control columns for the transaction statement. 254 Appendix D: PWXPC . Cause: Action: Internal error. See the additional error message for more information. Contact Informatica Global Customer Support. Contact Informatica Global Customer Support. PWXPC_10062 Restart token file attribute cannot be fetched for connection connection_name. PWXPC_10058 Cache folder attribute cannot be fetched for connection connection_name. Cause: Action: Internal error. PWXPC_10063 Reader partition partition_name failed to flush to the recovery cache: error_message. Contact Informatica Global Customer Support.Action: See the additional error message for more information. Cause: Action: Internal error. PWXPC_10056 dispatcher cannot open the restart token file file_name. Cause: Action: Internal error. Cause: Internal error. PWXPC_10059 Recovery cache folder cache_folder_name specified for connection is invalid. Contact Informatica Global Customer Support. Cause: Action: Internal error. Cause: Action: Internal error.Messages . PWXPC_10060 CDC Reader dispatcher failed to register for recovery. Cause: Action: Internal error. Contact Informatica Global Customer Support. PWXPC_10061 Restart token folder attribute cannot be fetched for connection connection_name.

Because the Integration Service may have committed some of the data to the target before the initial session failed. the target database may receive duplicate records. Run the session again. PWXPC_10068 dispatcher cannot convert the restart tokens read from the restart token file file_name. PWXPC_10069 dispatcher cannot convert the restart tokens read from the recovery cache file. because the recovery cache file was modified or deleted. Verify that the information in the restart token file is valid. PWXPC_10065 Reader partition partition_name failed to close checkpoint checkpoint. Ensure that the restart token file folder you specify in the connection properties matches a restart token file folder on the PowerExchange Listener. PWXPC_10066 reader reader failed to enable recovery for the Source Qualifier qualifier_name. the target database may receive duplicate records. and may have added some invalid characters. PWXPC_10067 dispatcher cannot read restart tokens from the recovery cache file. Messages 10000 through 10099 255 . Contact Informatica Global Customer Support. Cause: Action: Internal error. Cause: Action: The restart token file folder specified for the connection does not match a restart token file folder name on the PowerExchange Listener. Because the Integration Service may have committed some of the data to the target before the initial session failed. Contact Informatica Global Customer Support. PWXPC_10087 RestartToken File Folder token_folder_name specified for connection is invalid. because the recovery cache file may have been modified. Cause: Action: The Integration Service cannot run the session in recovery mode. Cause: Action: Internal error. Cause: Action: The Integration Service cannot run the session in recovery mode.Action: Contact Informatica Global Customer Support. Cause: Action: Internal error. Error Code <error code>. PWXPC_10073 dispatcher cannot bind restart tokens. Run the session again. Contact Informatica Global Customer Support. Cause: Action: You edited the restart token file.

System error message. Informational. errno. message. PWXPC_11003 Session override File Name is being used as File List Cause: The File Name Override session property specifies a file name and the File list File session property has been selected. System error message. has been omitted. PWXPC_11005 dispatcher cannot open the restart token file [file_name]. Action: PWXPC_11006 dispatcher failure writing to restart token file [file_name]. and the system error number. errno. Correct the error indicated in the system error message and error code and then restart the task. Informational. System Error message [message] code [errno] Cause: PWXPC encountered an error reading from the restart token file. file_name. message. Informational. The required session attribute must be supplied. message. System Error message [message] code [errno] Cause: PWXPC encountered an error attempting to open the restart token file. indicates the failure reason. PWXPC_11002 Session override File Name [file_name] is being used Cause: Action: The File Name Override session property specifies file name file_name. errno. and the system error number. The File Name Override file name is used as the file list file name. System Error message [message] code [errno] Cause: PWXPC encountered an error writing to the restart token file. System error message. Action: PWXPC_11004 Session override IMS Unload file name [unload_file] is being used Cause: Action: The IMS Unload File Name session property specifies file name unload_file. 256 Appendix D: PWXPC . session_attribute. indicates the failure reason. file_name. Action: PWXPC_11007 dispatcher failure reading from restart token file [file_name]. indicates the failure reason. file_name.Messages . and the system error number. Correct the error indicated in the system error message and error code and then restart the task.Messages 11000 through 11099 PWXPC_11001 Cannot get session attribute session_attribute Cause: Action: A required session attribute.

System error message. PWXPC_11008 dispatcher failure deleting restart token file [file_name]. and the system error number. System Error message [message] code [errno] Cause: PWXPC encountered an error deleting the restart token file. Correct the error indicated in the system error message and error code and then restart the task. Action: Messages 11000 through 11099 257 . indicates the failure reason. message. errno. file_name.Action: Correct the error indicated in the system error message and error code and then restart the task.

PWXPC_12007 Invalid column specification for insert statement Cause: Action: Invalid column specification detected for insert statement. PWXPC_12002 Requested driver for target [target] not found Cause: Action: An invalid target driver was requested. PWXPC_12004 An error occurred accessing the target instance object Cause: Action: An error occurred accessing the target instance object. 258 Appendix D: PWXPC . Correct the SQL. Report error to Informatica Global Customer Support. PWXPC_12006 Missing or invalid values clause detected for insert statement Cause: Action: Missing or invalid values clause detected for insert statement. Report error to Informatica Global Customer Support. See previous messages for cause Cause: Action: The session failed to validate. Correct the SQL. Correct the SQL. PWXPC_12008 Invalid column name [column_name] detected for current table in user SQL Cause: Action: Invalid column name detected for table in user SQL.Messages 12000 through 12099 PWXPC_12001Session validation failed. Report error to Informatica Global Customer Support.Messages . PWXPC_12003 Requested driver for group [group] not found Cause: Action: An invalid group driver was requested. PWXPC_12005 An error occurred parsing a user supplied SQL statement [sql_stmt] Cause: Action: An error occurred parsing a user supplied SQL statement. Correct the SQL. See previous messages for the cause of the error.

165 B batch mode configuring sessions 127 Before image Flexible transactions 182 bulk load configuring 85 C CAPX access method 6 CAPXRT access method 6. 163 restart token file 160 stopping 114. 69 CDC datamap 133. 161 See also extraction map source definitions CDC sessions adding source 169 recovery example 172 removing source 169 restart 115. 168 CDEP restart 165 change data capture See change mode See also real-time mode Change Indicator Flexible transactions 182 change mode Condense 5 configuring connections 115 configuring sessions 133 code pages See also PowerCenter Installation and Configuration Guide configuring 241 supported code pages 241 compression configuring 106 Condense 259 . 6. 7 CBLO See constraint-based loading CDC data group source 5.Index A access method CAPX 6 CAPXRT 6. 115. 7 Application Multi-Group Source Qualifiers See source qualifiers application name restart points 115. 149.

68 VSAM 4. 79 datatypes 239 real-time mode application connections 87 260 Index F filelist description 127 flexible key transformations group source 185 Flexible Target Key Custom transformations 176 G group source 68 CDC data 5. 59 DTL__CAPXRESTART1 161 DTL__CAPXRESTART2 161 DTLUAPPL 161. 68 . 165 example 166 DTLUTSK 114. 69. 6. 168 E editing Source Qualifier transformations 72 encryption configuring 106 enhanced restart recovery processing 171 environment SQL See also PowerCenter Workflow Administration Guide configuring error messages PWXPC 248 extraction map 133. 161 extraction map source definitions editing 59 viewing 57 D data maps non-relational source definitions 39 viewing in the source definition 48 Datacom batch mode application connections 90 change mode application connections 91 datatypes DB2/390 239 DB2/400 239 overview 236 PowerExchange 237 transformation 237 transformation datatypes in source qualifiers 72 DB2 creating source definitions 21 creating target definitions 21 DB2/390 change mode application connections 87 configuring bulk load properties 85 connection types 78. 68 sequential 4. 208 connections configuring 81 list by source type 78 list by target type 79 constraint-based loading FullCBLOSupport 134 creating DB2 source definitions 21 DB2 target definitions 21 IMS source definitions 39 Oracle source definitions 30 source qualifiers 72 Sybase source definitions 34 VSAM source definitions 39 custom property FullCBLOSupport 134 DB2/400 change mode application connections 87 connection types 78. 208 workflows 126. 185 flexible key transformations 185 multiple records 4.change mode 5 UOW Cleanser 5. 79 datatypes 239 real-time mode application connections 87 default restart points 155 DTL__CAPXACTION 38. 50. 6 configuring code pages 241 compression 106 connections 81 encryption 106 pacing size 107 sessions 126.

152 PowerExchange performance 107 PowerExchange Change Data Capture Flexible transformations 180 PowerExchange Client for PowerCenter performance 3 PowerExchange Configuration File dbmover. 97. 152 application name 115. 92. 165 Index 261 N non-relational source definitions editing 50 editing metadata extensions 50 viewing data map details 48 viewing metadata extensions 58 non-relational sources configuring batch mode sessions 127 non-relational target definitions editing 50 editing metadata extensions 50 O Oracle connection types 78 creating source definitions 30 real-time application connections 97. 116. 91.cfg 14 PWXPC error messages 248 L loading constraints 134 logger token 161 M metadata extensions editing 50 viewing 49 viewing for non-relational source definitions 58 R Real-time Flush Latency configuring 117 real-time mode configuring Real-time Flush Latency 117 configuring sessions 133 recovery creating the tables 159 enhanced restart 171 example 172 PM_REC_STATE table 150 PM_RECOVERY table 149 PM_TGT_RUN_ID table 149 state file 151 tables 149 relational source definitions editing 37 relational sources configuring batch mode sessions 130 relational target definitions editing 37 relational targets configuring sessions 140. 98. 102 . 103 $PMRootDir/Restart 87. 92. 97. 98. 102. 116. 142 restart $PMRootDir/Cache 88. 98. 102. 103 IDMS batch mode application connections 90 change mode application connections 91 IMS batch mode application connections 90 change mode application connections 91 connection types 78 datatypes 237 real-time mode application connections 91 P pacing size configuring 107 pipeline partitioning See also PowerCenter Workflow Administration Guide batch mode 208 description 126. 91.I Idle Time configuring 88. 103 Restart 87. 92. 208 loading to targets 208 $PMRootDir Cache 88.

160 restart token file folder 116 RESTART1 161 RESTART2 161 sequence token 161 state file 151 tokens 150. 156 logger token 161 null restart tokens 156 operation 163 overview 149 PM_REC_STATE table 150 restart token file 116. extraction maps 57 262 Index V VSAM batch mode application connections 90 change mode application connections 91 connection types 78 datatypes 237 extracting data from multiple files 127 group source 68 real-time mode application connections 91 W workflows overview 126. 6 UOW Count configuring 116 update strategy 38. 103 Real-time Flush Latency 117 sessions overview 126. 59 S sequence token 161 sequential data sets group source 68 session conditions Idle Time 88. relational 37 IMS 39 viewing metadata extensions 49 viewing. 92. 208 . non-relational 50 editing. 163 CDEP 165 DTL__CAPXRESTART1 161 DTL__CAPXRESTART2 161 DTLUAPPL 161. 168 Sybase creating source definitions 34 T target definitions DB2 21 editing metadata extensions 50 editing non-relational 50 editing relational 37 viewing metadata extensions 49 transformations affecting row id 134 update strategy 38. 208 source definitions DB2 21 editing metadata extensions 50 editing.CDC sessions 115. 98. 59 U UOW Cleanser Condense 5. 152. extraction maps 59 editing. 50. 165 DTLUAPPL example 166 earliest points 155. 50. 151 restart points defaults 156 earliest 156 null 156 restart token file archiving 172 comment 160 configuring 160 example 162 explicit override 161 special override 161 syntax 160 VSAM 39 working with non-relational source definitions 39 Source Qualifier transformations See source qualifiers source qualifiers transformation datatypes 72 STOPTASK 114.

Sign up to vote on this title
UsefulNot useful