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 ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiInformatica 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PWX-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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623DTL_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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657DTL58001R to DTL62569I: Batch VSAM ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

Chapter 4: PWXEDM172000 to PWXEDM173002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671PWXEDM172000W 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

Chapter 5: PWXEDM175000 to PWXEDM175648 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities . . . . . . . . . . . . . . . . . . 775

Chapter 6: PWXEDM176400 to PWXEDM177699 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785PWXEDM176400E to PWXEDM176437E: CICS/VSAM ECCR . . . . . . . . . . . . . . . . . . . . 785 PWXEDM177000E to PWXEDM177593E: DB2 ECCR . . . . . . . . . . . . . . . . . . . . . . . . . . 792

Chapter 7: PWXEDM181200 to PWXEDM181599 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent . . . . . . . . . . . . . . . . 899 PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities . . . . . . . 903

Chapter 8: PWXEDM261000 to PWXEDM263999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907PWXEDM261000I to PWXEDM261010I: The Logger API . . . . . . . . . . . . . . . . . . . . . . . . 907 PWXEDM263000I to PWXEDM263039W: The Log Read API . . . . . . . . . . . . . . . . . . . . . 908

Chapter 9: Return and Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957 Messages 10000 through 10099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957 Messages 11000 through 11099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966 Messages 12000 through 12099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967 Messages 12100 through 12199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975

Table of Contents

v

vi

Table of Contents

PrefaceThis 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 ResourcesInformatica Customer PortalAs 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 DocumentationThe 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 [email protected]. 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 SiteYou 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 LibraryAs 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 BaseAs 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 [email protected].

Informatica Multimedia Knowledge BaseAs 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 [email protected].

Informatica Global Customer SupportYou 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

x

Preface

CHAPTER 1

PWX-00100 to PWX-35999This 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

1

PWX-00100 to PWX-00999PWX-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:





2

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-00109 Explanation:

System Action: User Response: PWX-00110 Explanation: System Action: User Response:


PWX-00100 to PWX-00999

3


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:

4


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


System Action: User Response: PWX-00121 Explanation: System Action: User Response:


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:

6



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

7


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 . 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.


8


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: . 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

PWX-00158 Explanation: System Action: User Response: PWX-00159 Explanation: System Action: User Response: PWX-00160 Explanation: System Action: User Response: PWX-00161 Explanation: System Action: User Response: PWX-00162 Explanation: System Action: User Response: PWX-00163 Explanation: System Action: User Response:

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


PWX-00166 Explanation: System Action: User Response: PWX-00167 Explanation: System Action: User Response: PWX-00168 Explanation: System Action: User Response: PWX-00169 Explanation: System Action: User Response: PWX-00170 Explanation:

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 , 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 . 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

PWX-00207 Explanation: System Action: User Response: PWX-00208 Explanation: System Action: User Response: PWX-00209 Explanation: System Action: User Response: PWX-00210 Explanation: System Action: User Response: PWX-00211 Explanation: System Action: User Response: PWX-00212 Explanation: System Action: User Response: PWX-00213 Explanation: System Action: User Response: PWX-00214 Explanation: System Action: User Response:

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 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 does not have access to , 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 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 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


PWX-00256 Explanation: System Action: User Response: PWX-00257 Explanation:

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:

PWX-00313 Explanation: System Action: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:

PWX-00357 Explanation: System Action:

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 instal

PWX 861HF14 Message Reference

Documents

Transcript of PWX 861HF14 Message Reference