PWX 861HF14 Message Reference

Message Reference
Informatica PowerExchange
(Version 8.6.1 HotFix 14)
Informatica PowerExchange Message Reference Version 8.6.1 April 2011 Copyright (c) 19982011 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 may be 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 B2B Data Exchange and Informatica On Demand 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. Copyright, Byte Designs Ltd. All rights reserved. This product includes ICU software which is copyright (c) 1995-2003 International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://www-306.ibm.com/software/globalization/icu/license.jsp. The product includes the zlib library copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler. 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 noninfringement, 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-MES-861-0008
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Informatica How-To Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Informatica Multimedia Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Chapter 1: PWX-00100 to PWX-35999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PWX-00100 to PWX-00999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 PWX-01000 to PWX-01999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 PWX-02000 to PWX-02999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 PWX-03000 to PWX-03999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 PWX-04000 to PWX-04999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 PWX-05000 to PWX-05999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 PWX-06000 to PWX-06999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 PWX-07000 to PWX-07999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 PWX-08000 to PWX-08999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 PWX-09000 to PWX-09999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 PWX-10000 to PWX-10999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 PWX-11000 to PWX-11999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 PWX-12000 to PWX-12999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 PWX-13000 to PWX-13999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 PWX-14000 to PWX-14999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 PWX-15000 to PWX-15999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 PWX-16000 to PWX-16999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 PWX-19000 to PWX-19999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 PWX-20000 to PWX-20999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 PWX-21000 to PWX-21999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 PWX-23000 to PWX-23999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 PWX-24000 to PWX-24999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 PWX-25000 to PWX-25999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 PWX-30000 to PWX-30999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 PWX-31000 to PWX-31999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 PWX-32000 to PWX-32999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 PWX-33000 to PWX-33999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 PWX-35000 to PWX-35999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Chapter 2: DTL_BMG003 to DTL_RPS105I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

DTL_BMG003E to DTL_BMG101E: Datacom Low Level Metadata Retrieval . . . . . . . . . . 623
Table of Contents
iii
DTL_DPL002I to DTL_DPL300I: Datacom MUF Real-time Log Processor . . . . . . . . . . . . 624 DTL_DPP001E to DTL_DPP993E: IDMS CDC EDP Log Feeder . . . . . . . . . . . . . . . . . . . 627 DTL_DPS900I to DTL_DPS907I: IDMS Intercept Stub . . . . . . . . . . . . . . . . . . . . . . . . . . 634 DTL_DPW002I to DTL_DPW532I: Datacom MUF Real-time Direct Log Processor . . . . . . 635 DTL_DPX000E to DTL_DPX999E: IDMS CV Exit and Real-time Journal Processor . . . . . 639 DTL_DPZ500I to DTL_DPZ514I: IDMS CDC EDP Log Feeder fakeit (EDM Interface) . . 641 DTL_PRP001E to DTL_PRP302E: Datacom CDC EDP Log Feeder . . . . . . . . . . . . . . . . . 643 DTL_RPC001E to DTL_RPC999E: Datacom and IDMS CDC Dataspace Controller . . . . . 648 DTL_RPS001E to DTL_RPS105I: Datacom MUF Address Space Subtask Exit . . . . . . . . . . 656
Chapter 3: DTL58001 to DTL62591 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

DTL58001R to DTL62569I: Batch VSAM ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Chapter 4: PWXEDM172000 to PWXEDM173002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent . . . . . . . . . . . . . . . 671 PWXEDM172500I to PWXEDM172798I: The PowerExchange Logger . . . . . . . . . . . . . . . . 709 PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) . . . . . . . . 759 PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger . . . . . . . . . . . . . . 772

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities . . . . . . . . . . . . . . . . . . 775

PWXEDM176400E to PWXEDM176437E: CICS/VSAM ECCR . . . . . . . . . . . . . . . . . . . . 785 PWXEDM177000E to PWXEDM177593E: DB2 ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . 792

PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent . . . . . . . . . . . . . . . . 899 PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities . . . . . . . 903

PWXEDM261000I to PWXEDM261010I: The Logger API . . . . . . . . . . . . . . . . . . . . . . . . 907 PWXEDM263000I to PWXEDM263039W: The Log Read API . . . . . . . . . . . . . . . . . . . . . 908
Chapter 9: Return and Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913 IBM Product Return and Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914 Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914 Abend Code U0001: PowerExchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914 Abend Code U0356: Batch VSAM ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 Abend Code U3035: PowerExchange Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 Abend Code U3680: DB2 ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 Return Codes 0 to 12: Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
iv
Table of Contents
Return Codes 1 to 412: Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916 Return Codes 0 to 12: PowerExchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917 Return Code 221: PowerExchange Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917 Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917 Reason Codes xxxx0800 to xxxx081F: Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918 Reason Codes 001 to 255: PowerExchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918 Reason Codes 00000601 to 00004499: Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921 Reason Codes 00000813 to 00001515: Encoded Commands . . . . . . . . . . . . . . . . . . . . 922 Reason Codes 00000C00 to 00000C0E: Common Services . . . . . . . . . . . . . . . . . . . . . . 923 Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger . . . . . . . . . . . . . . . . . . 923 Reason Codes 01440600 to 060906FF: PowerExchange Utilities . . . . . . . . . . . . . . . . . . 940 Reason Codes 01800101 to 01FFFFFF: Change Interface Component . . . . . . . . . . . . . 941 Reason Codes 04050000 to 0812000C0: Circular Queue . . . . . . . . . . . . . . . . . . . . . . . 946 Reason Codes 0A0B0001 to 0A0BFFFF: Log Write API . . . . . . . . . . . . . . . . . . . . . . . . 950 Reason Codes 0A0E0001 to 0A0EFFFF: Log Read API . . . . . . . . . . . . . . . . . . . . . . . . 952 Reason Codes 10000001 to 1007FFFF: DB2 ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . . 954 Reason Codes 00000004 to 00000054: Chainer Module (EDMQMGR0) . . . . . . . . . . . 955
Chapter 10: PWXPC Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957 Messages 10000 through 10099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957 Messages 11000 through 11099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966 Messages 12000 through 12099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967 Messages 12100 through 12199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Table of Contents
vi
Table of Contents
Preface
This message reference provides explanations, system actions, and user responses for the messages that PowerExchange generates. PowerExchange messages appear in the following format:
PWX-00106 DBAPI Error. Storage acquire failed.
You can customize the default message prefix PWX by using the MSGPREFIX parameter in the PowerExchange DBMOVER configuration file. For more information, see PowerExchange Reference Manual. This message reference applies to the following Informatica products:

PowerExchange for Adabas PowerExchange for CA Datacom PowerExchange for CA IDMS PowerExchange for DB2 for i5/OS PowerExchange for DB2 for Linux, UNIX, and Windows PowerExchange for DB2 for z/OS PowerExchange for Flat Files on i5/OS PowerExchange for Flat Files on Linux, UNIX, and Windows PowerExchange for IMS PowerExchange for Oracle PowerExchange for SQL Server PowerExchange for VSAM
Informatica Resources
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at http://mysupport.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Product Documentation, and access to the Informatica user community.
vii
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to the Product Documentation from http://mysupport.informatica.com.
Informatica Web Site

You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.
Informatica How-To Library

As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks.
Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at KB_Feedback@informatica.com.
Informatica Multimedia Knowledge Base

As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through email at KB_Feedback@informatica.com.
Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the WebSupport Service. WebSupport requires a user name and password. You can request a user name and password at http://mysupport.informatica.com.
viii
Preface
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America Toll Free Brazil: 0800 891 0202 Mexico: 001 888 209 8853 North America: +1 877 463 2435 Standard Rate North America: +1 650 653 6332 Europe / Middle East / Africa Toll Free France: 00800 4632 4357 Germany: 00800 4632 4357 Israel: 00800 4632 4357 Italy: 800 915 985 Netherlands: 00800 4632 4357 Portugal: 800 208 360 Spain: 900 813 166 Switzerland: 00800 4632 4357 or 0800 463 200 United Kingdom: 00800 4632 4357 or 0800 023 4632 Standard Rate Belgium: +32 15 281 702 France: 0805 804632 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 Asia / Australia Toll Free Australia: 1 800 151 830 New Zealand: 1 800 151 830 Singapore: 001 800 4632 4357 Standard Rate India: +91 80 4112 5738
Preface
ix
Preface
CHAPTER 1
PWX-00100 to PWX-35999
This chapter includes the following messages:

PWX-00100 to PWX-00999, 2 PWX-01000 to PWX-01999, 74 PWX-02000 to PWX-02999, 150 PWX-03000 to PWX-03999, 196 PWX-04000 to PWX-04999, 198 PWX-05000 to PWX-05999, 226 PWX-06000 to PWX-06999, 227 PWX-07000 to PWX-07999, 290 PWX-08000 to PWX-08999, 320 PWX-09000 to PWX-09999, 321 PWX-10000 to PWX-10999, 387 PWX-11000 to PWX-11999, 443 PWX-12000 to PWX-12999, 452 PWX-13000 to PWX-13999, 490 PWX-14000 to PWX-14999, 492 PWX-15000 to PWX-15999, 505 PWX-16000 to PWX-16999, 514 PWX-19000 to PWX-19999, 528 PWX-20000 to PWX-20999, 535 PWX-21000 to PWX-21999, 563 PWX-23000 to PWX-23999, 579 PWX-24000 to PWX-24999, 588 PWX-25000 to PWX-25999, 592 PWX-30000 to PWX-30999, 592 PWX-31000 to PWX-31999, 594 PWX-32000 to PWX-32999, 605 PWX-33000 to PWX-33999, 614 PWX-35000 to PWX-35999, 619
PWX-00100 to PWX-00999
PWX-00100 Explanation: System Action: User Response: DBAPI Error. Invalid request. A call was made to the PowerExchange Database API with a database action that is not recognized by the API. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAPI Error. OPEN is not first access request. A call was made to the PowerExchange Database API without a prior request to open a table for processing. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAPI Error. Internal Function Pointer is NULL. A call was made to the PowerExchange Database API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAPI Error. Logic Module Pointer is NULL. A call was made to the PowerExchange Database API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAPI Error. INIT or Load logic module request failed. A call was made to the PowerExchange Database API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAPI Error. Remote DB Access Failed. A call was made to the PowerExchange Database API that cannot be processed correctly. The API was attempting to initiate contact with a remote database. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-00101 Explanation: System Action: User Response:
Chapter 1: PWX-00100 to PWX-35999
DBAPI Error. Storage acquire failed. A call was made to the PowerExchange Database API that cannot be processed correctly. The API was attempting to allocate memory for processing when the error was issued. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAPI Error. Could not read SQLFile file_name. A call was made to the PowerExchange Database API that cannot be processed correctly. The API was attempting to read SQL statements from the specified file when the error occurred. The task that encounters the error ends. Correct the file that contains the SQL statements and try the request again. DBAPI Error. Length of SQL statement in SQLFile file_name exceeds maxlength bytes in total. A call was made to the PowerExchange Database API that cannot be processed correctly. The API was attempting to process SQL statements from the specified file when the error occurred. The length of the SQL statement exceeds the maximum length, maxlength, permitted by the API. The task that encounters the error ends. Correct the file that contains the SQL statements and try the request again. DBAPI Error. Requested function (function) is not supported by the Access method. A call was made to the PowerExchange Database API that cannot be processed correctly. The API was attempting to open or close an SQL Cursor when the error was issued. The access method specified does not support these functions. The task that encounters the error ends. Correct the file that contains the SQL statements and try the request again. KEY Error - check digit incorrect, input=check_digit, calculated=check_digit. The check digit on the license key is incorrect. Processing ends. Verify that the license key is correct. If it is correct and the problem persists, contact Informatica Global Customer Support for a new license key. KEY Error - key length must be 44 or 64 license_key, len=key_length The length of the specified license key is incorrect. The key must be 36 characters long without hyphens, or 44 characters long with hyphens. Processing ends. Verify that the license key is correct. If it is correct and the problem persists, contact Informatica Global Customer Support for a new license key.
PWX-00107 Explanation:
System Action: User Response: PWX-00108 Explanation:
System Action: User Response: PWX-00110 Explanation: System Action: User Response:
PWX-00100 to PWX-00999
KEY Error - illegal hyphen chars in key license_key. The separator character of the specified license key is incorrect.The valid separator character in the license key is the hyphen character. Processing ends. Verify that the license key is in blocks of four characters separated by hyphens. If the problem persists, contact Informatica Global Customer Support for a new license key. KEY Error - failed to open license key file. An error occurred when the system tried to open the license key file. Processing ends. Contact Informatica Global Customer Support. KEY Error - record read failed. An error occurred when the system tried to read the license key file. Processing ends. Contact Informatica Global Customer Support. KEY Error - license has expired. Key=day-month-year, current=day-month-year. The license key has expired. Processing ends. Contact Informatica Global Customer Support for a new license key. KEY Warning - license(license_key) has number day(s) before expiration. The specified license key expires after number number of days. Processing continues. Contact Informatica Global Customer Support for a new license key. KEY Error - IP mismatch, key=number.number.number.number, local=IP_address. The IP address for which the specified license key was issued does not match the specified local IP address. Processing continues. Verify that the license key is correct. If the problem persists, contact Informatica Global Customer Support for a new license key. KEY Error - Platform mismatch, key=key, local=platform. The platform for which the specified license key was issued does not match the local platform, such as PC or MVS. Processing ends. Verify that the license key is correct. If the problem persists, contact Informatica Global Customer Support for a new license key. KEY Error - Not authorized to use access method access_method on platform platform. The access method for which the license key was issued does not match the attempted system access method access_method on platform platform. Processing ends.
PWX-00113 Explanation: System Action: User Response: PWX-00114 Explanation: System Action: User Response: PWX-00115 Explanation: System Action: User Response: PWX-00116 Explanation: System Action: User Response: PWX-00117 Explanation: System Action: User Response:
PWX-00119 Explanation: System Action:
User Response:
Verify that the license key is correct. If the problem persists, contact Informatica Global Customer Support for a new license key. Version mismatch, local=version.release, remote=version.release The specified software version on the local platform is not the same as the version on the remote platform. PowerExchange allows communication among PowerExchange installations of the same version and release levels only. Processing ends. Verify that the correct version of the software is installed on each platform. KEY Error - Not licensed for feature feature. The license key in effect does not permit the use of the specified feature. Processing ends. Verify that you are using the correct license key. Contact Informatica Global Customer Support for a valid license key. KEY Error - Vendor code mismatch. The license key in effect was issued for a vendor other than the one for which the software was supplied. Processing ends. Verify that you are using the correct license key. Contact Informatica Global Customer Support for a valid license key. DBAPI Error. mode Parameterized SQL is not supported by the method Access method. A call was made to the PowerExchange Database API and the SQL statement contains substitution variables that are not supported in the requested mode by the access method. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Only 1 Output data source is allowed under a connection when confirm write is disabled. For multiple output targets confirm write must be set in the Data Source Name (DSN). The task that encounters the error ends. Ensure that the confirm write indicator is set in the DSN. If it is already set, contact Informatica Global Customer Support. DBAPI Error. DBCB (connection_ID) is defined within a connection, but has an invalid handle (handle). An error was detected by an internal process. The task that encounters the error ends. Contact Informatica Global Customer Support. DBAPI Error. The mode of a DBCB (mode) within a connection must match the connection Mode (mode2). An error was detected by an internal process. The task that encounters the error ends. Contact Informatica Global Customer Support.
PWX-00100 to PWX-00999 5
PWX-00123 Explanation: System Action: User Response: PWX-00124 Explanation: System Action: User Response:
DBAPI Error. Confirm write must be enabled for each Output data source for multiple data sources under one connection. For multiple output targets confirm write must be set in the Data Source Name (DSN). The task that encounters the error ends. Ensure that the confirm write indicator is set in the DSN. If it is already set, contact Informatica Global Customer Support. DBAPI Error. Only 1 Input data source is allowed under a connection. This is an internal issue. For input requests only one data source can be used by a connection. The task that encounters the error ends. Contact Informatica Global Customer Support. KEY Error - Usage of dbmove is restricted. An attempt was to use an access method for which the license key granted to the user does not permit. The task that encounters the error ends. Either correct the access method to use one of the access methods for which the license key was generated, or contact Informatica Global Customer Support for a valid license key. DBAPI Error. Invalid request to load logic module for AM access_method_desc, AM number access_method_num An attempt was to use an access method that is not supported on the platform requested. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Descriptor file input failure. The descriptor file name specified on the request (filename.dsc) either could not be found, contained no records or records that were invalid. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Requested conversion from field_type to field_type for table table_name column column_name is invalid. An attempt was to convert the attributes of a column that cannot be performed. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Failed to obtain CNV function pointer address. An internal error occurred while trying to convert data from one field type to another. The task that encounters the error ends. Contact Informatica Global Customer Support and specify the nature of the error and the field types involved in the conversion.
PWX-00134 Explanation: System Action: User Response: PWX-00135 Explanation: System Action: User Response: PWX-00136 Explanation: System Action: User Response: PWX-00137 Explanation: System Action: User Response:
DBAPI Error. CNV failed for column column_name fname table_name row number record_number. An error occurred while converting the value for the given column / record / table. The task that encounters the error ends. Contact Informatica Global Customer Support and specify the nature of the error and the field types involved in the conversion. DBAPI Error. CNV for column column_name field length column_length too long. An attempt was to convert the data for a column where the length of the column exceeds the maximum permitted by PowerExchange (currently 256 bytes). The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Internal table_action data handling error, file table_name row record_number. An unexpected error occurred while performing the action shown on the record and table name specified. The task that encounters the error ends. Contact Informatica Global Customer Support. DBAPI Error. number_of_errors data conversion errors during write of block that commenced at row row. While converting the data from the data source to the requested type, an error occurred. The task that encounters the error ends. Correct the invalid row and run the request again. DBAPI Error. number_errors data conversion errors during read of block that commenced at row record_number. During processing of a SQL statement, data conversion errors occurred. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Conversion error during write. RC="reason_code". DB="table_name". Column="column_name. Msg="error_message". During processing of a SQL statement, data conversion errors occurred. The task that encounters the error ends. See details in the error message, correct the SQL statement, and run the request again. DBAPI Error. Conversion error during read. RC="reason_code". DB="table_name". Column="column_name. Msg="error_message". During processing of a SQL statement, data conversion errors occurred. The task that encounters the error ends. See details in the error message, correct the SQL statement, and run the request again.
PWX-00139 Explanation: System Action: User Response: PWX-00140 Explanation: System Action: User Response: PWX-00141 Explanation: System Action: User Response: PWX-00142 Explanation: System Action: User Response: PWX-00143 Explanation: System Action: User Response: PWX-00144 Explanation: System Action: User Response:
PWX-00100 to PWX-00999
DBAPI Error. Null indicator set for not-null output column column_name. Block starts at row record_number. An attempt was made to set the value of the column name specified to a null value. The column definition does not allow a null value. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Error. Internal PARM UPDATE data handling error, for table_name. An internal error occurred while processing the specified table name. The task that encounters the error ends. Contact Informatica Global Customer Support and report the error, specifying the table name. DBAPI Error. Conversion for SQL Parameters. RC=return_code. DB="database". Column="column". Row=row. Msg="message". The value assigned to a parameter in the SQL statement is invalid. The task that encounters the error ends. See details in the error message, correct the SQL statement and run the request again. DBAPI Error. A Group Source read must only be called at the connection level. Group sources can only be read through the connection, not by the individual data sources. The task that encounters the error ends. Contact Informatica Global Customer Support. DBAPI Error. A NON Group Source read may not be invoked at the connection level. For non-group sources, the read must be done through the individual data source. The task that encounters the error ends. Contact Informatica Global Customer Support. DBAPI SEQ Filename table_name Open error reason reason_code <error_message>. While opening the specified file or table, an error occurred. In the message text:
PWX-00147 Explanation: System Action: User Response: PWX-00148 Explanation: System Action: User Response: PWX-00149 Explanation: System Action: User Response: PWX-00150 Explanation:
table_name is the name of the file or table that could not be opened. reason_code is the PowerExchange reason code for the error. Reason code 0071 on Linux, UNIX, or Windows platforms only indicates a possible locking error. See the error message for further information. System Action: User Response: The task that encounters the error ends. Correct the SQL statement and run the request again. For locking errors, attempt to determine and eliminate the reason for the lock. Then run the request again. DBAPI SEQ Filename table_name Read error on record record_number. An error occurred while reading the record from the table shown. The task that encounters the error ends. Correct the SQL statement and run the request again.
PWX-00152 Explanation: System Action: User Response: PWX-00153 Explanation: System Action: User Response: PWX-00154 Explanation: System Action: User Response: PWX-00155 Explanation: System Action: User Response: PWX-00156 Explanation:
DBAPI SEQ Filename table_name Write error on record record_number. Requested number_bytes, actually number_bytes written. An error occurred writing a record to the table name shown. This is due to a mismatch in the length of the record. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI SEQ Filename table_name Read error on record record_number. An error occurred while reading the record from the table shown. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI TXT Filename table_name buffer overflow reached on row record_number. length record_length. Sufficient space is not available in the record to write all the data to the file. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI TXT Filename table_name output reclen of record_length exceeds max of maximum_length. An attempt was to write a record where the record length of the file exceeds the maximum currently supported by PowerExchange. The task that encounters the error ends. Correct the SQL statement and run the request again. Error reason_code opening file table_name. Reason: <reason>. Abend code = abend_code. RC=return_code (xabend_code/x/return_code). cause. While opening the specified file or table, an error occurred. In the message text:

table_name is the name of the file or table that could not be opened. reason is the reason for the error. abend_code is the abend code for the error. return_code is the PowerExchange return code for the error. xabend_code is the hexadecimal abend code for the error. xreturn_code is the hexadecimal return for the error. cause is the cause of the error. System Action: User Response: PWX-00157 Explanation: System Action: User Response: The task that encounters the error ends. Correct the SQL statement and run the request again. Not authorized to create object object_name type object_type in library object_library. authority access needed. The user profile under which the PowerExchange task is running is not authorized to create the object. The task that encounters the error ends. Either grant the user profile the correct level of authority to create tables or change the user profile under which the PowerExchange Listener runs to a profile that does have the required authority.
PWX-00100 to PWX-00999 9
SQLGN SQL Column name column_name is a reserved word in access_method. An attempt was to create a table where the column name given is a reserved value. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN SQL Column name column_name greater than Max column length maximum_length. An attempt was to create a table where the length of the column name given is greater than that permitted. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN SQL string requested for DB table_name access method access_method invalid. An invalid SQL statement was requested by the user. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN CTL string requested for DB table_name access method access_method invalid. An invalid SQL statement was requested by the user. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN SQL unknown column type fname table_name colname column_name type column_type. An invalid value was specified for the column type for the column in the table specified. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN mode File table_name write error reason reason_code. An error occurred writing a record to the table specified. The task that encounters the error ends. If the mode shown is CTL report the error to Informatica Global Customer Support. Otherwise, correct the SQL statement and run the request again. DBAPI AM does not support Commit/Rollback on Connection DBCB. The use of SQL commands COMMIT and ROLLBACK are not supported on the target. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN mode File table_name Open error reason reason_code. An error occurred while opening the file. The reason code is shown. The task that encounters the error ends. If the mode shown is CTL report the error to Informatica Global Customer Support. Otherwise, correct the SQL statement and run the request again.
10
DBAPI For Access Method access_method Commits/Rollback must be on the connection DBCB. All commit / rollback requests must be performed on the connection. The task that encounters the error ends. Contact Informatica Global Customer Support. SQLGN SQL Length statement_length Exceeds maximum allowed maximum_length. An attempt was to use an SQL statement that is longer than currently permitted by PowerExchange. The task that encounters the error ends. Correct the SQL statement and run the request again. SQLGN SQL Warning - Columns created number_created greater than Max Columns maximum_allowed allowed by database. An attempt was to create a table with more columns than is permitted by the target database. The task continues. Correct the SQL statement and run the request again. DBAPI Error. Group Source is not supported by this access method (access_method). The group source feature within PowerExchange is not supported for the access method selected. The task that encounters the error ends. Correct the SQL statement and run the request again. Used by DMX routines. DMX Problem creating DMX directory <directory_name>, reason reason_code. While creating the directory used by Details for Data Map processing, an error occurred. In the message text:

directory_name is the name of the directory that could not be created. reason_code is the PowerExchange reason code for the error.
System Action: User Response: PWX-00171 Explanation: System Action: User Response: PWX-00172 Explanation: System Action: User Response:
The task that encounters the error ends. Correct the directory name and run the request again. DMX Request Name too long <datamap_name>. The length of the specified name exceeds the maximum length for a data name map permitted by PowerExchange. The task that encounters the error ends. Correct the data map name and run the request again. DMX Failed to Lock Resource rc = reason_code. The data map processing was unable to obtain an exclusive lock on the necessary data map resource. The object might be locked by another user accessing the resource. The task that encounters the error ends. Retry the request again to see if the lock was removed. If the error persists, contact Informatica Global Customer Support and provide details of the task being performed and the reason code.
PWX-00100 to PWX-00999 11
PWX-00173 Explanation: System Action: User Response: PWX-00174 Explanation: System Action: User Response: PWX-00175 Explanation: System Action: User Response: PWX-00176 Explanation: System Action: User Response: PWX-00177 Explanation: User Response: PWX-00178 Explanation: User Response: PWX-00179 Explanation: User Response: PWX-00180 Explanation: System Action: User Response: PWX-00181 Explanation: System Action: User Response:
DMX record already exists in output data set A data map record was not updated as it already exists. The NEW=Y parameter was not specified. The data map is not updated. Correct the error and run the request again. The requested stored procedure procedure_name was not found The stored procedure requested was not found in the DBMS catalog. Processing ends. Verify that the spelling of the procedure name is correct and rerun the stored procedure. Null PRESENCE found for file file_name When doing a DB_Presence call a null PRESENCE token was detected. Processing ends. Ensure that the file in question has a valid PRESENCE token. Stop on Error count error_count exceeded The stop on error count set for the request was exceeded. Processing ends. No response is required. _PWXSTATISTICS_ table_name,inserts,updates,deletes, commits,failures,mutates This message displays statistics for a multi-write connection. No response is required. Process started: Jobname=jobname,Jobid=jobid,User=user_ID, table_name_or_mapname,file_name This message displays Netport job file information. No response is required. Process ended: Jobname=jobname,Jobid=jobid,User=user_ID,Highest Rc=max_rc This message displays the Netport job return code. No response is required. Convert update to insert failed for table_name Converting a requested update to an insert failed due to storage constraints Any further attempts to convert an update to an insert are ignored. No response is required. Convert update to insert failed for table_name column column_name Converting a requested update to an insert failed due to column constraints Any further attempts to convert an update to an insert are ignored. There is insufficient column data in the update request for it to be converted to an insert, such as columns in the table are not nullable, and are not included in the update statement.
12
PWX-00182 Explanation: System Action: User Response: PWX-00200 Explanation: System Action: User Response: PWX-00201 Explanation: System Action: User Response: PWX-00202 Explanation: System Action: User Response: PWX-00203 Explanation: System Action: User Response: PWX-00204 Explanation: System Action: User Response: PWX-00205 Explanation: System Action: User Response: PWX-00206 Explanation: System Action: User Response:
Table table_name has failed action. Column data written to reject file file_name The action specified occurred as a tolerated error for the specified table. The error is logged in the specified file and processing continues. Processing continues. No response is required. DBAPI Validation error - invalid LRECL record_length. The record length specified is either less than one or is greater than the maximum currently supported by PowerExchange. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid BLKSIZE block_size. The block size specified is not permitted. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid RECFM record_format. The record format specified is not permitted. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid DB_MODE mode. The mode specified is not permitted. Valid modes are READ, WRITE, UPDATE, APPEND and EXECSQL. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid ACCESS_METHOD access_method. The access_method specified is not permitted. See manual for a list of valid access methods. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - DB NAME invalid or missing table_name. The table name specified is either invalid or was not specified. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid CR_LF switch switch. The value specified for the CR_LF parameter is not permitted. Valid values are C, L or Y. The task that encounters the error ends. Correct the parameter and run the request again.
PWX-00100 to PWX-00999
13
DBAPI Validation error - arraysize must be in range 0 - maximum_array_size. The value specified for the arraysize parameter is invalid. The range currently permitted by PowerExchange is from 0 through 250. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - null value supplied for SQL string. No value was specified for the SQL statement. The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Validation error - SQL string exceeds MaxSQLLen bytes. The length of the SQL string specified exceeds the value permitted by PowerExchange (32700 bytes). The task that encounters the error ends. Correct the SQL statement and run the request again. DBAPI Validation error - arraysize for DMX must = 1. The value specified for the arraysize parameter is invalid. For data map processing the value must be 1. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - blksize size_specified exceeds maximum allowed maximum_allowed. The block size specified exceeds the maximum value permitted. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - blksize block_size less than lrecl record_length. The value specified for the block size cannot be less than the record length specified for the table. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid blksize/lrecl combination block_size/record_length. The values specified for block size / record length are invalid. The block size must be an exact multiple of the record length. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Validation error - invalid filename table_name. The value specified for the table name is invalid for the database being processed. The task that encounters the error ends. Correct the parameter and run the request again.
14
DBAPI User Space Creation failure object_name RC=reason_code. An error was detected during the creation of an object used for internal use. The task that encounters the error ends. Contact Informatica Global Customer Support with the object name and reason code from the error message. DBAPI User Space Deletion failure object_name RC=reason_code. An error was detected during the creation of an object used for internal use. The task that encounters the error ends. Contact Informatica Global Customer Support with the object name and reason code from the error message. DBAPI Liblist library_name request failure RC=reason_code. An error was detected during the creation of an object used for internal use. The task that encounters the error ends. Contact Informatica Global Customer Support with the object name and reason code from the error message. Invalid encrypt and/or encrypt_level. The value entered for the ENCRYPT or ENCRYPTLEVEL parameter is invalid. The task that encounters the error ends. Verify that correct values were specified for the ENCRYPT and ENCRYPTLEVEL parameters. Function function_name has returned error code error_code. The function was unable to continue due to an internal error. The task that encounters the error ends. Contact Informatica Global Customer Support with the object name and reason code from the error message. DYNALLOC failed for file file_name RCs = S99ERROR/S99INFO. The dynamic allocation request (SVC 99) was failed by the operating system. Processing ends. To diagnose the problem, look for other system messages in the job log. For IKJxxyyzz messages, see the TSO/E Messages manual. See the MVS Authorized Assembler Services Guide SVC 99 ERROR/INFO codes. If the problem persists, contact Informatica Global Customer Support with the error messages and parameter input. Additional_message The dynamic allocation request (SVC 99) was failed by the operating system or by internal API error. Processing ends. See other messages. If the problem persists, contact Informatica Global Customer Support with details of error message and parameter input.
PWX-00100 to PWX-00999
15
VSAM Error. Call = calltype. VSAM Codes: R15=R15 Reason=reason (xR15/xreason). C=IO-retcd. msg. A VSAM error occurred. Processing ends. Review the R15 and Reason codes in the MVS documentation.If the problem persists, contact Informatica Global Customer Support. data_set_namename is not a valid data set name. The data set name contains invalid characters or the member name is longer than eight bytes Processing ends. Correct input. File allocation mode for file_name has been changed from mode1 to mode2 This message indicates that user input or defaults for a file have been overwritten based on consistency checks. In the message text:

PWX-00223 Explanation: System Action: User Response: PWX-00224 Explanation:
file_name is the file for which the allocation mode has changed. mode1 is the default allocation mode. mode2 is the revised allocation mode. User Response: PWX-00225 Explanation: System Action: User Response: PWX-00227 Explanation: System Action: User Response: PWX-00228 Explanation: System Action: User Response: No response is required. File allocation mode (mode) inconsistent for existing file Error message indicating consistency errors in input parameters for a preexisting file. Processing ends. Review parameter input or delete preallocated file. File Record Length (length) is too short for maximum data length (maxlength) The file is preallocated and the record length is too small for the largest potential output data record. Processing ends. Reallocate the file with a record length large enough for the output data record. API code page translation error. Column name. Buffer length length. An error occurred in a code page translation of the specified column performed by the API. Processing ends. For more information about the error, see the associated messages. Review that the correct code page is being used. Bulk application application stopped by command. A command stopped the specified bulk data movement application. This message usually indicates that data was only partially moved. Processing ends. Determine the cause of the stopped application. Then, run the bulk data movement task again.
16
Security call failed due to LOADLIB not being APF authorized. One of the libraries associated with the LOADLIB JCL DD statement is not APF authorized. APF authorization is required for this library. Processing ends. Contact Informatica Global Customer Support to ensure that all relevant libraries are made APF authorized. Userid <user_ID> failed signon authorization information. The signon for the specified user ID was not accepted. Processing ends. To diagnose the problem, review associated messages. Verify that the user ID and password are correct. In particular, verify that the password is up-to-date and not misspelled. Extended information in the form of a return code is available in the PowerExchange log. Userid user_ID not authorized to access sequential file file or file does not exist. The file access request for the specified user ID was not accepted. Processing ends. To diagnose the problem, review associated messages. If the file exists, then contact Informatica Global Customer Support to request authorization to access the file. If the file does not exist, determine whether the file is missing, or if you are trying to use the wrong file. Userid user_ID not authorized to access NETPORT JCL member or DSN does not exist. The file access request for the specified user ID was not accepted. Processing ends. To diagnose the problem, review associated messages. If the file associated with the NETPORT DD statement exists, then contact Informatica Global Customer Support to request authorization to access the file. If the file does not exist, determine whether the file is missing, or if you are trying to use the wrong file. Userid user_ID failed selective signon authorization. The access request for the specified user ID was not accepted. Processing ends. To diagnose the problem, review associated messages. Selective signon authorization is an advanced form of user ID checking. If errors are encountered in this area, contact Informatica Global Customer Support for advice. Provide all messages, and the contents of the NETPORT DD JCL member. Security signoff error in listener mainline. RC = rc. The PowerExchange Listener has encountered a catch-all security error, identified by the return code (RC) Processing ends. To diagnose the problem, review associated messages. This is considered a really serious problem. Try to reproduce it with the SRV trace set on, then send the PowerExchange Log and all messages to Informatica Global Customer Support.
PWX-00100 to PWX-00999
17
User user not authorized for access to listener components. The user is not authorized to access PowerExchange Listener components. Processing ends. To diagnose the problem, review associated messages. Verify that the license key is valid. If the license key is invalid, or the license key is valid but the problem persists, contact Informatica Global Customer Support. License key has expired. The license key that you are using is out-of-date. Processing ends. To diagnose the problem, review associated messages. Verify that the license key is valid. If the license key is invalid, or the license key is valid but the problem persists, contact Informatica Global Customer Support. Client and server vendor code mismatch. The license key on the client machine does not match that of the server machine, with regard to the 'vendor code' section. Processing ends. To diagnose the problem, review associated messages. Verify that the license key is valid. If the license key is invalid, or the license key is valid but the problem persists, contact Informatica Global Customer Support. Unable to resolve DSN for DD dsn. RC=return_code. This is an internal checking function that identified a target data set by reference to a supplied JCL DDName. Processing ends. To diagnose the problem, review associated messages. Try to reproduce the problem with the SEC trace set on, then send the PowerExchange Log and all messages to Informatica Global Customer Support. RACF call failed due to a bad request code. In internal general-purpose RACF interface was called, but cannot perform because the request is unrecognizable. Processing ends. To diagnose the problem, review associated messages. Try to reproduce the problem with the SEC trace set on, then send the PowerExchange Log and all messages to Informatica Global Customer Support. No RACF security decision could be made. The RACF profiles for protected resources have not been defined in such a manner that PowerExchange can work with them. Processing ends. This scenario is extremely unlikely to occur, but provision has to be made to catch it nonetheless. If it does happen, try to reproduce the problem with the SEC trace set on, then send the PowerExchange Log and all messages to Informatica Global Customer Support. Also contact RACF security personal, so that they can coordinate a fix.
18
The specified resource is not protected by RACF. The software is checking authorizations against a resource that is not protected by RACF (or equivalent). Processing ends. The resource is not RACF protected, but probably should be. Discuss the matter with your own RACF security personal, and come to an understanding. Userid user_ID not authorized to access resource resource req=req by RACF. The specified user ID is not allowed to make the specified request to the quoted resource. Processing ends. If the user ID should be authorized, contact your own RACF security personal, and ask for the RACF definitions to be changed accordingly. If the user ID is not authorized, then inform your management to get the process that you want to perform reassigned to someone who is. Userid user_ID, access resource resource, req=req failed by RACF. The specified user ID is not allowed to make the specified request to the quoted resource. Processing ends. If the user ID should be authorized, contact your own RACF security personal, and ask for the RACF definitions to be changed accordingly. If the user ID is not authorized, then inform your management to get the process that you want to perform reassigned to someone who is. Client and server site license mismatch. The license key on the client machine does not match that of the server machine. Processing ends. To diagnose the problem, review associated messages. Verify that the license key is valid. If the license key is invalid, or the license key is valid but the problem persists, contact Informatica Global Customer Support. KEY Error - License key is not valid for EDP product The license key that you have does not support your attempted use of the EDP feature. Processing ends. To diagnose the problem, review associated messages. Verify that the license key is valid. If the license key is invalid, or the license key is valid but the problem persists, contact Informatica Global Customer Support. KEY Error - License key is not valid for PowerExchange product The license key that you have does not support your attempted use of the PowerExchange feature. Processing ends. To diagnose the problem, review associated messages. Verify that the license key is valid. If the license key is invalid, or the license key is valid but the problem persists, contact Informatica Global Customer Support.
PWX-00100 to PWX-00999
19
RACF User Authorization Error - USERID is not given The user ID was not supplied. Processing ends. To diagnose the problem, review associated messages. Ensure that the user ID is correct. Hostname Error - gethostname() returned errno description Routine gethostname failed when attempting to get the host name from TCP/IP stack. Processing ends. There is a problem with the TCP/IP configuration. Pass the diagnostics on to Informatica Global Customer Support, and request highest severity support. Key Validation warning - gethostname() failure rc=errno. Routine gethostname failed when attempting to get the host name from TCP/IP stack. Processing ends. There is a problem with the TCP/IP configuration. Pass the diagnostics on to Informatica Global Customer Support, and request highest severity support. Userid <user> does not have <required> access to <resource>, return code<return_code>. The security limit was exceeded for the specified user. In the message text:
user is the user for whom the security limit was exceeded. required is the access level required. resource is the resource that the user was trying to access. return_code is the PowerExchange return code for the failure. System Action: User Response: PWX-00253 Explanation: System Action: User Response: PWX-00254 Explanation: System Action: User Response: The request fails. Correct the request or user security. Then, try the request again. Authorization for <access> requested, function symptom. The security limit was exceeded for a user. The request fails. Correct the request or user security. Then, try the request again. Userid <user> failed selective signon authorization. The access request for the specified user ID was not accepted. Processing ends. To diagnose the problem, review associated messages. Selective signon authorization is an advanced form of user ID checking. If errors are encountered in this area, contact Informatica Global Customer Support for advice. Provide all messages. DBAPI Normal EOF. End of file (EOF) reached. Processing ends normally. Review associated messages for any indication that this is an error.
20
DBAPI Record not found. Requested record not found. Processing ends normally. Review associated messages for any indication that this is an error. DBAPI Escape character EscapeCharacter in metadata qualifier is only valid preceding a wildcard character. While parsing the metadata qualifier, the escape character was found. This character is used to indicate that the following wildcard character (? or *) is to be treated as a normal character. Preceding any non-wildcard character is a syntax error. The API call fails. Review value assigned to pdtldsc_q1 before the API call. DBAPI Access Method method invalid. The access method given is not valid for access through a data map. Processing ends. Review value assigned to pdtldsc_accmethod before the API call. DBAPI Error. The cursor cannot be closed because there are results pending. A cursor cannot be closed until EOF was reached. The API call fails. Ensure all data read before attempting to close cursor. DBAPI Error. DB_CLOSE failed for file fname. Error closing file specified. Review associated messages for details or ramifications. The API call fails. See associated messages giving details. Verify that specified file is available to that user from that location. DBAPI Error. DB_COMMIT failed for file fname. Error performing commit on file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_DELETE failed for file fname. Error performing delete on file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location.
System Action: User Response: PWX-00258 Explanation: System Action: User Response: PWX-00259 Explanation: System Action: User Response: PWX-00261 Explanation: System Action: User Response:
PWX-00100 to PWX-00999
21
DBAPI Error. DB_DESCRIBE failed for file fname. Error describing file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_EXECSQL failed for file fname. Error executing SQL command given on file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location, and the SQL is valid. DBAPI Error. DB_FINDNEXT failed for file fname. Error executing findnext on file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_INSERT failed for file fname. Error inserting into file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_OPEN failed for file fname. Error opening file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_POINT failed for file fname. Error positioning within file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_PRESENCE failed for file fname. Error sending/receiving presence data for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location, and presence tokens are correct.
22
DBAPI Error. DB_READ failed for file fname. Read failed for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_READBIN failed for file fname. Binary read failed for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_ROLLBACK failed for file fname. Rollback failed for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_UPDATE failed for file fname. Update failed for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file/records exist, and are available to that user from that location. DBAPI Error. DB_OPENCURSOR failed for file fname. Open cursor failed for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_CLOSECURSOR failed for file fname. Close cursor failed for file specified. The API call fails. To diagnose the problem, see associated messages. Verify that specified file is available to that user from that location. DBAPI Error. DB_OPENCONNECTION failed for location location. Failed to open connection to specified location. The API call fails. To diagnose the problem, see associated messages. Verify that specified location and database are available to the user.
PWX-00100 to PWX-00999
23
DBAPI Error. DB_CLOSECONNECTION failed for location location. Failed to close connection to specified location. The API call fails. To diagnose the problem, see associated messages. Verify that specified location and database are available to the user. DBAPI Validation error - End Of Day Table Name invalid or missing table_name. The table name specified is either invalid or was not specified. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Error - DB_OPEN failed for table table_name. DB_OPEN has failed for the specified event table. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Error - DB_DESCRIBE failed for table table_name. DB_DESCRIBE has failed for the specified event table. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Error - No Explicit Connection DBCB for table table_name. When allocating a DBCB for the specified event table no explicit DBCB was found. This could mean that the read was not done under group source control. The task that encounters the error ends. Correct the parameter and run the request again. DBAPI Warning - Library not APF authorized, so cannot determine DB2 level - using default The PowerExchange loadlib concatenation is not APF authorized, so PowerExchange cannot determine if the DB2 subsystem is V8 new-function mode or not. The default DB2 interface is used, but V8 new-function mode facilities are unavailable APF authorize the libraries in the loadlib concatenation if DB2 V8 nfm facilities are required DBAPI Warning - DB2 level check failed, rc return_code; using default The DB2 version was not determined, for the reason described by the return code. Return codes are; -1 - no Subsystem Id was passed -2 - authorization failed The default DB2 interface is used, but V8 new-function mode facilities are unavailable Contact Informatica Global Customer Support. DBAPI Information - DB2 subsystem supports new-function mode enhancements, but PWX interface does not The DB2 subsystem supports array fetch/insert but the requested PowerExchange interface (default, DTLAMDB2 or DTLAMV7D) does not. The requested DB2 interface is used, but V8 new-function mode facilities are unavailable.
PWX-00287 Explanation: System Action: User Response: PWX-00288 Explanation: System Action:
24
User Response:
If the performance improvements provided for fetch or insert with DB2 V8 new-function mode are required, select DTLAMV8F as the interface. DBAPI Warning - DB2 version does not support the requested interface The DB2 subsystem does not support the requested interface. DTLAMV7D requires DB2 V7 or above, DTLAMV8F requires DB2 V8 new-function mode or above. The default DB2 interface is used, extra facilities are unavailable Only request the enhanced DB2 interfaces for a DB2 subsystem that can support them. CNVDT Date/time mask error. A mask passed to the Date/Time routine is not of the correct format or was not passed at all. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNVDT Date/time/timestamp data error. Invalid (or blank) data was passed to the Date/time routine. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Invalid sign in field. The data passed to the data conversion routine has too many signs in it. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Too many decimal point characters. The data passed to the data conversion routine has too many decimal points. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Field has too many digits after decimal point. The data passed to the conversion routine has more digits after the decimal point than the value in the 'scale' parameter. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Field contains non-numeric data. The data passed to the conversion routine contains non-numeric data. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support.
PWX-00100 to PWX-00999
25
CNV Field contains too many digits. The data passed to the conversion routine has more digits than defined in the 'precision' parameter passed. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Number is too large. The data passed to the conversion routine is too large for the attempted conversion. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Floating point exponent error. The data passed to the conversion routine is in the exponent format (an E was detected in the data), however, an error was detected in the format of the data passed. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNVDT Date/time mask precision. The precision passed to the Date/time routine does not match the size of the mask. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNVDT Date/time mask does not match field type. An incorrect field type was passed to the Date/Time routine. For DB2 data the field type should be either CHAR or BIN. For NATURAL the field type should be packed. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Invalid input or output field address This message is not used. CNV Truncation error. A number passed to the conversion would be truncated because the output precision is not big enough to hold the number. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Attempt to assign negative value to unsigned field. The conversion routine was passed a negative number, but the output field was defined as unsigned. The system sends a return code and message to the calling program.
PWX-00311 Explanation: PWX-00312 Explanation: System Action: User Response:

26
User Response:
Collect as much information as possible about the error and contact Informatica Global Customer Support. CNV Timestamp format incorrect for conversion to TOD format The conversion routine was passed a timestamp that is not of the format CCYY-MM-DD-HH.MI.SS.nnnnnn with length of 26. The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. CMP Invalid action. An invalid comparison action was requested. The program ends and reports the error. Correct the action request specified and run the affected program again. CMP Unknown type. An invalid field type was passed to the comparison routine. The program ends and reports the error. Correct the fields and run the affected program again. CMP Fieldtype error. An invalid comparison action was requested. This was caused by trying to compare two incompatible field types. The program ends and reports the error. Correct the request specified and run the affected program again. CMP Conversion error. An error occurred while trying to convert a field prior to comparison. The program ends and reports the error. Correct the request specified and run the affected program again. Replacement Character Conversion error. An error occurred while trying to parse the replacement character specified in the CONVCHAR parameter. The program ends and reports the error. Correct the character specified in the CONVCHAR statement and run the affected program again. OS Program name program_name invalid. The program requested to run under a PowerExchange Listener is not valid. The program ends and reports the error. Report the error to Informatica Global Customer Support giving details of the task being executed and the program name from the error message, if any.
PWX-00100 to PWX-00999
27
OS Failed to load program program_name, reason reason_code_1/reason_code_2. The PowerExchange Listener could not load the program for executing the given request. The program ends and reports the error. Report the error to Informatica Global Customer Support, giving details of the task being executed and the program name and error codes from the error message. OS Failed to load program program_name entry point entry_point, reason reason_code_1/reason_code_2. The PowerExchange Listener could not load the program at the requested point for executing the given request. The program ends and reports the error. Contact Informatica Global Customer Support, giving details of the task being executed and the program name, entry point and error codes from the error message. OS Failed to unload program program_name, reason reason_code_1/reason_code_2. The PowerExchange Listener could not unload the program for executing the given request. The program ends and reports the error. Contact Informatica Global Customer Support, giving details of the task being executed and the program name and error codes from the error message. OS Failed retrieving msg message from repository message_file. Reason = reason_code. A previous error was issued to a PowerExchange task where the task was unable to retrieve further information about the error. The program ends and reports the error. Contact Informatica Global Customer Support, giving details of the task being executed and all the information from message PWX-00354 issued. Unexpected opsys error error issuing details. An unexpected operating system error was detected. The program ends and reports the error. Contact Informatica Global Customer Support, giving details of the task being executed and all the information from message PWX-00355 issued. *EXECUTE authority to program (*PGM) not available. Must have *EXECUTE on QSYGETPH, QSYRLSPH and QWTSETP. PowerExchange requires specific authority to certain AS400 API's to correctly process security requests. These have not been provided to the user profile executing the PowerExchange Listener. The program ends and reports the error. Complete the installation instructions regarding the granting of the specific authorities and run the affected program again. Loadlib must be APF authorized. To perform certain security functions, PowerExchange requires authorization to these functions. The program ends and reports the error.
System Action: User Response:
28
User Response:
Complete the installation instructions regarding the authorizing of PowerExchange libraries and run the affected program again. Not authorized to write to log file (DTLLOG). The user identifier that is running a PowerExchange task does not have the authority to output information to the PowerExchange log file. The program ends and reports the error. Either grant the necessary authority to the user profile to have write access to the PowerExchange log file, or change the user profile that runs the PowerExchange tasks to a profile that does have authority, and run the affected program again. Environment variable DETAIL_HOME found and {ignored|used}. Use PWX_HOME instead. The environment variable DETAIL_HOME is obsolete but is supported for backward compatibility. If PWX_HOME is found, it takes precedence, and DETAIL_HOME is ignored. Remove the environment variable DETAIL_HOME if PWX_HOME is defined, or change DETAIL_HOME to PWX_HOME. DD DTLLOAD required for PC_AUTH=Y DD missing. If PC_AUTH=Y configured, PowerExchange Listener must allocate dd dtlload. Processing ends. Provide the dtlload dd. PC Auth Initialize failed, rc = rc PC Authorization routine failed to initialize. Processing ends. Verify steplib authorized; verify installation; contact Informatica Global Customer Support. PC Auth Terminate failed, rc = rc PC Authorization routine failed to terminate. Processing ends. Verify steplib authorized; verify installation; contact Informatica Global Customer Support. PC Auth Set failed, rc = rc PC Authorization routine failed to set authority. Processing ends. Verify steplib authorized; verify installation; contact Informatica Global Customer Support. PC Auth Get failed, rc = rc PC Authorization routine failed to get token. Processing ends.
User Response:
PWX-00100 to PWX-00999
29
User Response:
Verify steplib authorized; verify installation; contact Informatica Global Customer Support. PC Auth Open tasklib failed, rc = rc PC Authorization routine was unable to open tasklib. Processing ends. Verify that DD DTLLOAD is present, and that data sets are readable. PC Auth Close tasklib failed, rc = rc PC Authorization routine was unable to close tasklib. Processing ends. Verify that DD DTLLOAD is present, and that data sets are readable. PowerExchange Log file write error The PowerExchange log file cannot be written to. The file is probably full. The program ends and reports the error. Either purge the file or allocate more space to the file, depending upon environment, and run the affected program again. PC Auth not allowed in this context PC Authorization routine was not allowed in this context. Processing ends. Run without pc_auth=y. The default name1 filename has been overridden. The standard default for the file identified was changed by external action. No response is required. policy credentials policy is in place A STRICT, AUTOMATIC or DEFAULT credentials policy parameter can be specified in the CREDENTIALS_CASE configuration file. DEFAULT is assumed if the parameter is omitted, which causes PowerExchange to continues with legacy behavior. No response is required. Logon credentials for uid_pwd_processing by PowerExchange on this platform PowerExchange might apply processing to user supplied logon credentials dependent upon the capabilities of the host operating system and the CREDENTIAL_CASE parameter setting in the PowerExchange configuration file. In the message text, uid_pwd_processing is the processing, if any, that was applied. No response is required. DBMOVE No matching columns - run aborted. When matching source columns to target columns, prior to moving the data, no match was found. The DBMOVE command aborts without transferring any data. Verify the descriptions of the source and target tables. Non-matching column names can be mapped. Use the GUI to create a MAP statement in the command set.
PWX-00365 Explanation: System Action: User Response: PWX-00366 Explanation: System Action: User Response: PWX-00367 Explanation: System Action: User Response:
PWX-00368 Explanation: System Action: User Response: PWX-00369 Explanation: User Response: PWX-00370 Explanation:
User Response: PWX-00371 Explanation:
User Response: PWX-00400 Explanation: System Action: User Response:
30
DBMOVE Successful. No errors were encountered during the specified DBMOVE command. Processing ends. No response is required. DBMOVE FAILED, rcs return_code1/return_code2/return_code3. The DBMOVE command has failed. Associated messages provide more information. In the message text:
return_code1 is the PowerExchange code referring to the action being performed. return_code2 is a PowerExchange message code. return_code3 might be an error code from the underlying database. System Action: User Response: Processing of the DBMOVE command ends with rollbacks where applicable. For more information about the error, review the associated messages. If required, contact Informatica Global Customer Support and provide the return codes. FROM DB table_name <location>, AM=access_method, rows read num_rows, bytes num_bytes. This message displays statistics from the completed DBMOVE command. In the message text:
table_name is the data source table details. location is the location of the data source. access_method is the access method by which the table was accessed. num_rows is the number of rows accessed. num_bytes is the number of bytes accessed. System Action: User Response: PWX-00404 Explanation: Processing ends. No response is required. TO DB table_name <location>, AM=access_method, rows written num_rows, bytes num_bytes. This message displays statistics from the completed DBMOVE command. In the message text:

table_name is the data source table details. location is the location of the data source. access_method is the access method by which the table was accessed. num_rows is the number of rows accessed. num_bytes is the number of bytes accessed. System Action: User Response: PWX-00405 Explanation: System Action: User Response: PWX-00406 Explanation: Processing ends. No response is required. Time taken time secs, transferred at Rate MB per minute. Statistics from the completed DBMOVE command. Processing ends. No response is required. Time taken time secs. Statistics from the completed DBMOVE command.
PWX-00100 to PWX-00999 31
System Action: User Response: PWX-00407 Explanation: System Action: User Response: PWX-00408 Explanation: User Response: PWX-00409 Explanation: User Response: PWX-00410 Explanation:
Processing ends. No response is required. DBMOVE MVDB User requested termination. The user ended the move request. The system shuts down the move request. No response is required. DBAPI File file name, number rows read, byte_count_bytes_input application_name. This message displays a summary of bulk data movement activity. No response is required. DBAPI File file name, number rows statement_type, byte_count_bytes_output. This message displays a summary of data movement activity. No response is required. MVDB Could not generate SQL for table creation. While attempting to automatically create a target table for the data, the column names to be used were found to be invalid for the target database. For example, they might be too long, or they might be reserved words. DBMOVE aborts without creating a target table. Verify the names on the source table, and use the MAP functionality in the GUI to map from invalid source column names to new, valid ones. User Requested Cancel for DB databasename. A request to cancel the data transfer was honored. The system ends data transfer. No response is required. Failed to start task - Open Error on JCL member file_name rcs=code1/code2/code3. Unable to open the member containing the JCL for the task. The system rejects the start task request. Ensure that the JCL member is correctly specified. Failed to start task - Open INTRDR file file_name failed rcs=code1/code2/code3. The System cannot open SYSOUT RDR. The system rejects the start task request. Determine why MVS INTRDR facility is not usable. Failed to start task - Givesocket failed rcs=code1/code2/code3. A TCP/IP Givesocket call has failed. This can be indicative of too many jobs running concurrently. The system rejects the start task request. Ensure that the number of sockets (MAXSOCKETS in SYS1.PARMLIB on MVS) is not greater than the number of jobs running.
32
PWX-00415 Explanation: System Action: User Response: PWX-00416 Explanation: System Action: User Response: PWX-00417 Explanation:
Failed to start task - File Error rcs=code1/code2. The system failed to start the given job. This can be the result of a failed task socket call due to the system being too busy or timing out a new waiting task. The system rejects the start task request. Wait until the system is less busy or ensure that the started job didn't end with a JCL error. DBMOVE DB databasename FAILED. The DBMOVE requested has failed. The system ends the task. Review associated error messages to determine why the DBMOVE failed. Target DB table_name <location>, AM=access_method. This message displays information about the SQL command executed. In the message text:

table_name is the data source table details. location is the location of the data source. access_method is the access method by which the table was accessed. System Action: User Response: PWX-00418 Explanation: Processing ends. No response is required. FROM DB table_name <location> <DBName,DBName2> AM=access_method UID=userId MAXROWS=MaxRows, ARRAYSIZE=size, TIME=time, rows read rows, bytes bytes. This message displays enhanced statistics from a DBMOVE command, including the parameters used. In the message text:

table_name is the data source table details. location is the location of the data source. DBName and DBName2 are additional details from the source table. access_method is the access method of the source. userID is the user ID of the user that accessed the table. MaxRows is the MAXROWS parameter specified for the move. size is the array size (number of rows moved at a time). time is the time taken for the dbmove to complete. rows is the total number of rows read. bytes is the total number of bytes read. System Action: User Response: PWX-00419 Explanation: System Action: User Response: Processing ends. No response is required. Unable to move processing for file <file_name>. While the database control block was being processed, an error occurred for the specified file. The system issues an error message and processing ends. To resolve the problem, contact your system programmer.
PWX-00100 to PWX-00999
33
Unable to move processing for file <file_name> due to insufficient memory. While allocating memory for this move process, an error occurred for the specified file. The system issues an error message and processing ends. To resolve the problem, contact your system programmer. Invalid staging table <table_name>. The specified IBM CCD staging table is invalid. DBMOVE aborts without transferring any data. Verify the definition of the staging table. The following columns are mandatory:
IBMSNAP_COMMITSEQ IBMSNAP_INTENTSEQ IBMSNAP_OPERATION IBMSNAP_LOGMARKER PWX-00422 Explanation: System Action: User Response: PWX-00423 Explanation: System Action: User Response: PWX-00424 Explanation: System Action: User Response: PWX-00425 Explanation: Error writing to apply control tables. An error occurred updating the CCD control tables, which are specified by the IBM_CCD_CTL parameter and the IBM snap-register table. The DBMOVE command processing ends with rollbacks where applicable. For more information, review associated error codes and messages. Bad or missing entry in IBMSNAP_REGISTER for <schema.table>. The snap-register table must contain only one entry for the specified schema and table. DBMOVE aborts without transferring any data. Add an entry for the schema/table to the snap-register table. Warning - console handler failed to terminate as expected. The move has completed successfully, but the close processing has timed out. The close processing aborts. Consult with your systems department to determine cause of the failure. DBMOVE MAP error. Column <column_name> does not exist in target <table_name>. The MAP statement in the command set attempts to correlate field names in different locations. In this instance, the destination field does not exist. The field name and target label are identified. The task that encounters the error ends. Change the command set to contain valid fields for the target. Failed to start task - Job timed out. The submitted Netport job has not taken the socket within the time limit specified by the SUBMITTEDTIME parameter. The socket is reacquired by the PowerExchange Listener with no action against the Netport job taken. Find out why the Netport job did not start running and resubmit. Some possible reasons are the system is too busy or JCL error.
34
Version mismatch, local=version.release.modification, remote=version.release.modification The specified software version on the local platform is not the same as the version on the remote platform. PowerExchange allows communication among PowerExchange installations of the same version and release levels only. Processing ends. Verify that the correct version of the software is installed on each platform. PowerExchange Service utility. ----------------------------------------This message displays help information on the DTLLSTSI command. No response is required. DTLLSTSI [function][server name][EXE name][parms][-u userid/pwd] [-q] This message displays help information on the DTLLSTSI command. No response is required. function add, delete, stop, start, query and help
System Action: User Response: PWX-00501 Explanation: User Response: PWX-00502 Explanation: User Response: PWX-00503 Explanation: User Response: PWX-00504 Explanation: User Response: PWX-00505 Explanation: User Response: PWX-00506 Explanation: User Response: PWX-00507 Explanation: User Response: PWX-00508 Explanation: User Response: PWX-00509 Explanation: User Response: PWX-00510 Explanation:
This message displays help information on the DTLLSTSI command. No response is required. server name name of service (mandatory on all functions)
This message displays help information on the DTLLSTSI command. No response is required. EXE name name and path of service executable
This message displays help information on the DTLLSTSI command. No response is required. (mandatory on ADD function) This message displays help information on the DTLLSTSI command. No response is required. parms parameters passed to service executable
This message displays help information on the DTLLSTSI command. No response is required. (optional on ADD function) This message displays help information on the DTLLSTSI command. No response is required. -u userid/pwd userid and password (both optional on ADD function)
This message displays help information on the DTLLSTSI command. No response is required. -q No prompting or console messages
This message displays help information on the DTLLSTSI command.
PWX-00100 to PWX-00999
35
User Response: PWX-00511 Explanation: User Response: PWX-00512 Explanation: User Response: PWX-00513 Explanation: User Response: PWX-00514 Explanation: User Response: PWX-00515 Explanation: User Response: PWX-00516 Explanation: User Response: PWX-00517 Explanation: User Response: PWX-00518 Explanation: System Action: User Response: PWX-00519 Explanation: System Action: User Response:
No response is required. Example1:--------------------------------------------------- ---------------This message displays help information on the DTLLSTSI command. No response is required. DTLLSTSI add PowerExchange_Listener V:BINTLLSTNT node1 -u joe/mypwd -q This message displays help information on the DTLLSTSI command. No response is required. Add a service called PowerExchange_Listener with executable DTLLSTNT, parameter This message displays help information on the DTLLSTSI command. No response is required. node1, userid of joe and password of mypwd, no prompting or console messages. This message displays help information on the DTLLSTSI command. No response is required. Example2:--------------------------------------------------- ---------------This message displays help information on the DTLLSTSI command. No response is required. DTLLSTSI delete PowerExchange_Listener This message displays information about the DTLLSTSI command. No response is required. function function not supported! Identified function is not supported in the current context. No response is required. Are these parameters correct? (Y/N) This message prompts you to confirm the request. If you enter N, DTLLSTSI ADD processing ends. Enter Y if the parameters are correct, or enter N to end processing and re-enter parameters. Do you want to delete a running service? (Y/N) Prompt user to confirm request. If user enters N then stop DTLLSTSI command DELETE processing. Enter Y to confirm delete request or N to stop delete processing.
36
Adding service service with service name name, parameter parameter, userid user_ID and pwd pwd. This message confirms current actions. In the message text:

service is the service that was added. name is the service name. parameter is the parameter added to the service. user_ID is the user ID of the user adding the service. pwd is the password of the user. User Response: PWX-00521 Explanation: User Response: PWX-00522 Explanation: System Action: User Response: PWX-00523 Explanation: System Action: User Response: PWX-00524 Explanation: System Action: User Response: PWX-00525 Explanation: System Action: User Response: PWX-00526 Explanation: System Action: User Response: PWX-00527 Explanation: System Action: User Response: No response is required. Service name action OK. This message confirms that the requested action action to the service name has completed successfully. No response is required. Database access denied. RC=return_code. The registry operation encountered an error. PowerExchange Condense processing ends. No response is required. Invalid handle. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Invalid parameter. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Invalid service name. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Service name exists. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Service database locked. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again.
PWX-00100 to PWX-00999
37
PWX-00528 Explanation: System Action: User Response: PWX-00529 Explanation: System Action: User Response: PWX-00530 Explanation: System Action: User Response: PWX-00531 Explanation: System Action: User Response: PWX-00532 Explanation: System Action: User Response: PWX-00533 Explanation: System Action: User Response: PWX-00534 Explanation: System Action: User Response: PWX-00535 Explanation: System Action: User Response: PWX-00536 Explanation: System Action: User Response:
38
Service name does not exist. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Service name is not active. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Database does not exist. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Call is only valid in Windows. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. The account name is invalid or does not exist. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Unknown error. RC=return_code. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Service name is currently state. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Cannot find the specified service EXE name name. Check path and EXE name supplied. Trying to add specified program but unable to locate it. Processing ends. Verify that program location is correct. The dependency service or group failed to start. RC=return_code The return code return_code was received from a registry operation. Processing ends. Correct problem and try again.
PWX-00537 Explanation: System Action: User Response: PWX-00538 Explanation: System Action: User Response: PWX-00539 Explanation: System Action: User Response: PWX-00540 Explanation: System Action: User Response: PWX-00541 Explanation: User Response: PWX-00542 Explanation: User Response: PWX-00543 Explanation: System Action: User Response: PWX-00544 Explanation: System Action: User Response: PWX-00545 Explanation: System Action: User Response:
An instance of the service is already running. RC=return_code The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. The service did not start due to a logon failure. RC=return_code The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Could not obtain the TCP/IP Domain Name. Error in trying to get the standard host name for the local machine. Processing ends. Ensure that the machine is configured correctly. Incorrect number of arguments - use help for examples. The number of arguments specified in command is incorrect. Processing ends. Correct command text and try again. Service name RUNNING. Confirmation of service status. No response is required. Service name STOPPED. Confirmation of service status. No response is required. DTLLSTNT Error errfunction, RC=return_code Error in service processing. Processing ends. Examine error message, correct and try again. Service Request timeout. The return code return_code was received from a registry operation. Processing ends. Correct problem and try again. Could not create listener window. Unable to create the PowerExchange Listener window. Processing ends. Ensure that sufficient machine resources are available.
PWX-00100 to PWX-00999
39
PWX-00590 Explanation: User Response: PWX-00591 Explanation: User Response: PWX-00592 Explanation: User Response:
Active type codepage is codepage (description). This message displays during the start up of a PowerExchange Listener. No response is required. Tasks now active = number. This message displays during the processing of PowerExchange Listener tasks to indicate the number (number) of started tasks. No response is required. Warning. IRRSIU00/IRRSDU00 not loaded. RC=return_code. Reason=reason_code. Unix services may fail when running with SECURITY=2. Modules to support UNIX System Services on OS390 could not be loaded. This option (OUSP=Y) is only turned on at the request of Informatica Global Customer Support. Contact Informatica Global Customer Support. DTLLST1: IP addresses: IPAddresses List IP addresses detected during license key checking if more than one found (for example, multi-homed box). No response is required. MessageText This message displays additional messages during the start up of a PowerExchange Listener. For more information, see the listed messages, MessageText. Using name file_name This message displays the full names used - name and file_name - for the configuration and license key files during the start up of a PowerExchange Listener. No response is required. Tasks now active = number. Tasks starting = ports. This message displays when at least one task is active and another task is in the process of starting up. The PowerExchange Listener port is blocked while a task is starting using an SSL connection until it has completed the SSL_accept() command, which upgrades the socket to an SSL connection. The starting of SSL tasks can takes several seconds depending on the network, the number of certificates, and the CPU power of the client and server machines. In the message text:
PWX-00593 Explanation: User Response: PWX-00594 Explanation: User Response: PWX-00595 Explanation: User Response: PWX-00596 Explanation:
number is the number of active tasks. ports are the ports of the starting tasks. System Action: User Response: PWX-00600 Explanation: User Response: The PowerExchange Listener displays another informational message when the number of active or starting tasks changes. No response is required. Listener Jobname is JobName. This message displays during the start up of a PowerExchange Listener. No response is required.
40
Initialization of console handler failed. RC=reason_code. The PowerExchange Listener could not open the MVS console. The PowerExchange Listener Processing ends. Look at the system log for further messages. Contact your Systems Programmer or Informatica Global Customer Support. Failed to set STDIN non-blocking. RC=reason_code. The attempt to read from the console failed. Attempts to communicate with the PowerExchange Listener through the console might not succeed. Review other messages on the system log. Contact Informatica Global Customer Support. Failed to get Listener storage area, closing down. The PowerExchange Listener has failed to allocate sufficient resources. The PowerExchange Listener task ends. Ensure that enough system resources are available to the PowerExchange Listener. Number of input args invalid number. The requested task expects a certain number of arguments to be provided. The number provided does not match that expected by the task. The requested task ends. Correct the arguments passed to the task and try again. See the documentation for the correct format for running the required task. Listener Node name NodeId too long length=length. The name for the connection node specified when starting a PowerExchange Listener is longer than can be accommodated. The maximum length for a node is currently 64 characters. The PowerExchange Listener task ends. Correct the name of the connection node passed to the PowerExchange Listener and try the request again. Verify that the value in the PowerExchange configuration file for the LISTENER and NODE parameters do not exceed the maximum length allowed. Failed to load COMMS DLL RC=reason_code. The PowerExchange Listener failed to load the routine that controls communications between elements of the software. The PowerExchange Listener task ends. Ensure that the PowerExchange Listener task is being requested as per the supplied documentation. If it is, contact Informatica Global Customer Support for more guidance on correcting this issue, providing the reason code from the message to them. Listener VRM SoftwareVersion started. This message displays during the start up of a PowerExchange Listener. No response is required.
PWX-00607 Explanation: User Response:
PWX-00100 to PWX-00999
41
Listener has resumed accepting connections. The PowerExchange Listener was previously not accepting any more tasks as the maximum allowed had been reached. The PowerExchange Listener is now accepting further tasks as previous tasks have completed. No response is required. Listener has temporarily stopped accepting connections. The PowerExchange Listener has reached the maximum number of tasks that it can support. All future connections are ignored until currently running tasks have completed. No response is required. Duplicate handle failed RC = reason_code (HexReasonCode). A subtask submitted by a PowerExchange Listener has failed to start correctly. The subtask submitted by the PowerExchange Listener ends. Contact Informatica Global Customer Support and report the message including the reason codes. Failed to start process. RC = reason_code (HexReasonCode). A subtask submitted by a PowerExchange Listener has failed to start correctly. The subtask submitted by the PowerExchange Listener ends. Contact Informatica Global Customer Support and report the message including the reason codes. Failed to allocate child process base work area. There were insufficient system resources available to run a task submitted by a PowerExchange Listener. The subtask submitted by the PowerExchange Listener ends. Ensure that sufficient system resources are available to run the number of tasks required and try the request again. Failed to start child process - too many threads. RC = reason_code. A subtask was submitted with too many concurrent tasks running. The subtask submitted by the PowerExchange Listener ends. Contact Informatica Global Customer Support and report the message including the reason codes. Failed to start child process - invalid request. RC = reason_code. A subtask was requested with an invalid request. The subtask submitted by the PowerExchange Listener ends. Contact Informatica Global Customer Support and report the message including the reason codes. Failed to start child process - unknown error. RC = reason_code. An unexpected error occurred while starting a subtask. The subtask submitted by the PowerExchange Listener ends.
User Response: PWX-00609 Explanation: User Response: PWX-00610 Explanation: System Action: User Response:
42
User Response:
Contact Informatica Global Customer Support and report the message including the reason code. Process status error. RC = reason_code (HexReasonCode). An unexpected error occurred during the closing of a task. The subtask submitted by the PowerExchange Listener ends. Contact Informatica Global Customer Support and report the message including the reason code. Forced Close in progress. This message displays during the shut down of a PowerExchange Listener. No response is required. Standard Close in progress. This message displays during the shut down of a PowerExchange Listener. No response is required. All tasks closed. This message displays during the shut down of a PowerExchange Listener. No response is required. Waiting NumberOfSeconds for NumberOfTasks tasks to close. This message displays during shut down of the PowerExchange Listener. No response is required. Kill issued to NumberOfTasks tasks still alive. During shut down processing, the PowerExchange Listener had to end subtasks that had failed to complete their processing during the allotted time interval. No response is required. NumberOfTasks tasks failed to close within seconds seconds. This message displays during shut down of the PowerExchange Listener. No response is required. Listener shutdown complete. This message displays during shut down of the PowerExchange Listener. No response is required. Listener Node name NodeId not found in CFG file. An attempt was made to start a PowerExchange Listener for a node that had no entry in the PowerExchange configuration file. The PowerExchange Listener task ends Retry the command to start the PowerExchange Listener with a valid node from the PowerExchange configuration file. Listener/datamap server failed to set signal handlers. The PowerExchange Listener or data map server task was unable to set up error handling
PWX-00100 to PWX-00999 43
PWX-00617 Explanation: User Response: PWX-00618 Explanation: User Response: PWX-00619 Explanation: User Response: PWX-00620 Explanation: User Response: PWX-00621 Explanation: User Response: PWX-00622 Explanation: User Response: PWX-00623 Explanation: User Response: PWX-00624 Explanation: System Action: User Response:
The task ends. Contact Informatica Global Customer Support and report the message, including the reason codes. Failed to get job information. RC = reason_code (HexReasonCode). The task failed to retrieve the current job information for the task running. The task ends. Contact Informatica Global Customer Support and report the message, including the reason codes. Failed to create user queue UserQueue, reason ErrorCode/reason_code. An error was returned by the process that creates user queues for internal use by the application. The task ends. Contact Informatica Global Customer Support and report the message, including the reason codes. Security level 2 or selective signon has been set, but the signon table cannot be processed. PowerExchange could not load a valid PowerExchange sign-on file. The PowerExchange sign-on file authorizes users to:
Sign on to PowerExchange systems from specific IP addresses. Issue specific pwxcmd commands on Linux, UNIX, and Windows. System Action: User Response: The task ends. To determine the cause of the error, review accompanying error messages. Then, edit the sign-on file to correct any syntactical errors and run the request again.
Note: To disable selective sign-on, edit the SECURITY statement in the DBMOVER
configuration file. For more information about the sign-on file and selective sign-on, see the PowerExchange Reference Manual. PWX-00629 Explanation: System Action: User Response: PWX-00632 Explanation: System Action: User Response: PWX-00634 Explanation: System Action: Listener was started with security checking option specified but the required environment cannot be established. A security error occurred during the start of a task The task ends. See previously issued errors for further information. Correct the errors and retry the task. IP address invalid, line=LineNumber, IPAddress An invalid IP address was detected in the signon table at the line number shown. The task ends. Correct the IP address in the signon table and try the request again. DTLSGNON - Memory allocation failure During the signon processing the application has attempted to allocate some memory. This request failed due to lack of resources being available. The task ends.
44
Either retry the request later or ensure that sufficient system resources are available. Sub task was started with selective signon option but the selective signon table cannot be processed. The access request was not accepted. The system abandons the process in progress. Check the signon table for the platform the request failed on. Selective signon authorization is an advanced form of user ID checking. If errors are encountered in this area, If necessary contact Informatica Global Customer Support for advice. Provide all messages. Accept of connection from address Address port port timed out after seconds seconds An connection failed from the client address because the accept was not completed by the subtask within the maximum number of seconds after the subtask started. With SSL connections, the client should execute SSL_connect() while the PowerExchange Listener subtask should upgrade the socket is an SLL connection, validates certificates and executes SSL_accept(), but this processing does not complete in time. With non-SLL connections, there is not a problem because the accept of the incoming connection is done in a single atomic transaction. The incoming connection is discarded and the PowerExchange Listener port becomes available for work. This error might be caused by a problem on the network or on the client machine that is trying to make the connection. AuthGroup group_name specified for user user_ID does not exist in selective signon table. The authorization group specified for the user is not defined in the selective sign-on file. The selective sign-on file cannot be processed. The pwxcmd command is not processed. Verify that the AUTHGROUP assigned to the specified user exists and is specified correctly in the signon.txt file. User user_ID is not authorized for command The specified pwxcmd command is not in the list of allowed commands for the user's authorization group. The pwxcmd command is not processed. In the signon.txt file, verify that the following information is specified correctly:
The user is specified in the AUTHGROUP statement. The command is listed in the CMDLIST parameter in the AUTHGROUP statement. PWX-00642 Insufficient authority to verify password (userid userid return code information). Explanation: System Action: User Response: Insufficient authority existed to verify the password for the specified user ID. Processing ends. Depending on your platform, perform one of the following actions:
On Linux or UNIX: Run setup_pwxauth to grant the required authority. On Windows: The PowerExchange Listener user ID might require the act as part of the operating system' privilege. For more information, see the product documentation.
PWX-00100 to PWX-00999
45
PWX-00643 Unexpected failure attempting to verify password for userid userid (return code information). Explanation: System Action: User Response: PWX-00650 Explanation: User Response: PWX-00651 Explanation: User Response: PWX-00652 Explanation: System Action: User Response: PWX-00653 Explanation: User Response: PWX-00654 Explanation: User Response: During password verification for the specified user ID, an unexpected failure occurred. Processing ends. Contact Informatica Global Customer Support. Listener IPAddress - Listener on port port socket socket This is an informational message issued by the PowerExchange Listener during start up processing. No response is required. Listener Listener polling on port portnumber SSL-on This is an informational message issued by the PowerExchange Listener during start up processing. No response is required. TCP/IP TCPVerb Error, rc=ErrorCode, reason <message> During TCP/IP processing, an error occurred. The task ends. Correct the communications error reported and try the request again. Operator close met while waiting for TCPIP input. While transferring data across a network, the user entered a stop task request. This message is sent for information only. No response is required. Using TCPIP load module DTLNETsuffix. TCP/IP access is being done by the specified DTLNET load module On MVS, if parameter TCPIPVER is omitted, then TCP/IP access is performed by load module DTLNET. If parameter TCPIPVER is set to 2, then load module DTLNET2 is used. If parameter TCPIPVER is set to 3, then load module DTLNET3 is used. TCPIP Socket Statistics: Select Writable Writable_Select_count, Zero Bytes Sent sends_with_zero_bytes,RC Minus One send_return_code_-1, Successful Sends successful_sends, Attempted Sends attempted_sends This message displays TCP/IP statistics, and is used by Informatica Global Customer Support only. This message is not an indication that the network is constrained. No response is required. Port port is running in SSL mode This is an informational message issued by the PowerExchange Listener during start up processing. No response is required. TCPIP error detected during operation. Connection terminated TCP/IP message issued when a connection was lost. This is usually due to a either a network failure or one side of a conversation disappearing. The connection ends.
PWX-00655
Explanation: User Response: PWX-00656 Explanation: User Response: PWX-00657 Explanation: System Action:
46
User Response: PWX-00670 Explanation: System Action: User Response: PWX-00671 Explanation: System Action: User Response: PWX-00672 Explanation: User Response: PWX-00673 Explanation: User Response: PWX-00674 Explanation: User Response: PWX-00675 Explanation: System Action: User Response:
Find the reason for session termination and rectify. Unable to store listener security profile. An error occurred while verifying the user profile information. The task ends. See any previously issued messages for the task for further information. Unable to restore listener security profile. While verifying the user profile information, an error occurred. The task ends. See any previously issued messages for the task for further information. Record Mapping moved to Client for <file_name>. This is an informational message used when debugging the software. No response is required. Listener is waiting for work. The PowerExchange Listener is up and waiting for work. No response is required. Listener has issued RUNJOB to a PowerExchange support task. A batch task was successfully started. No response is required. Listener has failed to issue RUNJOB, rc = rc, profile =profile. An attempt to start a batch task was unsuccessful. PowerExchange Listener processing continues. Contact Informatica Global Customer Support and report the message, including the reason codes. Check the system logs for any other messages. Listener has passed a socket to a PowerExchange support task. The PowerExchange Listener has passed the client connection to the started batch task. No response is required. Received command command_text' The DBMOVE command subtask has received a command. No response is required. Command invalid DBMOVE command was invalid. No response is required. Commands accepted: DBMOVE command subtask first line of help. No response is required.
PWX-00676 Explanation: User Response: PWX-00680 Explanation: User Response: PWX-00681 Explanation: User Response: PWX-00682 Explanation: User Response:
PWX-00100 to PWX-00999
47
PWX-00683 Explanation: User Response: PWX-00684 Explanation: User Response: PWX-00685 Explanation: User Response: PWX-00690 Explanation: User Response: PWX-00700 Explanation: System Action: User Response:
C, CLOSE or STOP - stops DBMOVE DBMOVE command syntax. No response is required. D or DIS - displays current number of records read
DBMOVE command syntax. No response is required. H or HELP - displays this help syntax
DBMOVE command syntax. No response is required. Records read = number_of_records_read The DBMOVE command subtask is reporting the number of records read. No response is required. MTF unknown error. Attempt to start a PowerExchange Listener subtask failed. PowerExchange Listener temporarily stops accepting any new connections. Review other messages in the system log that could point at the cause. Contact Informatica Global Customer Support. MTF thread limit exceeded. Attempt to start a PowerExchange Listener subtask failed. The PowerExchange Listener temporarily stops accepting new connections. Increase the MAXTASKS parameter in the DBMOVER file and restart the PowerExchange Listener. MTF subtask abended Attempt to start a PowerExchange Listener subtask failed. The PowerExchange Listener temporarily stops accepting new connections. Review the log for other messages. MTF not active. Attempt to start a PowerExchange Listener subtask failed as the multi-tasking environment is not active. The PowerExchange Listener temporarily stops accepting new connections. Review the log for other messages. Contact Informatica Global Customer Support. MTF bad program linkage. Attempt to start a PowerExchange Listener subtask failed. The PowerExchange Listener temporarily stops accepting new connections. Contact Informatica Global Customer Support.
48
MTF Invalid taskid. Attempt to start a PowerExchange Listener subtask failed. The PowerExchange Listener temporarily stops accepting new connections. Contact Informatica Global Customer Support. MTF failed to find function. Attempt to start a PowerExchange Listener subtask failed. The PowerExchange Listener temporarily stops accepting new connections. Contact Informatica Global Customer Support. MTF out of memory. Attempt to start a PowerExchange Listener subtask failed. The PowerExchange Listener temporarily stops accepting new connections. Increase the size of the PowerExchange Listener region and restart the PowerExchange Listener. MTF failed to initialize for program program_name. Reason code reason. The MTF Environment could not be initialized to support PowerExchange Listener subtask. The PowerExchange Listener ends. Check the system log for further messages and contact your MVS Systems Programmer or Informatica Global Customer Support. Number Dormant TCBs The number of inactive persistent wait TCBs. No response is required. Attach failed for program program, rc = reason_code An unexpected error occurred during the initiation of a sub-task. The task ends. Contact Informatica Global Customer Support and report the message, including the reason codes. Active tasks: This is an informational message used by internal processes to aid in the reporting of active tasks. No response is required. task=task_ID, Partner=partner, Port=port, PwrCntrSess=session_name, Application=application_ID, Status=status, AM=access_method, Mode=mode, Process=task_process_name, SessId=session_ID This message displays the status of active tasks associated with a PowerExchange Listener. The task and task_ID variables vary based on platform and have the following values:
PWX-00709 Explanation: User Response: PWX-00710 Explanation: System Action: User Response:
PWX-00711 Explanation: User Response: PWX-00712
User Response:
For MVS and Windows, TaskId with the PowerExchange task number For Linux and UNIX, pid with the process ID For i5/OS, JOB with the i5/OS job number
PWX-00100 to PWX-00999
49
The remaining variables in this message can have the following values:
Partner. The TCP/IP address of the machine that contacted PowerExchange and caused the task to be created. Port. The TCP/IP port that was contacted. PwrCentrSess. For PowerExchange tasks created for PowerCenter sessions, the session name with the format integration_service/workflow_name/session_name. Otherwise, the value is N/A. Application. For CDC sessions, the value of the Application Name attribute on the PWXPC application connection. Otherwise, the value is N/A. Status. The task status, which is one of Active, STOPTASK acknowledged, or STOPTASK set. AM. The PowerExchange access method for the task. Mode. The request mode, which is one of Append, Exec, Read, Write, Update, or Unknown. Process. If available, the PowerExchange task process name. SessId. If available, the value of the DTLSESSID SQL escape sequence. User Response: PWX-00713 Explanation: User Response: PWX-00714 Explanation: System Action: User Response: PWX-00715 Explanation: User Response: PWX-00719 Explanation: User Response: PWX-00720 Explanation: System Action: User Response: No response is required. number active tasks This is an informational message used by internal processes to aid in the reporting of active tasks. No response is required. Command Parameter1 Parameter2 Command ignored because message The command entered was ignored because an error was found. PowerExchange ignores the command. Correct the command and try the request again. Command Parameter1 Parameter2 Processed OK This is an informational message that indicates that the command entered by the user was processed satisfactorily. No response is required. Listener cancelling idtype=id partner=ip_address port=port_number am=access_method additional_info This message displays during shutdown of PowerExchange to indicate the tasks that were running at the time are also being closed. No response is required. MVS abend, signal signal, abend code abend_code reason code reason_code An unexpected error was encountered by a subtask. The subtask ends. Correct the cause of the error and try the request again. If the error condition persists, contact Informatica Global Customer Support. User not authorized for TASK_CTRL function task_control resource resource access access. This should be supported by security messages.
50
System Action: User Response: PWX-00722 Explanation: System Action: User Response: PWX-00723 Explanation: System Action: User Response: PWX-00724 Explanation: System Action: User Response: PWX-00725 Explanation: System Action: User Response: PWX-00726 Explanation: System Action: User Response: PWX-00727 Explanation: System Action: User Response: PWX-00730 Explanation: System Action: User Response:
PowerExchange ends the request and returns control to the calling program. PowerExchange also logs security messages. Correct the request or user security. Then, try the request again. Command <command_name> failed: dtlamutl returned return_code on OPEN The specified command failed with the specified return code. PowerExchange ends the request and returns control to the calling program. Correct the request. Then, try the request again. Command <command_name> succeeded The specified command was successful. PowerExchange ends the request and returns control to the calling program. No response is required. Command <command_name> failed: dtlamutl returned rc on EXECSQL The specified command failed with the specified return code. The request ends and control is returned. Correct the request. Then, try the request again. Alloc: DDN=<DD_name> DSN=<data_set_name> This message displays the allocated data sets. PowerExchange ends the request and returns control to the calling program. No response is required. Close PowerExchange Listener received CLOSE command. PowerExchange processes the request. No response is required. Close FORCE PowerExchange Listener received CLOSE FORCE command. PowerExchange processes the request. No response is required. Codepage file name too long file_name The external code page file name as described in the PowerExchange configuration file, is too big. The fully qualified file name must be less than 512 bytes long. PowerExchange returns an error code and message, and abends. Rename the fully qualified code page file name and ensure that it is less than 512 bytes long. Unable to open codepage file file_name PowerExchange was unable to open the external codepage file. PowerExchange returns an error code and message, and abends.
PWX-00100 to PWX-00999
51
User Response:
Ensure that the fully qualified external codepage file name as entered in PowerExchange configuration file exists as typed. After this is done, resubmit the request. Error error_code reading codepage file file_name PowerExchange has had problems reading the codepage file. The error code error_code and codepage file name file_name are also returned. PowerExchange returns an error code and message, and abends. Contact Informatica Global Customer Support with details of the error for further investigation. Invalid character character in codepage file file_name, line line_number An invalid character was found in the codepage file. PowerExchange returns an error code and message, and abends. Characters in the codepage file should consist of only 2 valid hex characters followed by a space or end of line marker. Correct the invalid character and resubmit. Not enough characters in codepage file file_name There are not enough characters in the codepage file. PowerExchange returns an error code and message, and abends. There should be exactly 256 characters in a codepage. Correct the codepage file ensuring the correct number of characters are present, and resubmit. Codepage file file_name has too many characters on line line_number There are too many characters on the mentioned line of the codepage file. PowerExchange returns an error code and message, and abends. There should only be 16 characters on each line of the codepage file. Correct and resubmit. Codepage file file_name has too few characters on line line_number There are too few characters on the mentioned line of the codepage file. PowerExchange returns an error code and message, and abends. There should be 16 characters on each line of the codepage file. Correct and resubmit. Multibyte codepage codepage cannot be used here. PowerExchange has detected an invalid control code page request. PowerExchange returns an error code and message, and abends. Specify a single-byte control codepage. Error message building translation table for codepage codepage (codepage_number) codepage (codepage_number). PowerExchange was unable to build a translation table for the two codepages mentioned. PowerExchange returns an error code and message, and abends. Contact Informatica Global Customer Support with details of the error for further investigation. codepage_name is not a recognized codepage. The code page name on the PowerExchange configuration file was not recognized.
52
PowerExchange returns an error code and message, and abends. The codepage name should be one of the standard codepages such as, IBM-037 or a user codepage name such as USRCP01. Correct the codepage name in the PowerExchange configuration file and resubmit. Error converting from code_page_name (number) to code_page_name (number). The conversion routine could not convert between the code pages. PowerExchange sends a return code and message to the calling module. Collect as much information as possible about the error and contact Informatica Global Customer Support. Conversion error. error_information. Provides additional information about a conversion error. PowerExchange sends a return code and message to the calling module. Collect as much information as possible about the error and contact Informatica Global Customer Support. Length length Data data Provides additional information about a conversion error. PowerExchange sends a return code and message to the calling module. Collect as much information as possible about the error and contact Informatica Global Customer Support. Code page number (description) cannot be used over network. Endianness is relative to platform. The code page works differently on low and high ended platforms. It can only be used locally; not with a PowerExchange Listener or across a network. The task ends. Change the code page to one that defines explicit endianness. For example, UTF-16LE or UTF-16BE instead of UTF-16. code_page_number is not a recognized code page number. The code page number was not recognized. The code page number takes precedence over the code page name and must lie within the range of numbers recognized by PowerExchange. such as 1 = ISO-8859, 2 = IBM-037, 3 = IBM-037, 41 = UTF-8 PowerExchange returns an error code and message, and abends. If the code page number is bigger than 40, this indicates an ICU code page that might not be used on platforms that do not support ICU (for example, HP3000, ICL). Collect as much information as possible about the error and contact Informatica Global Customer Support. code page number code_page_number does not lie in ICU CPN range from low_code_page_number to high_code_page_number. The code page number is not in the required range for ICU code pages. PowerExchange returns an error code and message, and abends. On a ICUCONVERTER or ICUALIAS command, provide a valid ICU code page number.
PWX-00100 to PWX-00999
53
ICU data directory set to name. The ICU data directory was set to the specified directory. User-defined ICU code pages can be loaded from CNV files in this directory. No response is required. Truncation not supported for code page code_page_number (code_page_name) An attempt was to truncate data in a multibyte code page for which truncation is not available. Processing aborts. Ensure that no attempt is made to truncate using this code page. On reading, ensure that the column receiving the data is big enough On writing, truncate the source data before it is converted into the problem code page. Or use a different code page. Invalid UTF8 lead byte hex_of_byte at offset offset. An invalid lead byte was found in a UTF8 string. Processing aborts. Verify that the data is really in UTF8. Fix the data. DTLREXE Input LOC=location, PROG=program_name, PARMS=parameters, UID=<user_ID>. This message displays the location node, program, parameters passed, and the user ID passed to the Run/Execute procedure. PowerExchange displays an This message is informational. No response is required. DTLREXE User Return Codes 1=return_code, 2=return_code. The DTLREXE procedure has returned the displayed codes. Pass the return codes back to the calling module for action. Contact Informatica Global Customer Support with details of the error for further investigation. DTLREXE Startup Error <error_message>. The DTLREXE procedure has failed with the specified error. PowerExchange displays an error message and exits from the procedure. Contact Informatica Global Customer Support with details of the error. DTLREXEL Input received LOC=location, PROG=program_name, PARMS=parameters. Informational message showing location node, program and parameters received by the Run/Execute procedure. The system displays an informational message. No response is required. DTLREXEL User Return Codes 1=return_code, 2=return_code. Message showing the return codes from the DTLREXEL procedure. If they are not zero, further messages are displayed. The system displays an informational message.
PWX-00752 Explanation: System Action: User Response: PWX-00753 Explanation: System Action: User Response: PWX-00754 Explanation: System Action:
54
User Response:
If the return codes are non-zero, then no action is required. Otherwise note the other error messages and contact Informatica Global Customer Support for further investigation. DTLREXE Command OK! Informational message confirming that the DTLREXE procedure completed normally. Output the message. No response is required. DTLREXE Submit parameters FN=job_file, MODE=(action,wait_option), TIME=wait_time, SUBMITTIMEOUT=submit_timeout, OUTPUT=output_data_set, RESULT=result_data_set. Informational message showing location node, program, parameters passed and user ID being passed to the Run/Execute procedure. The system displays an informational message. No response is required. REXE Error translating field. An error occurred translating characters from one code page to another. Processing ends. PowerExchange reports an error. See associated error message for more details of the error that includes the source and target code pages, error information reported by ICU and the first 100 bytes of the problem data. If the error occurred on multibyte SQL, check that the CODEPAGE parameter specifies a multibyte code page for SQL on both the source and target machines. Cannot open vsam_data_set_type VSAM data set with access_method access method The VSAM access module could not open the data set specified with the access method listed. The system returns an error to the calling software. Correct the data set name or the access method. AMVSM Validation Error - not binary The VSAM access module was directed to open a data set in a non-binary mode. The system returns an error to the calling software. Contact Informatica Global Customer Support. AMVSM function_call failed RC=return_code RSN=reason_code for file=file name The VSAM access module encountered an error when calling a VSAM interface routine. The return and reason codes are documented in the IBM documentation, DFSMS Macro Instructions for Data Sets. The system returns an error to the calling software. Check IBM's manual DFSMS Macro Instructions for Data Sets for the MACRO return and reason codes. If the problem persists, contact Informatica Global Customer Support. AMVSM Authorization error for userid <user_ID> The VSAM access module was unable to access the data set because an authorization error occurred for the specified user ID. The system returns an error to the calling software. Correct the authorization problem.
PWX-00100 to PWX-00999 55
AMVSM Information retrieval failure, error code=0x S99ERROR, info code=0xS99INFO The VSAM access module encountered an error when attempting to retrieve information about the data set. The system returns an error to the calling software. Check for other system messages in the job log. The IKJxxyyzz messages are documented in the TSO/E Messages manual. Check the MVS Authorized Assembler Services Guide SVC 99 ERROR/INFO codes. If you cannot resolve the problem, contact Informatica Global Customer Support with details of error messages and parameter input. AMVSM Unsupported data set type <VSAM_data_set_type> The VSAM access module attempted to open a data set of a type that it does not support. The system returns an error to the calling software. Correct the data set name or the access method. AMVSM OPEN failed The VSAM access module encountered an error opening a data set. The system returns an error to the calling software. Correct the problem. AMVSM call_type failed - no position held The VSAM access module function failed because position was not held. The system returns an error to the calling software. Contact Informatica Global Customer Support. AMVSM VSAM file is empty and cannot be used until primed The VSAM access module function failed because the VSAM data set had not been primed. The system returns an error to the calling software. Prime the VSAM data set. AMVSM error related to empty data set processing The VSAM access module function failed because of errors encountered during empty data set processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. AMVSM processing_mode not supported with access_method access method The VSAM access module does not support the processing mode specified with the access method RRDS. The system returns an error to the calling software. The processing option is not available without the VSAMPREFIX option. AMVSM CI ACCESS only allowed for READMODE The VSAM access module was directed to use CIACCESS for other than read processing. The system returns an error to the calling software.
PWX-00779 Explanation: System Action: User Response: PWX-00780 Explanation: System Action: User Response: PWX-00781 Explanation: System Action: User Response: PWX-00782 Explanation: System Action: User Response: PWX-00783 Explanation: System Action: User Response: PWX-00784 Explanation: System Action: User Response: PWX-00785 Explanation: System Action:
56
User Response: PWX-00786 Explanation: System Action: User Response: PWX-00787 Explanation: System Action: User Response: PWX-00788 Explanation: System Action: User Response: PWX-00789 Explanation: System Action: User Response: PWX-00790 Explanation: System Action: User Response: PWX-00791 Explanation: System Action: User Response: PWX-00792 Explanation: System Action: User Response:
Remove the CIACCESS option. AMVSM CI ACCESS ignored, data set is compressed The VSAM access module was directed to use CIACCESS for a data set that is compressed. VSAM access does not allow CIACCESS for compressed data sets. Normal processing is used. Remove the CIACCESS option to avoid This message is informational. AMVSM CI ACCESS ignored, data set has spanned records The VSAM access module was directed to use CIACCESS for a data set that has spanned records. VSAM access does not support CIACCESS for spanned records. Normal processing is used. Remove the CIACCESS option to avoid This message is informational. AMVSM PREFIX not allowed for access_method access method The VSAM access module was directed to use the VSAMPREFIX option for an access method where it is not valid. The system returns an error to the calling software. Remove the VSAMPREFIX option. AMVSM PREFIX only allowed in READMODE for access_method access method The VSAM access module was directed to use the VSAMPREFIX option for an access method where it is only supported in read mode. The system returns an error to the calling software. Remove the VSAMPREFIX option. AMVSM call_type not allowed with CI ACCESS The VSAM access module was directed to perform the call specified, which is not supported with the CIACCESS option. The system returns an error to the calling software. Remove the CIACCESS option. AMVSM CI processing error <error_message> While processing a control interval, the VSAM access module encountered the specified error. The system returns an error to the calling software. Contact Informatica Global Customer Support. AMVSM PREFIX not allowed with special PowerExchange files The VSAM access module was asked to open a PowerExchange special file with the PREFIX option. The system returns an error to the calling software. Contact Informatica Global Customer Support.
PWX-00100 to PWX-00999
57
AMVSM PREFIX option required for operation operation The VSAM access module was asked to perform the operation specified and the PREFIX option is required for this type of processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. AMVSM record prefix invalid The VSAM access module was asked to operate on a record that contained an invalid record prefix. For example, the first 4 bytes of an RRDS record contain a prefix that must be zero. The system returns an error to the calling software. Attempt to correct the problem and contact Informatica Global Customer Support if unsuccessful. AMVSM error related to empty RRDS processing The VSAM access module function failed because of errors encountered during empty data set processing for an RRDS. The system returns an error to the calling software. Contact Informatica Global Customer Support. AMVSM error is likely opening an empty data set for read The VSAM access module encountered an error that is most likely attempting to open an empty data set for read. The system returns an error to the calling software. Correct and try again. Mandatory parameter parameter_name missing in TO/FROM/CMD definition. Required for access method access_method. A DBMOVE input error occurred. Processing of the DBMOVE command ends. Verify the input. Parameter parameter_name in TO/FROM definition is illegal for access method access_method. A DBMOVE input error occurred. Processing of the DBMOVE command ends. Verify the input. Parameters parameter_name in TO/FROM/CMD definition are mutually exclusive for access method access_method. A DBMOVE input error occurred. Processing of the DBMOVE command ends. Verify the input.
58
PWX-00803 Explanation: System Action: User Response: PWX-00804 Explanation: System Action: User Response: PWX-00805 Explanation: System Action: User Response: PWX-00806 Explanation: System Action: User Response: PWX-00807 Explanation: System Action: User Response: PWX-00808 Explanation: System Action: User Response: PWX-00809 Explanation: System Action: User Response: PWX-00810 Explanation: System Action: User Response: PWX-00811 Explanation:
Loader option parameter_name=parameter_value is not valid for access method access_method. A DBMOVE input error occurred. Processing of the DBMOVE command ends. Verify the input. TYPE=GLOBAL not applicable for MV. A DBMOVE input error occurred. - TYPE=GLOBAL is not implemented for MV. Processing of the DBMOVE command ends. Verify the input. Mapping to table table_name not in destination list. A table specified in the TO field mapping does not exist in the target list. Processing of the DBMOVE command ends. Check command set input. It is likely that a generated command set was manually altered. Syntax error in MAP instruction. Syntax error in the field mapping part of the command set. Processing of the DBMOVE command ends. Check command set input. APPLY requires source type CAPX/CAPXRT The FROM source type for the APPLY is not CAPX or CAPXRT or EMR. Processing of the DBMOVE command ends. Verify the input. TIMEOUTS is out of range in TO/FROM/CMD data definition. A DBMOVE input error occurred. Processing of the DBMOVE command ends. Verify the input. Both PWD and EPWD options are specified. Only one is permitted. PWD= and EPWD= have both been specified in DBMOVE parameters. Processing of the DBMOVE command ends. Specify DBMOVE with one of the specified options only. Decryption failed for an encrypted password An encrypted password specified in a dbconnection or repository user ID was invalid. Processing of the DBMOVE command ends. PowerExchange issues an error message. Contact Informatica Global Customer Support. Encryption failed for a plaintext password Password encryption failed when saving a command set created with the PowerExchange Navigator.
PWX-00100 to PWX-00999
59
The command set is not saved. Contact Informatica Global Customer Support. COMMIT count not compatible with PROCMODE Parameter COMMIT is not valid for APPLY Processing of the DBMOVE command ends. Verify the input. Missing encryption level for encryption type encryption_type. For the selected encryption type a mandatory encryption level must be entered. Validation fails. Ensure that a valid value is entered for parameter ENCRYPTLEVEL in the DBMOVER configuration file. Encryption type ENCRYPTTYPE is not supported on this platform. The selected encryption type is not supported on this platform. Validation fails. Enter a supported encryption type for this platform. Both keyword and keyword keywords are specified. Only one is permitted. The specified keywords, which are in the DBMOVER or PWXCCL configuration file, are mutually exclusive. Only one of these keywords is allowed. PowerExchange ignores the specified keywords. Enter only one of the keywords. Cumulative length of Oracle overrides is too long. A DBMOVE statement contains Oracle overrides where the cumulative length is too long. PowerExchange does not execute the statement. Resolve and retry. DBMOVE MQRESTART parameter required with MQ NRDB TARGETS. A DBMOVE statement contains CAPX or CAPXRT sources with AMLG type targets requires a DBMOVE MQRESTART parameter when the MQRESTART= parameter is specified in the DBMOVER configuration file. PowerExchange does not execute the statement. Resolve and retry. MQRESTART is not supported on this platform. MQRESTART is not supported on this platform. PowerExchange does not execute the statement. Contact Informatica Global Customer Support. Command list list_number targets both destination_table_name and destination_table_name. MQRESTART is not supported with multiple destinations.
System Action: User Response: PWX-00818 Explanation: System Action: User Response: PWX-00819 Explanation:
60
System Action: User Response: PWX-00820 Explanation: User Response: PWX-00821 Explanation: System Action: User Response: PWX-00822 Explanation: User Response:
PowerExchange does not execute the statement. Separate into multiple MV commands and rerun. Termination errors. Messages following this one are related to termination. No response is required. DBMOVE MQRESTART parameter specifies Y without MQ NRDB TARGETS. A DBMOVE statement contains CAPX or CAPXRT sources with AMLG type targets specifying MQRESTART=(Y) is not targeting MQ. PowerExchange does not execute the statement. Resolve and retry. DBMOVE MQRESTART providing restart information. The DBMOVE command is using MQ restart to provide restart information. No response is required unless this was not desired, then specify the DBMOVE TO parameter MQRESTART=(N) or remove the MQRESTART parameter from the DBMOVER configuration file. Override parameter parameter_name in TO/FROM definition is illegal for access method access_method. A DBMOVE input error occurred. Processing of the DBMOVE command ends. Verify the input. DBMOVE: Both DBN2 old_parameter and APPN new_parameter specify an application name. An application name was specified in both the DBN2 and the APPN parameters. Processing of the DBMOVE command ends abnormally. Specify the application name in either the DBN2 or the APPN parameter only. AMVSM OPEN warning: RC=return_code RSN=reason_code for file=file name The VSAM access module encountered a warning when opening a data set. For information about the return and reason codes, see the IBM documentation, DFSMS Macro Instructions for Data Sets. PowerExchange writes the message to the PowerExchange log. Processing continues. No response is required. AMVSM OPEN warning: unusable file file name opened for input The VSAM access module encountered a warning indicating an unusable data set was opened for input. PowerExchange writes the message to the PowerExchange log. Processing continues. No response is required. AMVSM OPEN warning: file file name has empty alternate indexes The VSAM access module encountered a warning indicating there are empty alternate indexes associated with the data set being opened.
PWX-00100 to PWX-00999 61
PowerExchange writes the message to the PowerExchange log. Processing continues. Any empty upgrade alternate index is not updated and a BLDINDEX is required to reflect the inserts. Memory error. Invalid length number bytes requested in pool poolid. 0 or negative bytes of memory have been requested. Processing ends. Contact Informatica Global Customer Support with details. Check for unterminated strings in any generated SQL supplied on any calls. Memory error. Invalid poolname poolid. Invalid poolid specified on request for memory. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Request request_type for shared memory failed. Error = error. Errno = error_number. A request for shared memory used for intertask communication failed. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Request for unsupported function. Unknown request. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Could not allocate number bytes for pool poolid. Insufficient resources to allocate requested memory. Processing ends. Ensure that sufficient resources are available to the process. Memory error. Address address for free is invalid. The memory to be freed is either invalid or was corrupted. Contact Informatica Global Customer Support with details. Memory error. Attempt to allocate duplicate element pool element_pool_id in pool poolid. The requested unique element pool already exists. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Invalid element poolid element_poolid in pool poolid. The request for an element pool specified a bad poolid. Processing ends. Contact Informatica Global Customer Support with details.
PWX-00901 Explanation: System Action: User Response: PWX-00902 Explanation: System Action: User Response: PWX-00903 Explanation: System Action: User Response: PWX-00904 Explanation: System Action: User Response: PWX-00905 Explanation: User Response: PWX-00906 Explanation: System Action: User Response: PWX-00907 Explanation: System Action: User Response:
62
PWX-00908 Explanation: System Action: User Response: PWX-00909 Explanation: System Action: User Response: PWX-00910 Explanation: System Action: User Response: PWX-00911 Explanation: System Action: User Response: PWX-00912 Explanation: System Action: User Response: PWX-00913 Explanation: System Action: User Response: PWX-00914 Explanation: System Action: User Response: PWX-00915 Explanation: System Action:
Memory error. Min/max size invalid for element poolid element_poolid in pool poolid. The Min/Max sizes for an automatic pool are inconsistent. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Attempt to allocate fixed element from automatic poolid element_poolid in pool poolid. An attempt was made to allocate a fixed element from an automatic pool. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Attempt to allocate automatic element of size nbytes from fixed poolid sub_poolid in pool poolid. An attempt was made to allocate an automatic element in a fixed element pool. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Automatic element size of length nbytes exceeds maximum for poolid element_poolid in pool poolid. The automatic element to be allocated exceeds the maximum size allowed for the element pool. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Could not create unique poolid using poolid. A duplicate poolid was encountered while creating unique pools. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Corrupt block at MemoryAddress in pool poolid. Length=NumberofBytes. An unexpected error occurred while a task has attempted to free some previously allocated memory. The process continues freeing any allocated memory. Contact Informatica Global Customer Support with details. Memory error. Address MemoryAddress is not on free chain, pool poolid, length=NumberOfBytes. An unexpected error occurred while a task has attempted to free some previously allocated memory. Processing ends. Contact Informatica Global Customer Support with details. Memory error. Total memory allocated less than zero. An unexpected error occurred while a task has attempted to allocate some memory. Processing ends.
PWX-00100 to PWX-00999
63
User Response: PWX-00930 Explanation: System Action: User Response: PWX-00931 Explanation: System Action: User Response:
Contact Informatica Global Customer Support with details. Input processor error. Initialization failure. A previously reported error has caused the initialization step of the task to end. Processing ends. Contact Informatica Global Customer Support with details. Input processor error. Cmdtab overflow. Adjust nentries on INP_DECLARE_CMDTABLE. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab is empty. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab missing INP_START_CMDTABLE. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab must contain at least one command definition. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab sequence error. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details.
64
Input processor error. Cmdtab duplicate key/sublist name ListName. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab error. No target defined. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab error. Illegal nested array. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab table error. Target outside range of base struct. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab table error. No target length defined. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab table error. Stack overflow. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends.
PWX-00100 to PWX-00999
65
User Response:
Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab table error. Stack underflow. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab table error. Statement definition with callback only allowed at level 0. Row RowNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor. Normal end of input. This is an informational message issued by the software when tracing is active. No response is required. Input error. File file_name. Line LineNumber. An unexpected error occurred during the initialization step of the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input syntax error at position ColumnNumber. Illegal character. A character was found in an input file that was not expected at that position. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input error. Too many tokens. An error was found on the input file where a parameter value has too many tokens specified. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double
66
quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. PWX-00948 Explanation: System Action: User Response: Input error. Statement too long. An error was found on the input file where a parameter value is longer than expected. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Missing double-quote at end of input statement. An error was found on the input file where a parameter is missing a double quote to terminate a string of characters. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input syntax error at position position. Too many levels of nesting. The level of nesting contained within the input file exceeds the maximum expected by the software. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Missing ')' at end of input statement. An error was found on the input file where a parameter is missing a) to terminate a value. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Hex token missing closing quote. Position position. An error was found on the input file where a hex parameter is missing a closing quote to terminate a string of hex characters. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details.
PWX-00100 to PWX-00999
67
Hex token does not contain an even number of bytes. Position position. An error was found in the input file where a string of hex characters does not contain an even number of characters. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Hex token contains invalid hex digits. Position position. An error was found in the input file where a string of hex characters contains an invalid hex character. Valid hex characters are A through F or 0 through 9. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input processor error. Cmdtab error. Conflicting validation options. Row RowNumber. An error was found in the validation processing for an input table. Processing ends. Contact Informatica Global Customer Support with details. A valid command set name must be supplied. An attempt was to run a task without specifying the name of the command set file. Processing ends. Rerun the task specifying the name of the command set file. Input error. File file_name is empty. An attempt was to run a task where the command set file contains no records. Processing ends. Rerun the task specifying the name of a command set file that contains valid information. Input processor error. Cmdtab missing INP_END_CMDTABLE. An error was found in the validation processing for an input table. Processing ends. Contact Informatica Global Customer Support with details. Mandatory parameter ParameterName not specified. The task expected to find the specified parameter in the input file, but no reference to the parameter was found. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details.
68
Input error. File file_name. Statement statement. Line LineNumber. An error was found in the validation processing for an input table. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Input error. Validation error code ErrorCode. An error was found in the validation processing for an input table. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Invalid value specified for parameter parameter. Position position. Value value. An invalid value was specified for the parameter shown at the position indicated. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Value specified for parameter parameter is too long. Position position. The value specified for the parameter shown is longer than expected. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Non-integral value specified for parameter parameter. Position position. Value value. An invalid value was specified for the parameter shown at the position indicated. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Value specified for parameter parameter is out of range. Position position. Value value. An invalid value was specified for the parameter shown at the position indicated. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details.
PWX-00100 to PWX-00999
69
Unexpected keyword parameter parameter=. Position position. An unexpected keyword was specified in the input file for the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Error parameter= sublist limit exceeded. Position position. An excess of parameters was specified within a list in the input file for the task. Processing ends. Correct the input file for the process and submit the task again, paying attention to any documented limits. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Unexpected positional parameter parameter. Position position. An unexpected positional parameter was specified in the input file for the task. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Error returned from input callback function. An internal error occurred while processing the input file. Processing ends. Contact Informatica Global Customer Support with details Too many NODE parms specified. Maximum number of NODES=MaximumNodes. The input file contains too many NODE statements. The current maximum permitted is shown in the error message. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. request_type is not allowed for access method access_method. The information request specified is not valid for the access method chosen. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details.
70
IP Address not valid dotted-decimal IP_Address. The input file contains an IP address that does not conform to the standard format of n.n.n.n. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. <journal_name> is wrong length for a journal name The input file contains an entry for the specified journal name, which is invalid for the operating system. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. <journal_name_qualifier> is wrong length for a journal name qualifier qualifier The input file contains an entry for the specified journal name qualifier, which is invalid for the operating system. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. <journal_name> has too many separators for a journal name The input file contains an entry for the specified journal name, which is invalid for the operating system. Processing ends. Correct the input file for the process and submit the task again. If there are non-standard characters in the input (such as brackets, quotes, back slashes) enclose that token in double quotes and retry. If the error recurs, contact Informatica Global Customer Support with details. Missing encryption level for encryption type ENCRYPTTYPE. For the selected encryption type a mandatory encryption level must be entered. Validation fails. Ensure that a valid value is entered for parameter ENCRYPTLEVEL in the DBMOVER configuration file. Encryption type ENCRYPTTYPE is not supported on this platform. The selected encryption type is not supported on this platform. Validation fails. Enter a supported encryption type for this platform.
PWX-00100 to PWX-00999
71
PWX-00980 Explanation: System Action: User Response: PWX-00981 Explanation: System Action: User Response: PWX-00982 Explanation: System Action: User Response: PWX-00983 Explanation: System Action: User Response: PWX-00984 Explanation: System Action: User Response: PWX-00985 Explanation: System Action: User Response: PWX-00986 Explanation:
Error on ICUCONVERTER(code_page_number, command, name, minimum_bytes, maximum_bytes, space_character_hex). An error occurred performing this command on the code page. Validation fails. Fix the invalid parameter. Error on ICUALIAS(code_page_number, command, alias,alias_type). An error occurred when processing this alias. Validation fails. Fix the invalid parameter. Invalid nameless code page number code_page_number on ICUCNVPROPERTY(code_page_number,name,value). The code page number for the property is not in use because it does not have a name Validation fails. Fix the invalid parameter. Error on ICUCNVPROPERTY(code_page_number,name, value). An error occurred when processing this ICU converter property. Validation fails. Fix the invalid parameter. Invalid space character hex space_character_hex. The hex of the space character is not valid. It must have an even number of characters between 2 and 20 and be formed of valid hex characters 0 to 9 or A to F. Validation fails. Fix the invalid parameter. code page number code_page_number does not lie in ICU user-defined CPN range from low_code_page_number to high_code_page_number. The code page number is not in the required range for ICU user-defined code pages. PowerExchange returns an error code and message, and abends. Fix the invalid parameter. Unable to convert space character hex space_character_hex in code page number code_page_number to a single UTF-8 character. The space character is the user-defined ICU code page did not successfully convert to UTF-8. This could be caused by a failure to load binary CNV file from the ICU data directory, or because the space character is invalid. Validation fails. Fix the invalid parameter.
72
PWX-00987 Explanation: System Action: User Response: PWX-00988 Explanation: System Action: User Response: PWX-00989 Explanation: System Action: User Response: PWX-00990 Explanation: System Action: User Response: PWX-00991 Explanation: System Action: User Response: PWX-00992 Explanation: System Action: User Response: PWX-00993 Explanation: System Action: User Response:
Error on ICUCONVERTER ADD. Code page number code_page_number is already in use with name name. The code page number is already in use because it has a name, so it is not valid to add another converter using this CPN. PowerExchange returns an error code and message, and abends. Fix the invalid parameter. Code page number code_page_number is not an existing named code page. The code page number is not in use because it does not have a name, so it is not valid to add aliases to it. PowerExchange returns an error code and message, and abends. Fix the invalid parameter. Error on ICUCONVERTER(code_page_number, command). An error occurred performing this command on the code page. Validation fails. Fix the invalid parameter. Error on ICUALIAS(code_page_number,command). An error occurred when processing this alias. Validation fails. Fix the invalid parameter. Alias missing on ICUALIAS(code_page_number,command). An alias was not specified in the 3rd parameter position. Validation fails. Fix the invalid parameter. Valid ICUCNVPROPERTY names are names. Lists the valid ICUCNVPROPERTY names. Message is output when a validation check on ICUCNVPROPERTY fails. Fix the invalid parameter. Duplicate keyword parameter parameter=. Position position. A duplicate keyword was specified in the input file for the task. Processing ends. Correct the input file for the process and submit the task again. If the error recurs, contact Informatica Global Customer Support with details. Invalid alias type type. Valid types are types_list. The optional alias type is invalid. It is not on the list of valid alias types also displayed in this message. Processing ends. Fix the invalid 4th sub-parameter by either supplying a valid type from the list or deleting it.
PWX-00100 to PWX-00999
73
CAPI_CONNECTION name CAPI_name appears more than once. The reported CAPI_CONNECTION name appears more than once. Message is output when a validation check fails. Fix the invalid parameter. CAPI_CONNECTION CAPI_name CAPINAME parameter reference is invalid. The reported CAPI_CONNECTION name contains an invalid CAPINAME reference. Message is output when a validation check fails. Fix the invalid parameter. Program logic error. Prog=Program. Line=LineNumber. P1=AdditionalInfo#1. P2= AdditionalInfo#2. An unexpected error occurred during normal processing. Processing ends. Contact Informatica Global Customer Support and report the error with any additional details provided. Split only valid for SEQ/TXT access methods The split option, which spreads output across multiple files, is valid for sequential or text output access methods only. DBMOVE aborts without transferring any data. Change the target type or split option.
PWX-01000 to PWX-01999
PWX-01201 Explanation: System Action: User Response: DTLNET Failed Windows Startup The task failed to start up correctly due to an error with the network. The task ends. Try the request again. If the task fails to start again, contact Informatica Global Customer Support. DTLNET Connect Waiting The software is waiting for a connection between the client and the server to be established. Processing continues. No response is required. DTLNET Request time out (see CFG timeout values) No response was received from the server during the time period specified in the PowerExchange configuration file. The task ends. If the network is busy, retry the request. Otherwise, change that the timeout values specified in the PowerExchange configuration files on client and server so that they are sufficient for processing to complete.
74
DTLNET Received length is not as expected The amount of data expected by the client from the server was different to that actually received. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Trying to Send when not in Send-State The software has issued a request to send data when the client is not in send mode. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Select error on receive An error occurred with the communications between the client and the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Received SEND_ERROR from partner The client has received an error while data was being sent by the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Failed to acquire client TCPIP address The software was unable to determine the IP address for the client. The task ends. Ensure that the client has got an IP address configured and try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET No matching NODE in CFG No corresponding entry was found in either the PowerExchange configuration file or the repository, if enabled, for the IP address. The task ends. Update the PowerExchange configuration file or repository as required and try the request again. DTLNET Failed to allocate memory The task has failed to allocate enough memory to perform the required function. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Listener Complete of Handover Failed An unexpected error occurred during the transmission of data. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support.
PWX-01000 to PWX-01999
75
DTLNET Polling failed, insufficient memory The task has failed to allocate enough memory to perform the required function. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Trying to Receive when not in receive_state The software has issued a request to receive data when the client is not in receive mode. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Receive failed to turn line around The task has failed while changing from send mode to receive mode. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Missing or invalid data length The task expected to either send or receive a number of bytes. This information was not available to the task. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Missing or invalid data pointer The task expected to either send or receive a number of bytes. This information was not available to the task. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Connect failed The task failed while attempting to connect to the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Initial Send failed During the initialization of the task, the client and the server initiate communications. The initial send request by the client failed to reach the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Initial Receive failed During the initialization of the task, the client and the server initiate communications. The initial receive request by the client failed to reach the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support.
76
DTLNET Send failed During the processing of the task, the client and the server communications failed. The send request by the client failed to reach the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Receive failed During the processing of the task, the client and the server communications failed. The receive request by the client failed to reach the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Disconnect failed During the processing of the task, the client and the server communications failed. The disconnect request by the client failed to reach the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Send Error failed During the processing of the task, the client and the server communications failed. The send error request by the client failed to reach the server. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Givesocket failed During the processing of the task, the client and the server communications failed. The give Socket request by the client failed. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Accept failed During the processing of the task, the client and the server communications failed. The accept request by the client failed. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Take Socket failed During the processing of the task, the client and the server communications failed. The take Socket request by the client failed. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Remote User Application Error The task received an error from a user application running on the server. The task ends.
PWX-01000 to PWX-01999
77
User Response:
Correct the user application and try the request again. If the task fails again, contact Informatica Global Customer Support for further guidance. DTLNET Remote Application Manager failed to load The task received an error while attempting to start a user application running on the server. The task ends. Correct the user application and try the request again. If the task fails again, contact Informatica Global Customer Support for further guidance. DTLNET No Data Received The task expected to receive a number of bytes. This information was not available to the task. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Remote Application Data Length error The amount of data expected by the client from the server was different to that actually received. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET Remote DB request not OPEN or FINDNEXT A request was received that was not expected. Only OPEN or FINDNEXT requests are expected. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET gethostname() failure No host name information was returned for the IP address supplied to the task. The task ends. Ensure that all TCP/IP configuration is correct and try the request again. If the task fails again, contact Informatica Global Customer Support. DTLNET GEN_EncryptBSAFE failure Function GEN_EncryptBSAFE returned an error The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DTLNET GEN_DecryptBSAFE failure Function GEN_DecryptBSAFE returned an error The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
78
DTLNET DB request terminated as encryption type is not supported. The encryption type is not supported. The task that encounters the error ends. Set an encryption type supported on the required platform. DTLNET SSL not supported on this platform. Request=request_type. SSL (secure sockets) is not supported on this platform but a request has come in from a client node that expects to use SSL. The task that encounters the error ends. Remove the SSL sub-parameter from the NODE statement in the remote machine. DTLNET Accept time out during SELECT When the PowerExchange Listener was accepting a new work request on one of its ports, a timeout occurred while executing the sockets SELECT command. After a 15 second pause, the incoming work request was rejected and the PowerExchange Listener polls for new work. This usually indicates that a network problem. DTLNET Accept time out during RECV of header. Expected bytes. Received bytes bytes. When the PowerExchange Listener was accepting a new work request on one of its ports, a timeout occurred while executing the sockets RECV command to get the first packet. After a 15 second pause, the incoming work request was rejected and the PowerExchange Listener polls for new work. This message might be caused by a network problem but more likely might indicate that a packet was received that was smaller than the PowerExchange Listener was expecting from a PowerExchange client. For example: 1. A client process such as DTLREXE sends a request to a NODE configured for SSL but the PowerExchange Listener was not configured for SLL. Check that the NODE statement in the client PowerExchange configuration file matches the PowerExchange Listener statement in the PowerExchange Listener configuration file. SSL should be present in both or absent in both. 2. If the PowerExchange Listener received a packet from a non-PowerExchange client, such as a port sniffer.
DTLNET Accept time out during RECV of data. Expected bytes. Received bytes bytes. When the PowerExchange Listener was accepting a new work request on one of its ports, a timeout occurred while executing the sockets RECV command to get the data packet. After a 15 second pause, the incoming work request was rejected and the PowerExchange Listener polls for new work. This message is not likely to happen because PowerExchange client programs do not usually send data packets on connection processing. Contact Informatica Global Customer Support DTLNET Receive time out during SELECT No network activity was detected by the sockets SELECT verb during the time period specified in the PowerExchange configuration file. The receive request fails and The task ends.
PWX-01000 to PWX-01999
79
User Response:
If the network is busy, retry the request. Otherwise, increment the receive seconds value in the TIMEOUTS parameter in the PowerExchange configuration files on client and server so that they are sufficient for processing to complete. DTLNET Receive time out during RECV of header. Expected bytes. Received bytes bytes. No network activity was detected by the sockets RECV verb during the time period specified in the PowerExchange configuration file while it was getting the header packet. The receive request fails and The task ends. If the network is busy, retry the request. Otherwise, increment the receive seconds value in the TIMEOUTS parameter in the PowerExchange configuration files on client and server so that they are sufficient for processing to complete. DTLNET Receive time out during RECV of data. Expected bytes. Received bytes bytes. No network activity was detected by the sockets RECV verb during the time period specified in the PowerExchange configuration file while it was getting the data packet. The receive request fails and The task ends. If the network is busy, retry the request. Otherwise, increment the receive seconds value in the TIMEOUTS parameter in the PowerExchange configuration files on client and server so that they are sufficient for processing to complete. DBNTC Failed to initialize communications to location Location, reason codes ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during the initialization of communications to the location given. Previous error messages should provide more information about the specified reason codes. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Failed to connect communications to location Location, reason codes ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during the connection to the location given. Previous error messages should provide more information about the specified reason codes. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Initial TaskStep CONVERSE failed to location Location, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during communications to the location given. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Internal Length error STD local=LocalLength, received RemoteLength. An internal process has found that there is a difference between the client and server software. The task ends.
80
User Response:
Ensure that both client and server are running the same release of the software. If they are, contact Informatica Global Customer Support and report the error. DBNTL Internal Length error IBMD local=LocalLength, received RemoteLength. An internal process has found that there is a difference between the client and server software. The task ends. Ensure that both client and server are running the same release of the software. If they are, contact Informatica Global Customer Support and report the error. DBNTL Initial Request not OPEN or FINDNEXT DB_Request. A request was received that was not expected. Only OPEN or FINDNEXT requests are expected. The task ends. Try the request again. If the task fails again, contact Informatica Global Customer Support. DBNTL Receive SQL for file file_name failed, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during communications while processing an SQL request for the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Failed to get storage for SQL for file file_name The task was unable to allocate sufficient memory required. The task ends. Try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Send of COLDSC failed DB file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during communications while processing a Column Describe request for the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Premature end of conversation received file file_name. Error(s) have occurred during communications causing the communications to stop. Previous error messages provide more information. The task ends. Correct any errors and try the request again. If the task fails again contact Informatica Global Customer Support.
PWX-01000 to PWX-01999
81
DBNTC Describe CONVERSE failed to location Location, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during communications while processing a Converse request for the location shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Col Entry length mismatch, local=LocalLength, remote=RemoteLength. An internal process has found that there is a difference between the client and server software. The task ends. Ensure that both client and server are running the same release of the software. If they are, contact Informatica Global Customer Support and report the error. DBNTC Describe failed DB file_name, NCOLs is zero. A describe of the file_name has failed to return any column metadata information required for the software. The task ends. Ensure that the file_name is valid and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Receive next request for file file_name failed, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Receive READ bad length length file file_name received, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Send READ header for file file_name failed, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support.
82
DBNTC Receive READ header for file file_name failed, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Send CLOSE header for file file_name failed, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Disconnect error for file file_name failed, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Receive WRITE data failed for file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Send failed for file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Converse for final WRITE failed for file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support.
PWX-01000 to PWX-01999
83
DBNTC ROLLBACK failed file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC ROLLBACK failed for file file_name, partner errors rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Operation Failed for file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC ExecSQL failed for file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Failed Final Insert send for file file_name, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. Application buffer size of buffer_size is too small.
Recommend = required_size . Check client config file APPBUFSIZE.
PWX-01277
Explanation: System Action: User Response:
The size of the application buffer specified in the PowerExchange configuration file is too small. The task ends. Correct the size of the buffer specified in the PowerExchange configuration file and try the request again.
84
DBNTC Flush of send buffer failed for file file_name. Rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Operation failed for file file_name. Rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTC Operation failed for file file_name due to a communications error. Rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL Received unexpected request request_type (description) from client. An unexpected request was received by the task. The task ends. Contact Informatica Global Customer Support DBNTC Describe PARAMETER RECEIVE failed to location Location, rcs ReasonCode1/ReasonCode2/ReasonCode3. Error(s) have occurred during processing of the file shown. Previous error messages should provide further information on the reason code(s) shown. The task ends. Correct the errors and try the request again. If the task fails again contact Informatica Global Customer Support. DBNTL DBCB number must be between 1 and Maximum_DBCB_Slots. A connection was made with a number outside of the range permitted. The current maximum is 16. The task ends. Contact Informatica Global Customer Support. DBNTL Open or FINDNEXT must be first request for a DBCB under a connection. A request was received that was not expected. Only OPEN or FINDNEXT requests are expected. The task ends.
PWX-01000 to PWX-01999
85
User Response: PWX-01285 Explanation: System Action: User Response: PWX-01286 Explanation: System Action: User Response: PWX-01287 Explanation: System Action: User Response: PWX-01288 Explanation: System Action: User Response: PWX-01289 Explanation: System Action: User Response: PWX-01290 Explanation: System Action: User Response:
Try the request again. If the task fails again, contact Informatica Global Customer Support. DBNT Process detected invalid presence direction of Direction. An unexpected error occurred during the communication. The task ends. Contact Informatica Global Customer Support DBNT2 Failed to create varstring for Variable. Program ProgramName, line number LineNumber. An internal error occurred during the processing of the task. The task ends. Contact Informatica Global Customer Support. DBNT Invalid presence type of PresenceType detected. An internal error occurred during the processing of the task. The task ends. Contact Informatica Global Customer Support. DBNTL Operator close met in function for file file_name The task has ended because the PowerExchange Listener under which the task was running was ended. The task ends. No response is required. DBNTC Connection target is IP_name IP_addr Port <port> PowerExchange was unable to contact the specified address and port. Processing ends. PowerExchange reports an error. Ensure that desired address is available with PowerExchange Listener running. DBNTC Receive error for file location - No user Data returned, rcs return_code1/return_code2/return_code3. Expected data from network receive not found. Processing ends. PowerExchange reports an error. Gather all log information and report problem to product Informatica Global Customer Support. DBNTC Error translating field. An error occurred translating characters from one code page to another. Processing ends. PowerExchange reports an error. See associated error message for more details of the error that includes the source and target code pages, error information reported by ICU and the first 100 bytes of the problem data. If the error occurred on multibyte SQL, check that the CODEPAGE parameter specifies a multibyte code page for SQL on both the source and target machines.
86
DBNTC Error found column column_name length length exceeds Table table_name Rowlength row_length. An error occurred while PowerExchange was calculating a variable column length. Inclusion of a variable length column in the mapping resulted in a calculated column length that is too long for the row being mapped. Processing ends. PowerExchange reports an error. Collect log information. Then, report the problem to Informatica Global Customer Support. DBNTC Error found column column_name length length exceeds Table table_name Collength column_length. The length of the data that PowerExchange received for column is longer than the column length in the mapping. Processing ends. PowerExchange reports an error. Collect log information. Then, report the problem to Informatica Global Customer Support. The network buffer length (APPBUFSIZE) maybe too small for good performance. Recommend at least n bytes. If the application buffer size specified in the PowerExchange DBMOVER configuration file cannot hold two data rows of maximum size, it might be too small for good performance when you use offload processing. Processing continues. If you use offload processing for a session that requires tuning to improve throughput, increase the size of the APPBUFSIZE parameter in the PowerExchange DBMOVER configuration file to at least the recommended value. For more information about tuning CDC offload processing, see the platform-specific CDC Guide. For more information about tuning bulk data offload processing, see the PowerExchange Bulk Data Movement Guide. Parameters parm_name and parm_name2 mutually exclusive Use of both parameters together as dbmove arguments is not allowed Processing ends. PowerExchange reports an error. Decide which parameter was intended and use only that one. Memory allocation error creating Valid Add Field List Out of memory, while creating a valid list of fields. PowerExchange reports an error and cannot present a list of valid items. This should not occur, Simplify the input records (if possible), upgrade memory or contact Informatica Global Customer Support. Base field base_name for element element in document document does not exist. An element exists that does not have a corresponding field, The field has probably been deleted. Processing continues. PowerExchange reports an error. Perform one of the following actions:
Create the document again. Add the missing field.

PWX-01000 to PWX-01999 87
Delete the element.
Invalid paste operation, details. An attempt was to paste an XML object in a position that is not allowed. PowerExchange reports an error and does not perform the paste operation. See the user documentation to determine what type of paste operations are allowed. Data conversion error 1324 getting element (expression). Reason: Invalid_XML_character. An attempt was to convert data to XML test that cannot be converted. PowerExchange reports an error and then behaves as configured (can be set to terminate, ignore, replace with default, skip the row or replace with null, depending on the field data conversion properties). Correct the input data or change the field conversion properties. Dependency resource_name is marked as hierarchical but other dependencies exist on the same level. An attempt was to create a document with an invalid structure in terms of the record dependency layout (see document properties). If the user clicks OK on the document properties dialog box, PowerExchange reports an error. The document is not created. See the documentation and ensure that the document structure is valid. Table or Document not found resource An attempt was to map data using a table or document name that does not exist. PowerExchange reports the error. Processing ends. Verify that the table or document name is correct. Error WHERE clause processing not currently supported for XML documents An attempt was to use a where clause in creating an XML document. This is Not currently supported. PowerExchange reports the error and stops mapping. DBMOVE processing ends. Remove where clause. XML character set identity is not supported An attempt was to use an XMLcharset parameter refers to an unsupported character encoding. PowerExchange reports the error and stops mapping. DBMOVE processing ends. Change the XMLCHARSET parameter to a supported character encoding. Document map as data target not currently supported An attempt was to use an XML document as the data target. PowerExchange reports the error and stops mapping. DBMOVE processing ends. Do not include references to the XML document (or SQL relating to it) in the to section of the dbmove commands, mapping to XML is done at source and should be referred to in the from section.
User Response: PWX-01325 Explanation: System Action: User Response: PWX-01331 Explanation: System Action: User Response: PWX-01335 Explanation: System Action: User Response: PWX-01336 Explanation: System Action: User Response: PWX-01340 Explanation: System Action: User Response:
88
Attributes must always be the top children under the Complex Type they modify. An attribute was created or placed in an invalid position in the document map. Attributes must be the first children of the element that they modify PowerExchange reports the error, The invalid operation is not permitted. Ensure that attributes are positioned correctly within the document definition. XML row data greater than 32K, buffer overflow An attempt was to map more than 32K of XML data in a single document row. PowerExchange reports the error and the move or data extraction ends. Redesign the map to produce smaller document rows. DB_READ_C Maximum Length for Application name is 20 characters. For A CAPX request the Maximum Length for Application name is 20 characters. The request fails. Correct the application/dbname2 and retry. DB_READ_C Application name must be defined. A CAPX request must have an application name provided. The request fails. Provide the application/dbname2 and retry. DB_READ_C Application name must start with an alpha followed by alphanumeric characters which can include _#%$ For a CAPX request, the application name must start with an alpha character, followed by alphanumeric characters, which can include the underline (_), hash (#), percent (%), or dollar ($) characters. The request fails. Correct the application/dbname2 and retry. Repository object is out of date: last updated by user_name A repository object was updated since it was retrieved by the user wishing to update it No response is required. Default repository repository_name is not in the list of repository connection names The name specified in REPOS_DEFAULT_CONNECTION is not defined as a REPOS_CONNECT name in dbmover.cfg. The command or facility ends. Correct the name on REPOS_DEFAULT_CONNECTION, or add a REPOS_CONNECT statement to dbmover.cfg for that name. Repository not found The name specified is not defined as a REPOS_CONNECT name in dbmover.cfg. The command or facility ends. Add a REPOS_CONNECT statement to dbmover.cfg for that name.
System Action: User Response: PWX-01376 Explanation: User Response: PWX-01386 Explanation: System Action: User Response:
PWX-01000 to PWX-01999
89
Repository folder not set This message indicates a system error. The request fails. Contact Informatica Global Customer Support. Inconsistent repository parameters specified command Mutually exclusive parameters were specified on the command line. Program ends. Correct error and retry. Repository parameters not required REPOS= or FOLDER= are not required for this command. Program ends. Correct error and rerun. Conflicting parameters specified Check DBMOVE documentation for correct parameter combinations. Program ends. Correct error and rerun. Repository location invalid This message indicates a system error. The command or facility ends. Contact Informatica Global Customer Support. Repository request failed due to memory error This message indicates a system error. The command or facility ends. Contact Informatica Global Customer Support. Invalid userid or password Either the user ID or password supplied through PowerExchange Navigator or REPOS_CONNECT in configuration was invalid. Repository connection fails. Supply the correct user ID or password and retry. Repository protocol invalid The only valid protocol for repository connection is TCP/IP. Repository connection fails. Specify the REPOS_CONNECT statement with TCP/IP as the protocol.
90
PWX-01426 Explanation: User Response: PWX-01427 Explanation: User Response: PWX-01428 Explanation: User Response: PWX-01429 Explanation: User Response: PWX-01430 Explanation: User Response: PWX-01431 Explanation: User Response: PWX-01432 Explanation: User Response: PWX-01433 Explanation: User Response: PWX-01434 Explanation: User Response: PWX-01435 Explanation: User Response: PWX-01436 Explanation: User Response:
You have insufficient authority for the requested action The user requested an action for a repository object for which they had insufficient authority. No response is required. Duplicate group name specified An attempt was made to add a resource to a group to which it is already a member. No response is required. Group not found This message is issued by the Repository API, and most likely indicates an internal error in PowerExchange. Contact Informatica Global Customer Support. User update failed This message is issued by the repository API, and indicates an internal error. Contact Informatica Global Customer Support. Group update failed This message is issued by the repository API, and indicates an internal error. Contact Informatica Global Customer Support. An attempt to update a repository policy failed This message is issued by the repository API, and indicates an internal error. Contact Informatica Global Customer Support. Repository resource not synchronized An attempt was made to update a repository object that was updated by another user since it was retrieved. Repeat the operation having first reopened the object. Repository folder was not created This message is informational. No response is required. Repository folder name invalid/not found This message is informational. Correct error and retry. Duplicate table name specified The specified table is already defined for the object. No response is required. Connection table not in current context A system error occurred. Contact Informatica Global Customer Support.
PWX-01000 to PWX-01999
91
Folder not set A system error occurred. Contact Informatica Global Customer Support. Table name not specified A system error occurred. Contact Informatica Global Customer Support. Column name not specified A system error occurred. Contact Informatica Global Customer Support. Duplicate column name specified A system error occurred. Contact Informatica Global Customer Support. Columns not found in repository A system error occurred. Contact Informatica Global Customer Support. User not authorized to access resource A system error occurred. Contact Informatica Global Customer Support. Local authority invalid A system error occurred. Contact Informatica Global Customer Support. Duplicate authority specified A system error occurred. Contact Informatica Global Customer Support. OS Login information not found for user A system error occurred. Contact Informatica Global Customer Support. Command set update failed A system error occurred. Contact Informatica Global Customer Support. Session update failed A system error occurred. Contact Informatica Global Customer Support.
92
Duplicate userid specified A system error occurred. Contact Informatica Global Customer Support. Requested userid not found A system error occurred. Contact Informatica Global Customer Support. Duplicate command set specified A system error occurred. Contact Informatica Global Customer Support. Requested command set not found A system error occurred. Contact Informatica Global Customer Support. Requested session not found A system error occurred. Contact Informatica Global Customer Support. Default userid not created A system error occurred. Contact Informatica Global Customer Support. Inconsistent userids specified for local access A system error occurred. Contact Informatica Global Customer Support. Password encryption failed A system error occurred. Contact Informatica Global Customer Support. Password decryption failed A system error occurred. Contact Informatica Global Customer Support. Connection to repository failed A system error occurred. Contact Informatica Global Customer Support. Plaintext and encrypted passwords specified for repository A system error occurred. Contact Informatica Global Customer Support.
PWX-01000 to PWX-01999
93
Duplicate XML name specified A system error occurred. Contact Informatica Global Customer Support. XML Document name not specified A system error occurred. Contact Informatica Global Customer Support. XML Document user name A system error occurred. Contact Informatica Global Customer Support. XML Document description A system error occurred. Contact Informatica Global Customer Support. User user_ID has no authority to create users or groups The user requested an action for a repository object for which they had insufficient authority. No response is required. User user_ID has no authority to execute against dbconnection connection_name The user requested an action for a repository object for which they had insufficient authority. No response is required. XYZ XYZ already exists A system error occurred. Contact Informatica Global Customer Support. Application name A system error occurred. Contact Informatica Global Customer Support. Use User authorization A system error occurred. Contact Informatica Global Customer Support. Xref failed for XYZ XYZ, XYZ XYZ A system error occurred. Contact Informatica Global Customer Support. Repository not available A system error occurred. Contact Informatica Global Customer Support.
94
PWX-01472 Explanation: User Response: PWX-01473 Explanation: User Response: PWX-01481 Explanation: System Action: User Response:
Errors occurred retrieving repository data, DTLDBAPI rcs1/2/3 = return_code1 return_code2 return_code3 A call to retrieve data from the repository failed. The cause of the failure is indicated by the return codes. Disconnect, then reconnect to the repository and try again. Connection to server lost, please reconnect and retry request A call to retrieve data was made when disconnected from the server. Reconnect to the repository and try again. CFG DATERANGE Parameter error - end date not start date. The end date in the DATERANGE parameter in the PowerExchange configuration file must be greater than the start date. PowerExchange displays an error dialog box. Processing abends. Correct the DATERANGE parameter in the PowerExchange configuration file, ensuring the end date is greater than the start date. CFG DEFAULTDATE Parameter error - Invalid date: <date> The date specified in the DEFAULTDATE parameter in the PowerExchange configuration file is not in the valid format, which is YYYYMMDD. PowerExchange displays an error dialog box. Processing abends. Correct the DEFAULTDATE parameter in the PowerExchange configuration file to a valid YYYYMMDD date format. Statement statementid out of sequence loading data map. A statement in the data map is being loaded in the incorrect sequence. Validation fails. If data map was not manually altered, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Full mapname length exceeds length bytes. The mapname length exceeds the permitted value. Validation fails. Enter a valid mapname length. The hexadecimal value specified is invalid. A hexadecimal field value is invalid. Validation fails. Enter a valid hexadecimal value. Record Id value is too long. The value specified for a Record Id field is longer than the field length. Validation fails. Enter a valid Record Id.
PWX-01000 to PWX-01999
95
Record Id value is invalid. The value specified for a Record Id field is not appropriate for the characteristics of the field. Validation fails. Enter a valid Record Id. Field type is not eligible for record Id usage. It is not appropriate to specify a Record Id for the field type. Validation fails. Either remove Record Id or alter the field type. name is not a valid name. Adabas field name is invalid. Validation fails. Ensure that the Adabas name is: two bytes long, first character is an alpha character (except e or E) and the second character is alphanumeric. Invalid field format. The field format string specified for a field is inappropriate to the field's characteristics. Validation fails. Enter a valid field format string. At least one record must be defined. The data map must contain at least one record. Validation fails. Enter a record. The computed length of record record_name is recsize which exceeds the value of maxsize specified in the map properties. A record length was specified for the record, which was exceeded. Validation fails. Check the record structure is correct and the record length specified is correct. Field field_name in record record_name: Type invalid in delimited format record. The record format is delimited, but the field is not an eligible type. Validation fails. Change field properties to make the field an eligible type. Field field_name in record record_name: Record Id field cannot be part of an array. Record Id field is not allowed to be a member of an array. Validation fails. Either remove field from array or remove Record Id.
96
Field field_name in record record_name: Record Id field must be at a fixed offset. If the record is not of a delimited format, the field must be at a fixed offset. Validation fails. Ensure that the field is at a fixed offset if record is not delimited format. Field field_name in record record_name: Variable array count field count_name is not of integral or allowed type. If field is a variable array, then the count field must be of an integral type. Validation fails. Ensure that count field is an integral type. Field field_name in record record_name: Variable length count field count_name is not of integral or allowed type. The count field is not an integral type. Validation fails. Ensure that count field is an integral type. Field field_name in record record_name: Cannot locate array count field count_name. Unable to locate the array count field. Validation fails. Ensure that the array count field precedes the field using it. Field field_name: Cannot locate array count field count_name. Unable to locate the array count field. Validation fails. Ensure that the array count field precedes the field using it. Field field_name in record record_name: Cannot locate variable length count field count_name. Unable to locate the variable length count field. Validation fails. Ensure that the variable length count field precedes the field using it. Field field_name: Cannot locate variable length count field count_name. Unable to locate the variable length count field. Validation fails. Ensure that the variable length count field precedes the field using it. Map contains rec_count records but only numrecid are specified with a Record Id field. Multiple records are defined but they do not all have IDs. Validation fails. Ensure that all records have IDs.
PWX-01000 to PWX-01999
97
At least one table or one document must be defined. The map must contain at least one table or document. Validation fails. Enter a table or document. Base field field_name for column column_name in table table_name does not exist. The base field does not exist for a table column. Validation fails. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Dependency record_name is marked for new_row but other dependencies exist on the same level. When there is more than one dependency at the same level, cannot mark dependent records for new_row. Validation fails. Check how you want to handle multiple instances of the selected record. Dependency record_name is marked for new_row but higher levels have more than one dependency per level. When there is more than one dependency at a higher level, cannot mark dependent records for new_row. Validation fails. Check how you want to handle multiple instances of the selected record. Dependency <record_name1> is marked for new_row and therefore cannot be a dependent of <record_name1> which is an array. The higher level is marked as an Array so the dependent record cannot be marked as New Row. Validation fails. Check how you want to handle multiple instances of the selected record. Segment segment referenced by dependency <record_name1> in table table_name is already referenced by dependency <record_name1>. The segment name was referenced by 2 record dependency. Validation fails. Ensure that a segment is only referenced once in a record dependency. Record dependencies may only be nested to a depth of levels_depth. Number of record dependencies exceeds maximum permitted. Validation fails. Reduce number of record dependencies. Top level of record dependency hierarchy for DL1 is limited to one dependency. Only one record can be defined at top level. Validation fails.
PWX-01522 Explanation: System Action: User Response: PWX-01523 Explanation: System Action: User Response: PWX-01524 Explanation: System Action: User Response: PWX-01525 Explanation: System Action: User Response: PWX-01526 Explanation: System Action: User Response: PWX-01527 Explanation: System Action:
98
User Response: PWX-01528 Explanation: System Action: User Response: PWX-01529 Explanation: User Response: PWX-01530 Explanation: System Action: User Response: PWX-01531 Explanation: System Action: User Response: PWX-01532 Explanation: User Response: PWX-01533 Explanation: System Action: User Response: PWX-01534 Explanation: System Action: User Response: PWX-01535 Explanation: System Action: User Response:
Ensure that only one record is defined at the top level. Field is too long for record Id usage. The field is too long to be used as a record Id. Validation fails. Enter a valid field. Integrity checks on map schema_name.map_name have produced the following warning: Message heads a list of warnings. Check warnings and see specific warning message. Integrity checks on map schema_name.map_name have produced the following error: Message heads a list of errors. Validation fails. Check errors and see specific error message. Field field_name in record record_name has type field_type which is not allowed for a delimited data map. The field type is illegal in a delimited map. Validation fails. Check that field type was entered correctly. Adabas field ada_field_name does not exist in the FDT. Unable to validate Adabas field as does not exist in the FDT. Verify that a refresh of the FDT is necessary. PowerExchange Datatype is not compatible with the FDT definition for Adabas field ada_field_name. The FDT field properties are not compatible with the PowerExchange field properties. Validation fails. Ensure that the PowerExchange field property was set correctly. Field field_name in record record_name is not compatible with the FDT definition for Adabas field ada_field_name. The characteristics of the PowerExchange field definition are compatible with the actual characteristics of the adabas field. Validation fails. Ensure that the PowerExchange field property was set correctly. Adabas field ada_field_name is not an MU or PE. Cannot be defined as an array. The Adabas field must be an MU or PE to defined as array. Validation fails. Check that the Adabas and PowerExchange field definitions are declared correctly.
PWX-01000 to PWX-01999
99
100
Length override is not valid for Adabas field ada_field_name. Using the FDT characteristics, the length override values specified for an Adabas field are not permissible. Validation fails. Check that the Adabas and PowerExchange field definitions are declared correctly. Offset override is not valid for Adabas field ada_field_name. Using the FDT characteristics, the offset override values specified for an Adabas field are not permissible. Validation fails. Check that the Adabas and PowerExchange field definitions are declared correctly. Length or precision exceeds maximum for Adabas field ada_field_name. PowerExchange=value1. Adabas=value2. Using the FDT characteristics, the length or precision exceeds the maximum for an Adabas field. Validation fails. Check that the Adabas and PowerExchange field definitions are declared correctly. Field type is not compatible with the FDT or override length for Adabas field ada_field_name. Effective length = length. The PowerExchange field type and/or length entered is not compatible with the FDT definition. Validation fails. Enter a valid field length or field type combination. Offset override plus PowerExchange length exceeds effective length for Adabas field ada_field_name. Effective length = length. The total PowerExchange length is greater than the FDT definition. Validation fails. Ensure that override length and offset length does not exceed PowerExchange length. Field field_name in record record_name cannot be mapped to Adabas group field ada_grp_field. Group contains multiple value or variable fields. Structure of Adabas group field does not allow field to be mapped. Validation fails. Correct field or group structure. Field field_name in record record_name needs an Adabas name (top level field). The mandatory Adabas Name field is empty. Validation fails. Enter a valid Adabas Name. Field field_name in record record_name: cannot locate null control field null_field. The field is set as a Nullable Field but the corresponding control field cannot be located. Validation fails.
User Response: PWX-01544 Explanation: System Action: User Response: PWX-01545 Explanation: User Response: PWX-01546 Explanation: System Action: User Response: PWX-01547 Explanation: System Action: User Response: PWX-01548 Explanation: System Action: User Response: PWX-01549 Explanation: System Action: User Response: PWX-01550 Explanation: System Action: User Response: PWX-01551 Explanation: System Action: User Response:
Ensure that the corresponding null control field exists. Field field_name in record record_name: cannot locate array null control field null_field. The field is set as a Nullable Field but the corresponding control field cannot be located. Validation fails. Ensure that the corresponding null control field exists. Number of fields in data map record does not match number of columns in table. Cannot check for null values in data. Number of fields in data map record does not match number of columns in table. Cannot check for null values in data. No response is required. Record record_name has a missing Type and/or Expression for Field name field_name. The field is not defined correctly. Validation fails. Enter the field type and/or an expression. Record record_name contains an invalid Field name field_name. The record contains an invalid field name. Validation fails. Enter a valid field name. Record record_name has a missing Phase value. A field containing an expression should have a phase value present. Validation fails. Enter a Phase value. Record record_name contains a duplicate Field name field_name. The record contains a duplicate Field name. Field name must be unique. Validation fails. Ensure that the field names are unique. Record record_name contains a Field named field_name which is not declared. The record contains a reference to an undeclared field name. Validation fails. Ensure that all field names are declared. Record record_name contains the error: error. The record contains an invalid expression. Validation fails. Ensure that only valid expressions are present.
PWX-01000 to PWX-01999
101
Record record_name has a missing Field Name. The record contains a field declaration with no field name. Validation fails. Ensure that all field declarations contain a valid field name. Record record_name requires a Precision value in the range min_range to max_range for Field field_name. The Precision value is not within the valid range. Validation fails. Enter a Precision value within the valid range. Record record_name requires a Scale value in the range min_range to max_range for Field field_name. The Scale value is not within the valid range. Validation fails. Enter a Scale value within the valid range. Record record_name requires a Length value in the range min_range to max_range for Field field_name. The Length value is not within the valid range. Validation fails. Enter a Length value within the valid range. name is not a valid character. Resource name is invalid Validation fails. Ensure that names consist only of characters A through Z, 0 through 9 and underscore. Names must start with an alphabetic character. PowerExchange Datatype is not compatible with the HP data set definition for field field_name. The HP field properties are not compatible with the PowerExchange field properties. Validation fails. Ensure that the PowerExchange field property was set correctly. E field array field_name requires an expression with a physical array field argument. The E field array (such as u1[*]) can only pass validations when the system can determine the array dimensions from a physical field argument within an expression. Validation fails. Ensure that the PowerExchange field property was set correctly. E field array field_name arguments field_name and field_name have different subscript dimensions. If the E field array has more than one physical field argument, then all must have the same array dimensions. The number of subscripts and the maximum number of occurrences at each level must be the same.
102
System Action: User Response: PWX-01560 Explanation: System Action: User Response: PWX-01561 Explanation: System Action: User Response: PWX-01562 Explanation: System Action: User Response: PWX-01563 Explanation: User Response: PWX-01564 Explanation: System Action: User Response: PWX-01565 Explanation: System Action: User Response: PWX-01566 Explanation: System Action: User Response: PWX-01567 Explanation: System Action: User Response: PWX-01568 Explanation:
Validation fails. Ensure that the PowerExchange field property was set correctly. Record record_name is unable to use Field Name field_name. Name being used in CCK processing. A field name is identical to a CCK Expression Field name. This is not permitted. Validation fails. Enter a unique field name that is not used in the record. field_name already exists, please use alternate name. A duplicate name for a resource was entered. Validation fails. Enter a unique resource name. Name field_name is not declared. An expression is referencing an undeclared field name. Validation fails. Ensure that the field referenced in the expression is declared. errormsg. This message is an internal placeholder. No response is required. Please enter a valid field_name name. The name field is empty. Validation fails. Enter a valid field name. Please enter a Precision value in the range min_range to max_range. The Precision value is not within the valid range. Validation fails. Enter a Precision value within the valid range. Please enter a Scale value in the range min_range to max_range. The Scale value is not within the valid range. Validation fails. Enter a Scale value within the valid range. Please enter a Length value in the range min_range to max_range. The Length value is not within the valid range. Validation fails. Enter a Length value within the valid range. Unable to use Field Name field_name. Name being used in CCK processing. It is not allowed to reuse CCK Expression Field names.
PWX-01000 to PWX-01999 103
System Action: User Response: PWX-01569 Explanation: System Action: User Response: PWX-01570 Explanation: System Action: User Response: PWX-01571 Explanation: System Action: User Response: PWX-01572 Explanation: System Action: User Response: PWX-01575 Explanation: System Action: User Response: PWX-01577 Explanation: System Action: User Response: PWX-01578 Explanation: System Action: User Response: PWX-01579 Explanation: User Response: PWX-01580 Explanation:
Validation fails. Enter a unique field name that is not used in the record. Missing Type and/or Expression. The field is not defined correctly. Validation fails. Enter the field type and/or an expression. Invalid Name field_name. The field name contains illegal characters. Validation fails. Enter a valid field name. Missing Phase value. A field containing an expression should have a phase value present. Validation fails. Enter a Phase value. Field Name field_name in record record_name is too long. The field name is too long. Validation fails. Enter a valid field name. Invalid Access Method for Filelist Processing. An invalid access method was selected for file list processing. Validation fails. Enter a valid access method or turn off file list processing. Filelist Processing specified no input files. The file of input files contained no valid files. Validation fails. Specify some valid files in the file list file. Filelist file contains an invalid filename: reason_code. The file of input files contained an invalid file name. Validation fails. Correct the invalid file name in the file list file. Filelist processing added filecount files. The number of valid input files is displayed. If this number is excessively large perhaps an invalid file list file was specified. Filelist Processing supports only read mode. An invalid access mode was selected for file list processing.
104
Validation fails. Filelist processing is only supported for reading. Offload Processing not invoked due to condition condition Offload Processing not used because of conflicting condition. Regular processing occurs. Remove the condition preventing offload processing. These are Parameterized SQL, Data Cleansing or Connection DBCB (this indicates Group Source processing). Several Search Fields defined for table table Only a search field can be associated to an Adabas table. Validation fails. Enter a unique resource name. No matching column in table table for Super Descriptor or part of it table All elements that make up the Super Descriptor must be present as columns. Validation fails. Correct the data map. All the members of field group field must be present in table table All elements of a group that is a Descriptor or a Super Descriptor must be present in the table. Validation fails. Correct the data map. Error error_reason at offset offset in UTF8 text. Length text_length Character length length Record type type. The specified field contains invalid UTF8 text. Data maps that contain a VERSION record must have all fields in the UTF8 code page. For example, characters POUND SIGN must be X'C2A3' and YEN SIGN must be X'C2A5'; a failure occurs if the lead byte is not X'C2'. The error reasons are:
1. 2. 3. 4. 5. System Action: User Response:
Lead byte is greater than X'7F'. Four bytes in character. Unknown character length. Truncated character at end of string. Non-leading byte less than X'80' in multi byte sequence.
The data map is not loaded. Processing ends. If the problem exists in the exported data maps file used by the PowerExchange Listener, then refresh the data map by sending it from the Navigator. If the problem exists in the data map (DMP) file used by the Navigator, then change the DMP file by using an external editor such as Notepad or vi. If a VERSION record is present and the characters are not in UTF8, then it is best to delete the VERSION record, ensure that the characters are in the ISO-8859 code page (on Windows, save as type ANSI), and then edit the map in the Navigator. If that is not successful, correct the invalid characters - either in UTF8 if the VERSION record is present, or in ISO-8859 if the VERSION record is absent.
PWX-01000 to PWX-01999
105
Data Map is not encoded correctly in UTF8 The data map contains a VERSION record and so must be in UTF8 but some bytes break the rules for UTF8. On Windows the problem might be caused by incorrectly saving a DMP file containing a VERSION record as ANSI. The data map is not loaded. Processing ends. If the problem exists in the exported data maps file used by the PowerExchange Listener, then refresh the data map by sending it from the Navigator. If the problem exists in the data map (DMP) file used by the Navigator, then change the DMP file by using an external editor such as Notepad or vi. If a VERSION record is present and the characters are not in UTF8, then it is best to delete the VERSION record, ensure that the characters are in the ISO-8859 code page (on Windows, save as type ANSI), and then edit the map in the Navigator. If that is not successful, correct the invalid characters - either in UTF8 if the VERSION record is present, or in ISO-8859 if the VERSION record is absent.
Save changes to Data Map map_name. The data map is being closed and contains unsaved changes. The system action depends on the user response. Perform one of the following actions:
Yes. Overwrites the file. No. Closes the data map without saving changes. Cancel. Edits the data map. PWX-01601 Explanation: System Action: User Response: PWX-01602 Explanation: System Action: User Response: PWX-01603 Explanation: System Action: User Response: PWX-01604 Explanation: System Action: User Response: PWX-01605 Explanation: System Action:
106
name already exists, please use alternate name. A duplicate name for a resource was entered. Validation fails. Enter a unique resource name. Please enter a Record size in the range min_range to max_range. The record size is not within the valid range. Validation fails. Enter a record size value within the valid range. Please enter a valid separator value. A separator value was not entered. Validation fails. Enter a valid separator value. Please enter a Field position in the range min_range to max_range. The Field position is not within the valid range. Validation fails. Enter a Field position value within the valid range. Please enter a Century value in the range min_range to max_range. The Century value is not within the valid range. Validation fails.
User Response: PWX-01606 Explanation: System Action: User Response: PWX-01607 Explanation: System Action: User Response: PWX-01608 Explanation: System Action: User Response: PWX-01609 Explanation: System Action: User Response: PWX-01610 Explanation: System Action: User Response: PWX-01611 Explanation: System Action: User Response: PWX-01612 Explanation: System Action: User Response: PWX-01613 Explanation: System Action: User Response:
Enter a Century value within the valid range. Please enter a Year value in the range min_range to max_range. The Year value is not within the valid range. Validation fails. Enter a Year value within the valid range. Please enter a Month value in the range min_range to max_range. The Month value is not within the valid range. Validation fails. Enter a Month value within the valid range. Please enter a Day value in the range min_range to max_range. The Day value is not within the valid range. Validation fails. Enter a Day value within the valid range. Please enter a Character Replacement value. A value for Character Replacement is missing. Validation fails. Enter a Character Replacement value. Please enter a Pivot value in the range min_range to max_range. The Pivot value is not within the valid range. Validation fails. Enter a Pivot value within the valid range. Please enter a Length value in the range min_range to max_range. The Length value is not within the valid range. Validation fails. Enter a Length value within the valid range. Please enter a Precision value in the range min_range to max_range. The Precision value is not within the valid range. Validation fails. Enter a Precision value within the valid range. Please enter a Scale value in the range min_range to max_range. The Scale value is not within the valid range. Validation fails. Enter a Scale value within the valid range.
PWX-01000 to PWX-01999
107
Please enter an Array value in the range min_range to max_range. The Array value is not within the valid range. Validation fails. Enter a Array value within the valid range. Please enter a Field Array value in the range min_range to max_range. The Field Array value is not within the valid range. Validation fails. Enter a Field Array value within the valid range. Please enter a valid Count Field value. The Field Array value is not within the valid range. Validation fails. Enter the name of the field that identifies the variable size. name is not a valid base field, please use alternate field. The base field cannot be found in the record definition. Validation fails. Select a base field that is correctly defined in the record. Please enter a valid File Name. The mandatory File Name field is empty. Validation fails. Enter a value for the File Name. Are you sure you want to delete resource name. This message confirms deletion of a resource. The system action depends on the user response. Perform one of the following actions:
Click Yes to delete the resource. Click No to cancel the request. PWX-01620 Explanation: System Action: User Response: PWX-01621 Explanation: System Action: User Response: Please enter a Record Dependency for resource name. At least one record dependency must exist for either a table or a document. Validation fails. Enter a record dependency for the specified resource name. Please enter a PSB name. The mandatory PSB name field must be entered. Validation fails. The system waits for the user response. Enter a value for the PSB name.
108
Please enter a PCB number in the range min_range to max_range. The mandatory PCB number field must be entered. Validation fails. Enter a PCB number value within the valid range. Please enter a valid resource name. The mandatory resource type name is missing and must be entered. Validation fails. Enter a valid name. Data Map map_name already exists in directory directory. Overwrite? A data map with an identical name already exists in the directory. The system action depends on the user response. Perform one of the following actions:

Click Yes to overwrite the data map. Click No to edit the data map properties.
The end of the database has been reached. The end of the database was reached and all the data was returned. No response is required. Do you want to rename the current Data Map from mapname1 to mapname2? Confirm the change of name of an existing data map. The system action depends on the user response. Perform one of the following actions:

Click Yes to rename the data map. Click No to edit the data map properties.
Data map map_name already exists in directory directory and is read only. Confirm the change of name of an existing data map. The system action depends on the user response. Perform one of the following actions:

Click Yes to rename the data map. Click No to edit the data map properties.
Deleting resource name will also delete number xrefs to this item. Continue? Confirm the deletion of a resource, which cause the removal of a number of cross referenced items. Click More PowerExchange to view the list of resources that are removed. The system action depends on the user response. Perform one of the following actions:

Click Yes to delete the item and its dependents. Click No to take no action.
PWX-01000 to PWX-01999
109
To perform a row test, Data Map map_name must be sent to remote location. Do you want to do this? Before performing a row test on a data map, the current version of the map must be sent to the remote location. The system action depends on the user response. Perform one of the following actions:

Click Yes to send the data map to the remote location. Click No to take no action.
Please enter a Segment Name. The mandatory Segment Name field is empty. Validation fails. Enter a value for the Segment Name. Please enter a Command Set Name. The mandatory Command Set Name field is empty. Validation fails. Enter a value for the Command Set Name. Please enter a DB Type. The mandatory DB Type field is empty. Validation fails. Enter a value for the DB Type. Please enter a Table qualifier. The mandatory table qualifier field is empty. Validation fails. Enter a value for the table qualifier. Please enter a Primary value in the range min_range to max_range. The Primary value is not within the valid range. Validation fails. Enter a Primary value within the valid range. Please enter a Secondary value in the range min_range to max_range. The Secondary value is not within the valid range. Validation fails. Enter a Secondary value within the valid range. Please enter a File Position value in the range min_range to max_range. The File Position value is not within the valid range. Validation fails. Enter a File Position value within the valid range.
110
PWX-01637 Explanation: System Action: User Response: PWX-01638 Explanation: System Action: User Response: PWX-01639 Explanation: System Action: User Response: PWX-01640 Explanation: User Response: PWX-01641 Explanation: System Action: User Response: PWX-01642 Explanation: User Response:
Please enter a Record size in the range min_range to max_range. The Record size value is not within the valid range. Validation fails. Enter a Record size value within the valid range. Please enter a Block size in the range min_range to max_range. The Block size value is not within the valid range. Validation fails. Enter a Block size value within the valid range. Please enter a Command Set name and path. The mandatory Command Set name and path field is empty. Validation fails. Enter a value for the Command Set name and path. Command set csname tested successfully!. A dbmove for the command set has completed successfully. No response is required. Please enter a Table name. The mandatory Table name field is empty. Validation fails. Enter a value for the Table name. Command set csname already exists in directory directory and is read only! A file by the same name already exists in the directory and cannot be overwritten as it is read only. To save the command set to the same file name, either delete, rename or write enable the existing file. Command set csname already exists in directory directory. Overwrite? A file by the same name already exists in the directory. Confirm whether to overwrite existing file. The system action depends on the user response. Perform one of the following actions:

Click Yes to overwrite the existing file. Click No to edit the command set properties.
Do you want to rename the current Folder from foldername1 to foldername2? Confirm the change of name of an existing Folder. The system action depends on the user response. Perform one of the following actions:

Click Yes to rename the folder. Click No to edit the folder properties.
PWX-01000 to PWX-01999
111
Save changes to Command Set csname? The Command Set is being closed and contains unsaved changes. The system action depends on the user response. Perform one of the following actions:

Click Yes to save and close the command set. Click No to close the command set without saving. Click Cancel to edit the command set. PWX-01646 Explanation: System Action: User Response: PWX-01647 Explanation: System Action: User Response: PWX-01648 Explanation: User Response: PWX-01649 Explanation: System Action: User Response: PWX-01650 Explanation: System Action: User Response: PWX-01651 Explanation: System Action: User Response: PWX-01652 Explanation: System Action: User Response: Please enter a valid custom SQL statement. The mandatory custom SQL statement is empty. Validation fails. Enter a value for the custom SQL statement. The custom SQL statement entered is too long! The custom SQL statement exceeds the permitted length. Validation fails. Enter a valid custom SQL statement. Command set csname exported to location successfully! This message confirms that the Command Set was successfully exported. No response is required. Please enter a name that is not a Resource folder name. The resource name is the same as the resource folder name. Validation fails. Enter a name that is not a Resource folder name. Please enter a file name which the remote file will be saved as. The mandatory file name is empty. Validation fails. Enter a value for the file name. Please enter a Start value in the range min_range to max_range. The Start value is not within the valid range. Validation fails. Enter a Start value within the valid range. Please enter an End value in the range min_range to max_range. The End value is not within the valid range. Validation fails. Enter a End value within the valid range.
112
No record definitions exist in the source. Check start and end columns. No record definitions exist in the copybook. Stop import of record definitions. Check record definitions exist in the source file and the Column Range values are correct in the Source Details page. The directory directory does not exist, would you like to create it? The directory path does not exist, confirm if the directory should be created. The system action depends on the user response. Perform one of the following actions:
Click Yes to create the directory. Click No to take no action. PWX-01655 Explanation: User Response: PWX-01656 Explanation: User Response: PWX-01657 Explanation: System Action: User Response: PWX-01658 Explanation: System Action: User Response: PWX-01659 Explanation: System Action: User Response: PWX-01660 Explanation: System Action: User Response: The directory directory could not be created, please check supplied directory name. The creation of a missing directory failed. Check the directory name is a valid system directory name. The import process has detected numdefinitions possible definitions of the data item name. The meta data contains multiple definitions of a data item. No response is required. Please select the required definition and resume the import. The import process has detected multiple definitions of a data item and the user is prompted to select required definition. When user has selected required definition continue the import process. Select the required definition from the multiple choices. Confirm you wish to delete Active registration <registration_name>: Making it History instead will retain a record of it. The selected Capture registration is active. Confirm the delete action. PowerExchange waits for user confirmation. Confirm or cancel the request. The line you selected does not correspond to a valid data definition. Please try again. The line selected by the user is not a valid data definition. When use has made a new selection continue the import process. Select the required definition from the multiple choices. Deleting numitems resource_type items will also delete numxrefs xrefs to these items. Continue? Confirmation dialog that selected item(s) and their dependents are to be deleted. Click More Details to view the items to be deleted. The system action depends on the user response. Perform one of the following actions:
Yes. Delete the selected items and their dependents.

PWX-01000 to PWX-01999 113
No. Take no action.
Are you sure you want to delete name?. Confirmation dialog that selected item(s) are to be deleted. The system action depends on the user response. Perform one of the following actions:

Click Yes to delete the selected items and their dependents. Click No to take no action.
resource_type will be pasted There are multiple positions the clipboard item(s) can be pasted. Select a relative position and click OK to continue with the paste. The system action depends on the user response. Perform one of the following actions:

Click OK to paste the item from the clipboard to the selected position. Click Cancel to take no action.
114
Please enter a Position value in the range min_range to max_range. The Position value is not within the valid range. Validation fails. Enter a Position value within the valid range. Please enter a Length value in the range min_range to max_range. The Length value is not within the valid range. Validation fails. Enter a Length value within the valid range. Please enter a Name. The mandatory Name field is empty. Validation fails. Enter a value for the Name. The field contains the invalid character character. The field contains the identified illegal character. Validation fails. Enter a valid string containing no illegal characters. Please enter a configuration Name. The mandatory configuration Name field is empty. Validation fails. Enter a value for the configuration Name. Please enter a configuration Path Name. The mandatory configuration Path Name field is empty. Validation fails.
User Response: PWX-01669 Explanation: System Action: User Response: PWX-01670 Explanation: System Action: User Response: PWX-01671 Explanation: System Action: User Response:
Enter a value for the configuration Path Name. The configuration with name: name already exists. The submitted name for the configuration already exists. Validation fails. Enter a unique configuration name. Please deselect the configuration before deleting it. Attempting to delete the currently selected configuration. Should make another configuration active and then delete required entry. Validation fails. Make another configuration active and then delete required entry. Cannot find the resource directory name. Do you want to create it? The resource directory does not exist, confirm if wish to create it. The system action depends on the user response. Perform one of the following actions:

Click Yes to create the resource directory. Click No to take no action.
PWX-01672 Explanation: User Response: PWX-01673 Explanation: System Action: User Response: PWX-01674 Explanation: System Action: User Response: PWX-01675 Explanation: System Action: User Response: PWX-01676 Explanation: System Action: User Response:
Cannot find the resource item name. This message indicates that a search for a required resource item failed. Check search criteria and resubmit. Please enter a valid Data Source Name. The mandatory Data Source Name field is empty. Validation fails. Enter a value for the Data Source Name. Please enter a valid Personal Metadata Name. The mandatory Personal Metadata Name field is empty. Validation fails. Enter a value for the Personal Metadata Name. Please select a Personal Metadata Location. The mandatory Personal Metadata Location field is empty. Validation fails. Enter a value for the Personal Metadata Location. Please select a Personal Metadata Type. The mandatory Personal Metadata Type field is empty. Validation fails. Enter a value for the Personal Metadata Type.
PWX-01000 to PWX-01999
115
Save changes to Personal Metadata metaname? The Personal Metadata file is being closed and contains unsaved changes. The system action depends on the user response. Perform one of the following actions:

Click Yes to save and close the Personal Metadata properties. Click No to close the Personal Metadata properties without saving. Click Cancel to return to the Personal Metadata properties editing dialog box. PWX-01678 Explanation: System Action: User Response: Personal Metadata metaname already exists in directory directory. Overwrite? A Personal Metadata file with an identical name already exists in the directory. The system action depends on the user response. Perform one of the following actions:
Click Yes to overwrite the file. Click No to edit Personal Metadata. PWX-01679 Explanation: User Response: Personal Metadata metaname already exists in directory directory and is read only! This message indicates that a file by the same name already exists in the directory and cannot be overwritten because it is read only. To save the Personal Metadata to the same file name, either delete, rename or write enable the existing file. Do you want to rename the current Personal Metadata from metaname1 to metaname2? Confirm the change of name of an existing Personal Metadata file. The system action depends on the user response. Perform one of the following actions:
Click Yes to rename the Personal Metadata. Click No to edit Personal Metadata. PWX-01681 Explanation: System Action: User Response: PWX-01682 Explanation: System Action: User Response: PWX-01683 Explanation: User Response: PWX-01684 Explanation: Please enter a Maximum Rows value in the range min_range to max_range. The Maximum Rows value is not within the valid range. Validation fails. Enter a Maximum Rows value within the valid range. The SEQ File Name selected (including path) exceeds the maximum possible allowable length. The name and full path of the file exceeds the maximum length. Validation fails. Enter a correct string for the path and file name. The file file_name does not exist. The file file_name does not exist. Ensure that the path and file name are correct and the file exists at that location. Please enter an SQL record length in the range min_range to max_range. The SQL record length value is not within the valid range.
116
System Action: User Response: PWX-01685 Explanation: User Response: PWX-01686 Explanation: System Action: User Response: PWX-01687 Explanation: System Action: User Response:
Validation fails. Enter a SQL record length value within the valid range. The end of the file has been reached. All the data was returned. No response is required. Please enter a Record number in the range min_range to max_range. The Record number value is not within the valid range. Validation fails. Enter a Record number value within the valid range. To open the selected name resource it has to be imported into the current configuration. Do you want to do this? Prompt to import resource into current configuration. The system action depends on the user response. Perform one of the following actions:

Click Yes to import the resource into the configuration. Click No to take no action.
Resource resource_name already exists in directory directory and is read only, the import will be terminated! The file to be imported already exists in the directory and is read only, so the import ends. Stop import of resource file. To save the resource file to the same file directory, either delete, rename or write enable the existing file and try import again. Resource resource_name already exists in directory directory. Overwrite? The file to be imported already exists in the directory. The system action depends on the user response. Perform one of the following actions:
Click Yes to overwrite the resource. Click No to take no action. PWX-01690 Explanation: System Action: User Response: To open a resource you must first configure the resource directories. A resource directory has to be created if a resource is to imported successfully. The system action depends on the user response. Perform one of the following actions:
Click Yes to create the resource directory and continue importing. Click No to take no action. PWX-01691 Explanation: System Action: User Response: Please enter a Database qualifier. The mandatory Database Qualifier field is empty. Validation fails. Enter a value for the Database Qualifier.
PWX-01000 to PWX-01999
117
Command Set building and loading is not enabled! Current license key does not authorize Command Set use. Terminate opening or importing of Command Sets. If building and loading of Command Sets is required then Contact Informatica Global Customer Support. Please enter a Database ID in the range min_range to max_range. The Database ID value is not within the valid range. Validation fails. Enter a Database ID value within the valid range. Please enter a File Number in the range min_range to max_range. The File Number value is not within the valid range. Validation fails. Enter a File Number value within the valid range. Please enter a Field Length in the range min_range to max_range. The Field Length value is not within the valid range. Validation fails. Enter a Field Length value within the valid range. Please enter a Field Offset in the range min_range to max_range. The Field Offset value is not within the valid range. Validation fails. Enter a Field Offset value within the valid range. To enable early detection of errors, it is recommended that you import the FDT details. Do you want to do this now? Import the FDT details to enable validation of the data map. The system action depends on the user response. Perform one of the following actions:
Click Yes to import FDT details. Click No to edit the data map. PWX-01698 Explanation: User Response: PWX-01699 Explanation: System Action: User Response: FDT imported successfully. The FDT was imported successfully and can be used in validation of data map. No response is required. Failed to update FDT cache file. Unable to update FDT cache file from the imported FDT file. Processing continues without FDT details. Ensure the imported FDT file was not moved or deleted.
118
PWX-01700 Explanation: User Response: PWX-01701 Explanation: User Response: PWX-01702 Explanation: System Action: User Response: PWX-01703 Explanation: System Action: User Response:
Data Map map_name send to node nodename successfully. This message confirms the successful sending of data map to node. No response is required. FDT refreshed successfully. This message confirms that the FDT details have been successfully refreshed. No response is required. Please enter a valid Name. The mandatory Name field is empty. Validation fails. Enter a value for the Name. If you send the Data Map to node nodename, this will invalidate your current FDT. Do you want to do this? Sending data map to node invalidates the current FDT details held for validation. The system action depends on the user response. Perform one of the following actions:
Click Yes to invalidate the current FDT. Click No to take no action. PWX-01704 Explanation: System Action: User Response: If you import the FDT from node nodename, this will invalidate your current Data map location. Do you want to do this? Importing the FDT invalidates the current data map location. The system action depends on the user response. Perform one of the following actions:
Click Yes to invalidate your current data map location. Click No to take no action. PWX-01705 Explanation: System Action: User Response: PWX-01706 Explanation: System Action: User Response: PWX-01707 Explanation: User Response: Please enter a Column Name. The mandatory Column Name field is empty. Validation fails. Enter a value for the Column Name. The resource is currently in use by another process and will be opened for read only! Another process currently has the file open, so the file is opened in read-only mode. Open file in read only mode. End process that is using the file to be able to edit contents. The resource name is currently in use by another process and cannot be action! This message indicates that another process currently has the file open so the required action action cannot be completed (import, save, overwrite or delete). End process that is using the file to be able to resubmit request.
PWX-01000 to PWX-01999
119
120
Please enter a legal fully qualified Path Name. The mandatory Path Name field is empty. Validation fails. Enter a value for the Path Name. Please enter different local and shared directory paths. The local and shared directory paths must be different locations. Validation fails. Enter different local and shared directory paths. Please enter an Exit Program Name. The mandatory Exit Program Name field is empty. Validation fails. Enter a value for the Exit Program Name. Please enter a Sub Schema Name. The mandatory Sub Schema Name field is empty. Validation fails. Enter a value for the Sub Schema Name. Please enter a Database Name. The mandatory Database Name field is empty. Validation fails. Enter a value for the Database Name. Please enter a Dictionary Name. The mandatory Dictionary Name field is empty. Validation fails. Enter a value for the Dictionary Name. Please enter an IDMS Record Name. The mandatory IDMS Record Name field is empty. Validation fails. Enter a value for the IDMS Record Name. Please enter an Area Name. The mandatory Area Name field is empty. Validation fails. Enter a value for the Area Name. Please enter a Natural User Library Path. The mandatory Natural User Library Path field is empty. Validation fails. Enter a value for the Natural User Library Path.
PWX-01717 Explanation: System Action: User Response: PWX-01718 Explanation: System Action: User Response: PWX-01719 Explanation: System Action: User Response: PWX-01720 Explanation: System Action: User Response: PWX-01721 Explanation: System Action: User Response: PWX-01722 Explanation: System Action: User Response: PWX-01724 Explanation: System Action: User Response: PWX-01725 Explanation: System Action: User Response: PWX-01726 Explanation: System Action:
Please enter an Owner Name. The mandatory Owner Name field is empty. Validation fails. Enter a value for the Owner Name. Please enter a Set Name. The mandatory Set Name field is empty. Validation fails. Enter a value for the Set Name. Please enter a Directory Name. The mandatory Directory Name field is empty. Validation fails. Enter a value for the Directory Name. No blank characters are allowed in field names. No blank characters are allowed in field names. Validation fails. Enter a field name without blank characters. Set Name setname already exists, please use alternate name. A duplicate Set Name was entered. Validation fails. Enter a unique Set Name. Unable to find the IDMS record name record_name in the list of records. Failed to retrieve the IDMS record name from the parent/child record. Do not allow table dependency. Check the record definitions are correct. Unable to edit field. A record dependency exists in table tabname, for record record_name with set name setname. Unable to edit the owner or set name as a table exists that is using this relationship. Enable only read only access to details. Must remove dependent tables if need to alter or remove owner records and set name. Please enter a PCB name. The mandatory PCB name field is empty. Validation fails. Enter a value for the PCB name. Please enter a valid resource_type Name. Mandatory field Name is missing. Validation fails.
PWX-01000 to PWX-01999
121
User Response: PWX-01727 Explanation: System Action: User Response: PWX-01728 Explanation: System Action: User Response: PWX-01729 Explanation: User Response:
Enter a valid Name. Please select a resource_type Location. Mandatory field Location is missing. Validation fails. Enter a valid Location. Please select a resource_type Type. Mandatory field Type is missing. Validation fails. Enter a valid Type. resource_type resource_name already exists in directory directory and is read only! This message indicates that a resource by the same name already exists in the directory and cannot be overwritten because it is read only. To save the resource to the same file name, either delete, rename or write enable the existing resource. resource_type resource_name already exists in directory directory. Overwrite? A resource with an identical name already exists in the directory. The system action depends on the user response. Perform one of the following actions:

Click Yes to overwrite the resource. Click No to taken no action.
Save changes to resource_type resource_name? The resource is being closed and contains unsaved changes. The system action depends on the user response. Perform one of the following actions:

Click Yes to save and close the resource. Click No to close the resource without saving. Click Cancel to close the dialog box and take no action. PWX-01732 Explanation: System Action: User Response: PWX-01733 Explanation: System Action: User Response: Please enter a valid resource_type group_name. The mandatory field is empty. Validation fails. Enter a valid string. Please enter a valid Capture Registration Name. The mandatory Capture Registration Name field is either empty or contains an invalid character. A registration must start with a letter and then either letters or numbers. Validation fails. Enter a valid value for the Capture Registration Name.
122
resource_type resource_name already exists. Please choose an alternative name. The resource name already exists. Validation fails. Enter a unique resource name. Please enter a Bit Position value between 1 and maximum. The Bit Position value is not within the valid range. Validation fails. Enter a Bit Position value within the valid range. Please enter a Time value between 0 and 99999. The Time value is not within the valid range. Validation fails. Enter a Time value within the valid range. Please enter a JCL Template. The mandatory JCL Template field is empty. Validation fails. Enter a value for the JCL Template. Please enter a CTL Template. The mandatory CTL Template field is empty. Validation fails. Enter a value for the CTL Template. Please enter a FName. The mandatory FName field is empty. Validation fails. Enter a value for the FName. Please enter a Calling Convention. The mandatory Calling Convention field is empty. Validation fails. Enter a value for the Calling Convention. Version version1 of Capture Registration name is already ACTIVE. Version version2 will be created INACTIVE. Do you want to do this? This message confirms the action to take for Capture Registration. The system action depends upon the user response. Perform one of the following actions:
Click Yes to overwrite the file. Click No to ignore changes. Click Cancel to close the dialog and take no action.
PWX-01000 to PWX-01999
123
Version version1 of Capture Registration name will be made ACTIVE and Version version2 will be made HISTORY. Do you want to do this? Confirm changing status of the Capture Registration. Set the version numbers of the active and history capture registrations. Perform one of the following actions:

Click Yes to accept the changes. Click No to ignore the changes. Click Cancel to close the dialog box and take no action. PWX-01744 Explanation: System Action: User Response: Do you want to rename the current resource_type from resource_name1 to resource_name2? Confirm the change in resource name. The system action depends on the user response. Perform one of the following actions:
Click Yes to change the resource name. Click No to lose resource changes and take no action. PWX-01745 Explanation: System Action: User Response: PWX-01746 Explanation: System Action: User Response: PWX-01747 Explanation: System Action: User Response: PWX-01748 Explanation: System Action: User Response: PWX-01749 Explanation: User Response: PWX-01755 Explanation: System Action: Please enter a valid Extract Definition Map Name. The mandatory Extract Definition Map Name field is empty. Validation fails. Enter a value for the Extract Definition Map Name. Please enter a valid Extract Definition Table Name. The mandatory Extract Definition Table Name field is empty. Validation fails. Enter a value for the Extract Definition Table Name. Please enter a Library Name. The mandatory Library Name field is empty. Validation fails. Enter a value for the Library Name. There are no Data Maps to import from location location. No data maps found from the location. Stop import process. Verify that location was submitted correctly and that data maps exist at specified location. The Data Map(s) have been successfully imported from location location. This message confirms that selected data maps were successfully imported from the specified location location. No response is required. Please enter a Record ID between 10 and 9999. The Record ID value is not within the valid range. Validation fails.
124
Enter a Record ID value within the valid range. Are you sure you want to delete the selected field? Confirm deletion of the selected field. The system action depends on the user response. Perform one of the following actions:

Click Yes to delete the field. Click No to take no action.
Invalid Order. Permitted values are ASC or DESC. A mandatory Order value must be entered. Validation fails. Enter a valid Order value. Please enter a Schema Version of HIGHEST, LOWEST or a numeric between 1 and 9999. The Schema Version value is not valid. Validation fails. Enter a valid Schema Version value. Please enter a Database Name. The mandatory Database Name field is empty. Validation fails. Enter a value for the Database Name. Please enter a UTC Timestamp. The mandatory UTC Timestamp field is empty. Validation fails. Enter a value for the UTC Timestamp. Please enter a Database Name. The mandatory Database Name field is empty. Validation fails. Enter a value for the Database Name. Please enter a data set name. The mandatory Data set Name field is empty. Validation fails. Enter a value for the data set name. To enable early detection of errors, it is recommended you import the data set definition. Do you want to do this now? Import the data set details to enable validation of the data map. The system action depends on the user response. Perform one of the following actions:
Click Yes to import the data definition.

PWX-01000 to PWX-01999 125
Click No to take no action and edit he data map.
PWX-01766 Explanation: User Response: PWX-01767 Explanation: User Response: PWX-01768 Explanation: System Action: User Response: PWX-01770 Explanation: System Action: User Response: PWX-01771 Explanation: System Action: User Response: PWX-01772 Explanation: System Action: User Response: PWX-01 Explanation: System Action: User Response: PWX-01774 Explanation: System Action: User Response: PWX-01775 Explanation: System Action: User Response:
Data Set definition imported successfully. The data set was imported successfully and can be used in the validation of data map. No response is required. Data Set definition refreshed successfully. Confirmation that the data set details have been successfully refreshed. No response is required. Failed to update data set definition cache file. Unable to update data set cache file from the imported data set file. Continue without data set details. Ensure the imported data set file was not moved or deleted. Invalid Field Type. The Field Type value is invalid. Validation fails. Enter a valid Field Type. Please enter a Journal Library. The mandatory Journal Library field is empty. Validation fails. Enter a value for the Journal Library. Please enter a Journal Name. The mandatory Journal Name field is empty. Validation fails. Enter a value for the Journal Name. Please enter a Library Name. The mandatory Library Name field is empty. Validation fails. Enter a value for the Library Name. Please enter a Receiver. The mandatory Receiver field is empty. Validation fails. Enter a value for the Receiver. Please enter a Sequence Number. The mandatory Sequence Number field is empty. Validation fails. Enter a value for the Sequence Number.
126
Invalid Sequence Number. Please enter a value of FIRST, LAST or a numeric. The value entered for the Sequence Number is invalid. Validation fails. Enter a valid Sequence Number. XML parser error: errormessage. The XML parser has returned an error. Quit XML parsing. Check XML parsing error and take appropriate action. Please enter a valid Key value (M,S,U or blank). An invalid Key value was entered. Validation fails. Enter a valid value for the Key. Please enter a Data Set Name. The mandatory data set Name field is empty. Validation fails. Enter a value for the data set Name. Please enter a File Number. The mandatory File Number field is empty. Validation fails. Enter a value for the File Number. Please enter a Database ID. The mandatory Database ID field is empty. Validation fails. Enter a value for the Database ID. Only 1 unique key value can be declared. More than one key value was declared for a Search Field. Validation fails. Ensure that a Key value is declared for only one Search Field. Record not found for record name name. Unable to find the record declared in the Record Dependencies. Stop creation of table. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-01000 to PWX-01999
127
CCK fields exist for record record_name, but the Generate CCK Columns flag is deselected. Continue? Confirm that you do not want to generate CCK columns for the table. The system action depends on the user response. Perform one of the following actions:

Click Yes to continue without generating CCK fields. Click No to edit table properties.
At least 1 Key Column must be selected for a Full Condense. If Full condense is selected ensure that at least one key exists. Validation fails. If Full condense is selected ensure that at least one key exists. At least 1 Column must be selected. At least one column must be selected. Validation fails. Select at least one column. The total size of the key column(s) exceeds the limits for a Full Condense. The total size of the key column(s) exceeds the limits for a Full Condense. Validation fails. Alter key column selection so total size does not exceed Full Condense limits. A Receiver Name of record_name together with a Sequence Number of seqnumber is not allowed! Invalid combination of Receiver Name and Sequence Number. Validation fails. Enter a correct combination of Receiver Name and Sequence Number. A Sequence Number of seqnumber is not allowed! It can only be *FIRST, *LAST or a number. An invalid Sequence Number was entered. Validation fails. Enter a valid Sequence Number. A Receiver Name of <record_name1> is not allowed! Please change it to <record_name1>. The Receiver Name was entered incorrectly. Validation fails. Alter Receiver Name to suggested text. Please enter a Segment Level in the range 1 to 15. The Segment Level value is not within the valid range. Validation fails. Enter a Segment Level value within the valid range.
128
Please enter a Segment Code in the range 1 to 15. The Segment Code value is not within the valid range. Validation fails. Enter a Segment Code value within the valid range. For a Segment Level value of 1, please enter a Parent Segment Code of 0. Incorrect combination of Segment Level value and Parent Segment Code. Validation fails. For a Segment Level value of 1, enter a Parent Segment Code of 0. Please enter a Key Start in the range 0 to 32766. The Key Start value is not within the valid range. Validation fails. Enter a Key Start value within the valid range. Please enter a Key Length in the range 1 to 255. The Key Length value is not within the valid range. Validation fails. Enter a Key Length value within the valid range. Segment Name and Parent Segment Name are not allowed to be identical. Segment Name and Parent Segment Name are not allowed to be identical. Validation fails. Alter either the Segment Name or the Parent Segment Name. Please enter a Queue Manager. The mandatory Queue Manager field is empty. Validation fails. Enter a value for the Queue Manager. Please enter a Queue Name. The mandatory Queue Name field is empty. Validation fails. Enter a value for the Queue Name. Bad basename - the character character is not permitted. Invalid character entered for column basename. Validation fails. Enter a valid basename. Please enter a MUF Name. The mandatory MUF Name field is empty. Validation fails. Enter a value for the MUF Name.
PWX-01000 to PWX-01999 129
Please enter a User Requirements Table. The mandatory User Requirements Table field is empty. Validation fails. Enter a value for the User Requirements Table. Please enter a Long Table Name. The mandatory Long Table Name field is empty. Validation fails. Enter a value for the Long Table Name. Please enter a Short Table Name. The mandatory Short Table Name field is empty. Validation fails. Enter a value for the Short Table Name. Please enter a Table ID in the range of 1 to 240. The Table ID value is not within the valid range. Validation fails. Enter a Table ID value within the valid range. Please enter a Table Status. The mandatory Table Status field is empty. Validation fails. Enter a value for the Table Status. Please enter a Table Version in the range of 1 to 999. The Table Version value is not within the valid range. Validation fails. Enter a Table Version value within the valid range. Please enter a Database ID in the range of 1 to 5000. The Database ID value is not within the valid range. Validation fails. Enter a Database ID value within the valid range. resource_type name already exists. Please enter a different name. The name already exists in the Command Set resource tree. Validation fails. Enter a unique name that does not exist in Command Set resource tree. If you delete the Source source then all Targets and Row Exits will also be deleted. Do you want to do this? Confirm deletion of the Source, which deletes all Targets and Row Exits. The system action depends on the user response.
130
User Response:
Perform one of the following actions:
Click Yes to delete the selected items and their dependents. Click No to take no action. PWX-01812 Explanation: System Action: User Response: PWX-01813 Explanation: User Response: PWX-01814 Explanation: System Action: User Response: PWX-01815 Explanation: System Action: User Response: PWX-01816 Explanation: System Action: User Response: PWX-01817 Explanation: User Response: PWX-01818 Explanation: System Action: User Response: Please enter a resource_type name. Mandatory SOURCE/TARGET name is empty. Validation fails. Enter a valid name. Source column sourcecol is already mapped to target column targetcol. The source column could not be mapped to the target column because a mapping already exists. No response is required. Command set csname is incomplete and cannot be action. A Command Set can only be saved, exported or tested if there is a source and at least one target. Validation fails. Ensure that there is at least a source and at least one target. Name already exists, please use alternate name. A duplicate Name was entered. Validation fails. Enter a unique Name. name already exists as a field or expression name in the record, please use alternate name. A duplicate field or expression name was entered for the record. Validation fails. Enter a unique name for the field or expression. If you only select a dbconnection, the remaining resource_type information has to be manually configured. Do you want to do this? By selecting only the dbconnection, the additional information gained by selecting a table or column must be entered manually. No response is required. If you delete Target target then the Target Connection and dependent Row Exit Interfaces will also be deleted. Continue? Confirm deletion of the Target, which deletes all dependent Row Exit Interfaces The system action depends on the user response. Perform one of the following actions:
Click Yes to delete. Click No to take no action.
PWX-01000 to PWX-01999
131
PWX-01819 Explanation: System Action: User Response: PWX-01821 Explanation: System Action: User Response: PWX-01822 Explanation: System Action: User Response: PWX-01823 Explanation: User Response: PWX-01824 Explanation: System Action: User Response: PWX-01825 Explanation: System Action: User Response: PWX-01826 Explanation: System Action: User Response: PWX-01827 Explanation: System Action: User Response: PWX-01828 Explanation: System Action: User Response:
For Segment Level values of 1, please enter a Parent Segment Code in the range of 1 to 255. The Parent Segment Code is not within the valid range. Validation fails. Enter a Parent Segment Code within the valid range. Personal Metadata metaname already exists, please use alternate name. A duplicate Personal Metadata name was entered. Validation fails. Enter a unique name for the Personal Metadata. Please enter a Schema Name. The mandatory Schema Name field is empty. Validation fails. Enter a value for the Schema Name. Schema schema_name exported to location successfully! This message confirms that the schema was successfully exported. No response is required. The Source and Target names are the same. Please use different names. Identical Source and Target names have been entered for the record. Validation fails. Enter unique names for the Source and Target names. Please enter a Long Key Name. The mandatory Long Key Name field is empty. Validation fails. Enter a value for the Long Key Name. Please enter a Short Key Name. The mandatory Short Key Name field is empty. Validation fails. Enter a value for the Short Key Name. Long Key Name key_name already exists, please use alternate name. A duplicate Long Key Name was entered. Validation fails. Enter a unique name for the Long Key Name. Please enter a Key Sensitivity. The mandatory Key Sensitivity field is empty. Validation fails. Enter a value for the Key Sensitivity.
132
Short Key Name key_name already exists, please use alternate name. A duplicate Short Key Name was entered. Validation fails. Enter a unique name for the Short Key Name. Name name already exists, please use alternate name. A duplicate name was entered. Validation fails. Enter a unique name. The maximum length of max_chars characters has been exceeded. The field value exceeds its maximum length. Validation fails. Enter a valid field value. Changing the Target type will lose existing column mappings. Continue? Confirmation that changing the Target type drops the existing column mappings. The system action depends on the user response. Perform one of the following actions:
Click Yes to continue processing. Click No to take no action. PWX-01833 Explanation: System Action: User Response: PWX-01834 Explanation: System Action: User Response: Please enter an Application Name, as it is a required field for CAPX and CAPXRT. The mandatory Application Name field is empty. Validation fails. Enter a value for the Application Name. Use of a custom SQL will lose existing column mappings. Continue? Confirmation that use of custom SQL drops the existing column mappings. The system action depends on the user response. Perform one of the following actions:

Click Yes to continue processing. Click No to take no action.
Please enter an Array Size in the range min_range to max_range. The Array Size value is not within the valid range. Validation fails. Enter a Array Size value within the valid range. Please enter a Time to linger before returning EOF in the range min_range to max_range. The Time to linger before returning EOF value is not within the valid range. Validation fails. Enter a Time to linger before returning EOF value within the valid range.
PWX-01000 to PWX-01999
133
Please enter an Envelope Count in the range min_range to max_range. The Envelope Count value is not within the valid range. Validation fails. Enter a Envelope Count value within the valid range. Invalid AIN entry. Invalid AIN entry. Validation fails. Enter a valid AIN entry. The Data Map Name contains the invalid character _. Please correct. The _ (underscore) character is not permitted in the data map name. Validation fails. Enter a valid data map name. Please enter a Base Field. The mandatory Base Field is empty. Validation fails. Enter a value for the Base Field. There are pending column map changes. Do you want to apply them? Confirm if want to apply column map changes. The system action depends on the user response. Perform one of the following actions:

Click Yes to apply column map changes. Click No to reset column mappings.
At least one column must be mapped. At least one column must be mapped. Validation fails. Create at least one column mapping. Selected extract run has no runtime. The extract run has no run time. Validation fails. Enter a run-time value for the extract run. No DBD Name is contained with the Data Map map_name. Data Maps must be created using the DBD import capability. No DBD Name is contained with the data map. Validation fails. Create data map with the DBD import capability.
134
Changing a Table qualifier will lose existing column mappings. Continue? Confirm change in Table qualifier. This change resets existing column mappings. The system action depends on the user response. Perform one of the following actions:

Click Yes to apply changes and reset column mappings. Click No to take no action.
Item not found, unable to issue delete instruction. Attempting to remove Key and existing DKF fields but item not found. Delete processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Please enter a CAPX Timeout value in the range of min_range to max_range. The CAPX Timeout value is not within the valid range. Validation fails. Enter a CAPX Timeout value within the valid range. Drive drive is not available. Please make the drive available or select another Resource Configuration. Attempting to access a drive that is not available. Validation fails. Make drive available or select a different Resource Configuration. Please enter a valid UserID. The mandatory UserID field is empty. Validation fails. Enter a value for the UserID. Please enter a valid Password. The mandatory Password field is empty. Validation fails. Enter a value for the Password. Please enter a valid IP Address. The mandatory IP Address field is empty. Validation fails. Enter a value for the IP Address. Please enter a Port Number in the range min_range to max_range. The Port Number value is not within the valid range. Validation fails. Enter a Port Number value within the valid range.
PWX-01000 to PWX-01999
135
PWX-01854 Explanation: User Response: PWX-01855 Explanation: User Response: PWX-01856 Explanation: System Action: User Response: PWX-01857 Explanation: System Action: User Response: PWX-01858 Explanation: System Action: User Response: PWX-01859 Explanation: System Action: User Response:
You are now Logged on to Configuration configuration. This message confirms that the user is successfully logged on to the selected configuration. No response is required. You are now Logged off from Configuration configuration This informational message confirms that the user is successfully logged off from the existing configuration. No response is required. Please set up a Repository for the configuration configuration The selected configuration has no IP Address or Host name. Validation fails. Add an IP Address or Host name to the selected configuration. Please add the User to at least one Group The user must belong to at least one group. Validation fails. Add the user to at least one group. Please enter a valid Host Name. The mandatory Host Name field is empty. Validation fails. Enter a value for the Host Name. Save changes to resource_type resource_name? The resource is being closed and contains unsaved changes. The system action depends on the user response. Perform one of the following actions:
Click Yes to save and close the resource. Click No to close the resource without saving. Click Cancel to return to the dialog box. PWX-01860 Explanation: System Action: User Response: Renaming resource from name1 to name2 may cause problems with other resources that rely on it. Do you want to proceed? Confirm the renaming of the resource, although there might be dependent resources. The system action depends on the user response. Perform one of the following actions:

Click Yes to rename the resource. Click No to close the resource without saving.
Deleting resource name may cause problems with other resources that rely on it. Do you want to proceed? Confirm the deletion of the resource, although there might be dependent resources. The system action depends on the user response. Perform one of the following actions:
136
Click Yes to delete the resource. Click No to take no action. Please enter a valid GroupID. The mandatory GroupID field is empty. Validation fails. Enter a value for the GroupID. Passwords do not match. Please re-enter. The two password strings do not match. Validation fails. Ensure that the passwords are matching. Please enter a Send Buffer Size in the range min_range to max_range. The Send Buffer Size value is not within the valid range. Validation fails. Enter a Send Buffer Size value within the valid range. Please enter a Receive Buffer Size in the range min_range to max_range. The Receive Buffer Size value is not within the valid range. Validation fails. Enter a Receive Buffer Size value within the valid range. Please select a Database Connection Location. The mandatory Database Connection Location field is empty. Validation fails. Enter a value for the Database Connection Location. Please select at least one Group. At least one group must be selected. Validation fails. Select at least one group. Please select a source. No source was selected. Validation fails. Select a source. Please make a selection. No target was selected. Validation fails. Select a target.
PWX-01000 to PWX-01999
137
Please enter a Name. The mandatory Name field is empty. Validation fails. Enter a value for the Name. Please enter a valid User Exit. The mandatory User Exit field is empty. Validation fails. Enter a value for the User Exit. Please enter an Interface Name. The mandatory Interface Name field is empty. Validation fails. Enter a value for the Interface Name. At least 1 output must be entered. At least one output must be entered. Validation fails. Enter at least one output item. At least 1 input column must be entered. At least one input column must be entered. Validation fails. Enter at least one input item. Do you want to reset the list? Resetting the list discards all changes. The system action depends on the user response. Perform one of the following actions:
Click Yes to reset the list. Click No to take no action. PWX-01876 Explanation: System Action: User Response: PWX-01877 Explanation: System Action: User Response: Please set the Group Privilege. No Group Privileges have been set. Validation fails. Enter at least one Group Privilege. Table name tabname already exists, please use an alternate name. A duplicate table name was entered. Validation fails. Enter a unique table name.
138
Please select at least one table At least one table must be selected to save changes. Validation fails. At least one table must be selected before clicking OK. Click Cancel to take no action and close dialog. Are you sure you want to remove User Authentication for Location location Confirm removal of User Authentication for selected Location. The system action depends on the user response. Perform one of the following actions:
Click Yes to remove user authentication. Click No to take no action. PWX-01880 Explanation: System Action: User Response: PWX-01881 Explanation: System Action: User Response: PWX-01882 Explanation: System Action: User Response: PWX-01883 Explanation: System Action: User Response: PWX-01884 Explanation: System Action: User Response: PWX-01885 Explanation: System Action: User Response: Wait Time range is 0 or 2 - 86400. The Wait Time value is not within the valid range. Validation fails. Enter a Wait Time value within the valid range. Please enter a Supplement Log Group Name. The mandatory Supplement Log Group Name field is empty. Validation fails. Enter a value for the Supplement Log Group Name. You do not have execution access to Database Connection dbconnection Inform user that they do not have execution access to the Database Connection. Validation fails. Add execution access to user properties. Please enter a Calling Convention. The mandatory Calling Convention field is empty. Validation fails. Enter a value for the Calling Convention. Please enter a unique Interface Name. The mandatory Interface Name field already exists for the Row Exit. Validation fails. Enter an Interface Name value that is unique for the Row Exit. Please enter a Send Message Length in the range min_range to max_range. The Receive Buffer Size value is not within the valid range. Validation fails. Enter a Receive Buffer Size value within the valid range.
PWX-01000 to PWX-01999
139
Please enter a Receive Message Length in the range min_range to max_range. The Receive Message Length value is not within the valid range. Validation fails. Enter a Receive Message Length value within the valid range. This version of PowerExchange requires that command sets are held in the repository. Would you like csname to be migrated? To view and edit a Command Set created in a previous version of PowerExchange, import the file using the migration utility. The system action depends on the user response. Perform one of the following actions:
Click Yes to migrate the command set. Click No to take no action. PWX-01888 Explanation: System Action: User Response: Command Set csname must be migrated before it can be viewed or amended. To view and edit a Command Set created in a previous version of PowerExchange, import the file using the migration utility. The system action depends on the user response. Perform one of the following actions:
Click Yes to migrate the command set. Click No to take no action. PWX-01889 Explanation: System Action: User Response: Changing the Input Source will reset and create new default column mappings. Continue? Confirm change in the Input Source. This resets and create new default column mappings. The system action depends on the user response. Perform one of the following actions:
Click Yes to apply changes and create new default column mappings. Click No to take no action. PWX-01890 Explanation: System Action: User Response: Changing the Output Target will reset and create new default column mappings. Continue? Confirm change in the Output Target. This resets and create new default column mappings. The system action depends on the user response. Perform one of the following actions:
Click Yes to apply changes and create new default column mappings. Click No to take no action. PWX-01891 Explanation: System Action: User Response: Changing the Interface Columns will reset and create new default column mappings. Continue? Confirm change in the Interface Columns. This resets and create new default column mappings. The system action depends on the user response. Perform one of the following actions:
Click Yes to apply changes and create new default column mappings. Click No to take no action.
140 Chapter 1: PWX-00100 to PWX-35999
There are pending column changes, which will reset and create new default column mappings. Do you want to apply them? There are changes to the column details that have not been applied. Confirm changes, which resets and create new default column mappings. The system action depends on the user response. Perform one of the following actions:

Click Yes to apply changes and create new default column mappings. Click No to take no action.
There are pending column changes. Do you want to apply them? There are changes to the column details that have not been applied. The system action depends on the user response. Perform one of the following actions:

Click Yes to apply changes. Click No to take no action.
PWX-01894 Explanation: System Action: User Response: PWX-01895 Explanation: System Action: User Response: PWX-01896 Explanation: System Action: User Response: PWX-01897 Explanation: System Action: User Response: PWX-01898 Explanation: User Response:
Please enter an Input Connection. The mandatory Input Connection field is empty. Validation fails. Enter a value for the Input Connection. Please enter an Output Connection. The mandatory Output Connection field is empty. Validation fails. Enter a value for the Output Connection. Please select a Command Set. A session requires that at least one Command Set is selected. Validation fails. Select at least one Command Set. Administrator userID user_ID cannot be deleted. Unable to delete the mandatory Administrator user ID. Validation fails. No response is required. You have logged on using the Administrator default password. Please change it before you log on again. The Administrator's default password should be changed to prevent any unauthorized access. Open the admin file located under the Users section of the Resource Explorer and change the password.
PWX-01000 to PWX-01999
141
Administrator groupID groupid cannot be deleted. Unable to delete the mandatory Administrator groupID. Validation fails. No response is required. dbqualifier is required for a resource_type Database Connection. A mandatory database qualifier is missing. Validation fails. Enter the database qualifier and resubmit request. Please select a dbconnection Database Connection or Table. A Source/Target Database Connection or Table must be selected. Validation fails. Select a Database Connection or Table. Migration of locally held Command Sets requires a Repository. Please configure one and try again. To view and edit a Command Set created in a previous version of PowerExchange, the Command Set must be migrated to a Repository. Validation fails. To use the Repository ensure That REPOS_ENABLE=Y is set in the dbmover.cfg, create a Repository and import the Command Set to the Repository using the migration utility. Please configure a destination Folder. To view and edit a Command Set created in a previous version of PowerExchange, the Command Set must be migrated to a Repository Folder. Validation fails. Add a Folder item under the Folders icon. Please select a destination Folder. The Command Set is migrated to a destination Folder. No destination folder was selected. Validation fails. Select a destination Folder. Name name already exists in Folder folder, please use alternate name. A duplicate Folder resource name was entered. Validation fails. Enter a unique Folder resource name. Please select a resource_type Database Connection. To migrate a Command Set it is mandatory to select a Source/Target Database Connection. Validation fails. Select a Source/Target Database Connection.
142
Repository Command Set names are restricted to nine characters. Please confirm name name which is unique in folder folder. Confirm the new nine character Command Set name that was generated. The system action depends on the user response. Perform one of the following actions:

Click Yes to accept the command set name. Click No to take no action.
Command Set csname has been successfully migrated to Folder folder. This message confirms successful migration of the command set. No response is required. User user has no select access to V$PARAMETER for Oracle Instance instance. The database user does not have authority to access the view V$PARAMETER. Validation fails. Use an alternative database user with the necessary authority or grant the required privileges to the current user. Deleting Folder folder will also delete the Folder's contents. Do you want to continue? Confirm deletion of the Folder, which deletes its contents. The system action depends on the user response. Perform one of the following actions:
Click Yes to delete the folder and its contents. Click No to take no action. PWX-01911 Explanation: User Response: PWX-01912 Explanation: System Action: User Response: PWX-01913 Explanation: User Response: PWX-01914 Explanation: System Action: User Response: Configuration configuration refreshed successfully. This message confirms successful refresh of the Configuration. No response is required. Please enter an Application Name. The mandatory Application Name field is empty. Validation fails. Enter a value for the Application Name. Configuration configuration could not be refreshed. This message confirms that the refresh of the Configuration was unsuccessful. Verify that the connection to the node where the repository is located is still responding. Please enter a Commit after N Records value in the range min_range to max_range. The Commit after N Records value is not within the valid range. Validation fails. Enter a Commit after N Records value within the valid range.
PWX-01000 to PWX-01999
143
Please enter a Commit After N UOWs value in the range min_range to max_range. The Commit After N UOWs value is not within the valid range. Validation fails. Enter a Commit After N UOWs value within the valid range. Please enter a PowerExchange Control Table name. The mandatory PowerExchange Control Table field is empty. Validation fails. Enter a value for the PowerExchange Control Table. Please enter a Start of Range Sequence Number. The mandatory Start of Range Sequence Number field is empty. Validation fails. Enter a value for the Start of Range Sequence Number. Please enter an End of Range Sequence Number. The mandatory End of Range Sequence Number field is empty. Validation fails. Enter a value for the End of Range Sequence Number. Start of Range Sequence Number has been truncated to 15 digits. The maximum length of the Range Sequence Number was exceeded. Truncate the Range Sequence Number. No response is required. Function not available as the Name has reached the maximum number of characters permitted. The maximum length of the Name was exceeded. Validation fails. Enter a valid Name. No column mappings are defined. Do you want to continue? Confirm that the Command Set is to be created with no column mappings. The system action depends on the user response. Perform one of the following actions:

Click Yes to create the command set. Click No to take no action.
Source already mapped to target. Addition of a Row Exit will discard existing mappings. Do you want to continue? Column mappings are redundant with the existence of a Row Exit and are deleted. The system action depends on the user response. Perform one of the following actions:
Click Yes to continue with the creation of a Row Exit. On completion of the Row Exit wizard, the column mappings are deleted.
144
Click No to take no action and close the Row Exit wizard.
Oracle SID orasid1 returned by the listener differs from Oracle SID orasid2 obtained from the Oracle Database. The Oracle SID supplied must match the Oracle SID obtained from the database to continue with Capture Registration. Validation fails. Verify that the Oracle SID entered in the ORACLEID= parameter of the DBMOVER configuration file matches the Oracle SID of the database. Please enter a Data Buffer number in the range min_range to max_range. The Data Buffer number is not within the valid range. Validation fails. Enter a Data Buffer number within the valid range. Please enter an Index Buffer number in the range min_range to max_range. The Index Buffer number is not within the valid range. Validation fails. Enter an Index Buffer number within the valid range. Do you want to use the existing publication? Provide user choices to use existing publication or create a new one. The system action depends on the user response. Perform one of the following actions:
Click Yes to continue processing. Click No to create a new publication. PWX-01927 Explanation: System Action: User Response: Any existing articles defined to the PowerExchange publication will be dropped.Do you want to continue? Warning message for publication replacement. The system action depends on the user response. Perform one of the following actions:
Click Yes to create a publication. Click No to take no action. PWX-01928 Explanation: System Action: User Response: Article already exists with a different capture profile. Do you want to continue? Warn user the consequence of updating article information. The system action depends on the user response. Perform one of the following actions:
Click Yes to update the article. Click No to take no action. PWX-01929 Explanation: System Action: This will change the capture profile of an existing table. Do you want to continue? Warn user the possibility of remove of existing profile. The system action depends on the user response.
PWX-01000 to PWX-01999
145
User Response:
Perform one of the following actions:
Click Yes to update the article. Click No to take no action. PWX-01930 Explanation: System Action: User Response: It is recommended that your Striva settings are imported to the Informatica registry key. Do you want to do this? As part of the Navigator rebadging, the Striva registry key information must be copied to the Informatica registry key to avoid loss of Navigator settings. The system action depends on the user response. Perform one of the following actions:
Click Yes to continue processing. Click No to take no action. PWX-01931 Explanation: User Response: PWX-01936 Explanation: User Response: PWX-01937 Explanation: User Response: PWX-01938 Explanation: User Response: PWX-01939 Explanation: User Response: PWX-01940 Explanation: User Response: PWX-01943 Explanation: User Response: PWX-01944 Explanation: Striva registry settings have been successfully imported. Confirmation of successful Striva registry key import to the Informatica registry key. Click OK to close the message dialog box. Unicode font font is not present on this system. Some characters may not be displayed correctly. A Unicode font is necessary to display all characters correctly. Install correct Unicode font. Creator name cannot be used in a registration as it is greater than length characters. Creator names greater than the maximum number of characters cannot be used in registrations. Click OK to close the message dialog box. Schema name cannot be used in a registration as it is greater than length characters. Schema names greater than the maximum number of characters cannot be used in registrations. Click OK to close the message dialog box. Table name cannot be used in a registration as it is greater than length characters. Table names greater than the maximum number of characters cannot be used in registrations. Click OK to close the message dialog box. Column name cannot be used in a registration as it is greater than 32 characters. Column names of greater than 32 characters cannot be used in registrations. Click OK to close the message dialog box. File name is read only. Please save to an alternative name. The file name is read-only. Save to alternative file. Please enter an Owner Key Position in the range min_range to max_range. The Owner Key Position is not within the valid range.
146
System Action: User Response: PWX-01945 Explanation: User Response: PWX-01947 Explanation: System Action: User Response: PWX-01948 Explanation: System Action: User Response: PWX-01949 Explanation: System Action: User Response: PWX-01950 Explanation: System Action: User Response: PWX-01951 Explanation: User Response: PWX-01952 Explanation: User Response: PWX-01953 Explanation: System Action: User Response: PWX-01954 Explanation: System Action: User Response:
Validation fails. Enter an Owner Key Position within the valid range. List item name not found. DL1 field not found in list. Click OK to close the message dialog box. Please enter an Owner Page Group in the range min_range to max_range. The Owner Page Group is not within the valid range. Validation fails. Enter an Owner Page Group within the valid range. Please enter an Owner Radix in the range min_range to max_range. The Owner Radix is not within the valid range. Validation fails. Enter an Owner Radix within the valid range. Please enter a Page Group in the range min_range to max_range. The Page Group is not within the valid range. Validation fails. Enter a Page Group within the valid range. Please enter a Radix in the range min_range to max_range. The Radix is not within the valid range. Validation fails. Enter a Radix within the valid range. Please select only one capture registration for merging. Only one capture registration can be selected for merging. Select one capture registration. Please enter a valid bulk datamap name. A bulk data map name is needed for merging. Enter a valid bulk data map name. Record record_name not found. Changes to the source Data Map may have occurred. Record not found in map. The data map might have changed since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Unknown Extension Type. Expression field type unknown. Stop saving of Extract Definition. If the problem persists, contact Informatica Global Customer Support.
PWX-01000 to PWX-01999 147
Table tabname not found. Changes to the source Data Map may have occurred. Table not found in map. The data map might have been altered since the extraction map was generated. The extraction process ends. Verify that the extraction map is valid. Column colname not found. Changes to the source Data Map may have occurred. Column not found in map. The data map may have altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Document docname not found. Changes to the source Data Map may have occurred. Document not found in map. The data map may have altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Element elename not found. Changes to the source Data Map may have occurred. Element not found in map. The data map may have altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Field fldname not found. Changes to the source Data Map may have occurred. Field not found in map. The data map may have altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Column colname not found. Error in renaming column. Changes to the source Data Map may have occurred. Column not found in map. The data map may have altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Record Dependency recdep not found. Changes to the source Data Map may have occurred. Record Dependency not found in map. The data map may have altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid.
148
PWX-01962 Explanation: System Action: User Response: PWX-01963 Explanation: System Action: User Response: PWX-01964 Explanation: System Action: User Response: PWX-01965 Explanation: User Response: PWX-01966 Explanation: User Response: PWX-01967 Explanation: User Response: PWX-01968 Explanation: System Action: User Response: PWX-01969 Explanation: System Action: User Response: PWX-01970 Explanation: System Action: User Response:
Vertical Array Control array not found. Changes to the Data Source may have occurred. Vertical Array Control not found in map. The data map might have been altered since the extract map was generated. The extraction process ends. Verify that the extraction map is valid. Bulk datamap table array not found. Extract Definition cannot be loaded for amendment. Table not found in bulk map. The extraction process ends. Verify that the extraction map is valid. Documentation file PowerExchangeHelp.chm cannot be found in directory dir. The help file, PowerExchangeHelp.chm, was not found in Helpdoc directory. The online Help is not displayed. Ensure that the file PowerExchangeHelp.chm is in the Helpdoc directory. Warning - Some column data is greater than 256 characters and has been truncated for display purposes. Row Test unable to display column data greater than 256 characters. No response is required. Warning - You are about to add a field after field name which is end of record delimited. A field is being added after an End of Record delimited record. Click OK to close the message dialog box. The name of this table is invalid for registration purposes. PowerExchange only allows registration of tables with names comprising characters in the range ASCII x00-x7F plus GB pound and Yen signs Click OK to close the message dialog box. Please enter a Minimum Root Length in the range min_range to max_range. The Minimum Root Length is not within the valid range. Validation fails. Enter a Minimum Root Length within the valid range. Please enter a Data Length in the range min_range to max_range. The Data Length is not within the valid range. Validation fails. Enter a Data Length within the valid range. Please enter a Prefix Length in the range min_range to max_range. The Prefix Length is not within the valid range. Validation fails. Enter a Prefix Length within the valid range.
PWX-01000 to PWX-01999
149
Please enter a Control Portion Length in the range min_range to max_range. The Control Portion Length is not within the valid range. Validation fails. Enter a Control Portion Length within the valid range. Key key_name found in table table_name is not valid. The key in the table is not valid. Validation fails. Place a valid key in the table. Key key_name found in table table_name is not valid and has been removed. The key in the table is not valid and was removed. Validation fails. Place a valid key in the table. Enter an IDMS Presspack DCTABLE Name. The CA-IDMS Presspack COMPRESS option is active on the records from which PowerExchange captures changes. However, the Presspack DCTABLE name is not specified. Presspack requires this name to find the DCT table to use for runtime decompression during PowerExchange change data capture (CDC). PowerExchange Navigator validation of the data map fails. Enter a value for the Presspack DCTABLE name on the records of interest for CDC. Only one compression option is allowed to be active. CA-IDMS standard compression and Presspack compression are mutually exclusive. Only one of these compression options can be active for your IDMS records at a time. PowerExchange Navigator validation of the data map fails. Clear one of the compression options.. Enter a Key Position in the range minimum to maximum or clear the field. The key position is not within the valid range of values. PowerExchange Navigator validation of the data map fails. Enter a key position that is within the valid range of values.
PWX-02000 to PWX-02999
PWX-02000 Explanation: System Action: User Response: PWX-02001 Explanation: Database logon error. UserId must be specified. A connection to a database requires a user ID. Connection attempt is abandoned. Provide a user ID. Database logon error. Password must be specified. A connection to a database requires a password.
150
Connection attempt is abandoned. Provide a password. Database connection error. SQLCODE = sqlcode. UserId = user_ID. Database = database. A connection to a database returned an error. Connection attempt is abandoned. Verify that the connection parameters (database name, user ID, password) are correct. Database disconnect error. SQLCODE = sqlcode. A disconnect from a database return an error. The connection might be still open. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Cursor open error. SQLCODE = sqlcode. An open cursor call returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Cursor close error. SQLCODE = sqlcode. A close cursor call returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL prepare error. SQLCODE = sqlcode. A SQL prepare call returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL describe error. SQLCODE = sqlcode. A SQL describe call returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL statement is not a SELECT. An error was issued because a the statement being describe in READMODE is not a select one. The database connection is closed. Contact Informatica Global Customer Support. SQL error binding input variable. SQLCODE = sqlcode. A bind of an input variable returned an error.
PWX-02000 to PWX-02999 151
The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL exec error. SQLCODE = sqlcode. An SQL exec call returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL fetch error. SQLCODE = sqlcode. An SQL fetch call returned an error. The database connection is closed. Review the sqlcode in the database manual. For Adabass, an SQLCODE of 1255 should be interpreted as an SQLCODE of 255 (NAB error). If the problem persists, contact Informatica Global Customer Support. SQL error binding output variable. SQLCODE = sqlcode. A bind of an output variable returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Rollback error. SQLCODE = sqlcode. A rollback returned an error. The database connection is closed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Table does not exist. SQLCODE = sqlcode. A SQL call was attempted using a non existing table. The call failed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Too many active requests for module module_name. A SQL call was issued but there are too many requests for that module. The call was not executed. Wait until some of the other requests complete. Length of SQL generated for insert exceeds num_bytes bytes. The length of the SQL call exceeds the maximum allowed. The call was not executed. Use a different SQL call. If the problem persists, contact Informatica Global Customer Support.
152
Error executing native command command. The execution of a native command ended up with an error. The call was not executed. Verify that the command is a valid one, contact Informatica Global Customer Support otherwise. Commit error. SQLCODE = sqlcode. The execution of a commit call ended up with an error. The commit was not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL insert failure. SQLCODE = sqlcode. The execution of a insert call ended up with an error. The insert was not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Row in error is row row. The execution of a SQL call ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Declare cursor error. SQLCODE = sqlcode. The execution of a declare cursor call ended up with an error. The declare cursor was not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Allocate descriptor error. SQLCODE = sqlcode. The execution of an allocate call ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Get descriptor error. SQLCODE = sqlcode. The execution of a get descriptor ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL put error. SQLCODE = sqlcode. The execution of a SQL put get ended up with an error. The SQL call is not executed.
PWX-02000 to PWX-02999
153
User Response:
Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Truncate failed. SQLCODE = sqlcode An attempt to clear a file ended up with an error. The request fails. Review the sqlcode/errno. If the problem persists, contact Informatica Global Customer Support. SQL PARM prepare error. SQLCODE = sqlcode. The execution of a SQL prepare ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. SQL PARM describe error. SQLCODE = sqlcode. The execution of a SQL describe ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Length of SQL generated for update exceeds number bytes. The SQL sentence generated exceeds the maximum limit. The SQL call is not executed. Use a shorter SQL sentence or If the problem persists, contact Informatica Global Customer Support. SQL update failure. SQLCODE = sqlcode. The execution of a SQL prepare ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Length of SQL generated for delete exceeds number bytes. The SQL sentence generated exceeds the maximum limit. The SQL call is not executed. Use a shorter SQL sentence or If the problem persists, contact Informatica Global Customer Support. SQL delete failure. SQLCODE = sqlcode. The execution of a SQL delete ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support.
154
Group Source read requested, but GS option not set. The execution of a SQL delete ended up with an error. The SQL call is not executed. Review the sqlcode in the database manual. If the problem persists, contact Informatica Global Customer Support. Oracle id oracle_id not found in config. Oracle Id needed to connect to Oracle. The connect was not attempted. Review the configuration parameters. Stop on Errors range is 0 - 2147483647. The Stop on Errors value is not within the valid range. Validation fails. Enter a Stop on Errors value within the valid range. DB2 subsystem subsystem_id, release db2_release does not support DB2V8 new-function facilities The DB2 subsystem was configured as DB2V8 new-function mode through the DB2ID configuration parameter, but is not running DB2 V8 in new-function mode Disconnect from DB2 and return error Correct the DB2ID parameters for this DB2 subsystem DB2 subsystem subsystem_id, release db2_release does not support V8 compatibility mode/preV8 facilities The DB2 subsystem was configured as DB2V8 compatibility mode or pre-V8 through the DB2ID configuration parameter, but is running DB2 V8 in new-function mode Disconnect from DB2 and return error Correct the DB2ID parameters for this DB2 subsystem Database connection error. UserId = user_ID. Database = database. A connection to a database returned an error. Connection attempt is abandoned. Review the connection parameters (database name, user ID, password). Database connection error. UserId = user_ID. Server = server. A connection to a database returned an error. Connection attempt is abandoned. Review the connection parameters (server name, user ID, password). Database connection error. UserId = user_ID. Server = server. Database = database. A connection to a database returned an error. Connection attempt is abandoned. Review the connection parameters (server name, database name, user ID, password).
PWX-02000 to PWX-02999
155
156
identifier An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. operator An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. hexadecimal constant An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. compound identifier An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. quoted identifier An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. end of statement An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. numeric constant An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. character constant An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. parameterized SQL substitution marker An error occurred with this type of token within the SQL Processing ends. To diagnose the problem, see associated messages.
Error positionin SQL: SQL Displays up to 100 bytes of SQL in error. If the SQL was truncated then the position of the error is provided. Processing ends. Fix the SQL and try again. SQL error at position position. Parameterized SQL substitution marker not expected. A parameterized SQL substitution marker (?) is not allowed in this context. Processing ends. Ensure that the question marks are in the allowed positions. The DB2390IMG access method is only valid in a mainframe platform. The DB2390IMG access method should be run in a mainframe platform. The system does not perform the extraction. Change the location to point to a mainframe PowerExchange Listener. CAPX/CAPXRT table does not include mandatory column(s) for Apply. columns The table does not include a column needed for Apply Processing ends. Review extraction map columns. Verify that AutoGeneratedColumns are selected. SQL error at position position. Two tier table name table_name must be of format schema.mapname_table_name. The table name has not two tiers. Processing ends. Verify table name. unknown token type An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. Error error_num parsing SQL. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected keyword keyword. Found token token. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Length of token exceeds length bytes. An error occurred during parsing of a SQL statement.
PWX-02000 to PWX-02999
157
System Action: User Response: PWX-02123 Explanation: System Action: User Response: PWX-02124 Explanation: System Action: User Response: PWX-02125 Explanation: System Action: User Response: PWX-02126 Explanation: System Action: User Response: PWX-02127 Explanation: System Action: User Response: PWX-02128 Explanation: System Action: User Response: PWX-02129 Explanation: System Action: User Response: PWX-02130 Explanation: System Action: User Response:
The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Identifier identifier contains too many levels of qualifier. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected an identifier following final period in identifier identifier. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Character char is invalid following final period in identifier identifier. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Identifier identifier is missing closing quotes. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Invalid null identifier found in identifier. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected column name. Found constant. An error occurred during parsing of a SQL statement. A column name was expected. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected identifier. Found token token. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected result name. Found token token. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct.
158
SQL error at position position. Expected operator , or keyword FROM. Found token token. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected end of statement or WHERE. Found token token. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Table name table_name requires schema name. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify the table name in the SQL statement. SQL error at position position. Table name table_name requires schema and map names. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify the table name in the SQL statement. SQL error at position position. Qualifier qualifier is not an exposed name in the FROM list. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Name name is ambiguous. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Token exceeds length bytes. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct. Error loading data map qualifier1.qualifier2. The loading of a data map failed. Processing ends. The map might be corrupted. Create the map again and retry the request. On the MVS platform, verify the region size associated with the job. A larger region might be needed to load the map.
PWX-02000 to PWX-02999
159
SQL error at position position. Table table_name does not exist. Table used in a SQL statement does not exist. Processing ends. Verify that the SQL statement is correct. SQL error at position position. Column column_name does not exist in table table_name. Column used in a SQL statement does not exist in a particular table. Processing ends. Verify that the SQL statement is correct. Record mapping failure. Table=table_name. Record=record_name. Row=row_number. Error mapping an input record. Terminate or skip the record. It depends of the option defined in the data map Verify the data on the row affected and the record definition in the data map. Field extends past end of record. Field=field. Table=table_name. Record=record_name. Row=row_counter. The length of the input data is shorter than the input record expected. Processing ends. Verify the data on the row affected and the record definition in the data map. Calculated field length of field_length bytes exceeds maximum of max_length. Field=field_name. Table=table_name. Record=record_name. Row=row_number. The calculated field length of the input record is greater than the maximum length of the field. Processing ends. Verify the data on the row affected and the record definition in the data map. Short record read. Expected length bytes. Read length bytes. Record count=counter. A data record read shorter than expected. Processing ends. Verify the data on the row affected and the record definition in the data map. Count conversion error. Count field count_field_name for field_name. Table=table_name. Record=record_name. Row=row_number. Reason: Null field. A non optional count field has null values. Processing ends. Verify the data on the row affected. Count conversion error. Count field count_field_name for field_name. Table=table_name. Record=record_name. Row=row_number. Reason: Length error. Error mapping a length count field for a variable length field. Processing ends. Verify the data on the row affected.
160
PWX-02147 Explanation: System Action: User Response: PWX-02148 Explanation: System Action: User Response: PWX-02149 Explanation: System Action: User Response: PWX-02150 Explanation: System Action: User Response: PWX-02151 Explanation: System Action: User Response: PWX-02152 Explanation: User Response: PWX-02153 Explanation: System Action: User Response: PWX-02154 Explanation: System Action: User Response:
Count conversion error. Count field count_field_name for field_name. Table=table_name. Record=record_name. Row=row_number. Reason: message Error mapping a length count field for a variable length field. Processing ends. Verify the data on the row affected. Variable array count error. Array=array_name. Table=table_name. Record=record. Row=row_number. Computed size=size. Specified=specified_size. Error mapping an array. Processing ends. Verify the data on the row affected and the array definition in the data map. Conversion length error. Field=field_name. Table=table_name. Record=record_name. Row=row_number. An error occurred during a conversion process. Processing ends. Verify the data on the row affected. Date-time conversion error. Field=field_name. Table=table_name. Record=record_name. Row=row_number. Reason: message An error occurred during a date-time conversion process. Processing ends. Verify the data on the row affected. Row skipped due to data errors. Error arising from expression evaluation due to data conversion or a data checking error. Skip the row Verify the data on the row affected. First count bytes of bad data: <data> x'hex_data'. Bad data was printed, causing errors. View associated messages. Field contents have failed validity checks. Field=field_name. Table=table_name. Record=record_name. Row=row_number. The specified field failed validation. Processing ends. Verify the record definition in the data map and the data on the row affected. Numeric conversion error. Field=field_name. Table=table_name. Record=record_name. Row=row_number. Reason: message An error occurred during a numeric conversion process. Processing ends. Verify the record definition in the data map and the data on the row affected.
PWX-02000 to PWX-02999
161
WHERE clause must contain at least one conditional expression. Error parsing an SQL statement, WHERE clause without conditional expression. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected ). Found token1 token2. Error parsing an SQL statement, ) expected. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Mismatched ). Error parsing an SQL statement, mismatched ). The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected boolean operator operator. Found token1 token2. Error parsing an SQL statement, boolean operator expected. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected identifier or constant. Found token1 token2. Error parsing an SQL statement, expected identifier or constant. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected keyword keyword or relational operator. Found token1 token2. Error parsing an SQL statement, keyword expected. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected constant. Found column name. An error occurred during parsing of a SQL statement. Expected constant, found column name instead. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Constant missing closing quote. An error occurred during parsing of a SQL statement. Constant missing closing quote. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Constant exceeds length bytes. An error occurred during parsing of a SQL statement. Constant exceeding maximum length.
162
The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Invalid digit digit in hexadecimal constant. An error occurred during parsing of a SQL statement. Invalid digit found in hexadecimal constant. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Hexadecimal constant does not contain an even number of digits. An error occurred during parsing of a SQL statement. Hexadecimal constant with even number of digits. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Invalid numeric constant constant. An error occurred during parsing of a SQL statement. Invalid numbered constant found. The SQL call is not executed. Verify that the SQL statement is correct. Column column_name in expression expression at position position is illegal for comparison. Length exceeds length bytes. An error occurred during parsing of a SQL statement. Column name in expression is illegal. The SQL call is not executed. Verify that the SQL statement is correct. Comparison expression expression at position position is always constant. An error occurred during parsing of a SQL statement. Comparison expression is always constant. The SQL call is not executed. Verify that the SQL statement is correct. Comparison expression expression at position position is illegal. Mismatched operand types (type1/type2). An error occurred during parsing of a SQL statement. Comparison expression with mismatched types. The SQL call is not executed. Verify that the SQL statement is correct. Evaluation of expression expression at position position failed with return code return_code at row row. Explanation follows: An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct.
PWX-02000 to PWX-02999
163
SQL error at position position. Expected character constant for LIKE pattern. An error occurred during parsing of a SQL statement. Expected character constant for LIKE pattern. The SQL call is not executed. Verify that the SQL statement is correct. Comparison expression expression at position position is illegal. Column is not CHAR or VARCHAR type. An error occurred during parsing of a SQL statement. Expecting a CHAR or VARCHAR type column. The SQL call is not executed. Verify that the SQL statement is correct. Numeric constant constant in expression expression at position position is illegal. More than max_digits digits before/after point. An error occurred during parsing of a SQL statement. Numeric constant with too many digits in expression. The SQL call is not executed. Verify that the SQL statement is correct. Comparison expression expression at position position is illegal. Bad date constant 'constant'. Expected YYYY-MM-DD. An error occurred during parsing of a SQL statement. Date constant with incorrect format, or outside DATERANGE. The SQL call is not executed. Verify all dates in the SQL statement are valid, and within the DATERANGE configuration setting. Comparison expression expression at position position is illegal. Bad time constant 'constant'. Expected HH.MI.SS. An error occurred during parsing of a SQL statement. Time constant with incorrect format. The SQL call is not executed. Verify that the SQL statement is correct. Comparison expression expression at position position is illegal. Bad timestamp constant 'constant'. Expected YYYY-MM-DD HH.MI.SS.NNNNNN. An error occurred during parsing of a SQL statement. Timestamp constant with incorrect format. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Expected single escape character. An error occurred during parsing of a SQL statement. The SQL call is not executed. Verify that the SQL statement is correct.
164
SQL error at position position. Escape character character in LIKE pattern only valid before _ or %. An error occurred during parsing of a SQL statement. Escape character invalid. The SQL call is not executed. Verify that the SQL statement is correct. SQL error at position position. Escape character cannot be % or _. An error occurred during parsing of a SQL statement. Incorrect escape character. The SQL call is not executed. Verify that the SQL statement is correct. Error building output record. Fld field_name. Table table_name. Record record_name. Value value (map_length bytes) exceeds target length of data_length. Field definition is too short for the input data. Processing ends. Verify the output data map definition and the data on the row affected. Error building output record. Fld field_name. Table table_name. Record record_name. Date conversion error: date. Error converting to the output date format using an specified format string Processing ends. Verify the output data map definition and the data on the row affected. The result set does not contain any columns. The result set of a statement does not contain any columns. Processing ends. Verify the SQL statement. Output to tables built upon 1 physical record is not supported. Output table with more than one physical record. Processing ends. Verify the definition of the output data map. The target access method is not supported for output. Access method specified for output is not valid. Processing ends. Verify the output access method in the move command. Output to tables containing arrays in list format is not supported. A data move was attempted to a table with array in list format. Processing ends. Verify the table in the output data map.
PWX-02000 to PWX-02999
165
Error building output record. Fld field_name. Table table_name. Record record_name. NUMCHAR conversion error: message. An error occurred during a numeric conversion process. Processing ends. Verify the record definition in the data map and the data on the row affected. Field field_name references ADABAS field field_name with a conflicting level of subscript to a previous reference. Adabas file structure invalid. Processing ends. Review and correct Adabas file definition. Field field_name references ADABAS field field_name in a different group (group_name) from a previous reference (group_name). Adabas file structure invalid. Processing ends. Review and correct Adabas file definition. Adabas field field_name referenced by field_name does not exist in FDT. DBId=database_ID. File=file_num. Dictionary definition does not match FDT. Processing ends. Verify and correct dictionary mismatch with FDT. Field field_name references ADABAS field field_name in an invalid PE group (group). True parent is parent. Adabas file structure invalid. Processing ends. Verify and correct Adabas file definition. Field field_name references ADABAS field field_name in an invalid PE group (group). field_name is not a member of any PE group. Dictionary definition does not match FDT. Processing ends. Verify and correct dictionary mismatch with FDT. Found negative length count for ADABAS field field_name. Invalided field length count in Adabas field. Processing ends. Correct field length definition. Array overflow for field field_name mapped to ADABAS field field_name at array level level_num. Actual=level_num. Defined=level_def. Dictionary definition does not match FDT. Processing ends.
166
User Response: PWX-02194 Explanation: System Action: User Response: PWX-02195 Explanation: System Action: User Response: PWX-02196 Explanation: User Response: PWX-02197 Explanation: System Action: User Response: PWX-02198 Explanation: System Action: User Response: PWX-02199 Explanation: System Action: User Response: PWX-02200 Explanation: System Action: User Response: PWX-02201 Explanation: System Action: User Response:
Verify and correct dictionary mismatch with FDT. Record mapping failure. Table=table_name. Record=record_name. Row=row_number. Offset into file = offset. An error occurred trying to map a record from a file to a data map record. Processing ends. Verify the record definition in the data map. Record mapping failure. Table=table. Unknown record type at offset offset into file. Record of unknown type found in file. Processing ends. Verify the record definition in the data map. ADABAS OPT: message. Information about Adabas optimization. No response is required. Error Creating datamap: schema/map_name Error produced when trying to create an internal temporary data map in memory. Processing ends. Verify the region size if MVS. Contact Informatica Global Customer Support. Search field and field definition mismatch. Datamap=datamap_name, search field position= position. Search field does not match a field or group of consecutive fields. Processing ends. Verify that the search field definition maps a field or several consecutive fields. feature feature not available for access method access_method on platform platform A feature not available for a particular access method in a given platform was requested. Processing ends. Verify the move command. Incorrect environment for DL1 execution. Check NETPORT for server job or executable for client. Error trying to run a NETPORT job. Processing ends. Verify NETPORT for server job, executable for client or location. PCB number pcb_number is not in the specified PSB. Incorrect PCB number used. Processing ends. Verify the PCB/PSB used in the data map.
PWX-02000 to PWX-02999
167
Unexpected DL1 status code status_code. message An DL1 error occurred. Processing ends. Verify the meaning of the status code in the DL1 documentation. Invalid variable segment length encountered. Segment = Segment_name. Length = length. Length specified in the data map for that segment is incorrect. Processing ends. Verify the record definition mapping that segment in the data map. Unexpected error returned from Get_IMSConcatenatedKey. RC = r<eturn_code>, reason = <reason_code> The Get_IMSConcatenatedKey function returned one of the following return codes:

001. Unsupported DBD type. 002. Supplied buffer to short for key. 003. Required sub module not found. 004. Required sub module load failed. This return code is associated with a reason code in the low-order two bytes, as follows: +0004. MODULE NOT FOUND. +0008. DFSMODU0 ALLOCATION ERROR. +000C. BLDL ALLOC ERROR. +0010. BLDL/FETCH I/O ERROR. +0014. REQUESTED MEMBER NOT A LOAD MODULE. +001C. FETCH PROGRAM CHECK. +0024. DCB NOT OPEN FOR BLDL ERROR (CAN BE CAUSED IF THE POWEREXCHANGE LOAD LIBRARY IS A PDSE INSTEAD OF A PDS). 005. Not used. 006. Sub module unload failed. 007. Free storage failed. 008. Not used. 009. Not used. 010. ODBA SSOB block not found. 011. Alloc storage failed. 012. No IMS ESS found. 013. ECCR not installed. 014. Agent not found. 015. Bad agent identifier. 016. Not used. 017. Get agent handle failed. 018. Agent authorization call failed. 019. Agent de authorization call failed. 020. ISWITCH failed. 021. Return from ISWITCH failed. 022. Region type not supported. System Action: User Response: Processing ends. Verify the return code value.
168
PWX-02205 Explanation: System Action: User Response: PWX-02206 Explanation: System Action: User Response: PWX-02207 Explanation: User Response: PWX-02208 Explanation: User Response: PWX-02209 Explanation: User Response: PWX-02210 Explanation: User Response: PWX-02211 Explanation: System Action: User Response: PWX-02212 Explanation: System Action: User Response: PWX-02213 Explanation: System Action: User Response: PWX-02214 Explanation:
Cannot write to multiple segments. An attempt was made to write to IMS using a data map that refers to more than one segment. Processing ends. Only write using single-segment data map. Error validating CCK fields. The CCK fields declared in the data map are insufficient, or incorrectly sized. Processing ends. Verify the data map definition. SQL used: SQL Log of the SQL used. No response is required. Initial IMS call: Function_code The function code of the first call to IMS. No response is required. SSA: <SSA> xhex_value_of_SSA' This message displays the log of the specified SSA that was used by the IMS call. No response is required. Refer to IBM DL1 status code reference. A DL1 error occurred. Look up the errors in the IBM DL1 documentation. Check segment names and hierarchical order. A DL1 error occurred. Processing ends. Verify that the segment names and order in the data map. Check PCB is DB type. Error occurred trying to access a database with a non DB type PCB. Processing ends. Verify that the PCB is specified in the data map. Check DB data sets are defined to the job. Error occurred during an IMS data set open. Processing ends. Verify that the data sets are DD or dynamic allocation. Attempt to insert a segment with a duplicate key. Error occurred during an IMS ISRT.
PWX-02000 to PWX-02999
169
Processing ends. Verify data for conflicting row. ODBA Call_type Call Failed RC=return_code Reason=reason_code. An error occurred after issuing a DL1 call. Processing ends. Verify the DL1 documentation for the return code and reason code. Unexpected DL1 status code Status_code. message.AIB Rc=return_code Reason=reason_code. An error occurred after issuing a DL1 call. Processing ends. Verify the DL1 documentation for the return code and reason code. Target is local. Requested bulk load mode type switched from JOB to TASK A request to run a DB2 bulk load in local mode was changed to run as a task instead of as a job. Job submission is not supported in local mode. The bulk load is run in TASK mode, instead of JOB mode. No response is required. DB2 Array Insert: row row sqlcode sqlcode sqlstate sqlstate An error occurred inserting a row in DB2 V8 new-function mode Processing ends. No response is required. DB2 subsystem identifier must be specified. Trying to execute an attach without a DSN ID. Processing ends. Provide a DB2 subsystem identifier. DB2 subsystem identifier dsnid is invalid. Trying to execute an attach with an invalid DSN ID. Processing ends. Provide a valid DB2 subsystem identifier. DB2 CAF/DB2 level mismatch. There is a mismatch between the DB2 CAF and DB2 releases. Processing ends. Consult the Database Administrator. DB2 subsystem dsnid is not available. CAF RC=return_code. Reason=reason. The DB2 subsystem is not available. Processing ends. Verify that the dsnid is correct and running.
170
PWX-02254 Explanation: System Action: User Response: PWX-02255 Explanation: System Action: User Response: PWX-02256 Explanation: User Response: PWX-02257 Explanation: System Action: User Response: PWX-02258 Explanation: System Action: User Response: PWX-02259 Explanation: System Action: User Response: PWX-02260 Explanation: System Action: User Response: PWX-02261 Explanation: User Response: PWX-02262 Explanation: System Action: User Response:
DB2 AF (AFname) error during phase. Plan=<plan_name>. AF RC=return_code. Reason=reason_code. A DB2 AF error occurred. Processing ends. View the return and reason codes. DB2 AF (AFname) error. SQLCODE=sqlcode. message. A DB2 AF error occurred. Processing ends. View the SQL code and messages. DB2 error formatting message. RC=return_code. Original SQLCODE=sqlcode. Original info=info. Error calling DSNTIAR/sqlaintp to format a previously issued SQL message. View the return code from the utilities. DB2 distinct and large object types are not supported. A describe returned a warning indicating the use of large object types. Large objects are not supported. Processing ends. Contact Informatica Global Customer Support. Could not create PowerExchange catalog view viewname. The creation of a catalog view failed. Processing ends. View other messages for possible SQL errors. The access method access_method is not valid for this platform. Use ValidAccessMethod. The access method used is invalid. Processing ends. Use the access method suggested in the message. Could not grant select authority on object to PUBLIC. A GRANT action on an object failed. Processing ends. View other messages for possible SQL errors. Information only. request_type used for DB2 catalog request. This information message describes a catalog access request. No response is required. Expected parameter of PowerExchange library name not supplied. Job failed. The install catalog view program expects PowerExchange library as parameter. Processing ends. Supply PowerExchange library name.
PWX-02000 to PWX-02999 171
PWX-02263 Explanation: User Response: PWX-02264 Explanation: System Action: User Response: PWX-02265 Explanation: System Action: User Response: PWX-02266 Explanation: System Action: User Response: PWX-02267 Explanation: System Action: User Response: PWX-02268 Explanation: System Action: User Response: PWX-02269 Explanation: System Action: User Response: PWX-02270 Explanation: User Response: PWX-02271 Explanation: System Action: User Response:
Setup of PowerExchange catalog views in library libraryname completed OK. The setup of PowerExchange catalog views finished successfully. No response is required. *** Setup of PowerExchange catalog views in library libraryname FAILED ***. The setup of PowerExchange catalog views did not finish successfully. PowerExchange reports the error. Look for previous messages to check for error and reason codes. PowerExchange catalog view viewname already exists. Skipping to next step. The view the utility tried to create already existed. Skip to the creation of next view. No response is required. Error loading DB2 interface interface_name. Completion code = return_code. Reason = reason_code. The load of an attach facility produced an error. Processing ends. View the return code and reason code. RRS/MVS not active. Completion code = return_code. Reason = reason_code. RRSAF not available. Processing ends. View the return code and reason code. Plan plan_name does not exist or is not authorized to user user_ID. The plan does exist or it is not authorized. Processing ends. Review the plan name. Load cancelled - Maximum number (number) of load tasks are already running. There are too many task using the load utility. Processing ends. Rerun the job when the other tasks have finished. DB2 Loader completed with Warnings. RC=return_code. The DB2 loader completed with warnings. View the meaning of the return code. DB2 Loader completed with Errors. RC=return_code. The DB2 loader completed with errors. Processing ends. View the meaning of the return code.
172
Invalid DB2 loader mode or mode not supported : Flags=(mode). The DB2 loader mode is invalid. Processing ends. Review the DB2 load mode in the configuration parameters. Background job time limit exceeded. No results to report. The background job did not complete in the time specified. Processing ends. Review the Time parameter for load job. Background job not started within time limit. No results to report. The background job did not start in the time specified. Processing ends. Review the DBMOVER parameter for load job. DD Name SYSPRINT is already allocated. Possibly remove it from the Listener JCL. DD Name SYSPRINT is already allocated. Processing ends. Remove the DD SYSPRINT from the PowerExchange Listener JCL. Use of DB2 connection RRSAF with a TASK load invalid. Use CAF or change load mode. The loader (DSNUTILB) uses CAF and PowerExchange Listener is probably using RRSAF. Processing ends. If the type of load is TASK check what connection the PowerExchange Listener has to DB2. The loader (DSNUTILB) uses CAF and an Address space must use only one type of connection. Unable to create communication token to background load, rc=return_code. Mode set to NOWAIT. The system was unable to create a communication token. Option changed to NOWAIT No response is required. Input SQL has parameter parameter marker marker but no where clause. SQL was parsed and there is no where clause. Processing ends. Correct the SQL query. Internal error SQL parameter marker work string too small. size = size need size_need. An internal error occurred. Processing ends. Contact Informatica Global Customer Support,
PWX-02000 to PWX-02999
173
EBCDIC CCSID(s) not provided for ASCII/UNICODE database DB2 translates ASCII/UNICODE data to or from EBCDIC data (OS390 and z/OS). The PowerExchange Listener must have the corresponding EBCDIC CCSIDs for the translated data to process it correctly. Processing ends. See the section in the manual regarding the DB2CODEPAGE configuration parameter, supply suitable CCSID(s), stop/restart the PowerExchange Listener and retry. encoding_scheme type CCSID ccsid has no corresponding codepage There is no corresponding codepage for the CCSID provided. Processing ends. Correct the error. Then, run the request again. If the CCSID is a valid one, contact Informatica Global Customer Support. CCSID ccsid <codepage> is not an encoding_type codepage The specified CCSID has the wrong type, such as an ASCII CCSID instead of an EBCDIC CCSID. Processing ends. Correct the error. Then, run the request again. CCSID ccsid <codepage> is not a type codepage The specified CCSID has the wrong type, such as a single-byte CCSID instead of an double-byte CCSID. Processing ends. Correct the error. Then, run the request again. Active encoding type CCSID is ccsid <codepage> The specified CCSID was issued for corresponding DB2 data. No response is required. CCSID for column <column_name> ccsid does not match configured values The CCSID for the specified column returned by DB2 does not match the corresponding value entered through the DB2CODEPAGE configuration parameter. Processing ends. Correct the configured DB2CODEPAGE values and restart the PowerExchange Listener. Then, run the request again. type codepage for db2_subsystem is code_page <code_page_name> This message is displayed when a DB2 connection is opened.The message indicates which codepage translations are used for a given DB2 subsystem in the absence of explicit definitions made through the DB2CODEPAGE configuration parameter. No response is required. Invalid AS400 override statement found <override_statement> The AS400 DB2 access method issues this message during Describe processing. The format for the override statement should be one of the following formats:
PWX-02282 Explanation: System Action: User Response: PWX-02283 Explanation: System Action: User Response: PWX-02284 Explanation: User Response: PWX-02285 Explanation: System Action: User Response:
FromFile/ToLibrary/ToFile
174
FromFile/ToLibrary/ToFile/ToMember.
PowerExchange does not perform override processing on the statement. DB2 processing continues. Correct the override statement that is in error in the override string. AS400 override string <override_string> contains more than current maximum allowed statements <max_allowed> The AS400 DB2 access method issues this message during Describe processing. The string has a limit to the number of statements that can be processed. PowerExchange does not perform override processing on the additional statements. DB2 processing continues. Correct the override string specified. option_name is unavailable when running in local mode The option indicated is unavailable when PowerExchange is running in local mode, for example, is not through a PowerExchange Listener. These can currently be a DB2 bulk load to a partitioned table, or with NOSUBMIT specified. Processing ends. Run any requests including these options through a PowerExchange Listener, but not as a Netport job. DB2 Bulk load not valid for partitioned and non-partitioned tables Tables for bulk load can be either for partitions or not. Processing ends. Correct the workflow and rerun Filename file_name is invalid for partitioned load File names for partitioned loads must take the form aaa.bbb/PARTnn where nn is the partition number. Processing ends. Correct the file name and rerun. Filename file_name is unknown for partitioned load The filename in the message was not specified as being for a partition. Processing ends. Correct the file name and rerun. Datasource name must be specified. A data source is needed to do a connect. Processing ends. Provide a data source name. AllocEnv failure. An memory error occur allocating an environment handle. Processing ends. Look for possible causes in the ODBC manuals (SQLAllocEnv).
PWX-02000 to PWX-02999 175
CLI SQLState=sqlstate. Native=native_error. message A CLI call returned an error. Log the error. Review the sqlsate, native_error and message in the CLI/ODBC manuals. CLI Function returning function_name is error_code. A CLI call returned an error. Log the error. View the error code for that function in the CLI/ODBC manuals. Could not switch to database database. Error trying to switch to a database other than the default specified in the DSN configuration. Processing ends. Review the database name provided. ODBC driver driver_title removed. The specified ODBC driver was deleted from the registry. Processing continues. No response is required. ODBC driver driver_title added. The specified ODBC driver was added to the registry. Processing continues. No response is required. RC=return_code removing ODBC driver driver_title. error_description. An error occurred when removing the ODBC driver from the registry. Processing ends. Error 6 (component not found in the registry) might occur if an attempt is made to remove drivers that were not installed. RC=return_code adding ODBC driver driver_title. error_description. An error occurred when adding the ODBC driver to the registry. Processing ends. Contact Informatica Global Customer Support. Access method access_method is not allowed with original access method OriginalAccessMethod An invalid combination of access method and original access method have been specified for a task. Certain combinations are currently not permitted, for example you cannot use CAPX for a MSSQL registration. The task ends reporting the error. Correct the request and try again.
176
PWX-02350 Explanation: System Action: User Response: PWX-02351 Explanation: System Action: User Response: PWX-02352 Explanation: System Action: User Response: PWX-02353 Explanation: System Action: User Response: PWX-02354 Explanation: System Action: User Response: PWX-02355 Explanation: System Action: User Response: PWX-02356 Explanation: System Action: User Response: PWX-02357 Explanation:
Server name not specified and DSQUERY environment variable not set. A problem occurred trying to connect to the server specified and the required environment variable DSQUERY was not set. No connection was made. Report error and abend processing. Verify that the server name was correctly entered and that the server instance is available. Connect failed to server server_name in function function_name, return code = return_code. A problem occurred connecting to the server specified while attempting the function specified. The return code has also been displayed. Report error and abend processing. Verify that the server is still available. Unable to switch to database database_name using command on server server_name, location return code = return_code. The command specified was unable to switch to the database specified on the server specified. The return code is displayed, location is 'client' or 'server'. Report error and abend processing. Verify that the server is still available. Server-Msg: message_number message The Sybase server has returned the displayed error number and message. Report error and abend processing. Note the message displayed and act accordingly. Client-Msg: Severity=severity_code,L=layer,O=origin, S=severity,N=Number,Message_code,message The Sybase client has returned the displayed information. Report error and abend processing. Note the message displayed and act accordingly. Describe failed to server server_name in function function, return code = return_code. The describe failed while attempting the function specified. The return code has also been displayed. Report error and abend processing. Verify that the server is still available. Table referenced in SQL_Statement not found in database database_name on server server_name. The table mentioned in the SQL statement was not found. Report error and abend processing. Verify that the table is still available. Column name column_name of length length from database database_name too long for PowerExchange data descriptor. The column name is too long for PowerExchange.
PWX-02000 to PWX-02999
177
Report error and abend processing. The column in the source database might need to be excluded from the requested data, or the name changed to a shorter one. Column name column_name from database database_name has unhandled datatype of Datatype. The column mentioned is of a datatype that is not supported by PowerExchange. Report error and abend processing. The column in the source database must be excluded from the requested data. Contact Informatica Global Customer Support with details of the datatype if you feel it should be included in the PowerExchange product. Bulk Load Commit, No. of rows (or -1) = Number, for table table_name in database database_name The number of rows committed. Informational message only. No response is required. Bulk Load Err,N=error_code,S=severity,message An error occurred on the Bulk Load. The error code, severity and message string are displayed. Report error and abend processing. Note the message displayed and act accordingly. Bulk Load OS Err N=error_code,S=severity,message An Operating System error occurred on the Bulk Load. The error code, severity and message string are displayed. Report error and abend processing. Note the message displayed and act accordingly. Bulk Load Srvr=server_name,Prc=Procedure_name, N=message_number,ST=message_state,S=severity, L=line_number,message_text An error occurred on the Bulk Load Server. The procedure name, message state and line number are also displayed. Report error and abend processing. Note the message displayed and act accordingly. Failure when using server,server_name,database,database_name, in function function_name,return code = return_code. An error occurred when using the Server. The procedure name, message state and line number are also displayed. Report error and abend processing. Note the message displayed and act accordingly. IDMS Sub-Schema not specified in the data map data_map_name. The data map doesn't contain a sub-schema. The system displays an error message and waits for the user response.
178
User Response: PWX-02401 Explanation: System Action: User Response: PWX-02402 Explanation: System Action: User Response: PWX-02403 Explanation: System Action: User Response: PWX-02404 Explanation: System Action: User Response: PWX-02405 Explanation: System Action: User Response: PWX-02406 Explanation: System Action: User Response:
Correct the data map or import the metadata again to re-create the data map. IDMS Function function returned status status. The IDMS function displayed has failed with the status shown. The system displays an error message and waits for the user response. Contact your database systems team with details of the error. IDMS Record name not specified in data map record recordname for table table_name. The record name within the table displayed was not specified in the data map. The system displays an error message and waits for the user response. Correct the data map or import the metadata again to re-create the data map. IDMS Area name not specified in data map record recordname for table table_name. The area name for the record within the table displayed was not specified in the data map. The system displays an error message and waits for the user response. Correct the data map or import the metadata again to re-create the data map. IDMS Set name not specified in data map record recordname for table table_name. The set name for the record within the table displayed was not specified in the data map. The system displays an error message and waits for the user response. Correct the data map or import the metadata again to re-create the data map. IDMS System Index Set name not specified in data map record recordname for table table_name. The system index set name for the record within the table displayed was not specified in the data map. The system displays an error message and waits for the user response. Correct the data map or import the metadata again to re-create the data map. IDMS Unable to Start IDMSX unshared service service, service library = service_library, rc = return_code. IDMS was unable to start the requested unshared service. The task that encounters the error ends. Correct the unshared service name and service library name, and/or check appropriate service permissions have been granted, and run the request again. IDMS Unable to Connect to IDMSX shared service service, service library = service_library, rc = return_code. IDMS was unable to connect to the requested shared service. The task that encounters the error ends. Correct the shared service name and service library name, and/or check appropriate service permissions have been granted, and run the request again. IDMS Error when stopping IDMSX unshared service service, service library = service_library, rc = return_code. IDMS was unable to stop the requested unshared service.
PWX-02000 to PWX-02999
179
The task that encounters the error ends. Correct the unshared service name and service library name, if necessary, and run the request again. If the names given are correct, contact your IT department or Informatica Global Customer Support and report the message. IDMS Error when disconnecting from IDMSX shared service service, service library = service_library, rc = return_code. IDMS was unable to disconnect from the requested shared service. The task that encounters the error ends. Correct the shared service name and service library name, if necessary, and run the request again. If the names given are correct, contact your IT department or Informatica Global Customer Support and report the message. IDMS can only be accessed with security level 2 via a Netport job. When security level 2 is specified, the access must go through a Netport job to ensure that each access refreshes security information. The system displays an error message and waits for the user response. Use a Netport connection for access. IDMS. Failed to load module module, rc=return_code reason code=reason_code. The loading of an IDMS subschema failed. Processing ends. The system issues an error message. Review the documentation for the meaning of the return code and reason codes. IDMS. The module loaded module has an incorrect eye catcher. The IDMS module loaded has not the expected eye catcher IB50. Processing ends. The system issues an error message. We probably have loaded an invalid subschema. No default server specified. Message not currently used. No response is required. IDMS Meta Data Retrieval, Job jobname failed return code = return_code. The IDMS Meta Data retrieval job has failed with the return code shown. The system displays an error message and waits for the user response. Contact your system programmer with details of the job and return code for further investigation. IDMS Meta Data Retrieval, Timed Out waiting for Job jobname. The IDMS Meta Data retrieval job has timed out. The system displays an error message and waits for the user response. Contact your system programmer with details of the job for further investigation. IDMS Meta Data Retrieval, Job jobname not started. The IDMS Meta Data retrieval job was not started.
PWX-02410 Explanation: System Action: User Response: PWX-02448 Explanation: System Action: User Response: PWX-02449 Explanation: System Action: User Response: PWX-02450 Explanation: User Response: PWX-02500 Explanation: System Action: User Response:
180
The system displays an error message and waits for the user response. Contact your system programmer with details of the job for further investigation. IDMS Meta Data Retrieval, PowerExchange Load Library not authorized. The PowerExchange Load Library was not APF authorized. The system displays an error message and waits for the user response. Contact your system programmer and ask for the PowerExchange Load Library to be APF authorized. Unable to create communication token for background metadata retrieval. The allocation of the MVS token services control token failed. The system displays an error message and waits for the user response. To resolve the problem, contact your system programmer. IDMSX - Metadata requested was not available, RC=(return_code1/return_code2/return_code3), please check your parameters. A request for metadata information was made, but the parameters supplied are invalid. The task that encounters the error ends. Correct the parameters and run the request again. IDMSX - Invalid Metadata parameter(s) <metadata_parameters> A request for metadata information was made, but the parameters supplied are invalid. The task that encounters the error ends. Correct the parameters and run the request again. DATACOM Meta Data Retrieval, Job jobname failed return code = return_code. The Datacom Meta Data retrieval job failed with the specified return code. The system displays an error message and waits for the user response. Contact your system programmer with details of the job and return code for further investigation. DATACOM Meta Data Retrieval, Timed Out waiting for Job jobname. The Datacom Meta Data retrieval job timed out. The system displays an error message and waits for the user response. Contact your system programmer with details of the job for further investigation. DATACOM Meta Data Retrieval, Job jobname not started. The Datacom Meta Data retrieval job was not started. The system displays an error message and waits for the user response. Contact your system programmer with details of the job for further investigation. DATACOM Meta Data Retrieval, PowerExchange Load Library not authorized. The PowerExchange Load Library was not APF authorized. The system displays an error message and waits for the user response.
PWX-02000 to PWX-02999
181
User Response:
Contact your system programmer and ask for the PowerExchange Load Library to be APF authorized. Unable to create communication token for background metadata retrieval. The allocation of the MVS token services control token failed. The system displays an error message and waits for the user response. To resolve the problem, contact your system programmer. The metadata requested was not available or you do not have access, please check your parameters. The metadata requested from the Datacom database was not found or you do not have access to it. The system displays an error message and waits for the user response. Review the Datacom metadata requested against the database and correct the parameters entered. Group Source, Access method must be one of CAPX, CAPXRT, EMR, IMSUNLD, NRDB, NRDB2. An invalid access method was passed to the Group Source process. Processing ends. The system issues an error message. Review and correct the access method. Group Source, Access methods cannot be mixed. The access method for all sources must be the same. Processing ends. The system issues an error message. Review all sources and ensure that all access methods are the same. Group Source, An NRDB table contains a complex row. Group source processing cannot return multiple rows unless the New Row option is selected for the record. Group source processing ends. The system issues an error message. Perform the following steps: 1. In the PowerExchange Navigator, open the data map that contains the table. 2. On the Data Map tab, right-click the data map and click Properties. 3. In the Table Properties dialog box for the table, select the record in the Record Dependencies list. 4. In the How do you want to handle multiple instances of selected record?, click New Row. For more information about complex tables, see the PowerExchange Navigator User Guide.
Group Source, The same physical data source must be used for all members of the Group. The physical data source for all members of the group must be the same. Processing ends. The system issues an error message. Ensure that all physical data sources are the same.
182
PWX-02554 Explanation: User Response: PWX-02555 Explanation: System Action: User Response: PWX-02575 Explanation: System Action: User Response: PWX-02576 Explanation: System Action: User Response: PWX-02600 Explanation:
Group Source, number = data_map_file_name, number = data_map_file_name. This message provides additional information, including the data map file names, for message PWX-02553. No response is required. Group Source, Only NRDB or NRDB2 Data Maps for SEQ, ESDS, KSDS or TAPE are allowed. For Group Source, only NRDB or NRDB2 data maps for SEQ, ESDS, KSDS, or TAPE are allowed. Processing ends. The system issues an error message. Ensure that only the allowed data map access methods are used. Multiple Targets, datamap primary paths cannot be mixed. With multiple targets, all primary paths must be the same. Processing ends. The system issues an error message. Ensure that all primary paths are the same for multiple targets. Multiple Targets, datamap access methods cannot be mixed. With multiple targets, all access methods must be the same. Processing ends. The system issues an error message. Ensure that all access methods are the same for multiple targets. Direction Type=type Precn=99 Scale=99 Len=99 Data=xxxx. The message provides information about an E Fields that cannot be converted from one type to another during a declaration. One message describes the from field, which is normally a NUMCHAR. The other message describes the to field. This message is always accompanied by messages PWX-02614, PWX-02603, PWX-02601, and sometimes by message PWX-02626.
The task ends. Determine which E Field is causing the problem by reviewing message PWX-02603. See message PWX-02614 for user responses. Type=99 (type_decription) Length=99 Precision=99 Scale=99. The message provides information about the declaration of a problem E Field. It is always accompanied by message PWX-02603, which displays the name of the field, and by other messages that show the cause of the error. The task ends. Determine which E Field is causing the problem by reviewing message PWX-02603 and associated messages. Correct the E Field. Expression=xxxx. The message displays expression information in a problem E Field. It is always accompanied by message PWX-02603, which displays the name of the field, and by other messages that show the cause of the error. The task ends. Determine which E Field is causing the problem by reviewing message PWX-02603 and associated messages. Correct the E Field.
PWX-02000 to PWX-02999
183
Problem with Record 99 Field Nbr 99 Name xxxx Action Nbr 99. The message identifies a problem E Field that has failed. It is always accompanied by other messages that show the cause of the error. The task ends. In most situations, the corresponding E Field can be identified in the Navigator by using the Name. Where the same name is used in different records, use the record number to distinguish them. Determine the cause of the error from associated messages and correct the E Field. Invalid Expression. xxxxx. When initializing E Fields prior to processing the first record, an expression is met that is not a constant, and it fails validation as a Function. Normally syntax errors on functions should be detected at the time when a map is created by the Navigator. This error is rarely seen. The task ends. Load the data map into the Navigator and go to the E Field Window. All E Fields are validated. The invalid field is highlighted. Correct and save the data map and send it to the remote node. Then, rerun. Problem data. xxxxx. An error was detected in validating function syntax in an expression that caused associated message PWX-02604 and the actual data in error was provided. The task ends. See message PWX-02604 for responses. Unrecognized field type 99. The field type number is not valid. The task ends. Load the map into the Navigator and go to the E Field Window. All E Fields are validated and the problem one highlighted. Correct and Save the data map and send it to the remote node, then rerun. type 99 without name. A field type number was specified indicating that a new E field is being declared, but the name is missing. The task ends. Load the map into the Navigator and go to the E Field Window. All E Fields are validated and the problem one highlighted. Correct and save the data map and send it to the remote node, then rerun. attribute required on field type 99 (field_type). A new E field is being declared, but the attribute (Length or Precision) is missing, and is required for the field type. The task ends. Load the map into the Navigator and go to the E Field Window. All E Fields are validated and the problem one highlighted. Correct and save the data map and send it to the remote node, then rerun.
184
Duplicate declaration for name xxxx A new E field is being declared (it has a field type) but the name was previously used in another E Field. The task ends. Load the map into the Navigator and go to the E Field Window. All E Fields are validated and the problem one highlighted. Correct and save the data map and send it to the remote node, then rerun. Field XXXX not found. A field was not found when processing XML. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. System function xxxx not found. The specified system function (such as CopyData) was not found within module DTLFUNC. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time. RC=99 from function xxxx. The specified function returned the return code that indicates a failure. The task ends. If the message occurred together with a PWX-02614 message, then a problem has occur on attempting to convert a numeric constant that is out of range for a specific E Field, so review message PWX-02614. Otherwise a failure occurred during a call to the specified function and the response depends on which function it is. If the function is CALLPROG, then the user exit program might not be loadable. If the problem cannot be determined, contact Informatica Global Customer Support, specifying the function being performed at the time. Supported attribute = value. The message shows available values for the attribute Associated messages include PWX-02667, which shows problem attribute, and PWX-02603, which identifies the problem E Field. The task ends. See message PWX-02667. Subroutine=external_module_and_entry_point. Linkage type type. When the CALLPROG function hits a problem on loading or executing, this message displays the modules and entry point (for languages that support more than one entry point per module) and the linkage type. The task ends. See the associated messages., which could be PWX-00351 or PWX-00352, for problems on loading the module, and messages PWX-02667, PWX-02668, and PWX-02676 for problems on executing the external routine.
PWX-02000 to PWX-02999
185
Function function received number argument(s). Required exactly number. The function received an unexpected number of arguments. Validation done earlier in the process when the user defines the function in the map usually prevents this problem. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function received number argument(s). Required minimum of number. The function received an unexpected number of arguments. Validation done earlier in the process when the User defines the function in the map usually prevents this problem. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function received number argument(s). Required maximum of number. The function received an unexpected number of arguments. Validation done earlier in the process when the User defines the function in the map usually prevents this problem. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function received no result argument. The function did not receive result arguments. Validation done earlier in the process when the User defines the function in the map usually prevents this problem. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function Unsupported conversion from source_field_type_number (source_field_type_description) to target_field_type_number (target_field_type_description). The conversion between the source and target field types is not supported. The task ends. Locate the problem E Field by using message PWX-02603. The function is usually COPYDATA, which can be called explicitly by COPYDATA(source,target) or by an assignment where expression is set to a source field name or constant. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task.a Function function Unexpected RC=return_code from API_routine. While processing the function, an unexpected return code was received from the subroutine. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function Unexpected change of conversion in attribute 1st=value 2nd=value. The conversion attributes have unexpectedly changed between the first and second calls.
PWX-02664
186
The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function does not support attribute of value. The specified function does not support a particular attribute value. For example, function CALLPROG does not support more than 20 arguments. Function CALLPROG only supports particular linkage types depending on which operating system it is being run on. Associated messages include PWX-02650 that shows available values for the attribute, and PWX-02603 that identifies the problem E Field. The task ends. Locate the problem E Field using the PWX-02603 message. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Linkage linkage_type received number argument(s). Required condition number. The number of arguments passed to the CALLPROG routine is invalid. CALLPROG requires at least one and no more than 20 arguments passed to the external subroutine. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function Conversion Length=length Data=<data>. Data could not be converted from one field type to another. Message PWX-02665 accompanies this message. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function Result missing attribute value. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function Result type not among supported types <field_types>. The field type of the result argument is not supported by the specified function. The supported field types are listed in the message. For example, the LengthOf function returns results in field types of NUM32 or NUM32U only, so an error occurs if the result argument is a CHAR field type. The task ends. Identify the invalid E Field by using message PWX-02603. In the PowerExchange Navigator, correct the E Field, save the data map, send it to the remote node, and run the task again. Function function Argument number type field_type_number not among supported types <supported_field_types>. The field type of the result argument is not supported by the specified function. The supported field types are listed in the message. For example, the second argument passed to
PWX-02000 to PWX-02999
187
the Split function must be the NUM32 or NUM32U type only. Using any other type results in an error. System Action: User Response: The task ends. Identify the invalid E Field by using message PWX-02603. In the PowerExchange Navigator, correct the E Field, save the data map, send it to the remote node, and run the task again. CHECK met return_code condition. A problem was flagged by the CHECK function because either the return code is in a list of bad return codes, or the return code is not on a list of good ones. The task responds according to the data map definitions in Properties > Data Checking > How do you want to handle Record Mapping Errors. Usually, this value is set to Terminate the data extract or skip row. Identify the invalid E Field by using message PWX-02603. Determine where the return code was set and react accordingly. Typically this means fixing something in an external routine called by the CALLPROG function. CHECK message message. This message displays the text passed of argument 2 to function CHECK that should help to explain the conditions of the error. Message PWX-02674 accompanies it. The system issues message PWX-02674. See the user response for message PWX-02674. Routine routine_module_and_entry_point signalled a failure code = return_code. This message is displayed if a non-zero return was returned by an external subroutine to function CALLPROG and no result argument was allocated to hold the code for the failure. The default error handling is to treat this as an error. The task responds according to the data map definitions in Properties > Data Checking > How do you want to handle Record Mapping Errors. Usually, this value is set to Terminate the data extract or skip row. Locate the problem E Field by using message PWX-02603. Determine where the return code was set and react accordingly. Typically this means fixing something in an external routine called by function CALLPROG. It is also possible to tolerate certain return codes by defining a result argument to function CALLPROG and use function CHECK to distinguish errors from values that can be ignored. Function function Argument number type field_type_number (field_type_description) only allowed as last. The function only allows arguments of this fields type as the last argument For example, function FRAGMENT only allows variable length arguments such as VARCHAR or VARBIN in the last argument. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function Offset value greater than field length or negative. The function was passed an invalid offset in relation to the size of the field it is operating on. This situation might be triggered by functions such as SETBITA or SETBITN. The task ends.
User Response:
System Action:
User Response:
188
User Response:
Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function invalid for access method access_method_number The function cannot be executed for the access method of the map. For example function GETDATABASEKEY can only be accessed for access methods such as Adabas, CAPX, CAPXRT, DL1, ESDS, HPIMAGE, IDMS, ODBA, RRDS, SEQ on AS400 so attempting to use the function for other access methods triggers the error. The task ends. Locate the problem E Field by using message PWX-02603. Either delete the E Field using the Navigator or change the access method. Then save the data map, send it to the remote node and rerun the task. Function function Internal error, key for access method access_method_number must be number not number bytes long The size of the result argument passed to function GETDATABASEKEY does not match the size of a database key of this type. For example, an IDMS database key must be a NUM32. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function Internal error, key for access method access_method_number missing No result argument was passed to function GETDATABASEKEY The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function Set set_name not found. The specified set was not found in the list of sets used by the map. The task ends. Locate the problem E Field by using message PWX-02603. Using the Navigator, check the Owner Records and Set names TAB of the record for the correct spelling of the set name. Correct the E Field, save the data map, send it to the remote node and rerun the task. Function function could not set up text constant for foreign encoded file. A text constant is being copied to a CHAR or VARCHAR field on a file in a foreign code page and the translation cannot be satisfied by a simple table-driven translation (such as IBM-037 to ISO-8859) and a ICU translator for the code pages cannot be set up. The task ends. Verify that the map properties define the correct foreign encoding. On platforms that do not support ICU, only the first 40 code pages are supported while code pages from UTF-8 onwards are not supported. See message PWX-00739 for the from and to code page. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task.
PWX-02000 to PWX-02999
189
Function function. Error translating foreign encoded CHAR/VARCHAR field before_or_after conversion. A User-defined field is involved in a conversion between a numeric field and a CHAR or VARCHAR field on a file where the code page is foreign to the platform, and a problem occurred during the code page translation process. The task ends. Verify that the data is actually in the code page specified in the map properties. Function function. Error on action. Buffer size=size. The function reported an error. The task ends. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function could not set up code page translator on foreign encoded CHAR/VARCHAR field. A User-defined field is involved in a conversion between a numeric field and a CHAR or VARCHAR field on a file where the code page is foreign to the platform, and the translation cannot be satisfied by a simple table-driven translation (such as IBM-037 to ISO-8859) and an ICU translator for the code pages cannot be set up. The task ends. Verify that the map properties define the correct foreign encoding. On platforms that do not support ICU, only the first 40 code pages are supported while code pages from UTF-8 onwards are not supported. See message PWX-00739 for the from and to code page. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Function function received an invalid value for input argument argument_number. A User-defined field received a data value for the specified argument that is out of range. The task ends. Verify that the map properties specify valid input values for the user-defined field that uses the function specified in the error message. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Parsing error on text text. An error was met when parsing the text to identify the next character and its length. The task ends. This error might be triggered if the text was not valid in the code page of the data map. On Windows and UNIX, this is UTF-8. On AS400 it is IBM-37 and on MVS it is IBM-1047. Function function argument argument_number value value is out of range. Minimum=minimum. Maximum="maximum. The value of the specified argument passed to the specified function is outside of the allowable minimum to maximum range. In the message text:
function is the function to which the invalid argument was passed. argument_number is the number of the invalid argument. value is the value of the invalid argument.
190
minimum is the minimum value of the allowable range. maximum is the maximum value of the allowable range. The task ends. Perform the following steps: 1. Correct the data map properties to specify valid input values for the user-defined field that uses the specified function. 2. In the PowerExchange Navigator, correct the E Field. 3. Save the data map. 4. Send the map to the remote node. 5. Rerun the task.
CCK Build - No search field entries in Rec=<record_name1>, for Rec=<record_name2>. A unique key field is not defined. E-field generation fails. Ensure that the Search Fields contain a unique key field. CCK Build - No matching fields found for SF=<search_field>, in Rec=<record_name1>, for Rec=<record_name2>. The Search Field is not CCK. E-field generation fails. Review your Search Fields for non CCK fields. CCK Build - Fld=<field_name> overlaps SF=<search_field>, in Rec=<record_name1>, for Rec=<record_name2>. Search Field overlaps the CCK entries. E-field generation fails. Verify your Search Fields. CCK Build - No Parent Segment Name in Rec=<record_name1>, for Rec=<record_name1>. Record does not have a Parent Segment. E-field generation fails. Verify your table/document definition. CCK Build - No Record found for Seg=<segment_name>, in Rec=<record_name1>, for Rec=<record_name1>. CCK for parent segment not found. E-field generation fails. Verify your table/document definition. CCK Build - No matching fields found for Rec=<record_name>. No matching fields found for CCK. E-field generation fails. Verify your Search Fields.
PWX-02000 to PWX-02999
191
CCK Build - MapIMSCCK Function string = fname, Maximum = Maxnum, for Rec=<record_name>. String required to build MapIMSCCK is too long. E-field generation fails. Verify your Search Fields definition. CCK Build - Parent Segment=<segment_name> references itself, in Rec=<record_name1>, for Rec=<record_name1>. Parent record point to itself. E-field generation fails. Verify your record definition. CCK Build - SF=<search_field>, in Rec=<record_name1>, for Rec=<record_name1> not completely mapped. Search field not completely mapped. E-field generation fails. Verify your Search Fields definitions. Unique search field required at all levels in hierarchy. This IMS data map is not suitable for the attempted write action across multiple levels, because it does not have a unique search field at each level in the hierarchy. The operation ends. Use a data map where unique keys are specified, or where only one level is written to at a time. Invalid hierarchy in IMS datamap. This IMS data map contains an error in the hierarchy details. The operation ends. Verify the segment name and parent segment name for each record in the data map. CECRM - Base resource_type <resource_name> not found. Unable to locate the capture registration table/document required to build the extract map. Stop creation of extract map. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - Unable to find record <record_name> to build record dependencies. Unable to find a dependent record of a table/document required to build the extract map. Stop creation of extract map. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - No resource_type entries found. The extract map being created does not contain a required resource (record/table/document). Stop creation of extract map.

192
User Response:
Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - No resource_type1 entries found for <resource_type2> resource_name. No columns/elements entries found in the table/document. Stop creation of extract map. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - Invalid table name, missing the character '_' (underscore). Invalid table name. The table name is missing the character '_' (underscore). Stop creation of extract map. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - Invalid basename, missing the character ':'. Invalid basename. The basename is missing the character ':'. Stop creation of extract map. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - Bad base name, no suffix. The base name contains two parts: recordname:field_name. The field_name is missing. The creation of the extract map ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CECRM - Building Extract Definition datamap. Unable to load capture registration crname for instance instance. Unable to load the capture registration map. Stop creation of extract map. Verify that the capture registration map was not deleted. CECRM - Start Load Session failed for location location for user name user_name. Unable to Start Load Session. Stop creation of extract map. Verify the value specified for REPNODE in the connect parameters and that a PowerExchange Listener exists on that node. CECRM - Data Map Save Failed. rc=return_code, Location=location, User Name=user_name. Unable to save data map. Stop creation of extract map. Verify the value specified for REPNODE in the connect parameters and that a PowerExchange Listener exists on that node.
PWX-02000 to PWX-02999
193
CECRM - Data Map Load Failed. Location=location, User Name=username, Schema Name=schemanama, Map Name=mapname. Unable to load data map. Stop creation of extract map. Verify the value specified for REPNODE in the connect parameters and that a PowerExchange Listener exists on that node. Incompatible column types. DB2 Column column of type type; Map Column column of type type. Column validation failure. Stop creation of extract map. Select another bulk data map for merging. Incompatible column lengths. DB2 Column column of length length; Map Column column of length length. Column validation failure. Stop creation of extract map. Select another bulk data map for merging. Warning - Length checks cannot be validated for merge of column DB2_column_name. Mapped group contains variable length columns. Length validation of VARCHAR and VARBIN fields was not performed for multiple fields within a group. No response is required. Unable to determine root segment from old-style datamap; skipping optimizations The DL/1 access routine cannot determine if a segment is the root segment when accessing a database of type HDAM, DEDB or PHDAM. Optimizations are switched off. Unqualified SSA's are used to read the database segments Create the data map again for the database root segment. DMSRV - Datamap file file_name already in use The specified data map data set is already in use by another PowerExchange Listener within the same system The PowerExchange Listener issuing this message attempts to contact the system with access to the data map file No response is required unless associated messages indicate that the PowerExchange Listener cannot meet the data map requests. DMSRV - return code return_code on datamap file enqueue Attempting to enqueue on the data map data set resulted in a no-zero return code. The data map server task for this PowerExchange Listener ends. If return code is less than 0, contact Informatica Global Customer Support. Return codes greater than 0 are as documented for MVS ENQ (SVC 56) ,RET=USE.
PWX-02731 Explanation: System Action: User Response: PWX-02732 Explanation: System Action: User Response: PWX-02733 Explanation: User Response: PWX-02760 Explanation: System Action: User Response: PWX-02800 Explanation: System Action: User Response:
194
PWX-02802 Explanation: System Action: User Response: PWX-02803 Explanation: System Action: User Response: PWX-02804 Explanation: User Response: PWX-02805 Explanation: User Response: PWX-02806 Explanation: User Response: PWX-02820 Explanation: System Action: User Response: PWX-02821 Explanation: System Action: User Response: PWX-02822 Explanation: System Action: User Response: PWX-02830 Explanation: System Action: User Response:
DMSRV - Datamap file open failed, task terminating The data map file could not be opened. The PowerExchange log contains messages messages describing the error. The data map server task for this PowerExchange Listener ends. Review log messages and correct the error. DMSRV - Datamap file open failed, task terminating The data map file could not be opened. The PowerExchange log contains messages describing the error. The data map server task for this PowerExchange Listener ends. Review log messages and correct the error. Listener is datamap server using data_set_name This PowerExchange Listener is functioning as the data map server, and handles all data map requests for this system. No response is required. Listener will use datamap server at node node (ipaddr, port portnum) This PowerExchange Listener uses the specified node as data map server. No response is required. No datamap server specified for this Listener No data map server was specified for the PowerExchange Listener, and no data map file. defined. No response is required. Datamap server Data map server nodename was not correctly specified. The program ends. Correct error and retry. Datamap subtask Y or N are the only correct parameters for DM_SUBSTASK. The program ends. Enter either Y or N for the parameter. Datamap data set resource RACF resource name for data map access was incorrectly specified. The program ends. Correct error and retry. Error if row not found Y or N are the only correct parameters for ERRROWNOTFOUND. The program ends. Enter either Y or N for the parameter.
PWX-02000 to PWX-02999
195
Field Delimiter is incorrectly specified Field Delimiter is incorrectly specified. The program ends. Correct error and retry. Record Delimiter is incorrectly specified Record Delimiter is incorrectly specified. The program ends. Correct error and retry.
PWX-03000 to PWX-03999
PWX-03000 Explanation: System Action: User Response: Access method for map schema.map does not support parameterized SQL An attempt was to execute parameterized SQL with a map access method that does not support it. The task ends. The presence of a question mark in the WHERE clause causes the system to switch to parameterized SQL mode and receives parameters on each read request. Remove the question mark if it was not intended. Parameterized SQL processing is limited to certain map access methods such as KSDS and SEQ. Error setting up code page translator for field name. While processing a foreign encoded file, an error occurred trying to initialize a translator between the foreign code page and the native code page (see message PWX-00739 for the code page numbers). The task ends. Verify that the code page defined in the map properties (or if absent the data code page in the PowerExchange configuration file) is correct. Verify that the field type is correct. Verify whether the ICU code page translation system is available on the platform where the PowerExchange Listener is running. All field types are translated into the single byte native code page for the platform except for CHAR and VARCHAR fields that are mapped to SQL types of CHAR and VARCHAR. If processing a multibyte or foreign-encoded file on a platform where the ICU code page translation facility is not available, it is not possible to map CHAR fields to DATE, or to use NUMCHAR fields. Code page translation error. Field name. Buffer length length. Type=type. While processing a foreign encoded file, an error occurred in translating between the foreign code page and the native code page during reading. The task ends. Verify that the data is in the correct code page as reported in the from code page. Unrecognized Sql code page number code_page_number. info The SQL code page number was not recognized on this platform. The task ends.
196
User Response:
Verify that there is a valid SQL code page defined in the PowerExchange configuration file CODEPAGE parameter. Error translating Sql from code page code_page_number to UTF-8. Buffer size buffer_size. info Translation of SQL to UTF-8 was unsuccessful. The task ends. Contact Informatica Global Customer Support. Data Map access method is read only Only read operations are permitted on data maps of this type. The task ends. No response is required. <Printing of field contents suppressed> Printing of bad data causing previous errors was suppressed. Review other messages produced. SELECT DISTINCT not supported for this source SQL containing select distinct was used, and is not supported for this source. The task ends with a describe error. Change the SQL, removing the distinct keyword. ORDER BY not supported for this source SQL containing order by was used, and is not supported for this source. The task ends with a describe error. Change the SQL, removing the order by instruction. SELECT DISTINCT not guaranteed with Expressions SQL containing select distinct was used, and some user defined fields (Expressions) requested. Select distinct should only be used with whole DB2 fields. SQL containing select distinct is passed to DB2, but additional columns not seen by the user might be requested that result in apparent duplicate rows being returned. Verify that select distinct is having a meaningful effect. Character in "transchar" parameter does not translate to target code page. The character specified in the named override parameter cannot be translated to the target code page. The task terminates with a "translate" error. Edit the parameter to specify a valid, translatable character. Group Source buffer is empty The group source buffer is empty. PowerExchange reads the next source record. This message indicates an internal error. Contact Informatica Global Customer Support.
PWX-03004 Explanation: System Action: User Response: PWX-03005 Explanation: System Action: User Response: PWX-03006 Explanation: User Response: PWX-03007 Explanation: System Action: User Response: PWX-03008 Explanation: System Action: User Response: PWX-03009 Explanation: System Action: User Response: PWX-03010 Explanation: System Action: User Response: PWX-03020 Explanation: System Action: User Response:
PWX-03000 to PWX-03999
197
No ADALNK environment variable defining the Adabas client library. The UNIX environment variable ADALNK is not present. This variable defines the full path and library name of the Adabas library, which is used to communicate to the Adabas nucleus program. Processing ends. Export the ADALNK environment variable pointing to the full path and library name. FDT Field length changed after code page conversion. Before conversion length. After conversion length. The field length unexpectedly changed after converting from the FDT source code page to the local code page when Adabas capture is running fully offloaded. Processing ends. Contact Informatica Global Customer Support. Error converting field field in structure type type at offset offset of the Adabas FDT. An error occurred during the code page conversion of the specified field when Adabas capture is running fully offloaded. Processing ends. Contact Informatica Global Customer Support. Error converting structure type byte byte at offset offset of the Adabas FDT. An error occurred during the code page conversion of the structure type when Adabas capture is running fully offloaded. Processing ends. Contact Informatica Global Customer Support. Wide character code page is not defined but is needed for field field. While processing captured data, PowerExchange encountered an Adabas format WIDECHAR field, but the wide-character code page is not defined. The system cannot determine the space character to use for padding. Processing ends. Define the wide-character code page in one of the following places:

System Action: User Response: PWX-03201 Explanation: System Action: User Response: PWX-03202 Explanation: System Action: User Response: PWX-03203 Explanation: System Action: User Response: PWX-03204 Explanation:
Data map field properties Data map properties for Adabas Adabas CODEPAGE statement in the DBMOVER configuration file
PWX-04000 to PWX-04999
PWX-04000 Explanation: System Action: User Response: Statement exceeds number bytes or number tokens. Remainder of statement ignored. The statement in the file being imported is either too long or has too many tokens. The import procedure flags the statement in error and continue. Verify that the file being imported conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported.
198
PIC error - field field_name, invalid first character character. The PICTURE clause for the field field_name starts with an invalid character. The import procedure flags the statement in error and continue. Verify that the PICTURE clause for the field starts with a correct character such as, X, 9, S. and so on. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. PIC error - field field_name, PIC picture_clause not allowed with COMP_n usage usage. The PICTURE clause for the field field_name is not allowed with the comp-n usage. The import procedure flags the statement in error and continue. Verify that the PICTURE clause for the field conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. PIC error - field field_name, No matching bracket or illegal char character. The PICTURE clause for the field field_name either has no matching bracket, or contains an illegal character. The import procedure flags the statement in error and continue. Verify that the PICTURE clause for the field conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. PIC error - field field_name, invalid character in picture picture_clause. The PICTURE clause for the field field_name contains an illegal character. The import procedure flags the statement in error and continue. Verify that the PICTURE clause for the field conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. PIC error - field field_name, Invalid PIC picture_clause and usage usage combination. The PICTURE clause for the field field_name is incompatible with the usage. The import procedure flags the statement in error and continue. Verify that the PICTURE clause for the field conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. PIC error - field field_name, Precision 18 for PIC picture_clause and usage usage. The PICTURE clause for the field field_name is incompatible with the usage. The import procedure flags the statement in error and continue. Verify that the PICTURE clause for the field conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. PIC error - field field_name, Invalid type token The PICTURE clause for the field field_name has an invalid token within the statement. The import procedure flags the statement in error and continue.
PWX-04000 to PWX-04999
199
User Response:
Verify that the PICTURE clause for the field conforms to the language syntax. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. The 'LIKE' field field_name has not previously been imported In a PL/I import, a field was defined as 'LIKE' another field. However, the original field does not exist. The import procedure flags the statement in error and continues processing. Verify that the spelling of the original field name is correct. If it is correct, then contact Informatica Global Customer Support, including a copy of the file being imported. Fully qualified field name 512 bytes - field_name When using the LIKE clause in a PL/I import on a group field, PowerExchange concatenates the original element field names with the new group name. If this generates a name with a length greater than 512, this message is generated. The import procedure flags the statement in error and continue. Reduce the length of field_names in the copybook so that generated names are less than 512 characters long. Variable array field_name, set to number occurrences A variable array was set to the given number of occurrences. PowerExchange has no way of determining the length of a variable so a default is given (usually 10). The system displays an informational message. Verify that the number of occurrences is valid for the data to be moved. If not, the array size can be manually changed in the PowerExchange windows interface. Field field_name has digit as first character. Changed to N. A field name begins with a number rather than a character. The system displays a warning message. PowerExchange field names cannot begin with a number. If a field name contains a number as the first character, the number is changed to 'N.' Zero length field has been ignored. PL/I allows fields to be defined as zero length. PowerExchange does not allow zero length fields, so it is ignored. The system displays an informational message. No response is required. Maximum length for character field is number. PL/I does not allow character fields with a length greater than 32765. The import procedure flags the statement in error and continue. Verify that the length of the character field is correct. If so, try splitting the field into smaller fields. Statement statement_number has number tokens, should be number. PL/I does not allow character fields with a length greater than 32765. The import procedure flags the statement in error and continue.
200
User Response:
Verify that the length of the character field is correct. If so, try splitting the field into smaller fields. An external floating point field has been imported as CHAR. PowerExchange cannot convert the NUMCHAR format of an external floating point into a float type, so it has imported it as a CHAR field. The system displays an informational message. No response is required. Field field_name has precision <precision> which is greater than maximum supported <max_supported> for usage usage. The precision clause for the field field_name is too large to be supported. The import procedure flags the statement in error and continue. Verify that the precision clause for the field conforms to the maximum supported by PowerExchange. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. Source import ended. The source import has finished. The system displays an informational message. No response is required. number records imported. The displayed number of records have been created by the import procedure. The system displays an informational message. No response is required. number errors encountered. The displayed number of errors have been reported by the import procedure. The system displays a warning message. Review each error and follow instructions for each error message. Bad level number at position column_number. The import procedure is looking for a level number as the first token of a statement, but was unable to find one. The import procedure flags the statement in error and continue. Verify that the file being imported conforms to the language syntax. Also check the start column setting on the PowerExchange windows interface to ensure that any extraneous characters at the start of a statement are being ignored. If correct, then contact Informatica Global Customer Support, including a copy of the file being imported. Redefinition field_name skipped by request. The redefinition was not selected by the user. The system displays an informational message. No response is required.
PWX-04000 to PWX-04999
201
number fields imported. The number of fields displayed have been created by the import procedure. The system displays an informational message. No response is required. number tables created. The number of tables displayed have been created by the import procedure. The system displays an informational message. No response is required. More than number levels of nesting. Field field_name ignored. PowerExchange has a maximum number of level nesting, currently 15. Any fields that have been nested more deeply than this are ignored. The import procedure flags the statement in error and continue. Try rationalizing the number of levels in the copybook. If this can't be done, contact Informatica Global Customer Support with the copybook information for further advice. Definition field_name selected. The field_name displayed was selected from the redefinition list. The system displays an informational message. No response is required. Array size for field field_name is missing or not in range 1 - number. The array size was not defined after an OCCURS clause or it exceeds PowerExchange's maximum allowable arraysize (currently 4096). The import procedure flags the statement in error and continue. Verify that the OCCURS value is correctly shown in the copybook and is within PowerExchange's limits. If it is, then contact Informatica Global Customer Support with the copybook information for further advice. No variable array control variable specified for field field_name. The field name displayed was defined as an 'OCCURS DEPENDING ON' array, but no control variable was specified. The import procedure flags the statement in error and continue. Verify that a control variable for the field was entered in the copybook. If it has, then contact Informatica Global Customer Support with the copybook information for further advice. number records skipped. This message shows the number of duplicated records that were skipped by the import procedure. The system displays an informational message. No response is required.
202
number duplicate records overwritten. This message shows the number of duplicated records that were overwritten by the import procedure. The system displays an informational message. No response is required. number duplicate records automatically renamed. This message shows the number of duplicated records that were renamed by the import procedure. The system displays an informational message. No response is required. number fields skipped. This message shows the number of duplicated fields that were skipped by the import procedure. The system displays an informational message. No response is required. number duplicate fields overwritten. This message shows the number of duplicated fields that were overwritten by the import procedure. The system displays an informational message. No response is required. number duplicate fields automatically renamed. This message shows the number of duplicated fields that were renamed by the import procedure. The system displays an informational message. No response is required. number tables skipped. This message shows the number of duplicated tables that were skipped by the import procedure. The system displays an informational message. No response is required. number duplicate tables overwritten. This message shows the number of duplicated tables that were overwritten by the import procedure. The system displays an informational message. No response is required. number duplicate tables automatically renamed. This message shows the number of duplicated tables that were renamed by the import procedure. The system displays an informational message.
PWX-04000 to PWX-04999 203
No response is required. Root segment not found in source. Hierarchical tables not created. A root segment was not found on a DBD import file. Because of this no hierarchical table structure was able to be produced. The system displays a warning message. Verify the DBD import file for a root segment. If this is missing or in the incorrect format, then correct. If it seems to be correct, then contact Informatica Global Customer Support with the copybook information for further advice. No record for segment segment_name was found in the data map. Generated record recordname for While generating the hierarchical structure no record was found for the specified segment. A dummy record was generated for consistency. The system displays a warning message. Verify the DBD import file for record/segment consistency. If it seems to be correct, then contact Informatica Global Customer Support with the copybook information for further advice. number records generated to satisfy hierarchy. A number of records have been generated to satisfy the hierarchy. Not used any more. No response is required. Field field_name does not occupy space on the segment and has been ignored. The field is not used by PowerExchange and so was ignored. This mainly occurs for secondary index fields and concatenated key markers. The system displays an informational message. No response is required. number tables refreshed from imported records. Tables have been refreshed from data on the imported records. The system displays an informational message. No response is required. number IMS Concatenated key warnings. A number of warnings have been generated by the IMS concatenated key process. The system displays a warning message. Review the warnings given and take the appropriate action as advised by each individual message. Import stopped after first DBD. Any more DBDs will be ignored. More than one DBD appears on the DBD import file. PowerExchange processes only one DBD at a time. The system displays a warning message. If more than one DBD is required, then split the import file so that only one DBD appears on each import file.
204
number duplicate records appended to. This message shows the number of duplicated records that were appended to by the import procedure. The system displays an informational message. No response is required. IDMS schema has not been validated The IDMS schema being imported was not validated and might contain invalid data. Produce an message and abort import. Ensure that a properly valid schema is being used in the IDMS import procedure. Invalid call type (should be 0 (initial), 1 (process a line), 2 (final)) Internal error. The request fails. Contact Informatica Global Customer Support for support. Invalid or missing level number Source input line has invalid level number. The request fails. Correct the input and retry. Invalid or missing field length The Adabas ECCR is ending. The ECCR ends. Examine the ECCR output for diagnostic information. Correct the error if possible. Then, start the ECCR again. Missing '=' (equal sign) Invalid syntax (such as FNDEF or SUPDE missing the '='). The request fails. Correct the input and retry. Invalid or missing start position Invalid syntax in SUPDE/SUBDE specification. The request fails. Correct the input and retry. Invalid or missing end position Invalid syntax in SUPDE/SUBDE specification. The request fails. Correct the input and retry. More than 20 parents for super-field/descriptor Invalid specification of SUPDE.
PWX-04000 to PWX-04999
205
The request fails. Correct the input and retry. Only one parent for super-field/descriptor Invalid specification of SUPDE. The request fails. Correct the input and retry. Invalid field name Source input line contains invalid field name. The request fails. Correct the input and retry. Reserved field name used Source input line contains field name E0->E9. The request fails. Correct the input and retry. Invalid field format specification Source input line contains invalid format (should be A,P,B and so on). The request fails. Correct the input and retry. Missing keyword, record ignored Source input line is invalid, no recognized keyword (FNDEF and so on). The request fails. Correct the input and retry. Missing '(' (left parenthesis) Source input line, invalid specification of PHONDE parameter. The request fails. Correct the input and retry. Invalid option specified Source input - wrong specification of option (MU,PE,DE,LA and so on). The request fails. Correct the input and retry. Invalid occurs value Source input - invalid value for PE/MU occurs item. The request fails. Correct the input and retry.
206
Redefines option must be 'R' or blank Source input error in Redefines Option - could be internal error. The request fails. If redefines field is correct, contact Informatica Global Customer Support otherwise correct the input and retry. Too many parameters entered Too many parameters or commas in source line. The request fails. remove redundant parameters or commas in source line and retry. Invalid field type Source input line field type is incorrect. Correct values are A, P, and so on. The request fails. Correct the input and retry. Invalid Natural format Source input line Natural format is not one of D,T,I or L. The request fails. Correct the input and retry. Invalid scale<scale> Source input line scale is invalid, probably too large. The request fails. Correct the input and retry. Invalid or missing array count Probable internal error. The request fails. Contact Informatica Global Customer Support for support. Invalid Super Descriptor list Probable internal error. The request fails. Contact Informatica Global Customer Support for support Invalid Unique indicator Probable internal error. The request fails. Contact Informatica Global Customer Support for support. Invalid scale in relation to field length: scale=scale length=length Source input line scale is invalid, probably too large. The request fails.
PWX-04000 to PWX-04999
207
User Response: PWX-04251 Explanation: System Action: User Response: PWX-04252 Explanation: System Action: User Response: PWX-04301 Explanation: System Action: User Response: PWX-04302 Explanation: System Action: User Response: PWX-04303 Explanation: System Action: User Response: PWX-04350 Explanation:
Correct the input and retry. DDM ddm not found in FDIC(dbid,fileno) The FDIC file specified does not contain the DDM. The request fails. Correct the FDIC values or DDM name and retry. Requested FDIC(dbid,fileno) does not appear to exist The FDIC file specified does not exist or is locked. The request fails. Correct the FDIC values and retry. File file not found in FDIC(dbid,fileno) The FDIC file specified does not contain the file/view. The request fails. Correct the FDIC values or file/view name and retry. Requested FDIC(dbid,fileno) does not appear to exist The FDIC file specified does not exist or is locked. The request fails. Correct the FDIC values and retry. Invalid function: function The function passed to the access method is invalid. Request failed. Change the function. Valid ones are: GETDDM, GETPREDICT, GETFDT. ERROR - PLOG Out of Sequence. The PLOG file being added to the PCAT control file was created prior to the one that was last added. This indicates that two or more PLOG copy jobs have run in the wrong sequence, or that a database restore was run that has invalidated the PLOGS created after the point in time the restore has reset the database to. Program ends with return code 8. Contact computer operations and/or the DBA to establish the cause of the error. Use the 'D' delete function of the DTLCCADW utility to remove PCAT entries as necessary (the 'R' report function might facilitate the investigation). Add the PLOGs to the PCAT again in their correct sequence using the 'A' append function of DTLCCADW. Plog record seqno dsn=dsname being deleted. Informational message only. No response is required. *** WARNING - Record seqno just deleted was the latest added - use L function to reset Indicates that the user has deleted the PCAT entry that was the highest numbered (for example, latest added) on the PCAT file. The overall control record therefore MUST be reset to the new highest sequence number.
PWX-04351 Explanation: User Response: PWX-04352 Explanation:
208
User Response:
Reset the PCAT control record either manually or by running the 'L' (reset to Latest) function of DTLCCADW. ERROR - Record already exists with seqno seqno An attempt was to use the 'I' insert function to add a record, but a record already exists with that sequence number. Program ends with return code 8. Run the 'R' report function of DTLCCADW to check the record already on the file. Either delete this record and rerun the insert, or use a different sequence number. ERROR - Attempt to insert after highest existing key sequence An attempt was to use the 'I' insert function to add a record, but the sequence number is higher than the last entry added. Program ends with return code 8. Run the 'R' report function of DTLCCADW to check the sequence numbers. The 'A' append function must be used when adding a record to the end of the file. ERROR - EOF reached or some other error encountered, rc=return_code While attempting to read the PCAT file an invalid condition was encountered, probably no '999999999' control record found. Program ends with return code 8. Run the 'R' report function of DTLCCADW to check the file status, Correct the error and run the request again. Control record latest key before update is seqno. This message indicates what the highest control file sequence number is set to. No response is required. ERROR - in updating Control record - rc=return_code While attempting to update an entry on the PCAT file, an invalid condition was encountered. Program ends with return code 8. Run the 'R' report function of DTLCCADW to check the file status, Correct the error and run the request again. Control record latest key now reset to seqno. This message confirms reset of control record. No response is required. ERROR - in processing PLOG, rc=return_code While attempting to read an entry on the PCAT file, an invalid condition was encountered. The internal return code is shown. Program ends with return code 8. Review all output for further information. Run the 'R' report function of DTLCCADW to check the file status, Correct the error and run the request again.
PWX-04000 to PWX-04999
209
ERROR - in processing VSAM control file, rc=return_code While attempting to access the VSAM PCAT file, an invalid condition was encountered. The internal return code is shown. Program ends with return code 8. Review all output for further information. Run the 'R' report function of DTLCCADW to check the file status, Correct the error and run the request again. ERROR - PLOG dsn dsname reason. While attempting to extract information from a PLOG, an invalid condition was encountered. The data set name being accessed and a possible cause is built into the error message. Program ends with a non-zero return code. Review all output for further information and check the output from the PLOG copy job that created the PLOG in question. Take whatever action is appropriate to the error. If in doubt, contact Informatica Global Customer Support. ERROR - JCL file problem, rc=return_code. While attempting to access the file containing the JCL, an invalid condition was encountered. The internal return code is shown. Program ends with a non-zero return code. Review all output for further information. Correct any error and rerun. If in doubt, contact Informatica Global Customer Support. ERROR - INTRDR file problem, rc=return_code. While attempting to write JCL to the internal reader, an invalid condition was encountered. The internal return code is shown. Program ends with a non-zero return code. Review all output for further information. Correct any error and rerun. If in doubt, contact Informatica Global Customer Support. ERROR - in delete VSAM record, rc=return_code While attempting to delete an entry on the PCAT file, an invalid condition was encountered. The internal return code is shown. Program ends with return code 8. Review all output for further information. Run the 'R' report function of DTLCCADW to check the file status, Correct the error and run the request again. ERROR - wrong number of parameters. Correct and resubmit. For the function code specified in the EXEC statement, the wrong number of parameters was entered. Program ends with return code 8. Verify the parameters on the EXEC statement. Correct the error. Then, run the request again. ERROR - in ADASEL job submission - probably invalid key. An error was encountered while attempting to submit JCL to the internal reader for a given PCAT file sequence number.
210
Program ends with return code 8. Review the output for any further diagnostic messages. Review the PCAT entry for the given sequence number. Correct any error and rerun. If in doubt, contact Informatica Global Customer Support. ERROR - in appending PLOG control record, dsn=dsn. An error was encountered using the 'A' append or 'P' populate function of DTLCCADW. Program ends with return code 8. Review the output for any further diagnostic messages. Run the 'R' report function of DTLCCADW to check the file status, Correct the error and run the request again. If in doubt, contact Informatica Global Customer Support. ERROR - in deleting PLOG record - probably invalid key. An error was encountered while attempting to delete an entry for a given PCAT file sequence number. Program ends with return code 8. Review the output for any further diagnostic messages. Review the PCAT entry for the given sequence number. Correct any error and rerun. ERROR - in insert PLOG routine. An error was encountered while attempting to insert an entry for a given PCAT file sequence number. Program ends with return code 8. Review the output for any further diagnostic messages. Review the PCAT entry for the given sequence number. Correct any error and rerun. ERROR - in reset latest sequence number routine. An error was encountered while attempting to use the PCAT 'reset sequence number' function of DTLCCADW. Program ends with return code 8. Review the output for any further diagnostic messages. Run the 'R' report function of DTLCCADW to check the file status, correct any error and rerun. ERROR - error in opening file of PLOG DSNAMES - check jcl. An error was encountered while attempting to use the 'P' populate function of DTLCCADW. Probable JCL error. Program ends with return code 8. Review the output for any further diagnostic messages. Run the 'R' report function of DTLCCADW to check the file status, correct any error and rerun. End of PLOG file population action. Informational message only. Run the 'R' report function of DTLCCADW to check the file status. ERROR - in read PLOG file list file, rc=return_code. An error was encountered while attempting to use the 'P' populate function of DTLCCADW. Probable JCL error.
PWX-04000 to PWX-04999
211
Program ends with return code 8. Review the output for any further diagnostic messages. Run the 'R' report function of DTLCCADW to check the file status, correct any error and rerun. ERROR - Parm 1 must be S,A,D,I,P,E,L or R - correct & resubmit The first parameter must be S,A,D,I,P,E,L or R. Program ends with return code 8. Verify the parameter statement in JCL. Correct the error. Then, run the request again. PLOG dsname dsname has been added with key sequence seqno. Informational message only. No response is required. Function function has ended successfully. Informational message only. No response is required. Parameter IGNORENOCHANGEUPDATES invalid. Must be Y or N The value passed to the specified parameter is invalid. The Adabas log capture job ends. Enter either Y or N for the parameter. Error error code reading captured data file file name. While reading the specified Partial or Full Condense file, an error occurred. A previous message that includes the same error number provides more precise information about the cause of the error. The request fails. Locate the more precise error message and respond to that. Error error code opening captured data file file name. An error occurred while trying to open the specified Partial or Full Condense file. This might occur if the file no longer exists, or if the job has insufficient authority to read the file. The request fails. Locate the specified file. If the file was deleted, then action must be taken to synchronize the CDCT file with the files that actually exist. For example, one method is to rematerialize and cold start Condensing that clears out all information for this Instance from the CDCT, checkpoint and deletes all Condensed files for the external capture mask (MVS) or Condense library (AS400). Another method is to locate a checkpoint file that defines an appropriate time to restart, then delete other checkpoint files that are more recent. On running the Condense, the system synchronizes the CDCT file with the DCT entries in the checkpoint file, which causes problem records to be deleted from the CDCT, and processing resumes from the point defined by the sequence and restart tokens. Considerable care must be taken contact Informatica Global Customer Support. If the file does exist, then it is useful to attempt to read it through a PowerExchange Listener such as from a Navigator or DBMOVE job where the source is defined by a data
PWX-04374 Explanation: System Action: User Response: PWX-04375 Explanation: User Response: PWX-04376 Explanation: User Response: PWX-04377 Explanation: System Action: User Response: PWX-04500 Explanation:
212
map under the NRDB access method. If the problem cannot be determined, contact Informatica Global Customer Support. PWX-04502 Explanation: Error error code opening condensed data captured table CDCT file name. The task was unable to open the CDCT file. On MVS, file name shows the MVS DDNAME DTLCACDC and on AS400s shows the data library and file name. On MVS, the problem might occur if DDNAME DTLCACDC was not present (or allocated to DUMMY) in the PowerExchange Listener JCL or in the DBMOVE JCL if the from location is LOCAL. On AS400s, either the specified file might not exist or it cannot be opened because of access permissions. The request fails. Locate the CDCT file. If it does not exist, create a new CDCT file and initialize it as described in the adaptor documentation so that it has the correct record length, key length and trailer record. If the CDCT does exist, create an NRDB map and do a Row Test on it through the Navigator. If the problem cannot be determined, contact Informatica Global Customer Support. Error error code reading condensed data captured table CDCT file name. An error occurred while reading the CDCT file that happens during initialization of the CAPX access method, to determine that Condensed file to process according to the Instance and sequence token criteria. The request fails. Verify that the CDCT file has the appropriate record length, key length and a trailer record. If the problem cannot be determined, contact Informatica Global Customer Support. Error error code closing Condensed Data Captured Table CDCT file name. An error occurred while closing the CDCT file. The request fails. Contact Informatica Global Customer Support Error error code accessing Condensed Data Captured Table CDCT file name. An error occurred while doing a point and read on the CDCT file. An accompanying message provides more precise information. The request fails. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Error return_code1.return_code2.return_code3 opening capture data extract process table file_name/action. Errors were encountered opening the stated file for extract progress. On some platforms this might relate to automatic file creation. This can be caused by a partial change to the configuration. The request fails. Review associated messages, establish cause, fix file and retry. Error return_code1.return_code2.return_code3 reading capture data extract process table file_name. A read of extract process failed for the stated file.
PWX-04000 to PWX-04999
213
System Action: User Response: PWX-04509 Explanation: System Action: User Response: PWX-04510 Explanation: System Action: User Response: PWX-04511 Explanation: System Action: User Response: PWX-04512 Explanation: User Response: PWX-04513 Explanation: System Action: User Response: PWX-04515 Explanation: System Action: User Response: PWX-04519 Explanation: System Action: User Response:
The request fails. Review associated messages, establish cause, fix file and retry. Error closing rc capture data extract process table file_name. A problem was encountered closing the capture data extract process file. This might be a secondary problem give first problem priority to see if this is related. The request fails. Review associated messages, establish cause, fix file and retry. Error accessing capture data extract process table file_name code return_code1/return_code2/return_code3. A request failed to find extract process for the stated file. The request fails. Review associated messages, establish cause, fix file and retry. Missing capture data extract process table on file file_name code return_code1/return_code2/return_code3. A physical extension record is missing that is part of a logical progress record. The request fails. Contact Informatica Global Customer Support with associated errors. Opening captured file file_name. Audit trail of files used in CAPX extract for PowerExchange Change. Audit trail if needed. Error return_code1.return_code2.return_code3 writing capture data extract process table file_name. Failure writing an extract progress record. The request fails. Review associated messages, establish cause, fix file and retry. Unrecognized capture data extract start type starttype. A request for an extract of capture data was made with an unrecognized start type parameter. The request fails. Review request, establish cause, fix and retry. Error error code reading Condensed Data Capture Files. An error occurred while loading information about files to process from the CDCT file during the initialization of a CAPX extraction. The task ends. See the associated messages PWX-04502, PWX-04503, PWX-04504, and PWX-04506.
214
There is no condensed data to extract for instance instance 1st registration tag registration_tag. No Condense files exist in the CDCT that satisfy the criteria of sequence tokens, Instance and list of registration tags. The message displays the instance and first registration tag. (There might be several registration tags if a command list is being executed.) This message appears only on the PowerExchange Listener and not on the client. Processing ends successfully, but no data is extracted. Verify that data is present for extracting. Maybe the Condense job has not run recently. Row for Every record option only allowed for Data Capture. A Row for every record was requested but the request is not of the data capture extract type. The request fails. If configuration and request are new investigate, correct and retry otherwise report to Informatica Global Customer Support with associated errors. No application for Data Capture. The mandatory application parameter was not provided to a CAPX or CAPXRT extraction. The request fails. Ensure that the application name is provided. In a command set, the application name is entered through From parameter DBN2. On a Row Test screen, the application name is entered in an entry field called application_name. Invalid combination of condense files or types detected. This error occurs when you attempt to extract change data for:
Capture registrations with different condense types (none, partial, or full) A single capture registration with changes in both full and partial condense files System Action: User Response: The request fails. If you are using group source to extract change data from condense files, separate the capture registrations so that only a single condense type is included in the extraction. Include capture registrations with a condense type of Full in one extraction, a condense type of None in another extraction, and a condense type of Partial in a different extraction. Run these extractions separately. If a condense type for a specific capture registration was changed between Full and Partial, then additional action is required. You must either recondense the data into a single type of condense file or you must change the extraction start point to skip over the condense files of the previous condense type. Before altering the capture registration to change the condense type, extract all data. If the issue cannot be resolved, contact Informatica Global Customer Support. PWX-04528 Explanation: Error Progress data has changed submessage. Data Capture. The record being updated does not match the record for which the update was requested. This might imply an update in another process. The associated message assists in diagnosing the problem. These are the possible sub messages:

outside extract control control field corrupted control field added

PWX-04000 to PWX-04999 215
control field out of step control field delete out of step The request fails. It is possible you can identify the clash of requests, if so attempt them separately. However should this not be the case contact Informatica Global Customer Support with this and associated messages. Error can not restart registration extractname with <start_time>. Data Capture.
This message was issued for one of the following reasons: 1. A restart was attempted for the specified extract against the extract started at the described time, but the extract was different. This might be a result of sharing an application between multiple extracts, which means the wrong extract was run for the restart. 2. A request was made for the specified extract before the extract started at the described time completed. This happens because an application was shared between multiple extracts and the extract requests have not been single streamed. The PowerExchange log describes this symptom more clearly, to identify overlaps look from <start_time> forward through the failure and check where each task starts and ends.
System Action: User Response: PWX-04539 Explanation: System Action: User Response: PWX-04540 Explanation: System Action: User Response: PWX-04541 Explanation:
The request fails. Review associated messages, establish cause, fix and retry. Error accessing capture data application index file_name code return_code1/return_code2/return_code3. A request failed to find an application index for the stated file. The request fails. Review associated messages, establish cause, fix file and retry. Error return_code1.return_code2.return_code3 reading capture data application index file_name. A read of an application index failed for the stated file. The request fails. Review associated messages, establish cause, fix file and retry. Error Application Index data reason. Data Capture. The application cannot be used for the reasons:

Utility update incomplete. Utility in progress or failed has changed outside extract control. Concurrent processes file controls corrupted. Internal fields overwritten file controls inconsistent. See message PWX-04559. Internal fields overwritten sequence failure on application index. See message PWX-04559. Old sequence error on application index. See message PWX-04559. System Action: User Response: The request fails. For the last three reasons, concurrent requests caused conflicting updates. A file was corrupted. Investigate previous failures as the cause of the file corruption. Restore the file as necessary. Retry request. Contact Informatica Global Customer Support with associated errors and logs in the event of continuing problems.
216
Error return_code1.return_code2.return_code3 writing capture data extract application index file_name. Failure writing an application index record. The request fails. Review associated messages, establish cause, fix file and retry. Userid <user_ID> does not have <required> access to <resource>, return code<return_code>. Security limit exceeded for user. The request fails. Correct the request or user security. Then, try the request again. Capture Extract Authorization Warning : Userid <user_ID> return code <return_code>. The attempt to sign the user on failed with the return code. The request fails. Correct the request or user security. Then, try the request again. Capture Extract source Reset to extractstart No CDE progress found. This message was issued for one of the following reasons: 1. No extract was found relating to the start point set in the navigator. This might be a result of sharing an application between multiple extracts, which means the wrong extract was run after the reset. 2. XTYPE=RS used to restart.
The request fails. Correct the request. Then, try the request again. Capture Extract Before Images not possible for file name. Before images requested but only after images are available on the specified condensed file DBMOVE parameter IMTYPE cannot be set to BA or TU where there are no after images stored in the Condense files. When the Condensing was done, the job used parameter CAPT_IMAGE set to AI (after images) instead of BA (before and after images). The request fails. Either run the CAPX extract with parameter IMTYPE=AI or rematerialize and run the Condense job with CAPT_IMAGE=BA Unrecognized Capture Extract image type requestedtype. An image type other than BA/AI/TP was found in the request. The request fails. Correct the request. Then, try the request again. Error Capture extract started without connection dbcb. The request for CAPX(RT) is not correctly structured. The request fails. If configuration and request are new investigate, correct and retry otherwise report to Informatica Global Customer Support with associated errors.
PWX-04000 to PWX-04999
217
Clash on attribute. First command set value. Other command set value. In a command list used for a CAPX or CAPXRT move, there is inconsistency between the first and a subsequent command set on an attribute such as:

Instance (where extract is sourced) Image type (defined by parameter IMTYPE such as AI,BA,TU) Source type (numeric database type such as 1=DB2, 2=IMS and so on) Extract type (defined by parameter XTYPE, such as RS=restart, SL=since last) System Action: User Response: PWX-04552 Explanation: System Action: User Response: PWX-04553 Explanation: The request fails. Correct the command sets so that they have consistent attributes, then retry. Error Group DBCB found processedsources members expected requestedsources. An error was encountered identifying sources. The request fails. Contact Informatica Global Customer Support with associated errors. Error restart tokens required/not_allowed for application application_name. Application supplied restart tokens were present on the request for the application that did not allow them, or are missing when required. This would catch an application change to application restart control as there is no way to pass this control it is not allowed. The request fails. Correct the request or start a new application. Error Start point reset through Navigator restart tokens expected. After a reset current start point in the Navigator, tokens have been supplied by the application. Which restart point was intended? The request fails. Correct the request or start a new application. Error could not find registration tag registrationtag in application <application_name>. A registration tag was not found, after initial validation. The request fails. Contact Informatica Global Customer Support with associated errors. Error progress data expected requested unique registration tags found present in application application. An error was encountered with sources after initialization. The request fails. Contact Informatica Global Customer Support with associated errors. Application Index data for <application_name> not found. The application was not found. For an error, the request fails. For a warning, this message might be relevant to an associated failure. For extracts check the PowerExchange log to see if this message is related (time). Find out what the application should have been and retry the request.
System Action: User Response: PWX-04554 Explanation: System Action: User Response: PWX-04556 Explanation: System Action: User Response: PWX-04557 Explanation: System Action: User Response: PWX-04558 Explanation: System Action: User Response:
218
Error Application Index data for <application_name> could not be built. A problem was encountered rebuilding an application record that might have been split over physical records. The request fails. Investigate how this might have been corrupted by previous failures. Restore the file as necessary. Retry request. Contact Informatica Global Customer Support with associated errors and logs in the event of continuing problems. Error accessing capture data progress extensions file_name code return_code1/return_code2/return_code3. A problem was encountered rebuilding a progress record, that was split over physical records. The request fails. Investigate how this might have been corrupted by previous failures. Restore the file as necessary. Retry request. Contact Informatica Global Customer Support with associated errors and logs in the event of continuing problems. Error progress data could not be rebuilt File <file_name> Application <application_name> started <start_time> A problem was encountered rebuilding a progress record, which might have been split over physical records. The request fails. Investigate how this might have been corrupted by previous failures. Restore the file as necessary. Retry request. Contact Informatica Global Customer Support with associated errors and logs in the event of continuing problems. Error tokens found on application index <application_name> none expected. Restart tokens were present on the application, which due to the request are not expected. This would catch an application change to application restart control as there is no way to pass this control it is not allowed. The request fails. Correct the request or start a new application. Error action <action_type> for registration <registration> application application still requested. A token added by the DTLUAPPL token utility cannot be processed because it is still part of the request. It is considered unlikely that a token would be dropped manually without intending to drop it. The request fails. Remove the token to the request and retry. Error action <action_type> for registration <registration> application <application> cannot be processed. A token added by the DTLUAPPL token utility cannot be processed because it is not part of the request. It is considered unlikely that a token would be added manually without intending to use it. The request fails.
System Action:
PWX-04000 to PWX-04999
219
User Response:
Add the token to the request and retry or create a temporary/new application to get around the timing issue. Regn tag registration_tag sequence hexprint PowerExchange Logger hexprint This message provides information about the tokens that indicate where the extraction started. A hexprint value of double zero (00) shows no data has ever been extracted and the token utility was not run for the application. This information is for audit purposes. Capture Extract RC=return_code from API_routine error_information An error occurred in the specified routine. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Re-extracting Application application from extract of timestamp. The extract that started at the stated time for the application is being restarted. This information is for audit purposes. Overridden for description extract original becomes internal for recording. The extract was over ridden and has a new extract name for progress recording. This means it cannot be confused with a normal run of the extract. This information is for audit purposes. Error Registration registratiuon_name condense type is current_condense_type, needs to be set for this request. The condense setting in the extraction map does not match the specified condense type in the associated capture registration. The extraction request fails. Perform the following actions: 3. Correct the condense type in the capture registration. Valid condense types are Full and Partial. 4. Update the extraction map to associate it with the new version of the capture registration. 5. Retry the extraction request.
PWX-04567 Explanation: User Response: PWX-04568 Explanation: User Response: PWX-04570 Explanation: System Action: User Response:
Error Regn tag registration_tag start sequence sequence_token is past condense limit sequence_token The specified start position is more recent than the most recent file on the CDCT for this registration tag. Consequently there is no data to be extracted. This message is rarely seen because this condition is a warning that does not stop the successful termination of the extraction and then warning messages are discarded. The message might be seen in conjunction with error messages, which cause the extraction to complete unsuccessfully. Normally, the start position for one CAPX extract is the same as the end position of the previous run. The task continues with no data being extracted. Verify that the start sequence token is correct. If the issue cannot be resolved, contact Informatica Global Customer Support
220
Error Timeout value not in range: seconds. Timeout too big. The request fails. Resolve and retry. Error tokentype token size current is different to startsize (the size first used for this extract) Error token size inconsistent for token type. Accompanied by message PWX-04574 for each token. Collection is ended and the request fails. Resolve and retry. size - <hexprint> The token being reported. Processing continues. Use with the associated error to establish why this token was sent to the application. Invalid Journal value: journal The Journal Library Name should be between 1 and 10 alphabetic characters in length. The Journal file name should be between 1 and 10 alphabetic characters in length. The values should be separated by a forward slash (/). The request fails. Resolve and retry. Invalid Library/file_name value: libfile_name The Library Name should be between 1 and 10 alphabetic characters in length. The file name should be between 1 and 10 alphabetic characters in length. The values should be separated by a forward slash (/). The request fails. Resolve and retry. Error event table required/not_allowed for application application_name. An event table eventtb was present on the request for the application, which did not allow them, or was missing when required. This would catch a change to application end control, which is not allowed. The request fails. Correct the request or start a new application. Application_Name: Capture_Registration: Ins= Num_Inserts Upd=Num_Updated Del=Num_Deleted Cmt=Num_Commits Total=Total_Num Informational message for CAPX/CAPXRT/EMR sources, giving a breakdown of records read from the source for each Capture Registration No response is required. extraction_map Volume_Set
System Action: User Response: PWX-04578 Explanation: User Response: PWX-04579 Explanation:
Table displays all Extraction Maps and the corresponding Volume Set names. A single session can only process Extraction Maps for a single HP3000 Volume Set.
PWX-04000 to PWX-04999 221
System Action: User Response: PWX-04580 Explanation: System Action: User Response: PWX-04581 Explanation: System Action: User Response: PWX-04582 Explanation: System Action: User Response: PWX-04583 Explanation: System Action: User Response: PWX-04584 Explanation: User Response: PWX-04585 Explanation: System Action: User Response: PWX-04586 Explanation: System Action: User Response: PWX-04587 Explanation: User Response:
Extraction fails. Resolve and retry. Extraction references log data from different Volume Sets. Data Extraction references Extraction Maps that include log data on more than one HP3000 Volume Set. A single extraction can only reference data from a single Volume Set. Extraction fails. Resolve and retry. Error Finding AS4J connection connection. The CAPI connections did not find a type AS4J connection. Extraction fails. Resolve and retry. Error Rc return_code from receiver list lookup. The lookup of the receivers associated with the journal for CDC extract failed with the given code. The request fails. Review associated messages, establish cause, fix and retry. Error converting token_occurrence to new release with rc return_code. A return code was received converting the stated occurrence of token to the new release. The request fails. Review associated messages, establish cause, fix and retry. extract_information Information describing the extract for audit and diagnostic purposes. Use with associated messages, for investigation or diagnosis. extraction_map Oracle_Id
Table displays all Extraction Maps and the corresponding Oracle connection ids. A single session can only process Extraction Maps for a single Oracle instance. Extraction fails. Resolve and retry. Extraction references log data from different Oracle instances. Data Extraction references Extraction Maps that include log data on more than one Oracle connection ID. A single extraction can only reference data from a single Oracle instance. Extraction fails. Resolve and retry. application_name: Records read=number_of_records_read Process message for records read. No response is required.
222
PWX-04588 Explanation: User Response: PWX-04589 Explanation: System Action: User Response: PWX-04590 Explanation: User Response: PWX-04591 Explanation: System Action: User Response: PWX-04592 Explanation: System Action: User Response: PWX-04593 Explanation:
application_name: Total records read=number_of_records_read Final process message for records read. No response is required. Unable to add Tokens. Unable to add sequence and restart tokens to CAPX temporary area. Extraction fails. Resolve and retry. Final Sequence read sequence The final sequence read while retrieving change data. Sequence of double zero shows no data has ever been extracted and the token utility was not run for the application. No response is required. Error accessing capture data Cross Reference index file_name code return_code1/return_code2/return_code3. A request failed to find an Cross Reference index for the stated file. The request fails. Review associated messages, establish cause, fix file and retry. Error return_code1.return_code2.return_code3 reading capture data Cross Reference index file_name. A read of a Cross Reference index failed for the stated file. The request fails. Review associated messages, establish cause, fix file and retry. Error Cross Reference Index data reason. Data Capture. The Cross Reference cannot be used for the reasons: Utility update incomplete - utility in progress or failed has changed outside extract control - concurrent processes file controls corrupted. The request fails. Concurrent requests have caused conflicting updates. Restore the file as necessary. Retry request. Contact Informatica Global Customer Support with associated errors and logs in the event of continuing problems. Error return_code1.return_code2.return_code3 writing capture data extract cross reference index file_name. Failure writing an cross reference index record. The request fails. Review associated messages, establish cause, fix file and retry. Error Cross Reference Index data for <application> could not be found. A problem was encountered reading a cross reference record. The request fails.
PWX-04000 to PWX-04999
223
User Response:
Investigate how this might have been corrupted by previous failures. Restore the file as necessary. Retry request. Contact Informatica Global Customer Support with associated errors and logs in the event of continuing problems. <change_to> extraction for <resource> A change is being reported to extraction for the resource. Possible changes:
Warning unexpected - Additional extracted resource not notified by DTLUAPPL token utility. New - Additional extracted resource. Warning ended - Ended extracting resource not notified by DTLUAPPL token utility. Ended - Ended extracting resource. User Response: PWX-04597 Explanation: System Action: User Response: PWX-04598 Explanation: System Action: User Response: PWX-04599 Explanation: System Action: User Response: PWX-04600 Explanation: System Action: User Response: PWX-04601 Explanation: System Action: User Response: PWX-04602 Explanation: System Action: For warnings it might be worth investigating or looking at procedures. Error hashing extract names size Calc_size is greater than full_size less prefix (sizeinf). Internal error. The request fails. Contact Informatica Global Customer Support. Error checking extract request against extract history rc application extract_start. The matching process failed for with the stated return code while matching the given application and start timestamp. The request fails. See the associated messages. Error return_code1.return_code2.return_code3 writing capture data extract process table file_name.application. The cross-reference process failed for with the stated return code while writing the given application. The request fails. See the associated messages. Error return_code1.return_code2.return_code3 writing capture data extract process table registration_tag.sequence. The cross-reference process failed for with the stated return code while writing the given registration tag and sequence. The request fails. See the associated messages. Warning application changed extract over this release implementation not recommended. See related message PWX-04596. Request continues. See the associated messages. Verify that continuity is maintained. extraction_map UDB_db
Table displays all Extraction Maps and the corresponding UDB databases. A single session can only process Extraction Maps for a single UDB database. Extraction fails.
224
User Response: PWX-04603 Explanation: System Action: User Response: PWX-04604 Explanation:
Resolve and retry. Extraction references log data from different UDB databases. Data Extraction references Extraction Maps that include log data on more than one UDB database. A single extraction can only reference data from a single UDB database. Extraction fails. Resolve and retry. map_schema LOGSID_instance map_type Table displays all Extraction Maps and the corresponding LOGSID instance and map type. A single session can only process Extraction Maps for a single LOGSID instance and matching map types. First misstating is highlighted, preceded by and followed by asterisks Extraction fails. Resolve and retry. Extraction references log data from different LOGSID instances or types. Data Extraction references Extraction Maps that include log data on more than one LOGSID instance or type. A single extraction can only reference data from a single LOGSID instance or type. Extraction fails. Resolve and retry. Connection lookup failed for connection_override and registration tag registration_tag. See related messages. Extraction fails. See the associated messages. Resolve and retry. Connection lookup failed for internal connection from Connection. See related messages. Extraction fails. See the associated messages. Resolve and retry. Connection override Connection gave subparameter<value> which clashed with instance_override. Investigate why the connection and instance clash. The configuration is a starting point the Connection control statements should tie in the exact connection used, the reason it was used can be derived from those connection parameters and the extract request. Extraction fails. Resolve and retry. CAPX Failed to create varstring for Variable. Program program_name, line number LineNumber. An internal error occurred during the processing of the task. The task ends. Contact Informatica Global Customer Support.
PWX-04000 to PWX-04999
225
Unable to find valid CAPX-type CAPI_CONNECTION statement for registration tag <registration_tag_name>. A valid CAPI_CONNECTION statement of type CAPX does not exist in the PowerExchange configuration file. The task ends. Verify that a CAPX-type CAPI_CONNECTION statement exists in the PowerExchange configuration file. If one exists, make sure that a CAPI_SRC_DFLT statement of type CAPX exists and points to the CAPI_CONNECTION statement. Error loading EOD data map qualifier1.qualifier2. The specified data map could not be loaded. The data map might be corrupted. Processing ends. Re-create the data map. Try the request again. On the MVS platform, ensure that the region size associated with the job is sufficient. To load the data map, a larger region might be required.
PWX-05000 to PWX-05999
PWX-05000 Explanation: System Action: User Response: PWX-05001 Explanation: System Action: User Response: PWX-05950 Explanation: System Action: User Response: PWX-05951 Explanation: System Action: User Response: Length of object name for object type object_type exceeds nnn bytes. The length of the object of the specified type exceeds nnn bytes. Processing continues. No response is required. Error error deleting cache file file_name. While deleting the specified cache file, an error occurred. Processing continues. No response is required. Unexpected record type. Expected <expected_record_type>, but found <found_record_type>. An unexpected record type was received. Processing continues. No response is required. Missing End-of-Block marker in block <block>. The specified block lacks an end-of-block marker Processing continues. No response is required.
226
PWX-06000 to PWX-06999
PWX-06001 Explanation: System Action: User Response: PWX-06003 Explanation: System Action: User Response: PWX-06004 Explanation: System Action: User Response: (Capture) DATA_SHARE An error was found with parameter DATA_SHARE in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) CHKPT_INTERVAL An error was found with parameter CHKPT_INTERVAL in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) CAPT_MASK An error was found with parameter CAPT_MASK in the Capture configuration file. The Condense job ends. Parameter CAPT_MASK is mandatory on MVS and not allowed on AS400s. On MVS, it should be set to the qualifiers for the data set names of partial or full condense files, which the job creates. (Capture) EXTF_PRIM_ALLOC An error was found with parameter EXTF_PRIM_ALLOC in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) EXTF_SCND_ALLOC An error was found with parameter EXTF_SCND_ALLOC in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) EXTF_VOL invalid An error was found with parameter EXTF_VOL in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) EXTF_UNIT invalid An error was found with parameter EXTF_UNIT in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant.
PWX-06000 to PWX-06999
227
(Capture) FILE_SWITCH_CRIT An error was found with parameter FILE_SWITCH_CRIT in the Capture configuration file. The Condense job ends. Parameter FILE_SWITCH_CRIT can take three values.
M. File switch occurs after the number of minutes in FILE_SWITCH_VAL has elapsed. This is the default. R. File switch occurs after the number of records in FILE_SWITCH_VAL was written to partial or full condense files. Z. File switches do not occur automatically, but might be done after a manual request. File switches might not be necessary when running batch condenses (COL_END_LOG=1) where record volumes are not excessive. PWX-06010 Explanation: (Capture) FILE_SWITCH_VAL An error was found with parameter FILE_SWITCH_VAL in the Capture configuration file. The parameter defines a number of minutes or records depending on the value of parameter FILE_SWITCH_CRIT. The Condense job ends. Set the parameter to the required number of minutes or records. (Capture) EXTF_TYPE An error was found with parameter EXTF_UNIT in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) INTF_PRIM_ALLOC An error was found with parameter INTF_PRIM_ALLOC in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) INTF_SCND_ALLOC An error was found with parameter INTF_SCND_ALLOC in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) INTF_VOL An error was found with parameter INTF_VOL in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) INTF_UNIT An error was found with parameter INTF_UNIT in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant.
System Action: User Response: PWX-06012 Explanation: System Action: User Response: PWX-06013 Explanation: System Action: User Response: PWX-06014 Explanation: System Action: User Response: PWX-06015 Explanation: System Action: User Response: PWX-06016 Explanation: System Action: User Response:
228
(Capture) INTF_TYPE An error was found with parameter INTF_TYPE in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) CONDF_PRIM_ALLOC An error was found with parameter CONDF_PRIM_ALLOC in the Capture configuration file. The Condense job ends. Set the parameter to the number of primary allocation units as defined by parameter CONDF_TYPE (tracks, cylinders or records). If omitted, it defaults to 1. This parameter is used on MVS and is not used on AS400s. (Capture) CONDF_SCND_ALLOC An error was found with parameter CONDF_SCND_ALLOC in the Capture configuration file. The Condense job ends. Set the parameter to the number of secondary allocation units as defined by parameter CONDF_TYPE (tracks, cylinders or records). If omitted, it defaults to 1. This parameter is used on MVS and is not used on AS400s. (Capture) CONDF_VOL An error was found with parameter CONDF_VOL in the Capture configuration file. The Condense job ends. Set the parameter to the VOL SER of the disk where partial and full condense files are to be allocated. If omitted, condense files are not restricted to a single disk. This parameter is used on MVS and is not used on AS400s. (Capture) CONDF_UNIT An error was found with parameter CONDF_UNIT in the Capture configuration file. The Condense job ends. Set the parameter to the unit type of the disk where partial and full condense files are allocated. This parameter is used on MVS and is not used on AS400s. (Capture) CONDF_TYPE An error was found with parameter CONDF_TYPE in the Capture configuration file. The Condense job ends. Set the parameter to the allocation unit for partial and full condense files, which is used in conjunction with parameters CONDF_PRIM_ALLOC and CONDF_SCND_ALLOC. Allowed values are TRK, CYL, REC. If omitted, allocation is done in cylinders. This parameter is used on MVS and is not used on AS400s. (Capture) NO_DATA_WAIT An error occurs in the NO_DATA_WAIT parameter of the PowerExchange Condense configuration file. PowerExchange Condense ends.
PWX-06000 to PWX-06999
229
User Response:
The NO_DATA_WAIT parameter must be set to a positive number. When PowerExchange Condense runs in continuous mode (COLL_END_LOG=0), the NO_DATA_WAIT parameter defines the number of minutes that PowerExchange Condense waits before starting another condense cycle. For the Adabas and IMS ECCRs, the NO_DATA_WAIT parameter defines the number of seconds that the ECCR waits for files during the first file iterations. (Capture) NO_DATA_WAIT2 An error occurs in the NO_DATA_WAIT2 parameter in the PowerExchange Condense configuration file. PowerExchange Condense ends. The NO_DATA_WAIT2 parameter must be set to a positive number. For PowerExchange Condense, the parameter defines the number of seconds that PowerExchange waits at the end-of-log for more change data before returning control to PowerExchange Condense. If this wait period elapses and new change data has not been received, PowerExchange returns control to the PowerExchange Condense, and PowerExchange Condense then stops the current condense cycle. For Adabas and IMS ECCRs, the NO_DATA_WAIT2 parameter defines the number of seconds that the ECCR waits for files for second and subsequent file iterations. (Capture) COND_CDCT_RET_P An error was found with parameter COND_CDCT_RET_P in the Capture configuration file. The job ends. The parameter must be set to a positive number defining the retention period in days for partial and full condense files. If omitted, it defaults to 60 days. (Capture) KEEP_ECF_OPT An error was found with parameter KEEP_ECF_OPT in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) CHKPT_NUM An error was found with parameter CHKPT_NUM in the Capture configuration file. The Condense job ends. The parameter must be set to a positive number defining the number of checkpoint files, which the Condense job uses to remember its position within the CAPI system through restart tokens, and the Condensed file information, which matches the CDCT file. A minimum of three checkpoint files is required. (Capture) CHKPT_BASENAME An error was found with parameter CHKPT_BASENAME in the Capture configuration file. The Condense job ends. The parameter must be set to the prefix of checkpoint files, which the Condense job uses to remember its position within the CAPI system through restart tokens, and the Condensed file information, which matches the CDCT file. The system appends suffixes in the format V1,V2 to format the actual file name. On MVS, data set qualifiers are used. On AS400s, a library and file mask are used.
230
(Capture) CHKPT_VOLSERS An error was found with parameter CHKPT_VOLSERS in the Capture configuration file. The Condense job ends. The parameter is optional and is only used on MVS. If used, then three disk VOL SER s are defined on which checkpoint data sets are allocated. (Capture) COND_ECF_RET_P An error was found with parameter COND_ECF_RET_P in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. Controller: Parse Error An error was met when loading the capture parameters files. The Condense job ends. Determine the parameter in error from the to diagnose associated messages, fix it and run the Condense job again. On MVS, the parameter file is read through DD DTLCACFG. On AS400s, the parameter file is *LIBL/CFG(CAPTPARM) Controller: Error expressing interest in event=event rc=return_code. An error occurred during the initialization of the interprocess event signalling. The Condense job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Error starting subtask name One of the three sub tasks started by the Condense Controller failed to start. For example, the Command Handler, Condense, or Dump task.
On MVS, this might occur if load modules DTLCCMD0, DTLCCND2 or DTLCDUMP could not be located. On AS400, this might occur if programs DTLCCMDH, DTLCCNDS, DTLCDUMP or service programs DTLCCMD0, DTLCCND2, DTLCDUMP could not be located. System Action: User Response: PWX-06035 Explanation: System Action: User Response: The Condense job ends. Verify that the necessary load modules are available. Controller: Error reading Capture KSDS. An attempt to read a SRT record from a Condense checkpoint file was unsuccessful on a warm start. The Condense job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. The Condense checkpoint file might be invalid. Controller: Started timestamp. Displays the date and time when the Condense Controller started. Processing continues. No response is required.
PWX-06000 to PWX-06999
231
Controller: Running as a PAC job (PGM=EDMPAC). On MVS, the program is running in the PAC environment under the control of program EDMPAC. Processing continues. No response is required. Checkpoint file file name has time timestamp. The file was created from a checkpoint at the given time. Processing continues. No response is required. Controller: Ending. This is the last message logged by Condense Controller prior to an orderly close down. The sub tasks (Command Handler, Condense and Dump) have already ended. The job ends. No response is required. Checkpoint restart using file file name. The specified file was used to provide the restart points in a warm start. Processing continues. No response is required. Error opening checkpoint restart file file name. An error occurred trying to open the selected file to provide the restart points in a warm start. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. The Condense checkpoint file might be invalid. Controller: unknown task specified for tracing. task_name An attempt was made through the Command Handler to set tracing on for a task that was not recognized. The command is ignored. Processing continues. If tracing is required, supply a valid task name such as CMD_HANDLER, CMDH, CONDENSE, COND, CONTROLLER, CONT, ALL. Controller: unknown command. An attempt was made through the Command Handler to issue a command that was not recognized. The command is ignored. Processing continues. See the adaptor guide documentation. Valid commands include CONDENSE, SHUTCOND, SHUTDOWN, STOPTASK, TRACEALL,TRACEOFF, TRACEON
232
Error posting event event rc=return_code. An error occurred when posting an event for cross task communication between the Controller, Command Handler, Condense, Dump. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Warm start complete. Tables restored from checkpoint file. Run time information concerning restart points was read in from the most recent checkpoint file. Reloading the registrations for the given DBID and DB_TYPE values was completed. Processing continues. with starting of the Condense sub task. No response is required. Controller: Cold start complete. Cold start processing has completed. Loading the registrations for the given DBID and DB_TYPE values was completed. Processing continues. with starting of the Condense sub task. No response is required. (Capture) CHKPT_VOLSERS 1 An error was found with the first comma-delimited parameter following CHKPT_VOLSERS in the Capture configuration file. The Condense job ends. Define a MVS disk VOLSER using a maximum of six characters. (Capture) CHKPT_VOLSERS 2 An error was found with the second comma-delimited parameter following CHKPT_VOLSERS in the Capture configuration file. The Condense job ends. Define a MVS disk VOLSER using a maximum of six characters. (Capture) CHKPT_VOLSERS 3 An error was found with the third comma-delimited parameter following CHKPT_VOLSERS in the Capture configuration file. The Condense job ends. Define a MVS disk VOLSER using a maximum of six characters. (Capture) DB_TYPE An error occurs in the DB_TYPE parameter in the PowerExchange Condense configuration file. PowerExchange Condense ends. The DB_TYPE value must be one of the following values: ADA, AS4, DB2, DCM, IDM, IMS, or VSM. The Adabas ECCR requires ADA. The IMS ECCR requires IMS.
PWX-06000 to PWX-06999
233
(Capture) SUBSYSTEM_ID An error was found with parameter SUBSYSTEM_ID in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) COLLECTION_BLK_SIZE An error was found with parameter COLLECTION_BLK_SIZE in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) CHKPT_PRIM_ALLOC An error was found with parameter CHKPT_PRIM_ALLOC in the Capture configuration file. The Condense job ends. On MVS, this mandatory parameter defines the allocation unit for primary extents on checkpoint files. On AS400s, this parameter is not used so delete it. (Capture) CHKPT_SCND_ALLOC An error was found with parameter CHKPT_SCND_ALLOC in the Capture configuration file. The Condense job ends. On MVS, this mandatory parameter defines the allocation unit for secondary extents on checkpoint files. On AS400s, this parameter is not used so delete it. Controller: Startup aborted, no checkpoint files named checkpoint_base* exist and cold start declined. No checkpoint files were found, but the user replied no to a request to confirm a Cold Start. The Condense job ends. If a cold start is required, reply yes to the confirmation request. If a warm start is required, ensure that the CHKPT_BASENAME parameter is correct and the checkpoint files created from the last run exist. Controller: subtask name ended. The specified subtask ended. Controller termination Processing continues. No response is required. Controller: Error handler triggered. A fatal error was detected by the C signalling system and an attempt was to shut down immediately all subtasks. Parameter SIGNALLING was set to Y. The Condense job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
234
Controller: Failure in error handler, immediate shutdown. while responding to a signalled fatal error, the system was unable to post an all tasks shutdown event. The Condense job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Condensing ended. Last checkpoint time time. The date and time of the last checkpoint file is logged. The Condense job ends. normally. No response is required. Controller: Error reading checkpoint SRT record, rc = return_code. An error was met reading the SRT record from the checkpoint file. The Condense job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. The Condense checkpoint file might be invalid. Controller: Error initializing tasks event table, rc = return_code. An error was met initializing the tasks event table that is used to allow communication between the Controller, Command Handler, Condense and Dump tasks. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. On AS400s, this message might be logged if there is an attempt to run 2 Condense jobs concurrently. The second job is not able to get at message queues that are locked by the first job. Verify that another instance of the Condense jobs is still running. Controller: Open Checkpoint failed, rc = return_code. An error was met on processing the checkpoint files to determine which is the most recent. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Error reading registrations from CCT file, rc = return_code. An error was met while reading registrations from the CCT file. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Error reading DCT records from checkpoint file, rc = return_code. An error was met while reading DCT records from the checkpoint file. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-06000 to PWX-06999
235
Starting Subtask program name. The specified program is being started for one of the sub tasks. Programs such as DTLCCMDH, DTLCCND2/DTLCCNDS, DTLCDUMP are used to run the Command Handler, Condense and Dump sub tasks. Processing continues. No response is required. Controller: Could not start trace trace_filter. Maximum number of traces already active. An unsuccessful attempt was made through the Condense command handler to set a trace on, but the maximum number of traces were already active. Processing continues. The trace command is ignored. Remove an active trace filter before adding the new one. Controller: Error closing checkpoint file after read. rc=return_code. During a Warm start, an error occurred on a close after reading records from the checkpoint file. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Capture failed to set signal handlers. An error occurred while registering a routine to handle C signals for detecting fatal errors. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Fatal error detected. Signal signal_name. Abend code code. Reason code code. A fatal error signal was detected. The job ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. (Capture) CONSUMER_API An error was found with parameter CONSUMER_API in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. (Capture) SIGNALLING An error was found with parameter SIGNALLING in the Capture configuration file. The Condense job ends. The parameter can take only values of N (default) or Y. (Capture) SEQUENCE_TOKEN An error was found with parameter SEQUENCE_TOKEN, SEQUENCE_TOKN2 or SEQUENCE_TOKN3 in the Capture configuration file. The Condense job ends.
236
The parameter has a maximum length of 256, and should contain hex values. (Capture) RESTART_TOKEN An error was found with parameter RESTART_TOKEN, RESTART_TOKN2 or RESTART_TOKN3 in the Capture configuration file. The Condense job ends. The parameter has a maximum length of 256, and should contain hex values. Parameter parameter value value invalid because reason The value passed to the specified parameter is invalid. The Condense job ends. Correct the parameter so it satisfies the validation requirement. Parameter LOGGING invalid. Must be Y or N The value passed to the specified parameter is invalid. The IMS log capture job ends. Enter either Y or N for the parameter. Parameter READLOG invalid. Must be a DD or DSN The value passed to the specified parameter is invalid. The IMS log capture job ends. Correct the parameter so it satisfies the validation requirement. Parameter COLDSTART invalid. Must be Y or N The value passed to the specified parameter is invalid. The IMS log capture job ends. Enter either Y or N for the parameter. Parameter STARTTIME invalid. Must be a valid timestamp The value passed to the specified parameter is invalid. The IMS log capture job ends. Correct the parameter. Parameter BYPASS_VERSION_CHECKING. Must be Y or N The value passed to the specified parameter is invalid. The IMS log capture job ends. Enter either Y or N for the parameter. Parameter CLEANUP. Must be Y or N The CLEANUP parameter in the Datacom ECCR table-based configuration member has an invalid value. The Datacom table-based ECCR ends. Enter either Y or N for the parameter.
PWX-06000 to PWX-06999
237
(Capture) CLEANUP_INTERVAL The CLEANUP_INTERVAL parameter in the Datacom ECCR table-based configuration member has an invalid value. The Datacom table-based ECCR ends. Set the parameter to a positive number. (Capture) CDC_BASE The CDC_BASE parameter in the Datacom ECCR table-based configuration member has an invalid value. The Datacom table-based ECCR ends. Set the parameter to a positive number. (Capture) CDC_ID The CDC_ID parameter in the Datacom ECCR table-based configuration member has an invalid value. The Datacom table-based ECCR ends. Set the parameter to a character. (Capture) REG_MUF The REG_MUF parameter in the Datacom ECCR table-based configuration member has an invalid value. The Datacom table-based ECCR ends. Set the parameter to a valid Datacom MUF name. (Capture) TSF The TSF parameter in the Datacom ECCR table-based configuration member has an invalid value. The Datacom table-based ECCR ends. Set the parameter to the name of the file that contains change data for test purposes. No registrations found on the CCT file. No registrations were found on the CCT file. Processing ends. Ensure that there are registrations for the DBID and DB_TYPE parameters type token hex_value The sequence and restart tokens from a cold start at specific tokens are displayed in hexadecimal, prior to a request for confirmation. On MVS, the confirmation request is in a PWX-06101 message sent to the operators console as a WTOR. Processing continues. Respond either Y or N to the cold start confirmation request. No checkpoint files, cold start from specified restart point restart_point (Y/N) On MVS, this message is used in a WTOR prompt, which requires a reply of Y or N to confirm that a cold start of the Condense job is required. The system waits for the reply to the WTOR.
System Action: User Response: PWX-06101 Explanation: System Action:

238
User Response: PWX-06102 Explanation: System Action: User Response: PWX-06103 Explanation: System Action: User Response: PWX-06104 Explanation: System Action: User Response: PWX-06105 Explanation: System Action: User Response: PWX-06106 Explanation: System Action: User Response:
Reply either Y or N to the WTOR after checking the hex values of the tokens. No checkpoint files and no tokens specified, cold start using current PowerExchange Logger file position file_position (Y/N) On MVS, this message is used in a WTOR prompt that requires a reply of Y or N to confirm that a cold start of the Condense job is required. The system waits for the reply to the WTOR. Respond Y or N to the WTOR. Cold Start accepted A reply of Y was received from the confirmation request that a cold start is required. Processing continues. No response is required. Cold Start declined A reply of N was received from the confirmation request that a cold start is required. Processing ends. No response is required. Controller: Executing command command. The specified command received from the Command Handler was processed. The command is executed. No response is required. Controller: Signal Error error_information. A fatal error was detected by the C signalling environment. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: All subtasks shut down. The Command Handler, Condense and Dump subtasks have shut down. Processing ends. No response is required. Controller: Error in API_routine rc=return_code. An error occurred. The message text and return code describe the error. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Warning reason. An unexpected event occurred. Processing continues.
PWX-06000 to PWX-06999
239
User Response:
Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Unloaded module name. The program for the specified task is unloaded. This is the last message logged from the Command Handler, Condense or Dump tasks. Processing continues. No response is required. Controller: All tasks initialization complete. The Controller has received event notifications from the Command Handler, Condense and Dump tasks that they have completed their initialization and are ready to start work. Processing continues. The Controller posts event capture startup complete and takes an initial checkpoint. No response is required. Controller: Starting the capture subtasks. The subtask programs (Command handler, Condense, Dump) are about to be loaded and run. Processing continues. No response is required. No active Capture Registrations No active Capture Registrations were read from the CCT file for the given database type and ID. Processing ends. Review the values of DBID and DB_TYPE in the Capture Configuration file against the values in the Registration Group on the Navigator. Then open the Registration Group and check that there are some active registrations. No active Capture Registrations for processing After validation processing, no Capture Registrations remain for processing. Processing ends. See message PWX-06114. This error might be logged if active registrations have the Condense type set to none instead of partial or full. Registration load Session could not be started. An error occurred while processing Capture Registrations. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Failure loading registration for Instance connection_instance. Registration failed to load for the specified instance. Initializationcollection is ended and the request fails. Use this and the associated messages to correct the request or configuration and retry.
240
Registration loaded: DBName: database_name RegName: name Creator: creator Table: table The registration was successfully loaded. Processing continues. No response is required. Controller: change_type registration tag tag Reports a change to a registration tag. The change type can be added new or discarded inactive. Processing continues. No response is required. Error adding MSS publication. Reports a change to a registration tag. The change type can be added new or discarded inactive. Processing ends. Review the parameters passed to the utility. Registration loaded: DBName: database_name RegName: name Condense: option Creator: creator Table: table The registration was successfully loaded. Processing continues. No response is required. (Capture) COND_ON_FSWITCH An error was found with parameter COND_ON_FSWITCH in the Capture configuration file. The Condense job ends. Delete the parameter. It is redundant. Controller: Controller switched trace action task_name. Following a TRACE command to the Command Handler, the action was taken to the specified task. Processing continues. No response is required. Controller: Error fetching / releasing load module DTLIDCAM. An error was met when fetching or releasing load module DTLIDCAM. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Error unloading task task_name. An operating system error was met while trying to unload the program for a Condense job subtask (DTLCCMDH, DTLCCNDS/DTLCCND2, DTLCDUMP). Processing ends.
PWX-06000 to PWX-06999 241
User Response:
Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Controller: Premature end of Condense subtask. A failure occurred in the Condense subtask causing it to end prematurely. For example, the Condense subtask ended during initialization before posting the Condense initialization complete event. Or the Condense subtask ended without the all tasks shutdown event having been posted. Processing ends. Determine the cause of the error from associated messages from the Condense task. PWXCCL configuration error: CAPTURE_NODE_PWD and CAPTURE_NODE_EPWD parameters are mutually exclusive. Both the CAPTURE_NODE_PWD and CAPTURE_NODE_EPWD parameters are specified in the pwxccl.cfg configuration file for the PowerExchange Logger for Linux, UNIX, and Windows. Only one of these parameters is allowed. The PowerExchange Logger process fails to initialize. Remove or comment out either the CAPTURE_NODE_PWD parameter or the CAPTURE_NODE_EPWD parameter. Alternatively, you can remove both parameters because they are optional. Controller: Error processing ERT records. rc=return_code. An error was met processing ERT records from the checkpoint file or in adding additional ERT records derived from tags for fresh registrations. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Checkpoint taken to file=file name time= timestamp A checkpoint was taken at this time to this file. Processes continues No response is required. No columns in registration. DBName: database_name RegName: name Creator: creator Table: table No columns were read on the specified registration, so it cannot be processed. Processing ends. Review the registration with the Navigator and recreate it with some columns. Invalid specification for ADASEL_DSN in Capture Parameters The value specified for ADASEL_DSN is incorrect. Processing ends. Review the contents of DDname DTLCACFG. Correct the error. Then, run the request again.
242
Controller: Error processing RET records. rc=return_code. An error was met processing RET records from the checkpoint file. The data relates to retention of condensed data Processing ends. Determine the cause of the error from associated messages from the Condense task. If necessary, contact the Supplier to report the error, specifying the function being performed at the time of the error. RACF_CLASS An error was found with parameter RACF_CLASS in the configuration file. Processing ends. The parameter value is text with a maximum length of 8bytes. The parameter is used in MVS PowerExchange Listener jobs. (Capture) COLL_END_LOG An error was found with parameter COLL_END_LOG in the Capture configuration file. Processing ends. The parameter value can be 0 meaning run continuously or 1 meaning run in batch mode and shut down when no data has arrived with a time interval. RECONID An error was found with the RECONID parameter in the DBMOVER configuration file. Processing ends. The parameter value is text with a maximum length of eight bytes. The parameter is used in MVS PowerExchange Listener or IMS ECCR jobs. RECON1 An error was found with the RECON1 parameter in the configuration file. Processing ends. The parameter value is text with a maximum length of 44 bytes. The parameter is used in MVS PowerExchange Listener or IMS ECCR jobs. RECON2 An error was found with the RECON2 parameter in the configuration file. Processing ends. The parameter value is text with a maximum length of 44 bytes. The parameter is used in MVS PowerExchange Listener or IMS ECCR jobs. RECON3 An error was found with the RECON3 parameter in the configuration file. Processing ends. The parameter value is text with a maximum length of 44 bytes. The parameter is used in MVS PowerExchange Listener or IMS ECCR jobs.
PWX-06000 to PWX-06999
243
DBDLIB An error was found with the DBDLIB parameter in the configuration file. Processing ends. The parameter value is text with a maximum length of 44 bytes. The parameter is used in MVS PowerExchange Listener or IMS ECCR jobs. IMSID An error was found with the IMSID parameter in the configuration file. Processing ends. A maximum of ten IMSID array entries can be processed. The parameter is used in MVS PowerExchange Listener or IMS ECCR jobs. RECON An error was found with the RECON parameter in the configuration file. Processing ends. The parameter contains a list of three RECON values. It is used in MVS PowerExchange Listener or IMS ECCR jobs. (Capture) CAPT_IMAGE An error was found with parameter CAPT_IMAGE in the Capture configuration file. Processing ends. The parameter value can be AI meaning capture After Images only or BA meaning capture both Before and After images onto condense files. (Capture) OPER_WTO An error was found with parameter OPER_WTO in the Capture configuration file. Processing ends. Enter either Y or N for the parameter. (Capture) CAPT_STATS An error was found with parameter CAPT_STATS in the Capture configuration file. Processing ends. Enter either Y or N for the parameter. IMS SLDS File file_name closed with Some:No records processed. Progress since last statistics display: The IMS Log Based ECCR generates capture statistics message (PWX-06152) when it completes the processing of an IMS log. These statistics reflect the capture counts since the last PWX-06152 message was generated. If multiple logs are being processed, the capture counts reflect the total of all logs being processed concurrently as opposed to the specific log closed. No response is required. registration/dbd/segment ISRT=number DLET=number REPL=number Informational message. No response is required.
User Response: PWX-06153 Explanation: User Response:
244
DTLCACON argument format error found <parameter> expected <cs=> The parameter or argument passed to DTLCACON does not begin with cs= keyword. The request fails. Correct argument and resubmit. executable configuration file overridden with file_name When you started the DTLCACON or PWXCCL executable, PowerExchange used the override configuration file that you specified in the cs= parameter. PowerExchange Logger or PowerExchange Condense processing continues. No response is required. You can use this message as part of an audit trail. Mixing registrations from override <DBID> and default <INST> DBIDS not allowed The registrations processed so far are sourced from the DBID in the cfg(CAPTPARM) and the INSTANCE in CFG(DBMOVER). This is not allowed. Processing ends. Change parameterisation to limit registrations to one instance or create extra registrations to circumvent the test. Registration <registration_name> not found The registration was not found in either of the available instances. Processing ends. Review both the DBID in the cfg(CAPTPARM) and the INSTANCE (INST) in CFG(DBMOVER) and ensure that the registration is correct. Missing registrations expected <parameter_count> found <match_count.> The registrations processed have not all been found Processing ends. Review both the DBID in the cfg(CAPTPARM) and the INSTANCE (INST) in CFG(DBMOVER) and ensure that the registrations are correct. DTLCACON sub process ids begin <process_number> for start at <start_time> This message is informational. This message is provided to assist diagnosis in subtasks and act as audit trail when multiple condenses are run. DTLCACON Connection instance missing <count_of> connections. The condense controller has not found a default instance in the dbmover configuration file. Note if the connections count is zero there is no connection information. Correct the dbmover configuration or ensure that it is in the datalib in the library list. (Capture) KEY_CHANGE_ALW An error was found with parameter KEY_CHANGE_ALW in the Capture configuration file. Processing ends. Enter either Y or N for the parameter.
PWX-06000 to PWX-06999
245
Error creating file name for Capture checkpoint file. An error was met in creating a file name for a Capture checkpoint file. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Access method access_method in command set commandset does not match other command sets. When multiple command sets are executed through a command list, either one of the from access methods is not the same as the others, or one of the to access methods is not the same as the others. Processing ends. Correct the access method in the problem command set. Source file/table_name in command set command_set_name already present in command list. Data source in this command set exactly matches one already specified in another command set in this list. Multiple targets can be specified in the same command set. Do not use a second command set to achieve this. DBMOVE aborts without transferring any data. Put all targets from the one data source in the same command set. Location location in command set command_set_name does not match other command sets. All command sets must have their data sources from the same location. DBMOVE aborts without transferring any data. Restrict command lists to those command sets that are from the same location. Invalid Session Id in command list. The session is invalid such as not enclosed in double quotes or longer than eight characters. DBMOVE aborts without transferring any data. Correct the session parameter. Restarting session session after number records. DBMOVE is restarting at the specified point. Processing continues. No response is required. Error writing to session log file name. An error was met in writing to (or opening and closing) the session log file. Processing ends. Verify that the file name is valid, that permissions allow writing to the file and that there is adequate space on the disk. Error reading session log file name. An error was met in reading the session log file.
246
System Action: User Response: PWX-06170 Explanation: System Action: User Response: PWX-06171 Explanation: System Action: User Response: PWX-06172 Explanation: System Action: User Response: PWX-06173 Explanation: System Action: User Response: PWX-06174 Explanation: System Action: User Response: PWX-06175 Explanation: System Action: User Response: PWX-06176 Explanation: System Action: User Response: PWX-06177 Explanation: System Action:
Processing ends. Verify that the file name is valid and that permissions allow reading from the file. Type TXT not valid FROM type in DBMOVE. TXT is not permitted as a data source type. DBMOVE aborts without transferring any data. Reconsider the type of the data source. SEQ is a probable replacement. Error restarting - session logged differs from current DBMOVE. There is a difference between the session log record and the way that the current DBMOVE was called. The attempt to restart the DBMOVE is aborted. Review the session log record and the DBMOVE parameters. Cannot use COLS= in command list. Use MAP= instead (command_set_name). COLS= is deprecated, and the functionality can be achieved with a MAP= statement. If using a command set in a command list, MAP= must be used. DBMOVE aborts without transferring any data. Rewrite the command set to use MAP=. Cannot specify multiple session ids. The session ID was specified more than once. DBMOVE aborts without transferring any data. Remove the extra session parameter from the command set. DB dbname in command set command_set_name does not match other command sets. All command sets in this command set list must have the same dbname as specified in the db= parameter of the command sets. DBMOVE aborts without transferring any data. Make sure all command sets have the same source DB. Error Finding AS4J connection. The CAPI connections do not include a type AS4J connection. Extraction fails. Resolve and retry. Error Rc return_code from receiver list lookup. The lookup of the receivers associated with the journal for CDC extract failed with the given code. The request fails. Review associated messages, establish cause, fix and retry. Error converting token_occurrence to new release with rc return_code. A return code was received converting the stated occurrence of token to the new release. The request fails.
PWX-06000 to PWX-06999
247
User Response: PWX-06178 Explanation: System Action: User Response: PWX-06179 Explanation: User Response: PWX-06210 Explanation:
Review associated messages, establish cause, fix and retry. Error updating token_occurrence token to new release with rc return_code. A return code was received updating the stated occurrence of token to the new release. The request fails. Review associated messages, establish cause, fix and retry. IMS ECCR Run complete. Totals for this run: This message displays the statistics for all logged changes for this run. No response is required. (Capture) FILE_SWITCH_MIN An error was found with parameter FILE_SWITCH_MIN in the Capture configuration file. The subparameters define a number of minutes or records depending on the value of parameter FILE_SWITCH_CRIT. The Condense job ends. Set the subparameters to the required number of minutes or records. (Capture) FILE_SWITCH_MIN (value, subparameter 1) An error was found with subparameter 1 of the FILE_SWITCH_MIN parameter in the Capture configuration file. This subparameter defines the minimum number of minutes or records (depending on the value of parameter FILE_SWITCH_CRIT) between file switches. The Condense job ends. Set the subparameter to the required number of minutes or records. (Capture) FILE_SWITCH_MIN (ignore value, subparameter 2) An error was found with subparameter 2 of the FILE_SWITCH_MIN parameter in the Capture configuration file. This subparameter defines the number of minutes or records (depending on the value of parameter FILE_SWITCH_CRIT) that a cold-started condense ignores the FILE_SWITCH_MIN subparameter 1 value and only perform file switches based on the FILE_SWITCH_VAL parameter. The Condense job ends. Set the subparameter to the required number of minutes or records. (Capture) FILE_FLUSH_VAL An error was found with the FILE_FLUSH_VAL parameter in the Capture configuration file. This parameter defines the number of seconds between flushes of partial condense files, to allow Continuous Capture CAPXRT sessions to capture data from the current partial condense file. The Condense job ends. Set the subparameter to the required number of seconds. (Capture) FILE_SWITCH_MIN subparameter 1 value (value_from_condense_config_file) is = FILE_SWITCH_VAL (value_from_condense_config_file). The minimum file switch time specified in the Capture configuration file is greater than or equal to the base file switch time. The minimum value is ignored, and all file switches take place based on FILE_SWITCH_VAL.
248
The Condense job continues. If this is not the desired behavior, correct the values in the Condense configuration file. PWXCCL configuration: Input parser failed with RC=(return_code) while parsing the PowerExchange Logger configuration file (file_name). The PowerExchange parser encountered an error while validating the pwxccl.cfg configuration file for the PowerExchange Logger for Linux, UNIX, and Windows. In the message text:
return_code is the return code for the error. file_name is the name of the PowerExchange Logger configuration file, pwxccl.cfg. System Action: User Response: The PowerExchange Logger process fails to initialize. Review the messages related to this failure in the PowerExchange message log file to identify the PowerExchange Logger configuration parameters that failed validation. Then correct these parameters. CCL Configuration: CHKPT_BASENAME directory not accessible. CHKPT_BASENAME=(path_basename) System errno=<error_number> PowerExchange cannot access or create the directory for storing the generated checkpoint files for the PowerExchange Logger for Linux, UNIX, and Windows. This directory is specified in the CHKPT_BASENAME parameter of the pwxccl.cfg file. In the message text, system errno is the error code returned from the directory access attempt. System Action: User Response: The PowerExchange Logger process fails to initialize. Ensure that the CHKPT_BASENAME parameter specifies a valid path. Also, ensure that the PowerExchange Logger process has adequate permissions to create the directory if it does not exist. CCL Configuration: EXT_CAPT_MASK directory not accessible. CHKPT_BASENAME=(path_mask) System errno=<error_number> PowerExchange cannot access or create the directory for storing the log files of the PowerExchange Logger for Linux, UNIX, and Windows. This directory is specified in the EXT_CAPT_MASK parameter of the pwxccl.cfg file. In the message text, system errno is the error code returned from the directory call. System Action: User Response: The PowerExchange Logger process fails to initialize. Ensure that EXT_CAPT_MASK parameter specifies a valid path. Also, ensure that the PowerExchange Logger process has adequate permissions to create the directory if it does not exist. GROUPDEFS= and REGS= not allowed at the same time GROUPDEFS and REGS parameters cannot be used together. Validation fails. Correct the parameters in the condense configuration file. GROUP An error was found with parameter GROUP in the configuration file. Processing ends. The syntax should be GROUP=(group_name,mask).
PWX-06000 to PWX-06999
249
GROUPNAME An error was found with parameter GROUPNAME in the configuration file. Processing ends. The syntax should be GROUP=(group_name,mask). The name length should less than or equal to 255. GROUPCAPTMASK An error was found with parameter GROUPCAPTMASK in the configuration file. Processing ends. The syntax should be GROUP=(group_name,mask). The mask length should less than or equal to 255. SCHEMANAME An error was found with parameter SCHEMANAME in the configuration file. Processing ends. The syntax should be SCHEMANAME=schema. The schema length should less than or equal to 255. REGNAME An error was found with parameter REGNAME in the configuration file. Processing ends. The syntax should be REGNAME=registration. The registration name length should less than or equal to 8. GROUPDEFS An error was found with parameter GROUPDEFS in the configuration file. Processing ends. The syntax should be GROUPDEFS=file_name. Statement statementid out of sequence in config file A statement in the configuration file is being loaded in the incorrect sequence. Validation fails. Correct the parameters in the condense configuration file. Only one parameter per line allowed in the config file A statement in the configuration file contains several parameters. Validation fails. Correct the parameters in the condense configuration file. Duplicated groups not allowed in the config file. Group group_name Duplicated groups in the configuration file. Validation fails. Correct the parameters in the condense configuration file.
250
PWX-06260 Explanation: System Action: User Response: PWX-06261 Explanation: System Action: User Response: PWX-06262 Explanation: System Action: User Response: PWX-06263 Explanation: System Action: User Response: PWX-06264 Explanation: System Action: User Response: PWX-06265
SCHEMA parameter not allowed for dbtype Schema parameter is not allowed for some database types. Validation fails. Correct the parameters in the condense configuration file. Group <group> cannot use registration <registration_name> for reg_schema=<schema> table=<table> with schema=<schema>. Already used. A registration already exists for that schema and table name. Ignore the registration, print a message and continue processing. No response is required. Duplicated capture masks not allowed in the config file. Mask maskname Duplicated capture masks in the configuration file. Validation fails. This ends duplicate condense file names. Correct the parameters in the condense configuration file. No Registrations found for group <group_name>. No registrations were found matching the registration parameters specified for this group. Validation fails. Condense ends. Review the Registration statements for this particular group. Group <group> using registration <registration_name> reg_schema=<schema> table=<table> with schema=<schema>. A group uses a registration with a schema override. A report of the registrations used by GROUPDEFS is printed. No response is required. CCL Configuration: Input Parser failed with RC (return_code) for CCL GROUPDEF config file (file_name). Parsing of the CCL GROUPDEF configuration file failed. In the message text:
return_code is the return code for the error. file_name is the name of the CCL configuration file that was being processed. System Action: User Response: The CCL job fails. Review the log to identify incorrect CCL GROUPDEF parameter values, if any. Then correct those parameter values. Thread attribute initialization failure. Default attributes will be used. RC = <return_code> : <explanation> The process was not able to modify thread execution attributes. The process attempts to run using default execution attributes. If the process fails, contact your software provider with this and any other errors or warnings reported by the process.
PWX-06000 to PWX-06999
251
Cannot modify default thread stack size. Default stack size will be used. RC = <return_code> : <explanation> The process was not able to modify the default thread stack size. The process attempts to run using the default thread stack size. If the process fails, contact your software provider with this and any other errors or warnings reported by the process. Thread attribute deletion failure. RC = <return_code> : <explanation> The process was not able to delete thread execution attributes. The process continues. If the process fails, contact your software provider with this and any other errors or warnings reported by the process. CCL Controller: Signal SIGTERM received. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows received a signal to initiate shutdown processing. The Controller initiates shutdown processing. No response is required. CCL Controller: Clean shutdown will be initiated. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows is about to initiate shutdown processing. The Controller task will initiate a controlled shutdown, which preserves change data. No response is required. CCL Controller: Event <event_id>, <event_name> is ignored because the PowerExchange Logger is shutting down. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows ignored the specified event because the PowerExchange Logger is shutting down. Shutdown processing continues. No response is required. CCL Controller: Event <event_id>, <event_name> is ignored because it is an unknown event. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows ignored the specified event because it does not recognize the event as a defined event. The Controller ignores the event. No response is required. CCL Controller: Controller can shut down immediately because no subtasks are running. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows received a SHUTDOWN command before any of its subtasks had started. Consequently, the Controller does not have to wait for its subtasks to complete before initiating shutdown processing. The Controller initiates PowerExchange Logger shutdown processing immediately. No response is required.
252
CCL Controller: Command Handler shut down because of an error. The Command Handler subtask of the PowerExchange Logger for Linux, UNIX, and Windows shut down because it encountered an error. The PowerExchange Logger shuts down. To diagnose the error, review the relevant messages in the PowerExchange log file. CCL Controller: Event <event_id>, <event_name> is ignored because Command Handler has shut down. Because the Command Handler subtask of the PowerExchange Logger for Linux, UNIX and Windows has shut down, the specified event is ignored. All subsequent events will also be ignored. PowerExchange Logger shutdown processing continues. No response is required. CCL Controller: PWXCCLW task shut down because of an error. The internal PWXCCLW task of the PowerExchange Logger for Linux, UNIX, and Windows shut down because it encountered an error. The PowerExchange Logger will shut down. To diagnose the error, review the relevant messages in the PowerExchange log file. CCL Controller: Event <event_id>, <event_name> is ignored because the PWXCCLW task has shut down. Because the internal PWXCCLW task of the PowerExchange Logger for Linux, UNIX and Windows has shut down, the specified event is ignored. All subsequent events will also be ignored. PowerExchange Logger shutdown processing continues. No response is required. CCL Controller: DTLCDUMP task shut down because of an error. The internal DTLCDUMP task of the PowerExchange Logger for Linux, UNIX, and Windows shut down because it encountered an error. The PowerExchange Logger will shut down. To diagnose the error, review the relevant messages in the PowerExchange log file. CCL Controller: Event <event_id>, <event_name> is ignored because internal DTLCDUMP task has shut down. Because the internal DTLCDUMP task of the PowerExchange Logger for Linux, UNIX and Windows shut down, the specified event is ignored. All subsequent events will also be ignored. PowerExchange Logger shutdown processing continues. No response is required. CCL Controller: Event ID ALL_TASK_SHUTDOWN ignored. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows ignored the ALL_TASK_SHUTDOWN event because a shutdown is in progress. Any subsequent shutdown requests are ignored. PowerExchange Logger shutdown processing continues.
System Action:
PWX-06000 to PWX-06999
253
No response is required. CCL Controller: Event <event_id>, <event_name> is ignored because a PowerExchange Logger shutdown is pending. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows ignored the specified event because a PowerExchange Logger shutdown is pending. PowerExchange Logger shutdown processing continues. No response is required. CCL Controller: Failed to post event PEV_ALL_TASK_SHUTDOWN during error handling. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows failed to post a PEV_ALL_TASK_SHUTDOWN event during error handling. The PowerExchange Logger shuts down. To diagnose the event failure that invoked error handing, review the relevant messages in the PowerExchange log file. CCL Controller: Subtask wait interval expired during error handling. Controller is shutting down. The Controller task of the PowerExchange Logger for Linux, UNIX, and Windows waited longer than the wait interval of one minute for a subtask to respond during error handing. The PowerExchange Logger will shut down. To diagnose the event failure that invoked error handing, review the relevant messages in the PowerExchange log file. CCL Controller: Timer expired after (number_of_seconds) seconds while waiting for (number_of_tasks) tasks to close. During shutdown processing, the Controller task of the PowerExchange Logger for Linux, UNIX, and Windows waited the maximum number of seconds for subtasks to end but not all subtasks ended. This wait interval is specified in the CONDENSE_SHUTDOWN_TIMEOUT parameter of the pwxccl.cfg file. The PowerExchange Logger shuts down. To increase the wait interval, edit the CONDENSE_SHUTDOWN_TIMEOUT value in pwxccl.cfg. CCL Controller: Event <event_id>, <event_name> ignored during WaitForStartup. During PowerExchange startup, the specified event was ignored because of an internal WaitForStartup command. PowerExchange Logger startup processing continues. No response is required. CHKPT_FILE_CTL=<file_name> and space/volumes not allowed at the same time CHKPT_FILE_CTL and any of CHKPT_PRIM_ALLOC, CHPPT_SCND_ALLOC and CHKPT_VOLSERS parameters cannot be used together. Validation fails. Change the configuration file so it conforms to the rules
254
resource=<file_name> and resource conflict (type) A parameter conflict exists in the condense configuration file. In the message text:

resource is the parameter in the condense configuration file. file_name is the name of the condense configuration file. type is one of the following values and describes the error: BOTH STOR. CONDF_FILE_CTL and CONDF_PART_STORCLAS cannot be used together with the CONDF_UNIT and CONDF_VOL parameters. FULL STOR. CONDF_FILE_CTL cannot be used together with the CONDF_UNIT and CONDF_VOL parameters when performing a full condense. PART STOR. CONDF_PART_STORCLAS cannot be used together with the CONDF_UNIT and CONDF_VOL parameters when performing a partial condense. System Action: User Response: PWX-06309 Explanation: System Action: User Response: PWX-06310 Explanation: System Action: User Response: PWX-06311 Explanation: System Action: User Response: PWX-06312 Explanation: Validation fails. Correct the parameters in the condense configuration file. Error Opening Parm file rc1=<return_code1> rc2=<return_code2> rc3=<return_code3> filename=<file_name> While attempting to open the specified file, an error occurred. Processing ends. To diagnose the problem, review the return codes. Error CTL line size length=length is over limit limit The line too long. Processing ends. Verify the parameter. Error reading CTL file rc1=<return_code1> rc2=<return_code2> rc3=<return_code3> filename=<filename> Error trying to read specified file name. Processing ends. To diagnose the problem, review the return codes. Error KEY supplied (user_key) only matches (expected) for number bytes. () An error occurred while processing a control file the message records an issue with the file key specification. The message should appear in a print of the control file after the problem line. Processing ends. Change the control file so it conforms to the rules. Error name line <original> becomes <example> around <nnn> bytes, exceeds 80. An error occurred while processing a control file. The specified line does not fit in columns 2 to 80 when the largest possible generated name is substituted. The example shows the specified prefix. Processing ends. Change the control file so it conforms to the rules or find the prefix in the condense parameters or group definitions.
PWX-06000 to PWX-06999
255
Error no key in CTL file file name. No key was found when processing the specified control file. Processing ends. Change the control file so it conforms to the rules. Error found number names on file file_name - expected 3. An error occurred while processing a control file. An incorrect number of lines have been found in the specified control file. Processing ends. Change the control file so it conforms to the rules. Error found number lines on file file name - expected 35. An error occurred while processing a control file an incorrect total number of none comment lines have been found in the specified control file. The print of the parameter file shows the number of lines accepted before processing the line following. Processing ends. Change the control file so it conforms to the rules. Warning derived suffix suffix limit number for cluster in file file name - check. This warning invites you to check the suffix derived is as intended, the system feels it was not ended correctly or is longer than allowed. This poses a risk to future processing. Processing continues. Correct the control file. Error: Chkpt ctl <file_name> contains suffix <value> for cluster name. This stops suffixes on checkpoints causing processing errors due to confusion on warm starts or creating checkpoints, Checkpoints names are generated form CHKPT_BASENAME and it is essential for smooth running that this association is not volatile. Within the checkpoint most running information is stored and flexibility is allowed for other names which can be stored in and then retrieved from the checkpoint. Processing ends. Correct the control file. Condense File I/F: Error in action on file_type file. Codes code1,code2,code3. File=file name. An error occurred while processing a Condense file and this message logs the action being performed, the return codes and the name of the file. The file type can be CDCT, full, or partial. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
256
Condense File I/F: Full file: Hashed Ind=hi_hex Synonym=counter Image=img_hex tag=registration_tag. An error occurred while processing the Full Condense file and this message logs information about the key of a full condense file at the time of an error. In the message text:
hi_hex is the hexadecimal hashed index. If the hashed index is 00 and the synonym counter is set to -1, and the total length of all columns that form the key is less than 200. Otherwise, the hashed index is set to FF and the synonym counter is set to -2 for the first synonym, -3 for the second synonym, and so on. counter is the synonym counter. img_hex is the hexadecimal image value. registration_tag is the capture registration tag. System Action: User Response: PWX-06352 Explanation: System Action: User Response: Processing ends. See the associated messages for the reason for the error. Condense File I/F: Full file: Hashed key=key. An error occurred while processing the Full Condense file and this message logs the hashed key of the record affected. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense File I/F: CDCT file type key: Instance=instance tag=tag token=hex error_information. This is a print of the key for a CDCT for which IO was being attempted. It provides supplementary information when required. Processing continues. See the associated messages produced at the time of an error. Condense File I/F: type=value. This message logs error information. The type can be expected instance, expected tag. Processing ends. See the associated messages for the reason for the error. Condense File I/F: Error in API_routine rc=return_code. An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Error: Checkpoint File file name could not be read: detail An error occurred when trying to read the checkpoint files during condense warm start MVS only. Processing ends. Check detail reason. Review logs for system messages.
PWX-06000 to PWX-06999
257
Warning: Checkpoint file file name could not be read and was ignored: detail An error occurred when trying to read the checkpoint files during condense warm start Not for MVS. Processing continues. No response is required. Condense: Starting. Instance=instance. The PowerExchange Condense subtask is started. The instance value, instance, from the configuration file DBID parameter is used as the first part of the key to the CDCT file. PowerExchange Condense processing continues. No response is required. Condense: Ending status. The PowerExchange Condense subtask is ending. The status variable indicates whether the subtask ended successfully or unsuccessfully. PowerExchange Condense processing continues. If the PowerExchange Condense subtask ended unsuccessfully, review previously logged messages to determine the cause of the problem. Condense: Warning reason. PowerExchange Condense encountered an unexpected event. PowerExchange Condense processing continues. Contact Informatica Global Customer Support specifying the function being performed at the time of the error. Condense: Shutting down because all tasks shutdown event received. The PowerExchange Condense subtask is shutting down because an all tasks shutdown event was received. The PowerExchange Condense subtask shuts down. Review the reason for the all tasks shutdown condition, which might be caused by the PowerExchange Condense Controller or Command Handler subtask. Condense: Deleting file condense_file_name. PowerExchange Condense has deleted the specified condense file because no entry for it exists in the CDCT file. When PowerExchange initializes, shuts down, or performs a file switch, it might delete condense files for the following reasons:
Based on the setting of the PowerExchange Condense COND_CDCT_RET_P parameter, the condense file has expired. The CDCT file does not contain an entry for this condense file. The CDCT entry might not exist for a variety of reasons such as: A failure occurred when the condense file was created. The CDCT was synchronized with the contents of an old checkpoint data set when PowerExchange Condense was restarted. System Action: User Response: PowerExchange Condense processing continues. No response is required.
258
Condense: Deleting CDCT record. Reason: reason_code. Tag=tag Sequence=hex date_and_condense_file_name. PowerExchange Condense deleted a CDCT entry for the specified key and reason code. The key is defined by the given tag and sequence values, plus the instance of the job. In the message text:
reason_code is the reason code: 1. Data not in step - del. 2. Data not in step - ins. 3. Retention period. 4. Data not filed yet. 10. Data not checkpointed. 11. Data is older than retention period. tag is the registration tag. hex is the hexadecimal value of the sequence number. date_and_condense_file_name is the date and condense file name. The date and condense file name are omitted if the same date and file name is displayed in the previous PWX-06405 message. System Action: User Response: PWX-06406 Explanation: PowerExchange Condense processing continues. No response is required. Condense: Error Reason: routine rc=return_code. A PowerExchange Condense routine encountered an error. In the message text:
routine is the routine that encountered the error. return_code is the return code: 1. Data not in step - del. 2. Data not in step - ins. 3. Retention period. 4. Data not filed yet. 10. Data not checkpointed. 11. Data is older than retention period. 51. Create Partial Condensed Group File. 100. Rollback failure. 101. Initialize CAPI failure. 102. Failure on warm start CDCT check. 103. READ I/F_Open. 104. Delete_incomplete condensed data. 105. Point And Read CDCT. 106. CDCT data not checkpointed. 107. Matching CDCT data to checkpoint. 108. CDCT data only on checkpoint. 109. Read Next CDCT. 110. CDCT data not checkpointed. 111. CDCT data only on checkpoint. 112. Read Next CDCT. 113. Insert CDCT. 114. Point And Read CDCT. 115. Condense File Switch.
PWX-06000 to PWX-06999
259
116. Condensing. 117. READ_I/F Data Access Problem. 118. READ_I/F. 119. Create Partial Condensed File. 120. Write Part Cond Rec. 121. Create Full Condensed File. 122. Calling IDCAMS. 123. Point And Read Full Cond Rec. 124. Point And Read Full Cond Rec. 125. Build Full Cond Rec. 126. Build Full Cond Rec. 127. F164_InsertCDCTsFromList. 128. Taking checkpoint. 129. READ_I/F Close. System Action: User Response: PowerExchange Condense processing continues. If you receive a return code of 1 through 99, us the return code to correct environmental issues. If you receive a return code of 100 through 999, contact Informatica Global Customer Support specifying the reason for the error. PWX-06407 Explanation: System Action: User Response: Condense: Error in action on file_type file. Codes code1,code2,code3. File=file_name. PowerExchange Condense encountered an error while performing action action against the file file_name. Return code information is supplied in the code1, code2, and code3. PowerExchange Condense processing continues. Perform one of the following actions:
If code3 is 0071 on a Windows UNIX or Linux platform, a locking issue might have occurred on a shared file. Eliminate the contention problem and restart PowerExchange Condense. Otherwise contact Informatica Global Customer Support specifying the function being performed at the time of the error. PWX-06408 Explanation: System Action: User Response: PWX-06409 Explanation: System Action: User Response: CCL Writer: CREAD returned invalid record type <record_type> from CreadPublic.RecordType. CREAD returned an error related to the specified record type to the PowerExchange Logger for Linux, UNIX, and Windows. Processing ends. Contact Informatica Global Customer Support. Condense: Full file error. Change type change_type invalid on before_or_after image. A consistency validation on change type change_type and before_or_after image type has failed. PowerExchange Condense processing continues. Contact Informatica Global Customer Support specifying the function being performed at the time of the error.
260
Condense: Full file error. Change type change_type followed by change type change_type. A consistency validation on change types and image types has failed. This error might occur because all updates have been processed. For example, the error might occur if one program updates a database with journaling on followed by another program updating the same keys with journaling off, and then another program updates the database with journaling on.
PowerExchange Condense processing continues. Verify that all updates have been made to the database journals. Sometimes you must register and run a partial condense for the affected tag to see the sequence of updates for the problem key. If the problem persists, contact Informatica Global Customer Support specifying the function being performed at the time of the error.
Condense: type=value. This message logs error information. In the message text:
type is one of the following values: registration tag sequence token restart token value is the value of the specified type. System Action: User Response: PWX-06412 Explanation: System Action: User Response: PWX-06413 Explanation: PowerExchange Condense processing continues. To determine the cause of the error, review associated messages. Condense: Registration Tag=tag This message reports each of the registration tags that the PowerExchange Condense subtask is processing prior to initializing CAPI. PowerExchange Condense processing continues. No response is required. Condense: Highest Restart Token. Sequence=hex PowerExchange Logger=hex This message reports the start point used by the CAPI interface. On a warm start, the values are taken from the ERT record on the checkpoint file, which has a key of all hexadecimal 'FF' characters.
The sequence token defines the value of the last record processed, or binary zeros on a cold start, and only records sequence tokens greater than this value that are processed and written to partial or full condense files. The restart token defines the time when the CAPI system starts accumulating units of work (UOWs). The restart token might precede the sequence token if there were incomplete UOWs when the last Condense job shut down. System Action: User Response: PWX-06414 Explanation: System Action: User Response: PowerExchange Condense processing continues. No response is required. Condense: error_information This message displays general information. PowerExchange Condense processing continues. No response is required.
PWX-06000 to PWX-06999
261
Condense: Condense completed. Total Records=total_records_count, Data=data_count, UOWs =UOW_count This message logs record counts in the last Condense run when the PWX-06417 message was logged. In the message text:
total_records_count is the is the total number of records processed since the Condense activity started, for example, since the PWX-06417 message was logged. If running in Continuous mode, there might be multiple Condense runs before the file is closed by a file switch. data_count is the Data count and is the number of Delete, Insert and Update records. Note: The before image (type T) records are not included in this count. UOW_count is the number of units of work. System Action: PowerExchange Condense processing continues as follows:
If the job is running in batch mode, then the job shuts down. If the job is running in continuous mode, then the Condense task sleeps for the number of minutes defined by the NO_DATA_WAIT parameter. Then, the system performs another Condense. User Response: PWX-06416 Explanation: No response is required. Condense: Shutting down because reason This message logs the reason that the Condense task shutting down. Normal reasons for the shutdown include:
A Single Condense run completed. For example, COLL_END_LOG=1 and the data was exhausted. A SHUTDOWN event was received from another task such as the Command handler through the tasks events table or through the Consumer API EOF return code. Abnormal reasons for shutting down include Data Access problems on the Consumer API. System Action: User Response: Processing shuts down. No response is required if a shutdown was expected, such as when a batch Condense was being run. Otherwise, use this message to diagnose the problem. Condense: Start to Condense because reason The system has started condensing data. In the message text:
reason is one of the following values: initialization complete. First run. CONDENSE Command Received. The user entered this command. no commands received after time period expired. No commands were received after the time period expired.
The Condense tasks start to extract captured data and write it to the condense files. No response is required.
262
Condense: Closed file file_name PowerExchange Condense has closed the specified file. The data is now available to a CAPX DBMOVE or can be viewed through an appropriate program. One of the following actions occur:
If the job is running in continuous mode, PowerExchange Condense processing continues. and the next file switch causes other files to become available for CAPX processing. If the job is running in batch mode, PowerExchange Condense processing shuts down. User Response: PWX-06419 Explanation: No response is required. Condense: Doing file switch. Records=count Reason=reason This message indicates that a file switch occurred. Reason reason is one of the following values:

FILESWITCH request was received from the user through the Command Handler Records criteria met Minutes criteria met 1st EndUOW after previous file switch occurs when the previous partial condense file did not end on a unit of work File switching makes condense files available to CAPX extractions when running in continuous mode, and is accompanied by PWX-06418 messages logging the specific partial and full condense file names. System Action: User Response: PWX-06420 Explanation: PowerExchange Condense processing continues. No response is required. Condense: Checkpoint done. Sequence=hex_value PowerExchange Logger=hex_value This message logs the hexadecimal values of the sequence and restart tokens when a checkpoint completes. This message is accompanied by message PWX-06136, which provides the time of the checkpoint. PowerExchange Condense processing continues. No response is required. Condense: current_time Starting wait on commands for number units This message is logged when the job is running in continuous mode and enters a sleep state between Condenses. The job waits for either the time to expire, or for a command to be passed from the user through the Command Handler task. If waiting is acceptable, no response required. Otherwise, you can wake up PowerExchange Condense processing by using commands such as CONDENSE, FILESWITCH or SHUTDOWN. For more information about these commands, see the PowerExchange Command Reference. Condense: Received FILESWITCH request. A manual FILESWITCH request was received. The Condense task closes the partial and full condense files and add entries for them in the CDCT file so that the data becomes available to a CAPX extraction. PowerExchange Condense processing continues. No response is required.
User Response:
PWX-06000 to PWX-06999
263
Condense: Retention Data creation start_time Reducing count CDCTs, please wait A maintenance operation is starting, it is designed to reduce memory used for retention processing. The process converts data PowerExchange Condense processing continues. No response is required. Condense: Retention Data creation complete end_time Replaced count CDCTs, Created count RETs A maintenance operation has completed. PowerExchange Condense processing continues. No response is required. Condense: Retention Data creation failed For condense_end_time with rc return_code A maintenance operation failed. Processing ends. Review associated messages to determine the cause of the failure. If you cannot resolve the problem, contact Informatica Global Customer Support. CCL Writer: Restart sequence tokens are not ascending: Previous=<token_value> Current=<token_value> The PowerExchange Logger detected that the current sequence token value is not greater than the previous sequence token value, as required. Processing ends. Verify that the restart tokens are valid. Condense: Error: No registrations so initialization aborted. The Condense task received no active registrations to process and aborted. The Condense job fails. Verify that the parameters DBID and DB_TYPE in the capture configuration file are correct. On the Navigator, open the registration Group for this combination of DBID, DB_TYPE and platform and check that there are active registrations. Condense: Too many condense files per time_unit. Sequence 1 file created on date at time. The system cannot safely create a unique file name for a new partial or full condense file because too many files have been created within the time period. The Condense job fails. Set the configuration parameters to produce files less frequently. On MVS, the limit is 999 files per minute. On AS400, the limit is 9999 files per day.
264
Condense: Full file: Key Length=key_length Hashed Ind=hi_hex Synonym=counter tag=registration_tag. This message logs information about the key of a full condense file. In the message text:

key_length is the total lengths of all columns that form the key. hi_hex is the hexadecimal hashed index. counter is the synonym counter. registration_tag is the capture registration tag. If the key_length does not exceed 200, then the hashed index is set to 00 and the synonym counter is set to -1; there are no synonyms. If the key_length exceeds 200, then the hashed index is set to FF and the synonym counter is set to -2 for the first synonym and -3, -4, and so on for subsequent synonyms. Column data is reduced to 200 bytes; this action produces a key that is the same as an existing record with different column data. System Action: User Response: PWX-06432 Explanation: Processing ends. See the associated messages for the reason for the error. Condense: Full file: type Key=column_data. This message logs information about the key of a full condense file. The type can take values of hashed and column. The hashed key is used on the indexed full condense file and has a maximum length of 200 bytes. The column key is the true data and is only displayed if hashing was used. Processing ends. See the associated messages for the reason for the error. Condense: Change type sequence error. before=change_type after=change_type incoming=change_type. An invalid sequence of change types was met. Change types can be one of the following types:

D. delete. I. insert. T. before image of an update. U. after image of an update. Z. no change type affecting this before or after image. System Action: User Response: Processing ends. Verify that all updates are on the database journals. Sometimes it is necessary to register and run a partial condense for the affected tag to see the sequence of updates for the problem key. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Full File error - validation of incoming updates: error_information. An error occurred while processing the Full Condense file. Processing ends. This message is issued if an inconsistent sequence of update records are encountered for the same record key - for example multiple sequential inserts without an intervening delete. It is possible that a file was restored and updates rerun, thereby capturing the same updates twice. Verify that this is not the case. If all fails, contact Informatica Global Customer Support and provide all error messages.
PWX-06000 to PWX-06999
265
Condense: Deleting CDCT record. PEV_post_interested on event=event (event_name). Return code=return_code. An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Deleting CDCT record. storing restart in ERT for EdmName=(edmname). Return code=return_code An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Deleting CDCT record. Getting true key Incoming registration tag=tag change type=type Return code=return_code An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Deleting CDCT record. GetTrueKey registration tag=tag synonym=synonym image=image Return code=return_code An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Deleting CDCT record. Full BA Validation Incoming changetype=changetype Return code=return_code An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Deleting CDCT record. posting event=event (event_name) Return code=return_code An error occurred with information in description and return code. Processing ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Condense: Flush for file <file_name> failed. Return code = <system_return_code>: <reason_for_failure> An attempt to flush records to the specified file failed. The condense process fails.
266
User Response:
Fix the problem described in the message and restart the condense process. This problem usually indicates either an out-of-space condition or an I/O error. FS: R=recordsreason C=CDCTcount CPUms(so_far,delta) Files(list_of_files_with_type) CKPT(version,datetime) S=sequence,L=logger This is a none verbose message, which covers a complete file switch. More information is given in the full messages this replaces 6419, 6418, 6136, and 6420 for file switches. Note that the file list for flexible condense is in the sequence the group parameters were presented and not creation sequence. This is a non verbose Audit trail, PowerExchange Condense processing continues. No response is required. A_list_of_wait_condense_cycles This is a none verbose message, which covers a period of condensing and waiting as facilitated by continuous mode condense. A wait is shown as 'W' for wait number for wait units and unit prefix for (seconds, minutes or hours. If this is followed by an 'I' the wait was interrupted. A condense is shown as 'C' followed by statistics (see message PWX-06415) when condense completes. More information is given in the full messages this replaces PWX-06421, PWX-06417, and PWX-06415. This is a non verbose Audit trail, PowerExchange Condense processing continues. No response is required. Data missing for period_ending CDCT registration tag <tag> summary_line The data on the checkpoint shows we are missing this range of data on the CDCT. Due to the volume of data required to keep this data we can no longer reinstate the resource. The data available is limited to retention requirements. This is a summary of missing resources, PowerExchange Condense processing continues. Use to investigate loss. Missing condensed data accepted A reply of Y was received from the confirmation request that Missing condensed data is acceptable. PowerExchange Condense processing continues. No response is required. Missing condensed data declined A reply of N was received from the confirmation request that a Missing condensed data is acceptable. Processing ends. No response is required. There are missing resources, these can not be recovered. Continue (Y/N) On MVS, this message is used in a WTOR prompt that requires a reply of Y or N to confirm that it is acceptable that the resources absence is satisfactory. The resources were summarized in previous messages. This could arise if data retention was extended and condense was restarted with a checkpoint from before the change in data retention. The system waits for the reply to the WTOR. Reply either Y or N to the WTOR if it is acceptable that the resources are missing.
PWX-06000 to PWX-06999
267
PWX-06450 Explanation: User Response: PWX-06451 Explanation: User Response: PWX-06452 Explanation: System Action: User Response: PWX-06453 Explanation: User Response: PWX-06454 Explanation: User Response: PWX-06455 Explanation: User Response: PWX-06456 Explanation: System Action: User Response: PWX-06457 Explanation: System Action: User Response: PWX-06458 Explanation: System Action: User Response: PWX-06459 Explanation: System Action: User Response:
Command Handler: Starting. The command handle task is starting. No response is required. Command Handler: WARNING There are new events not included. Internal checking error. Contact Informatica Global Customer Support, including the error code issued. Command Handler: Error in CMDH PEV_post_interested. ret=<return_code>. Command handler task failed to post an event. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: shutting down. The command handler task is ending. No response is required. Command Handler: has stopped. The command handler has ended. No response is required. Command Handler: received CAPTURE_STARTUP_COMPLETE event. Capture startup was completed. No response is required. Command Handler: File Switch already requested. A file switch was requested previously. Ignore the last file switch request. Wait for the completion of the initial file switch. Command Handler: Startup Incomplete. A file switch was requested and the system still starting up. Ignore the file switch request. Wait for the startup completion before requesting a file switch. Command Handler: CEEDMP not supported on AS400. A CEEDMP was requested in an AS400 platform where it is not supported. Ignore the request. No response is required. Command Handler: Closing after RC=%d from WaitForCapiCommand Command handler received an error while waiting for a CAPI command. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued.
268
PWX-06460 Explanation: System Action: User Response: PWX-06461 Explanation: System Action: User Response: PWX-06462 Explanation: System Action: User Response: PWX-06463 Explanation: System Action: User Response: PWX-06464 Explanation: System Action: User Response: PWX-06465 Explanation: System Action: User Response: PWX-06466 Explanation: System Action: User Response: PWX-06467 Explanation: User Response: PWX-06468 Explanation: System Action: User Response:
Command Handler: New File Switch requested. A new file switch was requested. A file switch will occur shortly. No response is required. Command Handler: New File Switch requested. CONDENSE request generated. A new file switch was requested, a CONDENSE will happen. A CONDENSE process will happen as a result of the file switch request. No response is required. Command Handler: Close Condense request already queued. A close condense command was already queued. Ignore the new close command as the previous one is in progress. Wait for the close to happen. Command Handler: Close Condense request is now queued. A close condense command was queued. A close condense will occur shortly. Wait for close to happen. Command Handler: Shutdown will occur shortly. Shutdown will occur shortly. A shutdown will occur shortly. Wait for shutdown to happen. Command Handler: Shutdown will occur after Condense can write checkpoint files. A shutdown was requested but there is a condense running. Shutdown will happen after a checkpoint. A shutdown will occur after a checkpoint. Wait for shutdown to happen. Command Handler: ERROR: CAPI_Connect unsuccessful for CAPICMD. An error happened when trying to do a CAPI_CONNECT. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: Setting Condense to shut down on running out of data. A condense is started after capturing all the available data. No response is required. Command Handler: Condense request issued. A condense command was queued. A condense process is started. No response is required.
PWX-06000 to PWX-06999
269
270
Command Handler: PEV_express interest on event=event_number (event_name) rc=return_code. An error occurred when the command handler was expressing interest in an event. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: ERROR: CAPI_RestartInit unsuccessful for CAPICMD. An error occurred when the command handler was trying to get a restart token. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: ERROR: CAPI_SetRestartInfo unsuccessful for CAPICMD. An error occurred when the command handler was trying to set some restart info. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: ERROR: CAPI_Open unsuccessful for CAPICMD. An error occurred when the command handler was trying to do a CAPI_Cpen. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: ERROR: CAPI_SendRestartInfo unsuccessful for CAPICMD. An error occurred when the command handler was trying to do a CAPI_Send. The command handler task ends. Contact Informatica Global Customer Support, including the error code issued. Command Handler: ERROR: Waiting aborted. RC=return_code from examine_and_wait_on_stimer While the command handler was waiting for an event, an error occurred. The command handler task ends. Contact Informatica Global Customer Support with the return code for the error. Command Handler: Received CAPI_EOF from /P jobname. A SDSF /P jobname was issued. The command handler task ends. No response is required. Command Handler: Issuing all tasks shutdown to ensure condense is closed. A SDSF /P jobname was issued. A shutdown command is issued to ensure that condense is closed. Shutdown will happen. No response is required. Command Handler: ERROR: Unexpected CAPI_Read RC=return_code. Unexpected return code from CAPI_Read.
The command handler task ends. No response is required. Command Handler: ERROR: Waiting aborted. Unexpected return from a CAPI call. The command handler task ends. No response is required. Command Handler: ERROR: Unexpected CAPI record type=etype (record_type) from CAPI_Read Unexpected record type return from a CAPI call. The command handler task ends. Contact Informatica Global Customer Support, including the record type returned. Command Handler: RC=return_code from CAPI_GetData. Error calling CAPI_GetData. The command handler disregards the command. No response is required. Command Handler: WARNING: Continuing with NULL command string. Error calling CAPI_GetData. The command handler disregards the command. No response is required. Command Handler: Closing down CAPI interface. Interface to CAPI is closing down. Closing down CAPI. No response is required. Command Handler: CAPI_Close RC=return_code. Executing CAPI_Disconnect. CAPI_Close executed with return code = rc. Disconnections from CAPI. No response is required. Command Handler: CAPI_Disconnect RC=return_code. CAPI_Disconnect executed with return code = rc. Disconnections from CAPI. No response is required. Condense: Display Status Request Received A user request to display the status of the condense process was received. Processing continues. No response is required.
PWX-06000 to PWX-06999
271
PWX-06487 Explanation: System Action: User Response: PWX-06488 Explanation: System Action: User Response: PWX-06490 Explanation: User Response: PWX-06491 Explanation: User Response: PWX-06492 Explanation: System Action: User Response:
Command Handler: Error notifying command handler of FILESWITCH request. RC = return_code. The system could not notify the command handler of a user-specified FILESWITCH request. The command handler task ends. Contact Informatica Global Customer Support, including the return code value. Command Handler: Error notifying command handler of DISPLAY STATUS request. RC = return_code. The system could not notify the command handler of a user-specified DISPLAY STATUS request. The command handler task ends. Contact Informatica Global Customer Support, including the return code value. Dump: starting. Capture dump task is starting. No response is required. Dump: ending. Capture dump task is ending. No response is required. Dump: RC=return_code from action on event eventnumber. An error happen in an PEV call. DUMP task ends. Contact Informatica Global Customer Support, including the return code, action and event number. Dump: Table table_name is empty. The table to dump is empty. No response is required. Dump: task is waiting for an event. The dump task is waiting for an event. No response is required. Dump: task got an event event_num=event_num. DUMP task got an event. No response is required. Collection started without registration information. No registrations have been initialized. There might be some other messages. This is likely to be configuration or the request. Initialization is ended and the request fails. Investigate underlying cause in associated messages to find reason.
PWX-06493 Explanation: User Response: PWX-06494 Explanation: User Response: PWX-06495 Explanation: User Response: PWX-06705 Explanation: System Action: User Response:
272
CPT consistency check open error return_code (AS400 capture). The request SELECT LAST_ALTERED_TIMESTAMP FROM qsys2.systables has failed to open for the table currently being initialized for collection. Security or naming are likely causes. Initialization collection is ended and the request fails. Investigate underlying cause in associated messages to find reason. CPT consistency check describe error return_code (AS400 capture). The request SELECT LAST_ALTERED_TIMESTAMP FROM qsys2.systables has failed to describe for the table currently being initialized for collection. Security or naming are likely causes. Initialization collection ends and the request fails. Investigate underlying cause in associated messages to find reason. System information missing for table table_name schema schema_name (AS400 capture). The request SELECT LAST_ALTERED_TIMESTAMP FROM qsys2.systables has failed to find the table currently being initialized for collection. Naming or setup are the likely causes. Initialization collection is ends and the request fails. Verify names and identities. System information error for table table_name schema schema_name (AS400 capture). The request SELECT LAST_ALTERED_TIMESTAMP FROM qsys2.systables has failed for the table currently being initialized for collection. Security or naming are likely causes. Initialization collection ends and the request fails. Investigate underlying cause in associated messages to find reason. Registration LAST_ALTERED_TIMESTAMP current LAST_ALTERED_TIMESTAMP (AS400 capture). This is a supporting message showing the last altered timestamp for the database at registration and as found by the initialization process. It use is to highlight the dates associated with a problematic change to the database. See the associated messages. See the associated messages. CPT build open error return_code schema_name.table_name (AS400 capture). The request SELECT * FROM schema_name.table_name has failed to open for the table currently being initialized for collection. Security or naming is likely causes. Initializationcollection ends and the request fails. Investigate underlying cause in associated messages to find reason. CPT build describe error return_code (AS400 capture). The request SELECT * FROM schema_name.table_name has failed to open for the table currently being initialized for collection. Security or naming are likely causes. Initializationcollection ends and the request fails. Investigate underlying cause in associated messages to find reason.
PWX-06000 to PWX-06999 273
CPT build close error (return_code).return_code1.return_code2.return_code3 (AS400 capture). The request SELECT * FROM schema_name.table_name has failed to close for the table currently being initialized for collection. Security or naming are likely causes. Initializationcollection ends and the request fails. Investigate underlying cause in associated messages to find reason. Table schema_name.table_name Field column_name missing (AS400 capture) The table was registered with a column, which is no longer present. Message PWX-06710 is also produced for information. Initializationcollection ends and the request fails. Investigate change to table and fix as necessary before restarting. Table schema_name.table_name Field column_name changed (AS400 capture) An attribute of the column has changed. Message PWX-06716 is also produced for the problem. Message PWX-06710 is also produced for information. See the associated messages. See the associated messages. Field attribute was registered_value is now current_value.(AS400 capture) The reported change in the field as detailed in message PWX-06715 by changes identified on message PWX-06710 means the results of collection are unpredictable. Initializationcollection ends and the request fails. Investigate change to table and fix as necessary before restarting. Memory for usage size bytes could not be allocated. (AS400 Capture). Memory allocation error. Initializationcollection ends and the request fails. Investigate if task was running in adequate memory. If the problem persists Contact Informatica Global Customer Support. Overflow error fieldlength of data extracted maxlength allowed.(DB2 capture) This supports another error. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. Collector now active hex restart token (AS400 Capture) This message records the starting position. Prints the restart token. Only needed for information purposes but might be of use if something was missed out of restart. Warning source rtype Journal_entry_type (AS400 Capture). This message warns that an unknown journal entry was encountered from the source specified. Prints warning.

274
Contact Informatica Global Customer Support if notifying a possibly associated error. UOW maintenance failure switch trace name level on.(AS400 capture) Commitment control information is corrupt in memory. Collection ends and the request fails. Unless extra trace information was output restart at a suitable point with trace=(name,level,99) to get diagnosis information. Contact Informatica Global Customer Support with information. Error/Warning no start of UOW timestamp found processing commit cycle entry_type_Is_start_rba_good.(AS400 capture) For an error, collection was started in the middle of a unit of work, which includes updates to be collected. For a warning, collection was started in the middle of a unit of work. For error, collection ends and the request fails. Establish the correct restart point and set it using the restart utility. Table schema_name.table_name insert string error.(AS400 capture) A problem was encountered when extracting and formatting an insert for the table. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. Table schema_name.table_name delete string error.(AS400 capture) A problem was encountered when extracting and formatting a delete for the table. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. Table schema_name.table_name undo string error.(AS400 capture) A problem was encountered when extracting and formatting an undo string for an update for the table. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. Table schema_name.table_name redo string error.(AS400 capture) A problem was encountered when extracting and formatting a redo string for an update for the table. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. Error attempting to find pending insert for journal_code/entry_type of registration_name. (AS400 Capture). A redo string has failed to find an associated undo string for the specified registration. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors.
PWX-06000 to PWX-06999
275
Error missing internal column columnnum of indexdown. (DB2 Capture). This supports another error. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. No records found in PowerExchange Data Capture Control File file_name. The AS400 controller job was submitted without any Change Data Capture Registrations having been made against the Database Identifier parameter (DBID = XXXX) in file datalib/cfg(captparm). The AS400 controller job ends. Ensure that any registrations have been made against the correct Database Identifier, if any have been made, otherwise enter new registrations. Error resolving to user queue name. Reason error code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the user queue and the error code issued from the error message. Error retrieving job information. Reason error_code - description. An internal error occurred while attempting to retrieve job information. The AS400 Journal Processing task that encountered the error checks to see if it can proceed with the processing. If it cannot, processing ends. Contact Informatica Global Customer Support, including the error code issued. Error sending data to user queue <library/queue_name>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the queue and the error code issued. Error error_code user index <user_index>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the user index and the error code issued. Error reading data area <library/data_area>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the data area and the error code issued. Error changing data area <library/data_area>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends.

276
User Response:
Contact Informatica Global Customer Support, including the name of the data area and the error code issued. Error retrieving user index entry from <user_index>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the user index and the error code issued. DTLAS4JE submitted beyond PowerExchange scope. Job terminated. An attempt was made to execute a PowerExchange AS400 Journal Processing task outside of the control of a PowerExchange Controller task. The AS400 Journal Processing task that encountered the error ends. ALL PowerExchange AS400 Journal Processing tasks MUST be executed under the control of a PowerExchange Controller Task. Any attempts to manually execute the task are explicitly prohibited. The user should refrain from any attempts to manually execute the task. AS400 User Message Queue The AS400 User Message Queue (AS400USRMSGQ=XXXXXXXXXX) option in file datalib/cfg(dbmover) has an invalid value. This is detected at the start of the PowerExchange Listener task. The PowerExchange Listener task ends issuing error message DTL00964. Correct the value in the configuration file, or remove the entry to default to the system operator message queue (QSYSOPR). Error sending message to user <user_ID>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the user and the error code issued. Error receiving message from user <user_ID>. Reason reason_code. An internal error occurred while processing entries from a journal receiver. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the name of the user and the error code issued. Error converting date. Reason error_code - description. An internal error occurred while attempting to convert a date. The AS400 Journal Processing task that encountered the error checks to see if it can proceed with the processing. If it cannot, processing ends. Contact Informatica Global Customer Support, including the error code issued.
PWX-06000 to PWX-06999
277
Error retrieving journal lock file PWXJRNLCKP. Reason error_code - description. An internal error occurred while attempting to retrieve the location for the journal lock file PWXJRNLCKP. The AS400 Journal Processing task that encountered the error ends. Contact Informatica Global Customer Support, including the error code issued. AS400 Condensed Files Library Name Parameter COND_DIR is not present in *LIBL/CFG(CAPTPARM). This parameter is mandatory on AS400 Condenses. The Condense job ends Perform the following actions: 1. Ensure that the library list is set up correctly so that file CFG and member CAPTPARM are picked up. 2. Edit member CAPTPARM in file CFG and ensure that COND_DIR is set to the library where partial and full condense files are to be written.
AS400 Capture Data Maps Library Name A problem was encountered with parameter CPX_DIR in the CFG file The task ends Edit the CPX_DIR parameter to ensure that it defines a valid entry. CPX_DIR is an optional parameter used to define the AS400 library where capture maps are stored. The parameter should not be used on other platforms. CAPI_CONN_NAME A problem was encountered with parameter CAPI_CONN_NAME in the CFG file The task ends Edit the CAPI_CONN_NAME parameter to ensure that it defines a valid entry that matches a NAME on a CAPI_CONNECTION parameter used by the Data Capture system when running Condenses or CAPXRT extractions. If not present, the parameter defaults to CAPIEDP. parameter optional_parameter parameters missing (AS4J) Some of the instance and journal are missing from the CAPI Connection in the configuration, PowerExchange data library/CFG(dbmover). Collection ends and the request fails. Correct the connection information and retry. No files associated to journal journal_identity expected <requested_number> (AS4J) The request related to the stated journal but no files are journaled to it. Collection ends and the request fails. Correct the connection information and retry. <count> files associated to journal journal_identity expected <requested_number> (AS4J) The request related to the stated journal but insufficient files are journaled to it. Collection ends and the request fails. Correct the connection information or request and retry.
278
<internal_journal_ID> journals associated to restart token expected none DIR (AS4J) A restart token associated with processing a dedicated merged journal was supplied when direct processing was requested. These are not compatible. The internal journal ID is expected to be zero. Collection ends and the request fails. Correct the connection information, request or restart point and retry. file <schema_name.table_name> not associated to journal journal_identity as expected (AS4J) The resource identified is not currently journaled to the supplied journal. Collection ends and the request fails. Correct the connection information or request and retry. Error outside commitment control description of issue and journal identity(AS4J) This is one of a pair. The problem only occurs processing update pairs outside commitment control. The reason two messages are supplied is generally that an after image failed to follow a before image. The messages describe what the status is and what was expected. Collection ends and the request fails. Contact Informatica Global Customer Support with associated errors. error/warning user identity action of/for resource_at_timestamp(AS4J) In the message text, action is one of the following values:
changed format of. Error with associated messages. stopped journaling for. Warning. started journaling for. Warning. deleted. Error. moved. Error. renamed. Error. System Action: User Response: PWX-06779 Explanation: System Action: User Response: PWX-06780 Explanation: System Action: User Response: PWX-06781 Explanation: For a warning the record is ignored. For an error collection ends and the request fails. Correct the connection information or request and retry. Table schema_name.table_name Extra field column_name unregistered (AS400 capture) All columns are to be collected and this is the notification of an unregistered column. Collection ends and the request fails. Correct the database or registration and retry. Override for Table format issue Internal registration tag <overridden_tag> (AS400 capture) The registration used to pass the overrides could not be understood as the format seems to be missing a separator. Collection ends and the request fails. Contact Informatica Global Customer Support. Override for Table (library/file) collection using registration registration_name (AS400 capture) Record of the override file for a registration.
PWX-06000 to PWX-06999
279
System Action: User Response: PWX-06782 Explanation: System Action: User Response: PWX-06783 Explanation: System Action: User Response: PWX-06784 Explanation: System Action: User Response: PWX-06785 Explanation: System Action: User Response: PWX-06786 Explanation: System Action: User Response: PWX-06787 Explanation:
This message provides an audit trail. Only for information on the overrides being processed. <override_data> is wrong length for an override name The override parameter given fails a basic length test. Collection ends and the request fails. Correct the request. Then, try the request again. <override_data> is wrong length for an override name attribute qualifier The override parameter given fails a length test on the described sub field. Collection ends and the request fails. Correct the request. Then, try the request again. <override_data> has too many separators for an override name The override parameter given fails a test on the number of separators exceeding one. Collection ends and the request fails. Correct the request. Then, try the request again. Error no Instance supplied in CAPI connection (AS400 capture). The instance connection parameter was not supplied. Collection ends and the request fails. Correct the configuration and retry. Error multiple STOPIT connection parms condition1 & condition2 (AS400 capture). The stopit connection parameter occurred twice; this is a conflicting request needing user correction. Collection ends and the request fails. Correct the configuration and retry. Error library/file not journaled for before images (AS400 capture). The request for collection is against a file that does not have journaling set up for it with before images. Before images are used with after images to collect data for both deletes to identify the deleted record and updates not to pass on null updates where this can be identified. Collection ends and the request fails. Correct the request or set the journaling correctly and retry. Error CLRPFM used by AS400 job identity on library/file prevents processing by AS400 capture. The file registered for collection was cleared using the AS400 CLRPFM command. Clearing a file in this manner only writes a single journal entry and provides AS400 capture with no means of identifying the actual records deleted from the file. Collection ends and the request ends. This file requires a new restart token that is after this incident. The user should ensure that NO files registered for collection are cleared in this manner.
280
PWX-06789 Explanation: System Action: User Response: PWX-06790 Explanation: System Action: User Response: PWX-06791 Explanation: User Response: PWX-06792 Explanation: System Action: User Response: PWX-06793 Explanation: System Action: User Response: PWX-06794 Explanation:
Error No data for Delete of library/file (AS400 capture). PowerExchange Condense needs before images in order to pass information about deletions. PowerExchange Condense processing ends. This file must be restarted. Error No before data for update of library/file (AS400 capture). PowerExchange Condense needs before images to determine if any changes exist for registered columns. PowerExchange Condense processing ends. This file must be restarted. desc<value> : desc<value> Support data. Continuation of messages PWX-06789 and PWX-06790. No response is required. Override for collection Journal (jmlid) from parameter jrnlparm (AS400 capture) Record of the override file for a journal. This message provides an audit trail. Only for information on the overrides being processed. ErrorToken building did not expect microseconds microseconds. The token building process only expects whole seconds. Processing fails. Contact Informatica Global Customer Support. Error receiver chaining issue to next_receiver from last_receiver expected to next_receiver from previous. Receiver chaining processing has broken down. This is critical to collection. The second pair of receivers in the message are as reported by the system on a list of receivers associated with the journal. Processing fails. Determine if journal maintenance is the cause of the error. Otherwise, contact Informatica Global Customer Support. Changing journal receiver to <next_receiver> at <sequence_number>. This message displays the audit trail for start of receiver changes. Audit trail if needed. Changed journal receiver from <last_receiver> to <current_receiver> at <sequence_number>. This message displays the audit trail for end of receiver changes. Audit trail if needed.
PWX-06795 Explanation: User Response: PWX-06796 Explanation: User Response:
PWX-06000 to PWX-06999
281
Error receiver next_receiver missing from chain ending last_receiver from previous. Receiver chaining processing has broken down. This is critical to collection. The second pair of receivers in the message are the latest as reported by the system on a list of receivers associated with the journal. There is no matching receiver. Processing fails. Determine if journal maintenance is the cause of the error. Otherwise, contact Informatica Global Customer Support. Error Changed journal receiver format issue to <next_receiver>length expected <expected_receiver>. Error receiver change format errors. Processing fails. Review the message. Contact Informatica Global Customer Support. Error previous receiver previous_receiver unexpected on change to current_receiver from previous. Receiver chaining processing has broken down. This is critical to collection. The second pair of receivers in the message are the last processed and the current presumed journal. There is no backward matching receiver for the previous one read. Processing fails. Determine if journal maintenance is the cause of the error. Otherwise, contact Informatica Global Customer Support. Error On Checkpoint deleting file rc error. Checkpoint could not delete oldest checkpoint file. Processing fails after optional operator message and retries. Contact Informatica Global Customer Support. Error On Checkpoint creating file rc error. Checkpoint could not create next checkpoint file.
Note: MVS only As a checkpoint is created after a delete in some cases that delete might
have failed in a way that was indistinguishable from a not found at the return code level. This means there is a risk of this relating to a delete failure. System Action: User Response: PWX-06805 Explanation: Processing fails after optional operator message and retries. Contact Informatica Global Customer Support. AS400 Event Message Queue The value entered for the AS400EVENTMSGQ parameter in the DBMOVER configuration file is invalid. This error is detected at the start of the PowerExchange Listener task. The PowerExchange Listener task ends. Correct the value of, or remove the entry for, the AS400EVENTMSGQ parameter in the DBMOVER configuration file to disable AS400 event message processing. Error sending message to message queue <message_queue>>. Reason reason_code - reason_description. When a message was being sent to the AS400 Event Message Queue, an error occurred.
282
The task continues. Contact Informatica Global Customer Support. Object object_name type object_type not found. When the existence of an object was being verified, an error occurred. The task ends. Contact Informatica Global Customer Support. CLRPFM command issued by AS400 job identify on library/file ignored by DB2 for AS400 capture because ALWCLRPFM=Y specified. An i5/OS job issued a Clear Physical File Member (CLRPFM) command to remove all data, including deleted records, from the specified physical file. This file is registered for DB2 for i5/OS change data capture (CDC). However, PowerExchange CDC cannot capture CLRPFM changes. Because the ALWCLRPFM parameter is set to Y on the AS4J CAPI_CONNECTION statement in the DBMOVER file, PowerExchange ignores the CLRPFM command instead of stopping CDC processing. The ALWCLRPFM parameter should be specified only at the direction of Informatica Global Customer Support because it can cause data integrity problems on the target. PowerExchange ignores the CLRPFM changes and continues CDC processing. Determine if the ignored CLRPFM changes caused data integrity problems on the target. If data integrity was damaged, correct the target, as needed, to restore data integrity. Error type token length received wrong expected value_description. Token conversion received a token of incorrect length. Processing fails. Verify that the token is correct. Otherwise, contact Informatica Global Customer Support. Error type token conversion error rc return_code. Token conversion failed for specified token or section of token. Associated messages should identify problem. The request fails. Resolve problem and retry. Error could not associate timestamp timestamp sequence sequence_number to a receiver associated to journal. The token conversion process could not find the journal entry on any known receiver. The process looks backward though the journals to find the first receiver attached before the specified journal entry timestamp. The journal sequence number should be in the range first to last, but is not. The timestamp and sequences in the restart token do not match any in the journal receivers available to the process for one of the following reasons:
Date manipulation, dates, and sequences have been reset for receivers that are no longer available to this process. Journal receivers have been deleted and the restart token timestamps and sequences belong to receivers that are no longer available to this process. The CAPTPARM member points to different journals from those present when checkpoint was taken. System Action: Processing fails.
PWX-06000 to PWX-06999
283
No response is required. Error choice receivers for timestamp timestamp sequence sequence_number, receiver and receiver are possible. Token conversion found two possible journal entries on known receivers. Processing fails. The process looks backward though the journals to find the first receiver attached before the journal entry timestamp given in the message. Because of time and sequence changes at least the two given receivers are possible. The process cannot safely decide between these. This conversion is to avoid this lack of uniqueness, but it cannot cure the problem retrospectively. The cause of this could be date manipulation, dates, and sequences have been reset for receivers, which means a time sequence pair could be in more than one receiver. Error building CCT entry open error return_code with request_type. The request given in the message has failed to open for the table currently being initialized for collection. Security or naming are likely causes. Initialization of collection ends and the request fails. Investigate underlying cause in associated messages to find reason. Error building CCT entry describe error return_code with request_type. The request given in the message has failed a describe for the table currently being initialized for collection. Security or naming are likely causes. Initialization of collection ends and the request fails. Investigate underlying cause in associated messages to find reason. CPT consistency check close error return_code (IMS capture). The request given in the message has failed to close for the table currently being initialized for collection. Security or naming are likely causes. Initialization of collection ends and the request fails. Investigate underlying cause in associated messages to find reason. CPT build describe error return_code request_type (IMS capture). The request given in the message has failed a describe for the table currently being initialized for collection. Security or naming are likely causes. Initialization of collection ends and the request fails. Investigate underlying cause in associated messages to find reason. Initialization failed waiting termination.(IMS capture) Initialization cannot continue see associated messages. Initialization of collection ends and the request fails. Investigate underlying cause in associated messages to find reason. IMS close failure RC return_code . (IMS Capture) The request given in the message has failed to close for the table currently being initialized for collection. Security or naming are likely causes. Initialization of collection ends and the request fails.
284
Investigate underlying cause in associated messages to find reason. CCIMT: SLDS data set data_set_name is of interest but marked as LOGERR The specified IMS SLDS data set is of interest for change data capture. However, the data set entry in the PRISLDS log of the IMS RECON data set indicates that the data set is in error. The IMS log-based ECCR reads the corresonding data set entry in the SECSLDS log, if available. No response is required. Compressed SLDS entry with Start time=time_stamp ignored The IMS log-based ECCR found a data set entry with the specified start time and the data set name of "COMPRESSED DATA SET" in the PRILOG or SECLOG records or the PRISLDS or SECSLDS records of the RECON data set. The ECCR cannot identify a data set based on this data set name. The IMS log-based ECCR ignores the compressed data set when capturing changes. No response is required. IMS SECLOG not found. RECON key=hexadecimal_value In the IMS RECON data set, the IMS log-based ECCR did not find a SECLOG record of type x'09' that has the specified key value. The corresponding PRILOG record indicates that the data set is in error. Because the ECCR cannot find a valid data set entry in either the PRILOG or SECLOG, the ECCR job ends abnormally with a return code greater than 4. Verify that your IMS database is configured to use SECLOG recovery logs. If so, check the SECLOG records in all of the RECON data sets to find the record with the specified key. IMS SECDSE in error DSE=data_set_name A data set entry in the SECLOG or SECSLDS log of the IMS RECON data set indicates that the specified log data set is in error. The corresponding data set entry with the same start time in the PRILOG or PRISLDS log also indicates that the log data set is in error. Because the IMS log-based ECCR cannot find a valid data set entry in either the primary log or secondary log of the RECON data set, the ECCR job ends abnormally. To identify the data set that is marked as in error in the PRILOG or PRISLDS log, use the IMS LIST.LOG command. Then try to repair at least one of the data sets that are marked as in error in the primary and secondary logs. IMS SECDSE not found for PRIDSE=data_set_name In the SECLOG or SECSLDS log of the RECON data set, the IMS log-based ECCR did not find a data set entry with a start time that matches the start time of the specified data set entry in the PRILOG or PRISLDS log. The PRILOG or PRISLDS data set entry indicates that this data set is in error. Because the ECCR did not find a valid data set entry in the primary or secondary logs, the ECCR job ends abnormally. Try to repair the data set that is marked as in error in the PRILOG or PRISLDS.
PWX-06000 to PWX-06999
285
IMS SECSLDS in error. DSN=data_set_name A SECSLDS data set entry in the RECON data set indicates that the specified SLDS data set is in error. The corresponding PRISLDS entry with the same start time also indicates that the data set is in error. The IMS log-based ECCR job ends abnormally. To identify the data set that is marked as in error in the PRISLDS log, use the IMS LIST.LOG command. Then try to repair at least one of the data sets that are marked as in error in the PRISLDS and SECSLDS logs. IMS SECSLDS not found for in error PRISLDS. RECON key=hexadecimal_value In the SECSLDS log of the RECON data set, the IMS log-based ECCR did not find a SECSLDS record of type x'47' that corresponds to the PRISLDS record with the specified key value. The PRISLDS data set entry indicates that the data set is in error. Because the ECCR did not find a valid data set entry for the SLDS data set in either the PRISLDS or SECSLDS, the ECCR job ends abnormally. To identify the data set that is marked as in error in the PRISLDS, use the IMS LIST.LOG command. Then try to repair the data set. CCIMT: ECCR starting at IMS log time time_stamp (YY/MM/DD HH:MM:SS). At startup, the IMS log-based ECCR begins reading change data from the point in the SLDS logs that corresponds to the specified time stamp. The ECCR processes changes. No response is required. (Capture) Please confirm cold start? (Y/N) Capture has no restart point and requests agreement to a Cold start. Waits for operator response. Enter Y or N to the message. ECCR Abnormal end: reason Capture shutdown abnormally. Processing ends. Review PowerExchange and system logs for other messages. CCIMT:(ECCR ECCR_name)IMS Log data_set_name - start hextime time end hextime time is unusable. This message is issued if the ERROR_LOG=WTOR option is chosen. The IMS log identified in the message is in error. This depends on choice made in the next message. Run IMS recovery to correct the log and rerun. CCIMT:(ECCR ECCR_name)Please enter one of the following options: ABEND/WAIT/SKIP This message is issued if the ERROR_LOG=WTOR option is chosen. The IMS log identified in the previous messages is in error. The system action is determined by the user response:
PWX-06967 Explanation: System Action: User Response: PWX-06970 Explanation: System Action: User Response: PWX-06971 Explanation: System Action: User Response: PWX-06973 Explanation: System Action: User Response: PWX-06974 Explanation: System Action:
ABEND. The IMS ECCR ends. WAIT. The IMS ECCR waits and retries, allowing the error log to be corrected.
SKIP. The IMS ECCR skips the log in error and continues.
User Response:
Informatica recommends the WAIT option. Run IMS batch backout to correct the log.

ABEND. Stop the IMS ECCR. WAIT. Wait and retry, allowing the error log to be corrected. SKIP. Skip the log in error. This option is not recommended, as the skipped log file cannot ever be reprocessed. Unless you are sure that the log file will never be corrected using batch backout, do not choose this option. PWX-06975 Explanation: CCIMT:(ECCR ECCR_name)Confirm you wish to PERMANENTLY skip this log file: reenter SKIP This message is issued if the ERROR_LOG=WTOR option is chosen. The IMS log identified in the previous messages is in error. The operator choose action SKIP in response to previous messages. The system action is determined by the user response:
SKIP. Skip the log in error and continue. This option is not recommended.
Enter SKIP if you want to skip this log. CCIMT:(ECCR ECCR_name)IMS Log data_set_name is SKIPPED due to ERROR_LOG=SKIP or Operator Action. This message is issued if the ERROR_LOG=SKIP option is chosen or ERROR_LOG=WTOR option is chosen and the operator chooses the SKIP option. The IMS log identified in the message is in error. The IMS ECCR continues without processing the skipped log. This log is now permanently skipped. No response is required. CCIMT:(ECCR ECCR_name)IMS ECCR will wait for the error log to be corrected and retry. This message is issued an error log is encountered and ERROR_LOG=WAIT is chosen. It is also issued if ERROR_LOG=WTOR was chosen and the operator chose to WAIT. Wait and retry, allowing the error log to be corrected. No response is required. CCIMT:(ECCR ECCR_name)IMS ECCR will terminate due to log in error This message is issued an error log is encountered and ERROR_LOG=ABEND (default) is used. It is also issued if ERROR_LOG=WTOR was chosen and the operator chose to ABEND. Processing ends. No response is required. CCT used by collector does not match Agent cache used by PowerExchange Logger. Changes were found for a capture registration defined to the ECCR. However, when these changes were reported to the PowerExchange Logger, the Agent cache that is used by the PowerExchange Logger did not have a record of this registration. ECCR ends with an error. Check that DTLAMCPR in the repository PowerExchange Listener is the same as in the ECCR. Agent cache is refreshed only after the UPDATEINTERVAL is specified in the AGENTREP file. If new registrations have been created and updates captured for them,
PWX-06000 to PWX-06999
287
the Agent cache might not have the new registrations yet. Wait for UPDATEINTERVAL and then restart the ECCR. PWX-06981 Explanation: System Action: User Response: PWX-06982 Explanation: DBRC API function file_name failed. rc=return_code A call to the IMS DBRC API failed. IMS ECCR terminates with an error. Review the return code information. CCIMT: Mode nologging: Start date is start_date Logging is disabled for the IMS log-based ECCR. This message appears when you start the IMS ECCR. In the message text, the start_date is the date when the IMS ECCR was started. User Response: PWX-06983 Explanation: No response is required. CCIMT: F01A PowerExchange Logger API INIT failed rc=0xreturn_code rsn=0xreason_code The IMS ECCR did not connect to the PowerExchange Logger because PowerExchange Logger initialization failed. In the message text:
return_code is the PowerExchange return code for the failure. reason_code is the PowerExchange reason code for the failure. System Action: User Response: PWX-06984 Explanation: User Response: PWX-06985 Explanation: The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. CCIMT: No Extended Info The PowerExchange Logger provides no extended information for the IMS ECCR. No response is required. CCIMT: F01A PowerExchange Logger API RSTR call failed; rc=0xreturn_code rsn=0xreason_code A restart call of the PowerExchange Logger failed. In the message text:

return_code is the PowerExchange return code for the failure. reason_code is the PowerExchange reason code for the failure.
To determine the cause of the warning, review the specified return and reason codes. CCIMT: F01A PowerExchange Logger API GLCI call failed; rc=0xreturn_code rsn=0xreason_code A GLCI call to the PowerExchange Logger failed. In the message text:
return_code is the PowerExchange return code for the failure. reason_code is the PowerExchange reason code for the failure. User Response: Use the return code and reason code to determine the cause of the warning.
288
CCIMT: F01A GLCI did not return any extended Info A GLCI call to the PowerExchange Logger did not return any extended information. No response is required. CCIMT: F01A PowerExchange Logger API GHSQ call failed; rc=0xreturn_code rsn=0xreason_code A GHSQ call to the PowerExchange Logger failed. In the message text:

return_code is the PowerExchange return code for the failure. reason_code is the PowerExchange reason code for the failure.
User Response: PWX-06989 Explanation: System Action: User Response: PWX-06990 Explanation: System Action: User Response: PWX-06991 Explanation: User Response: PWX-06992 Explanation:
Use the return code and reason code to determine the cause of the warning. CCIMT: Cold start accepted The IMS ECCR accepted a request to cold start. The IMS ECCR cold starts. No response is required. CCIMT: Cold start declined The IMS ECCR rejected a request to cold start. The IMS ECCR does not start. No response is required. CCIMT: Cold start using start date date A cold start of the IMS ECCR begins at record with the specified start date. No response is required. CCIMT: Unable to find current RECON copy1 file rc A usable copy of a RECON data set could not be found. In the message text:

copy1 is the name of the RECON data set copy that could not be found. rc is the PowerExchange return code for the failure.
The IMS ECCR ends. Verify that the parameters for the RECON data sets are correct. CCIMT: SLDS data set data_set is of interest The IMS ECCR uses the specified SLDS data set for change data capture. No response is required. CCIMT: IMS ECCR will process the SLDS records from start time start_clock, hex1 to end time end_clock, hex2. The IMS ECCR processes the SLDS records from the specified start time to the specified end time. In the message text:

start_clock is the start store clock timestamp for the SLDS record. hex1 is the start clock time timestamp in hexadecimal format. end_clock is the end store clock for the SLDS record.
PWX-06000 to PWX-06999 289
hex2 is the end store clock timestamp in hexadecimal format.
User Response: PWX-06996 Explanation: User Response: PWX-06997 Explanation: User Response: PWX-06998 Explanation: System Action: User Response:
No response is required. CCIMT: unable to process beyond start_time (start time of ACTIVE OLDS) The IMS ECCR cannot process the IMS online OLDS data set records that have start time later than the specified start time. No response is required. CCIMT: unable to process beyond start_time (start time of unarchived OLDS) The IMS ECCR cannot process the IMS unarchived OLDS data set records that have start time later than the specified start time. No response is required. CCIMT: ***** Error opening recon data_set_name ***** The IMS ECCR cannot open the specified RECON data set. The IMS ECCR does not use the specified data set for change data capture. Verify that the parameters specified for the RECON data set are correct for change data capture. CCIMT: data_set_name will not be used during this Collector run The IMS ECCR will not use the specified RECON data set. The IMS ECCR does not use the specified data set. Verify that the parameters specified for the RECON data set are correct.
PWX-07000 to PWX-07999
PWX-07000 Explanation: System Action: User Response: PWX-07001 Explanation: System Action: User Response: PWX-07002 Explanation: System Action: User Response: PWX-07003 Explanation: Length of DSN exceeds number bytes. The Data Source Name entered exceeds 32 bytes in length. DTLODBC returns error code -1. Correct the input. Length of userid exceeds number bytes. The user ID entered exceeds 128 bytes in length. DTLODBC returns error code -1. Correct the input. Length of password exceeds number bytes. The password entered exceeds 128 bytes in length. DTLODBC returns error code -1. Correct the input. Function sequence error. An invalid sequence of ODBC functions was attempted. For example SQLFreeConnect was issued without a prior SQLDisconnect.
290
DTLODBC returns error code -1. Correct the logical sequence of ODBC calls. If this does not resolve the problem contact Informatica Global Customer Support with an ODBCD trace. Invalid or unsupported option option. An ODBC call requested an unsupported option. This is a generic error that can be returned on different ODBC calls. DTLODBC returns error code -1. Review documentation for supported functionality or correct error in ODBC call parameters. Invalid column number. The column descriptor for a column number was requested that was outside the valid range of 1 through n columns. DTLODBC returns error code -1. Review the ODBC request parameters. If this does not resolve the problem contact Informatica Global Customer Support with an ODBCD trace. Data truncated. This can be raised for a number of ODBC calls. Basically, a result string parameter was too small. DTLODBC returns error code (-1) (or SQL_SUCCESS_WITH_INFO (+1) for SQLDriverConnect or SQLGetInfo calls). Increase the size of the area passed for the string result and its length in the ODBC call. Type or length changed on rebind. The type or length changed on rebind. No response is required. Unknown SQL_C_TYPE (coltype). Attempt to bind a column to a user buffer failed as the user column type Was not recognized and the conversion could not be performed. DTLODBC returns error code -1. Review the column type parameter in the request. If this does not resolve the problem contact Informatica Global Customer Support with an ODBCD trace. Driver does not support prompting. An SQLDriverConnect call requested prompting. This is not supported. DTLODBC returns error code -1. Change the ODBC request uwMode parameter.
PWX-07006 Explanation: System Action: User Response: PWX-07007 Explanation: User Response: PWX-07008 Explanation: System Action: User Response:
PWX-07010 No DSN supplied and driver does not support prompting. Explanation: System Action: User Response: An SQLDriverConnect call did not pass a connection string or the connection string did not contain a DSN= keyword. DTLODBC returns error code -1. Change the ODBC request to pass a connection string.
PWX-07000 to PWX-07999
291
Data conversion error fetching column colnum (colname). Reason: msg. A data conversion error occurred. The message gives more detailed information about the cause. DTLODBC returns error code -1. For more information, review other messages from the PowerExchange API. If you cannot resolve the problem, contact Informatica Global Customer Support with and ODBCD trace. GetInfo for type infotype is not supported by the driver. A SQLGetInfo call requested unsupported type of information. DTLODBC returns error code -1. Review documentation for supported functionality. Alternatively, review call for parameter errors. Overflow building metadata SQL request. During translation of the meta_SQL request into PowerExchange format, it has overflowed the storage area of 2048 bytes. DTLODBC returns error code -1. Review the request and reformat if necessary. Column colnum, colname has already been bound by SQLBindCol. SQLGetData was requested for a column that was previously bound with a SQLBindCol to another target area. DTLODBC returns error code -1. Review sequence of calls or column number. SQLExtendedFetch. Error fetching column colnum (colname) at row RowNumber of rowset. Error occurred while moving data to the receivers bound column. DTLODBC returns SQL_SUCCESS_WITH_INFO (+1) on SQLExtendedFetch or 0 on SQLGroupFetch or DTLFetch. Review other messages for details (such as conversion error and so on). Driver not capable. (FetchType for SQLExtendedFetch)) The SQLExtendedFetch call fetchtype was not SQL_FETCH_NEXT. DTLODBC returns error code -1. Review documentation for supported functionality or correct error in ODBC call parameters. Invalid column number. Only maxnum columns supported before describe. Column number passed on SQLBindCol or SQLBindParameter call has an invalid value. DTLODBC returns error code -1. Correct ODBC parameter error or reduce the number of columns and parameters to be bound. If the problem persists, contact Informatica Global Customer Support with an ODBCD trace.
292
ColAttributes for type infotype is not supported by the driver. SQLColAttributes call requested a type of information about a column that is not supported. DTLODBC returns error code -1. Review documentation for supported functionality or correct error in ODBC call parameters. DBType not specified in odbc.ini for DSN datasource. Error on SQLConnect call. The requested PowerExchange ODBC source has no DBtype defined. DTLODBC returns error code -1. Correct the odbc.ini file. Location not specified in odbc.ini for DSN datasource. Error on SQLConnect call. The requested PowerExchange ODBC source has no location defined. DTLODBC returns error code -1. Correct the odbc.ini file. BindParameter number exceed number of markers in SQL statement. The number of parameter markers in the SQL statement is less than the parameter number passed on the call; DTLODBC returns error code -1. Verify that the ODBC request parameters are correct. Column colnum, colname has not been bound before executing SQL statement. The parameter marker in the SQL statement was not bound to a value. DTLODBC returns error code -1. Verify that the sequence of ODBC requests is correct. Invalid column number (parmnum) in BindParameter. The column descriptor for a parameter number was requested that was outside the valid range for that statement. DTLODBC returns error code -1. Verify that the ODBC request parameters are correct. SQL Function function is not supported. The type of SQL statement passed to SQLPrepare is not supported. DTLODBC returns error code -1. Correct the SQL statement. Cannot determine column number from SQL statement. The type of SQL Statement is not an insert, update, select, or delete and has no columns to describe. DTLODBC returns error code -1.
PWX-07000 to PWX-07999
293
User Response: PWX-07027 Explanation: System Action: User Response: PWX-07028 Explanation: System Action: User Response: PWX-07029 Explanation:
Correct the SQL statement. Invalid SQL statement <SQL_text>. The type of SQL statement passed to SQLPrepare is not recognized, or an Insert SQL statement has no VALUES clause. DTLODBC returns error code -1. Correct the SQL statement passed on the call. Number of columns in the result set have changed during re-execution of statement. The number of columns returned by the request has changed. DTLODBC returns error code -1. Internal error. Contact Informatica Global Customer Support with an ODBCD trace. Driver not capable of handling specified parameter parameter. Unsupported functionality or error in ODCB call parameters. For example in SQLGetStmtOption, ROWSET_SIZE and CURSOR_TYPE are the only supported options. DTLODBC returns error code -1. Review documentation for supported functionality or correct the ODBC call parameters. PKEYS do not support returning primary keys from multiple tables in a single call. The metadata request for primary key descriptions either did not specify a table or specified a generic table name. DTLAMODB returns error code 7030. Correct the request. FKEYS requires either the parent table or the foreign table. The metadata request for foreign key descriptions did not specify either a child nor a parent table. DTLAMODB returns error code 7031. Correct the request. FKEYS does not allow wildcards in the table names. The metadata request for foreign key descriptions specified a generic table name. DTLAMODB returns error code 7032. Correct the request. DBQual2 (AppName) not specified in odbc.ini for DSN datasource. For CAPX or CAPXRT, the odbc.ini file did not specify DBQUAL2, and it was not specified through a DTLAPP= escape sequence either. DTLODBC returns error code -1. Correct the coding error or the error in the odbc.ini file. No rows or more than one row were action. This message is informational. DTLODBC returns warning code SQL_SUCCESS_WITH_INFO (+1).
System Action: User Response: PWX-07030 Explanation: System Action: User Response: PWX-07031 Explanation: System Action: User Response: PWX-07032 Explanation: System Action: User Response: PWX-07033 Explanation: System Action: User Response: PWX-07034 Explanation: System Action:
294
User Response: PWX-07035 Explanation: System Action: User Response: PWX-07036 Explanation: System Action: User Response: PWX-07037 Explanation: System Action: User Response: PWX-07038 Explanation: System Action: User Response: PWX-07072 Explanation: User Response: PWX-07073 Explanation: User Response: PWX-07074 Explanation: User Response: PWX-07075 Explanation: System Action: User Response: PWX-07076 Explanation:
Verify results against application expectations. Must connect with GSMODE=YES to use Group Fetch. The CLI call did not specify GSMODE=YES on a DTLGroupFetch call. DTLSCLI returns error code (-1). Correct the request. Only Select statements may be active for Group Fetch. The DTLGroupFetch CLI call used a non-Select type SQL statement. DTLSCLI returns error code (-1). Change the call statement. Group Fetch open connection failed: RC=return_code rc1=return_code1 rc2=return_code2. The DTLConnect CLI call failed on the call to the PowerExchange API Openconnection call. DTLSCLI returns error code (-1). Review other messages from the PowerExchange API. Group Fetch read connection failed: RC=return_code rc1=return_code1 rc2=return_code2. The DTLGroupFetch CLI call failed on the call to the PowerExchange API DB_READ call. DTLSCLI returns error code (-1). Review other messages from the PowerExchange API. MQGETOPT This message is informational. No response is required. NOUPDATECDEP This message is informational. No response is required. TIMEOUT This message is informational. No response is required. Unable to process Bind Control request. Statement (hstmt) parameter is NULL. Unable to process Bind Control request due to an invalid NULL value passed for the Statement parameter. Return error code. Ensure that a correct Statement is passed to the Bind Control function. Unable to process Bind Control request. Buffer parameter is NULL. Unable to process Bind Control request due to an invalid NULL value passed for the Buffer parameter.
PWX-07000 to PWX-07999
295
Return error code. Ensure that a correct Buffer parameter is passed to the Bind Control function. Unable to process Bind Control request. Buffer length parameter is invalid. Unable to process Bind Control request due to an invalid value passed for the Buffer Length parameter. Buffer length must be greater than 0. Return error code. Ensure that a correct Buffer Length is passed to the Bind Control function. Unable to process Bind Control request. Control Type invalid. Unable to process Bind Control request due to an invalid value passed for the Control Type parameter. Valid values include SCLI_RESTART_TOKEN1 and SCLI_RESTART_TOKEN2. Return error code. Ensure that a correct Control Type is passed to the Bind Control function. Unable to process Execute Control request. Pass either a Connection (hdbc) or a Statement (hstmt). Unable to process Execute Control request as the Connection and Statement parameters are mutually exclusive. Return error code. Submit a value for either Connection or Statement. Unable to process Execute Control request. Control Type invalid. Unable to process Execute Control request due to an invalid value passed for the Control Type parameter. The valid value is SCLI_RESTART_TOKEN_PUT. Return error code. Ensure that a correct Control Type is passed to the Execute Control function. Unable to process Execute Control request. Ensure Restart Tokens have been bound using DTLBindControl. Unable to process Execute Control request due to an invalid NULL value for presence of the DBCB. Return error code. Ensure that the Restart Tokens have been bound using DTLBindControl. Unable to process Execute Control request. The value for SCLI_RESTART_TOKEN1 is invalid. Unable to process Execute Control request. The SCLI_RESTART_TOKEN1 parameter has an invalid value. Return error code. Ensure that the Restart Tokens have been bound using DTLBindControl. Unable to process Execute Control request. The value for SCLI_RESTART_TOKEN2 is invalid. Unable to process Execute Control request. The SCLI_RESTART_TOKEN2 parameter has an invalid value.
System Action: User Response: PWX-07079 Explanation: System Action: User Response: PWX-07080 Explanation: System Action: User Response: PWX-07081 Explanation: System Action: User Response: PWX-07082 Explanation: System Action: User Response: PWX-07083 Explanation:
296
Return error code. Ensure that the Restart Tokens have been bound using DTLBindControl. DB_PRESENCE call failed: rc1=return_code1 rc2=return_code2 rc3=return_code3. The DTLExecuteControl CLI call failed on the call to the PowerExchange API DB_PRESENCE call. DTLSCLI returns error code Review other messages from the PowerExchange API. Too many SQL statements. CAPXRT and CAPX are only allowed one statement when reading. Return error code. Remove additional statements. Missing encryption level for encryption type ENCRYPTTYPE. For the selected encryption type a mandatory encryption level must be entered. Validation fails. Ensure that a valid value is entered for parameter ENCRYPTLEVEL. Invalid capture latency time. Invalid latency time specified. Validation fails. Enter a valid latency time. LATENCY=(nsec,Y/N) Invalid capture latency time. Invalid latency time specified. Valid values are 0.86400. Validation fails. Enter a valid latency time. LATENCY=(nsec,Y/N). Invalid capture latency flag. Invalid latency flag specified. Valid values are:

Y=latency time accurate N=latency time approximate
System Action: User Response: PWX-07094 Explanation: System Action: User Response: PWX-07095 Explanation: System Action:
Validation fails. Enter a valid option (Y/N). Bad codepage value : The codepage parameter in the connect string is not valid. The connection fails. Verify that the connect string parameters are correct. Bad codepage in odbc.ini for DSN DSName. The codepage associated with the ODBC datasource is not supported. The connection to the ODBC data source fails.
PWX-07000 to PWX-07999
297
Verify that the configuration of the ODBC data source is correct. column number (name) ODBC caller buffer length buffer_length less than minimum minimum for multibyte code page PowerExchange_code_page_number (name). The specified column that has data in a multibyte code page and the length of the client data might differ from the length on the source DBMS. The length of the buffer provided to ODBC in API SQLBindCol is smaller than the length that PowerExchange uses on Read or other requests. The connection to the ODBC data source fails. In the ODBC data source, check the length of the problem column after considering potential expansion because of different code pages. For example, a CHAR column of precision 22 in code page IBM EBCDIC Japanese (IBM-930) must be bound to a considerably larger buffer if the ODBC driver delivers results in UTF-8. Invalid use of null pointer The Attribute argument identified a statement attribute that required a string attribute and the ValuePtr argument was a null pointer. Setting of the statement attribute failed. Pass a valid pointer to a string. Invalid string or buffer length *ValuePtr is a character string, and the StringLength argument was less than 0, but was not SQL_NTS. Call to set statement attribute failed. Pass a valid pointer to a string and StringLength. Invalid attribute/option identifier The value specified for the argument Attribute was not valid for the version of ODBC supported by the driver. Call to set statement attribute failed. Enter only valid supported argument attributes. The string or buffer length has exceeded the maximum value of maxvalue The string or buffer length has exceeded the maximum value. Call to set statement attribute failed. Pass a string within the length boundaries. Invalid or conflicting LOGSID. Invalid or conflicting LOGSID specified. Maximum size is 8. Validation fails. Enter a valid LOGSID and ensure that it does not conflict with other options. Invalid escape sequence value(value) for value: Allowed length=length Used length=length The escape sequence value exceeds allowed length. Validation fails. Enter a valid value.
298
Statement <statement> cannot be processed with statement attribute DTL_ATTR_UPDELSEINS The statement has the DTL_ATTR_UPDELSEINS attribute set, but is incompatible with update else insert processing. Update else insert processing is not performed for the statement. No response is required. Error override file <file_name> not found The error override file specified in dbmover.cfg was not found. Processing ends. Correct or remove the error override file specification in the configuration (such as, DB2_ERRORFILE). Scaling metadata column precision assuming an ODBC connection code page of code_page_name (number) When importing metadata on a table, the connection code page is not known. The system assumes that the ODBC connection code page is the same as the configuration data code page and determines the bytes required at run time to hold CHAR and VARCHAR columns. This message might be useful if a PWX-07096 truncation message occurs when running a workflow using ODBC. Scaling metadata column precision by expansion_factor assuming an ODBC connection code page of code_page_name (number) When importing metadata on a table, the connection code page is not known. The system assumes that the ODBC connection code page is the same as the configuration data code page and determines the bytes required at run time to hold CHAR and VARCHAR columns by multiplying by the maximum bytes per character. This message might be useful if a PWX-07096 truncation message occurs when running a workflow using ODBC. Overriding the Write Mode to Confirm Write On as location value is set to 'local'. This message displays during the start up of an ODBC or SCLI session. No response is required. module_name connected using API_routine PWX Version: Software_Version, Patch Level: patch_level. This message displays during the start up of an ODBC or SCLI session. No response is required. Connected using local code pages: Control=code_page (internal_number) Data=code_page (internal_number) SQL=code_page (internal_number). Provides information about the code pages in use when connect calls are done. The control and SQL code pages are defined in the PowerExchange configuration file dbmover.cfg. The data code page is taken from the connection LocalCodepage parameter, but is overridden to UTF8 on Metadata calls when importing source or target tables. No response is required.
User Response:
User Response:
PWX-07120 Explanation: User Response: PWX-07121 Explanation: User Response: PWX-07122 Explanation:
User Response:
PWX-07000 to PWX-07999
299
module_name disconnected using API_routine. This message displays during the end of an ODBC or SCLI session. No response is required. Error translating field in call_type. A code page conversion error occurred. Processing on the statement fails Review the associated messages for information about the characters and the source and target code pages. If the error occurs during a Connect, ensure that the control code page is capable of receiving the characters. If the error occurs during a Prepare, ensure that the SQL code page is capable of receiving the characters and that the connection code page(s) are correct. Error getting information on internal_code_page_number in call_type. An invalid internal code page number was used. Processing on the statement fails Contact Informatica Global Customer Support SQL code page code_page (internal_number) is not valid on this platform. Reason reason_number. The SQL code page in the configuration file is not valid.

Reason 1. The code page does not support a minimum of one byte per character. Reason 2. The code page is foreign to the platform and is not compatible with the code page that programs are compiled in.
Processing fails. Provide a suitable SQL code page in the PWX configuration file (dbmover.cfg). For SQL containing multibyte characters on Windows and UNIX, UTF-8 can be used. action table table_name Rows = count Applied = count Failed = count mutated This messages displays statistics for Confirmwrite=T processing. No response is required. Data Code Page reset to code_page (internal_number). This message displays information about the code pages used by PowerExchange. The data code page is taken from the PowerCenter connection Codepage parameter. Processing continues. No response is required. Failed to reset data Code Page to code_page_name. Data Code Page reverted to code_page_name (internal_number). This message displays information about the code pages used by PowerExchange The data code page is taken from the PowerCenter connection Codepage parameter. Processing continues. No response is required.
PWX-07129 Explanation: User Response: PWX-07130 Explanation: System Action: User Response: PWX-07131 Explanation: System Action: User Response:
300
Invalid escape value for Worker Threads: Specified Value=value Allowed Maximum=max The value specified for the DTLWORKERS SQL escape sequence is outside of the valid range of 0 to 64. When you select offload processing for a PowerExchange Change Data Capture (CDC) or bulk data movement session, the DTLWORKERS SQL escape sequence specifies the number of threads that PowerExchange uses on the Integration Service machine to process data.
The session ends. Enter a valid value in the DTLWORKERS SQL escape sequence. For optimal performance, this value should not exceed the number of installed or available processors on the Integration Service machine. For more information about SQL escape sequences, see the PowerExchange Reference Manual. JXAS4 failed to open file file_name during Action function. Return codes are Code1, Code2 & Code3. An error occurred during the opening of the file for the action specified in the error message. Processing of the journal entries ends. Contact Informatica Global Customer Support reporting the error and the return codes given. JXAS4 failed to prepare file file_name during Action function. Return codes are Code1, Code2 & Code3. An error occurred during the file preparation for the action specified in the error message. Processing of the journal entries ends. Contact Informatica Global Customer Support reporting the error and the return codes given. JXAS4 failed to read file file_name during Action function. Return codes are Code1, Code2 & Code3. An error occurred during the reading of the file for the action specified in the error message. Processing of the journal entries ends. Contact Informatica Global Customer Support reporting the error and the return codes given. JXAS4 failed to close file file_name during Action function. Return codes are Code1, Code2 & Code3. An error occurred during the closing of file for the action specified in the error message. Processing of the journal entries ends. Contact Informatica Global Customer Support reporting the error and the return codes given. JXAS4 failed to write to file file_name during Action function. Return codes are Code1, Code2 & Code3. An error occurred during the write to file for the action specified in the error message. Processing of the journal entries ends.
PWX-07000 to PWX-07999
301
User Response:
Contact Informatica Global Customer Support reporting the error and the return codes given. JXAS4 failed to delete from file file_name during Action function. Return codes are Code1, Code2 & Code3. An error occurred during the delete from file for the action specified in the error message. Processing of the journal entries ends. Contact Informatica Global Customer Support reporting the error and the return codes given. Failed to lock receiver Receiver in Library for reference Reference. Receiver count count. Reason reason_code. An error occurred during the locking of a journal receiver. See previous messages for further information. Processing of the journal entries continues. Contact Informatica Global Customer Support reporting the error and the return codes given. Failed to unlock receiver Receiver in Library for reference Reference. Receiver count count. Reason reason_code. An error occurred during the unlocking of a journal receiver. See previous messages for further information. Processing of the journal entries continues. Contact Informatica Global Customer Support reporting the error and the return codes given. Failed to unlock all receivers for current job. Reason reason_code. An error occurred during the unlocking of all journal receivers for the task. See previous messages for further information. Processing of the journal entries continues. Contact Informatica Global Customer Support reporting the error and the return codes given. Invalid DEFER(INSERT/IUD)PREP option The DEFERINSERTPREP or DEFERIUDPREP parameter has an invalid value. Validation fails. Enter a valid DEFERxxxPREP (Y/N). CCIMT: IMS level does not match key length of RECON data set. The key length of the RECON data set does not match the IMS level. The RECON data sets, which are KSDS data sets, have version-dependent differences. One of these differences is the key length. The IMS ECCR does not use this RECON data set. No response is required.
302
CCIMT: A RECON read error occurred. Return codes=return_code1,return_code2,return_code3 An error occurred while the IMS ECCR was reading information about archive logs from the RECON data set. In the message text:
return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure.
System Action:
The IMS ECCR does not use the RECON data set. The IMS ECCR maintains three copies of the RECON data sets. The primary RECON data set is called RECON1 or Copy1. The second data set is called RECON2 or Copy2. The third is called RECON3 or SPARE. If the IMS ECCR fails to access RECON1, it tries to use RECON2 or RECON3.
No response is required. CCIMT: A RECON version mismatch exists in RECON data set data_set_name The version level of the specified RECON data set does not match the IMS level. The IMS ECCR ends. Verify that the RECON data sets specified in the IMS ECCR configuration parameters are correct. CCIMT: IMS ECCR cannot process the key in record 2 of RECON data set data_set_name The IMS ECCR cannot process the key in record 2 of the specified RECON data set. The record contains an invalid key. The IMS ECCR does not use this RECON data set for change data capture. The IMS ECCR maintains three copies of the RECON data sets. The primary RECON data set is called RECON1, or Copy1. The second data set is called RECON2, or Copy2. The third is called RECON3, or SPARE. If the IMS ECCR fails to access RECON1, it tries to use RECON2 and RECON3.
User Response:
Verify that the RECON data set specified in the IMS ECCR configuration parameters are correct. The following examples shows a valid specification of configuration parameters:
DBID=IMSA DB_TYPE=IMS ECCRNAME=MIGIMSA0 RECID=A0 IMSID=(IMSA,IMS1010.ACBLIB, RECON=(IMS1010.RECON1, IMS1010.RECON2, IMS1010.RECON3)) NO_DATA_WAIT=60 NO_DATA_WAIT2=600 CAPT_STATS=Y COLDSTART=N
PWX-07000 to PWX-07999
303
CCIMT: The IMS ECCR cannot read change data from the overflow log record X07, key<key>. Return codes=return_code1,return_code2,return_code3 The IMS ECCR cannot read change data from the overflow log record that has the specified key. The RECON data sets contain different types of records, one of which is the X'07' record. The information in this type of record can be stored in a single record or in multiple records. In the message text:
key is key of the overflow record. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure. System Action: User Response: The IMS ECCR ends. Verify that the RECON data set is correct. Because the read failed, something could be wrong with the data set. CCIMT: The IMS ECCR cannot process the RECON point request to log record X05, key<key>. Return codes=return_code1,return_code2,return_code3 The IMS ECCR cannot use the pointer in the RECON data set to access the X05 log record. In the message text:
key is key of the record pointed to. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure. System Action: User Response: PWX-07257 Explanation: The IMS ECCR ends. Verify that the RECON data set is correct. CCIMT: The IMS ECCR cannot read the RECON data set record X05. Return codes=return_code1,return_code2,return_code3 The IMS ECCR cannot read change data from the x05 record of the RECON data set. In the message text:
return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure.
The IMS ECCR ends. Verify that the RECON data set is correct. CCIMT: Unable to allocate memory for PRILOG record The IMS ECCR cannot allocate memory to process the PRILOG record in the RECON data set. The IMS ECCR ends. Verify that the region size for the ECCR job or started task is sufficient. CCIMT: The IMS ECCR cannot read the RECON SECLOG data set record. Return codes=return_code1/return_code2/return_code3 The IMS ECCR cannot read the SECLOG in the RECON data set. In the message text, return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure.
System Action:
The IMS ECCR ignores the SECLOG record and continues to the PRILOG record.
304
No response is required. CCIMT: Unclosed log implies ECCR processing must stop before timestamp The IMS ECCR found an unclosed log. The IMS ECCR can process only closed logs. If it finds an unclosed log, it cannot continue processing beyond the starting time of the unclosed log, which is indicated by the specified timestamp. The IMS ECCR ends before the specified timestamp. No response is required. CCIMT: The IMS ECCR will use offline log data_set The IMS ECCR uses the specified offline log data set. For example, offline logs created by jobs with DL/1 Batch data maps. The IMS ECCR creates a list of logs that are candidates to be processed. Some of the logs are dropped from the list later depending on timing decisions. This message is issued in the following situations:
A candidate log on the interest list is flagged with an error so the ECCR uses the specified offline log instead. In this case, this message is followed by messages PWX-07262 and PWX-07263. The message level in the IMS ECCR parameters is greater than 0. In this case, this message is an informational message. System Action: User Response: PWX-07262 Explanation: The IMS ECCR processing continues. No response is required. CCIMT: The IMS ECCR will use offline log data set with start time start_time_hex start_time and end time stop_time_hex stop_time The IMS ECCR uses the offline log data set. In the message text:

start_time_hex is log data set start time in hexadecimal format. start_time is the log data set start time. stop_time_hex is the log data set stop time in hexadecimal format. stop_time is the log data set stop time. System Action: User Response: PWX-07263 Explanation: System Action: User Response: PWX-07264 Explanation: System Action: User Response: The IMS ECCR processing continues. No response is required. CCIMT: Action is required to make data set dataset_name usable because it is flagged with an error. IMS flags the specified log data set with an error. Consequently, the IMS ECCR cannot use this log data set for change data capture until the error is corrected. IMS does not use the log data set. Correct the log data set. CCIMT: The IMS ECCR cannot process data set data_set_name because it has no start time. The IMS ECCR cannot process the specified data set because the log data set does not specify a start time. The IMS ECCR ignores the data set. Correct the log data set to specify a start time.
PWX-07000 to PWX-07999
305
CCIMT: The IMS ECCR cannot process data_set_name because it has no stop time. The IMS ECCR cannot process the specified data set because the log data set does not specify a stop time. The IMS ECCR ignores the data set. Correct the log data set to specify a stop time. Unable to process data set data_set_name because its stop time is greater than the start time of the active logs. The IMS ECCR cannot process the specified data set because its stop time is greater than the start time of active logs. The IMS ECCR cannot process logs with times greater than the start time of the active logs. The message can be issued for batch logs or system log data sets (SDLS). When the active logs become inactive, the IMS ECCR processes the data sets. No response is required. CCIMT: Unable to process data set dataset_name because its end time is later than the start time on an unprocessed log. The IMS ECCR cannot process the specified data set because its stop time is greater than the start of a log that cannot be processed. The IMS ECCR processes the data set. No response is required. CCIMT:(ECCR ECCR_name) Selected Option is option An invalid option, option, was selected for the IMS ECCR. Correct the invalid option for the IMS ECCR. CCIMT: The ECCR is ignoring log <log_name> because the allocation failed and the stop time is not greater than the current time. The IMS ECCR cannot process the specified log data set because the allocation failed and the stop time is less than or equal to the current time. The IMS ECCR ignores the data set. This message is always followed by PWX-07270, which indicates an open of a log failed. No response is required. CCIMT: This log has probably been deleted after being processed in a previous run. The IMS ECCR cannot process the data set because the allocation failed. The IMS ECCR ignores the data set. No response is required.
System Action: User Response: PWX-07267 Explanation: System Action: User Response: PWX-07268 Explanation: User Response: PWX-07269 Explanation: System Action: User Response: PWX-07270 Explanation: System Action: User Response:
306
CCIMT: The IMS ECCR is unable to open data set data_set_name with start time start_time stop time stop_time. Return codes=return_code1,return_code2,return_code1 The IMS ECCR cannot process the specified RECON data set because it cannot open it. In the message text:

data_set_name is the data set that cannot be opened. start_time is the start time of the log data set. stop_time is the stop time of the log data set. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure. Log data set start and stop times are stored in the RECON for every log data set. System Action: User Response: PWX-07272 Explanation: User Response: PWX-07273 Explanation: The IMS ECCR ends. Verify that the log data set is correct. CCIMT: The IMS ECCR is processing log data set data_set_name The IMS ECCR is processing the specified log. No response is required. CCIMT: F55 PowerExchange Logger API ABRT failed rc=0xreturn_code rsn=0xreason_code An ABRT call to the PowerExchange Logger failed. In the message text:
return_code is the PowerExchange return code for the failure. reason_code is the second reason code for the failure. System Action: User Response: PWX-07274 Explanation: The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. CCIMT: F03 PowerExchange Logger API ISRT failed rc=0xreturn_code rsn=0xreason_code tag=registration_tag An ISRT call to the PowerExchange Logger failed. In the message text:
return_code is the PowerExchange return code for the failure. reason_code is the second reason code for the failure. System Action: User Response: PWX-07275 Explanation: The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. CCIMT: F03 PowerExchange Logger API REPL failed rc=0xreturn_code rsn=0xreason_code tag=registration_tag An REPL call to the PowerExchange Logger failed. In the message text:

return_code is the PowerExchange return code for the failure. reason_code is the second reason code for the failure. registration_tag is the capture registration tag. System Action: User Response: The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes.
PWX-07000 to PWX-07999
307
CCIMT: F03 PowerExchange Logger API DLET failed rc=0xreturn_code rsn=0xreason_code tag=registration_tag An DLET call to the PowerExchange Logger failed. In the message text:

return_code is the PowerExchange return code for the failure. reason_code is the second reason code for the failure. registration_tag is the capture registration tag for table capture. System Action: User Response: PWX-07277 Explanation: System Action: User Response: The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. : Unable to find BUOW for current operation. Producing a dump. The ending units of work (UOWs) are missing in a warm start of the ECCR. The IMS ECCR ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: The TRACEON command is missing the trace filter and trace level The syntax of the TRACEON command is incorrect. The TRACEON command requires a trace filter and trace level. The IMS ECCR does not process the command. To get the trace filter and level values, contact Informatica Global Customer Support. For more information about the TRACEON command, see the PowerExchange Command Reference. CCIMT: F51 PowerExchange Logger API BUOW failed rc=0xreturn_code A BUOW call to the PowerExchange Logger failed. The ECCR will shut down. Review the return code and reason code. CCIMT: F54 PowerExchange Logger API CHKP failed rc=0xreturn_code rsn=0xreason_code An CHKP call to the PowerExchange Logger failed. The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. CCIMT: F61 PowerExchange Logger API BUOW failed rc=0xreturn_code rsn=0xreason_code An BUOW call to the PowerExchange Logger failed. In the message text:

return_code is the PowerExchange return code for the failure. reason_code is the reason code for the failure.
The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes.
308
CCIMT: F65 PowerExchange Logger API ABRT failed rc=0xreturn_code rsn=0xreason_code An ABRT call to the PowerExchange Logger failed. In the message text:

return_code is the PowerExchange return code for the failure. reason_code is the reason code for the failure.
The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. CCIMT: F66 PowerExchange Logger API Evnt failed rc=0xreturn_code rsn=0xreason_code An EVNT call to the PowerExchange Logger failed. In the message text:
return_code is the PowerExchange return code for the failure. reason_code is the reason code for the failure. System Action: User Response: PWX-07291 Explanation: User Response: PWX-07292 Explanation: System Action: User Response: The IMS ECCR ends. To diagnose the problem, review the specified return and reason codes. CCIMT: DTLCCIMT is shutting down after reading the IMS log to timestamp The IMS ECCR completed reading the IMS log records up to the specified time and is now shutting down. No response is required. CCIMT: Log record Incomplete. Updates lost. The IMS ECCR read an incomplete log record. Updates are lost. The IMS ECCR ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: First Record is not found. The IMS ECCR cannot find the first record in a data set. The IMS ECCR ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: The IMS ECCR is processing recovery token: recovtkn MVS storeclock value: stk The IMS ECCR is processing a recovery token. In the message text:
recovtkn is the recovery token. stk is the stored clock timestamp of the log. User Response: PWX-07295 Explanation: System Action: No response is required. CCIMT: Report Error to Informatica Global Customer Support IMS ECCR encountered a severe error during change data capture. The IMS ECCR ends.
PWX-07000 to PWX-07999
309
User Response:
To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: Interleaved updates lost. Processing recovery token. The specified recovery token is being processed. Updates are lost. The IMS ECCR processes the specified recovery token and then ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: A call to DTLCCEXP failed with return code return_code An IMS ECCR call to DTLCCEXP returned an error with specified return code. The IMS ECCR ignores the record. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: Internal diagnostic information: ptr_dedr ptr_tank logl size compression_algorithm output A call to DTLCCEXP returned an error. This message provides the following diagnostic information for Informatica Global Customer Support:

ptr_dedr is the pointer to the original area. ptr_tank is the pointer to the decompression area. logl is the pointer to the data after the log header. size is the size of the data. compression_algorithm is the compression algorithm. output is the pointer to the decompressed data. System Action: User Response: The IMS ECCR ignores the record. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: ptr=pointer eorec=end_of_record A call to DTLCCEXP returned an error. This message provides internal pointer values, pointer and end_of_record, for diagnostic use by Informatica Global Customer Support. The IMS ECCR ignores the record. Contact Informatica Global Customer Support. CCIMT: The IMS log record ID is invalid because it contains more than two hexadecimal characters. The IMS log record ID has an invalid value because its value is greater than two hexadecimal characters. The IMS ECCR ends. Verify that the IMS ECCR input parameters are correct. CCIMT: The IMS log record ID is invalid because its value is less than hexadecimal A0. The IMS log record ID has an invalid value because its value is less than hexadecimal A0. The IMS ECCR ends. Verify that the input parameters are correct.
310
CCIMT: The IMS log record ID for marker events is record_id. The marker events parameter for the IMS log record ID is record_ID. The IMS ECCR ends. Verify that the input parameters are correct. CCIMT: The IMS log record ID is invalid because it is specified in non hexadecimal characters. An invalid IMS log record ID containing non-hexadecimal characters was specified. The IMS ECCR ends. Verify that the input parameters are correct. CCIMT: Unable to read HALDB partition info for DBD dbd_name from Recon The IMS ECCR cannot read the HALDB partition information for the specified DBD from the IMS RECON data set. The IMS ECCR ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. CCIMT: Unable to allocate memory for partition information The IMS ECCR cannot allocate more memory. The IMS ECCR ends. Verify that the JCL region size is correct. CCIMT: The log might have been previously processed to EOF. It is being reread for continuity only. The IMS ECCR might have processed this SLDS data set already. The IMS ECCR rereads the SLDS data set for continuity. The data set might have already been processed. No response is required. Because the SLDS data set was already processed, the absence of the log is tolerated. The IMS ECCR tolerates the absence of the log. No response is required. CCIMT: PowerExchange Logger API Stsl(call_supported) failed rc=0xreturn_code. An Stsl call to the PowerExchange Logger failed. The Stsl call supports the specified call. No response is required. DTL07901 Please confirm cold start (Y/N) (ADABAS capture). Restart information was not available from the PowerExchange Logger or PowerExchange Agent for a warm start of the Adabas ECCR. Consequently, PowerExchange requests confirmation for a cold start. PowerExchange waits for a reply. Enter Y to confirm the cold start, or enter N to deny it.
PWX-07305 Explanation: System Action: User Response: PWX-07306 Explanation: System Action: User Response: PWX-07307 Explanation: User Response: PWX-07308 Explanation: User Response: PWX-07901 Explanation:
PWX-07000 to PWX-07999
311
DTL07902 Cold start denied by operator (ADABAS capture). The operator replied N to the message PWX-07901, which requests confirmation of a cold start. This action denies the Adabas ECCR cold start. The Adabas ECCR ends. No response is required. DTL07903 Finished processing plog_file (ADABAS capture). This message indicates that the Adabas ECCR finished processing the specified PLOG data set. The Adabas ECCR ends. No response is required. DTL07904 Collector closing down (ADABAS Capture) The Adabas ECCR is shutting down. ECCR processing ends. No response is required. DTL07905 Current PLOG copy is plog_file latest time processed timestamp (ADABAS Capture) This message identifies the last Adabas PLOG file processed and the timestamp for that processing. Adabas ECCR processing continues. No response is required. PowerExchange Logger API Call ctype failed rc=return_code rsn=rsn (ADABAS CAPTURE) The specified type of call to the PowerExchange Logger API failed with the reported return and reason codes. Adabas ECCR processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. Error translating File number to File name rc=return_code (ADABAS CAPTURE) The Adabas ECCR encountered an error when trying to access a PLOG file. ECCR processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. Error while accessing data sets DD:DDEXPA1 and DD:DTLCCETL rc=return_code (ADABAS CAPTURE) The data sets to which the DDEXPA1 and DTLCCETL DD names point were not accessible. Adabas ECCR processing ends. Verify that the data sets are set up correctly. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support.
312
Error while reading log data sets rc=return_code (ADABAS CAPTURE) An error occurred while reading the log data sets. Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. Error while attempting to action registration. rc=return_code rsn=rsn regtag=registration (ADABAS CAPTURE) The attempted action on a capture registration failed with the reported reason and return codes. Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. Attempt to write to event marker failed with rc=return_code. Continuing(ADABAS CAPTURE) An attempt to write an update to the event marker table failed. PowerExchange Condense processing continues. No response is required. CCT used by PowerExchange Logger is not that in use by this Collector (ADABAS CAPTURE) The CCT file that the ECCR is using does not match that used by the PowerExchange Logger. Change capture processing ends. Correct the CCT file that is defined to the PowerExchange Logger process. An unrecoverable error related to LLB logging has occurred (ADABAS CAPTURE) A fatal error occurred. Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. OPENFILE in mode mode failed. File name=file_name rc1=return_code1 rc2=return_code2 rc3=return_code3 (ADABAS CAPTURE) An attempt to open the specified file failed. In the message text:
mode is the open file mode. file_name is the name of the file that was being opened. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure. System Action: User Response: Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support.
PWX-07000 to PWX-07999
313
CLOSEFILE in mode mode failed. File name=file_name rc1=return_code1 rc2=return_code2 rc3=return_code3 (ADABAS CAPTURE) An attempt to close the specified file failed. In the message text:

mode is the close file mode. file_name is the name of the file that was being closed. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure. System Action: User Response: Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. READFILE failed at ref - File name=file_name rc1=return_code1 rc2=return_code2 rc3=return_code3 (ADABAS CAPTURE) An attempt to read the specified file failed. In the message text:

file_name is the name of the file that was being read. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure.
Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. WRITEFILE failed at ref - File name=file_name rc1=return_code1 rc2=return_code2 rc3=return_code3 (ADABAS CAPTURE) An attempt to write data to the specified file failed.

file_name is the name of the file that was being written to. return_code1, return_code2, and return_code3 are PowerExchange return codes for the failure.
Processing ends. To diagnose the problem, review associated messages. If the problem persists, contact Informatica Global Customer Support. DTLCCADA shutting down having read to time time record number recno fileno fileno Adabas ECCR read process is ending. This message indicates the last record read. ECCR processing ends. No response is required. Initialization failed waiting termination.(ADABAS capture) Adabas ECCR initialization failed. Consequently, the ECCR is ending. ECCR processing ends. Examine the ECCR output for additional information. Correct any errors. Then run the request again. Extraction Map=<dbid.fnr> does not contain DBID and/or FileID. The registration is not a valid Adabas registration.
314
Extraction processing fails. Examine the registration and correct the DBID or file number. Then, run the request again. DTLCCIDL shutting down having read to ...... The IDMS log-based ECCR is shutting down. IDMS ECCR processing ends. No response is required. Tracing turned off. Tracing was disabled in response to the TRACEOFF command. No response is required. Please confirm cold start (Y/N) (IDMS capture). Restart information was not available from the PowerExchange Logger or PowerExchange Agent for a warm start of the IDMS ECCR. Consequently, PowerExchange requests confirmation for a cold start. PowerExchange waits for a reply. Enter Y to confirm the cold start, or enter N to deny it. Cold start denied by operator (IDMS capture). The operator replied N to the message PWX-07969, which requests confirmation of a cold start. This action denies a cold start of the IDMS ECCR. The IDMS ECCR ends. No response is required. Collector closing down (IDMS Capture) The IDMS log-based ECCR is closing. The ECCR ends. No response is required. Initialization failed, awaiting termination.(IDMS capture) The IDMS log-based ECCR failed to initialize and is closing. The ECCR ends. To diagnose the problem, review the IDMS ECCR output. Then, correct the error and restart the ECCR. Read IDMS Journal routine failed.Additional info: RC= return_code(IDMS capture) The IDMS ECCR routine for reading IDMS journals failed with the specified return code. The ECCR ends. To diagnose the problem, review the IDMS ECCR output. Then, correct the error and restart the IDMS ECCR. Error writing to PowerExchange Logger. Additional info: text(IDMS capture) The IDMS log-based ECCR encountered an error when attempting to write change data to the PowerExchange Logger. This message contains information about the error.
PWX-07967 Explanation: System Action: User Response: PWX-07968 Explanation: User Response: PWX-07969 Explanation:
System Action: User Response: PWX-07970 Explanation: System Action: User Response: PWX-07971 Explanation: System Action: User Response: PWX-07972 Explanation: System Action: Explanation:
PWX-07973 Explanation: System Action: Explanation:
PWX-07000 to PWX-07999
315
System Action: Explanation:
ECCR processing ends. To diagnose the problem, review the text of this message and the IDMS ECCR output. Correct the error and restart the IDMS ECCR. Logsid specified in DTLCACFG does not match any in DTLCFG.(IDMS capture) The LOGSID value in the IDMS ECCR configuration file does not match the LOGSID value in the DBMOVER configuration file. The DTLCACFG DD points to the IDMS ECCR configuration file, and the DTLCFG DD points to the DBMOVER configuration file. ECCR processing ends. Ensure that the LOGSID value in the IDMS configuration file matches the LOGSID value in the DBMOVER configuration file. Then, restart the IDMS ECCR. Latest time processed time Records processed number (IDMS Capture) This message displays the timestamp for the log record that the IDMS ECCR last processed and the total number of log records that the IDMS ECCR processed since it started. In the message text:

time is the time that the last IDMS log record was processed. number is the number of records processed in this run.
IDMS ECCR processing continues. No response is required. registration Inserts=number Deletes=number Updates=number This message displays the number of inserts, deletes, and updates that were captured based on the specified capture registration during the current run of the IDMS ECCR. No response is required. Error Matching UOWs. Additional info: function_name No matching UOW found Returning with RC=return_code (IDMS capture) The IDMS ECCR did not find a corresponding unit of work (UOW) for an update. In the message text:
function_name is the function for which the IDMS ECCR did not find a UOW. return_code is the PowerExchange return code for the error. System Action: User Response: ECCR processing ends. To diagnose the problem, review the ECCR output. Correct the error if possible. Then restart the IDMS ECCR. PowerExchange Logger API INIT failed rc=0xreturn_code rsn=0xreason_code PowerExchange Logger API initialization failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:
return_code is the PowerExchange return code for the error. reason_code is the PowerExchange reason code for the error. System Action: User Response: The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible.
316
PowerExchange Logger API RSTR failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API RSTR call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:

return_code is the PowerExchange return code for the error. reason_code is the PowerExchange reason code for the error.
The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API GLCI failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API GLCI call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:
return_code is the PowerExchange return code for the error. reason_code is the PowerExchange reason code for the error. System Action: User Response: PWX-07983 Explanation: The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API GHSQ failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API GHSQ call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:
return_code is the PowerExchange return code for the error. reason_code is the PowerExchange reason code for the error. System Action: User Response: PWX-07984 Explanation: The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API BUOW failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API BUOW call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:

The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API CHKP failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API CHKP call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:

The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible.
PWX-07000 to PWX-07999
317
PowerExchange Logger API ABRT failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API ABRT call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:

The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API DLET failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API DLET call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:
return_code is the PowerExchange return code for the error. reason_code is the PowerExchange reason code for the error. System Action: User Response: PWX-07988 Explanation: The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API ISRT failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API ISRT call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:
return_code is the PowerExchange return code for the error. reason_code is the PowerExchange reason code for the error. System Action: User Response: PWX-07989 Explanation: The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API REPL failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API REPL call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:

The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible. PowerExchange Logger API EVNT failed rc=0xreturn_code rsn=0xreason_code A PowerExchange Logger API EVNT call failed during an ECCR attempt to write data to the PowerExchange Logger. In the message text:

The ECCR ends. Use the return and reason codes to diagnose the problem. Correct the error if possible.
318
PWX-07991 Explanation: System Action: User Response: PWX-07992 Explanation: System Action: User Response: PWX-07993 Explanation: System Action: User Response: PWX-07994 Explanation: User Response: PWX-07995 Explanation: User Response: PWX-07996 Explanation: User Response: PWX-07997 Explanation: User Response: PWX-07998 Explanation: User Response: PWX-07999 Explanation: System Action: User Response:
GLCI did not return any eXtended Info. Cold Start implied A PowerExchange Logger GLCI call did not return any extended information. The ECCR cold starts. No response is required. PowerExchange Logger API Stsl(supported_call) failed rc=0xreturn_code rsn=0xreason_code The specified PowerExchange Logger API Stsl call encountered an error while attempting to write a timestamp to the PowerExchange Logger in preparation for other write calls. The ECCR ends. Review the return and reason codes. A RSTR call to the PowerExchange Logger did not return any extended information The PowerExchange Logger did not return any extended information in response to a RSTR call. ECCR processing continues. No response is required. Tracing is on Tracing is enabled. No response is required. Tracing is off Tracing is disabled. No response is required. Number of traces is n This message displays the number of traces that are enabled. No response is required. Trace level=trace_level filter=trace_filter A trace with the specified trace level and filter is enabled. No response is required. Trace trace_ID level trace_level turned on A trace with the specified trace ID and trace level is enabled. No response is required. No space for an additional trace A TRACEON request cannot be met because empty trace slots are not available. Tracing is not enabled. No response is required.
PWX-07000 to PWX-07999
319
PWX-08000 to PWX-08999
PWX-08384 Explanation: System Action: User Response: PWX-08386 Explanation: System Action: User Response: PWX-08387 Explanation: System Action: User Response: PWX-08388 Explanation: System Action: User Response: PWX-08408 Explanation: System Action: User Response: PWX-08409 Explanation: System Action: User Response: PWX-08476 Explanation: System Action: User Response: NumericSign (F) NumericSign must be set to 'F' to force UPACKED and UZONED fields to have a sign nibble of x'F.' The PowerExchange Listener aborts. Specify a valid NUMERICSIGN option. Registration Condense Option Parameter error during load of extract map The load operation is aborted review map contents and/or contact Informatica Global Customer Support Registration Source Owner Parameter error during load of extract map. The load operation is aborted. Review map contents and/or contact Informatica Global Customer Support. Registration Source Table Parameter error during load of extract map. The load operation is aborted. Review map contents and/or contact Informatica Global Customer Support. TEMPHLQ (High Level Qualifier) An invalid High Level DSN Qualifier was specified. The PowerExchange Listener aborts. Specify a valid High Level Qualifier and restart PowerExchange Listener. SUBMITTIMEOUT An invalid number of seconds before a netport job times out was specified. The valid range is 1- 86,400 seconds. The PowerExchange Listener exits. Specify a valid time. (Capture) MSGLVL An error was found with parameter MSGLVL in the Capture configuration file. The job ends. The parameter must be set to a positive number.

0. Default. Provides basic level of information concerning log processing. 1. Provides additional information.
Invalid ORACLECODEPAGE PWX code page name name The code page name was not recognized. Initialization aborts.
320
User Response:
Find the correct name for the code page. Utility ICUCHECK lists the names of code pages supported by PowerExchange. Invalid ORACLECODEPAGE PWX code page name name The code page name was not recognized. Initialization aborts. Find the correct name for the code page. Utility ICUCHECK lists the names of code pages supported by PowerExchange.
PWX-09000 to PWX-09999
PWX-09000 Explanation: System Action: User Response: Registration: Load Error. Field = APP_NAME. PowerExchange could not load the specified Capture Registration. The field 'APP_NAME' (Application Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = CONDENSE_OPT. PowerExchange could not load the specified Capture Registration. The field 'CONDENSE_OPT' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = CR_NAME. PowerExchange could not load the specified Capture Registration. The field 'CR_NAME' (Registration Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = CREG_STA. PowerExchange could not load the specified Capture Registration. The field 'CREG_STA' (Registration Status) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
321
Registration: Load Error. Field = DATAMAP_NM. PowerExchange could not load the specified Capture Registration. The field 'DATAMAP_NM' (data map name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DBID. PowerExchange could not load the specified Capture Registration. The field 'DBID' (Database ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DTL_NM. PowerExchange could not load the specified Capture Registration. The field 'DTL_NM' (PowerExchange Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = EYE. PowerExchange could not load the specified Capture Registration. The field 'EYE' (Eyecatcher String) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = FILENAME. PowerExchange could not load the specified Capture Registration. The field 'FILENAME' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IN_DB. PowerExchange could not load the specified Capture Registration. The field 'IN_DB' (Input Database) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
322
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IN_SCHEMA. PowerExchange could not load the specified Capture Registration. The field 'IN_SCHEMA' (Input Schema) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IN_TBLE. PowerExchange could not load the specified Capture Registration. The field 'IN_TBLE' (Input Table) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IN_TYPE. PowerExchange could not load the specified Capture Registration. The field 'IN_TYPE' (Input Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = MVS_NM. PowerExchange could not load the specified Capture Registration. The field 'MVS_NM' (MVS Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OBID. PowerExchange could not load the specified Capture Registration. The field 'OBID' (OB ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OUT_COLS. PowerExchange could not load the specified Capture Registration. The field 'OUT_COLS' (Number of Output Columns) could not be read. See the associated messages for further diagnostics.
PWX-09000 to PWX-09999
323
Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OUT_DB. PowerExchange could not load the specified Capture Registration. The field 'OUT_DB' (Output DB Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OUT_LOCN. PowerExchange could not load the specified Capture Registration. The field OUT_LOCN, which is the output location in the PowerExchange configuration, could not be read. Registration Load process is abandoned. See the associated messages for further diagnostics. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OUT_SCHEMA. PowerExchange could not load the specified Capture Registration. The field 'OUT_SCHEMA' (Output Schema) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OUT_TBLE. PowerExchange could not load the specified Capture Registration. The field 'OUT_TBLE' (Output Table Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = OWNER. PowerExchange could not load the specified Capture Registration. The field 'OWNER' (Registration Owner) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
324
Registration: Load Error. Field = REG_DT_TIME. PowerExchange could not load the specified Capture Registration. The field 'REG_DT_TIME' (Registration Date/Time) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = REG_TYPE. PowerExchange could not load the specified Capture Registration. The field 'REG_TYPE' (Registration Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = ROW_ID. PowerExchange could not load the specified Capture Registration. The field 'ROW_ID' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = SRC_COLS. PowerExchange could not load the specified Capture Registration. The field 'SRC_COLS' (No. of source columns) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = STRT_RBA. PowerExchange could not load the specified Capture Registration. The field 'STRT_RBA' (Start Relative Byte Address) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TERM_ID. PowerExchange could not load the specified Capture Registration. The field 'TERM_ID' (Terminal ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
PWX-09000 to PWX-09999
325
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = USER_NM. PowerExchange could not load the specified Capture Registration. The field 'USER_NM' (User name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = PWORD. PowerExchange could not load the specified Capture Registration. The field 'PWORD' (Encrypted Password) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = VRM. PowerExchange could not load the specified Capture Registration. The field 'VRM' (Version-Release-Mod Level) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = NAME. PowerExchange could not load the specified Capture Registration. The field 'NAME' (Registration Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DBTYPE. PowerExchange could not load the specified Capture Registration. The field 'DBTYPE' (Sic) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = INSTANCE. PowerExchange could not load the specified Capture Registration. The field 'INSTANCE' (Database Instance) could not be read. See the associated messages for further diagnostics.
326
Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = VERSION. PowerExchange could not load the specified Capture Registration. The field 'VERSION' (Registration version) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COLNUM_DTL. PowerExchange could not load the specified Capture Registration. The field 'COLNUM_DTL' (Column Number - PowerExchange) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_DETAIL_TYPE. PowerExchange could not load the specified Capture Registration. The field 'COL_DETAIL_TYPE' (PowerExchange Column Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_LEN. PowerExchange could not load the specified Capture Registration. The field 'COL_LEN' (Column Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_NUM. PowerExchange could not load the specified Capture Registration. The field 'COL_NUM' (Column Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
327
Registration: Load Error. Field = COL_PRECISION. PowerExchange could not load the specified Capture Registration. The field 'COL_PRECISION' (Column Precision) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_SCALE. PowerExchange could not load the specified Capture Registration. The field 'COL_SCALE' (Column Precision) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_NULLABLE. PowerExchange could not load the specified Capture Registration. The field 'COL_NULLABLE' (Column Nullable Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_SEARCHFIELD. PowerExchange could not load the specified Capture Registration. The field 'COL_SEARCHFIELD' (Column Searchfield Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COLNAME. PowerExchange could not load the specified Capture Registration. The field 'COLNAME' (Column Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COLNUM_DB2. PowerExchange could not load the specified Capture Registration. The field 'COLNUM_DB2' (Column Number for DB2) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
System Action:
328
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_TYPE. PowerExchange could not load the specified Capture Registration. The field 'COLNUM_TYPE' (Column Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COMMENT. PowerExchange could not load the specified Capture Registration. The field 'COMMENT' (Registration Comment) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = EDIT_SEQNO. PowerExchange could not load the specified Capture Registration. The field 'EDIT_SEQNO' (Registration Edit Sequence Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SCHEMA. PowerExchange could not load the specified Capture Registration. The field 'IMS_SCHEMA' (Registration IMS Schema name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_MAPNAME. PowerExchange could not load the specified Capture Registration. The field 'IMS_MAPNAME' (Registration IMS data map name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
329
Length error building filename for SAVE. PowerExchange could not load the specified Capture Registration. An error occurred trying to build one of the repeating fields (such as Columns, Datacom Element, IDMS Path record) that comprises the capture registration. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_TABLE. PowerExchange could not load the specified Capture Registration. The field 'IMS_TABLE' (Registration IMS Table name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_DBD_VERSION. PowerExchange could not load the specified Capture Registration. The field 'IMS_DBD_VERSION' (Registration IMS DBD Version) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_CAPT_OPT. PowerExchange could not load the specified Capture Registration. The field 'IMS_CAPT_OPT' (Registration IMS Capture Options) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Length error building registration filename for SAVE. PowerExchange could not save the specified Capture Registration. PowerExchange must generate a local file name based on component parts of the registration. This local file name exceeds the maximum of 'DB_MAX_NAME_LEN'(128 characters). This error is symptomatic of internal data overlay problems, because the user cannot supply components whose aggregate length exceeds the allowed maximum. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
330
Length error building group filename for SAVE. PowerExchange could not save the specified Capture Registration Group. PowerExchange must generate a local file name based on component parts of the registration group. This local file name exceeds the maximum of 'DB_MAX_NAME_LEN'(128 characters). This error is symptomatic of internal data overlay problems, because the user cannot supply components whose aggregate length exceeds the allowed maximum. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_DBD_SEGNAME. PowerExchange could not load the specified Capture Registration. The field 'IMS_DBD_SEGNAME' (Registration IMS DBD Segment Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_DBD_SEGNUM. PowerExchange could not load the specified Capture Registration. The field 'IMS_DBD_SEGNUM' (Registration IMS DBD Segment Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_DBD_DBTYPE. PowerExchange could not load the specified Capture Registration. The field 'IMS_DBD_DBTYPE' (Registration IMS DBD Database Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration not found. Do you want to amend the Extract Definition? PowerExchange could not load the specified Capture Registration. A dialog is opened prompting the user to amend the extraction map. Amend the Capture extraction map as required. Reg. Group: Load Error. Field = LOCATION PowerExchange could not load the specified Capture Registration Group. The field 'LOCATION' (sic) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned.
PWX-09000 to PWX-09999
331
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = ACCMETH PowerExchange could not load the specified Capture Registration Group. The field 'ACCMETH' (Access Method) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = INSTANCE PowerExchange could not load the specified Capture Registration Group. The field 'INSTANCE' (Database instance) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = USER_NM PowerExchange could not load the specified Capture Registration Group. The field 'USER_NM' (User Name) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = PWORD PowerExchange could not load the specified Capture Registration Group. The field 'PWORD' (Encrypted Password) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Error creating group PowerExchange could not load the specified Capture Registration Group. It could not acquire enough memory to hold the loaded registration group. This is a severe systemic error. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Resolution might require an intensive 'MEM' trace, so the user is urged to work with Informatica Global Customer Support to enable them to recreate the problem at their own site, rather than the users.
332
Reg. Group: Load Error. Field = PARM_NAME PowerExchange could not load the specified Capture Registration Group. The field 'PARM_NAME' (Registration Group Name) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Registration: Load Error. Field = IMS_COLNAME. PowerExchange could not load the specified Capture Registration. The field 'IMS_COLNAME' (IMS Column Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_COLNUM_DB2 PowerExchange could not load the specified Capture Registration. The field 'IMS_COLNUM_DB2' (IMS Column Number for DB2) could not be read. This field should always be zero in these circumstances (IMS registration). See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_COLNUM_DTL PowerExchange could not load the specified Capture Registration. The field 'IMS_COLNUM_DTL' (IMS Column Number for PowerExchange) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SEGNAME PowerExchange could not load the specified Capture Registration. The field 'IMS_SEGNAME' (IMS Column Segment Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
333
Registration: Load Error. Field = IMS_DETAIL_TYPE PowerExchange could not load the specified Capture Registration. The field 'IMS_DETAIL_TYPE' (IMS Column PowerExchange Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_COL_TYPE PowerExchange could not load the specified Capture Registration. The field 'IMS_COL_TYPE' (IMS Column Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_COL_LEN PowerExchange could not load the specified Capture Registration. The field 'IMS_COL_LEN' (IMS Column Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_KEY_COL_SEQ PowerExchange could not load the specified Capture Registration. The field 'IMS_KEY_COL_SEQ' (IMS Column Sequence within composite key) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_PRECISION PowerExchange could not load the specified Capture Registration. The field 'IMS_PRECISION' (IMS Column Precision) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SCALE PowerExchange could not load the specified Capture Registration. The field 'IMS_SCALE' (IMS Column Scale) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.

334
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_NULLABLE PowerExchange could not load the specified Capture Registration. The field 'IMS_NULLABLE' (IMS Nullable Field Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SEARCHFIELD PowerExchange could not load the specified Capture Registration. The field 'IMS_SEARCHFIELD' (IMS Column-is-Searchfield Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Access Method could not obtain database lock. The specified file is in use by another task in the system and cannot be obtained. See the associated messages for further diagnostics. The access method cannot carry on without the specified file, and returns to caller. Retry the operation after you have determined that whatever process held the lock on the required file was freed. If no such process can be identified, Contact Informatica Global Customer Support for support on which traces are required. Error Opening DB for <caller>, return code <return_code>. PowerExchange cannot open the Database that it needs to save the current registration group, as requested by the caller. See the associated messages for further diagnostics. The access method cannot carry on without the specified file, and returns to caller. Determine the cause of the error based on the return code, which is the feedback code from the PowerExchange API. Consult the supplied documentation for the meanings of these codes. API function <function> returned non-zero return code <return_code>, DBCB RCs <return_code1/return_code2/return_code3>. A generic error occurred within the PowerExchange API. In the message text:

file_name is the name of the file that was being read. function is the name of the function being processed at the time of the error. return_code is the API return code. return_code1, return_code2, and return_code3 are DBCB return codes, which are internal codes that should be reported to Informatica Global Customer Support. System Action: The access method cannot continue, and returns to the caller.
PWX-09000 to PWX-09999
335
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Error - No Load Session Work Area supplied. The CDEP Database cannot be read, because no work area exists to manage the request. Internal logic area. Normally used as a trap in product development. The user should never see the message, but instructions are provided here for completeness. See the associated messages for further diagnostics. The access method cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Could not create object <object>. PowerExchange internal processing is creating items in memory to support the user request. Internal logic area. Normally used as a trap in product development. The user should never see the message, but instructions are provided here for completeness. See the associated messages for further diagnostics. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Input Processor failed to initialize, return code<return_code>. This is an internal error that is only likely to be seen during product development. The Input Processor is an internal PowerExchange function, and problems in this area must be referred to Informatica Global Customer Support. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Input Processor - unusual end, return code<return_code>. This message provides supplementary diagnostic information, and is issued after previous messages describing a specific problem area. The return code indicates the internal response of the PowerExchange software to the problem. See the associated messages for further diagnostics. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Missing parms for delete request, return code<return_code>. Both schema and mapname must be supplied to a delete request. This message comes from an internal sanity check, and the user should not see it. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
336
Cannot add record, record sequence <sequence>, does not match file <file>. The user is trying to add a record to the database, but the request was not allowed because the internal controls have rejected it. This is most likely to occur because two users have attempted to update the same record at the same time. PowerExchange cannot continue, and returns to the caller. coordinate the update request to ensure that two users do not update the same record at the same time. Cannot add record, schema <schema>, table <table> are already used by record <record>. The user is trying to add a record to the database, but the request was not allowed because the particular record/schema combination have already been used by another registration. PowerExchange rejects the registration. Identify the registration that already uses the schema/table combination and decide how to manage your requirements. Record not found for key <key>. No record with the specified key exists on the database. This must be a Informatica Global Customer Support error, unless the user is using unorthodox methods to access the data, and supplying their own key manually. PowerExchange rejects the registration. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Memory Problem code<code> in <internal_routine>. PowerExchange internal processing is creating items in memory to support the user request. Internal logic area. Normally used as a trap in product development. The user should never see the message, but instructions are provided here for completeness. See the associated messages for further diagnostics. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SYSTEM_TYPE. PowerExchange could not load the specified Capture Registration. The field 'IMS_SYSTEM_TYPE' (sic) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SPANS_SEGMENTS. PowerExchange could not load the specified Capture Registration. The field 'IMS_SPANS_SEGMENTS' (IMS Spans Segments Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
System Action:
PWX-09000 to PWX-09999
337
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Userid <user_ID> does not have access <access> to area, return code<return_code>. The specified user ID does not have access rights, according to the users own security software. PowerExchange cannot continue, and returns to the caller. Review internal security procedures. If the user should have the requested access then update the definitions in the target systems's security software (such as RACF for MVS systems). If the user should not have access, then deal with the situation appropriately. Authorization Warning : Userid <user_ID> return code <return_code>. The specified user ID does not have access rights, according to the users own security software. PowerExchange cannot continue, and returns to the caller. Review internal security procedures. If the user should have the requested access then update the definitions in the target systems's security software (such as RACF for MVS systems). If the user should not have access, then deal with the situation appropriately. User <user_ID> is not licensed to use Changed Data Capture functions. The specified user ID does not have access rights, according to the users licensed features. PowerExchange cannot continue, and returns to the caller. Review the license and/or user authorizations. CPR Enq/Deq failed with rc<return_code>, on resource<resouce>, function<function>. On MVS systems, PowerExchange enqueues on certain system databases ('resource'). PowerExchange cannot continue, and returns to the caller. PowerExchange was unable to do this because of a system block. Combine the information in the return code and function to determine the probable cause of the failure. The most obvious and frequent reason for it is that another active task has already allocated the required database. Database error. Missing trailer in <database> database. PowerExchange cannot find the special trailer record in the specified database. PowerExchange cannot continue, and returns to the caller. The Database was damaged, probable due to it being modified by an external program such as DITTO. Add a trailer record to the database, under instruction from Informatica Global Customer Support. CDEP Load error. Field = APPLICATION PowerExchange could not load the specified CDEP Record. The field 'APPLICATION' (Application Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
338
CDEP Load error. Field = QUAL_EXT_NM PowerExchange could not load the specified CDEP Record. The field 'QUAL_EXT_NM' (Qualified Extract Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = START_FLIP PowerExchange could not load the specified CDEP Record. The field 'START_FLIP' (Start Timestamp in 2's complement form) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = STRT_CAPT_CPT PowerExchange could not load the specified CDEP Record. The field 'STRT_CAPT_CPT' (Start Capture Checkpoint) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = STRT_RBA PowerExchange could not load the specified CDEP Record. The field 'STRT_RBA' (Start Relative Byte Address) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = STRT_LRSN PowerExchange could not load the specified CDEP Record. The field 'STRT_LRSN' (Start LRSN) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = END_CAPT_CPT PowerExchange could not load the specified CDEP Record. The field 'END_CAPT_CPT' (End Capture Checkpoint) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned.
PWX-09000 to PWX-09999 339
System Action:
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = END_RBA PowerExchange could not load the specified CDEP Record. The field 'END_RBA' (End Relative Byte Address) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = END_LRSN PowerExchange could not load the specified CDEP Record. The field 'END_LRSN' (End LRSN) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = START_TYPE PowerExchange could not load the specified CDEP Record. The field 'START_TYPE' (Start of Run Type) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = START_PARM PowerExchange could not load the specified CDEP Record. The field 'START_PARM' (Start Run Parameters) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = USER_NM PowerExchange could not load the specified CDEP Record. The field 'USER_NM' (User Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = TERM_ID PowerExchange could not load the specified CDEP Record. The field 'TERM_ID' (Terminal ID) could not be read. See the associated messages for further diagnostics.
340
CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = MVS_NM PowerExchange could not load the specified CDEP Record. The field 'MVS_NM' (MVS User Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = DTL_NM PowerExchange could not load the specified CDEP Record. The field 'DTL_NM' (PowerExchange User Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXTRACT_START PowerExchange could not load the specified CDEP Record. The field 'EXTRACT_START' (Extract Start Timestamp) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXTRACT_END PowerExchange could not load the specified CDEP Record. The field 'EXTRACT_END' (Extract End Timestamp) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = REGISTRATION_NAME PowerExchange could not load the specified CDEP Record. The field 'REGISTRATION_NAME' (Registration Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
341
CDEP Load error. Field = CONDENSED_FNAME (EXT) PowerExchange could not load the specified CDEP Record. The field 'CONDENSED_FNAME' (Condensed File Name - Extract) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = CAPT_CPT PowerExchange could not load the specified CDEP Record. The field 'CAPT_CPT' (Capture Checkpoint) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = RBA PowerExchange could not load the specified CDEP Record. The field 'RBA' (RBA) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = CONDENSED_FNAME (CON) PowerExchange could not load the specified CDEP Record. The field 'CONDENSED_FNAME' (Condensed File Name - Condense) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = STATUS PowerExchange could not load the specified CDEP Record. The field 'STATUS' (Status code) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = STATUS_TS PowerExchange could not load the specified CDEP Record. The field 'STATUS_TS' (Status Timestamp) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned.
342
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = REGLK PowerExchange could not load the specified CDEP Record. The field 'REGLK' (Condense Registration Link) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = START_FLIP PowerExchange could not load the specified CDEP Record. The field 'START_FLIP' (Start Timestamp - Flipped for sorting) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINVAR1_REGISTRATION_NAME PowerExchange could not load the specified CDEP Record. The field 'AINVAR1_REGISTRATION_NAME' (Application Index Registration Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINVAR1_REG_TAG PowerExchange could not load the specified CDEP Record. The field 'AINVAR1_REG_TAG' (Application Index Registration Tag) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINVAR1_STR_SEQ PowerExchange could not load the specified CDEP Record. The field 'AINVAR1_STR_SEQ' (Application Index Start Sequence) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
343
CDEP Load error. Field = AINVAR1_STR_RES PowerExchange could not load the specified CDEP Record. The field 'AINVAR1_STR_SEQ' (Application Index Restart Token) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Could not create EXT object. PowerExchange internal processing is creating items in memory to support the user request. Internal logic area. Normally used as a trap in product development. The user should never see the message, but instructions are provided here for completeness. See the associated messages for further diagnostics. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Could not create CON object. PowerExchange internal processing is creating items in memory to support the user request. Internal logic area. Normally used as a trap in product development. The user should never see the message, but instructions are provided here for completeness. See the associated messages for further diagnostics. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINVAR1_UNACTIONED PowerExchange could not load the specified CDEP Record. The field 'AINVAR1_UNACTIONED' (Application Index Unactioned Flag) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Length <length> of TOKEN <token>. exceeds maximum <nnn>. Internal logic area. Normally used as a trap in product development. The user should never see the message, but instructions are provided here for completeness. See the associated messages for further diagnostics. PowerExchange cannot continue, and returns to the caller. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
344
CDEP Load error. Field = AINPARM_APPLICATION PowerExchange could not load the specified CDEP Record. The field 'AINPARM_APPLICATION' (Application Index Application) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINPARM_QUAL_EXT_NM PowerExchange could not load the specified CDEP Record. The field 'AINPARM_QUAL_EXT_NM' (Application Index Qualified Extract Name) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINPARM_STRT_FLIP PowerExchange could not load the specified CDEP Record. The field 'AINPARM_STRT_FLIP' (Application Index Start Timestamp - Flipped) could not be read. See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINPARM_GUI_CURR_UPDT PowerExchange could not load the specified CDEP Record. The field 'AINPARM_GUI_CURR_UPDT' could not be read. (Application Index GUI Current Update Timestamp) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = AINPARM_RST_NO PowerExchange could not load the specified CDEP Record. The field 'AINPARM_RST_NO' could not be read. (Application Index Restart Number) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = CDLDA_PAV_CREATE PowerExchange could not load the specified CDEP Record. It was attempting to create a variable portion of an Application Index record in memory as a child record). Internal logic area. Normally used as a trap in product development. The user should never see the
PWX-09000 to PWX-09999
345
message, but instructions are provided here for completeness. See the associated messages for further diagnostics. The field 'CDLDA_PAV_CREATE' could not be read. (Application Index Restart Number) See the associated messages for further diagnostics. System Action: User Response: CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Memory error. Resource <resource>, return code <return_code>. This is a general purpose diagnostic error detected by memory management functions. The resource name shows the internal table or memory block that could not be allocated. The reason code is the one returned by General Purpose routines which control memory management. CDEP functionality that was in progress is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM5_REGISTRATION_NAME PowerExchange could not load the specified CDEP Record. The field 'EXT_NM5_REGISTRATION_NAME' could not be read. (Extract Record Registration Name) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM5_REG_TAG PowerExchange could not load the specified CDEP Record. The field 'EXT_NM5_REG_TAG' could not be read. (Extract Record Registration Tag) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM5_STR_SEQ PowerExchange could not load the specified CDEP Record. The field 'EXT_NM5_STR_SEQ' could not be read. (Extract Record Start Sequence Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM5_STR_RES PowerExchange could not load the specified CDEP Record. The field 'EXT_NM5_STR_RES' could not be read. (Extract Record Start Restart Token) See the associated messages for further diagnostics.
346
CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM5_END_SEQ PowerExchange could not load the specified CDEP Record. The field 'EXT_NM5_END_SEQ' could not be read. (Extract Record End Sequence Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM5_END_RES PowerExchange could not load the specified CDEP Record. The field 'EXT_NM5_END_RES' could not be read. (Extract Record End Restart Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = CDEP_TOK_SEQ PowerExchange could not load the specified CDEP Record. The field 'CDEP_TOK_SEQ' could not be read. (CDEP Sequence Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = CDEP_TOK_RST PowerExchange could not load the specified CDEP Record. The field 'CDEP_TOK_RST' could not be read. (CDEP Restart Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. CDEP Load error. Field = EXT_NM_TOK_SEQ PowerExchange could not load the specified CDEP Record. The field 'EXT_NM_TOK_SEQ' could not be read. (CDEP Extract Sequence Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
347
CDEP Load error. Field = EXT_NM_TOK_RST PowerExchange could not load the specified CDEP Record. The field 'EXT_NM_TOK_RST' could not be read. (CDEP Extract Restart Token) See the associated messages for further diagnostics. CDEP Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_COLLECTOR_START PowerExchange could not load the specified capture registration. The field IMS_COLLECTOR_START (IMS ECCR start time) could not be read. See the associated messages for diagnostic information. Registration load process ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database that contains the failing registration, with information on the software level being used. Registration: Load Error. Field = IMS_IMS_DBD_NAME PowerExchange could not load the specified Capture Registration. The field 'IMS_IMS_DBD_NAME' (IMS DBD Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_JOURNAL_NAME PowerExchange could not load the specified Capture Registration. The field 'AS4_JOURNAL_NAME' (AS400 Journal Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_JOURNAL_LIB PowerExchange could not load the specified Capture Registration. The field 'AS4_JOURNAL_LIB' (AS400 Journal Library Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
348
Registration: Load Error. Field = AS4_START_POS PowerExchange could not load the specified Capture Registration. The field 'AS4_START_POS' (AS400 Start Position) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_COLNAME PowerExchange could not load the specified Capture Registration. The field 'AS4_COLNAME' (AS400 Column Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_COLNUM_DB2 PowerExchange could not load the specified Capture Registration. The field 'AS4_COLNUM_DB2' (AS400 DB2 Column Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_COLNUM_DTL PowerExchange could not load the specified Capture Registration. The field 'AS4_COLNUM_DTL' (AS400 PowerExchange Column Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_SEGNAME PowerExchange could not load the specified Capture Registration. The field 'AS4_SEGNAME' (AS400 Segment Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
349
Registration: Load Error. Field = AS4_DETAIL_TYPE PowerExchange could not load the specified Capture Registration. The field 'AS4_DETAIL_TYPE' (AS400 PowerExchange Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_COL_TYPE PowerExchange could not load the specified Capture Registration. The field 'AS4_COL_TYPE' (AS400 Column Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_COL_LEN PowerExchange could not load the specified Capture Registration. The field 'AS4_COL_LEN' (AS400 Column Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_KEY_COL_SEQ PowerExchange could not load the specified Capture Registration. The field 'AS4_KEY_COL_SEQ' (AS400 Key Column Sequence Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_PRECISION PowerExchange could not load the specified Capture Registration. The field 'AS4_PRECISION' (AS400 Column Precision) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
350
Registration: Load Error. Field = AS4_SCALE PowerExchange could not load the specified Capture Registration. The field 'AS4_SCALE' (AS400 Column Scale) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_NULLABLE PowerExchange could not load the specified Capture Registration. The field 'AS4_NULLABLE' (AS400 Column Nullable Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_SEARCHFIELD PowerExchange could not load the specified Capture Registration. The field 'AS4_SEARCHFIELD' (AS400 Column Is A Searchfield Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_RECEIVER_NAME PowerExchange could not load the specified Capture Registration. The field 'AS4_RECEIVER_NAME' (AS400 Receiver Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS4_RECEIVER_LIB PowerExchange could not load the specified Capture Registration. The field 'AS4_RECEIVER_LIB' (AS400 Receiver Library Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
351
Registration: Load Error. Field = REGISTRATION_TAG PowerExchange could not load the specified Capture Registration. The field 'REGISTRATION_TAG' (Sic) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = REAL FILE NAME PowerExchange could not load the specified Capture Registration. The field 'REAL FILE NAME' (Sic) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DATA SET NAME PowerExchange could not load the specified Capture Registration. The field 'DATA SET NAME' (Sic) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = ADABAS FILE NUMBER PowerExchange could not load the specified Capture Registration. The field 'ADABAS FILE NUMBER' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = ADABAS DB ID PowerExchange could not load the specified Capture Registration. The field 'ADABAS DB ID' (Adabas Database ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM DB ID PowerExchange could not load the specified Capture Registration. The field 'DCOM DB ID' (Datacom Database ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
System Action:
352
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM_TABLENAME PowerExchange could not load the specified Capture Registration. The field 'DCOM_TABLENAME' (Datacom Database ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM_TABLEID PowerExchange could not load the specified Capture Registration. The field 'DCOM_TABLEID' (Datacom Table ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM_RECORDLENGTH PowerExchange could not load the specified Capture Registration. The field 'DCOM_RECORDLENGTH' (Datacom Record Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM_RECOVERYFLAG PowerExchange could not load the specified Capture Registration. The field 'DCOM_RECOVERYFLAG' (Datacom Recovery Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM_VERSION PowerExchange could not load the specified Capture Registration. The field 'DCOM_VERSION' (Datacom Version) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
353
Registration: Load Error. Field = DCOM ELEMENT NAME PowerExchange could not load the specified Capture Registration. The field 'DCOM ELEMENT NAME' (Datacom Element Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM ELEMENT OFFSET PowerExchange could not load the specified Capture Registration. The field 'DCOM ELEMENT OFFSET' (Datacom Element Offset) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = DCOM_ELEMENT LENGTH PowerExchange could not load the specified Capture Registration. The field 'DCOM ELEMENT LENGTH' (Datacom Element Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_KEYLEN PowerExchange could not load the specified Capture Registration. The field 'IMS_KEYLEN' (IMS Key Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_KEYSTART PowerExchange could not load the specified Capture Registration. The field 'IMS_KEYSTART' (IMS Key Start) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
354
Registration: Load Error. Field = IMS_DBD_DSNAME PowerExchange could not load the specified Capture Registration. The field 'IMS_DBD_DSNAME' (IMS DBD Dataset Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_CVNAME PowerExchange could not load the specified Capture Registration. The field 'IDMS_CVNAME' (IDMS CV Dataset Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_BASE_RECNAME PowerExchange could not load the specified Capture Registration. The field 'IDMS_BASE_RECNAME' (IDMS Base Record Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_BASE_RECID PowerExchange could not load the specified Capture Registration. The field 'IDMS_BASE_RECID' (IDMS Base Record ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_DBNAME PowerExchange could not load the specified Capture Registration. The field 'IDMS_DBNAME' (IDMS Database Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
355
Registration: Load Error. Field = IDMS_COMPRESS_IND PowerExchange could not load the specified Capture Registration. The field 'IDMS_COMPRESS_IND' (IDMS Compress Indicator) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_VARIABLE_IND PowerExchange could not load the specified Capture Registration. The field 'IDMS_VARIABLE_IND' (IDMS Variable Indicator) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_CHAIN_IND PowerExchange could not load the specified Capture Registration. The field 'IDMSP_CHAIN_IND' (IDMS Path - Chain Indicator) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_IDMSP_RECORD_NAME PowerExchange could not load the specified Capture Registration. The field 'IDMSP_IDMSP_RECORD_NAME' (IDMS Path - Record Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_SET_NAME PowerExchange could not load the specified Capture Registration. The field 'IDMSP_SET_NAME' (IDMS Path - Set Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
356
Registration: Load Error. Field = IDMSP_RECORD_ID PowerExchange could not load the specified Capture Registration. The field 'IDMSP_RECORD_ID' (IDMS Path - Record ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_COMPRESS_IND PowerExchange could not load the specified Capture Registration. The field 'IDMSP_COMPRESS_IND' (IDMS Path - Compress Indicator) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_VARIABLE_IND PowerExchange could not load the specified Capture Registration. The field 'IDMSP_VARIABLE_IND' (IDMS Path - Variable Indicator) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_CONN_TYPE PowerExchange could not load the specified Capture Registration. The field 'IDMSP_CONN_TYPE' (IDMS Path - Connection Type) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. DBD Name not supplied by caller An internal function call was verified for correctness, but an error was detected. The internal function is 'DBD Load'. The error in the call is that the name of the DBD to be loaded was not supplied. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics.
PWX-09000 to PWX-09999
357
DBD File Name not supplied by caller An internal function call was verified for correctness, but an error was detected. The internal function is 'DBD Load'. The error in the call is that the file name containing the DBD to be loaded was not supplied. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. Recon Name not supplied by caller An internal function call was verified for correctness, but an error was detected. The internal function is 'Recon Name'. The error in the call is that the file name containing the DBD to be loaded was not supplied. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. Recon File Name not supplied by caller An internal function call was verified for correctness, but an error was detected. The internal function is 'Recon File Name. The error in the call is that the file name containing the DBD to be loaded was not supplied. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. DBD Segment Name not supplied by caller An internal function call was verified for correctness, but an error was detected. The internal function is 'DBD Segment Name.' The error in the call is that the file name containing the DBD to be loaded was not supplied. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. I/O Operation <operation> on data set <data_set> failed. System code <system_code>. The specified operation - read, write, open, close - failed on the specified data set. The return code indicating the error is supplied in the system_code field. A serious system error occurred, which might indicate corruption of the data set. The I/O operation is abandoned, along with any API services that were in progress. Contact Informatica Global Customer Support with existing diagnostics. ISB Enq/Deq failed with rc<return_code>, on resource <resource>, function <function>. This is not really an error, but a safety feature to avoid potential corruption of user data. The Access Method 'ISB' needs a resource that it cannot obtain. It is requesting the resource in support of a user request made through the PowerExchange API. The user request in progress at the time, is reported in the'function' field. The resource that the Access Method cannot obtain, is reported in the 'resource' field. The return code indicating the error is supplied in the return_code field. The I/O operation is abandoned, along with any API services that were in progress.
System Action:
358
User Response:
If you are able to determine what is causing the contention (such as two identical processes running at the same time), then you can fix the problem locally. Otherwise, Contact Informatica Global Customer Support with existing diagnostics. Invalid function verb <function_verb>. An internal function call was verified for correctness, but an error was detected. The verb supplied in the SQL by the caller, and quoted in the message, is unrecognized. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. Dynamic allocation of <resource> failed. RC <return_code>. The specified resource is required to complete the current process, but PowerExchange was unable to acquire it. The function call request is rejected. The caller issues supplementary messages, which elaborate on the error. Perform the following actions: 1. Consult operating system supplier manuals for dynamic allocation return codes. 2. Contact Informatica Global Customer Support with existing diagnostics.
Load of DBD <IMS_DBD> failed. Return Code <return_code>, Reason Code <reason_code>. The specified IMS DBD could not be loaded. The return and reason codes are the native IMS ones, describing the error. This is probably an IMS problem. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Consult the IBM IMS return codes documentation. 2. Contact Informatica Global Customer Support with existing diagnostics.
Load of Module <load_module> failed. Return Code <return_code>, Reason Code <reason_code>. The specified load module could not be loaded. The return and reason codes are native to IMS and describe the error. This is probably an IMS problem. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Consult the IBM IMS return codes documentation. 2. Contact Informatica Global Customer Support with existing diagnostics.
No image copy has been taken for table <table> in <database>. The DB2 image copy for the specified table could not be found in the database. Processing ends. Review other messages to discount environmental problems. Contact your DB2 DBA. No segments found for DBD <DBD>. The specified DBD appears to lack segments. This is probably an IMS problem.
PWX-09000 to PWX-09999
359
The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Ensure that correct IMS parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
PDS List could not be built. RC<return_code>. The software is trying to obtain a list of the members of a partitioned-format data set, but was not able to do so. This is probably an IMS problem. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. DSN <DSN> does not contain member <member>. The specified partitioned data set does not contain the specified member. This is probably an IMS problem. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Ensure that correct IMS parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
No segments exits found for DBD <DBD>. The specified DBD does not appear to have any segment extensions, when it should. This is probably an IMS problem. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Ensure that correct IMS parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
TableSpace <tablespace> in <database> is compressed. Image copy reading not supported. Compressed tables cannot be read. The specified tablespace is compressed. Processing ends. If you believe the tablespace is not compressed, review other messages to discount environmental issues. Consult your DBA. Error reading page from file <file>. Self-explanatory. This is probably an IMS problem. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Ensure that correct IMS parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
360
Dictionary Page found. Image copy reading not supported for compressed TS. Self-explanatory. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Use the following procedure to correct the problem: 1. Ensure that correct parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
Location for the remote DB2 catalog not specified. The caller has not supplied a location for the desired remote DB2 catalog, but this information is mandatory. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Use the following procedure to correct the problem. 1. Ensure that correct parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
Error code <error_code> searching DSN <DSN> for member <member>. The specified member could not be found in the stated data set. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Use the following procedure to correct the problem. 1. Ensure that correct parameters have been set in the dbmover.cfg parameters. It is possible that the wrong DSN was specified in the parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
IMS config <config_parameter_name> not found in Listener Parms. The specified configuration parameter name could not be found in the PowerExchange Listener configuration parameters. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Do the following: 1. Ensure that correct IMS parameters have been set in the dbmover.cfg parameters. 2. Contact Informatica Global Customer Support with existing diagnostics.
Datamap name <data_map_name> is invalid. The data map passed a parameter with an invalid value. It should have a schema_name.map_name format The data map is not created. Use a valid data map name. Datamap name schema_name.map_name not generated because location=local. The data map was not generated because it must go through a PowerExchange Listener. The data map is not created. Change the location and run the job under a PowerExchange Listener.
PWX-09000 to PWX-09999
361
The LOGSID entry name <LOGSID_name> is too long (maximum 8). The LOGSID name passed as a parameter is too long. It should be no more than eight characters The task that encounters the error ends. Use a valid LOGSID name. The LOGSID entry name <LOGSID_name> not found The LOGSID name passed as a parameter was not found in dbmover.cfg for the specified location The task that encounters the error ends. Use a valid LOGSID name and/or ensure that logsid entry exists in dbmover.cfg for the location specified. No LOGSID entries found in config file No LOGSID entries were found in dbmover.cfg for the specified location. The task that encounters the error ends. Use a valid logsid name and/or ensure that logsid entry exists in dbmover.cfg for the location specified. No EXIT= found for DBD <DBD>. The specified DBD appears to not have EXIT= specified. It is therefore impossible to extract the log status. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Ensure that EXIT= is used with DBD's where log-based capture is required. Name mismatch for segment code code. Data map segment name name_1. File segment name name_2. The segment name read from the IMS unload file does not match the segment name in the data map. Processing ends. Ensure that the data map and IMS unload file have the same segment names. Dataset data_set_name has invalid format for database_type IMS Unload. For the specified database type, the specified data set does not have the correct IMS unload data set format. Processing ends. Ensure that the data set has the correct IMS unload data set format. DBAM_BASE_Point: Locate request for file <file_name> made without implicit key access option. An attempt was made to start processing on a keyed file without previously specifying that the file should be processed in keyed sequence. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
362
DBAM_BASE_Point: Keyed access requested for file <file> that has no key fields specified. An attempt was made to start processing on a keyed file in keyed sequence where the requested file is not a keyed file. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. DBAM_BASE_Point: Locate operation for key value <key_value> on file <file> failed with reason code <reason_code>. An attempt made to start processing on a keyed file has resulted in an unexpected error being issued by the system. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error, the name of the file, the value of the key, and the reason code reported in the error. DBAM_BASE_Delete: Delete request for file <file> failed with reason code <reason_code>. An attempt made to delete a record on a keyed file has resulted in an unexpected error being issued by the system. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error, the name of the file and the reason code reported in the error. DBAM_BASE_Update: Update request for file <file> failed with reason code <reason_code>. Bytes Returned = <nnn>. An attempt made to update a record on a keyed file has resulted in an unexpected error being issued by the system. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error, the name of the file, the reason code reported in the error and the number of bytes returned. Failed to add member member to file An attempt made to add a member to a file has resulted in an unexpected error being issued by the system. The task might allow time to resolve through a console message before terminating when no further retries are requested. Otherwise The task that encounters the error ends. Investigate any local cause and resolve, failing this, Contact Informatica Global Customer Support, specifying the function being performed at the time of the error, the name of the file, and any extra information on associated messages. Invalid AS400 Meta Data Request specified <request_type>. An internal function call was verified for correctness, but an error was detected. The verb supplied in the SQL by the caller, and quoted in the message, is unrecognized. The function call request is rejected. Contact Informatica Global Customer Support with existing diagnostics.
PWX-09000 to PWX-09999
363
AS400 Meta Data Request <request_type> failed calling QUSLRCD API for file <library/file>. API error = <error_message_ID> - <error_message>. An internal function call was verified for correctness, but an error was detected by an API call. The function call request is rejected. Contact Informatica Global Customer Support with existing diagnostics. AS400 Meta Data Request <request_type> failed calling QUSPTRUS API for file <library/file>. API error = <error_message_ID> - <error_message>. An internal function call was verified for correctness, but an error was detected by an API call. The function call request is rejected. Contact Informatica Global Customer Support with existing diagnostics. AS400 Meta Data Request <request_type> failed calling QUSLFLD API for file <library/file>. API error = <error_message_ID> - <error_message>. An internal function call was verified for correctness, but an error was detected by an API call. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. Expected QADBXREF field DBXLFI length <length> data <data>. Actually read length <length> data <data>. An attempt to read a record from table QSYS/QADBXREF to find a short physical file name from a long table name was not successful. The expected length and data shows what was requested by the caller of the AS4COLS API. The actual read values shows what was actually read. This situation might arise when processing a table name longer than 10 characters, or a table name containing special characters such as pound or yen signs. The function call request is rejected. The caller has to deal with it, and issue supplementary messages, to elaborate on the error. Contact Informatica Global Customer Support with existing diagnostics. Error receiving message from user <user_ID>. Reason reason_code. While receiving a message from the specified user ID, an error occurred. No response is required. Number of tokens <nnn> exceeds maximum allowed in SQL string <SQL_string>. The software is performing an internal operation to split the contents of a string into a set of discrete items ('tokens'). The number of tokens found is greater than the allowed maximum. The most likely cause of this is a memory overlay that has corrupted the source string. This kind of message is primarily a development aid, and should not be seen by the user in production status. The internal parsing operation is abandoned, and processing of the underlying user request ends. Contact Informatica Global Customer Support for support on which traces are required, along with information on the software level being used. At least the 'DTLAMMQS' trace is needed.
364
Invalid Data Request type in SQL - <SQL_string>. This kind of message is primarily a development aid, and should not be seen by the user in production status. Two parts of PowerExchange are communicating with each other through a character string in internal SQL format. The receiving software does not recognize the 'request type' verb in the SQL, which is displayed in the message for debugging. The internal request is abandoned, and processing ends. Contact Informatica Global Customer Support for support on which traces are required, along with information on the software level being used. At least the 'DTLAMMQS' trace is needed. Could not generate a tag. Return Code <return_code>. This kind of message is primarily a development aid, and should not be seen by the user in production status. A 'tag' is an internally generated value that represents a unique value. There are many reasons why tag generation could conceivably fail, but the return code indicates this to Informatica Global Customer Support. The internal request is abandoned, and processing ends. Contact Informatica Global Customer Support for support, quoting the full text of the message. Could not verify a tag. Return Code <return_code>. This kind of message is primarily a development aid, and should not be seen by the user in production status. A 'tag' is an internally generated value that represents a unique value. After generation, the new tag is internally verified. There are many reasons why tag verification could conceivably fail, but the return code indicates this to Informatica Global Customer Support. The internal request is abandoned, and processing ends. Contact Informatica Global Customer Support for support, quoting the full text of the message. Registration: Load Error. Field = IMS_SEGCODE PowerExchange could not load the specified Capture Registration. The field 'IMS_SEGCODE' (IMS Segment Code) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IMS_SEGPARENTCODE PowerExchange could not load the specified Capture Registration. The field 'IMS_SEGPARENTCODE' (IMS Segment Parent Code) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
365
Registration: Load Error. Field = IMS_SEGLEVEL PowerExchange could not load the specified Capture Registration. The field 'IMS_SEGLEVEL' (IMS Segment level) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = ALLCOLS_FLAG PowerExchange could not load the specified Capture Registration. The field 'ALLCOLS_FLAG' (All Columns Selected Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IS_DOC_FLAG PowerExchange could not load the specified Capture Registration. The field 'IS_DOC_FLAG' (Registration-is-a-document Flag) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_KEYOFF. PowerExchange could not load the specified Capture Registration. The field 'COL_KEYOFF' (Column Key Offset) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = COL_KEYLEN. PowerExchange could not load the specified Capture Registration. The field 'COL_KEYLEN' (Column Key Length) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
366
Registration: Load Error. Field = COL_KEYDBNAME. PowerExchange could not load the specified Capture Registration. The field 'COL_KEYDBNAME' (Column Key DB Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Save Error. IMS TAG <IMS_tag> and Instance <instance> combination are already used by record <record>. PowerExchange could not save the specified Capture Registration. The combination of TAG and Instance form a unique value. After it was taken, no new registrations might reuse it. The specified record on the database is already using this TAG/Instance combo. Registration Save process is abandoned. Review whether the old or new registration should be the active one. Delete as appropriate. Registration: Load Error. Field = IDMS_SUBSCHNAME PowerExchange could not load the specified Capture Registration. The field 'IDMS_SUBSCHNAME' (IDMS Sub-Schema Name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = ORACLE_SID PowerExchange could not load the specified Capture Registration. The field 'ORACLE_SID' (Oracle SID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = ORACLE_SLG PowerExchange could not load the specified Capture Registration. The field 'ORACLE_SLG' (Oracle SLG) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TIM_DBNAME PowerExchange could not load the specified Capture Registration. The field 'TIM_DBNAME' (Turbo Image DB name) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
PWX-09000 to PWX-09999 367
System Action:
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TIM_DSNO PowerExchange could not load the specified Capture Registration. The field 'TIM_DSNO' (Turbo Image Data Set Number) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TIM_GROUP PowerExchange could not load the specified Capture Registration. The field 'TIM_GROUP' (Turbo Image Group ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TIM_ACCOUNT PowerExchange could not load the specified Capture Registration. The field 'TIM_ACCOUNT' (Turbo Image Account ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TIM_CODEPAGE PowerExchange could not load the specified Capture Registration. The field 'TIM_CODEPAGE' (Turbo Image Codepage ID) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = TIM_VOLUMESET PowerExchange could not load the specified Capture Registration. The field 'TIM_VOLUMESET' (Turbo Image Volumeset) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
368
Registration: Load Error. Field = TIM_LOCATION PowerExchange could not load the specified Capture Registration. The field 'TIM_LOCATION' (Turbo Image Location) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = CHANGED_MARKER PowerExchange could not load the specified Capture Registration. The field 'CHANGED' (Column Changed Marker) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = AS400_Internal_Time PowerExchange could not load the specified Capture Registration. The field 'AS400_Internal_Time'could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = MSS_DBSVR PowerExchange could not load the specified Capture Registration. The field 'MSS_DSTSVR' (Microsoft SQL Server Database Server) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = MSS_DB PowerExchange could not load the specified Capture Registration. The field 'MSS_DSTSVR' (Microsoft SQL Server Database) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PWX-09000 to PWX-09999
369
Registration: Load Error. Field = MSS_TBL PowerExchange could not load the specified Capture Registration. The field 'MSS_DSTSVR' (Microsoft SQL Server Table) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = MSS_DSTSVR PowerExchange could not load the specified Capture Registration. The field 'MSS_DSTSVR' (Microsoft SQL Server Distribution Server) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = MSS_DSTDB PowerExchange could not load the specified Capture Registration. The field 'MSS_DSTSVR' (Microsoft SQL Server Distribution Database) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = MSS_ARTICLE PowerExchange could not load the specified Capture Registration. The field 'MSS_ARTICLE' (Microsoft SQL Server Article Id) could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Value of property <property_value> not within range <nnn> to <nnn> PowerExchange could not load the specified Capture Registration. The field 'PWR_codepage_num'could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
370
Registration: Load Error. Field = PWR_codepage_num PowerExchange could not load the specified Capture Registration. The field 'PWR_codepage_num'could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = CCSID PowerExchange could not load the specified Capture Registration. The field 'CCSID'could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_PAGEGROUP PowerExchange could not load the specified Capture Registration. The field 'IDMS_PAGEGROUP' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_RADIX PowerExchange could not load the specified Capture Registration. The field 'IDMS_RADIX' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_AREA_NAME PowerExchange could not load the specified Capture Registration. The field 'IDMS_AREA_NAME' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_PAGEGROUP PowerExchange could not load the specified Capture Registration. The field 'IDMSP_PAGEGROUP' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned.
System Action:
PWX-09000 to PWX-09999
371
User Response:
Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_RADIX PowerExchange could not load the specified Capture Registration. The field 'IDMSP_RADIX' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_AREA_NAME PowerExchange could not load the specified Capture Registration. The field 'IDMSP_AREA_NAME' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_MINIMUM_ROOT_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMS_MINIMUM_ROOT_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_DATA_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMS_DATA_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMS_PREFIX_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMS_PREFIX_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
372
Registration: Load Error. Field = IDMS_CONTROL_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMS_CONTROL_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_MINIMUM_ROOT_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMSP_MINIMUM_ROOT_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_DATA_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMSP_DATA_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_PREFIX_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMSP_PREFIX_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Registration: Load Error. Field = IDMSP_CONTROL_LENGTH PowerExchange could not load the specified Capture Registration. The field 'IDMSP_CONTROL_LENGTH' could not be read. See the associated messages for further diagnostics. Registration Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. Oracle ID Oracle_ID not found in configuration The specified Oracle ID is not defined in an ORACLEID statement in the DBMOVER configuration file. If the Oracle registration group accesses the Oracle database using a remote PowerExchange Listener, the PowerExchange Listener configuration file is in error.
PWX-09000 to PWX-09999
373
Processing ends. Add an ORACLEID statement for the specified Oracle instance to the DBMOVER configuration file, or if you use a remote PowerExchange Listener, correct the PowerExchange Listener configuration. Registration: Load Error. Field = IDMS_PRESSPACK_COMPRESSED_IND PowerExchange cannot load the specified capture registration because it cannot read the IDMS_PRESSPACK_COMPRESSED_IND field. The registration load process fails. For more information about this error, see the messages that accompany this one in the message log. To run traces, contact Informatica Global Customer Support to find out which traces are required. Also give Customer Support a copy of the database that contains the failing registration and information about its software level. Registration: Load Error. Field = IDMS_PRESSPACK_DCTABLE_NAME PowerExchange cannot load the specified capture registration because it cannot read the IDMS_PRESSPACK_DCTABLE_NAME field. The registration load process fails. For more information about this error, see the messages that accompany this one in the message log. To run traces, contact Informatica Global Customer Support to find out which traces are required. Also give Customer Support a copy of the database that contains the failing registration and information about its software level. Registration: Load Error. Field = IDMSP_PRESSPACK_COMPRESSED_IND PowerExchange cannot load the specified capture registration because it cannot read the IDMSP_PRESSPACK_COMPRESSED_IND field. The registration load process fails. For more information about this error, see the messages that accompany this one in the message log. To run traces, contact Informatica Global Customer Support to find out which traces are required. Also give Customer Support a copy of the database that contains the failing registration and information about its software level. Registration: Load Error. Field = IDMSP_PRESSPACK_DCTABLE_NAME PowerExchange cannot load the specified capture registration because it cannot read the IDMSP_PRESSPACK_DCTABLE_NAME field. The registration load process fails. For more information about this error, see the messages that accompany this one in the message log. To run traces, contact Informatica Global Customer Support to find out which traces are required. Also give Customer Support a copy of the database that contains the failing registration and information about its software level. REGF: An invalid registration tag <registration_tag> was passed to the registration tag encoder. An internal PowerExchange process attempted to call an internal registration tag encoding mechanism, and passed an invalid registration tag to the encoding function. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
374
REGF: A null or zero length attribute parameter (position <nth_attribute>) was passed to the registration tag encoder. An internal PowerExchange process attempted to call an internal registration tag encoding mechanism, and passed a null or zero length attribute parameter to the encoding function. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: A null or zero length value parameter (position <nth_value>) was passed to the registration tag encoder. An internal PowerExchange process attempted to call an internal registration tag encoding mechanism, and passed a null or zero length value parameter to the encoding function. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: Registration tag <tag_name> overrides generated length <length_of_tag_plus_overrides> exceeds allowed max <maximum_allowable_length>. Too much override data is being specified for the associated Capture registration. Processing ends. You must reduce the number of overrides you are specifying for this registration in the session you are trying to run.
Note: The generated override registration tag is printed in the PowerExchange log file of the
PowerExchange Listener that is running your session. PWX-09714 Explanation: System Action: User Response: REGF: Registration tag <tag_name> length <length_of_tag> exceeds allowed max <maximum_allowable_length>. The base Capture registration tag name passed to the internal PowerExchange encode/decode routine is too long. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: Base Registration tag <tag_name> has an invalid character <character>. The base Capture registration tag name passed to the internal PowerExchange encode/decode routine has a character that is not allowed. Processing ends. If you have manually named the Capture registration tag, rename it without the offending character. If not, contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: Base Registration tag <tag_name> has a malformed override attribute name <attribute_name>. The override Capture registration tag name passed to the internal PowerExchange encode/decode routine contains an attribute name that is improperly formatted.
PWX-09000 to PWX-09999
375
Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PowerExchange Listener that is running your session. PWX-09718 Explanation: System Action: User Response: REGF: Base Registration tag <tag_name> attribute <attribute_name> has a malformed value <attribute_value>. The override Capture registration tag name passed to the internal PowerExchange encode/decode routine contains an attribute value that is improperly formatted. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PowerExchange Listener that is running your session. PWX-09719 Explanation: System Action: User Response: REGF: Input attribute <attribute_number> duplicates attribute <attribute_name> of base registration tag <registration_tag>. The override Capture registration attribute passed to the internal PowerExchange encode/decode routine is a duplicate of one that exists on the input registration tag. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: Input attributes <attribute_number> and <attribute_number> named <attribute_name> of base registration tag <registration_tag> are duplicates. Duplicate override Capture registration attributes were passed to the internal PowerExchange encode/decode routine. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: Existing attributes <attribute_number> and <attribute_number> named <attribute_name> of base registration tag <registration_tag> are duplicates. The registration tag passed to the internal PowerExchange encode/decode routine contained duplicate attributes. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used. REGF: An override registration tag had a zero-length base registration name. The internal registration tag encoding mechanism was passed a registration name that began with an underscore character. Processing ends.
376
User Response:
If you have attempted to modify your registration tag name, ensure that you did not use the underscore ('_') character. If you have not attempted to modify your registration tag name, contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
Note: The input registration tag is printed in the PowerExchange log file of the
PowerExchange Listener that is running your session. PWX-09723 Explanation: System Action: User Response: REGF: An override registration tag had a zero-length attribute name. The internal registration tag encoding mechanism was passed an invalid override registration tag. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PowerExchange Listener that is running your session. PWX-09724 Explanation: System Action: User Response: REGF: The <attribute_name> attribute of an override registration tag had a zero-length value. The internal registration tag encoding mechanism was passed an invalid override registration tag. Processing ends. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the database containing the failing registration, along with information on the software level being used.
PowerExchange Listener that is running your session. PWX-09725 Explanation: System Action: User Response: PWX-09750 Explanation: Registration tag override attribute <attribute_name> has an invalid format. An override specified for a CAPXRT extraction contains invalid characters. The task that encounters the error ends. Contact Informatica Global Customer Support. This is an internal error. DTLCMD information command. This message provides one of the following types of information for the specified command:
command entered command failed invalid command input invalid User Response: PWX-09751 Explanation: System Action: User Response: No response is required. User user_ID logon failure. The specified user ID could not be logged on. The user ID and password are not valid. Processing ends. Verify that the user ID and password for the target system are correct. Or, change the security requirements on the target system by using the SECURITY parameter in the DBMOVER configuration file.
PWX-09000 to PWX-09999 377
User <user_ID> is not licensed to use TIM Database functions. Caller is not licensed. The request fails. Verify that the TurboIMAGE access module license is still valid. Number of tokens <nnn> in SQL string <SQL_string> exceeds maximum allowed. Cannot parse SQL string: too many tokens. The request fails. Simplify the SQL string. Unrecognized function <function>. SQL function verb not recognized. The request fails. Supply a valid SQL function verb. Invalid Data Request type in SQL - <SQL_string>. Cannot identify SQL function type. The request fails. Supply a valid SQL data request type. Unable to prepare work area to hold the results of the request, rc <return_code>. Cleanup after the previous DESCRIBE cycle failed. The request fails. Internal error; report to Informatica Global Customer Support. Return Code <return_code> from <operation> on Set <set> in Database <database>. Function <function>. An error code was returned while reading from the database. Associated messages should identify problem. The request fails. Resolve problem and retry. There are no Sets in Database <database>. Unable to recover database data set information. The request fails. Verify that the supplied password provides read access to the database. The setname supplied <set_name> is not recognized as a member of Database <database>. Supplied data set name not found. The request fails. Verify that a valid data set name was supplied, and that the supplied password has read access to the data set,
378
Could not allocate poolid <poolid_name>, rc <return_code>. An attempt to allocate memory off the nominated poolid failed. The DTLAMCSR access method returns this error to the calling software. Collect evidence and contact Informatica Global Customer Support. User is not licensed for this access method. The user does not hold a license key for the access method. The DTLAMCSR access method returns this error to the calling software. Obtain an appropriate extension to the license key. Member DBCB not connected. DBCB is <description>. The DBCB is not connected. The DTLAMCSR access method returns this error to the calling software. Collect evidence and contact Informatica Global Customer Support. Process <function_name> given invalid DBCB at <address>, with number <number>. This message is informational. The DTLAMCSR access method returns this error to the calling software. Collect evidence and contact Informatica Global Customer Support. Supporting file access layer returns rc<number>, text<reason>. The underlying file access mechanism has returned an error. The DTLAMCSR access method returns this error to the calling software. Attempt to resolve reason for failure, such as invalid file names, permissions failures and so on by examining the reason text. If this cannot be resolved, collect evidence and contact Informatica Global Customer Support. SQL Error : <text_string>. The input SQL string contains an error in syntax or values supplied. The DTLAMCSR access method returns this error to the calling software. Correct the error identified in the text string and resubmit. Error allocating memory <text_string>, rc <return_code>. The system was unable to allocate sufficient memory. The DTLAMCSR access method returns this error to the calling software. Collect evidence and contact Informatica Global Customer Support. Critical error in value <text_string>. Explanation <text_string>. A critical data item or computed value contains an error. The DTLAMCSR access method returns this error to the calling software. Use the explanation text string in the message to correct the error. Then resubmit the request. If you cannot resolve the error, contact Informatica Global Customer Support.
PWX-09000 to PWX-09999
379
Restart data mismatch - VERSION should be equal in both RI <text_string> and SEQ <text_string>. A call to validate restart information against the catalog failed. The DTLAMCSR access method returns this error to the calling software. Correct the information input to RI and SEQ values in the SQL string. Invalid restart data supplied - RI=<text_string>, SEQ= <text_string>. There is a conflict between the RI and SEQ components in the input SQL. The DTLAMCSR access method returns this error to the calling software. Correct the information input to RI and SEQ values in the SQL string. Requested verb for file access not recognized <verb_number>. Access to a file cannot be made as the verb is not open/close/read. The DTLAMCSR access method returns this error to the calling software. Collect evidence and contact Informatica Global Customer Support. Validation of supplied block/offset restart values <block_number> offset fails (catalog values <block_numberoffset>). The supplied RI and SEQ string values do not match known values as read from the catalog. The DTLAMCSR access method returns this error to the calling software. Correct the values and resubmit. catalog read failed, reason <text_string> rc <return_code>. Attempting to open or read from the catalog has failed. The DTLAMCSR access method returns this error to the calling software. Correct the error described in the output message and resubmit. Restart data mismatch - FILE in RI greater than FILE in SEQ, RI <text_string> and SEQ <text_string>. A call to validate restart information against the catalog failed. The DTLAMCSR access method returns this error to the calling software. Correct the information input to RI and SEQ values in the SQL string. Presspack error : <text_string>. An error occurred when PowerExchange invoked the Presspack decompression routine IDMSUNPS during CDC processing. The IDMS access method returns this error. Correct the error identified in this message and resubmit. DTLAINT interface error : rc <result_code>, text <result_text>. An error occurred during initialization of a PowerExchange internal interface called DTLAINT. The DTLAINT interface returns this error with the specified result code and text to the calling software.
380
Contact Informatica Global Customer Support. DTLAINT interface error from invoked routine <routine_name>, rc <result_code>. An error occurred when the internal DTLAINT interface was invoking the specified routine. The DTLAINT interface returns this error with the specified result code to the calling software. Contact Informatica Global Customer Support. DTLCLOCK timestamp conversion error : <result_code>. An error occurred when the internal DTLAINT interface invoked the DTLCLOCK routine to convert a Datacom SQL time stamp in a change record to storeclock format. The routine attempts this conversion only when LOCAL_TIME=Y is specified in the Datacom table-based ECCR configuration member. The error might be caused by an incorrectly formed Datacom SQL time stamp. The DTLCLOCK routine returns this error with the specified result code to the calling software. Contact Informatica Global Customer Support. Could not allocate poolid <pool_ID>, rc <result_code>. An attempt to allocate memory for the specified pool ID failed. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. User is not licensed for this access method. The license key does not allow use of the DTLAMSCT access method for Datacom CDC. The DTLAMCST access method returns this error to the calling software. To obtain a valid extension to the license key, contact Informatica Global Customer Support. Member DBCB not connected. DBCB is <dbcb>. The specified DBCB is not connected. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Process <function_name> given invalid DBCB at <address>, with number <number>. The specified process provided an invalid DBCB. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Supporting file access layer returns rc<number>, text<reason>. The underlying file access mechanism returned an error. The reason for the failure might be invalid file names or a permissions failure. The DTLAMCST access method returns this error to the calling software. To diagnose the error, review the specified reason text. If you cannot resolve the error, contact Informatica Global Customer Support.
PWX-09000 to PWX-09999
381
SQL Error : <text_string>. The specified input SQL string for the DLTAMCST access method for Datacom CDC contains an error. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Error allocating memory <text_string>, rc <return_code>. PowerExchange could not allocate sufficient memory. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Critical error in value <text_string>. Explanation <text_string>. A critical data item or computed value contains an error. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Restart data mismatch - VERSION should be equal in both RI <text_string> and SEQ <text_string>. A call to validate restart information against the catalog failed. The DTLAMCST access method returns this error to the calling software. Correct the RI and SEQ values in the SQL string. Invalid restart data supplied - RI=<text_string>, SEQ=<text_string>. A conflict exists between the RI and SEQ values in the input SQL. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Requested verb for file access not recognized <verb_number>. The DTLAMCST access method cannot access a file because the verb is not open, close, or read. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Validation of supplied block/offset restart values <block_number> <offset> fails (catalog values <block_number><offset>). The supplied RI and SEQ values do not match the known values read from the catalog. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Catalog read failed, reason <text_string> rc <return_code>. An attempt to open or read from the catalog failed. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support.
382
Restart data mismatch - FILE in RI greater than FILE in SEQ, RI <text_string> and SEQ <text_string>. A call to validate restart information against the catalog failed. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Supporting datacom interface access layer returns rc<return_code>, text<reason>. The underlying Datacom interface access mechanism returned an error. The error might be an invalid configuration or a permissions failure. The DTLAMCST access method returns this error to the calling software. Contact Informatica Global Customer Support. Datacom Multi User Facility is not active for Change Data Capture function, Reply Y to continue or N to cancel. The Datacom MUF is not active for one of the following Datacom table-based CDC functions:

ECCR. The ECCR might have been started when the MUF was not running. Cleanup. The MUF has probably crashed or been inadvertently shutdown by the operator.
The ECCR waits for a user response. Your response depends on whether the MUF is not active for ECCR or cleanup:
ECCR. Restart the MUF and then respond Y to the message. Cleanup. Stop the ECCR and restart it. PWX-09891 Explanation: System Action: User Response: PWX-09893 Explanation: User Response: PWX-09894 Explanation: User Response: PWX-09895 Explanation: User Response: PWX-09896 Explanation: User Response: Wait for Datacom Multi User Facility denied by operator Operator replied to message PWX-09890 to cancel the Datacom ECCR startup rather than wait for the Datacom MUF to become active. The Datacom table-based ECCR ends. No response is required. Datacom RT Table Based CDC, Cleanup Task Started <time>. The cleanup task for Datacom CDC tables has started. No response is required. Datacom RT Table Based CDC, Cleanup Task Activated <time>. The cleanup task for Datacom CDC tables is running. No response is required. Datacom RT Table Based CDC, Cleanup Task Waiting for work <time>. The cleanup task for Datacom CDC tables is currently idle. No response is required. Datacom RT Table Based CDC, Cleanup Task Terminated <time>. The cleanup task for the Datacom CDC tables has ended. No response is required.
PWX-09000 to PWX-09999
383
PWX-09897 Explanation: System Action: User Response: PWX-09898 Explanation: System Action: User Response: PWX-09899 Explanation: System Action: User Response: PWX-09900 Explanation: User Response: PWX-09901 Explanation: System Action: User Response: PWX-09950 Explanation: System Action: User Response: PWX-09951 Explanation: System Action: User Response:
Cleanup subtask creation failed, rc return_code The cleanup task for Datacom CDC tables failed to start. The return code depends on the operating system environment. The Datacom table-based ECCR ends. Contact Informatica Global Customer Support. The cleanup subtask has terminated prematurely The cleanup task for Datacom CDC tables has terminated. See associated error messages. The Datacom table-based ECCR ends. Contact Informatica Global Customer Support. Presspack error: <text_string>. An error occurred when PowerExchange invoked the Presspack decompression routine. The PowerExchange access method returns this error. Correct the error identified in this message and resubmit. ADABAS STATS: STATS This message provides details of Adabas file usage: STATS. No response is required. Truncate (refresh) not supported for Adabas A request to delete all records in an Adabas file was issued. This action is not supported. The system ends the current task. No response is required. CAPI i/f: Connect OK. Sources = number A successful connection was made to the PowerExchange Consumer API. The task continues with other initialization work. No response is required. CAPI i/f: RC= return_code from CAPI_routine error_information An error occurred in the specified CAPI routine. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI i/f: error_information An internal error occurred. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI i/f: warning_information An unexpected logic situation occurred, but Processing continues. The task processing continues.

384
User Response: PWX-09957 Explanation: System Action:
Contact Informatica Global Customer Support to report the warning. CAPI i/f: Read times out after TimeOut seconds Additional_Information The first attempt to read captured data was made to the PowerExchange Consumer API with the time-out period as specified. Either data is returned to the caller (CAPXRT extraction or Condense) or the time interval expires and the calling process closes. If the time-out period is 86400 seconds, then reading never expires. For example, the system waits for data forever, or until the task is manually closed. No response is required. CAPI i/f: Image_Type image Header invalid: Error_Information An error occurred while assembling the before or after image of a database type that can be composed of several fragments or exceed 32 KB in length such as log-based IMS or Adabas records. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI i/f: token_type restart tokens: Sequence=token1 PowerExchange Logger=token2 The message displays CAPI sequence token values in hexadecimal values. The token_type is one of the following values:
Earliest UOW. Occurs when a cold start is done on a CAPXRT extraction or when Condense and the specified start tokens contained all zeros and were replaced by the earliest tokens available on the system as displayed. 1st UOW record. Might occur together with a record dump in hexadecimal following an internal error during buffer assembly such as for log-based IMS or Adabas records. Current record. Might occur together with a record dump in hexadecimal following an internal error during buffer assembly such as for log-based IMS or Adabas records. User Response: PWX-09960 Explanation: No response is required. CAPI i/f: Image_Type image: Header Total Rec Length=record_length Assembled Buffer Length=Buffer_Length This message occurs reports an internal error during buffer assembly such as log-based IMS or Adabas records. In the message text:

Image_Type is the type of image. record_length is the record length. Buffer_Length is the assembled buffer length. System Action: User Response: The task dumps record information and then aborts. Contact Informatica Global Customer Support specifying the function being performed at the time of the error. CAPI i/f: Image_Type image: Reallocated buffer from Current_Size to Required_Size The buffer used to assemble records from several fragments was increased from its initial allocation of 32668 bytes because a large record was encountered. This might occur for database types such as IMS and Adabas. The image type can be either Before or After. The task continues using the new memory allocation. No response is required.
PWX-09000 to PWX-09999 385
CAPI i/f: Image_Type image: Expected to read Expected_Bytes bytes. Met Reason An error occurred during buffer assembly causing reading to stop before the expected number of bytes was met. The reason field provides some information about the record just read. The image type can be either Before or After. The reason is one of the following:

END UOW record Data record with no before image Data record with no after image System Action: User Response: The task that encounters the error ends after dumping the record buffers. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI i/f: Before image: Expected Expected_Bytes but accumulated Accumulated_Bytes bytes in buffer. After reading all fragments, the actual number of bytes in the assembled buffer did not match the expected number. This might occur for database types such as IMS and Adabas. The task that encounters the error ends after dumping the record buffers. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI i/f: Current PowerExchange Logger log files position: Sequence=token1 Restart=token2 The message displays CAPI sequence token values in hexadecimal format for the current PowerExchange Logger position when a cold start is done on a CAPXRT extraction, or when Condense and no tokens were specified. The task continues with other initialization work. No response is required. CAPI i/f: End of file. Reason. The message displays one of the following reasons for shutting down a CAPXRT extraction or a Condense:
STOPTASK received. A request was received to stop; for example, through program DTLUTSK.EXE. Shut down requested. A normal stop request was received by the CAPI interface. This could arise from a user request, or could be triggered on MVS if the CAPI_CONNECTION statement of type EDPQ with parameter EOF=Y. System Action: User Response: PWX-09966 Explanation: The task ends. No response is required. CAPI i/f: No data in timeout period. Last data time=time_information. The message displays progress information if the system is reading through logs where there is nothing of interest, and the end of the log (when the CAPXRT extraction or Condense started) was not reached. The progress information ends after a PWX-09967 message is displayed. On expiration of the time interval without any data being retrieved, the message is issued. The message displays the last data time and the timestamp of the last data updates read. The task continues reading from the logs. Use the last data time to determine what part of the log is being processed. No response is required.
386
CAPI i/f: End of log for time timestamp reached The log position is noted when a CAPXRT extraction or Condense job starts and this message is issued when that position is reached. Sometimes a considerable time is taken to process from the start point to the end of log position, during which fresh updates enter the system, so the true end of log might be reached later. The message is issued only once. The timestamp indicates when the job started. The task continues reading from the logs. No response is required. CAPI i/f: facility not supported The optional facility is not supported on this CAPI Connection type. The CAPI facility NotifyCurrentEndOfLog is used to ensure that all records are read (without the job ending through a time out) up to the current end of log position, together with logging of messages PWX-09966 and PWX-09967. The NotifyCurrentEndOfLog is not supported on the old CAPI_CONNECTION type of EDPQ under MVS PAC jobs. Processing continues. without using the specified facility. Confirm with Informatica Global Customer Support that the specified facility is not needed. CAPI i/f: No data in timeout period. Current time=Time_Information. The message displays progress information if the system is reading through logs where there is nothing of interest, and the end of the log (when the CAPXRT extraction or Condense started) was not reached. The progress information ends after a PWX-09967 message has displayed. On expiration of the time interval without any data being retrieved, the message is issued. The Time Information can be sometimes used to give an indication of what part of the log is being processed. It shows the current time. The task continues reading from the logs. No response is required. CAPI i/f: Changed ChangedNumber sources to earliest sequence token The messages displays information of the number of sources for which the log is processed from the earliest sequence token in the log. The task continues reading from the logs. No response is required.
PWX-10000 to PWX-10999
PWX-10000 Explanation: System Action: User Response: PWX-10001 Explanation: System Action: DTERIOM function not implemented. The repository access module received a request that is not implemented. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM wrong number of parms for call 'request_mnemonic', number_of_parms received, number_of_parms expected. The repository access module received a request with an unexpected number of parameters. An error is returned to the requesting software.
PWX-10000 to PWX-10999 387
Report the message to Informatica Global Customer Support. DTERIOM unsupported encoded command (request_mnemonic). The repository access module received an encoded command request that is not supported. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM invalid encoded command request buffer. The repository access module received an encoded command request with improperly formed buffer. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM invalid convert buffer. The repository access module received a request with an improperly formed convert buffer. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM unsupported database type (character_value' X'hex_value'). The repository access module received a request with an unsupported database type. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM in-memory repository error. The repository access module was unable to allocate memory. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM reply buffer is too small. The repository access module was unable to generate a response because the reply buffer was too small. An error is returned to the requesting software. Report the message to Informatica Global Customer Support. DTERIOM repository open error (run-time_error_text) The repository access module encountered an error when attempting to open the repository. The repository is not opened. Attempt to correct the problem based on the run-time_error_text. DTERIOM repository info error (run-time_error_text) The repository access module encountered an error when attempting to retrieve information about the repository file. The repository is not processed. Attempt to correct the problem based on the run-time_error_text.
388
DTERIOM repository data error (error_description) The repository access module encountered an error when attempting to retrieve data from the repository file. The repository is not processed. Use the error text to correct the problem. DTERIOM already exited The repository access module is being called after it has ended. The system returns an error to the calling software. Report the message to Informatica Global Customer Support. DTERIOM subtask error: error_text The repository access module's helper subtask has encountered an error. This error is reported by the main module. The system returns an error to the calling software. Attempt to correct the problem based on the error text. DTERIOM unknown repository subtask error The repository access module's helper subtask has abnormally ended. This error is reported by the main module. The system returns an error to the calling software. Report the message to Informatica Global Customer Support. DTERIOM repository subtask initialization error The repository access module's helper subtask has encountered an error before completing initialization. This error is reported by the main module. The system returns an error to the calling software. Report the message to Informatica Global Customer Support. DTERIOM CRAM_Get_Registration_List failed The repository access module encountered an error when attempting to retrieve capture registration information. The repository is not processed. Attempt to correct the problem based on other error messages that are issued. DTERIOM CRLD_Start_Load_Session failed The repository access module encountered an error when attempting to retrieve capture registration information. The repository is not processed. Attempt to correct the problem based on other error messages that are issued. DTERIOM CRLD_LoadCR failed The repository access module encountered an error when attempting to retrieve capture registration information. The repository is not processed.
PWX-10000 to PWX-10999
389
User Response: PWX-10018 Explanation: System Action: User Response: PWX-10019 Explanation: System Action: User Response: PWX-10020 Explanation: System Action: User Response: PWX-10021 Explanation: System Action: User Response: PWX-10022 Explanation: System Action: User Response: PWX-10023 Explanation: System Action: User Response: PWX-10024 Explanation: System Action: User Response: PWX-10025 Explanation:
Attempt to correct the problem based on other error messages that are issued. DTERIOM IMR_Add_... failed The repository access module encountered an error when attempting to store capture registration information. The repository is not processed. Attempt to correct the problem based on other error messages that are issued. DTERIOM RRM_GetRegDataCols(pCReg) object count conflict The repository access module encountered an error when attempting to retrieve capture registration information. The repository is not processed. Report the message to Informatica Global Customer Support. DTERIOM column definition invalid (table instance_name.owner_name.table_name column column_name) The repository access module encountered an error when attempting to retrieve capture registration information. The column in the table specified has invalid attributes. The repository is not processed. Report the message to Informatica Global Customer Support. DTERIOM not all columns registered (table instance_name.owner_name.table_name) The repository access module encountered an error when attempting to retrieve capture registration information. The column in the table specified has invalid attributes. The repository is not processed. Report the message to Informatica Global Customer Support. DTERIOM data set name required on OPEN command The repository access module received an OPEN command without a data set name. The system returns an error to the calling software. Report the message to Informatica Global Customer Support. DTERIOM repository subtask request error The repository access module's helper subtask encountered request error. The system returns an error to the calling software. Report the message to Informatica Global Customer Support. DTERIOM repository already open The repository access module received an OPEN command when the repository was already believed to be open. The system returns an error to the calling software. Report the message to Informatica Global Customer Support. DTERIOM repository alloc failed (error X'error_code', info X'info_code') The repository access module encountered an error when attempting to dynamically allocate the repository data set.
390
The repository is not processed. Attempt to correct the problem based on the error and information codes. For more information about the error and information codes, see the IBM document, MVS Programming: Authorized Assembler Services Guide. DTERIOM repository dealloc failed (error X'error_code', info Xinfo_code) The repository access module encountered an error when attempting to dynamically deallocate the repository data set. Attempt to correct the problem based on the error and information codes. For more information about the error and information codes, see the IBM document, MVS Programming: Authorized Assembler Services Guide. DTERIOM data set is not a PowerExchange repository The repository access module determined that the data set specified is not a PowerExchange repository. The data set is not used. Specify the correct data set name. DTERIOM duplicate registration tag (capture type 'type' name 'name') The repository access module encountered two different capture registrations with the same registration tag. The repository is not processed. Report the message to Informatica Global Customer Support. DTERIOM same object has different registration tags The repository access module encountered the same capture registration object with different registration tags. The repository is not processed. Report the message to Informatica Global Customer Support. DTERIOM no capture registrations loaded The repository access module did not find any capture registrations in the repository. If correct, ignore, otherwise report the message to Informatica Global Customer Support. DTERIOM config open error (run-time_error_text) The repository access module encountered an error when attempting to open the repository access configuration file. The repository configuration is not processed. Attempt to correct the problem based on the run-time_error_text. DTERIOM config read error (return_code) The repository access module encountered an error when attempting to read the repository access configuration file. The repository configuration is not processed. Attempt to correct the problem based on the run-time_error_text.
PWX-10027 Explanation: System Action: User Response: PWX-10028 Explanation: System Action: User Response: PWX-10029 Explanation: System Action: User Response: PWX-10030 Explanation: User Response: PWX-10031 Explanation: System Action: User Response: PWX-10032 Explanation: System Action: User Response:
PWX-10000 to PWX-10999
391
392
DTERIOM config line line_number more than nnn characters (line_text) The repository access module encountered a line in the repository access configuration file that was longer than the maximum allowed. The repository configuration is not processed. Correct the problem. DTERIOM config line line_number no keyword/value separator (line_text) The repository access module encountered a line in the repository access configuration file that did not contain a keyword/value separator character. The repository configuration is not processed. Correct the problem. DTERIOM config line line_number keyword keyword unknown The repository access module encountered a line in the repository access configuration file that contained an unknown keyword. The repository configuration is not processed. Correct the problem. DTERIOM config line line_number keyword keyword specified twice The repository access module encountered a line in the repository access configuration file that contained a keyword specified twice. The repository configuration is not processed. Correct the problem. DTERIOM config line line_number keyword keyword value missing The repository access module encountered a line in the repository access configuration file that contained a keyword without a value. The repository configuration is not processed. Correct the problem. DTERIOM config line line_number keyword keyword must be a number from nnn and nnn The repository access module encountered a line in the repository access configuration file that contained a keyword with a numeric value that was out of range. The repository configuration is not processed. Correct the problem. DTERIOM config line line_number keyword keyword more than number_of characters The repository access module encountered a line in the repository access configuration file that contained a keyword with a string value that was too long. The repository configuration is not processed. Correct the problem. DTERIOM config keyword 'keyword' missing The repository access module encountered after reading the repository access configuration file determined that a required keyword was not specified. The repository configuration is not processed.
User Response: PWX-10041 Explanation: System Action: User Response: PWX-10042 Explanation: System Action: User Response: PWX-10043 Explanation: System Action: User Response: PWX-10044 Explanation: System Action: User Response:
Correct the problem. DTERIOM config keyword keyword' requires keyword 'keyword' The repository access module encountered after reading the repository access configuration file determined that a keyword required by another keyword was not specified. The repository configuration is not processed. Correct the problem. DTERIOM cache data_set_name info error (run-time_error_text) The repository access module encountered an error when attempting to retrieve information about a repository cache data set. The cache data set is not processed. Attempt to correct the problem based on the run-time_error_text. DTERIOM cache data_set_name has invalid format The repository access module determined that the cache data set specified has an incorrect format. The cache data set is not processed. Correct the problem. DTERIOM cache data_set_name serialization error The repository access module encountered an error when attempting to serialize the cache data set specified. The cache data set is not processed. The problem might be encountered if multiple agents are using the same cache data sets. If that is not the case, report the message to Informatica Global Customer Support. DTERIOM cache data_set_name open error (run-time_error_text) The repository access module encountered an error when attempting to open a repository cache data set. The cache data set is not processed. Attempt to correct the problem based on the run-time_error_text. DTERIOM cache data_set_name write error (run-time_error_text) The repository access module encountered an error when attempting to write to a repository cache data set. The cache data set is not processed. Attempt to correct the problem based on the run-time_error_text. DTERIOM cache identifier error The repository access module encountered an error while attempting to load capture registrations from a cache data set. The cache data set is not processed. Report the message to Informatica Global Customer Support.
PWX-10000 to PWX-10999
393
DTERIOM cache encoding error The repository access module encountered an error while attempting to write capture registrations to a cache data set. The cache data set is not processed. Report the message to Informatica Global Customer Support. DTERIOM CRAM_Get_CCT_Update_TS failed (return_code) The repository access module encountered an error while attempting to retrieve the current repository update time stamp. This error usually indicates a problem with the repository server. Registrations are not retrieved. Match the return code to the corresponding message in this reference. If you cannot resolve the error, contact Informatica Global Customer Support. last error: error_text Displayed in response to the REPSTATUS agent command. Contains the last error encountered attempting to access capture registrations. See the user response for the original error message. refresh active Displayed in response to the REPSTATUS agent command. Indicates that a capture registration refresh is in progress. No response is required. last refresh attempt time Displayed in response to the REPSTATUS agent command. Indicates when the last capture registration refresh was performed. No response is required. current change identifier changer_identifier Displayed in response to the REPSTATUS agent command. Displayed the current capture registration change identifier. No response is required. invalid repository data_set_name Displayed in response to the REPSTATUS agent command. Indicates that the current repository data set name has an invalid value. Correct the problem. configuration type repository data_set_name Displayed in response to the REPSTATUS agent command. Indicates that the current repository data set is a configuration file. No response is required. CCT repository data_set_name Displayed in response to the REPSTATUS agent command. Indicates that the current repository data set is a PowerExchange CCT data set.
PWX-10050 Explanation: User Response: PWX-10051 Explanation: User Response: PWX-10052 Explanation: User Response: PWX-10053 Explanation: User Response: PWX-10054 Explanation: User Response: PWX-10055 Explanation: User Response: PWX-10056 Explanation:
394
User Response: PWX-10057 Explanation: User Response: PWX-10058 Explanation: User Response: PWX-10059 Explanation: User Response: PWX-10060 Explanation: User Response: PWX-10061 Explanation: System Action: User Response:
No response is required. location location Displayed in response to the REPSTATUS agent command. Indicates that capture registrations are being retrieved from location location. No response is required. cache (cache_data_set_number) data_set_name Displayed in response to the REPSTATUS agent command. Displays the number and name of a repository cache data set. No response is required. helper subtask inactive, repository closed Displayed in response to the REPSTATUS agent command. Indicates that the repository is closed. No response is required. helper subtask inactive, cycling Displayed in response to the REPSTATUS agent command. Indicates that the helper subtask is in the process of restarting. No response is required. helper subtask abnormally terminated, code=abend_code, reason=reason_code Displayed in response to the REPSTATUS agent command or when it is an abnormal termination of the helper subtask is detected. The helper subtask is not restarted. Attempt to determine cause of problem. To restart helper subtask issue REPCLOSE followed by REPOPEN commands to agent. If the problem persists, contact Informatica Global Customer Support. memory usage: REGS abend_code registration_memory abend_codeK, VIRT private_areaK, SYS system_areaK, EXT extended_private_areaK, SYS extended_system_areaK Displays the current memory usage similar to IBM message IEF374I. Registration memory indicates the current kilobytes dedicated to caching capture registrations. In the message text:
PWX-10062
Explanation:
private_area is the maximum kilobytes of storage (high-water mark) that the agent has used from the user region of the private area. system_area is the maximum kilobytes of storage (high-water mark) that the agent has used from the following areas: LSQA, SWA, and high private area. extended_private_area is the maximum kilobytes of storage (high-water mark) that the agent has used from the user region of the extended private area. This value includes the current memory usage. extended_system_area is the maximum kilobytes of storage (high-water mark) that the agent has used from the following areas: extended LSQA, extended SWA, and extended high private area. User Response: No response is required.
PWX-10000 to PWX-10999
395
memory usage: below the line below_percentage%, above the line above_percentage% Displays the current memory usage as a percentage of available storage below and above the line. No response is required. CAPI: Internal error: Null token pointer passed to API_routine. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: No source information was passed to the Consumer API. The source list for a change extract was invalid missing. The task that encounters the error ends. Correct the source list information and try the request again. CAPI: Internal error: Null source interest list pointer passed to CAPI_Connect. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: CAPI_Connect caller specified <n> sources, provided <n> sources. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: CAPI_Connect caller did not provide a connection profile. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Connection profile <CONN_NAME> not found. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The DBMOVER.cfg might be corrupt. Make sure that the value specified for CAPI_CONN_NAME is correct. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: Unable to allocate memory for object_name. Insufficient memory resources exist to perform the task. The task that encounters the error ends. Increase the memory resources available to the task. Contact Informatica Global Customer Support if the error persists.
396
CAPI: Unable to find connection information for Connection profile <connection>. The CAPI_CONNECTION stanza for the specified CAPI_CONN_NAME is not found in DBMOVER.cfg. The task that encounters the error ends. Correct the values in DBMOVER.cfg. CAPI: Unable to load connection dll <DLLNAME>. The DLL specified was not found. The task that encounters the error ends. Verify that the CAPI_CONNECTION statement in DBMOVER.cfg is correct. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: Internal error: No token was passed to API_routine. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: API Token has invalid eyecatcher <xxx>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: API Token version <nn.nn.nn.nn> less than required minimum <nn.nn.nn.nn> A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Cannot process <call_type> call due to a prior error in the API. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: <call_type> call must succeed before <call_type> call can be attempted. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: <call_type> call was already successfully completed. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends.
PWX-10000 to PWX-10999 397
User Response:
Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: No enumerator was passed to <function_name>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: No return data pointer was passed to <API_routine>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Open Consumer API connection must be closed before disconnect is attempted. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Cannot issue <call_type> call after <call_type> call has been issued. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Source restart info not passed to <API_routine>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Invalid Source restart object info passed to <API_routine>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: source-tag not found in interest list. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
398
CAPI: Function <function_name> not implemented for this connection type. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error continues. No response is required. CAPI: No DLL specified in connection profile <CAPI_CONN_NAME>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: <call_type> call must be done before <API_call> call. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Required routine<routine_name> not implemented in CAPIINT. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Warning: Termination handle handle_name failed for <function>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error continues. The task might not terminate cleanly. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Zero length for SequenceInfo invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Warning: Low SequenceInfo and low Restartinfo found in different restart tokens. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error continues. There is a possible inconsistency in restart object values. Verify that the restart values are correct. CAPI: Internal error: Zero length for RestartInfo invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends.
PWX-10000 to PWX-10999
399
User Response:
Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Invalid Restart Sequence returned from read: Inconsistent length or does not ascend. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: No data passed to routine routine_name. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Invalid data type <data_type> passed to routine routine_name. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Invalid extended data type <data_type> passed to routine routine_name. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Extended data type <data_type> passed to routine routine_name invalid for this consumer. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Unexpected data for data type <data_type> passed to routine routine_name. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Required data for data type <data_type> not passed to routine routine_name. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends.
400
User Response:
Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Internal error: Invalid record type <record_type> passed to routine routine_name. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: No attribute info supplied to LRP interface. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: WARNING: Unrecognized attribute <name:value> passed to LRP interface. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error continues. No response is required. CAPI: ERROR: No input queue identifier in attribute list passed to LRP interface. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Common services connect failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. CAPI: ERROR: No platform Token. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Not connected. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-10000 to PWX-10999
401
CAPI: ERROR: Queue open failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. CAPI: ERROR: Command Queue open failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. CAPI: ERROR: Queue close failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. CAPI: ERROR: Command Queue close failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. CAPI: ERROR: CS info call failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Review the return and reason codes. CAPI: ERROR: Input Queue not found in PAC. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the PAC task specified in the PARM is correct for this process. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: ERROR: Common services disconnect failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. CAPI: ERROR: Read Queue token missing or invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly.
402
The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Source list missing or invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Restart token missing or invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Non standard record format received. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Restart request not sent. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: WARNING: Queue closed before EOF encountered. EOF was not received from LRP within the timeout period specified in the EDM parameters. The task that encounters the error continues. Increase the value specified in the PACTIMR parameter. Contact Informatica Global Customer Support if it persists. CAPI: ERROR: Interest list encoded command put failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in PowerExchange Change Capture Messages Reference. CAPI: ERROR: Request transaction encoded command put failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends.
PWX-10000 to PWX-10999
403
User Response:
The return and reason codes are documented in PowerExchange Change Capture Messages Reference. CAPI: ERROR: Timer set failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Timer cancel failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Wait call failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Read from LRP connection failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in PowerExchange Change Capture Messages Reference. CAPI: ERROR: Set restart object failed. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Get store clock value failed. Return Code : rc. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Error setting after data token. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
404
CAPI: ERROR: Command Queue token missing or invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Record data inconsistent with function INSERT. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Record data inconsistent with function UDPATE. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Record data inconsistent with function DELETE. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Event Mark call failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. Inspect the EDMMSG for further information. CAPI: ERROR: Log Queue not found in PAC. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the PAC task specified in the parameter is correct for this process. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: ERROR: No Log Queue defined to PAC. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the PAC task specified in the parameter is correct for this process. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: ERROR: CS EDMSDIR get call failed. Return Code : return_code Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends.
PWX-10000 to PWX-10999 405
User Response:
The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. Inspect the EDMMSG for further information. CAPI: ERROR: No Input Queue defined to PAC. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the PAC task specified in the parameter is correct for this process. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: ERROR: No input queue identifier in attribute list passed to LRP interface. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Shutdown Request encoded command put failed. Return Code : rc Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. Inspect the EDMMSG for further information. CAPI: ERROR: PowerExchange Logger disconnect request failed. Return Code: return_code Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Review the return and reason codes and the EDMMSG messages for additional information. CAPI: ERROR: PACINFO call failed. Return Code : return_code Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. The return and reason codes are documented in the Return Codes and Reason Codes sections of this manual. Inspect the EDMMSG for further information. CAPI: ERROR: Command connection not valid for GenRestart. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the PAC task specified in the parameter is correct for this process. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: ERROR: Unknown command record format read. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
406
CAPI: ERROR: No Log attribute supplied. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Log Read API <call_type> call failed. Return Code : return_code Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Review the EDMMSG log for additional information. Verify the status of the PowerExchange Logger and PowerExchange Agent. If you cannot resolve the problem, contact Informatica Global Customer Support. CAPI: ERROR: Log Write API <call_type> call failed. Return Code : return_code Reason Code: reason_code. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Inspect the EDMMSG log for further information. Verify the status of the PowerExchange Logger and PowerExchange Agent. If you cannot resolve the problem, contact Informatica Global Customer Support. CAPI: ERROR: Data for <data_type> extended data request invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: Warning: Extended data for request type <data_type>:<decription> not available. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error continues. Report the message to Informatica Global Customer Support. CAPI: ERROR: VARSTRING <operation_type> operation failed for object <object>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that no resource constraints have been exceeded. If the problem persists contact Informatica Global Customer Support. CAPI: ERROR: Restart values have incorrect length. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-10000 to PWX-10999
407
CAPI: ERROR: Enqueue failed. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Dequeue failed. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Unable to find IMS segment RBA for cascade key. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: DLL compile/link Version mismatch: DLL <nm>: DLL ver nn.nn.nn.nn. Link ver nn.nn.nn.nn. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: CAPI Version mismatch: DLL <nm> version <nn.nn.nn.nn>. Version Required <nn.nn.nn.nn>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Possible incorrect application of a product patch. Contact Informatica Global Customer Support if the problem cannot be resolved. CAPI: ERROR: <data_type> is not a valid extended datatype. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: No source restart information. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. View the documentation on setting apply restart tokens. If the process was followed correctly, report the problem to Informatica Global Customer Support. CAPI: ERROR: Sequence info must be <n> bytes. A call was made to the PowerExchange Consumer API that cannot be processed correctly.
408
The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Restart info must be <n> bytes. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: log name in restart info does not match log name for connect <log_name>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify the PowerExchange Logger name specified in the CAPI_CONNECTION. It must conform to the PowerExchange Logger name in the restart token if this is not an initial run. CAPI: ERROR: NULL values not allowed in Restart Token. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. View the documentation on setting apply restart tokens. If the process was followed correctly, report the problem to Informatica Global Customer Support. CAPI: ERROR: Restart token lengths not consistent. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. View the documentation on setting apply restart tokens. If the process was followed correctly, report the problem to Informatica Global Customer Support. CAPI: ERROR: Extended Info exists for none-capable caller. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the CAPI_CONNECTION parameters in the DBMOVER.cfg are correct. If you cannot resolve the error, contact Informatica Global Customer Support. CAPI: ERROR: Log read (RESTART) point beyond requested send point (SEQUENCE). A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. View the documentation on setting apply restart tokens. If the process was followed correctly, report the problem to Informatica Global Customer Support. CAPI: ERROR: Consumer not capable of required extended data processing. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the CAPI_CONNECTION parameters in the DBMOVER.cfg are correct. If you cannot resolve the error, contact Informatica Global Customer Support.
PWX-10000 to PWX-10999
409
CAPI: ERROR: Multiple objects allowed only on SourceEvent or RestartInfo <function> A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Restart token missing for source <source_tag>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. View the documentation on setting apply restart tokens. If the process was followed correctly, report the problem to Informatica Global Customer Support. CAPI: ERROR: Helper routine <helper_routine> can only be called during <API_call>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Extended data type type is not setable.(routine <helper_routine>). A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. CAPI: ERROR: Restart token for source <source_tag> invalid. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. View the documentation on setting apply restart tokens. If the process was followed correctly, report the problem to Informatica Global Customer Support. CAPI: ERROR: Log name from connect <log_name> must match log name from EDMSDIR <log_name>. A call was made to the PowerExchange Consumer API that cannot be processed correctly. The task that encounters the error ends. Verify that the CAPI_CONNECTION log parameter matches the log name in the EDMSDIT. If you cannot resolve the error, contact Informatica Global Customer Support. ERROR: Too many non-CAPX <PWX_config_file_statement_type> statements. <number_found> found, <number_allowed> allowed. Too many statements of the specified type were found in the PowerExchange configuration file. The task that encounters the error ends. Remove the extra statements and restart the task. The maximum number allowed is stated in the error message.
410
PWX-10386 Explanation: System Action: User Response: PXW-10387 Explanation:
INFO: End of file processing initiated by event table processing. A change record was detected for an event table, which causes the extraction process to shut down. The task ends normally. No response is required. IMS id missing for request to read IMS unload file A data map that requests a read of an IMS unload file does not include an IMS SSID. The library from which to load the DBD is specified through a combination of information from the IMS SSID and the DBMOVER IMSID parameters. The task that encounters the error ends. If you are using a DL/1 Batch data map, add an IMS SSID to the data map. If you are using an IMS ODBA data map, the IMS SSID should already be present. Also, verify that the IMSID parameter in the DBMOVER configuration member specifies the DBD library for the IMS subsystem. Memory management problem for item <item_reference>, return code <return_code>. Insufficient resources to allocate requested memory Processing ends. Ensure that sufficient resources are available to the process. <operation> to QManager <queue_manager>, Queue <queue_name>, ret code <return_code>, reason <reason_code> An operation on the queue has failed. Processing ends. For a more detailed explanation of the error, review the messages that follow this message. Cannot continue. Parameter <parameter_name> was not supplied. The user has not specified an essential parameter. Processing ends. Determine the correct value of the parameter, and supply it. The member DBCB provided has no link to a Connection DBCB. The API was called with an invalid configuration. Processing ends. Use connection DBCBs. Refer to IBM MQ Manuals for explanation of these messages. Other messages have returned MQ codes and responses. Read associated messages for MQ references. Could not create Pool ID for <pool_ID_base>, rc <return_code>. An internal memory configuration error occurred. Processing ends. Contact Informatica Global Customer Support with details.
PWX-10400 Explanation: System Action: User Response: PWX-10401 Explanation: System Action: User Response: PWX-10404 Explanation: System Action: User Response: PWX-10405 Explanation: System Action: User Response: PWX-10406 Explanation: User Response: PWX-10407 Explanation: System Action: User Response:
PWX-10000 to PWX-10999
411
Explanation: explanation_text. Brief MQ reason code explanation. No response is required. Trying to connect to <queue_manager>, but already connected to <queue_manager>. While already connected to a queue manager, an attempt was made to connect to a different one. Processing ends. If calling the API, verify the logic, otherwise contact Informatica Global Customer Support. <operation> to queue <queue_name> failed, since it is not opened for Syncpointing. An syncpointing-related operation was requested on a queue that was not opened for syncpointing. Processing ends. If calling the API, verify the logic, otherwise contact Informatica Global Customer Support. Invalid DBCB used in call to <function>, DBCB <DBCB_address> DBCB No. <DBCB_number>. The API was called with an invalid configuration. Processing ends. If calling the API, verify the logic, otherwise contact Informatica Global Customer Support. Crucial Value error in field<field_name>. Explanation: problem_description. The API was called with an invalid configuration. Processing ends. If calling the API, verify the logic, otherwise contact Informatica Global Customer Support. User <user_ID> is not licensed to use Message Queue functions. MQ access is not permitted with the license key given. Processing ends. Contact Informatica Global Customer Support for a new license key. Cannot call UPDATE on queue opened for browsing DB_UPDATE called on a queue opened for non-destructive reads. The system does not read from or write to that queue. Contact Informatica Global Customer Support and specify the nature of the error. AMMQS: <error_description> The module DTLAMMQS has encountered a fatal error described by the specified descriptive text. The system returns an error to the calling software. Contact Informatica Global Customer Support.
412
PWX-10500 Explanation: User Response: PWX-10501 Explanation: System Action: User Response: PWX-10502 Explanation: System Action: User Response: PWX-10503 Explanation: System Action: User Response: PWX-10504 Explanation: System Action: User Response: PWX-10505 Explanation: System Action: User Response: PWX-10506 Explanation: User Response: PWX-10507 Explanation: User Response: PWX-10508 Explanation: System Action: User Response:
command_input The current command input line. No response is required. Invalid hex character (character) in <parameter> The parameter specified contained an invalid hex character. Processing ends. Correct the error. Then, run the request again. Odd number of hex characters in <parameter> The parameter specified contained an odd number of hex characters. Processing ends. Correct the error. Then, run the request again. Conflicting parameters <parameter1> and <parameter2> The parameters specified cannot be specified together. Processing ends. Correct the error. Then, run the request again. Invalid entry_source_or_target The specified parameter specified has an invalid value. Processing ends. Correct the error. Then, run the request again. No command specified No command was specified. Processing ends. Correct the error. Then, run the request again. Syntax for the MQ restart utility: First line of HELP output. No response is required. help_information Line of HELP output. No response is required. Entry (source_name,target_name,target_type) already present in application application_name Entry is already defined in the application. Processing ends. Correct the error. Then, run the request again. It should be noted: source names are not case sensitive; NRDB target names are not case sensitive and the format does not matter (a.b_C is equivalent to A.B.C).
PWX-10000 to PWX-10999
413
No application in effect The command being executed requires an application. The application name can be specified by the APPL= keyword or on the SETDEF command. Processing ends. Correct the error. Then, run the request again. No queue name in effect The command being executed requires a queue name. The queue name can be specified on the SETDEF command or in the DBMOVER configuration file. Processing ends. Correct the error. Then, run the request again. MQR API call call_name returned error return_code (return_mnemonic) The MQ restart API call specified returned an error. Additional messages should help determine why the error was returned. Processing ends. Correct the error. Then, run the request again. No application loaded The command being executed requires an application to be loaded. Processing ends. Correct the error. Then, run the request again. Application <application_name> already exists The command being executed requires the application to not already exist in the restart queue. Processing ends. Correct the error. Then, run the request again. Application <application_name> not found The application was not found in the restart queue. Processing ends. Correct the error. Then, run the request again. Error ignored because of option_description option The previous error was ignored. Processing continues. No response is required. Error treated as fatal The previous error was treated as fatal. Processing ends. Correct the error. Then, run the request again.
414
Command command_name complete The command's processing has completed without error. Processing continues. No response is required. Pending changes not saved Previous command(s) modified the state of the restart queue, but those changes were not saved. Processing ends. Correct by adding APPLSAVE command and rerun. Entry (source_name,target_name,target_type) not present in application application_name Entry is not defined in the application. Processing ends. Correct the error. Then, run the request again. Command cannot be processed while application <application_name> is running Command is not allowed when application is running. Processing ends. If application is not truly running, use APPLCLR command to clear running indication and reissue command. If application is truly running, stop application and reissue command. Otherwise contact Informatica Global Customer Support. parameter_name parameter requires parameter_name parameter One parameter requires the specification of a second parameter. Processing ends. Correct the error. Then, run the request again. Memory allocation failure. Memory allocation failure. Processing ends. Attempt to rerun, If the problem persists, contact Informatica Global Customer Support. CAPI call call_name returned error return_code (return_mnemonic) The CAPI call specified returned an error. Additional messages should help determine why the error was returned. Processing ends. Correct the error. Then, run the request again. CAPI call call_name returned return_code (return_mnemonic) The CAPI call specified returned an non-success return code. Additional messages should help determine why this happened. No response is required.
PWX-10521 Explanation: System Action: User Response: PWX-10522 Explanation: System Action: User Response: PWX-10523 Explanation: System Action: User Response: PWX-10524 Explanation: User Response:
PWX-10000 to PWX-10999
415
Application: application_name (update_time) running Output from the PRINT command. Processing continues. No response is required. RunId: running_id Output from the PRINT command. Processing continues. No response is required. Rst: first portion or all of restart token Output from the PRINT command. Processing continues. No response is required. Seq: first portion or all of sequence token Output from the PRINT command. Processing continues. No response is required. continuation of restart or sequence token Output from the PRINT command. Processing continues. No response is required. Entry: S=source T=target TT=target_type Output from the PRINT command. Processing continues. No response is required. MQR application <application_name> appears to be active The application appears to already be active. Processing ends. Determine if multiple processes are using the same application name and queue. If not, this situation could have been caused by a job abnormally terminating. If this is the case use the APPCLEAR command to clear the run ID, otherwise contact Informatica Global Customer Support. MQR run id mismatch, expected <run_id>, actual <run_id> The run ID in the queue record did not match the expected run ID. This is most likely caused by multiple processes using the same application name at the same time. Processing ends. Attempt to determine if multiple processes are using the same application name and queue. If not and the first run ID is the empty string use the APPCLEAR command to clear the run ID, otherwise contact Informatica Global Customer Support.
416
MQR update time mismatch, expected <run_id>, actual <run_id> The update time in the queue record did not match the expected update time. This is most likely caused by multiple processes using the same application name at the same time. Processing ends. Attempt to determine if multiple processes are using the same application name and queue. If not, contact Informatica Global Customer Support. MQR API level mismatch, caller=API_level_number, implementation= API_level_number The caller of the MQ restart API was not compiled with the same API level as the implementation. Processing ends. Contact Informatica Global Customer Support. MQR queue error on <call_type> call, rcs=return_code1/return_code2/return_code3 The MQ restart API encountered an error while accessing the restart queue. In the message text

call_type is the type of call that encountered the error. return_code1, return_code2, and return_code3 are the PowerExchange return codes for the failure.
System Action: User Response: PWX-10577 Explanation: System Action: User Response: PWX-10578 Explanation: User Response: PWX-10579 Explanation: User Response: PWX-10595 Explanation:
Processing ends. Correct the error. Then, run the request again. MQR record content <error_description> An error was encountered parsing the content of the queue restart records. Processing ends. Contact Informatica Global Customer Support. Entry Source=<source_name> Target=<target_name> Type=<target_type> Related to record content error. Describes E record related to error. No response is required. Entry Restart identifier=<restart_ID> Related to record content error. Describes R record related to error. No response is required. MQR running state recovered, formerly <old_run_ID> The application appeared to be running, but enough time had elapsed that it is being assumed that the application has abnormally ended. This instance of the application is taking over. No response is required. optional_description hex_digits Related to token error. Displays value of token. No response is required.
User Response: PWX-10598 Explanation: User Response:
PWX-10000 to PWX-10999
417
Application=<application> does not exist. It will be ADDED. Trying to modified an application that it does not exist. Application is added. No response is required. Field application action Entered an incorrect application action. Possible values are:
ADD MOD END PRINT SEQUENCE RESTART UID EPWD System Action: User Response: PWX-10601 Explanation: System Action: User Response: PWX-10602 Explanation: System Action: User Response: PWX-10603 Explanation: System Action: User Response: PWX-10604 Explanation: System Action: User Response: PWX-10605 Explanation: System Action: User Response: PWX-10606 Explanation:
418
Processing ends. Use a valid syntax for the utility input. Field application This field should be APPL or appl. Processing ends. Use a valid syntax for the utility input. Field application rsttkn This field should be RSTTKN. Processing ends. Use a valid syntax for the utility input. Field application registration This field should be a registration name. Processing ends. Use a valid syntax for the utility input. Field application name This field should be an application name. Processing ends. Use a valid syntax for the utility input. Field application generate This field should be GENERATE. Processing ends. Use a valid syntax for the utility input. Field application modall This field should be MODALL.
System Action: User Response: PWX-10607 Explanation: System Action: User Response: PWX-10608 Explanation: System Action: User Response: PWX-10609 Explanation: System Action: User Response: PWX-10610 Explanation: System Action: User Response: PWX-10611 Explanation: System Action: User Response: PWX-10612 Explanation: System Action: User Response: PWX-10613 Explanation: System Action: User Response: PWX-10614 Explanation: User Response: PWX-10615 Explanation:
Processing ends. Use a valid syntax for the utility input. Field application preconfig This field should be PRECONFIG. Processing ends. Use a valid syntax for the utility input. Parsing error: <information> Input error for the utility. Processing ends. Use a valid syntax for the utility input. Field application instance This field should be an instance name. Processing ends. Use a valid syntax for the utility input. Buffer overflow error The text generated exceeds an internal maximum length. Processing ends. Contact Informatica Global Customer Support. Registration <registration_name> not found in application <applname> Trying to modify a registration that does not exist in the application Processing ends. Use ADD instead of MOD. Several registrations with tag=<tag_name>, reg=<registration_name> will not be modified Trying to modify a registration with a tag used by several others. The registration is not modified. Use MODALLSAMETAG option. Application <application> does not exist. Can not MOD <registration>. Use ADD RSTTKN Trying to modify a registration of an application that does not exit. Processing ends. Use ADD RSTTKN Registration versions are different. Registration <version> in CDEP will be changed to <version> in application <application>. The version of the registration stored in CDEP is different. The version is changed. No response is required. Error parm size length=length is over nnn limit Parameter too long.
PWX-10000 to PWX-10999 419
Processing ends. Verify the parameter. Encrypted Password Required password by some utilities. Processing ends. Specify a password. Error OpenING Parm file rc1=<return_code1> rc2=<return_code2> rc3=<return_code3> filename=<file_name> During an attempt to open the specified file, an error occurred. In the message text
return_code1, return_code2, and return_code3 are the PowerExchange return codes for the failure. file_name is the name of the file that could not be opened. System Action: User Response: PWX-10618 Explanation: Processing ends. To diagnose the problem, review the return codes. Error READING Parm file rc1=<return_code1> rc2=<return_code2> rc3=<return_code3> filename=<file_name> Error trying to read file name. In the message text
return_code1, return_code2, and return_code3 are the PowerExchange return codes for the failure. file_name is the name of the file that could not be read. System Action: User Response: PWX-10619 Explanation: User Response: PWX-10620 Explanation: System Action: User Response: PWX-10621 Explanation: System Action: User Response: PWX-10622 Explanation: System Action: Processing ends. To diagnose the problem, review the return codes. Reg=<registration_name> tag=<registration_tag> modified because MODALLSAMETAG. More than one registration was changed because MODALLSAMETAG. No response is required. Unload file name required. An attempt was made to read an unload file and no file name was supplied. The task that encounters the error ends. Specify an unload file. DTLUCBRG Error: parameter parameter missing. A mandatory parameter is missing from the input source. DTLUCBRG processing ends. Specify the missing parameter and run the request again. DTLUTSK Error: Password and Encrypted Password conflict. Specify only one. Two conflicting parameters specified to DTLTUTSK. DTLUTSK ends.
420
Specify only one of the conflicting parameters. Incorrect Action: action. Valid values are: LISTTASK/STOPTASK/LISTLOCATIONS An invalid action was requested. Only LISTTASK, STOPTASK or LISTLOCATIONS are valid ones. The task that encounters the error ends. Specify LISTASK, STOPTASK or LISTLOCATIONS. DTLUTSK Help: CMD=LISTTASK/STOPTASK LOC=location UID=uid PWD=pwd/EPWD=encryptpwd") A syntax help was requested from DTLUTSK. The DTLUTSK utility prints a syntax help. Specify the parameters to DTLUTSK according to the help provided. DTLUCBRG: Table mask <qual1.qual2> should have three qualifiers. An attempt was made to register some tables providing only two qualifiers. DTLUCBRG processing ends. Specify a table mask with three qualifiers. DTLUCBRG: Table mask <mask> should have at least <n> chars. An attempt was made to register some tables providing a short table mask. DTLUCBRG processing ends. Specify a longer table mask. DTLUCBRG: Need to use a listener. An attempt was made to register tables with location LOCAL. A PowerExchange Listener is required. DTLUCBRG processing ends. Specify a location different from LOCAL. DTLUCBRG: Password and Encrypted Password conflict. Specify only one. An attempt was made to register tables specifying both a password and an encrypted password. DTLUCBRG processing ends. Specify only one of the conflicting parameters. DTLUCBRG: Database type not allowed =<database_type>. An attempt was made to register tables for a non supported database type. DTLUCBRG processing ends. Specify a valid database type. DTLUCBRG: CONDTYPE <condtype> incorrect. Valid values are: COND, FULL or NONE. An attempt was to register tables with an invalid condense value. DTLUCBRG processing ends. Specify a valid cond type (COND/FULL/NONE).
PWX-10000 to PWX-10999
421
DTLUCBRG: Instance <instance_name> exceeds <n> chars. An attempt was to register some tables with a too long instance name. DTLUCBRG processing ends. Use a shorter instance name. DTLUCBRG: Status <status> invalid. Valid values are 'A' or 'I'. An attempt was to register some tables with an invalid status. DTLUCBRG processing ends. Use A (ACTIVE) or I (INACTIVE). DTLUCBRG: Status required. Valid values are 'A' or 'I'. An attempt was to register some tables with no status. DTLUCBRG processing ends. Use A (ACTIVE) or I (INACTIVE). DTLUCBRG: Error creating extraction map for table. Error creation a extraction map for a table. DTLUCBRG processing ends. This message is the result of errors in other utility modules. Look for other messages issued by the same job/task.If this does not clarify the matter, contact Informatica Global Customer Support with all the log messages. DTLUCBRG: No tables to register with mask <qualifier1.qualifier2>. No tables to register for that mask. DTLUCBRG processing ends. Use a different mask. DTLUCBRG: DBD DSN Name (x chars) is too long y. An attempt was to register an IMS table with a DBD data set name that is too long. DTLUCBRG processing ends. Correct the DBD Dataset name. DTLUCBRG: Registration type <registration_type> invalid. Valid values are Synchronous/LogBased. An attempt was to register some tables with an invalid registration type. DTLUCBRG processing ends. Use Synchronous or LogBased. DTLUCBRG: Capture Registration=<registration_name> could not be created in memory. An attempt was to create a registration. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued.
422
DTLUCBRG: Table <qualifier1.qualifier2> already registered in reg=<registration_name>. An attempt was to register a table already registered. DTLUCBRG processing ends. The table is already registered. DTLUCBRG: Column <column_name> could not be created in memory for regs=<registration_name>. An attempt was to create a column for a registration. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued. DTLUCBRG: Error loading registrations <registration_name>. An attempt was to load a registration. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued. DTLUCBRG: Registration <registration_prefix.registration_sequence> already exists. An attempt was to create a registration that already exists. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued. DTLUCBRG: Parameter <parameter> format <error_description>. The supplied parameter has a format error, as described. exists. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued. DTLUCBRG: Parameter mismatch. Reason<description>. The supplied parameter has a format error, as described. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued. DTLUCBRG: File IO Error. Reason<description>. Input/Output Error on file, as described. DTLUCBRG processing ends. Review associated error messages to determine why the run failed. Should local resolution fail, contact Informatica Global Customer Support, including the name of the user and the error code issued.
PWX-10000 to PWX-10999 423
DTLUCBRG: Warning<description>. Warning message. Unusual situation that might be an error. DTLUCBRG processing continues. Interpret the message in the light of users own expectations. DTLUCBRG: No tables already registered with mask <qualifier1.qualifier2>. No tables to register for that mask. DTLUCBRG processing ends. Use a different mask. DTLUCBRG: Location <location> not supported for parameter <parameter_name>. The location entered is not supported by DTLUCBRG. DTLUCBRG processing ends. Use a different location. DTLUCBRG must run under the control of a PowerExchange Listener. DTLUCBRG: DB2 type not allowed for a non EBCDIC platform, use type UDB. The DB2 type is not supported for a non EBCDIC platform. DTLUCBRG processing ends. Use UDB DTLUCBRG: UDB type not allowed for a EBCDIC platform, use type DB2. The UDB type is not supported for EBCDIC platform. DTLUCBRG processing ends. Use DB2 DTLUCBRG: CRGPREFIX <prefix> contains invalid characters for a registration name. The prefix can only contain characters 'a' through 'z' and '0' through '9.' However, '0' through '9' cannot be used as the first character. DTLUCBRG processing ends. Correct the prefix and try the request again. DTLURDMO: Table <schema.table_name> contains invalid characters and requires a prefix for registration. DTLURDMO does not allow the first character of the table name to be a number, even if the database allows it. DTLURDMO ignores the table and continue processing. Specify a letter as the first character of the table name and try the request again. DTLUCBRG: MSSQL Registrations can not be created from this platform. MSSQL registrations rely heavily on information retrieved from the MSSQL publication. This information is only available from PC installations. DTLUCBRG processing ends. Run the DTLUCBRG utility from a valid PC.
424
DTLUCBRG: Full condense is not allowed on table <schema.table_name>. Table has no unique key specified. An attempt was to register a table for full condense where the table does not have a unique key specified. This is a prerequisite for full condense. DTLUCBRG does not register the table for change data capture and continue processing with the next available table. Either specify a unique key for the table and run the request again or change the condense type to either Part or None. DTLUCBRG: CRGNAME <prefix> contains invalid characters for a registration name. The DTLUCBRG utility does not allow the CRGNAME value to begin with a number. This CRGNAME value must begin with a letter to generate a valid registration tag name. For the rest of the name, you can use any combination of alphanumeric characters from "a" through "z" and from "0" through "9." DTLUCBRG ends abnormally. Enter a letter as the first character in the CRGNAME value and then try running DTLUCBRG again. CAPI: ERROR: attribute_name missing The UOW cleanser's CAPI_CONNECTION information did not contain the required attribute. Connection does not open. Correct CAPI_CONNECTION information. CAPI: WARNING: attribute_name ignored The UOW cleanser's CAPI_CONNECTION information contained an attribute that is not available on this platform. The attribute was ignored. No response is required. The attribute can be removed from the CAPI information. CAPI: INFO: Subordinate function_name returned return_code The UOW Cleanser received the indicated return code from a subordinate CAPI call. No response is required. CAPI: WARNING: Subordinate function_name returned return_code reason reason_code The UOW Cleanser received the indicated return and reason codes from the subordinate CAPI call. A warning is returned to calling software. No response is required. CAPI: ERROR: Subordinate function_name returned return_code The UOW Cleanser received the indicated return code from a subordinate CAPI call. The system returns an error to the calling software. No response is required. CAPI: ERROR: Internal error <description> The UOW Cleanser encountered an internal error. The system returns an error to the calling software.
PWX-10000 to PWX-10999 425
PWX-10700 Explanation: System Action: User Response: PWX-10701 Explanation: User Response: PWX-10702 Explanation: User Response: PWX-10703 Explanation: System Action: User Response: PWX-10704 Explanation: System Action: User Response: PWX-10705 Explanation: System Action:
Contact Informatica Global Customer Support. CAPI: ERROR: Subordinate CAPI returned unknown record type (record_type) The UOW Cleanser encountered an unknown record type. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Missing required data (description) The UOW Cleanser received a record from the subordinate CAPI that was missing some required data. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Invalid data for descriptive_text The UOW Cleanser received a record from the subordinate CAPI that contained invalid data. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: QSTD call function call return return_code (return_code_mnemonic) The UOW Cleanser encountered an error when accessing a spill data set. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Sequence invalid (must be even number of bytes (length=length)) The UOW Cleanser received a restart sequence number that consisted of an odd number of bytes. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. CAPI: Source list index number The UOW Cleanser encountered an error with source corresponding to index number. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Publishing (description) The UOW Cleanser encountered an error when attempting to publish a record value. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Calling CallBack function_name (rc=return_code) The UOW Cleanser encountered an error when calling the call back function indicated. The system returns an error to the calling software. Contact Informatica Global Customer Support.
426
CAPI: ERROR: Subordinate CAPI returned inappropriate extended data The UOW Cleanser encountered inappropriate extended data from the subordinate CAPI The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Operation backout error (descriptive_text) The UOW Cleanser encountered an error when processing a back out operation. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Subordinate CAPI IMS extended info conflict The UOW Cleanser encountered an error with the extended information options presented by the subordinate CAPI. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: IMS fast path cascade delete in-flight at end UOW The UOW Cleanser encountered an error when processing an IMS fast path cascade delete. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: IMS fast path cascade delete invalid level (number) The UOW Cleanser encountered an error when processing an IMS fast path cascade delete. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: IMS fast path cascade delete base key error (number) The UOW Cleanser encountered an error when processing an IMS fast path cascade delete. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: IMS fast path cascade delete level out of order (number) The UOW Cleanser encountered an error when processing an IMS fast path cascade delete. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Sequence invalid (end unit of work record before record) The UOW Cleanser received a restart sequence number that was invalid. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. CAPI: ERROR: Sequence invalid (end unit of work record in error) The UOW Cleanser received a restart sequence number that was invalid. The system returns an error to the calling software.
PWX-10000 to PWX-10999
427
User Response: PWX-10724 Explanation: System Action: User Response: PWX-10725 Explanation: System Action: User Response: PWX-10726 Explanation: User Response: PWX-10727 Explanation: User Response: PWX-10728 Explanation: System Action: User Response: PWX-10729 Explanation: User Response: PWX-10730 Explanation: User Response: PWX-10731 Explanation: System Action: User Response: PWX-10732 Explanation: System Action: User Response:
428
Correct the source of the invalid restart sequence number. CAPI: ERROR: Sequence invalid (record in error) The UOW Cleanser received a restart sequence number that was invalid. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. CAPI: ERROR: Restart invalid (subordinate CAPI returned error) The UOW Cleanser received a restart sequence number that was invalid. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. CAPI: Sequence number of end unit of work record The UOW Cleanser issues this message when directed to print a restart token. It indicates that the following messages apply to the end unit of work's sequence number. No response is required. CAPI: Sequence number of record The UOW Cleanser issues this message when directed to print a restart token. It indicates that the following messages apply to the record's sequence number. No response is required. CAPI: ERROR: Begin UOW encountered for existing UOW The UOW Cleanser encountered a begin unit of work record for a unit of work it believed was already active. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: ERROR: Existing UOW sequence/restart information This message is issued in conjunction with message PWX-10728 to indicate the following message relate to the existing unit of work. No response is required. CAPI: description: hex data character_data The UOW Cleanser uses this message to display binary data. No response is required. CAPI: ERROR: Required extended data (description) error The UOW Cleanser's subordinate CAPI does not support the required extended attribute. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: Sequence unformattable by UOW cleanser (no bytes or odd number of bytes) The UOW Cleanser was directed to format a restart sequence value that was invalid. The system returns an error to the calling software. Correct the source of the invalid restart sequence number.
CAPI: Incompatible extended data support: description The UOW Cleanser's subordinate CAPI does not support all of a set of required extended attributes. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPI: INFO: Backouts of changes resulted in <number_of_mismatches> symmetry mismatches in transaction <hexadecimal_transaction_identifier> The UOW Cleanser detected that changes were backed out in an unexpected order. PowerExchange expects changes to be backed out symmetrically, in the reverse order in which they were made. The message indicates the number of symmetry mismatches for the specified committed transaction. CDC processing continues. Examine the source transaction to determine if the symmetry mismatches affect data integrity. If not, no action is required. QSTD: MVS spill file allocation failure, error code=0xerror_code_in_ex, info code=0xinfo_code_in_hex The spill to disk module encountered an error when attempting to allocate a spill data set. The error and info codes are documented in IBM's MVS Programming: Authorized Assembler Services Guide. The system returns an error to the calling software. Attempt to correct the problem based on error/info codes. QSTD: Spill file write error (runtime_error_code) run-time_error_text The spill to disk module encountered an error when attempting to write to a spill data set. The system returns an error to the calling software. Attempt to correct the problem based on runtime error information. QSTD: AS400 spill file allocation failure, func=function_name, rc=function_return_code, text=run-time_error_text The spill to disk module received an error when attempting to allocate a spill data set on the AS/400. The system returns an error to the calling software. Attempt to correct the problem based on runtime error information. QSTD: Spill file allocation failure, func=function_name, rc=function_return_code, text=run-time_error_text The spill to disk module received an error when attempting to allocate a spill data set on a UNIX platform. The system returns an error to the calling software. Attempt to correct the problem based on runtime error information. QSTD: Spill file function_name error (function_return_code) run-time_error_text The spill to disk module received an error when attempting to operate on a spill data set. The system returns an error to the calling software. Attempt to correct the problem based on runtime error information.
PWX-10000 to PWX-10999 429
PWX-10800 Explanation: System Action: User Response: PWX-10801 Explanation: System Action: User Response: PWX-10803 Explanation: System Action: User Response: PWX-10804 Explanation: System Action: User Response: PWX-10805
Oracle Capture: Unable to allocate memory. Oracle Capture was unable to allocate memory to store the data specified in the message. Oracle Capture processing ends. Correct the problem that caused the memory shortage. Oracle Capture: Internal error: Null Token address passed to <function_name>. Storage common to the PowerExchange Capture modules was lost. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: Internal error: <function_name> could not find a platform token. Storage common to the PowerExchange Oracle Capture modules was lost. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: Internal error: <function_name> found an invalid eyecatcher <data_value> in the platform token. Storage common to the PowerExchange Oracle Capture modules was lost or corrupted. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: Platform token Version mismatch in <function_name>. Received: <version.release.modification_level.patch_level>. Expected: <version.release.modification_level.patch_level>. A version level mismatch was discovered in PowerExchange Oracle Capture. Oracle Capture processing ends. This is most likely caused by incorrect settings in your environment variables. Verify that your path and shared library path variables are set to point to the same PowerExchange binaries. A secondary cause of this message could be an incomplete or failed installation of the PowerExchange software. Oracle Capture: Missing function in oci shared library <Oracle_OCI_library_name> : <Oracle_OCI_function_name>. Either the Oracle OCI shared library was not found, or a required function of the OCI was not found in the OCI shared library. Oracle Capture processing ends. This is most likely caused by incorrect settings in your Oracle environment variables. Ensure that your path, shared library path, and ORACLE_HOME variables are set properly. In AIX environments, it is possible for this message to be generated due to an incomplete or failed installation of the PowerExchange software. Oracle Capture: WARNING: Unrecognized attribute:value <keyword:value> passed to Oracle Capture interface. An unknown keyword was found in the CAPI_CONNECTION (TYPE=ORCL) statement in your DBMOVER configuration file. Oracle Capture ignores the keyword and continues
430
User Response:
To get rid of the warning, edit your DBMOVER configuration file and remove the offending keyword. Oracle Capture: error_occurred, RC <OCI_return_code> while allocating the following item. Oracle messages follow. An Oracle error occurred when attempting to allocate required Oracle data structures. Oracle Capture processing ends. Accompanying messages display the Oracle error explanation. Fix the problem described by the Oracle error explanation and restart Oracle Capture. Oracle Error Code <OCI_error_code>: Error message follows. An Oracle OCI error occurred. Oracle Capture processing ends. This message is one of a series of messages that are generated when an Oracle SQL call fails. Review the messages that are generated both before and after this message to determine why the SQL call failed. Fix the problem and restart Oracle Capture. Oracle Capture: OCI call succeeded. The Oracle OCI call was successful. Oracle Capture processing continues. No response is required. This message is only generated when Informatica Global Customer Support requests that certain PowerExchange traces be turned on to help debug an existing problem. Oracle Capture: OCI call succeeded with information messages. The Oracle OCI call succeeded. Oracle Capture processing continues. Review the additional Oracle informational messages that follow. Oracle Capture: Unable to determine OCI error. A null error handle was passed. Invalid data was passed to the Oracle Capture error handler. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: Unable to determine OCI error. A recursive error situation was discovered. The OCI call used to access the Oracle error message that was generated due to a previous error has failed. Oracle Capture processing ends. Inspect your Oracle logs for trouble with your Oracle instance. Ensure that your Oracle instance is available. This message can occur if a SHUTDOWN IMMEDIATE or SHUTDOWN ABORT command is sent to the Oracle instance in question. Oracle Capture: OCI call is missing required data. An invalid Oracle OCI call was attempted. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support.
PWX-10000 to PWX-10999 431
PWX-10815 Explanation: System Action: User Response: PWX-10816 Explanation: System Action: User Response: PWX-10817 Explanation: System Action: User Response: PWX-10818
Oracle Capture: The handle type passed to the OCI call was incorrect. The storage required to communicate with Oracle was lost or corrupted. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: The OCI call is non-blocking, but was treated as a blocking call. PowerExchange Oracle Capture did not handle an Oracle OCI call properly. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: Unknown OCI failure code <return_code>. An unknown return code was passed to PowerExchange Oracle Capture from Oracle. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: error_occurred while attaching to server <Oracle_instance_name> (from <{dtlcfg_file|ORACLE_SID|default_location}>). Rc = <return_code>. Oracle messages follow. Oracle Capture could not connect to the specified Oracle instance. Oracle Capture processing ends. The from clause of this error message specifies where Oracle capture retrieved the instance name to which it is attempting to connect. Inspect the following messages to determine the reason for the failure, correct the problem, and restart Oracle Capture. Oracle Capture: error_occurred while setting <Oracle_connection_value> attribute of <Oracle_connection_attribute>. Rc = <return_code>. Oracle messages follow. PowerExchange Oracle Capture encountered an error while trying to set the specified value of the specified connection attribute. Oracle Capture processing ends. Inspect the messages that follow to determine the cause of the error, fix the problem, and restart Oracle Capture. Oracle Capture: error_occurred while beginning session with server <Oracle_instance> using userid <Oracle_user_ID>. Rc = <return_code>. Oracle messages follow. Oracle Capture could not connect to the specified Oracle instance using the specified Oracle user ID. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle capture could not connect to the specified Oracle instance. Fix the problem and restart Oracle Capture. Oracle Capture: error_occurred while determining Oracle server version. Rc = <return_code>. Oracle messages follow. Oracle Capture could not determine the version of Oracle that is running on the server to which it is connected. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle could not access the Oracle version information. Fix the problem and restart Oracle Capture.
432
Oracle Capture: Oracle session setup successful: Oracle Capture initialization completed successfully. Oracle Capture processing continues. No response is required. Oracle Capture: error_occurred, RC <return_code> while preparing the following statement. Oracle messages follow. Oracle Capture could not issue an SQL PREPARE for the statement that follows. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle Capture could not prepare the statement. Fix the problem and restart Oracle Capture. Oracle Capture: error_occurred, RC <return_code> while executing the following statement. Oracle messages follow. Oracle Capture could not issue an SQL EXECUTE IMMEDIATE for the statement that follows. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle Capture could not execute the statement. Fix the problem and restart Oracle Capture. Oracle Capture: error_occurred, RC <return_code> while accessing <attribute_name> attribute for the following statement. Oracle messages follow. Oracle Capture could not retrieve the specified attribute of the table specified in the SQL statement that follows. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle Capture could not retrieve the specified information for the table. Fix the problem and restart Oracle Capture. CATEND parm <value> must be in 24-hour HH:MM format. The CATEND keyword in the dbmover.cfg CAPI_CONNECTION (TYPE=ORCL) statement contains an invalid value. Oracle Capture ends Fix the value in the DBMOVER configuration file and restart Oracle Capture. CATBEGIN parm <value> must be in 24-hour HH:MM format. The CATBEGIN keyword in the dbmover.cfg CAPI_CONNECTION (TYPE=ORCL) statement contains an invalid value. Oracle Capture ends Fix the value in the DBMOVER configuration file and restart Oracle Capture. Oracle Capture: error_occurred, RC <return_code> while defining SELECT variables for the following statement. Oracle messages follow. Oracle returned an error while attempting to define SQL host variables for the SQL statement that follows. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle would not allow the definition to occur. Fix the problem and restart Oracle Capture.
PWX-10000 to PWX-10999 433
Oracle Capture: error_occurred while attempting to end the OCI session. Rc = <return_code>. Oracle messages follow. Oracle returned an error when Oracle Capture attempted to end its session with the Oracle instance. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle would not allow the session to end. Fix the problem and restart Oracle Capture. Oracle Capture: error_occurred while attempting to detach from the server. Rc = <return_code>. Oracle messages follow. Oracle returned an error when Oracle Capture attempted to end its session with the Oracle instance. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle would not allow the session to end. Fix the problem and restart Oracle Capture. Oracle Capture: error_occurred while attempting to free the OCI environment. Rc = <return_code>. Oracle messages follow. Oracle returned an error when Oracle Capture attempted to free the storage it used to communicate with the Oracle instance. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle would not allow the storage to be freed. Fix the problem and restart Oracle Capture. Oracle Capture: error_occurred while querying Oracle V$DATABASE. Rc = <return_code>. Oracle messages follow. Oracle returned an error when Oracle Capture attempted to access the V$DATABASE Oracle dynamic view. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle would not allow access to the V$DATABASE dynamic view. Fix the problem and restart Oracle Capture. Oracle Capture: Minimal supplemental logging is not active. Oracle capture cannot continue. Minimal supplemental logging, as described in Chapter 9 of the Oracle 9i Database Administrator's Guide, is not active. Oracle Capture processing ends. The user should log on to Oracle and issue the following command: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA Note that if this occurs, any attempt to capture data before this point in the Oracle log might result in invalid or missing data. Oracle Capture: Null restart token passed to Oracle Capture. Oracle Capture was not passed any information to allow it to determine where it should start reading the Oracle log. Oracle Capture processing ends. This is most likely an operational error. It usually occurs when a new Oracle table is incorrectly defined to PowerExchange. Review the procedures you used to define your
434
tables to PowerExchange, and ensure that all necessary actions are completed. Fix any problems and restart Oracle Capture. PWX-10837 Explanation: System Action: User Response: Oracle Capture: Invalid restart token passed to Oracle Capture: Explanation. The restart information passed to Oracle Capture is invalid. The rest of the message describes the details of the problem. Oracle Capture processing ends. This is most likely an operational error. It either occurs when a new Oracle table is incorrectly defined to PowerExchange, when a request to capture uses restart information from a different Oracle instance than the one to which Oracle Capture is connecting, or when a non-Oracle data source is passed to Oracle Capture. It can also happen if the restart information was manually adjusted in an incorrect manner. Determine the source of the problem, fix the problem, and restart Oracle Capture. Oracle Capture: Invalid restart token restart SCN passed to Oracle Capture: Explanation. The restart information passed to Oracle Capture is invalid. The rest of the message describes the details of the problem. Oracle Capture processing ends. This is most likely an operational error. It either occurs when a new Oracle table is incorrectly defined to PowerExchange, when a request to capture uses restart information from a different Oracle instance than the one to which Oracle Capture is connecting, or when a non-Oracle data source is passed to Oracle Capture. It can also happen if the restart information was manually adjusted in an incorrect manner. Determine the source of the problem, fix the problem, and restart Oracle Capture. Oracle Capture: Restart token sequence SCN is less than restart SCN. The restart information passed to Oracle Capture is invalid. The rest of the message describes the details of the problem. Oracle Capture processing ends. This is most likely an operational error. It either occurs when a new Oracle table is incorrectly defined to PowerExchange, when a request to capture uses restart information from a different Oracle instance than the one to which Oracle Capture is connecting, or when a non-Oracle data source is passed to Oracle Capture. It can also happen if the restart information was manually adjusted in an incorrect manner. Determine the source of the problem, fix the problem, and restart Oracle Capture. Oracle Capture: Unable to initialize LOB storage queuing environment. Oracle Capture was unable to initialize the temporary storage method used to store LOB pieces until a complete piece can be sent. Oracle Capture processing ends. This message is currently unused. Oracle Capture does not support LOB data. Oracle Capture: Unable to find registration information for source <registration_tag>. The registration information for the data source represented by the given registration tag was not found in the repository. Oracle Capture processing ends. Verify your dbmover.cfg parameters to ensure that Oracle capture is connecting to the correct repository. Verify the definition of the registration tag to ensure that it is marked active. Ensure that the registration tag points to an Oracle table.
PWX-10000 to PWX-10999
435
Oracle Capture: Registration tags <registration_tag> and <registration_tag> both point to source table <owner. table_name>. A duplicate registration was found for the specified table. Oracle Capture processing ends. If this error occurs, contact Informatica Global Customer Support. Oracle Capture: Unable to insert source table information into hash table. Oracle Capture was unable to allocate storage in which to keep information about the tables being captured. Oracle Capture processing ends. Inspect any previous error messages and follow the instructions provided for the user response for those error messages. Oracle Capture: Registration for table <owner>.<table_name> contains duplicate column name <column_name>. The PowerExchange registration of the specified table has duplicate definitions for the specified column. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: error_occurred, RC <return_code> while binding variables for the following statement. Oracle messages follow. Oracle returned an error when Oracle Capture tried to create host variables for the following SQL statement. Oracle Capture processing ends. Inspect the following error messages. Determine what caused the problem, fix it, and restart Oracle Capture. Oracle Capture: error_occurred while finding Catalog on archived log. Rc = <return_code>. Oracle messages follow. Oracle Capture encountered an error while attempting to find a copy of the Oracle catalog on the Oracle log. Oracle Capture processing ends. Inspect error messages both before and after this message. Follow the instructions provided in the user response for these messages to resolve the problem, and restart Oracle Capture. Oracle Capture: Error while accessing hash table. Oracle Capture could not access internal information about the tables for capture. Oracle Capture processing ends. Inspect error messages both before and after this message. Follow the instructions provided in the user response for these messages to resolve the problem, and restart Oracle Capture. Oracle Capture: Transactions are active during restart point generation. It is possible that changes can be skipped. The Capture initialization process has discovered that Oracle transactions are active during the generation of a restart point for Oracle Capture. The utility continues.
436
User Response:
Ensure that the active transactions do not access the Oracle tables that are input to the Capture initialization process. If active transactions access these tables, and the generated restart point is used to restart Oracle Capture, the changes made by the active transactions is not captured. Oracle Capture: NULL Read segment size request. This message is for future use. Oracle Capture processing ends. This message is unused at this time. Oracle Capture: Invalid input received for Read segment size request. This message is for future use. Oracle Capture processing ends. This message is unused at this time. Oracle Capture: Unsupported PowerExchange column type <column_type> found for table <owner>.<table_name>, column <column_name>. The specified column has a data type that is unsupported by Oracle Capture. Oracle Capture processing ends. Remove the column from the PowerExchange repository definition of the specified table and restart Oracle Capture. Oracle Capture: error_occurred while finding supplemental log groups. Rc = <return_code>. Oracle messages follow. An error occurred while attempting to find Oracle supplemental log groups for the tables to be captured. Oracle Capture processing ends. Inspect error messages both before and after this message. Follow the instructions provided in the user response for these messages to resolve the problem, and restart Oracle Capture. Oracle Capture: Column <column_name> of table <owner>.<table_name> does not belong to a supplemental log group with the ALWAYS option. The specified column does not belong to a supplemental log group of the required type. Oracle Capture processing ends. This message is usually generated for one of the following reasons:
A schema_name override was specified in the PWXPC Application Connection definition being used for the failing PowerCenter session. This override is case sensitive, and was entered in lower case. A schema_name override was specified in the PWXPC Application Connection definition being used for the failing PowerCenter session, and has not altered the DDL created by the PowerExchange Capture registration process to point to the correct schema, or has not run the altered DDL. The DDL that was created by the PowerExchange Capture registration process was not executed. The table definition was altered, but the PowerExchange Capture registration was not recreated.
PWX-10000 to PWX-10999
437
Oracle Capture: error_occurred while describing Oracle LogMiner contents table. Rc = <return_code>. Oracle messages follow. Oracle Capture encountered an error while defining host variables to contain data from the V$LOGMNR_CONTENTS table. Oracle Capture processing ends. Inspect error messages both before and after this message. Follow the instructions provided in the user response for these messages to resolve the problem, and restart Oracle Capture. Oracle Capture: LogMiner error: Error_type in {Before image|After image} at column <offset>. SCN = <Oracle_SCN>. SCN record sequence = <nth_record_with_this_Oracle_SCN>. Data follows. Oracle Capture was unable to parse the SQL statement returned by LogMiner. Oracle Capture processing ends. This is most likely caused by an attempt to capture a column that contains LogMiner SQL output. This situation causes a recursion error, and is not supported at this time. If this is not the case, contact Informatica Global Customer Support. Oracle Capture: Single instance mode was requested without specifying log destination and/or thread parameters. The user specified SNGLINST=Y in the dbmover.cfg CAPI_CONNECTION TYPE=ORCL statement, and did not specify both the LOGDEST and LGTHREAD keywords. Oracle Capture processing ends. When running in single instance mode, you must specify both LOGDEST and LGTHREAD parameters as well. These are the parameters that tell Oracle Capture that instance's logs to use for the capture process. Oracle Capture: An attempt was made to remove an unknown transaction id <Oracle_transaction_ID> from the active transaction list. This is an internal error. Oracle Capture processing ends. Contact Informatica Global Customer Support. Oracle Capture: No active transactions were found when attempting to format a change record. This is an internal error. Oracle Capture processing ends. Contact Informatica Global Customer Support. Oracle Capture: LogMiner error: Invalid record timestamp. SCN = <Oracle_SCN>. SCN record sequence = <nth_record_with_this_SCN>. Data = <timestamp_string>. Oracle Capture could not format the timestamp of the change record returned by LogMiner Oracle Capture processing ends. Contact Informatica Global Customer Support.
PWX-10912
438
Oracle Capture: Column <column_name> of table <OWNER>.<table_name> not registered. The registration is defined to require mapping all columns. Oracle Capture encountered a column that is not part of the PowerExchange registration for the specified table, and the table was registered with the Select all and notify changes option. Oracle Capture processing ends. Reregister the table to include the specified column, or reregister the table without the Select all and notify changes option. Oracle Capture: Column <column_name> of table <OWNER>.<table_name> is required. No data exists for it. SCN = <Oracle_SCN>. SCN record sequence = <nth_record_with_this_SCN>. No data was found for the column in question during a captured SQL operation. Oracle Capture processing ends. Because of the supplemental logging requirements for Oracle Capture, data for all columns should always exist during any captured SQL operation for the table involved. This message means that the table was altered or redefined, removing the column in question from the table's definition in the Oracle catalog. The user should reregister the table to PowerExchange. Oracle Capture: Queue error retrieving data for column <column_name> of table <OWNER>.<table_name>. SCN = <Oracle_SCN>. SCN record sequence = <nth_record_with_this_SCN>. This message is not currently used. Oracle Capture processing ends. This message is not currently used. Oracle Capture: Unable to Delete LOB storage queue. This message is not currently used. Oracle Capture processing ends. This message is not currently used. Oracle Capture: Begin UOW SCN <Oracle_SCN> is less than previously processed SCN <Oracle_SCN>. This message is not currently used. Oracle Capture processing ends. This message is not currently used. Oracle Capture: Data error in {Before image|After image}. Messages follow. A data conversion error occurred while processing the current log record. Oracle Capture processing ends. Inspect the error messages both before and after this message to retrieve the details of the error. The details include the table and column in error, and the data that caused the conversion error. This is most likely caused when the Oracle definition of the table in question and the PowerExchange registration definition of the table do not match. Reregister your table to PowerExchange, using the correct definition for the table.
PWX-10918
PWX-10919
Explanation: System Action: User Response: PWX-10920 Explanation: System Action: User Response: PWX-10921 Explanation: System Action: User Response: PWX-10922 Explanation: System Action: User Response:
PWX-10000 to PWX-10999
439
Oracle Capture: Table/column in error: <OWNER>.<table_name>.<column_name>. SCN = <Oracle_SCN>. SCN record sequence = <nth_record_with_this_SCN>. The specified column contains data that does not match the PowerExchange registration definition of the table. Oracle Capture processing ends. This message is issued with message PWX-10922. See the user response for message PWX-10922. Oracle Capture: LogMiner statement in error follows. The following LogMiner statement contains data that does not match the PowerExchange registration definition of the table specified in the statement. Oracle Capture processing ends. This message is issued with message PWX-10922. See the user response for message PWX-10922. Queue error occurred while storing data This message is currently not used. This message is currently not used. Oracle Capture: Restart token sequence info is missing. The Oracle Capture restart token for a previously-specified capture source does not contain sequence information. This is normal during restart processing. Oracle Capture processing continues. No response is required. Oracle Capture: Restart token sequence info follows. Information used to perform Oracle Restart is printed out. Oracle Capture processing continues. No response is required. Oracle Capture: Restart token Oracle DBNAME: <Oracle_database_name> This is the name of the Oracle database to which Oracle Capture is supposed to be connected. Oracle Capture processing continues. No response is required. unless a restart error occurs. If this happens, use the REPNODE and ORACOLL parameters of the CAPI_CONNECTION(TYPE=ORCL) statement (in the DBMOVER configuration file used by the system running the capture) to find the system containing the PowerExchange Listener responsible for collecting the changed data. Review the fourth parameter of the PowerExchange Listener's dbmover.cfg ORACLEID keyword to ensure that the Oracle connection string points to the same Oracle instance as the restart token. Oracle Capture: Restart token restart info Start Read SCN: <Oracle_SCN> This specifies the Oracle SCN at which Oracle Capture starts reading Oracle log data. Oracle Capture processing continues. No response is required.
PWX-10931 Explanation: User Response: PWX-10953 Explanation: System Action: User Response: PWX-10954 Explanation: System Action: User Response: PWX-10955 Explanation: System Action: User Response:
440
Oracle Capture: Restart token restart info Start Return Data SCN: <Oracle_SCN> This specifies the Oracle SCN at which Oracle Capture starts returning Oracle log data to the caller. Oracle Capture processing continues. No response is required. Oracle Capture: Restart token sequence info SCN: <Oracle_SCN> This specifies the Oracle SCN portion of the internal change sequence number of the last record that the Oracle Capture caller processed. Oracle Capture processing continues. No response is required. Oracle Capture: Restart token sequence info SCN sequence: <Oracle_SCN> This specifies an Oracle Capture-generated portion of the internal change sequence number of the last record that the Oracle Capture caller processed. Oracle Capture processing continues. No response is required. Oracle Capture: Oracle SID <Oracle_SID> from collection id <collection_ID> does not match connected SID <Oracle_SID>. The Oracle connect strings for the repository and the capture point to different Oracle instances. Oracle Capture processing ends. Ensure that parameters 3 and 4 of the dbmover.cfg ORACLEID statement pointed to by your local dbmover.cfg CAPI_CONNECTION (TYPE=ORCL) statement point to the same Oracle instance. Oracle Capture: error_occurred while querying Oracle V$PARAMETER. Rc = <return_code>. Oracle messages follow. Oracle Capture could not access the V$PARAMETER dynamic view. Oracle Capture processing ends. Inspect the error messages both before and after this message, perform the error recovery specified in the user response fields for these messages, and restart Oracle Capture. Oracle Capture: error_occurred, RC <return_code> while performing the following attribute processing. Oracle messages follow. Oracle Capture encountered errors attempting to set Oracle OCI session parameters. Oracle Capture processing ends. Inspect the error messages both before and after this message, perform the error recovery specified in the user response fields for these messages, and restart Oracle Capture. Oracle Capture: Internal error: Unable to find source restart info for table <OWNER>.<table_name>, PowerExchange tag <registration_tag_name>. The Oracle Capture caller failed to send restart information to Oracle capture for the specified table. Oracle Capture processing ends. This is an internal error. Contact Informatica Global Customer Support.
PWX-10000 to PWX-10999 441
Oracle Capture: error_occurred while determining SCN start/end differential. Rc = <return_code>. Oracle messages follow. Oracle Capture could not determine the differential between the current SCN and its restart SCN. Oracle Capture processing ends. Inspect the following error messages to determine why Oracle could not access this information. Oracle Capture performs this operation through a SELECT from SYS1.DUAL. The problem is most likely due to accessibility problems to this table. Fix the problem and restart Oracle Capture. Oracle Capture: Unformatted log data found at SCN <Oracle_SCN> sequence <nth_instance_of_SCN>. LogMiner did not format the log data found at the reported Oracle SCN. Oracle Capture ends or continues based on dbmover.cfg parameter BYPASSUF value. If 'Y' is specified it continues. If not, Oracle Capture processing ends. See Reference Manual for more detail on the use of the BYPASSUF parameter. Contact Informatica Global Customer Support if running with BYPASSUF=Y is not specified and Oracle Capture processing ends. Oracle Capture: WARNING: Unrecognized override:value <override_name>.<override_value> passed to Oracle Capture interface. Oracle Capture received an unknown override parameter from its caller. Oracle Capture processing continues. Contact Informatica Global Customer Support. Oracle Capture: Cannot capture multiple schemas when using schema override. Oracle Capture received an request to capture tables in multiple schemas when the user specified the ORASCHEMA override as a DBMOVE input parameter. Oracle Capture processing ends. Create a new DBMOVE task for all tables that do not exist in the schema you wish to override, and remove those tables from the current DBMOVE task. Oracle Capture: Processing registration for table <schema_name>.<table_name> Oracle Capture is reading the capture registration of the specified table. Oracle Capture processing continues. No response is required. Oracle Capture: Using registration for table <schema_name>.<table_name> to process override table <schema_name>.<table_name> Oracle Capture is using the capture registration of the first table to process the second table, as per the override instructions passed to Oracle Capture. Oracle Capture processing continues. No response is required.
User Response:
442
Oracle Capture: Using registration for table <schema_name>.<table_name> to process global override table <schema_name>.<table_name> Oracle Capture is using the capture registration of the first table to process the second table, as per the global schema override name passed to Oracle Capture. Oracle Capture processing continues. No response is required. Oracle Capture: Duplicate transaction transaction_id found at SCN <SCN>, SCN record sequence <nth_record_with_this_SCN>. Oracle Capture found a begin transaction record for an active transaction ID for which Oracle LogMiner has already reported change data. Oracle Capture processing ends. This is possibly an Oracle LogMiner error. Contact Informatica Global Customer Support.
PWX-11000 to PWX-11999
PWX-11000 Explanation: System Action: User Response: PWX-11001 Explanation: System Action: User Response: HASH: Internal error: Null token pointer passed to function_name. The shared data pointer necessary for PowerExchange's internal hashing functions is missing. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Unable to allocate storage for data_description. The internal PowerExchange hashing function was unable to allocate the required storage. Depends on the PowerExchange function that is using the hashing functionality. Determine why a storage shortage exists for the process. Correct the problem and retry the function. HASH: Invalid eyecatcher passed to function_name: <eyecatcher_value>. The shared storage necessary for PowerExchange internal hashing functions was corrupted. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Invalid token address passed to function_name: passed = <hex_address>; expected = <hex_address>. The shared storage necessary for PowerExchange internal hashing functions was corrupted. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Internal error: Cannot destroy a non-empty hash table. An internal PowerExchange function attempted to destroy a hash table without processing the contents of the table. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support.
PWX-11000 to PWX-11999 443
HASH: No key value was passed to function_name. An internal PowerExchange function attempted to retrieve or insert data into a hash table without providing a hashing key for the data. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Internal error: Null object pointer passed to function_name. An internal PowerExchange function attempted to insert data into a hash table without providing the data to be inserted. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Internal error: Null retrieval token pointer passed to function_name. An internal PowerExchange function attempted to serially retrieve the data in a hash table without providing the data necessary to determine that function's current position in the table. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Internal error: No token passed to function_name. The shared data pointer necessary for PowerExchange internal hashing functions is missing. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Internal error: No retrieval token passed to function_name. An internal PowerExchange function attempted to serially retrieve the data in a hash table without providing the data necessary to determine that function's current position in the table. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Invalid retrieval token address passed to function_name: passed = <hex_address>; expected = <hex_address>. An internal PowerExchange function attempted to retrieve data sequentially from a hash table, but passed the hashing function an invalid token. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. HASH: Internal error: Null key pointer passed to function_name. An internal PowerExchange function attempted to retrieve or insert data into a hash table without providing a hashing key for the data. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support.
444
HASH: Internal error: Not in retrieval mode. An internal PowerExchange function attempted to sequentially retrieve data from a hash table without initializing its position in the table. Depends on the PowerExchange function that is using the hashing functionality. This is an internal error. Contact Informatica Global Customer Support. Oracle Capture: Unable to convert LogMiner data from server code page <code_page_of_Oracle_server> to UTF8. Oracle LogMiner can return redo/undo data in the server's code page instead of the code page requested by the client. The Oracle code page conversion function used to convert this data into a usable format has failed. Oracle Capture processing ends. This is possibly an Oracle error. Contact Informatica Global Customer Support. Oracle Capture: Oracle returned error code return_code attempting to return the client code page. The Oracle OCI call used to return the client code page failed with the error code returned in the message. Oracle Capture processing ends. This is possibly an Oracle error. Contact Informatica Global Customer Support. Ensure that your Oracle Client software is at least at the 9.2.0.3 level. Oracle Capture: error_occurred while finding the database code page. Rc = <return_code>. Oracle messages follow. An error occurred while attempting to find the database code page of the Oracle database from which you are capturing data. Oracle Capture processing ends. Inspect error messages both before and after this message. Follow the instructions provided in the user response for these messages to resolve the problem, and restart Oracle Capture. A likely problem is that the Oracle user you are using to run the session does not have SELECT access to the PUBLIC.V$NLS_PARAMETERS dynamic view. Oracle Capture: Unable to convert LogMiner data from UTF8 to server code page code_page_of_Oracle_server. PowerExchange Oracle Capture registrations created prior to PWX Version 8.5 store character data in the code page of the Oracle database server, while processing data in the UTF8 code page. The conversion from UTF8 to the server code page failed. Oracle Capture processing ends. This is possibly an Oracle error. Contact Informatica Global Customer Support. Oracle Capture: Processing attribute <attribute> value <value> PowerExchange Oracle Capture found the specified attribute and value. Processing continues. No response is required. Oracle Capture: Loading OCI module <module_name> PowerExchange Oracle Capture is loading the OCI module.
PWX-11000 to PWX-11999
445
Processing continues. No response is required. Oracle Capture: Creating OCI environment PowerExchange Oracle Capture is creating an OCI environment. Processing continues. No response is required. Oracle Capture: Creating OCI error handle PowerExchange Oracle Capture is creating an OCI error handle. Processing continues. No response is required. Oracle Capture: Creating OCI server handle PowerExchange Oracle Capture is creating an OCI server handle. Processing continues. No response is required. Oracle Capture: Creating OCI service context handle PowerExchange Oracle Capture is creating an OCI service context handle. Processing continues. No response is required. Oracle Capture: Connecting to server_name server (from location) PowerExchange Oracle Capture is connecting to the specified Oracle server from the specified location. Processing continues. No response is required. Oracle Capture: Setting OCI service context server attribute PowerExchange Oracle Capture is setting an OCI service context server attribute. Processing continues. No response is required. Oracle Capture: Creating OCI session handle PowerExchange Oracle Capture is creating an OCI session handle. Processing continues. No response is required. Oracle Capture: Setting session userid attribute to <userid>/UTF8<code_page> PowerExchange Oracle Capture is setting the user ID attribute to the specified value. Processing continues. No response is required.
446
Oracle Capture: Setting session password attribute to <password> PowerExchange Oracle Capture is setting the password attribute to the specified value. Processing continues. No response is required. Oracle Capture: Creating OCI session PowerExchange Oracle Capture is creating an OCI session. Processing continues. No response is required. Oracle Capture: Setting OCI service context session attribute PowerExchange Oracle Capture is setting an OCI service context session attribute. Processing continues. No response is required. Oracle Capture: Oracle session setup successful: Oracle_version PowerExchange set up an Oracle session successfully. Processing continues. No response is required. Oracle Capture: Source setup complete PowerExchange Oracle Capture set up the source successfully. Processing continues. No response is required. Oracle Capture: Next catalog write will occur on time The next Oracle catalog write will occur on at the specified time. Processing continues. No response is required. Oracle Capture: Retrieving End of Log SCN PowerExchange Oracle Capture is starting the process of retrieving an SCN. Processing continues. No response is required. Oracle Capture: End-of-log SCN <SCN> PowerExchange Oracle Capture successfully retrieved an SCN. Processing continues. No response is required. Oracle Capture: Searching for archive logs for thread <thread>, dest <dest>, SCN <SCN> PowerExchange Oracle Capture is searching for archive logs for the specified thread, destination, and SCN. Processing continues.
PWX-11000 to PWX-11999
447
No response is required. Oracle Capture: Using archive log <archive_log> PowerExchange Oracle Capture is using the specified archive log. Processing continues. No response is required. Oracle Capture: Using SCN <SCN> for LogMiner start PowerExchange Oracle Capture is using the specified SCN to start LogMiner. Processing continues. No response is required. Oracle Capture: No logs found for thread <thread_num> dest <dest> PowerExchange Oracle Capture cannot find logs for the specified thread and destination. Processing continues. No response is required. Oracle Capture: Restart point <restart_point> has been reached PowerExchange Oracle Capture reached the restart point. Processing continues. No response is required. Oracle Capture: Writing catalog PowerExchange Oracle Capture is writing the catalog. Processing continues. No response is required. Processing SCN <scn>. Current SCN is <current_scn> PowerExchange Oracle is processing the specified SCN. The message text displays the current SCN. Processing continues. No response is required. number_calls Oracle LogMiner calls. The Oracle LogMiner made the specified number of calls. Processing continues. No response is required. number_read_calls Oracle LogMiner polls for a select. After the specified number of read calls, the Oracle LogMiner polls for a select. Processing continues. No response is required.
448
PWX-11085 Explanation: System Action: User Response: PWX-11086 Explanation: System Action: User Response: PWX-11087 Explanation: System Action: User Response: PWX-11088 Explanation: System Action: User Response: PWX-11089 Explanation: User Response: PWX-11090 Explanation: System Action: User Response: PWX-11091 Explanation: System Action: User Response: PWX-11110 Explanation: System Action: User Response:
number_read_waits Oracle LogMiner waits for a select. This message displays the number of times that Oracle Capture went into a wait state to wait for a record to be returned by LogMiner. Processing continues. No response is required. reads_ratio Selects per call. This message displays the number of read calls to the number of reads ratio. Processing continues. No response is required. waits_ratio Waits per call. This message displays the number of read waits to the number of reads ratio. Processing continues. No response is required. Current OCI prefetch value: OCI_prefetch This message displays the current value of the OCI fetch array size that is used by Oracle capture. Processing continues. No response is required. Current time: current_time This message displays the current time, which is used to determine the time differential between now and the log record currently being processed. No response is required. Timestamp of last processed log record: timestamp_of_last_log_record This message displays the timestamp of the last log record, which is used to determine the time differential between now and the log record currently being processed. Processing continues. No response is required. Time differential (in seconds): time_in_seconds This message displays the time differential in seconds between now and the timestamp of the log record currently being processed. Processing continues. No response is required. Restart info invalid (reason=<reason_code>) The HP3000 CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart info.
PWX-11000 to PWX-11999
449
Restart info length <length> invalid, must be <length> The HP3000 CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart info. Restart info volume index <volume_index> invalid, must be <volume_index> The HP3000 CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart info or correct the CAPI configuration information to reflect the correct volume set name. Sequence info invalid (reason=<reason_code>) The HP3000 CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Sequence info length <length> invalid, must be <length> The HP3000 CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Location missing The HP3000 CAPI module requires that location be specified in the CAPI_CONNECTION information. The system returns an error to the calling software. Correct the CAPI_CONNECTION information. Volume set missing The HP3000 CAPI module requires that volume set be specified in the CAPI_CONNECTION information. The system returns an error to the calling software. Correct the CAPI_CONNECTION information. Pseudo : <number>
PWX-11113 Explanation: System Action: User Response: PWX-11114 Explanation: System Action: User Response: PWX-11115 Explanation: System Action: User Response: PWX-11116 Explanation: System Action: User Response: PWX-11117 Explanation: User Response: PWX-11118 Explanation: User Response: PWX-11119 Explanation: User Response:
The HP3000 CAPI module uses this message to format restart information. No response is required. Byte offset : <number> The HP3000 CAPI module uses this message to format restart information. No response is required. Log File : <number>
The HP3000 CAPI module uses this message to format restart information. No response is required.
450
PWX-11120 Explanation: User Response: PWX-11121 Explanation: User Response: PWX-11122 Explanation: System Action: User Response: PWX-11123 Explanation: System Action: User Response: PWX-11125 Explanation: System Action: User Response: PWX-11126 Explanation: System Action: User Response: PWX-11127 Explanation: System Action: User Response: PWX-11128 Explanation: System Action: User Response: PWX-11129 Explanation: User Response:
Volume index: <number> The HP3000 CAPI module uses this message to format restart information. No response is required. Earliest available log record The HP3000 CAPI module uses this message to format restart information. No response is required. API call function_name returned return_code The HP3000 CAPI module encountered an unexpected return code from the call indicated. The system returns an error to the calling software. Contact Informatica Global Customer Support. no_filter_tag and other tags cannot be mixed The HP3000 CAPI module encountered the special registration tag indicating no filtering in combination with other registration tags. The system returns an error to the calling software. Contact Informatica Global Customer Support. Invalid tag at index index_number (registration_tag) The HP3000 CAPI module encountered an invalid registration tag at the index indicated. The system returns an error to the calling software. Contact Informatica Global Customer Support. Invalid record type (record_type) returned from read The HP3000 CAPI module encountered an unexpected record type on the HP3000 log. The system returns an error to the calling software. Contact Informatica Global Customer Support. Invalid action type ('character_action_code' 0xhex_action_code) returned from read The HP3000 CAPI module encountered an unexpected action code on the HP3000 log. The system returns an error to the calling software. Contact Informatica Global Customer Support. Error retrieving sequence number from record The HP3000 CAPI module encountered an error when attempting to retrieve the sequence number from a HP3000 log record. The system returns an error to the calling software. Contact Informatica Global Customer Support. Seq: sequence_number The HP3000 CAPI module uses this message to report the sequence of a record associated with other messages. No response is required.
PWX-11000 to PWX-11999
451
Error retrieving sequence number for current end of log The HP3000 CAPI module encountered an error when attempting to retrieve the sequence number of the current end of log. The system returns an error to the calling software. Contact Informatica Global Customer Support. Repository call <function_name> failed for repository <return_code> The HP3000 CAPI module encountered an error when attempting to interact with the repository. The system returns an error to the calling software. Contact Informatica Global Customer Support. Tag registration_tag volume set <volume_set_name> does not match configured volume set <volume_set_name> The HP3000 CAPI module determined that the registration tag in question does not appear to be on the volume set specified in the CAPI_CONNECTION information. The system returns an error to the calling software. Correct the source of the invalid restart info or correct the CAPI configuration information to reflect the correct volume set name. No active entry for registration tag <registration_tag> found in repository <location> The HP3000 CAPI module could not locate the registration tag specified in the repository at the location specified. The system returns an error to the calling software. Correct the problem by specifying the correct location or removing the registration tag from the list of sources. Sequence info volume index <volume_index> invalid, must be <volume_index> The HP3000 CAPI module encountered invalid sequence information. The system returns an error to the calling software. Correct the source of the invalid restart info or correct the CAPI configuration information to reflect the correct volume set name. Invalid tag (registration_tag) The HP3000 CAPI module encountered an invalid registration tag. The system returns an error to the calling software. Contact Informatica Global Customer Support.
PWX-12000 to PWX-12999
452
DBAP: ERROR: <error_message> An error occurred as described in error_message. A diagnostics log is created and processing ends. Correct entry and restart Apply.
PWX-12003 Explanation: User Response: PWX-12004 Explanation: User Response: PWX-12005 Explanation: User Response: PWX-12006 Explanation: User Response: PWX-12007 Explanation: User Response: PWX-12008 Explanation: User Response: PWX-12009 Explanation: User Response: PWX-12010 Explanation: User Response: PWX-12011 Explanation: User Response: PWX-12012 Explanation: User Response: PWX-12013 Explanation: User Response: PWX-12014 Explanation:
DBAP: __DBAP__RESERVED__12003 Reserved. No response is required. APPOPT LOGPATH=pathname (ignored for OS/390) This message displays Apply configuration parameter information. No response is required. SECOPT PWDENCRYPT={Y|N} This message displays Apply configuration parameter information. No response is required. SECOPT TYPE={DATABASE|SYSTEM} This message displays Apply configuration parameter information. No response is required. RSOPT RESTARTTB=restart_table_name This message displays Apply configuration parameter information. No response is required. RSOPT STATUSTB=status_table_name This message displays Apply configuration parameter information. No response is required. RSOPT RESTARTTS=tablespace_name This message displays Apply configuration parameter information. No response is required. APPOPT APPLYNAME=applyname (max 8 characters) This message displays Apply configuration parameter information. No response is required. APPOPT ANALYZE={Y|N} This message displays Apply configuration parameter information. No response is required. APPOPT ERRORSTATS={Y|N} This message displays Apply configuration parameter information. No response is required. RSPOPT MAINT=(INIT=x,...) (valid values INIT={Y|N}) This message displays Apply configuration parameter information. No response is required. APPOPT ARRAYPROCESS={Y|N} This message displays Apply configuration parameter information.
PWX-12000 to PWX-12999 453
User Response: PWX-12015 Explanation: User Response: PWX-12016 Explanation: User Response: PWX-12017 Explanation: User Response: PWX-12018 Explanation: User Response: PWX-12019 Explanation: User Response: PWX-12020 Explanation: User Response: PWX-12021 Explanation: User Response: PWX-12022 Explanation: User Response: PWX-12023 Explanation: User Response: PWX-12024 Explanation: User Response: PWX-12025 Explanation: User Response:
No response is required. APPOPT SKIPROWS=n (where n= 0 - 32767) This message displays Apply configuration parameter information. No response is required. APPOPT PROCESSROWS=n (where n= 0 - 32767) This message displays Apply configuration parameter information. No response is required. APPOPT LOGFORMAT={HTML|TEXT} This message displays Apply configuration parameter information. No response is required. APPOPT STATINTERVAL=n (where n= 0 - 120) This message displays Apply configuration parameter information. No response is required. APPOPT LOADDATA={Y|N} This message displays Apply configuration parameter information. No response is required. APPOPT PERFMON=n (where n= 0 - 120) This message displays Apply configuration parameter information. No response is required. DBWAITTIME=n (where n= 0 - 120) This message displays Apply configuration parameter information. No response is required. APPERR option1, option2,... This message displays Apply configuration parameter information. No response is required. TABOPT option1, option2,... This message displays Apply configuration parameter information. No response is required. IDCOL This message displays Apply configuration parameter information. No response is required. AUTOCORRECT This message displays Apply configuration parameter information. No response is required.
454
TABOPT table_name This message displays Apply configuration parameter information. No response is required. TABOPT IDCOL COLNAME This message displays Apply configuration parameter information. No response is required. MATTEST parm Valid values (Y or N) This message displays Apply configuration parameter information. No response is required. Error Option Type Valid values (INCO,UNEX,AVAL,CODE) This message displays Apply configuration parameter information. No response is required. Error Option Limit This message displays Apply configuration parameter information. No response is required. Error Option Code This message displays Apply configuration parameter information. No response is required. Error Option Action Valid values (SKIP=Y or SKIP=N) This message displays Apply configuration parameter information. No response is required. Apply CMD Valid values (APPOPT;TABOPT;RSOPT;APPERR;TABERR;SECOPT;IDCOL) This message displays Apply configuration parameter information. No response is required. APPOPT STOPONWARN={Y|N} This message displays Apply configuration parameter information. No response is required. TOKEN This message displays Apply configuration parameter information. No response is required. FLAG This message displays Apply configuration parameter information. No response is required.
PWX-12000 to PWX-12999
455
PWX-12037 Explanation: User Response: PWX-12043 Explanation: System Action: User Response: PWX-12044 Explanation: User Response: PWX-12045 Explanation: User Response: PWX-12046 Explanation: User Response: PWX-12047 Explanation:
xxxERR TYPE=({AVAL|UNEX|INCO|CODE}, limit, code, {Y|N}) where l = 0 - 32767 and code = 0 - 32767) This message displays Apply configuration parameter information. No response is required. STATUSINDEX (required for MVS/DB2) This message displays Apply configuration parameter information. A diagnostics log is created and processing ends. Specify the STATUSINDEX parameter in the RSOPT section and restart Apply. TABERR This message displays Apply configuration parameter information. No response is required. DBAP: INFO: IDCOL specification overriding primary key column <column> for table <table> An IDCOL was specified for a primary key column. No response is required. DBAP: INFO: IDCOL specified for column <column>, table <table> An IDCOL entry was specified for column column in table table. No response is required. DBAP: WARNING: No primary Key or IDCOL specification found for table = <table> No primary key was defined on the specified target table and no IDCOL options were found for that table in the Apply configuration file. Performance for DELETE and UPDATE processing might be impacted. No response is required. RSPOPT MAINT=(__BYPASS=x,...) (valid values __BYPASS= {Y|N}) This message displays Apply configuration parameter information. No response is required. No row was found for DELETE or the result of a query is an empty table Error occurred during DELETE. A FAILED SQL log is created. Correct error and restart Apply. No row was found for UPDATE or the result of a query is an empty table Error occurred during UPDATE. A FAILED SQL log is created. Examine Failed SQL LOG to determine if the error was acceptable. Error has been corrected by AUTOCORRECT option AUTOCORRECT processing was used to correct Database Integrity error. A FAILED SQL log is created.
User Response: PWX-12048 Explanation: User Response: PWX-12049 Explanation: System Action: User Response: PWX-12050 Explanation: System Action: User Response: PWX-12051 Explanation: System Action:
456
Examine Failed SQL LOG to determine if the error was acceptable. Failed on Prepare of SQL statement DBMS Failed to prepare a SQL Statement. A FAILED SQL log is created. Examine Failed SQL LOG to determine if the error was acceptable. Correct error and restart Apply if applicable. APPOPT UOWABORT = {Y|N} Parse error for Apply configuration, UOWABORT. Valid values are Y or N. A diagnostics log is created and processing ends. Correct entry and restart Apply. RSOPT MAINT=(x=y,...) (where x = keywords TYPE,UID,DB,PWD,INIT) This message displays Apply configuration parameter information. No response is required. APPOPT MAXHANDLES=n (where n= 20 - 32767) This message displays Apply configuration parameter information. No response is required. RSOPT MAINT=(DBNAME=dbname,...) This message displays Apply configuration parameter information. No response is required. RSOPT MAINT=(DBNAME={UDBDB2|DB2|ORACLE|MSSQL} ,...) This message displays Apply configuration parameter information. No response is required. RSOPT MAINT=(UID=user_ID,...) This message displays Apply configuration parameter information. No response is required. RSOPT MAINT=(PWD=password,...) This message displays Apply configuration parameter information. No response is required. RSOPT MAINT=(INIT={Y|N},...) This message displays Apply configuration parameter information. No response is required. RSOPT MAINT=(__BYPASS={Y|N},...) This message displays Apply configuration parameter information. No response is required.
PWX-12053 Explanation: System Action: User Response: PWX-12054 Explanation: User Response: PWX-12055 Explanation: User Response: PWX-12056 Explanation: User Response: PWX-12057 Explanation: User Response: PWX-12058 Explanation: User Response: PWX-12059 Explanation: User Response: PWX-12060 Explanation: User Response: PWX-12061 Explanation: User Response:
PWX-12000 to PWX-12999
457
PWX-12062 Explanation: User Response: PWX-12063 Explanation: User Response: PWX-12064 Explanation: User Response: PWX-12065 Explanation: User Response: PWX-12066 Explanation: User Response: PWX-12067 Explanation: User Response: PWX-12068 Explanation: System Action: User Response: PWX-12069 Explanation: System Action: User Response: PWX-12070 Explanation: System Action: User Response: PWX-12071 Explanation: User Response:
RSOPT CREATE_RS_TABLES={Y|N} This message displays Apply configuration parameter information. No response is required. TABOPT ADDSTATUSACTIVE = {Y|N} This message displays Apply configuration parameter information. No response is required. RSOPT ADDSTATUSACTIVE = {Y|N} This message displays Apply configuration parameter information. No response is required. APPOPT COMMIT=({UOW|ROW|SEC}, nnnnn) This message displays Apply configuration parameter information. No response is required. COMMIT=(type, nnnnn) where type = {UOW|ROW|SEC} This message displays Apply configuration parameter information. No response is required. COMMIT=(type, nnnnn) where nnnnn = 0 - 99999 This message displays Apply configuration parameter information. No response is required. DBAP: CONFIG ERROR: Commit Freq (specified in command set MV TO ...COMMIT=x) is not compatible with APPOPT UOWABORT=Y Parse error for Apply configuration. Parameters are mutually exclusive. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: CONFIG ERROR: APPOPT COMMIT=(UOW,x) is not compatible with APPOPT UOWABORT=Y. Parse error for Apply configuration. Parameters are mutually exclusive. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: CONFIG ERROR: Error processing Apply configuration file. Parse or file error occurred for Apply configuration. Review Apply log for errors. A diagnostics log is created and processing ends. Correct entry and restart Apply. MATTEST: UPDATEIMAGE= {AI|BA|TU} MATTEST Configuration Parameter Information. No response is required.
458
DBAP: CONFIG ERROR: APPOPT must appear before any TABOPT or TABERR parms are specified. Parse error for Apply configuration. Parameters are not in correct order. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: CONFIG ERROR: SECOPT must appear before any TABOPT or TABERR parms are specified. Parse error for Apply configuration. Parameters are not in correct order. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: CONFIG ERROR: RSOPT must appear before any TABOPT or TABERR parms are specified. Parse error for Apply configuration. Parameters are not in correct order. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: CONFIG ERROR: APPERR must appear before any TABOPT or TABERR parms are specified. Parse error for Apply configuration. Parameters are not in correct order. A diagnostics log is created and processing ends. Correct entry and restart Apply. APPOPT MSSQL_SERVER= servername Parse error for Apply configuration. Required for MS SQL Server. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: CONFIG ERROR: SQLTYPE not valid for DBMS Parse error for Apply configuration. A diagnostics log is created and processing ends. Select a valid SQLTYPE and restart Apply. DBAP: CONFIG ERROR: SQLTYPE not valid for platform Parse error for Apply configuration. A diagnostics log is created and processing ends. Select a valid SQLTYPE and restart Apply. DBAP: ERROR: <error_message> An error occurred as described in error_message. A diagnostics log is created and processing ends. Correct error(s) and restart Apply.
PWX-12000 to PWX-12999
459
PWX-12101 Explanation: System Action: User Response: PWX-12102 Explanation: System Action: User Response: PWX-12103 Explanation: User Response: PWX-12105 Explanation: System Action: User Response: PWX-12106 Explanation: System Action: User Response:
DBAP: Internal Error: <error_message> An internal error occurred as described in error_message. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: WARNING: <warning_message> A warning occurred as described in warning_message. Processing continues. No response is required. User might evaluate warning for later processing. DBAP: <message> This message is described in message. No response is required. DBAP: ERROR: Creation of new DB adaptor failed An error occurred while trying to create a new Database connection adaptor. A diagnostics log is created and processing ends. Review the Apply Log for previous errors. Correct errors and restart Apply. DBAP: ERROR: Open log failed for log name: <log_name> An output log could not be opened. A diagnostics log is created and processing ends. Review and correct the LOGPATH parameter in the DBMOVER configuration file and the Apply configuration file. Ensure that these directories have WRITE access for distributed systems. For MVS systems, ensure that the DD names for logs are spelled correctly. Then, restart Apply.
Inconsistency Errors processed = <n>, Limit = <n>, Skip = <{Y|N}>, SetLvl = <{A|T|*}> Informational message that displays the Inconsistency error processing for a table. This message is preceded by message PWX-12112.

Errors processed = <n>. Number of actual errors processed. Limit = <n>. Error limit specified on APPERR or TABERR apply configuration parameter. Skip = <{Y|N}>. Error skip action specified on APPERR or TABERR apply configuration parameter. SetLvl = <{A|T|*}>. A = options set in APPERR or default. T= options set in TABERR [*]. If an asterisk (*) is displayed, this indicates that Limit was exceeded. User Response: PWX-12108 Explanation: No response is required. Unavailable Errors processed = <n>, Limit = <n>, Skip = <{Y|N}>, SetLvl = <{A|T|*}> Informational message that displays the Unavailable error processing for a table. This message is preceded by message PWX-12112.
Errors processed = <n>. Number of actual errors processed. Limit = <n>. Error limit specified on APPERR or TABERR apply configuration parameter. Skip = <{Y|N}>. Error skip action specified on APPERR or TABERR apply configuration parameter.
460
SetLvl = <{A|T|*}>. A = options set in APPERR or default. T= options set in TABERR [*]. If an asterisk (*) is displayed, this indicates that Limit was exceeded.
No response is required. Unexpected Errors processed = <n>, Limit = <n>, Skip = <{Y|N}>, SetLvl = <{A|T|*}> Informational message that displays the Unexpected error processing for a table. This message is preceded by message PWX-12112.
Errors processed = <n>. Number of actual errors processed. Limit = <n>. Error limit specified on APPERR or TABERR apply configuration parameter. Skip = <{Y|N}>. Error skip action specified on APPERR or TABERR apply configuration parameter. SetLvl = <{A|T|*}>. A = options set in APPERR or default. T= options set in TABERR [*]. If an asterisk (*) is displayed, this indicates that Limit was exceeded. User Response: PWX-12110 Explanation: No response is required. Error Code <code> Errors processed = <n>, Limit = <n>, Skip = <{Y|N}>, SetLvl = <{A|T|*}> Informational message that displays the Unexpected error processing for a table. This message is preceded by message PWX-12112.

Errors processed = <n>. Number of actual errors processed. Limit = <n>. Error limit specified on APPERR or TABERR apply configuration parameter. Skip = <{Y|N}>. Error skip action specified on APPERR or TABERR apply configuration parameter. SetLvl = <{A|T|*}>. A = options set in APPERR or default. T= options set in TABERR [*]. If an asterisk (*) is displayed, this indicates that Limit was exceeded. User Response: PWX-12112 Explanation: User Response: PWX-12113 Explanation: System Action: User Response: PWX-12114 Explanation: System Action: User Response: PWX-12115 Explanation: System Action: User Response: No response is required. DBAP: INFO: Error handling specifications (APPERR, TABERR) for table_name Error options display for the specified table. This message is followed by one or more of the following messages: PWX-12107, PWX-12108, PWX-12109, or PWX-12110. No response is required. DBAP: ERROR: Parm STATUSINDEX not specified. This parm is required for DB2. Parse error for Apply configuration. An index for Restart/Status tables is required for MVS DB2. A diagnostics log is created and processing ends. Correct entry and restart Apply. DBAP: Internal error: DBCB must be a connection DBCB An internal error occurred during PowerExchange Apply Processing. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: Internal error: DBCB must be a member DBCB An internal error occurred during PowerExchange Apply Processing. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs.
PWX-12000 to PWX-12999 461
DBAP: Internal error: An invalid pointer was found for structure structure address = address An internal error occurred during PowerExchange Apply Processing. A diagnostics log is created and processing ends. Collect logs and contact Informatica Global Customer Support. TYPE=<type>, CODE=<code>, LIMIT=<limit>, SKIP=<{Y|N}>, ERRORS=<errors>, SETLVL=<{A|T|*}> Specifies the error handling and limits by type, Set by APPERR and /or TABERR in Apply Configuration.
type is one of the following values: INCO UNEX AVAL CODE code is the DBMS code if the specified TYPE is CODE. limit is the number of errors to process through SKIP. SKIP=<{Y|N}>. Specifies the action to be taken if LIMIT is exceeded. errors is the number of errors processed for error handling option. SETLVL=<{A|T|*}>. Level at which the error handling options were specified. If the set level value is an asterisk (*), the error handling limit was exceeded. User Response: PWX-12120 Explanation: System Action: User Response: PWX-12123 Explanation: System Action: User Response: PWX-12124 Explanation: System Action: User Response: No response is required. DBAP: ERROR: Apply DB connection could not be instantiated. An internal error occurred during PowerExchange Apply Processing. A diagnostics log is created and processing ends. Review logs for previous errors. Correct errors and restart Apply. DBAP: ERROR: Memory allocation error in function: function The specified Apply function could not obtain the required memory. A diagnostics log is created and processing ends. Contact your system administrator to request additional memory. DBAP: ERROR: Error obtaining restart/status information for table <table> During PowerExchange Apply restart processing for the specified table, an error occurred. A diagnostics log is created and processing ends. Ensure that the Restart/Status tables were created properly. Review Apply and system logs for previous errors. Correct errors. Then, restart Apply. DBAP: ERROR: Unhandled Exception caught. Function: function OS errno = error_number error_message During PowerExchange Apply processing in the specified function, an unhandled error occurred. In the message text:
function is the function. error_number is the operating system error number.This value might or might not be present depending on the operating system.
462
error_message is the operating system error message. This value might or might not be present depending on the operating system.
A diagnostics log is created and processing ends. Review Apply and system logs to determine the failing component. If the problem persists, contact Informatica Global Customer Support. DBAP: ERROR: Apply Engine Open failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Close Connection failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Close failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Insert failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Update failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Delete failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs.
PWX-12000 to PWX-12999
463
DBAP: ERROR: Apply Engine Commit failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Rollback failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Describe failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Apply Engine Open Connection failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DTL: Internal Error: CallStack Overflow An internal error occurred during PowerExchange Apply Processing. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DTL: ERROR: Memory allocation failed. A function in Apply could not obtain the required memory. A diagnostics log is created and processing ends. Contact your System Administrator for making more memory available. DBAP: Internal error. Unhandled exception during parsing of config file or DBCB_APPLY corrupted. An internal error occurred during PowerExchange Apply Processing. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Error occurred during configuration processing for input file <file> During processing of the Apply configuration file, an error occurred.
464
A diagnostics log is created and processing ends. Review the Apply log for error messages to determine the cause of the failure. Correct errors. Then, restart Apply if applicable. DBAP: ERROR: OS Error found: error_number error_message During Apply processing, an operating system error occurred. A diagnostics log is created and processing ends. Review the Apply log for error messages to determine the cause of the failure. Correct errors. Then, restart Apply if applicable. Or, collect logs and contact Informatica Global Customer Support. Task Name = task_name
PWX-12146 Explanation: User Response: PWX-12147 Explanation: User Response: PWX-12148 Explanation: User Response: PWX-12151 Explanation: System Action: User Response: PWX-12153 Explanation: User Response: PWX-12155 Explanation: User Response: PWX-12156 Explanation: System Action: User Response:
This message displays the job or task name. No response is required. Task ID = task_ID
This message displays the job or process ID. No response is required. <Informatica_copyright_information> This message provides copyright details. No response is required. DBAP: Internal Error: DBCB contained zero rows A Data Base Control Block was received that did not contain any rows. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. Name Nullable Precision Scale Length KeyPos IdCol DTL Ignore Type
This message displays column attributes of a selected table and is preceded by message PWX-1 12155. See message PWX-12154 for description of displayed information. No response is required. Column Description for table table_name This message displays column attributes for the specified table. See message PWX-12153, and PWX-12154 for description of displayed information. No response is required. DBAP: ERROR: Database Disconnect failed. An error trying close or free resources for a DBMS. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs.
PWX-12000 to PWX-12999
465
DBAP: ERROR: Apply Engine INIT failed. An error caused an apply function to fail. This message is preceded by other error messages. A diagnostics log is created and processing ends. Review Apply Log for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DTLUARST: ERROR: Invalid Command Passed To Program DLTUARST received an invalid command. A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. DTLUARST: ERROR: Get EMR Info Failed Get EMR Info Failed. A diagnostics log is created and processing ends. Review Apply Log for additional error messages that caused this function to fail. Correct errors and restart DTLUARST utility if applicable. DTLUARST: Insert failed. An insert operation failed. A diagnostics log is created and processing ends. Review Failed SQL Log for additional error messages that caused this function to fail. Correct errors and restart DTLUARST utility if applicable. DTLUARST: Update failed. An Update operation failed. A diagnostics log is created and processing ends. Review Failed SQL Log for additional error messages that caused this function to fail. Correct errors and restart DTLUARST utility if applicable. DTLUARST: Delete failed. A Delete operation failed. A diagnostics log is created and processing ends. Review Failed SQL Log for additional error messages that caused this function to fail. Correct errors and restart DTLUARST utility if applicable. EMR EMRTABLE=table_name Parameter format for DTLUARST utility. A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. DISPLAY={Y|N} Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable.
466
ADD TABLE=table.name Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. REMOVE TABLE=table.name Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. CHANGE TABLE=table.name Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. STATUS={ACTIVE|SKIPUSER} Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. REASON={MATERIALIZED|INITIALIZED|USERID|CORRECTED} Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. SEQ=sequence_number Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. RSTPOINT=restart_point Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. EMR_ROWID=nnnnn Parameter format for DTLUARST utility A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. DTLUARST: Incorrect parms for status table update Invalid parameter for status table update A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable.
PWX-12000 to PWX-12999 467
DBAP: Internal Error: Table Control has invalid State for I/U/D An internal error occurred during PowerExchange Apply Processing. An attempt to use a Table Control Object that was not fully initialized or is terminating. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: Internal Error: Missing Required Virtual Column - column During PowerExchange Apply processing, an internal error occurred. A virtual column that is required by PowerExchange Apply internal processing was not found. A diagnostics log is created and processing ends. Collect logs and contact Informatica Global Customer Support. DBAP: Internal Error: Invalid Action code <action_code> row %row. Expecting <action_code> During PowerExchange Apply Processing, an internal error occurred. A diagnostics log is created and processing ends. Collect logs and contact Informatica Global Customer Support. DBAP: Internal Error: Max number of columns has been exceeded for table table. MAX: max Result: result During PowerExchange Apply processing, an internal error occurred. A select requested more columns than is allowed. A diagnostics log is created and processing ends. Collect logs and contact Informatica Global Customer Support. DTLUARST: Error creating specified EMR table Error occurred while creating specified EMR table A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. TXT statistics follow*/ DTLUARST: Specified row could not be found in EMR table: row_description Error occurred while getting EMR table information A diagnostics log is created and processing ends. Correct errors and restart DTLUARST utility if applicable. DBAP: Internal Error: Commit requested while envelope in effect. An internal error occurred during PowerExchange Apply Processing. A commit action was requested where current sequence number is equal to the previous sequence number. A diagnostics log is created and processing ends. This error might occur while processing single source records to multiple target tables or due to logic errors in exits. If exits are involved, please review any manipulation of restart sequence numbers for errors. Otherwise, Contact Informatica Global Customer Support and provide logs. Insert Update Delete Total
This message displays column headings for message PWX-12203.
468
The system displays message PWX-12203. No response is required. type insert update delete total This message describes the types of records and the operations processed:
type is the type of record and is one of the following values: Successful. Change records that were successfully applied by operation. Auto Corrected. Change records that were successfully auto corrected by operation. Skipped (Restart). Change records that were skipped due to Restart Status or Sequence number by operation. Inconsistency Errors. Change records that were in error due to Inconsistency errors by operation. Unavailable Errors. Change records that were in error due to DBMS Unavailable errors by operation. Unexpected Errors. Change records that were in error due to DBMS Unexpected errors by operation. Rolled Back. Change records that were Rolled Back due to other errors. by operation. insert indicates that an insert was performed. update indicates that an update was performed. delete indicates that a delete was performed. total is the total number of change records that were processed by operation. User Response: PWX-12204 Explanation: User Response: PWX-12205 Explanation: User Response: PWX-12216 Explanation: User Response: PWX-12217 Explanation: User Response: PWX-12222 Explanation: User Response: PWX-12224 Explanation: User Response: This message displays the heading information for Apply statistics. No response is required. Status Insert Update Delete Total This message displays the column headings for message PWX-12203. No response is required. *** A P P L Y S T A T I S T I C S *** This message displays the heading information for Apply statistics. No response is required. No response is required. DBAP: INFO: *** A P P L Y S T A T I S T I C S ***
This message displays the heading for Apply statistics. No response is required. ____________ __________ __________ __________ This message displays the heading underline for Apply statistics. No response is required.
This message displays when statistics are printed for Apply. No response is required.
PWX-12000 to PWX-12999
469
PWX-12225 Explanation: User Response: PWX-12226 Explanation: User Response: PWX-12232 Explanation: User Response: PWX-12234 Explanation: User Response: PWX-12236 Explanation: User Response: PWX-12237 Explanation: User Response: PWX-12250 Explanation: System Action: User Response:
Status____________ ___________ _ ____________ ____________ This message provides formatting. No response is required. Number of Commits =n
This message displays the number for commits processed by Apply. No response is required. Total Elapsed Time (Seconds) = secs This message displays the Total Elapsed time for Apply processing. No response is required. Total CPU Time (Seconds) = seconds
This message is informational. Total CPU time used by Apply. No response is required.
This message provides formatting. No response is required.
This message provides formatting. No response is required. DBAP: ERROR: Restart Processing: Allocating RESTART/STATUS tables failed. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Restart Processing: Allocating RESTART/STATUS tables failed during initialization. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Restart Processing: RESTART/STATUS table initialization failed. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs.
470
DBAP: ERROR: Restart Processing: RESTART/STATUS table processing failed. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable, or contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Restart Processing: no RESTARTDB Object. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: no RESTARTTABLE Object. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: no STATUSTABLE Object. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: Table initialize failed. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: RESTARTDB Object error. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: Error creating DBCB. An error occurred during restart. A diagnostics log is created and processing ends.
PWX-12000 to PWX-12999
471
User Response:
Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: initialize RESTARTTB error An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: SELECT RESTART error An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: Open Restart DBCB error An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART tables. DBAP: ERROR: Restart Processing: Duplicate sequence number. An internal error occurred during PowerExchange Apply Processing. Duplicate sequence number was encountered. PowerExchange Apply internal processing was not found. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Restart Processing: Invalid STATUS. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables. DBAP: ERROR: Restart Processing: Invalid STATUS_REASON. An error occurred during restart. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables.
472
PWX-12271 Explanation: User Response: PWX-12272 Explanation: User Response: PWX-12274 Explanation: User Response: PWX-12276 Explanation: User Response: PWX-12278 Explanation: System Action: User Response:
Restart Table Values Display of restart tables values. No response is required. APPLY_SEQUENCE: value Display APPLY_SEQUENCE values. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables. No response is required. Status Table Values Display of status tables values. No response is required. STATUS : status
Display STATUS values. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables. No response is required. DBAP: ERROR: Rollback processing failed during RESTART processing. An error occurred during restart processing. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables. DBAP: ERROR: Commit processing failed during RESTART processing. An error occurred during restart processing. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables. DBAP: ERROR: New Record Sequence Number is less than current Sequence number. Sequence number order error was encountered. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Bad STATUS transition during Sequence number processing. Bad STATUS transition during Sequence number processing. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Invalid STATUS passed to Sequence number processing. Invalid STATUS passed to Sequence number processing. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs.
PWX-12000 to PWX-12999 473
PWX-12286 Explanation: User Response: PWX-12288 Explanation: User Response: PWX-12290 Explanation: System Action: User Response: PWX-12291 Explanation: System Action: User Response: PWX-12292 Explanation: System Action: User Response: PWX-12293 Explanation: System Action: User Response: PWX-12294 Explanation: System Action: User Response: PWX-12295 Explanation: System Action: User Response: PWX-12296 Explanation: System Action: User Response:
Current APPLY_SEQUENCE: seqnumber Current Sequence number of change record being processed. No response is required. Apply RESTART table: table_name Name of RESTART table. No response is required. DBAP: ERROR: Invalid parameter passed to ::F00_GetNextRow. Invalid parameter passed to ::F00_GetNextRow. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Already connected to server. An attempt was made to connect to a server with an active connection. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Not connected to server. An attempt was made to connect to a server without an active connection. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Error during data conversion. Output buffer too small. Error converting data. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Maximum error count for the connection has been reached. The error limit was exceeded for the DBMS connection. The error limits are specified in APPERR and TABERR in the Apply configuration file. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Commit of current transaction failed. Error occurred during a COMMIT. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Rollback of current transaction failed. Error occurred during a Rollback. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
474
DBAP: ERROR: Wait time for DBMS function has been exceeded. A DBMS transaction took longer than specified in APPOPT DBWAITTIME. A diagnostics log is created and processing ends. Look for possible deadlocks or degraded performance on the DBMS server such as large tables without or invalid indexes. Correct errors and restart Apply if applicable. DBAP: ERROR: LRU - no handles were found. A error was issued during DBMS handle LRU processing. See the user guide section on DBMS handle LRU processing. Correct errors and restart Apply if applicable. DBAP: ERROR: LRU - statement handle release failed. A error was issued during DBMS handle LRU processing. See to the user guide section on DBMS handle LRU processing. Correct errors and restart Apply if applicable. DBAP: ERROR: Empty SELECT statement passed to ::SelectTableData function. Empty SELECT statement passed to ::SelectTableData function. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. DBAP: ERROR: Restart Processing: Invalid status table values for table table Status table values for specified table are invalid. Likely caused by Sequence number or restart point value that are inexistent with status/status reason values. A diagnostics log is created and processing ends. Review Apply Log/FAILED SQL LOG for error messages that caused this function to fail. Correct errors and restart Apply if applicable. Consult the documentation for utility DTLUARST for creating and maintaining RESTART/STATUS tables. DBAP: ERROR: UDB - SQLPrepare failed. SQLPrepare failed during UDB processing. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - execution failed. SQLExecute failed during UDB processing. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - column description failed. An attempt to obtain a column description failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
PWX-12000 to PWX-12999
475
476
DBAP: ERROR: UDB - column bind failed. An attempt to bind a column failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - column bind failed. An attempt to bind a column failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - get next row failed An attempt to get next row failed after a SELECT. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - Rollback of current transaction failed. Rollback of current transaction failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - Commit of current transaction failed. Commit of current transaction failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLAllocHandle env failed. UDB function, SQLAllocHandle env failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLAllocHandle con failed. UDB function, SQLAllocHandle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLAllocHandle stmt failed. UDB function, SQLAllocHandle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLSetStmtAttr failed. UDB function, SQLSetStmtAttr failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
DBAP: ERROR: UDB - SQLFreeHandle env failed. UDB function, SQLFreeHandle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLFreeHandle con failed. UDB function, SQLFreeHandle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLFreeHandle stmt failed. UDB function SQLFreeHandle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLParamOptions failed. UDB function SQLParamOptions failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLNumResultCols failed. UDB function SQLNumResultCols failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - Library load failed. DBMS load library failed. A diagnostics log is created and processing ends. Verify that STEPLIB/JOBLIB or PATH is correct for DBMS Library. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - SQLConnection open failed. UDB function, SQLConnection failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - Allocate bind failed. UDB function Allocate bind failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: UDB - Populate bind failed. UDB function Populate bind failed. A diagnostics log is created and processing ends.
PWX-12000 to PWX-12999
477
User Response: PWX-12335 Explanation: User Response: PWX-12336 Explanation: System Action: User Response: PWX-12370 Explanation: System Action: User Response: PWX-12371 Explanation: System Action: User Response: PWX-12372 Explanation: System Action: User Response: PWX-12373 Explanation: System Action: User Response: PWX-12374 Explanation: System Action: User Response: PWX-12375 Explanation: System Action: User Response: PWX-12376 Explanation: System Action:
478
Correct errors and restart Apply if applicable. DBAP: WARN: UDB - Performance degraded: Dynamic statement caching not enabled. UDB to increase performance Informatica recommends that Dynamic Statement Cashing be enabled in DBMS If increased performance is desired, enable Dynamic Statement Cashing in DBMS DBAP: ERROR: UDB - Set statement option failed. UDB function Set statement option failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Prepare failed. ORACLE function Prepare failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Execution failed ORACLE function Execution failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Column bind failed ORACLE function Column bind failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Rollback of current transaction failed. ORACLE function Rollback failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Commit of current transaction failed. ORACLE function Commit failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIHandleAlloc stmt failed. ORACLE function OCIHandleAlloc failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIHandleFree stmt failed. ORACLE function OCIHandleFree failed. A diagnostics log is created and processing ends.
Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIGetAttrParam count failed. ORACLE function OCIGetAttrParam failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIStmtFetch failed. ORACLE function OCIStmtFetch failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIStmtFetch2 failed. ORACLE function OCIStmtFetch failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIDefineByPos failed. ORACLE function OCIDefineByPos failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIParamGet failed. ORACLE function OCIParamGet failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIGetAttr failed. ORACLE function OCIGetAttr failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIHandleAlloc stmt failed. ORACLE function OCIHandleAlloc failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Bind Buffers failed. ORACLE function Allocate Bind Buffers failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
PWX-12000 to PWX-12999
479
DBAP: ERROR: ORACLE - Library load failed. DBMS load library failed. A diagnostics log is created and processing ends. Verify STEPLIB/JOBLIB or PATH is correct for DBMS Library. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Connection open failed. ORACLE function Connection open Buffers failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Environmental variable ORACLE_HOME does not exist. A required environment variable does not exist. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Environmental variable ORACLE_HOME not defined. A required environment variable does not exist. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Populate Bind Buffers failed. ORACLE function Populate Bind Buffers failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - OCIDescribeAny failed. ORACLE function OCIDescribeAny failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: DB Bind failed for table = <table> column = <column> pos = position at line = line A DBMS function bind failed. A diagnostics log is created and processing ends. Correct errors. Then, if applicable, restart Apply. DBAP: ERROR: ORACLE - Initialize DB connection in OCIEnvCreate failed. ORACLE function OCIEnvCreate failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Error Handle 1 failed. ORACLE function Allocate Error Handle failed.
PWX-12386 Explanation: System Action: User Response: PWX-12387 Explanation: System Action: User Response: PWX-12388 Explanation: System Action: User Response: PWX-12390 Explanation: System Action: User Response: PWX-12391 Explanation: System Action: User Response: PWX-12392 Explanation: System Action: User Response: PWX-12393 Explanation: System Action: User Response: PWX-12394 Explanation:
480
A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Error Handle 2 failed. ORACLE function Allocate Error Handle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Error Handle 3 failed. ORACLE function Allocate Error Handle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Server Handle failed. ORACLE function Allocate Server Handle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Service Context Handle failed. ORACLE function Allocate Context Handle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Attach to server failed. ORACLE function Attach failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Set server handle attribute in service context failed. ORACLE function Set server handle failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Allocate Session Handle failed. ORACLE function Allocate failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Set username attribute in Session Handle failed. ORACLE function Set attribute failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
PWX-12000 to PWX-12999
481
DBAP: ERROR: ORACLE - Set password attribute in Session Handle failed. ORACLE function Set attribute failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Session Start failed. ORACLE failed to start session, A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - Set Session Handle in Service Context failed. ORACLE Set Session Handle in Service Context failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: ORACLE - LRU could not recover from ORA-01000. Increase open_cursors. ORACLE LRU could not recover from ORA-01000. Increase open_cursors. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Execute failed. MSSQL function Execute failed. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Prepare failed. MSSQL function Prepare failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failed to return column information. MSSQL function describe failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server row accessor. MSSQL function describe failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
482
DBAP: ERROR: MSSQL - Failure while creating SQL Server row accessor. MSSQL CreateAccessor failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while retrieving row(s) from SQL Server. MSSQL GetNextRows failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while retrieving row data from SQL Server. MSSQL GetData failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server rowset. MSSQL rowset failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server session. QueryInterface -IID_IDBCreateSession failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while creating SQL Server command. MSSQL CreateSession failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server command text. MSSQL CreateCommand failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server column information. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
PWX-12000 to PWX-12999
483
DBAP: ERROR: MSSQL - Failure while initializing SQL Server session. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server command. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server rowset. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server command with parameters. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failed on call to SetParameterInfo for command object. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Populate Bind Buffers failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while performing IMalloc function. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server database connection layer. MSSQL CoCreateInstance function failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server database properties. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends.
484
Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server database connection properties. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server database connection. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while setting data source properties. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while initializing SQL Server Prepare Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Prepare of SQL statement failed. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure during pIDBProperties-GetProperties command. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while setting SQL Server Command Text. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure during IID_ITransactionLocal object creation. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable.
PWX-12000 to PWX-12999
485
DBAP: ERROR: MSSQL - Failure while setting binding information in DBBINDING structure. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while allocating Array Processing data buffers. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while executing StartTransaction. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while executing Transaction Commit. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: MSSQL - Failure while executing Transaction Abort. Message PWX-12298 is issued with MSSQL error information. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Restart Processing: Error Setting Statistics for STATUS table. Apply cannot set error statistics for table. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Restart Processing: Error Setting Statistics for RESTART table. Apply cannot set error statistics for table. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Restart Processing: Restart row not found. Apply is unable find a row in the RESTART table. A diagnostics log is created and processing ends. Correct errors and restart Apply if applicable. DBAP: ERROR: Restart Processing: Apply Restart Table(s) not found. Apply is unable find specified restart table(s). A diagnostics log is created and processing ends.
486
User Response: PWX-12499 Explanation: System Action: User Response: PWX-12500 Explanation: System Action: User Response: PWX-12501 Explanation: System Action: User Response: PWX-12502 Explanation: System Action: User Response: PWX-12503 Explanation: System Action: User Response: PWX-12504 Explanation: System Action: User Response: PWX-12505 Explanation: System Action: User Response: PWX-12506 Explanation: System Action: User Response: PWX-12507 Explanation:
Correct errors and restart Apply if applicable. DBAP: ERROR: Invalid message number for DBAP An invalid apply message was received. A diagnostics log is created and processing ends. Contact Informatica Global Customer Support and provide logs. Xpath not found The requested XML element (refused to using XPATH syntax) was not found in the configuration document. Up to the calling application. Ensure that the element requested is present in the configuration file. Unable to open XML config file The requested XML configuration document does not exist. Error reported, program ends. Ensure that configuration file exists and the path is correct. XML document too large The requested XML configuration document is too large max size 4k. PowerExchange reports the error and the program ends. Reduce the size of the configuration file. Invalid target type parameter Parameter target type invalid, must be a string no longer than 128 characters PowerExchange reports the error and the program ends. Use a valid target type string. Invalid location parameter Parameter location invalid, must be a string no longer than 128 characters PowerExchange reports the error and the program ends. Use a valid location string. Invalid target Parameter target invalid, must be a string no longer than 128 characters PowerExchange reports the error and the program ends. Use a valid target string. Invalid tracefile name. Parameter tracefile invalid, must be a string no longer than 128 characters PowerExchange reports the error and the program ends. Use a valid tracefile string. Invalid user ID Parameter user ID invalid, must be a string no longer than 128 characters
PWX-12000 to PWX-12999 487
PowerExchange reports the error and the program ends. Use a valid user ID string. Invalid password Parameter password invalid, must be a string no longer than 128 characters. PowerExchange reports the error and the program ends. Use a valid password string. Invalid commit type Parameter commit type invalid, must be a string no longer than one character. PowerExchange reports the error and the program ends. Use a valid commit type string, R for random commit interval, otherwise defaults to 1000. Invalid Max records (must be numeric) Parameter Max records invalid, must be numeric. PowerExchange reports the error and the program ends. Use a valid Max records string. Invalid commit interval (must be numeric) Parameter commit interval invalid, must be numeric. PowerExchange reports the error and the program ends. Use a valid commit interval string. Invalid sleep interval (must be numeric) Parameter sleep interval invalid, must be numeric. The units are 1/1000 seconds. PowerExchange reports the error and the program ends. Use a valid sleep interval string. Invalid UID randomize value (must be Y or N) Parameter UID randomize invalid, must be Y or N. PowerExchange reports the error and the program ends. Enter either Y or N for the parameter. Invalid UID pattern Parameter UID pattern invalid, must be string max length 100 characters. PowerExchange reports the error and the program ends. Use a valid UID pattern string. Invalid Startkey (must be numeric) Parameter Startkey invalid, must be numeric. PowerExchange reports the error and the program ends. Use a valid Startkey string.
488
Invalid Endkey (must be numeric) Parameter Endkey invalid, must be numeric. PowerExchange reports the error and the program ends. Use a valid Endkey string. XML processing is no longer supported XML processing not supported in PowerExchange. PowerExchange reports the error and the program ends. DESCRIBE ELEMENTS and DOCS not longer supported EMR: 'CAPI_call' failed rc=(return_code') The CAPI call 'CAPI_call' returned the specified failure return code. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: CAPI_call info generated (rc=(return_code)) The CAPI call 'CAPI_call' returned the specified informational return when not expected. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: CAPI_call warning generated (rc=(return_code)) The CAPI call 'CAPI_call' returned the specified warning return code. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: description: hex_dump character_dump A hexadecimal dump of additional information was generated for description. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: Unexpected CAPI Record. Type=(CAPI_record_type) A CAPI call returned an unexpected CAPI record type 'CAPI_record_type'. See message PWX-12703 for CAPI sequence number. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: ERROR: Internal error: description The EMR Access Method encountered internal error description. The request fails. Collect all messages and logs then contact Informatica Global Customer Support.
PWX-12000 to PWX-12999
489
EMR DATAMAP Internal error: description The EMR Access Method encountered internal error 'description' while building its data map. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: WARNING: Multiple source DBCBs in PROCMODE=APPLY DBMOVE detected at DBCB DBCB_number This is an odd condition. Processing continues. No response is required. EMR: ERROR: PROCMODE=APPLY and Presence missing for DBCB DBCB_number When running in PROCMODE=APPLY, DBCB Presence information for the DBCB with number 'DBCB_number' is missing. The request fails. Collect all messages and logs then contact Informatica Global Customer Support. EMR: EOF due to CAPI_return_code (CAPI_reason_code) This lists the precise CAPI return code and reason code when EMR decided to return EOF. Processing continues. No response is required.
PWX-13000 to PWX-13999
PWX-13001 Explanation: System Action: User Response: Decrypt: Memory Allocation Error An internal error occurred while decrypting a given string. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Input Invalid Character In String An invalid character was found in the string passed to the PowerExchange Decrypt function. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Input Invalid Length The length of the string passed to the PowerExchange Decrypt function is invalid. The task that encounters the error ends.
490
User Response:
Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Input String Is Internal Buffer The PowerExchange Decrypt function was called where the memory address of the input string corresponds to that used by the function. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Input String Is Null The PowerExchange Decrypt function was called without a value to decrypt. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Output String Size Error The PowerExchange Decrypt function was called with insufficient memory allocated to return the decrypted value for the input string passed. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Input String Is Too Long The PowerExchange Decrypt function was called where the length of the string to decrypt is greater than that permitted by the function. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Decrypt: Output String is Too Short The PowerExchange Decrypt function was called with insufficient memory allocated to return the decrypted value for the input string passed. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Encrypt: Memory Allocation Error An internal error occurred while encrypting a given string. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-13000 to PWX-13999
491
Encrypt: Input Invalid Character In String An invalid character was found in the string passed to the PowerExchange Encrypt function. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Encrypt: Input String Is Internal Buffer The PowerExchange Encrypt function was called where the memory address of the input string corresponds to that used by the function. The task that encounters the error ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Encrypt: Input String Is Null The PowerExchange Encrypt function was called without a value to encrypt. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Encrypt: Output String Size Error The PowerExchange Encrypt function was called with insufficient memory allocated to return the encrypted value for the input string passed. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Encrypt: Input String Is Too Long The PowerExchange Encrypt function was called where the length of the string to encrypt is greater than that permitted by the function. The task that encounters the error ends. Correct the string being passed to the function if this is input by the user. Otherwise, contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
PWX-14000 to PWX-14999
PWX-14010 Explanation: System Action: User Response: setReadOnly() cannot be called when in a transaction An error was detected. The task that encounters the error ends. Correct the problem and retry.
492
Custom mapping is not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Stored procedure calls in SQL statements are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Scalar functions in SQL statements are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Outer joins in SQL statements are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Escape character is missing A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. Escape clause keyword is missing A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. Incomplete escape sequence - missing '}' A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. Multiple ResultSets are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Batch updates are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry.
PWX-14000 to PWX-14999 493
494
This method cannot be used with PreparedStatement An error was detected. The task that encounters the error ends. Correct the problem and retry. Invalid maximum field size ignored An illegal field size was specified. The invalid field size is ignored. Supply a valid field size. CallableStatement is not supported by this Driver Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Scrollable ResultSets are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Current row has been deleted An error was detected. The task that encounters the error ends. Correct the problem and retry. Cursor must be positioned on the insert row An error was detected. The task that encounters the error ends. Correct the problem and retry. Cursor must not be positioned on the insert row An error was detected. The task that encounters the error ends. Correct the problem and retry. Zero is not a valid row number An error was detected. The task that encounters the error ends. Specify a valid row number. There is no current row An error was detected. The task that encounters the error ends. Correct the problem and retry.
The ResultSet is closed An error was detected. The task that encounters the error ends. Correct the problem and retry. The ResultSet is not scrollable An error was detected. The task that encounters the error ends. Correct the problem and retry. The ResultSet cannot be updated An error was detected. The task that encounters the error ends. Correct the problem and retry. Custom mapping is not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. Positioned updates are not supported Attempt to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. The Insert Row is empty An error was detected. The task that encounters the error ends. Correct the problem and retry. Connection allocation failed An internal error was detected. The task that encounters the error ends. Correct the problem and retry. PowerExchange initial is at ion failed An internal error was detected. The task that encounters the error ends. Correct the problem and retry. Required parameter parameter is missing A syntax error was detected. The task that encounters the error ends. Correct the problem and retry.
PWX-14000 to PWX-14999 495
496
Unsupported DBTYPE value <value> A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. DB_OPEN failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. Statement allocation failed An internal error was detected. The task that encounters the error ends. Correct the problem and retry. DB_DESCRIBE failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. DB_READ failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. Update failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. Storage allocation failed An error was detected. The task that encounters the error ends. Correct the problem and retry. Invalid DTLXTYPE escape clause <clause> A syntax error has been detected. The task that encounters the error ends. Correct the problem and retry. Invalid DTLIMTYPE escape clause <clause> A syntax error was detected in the specified clause. The task that encounters the error ends. Correct the problem and retry.
DBNAME2 is required for CAPX/CAPXRT An error was detected. The task that encounters the error ends. Correct the problem and retry. Commit failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. Rollback failed, rc=<return_code> An internal error was detected. The task that encounters the error ends. Correct the problem and retry. Column number nnn out of range An error was detected. The task that encounters the error ends. Correct the problem and retry. Unsupported SQL statement type <type> An attempt was made to use an unsupported feature. The task that encounters the error ends. Correct the problem and retry. UPDATE statement is missing SET A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. Parameter number nnn is out of range An error was detected. The task that encounters the error ends. Correct the problem and retry. INSERT statement is missing VALUES A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. Unknown column name <name> An error was detected. The task that encounters the error ends. Correct the problem and retry.
PWX-14000 to PWX-14999 497
PWX-14221 Explanation: System Action: User Response: PWX-14222 Explanation: System Action: User Response: PWX-14223 Explanation: System Action: User Response: PWX-14224 Explanation: System Action: User Response: PWX-14225 Explanation: System Action: User Response: PWX-14226 Explanation: System Action: User Response: PWX-14300 Explanation: System Action: User Response: PWX-14302 Explanation: User Response: PWX-14303 Explanation:
Statement cannot contain placeholder A syntax error was detected. The task that encounters the error ends. Correct the problem and retry. Invalid SQL statement for Query <query> A syntax error has been detected. The task that encounters the error ends. Correct the problem and retry. DB_INSERT failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. SQL Statement <statement> requires WHERE A syntax error has been detected. The task that encounters the error ends. Correct the problem and retry. DB_CLOSE failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. DB_CLOSECURSOR failed, rc=return_code An error was detected. The task that encounters the error ends. Correct the problem and retry. DTLUCDEP argument format error found keyword The parameter or argument fed to DTLUCDEP does not start with the cs= keyword. The request fails. Correct argument and resubmit. Field override required Used in command parsing messages. No response is required. Override value can only be FORCE to modify protected data got parameter The override value is used as FORCE to confirm complete clearance of history. So the parameter is only valid with history of 0, and override of FORCE. such as modify appl testam3 0 force. The request fails.
System Action:
498
Correct parameter file and resubmit. Problem rc keeping list of used keys like key A problem occurred in maintaining a list of values. Possible causes are - memory issues. The request fails. Correct and resubmit. Trace task ending. TRACING statement is missing from the configuration file. The DBMOVER configuration file does not contain a TRACING statement. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. To use the alternative PowerExchange log, specify the TRACING parameter in the DBMOVER configuration file. For more information about the TRACING parameter, see the PowerExchange Reference Manual. Trace task ending. Internal error: No trace communication area is available. The alternative logging task could not find its internal communications control block. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. To use alternative logging, view the PowerExchange log file for additional messages. To correct the problem, follow the user responses for these messages. Trace task ending. Internal error: Trace task is not supported for this platform. Alternative logging is not supported on your platform. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. No response is required. Shared memory flush error: system_error_message The alternative logging task encountered an error when attempting to write data to shared memory. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. View the following PowerExchange log file for additional messages:

The alternative log files for the process The PowerExchange log file
To correct the problem, follow the user response instructions for any messages you find in these logs. If PowerExchange does not issue related error messages, see your operating system documentation for information about the error referenced in this message. Then take the corrective action that is specified. MVS users might need to review the JES log for the job to find the associated system messages.
PWX-14000 to PWX-14999
499
Error writing to trace file <file_name>. Error code = <system_error_number>: <system_error_message> The alternative logging task encountered an error when attempting to write to the specified trace file. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. View the following PowerExchange log file for additional messages:

To correct the problem, follow the user response instructions for any messages you find in these logs. If PowerExchange does not issue related error messages, see your operating system documentation for information about the error referenced in this message. Then take the corrective action that is specified. On MVS, you might need to review the JES log for the job to find the associated system messages. PWX-14517 Explanation: Configuration file parameters LOGPATH and TRACING/PFX will cause tracing file names nnn bytes too long. PowerExchange creates the alternative log files names by using the LOGPATH parameter, and the PFX parameter of the TRACING statement, in the DBMOVER configuration file. PowerExchange has detected that these values result in a file name that is too long for the operating system on which it is running. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. Change the value of the LOGPATH parameter, and the PFX parameter of the TRACING statement, so that the generated file names meet the requirements of your operating system. Unable to allocate memory for log files. PowerExchange cannot obtain sufficient memory to create the log file for alternative logging. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. Increase the amount of memory available for the PowerExchange task. Error determining file information for log file <file_name>. Error = <system_error_number>: <system_error_message> The alternative logging task encountered an error when attempting to determine the end of the latest log file. In the message text:
file_name is the name of log file for which the error occurred. system_error_number is the number of the error message. system_error_message is the text of the error message. System Action: Alternative logging ignores APPEND processing and uses the next log file to begin logging data.
500
User Response:
View the following PowerExchange log file for additional messages:
The alternative log files for the process The PowerExchange log file To correct the problem, follow the user response instructions for any messages you find in these logs. If PowerExchange does not issue related error messages, see your operating system documentation for information about the error referenced in this message. Then take the corrective action that is specified. On MVS, you might need to review the JES log for the job to find the associated system messages. PWX-14520 Explanation: System Action: User Response: Cannot append to log file file_name due to previous error. The alternative logging task encountered an error when attempting to determine the end of the specified log file. Alternative logging ignores APPEND processing and uses the next log file to begin logging data. View the following PowerExchange log file for additional messages:

To correct the problem, follow the user response instructions for any messages you find in these logs. If PowerExchange does not issue related error messages, see your operating system documentation for information about the error referenced in this message. Then take the corrective action that is specified. On MVS, you might need to review the JES log for the job to find the associated system messages. PWX-14521 Explanation: File lrecl nnn not compatible with requested max trace record size nnn. The logical record length of the alternative log file that was used by a prior invocation of this process is not compatible with the RECLEN parameter specified on the TRACING statement in the DBMOVER configuration file. Alternative logging ignores APPEND processing and uses the next log file to begin logging data. The problem corrects as the alternative logging task cycles through the log files for the process. Error opening trace file file_name. Open options: option_string. Error code = system_error_number: system_error_message The alternative logging task encountered an error when attempting to open the specified alternative log file. In the message text:

file_name is the name of the log file for which the error was reported. option_string specifies the open options for the file. system_error_number is the number of the error message. system_error_message is the text of the error message. System Action: PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log.
PWX-14000 to PWX-14999
501
User Response:
View the following PowerExchange log file for additional messages:
The alternative log files for the process The PowerExchange log file To correct the problem, follow the user response instructions for any messages you find in these logs. If PowerExchange does not issue related error messages, see your operating system documentation for information about the error referenced in this message. Then take the corrective action that is specified. On MVS, you might need to review the JES log for the job to find the associated system messages. PWX-14524 Explanation: Tracing failure: Trace data set/GDG file_name is in use by another job. The specified alternative logging log data set or GDG data set is being used by another job. This error can occur for the following reasons:

More than one instance of PowerExchange is installed on the system. Multiple PowerExchange installations on different systems use shared DASD.
PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. Change the value of the LOGPATH parameter, and the PFX parameter in the TRACING statement, to generate log file names that are unique across your PowerExchange installations. GDG referenced by DDNAME ddname will be used for tracing. All other DTLLOGnn files will be ignored. PowerExchange uses the specified GDG to create data sets for alternative logging. If other DTLLOGnn DD statements are specified in the JCL, PowerExchange ignores those data sets. No response is required. Legacy tracing is in effect. The DBMOVER configuration file does not contain a TRACING statement so alternative logging is not in effect. PowerExchange writes messages to the standard PowerExchange log file. For information about specifying the TRACING statement in the DBMOVER configuration file, see the PowerExchange Reference Manual. Error starting tracing subtask: system_error_message. Legacy tracing is in effect. PowerExchange could not start the alternative logging task. PowerExchange writes all messages to the default PowerExchange log file and does not use the alternative log. View the following PowerExchange log file for additional messages:

To correct the problem, follow the user response instructions for any messages you find in these logs. If PowerExchange does not issue related error messages, see your operating system documentation for information about the error referenced in this message. Then take the corrective action that is specified.
On MVS, you might need to review the JES log for the job to find the associated system messages. PWX-14600 Explanation: System Action: User Response: Internal error: No name passed to serialization handle creation function. A PowerExchange function incorrectly formatted a call to an internal serialization control function. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, report the failure, along with this error message, to Informatica Global Customer Support. There is no user action that can correct this problem. Internal error: Invalid name <handle_name> passed to serialization handle creation function. A PowerExchange function incorrectly formatted a call to an internal serialization control function. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, report the failure, along with this error message, to Informatica Global Customer Support. There is no user action that can correct this problem. Semaphore creation error: <system_message> The system could not create a serialization control block. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, view the PowerExchange log file for associated messages. To correct the problem, follow the user response instructions for these messages. If there are no other error messages, see your operating system documentation for the explanation of the error information included in this message. Then, take any specified corrective action. Semaphore control error: <system_message> The system could not complete a resource serialization request.The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, view the PowerExchange log file for associated messages. To correct the problem, follow the user response instructions for these messages. If there are no other error messages, see your operating system documentation for the explanation of the error information included in this message. Then, take any specified corrective action. Internal error: Serialization/mutex handles are not supported on this platform. A PowerExchange function incorrectly requested a serialization function on a software and hardware platform that does not support the type of serialization requested. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, report the failure, along with this error message, to Informatica Global Customer Support. There is no user action that can correct this problem. Unable to access semaphore <semaphore_name>: <system_message> The PowerExchange function could not access a shared resource serialization control block. The required serialization does not take place. Subsequent processing might fail.
PWX-14000 to PWX-14999
503
User Response:
If subsequent processing fails, view the PowerExchange log file for associated messages. To correct the problem, follow the user response instructions for these messages. If there are no other error messages, see your operating system documentation for the explanation of the error information included in this message. Then, take any specified corrective action. Internal error: Invalid Serialization/mutex handle passed to function <function_name>. A PowerExchange function passed an invalid serialization control block to the PowerExchange serialization handler. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, report the failure, along with this error message, to Informatica Global Customer Support. There is no user action that can correct this problem. Unable to obtain semaphore <semaphore_name>: <system_message> The PowerExchange function could not acquire the requested serialization lock. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, view the PowerExchange log file for associated messages. To correct the problem, follow the user response instructions for these messages. If there are no other error messages, see your operating system documentation for the explanation of the error information included in this message. Then, take any specified corrective action. Unknown return code <nnn> attempting to obtain semaphore <semaphore_name>. The system returned an unknown error code to a serialization request. The required serialization does not take place. Subsequent processing might fail. If subsequent processing fails, report the failure, along with this error message, to Informatica Global Customer Support. There is no user action that can correct this problem. Unable to release semaphore <semaphore_name>: <system_message> The PowerExchange function could not release the requested serialization lock. The required serialization fails. Subsequent processing might fail. If subsequent processing fails, view the PowerExchange log file for associated messages. To correct the problem, follow the user response instructions for these messages. If there are no other error messages, see your operating system documentation for the explanation of the error information included in this message. Then, take any specified corrective action.
Note: If the system message is 'Task does not own this semaphore.', then PowerExchange
User Response:
attempted to release an IBM z/OS enqueue object that it does not own. If you receive this message as part of the PWX-14610 error message, report the failure to Informatica Global Customer Support. PWX-14612 Explanation: Explanation: User Response: Unable to destroy semaphore <semaphore_name>: <system_message> The PowerExchange function could not deallocate the requested serialization lock. Subsequent processing might fail. If subsequent processing fails, view the PowerExchange log file for associated messages. To correct the problem, follow the user response instructions for these messages. If there are no other error messages, see your operating system documentation for the explanation of the error information included in this message. Then, take any specified corrective action.
504
PWX-15000 to PWX-15999
PWX-15700 Explanation: System Action: User Response: PWX-15701 Explanation: System Action: User Response: PWX-15702 Explanation: System Action: User Response: SQL-DMO interface returned error error code with text: error_text. An error was received from the SQL Server SQL-DMO interface. Capture registration fails. Review the Microsoft SQL Server documentation for appropriate response. Table 'OWNER.name' is not a valid candidate for capture The selected table was a system table or did not have a primary key. The table is rejected as a choice for capture. Select a valid candidate table. COM function call function failed with rc return_code. A component object model call failed. Capture registration fails. This error might indicate that the SQL Server Client software is not installed correctly. Verify the installation. Contact Informatica Global Customer Support if the error persists. Insufficient memory resources to perform capture registration. Insufficient memory resources to perform capture registration. Capture registration fails. Investigate any resource constraints. Server server_name is not configured for publication. No distribution database was identified for the server. Capture registration fails. See the MS SQL capture documentation on prerequisites for capture Internal Error: Server instance not set. An internal logic error occurred. Capture registration fails. Contact Informatica Global Customer Support with details of the error. Internal Error: Database not set. An internal logic error occurred. Capture registration fails. Contact Informatica Global Customer Support with details of the error. Publication article for database database_name table OWNER.name is corrupt. The article for this table in the PowerExchange Change Capture publication for this database does not match the expected profile. It might not be a PowerExchange generated article, or it might have been updated outside of the GUI. Capture registration fails. The article must be deleted using the SQL Server management console before proceeding.
PWX-15000 to PWX-15999
505
Internal Error: Article must be validated before it is saved. An internal logic error occurred. Capture registration fails. Contact Informatica Global Customer Support with details of the error. Publication article for database database_name table OWNER.name failed validation. Reason: reason_text. The article failed validation for the reason described and was not created. Capture registration fails. Correct the registration and retry the status update. Registration group in error. Delete the registration group and recreate. The generated instance name for the registration group does not uniquely identify a instance/database combination at a location. Can happen if the first capture registrations is added to a group some time after it was created, or location is changed. Capture registration fails. Delete the registration and recreate. COM function call CoInitializeEx failed with rc RPC_E_CHANGED_MODE. The call to routine CoInitializeEx failed to initialize the COM library to the COINIT_MULTITHREADED concurrency mode. This indicates contention with another module that has initialized the COM library to a different concurrency mode. Capture registration fails. Note the sequence of events leading up to the problem and contact Informatica Global Customer Support. Internal Error: Unable to acquire number bytes of storage. MSSQL Capture extract was unable to allocate sufficient storage. MSSQL Capture extract fails. Investigate any resource constraints. CAPI Connect information invalid or missing. The information supplied in the configuration file for this connection is missing or invalid. MSSQL Capture extract fails. See the MSSQL capture documentation for instructions on setting up the CAPI_CONNECTION in the configuration file. COM function call function failed with rc return_code. A component object model call failed. MSSQL Capture extract fails. This error might indicate that the SQL Server Client software is not installed correctly. Verify the installation. Contact Informatica Global Customer Support if the error persists.
506
OLE-DB error: error_text Message contains details of errors generated by the OLE DB interface. Multiple messages are possible. MSSQL Capture extract fails. The ERROR TEXT displays the nature of the problem. Contact Informatica Global Customer Support if the error persists. Internal error: Table column count column_count exceeds maximum max_column_count allowed A select was attempted on a table with more than the maximum number of columns allowed. MSSQL Capture extract fails. Contact Informatica Global Customer Support with details of the error. Internal error: Bind error bind_status received for columncolumn_num when retrieving article data. An unexpected error was received retrieving the capture article information. MSSQL Capture extract fails. Contact Informatica Global Customer Support with details of the error. Internal error: Bad status column_status received for column column_num when retrieving article data. An unexpected error was received retrieving the capture article information. MSSQL Capture extract fails. Contact Informatica Global Customer Support with details of the error. Server server_name, Database database_name contains no article publications. The database specified in the connect parameters is not a distribution database or no articles are published to it. MSSQL Capture extract fails. Verify the values specified for DISTSRV and DISTDB in the connect parameters. The table identified by tag PowerExchange_tag is not published to server server_name, Database database_name. The database specified in the connect parameters is not the distribution database for the requested table publication. MSSQL Capture extract fails. Verify the values specified for DISTSRV and DISTDB in the connect parameters. Repository node rep_node does not contain any capture registrations for MSSQLServer. Either the repository specified in the connect parameters does could not be connected to, or does not contain any capture registrations for MS SQL Server. MSSQL Capture extract fails. Verify the value specified for REPNODE in the connect parameters.
PWX-15000 to PWX-15999
507
Load of work session for Repository node rep_node failed. The attempt to load a work session with the repository specified in the connect parameters failed. MSSQL Capture extract fails. Verify the value specified for REPNODE in the connect parameters and that a PowerExchange Listener exists on that node. Load of capture registration from Repository node rep_node failed. The attempt to load a capture registration from the repository specified in the connect parameters failed. MSSQL Capture extract fails. Review the PowerExchange.LOG of the PowerExchange Listener at REP NODE as well as for this task for possible causes. Contact Informatica Global Customer Support if the problem cannot be resolved. Multiple active capture registration exist for tag PowerExchange_tag. Multiple active capture registrations were found for this tag. This indicates a problem in the repository. MSSQL Capture extract fails. Use the GUI interface to attempt to deactivate the anomalous registrations. Report the problem to Informatica Global Customer Support. Table name mismatch between published article and PowerExchange registration for tag PowerExchange_tag. The registration in the repository does not match with the published article. Message PWX-15799 provides more information. MSSQL Capture extract fails. Confirm that the repository identifier (REPNODE) is correct for this registration. No active PowerExchange registration found for registration tag PowerExchange_tag. No active registration was found in the repository specified for this tag. MSSQL Capture extract fails. Confirm that the repository identifier (REPNODE) is correct for this registration and that the registration is active. Internal Error: Invalid number of parms supplied to SQL call: Expected count, received count. This is an internal logic error. MSSQL Capture extract fails. Report the error to Informatica Global Customer Support. Unable to resolve DBID for database database_name. Access to table master.dbo.sysdatabases failed. MSSQL Capture extract fails. This might indicate authorization problems. Look for associated SQL-DMO messages.
508
Unable to determine current log position. Access to table dbo.MSrepl_transactions failed. MSSQL Capture extract fails. This might indicate authorization problems. Look for associated SQL-DMO messages. Internal Error: Bind for parameter column column_number returned status bind_status. Attempt to bind column data failed. MSSQL Capture extract fails. Report the error to Informatica Global Customer Support. Restart information invalid : reason_code. A restart token supplied to the interface is invalid. Restart tokens for this interface must be created by this interface and must contain the correct distribution server and database identifiers. MSSQL Capture extract fails. If the correct restart information cannot be determined rematerialization of the target must be performed. Sequence information invalid : reason_code. A restart token supplied to the interface is invalid. Restart tokens for this interface must be created by this interface and must contain the correct distribution server and database identifiers. MSSQL Capture extract fails. If the correct restart token cannot be determined rematerialization of the target must be performed. Schema change detected for table OWNER.NAME. The capture extract detected a schema change for the indicated table. The change should be described in associated 1579 messages. Dependent on the value of the data warning flags in the connect parameter. If Warn on Schema Change is not in effect then MSSQL Capture extract fails, otherwise a warning is issued and processing continues. The capture registration and target should be updated to reflect the schema change before the capture extract is restarted. Invalid Capture data for table OWNER.NAME. Update type not recognized. The capture extract detected an unrecognized update type. MSSQL Capture extract fails. The mssql publication definition might have been corrupted. The table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. Invalid Capture data for table OWNER.NAME, columncolumn_num. expected PowerExchange TYPE PowerExchange_TYPE, found TYPE. The capture extract detected unexpected data. MSSQL Capture extract fails. The mssql publication definition might have been corrupted. The table must be reregistered through the PowerExchange GUI. Target rematerialization might be required.
PWX-15000 to PWX-15999 509
User Response:
Invalid Capture data for table OWNER.NAME, columncolumn_num. expected length LENGTH, found LENGTH. The capture extract detected unexpected data. MSSQL Capture extract fails. The mssql publication definition might have been corrupted. The table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. Numeric conversion for table OWNER.NAME, column column_num failed with rc return_code. Conversion from character to numeric failed. This message is followed by a display of the character data. MSSQL Capture extract fails. Confirm that the data is correct for the indicated column. The mssql publication definition might have been corrupted. If this is the case, the table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. If the data is correct report the error to Informatica Global Customer Support. Timestamp conversion for table OWNER.NAME, column column_num failed with rc return_code. Conversion from character to Timestamp failed. This message is followed by a display of the character data. MSSQL Capture extract fails. Confirm that the data is correct for the indicated column. The mssql publication definition might have been corrupted. have been corrupted. If this is the case, the table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. If the data is correct report the error to Informatica Global Customer Support. Internal error: Unexpected datatype PowerExchange_DATATYPE for column column_name of table OWNER.NAME. The capture registration for this table contains a column type not handled by the extract program. MSSQL Capture extract fails. report this error to Informatica Global Customer Support. Invalid Capture data for table OWNER.NAME, column column_name. Found NULL data expected non-NULL. The capture extract detected NULL data for a column registered not-nullable. MSSQL Capture extract fails. The mssql publication definition might have been corrupted. The table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. Internal error: Unexpected data encountered processing data for table OWNER.NAME at data posn POSITION. Unexpected or invalid data was encountered processing the capture data string. Associated 15799 messages dump the current data string. MSSQL Capture extract fails. report this error to Informatica Global Customer Support.
510
Capture data for table OWNER.NAME invalid. Number of columns found COLUMN_COUNT did not match expected number COLUMN_COUNT. The capture extract did not find the expected number of columns for this table. MSSQL Capture extract fails. The mssql publication definition might have been corrupted. The table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. Capture data truncated for table OWNER.NAME, column column_num. Maximum expected LENGTH , found LENGTH . The capture data for the indicated column exceeded the PowerExchange processing limit. The system action is dependent on value of the data warning flags in the connect parameter. If Warn on Data Truncation is not in effect then MSSQL Capture extract fails, otherwise a warning is issued, the data is truncated and processing continues. The data length for this column is greater than can be efficiently processed. Consider Turning off capture for the column. Internal error: Capture data image len " LENGTH " for table OWNER.NAME exceeds expected size " LIMIT ". Capture data image length for the current table exceeds the expected size. MSSQL Capture extract fails. Report this problem to Informatica Global Customer Support. Max buffer length BUFFER_LENGTH for input data exceeded for table OWNER.NAME. The maximum buffer length for input data was exceeded. Probably caused by an attempt to process a long column. MSSQL Capture extract fails. The data length for a column is greater than can be efficiently processed. Consider Turning off capture for the column. Alternatively use the MEMCACHE connect parameter to override the default allocation. Invalid capture data for an update for table OWNER.NAME. Before or After Image missing. Either the before image or after image for an update is missing. MSSQL Capture extract fails. The mssql publication definition might have been corrupted. The table must be reregistered through the PowerExchange GUI. Target rematerialization might be required. Change data lost for requested sources. The earliest sequence for the requested sources was not found in the replicated data table. This depends on values of DWFLAGS in the CAPI_CONNECTION parameter in the DBMOVER configuration file. See the PowerExchange Reference manual for details of DWFLAGS and its default values. Specifically, if the WARN ON CHANGE DATA LOST positional flag is not set to Y then MSSQL Capture extract fails, otherwise a warning is issued and processing continues. The transaction retention period for the distribution DB might be insufficient. See the PowerExchange Reference manual for details on the CAPI_CONNECTION for MSSQL.
User Response:
User Response:
PWX-15000 to PWX-15999
511
Reg. Group: Load Error. Field = MSS_DistServer PowerExchange could not load the specified Capture Registration Group. The field 'MSS_DistServer' (sic) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = MSS_DistDatabase PowerExchange could not load the specified Capture Registration Group. The field 'MSS_DistServer' (sic) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = MSS_DatabaseServer PowerExchange could not load the specified Capture Registration Group. The field 'MSS_DistServer' (sic) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. Reg. Group: Load Error. Field = MSS_Database PowerExchange could not load the specified Capture Registration Group. The field 'MSS_DistServer' (sic) could not be read. See the associated messages for further diagnostics. Registration Group Load process is abandoned. Contact Informatica Global Customer Support for support on which traces are required, or give Informatica Global Customer Support a copy of the failing registration group file, along with information on the software level being used. MESSAGE_TEXT . Message providing additional text for previous messages. See previous messages. Error " rc " returned from RtvJrnEntry API. Code " error_code " Info = error_information. Message providing diagnosis of possible error reading journal. Processing fails unless the error is harmless. Contact Informatica Global Customer Support if the process failed. unless the situation is as a result of user or system intervention.
512
Information Journal Block end and receiver change at seq sequence. A message to show the occurrence of this event. Processing continues. Contact informatica Global Customer Support with other information in event of a failure. Warning. Over 100 receivers " receiver_count " returned. Trying for memory allocation "allocation_bytes ". Message providing diagnosis of possible error reading journal. Processing fails unless the error is harmless. Contact informatica Global Customer Support if process failed. unless the situation is as a result of user or system intervention. Error " ErrorCode " returned from RtvJrnInfo API. Info = error_information. Message providing diagnosis of error retrieving journal information. The task fails. Contact informatica Global Customer Support, unless the situation is a result of user or system intervention. Error " ErrorCode " returned from RtvJrnRcvrInfo API. Info = error_information. Message providing diagnosis of error retrieving journal receiver information. The task fails. Contact informatica Global Customer Support, unless the situation is a result of user or system intervention. Journal receiver " Journal_Receiver " defined with MINENTDTA option other than *NONE. An attempt was made to process journal entries for a journal receiver defined with MINENTDTA option other than *NONE. IBM does not currently allow these entries to be processed by PowerExchange. If the journal receiver was defined for MINENTDTA(*FILE) the changed data is stored using an IBM hash algorithm. This data cannot be extracted by Non-IBM software. If the journal receiver was defined for MINENTDTA(*FLDBDY) only those fields that have had their values changed on an update are returned. All other fields have a default value returned based upon the field type. The task fails. Change the journal so that this option is correctly specified for the next receiver generated and restart the task from the new journal receiver. Unable to process journal receiver receiver_library/receiver_name associated with journal journal_library/journal_name. Journal receiver storage freed during save. During the last save of the journal receiver the option to free the storage occupied by the journal receiver was specified. This removes the journal entries from the receiver that PowerExchange is expecting to process. The task fails. Either restore the journal receiver from the backup taken to restore the journal entries or restart the process after the receiver with freed storage by generating new restart tokens.
PWX-15000 to PWX-15999
513
Unable to process journal receiver receiver_library/receiver_name associated with journal journal_library/journal_name. Journal receiver has partial status. The journal receiver does not contain all the journal entries expected. This might lead to incomplete data changes being processed by the PowerExchange Change Data Capture software. The task fails. Attempt to restore the journal receiver so that the status is no longer partial. If this is not possible the option ALWPARTIAL=Y might be specified on the CAPI_CONNECTION parameter to permit processing. After the receiver in error was processed, it is recommended that this setting be changed to N or removed.
PWX-16000 to PWX-16999
PWX-16100 Explanation: System Action: User Response: PWX-16101 Explanation: System Action: User Response: PWX-16102 Explanation: System Action: User Response: PWX-16103 Explanation: System Action: User Response: PWX-16104 Explanation: System Action: User Response: PWX-16105 Explanation: System Action: User Response: DTLURDMO input error (Stmt stmt_no): Invalid option option used with access method access_method The specified option is invalid for the specified access method. Processing proceeds, but as validate-only. Specify the command without the invalid options. Parameter parameter is required, but has not been supplied The requested process requires the specified parameter. Processing proceeds, but as validate-only. Specify the command with the required parameter. Only one of DM_COPY, XM_COPY or REG_COPY can be used at a time This message is informational. Processing ends. Specify the input with one type of command only. Only one of PWD= or EPWD= can be used at a time This message is informational. Processing ends. Specify the input with one type of command only. Table table_name not found in map The specified table was not found in the data map. The request to rename the table is ignored. Specify the input with the correct table_name. Datamap not written, rc = return_code The data map was not written. Processing continues. No response is required.
514
Incompatible access methods, input = input_access_method, map = output_access_method The specified input access method does not match the access method specified in the data map. Processing continues. Correct the error and run the request again. Datamap schema.map_name not found The requested data map was not found. Processing continues. No response is required. DTLURDMO input error (Stmt stmt_no): CONDENSE=option is not valid. The specified condense option is not recognized. Validation processing continues. Correct the error and run the request again. DTLURDMR Report: report_line Generic report line, details explained in text Processing continues. Read and act on information where necessary DTLURDMR input error (Stmt stmt_no): MODIFY TABLE= not supported in REG_COPY. Use the MODIFY REGTABLE statement instead This message displays a generic report line. Validation processing continues. Correct the error and run the request again. DTLURDMO input error: run terminated due to input errors See the associated messages. Processing ends. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): parameter already specified A parameter was supplied twice. Validation processing continues. Identify the source of the duplication, Correct the error and run the request again. DTLURDMO input error: (Stmt stmt_no): A process statement should be coded before statement A SELECT, EXCLUDE, RENAME or MODIFY statement was specified without a previous DM_COPY, XM_COPY or REG_COPY process statement. Validation processing continues. Specify one of the processing statements before the SELECT, EXCLUDE, RENAME or MODIFY statement.
PWX-16000 to PWX-16999
515
DTLURDMO input error (Stmt stmt_no): DBTYPE not allowed for DM_COPY. Use am= to filter datamaps The type is not a valid filter for this operation. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): No valid parameters found for statement. Valid keywords are parameter and parameter Missing parameter text, valid parameters are suggested. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): No valid parameters found for statement. Valid keywords is parameter Missing parameter text, the valid parameter is given. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): Invalid DBTYPE specified. type The database type used is invalid. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): statement requires parameter and parameter Missing parameter text, valid parameters are given. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): access_method not valid for statement The access method used is invalid. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): DBID=value needs to match suffix generated for (dbserver."dbname") The parameter can cause issues for the access method used. The parameter must obey naming conventions and have a good match to the target. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): KEEPREGTAG=value not needed for MSS The parameter can cause issues for the access method used. As the tag is regenerated, it is maintained if appropriate. Validation processing continues. Correct the error and run the request again.
516
DTLURDMO input error (Stmt stmt_no): DBID=value mismatch instance for (dbserver.dbname) against (edbserver.edbname) The parameter can cause issues for the access method used. The parameter must obey naming conventions and have a good match to the target. The parameters dbname and dbserver do not match the existing dbname and dbserver for the instance. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): Renaming Maps and changing map attributes are mutually exclusive A MODIFY statement included rename parameters (SCHEMA=, MAP=) and the alteration of map attributes parameter (AM=xxx). These parameters are mutually exclusive:
Renaming is performed on all maps selected by the active filters Alteration of map attributes are applicable for the specified access method only System Action: User Response: PWX-16124 Explanation: Validation processing continues. Specify separate MODIFY statements for these parameters. DTLURDMO input error (Stmt stmt_no): Access method not supplied for statement altering map properties A MODIFY statement included the alternation of map attributes parameter (AM=xxx) but the statement did not include an access method parameter. The map attributes that can be changed on copying depend on the access method so AM= is a required parameter. Only MODIFY statements that rename map components do not require the AM= parameter. Validation processing continues. Correct the error and run the request again. DTLURDMO input error (Stmt stmt_no): The statement statement is only valid with statement The specified statement is not compatible with the selected operation. For example, KEEPREGTAG is not compatible with DM_COPY. Validation processing continues. Correct the error and run the request again. PARM OLDNAME changed to NEWNAME The map parameter identified was successfully changed. Processing continues. No response is required. Datamap SCHEMA.MAP written successfully The data map was successfully written. Processing continues. No response is required. Processing datamap MAPNAME This message is informational. Processing continues.
System Action: User Response: PWX-16125 Explanation: System Action: User Response: PWX-16200 Explanation: System Action: User Response: PWX-16201 Explanation: System Action: User Response: PWX-16202 Explanation: System Action:
PWX-16000 to PWX-16999
517
No response is required. Windows_Message This message is informational. Processing depends on message. No response is required. Unable to create file : file_name The specified file could not be created. Processing ends. Verify the file name and environment. Error: End of rsttkn resource_name before run of Application application. An application without a run history and no pending tokens cannot have a resource to remove with END RSTTKN - error. The system ends the request. Verify that there is no error in the request. DTLUCDEP might help by printing applications, DTLUAPPL can print a limited report PRINT APPL ALL. The PowerExchange Navigator can also display Data Capture Application Groups. Resubmit the correct request. Unknown database type database_type. Unable to carry out ODL request as the database type is unsupported. The system ends the request. Only use Access Method ODL for supported database types. Database error: database_error. A database error was returned. The system ends the request. Correct the error and try again. Unknown statement type: statement_type. An unknown statement type was submitted. The system ends the request. Correct the error and try again. Unknown Access Method Type: access_method_type. An unknown access method type was submitted. The system ends the request. Contact Informatica Global Customer Support. Column: column_name in Table: table_name contains an unsupported data type: column_type. The table contains an unsupported data type that is not handled by PowerExchange. The system ends the request.
PWX-16400 Explanation: System Action: User Response: PWX-16401 Explanation: System Action: User Response: PWX-16402 Explanation: System Action: User Response: PWX-16404 Explanation: System Action: User Response: PWX-16405 Explanation: System Action:
518
Ensure that tables use supported data types. Unknown Meta Data Type: type. An unknown access method type was submitted. The system ends the request. Contact Informatica Global Customer Support. Set Global Locale failed with code page name 'name'. The code page name is not recognized by the PMI18N module. The system ends the request. An incorrect value was specified in the 3rd parameter of the dbmover.cfg ORACLECODEPAGE statement. Oracle environment variable NLS_LANG not defined. The environment variable NLS_LANG was not defined. The third component of this variable defines the character set that Oracle uses to exchange data with calling applications. Processing continues. but the system might not be able to use the correct code page for character data. Specify this environment variable according to Oracle instructions. No dot in Oracle environment variable NLS_LANG value. The dot is missing from the NLS_LANG environment variable value. The expected format is Language_Territory.character set and the system uses the dot to determine where the character set starts. Processing continues. but the system might not be able to use the correct code page for character data. Specify this environment variable according to Oracle instructions. Oracle environment variable NLS_LANG value was not recognized. The system could not automatically identify a PMI18N locale code page to match the Oracle character set in NLS_LANG. Processing continues. using the code pages specified in ORACLECODEPAGE for this TNSNAME. If none were specified, then it uses the system defaults but might not be able to handle SQL correctly. Specify the ORACLECODEPAGE statement in the configuration file so that the correct code page is used. Oracle environment variable NLS_LANG value yielded code pages PowerExchange_code_page (internal_number) and PWC_code_page. The system automatically identified the specified code pages from the Oracle character set in NLS_LANG. Processing continues. using the specified code pages. This message is output in conjunction with other error messages. Respond to the error messages.
System Action: User Response: PWX-16410 Explanation: System Action:
User Response:
PWX-16000 to PWX-16999
519
Used ORACLECODEPAGE statement to determine code pages. The system used the ORACLECODEPAGE statement in the configuration file to determine the code pages. Processing continues. using the specified code pages. This message is output in conjunction with other error messages. Respond to the error messages. Describe failed for column column_name in table table_name. The column does not exist in the specified table. The system ends the request. Change the query to match the table metadata. Unable to determine PWX codepage number using alias PowerExchange_code_page_alias formed from environment variable DB2CODEPAGE The DB2CODEPAGE environment variable value is used to create a PowerExchange code page alias and the alias is not found. The system ends the request. Contact Informatica Global Customer Support. Following error occurred during truncate processing: error_message. Error occurred while attempting to truncate string value. The system ends the request. Contact Informatica Global Customer Support. Error parsing parameter columns: expected: expected, found: found. While parsing SQL the number of columns expected is different to expected number. The system ends the request. Contact Informatica Global Customer Support. ICU data directory changed to current_ICU_data_directory for ODL. Previously it was former_ICU_data_directory. After initializing the PMI18N environment, the ICU data directory has changed from the previous value that might have been set by the configuration ICUDATADIR parameter. Processing continues. but might fail later if a CNV file for a custom ICU code page is not found in the specified directory. It is best to change the ICUDATADIR to be the same as the change to value. Error calling routine routine_name. Return code return_code. An error was returned from the specified routine. Processing ends. Contact Informatica Global Customer Support. Unknown Meta Data Type: type. An unknown Meta Data type was submitted. The system ends the request.
520
Contact Informatica Global Customer Support. Internal Error: Buffer memory limit exceeded. The buffer memory size is insufficient to store required meta data. The system ends the request. Contact Informatica Global Customer Support. Unknown request type request_type. Unable to handle unknown request type. The system ends the request. Contact Informatica Global Customer Support. Error code code returned from database access module. The access module returned an error. The system ends the request. Contact Informatica Global Customer Support. Access method will handle read requests only. Access method will handle read requests only. The system ends the request. Contact Informatica Global Customer Support. Access method will handle meta data requests only. Access method will handle meta data requests only. The system ends the request. Contact Informatica Global Customer Support. Unhandled Meta Data request: request_type. Unhandled Meta Data request. The system ends the request. Contact Informatica Global Customer Support. Invalid use of null pointer Invalid use of null pointer. Setting of the string failed. Pass a valid pointer. Missing partner access method. Please specify. No partner access method was specified. The system ends the request. Contact Informatica Global Customer Support.
PWX-16000 to PWX-16999
521
Catalog Name parameter is missing from LOGSID entry LOGSID_statement The catalog name data set was not included on the specified LOGSID entry in the DBMOVER configuration file. Processing ends. Edit the DBMOVER configuration file, and include the catalog name data set in the LOGSID statement specified in the error message. Instance Name parameter is missing from LOGSID entry LOGSID_statement The Instance name parameter was not included on the specified LOGSID entry in the DBMOVER configuration file. Processing ends. Edit the DBMOVER configuration file, and include the instance name parameter in the LOGSID statement specified in the error message. IDMSX CAPI: Sequence info block offset: offset The current IDMSX log record's offset into the log file block in which it resides is published. The task continues. No response is required. This message might be issued in response to an earlier error to help identify the log record that was being processed when the error occurred. IDMSX CAPI: Sequence info block number: log_file_block_number The log file block number in which the current IDMSX log record resides is published. The task continues. No response is required. This message might be issued in response to an earlier error to help identify the log record that was being processed when the error occurred. IDMSX CAPI: Sequence info file number: log_file_number The log file number in which the current IDMSX log record resides is published. The task continues. No response is required. This message might be issued in response to an earlier error to help identify the log record that was being processed when the error occurred. IDMSX CAPI: Sequence info version number: version_number The log record sequence info version number of the current IDMSX log record is published. The task continues. No response is required. This message might be issued in response to an earlier error to help identify the log record that was being processed when the error occurred. IDMSX CAPI: IDMSX instance name: hexadecimal_dump_of_instance_name : instance_name The instance name that generated the current IDMSX log record is published. The task continues. No response is required. This message might be issued in response to an earlier error to help identify the log record that was being processed when the error occurred.
522
IDMSX CAPI: IDMSX restart info contains early value The restart information for this task points to the earliest existing point in the IDMSX log. The task continues. No response is required. This message might be issued in response to an earlier error to help identify the log record that was being processed when the error occurred. IDMSX CAPI: no_filter_tag and other tags cannot be mixed The IDMSX CAPI module encountered the special registration tag indicating no filtering in combination with other registration tags. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Registration tag named registration_tag is longer than maximum tag name length of maximum_tag_name_length_value. The IDMSX CAPI module encountered an invalid registration tag. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Error code return_code connecting to IDMSX log reader in module module_name. The IDMSX CAPI module could not connect to the IDMSX log reader. The system returns an error to the calling software. Scan the output log for errors immediately prior or subsequent to this message to help pinpoint the source of the error. IDMSX CAPI: Seek to end of log returned NULL value. The IDMSX CAPI module could not find the current end of the IDMSX log. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: IDMSX log API call call_type returned rc=return_code, reason=reason_code2/ reason_code2/reason_code3 The IDMSX CAPI module encountered an error while reading the IDMSX log. In the message text
call_type is the type of call that encountered the error. return_code1, return_code2, and return_code3 are the PowerExchange return codes for the failure. System Action: User Response: PWX-16575 Explanation: System Action: User Response: The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: IDMSX log API returned invalid record type hexadecimal_record_type_value The IDMSX CAPI module received an invalid record type from the IDMSX log read routine. The system returns an error to the calling software. Contact Informatica Global Customer Support.
PWX-16000 to PWX-16999
523
PWX-16576 Explanation: System Action: User Response: PWX-16577 Explanation: System Action: User Response: PWX-16578 Explanation: User Response:
IDMSX CAPI: IDMSX log API returned invalid action code hexadecimal_action_type_value for record type record_type description The IDMSX CAPI module received an invalid subtype code for the given record type from the IDMSX log read routine. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: IDMSX log API returned invalid tag name index index_value The IDMSX CAPI module received a tag name index value that was out of bounds. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Current log record sequence info: hex_sequence_info This message reports the hexadecimal sequence information of the current IDMSX log record. No response is required.This message might be reported in response to another error. If so, use the information in this message with error messages that might be immediately prior or subsequent to this message to help pinpoint the source of the error. IDMSX CAPI: Error reported in IDMSX Capture module module_name: RC = return_code The specified Capture module encountered an error. The system returns an error to the calling software. Scan the output log for error messages that are immediately prior or subsequent to this message to help pinpoint the source of the error. IDMSX CAPI: Error reported in Repository function function_name: location = node_name The specified Repository module encountered an error. The system returns an error to the calling software. If the location name is local, scan the output log for error messages that are immediately prior or subsequent to this message to help pinpoint the source of the error. If the location name is other than local, scan the output log of the PowerExchange Listener running at the specified location for error messages. IDMSX CAPI: Restart info length length_in_bytes does not match expected length length_in_bytes Invalid restart information was discovered. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Sequence info length length_in_bytes does not match expected length length_in_bytes Invalid restart information was discovered. The system returns an error to the calling software. Contact Informatica Global Customer Support.
524
IDMSX CAPI: Configuration LOGSID configuration_parm_LOGSID_value is being overridden to LOGSID override_LOGSID_value The LOGSID value found in the configuration parameters is being overridden by the specified value. No response is required.The IDMSX instance value is contained in the LOGSID configuration parameter. This value is used to connect to the correct IDMSX log and to filter the registration information that IDMSX CAPI looks for when determining which sources to capture. If there are not found registration errors, ensure that the LOGSID configuration parameter chosen contains the correct capture catalog and instance information. IDMSX CAPI: Number of CAPI caller sources number_of_sources_to_process is different from Setup number number_of_sources_with_restart_information Some source registrations do not contain restart information. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: An invalid registration tag was found. Tag length = length_of_tag_name, tag name = tag_name An invalid source registration name was passed to IDMSX CAPI. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Restart information was not provided for registration tag tag_name The caller of the CAPI routine failed to provide restart information for the specified tag name. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Registration info not found for tag tag_name There was no registration information for the specified tag name. The system returns an error to the calling software. Ensure that the registration tag name you have provided belongs to the IDMSX instance from which you are capturing changes. IDMSX CAPI: Registration info is being processed for tag tag_name Registration information is being processed for the specified tag name. No response is required.This message is emitted to verify that data for the specific registration is being captured. IDMSX CAPI: Multiple LOGSID statements with id LOGSID_name have been found. There are more than one LOGSID statements with the same ID value in the DBMOVER configuration file. The system returns an error to the calling software. Remove the duplicate LOGSID statement from the DBMOVER configuration file.
PWX-16000 to PWX-16999
525
IDMSX CAPI: A LOGSID statement with id LOGSID_name has not been found. There are no LOGSID statements with the same ID as the one specified in the CAPI_CONNECTION TYPE=LOGS statement in dbmover.cfg, or as specified in the PowerCenter IDMSX Capture session parameters. The system returns an error to the calling software. There is either an incorrect specification in the CAPI_CONNECTION statement or one of the LOGSID statements in the DBMOVER configuration file, or in the PowerCenter IDMSX Capture session parameters. Alternatively, the LOGSID statement specified in the CAPI_CONNECTION statement or in the PowerCenter IDMSX Capture session parameters is missing from the DBMOVER configuration file. Fix the problem and retry. IDMSX CAPI: Restart info instance instance_name_from_restart_token does not match expected_instance_instance_name_from_config_file Invalid restart information was discovered. The system returns an error to the calling software. The instance name is specified in a LOGSID statement in the DBMOVER configuration file. If you change this value, and do not reset the Capture job's application, you can get this error. IDMSX CAPI: Defined number of output columns output_columns_defined_to_be_returned_from_IDMSX_CAPI does not match expected number output_columns_defined_to_IDMSX_CAPI Internal CAPI definition of IDMSX capture row image differs from the IDMSX definition. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Defined output column IDMSX_capture_column_name differs from expected column CAPI_capture_column_name Internal CAPI definition of IDMSX capture row image differs from the IDMSX definition. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Expected number of output columns output_columns_defined_to_IDMSX_CAPI differs from returned number columns_returned_from_IDMSX Internal CAPI definition of IDMSX capture row image differs from the capture row returned by IDMSX. The system returns an error to the calling software. Contact Informatica Global Customer Support. IDMSX CAPI: Expected column < column_name > type < column_type > precision < column_precision > scale <column_scale > nullable < nullability_indicator > Internal CAPI definition of IDMSX capture row image differs from the capture row returned by IDMSX. This message is a two-part message. The second part, message PWX-16597, immediately follows. The system returns an error to the calling software. Contact Informatica Global Customer Support.
PWX-16593
Explanation: System Action: User Response: PWX-16594 Explanation: System Action: User Response: PWX-16595
Explanation: System Action: User Response: PWX-16596 Explanation:
526
differs from output column < column_name > type < column_type > precision < column_precision > scale <column_scale > nullable < nullability_indicator > Internal CAPI definition of IDMSX capture row image differs from the capture row returned by IDMSX. This message is the second part of message PWX-16596, which immediately precedes this message. The system returns an error to the calling software. Contact Informatica Global Customer Support. Last message in CAPI IDMSX range This message is informational. Processing continues. No response is required. SMF Storage request failed A request for SMF storage failed Contact Informatica Global Customer Support. Statistics collection to type destination, interval minutes minutes Statistics collection for this PowerExchange Listener is through SMF or file (type) to target SMF record number or data set, with interval collection every minutes minutes. No response is required. SMF subtask creation failed, rc return_code The SMF collection task failed to start. The return code depends on the operating system environment. The PowerExchange Listener ends. Contact Informatica Global Customer Support. SMF interval subtask started, collection interval mins minute(s) The SMF collection task is active and collects statistics every x minutes. No response is required. SMF interval subtask ended, cycle count = count The SMF collection task has ended cleanly, having collected interval data the specified number of times. No response is required. STATS requested to be written to SMF, but loadlib is not APF authorized. Writing STATS to SMF requires the PowerExchange library to be APF authorized. The PowerExchange Listener ends. Add the PowerExchange load library to the APF authorized list.
System Action: User Response: PWX-16699 Explanation: System Action: User Response: PWX-16710 Explanation: User Response: PWX-16711 Explanation: User Response: PWX-16712 Explanation: System Action: User Response: PWX-16713 Explanation: User Response: PWX-16714 Explanation: User Response: PWX-16715 Explanation: System Action: User Response:
PWX-16000 to PWX-16999
527
PWX-19000 to PWX-19999
PWX-19700 Explanation: System Action: User Response: PWX-19701 Explanation: Missing parm parameter The parameter is required for DTLUCSR2. The DTLUCSR2 utility processing ends. Code the missing parameter. Error on print DBCB call_type call, rcs=return_code1/return_code2/return_code3 DTLUCSR2 encountered an error while processing the DATABASE FILE. In the message text
call_type is the type of call for which the error occurred. return_code1, return_code2, and return_code3 are the PowerExchange return codes for the failure. System Action: User Response: PWX-19702 Explanation: System Action: User Response: PWX-19703 Explanation: System Action: User Response: PWX-19704 Explanation: System Action: User Response: PWX-19706 Explanation: System Action: User Response: PWX-19707 Explanation: System Action: User Response: PWX-19708 Explanation: System Action:
528
Processing ends. Correct the error. Then, run the request again. Error processing DATABASE FILE An error was encountered processing the DATABASE FILE, additional messages follow. The DTLUCSR2 utility processing ends. Investigate error. Unexpected end of file reached on DATABASE FILE While reading from DATABASE FILE, end of file (EOF) was reached. The DTLUCSR2 utility processing ends. Investigate error. Read error on DATABASE FILE, rc=return_code rc_description DTLUCSR2 encountered an error while reading the DATABASE FILE. Processing ends. Correct the error. Then, run the request again. Internal error, prog=program_name, line=line_number, desc=description An internal error was encountered. The system returns an error to the calling software. Contact Informatica Global Customer Support. Open error on DATABASE FILE, rc="return_code" rc_description DTLUCSR2 encountered an error while opening the DATABASE FILE. Processing ends. Correct the error. Then, run the request again. fldata() failed for DATABASE FILE, rc="return_code" fldata() call failed attempting to obtain block size information for DATABASE FILE. Processing ends.
Correct the error. Then, run the request again. Unable to obtain DSN for DATABASE FILE fldata() call failed attempting to obtain block size information for DATABASE FILE. Processing ends. Correct the error. Then, run the request again. Return File Info allocation failure, error code=0x"error_code_in_hex", info code=0x"info_code_in_hex" DTLUCSR2 encountered an error when attempting to obtain file information using MVS dynamic allocation. The error and info codes are documented in the IBM MVS Programming: Authorized Assembler Services Guide. The system returns an error to the calling software. Attempt to correct the problem based on error/info codes. DATABASE FILE fseek failed: rc="fseek_return_code"; offset="fseek_position"; method=method DTLUCSR2 encountered an error using fseek on the DATABASE FILE. The system returns an error to the calling software. Attempt to correct the problem based on error/info codes. Missing parm parameter The parameter is required for DTLULCAT. The DTLULCAT utility Processing ends. Code the missing parameter. Error on print DBCB call_type call, rcs=return_code1/return_code2/return_code3 DTLULCAT encountered an error while processing the DD LOGFILE. In the message text

call_type is the type of call that encountered the error. return_code1, return_code2, and return_code3 are the PowerExchange return codes for the failure.
Processing ends. Correct the error. Then, run the request again. Error processing LOGFILE An error was encountered processing DD LOGFILE, additional messages follow. The DTLULCAT utility processing ends. Investigate error. Unexpected end of file reached on DD LOGFILE While reading from DD LOGFILE, end of file (EOF) was reached. The DTLULCAT utility processing ends. Investigate error.
PWX-19000 to PWX-19999
529
Read error on DD LOGFILE, rc="return_code" rc_description DTLULCAT encountered an error while reading the DD LOGFILE. Processing ends. Correct the error. Then, run the request again. First LOGFILE record is not TIME. The first record read from the DD LOGFILE should be a TIME record, but it is not. Processing ends. Examine logfile. Internal error, prog=program_name, line=line_number, desc=description An internal error was encountered. The system returns an error to the calling software. Contact Informatica Global Customer Support. Open error on DD LOGFILE, rc="return_code" rc_description DTLULCAT encountered an error while opening the DD LOGFILE. Processing ends. Correct the error. Then, run the request again. fldata() failed for DD LOGFILE, rc="return_code" fldata() call failed attempting to obtain block size information for DD LOGFILE. Processing ends. Correct the error. Then, run the request again. Unable to obtain DSN for DD LOGFILE fldata() call failed attempting to obtain block size information for DD LOGFILE. Processing ends. Correct the error. Then, run the request again. Return File Info allocation failure, error code=0x"error_code_in_hex", info code=0x"info_code_in_hex" DTLULCAT encountered an error when attempting to obtain file information using MVS dynamic allocation. The error and info codes are documented in the IBM MVS Programming: Authorized Assembler Services Guide. The system returns an error to the calling software. Attempt to correct the problem based on error/info codes. LOGFILE fseek failed: rc="fseek_return_code"; offset="fseek_position"; method=method DTLULCAT encountered an error using fseek on the file LOGFILE. The system returns an error to the calling software. Attempt to correct the problem based on error/info codes.
530
PWX-19804 Explanation: System Action: User Response: PWX-19805 Explanation: System Action: User Response: PWX-19817 Explanation: System Action: User Response: PWX-19818 Explanation: System Action: User Response: PWX-19850 Explanation: System Action: User Response: PWX-19851 Explanation: User Response: PWX-19852 Explanation: System Action: User Response: PWX-19853 Explanation: System Action: User Response: PWX-19854 Explanation: System Action:
IDMS CATLG: STATUS must be A,S or T Correct the STATUS parameter and resubmit. Program ends with return code 8. No response is required. IDMS CATLG: LOG_DATA_TYPE must be IXL or IDL Correct the LOG_DATA_TYPE parameter and resubmit. Program ends with return code 8. No response is required. IDMS CATLG: FIRST_RECORD_SEQUENCE_NUMBER Sequence number must be 16 in length Ensure that the FIRST_RECORD_SEQUENCE_NUMBER parameter is 16 characters in length and resubmit. Program ends with return code 8. No response is required. IDMS CATLG: FIRST_RECORD_TIME_STAMP Timestamp must be 16 in length and greater than the previous Entry added. Correct the FIRST_RECORD_TIME_STAMP parameter and resubmit. Program ends with return code 8. No response is required. IDMS CATLG FILE: VSAM Error rc=return_code A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Record with key key_and_data successfully added. This message is informational. No response is required. IDMS CATLG FILE: Record Add Failure with key key_and_data. A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Internal error - function not known. Internal function error Program ends with return code 8. Inform the software vendor. IDMS CATLG FILE: Entry Record with key key_and_data - Deletion Failure. A VSAM/cISAM error occurred. Program ends with return code 8.
PWX-19000 to PWX-19999 531
Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Instance Record with key key_and_data - Insertion Failure. A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Record with key key_and_data - Remove Instance Failure. A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Entry Record with key key_and_data - Update Failure. A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Instance with key key_and_data - Report Failure. A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Instance with key key_and_data - Export Failure. A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Add Entry Failure trying to add Entry num new_number, current highest is highest_so_far A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file instance and entries, correct any errors, resubmit. IDMS CATLG FILE: Add Entry Failure trying to read highest entry Entry num entry_number A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Add Entry Failure - Timestamp not greater than previous for key key_and_data A VSAM/cISAM error occurred. Program ends with return code 8. Review the IDMS Catalog file, last entry added - new one must have a higher timestamp. Correct any errors, resubmit.
532
PWX-19863 Explanation: User Response: PWX-19864 Explanation: User Response: PWX-19865 Explanation: User Response: PWX-19866 Explanation: System Action: User Response: PWX-19867 Explanation: System Action: User Response: PWX-19868 Explanation: User Response: PWX-19869 Explanation: System Action: User Response:
IDMS CATLG FILE: Instance successfully removed, key key_and_data This message is informational. No response is required. IDMS CATLG FILE: Entry successfully removed, key key_and_data This message is informational. No response is required. IDMS CATLG FILE: Instance successfully inserted, key key_and_data This message is informational. No response is required. IDMS CATLG FILE: Add Instance Failure - key already exists key_and_data The Instance being added already exists. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Instance not found - key key_and_data The Instance being accessed does not exist. Program ends with return code 8. Review the IDMS Catalog file, correct any errors, resubmit. IDMS CATLG FILE: Entry successfully updated, key key_and_data This message is informational. No response is required. IDMS CATLG FILE: Add Entry Failure - Central/Local journal timestamps mismatch for key key_and_data An existing Central mode journal has a timestamp that conflicts with a Local journal being added. Program ends with return code 8. An existing Central mode journal has a first record timestamp that is later than the timestamp of the last record in the Local journal being added. IDMS CATLG FILE: END OF INPUT FILE This message is informational. No response is required. IDMS CATLG FILE: Last Error message for IDMS Catalog This message is informational. No response is required. IDMS ILSR2: SR3 Database Key, K= value, length range 1 to 8 Correct the SR3 Database Key, K= value parameter and resubmit (Max length 8). Program ends with return code 8.
PWX-19870 Explanation: User Response: PWX-19899 Explanation: User Response: PWX-19950 Explanation: System Action:
PWX-19000 to PWX-19999
533
No response is required. IDMS ILSR2: SR3 Record Identifier, R= value, length range 0 to 9999 Correct the SR3 Record Identifier, R= value parameter and resubmit (Numeric 0 to 9999). Program ends with return code 8. No response is required. IDMS ILSR2: SR3 Record Length, L= value, length range 100 to 32767 Correct the SR3 Record Length, L= value parameter and resubmit (Numeric 100 to 32767). Program ends with return code 8. No response is required. IDMS ILSR2: SR3 Page Group, P= value, length range 0 to 32767 Correct the SR3 Page Group, P= value parameter and resubmit (Numeric 0 to 32767). Program ends with return code 8. No response is required. IDMS ILSR2: SR3 SUM Total, SR2TOTAL value, length range 1 to 8 Correct the SR3 SUM Total value, SR2TOTAL= value parameter and resubmit (Max length 16). Program ends with return code 8. No response is required. IDMS ILSR2: SR3 END Total, SR2TOTAL value, length range 1 to 8 Correct the SR3 END Total value, SR2TOTAL= value parameter and resubmit (Max length 16). Program ends with return code 8. No response is required. IDMS ILSR2: SR3 Database Key, K=string non character hexadecimal digit at position position Correct the SR3 Database Key, K= value parameter and resubmit (Max length 8). Program ends with return code 8. No response is required. IDMS ILSR2: SR3 SUM Total, SR2TOTAL value string, non character hexadecimal digit at position position Correct the SR3 SUM Total value, SR2TOTAL= value parameter and resubmit (Max length 16). Program ends with return code 8. No response is required.
534
IDMS ILSR2: SR3 END Total, SR2TOTAL value string, non character hexadecimal digit at position position Correct the SR3 END Total value, SR2TOTAL= value parameter and resubmit (Max length 16). Program ends with return code 8. No response is required. IDMS ILSR2: SR2 Database Key, K=string non character hexadecimal digit at position position Correct the SR2 Database Key, K= value parameter and resubmit (Max length 8). Program ends with return code 8. No response is required. IDMS ILSR2: SR2 Database Key, K= value, length range 1 to 8 Correct the SR2 Database Key, K= value parameter and resubmit (Max length 8). Program ends with return code 8. No response is required.
PWX-20000 to PWX-20999
PWX-20010 Explanation: System Action: User Response: PWX-20011 Explanation: System Action: User Response: PWX-20012 Explanation: System Action: User Response: supporting_information The DB2 for Linux, UNIX, and Windows CAPI module issued a message that required additional supporting information contained in this message. Depends on specific message issued. Based on specific message issued. Restart info length length invalid, must be length The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart info. Restart info database database(0xhex_database_value) invalid, must be database (0xhex_database_value) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart info or correct the CAPI configuration information to reflect the correct volume set name. Restart info VTS virtual_time_stamp invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software.
PWX-20000 to PWX-20999
535
User Response: PWX-20014 Explanation: System Action: User Response: PWX-20015 Explanation: System Action: User Response: PWX-20016 Explanation: System Action: User Response: PWX-20017 Explanation: System Action: User Response: PWX-20018 Explanation: System Action: User Response: PWX-20019 Explanation: System Action: User Response: PWX-20020 Explanation: User Response: PWX-20021 Explanation:
Correct the source of the invalid restart sequence number. Sequence info commit VTS hex_sequence_value invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Sequence info commit accuracy hex_sequence_value invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Sequence info length length invalid, must be length The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Sequence info 0x hex_sequence_value invalid (reason=<reason_code>) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid sequence information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Database missing The DB2 for Linux, UNIX, and Windows CAPI module requires that database be specified in the CAPI_CONNECTION information. The system returns an error to the calling software. Correct the CAPI_CONNECTION information. Sequence info commit partition hex_number invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. UDB commit VTS : virtual_time_stamp
The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format sequence information. No response is required. UDB commit partition: commit_partition_number The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart information.
536
User Response: PWX-20022 Explanation: User Response: PWX-20023 Explanation: User Response: PWX-20024 Explanation: User Response: PWX-20025 Explanation: User Response: PWX-20026 Explanation: User Response: PWX-20027 Explanation: User Response: PWX-20028 Explanation: User Response: PWX-20029 Explanation: User Response: PWX-20030 Explanation: User Response:
No response is required. UDB record partition: record_partition_number The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart sequence information. No response is required. UDB record LLSN : record_logical_LSN
The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart sequence information. No response is required. UDB publish sequence: number The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart sequence information. No response is required. UDB database : database_name
The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart information. No response is required. UDB restart VTS time: virtual_time_stamp The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart information. No response is required. UDB sequence <NULL> The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart information. No response is required. Default The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart information. No response is required. NULL The DB2 for Linux, UNIX, and Windows CAPI module uses this message to format restart information. No response is required. Database database_name partition partition_number This message communicates the database and partition and is issued in conjunction with other messages. No response is required.
PWX-20000 to PWX-20999
537
PWX-20031 Explanation: System Action: User Response: PWX-20032 Explanation: User Response: PWX-20033 Explanation: User Response: PWX-20034 Explanation: System Action: User Response: PWX-20035 Explanation: User Response: PWX-20036 Explanation: System Action: User Response: PWX-20037 Explanation: System Action: User Response: PWX-20038 Explanation:
no_filter_tag and other tags cannot be mixed The DB2 for Linux, UNIX, and Windows CAPI module encountered the special registration tag indicating no filtering in combination with other registration tags. The system returns an error to the calling software. Contact Informatica Global Customer Support. UDB transaction transaction_id, first log record LLSN logical_LSN The DB2 for Linux, UNIX, and Windows CAPI module uses this message to report the transaction ID and logical LSN of a unit of work associated with other messages. No response is required. UPD table: <schema_name>.<table_name> The DB2 for Linux, UNIX, and Windows CAPI module uses this message to report the table name of a resource associated with other messages. No response is required. Column column_name contains an unsupported default default_value_text The DB2 for Linux, UNIX, and Windows CAPI module needed to map the default value of a column and the value is not supported. The system returns an error to the calling software. Contact Informatica Global Customer Support. Database database_name transaction commit VTS commit_VTS_value restart time restart_VTS_time The DB2 for Linux, UNIX, and Windows CAPI module uses this message to report the logical unit of work associated with other messages. No response is required. Internal error, prog=program_name, line=line_number, desc=description An internal error was encountered. The system returns an error to the calling software. Contact Informatica Global Customer Support. Repository call function_name failed for repository return_code The DB2 for Linux, UNIX, and Windows CAPI module encountered an error when attempting to interact with the repository. The system returns an error to the calling software. Contact Informatica Global Customer Support. Tag registration_tag database database_name does not match configured database database_name The DB2 for Linux, UNIX, and Windows CAPI module determined that the registration tag in question does not appear to be on the database specified in the CAPI_CONNECTION information. The system returns an error to the calling software. Correct the source of the invalid restart info or correct the CAPI configuration information to reflect the correct database name.
538
No active entry for registration tag registration_tag found in repository location The DB2 for Linux, UNIX, and Windows CAPI module could not locate the registration tag specified in the repository at the location specified. The system returns an error to the calling software. Correct the problem by specifying the correct location or removing the registration tag from the list of sources. no_filter_tag specified without RequestNoChangeData extended attribute The DB2 for Linux, UNIX, and Windows CAPI module encountered the special registration tag indicating no filtering without the RequestNoChangeData extended attribute. The system returns an error to the calling software. Contact Informatica Global Customer Support. Registration tags registration_tag and registration_tag both refer to table creator_name.table_name The DB2 for Linux, UNIX, and Windows CAPI module encountered multiple registration tags referring to the same table. The system returns an error to the calling software. Contact Informatica Global Customer Support. Table registration creator_name.table_name columns column_name and column_name both have output column number output_column_number The DB2 for Linux, UNIX, and Windows CAPI module encountered a table registration with multiple columns with the same output column number. The system returns an error to the calling software. Contact Informatica Global Customer Support. Table registration creator_name.table_name contains column name column_name more than once The DB2 for Linux, UNIX, and Windows CAPI module encountered a table registration with multiple columns with the same name. The system returns an error to the calling software. Contact Informatica Global Customer Support. Table registration creator_name.table_name column column_name has unsupported type <data_type> The DB2 for Linux, UNIX, and Windows CAPI module encountered a table registration with a column with an unsupported data type. The system returns an error to the calling software. Remove column from registration or contact Informatica Global Customer Support. Table registration creator_name.table_name does not represent all columns in schema (see log) The DB2 for Linux, UNIX, and Windows CAPI module encountered data for a table registration with select all and notify changes and some of the columns in the actual table were not in the registration.
System Action: User Response: PWX-20041 Explanation: System Action: User Response: PWX-20042 Explanation: System Action: User Response: PWX-20043 Explanation: System Action: User Response: PWX-20044 Explanation: System Action: User Response: PWX-20045 Explanation:
PWX-20000 to PWX-20999
539
The system returns an error to the calling software. Correct registration or contact Informatica Global Customer Support. Table registration creator_name.table_name contains columns not in schema (see log) The DB2 for Linux, UNIX, and Windows CAPI module encountered data for a table registration with select all and notify changes and some of the columns in the registration were not in the actual table. The system returns an error to the calling software. Correct registration or contact Informatica Global Customer Support. Column column_name Column name related to an other error message. No response is required. Transaction hex_transaction_ID on partition partition_number starts at LLSN hex_logical_LSN This message is issued in conjunction with other messages to report the LLSN where a transaction starts. No response is required. Tag name tag_name Tag name related to an other error message. No response is required. Record at LLSN hex_logical_LSN ignored because transaction hex_transaction_ID not active The DB2 for Linux, UNIX, and Windows CAPI module encountered a record that was not associated with an active transaction. This can during restart and is only provided as a possible diagnostic. No response is required. Record at LLSN hex_logical_LSN is a data operation related to a catalog operation in the same transaction The DB2 for Linux, UNIX, and Windows CAPI module encountered a data operation and a catalog operation for a table being captured in the same transaction. The UDB capture process does not support this. The system returns an error to the calling software. Adjust the restart point to skip over this transaction. This might involve rematerializing the table. Table <schema_name>.<table_name> Table name related to an other error message. No response is required. Record at LLSN hex_logical_LSN is record_type, not expected in state state_name The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected record in the log. The system returns an error to the calling software.
System Action: User Response: PWX-20047 Explanation: User Response: PWX-20048 Explanation: User Response: PWX-20049 Explanation: User Response: PWX-20050 Explanation:
PWX-20052 Explanation: User Response: PWX-20053 Explanation: System Action:

540
User Response: PWX-20054 Explanation: System Action: User Response: PWX-20055 Explanation: System Action: User Response: PWX-20056 Explanation:
Contact Informatica Global Customer Support. Record at LLSN hex_logical_LSN references TID=0xhex_ID FID=0xhex_ID, expected TID=0xhex_ID FID=0xhex_ID The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected record in the log. The system returns an error to the calling software. Contact Informatica Global Customer Support. Record at LLSN hex_logical_LSN has problem: description The DB2 for Linux, UNIX, and Windows CAPI module encountered an error with a record in the log. The system returns an error to the calling software. Contact Informatica Global Customer Support. Record at LLSN hex_logical_LSN is normal commit for crashing transaction The DB2 for Linux, UNIX, and Windows CAPI module encountered a record with contradictory information. This has most likely been handled correctly and is issued only as a possible diagnostic. No response is required. Partition partition_number transaction transaction_id This message communicates the partition and transaction ID and is issued in conjunction with other messages. No response is required. UDB CAPI_CONNECTION parameter_name parameter requires parameter_name parameter In a UDB CAPI_CONNECTION statement, one parameter requires the specification of a second parameter. Processing ends. Correct the error. Then, run the request again. UDB DB database_name: CAPI_CONNECTION statement is the source of security information; USERID=user_ID The CAPI_CONNECTION statement is the source of the user ID and password used when connecting to the UDB database. Processing continues. No response is required. API call function_name returned return_code The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected return code from the call indicated. The system returns an error to the calling software. Contact Informatica Global Customer Support.
User Response: PWX-20057 Explanation: User Response: PWX-20058 Explanation: System Action: User Response: PWX-20059 Explanation: System Action: User Response: PWX-20060 Explanation: System Action: User Response:
PWX-20000 to PWX-20999
541
PWX-20061 Explanation: System Action: User Response: PWX-20062
API call function_name failed for table <schema_name>.<table_name> The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected return code from the call indicated when processing the table specified. The system returns an error to the calling software. Contact Informatica Global Customer Support. Compensation Record at LLSN "hex_logical_LSN" "CAPDL_record_type_name" ("CAPDL_record_type_value") TID=0xhex_ID FID=0xhex_ID does not match queued op "queued_operation_type_name" ("queued_operation_type_value") TID=0xhex_ID FID=0xhex_ID While collapsing backout records for a transaction, the DB2 for Linux, UNIX, and Windows consumer API (CAPI) module encountered an unacceptable sequence of log records. This message is primarily for diagnostic use by Informatica Global Customer Support. An error is returned to the calling software. Contact Informatica Global Customer Support. Compensation Record at LLSN "hex_logical_LSN" should be "CAPDL_record_type_name" ("CAPDL_record_type_value") While collapsing backout records for a transaction, the DB2 for Linux, UNIX, and Windows consumer API (CAPI) module encountered an unacceptable sequence of log records. An error is returned to the calling software. Contact Informatica Global Customer Support. Capture catalog (capture_catalog_name) initialization failed with rc=return_code The DB2 for Linux, UNIX, and Windows CAPI module encountered an error when attempting to access the capture catalog. The system returns an error to the calling software. Attempt to resolve the problem based on other error messages issued. API call function_name returned return_code The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected return code from the call indicated. The system returns an error to the calling software. Contact Informatica Global Customer Support. Capture catalog (capture_catalog_name) probably corrupted or uninitialized The DB2 for Linux, UNIX, and Windows CAPI module encountered an error when attempting to access the capture catalog. The system returns an error to the calling software. Verify the capture catalog was initialized, if it has contact Informatica Global Customer Support. Capture catalog (capture_catalog_name) row error VTSTIME=virtual_time_stamp VTSACC=number The DB2 for Linux, UNIX, and Windows CAPI module encountered an error in the row corresponding to the values in the message.
Explanation:
542
The system returns an error to the calling software. Contact Informatica Global Customer Support. Column column_name registration shows NOT NULL, but actual column is nullable The column registration does not match the actual column definition. An error is return to the calling software. Correct registration or contact Informatica Global Customer Support to report error. Column column_name registration shows nullable, but actual column is NOT NULL The column registration does not match the actual column definition. An error is return to the calling software. Correct registration or contact Informatica Global Customer Support to report error. Column column_name registration shows type type_name (internal_type_name), but actual column is type catalog_type_name The column registration does not match the actual column definition. An error is return to the calling software. Correct registration or contact Informatica Global Customer Support to report error. Column column_name registration has an incompatible length for the actual column The column registration does not match the actual column definition. An error is return to the calling software. Correct registration or contact Informatica Global Customer Support to report error. Column column_name registration has an incompatible scale for the actual column The column registration does not match the actual column definition. An error is return to the calling software. Correct registration or contact Informatica Global Customer Support to report error. Table registration creator_name.table_name contains incompatible or unsupported columns (see log) The DB2 for Linux, UNIX, and Windows CAPI module encountered a table registration with one or more columns with columns incompatible with the current schema or with unsupported data types. The system returns an error to the calling software. Remove column from registration or contact Informatica Global Customer Support. Column column_name registration shows codepage, but actual column has codepage The column registration does not match the actual column definition. An error is return to the calling software. Correct registration or contact Informatica Global Customer Support to report error.
PWX-20000 to PWX-20999
543
Table registration <"creator_name"."table_name"> is not defined; registration tag name <"tag_name"> During DB2 for Linux, UNIX, and Windows CDC, the PowerExchange UDB CAPI did not find the specified DB2 table in the capture catalog table or at the restart point. This problem might occur for the following reasons:

The The The The System Action: User Response:
table no longer exists. restart point is invalid. capture registration is corrupted or is not the correct one for the table. UDB CAPI_CONNECTION statement points to the wrong capture catalog table.
The system returns an error to the calling software. Verify that the capture registration, restart point, and capture catalog are correct. Correct any problems, and then rerun the CDC session. Table registration creator_name.table_name does not have data capture changes on The DB2 for Linux, UNIX, and Windows CAPI module did not find the table to be defined with data capture changes on at the restart point or current catalog. The system returns an error to the calling software. Correct registration or alter table and rerun. Table registration creator_name.table_name contains long fields and does not have data capture changes including long fields on The DB2 for Linux, UNIX, and Windows CAPI module found the table to contain long fields and did not find the table to be defined with data capture changes including long fields on at the restart point or current catalog. The system returns an error to the calling software. Correct registration or alter table and rerun. Additional table registration capture problems in log The DB2 for Linux, UNIX, and Windows CAPI module found problems with the requested registrations. See the log on the capture system for details of these problems. The system returns an error to the calling software. Correct problems and rerun. Table registration creator_name.table_name contains long columns and does not have data capture changes including long fields on The DB2 for Linux, UNIX, and Windows CAPI module encountered data for a table registration with columns with either LONG VARCHAR or LONG VARGRAPHIC types and data capture changes including long fields was not active. The system returns an error to the calling software. Correct registration or alter table and rerun. Table registration <"creator_name"."table_name"> indicates use of row compression. PowerExchange does not support change data capture (CDC) for DB2 for Linux, UNIX, and Windows Version 9.7 tables that use data row compression. PowerExchange issues an error message and capture processing ends. Disable data row compression for the specified table by setting the DB2 COMPRESS attribute to NO.
544
Capture catalog table_name has number partitions, database database_name has number partitions A UDB Capture module encountered a difference between what the capture catalog and the database report for the number of partitions. If partitions have been added or removed, the DTLUCUDB SNAPUPDT utility might need to be run. The system returns an error to the calling software. Correct problems and rerun. Capture catalog table_name partition information does not match database database_name A UDB Capture module encountered a difference between what the capture catalog and the database report for partition information. The system returns an error to the calling software. Correct problems and rerun. Capture catalog table_name reports number as catalog partition, database database_name reports number A UDB Capture module encountered a difference between what the capture catalog and the database report for the catalog partition. The system returns an error to the calling software. Correct problems and rerun. Database database_name reports both partition number and partition number as catalog partitions The DB2 for Linux, UNIX, and Windows CAPI module encountered the database reporting more than one catalog partition. The system returns an error to the calling software. Correct problems and rerun. Database database_name reported no catalog partition The DB2 for Linux, UNIX, and Windows CAPI module encountered a problem when the database did not report a catalog partition. The system returns an error to the calling software. Correct problems and rerun. Sequence info record partition hex_number invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Sequence info record LLSN hex_number invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number.
System Action: User Response: PWX-20101 Explanation: System Action: User Response: PWX-20102 Explanation: System Action: User Response: PWX-20103 Explanation: System Action: User Response: PWX-20104 Explanation: System Action: User Response: PWX-20110 Explanation: System Action: User Response: PWX-20111 Explanation: System Action: User Response:
PWX-20000 to PWX-20999
545
PWX-20112 Explanation: System Action: User Response: PWX-20120 Explanation: System Action: User Response: PWX-20121
Sequence info publish sequence hex_number invalid (reason=reason_code) The DB2 for Linux, UNIX, and Windows CAPI module encountered invalid restart information. The system returns an error to the calling software. Correct the source of the invalid restart sequence number. Subordinate transaction transaction_id on partition number ignored because it references non-existent partition number The DB2 for Linux, UNIX, and Windows CAPI module encountered a subordinate unit of work that indicated a coordinating partition that no longer exists. The unit of work is discarded. No response is required. Subordinate transaction transaction_id on partition number ignored because coordinating partition number reached VTS virtual_time_stamp and commit was VTS virtual_time_stamp The DB2 for Linux, UNIX, and Windows CAPI module encountered a subordinate unit of work that had a commit virtual time stamp less than the current virtual time stamp on the coordinating partition. The unit of work is discarded. No response is required. Coordinating transaction transaction_id on partition number references subordinate transaction on non-existent partition number The DB2 for Linux, UNIX, and Windows CAPI module encountered a coordinating unit of work that indicated a subordinate transaction on a non-existent partition. The subordinate unit of work is ignored. No response is required. Coordinating transaction transaction_id on partition number references subordinate transaction on partition number that was not found The DB2 for Linux, UNIX, and Windows CAPI module encountered a coordinating unit of work that indicated a subordinate transaction on a non-existent partition. The subordinate unit of work is ignored. No response is required. End of log reached at VTS end_of_log_VTS_value before seek VTS of seek_VTS_value The DB2 for Linux, UNIX, and Windows CAPI module reached the end of log without encountering the seek point. The system returns an error to the calling software. Contact Informatica Global Customer Support. Transaction transaction_id has no VTS The DB2 for Linux, UNIX, and Windows CAPI module encountered a unit of work (UOW) required for processing that does not contain a VTS. An error is returned to the calling software. Contact Informatica Global Customer Support.
Explanation:
546
STOPTASK received while seeking restart point The DB2 for Linux, UNIX, and Windows CAPI module received STOPTASK seeking restart point in the UDB log Processing ends. No response is required. Unable to find partition partition_number LSN positioning entry for Seek VTS start_of_log_VTS_value The UDB CAPI attempts to position within the various log files to begin reading log data. For the given partition, no LSN positioning entry was found. Processing ends. No response is required. Table object log record skipped because of no matching SYSTABLES activity The DB2 for Linux, UNIX, and Windows CAPI module encountered a create or drop table object log record without any matching SYSTABLES activity. This most likely represents REDISTRIBUTE processing and was therefore skipped. The log record is skipped. No response is required. Catalog operation catalog_operation_description missing The DB2 for Linux, UNIX, and Windows CAPI module expected the catalog operation, but did not find it. An error is return to the calling software. Contact Informatica Global Customer Support to report error. No matching data partition operations found (catalog_operation_description) The DB2 for Linux, UNIX, and Windows CAPI module did not find any matching data partition operations for a system table operation. An error is return to the calling software. Contact Informatica Global Customer Support to report error. Unexpected catalog operation catalog_operation_description The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected catalog operation. An error is return to the calling software. Contact Informatica Global Customer Support to report error. Column create_or_drop for column column_name in table creator_name.table_name skipped The DB2 for Linux, UNIX, and Windows CAPI module encountered a create or drop column log record with a table name that was not known. This record was probably a non-table object, such as a view. The log record is skipped. No response is required.
PWX-20000 to PWX-20999
547
Database database_name previous transaction commit VTS commit_VTS_value restart time restart_VTS_time The DB2 for Linux, UNIX, and Windows CAPI module uses this message to report the previous logical unit of work associated with other messages. No response is required. Expected consecutive catalog column operations to be identical: first=column_operation current=current_column_operation The DB2 for Linux, UNIX, and Windows CAPI module expected identical consecutive catalog operations but found unlike operations. In the message text:

column_operation is the first catalog operation. current_column_operation is the latest catalog operation.
System Action: User Response: PWX-20146 Explanation: System Action: User Response: PWX-20160 Explanation: User Response: PWX-20163 Explanation: User Response: PWX-20201 Explanation: System Action: User Response: PWX-20202 Explanation: System Action: User Response: PWX-20203 Explanation:
An error is returned to the calling software. Contact Informatica Global Customer Support. Expected consecutive catalog operations to be for same table: first=creator.table current=creator.table The DB2 for Linux, UNIX, and Windows CAPI module expected, but did not find, consecutive catalog operations to be for the same table. An error is returned to the calling software. Contact Informatica Global Customer Support. CCatalog statistics capture_catalog_state processing This message begins a report of UDB Capture Catalog entries. No response is required. number_of_entries CCatalog capture catalog entry_type_entries This message displays a count of entries in the capture catalog for a certain entry type. No response is required. CAPDL: Unable to allocate storage for resource. UDB Log Reader ends. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDL Internal error, prog=program_name, line=line_number, desc=description UDB Log Reader encountered an internal error in processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. DB2 API db2ReadLog error. DB=database_ID PART=partition_number sqlcode=sql_code APIrc=return_code function=function (additional_information) The DB2 for Linux, UNIX, and Windows Log Reader received an SQL error from the DB2 API when reading change data from the DB2 logs. In the message text:
548
database_ID identifies the database for which the DB2 logs were being read. partition_number identifies the DB2 partition for which the DB2 logs were being read. sql_code is the SQL code that was returned for the error. return_code is the DB2 API return code that was returned for the error. function is the DB2 API function code or operation. additional_information is related information, which might also be shown in PWX-20251. DB2 change data capture processing stops. Contact Informatica Global Customer Support. SQL_message UDB Message text relating to preceding PWX-20203 message. No response is required. CAPDL: Error formatting sql error code; rc=SQL_message (SQL_message) Error received while trying to format the preceding SQL error code. No response is required. CAPDL: GetRecord CAPDL_LSN does not ascend: current lsn=lsn, previous lsn=lsn Error received while trying to format the preceding SQL error code. No response is required. CAPDL: UDB Log Read Error: requested lsn=lsn ; returned lsn=lsn ; last read lsn=lsn The UDB Log Read routine did not return the expected log record. The system returns an error to the calling software. No response is required. CAPDL: UDB Log Read Error: LSNs do not ascend: last good lsn=lsn ; next lsn=lsn The UDB Log Read routine did not return the expected log record. The system returns an error to the calling software. No response is required. CAPDL: UDB DB database; PART partition; log record at lsn may contain unrecognized data more_info The UDB Log Read routine read a record that did not conform to its knowledge of UDB log records. If the UDB log reader is requested to stop on this event, the log record is dumped and an error is returned. If the log reader is not requested to stop on this event, the log record is dumped and processing continues. The log reader can be directed to limit the number of records dumped. An error is returned if the reader is directed to do such. No response is required. count - unrecognized suspect_reason This message describes why message PWX-20211 is issued. This message might appear multiple times after message PWX-20211. Processing continues. No response is required.
PWX-20000 to PWX-20999 549
System Action: User Response: PWX-20204 Explanation: User Response: PWX-20205 Explanation: User Response: PWX-20207 Explanation: User Response: PWX-20209 Explanation: System Action: User Response: PWX-20210 Explanation: System Action: User Response: PWX-20211 Explanation:
diagnostic_info There is an error with or suspicion about a UDB log record. This is diagnostic line might be one of several. An error might be returned to the calling software. No response is required. CAPDL: UDB DB database; PART partition; max count(max_count_value) of records with possible unrecognized data reached The UDB log reader was directed to limit the number of records to report that do not conform to the log reader's understanding of log records and the limit was reached. Processing continues. No response is required. CAPDL: Incorrect header level: expected expected_level; received received_level There is an incompatibility between the UDB log reader and its caller. The system returns an error to the calling software. No response is required. CAPDL: Format value invalid for internal UDB record; RecType=0xrecord_type; FMT=0xformat_type While decoding a portion of UDB log record the log reader detected an improper value. The system returns an error to the calling software. No response is required. CAPDL: UDB DB database; PART partition; log record at lsn is invalid; rc=return_code more_info The UDB log reader detected an error in log record. The rc value is the number of a message appearing with more detail of the error. A dump of the log record is generated locally. The system returns an error to the calling software. No response is required. CAPDL: FMT1 row image does not match prepare data: prepare length 0xprepare_length; row length 0xrow_length; table table The UDB log reader was requested to decode a row image for a table. The row image did not match information presented describing the row. The row image and row description information are dumped locally. The system returns an error to the calling software. No response is required. CAPDL: FMT2 row image does not match prepare data: columns at prepare Prepare_column_count; columns in row log_record_column_count; table table_name The UDB log reader was requested to decode a row image for a table. The row image did not match information presented describing the row. The row image and row description information are dumped locally. The system returns an error to the calling software. No response is required.

550
CAPDL: FMT2 row image internal length 0xinternal_length does not match external length 0xexternal_length; table table_name The UDB log reader was requested to decode a row image for a table. The row image did not match information presented describing the row. The row image and row description information are dumped locally. The system returns an error to the calling software. No response is required. CAPDL: UDB DB database; PART partition; log record at lsn handling unclear: reason The UDB log reader has read a record that the reader believes is critical for processing but does not know how to process. The system returns an error to the calling software. No response is required. CAPDL: Unexpected SYSTEM DEFAULT attribute found (attribute value 0xattribute_value) for column column_number of table_name The UDB log reader was requested to decode a row image for a table. A column in the row contained the SYSTEM DERAULT attribute, and this column type should not have this attribute. The system returns an error to the calling software. No response is required. CAPDL: Unexpected attribute value 0xattribute_value found in FMTformat_type row data for column column_number of table_name The UDB log reader was requested to decode a row image for a table. A column in the row contained an attribute that was not expected. The system returns an error to the calling software. No response is required. CAPDL: Row Image Dump: image is image_information A row image is being dumped for some problem. Processing continues. No response is required. CAPDL: Column column_number data outside row image: offset 0xoffset length 0xlength image length 0ximage_length; Table table_name The UDB log reader was requested to decode a row image for a table. While locating data for a column an inconsistency was detected. The system returns an error to the calling software. No response is required. CAPDL: No (0) columns presented to CAPDL_PREPARE; Table table_name The UDB log reader was presented table information for future row image decoding but there were no columns presented. The system returns an error to the calling software. No response is required.
PWX-20000 to PWX-20999
551
CAPDL: Table: table Column: column is not nullable and has no default value CAPDL_Execute tried to produce a column value for column not physically present in the row image, however the column was not nullable and did not have a default value. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDL: Database must be configured with LOG RETAIN and/or USER EXITS ON. The UDB log reader uses the UDB db2ReadLog API that has this requirement. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDL: API Usage Error: error_description A usage error occurred using the CAPDL API. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDL: Inconsistent data returned by db2ReadLog The PowerExchange DB2 for Linux, UNIX, and Windows Log Reader received inconsistent data from the DB2 API db2ReadLog routine. The DB2 control blocks that were used to read the log buffer are dumped. DB2 change data capture processing ends. Contact Informatica Global Customer Support. CAPDL: Unsupported DB release level <0xdb_release_level> The internal DB release level is not recognized by UDB Capture. This value is not the DB2 version, but is associated with it. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDL: UDB DB database_name; PART partition_number; LSN log_sequence_number; rc=PWX_return_code; error processing log record The UDB log reader detected an error in log record. This message identifies the record in error. The system returns an error to the calling software. Contact Informatica Global Customer Support. DB2 API db2ReadLog returned a buffer that failed validity checking. records=number_of_records bytes=bytes The PowerExchange DB2 for Linux, UNIX, and Windows Log Reader received an error when validating the data in the buffer of log records returned by the DB2 API db2ReadLog routine. The Log Reader found unused records or bytes in the buffer. This message identifies the number of unused records and unused bytes. The DB2 control blocks that were used to read the log buffer are dumped for diagnostic use. Contact Informatica Global Customer Support.
552
DB2 API db2ReadLog data area data_area_name dump from location A dump of the DB2 control blocks or buffers that are used for reading the DB2 logs was taken from the specified location. DB2 log read processing continues. No response is required. control_block_field_name control_block_field_value control_block _field_value_description This message describes a control block field that is included a dump of the DB2 control blocks that are used for reading DB2 logs. The message includes the field name and value and an optional description of either the field or value. DB2 log read processing continues. No response is required. SNAPUPDT action partition partition_number The SNAPUPDT command of the DTLUCUDB utility has discovered that a partition was added or deleted from the database. This message appears for each partition added or deleted. Processing continues. No response is required. Capture catalog partition information matches database; no changes for capture catalog. SNAPUPDT found no difference between the capture catalog and the database; Processing continues. No response is required. Database catalog partition partition_number missing from Capture Catalog or Database While obtaining Capture Catalog partition information with database partition information, the partition that should contain the UDB Catalog could not be found. The program ends and reports the error. Contact Informatica Global Customer Support if the error persists. Capture catalog update bypassed since REPLACE=Y not specified DTLUCUDB did not update the capture catalog. Processing ends. No response is required. New partition: partition_number VTS: virtual_time_stamp is less than the Capture Catalog low VTS: virtual_time_stamp While adding a positioning entry for a new partition, the new partition's VTS value is less than the Capture Catalog's current low VTS value. It is expected that any VTS value for a new partition should be older than the VTS of when the Capture Catalog is created. The program ends and reports the error. Contact Informatica Global Customer Support if the error persists.
PWX-20000 to PWX-20999
553
PWX-20500 Explanation: User Response: PWX-20501 Explanation: System Action: User Response: PWX-20502 Explanation: System Action: User Response: PWX-20503 Explanation: System Action: User Response: PWX-20504 Explanation: User Response: PWX-20505 Explanation: User Response: PWX-20506 Explanation: System Action: User Response: PWX-20507 Explanation: System Action: User Response: PWX-20508 Explanation: System Action: User Response: PWX-20509 Explanation:
command_input The current command input line. No response is required. Invalid hex character (character) in parameter The parameter specified contained an invalid hex character. Processing ends. Correct the error. Then, run the request again. Odd number of hex characters in parameter The parameter specified contained an odd number of hex characters. Processing ends. Correct the error. Then, run the request again. No command specified No command was specified. Processing ends. Correct the error. Then, run the request again. Syntax for the UDB capture utility: First line of HELP output. No response is required. help_information Line of HELP output. No response is required. Command command_name complete The command's processing has completed without error. Processing continues. No response is required. API call function_name returned error error code. The UDB capture encountered an unexpected error when making an API call. The program ends and reports the error. Contact Informatica Global Customer Support if the error persists. parameter_name parameter must be specified A required parameter was not specified. Processing ends. Correct the error. Then, run the request again. parameter_name parameter requires parameter_name parameter One parameter requires the specification of a second parameter.
554
System Action: User Response: PWX-20510 Explanation: System Action: User Response: PWX-20511 Explanation: User Response: PWX-20512 Explanation: User Response: PWX-20513 Explanation: System Action: User Response: PWX-20514 Explanation: System Action: User Response: PWX-20515 Explanation:
Processing ends. Correct the error. Then, run the request again. Catalog activity detected at VTS virtual_time_stamp/partition_number LLSN hex_logical_log_sequence (please rerun) Catalog activity was detected at the LLSN indicated while a snapshot was being attempted. Processing ends. Prevent catalog activity and rerun. database keywords This message is informational. No response is required. Producing file 'file name' The utility produced the file specified in response to the command. No response is required. parameter_name parameter conflicts with parameter_name parameter One parameter conflicts with the specification of a second parameter. Processing ends. Correct the error. Then, run the request again. Pseudolog call call_name failed The utility encountered an error when calling the function listed. Processing ends. Correct the error. Then, run the request again. Capture catalog contains rows and REPLACE=Y not specified. While processing the SNAPSHOT command the utility detected existing rows in the capture catalog table and the REPLACE=Y keyword was not specified. Replacing the contents of the capture catalog can cause log data to no longer be accessible. Processing ends. If replacing the contents of the capture catalog is what is desired, specify the REPLACE=Y keyword and rerun. Otherwise, correct error and rerun. Note: Replacing the contents of a capture catalog can make log data inaccessible. This message displays supporting information for message PWX-20515. No response is required. Output file file name exists and REPLACE=Y not specified. REPLACE=Y required to replace existing file. No response is required. Invalid decimal character (character) in parameter The parameter specified contained an invalid decimal character. Processing ends.
PWX-20000 to PWX-20999 555
PWX-20516 Explanation: User Response: PWX-20517 Explanation: User Response: PWX-20518 Explanation: System Action:
User Response: PWX-20519 Explanation: User Response: PWX-20522 Explanation: System Action: User Response:
Correct the error. Then, run the request again. End of UDB log file reached End of file (EOF) encountered No response is required. UCUDB: Unable to allocate memory for object_name. Insufficient memory resources exist to perform the task. The task that encounters the error ends. Increase the memory resources available to the task. Contact Informatica Global Customer Support if the error persists. Partition partition_number VTS virtual_time_stamp_at_end_of_log (LSN_logical_sequence_number_at_end_of_log) has not advanced to SNAPSHOT end VTS ending_virtual_time_stamp After building a capture catalog, SNAPSHOT processing reads all logs to a common ending point. One partition's log has not advanced to the common ending point and this is odd. Processing continues. No response is required. terminator value reached reading UDB log file DTLUCUDB log processing ends. Either the Ending Log Sequence Number (ELSN) or Ending Virtual Time Stamp (EVTS) was reached. No response is required. UCUDB Internal error, prog=program_name, line=line_number, desc=description DTLUCUDB UDB Utility encountered an internal error in processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. db_element: db_element_value An aspect of the UDB DB is listed. No response is required. virtual_time_stamp value '' in error: reason Instance partition information is listed. No response is required. Error on file file name: operation Instance partition information is listed. No response is required. OS_description_of_file_error Description of error writing to file. No response is required.
PWX-20523
Explanation:
System Action: User Response: PWX-20524 Explanation: User Response: PWX-20525 Explanation: System Action: User Response: PWX-20527 Explanation: User Response: PWX-20529 Explanation: User Response: PWX-20538 Explanation: User Response: PWX-20539 Explanation: User Response:
556
PWX-20540 Explanation: User Response: PWX-20541 Explanation: User Response: PWX-20544 Explanation:
Begin LSN UDB_log_sequence_number selected for BVTS value The utility is using the LSN specified in the message as the value to begin reading the UDB log. No response is required. Type_of_UDB_log_sequence_information: UDB_log_sequence_information Informational Database log sequence information. No response is required. Unable to find partition partition_number LSN positioning entry in capture catalog for VTSTIME vts_time; rc = return_code For the input BVTS value, a starting LSN was not found in the capture catalog for the stated partition. The requested BVTS value must be within the scope of the capture catalog. Most likely the BVTS value is before the capture catalog was created. The command ends. Specify a BVTS value within the scope of the capture catalog. Partition number partition_number not part of DB database_name The specified partition is not part of the database. The command ends. Supply proper partition number. Error(s) encountered producing LOGPRT output Error(s) have been detected while producing LOGPRT output. The command ends. Look for earlier error messages relating to LOGPRT output. log_start_point is not greater than log_start_point End point (ELSN or EVTS) is not greater than specified (BLSN) or determined (from BVTS) start point. Processing ends. Correct the error. Then, run the request again. LOGPRT requires command_parameter or command_parameter to determine log read start point LOGPRT requires a start point in the log. Processing ends. Correct the error. Then, run the request again. Using default parameter_name=parameter_value The utility is using parameter_value as the value for the parameter parameter_name. No response is required. type default restart point: time_value This message indicates the default restart point before (old) or after (new) DTLUCUDB utility command UPDTDRP processing.
System Action: User Response: PWX-20545 Explanation: System Action: User Response: PWX-20548 Explanation: System Action: User Response: PWX-20550 Explanation: System Action: User Response: PWX-20551 Explanation: System Action: User Response: PWX-20552 Explanation: User Response: PWX-20555 Explanation:
PWX-20000 to PWX-20999
557
User Response: PWX-20558 Explanation: User Response: PWX-20559 Explanation: User Response: PWX-20560 Explanation: System Action: User Response: PWX-20563 Explanation: User Response: PWX-20569 Explanation:
No response is required. VTS precedes capture catalog start, substituting capture catalog start. The input VTS value is before the start of the capture catalog. The VTS of the start of the capture catalog is being substituted. No response is required. Partition partition_number LSN log_sequence_number optional_log_file The LSN (log sequence number) in a partition where to log reading begins for the input VTS. No response is required. Input VTS relationship_and_type Capture Catalog VTS capture_catalog_VTS_value The input VTS value is outside the bounds of the Capture Catalog. It is either below the low (or start) VTS or is it above the high VTS. Processing ends. Select a proper VTS and retry command. capture_catalog_special_entry_name capture_catalog_special_entry_value A Capture Catalog special entry is listed. No response is required. or specify one of the special VTSDT values 'EOC' or 'NOW' An invalid VTSDT value was entered. An error message indicating the format for an actual value precedes this message. This message includes the special values that might also be specified. The request fails. Correct input and rerun. CAPDS: Unable to allocate memory for object_name. Insufficient memory resources exist to perform the task. The task that encounters the error ends. Increase the memory resources available to the task. Contact Informatica Global Customer Support if the error persists. CAPDS: Unable to load module module_name, error_information. The UDB capture module could not load the UDB shared library. The program ends and reports the error. Verify that paths have been set up correctly. Contact Informatica Global Customer Support if the error persists. CAPDS: Unable to resolve function function_name in module module_name, error_information. The UDB capture module could not load the UDB shared library. The program ends and reports the error. Verify that paths have been set up correctly. Contact Informatica Global Customer Support if the error persists.
558
CAPDS: SQL API function_name returned error error code (error_code_desc), error_information. The UDB capture encountered an unexpected error when making a SQL API call. The program ends and reports the error. Contact Informatica Global Customer Support if the error persists. State=SQL_state, Code=SQL_code, Msg=SQL_message Information related to an SQL failure. Depends on specific message issued. Based on specific message issued. CAPDS Internal error, prog=program_name, line=line_number, desc=description UDB SQL processor encountered an internal error in processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. Capture catalog verification error, expected number_of_columns columns, found number_of_columns (table table_name) UDB SQL processor failed to verify the schema of the capture catalog table. The system returns an error to the calling software. Supply a capture catalog table name that has the correct schema. Capture catalog verification error, column column_name unknown (table table_name) UDB SQL processor failed to verify the schema of the capture catalog table. The system returns an error to the calling software. Supply a capture catalog table name that has the correct schema. Capture catalog verification error, column column_name wrong format (table table_name) UDB SQL processor failed to verify the schema of the capture catalog table. The system returns an error to the calling software. Supply a capture catalog table name that has the correct schema. Capture catalog verification error, column column_name not found (table table_name) UDB SQL processor failed to verify the schema of the capture catalog table. The system returns an error to the calling software. Supply a capture catalog table name that has the correct schema. CAPDS: UDB API function_name error apirc=error code The UDB capture encountered an unexpected error when making a UDB API call. The program ends and reports the error. Contact Informatica Global Customer Support if the error persists. State=SQL_state, Code=SQL_code, Msg=SQL_message Information related to an SQL based API failure.
PWX-20000 to PWX-20999
559
Depends on specific message issued. Based on specific message issued. CAPDS: At PARTITION statement partition_statement_number: PARTITION_NUMBERs do not ascend; dbconfig file = dump_file During CAPDS initialization using DUMPDIAG data, a PARTITION statement was read that did not have an increasing PARTITION_NUMBER. Source identifies where the catalog partition number and partition definitions came from. The task that encounters the error ends. Correct dbconfig.txt input. CAPDS: Catalog partition (partition_number) is not a defined partition. Source: source During CAPDS initialization, the catalog partition number did not match any of the defined partitions. Source identifies where the catalog partition number and partition definitions came from. The task that encounters the error ends. Correct input. CAPDS: DB2 environment variable not set: environment_variable_setting During CAPDS initialization, the DB2 environment variable was not found to be properly set. This setting is required. The task that encounters the error ends. Correct input. CAPDS: For Windows, CAPDS was unable to make the environment variable setting: environment_variable_setting During CAPDS initialization, the DB2 environment variable was not found to be properly set. On Windows, CAPDS tried to set the environment variable, but was unsuccessful. The task that encounters the error ends. Set the environment variable externally. CAPDS: UDB Fix Pack level found_fix_pack_level is below the minimum of minimum_fixpac_level During CAPDS initialization, the UDB Fix Pack level was insufficient. The task that encounters the error ends. Install the correct UDB Fix Pack. CAPDS: UDB Version found_version_level not supported During CAPDS initialization, the UDB Version was found to be improper. The task that encounters the error ends. Use supported UDB Version. CAPDS: Unrecognized SQL_DBMS_VER format: SQL_DBMS_VER_value During CAPDS initialization, SQL_DBMS_VER could not be parsed. The task that encounters the error ends. Please contact Informatica Global Customer Support for technical support.
560
PWX-20619 Explanation: System Action: User Response: PWX-20620 Explanation: System Action: User Response: PWX-20621 Explanation: System Action: User Response: PWX-20622 Explanation: System Action: User Response: PWX-20623 Explanation: System Action: User Response: PWX-20624 Explanation: System Action: User Response: PWX-20625
CAPDS: Specified DB db_name is remote The specified database is marked remote in the UDB database directory. The task continues. No response is required. CAPDS: Specified DB db_name not found in UDB database directory During CAPDS initialization, a database was specified that was not found in the UDB database directory. The task that encounters the error ends. Please contact Informatica Global Customer Support for technical support. CAPDS: Warning: UID user_ID does not have SYSADM or DBADM authority During CAPDS initialization, the specified user ID was found not to have the proper authority. Further processing likely fails. The task that encounters the error ends. Use a user ID with proper authority. CAPDS: Warning: DB db_name is not configured with archive logging During CAPDS initialization, a database was specified that did not have archive logging. The task that encounters the error ends. Configure database with archive logging. CAPDS: Codepage conversion error for nature_of_data data. (tgtlen=expected_max_length_of_data, newlen=new_length_of_data) Error during data translation. The task that encounters the error ends. Please contact Informatica Global Customer Support for technical support. CAPDS: No codepage info found for code_page_name No code page info could be found in PowerExchange for the code page. The task that encounters the error ends. Please contact Informatica Global Customer Support for technical support. CAPDS: No codepage translator found for source_code_page_name (source_PWX_internal_code_page_number) to target_code_page_name (target_PWX_internal_code_page_number) No codepage translator could be found in PowerExchange for the two code pages. The task that encounters the error ends. Please contact Informatica Global Customer Support for technical support. CAPDS: Copying nature_of_data_being_converted data, target area size is insufficient: srclen=source_data_length tgtlen=target_area_length Target area size found to be insufficient when copying data in codepages conversion routine. The task that encounters the error ends.
Explanation: System Action: User Response: PWX-20626 Explanation: System Action:
PWX-20000 to PWX-20999
561
User Response: PWX-20627
Please contact Informatica Global Customer Support for technical support. CAPDS: PWX codepage code_page_name (DB2 code page=code_page_number) has unexpected properties: min_char_size=minimum_character_size max_char_size=maximum_character_size is ascii: "Yes_or_No" Codepage has unexpected properties. Processing continues. Contact Informatica Global Customer Support with details. CAPDS: DB database_name platform is endian_type endian, local platform is endian_type endian Local platform endian use must match that of the db. Processing ends. Run on platform with like db endian use. Error -1651 indicates db server not capable of API function, server may not be DB2 LUW The UDB capture encountered an unexpected error when making a UDB API call. The program ends and reports the error. Contact Informatica Global Customer Support if the error persists. PseudoLog error: error_description Information related to a PseudoLog failure. Depends on specific message issued. Based on specific message issued. CAPDD: Unable to allocate memory for object_name. Insufficient memory resources exist to perform the task. The task that encounters the error ends. Increase the memory resources available to the task. Contact Informatica Global Customer Support if the error persists. API call function_name returned return_code The DB2 for Linux, UNIX, and Windows CAPI module encountered an unexpected return code from the call indicated. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDD Internal error, prog=program_name, line=line_number, desc=description A UDB capture module encountered an internal error in processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDD OP error LLSN=LLSN_hex_value SEQ=SEQ_value A UDB capture module encountered an error in processing data from the capture catalog. The LLSN and SEQ of the row are reported in this message. The specific error should be detailed in other messages.
Explanation: System Action: User Response: PWX-20628 Explanation: System Action: User Response: PWX-20629 Explanation: System Action: User Response: PWX-20699 Explanation: System Action: User Response: PWX-20700 Explanation: System Action: User Response:
562
The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDD OP parameters conflict parameter_name and parameter_name A UDB capture module encountered an error in processing data from the capture catalog. The system returns an error to the calling software. Contact Informatica Global Customer Support. CAPDM: Unable to allocate memory for object_name. Insufficient memory resources exist to perform the task. The task that encounters the error ends. Increase the memory resources available to the task. Contact Informatica Global Customer Support if the error persists. AM UTL command (command_text) has failed with RC=return_code The command processed by the UTL access method has failed. Processing ends. Review command text for errors. See other messages. AM UTL command starting: command_text The command processed by the UTL access method has started. No response is required. AM UTL command complete: command_text The UTL access method command has completed successfully. No response is required. Allocation: DDN: DD_name DSN: file_name File allocation message. No response is required.
PWX-20900 Explanation: System Action: User Response: PWX-20901 Explanation: User Response: PWX-20902 Explanation: User Response: PWX-20904 Explanation: User Response:
PWX-21000 to PWX-21999
PWX-21000 Explanation: System Action: User Response: PWX-21001 Explanation: System Action: User Response: No help can be given on empty string User has requested help for an empty string. The task ends. Correct the input and retry. Function not recognized. No help can be given. The function is not recognized. The task ends. Verify function name, correct and retry.
PWX-21000 to PWX-21999
563
PWX-21002 Explanation: System Action: User Response: PWX-21003 Explanation: System Action: User Response: PWX-21004 Explanation: System Action: User Response: PWX-21005 Explanation: System Action: User Response: PWX-21006 Explanation: System Action: User Response: PWX-21007 Explanation: User Response: PWX-21008 Explanation: System Action: User Response: PWX-21009 Explanation: User Response: PWX-21010 Explanation: System Action: User Response:
Empty Expression User has not entered an expression. The task ends. Enter required expression and retry. Invalid Negative Field Type field_type For the requested field type, the value cannot be negative. The task ends. Correct the input and retry. Leading space character not allowed in expression The expression cannot begin with a space. The task ends. Correct the input and retry. Unknown Field Type field_type The field type specified is invalid. The task ends. Enter correct field type and retry. Assignment to itself not allowed The expression name being used as a function parameter is the same as the expression itself. The task ends. Correct the function parameters and retry. Field Assignment assumed Field assignment assumed. No response is required. Field field_name not found The field specified is not recognized. The task ends. Verify the field name against the field list, correct and retry. Field Assignment ok The field assignment is okay. No response is required. This declaration field type field_type differs from function result field type field_type The function result type is incompatible with the expression declaration. The task ends. Either correct the declaration field type, or the function result type and retry.
564
Function function_name Result missing Field Type Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function_name Result missing pNullThisTime Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function_name Result missing pDataLength Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function_name Result missing ppData Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function_name Result missing BufferLength Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function_name Result missing Minimum BufferLength Actual_Length Actual Minimum_Length Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Text literal can only be used on declaration Inappropriate usage of a text literal. The task ends. Correct the input and retry. Text literal not allowed on Field type field_type A text literal cannot be used for the specified target field type. The task ends.
PWX-21000 to PWX-21999
565
User Response: PWX-21019 Explanation: System Action: User Response: PWX-21020 Explanation: User Response: PWX-21021 Explanation: System Action: User Response: PWX-21022 Explanation: User Response: PWX-21023 Explanation: System Action: User Response: PWX-21024 Explanation: System Action: User Response: PWX-21025 Explanation: System Action: User Response: PWX-21026 Explanation: System Action: User Response: PWX-21027 Explanation: System Action: User Response:
Correct the input and retry. Text literal length length exceeds field length length The length of the text literal exceeds the target field length. The task ends. Correct the input and retry. Text literal expression OK The text literal expression is okay. No response is required. Numeric literal can only be used on declaration Inappropriate usage of a numeric literal. The task ends. Correct the input and retry. Numeric literal expression OK The numeric literal expression is okay. No response is required. Left bracket not found Mismatch in number of left and right brackets. The task ends. Analyze the specified function and parameters, correct the input and retry. Function name exceeds maximum size Size Function name is too long. The task ends. Correct the input and retry. Function not recognized function Function name is not recognized. The task ends. Correct function name specification and retry. Function call last character not a closing parenthesis character The last character of the function call is not a closing parenthesis. The task ends. Correct the input and retry. Function received Number arguments but requires at most maximum Too few arguments were passed to the function. The task ends. Correct the input and retry.
566
PWX-21028 Explanation: System Action: User Response: PWX-21029 Explanation: System Action: User Response: PWX-21030 Explanation: User Response: PWX-21031 Explanation: System Action: User Response: PWX-21032 Explanation: System Action: User Response: PWX-21033 Explanation: System Action: User Response: PWX-21034 Explanation: System Action: User Response: PWX-21035 Explanation: System Action: User Response: PWX-21036 Explanation: System Action: User Response:
Function received Number arguments but requires at least Minimum Mismatch in number of left and right brackets. The task ends. Analyze the specified function and parameters, correct the input and retry. Previous declaration field type field_type differs from function result field type field_type The function result type is incompatible with the previous expression declaration. The task ends. Either correct the declaration field type, or the function result type and retry. FunctionCall Expression OK The function call expression is okay. No response is required. Invalid NULL argument Specification of a non-null argument is required. The task ends. Correct the input and retry. Invalid NULL final argument Specification of a non-null final argument is required. The task ends. Correct the input and retry. End of argument unexpected character character The character identified in the message is invalid. The task ends. Correct the input and retry. Argument argument not found One of the arguments specified cannot be found. The task ends. Correct the input and retry. Field field cannot be an argument on the same line as its declaration The field identified in the message is on the same line as its own declaration. The task ends. Do not use the declaration field name as an argument on the same line. Memory error Shortage of memory. The task ends. Possible internal error - contact Informatica Global Customer Support for technical support.
PWX-21000 to PWX-21999
567
PWX-21037 Explanation: System Action: User Response: PWX-21038 Explanation: System Action: User Response: PWX-21039 Explanation: User Response: PWX-21040 Explanation: System Action: User Response: PWX-21041 Explanation: System Action: User Response: PWX-21042 Explanation: System Action: User Response: PWX-21043 Explanation: System Action: User Response: PWX-21044 Explanation: System Action: User Response: PWX-21045 Explanation: System Action: User Response:
Last character of text literal not a closing quote character A text literal must end with a closing quote. The task ends. Correct the input and retry. Invalid Literal Text Literal. 1 quote character Invalid specification of a text literal. The task ends. Verify specification of text literals, correct the input and retry. Text literal expression OK The text literal expression is okay. No response is required. Literal numeric literal has more than 1 decimal Numeric literal has more than one period (.) The task ends. Correct the input and retry. Literal numeric literal has non numeric data Digit The specified literal has non-numeric characters. The task ends. Correct the input and retry. Literal numeric literal has a single minus sign and no digits A minus sign was used in the wrong position. The task ends. Correct the input and retry. Literal numeric literal not allowed on Field type field_type field_type The field type does not support a numeric literal. The task ends. Correct the input and retry. Literal numeric literal has a decimal point but scale =0 The expression has a zero scale, therefore cannot have a decimal point in a numeric literal. The task ends. Either specify a scale or remove decimal point and retry. Literal numeric literal has Non numeric data after conversion #2 After conversion the numeric literal contains at least one non-numeric character. The task ends. Verify the specification of the numeric literal, correct the input and retry.
568
Literal numeric field_name literal has number less than minimum Minimum The field specified has a value too low for its type. The task ends. Correct the input and retry. Literal numeric field_name literal has number greater than maximum maximum The field specified has a value too high for its type. The task ends. Correct the input and retry. Result name not found (by Find routine) The field name specified cannot be located. The task ends. Correct the input and retry. IDMS Owner Set name missing, expression Function requires the specification of an IDMS Owner Set name. The task ends. Specify an IDMS Owner Set name and retry. No help available on argument argument Maximum arguments maximum used by function No help is available for the argument specified. The task ends. Correct the input and retry. No help available on argument argument Not yet defined in help No help is available for the argument specified. The task ends. Correct the input and retry. Logic Error function - Invalid function number on entry, contact Informatica Global Customer Support Probable internal error. The task ends. Please contact Informatica Global Customer Support for technical support having noted the error message details. Invalid function number on entry Probable internal error. The task ends. Please contact Informatica Global Customer Support for technical support. Logic Error function - Fast function table invalid, contact Informatica Global Customer Support Probable internal error.
PWX-21000 to PWX-21999 569
The task ends. Please contact Informatica Global Customer Support for technical support. Fast function table invalid Probable internal error. The task ends. Please contact Informatica Global Customer Support for technical support. Expression function not valid for this access method The function specified is not valid for the access method. The task ends. Correct the function used and retry. Specified data type Result_Field_Type invalid for function The data type specified is not compatible with the function. The task ends. Either correct the function or the data type being used and retry. Invalid binary length specified for function, should be length The function specified requires a binary length compatible, as shown. The task ends. Either correct the function or the length being used and retry. which is in bad value list The function has returned a value that is in bad value list. The task ends. Correct the function or parameter specification and retry. which is not in good values list The function has returned a value that is not in good values list. The task ends. Correct the function or parameter specification and retry. Function function Result missing Field Type Argument not pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function Result missing Field Type Argument pre-allocated. A problem was encountered with an internal consistency check on the result set argument. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error.
570
CRX map needs to be refreshed. Sequence buffer (length) required (length) A problem was encountered with an internal buffer length. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. RestartLength (length) BufferLength (length) An internal problem occurred with the Data capture restart address. The task ends. Contact Informatica Global Customer Support with details. Unexpected field type Probable internal error. The task ends. Contact Informatica Global Customer Support with details. Field type unknown by GEN_GetFldTabFromId Probable internal error. The task ends. Contact Informatica Global Customer Support with details. Unknown Comparison Type=type Probable internal error. The task ends. Contact Informatica Global Customer Support with details. Function Copydata. Error on initializing foreign trim character. Buffer size=size. Error with foreign trim character when using Trim function. The task ends. Examine trim character specification, correct and retry. Function Copydata. Error on initializing foreign pad character. Buffer size=size. Error with pad character when using Trim function. The task ends. Examine pad character specification, correct and retry. Linkage linkage_type received number argument(s). Required less than number. The number of arguments passed to the CALLPROG routine is invalid. CALLPROG requires at least one and no more than 20 arguments passed to the external subroutine. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task.
PWX-21000 to PWX-21999
571
Linkage linkage_type received number argument(s). Required at least 1. The number of arguments passed to the CALLPROG routine is invalid. CALLPROG requires at least one and no more than 20 arguments passed to the external subroutine. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Linkage linkage_type received number argument(s). Required less than number. The number of arguments passed to the CALLPROG routine is invalid. CALLPROG requires at least one and no more than 20 arguments passed to the external subroutine. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Linkage linkage_type received number argument(s). Required at least 1. The number of arguments passed to the CALLPROG routine is invalid. CALLPROG requires at least one and no more than 20 arguments passed to the external subroutine. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Supported values = L (left), R (Right), B (Both), space (Both). The message shows available values for the attribute Associated messages include 21082 that shows problem attribute and PWX-02603 that identifies the problem E Field. The task ends. See message PWX-21082. Function function Unexpected RC=return_code from Conversion function. While processing the function, an unexpected return code was received from the subroutine. The task ends. Contact Informatica Global Customer Support, specifying the function being performed at the time of the error. Function function does not support direction argument 2 value of value. The specified function does not support a particular attribute value. For example, function CALLPROG does not support more than 20 arguments. Function CALLPROG only supports particular linkage types depending on which operating system it is being run on. Associated messages include 21080 that shows available values for the attribute, and PWX-02603 that identifies the problem E Field. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task.
572
Function function. Error translating foreign encoded CHAR/VARCHAR field before conversion. A User-defined field is involved in a conversion between a numeric field and a CHAR or VARCHAR field on a file where the code page is foreign to the platform, and a problem occurred during the code page translation process. The task ends. Verify that the data is actually in the code page specified in the map properties. Function function. Error translating foreign encoded CHAR/VARCHAR field after conversion. A User-defined field is involved in a conversion between a numeric field and a CHAR or VARCHAR field on a file where the code page is foreign to the platform, and a problem occurred during the code page translation process. The task ends. Verify that the data is actually in the code page specified in the map properties. Function function does not support Arguments passed to external subroutine of value. The specified function does not support a particular attribute value. For example, function CALLPROG does not support more than 20 arguments. Function CALLPROG only supports particular linkage types depending on which operating system it is being run on. Associated messages include PWX-21086 which shows available values for the attribute, and PWX-02603 which identifies the problem E Field. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task. Supported Max Arguments passed to external subroutine = Number. The message shows maximum values for the attribute Associated messages include 21085 which shows problem attribute and PWX-02603 which identifies the problem E Field. The task ends. See message PWX-21085. Supported Linkage types on this platform = platform. The message shows available values for the attribute Associated messages include PWX-21088 that shows problem attribute and PWX-02603 that identifies the problem E Field. The task ends. See message PWX-21088. Function function does not support Linkage type of value. The specified function does not support a particular attribute value. For example, function CALLPROG does not support more than 20 arguments. Function CALLPROG only supports particular linkage types depending on which operating system it is being run on. Associated messages include PWX-21087 that shows available values for the attribute, and PWX-02603 that identifies the problem E Field. The task ends. Locate the problem E Field by using message PWX-02603. Correct the E Field using the Navigator, save the data map, send it to the remote node and rerun the task.
PWX-21000 to PWX-21999
573
Argument argument not found in record record_name The argument name was not located in the record. The task ends. Verify argument name, correct the input and retry. Argument argument not found in table table_name The argument name was not located in the table. The task ends. Verify argument name, correct the input and retry. Argument argument not found in runtime table The argument name was not located in the runtime table. The task ends. Verify argument name, correct the input and retry. Argument argument not found context type context_type The argument name was not located. The task ends. Verify argument name, correct the input and retry. Single-quote not allowed in a function argument unless enclosed in single-quotes. A single-quote is only allowed in literals for which the first and last characters are also single-quotes. Single-quote characters in the middle of a literal must be escaped by prefixing with an additional single-quote. For example, COPYDATA('Peter''s dog',F1). The task ends. Correct the argument and retry. Incorrect usage of single quote characters in a text literal. Text literals must be enclosed by a single-quote character in the first and last positions. If a single-quote character is needed within the literal, it must be escaped by prefixing with an additional single-quote. For example, COPYDATA('Peter''s dog',F1). The system has detected a single-quote character that should terminate the literal and then has met unexpected characters following it. The task ends. Correct the argument and retry. CAPXRT close of incomplete run (no Extract end time) The CAPXRT extraction did not reach a normal close. See the associated messages. See the associated messages. Incomplete CAPXRT run. Current buffer last flushed at time The last data push was at the stated time. See the associated messages. Current buffer : Total commits since flush = number of commits The message shows the number of commits since the last flush.
System Action: User Response: PWX-21400 Explanation: User Response: PWX-21401 Explanation: User Response: PWX-21402 Explanation:
574
User Response: PWX-21403 Explanation: User Response: PWX-21404 Explanation: User Response: PWX-21405 Explanation: User Response: PWX-21406 Explanation: User Response: PWX-21407 Explanation: User Response: PWX-21408 Explanation: User Response: PWX-21500 Explanation:
See the associated messages. Current buffer : Total reads since flush = number_of_reads The message shows the number of reads since the last flush. See the associated messages. Current buffer: Last RC = last_return_code, Previous RC = previous_return_code The message shows the last return code and the one before. See the associated messages. Incomplete CAPXRT run. Previous buffer last flushed at time In the previous buffer, the last data push was at the stated time. See the associated messages. Previous buffer : Total commits since flush = number of commits In the previous buffer, the number of commits since the last flush. See the associated messages. Previous buffer : Total reads since flush = number_of_reads In the previous buffer, the number of reads since the last flush. See the associated messages. Previous buffer: Last RC = last_return_code, Previous RC = previous_return_code In the previous buffer, the last return code and the one before. See the associated messages. Datacom access error on Open. rc=return_code. flg=flag cd=CA_DATACOM/DB_Return_Codes irc=internal_return_code. An error occurred when opening a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide. The task ends. Contact Informatica Global Customer Support. Datacom access error on Initial Point. rc=return_code. flg=flag cd=CA_DATACOM/DB_Return_Codes irc=internal_return_code. An error occurred when performing the initial Point on a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide. The task ends. Contact Informatica Global Customer Support. Datacom access error on Point. rc=return_code. flg=flag cd=CA_DATACOM/DB_Return_Codes irc= internal_return_code. An error occurred when performing a Point on a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide.
PWX-21000 to PWX-21999
575
The task ends. Contact Informatica Global Customer Support. Datacom access error on Optimized Read. rc=return_code. flg=flag cd=CA_DATACOM/DB_Return_Codes irc= internal_return_code. An error occurred when performing an Optimized Read on a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide. The task ends. Contact Informatica Global Customer Support. Datacom access error on Sequential Read. rc=return_code. flg=flag cd=CA_DATACOM/DB_Return_Codes irc= internal_return_code. An error occurred when performing a Sequential Read on a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide. The task ends. Contact Informatica Global Customer Support. Datacom access error on Write. rc=return_code. flg=flag cd=CA_DATACOM/DB_Return_Codes irc= internal_return_code. An error occurred when performing a Write on a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide. The task ends. Contact Informatica Global Customer Support. Datacom access error on Close. rc=return_code. flg=flag cd=CA-DATACOM/DB_Return_Codes irc= internal_return_code. An error occurred when performing a Close on a Datacom database. The CA-Datacom/DB return codes and internal return code values can be looked up in the Datacom manuals, such as CA-DATACOM/DB Message Guide. The task ends. Contact Informatica Global Customer Support. Connection of name connname not found in configuration. An error occurred when attempting to retrieve a connection of the given name from the CAPI CONNECTIONS in the configuration. The task ends with associated messages. Investigate where the problem name was sourced, it might be an internal reference in the configuration or might be in the request. Find the inconsistency correct and retry. Connection of name connname not first attribute connattr expected CAPINAME. An error occurred when attempting to identify an internal connection related to the given connection name. The task ends.
576
User Response:
Investigate the configuration the connection identified should have a CAPINAME reference to another connection. If this looks correct contact Informatica Global Customer Support with the configuration. Connection for connname not found in configuration. reason. This gives the reason a lookup was invoked. The task ends with associated messages. Use this message to guide you back to where the lookup value came from. Connection of type in_type<capture_type> not found in configuration. An error occurred when attempting to retrieve a connection of the type from the CAPI CONNECTIONS in the configuration. The task ends with associated messages. Investigate where the problem type was sourced, it might be an internal reference in the configuration or might be in the request. Note that the transformation of in type to capture type is given to assist diagnosis. Find the inconsistency, correct and retry. Connection of internal name CAPINAME not found in configuration. An error occurred when attempting to retrieve a connection of the given internal name from the CAPI CONNECTIONS in the configuration. The task ends with associated messages. Investigate where the problem name was sourced, it is an internal reference in the configuration. Find the inconsistency, correct and retry. Connection selected Conn_name found from covr<Conn_Override> tag<registration_tag> type<Type_used> int<Internal_Request> method<Method_used>. This is an This message provides an audit trail. Connection selected is the result. Any of the following parameters might be omitted.

covr is the CONN_OVR parameter on the request. tag is a registration being extracted. type is the type of registration. int is TRUE if the internal connection was requested. method used shows the resource type that gave the connection. System Action: User Response: PWX-21711 Explanation: System Action: User Response: PWX-21720 Explanation: System Action: User Response: Processing continues. An audit trail needs no action, but might be useful to help understand product behavior. Parameter parameter_name is not valid with PROG=program_name The parameter specified is not valid with the selected program. Processing ends. Correct the invalid parameter and rerun DTLREXE. Error creating poolid pool_name, rc = return_code An attempt to create a unique memory pool name failed. Processing ends. Contact Informatica Global Customer Support with details.
PWX-21000 to PWX-21999
577
Error allocating memory for area_name, rc = return_code An attempt to allocate memory for the specified area failed. Processing ends. Contact Informatica Global Customer Support with details. Invalid DBCB for access method DBAM_EXEC An attempt was made to open a dbcb for access method DBAM_EXEC without first opening a connection. Processing ends. Contact Informatica Global Customer Support with details. Invalid DBCB for access method DBAM_EXEC An attempt was made to open a connection for access method DBAM_EXEC with an invalid dbcb. Processing ends. Contact Informatica Global Customer Support with details. Routine routine_name out of order An attempt was made to read the output from a submitted job, before the job was submitted. Processing ends. Contact Informatica Global Customer Support with details. Invalid value for value, reason description An attempt was made to read the results from DBAM_EXEC with an invalid array size. Processing ends. Contact Informatica Global Customer Support with details. Fault tolerance logging file file_name open error An attempt to open the specified file failed. The purpose of this was to log errors for reporting back issues tolerated by the process. Processing ends. Review the associated messages to establish a cause. Fault tolerance logging file file_name write error An attempt to write to the specified file failed. The purpose of this was to log errors for reporting back issues tolerated by the process. Processing ends. Review the associated messages to establish a cause. Fault tolerance logging file invalid prefix <prefix> The reject file prefix supplied results in the creation of a reject file name with an invalid length. Processing ends. Correct the reject file prefix.
578
PWX-23000 to PWX-23999
PWX-23010 Explanation: System Action: User Response: PWX-23011 Explanation: System Action: User Response: CAPX Capture: Unexpected token found by Connect process. This is an internal error. Processing ends. Contact Informatica Global Customer Support with details. CAPX Capture: Unable to allocate memory for <object>. PowerExchange could not allocate memory for the specified object. Processing ends. Increase the amount of memory available to the process, then restart the process. Message PWX-00904 provides details about the amount of memory that was requested. CAPX Capture: WARNING: Unrecognized attribute:value keyword:value passed to CAPX Capture interface. An unknown keyword was found in the CAPI_CONNECTION (TYPE=CAPX) statement in the DBMOVER configuration file. CAPX Capture ignores the keyword and continues. To get rid of the warning, edit the DBMOVER configuration file and remove the offending keyword. CAPX Capture: Invalid extended connection value <value> for attribute <attribute>. An unknown value was passed for a connection override of a CAPX or CAPX-type CAPXRT capture. Processing ends. Contact Informatica Global Customer Support with details. CAPX Capture: WARNING: Unrecognized override:value <Override_name:Override_value> passed to CAPX Capture interface. CAPX Capture received an unknown override parameter from its caller. CAPX Capture processing continues. Contact Informatica Global Customer Support with details. CAPX Capture: Missing condense instance. CAPX Capture requires a condenser instance value to determine what set of condense files to capture from. The instance value was not provided. Processing ends. Specify the condense instance value from which you wish to capture in the appropriate location in the PowerCenter session. Optionally, you can provide the instance value in the DFLTINST keyword of the CAPI_CONNECTION TYPE=CAPX statement in the DBMOVER configuration file. CAPX Capture: Missing condense image type (BA, AI, or TU). CAPX Capture requires the output image format you desire. The value was not provided. Processing ends. Specify the output image format in the appropriate location in the PowerCenter session.
PWX-23000 to PWX-23999 579
CAPX Capture: Missing condense file type (Full or Partial). CAPX Capture requires the condense file type. The value was not provided. Processing ends. Contact Informatica Global Customer Support with details. CAPX Capture: Internal error: function_name could not find a platform token. Storage common to the PowerExchange CAPX Capture modules was lost. Processing ends. Contact Informatica Global Customer Support with details. CAPX Capture: Internal error: function_name found an invalid eyecatcher <data_value_byte_1data_value_byte_2data_value_byte_3data_value_byte_4> in the platform token. Storage common to the PowerExchange CAPX Capture modules was lost or corrupted. Processing ends. Contact Informatica Global Customer Support with details. CAPX Capture: Platform token Version mismatch in function_name. Received: Version.release.modification_level. patch_level. Expected: Version.release. modification_level.patch_level. A version level mismatch was discovered in PowerExchange CAPX Capture. Processing ends. This is most likely caused by incorrect settings in the environment variables. Ensure that the path and shared library path variables are set to point to the same PowerExchange binaries. A secondary cause of this message could be an incomplete or failed installation of the PowerExchange software. CAPX Capture: Unable to initialize Windows network processing. Rc =WSAStartup_return_code. Windows network initialization failed. Processing ends. This is most likely caused by a missing winsock dll, a bad PATH environment variable, or system instability. Fix the problem and retry. CAPX Capture: You must run a condense for instance condense_instance_name before generating a default restart point. CAPX Capture cannot generate a default restart point to begin processing until a condense process is run for the specified condense instance. Processing ends. This is most likely caused by attempting to run the PowerExchange DTLUAPPL program to create an initial restart point. CAPX CAPI cannot create this restart point unless condense files exist for the condense instance from which you are attempting to capture. Run a condense process for the instance and retry.
Explanation: System Action: User Response: PWX-23020
580
PWX-23023
CAPX Capture: Unable to open/read/close CDCT/condense file file name. return_code1/return_code2/return_code3 = <PWX_return_code/platform_dependent_return_code/ platform_dependent_reason_code>. CAPX Capture cannot open the specified file. Processing ends. Use any prior error messages and the platform-dependent return/reason codes to determine what the problem might be. Fix the problem and retry. CAPX Capture: Internal CDCT condense option discrepancy for condense file condense_file_name. CAPX Capture found CDCT entries for the specified file that contain different condense options. Processing ends. Two PWX-23025 error messages follow this message, detailing the error. Collect the information and contact Informatica Global Customer Support. CAPX Capture: current/new CDCT entry registration tag: registration_tag_name Condense option: {F(ull)|P(artial)}. This message describes the condense option found for a CDCT entry described in a prior message. Perform the actions described in any message that was emitted immediately prior to this message. CAPX Capture: Internal CDCT image type discrepancy for condense file condense_file_name. CAPX Capture found CDCT entries for the specified file that contain different image types. Processing ends. Two PWX-23027 error messages follow this message, detailing the error. Collect the information and contact Informatica Global Customer Support. CAPX Capture: current/new CDCT entry registration tag: <registration_tag_name> Image type: <AI/BA/TU/unknown:internal_numeric_image_type_value> This message describes the image type found for a CDCT entry described in a prior message. Perform the actions described in any message that was emitted immediately prior to this message. CAPX Capture: Sequence info discrepancy found in CDCT for condense file condense_file_name. The sequence info format in the condense file list does not match that passed to CAPX Capture. Processing ends. Ensure that the correct token files were used to start the capture session, and that you have not overlaid the PowerExchange CDCT file.
PWX-23000 to PWX-23999
581
CAPX Capture: Condense file file name does not match required file prefix <condense_file_prefix>. The condense file's prefix does not match that of others in the condense file list. Processing ends. This situation occurs when you attempt to capture from a group source session and the sources from which you are capturing are not part of the same condense instance, or, in the case of flexible condense, the sources are not part of the same condense group. CAPX Capture: Condense file file name condense type <F/P> does not match requested type <F/P>. The condense file's condense type (full or partial) does not match the condense type requested for this extraction. Processing ends. This situation occurs when you attempt to capture a source that was condensed with full condense processing and you are requesting that partial condense files be read for that source, or the source was condensed with partial condense processing and you are requesting that full condense files be read for that source. Make sure that you are requesting data from the correct capture instance. CAPX Capture: Condense file condense_file_name image type <AI/BA/TU/unknown>:<internal_numeric_image_type_value> does not match requested type <AI/BA/TU/unknown>:<internal_numeric_image_type_value>. The image types in the condense file do not match the image type requested for this extraction. Processing ends. This action happens if you attempt to capture a source that was condensed with after images only, but are requesting a BA- or TU-type extraction. Make sure that you are requesting data from the correct capture instance. CAPX Capture: End sequence of condense file condense_file_name is greater than begin sequence of file condense_file_name. The latest sequence number of the first condense file is greater than the earliest sequence number of the next file in the list of files to be processed. Processing ends. This situation occurs when you attempt to extract changes from multiple sources in different flexible condense groups. In a given extraction, you can only capture changes from a single condense instance or, in the case of flexible condense, from the same condense group. If you receive this message while you are attempting to move sources between condense groups, it is most likely because you did not correctly follow the necessary procedures. See the product documentation for information on the procedures necessary to successfully move sources between condense groups. CAPX Capture: Condense file condense_file_name name has an unexpected format: <detailed_description_of_error>. The condense file name is not of the expected format. Processing ends. This is most likely an internal error. Contact Informatica Global Customer Support.
PWX-23031
582
CAPX Capture: Source info for PowerExchange tag <registration_tag_name> not passed to CAPX Capture. The CAPX Capture caller failed to send any information to CAPX Capture for the specified capture registration. Processing ends. This is an internal error. Contact Informatica Global Customer Support. CAPX Capture: Unable to find source restart info for PowerExchange tag <registration_tag_name>. The CAPX Capture caller failed to send restart information to CAPX Capture for the specified capture registration. Processing ends. This is an internal error. Contact Informatica Global Customer Support. CAPX Capture: Condense file condense_file_name begins a new condense group for PowerExchange tag <registration_tag_name>. The CAPX Capture session detected that a source was moved to a new condense group while the session was processing changes from a different condense group. The process ends normally when all condense files for the current condense group have been processed. This is normal behavior. CAPX Capture cannot process changes from multiple condense groups in the same run. If you are moving sources between condense groups, see the product documentation for instructions. If you have only changed the file name prefix for an existing condense group, simply restart the session. CAPX Capture: No source filtering was requested, but a source filter list was passed. The CAPX Capture session detected that specific sources were requested along with a request to return data for all sources. Processing ends. This is an internal error. Contact Informatica Global Customer Support. CAPX Capture: Select timeout error return_code: <error_explanation> The CAPX Capture session issued a timed wait that failed. This is a warning message only. Processing continues. If this message is accompanied by other errors, then contact Informatica Global Customer Support. CAPX Capture: Unexpected record type "internal_record_type_code" sent to publishing algorithm. The CAPX Capture session attempted to process a record that was not a begin-uow, data, or end-uow record. Processing fails. This is an internal error. Contact Informatica Global Customer Support. CAPX Capture: Restart token has invalid default sequence information. CAPX Capture encountered an invalid restart token. A subsequent message prints out the token that was encountered.
PWX-23000 to PWX-23999
583
Processing fails. Verify the following: 1. Ensure that the PWX application name was not changed between runs of your PowerCenter session or PWX application. 2. If this is a new PowerCenter session or PWX application, make sure that you are not using a preexisting PWX application name. 3. Verify that the CAPI_CONNECTION keywords in your PWX DBMOVER configuration file are set up correctly. 4. Ensure that the correct PowerCenter token files are being used. 5. For PWX applications, ensure that the correct directories are being specified for the dbmover.cfg CAPT_XTRA and CAPT_PATH keywords.
CAPX Capture: Restart token has sequence information that is too short. CAPX Capture encountered an invalid restart token. A subsequent message prints out the token that was encountered. Processing fails. See the user response for message PWX-23040. CAPX Capture: Restart token has invalid sequence information. CAPX Capture encountered an invalid restart token. A subsequent message prints out the token that was encountered. Processing fails. See the user response for message PWX-23040. CAPX Capture: Restart token contains invalid instance name instance_name_from_restart_token, expects instance instance_name_from_session_parms. CAPX Capture encountered an invalid restart token. A subsequent message prints out the token that was encountered. Processing fails. See the user response for message PWX-23040. CAPX Capture: Restart token: An internal request was made to CAPX Capture to print out a restart token. A subsequent message prints out the token that was encountered. The system action depends on the reason the message was issued. This message might be issued either as an informational message, or to provide data in case of a previously-encountered error. If the session ends in error, scan the output for other error messages, and respond as is appropriate for those other messages. CAPX Capture: Socket allocation error <return_code>: <error_explanation> The CAPX Capture session could not allocate a communications socket. Processing ends. Using the system error description supplied by this message, determine and correct the cause of the error, and retry the process.
Explanation: System Action: User Response: PWX-23044 Explanation: System Action: User Response:
584
CAPX Capture: Sequence info in recreated file condense_file_name record <record_number> greater than expected. CAPX Capture detected a non-warm condense restart. The last record that CAPX Capture processed was not recaptured by the condense process. CAPX capture processing ends. This can happen when Condense is cold-started while a CAPX capture session is still active. Cold-starting Condense usually means you must rematerialize the targets. To keep the targets safe, CAPX Capture ends if it encounters this problem. If required, rematerialize the targets and restart the CAPX Capture session. If you do not need to rematerialize, simply restart the CAPX Capture session. CAPX Capture: Possible CDCT mismatch for file condense_file_name. CAPX Capture could not open a condense file that was cataloged in the CDCT. CAPX capture processing ends. This is most likely a mismatch between the CDCT and the directory containing the condense files. This can happen if you manually delete condense files outside of the control of the condense process. Verify that the file specified in the error message actually exists. If the file exists, see the prior message that describes the file open error and fix the problem. If the file does not exist, try restarting the Condense process. If, after the Condense process is fully restarted, the problem still exists, consider attempting to restore the file, the CDCT, and/or the CCT. If the problem still exists, contact Informatica Global Customer Support. CAPX Capture: Cannot determine correct current condense file. CAPX Capture could not determine the correct current condense file because none of the sources being processed by the current session have entries in the CDCT. The CAPX Extraction process waits for a Condense file switch before it starts to extract changes. This can happen either during Condense cold start or after CDCT maintenance ages off all CDCT entries pertaining to the sources being processed by the current PWX or PWC session. This is a normal condition. The CAPX Extraction process waits for a Condense file switch, and then proceed to extract data. CAPX Capture: Cannot determine correct current condense file. Sources belong to different groups: file_prefix_for_group1 - file_prefix_for_group2 CAPX Capture could not determine the correct current condense file because the sources being processed by the current session contain CDCT entries that point to different Condense sessions or different Flexible Condense groups. The CAPX Extraction process waits for a Condense file switch before it determines whether this is an error. This situation occurs when sources are moved between Condense groups. If this is the case, the CAPX Extraction process begins extracting changes at the next Condense file switch. If sources have not been moved, an error message is issued at the next Condense file switch indicating that sources are not in the same flexible condense group. If this occurs, follow the instructions contained in the appropriate PowerExchange CDC guide to recover from the error. CAPX Capture: Fsync for file <file_name> failed. Return code = <system_return_code>: <reason_for_failure> CAPX capture failed to synchronize records to the specified file. The extraction process fails.
PWX-23000 to PWX-23999
585
User Response:
Fix the problem described in the message and restart the extraction process. This problem usually indicates an I/O error. Parsing not supported for code page code_page_number (code_page_name) An attempt was made to parse data in a multibyte code page for which there is no support for examining each character one at a time. This error is typically generated when doing a DTLDescribe request with escape and wild card processing, or accessing metadata. Processing aborts. Verify the SQL page in the configuration file. It is possible to parse all fixed width code pages, EBCDIC mixed width code pages containing 0E/0F shift bytes, ASCII mixed width code pages prefixed by starter bytes and UTF-8. It is not possible to parse code pages such as ISCII, ISO-2022, compression and email code pages. If a multibyte SQL code page is needed, then UTF-8 should be used on ASCII platforms and an appropriate EBCDIC mixed width code page on EBCDIC platforms. 'ICU_error_code' converting from source CP to intermediate UNICODE. ICU has reported an error, ICU_error_code, when converting characters from the source code page to the intermediate Unicode. This is the first part of two-step process: Convert from source to intermediate Unicode, and then from intermediate Unicode to the target code page. Common error codes include:
U_FILE_ACCESS_ERROR. Code page converter is missing. U_INVALID_CHAR_FOUND. Typically character not present in target. U_TRUNCATED_CHAR_FOUND. A multibyte character is incomplete. U_ILLEGAL_CHAR_FOUND. Corrupt source data. U_BUFFER_OVERFLOW_ERROR. Target buffer is not big enough. System Action: User Response: Processing aborts. Consult the ICU web site for the meaning of the ICU error code. To correct the problem, use the other error messages, verify that the correct code pages are being used and that the data is valid. 'ICU_error_code' converting from intermediate UNICODE to target CP. ICU has reported an error when converting characters from Unicode to the target code page. This is the second part of two-step process (converting from source to intermediate Unicode, and then from intermediate Unicode to the target code page). Processing aborts. Consult the ICU web site for the meaning of the error. Using the other error messages, verify that the correct code pages are being used and that the data is valid. 'ICU_error_code' converting both to and from UNICODE. ICU has reported errors when converting characters both ways (from the source code page to Unicode and from Unicode to the target code page). Processing aborts. Consult the ICU web site for the meaning of the error. Using the other error messages, verify that the correct code pages are being used and that the data is valid. Bytes number to number of data: data Provides additional information about a conversion error. Single-byte characters that are not control characters are displayed using this message.
586
The system sends a return code and message to the calling program. Collect as much information as possible about the error and contact Informatica Global Customer Support. Bytes number to number of data: data Provides additional information about a conversion error. Multibyte characters or not control characters are displayed in hex using this message. Processing aborts. Collect as much information as possible about the error and contact Informatica Global Customer Support. Unable to convert to Unicode at offset offset source characters: data Specifies the hex of source characters that cannot be converted to Unicode. Processing aborts. Using associated error messages, determine whether the data is invalid or the wrong source code page is being used. Unable to convert to target code page at offset offset Unicode characters: data Specifies the hex of a Unicode 16 bit integer that cannot be converted to the target code page. Processing aborts. Using associated error messages, determine whether the data is invalid or the wrong source or target code page is being used. First problem Unicode character: name Specifies the name of the first problem Unicode character that failed conversion and was reported in a PWX-23507 message. Processing aborts. Using associated error messages, determine whether the data is invalid or the wrong source or target code page is being used. Invalid UTF8 lead byte at position position value value An invalid UTF8 lead byte was met during parsing. Valid lead bytes lie the range x'00' to x'7F' or have the first 2 or 3 bits set (X'Cx', x'Dx'). Processing aborts. Using associated error messages, determine whether the data is invalid or the wrong source or target code page is being used. Error initializing translator for column column An error was met when initializing the control structure used to translate between a source and target code page for the specified column. Processing aborts. See the to diagnose associated messages for the reason. Error error opening a converter for code page name An error was met when opening an ICU converter for the name code page. Processing aborts.
PWX-23000 to PWX-23999 587
User Response:
The ICU data library might not contain the required code page. Verify that the ICU data library shipped for PowerExchange is in the correct place on the path. Use ICUCHECK to see the full list of code pages. ICU data directory already set to existing_name and cannot be changed to new_name. The ICU data directory has already been set to the specified directory that is different to the requested one using a case sensitive comparison. It is not possible to change it to a different directory in the same run unit. Processing continues. The system ignores the value in the configuration file ICUDATADIR parameter and looks for code page CNV files in first directory that was set by an earlier caller that was not PowerExchange. Set the ICUDATADIR parameter to be the same as the existing name and copy the code page CNV files to this directory. Error calling routine routine_name. Return code return_code. Error description description. An ICU error was returned from the specified routine. Processing ends. Contact Informatica Global Customer Support.
System Action:
User Response:
PWX-24000 to PWX-24999
PWX-24000 Explanation: User Response: PWX-24001 Explanation: User Response: PWX-24002 Explanation: User Response: PWX-24003 Explanation: System Action: User Response: Retrieve IDMS Logs - location loc cfg_dir cfg_dir log_dir log_dir restart restart DTLRLOGS application start message recording basic configuration details. No response is required. Retrieve IDMS Logs - start time start_time - end time end_time Records the start and end times of an invocation of the dtlrlogs application. No response is required. Retrieve IDMS Logs - cycles cycles retrieved file counts: cdc cdc, logs logs Records the number of cycles executed on the timer poll and the total number of files retrieved. No response is required. Application error, rc = rc The application has generated an error or received a failing result code from a support function. The application reports the error and closes down. Determine the cause by reference to the result code reported and if necessary collect evidence and report the failure to Informatica Global Customer Support. File details: Time time, from from to to - transferred rows rows bytes bytes Records details of the successful transfer of a file by the application. No response is required.
588
Filename file_name fails to open, rc = rc Records a failure during an operation to open a file. The application reports the error and closes down. Determine the cause by reference to the result code reported and if necessary collect evidence and report the failure to Informatica Global Customer Support. Error: Filename filename does not seem to be a CDCT, The CDCT file specified by the FILE parameter does not contain CDCT records. The system records a failure. Correct the parameter and restart. Error: Filename filename does not seem to be a Checkpoint, The CHKPT file specified by the FILE parameter does not contain Checkpoint records. The system records a failure. Correct the parameter and restart. Open Error: Filename filename, The file specified by the FILE parameter is incorrect. The system records a failure. Correct the parameter and restart. Error: Point for file filename fail rc return_code <return_code1-return_code2-return_code3> An error occurred during keyed access to file. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Error: Read on file filename fail rc return_code <return_code1-return_code2-return_code3> An error occurred during a file read operation. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Error Part index of tag<tag_text> is populated and part index is empty. The tag field is expected to be in sections and completed in turn. When a blank is found in the middle of the tag, it might indicate a keying error or an incomplete request. The system records a failure and stops processing. Correct the punctuation and rerun. Error Part index of key<tag_text> is populated and part index is empty. The key field is expected to be in sections and completed in turn. When a blank is found in the middle of the key, it might indicate a keying error or an incomplete request. The system records a failure and stops processing.
PWX-24000 to PWX-24999
589
Correct the punctuation and rerun. Error Part index of key<tag_text> is not in hexadecimal The specifed key field is not a hexadecimal value. The system records a failure and stops processing. Correct the parameter. Valid values are from 0 through 9 and from A through F. Scope is not allowed with this type of run. A SCOPE parameter was specified on a request type where it is not applicable. The system records a failure and stops processing. Remove the SCOPE parameter or correct the request to the resource required. Error Source missing for rebuild CHECKPOINT/SAVED_COPY required The requested REBUILD_CDCT requires an input file. The system records a failure and stops processing. Use the CHECKPOINT parameter to start from a checkpoint, or use the SAVED_COPY parameter if something was saved in an earlier run. Error Source duplicated for rebuild CHECKPOINT <checkpoint> and SAVED_COPY <saved_filename>. One only required The requested REBUILD_CDCT needs only one input file. The system records a failure and stops processing. Use the CHECKPOINT parameter to start from a checkpoint, or use the SAVED_COPY parameter if something was saved in an earlier run. Error file for SAVE_COPY <save_filename> and SAVED_COPY <saved_filename> both present. One only required The requested REBUILD_CDCT needs to know the run type, these are mutually exclusive. The system records a failure and stops processing. Use the CHECKPOINT parameter to start from a checkpoint, or use the SAVED_COPY parameter if something was saved in an earlier run. Open for file filename fail rc return_code <return_code1-return_code2-return_code3> An error occurred during a write operation. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Error open of Saved file filename fail rc return_code <return_code1-return_code2-return_code3> An error occurred during an open of a saved file. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun.
PWX-24127 Explanation: Explanation: System Action:
590
Error open of Save file filename fail rc return_code <return_code1-return_code2-return_code3> An error occurred during an open of a saved file for creation. Records a failure and stops. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Write to file filename fail rc return_code <return_code1-return_code2-return_code3> An error occurred during a write operation. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Error:Read of saved file filename failed rc return_code <return_code1-return_code2-return_code3> An error occurred during a read of data from the saved file. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Warning: details A CDCT file could not be recreated, which might occur if the CDCT file was created by a "1st EndUOW after previous file switch" fileswitch. This is caused by pwxccl being in the middle of a large UOW such that a fileswitch is done then another is scheduled for the End of UOW so that the target gets the data and commit quickly. Further this is related to a table updated in the UOW but not in the time delimited by the preceding fileswitch and the EndUOW. So no data is present to regenerate the CDCT. The system continues processing. Review the output and repeat run if necessary. Error:Write to CDCT file filename failed rc return_code <return_code1-return_code2-return_code3> An error occurred during a write of data to the CDCT file. The system records a failure and stops processing. The return codes indicate associated messages to investigate. Correct the parameters and rerun. Error: Filename filename has both BA and AI CDCTs, Image parameter required Error about unusual image types, Both possible types exist in this system without a parameter we cannot derive an accurate value. The system records a failure. Provide an Image of BA or AI and restart. Warning: Filename filename has both BA and AI CDCTs Warns about unusual image types. Continues if a parameter exists. Verify that this is correct before resuming processing.
PWX-24000 to PWX-24999 591
Warning: Filename filename has type CDCTs but parm has ptype Warns about image types override which does not match checkpoints image type. Processing continues. Verify that this is correct before resuming processing. Warning: Filename filename has type CDCTs but data has Before Images Image types do not match data analysis. Processing continues. Verify that this is correct before resuming processing.
PWX-25000 to PWX-25999
PWX-25404 Explanation: User Response: PWX-25405 Explanation: System Action: User Response: Processing console program. command_string The named console program executes with the specified command and arguments. No response is required. Argument "argument" is required with command "command" The specified argument is required on the command but was not entered. Command processing fails. Enter the command again with the required argument.
PWX-30000 to PWX-30999
PWX-30000 Explanation: System Action: User Response: PWX-30001 Explanation: System Action: User Response: PWX-30002 Explanation: System Action: User Response: Improper attribute value: value While validating a PTRINF field, the attribute value specified is found to be improper. The field is rejected. Correct the attribute value. Specifying attribute is invalid. While validating a PTRINF field, an attribute is specified that is not allowed. The field is rejected. Remove the attribute Field field_number specifies attribute but reason While validating a PTRINF field, an attribute is specified but does not apply for the given reason. The field is rejected. Remove the attribute
592
Output group output_group_number projects no fields While requesting a mapping, an output group is found that does not project any fields. The set mapping request is rejected. Correct the mapping request. PWX error; rc=return_code description Error returned from PowerExchange function. The request is rejected. Correct the request PTRINF Internal error, prog=program_name, line=line_number, desc=description PowerExchange interface processor encountered an internal error in processing. The system returns an error to the calling software. Contact Informatica Global Customer Support. Variable length field field_number specifies field field_number as count but description While validating fields a field construction error is discovered. The field is rejected. Correct the field specification. Field is variable length but specifies no count field While validating fields a field construction error is discovered. The field is rejected. Correct the field specification. diagnostic_information One or more lines of diagnostic output. Diagnostic output is produced. No response is required. Field field_number uses field field_number as array bound but its type field_type is not acceptable While validating fields a field construction error is discovered. The field is rejected. Correct the field specification. Field field_number uses field field_number as array bound but it is out of range While validating fields a field construction error is discovered. The field is rejected. Correct the field specification.
PWX-30000 to PWX-30999
593
PWX-31000 to PWX-31999
PWX-31021 Explanation: System Action: User Response: PWX-31022 Explanation: System Action: User Response: PWX-31023 Explanation: System Action: User Response: PWX-31024 Explanation: System Action: User Response: PWX-31025 Explanation: Error initializing SSL An error occurred while initializing SSL. The task ends. Review the associated messages for the reason. Error initializing the context An error occurred while initializing the SSL context The task ends. Review the associated messages for the reason. Open secure socket failed An error occurred while opening the secure socket. The task ends. Review the associated messages for the reason. Peer authority check failed An error occurred while verifying the authority of the peer certificate. The task ends. Review the associated messages for the reason. SSL ERR_print_errors information. error_information Error information obtained from the SSL error stack using ERR_print_errors. The SSL error information in the error_information variable appears in the following format:
[pid]:error:[error_code]:[library_name ]:[function_name] :[reason_string]:[file_name]:[ line]:[optional_text_message]
System Action: User Response: PWX-31026 Explanation: System Action: User Response: PWX-31027 Explanation: System Action: User Response: PWX-31028 Explanation: System Action:
594
The task ends because of the error reported in an associated message. To diagnose the problem, see associated messages. SSL extra information. error_information Error information derived from various sources. The task ends because of the error reported in an associated message. To diagnose the problem, see associated messages. SSL_read problem. rc=return_code. Error=error error_description. Expected bytes. Read bytes bytes Error returned by the SSL_read API when reading data. The task ends. Look up the reason code in the SSL documentation. SSL_read error ignored while clearing socket prior to disconnect. Prior to closing sockets, all packets are read and error conditions might be flagged if the remote peer has already disconnected. Processing continues to the termination step.
User Response:
No response is required. This is an internal informational message and should never be displayed. SSL_write problem. rc=return_code return_code_description. Wrote bytes bytes Error returned by the SSL_write API when writing data. The task ends. Look up the reason code in the SSL documentation. Client timeout on SSL_connect after seconds seconds. The client was unable to connect to the PowerExchange Listener in the time limit specified. The task ends. Increase the number of seconds specified in the first value in the TIMEOUTS parameter in the configuration file. Listener timeout on SSL_accept after seconds seconds. The PowerExchange Listener was unable to connect to the PowerExchange Listener in the time limit specified. The task ends and the PowerExchange Listener resumes listening for fresh work. Increase the number of seconds specified in the first value in the TIMEOUTS parameter in the configuration file. Timeout on SSL_read after seconds seconds. Expected bytes. Received bytes bytes. An attempt to receive the given number of bytes on a SSL socket timed out before all the bytes were processed. The task ends. Look for an error at the other end of the connection. If there was no problem and then increase the number of seconds specified in the third value in the TIMEOUTS parameter in the configuration file. Timeout on SSL_write after seconds seconds. Expected bytes. Wrote bytes bytes. An attempt to write the given number of bytes on a SSL socket timed out before all the bytes were processed. The task ends. Look for an error at the other end of the connection. If there was no problem and then increase the number of seconds specified in the second value in the TIMEOUTS parameter in the configuration file. Can not read certificate chain file. Key=key. Error returned by API SSL_CTX_use_certificate_chain_file when reading the certificate file. The task ends. Look up the reason code in the SSL documentation. Can not read key file. Key=key. Error returned by API SSL_CTX_use_PrivateKey_file. The task ends.
PWX-31000 to PWX-31999
595
User Response: PWX-31036 Explanation: System Action: User Response: PWX-31037 Explanation: System Action: User Response: PWX-31038 Explanation: System Action: User Response: PWX-31039 Explanation: System Action: User Response: PWX-31040 Explanation: System Action: User Response: PWX-31041 Explanation:
Look up the reason code in the SSL documentation. Error verifying Certificate Authority locations. CA list=CA_list. CA path=CA_path. Error returned by API SSL_CTX_load_verify_locations. The task ends. Look up the reason code in the SSL documentation. SSL connect error. rc=return_code. Error=error error_description. Error returned by API SSL_connect that is executed on the client side. The task ends. Look up the reason code in the SSL documentation. SSL accept error. rc=return_code. Error=error error_description. Error returned by API SSL_accept that is executed on the server side. The task ends. Look up the reason code in the SSL documentation. Certificate does not verify. rc=return_code name. Error returned by API SSL_get_verify_result after opening a socket. The Peer certificate failed to verify. The task ends. Look up the reason code in the SSL documentation. Failed to get certificate from peer Error returned by SSL wrapper routine. The task ends. Look up the reason code in the SSL documentation. errno errno errno_description. The value of the errno integer and its description that provides information about an error reported in the IO system which SSL is used. The description is provided by strerror() in Windows and perror() on UNIX. The task ends because of the error reported in an associated message. See to diagnose associated messages. file file line line flags flags error error_number error_description. data data. The messages reports an error from the Open SSL error stack reporting mechanism. The task ends because of the error reported in an associated message. See to diagnose associated messages. rc rc from call_type indicates error_description Generally SSL APIs return 1 when successful. In failure situations, sometimes return code 0 indicates an minor error and -1 indicates a different major error. The task ends because of the error reported in an associated message. To diagnose the problem, see associated messages.
596
Certificate number. Start date start_date. End date end_date. Subject subject. Issuer issuer. This message provides information about a certificate when validation has failed. The task terminates because of the error reported in an accompanying error message. See the accompanying error message. Certificate number does not verify. rc=return_code "name". An error was returned by the OpenSSL API SSL_get_verify_result after opening a socket. The peer certificate could not be verified. The task ends. Check the return code in the OpenSSL documentation. SSL_connect failed. Check server log for errors. The attempt to connect to the server with SSL_connect() failed with error 5 (SSL_ERROR_SYSCALL). The server might have rejected the connection. The task ends. Check the server log for error messages. If the server is on Linux, UNIX, or Windows, check its PowerExchange log file. If the server is on z/OS, check the AT-TLS system log. If a problem exists with the client certificate, the information is logged on the server machine. SSL_accept failed. Check client log for errors. The attempt to accept the connection request with SSL_accept() failed with error 5 (SSL_ERROR_SYSCALL). The client might have rejected the connection. The task ends. Check the PowerExchange log file on the client machine for error messages. First SSL_read after connecting failed. Check server log for errors. The attempt to read from the server after connecting failed with error 5 (SSL_ERROR_SYSCALL). The server might have rejected the connection. The task ends. Check the server log for error messages. If the server is on Linux, UNIX, or Windows, check its PowerExchange log file. If the server is on z/OS, check the AT-TLS system log. First SSL_write after connecting failed. Check server log for errors. The attempt to write to the server after connecting failed with error 5 (SSL_ERROR_SYSCALL). The server might have rejected the connection. The task ends. Check the server log for errors. If the server is on Linux, UNIX, or Windows, check its PowerExchange log file. If the server is on z/OS, check the AT-TLS system log. First SSL_read after accepting a connection has failed. Check client log for errors. The attempt to read from the client after connecting failed with error 5 (SSL_ERROR_SYSCALL). The client might have rejected the connection. The task ends. Check the server log for error messages. If the server is on Linux, UNIX, or Windows, check its PowerExchange log file. If the server is on z/OS, check the AT-TLS system log.
PWX-31000 to PWX-31999 597
First SSL_write after accepting a connection has failed. Check client log for errors. The attempt to write to the client after connecting failed with error 5 (SSL_ERROR_SYSCALL). The client might have rejected the connection. The task ends. Check the PowerExchange log file on the client machine for error messages. Error setting GSK variable variable. rc=return_code. Reason=reason_code. An error occurred because one of the following attributes of the GSK API could not be set:
gsk_attribute_set_numeric_value gsk_attribute_set_buffer gsk_attribute_set_enum System Action: User Response: PWX-31072 Explanation: System Action: User Response: PWX-31073 Explanation: System Action: User Response: PWX-31074 Explanation: System Action: User Response: PWX-31075 Explanation: System Action: User Response: PWX-31076 Explanation: System Action: User Response: PWX-31077 Explanation: System Action: User Response:
598
The task ends. Look up the reason code in the SSL documentation. Error in gsk_secure_socket_close. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_secure_socket_close. The socket could not be closed. The task ends. Look up the reason code in the SSL documentation. Error in gsk_secure_socket_misc. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_secure_socket_misc. The socket could not be manipulated. The task ends. Look up the reason code in the SSL documentation. Error in gsk_environment_open. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_environment_open. The Environment could not be opened. The task ends. Look up the reason code in the SSL documentation. set env attributes failed Error returned by SSL wrapper routine. PowerExchange reports the error. Environment attribute set failed. Cfailed.heck parameters, retry. Error in gsk_environment_init. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_environment_init. Environment initialization failed. The task ends. Look up the reason code in the SSL documentation. Error in gsk_secure_socket_open. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_secure_socket_open. Secure socket open failed. The task ends. Look up the reason code in the SSL documentation.
Error in set fd attribute. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_attribute_set_numeric_value. Set FD attribute failed. The task ends. Look up the reason code in the SSL documentation. Error in set session type. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_attribute_set_enum. Set session type (client / server) failed. The task ends. Look up the reason code in the SSL documentation. Error in gsk_attribute_set_callback. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_attribute_set_callback. Set of the local IO callback routines failed. The task ends. Look up the reason code in the SSL documentation. Error in gsk_secure_socket_init. rc=return_code. Reason=reason_code. Error returned by GSK API gsk_secure_socket_init. Secure socket initialization failed. The task ends. Look up the reason code in the SSL documentation. Conversion error. Source Data not valid packed Error returned by conversion routine. An expected packed number is not a valid one. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Target address is zero Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Target length not 4 or 8 Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Source address zero Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Source length in digits invalid (less than zero or 31) Error returned by conversion routine.
PWX-31000 to PWX-31999
599
PowerExchange reports the error. Verify that the input data is correct. Conversion error. Source scale in digits invalid (less than zero or source len) Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Validate request is invalid (Should be 'Y' or 'N') Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Target scale in digits invalid (less than zero or target len) Error returned by conversion routine. PowerExchange reports the error Verify that the input data is correct. Conversion error. Unsigned result request invalid (it should be 'Y' or 'N') Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Unexpected overflow during conversion to packed decimal Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. No non-zero bytes found in packed decimal field (no sign) Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Return code or reason code fields not supplied Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Source data not valid zoned Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct.
600
Conversion error. Source value too large, before scaling Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Source value too large, when being scaled Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Source value too large, when being placed in target Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Conversion error. Generic error from MVS conversion routines Error returned by conversion routine. PowerExchange reports the error. Verify that the input data is correct. Threading not supported (reason: reason_code) - reverting to single threaded mode The PowerCenter session cannot use multithreaded processing. The specified reason code is one of the following values:

0. Unknown. 1. Parameters not supported. 2. Non-ordered processing not supported. 3. Only Group Source processing is supported. 4. Offload processing is required for threading. 5. Caller must manage restart tokens. 6. Only local mode processing supported. 7. Access Method not supported. 8. DB Request type not supported. 9. File format not supported. 10. Late initial binds (post-first read) not supported. System Action: User Response: The session runs in single-threaded mode. To suppress this warning, change the value of the Worker Threads attribute to 0 on the PWXPC application connection. For more information about PWXPC connection attributes, see PowerExchange Interfaces for PowerCenter. Threading: component encountered error return_code1/return_code2/return_code3 during process on thread threadID While running a PowerCenter session in multithreaded mode, a PowerExchange component, component, encountered an error. In the message text:
component is the component that encountered the error.
PWX-31000 to PWX-31999
601
return_code1, return_code2, and return_code3 are PowerExchange return codes or message IDs for the failure. process is the PowerExchange process that was running when the error occurred. threadID is the ID of thread thread_name.
The PowerCenter session fails. To diagnose the problem, review additional error messages logged in the PowerCenter session log or in the PowerExchange log on the PowerCenter Integration Service machine. For additional assistance, contact Informatica Global Customer Support. Timed out waiting for thread after time milliseconds Multithreaded processing timed out while waiting for thread. PowerExchange reports the error. No response is required. Thread thread_ID ended unexpectedly During processing for a request running in multithreaded mode, thread thread_ID ended unexpectedly. PowerExchange reports the error. To diagnose the problem, review additional messages in the PowerCenter session log and in the PowerExchange log on the PowerCenter Integration Service machine. Running request in threaded mode (worker threads: worker_threads, arraysize: arraysize, stagger: stagger, timeout after: timeout) A request is being processed in multithreaded mode. In the message text:

worker_threads is the Worker Threads attribute value on the PWXPC connection. arraysize is the PWXPC Array Size connection attribute value. stagger is the stagger value. timeout is the threading timeout value. System Action: User Response: Multithreaded processing continues. No response is required. For more information about the PWXPC connection attributes, see PowerExchange Interfaces for PowerCenter. Approximate total dynamic memory allocation for threaded-mode processing is mb MB This message displays the approximate total dynamic memory usage, mb MB, for multithreaded-mode processing. Multithreaded processing continues. No response is required. To modify memory usage, in PowerCenter, change the values of the PWXPC Worker Threads and Array Size connection attributes. For more information about the PWXPC connection attributes, see PowerExchange Interfaces for PowerCenter. PWX-31209 Explanation: System Action: Memory allocation failure (threading) - bytes bytes, file file, line line During multithreading processing, a memory allocation failure occurred. PowerExchange reports the error.
602
User Response:
To modify memory usage, in PowerCenter, change the PWXPC Worker Threads and Array Size connection attributes. For more information about these PWXPC connection attributes, see PowerExchange Interfaces for PowerCenter. PowerExchange home directory not found in LD_LIBRARY_PATH The PowerExchange home directory was not found in the LD_LIBRARY_PATH path. Multithreaded processing continues. Add the PowerExchange home directory to the LD_LIBRARY_PATH path. Then, restart the node. PowerExchange threading stats for last rows rows. Cycle (array) size is size rows. out out of array occurred. PowerExchange reports the performance of a multi-threaded session. Processing continues. No action required. Cycle time: pct% (avg: avg min: min max: max usecs) PowerExchange reports the performance of a multi-threaded session. Processing continues. No action required. IO time: pct% (avg: avg min: min max: max usecs) PowerExchange reports the performance of a multi-threaded session. Processing continues. No action required. Parse time: pct% (avg: avg min: min max: max usecs) PowerExchange reports the performance of a multi-threaded session. Processing continues. No action required. Extern time: pct% (avg: avg min: min max: max usecs) PowerExchange reports the performance of a multi-threaded session. Processing continues. No action required. Delay time: pct% (avg: avg min: min max: max usecs) PowerExchange reports the performance of a multi-threaded session. Processing continues. No action required. Offloading - Unable to contact Listener on remote system During of an offloaded request, connectivity to the remote system failed. This problem is usually caused by a network related problem such as an incorrect IP address. PowerExchange reports the error.
PWX-31000 to PWX-31999
603
Examine other log entries. Offloading and/or Threading may not be possible for this type of request For this type of request, offloading or threading might not be possible. Processing ends. Review previous error messages. If required, in the connection dialog box, set offload='N' worker threads=0 and rerun the request. PowerExchange performance settings: offload type: 'type', worker threads: threads (for connection am, mode mode) This message summarizes the performance settings used by this PowerExchange connection. Processing continues. No response is required. Offloading must be specified in PowerCenter connection dialog Offloading must be specified in the PowerCenter connection dialog box. Processing continues. Perform the following steps: 1. Remove any OFFLOAD settings from the configuration file for the PowerExchange Listener. 2. Remove any offloading setting from the PowerExchange data map. 3. Specify the offloading setting in the PowerCenter Connect to Repository dialog box.
Missing CAPI Connection for offload processing A CAPI connection statement is missing for offload processing. Processing ends. Add the missing CAPI connection statement to the PowerExchange configuration file on the client. Cached datamap retrieval failure During retrieval of a cached data map, an error occurred. The system displays a warning message and tries to continue processing by retrieving the data map directly. Contact Informatica Global Customer Support. Offloading/Threading is not supported for this type of request For this type of request, offloading and threading are not supported. Processing continues without offloading. To suppress this message, set offload='N' in the PowerCenter Connect to Repository dialog box. Request for optimization attributes from source who failed (rc return_code) A request for optimization attributes failed. Processing continues without using the offloading or threading performance settings. Contact Informatica Global Customer Support.

604
Duplicate network transmission sequence number seq is ignored A duplicate network transmission sequence number is ignored. Processing continues. Contact Informatica Global Customer Support. Async socket requires (TCPIP send buffer) n bytes. Increase TCPIP send buffer size or reduce APPBUFSIZE The asynchronous socket requires the specified number of bytes for the TCP/IP send buffer size. Processing ends. Perform one of the following actions:
Increase the TCP/IP send buffer size on the LISTENER statement in Power Exchange Listener DBMOVER configuration file. Reduce the value of the APPBUFSIZE parameter in the DBMOVER configuration file for the Power Exchange client. PWX-31517 Explanation: Datamaps will be retrieved from listener at location 'location' PowerExchange retrieves extraction maps for this connection from the PowerExchange Listener at the location specified in the Map Location attribute of the PWX CDC application connection. Processing continues. If the extraction map retrieval fails, verify that the Map Location attribute specifies the correct location for the extraction maps. Extraction maps reside at the PowerExchange Listener location where the change data is captured. Only specify a value for the Map Location attribute if you have used CDC offload processing with the PowerExchange Logger for Linux, UNIX, and Windows to recapture change data from a remote system where it was originally captured to PowerExchange Logger log files on Linux, UNIX, or Windows.
PWX-32000 to PWX-32999
PWX-32001 Explanation: System Action: User Response: PWX-32002 Explanation: System Action: User Response: Input SQL has a where clause but no from clause. The SQL does not contain a from clause. SQL processing ends. Correct the SQL statement. MVS table not on AS400. Database type should be AS4 and not DB2. An attempt was made to access an MVS system table from an AS400 system. Processing ends with a table not found error. If you are adding a capture registration on an AS400 system, ensure that the type is AS4, not DB2, in the registration group. Error creating poolid pool_name, rc = return_code An attempt to create a unique memory pool name failed. Processing ends.
PWX-32000 to PWX-32999
605
Contact Informatica Global Customer Support. Error allocating memory for area_name, rc = return_code An attempt to allocate memory for the specified area name failed. Processing ends. Contact Informatica Global Customer Support. Invalid DBCB for access method DBAM_DBO An attempt was made to open a DBCB for the DBAM_DBO access method before a connection was opened. Processing ends. Contact Informatica Global Customer Support. Invalid DBCB for access method DBAM_DBO An attempt was made to open a connection for the DBAM_EXEC access method with an invalid DBCB. Processing ends. Contact Informatica Global Customer Support with details. DB2 Offload: buffer length = length, rows in buffer (arraysize) = rows When DB2 offload processing is active, this message displays shows the actual buffer size required to hold the requested arraysize of data. Processing continues. No response is required. DB2 Offload: APPBUFSIZE = length, max rows in buffer (arraysize) = rows When DB2 offload processing is active, this message displays the maximum number of rows that fit in the application buffer. Processing continues. No response is required. DB2 Offload: DB2 Version must be V8 new function mode or above to use DB2 offload DB2 offload was requested for a DB2 subsystem running at a level previous to DB2 V8 new function mode. Processing ends. Do not use OFFLOAD=Y with DB2 subsystems previous to DB2 V8 new function mode. DB2 Offload: Required length length exceeds APPBUFSIZE app - increase APPBUFSIZE or reduce ARRAY_SIZE During DB2 offload processing, the configured application buffer was too small to contain the data. Processing ends. Perform one of the following actions:
Increase the application buffer size by setting the APPBUFSIZE parameter in the PowerExchange client configuration file. Reduce the ARRAY_SIZE specified on the PowerCenter connection dialog.
606
CDC OFFLOAD Error - Open connection failed with return code <return_code>. The CAPI offload module attempted to open a network connection and failed. Processing ends. To diagnose the problem, view diagnostic information in the local and remote target logs. CDC OFFLOAD Error - Open dependent connection failed with return code <return_code>. The CAPI offload module attempted to open a dependent network connection and failed. Processing ends. To diagnose the problem, view diagnostic information in the local and remote target logs. CDC OFFLOAD Error - Describe failed for SQL <SQL_string> with return code <return_code>. The CAPI offload module attempted to describe the parameter or data SQL and failed. Processing ends. To diagnose the problem, view diagnostic information in the local and remote target logs. Collect the information and contact Informatica Global Customer Support. CDC OFFLOAD Error - CAPI_CONNECTION <connection_name> not found in local configuration file. The CAPI offload module requires that the CAPI_CONNECTION statements for the process are defined in the local PowerExchange configuration file. Processing ends. Add the appropriate CAPI_CONNECTION statements to the local PowerExchange configuration file. CDC OFFLOAD Error - The CAPINAME parameter in CAPI_CONNECTION <connection_name> refers back to itself. The CAPINAME parameter in the CAPI_CONNECTION statement must refer to a different CAPI_CONNECTION. Processing ends. Correct the CAPI_CONNECTION statement in the local PowerExchange configuration file. CDC OFFLOAD Error - Unable to initialize parameter translator from local codepage <local_control_code_page> to remote codepage <remote_control_code_page>. While initializing the control structure used to translate parameters when communicating with the offload node, the CAPI offload module encountered an error. Processing aborts. To determine the reason for the error, review associated messages. CDC OFFLOAD Error - Unable to translate parameter from local codepage <local_control_code_page> to remote codepage <remote_control_code_page>. While attempting to translate a parameter when communicating with the offload node, the CAPI offload module encountered an error. Processing aborts. To determine the reason for the error, review associated messages.
PWX-32000 to PWX-32999
607
608
CDC OFFLOAD Error - Unable to send <object> to remote node. Serialization return code <return_code>. While serializing CAPI data to send to a remote node, the CAPI offload module encountered an error. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - DBAPI read failed with return codes return_code1/return_code2/return_code3. While serializing data to send to remote node, the CAPI offload module encountered an error. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Unknown parameter <parameter_name> passed to CAPI offload. The CAPI offload module received an unknown parameter. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Required parameter <parameter_name> missing. The CAPI offload module did not receive a required parameter. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Unexpected data encountered sending <object> to remote node. While sending CAPI data to a remote node, the CAPI offload module encountered unexpected data. Processing aborts. Contact Informatica Global Customer Support. CAPOFFLD Info - Initializing CAPI offload proxy. VRM <PWX_version> Build <build> Date <build_date>. This message is informational. Processing continues. No response is required. CAPOFFLD Info - Initializing CAPI offload stub. VRM <PWX_version> Build <build> Date <build_date>. This message is informational. Processing continues. No response is required. CDC OFFLOAD Error - Function <function_name> called with invalid dbcb number <dbcb_number>. An internal error occurred. Processing continues.
No response is required. CDC OFFLOAD Error - Module <module_name> line <line_number>: Insufficient memory resources available. Allocation request for <bytes> bytes failed. The task cannot be completed due to insufficient memory resources. The task that encounters the error ends. Increase the memory resources available to the task. If you cannot resolve the error, contact Informatica Global Customer Support. CDC OFFLOAD Error - Expected data not returned from offload node when sending <object>. Expected CAPI data was not returned from the offload node. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Expected data not received by offload node. Expected CAPI data was not received by the offload node. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Unrecognized request <request> received by offload node. The offload node received a processing request of an unknown type. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Unexpected data type <data_type> received while processing request <request> on offload node. The offload node received unexpected data for the request. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Required data type <data_type> not returned from subordinate CAPI at offload node. CAPI RC=<return_code>. The CAPI read on the offload node failed to retrieve the expected data. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Unexpected Record Type <record_type> returned from subordinate CAPI at offload node. The CAPI read on the offload node returned an unexpected record type. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Close failed for offload connection. DBAM RC=<return_code>. The CAPI offload module attempted to close the connection to the peer node and failed. Processing ends.
PWX-32000 to PWX-32999 609
User Response:
For more diagnostic information, view the local log or the log at the remote peer. Collect the information and contact Informatica Global Customer Support. CAPOFFLD Warning - Open task DBCB failed with return code <return_code>. During shutdown processing the attempt to communicate the shutdown to the remote peer failed. The task shuts down. To diagnose the problem, view diagnostic information in the local and remote target logs. CAPOFFLD Warning - Execute task DBCB failed with return code <return_code>. During shutdown processing, the attempt to communicate the shutdown to the remote peer failed. The task shuts down. To diagnose the problem, view diagnostic information in the local and remote target logs. CAPOFFLD Warning - End of data stream not received from peer task within in the allotted time (10 Seconds). During shutdown processing, the remote peer failed to return end of file. The task shuts down. To diagnose the problem, view diagnostic information in the local and remote target logs. CDC OFFLOAD Error - GenRestart read call returned an unexpected return code. RC=<return_code>. During genrestart processing, the read at the peer node encountered an unexpected condition. Processing ends. More diagnostic information might appear in the log locally or at the remote peer. Collect the information and contact Informatica Global Customer Support. CDC OFFLOAD Error - CAPI Connection definition for <source> not found local PowerExchange configuration file. Offload processing for CDC sources requires that CAPI connections be defined locally. Processing ends. Add the CAPI_CONNECTION statement to the local PowerExchange configuration file. CDC OFFLOAD Error - DBAPI presence call failed with return codes return_code1/return_code2/return_code3. While serializing data to send to the offload peer, the CAPI offload module encountered an error. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Set Timeout call failed with return code return_code. While serializing data to send to the offload peer, the CAPI offload module encountered an error. Processing aborts. Contact Informatica Global Customer Support.
PWX-32128 Explanation: Explanation: System Action: PWX-32129 Explanation: System Action: User Response: PWX-32130 Explanation: System Action: User Response:
610
CDC OFFLOAD Error - Required data type <data_type> not returned from offload peer. The serialization record did not contain the expected data. Processing aborts. Contact Informatica Global Customer Support. CDC OFFLOAD Error - Failed to serialize any data to buffers. Requested <bytes_requested>. Available <bytes_available>. The space required to serialize the record data exceeds the buffer size of the application. Processing aborts. Increase the APPBUFSIZE parameter in the PowerExchange configuration file. CAPI Error - Unknown parameter <parameter_name> passed to CAPI. An unknown parameter was passed to the CAPI module. Processing aborts. Contact Informatica Global Customer Support. The Service attempted to subscribe to a Command Handler a second time. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service can receive input commands from only one instance of a pwxcmd command handler. The pwxcmd command handler ignores the additional subscription. Processing continues. No response is required. The Command Handler encountered an internal error. The pwxcmd command handler encountered an internal error while processing a command. Depending on the error, processing might continue. No response is required. Data Model validation failed. The pwxcmd command handler received an invalid response from a PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service. The pwxcmd command handler discards the invalid response. Processing continues. No response is required. Command Handler initialization failed. The pwxcmd command handler failed to initialize. The pwxcmd command is not processed. Contact Informatica Global Customer Support. Provide information about the function being performed at the time of the error. The program attempted an invalid action. The pwxcmd command handler encountered an internal error while processing a command. Depending on the error, processing might continue.
PWX-32000 to PWX-32999
611
User Response: PWX-32508 Explanation: System Action: User Response: PWX-32530 Explanation: System Action: User Response: PWX-32531 Explanation: System Action: User Response: PWX-32532 Explanation:
No response is required. Unable to suppress signals: check POSIX(ON) is set. The system was unable to suppress signals. Processing continues. Verify that the PowerExchange Listener is running with POSIX(ON). A message was received on an unexpected communications channel. The pwxcmd command handler received a request from an unexpected source. The pwxcmd command handler ignores the request. Processing continues. No response is required. The command handler failed to add a reference to the PWXCMD connection. While processing a message, the pwxcmd command handler tried, but failed, to add a reference to a connection to keep the connection open. The pwxcmd command handler ignores the request. Processing continues. No response is required. An incoming connection contained an invalid Service type. Connection to Service service refused. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service received a request from a client to open a channel. However, the client specified an incorrect service type. The PowerExchange service rejects the channel request. Processing continues. In the local DBMOVER configuration file, review the CMDNODE parameter. Verify that the service type matches the service type of the PowerExchange service that is listening on the remote machine. Valid service types are LISTENER and CONDENSE. The Service name or type is not available to the PWXCMD command handler. PWXCMD input is disabled. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service tried to start a pwxcmd command handler but failed to provide the service name or service type. The pwxcmd command input is disabled. Processing continues. Verify that the configuration for the PowerExchange service is correct. The Service node is not available to the PWXCMD command handler. PWXCMD input is disabled. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service tried to start a pwxcmd command handler but did not find a SVCNODE entry that matched the service name in the DBMOVER configuration file. The pwxcmd command input is disabled. Processing continues. Verify that the configuration for the PowerExchange service is correct. Unable to extract the command from a data model. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service could not extract a recognized command from the data model that it received.
612
The pwxcmd command handler processing continues. No response is required. Command command not recognized. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service did not recognize the specified command. The pwxcmd command handler processing continues. No response is required. Failed to process PWXCMD command. See log for details. While processing a command, a PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service encountered an error. The pwxcmd command handler processing continues. For details, see the log for the PowerExchange service. Failed to convert a PWXCMD command to the local code page. A PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows Windows service encountered an error while processing a pwxcmd command. The pwxcmd command is ignored. Processing continues. For details, see the log for the PowerExchange service. Failed to convert a PWXCMD response from the local code page. While processing a response to a pwxcmd command, a PowerExchange Listener or PowerExchange Logger for Linux, UNIX, and Windows service encountered an error. The PowerExchange service discards the command response and returns an error. For details, see the log for the PowerExchange service. Command Handler communications initialization failed. An internal error occurred. The pwxcmd command handler processing ends. Contact Informatica Global Customer Support. Command Handler failed to create a connection to remote_service. The pwxcmd command handler failed to establish communication with the specified remote PowerExchange Listener, PowerExchange Condense, or a PowerExchange Logger for Linux, UNIX, and Windows service. The pwxcmd command handler processing ends. Review the local configuration for, and verify the status of, the remote PowerExchange service. Command Handler failed to create a channel to remote_service. The pwxcmd command handler failed to create a channel to the specified remote PowerExchange Listener, PowerExchange Condense, or a PowerExchange Logger for Linux, UNIX, and Windows service. The pwxcmd command handler processing ends. Verify the status of the remote PowerExchange service.
PWX-32000 to PWX-32999
613
Command Handler failed to send a message to remote_service. The pwxcmd command handler failed to send a message to the specified remote PowerExchange Listener, PowerExchange Condense, or a PowerExchange Logger for Linux, UNIX, and Windows service. The pwxcmd command handler processing ends. Verify the status of the remote PowerExchange service. Command Handler failed to receive a reply from remote_service. The pwxcmd command handler failed to receive a reply from the specified remote PowerExchange Listener, PowerExchange Condense, or a PowerExchange Logger for Linux, UNIX, and Windows service. The pwxcmd command handler processing ends. Verify the status of the remote PowerExchange service. No command node entry for service remote_service in config file. The pwxcmd command handler did not find a CMNNODE entry in the DBMOVER configuration file for the specified remote PowerExchange Listener, PowerExchange Condense, or a PowerExchange Logger for Linux, UNIX, and Windows service. Processing ends. Review the CMDNODE entries in the DBMOVER configuration file. Command Handler channel creation refused by remote_service. The specified remote PowerExchange Listener, PowerExchange Condense, or a PowerExchange Logger for Linux, UNIX, and Windows service refused to allow communication. Processing ends. In the local DBMOVER configuration file, review the CMDNODE entry and verify that the service type matches the service type of the service that uses the port on the remote machine, as specified in the SVCNODE entry in the remote DBMOVER configuration file.
PWX-33000 to PWX-33999
PWX-33001 Explanation: Please confirm cold start (Y/N) (DATACOM capture). Because restart information is not available from the PowerExchange Logger or PowerExchange Agent, the Datacom ECCR cannot warm start. PowerExchange prompts you to confirm or deny a cold start. The system waits for a reply. Enter Y to confirm the cold start. Enter N to stop the cold start. Cold start denied by operator (DATACOM capture). A reply of N was received in response to message PWX-33001. Datacom ECCR processing ends. No response is required.
614
Collector closing down (DATACOM Capture) The Datacom table-based ECCR is closing. Datacom ECCR processing ends. No response is required. Initialization failed, awaiting termination. (DATACOM capture) The Datacom table-based ECCR is closing. Datacom table-based ECCR processing ends. For additional information, review the ECCR output. Correct the error and run the request again. Read DATACOM Stream routine failed.Additional info: RC= return_code (DATACOM capture) During an attempt to access the Datacom streams, an error occurred. Datacom table-based ECCR processing ends. For more information, review the ECCR output. Correct the error and run the request again. Error writing to PowerExchange Logger. Additional info: text (DATACOM capture) During an attempt to write to the PowerExchange Logger, an error occurred. Datacom table-based ECCR processing ends. For more information, review the ECCR output. Correct the error and run the request again. Logsid specified in DTLCACFG does not match any in DTLCFG. (DATACOM capture) The LOGSID value in the Datacom ECCR configuration member does not match the LOGSID value in the DBMOVER configuration file. The DTLCACFG DD points to the Datacom ECCR configuration file, and the DTLCFG DD points to the DBMOVER configuration file. Datacom ECCR processing ends. For more information, review the ECCR output. Correct the error and run the request again. Latest time processed time Records processed number (DATACOM Capture) This message displays the last Datacom record that was processed and the number of records processed in this run. Datacom ECCR processing continues. No response is required. registration Inserts=number Deletes=number Updates=number This message displays the number of inserts, deletes, and updates that were performed for the specified registration during this run of the Datacom ECCR. Datacom ECCR processing continues. No response is required.
PWX-33000 to PWX-33999
615
DTLCCDCR shutting down having read to ...... The Datacom table-based ECCR is shutting down. Datacom ECCR processing ends. No response is required. Error Matching UOWs. Additional info: function_name No matching UOW found Returning with RC=return_code (DATACOM capture) A corresponding unit of work (UOW) was not found for an update. Datacom ECCR processing ends. For more information, review the ECCR output. Correct the error and run the request again. CCDCR: either STREAMID or MUF must be specified in the capture parms A STREAMID or MUF identifier must be specified in the Datacom ECCR configuration file. ECCR processing ends. Add the STREAMID or MUF parameter to the capture parameters. CCLWTR: Fatal error - CDCT Retention Control found new CDCT greater than active CDCT. Caller=caller_id. The CDCT Retention Control program encountered a fatal error. The CDCT file stores information about the PowerExchange Logger for Linux, UNIX, and Windows log files. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Invalid null sequence token encountered. Caller=caller_id. The PowerExchange Logger for Linux, UNIX, and Windows encountered a null sequence token, which resulted in a fatal error. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Invalid null restart token encountered. Caller=caller_id. The PowerExchange Logger for Linux, UNIX, and Windows encountered a null restart token, which resulted in a fatal error. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Incoming CAPI record length length exceeds the maximum length of max_length. The PowerExchange Logger for Linux, UNIX, and Windows received a record from CAPI that exceeds the maximum record length. Consequently, a fatal error occurred. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support.
616
CCLWTR: Fatal error - Invalid partial condense logic. Caller=caller_ID. The PowerExchange Logger for Linux, UNIX, and Windows encountered invalid partial condense logic, which resulted in a fatal error. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Checkpoint files do not contain an ERT record for registration tag=<tag_name>. The PowerExchange Logger for Linux, UNIX, and Windows did not find an ERT record in the ERT list for the specified registration tag. Consequently, a fatal error occurred. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Change record registration tag=<tag_name> does not match ERT1 registration tag=<tag_name> at pgm line The PowerExchange Logger for Linux, UNIX, and Windows did not find an ERT record in the ERT list for the specified registration tag. Consequently, a fatal error occurred. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Records found for a UOW but no partial condense file has been created. The PowerExchange Logger for Linux, UNIX, and Windows found change records for a UOW but could not log them because a condense file has not been created. Consequently, a fatal error occurred. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Invalid control block <control_block> encountered at pgm line The PowerExchange Logger for Linux, UNIX, and Windows encountered an invalid or corrupted control block, which resulted in a fatal error. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - No PowerExchange Logger log file name found for registration tag = <tag_name>. The PowerExchange Logger for Linux, UNIX, and Windows could not find the name of the log file for the specified registration tag. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support. CCLWTR: Fatal error - Retention lookup error <error> on PowerExchange Logger log file with file name=name. The PowerExchange Logger for Linux, UNIX, and Windows Retention lookup failed for specified condense log file, which resulted in a fatal error. PowerExchange Logger processing ends abnormally. Contact Informatica Global Customer Support.
PWX-33000 to PWX-33999 617
CCLCKPT: OPEN error on checkpoint file=<file_name>, RC1=return_code1, RC2=return_code2, RC3=return_code3. The specified checkpoint file failed to open. This message includes the return codes for the error. The PowerExchange Logger for Linux, UNIX, and Windows reports the error and ends. Review the PowerExchange message log to determine the cause of the OPEN error. Typically, return_code2 contains the reason for the error. CCLCKPT: CLOSE error on checkpoint file=<file_name>, RC1=return_code1, RC2=return_code2, RC3=return_code3. The specified checkpoint file failed to close. This message includes the return codes for the error. The PowerExchange Logger for Linux, UNIX, and Windows reports the error and ends. Review the PowerExchange message log to determine the cause of the CLOSE error. Typically, return_code2 contains the reason for the error. CCLCKPT: SRT_HI WRITE error on checkpoint file=<file_name>. RC1=return_code1, RC2=return_code2, RC3=return_code3. The PowerExchange Logger for Linux, UNIX, and Windows encountered a SRT-HI WRITE error when processing the specified checkpoint file. This message includes the return codes for the error. The PowerExchange Logger reports the error and ends. Review the PowerExchange message log to determine the cause of the SRT_HI WRITE error. Typically, return_code2 contains the reason for the error. CCLCKPT: SRT WRITE error on checkpoint file=<file_name>, RC1=return_code1, RC2=return_code2, RC3=return_code3. The PowerExchange Logger for Linux, UNIX, and Windows encountered a SRT WRITE error when processing the specified checkpoint file. This message includes the return codes for the error. The PowerExchange Logger reports the error and ends. Review the PowerExchange message log to determine the cause of the WRITE error. Typically, return_code2 contains the reason for the error. CCLCKPT: Checkpoint file deleted. File=file_name, RC=return_code, Erno=error_number. The specified checkpoint file was deleted. Because this message is informational and does not indicate an error, the error number is 0. No response is required. PWXCCL: Warning - DTLCACON will not be supported in future releases. Use the PWXCCL executable. The PowerExchange Condense DTLCACON executable will not be supported in PowerExchange releases later than 8.6.1 on Linux, UNIX, or Windows. On these platforms, DTLCACON is replaced by the PWXCCL executable for the PowerExchange Logger for Linux, UNIX, and Windows. PowerExchange Condense will continue to be supported on MVS and i5/OS. If you use PowerExchange 8.6.1 on Linux, UNIX, or Windows, migrate from PowerExchange Condense to the PowerExchange Logger for Linux, UNIX, and Windows. You must do so before you upgrade to a PowerExchange release later than 8.6.1.
User Response:
618
CCLWTR: Fsync for file <file_name> failed. Return code = <return_code>: <reason> An attempt to synchronize records to the specified file failed. This problem is usually caused by an I/O error. The PowerExchange Logger for Linux, UNIX, and Windows ends. Correct the problem described in the message and start the PowerExchange Logger for Linux, UNIX, and Windows again.
PWX-35000 to PWX-35999
PWX-35000 Explanation: User Response: PWX-35001 Explanation: REPORT FOR COMMAND command This message displays the heading of a PWXUSSL report. No response is required. SSL cipher list set to cipher_list This message displays the available cipher list. If you include the SSL_CIPHER_LIST statement in the DBMOVER configuration file, PowerExchange issues the SSL_CTX_set_cipher_list() OpenSSL command to set the cipher list when establishing an SSL connection. No response is required. number_of_ciphers available ciphers The message reports the number of ciphers returned by SSL_get_cipher_list(). If you include the SSL_CIPHER_LIST statement in the DBMOVER configuration file, PowerExchange issues the SSL_CTX_set_cipher_list() OpenSSL command to set the cipher list when establishing an SSL connection. No response is required. Ciphers Report for Hex Id, Strength and Version This message displays the heading of a PWXUSSL report. No response is required. sequence cipher_name hex id=hex_id strength=strength version=version This message displays the heading of a PWXUSSL report. No response is required. Ciphers Report for Key Exchange, Encryption, Signature and Message Authentification This message displays the heading of a PWXUSSL report. No response is required. sequence cipher_name Key Ex=key_exchange_type Enc=encryption_type Au=signature_type MAC=message_authentication_type This message displays the heading of a PWXUSSL report. No response is required.
User Response: PWX-35005 Explanation: User Response: PWX-35006 Explanation: User Response: PWX-35007 Explanation: User Response: PWX-35008 Explanation: User Response:
PWX-35000 to PWX-35999
619
PWX-35011 Explanation: User Response: PWX-35012 Explanation: User Response: PWX-35013 Explanation: System Action: User Response: PWX-35021 Explanation: User Response: PWX-35022 Explanation: User Response: PWX-35023 Explanation: User Response: PWX-35024 Explanation: User Response: PWX-35025 Explanation: User Response: PWX-35026 Explanation: User Response: PWX-35027 Explanation: User Response: PWX-35028 Explanation: User Response:
620
File contains number_of_certificates X509 certificates and number_of_subject_names subject names This message displays information about the contents of a certificate file. No response is required. Certificate number. Subject Name name This message provides information about a certificate. No response is required. Unable to load file filename using available INFORM types The certificate file could not be loaded using the OpenSSL INFORM type of PEM or DER. The application terminates. Contact Informatica Global Customer Support. Certificate number. Serial number. Version number. This message provides information about a certificate. No response is required. Valid from date time zone time_zone_code. Valid to date time zone time_zone_code. This message provides information about a certificate. No response is required. Subject name name This message provides information about a certificate. No response is required. Issuer name name This message provides information about a certificate. No response is required. Signature algorithm algorithm This message provides information about a certificate. No response is required. Public Key algorithm name. Size number bits. This message provides information about a certificate. No response is required. Subject and Issuer names are the same. (Self-certified) This message provides information about a certificate. No response is required. Certificate is not yet valid This message provides information about a certificate. No response is required.
PWX-35029 Explanation: User Response: PWX-35031 Explanation: User Response: PWX-35032 Explanation: User Response: PWX-35033 Explanation: User Response: PWX-35041 Explanation: System Action: User Response: PWX-35042 Explanation: System Action: User Response:
Certificate has expired This message provides information about a certificate. No response is required. ***** START OF RESULT SET FROM API X509_print_ex_fp ***** This message provides information about a certificate. No response is required. ***** END OF RESULT SET FROM API X509_print_ex_fp ***** This message provides information about a certificate. No response is required. Private key information data This message provides information about a certificate. No response is required. API call routine failed The named API, called by the PWXUSSL utility, failed. The PWXUSSL utility terminates. Contact Informatica Global Customer Support. API call routine returned return_code The named API, called by the PWXUSSL utility, failed. The PWXUSSL utility terminates. Contact Informatica Global Customer Support.
PWX-35000 to PWX-35999
621
622
CHAPTER 2
DTL_BMG003 to DTL_RPS105I

DTL_BMG003E to DTL_BMG101E: Datacom Low Level Metadata Retrieval, 623 DTL_DPL002I to DTL_DPL300I: Datacom MUF Real-time Log Processor, 624 DTL_DPP001E to DTL_DPP993E: IDMS CDC EDP Log Feeder, 627 DTL_DPS900I to DTL_DPS907I: IDMS Intercept Stub, 634 DTL_DPW002I to DTL_DPW532I: Datacom MUF Real-time Direct Log Processor, 635 DTL_DPX000E to DTL_DPX999E: IDMS CV Exit and Real-time Journal Processor, 639 DTL_DPZ500I to DTL_DPZ514I: IDMS CDC EDP Log Feeder fakeit (EDM Interface), 641 DTL_PRP001E to DTL_PRP302E: Datacom CDC EDP Log Feeder, 643 DTL_RPC001E to DTL_RPC999E: Datacom and IDMS CDC Dataspace Controller, 648 DTL_RPS001E to DTL_RPS105I: Datacom MUF Address Space Subtask Exit, 656
DTL_BMG003E to DTL_BMG101E: Datacom Low Level Metadata Retrieval

DTL_BMG003E Explanation: System Action: User Response: DTL_BMG011E Explanation: System Action: User Response: DTL_BMG012E Explanation: System Action: SYNTAX ERROR AT OPERAND: Operand The operand contains a syntax error. Processing ends. Correct the errant SYSIN statements and rerun the job. TABLE STATEMENT MISSING A required table statement was missing from parameters. Processing ends. Correct the errant SYSIN statements and rerun the job. ERRORS DETECTED IN SYSIN, PROGRAM TERMINATED One or more errors were detected in the SYSIN DD stream of a serious nature and processing may not continue. Processing ends.
623
User Response: DTL_BMG013E Explanation: System Action: User Response: DTL_BMG025E Explanation: System Action: User Response: DTL_BMG026E Explanation:
Correct the errant SYSIN statements and rerun the job. DATABASE STATEMENT MISSING A required database statement was missing from parameters. Processing ends. Correct the errant SYSIN statements and rerun the job. LIST STATEMENT MISSING A required list statement was missing from parameters. Processing ends. Correct the errant SYSIN statements and rerun the job. VERSION AND STATUS INCONSISTENT One of the following was provided

A version with PROD Version 000 without HIST
System Action: User Response: DTL_BMG027W Explanation: System Action: User Response: DTL_BMG101E Explanation: System Action: User Response:
Processing ends. Correct the errant SYSIN statements and rerun the job. NO DATA MATCHES CRITERIA The selection criteria resulted in no matching data. Processing continues. with warning issued. This may or may not be expected, proceed accordingly. DSF ERROR code An error occurred with the DSF. Processing ends. investigate, correct the error and resubmit.
DTL_DPL002I to DTL_DPL300I: Datacom MUF Realtime Log Processor

DTL_DPL002I Explanation: System Action: User Response: DTL_DPL005E Explanation: System Action: User Response: INPUT STATEMENT: Input_line Displays the input statement being processed. Processing continues. This message provides an audit trail. ERROR READING OR FINDING DTLINPUT DD There is a problem with the DTLINPUT input DD, processing continues. Processing continues. Investigate, correct the associated error and restart if necessary.
624
Chapter 2: DTL_BMG003 to DTL_RPS105I
DTL_DPL012E Explanation: System Action: User Response: DTL_DPL066E Explanation: System Action: User Response: DTL_DPL161E Explanation: System Action: User Response: DTL_DPL162E Explanation: System Action: User Response: DTL_DPL164E Explanation: System Action: User Response: DTL_DPL231I Explanation: System Action: User Response: DTL_DPL232I Explanation: System Action: User Response: DTL_DPL277I Explanation: System Action: User Response: DTL_DPL278I Explanation: System Action: User Response:
ERRORS DETECTED IN DTLINPUT, INPUT IGNORED Errors have been detected in the input, Processing continues. Processing continues. Investigate, correct the associated error and restart if necessary. NOT RUNNING AUTHORIZED, PROPAGATION TERMINATED This needs more authority to run, see documentation. Processing ends. investigate, correct the error and resubmit. TOKEN SERVICES FAILURE code A failure occurred accessing data through or for a token. Processing ends. investigate, correct the error and resubmit. UNABLE TO LOCATE MUF The Multi User facility (MUF) was not found using the supplied parameters. Processing ends. investigate, correct the error and resubmit. TOKEN = token The token involved in the related error. Processing ends. investigate, correct the associated error and resubmit. dbms_name PROPAGATION ENABLED Information that propagation is enabled for a database. Processing continues. This message provides an audit trail. dbms_name PROPAGATION DISABLED Information that propagation is disabled for a database. Processing continues. This message provides an audit trail. MOVER TRANSACTIONS IGNORED = count Print of ignored and filtered MOVER transactions. Processing continues. This message provides an audit trail. OPEN TRANSACTIONS IGNORED = count Print of ignored and filtered OPEN transactions. Processing continues. This message provides an audit trail.
DTL_DPL002I to DTL_DPL300I: Datacom MUF Real-time Log Processor 625
DTL_DPL279I Explanation: System Action: User Response: DTL_DPL280I Explanation: System Action: User Response: DTL_DPL281I Explanation: System Action: User Response: DTL_DPL282I Explanation: System Action: User Response: DTL_DPL283I Explanation: System Action: User Response: DTL_DPL284I Explanation: System Action: User Response: DTL_DPL285I Explanation: System Action: User Response: DTL_DPL286I Explanation: System Action: User Response: DTL_DPL287I Explanation: System Action: User Response:
626
TOTAL INVOCATIONS = count Print of exit invocations. Processing continues. This message provides an audit trail. TOTAL TRANSACTIONS READ = count Print of transaction count. Processing continues. This message provides an audit trail. TOTAL TRANSACTIONS SKIPPED = count Print of transaction count. Processing continues. This message provides an audit trail. ADD TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. UPDATE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. DELETE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. CLOSE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. LOGCX TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. COMIT TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail.
DTL_DPL288I Explanation: System Action: User Response: DTL_DPL289I Explanation: System Action: User Response: DTL_DPL290I Explanation: System Action: User Response: DTL_DPL299E Explanation: System Action: User Response: DTL_DPL300I Explanation: System Action: User Response:
LOGIT TRANSACTIONS IGNORED = count Print of ignored and filtered LOGIT transactions. Processing continues. This message provides an audit trail. LOGTB TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. ROLBK TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. UNKNOWN TRANSACTIONS FOUND = count Print of transaction count for unknown transactions. Processing ends. Report this error to Informatica Global Customer Support. POWEREXCHANGE COLLECTOR INITIALIZED The collector is initialized ready to get data. Processing continues. This message provides an audit trail.
DTL_DPP001E to DTL_DPP993E: IDMS CDC EDP Log Feeder

DTL_DPP001E Explanation: System Action: User Response: DTL_DPP002I Explanation: System Action: User Response: DTL_DPP005E Explanation: System Action: SYSPRINT DD MISSING The sysprint could not be used, most likely cause is it is missing. Processing ends. Investigate, correct the associated error and resubmit. INPUT STATEMENT: Input_line Forms a full list of the parameters. Processing continues. This message provides an audit trail. ERROR READING OR FINDING SYSIN DD There is a problem with the input SYSIN DD. Processing ends.
627
User Response: DTL_DPP009I Explanation: System Action: User Response: DTL_DPP012E Explanation: System Action: User Response: DTL_DPP014E Explanation: System Action: User Response: DTL_DPP106E Explanation: System Action: User Response: DTL_DPP119E Explanation: System Action: User Response: DTL_DPP120E Explanation: System Action: User Response: DTL_DPP121E Explanation: System Action: User Response: DTL_DPP122E Explanation: System Action: User Response:
investigate, correct the associated error and resubmit. CONSOLE STATEMENT: console_line Copy of console output. Processing continues. This message provides an audit trail. ERRORS DETECTED IN SYSIN, PROGRAM TERMINATED As errors have been detected in the input, Processing ends. Processing ends. investigate, correct the associated error and resubmit. CONSOLE INPUT COMMAND IGNORED ON ERROR See associated console statement that is in error. Processing ends. investigate, correct the associated error and resubmit. POWEREXCHANGE REPLICATION ENVIRONMENT NOT FOUND The Change Controller was not correctly run. Processing ends. Run the Change Controller with valid information. CV ALREADY SPECIFIED The CV parameter has already been specified. Processing ends. investigate, correct the associated error and resubmit. NO CV SPECIFIED The required CV parameter is missing. Processing ends. investigate, correct the associated error and resubmit. UNABLE TO LOCATE CV CV The specified CV was unable to be found. This is because of an error in the SYSIN stream or the CV was not defined to a Change Controller. Processing ends. Correct command stream and rerun job or define the CV through the Change Controller. UNABLE TO ESTABLISH DATASPACE FOR CV The specified CV does not have a dataspace available for connection most likely because the Change Controller ended. Processing ends. Review the jcl and input for the Change Controller and insure that it is currently active.
628
DTL_DPP123E Explanation: System Action: User Response:
TOKEN CREATE ERROR 4 An attempt to create a system token failed for duplicates. Processing ends. Verify that there is not another copy of the Change Propagator already running for the CV listed in the SYSIN stream. TOKEN CREATE ERROR 8 An internal error occurred in token creation. Processing ends. Contact Informatica Global Customer Support. TOKEN SERVICES FAILURE, RC=return_code If rc is a 4, the Change Controller for this CV was not started. If rc is anything else, token services had an internal error. Processing ends. If rc is a 4, check the Change Controller, otherwise contact Informatica Global Customer Support. TOKEN = rc This message is generated in combination with other token error messages. Processing ends. Review output for other token error messages. Jobname PROPAGATION COLLECTOR ENABLED FOR dbms_name Collection was enabled for the database. Processing continues. This message provides an audit trail. PROPAGATION COLLECTOR ALREADY ENABLED FOR dbms_name An enqueue has failed. This implies propagation is already enabled. Processing ends. If this is not reasonable in the circumstances Contact Informatica Global Customer Support for further assistance. UNABLE TO INITIALIZE CONSOLE RC= rc While attempting to initialize the common component for console support, a return code of rc was encountered. Processing ends. Contact Informatica Global Customer Support with the return code. UNABLE TO INITIALIZE DTLXISTL rc While attempting to initialize the common component for timer management, an error was encountered. Processing ends. Contact Informatica Global Customer Support for further assistance.
DTL_DPP124E Explanation: System Action: User Response: DTL_DPP161E Explanation: System Action: User Response:
DTL_DPP164E Explanation: System Action: User Response: DTL_DPP231I Explanation: System Action: User Response: DTL_DPP232E Explanation: System Action: User Response:
DTL_DPP240E Explanation: System Action: User Response: DTL_DPP243E Explanation: System Action: User Response:
629
UNABLE TO INITIALIZE DTLXIPII rc While attempting to initialize the IDMS interface, an error was encountered. Processing ends. Review the JCL for Propagator errors or contact Informatica Global Customer Support for further assistance. FUNCTION BYPASS FOR RUNUNIT run_unit, REASON=feedback Record of BYPASS encountered with reason feedback. Processing continues. This message provides an audit trail. EXISTING TXN FOUND FOR RUNUNIT run_unit An internal error has happened causing the same transaction to exist twice in the system. Processing ends. Contact Informatica Global Customer Support. SEQUENCE ERROR ON rectype An internal error occurred in that a rectype was found for a transaction without a corresponding BEGN. Processing ends. Contact Informatica Global Customer Support. TRANSACTION FOUND AS Rectype. RUNUNIT Unit_of_recovery, SEQ=seq1rst2 Trace output. Processing continues. This is the trace entry. BEGN UNABLE TO CREATE TXN/TASK An internal error. Processing ends. Contact Informatica Global Customer Support. LINKAGE FAILURE rc An internal error. Processing ends. Contact Informatica Global Customer Support. CDMSLIB ERROR return_code The Change Propagator was unable to locate the CDMSLIB DD statement or unable to open the data set. Processing ends. Review the JCL for the Change Propagator for a valid CDMSLIB DD statement.
DTL_DPP254I Explanation: System Action: User Response: DTL_DPP257E Explanation: System Action: User Response: DTL_DPP258E Explanation: System Action: User Response: DTL_DPP259I Explanation: System Action: User Response: DTL_DPP260E Explanation: System Action: User Response: DTL_DPP270E Explanation: System Action: User Response: DTL_DPP271E Explanation: System Action: User Response:
630
DTL_DPP282I Explanation: System Action: User Response: DTL_DPP283I Explanation: System Action: User Response: DTL_DPP284I Explanation: System Action: User Response: DTL_DPP285I Explanation: System Action: User Response: DTL_DPP286I Explanation: System Action: User Response: DTL_DPP287I Explanation: System Action: User Response: DTL_DPP288I Explanation: System Action: User Response: DTL_DPP301E Explanation: System Action:
INSERT TRANSACTIONS PROCESSED = feedback This is the number of INSERT transactions that were passed to the PowerExchange Logger. Processing continues. This message provides an audit trail. UPDATE TRANSACTIONS PROCESSED = feedback This is the number of UPDATE transactions that were passed to the PowerExchange Logger. Processing continues. This message provides an audit trail. DELETE TRANSACTIONS PROCESSED = feedback This is the number of DELETE transactions that were passed to the PowerExchange Logger. Processing continues. This message provides an audit trail. COMMIT TRANSACTIONS PROCESSED = feedback BY ENDJ This is the number of COMMIT transactions that were passed to the PowerExchange Logger because of an ENDJ. Processing continues. This message provides an audit trail. BUOW TRANSACTIONS PROCESSED = feedback This is the number of BUOW transactions that were passed to the PowerExchange Logger. Processing continues. This message provides an audit trail. COMMIT TRANSACTIONS PROCESSED = feedback BY COMT This is the number of COMMIT transactions that were passed to the PowerExchange Logger because of an COMT. Processing continues. This message provides an audit trail. ABORT TRANSACTIONS PROCESSED = feedback This is the number of ABORT transactions that were passed to the PowerExchange Logger. Processing continues. This message provides an audit trail. EDP CMD command ERROR RC=return_code1return_code2,status JOB=jobname UOW=tkn1tkn2 The command has failed as stated in the given jobname at the tkn1 tkn2 Unit Of Work. Processing ends.
631
User Response:
Investigate, if possible correct the associated error and resubmit. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support. DPII ABENDED IDMS interface from the Change Propagator abended. Processing ends. Contact Informatica Global Customer Support. USER HAS REQUESTED FILTERING OF SR4 RECORDS The user has specified "IGNORE_SR4" in the DTLXIPIP input stream. Any SR4 record encountered in the change stream is ignored. This feature should only be used with guidance from Informatica Global Customer Support. Processing continues. This message provides an audit trail. USER HAS REQUESTED USE OF SR3 HASH TABLE The user has specified "SR3_HASH" in the DTLXIPIP input stream. Any SR3 record encountered in the change stream uses the SR3 hash table, built using the input generated by the DTLUCSR2, to utility to reidentify SR3 journal records. Processing continues. This message provides an audit trail. USER HAS DISABLED USE OF SR3 HASH TABLE The user has specified "SR3_HASH OFF" in the DTLXIPIP input stream. Any SR3 record encountered in the change stream does not use the SR3 hash table, built using the input generated by the DTLUCSR2, to reidentify SR3 journal records. Processing continues. This message provides an audit trail. UNABLE TO ESTABLISH SR3 HASH TABLE Establishment of SR3 Hash Table has failed. An accompanying message is issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support. SR3 HASH TABLE SUCCESSFULLY BUILT Establishment of SR3 Hash Table was successful. Processing continues. This message provides an audit trail. HASH INTERFACE INVOCATION ERROR = rc An error occurred using the SR3 hash table interface. An accompanying message may be issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support.
DTL_DPP302E Explanation: System Action: User Response: DTL_DPP980I Explanation:
System Action: User Response: DTL_DPP981I Explanation:
System Action: User Response: DTL_DPP982I Explanation:
System Action: User Response: DTL_DPP983E Explanation: System Action: User Response: DTL_DPP984I Explanation: System Action: User Response: DTL_DPP985E Explanation: System Action: User Response:
632
DTL_DPP986E Explanation: System Action: User Response: DTL_DPP987E Explanation: System Action: User Response: DTL_DPP988E Explanation: System Action: User Response: DTL_DPP989E Explanation: System Action: User Response: DTL_DPP990I Explanation:
HASH INTERFACE BUILD ERROR = rc An error occurred while building the SR3 hash table. An accompanying message is issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support. HASH INTERFACE DESTROY ERROR = rc An error occurred while removing the SR3 hash table. An accompanying message is issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support. HASH INTERFACE FIND ERROR = rc An error occurred while using the SR3 hash table. An accompanying message is issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support. message RETURNED HASH INTERFACE ERROR MSG An error occurred using the SR3 hash table interface. This message contains additional error information returned by the interface. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support. USER HAS DISABLED FILTERING OF SR4 RECORDS The user has specified "IGNORE_SR4 OFF" in the DTLXIPIP input stream. Any SR4 record encountered in the change stream is processed. This feature should only be used with guidance from Informatica Global Customer Support. Processing continues. This message provides an audit trail. LOAD OF HASH ROUTINE DTLIAHTB, FAILED The hash interface routine DTLIAHTB module could not be loaded. Ensure That DTLIAHTB module is in steplib library. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support. UNABLE TO RESOLVE BEFORE IMAGE SR3 DB-KEY db-key FROM HASH TABLE An error occurred while using the SR3 hash table to find the specified before image. An accompanying message is issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support.
System Action: User Response: DTL_DPP991E Explanation: System Action: User Response: DTL_DPP992E Explanation: System Action: User Response:
633
UNABLE TO RESOLVE AFTER IMAGE SR3 DB-KEY db-key FROM HASH TABLE An error occurred while using the SR3 hash table to find the specified after image. An accompanying message is issued indicating reason for failure. Processing continues. If you cannot resolve the problem, contact Informatica Global Customer Support.
DTL_DPS900I to DTL_DPS907I: IDMS Intercept Stub

DTL_DPS900I Explanation: System Action: User Response: DTL_DPS901E Explanation: System Action: User Response: DETAIL-IDMS INITIALIZATION This is an informative message that shows an attempt starting to load as an IDMS exit. Processing continues. This message provides an audit trail. LOAD ERROR OF DTLXIPIX The DTLXIPIX was unable load. Processing ends. Review the IDMS CV JCL to see if the PowerExchange Change Capture for IDMS libraries are in the STEPLIB. Correct the JCL and restart IDMS. NO STORAGE FOR DETAIL-IDMS EXIT This is an internal error. Processing ends. Contact Informatica Global Customer Support. DETAIL-IDMS INITIALIZATION FAILURE Other errors have occurred and IDMS cannot continue. Processing continues. Look for other error messages and address those problems. RESTART WILL BE ATEMPTED The current task is failing and restart is attempted. Processing continues. This message provides an audit trail. RESTART NOT POSSIBLE The current task is failing and restart is not possible. Processing ends. Look for other error messages and address those problems. DETAIL-IDMS INITIALIZATION COMPLETE This is an informative message that shows that the intercept stub was correctly linked and invoked as an IDMS exit. Processing continues.
DTL_DPS902E Explanation: System Action: User Response: DTL_DPS903E Explanation: System Action: User Response: DTL_DPS904E Explanation: System Action: User Response: DTL_DPS905E Explanation: System Action: User Response: DTL_DPS906I Explanation: System Action:
634
User Response: DTL_DPS907I Explanation: System Action: User Response:
This message provides an audit trail. ALL FACILITIES NOT CURRENTLY ACTIVE The initialization has not completed cleanly as the return code is 4, this is not always an issue. Processing continues. If this is an issue investigate associated messages.
DTL_DPW002I to DTL_DPW532I: Datacom MUF Realtime Direct Log Processor

DTL_DPW002I Explanation: System Action: User Response: DTL_DPW005E Explanation: System Action: User Response: DTL_DPW012E Explanation: System Action: User Response: DTL_DPW066E Explanation: System Action: User Response: DTL_DPW106E Explanation: System Action: User Response: DTL_DPW119E Explanation: System Action: User Response: INPUT STATEMENT: Input_line Displays the input statement being processed. Processing continues. This message provides an audit trail. ERROR READING OR FINDING DTLINPUT DD There is a problem with the DTLINPUT input DD, processing continues. Processing continues. Investigate, correct the associated error and restart if necessary. ERRORS DETECTED IN DTLINPUT, INPUT IGNORED Errors have been detected in the input, processing continues. Processing continues. Investigate, correct the associated error and restart if necessary. NOT RUNNING AUTHORIZED, PROPAGATION TERMINATED This needs more authority to run, see documentation. Processing ends. investigate, correct the error and resubmit. DETAIL PROPAGATION ENVIRONMENT NOT FOUND The Change Controller was not correctly run. Processing ends. Run the Change Controller with valid information. MUF ALREADY SPECIFIED The MUF parameter has already been supplied. Processing ends. Investigate, correct the associated error and resubmit.
DTL_DPW002I to DTL_DPW532I: Datacom MUF Real-time Direct Log Processor
635
DTL_DPW120E Explanation: System Action: User Response: DTL_DPW160I Explanation: System Action: User Response: DTL_DPW161E Explanation: System Action: User Response: DTL_DPW162E Explanation: System Action: User Response: DTL_DPW164E Explanation: System Action: User Response: DTL_DPW233I Explanation: System Action: User Response: DTL_DPW234E Explanation: System Action: User Response:
NO MUF SPECIFIED The required MUF parameter is missing. Processing ends. investigate, correct the associated error and resubmit. UNABLE TO LOAD MODULE name The specified module could not be loaded. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. TOKEN SERVICES FAILURE code A failure occurred accessing data through or for a token. Processing ends. investigate, correct the error and resubmit. UNABLE TO LOCATE MUF The Multi User facility (MUF) was not found using the supplied parameters. Processing ends. investigate, correct the error and resubmit. TOKEN = token The token involved in the related error Processing ends. investigate, correct the associated error and resubmit. Jobname PROPAGATION COLLECTOR ENABLED FOR dbms_name Collection was enabled for the database. Processing continues. This message provides an audit trail. PROPAGATION COLLECTOR ALREADY ENABLED FOR dbms_name An enqueue has failed. This implies propagation is already enabled. Processing ends. If this is not reasonable in the circumstances Contact Informatica Global Customer Support for further assistance. CYCLE START FOUND FOR SEQUENCE NUMBER = seq_start Print of cycle start sequence number. Processing continues. This message provides an audit trail. CYCLE END FOUND FOR SEQUENCE NUMBER = seq_end Print of cycle end sequence number. Processing continues.
DTL_DPW260I Explanation: System Action: User Response: DTL_DPW261I Explanation: System Action:
636
User Response: DTL_DPW277I Explanation: System Action: User Response: DTL_DPW278I Explanation: System Action: User Response: DTL_DPW279I Explanation: System Action: User Response: DTL_DPW280I Explanation: System Action: User Response: DTL_DPW281I Explanation: System Action: User Response: DTL_DPW282I Explanation: System Action: User Response: DTL_DPW283I Explanation: System Action: User Response: DTL_DPW284I Explanation: System Action: User Response:
This message provides an audit trail. MOVER TRANSACTIONS IGNORED = count Print of ignored and filtered MOVER transactions. Processing continues. This message provides an audit trail. OPEN TRANSACTIONS IGNORED = count Print of ignored and filtered OPEN transactions. Processing continues. This message provides an audit trail. TOTAL INVOCATIONS = count Print of exit invocations. Processing continues. This message provides an audit trail. TOTAL TRANSACTIONS READ = count Print of transaction count. Processing continues. This message provides an audit trail. TOTAL TRANSACTIONS SKIPPED = count Print of transaction count. Processing continues. This message provides an audit trail. ADD TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. UPDATE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. DELETE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail.
DTL_DPW002I to DTL_DPW532I: Datacom MUF Real-time Direct Log Processor
637
DTL_DPW285I Explanation: System Action: User Response: DTL_DPW286I Explanation: System Action: User Response: DTL_DPW287I Explanation: System Action: User Response: DTL_DPW288I Explanation: System Action: User Response: DTL_DPW289I Explanation: System Action: User Response: DTL_DPW290I Explanation: System Action: User Response: DTL_DPW299E Explanation: System Action: User Response: DTL_DPW301E Explanation: System Action: User Response:
CLOSE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. LOGCX TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. COMIT TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. LOGIT TRANSACTIONS IGNORED = count Print of ignored and filtered LOGIT transactions. Processing continues. This message provides an audit trail. LOGTB TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. ROLBK TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. UNKNOWN TRANSACTIONS FOUND = count Print of transaction count for unknown transactions. Processing ends. Report this error to Informatica Global Customer Support. EDP CMD command ERROR RC=return_code1,status JOB=jobname UOW=tkn1tkn2 The command has failed as stated in the given jobname at the tkn1 tkn2 Unit Of Work. Processing ends. Investigate, if possible correct the associated error and resubmit. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support.
638
DTL_DPW302E Explanation:
UNREGISTERED ELEMENT, element, IN MODULE DBID=dbid, TBL=table, SOURCE=source A table that was registered for capture now contains an unregistered element. This suggests a change to the database without reregistering the table and perhaps other tasks at the target for this collection. Processing ends. Use the messages to work out what has caused this, establish scope and a way forward. It may be necessary to rematerialize and restart capture of this and any other effected tables. Contact Informatica Global Customer Support for further support. CHECKPOINT FOR NON ACTIVE TASK A "LOGC" or "COMIT" checkpoint was encountered for a non active task. Processing ends. Investigate, if possible correct the associated error and resubmit. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support. dbms_name PROPAGATION ENABLED Information that propagation is enabled for a database. Processing continues. This message provides an audit trail. dbms_name PROPAGATION DISABLED Information that propagation is disabled for a database. Processing continues. This message provides an audit trail.
DTL_DPW303E Explanation: System Action: User Response:
DTL_DPW531I Explanation: System Action: User Response: DTL_DPW532I Explanation: System Action: User Response:
DTL_DPX000E to DTL_DPX999E: IDMS CV Exit and Real-time Journal Processor

DTL_DPX000E Explanation: System Action: User Response: UNABLE TO ESTABLISH ENVIRONMENT The IDMS environment was not successfully established. Processing ends. Investigate, if possible correct the associated error and resubmit. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support. INPUT STATEMENT: Input_line Displays the input statement being processed. Processing continues. This message provides an audit trail.
DTL_DPX002I Explanation: System Action: User Response:
DTL_DPX000E to DTL_DPX999E: IDMS CV Exit and Real-time Journal Processor
639
DTL_DPX005E Explanation: System Action: User Response: DTL_DPX012E Explanation: System Action: User Response: DTL_DPX101I Explanation: System Action: User Response: DTL_DPX121I Explanation: System Action: User Response: DTL_DPX122I Explanation: System Action: User Response: DTL_DPX123I Explanation: System Action: User Response: DTL_DPX161E Explanation: System Action: User Response:
ERROR READING OR FINDING DTLINPUT DD There is a problem with the DTLINPUT input DD, processing continues. Processing continues. Investigate, correct the associated error and restart if necessary. ERRORS DETECTED IN DTLINPUT, INPUT IGNORED Errors have been detected in the input, processing continues. Processing continues. Investigate, correct the associated error and restart if necessary. dbms PROPAGATION INITIALIZATION' Propagation was initialized for the specified database. Processing continues. This message provides an audit trail. CV PROPAGATION ENABLED Propagation was enabled for the specified database. Processing continues. This message provides an audit trail. CV PROPAGATION ENVIRONMENT NOT FOUND No CV could be found amongst those defined by Change Controller for the given name. Processing ends. Correct the jobname or Change Controller command stream and rerun job. CV PROPAGATION DISABLED Propagation was disabled for the specified database. Processing continues. This message provides an audit trail. TOKEN SERVICES FAILURE return_code If the return code is 4, the Change Controller for this CV was not started. Return codes of greater than 4 indicate an internal token services error. Processing ends. For a return code of 4, check the Change Controller. Otherwise, contact Informatica Global Customer Support. TOKEN = token_value This message provides diagnostic information. Processing continues. for other messages. Review output for other messages.
DTL_DPX164E Explanation: System Action: User Response:
640
DTL_DPX798E Explanation: System Action: User Response:
SUBSYSTEM ERROR, RC=return_code, WHILE RUNNING IDMS IN non standard STORAGE PROTECT KEY An error occurred in a subsystem. Processing ends. Investigate, if possible correct the associated error and resubmit. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support. NON STANDARD STORAGE PROTECT KEY: key The printed key is not standard. Processing continues. See any associated messages. DATASPACE IN UNKNOWN STATE Data type unknown (or TIME, AREA). Processing ends. with dump of data including type. Investigate, if possible correct the associated error and resubmit. It may be necessary to restart beyond this point. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support.
DTL_DPX799I Explanation: System Action: User Response: DTL_DPX999E Explanation: System Action: User Response:
DTL_DPZ500I to DTL_DPZ514I: IDMS CDC EDP Log Feeder fakeit (EDM Interface)
DTL_DPZ500I Explanation: System Action: User Response: DTL_DPZ501I Explanation: System Action: User Response: DTL_DPZ502E Explanation: System Action: User Response: DTL_DPZ503E Explanation: System Action: User Response: POWEREXCHANGE STUB PARM COUNT IS Number Record of parameter count. Processing continues. audit trail POWEREXCHANGE STUB FUNCTION IS function Record of function passed to the PowerExchange Logger. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB UNKNOWN FUNCTION function Internal error. Processing ends. contact Informatica Global Customer Support. POWEREXCHANGE STUB PARM COUNT NEEDED IS Number Internal error. Processing ends. contact Informatica Global Customer Support.
DTL_DPZ500I to DTL_DPZ514I: IDMS CDC EDP Log Feeder fakeit (EDM Interface)
641
DTL_DPZ504I Explanation: System Action: User Response: DTL_DPZ505I Explanation: System Action: User Response: DTL_DPZ506I Explanation: System Action: User Response: DTL_DPZ507I Explanation: System Action: User Response: DTL_DPZ508I Explanation: System Action: User Response: DTL_DPZ509I Explanation: System Action: User Response: DTL_DPZ510I Explanation: System Action: User Response: DTL_DPZ511I Explanation: System Action: User Response: DTL_DPZ512I Explanation: System Action: User Response:
642
POWEREXCHANGE STUB PARM UOW JOBNAME IS jobname The jobname for the unit of work is printed. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM UID IS user_ID The user ID passed printed. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM SOURCE IS source_name The source name passed to the PowerExchange Logger printed. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM DATA1 FOR 80 BYTES IS data The data printed is the first 80 bytes of an insert, a delete or a before image for an update. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM DATA2 FOR 80 BYTES IS data The data printed is the first 80 bytes of an after image for an update. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM OPTS IS user_ID The options passed to the PowerExchange Logger is printed. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM OPTS LEN IS user_ID The actual length of the data following is printed. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM DATA1 LEN IS length The actual length of the data following is printed. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM DATA2 LEN IS length The actual length of the data following is printed. Processing continues. This message provides an audit trail.
DTL_DPZ513I Explanation: System Action: User Response: DTL_DPZ514I Explanation: System Action: User Response:
POWEREXCHANGE STUB PARM UOW RUID IS run_unit_id The run unit ID is printed. this matches the IDMS run unit ID. Processing continues. This message provides an audit trail. POWEREXCHANGE STUB PARM UOW TSN IS transaction_seq_no The transaction sequence number is printed. It is a sequential number within a run unit ID. Processing continues. This message provides an audit trail.
DTL_PRP001E to DTL_PRP302E: Datacom CDC EDP Log Feeder

DTL_PRP001E Explanation: System Action: User Response: DTL_PRP002I Explanation: System Action: User Response: DTL_PRP005E Explanation: System Action: User Response: DTL_PRP009I Explanation: System Action: User Response: DTL_PRP012E Explanation: System Action: User Response: DTL_PRP014E Explanation: System Action: SYSPRINT DD MISSING The sysprint could not be used, most likely cause is it is missing. Processing ends. investigate, correct the associated error and resubmit. INPUT STATEMENT Input_line Forms a full list of the parameters. Processing continues. This message provides an audit trail. ERROR READING OR FINDING SYSIN DD There is a problem with the input SYSIN DD. Processing ends. investigate, correct the associated error and resubmit. CONSOLE STATEMENT: data Print of the console input being processed. Processing continues. Audit trail ERRORS DETECTED IN SYSIN, PROGRAM TERMINATED As errors have been detected in the input, Processing ends. Processing ends. investigate, correct the associated error and resubmit. CONSOLE INPUT COMMAND IGNORED ON ERROR As errors have been detected in the console input, Processing ends. Processing ends.
DTL_PRP001E to DTL_PRP302E: Datacom CDC EDP Log Feeder 643
User Response: DTL_PRP060E Explanation: System Action: User Response: DTL_PRP061E Explanation: System Action: User Response: DTL_PRP062E Explanation: System Action: User Response: DTL_PRP070E Explanation: System Action: User Response: DTL_PRP119E Explanation: System Action: User Response: DTL_PRP120E Explanation: System Action: User Response: DTL_PRP121E Explanation: System Action: User Response: DTL_PRP122E Explanation: System Action: User Response:
Investigate, correct the associated error and resubmit. DATA = data Print of data from trace or for diagnosis. Processing continues. Audit trail or support for other messages. UPPER = data Print of data (first character of hexadecimal pair) from trace or for diagnosis. Processing continues. Audit trail or support for other messages. LOWER = data Print of data (second character of hexadecimal pair) from trace or for diagnosis. Processing continues. Audit trail or support for other messages. HEADER DATA DUMP Print of data from trace or for diagnosis, header. Processing continues. Audit trail or support for other messages. MUF ALREADY SPECIFIED The MUF parameter has already been supplied. Processing ends. Investigate, correct the associated error and resubmit. NO MUF SPECIFIED The required MUF parameter is missing. Processing ends. Investigate, correct the associated error and resubmit. UNABLE TO LOCATE MUF MUF The specified MUF could not be located. Processing ends. Investigate, correct the associated error and resubmit. UNABLE TO ESTABLISH DATASPACE FOR MUF A dataspace could not be found or created for the specified MUF. Processing ends. Check the Change Controller to ensure that the specified MUF was specified in create mode.
644
DTL_PRP165I Explanation: System Action: User Response: DTL_PRP221I Explanation: System Action: User Response: DTL_PRP226E Explanation: System Action: User Response: DTL_PRP227E Explanation: System Action: User Response: DTL_PRP231I Explanation: System Action: User Response: DTL_PRP232E Explanation: System Action: User Response:
TOKEN CREATED FOR MUF A token was created for the specified MUF. Processing continues. This message provides an audit trail. DATASPACE IS NOT-ACTIVE FOR dbms_name NON CREATE MODE A dataspace could not be created because the Change Controller was not running in create mode. Processing ends. Run the Change Controller in create mode. TOKEN RETRIEVAL ERROR, RC=return_code The process received an error while trying to retrieve a token. Processing ends. Contact Informatica Global Customer Support for further assistance. TOKEN CREATION ERROR return_code The process received an error while trying to create a token. Processing ends. Contact Informatica Global Customer Support for further assistance. Jobname PROPAGATION COLLECTOR ENABLED FOR dbms_name Collection was enabled for the database. Processing continues. This message provides an audit trail. PROPAGATION COLLECTOR ALREADY ENABLED FOR dbms_name An enqueue has failed. This implies propagation is already enabled. Processing ends. If this is not reasonable in the circumstances contact Informatica Global Customer Support for further assistance. UNABLE TO INITIALIZE CONSOLE RC= return_code Console support component initialization failed with return code. Processing ends. Contact Informatica Global Customer Support with return code. UNABLE TO INITIALIZE DTLXISTL An error occurred initializing the timer management component. Processing ends. Contact Informatica Global Customer Support for further assistance.
DTL_PRP240E Explanation: System Action: User Response: DTL_PRP243E Explanation: System Action: User Response:
645
DTL_PRP259I Explanation: System Action: User Response: DTL_PRP260I Explanation: System Action: User Response: DTL_PRP261I Explanation: System Action: User Response: DTL_PRP280I Explanation: System Action: User Response: DTL_PRP281I Explanation: System Action: User Response: DTL_PRP282I Explanation: System Action: User Response: DTL_PRP283I Explanation: System Action: User Response: DTL_PRP284I Explanation: System Action: User Response: DTL_PRP285I Explanation: System Action: User Response:
646
TRANSACTION FOUND AS transaction. RUNUNIT Run_unit, UOW=UOW Print of Transaction run unit and unit of work/recovery. Processing continues. This message provides an audit trail. CYCLE START FOUND FOR SEQUENCE NUMBER = seq_start Print of cycle start sequence number. Processing continues. This message provides an audit trail. CYCLE END FOUND FOR SEQUENCE NUMBER = seq_end Print of cycle end sequence number. Processing continues. This message provides an audit trail. TOTAL TRANSACTIONS READ = count Print of transaction count. Processing continues. This message provides an audit trail. TOTAL TRANSACTIONS SKIPPED = count Print of transaction count. Processing continues. This message provides an audit trail. ADD TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. UPDATE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. DELETE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. CLOSE TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail.
DTL_PRP286I Explanation: System Action: User Response: DTL_PRP287I Explanation: System Action: User Response: DTL_PRP288I Explanation: System Action: User Response: DTL_PRP289I Explanation: System Action: User Response: DTL_PRP290I Explanation: System Action: User Response: DTL_PRP300E Explanation: System Action: User Response: DTL_PRP301E Explanation: System Action: User Response:
LOGCX TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. COMIT TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. LOGIT TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. LOGTB TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. ROLBK TRANSACTIONS PROCESSED = count Print of transaction count. Processing continues. This message provides an audit trail. UNKNOWN TRANSACTIONS FOUND = count Print of transaction count for unknown transactions. Processing ends. Report this error to Informatica Global Customer Support. EDP CMD command ERROR RC=return_code1return_code2,status JOB=jobname UOW=tkn1tkn2 The command has failed as stated in the given jobname at the tkn1 tkn2 Unit Of Work. Processing ends. Investigate, if possible correct the associated error and resubmit. Should there be no reason for this from associated messages or it is not clear contact Informatica Global Customer Support. UNREGISTERED ELEMENT, element, IN MODULE module DBID=dbid, TBL=table, SOURCE=source A table that was registered for capture now contains an unregistered element. This suggests a change to the database without reregistering the table and perhaps other tasks at the target for this collection. Processing ends.
DTL_PRP302E Explanation:
System Action:
647
User Response:
Use the messages to work out what has caused this, establish scope and a way forward. It may be necessary to rematerialize and restart capture of this and any other effected tables. Contact Informatica Global Customer Support for further support.
DTL_RPC001E to DTL_RPC999E: Datacom and IDMS CDC Dataspace Controller

DTL_RPC001E Explanation: System Action: User Response: DTL_RPC002I Explanation: System Action: User Response: DTL_RPC005E Explanation: System Action: User Response: DTL_RPC008I Explanation: System Action: User Response: DTL_RPC009I Explanation: System Action: User Response: DTL_RPC012E Explanation: System Action: User Response: DTL_RPC014E Explanation: System Action: User Response: SYSPRINT DD MISSING The sysprint could not be used, most likely cause is it is missing. Processing ends. investigate, correct the associated error and resubmit. INPUT STATEMENT: Input_line Forms a full list of the parameters. Processing continues. This message provides an audit trail. ERROR READING OR FINDING SYSIN DD There is a problem with the input SYSIN DD. Processing ends. investigate, correct the associated error and resubmit. PARM STATEMENT: Parameter_line Copy of parameter input. Processing continues. This message provides an audit trail. CONSOLE STATEMENT: console_line Copy of console output. Processing continues. This message provides an audit trail. PROGRAM TERMINATED. INPUT ERROR FROM PARM/SYSIN One or more errors were detected in the SYSIN DD stream of a serious nature and processing may not continue. Processing ends. Correct the errant SYSIN statements and rerun the job CONSOLE INPUT COMMAND IGNORED ON ERROR See associated console statement that is in error. Processing ends. Investigate, correct the associated error and resubmit.
648
DTL_RPC019I Explanation: System Action: User Response: DTL_RPC105E Explanation: System Action: User Response: DTL_RPC119E Explanation: System Action: User Response: DTL_RPC120E Explanation: System Action: User Response: DTL_RPC160I Explanation: System Action: User Response: DTL_RPC165I Explanation: System Action: User Response: DTL_RPC166I Explanation: System Action: User Response: DTL_RPC167I Explanation: System Action: User Response: DTL_RPC168I Explanation: System Action: User Response:
DUPLICATE SOURCE STATEMENT IGNORED A duplicate parameter was ignored. Processing continues. Investigate and correct the error to eliminate the warning in the future. INVALID RCM MODULE The RCM Module is not correct. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. EXPECTED CV OR MUF KEYWORD NOT FOUND The keyword encountered did not identify a MUF or CV. Processing ends. Investigate, correct the associated error and resubmit. NO DBMS (CV/MUF) REGION SPECIFIED The required identity of a CV or MUF is missing. Processing ends. Investigate, correct the associated error and resubmit. UNABLE TO LOAD MODULE name The specified module could not be loaded. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. TOKEN CREATED FOR resource A token was created for this particular resource. Processing continues. This message provides an audit trail. UNABLE TO LOAD TO CSA resource The specified module could not be loaded to CSA. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. CSA LOAD ERROR R15=return_code The return code for the module load to CSA that failed. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. CSA LOAD ERROR R1=reg1 Register 1 diagnostics or the module load to CSA that failed. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support.
DTL_RPC001E to DTL_RPC999E: Datacom and IDMS CDC Dataspace Controller 649
DTL_RPC170I Explanation: System Action: User Response: DTL_RPC201E Explanation: System Action: User Response: DTL_RPC202W Explanation: System Action: User Response: DTL_RPC203W Explanation: System Action: User Response: DTL_RPC204E Explanation: System Action: User Response: DTL_RPC205I Explanation: System Action: User Response: DTL_RPC206I Explanation: System Action: User Response: DTL_RPC208I Explanation: System Action: User Response: DTL_RPC209I Explanation: System Action:
GET CAPTURED REGISTRATIONS FROM LOCATION place Information: the location "PSEUDO/LOCAL" or actual where registrations are being taken from. Processing continues. This message provides an audit trail. MODULE UNABLE TO BE LOADED resource The specified RCM module could not be loaded. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. MODULE NOT FOUND resource The specified RCM module could not be found. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. MODULE ALREADY ACTIVE resource Warning that this specified resource was previously activated. Processing continues. Investigate and correct the error to eliminate the warning in the future. MODULE ALREADY DEACTIVATED resource The specified resource is not active. Processing ends. Investigate, correct the associated error and ready for resubmission. DBID IS dbname Print of the dbname. Processing continues. This message provides an audit trail. TABLE NAME IS table Print of the table name code. Processing continues. This message provides an audit trail. SETNAME = setname Print of the set name. Processing continues. This message provides an audit trail. PATH SOURCE NAME IS path_source_name Print of the path source name. Processing continues.
650
User Response: DTL_RPC210I Explanation: System Action: User Response: DTL_RPC211I Explanation: System Action: User Response: DTL_RPC212I Explanation: System Action: User Response: DTL_RPC213I Explanation: System Action: User Response: DTL_RPC214I Explanation: System Action: User Response: DTL_RPC215I Explanation: System Action: User Response: DTL_RPC216I Explanation: System Action: User Response: DTL_RPC217I Explanation: System Action: User Response:
This message provides an audit trail. STATUS FOR MODULE resource Print of the Module name. Processing continues. This message provides an audit trail. MODULE IS ACTIVE Print of the resource status. Processing continues. This message provides an audit trail. MODULE IS INACTIVE Print of the resource status. Processing continues. This message provides an audit trail. DBNAME IS dbname This is a result of a status command for a registration against the specified DBID. Processing continues. This message provides an audit trail. RECORD NAME IS record This is a result of a status command for a registration against the specified record. Processing continues. This message provides an audit trail. BASE SOURCE NAME IS source This is a result of a status command for a registration. The registration is against the specified propagation source. Processing continues. This message provides an audit trail. NO BASE SOURCE NAME SPECIFIED This is a result of a status command for a registration. The registration is not against a specified propagation source. Processing continues. This message provides an audit trail. RECORD ID = recid This is a result of a status command for a registration. The registration is against the specified record ID. Processing continues. This message provides an audit trail.
651
DTL_RPC218I Explanation: System Action: User Response: DTL_RPC219I Explanation: System Action: User Response: DTL_RPC220I Explanation: System Action: User Response: DTL_RPC221I Explanation: System Action: User Response: DTL_RPC222I Explanation: System Action: User Response: DTL_RPC223I Explanation:
PATH COUNT = count This is a result of a status command for a registration. The registration is has the stated path count. Processing continues. This message provides an audit trail. NO RCM MODULES FOUND No RCM modules could be found. Processing continues. Resubmit the request, if necessary, changing the selection. DATASPACE IS ACTIVE FOR MUF This message indicates that a Change Controller is active for the specified MUF and has built a dataspace. Processing continues. This message provides an audit trail. DATASPACE IS NOT-ACTIVE FOR MUF There is no current dataspace for specified MUF and this execution of the Change Controller cannot build one because it is not in CREATE mode. Processing ends. Rerun the job if necessary with a CREATE statement to create a dataspace for the MUF. DATASPACE CREATED WITH NAME MUF This is an informative message that a Change Controller in create mode created a dataspace for specified MUF. Processing continues. This message provides an audit trail. DATASPACE CREATED WITH number BLOCKS This is an informative message for the size of the dataspace. Normally is 524287 or 524288. If the number is significantly different, contact your system programmer to see if the dataspace size was restricted in your shop. Processing continues. This message provides an audit trail. DATASPACE CREATED WITH origin ORIGIN This is the origin of the dataspace and is meant for debugging purposes only. Processing continues. This message provides an audit trail. TOKEN RETRIEVAL ERROR The program received an error while trying to retrieve a token. Processing ends. Contact Informatica Global Customer Support.
System Action: User Response: DTL_RPC224I Explanation: System Action: User Response: DTL_RPC226E Explanation: System Action: User Response:
652
DTL_RPC227E Explanation: System Action: User Response: DTL_RPC228E Explanation: System Action: User Response: DTL_RPC229E Explanation: System Action: User Response: DTL_RPC231I Explanation: System Action: User Response: DTL_RPC232I Explanation: System Action: User Response: DTL_RPC233I Explanation: System Action: User Response: DTL_RPC234I Explanation: System Action: User Response: DTL_RPC237E Explanation: System Action: User Response: DTL_RPC238E Explanation: System Action: User Response:
TOKEN CREATION ERROR code While attempting to create a token, the program received error printed. Processing ends. Contact Informatica Global Customer Support. DATASPACE ALLOCATION ERROR code An error occurred during dataspace allocation with internal error as printed. Processing ends. Contact Informatica Global Customer Support. DATASPACE CREATION ERROR code An error occurred during dataspace creation with internal error as printed. Processing ends. Contact Informatica Global Customer Support. dbms ENABLED FOR PROPAGATION The specified dbms was enabled for propagation. Processing continues. This message provides an audit trail. dbms PROPAGATION DISABLED The specified dbms was disabled for propagation. Processing continues. This message provides an audit trail. dbms PROPAGATION DISABLE PENDING The specified dbms is being disabled for propagation. Processing continues. This message provides an audit trail. dbms PROPAGATION ENABLE PENDING The specified dbms is being enabled for propagation. Processing continues. This message provides an audit trail. RCM registration HAS INVALID VERSION The registration version did not match. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. UNABLE TO LOAD SCHEMA schema The specified schema could not be loaded. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support.
DTL_RPC001E to DTL_RPC999E: Datacom and IDMS CDC Dataspace Controller 653
DTL_RPC240E Explanation: System Action: User Response: DTL_RPC243E Explanation: System Action: User Response: DTL_RPC244E Explanation: System Action: User Response: DTL_RPC245I Explanation: System Action: User Response: DTL_RPC250E Explanation: System Action: User Response: DTL_RPC251E Explanation: System Action: User Response: DTL_RPC600E Explanation: System Action: User Response: DTL_RPC601E Explanation: System Action: User Response:
UNABLE TO INITIALIZE CONSOLE RC= rc While attempting to initialize the common component for console support, the return code rc was encountered. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. UNABLE TO INITIALIZE DTLXISTL While attempting to initialize the common component for timer management, an error was encountered Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. UNEXPECTED GET CONSOLE STATUS RC= rc The console status rc was give when attempting to get a console. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. PROPAGATION ENVIRONMENT ESTABLISHED The environment is now ready for propagation. Processing continues. This message provides an audit trail. INVALID SUBSCHEMA MODULE TYPE 1 The subschema module name was not IB50 and an error occurred. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. INVALID SUBSCHEMA MODULE TYPE 2 The subschema module name was not SR51 and an error occurred. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. REGISTRATION CAPTURE INVOKATION ERROR return_code An error occurred accessing capture registrations. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. REGISTRATION CAPTURE OPEN ERROR return_code An error occurred accessing capture registrations. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support.
654
DTL_RPC602E Explanation: System Action: User Response: DTL_RPC603E Explanation: System Action: User Response: DTL_RPC604E Explanation: System Action: User Response: DTL_RPC611I Explanation: System Action: User Response: DTL_RPC612I Explanation: System Action: User Response: DTL_RPC990I Explanation: System Action: User Response: DTL_RPC991E Explanation: System Action: User Response: DTL_RPC998I Explanation: System Action: User Response: DTL_RPC999E Explanation: System Action:
REGISTRATION CAPTURE CLOSE ERROR return_code An error occurred accessing capture registrations. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. REGISTRATION CAPTURE READ ERROR return_code An error occurred accessing capture registrations. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. REGISTRATION CAPTURE RETURNED EMPTY DATAMAP Nothing was returned when accessing a capture registration. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. MODULE name IS ACTIVE The specified registration module is currently active. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. MODULE name IS INACTIVE The specified registration module is currently inactive. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. dbms DATASPACE EMPTY/INUSE Status of dataspace. Processing continues. This message provides an audit trail. dbms IS ALREADY UP; PROPAGATION INACTIVE UNTIL JOB IS RECYCLED The stated resource is already up. Propagation is inactive, recycling the job is usually a solution. Processing ends. If investigation does not reveal a solution, contact Informatica Global Customer Support. SHUTDOWN REQUEST IGNORED; PROPAGATION ACTIVE FOR dbms As propagation is still active for the specified database, the shutdown request was ignored. Processing continues. Investigate why this has happened. message See a message and associated messages. Processing ends.
655
User Response:
If investigation does not reveal a solution, contact Informatica Global Customer Support.
DTL_RPS001E to DTL_RPS105I: Datacom MUF Address Space Subtask Exit

DTL_RPS001E Explanation: System Action: User Response: DTL_RPS101I Explanation: System Action: User Response: DTL_RPS102I Explanation: System Action: User Response: DTL_RPS103I Explanation: System Action: User Response: DTL_RPS105I Explanation: System Action: User Response: SYSPRINT DD MISSING The sysprint could not be used, most likely cause is it is missing. Processing ends. Investigate, correct the associated error and resubmit. dbms PROPAGATION INITIALIZATION Propagation was initialized for the specified database. Processing continues. This message provides an audit trail. MUF PROPAGATION INITIALIZATION COMPLETE Propagation initialization complete for the specified database. Processing continues to completion. This message provides an audit trail. MUF PROPAGATION TERMINATED Propagation was terminated for the specified database. Processing continues to completion. This message provides an audit trail. PROPAGATION TERMINATED - INVALID MASTERLIST Propagation ended for the specified database due to invalid "MASTER LIST" format. Processing continues to completion. Investigate, correct the associated error and resubmit.
656
CHAPTER 3
DTL58001 to DTL62591
DTL58001R to DTL62569I: Batch VSAM ECCR, 657
DTL58001R to DTL62569I: Batch VSAM ECCR

This section contains messages for the VSAM batch environmental change capture routine (ECCR). DTL58001R Explanation: System Action: User Response: VCC Reply RETRY/ABEND/IGNORE. The batch VSAM ECCR detected a service request error, as identified in a previous error message. The batch VSAM ECCR issues a WTOR requesting operator intervention and waits for the operator response. Perform one of the following actions:
To continue without the service request, reply ABEND or IGNORE. Otherwise, eliminate the cause of the error and reply RETRY. DTL58004I Explanation: VCC VCCDIR storage directory exceeded. The storage directory, VCCDIR, is not large enough to contain all of the requested anchor storage directory entries in your address space or partition. This is an internal processing error. The batch VSAM ECCR does not anchor the storage in VCCDIR. Contact Informatica Global Customer Support. VCC length bytes {STORAGE|GETMAIN} error REG15=nnn(xx). The program was unable to acquire virtual storage. In the message text:

System Action: User Response: DTL58005I Explanation:
length is the virtual storage length. nnn is the macro name. xx is the VSAM return code. System Action: User Response: The batch VSAM ECCR aborts the request. For a description of the return code, see the appropriate IBM manual.
657
DTL58006I Explanation:
VCC length bytes address {STORAGE|FREEMAIN} error REG15=nnn(xx). The batch VSAM ECCR encountered an error was encountered when it tried to release virtual storage. In the message text:

length is the virtual storage length. address is the virtual storage address. nnn is the macro name. xx is the VSAM return code. System Action: User Response: DTL58007I Explanation: The batch VSAM ECCR aborts the request. For a description of the return code, see the appropriate IBM manual. VCC module_name not found [in ddname]. The batch VSAM ECCR tried to load module module_name into virtual storage, but could not find the module in the search sequence of libraries or, if applicable, in the private library ddname. The batch VSAM ECCR aborts the request. Verify that the library containing the module is included in your JOBLIB or STEPLIB concatenation. Rerun the job. VCC {RESERVE|ENQ|DEQ} error RETCD=nnn(xx) QNAME=qname RNAME=rname. Processing for the macro nnn encountered an error while attempting to acquire or release exclusive control of enqueue name qname and resource name rname. In the message text:

error is the error encountered by the batch VSAM ECCR. nnn is the macro name. xx is the VSAM return code. qname is the enqueue name. rname is the resource name. System Action: User Response: DTL58012I Explanation: The batch VSAM ECCR aborts the request. For a description of the return code, see the appropriate IBM manual. VCC ddname could not be opened for {input|output|update} REG15=nnn(xx) [ACBERFLG=nnn(xx)] [data_set]. The VSAM ECCR encountered an error while attempting to open file ddname for input, output, or update. In the message text:
ddname is the file that VSAM ECCR was trying to open. nnn is the macro name. xx is the VSAM return code. ACBERFLG=nnn(xx) is the macro name and error code, which is displayed if file ddname was a VSAM file. data_set is the data set name. System Action: The batch VSAM ECCR aborts the request.

nnn is the macro name. xx is the VSAM return code.
User Response:
Use the error codes, nnn(xx), and the associated IBM open error message to determine the cause of the error.
658
Chapter 3: DTL58001 to DTL62591
DTL58013I
VCC ddname could not be closed REG15=nnn(xx) [ACBERFLG=nnn(xx)] [data_set]. When the VSAM ECCR tried to close file ddname, an error occurred. In the message text:

ddname is the file that VSAM ECCR was trying to close. nnn is the macro name. xx is the VSAM return code. ACBERFLG=nnn(xx) is the macro name and error code, which is displayed if file ddname was a VSAM file. data_set is the data set name. System Action: User Response: The batch VSAM ECCR aborts the request. Determine the error from the error codes, nnn(xx), and the associated IBM close error message. VCC ddname could not be TCLOSEd REG15=nnn(xx) [ACBERFLG=nnn(xx)][data_set]. An error occurred while attempting to TCLOSE file ddname (CLOSE TYPE=T). If the file was a VSAM file, the ACB error flag is indicated in the message. The data set name may also be in the message. The batch VSAM ECCR aborts the request. For a description of the return code, see the appropriate IBM manual. VCC ddname DD name too long for CONCAT/COPIES. The value of UCCCOPY resulted in an attempt to generate a new ddname longer than eight characters. The length of the sequential qualifier plus the length of ddname determines the total length of the DD name to be generated. The batch VSAM ECCR aborts the request. Contact Informatica Global Customer Support. VCC ddname maximum record length exceeded. The ECCR attempted to write a record that is longer than the definition of the file (ddname) accepts. The batch VSAM ECCR aborts the request. Verify that the length of the record is small enough to be accepted by the file, or increase the maximum record length of the file. VCC ddname minimum record length too short. The ECCR attempted to write a record that is shorter than the definition of the file (ddname) will accept. The batch VSAM ECCR aborts the request. Verify that the length of the record is large enough to be accepted by the file, increase the minimum record length, or if a keyed file, decrease the key length or relative key position. VCC VCCSERV csect request name VCCSERV+xxxxxx. Request not supported. An internal logic error occurred. This is an internal processing error used for debugging. The request is aborted with an abnormal termination. Record the contents of the error message and contact Informatica Global Customer Support.
System Action: User Response: DTL58018I Explanation: System Action: User Response:
DTL58019I Explanation: System Action: User Response:
659
VCC macro error REG15=nnn(xx) [REG0=nnn(xx)]. An error occurred while attempting to issue the specified macro. The batch VSAM ECCR aborts the request. Record the return codes, nnn(xx), and see the description in the appropriate IBM manual to determine your action. VCC ddname macro error REG15=nnn(xx) [REG0=nnn(xx)]. An error occurred while attempting to issue the specified macro. This macro was issued on behalf of a file request. The batch VSAM ECCR aborts the request. Record the return codes, nnn(xx), and see the description in the appropriate IBM manual to determine your action. VCC ddname REG15=nnn(xx) RPLERRCD=nnn(xx) message. A VSAM error was encountered. The ddname, the return code, the RPL error code, and a message are displayed. The text of message is the VSAM ECCRs interpretation of the VSAM error information. A register 15 value of 8 and an RPLERRCD of 92 (5C) usually indicates an out-of-sync condition between the primary and alternate control data sets (CDSs). Action varies according to the type of VSAM error. If the message is considered a warning, the request continues. Otherwise, The batch VSAM ECCR aborts the request. See the appropriate IBM VSAM manual for a complete description of the return codes to help you diagnose the error. If you cannot correct the error, contact Informatica Global Customer Support. In the case of a RPLERRCD of 92 (5C), compare the primary and alternate CDSs to identify any differences. If you determine that one data set is missing some of the records that exist in the other, use IDCAMS to delete/define the smaller data set, and then REPRO the larger. If you are unable to verify that one CDS is complete, you may need to combine the records in both to build a new CDS that contains all records.
VCC ddname physical error

SYNADAF message text.
A QSAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is displayed. The batch VSAM ECCR aborts the request. See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again. VCC ddname physical error
A BSAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is displayed. The batch VSAM ECCR aborts the request. See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again.
660
VCC ddname message

A BDAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is also displayed. The batch VSAM ECCR aborts the request. See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again. VCC ddname message
An ISAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is also displayed. The batch VSAM ECCR aborts the request. See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again. VCC ddname abcode abend error. A system abend was encountered for the data set referred to by ddname. The batch VSAM ECCR aborts the request. See the appropriate IBM manual for a complete description of the associated abend code. VCC ddname physical error. A physical error was encountered for the data set referred to by ddname. The batch VSAM ECCR aborts the request. This message is accompanied by an IBM error message. See the appropriate IBM manual for a description of the associated error message. VCC ddname wrong length record. A wrong-length record was encountered for the data set referred to by ddname. The input buffer is not large enough to contain the contents of a record. The batch VSAM ECCR aborts the request. This message is accompanied by an IBM error message. See the appropriate IBM manual for a description of the associated error message. VCC ddname file is not open. The file must be opened before your request to modify it can be processed. The request for modification is ignored. Verify the file is open before attempting to modify it. VCC ddname file is already open. A request to open a file was made to a file that is already open. This is an internal processing error. The batch VSAM ECCR aborts the request. Contact Informatica Global Customer Support.
DTL58033I Explanation: System Action: User Response: DTL58034I Explanation: System Action: User Response:
DTL58036E Explanation: System Action: User Response: DTL58037I Explanation: System Action: User Response:
661
DTL58038I Explanation: System Action: User Response: DTL58491I Explanation:
VCC ddname filename missing. The file identified by ddname cannot be found. The batch VSAM ECCR aborts the request. Contact Informatica Global Customer Support. VCC VCCJCLOC error REG15=nnn(xx) TUKEY=(xxxx). A dynamic allocation function was requested and an error was detected in the JCL parsing routine or in the parameter list used by VCCSVC99 and VCCJCLOC. The VCCJCLOC return code and the affected text unit key are displayed. The text unit in error is ignored. This is an internal processing error. Contact Informatica Global Customer Support. VCC DYNALLOC PARM list length=length. A dynamic allocation function was requested. This message displays the length of the dynamic allocation parameter list that was generated. This debugging message is specified only if tracing is being performed. Processing continues. No action is required. VCC DYNALLOC text units {pointer list|area} exceeded. A dynamic allocation function was requested and the dynamic allocation parameter list was exceeded. This is an internal processing error. The dynamic allocation request is aborted. Contact Informatica Global Customer Support. VCC DYNALLOC error REG15=nnn(xx). A dynamic allocation function was requested and an error occurred when issuing the SVC 99. The SVC 99 return code is displayed. This is an internal processing error. The dynamic allocation request is aborted. Contact Informatica Global Customer Support. VCC DYNALLOC error-info reason code=(xxxx-xxxx). A dynamic allocation function was requested and an error occurred when issuing the SVC 99. The SVC 99 error and reason codes are specified in hexadecimal. This is an internal processing error. The dynamic allocation request is aborted. Contact Informatica Global Customer Support. VCC DYNALLOC message. A dynamic allocation function was requested and an error occurred when issuing the SVC 99. The SVC 99 error and reason description is specified in the message. This is an internal processing error. The dynamic allocation request is aborted. Contact Informatica Global Customer Support.
System Action: User Response: DTL58493I Explanation: System Action: User Response: DTL58494I Explanation: System Action: User Response: DTL58495I Explanation:
662
DTL58499I Explanation: System Action: User Response: DTL58504E Explanation:
VCC jclstmt. A dynamic allocation function was requested and an error occurred when issuing the SVC 99. The JCL statement in error is displayed. This is an internal processing error. The dynamic allocation request is aborted. Contact Informatica Global Customer Support. VCC parmname is an unrecognized parameter. The product does not recognize the indicated parameter. Only the first eight characters are displayed in the message text. This is an internal processing error. The registration request is bypassed. Processing continues with the next request. Contact Informatica Global Customer Support. VCC Keyword parmname must be followed by a ( or =. The parameter name in the message text was not followed by either a left parenthesis or an equal sign. This is an internal processing error. The registration request is bypassed. Processing continues with the next request. Contact Informatica Global Customer Support. VCC Key = key successfully {updated|added|deleted}. The key in the message was successfully added, deleted, or updated according to your request. Processing continues. No action is required. VCC Key key not found - could not be deleted. A delete was requested for a record of the indicated key, but the key could not be found in the control data set. This is an internal processing error. The automatic registration process is terminated. Contact Informatica Global Customer Support. VCC Invalid subparameter length for parmname. The subparameter name in the message text was specified with too many characters of data. This is an internal processing error. The requested action is bypassed. Contact Informatica Global Customer Support. VCC subparameter is an invalid subparm for parameter. The indicated subparameter is not valid for the parameter. The command is rejected. Processing continues. Correct the control statement and run the job again. For more information on controlling the VSAM ECCR, see PowerExchange CDC Guide for z/OS. VCC Invalid control statement continuation. When a - (blank, hyphen) is used in a control statement, the next record encountered must be a continuation of the control statement.
System Action: User Response: DTL58505E Explanation: System Action: User Response: DTL58513I Explanation: System Action: User Response: DTL58514I Explanation: System Action: User Response: DTL58517E Explanation: System Action: User Response: DTL58527E Explanation: System Action: User Response:
DTL58541E Explanation:
663
The command is rejected. Processing continues. Check the control statement and correct the continuation record as needed, or remove the continuation character. Then, run the change capture job again. VCC KEY=key successfully {added|updated|deleted}. The record identified by key was processed normally. Processing continues. No action is required. VCC System error R15(return_code), R0(feedback_code). An environmental or other internal error occurred. Processing ends. Save all job output and contact Informatica Global Customer Support. VCC Interface module module_name could not be loaded. The program module_name was specified in the VCCCOPT table but could not be loaded. Initialization continues with the next parameter. Contact Informatica Global Customer Support. VCC VSAM CHANGE CAPTURE ACTIVE VSAM change capture is active. No action is required. VCC Interface module module_name disabled after failure. An error occurred in the program module_name. The program module_name is disabled for the remainder of processing in the current job step. Job processing continues. Save the job output and contact the interface vendor. VCC VFL requires MVS/ESA Version 4 or above. VSAM Forklift (VFL) support was specified in the VCCCOPT table but the job is not running under a release of MVS/ESA SP4 or later. VFL initialization ends. Job processing continues. If VFL is required, rerun the job under MVS/ESA Version 4.3 or later. VCC VCCCOPT parameter=value required in down-level MVS. VSAM Forklift (VFL) support was specified in the VCCCOPT table, but a parameter is missing that is required when the job is not running under a release of MVS/ESA SP4 or later. VFL initialization ends. Job processing continues. If VFL is required, rerun the job under MVS/ESA Version 4.3 or later. VCC Internal logic error, R0(fbc) R15(rc). subsysid An internal logic error has been detected. The feedback code (fbc) and the return code (rc) are listed. The job abends with a U0356 abend code.
DTL58571I Explanation: System Action: User Response: DTL60163S Explanation: System Action: User Response: DTL60164E Explanation: System Action: User Response: PWX60165I Explanation: User Response: DTL60166E Explanation: System Action: User Response: DTL60175E Explanation: System Action: User Response: DTL60176E Explanation:
System Action: User Response: DTL60222S Explanation: System Action:

664
User Response:
Contact your Informatica Corporation technical support representative and provide the return code (rc). VCC Journaling in effect for program dataset. The batch journaling feature has begun journaling changes to the indicated data set on behalf of the indicated program. Processing continues. No action is required. VCC Journaling not in effect for program dataset. The batch journaling feature was attempting to journal changes to the indicated dataset on behalf of the indicated program and encountered an error. The system performs one of the following actions, based on how the JRNLERR parameter of the VSAM ECCR journal control table (VCCJCT) was specified:

DTL60500I Explanation: System Action: User Response: DTL60501S Explanation: System Action:
ABEND The batch job step abnormally ends. NOABEND Journaling does not take place; batch job processing continues. This is the default. OPERATOR The console operator must specify the action to be taken. User Response: DTL60502I See the accompanying messages. VCC nnnn fileid journal records were inserted by exit exit_pgm.
nnnn fileid journal records were deleted by exit exit_pgm. nnnn fileid journal records were created on dataset. nnnn fileid log records were created on dataset.
Explanation:
These messages are statistical, where nnnn identifies the number of records and fileid identifies the VSAM file. The installation-written exit program is identified by exit_pgm and the journal or log is identified by dataset. Processing continues. No action is required. VCC {JNL|LOG}
(OPN=nnn, RDU=nnn, ADD=nnn, UPD=nnn, DEL=nnn, TOT=nnn) data_set.
System Action: User Response: DTL60503I
or {KSDS|ESDS|RSDS|PATH}
(OPN=nnn, RDU=nnn, ADD=nnn, UPD=nnn, DEL=nnn, CLO=nnn) data_set.
Explanation:
The first form of this message reports the number of journal records written to journal (JNL) and/or log (LOG) for each activity and the name of the journal or log data set. The activities are opens (OPN), reads-for-update (RDU), adds (ADD), updates (UPD), deletes (DEL), and closes (CLO). TOT reflects the sum of the other activity records. The second form reports the type of VSAM file being journaled, the type and quantity of each activity, and the name of the VSAM data set. OPN and CLO reflect the number of records in the data set when it was opened or closed.
Processing continues. No action is required.
665
DTL60504I Explanation: System Action: User Response: DTL60505S Explanation:
VCC Has been terminated by exit exit_routine. A user-defined exit routine (exit_routine) requested that change capture processing be terminated. VSAM ECCR processing ends. Determine why the installation exit program requested the termination. VCC ddname Spanned CI processing is not supported. An attempt was made to capture changes from the ddname VSAM file. The VSAM file contains spanned records, and it was accessed in control interval (CI) mode. The VSAM ECCR does not support CI processing for spanned records. VSAM ECCR processing ends. Do not attempt to capture changes for a file containing spanned records if it is being accessed in control interval mode. Exclude the program or cancel the registration for the VSAM source file. VCC ddname VSAM organization not supported. An attempt was made to capture changes from the ddname VSAM file. The VSAM file organization was not KSDS, ESDS, or RRDS. The job continues and changes will not be captured. Do not attempt to capture changes from VSAM files that are not KSDS, ESDS, or RRDS. Turn off the registration for the VSAM source file. VCC ddname VSAM {SHOWCB|TESTCB} error. REG0=nnn(xx). The VSAM ECCR received a nonzero return code when it executed the macro shown in the message. VSAM ECCR processing ends. Contact Informatica Global Customer Support. VCC ddname DYNALLOC error xxxx-xxxx [text]. An error was encountered while attempting to dynamically allocate the primary or alternate control data set (CDS). The code (xxxx-xxxx) indicates the error and reason codes returned to SVC 99. Processing ends. Contact Informatica Global Customer Support. VCC fileid {log|journal} buffers saved to dataset. The contents of the log or journal buffers for the VSAM file identified by fileid were saved to the emergency log data set identified by data set. Processing continues. No action is required. The emergency log data set should be concatenated with other journals if a backout becomes necessary. VCC fileid {log|journal} buffers not saved-no before images in memory. No before-image records were found in memory. Processing continues. No action is required.
DTL60506S Explanation: System Action: User Response:
DTL60507S Explanation: System Action: User Response: DTL60508E Explanation:
System Action: User Response: DTL60510I Explanation: System Action: User Response:
666
DTL60516S Explanation: System Action: User Response: DTL60517S Explanation: System Action: User Response: DTL60566S Explanation: System Action: User Response:
VCC Storage at address has been corrupted. The storage at address has been destroyed. VSAM ECCR processing ends. Contact Informatica Global Customer Support. VCC VSAM path or base cluster component is not in the JCT for ddname=ddname. The VSAM ECCR's journal control table (VCCJCT) must contain both the base cluster of a sphere and related paths, but one of the components (ddname) was missing. Message DTL60501S follows. Contact Informatica Global Customer Support. VCC VCC0192A was not found in JOBLIB/STEPLIB. The VCC0192A module was not found in the JOBLIB or STEPLIB concatenation. This module is required for VSAM ECCR processing. VSAM ECCR processing ends. Make sure that either a JOBLIB or STEPLIB DD statement is specified in the change capture job, that the specified library is APF-authorized, and that the library contains the VCC0192A module. Then, run the job again. VCC SOC3 ABEND requested for module exit data_set. An error occurred while the indicated module was capturing changes from the indicated data_set. The VSAM exit that was being processed is also indicated. The VSAM ECCR ends with a SOC3 abend whenever a severe error is encountered. See the accompanying messages. VCC abcode ABEND encountered in module [exit data_set]. An abend occurred in the indicated module while the journaling program was journaling changes. If the error occurred in a Informatica Corporation module, the VSAM exit being processed and the data_set being journaled are displayed. The abend continues. If the error occurred in a PowerExchange module, contact Informatica Global Customer Support. VCC (PSW) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
(0-3) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx (4-7) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx (8-11) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx (12-15) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
DTL60570S Explanation: System Action: User Response: DTL60571E Explanation: System Action: User Response:
DTL60573I
An abend occurred. Processing continues. Save the information for debugging if you need to contact Informatica Global Customer Support. VCC ESTAE error REG15=nnn(xx). An error occurred while issuing the MVS ESTAE macro. Processing continues. Contact Informatica Global Customer Support.
DTL60579E Explanation: System Action: User Response:
667
DTL60580E Explanation: System Action: User Response: DTL60582S Explanation: System Action: User Response:
VCC nnnn bytes not allocated. Insufficient storage is available to satisfy the request for nnnn bytes. Change capture processing ends. Increase the region size and run the job again. VCC module not available [REG15=nnn(xx)] The module identified in the message could not be found or, if an error code is displayed, an error occurred while attempting to load the module. Processing ends. Ensure that the library containing the indicated module is in the STEPLIB, JOBLIB, or the system link list, and run the job again. If MVS could not load the module, see the associated IBM error messages. VCC Reply RETRY ABEND or IGNORE. A change capture error was encountered and the console operator must specify how to continue. The operator reply was requested through the JRNLERR=OPERATOR parameter in the VSAM ECCR journal control table (VCCJCT). A response of RETRY will direct the journaling program to retry the operation. A response of ABEND causes the job to terminate. A response of IGNORE directs the journaling program to stop journaling the changes to the VSAM data set specified in the associated error message, but the application program continues processing. The console operator should reply RETRY, ABEND, or IGNORE. VCC This module must run in 31 bit addressing mode. VCCADHK was relinked as AMODE(24) or it is being run on an MVS/370 system. VCCADHK ends. Make sure that VCCADHK is linked as AMODE(31) and is being run on an MVS/ESA system. VCC Requested syncpoint syncid has been written to dataset. The batch syncpoint process invoked explicitly by PWXEDMJSYNC has written a syncpoint record with the indicated numeric syncid to the log data set specified by dataset. Processing continues. No action is required. VCC End-of-task syncpoint syncid has been written to dataset. The batch syncpoint process invoked implicitly at normal task termination has written a syncpoint record with the indicated numeric syncid to the journal or log data set specified by dataset. Processing continues. No action is required. VCC Load of the installation options table, VCCCOPT, has failed. An attempt to load the CICS Integrity Series products installation options table, VCCCOPT, was unsuccessful. This message is accompanied by one or more messages describing the reason for the load failure. The ECCR continues processing and issues a return code of 4.
DTL60590R Explanation:
System Action:
User Response: DTL60598S Explanation: System Action: User Response:
DTL60631I Explanation: System Action: User Response: DTL60632I Explanation:
System Action: User Response: DTL60878E Explanation: System Action:
668
User Response: DTL60879I Explanation:
Contact Informatica Global Customer Support. VCC Product distribution defaults will be enforced for this execution. The VSAM ECCR was unable to load an installation options table, VCCCOPT, customized for your site requirements. A default table supplied on the distribution tape will be used. The ECCR continues processing and issues a return code of 4. This message is accompanied by one or more messages describing the reason the VSAM ECCR was unable to obtain the installation options table. VCC A back level (vv.rr.mm) of the installation options table, VCCCOPT, has been loaded. An obsolete version of the installation options table, VCCCOPT, was loaded by the VSAM ECCR. Execution continues using a default VCCCOPT supplied on the distribution tape. A return code of 4 accompanies this message. Contact Informatica Global Customer Support. VCC Invalid variable control statement. subsysid The job encountered a control statement within <*BEGINVAR> and <*ENDVAR> statements with an invalid format. The format of variable substitution statements in SAMPVARS is <*SS S=@var_symbolV=&value*> Processing ends. If you are running the installation jobs in batch, verify your variable control statements in the SAMPVARS member. If you cannot determine the problem, or if you are using the online installation facility, contact Informatica Global Customer Support. VCC variable is an invalid variable symbol. subsysid The format of variable substitution statements in SAMPVARS is <*SS S=@var_symbolV=&value*> The job encountered a variable following the S= that it did not recognize.
DTL60880E Explanation: System Action: User Response: DTL62559E Explanation:
System Action: User Response: DTL62561E Explanation:
Processing ends. Contact Informatica Global Customer Support. VCC Invalid variable construct - missing {S|V}. subsysid The job encountered a statement that was missing the S= or V= symbol. The format of variable substitution statements in SAMPVARS is:
<*SS S=@var_symbolV=&value*>
System Action: User Response: DTL62562E Explanation:
Processing ends. Contact Informatica Global Customer Support. VCC Variable length for var_symbol was exceeded. subsysid The job encountered a variable symbol that was longer than 10 characters. The format of variable substitution statements in SAMPVARS is:
<*SS S=@var_symbolV=&value*>
Processing ends. Contact Informatica Global Customer Support.
669
VCC Substitute length for value was exceeded. subsysid The job encountered a value that was longer than the expected value. The format of variable substitution statements in SAMPVARS is: <*SS S=@var_symbolV=&value*> Processing ends. Contact Informatica Global Customer Support. VCC Invalid library name: ddname. subsysid The data set referenced by ddname does not exist. Processing ends. Contact Informatica Global Customer Support. VCC Processing library: ddname. subsysid The installation job lists each DD name as it is referenced during processing. Processing continues. No action is required. VCC Installation bypassed for: membername. subsysid This message lists each member name that was unloaded from the product tape, but was not selected for processing because the product was not selected for installation. Processing continues. No action is required. VCC Member selected for installation is: membername. subsysid
System Action: User Response: DTL62564E Explanation: System Action: User Response: DTL62565I Explanation: System Action: User Response: DTL62566I Explanation: System Action: User Response: DTL62567I Explanation: System Action: User Response: DTL62568I Explanation: System Action: User Response: DTL62569I Explanation: System Action: User Response:
This message lists each member name that was unloaded from the product tape as it is selected for processing because the product was selected for installation. Processing continues. No action is required. VCC Symbol length was exceeded. subsysid The JCL generating job encountered a variable symbol greater than 11 characters. Processing continues. No action is required. VCC var_symbol symbol was not found. subsysid The JCL generating job expected input for the variable symbol var_symbol, but did not receive it. Processing continues. No action is required.
670
CHAPTER 4
PWXEDM172000 to PWXEDM173002

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent, 671 PWXEDM172500I to PWXEDM172798I: The PowerExchange Logger, 709 PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC), 759 PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger, 772
PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent

PWXEDM172000W Undefined message number msgnumber Explanation: A module issued a Informatica Corporation message number msgnumber, but the message module does not define this number. This message is substituted for the undefined message. Processing continues. Contact Informatica Global Customer Support. module: EDM Agent. Version v.rr.mm. The PowerExchange Agent issues this message during initialization to supply the following information:

System Action: User Response: PWXEDM172001I Explanation:
Version number (v) Release number (rr) Modification number (mm) System Action: User Response: Processing continues. No action is required.
671
PWXEDM172002I Explanation:
module: ChangeDataMove. Version v.rr.mm. Release date: date The PowerExchange Agent issues this message in the early stages of initialization to inform you of the following information for PowerExchange:

Version number (v) Release number (rr) Modification number (mm) Release date (date) System Action: User Response: PWXEDM172003I Explanation: System Action: User Response: Processing continues. No action is required. module: Processing terminated, Return code=rc. The PowerExchange Agent ended processing with a return code of rc. Processing continues. No action is required. For more information about the return code, see Return Codes 0 to 12: PowerExchange Agent on page 917. module: EDM Agent must run as an MVS started-task You attempted to run the PowerExchange Agent in a batch or TSO address space. The PowerExchange Agent ends. Run the PowerExchange Agent as an MVS started task. module: TESTAUTH failed. program must execute with APF authorization You attempted to run the PowerExchange Agent from a library that is not an APF-authorized load library. If any unauthorized libraries are included in the STEPLIB concatenation, APF-authorization is dropped for all of them. The PowerExchange Agent ends. Authorize the load library from which the PowerExchange Agent is to be run. You can use the MVS SETPROG command to perform the library authorization. module: OPEN of ddname file failed PowerExchange cannot open the file with the DD name ddname. Processing of file ddname ends. If the ddname is EDMSCTL, the PowerExchange Agent ends. If the DD name is EDMSCTL, supply a valid PowerExchange Agent control file. For any other DD name, determine the cause of the error, correct the problem and run the job again. If you cannot determine the cause of the problem, contact Informatica Global Customer Support. module: The ddname file has an invalid format The PowerExchange Agent startup parameter data set with DD name ddname has an invalid data set format and cannot be processed. The PowerExchange Agent ends. Verify that the PowerExchange Agent startup parameter data set is a sequential (PS) data set with fixed-length, 80-byte record. Then, run the job again.
PWXEDM172004E Explanation: System Action: User Response: PWXEDM172005E Explanation:
PWXEDM172006E Explanation: System Action: User Response:
672
Chapter 4: PWXEDM172000 to PWXEDM173002
PWXEDM172008I Explanation: System Action: User Response: PWXEDM172009E Explanation: System Action: User Response:
module: action ddname file The PowerExchange Agent control file is about to be processed or has been processed as shown by action. Processing continues. No action is required. module: An error was found in the ddname file: PowerExchange found an error in the PowerExchange Agent startup parameter data set (control file). Subsequent messages describe the error. The PowerExchange Agent ends. Determine the cause of the error, edit the PowerExchange Agent startup parameter data set (control file), and restart the PowerExchange Agent.
PWXEDM172010{I|W|E}module: text Explanation: System Action: User Response: PWXEDM172011E Explanation: System Action: User Response: PWXEDM172012E Explanation: System Action: User Response: This message provides additional information related to the previously displayed message or messages. Processing continues. Your response varies depending on which related messages and message text you received. module: The default operand for the keyword keyword is invalid A default operand for the specified keyword is invalid. This is an internal program error. The PowerExchange Agent ends. Contact Informatica Global Customer Support. module: A logic error has been detected An unrecoverable internal program error has been detected. The currently active task abends. Collect all available information about the error. Contact Informatica Global Customer Support. module: LOAD Failed. Module=module_name, Code=abend_code, Reason=reason A LOAD macro was issued for the module module_name, but the MVS Contents Supervision could not locate the module. The resulting abend and reason codes are indicated by abend_code and reason. The PowerExchange Agent ends. Verify that all required load libraries are included in the PowerExchange Agent STEPLIB or JOBLIB concatenation, and start the PowerExchange Agent again. For more information about the abend code and reason code, see Reason Codes 001 to 255: PowerExchange Agent on page 918 and Abend Code U0001: PowerExchange Agent on page 914. module: Reason: explanation This message further explains an error found in the PowerExchange Agent startup parameter data set (control file). Processing continues. Determine the cause of the error, edit the PowerExchange Agent startup parameter data set (control file), and restart the PowerExchange Agent.
PWXEDM172013E Explanation:
PWXEDM172014I Explanation: System Action: User Response:
673
module: GETMAIN failed for initialization control block The PowerExchange Agent could not get the storage required for its initialization processing. The PowerExchange Agent ends. Increase the region size, and restart the PowerExchange Agent. module: A valid JOBLIB or STEPLIB DCB could not be found. The PowerExchange Agent must run with a valid JOBLIB or STEPLIB concatenation. A valid JOBLIB or STEPLIB concatenation must contain all of the modules that the PowerExchange Agent loads. However, the PowerExchange Agent could not find a valid JOBLIB or STEPLIB concatenation. The PowerExchange Agent ends. Create a valid JOBLIB or STEPLIB concatenation. Then, run the job again. module: VSAM ECCR support not installed by a prior CCVActive=YES keyword, command rejected The user issued a CCV command, but the ECCR code is not loaded in the LPA. For activation, at least one CCVActive=YES parameter must be specified between system IPLs. Processing continues without the VSAM ECCR. Specify the CCVActive=YES keyword for the PowerExchange Agent configuration parameters, and restart the PowerExchange Agent. module: VSAM ECCR status This message signals the installation or refresh of the VSAM ECCR. Processing continues. No action is required. module: Another EDM Agent is running with AgentID agentid The PowerExchange Agent that is currently initializing detected another PowerExchange Agent already running that has the same agentid. The PowerExchange product stops processing the currently initializing PowerExchange Agent. Determine which instance of the PowerExchange Agent should be running. If the PowerExchange Agent that should be run is the one that is initializing, use the SHUTDOWN command to terminate the currently running PowerExchange Agent. module: Existing SSCVT agentid was not built by an EDM Agent and cannot be used. The PowerExchange Agent that is currently initializing, detected the presence of an MVS SSCVT that matches its specified agentid. However, the SSCVT was not built by the PowerExchange Agent. Therefore, it cannot be used. The PowerExchange Agent ends. Verify that the agentid does not conflict with an existing MVS SSCVT. If there is no conflict, use the SSCVT address to do a PowerExchange Agent cold start and refresh the SSCVT.
System Action: User Response: PWXEDM172017I Explanation: System Action: User Response:
674
module: STORAGE OBTAIN failed for SubPool subpool. EDM Agent agentid cannot be initialized The PowerExchange Agent that is currently initializing could not get common storage for its global control blocks. This condition indicates that a severe shortage of CSA or ECSA exists. The PowerExchange Agent ends. Restart the PowerExchange Agent when CSA or ECSA storage is available. module: EDM Agent agentid appears to be active and cannot be initialized A previous execution terminated without completing its termination processing. Consequently, the currently initializing PowerExchange Agent could not reclaim its global environment. A failure in the PowerExchange Agent recovery processing can cause this problem. The PowerExchange Agent ends. Collect all available information about the error. Contact Informatica Global Customer Support. module: Active=total1_modules, Inactive=total2_modules This message shows the number of active and inactive CCV0192A modules found on the LPAQ. Processing continues. No action is required. module: New control_block built for EDM Agent agentid. Addr=address The PowerExchange Agent identified by agentid has established its global environment and anchored that environment from the specified control block at the address indicated in address. Processing continues. No action is required. module: STORAGE OBTAIN failed for work_area The currently initializing PowerExchange Agent could not get common storage for the indicated work area. This condition indicates that a severe shortage of ECSA exists. The PowerExchange Agent ends. Restart the PowerExchange Agent when ECSA storage is available. module: EPA for generic ESTAEX/ARR module has not been established The PowerExchange Agent could not determine the address of its generic ESTAE-type recovery routine. This condition indicates that an internal logic error occurred. The PowerExchange Agent ends. Collect all available information about the error. Contact Informatica Global Customer Support. module: ESTAEX failed. Return Code=rc, Reason=reason The PowerExchange Agent could not establish an ESTAE-type environment because the ESTAEX macro failed. The macro provides the return and reason codes shown. The PowerExchange Agent ends.
System Action: User Response: PWXEDM172022E Explanation:
PWXEDM172023I Explanation: System Action: User Response: PWXEDM172024I Explanation:
System Action: User Response: PWXEDM172025E Explanation: System Action: User Response: PWXEDM172026E Explanation: System Action: User Response:
PWXEDM172027E Explanation: System Action:
675
User Response:
Collect all available information about the error. Contact Informatica Global Customer Support. For more information about the abend code and reason code, see Reason Codes 001 to 255: PowerExchange Agent on page 918 and Abend Code U0001: PowerExchange Agent on page 914. module: LOAD of module module resolved to the LPA During its initialization, the PowerExchange Agent attempted to load a module, but it does not reside in a JOBLIB or STEPLIB concatenation. The PowerExchange Agent ends. Verify that the required module is in a JOBLIB or STEPLIB concatenation, and start the PowerExchange Agent again. module: STORAGE OBTAIN failed for recovery work area Storage could not be obtained for a PowerExchange Agent recovery work area. The PowerExchange Agent ends. Increase the region size, and start the PowerExchange Agent again. If increasing the region size does not fix the problem, collect all available information about this error. Contact Informatica Global Customer Support. module: ESTAEX/ARR invoked for ABEND code=abend, Reason=reason, PSW=psw An abend condition invoked the PowerExchange Agent module ESTAEX/ARR. The message displays the abend and reason codes in the abend and reason fields and displays the abend program status word (PSW) in the psw field. The abend processing continues. Determine the cause of the abend or contact Informatica Global Customer Support. module: register_type start_registerend_register register register register register This message describes an abend condition. The message text contains the following variables:
register_type is either GPR or AR. start_register is the first register being dumped. end_register is the last register being dumped. register contains the contents of a register. This message is issued until the contents of all registers are displayed: four times for 16 registers, or eight times if access registers are included. System Action: User Response: PWXEDM172032E Explanation: System Action: User Response: Processing continues. No action is required. module: STORAGE OBTAIN failed for persistent module module_name Storage could not be obtained for globally loading the module_name module. This indicates a severe shortage of CSA, ECSA, SQA, or ESQA. The PowerExchange Agent ends. Restart the PowerExchange Agent when storage is available.
676
PWXEDM172033W module: PMP deleted. Module=module_name, Addr=address Explanation: System Action: User Response: PWXEDM172034E Explanation: The persistent module module_name has been removed from common storage. The variable address indicates the address of the prefix area. Processing continues. No action is required. module: No room in agentid SSVT function list for persistent module module The subsystem exit module indicated by module could not be linked into the PowerExchange Agent SSVT function matrix, because there are no free entries remaining. This condition indicates an internal program error. The PowerExchange Agent ends. Collect all available information about the error. Contact Informatica Global Customer Support. module: STORAGE OBTAIN failed for CDE/XTLST area for persistent module module The PowerExchange Agent could not get storage in subpool 245 for the CDE/XTLST area. The storage is required for the module identified by module. This condition indicates a severe shortage of SQA storage. The PowerExchange Agent ends. Restart the PowerExchange Agent when more SQA storage is available. module: Architectural incompatibility detected. Old version=(oldarch/oldver), New version=(newarch/newver) The PowerExchange Agent currently initializing detected an architectural incompatibility in one or more control blocks. The existing PowerExchange Agent cannot be reused. The old and new architectures are shown in the oldarch/oldver and newarch/newver fields, respectively. The PowerExchange Agent ends. Issue a DRAIN command for the PowerExchange Agent, then use the SHUTDOWN COMPLETELY command to terminate PowerExchange Agent processing. After the PowerExchange Agent ends, you can restart it normally. module: EDMSINIT request rejected. EDM Agent agentid is status The PowerExchange Agent is drained or in the process of draining and has rejected an EDMSINIT request. An error message preceding this one displays the task that issued the request and the resulting return and reason codes. The message text contains the following variables:

module is the failing module. agentid is the PowerExchange Agent. status is the status of the draining process. System Action: User Response: The PowerExchange Agent rejects the EDMSINIT call. The function that issued the request may also fail. Issue a RESUME command to allow EDMSINIT calls, if necessary.
677
PWXEDM172038{W|I|E}module: EDM Agent agentid is status Explanation: A module issued a DRAIN, RESUME, or SHUTDOWN COMPLETELY command for the specified PowerExchange Agent. In the message text:
W, I, or E is the message suffix. The meaning depends on the message suffix. W. If you receive a warning message, a preceding error message indicates which command was issued. If a DRAIN command was issued, it could not be accepted because the PowerExchange Agent was already drained or in the process of draining. If a RESUME command was issued, it could not be accepted because the PowerExchange Agent was not drained or was in the process of draining. I. If you receive an informational message, a RESUME command was issued for the specified PowerExchange Agent and the PowerExchange Agent has been resumed. E. If you receive an error message, a SHUTDOWN COMPLETELY command was issued for the specified PowerExchange Agent, but the PowerExchange Agent is not drained. module is the module that issues the command. agentid is the PowerExchange Agent ID. status is the status. System Action: The system takes one of the following actions based on the message suffix:
W. Command processing stops. I. Processing continues. E. SHUTDOWN COMPLETELY command processing stops. User Response: Take one of the following actions based on the message suffix:
W. Determine whether the PowerExchange Agent status is what you want. If required, issue a DRAIN or RESUME command. I. No action is required. E. Drain the PowerExchange Agent and reissue the SHUTDOWN COMPLETELY command. PWXEDM172039I Explanation: module: The following JES2 Initiators must be drained before EDM Agent agentid can drain: A DRAIN command was issued for the specified PowerExchange Agent. However, due to SUBSYS DD affinities with the PowerExchange Agent, certain JES2 initiator tasks are currently registered for PowerExchange Agent services. The PowerExchange Agent cannot drain until all registered tasks have terminated. This message is followed by one or more messages listing those initiators that must be drained to allow all registered tasks to terminate. The PowerExchange Agent remains in draining status. Drain the specified initiators with the $PIx JES2 command to enable the PowerExchange Agent to complete draining. After each initiator has been drained, you can restart it. module: A command command is currently pending The PowerExchange Agent rejected the specified command because a conflicting command is currently pending. For example, this message is displayed if you issue a SHUTDOWN command followed by a SHUTDOWN COMPLETELY command. Processing ends. Reissue the correct command or wait for the pending command to time-out, then reissue the command.
678
module: STORAGE OBTAIN failed for VSAM OPEN/CLOSE intercept CDE/XTLST area. Subpool=subpool The PowerExchange Agent could not get the storage required to build a CDE/XTLST area for a VSAM ECCR OPEN/CLOSE intercept. The storage was requested in the indicated subpool. This usually indicates a shortage of common storage. Additional messages may be issued indicating the impact of this condition. Functions that depend on the CDE or XTLST area are unavailable. Restart the PowerExchange Agent when more common storage is available. module: Unsupported MVS release. MVS SP4.3.0 or higher is required for execution The PowerExchange Agent was started on an unsupported release of MVS. Your site must have MVS Version 4 Release 3 or later installed to run PowerExchange. The PowerExchange Agent ends. Upgrade to a compatible version of MVS. module: Data at PSW address - word1 word2 word3 word4 word5 word6 This message provides additional information about an abend. The word fields contain 24 bytes of data from the abend program status word (PSW). The abend processing continues. Use the information in this message and any related messages to determine the reason for the abend. Contact Informatica Global Customer Support. module: Refresh SSCVT for AgentId agent_ID ignored. Addr=address This message can display during a cold or warm start. If the existing MVS SSCVT for the PowerExchange Agent is
System Action: User Response: PWXEDM172042E Explanation: System Action: User Response: PWXEDM172043I Explanation: System Action: User Response:
PWXEDM172044I Explanation: System Action:
Not in errorthe PowerExchange Agent proceeds with the normal startup request, using the existing SSCVT to continue processing. In errorand the PowerExchange Agent SSCVT does not match the refresh SSCVT statement in the EDMSCTRL module, the PowerExchange Agent startup process ends with message PWXEDM172020. User Response: If the existing MVS SSCVT for the PowerExchange Agent is:

Not in error Remove the REFRESHSSCVT= statement from the EDMSCTRL module. In error Update the REFRESHSSCVT= statement from the EDMSCTRL module with the correct SSCVT, and do a PowerExchange Agent cold start to refresh the SSCVT or perform an initial program load (IPL). PWXEDM172045I Explanation: module: External {activation|deactivation} of VSAM Batch ECCR detected by Agent agent_ID The PowerExchange Agent detected that the status of the VSAM batch ECCR was changed by some other agent. Because the VSAM batch ECCR is activated globally for one z/OS system, the action of activating or deactivating this ECCR affects all PowerExchange Agents on that z/OS system. Processing continues. If the change in the VSAM batch ECCR is acceptable, no action is required. If you wish to change the status, issue the STOP or START command for the PowerExchange Agent with the appropriate VSAMECCR operand.
679
module: Sysplex Message Log operation failed. Code=return_code, Rsn=reason_code A module encountered an error while attempting to perform an operation using the PowerExchange sysplex message log. The PowerExchange Agent stops its attempts to record messages in the PowerExchange sysplex message log, but the PowerExchange Agent message logging into the PowerExchange Agent EDMSLOG data set continues. Contact Informatica Global Customer Support.
User Response:
PWXEDM172047W module: MVS Logger operation failed for stream name stream_name, Code=return_code, Rsn=reason_code Explanation: A module encountered an error while attempting to connect to a MVS system logger stream using the IXGCONN macro to generate the specified stream name. The PowerExchange Agent attempted to connect to a MVS system logger stream, because the SysplexLogDays startup parameter for the PowerExchange Agent, which specifies the retention period for messages in the PowerExchange sysplex message log, was non-zero. It is possible that the MVS system is not in a parallel sysplex or that the stream name is not defined for the MVS system logger component. System Action: The PowerExchange Agent stops its attempts to record messages in the PowerExchange sysplex message log, but the PowerExchange Agent message logging into the PowerExchange Agent EDMSLOG data set continues. Verify that the PowerExchange sysplex message log is correctly set up. For more information about the IXGCONN return and reason codes, see the IBM MVS programming documentation for your MVS version. Contact Informatica Global Customer Support. module: MVS Logger Connect failed for stream name stream_name, Code=return_code, Rsn=reason_code A module encountered an error while attempting to perform a MVS logger operation using the PowerExchange sysplex message log. The PowerExchange Agent stops its attempts to record messages in the PowerExchange sysplex message log, but the PowerExchange Agent message logging into the PowerExchange Agent EDMSLOG data set continues. If the MVS logger operation is IXGCONN, IXGDELET, IXGBRWSE, or IXGWRITE, see the IBM MVS programming documentation for your MVS version for more information about the return and reason codes for the operation. Correct any environmental problems, then restart the PowerExchange sysplex message log by stopping and restarting the LOG subtask of the PowerExchange Agent. Contact Informatica Global Customer Support. module: agentid Command Exit. Command buffer could not be found The PowerExchange Agent agentid attempted to process an operator command but could not find the command buffer. This indicates an internal program error. The PowerExchange Agent ends command processing. Collect all available information about the error. Contact Informatica Global Customer Support. module: agentid function_name Exit. STORAGE OBTAIN failed for work area Storage could not be obtained for processing the subsystem exit function function_name for the PowerExchange Agent agentid. Processing of the exit ends.
User Response:
User Response:
680
User Response: PWXEDM172052I Explanation: System Action: User Response: PWXEDM172053E Explanation:
No action is required. module: agentid Command Exit. command command has been queued for execution The PowerExchange Agent agentid accepted the command and placed it in the command buffer for subsequent processing. Processing continues. No action is required. module: agentid function Exit ABENDed. Code=abend_code, Reason=reason,PSW=psw The subsystem function shown in function for the PowerExchange Agent indicated by agentid abended. This message displays the cause of the abend in the abend_code and reason fields and displays the abend program status word (PSW) in the psw field. Subsystem exit processing ends. Also, the function that requested the service may fail. Collect all available information about the error. Contact Informatica Global Customer Support. For more information about the abend code and reason code, see Reason Codes 001 to 255: PowerExchange Agent on page 918 and Abend Code U0001: PowerExchange Agent on page 914.
PWXEDM172054W module: agentid Command Exit. command command rejected Agent is not active Explanation: The PowerExchange Agent command exit accepted the valid command in command. However, the PowerExchange Agent agentid is not active. Therefore, the command cannot be queued for processing. The PowerExchange Agent rejects the specified command. Start the specified PowerExchange Agent, and enter the command again.
PWXEDM172055W module: agentid Command Exit. Null command ignored Explanation: System Action: User Response: The PowerExchange Agent agentid detected a command that has no text following the command prefix. The PowerExchange Agent rejects the command. Enter the command again. For the correct command syntax, see the PowerExchange Command Reference. module: agentid Command Exit. 'command' is not a valid EDM Agent command The PowerExchange Agent agentid detected an invalid command. The PowerExchange Agent rejects the specified command. Enter the command again. For the correct command syntax, see the PowerExchange Command Reference. module: agentid Command Exit. command command has too {many|few} operands. {minimum|maximum} operand count is n A command sent to the PowerExchange Agent agentid contained too many or too few operands. The minimum or maximum operand count is specified by n. The PowerExchange Agent rejects the specified command. Enter the command again. For the correct command syntax, see the PowerExchange Command Reference.
681
module: agentid Command Exit. command command rejected insufficient buffer space The PowerExchange Agent agentid accepted a valid command. However, the command buffer did not have enough space for the command to be queued. The PowerExchange Agent rejects the specified command. Enter the command again. If the error persists, contact Informatica Global Customer Support. You may need to issue a CANCEL command to shut down the specified PowerExchange Agent. module: SRB failed. Function=function, Return Code=rc An SRB, which the PowerExchange Agent scheduled, encountered an error during processing of the specified function. This message also displays the return code rc. The SRB function ends. Depending on the error, the PowerExchange Agent may terminate, also. Collect all available information about the error. Contact Informatica Global Customer Support. For more information about the return code, see Return Codes 0 to 12: PowerExchange Agent on page 917. module: {Code=abend_code|Return Code=rc}, {Reason=reason|Date=text} psw This message provides additional information about an SRB failure.
If the SRB error causes an abend, abend_code provides the abend code, reason provides the reason code associated with the abend, and psw provides the program status word (PSW) associated with the abend. If the SRB error does not cause an abend, rc provides the return code and text provides function-specific information about this error. The PSW is not provided for this type of error. System Action: User Response: The SRB function ends. Based on the error, the PowerExchange Agent might also stop. For more information about the abend code, return code, and reason code, see Return and Reason Codes on page 913. Collect all available information about the error. Contact Informatica Global Customer Support. module: {AXSET|AXRES|ATSET} failed. Code=abend_code, Reason=reason The specified AXSET, AXRES, or ATSET macro abended. abend_code and reason provide additional information about the abend. The PowerExchange Agent ends. For more information about the abend code and reason code, see Reason Codes 001 to 255: PowerExchange Agent on page 918 and Abend Code U0001: PowerExchange Agent on page 914. Collect all available information about the error. Contact Informatica Global Customer Support. module: agentid function Exit status The subsystem exit specified by function has been entered or exited for the PowerExchange Agent identified in agentid. Processing continues. No action is required.
682
PWXEDM172063E Explanation: System Action: User Response: PWXEDM172064I Explanation:
module: STORAGE OBTAIN failed for SRB control block Storage could not be obtained in subpool 239 for the PowerExchange Agent SRB control block. This error indicates a severe shortage of SQA or ESQA. The PowerExchange Agent ends. Start the PowerExchange Agent again when SQA and ESQA are available. module: Dataspace status. Name=name, STOKEN=stoken, Blocks=blocks This message displays the status of the PowerExchange Agent common data space:
status indicates whether the PowerExchange Agent created the data space or located the common data space. name is in the format nnnnnEDM, where nnnnn is a prefix assigned to the data space by MVS. stoken displays the unique ID that MVS associates with the data space. blocks shows the size of the data space in 4 KB blocks. System Action: User Response: PWXEDM172065E Explanation: Processing continues. No action is required. module: RACROUTE AUTH failed. SAF Return Code=safrc, Return Code=rc, Reason=reason A PowerExchange component attempted to register itself for the PowerExchange Agent services. However, the job or user did not have authority to use the PowerExchange Agent services. This message displays the SAF return code in safrc, the RACF or equivalent return code in rc, and the reason code in reason. The PowerExchange Agent writes the RACF or equivalent messages associated with the error to the PowerExchange Agent message log. System Action: User Response: The system rejects the registration request. Contact your security administrator for assistance. You can disable the RACROUTE performed during registration by specifying InitAuthCheck=No in the PowerExchange Agent control statements (AGENTCTL). See the PowerExchange CDC Guide for z/OS for information about the PowerExchange Agent control statements. module: agentid PC routine ABENDed. CSECT=csect, Code=abend_code, Reason=reason, PSW=psw The PC routine identified by csect terminated abnormally with abend code abend_code and reason code reason. The psw variable identifies the program status word (PSW) being used at the time of the abend. The PC function ends. Depending on the error, the function that issued the request may fail. Collect all available information about the error. Contact Informatica Global Customer Support. For more information about the abend code and reason code, see Reason Codes 001 to 255: PowerExchange Agent on page 918 and Abend Code U0001: PowerExchange Agent on page 914.
683
module: ATTACHX failed. Module=module,Return Code=rc The PowerExchange Agent main task attempted to attach a new subtask. The internal ATTACHX macro failed and returned the return code rc. The variable module provides the name of the load module that was specified in the associated ATTACHX macro, and rc provides the return code from the ATTACHX macro. If the error occurred while the PowerExchange Agent was starting, the PowerExchange Agent ends. If the error occurred during processing of a PowerExchange Agent START command, the PowerExchange Agent continues processing. Collect all available information about the error. Contact Informatica Global Customer Support. For more information about the return code, see Return Codes 0 to 12: PowerExchange Agent on page 917 and Reason Codes 001 to 255: PowerExchange Agent on page 918. module: STORAGE OBTAIN failed for Subtask control blocks The PowerExchange Agent could not get storage for the PowerExchange Agent subtask work areas. The PowerExchange Agent ends. Increase the region size, and start the PowerExchange Agent again.
System Action:
User Response:
PWXEDM172069{I|E}module: Subtask {attached|detached}. Module=module, TaskID=taskid, Return Code=rc Explanation: This message shows whether the subtask identified in taskid was attached or detached. The variable module provides the name of the load module that was specified in the associated ATTACHX or DETACH macro, and rc provides the return code from the ATTACHX or DETACH macro. Processing continues. No action is required. For more information about the return code, see the appropriate IBM assembler services documentation. module: Subtask ABENDed. Module=load_module, TaskID=taskid, Code=abend_code The subtask indicated by taskid terminated abnormally with the abend code abend_code. The variable load_module provides the name of the load module that was specified in the associated ATTACHX macro. The subtask ends. Use the PowerExchange Agent START command to start the subtask again. If the problem persists, collect all available information about the error. Contact Informatica Global Customer Support. For more information about the abend code, see Abend Code U0001: PowerExchange Agent on page 914. module: Subtask initialization completed. TaskID=taskid The PowerExchange Agent subtask taskid initialized. Processing continues. No action is required. module: Log file ddname &OPENED. LogClass=class, LogLimit=limit, LogHold={Yes|No} The PowerExchange message log specified in ddname was opened. The variable class displays the SYSOUT class, and the variable limit specifies the record limit. LogHold shows the SYSOUT HOLD option as either Yes or No. Processing continues.
System Action:
684
User Response: PWXEDM172073E Explanation: System Action: User Response:
No action is required. module: DYNALLOC failed. DD Name=ddname, Return Code=rc, Error code=error, Info code=info A dynamic allocation request for the specified DD name failed. The DYNALLOC macro return code, error code, and information code provide information about the failure. The dynamic allocation fails. The function that issued the dynamic allocation request may fail also. For more information about the return code, error code, and information code, see the appropriate IBM assembler services documentation. Attempt to determine the cause of the error, correct the problem, and run the job again. If you cannot determine the cause of the error or if the error persists, contact Informatica Global Customer Support. module: STORAGE OBTAIN failed for storage location 16Mb A request for storage above or below 16 MB, as shown in location, failed. The function that requested the storage may fail. Increase the region size, and run the job again. If increasing the region size does not fix the problem, collect all available information about the error. Contact Informatica Global Customer Support. module: EDM Agent tasktype ABENDed. TaskID=taskid Code=abend_code, Reason=reason, PSW=psw Either the PowerExchange Agent main task or a subtask abended. The variables tasktype and taskid identify the task that abended. This message also provides the abend code, the reason code, and the abend program status word (PSW). If a subtask abended, the PowerExchange Agent continues without the subtask, and the functions provided by that subtask are unavailable. If the PowerExchange Agent main task abends, the PowerExchange Agent ends. Use the PowerExchange Agent START command to restart the failed subtask. If the problem persists, collect all available information about the error. Contact Informatica Global Customer Support. For more information about the abend code and reason code, see Reason Codes 001 to 255: PowerExchange Agent on page 918 and Abend Code U0001: PowerExchange Agent on page 914. module: ddname file CLOSED The file specified by ddname is closed. Processing continues. No action is required. module: Repeat command command for EDM Agent agentid within 15 seconds to confirm request You issued the specified command to the PowerExchange Agent agentid. You must repeat the specified command to confirm the command and queue it for processing. You must repeat the command within 15 seconds. Processing continues. Enter the specified command within 15 seconds to confirm the request, or ignore the message to cancel the command.
System Action:
User Response:
685
PWXEDM172078{I|W}module: command_name command status by PowerExchange Agent agentid Explanation: System Action: User Response: PWXEDM172079E Explanation: System Action: User Response: The PowerExchange Agent agentid accepted or rejected the specified command. Processing continues. No action is required. module: agentid Command Exit. command command takes no operands The specified command has no operands. However, the PowerExchange Agent agentid received the command with one or more operands. The PowerExchange Agent rejects the command. Enter the command without operands. See the PowerExchange Command Reference for the correct command syntax. module: agentid Command Exit. command command RACROUTE AUTH failed. SAF Return Code=safrc,Return Code=rc,Reason=reason The PowerExchange Agent agentid received the specified command. However, you or the job issuing the command did not have the proper authority to issue that command to the specified agent. The variable safrc displays the SAF return code, rc displays the RACF or equivalent return code, and reason displays the RACF or equivalent reason code. The system writes the RACF or equivalent messages associated with the error to the PowerExchange Agent message log. System Action: User Response: The PowerExchange Agent rejects the command. Time stamp system security administrator for assistance. You can disable the RACROUTE performed during command processing by specifying CmdAuthCheck=No in the PowerExchange Agent control statements (AGENTCTL). See the PowerExchange CDC Guide for z/OS for information about the PowerExchange Agent control statements. module: EDMSINIT failed. Return Code=rc,Reason=reason A request to register for PowerExchange Agent services failed. The return code rc and the reason code reason provide additional information about the error. The PowerExchange Agent rejects the registration request. The function that requested registration may fail, also. Use the information supplied in this message to determine the cause of the problem, correct the problem, and run the job again. For more information about the return code and reason code, see Return Codes 0 to 12: PowerExchange Agent on page 917 and Reason Codes 001 to 255: PowerExchange Agent on page 918. If you cannot determine the cause of the problem, contact Informatica Global Customer Support. module: command command could not be processed by PowerExchange Agent agentid The PowerExchange Agent could not process the specified command because the subtask that processes the command is not active. Processing of the command ends. Use the PowerExchange Agent DISPLAY TASKS command to display the active subtasks. Verify that all subtasks are active, and submit the command again. If the problem persists and you cannot determine the cause, contact Informatica Global Customer Support.
686
PWXEDM172083I Explanation: System Action: User Response: PWXEDM172084I Explanation: System Action: User Response: PWXEDM172085E Explanation:
module: The fileid is {open|close} You issued a command to open or close the file specified in fileid. However, the file is already open or closed. The PowerExchange Agent rejects the request. Verify that the command is valid, and issue it again, if needed. module: SUBSYS data set {opened|closed}. DD Name=ddname, DSN=dsname The operation to open or close the SUBSYS data set identified by ddname and dsname completed. Processing continues. No action is required. EDMSPCR1: SUBSYS dataset DYNALLOC failed DSN=dsn, RC=nn, Err=nnnn, Info=nnnn A dynamic allocation request failed for a SUBSYS data set with a data set name dsn. The DYNALLOC return code, error code and info code are shown by RC=, Err=, and Info= respectively. The dynamic allocation fails and the function that issued the request may also fail. If the cause of the error cannot be determined, contact Informatica Global Customer Support. module: agentid function Exit error. See Syslog and/or EDM Agent log for details A SUBSYS data set allocation request failed. Either the PowerExchange Agent subsystem or the allocation exit (as specified in function) issued the request. The system writes the messages describing the error to the SYSLOG message log, the PowerExchange Agent message log, or both. The allocation request fails. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameter, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: agentid Allocation Exit status for {batch|dynamic} allocation The PowerExchange Agent agentid subsystem allocation exit has been entered or exited, as shown in status, for either batch or dynamic allocation. Processing continues. No action is required.
PWXEDM172088W module: The JES SAST could not be found and/or updated. SUBSYS data set I/O may be unavailable Explanation: System Action: User Response: The JES subsystem allocation sequence table (SAST) either could not be found or could not be safely updated. This is an internal error. The PowerExchange Agent continues processing. However, the functions that require SUBSYS I/O fail. Collect all available information about the error. Contact Informatica Global Customer Support. module: command command has an invalid operand operand The specified command contains the specified invalid operand. The processing of the command ends.
687
User Response: PWXEDM172090I Explanation: System Action: User Response: PWXEDM172091E Explanation: System Action: User Response:
Enter the command again with valid operands. module: Agent Trace is {on|off} When you issue a PowerExchange Agent TRACE command, the PowerExchange Agent issues this message to provide the status of the trace. The status of the trace is on or off. Processing continues. No action is required. module: Required SUBSYS keyword 'keyword' was not found A SUBSYS allocation request specified a parameter list that did not contain the required keyword, identified by keyword. The PowerExchange Agent rejects the allocation request. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameter, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: function Exit processing SUBSYS data set. DD Name=ddname The subsystem exit indicated by function has been entered for the DD statement ddname. The variable function can represent one of the following subsystem exits:

Allocation exit Unallocation exit Open exit Close exit System Action: User Response: PWXEDM172093E Explanation: Processing continues. No action is required. module: SUBSYS data set parm 'parameter' error_text During allocation of a subsystem data set, the system found an invalid SUBSYS parameter. The variable parameter displays the incorrect parameter, and the variable error_text displays the type of error that occurred. The PowerExchange Agent rejects the allocation request. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameters, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: agentid SUBSYS data set allocation failed. See Syslog and/or Agent log for details The PowerExchange Agent agentid subsystem allocation exit cannot process an allocation request for a SUBSYS data set. The system writes the additional messages that describe the error to the SYSLOG message log, the PowerExchange Agent message log, or both. The PowerExchange Agent does not process the allocation request. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameters, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: Data set name required for allocation of SUBSYS data set. DD name=ddname The system cannot process an allocation request for a subsystem data set because either you or the system did not specify a data set name. The variable ddname displays the DD name.
688
The PowerExchange Agent does not process the allocation request. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameters, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: EDMSSSIO function failed. DD name=ddname, RC=return_code, Reason=reason An EDMSSSIO macro, which manages SUBSYS I/O work areas, failed. The variable function identifies the failing operation. The function that issued the EDMSSSIO macro may fail. For more information about the return code and reason code, see Return Codes 0 to 12: PowerExchange Agent on page 917 and Reason Codes 001 to 255: PowerExchange Agent on page 918. Use the information in this message to determine the cause of the error, correct the problem, and run the job again. If the error persists or you cannot determine the cause of the error, contact Informatica Global Customer Support. module: {successful|unsuccessful|duplicate} EDMSINIT performed for TCB tcb_address. Return Code=rc, Reason=reason The EDMSINIT macro completed a successful, unsuccessful, or duplicate PowerExchange Agent registration call with the return code rc and reason code reason. If the call failed, the function that issued the macro may fail, also. If the call was successful, processing continues. If the call was successful, no action is required. If the call failed, use the information in this message to determine the cause of the failure, correct the cause, and run the job again. If you cannot determine the cause of the failure or if the failure persists, collect all available information about the error. Contact Informatica Global Customer Support. For more information about the return code and reason code, see Return Codes 0 to 12: PowerExchange Agent on page 917 and Reason Codes 001 to 255: PowerExchange Agent on page 918. module: Agent control_block {obtained|released}. Addr=address The system either obtained or released the specified control block at the specified address. Processing continues. No action is required. module: Passing control to SUBSYS data set function module module The PowerExchange Agent is about to call the specified load module for the specified function. A JCL DD statement or a DYNALLOC SUBSYS parameter specified the load module. Processing continues. No action is required.
PWXEDM172100{I|E}module: Control returned from module module. Return Code=rc, Reason=reason Explanation: The specified load module, which you specified in either a JCL DD statement or a DYNALLOC SUBSYS parameter, returned control with the return code rc and reason code reason. If the return code or reason code indicates an error, the function that called the specified module may terminate.
System Action:
689
User Response:
If the return code and reason code do not indicate an error, no action is required. If the codes indicate an error, use the return and reason codes to determine the cause of the error, correct the cause, and run the job again. For more information about the return code and reason code, see Return Codes 0 to 12: PowerExchange Agent on page 917 and Reason Codes 001 to 255: PowerExchange Agent on page 918. If the error is an assembler language error, see the appropriate IBM assembler services documentation for information on the return and reason codes. module: agentid function_name Exit could not find EDSSIOW area for DD name ddname The subsystem exit function function_name, which is for the PowerExchange Agent identified in agentid, was unable to find the EDSSIOW control block associated with the specified ddname. This is an internal program error. Subsystem exit processing ends. The function that requested the service may fail also. Collect all available information about the error. Contact Informatica Global Customer Support. module: agentid function_name Exit could not find module module_name specified in JCL/DYNALLOC SUBSYS parameters The subsystem exit function function_name could not find a module specified in the DYNALLOC or JCL DD SUBSYS parameters. The PowerExchange Agent does not process the allocation request. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameters, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: Duplicate SUBSYS function request. DD Name=ddname, DSN=dsname The system issued a duplicate allocation or open request for the SUBSYS data set identified by ddname and dsname. The request fails. The function that issued the request may fail also. Collect all available information about the error. Contact Informatica Global Customer Support. module: Module module ABENDed. Code=abend_code, Reason=reason, PSW=psw The specified load module, which you specified in either a JCL DD statement or DYNALLOC SUBSYS parameter, terminated abnormally with the abend code abend_code, reason code reason and program status word (PSW) psw. The function that called the module may terminate. Use the abend code, reason code and PSW to determine the cause of the error, correct the cause, and run the job again. For more information about the abend code and reason code, see either the appropriate IBM assembler services documentation or Return and Reason Codes on page 913. If you cannot determine the cause of the failure or if the failure persists, collect all available information about the error. Contact Informatica Global Customer Support. module: STIMERM failed. Return Code=rc A STIMERM macro failed and returned the return code rc. The function that issued the STIMERM macro may fail. Use the return code to determine the cause of the error, correct the cause, and run the job again. For more information about the return code, see the appropriate IBM assembler services documentation. If you cannot determine the cause of the failure or if the failure
690
persists, collect all available information about the error. Contact Informatica Global Customer Support. PWXEDM172106E Explanation: module: macro function failed. Return Code=rc, Reason=reason Either a $DLIGPPL or a $DLICQPL macro failed and rendered a return code and a reason code. The first two hexadecimal values (xx) of the circular queue reason code (xxyyzzzz) display the return code. The second two hexadecimal values (yy) display the function code. The last four hexadecimal values (zzzz) display the reason code. The specified function that made the request may fail. Use the return, function, and reason codes to determine the cause of the error, correct the cause, and run the job again. For more information about the reason code, see DTL58001 to DTL62591 on page 657. module: EDM Agent Global Queue function_name. DSN=dsname, tokentype=token The global queue function function_name completed for the SUBSYS data set dsname. The variables tokentype and token are internal values that uniquely identify global queue structures. Processing continues. No action is required. module: No DD suffix for allocation. DSN=dsname All available DD name suffixes used for generating SUBSYS DD names are in use. The system cannot perform the DYNALLOC for the SUBSYS data set identified by dsname. The allocation request fails. The function that issued the request may fail, also. If a JCL DD statement initiated the allocation request, correct the SUBSYS parameters, and submit the job again. Otherwise, collect all available information about the error. Contact Informatica Global Customer Support. module: {open|close} failed for SUBSYS data set. DD Name=ddname, Return Code=rc, ACBERFLG=acb_error An open or close of the SUBSYS data set failed. The open or close function returned the DD name ddname, return code rc, and the ACB error code acb_error. The function that issued the request may fail. Use the information in this message to determine the cause of the error, correct the problem, and run the job again. If the error persists or you cannot determine the cause of the error, contact Informatica Global Customer Support. module: SUBSYS data set {opened|closed}. DD Name=ddname, LRecl=record_length, BlkSize=block_size The SUBSYS data set associated with the specified DD name was opened or closed. This message provides the logical record length and block size. Processing continues. No action is required.
691
module: The Global Service module table is full. Service module load_module could not be LOADed The identified load module, which you specified in a ServiceModule control file statement, could not be loaded because no free entries exist in the PowerExchange Agent service module table. The PowerExchange Agent ends. Remove the ServiceModule statement from the PowerExchange Agent control file, and start the PowerExchange Agent again. If the ServiceModule statement is required, contact Informatica Global Customer Support. module: Subtask status. Module=load_module, TaskID=taskid You entered a PowerExchange Agent START command, and the system is displaying the result of the command in status, the subtask ID in taskid, and the module specified in the ATTACHX macro in load_module. Processing continues. No action is required. module: The taskid Subtask is status You issued a PowerExchange Agent START or STOP command for the specified subtask, but that subtask is already started, stopped, active, or inactive, as indicated in status. The PowerExchange Agent rejects the START or STOP command. Enter the correct command, if it is required. module: Address space created. ASCB=ascb, STOKEN=stoken The system created an address space with the specified ASCB address and STOKEN. Processing continues. No action is required. module: ASCRE failed. Return Code=rc, Reason=reason A request to create an address space using the ASCRE macro failed, and the macro returned the return code rc and reason code reason. The function that issued the request may fail. Use the information in this message to determine the cause of the failure, correct the cause, and run the job again. If the error persists or you cannot determine the cause of the error, contact Informatica Global Customer Support. module: EDMRIOM function call failed. Error message follows: The PowerExchange repository request function that was issued to the ERMRIOM module failed. An additional error message that further describes the error follows this message. The function that issued the request may fail. Use the information in this message and the following message to determine the cause of the failure, correct the cause, and run the job again. If the error persists or you cannot determine the cause of the error, contact Informatica Global Customer Support. module: Invalid DSN for Global Queue request. DSN=dsname A global queue request failed because the data set name dsname is invalid. The function that issued the request may fail.
System Action: User Response: PWXEDM172113E Explanation: System Action: User Response: PWXEDM172114I Explanation: System Action: User Response: PWXEDM172115E Explanation: System Action: User Response:
692
User Response:
Collect all available information about the error. Contact Informatica Global Customer Support. module: $PDX function request failed. See Agent log for error message A $PDX macro that was issued for the specified function failed. The PowerExchange Agent writes this message to the SYSLOG message log to indicate that you can find additional error messages in the PowerExchange Agent message log. The function that issued the macro may fail. Use the information in this message and in the associated messages in the PowerExchange Agent message log to determine the cause of the failure, correct the cause, and run the job again. If the error persists or you cannot determine the cause of the error, contact Informatica Global Customer Support. module: Repository file OPENed. Repository DSN=dsname The PowerExchange Agent has opened the PowerExchange repository data set dsname. Processing continues. No action is required. module: EP Name=ep_name, EPA=ep_address, Major Name=major_name, Load Point=load_point, Length=length This message provides additional information about an abend condition. It displays the name and address of the program that is abending. The abend processing continues. Use this message and any related message to help determine the cause of the abend. For assistance, contact Informatica Global Customer Support. prog: SUBSYS data set dynamic deallocation failed. DD Name=ddname, RC=rc, Error code=error, Info code=info A dynamic deallocation request for a SUBSYS data set failed. This message displays the DD name and the DYNALLOC return code, error code, and info code. The dynamic allocation fails and the function that issued the request may also fail. Use this message and any related message to help determine the cause of the abend. Contact Informatica Global Customer Support if you need assistance. ALESERV ADD for status Performance Dataspace failed. RC = return_code An ALESERV ADD issued by the PowerExchange Agent encountered an error. The return code is shown by return_code. The initialization process for the PowerExchange Agent ends. Contact Informatica Global Customer Support. Performance Dataspace validation failed, Reason = reason_code The PowerExchange Agent subtask that manages the performance data space found incorrect data in the anchor control block within the dataspace. The reason code indicates what was incorrect. The management subtask for the performance data space ends. This condition might exhaust the space in the dataspace. Contact Informatica Global Customer Support. Note that the performance data space can be deleted and recreated by shutting down the AGENT STARTED task using the
PWXEDM172119I Explanation: System Action: User Response: PWXEDM172120I Explanation: System Action: User Response:
693
COMPLETLY operand of the SHUTDOWN command, and then restarting the PowerExchange Agent. PWXEDM172125E Explanation: System Action: User Response: DSPSERV EXTEND failed for Performance Dataspace. RC = return_code. Reason = reason_code An attempt to enlarge the performance data space using the DSPSERV macro with the EXTEND operand failed, with the return and reason code indicated. The management subtask for the performance data space ends. this could result in space in the dataspace becoming exhausted. Contact Informatica Global Customer Support. Note that you can perform the following tasks: 1. Delete the performance data space. 2. Recreate it by shutting down the PowerExchange Agent started task by using the COMPLETELY operand of the SHUTDOWN command. 3. Restart the PowerExchange Agent. PWXEDM172126I Explanation: System Action: User Response: DSPSERV Performance Dataspace successfully extended by blks 4K blocks The performance data space was becoming full and was extended by the indicated number of blocks. Each block is 4K bytes in size. Processing continues. No action is required.
PWXEDM172127W DSPSERV Performance Dataspace is not at maximum size: blks blocks Explanation: System Action: User Response: After the extension indicated in the previous message, the performance data space is now at its maximum size. Processing continues, but no additional increases can be performed. As a result, it is possible that space in the performance data space could become exhausted. No action is required. If the performance data space becomes exhausted, it may be necessary to change the size parameters. Use PKDataspaceInit and PKDataspaceMax in the PowerExchange Agent Control Statement AGENTCTL file to change the size parameters. Recreate the performance data space by shutting down the PowerExchange Agent started task using the COMPLETELY operand of the SHUTDOWN command, and then restarting the PowerExchange Agent. Error in Free Space element in Performance Dataspace, A = Address, RSN = reason_code An internal error was found in the free space elements maintained in the performance data space. The erroneous free space element is removed from processing and is not eligible for reuse. Contact Informatica Global Customer Support. num Free Space elements, containing numK and num bytes, successfully reclaimed The free space reclamation process has completed a cycle of processing. The indicated number of blocks of free space containing the indicated total of bytes have been made available for reuse in the performance data space. Processing continues. No action is required.
694
Error in Free Space queue in Performance Dataspace, RSN = reason_code An internal error was found in the free space queue maintained in the performance data space. The management subtask for the performance data space ends. This could result in space in the dataspace becoming exhausted. Contact Informatica Global Customer Support. Note that the performance data space can be deleted and recreated by shutting down the PowerExchange Agent started task using the COMPLETELY operand of the SHUTDOWN command, and then restarting the PowerExchange Agent. DELETE failed. Module = mod, Return code = rc A DELETE macro was issued for the module shown by mod. However, MVS Contents Supervision was unable to remove the load module from the environment. The return code from the DELETE macro is indicated by rc. The PowerExchange Agent subtask or task ends. Contact Informatica Global Customer Support. Dataspace Request failed, reqname, Return code=rc, Reason = reason_code An attempt by the PowerExchange Agent to invoke the virtual storage manager for the performance data space was unsuccessful. The type of request that failed is indicated by the reqname. The management subtask for the performance data space ends. This could result in space in the dataspace becoming exhausted. Contact Informatica Global Customer Support. num Used Space elements, containing numK and num bytes, successfully purged The space purge process has completed a cycle of processing. The indicated number of blocks of used space, containing the indicated number of total bytes, have been removed from the performance data space. The space purge process identifies monitoring data that is obsolete and removed it from the dataspace. Processing continues. No action is required. Attempt to unlatch POA block at address addr during recovery {was|was not} successful An attempt to remove a latch on a POA control block during recovery from an abend that occurred in the management subtask for the performance data space was or was not successful, as indicated. The POA control block was located at the address indicated by addr within the performance data space. The management subtask for the performance data space ends due to the previous abend. Contact Informatica Global Customer Support. If the latch was not removed, it may become necessary to delete and recreate the performance data space by shutting down the PowerExchange Agent started task using the COMPLETELY operand of the SHUTDOWN command, and then restarting the PowerExchange Agent.
695
Creation of SCOPE=COMMON dataspace failed, check PARMLIB MAXCAD limit An attempt to create a SCOPE=COMMON dataspace for the PowerExchange Agent using the DSPSERV CREATE operand failed. The return code and reason code are given in the DATA = value portion of the previous message. The specific return code and reason code indicate that the maximum number of SCOPE=COMMON dataspaces may have been reached. The PowerExchange Agent ends. To increase the limit, it will be necessary to change the MAXCAD value in the IEASYSxx member of SYS1.PARMLIB, and re-IPL. Contact Informatica Global Customer Support. module: EDMSDIR contains Agent Id agent_ID, which does not match Agent name agent_name The PowerExchange Agent loaded the EDMSDIR load module, but the specified agent ID is not the same as the name of the PowerExchange Agent. The PowerExchange Agent processing ends. Verify that the PowerExchange Agent is using the correct EDMSDIR load module. module: Existing control_block, used by Agent agent_ID. Addr=address. status The PowerExchange Agent found a valid MVS subsystem control block, located at the specified address. The PowerExchange Agent processing continues. The possible values for status are:
PWXEDM172138E Explanation: System Action: User Response: PWXEDM172139I Explanation: System Action:
RECLAIM Use, as is. REFRESH Rebuild. User Response: PWXEDM172140I Explanation: No action is required. module: {Duplicate Log Reader|Log Reader} log_reader_name disconnected from Log Merge task logger_id, return code=rc, reason code=reason A task or job has disconnected from the Log Merge task. The name and type of the task or job are indicated in the message, along with any return code or reason code associated with the disconnection. If the return code and reason code are zero, this is normal. If the return code and reason code are non-zero, the disconnect may have occurred due to some other problem. Processing continues If the return code and reason code are non-zero, look for other messages that might indicate a problem, and check the meaning of the return code and reason code for an explanation of the problem. Also look at the output created by the associated job or task for any possible error. module: EDM Logger logger_jobname has started on system smf_ID A member Logger, logger_jobname, that is part of the Post-Log Merge process has been started on system smf_id. As part of its initialization, it will signon to the Post-Log Merge task to verify proper serialization and sequencing of log records being merged from all the member Loggers. The message text includes the job name of the member Logger, the SMF id of the system on which the member Logger is executing, and the name of the log reader whose status has been changed to recognize that the member Logger is now active. The message will be issued once for each active log reader that will receive data merged from that member Logger. Processing continues.
696
User Response:
This is an informational message. No action is required.
PWXEDM172142W module: Logger logger_jobname on system smf_id has terminated for Log Reader log_reader_name - LMF will continue Explanation: A member Logger, logger_jobname, that is part of the Post-Log Merge process ends. The Post-Log Merge task will continue to merge data from that member Logger until the end of its data is reached. After that time, new data from that member is not merged by the Post-Log Merge task until the member Logger signs back on to the Post-Log Merge task. The signon of a member Logger is indicated by message PWXEDM172141I. The message text includes the job name of the member Logger (logger_jobname), the SMF id (smf_id) of the system on which the member Logger was executing, and the name of the log reader (log_reader_name) whose status has been changed to recognize that the member Logger is no longer active. The message will be issued once for each active log reader that was receiving data merged from that member Logger. System Action: User Response: Processing continues. Investigate the termination of the member Logger. If the termination was expected, such as during a shutdown so that the system could be IPLed, no user action is required. If the termination was unexpected, determine the reason and attempt to restart it. If the problem cannot be determined, or if the member Logger cannot be restarted, contact Informatica Global Customer Support. module: LMF merging data from an invalid environment LMF has found multiple loggers being merged which are not on the same sysplex, are on the same sysplex but do not have an external timer, or the PowerExchange Loggers are not on the same CPU. Processing stops. Remove the ERDSs that are not to be merged or run the PowerExchange Logger on the correct system. module: Invalid JCL PARM value value for {Log Merge|Log Scan/Print Utility} task The job or task was started with JCL that specified PARM=, but the value in the PARM parameter was not valid. The message contains up to eight characters of the invalid value that was supplied in the JCL. The only valid value is Traced, where the value of x is one of E, S, or L. The default value is E, meaning that no tracing is to occur. The Log Merge or Log Scan/Print task ends. Correct the JCL that was used to start the job or task, and restart it. If the problem persists, contact Informatica Global Customer Support for assistance. module: LMF is using LOGRGRP but the UOW sequence number used is not a timestamp LMF has found that the LOGRGRP is used in the EDMSDIR, but the PowerExchange Logger does not have a time stamp in the sequence field. Processing stops. Verify that the PowerExchange Loggers that are being merged have a value of ''Y for all specified in the LOGRGRP parameter in the EDMSDIR. module: LMF is now processing dataset dataset_name for {Log Scan/Print Utility|Log Reader log_reader_name} LMF is identifying the LOG DATASET to be processed next. Processing continues. The process for which the data set is being accessed is identified as either:
697
Log Scan/Print Utility Log Reader - followed by log reader name No action is required. module: LMF has encountered an error with function function return code=rc The program has encountered an error during a log process function from DSPSERV, IV, HSPSERV, DYNAMIC ALLOCATION, DYNAMIC REALLOCATION, or OPEN. The following functions could be related to the error encountered:

User Response: PWXEDM172147E Explanation:
UNMAP UNACCESS UNIDENTIFY RELEASE DELETE DEALLOCATE GENCB OPEN SHOWCB CLOSE CREATE IDENTIFY ACCESS MAP RESET SREAD OPEN MODCB GETRPL POINT System Action: User Response: PWXEDM172148E Explanation: System Action: User Response: PWXEDM172149E Explanation: System Action: User Response: PWXEDM172150E Explanation: System Action: User Response: Processing ends. Investigate failure and contact Informatica Global Customer Support. module: Error was encounter opening the archive log dataset return code=rc The program has encountered an error during the open of the archive log. Processing ends. Investigate why open failed and contact Informatica Global Customer Support. module: End of file has been reached on the allocated log. This should not occur The program has reached EOF on an archive data set, this should not occur. Processing ends. Contact Informatica Global Customer Support. module: Dynamic allocation error has occurred return code=rc An error was detected during dynamic allocation of an active or archive data set. Processing ends. Check to see if the data set was allocated to another job or if the data set still exists.
698
PWXEDM172151I Explanation: System Action: User Response: PWXEDM172152E Explanation:
module: Log merge will use {XCF|the MVS LOGGER} for data transmission. This message describes the mode of transmission for the log merge. Processing continues. No action is required. module: Global function failed Return code=rc The issuing program called a service or function that returned a non-zero return code. Some of the functions that can have this error are in the following list:
READQ PUTQ CONNECTQ DISCONNECTQ XCF group get XCF sign on to the PowerExchange Logger XCF free XCF join XCF leave XCF get CREATEQ OPENQ CLOSEQ MVS Logger connect MVS Logger write MVS Logger browse start MVS Logger browse MVS Logger delete XCF put DELETEQ System Action: User Response: PWXEDM172153E Explanation: System Action: User Response: PWXEDM172154E Explanation: System Action: User Response: PWXEDM172155E Explanation: System Action: User Response: Processing ends. Check for previous error messages. Contact Informatica Global Customer Support module: The EDM Logger is not available. An error was detected in EDMLSND1. The PowerExchange Logger is not up and executing. Processing ends. Contact Informatica Global Customer Support. Error initializing common services. An error was detected in EDMLSND1. Processing ends. Contact Informatica Global Customer Support. Agent is not active An error was detected in EDMLSND1. Processing ends, Contact Informatica Global Customer Support.
699
PWXEDM172156E Explanation: System Action: User Response: PWXEDM172157E Explanation: System Action: User Response:
Error in common services connect. An error was detected in EDMLSND1. Processing ends. Contact Informatica Global Customer Support. EDMLSND3 could not be loaded. An error was detected in EDMLSND1. The module could not be loaded. Processing ends. Find out why the module did not load. Verify that the module is not missing and there is not a storage problem. module: Sender is ready for processing This is an informational message notifying you that the sender is ready for processing. Processing continues. No action is required. module: Inconsistent response from LRP-XCF The LMF control module was expecting a read response. The job will terminate. Restart job or contact Informatica Global Customer Support. module: Get main failed at initialization. Return code=rc An error was detected indicating that virtual storage is not available. Processing ends. Increase the size on the region card. module: Receiver is ready for processing. This is an informational message notifying you that the receiver is up and ready for processing. Processing continues. No action is required. module: Critical error -- receiver table is full. The receiver table is full and cannot accept more data. Processing ends. Contact Informatica Global Customer Support. module: Sender has been restarted, a possible loss of data has occurred. Informational message records were left in the receiver at the restart of the sender. The restart cannot be validated. Processing continues. Verify records that are in question.
PWXEDM172158I Explanation: System Action: User Response: PWXEDM172159E Explanation: System Action: User Response: PWXEDM172160E Explanation: System Action: User Response: PWXEDM172161I Explanation: System Action: User Response: PWXEDM172162E Explanation: System Action: User Response: PWXEDM172163I Explanation: System Action: User Response:
700
PWXEDM172164E Explanation: System Action: User Response: PWXEDM172165E Explanation: System Action: User Response: PWXEDM172166E Explanation: System Action: User Response: PWXEDM172167E Explanation: System Action: User Response: PWXEDM172168E Explanation:
module: The receiver has encountered a buffer full condition. Buffer space has been exhausted and records cannot be processed. The system will retry for buffers later. No action is required. The receiver is not available. The receiver was not available at the time the sender was started. Processing ends. Start the receiver on the appropriate system. module: PAC/LRP must be on the same MVS image as LMF The PAC job must run on the same MVS image that LMF is running on. Processing ends. Start the PAC job on the same system as LMF. module: PAC/LRP with the same name is already active with LMF A previous PAC with the same name had already been attached with LMF. Processing ends. Investigate why PAC is already attached with LMF. module: Reader rrrrrrrr terminating abnormally: reason A Log Reader task has encountered an unexpected logic error, and must terminate. The specific reason for the error is indicated in the message text. If the module shown in the message is EDMLPOPU then this is related to Post-Log merge processing. The reason can be one of:

Unknown ECB Posted Logical Reader Error
The Log Reader subtask will terminate, and the corresponding Log Reader job will also terminate. Investigate the cause of the error indicated, and if possible, restart the Log Reader job. If the Log Reader job will not restart, contact Informatica Global Customer Support. module: QUIT has been issued the sender is terminating This informational message indicates that the pre-log merge sender task is ending due to a user request. The pre-log merge sender task ends. No action is required. module: Receiver -- operator reply The receiver was not available at the time the sender was started. Processing ends. Start the receiver on the appropriate system.
701
PWXEDM172171I Explanation: System Action: User Response: PWXEDM172172I Explanation: System Action: User Response: PWXEDM172173I Explanation: System Action: User Response: PWXEDM172174E Explanation: System Action: User Response:
module: QUIT has been issued the receiver is terminating This informational message indicates that the pre-log merge receiver task is ending due to a user request. The pre-log merge receiver task ends. No action is required. module: Sender has signed on to the EDM Logger The sender has communicated through XCF to the PowerExchange Logger. Processing ends. Start the receiver on the appropriate system. module: Sender has signed on to the EDM receiver The sender talked to the receiver. Processing ends. Start the receiver on the appropriates system. module: Sender is terminating due to a critical write error The sender is ending. A critical error has occurred which will result in data loss. Processing ends. Find out why the error occurred by reviewing the previous message.
PWXEDM172175W module: An External Timer Routine is necessary to run LMF Explanation: LMF has issued a warning about the external timer. If the PowerExchange Loggers are run from the same system, an external timer is not necessary. However, there are no integrity checks to verify this. Processing continues after warning. An external timer must be running to insure time integrity. module: Receiver has signed on to the EDM Logger The receiver has started communication with the PowerExchange Logger. Processing continues. No action is required. module: Sender asynchronous process terminating The receiver has started communication with the PowerExchange Logger. Processing continues. No action is required. module: Last record transmitted was record record_number This message displays the count of transmitted records from the sender. The message is displayed at termination. Processing continues. No action is required.
System Action: User Response: PWXEDM172176I Explanation: System Action: User Response: PWXEDM172177I Explanation: System Action: User Response: PWXEDM172178I Explanation: System Action: User Response:
702
PWXEDM172179E Explanation: System Action: User Response: PWXEDM172180I Explanation: System Action: User Response: PWXEDM172181I Explanation: System Action: User Response: PWXEDM172182I Explanation: System Action: User Response: PWXEDM172183E Explanation:
module: Attach failed for module module_name return code=rc The issuing program called a service or function which returned a non-zero return code. Processing ends. Check for previous error messages and then contact Informatica Global Customer Support. module: System system_ID on record record_number at store clock time This informational message displays the last record received by the receiver. The message is displayed at termination. Processing continues. No action is required. module: Next record to be processed from system system_ID is record_number. There are no records queued. This informational message displays records queued by system in the receiver. The message is displayed at termination. Processing continues. No action is required. module: No records have been processed since start-up. This informational message states that no records have been processed since start-up. Processing continues. No action is required. module: Log Reader log_reader_name has sent a type request but no signon entry is present in LMF LMF cannot find the entry in the PAC table that corresponds to the job or task that sent the request. The type of request and the job or task that sent the request are included in the message. The variable type is one of the following values:

Request Data Transfer Shutdown Data Transfer Terminate Process System Action: User Response: The request is ignored. This may lead to the job or task that sent the request being in a permanent wait. Identify the job or task that sent the request, and determine its status. If necessary, cancel that job or task, and attempt to rerun it. If the problem persists, contact Informatica Global Customer Support. module: The receiver is not communicating sender waiting The sender was in the act of transmitting and received an inactive condition from the receiver. The job waits for the restart of the receiver to attempt recovery. No action is required. module: The sender attempted restart but could not retransmit data requested by receiver This error message notifies that the sender was in the act of retransmitting data after the receiver started and the required record was found to have been flushed from the buffers. The sender will terminate because data integrity is lost.
PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 703
PWXEDM172184I Explanation: System Action: User Response: PWXEDM172185E Explanation: System Action:
User Response: PWXEDM172186I Explanation: System Action: User Response: PWXEDM172187E Explanation: System Action: User Response: PWXEDM175188I Explanation: System Action: User Response: PWXEDM172189I Explanation: System Action: User Response: PWXEDM172190I Explanation: System Action: User Response: PWXEDM172191I Explanation:
Restart the sender and any job that is running. The receiver has started communication with the sender again The sender has been waiting for a reset from the receiver. The reset has now been received and transmission will start again. The sender starts transmission again. No action is required. module: The EDM Logger has terminated. The receiver is waiting to restart. The receiver uses queues established by the PowerExchange Logger. If the PowerExchange Logger ends, it must be restarted so that the receiver may run. The receiver ends. Restart the PowerExchange Logger. module: System Checkpoint record record_number This informational message shows the last checkpoint record. Processing continues. No action is required. module: System Reset on record record_number after the receiver restart This informational message shows the last reset record. Processing continues. No action is required. module: System trace has been turned to option trace_option This informational message displays the trace option entered on the modify command. Processing continues. No action is required. module: LMF will {begin|stop} transferring data for {Log Scan/Print Utility|Log Reader log_reader_name} at log_location Displays the starting data transfer location that will be used for the Log Reader job or the specified task in the message, or for the Log Scan/Print Utility run. The words Log Reader followed by log_reader_name appear if this message is issued in Post-Log Merge. The words Log Scan/Print Utility (and no name) appear if the message is issued from the Log Scan/Print utility.
The job continues processing. Informational message only. module: LMF Tasks have stopped successfully due to operator shutdown This informational message notifies that the LMF system is ending due to operator request. The job ends. No action is required.
704
EDMLCTRD: Reader xxxxxxxx has terminated [abnormally] The specified log reader ended abnormally. Check the output from job to find the reasons for termination. The LMF continues the function that it was processing. Restart the job, if necessary. module: LMF task for {Log Reader log_reader_name|Log Scan/Print Utility} has terminated prematurely due to an abend The LMF task corresponding to the specified job ended abnormally. The words Log Reader followed by log_reader_name appear if this message is issued in Post-Log Merge. The words Log Scan/Print Utility (and no name) appear if the message is issued from the Log Scan/Print utility. The LMF task will terminate Look at the output from the LMF Job, and from the corresponding Log Reader job, to determine the reason. module: LMF task for {Log Reader log_reader_name|Log Scan/Print Utility} is terminating due to an operator stop or PAC termination The log read tasks under LMF have terminated. The words Log Reader followed by log_reader_name appear if this message is issued in Post-Log Merge. The words Log Scan/Print Utility (and no name) appear if the message is issued from the Log Scan/Print utility Continue termination. No action is required. EDMLCTRD: Reader xxxxxxxx has requested stop transmission A log reader requests that post-log merge stop transmission of data. The log reader subtask ends but other active log readers, if any, continue to function. No action is required. Unable to LOAD module module_name The specified module could not be found in the JOBLIB or STEPLIB concatenation. Processing ends. Verify that all required LOAD libraries are in the JOBLIB or STEPLIB concatenation. module: LMF table populate tasks are terminating due to an operator stop or PAC termination The log read tasks under LMF have terminated. Processing continues. No action is required. module: LMF time has encountered an error return code=rc The LMF timer macro has encountered an error. Region will terminate. Investigate possible reasons for termination and contact Informatica Global Customer Support.
System Action: User Response: PWXEDM172196I Explanation: System Action: User Response: PWXEDM172197E Explanation: System Action: User Response: PWXEDM172198I Explanation: System Action: User Response: PWXEDM172199E Explanation: System Action: User Response:
705
module: display_type display for EDM Agent agentid You entered a PowerExchange Agent DISPLAY command, and this message indicates both the type of display list that follows this message and the PowerExchange Agent for which the display list is generated. Processing continues. No action is required. module: No locks are currently held You issued a DISPLAY LOCKS command, but no PowerExchange Agent locks are currently held. Processing continues. No action is required. module: object ASCB=ascb_address, TCB=tcb_address You entered a PowerExchange Agent DISPLAY LOCKS or DISPLAY TASKS command. If you used DISPLAY LOCKS, object identifies the name of the PowerExchange lock and ascb_address and tcb_address identify the ASCB and TCB addresses of the owner of the lock. If you used DISPLAY TASKS, object identifies the TAFF entry, and ascb_address and tcb_address identify the ASCB and TCB addresses of the registered tasks. Processing continues. No action is required. module: Job=job, Step=step, ProcStep=proc_step, JobID=jesid You entered a DISPLAY TASKS command, and this message provides the job name, step name, PROC step name and JES job ID of a registered task. Processing continues. No action is required. module: Handle addr=handle_address, Task-related area addr=task_address You entered the PowerExchange Agent DISPLAY TASKS command, and this message provides the addresses of both the PowerExchange Agent handle and the task-related work area of a registered task. Processing continues. No action is required. module: dsname - CQMN=token, Seq=seq_number You entered a DISPLAY GBLQDSNS command, and this message is the response to the command. The message displays the data set name, the circular queue main token, and a unique sequence number for the PowerExchange Agent global circular queue. Processing continues. No action is required. module: End of list The PowerExchange Agent issues this message at the end of all DISPLAY command output lists. Processing continues. No action is required.
System Action: User Response: PWXEDM172201I Explanation: System Action: User Response: PWXEDM172202I Explanation:
706
module: module_name EPA=epa, Version=version, Date=date, Time=time You entered the PowerExchange Agent DISPLAY MODULES command, and this message provides the entry-point address (EPA), version, and build date and time for the module specified in module_name. If version, date, or time contain queries, the PowerExchange Agent component does not own the module but is using it. Processing continues. No action is required. PMP addr=address, Subpool=subpool, Module len=modlength, PMP len=pmplength, CDE=cde_address You entered a DISPLAY MODULES command. For each copy of a module identified in a preceding message, the PowerExchange Agent displays the address of the module prefix, the storage subpool into which the module was loaded, the length of the module, and the combined length of the module and its prefix. If an associated LPA CDE exists, the message also displays the CDE address. Processing continues. No action is required. module: Repository request failed. Return Code=rc,Reason=reason A request for PowerExchange repository data failed and returned the return code rc and reason code reason. The PowerExchange repository rejects the request. The calling function may fail, also. Use the return code and reason code to determine the cause of the error, correct the cause, and run the job again. For more information about the return code and reason code, see Return Codes 0 to 12: PowerExchange Agent on page 917 and Reason Codes 001 to 255: PowerExchange Agent on page 918. If you cannot determine the cause of the failure or if the failure persists, collect all available information about the error. Contact Informatica Global Customer Support. module: JCL EXEC PGM=jclprogram, RB CDE Program=rbprogram, Initiator ID=initid This message is issued in response to a DISPLAY command. It provides the program name from the JCL EXEC (jclprogram) and the program name from the current PRB associated with the address space identified in a preceding message (rbprogram). For a batch job, this message also displays the associated JES initiator ID (initid). Processing continues. No action is required. module: module_wait1 (ascb1/tcb1) status module_hold2 (ascb2/tcb2) for lock=lockid(ecb_address/ecb) This message displays a status for the module identified in module_wait1 when it is trying to get a lock from the module identified in module_hold2. The status can be one of the following conditions: The module identified by module_wait1 is waiting for the lock. The module identified by module_wait1 is posting to module_hold2. Processing continues. No action is required.
System Action: User Response: PWXEDM172209E Explanation: System Action: User Response:
Explanation: Explanation: System Action: User Response:
707
PWXEDM172212I Explanation: System Action: User Response: PWXEDM172213I Explanation: System Action: User Response: PWXEDM172214I Explanation:
module: module_wait (ascb/tcb) now owns lockid lock The specified module gained ownership of the lock designated by lockid. Processing continues. No action is required. module: SRB POSTING module_wait(ascb/tcb) for lockid(ecb_address/ecb) The module holding the lock designated by lockid will post to the module that is waiting for the lock. Processing continues. No action is required. module: agent_ID function Exit status. ASCB=ascb_address, ASID=asid, TCB=tcb_address An end-of-task, early-end-of-task, or end-of-memory exit routine, as shown by function, for the PowerExchange Agent indicated by agent_ID, either received control or completed processing as shown by status. The ending task or address space is indicated by ascb_address, asid, and tcb_address. For an end-of-memory exit routine, the TCB will be zero. Processing continues. No action is required. module: Resource Mngr status. Type=type(ecb_address), Owner=(owner_ascb/owner_tcb), Target=(target_ascb/target_tcb) A resource manager element was either added or deleted, as shown by status. The type is ECB or ROUTINE, and the ecb_address indicates the ECB address in the owning ASID, or the address of the routine in common storage. The owner_ascb and owner_tcb addresses indicate the ASCB and TCB of the module that owns the element. The target_tcb and target_ascb indicate the ASCB and TCB of the module that is being monitored. Processing continues. No action is required. module: VSAM service SVC status. Job=job_ID, Step=step_ID This message provides status information about the VSAM service, including job and step identifiers. Processing continues. No action is required. module: EDM VSAM Change Capture {deactivated|reactivated} This message shows the status of the VSAM change capture process for the PowerExchange Agent, when starting or stopping. Processing continues. No action is required. module: agent_ID Clean up - operation. item=value The PowerExchange Agent specified in the message is performing clean-up tasks for the operation. The value field displays additional information about the operation. Processing continues.
System Action: User Response: PWXEDM172216I Explanation: System Action: User Response: PWXEDM172217I Explanation: System Action: User Response: PWXEDM172249I Explanation: System Action:
708
User Response: PWXEDM172256I Explanation: System Action: User Response: PWXEDM172257E Explanation:
No action is required. module: EDM Agent agent_ID has completed initialization The PowerExchange Agent identified in the message completed its startup procedure. Processing continues. No action is required. EDMSREP0: REPSTATUS operation failed, RC=rc A REPSTATUS was issued command but the execution of that command failed. The return code that was received from the REPSTATUS command is included in the message text. Error messages that further describe the problem should appear earlier in the EDMSLOG data set in the PowerExchange Agent. Processing continues. This message is normal if a REPSTATUS command is issued when the PowerExchange Agent parameters specify RepositoryMode=EDP. See the message PWXEDM172010I in the PowerExchange Agent JOBLOG to determine the RepositoryMode specified at startup. If RepositoryMode=Detail is specified and this message is issued, contact Informatica Global Customer Support.
PWXEDM172500I to PWXEDM172798I: The PowerExchange Logger

PWXEDM172500I Explanation: System Action: User Response: logger_title READY loggerid The PowerExchange Logger identified by logger_title and loggerid is ready for you to enter a command. The PowerExchange Logger waits for you to enter the command. Enter a PowerExchange Logger command for the designated PowerExchange Logger. Enter this number with the interactive commands for this PowerExchange Logger. To verify that you are entering a command for the correct PowerExchange Logger, get the outstanding reply number. The outstanding reply number is the number preceding the message number. In the following example, the outstanding reply number is the *05 preceding PWXEDMLOG172500I.
11.43.44 STC01278 *05 PWXEDM172500I ################ -READY- ########
For more information about the interactive PowerExchange Logger commands, see the PowerExchange Command Reference. PWXEDM172501A Explanation: System Action: User Response: logger_title AWAITING MORE INPUT loggerid The PowerExchange Logger received a partial command or subcommand and is waiting for the remainder of the command. The PowerExchange Logger waits on the remainder of a command or a subcommand. Enter a valid PowerExchange Logger command or subcommand.
709
EDM Logger initialization in-progress with EDMLID= subsystem and product level vrmm date The PowerExchange Logger initialization is in progress. EDMLID displays the subsystem name. The product level displays the PowerExchange Logger version (v), release (r) and modification (mm) level. The date field displays the PowerExchange Logger release date. The PowerExchange Logger continues processing captured data. No action is required. EDM Logger current RBA = current_RBA is less than requested RBA = requested_RBA The current writing position of the PowerExchange Logger is less than the starting relative byte address (RBA) requested by a reader task. The reader task ends and processing continues. Correct the requested RBA of the log read processor (LRP). Logger RBA = logger_RBA, Read RBA = read_RBA, Start RBA = start_RBA This message is part of the reader connection report and shows the following RBA information:

System Action: User Response: PWXEDM172503E Explanation: System Action: User Response: PWXEDM172504I Explanation:
Logger RBA. The location where the PowerExchange Logger is currently writing. Read RBA. The location last processed by the log reader. Start RBA. The requested starting location for the log reader. The RBAs point to the current block, but do not reflect the current record being processed within that block. System Action: User Response: PWXEDM172505I Explanation: System Action: User Response: PWXEDM172506I Explanation: System Action: User Response: The PowerExchange Logger processing continues. No action is required. EDM Logger UOW=unit_of_work This message is part of the unit of work (UOW) report and shows the PowerExchange Logger UOW information. The PowerExchange Logger processing continues. No action is required. logger_title subtask shutdown in progress The specified PowerExchange Logger received a stop request. The PowerExchange Logger begins the termination process. No action is required.
PWXEDM172507W logger_title subtask subtask abended with abend_code Explanation: System Action: User Response: The subtask identified by subtask, which is within the PowerExchange Logger identified by logger_title, has ended abnormally with the abend code abend_code. The specified subtask ends abnormally. This is an internal error. Collect all available information about the cause of the abend, and contact Informatica Global Customer Support. logger_title subtask TASK COMPLETE, Return Code=rc The PowerExchange Logger subtask specified by logger_title and subtask completed with the return code rc.
710
Processing continues. Use the return code to determine whether the task completed normally. If it did, no action is required. If it did not, collect all available information about the cause of the termination, and contact Informatica Global Customer Support. For information about the return code, see Return Code 221: PowerExchange Logger on page 917. EDM Logger subsystem_ID shutdown complete The termination for the PowerExchange Logger specified by subsystem_ID completed. The specified PowerExchange Logger ends normally. No action is required.
PWXEDM172510W EMERGENCY SHUTDOWN COMPLETE, Return Code=rc Explanation: The recovery routine (ESTAE) program received control following a system abend. The return code (rc) is one of the following:

0. No ITASKs or connections were active at termination time. 4. One or more ITASKs were active at termination time.
The PowerExchange Logger ends abnormally. Collect all available information about the cause of the shutdown, and contact Informatica Global Customer Support. For information about the return code, see Return and Reason Codes on page 913. EDM Logger initialization failed, unable to load module module The PowerExchange Logger was unable to load the specified module during initialization. The PowerExchange Logger ends abnormally. Collect all available information about the cause of the termination, and contact Informatica Global Customer Support. EDM Logger is now accepting data The PowerExchange Logger has completed its start-up processes. Change capture jobs may now be executed. Processing continues. No action is required. The EDMSDIR LOGRGRP parameter has been changed The LOGRGRP parameter has been changed. This cannot occur because formatting of sequence numbers is different. A cold start is required to perform this change. The PowerExchange Logger ends. Either cold start or change the LOGRGRP back to its original value. ASCB address in logger data record is not an ASCB The address passed in the PowerExchange Logger data record for the address space is incorrect. The PowerExchange Logger ignores the record and will not post the ECCR. If any ECCR is left in a wait, it must be cancelled. EDM Sysplex Report This is an informational message showing the result of status command. Processing continues.
PWXEDM172500I to PWXEDM172798I: The PowerExchange Logger 711
PWXEDM172512I Explanation: System Action: User Response: PWXEDM172513E Explanation: System Action: User Response: PWXEDM172514E Explanation: User Response: PWXEDM172517I Explanation: System Action:
User Response: PWXEDM172518I Explanation: System Action: User Response: PWXEDM172519I Explanation: System Action: User Response: PWXEDM172520I Explanation: System Action: User Response:
No action is required. Sysplex Name - sysplex_name Sysplex status - sysplex_status This is an informational message showing the result of status command and identifying general Sysplex information. Processing continues. No action is required. EDM Groupname - XCF_group_name Members Connected - This is an informational message showing the result of status command and showing PowerExchange members operations in the system. Processing continues. No action is required. Jobname jobname Sysplex sysplex_name Member XCF_member This is an informational message showing the result of status command. Processing continues. No action is required.
PWXEDM172521W Another CONSOLE is already activated, (e.g. SDSF) please deactivate Explanation: System Action: User Response: This is a warning that another console is activated under the ISPF task. The command is not executed until the other console is deactivated. End the ISPF by using the console.
PWXEDM172522W System name is incorrect return code=rc, reason code=reason Explanation: System Action: User Response: PWXEDM172523I Explanation: System Action: User Response: An improper system name was used when attempting to route a command. The command is not executed until the proper system name is used. Use the status command to find systems in the sysplex. No groups related to EDM were found A search for PowerExchange related activity was performed and no systems were found active. Processing continues. No action is required.
PWXEDM172524W ECCR_name on wrong MVS image to connect with Logger Explanation: System Action: User Response: An ECCR or Reader has tried to connect with the PowerExchange Logger from a system it cannot be connected from. If multiple MVS images are required, use pre or post log merge. The system continues ignoring input from the job. Run the job on the system with the PowerExchange Logger or establish a log merge environment.
712
Logger running from a non-APF authorized library, ROUTCDE=routing_code, DESC=descriptor_code The PowerExchange Logger was running from a library that was not an APF-authorized load library. If any unauthorized library is included in the STEPLIB concatenation, APF-authorization is dropped for it. The PowerExchange Logger ends. Authorize the load library from which the PowerExchange Logger is to be run. You can use the MVS SETPROG command to perform the library authorization.
PWXEDM172542W Change capture agent xcf_member_name connection to Logger logger_id deferred reason Explanation: This message is issued when the PowerExchange Logger has received a signon request from a change capture agent (an ECCR), xcf_member_name, but cannot process that request immediately. In this case, the signon is deferred and is processed after the PowerExchange Logger is able to do so. Processing continues. When the PowerExchange Logger is able to process the request, message PWXEDM172668I is issued to indicate that the signon request has now been processed and a response is sent back to the ECCR. If the deferred signon request fails, message PWXEDM172669I is issued instead of PWXEDM172668I. The name of the ECCR (xcf_member_name), the name of the PowerExchange Logger (logger_id), and a description of the reason why the signon had to be deferred temporarily (reason) are included in the text of the message. The only current value for reason is Logger quiesced. However, the processing in the ECCR is delayed until the PowerExchange Logger is able to process the signon request, and respond back to the ECCR. User Response: Investigate the reason for the delay in processing the signon request by the PowerExchange Logger. In a Post-Log Merge environment, one possible cause is that the PowerExchange Logger has entered a quiesced state for Post-Log Merge. It needs to leave that state (resume normal operations) before it can allow any ECCRs to connect. In this situation, you may need to refer to any messages that might have been issued in the Post-Log Merge task to determine why the PowerExchange Logger cannot resume normal operations. If you cannot identify and correct the problem, contact Informatica Global Customer Support. PWXEDM172543W Logger logger_id quiesce failed from xcf_member_name (jobname job_name on system system_name), return code=return_code, reason code=reason_code Explanation: This message is issued when the PowerExchange Logger has received a response to a quiesce request but the return code (return_code) and reason code (reason_code) indicate that the quiesce request could not be honored. The quiesce request (QUIESCL command) is sent to the Post-Log Merge task by the PowerExchange Logger because there are no ECCRs connected to it for the duration of the interval specified by TIME_CHKPT_FREQ in the PowerExchange Logger options (EDMUPARM). The name of the PowerExchange Logger (logger_id), the name of the Post-Log Merge task (xcf_member_name), the job name under which the Post-Log Merge task is executing (job_name), and the system on which it is executing (system_name) are all included in the text of the message. The message text also includes the value of the return code (return_code) and reason code (reason_code) that the PowerExchange Logger found in the QUIESCL response message. The reason codes that appear in the message are documented in Reason Codes 00000601 to 00004499: Command on page 921.
PWXEDM172500I to PWXEDM172798I: The PowerExchange Logger 713
System Action:
Processing continues and the PowerExchange Logger leaves the quiesced state. The state of the Post-Log Merge address space cannot be determined by the PowerExchange Logger. Investigate the reason for the error in processing the QUIESCL request by the Post-Log Merge task. You may need to refer to messages that may have been issued by the Post-Log Merge task itself for further information on why it failed to honor the quiesce request. To correct the problem, it may be necessary to recycle either the Post-Log Merge task or the PowerExchange Logger. If you cannot identify and correct the problem, contact Informatica Global Customer Support. Logger logger_id successfully resumed logging for merging by xcf_member_name (jobname job_name on system system_name) This message is issued when the PowerExchange Logger has received a successful response to a request to resume logging data. The response is issued by the Post-Log Merge task as a result of a RESUMEL request sent by the PowerExchange Logger to the Post-Log Merge task. The request was sent because the PowerExchange Logger had previously communicated to the Post-Log Merge task that the PowerExchange Logger was going to temporarily stop logging (quiesce itself ) as there were no ECCRs currently connected to the PowerExchange Logger. However, one or more ECCRs have now tried to connect to the PowerExchange Logger so it must change its status with the Post-Log Merge task. The purpose of the quiesce and resume process is to allow the Post-Log Merge task to operate more efficiently as it does not have to worry about merging data from any Loggers that are quiesced. The name of the PowerExchange Logger (logger_id), the name of the Post-Log Merge task (xcf_member_name), the job name under which the Post-Log Merge task is executing (job_name), and the system on which it is executing (system_name) are all included in the text of the message.
Processing continues No action is required.
PWXEDM172545W Logger logger_id resume failed from xcf_member_name (jobname job_name on system system_name), return code=return_code, reason code=reason_code Explanation: This message is issued when the PowerExchange Logger has received a response to a resume request but the return code and reason code indicate that the resume request could not be honored. The resume request (RESUMEL command) was sent by the PowerExchange Logger to the Post-Log Merge task because there are ECCRs that have asked to connect to the PowerExchange Logger but it was quiesced at that time. The message text contains the following variables:

logger_id is the name of the PowerExchange Logger. xcf_member_name is the name of the Post-Log Merge task. job_name is the job name under which the Post-Log Merge task is executing. system_name is the system on which the job is executing. return_code is the value of the return code. reason_code is the reason code that the PowerExchange Logger found in the RESUMEL response message. The reason code is documented in Reason Codes 00000601 to 00004499: Command on page 921. User Response: No action is required.
PWXEDM172546W Invalid xcf_command response received by Logger logger_id from xcf_member_name (jobname job_name on system system_name) - reason_text Explanation: This message is issued when the PowerExchange Logger has received a QUIESCL or RESUMEL message but there is an error in the message or in the state of the
714
PowerExchange Logger at that time. As a result, the PowerExchange Logger was unable to properly process the message. The XCF command (either QUIESCL or RESUMEL), the name of the PowerExchange Logger (logger_id), the name of the process that sent the message (xcf_member_name), the job name under which the sender is executing (job_name), and the system on which it is executing (system_name) are all included in the text of the message. The reason_text is one of the following values:

Command received was not reply Sender not Post-Log Merge task Logger not currently quiesced System Action: Processing continues. If the message was for a RESUMEL command and the PowerExchange Logger is currently quiesced, it will remain in that state. This, in turn, would mean that one or more ECCRs might be unable to complete their connection to the PowerExchange Logger. User Response: Investigate the reason for the error in processing the message by the PowerExchange Logger. You may need to refer to messages that may have been issued by the corresponding Post-Log Merge task for further information on what happened to cause the error in the quiesce or resume request. If the PowerExchange Logger is currently quiesced, and does not leave that state due to the problem described in this message, it may be necessary to recycle either the Post-Log Merge task or the PowerExchange Logger. If you cannot identify and correct the problem, contact Informatica Global Customer Support. Post-Log Merge task xcf_member_name (jobname job_name on system system_name) {is now active|has left the system} This message is issued when the PowerExchange Logger detects a status change in the Post-Log Merge task that is supposed to merge the data the PowerExchange Logger is recording. The Post-Log Merge task has: Joined the XCF group (and has processed and responded to the signon request of the PowerExchange Logger) as a result of either the Post-Log Merge task or the PowerExchange Logger initializing Left the XCF group and so has stopped merging data from the PowerExchange Logger The logical name of the Post-Log Merge task (xcf_member_name), the actual job name of the Post-Log Merge task (job_name) and the system where the Post-Log Merge task is/was executing (system_name) are all included in the text of the message. The message also identifies whether the Post-Log Merge task has become active or has left the system. System Action: Processing continues. However, if the PowerExchange Logger is currently quiesced, and the Post-Log Merge task has left the XCF group, the quiesce status of the PowerExchange Logger is automatically lifted. No action is required.
User Response:
PWXEDM172548W Invalid signon command received by Logger logger_id from xcf_member_name (jobname job_name) - reason_text Explanation: This message is issued when the PowerExchange Logger has received a SIGNON command but there is an error in the command. As a result, the PowerExchange Logger was unable to properly process the SIGNON command. The name of the PowerExchange Logger (logger_id), the name of the process that sent the command (xcf_member_name) and the job name under which the sender is executing (job_name) are all included in the text of the message. The message text also includes a description of what problem the PowerExchange Logger found in the SIGNON message. The reason_text is one of the following values:
715
Command received was not request Command received was not reply Sender not Post-Log Merge task Processing continues. However, if the PowerExchange Logger is waiting for confirmation of a successful signon to the Post-Log Merge task, the PowerExchange Logger might be unable to complete its initialization process. Investigate the reason for the error in processing the SIGNON message by the PowerExchange Logger. You may need to refer to messages that may have been issued by the corresponding Post-Log Merge task for further information on what happened to cause the error in the signon request. If the PowerExchange Logger is currently initializing, and does not complete that process due to the problem described in this message, it may be necessary to recycle either the Post-Log Merge task or the PowerExchange Logger. If you cannot identify and correct the problem, contact Informatica Global Customer Support.
System Action:
User Response:
PWXEDM172549W Logger logger_id signon failed to xcf_member_name (jobname job_name on system system_name), return code=return_code, reason code=reason_code Explanation: This message is issued when the PowerExchange Logger has received a response to a signon request but the return code and reason code indicate that the signon request could not be honored. The signon request was sent by the PowerExchange Logger to the Post-Log Merge task because the PowerExchange Logger either found the Post-Log Merge task active during its own initialization or discovered that the Post-Log Merge task had just entered the system (joined the XCF group). The name of the PowerExchange Logger (logger_id), the name of the Post-Log Merge task (xcf_member_name), the job name under which the Post-Log Merge task is executing (job_name), and the system on which it is executing (system_name) are all included in the text of the message. The message text also includes the value of the return code and reason code that the PowerExchange Logger. The message text also includes the value of the return code (return_code) and reason code (reason_code) that the PowerExchange Logger found in the SIGNON response message. The reason codes that appear in the message are documented in Reason Codes 00000601 to 00004499: Command on page 921. System Action: Processing continues. However, if the PowerExchange Logger is waiting for confirmation of a successful signon to the Post-Log Merge task, the PowerExchange Logger might be unable to complete its initialization process. Investigate the reason for the error in processing the SIGNON message by the PowerExchange Logger. You may need to refer to messages that may have been issued by the corresponding Post-Log Merge task for further information on what happened to cause the error in the signon request. If the PowerExchange Logger is currently initializing, and does not complete that process due to the problem described in this message, it may be necessary to recycle either the Post-Log Merge task or the PowerExchange Logger. If you cannot identify and correct the problem, contact Informatica Global Customer Support. Number of active ECCRs = nnnn, Logger is currently {quiesced|not quiesced} This message is issued during the processing of a PowerExchange Logger Display command for writer connections. It shows the number of active ECCRs, nnnn, currently connected to this PowerExchange Logger. Even though type 1 ECCRs that are not currently connected to the PowerExchange Logger can be shown in the Writer Connection report, they are not counted as being active. The message text also shows whether the PowerExchange Logger is currently quiesced or not. The PowerExchange Logger can only be quiesced if it is part of a Post-Log Merge group. In a Post-Log Merge environment, the PowerExchange Logger can inform the Post-Log Merge task if there are no active ECCRs. This speeds up the merging of data from all the PowerExchange Loggers by the Post-Log Merge task.
716 Chapter 4: PWXEDM172000 to PWXEDM173002
User Response:
Processing continues. No action is required. Logger oper_name operation for queue queue_name failed for UOW uow_id with return code=return_code, reason code=reason_code This message is issued when the PowerExchange Logger has attempted an operation on an internal queue and the return code from the operation indicated that the operation was not successful. The PowerExchange Logger was processing a UOW record when the error occurred. The type of operation that was attempted (oper_name), the name of the internal queue (queue_name), the UOW id assigned to the UOW by the PowerExchange Logger (uow_id), the return code (return_code), and the reason code (reason_code) from the failed operation are all included in the text of the message. The return and reason codes for this message, which are generated in EDMQMGR0, are not currently documented. The value of oper_name is one of the following values:

Add (Phase1) Add (Phase2) Delete (UOW) The value of queue_name is one of the following parameters:

GBLXCFQCB GBLOUQQCB
The PowerExchange Logger ends abnormally. Investigate the reason for the failure in the queue operation, using appropriate operating system documentation, along with any other messages that may have been issued in conjunction with this problem. If you cannot correct the problem, contact Informatica Global Customer Support. Logger logger_id is now quiesced - Post-Log Merge task xcf_member_name (jobname job_name on system system_name) notified This message is issued when the PowerExchange Logger has entered the quiesce state. This state occurs when there are no ECCRs connected to it and this has been true for the duration of the interval specified by TIME_CHKPT_FREQ in the PowerExchange Logger options (EDMUPARM). This will only occur for PowerExchange Loggers that are part of a Post-Log Merge environment. The corresponding Post-Log Merge task has been notified, which allows it to operate more efficiently because it does not have to worry about merging data from any PowerExchange Loggers that are quiesced. The name of the PowerExchange Logger (logger_id), the name of the Post-Log Merge task (xcf_member_name), the job name under which the Post-Log Merge task is executing (job_name), and the system on which it is executing (system_name) are all included in the text of the message.
Processing continues. No action is required. Logger logger_id attempt to {quiesce|resume} failed with return code=return_code, reason code=reason_code This message is issued when the PowerExchange Logger has attempted to send a command to the Post-Log Merge task, but the PUT operation to XCF failed. The command will have been either a quiesce (QUIESCL command) or a resume (RESUMEL) command.
717
The name of the PowerExchange Logger (logger_id), the specific command that was being attempted, and the return code (return_code) and reason code (reason_code) that resulted, are all included in the text of the message. The return and reason codes for this message, which are generated in EDMXXCF, are not currently documented. System Action: Processing continues. If the command being sent was a quiesce, the PowerExchange Logger is not quiesced. This in turn means that the Post-Log Merge task will have to continue to merge data from this PowerExchange Logger, even though there may not be any new user data being logged. If the command was a resume, the PowerExchange Logger will not leave the quiesced state. This which means that ECCRs that try to connect to the PowerExchange Logger will be delayed (will not get a response to a signon request) until the problem is resolved. User Response: Investigate the reason for the failure in the PUT operation, using appropriate operating system documentation, along with any other messages that may have been issued in conjunction with this problem. You may need to refer to messages that may have been issued by the corresponding Post-Log Merge task for further information on what happened to cause the error in sending the command. To resolve the problem, it may be necessary to recycle either the Post-Log Merge task or the PowerExchange Logger. If you cannot correct the problem, contact Informatica Global Customer Support. Logger logger_id attempting to write to active log dataset_name at RBA rba, but is quiesced This message is issued when the PowerExchange Logger has attempted to log some data but the Physical Logger has determined that the PowerExchange Logger is quiesced. When a PowerExchange Logger is quiesced, it must not write any new data to the current active log data set because the Post-Log Merge task will not retrieve it. The name of the PowerExchange Logger that encountered this problem (logger_id), the name of the active log data set it was attempting to write to (dataset_name), and the RBA location that was to be written (rba) are all included in the text of the message. System Action: User Response: The PowerExchange Logger ends abnormally. This situation indicates that a logic error has occurred in the processing of a PowerExchange Logger that is quiesced. PowerExchange Loggers only become quiesced in a Post-Log Merge environment. You need to gather the output from the PowerExchange Logger and its corresponding Agent, and report the problem to Informatica Global Customer Support. Logger current timestamp=cur_timestamp is less than requested timestamp=req_timestamp. This message is issued when the PowerExchange Logger receives a request to send data to a log reader but the starting location that is requested, req_timestamp, is later than the location at which the PowerExchange Logger is currently recording, cur_timestamp. The data requested does not exist yet. This message is only issued when the PowerExchange Logger is operating in a Post-Log Merge environment. The timestamps displayed are TOD clock values. The PowerExchange Logger continues normally. However, the request to read log data is terminated. This will most likely result in the abnormal termination of the process that requested the data. The process that requested the log data has used an invalid location at which to start reading. This is most likely the result of using incorrect or obsolete restart information when starting that process. Determine what was the origin of the invalid starting location and correct it so that log reading can start at a valid location. To resolve the problem, you might need to cold start the process that is requesting the data to be read from the
System Action:
User Response:
718
PowerExchange Logger. If you cannot correct the problem, contact Informatica Global Customer Support. PWXEDM172557E Explanation: Logger command_name command failed for logger_dataset, failure_reason The PowerExchange Logger was processing a command for an active or archive log data set, when it determined that the command could not be processed. The command being processed, the data set name upon which the command was operating, and a description of the problem encountered, are all included in the text of the message. Where:

command_name = DELETE_LOG failure_reason = data set not found in any restart data set deletion of current active log not permitted deletion of active log not needing archival not permitted
For example: PWXEDM172557E PWXEDM172557E Logger { command failed for $44, { Logger DELETE_LOG command failed, for EDMUSR1.EDMTEST.DBML.SECLOG.DS94, dataset not found in any restart dataset Logger DELETE_LOG command failed, for EDMUSR1.EDMTEST.DBML.SECLOG.DS04, deletion of current active log not permitted Logger DELETE_LOG command failed, for EDMUSR1.EDMTEST.DBML.PRILOG.DS04, deletion of active log needing archival not permitted The command being processed will terminate. However, PowerExchange Logger processing will continue normally. Examine the description of the problem that was encountered, and see if there was an error in the command that was issued, which could be corrected. For example, if you are trying to delete an archive log data set (using the DELETE_LOG command) but you have entered the data set name incorrectly, reenter the command with the correct data set name. If you cannot correct the problem, contact Informatica Global Customer Support. EDM Logger immediate command received: command In response to the outstanding write-to-operator-with-reply (WTOR) command, the operator entered the immediate command, specified by command. The command executes immediately. No action is required. EDM Logger input commands accepted, execution started The PowerExchange Logger read the command set from the SYSIN file for a batch job. No syntax errors were found. The system executes the command set. No action is required.
PWXEDM172557E
PWXEDM172557E User Response: System Action:
PWXEDM172573W EDM Logger command execution aborted due to syntax errors Explanation: System Action: The batch job command set, which was read from the SYSIN file, contains syntax errors. The system does not execute the command set.
719
User Response:
Determine the cause of the syntax errors, and enter a valid command set. To help you determine the cause of the errors, a more specific message precedes this message.
PWXEDM172574W EDM Logger command set and or input block flushed, with return code 08 Explanation: System Action: User Response: A command was entered incorrectly in a command set. The system does not execute the command set. Determine the cause of the command error, and enter a valid command set. To help you determine the cause of the errors, a more specific message precedes this message. EDM Logger command command for userid (task sequence_number) abended with abend_code The specified PowerExchange Logger command for the specified user ID terminated abnormally with the abend code shown. The internal PowerExchange Logger assigned task sequence number is provided for trouble shooting. The subtask ends. Collect all available information about the cause of the abend, including the contents of this message, and contact Informatica Global Customer Support. EDM Logger command command complete for userid (task task_sequence_number), with Return Code=rc The specified PowerExchange Logger command set for the specified task completed with the return code rc. The subtask completes normally. Use the return code and the associated command message output to determine whether the command completed. For more information, see Return Code 221: PowerExchange Logger on page 917 and Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDM Logger command command in progress for userid (task task_sequence_number) A PowerExchange Logger started an action subtask for the specified command. The subtask continues to run. Wait for the command to complete. Change records logged - number_of_records, comprising number_of_UOWs UOWs, current RBA=relative_byte_address, current time=timestamp This message shows the number of records and UOWs captured during this execution of the PowerExchange Logger. It also shows the current relative byte address and the current time in TOD clock format, which is useful in Post-Log Merge environments. The PowerExchange Logger processing continues. No action is required.
720
log_reader_name starting_sequence_number hh:mm:ss.th yyyy/ddd sysplex_name function_name This message is issued as a result of issuing the Display command for the Post-Log Merge task. It lists each of the log readers that are currently connected to the Post-Log Merge task, along with some information about the data requested by the log reader. This message contains:

The name of one log reader (log_reader_name) The sequence number at which that log reader started reading (starting_sequence_number) The date and time that are equivalent to that starting sequence number (hh:mm:ss.th yyyy/ddd) The name of the sysplex in which the log reader is executing (zsysplex_name). If the log reader is in the process of shutting down, the function_name variable will contain a value of STOP. If there are currently no log readers connected to the Post-Log Merge task, the log_reader_jobname will show as NO-JOBS and none of the other information will be shown. This message will be issued once for each log reader that is connected. It will be followed by multiple PWXEDM172580I messages, one for each PowerExchange Logger from which data is being merged for this log reader. The PWXEMD172579I messages will be preceded by one title line to identify each of the fields that are contained in the message. System Action: User Response: PWXEDM172580I Explanation: Processing continues. No action is required. logger_jobname smf_id current_sequence_number hh:mm:ss.th yyyy/ddd rba flag log_dataset_name This message is issued as a result of issuing the Display command for the Post-Log Merge task. It follows message DTLEMD172579I for each specific log reader. It lists each PowerExchange Logger from which data is being merged for that log reader along with status information about the data being merged from that PowerExchange Logger. The message contains:

The job name (logger_jobname) for the PowerExchange Logger The system name (smf_id) of the system on which the PowerExchange Logger is executing The sequence number of the data that is currently being read from that PowerExchange Logger (current_sequence_number) The date and time that are equivalent to that current sequence number hh:mm:ss.th yyyy/ddd) The RBA in that PowerExchange Logger's log data that contains that sequence number (rba) Coded information about the merge status (flag) The data set name of the log data set from which data is currently being merged from that PowerExchange Logger (log_dataset_name). This message will be issued once for each PowerExchange Logger from which data is being merged for the log reader. The DTLEDM172580I messages will be preceded by one title line to identify each of the fields that are contained in the message. System Action: User Response: Processing continues. No action is required.
721
PWXEDM172581W No changes were made to loggerid logger options no keywords were found Explanation: System Action: User Response: PWXEDM172582I Explanation: System Action: User Response: PWXEDM172585I Explanation: System Action: User Response: PWXEDM172586I Explanation: System Action: User Response: PWXEDM172587E Explanation: System Action: User Response: PWXEDM172588E Explanation: You entered a request to update existing options for the specified PowerExchange Logger. However, PowerExchange Change found no keywords to make those changes. Processing continues. Enter the correct keywords, and run the job again. EDM Logger loggerid has been deleted The request to delete the specified PowerExchange Logger completed. Processing continues. No action is required. EDM Logger successfully built logger master control block cb_name The PowerExchange Logger completed building the PowerExchange Logger internal master control block with the name cb_name. Processing continues. No action is required. EDM Logger was unable to {connect to|disconnect from} a manager. Return code=rc, reason code=reason The PowerExchange Logger could not connect to or disconnect from a media manager. Processing continues. No action is required. EDM Logger aborted, //EDMPARMS DD statement is missing An EDMPARMS DD statement was not found in the job step. The PowerExchange Logger address space ends abnormally. Include a valid EDMPARMS DD statement in the job step, and run the job again. EDM Logger aborted, EDMZPARM module could not be loaded An error occurred when the PowerExchange Logger attempted to open the EDMPARMS DD statement, load the member EDMUOPT0 from that library, or load the default options member EDMCOPT0 from the STEPLIB. The PowerExchange Logger address space ends abnormally. Include a valid EDMPARMS DD statement in the job step, and restart the PowerExchange Logger. EDM Logger aborted, //EDMPARMS DD statement is invalid The EDMPARMS DD statement must point to a single load library. This message indicates that the DD statement was concatenated or that the data set specified in the DD statement was not a load library. The data set must be DSORG=PO and RECFM=U. The PowerExchange Logger address space terminated abnormally. Include a valid EDMPARMS DD statement with a valid load library name in the job step, and restart the PowerExchange Logger.
722
PWXEDM172590W {Log reader|Change capture|Unknown} agent xcf_member_name disconnected from Logger logger_id, return code=return_code, reason code=reason_code Explanation: This message is issued when an agent attempts to connect to the PowerExchange Logger but some type of error occurs while trying to process the connection. The PowerExchange Agent may either be a change capture agent (an ECCR) which supplies data to be logged or a log reader agent which receives data that has been logged. The message text includes the type of the PowerExchange Agent, the name of the PowerExchange Agent (xcf_member_name), the name of the PowerExchange Logger (logger_id), as well as a return code (return_code) and reason code (reason_code) that identifies the problem that was encountered. The reason codes that appear in the message are documented in Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. System Action: The connection request is refused. The PowerExchange Agent that requested the connection is sent a negative response to its Signon request. This will typically result in a failure in the process that attempted to connect to the PowerExchange Logger. Investigate the reason for the failure in the Signon, using any other messages that may have been issued, along with appropriate operating system documentation, if necessary. It may be necessary to restart the log reader or change capture agent, if it failed as a result of the connection refusal. If you cannot correct the problem, contact Informatica Global Customer Support. EDM Logger data transfer for client will start at Logrba=logrba The PowerExchange Logger received a request from the specified log reader (client) to begin transferring data to either begin or end transferring data at the specified logrba. The first case (start) of the message will always be issued when a log reader connects to the PowerExchange Logger. The second case (end) only occurs if the log reader has specified a log location at which it wishes to stop receiving data. Processing continues. No action is required. EDM Logger data transfer for client ended. num_read records enqueued, num_filter records filtered out The PowerExchange Logger completed the data transfer for the specified client. The number of change records that the PowerExchange Logger passes to the log reader is indicated by the variable num_read. The PowerExchange Logger filters change records based on the list of EDMNAMEs passed by the log reader and only passes the log reader change records for those sources. The variable num_filter indicates the number of change records that the PowerExchange Logger read but did not pass to the log reader. If the log reader does not provide a resource interest list, the PowerExchange Logger does not filter change records and the value for num_filter is zero. The PowerExchange Logger also writes message PWXEDM172791I to its EDMMSG data set, which includes the number of sources in the resource interest list. To determine the EDMNAMEs that the log reader included in the resource interest list, see the PWXEDM263025I messages in the EDMMSG data set of the log reader address space. System Action: User Response: PWXEDM172593I Explanation: Processing continues. No action is required. EDM Logger restart process in progress using checkpoint at Logrba=logrba The PowerExchange Logger has determined the checkpoint to use during restart. The logger will start searching for the checkpoint in the log data set containing the checkpoint at logrba.
User Response:
723
System Action: User Response: PWXEDM172594I Explanation: System Action: User Response: PWXEDM172595I Explanation: System Action: User Response:
Processing continues. No action is required. EDM Logger will commence log forward restart processing at Logrba=logrba The PowerExchange Logger completed searching the restart checkpoint in the current active log and will start forward processing from the specified logrba. Processing continues. No action is required. EDM Logger will commence recording at Logrba=logrba The PowerExchange Logger completed forward processing of the current active log and will begin recording at the specified logrba. Processing continues No action is required.
PWXEDM172596W EDM Logger waiting for {reader|ECCR} Task (job_name) Explanation: When you issue an MVS P or STOP command with the QUIESCE option, the PowerExchange Logger lists the reader tasks and ECCRs that must complete before the PowerExchange Logger begins shutdown. The PowerExchange Logger stops processing the current command set. No action is required. EDP Log Reader {initialized|ended} for rder_id at date time, return code=rc, reason code=reason The PowerExchange Logger initiated/ended the Log Reader, rdr_id, on the date and time displayed in the message. Processing continues. No action is required. If rc and reason are non-zero, see Reason Codes 00000601 to 00004499: Command on page 921.
PWXEDM172599W DELETE=YES was specified for loggerid logger options which do not exist request ignored Explanation: System Action: User Response: PWXEDM172602E Explanation: A request was made to delete the specified options. However, the PowerExchange Logger could not find the options in the EDMZPARM module. The PowerExchange Logger ignores the request and ends the function. Enter the request with a valid PowerExchange Logger ID. EDM Logger internal GENCB for VSAM_control_block failed with Return Code = rc, and reason code reason for ddname ddname VSAM GENCB operation failed and returned a return code in R15 and a reason code in R0. The value of the VSAM_control_block is either RPL or ACB. The variable rc represents the return code and reason represents the reason code. If the VSAM operation is against the JOURNAL or TRACE file, the PowerExchange Logger suspends VSAM file processing. If the operation is for a DEFINE_LOG command, the PowerExchange Logger ends the command. Otherwise, the PowerExchange Logger ends. Check and correct the VSAM file definitions, and run the job again.
System Action:
User Response:
724
EDM Logger internal VSAM macro failed with Return Code = rc, and feedback code code for ddname ddname A VSAM macro operation failed. SHOWCB captured the return code and feedback code. If the VSAM operation is against the JOURNAL or TRACE file, the PowerExchange Logger suspends VSAM file processing. If the operation is for a DEFINE_LOG command, the PowerExchange Logger ends the command. Otherwise, the PowerExchange Logger ends. Check the appropriate VSAM manual for an explanation of the return code and feedback code to determine the cause of the error. Correct the problem, and run the job again. UNALLOCATION FAILED, EC = error_code Dynamic deallocation failed during an SVC 99 operation. The PowerExchange Logger ends. Collect all available information about the cause of the dynamic deallocation failure, and contact Informatica Global Customer Support. IDCAMS PASSED Return Code = rc The return code from IDCAMS is not zero. Either the DEFINE or DELETE CLUSTER operation failed. If the IDCAMS operation is against the JOURNAL file, the PowerExchange Logger suspends JOURNAL file processing. Otherwise, the PowerExchange Logger ends. For information about the return code, see the appropriate IDCAMS manual. Determine the cause of the error, correct the problem, and run the job again. EDM Logger internal MODCB for {ACB|RPL} failed with RC= rc, and reason code reason for ddname ddname VSAM MODCB operation failed and returned a return code in R15, shown in rc, and a reason code in R0, shown in reason. If the VSAM operation is against the JOURNAL or TRACE file, the PowerExchange Logger suspends VSAM file processing. If the operation is for a DEFINE_LOG command, the PowerExchange Logger ends the command. Otherwise, the PowerExchange Logger ends. Check and correct the VSAM file definitions, and run the job again.
User Response:
User Response:
PWXEDM172608W DELETE=YES was specified for default_options_module logger options default options cannot be deleted Explanation: The DEFINE command internal code attempted to delete the default options module. This operation is not allowed. This message is displayed if you entered the default PowerExchange Logger title '########', which is a PowerExchange Logger reserved word. The PowerExchange Logger does not let you delete the default options for this PowerExchange Logger. The system ignores the deletion attempt and displays this message. Enter the correct PowerExchange Logger ID in the DEFINE command, and issue the command again. {UNALLOCATE|ALLOCATE} FAILED FOR ACTIVE {COPY|ARCHIVE} COPY DSN = dsname RC = return_code, EC = error_code Dynamic allocation, UNALLOCATE or ALLOCATE, failed for the specified data set. This message is issued in one of two formats. Error (E) or Warning (W) levels.
725
System Action:
If this is an E level message, the command will terminate. If this is a W level message, the command will continue. Warning level messages are issued for optional data sets, such as spill files. Error level messages are issued for failures related to required data sets. Correct the cause of the allocation failure and reenter the command.
User Response:
PWXEDM172611W n COMMAND SET(S) FLUSHED DUE TO ERROR Explanation: A command set terminated abnormally with a return code of 8 or higher. The PowerExchange Logger flushes all command sets queued for execution for the same user. The number of command sets flushed are shown in n. The PowerExchange Logger flushes all command sets already queued for the user without executing them. Correct the problem that caused the error, and run the job again. Command command is not allowed; EDM Logger feature is not installed This command is not valid for the Informatica Corporation PowerExchange Logger product you have installed on your system. The command set is not executed, and all following command sets are flushed. See the appropriate Informatica Corporation documentation for the correct command, and issue that command. Otherwise, contact the Informatica Corporation sales organization to purchase the additional features required to use this command. I/O Error, DSN=dsname An I/O error occurred during the processing of the specified data set. The message that follows this message provides the SYNAD exit routine error information. The PowerExchange Logger ends the command set. Use the information in the message that follows this one to determine the cause of the I/O error, correct the problem, and resubmit the request. I/O ERROR SYNAD DATA: error_data An I/O error occurred during processing. This message provides additional information about the SYNAD exit routine error. The PowerExchange Logger ends the command set. Use the SYNAD exit routine error information to determine the cause of the error. Correct the problem, and submit the request again. action failed for DSN=dsname A request to perform an action on the data set specified by dsname failed. The possible actions include OPEN or CLOSE the data set or the RDJFCB, which is a macro that reads the data set job file control block. The PowerExchange Logger subtask abends, and the PowerExchange Logger ends the command set. To determine the cause of the abend, check the PowerExchange Logger job log for system messages that can provide additional information. Correct the problem, and submit the request again. {OPEN|CLOSE} ABEND abend_code FOR DSN=dsname A request to OPEN or CLOSE the data set specified by dsname terminated abnormally with the indicated abend code. The PowerExchange Logger subtask abends, and the PowerExchange Logger ends the command set.
PWXEDM172615E Explanation: User Response:
User Response:
726
User Response:
To determine the cause of the abend, look in the PowerExchange Logger job log for system messages that can provide additional information about the abend. Correct the problem, and submit the request again. EDM Logger Task (task_name) terminated prematurely interrupt code=interrupt_code The task listed had abended prematurely from execution. The code displayed is the termination ECB of the task. The system will attempt shutdown after this error. Restart the PowerExchange Logger and contact Informatica Global Customer Support.
PWXEDM172619W EDM Logger has adjusted your primary and secondary archive allocation by 25. Explanation: An abend SB37 has occurred during the archive log process. The PowerExchange Logger is adjusting the allocation by 25. Update your parameters with an appropriate archive value. The archive will be driven with the higher values. Update your archive options with a higher value for archiving. Open/Write error attempting to post function to the globalq Rc=return code Rsn=reason code An error has occurred while attempting to post a function to the global queue for the edmlllg0 module. The PowerExchange Logger abends. Restart the PowerExchange Logger and contact Informatica Global Customer Support. USER:userid NOT AUTHORIZED TO USE FUNCTION:function The functional security module detected that the specified user is not authorized to use the requested function. (The text of this message may be changed by your system administrator at installation time by using the installation security exit.) The PowerExchange Logger ends the function. Contact your system administrator to get authorization to use this function. EDM Logger loggerid not found. The DEFINE function failed to find the PowerExchange Logger specified by loggerid in the options module. The DEFINE function skips this PowerExchange Logger and continues processing. Edit your options module to include a valid PowerExchange Logger ID, and run the job again.
User Response: PWXEDM172620E Explanation: User Response: PWXEDM172621E Explanation:
User Response:
PWXEDM172623W EDM Logger was unable to allocate TRACE data set, tracing suspended Explanation: User Response: An attempt by the PowerExchange Logger to allocate the trace data set failed. Processing continues without the trace facility. Check for specific allocation error messages preceding this message, and correct the allocation problem. If necessary, change the journal data set name in the PowerExchange Logger DEFINE command options.
PWXEDM172624W EDM Logger parms module EDMUPARMS not found in EDMPARMS library, default EDMZPARM will be used Explanation: User Response: The parameter options module was not found in the EDMPARMS library. The default module is loaded into memory. The system loads the default module, EDMZPARM. Check the EDMPARMS library for the EDMUPARM member. For more information on creating EDMUPARM, see the PowerExchange Installation Guide for MVS Components.
727
PWXEDM172625W EDM Logger trace I/O error, tracing facility temporarily suspended Explanation: User Response: An attempt by the PowerExchange Logger to READ or WRITE the trace data set failed. Processing continues without the trace facility. Check for specific allocation error messages preceding this message, and correct the allocation problem. If necessary, change the journal data set name in the PowerExchange Logger DEFINE command options. EDM Logger {Internal|External} trace status is {*ACTIVE*|*INACTIVE*}, loggerid This message specifies whether the trace type is internal or external and whether the trace status is active or inactive for the specified PowerExchange Logger. Processing continues. No action is required. EDM Logger DEFINE_LOG aborted; required statement_name DD statement missing The DEFINE_LOG function failed to locate a required DD statement in the JCL. The name of the DD statement is specified by statement_name. The DEFINE_LOG function ends. Add a valid DD statement to your JCL, and run the job again. EDM Logger DEFINE_LOG aborted; invalid condition ddname data set The DEFINE_LOG function failed due to an invalid condition detected in the restart data set in the JCL. The conditions are DUMMY, TEMP, or SYSIN/SYSPUT and ddname is the ddname of the restart data set that has the error. The DEFINE_LOG function ends. Verify that you have valid ERDS01/ERDS02 data sets in your JCL for this job, and run the job again. EDM Logger internal macro failed for ddname data set The DEFINE_LOG function failed due to an invalid return code received from the internal macro for the data set specified by ddname. The DEFINE_LOG function ends. Verify that you have valid ERDS01/ERDS02 data sets in your JCL for this job, and run the job again. EDM Logger ERDS active log data set record is full, DDNAME=ddname The active log data set is full, and you cannot insert additional entries. The variable ddname specifies the DD name of the full restart data set (ERDS). The PowerExchange Logger aborts the DEFINE_LOG command with a return code of 8. Use the VSAM IDCAMS REPRO command to dump the restart data set. Determine the current status of the restart data set, correct the problem, and run the job again. Specified DSNAME already exists in ERDS, DDNAME=ddname You entered a DEFINE_LOG command with a data set name that already exists in the restart data set (ERDS). An entry is made in a restart data set (ERDS) if the specified data set name currently exists in either the active or archive record of that restart data set. The variable ddname specifies the DD name of the specified restart data set. The DEFINE_LOG command ends. Either correct the data set name in the control statement and run the command again, or delete the existing data set name from the restart data set and run the job again.
User Response:
User Response:
User Response:
728
EDM Logger restart data set with ddname ERDS01 is empty The PowerExchange Logger requires at least one restart data set to operate. The data set allocated to ERDS01 is empty. This operation abends. Verify that you have at least one valid PowerExchange Logger restart data set in the JCL, and run the job again. EDM Logger restart data set with ddname ERDS02 is empty The PowerExchange Logger requires at least one restart data set to operate. The data set allocated to ERDS02 is empty. Processing continues with only one restart data set. Check the PowerExchange Logger restart data sets in the JCL to verify that the correct second data set was specified and that it exists.
PWXEDM172634W EDM Logger dsname timestamp mismatch detected. Processing continues. Explanation: User Response: The PowerExchange Logger detected a time stamp mismatch between the two restart data sets specified for the dual mode. Processing continues with only one restart data set. Check the PowerExchange Logger restart data sets in the JCL to verify that the correct second data set was specified and that it exists. Also, verify that the two restart data sets have the same time stamp. EDM Logger internal logic error building control_block for ERDS The PowerExchange Logger was unable to build the specified internal log control block for the specified restart data set (ERDS). The task ends abnormally with a user abend code of U3035 and a reason code of X'FFFF00xx'. Get the job step listing, and contact Informatica Global Customer Support. EDM Logger could not find logrba=eol_rba in any log data set. Highest logrba found is hi_rba The log manager attempted to find the end-of-log RBA (eol_rba), which is the log record that has been recorded in the PowerExchange Logger restart data set as the highest RBA written. This RBA cannot be found in any log data set. The variable hi_rba indicates the highest RBA that could be found in any data set. The task ends abnormally with a user abend code of U3035. The most likely cause is that the log data set containing the requested RBA was deleted from the restart data set by the DELETE_LOG command. If the data set has not been reused, run the DEFINE_LOG command to add this data set back into the restart data set. Restart the PowerExchange Logger. EDM Logger Restart Log Manager unable to initialize EDML restart data set ddname The PowerExchange Logger was unable to initialize the restart data set allocated to the specified ddname. The task ends abnormally with the user abend code of U3035 and reason code X'FFFF00xx'. Verify that you specified the correct PowerExchange Logger restart data sets in the JCL. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDM Logger system timestamp for ERDS = timestamp The PowerExchange Logger displays the system time stamp from the restart data set (ERDS). The tasks that are running continue. No action is required.
User Response:
User Response:
PWXEDM172638I Explanation: User Response:
729
EDM Logger loggerid dsname=dsname, startrba=startrba, endrba=endrba At initialization time, the PowerExchange Logger shows which one of the active log data sets the system is using so you can verify it is starting with the correct one. The task continues to run. No action is required. EDM Logical Logger unable to obtain new internal log buffer The PowerExchange logical logger was unable to get a new buffer to continue logging operations. The task ends abnormally with the user abend code of U3035 and the reason code X'F9FF00xx'. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. For more information about the reason code, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDM Logical module received invalid return code from move routine Either the PowerExchange logical logger or logical ready module received an invalid return code from the internal routine that moves log records to the buffer. The task ends abnormally with a user abend code of U3035 and a reason code of X'F9FF00xx'. Recreate the problem by getting a PowerExchange Logger trace using the TRACE command. Have the trace file and the job step listing available, and contact Informatica Global Customer Support. For more information about the reason code, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDM Log allocation error dsname=dsname, error status=reason The PowerExchange physical logger encountered an error while attempting to allocate the active or archive log data set specified by dsname. The status shows the error reason code that the MVS dynamic allocation returns. The log manager actions vary depending on the type of data set involved. The following actions apply to active log data sets: If the error is encountered during log manager initialization, PowerExchange startup ends. If two copies of the active log data set are defined, this message appears only once. For archive log data sets, two copies of the archive log data sets are defined and processing continues on the remaining archive log data set. Your response varies depending on the type of data set involved and the type of error that occurred. If you were allocating active log data sets and if the problem occurred during initialization, you can resolve the problem by doing one of the following:
User Response:
User Response:
Explanation: Explanation:
Resolve the error associated with the active log data set as indicated by the reason code. Provide another copy of the active log using IDCAMS. Update the restart data set (ERDS) with the PowerExchange Logger batch utility. Restart the PowerExchange Logger. or For archive log data sets
If the problem occurred during allocation with the intent to write the data set, no immediate action is required. However, failure to resolve the SVC99 error (indicated by the reason code) may eventually cause the available space in the active log to be exhausted (DSNJ111E), which may cause all future off-loads to fail due to the same error.
730
If the problem occurred during allocation with the intent to read the data set, the problems are likely MVS dynamic allocation errors. Therefore, perform the following tasks: Determine the cause of the problem using the appropriate MVS system messages and codes, and correct those problems. Use the batch command DELETE_LOG to delete the archive log data set from the restart data set archive log inventory. Use the DEFINE_LOG function to add the data set back into the archive log inventory, pointing to the correct volume and device.
Physical Logger received a RC=nnnn reason code nnnnnnnn from DSPSERV(or HSPSERV) CREATE(or SREAD, DELETE or RELEASE) macro for LOG dsname The PowerExchange physical logger received an invalid return code from the specified internal macro for the service indicated. The reason code provides the reason why the macro processing failed or cannot continue. The task ends abnormally with a user abend code of U3035 and a reason code of X'F9FF00xx'. Identify the MVS data in the virtual (DIV) macro that is causing the problem, and correct it, if necessary. For more information about the reason code, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDML Physical Logger received a RC=rc, reason code=reason, from DIV macro macro for log ddname The PowerExchange physical logger received an invalid return code from the specified internal MVS data in virtual (DIV) macro for the service indicated. The reason code indicates why the DIV macro processing failed or cannot continue. The task ends abnormally with the user abend code of U3035 and reason code X'F9FF00xx'. Identify the MVS data in the virtual (DIV) macro that is causing the problem using the MVS system messages and codes. If necessary, correct the problem, and run the job again. For more information about the reason code, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. Write error, dsname=dsname, Rc=return code, Rsn=reason code The PowerExchange physical logger encountered a write error in the specified active log data set. The error occurred while the PowerExchange Logger was writing the log buffers to an active log data set. The return code and reason code provide error information returned by the HSPSERV or DIV services. The system action varies depending on the active logging option you selected:
User Response:
User Response:
If you selected the dual active logging option, the log manager switches to the next data set for this copy. If the next data set is not ready, the log manager temporarily enters single logging mode and allocates a replacement data set for the one that encounters the error. The PowerExchange Logger resumes dual logging as soon as possible. If you selected the single active logging option and the next data set is not ready, the log manager waits for that data set to become available. The PowerExchange Logger inhibits log writing until the replacement data set is ready to receive data. See the appropriate MVS publication for a description of the HSPSERV reason codes. Correct the log marked as STOPPED by deleting the log with the DELETE_LOG command and reallocating the log, and run the job again.
Note: A log is not usable if the status of the log is STOPPED.
731
EDML Physical Logger initialization failed for dsname=dsname, logrba=logrba The PowerExchange physical logger encountered an error during the initialization of the active log data set specified by dsname. The PowerExchange Logger truncates the current active log and attempts to switch to the next active log data set. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDML Physical Logger termination failed for dsname=dsname, logrba=logrba. The PowerExchange physical logger encountered an error during the termination of the active log data set specified by dsname. The PowerExchange Logger truncates the current active log. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDML Physical Logger initialization failed, unable to determine blocks available for logging The PowerExchange physical logger encountered an error when trying to determine the total blocks available for logging during this run. Processing ends abnormally with an abend code of U3035 and a reason code of X'00F9FF02'. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. For more information about the reason code, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDM Logger Offload handler will attempt to continue with active log copy The off-load handler was unable to allocate the active log copy1 data set. If dual active logging is in effect, the PowerExchange Logger off-load handler attempts to continue by switching to and using the second copy. If this attempt fails or if dual active logging is not in effect, the PowerExchange Logger ends the off-load process. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDM Logger Offload terminated for dsname=dsname, reason code=reason The PowerExchange Logger off-load handler was unable to archive active log data set, dsname. The reason code, reason, indicates the cause of the termination as follows.

User Response:
User Response:
User Response:
User Response:
01. The PowerExchange Logger was unable to allocate the active log data set. 02. The PowerExchange Logger was unable to identify the active log data set using the DIV IDENTIFY macro. 03. The PowerExchange Logger was unable to access the active log data set using the DIV ACCESS macro. 04. The PowerExchange Logger was unable to map the active log data set using the DIV MAP macro. 05. An I/O error occurred while the PowerExchange Logger was reading the active log data set. 06. An I/O error occurred while the PowerExchange Logger was writing to the active log data set. System Action: The PowerExchange Logger ends the off-load process.
732
User Response:
To determine the cause of the problem, view the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, contact Informatica Global Customer Support and provide the job step listing. EDM Log unallocation error dsname=dsname, error status=reason The PowerExchange physical logger encountered an error while attempting to allocate the active or archive log data set specified by dsname. This message displays the reason code returned by the MVS dynamic allocation (SVC99). If this message is coming from the offloading handler, the PowerExchange Logger ends the archive process. Use the appropriate MVS system messages and codes to determine the cause of the problem. Correct the cause of the allocation failure, and enter the command again. EDM Logger internal DEFINE_LOG command failed for DSNAME=dsname The PowerExchange Logger off-load processor encountered an error while attempting to update the PowerExchange Logger restart data set (ERDS) with the new archive data set information. The PowerExchange Logger ends the off-load process. If the error is coming from the off-loading handler, the PowerExchange Logger ends the archive process. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDM Logger log read error dsname=dsname, logrba=logrba, return code is rc The PowerExchange Logger off-load processor encountered an error while attempting to read the active log specified by dsname. The system action depends on when the error occurs: If the error occurs during the off-load process, the off-load processor tries to read the RBA range from a second copy.
User Response:
User Response:
If a second copy does not exist, the off-load processor stops the active log data set. If the second copy also has an error, the processor stops only the original data set that triggered the off-load. The archive log data set ends, which leaves a gap in the archived log RBA range. The PowerExchange Logger issues message PWXEDM172654E. If the second copy is satisfactory, the off-load processor does not stop the first copy. or
If the error occurs during restart, the PowerExchange Logger ends. During restart, all copies of the active log data set must be available to the PowerExchange Logger. If the active log data set has been stopped, it is no longer used for logging. However, the data set is not deallocated. The PowerExchange Logger continues to use it for reading.
or
User Response:
Check any system messages, such as IEC prefixed messages, and attempt to resolve the problem using the recommended actions given in those messages. Alternatively, you can write a program to archive as much of the stopped active log data set as possible. Then, run the change log inventory utility to notify the restart data set (ERDS) of the new archive log and log RBA range.
Note: When you receive this message, the data set may or may not be stopped. In either
case, you should replace an active log data set that gives persistent errors of this type. Warning! Repairing the stopped active log does not solve this problem because the off-load processor does not go back to unload the stopped log. You must perform the off-load process and reestablish a valid active log.
733
EOD reached at dsname=dsname, Logrba=logrba The PowerExchange Logger log read processor reached the end of the file at the specified logrba in the specified log data set name. Processing continues. No action is required. EDM Logger unable to process log truncation request for reason reason The PowerExchange Logger off-load processor encountered an error while attempting to truncate the current active log. While processing an ARCHIVE_LOG command, the PowerExchange Logger physical logger routine received an internal request to force-write the log buffer and to truncate and switch the active log to the next available active log data set. This is an internal error detected by the PowerExchange physical logger. The error may have been caused by an unrelated abend in the PowerExchange physical logger, a STOP MODE=FORCE command, or an abnormal subsystem termination. As indicated by reason code reason, the request failed for one of the following reasons:

04. The end of current active log operation failed. 08. The determine new active log operation failed.
The PowerExchange Logger stops processing the command. Look up the messages and abends that precede this message for possible causes of the error. If possible, correct the problem and run the job again. If the problem persists, collect all available information about the error and contact Informatica Global Customer Support. EDM Logger asynchronous log archive subtask initiated The PowerExchange Logger accepted the ARCHIVE_LOG command you submitted. The PowerExchange Logger started an asynchronous task to archive (off-load) the active log data set. The system truncates the current active log data set or sets, switches to the next available active log data set or sets, and initiates an asynchronous off-load task to archive the active log data set or sets. The term asynchronous indicates that control returns to the invoker as soon as the off-load task starts. Therefore, the PowerExchange Logger command processor accepts and processes any PowerExchange Logger commands while the off-load task is running. If you used the MODE(QUIESCE) option with the ARCHIVE_LOG command, the system displays message PWXEDM172658I.
User Response: PWXEDM172658I Explanation:
Follow normal operational procedures when the off-load task begins. EDM Logger ARCHIVE_LOG QUIESCE command ended. EDM Logger capture activity is now resumed The PowerExchange Logger processed an ARCHIVE_LOG command with the MODE QUIESCE option. As part of MODE QUIESCE processing, the PowerExchange Logger stops all new update activity against PowerExchange Logger resources. Normal PowerExchange Logger activity for all users and jobs was blocked during the quiesce period. This message signals the end of the quiesce processing and the resumption of normal PowerExchange Logger activity for all users and jobs. The PowerExchange Logger resumes normal logging activity for all users and jobs that were blocked during the quiesce period. No action is required.
User Response:
734
EDM Logger ARCHIVE_LOG command is already in progress You attempted to issue an ARCHIVE_LOG command while another ARCHIVE_LOG command was already in progress. The system continues processing the original ARCHIVE_LOG command and ignores the second command. No action is required. EDM Logger ARCHIVE_LOG command terminated. Current active log data set is the last available The PowerExchange Logger rejected the ARCHIVE_LOG command because the current active log is the last available active log data set. The PowerExchange Logger ends command processing. If you do not correct this situation, the PowerExchange Logger issues warning messages as the available log data space reaches critically low levels. When the active log becomes full, a final message indicates that there is no active log, and the PowerExchange Logger halts processing until you make active log space available. To clear this condition, take the steps necessary to complete other waiting off-load tasks. After you make another active log available (reusable) by completing the off-load process for that log, command processing for the current active log can proceed. EDM Logger ARCHIVE_LOG completed for dsname=dsname, startrba=startrba, endrba=endrba, starttime=starttime, endtime=endtime The PowerExchange Logger completed off-loading the archive log data set for the volume specified by dsname. The PowerExchange Logger creates an archive data set. It also updates the archive log data set inventory in the PowerExchange Logger restart data set (ERDS) with the information shown in this message, including start and end RBA. The system waits for an active log to be made available before it proceeds with command processing for the current active log. The starttime and endtime fields report the time range contained in the archive log data set that was created and these time values are recorded in the archive log data set inventory in the restart data set (ERDS).
User Response:
No action required. EDM Logger was unable to {ADD|DELETE|FIND} UOW uowid to internal table When the PowerExchange physical logger received a begin_UOW record for the unit of work (UOW) specified in uowid, it could not add, delete, or find that UOW in the internal table. The PowerExchange Logger ends. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDM Logger received sync record without a corresponding begin_UOW record for UOW uowid The PowerExchange physical logger received a begin_sync_PH1, begin_sync_PH2, or end_sync_PH2 record. However, a begin_UOW does not exist for this unit of work (UOW). The PowerExchange Logger requires a begin_UOW before it can recognize a begin_ or end_sync record. The PowerExchange Logger ignores this UOW record and continues processing. Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support.
User Response:
User Response:
735
Logger logger_operation operation for queue queue_name failed for entry entry_value with return code=return_code, reason code=rsn_code The Logger was performing an operation on an internal table, when it detected that the operation had not completed. The operation that was being performed, the name of the internal table, which is the queue name, the entry that was being processed, and the return code and reason code that resulted, are all included in the text of the message. logger_operation is one of the following values:

ADD DELETE FIND queue_name is GBLCHKQCB. User Response: Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. The Logger ends abnormally. EDML Physical Reader operation failed for dsname=dsname, logrba=logrba The PowerExchange physical reader encountered an error during the operation shown in this message for the archive data set dsname. The possible operations include
System Action: PWXEDM172665E Explanation:
Initialization Termination Get buffer Unallocation The PowerExchange Logger ends the current archive extraction process. User Response: Check the JES2 log for previous messages from the PowerExchange physical logger to help determine the cause of the problem. If the problem persists, get the job step listing, and contact Informatica Global Customer Support. EDM Logger has determined that XCF is operating in local mode only The PowerExchange Logger Cross-System Coupling Facility (XCF) interface determined that the XCF is operating in local mode only. Local mode limits signaling and communications to this CPU. Processing continues. No action is required.
736
EDM Logger Reader operation failed for lrp_client with reason code reason, and return code rc The specified PowerExchange Logger reader operation operation failed for LRP client lrp_client. The reason code reason and the return code rc provide additional information about the error. The variable operation indicates which operation was running and is one of the following:

BLDPIP. A build SENDPIPE command failed. BLDRDT. An attempt to build a request data transfer (REQTRN) reply command failed. CLOSE. An attempt to close a circular queue failed. CSCONN. A common services CONNECT failed. INVRBA. The logger reader was unable to find a valid log data set, or it found a log data set with an invalid RBA. OPEN. An attempt to open an output circular queue failed. OPNXCF. An attempt to open a XCF message queue failed. PUT. An attempt to PUT to a circular queue failed. RDINIT. The logical log reader was unable to initialize. RDTERM. An attempt to terminate processing by the logical log reader failed. RDTRPL. An attempt to send a request data transfer command (REQTRN) reply through the circular queue failed. READ. An attempt by the logical log reader to READ from a log failed. REREAD. An attempt by the logical log reader to READ from a log failed. SNDPIP. An attempt to insert a pipe cleaner in a circular queue failed. SNDRDT. An attempt to send a request data transfer (REQTRN) reply command failed. TERM. A logical log reader failed to terminate. UNALLO. An attempt to have the logical log reader unallocate the current log data set failed. UOWFND. The exact position in the log data from which data transfer is supposed to start cannot be found. System Action: User Response: The PowerExchange Logger stops abnormally. To determine the cause of the problem, look at the values of operation, reason, and rc. The return and reason codes are documented in Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. If the return code value is 0008, then the reason code is documented in Reason Codes 001 to 255: PowerExchange Agent on page 918. Correct the problem, restart the PowerExchange Logger, and run the job again. If the problem persists, collect all available information about the error, including the contents of this message, and contact Informatica Global Customer Support. PWXEDM172668I Explanation: {Change Capture|Log Reader} agent xcf_member_name connected to Logger logger_id, reason code=reason, return code=rc The Logger Cross-System Coupling Facility (XCF) interface received and processed a connection request from xcf_member_name for Logger logger_id. The connector is either an environmental change capture routine (ECCR), indicated by Change capture, or a log reader. Processing continues. No action is required. For more information about the return and reason codes, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923.
737
job {Change Capture|Log Reader} agent disconnected from EDM Logger loggerid, reason code=reason, return code=rc The PowerExchange Logger Cross-System Coupling Facility (XCF) interface received and processed a disconnection request from the subsystem (agent) job. The module that disconnected from the PowerExchange Logger is either an environmental change capture routine (ECCR), shown in the message as Change Capture, or the log read processor (LRP), shown in the message as Log Reader. Processing continues. No action is required. For more information about the return and reason codes, see Reason Codes 00000601 to 00004499: Command on page 921 and Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDM Logger Client job started The PowerExchange Logger Cross-System Coupling Facility (XCF) interface received and processed a join request from the job, specified by job, to the PowerExchange Logger XCF group. Processing continues. No action is required. EDM Logger Client job_name {ended successfully|end data transfer|ended abnormally} The Logger Cross-System Coupling Facility (XCF) interface received and processed an end or end data transfer request from the job, job_name, for the PowerExchange Logger XCF group. Processing continues. If the job ended or ended data transfer, no action is required. If the job ended abnormally, check the JES2 log for previous messages from the PowerExchange Logger. Correct the problem and resubmit the job. Contact Informatica Global Customer Support.
EDM Logger last active log data set is nn percent full The PowerExchange Logger issues this message when the last available active log data set is 75 percent full. The PowerExchange Logger reissues this message after each additional five percent of the remaining data set space is filled. Several possible causes exist for the shortage of active log data set space:
Excessive logging, such as too many users requesting logs at the same time. Delayed or slow off-loading, caused by such things as the system operator failing to mount archive volumes, making incorrect replies to off-load process messages, or using devices with slow device speeds. Excessive use of the ARCHIVE_LOG command. Each time the ARCHIVE_LOG command is used, it causes the PowerExchange Logger to switch to a new active log data set and to initiate an off-load of the previous active log. Although the ARCHIVE_LOG command is not run when only one active log data set remains in a copy of the active log, excessive use of the command could have consumed all space in the active log except for the current active log data set or sets. Off-load process failure. See additional information in the user response. Insufficient active log space. See the additional information in the user response.
738
System Action:
Each time it issues this message, the PowerExchange Logger tries to perform off-load processing. If the off-load process is successful, the PowerExchange Logger does not reissue this message. If the off-load process is unsuccessful and if the cause of the failure is not corrected, the active log data space fills until it reaches capacity. The PowerExchange Logger then issues message PWXEDM172673I and halts all processing of changed data. To clear this condition, you must either correct the problem that is causing the off-load process to fail, or you must add more active log data sets:
User Response:
To correct the off-load failure condition, you must take the steps necessary to complete other waiting off-load tasks. When an active log data set is made available or reusable by completing the off-load process for it, PowerExchange logging activity can continue. Perform a display request to determine the outstanding requests related to the log off-load process. Take the necessary action to satisfy any requests, and permit the off-load process to continue. If the off-load process fails to complete normally or cannot be initiated, notify the system programmer. To add more data sets, you must stop the logging process, terminate the PowerExchange Logger, run the logger batch change utility to add new active log data sets, then restart the PowerExchange Logger. PWXEDM172673I Explanation: System Action: User Response: EDM Logger out of space in active log data sets Due to delays in off-load processing, all space in all active log data sets has been used. The PowerExchange Logger cannot continue processing. The log manager waits for an available data set. Use a DISPLAY OBJECT=LOG command to verify that there are no outstanding requests related to the log off-load process. Take the necessary action to satisfy any requests and permit the off-load process to continue. If the delay was caused by the lack of a resource required for the off-load process, you must make the resource available to allow the off-load process to complete. When the resource is available, it permits the PowerExchange Logger to resume processing. For information about the DISPLAY command, see the PowerExchange Command Reference. EDM Logger {simple|extended} checkpoint complete, Startrba=startrba, Endrba=endrba at yyyy.ddd hh:mm:ss.nn Start time=timestamp The Logger completed either a simple or an extended internal checkpoint that was created on yyyy.ddd at hh:mm:ss.nn. The checkpoint records are written to the active log data set between the designated start and end RBA addresses. The value for the start time timestamp is the TOD clock time stamp (GMT) when the checkpoint record was created. This message provides a record of where the PowerExchange Logger is currently logging data. In a Post-Log Merge environment, this will be the effective RBA of the first checkpoint record that is created. In a Post-Log Merge environment, the time stamp is needed to provide the same running record of where the PowerExchange Logger is currently logging data. System Action: User Response: PWXEDM172676I Explanation: Processing continues. No action is required. EDM Logger Change Capture XCF-Syncpoint request for uowid complete at date time The PowerExchange Logger completed a sync point request sent through the Cross-System Coupling Facility (XCF) for an environmental change capture routine (ECCR) unit-of-work ID. Processing continues. No action is required.
739
EDM Logger Change Capture XCF-Syncpoint request for job failed (failure) at date time The PowerExchange Logger was unable to process a sync point request sent through the Cross-System Coupling Facility (XCF) for an environmental change capture routine (ECCR). The following types of failure occur in the internal communication between the ECCR and the logger.

Invalid input Invalid resync
Processing continues. To correct the problem, contact Informatica Global Customer Support. EDM Logger loggerid detected nnnn in-doubt units of work during restart This message is sent to the JES console when the PowerExchange Logger detects any units of work (UOWs) that are in-doubt during restart. The message shows the number of in-doubt units of work (nnnn) found for the specified PowerExchange Logger. Processing continues. See the PowerExchange CDC Guide for z/OS for information about resolving in-doubt units of work. EDP Logger report_title report follows: The DISPLAY OBJECT=LOG and DISPLAY OBJECT=CONNECTION commands issue this message to show the title of the report they generate as output. This message precedes the other messages this command generates. The value report_title can be any of the following titles:
Display Log All Display Log Active Display Log Archive Display Connection UOW Display Connection Readers Display Connection Writers Logger RBA=logger_rba, Read RBA=read_rba, Start location=start_loc This is part of the reader connection report. It appears as an unnumbered message line within message PWXEDM172679I when it is reporting on Reader Connections that currently exist. It shows where the PowerExchange Logger is currently writing (logger_rba), where the log read last processed (Read_rba) and where the request for reading started (start_loc). The RBAs that are reported are the address of the beginning of the block of Logger data and do not reflect the record currently being processed within that block. The start location is expressed in the form of a time stamp in TOD clock format. This message is only included in the reader connection report when the PowerExchange Logger is operating in a Post-Log Merge environment. System Action: User Response: PWXEDM172680I Explanation: System Action: User Response: Processing continues. No action is required. EDM Logger command normal completion at date time Processing completed for the specified command. Processing continues. No action is required.
740
EDM Logger RESOLVE_INDOUBT {COMMIT|ABORT} request for uowid failed {find UOW|build packet} at date time The PowerExchange Logger failed to process a RESOLVE_INDOUBT COMMIT or ABORT request entered by an immediate command. Either the PowerExchange Logger failed to find the specified unit of work, or the PowerExchange Logger could not build the packet. Processing continues. If the failure occurred in finding the unit of work, verify that the unit of work ID specified in the RESOLVE_INDOUBT command matches the unit of work ID shown in the DISPLAY OBJ=CONN,TYPE=UOW command. Run again. If the problem persists, contact Informatica Global Customer Support.
System Action:
User Response:
If the failure occurred when building the packet, contact Informatica Global Customer Support. Logger RESOLVE_INDOUBT {ABORT|COMMIT} done for uowid at scheduled date/time The PowerExchange Logger is processing a RESOLVE_INDOUBT request for the specified unit of work (UOW). The request was entered by a command that specified the UOW should be processed now. The message shows the scheduled date and time, which should approximate the present date and time. Processing continues. No action is required. EDM Logger unable to connect to EDM Common Services, Return code=rc, Reason code=reason The PowerExchange Logger was unable to connect to the PowerExchange Agent during initialization. The return and reason codes provide additional information about the error. The PowerExchange Logger ends abnormally. Verify that the PowerExchange Agent and the common services module are operational, and run the job again. For more information about the return and reason codes, see Return Codes on page 915 and Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDM Logger {simple|extended} checkpoint complete for UOW uowid at date time The PowerExchange Logger completed the specified simple or extended internal checkpoint for the specified unit of work (UOW) at the specified date and time. Processing continues. No action is required. EDM Logger loggerid unable to shut down. {Change Capture|EDM Log Reader} client name still active You entered the PowerExchange Logger STOP command with the parameter MODE=QUIESCE. This message indicates that the specified environmental change capture routine (ECCR) or PowerExchange log reader is still active. The PowerExchange Logger waits for the specified ECCR or log reader to disconnect. No action is required.
User Response:
User Response:
741
EDM Logger loggerid is already active in the system The PowerExchange Logger attempted to create a new Cross-System Coupling Facility (XCF) member for the associated PowerExchange Agent. However, an XCF group with the same name is already in the system. The PowerExchange Logger ends. Verify that the PowerExchange Logger ID is correct in the JCL parameter, and run the job again. EDM Logger command command {failed|completed} with return code=rc, and reason code=reason The specified command completed or failed with the specified return and reason codes. This message displays for the following commands:

User Response:
ARCHIVE_LOG DEFINE DEFINE_LOG DEL_LOG DISPLAY END PRINT RESOLVE_INDOUBT STOP TRACE If the return and reason codes are 0, processing continues. Otherwise, although logger processing continues, the specific command processing ends. If the return and reason codes are 0, no user action is required. Otherwise, check the JES2 log for previous messages from the PowerExchange Logger for pertaining to the specified command. User Response: If this message is a result of an ARCHIVE_LOG command, you must correct the problem that is preventing the PowerExchange Logger from performing the archiving process normally. This may be due to such things as space availability or catalog problems. When the problem is corrected, other waiting off-load tasks have completed, and another active log is available, reissue the ARCHIVE_LOG command for the current active log. If you do not correct the error, the PowerExchange Logger will issue warning messages as available active log data space reaches critically low levels. A final message indicates that there is no active log and the PowerExchange Logger stops processing until active log space is made available. EDM Logger loggerid detected Client clientid in invalid state state. The PowerExchange Logger shown in the message attempted to send a message to the specified client by XCF, but the client was in an invalid state. For example, if an ECCR job abends, the PowerExchange Logger detects a FAILED state. Processing continues. Determine why the client is in an invalid state by checking the JES2 log messages for the specified client. Correct the cause for the invalid XCF state of the client and run the job again. EDM Logger LOG_FILE command loaded UOW uowid at date time The PowerExchange Logger completed a request from a LOG_FILE command to load the unit of work identified by uowid. The message also shows the date and time when the UOW was loaded. Processing continues.
System Action:
742
No action is required. EDM Logger logic error. Invalid Logrba=logrba, for log with Startrba=startrba, Endrba=endrba The PowerExchange Logger physical logger received a request to write a block with a logrba outside the boundaries of the current active log. This message provides the requested logrba and the startrba and endrba for the current active log. The PowerExchange Logger abends with an abend code of U3035 and reason code X'0F9FF020'. Contact Informatica Global Customer Support. For more information about the reason code, see Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. EDM Logger has found an error in log active_log. Log stopped. The PowerExchange Logger physical logger found an error while setting up the specified active_log. The PowerExchange Logger stops both the primary and corresponding secondary logs. The PowerExchange Logger does not use them during the current run. Look for system messages, such as IEC prefixed messages, and use the information in those messages to determine the cause of the problem, correct the problem, and run the job again. In addition, you may need to recover the log by using the DELETE_LOG and DEFINE_LOG commands. EDM Logger detected an unequal number of primary and secondary logs defined in ERDS. The PowerExchange Logger physical logger found a usable secondary log during the switch log process after running in a single logging operation. Processing continues. No action is required. EDM Logger detected an insufficient number of active logs defined in ERDS. Not enough active log data sets are defined in the restart data set (ERDS) to start logging captured data. This condition usually exists for one of the following reasons: You have defined fewer than two data sets for one of the active log copy sets. EDMUPARM specified ACTIVE_LOG_MODE=DUAL in the PowerExchange Logger initialization parameters. However, data sets for two copies of the active log are not defined in the restart data set. Fewer than two data sets are available (not flagged as STOPPED) for one of the active log copy sets. The PowerExchange Logger start-up ends. Use the logger batch change utility to make the number of active log data sets defined in the restart data set consistent with the parameters specified in EDMUPARM. The PowerExchange Logger does not reuse log data sets that have the status STOPPED. You must recover these data sets, by either redefining or recovering them from the other copy of the log. In addition to clear the STOPPED status, you must delete the log data sets and add them to the restart data set with the appropriate RBA addresses. To delete and add the log data sets to the restart data sets, use the logger batch change utility. After correcting the problem, restart the PowerExchange Logger.
User Response:
User Response:
PWXEDM172692E Explanation: System Action: User Response: PWXEDM172693E Explanation: Explanation: Explanation:
Explanation:
743
EDM Logger detected an invalid record on input Queue. Record ignored. The PowerExchange Logger detected an invalid record type on the input queue while processing changed records. A valid record must have one of the following indicators in position 24 of the record to be logged:

C. Change data record. P. Packet header or trailer record. R. Row column description record. S. Service record. U. Batch/utility record. L. Logger record. If any other indicator appears in position 24, the PowerExchange Logger considers the record invalid. The PowerExchange Logger ignores the invalid record. System Action: User Response: PWXEDM172696E Explanation: System Action: User Response: Processing continues. No action is required. EDM Logger could not find checkpoint with Logrba=logrba in any log data set The PowerExchange Logger could not locate a checkpoint at the address specified by logrba in any known data set. The logger requires a checkpoint for restart processing. Processing ends. Determine a valid checkpoint for restart, and start the logger again. If you need assistance in determining a checkpoint, contact Informatica Global Customer Support. EDM Logger operation operation for XCF Message Q failed with reason code=reason, and return code=rc The PowerExchange Logger failed when it tried to perform the specified operation for the XCF local circular queue. The XCF circular queue may have an internal error. The return and reason codes provide additional information about the error. Processing ends. Gather all available information about the error and contact Informatica Global Customer Support. For more information about the return and reason codes, see Return Codes on page 915 and Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger on page 923. Logger received an invalid request data transfer start: loggerid startrba, from log reader log_reader_name The Logger, loggerid, XCF interface received an invalid start RBA, startrba, from the log reader, log_reader_name. Processing continues. The Logger requests an abend for the log reader shown in the message. Check the EDMPARMS DD statement or STEPLIB concatenation for the EDMSDIR module and verify that the correct Logger name is specified. Correct the job and run it again. EDP Logger reinstated ECCR= job_name, oldest RBA= oldest_RBA, last read RBA= last_RBA, last Logger UOW= last_UOW The PowerExchange Logger encountered a type-1 ECCR with the indicated relative byte address (RBA), during the restart process. The PowerExchange Logger reinstated the specified ECCR in internal control blocks. The PowerExchange Logger processing continues.
System Action:
744
No action is required. EDM Logger unable to find options for loggerid, default options in effect The PowerExchange Logger initialization processor was unable to locate the options data set (EDMUPARM) for the logger ID specified in the message. The logger will use the default options found in EDMZPARM. Processing continues. No action is required. EDM Logger executing with control_block at logrba The PowerExchange Logger is executing with the indicated control block at the location indicated in the message. Processing continues. No action is required.
PWXEDM172702W EDM Logger stealing log=log.dataset.name, Startrba=rrrrrrrrrrrr, nnnnnnnn Log Readers active Explanation: The PowerExchange Logger needs to reuse an active log with the data set name and starting RBA indicated in the message, because no other active logs are available to it. However, one or more Log Reader processes are currently reading the active log. The number of Log Reader processes is shown in the message. The PowerExchange Logger begins to write new data to the active log data set. This may result in an abend in the Log Reader process. Determine why the PowerExchange Logger was forced to steal the active log data set. It may possibly be necessary to increase the number of active log data sets, especially if more Log Reader processes are normally run than there are active log data sets. You can use the PowerExchange Logger DISPLAY command to determine the number of Log Reader processes currently active. This problem may also be caused by a failure to archive active log data, so the status of any recent archive attempts should be examined. You can also use the PowerExchange Logger DISPLAY command to determine the status of the active log data sets, in particular, which, if any, need to be archived. EDM Logger is now operating in single logging mode on ds_type The PowerExchange Logger encountered an allocation or I/O error in the restart data set or in an active log data set. Processing continues. The PowerExchange Logger enters single logging mode for the data set type indicated by ds_type. No action is required. However, you should review the JES log and the PowerExchange message log to resolve the error in the data set indicated by the message. EDM Logger command processor found that required keyword keyword is missing You entered a command without a required keyword. The current command set ends. Enter the command set with the required keyword, and run the job again. EDM Logger command processor detected keyword~=~?, which is not supported in batch In ISPF, you can use a question mark (?) in place of keywords to indicate that ISPF should prompt for the value of the keyword at execution time for that keyword. This option is not allowed when running in batch mode. The PowerExchange Logger ends processing of the current command set.
PWXEDM172711E Explanation: User Response: PWXEDM172712E Explanation:
745
Correct this command set, and submit it again. EDM Logger command processor detected a non-alphanumeric value for keyword The keyword you entered contains invalid characters. The value for the specified keyword must consist of all alphanumeric characters and must begin with a non-numeric character. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected keyword keyword=value and keyword=value that are mutually exclusive You cannot use both of the specified keywords or keyword values in a single command set. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected a value length error for keyword, found value The value for the specified keyword must not exceed a maximum length. The value you entered was too long for the format. For example, a time stamp must not exceed 13 bytes, and a data set name must not exceed 44 bytes. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. error_description for keyword_name - found value_found The indicated value of the keyword_name, ERROR DESCRIPTION, KEYWORD NAME, or VALUE FOUND, must conform to a special format, such as, data set name, time stamp. The value entered was not acceptable. The current command set is terminated. Correct the command and resubmit. If necessary, read the keyword description in the manual to insure that the data format is acceptable. Time stamp value must be specified as YYDDD/HHMMSST where YYDDD is a valid Julian date and HHMMSST is a valid time. Using tenths of seconds is optional. DRRN values must begin with 04 or 08. An IMS log code value must be in the range AO to FF. EDM Logger command processor was expecting a keyword, found value The PowerExchange Logger command processor was expecting a keyword, but found another value, such as the next characters in the input stream, instead. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected keyword keyword value delimiter incorrect The keyword value for the specified keyword was followed by an equal (=) sign, as in KEY=XXXX=. This command structure is incorrect. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected duplicate value value for keyword keyword The indicated value appears twice in the list for the specified keyword. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again.
User Response: PWXEDM172714E Explanation: User Response: PWXEDM172715E Explanation:
User Response:
User Response: PWXEDM172719E Explanation: User Response:
746
PWXEDM172720E Explanation: User Response: PWXEDM172721E Explanation:
EDM Logger command processor detected keyword keyword expecting value, found value_entered The value you entered is not valid for this keyword. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected a length error, part_of_name The scan found a name or an undelimited value that is too long. This message shows the first part of the invalid name. The syntax scan does not accept any name or undelimited value longer than 64 characters. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor expects a numeric value for keyword, found value The PowerExchange Logger command processor found the specified non-numeric value for the specified keyword that requires a numeric value. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. VALUE TOO LONG FOR keyword The value you entered is too long for this keyword. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again EDM Logger command processor was expecting a value for keyword, found end of input or delimiter You entered a keyword with no value, such as KEY=. You cannot use the specified keyword with a null value. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected a missing string delimiter for keyword The PowerExchange Logger did not find an expected string delimiter for the specified command. To specify strings, use the X'00' or C'AA' format, where the characters after the X or C may be any character except a blank or semicolon. The PowerExchange Logger ends processing of the current command set. Correct this command, and submit it again. EDM Logger command processor detected a string delimiter missing or invalid for keyword The PowerExchange Logger did not find a string delimiter either at the end of the previous line or the beginning of the current line. When you continue a string across multiple lines, you must enter a string delimiter as the first non-blank character on each continuation line. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected a null string for keyword The PowerExchange Logger found a null string, such as C' ' or X' ', for the specified keyword. This command does not allow null strings for this keyword. The PowerExchange Logger ends processing of the current command set.
User Response: PWXEDM172723E Explanation: User Response: PWXEDM172725E Explanation: User Response: PWXEDM172726E Explanation:
747
Correct this command, and submit it again. EDM Logger command processor detected invalid hexadecimal digits for keyword The PowerExchange Logger found characters other than 0123456789ABCDEF in a hexadecimal string. For example, X'12G4' is invalid. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected an odd number of hexadecimal digits for keyword The PowerExchange Logger found an odd number of characters between the delimiters of a hexadecimal string. For example, X'123' is invalid. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor found that string starting character is invalid for keyword, must start with quote, C, or X Some PowerExchange Logger keywords accept only delimited values. You can specify a delimited value using any of the following formats. The specified string did not conform to any of these formats.

Enclose the value in single or double quotes, as in the following example: Specify a C, followed by the beginning delimiter, which is any special character including quotes, followed by the value, followed by the ending delimiter.For example: Specify an X, followed by the beginning delimiter, which is any special character including quotes, followed by the value expressed in hexadecimal, followed by the ending delimiter. The following is a valid example:
KEYWORD='VALUE'
KEYWORD=C/VALUE/
KEYWORD=X'E5C1D3E4C5'
System Action: User Response: PWXEDM172732E Explanation: System Action: User Response: PWXEDM172733E Explanation: System Action: User Response: PWXEDM172734E Explanation: System Action:
The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected a value for keyword that is too long The PowerExchange Logger found that the value entered for the specified keyword was longer than the maximum length allowed. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor detected a duplicate keyword keyword The PowerExchange Logger found the same keyword twice in the command being processed. Duplicate keywords in a command are not allowed. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor was expecting a comma, found characters The PowerExchange Logger expected to find a comma between the values for a keyword. Instead, it found the characters shown in this message. The PowerExchange Logger ends processing of the current command set.
748
Correct this command set, and submit it again. EDM Logger command processor was expecting a subcommand, found characters followed by = The PowerExchange Logger expected to find a subcommand. Instead, it found the specified characters, which are the next characters in the input stream, followed by an equal sign. These characters do not specify a subcommand. Possible reasons for this are:

A comma missing between two keywords A level 2 command followed by an equal sign A misspelled subcommand System Action: User Response: PWXEDM172736E Explanation: System Action: User Response: PWXEDM172737E Explanation: System Action: User Response: PWXEDM172738E Explanation: System Action: User Response: PWXEDM172739I Explanation: Explanation: User Response: PWXEDM172740E Explanation: The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. ABBREVIATION abbreviation IS AMBIGUOUS A command, keyword, or value name abbreviation is too short. More than one keyword or command name begins with the specified characters. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger keyword keyword value must be between low_value AND high_value The PowerExchange Logger found a keyword value, which must be a number, outside the acceptable range. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger subcommand subcommand may only be used once in this command set The PowerExchange Logger found the specified subcommand more than once in the command set. You can enter this subcommand only once in a single command set. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. FORMATTING OF THE LOG DATASET IS COMPLETE The PowerExchange Logger utility has completed the pre-formatting of the log data set. Processing continues. No action is required. EDM Logger command processor was expecting a command, found characters The PowerExchange Logger expected to find a command. Instead, it found one of the following:
A word that is not a command The END command The end of the input file Other invalid characters System Action: User Response: The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again.
749
EDM Logger command processor was expecting a subcommand, found characters The PowerExchange Logger expected to find a subcommand. Instead, it found either a word that is not a command or invalid characters. A KEYWORD=VALUE parameter must be followed by either a comma and another keyword, the END command, or a subcommand. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. EDM Logger command processor was expecting a command, found command followed by = The PowerExchange Logger expected to find a command. Instead, it found either a keyword or a command name, followed by an equal sign. Neither is valid. The PowerExchange Logger ends processing of the current command set. Correct this command set, and submit it again. Invalid state reason for EDMLCP00 The PowerExchange Logger received an invalid reason code from the command parsing routine. The PowerExchange Logger ends processing of the current command set. Contact Informatica Global Customer Support. keyword1=value1 is required when keyword2=value2 is used The PowerExchange Logger did not find the first keyword and value, which are required when the command set includes the second keyword and value that are displayed in this message. The PowerExchange Logger ends processing of the current command set. Enter the command set with the required first keyword, or eliminate the second keyword. Command structure is not compatible with {required|excluded|assumed} keyword The PowerExchange Logger found a required, excluded, or assumed keyword or value that is not valid for the command structure. This error indicates an internal logic error in the command structure. The PowerExchange Logger ends processing of the current command set. Contact Informatica Global Customer Support. The subcommand subcommand and keyword keyword=value are mutually exclusive The PowerExchange Logger found a keyword or keyword=value that you cannot use with the specified subcommand. The PowerExchange Logger ends processing of the current command set. Correct this command, and submit it again. The subcommand subcommand is required when keyword=value is used The PowerExchange Logger did not find the specified subcommand. This subcommand is required when you use the specified keyword or keyword and value. The PowerExchange Logger ends processing of the current command set. Enter the command set either with the required subcommand or without the specified keyword.
System Action: User Response: PWXEDM172742E Explanation: System Action: User Response: PWXEDM172743E Explanation: System Action: User Response: PWXEDM172744E Explanation:
System Action: User Response: PWXEDM172746E Explanation: System Action: User Response: PWXEDM172747E Explanation: System Action: User Response:
750
Threshold% value for phase_name higher than threshold% value for phase_name Threshold values must be in order by phase. The monitor phase threshold must be less than or equal to the protect phase threshold which must be less than or equal to the overflow phase threshold. The PowerExchange Logger ends processing of the current command set. Correct the command set and resubmit. Reset% value greater than threshold% value for subcommand-name You specified a Reset% keyword value that was greater than the Threshold% value. This is not allowed. The PowerExchange Logger ends processing of the current command set. Correct the command and resubmit. FORMAT UTILITY HAS ABORTED DUE TO ERROR IN RTN: routine RSN: reason_code RC: return_code
System Action: User Response: PWXEDM172769E Explanation: System Action: User Response: PWXEDM172770E Explanation:
The format utility (EDMLUTL0) for the PowerExchange Logger active log data sets has abended due to an error that occurred while formatting the data set. The routine in which the error occurred, and the hexadecimal value of the return code and reason code for the operation that failed, are included in the text of the message. The value for the routine could be one of: Operation
GETM-PGE GETMAIN GENCB GENCB (ACB) SHOW-OPNSHOWCB FIELDS=(ERROR) OPEN OPEN (ACB) SHOWCB SHOWCB FIELDS=(XENDRBA,XHALCRBA) SHOW-CLO SHOWCB FIELDS=(ERROR) CLOSE CLOSE (ACB) DSPSERV DSPSERV CREATE DIV-IDNT DIV IDENTIFY DIV-ACC DIV ACCESS DIV-MAP DIV MAP HSPSERV HSPSERV SWRITE DIV-SAV DIV SAVE
The utility is terminated. Determine the cause of the failure from the return code and reason code that were issued for the failing operation, by consulting the appropriate IBM product documentation. If the problem cannot be identified, collect the output from the failing job, and contact Informatica Corporation Product Support. EDM Task task_name has encountered an error_type error with return code=rc, reason code=reason The PowerExchange Logger detected an unexpected condition with an unknown resolution. The PowerExchange Logger ends. Contact Informatica Global Customer Support.
751
PWXEDM172772W EDM Logger logger_name is on the last active log, check EDMMSG for more information Explanation: The PowerExchange Logger processed its last active log, and has no more selectable logs left to process. Possible reasons for this include:

A lack of archive space The capture process is occurring at a faster pace than the archival process
The PowerExchange Logger continues processing. Verify if the capture process is occurring at a faster pace than the archival process, then increase the number of active logs. DB2 Cur/RBA = current_RBA Oldest/RBA = oldest_RBA This message is issued each time the DB2 ECCR connects or disconnects. It shows the DB2 relative byte address (RBA) that the ECCR is currently processing, and the oldest UOW if one is in progress. The DB2 ECCR continues processing. No action is required. However, you may need this information if you use a STARTLOC command. Event Mark generated by ECCR eccrname for:
DB2 QUIESCE of TABLESPACE tablespace_name at DB2 RBA/LRSN {db2_rba|db2_lrsn} -orFinished with Plog copy plog_dsn, last time date time EDP Logger RBA . . . . . . . . . : loggerRBA Sequence number . . . . . . . . . : seqNum Edition number . . . . . . . . . : editionNum Source EDMNAME(s) . . . . . . . . : source_tagname
PWXEDM172774I
Explanation:
The PowerExchange Logger issues this message listing the contents of the event marker. The following events cause this message to be issued:
The DB2 ECCR sees a table space QUIESCE and sends an event marker to the PowerExchange Logger. The variables db2_rba and db2_lrsn represent the point in the DB2 log at which the QUIESCE is seen. If the DB2 logs are for a DB2 data-sharing system, then the value is a LRSN. Otherwise, the value is a RBA. The Adabas ECCR finishes processing a PLOG. The variables date and time represent the date and time at which the Adabas ECCR finished processing the PLOG. System Action: User Response: No action is required. You can use the EDP Logger RBA and Sequence number values to construct a restart point for change data capture extraction processes. For more information on providing restart points for extraction processes, see the PowerExchange CDC Guide for z/OS. EDM Logger received record_type record with no Begin_UOW from ECCR eccr_name for UOW uowID, SEQ= seq_no PowerExchange issues this error message each time it encounters a record from an ECCR where the ECCR had not provided the corresponding begin UOW record. Record_type indicates the type of record and can have one of the following values:

BEGIN_PH1. begin-phase-1 record. BEGIN_PH2. begin-phase-2 record. END_PH2. end-phase-2 record. CHANGE. change record. eccr_name indicates the name of the ECCR. uowID indicates the UOW ID of the UOW that was assigned by the ECCR. seq_no indicates the ECCR-assigned sequence number for the record.
This message is issued as a WTO, and the message also appears in the EDMSLOG file of the PowerExchange Agent. User Response: Check the JES2 log for previous messages from the logger. Also examine the ECCR that provided the data for any previous messages. If you cannot determine the problem from previous messages, contact Informatica Global Customer Support and have the job step listings available.
PWXEDM172778W EDM Logger discarding duplicate Begin UOW from ECCR eccrname for UOW uowsequencenumber Explanation: PowerExchange Logger received a begin_UOW record for which it already received the begin_UOW: a duplicate begin_UOW. The text of the message includes the UOWid assigned by the ECCR, as well as the name of the ECCR that supplied the record. This can occur on restart of any type 1 ECCR, the DB2 ECCR is the only type 1 ECCR, if the previous instance of the ECCR was not shutdown using the QUIESCE command. The following actions occur: 1. Warning message identified as PWXEDM172778W issued. 2. The PowerExchange Logger ignores this record and processing continues. User Response: Perform the following actions: 1. Check the JES2 log for previous messages from the EDML Logger. Also examine the ECCR that provided the data for any previous messages. 2. Have the job step listings available if contacting Product Support. PWXEDM172779W EDM Logger retrying HSPSERV SREAD of block at RBA rrrrrrrrrrrr, found RBA ffffffffffff Explanation: For each Log Reader Process (LRP) task that connects to the PowerExchange Logger, there is an associated Log Reader subtask in the PowerExchange Logger that reads the active and archive log data and passes it to the LRP task. Occasionally, after a Logger switches active log data sets, a user abend U3035 occurs in a Log Reader subtask that is reading data from the new active log data set. The abend can either be with reason code 0033FF05, or with reason code 00D6FF14, if fix 300074 is installed. An abend0C4 after label READ1065 in EDMLLRD0 can also occur. The reason for these abends is that an HSPSERV SREAD operation has returned a page containing all zeros, for a page that had previously been read. This is a problem that is described in IBM APAR OW56713. Because there is no fix currently available for APAR OW56713, logic was added to detect the condition, and to retry the HSPSERV SREAD operation, up to 100 times. Each time the retry is required, message 172779 is issued. The found RBA value ffffffffffff will most likely be zero. If the condition persists after 100 retries have been done, the Log Reader subtask of the PowerExchange Logger will abend with user abend U3035 and reason code 00D6FF14. This will cause the PAC jobs containing the associated LRP tasks to terminate. However, the PowerExchange Logger address space will NOT terminate, and the PowerExchange Logger will continue writing data to the active log that it receives from ECCRs. Restart any terminated PAC jobs. Wrong RBA found in log record in DSN=archive.log.dataset.name. Expected RBA eeeeeeeeeeee, found RBA ffffffffffff The EDM Logger was processing data in an archive log data set, but encountered a log record whose internally-recorded RBA was not the value that was expected. Because each log record has a constant amount of data, 4 KB, the RBA recorded in each record should increase by a constant value of X'1000'. The archive log data set in which this condition was found, the RBA that was expected to be found, and the RBA value that was actually found, are all included in the message. This is most likely the result of an I/O error in reading or writing the archive log data set.
System Action:
System Action:
753
System Action:
The following actions occur: 1. Error message identified as PWXEDM172780E issued. 2. The Logger task that encountered this error ends. If this was a task that was reading log data for a log reader process, this will cause the associated log reader process to terminate as well. If this occurs during initialization of the PowerExchange Logger, the PowerExchange Logger address space will terminate.
User Response:
Examine the status of the log data set that had the error. Try reading the data set yourself to see if the error is permanent or temporary. If the error seems permanent, you may need to use the corresponding secondary log data set to recreate the failing primary log data set. You can then restart the log reader process that failed, or the PowerExchange Logger itself, if the failure occurred during Logger initialization. If you cannot correct the problem, contact Informatica Corporation Product Support. Missing data at EOF on log dataset archive.log.dataset.name. Expected last RBA eeeeeeeeeeee, found RBA ffffffffffff The EDM Logger was processing data in an archive log data set, and encountered the end of the data set. However, the last log record read did not have the RBA value that was expected. The RBA range in each log data set is recorded in the Restart data sets, but the last log record read did not have the ending RBA recorded for this log data set. So, data that should have been found in the log data set is missing. The archive log data set in which this condition was found, the RBA that was expected to be found, and the RBA value that was found in the last record read, are all included in the message. This is most likely the result of an I/O error in reading or writing the archive log data set. The following actions occur: 1. Error message identified as PWXEDM172781E issued. 2. The Logger task that encountered this error ends. If this was a task that was reading log data for a log reader process, this will cause the associated log reader process to terminate as well. If this occurs during initialization of the PowerExchange Logger, the PowerExchange Logger address space will terminate.
System Action:
User Response:
Examine the status of the log data set that had the error. Try reading the data set yourself to see if the error is permanent or temporary. If the error seems permanent, you may need to use the corresponding secondary log data set to recreate the failing primary log data set. You can then restart the log reader process that failed, or the PowerExchange Logger itself, if the failure occurred during Logger initialization. If you cannot correct the problem, contact Informatica Corporation Product Support. ACTIVE LOG DATASET IS TOO LARGE The format utility (EDMLUTL0) for the PowerExchange Logger active log data sets has abended because the size of the active log data set it was provided exceeds the maximum size allowed for active log data sets. Due to restrictions imposed by the DSPSERV function, the maximum number of 4k blocks in the data set is 524,288. This corresponds to 2,912 cylinders, for a 3390 device, or 3,495 cylinders, for a 3380 device. The format utility ends. Delete the active log data set, and recreate it with a smaller number of cylinders, then rerun the format utility.
754
PWXEDM172783W Logger temporarily in single log mode, using {primary|secondary} log active.log.dataset.name Explanation: The Physical Logger encountered an error when trying to allocate or initialize an active log data set. Messages will have been issued previously to identify exactly what type of problem occurred. This message will only be issued if dual logging has been specified for active log data. The message identifies which data set will be used as the active log data set, and whether that is the primary or secondary active log. The Logger will temporarily switch to single logging mode, but will continue operating normally otherwise. The Logger will resume dual logging mode when it switches to the next pair of active logs, assuming that both the primary and secondary active logs can be allocated and initialized. Investigate the earlier messages that indicate why the primary or secondary active log could not be used, and take any corrective action they indicate. If you cannot correct the problem, contact Informatica Corporation Product Support. Attach failed for module load_module return code=x'nnnnnnnn' The Physical Logger encountered an error when it attempted to ATTACH a load module needed for its processing. The message identifies what load module it was attempting to ATTACH, as well as the return code received from the operation. The Logger will terminate abnormally. Investigate the reason for the failure in the ATTACH macro, using appropriate operating system documentation, along with any other messages that may have be issued in conjunction with this problem. If you cannot correct the problem, contact Informatica Corporation Product Support. Logger subtask terminating for program program_name, Return code=return_code or PWXEDM172785E Explanation: Logger subtask terminating for program program_name, Abend code={Ssss|Uuuuu}, Reason code=reason_code The Logger attaches several subtasks, and monitors their status. If any of the subtasks ends abnormally, either by abending, or by setting a non-zero return code, this message may be issued to indicate that the abnormal termination occurred. This message is issued as the PowerExchange Logger is ending. The message identifies which program was attached (program_name) that terminated abnormally, as well as the system (Ssss) or user (Uuuuu) abend code and associated abend reason code (reason_code), that was encountered, in the case of an abend, or the return code (return_code) in the case of a non-zero return code being detected. The system abend code (Ssss), the reason code (reason_code) and the return code (return_code) are all expressed in hexadecimal. The user abend code (Uuuuu) is in decimal.
Note: program_name, return_code, sss, uuuu and reason_code are substitution variables.
System Action:
User Response:
PWXEDM172785E
The Logger continues termination. PowerExchange issuges this message when the PowerExchange Logger ends abnormally or normally. Investigate any earlier messages that might indicate why a subtask may have abended or set a non-zero return code. Determine the reason for the abend or non-zero return code, using product documentation, along with appropriate operating system documentation, if necessary. If you cannot determine the reason for the problem, contact Informatica Corporation Product Support.
755
global_queue_function call to global queue global_queue_dsn failed. RC=return_code, Reason=rsn_code The Logger encountered an error while processing the global circular queue, global_queue_dsn, it uses to send or receive data. Global queues are used to pass data between address spaces. The function that encountered the error, the name of the global circular queue, the return code, and reason code that were encountered for the function in question are all included in the message text. The possible function calls are:
CLOSE CREATE DELETE GET OPENINL OPENOUT PUT SETEOF System Action: User Response: The Logger ends abnormally. Investigate the reason for the failure in the function call, using any other messages that may have been issued, along with appropriate operating system documentation, if necessary. If you cannot correct the problem, contact Informatica Corporation Product Support. Number of active log datasets currently available: Primary=pppp, Secondary=ssss This message is issued as a result of the Display command for OBJECT=LOG and TYPE=ACT or TYPE=ALL, when the status of active log data sets is requested. Because some of the active log data sets may require archive activity before they can be used to record more data, not all of the active log data sets that will be shown in the output of the 172679 message, which is also produced by this form of the DISPLAY command, are actually available. This message summarizes how many active log data sets ARE available to record more data. The CURRENT active log data sets, which are the ones with the status of in-use in message 172679, are considered as available until they become full. Processing continues normally. This is an informational message. No user action is required normally. If not all of the defined active log data sets are available, it may be that they are not being archived in a timely manner. Look for other messages that might indicate why the archive process is not completing. All active log datasets with Startrba=rrrrrrrrrrrr are unusable This message is issued when a primary active log data set, and a secondary active log data set, if dual logging has been configured for active log data sets) has been found that has been assigned the desired starting RBA, but no active log data set that DOES have that starting RBA is usable. An active log data set that has been assigned this starting RBA is needed because the active log data set or data sets that contained the previous RBA range have become full. The starting RBA that was being looked for is included in the text of the message. Possibly the initialization of the active log data set failed when the PowerExchange Logger was trying to switch to it, in which case message 172642 will have been issued to document the error that occurred. Or, the active log data set may have become unusable during some previous execution of the PowerExchange Logger, in which case it will have had the status STOP when the PowerExchange Logger was started. The status of the active logs can be seen using the PowerExchange Logger DISPLAY command. System Action:
756
The Logger ends abnormally.
User Response:
Investigate the reason for the failure in the active log data set, using any other messages that may have been issued, along with appropriate operating system documentation, if necessary. You can also issue the PowerExchange Logger DISPLAY command in batch mode to determine the status of all the active log data sets that are defined. See member #DISPLOG in the SAMPLIB data set for sample JCL to do this. It may be possible to delete the active log data set that has been assigned the specified starting RBA, and the corresponding secondary active log data set, if applicable, using the DELETE_LOG command in a batch invocation of the PowerExchange Logger, similar to SAMPLIB member #DISPLOG, in which case the PowerExchange Logger might be able to be restarted. If you cannot correct the problem, contact Informatica Corporation Product Support.
PWXEDM172789W Logger logger_operation operation for queue queue_name failed for address_space_name with return code=return_code, reason code=rsn_code Explanation: This message is issued when the PowerExchange Logger has attempted an operation on an internal queue, and the return code from the operation indicated that the operation was not successful. The Logger was either processing a message FROM another address space, or attempting to send a message TO another address space, when the error occurred. The variable logger_operation has one of the following values:

Add (Phase1) Add (Phase2) Delete (UOW) Delete (ECCR) Delete (LogRdr) Add (TermEccr) Add (StopEccr) Add (StopLogRdr) Initialize (EDMNAME) Add (EDMNAME) Term (EDMNAME) The variable queue_name has one of the following values:
GBLXCFQCB GBLOUQQCB GBLINQQCB OUQEDMQCB The type of operation that was attempted, the name of the internal queue, the identification of the other address space, and the return code and reason code from the failed operation, are all included in the text of the message. System Action: Processing continues. However, if the PowerExchange Logger was processing a message it received, it will drop the message, and if the PowerExchange Logger was attempting to send a message to another address space, the message is not sent. In either case, this may leave other address spaces in an unexpected wait condition. Investigate the reason for the failure the PowerExchange Logger experienced in processing the message it received, or in sending a message, using any other messages that may have been issued, including those issued from other address spaces, including log readers or ECCRs. You may also need to refer to appropriate operating system documentation, if appropriate. If you cannot identify and correct the problem, contact Informatica Corporation Product Support.
User Response:
757
PWXEDM172790W command_name command sent by log reader agent log_reader to Logger logger_id discarded, reason_text Explanation: The PowerExchange Logger has received an encoded command from another address space, but is unable to process the encoded command because it encountered an error while trying to do so. The messages includes the following variables:
command_name. Identifies the encoded command that was being processed, which is Resource Interest List. log_reader. Identifies the token for the log reader address space that sent the encoded command logger_id. Identifies the PowerExchange Logger ID reason_text. Describes the error that occurred while trying to process the encoded command and has one of the following values: No matching signed on reader Resource Interest List after REQTRN Encoded command not a request List type is not EDMNAMEs List contains domain names List contains target names List contains category data $EDMCHN error System Action: Processing continues. However, the PowerExchange Logger drops the encoded command, which might leave the log reader address space in an unexpected wait condition and result in that address space timing out. Investigate the reason for the problem described in the message text, by using any other messages that may have been issued such as those issued from the log reader or any ECCRs. You may also need to refer to operating system documentation. If you cannot identify and correct the problem, contact Informatica Global Customer Support. command_name command from log reader agent log_reader with num_names name(s) successfully The PowerExchange Logger has received a Resource Interest List encoded command from a log reader address space and has processed it successfully. The Resource Interest List encoded command provides the PowerExchange Logger with a list of EDMNAMEs in which the log reader is interested. The PowerExchange Logger uses this list to filter change records for other EDMNAMEs from the log data so that only change records of interest are sent to the log reader address space. This filtering reduces resource consumption in the log read process in the log reader. The message includes the token name of the log reader address space in the log_reader variable and the number of EDMNAMEs in the Resource Interest list in the num_names variable. Processing continues. No action is required. generic_message This is a PowerExchange Logger informational message. Processing continues. Respond to the message, if applicable. Otherwise, no action is required.
User Response:
758
PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC)

PWXEDM172800E Explanation: Error in module 'module' offset X'number'. text The change interface component (CIC) detected an error in the specified module at the specified offset. This message can occur when columns are added to SYSTABLES. Additional information about the type of error returned is shown in the text portion of the message. Processing ends. Collect all available information about the termination, and contact Informatica Global Customer Support. process failed. Return code=rc, Reason code=reason. Text The issuing program called a service or function that returned a nonzero return code. Additional information about the type of error returned are shown in the text portion of the message. Processing ends. Check the JES message log and the EDMMSG message log for previous error messages that relate to this error. If this message shows an IBM return code, see the IBM messages and codes documentation that applies to your subsystem. Collect all available information about the termination, and contact Informatica Global Customer Support. PowerExchange issues reason codes from encoded commands that pass between program modules. Some of these reason codes are displayed in the messages you see when an error occurs. For more information about the reason code shown in the message, see Reason Codes 00000813 to 00001515: Encoded Commands on page 922 and Reason Codes 00000C00 to 00000C0E: Common Services on page 923. PWXEDM172802E Explanation: Service task ended prematurely. Completion code=rc, Reason=reason. Program=program The PowerExchange common service environment contains a variety of subtasks, such as message and trace, that must remain active until they are explicitly shut down. One or more of these subtasks ended prematurely. For more information about the reason code shown in the message, see Reason Codes 00000601 to 00004499: Command on page 921. PowerExchange issues reason codes from encoded commands that pass between program modules. Some of these reason codes are displayed in the messages you see when an error occurs. For more information, see Reason Codes 00000813 to 00001515: Encoded Commands on page 922 and Reason Codes 00000C00 to 00000C0E: Common Services on page 923. Processing ends. User Response: Check for previous error messages that relate to this error. Collect all available information about the termination, and contact Informatica Global Customer Support. EDM Agent is not active and STEPLIB is not APF-authorized Certain execution environments require the PowerExchange Agent to run in supervisor state. The PowerExchange Agent must be active, or the job must be executed from an APF-authorized library.
System Action:
759
Processing ends. Make the PowerExchange Agent active or execute the job from an APF-authorized library. If any unauthorized libraries are included in the STEPLIB concatenation, APF-authorization is dropped for all of them. Unable to LOAD module module The specified module could not be found in the JOBLIB/STEPLIB concatenation. Processing ends. Verify that all required load libraries are in the JOBLIB/STEPLIB concatenation. DD ddname is missing The specified DD statement, which is required, is missing. Processing ends. Provide the specified DD statement, and run the job again. Unable to OPEN DD ddname The change interface component (CIC) could not OPEN the file specified in the DD statement. Processing ends. See any previous error messages related to this error to determine why the OPEN failed. Then, correct the problem, and run the job again. ABEND issued by function, Abend code=abend_code, Reason code=reason. Text The specified function issued an abend with the abend code and reason code shown. Additional information about the type of error returned are shown in the text portion of the message. Processing ends. Check for previous error messages related to this error. Collect all available information about the termination, and contact Informatica Global Customer Support. Change Capture active for object [attributes] Edition=edition_number EDMNAME=edmname The Change Interface Component (CIC) issues this message when it activates an environmental change capture routine (ECCR) for a source database or file. It identifies the edition number and EDMNAME of the object. The message may also provide additional attributes for the object, such as the IMS segment name. Additional messages that follow this one provide information about the captured changes for the specified object. Processing continues. No action is required. Change Capture counts for object: Insert=n, Update=n, Delete=n The PowerExchange Agent issues this message after running an environmental change capture routine (ECCR) to show the record counts of how many records were inserted, updated, and deleted for the primary data source specified in object. Processing continues. No action is required.
PWXEDM172804E Explanation: System Action: User Response: PWXEDM172805E Explanation: System Action: User Response: PWXEDM172806E Explanation: System Action: User Response:
760
XCF function in error. Return code=rc, Reason code=reason. Group='group', Member='member'. The indicated Cross-System Coupling Facility (XCF) function for the specified member encountered an error. The return code and reason code are provided. The return and reason codes are documented in the IBM sysplex services documentation. The job step attempts to recover the failing job, and the job remains active to process other requests. Check for previous error messages related to this error. Collect all available information about the message, and contact Informatica Global Customer Support. XCF is in local mode only The Cross-System Coupling Facility (XCF) is active but is not using the coupling facility hardware. Processing continues. No action is required. Unable to establish XCF connection to EDM Logger (loggerid) The job was unable to contact the specified PowerExchange Logger through the Cross-System Coupling Facility (XCF) interface. The job ends. Make sure the PowerExchange Logger is running. If it is, make sure the terminated job and the PowerExchange Logger are using the same default configuration options (EDMSDIR). call_type call to global queue global_queue_ID failed. RC=rc, Reason code=reason. Global queues are used to pass data between address spaces. A call to the global queue service failed. The type of call can be CREATE, DELETE, OPEN, CLOSE, GET, PUT, or SETEOF. The job ends. Check for previous error messages related to this error. Collect all available information about the termination, and contact Informatica Global Customer Support. CIC circular queue manager received a record with an invalid IPC header from program The specified program passed a record with an invalid header to the change interface component (CIC) circular queue manager. Processing ends. Collect all available information about the termination, and contact Informatica Global Customer Support. EDM Agent is required This job uses certain PowerExchange facilities, such as global queues, that require the PowerExchange Agent. Processing ends. Start the PowerExchange Agent, and run the job again. EDM Logger (loggerid) terminated abnormally while an ECCR was active While an environmental change capture routine (ECCR) was active, the change interface component (CIC) received notice through the Cross-System Coupling Facility (XCF) that the PowerExchange Logger terminated.
PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 761
Explanation: User Response:
Depending on the value of the system global parameter, CCERR, one of the following actions occur: The job continues but PowerExchange Change stops. You will lose any changes in progress. (CCERR=CONT) Processing ends. (CCERR=ABEND) Determine what caused the PowerExchange Logger to terminate, correct the problem, and restart the PowerExchange Logger. EDM ECCR received TERMINATE command from EDM Logger loggerid While an environmental change capture routine (ECCR) was active, the change interface component (CIC) received a TERMINATE command from the PowerExchange Logger. This could be caused by a user stopping the PowerExchange Logger. The ECCR ends. Determine what caused the PowerExchange Logger to terminate. Correct the problem, and start the logger again. status XCF group 'group' as member 'member' The specified job either joined or left a Cross-System Coupling Facility (XCF) group. The environmental change capture routines (ECCRs) use the XCF to communicate with the PowerExchange Logger. Processing continues. No action is required. XCF group 'group' status by member 'member' The job was notified through the Cross-System Coupling Facility (XCF) that another job, indicated by member, either joined or left the designated XCF group. The variable status indicates whether the job joined or left the group. The environmental change capture routines (ECCRs) use the XCF to communicate with the PowerExchange Logger. Processing continues. No action is required. Change Capture initialized for CICS/VSAM on CICS/TS V2.2.0 This informational message is issued to document the software level of the CICS capture environment in which the ECCR has been initialized. Processing continues No action is required. Change Capture initialized for DB2 on V7.1.0 - ssid This informational message is issued to document the software level of the DB2 capture environment in which the ECCR has been initialized. Processing continues No action is required. Change Capture initialized for IMS environment on Vv.r.m imsid In this case, the variable environment will be either Online, Batch or DBRC, depending on the IMS environment in which the ECCR is initializing. The variable Vv.r.m is the level of IMS in this environment, and the variable imsid is the IMSID of the IMS environment. Processing continues
User Response:
System Action: User Response: PWXEDM172820I Explanation: System Action: User Response: PWXEDM172820I Explanation: System Action: User Response: PWXEDM172820I Explanation:
System Action:
762
No action is required. Change Capture initialized for DB2 on V8.1.0 - ssid(x) This informational message is issued to document the software level of the DB2 capture environment in which the ECCR has been initialized. The message text contains the following variables:

ssid is the subsystem ID. x specifies the mode of the DB2 V8 subsystem and is one of the following values: C. Compatibility mode. E. Enabling-New-Function mode. N. New-Function mode.
Processing continues. No action is required. XCF member 'member' already active in group 'group' The job attempted to join a Cross-System Coupling Facility (XCF) group using a member name that already exists. This is usually the result of an attempt to start a PowerExchange Logger with a logger ID that is already active. Processing ends. Make certain that the logger ID specified in your startup JCL is the one you want to start. If not, edit and run the startup JCL. If the logger ID specified in your start-up JCL is the one you want to start and you are trying to perform maintenance on your logs, you must first stop the active PowerExchange Logger. Examples of such maintenance tasks are:
Adding, moving, or changing the size of active logs. Recovering damaged logs or restart data sets. Deleting archived logs. Contact Informatica Global Customer Support. PWXEDM172822I Explanation: EDM Global Directory name loaded from dsname, Agent Id=agentid, Logger Id=loggerid The global directory (EDMSDIR), which contains global processing options, was loaded from the specified data set. PowerExchange Change will use the PowerExchange Agent and PowerExchange Logger specified by agentid and loggerid in this message. Processing continues. No action is required.
PWXEDM172823W Unable to connect to EDM Agent agentid, RC=rc, Reason code=reason Explanation: System Action: User Response: The job or component issuing this message was unable to contact the specified PowerExchange Agent. The job or component continues processing without the PowerExchange Agent services. Verify that the job or component is trying to connect to the correct PowerExchange Agent. Verify that your PowerExchange Agent startup procedure is correct and that it was started correctly.
PWXEDM172824W EDM Change Capture waiting on {the Loggers queue|the ECCR-to-CIC queue} since date time. Using EDM Logger loggerid. Explanation: System Action: The job or component issuing this message has filled the queue used to send changed data to the PowerExchange Logger. Processing continues.
PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 763
User Response:
To determine the reason for the wait, note any PowerExchange Logger messages displayed to the console. Take any corrective action indicated by these additional messages.
PWXEDM172825W UOWs are waiting on EDM syncpoint; see EDM log Explanation: System Action: User Response: The job issuing this message contains some units of work that are waiting on PowerExchange Change to complete sync point processing. Processing continues. To determine the reason for the wait, check the EDMMSG data set and any PowerExchange Logger messages displayed to the console. Take any corrective action indicated by these additional messages.
PWXEDM172826W Following unit-of-work has been waiting on {Phase 1 syncpoint processing|Phase 2 syncpoint processing} since date time uowid Explanation: System Action: User Response: The specified unit of work is waiting on the specified commit processing phase. This message is preceded by message PWXEDM172825. Processing continues. To determine the reason for the wait, check the EDMMSG data set and any PowerExchange Logger messages displayed to the console. Take any corrective action indicated by these additional messages. EDM Logger returned error during {Phase 1 syncpoint processing|Phase 2 syncpoint processing|'resolve in-doubt' processing}, return code=rc, Reason code=reason. Unit-of-work id follows: uowid The PowerExchange Logger generated a non-zero return code during the specified process. The ID for the affected unit of work is displayed. Processing continues. To determine the cause of the error, check the EDMMSG data set and any messages displayed by the PowerExchange Logger. For an explanation of the return codes and reason codes, see Return Codes on page 915 and Reason Codes 01800101 to 01FFFFFF: Change Interface Component on page 941. EDM ECCR sent n records to Logger loggerid (m change records) This message provides a count (n) of the records sent from the ECCR to the specified PowerExchange Logger. It also displays how many of these records were changed records (m). The remaining records are unit of work header/trailer records. Processing continues. No action is required. module loaded at address The specified module was loaded at the specified address. Processing continues. No action is required. Capture Status {not resolved|resolved as inactive} for structure_name, DEST=SUBSYS This message is issued by the CIC component of IMS online capture when either a repository call to determine capture status failed or when resolution of capture status occurs after a repository call failure.
PWXEDM172828E
764
System Action:
If the capture status is undetermined and CCERR=ABEND is specified in the EDMSDIR parameters, transactions that attempt to UPDATE the database will ABEND with a U4094. Determine why the repository call failed by checking the PowerExchange Agent status and the PowerExchange Agent message log (EDMSLOG). Take the necessary action to correct the problem. The status of all undetermined databases will be resolved when the next database OPEN initiates a repository call. If the cause of the error cannot be determined, contact Informatica Global Customer Support. EDM ECCR job {connected to|disconnected from} EDM Logger loggerid, Log RBA=log_rba The change capture routine identified by the specified job or IMS ID (job) connected to or disconnected from the specified PowerExchange Logger. The log_rba indicates the starting position in the log for the connection. Processing continues. No action is required. DB2 ECCR terminating due to prior logger failure The DB2 ECCR is ending because its connection to the PowerExchange Logger was disrupted. Without a connection to the PowerExchange Logger, data might be lost. Processing ends. Restart the PowerExchange Logger. Restart the DB2 ECCR using the START WARM statement. This allows the DB2 ECCR to synchronize with the PowerExchange Logger. Resolve-in-doubt: UOW=uowid, Func=Abort, Return code=rc, Reason code=reason This message provides the results of a resolve-in-doubt call from IMS. It indicates that the specified unit of work had to be aborted due to errors during sync point processing. The reason and return codes provide additional information about the error. Processing continues. No action is required. For an explanation of the return codes and reason codes, see Return Codes on page 915 and Reason Codes 01800101 to 01FFFFFF: Change Interface Component on page 941.
User Response:
PWXEDM172844W Following unit-of-work failed during {Phase 1|Phase 2} syncpoint processing, Reason code=reason Explanation: System Action: User Response: PWXEDM172845I Explanation: System Action: User Response: A unit-of-work was told to abort because of a prior error. The unit-of-work abends. See prior messages issued for cause of the error. Reply is value An operator responded with the specified value. Processing continues. No action is required.
PWXEDM172846W Following unit of work was {committed|aborted} during restart processing, SUBSYSTEM=sysid, TOKEN=uowid. Explanation: System Action: This message indicates the status of in-doubt units of work during restart processing in a CICS/DBCTL environment. Processing continues.
765
User Response:
No action is required.
PWXEDM172847W Following unit of work requires manual resolution, SUBSYSTEM=sub_system TOKEN=UOWID. Explanation: System Action: User Response: This message indicates that the UOW identified by the sub_system and UOWID variables is in doubt and requires intervention to resolve. Processing continues. You must manually resolve the UOW in question. If IMS is in doubt, issue the IMS /CHANGE command, with the CCTL and PRTKN options to resolve the UOW. For more information about this command, see the IBM IMS documentation. If IMS is not in doubt, issue the PowerExchange Logger RESOLVE_INDOUBT command to resolve the UOW. For more information about this command, see the PowerExchange CDC Guide for z/OS.
PWXEDM172848W EDMCIRDB COULD NOT OBTAIN STORAGE{

EDMCIRDBIMS ESS CALL TO IMS DBC FAILED| EDMCIRDBGETMAIN FAILED IN IDENTIFY| EDMCIRDBFREEMAIN IMS AREA DID NOT WORK| EDMCIRDBIDENTIFY GETMAIN NEW AREA ERROR| EDMCIRDBKEY 7 STORAGE GETMAIN ERROR| EDMCIRDBFREEMAIN KEY 7 BAD}
Explanation:
This message indicates a critical error occurred in the module EDMCIRDB. The module could not get storage space necessary for processing. If the module can detect a specific reason for the failure, it displays one of the messages that explain why storage could not be obtained. Processing continues, but resolve-in-doubt processing is not available. Contact Informatica Global Customer Support. EDMCICRG: environment_type RET=rc, RSN=reason, structure_name This informational message is written to the PowerExchange Agent log data set each time the CIC checks the PowerExchange repository for changes to the specified structure. The environment type, DB2, IMS, or VSAM, is issued with this message. The return and reason codes provide additional information about the structure and the capture process. The following return codes can be issued with this message:

0. The specified structure is registered in the PowerExchange repository. 8. The specified structure is not registered in the PowerExchange repository.
The following reason codes can be issued with this message:
1701. The registration check failed for an unknown reason. 1702. No structure profiles exists. 1703. There are no profiles for the category type 1704. There are no profiles that match the specified name. 1705. The structure is not active for the requested time. 1706. There is no object profile for the specified structure. 1707. The capture flag is not active for the specified structure. 1708. A registration check for a DB2 or IMS resource type has been made in the wrong mode (internal error). Contact Informatica Global Customer Support. System Action: User Response: Processing continues. No action is required.
766
Logger loggerid is on system sysid1, jobid is on system sysid2 The job identified by jobid must run on the same system as the PowerExchange Logger identified by loggerid. For example, an ECCR must run on the same system as its associated PowerExchange Logger. The specified job ends. Get the PowerExchange Logger ID associated with the job from the default configuration options, EDMSDIR. The system IDs are usually defined in the System Management Facility (SMF) member of SYS1.PARMLIB. Use one of the following methods to correct the error:

Move the job to the PowerExchange Logger system and run it again. Initiate a PowerExchange Logger on the system where the job was run, and edit the job to point to the new PowerExchange Logger.
PWXEDM172851W EDMXMSGX unable to acquire lock, message skipped Explanation: System Action: User Response: The IMS ECCR attempted to issue a message, but the message formatter was busy. In an IMS ECCR environment, messages must be issued one at a time. Processing continues. A message from the IMS ECCR is lost. The error might have occurred in an IMS BMP or MPP region. Check IMS BMP and MPP regions for messages that might require a response. For information on IMS messages, see the appropriate MVS publication for a description of the IMS messages codes. report_title: options When you start an ECCR or other component, PowerExchange issues a report that shows the options in effect for that component. The message is followed by a list of options in effect at the time the component started. Depending on the component, the options shown include:
Default options specified in EDMSDIR DFSESL DD statement options TCP/IP options PowerExchange data transformer (TNR) options System Action: User Response: PWXEDM172853I Explanation: System Action: User Response: PWXEDM172854I Explanation: System Action: User Response: Processing continues. No action is required. Change Capture counts for object Segment=segment_name, ISRT=n, REPL=n, DLET=n This message shows the IMS DBD name for which the ECCR captured changes. The message identifies the IMS segment and the totals for each type of captured change. Processing continues. No action is required. Segment=segment_name, Segment Code=segment_code, ISRT=n, REPL=n, DLET=n This message follows PWXEDM172853 and shows capture counts by segment for an IMS ECCR. The message number is not shown. Processing continues. No action is required.
767
Edition=n, EDMNAME=edmname This message follows message PWXEDM172808 and shows the EDMNAME for the data being captured. The message number is not shown. Processing continues. No action is required. Segment=segment_name, SegCode=segment_code, Edition=n, EDMNAME=edmname This message follows message PWXEDM172808 and shows the EDMNAME for the data being captured. This message is used to show the EDMNAME for segments in an IMS database. The message number is not shown. Processing continues. No action is required. EDM Agent agentid {has not been started|is not active} The PowerExchange Agent is not active. The PowerExchange Agent must be running to perform change captures. Processing ends. Start the PowerExchange Agent, and try the job again. Counts for CIC internal data queue; Record count=nnnn, queue full count=nnnn, queue empty count=nnnn This informational message describes the number of times a task waited on either a full queue or an empty queue. Processing continues. No action is required. No active profile found. Function='02' The EDMFUNC module was called with a command of '02'. No active registered object was found in the PowerExchange repository. The EDMFUNC module returns a nonzero return code and processing ends. You must register and activate one or more objects in the PowerExchange repository before you can run the change capture process.
System Action: User Response: PWXEDM172857E Explanation: System Action: User Response: PWXEDM172863I Explanation: System Action: User Response: PWXEDM172865E Explanation: System Action: User Response:
PWXEDM172872W DD ddname {not allocated, already existed|not deallocated, did not exist}. Explanation: System Action: User Response: The dynamic allocation service could not either allocate the DD because it already existed or deallocate the DD because it did not exist. Processing continues. Use any messages issued after this message to determine whether any action is necessary. If no messages are issued, no action is necessary. The following ZAPs have been applied: This message precedes a line that shows which ZAP modifications have been incorporated into the PowerExchange code. Processing continues. No action is required. This information may be requested by Informatica Global Customer Support.
768
Changed data lost for EDMNAME=edmname {due to failing logger|due to updates during logger failure|recovery needed on target object} (mm/dd/yy HH:MM:SS) This message is issued by CIC when the logger ends abnormally and the CCERR keyword is specified as CONTINUE. The EDMNAME displayed in the message indicates the target with lost change data status. The date and time of the last update made against an object, IMS segment or VSAM data set, is displayed between the brackets () in the error message text. The variations of message text, indicated in brackets [message_text] are further described below:
Due to failing logger - the most common type of message text returned for this error. This message is asynchronous, with notification from XCF that the logger has ended. Due to updates during logger failure - logger terminated during send and was discovered later. It is possible to get both messages, due to failing logger and due to updates during logger failure. recovery needed on target object - this message indicates that the logger terminated with a database or file open and recovery is needed. With this type of message, the date and time may be omitted, and will show as empty parenthesis. System Action: User Response: This message is followed by the warning message PWXEDM172875W. Data capture processing continues despite the data loss. This message indicates that changes have been made to the source that have not been captured, which could result in the target being out of sync with the source component. The target may need to be repopulated or recovered from the indicated time stamp.
PWXEDM172875W Number of targets with CMD recovery needed status=N Explanation: This message indicates the total number (N) of Source objects or segment names that are out of sync with their targets as a result of continued updating during an outage of the PowerExchange Logger. Processing continues. This message indicates the total number of CDM Source objects that are out of sync with their targets. The target needs to be repopulated or recovered from the indicated time stamp before the source and objects will be synchronized.
PWXEDM172876W Unable to record recovery needed status for EDMNAME=edmname, RC=rc, Reason=reason Explanation: System Action: User Response: PWXEDM172877E Explanation: System Action: User Response: PWXEDM172878I Explanation: System Action: The system is unable to record a recovery needed status for a given PowerExchange object, due to failure on the repository data set. Processing continues. The instance of lost changed data is not recorded in the repository for the displayed object. See the preceding messages to determine the reason for failure. Unable to load module. EDMSDIR must be in EDMPARMS or STEPLIB dataset The system is unable to load the EDMSDIR from either the EDMPARMS DD or the STEPLIB DD. Processing continues, data is not captured. See the preceding messages to determine the reason for failure. Processing DD ddname with DSN dsnname The change interface component is processing the specified data definition name for the specified data set name. Processing continues.
769
User Response: PWXEDM172879I Explanation: System Action: User Response: PWXEDM172880E Explanation: System Action: User Response: PWXEDM172881E Explanation: System Action: User Response:
No action is required. Area "nn" processed for DD "ddname" The change interface component is processing the specified FastPath area for the specified data definition name. Processing continues. No action is required. Duplicate area "nn" found in DD "ddname" The change interface component encountered a FastPath area, in the specified data definition name, that was previously processed. The change interface component checks the remaining FastPath areas, but does not update the data. The job abends after all of the areas are checked. Check which data definition names contain the correct data and restart the job. *** The following UOWs must be manually resolved *** This IMS environmental change capture routine (ECCR) message indicates that you must manually commit or abort units of work (UOW). The IMS ECCR continues the startup process. Use the RESOLVE_INDOUBT command to commit or abort the listed UOWs. See the PowerExchange CDC Guide for z/OS for information about resolving in-doubt units of work. UOW In-doubt ECCR=jobname UOWID=uowid needs manual resolution This IMS ECCR message follows messages PWXEDM172881E and PWXEDM172883E and shows a list of the UOWs that you must manually commit or abort. The IMS ECCR continues the startup process. Use the RESOLVE_INDOUBT command to commit or abort the listed UOWs. See the PowerExchange CDC Guide for z/OS for information about resolving in-doubt units of work. UOWs for change capture were unresolved due to IMS COLDSTART This IMS ECCR message indicates that you must manually commit or abort units of work that remain unresolved due to an IMS cold start process. The IMS ECCR continues the startup process. Use the RESOLVE_INDOUBT command to commit or abort the listed UOWs. See the PowerExchange CDC Guide for z/OS for information about resolving in-doubt units of work. nn schema(s) marked for refresh The change interface component marks the EDMNAMEs for which LRP requires a schemas, for refresh. This is in response to a F pacjob,LRP,REFRESH command request, for refresh. Note, for example, that DB2 requires a schema and IMS does not. The change interface component reads the schemas when LRP processes the next CCD record for the EDMNAMEs. No action is required.
770
LRP schema for edmname refreshed due to {Schema Time Stamp|Refresh command} The change interface component refreshes a schema for an EDMNAME due to the time stamp of the schema or an earlier LRP,REFRESH command. Processing continues. No action is required. The following Load Module replacements have been installed: This message precedes a line that shows which load module replacements have been installed into the product. Any subsequent fix, by means of a load module replacement, updates this message line. Processing continues. No action is required. EDP is not receiving control from the DBRC Interface, DATA CAPTURE IS STOPPED The DBRC interface, that is used by PowerExchange, cannot receive control. The IMS ECCR continues the startup process and the PowerExchange change capture process is turned off. Check the DBRC address space to verify that the correct libraries are in the DBRC region. Action if ECCR error encountered has been set to {CONTINUE|ABORT} The IMS operator issued a /SSR command to set the CCERR field in the EDMSDIR default options module to a temporary value. The CCERR field determines to action of the ECCR when it is unable to capture changes for a data resource. The IMS processing continues. No action is required.
System Action: User Response: PWXEDM172887E Explanation: System Action: User Response: PWXEDM172889I Explanation:
PWXEDM172890W There are no open databases registered for capture Explanation: System Action: User Response: The IMS operator issued a /SSR command, STAT or STATWTO, to request statistics but no databases have passed the registration process. The IMS processing continues. No action is required.
PWXEDM172891W An SSR command has been issued that is unknown to EDP Explanation: System Action: User Response: The IMS operator issued a /SSR command other than a PowerExchange CONTINUE, ABORT, STAT, or STATWTO command. The IMS processing continues. Verify that you are using the desired /SSR command and reissue.
PWXEDM172893W eccr_type ECCR eccr_name waiting for Logger Restart UOW information Explanation: When you initialize the DB2 ECCR, the ECCR relies on the PowerExchange Logger to supply the necessary restart information. If the logger cannot return this information. For example, it is waiting for a tape mount. The ECCR will suspend initialization and display a message. Investigate the state of the logger. If you can resolve the problem with the logger, the ECCR will continue initialization.
771
PWXEDM172894W Successful registration of IMS DBD/DSN dbdname/dataset.name prior to full ECCR initialization Explanation: The ECCR determined that data should be captured from the object whose name is included in the message. However, full initialization of the ECCR had not been completed, so the registration data could not be forwarded to the CIC Mailman function. Processing continues. When full ECCR initialization is completed, the registration data will be forwarded, and message 172808 will be issued. Because no changes can be made to the object in question until full ECCR initialization is complete, there is no loss of data as a result of this situation. This message is normal during initialization of the ECCR, particularly for IMS FastPath databases, or in cases IMS can open databases that were open during the previous instance of IMS. If this message occurs at other times, or if the 172808 message is never received, contact Informatica Corporation Product Support.
System Action:
User Response:
PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger

PWXEDM173000W XCF request {QUIESCL|RESUMEL} received from member Logger xcf_member_name (jobname logger_jobname on system system_name) - reason_text Explanation: The Post-Log Merge task received a request to change the status of a member Logger but the current status of that member Logger was inconsistent with the change in status that was requested. The type of request that was received, the XCF member from which the request was received (xcf_member_name), the actual job name of the member Logger (logger_jobname), and the system where the member Logger was executing (system_name) are all included in the text of the message. The message also identifies the type of problem that the Post-Log Merge task detected in the request it received.The reason_text is one of the following values:

Member already quiesced Member not quiesced Member stopped System Action: User Response: Processing continues but the status of the member Logger, as understood by the Post-Log Merge task, is not changed. Investigate the reason why the Post-Log Merge task believed the member Logger's current status was inconsistent with the XCF request, using any other messages that may have been issued, including those issued from other address spaces, in particular the member Logger in question. You may also need to refer to related operating system documentation, if appropriate. If you cannot identify and correct the problem, contact Informatica Global Customer Support. Member Logger xcf_member_name (jobname logger_jobname on system system_name) now {quiesced|resumed} logging for log reader log_reader_name The Post-Log Merge task detected a status change in one of the member Loggers from which it is merging data. The status change occurred because the member Logger sent a message to the Post-Log Merge task. Either the PowerExchange Logger entered a quiesce status meaning that it will temporarily not log any more data, or the PowerExchange Logger has left the quiesce status meaning that it will resume logging data.
772
The logical name for the member Logger (xcf_member_name), the actual job name of the member Logger (logger_jobname), and the system where the member Logger is executing (system_name) are all included in the text of the message. The message also identifies the type of status change, such as quiesce or resume, as well as the logical name (log_reader_name) for a log reader that is affected. The message is issued once for each log reader that is active at the time the status changes. System Action: User Response: PWXEDM173002I Explanation: Processing continues. No action is required. Member Logger xcf_member_name (jobname logger_jobname on system system_name) {is now active|has left the system} The Post-Log Merge task detected a status change in one of the member Loggers from which it was merging data. Either the member Logger has signed on to the Post-Log Merge task and will now start logging data that will need to be merged or the member Logger has left the XCF group and so is not logging any additional data that would need to be merged. The logical name for the member Logger (xcf_member_name), the actual job name of the member Logger (logger_jobname), and the system where the member Logger is executing (system_name) are all included in the text of the message. The message also identifies whether the member Logger has become active or has left the system. This message may be followed by message DTLEDM172141I if the PowerExchange Logger became active, or may be preceded by message DTLEDM172142W if the PowerExchange Logger left the system, for each log reader that may have been receiving merged data from that Logger. System Action: User Response: Processing continues. No action is required.
PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger
773
774
CHAPTER 5
PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities, 775
PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities

PWXEDM175015I Explanation: message_text The PowerExchange Create Event Marker utility (EDMXLUTL) issues this informational message. The text shown in the message varies depending on the context in which the message was issued. In some cases, the message contains references to other error messages showing control card contents and errors that were encountered during control card interpretation. The utility either discards the control card in error, or ends processing, depending on the error detected. The message sometimes provides additional information about system action. Correct the control card in error, or correct the problems indicated in the message text. If other messages are included in the text, correct the problems associated with those messages. Then, run the job again. message_text, return code=rc, reason=reason, logrba=logrba The PowerExchange Create Event Marker utility issues this message to indicate the status of an event command. The message text contains the following variables:

System Action:
User Response:
message_text is the message text. rc is the return code produced when the command executed. reason is the reason code produced when the command executed. logrba is the relative byte address of the event command in the log. System Action: Processing continues. Commands that contain errors are not completed.
775
User Response:
If the command did not execute correctly, correct the error in the command that is indicated by the return and reason codes, or by a reference to another message. Then, submit the command again. For more information on the return and reason codes, see Reason Codes 01440600 to 060906FF: PowerExchange Utilities on page 940 and Reason Codes 00000601 to 00004499: Command on page 921. message_text, highest return code=rc, highest reason=reason The PowerExchange Create Event Marker utility issues this message to indicate that the PowerExchange command event utility has completed processing. The message contains the highest return and reason codes produced during command event processing. The utility ends. If the Create Event Marker utility completed processing with errors, correct the error indicated by the return and reason codes, or by the messages referenced in text. Then, execute the utility again. For more information on the return and reason codes, see Reason Codes 01440600 to 060906FF: PowerExchange Utilities on page 940. Event Mark Notify={EDITION|COPY|ENDCOPY} Summary: event_type.....:event_value... This message is issued by the PowerExchange Create Event Marker utility to indicate that the completion of a notify edition, copy, or end-of-copy marker has been recorded to the PowerExchange Logger. Possible values for the event_type include:
Event Mark Logger RBA Event Sequence number Event Edition number Event Source EDMNAME Related Target EDMNAME This message provides the logger ID and the logger sequence number needed by the apply restart utility. When the notify is for EDITION, this message issues a line for each source EDMNAME that the notify command processed. This message also provides an edition number for each source EDMNAME. If a target EDMNAME is related to the source EDMNAME in the message, this message issues a line for each related target EDMNAME. System Action: User Response: PWXEDM175028E Explanation: The PowerExchange Create Event Marker utility processing continues. Make a note of the information to be used as input to the apply restart utility. EDMNAME, edition=edition_level, reason=reason_code [reason_explanation] This message is issued by the PowerExchange event utility when an attempt to update the edition level of the object fails. The explanation for the reason code may, or may not be present. Processing for the current command ends with an error. Correct the error identified by the reason code and run the utility again. For more information see Reason Codes 00000601 to 00004499: Command on page 921. Event notify utility abending due to write end packet failure, reason=reason An attempt to write the ending packet record for the event notify process has failed. This causes the PowerExchange Logger to write the ending packet record. The reason code in the message indicates why the packet could not be written. The PowerExchange Logger ends processing for the event notify utility. Correct the problem identified by the reason code and run the utility again. For more information on reason codes, see Reason Codes 01440600 to 060906FF: PowerExchange Utilities on page 940.
776
MESSAGE message number (internal message text) HAS NOT BEEN PASSED THE CORRECT NUMBER OF PARAMETERS The internal message generator for the BSCT component has incorrectly formatted data necessary for the message number in question. The actual severity of the error is determined by the severity of the message number in question.
System Action: User Response: PWXEDM175604I Explanation: System Action: User Response: PWXEDM175605E Explanation: System Action: User Response:
The PowerExchange job will perform the action associated with the message that could not be generated. Contact Customer Support for assistance in determining the exact error. BSCT CREATION TIME: mm dd yyyy hh:mm:ss PowerExchange generates this informational message when verifying the version of the BSCT component. The PowerExchange job continues. No response is required. UNABLE TO FIND EDP RELEASE LEVEL The BSCT subcomponent was not able to load an PowerExchange global control block. The PowerExchange job ends. Ensure that the correct libraries are specified in the PowerExchange job's STEPLIB concatenation. Increase the PowerExchange job's REGION size. Check to see if other errors occurred in either the EDMMSG output or the JES message log, and fix the problems indicated by those messages. BSCT AT LEVEL v.r.mm.fff PowerExchange generates this informational message when verifying the version of the BSCT component. The PowerExchange job continues. No response is required. TARGET PROCESSING IS COMPLETE FOR TARGET: target_name Processing has completed for the specified target (target_name). The PowerExchange job continues. No response is required. target informational message The PowerExchange target specified in the previous message (PWXEDM175607I) has generated the data displayed in this message. The PowerExchange job continues. No response is required.
PWXEDM175606I Explanation: System Action: User Response: PWXEDM175607I Explanation: System Action: User Response: PWXEDM175608I Explanation: System Action: User Response:
PWXEDM175609W target warning message Explanation: System Action: User Response: The PowerExchange target specified in message PWXEDM175607I has generated the data displayed in this message. The PowerExchange job continues. Review the information provided by the target processor to determine if the warning requires a response.
PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities 777
PWXEDM175610I Explanation: System Action: User Response: PWXEDM175611I Explanation: System Action: User Response: PWXEDM175612I Explanation: System Action: User Response: PWXEDM175613I Explanation: System Action: User Response: PWXEDM175614I Explanation: System Action: User Response: PWXEDM175616I Explanation: System Action: User Response: PWXEDM175617I Explanation: System Action: User Response: PWXEDM175618I Explanation: System Action: User Response: PWXEDM175619I Explanation:
778
TARGET INITIALIZATION STEP 2 COMPLETE FOR TARGET target_namePhase 2 Initialization processing for the specified target (target_name) has completed. The PowerExchange job continues. No response is required. TARGET INITIALIZATION STEP 2 STARTING FOR TARGET target_name Phase 2 initialization processing for the specified target (target_name) has started. The PowerExchange job continues. No response is required. TARGET INITIALIZATION STEP 1 COMPLETE FOR TARGET target_name Phase 1 initialization processing for the specified target (target_name) has completed. The PowerExchange job continues. No response is required. TARGET INITIALIZATION STEP 1 STARTING FOR TARGET target_name Phase 1 initialization processing for the specified target (target_name) has started. The PowerExchange job continues. No response is required. BULK SOURCE CONTROL TASK PROCESSING STARTING The PowerExchange PAC has started the BSCT component. The PowerExchange job continues. No response is required. BSCT SOURCE/TARGET INTEREST LIST DELIVERY IS STARTING The BSCT component has begun communication with the PowerExchange data transformer component. The PowerExchange job continues. No response is required. BSCT SOURCE/TARGET INTEREST LIST DELIVERY IS COMPLETE The BSCT component has sent the source and target interest lists to the PowerExchange data transformer component. The PowerExchange job continues. No response is required. BSCT TARGET INITIALIZATION IS STARTING The BSCT component has started to send initialization information to the PowerExchange target processors. The PowerExchange job continues. No response is required. BSCT TARGET INITIALIZATION IS COMPLETE The BSCT initialization process is complete.
System Action: User Response: PWXEDM175620I Explanation: System Action: User Response: PWXEDM175621E Explanation: Explanation: User Response:
The PowerExchange job continues. No response is required. BULK SOURCE CONTROL TASK PROCESSING IS COMPLETE The BSCT component has determined that all processing for this PowerExchange job has completed. The PowerExchange job ends. No response is required. ERROR ATTEMPTING TO CONNECT TO EDP MESSAGE PROCESSOR: RC = return_code The BSCT component cannot connect to the internal PowerExchange message processor. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO DISCONNECT FROM EDP MESSAGE PROCESSOR: RC = return_code The BSCT component cannot disconnect from the internal PowerExchange message processor. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO CONNECT TO EDP COMMON SERVICES: RC = return_code; REASON CODE = reason_code The BSCT component cannot connect to PowerExchange common services. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO DISCONNECT FROM EDP COMMON SERVICES: RC = return_code; REASON CODE = reason_code The BSCT component cannot disconnect from PowerExchange common services. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO ACCESS EDP PAC INFORMATION: RC = return_code; REASON CODE = reason_code The BSCT component cannot access PowerExchange PAC internal control blocks. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. This error can also occur if you attempt to run program EDMBDSC outside of a PAC environment.
779
ERROR ATTEMPTING TO OPEN INTERNAL INPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component cannot communicate with other PowerExchange components necessary to perform a PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO OPEN INTERNAL OUTPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component cannot communicate with other PowerExchange components necessary to perform a PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO OPEN INTERNAL COMMAND QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component cannot communicate with other PowerExchange components necessary to perform a PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO CLOSE INTERNAL INPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO CLOSE INTERNAL OUTPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO CLOSE INTERNAL COMMAND QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation.
780
The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO READ FROM INTERNAL INPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO WRITE TO INTERNAL OUTPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. target status information The target apply component sends status information messages to the BSCT component, usually during checkpoint processing. The PowerExchange job continues. No response is required. TARGET INITIALIZATION ERROR FOR TARGET target_name The specified target apply component (target_name) encountered an error during initialization. The PowerExchange job ends. Check the log file of the failed target apply component. Fix the problem that generated the error, and restart the job. ERROR ATTEMPTING TO SEND INTEREST LISTS The BSCT component could not send source or target processing lists to the data transformer component. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. ERROR ATTEMPTING TO SEND PAC INIT COMPLETE COMMAND The BSCT component could not send an initialization-complete message to the PAC master task. The PowerExchange job ends.
781
User Response:
Scan the PowerExchange job log for prior errors. This problem most likely occurred because of a failure in another PowerExchange component. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. BULK PROFILE NAME IS MISSING The PowerExchange job contains an invalid or missing PowerExchange profile name. The PowerExchange job ends. Ensure that you specified the correct profile name as input to the PowerExchange job and that the correct PowerExchange repository is being used. INTERNAL ERROR BUILDING BULK PROFILE REQUEST: error_information The PowerExchange job could not find a valid profile with the given PowerExchange profile name. The PowerExchange job ends. Ensure that you specified the correct profile name as input to the PowerExchange job and that the correct PowerExchange repository is being used. Use the PowerExchange console to ensure that the PowerExchange profile has not been disabled due to errors in its definition. target error information A target apply task encountered an error. This message lists the error. The PowerExchange job ends. A prior error message specified the target in error. Fix the problem specified in the prior error message. You may need to look at the output log of the target apply component to determine what the actual error is. After the problem is fixed, restart the PowerExchange job. TARGET RETURNED AN INVALID RESPONSE A target apply task encountered an unknown processing error. The PowerExchange job ends. A prior error message specified the target in error. Scan the output log of the target apply component to determine what the actual error is. After the problem is fixed, restart the PowerExchange job. SOURCE TYPE 'DB2/IMS/VSAM' NOT LICENSED FOR USE The licensing check failed. The PowerExchange job ends. Ensure that you have a proper license to run the PowerExchange product. Ensure that the data set that contains the PowerExchange licensing key is specified in your STEPLIB concatenation. UNABLE TO ACCESS PAC CONTROL BLOCKS: RC= return_code; REASON CODE = reason_code The BSCT was unable to access internal PAC control blocks. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing. This error can also occur if you attempt to run program EDMBDSC outside of a PAC environment.
782
PWXEDM175646E Explanation: System Action: User Response: PWXEDM175647E Explanation: System Action: User Response: PWXEDM175648E Explanation: System Action: User Response:
A TARGET COMPLETE MESSAGE WAS SENT FOR AN UNKNOWN TARGET target_name BSCT has received information from an unknown target writer (target_name). The PowerExchange job ends. Contact Informatica Global Customer Support. NO TARGET WRITERS SUCCESSFULLY INITIALIZED PowerExchange does not currently issue this message. The data propagation job ends. Contact Informatica Global Customer Support. UNEXPECTED actual_response_type RESPONSE RECEIVED WHEN expected_response_type RESPONSE EXPECTED A target writer terminated unexpectedly. The PowerExchange job ends. Scan the PowerExchange job log for prior errors. Scan the target writers' job logs for errors. When the problem is resolved, rerun the job.
783
784
CHAPTER 6

PWXEDM176400E to PWXEDM176437E: CICS/VSAM ECCR, 785 PWXEDM177000E to PWXEDM177593E: DB2 ECCR, 792
PWXEDM176400E to PWXEDM176437E: CICS/VSAM ECCR

PWXEDM176400E Explanation: Undefined message number msg_number A CICS/VSAM ECCR internal module issued a message; however, the specified message number is not defined in the message table. The CICS/VSAM ECCR does not display the issued message. Processing continues. Collect all available information about the error and contact Informatica Global Customer Support. CICS function failed. Program is program, Exit is exit. Reason: eibrcode, eibresp, eibresp2 CICS/VSAM ECCR initialization failed to load or enable a CICS/VSAM ECCR exit program. CICS/VSAM ECCR initialization fails. Determine the cause of the failure by examining the function program name, exit name, and reason codes. The reason codes are the contents of the EIBRCODE, EIBRESP, and EIBRESP2 fields. For the meaning of these EIB codes, see the CICS Application Reference Manual. Correct the problem, and start the CICS/VSAM ECCR again. CICS shutdown scheduled due to fatal error in CIC function CICS/VSAM ECCR initialization detected a fatal error in a common interface component (CIC) function. The possible values for function are:
Initialization Termination
785
The CICS/VSAM ECCR ends. Determine the cause of the failure by examining the SYSLOG and the CICS/VSAM ECCR error log. Correct the problem, and start the CICS/VSAM ECCR again. Fatal error returned from EDMCCICS. Reason code is reason CICS/VSAM ECCR initialization detected a fatal error. The common interface component (CIC) passed the reason code displayed in reason to this ECCR. CICS/VSAM ECCR initialization fails. Determine the cause of the failure by examining the SYSLOG and the CICS/VSAM ECCR error log, correct the problem, and start the CICS/VSAM ECCR again. For more information about the reason code, see Reason Codes 01800101 to 01FFFFFF: Change Interface Component on page 941 or Reason Codes 00000601 to 00004499: Command on page 921. CICS EDM initialization completed successfully CICS/VSAM ECCR initialization completed successfully. CICS/VSAM ECCR is now ready to capture changed data. No action is required. CICS EDM initialization in progress CICS/VSAM ECCR initialization is beginning. The CICS/VSAM ECCR is initialized. No action is required. Invalid operand specified - press enter for help The CICS/VSAM ECCR operator transaction was entered with an invalid operand. The operator transaction is not processed. Reenter the PowerExchange operator transaction with a valid operand. You can use the operand HELP to display a list of operands and their functions. EDM initialization request rejected - EDM is already initialized You entered an operator transaction request to initialize the CICS/VSAM ECCR; however, the CICS/VSAM ECCR was already initialized. The initialization request is rejected. No action is required. EDM {TERMINATION|DISPLAY} request rejected - EDM has not been initialized You entered a CICS/VSAM ECCR operator transaction to request the specified function, but the CICS/VSAM ECCR was not initialized. The CICS/VSAM ECCR rejects the request. Initialize the CICS/VSAM ECCR, and enter the request again. EDM termination complete The CICS/VSAM ECCR terminated. It is no longer active. No additional change capture requests can be processed. No action is required.
PWXEDM176404I Explanation: System Action: User Response: PWXEDM176405I Explanation: System Action: User Response: PWXEDM176406E Explanation: System Action: User Response:
PWXEDM176407E Explanation: System Action: User Response: PWXEDM176408E Explanation: System Action: User Response: PWXEDM176409I Explanation: System Action: User Response:
786
Unable to locate file filename in change directory. Data set name is: dsname The OPEN command processing failed to locate the specified file in the change capture directory. The CICS/VSAM ECCR rejects the OPEN request and closes the file. Collect the available information about the error and contact Informatica Global Customer Support. Error occurred during {OPEN|CLOSE} of file filename, ECCR is terminating The OPEN or CLOSE command processing detected that the CICS/VSAM ECCR is no longer capturing changes. The CICS/VSAM ECCR connection is terminated, and the OPEN or CLOSE request continues. Determine why the CICS/VSAM ECCR terminated. If required, reconnect the CICS/VSAM ECCR, and initialize the CICS/VSAM ECCR interface. You can reconnect the ECCR by using the EDMC transaction or by restarting CICS. For more information about the CICS/VSAM ECCR, see the PowerExchange CDC Guide for z/OS. Error occurred during {OPEN|CLOSE} of file filename, file changes suppressed The OPEN or CLOSE command processing detected a critical error requiring ECCR termination. Because the CCERR EDMSDIR option has been set to ABEND, the CICS File Control exits used by the CICS/VSAM ECCR will stay activated, to prevent further changes to any files. This ensures the integrity of the change capture process. Any CICS transaction that attempts to update files that already had been determined as needing to be captured, or that open ANY files after the error and attempt to update them, are abended. Determine the cause of the failure by examining the SYSLOG and the EDP error log, and correct the cause of the error. Issue the EDMC transaction with the DISPLAY operand, and look for files with a status of Reg Error. This status will only exist for files whose registration status, when they were being opened, could not be determined, and only if the EDMSDIR option CCERR=ABEND is in effect (if CCERR=CONT, the CICS/VSAM ECCR would have shutdown completely). To remove the CICS exits established by the ECCR, and allow updates to files that are being prevented, manually terminate the ECCR, using the EDMC transaction with the TERM operand. However, any changes made after this point will not be captured by the CICS/VSAM ECCR. Once the original problem has been corrected, you can start the CICS/VSAM ECCR again using the EDMC transaction with the INIT operand.
User Response:
File filename is not recoverable and has been closed. Data set name is dsname The OPEN command processing detected that the specified file has been registered for change capture, but it is not defined as a recoverable file. Unrecoverable files cannot participate in change capture. The CICS/VSAM ECCR rejects the OPEN request and closes the file. Either redefine the file as a recoverable file and submit the request again, or remove the file from the change capture register. File filename is not keyed or numbered VSAM and has been closed. Data set name is dsn OPEN processing detected that the specified file has been registered for change capture but is not defined as a VSAM KSDS or as a VSAM RRDS The OPEN request is rejected and the file is closed.
787
User Response:
Only VSAM KSDS or RRDS files may participate in change capture. Redefine the file as a VSAM KSDS or RRDS file and retry, or remove the file from the change capture register. Unable to locate before image record for update of file filename An update or delete request was unable to locate the required before image of the record. The CICS/VSAM ECCR rejects the file request. Collect all available information about the error and contact Informatica Global Customer Support. Unexpected return code rc on update call for file filename A file update request received an invalid return code from the common interface component (CIC). The CICS/VSAM ECCR rejects the file request. Collect all available information about the error and contact Informatica Global Customer Support. EDM termination failed. Return code is rc CICS/VSAM ECCR termination received an invalid return code from the common interface component (CIC). CICS/VSAM ECCR termination does not occur. Collect all available information about the error and contact Informatica Global Customer Support. EDM syncpoint (1|2|R) failed. Reason code is reason CICS/VSAM ECCR sync point processing received an invalid return code from the common interface component (CIC) during the specified phase of sync point processing. The sync point phases are as follows:
1 - Phase 1 2 - Phase 2 R - Rollback This message can also occur if the PowerExchange Logger was unavailable during sync point processing. System Action: User Response: The sync point fails, and the CICS/VSAM ECCR backs out the transaction. Check the PowerExchange message log (EDMMSG) for other messages that might contain information about the error. Collect all available information about the error. Contact Informatica Global Customer Support. Unable to obtain key details. Component: type, return code: rc, file: filename The system attempted to obtain the key details for the base data set for a VSAM path. The SHOWCAT command failed on the specified component with a return code of rc. The file OPEN request fails, and the CICS/VSAM ECCR closes the file. Ensure that the VSAM path and associated components are correctly defined. Contact Informatica Global Customer Support. Unable to locate data component for base data set of file filename The system attempted to obtain the key details for the base data set for a VSAM path. The SHOWCAT command for the base cluster did not return any information about the associated data component.
788
The file OPEN request fails, and the CICS/VSAM ECCR closes the file. Ensure that the VSAM PATH and associated components are correctly defined. Contact Informatica Global Customer Support. File request timed out waiting for file open to complete, file is filename The system attempted to access the specified file while OPEN processing was occurring. After 12 attempts, with a 5-second wait for each attempt, the OPEN processing did not complete. The file OPEN request fails. Determine why the file OPEN did not complete. A possible cause is that a data set recall was in progress. Resubmit the request after the OPEN completes. EDM initialization request rejected. Unsupported CICS Release You attempted to initialize the CICS/VSAM ECCR in an unsupported release of CICS. The CICS/VSAM ECCR rejects the initialization request. Run the CICS/VSAM ECCR on a supported release of CICS. File filename is a UMT Data Table and has been closed. Data set name is dsname. OPEN command processing detected that the specified file is registered for change capture, but the file is defined as a user-maintained data table. The CICS/VSAM ECCR does not support user-maintained data tables. Only VSAM KSDS files can be registered for change capture. The file OPEN request fails, and the CICS/VSAM ECCR closes the file. Ensure that the VSAM path and associated components are correctly defined. Redefine the file as a KSDS, or cancel the registration for the VSAM source file. Error closing file, DD=ddname, DSN=dsname, RESP=response1, RESP2=response2 An error occurred when the CICS/VSAM ECCR attempted to close a data set. Processing continues. The data set specified in the message remains open. Refer to any previous messages to determine why the ECCR tried to close the data set. For more information about the values of RESP and RESP2, see the IBM CICS system programming documentation. EDM is disabled. Issue TERM and INIT commands to reactivate PowerExchange is inactive because of a previous error. CICS/VSAM ECCR processing ends. Check the PowerExchange message log to determine why PowerExchange processing stopped. Issue the TERM and INIT commands to restart the CICS/VSAM ECCR. Error inquiring on file, DD=ddname, DSN=dsname, RESP=response1, RESP2=response2 An error was encountered while performing INQUIRE on a file to determine whether or not it is a PATH. The OPEN request is rejected and the file is closed. For RESP response and RESP2 response2 values, see the CICS System Programming Reference Manual.
789
Error inquiring on file, DD=ddname, DSN=dsname, RESP=response1, RESP2=response2 An error was encountered while performing INGQUIRE on a file to determine various file attributes such as key length or file type. The OPEN request is rejected and the file is closed. For RESP response and RESP2 response2 values, see the CICS System Programming Reference Manual. UOWs were unresolved for Change Capture due to CICS COLDSTART The last termination of the Customer Information Control System (CICS) left units of work (UOWs) in doubt. The CICS start process and change capture processing continues. See the PowerExchange Logger commands and manually resolve the in-doubt UOWs.
PWXEDM176429W CICS System Log status is log_status, change capture continuing due to CCERR=CONT Explanation: System Action: The PowerExchange initialization process completed successfully, but the CICS system log is not enabled and active. In this state, the CICS cannot back out any changes from abended transactions. The PowerExchange change capture process will not apply changes from abended transactions, so the source and target may no longer remain in sync. The CICS start process and change capture processing continues. To ensure that the source and target remain synchronized, verify that the CICS system log is properly defined and that it does not exist as a dummy log. CICS System Log status is log_status, CICS shutdown scheduled due to CCERR=ABEND The PowerExchange initialization process completed successfully, but the CICS system log is not enabled and active. In this state, the CICS cannot back out any changes from abended transactions. The PowerExchange change capture process will not apply changes from abended transactions, so the source and target may no longer remain in sync. The CICS processing ends. To ensure that the source and target remain synchronized, verify that the CICS system log is properly defined and that it does not exist as a dummy log. Syncpoint processing entered, type value is contents When enabled, this diagnostic message indicates the contents for the FUNC (syncpoint function code), TRWA (transaction-related work area), and TFWA (task file work area) at every synchronization point. No response is required. ECCR processing beginning for UOW, using TFWA contents When enabled, this information message is issued every time a task file work area is created, which happens at the start of a UOW. Contents contains the contents of the task file work area. No response is required. ECCR captured operation for file_name, using TFWA contents When enabled, this informational message is issued every time a change (UPDATE, INSERT, or DELETE) is captured (that is, after the change is sent to the change interface component (CIC) component). Operation indicates whether the change was a DELETE,
User Response:
User Response:
790
INSERT, or UPDATE, and file_name indicates the CICS file name. Contents contains the contents of the task file work area. User Response: No response is required.
PWXEDM176435W CICS EDM termination completed with warnings Explanation: This message can be issued during termination of the CICS/VSAM ECCR (for example, as a result of issuing the EDMC transaction with the TERM operand), if problems occur while performing the termination. This message is issued instead of the usual message 176409. An example of a situation that could cause this is if the EDMC transaction with the TERM operand is being issued after the CICS/VSAM ECCR automatically shutdown due to an error in processing while EDMSDIR option CCERR=ABEND is in effect. In this case, message 176412 will have been issued previously. This message could also be issued, if the EDMSDIR option CCERR=CONT is in effect, if an error occurs while the ECCR is being initialized, and the registration status of an already-open file cannot be determined. Determine the cause of the failure by examining the SYSLOG and the CICS/VSAM ECCR error log. If you want the CICS/VSAM ECCR to be active, correct any problems and restart the ECCR, using the EDMC transaction with the INIT operand. If the problem persists, contact Informatica Global Customer Support. PWXEDM176436W CICS EDM initialization completed with warnings Explanation: This message can be issued at the completion of CICS/VSAM ECCR initialization, instead of the usual message 176404. This would most likely occur if, while scanning all the already-open files to determine their registration status, an error occurred. This should have resulted in the issuance of message 176412 for each file during initialization. To preserve the integrity of the change capture process, as specified with the EDMSDIR option CCERR=ABEND, all files found open during CICS/VSAM ECCR initialization are recorded by the ECCR, and updates to them will be prevented. System Action: At this point, the ECCR will be only partially active, and any CICS transaction that attempts to update files for which message 176412 was issued, or that open ANY files and attempt to update them, are abended. Issue the EDMC transaction with the DISPLAY operand, and look for files with a status of Reg Error. This status will only exist for files whose registration status, when found to be already open during initialization, could not be determined, and only if the EDMSDIR option CCERR=ABEND is in effect (if CCERR=CONT, the initialization of the CICS/VSAM ECCR would fail completely and message 176437 is issued). Also, look for other reasons why the initialization of the CICS/VSAM ECCR would have failed, by examining the SYSLOG and the CICS/VSAM ECCR error log. If message 176412 was issued during the initialization process, and if you want the CICS/VSAM ECCR to be active, correct any problems and restart the ECCR, by first issuing the EDMC transaction with the TERM operand, and then issuing the EDMC transaction with the INIT operand. If the problem persists, contact Informatica Global Customer Support.
User Response:
User Response:
791
CICS EDM initialization failed This message can be issued at the completion of CICS/VSAM ECCR initialization, instead of the usual message 176404. This would most likely occur if, while scanning all the already-open files to determine their registration status, an error occurred. This message is only issued if the EDMSDIR option CCERR=CONT is in effect (if CCERR=ABEND, the initialization of the CICS/VSAM ECCR completes partially, and message 176436 is issued). Look for reasons why the initialization of the CICS/VSAM ECCR would have failed, by examining the SYSLOG and the CICS/VSAM ECCR error log. Correct any problems discovered and restart the ECCR, by issuing the EDMC transaction with the INIT operand. If the problem persists, contact Informatica Global Customer Support.
User Response:
PWXEDM177000E to PWXEDM177593E: DB2 ECCR

PWXEDM177000E Explanation: System Action: User Response: ERROR - MODULE CCDCICI REASON CODE=1 The change interface component (CIC) did not post a termination event control block (ECB). This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. ERROR - MODULE CCDCICI REASON CODE=3 The change interface component (CIC) did not post a communication event control block (ECB). This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent or PowerExchange Logger issued. Correct the problem, and run the job again. ERROR - MODULE CCDCICI REASON CODE=4 The change interface component (CIC) did not post any of the expected event control blocks (ECBs). This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. INTERFACE ERROR RETURN CODE=X'rc' (rc) REASON CODE=X'reason' (reason) The change interface component (CIC) encountered an internal error and returned control to the DB2 ECCR. The CIC also passed the return code rc and reason code reason to the DB2 ECCR. This is an internal CIC error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
System Action:
792
User Response:
Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. ERROR - MODULE CCDCICP REASON CODE=1 The change interface component (CIC) did not post a termination event control block (ECB). This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. ERROR - MODULE CCDCICP REASON CODE=3 The change interface component (CIC) did not post a communication event control block (ECB). This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. ERROR - MODULE CCDCICP REASON CODE=4 The change interface component (CIC) did not post any of the expected event control blocks (ECBs). This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. EDM INTERFACE ERROR RETURN CODE=X'rc' (rc) REASON CODE=X'reason' (reason) The change interface component (CIC) encountered an internal error and returned control to the DB2 ECCR. The CIC also passed the return code rc and reason code reason to the DB2 ECCR. This is an internal CIC error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Ensure that the PowerExchange Agent and PowerExchange Logger are active. To determine the cause of the error, check the PowerExchange message log for additional messages associated with this error that the CIC, PowerExchange Agent, or PowerExchange Logger issued. Correct the problem, and run the job again. {START|STOP} TRACE(MONITOR) CLASS(1) HAS BEEN EXECUTED The DB2 ECCR issued the -START/STOP TRACE(MONITOR) CLASS(1) DB2 command. This DB2 command enables capturing changed data for the DB2 subsystem. Processing continues. No action is required.
793
ERROR WHILE ISSUING IFI CALL - IFI RC/RSNC=rc/reason The DB2 ECCR encountered an error while trying to issue the -START TRACE(MONITOR) CLASS(1) DB2 command. For an explanation of the DB2 return code rc and reason code reason, see IBM DB2 messages and codes manual. The DB2 ECCR abends. Check the PowerExchange message log for any messages associated with this message. To correct the problem, follow the instructions in the associated messages, if any, and in IBM DB2 messages and codes manual. Then, start the DB2 ECCR again. EDM LOGGER UOW IS NOT THE SAME AS DB2 CHANGE CAPTURE AT TERMINATION When the DB2 ECCR terminated, the oldest open unit of work (UOW) in the PowerExchange Logger did not match the oldest open unit of work in the DB2 ECCR capture directory. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. EDM LOGGER LAST READ RBA IS GREATER THAN DB2 CHANGE CAPTURE AT TERMINATION When the DB2 ECCR terminated, the PowerExchange Logger had a last read RBA greater than the last read RBA in the DB2 ECCR capture directory. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DB2 ECCR STATUS: LAST READ RBA=rba OLDEST OPEN URID=urid This message displays the last read RBA and the oldest open unit-of-recovery ID (URID) in the DB2 ECCR capture directory. (An PowerExchange Logger UOW is the same as a DB2 unit of recovery (UR).) Processing continues. No action is required. EDM LOGGER: LAST READ RBA=rba OLDEST OPEN URID=urid This message displays the last read RBA and the oldest open unit-of-recovery ID (URID) that the DB2 ECCR received from the PowerExchange Logger. (An PowerExchange Logger UOW is the same as a DB2 unit of recovery (UR).) This message is issued at the start-up of the ECCR. Processing continues. No action is required. DIRECTORY CANNOT BE ACCESSED During a restart, the DB2 ECCR could not access a directory it requires. The restart fails. The DB2 ECCR abends. Use the information from other messages associated with the failure to correct the problem. Then, try the restart again. ROLLBACK HAS FAILED During a restart, the DB2 ECCR issued a rollback, and the DB2 rollback failed.
794
The restart fails. The DB2 ECCR abends. Use the information from other messages associated with the failure to correct the problem. Then, try the restart again. TABLE=table_name NOT DEFINED During a restart, the DB2 ECCR tried to find the specified table name, but the table name is not defined to DB2. The restart fails. The DB2 ECCR abends. Use the information from other messages associated with the failure to correct the problem. Then, try the restart again. If the fully-qualified table name is in excess of 27 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177016W TABLE NOT DEFINED, EDIT PROCEDURE NOT FOUND PWXEDM177016W CREATOR=creator_name PWXEDM177016W TABLE=table_name
In addition, if one or the other of the creator or name are themselves longer than 80 characters, the name is continued, as in:
PWXEDM177016W TABLE NOT DEFINED, EDIT PROCEDURE NOT FOUND PWXEDM177016W CREATOR=long_creator_name.... PWXEDM177016W continued_creator
PWXEDM177016W TABLE=long_table_name.... PWXEDM177016W continued_name
EDITPROC file_name UPDATED IN TABLE table_name During a restart, the DB2 ECCR encountered an updated EDITPROC exit routine in the specified table. Processing continues. No action is required. OPEN FAILED FOR DDNAME PWXEDMTRACE The DB2 ECCR could not open the DD name PWXEDMTRACE. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. CLOSE FAILED FOR DDNAME PWXEDMTRACE The DB2 ECCR could not close the DD name PWXEDMTRACE during termination. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. STORAGE OBTAIN/RELEASE FAILED A GETMAIN error occurred. The DB2 ECCR was unable to obtain or release storage. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support.
795
PWXEDM177021W LZCOMPRS FREE FAILURE, RC = rc REASON = reason Explanation: System Action: User Response: The DB2 ECCR encountered an internal error while processing a compressed row. For descriptions of the return code and reason code, see the appropriate MVS publication. Processing continues. Collect all available information about the error. Contact Informatica Global Customer Support. DYNAMIC ALLOCATION FAILED, DSNAME = dsname SVC 99 RC = rc REASON = reason INFO CODE = code While processing a compressed row from the data set dsname, the DB2 ECCR encountered an internal error that was caused by dynamic allocation. For descriptions of the return code, reason code, and information code returned by the dynamic allocation routine (SVC 99), see the appropriate MVS publication. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. OPEN FAILED FOR DSNAME = dsname While the DB2 ECCR was processing a compressed row, the system failed to open the specified data set. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. POINT FAILED WITH RC = rc FOR RBA = rba IN DSNAME = dsname While processing a compressed row from the specified data set, the DB2 ECCR encountered an internal error. For a description of the return code, see the appropriate MVS publication The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. SEQUENTIAL GET FAILED WITH RC = rc DSNAME = dsname While processing a compressed row from the specified data set, the DB2 ECCR encountered an internal error. For a description of the return code, see the appropriate MVS publication The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. CONNECT TO LZ COMPRESS INTERFACE FAILED WITH RC = rc REASON = reason DSNAME = dsname The DB2 ECCR is unable to decompress a compressed row from the specified data set. For descriptions of the return code and reason code, see the appropriate MVS publication. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support.
796
PWXEDM177027W CLOSE FAILED WITH RC = rc DSNAME = dsname Explanation: While processing a compressed row from the specified data set, the DB2 ECCR encountered an internal error. For a description of the return code, see the appropriate MVS publication Processing continues. Collect all available information about the error. Contact Informatica Global Customer Support.
PWXEDM177028W DYNAMIC DEALLOCATION FAILED, DSNAME = dsname SVC 99 RC = rc REASON = reason INFO CODE = code Explanation: While processing a compressed row from the specified data set, the DB2 ECCR encountered an internal error caused by dynamic deallocation. For descriptions of the return code, reason code, and information code returned by the dynamic allocation routine (SVC 99), see the appropriate MVS publication. Processing continues. Collect all available information about the error. Contact Informatica Global Customer Support. LZCOMPRS EXPANSION FAILURE, RC = rc REASON = reason DSNAME = dsname The DB2 ECCR is unable to decompress a compressed row from the specified data set. For descriptions of the return code and reason code, see the appropriate MVS publication. The DB2 ECCR abends. Collect all available information about the error. Contact Informatica Global Customer Support. CAPTURE PROGRAM error_reason_text The DB2 ECCR encountered an error that was identified in a preceding message. This message provides additional information about the error. The DB2 ECCR action varies based on one of the following error reasons:
ATTEMPTS TO CONTINUE:
The DB2 ECCR stops processing the record or operation that caused the error. Then, the DB2 ECCR attempts to continue by processing the next log record or the next ST definition.
ABENDS: ABENDS with PERMIL=0:
The DB2 ECCR abends because the error is too severe to continue.
The DB2 ECCR abends because the //REPL2CTL file contains (or defaults to) an EC PERMIL=0 control record.
ABENDS-PERMIL= THRESHOLD IS EXCEEDED:
The DB2 ECCR abends because the number of errors that occurred exceeds the maximum number of errors specified on the //REPL2CTL file EC PERMIL=nnn control record. User Response: Your response depends on the system action.
ATTEMPTS TO CONTINUE: ABENDS: ABENDS with PERMIL=0:

PWXEDM177000E to PWXEDM177593E: DB2 ECCR 797
No action is required.
Use the information in the associated messages to determine your response.
Provide an EC PERMIL=nnn control record in //REPL2CTL, and restart the DB2 ECCR. A value greater than 0 allows the DB2 ECCR to skip the log records that result in errors.
ABENDS-PERMIL= THRESHOLD IS EXCEEDED:
Increase the PERMIL=nnn value in the EC PERMIL=nnn control record, and restart the DB2 ECCR. Increasing this value allows the DB2 ECCR to tolerate more errors and allows it to skip more log records that result in errors. PWXEDM177031W SUSPENDING ERROR DIAGNOSIS Explanation: To keep from filling the consoles and the trace data sets with error information, the DB2 ECCR limits the number of errors that can issue error messages and diagnosis information to a maximum number of errors per hour. The DB2 ECCR issues this message when it encounters an error and the maximum number of errors per hour is reached. Between the time it issues this message and the beginning of the next hourly cycle, the DB2 ECCR suspends issuing error messages and diagnosis information for errors that do not result in abends. Processing continues. However, the DB2 ECCR might handle some errors without providing the associated error messages. No action is required. RESOURCE CLEANUP IS COMPLETE The DB2 ECCR completed the resource cleanup process. Processing continues. No action is required. LOAD MODULE PX029010 IS NOT 'REUSABLE' You did not specify the DB2 ECCR load module PX029010 as REUSABLE or REENTRANT when you processed it using the linkage editor. The preferred setting is REENTRANT; the minimum acceptable setting is REUSABLE. The DB2 ECCR abends. Specify the load module PX029010 as REUSABLE or REENTRANT, and process the module with the linkage editor. Then, run the job again. LOAD MODULE PX029011 IS NOT 'REUSABLE' You did not specify the DB2 ECCR load module PX029011 as REUSABLE when you processed it using the linkage editor. The DB2 ECCR abends. Specify the load module PX029011 as REUSABLE, and process the module with the linkage editor. Then, run the job again. IMS ENVIRONMENT IS INVALID FOR CAPTURE PROGRAM You attempted to run the DB2 ECCR in an IMS region. You cannot run the DB2 ECCR in an IMS region. The DB2 ECCR abends. Change the JCL to run the DB2 ECCR in a non-IMS environment, and run the job again. INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend.
System Action: User Response: PWXEDM177032I Explanation: System Action: User Response: PWXEDM177033E Explanation:
798
The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID CPOOL-ID The DB2 ECCR found an invalid CPOOL ID. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID CPOOL CELL-ADDRESS The DB2 ECCR found an invalid CPOOL cell address. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID CPOOL-ID IN CELL The DB2 ECCR found an invalid CPOOL ID in the cell. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. AREA TOO LARGE FOR CPOOL SERVICES The DB2 ECCR found an area that is too large for the CPOOL services. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID CHAIN OF CELL ELEMENTS The DB2 ECCR found an incorrect sequence of cell elements. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID CHAIN OF CELL ELEMENTS The DB2 ECCR found an incorrect sequence of cell elements. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
799
INTERNAL ERROR: INVALID CALL-FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: DUPLICATE HASH-ENTRIES The DB2 ECCR found duplicate entries in the hash table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: POSITION NOT ESTABLISHED The DB2 ECCR was attempting to do a GET NEXT operation amongst entries created by an internal hashing function but was unable to do so because no position had been previously established within the hashing entries. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM ACKNOWLEDGES AN MVS STOP COMMAND The DB2 ECCR issues this message to acknowledge the MVS STOP command you entered. The DB2 ECCR stops. No action is required. CAPTURE PROGRAM ACKNOWLEDGES AN MVS 'MODIFY REFRESH' COMMAND The DB2 ECCR issues this message to acknowledge that you issued a MVS MODIFY job,REFRESH command. This command causes the DB2 ECCR to update its control information based on the contents of the repository. The DB2 ECCR refreshes its control information based on the contents of the repository. No action is required. CAPTURE PROGRAM ACKNOWLEDGES A QUIESCE COMMAND The DB2 ECCR displays this message to acknowledge receipt of the QUIESCE or QU command you entered. T he DB2 ECCR enters a quiesced state. No action is required. QEDIT MACRO FAILED An internal error caused the QEDIT macro to fail. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
800
QEDIT MACRO FAILED An internal error caused the QEDIT macro to fail. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - UNEXPECTED VALUE IN R2PMOD FIELD The DB2 ECCR found an incorrect value in the R2PMOD field. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNSUPPORTED MVS COMMAND You issued an MVS command that the DB2 ECCR does not support. You might have entered the command incorrectly. The DB2 ECCR ignores the command and continues processing. Enter a valid command that the DB2 ECCR supports. For a list of the MVS commands that the DB2 ECCR supports, see the PowerExchange CDC Guide for z/OS. PARAMETER ON MODIFY COMMAND IS MISSING You entered an MVS MODIFY command without all of the necessary parameters. The DB2 ECCR ignores the MODIFY command and continues processing. Reenter the MVS MODIFY command with all of the required parameters. PARAMETER ON MODIFY COMMAND IS TOO SHORT You entered an MVS MODIFY command with an incomplete parameter. The DB2 ECCR ignores the MODIFY command and continues processing. Reenter the MVS MODIFY command with the correct parameter. PARAMETER ON MODIFY COMMAND IS TOO LONG You entered an MVS MODIFY command with an incorrect parameter. The parameter contains extra data. The DB2 ECCR ignores the MODIFY command and continues processing. Reenter the MVS MODIFY command with the correct parameter. SUPPORTED PARMS FOR MODIFY COMMAND ARE 'RE', 'DI', 'URID', 'TERM', AND 'QU' You issued an MVS MODIFY command with an invalid parameter. The DB2 ECCR ignores the MODIFY command and continues processing. Reenter the MVS MODIFY command with the correct parameter. For information on the supported parameters, see the PowerExchange Command Reference. 1ST PARAMETER OF MODIFY COMMAND IS INVALID OR NOT FOLLOWED BY A COMMA You issued an MVS MODIFY command in which the first parameter was invalid or was not followed by a comma. The DB2 ECCR ignores the MODIFY command and continues processing.
PWXEDM177053E Explanation: System Action: User Response: PWXEDM177054E Explanation: System Action: User Response: PWXEDM177055E Explanation: System Action: User Response: PWXEDM177056E Explanation: System Action: User Response:
User Response:
Reenter the MVS MODIFY command with the correct parameter. For information on the supported parameters, see the PowerExchange Command Reference. 'DISPLAY' PARAMETER IS FOLLOWED BY ONE OR MULTIPLE INVALID PARAMETER You issued an MVS MODIFY command in which the DISPLAY or DI parameter was followed by one or more unsupported parameters. The DB2 ECCR ignores the MODIFY command and continues processing. Enter the MVS MODIFY command with the correct parameter. 'TERM' PARAMETER IS INVALID, MUST BE A 12 CHARACTER HEXADECIMAL NUMBER You entered an invalid unit-of-recovery ID (URID) or unit-of-work ID (UOWID) for the TERM command. You must enter the command as TERM,<number>, where <number> represents a 12-digit, hexadecimal number that identifies a UR (or UOW). For example, TERM,00123AB0C000 The DB2 ECCR ignores the TERM command. Enter the TERM command again using the correct command syntax. For more information about the TERM parameter, see the PowerExchange Command Reference. INTERNAL ERROR: RELEASE FUNCTION NOT PERMITTED The DB2 ECCR storage release function attempted to release storage used by an internal hashing function but could not do so for one of the following reasons:

The subpool that was used when the hashing environment was established was zero The storage release function detected that some of the entries in the hashing environment were still in use
The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM NOT READY TO PROCESS MODIFY COMMANDS You entered an MVS MODIFY command. The current status of the DB2 ECCR does not allow processing of the MODIFY commands. The DB2 ECCR ignores the MODIFY command and continues processing. Reenter the MODIFY command later when the DB2 ECCR can process it.
PWXEDM177062W CAPTURE PROGRAM WAITING FOR DB2 CONNECTION Explanation: System Action: User Response: The DB2 ECCR is waiting for the connection to DB2 to complete; therefore, it cannot process the command. The DB2 ECCR ignores the command and waits for the connection to DB2 to complete. If the connection to DB2 takes an excessive amount of time to complete, you need to determine the cause of the delay. Otherwise, wait until the connection is complete, and enter the command again.
PWXEDM177064W CAPTURE PROGRAM IN START PHASE Explanation: System Action: User Response: The DB2 ECCR has not completed the initialization phase; therefore, it cannot process the command. The DB2 ECCR ignores the command. Reenter the command after the DB2 ECCR completes the initialization phase.
802
PWXEDM177065W CAPTURE PROGRAM IN COLD-START PHASE Explanation: System Action: User Response: The DB2 ECCR has not completed the cold-start process; therefore, it cannot process the command. The DB2 ECCR ignores the command. Reenter the command after the DB2 ECCR completes the cold-start process.
PWXEDM177066W CAPTURE PROGRAM IN SPECIAL START PHASE Explanation: System Action: User Response: PWXEDM177067E Explanation: System Action: User Response: PWXEDM177068E Explanation: System Action: User Response: The DB2 ECCR has not completed the special-start process; therefore, it cannot process the command. The DB2 ECCR ignores the command. Reenter the command after the DB2 ECCR completes the special-start process. CAPTURE PROGRAM IN REFRESH PHASE The DB2 ECCR has not completed the refresh process; therefore, it cannot process the command. The DB2 ECCR ignores the command. Reenter the command after the DB2 ECCR completes the refresh process. MODIFY COMMAND REJECTED The DB2 ECCR rejected an MVS MODIFY command. The DB2 ECCR ignores the MODIFY command. Check the other messages associated with this error to determine why the DB2 ECCR rejected the MODIFY command. Then, correct the problem, and enter the MODIFY command again. UNEXPECTED RETURN CODE FROM 'ENQ' MACRO - RC IS IN R8 The ENQ macro sent a nonzero return code to the DB2 ECCR. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM WITH NAME=name IS ALREADY EXECUTING You started the specified DB2 ECCR when a DB2 ECCR with the same name is already running. You cannot run more than one DB2 ECCR with the same name. If you need to run multiple DB2 ECCRs at the same time, they must have different names. The second DB2 ECCR with the same name abends. If you need to run multiple DB2 ECCRs in parallel, assign a different name to each DB2 ECCR. Specify the name of the DB2 ECCR in the NAME= keyword parameter of the CA control record in the //REPL2CTL file. Also, provide each DB2 ECCR running in parallel with a different capture directory table and a different DB2 plan. NBR OF TRACE-ELEMENTS IS INVALID The DB2 ECCR found an incorrect number of internal trace elements. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
803
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. LENGTH OF TEXT TO BE TRACED IS INVALID The DB2 ECCR found the length of text to be traced is invalid. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. LENGTH OF AREA TO BE TRACED IS INVALID The DB2 ECCR found the length of the area to be traced is invalid. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. OPEN-FAILURE FOR //REPL2CTL The DB2 ECCR could not open the //REPL2CTL file. The DB2 ECCR abends. To determine the cause of the error, check for other MVS issued error messages that contain additional information about the error. Then, correct the problem, and run the job again. //REPL2CTL FILE IS EMPTY The DB2 ECCR //REPL2CTL file does not contain the required control records. The DB2 ECCR abends. Add the required control cards to the //REPL2CTL file, and run the job again. For information about the required control cards, see the PowerExchange Installation Guide. ERRORS IN //REPL2CTL RECORDS - SEE //REPL2PRT LIST FOR DETAILS The DB2 ECCR detected one or more errors in the control records in the //REPL2CTL file. The DB2 ECCR writes a detailed description of the errors in the //REPL2PRT file. The DB2 ECCR abends. Check the error messages in the //REPL2PRT file to determine the cause of the error, correct the problem, and run the job again. ZERO CR RECORDS IN //REPL2CTL FILE The //REPL2CTL file does not contain a CR control record. It must contain at least one CR control record. The DB2 ECCR abends. Provide at least one CR control record (and its associated RD and ST control records) in the //REPL2CTL file, and run the job again. ZERO CA OR CQ RECORDS IN //REPL2CTL FILE The //REPL2CTL file does not contain either a CA record or a CQ record or both.
804
The DB2 ECCR abends. Provide one CA record and one CQ record in the //REPL2CTL file, and run the job again. ST RECORD NOT SUPPORTED An ST record found in the //REPL2CTL file is not supported. The DB2 ECCR abends. To bypass the error, delete the ST record from the //REPL2CTL file. Then, start the DB2 ECCR again. INTERNAL ERROR: UNEXPECTED RECRTTYPE VALUE The DB2 ECCR found an incorrect RECRTTYPE value. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: UNEXPECTED RETURN FROM COLSUB SUBROUTINE The DB2 ECCR received an incorrect value from the COLSUB subroutine. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. OPEN OF //REPL2OPT HAS FAILED The DB2 ECCR could not open the //REPL2OPT file. The DB2 ECCR abends. To determine the cause of the error, check for other MVS issued error messages that contain a more detailed description of the error. Correct the problem, and run the job again. ERRORS IN //REPL2OPT RECORDS - SEE //REPL2PRT LIST FOR DETAILS The DB2 ECCR detected one or more errors in the control records in the //REPL2OPT file. The DB2 ECCR writes a detailed description of the errors in the //REPL2PRT file. The DB2 ECCR abends. To determine the cause of the error, see the error messages in the //REPL2PRT file. Correct the problem, and run the job again. STATISTICS OF CAPTURE PGM program_name AT=timestamp The specified DB2 ECCR is writing statistics at the specified date and time. Processing continues. No action is required. For more information about the statistics report displayed, see the PowerExchange Command Reference or the PowerExchange CDC Guide for z/OS. DETAIL-LEVEL STATISTICS FOLLOW BELOW The DB2 ECCR writes detailed statistics. Processing continues.
User Response:
No action is required. For more information about the statistics report displayed, see the PowerExchange Command Reference or the PowerExchange CDC Guide for z/OS. STCKCONV MACRO FAILED When the DB2 ECCR accessed it, the STCKCONV macro failed. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM ABENDS The DB2 ECCR abends because of an error that previous error messages describe. The DB2 ECCR abends. Check previous error messages for an explanation of the error. Correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE X029100 The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE X029100 The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
806
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends.
807
User Response:
Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - UNEXPECTED COLTYPE FOR A STRING DEFAULT VALUE The DB2 ECCR found an unexpected column type for a string default value. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
808
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - UNEXPECTED COLTYPE FOR A NUMERICAL DEFAULT VALUE The DB2 ECCR found an unexpected column type for a numeric default value. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - UNEXPECTED LENGTH FOR A GRAPHIC STRING DEFAULT VALUE The DB2 ECCR found an unexpected length for a graphic string default value. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODUL E module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend.
809
The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. T he DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODUL E module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends.

810
User Response:
Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name The DB2 ECCR found an invalid value in FUN2 for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
811
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. DB2/CAF CONNECT Error - RC/RSNC=rc/reason CN=connect_name The DB2 ECCR could not connect to DB2 using the DB2 Call Attach Facility (CAF), where connect_name is the name used to connect to DB2. DB2 and the CAF returned the return code rc and the reason code reason. The DB2 ECCR abends. For a description of the return code and reason code, see the IBM DB2 messages and codes manual. Correct the problem, and run the job again. SEE DB2 MESSAGES AND CODES FOR AN EXPLANATION OF THE RSNC The DB2 ECCR could not connect to DB2 using the DB2 Call Attach Facility (CAF). To provide additional information about the error, the DB2 ECCR issues both this message and PWXEDM177135E. The purpose of this message is to direct you to see IBM DB2 messages and codes manual for a description of the reason code in message PWXEDM177135E. The DB2 ECCR abends. See IBM DB2 messages and codes manual for a description of the reason code in message PWXEDM177135E. CAPTURE PROGRAM ABENDS Because it could not connect to DB2, the DB2 ECCR abends. The DB2 ECCR issues other messages with more detailed information prior to issuing this message. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. DB2/CAF OPEN ERROR - RC/RSNC=rc/reason The DB2 ECCR issued a DB2 Call Attach Facility (CAF) OPEN call. The OPEN call failed. CAF and DB2 provide the return code rc and the reason code reason. The DB2 ECCR abends. See IBM DB2 messages and codes manual for a description of the return code and reason code. If possible, use the contents of this message and any associated messages to determine the cause of the error. Then, correct the problem, and run the job again. If the problem
812
persists, collect all available information about the error. Contact Informatica Global Customer Support. PWXEDM177139I Explanation: SEE DB2 MESSAGES AND CODES FOR AN EXPLANATION OF THE RSNC The DB2 ECCR could not perform a DB2 Call Attach Facility (CAF) OPEN call. To provide additional information about the error, the DB2 ECCR issues both this message and PWXEDM177138E. The purpose of this message is to direct you to see IBM DB2 messages and codes manual for a description of the reason code in message PWXEDM177138E. The DB2 ECCR abends. See IBM DB2 messages and codes manual for a description of the reason code in message PWXEDM177135E. CAPTURE PROGRAM ABENDS Because its DB2 Call Attach Facility OPEN call failed, the DB2 ECCR abends. The DB2 ECCR issues other messages with more detailed information prior to issuing this message. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. CAPTURE PGM CAN NOT OBTAIN THE ID OF THE CURRENT DB2 SERVER The DB2 ECCR could not obtain the identification of the current DB2 server. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. SQL ERROR FOR SET:CS=CURRENT SERVER The DB2 ECCR could not obtain the identification of the current DB2 server. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. ERROR IN DB2 COMMIT PROCESSING The DB2 ECCR could not execute a DB2 COMMIT command. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. ERROR IN DB2 ROLLBACK PROCESSING The DB2 ECCR could not perform a DB2 rollback process. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again.
813
ROLL-BACK FAILED The DB2 ECCR could not perform a DB2 rollback process. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. COMMIT PROCESSING FAILED The DB2 ECCR could not execute a DB2 COMMIT command. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. ACCESS TO TCAPRESTART FAILED As part of its COMMIT command processing, the DB2 ECCR could not update the TCAPRESTART table. The DB2 ECCR issues other messages with more detailed information about this error. The DB2 ECCR abends. To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again. MQPUT INTO SELF-ADDRESSED QUEUE FAILED The MQPUT function for a self-addressed queue failed. This is an internal error of the DB2 ECCR. The DB2 ECCR abends. Contact Informatica Global Customer Support. DB2 CAPTURE PERFORMS A ROLL-BACK For reasons described in previous messages, the DB2 ECCR is performing a DB2 rollback process. Processing continues. No action is required. ISSUING AN SQL ROLLBACK For reasons described in previous messages, the DB2 ECCR issued a DB2 rollback process request. Processing continues. No action is required. DB2 Vv.r.m is not supported. The minimum supported level is Vv.r.m. PowerExchange does not support your DB2 release level. This message shows the minimum supported DB2 release level by the PowerExchange product. The DB2 ECCR abends. Contact Informatica Global Customer Support.
PWXEDM177148E Explanation: System Action: User Response: PWXEDM177149I Explanation: System Action: User Response: PWXEDM177151I Explanation: System Action: User Response: PWXEDM177152E Explanation: System Action: User Response:
814
DB2 Vv.r.m is not supported. The {minimum|maximum} supported level is Vv.r.m. PowerExchange does not support your DB2 release level. If the DB2 release level is too old, this message shows the minimum DB2 release level supported by PowerExchange. If the DB2 release level is too new, this message shows the maximum DB2 release level supported by PowerExchange. The DB2 ECCR abends. Contact Informatica Global Customer Support. DB2/CAF OPEN ERROR - RC/RSNC=rc/reason A subtask of the DB2 ECCR issued a DB2 Call Attach Facility (CAF) OPEN call. The OPEN call failed. CAF and DB2 pass a return code and a reason code to the DB2 ECCR. The DB2 ECCR abends. See IBM DB2 messages and codes manual for a description of the return code and reason code. If possible, use the contents of this message and any associated messages to determine the cause of the error. Then, correct the problem, and run the job again. If the problem persists, call Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. LOG BUFFER-FLUSHING SUBTASK ABENDS A DB2 ECCR subtask is abending. The subtask abends. Use the information contained in other messages associated with this error to determine the cause of the error. Then, correct the problem, and run the job again. LOG BUFFER-FLUSHING SUBTASK ABENDS A DB2 ECCR subtask is abending. The subtask abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. SEE DB2 MESSAGES AND CODES FOR AN EXPLANATION OF THE RSNC A DB2 ECCR subtask encountered a DB2 related problem. The subtask abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. LOG BUFFER-FLUSHING SUBTASK ABENDS A DB2 ECCR subtask is abending. The subtask abends. Use the information that other messages associated with this error to determine the cause of the error. Then, correct the problem, and run the job again.
815
INTERNAL ERROR: CONSTANT TO BE CONVERTED IS TOO LONG The DB2 environmental change capture routine (ECCR) found a constant that is too long to convert. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: X029166 IS CALLED FOR AN UN-EXPECTED CONVERSION TYPE The DB2 ECCR found an incorrect conversion type. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SQL ERROR: OPERATION=operation TABLE=table The specified DB2 ECCR SQL operation encountered an error when working with the specified table. DB2 ECCR processing continues. However, in some situations, the columns you defined using user defined default values may not get replicated with those default values. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. SQL-ERROR WHILE ATTEMPTING TO CONVERT A USER-PROVIDED DEFAULT VALUE The DB2 ECCR encountered an error in an SQL statement that converts a user defined default value from an external format to an internal format. See message PWXEDM177171E for additional information about this error. DB2 ECCR processing continues. However, in some situations, the columns you defined using user defined default values might not get replicated with those default values. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: LOG POSITION DOES NOT EXIST The DB2 ECCR attempted to locate a nonexistent log position. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNACCEPTABLE RETURN CODE FROM X029172 The DB2 ECCR internal module X029172 issued an incorrect return code.
816
The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. 1ST SEGMENT OF A MULTI-SEGMENT DB2 LOG RECORD IS MISSING While processing a multi-segment DB2 log record, the DB2 ECCR read a log record segment that was greater than or equal to the second log record segment without reading the first log record segment. Possibly, the DB2 log is corrupt or the DB2 ECCR has a logic error. The message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. EXPECTED LAST SEGMENT OF A MULTI-SEGMENT DB2 LOG RECORD IS MISSING While processing the DB2 log, the DB2 ECCR could not find the last segment of a multi-segment DB2 log record. Possibly, the DB2 log is corrupt or the DB2 ECCR has a logic error. The message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED ERROR ATTEMPTING TO READ 1ST RECORD OF ACTIVE DB2 LOG While processing the DB2 log, the DB2 ECCR encountered an error. Possibly, the DB2 log is corrupt, or the DB2 ECCR has a logic error. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: LOG POSITION DOES NOT EXIST The DB2 ECCR attempted to locate a nonexistent log position. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNACCEPTABLE RETURN CODE FROM X029174 The DB2 ECCR internal module X029174 issued an incorrect return code. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
817
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: LOG POSITION DOES NOT EXIST The DB2 ECCR attempted to locate a nonexistent log position. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNACCEPTABLE RETURN CODE FROM X029175 The DB2 ECCR internal module X029175 issued an incorrect return code. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ACCESS TO FIRST LOG RECORD OF ACTIVE LOG FAILED AFTER 4 RETRIES The DB2 ECCR could not read the first log record of the active DB2 log with an instrumentation facility interface (IFI) READS command during four consecutive attempts. The DB2 ECCR repeated the following steps four times: 1. The DB2 ECCR issued a call to DB2 to perform an IFI READS command on the first log record in the active log. The IFI READS reported that the requested log RBA was not in the active log and returned a new RBA for the first log control interval (CI) of the active log. 2. The DB2 ECCR attempted to read the log CI located at this RBA. The read attempt failed. After the fourth attempt, the DB2 ECCR abends.
System Action:
User Response:
Collect all available information about the error.Then, contact Informatica Global Customer Support. ACCESS TO FIRST LOG RECORD OF ACTIVE LOG FAILED The DB2 ECCR cannot access the first log record of the active log. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
818
UNACCEPTABLE RETURN CODE FROM X029176 The DB2 ECCR internal module X029176 issued an incorrect return code. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: LOG POSITION DOES NOT EXIST The DB2 ECCR attempted to locate a nonexistent log position. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DB2 LOG CI CONTAINS A RECORD WITH A INVALID RECORD LENGTH While processing the DB2 log, the DB2 ECCR read a DB2 log record that has an invalid record length. Possibly, the DB2 log is corrupt, or the DB2 ECCR has a logic error. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. RBA IS NOT THE RBA OF A DB2 LOG RECORD; OR LOG CI IS NOT CORRECT' The DB2 ECCR detected an error in the DB2 log CI when validating the DB2 log control interval (CI) format in the DB2 log. Possibly, the DB2 log is corrupt, or the DB2 ECCR has a logic error. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. OFFSET TO LAST LOG_RECORD WITHIN LOG CI IS NOT CORRECT The DB2 ECCR detected an error in the DB2 log CI when validating the DB2 log control interval (CI) format in the DB2 log. Possibly, the DB2 log is corrupt, or the DB2 ECCR has a logic error. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
819
INTERNAL ERROR: LOG POSITION IS NOT SET The DB2 ECCR cannot determine where to start reading from the log because a log starting position is not set. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR OF LOG READ MODULES The DB2 ECCR encountered an internal error while using the log read modules. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177196W TRACE(MONITOR) CLASS(1) IS INACTIVE Explanation: The DB2 ECCR issued an IFCID 306 READS call, but received reason code x'00E60832', which indicates that the IFCID required for the READS call is not active. This is activated when the DB2 ECCR initializes, when it issues a DB2 command 'START MONITOR(TRACE) CLASS(1)'. However, it is possible to issue a DB2 command to stop the trace. When the DB2 ECCR detects this condition, it issues this message and then restarts the trace. No response is required., because the DB2 ECCR will restart the required trace. If the trace cannot be restarted, the DB2 ECCR will abend.
PWXEDM177198W PROPER DB2 AUTHORIZATION MISSING TO READ DB2 LOG WITH IFI READS CALLS Explanation: The DB2 ECCR cannot read the DB2 log. Possibly, the DB2 ECCR does not have the DB2 privileges it requires to issue calls to read the DB2 log using the IFI READS commands. The DB2 ECCR abends. Grant the MONITOR2 privilege to the DB2 authorization ID used for the DB2 ECCR. Then, run the job again. INTERNAL ERROR: IFI CALL WITH WQALMODF ISSUED WITHOUT RELEASING PREVIOUS POSITION The DB2 ECCR encountered an internal error. Possibly, the DB2 ECCR issued an incorrect sequence of IFI READS calls when reading the DB2 log. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: IFI CALL WITH WQALMODN ISSUED WITHOUT HAVING AN IFI POSITION The DB2 ECCR encountered an internal error. Possibly, the DB2 ECCR issued an incorrect sequence of IFI READS calls when reading the DB2 log. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
820
INTERNAL ERROR: UNEXPECTED IFI REASON CODE IN IFCA FOR COMPRESSED DATA While the DB2 ECCR was issuing calls to read the DB2 log with DB2 instrumentation facility interface (IFI) READS commands, the IFI returned an unexpected reason code in the IFCA. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. RETRIES OF IFI READS CALL NOT SUCCESSFUL The DB2 ECCR could not read the DB2 logs with calls that used the DB2 IFI READS commands. The return code and reason code from IFI indicated that the DB2 ECCR needed to retry the IFI READS command, but the retries were not successful. This error is either a DB2 error or a DB2 ECCR logic error. The DB2 ECCR abends. Collect all available information about the error. Then, contact Informatica Global Customer Support. ERROR WHILE ATTEMPTING TO READ AN ACTIVE DB2 LOG The DB2 ECCR encountered an error while processing an active DB2 log. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED SPANNED IFI RECORD While reading the active DB2 log with a DB2 IFI READS command, the DB2 ECCR encountered a spanned IFI record. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED LENGTH OF IFI RECORD While reading the active DB2 log with a DB2 IFI READS command, the DB2 ECCR found an IFI record with an incorrect length. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED NBR OF IFI DATA SECTIONS While reading the active DB2 log with a DB2 IFI READS command, the DB2 ECCR encountered an IFI record with an incorrect number of data sections. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue.
821
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED OFFSET IN IFI SELF DEFINING SECTION While reading the active DB2 log with an IFI READS command, the DB2 ECCR found an incorrect offset in the IFI self-defining section. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED LENGTH IN IFI SELF DEFINING SECTION While reading the active DB2 log with an IFI READS command, the DB2 ECCR found an incorrect length in the IFI self-defining section. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RBA VALUE IN DB2 LCID While reading the active DB2 log with a DB2 IFI READS command, the DB2 ECCR encountered an incorrect RBA value in the DB2 log control interval definition (LCID) located at the end of the log control intervals (CI). Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. IFI RC=0 WITH IFCABM=0 A DB2 instrumentation facility interface (IFI) command failed with a return code of 0 and an IFCABM field value of 0. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ERROR WHILE READING DB2 LOG - IFI RC/RSNC=rc/reason The DB2 ECCR cannot read a record from the active DB2 log using the instrumentation facility interface (IFI) READS command. The IFI READS command returned the return code rc and the reason code reason. The return code and reason code are described in IBM DB2 messages and codes manual. If you did not provide an EC control record in the //REPL2CTL file, the DB2 ECCR abends. Otherwise, the DB2 ECCR may either abend or attempt to continue. Use the description of the IFI return code and reason code in IBM DB2 messages and codes manual to determine the cause of the error. Then, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
822
INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: LOG POSITION IS NOT SET The DB2 ECCR cannot determine where to start reading from the log because a log starting position is not set. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR OF LOG READ MODULES The DB2 ECCR encountered an internal error while using the log read modules. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177215W TRACE (MONITOR) CLASS(1) INACTIVE Explanation: System Action: User Response: The DB2 ECCR cannot read the DB2 logs. Possibly, you did not start the DB2 TRACE for MONITOR CLASS 1. The DB2 ECCR abends. Issue the DB2 command START TRACE (MONITOR) CLASS(1).
PWXEDM177216W PROPER DB2 AUTHORIZATION MISSING TO READ DB2 LOG WITH IFI READS CALLS Explanation: The DB2 ECCR cannot read the active DB2 log. Possibly, the DB2 ECCR does not have the DB2 privileges it requires to issue calls to read the DB2 log using the IFI READS commands. The DB2 ECCR abends. Grant the MONITOR2 privilege to the DB2 authorization ID used by the DB2 ECCR. Then, run the job again. RETRIES OF IFI READS CALL NOT SUCESSFULL The DB2 ECCR cannot read the DB2 logs with calls that use the DB2 IFI READS commands. The return code and reason code from IFI indicated that the DB2 ECCR needed to reissue the IFI READS command; however, the subsequent attempts were not successful. This error is either a DB2 error, or a DB2 ECCR logic error. The DB2 ECCR abends. Collect all available information about the error. Then, contact Informatica Global Customer Support. UNACCEPTABLE ERROR WHILE ACCESSING AN ACTIVE DB2 LOG The DB2 ECCR encountered an error while reading an active DB2 log. The DB2 ECCR abends.
823
User Response:
Collect all available information about the error, including the output from the JES log and the //REPL2PRT, //REPL2TRA, //REPL2TRU, and //SYSUDUMP files. Then, contact Informatica Global Customer Support. ERROR WHILE READING AN ARCHIVED DB2 LOG The DB2 ECCR encountered an error while reading an archived DB2 log. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED END OF DATA IN ARCHIVED LOGS The DB2 ECCR found an incorrect end-of-data condition while reading an archived log. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. PROBABLY A DYNAMIC ALLOCATION FAILURE FOR AN ARCHIVED LOG DATASET The DB2 ECCR could not read an archived DB2 log with the DB2 DSNJSLR macro services. According to information provided by the DSNJSLR macro, the most probable cause is an archived log data set dynamic allocation failure. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. ERROR WHILE ACCESSING DB2 LOG - DSNJSLR FUNC=function_name RC/RSNC=rc/reason The DB2 ECCR could not read an archived DB2 log with the DB2 DSNJSLR macro services. The DB2 ECCR requested the DSNJSLR function function_name. The DB2 DSNJSLR service function returned the return code rc and the reason code reason. The return code and reason code are described in IBM DB2 messages and codes manual. The DB2 ECCR abends. To determine the cause of the error, check IBM DB2 messages and codes manual for an explanation of the return and reason codes. Correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
SLRFRC=slrfrc SLRFINFO=slrinfo SLRFERCD=slrfercd SLRFRG15=r15 The DB2 ECCR cannot read an archived DB2 log using the DB2 DSNJSLR macro services. This message displays the feedback information the DSNJSLR macro stores in the DB2 stand-alone log GET feedback area. The feedback area, which the DSNDSLRF macro created and mapped, holds the contents of the following fields:

SLRFRC SLRFINFO SLRFERCD SLRFRG15 System Action: The DB2 ECCR abends.
824
User Response:
To determine the cause of the error, check IBM's DB2 system administration guide for explanations of the contents of these fields. Also, check for other messages associated with this error. If you can, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
SLRFDDNM=slrfddnm SLRFRBA=slrfrba The DB2 ECCR cannot read an archived DB2 log using the DB2 DSNJSLR macro services. This message displays the feedback information the DSNJSLR macro stores in the DB2 stand-alone log GET feedback area. The feedback area, which the DSNDSLRF macro created and mapped, holds the contents of the following fields: SLRFDDNM SLRFRBA The DB2 ECCR abends. To determine the cause of the error, check IBM's DB2 system administration guide for explanations of the contents of these fields. Also, check for other messages associated with this error. If you can, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
Explanation: Explanation: System Action: User Response:
SEE DB2 MESSAGES AND CODES FOR A DESCRIPTION OF THE RSNC= The DB2 ECCR could not read an archived DB2 log using the DB2 DSNJSLR macro services. The DB2 ECCR issued a prior message that includes the reason code the DB2 DSNJSLR macro service returned. The DB2 ECCR issues this message to remind you to look in IBM DB2 messages and codes manual for the description of that reason code. Processing continues. See IBM DB2 messages and codes manual for an explanation of the reason code. ACCESSING LOG POSITION=rba IN ARCHIVED LOG The DB2 ECCR is preparing to read DB2 log records contained in an archived DB2 log. This message displays the log RBA the DB2 ECCR is accessing in the archived DB2 log. Processing continues. No action is required. ARCHIVED LOG PROCESSING COMPLETED The DB2 ECCR is changing from reading an archived DB2 log to reading an active DB2 log. Restart processing has processed all of the log records for tables that were specified as active when the restart began. Processing continues. No action is required. INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
825
INTERNAL ERROR: LOG POSITION IS NOT SET The DB2 ECCR cannot determine where to start reading from the log because a log starting position is not set. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR OF LOG READ MODULES The DB2 ECCR encountered an internal error while using the log read modules. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RBA VALUE IN DB2 LCID While reading an archived log, the DB2 ECCR encountered an unexpected RBA value in the DB2 log control interval definition (LCID) located at the end of the log control intervals. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR OF LOG READ MODULES The DB2 ECCR encountered an internal error while using the log read modules. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ...PROBABLY ARCHIVED LOGS ARE NOT PROVIDED PROPERLY TO CAPTURE PROGRAM The DB2 ECCR encountered errors while reading log records from an archived DB2 log. After reading a log control interval (CI), the DB2 ECCR detected that the log control interval RBA located at the end of the log CI had a different value. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNACCEPTABLE ERROR WHILE ACCESSING AN ARCHIVED DB2 LOG The DB2 ECCR encountered an error while reading an archived DB2 log. The DB2 ECCR abends. To determine the cause of the error, check other messages associated with this error for more detailed information about the error. Then, correct the problem, and run the job again. PROBABLY A DYNAMIC ALLOCATION FAILURE FOR AN ARCHIVED LOG DATA SET The DB2 ECCR could not read an archived DB2 log with the DB2 DSNJSLR macro services. The most probable cause is a dynamic allocation failure for an archived log data set. Another cause might be that the ECCR could not find the appropriate data set.
826
The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. ERROR WHILE ACCESSING DB2 LOG-DSNJSLR FUNC=function_name, RC/RSNC=rc/reason The DB2 ECCR could not read an archived DB2 log with the DB2 DSNJSLR macro services. The DB2 ECCR requested the DSNJSLR function function_name. The DB2 DSNJSLR service function returned the return code rc and the reason code reason. The return code and reason code are described in IBM DB2 messages and codes manual. The DB2 ECCR abends. To determine the cause of the error, check IBM DB2 messages and codes manual for an explanation of the return and reason codes. Correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
SLRFRC=slrfrc SLRFINFO=slrinfo SLRFERCD=slrfercd SLRFRG15=r15 The DB2 ECCR cannot read an archived DB2 log using the DB2 DSNJSLR macro services. This message displays the feedback information the DSNJSLR macro stores in the DB2 stand-alone log GET feedback area. The feedback area, which the DSNDSLRF macro created and mapped, holds the contents of the following fields:

SLRFRC SLRFINFO SLRFERCD SLRFRG15 System Action: User Response: The DB2 ECCR abends. To determine the cause of the error, check IBM's DB2 system administration guide for explanations of the contents of these fields. Also, check for other messages associated with this error. If you can, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. PWXEDM177238E Explanation: SLRFDDNM=slrfddnm SLRFRBA=slrfrba The DB2 ECCR cannot read an archived DB2 log using the DB2 DSNJSLR macro services. This message displays the feedback information the DSNJSLR macro stores in the DB2 stand-alone log GET feedback area. The feedback area, which the DSNDSLRF macro created and mapped, holds the contents of the following fields:

SLRFDDNM SLRFRBA
The DB2 ECCR abends. To determine the cause of the error, check IBM's DB2 system administration guide for explanations of the contents of these fields. Also, check for other messages associated with this error. If you can, correct the problem, and run the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
SEE DB2 MESSAGES AND CODES FOR A DESCRIPTION OF THE RSNC= The DB2 ECCR could not read an archived DB2 log using the DB2 DSNJSLR macro services. The DB2 ECCR issued a prior message that includes the reason code the DB2
827
DSNJSLR macro service returned. The DB2 ECCR issues this message to remind you to look in IBM DB2 messages and codes manual for the description of that reason code. System Action: User Response: PWXEDM177240I Explanation: System Action: User Response: PWXEDM177241I Explanation: Processing continues. See IBM DB2 messages and codes manual for an explanation of the reason code. ACCESSING LOG POSITION=rba IN ARCHIVED LOG The DB2 ECCR is preparing to read DB2 log records contained in an archived DB2 log. This message displays the log RBA the DB2 ECCR is accessing in the archived DB2 log. Processing continues. No action is required. ARCHIVED LOG PROCESSING COMPLETED The DB2 ECCR is changing from reading an archived DB2 log to reading an active DB2 log. Restart processing has processed all of the log records for tables that were specified as active when the restart began. Processing continues. No action is required. INTERNAL ERROR: INVALID CALL FUNCTION The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: LOG POSITION IS NOT SET The DB2 ECCR cannot determine where to start reading from the log because a log starting position is not set. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR OF LOG READ MODULES The DB2 ECCR encountered an internal error while using the log read modules. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR OF LOG READ MODULES The DB2 ECCR encountered an internal error while using the log read modules. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
828
...PROBABLY ARCHIVED LOGS ARE NOT PROVIDED PROPERLY TO CAPTURE PROGRAM The DB2 ECCR encountered errors while reading log records from an archived DB2 log. After reading a log control interval (CI), the DB2 ECCR detected that the log control interval RBA located at the end of the log CI had a different value. Message PWXEDM177030E describes whether the DB2 ECCR abends or attempts to continue. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED EYE-CATCHER IN R2PMAIN The R2PMAIN control block is incorrectly initialized. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. QEDIT MACRO FAILED The QEDIT macro to failed because an internal error occurred. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. QEDIT MACRO FAILED The QEDIT macro to failed because an internal error occurred. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. COLD-START WAS ABORTED BY OPERATORS The DB2 ECCR determined that it needed to perform a cold start. Before starting the cold start process, the DB2 ECCR asked you to confirm the need for a cold start. You decided to cancel (or terminate) this DB2 ECCR. The DB2 ECCR abends. No action is required. UNEXPECTED RETURN CODE FROM X029110 The specified module sent an unexpected return code to the DB2 ECCR. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ROLLBACK HAS FAILED The DB2 ECCR issued a rollback request, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again.
INTERNAL ERROR The DB2 ECCR encountered an unspecified internal error that caused the program to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ACCESS TO TCAPRESTART TABLE FAILED The DB2 ECCR could not access the TCAPRESTART table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. UNEXPECTED EYE-CATCHER IN DSNHDECP The DSNHDECP control block is incorrectly initialized. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. SPECIAL-START WAS ABORTED BY OPERATORS A START STARTLOC control record in the //REPL2OPT file requested a special start of the DB2 ECCR. Before starting the special-start process, the DB2 ECCR asked you to confirm the special-start request. You decided to cancel or terminate the DB2 ECCR. The DB2 ECCR abends. No action is required. UNEXPECTED RC IN R15 FROM ESTAE SETUP The DB2 ECCR received an unexpected return code from the MVS ESTAE macro. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM OF DB2 REPLICATION ENDING BECAUSE OF STOP COMMAND You issued an MVS STOP command to stop the DB2 ECCR. The DB2 ECCR stops. No action is required.
PWXEDM177259W WAITING ON DB2 CONNECTION Explanation: System Action: User Response: PWXEDM177260I Explanation: The DB2 ECCR could not connect to DB2. Probably, the DB2 is not started. The DB2 ECCR periodically attempts to connect to DB2. If appropriate, start DB2. BEGIN OF WARM-START PROCESSING The DB2 ECCR begins the warm-start process.
830
System Action: User Response: PWXEDM177261A Explanation:
Processing continues. No action is required. CONFIRM COLD-START OF CAPTURE PROGRAM OF DB2 REPLICATION: ANSWER 'OK' OR 'CANCEL' The DB2 ECCR determined that it needed to perform a cold start. Before starting the cold-start process, the DB2 ECCR displays this message to ask you to confirm the need for a cold start. Depending on your answer, the DB2 ECCR either proceeds with the cold-start process or abends. Click OK to confirm the cold-start request or CANCEL to terminate the DB2 ECCR. ANSWER TO MESSAGE PWXEDM177261A WAS INVALID You entered an incorrect answer to message PWXEDM177261A. The DB2 ECCR issues message PWXEDM177261A again. Enter a correct response to message PWXEDM177261A. CONFIRM SPECIAL-START OF CAPTURE PROGRAM OF DB2 REPLICATION: ANSWER 'OK' OR 'CANCEL' The //REPL2OPT file contains a START STARTLOC control record that requests a special start of the DB2 ECCR. Before starting the special-start process, the DB2 ECCR asks you to confirm the special-start request. Depending on your answer, the DB2 ECCR either proceeds with the cold-start process or abends. Click OK to confirm the cold-start request or CANCEL to terminate the DB2 ECCR. ANSWER TO MESSAGE PWXEDM177263A WAS INVALID You entered an incorrect answer to message PWXEDM177263A. The DB2 ECCR issues message PWXEDM177263A again. Enter a correct response to message PWXEDM177263A. PROCESSING IS COMPLETE The DB2 ECCR completed its processing. The DB2 ECCR ends. No action is required. SKIPPING FROM LOG-LOC rba TO LOC rba The DB2 ECCR detected a gap in the log data set while sequentially processing the DB2 log. Because of the gap, the DB2 ECCR is skipping from the first log RBA to the second log RBA. The DB2 ECCR attempts to continue. Determine why the DB2 log has a gap. Ensure that all log records needed for this change propagation are available. Also ensure that consistency between the primary (source) tables and the replicate (target) tables exists. If required, repopulate the replicate (target) tables. STARTING AT DB2 LOG LOCATION=location The DB2 ECCR started processing the DB2 log at the specified location.
System Action: User Response: PWXEDM177262E Explanation: System Action: User Response: PWXEDM177263A Explanation:
System Action: User Response: PWXEDM177264E Explanation: System Action: User Response: PWXEDM177265I Explanation: System Action: User Response: PWXEDM177266E Explanation:
831
Processing continues. No action is required. LAST READ DB2 LOG LOCATION=location/DB2 memberid The value of the variable location identifies the last DB2 log record the DB2 ECCR processed during the last successful COMMIT. Processing continues. No action is required. UNEXPECTED RETURN CODE FROM X029240 The specified module sent an unexpected return code to module X029201. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RETURN CODE FROM X029260 The specified module sent an unexpected return code to module X02901. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RETURN CODE FROM X029270 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access the capture directory table. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR issued a rollback request, and the DB2 rollback failed. The DB2 ECCR abends. Use the information that other messages associated with this error provide to determine the cause of the error. Then, correct the problem, and run the job again. UNEXPECTED RETURN CODE FROM LOG-READ FUNCTION The DB2 ECCR received an unexpected return code from the specified function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
832
User Response:
Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM OF DB2 REPLICATION ENDING BECAUSE DB2 IS STOPPING The DB2 ECCR detected that DB2 is ending. The DB2 ECCR stops. No action is required. CAPTURE PROGRAM OF DB2 REPLICATION ENDING BECAUSE OF A 'STOP CAPT' NOTIFICATION The event notification software wrote to the DB2 log a record that contains a STOP CAPTURE request for the DB2 ECCR. The DB2 ECCR has read that record and has stopped capturing changed data. The DB2 ECCR stops. No action is required. CAPTURE PROGRAM OF DB2 REPLICATION STOPPING AT THE 'STOPAFT' LOCATION The DB2 ECCR reached the DB2 log location identified in a STOPAFT control record in the //REPL2CTL file. The DB2 ECCR stops capturing changed data after it process that record. The DB2 ECCR stops. No action is required. CAPTURE PROGRAM OF DB2 REPLICATION ENDING BECAUSE OF MVS STOP COMMAND You issued an MVS STOP command to stop the DB2 ECCR. The DB2 ECCR stops. No action is required. CAPTURE PROGRAM OF DB2 REPLICATION ENDING BECAUSE OF CAPTURE QUIESCE COMMAND The DB2 ECCR is ending because you entered the QUIESCE (QU) command. The DB2 ECCR ends. No action is required. LOG POSITION BEFORE REFRESH PROCESSING FOLLOWS You issued an MVS MODIFY jobname,REFRESH command for the DB2 ECCR. The next message describes where the DB2 ECCR is currently positioned within the DB2 log. The DB2 ECCR refreshes its control information based on the newest version of the //REPL2CTL and //REPL2OPT files. No action is required. BEGIN DB2 CAPTURE TERMINATION The DB2 ECCR is starting the termination process. The DB2 ECCR ends. No action is required.
System Action: User Response: PWXEDM177279I Explanation: System Action: User Response: PWXEDM177280I Explanation: System Action: User Response: PWXEDM177281I Explanation: System Action: User Response: PWXEDM177282I Explanation: System Action: User Response:
833
PWXEDM177283I Explanation: System Action: User Response: PWXEDM177284I Explanation: System Action: User Response: PWXEDM177285I Explanation: System Action: User Response: PWXEDM177286I Explanation: System Action: User Response: PWXEDM177287I Explanation: System Action: User Response: PWXEDM177288I Explanation: System Action: User Response: PWXEDM177289I Explanation: System Action: User Response: PWXEDM177290I Explanation: System Action: User Response: PWXEDM177291I Explanation: System Action:
BEGIN OF COLD START INITIALIZATION The DB2 ECCR is initializing using the cold start process. The DB2 ECCR issues additional messages as the initialization process proceeds through the various phases. The DB2 ECCR initializes. No action is required. BEGIN OF PHASE-0 OF COLDSTART The DB2 ECCR is starting phase 0 of the cold-start process. Processing continues. No action is required. BEGIN OF PHASE-1 OF COLDSTART The DB2 ECCR is starting phase 1 of the cold-start process. Processing continues. No action is required. START OF DIRECTORY CLEAN-UP The DB2 ECCR started cleaning up the capture directory tables. Processing continues. No action is required. DIRECTORY CLEAN-UP COMPLETE The DB2 ECCR has completed the capture directory tables cleaning up. Processing continues. No action is required. BEGIN OF PHASE-2 OF COLDSTART The DB2 ECCR is starting phase 2 of the cold-start process. Processing continues. No action is required. START OF ACCESS TO SYSTABLESPACE The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSTABLESPACE table. Processing continues. No action is required. ACCESS TO SYSTABLESPACE COMPLETE The DB2 ECCR finished accessing the DB2 catalog SYSIBM.SYSTABLESPACE table. Processing continues. No action is required. START OF ACCESS TO SYSTABLES The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSTABLES table. Processing continues.
834
User Response: PWXEDM177292I Explanation: System Action: User Response: PWXEDM177293I Explanation: System Action: User Response: PWXEDM177294I Explanation: System Action: User Response:
No action is required. ACCESS TO SYSTABLES COMPLETE The DB2 ECCR finished accessing the DB2 catalog SYSIBM.SYSTABLES table. Processing continues. No action is required. BEGIN OF PHASE-3 OF COLDSTART The DB2 ECCR is starting phase 3 of the cold-start process. Processing continues. No action is required. VERIFYING CONSISTENCY OF OBTAINED CATALOG DEFINITIONS The DB2 ECCR verifying the consistency of the obtained DB2 catalog definitions. Processing continues. No action is required.
PWXEDM177295W CATALOG DEFINITIONS HAVE CHANGED - RETRYING PHASE-2 PROCESSING Explanation: The DB2 catalog definitions, which the DB2 ECCR obtained, have changed between phase 2 and phase 3 of the cold start process. This error occurs when you have not bound all DB2 packages with the ISOLATION option. The DB2 ECCR repeats the phase 2 processing. This extra cycle takes additional time. For more information about the ISOLATION option and about which DB2 packages need to be bound, see the PowerExchange CDC Guide for z/OS. Ensure that you bind all DB2 packages that must be bound using the ISOLATION(RR) option. Then, run the job again. BEGIN OF PHASE-4 OF COLDSTART The DB2 ECCR is starting phase 4 of the cold-start process. Processing continues. No action is required. SEARCHING COLD-START TIMESTAMP IN DB2 LOG The DB2 ECCR is searching in the DB2 log for the record that identifies the cold-start timestamp. The cold-start timestamp is a log record written between phase 2 and phase 3 of the cold start process. Processing continues. No action is required. BEGIN OF PHASE-5 OF COLDSTART The DB2 ECCR is starting phase 5 of the cold-start process. Processing continues. No action is required. START OF DIRECTORY UPDATE The DB2 ECCR is starting to update the capture directory tables. Processing continues.
System Action: User Response: PWXEDM177298I Explanation: System Action: User Response: PWXEDM177299I Explanation: System Action:
User Response: PWXEDM177301I Explanation: System Action: User Response: PWXEDM177302I Explanation: System Action: User Response: PWXEDM177303A Explanation:
No action is required. DIRECTORY UPDATE COMPLETE The DB2 ECCR finished updating its capture directory tables. Processing continues. No action is required. BEGIN OF PHASE-6 OF COLDSTART The DB2 ECCR is starting phase 6 of the cold-start process. Processing continues. No action is required. TABLE OR COLUMN DEFINITIONS NOT APPROPRIATE - SHALL CAPTURE PROGRAM CONTINUE? ANSWER 'YES' OR 'NO' One of the following conditions caused this error:
One or more ST, SC, or SE records identify a source table or column that does not exist in the DB2 catalog. One or more ST records identify a source table that was not defined with the 'DATA CAPTURE CHANGES' clause. System Action: User Response: The DB2 ECCR waits for your response. If you enter YES, the DB2 ECCR continues. If you enter NO, the DB2 ECCR abends. Check for other messages that identify the error in more detail. Enter YES if the DB2 ECCR is to continue processing. Enter NO if the DB2 ECCR is to abend. ANSWER TO MESSAGE PWXEDM177303A WAS INVALID You entered an incorrect answer to message PWXEDM177303A. The DB2 ECCR issues message PWXEDM177303A again. Enter a correct response to message PWXEDM177303A. COLD START OF CAPTURE PROGRAM ABORTED BY A DB2 STOP OR AN MVS STOP COMMAND The DB2 ECCR cold-start process terminated abnormally because you performed one of the following actions:
You stopped DB2 during the DB2 ECCR cold-start process. You issued an MVS STOP command to stop the DB2 ECCR. System Action: User Response: PWXEDM177306E Explanation: System Action: User Response: The DB2 ECCR abends. No action is required. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR could not access the capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR issued a rollback, and the DB2 rollback failed.
836
The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. UNEXPECTED RETURN CODE FROM LOG-READ FUNCTION The DB2 ECCR received an unexpected return code from the specified function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM CANCELED BY OPERATORS The DB2 ECCR issues this message after you enter NO for message PWXEDM177303A. A NO answer for that message instructs the DB2 ECCR to abend.) The DB2 ECCR abends. No action is required. COLDSTART OF CAPTURE PROGRAM IS COMPLETE The DB2 ECCR cold-start process is complete. The DB2 ECCR is now in the processing mode. Processing continues. No action is required. CAPTURE PROGRAM CAN NOT READ DB2 LOG RECORDS The DB2 ECCR cold-start process could not read DB2 log records successfully. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. CAPTURE PROGRAM ABENDS BECAUSE OF A DB2 OR MVS STOP COMMAND The DB2 ECCR cold-start process terminated abnormally because you performed one of the following actions:
PWXEDM177309E Explanation: System Action: User Response: PWXEDM177310I Explanation: System Action: User Response: PWXEDM177311E Explanation: System Action: User Response:
You stopped DB2 during the DB2 ECCR cold-start process. You issued an MVS STOP command to stop the DB2 ECCR. System Action: User Response: PWXEDM177313I Explanation: System Action: User Response: PWXEDM177314I Explanation: The DB2 ECCR abends. No action is required. BEGIN OF SPECIAL START OF CAPTURE PROGRAM The DB2 ECCR has started the special-start initialization process. The DB2 ECCR will issue additional messages as the initialization process proceeds through the various phases. The DB2 ECCR begins the special-start initialization process. No action is required. ACCESSING DB2 LOG AT REQUESTED START LOCATION='log_location' The DB2 ECCR special-start process started processing the DB2 log at the specified location.
837
System Action: User Response: PWXEDM177315I Explanation: System Action: User Response: PWXEDM177316I Explanation: System Action: User Response: PWXEDM177317I Explanation: System Action: User Response: PWXEDM177318I Explanation: System Action: User Response: PWXEDM177319I Explanation: System Action: User Response: PWXEDM177320I Explanation: System Action: User Response: PWXEDM177321I Explanation: System Action: User Response: PWXEDM177322I Explanation: System Action: User Response:
Processing continues. No action is required. BEGIN OF PHASE-1 OF SPECIAL START The DB2 ECCR is starting phase 1 of the special-start process. Processing continues. No action is required. START OF ACCESS TO SYSTABLESPACE The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSTABLESPACE table. Processing continues. No action is required. ACCESS TO SYSTABLESPACE COMPLETE The DB2 ECCR completed accessing the DB2 catalog SYSIBM.SYSTABLESPACE table. Processing continues. No action is required. START OF ACCESS TO SYSTABLES The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSTABLES table. Processing continues. No action is required. ACCESS TO SYSTABLES COMPLETE The DB2 ECCR completed accessing the DB2 catalog SYSIBM.SYSTABLES table. Processing continues. No action is required. BEGIN OF PHASE-2 OF SPECIAL START The DB2 ECCR is starting phase 2 of the special-start process. Processing continues. No action is required. BEGIN OF CLEANUP OF CAPTURE DIRECTORY The DB2 ECCR started cleaning up the capture directory tables. Processing continues. No action is required. BEGIN OF PHASE-3 OF SPECIAL START The DB2 ECCR is starting phase 3 of the special-start process. Processing continues. No action is required.
838
PWXEDM177323I Explanation: System Action: User Response: PWXEDM177324I Explanation: System Action: User Response: PWXEDM177325I Explanation: System Action: User Response: PWXEDM177326I Explanation: System Action: User Response: PWXEDM177327I Explanation: System Action: User Response: PWXEDM177328I Explanation: System Action: User Response: PWXEDM177329A Explanation:
CREATE DESCRIPTIONS BASED ON DB2 CATALOG The DB2 ECCR special-start process is creating descriptions of the primary (source) tables from information in the DB2 catalog. Processing continues. No action is required. BEGIN OF PHASE-4 OF SPECIAL START The DB2 ECCR is starting phase 4 of the special-start process. Processing continues. No action is required. CREATE DESCRIPTIONS BASED ON PRE-EXISTING CAPTURE DIRECTORY INFO The DB2 ECCR special-start process is creating descriptions of the primary (source) tables from preexisting capture directory information. Processing continues. No action is required. BEGIN OF PHASE-5 OF SPECIAL START The DB2 ECCR is starting phase 5 of the special-start process. Processing continues. No action is required. VERIFY EXISTENCE OF TABLE AND COLUMN NAMES The DB2 ECCR is verifying the existence of the tables and columns identified on ST, SC and SE control records in the //REPL2CTL file. Processing continues. No action is required. BEGIN OF PHASE-6 OF SPECIAL START: MAINTENANCE OF TCAPSTATUS TABLE The DB2 ECCR is starting phase 6 of the special-start process. Processing continues. No action is required. TABLE OR COLUMN DEFINITIONS NOT APPROPRIATE - SHALL CAPTURE PROGRAM CONTINUE? ANSWER 'YES' OR 'NO' The DB2 ECCR encountered one of the following conditions:
One or more ST, SC, or SE records identify a primary (source) table or column that does not exist according to the capture directory One or more ST records identify a primary (source) table that is not defined with the DATA CAPTURE CHANGES clause. You must determine whether the DB2 ECCR continues. System Action: User Response: The DB2 ECCR waits for your response. If you enter YES, the DB2 ECCR continues. If you enter NO, the DB2 ECCR abends. Check for other messages that identify the error in more detail. Enter YES if the DB2 ECCR is to continue processing. Enter NO if the DB2 ECCR is to abend.
839
ANSWER TO MESSAGE PWXEDM177329A WAS INVALID You entered an incorrect answer to message PWXEDM177329A. The DB2 ECCR issues message PWXEDM177329A again. Enter a correct response to message PWXEDM177329A. START OF CAPTURE PROGRAM ABORTED BY A DB2 STOP OR AN MVS STOP COMMAND The DB2 ECCR special-start process terminated abnormally because you performed one of the following actions:
You stopped DB2 during the DB2 ECCR special-start process. You issued an MVS STOP command to stop the DB2 ECCR. System Action: User Response: PWXEDM177332E Explanation: System Action: User Response: The DB2 ECCR abends. No action is required. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access the capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR issued a rollback, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. UNEXPECTED RETURN CODE FROM LOG-READ FUNCTION The DB2 ECCR received an unexpected return code from the specified function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM CANCELED BY OPERATORS You requested an abend of the DB2 ECCR by entering NO to message PWXEDM177329A. The DB2 ECCR abends. No action is required. TCAPCOLUMNS ROWS ARE MISSING The DB2 ECCR special-start process detected a description of a table that has no columns in the capture directory tables. The DB2 ECCR abends. Ensure that the capture directory tables are updated only by the DB2 ECCR and the capture directory maintenance utility. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
840
UNEXPECTED RETURN CODE FROM X029225 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. VALUE OF STARTLOC= IS TOO HIGH The value of the STARTLOC keyword in the START STARTLOC control record in the //REPL2CTL file is higher then the highest RBA value of the log. The DB2 ECCR abends. Provide a correct RBA value for the STARTLOC keyword, and run the job again. SPECIAL START OF CAPTURE PROGRAM IS COMPLETE The DB2 ECCR special-start process is complete. The DB2 ECCR enters the processing mode. Processing continues. No action is required. MAINTENANCE OF CAPTURE DIRECTORY IS COMPLETE The DB2 ECCR warm-start process completed the maintenance of the capture directory tables. Processing continues. No action is required. UNEXPECTED RETURN CODE FROM X029225 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. BEGIN OF REFRESH PROCESSING You issued an MVS MODIFY job,REFRESH command: therefore, the DB2 ECCR starts the refresh process. Processing continues. No action is required. MAINTENANCE OF CAPTURE DIRECTORY IS COMPLETE The DB2 ECCR refresh process completed the maintenance of the capture directory tables. Processing continues. No action is required. UNEXPECTED RETURN CODE FROM X029225 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend.
PWXEDM177338E Explanation: System Action: User Response: PWXEDM177339E Explanation: System Action: User Response: PWXEDM177340I Explanation: System Action: User Response: PWXEDM177341E Explanation: System Action: User Response:
PWXEDM177342I Explanation: System Action: User Response: PWXEDM177343I Explanation: System Action: User Response: PWXEDM177344E Explanation:
841
The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177345W FOLLOWING CAPTURE DEFINITIONS ARE BEING DROPPED Explanation: During a start or refresh process, the DB2 ECCR detected that one or more source registration that had previously been registered for capture is no longer registered for capture. This message is followed by message PWXEDM177346I which lists the table that has been dropped. Processing continues. No action is required. CR=crid ST=table This message identifies the source table, table, record that was deleted from or added to capture. The crid identifies the capture request (CR)ID of the deleted ST record; table identifies the ST record. Processing continues. If the fully-qualified table name is in excess of 80 characters long, a multiline version of the message is issued with the following format:
PWXEDM177346I CR=BMCDB2CC CREATOR=creator_name PWXEDM177346I TABLE=table
User Response: System Action: PWXEDM177346I Explanation:
In addition, if one or other of the creator or table name are themselves longer than 75 characters, the name is continued, as in:
PWXEDM177346I CR=BMCDB2CC CREATOR=creator_name... PWXEDM177346I continued_creator PWXEDM177346I TABLE=table ... PWXEDM177346I continued_name
User Response: System Action: PWXEDM177349I Explanation: System Action: User Response: PWXEDM177350E Explanation: System Action: User Response:
Processing continues. No action is required. FOLLOWING CAPTURE DEFINITIONS ARE BEING ADDED During its start or refresh process, the DB2 ECCR detected that new ST definitions were added. Processing continues. No action is required. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access the capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initialized a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again.
842
CAPTURE PROGRAM CANCELED BY OPERATOR You entered CANCEL for message PWXEDM177347A. The DB2 ECCR abends. No action is required. CAPTURE PROGRAM STOPPED The DB2 ECCR stopped the start or refresh process because you performed one of the following actions:
You stopped DB2 during the DB2 ECCR start or refresh process. You issued an MVS STOP command to stop the DB2 ECCR. System Action: User Response: PWXEDM177354A Explanation: The DB2 ECCR abends. No action is required. TABLE OR COLUMN DEFINITIONS NOT APPROPRIATE -- SHALL CAPTURE PROGRAM CONTINUE? ANSWER 'YES' OR 'NO' The DB2 ECCR detected one of the following error conditions:
One or more ST, SC, or SE records identify a source table or a column that does not exist according to the capture directory or the DB2 catalog. One or more ST records identify a source table that is not defined with the DATA CAPTURE CHANGES clause. You must determine whether the DB2 ECCR continues. System Action: User Response: The DB2 ECCR waits for your response. If you enter YES, the DB2 ECCR continues; if you enter NO, the DB2 ECCR abends. Check for other messages that identify the error in more detail. Enter YES if the DB2 ECCR is to continue. Enter NO if the DB2 ECCR is to abend. ANSWER TO MESSAGE PWXEDM177354A WAS INVALID You entered an incorrect answer for message PWXEDM177354A. The DB2 ECCR issues message PWXEDM177354A again. Enter a correct response for message PWXEDM177354A. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access the capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initialized a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. CAPTURE PROGRAM CANCELED BY OPERATOR You entered NO for message PWXEDM177354A. The DB2 ECCR abends.
843
No action is required. UNEXPECTED RETURN CODE FROM X029232 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM ABENDS AFTER MULTIPLE RETRIES The DB2 ECCR accessed the DB2 catalog to obtain descriptions of the primary (source) tables. The obtained descriptions were inconsistent, probably because data definition language (DDL) activity is changing the table descriptions concurrently with the DB2 ECCR access. If the DB2 ECCR cannot get consistent descriptions after several attempts, it abends. The DB2 ECCR abends. Start the DB2 ECCR when less DDL activity is occurring. If this action does not correct the problem, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE PROGRAM STOPPED The DB2 ECCR stopped the start or refresh process because you performed one of the following actions:

You stopped DB2 during the DB2 ECCR start or refresh process. You issued an MVS STOP command to stop the DB2 ECCR.
System Action: User Response: PWXEDM177362I Explanation: System Action: User Response: PWXEDM177363I Explanation: System Action: User Response: PWXEDM177364I Explanation: System Action: User Response: PWXEDM177365I Explanation: System Action:
The DB2 ECCR abends. No action is required. START OF ACCESS TO SYSCOLUMNS The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSCOLUMNS table. Processing continues. No action is required. ACCESS TO SYSCOLUMNS COMPLETE The DB2 ECCR completed accessing the DB2 catalog SYSIBM.SYSCOLUMNS table. Processing continues. No action is required. START OF ACCESS TO SYSFIELDS The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSFIELDS table. Processing continues. No action is required. ACCESS TO SYSFIELDS COMPLETE The DB2 ECCR completed accessing the DB2 catalog SYSIBM.SYSFIELDS table. Processing continues.
844
No action is required. CAPTURE-DIRECTORY OR DB2-CATALOG CAN NOT BE PROPERLY ACCESSED! The DB2 ECCR cannot access a table either in the capture directory or in the DB2 catalog. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initialized a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again.
PWXEDM177368W SYSTABLESPACE ROW NOT FOUND IN DB2 CATALOG Explanation: The DB2 ECCR could not find an expected row in the DB2 catalog SYSIBM.SYSTABLESPACE table. Probably, DDL activity is changing the table descriptions concurrently with the DB2 ECCR access. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177369W SYSCOLUMNS ROWS NOT FOUND IN DB2 CATALOG Explanation: The DB2 ECCR could not find an expected row in the DB2 catalog SYSIBM.SYSCOLUMNS table. Probably, DDL activity is changing the table descriptions concurrently with the DB2 ECCR access. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177370W SYSFIELDS ROW NOT FOUND IN DB2 CATALOG Explanation: The DB2 ECCR could not find an expected row in the DB2 catalog SYSIBM.SYSFIELDS table. Probably, DDL activity is changing the table descriptions concurrently with the DB2 ECCR access. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177371W TABLE=table DOES NOT EXIST IN DB2 CATALOG Explanation: The DB2 ECCR cannot find a description of the specified table in the DB2 catalog. You might have incorrectly defined the specified table on an ST record in the //REPL2CTL file. If the fully-qualified table name is in excess of 65 characters long (this includes the period (.) that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177371W TABLE DOES NOT EXIST IN DB2 CATALOG PWXEDM177371W CREATOR: creator_name PWXEDM177371W TABLE: table_name
845
Each part of the fully-qualified table name is on a separate line in the message. In addition, if one or the other of the creator or name are themselves longer than 80 characters, the name is continued, as in:
PWXEDM177371W TABLE DOES NOT EXIST IN CAPTURE DIRECTORY PWXEDM177371W CREATOR: creator_name_.... PWXEDM177371W PWXEDM177371W TABLE: PWXEDM177371W continued_creator_name table_name_.... continued_table_name
The DB2 ECCR issues additional messages to tell you whether it will abend or continue processing. Ensure the table name is spelled correctly on the ST record, and run the job again.
PWXEDM177372W INCONSISTENT DEFINITIONS FOR table Explanation: The DB2 ECCR attempted to obtain a description of the specified table from the DB2 catalog, but the obtained description was inconsistent. Probably, DDL activity is updating the catalog descriptions concurrently with the DB2 ECCR access. If the fully-qualified table name is in excess of 70 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177372W INCONSISTENT DEFINITIONS FOR TABLE PWXEDM177372W CREATOR: creator_name PWXEDM177372W TABLE: table_name
PWXEDM177372W INCONSISTENT DEFINITIONS FOR TABLE PWXEDM177372W CREATOR: creator_name_.... PWXEDM177372W PWXEDM177372W TABLE: PWXEDM177372W continued_creator_name table_name_.... continued_table_name
The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177373W DB2 CATALOG DEFINITION NOT AVAILABLE AT STARTUP FOR TABLE=table_name Explanation: When the DB2 ECCR starts, it attempts a description of the source table from the DB2 catalog. The table indicated by table_name did not have a catalog definition. The DB2 ECCR cannot capture updates from this table. If the fully-qualified table name is in excess of 40 characters long (this includes the period (.) that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177373W DB2 CATALOG DEFINITION NOT AVAILABLE AT STARTUP FOR TABLE PWXEDM177373W CREATOR: creator_name PWXEDM177373W TABLE: table_name
PWXEDM177373W DB2 CATALOG DEFINITION NOT AVAILABLE AT STARTUP FOR TABLE PWXEDM177373W CREATOR: creator_name_.... PWXEDM177373W 846 Chapter 6: PWXEDM176400 to PWXEDM177699 continued_creator_name
PWXEDM177373W TABLE: PWXEDM177373W
table_name_.... continued_table_name
System Action:
The DB2 ECCR suspends capturing changes from this table until it finds a CREATE TABLE request for this table in the DB2 log. The CREATE TABLE request must appear in the log after the specified restart RBA for the ECCR. No action is required. CAPTURE-DIRECTORY OR DB2-CATALOG CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a table either in the capture directory or in the DB2 catalog. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initialized a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. TABLE table_name NOT FOUND IN DB2 CATALOG The DB2 ECCR cannot find a description of the specified table in the DB2 catalog. This situation is normal if the specified table did not exist when the log records that are currently being processed were written. The DB2 ECCR cannot capture updated rows of the specified table until it finds and reads DDL log records that describe the next CREATE TABLE for that table.
The DB2 ECCR suspends capturing updated rows until it reads DDL log records describing the next CREATE TABLE for the specified table. Verify that the table name is correctly specified in the data resource registration. If the table name is correctly specified, you must create the table before you can capture changes. TWO TABLES WITH SAME DBID/PSID/OBID ARE RECORDED IN TCAPTABLES According to the descriptions in the TCAPTABLES table in the capture directory, two different tables have the same combination of DB2 DBID/PSID/OBID. The DB2 ECCR issues message PWXEDM177378E to provide the names of the two tables. The DB2 ECCR abends. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting all rows describing one of the two tables from the TCAPTABLES table. Then, start the DB2 ECCR again. table1 AND table2 This message displays the names of the tables described in message PWXEDM177377E. If either fully-qualified table name is in excess of 27 characters long (this includes the period (.) that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177378E table_name1 PWXEDM177378E AND PWXEDM177378E table_name1
847
Each fully-qualified table name is on a separate line in the message, with the word AND on a separate line in the message as well. This variant of the message can contain up to 80 characters of the fully-qualified table name. However, if either one of the fully-qualified table names are in excess of 80 characters, a further variation of the message is issued:
PWXEDM177378E CREATOR: creator_name1 PWXEDM177378E TABLE: PWXEDM177378E AND PWXEDM177378E CREATOR: creator_name2 PWXEDM177378E TABLE: table_name2 table_name1
PWXEDM177378E CREATOR: creator_name1_.... PWXEDM177378E PWXEDM177378E TABLE: PWXEDM177378E PWXEDM177378E AND PWXEDM177378E CREATOR: creator_name2_.... PWXEDM177378E PWXEDM177378E TABLE: PWXEDM177378E continued_creator_name2 table_name2_.... continued_table_name2 continued_creator_name1 table_name1 continued_table_name1
The DB2 ECCR abends. Follow the instructions in message PWXEDM177377E and message PWXEDM177378E. DELETE ONE OF THE TWO TABLES FROM TCAPTABLES This message provides a reminder to delete all rows that describe one of the tables message PWXEDM177378E identifies. The DB2 ECCR abends. See messagePWXEDM177377E. Delete all rows describing one of the two tables from the TCAPTABLES table. Then, start the DB2 ECCR again. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access the capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initialized a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. INTERNAL ERROR - HASH ENTRY DOES NOT POINT TO A TA DB2 ECCR detected an incorrect hash table entry. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends.
848
User Response:
You might correct the problem by running the job again. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - UNEXPECTED RETURN CODE FROM SEARCH The DB2 ECCR received an unexpected return code from the specified function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. TCAPCOLUMNS ROWS NOT FOUND IN CAPTURE DIRECTORY The capture directory describes a table that has no columns. A table must have at least one column. The DB2 ECCR abends. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the ST record for the problematic table and starting the DB2 ECCR again without capturing updates for this table. SEQUENCE-ERROR FOR TCAPCOLUMNS ROWS IN CAPTURE DIRECTORY The DB2 ECCR found the descriptions of the source table columns are not in the expected sequence in the TCAPCOLUMNS table. The DB2 ECCR abends. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the ST record for the problematic table and starting the DB2 ECCR again without capturing updates for this table. TCAPFIELDS ROW NOT FOUND IN CAPTURE DIRECTORY The DB2 ECCR did not find an expected row in the capture directory TCAPFIELDS table. The DB2 ECCR abends. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the ST record for the problematic table and starting the DB2 ECCR again without capturing updates for this table. TABLE=table DOES NOT EXIST IN CAPTURE DIRECTORY The DB2 ECCR cannot find a description of the specified table in the capture directory tables. If the fully-qualified table name is in excess of 60 characters long (this includes the period (.) that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177387E TABLE DOES NOT EXIST IN CAPTURE DIRECTORY PWXEDM177387E CREATOR: creator_name PWXEDM177387E TABLE: table_name
PWXEDM177387E TABLE DOES NOT EXIST IN CAPTURE DIRECTORY PWXEDM177387E CREATOR: creator_name_....
849
PWXEDM177387E PWXEDM177387E TABLE: PWXEDM177387E
continued_creator_name table_name_.... continued_table_name
The DB2 ECCR abends. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. Start the DB2 ECCR again.
PWXEDM177388W INCONSISTENT DEFINITIONS FOR table Explanation: The DB2 ECCR was obtaining a description of the specified table from the capture directory tables and found the description was not consistent. If the fully-qualified table name is in excess of 70 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177388W INCONSISTENT DEFINITIONS FOR PWXEDM177388W CREATOR: creator_name PWXEDM177388W TABLE:
table_name
PWXEDM177388W INCONSISTENT DEFINITIONS FOR PWXEDM177388W CREATOR: creator_name_ .... PWXEDM177388W PWXEDM177388W TABLE: PWXEDM177388W
continued_creator_name table_name_ .... continued_table_name
The DB2 ECCR abends. Check other error messages for more detailed descriptions of the error.
PWXEDM177389W COLUMN DESCRIPTIONS MISSING FOR TABLE=table Explanation: System Action: User Response: The DB2 ECCR cannot find the description of all columns in the specified table in the capture directory. You might have caused this error by using the ALTER TABLE statement. Processing continues. No action is required.
PWXEDM177390W UNUSABLE DEFINITION CR=cr ST=table Explanation: The DB2 ECCR cannot find in a usable definition for the specified capture request (CR) and source table (ST) definitions in the capture directory. If the fully-qualified table name is in excess of 65 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177390W UNUSABLE DEFINITION CR=capture_request_id PWXEDM177390W CREATOR: creator_name PWXEDM177390W TABLE: table_name
PWXEDM177390W UNUSABLE DEFINITION CR=capture_request_id PWXEDM177390W CREATOR: creator_name PWXEDM177390W continued_creator_name
850
PWXEDM177390W TABLE: PWXEDM177390W
table_name continued_table_name
The DB2 ECCR abends. Check for additional information in associated error messages. Ensure that the specified CR and ST definitions are correct in the //REPL2CTL file. Then, start the DB2 ECCR again. You can bypass this problem by deleting the ST record for the problematic table and starting the DB2 ECCR again without capturing updates for this table.
COLUMN column NOT FOUND FOR TABLE=table The DB2 ECCR cannot find a description of the specified column for the specified table in the capture directory. If the fully-qualified table name is in excess of 55 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177391E COLUMN column_name NOT FOUND FOR TABLE PWXEDM177391E CREATOR: creator_name PWXEDM177391E TABLE: table_name
PWXEDM177391E COLUMN column_name NOT FOUND FOR TABLE PWXEDM177391E CREATOR: creator_name_.... PWXEDM177391E PWXEDM177391E TABLE: PWXEDM177391E continued_creator_name table_name_.... continued_table_name
The DB2 ECCR abends. Check for additional information in associated error messages. Ensure that the specified CR and ST definitions are correct in the //REPL2CTL file. Correct wrong definitions, and start the DB2 ECCR again. You can bypass this problem by deleting the ST record for the problematic table and starting the DB2 ECCR again without capturing updates for this table.
INVALID CALL FUNCTION FOR X029242 The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR issued a rollback request, and the DB2 rollback failed.
851
The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. UNEXPECTED VALUE IN COLTYPE COLUMN OF TCAPCOLUMNS TABLE The DB2 ECCR found an incorrect value in the COLTYPE column of the TCAPCOLUMNS table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED VALUE IN FLDTYPE COLUMN OF table_name TABLE The DB2 ECCR found an incorrect value in the FLDTYPE column of the table_name table, where table_name is either TCAPFIELDS or SYSFIELDS. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177397W TABLE=table_name NOT DEFINED IN DB2 CATALOG Explanation: The DB2 ECCR cannot find a description of the specified table in the DB2 catalog. This situation might be normal if the table did not exist when the next log records to be processed were written. The action of the DB2 ECCR is described in additional messages. Ensure that the table names are spelled correctly in the ST records of the //REPL2CTL file. Then, run the job again.
PWXEDM177398W TABLE=table PROBABLY NOT DEFINED WITH 'DATA CAPTURE CHANGES' Explanation: The specified table may not have been defined with the DATA CAPTURE CHANGES attribute. If the fully-qualified table name is in excess of 45 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177398W TABLE PROBABLY NOT DEFINED WITH "DATA CAPTURE CHANGES" PWXEDM177398W CREATOR: creator_name PWXEDM177398W TABLE: table_name
PWXEDM177398W TABLE PROBABLY NOT DEFINED WITH "DATA CAPTURE CHANGES" PWXEDM177398W CREATOR: creator_name_.... PWXEDM177398W PWXEDM177398W TABLE: PWXEDM177398W continued_creator_name table_name_.... continued_table_name
The action of the DB2 ECCR is described in additional messages. If the table was not defined with the DATA CAPTURE CHANGES attribute, use the ALTER TABLE command to specify the DATA CAPTURE CHANGES attribute for the specified table.
852
If a table that was not defined with DATA CAPTURE CHANGES is subsequently altered to DATA CAPTURE CHANGES, this message will continue to be issued on startup or refresh of the ECCR until the first change record for the table is encountered. PWXEDM177399W COLUMN=column_name OF TABLE=table_name NOT DEFINED Explanation: The DB2 ECCR cannot find the column column_name in the TCAPCOLUMNS table or in the DB2 catalog. In the message text:

column_name is the column that you registered for capture. table_name is the table that contains the column registered for capture.
If the creator.table name for the table name is greater than 40 characters in length, including the period (.) separator, this message is displayed on multiple lines:
PWXEDM177399W COLUMN=column_name OF TABLE NOT DEFINED PWXEDM177399W CREATOR: creator_name PWXEDM177399W TABLE:
table_name
The column, creator, and table names are displayed on separate lines in the message. In addition, if either the creator_name or table_name is greater than 80 characters in length, it is continued on a separate line. The first 80 characters of the creator_name or table_name are displayed on one line, and the remaining characters of these names are displayed on the subsequent lines, as shown in the following examples:
PWXEDM177399W COLUMN=column_name OF TABLE NOT DEFINED PWXEDM177399W CREATOR: creator_name_ ... PWXEDM177399W PWXEDM177399W TABLE: PWXEDM177399W ...continued_creator_name
table_name _...
...continued_table_name
The DB2 ECCR continues running until it reads the next change record for the table. Then, the DB2 ECCR abends. Correct the column specification in the capture registration. Then warm start the DB2 ECCR. LAYOUT OF //REPL2OPT CONTROL RECORDS: The DB2 ECCR is starting the model layout of the possible control statements from the //REPL2OPT file. Processing continues. No action is required. START OF //REPL2OPT CONTROL RECORDS: The DB2 ECCR is starting to process the //REPL2OPT control statements. The DB2 ECCR displays the control statement with an indication of any syntax or other errors. Processing continues. If errors occur, use the information in the error text for the incorrect input statement to determine the cause of the error. Then, correct and reenter the statement. END OF //REPL2OPT CONTROL RECORDS The DB2 ECCR completed processing the //REPL2OPT control statements. Processing continues. No action is required.
853
LAYOUT OF //REPL2CTL CONTROL RECORDS: The DB2 ECCR is starting the model layout of the possible control statements from a //REPL2CTL file. Processing continues. No action is required. START OF //REPL2CTL CONTROL RECORDS: The DB2 ECCR is starting to process the control statements from the //REPL2CTL file. The DB2 ECCR displays both the control statements you entered and the control statements the DB2 ECCR created. The displayed information includes any syntax or other errors. Any control card created by the DB2 ECCR contains the following:
** SYSTEM GENERATED **
Processing continues. If errors occur, use the information in the error text for the incorrect input statement to determine the cause of the error. Then, correct and reenter the statement. END OF //REPL2CTL CONTROL RECORDS The DB2 ECCR completed processing the //REPL2CTL control statements. Processing continues. No action is required. * * * ABOVE RECORD IS IGNORED DURING REFRESH PROCESSING You entered the REFRESH command and input the //REPL2OPT START and DB2 control statements concurrently. The DB2 ECCR does not process input statements during a REFRESH. The DB2 ECCR completes the REFRESH, but ignores the START input statements and the DB2 control statements. If the system action is acceptable, no action is required. If you need the START and DB2 control statements processed, enter them again for processing at the next restart of the DB2 ECCR. error_text The DB2 ECCR found a syntax error in a statement in a //REPL2OPT file. The DB2 ECCR displays the contents of the erroneous statement. Then, the DB2 ECCR displays the reason for the syntax error in this message. The DB2 ECCR abends with abend code U3680. Correct the statement with the syntax error, and start the DB2 ECCR again. For the syntax of the //REPL2OPT input statements, see the PowerExchange CDC Guide for z/OS. For more information about the abend code, see Abend Code U3680: DB2 ECCR on page 915. error_text The DB2 ECCR found a syntax error in a statement in the //REPL2OPT file. The DB2 ECCR displays the contents of the erroneous statement. Then, the DB2 ECCR displays the reason for the syntax error in this message. The DB2 ECCR abends with abend code U3680.
PWXEDM177405I Explanation: System Action: User Response: PWXEDM177406I Explanation: System Action:
User Response:
User Response:
854
User Response:
Correct the statement with the syntax error, and start the DB2 ECCR again. For the syntax of the //REPL2OPT input statements, see the PowerExchange CDC Guide for z/OS. For more information about the abend code, see Abend Code U3680: DB2 ECCR on page 915. error_text The DB2 ECCR found a sequence error in a statement in the //REPL2CTL file. The DB2 ECCR displays the contents of the erroneous statement. Then, the DB2 ECCR displays the reason for the sequence error in this message. The DB2 ECCR abends with abend code U3680. Correct the statement with the sequence error, and start the DB2 ECCR again. For the syntax of the //REPL2CTL input statements, see the PowerExchange CDC Guide for z/OS. For more information about the abend code, see Abend Code U3680: DB2 ECCR on page 915. INVALID REPL2CTL CONTROL RECORD - CR You entered a capture request (CR) control statement in the //REPL2CTL file. The CR control statement is not a valid //REPL2CTL control statement. The DB2 ECCR abends with abend code U3680. Remove or correct the CR //REPL2CTL control statement, and start the DB2 ECCR again. For the syntax of the //REPL2CTL input statements, see the PowerExchange CDC Guide for z/OS. To determine the meaning of the abend code, see Abend Code U3680: DB2 ECCR on page 915. INVALID REPL2CTL CONTROL RECORD - ST You entered a source table (ST) control statement in the //REPL2CTL file. The ST control statement is not a valid //REPL2CTL control statement. The DB2 ECCR abends with abend code U3680. Remove or correct the ST //REPL2CTL control statement, and start the DB2 ECCR again. For the syntax of the //REPL2CTL input statements, see the PowerExchange CDC Guide for z/OS. To determine the meaning of the abend code, see Abend Code U3680: DB2 ECCR on page 915. error_text The DB2 ECCR found a syntax error in a statement in the //REPL2CTL file. The DB2 ECCR displays the contents of the erroneous statement. Then, the DB2 ECCR displays the reason for the syntax error in this message. The DB2 ECCR abends with abend code U3680. Correct the statement with the syntax error, and start the DB2 ECCR again. For the syntax of the //REPL2CTL input statements, see the PowerExchange CDC Guide for z/OS. To determine the meaning of the abend code, see Abend Code U3680: DB2 ECCR on page 915. START OF ACCESS TO SYSTABLEPART The DB2 ECCR started accessing the DB2 catalog SYSIBM.SYSTABLEPART table. This message is also issued when the DB2 ECCR requires information to decompress a table during processing. Processing continues. No action is required.
User Response:
User Response:
855
ACCESS TO SYSTABLEPART COMPLETE The DB2 ECCR finished accessing the DB2 catalog SYSIBM.SYSTABLEPART table. This message is also issued when the DB2 ECCR requires information to decompress a table during processing. Processing continues. No action is required.
PWXEDM177415W COLUMN=column OF NOTIFICATION TABLE=table NOT DEFINED Explanation: The //REPL2CTL file contains a source table (ST) record that includes the 'TYPE=NOTIF parameter. This parameter identifies the table as an event notification table; however, the table does not contain the specified column, which is a required column for event notification tables. If the fully-qualified table name is in excess of 27 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177415W COLUMN=column_name OF NOTIFICATION TABLE NOT DEFINED PWXEDM177415W CREATOR: creator_name PWXEDM177415W TABLE: table_name
PWXEDM177415W COLUMN=column_name OF NOTIFICATION TABLE NOT DEFINED PWXEDM177415W CREATOR: creator_name_.... PWXEDM177415W PWXEDM177415W TABLE: PWXEDM177415W continued_creator_name table_name_.... continued_table_name
Subsequent messages describe the DB2 ECCR action. Recreate the event notification table with all of the required columns. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR issued a rollback request, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Correct the problem, and run the job again.
856
ROLLBACK HAS FAILED The DB2 ECCR issued a rollback request, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. X029260 CALLED WITH INVALID CALL FUNCTION The specified module was called by an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. X029260 CALLED FOR UNEXPECTED DB2 CATALOG TABLE The specified module issued a call for an incorrect DB2 catalog table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RETURN CODE FROM X029261 Module X020260 received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. TCAPTABLESPACE HAS NO CURRENT ROW FOR DB=database TABLESPACE=tablespace While processing log records that describe DDL changes, the DB2 ECCR could not find a row in the capture directory TCAPTABLESPACE table for the specified DB2 database tablespace. The DB2 ECCR continues processing. However, it cannot capture changes from tables located in the identified tablespace. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. CAPTURE WILL NOT SUCCEED FOR TABLE=table While processing log records that describe DDL changes, the DB2 ECCR could not find a row in the capture directory TCAPTABLESPACE table for the tablespace containing the specified table. If the fully-qualified table name is in excess of 65 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177424E CAPTURE WILL NOT SUCCEED FOR TABLE PWXEDM177424E CREATOR: creator_name PWXEDM177424E TABLE: table_name
Each part of the fully-qualified table name is on a separate line in the message.
857
PWXEDM177424E CAPTURE WILL NOT SUCCEED FOR TABLE PWXEDM177424E CREATOR: creator_name_.... PWXEDM177424E PWXEDM177424E TABLE: PWXEDM177424E continued_creator_name table_name_.... continued_table_name
The DB2 ECCR continues processing. However, it cannot capture changes from the specified table. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. NO CURRENT TCAPTABLES ROW FOR TABLE=table While processing log records that describe DDL changes, the DB2 ECCR could not find a row in the capture directory TCAPTABLES table for the specified table. If the fully-qualified table name is in excess of 65 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177425E NO CURRENT TCAPTABLES ROW FOR TABLE PWXEDM177425E CREATOR: creator_name PWXEDM177425E TABLE: table_name
PWXEDM177425E NO CURRENT TCAPTABLES ROW FOR TABLE PWXEDM177425E CREATOR: creator_name_.... PWXEDM177425E PWXEDM177425E TABLE: PWXEDM177425E continued_creator_name table_name_.... continued_table_name
The DB2 ECCR continues processing. However, it cannot capture changes from the specified table. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. UNEXPECTED table IN TCAPWORK ROW The DB2 ECCR found an incorrect table name in a TCAPWORK row. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED DATA LENGTH IN LOG RECORD DESCRIBING A catalog_table UPDATE The DB2 ECCR found an incorrect data length in a log record that describes a change in the catalog_table table, which is one of SYSTABLES, SYSCOLUMNS, or SYSTABLESPACE. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
858
UNEXPECTED VALUE IN UPTYPE COLUMN OF A TCAPWORK ROW The DB2 ECCR found an incorrect value in a column in a TCAPWORK row. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. TCAPWORK TABLE DOES NOT CONTAIN EXPECTED ROWS The DB2 ECCR found incorrect rows in the TCAPWORK table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initiated a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. INVALID LENGTH OF A SYSTABLES COLUMN VALUE The DB2 ECCR found an incorrect length for a value in a column of the SYSTABLES table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID LENGTH OF A SYSCOLUMNS COLUMN VALUE The DB2 ECCR found an incorrect length for a value in a column in the SYSCOLUMNS table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID LENGTH OF A SYSFIELDS COLUMN VALUE The DB2 ECCR found an incorrect length for a value in a column in the SYSFIELDS table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
859
INVALID LENGTH OF A SYSTABLESPACE COLUMN VALUE The DB2 ECCR found an incorrect length for a value in a column in the SYSTABLESPACE table. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. NO UR(S) FOUND When you issued the unit-of-recovery ID (URID) command to the DB2 ECCR, it could not find any active units of recovery. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR ignores the command. This message can also be generated during Statistics and Refresh processing. Processing continues. No action is required. OPEN UNIT (S) OF RECOVERY You issued the unit-of-recovery ID (URID) command to the DB2 ECCR. The DB2 ECCR displays a list of the active units of recovery (UR) following this message. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). This message can also be generated during Statistics and Refresh processing. Processing continues. No action is required. UR=urid STATUS=code [UOW=uow_id] [LRSN=lrsn] LAST=last OPER=nn The DB2 ECCR displays a unit-of-recovery ID (URID) and an internal status code for each unit of recovery (UR) that is active at the time you issued the F DB2 eccr-name,URID command. A PowerExchange Logger unit of work (UOW) is the same as a DB2 UR. This message can also be generated during Statistics and Refresh processing. The variables in the message are as follows:

UR=urid. The urid variable is the unit-of-recovery ID (URID). STATUS=code. The code variable has one of the following values: P = Pending. The Begin UOW has been received but no change data has been received to capture. O = Old. There is change data to capture but no Begin UOW has been received. U = Unresolved. If the code value is U, then the UR value is always PENDING. The message includes a UOW=uow_id value that specifies the UOW ID assigned by the DB2 ECCR. No URID value is available because the URID has not been encountered during this execution of the DB2 ECCR.
Message PWXEDM177440W is issued when an outstanding UOW is not resolved. This situation occurs if in-flight units of work exist when the previous occurrence of the DB2 ECCR is shut down, usually without specifying QUIESCE. T = Transmitting. The DB2 ECCR is sending change data for this UOW to the Logger. A = Abort. There is no change data to capture for this aborted UOW. R = Rollback. There is change data to capture for this aborted UOW. LRSN=lrsn. The lrsn variable is the optional DB2 log record sequence number (LRSN) for the UR, which appears if the DB2 ECCR operates in a data sharing environment.
860
LAST=last. The last variable is the RBA or LRSN of the last record that was processed for this unit of work. OPER=nn. The nn variable is the internal code that represents the type of DB2 log record that was last processed for this unit of work. System Action: User Response: Processing continues. Use this data to diagnose problems with units of work that do not terminate properly, such as units of work that remain as persistent outstanding UOWs. There could be none or multiple messages of each type of format. Entries with UR=urid can be resolved, if necessary, using the DB2 ECCR TERM command. Entries with UR=PENDING can only be resolved using the Logger RESOLVE_INDOUBT command, and the result of that operation would only show up in the DB2 ECCR the next time it is restarted. After the restart, the resolved entries no longer show up in the output from the URID command and do not affect the restart point for the DB2 ECCR. PWXEDM177439I Explanation: UNIT OF RECOVERY: urid TERMINATED You issued the TERM command to the DB2 ECCR. The DB2 ECCR stopped processing the specified unit-of-recovery ID (URID). Also, the DB2 ECCR did not create unit-of-work (UOW) records for the PowerExchange Logger from the specified URID. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR stops processing the URID. No action is required.
PWXEDM177440W NO BEGIN UNIT OF RECOVERY FOR THE UR=urid Explanation: The DB2 ECCR received a change record; however, no unit-of-recovery (UR) or unit-of-work entry exists for the change record. The DB2 ECCR does not send the change record to the PowerExchange Logger. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR does not process this change record and processing continues. No action is required.
PWXEDM177441W UNIT OF RECOVERY: urid NOT ACTIVE Explanation: You entered the TERM command for the specified unit-of-recovery ID (URID) or unit-of-work ID. However, the specified URID was not active. Possibly, you entered the URID incorrectly. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR ignores the TERM command for the specified URID and processing continues. Issue the URID command to get a list of all active URIDs (UOWs). If required, issue the TERM command again with the correct URID of an active unit of recovery. BEGIN UNIT OF WORK OCCURRED OUT OF SEQUENCE: UR=urid The DB2 ECCR received a begin unit-of-work request for a unit-of-work ID (UOWID) or unit-of-recovery ID. However, the DB2 ECCR had already received a begin unit-of-work request for the URID. The DB2 ECCR can process only one unit-of-work request for a URID. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
UPDATE OF CAPTURED TABLE OUT OF SEQUENCE, IN ABORT STATUS: UR=urid A change was made to the associated table while the DB2 ECCR was in the abort status for the specified unit of recovery or unit of work. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Error deleting old outstanding UOW: URID=unit_of_work_identifier The DB2 change capture program was attempting to delete an old outstanding UOW that it had reconciled with data it found in DB2 log data. However, the process of doing the delete was unsuccessful. Processing will terminate following some more messages. Collect the complete DB2 ECCR job listing. Then, contact Informatica Global Customer Support. INVALID STATUS ENCOUNTERED FOR UR=urid STATUS=status The specified unit-of-recovery ID (URID) has an invalid DB2 ECCR internal status. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DISCARDING PREVIOUS UNPAIRED LOG RECORD WITH ID=log-rba While processing DB2 log records, the DB2 ECCR detected a log record that it could not pair with an expected continuation record. This error occurs if one of the following situations exist:
The DB2 ECCR has just completed a cold start, a warm start, or a refresh and all of the following conditions exist: You added new ST control records. You defined the new ST control records using IN control records that specify INITIALLY ACTIVE. The tables were being updated when the next log records to be processed after the start or refresh were written to the log. The DB2 ECCR just completed a special start. System Action: User Response: The DB2 ECCR discards the unpaired log record. See message PWXEDM177030E to determine whether the DB2 ECCR abends or attempts to continue. If this message is issued only occasionally and if it is issued each time because one of the above error conditions occurred, ignore the message. However, if it is issued frequently or for reasons other than those in the explanation, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DISCARDING CURRENT UNPAIRED LOG RECORD WITH ID=log-rba - text While processing DB2 log records, the DB2 ECCR detected a log record that it could not pair with an expected predecessor record. This error occurs if one of the following situations exist:
The DB2 ECCR has just completed a cold start, a warm start, or a refresh and all of the following conditions exist:
862
You added new ST control records. You defined the new ST control records using IN control records that specify INITIALLY ACTIVE. The tables were being updated when the next log records to be processed after the start or refresh were written to the log. The DB2 ECCR just completed a special start. System Action: User Response: The DB2 ECCR discards the unpaired log record. See message PWXEDM177030E to determine whether the DB2 ECCR abends or attempts to continue. If this message is issued only occasionally and if it is issued each time because one of the above error conditions occurred, ignore the message. However, if it is issued frequently or for reasons other than those in the explanation, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. TABLE DEFINITIONS NOT USABLE - table The DB2 ECCR cannot find a usable description of the specified table. If the fully-qualified table name is in excess of 70 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177448E TABLE DEFINITIONS NOT USABLE PWXEDM177448E CREATOR: creator_name PWXEDM177448E TABLE: table_name
PWXEDM1774448E TABLE DEFINITIONS NOT USABLE PWXEDM1774448E CREATOR: creator_name_.... PWXEDM1774448E PWXEDM1774448E TABLE: PWXEDM1774448E continued_creator_name table_name_.... continued_table_name
The DB2 ECCR abends. To determine the cause of the error, check for previously written error messages that may provide more information about the error. If possible, correct the problem, and run the job again. To bypass the error, delete the ST records for the specified table from the //REPL2CTL file. Then, start the DB2 ECCR again. DDL AND DML IN SAME UOW FOR TABLE=table The DB2 ECCR detected that a unit of work (UOW) performed both DDL operations (for example, CREATE TABLE) and DML operations (for example, SQL INSERT) for the same table. This capability is not supported by the current DB2 ECCR software level. A PowerExchange Logger unit of work (UOW) is the same as a DB2 unit of recovery (UR). If the fully-qualified table name is in excess of 65 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177450E DDL AND DML IN SAME UOW FOR TABLE PWXEDM177450E CREATOR: creator_name PWXEDM177450E TABLE: table_name
PWXEDM177450E DDL AND DML IN SAME UOW FOR TABLE PWXEDM177450E CREATOR: creator_name_.... PWXEDM177450E PWXEDM177450E TABLE: PWXEDM177450E continued_creator_name table_name_.... continued_table_name
The DB2 ECCR continues. However, some changes may not be captured. Make sure that the units of work for the specified table do not perform both DDL and data manipulation language (DML) operations on the same table in the same unit of work. VARIATION DETERMINATION MISMATCH FOR LOG RECORD WITH ID = logrba The DB2 ECCR uses a self-checking option to determine whether a DB2 log record is interpreted differently by several versions of the DB2 variation determination logic. If a record can be interpreted differently, the DB2 ECCR issues this message for that record. See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ERROR DETECTED WHILE PROCESSING COMMIT OR ROLLBACK RECORD The DB2 ECCR detected an error while processing a unit of recovery's control log record. See message PWXEDM177030E to determine whether the DB2 ECCR abends or attempts to continue. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. DIRECTORY CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a capture directory table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initiated a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. X029270 CALLED WITH INVALID CALL FUNCTION The specified module was called with an invalid call function. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED ROW-LENGTH FOR TABLE=table_name The DB2 ECCR is processing a DB2 log record for the specified table. The log record contains a row with an incorrect row length.
864
If the fully-qualified table name is in excess of 70 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177456E UNEXPECTED ROW-LENGTH FOR TABLE PWXEDM177456E CREATOR: creator_name PWXEDM177456E TABLE: table_name
PWXEDM177456E UNEXPECTED ROW-LENGTH FOR TABLE PWXEDM177456E CREATOR: creator_name_.... PWXEDM177456E PWXEDM177456E TABLE: PWXEDM177456E continued_creator_name table_name_.... continued_table_name
See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED ROW-LENGTH FOR TABLE=table_name The DB2 ECCR is processing a DB2 log record for the specified table. The log record contains a row with an incorrect row length. If the fully-qualified table name is in excess of 70 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177460E UNEXPECTED ROW-LENGTH FOR TABLE PWXEDM177460E CREATOR: creator_name PWXEDM177460E TABLE: table_name
PWXEDM177460E UNEXPECTED ROW-LENGTH FOR TABLE PWXEDM177460E CREATOR: creator_name_.... PWXEDM177460E continued_creator_name PWXEDM177460E TABLE: table_name_....
PWXEDM177460E continued_table_name
System Action:
See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. If the ECCR abends, it does so with a U3680 abend code and a reason code of 7. Make sure that the units of work for the specified table do not perform both DDL and DML operations on the same table in the same unit of work. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ROW NOT DECOMPRESSED, TABLE=owner.table_name, DB2 LOG LOCATION=rba The DB2 ECCR has received a log record through the IFI306 interface that has not been decompressed by DB2.
User Response:
865
PWXEDM177462E ROW NOT DECOMPRESSED, DB2 LOG LOCATION=rba PWXEDM177462E CREATOR: creator_name PWXEDM177462E TABLE: table_name
PWXEDM177462E ROW NOT DECOMPRESSED, DB2 LOG LOCATION=rba PWXEDM177462E CREATOR: creator_name_.... PWXEDM177462E PWXEDM177462E TABLE: PWXEDM177462E continued_creator_name table_name_.... continued_table_name
DB2 ECCR ends abnormally. If the REPL2TRA DD statement is present, trace information is provided that dumps several DB2 ECCR control blocks. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED COLUMN-TYPE CODE IN INTERNAL CONTROL BLOCK The DB2 ECCR found an unexpected column type code in an internal control block. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177464W INTERNAL ERROR: AREA TOO SMALL TO BUILD THE ROW IMAGE Explanation: System Action: User Response: When the DB2 ECCR attempted to create a row image in memory, it found the allocated memory area was too small. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177465W INTERNAL ERROR: AREA TOO SMALL TO BUILD THE OUTPUT MESSAGE Explanation: When the DB2 ECCR attempted to build an output message in memory, it found the allocated memory area was too small. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: UNEXPECTED R2PCLFUN VALUE The DB2 ECCR found an unexpected value in R2PCLFUN. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
866
INTERNAL ERROR: UNEXPECTED RETURN CODE FROM PX029280 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. FREEING LZCOMPRS DICTIONARY AT address, ID=number The DB2 ECCR is freeing the storage used by the DB2 dictionary identified in the message. Processing continues. No action is required. EDITPROC edit_proc RETURNED WITH RC/RSNC=rc/reason FOR TABLE=table The specified EDITPROC exit routine for the specified table returned with the specified return code and reason code. If the fully-qualified table name is in excess of 35 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177469E EDITPROC edit_proc RETURNED WITH RC/RSNC=rc/reason PWXEDM177469E CREATOR: creator_name PWXEDM177469E TABLE: table_name
PWXEDM177469E EDITPROC edit_proc RETURNED WITH RC/RSNC=rc/reason PWXEDM177469E CREATOR: creator_name_.... PWXEDM177469E PWXEDM177469E TABLE: PWXEDM177469E continued_creator_name table_name_.... continued_table_name
See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Determine why the EDITPROC exit routine encountered an error. Correct the problem, and run the job again. EDITPROC edit_proc OVERLAYED STORAGE - TABLE=table The specified EDITPROC exit routine overlaid a virtual storage area. If the fully-qualified table name is in excess of 55 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177470E EDITPROC edit_proc OVERLAYED STORAGE PWXEDM177470E CREATOR: creator_name PWXEDM177470E TABLE: table_name
PWXEDM177470E EDITPROC edit_proc OVERLAYED STORAGE PWXEDM177470E CREATOR: creator_name_....
867
PWXEDM177470E PWXEDM177470E TABLE: PWXEDM177470E
continued_creator_name table_name_.... continued_table_name
The DB2 ECCR abends. Correct the EDITPROC, and run the job again. UNEXPECTED CONTENT IN INTERNAL POINTERS The DB2 ECCR found incorrect internal pointers. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL AREA NOT LARGE ENOUGH FOR OUTPUT FROM FIELDPROC EXIT ROUTINE A FIELDPROC exit routine attempted to create its output; however, the area allocated for the output was too small. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. USER-PROVIDED FIELDPROC RETURNED WITH A NONZERO VALUE IN R15 A user-supplied FIELDPROC exit routine returned control to the DB2 ECCR with a nonzero value in register 15. A nonzero value in register 15 indicates that an error occurred. See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Use the information provided by other messages associated with this error to determine why the FIELDPROC exit routine encountered an error. Correct the problem, and run the job again. LENGTH OF COLUMN VALUE RETURNED BY A USER FIELDPROC IS INVALID The DB2 ECCR called a user-defined FIELDPROC exit routine to transform a value from the encoded field format into the decoded column format. The name of the FIELDPROC exit routine appears in another message. As described in the DB2 manuals for a VARCHAR and VARGRAPHIC column format, the FIELDPROC exit routine must return the two-byte length of the column value in the field FPVDVALE of the DB2 column value descriptor (CVD). This two-byte length must meet the following requirements:

It must be expressed as number of bytes. It must not be longer then the maximal length of the column. If it is a VARGRAPHIC column, it must be a multiple of 2. The DB2 ECCR detected that the returned value in FPVDVALE does not meet these requirements. System Action: User Response: See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Determine why the column value returned by the user-defined FIELDPROC exit routine did not meet these requirements. Correct the exit routine, and run the job again.
868
RC=rc RSNC=reason OF FIELDPROC=fieldproc FOR TABLE=table The DB2 ECCR called the specified FIELDPROC exit routine to transform a column value of the specified table from the encoded field format into the decoded column format. The FIELDPROC exit routine returned with a nonzero value in register 15. A nonzero value in register 15 signals that an error occurred. The FIELDPROC exit routine set the return code rc and reason code reason in the DB2 FPIB control block. The meanings of the return code and reason code are defined by the user-defined FIELDPROC exit routine. If the fully-qualified table name is in excess of 50 characters long (this includes the period . that is used as a separator between the creator and table name), a modified format is used:
PWXEDM177475E RC=rc RSNC=reason OF FIELDPROC=fieldproc FOR TABLE: PWXEDM177475E CREATOR: creator_name PWXEDM177475E TABLE: table_name
PWXEDM177475E RC=rc RSNC=reason OF FIELDPROC=fieldproc FOR TABLE: PWXEDM177475E CREATOR: creator_name_.... PWXEDM177475E PWXEDM177475E TABLE: PWXEDM177475E continued_creator_name table_name_.... continued_table_name
See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Determine why the FIELDPROC exit routine encountered an error. Correct the problem, and run the job again. text The FIELDPROC exit routine identified in message PWXEDM177475E returned with a nonzero value in register 15. A nonzero value in register 15 signals that an error occurred. The FIELDPROC exit routine also puts the address of a 40-byte error text message in the field FPBTOKPT and displays the 40-byte error text in this message. See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing. Determine why the FIELDPROC exit routine encountered an error. Correct the problem, and run the job again. UNEXPECTED EYE-CATCHER IN R2PMAIN The R2PMAIN control block is not initialized correctly. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. OPEN OF //SYSUT1 HAS FAILED The trace formatting utility could not open the //SYSUT1 file. Probably, you are missing a //SYSUT1 DD statement, or you are using an incorrect //SYSUT1 DD statement. The DB2 ECCR abends.
869
Ensure that you are using the correct //SYSUT1 DD statement, and run the job again. //SYSUT1 RECORD IS NOT A UNFORMATTED TRACE RECORD WRITTEN BY THE CAPTURE PGM While the trace formatting utility was reading records from the //SYSUT1 file, it found a record that is not an unformatted trace record. The DB2 ECCR writes the unformatted trace records. The DB2 ECCR abends. On the //SYSUT1 DD statement, specify a file that contains only //REPL2TRU output records written by the DB2 ECCR. Then, run the job again. UNEXPECTED LENGTH OF //SYSUT1 RECORD A record in the //SYSUT1 file has an incorrect length. The DB2 ECCR abends. Ensure that the //SYSUT1 DD statement specifies a file that contains only //REPL2TRU output records that the DB2 ECCR wrote. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. LENGTH OF //SYSUT1 RECORD IS TOO LARGE A record in the //SYSUT1 file has an incorrect length. The DB2 ECCR abends. Ensure that the //SYSUT1 DD statement specifies a file that contains only //REPL2TRU output records that the DB2 ECCR wrote. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED LENGTH OF DESCRIPTIVE TEXT The descriptive text contained in a //SYSUT1 record has an incorrect length. The DB2 ECCR abends. Ensure that the //SYSUT1 DD statement specifies a file that contains only //REPL2TRU output records that the DB2 ECCR wrote. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. TRACED DATA IS TOO LARGE The traced data contained in a //SYSUT1 record is larger than the DB2 ECCR expected. The DB2 ECCR abends. Ensure that the //SYSUT1 DD statement specifies a file that contains only //REPL2TRU output records that the DB2 ECCR wrote. If the problem persists, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. EXPECTED TRACE RECORD(S) ARE MISSING IN //SYSUT1 The //SYSUT1 file does not contain all of the expected trace records. Probably, you selectively copied the //REPL2TRU data set to an interim data set. The DB2 ECCR abends.
870
User Response:
Correct the problem by ensuring that all required records are in the //SYSUT1 file, and run the job again. TRACE FORMATTING IS COMPLETE The trace formatting utility processing is complete. The trace formatting utility ends. Processing continues. No action is required. CIC INTERFACE CALL FAILED The DB2 ECCR called the change interface component (CIC). However, the call failed and the CIC did not handle the error situation. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. DB2 CHANGE CAPTURE AND EDM Logger
LAST READ RBA EQUAL 0, COLD START RECOMMENDED
During a warm restart, both the DB2 ECCR checks the PowerExchange Logger for the RBA of the last record read during the previous change capture. The RBA for the current restart was zero. The restart processing is in error. Restart processing abends with a return code of 23. Use a cold start to restart the DB2 ECCR. UNABLE TO DETERMINE THE COLUMNS IN table_name The DB2 ECCR attempted to compare the PowerExchange schema for the specified table with the schema in the DB2 catalog. The ECCR could not determine the columns in the table. Surrounding messages provide more information about the error. The DB2 ECCR abends. Gather all available information about the error and contact Informatica Global Customer Support.
PWXEDM177489W DB2 CHANGE CAPTURE HAS INITIATED A COLD START Explanation: System Action: User Response: PWXEDM177490I Explanation: System Action: User Response: PWXEDM177491I Explanation: The DB2 ECCR has initiated a cold start. Either a previous cold start was unsuccessful, or an error in the change capture process requires a cold start. Restart processing continues. No action is required. A subsequent message asks you to confirm or cancel the cold start. statistics This informational message provides statistics about the DB2 ECCR change capture process. Processing continues. No action is required. statistics heading This informational message contains a report heading for statistics produced by the DB2 ECCR. This message is followed by PWXEDM177492E, which contains a row of statistics for each source table active during the change capture.
871
System Action: User Response: PWXEDM177492E Explanation: System Action: User Response: PWXEDM177493E Explanation:
Processing continues. No action is required. statistics This informational message provides statistics about the DB2 ECCR change capture process. Processing continues. No action is required. UNABLE TO task FOR table table_name, RC=rc, reason=reason. Text. The DB2 ECCR encountered an error during restart processing. The task variable specifies the ECCR task that received the error. The variable Text provides additional information about the error. The message also provides the table_name for which the error occurred, and the return_code and reason for the error. Possible values for the variable task are:

find EDMNAME get schema get active schema change schema $BLDCMD error for RETEDM $BLDCMD error for RETSCH $BLDCMD error for CHGSCH get pending schema System Action: User Response: DB2 ECCR processing continues. If the error is serious, the DB2 ECCR issues additional messages. Use the information in task and text and the return and reason codes to help you diagnose the error. For more information, review associated messages. Contact Informatica Global Customer Support. Automatic activation of schema for table table_name. Create time=timestamp1, alter time=timestamp2 The DB2 ECCR activated the schema for a DB2 source table identified by table_name. The times that the schema was created and most recently changed are indicated by the time stamps. Automatic schema activation can occur as part of the schema verification process. Processing continues. No action is required. Successful verification of {active|pending} schema for table table_name The DB2 ECCR verified the schema for the table identified by table_name. The ECCR compares the DB2 schema for the table to the corresponding schema registered with the PowerExchange repository. Schema verification completed successfully. The message also indicates whether the schema is active or pending. Processing continues. No action is required. THE START RBA SPECIFIED BY THE USER IS LESS THAN THE EDM LOGGER RBA The DB2 log RBA you specified during restart processing had a value less than the current RBA in the PowerExchange Logger. The DB2 ECCR abends.
System Action: User Response: PWXEDM177496E Explanation: System Action:
872
User Response:
Edit the STARTLOC parameter in REPL2OPT to an appropriate start RBA and run the restart job again. CAPTURE DIRECTORY: LAST READ RBA=rba OLDEST OPEN URID=urid This message displays the last read RBA and the oldest open unit-of-recovery ID (URID) from the DB2 environmental change capture routine (ECCR) capture directory. A PowerExchange Logger UOW is the same as a DB2 unit of recovery (UR). Processing continues. No action is required. Error acquiring {command|reply} buffer. Count=nnn, current size=size1, new size=size2 The DB2 ECCR detected an error when it attempted to acquire a command or reply buffer. The message provides the number of captured changes, the current size of the buffer and the new size of the buffer. The DB2 ECCR abends. Gather all of the available information about the error and contact Informatica Global Customer Support. CA NAME HAS CHANGED IN DDNAME REPL2CTL; CA NAME IS IGNORED DURING REFRESH PROCESSING The CA NAME statement specified in the REPL2CTL control file changed, and PowerExchange encountered the name change during refresh processing for the DB2 ECCR. Message number PWXEDM17500I displays the original capture name and the changed capture name found in the REPL2CTL control file. Refresh processing continues, but the changed CA name is ignored. If you do not want to use the new CA name, no action is required. If you want to process the new CA name, you must restart the DB2 ECCR. CURRENT CA NAME: ca_name1; CA NAME IN REPL2CTL: ca_name2 This message follows PWXEDM177499I, and provides additional information about that error. The CA NAME statement specified in the REPL2CTL control file changed, and PowerExchange encountered the name change during refresh processing for the DB2 ECCR. The name shown in ca_name1 identifies the capture name currently being processed by the DB2 ECCR. The name shown in ca_name2 identifies the capture name found in the REPL2CTL control file.
Refresh processing continues, but the changed CA name is ignored. If you do not want to use the new CA name, no action is required. If you want to process the new CA name, you must restart the DB2 ECCR. Registration {create timestamp|alter timestamp|create and alter timestamps} for table table_name changed to timestamp The time stamp or time stamps specified in the message have changed, but the schema matches the schema used for DB2 ECCR processing. PowerExchange automatically resets the dates for the registered table to match the DB2 date. Processing continues. No action is required.
873
The DB2 {schema|create_timestamp|alter_ timestamp|create/alter_timestamp} for table table_name does not match the {active|pending} profile schema. DB2 log time: timestamp. A report follows the message and provides details. The ECCR attempts to correct any differences. If the correction is successful, processing continues. If the correction is unsuccessful, processing ends and the ECCR generates error messages. No response is required. Changes captured for table table_name using schema with create time=timestamp1, alter time=timestamp2. This informational message is issued when the first change is captured for a particular schema registration. The message provides identifying information about the schema. Processing continues. No action is required. No Active Tables found in Repository for specified DB2 Registration Name RN=registration_name where registration_name is used to find profiles in the Repository During initialization, the DB2 ECCR did not find any active registrations that matched the DB2 ID. The DB2 ECCR abends. Register the tables for capture and then restart the ECCR. (You must register all applicable tables for capture before restarting the ECCR.) No {active|pending} schema found for table table_name for time timestamp. The active schema in the registration does not match the schema in the DB2 catalog, and no pending schema exists. The DB2 ECCR abends when it gets the first change record for this specified table. If the table should have an active schema, correct the registration and run the capture job again. Schema verification failed for table table_name The DB2 ECCR could not find a schema in the registration that matches the schema in the DB2 catalog. The DB2 ECCR abends. Recreate the capture registration so that it matches the DB2 schema. Table table_name {altered|created|dropped} at timestamp The specified table was registered in the PowerExchange repository, and PowerExchange detected that the table has been altered, created or dropped. The timestamp indicates when the function occurred. Processing continues. No action is required. LZCOMPRS BUILD FAILED, RC=rc, REASON=reason DSNAME=dsname During restart processing a build error occurred for the specified data set name. The processed log records were compressed, but the compression dictionary used during compression has been deleted or replaced. The DB2 ECCR requires the appropriate
874
compression dictionary to process the records. The return and reason codes provide additional information about the message. System Action: User Response: The DB2 ECCR abends. Restore the compression dictionary for the specified data set, and restart the ECCR. Contact Informatica Global Customer Support. {WARM|SPECIAL} START LOG RECORDS DO NOT MATCH CURRENT COMPRESSION DICTIONARY During a special start, the DB2 ECCR encountered an error when it tried to process compressed log records. The compression dictionary used during compression has been deleted or replaced. The DB2 ECCR requires the appropriate compression dictionary to process the records. The DB2 ECCR abends. Restore the compression dictionary for log records, and restart the ECCR. Contact Informatica Global Customer Support. TABLESPACE INFORMATION NOT AVAILABLE During decompression, the ECCR could not find information about the tablespace for the table being decompressed. This can occur if you specify a table for compression while the ECCR is running. The DB2 ECCR abends. Restart the DB2 ECCR using the START WARM statement. Then, run the change capture job again.
PWXEDM177518W TABLE DESCRIPTION NOT FOUND IN CAPTURE DIRECTORY Explanation: When processing DB2 log records for a table rename, the DB2 ECCR attempted to locate the row for the table being renamed in the TCAPTABLES capture directory table but did not find it. This is an internal error, because the TCAPTABLES information had been successfully located earlier during the processing of the log records for the table rename. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR - UNEXPECTED COLTYPE FOR A HEX DEFAULT VALUE The DB2 ECCR found an unexpected column type for a hexadecimal default value. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CA NAME=ca_name NOT FOUND OR IS INVALID IN //REPL2CTL The capture process name (CA NAME) statement specified in the REPL2CTL control file is missing or invalid, and PowerExchange encountered the missing or invalid name during the start of the DB2 ECCR. The DB2 ECCR abends. Provide a valid CA NAME and restart the DB2 ECCR. For more information about the REPL2CTL control file, see the PowerExchange CDC Guide for z/OS.
875
INTERNAL ERROR - INVALID CALL FUNCTION FOR X029232 The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. TCAPTABLESPACE ROW NOT FOUND IN CAPTURE DIRECTORY The capture directory describes a table that has no columns. A table must have at least one column. The DB2 ECCR abends. Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the ST record for the problematic table and starting the DB2 ECCR again without capturing updates for this table. UNEXPECTED VALUE IN UPTYPE COLUMN OF A TCAPWORK ROW The DB2 ECCR found an incorrect value in a column in a TCAPWORK row. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RETURN CODE FROM X029262 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INVALID LENGTH IN INDEX-CHANGE LOG RECORD The DB2 ECCR found an incorrect data length in a log record that describes a change in a DB2 index-change log record. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. CAPTURE-DIRECTORY OR DB2-CATALOG CAN NOT BE PROPERLY ACCESSED The DB2 ECCR cannot access a capture directory table or a DB2 catalog table. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. ROLLBACK HAS FAILED The DB2 ECCR initiated a rollback process, and the DB2 rollback failed. The DB2 ECCR abends.
876
User Response:
Use the information from the other messages associated with this error to determine the cause of the failure. Then, correct the problem, and run the job again. UNEXPECTED RETURN CODE FROM X029232 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. THIS MIGHT BE A TRANSIENT PROBLEM - TRY A WARMSTART OF THE CAPTURE PROGRAM The DB2 ECCR accessed the DB2 catalog to obtain descriptions of the primary (source) tables. The obtained descriptions are inconsistent, possibly because DDL activity is changing the table descriptions concurrently with the DB2 ECCR accesses. If it cannot get consistent descriptions after several attempts, the DB2 ECCR abends. The DB2 ECCR abends. Start the DB2 ECCR when less DDL activity is occurring. If this action does not correct the problem, collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. UNEXPECTED RETURN CODE FROM X029232 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Internal ERROR - Unrecognized datatype FOR Column column The DB2 ECCR cannot determine the data type for the specified column, while processing the data definition language (DDL) for a column definition. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Capture Program of DB2 Replication ending because of X029159 SUBTASK termination The specified subtask ended. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Error accessing Schema for Table=fully_qualified_table_name During initialization, and during processing of the REFRESH command, the DB2 ECCR obtains schema information for tables for which it needs to capture data. This information is obtained from the registration information for DB2 capture, and is accessed through the PowerExchange Agent. In the process of doing that, the ECCR was unable to acquire the schema information for a particular table. The fully-qualified table name for which schema information could not be obtained is included in the text of the message.
877
PWXEDM177533E Error accessing Schema for Table PWXEDM177533E Creator=creator_name PWXEDM177533E Table=table_name
In addition if one or the other of the creator or name are themselves longer than 80 characters, the name is continued, as in:
PWXEDM177533E Error accessing Schema for Table PWXEDM177533E Creator=long_creator_name_first_80_characters PWXEDM177533E continued_creator
PWXEDM177533E Table=long_table_name_first_80_characters PWXEDM177533E continued_name
The DB2 ECCR ends without processing any additional DB2 log data. Examine the registration status of the specified DB2 table. Look for any error messages in the DB2 ECCR and in the PowerExchange Agent that might indicate a problem with the schema information of this table. Correct any errors found in defining the schema for this table, and then restart the DB2 ECCR. If the problem persists after correcting the schema registration, or if the problem cannot be identified, contact Informatica Global Customer Support.
PWXEDM177534W Duplicate old outstanding UOW found: UOWid=uow_id Explanation: During a warm start, the DB2 ECCR was processing the list of outstanding UOWs that the Logger had recorded as being in progress from this ECCR. This list is used to ensure that the Logger is notified when these UOWs terminate, so that it can remove them from its records: otherwise they could affect restart of the DB2 ECCR, if the registration status of tables has changed since the last execution of the DB2 ECCR. The DB2 ECCR found that the UOW ID it was currently processing was a duplicate in the list received from the Logger. The UOW ID for which this condition was encountered is included in the message text. Processing continues. The duplicate UOW ID is dropped, but the original entry will still be processed. Contact Informatica Global Customer Support.
PWXEDM177535W Persistent outstanding UOW found: UR={urid|Pending}, UOWid=uow_id Explanation: During statistics processing, the DB2 ECCR produces a list of outstanding UOWs, in the same format as is produced through the URID command. However, each outstanding UOW is also examined to determine how long it has been outstanding. If any UOW is found to be outstanding for the entire duration of a statistics interval (this duration is specified at the startup of the DB2 ECCR in the STAT command), the DB2 ECCR issues this message to warn that the UOW has been outstanding for a lengthy period. This may mean that the completion of the UOW has been missed. The DB2 URID and the UOW ID assigned by the DB2 ECCR are included in the message text. The URID may contain the word PENDING, which indicates that this entry was originally obtained from information provided by the Logger during a warm start of the DB2 ECCR, not from the DB2 log data processed during this execution of the DB2 ECCR. Processing continues. If the same outstanding UOW continues to persist, you may need to examine the output from the DB2 ECCR, and from the DB2 subsystem(s) whose data it is processing, to determine why the UOW has not completed. You may need to run the DB2 utility DSN1LOGP (or equivalent) to determine if the UOW really is still outstanding. If you
878
cannot determine the reason why the UOW is still outstanding, contact Informatica Global Customer Support. PWXEDM177537E Explanation: Excessive {column name|old column name|new column name} length (len) found in table 'owner.table_name'. Truncated column name: truncated_column_name During processing of log records for the DB2 catalog, the DB2 ECCR encountered a column whose value is longer than currently supported by the DB2 ECCR. The table for which this column occurred, as well as the column name and the length of the value in that column are all included in the text of the message. This situation can only occur for a table that is defined in the repository as being one for which data should be captured. However, the DB2 ECCR can not properly record the definition of the table in its own tracking table, because of the column length. The column name option in the message occurs when a table is being added to capture during a warm start or as the result of a refresh command. The old column name and new column name options in the message occur when the DB2 ECCR processes DB2 log records for column renames. System Action: User Response: The DB2 ECCR ends. The DB2 ECCR does not support capturing changes from the table in question, because of the column length in the catalog data. You must change the table in question so that it is NOT to be captured, then warm-start the DB2 ECCR. If the problem reoccurs, contact Informatica Global Customer Support. Table 'from_owner.from_table' renamed to 'to_owner.to_table' at yyyy-mm-dd-hh.mm.ss.tttttt. During processing of log records for the DB2 catalog, the DB2 ECCR encountered a table rename. The from table name and the to table name, along with the DB2 timestamp at which the rename occurred, are all included in the text of the message. At least one of the tables is intended to be captured by the DB2 ECCR. Processing continues. This is an informational message issued to allow proper tracking of tables that the DB2 ECCR is capturing. There will be other messages indicating that a table is no longer being captured, or that it has now started to be captured. Table=owner.table now 'DATA CAPTURE CHANGES'. DB2-Log Location=rba During processing of log records, the DB2 ECCR detected that a table had acquired or lost the DATA CAPTURE CHANGES attribute. This attribute is necessary to allow the ECCR to capture data, so recording when that change in attribute occurred is important when trying to analyze what data was captured for the table, and when that capture started occurring. The name of the table for which the attribute change was detected, and the location in the DB2 log data where the change was detected, are included in the message. The message will also indicate whether the attribute was acquired (DATA CAPTURE CHANGES) or lost (DATA CAPTURE NONE). Processing continues. This is an informational message issued to allow proper tracking of tables that the DB2 ECCR is capturing. If the DATA CAPTURE CHANGES attribute was lost, determine if any changes were actually made to the table in question after that DB2 log location. If so, you may need to rematerialize any target data that uses this table as a source.
PWXEDM177540W Some DB2 catalog tables not defined with Data Capture Changes Explanation: This message indicates that one or more of five DB2 catalog tables were found NOT to have the recommended attribute DATA CAPTURE CHANGES. This message is issued during initialization. The five tables in question are SYSIBM.SYSTABLES,
879
SYSIBM.SYSCOLUMNS, SYSIBM.SYSTABLESPACE, SYSIBM.SYSFIELDS and SYSIBM.SYSCOPY. Message PWXEDM177398W will have been issued previous to this message to indicate which tables are missing the attribute. The DB2 ECCR requires this attribute to support capture for DB2 Version 8. Message PWXEDM177541W will be issued following this message to indicate that requirement. The attribute is also necessary to use the IFI306OPT statement, which can result in lower resource utilization in the DB2 ECCR. If one or more of these tables does NOT have the DATA CAPTURE CHANGES attribute, and an attempt to use the IFI306OPT statement is detected, message PWXEDM177542W will follow this one to indicate that the request has been ignored. System Action: User Response: If the level of DB2 to which the ECCR has connected is DB2 V7 or lower, initialization continues. Otherwise, the DB2 ECCR issues message PWXEDM177543E and ends. No action is required.
PWXEDM177541W Migration to DB2 V8 will not be allowed Explanation: This message is issued when the DB2 ECCR has connected to DB2 V7 or lower and found that some DB2 catalog tables are not defined with the DATA CAPTURE CHANGES attribute. The fact that some tables are missing this attribute is indicated by message PWXEDM177540W, which will have been issued previously. Which tables are missing this attribute will have been reported previously in message PWXEDM177398W. This message is issued to warn that it will not be possible to migrate to DB2 Version 8 because the DB2 ECCR requires that these tables have the DATA CAPTURE CHANGES attribute when connected to DB2 Version 8 or higher. System Action: User Response: Processing continues. To migrate to DB2 Version 8, activate the DATA CAPTURE CHANGES attribute for those tables that require it. Note that any DB2 catalog tables that currently have the DATA CAPTURE CHANGES attribute will lose it during the migration process. This message is a reminder that you must reestablish the DATA CAPTURE CHANGES attribute for these tables immediately after migrating to DB2 Version 8, and again after migrating to new-function mode in DB2 Version 8.
PWXEDM177542W Request for optimized IFI306 processing (IFI306OPT) ignored Explanation: This message is issued when the DB2 ECCR has connected to DB2 V7 or lower, and found that some DB2 catalog tables that are recommended to be defined with DATA CAPTURE CHANGES, are not defined with that attribute. The fact that some tables are missing this attribute is indicated by message PWXEDM177540W, which will have been issued previously. Which tables are missing this attribute will have been reported previously in message PWXEDM177398W. This message is issued to warn that the request to use optimized IFI306 processing cannot be honored, because the DB2 ECCR requires that these tables have the DATA CAPTURE CHANGES attribute to operate properly when using optimized IFI306 processing. System Action: Initialization continues. However, the standard IF306 processing method will be used, so the DB2 ECCR might require more resources to operate, than if the IFI306OPT specification had been honored. If you wish to use the optimized IFI306 processing option, activate the DATA CAPTURE CHANGES attribute for the tables that do not currently have it. Capture program of DB2 Replication ending - DB2 Catalog tables not Data Capture Changes This message indicates that the DB2 ECCR has connected to DB2 Version 8 or higher, and determined that one or more of five DB2 catalog tables did NOT have the required
User Response:
880
attribute DATA CAPTURE CHANGES. This message is issued during initialization. The following tables require the DATA CAPTURE CHANGES attribute:
SYSIBM.SYSTABLES SYSIBM.SYSCOLUMNS SYSIBM.SYSTABLESPACE SYSIBM.SYSFIELDS SYSIBM.SYSCOPY. Message PWXEDM177398W is also issued to indicate which tables are missing the attribute. This attribute is required for support of DB2 Version 8. System Action: User Response: The DB2 ECCR ends without processing any DB2 log data. You must activate the DATA CAPTURE CHANGES attribute for the tables that do not currently have it, before you will be able to restart the DB2 ECCR. Furthermore, you will now not be able to warm start the ECCR. Because the DB2 ECCR only recognizes the current status of the DB2 catalog tables on a cold start or special start, only that type of start will now be successful, even if the DB2 catalog tables are now all ALTERed to have the DATA CAPTURE CHANGES status. LOGGER INTERFACE ERROR - REQUEST FOR RBA AND UOW FAILED - RC=rc During a warm start of the DB2 ECCR, it attempted to get restart information from the Logger. However, an error occurred in calling module CCDCICP to get that information. The return code received from CCDCICP is included in the message. The DB2 ECCR ends without processing any DB2 log data. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Configuration not supported: Long table names registered During initialization of the DB2 ECCR or processing of the REFRESH command, the Db2 ECCR obtains the list of tables that are registered for capture. If any of the fully-qualified table names contain long parts (either the table owner, or the unqualified table name, is longer than 8 characters or 18 characters, respectively), the capture directory tables used by the DB2 ECCR must be expanded. This expansion allows the DB2 ECCR to record, in its own tables, the long table names that it is supposed to capture. However, the DB2 ECCR determined that its tables had not been properly expanded. In this case, message PWXEDM177549I will have been issued during initialization to indicate which table(s) were not expanded. Alternatively, the DB2 ECCR determined that its capture directory tables had been expanded, but that it was connected to a DB2 that could not support such long table names; the level of DB2 was prior to DB2 Version 8 new-function mode. In this case, message PWXEDM172820I will indicate to what level of DB2 the ECCR connected during initialization. User Response: System Action: The DB2 ECCR ends without processing any DB2 log data. Remove from capture the tables that have long name parts, and restart the DB2 ECCR. If the problem persists after removing all the tables with long name parts, contact Informatica Global Customer Support. Configuration not supported: Long column names registered During initialization of the DB2 ECCR or processing of the REFRESH command, the DB2 ECCR obtains the list of tables that are registered for capture. If any of the tables contain columns with long names (a column name longer than 18 characters), it is necessary that the capture directory tables used by the DB2 ECCR be expanded. This
881
expansion allows the DB2 ECCR to record, in its own tables, the long column names in the tables that it is supposed to capture. However, the DB2 ECCR determined that its tables had not been properly expanded. In this case, message PWXEDM177549I will have been issued during initialization to indicate which table(s) were not expanded. Alternatively, the DB2 ECCR determined that its capture directory tables had been expanded, but that it was connected to a DB2 that could not support such long column names; the level of DB2 was prior to DB2 Version 8 new-function mode. In this case, message PWXEDM172820I will indicate what level of DB2 the ECCR connected to, during initialization. User Response: The DB2 ECCR ends without processing any DB2 log data. Remove from capture the tables that have columns with long names, and restart the DB2 ECCR. If the problem persists after removing all the tables with long column names, contact Informatica Global Customer Support. PWXEDM177548E Explanation: Incorrect number of columns for table table. Expected exp_cols columns, DESCRIBE returned desc_cols columns During initialization, the DB2 ECCR examines the status of the capture directory tables, to determine if they have been updated to allow for full support for DB2 Version 8. For example, some columns need to be enlarged to hold longer table and column names allowed in DB2 Version 8 and higher. While verifying the status of the capture directory tables, the ECCR determined that one of its tables did not have the expected number of columns. The capture directory table (unqualified_table_name) for which the problem was detected, along with the number of columns it expected to see in this table (exp_cols), and the number actually in the table (desc_cols), as determined by doing a DESCRIBE on that table, are included in the message. User Response: The DB2 ECCR ends without processing any DB2 log data. Examine the definition of the capture directory tables used by the DB2 ECCR, and make sure that they were properly defined during the installation of the product. Correct any errors found in defining the tables, then restart the DB2 ECCR. If the problem persists after correcting the table definitions, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177549I Explanation: Capture Directory table table {has|has not} been expanded to fully support {DB2 V8|DB2 V9 and higher} During initialization, the DB2 ECCR examines the status of the capture directory tables, to determine if they have been updated to allow for full support for DB2 Version 8 or DB2 Version 9.1. For example, some columns need to be enlarged to hold longer table and column names allowed in DB2 Version 8 and higher. This message indicates whether or not each capture directory table now has the expanded definition. Processing continues. This is an informational message issued to allow users to identify whether the capture directory tables have been correctly defined for full support of DB2 Version 8 or DB2 Version 9.1. The DB2 ECCR issues this message at least once, identifying the highest level of DB2 that the capture directory tables support and, if applicable, do not yet support. Until all capture directory tables have been expanded, the DB2 ECCR cannot fully support DB2 Version 8 and long table and column names. In this situation, the DB2 ECCR abends when it encounters tables with long names or long column names that are registered for capture.
882
Similarly, the DB2 ECCR cannot fully support DB2 Version 9.1 unless all capture directory tables have been expanded. The DB2 ECCR requires expanded capture directory tables to support schema versioning in tables that are in Reordered Row Format (RRF) and to support tables with clone tables that have been exchanged. If the capture directory tables are not expanded, the DB2 ECCR may abend when it encounters schema versioning with RRF tables. For clone tables, the DB2 ECCR may not capture data correctly for the tables. PWXEDM177550E Explanation: Unexpected column (column_name) found in DESCRIBE data for table table During initialization, the DB2 ECCR examines the status of the capture directory tables, to determine if they have been updated to allow for full support for DB2 Version 8. For example, some columns need to be enlarged to hold longer table and column names allowed in DB2 Version 8 and higher. While verifying the status of the capture directory tables, the ECCR determined that one of its tables had a column that it did not expect. The capture directory table for which the problem was detected, along with the name of the column that was not expected to exist are included in the message. The DB2 ECCR ends without processing any DB2 log data. Examine the definition of the capture directory tables used by the DB2 ECCR, and make sure that they were properly defined during the installation of the product. Correct any errors found in defining the tables, then restart the DB2 ECCR. If the problem persists after correcting the table definitions, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177551E Explanation: System Action: User Response: SQL ERROR: OPERATION=operation TABLE=table The DB2 ECCR encountered an SQL operation error while accessing the specified table name. The DB2 ECCR abends. Examine any messages accompanying this one (particularly any DB2 messages that follow it) and determine what the underlying problem is. Correct the problem, then restart the DB2 ECCR. If the problem persists after taking corrective action, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177552I Explanation: Directory Tables expanded to support {DB2 V8|DB2 V9} New-Function Mode During initialization, the DB2 ECCR verifies whether the capture directory tables have been expanded to fully support DB2 Version 8 or DB2 Version 9.1. For DB2 Version 8 and higher, some columns need to be enlarged to hold longer table and column names. For DB2 Version 9.1 and higher, additional columns need to be added to some of the capture directory tables. This message indicates that all capture directory tables have been updated correctly. Therefore, the DB2 ECCR can fully support DB2 Version 8 new-function mode or DB2 Version 9.1 new-function mode, when connected to that level or higher. The DB2 ECCR issues this message twice if the Capture Directory tables have been expanded appropriately, once for DB2 Version 8 and once for DB2 Version 9.1. System Action: User Response: Processing continues. This is an informational message issued to allow users to identify whether the capture directory tables have been correctly defined for full support of DB2 Version 8 or DB2 Version 9.1.
PWXEDM177553W Table 'owner.table' Version changed from X'nnnn' to X'vvvv' at time_stamp Explanation: During processing of log records, the DB2 ECCR detected that the version of a table had changed. The version of the table defines what level of schema is being used for the table.
883
DB2 increments the table version when the data type of an existing column is altered using the following type of SQL statement: ALTER TABLE table ALTER column_name SET DATA TYPE
Note: Altering an existing VARCHAR column to increase its length does not always cause
DB2 to increase the version for the table in SYSIBM.SYSTABLES. The type of column data-type alteration reported in this message can only occur in DB2 Version 8 in new-function mode, or higher. The fully-qualified name of the table, the old and new values for the Version column, and the timestamp in the DB2 log record where this change occurred, are all included in the text of the message. System Action: Processing continues. However, if any log data is encountered that either, has a mixture of schema definitions, or, includes a schema definition that the DB2 ECCR cannot interpret, the DB2 ECCR will terminate abnormally. This is a warning message issued to indicate that the DB2 ECCR detected a schema change that might later cause abnormal termination of the ECCR. If the DB2 ECCR does abnormally terminate, you may be able to resolve the problem by performing a REORG on the table in question, because that will change all rows in the table to the same schema.
User Response:
PWXEDM177554W Conflicting schema versions for table 'owner.table' at DB2 log location = rba, Before image = X'bbbb', After image = X'aaaa' Explanation: During processing of log records describing an update operation, the DB2 ECCR detected that the before image of the update had been recorded under a different version than the after image had been recorded. The version of the table defines what level of schema is being used for the table. DB2 increments the table version when the data type of an existing column is altered using the following type of SQL statement: ALTER TABLE table ALTER column_name SET DATA TYPE
DB2 to increase the version for the table in SYSIBM.SYSTABLES. The type of column data-type alteration reported in this message can only occur in DB2 Version 8 in new-function mode, or higher. The fully-qualified name of the table, and the versions of schema under which the before image and after image were recorded, along with the DB2 log location of the record that contained the new schema version, are all included in the text of the message. System Action: Processing continues. However, if while processing the log records in which the ECCR detected multiple schema versions, the DB2 ECCR determines that it cannot interpret one of the schema versions, it will terminate abnormally. This is a warning message issued to indicate that the DB2 ECCR detected a schema version that might cause abnormal termination of the ECCR later. If the DB2 ECCR does abnormally terminate, you must do the following:

User Response:
delete the capture registration for the table warm-start the DB2 ECCR
To start capturing data for this table, you may need to perform a REORG on the table. The REORG operation changes all rows in the table to the same schema version. If the problem reoccurs, please contact Informatica Global Customer Support. PWXEDM177555W Unexpected schema version for table 'owner.table' at DB2 log location = rba, log version = X'nnnn', expected version = X'vvvv' Explanation: During processing of log records, the DB2 ECCR found data for a table that had been recorded under a different version than expected. The version of the table defines what level of schema is being used for the table. DB2 increments the table version when the data type of an existing column is altered using the following type of SQL statement: ALTER TABLE table ALTER column_name SET DATA TYPE
DB2 to increase the version for the table in SYSIBM.SYSTABLES. The type of column data-type alteration reported in this message can only occur in DB2 Version 8 in new-function mode, or higher. The fully-qualified name of the table, the DB2 log location of the record that contained the new version, the version found in the log record, and the version of schema that had been expected (which is obtained from the DB2 catalog) are all included in the text of the message. System Action: Processing continues. However, because the version of the schema may have changed, it is possible that the DB2 ECCR will terminate abnormally. This would occur if the DB2 ECCR cannot interpret the log data using the schema it has on record for this table. This is a warning message issued to indicate that the DB2 ECCR detected a schema version that might cause abnormal termination of the ECCR later. If the DB2 ECCR does abnormally terminate, you must do the following:
User Response:
delete the capture registration for the table warm-start the DB2 ECCR To start capturing data for this table, you may need to perform a REORG on the table. The REORG operation changes all rows in the table to the same schema version. If the problem reoccurs, please contact Informatica Global Customer Support. PWXEDM177556E Explanation: UNACCEPTABLE ERROR WHILE ACCESSING THE DB2 LOG The DB2 ECCR issued an IFCID 306 READS call, but received an unacceptable combination of return code and reason code. Additional messages will be issued to indicate either the specific return code and reason code that were encountered, or to describe the error based on the meaning of the return code and reason code. The DB2 ECCR ends without processing any additional DB2 log data. Examine the other messages issued at the time of the abend to determine the fundamental problem. Correct any errors described by these messages, then restart the ECCR. If the problem persists after correcting the errors, or if the problem cannot be identified, contact Informatica Global Customer Support. IFI RC=0 WITH IFCABM=0 The DB2 ECCR issued an IFCID 306 READS call, and received a return code of zero. However, while examining the data returned, it was found that the length of the data returned (IFCABM) was zero. This indicates a logical error in the DB2-supplied IFCID 306 interface. The DB2 ECCR ends without processing any additional DB2 log data. Examine any other messages that may have been issued at the time of the abend to try to determine the fundamental problem, including messages or abends in the DB2 subsystem to which the DB2 ECCR connects. Correct any errors described by these messages, then restart the ECCR using a WARM start. If the problem persists after correcting the errors, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177558E Explanation: REQUESTED LOG RECORD IS TOO OLD {- LOG POSITION=rba} The DB2 ECCR issued an IFCID 306 READS call, and received a reason code of x'00E60873', which indicates that the requested RBA or LRSN is too old. For example, it is no longer recorded in the DB2 BSDS. This error can also occur if the subsystem to which the DB2 ECCR is connected has been migrated into and then back out of datasharing mode, and the RBA requested has not been recorded by DB2 because the switch back to non-datasharing mode. If the READS request issued by the DB2 ECCR was
885
for a specific RBA or LRSN, the value supplied by the ECCR is included in the text of the message. System Action: User Response: The DB2 ECCR ends without processing any additional DB2 log data. If the DB2 ECCR was performing a special start, the requested RBA or LRSN will have been explicitly specified in the STARTLOC operand of the START control statement in the REPL2OPT file. If so, the value may have been specified incorrectly, in which case you should correct the STARTLOC value and restart the DB2 ECCR. If the DB2 ECCR was performing a WARM start, the requested RBA or LRSN is obtained from the PowerExchange Logger. Use the PowerExchange Logger DISPLAY command to determine what would have caused the PowerExchange Logger to supply an unusable restart point for the ECCR. It may be possible to remove, using the PowerExchange Logger RESOLVE_INDOUBT command, an outstanding UOW that originated in this ECCR. If so, this could change the restart point for the ECCR to a usable value, in which case you should be able to warm start the DB2 ECCR again. If this message is issued during a COLD start of the DB2 ECCR, or while it is running after a successful WARM, COLD or special start, examine any other messages that may have been issued at the time of the abend to try to determine the fundamental problem, including messages or abends in the DB2 subsystem to which the DB2 ECCR connects. Correct any errors described by these messages, then restart the ECCR using a WARM start. If the problem persists after performing the steps described above, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177559E Explanation: UNEXPECTED {LENGTH|NUMBER|OFFSET} IN control_block_field The DB2 ECCR successfully issued an IFCID 306 READS call, but while examining the output provided, it found an unexpected situation in the format or content of the data. The control block field in the READS output in which the error was found will be indicated in the text of the message, and will be one of:
QWT01R1L QWT01R1N QWT01R1O QWT02R1L QWT02R1N QWT02R1O System Action: User Response: The DB2 ECCR ends without processing any additional DB2 log data. This message indicates that the data supplied by DB2 from an IFCID 306 READS call was incorrectly formatted. Examine any other messages that may have been issued at the time of the abend to try to determine the fundamental problem, including messages or abends in the DB2 subsystem to which the DB2 ECCR connects. If these messages do indicate the fundamental problem, correct any errors described by these messages, then restart the ECCR using a WARM start. If the problem persists after performing the steps described above, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177560E Explanation: ZERO RECORD OCCURRENCES IN QW0306CT The DB2 ECCR successfully issued an IFCID READS call, but while examining the output provided, it found that the count of data records returned (QW0306CT) was zero. This indicates a logical error in the DB2-supplied IFCID 306 interface. The DB2 ECCR ends without processing any additional DB2 log data. Examine any other messages that may have been issued at the time of the abend to try to determine the fundamental problem, including messages or abends in the DB2 subsystem
886
to which the DB2 ECCR connects. Correct any errors described by these messages, then restart the ECCR using a WARM start. If the problem persists after correcting the errors, or if the problem cannot be identified, contact Informatica Global Customer Support. PWXEDM177561E Explanation: UNEXPECTED LENGTH OF IFI RECORD The DB2 ECCR successfully issued an IFCID 306 READS call, but while examining the output provided, it found that the length of all of the data records returned (QWIWHDRL) either was zero, or did not match the overall length of the data returned. This indicates a logical error in the DB2-supplied IFCID 306 interface. The DB2 ECCR ends without processing any additional DB2 log data. Examine any other messages that may have been issued at the time of the abend to try to determine the fundamental problem, including messages or abends in the DB2 subsystem to which the DB2 ECCR connects. Correct any errors described by these messages, then restart the ECCR using a WARM start. If the problem persists after correcting the errors, or if the problem cannot be identified, contact Informatica Global Customer Support. ERROR WHILE READING DB2 LOG -- IFI RC/RSNC=rc/reason The DB2 ECCR issued an IFCID 306 READS call, but the return code (rc) and/or reason code (reason) that resulted were unacceptable. This message will generally be preceded by one or more other messages issued by the DB2 ECCR that will provide additional information about the problem. The DB2 ECCR ends without processing any additional DB2 log data. Examine any other messages that may have been issued at the time of the abend to try to determine the fundamental problem, including messages or abends in the DB2 subsystem to which the DB2 ECCR connects. Correct any errors described by these messages, then restart the ECCR using a WARM start. If the problem persists after correcting the errors, or if the problem cannot be identified, contact Informatica Global Customer Support.
PWXEDM177563W No Begin Unit-of-Recovery for reason, UR=urid DB2 log location lrsn/mem_id Explanation: During processing of UR-type log records, the DB2 ECCR encountered a UR record for which there was not begin UR record.
Note: This situation might occur normally unless this is a WARM start after a successful
QUIESCE shutdown of the ECCR. On a COLD or SPECIAL start, or on a WARM start after a non-QUIESCE shutdown, in-flight units-of-work could exist at the start point. When the ECCR processes the UR records for those UOWs as they terminate, the ECCR issues this warning message. In the message text:
reason is the description of current record with one of the following values: Begin Phase1 End Phase1 Begin Phase2 Phase 1/2 Tran End Todo End Phase2 End Abort End Redo End Undo urid is the DB2-assigned URID. lrsn/mem_id is the LRSN and member ID of current log record where this URID was encountered.
887
User Response: System Action:
Processing continues. If this message occurs at times other than restart, contact Informatica Global Customer Support.
PWXEDM177564W Possible missing End Commit2 for UR=urid (lrns/mem_id) Explanation: The DB2 change capture program was processing a UR record for a unit of work (UOW) when it detected that a different UOW was in a questionable state, and might possibly be one where the End Commit2 record had not, and never would be, encountered. For this condition to be detected, the persistent outstanding UOW must already have begun commit processing, indicating that the Begin Phase2 UR record or the Phase 1/2 Transition UR record was already encountered for that UOW. This detection also only occurs if the DB2 capture program is reading at the very edge of the DB2 log data. In the message text:
urid is the DB2-assigned URID for the potential persistent UOW. lrsn/mem_id is the LRSN and member ID of current log record where this URID was encountered. System Action: This message is followed by message PWXEDM177565W, which documents the last log record type that was encountered for this UOW, along with the current DB2 log location at which this problem was encountered. Processing continues. Contact Informatica Global Customer Support. To diagnose this problem, it may be necessary to generate an SVC dump for the DB2 ECCR and any started tasks for the DB2 subsystem (of all the members, in the case of DB2 datasharing). Additional information that might be required would include JES output from the DB2 ECCR and the DB2 subsystem(s), output from DB2 utility DSN1LOGP, and copies of the archive logs that contain the log data where this problem was encountered.
User Response:
PWXEDM177565W Last operation operation, current DB2 log location lrsn/mem_id Explanation: The message provides additional information about the state of the DB2 change capture program at the point where either message PWXEDM177564W or PWXEDM177566W were issued. Specifically, the message includes a text description of the last operation or log record that was processed for the unit-of-work in question, along with the current DB2 log location when this condition was detected. In the message text:
operation is the last operation or log record type encountered for this URID and has one of the following values: Data Record Display Command Term command End UOW Begin UOW Abort UOW Unknown type Find Oldest Build hash tab Stats display Begin Phase1 End Phase1 Begin Phase2 Phase 1/2 Tran End Todo
888
lrsn/mem_id is the LRSN and member ID of current log record where this condition was detected.
Processing continues. See the description of message PWXEDM177564W or PWXEDM177566W for further information.
PWXEDM177566W No prior type for desc for UR=urid (lrsn/mem_id) Explanation: The DB2 ECCR was processing a UR record for a unit-of-work when it detected that the proper sequence of UR records had not been received. This could possibly mean that an intermediate UR record (such as a Begin Phase2 record, or a Phase 1/2 Transition record) had not been encountered. The URID for the potentially incorrect unit-of-work, along with the log location where the beginning of this UOW was encountered, are all included in the text of the message. In the message text:
type describes the operation or record type that was expected to have been encountered prior to the current record for this URID. The value is one of the following: Begin phase1 Phase 1/2 Tran descr describes the current record. The value will be End Phase2. urid is the DB2-assigned URID. lrsn/mem_id is the LRSN and member ID of current log record where the Begin UR for this URID was encountered. Currently, this message is only issued when End Phase2 records are being processed. This message is followed by message PWXEDM177565W, which documents the last log record type that was encountered for this UOW, along with the current DB2 log location at which this problem was encountered. System Action: Processing continues. Because the End Phase2 records was found for this unit-of-work, the UOW will be captured correctly, and will be available for further processing. However, because some of the expected UR records were not encountered, it is possible that some data records were also missed, and therefore would not have been captured. Contact Informatica Global Customer Support. To diagnose this problem, it may be necessary to generate an SVC dump for the DB2 ECCR and any started tasks for the DB2 subsystem (of all the members, in the case of DB2 datasharing). Additional information that might be required would include JES output from the DB2 ECCR and the DB2 subsystem(s), output from DB2 utility DSN1LOGP, and copies of the archive logs that contain the log data where this problem was encountered. Capture Directory or DB2 catalog can not be properly accessed The DB2 ECCR cannot access a table either in the capture directory or in the DB2 catalog. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Correct the problem and restart the DB2 ECCR. Rollback has failed The DB2 ECCR initialized a rollback process, and the DB2 rollback failed. The DB2 ECCR abends. Use the information from the other messages associated with this error to determine the cause of the failure. Correct the problem and restart the DB2 ECCR.
User Response:
889
Internal error - Invalid call function for X029233 The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177570W Column description not found in Capture Directory Explanation: The DB2 ECCR could not find an expected row in the DB2 ECCR capture directory TCAPCOLUMNS table. Probably, DDL activity is changing the table descriptions concurrently with the DB2 ECCR access. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177571W Field description not found in Capture Directory Explanation: The DB2 ECCR could not find an expected row in the DDB2 ECCR capture directory TCAPFIELDS table. Probably, DDL activity is changing the table descriptions concurrently with the DB2 ECCR access. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177572W Table description not found in Capture Directory Explanation: During processing of DB2 log records for a column rename, the DB2 ECCR was unable to locate the row for the table containing the column being renamed in capture directory TCAPTABLES table. This is an internal error, because the TCAPTABLES information had been successfully located earlier during the initialization of the DB2 ECCR. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177573W Inconsistent definitions for full_table_name - or Inconsistent definitions for table Creator: creator_name Table: table_name - or Inconsistent definitions for table Creator: creator_name_.... continued_creator_name Table: table_name_.... continued_table_name Explanation: The DB2 ECCR attempted to obtain a description of the specified table from the in the DDB2 ECCR capture directory TCAPTABLES table, but the obtained description was inconsistent. Probably, DDL activity is updating the catalog descriptions concurrently with the DB2 ECCR access. The DB2 ECCR issues the modified formats of the message in the following cases:
If the fully-qualified table name is in excess of 70 characters long If either the creator name or table name are longer than 80 characters
Each part of the fully-qualified table name is on a separate line in the message. System Action: User Response: The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Column 'from_column' renamed to 'to_column' in table 'owner.table' at yyyy-mm-ddhh.mm.ss.mmmmmm During processing of log records for the DB2 catalog, the DB2 ECCR encountered a column rename. The from column name and the to column name, along with the fullyqualified table name that contains the column being renamed, and the DB2 timestamp at which the rename occurred, are all included in the text of the message. This message is only issued if the table is registered for captured by the DB2 ECCR. Processing continues. The DB2 ECCR issues this informational message to allow proper tracking of the tables being captured. However, a schema change has been made to a table being captured. You must change the capture registration for the table to include the new column name. For more information about DB2 schema changes, see the PowerExchange CDC Guide for z/OS. Unexpected return code from X029233 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. INTERNAL ERROR: UNEXPECTED RETURN CODE FROM PX029025 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
PWXEDM177577W Capture for table 'owner.table' deferred due to pending table alteration Explanation: The DB2 ECCR detected a new table for which changes are to be captured during initialization following a warm start, special start, or a REFRESH command. The DB2 ECCR determined that, at the point in time that it would start or resume processing DB2 log records, the new table was being altered. As a result, no accurate and consistent information about the definition of the new table could be obtained. Processing continues. However, data for the table will not be captured until the DB2 log records that contain the latest changes to the definition of the table are encountered. At that point, the DB2 ECCR will start capturing data for the table. The DB2 ECCR issues this informational message to allow proper tracking of the tables being captured. Clone 'owner.table' is {added to|dropped from|exchanged with} table 'owner.table' at yyyymm-dd-hh.mm.ss.mmmmmm During processing of DB2 log records, the DB2 ECCR detected that a clone table has been added, dropped, or exchanged with its base table. The DB2 ECCR is currently capturing changes for the base table.
System Action:
User Response:
891
System Action:
Processing continues. The DB2 ECCR continues to capture changes for the base table but does not capture changes for the cloned table associated with that base table. If the clone and the base table have been exchanged, the DB2 ECCR now captures changes from the new instance of the table. The DB2 ECCR issues this informational message to allow proper tracking of the tables being captured. However, if the clone and the base table have been exchanged, additional action may be required. The change data that the DB2 ECCR captures from the new instance of the table may be inconsistent with the change data that has been captured from the previous instance of the table. If so, you may encounter problems when you attempt to apply the newly-captured change data to the targets. To resolve this inconsistent data, you may need to rematerialize any targets of this data. INVALID LENGTH OF A SYSCOPY COLUMN VALUE The DB2 ECCR found an incorrect length for a value in a column in the SYSCOPY table. This is an internal error. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. ---START ACCESS TO SCHEMA INFORMATION IN USER TABLE DATASETS During initialization, the DB2 ECCR has detected that it needs to obtain schema version information from a tablespace or partition data set of table registered for capture. for which it intended to capture changes. The DB2 ECCR issues this message to indicate that this process has started. Processing continues. The DB2 ECCR issues this informational message to provide progress information during the initialization process. ---ACCESS TO SCHEMA INFORMATION IN USER TABLE DATASETS COMPLETE During initialization, the DB2 ECCR has detected that it needs to obtain schema version information from a tablespace or partition data set of table registered for capture. for which it intended to capture changes. The DB2 ECCR issues this message to indicate that this process has completed. Processing continues. The DB2 ECCR issues this informational message to provide progress information during the initialization process. Unexpected return code from X029234 The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
User Response:
PWXEDM177583W Dynamic allocation failed for dataset "dsn", RC=rc, S99ERROR=s99error, S99INFO=s99info. Explanation: The DB2 ECCR needed to obtain schema information for a table, which it does by dynamically allocating and reading the tablespace data set or partition data set(s) for the table. However, the dynamic allocation request failed. The DB2 ECCR only dynamically
892
allocates the tablespace or partition data set(s) for a table if you are using DB2 Version 9.1 or higher. The message text includes the data set name, and the return code, error reason code, and information code returned from dynamic allocation. The DB2 ECCR also issues message PWXEDM177584W to identify the table, tablespace and partition number that triggered the dynamic allocation request. System Action: The DB2 ECCR continues to capture changes for the table, even though some schema version information may be unavailable. If the DB2 ECCR encounters log records for the table recorded using an older schema version, it may be unable to interpret that log data. In this case, the DB2 ECCR issues message PWXEDM177456E or PWXEDM177460E and does one of the following:

abends, if the REPL2OPT EC PERMIL statement value is 0 or has been exceeded discard the log records, if the REPL2OPT EC PERMIL statement value has not be exceeded
User Response:
The DB2 ECCR issues this warning message to indicate that there could be a problem capturing changes for this table. If the DB2 ECCR encounters errors capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E. To prevent the DB2 ECCR from either failing or discarding change data, determine the reason for the dynamic allocation failure using the return and reason codes provided in this message. If you reorganize the tablespace or partitions after a schema change that causes the schema version number change, all rows in the table will be recorded using the new schema version avoiding this problem. For additional assistance, contact Informatica Global Customer Support.
PWXEDM177584W Schema version processing skipped for 'owner.table', in tablespace database.tablespace, partition partnum. Explanation: The DB2 ECCR attempted to dynamically allocate the tablespace or partition data set(s) for the table to obtain schema version information. The DB2 ECCR dynamic allocation request failed. The message text includes the following information about the table that triggered the dynamic allocation request:

the fully-qualified table name the name of the database and tablespace containing the table the partition number, which is zero if the tablespace is not partitioned Previously, the DB2 ECCR issued message PWXEDM177583W containing information about the failed dynamic allocation request. The DB2 ECCR only dynamically allocates the tablespace or partition data set(s) for a table if you are using DB2 Version 9.1 or higher. System Action: The DB2 ECCR continues to capture changes for the table, even though some schema version information may be unavailable. If the DB2 ECCR encounters log records for the table recorded using an older schema version, it may be unable to interpret that log data. In this case, the DB2 ECCR issues message PWXEDM177456E or PWXEDM177460E and does one of the following:
abends, if the REPL2OPT EC PERMIL statement value is 0 or has been exceeded discard the log records, if the REPL2OPT EC PERMIL statement value has not be exceeded User Response: The DB2 ECCR issues this warning message to indicate that there could be a problem capturing changes for this table. If the DB2 ECCR encounters errors capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E. To prevent the DB2 ECCR from either failing or discarding change data, determine the reason for the dynamic allocation failure in message PWXEDM177583W.
If you reorganize the tablespace or partitions after a schema change that causes the schema version number change, all rows in the table will be recorded using the new schema version avoiding this problem. For additional assistance, contact Informatica Global Customer Support. PWXEDM177585W Dynamic unallocation failed for dataset 'dsn', DDname=dd_name, RC=rc, S99ERROR=s99erro, S99INFO=s99info. Explanation: The DB2 ECCR needed to obtain schema information for a table, which it does by dynamically allocating and reading the tablespace or partition data set(s) for the table. After processing the schema version information in the data set, the DB2 ECCR attempt to dynamically unallocate the data set failed. The DB2 ECCR only dynamically allocates the tablespace or partition data set(s) for a table if you are using DB2 Version 9.1 or higher. The message text includes the data set name that was being unallocated, and the return code, error reason code and information code returned from dynamic allocation. System Action: Processing continues. However, the failure to unallocate the data set may lead to resource problems in the DB2 ECCR later on. For example, the TIOT entry that was used when the data set was allocated may not be freed, which could lead to the DB2 ECCR exhausting the available space in the TIOT. Examine the return and reason codes provided in this message to determine the reason for the unallocation failure. You may need to recycle the DB2 ECCR to prevent future problems caused by the failure to unallocate the data set. If you are unable to determine the reason the dynamic unallocation request failed, contact Informatica Global Customer Support. Internal error - Invalid call function for X029234 The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Internal error - Invalid {R2PTA|CCDTS|CCDTP} control block address or contents The DB2 ECCR needed to obtain schema version information for a table, which it does by reading the tablespace or partition dataset(s) for the table. While processing the schema version information in the data set, the DB2 ECCR detected an invalid control block structure in its own control blocks. The error message identifies the specific control block in which the error was detected. This problem only occurs if you are using DB2 Version 9.1 or higher. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support. Errors in {Pageset header|OBDREC record} in 'dsn' for 'owner.table' - error_reason. The DB2 ECCR needed to obtain schema version information for a table, which it does by reading the tablespace data set or partition data set(s) for the table. While processing the schema version information for the table, the DB2 ECCR found invalid data in the pages in the data set. This problem only occurs if you are using DB2 Version 9.1 or higher. The message text includes the type of record being processed, the tablespace or partition data set name, the fully-qualified table name, and a description of the data error the DB2 ECCR detected. The error_reason variable has one of the following values:
User Response:
Inconsistent data in page
894
Page not from a file page set Page is not a file set header Not correct DBID/PSID in Hdr Page size is not correct Too many entries found Page number does not match Page is not System OBDREC page Record ID not in ID Map ID Map entry is a free entry Record is not a Record OBD Wrong OBID found in record OBD OBD record suffix invalid Wrong schema version in OBDREC Dupl. schema versions, diff. len No OBDREC records to read Tablespace page size invalid Tablespace DSSIZE invalid System Action: User Response: The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Also, run and collect the output from DB2 utility DSN1PRNT for the tablespace or partition data set. Then, contact Informatica Global Customer Support.
PWXEDM177589W Excessive schema version entries bypassed for 'owner.table' in dataset 'dsn'. Explanation: The DB2 ECCR needed to obtain schema version information for a table, which it does by reading the tablespace or partition data set(s) for the table. While processing the schema version information for the table, the DB2 ECCR found too many schema versions. The maximum number that the DB2 ECCR can record is 100. The message text includes the fully-qualified table name, along with the name of the tablespace or partition data set being processed at the time the problem was encountered. This problem only occurs if you are using DB2 Version 9.1 or higher. System Action: The DB2 ECCR only records information about the 100 most recent schema versions for the table. If the DB2 ECCR encounters log records created by DB2 using older schema versions, it may be unable to interpret that log data. In this case, the DB2 ECCR issues message PWXEDM177456E or PWXEDM177460E and does one of the following:
abends, if the REPL2OPT EC PERMIL statement value is 0 or has been exceeded discard the log records, if the REPL2OPT EC PERMIL statement value has not be exceeded For example, if the tablespace or partitions had been reorganized after the schema change that caused the schema version number to change, then there should be no rows in the table that were recorded using an older schema version. If the ECCR DOES encounter log records for the table that were recorded using an older schema version, it may be unable to interpret that log data. User Response: The DB2 ECCR issues this warning message to indicate that there could be a problem capturing log data for the table in question. However, the DB2 ECCR may still be able to capture data for the table. If the DB2 ECCR encounters errors capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E. If you reorganize the tablespace or partitions after a schema change that causes the schema version number change, all rows in the table will be recorded using the new schema version avoiding this problem.
895
PWXEDM177590W Schema version entries bypassed for 'owner.table' in dataset 'dsn' due to access violation. Explanation: The DB2 ECCR needed to obtain schema version information for a table, which it does by reading the tablespace or partition data set(s) for the table. The DB2 ECCR failed to open the data set because it does not have the necessary access authority. The message text includes the fully-qualified table name, along with the name of the data set being opened.MVS also issues messages to indicate that the open of this data set failed. This problem only occurs if you are using DB2 Version 9.1 or higher. System Action: The DB2 ECCR continues to capture changes for the table, even though some schema version information may be unavailable. If the DB2 ECCR encounters log records for the table recorded using an older schema version, it may be unable to interpret that log data. In this case, the DB2 ECCR issues message PWXEDM177456E or PWXEDM177460E and does one of the following:
abends, if the REPL2OPT EC PERMIL statement value is 0 or has been exceeded discard the log records, if the REPL2OPT EC PERMIL statement value has not be exceeded User Response: The DB2 ECCR issues this warning message to indicate that there could be a problem capturing log data for the table in question. However, the DB2 ECCR may still be able to capture data for the table. If the DB2 ECCR encounters errors capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E. To prevent this problem, update the access rules for the data set. The user ID under which the DB2 ECCR executes needs READ access to the data set listed in the message. If this message persists after the access rules have been updated to provide READ access, contact Informatica Global Customer Support. PWXEDM177591W Schema version entries bypassed for 'owner.table' in dataset 'dsn' due to open abend abend_code. Explanation: The DB2 ECCR needed to obtain schema version information for a table, which it does by reading the tablespace or partition data set(s) for the table. When the DB2 ECCR attempted to open the data set, an abend occurred. The DB2 ECCR intercepted and recovered from the abend. The message text includes the fully-qualified table name, along with the name of the data set being opened, and the abend code for the abend that occurred. MVS may also issue messages to indicate that the open of the data set failed. This problem only occurs if you are using DB2 Version 9.1 or higher. System Action: The DB2 ECCR continues to capture changes for the table, even though some schema version information may be unavailable. If the DB2 ECCR encounters log records for the table recorded using an older schema version, it may be unable to interpret that log data. In this case, the DB2 ECCR issues message PWXEDM177456E or PWXEDM177460E and does one of the following:
abends, if the REPL2OPT EC PERMIL statement value is 0 or has been exceeded discard the log records, if the REPL2OPT EC PERMIL statement value has not be exceeded User Response: The DB2 ECCR issues this warning message to indicate that there could be a problem capturing log data for the table in question. However, the DB2 ECCR may still be able to capture data for the table. If the DB2 ECCR encounters errors capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E. Use the return and reason codes provided in this message to determine the reason for the abend during open. If you are unable to determine the reason for the abend, contact Informatica Global Customer Support.
896
PWXEDM177592W Schema version entries bypassed for 'owner.table' in dataset 'dsn' - DSSIZE value unavailable. Explanation: The DB2 ECCR needed to obtain schema version information for a table, which it does by reading the tablespace or partition data set(s) for the table. However, the DB2 ECCR detected that columns added to the capture directory tables to support the schema version contain default values instead of the correct values from the DB2 catalog tables. The message text includes the fully-qualified table name, the name of the data set, and a description of what data was not available. This problem only occurs if you are using DB2 Version 9.1 or higher. System Action: The DB2 ECCR continues to capture changes for the table, even though some schema version information may be unavailable. If the DB2 ECCR encounters log records for the table recorded using an older schema version, it may be unable to interpret that log data. In this case, the DB2 ECCR issues message PWXEDM177456E or PWXEDM177460E and does one of the following:
abends, if the REPL2OPT EC PERMIL statement value is 0 or has been exceeded discard the log records, if the REPL2OPT EC PERMIL statement value has not be exceeded User Response: The DB2 ECCR issues this warning message issued to indicate that there could be a problem capturing log data for the table. However, the DB2 ECCR may still be able to capture data for the table. If the DB2 ECCR encounters errors capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E. To prevent this problem, you can execute SQL to update the columns in the capture directory tables with the correct values from the DB2 catalog tables. Informatica provides sample SQL to perform this update in members FIXTCAPC, FIXTCAPS and FIXTCAPT in the PowerExchange SAMPLIB library. If this message persists after the SQL updates to the capture directory tables have been done, contact Informatica Global Customer Support. PWXEDM177593E Explanation: System Action: User Response: UNEXPECTED VALUE IN SCHEMA_VERSIONS COLUMN OF TCAPTABLES TABLE The DB2 ECCR found an incorrect value in the SCHEMA_VERSIONS column of the TCAPTABLES table. This is an internal error. The DB2 ECCR abends. Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.
897
898
CHAPTER 7

PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent, 899 PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities, 903
PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent

PWXEDM181200E Explanation: System Action: User Response: module: Dynamic LPA operation_name operation for module module_name failed, RC=return_code, Rsn=reason_code A module, using the MVS dynamic LPA service (CSVDYLPA), failed while attempting to add a load module into the Link Pack Area (LPA). The PowerExchange Agent processing ends. See the MVS documentation for the CSVDYLPA service to determine the reason for the error, then take action to correct the error accordingly. module: Cannot locate CDE for module module_name after CSVDYLPA A module, using the MVS dynamic LPA service (CSVDYLPA), successfully added a load module into the Link Pack Area (LPA), but cannot locate the newly created CDE. The PowerExchange Agent subtask processing ends. Contact Informatica Global Customer Support. module: function QName=qname RName=rname status An ENQ or DEQ macro, as specified in function, was issued for the indicated qname and rname. The variable status indicates whether the specified macro obtained or released the required resource or whether the resource failed. The PowerExchange Agent processing continues or ends depending on whether the function performed successfully. If the function was successful, no action is required. If the function failed, a subsequent message further describes the error.
User Response:
899
module %%: Cannot change RepositoryMode on Agent warm startX. RepositoryMode=%% remains in effect. During a warm start of the PowerExchange Agent, it was determined that the specification of RepositoryMode in the PowerExchange Agent configuration parameters was different from what was initially specified. The mode that was in effect previously is indicated in the message. To ensure consistency in the usage of the PowerExchange Agent repository, the RepositoryMode value can only be changed when the PowerExchange Agent is started after being DRAINed and SHUTDOWN (with the COMPLETELY operand), or if the PowerExchange Agent is started STARTUP=COLD. The EDM Agent continues, but the indicated RepositoryMode remains in effect. If it is desired to change the RepositoryMode setting, shut down all other PowerExchange tasks that use this Agent, then issue the PowerExchange Agent DRAIN command, and the PowerExchange Agent SHUTDOWN command with the COMPLETELY operand, then start the PowerExchange Agent with the same parameters as were being used on this restart. The repository mode should then be set as desired. module %%: Current RepositoryMode is %%. This message is issued as a result of an PowerExchange Agent DISPLAY command with the REPMODE operand. Its purpose is to display the PowerExchange Agent RepositoryMode that is currently in effect. Normal processing continues. No response is required. module %%: DYNALLOC deallocation failed. DDname=%%,RC=%%,ErX ror code=%%,Info code=%% A dynamic deallocation request for the indicated DD Name failed. The DYNALLOC return code, error code and info code are shown by rc, error and info, respectively. The dynamic deallocation fails and the function that issued the request may also fail. If the cause of the error cannot be determined, contact Informatica Global Customer Support. module ##: %% This message is issued to augment and further describe one or more following messages. Not affected directly by this message. Depends on the circumstances that caused the message to be issued. module ##: Repository Configuration Parameters (%%): The repository configuration file is about to be processed. Normal processing continues. No response is required. module ##: Error in repository configuration file %% An error was found in a repository configuration file. The error is described in subsequent messages. The repository configuration is not used. Determine the cause of the error, edit the repository configuration file and reopen the repository.
PWXEDM181204 I Explanation:
PWXEDM181206I Explanation: System Action: User Response: PWXEDM181207I Explanation: System Action: User Response: PWXEDM181208E Explanation: System Action: User Response:
900
module ##: Error with repository cache data sets: An error was found in a repository configuration file. The error is described in subsequent messages. The repository configuration is not used. If the cause of the error cannot be determined, contact Informatica Global Customer Support. module ##: Soft error in cache %% (%%) This message is issued when a soft error is detected in a cache. Normal processing continues. Depends on the circumstances that caused the message to be issued. module ##: Cache %% newer than %% This message is issued when caches are not the same. Normal processing continues. Depends on the circumstances that caused the message to be issued. module ##: Using cached capture registrations (%%) This message is issued when cached registrations are used. Normal processing continues. Depends on the circumstances that caused the message to be issued. module ##: Repository access error: An error was encountered accessing the repository. The error is described in subsequent message(s). The currently loaded registrations (if any) continue to be used. The system retries every update interval. If the cause of the error cannot be determined, contact Informatica Global Customer Support. module ##: Repository access (re)established Repository access has been established for the first time or has been reestablished after an error was encountered. Normal processing continues. No response is required. module ##: New capture registrations (%%) New capture registrations have been loaded. Normal processing continues. No response is required. module : Repository status follows: This is the header for the output produced by the PowerExchange Agent REPSTATUS command. This is followed by message 181217, multiple times, and then by message 181218. Normal processing continues.
PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent 901
PWXEDM181210I Explanation: System Action: User Response: PWXEDM181211I Explanation: System Action: User Response: PWXEDM181212I Explanation: System Action: User Response: PWXEDM181213E Explanation: System Action: User Response:
PWXEDM181214I Explanation: System Action: User Response: PWXEDM181215I Explanation: System Action: User Response: PWXEDM181216I Explanation:
System Action:
No response is required. module : repository_status_information This is a detail line for the output produced by the PowerExchange Agent REPSTATUS command. This follows message 181216 and can be issued multiple times. It is then followed by message 181218. Each instance of message 181217 contains some specific information about the status of the PowerExchange Agent Repository subtask. Normal processing continues. No response is required. module : Repository status follows: This is the last line of the output produced by the PowerExchange Agent REPSTATUS command. This follows by message 181216, and multiple instances of message 181217. Normal processing continues. No response is required. module ##: Updated capture registrations (%%) This message is issued when registrations are updated as a part of open processing and the change identifier is the same. Normal processing continues. Depends on the circumstances that caused the message to be issued. module: Repository helper subtask ABENDed,Code=abend_code,Reason=reason_code This message is issued when the main repository task detects that the helper subtask has abnormally terminated. Repository helper subtask is not restarted. Determine the cause of the ABEND, issue REPCLOSE and REPOPEN commands to restore helper subtask or contact Product Support for assistance. module: Memory usage is increasing This message is issued when the main repository task detects that agent memory usage is increasing. This is now an optional message and will only be issued if the statement DTERIOMM DD DUMMY is coded in the PowerExchange Agent. Normal processing continues. A 181217 message detailing current memory usage follows this message. This message may be issued when a number of capture registrations are added. If this message is issued multiple times, it could indicate a problem and Informatica Corporation product support should be contacted. module : Memory usage %% the line is %% percent of the region limit This message is issued when the main repository task detects that agent memory usage has increased to be too close to the limit. It will be issued for the first time when the memory used is 80% of that available to the PowerExchange Agent process (either the system default or the REGION parameter associated with the PowerExchange Agent). It will then be issued at 85%, 90%, 95%, then every time the memory usage increases after that. For example, if it increased by 1% each time messages would be issued at 96%, 97%, 98%, and so on. Normal processing continues.
System Action: User Response: PWXEDM181218I Explanation: System Action: User Response: PWXEDM181219I Explanation: System Action: User Response: PWXEDM181220E Explanation: System Action: User Response:
System Action:
902
User Response:
A PWXEDM181117 message detailing current memory usage follows this message. The maximum region size of the PowerExchange Agent task should be increased. module : repository_module_build_information This message is issued during initialization of the PowerExchange Agent Repository subtask. It contains information to allow the build level of the Repository subtask modules to be identified. Normal processing continues. No response is required.
PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities

PWXEDM181300W Undefined message number message_number Explanation: A module issued a message number that was not defined in any message prototype module. This message substitutes for the intended one and the service aid utility processing continues. Contact Informatica Global Customer Support. module: DETAIL Service Aid. Version version.release.modification The PowerExchange service aid issues this message in the early stages of initialization. It shows the version, release and modification numbers. The PowerExchange service aid utility processing continues. No action is required. module: Processing terminated, RC=return_code The execution of the PowerExchange service aid utility ended with the specified return code. The service aid utility processing ends. Correct the error and run the job again. module: OPEN of ddname file failed A module made an unsuccessful attempt to open the specified file. Processing of the file ends. If the data definition name variable equals REPORT, then the PowerExchange service aid utility processing ends. If the data definition name variable equals REPORT, supply a valid file name and run the job again. Otherwise, contact Informatica Global Customer Support. module: GETMAIN failed for initialization control block The PowerExchange service aid utility could not obtain the storage required for its initialization processing. The PowerExchange service aid utility processing ends. Increase the region size and restart the PowerExchange service aid utility.
903
module: GETMAIN failed for Options area {EDMSDIR|EDMLEVEL|EDMUPARM} The PowerExchange service aid utility could not obtain the storage required for its options load module areas. The PowerExchange service aid utility processing ends. Increase the region size and restart the PowerExchange service aid utility. module: LOAD failed. Module=module_name, Code=abend_code, Reason=reason_code A module issued a load macro, but the MVS Contents Supervision program could not locate the specified module. The PowerExchange service aid utility processing ends. Ensure that all required load libraries are included in the PowerExchange service aid STEPLIB and/or JOBLIB concatenations, and restart the PowerExchange service aid utility. module: Module compare: Old old_EDMLEVEL not in DD new_EDMLEVEL An EDMLEVEL compare request did not supply the old EDMLEVEL in the DD EDMLEVEL statement. The PowerExchange service aid utility processing ends for the compare function. Include an EDMLEVEL DD statement that points to the library that contains the old EDMLEVEL load module. module: Compare: Old=New DSN: data_set_name An EDMLEVEL compare request tried to compare the same data set. The PowerExchange service aid utility processing ends for the compare function. Include an EDMLEVEL DD statement that points to the library that contains the correct old EDMLEVEL load module, and the correct new EDMLEVEL load module. module: EDMLEVEL compare error An EDMLEVEL compare request abended in the EDMUREPC module. The PowerExchange service aid utility processing ends for the compare function. Contact Informatica Global Customer Support. module: Invalid or duplicate input parm; must be: ALL, SDIR, UPRM, LEVL, CLEV, UBLD A module encountered an invalid or duplicate input parameter. The PowerExchange service aid utility processing ends for the function. Remove the duplicate parameter or enter a valid parameter. module: Unexpected EOD for DD ddname A module encountered an end-of-data (EOD) marker in the specified DD name. The only valid EOD marker exists in the EDMCNTL DD; any other EOD implies an internal error. The PowerExchange service aid utility processing ends. Contact Informatica Global Customer Support. module: module_name NOT in DD ddname A module could not find the specified module name in the data definition. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues. Ensure that the $CNTL module exists in the data set.
User Response:
PWXEDM181309E Explanation: User Response: PWXEDM181310E Explanation: User Response: PWXEDM181311E Explanation: System Action: User Response: PWXEDM181312I Explanation:
User Response:
904
PWXEDM181313I Explanation: User Response: PWXEDM181314I Explanation: User Response: PWXEDM181315I Explanation: User Response: PWXEDM181316I Explanation:
module: module_name source module build failed The build failed for the specified source module. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues. Correct the error by using the EXEC statement with the UBLD parameter. module: module_name source build completed successfully The build completed successfully for the specified source module. The PowerExchange service aid utility processing continues. No action is required. module: ASM and Link source module: module_name The build process successfully completed for a source module. The PowerExchange service aid utility processing continues. Assemble and link the specified module. module: Error in module_name. Can't build source source_name The build failed with an input error, for the specified source module. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues. Correct the error in the input module. Execute the PowerExchange service aid utility with the UBLD parameter, then assemble and link the EDMUDESC source module. module: module_name failed for DD ddname The RDJFCB open failed for the specified data definition name. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues. Correct the error and restart the PowerExchange service aid utility. module: DISP=OLD not specified for DD ddname The DISP=OLD parameter must be specified for the data definition name. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues. Correct the error and restart the PowerExchange service aid utility. module: STOW failed during operation_name for DD ddname The STOW command failed during the specified operation for the data definition name. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues. Correct the error and restart the PowerExchange service aid utility. module: No descriptive ZAP and LMOD info available Load module (LMOD) and ZAP descriptions (in load module EDMUDESC) do not exist for the EDMLEVEL or EDMLEVEL compare request. The PowerExchange service aid utility does not display the LMOD and ZAP information, and processing continues. If the $CNTL source module is available, execute the PowerExchange service aid utility with PARM=UBLD and assemble and link the EDMUDESC load module.
User Response:
User Response:
905
PWXEDM181500W Repository access through the agent, not by xxxxxxx DD statement Explanation: User Response: After applying patch P400019, the Event Marker utility now access the repository through the PowerExchange Agent instead of using a DD statement in the JCL. Remove the DD statement for the repository from the EDM Marker utility JCL.
906
CHAPTER 8

PWXEDM261000I to PWXEDM261010I: The Logger API, 907 PWXEDM263000I to PWXEDM263039W: The Log Read API, 908
PWXEDM261000I to PWXEDM261010I: The Logger API

PWXEDM261000I EDP Logger Write API Initialization Options: Connect Name . . . . . . . . . . . . :aaaaaaaa Connect Type . . . . . . . . . . . . : {Type0|Type1} Checkpointing. . . . . . . . . . . . : {Single|Two Phase} Registration Type. . . . . . . . . . : {EDP|Detail Tag} Use Extended Info. . . . . . . . . . : {Yes|No} Event Marks Only . . . . . . . . . . : {Yes|No} User Supplies UOWids . . . . . . . . . . : {Yes|No} Each task issues Termination . . . . . . : {Yes|No} The Log Write API has initialized. The API initialization options are listed. No response is required.
Explanation: User Response:
907
PWXEDM261010I
EDP Logger Write API Initialized {(yyyyyyyy)|Status|Terminating} Application High Sequence . . . . . . . : aaaaaaaaaaaa Application Low Sequence . . . . . . . . : bbbbbbbbbbb {No} UOWs on active list {No} UOWs on resync list UOW ------------------------------------SEQ ------------- Status---xxxxxxxx cccccccc ddddddddeeeeeeeeeeee {in-doubt|in-flight} No UOWs on active list No UOWs on resync list
Explanation:
This message appears at API initialization, normal termination and whenever an API STAT request is made. yyyyyyyy is the Log Write API token. No response is required.
User Response:
PWXEDM263000I to PWXEDM263039W: The Log Read API

This section contains messages for the Log Read API function. PWXEDM263000I Explanation: User Response: PWXEDM263001I Explanation: Log Read API Initialized: Header Version nnn The Log Read API has initialized for header version nnn. No response is required. Log Read API external parameters: This message is the header for the list of parameters supplied at the EDMLPRM DD statement. It is followed by multiple 263002 messages (which are issued without a message number). Normal processing continues. No response is required. echo_of_external_parameter This message echoes the control statement read from the EDMLPRM DD statement during initialization of the Log Read API. Normal processing continues. No response is required.
908
Error in control card: error_description This message is issued when an error has been encountered in one of the control statements read from the EDMLPRM DD statement. It will be issued after the 263002 message that echoed the text of the control statement. Error_description will be one of:

Blank card Keyword ran to end No = after keyword Internal error 1 No keyword value present Unknown Keyword Keyword value too long Keyword value not numeric System Action: Parsing of the remaining control statements continues, and any other errors that are discovered will also be reported. However, once the parsing has processed all the statements, the Log Read API ends abnormally. User Response: PWXEDM263010I Explanation: User Response: PWXEDM263011I Explanation: Correct the errors in the control statement and restart the Log Read API process. Logger xxxxxx (yyyyyyyy): Connecting using agent zzzz For PowerExchange logger xxxxxx using Read API token yyyyyyyy, the PowerExchange Log Read API connects to the logger using PowerExchange Agent zzzz. No response is required. Logger xxxxxx (yyyyyyyy): Opening to read from aaaaaaaaaaaaaaaaaaa to bbbbbbbbbbbbbbbbbb. The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, is opening the log to read from Logger sequence number aaaaaaaaaaaaaaaaaaa to Logger sequence number bbbbbbbbbbbbbbbbbb. An open begins the flow of data from the Logger. Note for bbbbbbbbbbbbbbbbbb: A value of all 0s indicates a request to read until EOF. A value of all Fs indicates a non ending reader. User Response: PWXEDM263012I Explanation: User Response: PWXEDM263013I Explanation: User Response: PWXEDM263014I Explanation: User Response: No response is required. Logger xxxxxx (yyyyyyyy): Disconnecting The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, is disconnecting from the Logger. No response is required. Log Read API Terminating The PowerExchange Log Read API is ending. No response is required. Logger xxxxxx (yyyyyyyy): Closing The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, is closing the Logger connection. A close stops the flow of data from the Logger. No response is required.
909
PWXEDM263015I Explanation: User Response: PWXEDM263020I Explanation:
Logger xxxxxx (yyyyyyyy): Logger selects starting
sequence number
The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, is requesting that the Logger determine the earliest available starting sequence number. No response is required. Logger xxxxxx (yyyyyyyy): Incomplete segmented record discarded The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, determined that a chain of record segments should be complete at this point of the log. Message PWXEDM263021I provides additional details about this condition. No response is required. RBA range aaaaaaaaaaaaaaaaaaa to bbbbbbbbbbbbbbbbbb found by record at RBA ccccccccccccccccccc Additional information for proceeding message PWXEDM263020I. The discarded segment begins at Logger sequence aaaaaaaaaaaaaaaaaaa and ends at bbbbbbbbbbbbbbbbbb. The detecting record is at Logger sequence ccccccccccccccccccc. No response is required. Logger xxxxxx (yyyyyyyy): EDMNAME filter list contains the following nnnn entries: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, lists the nnnn EDMNAMES in the EDMNAME filter list. For change data records, the Log Read API now returns only change records for EDMNAMEs in the list. No response is required. Logger xxxxxx (yyyyyyyy): zzzz The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, has EDMNAME zzzz in the EDMNAME filter list. No response is required. Logger xxxxxx (yyyyyyyy): empty EDMNAME filter list set The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, has an empty EDMNAME filter list. No change records will be returned. No response is required. Logger xxxxxx (yyyyyyyy): EDMNAME filter list cleared The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, has cleared the EDMNAME filter list. All change records will be returned.
Note: This message can appear as a result of an explicit request to clear the list or in the
User Response: PWXEDM263026I Explanation: User Response: PWXEDM263027I Explanation: User Response: PWXEDM263028I Explanation:
course of setting a new list. User Response: No response is required.
PWXEDM263030W Logger xxxxxx (yyyyyyyy): Record segment found at aaaaaaaaaaaaaaaaaaaa SEQ: bb CHN:cc Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, encountered a record segment. This event might be normal but it is unusual so it is being logged. The segment is at Logger sequence aaaaaaaaaaaaaaaaaaaa with segment sequence number bb. Internal chain flags are cc. No response is required.
User Response:
910
Logger xxxxxx (yyyyyyyy): SEDM EDMNAME list duplicate: zzzzz The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, encountered a duplicate EDMNAME, zzzzz, while building the EDMNAME filter list. No response is required.
PWXEDM263032W Logger xxxxxx (yyyyyyyy): aaaa failed: rc=0xbbbbbbb rsn=0xcccccccc Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, call aaaa failed with return code bbbbbbbb and reason code cccccccc. Additional internal return codes may follow in message PWXEDM263033I.
Note: if API appears after Logger then the failure occurred before or during a Logger
connection. User Response: Contact Informatica Global Customer Support.
PWXEDM263033W (internal code 0xaaaaaaa 0xbbbbbbbb) Explanation: An Log Read API function failed. Additional diagnostic information is presented. This information is helpful to support personnel. Often these values are PowerExchange return and reason codes. Contact Informatica Global Customer Support. Logger xxxxxx (yyyyyyyy): Subtask ended; rc=0xaaaaaaaa The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, helper subtask ended with return code aaaaaaaa. See related message PWXEDM263032W. Contact Informatica Global Customer Support. Logger xxxxxx (yyyyyyyy): Received ECMD aaaa reply with rc=0xbbbbbbbb rsn=0xcccccccc The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, received an encoded command reply numbered aaaa from the Logger. The encoded command contains return code bbbbbbbb and reason code cccccccc. For more information about return and reason codes, see Return and Reason Codes on page 913. No response is required. unless message PWXEDM263032W is also issued. In this case, contact Informatica Global Customer Support.
User Response: PWXEDM263035I Explanation: User Response: PWXEDM263036E Explanation:
User Response:
PWXEDM263037W Logger xxxxxx (yyyyyyyy): Unexpected ECMD aaaa reply received with rc=0xaaaaaaaa rsn=0xbbbbbbbb Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, received an unexpected encoded command reply numbered aaaa from the Logger. The encoded command reply contains return code aaaaaaaa and reason code bbbbbbb. See related message PWXEDM263032W. Contact Informatica Global Customer Support.
User Response:
PWXEDM263038W Logger xxxxxx (yyyyyyyy): Unexpected ECMD aaaa request received with rc=0xbbbbbbbb rsn=0xaaaaaaaa Explanation: For The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, received an unexpected encoded command request numbered aaaa is received from the Logger. The encoded command reply contains return code aaaaaaaa and reason code bbbbbbb. See related message PWXEDM263032W. Contact Informatica Global Customer Support.
User Response:
911
PWXEDM263039W Logger xxxxxx (yyyyyyyy): Unsupported Service Record: Explanation:
aaaaa
The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, received an unsupported Service Record from the Logger. The service record text is aaaa. The record is ignored. See related message PWXEDM263032W. Contact Informatica Global Customer Support.
User Response:
912
CHAPTER 9
Return and Reason Codes

This chapter includes the following abend codes, return codes, and reason codes:

Overview, 913 IBM Product Return and Reason Codes, 914 Abend Codes, 914 Return Codes, 915 Reason Codes, 917
Overview
Some PowerExchange messages include one or more codes that provide additional information. For example, a message may include a return code to indicate whether a component or utility ran successfully. In the following example, return code 0 indicates that the relevant component completed execution with no errors: PWXEDM172302I Subtask terminating for program=EDMMLRP1, Return code=X'00000000' (0) Reason=X'00000000' (0). You can receive the following types of codes in PowerExchange messages:

Abend codes Return codes Reason codes
For each code type, this appendix lists the codes in groups, based on the PowerExchange components that generate the codes.
913
IBM Product Return and Reason Codes

Some return and reason codes provided by PowerExchange are created by the MVS operating system or by another IBM product. For explanations of these codes, see the appropriate IBM MVS, IMS, VSAM, or DB2 documentation. Examples of IBM documents that contain explanations of return codes include:

DFSMS: DFSMSdfp Diagnosis z/OS MVS Programming: Authorized Assembler Services Guide z/OS MVS Programming: Authorized Assembler Services Reference IMS Messages and Codes DB2 for z/OS Messages DB2 for z/OS Codes
Abend Codes
Abend codes provide a notice that the system abnormally terminated. Some PowerExchange components issue a single abend code for all abends. Other components issue different abend codes with each abend message also providing a reason code that explains the abend. PowerExchange also issues abend codes that are created by the MVS operating system or another IBM product. For explanations of these abend codes, see the appropriate IBM MVS, IMS, VSAM, or DB2 documentation.
Abend Code U0001: PowerExchange Agent

The PowerExchange Agent issues a user abend code of U0001 to indicate that the PowerExchange Agent encountered an unrecoverable error. The PowerExchange Agent also issues a related reason code when it issues the abend code. In addition, the PowerExchange Agent always issues message PWXEDM172012E before issuing the message containing the abend code and the related reason code.
Table 9-1. PowerExchange Agent Reason Codes Related to ABEND Codes
Reason Code 00000001 00000002 00000003 00000004 00000005 00000006 00000007 00000101 00000102 00000103 00000201 00000202 00000203 00000204 Explanation The PowerExchange Agent detected an invalid initialization work area (EDMSIWRK) or pointer. The PowerExchange Agent detected an invalid agent global control area (EDMSCTRL) or pointer. The PowerExchange Agent detected an invalid ACB or pointer. The PowerExchange Agent detected an invalid RPL or pointer. The PowerExchange Agent detected an invalid SUBSYS I/O work area (EDMSSIOW) or pointer. The PowerExchange Agent detected an invalid subtask work area (EDMSSTSK) or pointer. The PowerExchange Agent detected a corrupted storage area chain. The PowerExchange Agent detected a zero length SUBSYS I/O PUT request. The PowerExchange Agent could not find a SUBSYS I/O buffer. The PowerExchange Agent detected a locate mode SUBSYS I/O PUT request. The PowerExchange Agent did not pass any parameters to the lock manager. The PowerExchange Agent passed a bad function code or operand to the lock manager. The lock manager could not obtain storage. The PowerExchange Agent passed an invalid ASCB and/or TCB address to the lock manager.
914
Chapter 9: Return and Reason Codes
Table 9-1. PowerExchange Agent Reason Codes Related to ABEND Codes

Reason Code 00000205 00000301 Explanation The PowerExchange Agent made a request for a lock that was lower in the lock hierarchy than a lock already being held. The Batch VSAM ECCR requested termination of the job.
The PowerExchange Logger may also issue a related reason code when it issues the abend code. The PowerExchange Logger generates this code based on the number or name of the module issuing the abend and the message number of the message that describes the abend in more detail.
Abend Code U0356: Batch VSAM ECCR

The Batch VSAM environmental change capture routine (ECCR) issues the U356 abend code to indicate that Batch VSAM ECCR abended.
Abend Code U3035: PowerExchange Logger

The PowerExchange Logger issues the U3035 user abend code to indicate the PowerExchange Logger abended.
Abend Code U3680: DB2 ECCR

The DB2 environmental change capture routine (ECCR) issues the U3680 user abend code to indicate the DB2 ECCR abended. The DB2 ECCR normally issues a related reason code. The DB2 ECCR generates this code based on the number or name of the module issuing the abend and the message number of the message that describes the abend in more detail. If your system abends, make a note of this abend related reason code. You will need this code when you call your product support representative for assistance.
Return Codes
After you run a PowerExchange job that provides a return code, the system logs that return code to an output file or prints it to a device. You can receive standard return codes, common return codes, or component specific return codes. Some return codes provided by PowerExchange are created by the MVS operating system or another IBM product. For explanations of these return codes, see the appropriate IBM MVS, IMS, VSAM, or DB2 documentation.
Return Codes
915
Return Codes 0 to 12: Standard

Lists values for the standard return codes. Notice that the values increase as the degree of severity increases.
Table 9-2. Standard Return Codes
Return Code 0 4 Explanation Indicates successful execution of the program, component, or module without warnings or errors. Indicates one of the following - The program, component, or module completed successfully, but the processing included warnings. - The program execution may be incomplete. In either situation, the program writes the warnings to an output or print file that you can use to determine the problem. Normally, you cannot determine whether the program executed successfully without examining this file. 8 Indicates an error occurred during program, component, or module execution. The program writes the error message to an output or print file that you can examine to determine the problem. Indicates the program, component, or module that ended during processing because of a severe error. Often, the error involves a problem with the operating system environment or authorization.
12
Return Codes 1 to 412: Common

Some internal components of PowerExchange use a common set of return codes. Some of these codes are the same as the standard codes but have an expanded explanation or a different explanation. Lists these common return codes and provides an explanation of each code.
Table 9-3. PowerExchange Common Return Codes
Decimal Return Code 1 2 4 Explanation The requested item or function was not found. The system found a duplicate of the requested function or item. This is the standard return code for warnings. When issued by an PowerExchange component, it provides one of the following specific warnings: - The system is sending an end-of-file (EOF) notification to a subtask. - The conversion buffer is too small. This is a warning. - An ECCR passed a record from an incorrect file. - The record came from a file that is not having data captured and propagated. - The system tried to send captured changes to a file that is not supposed to receive captured changes. The system must not call PowerExchange again. A critical error occurred. A security error occurred. A task abnormally ended (abended). The shutdown timer ended.
12 16 17 411 412
916
Return Codes 0 to 12: PowerExchange Agent

Lists the return codes the PowerExchange Agent issues.
Table 9-4. PowerExchange Agent Return Codes
Decimal Return Code 0 4 8 Explanation See Return Codes 0 to 12: Standard on page 916. See Return Codes 0 to 12: Standard on page 916. The PowerExchange Agent encountered a general error. The PowerExchange Agent was able to return a reason code and to display the reason code in the message with this return code. See Table 9-8 on page 918 for these reason codes. The PowerExchange Agent encountered a severe general error. The severity of the error prevented the PowerExchange Agent from returning a reason code.
12
Return Code 221: PowerExchange Logger

Lists the return code the PowerExchange Logger issues.
Table 9-5. PowerExchange Logger Return Code
Hexadecimal Return Code 00DD 221 Explanation A general error occurred.
Return Codes 0 to 8: Batch VSAM ECCR

Lists the return codes the Batch VSAM environmental change capture routine (ECCR) issues.
Table 9-6. Batch VSAM ECCR Return Codes
Decimal Return Code 0 4 8 Explanation The Batch VSAM ECCR change capture module is active. The specified module is initialized but is not active. The specified module has not been initialized.
Reason Codes
Reason codes provide information about system operations or about the cause of problems. This section provides lists and explanations of reason codes that can help you or your vendor product support representative troubleshoot the failing component. The PowerExchange reason codes are listed by PowerExchange component. Some reason codes provided by PowerExchange are created by the MVS operating system or another IBM product. For explanations of these reason codes, see the appropriate IBM MVS, IMS, VSAM, or DB2 documentation. Some components do not create reason codes, but display reason codes created by another component or the operating system. For example, the copybook compiler does not create reason codes. Each reason code it displays is created by a system routine and is documented in the IBM MVS manual cited in the message that returns the reason code.
Reason Codes
917
Reason codes are written to the appropriate message log or displayed as hexadecimal or decimal values. The hexadecimal format is X'xxxxxxxx' and the decimal format is (nnnnnnnn). The reason code is four bytes long. The first two bytes (four hexadecimal characters) identifying the internal module; the last two bytes (four hexadecimal characters) identifying the reason.
Reason Codes xxxx0800 to xxxx081F: Common

Several internal components of PowerExchange use a common set of reason codes. Table 9-7 lists these reason codes with explanations for each code. Because any module can issue these codes, the variable xxxx represents the first two bytes (four hexadecimal characters) of the reason code.
Table 9-7. Common PowerExchange Reason Codes
Reason Code xxxx0800 xxxx0801 xxxx0802 xxxx0803 xxxx0804 xxxx0805 xxxx0806 xxxx0807 xxxx0808 xxxx0809 xxxx080A xxxx080B xxxx080C Explanation A general program error occurred. An invalid function code was found. An invalid token was found. A common token was not found. A GETMAIN error occurred. A DD name was not found. A program LOAD error occurred. A circular queue problem occurred. You are not authorized for this function. An OPEN failed. The component was not able to obtain the supervisory state. An error occurred while processing a FREEMAIN function. A program DELETE error occurred
Reason Codes 001 to 255: PowerExchange Agent

The PowerExchange Agent displays two types of reason codes:

Messages that display the abend code U0001 also display a related reason code to help you determine the cause of the abend. Other messages display the second type of reason code to help you determine the cause of the error related to that message.
Table 9-8. PowerExchange Agent Reason Codes

Decimal Reason Code 001 002 003 004 005 006 007 Hexadecimal Reason Code 001 002 003 004 005 006 007 Explanation A private STORAGE OBTAIN failed. A private STORAGE OBTAIN for less than 16M bytes failed. A common STORAGE OBTAIN failed. A common STORAGE OBTAIN for less than 16M bytes failed. MVS is not at the required SP level. A RACROUTE AUTH call failed. An AUTH call, which is not a RACROUTE AUTH call, failed.
918

Decimal Reason Code 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 Hexadecimal Reason Code 008 009 00A 00B 00C 00D 00E 00F 010 011 012 013 014 015 016 017 Explanation An internal logic error occurred in the module that is calling the PowerExchange Agent. It did not send the correct password key. The required PowerExchange subsystem data space does not exist. The PowerExchange subsystem could not be found. A subsystem was found, but it is not an PowerExchange subsystem. An attempt to load the EDMSDIR module failed. The EDMXCIRQ circular queue returned an error. The global queue does not exist. The calling module did not pass an PowerExchange queue handle. The calling module passed a queue handle, but the handle has an incorrect version number or format. The calling module did not pass an PowerExchange handle. The calling module passed an PowerExchange handle, but the PowerExchange handle has an incorrect version number or format. The PowerExchange subsystem initialization (EDMSINIT) has not been performed. An PowerExchange subsystem initialization (EDMSINIT) was attempted; however, it is already initialized. An EDMSCTRL pointer is missing or invalid. The address space creation macro (ASCRE) failed. The address space creation macro (ASCRE) failed because another component sent the PowerExchange Agent an invalid address space name. The address space creation macro (ASCRE) failed because the requested resource is not available. The requesting component needs to request the resource later. If the requesting component times out before the resource is available, you may need to run the job again. The PowerExchange Agent attempted to create the global queue; however, it already exists. The PowerExchange Agent is processing a DRAIN command. The PowerExchange Agent completed processing for a DRAIN command. The EDMSASIN module terminated the address space creation macro (ASCRE). The PowerExchange Agent received a SHUTDOWN COMPLETELY command and was completely shut down. A dynamic allocation (DYNALLOC) for the subsystem DD failed. The global queue received a request from a program with an invalid ASID. There was a mismatch with the global queue sequence number. The PowerExchange Agent attempted to access the PowerExchange repository and found the PowerExchange repository was not open or found the PowerExchange repository command was invalid. The PowerExchange Agent received an invalid repository command. An error occurred with an RIOM call.
024
018
025 026 027 028 029 030 031 032 035
019 01A 01B 01C 01D 01E 01F 020 023
036 037
024 025
Reason Codes
919

Decimal Reason Code 040 045 046 047 048 060 061 062 063 070 071 072 230 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 Hexadecimal Reason Code 028 02D 02E 02F 030 03C 03D 03E 03F 046 047 048 0E6 0EF 0F0 0F1 0F2 0F3 0F4 0F5 0F6 0F7 0F8 0F9 0FA 0FB 0FC 0FD 0FE 0FF Explanation The PowerExchange Agent found that data was truncated. The module currently holds or has obtained the lock. The module does not currently hold the lock. The requested lock was unavailable. The lock is not held and cannot be obtained because of hierarchy rules. The SIOW area could not obtain storage. The resource manager could not obtain storage. The task work area could not obtain storage. The global queue handler could not obtain storage. A bad STOKEN occurred during an EDMSRMGR call. A bad TCB occurred during an EDMSRMGR call. The EDMSRMGR TCB is not in the home ASID. The PowerExchange Agent does not allow SRB mode callers. A request timed out. An illogical function request occurred. A required subsystem or subtask is not active. An OPEN command failed. A CLOSE command failed. The PowerExchange Agent encountered and invalid data set name. A module LOAD failed. The IBM timing macro (STIMERM) failed. The PowerExchange Agent encountered a command with the incorrect number of operands. Another component requested a function that is not available. The PowerExchange Agent could not add data to a buffer or file, because the buffer or file was full. Another component sent a request to the PowerExchange Agent to find something, but the PowerExchange Agent could not find it. The PowerExchange Agent found a duplicate request or duplicate record. One module passed an incorrect operand to another module. An invalid function was requested or the function request had an incorrect number of errors. An unexpected error occurred. An abnormal termination (abend) occurred.
920
Reason Codes 00000601 to 00004499: Command

PowerExchange issues reason codes from encoded commands that pass between program modules. Some of these reason codes are displayed in the messages you see when an error occurs.
Table 9-9. Command Reason Codes
Reason Code 00000601 00000602 00000603 00000604 00000605 00000702 Explanation An unknown error occurred. There is no schema registration. There is no relational schema registration. There is no object or schema that matches the specified EDMNAME. The object or schema is not active for the time requested. If message PWXEDM172702I is issued, then the Log Read task (EDMLCQO0) has been terminated because the PowerExchange Logger stole the active log it was using because no other active logs are available. Otherwise, the Log Read task (EDMLCQO0) in the PowerExchange Logger has abended. No logged-on reader control block found for Terminate Process. Terminate Process request failed. Client Control Block not found (client not already or no longer signed on to Logger). Invalid XCF message (unrecognized encoded command). Data Is No Longer Available (no RBA range can be found). data is not present in inventory (requested timestamp does not yet exist). Data Not Accessed Due To Error (for example, attempt to attach subtask failed). Log reader disconnected from Logger before initialization was completed. Tran Id Logger Name Not This Logger. No logged-on reader control block found for Request Data Transfer. Stop location is before start location. No such start location found. No logged-on reader control block found for Stop Data Transfer. Registration request failed for unknown reason. There are no database, data set, or subsystem registrations. There are no registrations of the specified type. There is no object or schema that matches the specified EDMNAME. The object or schema is not active for the time requested. The module cannot find the primary object profile for the object. Possible reasons include that the object is not defined to PowerExchange. For VSAM and IMS, this reason code can be generated if you create redefined records for a VSAM data set or an IMS segment, and then delete the primary record definition. Registration request for invalid object type. The PowerExchange Logger is shutting down. The PowerExchange Logger requires additional system resources. The queue could not be opened. Invalid signon request (requesting neither read mode nor write mode). Already signed on (duplicate jobname).
00000703 00000704 00000805 00000813 00001506 00001507 00001508 0000150A 00001510 00001511 00001514 00001515 00001601 00001701 00001702 00001703 00001704 00001705 00001706
00001708 00001901 00001902 00001903 00001904 00001905
Reason Codes
921
Table 9-9. Command Reason Codes

Reason Code 00001906 00001907 00001908 00001909 0000190A 0000190B 0000190C 0000190D 00002104 00002105 00002111 00002501 00002502 00002503 00002504 00002505 00002506 00002507 00002601 00002806 00004701 00004702 00004801 00004802 Explanation An XCF connection failed. The PowerExchange Logger is not ready. Logger on different CPU (Log Reader attempted to connect to Logger that was running on a different operating system instance). Failed to add log reader control block (OUQQ). Unable to start log reader subtask. Could not log ECCR signon record. Failed to add ECCR control block (INQQ). Resume operation failed. Invalid Resource Interest List command Chain error processing IntLst command No matching signed on reader An unknown error occurred. An unsupported data type was found. A module found unsupported data definition language (DDL) code. An object registration was not found. A schema registration was not found. There is no schema for the specified time. A change request failed. Could not log user data record Column name with excessive length encountered. Member Logger was already in quiesced status. Member Logger was already in stopped status. Member Logger was not in quiesced status. Member Logger was already in stopped status.
Reason Codes 00000813 to 00001515: Encoded Commands

Table 9-10 lists the Encoded Commands reason codes:
Table 9-10. Encoded Commands Reason Codes
Reason Code 00000813 00000805 00001506 00001507 00001508 00001510 00001514 00001515 Explanation Invalid XCF message (unrecognized encoded command). Client Control Block not found (client not already or no longer signed on to Logger). DATA IS NO LONGER AVAILABLE (no RBA range can be found). DATA IS NOT PRESENT IN INVENTORY (requested RBA does not yet exist). DATA NOT ACCESSED DUE TO ERROR (for example, required dataset cannot be allocated). TRAN ID LOGGER NAME NOT THIS LOGGER. Stop location is before start location. No such start location found.
922
Reason Codes 00000C00 to 00000C0E: Common Services

PowerExchange common services provide functions to many of the PowerExchange components. The reason codes shown below describe errors encountered during common services processing.
Table 9-11. Common Services Reason Codes
Reason Code 00000C00 00000C01 00000C02 00000C03 00000C0A 00000C0B 00000C0C 00000C0D 00000C0E Explanation The module could not obtain storage. The lock manager could not create an anchor. There are no available lock manager entries. The lock manager received an invalid entry. The module received an invalid trace ID. An MVS ATTACH function failed. The MVS service parameter list number was invalid. The MVS STIMERM SET function failed. The MVS STIMERM CANCEL function failed.
Reason Codes 0033FF01 to 00FFFFFF: PowerExchange Logger

Table 9-12 lists the reason codes for the PowerExchange Logger.
Table 9-12. PowerExchange Logger Reason Codes
Reason Code 0033FF01 0033FF02 0033FF03 0033FF04 0033FF05 0033FF06 0033FF07 0033FF08 0033FF09 0033FF0A 0033FF0B 0033FF0C 0033FF0D 0033FF20 0033FF21 0033FF22 0033FF23 0033FF24 0033FF25 Explanation The chainer module could not obtain a work area. An initialization error occurred. There was an invalid function code. An unknown return code was found during an attempt to move a record. The reader processor (EDMLLRD0) was unable to get a buffer. The reader processor (EDMLLRD0) detected an invalid record prefix. A refreshed buffer was not available for the reader processor (EDMLLRD0). The reader processor (EDMLLRD0) failed to get a refreshed buffer. The reader processor (EDMLLRD0) detected an invalid record prefix. There were entries in the read queue when the reader processor (EDMLLRD0) was expecting an empty queue. There were no entries found in the available queue. The reader processor (EDMLLRD0) failed to disconnect from PowerExchange common services. The reader processor (EDMLLRD0) failed to connect to PowerExchange common services. Available Queue empty when available buffer needed. Physical reader initialization failed. Error in GETBUFF. I/O error in physical read. I/O error in physical reread. Physical reader termination failed. During an unallocate call, physical reader termination failed.
Reason Codes
923

Reason Code 00D5FF01 00D5FF02 00D5FF03 00D5FF04 00D5FF05 00D5FF06 00D5FF07 00D5FF08 00D5FF09 00D5FF0A 00D5FF0B 00D5FF0C 00D5FF0D 00D5FF0E 00D6FF01 00D6FF02 00D6FF03 00D6FF04 00D6FF07 00D6FF08 00D6FF09 00D6FF0A 00D6FF0B 00D6FF0C 00D6FF0D 00D6FF0E 00D6FF0F 00D6FF10 00D6FF11 00D6FF12 00D6FF13 00D6FF14 00D7FF01 00D7FF02 00D7FF03 00D7FF04 Explanation Logger invoked in non-APF authorized state. Invalid function code supplied to EDMLPRD0. Dynamic allocation error for archive log dataset in EDMLPRD0. Open failed for archive log dataset in EDMLPRD0. RBA value has reached maximum permitted value (X'FFFFFFFFFFFF') in EDMLPRD0. Unexpected RBA encountered in archive log in EDMLPRD0 (missing or duplicated block(s)). Close failed for archive log dataset in EDMLPRD0. Invalid LOGQ parameter supplied to EDMLPRD0 at initialization. EDMLPRD0 could not locate secondary archive log dataset. No buffers available at initialization in EDMLPRD0. No buffers available at start of read in EDMLPRD0. Dynamic un-allocation error for archive log dataset in EDMLPRD0. Invalid LOGQ parameter supplied to EDMLPRD0 at start of read. Unexpected RBA encountered in archive log dataset at EOF in EDMLPRD0 (missing block(s)). The chainer module could not obtain a work area. Invalid function code supplied to EDMLPRD1. Dynamic allocation error for active log dataset in EDMLPRD1. Open failed for active log dataset in EDMLPRD1. Close failed for active log dataset in EDMLPRD1. Invalid LOGQ parameter supplied to EDMLPRD0 at initialization. EDMLPRD1 could not locate secondary active log dataset. No buffers available at initialization in EDMLPRD0. No buffers available at start of read in EDMLPRD0. The chainer module was unable to find an entry in the GBLBLKQ11 queue. The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue. The chainer module was unable to find an entry in the GBLBLKQ22 queue. Invalid LOGQ parameter supplied to EDMLPRD1 at start of read. Invalid LOGQ parameter supplied to EDMLPRD1 at start of reread. Error adding entry to GBLPH1QCB queue in EDMLPRD1. Primary active log stopped and dual active logs not available. Maximum retries (100) exceeded to successfully reread block from active log dataset in EDMLPRD1. The chainer module could not obtain a work area. The chainer module could not release a work area. The MODCB macro failed to modify the RPL control block. The print ERDS command processor (EDMLPR50) failed to GET the master log control record.
924

Reason Code 00D7FF05 00D7FF06 00D7FF07 00D7FF08 00D7FF09 00D7FF0A 00D8FF01 00D8FF02 00D9FF01 00D9FF02 00DAFF01 00DAFF02 00DAFF04 00DBFF01 00DBFF02 00DBFF03 00DCFF01 00DCFF02 00DDFF01 00DDFF02 00DDFF03 00DDFF04 00DDFF05 00DDFF06 00DDFF07 00DDFF08 00DDFF09 00DDFF0A 00DDFF0B 00DDFF0C 00DDFF0D 00DDFF0E 00DDFF0F 00DDFF10 00DDFF11 Explanation The print ERDS command processor (EDMLPR50) failed to GET the primary active log control record. The print ERDS command processor (EDMLPR50) failed to GET the secondary active log control record. The print ERDS command processor (EDMLPR50) failed to GET the primary archive log control record. The print ERDS command processor (EDMLPR50) failed to GET the secondary archive log control record. The print ERDS command processor (EDMLPR50) failed to GET the checkpoint control record. The print ERDS command processor (EDMLPR50) entered an ESTAE routine. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. SYNAD entered a spooled sysout file in EDMLPR20. The chainer module could not obtain a work area. The chainer module could not release a work area. Error connecting to Common Services. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. Cannot determine which ECB posted. The chainer module could not LOCK the queue control block (QCB). The chainer module could not UNLOCK the queue control block (QCB). Log reader disconnected from Logger before initialization was completed. The PowerExchange Logger found an invalid log RBA. An attempt to initialize a log reader failed. An attempt to open a circular queue failed. A log reader READ command failed. An attempt to PUT to a circular queue failed. A circular queue end-of-file error occurred. An attempt to close a circular queue failed. An attempt to terminate a log reader failed. An attempt by the logger to connect to the common services failed. An attempt to send a SENDPIPE command to the log read processor (LRP) failed. Circular queue PUT error for Request Data Transfer reply.
Reason Codes
925

Reason Code 00DDFF12 00DDFF13 00DEFF01 00DEFF02 00DEFF03 00DEFF04 00DEFF05 00DEFF06 00DEFF07 00DEFF08 00DEFF09 00DEFF0A 00DEFF0B 00DEFF13 00DFFF01 00DFFF02 00DFFF03 00DFFF04 00DFFF05 00E0FF01 00E0FF02 00E1FF01 00E2FF01 00E2FF02 00E2FF03 00E2FF04 00E2FF05 00E3FF01 00E4FF01 00E4FF02 00E5FF01 00E5FF02 00E5FF03 00E5FF04 Explanation No token found for XCF circular queue. Attempt to open XCF circular queue failed. The chainer module could not obtain a work area. The chainer module could not release a work area. An attempt to initialize a logical log reader failed. An attempt by the logical log reader to perform a READ failed. The PowerExchange Logger was unable to add a unit-of-work (UOW) entry to an internal UOW queue. An attempt to terminate the logical log reader failed. The PowerExchange Logger was unable to find a logrba in the selected logs. The PowerExchange Logger could not find a UOW for begin_PHASE1. The PowerExchange Logger could not find a UOW for begin_PHASE2. The PowerExchange Logger could not find a UOW for end_PHASE1. The PowerExchange Logger could not find a UOW for end_PHASE2. Cannot locate record prefix while repositioning in log on restart (EDMLPLG1). The chainer module could not obtain a work area for the write to operator with reply (WTOR) parameter list. The chainer module could not release a work area for the write to operator with reply (WTOR) parameter list. The chainer module could not release a work area for the write to operator with reply (WTOR) message text. The chainer module could not release a work area for the write to operator with reply (WTOR) output data area. The chainer module could not release the OPQ control block. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not release a work area. An incorrect post code was detected by the receiving module. An attempt to find an element address failed. The PowerExchange Logger cannot free a latch that is not held. A module is using a latch and it issued a request to use it again. A module cannot acquire a latch that it is currently using. The PowerExchange Logger latching processor could not find any latch queue control block (QCB) entries. A normal dump has been requested. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. Error performing buffer Force_write operation. Error performing Trunc_Log operation. The chainer module could not release a work area.
926

Reason Code 00E5FF05 00E5FF06 00E5FF07 00E6FF01 00E6FF02 00E7FF01 00E7FF02 00E7FF03 00E7FF04 00E8FF03 00E8FF04 00E9FF01 00E9FF02 00E9FF03 00E9FF04 00E9FF05 00E9FF06 00E9FF07 00E9FF08 00E9FF09 00E9FF0A 00E9FF0B 00E9FF0C 00E9FF0D 00E9FF0E 00E9FF0F 00E9FF10 00E9FF11 00E9FF12 00E9FF13 00E9FF14 00E9FF15 00E9FF16 00E9FF17 00E9FF18 00E9FF19 00E9FF20 Explanation Archive Log operation already in progress. Error performing Trunc_Buff operation. Error connecting to Common Services. An attempt by the chainer module to add a record to a queue failed. The chainer module is unable to obtain an area for a DATA COPY. The chainer module could not obtain a work area. The chainer module could not release a work area. An attempt to delete an old logger EDMUPARM module failed. An attempt to open the EDMPARMS data set failed. The pattern match processor found arguments with a length less than zero (0). The pattern match processor found a pattern larger than 256 bytes. Latch obtain error in EDMLOF20. The active log archive processor could not find an active log present in the LOGQ log queue. Dynamic allocation for the archive COPY1 data set failed. An attempt to perform an OPEN on the archive COPY1 data set failed. Dynamic allocation for the archive COPY2 data set failed. An attempt to perform an OPEN on the archive COPY2 data set failed. The PowerExchange Logger latching processor could not obtain the LOGQ COPY1 log queue. The PowerExchange Logger latching processor could not obtain the LOGQ COPY2 log queue. EDMLOF20 could not find COMMSRV connect token. The DIV ACCESS macro was unable to access the active logs. Primary (and secondary if applicable) active log dataset(s) stopped The DIV UNIDENTIFY macro was unable to unidentify the active log. A CLOSE command failed on an archive COPY1 data set. The RDJFCB macro failed on an archive COPY1 data set. A CLOSE command failed on an archive COPY2 data set. EDMLOF20 could not find secondary active log in LOGQ. An UNALLOCATE command failed on an archive COPY1 data set. An UNALLOCATE command failed on an archive COPY2 data set. An UNALLOCATE command failed on active log. An internal DEFINE_LOG COPY1 command failed. An internal DEFINE_LOG COPY2 command failed. The chainer module could not release a work area. The chainer module could not add a local area. The chainer module could not initialize the OPQ control block. The chainer module could not find an entry in the GBLBLKQ11 queue. The chainer module could not find an entry in the GBLBLKQ12 queue.
Reason Codes
927

Reason Code 00E9FF21 00E9FF22 00E9FF23 00E9FF24 00E9FF25 00E9FF26 00E9FF27 00E9FF30 00E9FF34 00EAFF01 00EAFF02 00EBFF01 00EBFF02 00EC0040 00ECFF01 00ECFF02 00ECFF03 00EDFF01 00EDFF02 00EEFF01 00EEFF02 00EFFF01 00EFFF02 00F0FF01 00F0FF02 00F1FF01 00F1FF02 00F1FF03 00F1FF04 00F1FF05 00F1FF06 00F1FF07 00F1FF08 00F1FF09 00F1FF0A 00F1FF0B 00F1FF0C 00F1FF0D Explanation The chainer module could not find an entry in the GBLBLKQ21 queue. The chainer module could not find an entry in the GBLBLKQ22 queue. The chainer module was unable to find an entry for LOG2 in the LOGQ queue. The active log archive processor is using the last active log. The log archive processor was unable to find a LOG2 data set name. SYNAD entered for archive log 1. SYNAD entered for archive log 2. Latch release error in EDMLOF20. Update ERDS process failed. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. The module receives an unexpected return code from the DBCTL subsystem interface. Contact your Informatica Corporation technical support analyst for assistance. The chainer module could not obtain a work area. The GETMAIN macro failed. The FREEMAIN macro failed. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not initialize the GCO queue. The chainer module could not add an entry to the GCO queue. The chainer module could not add or replace an entry on the GCO queue. The chainer module could not initialize the IMO queue. The chainer module could not add an entry to the IMO queue. The chainer module could not add or replace an entry on the IMO queue. The chainer module could not delete the GCO queue. The chainer module could not delete the IMO queue. The chainer module could not find the GCO queue. The EDMUPARM processor (EDMLDF20) could not load the modified options data set. The chainer module could not terminate the ICO queue.
928

Reason Code 00F1FF0E 00F1FF0F 00F1FF10 00F1FF11 00F2FF01 00F2FF04 00F2FF05 00F3FF01 00F3FF02 00F3FF03 00F3FF04 00F3FF05 00F3FF06 00F3FF07 00F3FF08 00F3FF09 00F3FF0A 00F3FF0B 00F3FF0C 00F3FF0D 00F3FF0E 00F3FF0F 00F3FF10 00F3FF11 00F3FF12 00F3FF13 00F3FF14 00F3FF15 00F3FF16 00F3FF17 00F3FF18 00F3FF19 00F3FF1A 00F3FF1B 00F3FF1C Explanation The chainer module could not terminate the GCO queue. The EDMUPARM processor (EDMLDF20) encountered an error when it attempted to delete one or more options. The EDMUPARM processor (EDMLDF20) was unable to find the DEFAULT SERVER OPTIONS module. The EDMUPARM processor (EDMLDF20) could not open the options data set. The chainer module could not obtain a work area. The chainer module could not return a work area. The define-logger processor (EDMLDF10) could not find the options data set. The PowerExchange Logger found an incorrect version of the EDMLC020 control module. The PowerExchange Logger found an incorrect version of the EDMLC030 control module. The chainer module could not initialize the CSA tracking queue. The chainer module was unable to initialize an area for the GLOBAL control block. The chainer module was unable to create an area for the GLOBAL control block. The chainer module was unable to initialize a task control, TC, queue. The chainer module was unable to initialize a LOC=31 storage unit. The chainer module was unable to initialize a LOC=24 storage unit. The chainer module was unable to initialize the INPUT queue. The initialization processor could not find the address of the chainer module while building a write to operator with reply (WTOR) command. The chainer module could not add a local control block for a write to operator with reply (WTOR) command. The initialization processor could not find the address of the chainer module while building the PowerExchange physical logger. The chainer module could not add a local control block for the PowerExchange physical logger. The BLDL FIND macro was unable to locate the EDMLC030 module. An OPEN command failed for STEPLIB. Subsystem initialization failed. An attempt to LOAD the options module EDMUPARM failed. The message display routine FREEMAIN command failed. An EDMPARMS DD statement is missing. An EDMZPARM module was not found. The options module DD concatenation has an error. An attempt to LOAD the options module EDMUPARM failed. An error occurred while initializing the queue for 241 XCA GETMAINS. Too many EDMLC030 modules exist in extended CSA (ECSA). An attempt by the chainer module to create a latch queue control block (QCB) failed. The chainer was unable to create a latch area. The chainer module had an error while creating LOGQ COPY1 block queue. The chainer module had an error while creating BLKQ COPY1 block queue.
Reason Codes
929

Reason Code 00F3FF1D 00F3FF1E 00F3FF1F 00F3FF20 00F3FF21 00F3FF22 00F3FF23 00F3FF24 00F3FF25 00F3FF26 00F3FF27 00F3FF28 00F3FF29 00F3FF2A 00F3FF2B 00F3FF2C 00F3FF2D 00F3FF2E 00F3FF2F 00F3FF30 00F3FF31 00F3FF32 00F4FF01 00F4FF02 00F4FF03 00F4FF04 00F4FF05 00F4FF06 00F4FF07 00F4FF08 Explanation The chainer module had an error while creating LOGQ COPY2 block queue. The chainer module had an error while creating the BLKQ COPY2 block queue. The chainer module had an error while creating LOGQ COPY1 block queue. The chainer module had an error while creating BLKQ COPY1 block queue. The chainer module had an error while creating LOGQ COPY2. The chainer module had an error while creating BLKQ COPY2. The chainer module had an error while adding a LOGF entry to the LATCH queue. The chainer module had an error while adding a CHKP entry to the LATCH queue. The chainer module had an error while initializing the unit-of-work (UOW) QCB queue control block. The chainer module was unable to initialize the CHK checkpoint queue control block (QCB). The chainer module was unable to initialize the ECCR INQ input queue control block (QCB). The chainer module was unable to initialize the LRP OUQ output queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to create a latch circular queue. The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a phase 1 queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a phase 2 queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a termination queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a packet queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a global queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a command queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize an XCF queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a trace queue control block (QCB). The PowerExchange Logger initialization processor (EDMLC015) encountered an incompatible EDMUPARM level. An attempt to load the initialization processor failed. The chainer module was unable to create the TC task control module. The ATTACH command passed a nonzero return code. The chainer module could not delete the LOC=31 storage unit. The chainer module was unable to obtain a work area for the ECB list. The chainer module could not delete the task control. The PowerExchange Logger initial checkpoint failed. The PowerExchange Logger final checkpoint failed.
930

Reason Code 00F4FF09 00F4FF0A 00F4FF0B 00F4FF0C 00F4FF0C 00F5FF01 00F5FF02 00F5FF03 00F5FF05 00F5FF06 00F6FF01 00F6FF02 00F6FF03 00F6FF04 00F6FF05 00F6FF08 00F6FF09 00F6FF0D 00F6FF0E 00F6FF0F 00F7FF01 00F7FF02 00F7FF03 00F7FF04 00F7FF05 00F7FF06 00F7FF07 00F7FF08 00F7FF09 00F7FF17 00F7FF18 00F7FF19 00F7FF1A 00F7FF1B 00F7FF1C 00F7FF1D 00F7FF1E Explanation An attempt to initialize the common services environment failed. An attempt to connect to common services failed. The main subtask processor (EDMLC010) could not create the circular queue. A POST error occurred. The main subtask processor (EDMLC010) could not connect to the PowerExchange subsystem. The main subtask processor (EDMLC010) could not post a write packet trailer. The chainer module could not obtain a work area. The EDMLPAR0 reason code is too large. A previous chainer error occurred. A required work area does not exist. The chainer module could not terminate the command queue. The PARSER Error processor received an invalid return code from the PARSER analyzer. The chainer module could not obtain a work area. The chainer module could not release a work area. The chainer module could not obtain an area for a VSAM DELETE statement. The chainer module could not obtain an area for a VSAM DEFINE statement. The chainer module could not obtain an area for a VSAM JOURNAL HEADER statement. An attempt to delete a statement area failed. The data set name is missing from an input parameter. R0 contains an invalid entry code. It contains an entry other than DELETE, DEFINE, or JOURNAL HEADER. Either the ALCACB. or ALCRPL. area is corrupt. The ALCALCAD area is corrupt. The chainer module could not obtain a work area. An attempt to initialize the common services environment failed. An attempt to connect to common services failed. An attempt to initialize the XCF interface failed. An attempt to open the XCF interface failed. An attempt to create the XCF interface failed. $XCF GET failed for message. $XCF GET failed for group event (Logger group). $XCF GET failed for group event (Post-Log Merge group). Failed adding log reader control block (OUQQ). Unable to start log reader subtask. ECCR is already connected to Logger. Unable to add PKT queue entry. Failed to add ECCR control block (INQQ). Invalid signon type (neither read nor write). Attempt to perform resume operation failed. Unable to locate log reader (OUQQ) control block.
Reason Codes
931

Reason Code 00F7FF1F 00F7FF20 00F7FF21 00F7FF22 00F7FF23 00F8FF01 00F8FF02 00F8FF03 00F8FF04 00F8FF05 00F8FF06 00F8FF07 00F8FF08 00F8FF09 00F8FF0A 00F8FF0B 00F8FF0C 00F8FF0D 00F8FF0E 00F8FF0F 00F8FF10 00F8FF11 00F8FF12 00F8FF13 00F8FF14 00F9F701 00F9F702 00F9F801 00F9F802 00F9F803 00F9F804 00F9F805 00F9F806 00F9F807 00F9F808 Explanation Could not write to global circular queue. Logger name in restart request does not match logger ID. End location in transfer request before start location. Terminate request did not complete successfully. Delete of log reader (OUQQ) control block fail. The chainer module could not obtain a work area. The chainer module is unable to delete the old ECB list. The chainer module is unable to obtain a new ECB list. The checkpoint processor received an unexpected termination of the QSAM I/O subtask. The checkpoint processor received an unexpected termination of the TIMER subtask. The checkpoint processor received an unexpected termination of the JOURNAL subtask. The checkpoint processor received an unexpected termination of the PROCESS subtask. The checkpoint processor received an unexpected termination of the RESTART subtask. The checkpoint processor received an unexpected termination of the LOGICAL subtask. The checkpoint processor received an unexpected termination of the PHYSICAL subtask. The checkpoint processor received an unexpected termination of the Checkpoint subtask. The checkpoint processor received an unexpected termination of the XCF subtask. The checkpoint processor received an unexpected termination of the VTAM I/O subtask. The checkpoint processor received an unexpected request for a checkpoint. The checkpoint processor received an unexpected request for a shutdown. The checkpoint processor received an unexpected operator reply. The checkpoint processor received an unexpected reload of EDMZPARM. The checkpoint processor received an unexpected termination of an MVS command. The chainer module was unable to delete a work area. The PowerExchange Logger found an invalid code. A WRITE to a restart data set (ERDS) failed. The routine that determines the number of blocks available in the active LOG2 was unable to obtain a LOGQ latch. The routine that determines the number of blocks available in active LOG2 was unable to release the LOGQ latch. The routine that determines the number of blocks available in active LOG2 was unable to obtain the LOGQ latch. The routine that determines the number of blocks available in active LOG2 was unable to release the LOGQ latch. The chainer module could not obtain a read buffer. The chainer module was unable to add an entry to the BLKQ COPY1 queue. The chainer module was unable to add an entry to the active LOGQ COPY1 queue. The chainer module was unable to add an entry to the archive BLKQ COPY1 queue. The chainer module was unable to add an entry to the archive LOGQ COPY1 queue. The chainer module was unable to find an entry in the GBLBLKQ11 queue.
932

Reason Code 00F9F809 00F9F80A 00F9F80B 00F9F901 00F9F902 00F9F903 00F9F904 00F9F905 00F9F906 00F9F907 00F9F908 00F9F909 00F9F90A 00F9F90B 00F9FA01 00F9FA02 00F9FA03 00F9FA04 00F9FA05 00F9FA06 00F9FA07 00F9FB01 00F9FB02 00F9FB03 00F9FB04 00F9FB05 00F9FB06 00F9FB07 00F9FB08 00F9FB09 00F9FB0A 00F9FB0B 00F9FB0C 00F9FB0D 00F9FB0E 00F9FB0F Explanation The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue. The chainer module was unable to find an entry in the GBLBLKQ22 queue. The routine that determines the number of blocks available in active LOG1 was unable to obtain the LOGQ latch. The routine that determines the number of blocks available in active LOG1 was unable to release the LOGQ latch. The chainer module could not obtain a read buffer. The chainer module was unable to add an entry to the BLKQ COPY1 queue. The chainer module was unable to add an entry to the active LOGQ COPY1 queue. The chainer module was unable to add an entry to the archive BLKQ COPY1 queue. The chainer module was unable to add an entry to the archive LOGQ COPY1 queue. The chainer module was unable to find an entry in the GBLBLKQ11 queue. The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue. The chainer module was unable to find an entry in the GBLBLKQ22 queue. The chainer module was unable to find an entry in the GBLBLKQ11 queue. The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue. The chainer module was unable to find an entry in the GBLBLKQ22 queue. A save error occurred in the physical logger processor (EDMLPLG0). The other log was already stopped. A save error occurred in the physical logger processor (EDMLPLG0). There is no secondary log. The secondary active log subtask (EDMLPLG2) has abended. The routine to terminate processing of active log could not obtain the LOGQ latch. The routine to terminate processing of active log could not release the LOGQ latch. The DIV UNACCESS macro could not stop accessing the LOG1 data set. The DIV UNIDENTIFY macro could not unidentify the LOG1 data set. The ALESERV DELETE macro could not delete the LOG1 data set. The DSPSERV DELETE macro could not delete the LOG1 data set. The DIV SAVE macro could not save the LOG2 data set. The DIV UNMAP macro could not unmap the LOG2 data set. The DIV UNACCESS macro could not stop accessing the LOG2 data set. The DIV UNIDENTIFY macro could not unidentify the LOG2 data set. The ALESERV DELETE macro could not delete the LOG2 data set. The DSPSERV DELETE macro could not delete the LOG2 data set. The chainer module was unable to find an entry in the GBLBLKQ11 queue. The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue.
Reason Codes
933

Reason Code 00F9FB10 00F9FC01 00F9FC02 00F9FC03 00F9FC04 00F9FC05 00F9FC06 00F9FC07 00F9FC08 00F9FC09 00F9FC0A 00F9FC0B 00F9FC0C 00F9FC0D 00F9FC0E 00F9FC0F 00F9FC10 00F9FC11 00F9FC12 00F9FC13 00F9FC14 00F9FC15 00F9FD01 00F9FD02 00F9FE01 00F9FF01 00F9FF02 00F9FF03 00F9FF04 00F9FF05 00F9FF06 00F9FF07 00F9FF08 00F9FF09 00F9FF0A Explanation The chainer module was unable to find an entry in the GBLBLKQ22 queue. The routine to initialize processing of active log could not obtain the LOGQ latch. The routine to initialize processing of the active log could not release the LOGQ latch. Dynamic allocation for the active LOG1 data set failed. The routine to initialize processing of the active log could not release the LOGQ latch. Dynamic allocation for the active LOG2 data set failed. The routine to initialize processing of the active log could not release the LOGQ latch. The DSPSERV CREATE macro could not create a hyperspace for HSP LOG1 data set. The ALESERV OBTAIN macro could not obtain the access least entry token (ALET) LOG1 data set. The DSPSERV CREATE macro could not create a hyperspace for HSP LOG2 data set. The ALESERV OBTAIN macro could not obtain the access least entry token (ALET) LOG2 data set. The DIV IDENTIFY macro could not identify the LOG1 data set. The DIV ACCESS macro could not access the LOG1 data set. The DIV MAP macro could not map the LOG1 data set. The DIV IDENTIFY macro could not identify the LOG2 data set. The DIV ACCESS macro could not access the LOG2 data set. The DIV MAP macro could not map the LOG1 data set. The chainer module was unable to find an entry in the GBLBLKQ11 queue. The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue. The chainer module was unable to find an entry in the GBLBLKQ22 queue. The physical logger found that both the primary and secondary active logs are in a stopped state. The routine to obtain new active log could not obtain the LOGQ latch. The routine to obtain new active log could not release the LOGQ latch. The chainer module could not obtain a command buffer. The chainer module could not obtain a work area. The GETSTOC routine was unable to determine the number of available blocks for logging to the LOG1 data set. The GETSTOC routine was unable to determine the number of available blocks for logging to the LOG2 data set. A GETNEWL error occurred while attempting to get a new log during initialization. The PowerExchange physical logger was unable to determine if a new active LOG2 exists. The PowerExchange physical logger was unable to determine if a new active LOG1 exists. The INIACTL routine could not initialize a new log. The chainer module was unable to find an entry in the GBLBLKQ11 queue. The chainer module was unable to find an entry in the GBLBLKQ12 queue. The chainer module was unable to find an entry in the GBLBLKQ21 queue.
934

Reason Code 00F9FF0B 00F9FF0C 00F9FF0D 00F9FF0E 00F9FF0F 00F9FF10 00F9FF11 00F9FF12 00F9FF13 00F9FF14 00F9FF15 00F9FF16 00F9FF17 00F9FF18 00F9FF19 00F9FF1A 00F9FF1B 00F9FF1C 00F9FF1D 00F9FF1E 00FAFF01 00FAFF02 00FAFF03 00FAFF04 00FAFF05 00FAFF06 00FAFF07 00FAFF08 00FAFF09 00FAFF0A 00FAFF0B 00FAFF0C 00FAFF0D 00FAFF0E 00FAFF0F 00FAFF10 00FAFF11 Explanation The chainer module was unable to find an entry in the GBLBLKQ22 queue. The chainer module was unable to add a LOCAL control block. The chainer module could not initialize the OPQ queue. An attempt to obtain a LOGQ latch failed. An attempt to release the LOGQ latch failed. No space is available in the active log. The physical logger processor (EDMLPLG0) was unable to build a UOW queue. The physical logger processor (EDMLPLG0) could not obtain the LOGS log queue. The physical logger processor (EDMLPLG0) entered an ESTAE routine. The physical logger processor (EDMLPLG0) encountered an invalid log RBA. The physical logger processor (EDMLPLG0) could not obtain a log queue latch. The physical logger processor (EDMLPLG0) could not release a log queue latch. The physical logger processor (EDMLPLG0) was unable to connect to PowerExchange common services. A write error occurred. There is no secondary log. A write error occurred. The other log was already stopped. Failure in attaching active log 2 subtask (EDMLPLG2). No available active log dataset. Number of secondary active log datasets does not match number of primary active log datasets. Archive log operation failed at initialization. Attempt to log data while logger is quiesced The chainer module could not obtain a work area. The chainer module was unable to obtain a buffer prefix. The chainer module was unable to obtain a buffer. A GETBUFF macro error occurred. It was unable to get a buffer. A MOVEREC macro error occurred, and it returned an unknown return code. The chainer module is unable to add a unit of work (UOW). The chainer module is unable to delete a unit of work (UOW). A WRITE to a restart data set (ERDS) failed. The MOVEREC macro could not write to a log begin_checkpoint record. The MOVEREC macro could not write to a log UOW_summary record. The MOVEREC macro could not write to a log end_checkpoint record. The chainer module was unable to add an entry to the CHK queue. The logical logger processor was unable to obtain a LOGQ latch. An attempt to connect to common services failed. The chainer module was unable to delete an entry from the CHK queue. The $DLICQPL macro could not open a circular queue. The PowerExchange logical logger processor (EDMLLLG0) was unable to obtain a LOGS latch.
Reason Codes
935

Reason Code 00FAFF12 00FAFF13 00FAFF14 00FAFF15 00FAFF16 00FAFF17 00FAFF18 00FAFF19 00FAFF1A 00FAFF1B 00FAFF1C 00FAFF1D 00FAFF1E 00FBFF01 00FBFF02 00FBFF03 00FBFF04 00FBFF05 00FBFF06 00FBFF07 00FBFF08 00FBFF0A 00FBFF0B 00FBFF0C 00FBFF0D 00FBFF0E 00FBFF0F 00FBFF10 00FBFF11 00FBFF13 00FBFF14 Explanation The PowerExchange logical logger processor (EDMLLLG0) was unable to read the global queue. The PowerExchange logical logger processor (EDMLLLG0) received a STIMERM SET error. The MOVEREC macro received a packet trailer error in the PowerExchange logical logger processor (EDMLLLG0) module. The PowerExchange logical logger processor (EDMLLLG0) module entered an ESTAE routine. The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a checkpoint (CHKPT). The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a checkpoint (CHKPT). The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a HARDN command. The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a HARDN command. The PowerExchange logical logger processor (EDMLLLG0) exceeded the maximum LOGRBA. The PowerExchange logical logger processor (EDMLLLG0) was unable to obtain a LOGQ latch. The PowerExchange logical logger processor (EDMLLLG0) received a STIMERM CANCEL error. The PowerExchange logical logger processor (EDMLLLG0) could not open the XCF message queue. The PowerExchange logical logger processor (EDMLLLG0) encountered an error in COMMUOW and could not complete a PUT command on the XCF message queue. The chainer module could not obtain a work area. The chainer module could not initialize the TC task control queue. The chainer module could not add an entry to the TCQ queue. The chainer module could not terminate the CMD queue. An error occurred while loading the dictionary. The chainer module could not delete the ECBLIST area. The chainer module could not obtain the ECBLIST area. The chainer module could not terminate the TCQ queue. The chainer module could not terminated the STR queue. The chainer module could not delete a work area. The chainer module could not terminate the GBLLIFPQ queue. The chainer module was unable to free an externalized CMD (EDMD) area. The chainer module could not delete the IPQ queue. The chainer module was unable to delete an entry from the LIFCMSQ queue. The chainer module could not add an entry to the TCQ queue. An ATTACH command returned a nonzero return code. The chainer module was unable to flush entries from the input CMD queue. The chainer module could not delete an entry from the TCQ queue.
936

Reason Code 00FCFF01 00FCFF02 00FCFF03 00FCFF04 00FCFF05 00FCFF06 00FCFF07 00FCFF09 00FCFF0A 00FCFF0B 00FCFF0C 00FDFF01 00FDFF02 00FDFF03 00FDFF04 00FDFF05 00FDFF06 00FDFF07 00FDFF08 00FDFF09 00FEFF01 00FEFF02 00FEFF03 00FEFF04 00FEFF05 00FEFF07 00FEFF08 00FEFF09 00FEFF0A 00FEFF0B 00FEFF0C 00FFCF01 00FFCF02 00FFCF03 00FFCF04 00FFCF05 00FFCF06 00FFCF07 Explanation The chainer module could not obtain a work area. The chainer module could not delete a work area. The chainer module could not delete the JNL queue. The chainer module could not delete data. The chainer module could not obtain a JNL record area. The chainer module could not release a JNL record area. An attempt to CLOSE or UNALLOCATE a JOURNAL data set failed. The journal processor (EDMLJNL0) encountered a SHOWCB error after a PUT function. The journal processor (EDMLJNL0) encountered a SHOWCB error after a PUT function. The journal processor (EDMLJNL0) encountered a SHOWCB error after a PUT function. An attempt to obtain an area to build a JOURNAL HEADER statement failed. An attempt to flush inactive LOCAL control blocks failed. An attempt by the chainer module to delete a local area failed. An attempt by the chainer module to obtain a work area failed. An attempt by the chainer module to release a work area failed. The chainer module was unable to free unused areas from the GBLP24Q queue. The chainer module was unable to free unused areas from the GBLP31Q queue. The chainer module was unable to free unused areas from the GBLGBLQ queue. Cannot determine which ECB posted. Error sending to global circular queue. The chainer module could not obtain a work area. The PowerExchange Logger was unable to open SYSIN. The chainer module was unable to add a local area control block. The PowerExchange Logger was unable to open SYSPRINT. The chainer module was unable to obtain an area to build an input record. The chainer module was unable to delete an output data area. The chainer module was unable to delete an I/O queue. The chainer module was unable to delete a local area. The chainer module was unable to delete a work area. The chainer module was unable to initialize an output queue. The third parameter, which shows the number of lines on a printed page, is invalid. The chainer module could not obtain a work area. The chainer module could not obtain a buffer area. The MODCB macro failed to modify the RPL control block. An attempt by this module to GET the master log control record failed. An attempt by the chainer module to FIND the master log control record failed. An attempt by this module to GET the primary active log control record failed. An attempt by the chainer module to FIND the primary active log control record failed.
Reason Codes
937

Reason Code 00FFCF08 00FFCF09 00FFCF0A 00FFCF0B 00FFCF0C 00FFCF0D 00FFCF0E 00FFDF01 00FFDF02 00FFDF03 00FFDF04 00FFDF05 00FFDF06 00FFDF07 00FFDF08 00FFDF09 00FFDF0A 00FFDF0B 00FFDF0C 00FFDF0D 00FFDF0E 00FFEF01 00FFEF02 00FFEF03 00FFF001 00FFF002 00FFF101 00FFF102 00FFF103 00FFF104 00FFF105 00FFF106 00FFF107 00FFF201 00FFF202 00FFF203 00FFF204 00FFF205 Explanation An attempt by this module to GET the secondary active log control record failed. An attempt by the chainer module to FIND the primary archive log control record failed. An attempt by this module to GET the next archive log failed. An attempt by the chainer module to FIND the secondary archive log control record failed. The MODCB macro failed to modify the RPL control block. An attempt by this module to GET the checkpoint control record failed. An attempt by this module to PUT the checkpoint control record failed. The chainer module could not obtain a work area. The chainer module could not obtain a buffer area. The MODCB macro failed to modify the RPL control block. An attempt by this module to GET the master log control record failed. An attempt by the chainer module to FIND the master log control record failed. An attempt by this module to GET the primary active log control record failed. An attempt by the chainer module to FIND the primary active log control record failed. An attempt by this module to GET the secondary active log control record failed. An attempt by the chainer module to FIND the primary archive log control record. An attempt by this module to GET the next archive log failed. An attempt by the chainer module to FIND the secondary archive log control record failed. The MODCB macro failed to modify the RPL control block. An attempt by this module to GET the checkpoint control record failed. An attempt by this module to PUT the checkpoint control record failed. An attempt to obtain a buffer for the master log failed. An attempt to perform an OPEN of the ERDS01 restart data set failed. An attempt to perform an OPEN of the ERDS02 restart data set failed. An attempt to obtain a read buffer failed. An attempt to add a checkpoint to the internal checkpoint queue failed. The chainer module was unable to initialize the LOGQ COPY1 queue. The chainer module was unable to initialize the BLKQ COPY1 queue. The chainer module was unable to obtain a read buffer. The chainer module was unable to add an entry to the BLKQ COPY2 queue. The chainer module was unable to add an entry to the active LOGQ COPY2 queue. The chainer module was unable to add an entry to the archive BLKQ COPY2 queue. The chainer module was unable to add an entry to the archive LOGQ COPY2 queue. The chainer module was unable to initialize the LOGQ COPY1 queue. The chainer module was unable to initialize the BLKQ COPY1 queue. The chainer module was unable to obtain a read buffer. The chainer module was unable to add an entry to the BLKQ COPY1 queue. The chainer module was unable to add an entry to the active LOGQ COPY1 queue.
938

Reason Code 00FFF206 00FFF207 00FFF301 00FFF302 00FFF303 00FFF304 00FFF305 00FFF306 00FFF307 00FFF401 00FFF402 00FFF403 00FFF404 00FFF405 00FFF406 00FFF407 00FFF501 00FFF502 00FFF601 00FFF602 00FFF701 00FFF702 00FFF801 00FFF802 00FFFB01 00FFFB02 00FFFC01 00FFFC02 00FFFD01 00FFFE01 00FFFF01 00FFFF02 00FFFF03 00FFFF04 00FFFF05 00FFFF06 Explanation The chainer module was unable to add an entry to the archive BLKQ COPY1queue. The chainer module was unable to add an entry to the archive LOGQ COPY1 queue. The chainer module was unable to initialize the LOGQ COPY1 queue. The chainer module was unable to initialize the BLKQ COPY1 queue. The chainer module was unable to obtain a read buffer. The chainer module was unable to add an entry to the BLKQ COPY2 queue. The chainer module was unable to add an entry to the active LOGQ COPY2 queue. The chainer module was unable to add an entry to the archive BLKQ COPY2 queue. The chainer module was unable to add an entry to the archive LOGQ COPY2 queue. The chainer module was unable to initialize the LOGQ COPY1 queue. The chainer module was unable to initialize the BLKQ COPY1 queue. The chainer module was unable to obtain a read buffer. The chainer module was unable to add an entry to the BLKQ COPY1 queue. The chainer module was unable to add an entry to the active LOGQ COPY1 queue. The chainer module was unable to add an entry to the archive BLKQ COPY1 queue. The chainer module was unable to add an entry to the archive LOGQ COPY1 queue. When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present. The chainer was unable to add a log to the internal log queue, LOGQ2. When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present. The chainer was unable to add a log to the internal log queue, LOGQ1. When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present. The chainer was unable to add a log to the internal log queue, LOGQ2. When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present. The chainer was unable to add a log to the internal log queue, LOGQ1. The chainer module could not find an archive log to delete. The chainer module was unable to perform a DELETE on the archive log queue, LOGQ2 The chainer module could not find an archive log to delete. The chainer module was unable to perform a DELETE on the archive log queue LOGQ1. The chainer module could not find an active log to delete. The chainer module could not find an active log to delete. The chainer module could not obtain a work area. The chainer module could not obtain an ERDS01 restart data set buffer. The chainer module could not obtain a ERDS02 restart data set buffer. The PowerExchange Logger is unable to build the LOGQ11 log queue. The PowerExchange Logger is unable to build the LOGQ12 log queue. The PowerExchange Logger is unable to build the LOGQ21 log queue.
Reason Codes
939

Reason Code 00FFFF07 00FFFF08 00FFFF09 00FFFF0A 00FFFF0B 00FFFF0C 00FFFF0D 00FFFF0E 00FFFF0F 00FFFF10 00FFFF11 00FFFF12 00FFFF13 00FFFF14 00FFFF15 00FFFF16 00FFFF17 00FFFF18 00FFFF19 Explanation The PowerExchange Logger is unable to build the LOGQ22 log queue. The PowerExchange Logger is unable to determine which log is the current active log. The ERDS01 restart data set DD statement is missing. The PowerExchange Logger found an invalid restart data set (ERDS). An attempt by the GENCB module to obtain the ACB for ERDS01 restart data set failed. An attempt to OPEN the ERDS01 restart data set failed. An attempt by GENCB to obtain the ACB for ERDS02 restart data set failed. An attempt to OPEN the ERDS02 restart data set failed. The online and ERDS01 restart data set is empty. An attempt by the GENCB macro to generate the RPL control block for the ERDS01 restart data set failed. An attempt by the GENCB macro to generate the RPL control block for the ERDS02 restart data set failed. An attempt to format the ERDS01 restart data set failed. An attempt to format the ERDS02 restart data set failed. An attempt to read the ERDS01 restart data set master log record failed. An attempt to read the ERDS02 restart data set master log record failed. An attempt by the MODCB macro to modify the ERDS01 restart data set RPL control block failed. An attempt by the MODCB macro to modify the ERDS02 restart data set RPL control block failed. The logger was unable to obtain the LOGQ latch. The logger was unable to build the checkpoint queue, CHKPT.
Reason Codes 01440600 to 060906FF: PowerExchange Utilities

Table 9-13 lists the reason codes issued by the PowerExchange utilities.
Table 9-13. Utility Reason Codes
Reason Code 01440600 01440601 01440602 01440603 01440604 01440609 01450605 01450606 01450607 01450608 Explanation The DCB failed to open properly. The PowerExchange Logger interface utility (EDMXLUTL) could not generate a required DCB. The PowerExchange Logger interface utility (EDMXLUTL) could not open a data set. The PowerExchange Logger interface utility (EDMXLUTL) could not close a data set. The PowerExchange Logger interface utility (EDMXLUTL) could not free a data set. A control card error was detected. The event command processor was (EDMXLEVT) unable to obtain working storage. The event command processor (EDMXLEVT) was unable to load the log utility process module. A bad PowerExchange standard record was detected. A bad PowerExchange canonical record was detected.
940
Table 9-13. Utility Reason Codes

Reason Code 01450618 0145061B 01450624 01450625 01450626 01450627 0145062E 01450651 01450652 01460605 01460619 0146061A 0146061B 0146061C 0146061D 0146061E 0146061F 01460620 01460621 01460622 01460623 01460625 01460626 01460627 01460629 0146062C 0146062D 0146062F 06030646 Explanation A PUT function for the output queue failed. The conversion buffer is too small. A LOAD function failed for the event command processor (EDMXLEVT). The build command service did not return an PowerExchange record. The event command processor (EDMXLEVT) could not find any active EDMNAMEs for data capture. Excessive number of descriptions (more than 5) to be added to event marker (from EDMXLEVT) The event command processor (EDMXLEVT) could not initialize the log utility because a previous failure occurred. A RETURN EDMNAME call failed. A DB2 request for a list of table names failed. The build command utility (EDMXIBCM) was unable to obtain working storage. A bad encoded command was passed to the build command utility (EDMXIBCM). No conversion buffer was passed to the build command utility (EDMXIBCM). The conversion buffer is too small. The conversion buffer length is zero. The conversion buffer has a bad header record. No worklist buffer was passed to the build command utility (EDMXIBCM). The worklist buffer is too small. The worklist buffer length is zero. The worklist buffer has a bad header record. A BUILD function failed for a pipe cleaner. A BUILD function failed for process termination. The build command utility (EDMXIBCM) did not return an PowerExchange record. A BUILD function fail for a registration list. The data set name is missing for a registration list request. The build command utility could not locate a database descriptor. A bad return code was received from a registration list request. The request type entered is not supported by the command module. The requested object category is invalid. A TESTCB function failed for the ACB.
Reason Codes 01800101 to 01FFFFFF: Change Interface Component

Table 9-14 lists the reason codes the Change Interface Component (CIC) issues.
Table 9-14. CIC Reason Codes
Reason Code 01800101 01800102 Explanation An invalid data type was found during an OPEN call. The GET and PUT functions require an open token.
Reason Codes
941

Reason Code 01800103 01800104 01800105 01800106 01800107 01800108 01800109 0180010A 0180010C 0180010D 01810101 01810102 01810103 01810104 01810105 01810106 01810107 01810108 01810109 Explanation An invalid IPC header was found. A prior error requires CIC to stop. For more information, see the previous error. No create token was provided. A global queue error occurred. The PowerExchange Agent is not active The mailman task ended prematurely. An error occurred in the mailman. The 'mailman ended' flag is on. The BUILD CDE function failed. The DELETE CDE function failed. CIC is being forced to terminate. A global queue error occurred. An error occurred during resync processing. A cross-memory post failed. The PowerExchange Logger quit during the termination process. The PowerExchange Logger is inactive, and the global directory (EDMSDIR) requested an abend. This code is returned during initialization in an offline environment. The caller requested that CIC post all units of work. The PowerExchange Logger has ended. The PowerExchange Logger is inactive, and the global directory (EDMSDIR) requested an abend. This code is returned during sync point processing in online IMS and CICS environments. The PowerExchange Logger terminated before the ECCR could connect to the logger. An XCF JOIN function failed. An XCF LEAVE function failed. An XCF PUT function failed. An XCF GET function failed. An XCF FREE BUFFER failed. An error occurred when CIC attempted to open a logger queue. The logger terminated during CIC initialization. The module was unable to get into a supervisory state. A name/token CREATE failed. A name/token RETRIEVE failed. A name/token DELETE failed. The BUILD CDE function failed. The DELETE CDE function failed. An error occurred when connecting to common services. A disconnect error from common services occurred. CIC is loading the program to CSA. Initialization for the module EDMCICLG failed.
0181010A 0181010B 0181010C 0181010D 0181010E 0181010F 01810110 01810111 01820101 01820102 01820103 01820104 01820105 01820106 01820107 01820108 01820109 0182010A
942

Reason Code 0182010B 0182010C 0182010D 01830101 01830102 01830103 01830104 01830105 01830106 01830107 01840101 01840102 01840103 01840104 01840105 01850101 01850102 01850103 01850104 01850105 01850106 01850107 01850108 01900101 01900102 01900103 01900104 01900105 01900106 01900107 01900108 01900109 01910101 01910102 01910103 01910104 01910105 01910106 Explanation The PUT function for the module EDMCICLG failed. Termination for the module EDMCICLG failed. A cross-memory post failed. An error was returned from the mailman. A name/token RETRIEVE failed. An invalid length was passed. The object's profile was not found. The mailman has ended. The PowerExchange Agent was unavailable during initialization. The PowerExchange Agent was unavailable during a registration call. An error occurred when connecting to common services. The SET STIMERM function failed. The STIMERM CANCEL function failed. An error occurred opening the mailman's queue. An error occurred closing the mailman's queue. An error was returned from the mailman. An error was returned from the mailman. The mailman abended. The mailman abended. The monitor subtask failed. The PowerExchange Agent is not active. An error occurred during a name/token RETRIEVE. Initialization for PowerExchange common services failed. Initialization for the module EDMCICIN failed. Termination for the module EDMCICIN failed. The mailman returned an error. A previous error occurred. For more information, see the previous error. The sync point 'begin phase 1' function failed. The sync point 'end phase 2' function failed. The logger stopped with abend U4094. The global directory (EDMSDIR) requested the abend. The PowerExchange Agent was not active during initialization. The PowerExchange Agent was not active during an OPEN call. An invalid function was received from the DB2 ECCR. No registration list was found for the table name. The registration routine returned an error. The module could not find a UOW entry, FREEUOW. The module could not find UOW entry, RECORD Sync point phase 1 failed.
Reason Codes
943

Reason Code 01910107 01910108 01910109 0191010A 0191010B 0191010C 0191010D 01920101 01920102 01920103 01920104 01920105 01920106 01920107 01920109 0192010A 0192010B 0192010C 0192010D 01930101 01930102 01930103 01930104 01930105 01930106 01930107 01930108 01930109 0193010A 0193010B 0193010C 01940101 01940102 01940103 01960101 01970101 01970102 01970103 Explanation Sync point phase 2 failed. Initialization for the module EDMCICIN failed. Termination for the module EDMCICIN failed. The PowerExchange Agent is not active. The PowerExchange Logger is not available. Error in resync processing (receiving outstanding UOWs from Logger) Error in count of outstanding UOWs received from Logger A previous error occurred. For more information, see the previous error. An invalid function code was encountered. The INIT function was called twice. CIC was not called for initialization. The module could not find its entry in the UOW table. The module is not capturing the specified file. An invalid sync parameter was encountered. Initialization for the module EDMCICIN failed. Termination for the module EDMCICIN failed. The registration routine returned an error. The mailman returned an error. The PowerExchange Agent is not active. Initialization for the module EDMCICIN failed. Termination for the module EDMCICIN failed. The IMODULE GETMAIN function failed. The IMODULE LOAD function failed. The module was unable to get into a supervisory state. The module could not find the PowerExchange Agent SSCT. The module encountered an invalid agent control block. The module could not find the IMS SSCT. There are no DBDs to capture. Initialization for the module $MSGX failed. Termination for the module $MSGX failed. The PowerExchange Agent is not active. The input vector for the calling program is too high. The module encountered an invalid UOW address. The PowerExchange Logger stopped, and the global options module (EDMSDIR) requested that the ECCR abend. An IMS ESS definition is required. The database is not registered for capture. The module was not passed the working storage address. A name/token RETRIEVE failed.
944

Reason Code 01970104 01990101 01990102 01990103 01990104 01990105 019B0101 019B0102 019B0103 019D0101 01A00101 01A00102 01A00103 01A00104 01A00105 01A00106 01A00107 01A00108 01A00109 01A0010A 01A0010B 01A0010C 01A0010D 01A0010E 01A0010F 01A00110 01A00111 01A20102 01A30101 01A30102 01B70101 01B70102 01B70103 01B70104 01A30103 01C40101 01C40102 Explanation Not an online region. No databases to capture. The module could not locate the DD name for the DBD in TIOT. An error occurred in locating JFCB. An error occurred when initializing the registration routine. An error occurred during in a GET function from the registration routine The input vector for the calling program is too high. The module encountered an invalid UOW address. The PowerExchange Logger stopped, and the global options module (EDMSDIR) requested that the ECCR abend. An IMS ESS definition is required. A subsystem is required. A global queue error occurred. The $GENDCB module failed. An OPEN function from the $GENDCB module failed. A CLOSE function from the $GENDCB module failed. An FREE function from the $GENDCB module failed. The DD statement PWXEDMCC is missing. The OPEN function failed. SET STIMERM failed. STIMERM CANCEL failed. An error occurred while the module was connecting to PowerExchange common services. An XCF JOIN function failed. An XCF LEAVE function failed. An XCF DESTDEL function failed. An XCF GET function failed. An XCF PUT function failed. An XCF FREEBUFF function failed. A global queue error occurred. A CIC initialization error occurred. A CIC termination error occurred. The agent from the SSM member is not active. The EDMSCTRL control block is invalid. The program must run in an IMS control region. There is a loop in the "ESAF add" routine. An invalid IPC header was found in the record. The input vector for the calling program is too high. The module encountered an invalid UOW address.
Reason Codes
945

Reason Code 01C40103 01C70101 Explanation The PowerExchange Logger stopped, and the global options module (EDMSDIR) requested that the ECCR abend. An IMS ESS definition is required.
Reason Codes 04050000 to 0812000C0: Circular Queue

The circular queue reason codes, displayed in the format xxyyzzzz, are comprised of the following parts:

xx is the hexadecimal return code. yy is the function code. Table 9-15 lists the circular queue function codes. zzzz is the reason code.Table 9-16 lists the circular queue reason codes.
Table 9-15. Circular Queue Function Codes

Function Code 01 02 03 04 05 06 08 0A 11 12 Description circular queue initialization (INIT) circular queue termination (TERM) circular queue open (OPEN) circular queue close (CLOSE) circular queue get (GET) circular queue put (PUT) circular queue delete (DELETE) circular queue create (CREATE) set end-of-file (SETEOF) on circular queue circular queue find-token (FNDTKN)
The circular queue reason codes are:

Table 9-16. Circular Queue Reason Codes
Reason Code 04050000 04050004 04120004 08010004 08010040 08020004 08020044 08020048 Explanation The circular queue module (EDMXCIRQ) GET function found no records available and encountered the end-of-file. The circular queue module (EDMXCIRQ) GET function found no records available from a conditional GET function. The circular queue module (EDMXCIRQ) FNDTKN function could not find the $DLICQTS opened-input control blocks. The circular queue module (EDMXCIRQ) INIT function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) INIT function's virtual-storage request for a circular queue initialization-token area failed. The circular queue module (EDMXCIRQ) TERM function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) TERM could not find the token value for the circular queue initialization control block. The circular queue module (EDMXCIRQ) TERM function encountered an invalid circular queue initialization control-block identifier.
946

Reason Code 08030004 08030008 08030010 08030020 08030024 08030028 08030030 08030034 08030036 08030038 08040004 08040008 08040010 08040014 08040018 08050004 08050008 08050010 08050014 08050018 08050020 08060004 08060008 08060010 Explanation The circular queue module (EDMXCIRQ) OPEN function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) OPEN function could not find the $DLICQMN control block. The circular queue module (EDMXCIRQ) OPEN function encountered an invalid open-request type. The circular queue module (EDMXCIRQ) OPEN function encountered an unavailable GET TASK block because of too many open requests for input. The circular queue module (EDMXCIRQ) OPEN function encountered an unavailable dynamic PUT TASK block because the virtual storage request failed. The circular queue module (EDMXCIRQ) OPEN function encountered an unavailable static PUT TASK block because of too many open requests for output. The circular queue module (EDMXCIRQ) OPEN function encountered a fixed-length logical record length (LRECL) less than 8 bytes. The circular queue module (EDMXCIRQ) OPEN function encountered a fixed-length LRECL greater than the maximum value allowed for the queue. The circular queue module (EDMXCIRQ) OPEN function does not allow the use of the WAIT=NO setting without also using the GET in LOCATE mode. The circular queue module (EDMXCIRQ) OPEN function does not allow the use of the WAIT=NO setting with a global queue. The circular queue module (EDMXCIRQ) CLOSE function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) CLOSE function could not find the $DLICQTS control block. The circular queue module (EDMXCIRQ) CLOSE function encountered an unopened $DLICQTS control block. The circular queue module (EDMXCIRQ) CLOSE function found that another task opened the $DLICQTS control block. The circular queue module (EDMXCIRQ) CLOSE function encountered an unknown $DLICQTS control-block task type. The circular queue module (EDMXCIRQ) GET function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) GET function could not find the token value for the $DLICQTS control block. The circular queue module (EDMXCIRQ) GET function found that the current task control block (TCB) does not own the $DLICQTS control block. The circular queue module (EDMXCIRQ) GET function found a $DLICQTS control block not opened for input. The circular queue module (EDMXCIRQ) GET function found a $DLICQTS control block at the end-of-file. The circular queue module (EDMXCIRQ) GET function encountered an invalid $DLICQEB control block. The circular queue module (EDMXCIRQ) PUT function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) PUT function could not find the token value for the $DLICQTS control block. The circular queue module (EDMXCIRQ) PUT function found that the current task control block (TCB) does not own the $DLICQTS control block.
Reason Codes
947

Reason Code 08060014 08060018 08060020 Explanation The circular queue module (EDMXCIRQ) PUT function found a $DLICQTS control block not opened for output. The circular queue module (EDMXCIRQ) PUT function encountered an invalid record size. The circular queue module (EDMXCIRQ) PUT function encountered a non-zero return code from a STATUS SET,MC,PROCESS macro call The circular queue module (EDMXCIRQ) PUT function encountered a non-zero return code from a STATUS RESET,MC,PROCESS macro call The circular queue module (EDMXCIRQ) DELETE function could not find the address for the $DLICQPL parameter list. The circular queue module (EDMXCIRQ) DELETE function could not find the address for the $DLICQMN control block. The circular queue module (EDMXCIRQ) SETEOF function could not find the address for the $DLICQPL macro. The circular queue module (EDMXCIRQ) SETEOF function could not find the address for the $DLICQPL macro. The circular queue module (EDMXCIRQ) SETEOF function encountered an invalid control-block identifier for the $DLICQMN control block. The circular queue module (EDMXCIRQ) SETEOF function encountered an invalid control-block identifier for the $DLICQMN control block. The circular queue module (EDMXCIRQ) SETEOF function found unclosed PUT tasks. The circular queue module (EDMXCIRQ) SETEOF function found unclosed PUT tasks. The circular queue module (EDMXCIRQ) SETEOF function found no available buffer space for the end-of-file indication. The circular queue module (EDMXCIRQ) SETEOF function found no available buffer space for the end-of-file indication. The circular queue module (EDMXCIRQ) FNDTKN function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) FNDTKN function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) FNDTKN function could not find the token value for the $DLICQMN control block. The circular queue module (EDMXCIRQ) FNDTKN function could not find the token value for the $DLICQMN control block. The circular queue module (EDMXCIRQ) FNDTKN function encountered a missing TCB owner value. The circular queue module (EDMXCIRQ) FNDTKN function encountered a missing TCB owner value. The circular queue module (EDMXCIRQ) FNDTKN function found that the current address space did not create this queue. The circular queue module (EDMXCIRQ) FNDTKN function found that the current address space did not create this queue. The circular queue module (EDMXCIRQ) FNDTKN function could not find any input $DLICQTS control blocks for this queue. The circular queue module (EDMXCIRQ) FNDTKN function could not find any input $DLICQTS control blocks for this queue.
08060024
08080004 08080008 08110004 08110004 08110010 08110010 08110014 08110014 08110018 08110018 08120004 08120004 08120008 08120008 08120010 08120010 08120014 08120014 08120018 08120018
948

Reason Code 0803000C 0803003C 0804000C 0804001C 0805000C 0805001C 080500FF 0806000C 0806001C 080600FF 0808000C 080A0004 080A0010 080A0014 080A0018 080A001C 080A0020 080A0030 080A0034 080A0038 080A003C 0811000C 0811000C Explanation The circular queue module (EDMXCIRQ) OPEN function encountered an invalid control-block identifier for the $DLICQMN control block. The circular queue module (EDMXCIRQ) OPEN function does not allow the use of the find-token (FNDTKN=Y) parameter with a global queue. The circular queue module (EDMXCIRQ) CLOSE function encountered an invalid control-block identifier for the $DLICQTS control block. The circular queue module (EDMXCIRQ) CLOSE function found that an incorrect task attempted to close the $DLICQTS control block (FNDTKN processing). The circular queue module (EDMXCIRQ) GET function encountered an invalid control-block identifier for the $DLICQTS control block. The circular queue module (EDMXCIRQ) GET function encountered a COND=YES setting along with an incompatible WAIT=NO setting. The circular queue module (EDMXCIRQ) GET function encountered a termination request from the CQTECB post code. The circular queue module (EDMXCIRQ) PUT function encountered an invalid control-block identifier for the $DLICQTS control block. The circular queue module (EDMXCIRQ) PUT function encountered an invalid $DLICQEB control block. The circular queue module (EDMXCIRQ) PUT function encountered a termination request from the CQTECB post code. The circular queue module (EDMXCIRQ) DELETE function encountered an invalid identifier for the $DLICQMN control block. The circular queue module (EDMXCIRQ) CREATE function could not find the address for the $DLIGPPL parameter list. The circular queue module (EDMXCIRQ) CREATE function encountered a subpool value outside 0 and 255 (inclusive). The circular queue module (EDMXCIRQ) CREATE function encountered a GET task-count value outside 1 and 15 (inclusive). The circular queue module (EDMXCIRQ) CREATE function encountered a PUT task-count value outside 0 and 255 (inclusive). The circular queue module (EDMXCIRQ) CREATE function encountered a buffer count value outside 1 and 255 (inclusive). The circular queue module (EDMXCIRQ) CREATE function encountered a buffer size value outside 4096 and 32760 (inclusive). The circular queue module (EDMXCIRQ) CREATE function's virtual-storage request for the $DLICQMN control block failed. The circular queue module (EDMXCIRQ) CREATE function's virtual-storage request failed for the $DLICQTS control block (GET TASK function). The circular queue module (EDMXCIRQ) CREATE function's virtual-storage request failed for the $DLICQTS control block (PUT TASK function). The circular queue module (EDMXCIRQ) CREATE function's virtual-storage request for circular queue buffers failed. The circular queue module (EDMXCIRQ) SETEOF function could not find the token value for the $DLICQMN control block. The circular queue module (EDMXCIRQ) SETEOF function could not find the token value for the $DLICQMN control block.
Reason Codes
949

Reason Code 0812000C 0812000C Explanation The circular queue module (EDMXCIRQ) FNDTKN function encountered an invalid control-block identifier for the $DLICQMN control block. The circular queue module (EDMXCIRQ) FNDTKN function encountered an invalid control-block identifier for the $DLICQMN control block.
Reason Codes 0A0B0001 to 0A0BFFFF: Log Write API

Table 9-17 lists the Log Write API function reason codes:
Table 9-17. Log Write API Reason Codes
Reason Code 0A0A000E 0A0A0010 0A0A0011 0A0A0012 0A0A0013 0A0B0001 0A0B0002 0A0B0003 0A0B0004 0A0B0005 0A0B0006 0A0B0007 0A0B0008 0A0B0009 0A0B000A 0A0B000B 0A0B000C 0A0B000D 0A0B000F 0A0B0014 0A0B0015 0A0B0016 0A0B0017 0A0B0018 0A0B0019 0A0B001A 0A0B001B 0A0B001C 0A0B001D 0A0B001F Explanation FirstThreeParmsIncomplete EdmcstubGetmainFailed LoadForEdmciapiFailed TokenFunctionMismatch InvalidToken TooManyParms RegTypeConflictWithAgent FunctionUnknownOrInvalidPerInitParms NotEnoughParmsForFunction FunctionProhibitedType0 FunctionProhibitedMultiTasked UOWNameIsNotLoggerConnectName DataParmInvalid 2ndDataParmInvalid FunctionInvalidPerInitOptions InvalidInitParm InternalErrorHandlingRegistrations InvalidAPIInitToken NullParameterPassed NoAPIInitToken APIInitTokenFunctionMismatch TokenGetmainFailed LoggerDisconnectFailed TERM_indoubt_UOW RegistrationCheckFailed LoggerConnectionFailed LoggerQueueOpenFailed LoggerInterfaceWriteFailed UOWAlreadyExists SendingChangeAfterCHK1
950

Reason Code 0A0B0020 0A0B0021 0A0B0022 0A0B0023 0A0B0024 0A0B0025 0A0B0026 0A0B0027 0A0B0028 0A0B0029 0A0B002A 0A0B002B 0A0B002C 0A0B002D 0A0B002E 0A0B002F 0A0B0030 0A0B0031 0A0B0032 0A0B0033 0A0B0034 0A0B0035 0A0B0036 0A0B0037 0A0B0038 0A0B0039 0A0B003A 0A0B003B 0A0B003C 0A0B003D 0A0B003E 0A0B0080 0A0B0081 0A0B0082 0A0B0083 0A0B0084 0A0B0085 0A0B0086 Explanation InternalErrorProcessingUOWs CommonSvcsInitFailed CommonSvcsConnectFailed ErrorObtainingLoggerResyncInfo ErrorTerminatingCommonSvcs HighSeqNotAscending LowSeqNotAscendingOrZero NameTokenFunctionFailed MissingAPIInitToken InconsistentMultiTaskInits UOWNotFound MustIssueCHK1First TooMuchExtendedInfoInPkt TooMuchExtendedInfoInChng InvalidLCIReturnArea MissingMSGDescTag InvalidDescTag EventMarkBuildFailed EvntMaxEdmnamesExceeded EvntMaxDescExceeded RegistrationInitializationFailed (this is new) AgentServicesUnavailable (this is new) RegistrationConnectionFailed RegistrationDisconnectionFailed InitType1MultiTaskedProhibited ConnTokenLogicErrorOnInit APIConnTokenNotFoundInChain APIConnTokenLogicErrorAtTerm FunctionProhibitedSingleTaskTerm LoggerMultitaskDisconnectFailed RegistrationMultitaskDisconnectionFailed RegistrationNameTooLong EccrNameTooLong Wrapper_InternalError Wrapper_TokenFunctionMismatch Wrapper_MemoryAllocationFailed Wrapper_InvalidToken Wrapper_UserIdTooLong
Reason Codes
951

Reason Code 0A0B0087 0A0B00C0 0A0B00C1 0A0B00C2 0A0B00C3 0A0B00D0 0A0B00D1 0A0B00D2 0A0B00D3 0A0B00D4 0A0B00D5 0A0B00D6 0A0B00D7 0A0B00D8 Explanation Wrapper_MessageTooLong XData_GNRS_Error XData_RSTR_Error XData_GHSQ_Error XData_GLCI_Error XData_LR_INIT_Error XData_LR_CONN_Error XData_LR_OPEN_Error XData_LR_GETL_Error XData_LR_BUOW_Missing XData_LR_NoRecords XData_LR_BUOWsNotFound XData_LR_PrematureEOF XData_LR_SIGNON_Missing
Reason Codes 0A0E0001 to 0A0EFFFF: Log Read API

Table 9-18 lists the Log Read API function reason codes:
Table 9-18. Log Read API Reason Codes
Reason Code 0A0D0300 0A0D0301 0A0D0302 0A0D0303 0A0D02FE 0A0E0001 0A0E0002 0A0E0003 0A0E0050 0A0E0051 0A0E0052 0A0E0053 0A0E0054 0A0E0055 0A0E0056 0A0E0057 0A0E0058 0A0E0059 0A0E005A Explanation EdmlrstbGetmainFailed LoadForEdmlrapiFailed TokenFunctionMismatch InvalidToken FirstThreeParmsIncomplete GETL_PROGRESS GETL_TIMEOUT GETL_EOF TooManyConnects InvalidSTDChgRec InvalidChgRecPFormat InvalidCRFChgRec InvalidSBCChgRec ConnectionIsOpen ConnectionNotOpen InvalidCONNParm LoggerConnectionFailed IncorrectHeaderVersion ESTAEFailedInHelper
952

Reason Code 0A0E005B 0A0E005C 0A0E005D 0A0E005E 0A0E005F 0A0E0060 0A0E0061 0A0E0062 0A0E0063 0A0E0064 0A0E0065 0A0E0066 0A0E0067 0A0E0070 0A0E0071 0A0E0072 0A0E0073 0A0E0074 0A0E0075 0A0E0076 0A0E0100 0A0E0101 0A0E0102 0A0E0103 0A0E0104 0A0E0105 0A0E0106 0A0E0107 0A0E0108 0A0E0109 0A0E010A 0A0E010B 0A0E010C 0A0E0110 0A0E0111 0A0E0112 0A0E0113 0A0E0114 Explanation HelperAttachFailed MissingOrDupSegs SegBufferSizeError InvalidOpenRBASeg ErrorManagingSegments ConnectionAlreadyOpen HelperTaskFailed LoggerDidNotRespondToCommand LoggerTerminatedConnection InvalidEventRec StorageObtainFailedInHelper OPENEndSEQltBeginSEQ InternalPlistError TimerSvcsActiveTimerInTransition TimerSvcsNoCONNToken TimerSvcsSTIMERMError TimerSvcsTimerAlreadyExists TimerSvcsTimerIDMismatch TimerSvcsNoActiveTimerInToken TimerSvcsTooManyTimers InvalidTokenType InvalidINITToken InvalidCONNToken ErrorCreatingLRAPILocalQueue ErrorOpeningLRAPILocalQueue ErrorLRAPILocalQueueNotOpen ErrorReadingLRAPILocalQueue ErrorLRAPILocalQueueEOF MoreThanOneAPIPerTCB ModuleLoadFailed ErrorWritingLRAPILocalQueue ErrorCreatingINTLSTCommand InterestListFailed ErrorDuringXCFJoin ErrorCreatingLoggerGlobalQueue ErrorOpeningLoggerGlobalQueue ErrorClosingLoggerGlobalQueue ErrorSendingCmdToLogger
Reason Codes
953

Reason Code 0A0E0115 0A0E0116 0A0E0117 0A0E0118 0A0E0119 0A0E011A 0A0E011B 0A0E011C 0A0E011D 0A0E011E 0A0E011F 0A0E0120 0A0E0121 0A0E0122 0A0E0123 0A0E0124 0A0E02F5 0A0E02F6 0A0E02F7 0A0E02FF 0A0E0304 0A0E0317 0A0E0318 0A0E0319 0A0E0320 Explanation ErrorReadingLoggerGlobalQueue ErrorTerminatingCommonSvcs ErrorInXCFGetMsg ErrorInXCFGetGroup ErrorInXCFFreeBuff RequestDataXferFailed InvalidRecordFromLogger StopDataXferFailed InvalidLCIReturnArea InvalidOpenParm BeginSeqRequired SEDMInitError SEDMAddError SEDMAddDuplicateEdmname SEDMTermError SEDMInternalError TooManyParms FunctionUnknownOrInvalidPerInitParms NotEnoughParmsForFunction NullParameterPassed TokenGetmainFailed CommonSvcsInitFailed CommonSvcsConnectFailed AgentServicesUnavailable ErrorProcessingExternalParameters
Reason Codes 10000001 to 1007FFFF: DB2 ECCR

Table 9-19 lists the DB2 ECCR reason codes.
Table 9-19. DB2 ECCR Reason Codes
Reason Code 10000001 10000002 10000003 10030001 10030002 10030003 Explanation The PowerExchange initialization module (CCDINI0) encountered an error when it attempted to initialize PowerExchange common services. The PowerExchange initialization module (CCDINI0) encountered an error when it attempted to connect to PowerExchange common services. The PowerExchange initialization module (CCDINI0) encountered an error when it attempted to initialize the schema checker (CCDSCHE). An attempt to get an EDMNAME failed. An attempt to get a schema failed. An attempt to change a schema failed.
954
Table 9-19. DB2 ECCR Reason Codes

Reason Code 10030004 10030005 10030006 10030007 10040001 10040002 10040003 10040005 10060001 10070001 10070002 10070003 10070004 10070005 10070006 10070007 Explanation An error occurred when the PDX interface (CCDRIOM) tried to acquire a command buffer. An error occurred when the PDX interface (CCDRIOM) tried to acquire a reply buffer. An error occurred when the PDX interface (CCDRIOM) received a call from the $RIOM macro. The PDX interface (CCDRIOM) could not find the EDMNAME in the registration list. The DB2 schema does not match the registration in the PowerExchange repository. An attempt to build an RCD record failed. A GETSCHEM call to the PDX interface (CCDRIOM) failed. During initialization, the DB2 ECCR schema checker (CCDSCHE) could not find a schema that matched the schema specified in the message. Schema verification failed. The DB2 ECCR found and invalid log record type. The DB2 ECCR could not locate the CREATE TIME field for the change record. The DB2 ECCR could not locate the ALTER TIME field for the change record. The DB2 ECCR (X029261) was unable to determine the DB2 version. The DB2 ECCR could not locate the data definition language (DDL) record end. The DB2 ECCR could not determine the data type for the column. The DB2 ECCR could not locate the source type identification (SOURCETYPEID) in the SYSCOLUMNS row.
Reason Codes 00000004 to 00000054: Chainer Module (EDMQMGR0)

Table 9-20 lists the Chainer Module reason codes:
Table 9-20. Chainer Module Reason Codes
Reason Code 00000004 00000008 0000000C 00000010 00000014 00000018 0000001C 00000020 00000024 00000028 0000002C 00000030 00000034 00000038 Explanation Record Not Found Insufficient Storage Invalid Record Prefix (Bad Addr) Invalid Flags or Key Addr Invalid Function Code Invalid Blksize/datal/lrecl TOQ Is Invalid Invalid Freespace Id Broken Synonym Chain KEYL Is Zero Ver Failed - BLKSIZE Ver Failed - Record Prefix Ver Failed - Ff000000 Not Last Exit Returned Non-zero
Reason Codes
955
Table 9-20. Chainer Module Reason Codes

Reason Code 0000003C 00000040 00000040 00000048 0000004C 00000050 00000054 Explanation Chain In Use Chain Already Locked, Lock Fails Chain Not Locked, Unlock Fails Invalid Owner of Locked Chain Serial Option Required Lock/unlk Invalid Register Form Parms Pagefix Unknown Return Code
956
CHAPTER 10
PWXPC Error Messages


Overview, 957 Messages 10000 through 10099, 957 Messages 11000 through 11099, 966 Messages 12000 through 12099, 967 Messages 12100 through 12199, 975
Overview
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. Messages from PowerExchange and PowerCenter also display in conjunction with these messages. For information about PowerExchange messages, see PowerExchange Message Reference. For information about PowerCenter messages, see PowerCenter Message Reference.
Messages 10000 through 10099

PWXPC_10001 Explanation: System Action: PWXPC_10002 Explanation: System Action: PWXPC_10003 Explanation: reader cannot get the Source Qualifier instances from the mapping. Internal error. Contact Informatica Global Customer Support. reader cannot get connection reference for the Source Qualifier instance qualifier_name. Internal error. Contact Informatica Global Customer Support. reader failed to initialize the source for the Source Qualifier instance qualifier_name. The Integration Service could not initialize the session.
957
System Action: PWXPC_10004 Explanation: System Action: PWXPC_10005 Explanation: System Action: PWXPC_10006 Explanation: System Action: PWXPC_10007 Explanation: System Action: PWXPC_10008 Explanation: System Action: PWXPC_10010 Explanation: System Action: PWXPC_10011 Explanation: System Action: PWXPC_10012 Explanation: System Action: PWXPC_10013 Explanation: System Action: PWXPC_10014 Explanation: System Action: PWXPC_10015 Explanation: System Action:
See the additional error message for more information. Cannot get connection property attribute_name. Internal error. Contact Informatica Global Customer Support. PowerExchange AllocEnv failed Internal error. Contact Informatica Global Customer Support. PowerExchange AllocConnect failed. Return code: return_code Internal error. Contact Informatica Global Customer Support. PowerExchange AllocConnect failed. Error message(s): additional_messages Internal error. Contact Informatica Global Customer Support. Cannot connect to the PowerExchange Listener. Return code: return_code. The Integration Service could not connect to the PowerExchange Listener. See the additional error message for more information. Cannot get metadata extension extension_name. Internal error. Contact Informatica Global Customer Support. PowerExchange AllocStmt failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information. PowerExchange Prepare failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information. PowerExchange Execute failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information. PowerExchange SetRow count failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information. PowerExchange Bind Col failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information.
958
Chapter 10: PWXPC Error Messages
PWXPC_10016 Explanation: System Action: PWXPC_10017 Explanation: System Action: PWXPC_10018 Explanation: System Action: PWXPC_10019 Explanation: System Action: PWXPC_10021 Explanation: System Action: PWXPC_10022 Explanation: System Action: PWXPC_10023 Explanation: System Action: PWXPC_10024 Explanation: System Action: PWXPC_10025 Explanation: System Action: PWXPC_10026 Explanation: System Action:
PowerExchange Group Fetch failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information. PowerExchange Fetch failed. Return code: return_code. PowerExchange Listener error. Check the additional error message for more information. Reader encountered an error during buffer flush. Internal error. Contact Informatica Global Customer Support. Connection parameter connection_attribute is missing. The specified connection attribute does not contain a value. Specify a value for the connection attribute. The schema is overwritten to [schema] in the session properties for the Source Qualifier [qualifier_name] The source schema in the source definition Metadata Extensions has been overridden in the session properties to the value shown. Informational. The data map is overwritten to [map_name] in the session properties for the Source Qualifier [qualifier_name] The data map name in the source definition Metadata Extensions has been overridden in the session properties to the value shown. Informational. reader prepared SQL statement [SQL_statement] for the group [group] in Source Qualifier [qualifier_name] for partition partition_number The prepared SQL statement for the source qualifier is shown. Informational. Partition [partition_number] initialized successfully The partition has successfully initialized. Informational. Cannot get the field projection information for the source source_name. Internal error. Contact Informatica Global Customer Support. reader cannot get the source list for the Source Qualifier qualifier_name. Internal error. Contact Informatica Global Customer Support.
959
PWXPC_10027 Explanation: System Action: PWXPC_10028 Explanation: System Action: PWXPC_10029 Explanation: System Action: PWXPC_10030 Explanation: System Action: PWXPC_10031 Explanation: System Action: PWXPC_10032 Explanation: System Action: Explanation: System Action: PWXPC_10033 Explanation: System Action: PWXPC_10034 Explanation: System Action:
The Source Qualifier [qualifier_name] has more than one source instance associated with it Multiple source definitions are connected to the same source qualifier. Associate only one source definition with a source qualifier. reader cannot get the value of the attribute attribute_name for the Source Qualifier qualifier_name. Internal error. Contact Informatica Global Customer Support. reader cannot get the fields for the source source_name. Internal error. Contact Informatica Global Customer Support. reader will use the extraction map [map_name] for the Source Qualifier [qualifier_name] The PowerExchange CDC Reader uses extraction map map_name. Informational. reader prepared SQL statement [sql_stmt] for extracting changed data for the relational Source Qualifier [qualifier_name] The SQL statement prepared for the source qualifier is displayed. Informational. An invalid extraction map name was provided for the source source_name of Source Qualifier qualifier_name. The extraction map in the session properties for the specified source is missing. Specify an extraction map in the session properties. or The extraction map name is not a valid extraction map name or is not the correct name for the source. Specify a valid extraction map name. Invalid filter string [filter] specified for Source Qualifier [qualifier_name] An invalid filter string is specified for the source qualifier. Informational. dispatcher cannot fetch changed data from the PowerExchange Listener. Error code: return_code. The Integration Service could not extract data from the PowerExchange Listener. See the PWXPC_10035 messages in the session log for more information about the error cause. Error message: [error_msg] The error message returned from PowerExchange is contained in error_msg. PWXPC_10035 is issued for each message returned by PowerExchange. The PowerExchange message number is included in error_msg. If necessary, see the PowerExchange messages manual to determine the error cause.
PWXPC_10035 Explanation:
System Action:
960
PWXPC_10036 Explanation: System Action:
dispatcher cannot connect to the PowerExchange Listener. Error code: return_code. The Integration Service could not connect to the PowerExchange Listener. See the PWXPC_10035 messages in the session log for more information about the error cause. dispatcher cannot create the transaction statement. Error code: return_code. Internal error. See the PWXPC_10035 messages in the session log for more information about the error cause. Contact Informatica Global Customer Support. dispatcher encountered an error in executing the transaction statement. Error code [return_code] Internal error. See the PWXPC_10035 messages in the session log for more information about the error cause. Contact Informatica Global Customer Support. dispatcher cannot bind the columns for the transaction statement. Error code return_code. Internal error. See the PWXPC_10035 messages in the session log for more information about the error cause. Contact Informatica Global Customer Support. The metadata extension attribute value [attribute] must start with a letter The attribute name must start with an alphabetic character. Correct the attribute name. The metadata extension attribute value [attribute] can only contain numbers and letters The attribute name contains characters that are not alpha numeric characters. Correct the attribute name. The metadata extension attribute 'AccessMethod' [access_method_value] is not valid for the source source_name. The value for the metadata extension attribute AccessMethod, access_method_value, is invalid in the XML file. The XML file may have been modified. Import the repository object from a new XML file. Avoid editing the XML file before importing. Invalid or duplicate group name [group_name] for the Extraction Map Name attribute for the Source Qualifier [qualifier_name] The group name specified for the extraction map is not valid. Correct the session. The Extraction Map Name attribute is not specified for the group [group_name] in the Source Qualifier [qualifier_name] The extraction map is not specified for the group displayed. Update the session and add the extraction map name.
PWXPC_10040 Explanation: System Action: PWXPC_10041 Explanation: System Action: PWXPC_10042 Explanation: System Action:
PWXPC_10043 Explanation: System Action: PWXPC_10044 Explanation: System Action:
961
The Extraction Map Name map_name is not valid for source source_name. The specified extraction map is not an extraction map for the source in the mapping. Specify an extraction map for the source in the mapping. Condense method method_name1 doesn't match with condense method method_name2. The mapping has multiple sources but their capture registrations do not all specify the same condense method. In the PowerExchange Navigator, ensure that each registration for each extraction map specified uses the same condense method. Condense method [cond_meth] is not valid. Condense Method have to be either 'Part' or 'Full' Internal error. Contact Informatica Global Customer Support. Connection parameters for different sources don't match. The connection attribute values for the connections you specified for the sources in the session properties are not the same. If you specify connections for each source, the connection attribute values of these connections must be identical to run a session in change or real-time mode. Specify a connection for the first source and specify None for the rest of the sources. Multiple connections are not required when running in change or real-time mode. Unable to find connection for PowerExchange CDC reader. Internal error. Contact Informatica Global Customer Support. A group name in the override [override] not matched to any projected group in the source The group name specified does not exist in the source. Correct the invalid group name specification. A group name [group_name] in the override [override] is duplicated The group name has been specified more than once. Correct the duplicate group name specification. The group name group_name in the filter filter is invalid. The group does not match any group names in the source. Specify a group name that matches a group name in the source. dispatcher cannot read restart tokens from the restart token file file_name. 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. See the additional error message for more information. dispatcher cannot write restart tokens to the restart token file file_name. 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.
PWXPC_10047 Explanation: System Action: PWXPC_10048 Explanation:
System Action:
PWXPC_10049 Explanation: System Action: PWXPC_10051 Explanation: System Action: PWXPC_10052 Explanation: System Action: PWXPC_10053 Explanation: System Action: PWXPC_10054 Explanation: System Action: PWXPC_10055 Explanation:
962
System Action: PWXPC_10056 Explanation: System Action: PWXPC_10057 Explanation: System Action:
See the additional error message for more information. dispatcher cannot open the restart token file file_name. The Integration Service could not open the restart token file. See the additional error message for more information. dispatcher cannot bind the restart token control columns for the transaction statement. Error code error_code. Internal error. See the PWXPC_10035 messages in the session log for more information about the error cause. Contact Informatica Global Customer Support. Recovery cache folder cache_folder_name specified for connection is invalid. Internal error. Contact Informatica Global Customer Support. CDC Reader reader failed to register for recovery. Internal error. Contact Informatica Global Customer Support. [process_id] Reader failed to flush to the recovery cache: [error_message] An error was encountered flushing the restart token information to the GMD. The error message, error_message, is the last messages from the GMD Cache coordinator. Contact Informatica Global Customer Support. [process_id] Reader failed to cache the restart token to the GMD: [error_message] An error was encountered caching the restart token in the GMD. The error message, error_message, is the last messages from the GMD Cache coordinator. Contact Informatica Global Customer Support. [process_id] Reader failed to close GMD checkpoint: [error_message] An error was encountered closing GMD checkpoint. The error message, error_message, is the last messages from the GMD Cache coordinator. Contact Informatica Global Customer Support. [process_id] reader failed to enable recovery for the Source Qualifier qualifier_name. Internal error. Contact Informatica Global Customer Support. [dispatcher] session ended after running for [rdr_time] seconds. Reader Time limit is reached The Integration Service stopped the session when the Reader Time Limit value, rdr_time, specified in the connection was reached. Informational. [dispatcher] session ended after waiting for [idle_time] seconds. Idle Time limit is reached PWXPC instructed the Integration Service to stop the session because the Idle Time value, idle_time, specified in the connection was reached.
Messages 10000 through 10099 963
PWXPC_10059 Explanation: System Action: PWXPC_10060 Explanation: System Action: PWXPC_10063 Explanation: System Action: PWXPC_10064 Explanation: System Action: PWXPC_10065 Explanation: System Action: PWXPC_10066 Explanation: System Action: PWXPC_10071 Explanation: System Action: PWXPC_10072 Explanation:
System Action: PWXPC_10073 Explanation: System Action:
Informational. [dispatcher] cannot bind restart tokens. Error Code [error_code]. Internal error. See the PWXPC_10035 messages in the session log for more information about the error cause. Contact Informatica Global Customer Support. [dispatcher] bound restart token successfully PWXPC has successfully bound the restart tokens. Informational. [dispatcher] could not create the restart token file [token_file] The restart token file could not be created. Ensure that the Integration Service has permission to create the file and that there is sufficient space. All the readers should be of one database type only The session contains multiple source database types and therefore multiple database readers. All source readers must be for the same database type. Correct the mapping. [dispatcher] raising real-time flush with restart tokens [restart1], [restart2] because UOW Count [uow_count] is reached PWXPC has flushed change data for the CDC sources to the targets because the UOW Count, uow_count, specified in the CDC connection has been reached. Informational. [dispatcher] raising real-time flush with restart tokens [restart1], [restart2] because Realtime Flush Latency [rtf_latency] occurred PWXPC has flushed change data for the CDC sources to the targets because the Real-time Flush Latency, rtf_latency, specified in the CDC connection has been reached. Informational. [dispatcher] writing restart tokens [restart1], [restart2] to the restart token file [token_filename] PWXPC has written the restart tokens to the restart token file, token_filename. Informational. Fatal Error: [dispatcher] could not allocate memory from heap Internal error. Contact Informatica Global Customer Support. dispatcher encountered an error in creating the environment object needed for connecting to PowerExchange Listener Internal error. Contact Informatica Global Customer Support.
PWXPC_10080 Explanation: System Action: PWXPC_10081 Explanation: System Action: PWXPC_10082 Explanation: System Action: PWXPC_10083 Explanation: System Action: PWXPC_10084 Explanation: System Action: PWXPC_10085 Explanation: System Action:
964
RestartToken File Folder token_folder_name specified for connection is invalid. The restart token file folder specified for the connection does not match a restart token file folder name on the Integration Service machine. Ensure that the restart token file folder you specify in the connection properties matches a restart token file folder on the Integration Service machine. [PWX_msg] PWXPC issues this message containing the message returned from PowerExchange when the connection specifies the Retrieve PWX log entries attribute. Informational. Relational source [schema.tablename] is invalid. Relational sources cannot have multiple groups A relational source has multiple groups. The source is invalid. Update the relational source mapping and remove any extraneous groups. The source [tablename], DB Type [db_type] is not a valid PWX source PWXPC encountered a table it does not recognize as a valid PowerExchange source. This is an internal error. Contact Informatica Global Customer Support. [dispatcher] raising real-time flush with restart tokens [restart1], [restart2] because RunTime Limit [run_limit] reached PWXPC has flushed change data for the CDC sources to the targets because the RunTime Limit, run_limit, specified in the CDC connection has been reached. Informational. Please use one group name for [source] in the query override for Extraction Map [map_name] The SQL query override specified for a multi-record source contains a duplicate group name. Correct the query override. The group name [group] in the query override for Extraction Map [map_name] is invalid The SQL query override specified for a multi-record source contains an unknown group name. Correct the query override. Invalid query override string [override] specified for Source Qualifier [source_qualifier] The SQL query override specified is invalid. Correct the query override. The field count [SQL_count] in the override SQL does not match the projected field count [source_count] for the source [source] The SQL Query override is invalid. It contains either too many or too few fields. Correct the query override.
PWXPC_10091 Explanation: System Action: PWXPC_10092 Explanation: System Action: PWXPC_10093 Explanation: System Action: PWXPC_10094 Explanation: System Action: PWXPC_10095 Explanation: System Action: PWXPC_10096 Explanation: System Action: PWXPC_10097 Explanation: System Action: PWXPC_10098 Explanation: System Action:
965

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

PWXPC_12001 Explanation: System Action: PWXPC_12002 Explanation: System Action: PWXPC_12003 Explanation: System Action: PWXPC_12004 Explanation: System Action: PWXPC_12005 Explanation: System Action: PWXPC_12006 Explanation: System Action: PWXPC_12008 Explanation: System Action: PWXPC_12010 Explanation: System Action: PWXPC_12011 Explanation: System Action: PWXPC_12012 Explanation: System Action: Session validation failed. See previous messages for cause The session failed to validate. See previous messages for the cause of the error. Requested driver for target [target] not found An invalid target driver was requested. Contact Informatica Global Customer Support. Requested driver for group [group] not found An invalid group driver was requested. Contact Informatica Global Customer Support. An error occurred accessing the target instance object An error occurred accessing the target instance object. Contact Informatica Global Customer Support. An error occurred parsing a user supplied SQL statement [sql_stmt] An error occurred parsing a user supplied SQL statement. Correct the SQL statement. Missing or invalid values clause detected for insert statement Missing or invalid values clause detected for insert statement. Correct the SQL statement. Invalid column name [column_name] detected for current table in user SQL Invalid column name detected for table in user SQL. Correct the SQL statement. User SQL parameter marker count [parm_cnt] does not match connected column count [col_cnt] User SQL parameter marker count, parm_cnt, does not match connected column count, col_cnt. Correct the SQL statement. Set clause of user SQL for update is invalid. Set clause of user SQL for update is invalid. Correct the SQL statement. User update SQL is missing a required clause (WHERE or SET). User SQL for update is missing a required clause, either WHERE or SET. Correct the SQL statement.
967
PWXPC_12013 Explanation: System Action: PWXPC_12014 Explanation: System Action: PWXPC_12015 Explanation: System Action: PWXPC_12016 Explanation: System Action:
Failed to retrieve session attribute [attribute] (attribute id[attr_id]) for session [session] Failure to retrieve the indicated session attribute, attribute, indicates possible corruption of the plug-in XML. Contact Informatica Global Customer Support. Number of Columns does not match number of Values specified for insert statement The number of columns does not match the number of values specified for insert statement. Correct the SQL statement. Error message: [pwx_msg] PowerExchange has returned an error message, pwx_msg. See the PowerExchange Message Reference for more information. Failed to create statement object. See following PWX messages for explanation PowerExchange encountered an error creating the statement object. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Prepare failed for the SQL statement [sql_stmt]. See following PWX messages for explanation PowerExchange encountered an error preparing the SQL statement. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Error encountered creating the environment object needed for connecting to PowerExchange Listener PWXPC encountered an error in creating the environment object needed to connect to PowerExchange. See PWXPC_12019. Contact Informatica Global Customer Support. error_msg PWXPC displays the message, error_msg, from the failure allocating the environment object. Verify that PowerExchange is correctly installed and available. Cannot connect to PowerExchange. Error code: [err_code]. See following PWX messages for explanation PWXPC encountered an error connecting to PowerExchange. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. No suitable conversion was found for the internal Powercenter datatype [pc_type] to PWX datatype [pwx_type] for column [column] PWXPC was unable to convert PowerCenter data type pc_type to PowerExchange data type pwx_type for column column. Contact Informatica Global Customer Support.
PWXPC_12018 Explanation: System Action: PWXPC_12019 Explanation: System Action: PWXPC_12020 Explanation: System Action:
968
Bind failed for parameter [parm_num] of the SQL statement [sql_stmt]. See following PWX messages for explanation Bind failed for parameter number parm_num. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Encountered a conversion error [rc = rc] fetching data for field [field_num] of row [row_num] for table [tablename]. PWXPC encountered a conversion error fetching field data. The field specification may be invalid. Contact Informatica Global Customer Support. Set paramoptions call failed for the SQL statement [sql_stmt]. See following PWX messages for explanation Set paramoptions call failed for the SQL statement sql_stmt. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Execution of the pre session SQL [sql_stmt] failed. The execution of the pre-session SQL statement sql_stmt failed. Correct the SQL statement. Execution of the post session SQL [sql_stmt] failed The execution of the post-session SQL statement sql_stmt failed. Correct the SQL statement. Execution of the truncate table SQL [sql_stmt] failed. The execution of the truncate table SQL statement sql_stmt failed. Correct the SQL statement. Commit request for the current connection failed. See following PWX messages for explanation The commit done by PowerExchange failed. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Rollback request for the current connection failed. See following PWX messages for explanation The rollback done by PowerExchange failed. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Describe failed for parameter [parm_num] of the SQL statement [sql_stmt]. See following PWX messages for explanation The describe done by PowerExchange failed See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause.
969
No key specification found for table [tablename]. Key must be specified if update or delete is required Table tablename has no key specified. Specify a key or select Insert only session option. Correct the session specifications. Insert operation failed Insert operation failed. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Update operation failed Update operation failed. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Delete operation failed Delete operation failed. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. Upsert operation failed Upsert operation failed. See the PowerExchange messages displayed in PWXPC_12015 for further information about the problem cause. The Upsert session attribute value [TRUE] is inconsistent with the confirm write connection attribute value [FALSE] Confirm Write has been disabled in the session connection. To use the Upsert attribute, you must specify either Confirm Write On or Asynchronous with Fault Tolerance in the Write Mode connection attribute. Session override [ovr_name] with value [ovr_value] is being used PWXPC uses session override ovr_name with value of ovr_value. Informational. Session property [prop_name] with value [prop_value] is being used PWXPC uses session property prop_name with value of prop_value. Informational. SQL statement [sql_stmt] successfully prepared for sql_action PWXPC has prepared the SQL statement sql_stmt. Informational. Processing Pre-SQL statement [sql_stmt] PWXPC is processing the SQL statement sql_stmt. Informational.
970
PWXPC_12055 Explanation: System Action: PWXPC_12056 Explanation: System Action: PWXPC_12057 Explanation: System Action: PWXPC_12058 Explanation: System Action: PWXPC_12060 Explanation: System Action: PWXPC_12062 Explanation: System Action: PWXPC_12063 Explanation: System Action: PWXPC_12064 Explanation: System Action: PWXPC_12065 Explanation:
Processing Post-SQL statement [sql_stmt] PWXPC is processing the SQL statement sql_stmt. Informational. Processing Truncate SQL [sql_stmt] PWXPC is processing the SQL statement sql_stmt. Informational. Connecting to PowerExchange with parameters: [conn_parms] PWXPC has connected to PowerExchange using the connection parameters conn_parms. Processing continues. [process_id] Unexpected data was encountered when reading the restart information from cache Unexpected data was encountered when reading the restart information. The cache may be corrupt. Contact Informatica Global Customer Support. session_restart_info PWXPC displays the extraction map name, the restart1 and restart2 tokens, and the source of the tokens for each source in the session. Informational. [process_id] Error encountered reading from the GMD state table: [error_message] An error was encountered reading from the GMD state table. PWXPC displays the last error message received from the GMD cache coordinator in error_message. Contact Informatica Global Customer Support. [process_id] Error encountered parsing data from the GMD state table An error was encountered parsing data from the GMD state table. The state table data may be corrupt. Contact Informatica Global Customer Support. [process_id] Error encountered resetting the GMD state table: [error_message] An error was encountered resetting the GMD state table. PWXPC displays the last error message received from the GMD cache coordinator in error_message. Contact Informatica Global Customer Support. [process_id] invalid hexadecimal representation of a restart token for Extraction Map [ext_map], sourced from [token_src] : [restart1] [restart2] The hexadecimal representation of the restart tokens, restart1 and restart2, is invalid. The ext_map variable contains either a specific extraction map name or ALL(Default Begin UOW) if all sources are affected. If token_src is Restart file, correct the restart tokens specified in the restart token file and restart the session. If token_src contains any other value, contact Informatica Global Customer Support.
System Action:
971
[process_id] restart tokens lengths [tok_len1]:[tok_len2] for map [ext_map], sourced from [token_src], is not consistent with previously read token lengths of [len1]:[len2] The hexadecimal length of the supplied restart tokens is inconsistent. PWXPC found restart tokens with hexadecimal length tok_len1 for the restart1 token and tok_len2 for the restart2 token. PWXPC expected len1 and len2 for the restart1 and restart2 tokens. The ext_map variable contains either a specific extraction map name or ALL(Default Begin UOW) if all sources are affected. If token_src is Restart file, correct the restart tokens specified in the restart token file and restart the session. If token_src contains any other value, contact Informatica Global Customer Support. [process_id] The length of the restart tokens received from PWX [pwx_len1]:[pwx_len2] is inconsistent with the token lengths read during restart [len1]:[len2] The length of the restart tokens read from PowerExchange is inconsistent with the token lengths read during restart. PowerExchange supplied a hexadecimal length of pwx_len1 for the restart 1 token and pwx_len2 for the restart2 token. PWXPC expected len1 and len2 for the restart1 and restart2 tokens. Correct the contents of the restart token file. [process_id] Last restart tokens read at reader termination : Restart 1 [restart1] : Restart 2 [restart2] During reader termination, PWXPC displays the last read restart token values. Depending upon the reason for reader termination, the changed data represented by these restart tokens may not be committed to the targets. Informational. [process_id] Running in recovery mode. Reader will resend the oldest uncommitted UOW to resync targets: from: Restart 1 [beg_restart1] : Restart 2 [beg_restart2] to: Restart 1 [end_restart1] : Restart 2 [end_restart2]. PWXPC is running in recovery mode and needs to re-synchronize the targets with the oldest uncommitted unit of work. PWXPC requests PowerExchange to send all data between tokens beg_restart1:beg_restart2 and end_restart1:end_restart2. Informational. [process_id] Recovery complete. Next session will restart at: Restart 1 [restart1] : Restart 2 [restart2]. PWXPC has completed recovery and updated the state table or file with the ending restart tokens, restart1 and restart2. The recovery session ends. Informational. [process_id] Error encountered writing to the GMD state table: [error_message] An error was encountered writing to the GMD state table. PWXPC displays the last error message received from the GMD cache coordinator in error_message. Contact Informatica Global Customer Support. [process_id] Recovery is not enabled for session. Restart cannot be guaranteed You did not enable a resume recovery strategy for a CDC session. Processing continues, but PWXPC does not guarantee that future restart processing will be accurate because recovery has not been requested.
System Action:
System Action: PWXPC_12068 Explanation:
System Action: PWXPC_12069
Explanation:
System Action: PWXPC_12070 Explanation: System Action: PWXPC_12071 Explanation: System Action: PWXPC_12072 Explanation: System Action:
972
User Response:
Change the CDC session and select Resume from last checkpoint for the Recovery Strategy attribute on the session Properties tab. [process_id] Session complete. Next session will restart at: Restart 1 [restart1] : Restart 2 [restart2] PWXPC reader has completed and displays the final restart tokens that will be used for the next warm start. Informational. Unable to expand session attribute attr_name PWXPC failed to expand a session attribute. Contact Informatica Global Customer Support. Unable to expand session attribute [attr_name] (attribute id[attr_id]) for session [session] PWXPC failed to expand session attribute attr_name. Contact Informatica Global Customer Support. Attempt to detect if group is projected failed. Source [source] ; Group [group] PWXPC could not detect projected groups. This is an internal error. Contact Informatica Global Customer Support. More than one DSQ contains projected groups and MergeCDCReaders is active This is an internal error. Contact Informatica Global Customer Support. Merged DSQ not found and MergeCDCReaders is active This is an internal error. Contact Informatica Global Customer Support. Original Source for a Merged DSQ not found This is an internal error. Contact Informatica Global Customer Support. Failed to retrieve the original Source for a Merged DSQ [dsq_name] This is an internal error. Contact Informatica Global Customer Support. Failed to retrieve the field list for the derivating Source for a Merged DSQ [dsq_name] This is an internal error. Contact Informatica Global Customer Support. Server flag MergeCDCReaders is set. All CDC Sources will be read in a single partition Custom property MergeCDCReaders=Yes is specified. Informational.
PWXPC_12075 Explanation: System Action: PWXPC_12080 Explanation: System Action: PWXPC_12081 Explanation: System Action: PWXPC_12082 Explanation: System Action: PWXPC_12083 Explanation: System Action: PWXPC_12084 Explanation: System Action: PWXPC_12085 Explanation: System Action: PWXPC_12086 Explanation: System Action: PWXPC_12087 Explanation: System Action: PWXPC_12088 Explanation: System Action:
973
PWXPC_12089 Explanation: System Action: PWXPC_12091 Explanation: System Action: PWXPC_12092 Explanation: System Action: PWXPC_12093 Explanation: System Action: PWXPC_12094 Explanation: System Action: PWXPC_12096 Explanation: System Action: PWXPC_12097 Explanation: System Action: PWXPC_12098 Explanation: System Action:
Server flag SingleThreadExecutionModel is set. Data from CDC Sources will not be repartitioned in the session Custom property SingleThreadExecutionModel=Yes is specified. Informational. [process_id] Cold start requested Cold start has been requested. Informational. [process_id] Warm start requested. Targets will be resynchronized automatically if required Warm start has been requested. If necessary, PWXPC performs recovery and continues session execution. Informational. [process_id] Recovery run requested. Targets will be resynchronized if required and processing will terminate Recovery has been requested. If necessary, PWXPC performs recovery and ends the session. Informational. [process_id] Advanced GMD recovery in affect. Recovery is automatic PWXPC uses advanced GMD recovery and automatically recovers the session. Informational. [process_id] Targets are in consistent state. No recovery required. During restart initialization processing, PWXPC has determined that recovery is not required. Informational. [process_id] An error was encountered setting the GMD application ID: [error_msg] An error was encountered setting the GMD application ID. Contact Informatica Global Customer Support. [process_id] Unable to establish restart points for recovery. PWXPC is unable to establish restart points for recovery because the session state data is corrupt. Update the restart token file with the restart tokens from the termination restart token file from the last successful session and cold start the session. [process_id] Read state length returned: status=[status_code] : cache status=[cache_code}] : Length=[len] PWXPC displays information returned from reading the state data from the state table. Informational.
974

PWXPC_12100 Explanation: System Action: PWXPC_12101 Explanation: System Action: PWXPC_12102 Explanation: [process_id] Read state info length returned: status=[status_code] : cache status=[cache_code}] : Length=[len] PWXPC displays information returned from reading the state data from the state file. Informational. [process_id] Realtime stop requested. Initiating end of file processing The Integration Service has requested that PWXPC stop gracefully. Informational. [process_id] raising real-time flush with restart tokens [restart1], [restart2] at end of CDC stream PowerExchange has indicated that the end of the change stream has been reached. The end of the change stream occurs when either the Idle Time is reached or the end of the last condense file is reached for PWX CDC Change connections. PWXPC flushes the restart tokens to the state table or state file. Informational. [process_id] raising real-time flush with restart tokens [restart1], [restart2] at end of recovery During recovery, PWXPC reads the last uncommitted unit of work and flushes the changed data to the targets. Informational. [process_id] raising real-time flush to flush initial restart tokens to the target During initialization, PWXPC determined that the reconciled restart tokens for all sources differs from what is currently recorded in the state table or state file. In this case, PWXPC commit the reconciled restart tokens to the state table or state file. [process_id] A token read from restart file exceeds maximum allowed length [max_len]. A restart token read from restart token file exceeds maximum allowed length. Correct the data in the restart token file and restart the session. [process_id] Expected restart token assignment not found for table [tablename]. PWXPC did not find the expected restart token assignment for the table tablename. Correct the data in the restart token file and restart the session. [process_id] Restart token [restart_token] specification exceeds the maximum allowed length[max_len]. Restart token length exceeded the maximum allowed length. Correct the data in the restart token file and restart the session. [process_id] Malformed override encountered reading from the restart file. The format of the special override statement in the restart token file is incorrect. Both RESTART1 and RESTART2 must be specified. Correct the data in the restart token file and restart the session.
System Action: PWXPC_12103 Explanation: System Action: PWXPC_12104 Explanation:
975
PWXPC_12109 Explanation: System Action: PWXPC_12110 Explanation: System Action: PWXPC_12111 Explanation: System Action: PWXPC_12112 Explanation: System Action: PWXPC_12113 Explanation: System Action: PWXPC_12114 Explanation: System Action: PWXPC_12115 Explanation:
[process_id] Unpaired restart specification encountered for table [tablename] while reading from the restart file. The format of the explicit override statement in the restart token file is incorrect. Both restart1 and restart2 token values must be specified for the table. Correct the data in the restart token file and restart the session. [process_id] Table [tablename] specified in the restart file is not a source in this session. A table specified in the restart token file is not a source in this session. Correct the data in the restart token file and restart the session. [process_id] The application name [app_name] length [app_length] exceeds the maximum allowed of max_len bytes. The application name, app_name, specified in the connection exceeds the maximum allowed length for application names. Correct the application name and restart the session. The application name [app_name] contains invalid characters. Allowed characters are alphanumerics and _#$% The application name, app_name, specified in the connection contains invalid characters. Correct the application name and restart the session. [process_id] Stop immediate detected. The Integration Service requested that PWXPC stop. Informational. [process_id] Wait for GMD checkpoint failed: [error_message] An error was encountered waiting on a GMD checkpoint. Target resources may be locked or unavailable. If the problem persists, contact Informatica Global Customer Support. Unable to map the insert column [column_name] to an update parameter as the column is not bound in the update. PWXPC is unable to map the indicated insert column to an update parameter as the column is not included in the update SQL. The Upsert option is ignored and processing continues. Correct the update SQL statement. Unable to map the insert column [column_name] to an update parameter as the column is bound more than once in the update. PWXPC is unable to map the indicated insert column to an update parameter as the column is included more than once in the update SQL statement. The Upsert option is ignored and processing continues. Correct the update SQL statement. Unable to map the update column [column_name] to an insert parameter as the column is not bound in the insert. PWXPC is unable to map the indicated update column to an insert parameter as the column is not included in the insert SQL statement. The Upsert option is ignored and processing continues.
976
Correct the insert SQL statement. Unable to map the update column [column_name] to an insert parameter as the column is bound more than once in the insert. PWXPC is unable to map the indicated update column to an insert parameter as the column is included more than once in the insert SQL statement. The Upsert option is ignored and processing continues. Correct the insert SQL statement. The insert column [column_name] will be mapped to update parameter [upd_position] for Upsert processing. The insert column, column_name, is mapped to the column in position upd_position in the update SQL statement. Informational. The update column [column_name] will be mapped to insert parameter [ins_position] for Upsert processing. The update column, column_name, is mapped to the column in position ins_position in the insert SQL statement. Informational. Upsert processing has been disabled due to previous errors. The Upsert option is disabled. Informational. Commit on EOF attribute for session must be disabled to guarantee restart. To guarantee that proper restart processing occurs, the PWXPC CDC reader must control commit processing to the targets. However, the Commit On End Of File option is enabled. When this option is enabled and a CDC sessions ends, PowerCenter performs a final commit after the PWXPC CDC reader has ended. This final commit can failure or duplicate data when the CDC session is restarted because the restart tokens do not match the state of the targets. Processing continues. Disable the Commit On End Of File attribute on the Properties tab of the CDC session. Failed creating statement object while fetching current restart information. See following PWX messages for explanation PowerExchange failed to create the statement object. Processing terminates. Review the PowerExchange messages in the session log to determine the cause of the failure. For additional assistance, contact Informatica Global Customer Support. Failed executing statement object while fetching current restart information. See following PWX messages for explanation PowerExchange failed to execute the statement object. Processing terminates. Review the PowerExchange messages in the session log to determine the cause of the failure. For additional assistance, contact Informatica Global Customer Support.
System Action: PWXPC_12119 Explanation: System Action: PWXPC_12120 Explanation: System Action: PWXPC_12121 Explanation: System Action: PWXPC_12122 Explanation:
System Action: User Response: PWXPC_12123 Explanation: System Action: User Response:
PWXPC_12124 Explanation: System Action: User Response:
977
Failed to fetch any current restart information. PowerExchange failed to fetch any current restart information. Processing terminates. Examine the PowerExchange logs at the location of the data source for the cause. For additional assistance, contact Informatica Global Customer Support. Failed creating connection object while fetching current restart information. See following PWX messages for explanation PowerExchange failed to create the connection object. Processing terminates. Review the PowerExchange messages in the session log to determine the cause of the failure. For additional assistance, contact Informatica Global Customer Support. Failed opening the PWX connection while fetching current restart information. See following PWX messages for explanation PowerExchange failed to open the connection to the remote PowerExchange. Processing terminates. Review the PowerExchange messages in the session log to determine the cause of the failure. For additional assistance, contact Informatica Global Customer Support. [dispatcher] raising real-time flush with restart tokens [restart1], [restart2] because Maximum Rows Per commit [commit_count] is reached PWXPC has flushed change data for the CDC sources to the targets because the Maximum Rows Per commit, commit_count, specified in the CDC connection has been reached. Informational. [process_id] Restart entry for [table_name] in the GMD restart information matches no source for this session. When adding or removing sources perform recovery to retrieve existing restart information followed by cold start. Table table_name is recorded in the GMD state restart information for this session. However, this table did not match any source in this session. Processing terminates. When adding or removing sources in CDC session, you must do the following: 1. Run recovery on the original session to populate the restart token file. 2. Alter the session to add or remove the source or target table. 3. If adding a source table, update the restart token file to provide restart tokens for the new source. 4. Cold start the session.
PWXPC_12128 Explanation: System Action: PWXPC_12129
PWXPC_12130
[process_id] Source table [table_name] has no matching restart information in the GMD restart information. When adding or removing sources perform recovery to retrieve existing restart information followed by cold start. Table table_name has no matching restart information in either the GMD state or the restart file. Processing terminates. When adding or removing sources in CDC session, you must do the following: 1. Run recovery on the original session to populate the restart token file.
978
2. Alter the session to add or remove the source or target table. 3. If adding a source table, update the restart token file to provide restart tokens for the new source. 4. Cold start the session. PWXPC_12131 Explanation: [process_id] A warm start was requested and no restart information was found in the GMD. Cold start must be performed to initialize the GMD restart information. You requested a warm start for a CDC session. PWXPC found no entry in the GMD state that matched the task instance ID and the application name specified in the CDC connection. Processing terminates. If this is a new CDC session that has not been previously run, you must use cold start. If you have modified the session and specified the incorrect application name in the CDC connection, correct it and restart the session. If you have modified the session to add or remove sources, then you must do the following: 1. Run recovery on the original session to populate the restart token file. 2. Alter the session to add or remove the source or target table. 3. If adding a source table, update the restart token file to provide restart tokens for the new source. 4. Cold start the session. PWXPC_12132 Explanation: System Action: PWXPC_12133 Explanation: System Action: PWXPC_12134 Explanation: Using Real-time Flush Latency of [rtf_latency] milliseconds. PWXPC uses the rtf_latency value that you specified on the PWX Real Time CDC application connection for the CDC session. Processing continues. Using Real-time Flush Latency of 2000 milliseconds. PWXPC uses the default value of 2000 milliseconds for the Real-time Flush Latency for the CDC session. Processing continues. Real-time Flush Latency disabled. You specified -1 for the Real-time Flush Latency value on the PWX Real Time CDC application connection for the CDC session. This value disables this option and so PWXPC does not use latency time to flush change data to the targets. Processing continues. If you want to flush change data to the targets using latency time, specify a non-negative value for the Real-time Flush Latency attribute. Otherwise, PWXPC uses the other commitment control attributes to control the flushing of change data to the targets. Teradata PT Restart behavior requested. Real-time Flush Latency will be ignored for first commit. You specified the TPTRecoveryModel=Yes custom property in the CDC session, which requests Teradata PT restart processing. When the Teradata PT restart processing is specified, PWXPC does the following:
Validates that you specified either the UOW Count or Maximum Rows Per commit attribute on the connection. For warm starts, disables the Real-time Flush Latency until one of the UOW Count or Maximum Rows thresholds is met.
Messages 12100 through 12199 979
For warm starts, ignores any empty UOWs generated by PowerExchange restart advance until one of the UOW Count or Maximum Rows thresholds is met.
User Response:
Use Teradata PT restart processing if the CDC session targets Teradata. Otherwise, do not specify the TPTRecoveryModel=Yes custom property. Teradata PT Restart behavior requires that UOW Count or Maximum Rows Per commit be > 0. You specified the TPTRecoveryModel=Yes custom property in the CDC session, which requests Teradata PT restart processing. To use Teradata PT restart processing, you must specify a value greater than zero for either the UOW Count or the Maximum Rows Per commit attribute on the PWX Real Time CDC connection. Processing terminates. Either disable Teradata PT restart processing or correct the connection for the CDC session. No threshold for Real-time flush specified. UOW Count, Maximum Rows Per commit, or Real-time Flush Latency must be > 0. The connection for the CDC session has disabled all of the commitment control attributes on the PWX CDC Real Time application connection. PWXPC cannot control commit processing to the targets for the CDC session. Processing terminates. You must specify a non-negative value for at least one of UOW Count, Maximum Rows Per commit, or Real-time Flush Latency attributes. Using Database Codepage [codepage_name][codepage_id]. PWXPC processes data using the database code page, codpage_name. Processing continues. Idle Time [idle_time] reset to 0 (stop at end of log) for offload processing. You selected Offload Processing in the CDC application connection for the session, and also specified a value greater than zero for the Idle Time attribute. PWXPC resets the Idle Time value to 0, which means that the CDC session stops after PowerExchange reaches the end of the change stream. When you use CDC offload processing, the value for the Idle Time attribute must either be -1 or 0. If you select -1, the CDC session continues to run until stopped. Otherwise, the CDC session ends when PowerExchange reaches the point that represented the end of the change stream when the session started.
PWXPC_12170 Explanation: System Action: PWXPC_12171 Explanation: System Action: User Response:
980
NOTICES
This Informatica product (the Software) includes certain drivers (the DataDirect Drivers) from DataDirect Technologies, an operating company of Progress Software Corporation (DataDirect) which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

PWX 861HF14 Message Reference

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

PWX 861HF14 Message Reference

Transféré par

Droits d'auteur :

Formats disponibles

Message Reference

Part Number: PWX-MES-861-0008

Chapter 1: PWX-00100 to PWX-35999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2: DTL_BMG003 to DTL_RPS105I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

Chapter 3: DTL58001 to DTL62591 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

Chapter 4: PWXEDM172000 to PWXEDM173002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

Chapter 5: PWXEDM175000 to PWXEDM175648 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

Chapter 6: PWXEDM176400 to PWXEDM177699 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785

Chapter 7: PWXEDM181200 to PWXEDM181599 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899

Chapter 8: PWXEDM261000 to PWXEDM263999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907

Chapter 9: Return and Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913

Chapter 10: PWXPC Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957

Informatica Web Site

Informatica How-To Library

Informatica Knowledge Base

Informatica Multimedia Knowledge Base

Informatica Global Customer Support

PWX-00101 Explanation: System Action: User Response:

PWX-00102 Explanation: System Action: User Response:

PWX-00103 Explanation: System Action: User Response:

PWX-00104 Explanation: System Action: User Response:

PWX-00105 Explanation: System Action: User Response:

Chapter 1: PWX-00100 to PWX-35999

PWX-00106 Explanation: System Action: User Response:

System Action: User Response: PWX-00108 Explanation:

System Action: User Response: PWX-00109 Explanation:

PWX-00111 Explanation: System Action: User Response:

PWX-00112 Explanation: System Action: User Response:

PWX-00118 Explanation: System Action: User Response:

PWX-00119 Explanation: System Action:

Chapter 1: PWX-00100 to PWX-35999

PWX-00122 Explanation: System Action: User Response:

PWX-00127 Explanation: System Action: User Response:

Chapter 1: PWX-00100 to PWX-35999

PWX-00138 Explanation: System Action: User Response:

PWX-00151 Explanation: System Action: User Response:

Chapter 1: PWX-00100 to PWX-35999

Chapter 1: PWX-00100 to PWX-35999

Chapter 1: PWX-00100 to PWX-35999

Chapter 1: PWX-00100 to PWX-35999

PWX-00215 Explanation: System Action: User Response:

PWX-00216 Explanation: System Action: User Response:

PWX-00217 Explanation: System Action: User Response:

PWX-00218 Explanation: System Action: User Response:

PWX-00219 Explanation: System Action: User Response:

PWX-00220 Explanation: System Action: User Response:

PWX-00221 Explanation: System Action: User Response:

PWX-00222 Explanation: System Action: User Response:

PWX-00223 Explanation: System Action: User Response: PWX-00224 Explanation:

PWX-00229 Explanation: System Action: User Response:

Chapter 1: PWX-00100 to PWX-35999

PWX-00230 Explanation: System Action: User Response:

PWX-00231 Explanation: System Action: User Response:

PWX-00232 Explanation: System Action: User Response:

PWX-00233 Explanation: System Action: User Response:

PWX-00234 Explanation: System Action: User Response:

PWX-00235 Explanation: System Action: User Response:

PWX-00236 Explanation: System Action: User Response:

PWX-00237 Explanation: System Action: User Response:

PWX-00238 Explanation: System Action: User Response:

PWX-00239 Explanation: System Action: User Response:

PWX-00240 Explanation: System Action: User Response:

PWX-00241 Explanation: System Action: User Response: