Transcript
Page 1: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Informatica® PowerExchange10.2 HotFix 1

Message Reference Volume 3

Page 2: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Informatica PowerExchange Message Reference Volume 310.2 HotFix 1August 2018

© Copyright Informatica LLC 2011, 2018

This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. 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 LLC.

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.

Informatica, the Informatica logo, and PowerExchange are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product.

The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at [email protected].

Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.

Publication Date: 2018-08-07

Page 3: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 1: DTL0001 to DTL5008. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8DTL0001 to DTL5008: i5/OS Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: DTL58001 to DTL62569. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18DTL58001R to DTL62569I: Batch VSAM ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3: PWXEDM172000 to PWXEDM173002. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent. . . . . . . . . . . . . . . . . . . . 34

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger. . . . . . . . . . . . . . . . . . . . . 74

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC). . . . . . . . . . . . . . 132

PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger. . . . . . . . . . . . . . . . . . . 146

Chapter 4: PWXEDM175000 to PWXEDM175648. . . . . . . . . . . . . . . . . . . . . . . . . . . . 148PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities. . . . . . . . . . . . . . . . . . . . . . 148

Chapter 5: PWXEDM176400 to PWXEDM177699. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . 158

PWXEDM177012I to PWXEDM177699W: DB2 ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 6: PWXEDM181200 to PWXEDM181599. . . . . . . . . . . . . . . . . . . . . . . . . . . . 244PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent. . . . . . . . . . . . . . . . . . . . 244

PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities. . . . . . . . . . . . . 248

Chapter 7: PWXEDM261000 to PWXEDM263999. . . . . . . . . . . . . . . . . . . . . . . . . . . . 252PWXEDM261000I to PWXEDM261010I: The Logger API. . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

PWXEDM263000I to PWXEDM263039W: The Log Read API. . . . . . . . . . . . . . . . . . . . . . . . . . 253

Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages. 258Abend, Return, and Reason Codes Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

IBM Product Return and Reason Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Table of Contents 3

Page 4: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PowerExchange Abend Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Abend Code U0001 - PowerExchange Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Abend Code U0356 - Batch VSAM ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Abend Code U3035 - PowerExchange Logger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Abend Code U3680 - DB2 ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

PowerExchange Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Return Codes 0 to 12 - Standard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Return Codes 1 to 412 - Common. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Return Codes 0 to 12 - PowerExchange Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Return Code 221: PowerExchange Logger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Return Codes 0 to 8 - Batch VSAM ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

PowerExchange Reason Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Reason Codes xxxx0800 to xxxx081F - Common. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Reason Codes 001 to 255 - PowerExchange Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Reason Codes 00000601 to 00004499 - Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Reason Codes 00000813 to 00001515 - Encoded Commands. . . . . . . . . . . . . . . . . . . . . 270

Reason Codes 00000C00 to 00000C0E - Common Services. . . . . . . . . . . . . . . . . . . . . . . 270

Reason Codes 0033FF01 to 00FFFFFF - PowerExchange Logger. . . . . . . . . . . . . . . . . . . . 271

Reason Codes 01440600 to 060906FF - PowerExchange Utilities. . . . . . . . . . . . . . . . . . . 294

Reason Codes 01800101 to 01FFFFFF - Change Interface Component. . . . . . . . . . . . . . . . 296

Function Codes 01 to 0A - Circular Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Reason Codes 04050000 to 0812000C0 - Circular Queue. . . . . . . . . . . . . . . . . . . . . . . . 303

Reason Codes 0A0A000E to 0A0B00D8 - Log Write API. . . . . . . . . . . . . . . . . . . . . . . . . 307

Reason Codes 0A0D0300 to 0A0E0320 - Log Read API. . . . . . . . . . . . . . . . . . . . . . . . . . 310

Reason Codes 10000001 to 1007FFFF - DB2 ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Reason Codes 00000004 to 00000054 - Chainer Module (EDMQMGR0) . . . . . . . . . . . . . . . 314

4 Table of Contents

Page 5: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PrefacePowerExchange Message Reference Volume 3 provides explanations, system actions, and user responses for Informatica® PowerExchange® messages DTL0001 to DTL62569I and messages with the prefix PWXEDM. Also, this message reference describes the abend, return, and reason codes that appear in PowerExchange messages.

For information about PowerExchange messages PWX-00000 to PWX-09999, see PowerExchange Message Reference Volume 1.

For information about PowerExchange messages PWX-10000 to PWX-37999, DTL_BMG003 to DTL_RPS105I, and PWXPC_10000 to PWXPC_12199, see PowerExchange Message Reference Volume 2.

The message references apply to the following Informatica products:

• PowerExchange for Adabas

• PowerExchange for CA Datacom

• PowerExchange for CA IDMS

• PowerExchange for DB2 for i5/OS and Flat Files

• PowerExchange for DB2 for Linux, UNIX, and Windows

• PowerExchange for DB2 for z/OS

• PowerExchange for Flat Files on Linux, UNIX, and Windows

• PowerExchange for IMS

• PowerExchange for Oracle

• PowerExchange for SQL Server

• PowerExchange for VSAM (including sequential flat files)

Informatica Resources

Informatica NetworkInformatica Network hosts Informatica Global Customer Support, the Informatica Knowledge Base, and other product resources. To access Informatica Network, visit https://network.informatica.com.

As a member, you can:

• Access all of your Informatica resources in one place.

• Search the Knowledge Base for product resources, including documentation, FAQs, and best practices.

5

Page 6: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

• View product availability information.

• Review your support cases.

• Find your local Informatica User Group Network and collaborate with your peers.

Informatica Knowledge BaseUse the Informatica Knowledge Base to search Informatica Network for product resources such as documentation, how-to articles, best practices, and PAMs.

To access the Knowledge Base, visit https://kb.informatica.com. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at [email protected].

Informatica DocumentationTo get the latest documentation for your product, browse the Informatica Knowledge Base at https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx.

If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected].

Informatica Product Availability MatrixesProduct Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types of data sources and targets that a product release supports. If you are an Informatica Network member, you can access PAMs at https://network.informatica.com/community/informatica-network/product-availability-matrices.

Informatica VelocityInformatica Velocity is a collection of tips and best practices developed by Informatica Professional Services. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions.

If you are an Informatica Network member, you can access Informatica Velocity resources at http://velocity.informatica.com.

If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].

Informatica MarketplaceThe Informatica Marketplace is a forum where you can find solutions that augment, extend, or enhance your Informatica implementations. By leveraging any of the hundreds of solutions from Informatica developers and partners, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at https://marketplace.informatica.com.

Informatica Global Customer SupportYou can contact a Global Support Center by telephone or through Online Support on Informatica Network.

6 Preface

Page 7: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

To find your local Informatica Global Customer Support telephone number, visit the Informatica website at the following link: http://www.informatica.com/us/services-and-training/support-services/global-support-centers.

If you are an Informatica Network member, you can use Online Support at http://network.informatica.com.

Preface 7

Page 8: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 1

DTL0001 to DTL5008This chapter includes the following topic:

• DTL0001 to DTL5008: i5/OS Commands, 8

DTL0001 to DTL5008: i5/OS CommandsDTL0001E PowerExchange Command Handler Message Queue was not found in library library.

Explanation: The PowerExchange command handler message queue was not found in the library that was specified in the CMDHDLRLIB parameter in a SNDDTLCMD or SNDPWXCMD command.

System Action: SNDDTLCMD or SNDPWXCMD command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. Correct the library name in the CMDHDLRLIB parameter in the SNDDTLCMD or SNDPWXCMD command. Typically, this library is the DATALIB library.

3. Run the command again.

DTL0002E Duplicate option specified on parameter parameter.

Explanation: In an i5/OS command, a duplicate option was entered for the specified parameter.

System Action: PowerExchange command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the i5/OS command, remove the duplicate option from the specified parameter.

3. Run the command again.

DTL0003E ALL must be the only value for parameter parameter.

Explanation: In a SNDDTLCMD or SNDPWXCMD command, an invalid value was entered for the specified parameter. The only valid value for the specified parameter is ALL.

System Action: SNDDTLCMD or SNDPWXCMD command processing ends.

8

Page 9: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the SNDDTLCMD or SNDPWXCMD command, set the specified parameter to ALL.

3. Run the command again.

DTL0004E Trace condition must be specified for each program specified.

Explanation: In a SNDDTLCMD or SNDPWXCMD command, trace conditions were omitted from programs specified in the command. A trace condition is required for each program that is specified in the command.

System Action: SNDDTLCMD or SNDPWXCMD command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. For each program that is specified in the SNDDTLCMD or SNDPWXCMD command, specify a trace condition.

3. Run the command again.

DTL0005E One or more options must be specified for parameter parameter.

Explanation: In an i5/OS command, the specified parameter did not contain any options. This parameter must contain at least one option.

System Action: PowerExchange command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the i5/OS command, enter one or more valid options for the specified parameter.

3. Run the command again.

DTL0011E Library library already exists.

Explanation: In a CRTPWXENV command, the CONDLIB, CPXLIB, or DATALIB parameter specifies a library that already exists.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, including the library parameter that specifies an existing library, press F1 in the message text on the console.

2. In the CRTPWXENV command, enter a different library name in the specified library parameter.

3. Run the command again.

DTL0012E Library names must be different.

Explanation: In a CRTPWXENV command, the same library name was entered in more than one library parameter. Each library parameter must specify a different library name.

System Action: CRTPWXENV command processing ends.

DTL0001 to DTL5008: i5/OS Commands 9

Page 10: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Perform the following actions:

1. If you want to display additional information for the message, including the library name that is specified in multiple library parameters, press F1 in the message text on the console.

2. In the CRTPWXENV command, specify a different library name in each library parameter.

3. Run the command again.

DTL0013E A PowerExchange capture library must be specified if a PowerExchange Condense library is specified.

Explanation: In a CRTPWXENV command, a PowerExchange Condense library was specified in the CONDLIB parameter, but the CPXLIB parameter was set to *NONE. If a library is specified in the CONDLIB parameter, a PowerExchange capture library must be specified in the CPXLIB parameter.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, enter the PowerExchange capture library name in the CPXLIB parameter.

3. Run the command again.

DTL0014E PowerExchange Listener message queue was not found in library library.

Explanation: The PowerExchange Listener message queue was not found in the specified library. This library was specified in a SNDLSTCMD command.

System Action: SNDLSTCMD command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the SNDLSTCMD command, correct the library name.

3. Run the command again.

DTL0015E A PowerExchange Listener task name is required.

Explanation: A SNDLSTCMD command with the LSTCMD(STOPTASK) parameter did not specify a PowerExchange Listener task name. In this command, a PowerExchange Listener task name is required.

System Action: PowerExchange command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the command, enter the name of the PowerExchange Listener task in the STOPTASK parameter. For example:

SNDLSTCMD LSTMSGQLIB(DATALIB) LSTCMD(STOPTASK) STOPTASK(MYAPP)

3. Run the command again.

10 Chapter 1: DTL0001 to DTL5008

Page 11: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL0016E Confirmation message queue library/message_queue was not found.

Explanation: The specified confirmation message queue was not found in the library specified in the CFMMSGQ parameter in a SNDLSTCMD command. This confirmation message queue is a user-defined message queue and not a PowerExchange message queue.

System Action: SNDLSTCMD command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the SNDLSTCMD command, enter a valid library name and message queue name in the CFMMSGQ parameter.

3. Run the command again.

DTL0017E Confirmation message queue cannot be an internal PowerExchange message queue.

Explanation: The confirmation message queue specified in the CFMMSGQ parameter in a SNDLSTCMD command is an internal PowerExchange message queue, which is not allowed.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the SNDLSTCMD command, enter a valid library name and message queue name in the CFMMSGQ parameter. The message queue must be a user-defined confirmation message queue and must exist in the specified library. Do not specify any of the following message queue values: CHECKPOINT, CMDHANDLER, COLLECTOR, CONDENSE, CONTROLLER, DTLOS_MSGQ, DUMP, or LISTENER.

3. Run the command again.

DTL0018E There is no active PowerExchange Listener running for library library.

Explanation: A parameter in a SNDLSTCMD command specifies a library that does not have an active PowerExchange Listener.

System Action: SNDLSTCMD command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. For the library specified in the library parameter in the SNDLSTCMD command, start the PowerExchange Listener, or specify a different library name in the library parameter in SNDLSTCMD command.

3. Run the command again.

DTL0019E The ASPDEV parameter is not valid for OS/400 release level level.

Explanation: A library name was specified in the ASPDEV parameter in a CRTPWXENV command, but the specified version of the operating system does not support independent auxiliary storage pools (IASPs). IASPs were introduced in OS/400 release V5R2M0.

System Action: CRTPWXENV command processing ends.

DTL0001 to DTL5008: i5/OS Commands 11

Page 12: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, set the ASPDEV parameter to *NONE.

3. Run the command again.

DTL0020E ASP device device was not found or is not available.

Explanation: In a CRTPWXENV command, an invalid device name was specified in the ASPDEV parameter. The specified device is not available or is not a valid ASP device name on this machine.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command enter a valid device name in ASPDEV parameter.

3. Verify that the specified ASP device is available.

4. Run the command again.

DTL0021E A PowerExchange Journal exit program library cannot be specified if a PowerExchange Condense library is not specified.

Explanation: In a CRTPWXENV command, a PowerExchange Journal exit program library was specified in the EXTPGMLIB parameter, but a PowerExchange Condense library name was not specified in the CONDLIB parameter. If a library is specified in the EXTPGMLIB parameter, a PowerExchange Condense library must be specified in the CONDLIB parameter.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, either set the EXTPGMLIB parameter to *NONE, or specify a PowerExchange Condense library name in the CONDLIB parameter.

3. Run the command again.

DTL0022E A PowerExchange Journal exit program library must be specified.

Explanation: In a CRTPWXENV command, the EXTPGMLIB parameter was set to *NONE, which is an invalid value if a PowerExchange Condense library name is specified in the CONDLIB parameter and the PowerExchange environment is being created in an independent auxiliary storage pool (IASP).

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, specify a PowerExchange Journal exit program name in the EXTPGMLIB parameter.

3. Run the command again.

12 Chapter 1: DTL0001 to DTL5008

Page 13: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL0023E Journal exit program library must be set to *NONE.

Explanation: In a CRTPWXENV command, a PowerExchange Condense library name was specified in the CONDLIB parameter, and a PowerExchange Delete Journal Receiver exit program name was specified in the EXTPGMLIB parameter. However, the EXTPGMLIB parameter must be set to *NONE if the PowerExchange environment is not being created in an independent auxiliary storage pool (IASP).

System Action: The PowerExchange Condense library specified in the CONDLIB parameter is used as the PowerExchange Delete Journal Exit program library.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. If you do not want to use the PowerExchange Condense library as the PowerExchange Delete Journal Exit program library, specify a different library name in the EXTPGMLIB parameter.

3. Run the command again.

DTL0024E The file file was found in library library.

Explanation: During installation, PowerExchange detected the specified file, which is required for PowerExchange processing, in the specified library, which is part of the system portion of the library list. The existence of the specified file in the system portion of the library list will cause the installation to fail, so PowerExchange ends the installation process.

System Action: PowerExchange installation processing stops. No files are created.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. Remove the specified file from the specified library.

3. Start the installation again.

Note: If, for operational reasons, the specified file must be located in the system portion of the library list, abandon the installation and contact Informatica Global Customer Support.

DTL0025E RMTSYSNAME must be set to *NONE if RMTRDBDIRE is set to *LOCAL.

Explanation: In a CRTPWXENV command, the RMTRDBDIRE parameter was set to *LOCAL, but the RMTSYSNAME parameter was not set to *NONE. If the RMTRDBDIRE parameter is set to *LOCAL, the RMTSYSNAME must be set to *NONE.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, set the RMTSYSNAME parameter to *NONE.

3. Run the command again.

DTL0001 to DTL5008: i5/OS Commands 13

Page 14: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL0026E RMTSYSNAME must be specified if RMTRDBDIRE is not set to *LOCAL.

Explanation: In a CRTPWXENV command, the RMTRDBDIRE parameter was set to a value other than *LOCAL, but the RMTSYSNAME parameter was set to *NONE. If the RMTRDBDIRE parameter is not set to *LOCAL, the RMTSYSNAME must be set to a entry that is defined in the “Work with TCP/IP host table entries” function.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, set the RMTSYSNAME parameter to an entry defined in the “Work with TCP/IP host table entries” function, and set the RMTRDBDIRE parameter to an entry that is defined in the “Work with Relational Database Directory Entries (WRKRDBDIRE)” function.

3. Run the command again.

DTL0027E The remote DB directory entry entry is not valid

Explanation: In a CRTPWXENV command, the entry specified in the RMTRDBDIRE parameter was not found in the directory listing or failed PowerExchange validation.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, set the RMTRDBDIRE parameter to an entry that is defined in the “Work with Relational Database Directory Entries (WRKRDBDIRE)” function. The entry cannot be an entry associated with the local machine or the loopback address, or an entry with a remote location of *ARDPGM (Application Requester Driver).

3. Run the command again.

DTL0028E The remote system name entry is not valid.

Explanation: In a CRTPWXENV command, the entry specified in the RMTSYSNAME parameter was not found in the host table entries, or specifies the local machine.

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, set the RMTSYSNAME parameter to an entry that is defined in the “Work with TCP/IP host table entries” function. The entry cannot be the machine where the CRTPWXENV command is running.

3. Run the command again.

DTL0029E RMTASPDEV must be set to * if RMTRDBDIRE is set to *LOCAL.

Explanation: In a CRTPWXENV command, the RMTRDBDIRE parameter was set to *LOCAL, but the RMTASPDEV parameter was not set to *. If the RMTRDBDIRE parameter is set to *LOCAL, the RMTASPDEV parameter must be set to *.

14 Chapter 1: DTL0001 to DTL5008

Page 15: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: CRTPWXENV command processing ends.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. In the CRTPWXENV command, set the RMTASPDEV parameter to *.

3. Run the command again.

DTL2001I The PowerExchange Listener has no active tasks.

Explanation: The PowerExchange Listener has no active tasks. This message is displayed in response to a SNDLSTCMD command issued with the DISPLAY DISPLAYOPT(ACTIVE) parameter.

User Response: No response is required.

DTL3001I The application application finished processing entries from receiver receiver in library library.

Explanation: The application specified in a command finished processing entries from the specified receiver in the specified library and released the lock on the journal receiver that prevented the receiver from being deleted.

Note: This message is displayed during PowerExchange CDC processing if AS4JRNEXIT=Y is specified on the AS4J CAPI_CONNECTION statement and the AS400EVENTMSGQ statement is included in the DBMOVER configuration file on i5/OS.

System Action: PowerExchange CDC processing continues.

User Response: Perform the following actions:

1. If you want to display additional information for the message, press F1 in the message text on the console.

2. Perform any necessary actions for the specified journal receiver.

DTL3002W The application application ignored operation operation on file file in library library to continue PowerExchange CDC processing.

Explanation: A journal entry for a CLRPFM command was encountered. To enable PowerExchange change data capture (CDC) processing to continue, the specified application ignored the specified operation on the specified file in the specified library. PowerExchange cannot replicate changes made by a CLRPFM command.

Note: This message is displayed during PowerExchange CDC processing if ALWCLRPFM=Y is specified on the AS4J CAPI_CONNECTION statement and the AS400EVENTMSGQ statement is included in the DBMOVER configuration file on i5/OS.

System Action: PowerExchange CDC processing continues, but data integrity might be compromised for any targets to which changes are applied.

User Response: No response is required. If you want to display additional information for the message, press F1 in the message text on the console.

DTL0001 to DTL5008: i5/OS Commands 15

Page 16: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL3003I PowerExchange has processed add event event_identifier.

Explanation: PowerExchange successfully processed an *ADDLIB event in the DB2 for i5/OS journal that is specified in a SNDPWXJRNE refresh request for the CDC library interest list. PowerExchange writes this message to the message queue that is specified in the AS400EVENTMSGQ statement of the DBMOVER member if you include the ALWLIBRFSH=Y parameter in the AS4J CAPI_CONNECTION statement and specify an Event Identifier value in the SNDPWXJRNE command.

User Response: No response is required.

DTL3004I PowerExchange has processed delete event event_identifier.

Explanation: PowerExchange successfully processed a *DLTLIB event in the DB2 for i5/OS journal that is specified in a SNDPWXJRNE refresh request for the CDC library interest list. PowerExchange writes this message to the message queue that is specified in the AS400EVENTMSGQ statement of the DBMOVER member if you include the ALWLIBRFSH=Y parameter in the AS4J CAPI_CONNECTION statement and specify an Event Identifier value in the SNDPWXJRNE command.

User Response: No response is required.

DTL5001E File library/source_file_name not found / unavailable

Explanation: The source file that you specified in the i5/OS RTVSQLSTMT command either does not exist or is currently unavailable. The RTVSQLSTMT command cannot write the SQL statements for re-creating DB2 for i5/OS source or target objects to the file.

System Action: The command terminates.

User Response: Verify that the source file exists and that you have the required authority to use it. Then try to run the command again.

DTL5002E File library/source_file_name is NOT a source physical file

Explanation: The source file that you specified in the i5/OS RTVSQLSTMT command is not a physical file. The configured RTVSQLSTMT command can write the SQL statements for re-creating DB2 for i5/OS source or target objects only to a physical file.

System Action: The command terminates.

User Response: If the library or file name in the command is incorrect, correct it. Then try to run the command again.

DTL5003E Member source_member_name already exists in the file library/source_file_name and RPLSRCMBR(*YES) was not specified

Explanation: The source member that you specified in the i5/OS RTVSQLSTMT command already exists in the source file. The command does not replace the existing member because RPLSRCMBR(*NO) is specified in the command.

System Action: The command terminates.

User Response: In the command, either specify a different source member or specify the RPLSRCMBR(*YES) option to allow the replacement of the existing member. Then try to run the command again.

16 Chapter 1: DTL0001 to DTL5008

Page 17: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL5004E Parameter parameter_name value parameter_value is not supported for i5/OS level version

Explanation: The i5/OS RTVSQLSTMT command includes the specified parameter value but this parameter value is not supported for the i5/OS version that is installed on the server. The RTVSQLSTMT command cannot provide the SQL statements for re-creating DB2 for i5/OS source or target objects.

System Action: The command terminates.

User Response: In the command, change the value of the specified parameter to either the default value or a value that is supported by your i5/Os version. Then try to run the command again.

DTL5005E Create RCAC Statements only permitted if Activate Row & Column Access has been specified

Explanation: In the i5/OS RTVSQLSTMT command, the Create RCAC Statements (CRTMSKPRM) parameter is set to *YES. The Create RCAC Statements parameter can be set to *YES only if the Activate Row & Column Access (ACTROWCOL) parameter is also set to *YES. However, the Activate Row & Column Access parameter value is *NO.

System Action: The command terminates.

User Response: In the command, either change the CREATE RCAC Statements parameter to *NO or change the Activate Row & Column Access parameter to *YES. Then try to run the command again.

DTL5006E SRCMBR cannot be *SQLOBJ for selected SQL Object

Explanation: The Source Member (SRCMBR) parameter in the i5/OS RTVSQLSTMT command cannot be set to *SQLOBJ when the SQL Object (SQLOBJNAM) parameter in the same command specifies a name that is less than 11 characters in length and not enclosed in double quotation marks (").

System Action: The command terminates.

User Response: In the command, enter a valid SRCMBR value. Then try to run the command again.

DTL5007E Parameter parameter_name cannot be parameter_value for selected SQL Object Type type

Explanation: In the i5/OS RTVSQLSTMT command, the specified parameter value is not valid for the type of SQL object that is specified in the SQLTYPE (SQL Type) parameter. The command cannot provide the SQL statements for re-creating DB2 for i5/OS source or target objects.

System Action: The command terminates.

User Response: To determine the valid SQL object types for the specified parameter, display help information for the parameter. Then either change the specified parameter value or the SQLTYPE parameter value to provide a valid combination of parameters. When finished, try to run the command again.

DTL5008E Parameters parameter1_name and parameter2_name cannot both be specified as option

Explanation: In the i5/OS RTVSQLSTMT command, the specified parameters are both set to the same option. However, only one of these parameters can use this option in the same command.

System Action: The command terminates.

User Response: In the command, edit these parameters to specify a valid combination of parameter values. Then try to run the command again.

DTL0001 to DTL5008: i5/OS Commands 17

Page 18: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 2

DTL58001 to DTL62569This chapter includes the following topic:

• DTL58001R to DTL62569I: Batch VSAM ECCR, 18

DTL58001R to DTL62569I: Batch VSAM ECCRThis section contains messages for the VSAM batch environmental change capture routine (ECCR).

DTL58001R VCC Reply RETRY/ABEND/IGNORE.

Explanation: The batch VSAM ECCR detected a service request error, as identified in a previous error message.

System Action: The batch VSAM ECCR issues a WTOR requesting operator intervention and waits for the operator response.

User Response: Complete 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 VCC VCCDIR storage directory exceeded.

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

System Action: The batch VSAM ECCR does not anchor the storage in VCCDIR.

User Response: Contact Informatica Global Customer Support.

DTL58005I VCC length bytes [STORAGE | GETMAIN] error REG15=nnn(xx).

Explanation: The program was unable to acquire virtual storage.

In the message text:

• length is the virtual storage length.

• nnn is the macro name.

• xx is the VSAM return code.

System Action: The batch VSAM ECCR aborts the request.

User Response: For a description of the return code, see the appropriate IBM manual.

18

Page 19: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL58006I VCC length bytes address {STORAGE|FREEMAIN} error REG15=nnn(xx).

Explanation: 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: The batch VSAM ECCR aborts the request.

User Response: For a description of the return code, see the appropriate IBM manual.

DTL58007I VCC module_name not found [in ddname].

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

System Action: The batch VSAM ECCR aborts the request.

User Response: Verify that the library containing the module is included in your JOBLIB or STEPLIB concatenation. Rerun the job.

DTL58011I VCC {RESERVE|ENQ|DEQ} error RETCD=nnn(xx) QNAME=qname RNAME=rname.

Explanation: 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: The batch VSAM ECCR aborts the request.

User Response: For a description of the return code, see the appropriate IBM manual.

DTL58001R to DTL62569I: Batch VSAM ECCR 19

Page 20: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL58012I VCC ddname could not be opened for {input|output|update} REG15=nnn(xx) [ACBERFLG=nnn(xx)] [data_set].

Explanation: 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: To determine the cause of the error, use the error codes nnn(xx) and the associated IBM open error message.

DTL58013I VCC ddname could not be closed REG15=nnn(xx) [ACBERFLG=nnn(xx)] [data_set].

Explanation: 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 appears if file ddname is a VSAM file.

• data_set is the data set name.

System Action: The batch VSAM ECCR aborts the request.

User Response: Determine the error from the error codes, nnn(xx), and the associated IBM close error message.

DTL58014I VCC ddname could not be TCLOSEd REG15=nnn(xx) [ACBERFLG=nnn(xx)][data_set].

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

System Action: The batch VSAM ECCR aborts the request.

User Response: For a description of the return code, see the appropriate IBM manual.

DTL58017I VCC ddname DD name too long for CONCAT/COPIES.

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

System Action: The batch VSAM ECCR aborts the request.

20 Chapter 2: DTL58001 to DTL62569

Page 21: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Contact Informatica Global Customer Support.

DTL58018I VCC ddname maximum record length exceeded.

Explanation: The ECCR attempted to write a record that is longer than the definition of the file (ddname) accepts.

System Action: The batch VSAM ECCR aborts the request.

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

DTL58019I VCC ddname minimum record length too short.

Explanation: The ECCR attempted to write a record that is shorter than the definition of the file (ddname) will accept.

System Action: The batch VSAM ECCR aborts the request.

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

DTL58020I VCC VCCSERV csectrequestname VCCSERV+xxxxxx. Request not supported.

Explanation: An internal logic error occurred. This is an internal processing error used for debugging.

System Action: The request is aborted with an abnormal termination.

User Response: Record the contents of the error message and contact Informatica Global Customer Support.

DTL58021I VCC macro error REG15=nnn(xx) [REG0=nnn(xx)].

Explanation: An error occurred while attempting to issue the specified macro.

System Action: The batch VSAM ECCR aborts the request.

User Response: Record the return codes, nnn(xx), and see the description in the appropriate IBM manual to determine your action.

DTL58022I VCC ddname macro error REG15=nnn(xx) [REG0=nnn(xx)].

Explanation: An error occurred while attempting to issue the specified macro. This macro was issued on behalf of a file request.

System Action: The batch VSAM ECCR aborts the request.

User Response: Record the return codes, nnn(xx), and see the description in the appropriate IBM manual to determine your action.

DTL58023I VCC ddname REG15=nnn(xx) RPLERRCD=nnn(xx) message.

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

System Action: If the message is considered a warning, the request continues. Otherwise, The batch VSAM ECCR aborts the request.

DTL58001R to DTL62569I: Batch VSAM ECCR 21

Page 22: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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

DTL58024I VCC ddname physical errorSYNADAF message text.

Explanation: A QSAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is displayed.

System Action: The batch VSAM ECCR aborts the request.

User Response: See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again.

DTL58026I VCC ddname physical errorSYNADAF message text.

Explanation: A BSAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is displayed.

System Action: The batch VSAM ECCR aborts the request.

User Response: See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again.

DTL58028I VCC ddname messageSYNADAF message text.

Explanation: A BDAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is also displayed.

System Action: The batch VSAM ECCR aborts the request.

User Response: See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again.

DTL58030I VCC ddname messageSYNADAF message text.

Explanation: An ISAM physical error (SYNAD) was encountered while processing ddname. A message buffer associated with the SYNAD is also displayed.

System Action: The batch VSAM ECCR aborts the request.

User Response: See the appropriate IBM manual for a complete description of the associated error message. Restore the data set and execute the program again.

DTL58033I VCC ddname abcode abend error.

Explanation: A system abend was encountered for the data set referred to by ddname.

System Action: The batch VSAM ECCR aborts the request.

User Response: See the appropriate IBM manual for a complete description of the associated abend code.

22 Chapter 2: DTL58001 to DTL62569

Page 23: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL58034I VCC ddname physical error.

Explanation: A physical error was encountered for the data set referred to by ddname.

System Action: The batch VSAM ECCR aborts the request.

User Response: This message is accompanied by an IBM error message. See the appropriate IBM manual for a description of the associated error message.

DTL58035I VCC ddname wrong length record.

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

System Action: The batch VSAM ECCR aborts the request.

User Response: This message is accompanied by an IBM error message. See the appropriate IBM manual for a description of the associated error message.

DTL58036E VCC ddname file is not open.

Explanation: The file must be opened before your request to modify it can be processed.

System Action: The request for modification is ignored.

User Response: Verify the file is open before attempting to modify it.

DTL58037I VCC ddname file is already open.

Explanation: A request to open a file was made to a file that is already open. This is an internal processing error.

System Action: The batch VSAM ECCR aborts the request.

User Response: Contact Informatica Global Customer Support.

DTL58038I VCC ddname filename missing.

Explanation: The file identified by ddname cannot be found.

System Action: The batch VSAM ECCR aborts the request.

User Response: Contact Informatica Global Customer Support.

DTL58491I VCC VCCJCLOC error REG15=nnn(xx) TUKEY=(xxxx).

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

System Action: The text unit in error is ignored.

User Response: This is an internal processing error. Contact Informatica Global Customer Support.

DTL58492I VCC DYNALLOC PARM list length=length.

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

System Action: Processing continues.

User Response: No response is required.

DTL58001R to DTL62569I: Batch VSAM ECCR 23

Page 24: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL58493I VCC DYNALLOC text units {pointer list|area} exceeded.

Explanation: A dynamic allocation function was requested and the dynamic allocation parameter list was exceeded. This is an internal processing error.

System Action: The dynamic allocation request is aborted.

User Response: Contact Informatica Global Customer Support.

DTL58494I VCC DYNALLOC error REG15=nnn(xx).

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

System Action: The dynamic allocation request is aborted.

User Response: Contact Informatica Global Customer Support.

DTL58495I VCC DYNALLOC error‑info reason code=(xxxx‑xxxx).

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

System Action: The dynamic allocation request is aborted.

User Response: Contact Informatica Global Customer Support.

DTL58498I VCC DYNALLOC message.

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

System Action: The dynamic allocation request is aborted.

User Response: Contact Informatica Global Customer Support.

DTL58499I VCC jclstmt.

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

System Action: The dynamic allocation request is aborted.

User Response: Contact Informatica Global Customer Support.

DTL58504E VCC parmname is an unrecognized parameter.

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

System Action: Processing continues with the next request.

User Response: Contact Informatica Global Customer Support.

DTL58505E VCC Keyword parmname must be followed by a ( or =.

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

System Action: Processing continues with the next request.

24 Chapter 2: DTL58001 to DTL62569

Page 25: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Contact Informatica Global Customer Support.

DTL58513I VCC Key = key successfully {updated|added|deleted}.

Explanation: The key in the message was successfully added, deleted, or updated according to your request.

System Action: Processing continues.

User Response: No response is required.

DTL58514I VCC Key key not found ‑ could not be deleted.

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

System Action: The automatic registration process is terminated.

User Response: Contact Informatica Global Customer Support.

DTL58517E VCC Invalid subparameter length for parmname.

Explanation: The subparameter name in the message text was specified with too many characters of data. This is an internal processing error.

System Action: The requested action is bypassed.

User Response: Contact Informatica Global Customer Support.

DTL58527E VCC subparameter is an invalid subparm for parameter.

Explanation: The indicated subparameter is not valid for the parameter.

System Action: The command is rejected. Processing continues.

User Response: Correct the control statement and run the job again. For more information on controlling the VSAM ECCR, see PowerExchange CDC Guide for z/OS.

DTL58541E VCC Invalid control statement continuation.

Explanation: When a “‑” (blank, hyphen) is used in a control statement, the next record encountered must be a continuation of the control statement.

System Action: The command is rejected. Processing continues.

User Response: Check the control statement and correct the continuation record as needed, or remove the continuation character. Then, run the change capture job again.

DTL58571I VCC KEY=key successfully {added|updated|deleted}.

Explanation: The record identified by key was processed normally.

System Action: Processing continues.

User Response: No response is required.

DTL60163S VCC System error R15(return_code), R0(feedback_code).

Explanation: An environmental or other internal error occurred.

System Action: Processing ends.

User Response: Save all job output and contact Informatica Global Customer Support.

DTL58001R to DTL62569I: Batch VSAM ECCR 25

Page 26: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL60164E VCC Interface module module_name could not be loaded.

Explanation: The program module_name was specified in the VCCCOPT table but could not be loaded.

System Action: Initialization continues with the next parameter.

User Response: Contact Informatica Global Customer Support.

PWX60165I VCC VSAM CHANGE CAPTURE ACTIVE

Explanation: VSAM change capture is active.

User Response: No response is required.

DTL60166E VCC Interface module module_name disabled after failure.

Explanation: An error occurred in the program module_name.

System Action: The program module_name is disabled for the remainder of processing in the current job step. Job processing continues.

User Response: Save the job output and contact the interface vendor.

DTL60175E VCC VFL requires MVS/ESA Version 4 or above.

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

System Action: VFL initialization ends. Job processing continues.

User Response: If VFL is required, rerun the job under MVS/ESA Version 4.3 or later.

DTL60176E VCC VCCCOPT parameter=value required in down‑level MVS.

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

System Action: Job processing continues.

User Response: If VFL is required, rerun the job under MVS/ESA Version 4.3 or later.

DTL60222S VCC Internal logic error, R0(fbc) R15(rc). subsysid

Explanation: An internal logic error has been detected. The feedback code (fbc) and the return code (rc) are listed.

System Action: The job abends with a U0356 abend code.

User Response: Contact your Informatica Corporation technical support representative and provide the return code (rc).

DTL60500I VCC Journaling in effect for programdataset.

Explanation: The batch journaling feature has begun journaling changes to the indicated data set on behalf of the indicated program.

System Action: Processing continues.

User Response: No response is required.

26 Chapter 2: DTL58001 to DTL62569

Page 27: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL60501S VCC Journaling not in effect for programdataset.

Explanation: The batch journaling feature was attempting to journal changes to the indicated dataset on behalf of the indicated program and encountered an error.

System Action: The system performs one of the following actions, based on how the JRNLERR parameter of the VSAM ECCR journal control table (VCCJCT) was specified:

• 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: See the accompanying messages.

DTL60502I VCC nnnn fileid journal records were inserted by exit exit_pgm.nnnnfileid journal records were deleted by exit exit_pgm.

nnnnfileid journal records were created on dataset.

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

System Action: Processing continues.

User Response: No response is required.

DTL60503I VCC {JNL|LOG}(OPN=nnn, RDU=nnn, ADD=nnn, UPD=nnn, DEL=nnn, TOT=nnn) data_set.

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

System Action: Processing continues.

User Response: No response is required.

DTL60504I VCC Has been terminated by exit exit_routine.

Explanation: A user‑defined exit routine (exit_routine) requested that change capture processing be terminated.

System Action: VSAM ECCR processing ends.

DTL58001R to DTL62569I: Batch VSAM ECCR 27

Page 28: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Determine why the installation exit program requested the termination.

DTL60505S VCC ddname Spanned CI processing is not supported.

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

System Action: VSAM ECCR processing ends.

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

DTL60506S VCC ddname VSAM organization not supported.

Explanation: An attempt was made to capture changes from the ddname VSAM file. The VSAM file organization was not KSDS, ESDS, or RRDS.

System Action: The job continues and changes will not be captured.

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

DTL60507S VCC ddname VSAM {SHOWCB|TESTCB} error. REG0=nnn(xx).

Explanation: The VSAM ECCR received a nonzero return code when it executed the macro shown in the message.

System Action: VSAM ECCR processing ends.

User Response: Contact Informatica Global Customer Support.

DTL60508E VCC ddname DYNALLOC error xxxx‑xxxx [text].

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

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

DTL60510I VCC fileid {log|journal} buffers saved to dataset.

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

System Action: Processing continues.

User Response: No response is required. The emergency log data set should be concatenated with other journals if a backout becomes necessary.

DTL60511I VCC fileid {log|journal} buffers not saved-no before images in memory.

Explanation: No before-image records were found in memory.

System Action: Processing continues.

User Response: No response is required.

28 Chapter 2: DTL58001 to DTL62569

Page 29: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL60516S VCC Storage at address has been corrupted.

Explanation: The storage at address has been destroyed.

System Action: VSAM ECCR processing ends.

User Response: Contact Informatica Global Customer Support.

DTL60517S VCC VSAM path or base cluster component is not in the JCT for ddname=ddname.

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

System Action: Message DTL60501S follows.

User Response: Contact Informatica Global Customer Support.

DTL60566S VCC VCC0192A was not found in JOBLIB/STEPLIB.

Explanation: The VCC0192A module was not found in the JOBLIB or STEPLIB concatenation. This module is required for VSAM ECCR processing.

System Action: VSAM ECCR processing ends.

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

DTL60570S VCC SOC3 ABEND requested for moduleexitdata_set.

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

System Action: The VSAM ECCR ends with a SOC3 abend whenever a severe error is encountered.

User Response: See the accompanying messages.

DTL60571E VCC abcode ABEND encountered in module [exitdata_set].

Explanation: An abend occurred in the indicated module while the journaling program was journaling changes.

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

User Response: If the error occurred in a PowerExchange module, contact Informatica Global Customer Support.

DTL60573I VCC (PSW) xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(0-3) xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

(4-7) xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

(8-11) xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

(12-15) xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: An abend occurred.

System Action: Processing continues.

User Response: Save the information for debugging if you need to contact Informatica Global Customer Support.

DTL58001R to DTL62569I: Batch VSAM ECCR 29

Page 30: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL60579E VCC ESTAE error REG15=nnn(xx).

Explanation: An error occurred while issuing the MVS ESTAE macro.

System Action: Processing continues.

User Response: Contact Informatica Global Customer Support.

DTL60580E VCC nnnn bytes not allocated.

Explanation: Insufficient storage is available to satisfy the request for nnnn bytes.

System Action: Change capture processing ends.

User Response: Increase the region size and run the job again.

DTL60582S VCC module not available [REG15=nnn(xx)]

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

System Action: Processing ends.

User Response: Ensure that the library containing the indicated module is in the STEPLIB, JOBLIB, or the system link list. Then, run the job again. If MVS could not load the module, see the associated IBM error messages.

DTL60590R VCC Reply RETRY ABEND or IGNORE.

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

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

User Response: The console operator should reply RETRY, ABEND, or IGNORE.

DTL60598S VCC This module must run in 31 bit addressing mode.

Explanation: VCCADHK was relinked as AMODE(24) or it is being run on an MVS/370 system.

System Action: VCCADHK ends.

User Response: Make sure that VCCADHK is linked as AMODE(31) and is being run on an MVS/ESA system.

DTL60631I VCC Requested syncpoint syncid has been written to dataset.

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

System Action: Processing continues.

User Response: No response is required.

DTL60632I VCC End‑of‑task syncpoint syncid has been written to dataset.

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

30 Chapter 2: DTL58001 to DTL62569

Page 31: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing continues.

User Response: No response is required.

DTL60878E VCC Load of the installation options table, VCCCOPT, has failed.

Explanation: An attempt to load the CICS Integrity Series products installation options table, VCCCOPT, was unsuccessful.

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

User Response: Contact Informatica Global Customer Support.

DTL60879I VCC Product distribution defaults will be enforced for this execution.

Explanation: 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 is used.

System Action: The ECCR continues processing and issues a return code of 4.

User Response: This message is accompanied by one or more messages describing the reason the VSAM ECCR was unable to obtain the installation options table.

DTL60880E VCC A back level (vv.rr.mm) of the installation options table, VCCCOPT, has been loaded.

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

System Action: A return code of 4 accompanies this message.

User Response: Contact Informatica Global Customer Support.

DTL62559E VCC Invalid variable control statement. subsysid

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

System Action: Processing ends.

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

DTL62560E VCC variable is an invalid variable symbol. subsysid

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

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

DTL58001R to DTL62569I: Batch VSAM ECCR 31

Page 32: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

DTL62561E VCC Invalid variable construct - missing {“S”|“V”}. subsysid

Explanation: 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: Processing ends.

User Response: Contact Informatica Global Customer Support.

DTL62562E VCC Variable length for var_symbol was exceeded. subsysid

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

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

DTL62563E VCC Substitute length for value was exceeded. subsysid

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

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

DTL62564E VCC Invalid library name: ddname. subsysid

Explanation: The data set referenced by ddname does not exist.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

DTL62565I VCC Processing library: ddname. subsysid

Explanation: The installation job lists each DD name as it is referenced during processing.

System Action: Processing continues.

User Response: No response is required.

DTL62566I VCC Installation bypassed for: membername. subsysid

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

System Action: Processing continues.

User Response: No response is required.

DTL62567I VCC Member selected for installation is: membername. subsysid

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

System Action: Processing continues.

32 Chapter 2: DTL58001 to DTL62569

Page 33: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

DTL62568I VCC Symbol length was exceeded. subsysid

Explanation: The JCL generating job encountered a variable symbol greater than 11 characters.

System Action: Processing continues.

User Response: No response is required.

DTL62569I VCC var_symbol symbol was not found. subsysid

Explanation: The JCL generating job expected input for the variable symbol var_symbol, but did not receive it.

System Action: Processing continues.

User Response: No response is required.

DTL58001R to DTL62569I: Batch VSAM ECCR 33

Page 34: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 3

PWXEDM172000 to PWXEDM173002

This chapter includes the following topics:

• PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent, 34

• PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger, 74

• PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC), 132

• PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger, 146

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.

System Action: Processing continues.

User Response: Contact Informatica Global Customer Support.

PWXEDM172001I module: EDM Agent. Version v.rr.mm.

Explanation: The PowerExchange Agent issues this message during initialization to supply the following information:

• Version number (v)

• Release number (rr)

• Modification number (mm)

System Action: Processing continues.

User Response: No response is required.

34

Page 35: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172002I module: ChangeDataMove. Version v.rr.mm. Release date: date

Explanation: 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: Processing continues.

User Response: No response is required.

PWXEDM172003I module: Processing terminated, Return code=rc.

Explanation: The PowerExchange Agent ended processing with a return code of rc.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172004E module: EDM Agent must run as an MVS started-task

Explanation: You tried to run the PowerExchange Agent in a batch or TSO address space.

System Action: The PowerExchange Agent ends.

User Response: Run the PowerExchange Agent as an MVS started task.

PWXEDM172005E module: TESTAUTH failed. program must execute with APF authorization

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

System Action: The PowerExchange Agent ends.

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

PWXEDM172006E module: OPEN of ddname file failed

Explanation: PowerExchange cannot open the file with the DD name ddname. Processing of file ddname ends.

System Action: If the ddname is EDMSCTL, the PowerExchange Agent ends.

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

PWXEDM172007E module: The ddname file has an invalid format

Explanation: The PowerExchange Agent startup parameter data set with DD name ddname has an invalid data set format and cannot be processed.

System Action: The PowerExchange Agent ends.

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

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 35

Page 36: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172008I module: actionddname file

Explanation: The PowerExchange Agent control file is about to be processed or has been processed as shown by action.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172009E module: An error was found in the ddname file:

Explanation: PowerExchange found an error in the PowerExchange Agent startup parameter data set (control file). Subsequent messages describe the error.

System Action: The PowerExchange Agent ends.

User Response: Determine the cause of the error, edit the PowerExchange Agent startup parameter data set (control file), and restart the PowerExchange Agent.

PWXEDM172010n module: text

Explanation: This message provides additional information related to the previously displayed message or messages. The message suffix is I, W, or E.

System Action: Processing continues.

User Response: The response depends on the message text and content of related messages.

PWXEDM172011E module: The default operand for the keyword keyword is invalid

Explanation: A default operand for the specified keyword is invalid. This is an internal program error.

System Action: The PowerExchange Agent ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172012E module: A logic error has been detected

Explanation: An unrecoverable internal program error has been detected.

System Action: The currently active task abends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172013E module: LOAD Failed. Module=module_name, Code=abend_code, Reason=reason

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

System Action: The PowerExchange Agent ends.

User Response: Verify that all required load libraries are included in the PowerExchange Agent STEPLIB or JOBLIB concatenation, and start the PowerExchange Agent again.

PWXEDM172014I module: Reason: explanation

Explanation: This message further explains an error found in the PowerExchange Agent startup parameter data set (control file).

System Action: Processing continues.

36 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 37: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Determine the cause of the error, edit the PowerExchange Agent startup parameter data set (control file), and restart the PowerExchange Agent.

PWXEDM172015E module: GETMAIN failed for initialization control block

Explanation: The PowerExchange Agent could not get the storage required for its initialization processing.

System Action: The PowerExchange Agent ends.

User Response: Increase the region size, and restart the PowerExchange Agent.

PWXEDM172016E module: A valid JOBLIB or STEPLIB DCB could not be found.

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

System Action: The PowerExchange Agent ends.

User Response: Create a valid JOBLIB or STEPLIB concatenation. Then, run the job again.

PWXEDM172017I module: VSAM ECCR support not installed by a prior CCVActive=YES keyword, - command rejected

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

System Action: Processing continues without the VSAM ECCR.

User Response: Specify the CCVActive=YES keyword for the PowerExchange Agent configuration parameters, and restart the PowerExchange Agent.

PWXEDM172018I module: VSAM ECCR status

Explanation: This message signals the installation or refresh of the VSAM ECCR.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172019E module: Another EDM Agent is running with AgentID agentid

Explanation: The PowerExchange Agent that is currently initializing detected another PowerExchange Agent already running that has the same agentid.

System Action: The PowerExchange product stops processing the currently initializing PowerExchange Agent.

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

PWXEDM172020E module: Existing SSCVT agentid was not built by an EDM Agent and cannot be used.

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

System Action: The PowerExchange Agent ends.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 37

Page 38: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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

PWXEDM172021E module: STORAGE OBTAIN failed for SubPool subpool. EDM Agent agentid cannot be initialized

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

System Action: The PowerExchange Agent ends.

User Response: Restart the PowerExchange Agent when CSA or ECSA storage is available.

PWXEDM172022E module: EDM Agent agentid appears to be active and cannot be initialized

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

System Action: The PowerExchange Agent ends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172023I module: Active=total1_modules, Inactive=total2_modules

Explanation: This message shows the number of active and inactive CCV0192A modules found on the LPAQ.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172024I module: New control_block built for EDM Agent agentid. Addr=address

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172025E module: STORAGE OBTAIN failed for work_area

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

System Action: The PowerExchange Agent ends.

User Response: Restart the PowerExchange Agent when ECSA storage is available.

PWXEDM172026E module: EPA for generic ESTAEX/ARR module has not been established

Explanation: The PowerExchange Agent could not determine the address of its generic ESTAE-type recovery routine. This condition indicates that an internal logic error occurred.

System Action: The PowerExchange Agent ends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

38 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 39: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172027E module: ESTAEX failed. Return Code=rc, Reason=reason

Explanation: The PowerExchange Agent could not establish an ESTAE-type environment because the ESTAEX macro failed. The macro provides the return and reason codes shown.

System Action: The PowerExchange Agent ends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172028E module: LOAD of module module resolved to the LPA

Explanation: During its initialization, the PowerExchange Agent attempted to load a module, but it does not reside in a JOBLIB or STEPLIB concatenation.

System Action: The PowerExchange Agent ends.

User Response: Verify that the required module is in a JOBLIB or STEPLIB concatenation, and start the PowerExchange Agent again.

PWXEDM172029E module: STORAGE OBTAIN failed for recovery work area

Explanation: Storage could not be obtained for a PowerExchange Agent recovery work area.

System Action: The PowerExchange Agent ends.

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

PWXEDM172030E module: ESTAEX/ARR invoked for ABEND code=abend, Reason=reason, PSW=psw

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

System Action: The abend processing continues.

User Response: Determine the cause of the abend or contact Informatica Global Customer Support.

PWXEDM172031I module: register_typestart_register–end_registerregisterregisterregisterregister

Explanation: 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: Processing continues.

User Response: No response is required.

PWXEDM172032E module: STORAGE OBTAIN failed for persistent module module_name

Explanation: Storage could not be obtained for globally loading the module_name module. This indicates a severe shortage of CSA, ECSA, SQA, or ESQA.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 39

Page 40: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Agent ends.

User Response: Restart the PowerExchange Agent when storage is available.

PWXEDM172033W module: PMP deleted. Module=module_name, Addr=address

Explanation: The persistent module module_name has been removed from common storage. The variable address indicates the address of the prefix area.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172034E module: No room in agentid SSVT function list for persistent module module

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

System Action: The PowerExchange Agent ends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172035E module: STORAGE OBTAIN failed for CDE/XTLST area for persistent module module

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

System Action: The PowerExchange Agent ends.

User Response: Restart the PowerExchange Agent when more SQA storage is available.

PWXEDM172036E module: Architectural incompatibility detected. Old version=(oldarch/oldver), New version=(newarch/newver)

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

System Action: The PowerExchange Agent ends.

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

PWXEDM172037E module: EDMSINIT request rejected. EDM Agent agentid is status

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

40 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 41: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Agent rejects the EDMSINIT call. The function that issued the request might also fail.

User Response: Issue a RESUME command to allow EDMSINIT calls, if necessary.

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

• n is the message suffix and is one of the following values:

- 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 response is required.

• E. Drain the PowerExchange Agent and reissue the SHUTDOWN COMPLETELY command.

PWXEDM172039I module: The following JES2 Initiators must be drained before EDM Agent agentid can drain:

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

System Action: The PowerExchange Agent remains in draining status.

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

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 41

Page 42: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172040E module: A command command is currently pending

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

System Action: Processing ends.

User Response: Reissue the correct command or wait for the pending command to time-out, then reissue the command.

PWXEDM172041E module: STORAGE OBTAIN failed for VSAM OPEN/CLOSE intercept CDE/XTLST area. Subpool=subpool

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

System Action: Additional messages may be issued indicating the impact of this condition. Functions that depend on the CDE or XTLST area are unavailable.

User Response: Restart the PowerExchange Agent when more common storage is available.

PWXEDM172042E module: Unsupported MVS release. MVS SP4.3.0 or higher is required for execution

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

System Action: The PowerExchange Agent ends.

User Response: Upgrade to a compatible version of MVS.

PWXEDM172043I module: Data at PSW address - word1word2word3word4word5word6

Explanation: This message provides additional information about an abend. The word fields contain 24 bytes of data from the abend program status word (PSW).

System Action: The abend processing continues.

User Response: Use the information in this message and any related messages to determine the reason for the abend. Contact Informatica Global Customer Support.

PWXEDM172044I module: Refresh SSCVT for AgentId agent_ID ignored. Addr=address

Explanation: This message can display during a cold or warm start.

System Action: If the existing MVS SSCVT for the PowerExchange Agent is

• Not in error—the PowerExchange Agent proceeds with the normal startup request, using the existing SSCVT to continue processing.

• In error—and the PowerExchange Agent SSCVT does not match the refresh SSCVT statement in the EDMSCTRL module, the PowerExchange Agent startup process ends with message PWXEDM172020.

42 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 43: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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 module: External {activation|deactivation} of VSAM Batch ECCR detected by Agent agent_ID

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

System Action: Processing continues.

User Response: If the change in the VSAM batch ECCR is acceptable, no response is required. If you wish to change the status, issue the STOP or START command for the PowerExchange Agent with the appropriate VSAMECCR operand.

PWXEDM172046E module: Sysplex Message Log operation failed. Code=return_code, Rsn=reason_code

Explanation: A module encountered an error while attempting to perform an operation using the PowerExchange sysplex message log.

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.

User Response: Contact Informatica Global Customer Support.

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.

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

PWXEDM172048E module: MVS Logger Connect failed for stream name stream_name, Code=return_code, Rsn=reason_code

Explanation: A module encountered an error while attempting to perform a MVS logger operation using the PowerExchange sysplex message log.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 43

Page 44: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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.

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

PWXEDM172050E module: agentid Command Exit. Command buffer could not be found

Explanation: The PowerExchange Agent agentid attempted to process an operator command but could not find the command buffer. This indicates an internal program error.

System Action: The PowerExchange Agent ends command processing.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172051E module: agentidfunction_name Exit. STORAGE OBTAIN failed for work area

Explanation: Storage could not be obtained for processing the subsystem exit function function_name for the PowerExchange Agent agentid.

System Action: Processing of the exit ends.

User Response: No response is required.

PWXEDM172052I module: agentid Command Exit. command command has been queued for execution

Explanation: The PowerExchange Agent agentid accepted the command and placed it in the command buffer for subsequent processing.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172053E module: agentidfunction Exit ABENDed. Code=abend_code, Reason=reason,PSW=psw

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

System Action: Subsystem exit processing ends. Also, the function that requested the service may fail.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

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.

System Action: The PowerExchange Agent rejects the specified command.

User Response: Start the specified PowerExchange Agent, and enter the command again.

44 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 45: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172055W module: agentid Command Exit. Null command ignored

Explanation: The PowerExchange Agent agentid detected a command that has no text following the command prefix.

System Action: The PowerExchange Agent rejects the command.

User Response: Enter the command again.

PWXEDM172056E module: agentid Command Exit. 'command' is not a valid EDM Agent command

Explanation: The PowerExchange Agent agentid detected an invalid command.

System Action: The PowerExchange Agent rejects the specified command.

User Response: Enter the command again.

PWXEDM172057E module: agentid Command Exit. command command has too {many|few} operands. {minimum|maximum} operand count is n

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

System Action: The PowerExchange Agent rejects the specified command.

User Response: Enter the command again.

PWXEDM172058E module: agentid Command Exit. command command rejected – insufficient buffer space

Explanation: The PowerExchange Agent agentid accepted a valid command. However, the command buffer did not have enough space for the command to be queued.

System Action: The PowerExchange Agent rejects the specified command.

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

PWXEDM172059E module: SRB failed. Function=function, Return Code=rc

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

System Action: Depending on the error, the PowerExchange Agent may terminate, also.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172060I module: {Code=abend_code|Return Code=rc}, {Reason=reason|Date=text} psw

Explanation: 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: The SRB function ends. Based on the error, the PowerExchange Agent might stop.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 45

Page 46: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172061E module: {AXSET|AXRES|ATSET} failed. Code=abend_code, Reason=reason

Explanation: The specified AXSET, AXRES, or ATSET macro abended. abend_code and reason provide additional information about the abend.

System Action: The PowerExchange Agent ends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172062I module: agentidfunction Exit status

Explanation: The subsystem exit specified by function has been entered or exited for the PowerExchange Agent identified in agentid.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172063E module: STORAGE OBTAIN failed for SRB control block

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

System Action: The PowerExchange Agent ends.

User Response: Start the PowerExchange Agent again when SQA and ESQA are available.

PWXEDM172064I module: Dataspace status. Name=name, STOKEN=stoken, Blocks=blocks

Explanation: 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: Processing continues.

User Response: No response is required.

PWXEDM172065E module: RACROUTE AUTH failed. SAF Return Code=safrc, Return Code=rc, Reason=reason

Explanation: 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: The system rejects the registration request.

46 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 47: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: 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). For information about the PowerExchange Agent control statements, see the PowerExchange CDC Guide for z/OS.

PWXEDM172066E module: agentid PC routine ABENDed. CSECT=csect, Code=abend_code, Reason=reason, PSW=psw

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

System Action: The PC function ends. Based on the error, the function that issued the request might fail.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172067E module: ATTACHX failed. Module=module,Return Code=rc

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

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

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172068E module: STORAGE OBTAIN failed for Subtask control blocks

Explanation: The PowerExchange Agent could not get storage for the PowerExchange Agent subtask work areas.

System Action: The PowerExchange Agent ends.

User Response: Increase the region size, and start the PowerExchange Agent again.

PWXEDM 172069 [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.

System Action: Processing continues.

User Response: No response is required. For more information about the return code, see the appropriate IBM assembler services documentation.

PWXEDM172070E module: Subtask ABENDed. Module=load_module, TaskID=taskid, Code=abend_code

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

System Action: The subtask ends.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 47

Page 48: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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

PWXEDM172071I module: Subtask initialization completed. TaskID=taskid

Explanation: The PowerExchange Agent subtask taskid initialized.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172072I module: Log file ddname &OPENED. LogClass=class, LogLimit=limit, LogHold={Yes|No}

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172073E module: DYNALLOC failed. DD Name=ddname, Return Code=rc, Error code=error, Info code=info

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

System Action: The dynamic allocation fails. The function that issued the dynamic allocation request may fail also.

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

PWXEDM172074E module: STORAGE OBTAIN failed for storage location 16Mb

Explanation: A request for storage above or below 16 MB, as shown in location, failed.

System Action: The function that requested the storage may fail.

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

PWXEDM172075E module: EDM Agent tasktype ABENDed. TaskID=taskid Code=abend_code, Reason=reason, PSW=psw

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

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

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

48 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 49: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172076I module: ddname file CLOSED

Explanation: The file specified by ddname is closed.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172077I module: Repeat command command for EDM Agent agentid within 15 seconds to confirm request

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

System Action: Processing continues.

User Response: Enter the specified command within 15 seconds to confirm the request, or ignore the message to cancel the command.

PWXEDM 172078 [I|W]

module: command_name command status by PowerExchange Agent agentid

Explanation: The PowerExchange Agent agentid accepted or rejected the specified command.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172079E module: agentid Command Exit. command command takes no operands

Explanation: The specified command has no operands. However, the PowerExchange Agent agentid received the command with one or more operands.

System Action: The PowerExchange Agent rejects the command.

User Response: Enter the command without operands.

PWXEDM172080E module: agentid Command Exit. command command RACROUTE AUTH failed. SAF Return Code=safrc,Return Code=rc,Reason=reason

Explanation: 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: The PowerExchange Agent rejects the command.

User Response: 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). For information about the PowerExchange Agent control statements, see the PowerExchange CDC Guide for z/OS.

PWXEDM172081E module: EDMSINIT failed. Return Code=rc,Reason=reason

Explanation: A request to register for PowerExchange Agent services failed. The return code rc and the reason code reason provide additional information about the error.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 49

Page 50: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Agent rejects the registration request. The function that requested registration may fail, also.

User Response: Use the information supplied in this message to determine the cause of the problem, correct the problem, and run the job again.

If you cannot determine the cause of the problem, contact Informatica Global Customer Support.

PWXEDM172082E module: command command could not be processed by PowerExchange Agent agentid

Explanation: The PowerExchange Agent could not process the specified command because the subtask that processes the command is not active.

System Action: Processing of the command ends.

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

PWXEDM172083I module: The fileid is {open|close}

Explanation: You issued a command to open or close the file specified in fileid. However, the file is already open or closed.

System Action: The PowerExchange Agent rejects the request.

User Response: Verify that the command is valid, and issue it again, if needed.

PWXEDM172084I module: SUBSYS data set {opened|closed}. DD Name=ddname, DSN=dsname

Explanation: The operation to open or close the SUBSYS data set identified by ddname and dsname completed.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172085E EDMSPCR1: SUBSYS dataset DYNALLOC failed DSN=dsn, RC=nn, Err=nnnn, Info=nnnn

Explanation: 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=nn, Err=nnnn, and Info=nnnn respectively.

System Action: The dynamic allocation fails and the function that issued the request may also fail.

User Response: If the cause of the error cannot be determined, contact Informatica Global Customer Support.

PWXEDM172086E module: agentidfunction Exit error. See Syslog and/or EDM Agent log for details

Explanation: A SUBSYS data set allocation request failed. Either the PowerExchange Agent subsystem or the allocation exit (as specified in function) issued the request.

System Action: The system writes the messages describing the error to the SYSLOG message log, the PowerExchange Agent message log, or both. The allocation request fails.

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

50 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 51: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172087I module: agentid Allocation Exit status for {batch|dynamic} allocation

Explanation: The PowerExchange Agent agentid subsystem allocation exit has been entered or exited, as shown in status, for either batch or dynamic allocation.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172088W module: The JES SAST could not be found and/or updated. SUBSYS data set I/O may be unavailable

Explanation: The JES subsystem allocation sequence table (SAST) either could not be found or could not be safely updated. This is an internal error.

System Action: The PowerExchange Agent continues processing. However, the functions that require SUBSYS I/O fail.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172089E module: command command has an invalid operand – operand

Explanation: The specified command contains the specified invalid operand.

System Action: The processing of the command ends.

User Response: Enter the command again with valid operands.

PWXEDM172090I module: Agent Trace is {on|off}

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172091E module: Required SUBSYS keyword 'keyword' was not found

Explanation: A SUBSYS allocation request specified a parameter list that did not contain the required keyword, identified by keyword.

System Action: The PowerExchange Agent rejects the allocation request.

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

PWXEDM172092I module: function Exit processing SUBSYS data set. DD Name=ddname

Explanation: 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: Processing continues.

User Response: No response is required.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 51

Page 52: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172093E module: SUBSYS data set parm 'parameter' error_text

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

System Action: The PowerExchange Agent rejects the allocation request.

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

PWXEDM172094E module: agentid SUBSYS data set allocation failed. See Syslog and/or Agent log for details

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

System Action: The PowerExchange Agent does not process the allocation request.

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

PWXEDM172095E module: Data set name required for allocation of SUBSYS data set. DD name=ddname

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

System Action: The PowerExchange Agent does not process the allocation request.

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

PWXEDM172096E module: EDMSSSIO function failed. DD name=ddname, RC=return_code, Reason=reason

Explanation: An EDMSSSIO macro, which manages SUBSYS I/O work areas, failed. The variable function identifies the failing operation.

System Action: The function that issued the EDMSSSIO macro might fail.

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

PWXEDM172097I module: [successful | unsuccessful | duplicate] EDMSINIT performed for TCB tcb_address. Return Code=rc, Reason=reason

Explanation: The EDMSINIT macro completed a successful, unsuccessful, or duplicate PowerExchange Agent registration call with the return code rc and reason code reason.

System Action: If the call failed, the function that issued the macro might also fail. If the call was successful, processing continues.

52 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 53: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: If the call was successful, no response 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.

PWXEDM172098I module: Agent control_block {obtained|released}. Addr=address

Explanation: The system either obtained or released the specified control block at the specified address.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172099I module: Passing control to SUBSYS data set function module module

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM 172100 [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.

System Action: If the return code or reason code indicates an error, the function that called the specified module might end.

User Response: If the return code and reason code do not indicate an error, no response 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.

If the error is an assembler language error, see the appropriate IBM assembler services documentation for information on the return and reason codes.

PWXEDM172101E module: agentidfunction_name Exit could not find EDSSIOW area for DD name ddname

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

System Action: Subsystem exit processing ends. Also, the function that requested the service might fail.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172102E module: agentidfunction_name Exit could not find module module_name specified in JCL/DYNALLOC SUBSYS parameters

Explanation: The subsystem exit function function_name could not find a module specified in the DYNALLOC or JCL DD SUBSYS parameters.

System Action: The PowerExchange Agent does not process the allocation request.

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

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 53

Page 54: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172103E module: Duplicate SUBSYS function request. DD Name=ddname, DSN=dsname

Explanation: The system issued a duplicate allocation or open request for the SUBSYS data set identified by ddname and dsname.

System Action: The request fails. Also, the function that issued the request might fail.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172104E module: Module module ABENDed. Code=abend_code, Reason=reason, PSW=psw

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

System Action: The function that called the module might end.

User Response: Use the abend code, reason code and PSW to determine the cause of the error, 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.

PWXEDM172105E module: STIMERM failed. Return Code=rc

Explanation: A STIMERM macro failed and returned the return code rc.

System Action: The function that issued the STIMERM macro might fail.

User Response: 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 persists, collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172106E module: macro function failed. Return Code=rc, Reason=reason

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

System Action: The macro that made the request might fail.

User Response: Use the return, function, and reason codes to determine the cause of the error, correct the cause, and run the job again.

PWXEDM172107I module: EDM Agent Global Queue function_name. DSN=dsname, tokentype=token

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172108E module: No DD suffix for allocation. DSN=dsname

Explanation: All available DD name suffixes used for generating SUBSYS DD names are in use. The system cannot complete the DYNALLOC for the SUBSYS data set identified by dsname.

54 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 55: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The allocation request fails. Also, the function that issued the request might fail.

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

PWXEDM172109E module: {open|close} failed for SUBSYS data set. DD Name=ddname, Return Code=rc, ACBERFLG=acb_error

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

System Action: The function that issued the request might fail.

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

PWXEDM172110I module: SUBSYS data set {opened|closed}. DD Name=ddname, LRecl=record_length, BlkSize=block_size

Explanation: The SUBSYS data set associated with the specified DD name was opened or closed. This message provides the logical record length and block size.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172111E module: The Global Service module table is full. Service module load_module could not be LOADed

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

System Action: The PowerExchange Agent ends.

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

PWXEDM172112I module: Subtask status. Module=load_module, TaskID=taskid

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172113E module: The taskid Subtask is status

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

System Action: The PowerExchange Agent rejects the START or STOP command.

User Response: Enter the correct command, if it is required.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 55

Page 56: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172114I module: Address space created. ASCB=ascb, STOKEN=stoken

Explanation: The system created an address space with the specified ASCB address and STOKEN.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172115E module: ASCRE failed. Return Code=rc, Reason=reason

Explanation: A request to create an address space using the ASCRE macro failed, and the macro returned the return code rc and reason code reason.

System Action: The function that issued the request might fail.

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

PWXEDM172116E module: EDMRIOM function call failed. Error message follows:

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

System Action: The function that issued the request might fail.

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

PWXEDM172117E module: Invalid DSN for Global Queue request. DSN=dsname

Explanation: A global queue request failed because the data set name dsname is invalid.

System Action: The function that issued the request might fail.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM172118E module: $PDX function request failed. See Agent log for error message

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

System Action: The function that issued the macro might fail.

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

PWXEDM172119I module: Repository file OPENed. Repository DSN=dsname

Explanation: The PowerExchange Agent opened the PowerExchange repository data set dsname.

System Action: Processing continues.

User Response: No response is required.

56 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 57: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172120I module: EP Name=ep_name, EPA=ep_address, Major Name=major_name, Load Point=load_point, Length=length

Explanation: This message provides additional information about an abend condition. It displays the name and address of the program that is abending.

System Action: The abend processing continues.

User Response: Use this message and any related message to help determine the cause of the abend. For assistance, contact Informatica Global Customer Support.

PWXEDM172121E prog: SUBSYS data set dynamic deallocation failed. DD Name=ddname, RC=rc, Error code=error, Info code=info

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

System Action: The dynamic allocation fails and the function that issued the request might also fail.

User Response: Use this message and any related message to help determine the cause of the abend. Contact Informatica Global Customer Support if you need assistance.

PWXEDM172123E ALESERV ADD for status Performance Dataspace failed. RC = return_code

Explanation: An ALESERV ADD issued by the PowerExchange Agent encountered an error. The return code is shown by return_code.

System Action: The initialization process for the PowerExchange Agent ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172124E Performance Dataspace validation failed, Reason = reason_code

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

System Action: The management subtask for the performance data space ends.

This condition might exhaust the space in the dataspace.

User Response: 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 COMPLETLY operand of the SHUTDOWN command, and then restarting the PowerExchange Agent.

PWXEDM172125E DSPSERV EXTEND failed for Performance Dataspace. RC = return_code. Reason = reason_code

Explanation: An attempt to enlarge the performance data space using the DSPSERV macro with the EXTEND operand failed, with the return and reason code indicated.

System Action: The management subtask for the performance data space ends. this could result in space in the dataspace becoming exhausted.

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

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 57

Page 58: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172126I DSPSERV Performance Dataspace successfully extended by blks 4K blocks

Explanation: The performance data space was becoming full and was extended by the indicated number of blocks. Each block is 4 K bytes in size.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172127W DSPSERV Performance Dataspace is not at maximum size: blks blocks

Explanation: After the extension indicated in the previous message, the performance data space is now at its maximum size.

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

User Response: No response 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.

PWXEDM172128E Error in Free Space element in Performance Dataspace, A = Address, RSN = reason_code

Explanation: An internal error was found in the free space elements maintained in the performance data space.

System Action: The erroneous free space element is removed from processing and is not eligible for reuse.

User Response: Contact Informatica Global Customer Support.

PWXEDM172129I num Free Space elements, containing numK and num bytes, successfully reclaimed

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172130E Error in Free Space queue in Performance Dataspace, RSN = reason_code

Explanation: An internal error was found in the free space queue maintained in the performance data space.

System Action: The management subtask for the performance data space ends. This could result in space in the dataspace becoming exhausted.

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

PWXEDM172132E DELETE failed. Module = mod, Return code = rc

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

58 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 59: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Agent subtask or task ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172133E Dataspace Request failed, reqname, Return code=rc, Reason = reason_code

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

System Action: The management subtask for the performance data space ends. This could result in space in the dataspace becoming exhausted.

User Response: Contact Informatica Global Customer Support.

PWXEDM172134I num Used Space elements, containing numK and num bytes, successfully purged

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172135E Attempt to unlatch POA block at address addr during recovery {was|was not} successful

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

System Action: The management subtask for the performance data space ends due to the previous abend.

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

PWXEDM172136E Creation of SCOPE=COMMON dataspace failed, check PARMLIB MAXCAD limit

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

System Action: The PowerExchange Agent ends.

User Response: To increase the limit, change the MAXCAD value in the IEASYSxx member of SYS1.PARMLIB, and re-IPL. Contact Informatica Global Customer Support.

PWXEDM172138E module: EDMSDIR contains Agent Id agent_ID, which does not match Agent name agent_name

Explanation: The PowerExchange Agent loaded the EDMSDIR load module, but the specified agent ID is not the same as the name of the PowerExchange Agent.

System Action: The PowerExchange Agent processing ends.

User Response: Verify that the PowerExchange Agent is using the correct EDMSDIR load module.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 59

Page 60: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172139I module: Existing control_block, used by Agent agent_ID. Addr=address. status

Explanation: The PowerExchange Agent found a valid MVS subsystem control block, located at the specified address.

System Action: The PowerExchange Agent processing continues. The possible values for status are:

• RECLAIM

• Use, as is.

• REFRESH

• Rebuild.

User Response: No response is required.

PWXEDM172140I module: {Duplicate Reader | Reader} log_reader_name disconnected from Log Merge task logger_ID, RC=return_code, RSN=reason

Explanation: A reader task or job disconnected from the Log Merge task. This message provides the name and type of the reader task or job, the return code, and the reason code. If the return code and reason code are zero, disconnection was normal. If the return code and reason code are non-zero values, the disconnection might be related to an error.

System Action: Processing continues

User Response: If the return code and reason code are non-zero values, look for related messages to diagnose the problem. Also look at the reader task or job output.

PWXEDM172141I module: Logger job_name has started on system SMF_ID for reader log_reader_name

Explanation: A member Logger job that is part of the Post-Log Merge process has been started on the specified system. During initialization, the Logger job signs on to the Post-Log Merge task to verify proper serialization and sequencing of the log records that are being merged from all of the member Loggers.

The message is issued once for each active log reader that will receive data merged from the member Logger. This message provides the job name of the member Logger, the SMF ID of the system on which the member Logger runs, and the name of the log reader whose status has been changed to recognize that the member Logger is now active.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172142W module: Logger job_name on system SMF_ID has terminated for reader log_reader_name - LMF will continue

Explanation: A member Logger job that is part of the Post-Log Merge process ended while processing data for the specified log reader. The Post-Log Merge task continues to merge data from that member Logger until it reaches the end of the data. The Post-Log Merge task then does not merge new data from that member Logger until the member Logger signs back on to the Post-Log Merge task. The member Logger signon will be indicated by message PWXEDM172141I.

This message is issued once for each active log reader that was receiving data merged from the member Logger. The message text includes the job name of the member Logger, the SMF ID of the system on which the member Logger ran, and the name of the log reader whose status has been changed to recognize that the member Logger is no longer active.

System Action: The Log Merge Facility (LMF) continues processing.

60 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 61: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: If the termination of the member Logger was expected, such as during a shutdown for an IPL of the system, no user action is required. If the termination was unexpected, determine the reason for the termination, correct the problem, and then try to restart the member Logger. If the problem cannot be diagnosed, or if the member Logger cannot be restarted, contact Informatica Global Customer Support.

PWXEDM172143E module: LMF merging data from an invalid environment

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

System Action: Processing stops.

User Response: Remove the ERDSs that are not to be merged or run the PowerExchange Logger on the correct system.

PWXEDM172144E module: Invalid JCL PARM value value for {Log Merge | Log Scan/Print Utility} task

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

System Action: The Log Merge or Log Scan/Print task ends.

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

PWXEDM172145E module: LMF is using LOGRGRP but the UOW sequence number used is not a timestamp

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

System Action: Processing stops.

User Response: Verify that the PowerExchange Loggers that are being merged have a value of ''Y” for “all” specified in the LOGRGRP parameter in the EDMSDIR.

PWXEDM172146I module: Processing dataset_name for {Scan/Print|Reader log_reader_name}

Explanation: The Log Merge Facility (LMF) is processing the specified log data set for the PowerExchange Log Scan and Print utility or a log reader.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 61

Page 62: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172147E module: LMF has encountered an error with function function RC=return_code

Explanation: The Log Merge Facility (LMF) encountered an error during a log process function invoked by the DSPSERV, DIV, HSPSERV, DYNAMIC ALLOCATION, DYNAMIC REALLOCATION, or OPEN macro. In the message text, function represents one of the following values:

• UNMAP

• UNACCESS

• UNIDENTIFY

• RELEASE

• DELETE

• DEALLOCATE

• GENCB

• OPEN

• SHOWCB

• CLOSE

• CREATE

• IDENTIFY

• ACCESS

• MAP

• RESET

• SREAD

• OPEN

• MODCB

• GETRPL

• POINT

System Action: Processing ends.

User Response: Gather information about the failure and then contact Informatica Global Customer Support.

PWXEDM172148E module: Error was encountered opening the archive log dataset. RC=return_code

Explanation: The program module encountered an error while opening an archive log data set. This message provides the return code for the error.

System Action: Processing ends.

User Response: Gather all available information about the error. Then contact Informatica Global Customer Support.

PWXEDM172149E module: End of file has been reached on the allocated log. This should not occur

Explanation: The program has reached EOF on an archive data set, this should not occur.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172150E module: Dynamic allocation error has occurred RC=return_code

Explanation: An error was detected during dynamic allocation of an active or archive log data set.

62 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 63: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing ends.

User Response: Check to see if the data set was allocated to another job and if the data set still exists.

PWXEDM172151I module: Log merge will use {XCF|the MVS LOGGER} for data transmission.

Explanation: This message describes the mode of transmission for the log merge.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172152E module: Global function failed RC=X"return_code"

Explanation: The issuing program called a service or function that returned a non-zero return code. In the message text, function represents one of the following values: 

• 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: Processing ends.

User Response: To diagnose the error, review the previous error messages. Then contact Informatica Global Customer Support.

PWXEDM172153E module: The EDM Logger is not available.

Explanation: An error was detected in EDMLSND1. The PowerExchange Logger is not up and executing.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 63

Page 64: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172154E Error initializing common services.

Explanation: An error was detected in EDMLSND1.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172155E Agent is not active

Explanation: An error was detected in EDMLSND1.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172156E Error in common services connect.

Explanation: An error was detected in EDMLSND1.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172157E EDMLSND3 could not be loaded.

Explanation: An error was detected in EDMLSND1. The module could not be loaded.

System Action: Processing ends.

User Response: Find out why the module did not load. Verify that the module is not missing and there is not a storage problem.

PWXEDM172158I module: Sender is ready for processing

Explanation: This is an informational message notifying you that the sender is ready for processing.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172159E module: Inconsistent response from reader-XCF

Explanation: The Log Merge Facility (LMF) control module expected a read response from the log reader but did not get it.

System Action: The Logger job will terminate.

User Response: Restart the job, or contact Informatica Global Customer Support.

PWXEDM172160E module: Getmain failed at initialization. RC=X"return_code"

Explanation: A GETMAIN request failed because of insufficient virtual storage.

System Action: Processing ends.

User Response: Increase the REGION size.

PWXEDM172161I module: Receiver is ready for processing.

Explanation: This is an informational message notifying you that the receiver is up and ready for processing.

System Action: Processing continues.

64 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 65: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM172162E module: Critical error -- receiver table is full.

Explanation: The receiver table is full and cannot accept more data.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172163I module: Sender has been restarted, a possible loss of data has occurred.

Explanation: Informational message records were left in the receiver at the restart of the sender. The restart cannot be validated.

System Action: Processing continues.

User Response: Verify records that are in question.

PWXEDM172164E module: The receiver has encountered a buffer full condition.

Explanation: Buffer space has been exhausted and records cannot be processed.

System Action: The system will retry for buffers later.

User Response: No response is required.

PWXEDM172165E The receiver is not available.

Explanation: The receiver was not available at the time the sender was started.

System Action: Processing ends.

User Response: Start the receiver on the appropriate system.

PWXEDM172166E module: Reader must be on the same MVS image as LMF

Explanation: The log reader must run on the same z/OS image as the Log Merge Facility (LMF).

System Action: Processing ends.

User Response: Start the log reader job on the same z/OS image as the LMF.

PWXEDM172167E module: Reader with the same name is already active

Explanation: A log reader of the same name is already active for Post Log Merge processing.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM172168E module: Reader rrrrrrrr terminating abnormally: reason

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

System Action: The Log Reader subtask will terminate, and the corresponding Log Reader job will also terminate.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 65

Page 66: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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

PWXEDM172169I module: QUIT has been issued the sender is terminating

Explanation: This informational message indicates that the pre‑log merge sender task is ending due to a user request.

System Action: The pre-log merge sender task ends.

User Response: No response is required.

PWXEDM172170I module: Receiver -- operator reply

Explanation: The receiver was not available at the time the sender was started.

System Action: Processing ends.

User Response: Start the receiver on the appropriate system.

PWXEDM172171I module: QUIT has been issued the receiver is terminating

Explanation: This informational message indicates that the pre‑log merge receiver task is ending due to a user request.

System Action: The pre-log merge receiver task ends.

User Response: No response is required.

PWXEDM172172I module: Sender has signed on to the EDM Logger

Explanation: The sender has communicated through XCF to the PowerExchange Logger.

System Action: Processing ends.

User Response: Start the receiver on the appropriate system.

PWXEDM172173I module: Sender has signed on to the EDM receiver

Explanation: The sender talked to the receiver.

System Action: Processing ends.

User Response: Start the receiver on the appropriates system.

PWXEDM172174E module: Sender is terminating due to a critical write error

Explanation: The sender is ending. A critical error has occurred which will result in data loss.

System Action: Processing ends.

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

System Action: Processing continues after warning.

User Response: An external timer must be running to insure time integrity.

66 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 67: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172176I module: Receiver has signed on to the EDM Logger

Explanation: The receiver has started communication with the PowerExchange Logger.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172177I module: Sender asynchronous process terminating

Explanation: The receiver has started communication with the PowerExchange Logger.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172178I module: Last record transmitted was record record_number

Explanation: This message displays the count of transmitted records from the sender. The message is displayed at termination.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172179E module: Attach failed for module module_name RC=x"return_code”

Explanation: The issuing program called a service or function that returned a non-zero return code.

System Action: Processing ends.

User Response: Check the previous error messages and then contact Informatica Global Customer Support.

PWXEDM172180I module: System system_ID on record record_number at store clock time

Explanation: This informational message displays the last record received by the receiver. The message is displayed at termination.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172181I module: Next record to be processed from system system_ID is record_number. There are no records queued.

Explanation: This informational message displays records queued by system in the receiver. The message is displayed at termination.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172182I module: No records have been processed since start-up.

Explanation: This informational message states that no records have been processed since start-up.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 67

Page 68: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172183E module: Log Reader log_reader_name has sent a “type” request but no signon entry is present in LMF

Explanation: 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: The request is ignored. This may lead to the job or task that sent the request being in a permanent wait.

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

PWXEDM172184I module: The receiver is not communicating sender waiting

Explanation: The sender was in the act of transmitting and received an inactive condition from the receiver.

System Action: The job waits for the restart of the receiver to attempt recovery.

User Response: No response is required.

PWXEDM172186I The receiver has started communication with the sender again

Explanation: The sender was waiting for a reset from the receiver. The reset was received and transmission starts again.

System Action: The sender starts transmission again.

User Response: No response is required.

PWXEDM172187E module: The EDM Logger has terminated. The receiver is waiting to restart.

Explanation: The receiver uses queues established by the PowerExchange Logger. If the PowerExchange Logger ends, it must be restarted so that the receiver may run.

System Action: The receiver ends.

User Response: Restart the PowerExchange Logger.

PWXEDM175188I module: System Checkpoint record record_number

Explanation: This informational message shows the last checkpoint record.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172189I module: System Reset on record record_number after the receiver restart

Explanation: This informational message shows the last reset record.

System Action: Processing continues.

User Response: No response is required.

68 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 69: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172190I module: System trace has been turned to option trace_option

Explanation: This informational message displays the trace option entered on the modify command.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172191I module: {begin | stop} data transfer for {Scan/Print | Reader log_reader_name} at log_location

Explanation: Data transfer is starting from or stopping at the specified log location for the PowerExchange Log Scan and Print utility or a log reader.

If the message specifies “Reader” followed by a reader name, the message is issued in Post-Log Merge. If the message specifies “Scan/Print,” the message is issued from the PowerExchange Log Scan and Print utility.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172192I module: LMF Tasks have stopped successfully due to operator shutdown

Explanation: This informational message notifies that the LMF system is ending due to operator request.

System Action: The job ends.

User Response: No response is required.

PWXEDM172193I EDMLCTRD: Reader xxxxxxxx has terminated [abnormally]

Explanation: The specified log reader ended abnormally. Check the output from job to find the reasons for termination.

System Action: The LMF continues the function that it was processing.

User Response: Restart the job, if necessary.

PWXEDM172194I module: LMF task for {Log Reader log_reader_name|Log Scan/Print Utility} has terminated prematurely due to an abend

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

System Action: The LMF task will terminate

User Response: Look at the output from the LMF Job, and from the corresponding Log Reader job, to determine the reason.

PWXEDM172195I module: {Scan/Print|Reader log_reader_name} terminates due to an operator STOP or reader termination

Explanation: Either the PowerExchange Log Scan and Print utility or a log reader ended because of an operator STOP command or Reader termination. The message specifies “Log Reader” followed by the log reader name if this message is issued in Post‑Log Merge. The message specifies “Scan/Print” if the message is issued from the PowerExchange Log Scan and Print utility.

System Action: The utility or reader ends.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 69

Page 70: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM172196I EDMLCTRD: Reader xxxxxxxx has requested stop transmission

Explanation: A log reader requests that post-log merge stop transmission of data.

System Action: The log reader subtask ends but other active log readers, if any, continue to function.

User Response: No response is required.

PWXEDM172197E Unable to LOAD module module_name

Explanation: The specified module could not be found in the JOBLIB/STEPLIB concatenation.

System Action: Processing ends.

User Response: Verify that all required LOAD libraries are in the JOBLIB/STEPLIB concatenation.

PWXEDM172198I module: LMF table populate tasks are terminating due to an operator stop or PAC termination

Explanation: The log read tasks that run under the Log Merge Facilitly (LMF) are ending.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172199E module: LMF timer has encountered an error RC=return_code

Explanation: The Log Merge Facility (LMF) timer macro encountered an error.

System Action: The storage region in which the macro runs ends.

User Response: Gather information about the error and then contact Informatica Global Customer Support.

PWXEDM172200I module: display_type display for EDM Agent agentid

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172201I module: No locks are currently held

Explanation: You issued a DISPLAY LOCKS command, but no PowerExchange Agent locks are currently held.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172202I module: object – ASCB=ascb_address, TCB=tcb_address

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

System Action: Processing continues.

70 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 71: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM172203I module: Job=job, Step=step, ProcStep=proc_step, JobID=jesid

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172204I module: Handle addr=handle_address, Task-related area addr=task_address

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172205I module: dsname - CQMN=token, Seq=seq_number

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172206I module: End of list

Explanation: The PowerExchange Agent issues this message at the end of all DISPLAY command output lists.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172207I module: module_name – EPA=epa, Version=version, Date=date, Time=time

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172208I PMP addr=address, Subpool=subpool, Module len=modlength, PMP len=pmplength, CDE=cde_address

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

System Action: Processing continues.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 71

Page 72: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM172209E module: Repository request failed. Return Code=rc,Reason=reason

Explanation: A request for PowerExchange repository data failed and returned the return code rc and reason code reason.

System Action: The PowerExchange repository rejects the request. Also, the calling function might fail.

User Response: Use the return code and reason code to determine the cause of the error, 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.

PWXEDM172210I module: JCL EXEC PGM=jclprogram, RB CDE Program=rbprogram, Initiator ID=initid

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172211I module: module_wait1 (ascb1/tcb1) statusmodule_hold2 (ascb2/tcb2) for lock=lockid(ecb_address/ecb)

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172212I module: module_wait (ascb/tcb) now owns lockid lock

Explanation: The specified module gained ownership of the lock designated by lockid.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172213I module: SRB POSTING module_wait(ascb/tcb) for lockid(ecb_address/ecb)

Explanation: The module holding the lock designated by lockid will post to the module that is waiting for the lock.

System Action: Processing continues.

User Response: No response is required.

72 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 73: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172214I module: agent_ID function Exit status. ASCB=ascb_address, ASID=asid, TCB=tcb_address

Explanation: 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 is zero.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172215I module: Resource Mngr status. Type=type(ecb_address), Owner=(owner_ascb/owner_tcb), Target=(target_ascb/target_tcb)

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172216I module: VSAM service SVC status. Job=job_ID, Step=step_ID

Explanation: This message provides status information about the VSAM service, including job and step identifiers.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172217I module: EDM VSAM Change Capture {deactivated|reactivated}

Explanation: This message shows the status of the VSAM change capture process for the PowerExchange Agent, when starting or stopping.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172249I module: agent_ID Clean up - operation. item=value

Explanation: The PowerExchange Agent specified in the message is performing clean-up tasks for the operation. The value field displays additional information about the operation.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172256I module: EDM Agent agent_ID has completed initialization

Explanation: The PowerExchange Agent identified in the message completed its startup procedure.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172000W to PWXEDM172257E: The PowerExchange Agent 73

Page 74: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172257E EDMSREP0: REPSTATUS operation failed, RC=rc

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

System Action: Processing continues.

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

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger

PWXEDM172502I EDM Logger initialization in‑progress with EDMLID= subsystem and product level vrmmdate

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

System Action: The PowerExchange Logger continues processing captured data.

User Response: No response is required.

PWXEDM172503E Logger Current RBA=current_RBA is less than requested RBA=requested_RBA

Explanation: The current PowerExchange Logger for z/OS writing position in the logs is before the starting relative byte address (RBA) that the log reader task requested.

System Action: The log reader task ends but Logger processing continues.

User Response: Correct the requested RBA of the log read processor (LRP).

PWXEDM172504I Log_RBA = log_RBA, Read_RBA = read_RBA, Start_RBA = start_RBA

Explanation: This message is part of the PowerExchange Logger for z/OS reader connection report. It shows the following RBA information:

• Log_RBA. The location at which the PowerExchange Logger is currently writing.

• Read_RBA. The location that the log reader last processed.

• Start_RBA. The requested starting location for the log reader.

The RBAs point to the current block but do not reflect the record that is currently being processed within that block.

System Action: PowerExchange Logger processing continues.

User Response: No response is required.

74 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 75: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172505I Logger UOW=uow_ID

Explanation: This message is part of the unit of work (UOW) report. It reports the UOW that the PowerExchange Logger for z/OS is processing.

System Action: PowerExchange Logger processing continues.

User Response: No response is required.

PWXEDM172506I logger_title logger_id shutdown in progress

Explanation: The specified PowerExchange Logger for z/OS received a stop request. This message is issued as a WTO message.

System Action: The PowerExchange Logger begins the termination process.

User Response: No response is required.

PWXEDM172507W logger_title logger_id task task_name abended abend_code - task_description

Explanation: The task identified by task task_name, which is within the PowerExchange Logger identified by logger_title logger_id, ended abnormally with the abend code abend_code. This message is issued as a WTO message.

System Action: The specified task ends abnormally.

User Response: This is an internal error. Collect all available information about the cause of the abend, and contact Informatica Global Customer Support.

PWXEDM172508I logger_title logger_id task task_name ended RC=return_code - task_description

Explanation: The specified PowerExchange Logger for z/OS subtask completed processing with the specified return code.

User Response: Use the return code to determine whether the task completed successfully. If the task did not complete successfully, collect all available information about the cause of the failure, and then contact Informatica Global Customer Support.

PWXEDM172509I logger_title logger_id shutdown complete

Explanation: The specified PowerExchange Logger for z/OS task ended. This message is issued as a WTO message.

User Response: No response is required.

PWXEDM172510W RDS is OPEN for update by another logger or JOB

Explanation: The ERDS is open and being used in update mode by another PowerExchange Logger for z/OS job or a batch update process. This message is issued as a WTO message.

System Action: The PowerExchange Logger ends abnormally.

User Response: Determine which job should be using the ERDS and then terminate the other one.

PWXEDM172511E Initialization failed: unable to load module module

Explanation: The PowerExchange Logger for z/OS was unable to load the specified module during initialization. This message is issued as a WTO message.

System Action: The PowerExchange Logger ends abnormally.

User Response: Collect all available information about the cause of the failure. Then contact Informatica Global Customer Support.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 75

Page 76: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172512I logger_titletitle initialized

Explanation: The PowerExchange Logger completed its start‑up processes and is ready for further processing. This message is issued as a WTO message.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172513E The EDMSDIR LOGRGRP parameter has been changed

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

System Action: The PowerExchange Logger ends.

User Response: Either cold start or change the LOGRGRP back to its original value.

PWXEDM172517I Sysplex Report

Explanation: This informational message presents the result of status command.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172518I Sysplex Name - sysplex_name Sysplex status - sysplex_status

Explanation: This is an informational message showing the result of status command and identifying general Sysplex information.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172519I Groupname - XCF_group_name Members Connected - -

Explanation: This informational message presents the cross-system coupling facility (XCF) group name and introduces the members in the sysplex.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172520I Jobname jobname Sysplex sysplex_name Member XCF_member

Explanation: This is an informational message showing the result of status command.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172521W Another CONSOLE is already activated, (e.g. SDSF) please deactivate

Explanation: This is a warning that another console is activated under the ISPF task.

System Action: The command is not executed until the other console is deactivated.

User Response: End the ISPF by using the console.

PWXEDM172522W System name is incorrect RC=return_code, RSN=reason_code

Explanation: An incorrect system name was used to route a command to a system in a sysplex.

System Action: The command is not executed.

76 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 77: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Use the status command to identify the systems that are in the sysplex.

PWXEDM172523I No groups related to EDM were found

Explanation: A search for PowerExchange related activity was performed and no systems were found active.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172524W ECCR_name on wrong MVS image to connect with Logger

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

System Action: The system continues ignoring input from the job.

User Response: Run the job on the system with the PowerExchange Logger or establish a log merge environment.

PWXEDM172530I TRACE ID trace_name level is number

Explanation: The trace identified by trace_name was set to the specified level.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172531I TRACE ID trace_name is off

Explanation: The trace identified by trace_name is set to level 0, which means the trace is turned off.

System Action: Processing continues. No tracing is recorded.

User Response: No response is required.

PWXEDM172532I No active TRACE IDs

Explanation: This message is issued in response to a DISPLAY TRACE command. No active traces were found.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172536I EDMLCTL statements:

Explanation: This message introduces a list of EDMLCTL control statements.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172537I edmlctl_statement

Explanation: This message displays one or more EDMLCTL control statements.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 77

Page 78: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172538I EDMLCTL statements end

Explanation: This message marks the end of the EDMLCTL control statement list.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172541E Logger running from a non‑APF authorized library, ROUTCDE=routing_code, DESC=descriptor_code

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

System Action: The PowerExchange Logger ends.

User Response: 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 Writer writer_identifier connection to Logger logger_ID deferred ‑ reason

Explanation: The PowerExchange Logger for z/OS received a signon request from an ECCR or log writer but cannot process the request immediately. The signon is deferred until the PowerExchange Logger can process it.

System Action: Processing continues.

After the PowerExchange Logger is able to process the signon request, the Logger issues message PWXEDM172668I to indicate that the signon request was processed and sends a response to the writer task.

If the signon request fails, the PowerExchange Logger issues message PWXEDM172669I. Also, this message text includes the writer identifier, the PowerExchange Logger ID, and the reason why the signon was deferred. The only reason value is “Logger quiesced.” However, the writer processing is deferred only until the PowerExchange Logger is able to process the signon request and respond to the writer.

User Response: Determine the reason for the PowerExchange Logger delay in processing the signon request.

In a Post‑Log Merge environment, one possible cause is that the PowerExchange Logger entered a quiesced state for Post‑Log Merge. The PowerExchange Logger must resume normal operations before it can allow any writers to connect to it. In this situation, see the messages related to the Post‑Log Merge task to determine why the PowerExchange Logger cannot resume normal operations.

If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

78 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 79: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172543W Logger logger_ID quiesce failed from post_log_merge_task_ID (jobname job_name on system system_name), RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS received a response to a quiesce request (QUIESCL command). The return code and reason code indicate that the quiesce request failed. The PowerExchange Logger sends the quiesce request to the Post-Log Merge task because no ECCRs are connected to the Logger for the interval that is specified in TIME_CHKPT_FREQ parameter in the PowerExchange Logger EDMUPARM options module.

This message includes the PowerExchange Logger ID, the Post-Log Merge task identifier, the name of the job under which the Post-Log Merge task runs, and the system on which the task runs. The message also includes the return code and reason code from the QUIESCL response message.

System Action: Processing continues and the PowerExchange Logger leaves the quiesced state. However, the PowerExchange Logger cannot determine the state of the Post-Log Merge address space.

User Response: Determine the reason for the error in Post-Log Merge task processing of the QUIESCL request. To diagnose the error, review messages that were issued by the Post-Log Merge task. To correct the problem, you might need to recycle either the Post-Log Merge task or the PowerExchange Logger. If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

PWXEDM172544I Logger logger_id successfully resumed logging for merging by xcf_member_name (jobname job_name on system system_name)

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

System Action: Processing continues

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 79

Page 80: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172545W Logger logger_ID resume failed from post_log_merge_task_name (jobname job_name on system system_name), RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS received a response to a resume request, but the return code and reason code indicate that the resume request failed. The PowerExchange Logger sent the resume request (RESUMEL command) to the Post-Log Merge task because some ECCRs tried to connect to the PowerExchange Logger while it was quiesced.

In this message text:

• logger_id is the name of the PowerExchange Logger.

• post_log_merge_task_name is the logical name of the Post-Log Merge task.

• job_name is the job name under which the Post-Log Merge task runs.

• system_name is the system on which the job runs.

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

User Response: No response 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 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.

80 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 81: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172547I Post‑Log Merge task xcf_member_name (jobname job_name on system system_name) [is now active | has left the system]

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

User Response: No response is required.

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:

• Command received was not request

• Command received was not reply

• Sender not Post‑Log Merge task

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.

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

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 81

Page 82: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172549W Logger logger_ID SIGNON failed to post_log_merge_task_name (jobname job_name on system system_name), RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS received a response to a signon request, but the return code and reason code indicate that the signon request failed. The PowerExchange Logger sent the signon request to the Post-Log Merge task because the PowerExchange Logger either determined during initialization that the Post-Log Merge task was active or discovered that the Post-Log Merge task had just joined the cross-system coupling facility (XCF) group.

This message includes the PowerExchange Logger ID, the task name for the Post-Log Merge task, the job name under which the Post-Log Merge task runs, and the system on which the Post-Log Merge task runs. The message also includes the return code and reason code that the PowerExchange Logger found in the SIGNON response message.

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.

User Response: Determine the reason for the PowerExchange Logger error in processing the SIGNON request. To diagnose the error, review the messages that were issued by the Post-Log Merge task. If the PowerExchange Logger cannot complete initialization because of the reported problem, you might need to restart either the Post-Log Merge task or PowerExchange Logger. If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

PWXEDM172550I number_of_eccrs Active ECCRs (Writers). Logger is currently {quiesced|not quiesced}

Explanation: This message is issued in response to a PowerExchange Logger for z/OS DISPLAY command for writer connections. It reports the number of active ECCRs that are currently connected to the PowerExchange Logger. Type 1 ECCRs that are not connected to the PowerExchange Logger are not counted, even though they are included in the Writer Connection report.

The message also reports whether the PowerExchange Logger is quiesced or not quiesced. The PowerExchange Logger can be quiesced only if it is part of a Post‑Log Merge group. In a Post‑Log Merge environment, the PowerExchange Logger informs the Post‑Log Merge task when no active ECCRs exist. This notification makes the merging of data from all of the PowerExchange Loggers by the Post‑Log Merge task faster.

System Action: Processing continues.

User Response: No response is required.

82 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 83: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172551E Logger operation_type operation for queue queue_name failed for UOW uow_ID with RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS attempted the specified operation on an internal queue. The return code indicates that the operation was not successful. When the error occurred, the PowerExchange Logger was processing a UOW record.

This message text includes the type of failed operation, the name of the internal queue, the UOW ID that the PowerExchange Logger assigned to the UOW, the return code, and the reason code. The return and reason codes are generated in EDMQMGR0 and are not currently documented.

The operation_type is one of the following values:

• Add (Phase1)

• Add (Phase2)

• Delete (UOW)

The queue_name is one of the following values:

• GBLXCFQCB

• GBLOUQQCB

System Action: The PowerExchange Logger ends abnormally.

User Response: Determine the reason for the operation failure. Use the appropriate operating system documentation. Also review any other messages that have been issued in conjunction with this problem. If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

PWXEDM172552I Logger logger_id is now quiesced ‑ Post‑Log Merge task xcf_member_name (jobname job_name on system system_name) notified

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 83

Page 84: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172553E Logger logger_ID attempt to {quiesce|resume} failed with RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS attempted to send a quiesce (QUIESCL) or resume (RESUMEL) command to the Post‑Log Merge task, but the PUT operation to the cross-system coupling facility (XCF) failed.

This message text includes the PowerExchange Logger ID, the type of command, the return code, and the reason code. The return code and reason code are generated in EDMXXCF and are not currently documented.

System Action: Processing continues.

If a quiesce command was issued, the PowerExchange Logger is not quiesced. The Post‑Log Merge task continues to merge data from this PowerExchange Logger, even if no new user data is being logged.

If a resume command was issued, the PowerExchange Logger remains in the quiesced state. ECCRs that try to connect to the PowerExchange Logger are delayed because they will not get a response to a signon request until the problem is resolved.

User Response: Determine the reason for the failure in the PUT operation. Use the appropriate operating system documentation. Also, review any other messages that have been issued in conjunction with this problem or that have been issued by the corresponding Post‑Log Merge task. To resolve the problem, you might need to restart either the Post‑Log Merge task or PowerExchange Logger. If you cannot correct the problem, contact Informatica Global Customer Support.

PWXEDM172554E Logger logger_id attempting to write to active log dataset_name at RBA rba, but is quiesced

Explanation: 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: The PowerExchange Logger ends abnormally.

User Response: 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 PowerExchange Agent, and report the problem to Informatica Global Customer Support.

PWXEDM172555E Logger current timestamp=cur_timestamp is less than requested timestamp=req_timestamp.

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

84 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 85: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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

User Response: 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 PowerExchange Logger. If you cannot correct the problem, contact Informatica Global Customer Support.

PWXEDM172557E Logger command_name command failed for logger_dataset, failure_reason

Explanation: 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 is one of the following values:

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

Logger DELETE_LOG command failed, for EDMUSR1.EDMTEST.DBML.SECLOG.DS94, dataset not found in any restart dataset

-or-

Logger DELETE_LOG command failed, for EDMUSR1.EDMTEST.DBML.SECLOG.DS04, deletion of current active log not permitted

-or-

Logger DELETE_LOG command failed, for EDMUSR1.EDMTEST.DBML.PRILOG.DS04, deletion of active log needing archival not permitted

System Action: The command processing ends.

PowerExchange Logger processing continues normally.

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

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 85

Page 86: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172558I Logger configuration parameters:

Loaded from . . . . . . . . . . . . . . : user_libraryLast update at . . . . . . . . . . . . . : timestampLast update by . . . . . . . . . . . . . : user_idDEFINELOGGER_TITLE . . . . . . . . . . . . . : logger_titleSYSTEM_OPTIONSsystem_optionsARCHIVE_OPTIONSarchive_optionsLOGGING_OPTIONSlogging_options

Explanation: This message lists the configuration parameters that were used to define the PowerExchange Logger. The message includes identifying information, such as the USERLIB, LOGGER_TITLE, and the user ID and timestamp when the logger was last updated.The message displays the following system options that were used to configure the PowerExchange Logger:

• LOGGER_NAME. The PowerExchange Logger ID.

• START_TRACE. Y or N to indicate whether the Logger trace is active. For the trace output to be received, the EDMTRACE DD statement must be in the Logger JCL.

• CHKPT_FREQUENCY. The number of log records to process before taking a checkpoint.

• TIMER_INTERVAL. Frequency of the Logger internal management operations, such as freeing unused virtual storage or detecting inactive tasks that need to be posted.

• TIME_CHKPT_FREQ. Frequency of time-based checkpoint records are created in a Post-Log Merge environment. This parameter is used only when running Post-Log Merge.

• SUFFIX. The unique suffix for a member in a Post-Log Merge group.

The message displays the following archive options that were used to configure the PowerExchange Logger:

• PREFIX_COPY1. The prefix for the first archive log data set name.

• PREFIX_COPY2. The prefix for the second archive log data set name.

• ARCHIVE_RTPD. The number of days to retain the first archive log data set.

• ARCHIVE_RTPD2. The number of days to retain the second archive log data set. This parameter is used if the interval is different than ARCHIVE_RTPD.

• ARCHIVE_UNIT. The device type or unit name of the device used to store the archive log data set.

• ARCHIVE_UNIT2. The device type or unit name of the device used to store the second archive log data set. This parameter is used if the unit is different than ARCHIVE_UNIT.

• ARC_UNIT_CNT. The number of DASD units to use for archiving.

• ARCHIVE_STCL. The SMS storage class name of the first archive log data set.

• ARCHIVE_STCL2. The SMS storage class name of the second archive log data set.

• ARCHIVE_MGCL. The SMS management class name of the first archive log data set.

• ARCHIVE_MGCL2. The SMS management class name of the second archive log data set.

• ARCHIVE_DACL. The SMS data class name of the first archive log data set..

86 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 87: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

• ARCHIVE_DACL2. The SMS data class name of the second archive log data set.

• SPACE_ALLOC. The unit type in which the primary and secondary spaces are allocated.

• PRIME_SPACE. The primary space allocation for DASD data sets in the unit type specified by SPACE_ALLOC.

• SEC_SPACE. The secondary space allocation for DASD data sets in the unit type that you specify in SPACE_ALLOC.

• ARCHIVE_BLKSIZE. The block size of the archive log data set.

The message displays the following logging options that were used to configure the PowerExchange Logger:

• LOG_INBUF. The number of 4-KB buffers used for reading the active and archive logs.

• LOG_OUTBUF. The size, in 4-KB buffers, of the output buffer that the PowerExchange Logger uses for writing the active and archive log data sets.

• ACTIVE_LOG_MODE. Whether the PowerExchange Logger writes to one (SINGLE) or two (DUAL) active log data sets at a time.

• ARCHIVE_LOG_MODE. Whether the PowerExchange Logger writes to one (SINGLE) or two (DUAL) archive log data sets at a time. The PowerExchange Logger generates archive logs when the active log is off-loaded.

• ERDS_LOG_MODE. Whether the PowerExchange Logger writes to one (SINGLE) or two (DUAL) restart data sets (ERDS) at a time.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172571I Immediate command received: command

Explanation: The PowerExchange Logger recognized command input as an immediate command.

System Action: The command runs.

User Response: No response is required.

PWXEDM172572I Input commands accepted, execution starts

Explanation: The PowerExchange Logger for z/OS read the command set from the SYSIN file for a batch job. No syntax errors were found.

System Action: The system executes the command set.

User Response: No response is required.

PWXEDM172573W command execution aborted due to syntax errors

Explanation: The command that the PowerExchange Logger for z/OS read from the SYSIN file for a batch job contained syntax errors.

System Action: The PowerExchange Logger does not run the command.

User Response: Identify and correct the syntax errors in the command set. For more information, see the more specific message that precedes this one.

PWXEDM172574W command set and/or input block flushed

Explanation: A PowerExchange Logger for z/OS command set was entered incorrectly.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 87

Page 88: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Logger does not run the command set.

User Response: Identify and correct the command error. For more information, see the more specific message that precedes this one.

PWXEDM172575E logger_command command for userid (task sequence_number) abended abend_code

Explanation: The PowerExchange Logger for z/OS command for the specified user ID ended abnormally. The message includes the Logger-assigned internal task sequence number and the abend code for troubleshooting purposes.

System Action: The subtask ends.

User Response: Collect all available information about the abend. Then contact Informatica Global Customer Support.

PWXEDM172576I logger_command command for userid (task sequence_number) complete RC=return_code

Explanation: The PowerExchange Logger for z/OS command for the specified user ID and task completed with the specified return code.

System Action: The task ends.

User Response: Use the return code and the associated message output to determine whether the command completed successfully.

PWXEDM172577I logger_command command for userid (task sequence_number) in progress

Explanation: A PowerExchange Logger for z/OS task is processing the specified command. The message includes the user ID associated with the command and task sequence number.

System Action: Processing continues.

User Response: Wait for the command to complete.

PWXEDM172578I number_of_records Change records logged, comprising number_of_UOWs UOWs. Current_RBA=rba, Current time=timestamp

Explanation: This message reports the number of records and UOWs captured during the current execution of the PowerExchange Logger for z/OS. It also reports the current relative byte address (RBA) and current time in TOD clock format, which is useful information in Post‑Log Merge environments.

System Action: PowerExchange Logger processing continues.

User Response: No response is required.

88 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 89: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172579I log_reader_name starting_sequence_number hh:mm:ss.thyyyy/dddsysplex_namefunction_name

Explanation: 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.thyyyy/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 is shown.

This message is issued once for each log reader that is connected. It is followed by multiple PWXEDM172580I messages, one for each PowerExchange Logger from which data is being merged for this log reader. The PWXEMD172579I messages are preceded by one title line to identify each of the fields that are contained in the message.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 89

Page 90: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172580I logger_jobname smf_id current_sequence_number hh:mm:ss.thyyyy/dddrbaflaglog_dataset_name

Explanation: 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.thyyyy/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 is issued once for each PowerExchange Logger from which data is being merged for the log reader. The DTLEDM172580I messages are preceded by one title line to identify each of the fields that are contained in the message.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172581W No changes were made to loggerid logger options – no keywords were found

Explanation: You entered a request to update existing options for the specified PowerExchange Logger. However, PowerExchange Change found no keywords to make those changes.

System Action: Processing continues.

User Response: Enter the correct keywords, and run the job again.

PWXEDM172582I Logger : logger_ID has been deleted

Explanation: A request to delete the specified PowerExchange Logger for z/OS instance is complete.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172585I Logger successfully built logger master control block block_name

Explanation: The PowerExchange Logger for z/OS finished building the specified Logger internal master control block.

System Action: Processing continues.

User Response: No response is required.

90 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 91: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172586I EDM Logger was unable to [connect to | disconnect from] a manager. Return code=rc, reason code=reason

Explanation: The PowerExchange Logger could not connect to or disconnect from a media manager.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172587E Logger aborted: EDMPARMS DD statement is missing

Explanation: The required EDMPARMS DD statement is not in the PowerExchange Logger for z/OS JCL.

System Action: The PowerExchange Logger address space ends abnormally.

User Response: Add an EDMPARMS DD statement to the JCL. Then run the Logger job again.

PWXEDM172588E Logger aborted: EDMZPARM module could not be loaded

Explanation: An error occurred when the PowerExchange Logger for z/OS tried to open the data set specified by the EDMPARMS DD statement and either load the EDMUOPT0 member from that data set or load the default options EDMCOPT0 member from the STEPLIB.

System Action: The PowerExchange Logger address space ends abnormally.

User Response: Enter a valid EDMPARMS DD statement in the job step. Then restart the PowerExchange Logger.

PWXEDM172589E Logger aborted: EDMPARMS DD statement is invalid

Explanation: The EDMPARMS DD statement in the PowerExchange Logger for z/OS JCL must point to a single load library. However, the DD statement is concatenated or points to a data set that is not a load library. Also, the DD data set must be allocated with the DSORG=PO and RECFM=U parameters.

System Action: The PowerExchange Logger address space ends abnormally.

User Response: Enter a valid EDMPARMS DD statement that specifies a load library name in the job step. Then restart the PowerExchange Logger.

PWXEDM172590W {Reader|Writer} identifier disconnected from logger logger_ID, RC=return_code, RSN=reason_code

Explanation: A log reader or writer tried to connect to the PowerExchange Logger for z/OS but a connection error occurred. A writer, which can be an ECCR, provides the change data to be logged. A reader reads the logged data.

The message text includes the reader or writer identifier, the PowerExchange Logger ID, and the return code and reason code for the error.

System Action: The PowerExchange Logger sends a negative response to the signon request of the reader or writer, which typically results in a failure of the reader or writer process.

User Response: To determine the reason for the failure of the signon request, review related messages and the appropriate operating system documentation. You might need to restart the log reader or change capture process if it failed as a result of the connection refusal. If you cannot correct the problem, contact Informatica Global Customer Support.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 91

Page 92: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172591I Reader identifier data transfer {starts|ends} at log_RBA

Explanation: The PowerExchange Logger for z/OS received a request from the specified log reader to either start or end transferring data at the specified log RBA. The message reports the start of data transfer when a log reader connects to the PowerExchange Logger. The message reports the end of data transfer when the log reader specifies a log location at which to stop receiving data.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172592I Reader identifier data transfer ended. number_of_records records selected, number_of_records records filtered.

Explanation: The PowerExchange Logger for z/OS completed the data transfer to the specified log reader. The message includes the number of change records that the PowerExchange Logger selected for the data transfer and the number of change records that the PowerExchange Logger filtered out. The PowerExchange Logger filters out change records based on the resource interest list of EDMNAMES from the log reader. If the log reader does not provide a resource interest list, the PowerExchange Logger does not filter change records and the message reports 0 as the number of records filtered.

The PowerExchange Logger also writes message PWXEDM172791I to the EDMMSG data set. This message indicates the number of source objects 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: Processing continues.

User Response: No response is required.

PWXEDM172593I Restart in progress using checkpoint at LogRBA=log_RBA

Explanation: This message reports the checkpoint position in the logs that the PowerExchange Logger for z/OS is using for restart processing.

System Action: The PowerExchange Logger searches for the checkpoint at the specified RBA in the log data set. Processing continues.

User Response: No response is required.

PWXEDM172594I Begin log forward restart processing at LogRBA=log_RBA

Explanation: The PowerExchange Logger for z/OS completed searching for the restart checkpoint in the current active log and will begin processing data forward from the specified log RBA.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172595I Begin recording at LogRBA=log_RBA

Explanation: The PowerExchange Logger for z/OS completed processing the current active log and will begin recording at the specified log RBA.

System Action: Processing continues.

User Response: No response is required.

92 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 93: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172596W Logger waiting for {reader|ECCR} Client (job_name) to end

Explanation: An MVS STOP (P) command was issued with the QUIESCE option to the PowerExchange Logger for z/OS. The PowerExchange Logger waits for log reader tasks to complete before beginning shutdown processing.

System Action: The PowerExchange Logger will shut down.

User Response: No response is required.

PWXEDM172597I Reader {initialized|ended} reader_ID at date time, RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS initiated or ended the specified log reader at the date and time given. The message includes the return code and reason code from this operation.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172599W DELETE=YES was specified for loggerid logger options which do not exist – request ignored

Explanation: A request was made to delete the specified options. However, the PowerExchange Logger could not find the options in the EDMZPARM module.

System Action: The PowerExchange Logger ignores the request and ends the function.

User Response: Enter the request with a valid PowerExchange Logger ID.

PWXEDM172602E Logger internal GENCB for VSAM_control_block failed with RC=return_code and RSN=reason_code for DDNAME ddname

Explanation: A PowerExchange Logger for z/OS internal VSAM GENCB operation failed and returned the specified return code in R15 and the specified reason code in R0. The VSAM_control_block value is either RPL or ACB.

System Action: If the VSAM GENCB operation ran against the JOURNAL or TRACE file, the PowerExchange Logger suspends VSAM file processing. If the GENCB operation was for a DEFINE_LOG command, the PowerExchange Logger ends the command. In other situations, the PowerExchange Logger ends.

User Response: Check the VSAM file definitions for any errors. Then run the job again.

PWXEDM172603E Logger internal VSAM macro failed with RC=return_code and feedback code code for DDNAME ddname

Explanation: A PowerExchange Logger for z/OS internal VSAM macro operation failed. This message includes the return code and feedback code that was captured by the SHOWCB macro.

System Action: If the VSAM operation ran against the JOURNAL or TRACE file, the PowerExchange Logger suspends VSAM file processing. If the operation was for a DEFINE_LOG command, the PowerExchange Logger ends the command. In other situations, the PowerExchange Logger ends.

User Response: To determine the cause of the error, check the appropriate VSAM manual for an explanation of the return code and feedback code. Then correct the problem and run the job again.

PWXEDM172604E UNALLOCATION FAILED, EC = error_code

Explanation: Dynamic deallocation failed during an SVC 99 operation.

System Action: The PowerExchange Logger ends.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 93

Page 94: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Collect all available information about the cause of the dynamic deallocation failure, and contact Informatica Global Customer Support.

PWXEDM172605E IDCAMS PASSED Return Code = rc

Explanation: The return code from IDCAMS is not zero. Either the DEFINE or DELETE CLUSTER operation failed.

System Action: If the IDCAMS operation is against the JOURNAL file, the PowerExchange Logger suspends JOURNAL file processing. Otherwise, the PowerExchange Logger ends.

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

PWXEDM172606E Logger internal MODCB for {ACB|RPL} failed with RC=return_code, and RSN=reason_code for DDNAME ddname

Explanation: The PowerExchange Logger for z/OS internal VSAM MODCB operation failed and returned the specified return code in R15 and the specified reason code in R0.

System Action: If the VSAM operation ran against the JOURNAL or TRACE file, the PowerExchange Logger suspends VSAM file processing. If the operation was for a DEFINE_LOG command, the PowerExchange Logger ends the command. In other situations, the PowerExchange Logger ends.

User Response: Check the VSAM file definitions. Then correct any errors and run the job again.

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.

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

User Response: Enter the correct PowerExchange Logger ID in the DEFINE command, and issue the command again.

PWXEDM172610E {UNALLOCATE|ALLOCATE} FAILED FOR {ACTIVE COPY|ARCHIVE COPY} DSN = dsname RC = return_code, EC = error_code

Explanation: Dynamic allocation failed {UNALLOCATE|ALLOCATE} for the specified data set. This message is issued in one of two formats. Error (E) or Warning (W) levels.

System Action: If this is an “E” level message, the command ends. 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.

User Response: Correct the cause of the allocation failure and reenter the command.

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

System Action: The PowerExchange Logger flushes all command sets already queued for the user without executing them.

94 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 95: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Correct the problem that caused the error, and run the job again.

PWXEDM172614E I/O Error, DSN=dsname

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

System Action: The PowerExchange Logger ends the command set.

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

PWXEDM172615E I/O ERROR SYNAD DATA: error_data

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

User Response: Use the SYNAD exit routine error information to determine the cause of the error. Correct the problem, and submit the request again.

PWXEDM172616E action failed for DSN=dsname

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

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

PWXEDM172617E {OPEN|CLOSE} ABEND abend_code FOR DSN=dsname

Explanation: A request to OPEN or CLOSE the data set specified by dsname ended abnormally with the specified abend code. The PowerExchange Logger subtask abends, and the PowerExchange Logger ends the command set.

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.

PWXEDM172619W logger_task_name primary and secondary archive allocation increased by 25

Explanation: A system abend SB37 occurred during the archive log allocation process because of insufficient space. The task identified by logger_task_name was running when the space problem occurred. The PowerExchange Logger for z/OS increased the primary and secondary space by 25.

System Action: Processing continues.

User Response: To prevent the SB37 system abend from recurring, Increase the values of the primary and secondary space parameters in the ARCHIVE_OPTIONS statement of the EDMUPARM options module.

PWXEDM172620E Open/Write error attempting to post function to the globalq RC=return_code RSN=reason_code

Explanation: An error occurred while attempting to post a function to the global queue for the edmlllg0 module.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 95

Page 96: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Logger ends abnormally.

User Response: Restart the PowerExchange Logger and contact Informatica Global Customer Support.

PWXEDM172622E Logger logger_ID not found.

Explanation: The DEFINE function failed to find the specified PowerExchange Logger for z/OS identifier in the EDMUPARM options module. The DEFINE function skips this PowerExchange Logger and continues processing.

User Response: Edit the EDMUPARM options module to include a valid PowerExchange Logger ID. Then run the job again.

PWXEDM172623W Logger was unable to allocate TRACE data set, tracing suspended

Explanation: The PowerExchange Logger for z/OS failed to allocate the trace data set.

System Action: Processing continues but tracing is suspended.

User Response: To diagnose the error, check allocation error messages that precede this message. Then, correct the allocation problem if possible.

PWXEDM172624W Logger parms module EDMUPARMS not found in EDMPARMS library, default EDMZPARM will be used

Explanation: The PowerExchange Logger for z/OS EDMUPARMS options module was not found in the EDMPARMS library.

System Action: The system loads the default module, EDMZPARM, into memory.

User Response: Check the EDMPARMS library for the EDMUPARM member. For more information about creating the EDMUPARM member, see the "Installing and Upgrading PowerExchange on z/OS" chapter in the PowerExchange Installation and Upgrade Guide.

PWXEDM172625W Logger trace I/O error tracing facility temporarily suspended(internal_error_code)

Explanation: The PowerExchange Logger for z/OS failed to READ or WRITE the trace data set because of an I/O error.

System Action: Processing continues but tracing is suspended.

User Response: To diagnose the error, check the error messages that precede this message. Then correct the I/O problem, if possible.

PWXEDM172626I INTERNAL trace status is {ACTIVE|INACTIVE}

Explanation: This message specifies whether an internal trace status is active or inactive for the PowerExchange Logger.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172627E Logger DEFINE_LOG aborted: required statement_name DD statement missing

Explanation: The PowerExchange Logger for z/OS DEFINE_LOG function failed to locate a required DD statement in the JCL. This message specifies the missing DD statement.

System Action: The DEFINE_LOG function ends abnormally.

User Response: Add the missing DD statement to the JCL. Then run the job again.

96 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 97: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172628E Logger NEWLOG aborted invalid condition ddname data set

Explanation: The PowerExchange Logger for z/OS NEWLOG function failed because an invalid condition was detected for the emergency restart data set (ERDS) defined by the specified DD in the Logger JCL. In the message text:

• condition is one of the following values: SYSOUT/SYSIN, NULL FILE, or TEMPORARY.

• ddname is either ERDS01 or ERDS02.

System Action: The NEWLOG function ends abnormally.

User Response: Ensure that the ERDS01 and ERDS02 DD statements in the JCL specify valid data sets. Then run the job again.

PWXEDM172629E Logger internal macro failed for ddname data set

Explanation: The PowerExchange Logger for z/OS internal DEFINE_LOG function failed because a macro returned an invalid return code for an emergency restart data set (ERDS) defined by the specified DD in the Logger JCL. In the message text:

• macro is RDJFCB.

• ddname is either ERDS01 or ERDS02.

System Action: The DEFINE_LOG macro ends abnormally.

User Response: Verify that valid ERDS01 and ERDS02 DD statements are correctly specified in the PowerExchange Logger JCL. Then run the job again.

PWXEDM172630E Logger ERDS active log data set record is full, DDNAME=ddname

Explanation: A PowerExchange Logger for z/OS DEFINE_LOG command cannot insert additional log definitions into the emergency restart data set (ERDS) because the ERDS is full. In the message text, ddname is the DDNAME of the full ERDS.

System Action: The PowerExchange Logger aborts the DEFINE_LOG command with a return code of 8.

User Response: Use the VSAM IDCAMS REPRO command to dump the ERDS. Examine the dump to determine the current status of the ERDS. Then, correct the problem and run the job again.

PWXEDM172631E Specified DSNAME already exists in ERDS, DDNAME=ddname

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

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

PWXEDM172632E Logger restart data set with DDNAME ERDS01 is empty

Explanation: The PowerExchange Logger for z/OS requires at least one emergency restart data set (ERDS) to operate. The primary data set allocated to ERDS01 is empty.

System Action: The PowerExchange Logger ends abnormally.

User Response: Ensure that the ERDS01 DD statement in the PowerExchange Logger JCL specifies a valid restart data set. Then run the job again.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 97

Page 98: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172633E Logger restart data set with DDNAME ERDS02 is empty

Explanation: The PowerExchange Logger for z/OS requires at least one emergency restart data set (ERDS) to operate. The dual data set allocated to ERDS02 is empty.

System Action: Processing continues with only the primary ERDS.

User Response: Check the PowerExchange Logger ERDS02 DD statement in the PowerExchange Logger JCL to verify that it specifies a valid restart data set that exists.

PWXEDM172634W Logger dataset_name Timestamp mismatch detected. Processing continues.

Explanation: The PowerExchange Logger for z/OS detected a time stamp mismatch between the primary and secondary emergency restart data sets (ERDSs) that are specified in the Logger JCL.

System Action: Processing continues with only one ERDS.

User Response: Check the PowerExchange Logger ERDS DD statements in the JCL to verify that the correct secondary ERDS was specified and exists. Also, ensure that the two ERDSs have the same time stamp.

PWXEDM172635E Logger internal logic error building control block block for restart_data_set

Explanation: The PowerExchange Logger for z/OS was unable to build the specified internal log control block for the emergency restart data set (ERDS).

System Action: The task ends abnormally with user abend code U3035 and reason code X'FFFF00xx'.

User Response: Get the job step listing. Then contact Informatica Global Customer Support.

PWXEDM172636E Logger could not find LogRBA=end-of-log_RBA in any log data set. Highest LogRBA found is RBA

Explanation: The PowerExchange Logger for z/OS log manager tried to find the end‑of‑log RBA, which is the highest RBA recorded in the emergency restart data set (ERDS). However, this RBA cannot be found in any log data set. The message reports the highest RBA that the log manager found.

System Action: The task ends abnormally with a user abend code U3035.

User Response: The most likely cause of this error is that a DELETE_LOG command deleted the log data set that contains the end-of-log RBA from the ERDS. If the log data set has not been reused, run the DEFINE_LOG command to add the log data set back to the ERDS. Then restart the PowerExchange Logger.

PWXEDM172637E Logger Restart Log Manager unable to initialize logger restart data set ddname

Explanation: The PowerExchange Logger for z/OS was unable to initialize the emergency restart data set that is allocated by the specified DD name. The ddname is either ERDS01 or ERDS02.

System Action: The task ends abnormally with user abend code U3035 and reason code X'FFFF00xx'.

User Response: Verify that you specified the correct PowerExchange Logger emergency restart data sets in the JCL. If the problem persists, get the job step listing. Then contact Informatica Global Customer Support.

PWXEDM172638I Logger System Timestamp for ERDS = date time

Explanation: This message reports the PowerExchange Logger for z/OS system time stamp for the emergency restart data set (ERDS).

System Action: Task processing continues.

98 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 99: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM172639I Active log Copy n is data_set_name for RBA range start_rba-end_rba

Explanation: At initialization, the PowerExchange Logger for z/OS identifies the active log data set that the system is currently using. Use this information to verify that the Logger is starting with the correct log data set.

System Action: The PowerExchange Logger continues running.

User Response: No response is required.

PWXEDM172640E Logical Logger unable to obtain new internal log buffer

Explanation: The PowerExchange logical logger was unable to get a new buffer to continue logging operations.

System Action: The task ends abnormally with user abend code U3035 and reason code X'F9FF00xx'.

User Response: To determine the cause of the problem, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172641E Logical module received invalid return code from move routine

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

System Action: The task ends abnormally with user abend code U3035 and reason code X'F9FF00xx'.

User Response: Complete a PowerExchange Logger trace by using the TRACE command. Get the trace file and job step listing. Then contact Informatica Global Customer Support.

PWXEDM172642E Log allocation error DSName=dsname, error status=reason_code

Explanation: The PowerExchange physical logger encountered an error while attempting to allocate the active or archive log data set with the specified data set name. The status value is the error reason code that the MVS dynamic allocation returns. The log manager response to the error depends on the type of data set involved.

For active log data sets, the following results can occur:

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

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 99

Page 100: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: The user response depends on the type of data set involved and the type of error that occurred.

If you were allocating active log data sets and the problem occurred during initialization, resolve the problem by performing one of the following actions:

• Resolve the error associated with the active log data set as indicated by the reason code.

• Provide another copy of the active log by using IDCAMS.

• Update the emergency restart data set (ERDS) with the PowerExchange Logger batch utility.

• Restart the PowerExchange Logger.

If you were allocating archive log data sets, respond as follows:

• 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) might eventually cause the available space in the active log to be exhausted (DSNJ111E). IF the active log becomes full, all future off-loads fail because of the same error.

• If the problem occurred during allocation with the intent to read the data set, the problems are likely MVS dynamic allocation errors. In this case, perform the following tasks:

- Determine the cause of the problem by using the appropriate MVS system messages and codes. Then correct those problems.

- Use the batch command DELETE_LOG to delete the archive log data set from the ERDS 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.

PWXEDM172643E Physical Logger received a RC=return_code RSN=reason_code from {DSPSERV|HSPSERV} {CREATE|SREAD|DELETE|RELEASE} macro for LOG log_dataset_name

Explanation: The PowerExchange physical logger received an invalid return code from an internal macro for the specified log data set.

System Action: The task ends abnormally with user abend code U3035 and reason code X'F9FF00xx'.

User Response: Identify the z/OS data in the virtual (DIV) macro that is causing the problem. If necessary, correct it.

PWXEDM172644E Physical Logger received a RC=return_code, RSN=reason_code, from DIV macro macro for log ddname

Explanation: The PowerExchange physical logger received an invalid return code from the specified internal MVS data in the virtual (DIV) macro for the specified log. The reason code indicates why the DIV macro processing cannot continue.

System Action: The task ends abnormally with user abend code U3035 and reason code X'F9FF00xx'.

User Response: To identify the z/OS data in the virtual (DIV) macro that is causing the problem, look up the MVS system messages and codes. If necessary, correct the problem and run the job again.

100 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 101: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172645E Write error DSName=dsname, RC=return_code, RSN=reason_code

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

System Action: The system action depends on the active logging option you selected:

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

User Response: See the appropriate z/OS documentation for a description of the HSPSERV reason codes. Also, correct the log marked as STOPPED by deleting it with the DELETE_LOG command and then reallocating it. Afterwards, run the job again.Note: A log that has a status is STOPPED is not usable.

PWXEDM172646E Physical Logger initialization failed for DSName=dsname, LogRBA=log_RBA

Explanation: The PowerExchange physical logger encountered an error during initialization of the active log data set that has the specified data set name.

System Action: The PowerExchange Logger truncates the current active log and tries to switch to the next active log data set.

User Response: To determine the cause of the error, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172647E Physical Logger termination failed for DSName=dsname, LogRBA=log_RBA.

Explanation: The PowerExchange physical logger encountered an error during termination of the active log data set that has the specified data set name.

System Action: The PowerExchange Logger truncates the current active log.

User Response: To determine the cause of the error, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172648E Physical Logger initialization failed unable to determine blocks available for logging

Explanation: The PowerExchange physical logger encountered an error when trying to determine the total blocks available for logging during the current run.

System Action: Processing ends abnormally with abend code U3035 and reason code X'00F9FF02'.

User Response: To determine the cause of the error, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 101

Page 102: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172649I Logger Offload handler will attempt to continue with active log copy 2

Explanation: The PowerExchange Logger offload handler was unable to allocate copy1 of the active log data set. If dual active logging is in effect, the PowerExchange Logger offload handler tries to continue by switching to copy 2 of the active log data set.

System Action: If the attempt to switch to copy 2 fails or if dual active logging is not in effect, the PowerExchange Logger ends the offload process.

User Response: To determine the cause of the problem, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172650E Logger Offload terminated for DSName=dsname, RSN=reason_code

Explanation: The PowerExchange Logger offload handler terminated because it was unable to archive the specified active log data set. The reason_code indicates the cause of the termination and can be one of the following values:

• 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 by using the DIV IDENTIFY macro.

• 03. The PowerExchange Logger was unable to access the active log data set by using the DIV ACCESS macro.

• 04. The PowerExchange Logger was unable to map the active log data set by 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 offload process.

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, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172651E Log unallocation error DSName=dsname, error status=reason_code

Explanation: The PowerExchange physical logger encountered a log unallocation error for the specified active or archive log data set. This message reports the reason code returned by MVS dynamic allocation (SVC99).

System Action: If this message is from the offload handler, the PowerExchange Logger ends the archive process.

User Response: To determine the cause of the error, look up the appropriate MVS system messages and codes. Then, correct the cause of the allocation failure and enter the command again.

PWXEDM172652E Logger internal DEFINE_LOG command failed for DSNAME=dsname

Explanation: The PowerExchange Logger offload processor encountered an error while attempting to update the PowerExchange Logger emergency restart data set (ERDS) with the new archive data set information.

System Action: The PowerExchange Logger ends the offload process. If the error is from the offload handler, the PowerExchange Logger ends the archive process.

102 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 103: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: To determine the cause of the problem, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172653E Logger log read error DSName=dsname, LogRBA=log_RBA, RC=return_code

Explanation: The PowerExchange Logger offload processor encountered an error while attempting to read the specified active log data set.

System Action: If the error occurred during the offload process, the offload processor tries to read the RBA range from a second copy.

• If a second copy does not exist, the offload 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 offload. 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 offload processor does not stop the first copy.

If the error occurred during restart, the PowerExchange Logger ends. A restart requires all copies of the active log data set to be available to the PowerExchange Logger.

If the active log data set has been stopped and is no longer used for logging, the data set is not deallocated. The PowerExchange Logger continues to use it for reading.

User Response: Check the system messages, such as IEC prefixed messages. Try to resolve the problem by using the recommended actions in those messages.

Alternatively, 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 emergency restart data set (ERDS) of the new archive log and log RBA range.

Note: When you receive this message, the data set can be stopped or not stopped. In either case, replace any active log data set that gives persistent errors of this type.

Warning: Repairing the stopped active log does not solve this problem because the offload processor does not go back to unload the stopped log. You must run the offload process and reestablish a valid active log.

PWXEDM172654I EOD reached at dsname=dsname, Logrba=logrba

Explanation: The PowerExchange Logger log read processor reached the end of the file at the specified logrba in the specified log data set name.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 103

Page 104: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172656E Logger unable to process log truncation request for reason reason_code

Explanation: The PowerExchange Logger physical logger encountered an internal error while attempting to truncate the current active log. While processing the ARCHIVE_LOG command, the PowerExchange Logger physical logger routine received an internal request to force‑write the log buffer and to truncate the active log and switch to the next available active log data set.

This error might have been caused by an unrelated abend in the PowerExchange physical logger, a STOP MODE=FORCE command, or an abnormal subsystem termination. The reason_code can be one of the following values:

• 04. The end of current active log operation failed.

• 08. The new active log operation could not be determined.

System Action: The PowerExchange Logger stops processing the command.

User Response: To diagnose the error, look up the messages and abends that precede this message. 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.

PWXEDM172657I Logger asynchronous log archive subtask initiated

Explanation: In response to an ARCHIVE_LOG command, the PowerExchange Logger started an asynchronous task to archive (offload) the active log data set. The PowerExchange Logger truncates the current active log data set, switches to the next available active log data set, and initiates the asynchronous offload task to archive the active log data set.

Note: The term asynchronous indicates that control returns to the invoker as soon as the offload task starts.

System Action: The PowerExchange Logger command processor accepts and processes any PowerExchange Logger commands while the offload task is running. If you use the MODE(QUIESCE) option with the ARCHIVE_LOG command, the system displays message PWXEDM172658I.

User Response: Follow normal operational procedures when the offload task begins.

PWXEDM172658I Logger ARCHIVE_LOG QUIESCE command ended. Logger capture activity is now resumed

Explanation: The PowerExchange Logger processed an ARCHIVE_LOG command with the MODE QUIESCE option. As part of MODE QUIESCE processing, the PowerExchange Logger stopped all 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 period and the resumption of normal PowerExchange Logger activity.

System Action: The PowerExchange Logger resumes normal logging activity for all users and jobs that were blocked during the quiesce period.

User Response: No response is required.

PWXEDM172659I Logger ARCHIVE_LOG command is already in progress

Explanation: An attempt to issue an ARCHIVE_LOG command was made while another ARCHIVE_LOG command was already in progress. The system continues processing the first ARCHIVE_LOG command and ignores the second command.

User Response: No response is required.

104 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 105: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172660I Logger ARCHIVE_LOG command terminated. Current active log data set is the last available

Explanation: The PowerExchange Logger for z/OS rejected the ARCHIVE_LOG command because the current active log is the last available active log data set.

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

User Response: Take the steps required to complete other waiting offload tasks. After you make another active log available (reusable) by completing the offload process for that log, command processing for the current active log can proceed.

PWXEDM172661I ARCHIVE_LOG done for DSName=data_set_name. StartRBA=start_rba, EndRBA=end_rba, StartTime=start_timestamp,EndTime=end_timestamp

Explanation: The PowerExchange Logger for z/OS archived the active log data set and updated the archive log data set inventory in the PowerExchange Logger emergency restart data set (ERDS) with the information about the new archive log.

In this message, the StartRBA and EndRBA values indicate the starting and ending relative byte addresses for the archive data set, and the StartTime and EndTime values indicate the time range.

User Response: No response is required.

PWXEDM172662E Logger was unable to {ADD | DELETE | FIND} UOW uow_ID to internal table

Explanation: When the PowerExchange physical logger received a begin UOW record for the specified unit of work (UOW), it could not add, delete, or find the UOW in the internal table.

System Action: The PowerExchange Logger ends.

User Response: To determine the cause of the error, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172663I Logger received sync_record_type record without corresponding begin_UOW record for UOW uow_ID

Explanation: The PowerExchange physical logger received a begin_sync_PH1, begin_sync_PH2, or end_sync_PH2 record for the specified UOW. However, a begin UOW record does not exist for this UOW. The PowerExchange Logger requires a begin_UOW record before it can recognize a begin_sync or end_sync record.

System Action: The PowerExchange Logger ignores the sync record for this UOW and continues processing.

User Response: To determine the cause of the error, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 105

Page 106: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172664E Logger operation_type operation for Queue queue_name failed for entry entry_value with RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS detected that an operation on an internal table failed. This message reports the operation type, the queue name of the internal table, the entry that was being processed, the return code, and the reason code.

In this message text, operation_type is one of the following values:

• ADD

• DELETE

• FIND

The queue_name is GBLCHKQCB.

System Action: The PowerExchange Logger ends abnormally.

User Response: To determine the cause of the failure, check the JES2 log for previous messages from the PowerExchange Logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172665E Physical Reader operation_type failed for DSName=dsname, LogRBA=log_RBA

Explanation: The physical reader encountered an error during an operation on the specified archive data set. The operation_type is one of the following values:

• Initialization

• Termination

• Get buffer

• Unallocation

System Action: The PowerExchange Logger ends the current archive extraction process.

User Response: To determine the cause of the problem, check the JES2 log for previous messages from the PowerExchange physical logger. If the problem persists, get the job step listing and contact Informatica Global Customer Support.

PWXEDM172666I Logger has determined that XCF is operating in local mode only

Explanation: The PowerExchange Logger for z/OS determined that the cross‑system coupling facility (XCF) is operating in local mode only. Local mode limits signaling and communications to the CPU.

System Action: Processing continues.

User Response: No response is required.

106 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 107: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172667E Reader operation_type failed for lrp_client. RSN=reason_code, RC=return_code

Explanation: A log reader operation failed for the specified log read processor (LRP) client.

In this message, operation_type is one of the following values:

• 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 PowerExchange 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: The PowerExchange Logger ends abnormally.

User Response: Use the reported reason code and return code to determine the cause of the problem. Correct the problem and then restart the PowerExchange Logger and run the job again. If the problem persists, collect all available information about the error and contact Informatica Global Customer Support.

PWXEDM172668I {Reader|Writer} identifier connected

Explanation: A log reader or writer requested to connect to the PowerExchange Logger for z/OS instance.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172669I {Reader|Writer} identifier disconnected from Logger logger_ID, RSN=reason_code, RC=return_code

Explanation: A log reader or writer disconnected from the PowerExchange Logger for z/OS. A writer can be an ECCR, and a reader is a process that reads the logs.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 107

Page 108: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172670I Client client_identifier started

Explanation: The log reader or writer client has started.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172671I Client client_identifier job_status

Explanation: This message reports the status of a log reader or writer job. In this message, job_status is one of the following values:

• ended successfully

• end data transfer

• ended abnormally

System Action: Processing continues.

User Response: If the job ended successfully or data transfer ended, no response is required. If the job ended abnormally, check the JES2 log for previous messages from the PowerExchange Logger. Then correct the problem and resubmit the job. Contact Informatica Global Customer Support if necessary.

PWXEDM172672I Last active log data set is nn percent full

Explanation: The PowerExchange Logger issues this message when the last available active log data set is 75 percent full. The PowerExchange Logger re-issues this message after each additional 5 percent of the data set space is filled.

The shortage of active log data set space has the following possible causes:

• Excessive logging, such as too many users requesting logs at the same time.

• Delayed or slow offloading, which can be caused by the system operator failing to mount archive volumes, incorrectly replying to offload 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 offloading 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 consume all space in the active log except for the current active log data set or sets.

• Offload process failure. For more information, see the user response.

• Insufficient active log space. For more information, see the user response.

System Action: Each time the PowerExchange Logger issues this message, it tries to perform offload processing. If the offload process is successful, the PowerExchange Logger does not re-issue this message. If the offload process is not successful and if the cause of the failure is not corrected, the active log data space fills until it reaches full capacity. The PowerExchange Logger then issues message PWXEDM172673I and halts all processing of change data.

108 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 109: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: To resolve this issue, you must either correct the problem that is causing the offload process to fail or add more active log data sets, as follows:

• To correct the problem this is causing the offload failure, complete other waiting offload tasks. Then, when an active log data set is made available or reusable, PowerExchange logging activity can continue. Perform a display request to determine the outstanding requests related to the log offload process. Respond to any outstanding requests and then permit the offload process to continue. If the offload process does not complete normally or cannot be initiated, notify the system programmer.

• To add more data sets, you must stop the logging process, stop the PowerExchange Logger, run the PowerExchange Logger batch change utility to add new active log data sets, and then restart the Logger.

PWXEDM172673I Logger out of space in active log data sets

Explanation: All space in all active log data sets has been used because of delays in offload processing. The PowerExchange Logger cannot continue processing.

System Action: The log manager waits for an available data set.

User Response: Use a DISPLAY OBJECT=LOG command to verify that no outstanding requests related to the log offload process exist. Respond to any outstanding requests and then permit the offload process to continue. If the delay was caused by lack of resources for the offload process, you must make the resources available so that the offload process can complete. The PowerExchange Logger can then resume processing.

PWXEDM172675I extended CHECKPOINT complete: RBA range start_rba-end_rba at date time. Start Time=timestamp ({QSAM I/O | TIMER | PROCESS | Restart I/O | logical log | physical log | XCF Interface | XCF Router})

Explanation: The PowerExchange Logger for z/OS completed an extended internal checkpoint. The checkpoint records were written to the active log data set between the specified StartRBA and EndRBA positions. The Start Time value is the TOD clock time stamp (GMT) that indicates when the checkpoint record was created. Use this message to determine where the PowerExchange Logger is currently logging data.

In a Post-Log Merge environment, this message shows the effective RBA of the first checkpoint record that was created. The timestamp is required to indicate the same record where the PowerExchange Logger is currently logging data.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172676I Logger Change Capture XCF‑Syncpoint request for uow_ID complete at date time

Explanation: The PowerExchange Logger completed processing a syncpoint request for the specified UOW ID. The request was sent through the cross‑system coupling facility (XCF) for an environmental change capture routine (ECCR). Request processing completed at the specified data and time.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 109

Page 110: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172677I Logger Change Capture XCF‑Syncpoint request for job failed (failure_type) at date time

Explanation: The PowerExchange Logger was unable to process a syncpoint request for the specified job. The request was sent through the cross‑system coupling facility (XCF) for an environmental change capture routine (ECCR). The failure occurred in the internal communication between the ECCR and PowerExchange Logger. The failure_type is one of the following values:

• Invalid input

• Invalid resync

System Action: Processing continues.

User Response: To correct the problem, contact Informatica Global Customer Support.

PWXEDM172678I Logger logger_ID detected nnnn uow_type units of work during restart

Explanation: The PowerExchange Logger for z/OS instance detected one or more units of work (UOWs) of the specified type during restart processing. In this message text, the uow_type is one of the following values:

• in-doubt

• in-commit

• in-abort

This message is sent to the JES console.

System Action: Processing continues.

User Response: For information about resolving in‑doubt UOWs, see the PowerExchange CDC Guide for z/OS.

110 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 111: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172679I Logger report_title report follows:

Explanation: The PowerExchange Logger for z/OS DISPLAY OBJECT=LOG and DISPLAY OBJECT=CONNECTION commands generate this message to present the title of a report that they generate. This message precedes the other messages that compose the report. The report_title is one of the following values:

• Log_Active

• Log_Archive

• UOW_Connection

• Reader_Connection

• Writer_Connection

If you enter the DISPLAY OBJECT=CONNECTION ,TYPE=READER command in a Post_Log Merge environment, this message adds the following line in the connection reader report:

Log_RBA=logger_rba, Read_RBA=read_rba, Start_Loc=start_locationThis line appears as an unnumbered message line in PWXEDM172679I. The line reports the following information for the current reader connections:

• Log_RBA. An RBA that indicates where the PowerExchange Logger is currently writing data.

• Read_RBA. An RBA that indicates where the log reader last processed.

• Start_Loc. A timestamp that indicates where the read request started. This timestamp is in TOD clock format.

Note: The Log_RBA and Read_RBA indicate the beginning of a block of Logger data. They do not reflect the record that is currently being processed within that block.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172680I Logger command normal completion at date time

Explanation: Processing of the PowerExchange Logger command completed successfully at the specified data and time.

User Response: No response is required.

PWXEDM172681E Logger RESOLVE_INDOUBT {COMMIT|ABORT} for UOW uow_ID failed at date time (error_type)

Explanation: A PowerExchange Logger for z/OS RESOLVE_INDOUBT COMMIT or ABORT command failed at the specified data and time. In this message, the error_type is one of the following values:

• UOW not found. The PowerExchange Logger did not find the specified UOW.

• ECCR=eccr_name. The PowerExchange Logger found the specified UOW, but the name of the ECCR that is associated with the UOW is incorrect.

• Gbl Queue error. An error occurred while PowerExchange was attempting to write a command notification to the PowerExchange Logger input queue.

• Pkt Queue error. The UOW information could not be added to the PowerExchange Logger internal queue.

• EDMLLLG0 error. An error occurred while the EDMLLG0 module was processing the command.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 111

Page 112: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The RESOLVE_INDOUBT command fails, but PowerExchange Logger processing continues.

User Response: If the UOW was not found, verify that the UOW ID specified in the RESOLVE_INDOUBT command matches the UOW ID shown in the DISPLAY OBJ=CONN,TYPE=UOW command output. If the ECCR name was incorrect, verify that the correct ECCR name is specified in the RESOLVE_INDOUBT command. After you correct either error, run the RESOLVE_INDOUBT UOW command again. If the problem persists, contact Informatica Global Customer Support.

If another error type caused the failure, contact Informatica Global Customer Support.

PWXEDM172682I Logger RESOLVE_INDOUBT {ABORT|COMMIT} done for uowid at scheduled date/time

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172683E No subsystem handle for agent agent_name RC=return_code, RSN=reason_code (code_description)

Explanation: The PowerExchange Logger for z/OS was unable to connect to the PowerExchange Agent during initialization.

System Action: The PowerExchange Logger ends abnormally.

User Response: Verify that the PowerExchange Agent and the common services module are operational, and then run the job again. Use the return code and reason code to get more information abou the error.

PWXEDM172684I Logger {simple|extended} CHECKPOINT complete for UOW=uow_ID at date time

Explanation: The PowerExchange Logger for z/OS completed a simple or extended internal checkpoint for the specified unit of work (UOW) at the specified date and time.

System Action: Processing continues.

User Response: No response is required.

112 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 113: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172687I Logger command command {failed|completed} with RC=return_code, RSN=reason_code

Explanation: The specified PowerExchange Logger for z/OS command completed or failed with the specified return code and reason code. In the message text, command is one of the following values:

• ARCHIVE_LOG

• DEFINE

• DEFINE_LOG

• DEL_LOG

• DISPLAY

• END

• PRINT

• RESOLVE_INDOUBT

• STOP

• TRACE

System Action: If the return code and reason code are 0, command processing continues. Otherwise, command processing ends, even though PowerExchange Logger processing continues.

User Response: If the return code and reason code are 0, no response is required. If the return code and reason code are a non-zero value, check the JES2 log for previous messages from the PowerExchange Logger that pertain to the specified command.

If this message is for an ARCHIVE_LOG command, you must correct the problem that is preventing the PowerExchange Logger from performing the archive process normally. This problem might be related to space availability or catalog issues. After the problem is corrected, other waiting offload tasks have completed, and another active log is available, issue the ARCHIVE_LOG command again for the current active log. If you do not correct the error, the PowerExchange Logger will issue warning messages when available active log data space reaches critically low levels. A final message indicates that there is no active log. The PowerExchange Logger then stops processing until active log space is made available.

PWXEDM172690E Logger logic error. Invalid LogRBA=log_RBA for log with StartRBA=start_RBA, EndRBA=end_RBA

Explanation: The PowerExchange Logger for z/OS received a request to write a block with a log RBA that is outside the boundaries of the currently active log. This message provides the requested log RBA and the start and end RBAs for the active log.

System Action: The PowerExchange Logger ends with abend code U3035 and reason code X'0F9FF020'.

User Response: Contact Informatica Global Customer Support.

PWXEDM172691W Logger could not locate DSName=dataset_name. Log stopped

Explanation: The PowerExchange Logger physical logger could not find the specified active log data set.

System Action: The PowerExchange Logger stops both the primary and corresponding secondary logs and does not use them during the current run.

User Response: To determine the cause of the problem, look for system messages, such as IEC prefixed messages. Then, correct the problem and run the job again. Also, you might need to recover the log by using the DELETE_LOG and DEFINE_LOG commands.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 113

Page 114: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172692E Logger detected an unequal number of primary and secondary logs defined in ERDS.

Explanation: The PowerExchange Logger physical logger found a usable secondary log during the log file switch process after it had been running in a single logging mode.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172693E Logger detected an insufficient number of active logs defined in ERDS.

Explanation: The PowerExchange Logger for z/OS detected that not enough active log data sets are defined in the emergency restart data set (ERDS) to start logging captured change data. This condition usually exists for one of the following reasons:

• Fewer than two data sets are defined for one of the active log copy sets.

• The EDMUPARM options module specifies ACTIVE_LOG_MODE=DUAL for dual logging. However, data sets for two copies of the active log are not defined in the ERDS.

• Fewer than two data sets are available for one of the active log copy sets. Available data sets are those not flagged as STOPPED.

System Action: PowerExchange Logger startup processing ends abnormally.

User Response: Use the PowerExchange Logger batch change utility to make the number of active log data sets defined in the ERDS consistent with the ACTIVE_LOG_MODE parameter in teh EDMUPARM module. You might need to recover log data sets that have a status of STOPPED. The PowerExchange Logger does not reuse STOPPED log data sets. To recover these data sets, either redefine them or recover them from the other copy of the log. Also delete the log data sets and add them to the ERDS with the appropriate RBA addresses. To delete and add log data sets to ERDSs, use the Logger batch change utility. When finished, restart the PowerExchange Logger.

PWXEDM172695I Logger detected an invalid record on Input Queue. Record ignored.

Explanation: The PowerExchange Logger for z/OS detected a record with an invalid record type on the input queue while processing change records. A valid record must have one of the following type indicators in position 24 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.

System Action: The PowerExchange Logger ignores the invalid record and continues processing.

User Response: No response is required.

PWXEDM172696E Logger could not find Checkpoint with LogRBA=log_RBA in any log data set

Explanation: The PowerExchange Logger for z/OS could not locate a checkpoint at the specified log RBA in any known log data set. The PowerExchange Logger requires a checkpoint for restart processing.

114 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 115: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing ends.

User Response: Determine a valid checkpoint for restart processing, and then start the PowerExchange Logger again. If you need assistance, contact Informatica Global Customer Support.

PWXEDM172697E Logger operation_type operation for XCF Message Q failed with RSN=reason_code, and RC=return_code({ EDMLCQ00|EDMLLLG0|EDMLST10|EDMLXMR0})

Explanation: The specified PowerExchange Logger operation for the cross-system coupling facility (XCF) local circular queue failed with the specified reason code and return code. The XCF circular queue might have an internal error.

In this message, the operation_type is one of the following values:

• CREATE

• OPEN

• PUT

• CLOSE

System Action: Processing ends.

User Response: Collect all available information about the error. Then contact Informatica Global Customer Support.

PWXEDM172698I Logger received an invalid request data transfer start: logger_ID startRBA, from Reader reader_identifier

Explanation: The PowerExchange Logger for z/OS received a start RBA that is not valid from the specified log reader.

System Action: Processing continues. The Logger send a request for the log reader to end.

User Response: Check the EDMPARMS DD statement or STEPLIB concatenation for the EDMSDIR module to verify that the correct Logger ID is specified. Then correct the job and run it again.

PWXEDM172699I ECCR task_name reinstated. Oldest RBA= oldest_RBA, Last RBA= last_RBA, Logger UOW= last_UOW

Explanation: During restart processing, the PowerExchange Logger for z/OS encountered a type‑1 ECCR and reinstated it in internal control blocks.

System Action: PowerExchange Logger processing continues.

User Response: No response is required.

PWXEDM172700I Logger unable to find options for logger_ID, default options in effect

Explanation: The PowerExchange Logger for z/OS initialization processor was unable to locate the EDMUPARM options module for the specified Logger ID. As a result, the PowerExchange Logger is using the default options in the EDMZPARM.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172701I Logger executing with control_block at log_RBA

Explanation: The PowerExchange Logger for z/OS is using the specified control block and executing at the specified RBA position in the log data set.

System Action: Processing continues.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 115

Page 116: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM172702W Stealing active_log_dataset StartRBA=start_rba - nnnnnnnn active readers

Explanation: The PowerExchange Logger for z/OS needs to reuse the specified active log data set name and start RBA, because no other active logs are available. However, the specified number of log reader processes are currently reading the active log. This message is issued as a WTO message.

System Action: The PowerExchange Logger begins to write new data to the active log data set. This action might result in a reader abend.

User Response: Determine why the PowerExchange Logger was forced to steal the active log data set. The number of active log data sets might be insufficient, especially if the number of log reader processes that normally run is greater than the number of active log data sets. To determine the number of reader processes that are currently active, use the PowerExchange Logger DISPLAY command.

Another cause of this problem is a failure to archive active log data. Examine the status of any recent archive attempts. You can also use the PowerExchange Logger DISPLAY command to determine the status of the active log data sets and whether any need to be archived.

PWXEDM172703I Logger is now operating in single logging mode on log_data_set

Explanation: The PowerExchange Logger encountered an allocation or I/O error in the specified emergency restart data set (ERDS) or active log data set. The PowerExchange Logger has switched to single logging mode for the specified log data set.

System Action: Processing continues.

User Response: To diagnose the error, review the messages in the JES log and PowerExchange message log.

PWXEDM172711E Command processor found that required keyword keyword is missing

Explanation: A PowerExchange Logger for z/OS command was entered without a required keyword. This message is issued as a WTO message.

System Action: The command is not executed.

User Response: Enter the command again with the required keyword.

PWXEDM172712E Command processor detected keyword=value, which is not supported in batch

Explanation: The PowerExchange Logger command includes the keyword=value specification, but this type of specification is not allowed when the Logger command processor runs in batch mode. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing of the current command set.

User Response: Correct the command set, and submit it again.

PWXEDM172713E Command processor detected a non alphanumeric value for keyword

Explanation: An invalid value was entered for the specified keyword in a PowerExchange Logger for z/OS command set. The keyword value must consist of all alphanumeric characters and begin with a non‑numeric character. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

116 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 117: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172714E Command processor detected keyword keyword1 and keyword2 which are mutually exclusive

Explanation: You cannot use both of the specified keywords in a single PowerExchange Logger for z/OS command set. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing of the current command set.

User Response: Correct the command set, and submit it again.

PWXEDM172715E Command processor detected a value length error for keyword, found value

Explanation: The value of the specified keyword found in the current PowerExchange Logger for z/OS command set is too long. The value must not exceed the maximum length for the value type. For example, a time stamp must not exceed 13 bytes, and a data set name must not exceed 44 bytes. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing of the current command set.

User Response: Correct this command set, and submit it again.

PWXEDM172716E error_description for keyword_name ‑ found value_found

Explanation: The indicated value of the keyword [ERROR DESCRIPTION | KEYWORD NAME | VALUE FOUND] must conform to a special format, such as data set name or time stamp. The value entered was not acceptable. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command and resubmit it. If necessary, read the keyword description in the manual to insure that the data format is acceptable. A 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”.

PWXEDM172717E Command processor was expecting a keyword, found value

Explanation: The PowerExchange Logger for z/OS command processor was expecting a keyword, but found another value, such as the next characters in the input stream. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172718E Command processor detected keyword keyword value delimiter incorrect

Explanation: The PowerExchange Logger for z/OS detected the specified keyword but the keyword value was incorrectly followed by an equals (=) sign, for example, KEY=XXXX=. This command structure is not valid. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172719E Command processor detected duplicate value value for keyword keyword

Explanation: The PowerExchange Logger for z/OS detected that the specified value is entered twice for the same keyword. A keyword cannot have duplicate values. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 117

Page 118: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Correct the command set and submit it again.

PWXEDM172720E Command processor detected keyword keyword expecting value, found value_entered

Explanation: The PowerExchange Logger for z/OS detected that the value entered for specified keyword is not valid. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172721E Command processor detected a length error, initial_part_of_value

Explanation: A PowerExchange Logger for z/OS syntax scan of a command set found a name or undelimited value that is too long. This message shows the first part of the invalid value. A name or undelimited value cannot be longer than 64 characters. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172722E Command processor expects a numeric value for keyword, found value

Explanation: The PowerExchange Logger for z/OS command processor found the specified non‑numeric value for a keyword that requires a numeric value. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172723E VALUE TOO LONG FOR keyword

Explanation: The value you entered is too long for this keyword. The PowerExchange Logger ends processing of the current command set.

User Response: Correct this command set, and submit it again

PWXEDM172725E Command processor was expecting a value for keyword, found end of input or delimiter

Explanation: The PowerExchange Logger for z/OS found a keyword for which no value is specified, for example, KEY=. The keyword cannot have a null value. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172726E Command processor detected a missing string delimiter for keyword

Explanation: The PowerExchange Logger for z/OS did not find a string delimiter, as expected, for the specified keyword. To specify strings, use the X'00' or C'AA' format, where the characters after the X or C can be any character except a blank or semicolon (;). This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command and submit it again.

118 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 119: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172727E Command processor detected a string delimiter missing or invalid for keyword

Explanation: The PowerExchange Logger for z/OS 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. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172728E Command processor detected a null string for keyword

Explanation: The PowerExchange Logger for z/OS found a null string, such as C' ' or X' ', for the specified keyword. This keyword cannot contain null strings. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command and submit it again.

PWXEDM172729E Command processor detected invalid hexadecimal digits for keyword

Explanation: The PowerExchange Logger for z/OS found invalid characters in a hexadecimal string that is specified for a keyword. Only the following alphanumeric characters are allowed: 0 1 2 3 4 5 6 7 8 9 A B C D E F. For example, the string X'12G4' is invalid. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172730E Command processor detected a odd number of hexadecimal digits for keyword

Explanation: The PowerExchange Logger for z/OS detected that the hexadecimal string that is specified for the keyword is invalid because it contains an odd number of characters between the delimiters. For example, X'123' is invalid. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172731E Command processor found that string starting character is invalid for keyword, must start with quote, C, or X

Explanation: The PowerExchange Logger for z/OS detected that the value entered for the specified keyword is invalid. The keyword accepts only delimited values that have one of the following formats:

• A value that is enclosed in single or double quotation marks. For example: KEYWORD='VALUE'

• A value that begins with C and is followed by a beginning delimiter, value, and ending delimiter. The delimiter can be any special character, including quotation marks. For example: KEYWORD=C/VALUE/

• A value that begins with X and is followed by a beginning delimiter, hexadecimal value, and ending delimiter. The delimiter can be any special character, including quotation marks. For example: KEYWORD=X'E5C1D3E4C5'

This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 119

Page 120: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Correct the command set and submit it again.

PWXEDM172732E Command processor detected a value for keyword that is too long

Explanation: The PowerExchange Logger for z/OS detected that the value entered for the specified keyword is longer than the maximum allowed length. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172733E Command processor detected a duplicate keyword keyword

Explanation: The PowerExchange Logger for z/OS detected that the same keyword is specified twice in the command set. Duplicate keywords are not allowed. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172734E Command processor was expecting a comma, found characters

Explanation: The PowerExchange Logger for z/OS expected to find a comma (,) between the values that are entered for a keyword. Instead of a comma, the PowerExchange Logger found the characters that are reported in this message. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172735E Command processor was expecting a subcommand, found characters followed by “=”

Explanation: The PowerExchange Logger for z/OS expected to find a subcommand within the command set. Instead, the PowerExchange Logger found the specified characters, which are the next string of characters in the input stream, followed by an equals (=) sign. Possible reasons for this error:

• A comma is missing between two keywords.

• A level 2 command is followed by an equals sign.

• A subcommand is misspelled.

This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172736E ABBREVIATION abbreviation IS AMBIGUOUS

Explanation: A command, keyword, or value name abbreviation is too short. More than one keyword or command name begins with the specified characters.

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Correct this command set, and submit it again.

PWXEDM172737E Keyword keyword value must be between value1 and value2

Explanation: The PowerExchange Logger for z/OS found a numeric keyword value that is outside the range of valid numeric values. This message is issued as a WTO message.

120 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 121: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172738E Subcommand subcommand may only be used once in this command set

Explanation: The PowerExchange Logger for z/OS found that the specified subcommand occurred more than once in the command set. This subcommand can be entered only once in a single command set. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172739I FORMATTING OF THE LOG DATASET IS COMPLETE

Explanation: The PowerExchange Logger utility has completed the pre-formatting of the log data set.

Processing continues.

User Response: No response is required.

PWXEDM172740E Command processor was expecting a command, found characters

Explanation: The PowerExchange Logger for z/OS expected to find a command but found the specified characters instead. The characters value can be one of the following string types:

• A word that is not a command

• The END command

• The end of the input file

• A string of invalid characters

This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172741E Command processor was expecting a subcommand, found characters

Explanation: The PowerExchange Logger for z/OS expected to find a subcommand but found either a word that is not a command or a string of invalid characters. The KEYWORD=VALUE specification must be followed by a comma and another keyword, the END command, or a subcommand. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172742E Command processor was expecting a command, found command_or_keyword_name followed by “=”

Explanation: The PowerExchange Logger for z/OS expected to find a command. Instead, it found either a command or keyword name followed by an equals (=) sign. This value is not valid. This message is issued as a WTO message.

System Action: The PowerExchange Logger stops processing the current command set.

User Response: Correct the command set and submit it again.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 121

Page 122: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172743E Invalid state reason for EDMLCP00

Explanation: The PowerExchange Logger received an invalid reason code from the command parsing routine.

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Contact Informatica Global Customer Support.

PWXEDM172744E keyword1=value1 is required when keyword2=value2 is used

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

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Enter the command set with the required first keyword, or eliminate the second keyword.

PWXEDM172745E Command structure is not compatible with [required | excluded | assumed] keyword

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

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Contact Informatica Global Customer Support.

PWXEDM172746E The subcommand subcommand and keyword keyword=value are mutually exclusive

Explanation: The PowerExchange Logger found a keyword or keyword=value that you cannot use with the specified subcommand.

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Correct this command, and submit it again.

PWXEDM172747E The subcommand subcommand is required when keyword=value is used

Explanation: The PowerExchange Logger did not find the specified subcommand. This subcommand is required when you use the specified keyword or keyword and value.

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Enter the command set either with the required subcommand or without the specified keyword.

PWXEDM172768E Threshold% value for phase_name higher than threshold% value for phase_name

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

System Action: The PowerExchange Logger ends processing of the current command set.

User Response: Correct the command set and resubmit.

PWXEDM172769E Reset% value greater than threshold% value for subcommand‑name

Explanation: You specified a Reset% keyword value that was greater than the Threshold% value. This is not allowed.

System Action: The PowerExchange Logger ends processing of the current command set.

122 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 123: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Correct the command and resubmit.

PWXEDM172770E FORMAT UTILITY HAS ABORTED DUE TO ERROR IN RTN: routine RC: return_code RSN: reason_code

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 the following:

• GETM-PGE GETMAIN

• GENCB GENCB (ACB)

• SHOW-OPN SHOWCB 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

System Action: The utility is terminated.

User Response: 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 Global Customer Support.

PWXEDM172771E Task task_name has encountered a error_type error with RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS task encountered an unexpected error condition with an unknown resolution.

System Action: The PowerExchange Logger ends abnormally.

User Response: Contact Informatica Global Customer Support.

PWXEDM172772W Logger logger_ID is on the last active log, check EDMMSG for more information

Explanation: The PowerExchange Logger for z/OS processed the last active log and has no more selectable logs left to process. Possible reasons for this situation:

• A lack of archive space

• The capture process is proceeding at a faster pace than the log archive process

System Action: The PowerExchange Logger continues processing.

User Response: Check if the capture process is proceeding faster than the log archive process. If so, increase the number of active logs.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 123

Page 124: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172773I Writer identifier Current RBA = current_RBA Oldest RBA = oldest_RBA

Explanation: This message is issued each time the DB2 for z/OS ECCR connects to or disconnects from DB2. It reports the ECCR, or writer, identifier, the DB2 relative byte address (RBA) that the ECCR is currently processing, and the RBA of the oldest UOW in progress.

System Action: ECCR processing continues.

User Response: No response is required. Retain this information if you plan to issue a STARTLOC command.

PWXEDM172774I Writer writer_name Event Mark generated:writer_banner_line

EDP Logger RBA . . . . . . . . . : loggerRBA

Sequence number . . . . . . . . . : seqNum

Edition number . . . . . . . . . : editionNum

Source EDMNAME(s) . . . . . . . . : source_tagname

Explanation: The PowerExchange Logger for z/OS issues this message to list the contents of an event marker that is written to the logs by a PowerExchange component that uses the Log Write API (LWAPI), such as an ECCR or the PowerExchange Listener. The writer_banner_line depends on the writer type. For example, the following banner lines might appear:

• DB2 QUIESCE of TABLESPACE tablespace_name at DB2 RBA/LRSN { db2_rba | db2_lrsn }The DB2 ECCR wrote an event marker when it detected a table space QUIESCE operation. The variables db2_rba and db2_lrsn represent the point in the DB2 log at which the QUIESCE was detected. If the DB2 logs are for a DB2 data-sharing system, the value is a LRSN. Otherwise, the value is a RBA.

• Finished with Plog copy plog_dsn , last time date time The Adabas ECCR wrote an event marker when it finished processing a PLOG. The variables date and time represent the date and time at which the Adabas ECCR finished processing the PLOG.

• CAPI generated Event MarkThe PowerExchange Logger wrote a CAPI-generated event marker.

This message is issued as a WTO message.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172777E Logger received record_type record with no Begin_UOW from ECCR eccr_name for UOW uow_ID, SEQ= sequence_number

Explanation: The PowerExchange Logger for z/OS issues this error message each time it receives a record from an ECCR without a corresponding begin UOW record for a UOW.

In the message text:

• record_type is one of the following values:

- BEGIN_PH1. begin‑phase‑1 record.

- BEGIN_PH2. begin‑phase‑2 record.

- END_PH2. end‑phase‑2 record.

124 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 125: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

- CHANGE. change record.

• eccr_name is the name of the ECCR.

• uowID is the UOW ID of the UOW that was assigned by the ECCR.

• sequence_number is the ECCR‑assigned sequence number for the record.

This message is issued as a WTO message and is written to the EDMSLOG file of the PowerExchange Agent.

User Response: Check the JES2 log for previous messages from the PowerExchange Logger. Also examine the previous messages for the ECCR. If you cannot diagnose the problem, collect the job step listings and contact Informatica Global Customer Support.

PWXEDM172778W Logger discarding duplicate Begin_UOW from ECCR eccr_name for UOW uow_ID

Explanation: The PowerExchange Logger for z/OS received a duplicate begin_UOW record from the specified ECCR for a UOW. The Logger already received this record. This situation can occur during a restart of a type 1 ECCR, if the previous ECCR instance was not shut down with the QUIESCE command. The only type 1 ECCR is the DB2 ECCR. In this message, the uow_ID is the RBA or sequence number of the begin_UOW record.

System Action: After this warning message is issued, the PowerExchange Logger ignores the begin_UOW record and continues processing.

User Response: Check the JES2 log for previous messages from the PowerExchange Logger. Also examine previous messages for the ECCR. If you cannot diagnose the problem, collect the job step listings and contact Informatica Global Customer Support.

PWXEDM172779W Logger retrying HSPSERV SREAD of block at RBA RBA, found RBA RBA

Explanation: Occasionally, after the PowerExchange 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 reason for these abends is that an HSPSERV SREAD operation returned a page that contains all zeros for a page that was previously read. This problem is described in IBM APAR OW56713. The PowerExchange Logger can detect this condition and retry the HSPSERV SREAD operation up to 100 times.

System Action: Each time a retry is required, message 172779 is issued. The found RBA value will most likely be 0. If the condition persists after 100 retries, the log reader subtask of the PowerExchange Logger abends with user abend code U3035 and reason code 00D6FF14. 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.

User Response: Restart any terminated log reader jobs.

PWXEDM172780E Wrong RBA found in log record in DSN=archive.log.dataset.name. Expected RBA eeeeeeeeeeee, found RBA ffffffffffff

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

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 125

Page 126: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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.

PWXEDM172781E Missing data at EOF on log dataset archive.log.dataset.name. Expected last RBA eeeeeeeeeeee, found RBA ffffffffffff

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

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

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.

PWXEDM172782E ACTIVE LOG DATASET IS TOO LARGE

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

System Action: The format utility ends.

User Response: Delete the active log data set, and recreate it with a smaller number of cylinders, then rerun the format utility.

126 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 127: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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 is used as the active log data set, and whether that is the primary or secondary active log.

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

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

PWXEDM172784E Attach failed for module load_module RC=x'nnnnnnnn'

Explanation: The PowerExchange Logger for z/OS encountered an error when it tried to ATTACH the specified load module, which is required for Logger processing. The message provides the return code related to this error.

System Action: The Logger will end abnormally.

User Response: To determine the reason for the failure in the ATTACH macro, use appropriate operating system documentation. Also review related messages. If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

PWXEDM172785E Logger subtask terminating for program program_name, Return code=return_code

- or -Logger subtask terminating for program program_name, Abend code={Ssss|Uuuuu}, Reason code=reason_code

Explanation: 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: The Logger continues termination. PowerExchange issues this message when the PowerExchange Logger ends abnormally or normally.

User Response: Investigate any earlier messages that might indicate why a subtask might 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 Global Customer Support.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 127

Page 128: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172786I task_name global_queue_function for global_queue_name failed. RC=return_code, RSN=reason_code description

Explanation: The PowerExchange Logger for z/OS encountered an error while processing a function call to the specified global circular queue that it uses to send or receive data. Global queues are used to pass data between address spaces. This message reports the task name, function type, the name of the global circular queue, the return code, and the reason code.

The global_queue_function can be one of the following values:

• CLOSE

• CREATE

• DELETE

• GET

• OPENINL

• OPENOUT

• PUT

• SETEOF

This message is issued as a WTO message.

System Action: The PowerExchange Logger ends abnormally.

User Response: To determine the reason for the failure in the function call, review related messages and examine the appropriate operating system documentation. If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

PWXEDM172787I Number of active log datasets currently available: Primary=pppp, Secondary=ssss

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

System Action: Processing continues normally.

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

128 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 129: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172788E All active log datasets with Startrba=rrrrrrrrrrrr are unusable

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

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 129

Page 130: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172789W Logger operation_type operation for queue queue_name failed for address_space with RC=return_code, RSN=reason_code

Explanation: The PowerExchange Logger for z/OS attempted an operation on an internal queue. The return code from the operation indicates that the operation was not successful. When the error occurred, the PowerExchange Logger was either processing a message from another address space or trying to send a message to another address space.

This message reports the type of Logger operation, the name of the internal queue, the identifier of the other address space, the return code, and rthe eason code.

The operation_type is 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 queue_name is one of the following values:

• GBLXCFQCB

• GBLOUQQCB

• GBLINQQCB

• OUQEDMQCB

System Action: Processing continues. However, if the PowerExchange Logger was processing a message that it received, it will drop the message. If the PowerExchange Logger was trying to send a message, the message will not be sent. In either case, the other address spaces might be left in an unexpected wait condition.

User Response: To determine the cause of the PowerExchange Logger problem with processing the message it received or tried to send, review other messages, including those issued from other address spaces, log readers, or ECCRs. Also, refer to the appropriate operating system documentation, if necessary. If you cannot diagnose and correct the problem, contact Informatica Global Customer Support.

130 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 131: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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.

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

PWXEDM172791I Reader identifier filter list has number entries

Explanation: The PowerExchange Logger for z/OS received a Resource Interest List from a log reader address space and processed it successfully. The Resource Interest List provides a list of registration EDMNAMEs for the source objects in which the log reader is interested. The PowerExchange Logger uses this list to filter change records 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. The message reports the number of EDMNAMEs in the Resource Interest List.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172792E Logger log DSName=data_set_name is not formatted.

Explanation: During initialization, the PowerExchange Logger for z/OS detected that the specified active log data set is not formatted. Typically, the Logger log data sets are formatted when they are created.

PWXEDM172502I to PWXEDM172798I: The PowerExchange Logger 131

Page 132: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Logger ends abnormally.

User Response: Use the PowerExchange EDMLUTL0 utility to format the log data set. To run the utility, use the sample JCL in the #EDMLFMT member of the hlq.SAMPLIB library.

PWXEDM172798I generic_message

Explanation: This is a PowerExchange Logger informational message.

System Action: Processing continues.

User Response: Respond to the message, if applicable. Otherwise, no response is required.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC)

PWXEDM172800E Error in module 'module' offset X'number'. text

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

System Action: Processing ends.

User Response: Collect all available information about the termination, and contact Informatica Global Customer Support.

PWXEDM172801E process failed. Return code=return_code, Reason code=reason_code. text

Explanation: A program called a service or function that returned a non-zero return code, which indicates an error. The text portion of this message presents information about the error.

System Action: Processing ends.

User Response: For more information about the error, check the preceding messages in the JES message log and EDMMSG message log. If this message presents an IBM return code, see the IBM messages and codes documentation for the subsystem type for an explanation of the return code. After you collect all available information about the error, contact Informatica Global Customer Support.

Note: PowerExchange issues reason codes from encoded commands that pass between program modules and might include these reason codes in error messages.

PWXEDM172802E Service task ended prematurely. Completion code=rc, Reason=reason. Program=program

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

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

Processing ends.

132 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 133: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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.

PWXEDM172803E EDM Agent is not active and STEPLIB is not APF‑authorized

Explanation: 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: Processing ends.

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

PWXEDM172804E Unable to LOAD module module

Explanation: The specified module could not be found in the JOBLIB/STEPLIB concatenation.

System Action: Processing ends.

User Response: Verify that all required load libraries are in the JOBLIB/STEPLIB concatenation.

PWXEDM172805E DD ddname is missing

Explanation: The specified DD statement, which is required, is missing.

System Action: Processing ends.

User Response: Provide the specified DD statement, and run the job again.

PWXEDM172806E Unable to OPEN DD ddname

Explanation: The change interface component (CIC) could not OPEN the file specified in the DD statement.

System Action: Processing ends.

User Response: See any previous error messages related to this error to determine why the OPEN failed. Then, correct the problem, and run the job again.

PWXEDM172807E ABEND issued by function, Abend code=abend_code, Reason code=reason_code. text.

Explanation: The specified function ended abnormally with the specified abend code and reason code. Report text with more information follows.

System Action: Processing ends.

User Response: Review the preceding messages that are related to this error. After you collect all available information about the error, contact Informatica Global Customer Support.

PWXEDM172808I Change Capture active for Tag registration_tag_name {DB2 table|VSAM file|IMS DBD/DSN|Detail} [attributes]

Explanation: This message reports that change data capture is active for the source object that is identified by the reported attributes and that is associated with the capture registration that has the specified tag name. For an IMS DBD or data set, the message lists the segments and the registration tab name is shown for each segment.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 133

Page 134: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172809I Change Capture counts for source_object: Insert=n, Update=n, Delete=n

Explanation: This message is issued after the ECCR stops to show counts of records that the ECCR sent to the PowerExchange Logger for z/OS for the specified source object, by record type. These counts are for low-level database operation types, not for SQL operations. This message is not issued if all of the counts are 0.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172810E XCF function in error. Return code=rc, Reason code=reason. Group='group', Member='member'.

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

System Action: The job step attempts to recover the failing job, and the job remains active to process other requests.

User Response: Check for previous error messages related to this error. Collect all available information about the message, and contact Informatica Global Customer Support.

PWXEDM172811I XCF is in local mode only

Explanation: The Cross‑System Coupling Facility (XCF) is active but is not using the coupling facility hardware.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172812E Unable to establish XCF connection to EDM Logger (loggerid)

Explanation: The job was unable to contact the specified PowerExchange Logger through the Cross‑System Coupling Facility (XCF) interface.

System Action: The job ends.

User Response: 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).

PWXEDM172813E call_type call to global queue global_queue_ID failed. RC=rc, Reason code=reason.

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

User Response: Check for previous error messages related to this error. Collect all available information about the termination, and contact Informatica Global Customer Support.

PWXEDM172814E CIC circular queue manager received a record with an invalid IPC header from program

Explanation: The specified program passed a record with an invalid header to the change interface component (CIC) circular queue manager.

System Action: Processing ends.

User Response: Collect all available information about the termination, and contact Informatica Global Customer Support.

134 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 135: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172815E EDM Agent is required

Explanation: This job uses certain PowerExchange facilities, such as global queues, that require the PowerExchange Agent.

System Action: Processing ends.

User Response: Start the PowerExchange Agent, and run the job again.

PWXEDM172816E EDM logger logger_ID terminated [abnormally] while {reader|writer} was active

Explanation: While a reader or writer task was active, the PowerExchange Logger ended. This message is issued as a WTO message.

System Action: Depending on the value of the system global parameter CCERR, one of the following actions occur:

• If CCERR=CONT, the job continues but PowerExchange change capture stops. The changes that were in progress are lost.

• If CCERR=ABEND, processing ends.

User Response: Try to determine what caused the PowerExchange Logger to terminate. Then correct the problem and restart the PowerExchange Logger.

PWXEDM172817E EDM ECCR received TERMINATE command from EDM Logger loggerid

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

System Action: The ECCR ends.

User Response: Determine what caused the PowerExchange Logger to terminate. Correct the problem, and start the PowerExchange Logger again.

PWXEDM172818I status XCF group 'group' as member 'member'

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172819I XCF group 'group' status by member 'member'

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 135

Page 136: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172820I Change Capture initialized for source_type on source_description

Explanation: This informational message reports the source software level in the CDC environment in which the ECCR has initialized. The message is issued as a WTO message and written to the EDMMSG and EDMSLOG data sets.

The message text includes the following variables:

• source_type is DB2, CICS/VSAM, IMS Batch, IMS DBRC, IMS Online, or VSAM Batch.

• source_description depends on the source type, as follows:

- For CICS/VSAM sources: CICS/TS version.

- For DB2 sources: [group_attach_name].subsystem_name, where group_attach_name is displayed only for a subsystem that is a member of a data sharing group

- For IMS Batch, IMS DBRC, and IMS Online sources: IMS_version - subsystem_ID.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172821E XCF member 'member' already active in group 'group'

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

System Action: Processing ends.

User Response: 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 EDM Global Directory name loaded from dsname, Agent Id=agentid, Logger Id=loggerid

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172823W Unable to connect to EDM Agent agentid, RC=rc, Reason code=reason

Explanation: The job or component issuing this message was unable to contact the specified PowerExchange Agent.

System Action: The job or component continues processing without the PowerExchange Agent services.

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

136 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 137: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172824W EDM Change Capture waiting on [the Logger’s queue | the ECCR‑to‑CIC queue] since datetime. Using EDM Logger loggerid.

Explanation: The job or component issuing this message has filled the queue used to send changed data to the PowerExchange Logger.

System Action: Processing continues.

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: The job issuing this message contains some units of work that are waiting on PowerExchange Change to complete sync point processing.

System Action: Processing continues.

User Response: 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 datetime uowid

Explanation: The specified unit of work is waiting on the specified commit processing phase. This message is preceded by message PWXEDM172825.

System Action: Processing continues.

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

PWXEDM172828E EDM Logger returned error during {Phase 1 syncpoint|Phase 2 syncpoint|'resolve in-doubt'} processing, return code=rc, Reason code=reason. Unit-of-work id follows: uowid

Explanation: The PowerExchange Logger generated a non-zero return code during the specified process. The ID for the affected unit of work is displayed.

System Action: Processing continues.

User Response: To determine the cause of the error, check the EDMMSG data set and any messages displayed by the PowerExchange Logger.

PWXEDM172829I EDM ECCR sent n records to Logger loggerid (m change records)

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172830I module loaded at address

Explanation: The specified module was loaded at the specified address.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 137

Page 138: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172831I Capture Status {not resolved|resolved as inactive} for structure_name, DEST=SUBSYS

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

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.

User Response: 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 is resolved when the next database OPEN initiates a repository call. If the cause of the error cannot be determined, contact Informatica Global Customer Support.

PWXEDM172841I EDM ECCR job {connected to|disconnected from} EDM Logger loggerid, Log RBA=log_rba

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172842E DB2 ECCR terminating due to prior logger failure

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

System Action: Processing ends.

User Response: Restart the PowerExchange Logger. Restart the DB2 ECCR using the START WARM statement. This allows the DB2 ECCR to synchronize with the PowerExchange Logger.

PWXEDM172843I Resolve-in-doubt: UOW=uowid, Func=Abort, Return code=rc, Reason code=reason

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172844W Following unit-of-work failed during {Phase 1|Phase 2} syncpoint processing, Reason code=reason

Explanation: A unit-of-work was told to abort because of a prior error.

System Action: The unit-of-work abends.

User Response: See associated messages issued for cause of the error.

PWXEDM172845I Reply is “value”

Explanation: An operator responded with the specified value.

System Action: Processing continues.

User Response: No response is required.

138 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 139: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172846W Following unit of work was {committed|aborted} during restart processing, SUBSYSTEM=sysid, TOKEN=uowid.

Explanation: This message indicates the status of in-doubt units of work during restart processing in a CICS/DBCTL environment.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172847W Following unit of work requires manual resolution, SUBSYSTEM=sub_system TOKEN=UOWID.

Explanation: This message indicates that the UOW identified by the sub_system and UOWID variables is in doubt and requires intervention to resolve.

System Action: Processing continues.

User Response: 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

{EDMCIRDB–IMS ESS CALL TO IMS DBC FAILED|EDMCIRDB–GETMAIN FAILED IN IDENTIFY|EDMCIRDB–FREEMAIN IMS AREA DID NOT WORK |EDMCIRDB–IDENTIFY GETMAIN NEW AREA ERROR|EDMCIRDB–KEY 7 STORAGE GETMAIN ERROR|EDMCIRDB–FREEMAIN 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.

System Action: Processing continues, but resolve-in-doubt processing is not available.

User Response: Contact Informatica Global Customer Support.

PWXEDM172849I EDMCICRG: environment_type RET=rc, RSN=reason, structure_name

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

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 139

Page 140: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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

User Response: No response is required.

PWXEDM172850E Logger loggerid is on system sysid1, jobid is on system sysid2

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

System Action: The specified job ends.

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

System Action: Processing continues. A message from the IMS ECCR is lost. The error might have occurred in an IMS BMP or MPP region.

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

140 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 141: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172852I Options in effect:

Explanation: When you start an ECCR or other component, PowerExchange issues a report that shows the options in effect for that component. This message text introduces that report. Depending on the component, the following options can be listed:

• LOAD library that contains EDMSDIR

• EDMSDIR assembly date and time

• EDP Rollup version and build information

• PowerExchange Agent ID

• PowerExchange Logger ID and type

If you use the CICS/VSAM ECCR, the EDMMSG output also shows the product distribution date.

If you use the DB2 for z/OS ECCR, the EDMSG output also shows the product distribution level, SYSOUT class, and action to take if the ECCR encounters an error.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172853I Change Capture counts for object Segment=segment_name, ISRT=n, REPL=n, DLET=n

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172854I Segment=segment_name, Segment Code=segment_code, ISRT=n, REPL=n, DLET=n

Explanation: This message follows PWXEDM172853 and shows capture counts by segment for an IMS ECCR. The message number is not shown.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172855I Edition=n, EDMNAME=edmname

Explanation: This message follows message PWXEDM172808 and shows the EDMNAME for the data being captured. The message number is not shown.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172856I Segment=segment_name, SegCode=segment_code, Edition=n, EDMNAME=edmname

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 141

Page 142: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172857E EDM Agent agentid {has not been started|is not active}

Explanation: The PowerExchange Agent is not active. The PowerExchange Agent must be running to perform change captures.

System Action: Processing ends.

User Response: Start the PowerExchange Agent, and try the job again.

PWXEDM172863I Counts for CIC internal data queue; Record count=nnnn, queue full count=nnnn, queue empty count=nnnn

Explanation: This informational message describes the number of times a task waited on either a full queue or an empty queue.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172865E No active profile found. Function='02'

Explanation: The EDMFUNC module was called with a command of '02'. No active registered object was found in the PowerExchange repository.

System Action: The EDMFUNC module returns a nonzero return code and processing ends.

User Response: You must register and activate one or more objects in the PowerExchange repository before you can run the change capture process.

PWXEDM172872W DD ddname {not allocated, already existed | not deallocated, did not exist}.

Explanation: The dynamic allocation service could not either allocate the DD because it already existed or deallocate the DD because it did not exist.

System Action: Processing continues.

User Response: Use any messages issued after this message to determine whether any action is necessary. If no messages are issued, no action is necessary.

PWXEDM172873I The following ZAPs have been applied:

Explanation: This message precedes a line that shows which ZAP modifications have been incorporated into the PowerExchange code.

System Action: Processing continues.

User Response: No response is required. This information may be requested by Informatica Global Customer Support.

142 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 143: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172874E Changed data lost for EDMNAME=edmname {due to failing logger|due to updates during logger failure|recovery needed on target object} (mm/dd/yyHH:MM:SS)

Explanation: This message is issued by CIC when the PowerExchange 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 three variations of message text, indicated in curly braces {message_text} are as follows:

• 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. PowerExchange 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 PowerExchange 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: This message is followed by the warning message PWXEDM172875W. Data capture processing continues despite the data loss.

User Response: 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. You might need to repopulate or recover the target 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.

System Action: Processing continues.

User Response: 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 are synchronized.

PWXEDM172876W Unable to record recovery needed status for EDMNAME=edmname, RC=rc, Reason=reason

Explanation: The system is unable to record a recovery needed status for a given PowerExchange object, due to failure on the repository data set.

System Action: Processing continues. The instance of lost changed data is not recorded in the repository for the displayed object.

User Response: See the preceding messages to determine the reason for failure.

PWXEDM172877E Unable to load module. EDMSDIR must be in EDMPARMS or STEPLIB dataset

Explanation: The system is unable to load the EDMSDIR from either the EDMPARMS DD or the STEPLIB DD.

System Action: Processing continues, data is not captured.

User Response: See the preceding messages to determine the reason for failure.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 143

Page 144: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM172878I Processing DD “ddname” with DSN “dsnname”

Explanation: The change interface component is processing the specified data definition name for the specified data set name.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172879I Area "nn" processed for DD "ddname"

Explanation: The change interface component is processing the specified FastPath area for the specified data definition name.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172880E Duplicate area "nn" found in DD "ddname"

Explanation: The change interface component encountered a FastPath area, in the specified data definition name, that was previously processed.

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

User Response: Check which data definition names contain the correct data and restart the job.

PWXEDM172881E *** The following UOWs must be manually resolved ***

Explanation: This IMS environmental change capture routine (ECCR) message indicates that you must manually commit or abort units of work (UOW).

System Action: The IMS ECCR continues the startup process.

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

PWXEDM172882E UOW In‑doubt ECCR=jobname UOWID=uowid needs manual resolution

Explanation: This IMS ECCR message follows messages PWXEDM172881E and PWXEDM172883E and shows a list of the UOWs that you must manually commit or abort.

System Action: The IMS ECCR continues the startup process.

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

PWXEDM172883E UOWs for change capture were unresolved due to IMS COLDSTART

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

System Action: The IMS ECCR continues the startup process.

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

PWXEDM172884I nn schema(s) marked for refresh

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

144 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 145: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The change interface component reads the schemas when LRP processes the next CCD record for the EDMNAMEs.

User Response: No response is required.

PWXEDM172885I LRP schema for edmname refreshed due to {Schema Time Stamp|Refresh command}

Explanation: The change interface component refreshes a schema for an EDMNAME due to the time stamp of the schema or an earlier LRP,REFRESH command.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172886I The following Load Module replacements have been installed:

Explanation: This message reports the load module replacements that have been installed or made by a subsequent fix.

System Action: Processing continues.

User Response: No response is required.

PWXEDM172887E EDP is not receiving control from the DBRC Interface, DATA CAPTURE IS STOPPED

Explanation: The DBRC interface, that is used by PowerExchange, cannot receive control.

System Action: The IMS ECCR continues the startup process and the PowerExchange change capture process is turned off.

User Response: Check the DBRC address space to verify that the correct libraries are in the DBRC region.

PWXEDM172889I Action if ECCR error encountered has been set to {CONTINUE|ABORT}

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

System Action: The IMS processing continues.

User Response: No response is required.

PWXEDM172890W There are no open databases registered for capture

Explanation: The IMS operator issued a /SSR command to request statistics [STAT| STATWTO], but there are no databases that have passed the registration process.

System Action: The IMS processing continues.

User Response: No response is required.

PWXEDM172891W An SSR command has been issued that is unknown to EDP

Explanation: The IMS operator issued a /SSR command other than a PowerExchange CONTINUE, ABORT, STAT, or STATWTO command.

System Action: The IMS processing continues.

User Response: Verify that you are using the desired /SSR command and reissue.

PWXEDM172800E to PWXEDM172894W: Change Interface Component (CIC) 145

Page 146: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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 PowerExchange Logger cannot return this information. For example, it is waiting for a tape mount.

System Action: The ECCR will suspend initialization and display a message.

User Response: Investigate the state of the PowerExchange Logger. If you can resolve the problem with the PowerExchange Logger, the ECCR will continue initialization.

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.

System Action: Processing continues. When full ECCR initialization is completed, the registration data is forwarded, and message 172808 is 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.

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

PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger

PWXEDM173000W XCF request {QUIESCL|RESUMEL} received from member xcf_member_name (logger_jobname on system_name) ‑ reason

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 is inconsistent with the requested status change.

This message includes the type of request that was received, the XCF member from which the request was sent, the job name of the member Logger, and the system where the member Logger runs.

The message also identifies the type of problem that the Post‑Log Merge task detected in the request. In the message text, reason is one of the following values:

• Member already quiesced

• Member not quiesced

• Member stopped

System Action: Processing continues but the status of the member Logger, as understood by the Post‑Log Merge task, is not changed.

146 Chapter 3: PWXEDM172000 to PWXEDM173002

Page 147: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: To diagnose the problem, review related messages, particularly those for the member Logger and including messages issued from other address spaces. If appropriate, refer to related operating system documentation. If you cannot identify and correct the problem, contact Informatica Global Customer Support.

PWXEDM173001I Member xcf_member_name (logger_jobname on system_name) now {quiesced|resumed} logging for Reader log_reader_name

Explanation: 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. The PowerExchange Logger either acquired a quiesced status, which means it will temporarily not log any more data, or resumed logging data after being quiesced.

This message is issued once for each log reader that is active at the time the status change. The message includes the logical name for the member Logger (xcf_member_name), the job name of the member Logger, and the name of the system where the member Logger is running. The message also indicates whether the status changed to quiesced or resumed and the logical name of the log reader that was affected by the change.

System Action: Processing continues.

User Response: No response is required.

PWXEDM173002I Member xcf_member_name (logger_jobname on system_name) {active|inactive}

Explanation: The Post-Log Merge task detected a status change in one of the member Loggers from which it was merging data. The member Logger either:

• Signed on to the Post-Log Merge task and will start logging the data to be merged

• Left the XCF group and will not log any additional data

This message includes the logical name for the member Logger (xcf_member_name), the job name of the member Logger, and the name of the system where the member Logger is running. This message also identifies whether the member Logger has become active or has left the system.

if the member Logger became active, this message is followed by message PWXEDM172141I. If the member Logger left the system, this message is preceded by message PWXEDM172142W, which issued for each log reader that was receiving merged data from the member Logger.

System Action: Processing continues.

User Response: No response is required.

PWXEDM173000W to PWXEDM173002I: The PowerExchange Logger 147

Page 148: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 4

PWXEDM175000 to PWXEDM175648

This chapter includes the following topic:

• PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities, 148

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities

PWXEDM175015I message_text

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

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

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

PWXEDM175016I message_text, return code=rc, reason=reason, logrba=logrba

Explanation: The PowerExchange Create Event Marker utility issues this message to indicate the status of an event command.

The message text contains the following variables:

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

148

Page 149: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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 294 and “Reason Codes 00000601 to 00004499 - Command” on page 267.

PWXEDM175017I message_text, highest return code=rc, highest reason=reason

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

System Action: The utility ends.

User Response: 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 294.

PWXEDM175025I Event Mark Notify={EDITION | COPY | ENDCOPY} Summary: event_type.....:event_value...

Explanation: 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: The PowerExchange Create Event Marker utility processing continues.

User Response: Make a note of the information to be used as input to the apply restart utility.

PWXEDM175028E EDMNAME, edition=edition_level, reason=reason_code [reason_explanation]

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.

System Action: Processing for the current command ends with an error.

User Response: 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 267.

PWXEDM175029E Event notify utility abending due to write end packet failure, reason=reason

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

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities 149

Page 150: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The PowerExchange Logger ends processing for the event notify utility.

User Response: 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 294.

PWXEDM175603E MESSAGE messagenumber (internal message text) HAS NOT BEEN PASSED THE CORRECT NUMBER OF PARAMETERS

Explanation: 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: The PowerExchange job will perform the action associated with the message that could not be generated.

User Response: Contact Customer Support for assistance in determining the exact error.

PWXEDM175604I BSCT CREATION TIME: mmddyyyyhh:mm:ss

Explanation: PowerExchange generates this informational message when verifying the version of the BSCT component.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175605E UNABLE TO FIND EDP RELEASE LEVEL

Explanation: The BSCT subcomponent was not able to load an PowerExchange global control block.

System Action: The PowerExchange job ends.

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

PWXEDM175606I BSCT AT LEVEL v.r.mm.fff

Explanation: PowerExchange generates this informational message when verifying the version of the BSCT component.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175607I TARGET PROCESSING IS COMPLETE FOR TARGET: target_name

Explanation: Processing has completed for the specified target (target_name).

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175608I target informational message

Explanation: The PowerExchange target specified in the previous message (PWXEDM175607I) has generated the data displayed in this message.

System Action: The PowerExchange job continues.

150 Chapter 4: PWXEDM175000 to PWXEDM175648

Page 151: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM175609W target warning message

Explanation: The PowerExchange target specified in message PWXEDM175607I has generated the data displayed in this message.

System Action: The PowerExchange job continues.

User Response: Review the information provided by the target processor to determine if the warning requires a response.

PWXEDM175610I TARGET INITIALIZATION STEP 2 COMPLETE FOR TARGET target_namePhase 2

Explanation: Initialization processing for the specified target (target_name) has completed. The

System Action: PowerExchange job continues.

User Response: No response is required.

PWXEDM175611I TARGET INITIALIZATION STEP 2 STARTING FOR TARGET target_name

Explanation: Phase 2 initialization processing for the specified target (target_name) has started. The

System Action: PowerExchange job continues.

User Response: No response is required.

PWXEDM175612I TARGET INITIALIZATION STEP 1 COMPLETE FOR TARGET target_name

Explanation: Phase 1 initialization processing for the specified target (target_name) has completed. The

System Action: PowerExchange job continues.

User Response: No response is required.

PWXEDM175613I TARGET INITIALIZATION STEP 1 STARTING FOR TARGET target_name

Explanation: Phase 1 initialization processing for the specified target (target_name) has started. The

System Action: PowerExchange job continues.

User Response: No response is required.

PWXEDM175614I BULK SOURCE CONTROL TASK PROCESSING STARTING

Explanation: The PowerExchange PAC has started the BSCT component.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175616I BSCT SOURCE/TARGET INTEREST LIST DELIVERY IS STARTING

Explanation: The BSCT component has begun communication with the PowerExchange data transformer component.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities 151

Page 152: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM175617I BSCT SOURCE/TARGET INTEREST LIST DELIVERY IS COMPLETE

Explanation: The BSCT component has sent the source and target interest lists to the PowerExchange data transformer component.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175618I BSCT TARGET INITIALIZATION IS STARTING

Explanation: The BSCT component has started to send initialization information to the PowerExchange target processors.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175619I BSCT TARGET INITIALIZATION IS COMPLETE

Explanation: The BSCT initialization process is complete.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175620I BULK SOURCE CONTROL TASK PROCESSING IS COMPLETE

Explanation: The BSCT component has determined that all processing for this PowerExchange job has completed.

System Action: The PowerExchange job ends.

User Response: No response is required.

PWXEDM175621E ERROR ATTEMPTING TO CONNECT TO EDP MESSAGE PROCESSOR: RC = return_code

Explanation: The BSCT component cannot connect to the internal PowerExchange message processor. The

PowerExchange job ends.

User Response: Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing.

PWXEDM175622E ERROR ATTEMPTING TO DISCONNECT FROM EDP MESSAGE PROCESSOR: RC = return_code

Explanation: The BSCT component cannot disconnect from the internal PowerExchange message processor.

System Action: The PowerExchange job ends.

User Response: Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing.

PWXEDM175623E ERROR ATTEMPTING TO CONNECT TO EDP COMMON SERVICES: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component cannot connect to PowerExchange common services. The

System Action: PowerExchange job ends.

User Response: Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing.

152 Chapter 4: PWXEDM175000 to PWXEDM175648

Page 153: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM175624E ERROR ATTEMPTING TO DISCONNECT FROM EDP COMMON SERVICES: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component cannot disconnect from PowerExchange common services. The

System Action: PowerExchange job ends.

User Response: Scan the PowerExchange job log for prior errors. Increase the PowerExchange job's REGION size. Ensure that the PowerExchange Agent is executing.

PWXEDM175625E ERROR ATTEMPTING TO ACCESS EDP PAC INFORMATION: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component cannot access PowerExchange PAC internal control blocks. The

System Action: PowerExchange job ends.

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

PWXEDM175626E ERROR ATTEMPTING TO OPEN INTERNAL INPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component cannot communicate with other PowerExchange components necessary to perform a PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175627E ERROR ATTEMPTING TO OPEN INTERNAL OUTPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component cannot communicate with other PowerExchange components necessary to perform a PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175628E ERROR ATTEMPTING TO OPEN INTERNAL COMMAND QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component cannot communicate with other PowerExchange components necessary to perform a PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities 153

Page 154: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM175629E ERROR ATTEMPTING TO CLOSE INTERNAL INPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175630E ERROR ATTEMPTING TO CLOSE INTERNAL OUTPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175631E ERROR ATTEMPTING TO CLOSE INTERNAL COMMAND QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175632E ERROR ATTEMPTING TO READ FROM INTERNAL INPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

PWXEDM175633E ERROR ATTEMPTING TO WRITE TO INTERNAL OUTPUT DATA QUEUE: RC = return_code; REASON CODE = reason_code

Explanation: The BSCT component encountered an error while attempting to communicate with other PowerExchange components necessary to perform PowerExchange propagation.

System Action: The PowerExchange job ends.

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.

154 Chapter 4: PWXEDM175000 to PWXEDM175648

Page 155: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM175634I target status information

Explanation: The target apply component sends status information messages to the BSCT component, usually during checkpoint processing.

System Action: The PowerExchange job continues.

User Response: No response is required.

PWXEDM175635E TARGET INITIALIZATION ERROR FOR TARGET target_name

Explanation: The specified target apply component (target_name) encountered an error during initialization.

System Action: The PowerExchange job ends.

User Response: Check the log file of the failed target apply component. Fix the problem that generated the error, and restart the job.

PWXEDM175636E ERROR ATTEMPTING TO SEND INTEREST LISTS

Explanation: The BSCT component could not send source or target processing lists to the data transformer component.

System Action: The PowerExchange job ends.

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.

PWXEDM175637E ERROR ATTEMPTING TO SEND PAC INIT COMPLETE COMMAND

Explanation: The BSCT component could not send an initialization‑complete message to the PAC master task.

System Action: The PowerExchange job ends.

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.

PWXEDM175638E BULK PROFILE NAME IS MISSING

Explanation: The PowerExchange job contains an invalid or missing PowerExchange profile name.

System Action: The PowerExchange job ends.

User Response: Ensure that you specified the correct profile name as input to the PowerExchange job and that the correct PowerExchange repository is being used.

PWXEDM175639E INTERNAL ERROR BUILDING BULK PROFILE REQUEST: error_information

Explanation: The PowerExchange job could not find a valid profile with the given PowerExchange profile name.

System Action: The PowerExchange job ends.

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

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities 155

Page 156: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM175640E target error information

Explanation: A target apply task encountered an error. This message lists the error.

System Action: The PowerExchange job ends.

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

PWXEDM175641E TARGET RETURNED AN INVALID RESPONSE

Explanation: A target apply task encountered an unknown processing error.

System Action: The PowerExchange job ends.

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

PWXEDM175642E SOURCE TYPE 'DB2/IMS/VSAM' NOT LICENSED FOR USE

Explanation: The licensing check failed.

System Action: The PowerExchange job ends.

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

PWXEDM175643E UNABLE TO ACCESS PAC CONTROL BLOCKS: RC= return_code; REASON CODE = reason_code

Explanation: The BSCT was unable to access internal PAC control blocks.

System Action: The PowerExchange job ends.

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

PWXEDM175646E A TARGET COMPLETE MESSAGE WAS SENT FOR AN UNKNOWN TARGET target_name

Explanation: BSCT has received information from an unknown target writer (target_name).

System Action: The PowerExchange job ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM175647E NO TARGET WRITERS SUCCESSFULLY INITIALIZED

Explanation: PowerExchange does not currently issue this message.

System Action: The data propagation job ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM175648E UNEXPECTED actual_response_type RESPONSE RECEIVED WHEN expected_response_type RESPONSE EXPECTED

Explanation: A target writer terminated unexpectedly.

System Action: The PowerExchange job ends.

156 Chapter 4: PWXEDM175000 to PWXEDM175648

Page 157: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Scan the PowerExchange job log for prior errors. Scan the target writers' job logs for errors. When the problem is resolved, rerun the job.

PWXEDM175000 to PWXEDM175648E: PowerExchange Utilities 157

Page 158: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 5

PWXEDM176400 to PWXEDM177699

This chapter includes the following topics:

• PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR, 158

• PWXEDM177012I to PWXEDM177699W: DB2 ECCR, 169

PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR

PWXEDM176400E Undefined message number msg_number

Explanation: A CICS/VSAM ECCR internal module issued a message. However, the specified message number is not defined in PowerExchange.

System Action: The message is not displayed. Processing continues.

User Response: Collect all available information about the error and contact Informatica Global Customer Support.

PWXEDM176401E function PROGRAM(program) EXIT(exit) failed. EIBRCODE=X"error_code", RESP=response_code, RESP2=response_code2

Explanation: During CICS/VSAM ECCR initialization, the EXEC CICS ENABLE or EXEC CICS EXTRACT EXIT function for the specified program and exit point failed with the specified CICS error code and response codes.

System Action: ECCR initialization fails.

User Response: To determine the cause of the failure, look up the CICS error code and response codes in the IBM CICS Application Reference Manual. Then correct the problem, and start the ECCR again.

PWXEDM176402E CICS Shutdown (Immediate) requested due to Initialization error/s

Explanation: During CICS/VSAM ECCR initialization, one or more fatal errors occurred. To prevent change data loss, the CICS region must be shut down.

System Action: PowerExchange issues a request to shut down CICS.

158

Page 159: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: To determine the cause of the errors, examine the CICS job log, MVS SYSLOG data set, and PowerExchange message log. Then correct the problem and start the CICS/VSAM ECCR again.

PWXEDM176403E Fatal error returned from EDMCCICS. Reason code is reason_code.

Explanation: During CICS/VSAM ECCR initialization, the EDMCCICS function returned a fatal error.

System Action: ECCR initialization fails.

User Response: To determine the cause of the failure, examine the CICS job log, SYSLOG data set, and PowerExchange message log. Then correct the problem.

PWXEDM176404I CICS/VSAM Change Capture Initialization completed successfully

Explanation: The CICS/VSAM ECCR completed initialization without any errors and is now active.

System Action: The ECCR begins capturing change data.

User Response: No response is required.

PWXEDM176405I CICS/VSAM Change Capture Initialization is in progress

Explanation: The CICS/VSAM ECCR is initializing.

System Action: Processing continues.

User Response: No response is required.

PWXEDM176406E Invalid operand specified - press ENTER for help

Explanation: The EDMC transaction for the CICS/VSAM ECCR was entered with an operand that is not valid.

System Action: The transaction terminates.

User Response: Press ENTER to display a list of valid operands for the transaction. Then enter the transaction again with a valid operand.

PWXEDM176407E Initialization request rejected - CICS/VSAM Change Capture is already initialized

Explanation: An EDMC transaction was entered with the INIT operand to manually initialize the CICS/VSAM ECCR. However, the ECCR already completed initialization.

System Action: The transaction terminates.

User Response: No response is required.

PWXEDM176408E operand request rejected - CICS/VSAM Change Capture has not been initialized

Explanation: The EDMC transaction for the CICS/VSAM ECCR was entered with the DISPLAY, OPTIONS, REFRESH, XPGM, or TERM operand. However, the transaction request was rejected because the ECCR has not been initialized.

System Action: The transaction terminates.

User Response: Initialize the CICS/VSAM ECCR and enter the transaction again.

PWXEDM176409I CICS/VSAM Change Capture Termination is complete

Explanation: A request to terminate the CICS/VSAM ECCR completed. The ECCR is no longer active.

System Action: Change capture processing stops.

PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR 159

Page 160: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM176410E No CCD entry for Registered File(file_name)

Explanation: During Open exit processing of the specified VSAM file, PowerExchange did not find an entry for the file in the Change Capture Directory (CCD). Open exit processing fails.

System Action: PowerExchange terminates the Open request and closes the file.

User Response: Contact Informatica Global Customer Support.

PWXEDM176411E Registration check failed for File(file_name) - CICS/VSAM CDC is terminating.

Explanation: During PowerExchange Open exit processing of the specified VSAM file, one or more registration-checking errors occurred.

System Action: Because CCERR=CONTinue is specified in the EDMSDIR options module, PowerExchange issues a request to stop the CICS/VSAM ECCR.

User Response: To determine the cause of the failure, examine the CICS job log, MVS SYSLOG data set, and PowerExchange message log. Then correct the problem.

PWXEDM176412E Registration check failed for File(file_name) - File changes suppressed

Explanation: During PowerExchange Open exit processing of the specified VSAM file, registration-checking errors occurred.

System Action: The file Open request continues but the file is marked with the "Reg Err" flag in the display of participating files to indicate that it is in error. Because CCERR=ABEND is specified in the EDMSDIR options module, any subsequent CICS tasks that write changes to the file end abnormally during syncpoint processing to avoid potential change data loss.

User Response: To determine the cause of the failure, examine the CICS job log, MVS SYSLOG data set, and PowerExchange message log. Then correct the problem. Also, stop the CICS/VSAM ECCR and then restart it to clear the error flag.

PWXEDM176413E Definition of Registered File(file_name) specifies Recovery(None)

Explanation: PowerExchange Open exit processing for the specified VSAM file failed. The failure occurred because the file resource definition specifies RECOVERY(NONE) but the INITPARM statement for the EDMKOPER module does not specify AllowRecoveryNone.

System Action: PowerExchange terminates the Open request and closes the file.Note: PowerExchange also reacts in this manner when you specify CCERR=ABEND in the EDMSDIR options module.

User Response: Verify that the VSAM file is correctly defined and that it is supposed to be registered for change data capture. If the file is correctly defined as RECOVERY(NONE), specify both AllowRecoveryNone in the INITPARM statement and CCERR=CONTinue in the EDMSDIR options module.

PWXEDM176414E Registered File(file_name) is not a local keyed or relative-record VSAM file

Explanation: PowerExchange Open exit processing of the specified VSAM file failed because the file is not a VSAM KSDS, RRDS, or VRRDS data set.

System Action: PowerExchange terminates the Open request and closes the file.

User Response: Verify that the VSAM file is correctly defined and that it is supposed to be registered for change data capture. Correct any problems.

160 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 161: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM176415E Unable to locate before image record for update of File(file_name)

Explanation: When trying to process an update or delete request for the specified VSAM file, PowerExchange did not find the before image of the record. PowerExchange needs the before image to process the change.

System Action: PowerExchange rejects the update or delete request.

User Response: Contact Informatica Global Customer Support.

PWXEDM176416E Unexpected return code return_code on update call for File(file_name)

Explanation: PowerExchange received an invalid return code for an update request for the specified VSAM file.

System Action: PowerExchange rejects the file update request.

User Response: Contact Informatica Global Customer Support.

PWXEDM176417E CICS/VSAM CDC Termination failed. Return code is return_code, Reason code is reason_code, Reason code is reason_code

Explanation: PowerExchange received an unexpected return code for a request to terminate the CICS/VSAM ECCR.

System Action: The ECCR does not terminate if the return code indicates a termination error.

User Response: Contact Informatica Global Customer Support.

PWXEDM176418E CICS/VSAM Change Capture Syncpoint (syncpoint_phase) failed. Reason code is reason_code

Explanation: During syncpoint processing, PowerExchange received a return code that is not valid. This error might occur because the PowerExchange Logger for z/OS is not available.

In this message, syncpoint_phase is one of the following values:

• 1. Phase 1.

• 2. Phase 2.

• E. End UOW.

• R. Rollback.

• V. UOW verification.

System Action: Syncpoint processing fails, and the CICS transaction is backed out.

User Response: For more information about the error, review accompanying messages in the PowerExchange message log.

PWXEDM176419E SHOWCAT for data_set_name {CLUSTER | DATA} failed with RC=return_code

Explanation: When PowerExchange tried to get key details for the base data set for a VSAM path, the VSAM SHOWCAT macro failed with specified return code on the CLUSTER or DATA component entry in the VSAM catalog.

System Action: PowerExchange terminates the Open request for the VSAM file and closes the file.

User Response: Verify that the VSAM path and the associated CLUSTER or DATA component are correctly defined. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR 161

Page 162: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM176420E No DATA component found for File(file_name). DSN is data_set_name

Explanation: When PowerExchange tried to get key details for the base data set for a VSAM path, the VSAM SHOWCAT macro did not return information about the DATA component that is associated with the base CLUSTER.

System Action: PowerExchange terminates the Open request for the VSAM file and closes the file.

User Response: Verify that the VSAM path and associated CLUSTER or DATA component are correctly defined. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176421E Invalid operand. Issue EDMC HELP to display all of the valid command operands.

Explanation: An EDMC transaction was entered with an invalid command operand. Enter HELP to list the valid operands.

System Action: The EDMC transaction terminates.

User Response: Enter one of the valid command operands at a terminal or from the operator console.

PWXEDM176422E Change Capture Initialization failed due to unsupported CICS release (component_level)

Explanation: An attempt was made to initialize the PowerExchange CICS/VSAM ECCR for a CICS Transaction Server version that PowerExchange does not support.

System Action: CICS/VSAM ECCR initialization fails.

User Response: Contact Informatica Global Customer Support.

PWXEDM176423E Registered File(file_name) is a non CICS-Maintained Data Table

Explanation: PowerExchange Open exit processing for the specified VSAM file failed because no CICS-maintained data table exists for it in memory.

System Action: PowerExchange terminates the Open request and closes the file.

User Response: Verify that the VSAM file is correctly defined in CICS and is registered for change data capture.

PWXEDM176424E CLOSE FILE(file_name) failed. EIBRESP=response_code, RESP2=response_code2

Explanation: During Open exit processing, PowerExchange encountered one or more errors that require the specified VSAM file to be closed to prevent change data loss. However, the EXEC CICS CLOSE request encountered an error.

System Action: The VSAM file does not participate in change data capture processing.

User Response: For more information about the errors that require the file to be closed, refer to the PowerExchange messages that precede this one in the PowerExchange message log. You can close the file manually, if necessary. For information about the EIBRESP and RESP2 response codes, see the IBM CICS Transaction Server for z/OS System Programming Reference.

PWXEDM176425W Registered File(file_name) allows read-only access - Change Capture bypassed

Explanation: The specified VSAM file is registered for change data capture but was opened in read-only mode. Because no changes can be written to a read-only file, PowerExchange does not capture changes from it.

System Action: PowerExchange ignores the file and continues change capture processing.

User Response: No response is required.

162 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 163: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM176426E INQUIRE FILE(file_name) failed. EIBRESP=response_code, RESP2=response_code2

Explanation: PowerExchange Open exit processing for the specified VSAM file failed because the EXEC CICS INQUIRE FILE request encountered an error.

System Action: PowerExchange terminates the Open request and closes the file.

User Response: For information about the EIBRESP and RESP2 response codes, see the IBM CICS Transaction Server for z/OS System Programming Reference.

PWXEDM176427E File(file_name) being closed due to ECCR errors. DSN is data_set_name

Explanation: PowerExchange Open exit processing encountered one or more errors that require the specified file to be closed to prevent change data loss.

System Action: PowerExchange terminates the Open request and closes the file.

User Response: For more information about the errors, see the PowerExchange messages that precede this one in the PowerExchange message log.

PWXEDM176428E UOWs were unresolved for Change Capture due to CICS Cold Start

Explanation: After a CICS cold start, PowerExchange found VSAM units of work (UOWs) that were left in an indoubt state from the last CICS termination. You must resolve these indoubt UOWs for the source and target to be consistent.

System Action: CICS startup processing and change capture processing continue.

User Response: Manually resolve the indoubt UOWs by using the PowerExchange Logger RESOLVE_INDOUBT command.

PWXEDM176429W CICS System Log (DFHLOG) log_status and EDM CCERR=CONTinue

Explanation: PowerExchange CICS/VSAM ECCR initialization completed successfully, but the CICS system log is not available. In this situation, CICS cannot back out transactions that abend, and PowerExchange does not apply changes from abended transactions. As a result, the source and target might become inconsistent.

In this message, log_status is one of the following values:

• is disabled

• is dummied

• has failed

• not found

System Action: CICS processing and PowerExchange change data capture processing continue.

User Response: To ensure that the source and target remain consistent, verify that the CICS system log is properly defined. It must not be defined as a dummy log.

PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR 163

Page 164: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM176430E CICS System Log (DFHLOG) log_status and EDM CCERR=ABEND

Explanation: PowerExchange CICS/VSAM ECCR initialization completed successfully, but the CICS system log is not available. In this situation, CICS cannot back out transactions that abend, and PowerExchange does not apply changes from those transactions. As a result, the source and target might become inconsistent.

In this message, log_status is one of the following values:

• is disabled

• is dummied

• has failed

• not found

System Action: PowerExchange issues a request to shut down the CICS region because CCERR=ABEND is specified in the EDMSDIR options module.

User Response: To ensure that the source and target remain consistent, verify that the CICS system log is properly defined. It must not be defined as a dummy log.

PWXEDM176431I Syncpoint processing entered, area value is contents

Explanation: The PowerExchange task-related user exit (TRUE) was invoked during syncpoint processing. The exit dumps the first 64 bytes of the contents of the CICS parameter area, TRWA data area, or TFWA control block to this message for diagnostic use.

In this message, area is one of the following values:

• FUNC

• TFWA control block

• TRWA data area

System Action: CICS processsing continues.

User Response: Send the contents of this message to Informatica Global Customer Support.

PWXEDM176432I CDC processing beginning for UOW, using TFWA contents

Explanation: The PowerExchange task-related user exit (TRUE) was invoked for the first time for a unit of work (UOW). The exit dumps the first 64 bytes of the contents of the TFWA control block to this message for diagnostic use.

System Action: CICS processing continues.

User Response: Send the contents of this message to Informatica Global Customer Support.

PWXEDM176433I CDC captured change_type for file_name, using TFWA contents

Explanation: The CICS/VSAM ECCR captured change data from the specified VSAM file when processing a unit-of-work (UOW). This message provides the first 64 bytes of the contents of the TFWA control block for diagnostic purposes.

In this message, change_type is one of the following values:

• delete

• insert

• update

System Action: Change data capture processing continues.

164 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 165: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Send the contents of this message to Informatica Global Customer Support.

PWXEDM176434W CDC participation allowed for File(file_name) due to AllowRecoveryNone

Explanation: PowerExchange Open exit processing can proceed for the specified nonrecoverable file because the AllowRecoveryNone keyword is specified in the INITPARM statement for the EDMKOPER module. However, this keyword might cause some changes to not be captured.

System Action: Change data capture processing continues.

User Response: Verify that use of the AllowRecoveryNone keyword is required.

PWXEDM176435W CICS/VSAM Change Capture {initialization | termination} completed with warnings

Explanation: CICS/VSAM ECCR initialization or termination completed with one or more warnings.

System Action: CICS processing continues.

User Response: If CICS file-processing errors occur after ECCR termination, restart the CICS region.

PWXEDM176436I Options in effect: ECCR Name=eccr_name, CCERR=option [AllowRecoveryNone]

Explanation: This message is issued during CICS/VSAM ECCR initialization. It reports the ECCR name and the CCERR option that is specified in the EDMSDIR options module. It also includes the "AllowRecoveryNone" keyword if you specified it in the INITPARM statement for EDMKOPER module. This keyword allows nonrecoverable files to participate in change data capture processing.

In this message, option is one of the following CCERR values:

• ABEND

• CONTinue

System Action: Change data capture processing continues.

User Response: No response is required.

PWXEDM176437E CICS/VSAM ECCR Initialization failed

Explanation: CICS/VSAM ECCR initialization failed because PowerExchange encountered one or more errors. The errors might have occurred because PowerExchange could not determine the status of some VSAM files that were open prior to the start of initialization.

System Action: PowerExchange does not capture change data.

User Response: To diagnose the problem, review other messages that were issued during ECCR initialization. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176438E <executing_program> PROGRAM(program_name) EXIT(exit_point) failed. EIBRCODE=X''EIBRCODE_code'', RESP=EIBRESP_code, RESP2=EIBRESP2_code

Explanation: During PowerExchange CICS/VSAM Change Capture processing, the specified program issued an EXEC CICS command request. However, CICS Transaction Server (TS) returned an error. This message provides the CICS TS response codes for the error.

System Action: PowerExchange Change Capture processing ends abnormally.

PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR 165

Page 166: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: To determine the cause of the error, look up the reported EIBRCODE, EIBRESP, and EIBRESP2 response codes for the EXEC CICS command in the IBM CICS TS application development or system programming documentation for the CICS TS version that you are using. Likely causes of the error include:

• A missing load module

• A missing or incorrect program resource definition

• A RACF security rule that prevents access to a requested resource

PWXEDM176439I Program(program_name) Enabled at Exit(exit_point), RESP2=response_code

Explanation: This message reports a CICS RESP2 response code for a program that is installed and enabled at the specified exit point in the CICS Transaction Server region. The response code indicates the status of the program. To determine the cause of the failure, look up the CICS response code in the IBM CICS Application Programming Reference. Then correct the problem and start the ECCR again

User Response: No response is required.

PWXEDM176440E file_id I/O Error, SYNADAF: IBM_error_text

Explanation: PowerExchange received an I/O error when processing the VSAM data set with the specified file ID in the target CICS Transaction Server (TS) region. This message includes the diagnostic information that the SYNADAF analysis macro returned for the error.

System Action: CICS TS continues running.

User Response: Check if the data set that is associated with the specified file ID is accessible and readable in the Time Sharing Option (TSO) environment. If it is not accessible and readable, correct or redefine the data set. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176441I EDMKOVRD CDC Override Options file was found. Processing of Override Statements begins.

Explanation: The PowerExchange CICS/VSAM ECCR has started processing the override options data set that is allocated by the EDMKOVRD DD statement in the CICS startup JCL in the CICS Transaction Server (TS) region. This data set contains override options for change data capture from VSAM data sets.

User Response: No response is required.

PWXEDM176442I EDMKOVRD DD Dummy sysin file was found. No CDC Override Options will be processed.

Explanation: No override options data set was allocated by the EDMKOVRD DD statement in the CICS startup JCL in the CICS Transaction Server (TS) region. No PowerExchange override options are active for VSAM CDC.

User Response: No response is required.

PWXEDM176443I EDMKOVRD Override dataset: data_set_name(member) was opened.

Explanation: The PowerExchange CICS/VSAM ECCR has issued an OPEN request for the override options data set that is allocated by the EDKOVRD DD statement in the CICS startup JCL. This data set contains override options for VSAM CDC.

User Response: No response is required.

166 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 167: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM176444I EDMKOVRD Open Error on Override dataset: data_set_name(member) RC=(return_code)

Explanation: An I/O error occurred when the PowerExchange CICS/VSAM ECCR was processing the specified override options data set that is allocated by the EDMKOVRD DD in the target CICS TS region.

System Action: CICS TS continues running.

User Response: Check if the specified data set is accessible and readable in the Time Sharing Option (TSO) environment. If it is not accessible and readable, correct or redefine the data set. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176445I CDC Override Options were updated mm/dd/yy at hh:mm:ss from data_set_name(member)

Explanation: PowerExchange updated or refreshed the override options for VSAM CDC in the specified data set at the given date and time. This data set was allocated by the EDMKOVRD DD in the CICS startup JCL in the CICS Transaction Server region.

User Response: No response is required.

PWXEDM176446W CDC Override Options contain errors. Make corrections where indicated.

Explanation: The PowerExchange CICS/VSAM ECCR detected a syntax error when processing the override options data set that is allocated by the EDMKOVRD DD in the CICS startup JCL in the CICS Transaction Server (TS) region.

System Action: CICS TS continues running.

User Response: Check the syntax of the statements in the EDMKOVRD override options data set. The beginning of a syntax error in a statement is indicated by an asterisk on the next line. Also, review the syntax errors that are reported in the CICS console log. Then correct any override option statement that is not valid and either restart CICS or issue the EDMC REFRESH command. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176447I EDMKOVRD DD not found in CICS startup. CICS/VSAM CDC Override Options not processed.

Explanation: The PowerExchange CICS/VSAM ECCR did not find the override options data set that is allocated by the EDMKOVRD DD statement in the CICS startup JCL in the CICS TS region. The ECCR uses the default values for the override options for VSAM change data capture.

User Response: No response is required.

PWXEDM176448I EDMKOVRD Override dataset: data_set_name(member) was closed.

Explanation: An I/O error occurred when the PowerExchange CICS/VSAM ECCR was processing the specified override options data set in the target CICS Transaction Server (TS) region. The data set was closed.

System Action: CICS TS continues running.

User Response: Check if the specified data set is accessible and readable in the Time Sharing Option (TSO) environment. If it is not accessible and readable, correct or redefine the data set. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176449I EDMKOVRD Close Error on Override dataset: data_set_name(member) RC=(return_code)

Explanation: An I/O error occurred when the PowerExchange CICS/VSAM ECCR was processing the specified override options data set in the target CICS Transaction Server (TS) region. An attempt to close the data set resulted in an error.

System Action: CICS TS continues running.

PWXEDM176400E to PWXEDM176455I: CICS/VSAM ECCR 167

Page 168: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Check if the specified data set is accessible and readable in the Time Sharing Option (TSO) environment. If it is not accessible and readable, correct or redefine the data set. If the problem persists, contact Informatica Global Customer Support.

PWXEDM176450I CICS/VSAM Change Capture is status for VSAM_source_type

Explanation: This message reports whether the PowerExchange CICS/VSAM Change Capture is active or inactive for the specified VSAM source type. The VSAM_source_type variable represents one of the following source types: VSAM ESDS, VSAM KSDS, or VSAME RRDS files or data sets, or CICS Maintained Data Tables.

User Response: No response is required.

PWXEDM176451I Change Capture disallowed for File(file_id) due to CAPTURE_vsam_dataset_type=OFF CDC Override Option

Explanation: PowerExchange will not capture change data from VSAM data sets that are associated with the specified CICS/VSAM file ID and that are of the data set type that is specified in a CAPTURE_vsam_dataset_type=OFF override option in the EDMKOVRD DD statement in the CICS region startup JCL or in the data set to which this DD statement points. You can set any of the following options to OFF to disable CDC for a specific VSAM data set type: CAPTURE_ESDS, CAPTURE_KSDS, CAPTURE_RRDS, or CAPTURE_CMDT.Note: For the CAPTURE_ESDS option, the default value is OFF.

User Response: No response is required.

PWXEDM176452I Change Capture disallowed for File(file_id) due to NOCAPTURE CDC Override Option

Explanation: PowerExchange will not capture change data from a VSAM data set that is associated with the specified CICS/VSAM file ID because the DSN=dataset_name,NOCAPTURE override option is specified in the EDMKOVRD DD statement in the CICS region startup JCL or in the data set to which this DD statement points. This option disables change capture for a specific VSAM data set and its CICS file ID.

User Response: No response is required.

PWXEDM176453I {Registered|Excluded} File(file_id) is associated with DSN(hlq.dataset_name)

Explanation: This message reports the VSAM data set that is associated with a file for which CDC processing is disallowed. The message also indicates whether the data set is registered for CDC or not registered (excluded). CDC processing is disallowed for the file and data set because either the CAPTURE_vsam_dataset_type=OFF or DSN=dataset_name,NOCAPTURE override option is specified in the EDMKOVRD DD statement in the CICS startup procedure or in the data set to which this DD statement points. This message accompanies message PWXEDM176451I or PWXEDM176452I.

User Response: No response is required.

PWXEDM176454W CDC CICS Exit program(program_name) at CICS Exit point(exit_point) is not defined as order

Explanation: This message warns that the specified CICS/VSAM CDC exit program is not installed in the recommended precedence order at the CICS exit point. The order value is either "First" or "Last," depending on when the exit program was enabled at the specified exit point. Another product or program might have installed a program to run at the same exit point prior to the EDMKOPER program. The EDMKOPER program is defined in the CICS startup PLTPI table and activates the CICS/VSAM Change Capture exit programs at CICS initialization.

System Action: CICS TS continues running.

168 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 169: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Check the order of entries in the CICS PLTPI for programs that are getting invoked after the EDMKOPER program entry. These programs might install other programs at the specified exit point, causing conflicts with the CICS/VSAM ECCR order requirements.

PWXEDM176455I CDC CICS Exit program(program name) at CICS Exit point(exit_point) is now defined as order

Explanation: A PowerExchange CICS/VSAM CDC exit program was not defined in the correct precedence order at the CICS exit point. To avoid potential CDC issues, the appropriate EXEC CICS system programming interface (SPI) commands were issued to correct the order of the program dynamically. This message identifies the new order, which is either "First" or "Last."

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCRPWXEDM177012I ECCR STATUS: LAST DB2 READ LOC rba_or_lrsn.data_sharing_member_id.sequence_number

OLDEST OPEN UOW {urid.data_sharing_member_id|*NONE*}

Explanation: This message reports the RBA or LRSN location of the last DB2 log record that the DB2 ECCR read and the URID of the oldest open UOW at that location in the DB2 log. In a data-sharing environment, the data-sharing member ID is included in both values. This message is issued when the DB2 ECCR ends.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177013I LOGGER: LAST DB2 READ LOC rba_or_lrsn OLDEST OPEN UOW uowid.data_sharing_member_id

Explanation: This message reports the RBA or LRSN of the last DB2 log record read and the oldest open UOW that the PowerExchange Logger sent to the ECCR for restart processing. This message is issued when the DB2 ECCR ends.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177016E TABLE creator.table_name NOT DEFINED.

Explanation: During a DB2 for z/OS ECCR restart, the ECCR tried to find the specified table. However, the table is not defined to DB2.

System Action: The ECCR restart fails.

User Response: To diagnose the error, review the other messages that are associated with the failure. Then try to restart the ECCR again.

PWXEDM177017I TABLE creator.table_name EDITPROC procedure_name UPDATED.

Explanation: During a DB2 for z/OS ECCR restart, the ECCR encountered an updated EDITPROC exit routine for the specified table.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 169

Page 170: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177018E OPEN FAILED FOR DDNAME PWXTRACE

Explanation: The DB2 ECCR could not open the data set with a DD name of PWXTRACE.

System Action: The DB2 ECCR abends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM177019E CLOSE FAILED FOR DDNAME PWXTRACE

Explanation: During termination, the DB2 ECCR could not close the data set with a DD name of PWXTRACE.

System Action: The DB2 ECCR abends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM177020E STORAGE OBTAIN/RELEASE FAILED

Explanation: A GETMAIN error occurred. The DB2 ECCR was unable to obtain or release storage.

System Action: The DB2 ECCR abends.

User Response: Collect all available information about the error. Contact Informatica Global Customer Support.

PWXEDM177021I LEVEL/LVL not specified.

Explanation: In a DB2 for z/OS ECCR TR command, the LEVEL, or LVL, keyword is required but is not specified. The command is intended for use by Informatica Global Support.

System Action: The command is not executed.

User Response: Correct the command input by adding the LEVEL keyword.

PWXEDM177022I ID exceeds 16 characters.

Explanation: In a DB2 for z/OS ECCR TR command, the ID keyword exceeds the maximum length of 16 characters. The command is intended for use by Informatica Global Support.

System Action: The command is not executed.

User Response: Correct the command input by entering an ID value of 16 characters or less.

PWXEDM177023I internal error processing ID

Explanation: An internal error occurred when PowerExchange was processing the ID value in a DB2 for z/OS ECCR TR command.

System Action: The command is not executed.

User Response: Contact Informatica Global Customer Support.

PWXEDM177024I unrecognized text after ID

Explanation: When processing a DB2 for z/OS ECCR TR command, PowerExchange found some unrecognized text after the ID keyword. The command input is not valid. This command is intended for use by Informatica Global Support.

System Action: The command is not executed.

User Response: Correct the command input.

170 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 171: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177025I LEVEL greater than one character.

Explanation: In a DB2 for z/OS TR command, the LEVEL keyword must specify only one numeric character. However, it specifies multiple numeric characters. The command is intended for use by Informatica Global Support.

System Action: The command is not executed.

User Response: Correct the command input by specifying a single numeric character in the LEVEL keyword.

PWXEDM177026I LEVEL not numeric.

Explanation: In a DB2 for z/OS ECCR TR command, the LEVEL keyword specifies a non-numeric value. The LEVEL value must be a single digit in the range 0 through 9. This command is intended for use by Informatica Global Support.

System Action: The command is not executed.

User Response: Correct the command input by specifying a single digit for the LEVEL keyword.

PWXEDM177030E CAPTURE PROGRAM error_response

Explanation: The DB2 ECCR encountered the error that is identified in a preceding message. This message provides additional information about the error.

System Action: The DB2 ECCR reacts in one of the following ways, depending on the reported error response:

• ATTEMPTS TO CONTINUE. The DB2 ECCR stops processing the record or operation that caused the error. Then the ECCR tries to process the next log record or the next ST definition.

• ABENDS. The DB2 ECCR abends because the error is too severe to continue.

• ABENDS with PERMIL=0. The DB2 ECCR abends because the REPL2CTL file contains or defaults to the EC PERMIL=0 control statement.

• ABENDS‑PERMIL=THRESHOLD IS EXCEEDED. The DB2 ECCR abends because the number of errors that occurred exceeds the maximum number of errors that are specified in the EC PERMIL control statement in the REPL2CTL file.

User Response: Depending on the error response and system action, respond in one of the following ways:

• ATTEMPTS TO CONTINUE. No response is required.

• ABENDS. Use the information in the associated messages to determine your response.

• ABENDS with PERMIL=0. Set the EC PERMIL control statement in the REPL2CTL file to a value greater than 0 to allow the DB2 ECCR to skip the log records that result in errors. Then restart the ECCR.

• ABENDS‑PERMIL= THRESHOLD IS EXCEEDED. Increase the EC PERMIL value in the REPL2CTL file. Then restart the ECCR. The larger EC PERMIL value enables the ECCR to tolerate more errors and 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.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 171

Page 172: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing continues. However, the DB2 ECCR might handle some errors without providing the associated error messages.

User Response: No response is required.

PWXEDM177036E INVALID CALL FUNCTION

Explanation: The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177037E INVALID CPOOL-ID

Explanation: The DB2 ECCR found an invalid CPOOL ID. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177038E INVALID CPOOL CELL-ADDRESS

Explanation: The DB2 ECCR found an invalid CPOOL cell address. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177039E INVALID CPOOL-ID IN CELL

Explanation: The DB2 ECCR found an invalid CPOOL ID in the cell. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177040E AREA TOO LARGE FOR CPOOL SERVICES

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177041E INVALID CHAIN OF CELL ELEMENTS

Explanation: The DB2 ECCR found an incorrect sequence of cell elements. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

172 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 173: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177042E INVALID CHAIN OF CELL ELEMENTS

Explanation: The DB2 ECCR found an incorrect sequence of cell elements. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177043E INTERNAL ERROR: INVALID CALL‑FUNCTION

Explanation: The DB2 ECCR encountered an invalid call function. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177044E INTERNAL ERROR: DUPLICATE HASH‑ENTRIES

Explanation: The DB2 ECCR found duplicate entries in the hash table. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177045E INTERNAL ERROR: POSITION NOT ESTABLISHED

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177046I CAPTURE PROGRAM ACKNOWLEDGES AN MVS STOP COMMAND

Explanation: The DB2 ECCR issues this message to acknowledge that an MVS STOP eccr_task command was entered.

System Action: The DB2 ECCR stops.

User Response: No response is required.

PWXEDM177047I CAPTURE PROGRAM ACKNOWLEDGES AN MVS 'MODIFY REFRESH' COMMAND

Explanation: The DB2 ECCR issues this message to acknowledge that an MVS MODIFY eccr_job, REFRESH command was entered. This command causes the DB2 ECCR to update its control information based on the current contents of the PowerExchange repository.

System Action: The DB2 ECCR refreshes its control information and continues processing.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 173

Page 174: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177048I CAPTURE PROGRAM ACKNOWLEDGES A QUIESCE COMMAND

Explanation: The DB2 ECCR issues this message to acknowledge that an MVS MODIFY eccr_job, QUIESCE command was entered.

System Action: The DB2 ECCR stops in a controlled manner after processing in-flight UOWs.

User Response: No response is required.

PWXEDM177049E QEDIT MACRO FAILED

Explanation: An internal error caused the QEDIT macro to fail.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then contact Informatica Global Customer Support.

PWXEDM177050E QEDIT MACRO FAILED

Explanation: An internal error caused the QEDIT macro to fail.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then contact Informatica Global Customer Support.

PWXEDM177051E INTERNAL ERROR ‑ UNEXPECTED VALUE IN R2PMOD FIELD

Explanation: An internal error occurred. The DB2 ECCR found an incorrect value in the R2PMOD field.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then contact Informatica Global Customer Support.

PWXEDM177052E UNSUPPORTED MVS COMMAND

Explanation: The DB2 ECCR does not support the MVS command that was entered.

System Action: The DB2 ECCR ignores the command and continues processing.

User Response: Verify that the command was entered correctly or enter another command that the DB2 ECCR supports. For more information about supported DB2 ECCR commands, see the PowerExchange Command Reference.

PWXEDM177053E PARAMETER ON MODIFY COMMAND IS MISSING

Explanation: An MVS MODIFY command for the DB2 ECCR was entered without all of the required parameters.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

User Response: Enter the MVS MODIFY command again with all of the required parameters. For more information about DB2 ECCR commands and parameters, see the PowerExchange Command Reference.

PWXEDM177054E PARAMETER ON MODIFY COMMAND IS TOO SHORT

Explanation: An MVS MODIFY command for the DB2 ECCR was entered with a parameter entry that is too short. The parameter might not be complete.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

174 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 175: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Enter the MVS MODIFY command again with a complete parameter specification. For more information about DB2 ECCR commands and parameters, see the PowerExchange Command Reference.

PWXEDM177055E PARAMETER ON MODIFY COMMAND IS TOO LONG

Explanation: An MVS MODIFY command for the DB2 ECCR was entered with a parameter specification that is too long.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

User Response: Enter the MVS MODIFY command again with the parameter correctly specified. For more information about DB2 ECCR commands and parameters, see the PowerExchange Command Reference.

PWXEDM177056E SUPPORTED PARMS FOR MODIFY COMMAND ARE "DI", "RE", "URID", "TERM", AND "QU"

Explanation: An MVS MODIFY command was entered for the DB2 ECCR with an invalid ECCR parameter.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

User Response: Enter the MVS MODIFY command again with one of the valid ECCR parameters that are identified in the message text. For more information about DB2 ECCR commands and parameters, see the PowerExchange Command Reference.

PWXEDM177057E 1ST PARAMETER OF MODIFY COMMAND IS INVALID OR NOT FOLLOWED BY A COMMA

Explanation: In an MVS MODIFY command for the DB2 ECCR, the first parameter is not valid or is not followed by a comma.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

User Response: Enter the MVS MODIFY command again with the correct parameter syntax. For more information about DB2 ECCR commands and parameters, see the PowerExchange Command Reference.

PWXEDM177058E "DISPLAY" PARAMETER IS FOLLOWED BY ONE OR MULTIPLE INVALID PARAMETERS

Explanation: AN MVS MODIFY command for the DB2 ECCR contains the ECCR DISPLAY, or DI, parameter followed by one or more parameters that the ECCR does not support.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

User Response: Enter the MVS MODIFY command again with only supported ECCR parameters. For more information about DB2 ECCR commands and parameters, see the PowerExchange Command Reference.

PWXEDM177059E "TERM" PARAMETER IS INVALID, MUST BE A 24-CHARACTER HEXADECIMAL NUMBER

Explanation: An invalid unit‑of‑recovery ID (URID) or unit‑of‑work ID (UOWID) value was entered in the DB2 ECCR TERM command. The URID or UOWID must be a 24-character hexadecimal value that follows TERM, for example:

F eccr_task_name,TERM,00000000000000123AB0C000System Action: The DB2 ECCR ignores the TERM command.

User Response: Enter the TERM command again with a URID or UOWID value in the correct hexadecimal format. For more information, see the PowerExchange Command Reference.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 175

Page 176: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177060E INTERNAL ERROR: RELEASE FUNCTION NOT PERMITTED

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177061W CAPTURE PROGRAM NOT READY TO PROCESS MODIFY COMMANDS

Explanation: An MVS MODIFY command was entered, but the current DB2 ECCR status does not allow processing of MODIFY commands.

System Action: The DB2 ECCR ignores the MODIFY command and continues processing.

User Response: Enter the MODIFY command later when the DB2 ECCR can process it.

PWXEDM177062W CAPTURE PROGRAM WAITING FOR DB2 CONNECTION

Explanation: The DB2 ECCR cannot process an ECCR command because it is waiting for the connection to DB2 to complete.

System Action: The DB2 ECCR ignores the command and waits for the connection to DB2 to complete.

User Response: If the connection to DB2 takes an excessive amount of time to complete, determine the cause of the delay. Otherwise, wait until the connection is complete and then enter the command again.

PWXEDM177064W CAPTURE PROGRAM IN START PHASE

Explanation: The DB2 ECCR has not completed initialization processing. Therefore, it cannot process the ECCR command that was entered.

System Action: The DB2 ECCR ignores the command.

User Response: Enter the command after the DB2 ECCR completes the initialization phase.

PWXEDM177065W CAPTURE PROGRAM IN COLD‑START PHASE

Explanation: The DB2 ECCR has not completed cold‑start processing. Therefore, it cannot process the ECCR command that was entered.

System Action: The DB2 ECCR ignores the command.

User Response: Enter the command after the DB2 ECCR completes the cold start.

PWXEDM177066W CAPTURE PROGRAM IN SPECIAL-START PHASE

Explanation: The DB2 ECCR has not completed special-start processing. Therefore, it cannot process the ECCR command that was entered.

System Action: The DB2 ECCR ignores the command.

User Response: Enter the command after the DB2 ECCR completes the special start.

176 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 177: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177067W CAPTURE PROGRAM IN REFRESH PHASE

Explanation: The DB2 ECCR has not completed refresh processing. Therefore, it cannot process the ECCR command that was entered.

System Action: The DB2 ECCR ignores the command.

User Response: Enter the command after the DB2 ECCR completes refresh processing.

PWXEDM177068W MODIFY COMMAND REJECTED

Explanation: The DB2 ECCR rejected an MVS MODIFY command.

System Action: The DB2 ECCR ignores the MODIFY command.

User Response: Check other messages associated with this error to determine why the DB2 ECCR rejected the MODIFY command. Then correct the problem and enter the command again.

PWXEDM177069E UNEXPECTED RETURN CODE FROM 'ENQ' MACRO ‑ RC IS IN R8

Explanation: The ENQ macro sent a nonzero return code to the DB2 ECCR. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177070E CAPTURE PROGRAM WITH NAME=name IS ALREADY EXECUTING

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

System Action: The second DB2 ECCR with the same name abends.

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

PWXEDM177071E NUMBER OF TRACE ELEMENTS IS INVALID

Explanation: An internal error occurred. The DB2 ECCR found an incorrect number of internal trace elements.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177072E LENGTH OF TEXT TO BE TRACED IS INVALID

Explanation: An internal error occurred. The DB2 ECCR determined that the length of the text to be traced is not valid.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 177

Page 178: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177073E LENGTH OF AREA TO BE TRACED IS INVALID

Explanation: An internal error occurred. The DB2 ECCR determined that the length of the area to be traced is not valid.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177074E OPEN FAILURE FOR REPL2CTL

Explanation: The DB2 ECCR could not open the REPL2CTL control data set.

System Action: The DB2 ECCR abends.

User Response: To diagnose the error, see other MVS-issued messages that contain additional information about the error. Then correct the problem and run the ECCR again.

PWXEDM177075E REPL2CTL FILE IS EMPTY

Explanation: The DB2 ECCR REPL2CTL file does not contain the required control statements.

System Action: The DB2 ECCR abends.

User Response: Add the required control statements to the REPL2CTL file and run the job again.

PWXEDM177076E ERRORS IN REPL2CTL RECORDS

Explanation: The DB2 ECCR detected one or more errors in the control statements in the REPL2CTL file.

System Action: The DB2 ECCR writes a detailed description of the errors in the REPL2PRT file and then abends.

User Response: To diagnose the error, review the error messages in the REPL2PRT file. Then correct the problems and run the job again.

PWXEDM177077E ZERO CR RECORDS IN REPL2CTL FILE

Explanation: An internal error related to the REPL2CTL data set occurred.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177078E USER SPECIFIED CR RECORD NOT SUPPORTED

Explanation: A user-specified CR record occurs in the REPL2CTL file but is not supported.

System Action: The DB2 ECCR abends.

User Response: To bypass the error, delete the CR record from the REPL2CTL file. Then start the DB2 ECCR again.

PWXEDM177079E USER SPECIFIED ST RECORD NOT SUPPORTED

Explanation: A user-specified ST record occurs in the REPL2CTL file but is not supported.

System Action: The DB2 ECCR abends.

User Response: To bypass the error, delete the ST record from the REPL2CTL file. Then start the DB2 ECCR again.

178 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 179: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177080E INTERNAL ERROR: NO SPC DEFINITION FOR catalog_table_name

Explanation: An internal error occurred. The specified table is identified as a DB2 catalog table of interest to the DB2 ECCR but is not on the internal list of allowable catalog tables.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including any dumps.

PWXEDM177082E OPEN OF REPL2OPT HAS FAILED

Explanation: The DB2 ECCR could not open the REPL2OPT file.

System Action: The DB2 ECCR abends.

User Response: To diagnose the error, review related MVS messages for this error. Then correct the problem and run the job again.

PWXEDM177083E ERRORS IN REPL2OPT RECORDS

Explanation: The DB2 ECCR detected one or more errors in the configuration statements in the REPL2OPT file.

System Action: The DB2 ECCR writes a detailed description of the errors to the REPL2PRT file and then abends.

User Response: To diagnose the error, review the error messages in the REPL2PRT file. Then correct the problem and run the job again.

PWXEDM177084I program_name capture statistics at timestamp

Explanation: This message introduces the following capture statistics that the specified DB2 ECCR program reported at the specified date and time (yyyy-mm-dd hh.mm.ss):

• DB2 Log Location - RBA of the current location of ECCR processing in the DB2 log.

• DB2 Log Timestamp - The timestamp of the last DB2 log record that the ECCR read.

• Current Delay - The time, in seconds, that it currently takes the ECCR to process a change record after the record is written to the DB2 log.

• Average Delay - The average time, in seconds, that it takes the ECCR to process a change record during the statistics reporting interval.

• DB2 log records - The number of log records that the ECCR read - total, during the reporting interval , and per second.

• EDM records - The number of EDM records that were processed - total, during the reporting interval, and per second.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 179

Page 180: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177085I {ST|SQ} Display

Explanation: This message introduces DB2 for z/OS ECCR statistics report that is generated at the reporting interval that is set in the STAT statement of the REPL2OPT DD data set or in response to an ECCR DISPLAY command. The type of statistics depends on how you set the LEV parameter in the STAT statement or on the parameters that you specify in the DISPLAY command. If you specify STAT LEV=ST statement or DISPLAY,ST command, this message shows the ST Display report, which provides counts of change records that the ECCR read from the DB2 log (total, for the reporting interval, and average per second) by source table. If you specify the STAT LEV=SQ statement or DISPLAY,SQ command, this message shows the SQ Display report, which provides counts of change records that the ECCR sent to the PowerExchange Logger for z/OS, by source table and record type. The SQ counts are for low-level types of database operations that indicate logging activity, not for SQL INSERT, UPDATE, and DELETE operations.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177086I No {ST|SQ} activity

Explanation: A DB2 for z/OS ECCR DISPLAY command that uses the ST or SQ parameter was issued without the ALL parameter. The ECCR found no change activity for which to report ST or SQ statistics in message PWXEDM177085I.

System Action: Processing continues.

System Action: No response is required.

PWXEDM177093E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177094E INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177095E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

180 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 181: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177099E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177100E INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177101E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177105E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177106E INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177107E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177114E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 181

Page 182: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177115E INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name

Explanation: The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177116E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177123E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177124E INTERNAL ERROR - INVALID VALUE IN FUN2 FOR MODULE module_name

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177125E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177129E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

182 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 183: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177130E INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name

Explanation: The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177131E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177132E INTERNAL ERROR - INVALID CALL FUNCTION FOR MODULE module_name

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177133E INTERNAL ERROR - INVALID SELECT-ID FOR MODULE module_name

Explanation: The DB2 ECCR found an invalid select ID for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177134E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177135E CAF CONNECT ERROR. RC=return_code RSNC=reason_code CN=connect_name

Explanation: The DB2 ECCR could not connect to DB2 by using the DB2 Call Attach Facility (CAF) and the specified connect name. This message includes the error return code and reason code.

System Action: The DB2 ECCR abends.

User Response: For a description of the return code and reason code, see the IBM DB2 messages and codes documentation. Then try to correct the problem and run the job again.

PWXEDM177136E CAF OPEN ERROR. RC=return_code RSNC=reason_code PLAN=plan_name

Explanation: The DB2 ECCR issued a DB2 Call Attach Facility (CAF) OPEN call. The OPEN call failed. CAF and DB2 provide the return code and the reason code for the failure.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 183

Page 184: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR abends.

User Response: For a description of the return code and reason code, see IBM DB2 messages and codes documentation. Use 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, collect all available information about the error and contact Informatica Global Customer Support.

PWXEDM177137I DB2_command

Explanation: The DB2 ECCR issued the specified DB2 command. The command response follows.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177138E IFI COMMAND ERROR. IFCARC1=return_code1 IFCARC2=return_code2

Explanation: While issuing a DB2 command through the instrumentation facility interface (IFI), the DB2 ECCR encountered a DB2 error related to an unrecognized column type. This messages includes the return codes from the IFCARC1 and IFCARC2 fields in the IFI Communication Area (IFCA).

System Action: The DB2 ECCR ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177141E CAPTURE PGM CAN NOT OBTAIN THE ID OF THE CURRENT DB2 SERVER

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

System Action: The DB2 ECCR abends.

User Response: To determine the cause of the problem, see the other error messages associated with this error. Correct the problem, and run the job again.

PWXEDM177142E SQL ERROR requesting {CURRENT SERVER | PRODUCTID_EXT | CATALOG_LEVEL}

Explanation: The DB2 for z/OS ECCR encountered an SQL error when requesting the specified special register or global variable value. The value can be the current DB2 server location, extended product identifier of the database manager, or catalog level.

System Action: The ECCR ends abnormally.

User Response: To determine the cause of the problem, see the associated messages that provide more detail about the error. Then try to correct the error and run the job again.

PWXEDM177143E ERROR IN DB2 COMMIT PROCESSING

Explanation: The DB2 ECCR could not process a DB2 COMMIT command. The DB2 ECCR issues other messages with more detailed information about this error.

System Action: The DB2 ECCR abends.

User Response: To diagnose the problem, see the other messages associated with this error. Then try to correct the problem and run the job again.

PWXEDM177144E ERROR IN DB2 ROLLBACK PROCESSING

Explanation: The DB2 ECCR could not process a DB2 rollback. The DB2 ECCR issues other messages with more detailed information about this error.

184 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 185: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR abends.

User Response: To diagnose the problem, see the other messages associated with this error. Then try to correct the problem and run the job again.

PWXEDM177145E ROLLBACK FAILED

Explanation: The DB2 ECCR could not complete DB2 rollback processing. The DB2 ECCR issues other messages with more detailed information about this error.

System Action: The DB2 ECCR abends.

User Response: To diagnose the problem, see the other messages associated with this error. Then try to correct the problem and run the job again.

PWXEDM177146E COMMIT PROCESSING FAILED

Explanation: The DB2 ECCR could not process a DB2 COMMIT command. The DB2 ECCR issues other messages with more detailed information about this error.

System Action: The DB2 ECCR abends.

User Response: To diagnose the problem, see the other messages associated with this error. Then try to correct the problem and run the job again.

PWXEDM177149I DB2 CAPTURE PERFORMS A ROLLBACK

Explanation: The DB2 ECCR is performing DB2 rollback processing.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177150I Connected to DB2 subsystem [group.]ssid

Explanation: The DB2 ECCR connected to the specified DB2 subsystem. If the subsystem is a member of a data sharing group, the message includes the group name.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177151I ISSUING AN SQL ROLLBACK

Explanation: The DB2 ECCR issued a request for rollback processing.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177152E DB2 Vv.r.m is not supported. The {minimum | maximum} supported level is Vv.r.m.

Explanation: PowerExchange does not support your DB2 version.release.modification level. If your DB2 level is too old, this message shows the minimum DB2 level that PowerExchange supports. If your DB2 release level is too recent, this message shows the maximum DB2 level that PowerExchange supports.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 185

Page 186: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177154E DB2 catalog level v.r.m not supported. Maximum supported is v.r.m.

Explanation: The DB2 for z/OS ECCR initialized against an unsupported DB2 catalog version. This message reports the unsupported DB2 version.release.modification level that was detected and the latest DB2 level that the ECCR supports.

System Action: The DB2 ECCR ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177155I DB2 {DSN6SPRM} configuration parameter {CATALOG|RESTRICT_ALT_COL_FOR_DCC} is 'value'

Explanation: This message reports the value of one of the following DB2 for z/OS subsystem configuration parameters:

• CATALOG. Specifies the high-level qualifier for the DB2 catalog table spaces.

• RESTRICT_ALT_COL_FOR_DCC. Controls whether certain table alterations can be performed on tables with the DATA CAPTURE CHANGES attribute. For more information about this parameter, see IBM DB2 documentation. If this parameter is set to YES, you might need to COLD start the DB2 ECCR after DB2 is upgraded. For more information, see the topics on migrating to a new DB2 version in the CDC Guide for z/OS.

DSN6SPRM is a DB2 macro.

System Action: Processing continues.

User Response: No action is required unless you need to change the setting for some reason.

PWXEDM177163E DB2/CAF OPEN ERROR - RC/RSNC=rc/reason

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

System Action: The DB2 ECCR abends.

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

PWXEDM177164E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The DB2 ECCR encountered an SQL operation error while accessing the specified table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177165E LOG BUFFER-FLUSHING SUBTASK ABENDS

Explanation: A DB2 ECCR subtask is abending.

System Action: The subtask abends.

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

PWXEDM177166E LOG BUFFER-FLUSHING SUBTASK ABENDS

Explanation: A DB2 ECCR subtask is abending.

186 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 187: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The subtask abends.

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.

PWXEDM177167I SEE DB2 MESSAGES AND CODES FOR AN EXPLANATION OF THE RSNC

Explanation: A DB2 ECCR subtask encountered a DB2 related problem.

System Action: The subtask abends.

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.

PWXEDM177168E LOG BUFFER-FLUSHING SUBTASK ABENDS

Explanation: A DB2 ECCR subtask is abending.

System Action: The subtask abends.

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

PWXEDM177169E INTERNAL ERROR: CONSTANT TO BE CONVERTED IS TOO LONG

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177170E INTERNAL ERROR: X029166 IS CALLED FOR AN UN-EXPECTED CONVERSION TYPE

Explanation: The DB2 ECCR found an incorrect conversion type. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177171E SQL ERROR: OPERATION=operation TABLE=table

Explanation: The specified DB2 ECCR SQL operation encountered an error when working with the specified table.

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

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.

PWXEDM177172E SQL-ERROR WHILE ATTEMPTING TO CONVERT A USER-PROVIDED DEFAULT VALUE

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

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

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 187

Page 188: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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.

PWXEDM177174E ERROR: LOG POSITION DOES NOT EXIST FOR 'NEXT' CALL

Explanation: An internal error occurred. The DB2 ECCR tried to locate a nonexistent position in the DB2 logs.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177194E INTERNAL ERROR: LOG POSITION IS NOT SET

Explanation: An internal error occurred. The DB2 ECCR cannot determine where to start reading the DB2 log because a log starting position is not set.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177195E INTERNAL ERROR OF LOG READ MODULES

Explanation: The DB2 ECCR encountered an internal error while using the log read modules.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177196W TRACE(MONITOR) CLASS(1) IS INACTIVE

Explanation: The DB2 ECCR issued an IFCID 306 READS call but received reason code x'00E60832'. This reason code indicates that the IFCID required for the READS call is not active. The IFCID is usually activated when the DB2 ECCR initializes and issues the DB2 'START MONITOR(TRACE) CLASS(1)' command. In this case, another DB2 command might have stopped the trace.

System Action: When the DB2 ECCR detects this condition, it issues this message and restarts the trace.

User Response: No response is required because the DB2 ECCR usually restarts the required trace. If the ECCR cannot restart the trace, it abends.

PWXEDM177198E PROPER DB2 AUTHORIZATION MISSING TO READ DB2 LOG WITH IFI READS CALLS

Explanation: The DB2 ECCR cannot read the DB2 log. The ECCR might not have the DB2 privileges that are required to issue IFI READS calls.

System Action: The DB2 ECCR abends.

User Response: Grant the MONITOR2 privilege to the DB2 authorization ID that the DB2 ECCR uses. Then run the job again.

PWXEDM177199E INTERNAL ERROR: IFI CALL WITH WQALMODF ISSUED WITHOUT RELEASING PREVIOUS POSITION

Explanation: The DB2 ECCR encountered an internal error. Possibly, the DB2 ECCR issued an incorrect sequence of IFI READS calls when reading the DB2 log.

System Action: The DB2 ECCR abends.

188 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 189: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177200E INTERNAL ERROR: IFI CALL WITH WQALMODN ISSUED WITHOUT HAVING AN IFI POSITION

Explanation: The DB2 ECCR encountered an internal error. Possibly, the DB2 ECCR issued an incorrect sequence of IFI READS calls when reading the DB2 log.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with a complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177201E INTERNAL ERROR: UNEXPECTED IFI REASON CODE IN IFCA FOR COMPRESSED DATA

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177202E RETRIES OF IFI READS CALL NOT SUCCESSFUL

Explanation: The DB2 ECCR could not read the DB2 archive log by using DB2 IFI READS calls. Based on the IFI return code and reason code, the DB2 ECCR attempted to retry the IFI READS calls ten times. However, none of the retries were successful. This problem is caused by a DB2 error or a DB2 ECCR logic error.

System Action: The DB2 ECCR abends.

User Response: Collect all available information about the error. You can find the data set name of the unavailable DB2 log data set in the JESMSGLG print file of the DB2 master address space. Then contact Informatica Global Customer Support.

PWXEDM177211I REFRESH now pending due to DDL changes.

Explanation: The DB2 for z/OS ECCR finished processing DDL changes for a DB2 unit of recovery (UR). The ECCR used DB2 object filtering to reduce the volume of change records returned from the DB2 IFI 306 READS routine. During capture processing, the ECCR determined that the DB2 list of objects for filtering changed. As a result, the ECCR initiated a REFRESH operation to use the updated list.

System Action: The ECCR initiates REFRESH processing

User Response: No response is required.

PWXEDM177212I DB2 IFI306 WQLS list entry count exceeded. n entries present. The DB2 limit is 50,000.

Explanation: The DB2 for z/OS ECCR is capturing changes for more tables than are allowed in the DB2 IFI 306 object filtering list. The DB2 object filtering list can contain no more than 50,000 objects.

System Action: ECCR processing continues but does not use DB2 object filtering to reduce the volume of change records. CPU consumption might increase.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 189

Page 190: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177220E Error processing DDL in DB2 UR eccr_description_of_urid.

Explanation: The DB2 for z/OS ECCR encountered an error while processing a DDL operation in the specified DB2 unit of recovery (UR). This message includes the ECCR description of the URID, which consists of 20 hexadecimal characters, a period, and four ending hexadecimal characters.

System Action: The ECCR describes the UR contents in subsequent messages.

User Response: Review the subsequent messages to get more diagnostic information about the error. Then contact Informatica Global Customer Support.

PWXEDM177221I for SYSIBM.table.

Explanation: The DB2 for z/OS ECCR encountered an error while processing a DDL operation in a log record in a DB2 unit of recovery (UR). The log record is for the DB2 catalog table SYSIBM.table.

System Action: The ECCR describes the UR contents in related messages.

User Response: Review the preceding PWXEDM177220E error message and related diagnostic messages. Then contact Informatica Global Customer Support.

PWXEDM177221I for SYSIBM.table.

Explanation: The DB2 for z/OS ECCR encountered an error while processing a DDL operation in a log record in a DB2 unit of recovery (UR). The log record is for the DB2 catalog table SYSIBM.table.

System Action: The ECCR describes the UR contents in related messages.

User Response: Review the preceding PWXEDM177220E error message and related diagnostic messages. Then contact Informatica Global Customer Support.

PWXEDM177223I UR contents:

Explanation: This message marks the start of the DB2 for z/OS ECCR internal information that describes the log records in the DB2 unit of recovery (UR) where the ECCR processing error occurred.

System Action: The ECCR describes the UR contents in related messages.

User Response: Review the preceding PWXEDM177220E error message and related diagnostic messages. Then contact Informatica Global Customer Support.

PWXEDM177224I DB2_ECCR_internal_description_of_log_records

Explanation: This message reports the DB2 for z/OS ECCR internal description of the log records in the DB2 unit of recovery (UR) where the ECCR processing error occurred.

System Action: The ECCR describes the UR contents in related messages.

User Response: Review the preceding PWXEDM177220E error message and related diagnostic messages. Then contact Informatica Global Customer Support.

PWXEDM177225I End of UR contents.

Explanation: This message marks the end of DB2 for z/OS ECCR internal information that describes the contents of the DB2 unit of recovery (UR) where the ECCR processing error occurred.

System Action: The ECCR reports no further information about the UR.

190 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 191: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Review the preceding PWXEDM177220E error message and related diagnostic messages. Then contact Informatica Global Customer Support.

PWXEDM177230I eccr_description_of _log_postition eccr_description_of_urid UR_operation [userid]

Explanation: The DB2 for z/OS ECCR encountered a DB2 unit of recovery (UR) log record for a UR that is specified in the SKIPURDML statement in the REPL2OPT DD data set. This message reports the following log record properties:

• log_position is the position of the record in the DB2 log.

• urid is the URID of the UR that contains the log record.

• UR_operation is one of the following DB2 internal operation types:

- BEGUR - Begin UR.

- BCP1 - Begin phase 1.

- BCP2 - Begin phase 1 to phase 2 transition.

- CP12T - Complete phase 1 to phase 2 transition.

- ECP2 - End phase 2.

- BABRT - Begin ABORT.

- EREDO - End REDO.

- ETODO - End TODO.

- EUNDO - End UNDO.

- EABRT - End ABORT.

• If UR_operation is BEGUR (Begin UR), the userid is reported. It is the user ID associated with the operation.

System Action: The ECCR processes the log record.

User Response: No response is required.

PWXEDM177231W log_postition urid dbid:psid:obid rid [I|U|D] ['N/A'|owner.table]

Explanation: The DB2 for z/OS ECCR encountered a DML record in the DB2 log for a unit of recovery (UR) that is specified in the SKIPURDML statement in the REPL2OPT DD data set. This message reports the following log record properties:

• log_position is the position of the record in the DB2 log.

• urid is the URID of the UR that contains the log record.

• dbid:psid:obid are the database ID, page space, and object ID of the table.

• rid is the row identifier of the changed row.

• [I|U|D] is the DML operation type, which can be Insert, Update, or Delete.

• owner.table_name identifies the table that the DML operation affected. If the table name cannot be determined, the value "N/A" appears.

System Action: The ECCR skips the DML log record.

User Response: No response is required.

PWXEDM177247E UNEXPECTED EYE-CATCHER IN R2PMAIN

Explanation: The R2PMAIN control block is incorrectly initialized. This is an internal error that causes the DB2 ECCR to abend.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 191

Page 192: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177248E QEDIT MACRO FAILED

Explanation: The QEDIT macro to failed because an internal error occurred.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177249E QEDIT MACRO FAILED

Explanation: The QEDIT macro to failed because an internal error occurred.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177253E INTERNAL ERROR

Explanation: The DB2 ECCR encountered an unspecified internal error that caused the program to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177255E UNEXPECTED EYE‑CATCHER IN DSNHDECP

Explanation: The DSNHDECP control block is incorrectly initialized. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177257E UNEXPECTED RC IN R15 FROM ESTAE SETUP

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177258I DB2 Capture ending because of STOP command.

Explanation: The DB2 for z/OS ECCR received an MVS STOP command.

System Action: The ECCR stops.

User Response: No response is required.

PWXEDM177259W WAITING ON DB2 CONNECTION

Explanation: The DB2 ECCR could not connect to DB2. Probably, the DB2 is not started.

192 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 193: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR periodically attempts to connect to DB2.

User Response: If appropriate, start DB2.

PWXEDM177262I Previous version-mode 'previous_DB2_version_mode (0xhex_value)' now set to 'new_DB2_version_mode (0xhex_value)'.

Explanation: After the DB2 for z/OS source system was migrated to a new DB2 version and mode, a warm start of the DB2 ECCR failed. In coordination with Informatica Global Customer Support, you determined that the migration path was valid and the warm start should have succeeded. Support instructed you to add a parameter to the REPL2OPT data set as a wordaround. This message indicates that the ECCR then successfully processed the new DB2 version and mode.

System Action: The DB2 ECCR starts and begins processing change data.

User Response: No response is required.

PWXEDM177263E Cannot warm start ECCR from 'Vprevious_DB2_version mode(0xhex_value)' to 'Vnew_DB2_version mode (0xhex_value)'.

Explanation: The DB2 for z/OS source system was migrated to a new DB2 for z/OS version and mode from a previous DB2 version and mode. However, the migration path between these DB2 versions and modes is not valid. As a result, an attempt to warm start the DB2 for z/OS ECCR after the migration failed with this error message. For example, this failure could occur if you migrated from DB2 Version 11 conversion mode to DB2 Version 11 new-function mode.

System Action: The DB2 ECCR ends abnormally.

User Response: Cold start the ECCR, or ensure that the migration from the earlier DB2 version and mode to the later DB2 version and mode is valid. If you need assistance, contact Informatica Global Support.

PWXEDM177264W No previous DB2 version-mode found. reason.

Explanation: The first time the DB2 ECCR was warm started after the DB2 for z/OS source system was migrated to a new DB2 version and mode, the ECCR was unable to fetch the previous DB2 version and mode from the PowerExchange Logger for one of the following reasons:

• Logger sequence does not contain old version-mode.

• Not requested from Logger.

• Logger has no sequence information.

System Action: The DB2 ECCR continues processing.

User Response: No response is required.

PWXEDM177265I PROCESSING IS COMPLETE

Explanation: The DB2 ECCR completed its processing.

System Action: The DB2 ECCR ends.

User Response: No response is required.

PWXEDM177266E Skipping from log loc rba_or_lrsn to loc rba_or_lrsn

Explanation: The DB2 ECCR detected a gap in the DB2 log data set while sequentially processing the log. This message identifies the RBAs, or LRSNs, that bound the gap. The DB2 ECCR skips from the first log RBA or LRSN specified in this message to the second log RBA or LRSN.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 193

Page 194: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR tries to continue.

User Response: Determine why the DB2 log has a gap. Ensure that all of the log records required for change capture processing are available. Also ensure that data consistency exists between the source and target tables. If source and target data is not consistent, repopulate the target tables.

PWXEDM177267I STARTING AT DB2 LOG LOCATION=rba_or_lrsn

Explanation: The DB2 ECCR started processing the DB2 log at the specified RBA or LRSN location.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177268I LAST READ DB2 LOG LOCATION=rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: This message identifies the location of the last DB2 log record that the DB2 ECCR processed for the last successful commit. In a data-sharing environment, the LRSN and data-sharing member ID are reported. The datasharing_member_id is 0 if data sharing is not used.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177276I DB2 CAPTURE ENDING DUE TO reason

Explanation: The DB2 ECCR capture program is ending for the specified reason. The reason variable can be one of the following values:

• XO29159 SUBTASK TERMINATION

• DB2 STOPPING

• A "STOP CAPT" NOTIFICATION

• REACHING "STOPAFT" LOCATION

• MVS STOP COMMAND

• CAPTURE QUIESCE COMMAND

System Action: The DB2 ECCR ends.

User Response: No response is required.

PWXEDM177281I LOG POSITION BEFORE REFRESH PROCESSING FOLLOWS

Explanation: An MVS MODIFY jobname,REFRESH command was issued to the DB2 ECCR. The next message indicates the position of the DB2 ECCR in the DB2 log just prior to refresh processing.

System Action: The DB2 ECCR refreshes its control information based on the newest versions of the REPL2CTL and REPL2OPT files.

User Response: No response is required.

PWXEDM177282I BEGIN DB2 CAPTURE TERMINATION

Explanation: The DB2 ECCR is beginning termination.

System Action: The DB2 ECCR ends.

User Response: No response is required.

194 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 195: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177283I Begin DB2 ECCR type processing.

Explanation: The DB2 ECCR is beginning the specified type of processing. The type variable can be one of the following values:

• WARM start

• COLD start

• SPECIAL start

• REFRESH

System Action: ECCR continues processing.

User Response: No response is required.

PWXEDM177284I Begin phase phase of eccr_start_type processing.

Explanation: The DB2 ECCR is starting the specified phase of cold start or special start processing. In the message text, phase is a number from 0 to 6, and eccr_start_type is either COLD start or SPECIAL start.

System Action: DB2 ECCR startup processing continues.

User Response: No response is required.

PWXEDM177286I DIRECTORY processing_type status.

Explanation: This message reports the status of DB2 ECCR cleanup of update processing of the capture directory tables. In the message text, processing_type is either cleanup or update, and status is either begins or ends.

System Action: The DB2 ECCR continues.

User Response: No response is required.

PWXEDM177289I DB2_catalog_table access status.

Explanation: The DB2 ECCR either started or finished accessing the specified DB2 catalog table. In the message text, DB2_catalog_table is one of the following values: SYSTABLESPACE, SYSTABLES, SYSCOLUMNS, SYSFIELDS, or Tablespace VSAM cluster. The status value is either begins or ends.

System Action: DB2 ECCR processing continues.

User Response: No response is required.

PWXEDM177290I SYSTABLEPART access status [for database_name.tablespace_name].

Explanation: The DB2 ECCR either started or finished accessing the DB2 catalog table SYSIBM.SYSTABLEPART for the specified database and partitioned tablespace. In the message text, status is either begins or ends.

System Action: DB2 ECCR processing continues.

User Response: No response is required.

PWXEDM177294I Verifying consistency of DB2 catalog definitions.

Explanation: The DB2 ECCR is verifying the consistency of the DB2 catalog definitions.

System Action: DB2 ECCR processing continues.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 195

Page 196: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177295I Catalog definitions have changed - retrying phase 2.

Explanation: The DB2 catalog definitions that the DB2 ECCR retrieved have changed between phase 2 and phase 3 of ECCR cold start processing. This situation can occur when you have not bound all of the required DB2 packages with the ISOLATION option.

System Action: The ECCR repeats phase 2 of startup processing, which increases the startup processing time.

User Response: For more information about the ISOLATION option and the DB2 packages that need to be bound, see the PowerExchange CDC Guide for z/OS. Ensure that you use the ISOLATION(RR) option to bind all of the DB2 packages that need to be bound. Then, cold start the ECCR again.

PWXEDM177297I Searching DB2 log for COLD start timestamp.

Explanation: The DB2 for z/OS ECCR is searching the DB2 log for the record that contains the ECCR cold start timestamp. The cold start timestamp is in a log record that is written between phase 2 and phase 3 of cold start processing.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177305I ECCR_start_type aborted by DB2 or MVS STOP command.

Explanation: A cold start or special start of the DB2 ECCR ended abnormally for one of the following reasons:

• DB2 stopped running during DB2 ECCR startup processing.

• Someone issued an MVS STOP command to stop the DB2 ECCR.

System Action: The DB2 ECCR stops running.

User Response: No response is required.

PWXEDM177310I ECCR_processing_type complete.

Explanation: This message reports that the specified type of DB2 ECCR processing is complete. In the message text, ECCR_processing_type is one of the following values:

• WARM start

• COLD start

• SPECIAL start

• REFRESH

System Action: The DB2 ECCR continues.

User Response: No response is required.

PWXEDM177313E {START STARTLOC= | STOPAFT LOGLOC=} value must be 20 hex characters.

Explanation: An invalid RBA value is specified for one of the following DB2 ECCR control statements:

• The START STARTLOC control statement in the data set that is allocated by the REPL2OPT DD statement in the ECCR JCL

• The STOPAFT LOGLOC control statement in the data set that is allocated by the REPL2CTL DD statement in the ECCR JCL

The value must consist of 20 hexadecimal characters.

196 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 197: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The ECCR ignores the specified control statement.

User Response: To use the optional START STARTLOC or STOPAFT LOGLOC control statement, enter a value that consists of 20 hexadecimal characters.

PWXEDM177314I Accessing DB2 log at requested location DB2_log_location.

Explanation: After a special start of the DB2 ECCR, the ECCR started processing the DB2 log at the specified RBA or LRSN location.

System Action: ECCR processing continues.

User Response: No response is required.

PWXEDM177323I CREATE DESCRIPTIONS BASED ON DB2 CATALOG

Explanation: The DB2 ECCR special‑start process is creating descriptions of the primary (source) tables from information in the DB2 catalog.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177325I CREATE DESCRIPTIONS BASED ON PRE-EXISTING CAPTURE DIRECTORY INFO

Explanation: The DB2 ECCR special-start process is creating descriptions of the primary (source) tables from preexisting capture directory information.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177327I VERIFY EXISTENCE OF TABLE AND COLUMN NAMES

Explanation: The DB2 ECCR is verifying the existence of the tables and columns identified on ST, SC and SE control records in the //REPL2CTL file.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177328I Begin maintenance of the DB2 ECCR TCAPSTATUS table.

Explanation: The DB2 for z/OS ECCR is beginning maintenance of the TCAPSTATUS capture directory table.

System Action: ECCR processing continues.

User Response: No response is required.

PWXEDM177331E START OF CAPTURE PROGRAM ABORTED BY A DB2 STOP OR AN MVS STOP COMMAND

Explanation: 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: The DB2 ECCR abends.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 197

Page 198: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177336E TCAPCOLUMNS ROWS ARE MISSING

Explanation: The DB2 ECCR special‑start process detected a description of a table that has no columns in the capture directory tables.

System Action: The DB2 ECCR abends.

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

PWXEDM177338E VALUE OF STARTLOC IS TOO HIGH

Explanation: In the DB2 ECCR REPL2OPT configuration file, the STARTLOC keyword in the START statement specifies an RBA value greater than the highest RBA value in the log.

System Action: The DB2 ECCR abends.

User Response: Correct the RBA value in the STARTLOC keyword of the START statement and run the job again.

PWXEDM177340I MAINTENANCE OF CAPTURE DIRECTORY IS COMPLETE

Explanation: The DB2 ECCR warm-start process completed the maintenance of the capture directory tables.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177343I MAINTENANCE OF CAPTURE DIRECTORY IS COMPLETE

Explanation: The DB2 ECCR refresh process completed the maintenance of the capture directory tables.

System Action: Processing continues.

User Response: No response is required.

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.

User Response: Processing continues.

System Action: No response is required.

PWXEDM177346I CR=crid ST=creator.table_name

Explanation: The specified DB2 for z/OS source table was deleted from or added to capture processing. The crid variable identifies the capture request ID.

User Response: Processing continues.

System Action: No response is required.

PWXEDM177349I FOLLOWING CAPTURE DEFINITIONS ARE BEING ADDED

Explanation: During its start or refresh process, the DB2 ECCR detected that new ST definitions were added.

198 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 199: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing continues.

User Response: No response is required.

PWXEDM177350E DIRECTORY CAN NOT BE PROPERLY ACCESSED

Explanation: The DB2 ECCR cannot access the capture directory table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177351E ROLLBACK HAS FAILED

Explanation: The DB2 ECCR initialized a rollback process, and the DB2 rollback failed.

System Action: The DB2 ECCR abends.

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.

PWXEDM177353E CAPTURE PROGRAM STOPPED

Explanation: 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: The DB2 ECCR abends.

User Response: No response is required.

PWXEDM177360E CAPTURE PROGRAM ABENDS AFTER MULTIPLE RETRIES

Explanation: The DB2 ECCR accessed the DB2 catalog to get descriptions of the source tables. However, the descriptions were inconsistent, probably because DDL changes were occurring on the tables at the same time as the ECCR was accessing the catalog. The ECCR tried several more times to get consistent table descriptions. Because these attempts were also unsuccessful, the ECCR abends.

System Action: The DB2 ECCR abends.

User Response: Restart 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.

PWXEDM177361E CAPTURE PROGRAM STOPPED

Explanation: The DB2 ECCR stopped startup or refresh processing because of one of the following actions:

• DB2 was stopped during the DB2 ECCR start or refresh process.

• An MVS STOP command was issued to stop the DB2 ECCR.

System Action: The DB2 ECCR abends.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 199

Page 200: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177368W catalog_table row not found in DB2 catalog

Explanation: The DB2 ECCR could not find a row in one of the following DB2 catalog tables:

• SYSTABLESPACE

• SYSCOLUMNS

• SYSFIELDS

This issue can occur during ECCR warm start or refresh processing in the following situations:

• A new capture registration is being processed for a table that was dropped or that was altered in a way that is inconsistent with the capture registration prior to the warm start or refresh command.

• DDL activity is occurring against the table or its table space.

System Action: The DB2 ECCR abends.

User Response: For the first situation, verify that the capture registration for the table matches the current table definition. If the table was dropped, delete the capture registration and warm start the DB2 ECCR. For the second situation, try to warm start the ECCR. If the ECCR fails again, complete the recommended actions for the first situation.

PWXEDM177371W TABLE 'creator.table_name' does not exist in DB2 catalog

Explanation: The DB2 ECCR cannot find a description of the specified table in the DB2 catalog. This issue can occur during warm start or refresh processing in the following situations:

• A new capture registration is being processed for a table that was dropped prior to the warm start or the refresh command.

• DDL activity is occurring against the table or its table space during the warm start or refresh process.

System Action: The DB2 ECCR abends.

User Response: For the first situation, delete the capture registration and warm start the DB2 ECCR. For the second situation, just warm start the DB2 ECCR.

PWXEDM177372W Table 'creator.table_name' inconsistent definitions

Explanation: The DB2 ECCR attempted to get a description of the specified table from the DB2 catalog. However, the description was inconsistent. This situation can occur when DDL activity is updating the catalog descriptions at the same time the DB2 ECCR is trying to access the descriptions.

System Action: The DB2 ECCR abends.

User Response: Look for prior messages in the DB2 ECCR output that concern this table. Then perform the actions that these messages suggest.

PWXEDM177373W Table 'creator.table_name' DB2 catalog definition not available at ECCR startup

Explanation: When the DB2 ECCR started, it tried to get a description of the specified table from the DB2 catalog. However, a table description was not available. As a result, the ECCR cannot capture change data for this table. This situation can occur during warm start or refresh processing when a new capture registration is being processed for a table that was created, or dropped and re-created, after the point in the log that the ECCR is processing for the warm start or refresh process.

200 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 201: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR abends.

User Response: Delete the capture registration and warm start the DB2 ECCR. After the ECCR processes past the point in the log where the table was first created or re-created, you can redefine the capture registration and refresh the ECCR .

PWXEDM177376I Table creator.table_name not found in {DB2 Catalog|TCAPTABLES}

Explanation: The DB2 for z/OS ECCR cannot find a description of the specified table in the DB2 catalog or PowerExchange capture directory (TCAP) tables even though this table is registered for change data capture. This situation is normal if the table did not exist when the current DB2 log records were written.

The ECCR cannot capture change data for the specified table until it finds and reads a log record that contains a CREATE TABLE statement for this table.

System Action: ECCR processing continues. However, no change data is captured for the specified table.

User Response: No response is required. If you want to capture change data for the table, verify that the table name is correctly specified in the capture registration or issue DDL to create the table.

PWXEDM177377E TWO TABLES WITH SAME DBID/PSID/OBID IN TCAPTABLES

Explanation: In the DB2 ECCR TCAPTABLES capture directory table, the table descriptions for two tables have the same combination of DB2 DBID, PSID, and OBID values. The PWXEDM177378E message provides the names of these two tables.

System Action: The DB2 ECCR abends.

User Response: To bypass this error, delete all rows that describe one of the tables from the TCAPTABLES table. Then start the DB2 ECCR again. Also ensure that only the DB2 ECCR updates the capture directory tables.

PWXEDM177378E creator.table1 and creator.table2

Explanation: This message identifies two tables to which the error reported in error message PWXEDM177377E pertains.

System Action: The DB2 for z/OS ECCR abends.

User Response: For more information about the error, see message PWXEDM177377E.

PWXEDM177379E DELETE ONE OF THE TWO TABLES FROM TCAPTABLES

Explanation: In the DB2 ECCR TCAPTABLES capture directory table, you must delete all rows for one of the two tables that are identified in message PWXEDM177378E. For a description of the error that requires this deletion, see message PWXEDM177377E.

System Action: The DB2 ECCR abends.

User Response: Delete all of the rows for one of the tables in the TCAPTABLES table. Then start the DB2 ECCR again.

PWXEDM177383E R2PASH TABLE SEARCH FAILED FOR DBID=dbid PSID=psid OBID=obid

Explanation: An internal error occurred. The DB2 ECCR R2PASH search function for the specified DBID, PSID, and OBID failed.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 201

Page 202: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177384E TCAPCOLUMNS ROWS NOT FOUND IN CAPTURE DIRECTORY

Explanation: The capture directory describes a table that has no columns defined. A table must have at least one column defined in the capture directory.

System Action: The DB2 ECCR abends.

User Response: Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the capture registration for the table and then deleting the row for this table in the TCAPTABLES table. Then restart the DB2 ECCR, re-create the capture registration, and refresh the ECCR.

PWXEDM177385E SEQUENCE‑ERROR FOR TCAPCOLUMNS ROWS IN CAPTURE DIRECTORY

Explanation: The DB2 ECCR found the descriptions of the table columns are not in the expected sequence in the TCAPCOLUMNS capture directory table.

System Action: The DB2 ECCR abends.

User Response: Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the capture registration for the table and then deleting the row for this table in the TCAPTABLES table. Then restart the DB2 ECCR, re-create the capture registration, and refresh the ECCR.

PWXEDM177386E TCAPFIELDS ROW NOT FOUND IN CAPTURE DIRECTORY

Explanation: The DB2 ECCR did not find a row in the TCAPFIELDS capture directory table.

System Action: The DB2 ECCR abends.

User Response: Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables. You can bypass this problem by deleting the capture registration for the table and then deleting the row for this table in the TCAPTABLES table. Then restart the DB2 ECCR, re-create the capture registration, and refresh the ECCR.

PWXEDM177387E TABLE creator.table_name DOES NOT EXIST IN CAPTURE DIRECTORY.

Explanation: The DB2 for z/OS ECCR cannot find a description of the specified table in the capture directory tables.

System Action: The ECCR abends.

User Response: Ensure that only the ECCR or the capture directory utility updates the capture directory tables. You can bypass this problem by deleting the capture registration for the table and then deleting the row for this table in the TCAPTABLES table. Then restart the ECCR, re-create the capture registration, and refresh the ECCR.

PWXEDM177388W TABLE creator.table_name INCONSISTENT DEFINITIONS.

Explanation: While the DB2 for z/OS ECCR was getting a description of the specified table from the capture directory tables, the ECCR determined that the description was not consistent.

System Action: The ECCR abends.

User Response: For more information, review any other messages that refer to this table.

PWXEDM177389W TABLE creator.table_name COLUMN DESCRIPTIONS MISSING.

Explanation: The DB2 for z/OS ECCR cannot find a description of the columns for the specified source table in the capture directory tables. This error might be caused by an ALTER TABLE statement that dropped or changed some columns in the table.

202 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 203: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing continues.

User Response: No response is required.

PWXEDM177390W TABLE creator.table_name UNUSABLE DEFINITION CR=capture_request.

Explanation: The DB2 for z/OS ECCR cannot find in a usable definition for the specified table and capture request (CR) in the capture directory tables.

System Action: The ECCR abends.

User Response: For more information about this error, see the associated error messages. Ensure that the capture registration definition is correct. Then start the ECCR again.

You can bypass this problem by deleting the capture registration for the table and then deleting the row for this table in the TCAPTABLES capture directory table. Then restart the ECCR, re-create the capture registration, and refresh the ECCR.

PWXEDM177392E INVALID CALL FUNCTION FOR X029242

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177393I Table table_name table space updated to new_tablespace_name (PSID X"tablespace_psid")

Explanation: The table space name and page set identifier (PSID) for the specified DB2 for z/OS source table have been updated in the PowerExchange DB2 ECCR capture directory. This message identifies the new table space name and PSID.

System Action: CDC processing continues.

User Response: No response is required.

PWXEDM177394W Table table_name non CDC {INSERT|DELETE|UPDATE} detected in DB2 UR urid_description at log_position.

Explanation: The DB2 for z/OS ECCR detected a data change record in the DB2 log for a tracked table for which the DATA CAPTURE CHANGES option is set but the log record is not in the format expected for CDC. This message includes the ECCR description of the unit-of-recovery ID (URID) and the log position at which the non-CDC change record occurs.

System Action: If the change is an UPDATE, the ECCR skips it. If the change is an INSERT or DELETE and the IFI306 statement in the REPL2OPT data set specifies OPT=Y or OPT=F, DB2 does not pass the change record to the ECCR.

User Response: Determine if the change should be captured. If you need assistance, contact Informatica Global Customer Support.

PWXEDM177395E UNEXPECTED VALUE IN COLTYPE COLUMN OF TCAPCOLUMNS TABLE

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 203

Page 204: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177396E UNEXPECTED VALUE IN FLDTYPE COLUMN OF table_name TABLE

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177397W Table table_name now DATA CAPTURE {NONE|CHANGES}.

Explanation: While processing DML changes to the DB2 catalog, the DB2 for z/OS ECCR detected a change in the DATA CAPTURE setting for the specified table. This message reports the new DATA CAPTURE setting.

System Action: CDC processing continues.

User Response: No response is required.

PWXEDM177398E TABLE creator.table_name PROBABLY NOT DEFINED WITH "DATA CAPTURE CHANGES"

Explanation: The specified DB2 table might not have been defined with the DATA CAPTURE CHANGES attribute. The DB2 for z/OS ECCR requires this attribute for change data capture.

System Action: See the associated messages to determine how the ECCR responds.

User Response: If the table was not defined with the DATA CAPTURE CHANGES attribute, use an ALTER TABLE statement to specify the DATA CAPTURE CHANGES attribute on the table. Afterwards, the ECCR continues to issue this message each time it starts or gets a refresh request, until it encounters the first change record for the table.

PWXEDM177399E TABLE creator.table_name COLUMN column_name NOT DEFINED

Explanation: The DB2 for z/OS ECCR cannot find the specified column in the TCAPCOLUMNS table or in the DB2 catalog.

System Action: The ECCR continues processing until it reads the next change record for the table. Then the ECCR abends.

User Response: Correct the column specification in the capture registration. Then warm start the ECCR.

PWXEDM177400I LAYOUT OF //REPL2OPT CONTROL RECORDS:

Explanation: The DB2 ECCR is starting the model layout of the possible control statements from the //REPL2OPT file.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177401I START OF REPL2OPT CONTROL STATEMENTS

Explanation: The DB2 ECCR started processing the configuration statements in the REPL2OPT data set. This message precedes a list of the configuration statements. The list includes any syntax or other errors in the statements.

System Action: Processing continues.

User Response: If a configuration statement contains an error, correct the statement in the REPL2OPT data set.

204 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 205: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177402I END OF REPL2OPT CONTROL STATEMENTS

Explanation: The DB2 ECCR completed processing the REPL2OPT configuration statements.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177403I LAYOUT OF //REPL2CTL CONTROL RECORDS:

Explanation: The DB2 ECCR is starting the model layout of the possible control statements from a //REPL2CTL file.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177404I START OF REPL2CTL CONTROL STATEMENTS

Explanation: The DB2 ECCR started processing the control statements in the REPL2CTL data set. This message precedes a list of the control statements that you or the ECCR created. The list includes any syntax or other errors in the statements.

Note: A control statement that the DB2 ECCR created is identified by the text ** SYSTEM GENERATED **.

System Action: Processing continues.

User Response: If a control statement contains an error, correct the statement in the REPL2CTL data set.

PWXEDM177405I END OF REPL2CTL CONTROL STATEMENTS

Explanation: The DB2 ECCR completed processing the REPL2CTL control statements.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177406I * * * ABOVE STATEMENT {HAS BEEN DEPRECATED | IS IGNORED DURING REFRESH PROCESSING | OPT=Y CAN MISS EVENTS. USE WITH CAUTION}

Explanation: This message reports some noteworthy condition about the preceding DB2 for z/OS ECCR control or configuration statement. The message reports any one of the following conditions:

• The statement is deprecated.

• The ECCR is ignoring the statement during ECCR REFRESH command processing.

• The IFI306 OPT=Y statement was specified and might cause the ECCR to not capture events such as a DB2 QUIESCE operation.

System Action: The DB2 ECCR does not use the statement.

User Response: No response is required. However, if you want the ECCR to use a statement that has not been deprecated, wait until refresh processing finishes and then restart of the DB2 ECCR.

PWXEDM177407E *** ERROR: error_text

Explanation: The DB2 ECCR found an error in a configuration statement in the REPL2OPT data set. The DB2 ECCR displays the erroneous statement. This message indicates the reason for the error.

System Action: The DB2 ECCR abends with abend code U3680.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 205

Page 206: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Correct the statement that has the error, and start the DB2 ECCR again. For more information about REPL2OPT statements, see the PowerExchange CDC Guide for z/OS.

PWXEDM177408E *** ERROR: error_text

Explanation: The DB2 for z/OS ECCR encountered an error related to specification of the SKIPURDML statement in the REPL2OPT DD data set. In this message, the error_text variable is one of the following reasons for the error:

• no blank after SKIPURDML

• no ''.'' in UR

• no trailing blank after UR

• maximum (255) SKIPURDML statements exceeded

• invalid characters in URID

System Action: The DB2 ECCR ends abnormally with abend code U3680.

User Response: Edit the REPL2OPT DD data set to correct the reported SKIPURDML error. Then start the ECCR again. For more information about the SKIPURDML statement, see the PowerExchange CDC Guide for z/OS.

PWXEDM177409E *** ERROR: error_text

Explanation: The DB2 ECCR found an error in a control statement in the REPL2CTL data set. The DB2 ECCR displays the erroneous statement. This message indicates the reason for the error.

System Action: The DB2 ECCR abends with abend code U3680.

User Response: Correct the statement that has the error, and start the DB2 ECCR again. For more information about REPL2CTL statements, see the PowerExchange CDC Guide for z/OS.

PWXEDM177410E *** ERROR: error_text

Explanation: The DB2 ECCR found an error in a control statement in the REPL2CTL data set. This message indicates the reason for the error.

System Action: The DB2 ECCR abends with abend code U3680.

User Response: Correct the statement that has the error, and start the DB2 ECCR again. For more information about REPL2CTL statements, see the PowerExchange CDC Guide for z/OS.

PWXEDM177411E *** ERROR: error_text

Explanation: The DB2 ECCR found an error in a control statement in the REPL2CTL data set. This message indicates the reason for the error.

System Action: The DB2 ECCR abends with abend code U3680.

User Response: Correct the statement that has the error, and start the DB2 ECCR again. For more information about REPL2CTL statements, see the PowerExchange CDC Guide for z/OS.

PWXEDM177412E *** ERROR: error_text

Explanation: The DB2 ECCR found an error in a control statement in the REPL2CTL data set. The DB2 ECCR displays the erroneous statement. This message indicates the reason for the error.

System Action: The DB2 ECCR abends with abend code U3680.

User Response: Correct the statement that has the error, and start the DB2 ECCR again. For more information about REPL2CTL statements, see the PowerExchange CDC Guide for z/OS.

206 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 207: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177421E X029260 CALLED FOR UNEXPECTED CATALOG TABLE table_name (ID=internal_id)

Explanation: An internal error occurred. The X029260 module issued a call for a DB2 catalog table with an incorrect table name.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177423E TCAPTABLESPACE HAS NO CURRENT ROW FOR DB=database TS=table_space

Explanation: While processing log records that describe DDL changes, the DB2 ECCR could not find a row in the TCAPTABLESPACE capture directory table for the specified DB2 table space.

System Action: The DB2 ECCR continues processing. However, it cannot capture changes from tables in the specified table space.

User Response: Ensure that only the DB2 ECCR or the capture directory utility update the capture directory tables.

PWXEDM177424E CAPTURE WILL NOT SUCCEED FOR TABLE creator.table_name

Explanation: While processing log records that describe DDL changes, the DB2 for z/OS ECCR could not find a row in the TCAPTABLESPACE capture directory table for the table space that contains the specified table.

System Action: The ECCR continues processing but cannot capture changes for the specified table.

User Response: Ensure that only the ECCR or the capture directory utility updates the capture directory tables.

PWXEDM177425E NO CURRENT TCAPTABLES ROW FOR TABLE creator.table_name

Explanation: While processing log records that describe DDL changes, the DB2 for z/OS ECCR could not find a row in the TCAPTABLES capture directory table for the specified table.

System Action: The ECCR continues processing but cannot capture changes for the specified table.

User Response: Ensure that only the ECCR or the capture directory utility updates the capture directory tables.

PWXEDM177426E UNEXPECTED TABLE NAME IN TCAPWORK ROW

Explanation: An internal error occurred. The DB2 ECCR found an incorrect table name in a row of the TCAPWORK capture directory table.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177428E UNEXPECTED VALUE IN UPTYPE COLUMN OF A TCAPWORK ROW

Explanation: An internal error occurred. The DB2 ECCR found an incorrect value in the UPTYPE column of a row in the TCAPWORK capture directory table.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 207

Page 208: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177430E DIRECTORY cannot be properly accessed by program_name

Explanation: The specified program cannot access a capture directory table to get information for DB2 ECCR processing.

System Action: The DB2 ECCR abends.

User Response: For more information about this error, see the associated messages. Then try to correct the error and run the job again.

PWXEDM177431E ROLLBACK HAS FAILED IN program_name

Explanation: The DB2 ECCR initiated a rollback process, but the rollback failed in the specified program.

System Action: The DB2 ECCR abends.

User Response: For more information about this error, see the associated messages. Then try to correct the problem and run the job again.

PWXEDM177436I No UOWS found

Explanation: This message is reported if the DB2 ECCR URID command was issued to display open UOWs for the DB2 subsystem or data-sharing group but the ECCR could not find any open UOW.

This message might also be reported during ECCR processing of a DISPLAY or REFRESH command.

System Action: The DB2 ECCR ignores the command. Processing continues.

User Response: No response is required.

PWXEDM177437I OPEN UOWs

Explanation: This message introduces a list of open UOWs that the DB2 ECCR displays in response to a URID command.

This message can also be issued during ECCR processing of a DISPLAY or REFRESH command.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177438I urid status last activity at last_log_position is activity_type

Explanation: The DB2 ECCR displays a DB2 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. The DB2 URID is the same as the PowerExchange Logger unit of work (UOW).

This message can also be generated during Statistics and Refresh processing.

This message contains the following variables:

• urid is the DB2 unit-of-recovery ID (URID) for the UR.

• status is one of the following values:

- ABORT. The UOW was aborted, and no change data is available to capture.

- OPEN. Change data is available to capture, but no Begin UOW record has been received.

- POTENTIAL. The Begin UOW was received, but no change data is available to capture yet.

208 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 209: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

- ROLLBACK. The UOW was rolled back, but change data is available to capture.

- TRANSMIT. The DB2 ECCR is sending change data for this UOW to the PowerExchange Logger for z/OS.

- UNRESOLVED. No urid value was encountered during the DB2 ECCR run. The ECCR records a URID value of PENDING for the specified UOW. When a UOW is outstanding, PowerExchange issues message PWXEDM177440W. This situation can occur if in‑flight units of work exist when the previous occurrence of the DB2 ECCR is shut down, usually not with a QUIESCE.

• last_log_position is the RBA or LRSN of the last record that was processed for this UOW.

• activity_type is one of the following values:

- Begin UOW

- End UOW

- Data

- Abort UOW

- Begin Phase1

- End Phase1

- Begin Phase2

- Phase 1/2 Tran

- End Todo

System Action: Processing continues.

User Response: Use this information to diagnose problems with UOWs that do not end properly, such as persistent outstanding UOWs.

If the message displays a valid urid value, you can use the DB2 ECCR TERM command to commit the UR. If the message reports a URID value of PENDING, you must use the Logger RESOLVE_INDOUBT command to commit or discard the UR. In this case, the next time the DB2 ECCR is restarted, it receives the result of the RESOLVE_INDOUBT command. 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 UOW uowid.data_sharing_member_id {TERMINATED | ABORTED}

Explanation: If this message displays “TERMINATED,” the DB2 ECCR TERM command was issued. The command causes the DB2 ECCR to stop processing the transaction with the specified UOWID. The DB2 ECCR does not create UOW records that correspond to the specified UOWID for the PowerExchange Logger.

If this message displays “ABORTED,” a currently logged UOW was encountered during a DB2 ECCR warm start. As a result, an ABORT record for the currently logged copy of the UOW is sent to the PowerExchange Logger.

System Action: If this message displays “TERMINATED,” the DB2 ECCR stops processing the specified UOWID and sends a record to the PowerExchange Logger that causes the PowerExchange Logger to treat this UOWID as if it were aborted. If you previously used the PowerExchange Logger RESOLVE_INDOUBT command to terminate the transaction, the state of the transaction in the PowerExchange Logger remains unchanged.

If this message displays “ABORTED,” the DB2 ECCR sends an ABORT record for the current UOWID to the PowerExchange Logger and then sends the entire UOW to the PowerExchange Logger again.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 209

Page 210: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required.

PWXEDM177440W No BEGIN UOW for uowid.data_sharing_member_id at log location rba_or_rsn.data_sharing_member_id.sequence_number

Explanation: In the specified DB2 log, the DB2 ECCR encountered a change record for a UOWID that does not have a BEGIN UOW entry. The DB2 ECCR does not send the change record to the PowerExchange Logger.

System Action: The DB2 ECCR continues processing but does not process this change record.

User Response: No response is required.

PWXEDM177441W UOW uowid.data_sharing_member_id not active

Explanation: The DB2 ECCR TERM command was entered for the specified UOW. However, this UOW is not active. The UOW might not be specified correctly in the command.

System Action: The DB2 ECCR continues processing and ignores the TERM command for the specified UOW.

User Response: Issue the URID command to get a list of all active UOWs. Then issue the TERM command again with the correct specification for an active UOW.

PWXEDM177442E BEGIN UOW OCCURRED OUT OF SEQUENCE: uowid.data_sharing_member_id

Explanation: The DB2 ECCR received a begin UOW request for the specified UOWID. However, a begin UOW request was already received for this UOWID. The DB2 ECCR can process only one UOW request for a UOWID at a time.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177443E UPDATE OUT OF SEQUENCE. UOW uowid.data_sharing_member_id IN ABORT STATUS

Explanation: An update was made to a source table while the DB2 ECCR was processing the specified UOW in Abort status.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177444E Error deleting old outstanding UOW uowid.sequence_number.data_sharing_member_id

Explanation: The DB2 ECCR capture program tried to delete an old outstanding UOW that the ECCR had previously reconciled with the data in the DB2 log. However, the deletion was unsuccessful.

System Action: The DB2 ECCR abends with additional messages.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing.

210 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 211: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177445E INVALID STATUS (status) ENCOUNTERED FOR UOW uow_id.data_sharing_member_id

Explanation: The specified UOW has a DB2 ECCR internal status that is not valid at some point in CDC processing. The status variable represents one of the following values:

• ABORT. The UOW was aborted, and no change data is available to capture.

• OPEN. Change data is available to capture, but no Begin UOW record has been received.

• POTENTIAL. The Begin UOW record has been received, but no change data is available to capture yet.

• ROLLBACK. The UOW was rolled back, but change data is available to capture.

• TRANSMIT. The DB2 ECCR is sending change data for the UOW to the PowerExchange Logger for z/OS.

• UNRESOLVED. No urid value was encountered during the DB2 ECCR run. The ECCR records a URID value of PENDING for the specified UOW. When a UOW is outstanding, PowerExchange issues message PWXEDM177440W. This situation can occur if in‑flight units of work exist when the previous occurrence of the DB2 ECCR is shut down, usually without specifying QUIESCE.

System Action: The DB2 ECCR ends abnormally.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177446E DISCARDING PREVIOUS UNPAIRED LOG RECORD FROM log_rba_or_lrsn.data_sharing_member_id.sequence number

Explanation: While processing DB2 log records, the DB2 ECCR detected that a log record was not paired with a continuation record. This error can occur in the following situations:

• The DB2 ECCR just completed a cold start.

• The DB2 ECCR just completed a warm start or refresh process under the following conditions:

- New capture registrations were added.

- The source tables were altered while the next log records to be processed were being written to the log.

• The DB2 ECCR just completed a special start.

System Action: The DB2 ECCR discards the unpaired log record. See message PWXEDM177030E to determine whether the DB2 ECCR abends or tries to continue.

User Response: If this message is issued occasionally, when one of the situations described in the explanation exist, ignore this error. However, if the message is issued frequently, or for reasons other than those previously described, collect the complete DB2 ECCR job listing, including the SYSUDUMP output, and then contact Informatica Global Customer Support.

PWXEDM177447E DISCARDING CURRENT LOG RECORD FROM log_rba _or_lrsn.data_sharing_member_id.sequence_number - reason

Explanation: The DB2 ECCR read the current record from the DB2 log and is discarding the record from the change capture stream. This message includes the reason for discarding the log record.

System Action: See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 211

Page 212: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Use this message to diagnose the problem. If you cannot correct the problem, contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177448E TABLE DEFINITIONS NOT USABLE - creator.table_name

Explanation: The DB2 for z/OS ECCR cannot find a usable description of the specified table.

System Action: The ECCR abends.

User Response: To diagnose the error, look for previous error messages that provide more information about the error. If possible, correct the problem and run the job again.

PWXEDM177450E Table creator.table_name DDL and DML in UOW uowid.data_sharing_member_id.

Explanation: The DB2 for z/OS ECCR detected that a UOW performed both DDL and DML operations on the same table. The ECCR does not capture changes from UOWs that contain both types of operations on the same table.

System Action: The ECCR continues processing but might not capture some changes for the table.

User Response: Ensure that the UOWs for the specified table do not perform both DDL and DML operations.

PWXEDM177451I CATALOG TABLE table_name, COLUMN column_name in urid.data_sharing_member_id at rba_or_lrsn.data_sharing_member_id.sequence number

Explanation: A Unicode conversion failure occurred when the DB2 ECCR was trying to read a DB2 log record for the specified DB2 catalog table. This message reports the catalog table name, column name, DB2 URID, and DB2 log.

System Action: DB2 ECCR processing ends.

User Response: Check the JES message log and the EDMMSG message log for related error messages. If any message includes an IBM return code, also see the IBM messages and codes manual for your DB2 version. After you collect all available information about the error, contact Informatica Global Customer Support.

Note: PowerExchange issues reason codes from encoded commands that pass between program modules. Some of these reason codes are displayed in messages that are issued when an error occurs.

PWXEDM177452E ERROR DETECTED WHILE PROCESSING COMMIT OR ROLLBACK RECORD

Explanation: The DB2 ECCR encountered an error while processing a unit of recovery control log record.

System Action: See message PWXEDM177030E to determine whether the DB2 ECCR abends or tries to continue.

User Response: To diagnose the error, look for other messages associated with this error. Then correct the problem and run the job again.

PWXEDM177453I PENDING UNRESOLVED logger URID lrsn

Explanation: In a DB2 for z/OS data-sharing environment, this message reports the DB2 LRSN of the last activity in a unit-of-recovery (UR) that the ECCR sent to the PowerExchange Logger for z/OS with a status of UNRESOLVED and a URID value of PENDING. The status and value are reported in the preceding PWXEDM177438I message.

System Action: The DB2 ECCR continues.

212 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 213: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required. For more information about the status, see the PWXEDM177438I message.

PWXEDM177454I logger URID lrsn

Explanation: In a DB2 for z/OS data-sharing environment, this message reports the DB2 LRSN of the last activity in a unit-of-recovery (UR) that the ECCR sent to the PowerExchange Logger for z/OS with a status other than POTENTIAL. The status and URID value are reported in the preceding PWXEDM177438I message.

System Action: The DB2 ECCR continues.

User Response: No response is required. For more information about the status, see the PWXEDM177438I message.

PWXEDM177456E Table creator.table_name column column_number column_name unexpected length in {normal|before} image

Explanation: When processing a DB2 log record for the specified table, the DB2 for z/OS ECCR encountered an invalid column length in the normal image or before image row for a DML operation.

System Action: The ECCR abends or continues processing, as indicated in message PWXEDM177030E.

User Response: Contact Informatica Global Customer Support. Provide the complete ECCR job listing, including the SYSUDUMP output.

PWXEDM177457I in UR urid at log_position

Explanation: This message identifies the unit-of-recovery (UR) and DB2 log position at which an operation that is reported in a preceding message occurred. This message includes the ECCR description of the UR identifier (URID) and the log position at which the change occurred.

System Action: CDC processing continues.

User Response: No response is required.

PWXEDM177459E X029271 UNEXPECTED LENGTH OF A DECIMAL COLUMN IN INTERNAL CONTROL BLOCK

Explanation: While attempting to capture a DB2 table row that contains a packed decimal column, the DB2 ECCR discovered that the length of the column, as described in its internal control blocks, was not valid for a packed decimal column.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177460E TABLE creator.table_name unexpected row length in {normal|before} image

Explanation: While the DB2 for z/OS ECCR was processing a DB2 log record for the specified table, it encountered an invalid row length.

System Action: The ECCR abends or continues processing, as indicated in the message PWXEDM177030E.

User Response: Ensure that the UOWs for the specified table do not include both DDL and DML operations. The ECCR does not support both types of operations in the same UOW for the same table. Also, collect the complete ECCR job listing, including the SYSUDUMP output. Then contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 213

Page 214: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177461E Invalid lengths at rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: While attempting to capture a DB2 table row, the DB2 ECCR could not correctly parse the specified log record that contains the change data for the row.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177462E|I Table creator.table_name ROW NOT DECOMPRESSED AT rba_or_lrsn.data_sharing_member_id.sequence_number RC=return_code, RS=reason_code, DG=diagnostic_code

Explanation: When reading DB2 log records with the DB2 IFI 306 interface, the DB2 for z/OS ECCR encountered a log record for the specified table that was not decompressed by DB2. The RC, RS, and DG values are the DB2 codes for the decompression failure.

PowerExchange issues this message as an error or informational message, depending on the ROWNOTDECOMPRESSED setting in the ECCR REPL2OPT file. This message is issued to the EDMMSG data set and as a WTO message.

System Action: If the ROWNOTDECOMPRESSED statement is set to FAIL (the default), the DB2 ECCR ends abnormally and this message is an error message. If the ROWNTODECOMPRESSED statement is set to NOFAIL, the ECCR skips the compressed records and continues processing, and this message is an informational message.

User Response: If this message is an informational message and the ECCR skips the compressed records, review the associated message PWXEDM177526 to identify the number of records that were skipped and their location in the DB2 log. If this message is an error message and the ECCR fails, determine the point in the log from which to restart the ECCR. Also, you can use the IBM DB2 documentation to troubleshoot the decompression failure.

PWXEDM177463E UNEXPECTED COLUMN‑TYPE CODE IN INTERNAL CONTROL BLOCK

Explanation: An internal error occurred. The DB2 ECCR found an unexpected column type code in an internal control block.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177464E INTERNAL ERROR: AREA TOO SMALL TO BUILD ROW IMAGE

Explanation: An internal error occurred. When the DB2 ECCR attempted to create a row image in memory, it found the allocated memory area was too small.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177465E INTERNAL ERROR: AREA TOO SMALL TO BUILD OUTPUT MESSAGE

Explanation: An internal error occurred. When the DB2 ECCR attempted to build an output message in memory, it found the allocated memory area was too small.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

214 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 215: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177466E INTERNAL ERROR: UNEXPECTED R2PCLFUN VALUE value

Explanation: An internal error occurred. The DB2 ECCR found an unexpected value in R2PCLFUN.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177469E TABLE creator.table_name EDITPROC proc_name RETURNED RC=return_code, RSN=reason_code

Explanation: The EDITPROC exit routine for the specified table encountered an error and returned the specified return code and reason code.

System Action: See message PWXEDM177030E to determine whether the DB2 for z/OS ECCR abends or continues processing.

User Response: Determine the cause of the EDITPROC exit routine error. Then correct the error and run the job again.

PWXEDM177470E TABLE creator.table_name EDITPROC proc_name OVERLAYED STORAGE

Explanation: The specified EDITPROC exit routine overlaid a virtual storage area.

System Action: The DB2 for z/OS ECCR abends.

User Response: Correct the EDITPROC exit routine, and then run the job again.

PWXEDM177471E UNEXPECTED CONTENT IN INTERNAL POINTERS

Explanation: An internal error occurred. The DB2 for z/OS ECCR found incorrect internal pointers.

System Action: The ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete ECCR job listing, including the SYSUDUMP output.

PWXEDM177472E INTERNAL AREA NOT LARGE ENOUGH FOR OUTPUT FROM FIELDPROC EXIT ROUTINE

Explanation: An internal error occurred. A FIELDPROC exit routine tried to generate its output, but the area allocated for the output was too small.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177473E USER PROVIDED FIELDPROC RETURNED WITH A NON-ZERO VALUE IN R15

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

System Action: See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing.

User Response: To diagnose the error, review other messages associated with this error. Then correct the problem and run the job again.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 215

Page 216: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177474E LENGTH OF COLUMN VALUE RETURNED BY A USER FIELDPROC IS INVALID

Explanation: 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 a related message.

As described in the DB2 manuals, for VARCHAR and VARGRAPHIC column formats, a FIELDPROC exit routine must return the 2-byte length of the column value in the FPVDVALE field of the DB2 column value descriptor (CVD). This 2-byte length must meet the following requirements:

• It must be expressed as a number of bytes.

• It must not be longer then the maximum length of the column.

• If it is a VARGRAPHIC column, it must be a multiple of 2.

The DB2 ECCR detected that the returned FPVDVALE value does not meet all of these requirements.

System Action: See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing.

User Response: Determine why the column value returned by the user‑defined FIELDPROC exit routine did not meet these requirements. Then correct the exit routine and run the job again.

PWXEDM177475E TABLE creator.table_name FIELDPROC proc_name RETURNED RC=return_code, RSN=reason_code

Explanation: The DB2 for z/OS ECCR called the specified FIELDPROC exit routine to transform a column value in 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 indicates that an error occurred. The FIELDPROC exit routine set the return code and reason code in the DB2 FPIB control block.

The meanings of the return code and reason code are defined by the user-defined FIELDPROC exit routine.

System Action: See message PWXEDM177030E to determine whether the ECCR abends or continues processing.

User Response: Determine why the FIELDPROC exit routine encountered an error. Then correct the error and run the job again.

PWXEDM177476E error_text

Explanation: The FIELDPROC exit routine that is identified in message PWXEDM177475E returned with a nonzero value in register 15. A nonzero value in register 15 indicates that an error occurred. This message displays the 40‑byte error text. The FIELDPROC exit routine also puts the address of a 40‑byte error text message in the FPBTOKPT field.

System Action: See message PWXEDM177030E to determine whether the DB2 ECCR abends or continues processing.

User Response: Determine why the FIELDPROC exit routine encountered an error. Then correct the problem and run the job again.

216 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 217: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177487E DB2 CHANGE CAPTURE AND EDM LoggerLAST READ RBA EQUAL 0, COLD START RECOMMENDED

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

System Action: Restart processing abends with a return code of 23.

User Response: Use a cold start to restart the DB2 ECCR.

PWXEDM177489W DB2 CHANGE CAPTURE HAS INITIATED A COLD START

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.

System Action: Restart processing continues.

User Response: No response is required. A subsequent message asks you to confirm or cancel the cold start.

PWXEDM177490I statistics

Explanation: This informational message provides statistics about the DB2 ECCR change capture process.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177491I statistics heading

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

System Action: Processing continues.

User Response: No response is required.

PWXEDM177492E statistics

Explanation: This informational message provides statistics about the DB2 ECCR change capture process.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177493E Unable to eccr_action for table creator.table_name, RC=return_code, RSN=reason_code.

Explanation: The DB2 for z/OS ECCR encountered an error during restart processing. This message identifies the table for which the error occurred and the ECCR action that could not be performed. This message also includes the return code, reason code, and information about the error if available.

The eccr_action can be one of the following values:

• get active schema

• $BLDCMD error for RETSCH

System Action: ECCR processing continues. For critical errors, the ECCR issues additional messages.

User Response: To diagnose the error, review the information in this message and in associated messages. If you need assistance, contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 217

Page 218: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177495I Table creator.table_name {active|pending} schema verified.

Explanation: When the DB2 for z/OS ECCR received the first change record for the specified table, the ECCR verified that the table schema matches the schema registered for the table in the PowerExchange repository. This message also indicates whether the schema is active or pending.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177496E THE START RBA SPECIFIED BY THE USER IS LESS THAN THE EDM LOGGER RBA

Explanation: The DB2 log RBA you specified during restart processing had a value less than the current RBA in the PowerExchange Logger.

System Action: The DB2 ECCR abends.

User Response: Edit the STARTLOC parameter in REPL2OPT to an appropriate start RBA and run the restart job again.

PWXEDM177498E Error acquiring {command|reply} buffer. Count=nnn, current size=size1, new size=size2

Explanation: The DB2 ECCR encountered an error when trying to acquire a command or reply buffer. This message provides the count of captured changes, the current size of the buffer, and the new size of the buffer.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with all of the available information about the error.

PWXEDM177499E {CA NAME|UOWPREFIX} HAS CHANGED IN REPL2CTL; {CA NAME|UOWPREFIX} IS IGNORED DURING REFRESH PROCESSING

Explanation: The CA NAME or UOWPREFIX control statement in the REPL2CTL data set changed. The DB2 ECCR detected the change during refresh processing. Message PWXEDM17500E displays the original CA NAME or UOWPREFIX value that the ECCR is currently using and the changed value in the REPL2CTL data set.

System Action: Refresh processing continues. The ECCR ignores the changed CA NAME or UOWPREFIX value in the REPL2CTL data set.

User Response: If you want to use the changed CA NAME or UOWPREFIX control statement in the REPL2CTL data set, restart the ECCR. Otherwise, no response is required.

PWXEDM177500E CURRENT {CA NAME|UOWPREFIX}: value1; {CA NAME|UOWPREFIX} IN REPL2CTL: value2

Explanation: This message follows message PWXEDM177499E and provides more information about the error. During refresh processing, the DB2 ECCR detected that the CA NAME or UOWPREFIX control statement in the REPL2CTL control file changed. This messages shows the CA NAME or UOWPREFIX value that the ECCR is currently using and the changed value in the REPL2CTL data set.

System Action: Refresh processing continues. The ECCR ignores the changed CA NAME or UOWPREFIX value in the REPL2CTL data set.

User Response: If you want to use the changed CA NAME or UOWPREFIX control statement in the REPL2CTL data set, restart the ECCR. Otherwise, no response is required.

218 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 219: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177508I Table creator.table_name changes captured. Schema create time timestamp1[, alter time timestamp2].

Explanation: This message is issued when the DB2 for z/OS ECCR captures the first change for the specified DB2 table by using the schema that have the specified timestamps. The timestamps indicate when the table was created and when the table was last altered if applicable.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177511E Table creator.table_name Schema verification failed.

Explanation: The DB2 for z/OS ECCR determined that the schema in the capture registration for the specified DB2 table does not match the table schema in the DB2 catalog.

System Action: The ECCR abends.

User Response: Create the capture registration again with a schema that matches the DB2 schema.

PWXEDM177513I Table creator.table_name {altered|created|dropped} at timestamp

Explanation: The specified DB2 table is registered for change data capture. The DB2 for z/OS ECCR detected that the table was altered, created, or dropped at the date and time in the specified timestamp..

System Action: Processing continues.

User Response: No response is required.

PWXEDM177518W TABLE 'creator.table_name' DESCRIPTION NOT FOUND IN CAPTURE DIRECTORY

Explanation: An internal error occurred. When processing DB2 log records for a table rename operation, the DB2 ECCR tried to locate a table definition row in the TCAPTABLES capture directory table for the table being renamed. However, the ECCR did not find the table definition.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177520E CA NAME=ca_name NOT FOUND OR IS INVALID IN REPL2CTL

Explanation: In the DB2 ECCR REPL2CTL data set, the CA NAME control statement is missing or is invalid. PowerExchange encountered this error during DB2 ECCR startup.

System Action: The DB2 ECCR abends.

User Response: Enter a valid CA NAME statement in the REPL2CTL data set and restart the DB2 ECCR. For more information about this REPL2CTL control statement, see the PowerExchange CDC Guide for z/OS.

PWXEDM177521E program_name internal error - invalid call function function_name

Explanation: An internal error occurred. The DB2 ECCR encountered an invalid call function for the specified program.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including the SYSUDUMP output.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 219

Page 220: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177522E TCAPTABLESPACE ROW NOT FOUND IN CAPTURE DIRECTORY

Explanation: The internal state of the DB2 ECCR capture directory tables is not correct.

This message is usually issued during an ECCR special start, when a DDL operation that deletes a tablespace occurs between the time the log record that is used for the special start is written and the time the special start is executed.

System Action: The DB2 ECCR abends.

User Response: Ensure that only the DB2 ECCR or capture directory utility updates the capture directory tables.

If you performed a special start, either try performing a cold start or retry the special start immediately after the point in the log where the error occurred. If this issue did not occur during a special start, or if you performed a special start and processed the DB2 log up to the current point in time, gather all ECCR job output, including the dump output, and then contact Informatica Global Customer Support.

PWXEDM177526E CAPTURE-DIRECTORY OR DB2-CATALOG CAN NOT BE PROPERLY ACCESSED

Explanation: The DB2 ECCR cannot access a capture directory table or a DB2 catalog table.

System Action: The DB2 ECCR abends.

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.

PWXEDM177527E ROLLBACK HAS FAILED

Explanation: The DB2 ECCR initiated a rollback process, and the DB2 rollback failed.

System Action: The DB2 ECCR abends.

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.

PWXEDM177528E UNEXPECTED RETURN CODE FROM X029232

Explanation: The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177529E THIS MIGHT BE A TRANSIENT PROBLEM - TRY A WARMSTART OF THE CAPTURE PROGRAM

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

System Action: The DB2 ECCR abends.

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

220 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 221: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177531E Table creator.table_name column column_name has unrecognized datatype 0xyyyyyyyy

Explanation: The DB2 for z/OS ECCR cannot determine the datatype for the specified column while processing a DDL statement that affects the column definition.

System Action: The ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete ECCR job listing, including the SYSUDUMP output.

PWXEDM177532E DB2 Capture ending because of X029159 SUBTASK termination.

Explanation: DB2 for z/OS ECCR capture processing ended because of the specified subtask termination error.

System Action: The ECCR abends.

User Response: Collect the ECCR job listing, including the SYSUDUMP output. Then contact Informatica Global Customer Support.

PWXEDM177533E Table 'creator.table_name' Error accessing schema.

Explanation: During initialization or REFRESH processing, the DB2 ECCR gets schema information for source tables from their capture registrations through the PowerExchange Agent. However, the ECCR was unable to get schema information for the specified table.

System Action: The DB2 ECCR abends, without processing any additional DB2 log data.

User Response: Examine the registration status of the specified DB2 table. Look for any error messages in the DB2 ECCR and PowerExchange Agent output that might indicate a problem with the schema information. Correct any errors and then restart the ECCR.

If the problem persists or cannot be identified, contact Informatica Global Customer Support.

PWXEDM177534W Duplicate old outstanding UOW found: uowid.data_sharing_member_id

Explanation: During a warm start, the DB2 ECCR processed the list of outstanding UOWs that the Logger has recorded as in progress from this ECCR. This list is used to notify the Logger when these UOWs terminate, so that the Logger can remove related records. Otherwise, the outstanding UOWs might affect ECCR restart. While processing the specified UOW, the ECCR determined that this UOW is a duplicate in the list.

System Action: Processing continues. The duplicate UOW is dropped, but the original entry will be processed.

User Response: Contact Informatica Global Customer Support.

PWXEDM177535W Persistent outstanding UOW urid.data_sharing_member_id found at rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: During statistics processing, the DB2 ECCR produces a list of outstanding UOWs in the same format as in the URID command output. The ECCR examines each outstanding UOW to determine how long it has been outstanding. If any UOW has been outstanding for the entire statistics interval, as specified at ECCR startup in the STAT command, the ECCR issues this message to warn that the UOW has been outstanding a long time. This situation might occur if the ECCR missed the completion of the UOW. This message includes the DB2 URID for the outstanding UOW.

System Action: Processing continues.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 221

Page 222: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: If the outstanding UOW persists, examine the output from the DB2 ECCR and DB2 subsystem to determine why the UOW has not completed. You can run the DB2 DSN1LOGP utility, or equivalent, to determine if the UOW is really outstanding. If you cannot determine the reason why the UOW is outstanding, contact Informatica Global Customer Support.

PWXEDM177536E IFI RETURNED OUT OF SEQUENCE RECORDS, CURRENT rba or lrsn.data_sharing_member_id, PREVIOUS rba or lrsn.data_sharing_member_id

Explanation: When processing log records that the DB2 IFI306 interface returned, the DB2 ECCR encountered log records that were out of sequence. This message identifies the current log and the previous log.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then contact Informatica Global Customer Support.

PWXEDM177537I Table owner.table_name OWNERSHIP TRANSFERRED to new_owner at timestamp.

Explanation: The owner of the specified DB2 for z/OS source table was changed. This message reports the name of the original owner, the name of the new owner, and the DB2 timestamp at which the change occurred. The timestamp is in the format yyyy-mm-dd-hh.mm.ss.tttttt.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177538I Table creator.table_name renamed to creator.new_table_name at timestamp.

Explanation: The name of the specified DB2 for z/OS source table was changed. This message reports the original table name, the new table name, and the DB2 timestamp at which the rename operation occurred. The timestamp is in the format yyyy-mm-dd-hh.mm.ss.tttttt.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177539I Table 'creator.table_name' now '{DATA CAPTURE CHANGES | DATA CAPTURE NONE'}. DB2 Log Location=rba_or_lrsn

Explanation: When processing log records, the DB2 ECCR detected that a source table acquired or lost the DATA CAPTURE CHANGES attribute. The DATA CAPTURE CHANGES attribute is required for the ECCR to capture data from the table. This message reports when the attribute changes so that you can analyze when capture processing could be active for the table. This message includes the name of the table for which the attribute changed and the location in the DB2 log data where the ECCR detected the change. The message also indicates whether the attribute was enabled (DATA CAPTURE CHANGES) or disabled (DATA CAPTURE NONE).

System Action: Processing continues.

User Response: This informational message helps properly track change capture for DB2 source tables. If the DATA CAPTURE CHANGES attribute was disabled, determine if any changes were written to the table after the specified DB2 log location RBA. If so, you might need to rematerialize the target that corresponds to the source table.

222 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 223: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177543E DB2 Catalog tables are not DATA CAPTURE CHANGES.

Explanation: During initialization, the DB2 for z/OS ECCR determined that one or more of the DB2 catalog tables that it uses does not have the required DATA CAPTURE CHANGES attribute. The ECCR uses the following catalog tables:

• SYSIBM.SYSTABLES

• SYSIBM.SYSCOLUMNS

• SYSIBM.SYSTABLESPACE

• SYSIBM.SYSFIELDS

• SYSIBM.SYSCOPY.

Message PWXEDM177398E indicates which of these tables is missing the attribute.

System Action: The ECCR ends without processing any DB2 log data.

User Response: Set the DATA CAPTURE CHANGES attribute on the catalog tables that are missing the attribute. Then cold start or special start the ECCR. If you warm start the ECCR, it does not recognize the current status of the DB2 catalog tables and fails, even if the DB2 catalog tables were altered to add the DATA CAPTURE CHANGES attribute.

PWXEDM177548I Verifying Capture Directory configuration supports up to DB2 v.r.m catalog level.

Explanation: The DB2 for z/OS ECCR is verifying that the PowerExchange capture directory tables support the DB2 catalog version that you use. In the message text, v.r.m is either the DB2 version.release.modification level or Vversion followed by the migration mode, for example, V10 NFM.

System Action: ECCR processing continues.

User Response: No response is required.

PWXEDM177549W ---TCAP_table_name has n columns. n columns expected.

Explanation: During initialization, the DB2 for z/OS ECCR examines the PowerExchange capture directory tables to determine if they support the DB2 version and mode that you use. The ECCR determined that the specified capture directory table does not contain the expected number of columns. In the message text, n is the number of columns.

System Action: The DB2 ECCR continues processing or ends abnormally, depending on the DB2 version.

User Response: Check the subsequent PWXEDM177552I message to determine the latest DB2 version that the capture directory tables support. If the tables do not support the version with which the ECCR is running, alter the specified capture directory table to support that DB2 version or a later DB2 version that PowerExchange supports.

PWXEDM177550W ---TCAP_table_name unexpected column column_name.

Explanation: During initialization, the DB2 ECCR examines the capture directory tables to determine if they support of the DB2 version and mode that you use. The ECCR determined that the specified table contains a column that the ECCR did not expect. In the message text, TCAP_table_name is the name of the capture directory table, and column_name is the name of the unexpected column.

System Action: The DB2 ECCR continues processing or ends abnormally, depending on the DB2 version.

User Response: Correct the definition of the specified capture directory table and restart the ECCR. If you need assistance, contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 223

Page 224: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177551W ---TCAP_table_name incorrect column attributes for column column_name

Explanation: During initialization, the DB2 for z/OS ECCR examines the PowerExchange capture directory tables to determine if they support the DB2 version and mode that you use. The ECCR found that the specified table contains a column with incorrect column attributes. In the message text, TCAP_table_name is the name of the capture directory table, and column_name is the name of the column with the incorrect attributes.

System Action: The DB2 ECCR continues processing or ends abnormally, depending on the DB2 version.

User Response: Check the subsequent PWXEDM177552I message to determine the latest DB2 version that the capture directory tables support. If the tables do not support the version with which the ECCR is running, upgrade the capture directory table to support that DB2 version or a later DB2 version that PowerExchange supports.

PWXEDM177552I Capture Directory supports up to DB2 version catalog level.

Explanation: During initialization, the DB2 for z/OS ECCR identified the latest DB2 catalog version that the PowerExchange capture directory tables support. In the message text,version is either the DB2 version.release.modification level or Vversion followed by the migration mode, for example, V11 NFM.

System Action: ECCR processing continues.

User Response: If the reported DB2 catalog version is earlier than the DB2 catalog version with which the ECCR runs, the ECCR might run with reduced functionality. In this case, alter the capture directory table definitions to meet the requirements of your DB2 version. For more information about upgrading the capture directory tables, see the PowerExchange CDC Guide for z/OS.

PWXEDM177553I Table owner.table_name version changed from n to m at timestamp.

Explanation: While processing DDL log records, the DB2 for z/OS ECCR detected that the version of the specified table changed. The table version defines the schema level that is used for the table. This message provides the fully qualified name of the table, the old and new versions, and the timestamp in the DB2 log record where this change occurred.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177555E Capture Directory does not support DB2 version catalog level.

Explanation: During initialization, the DB2 for z/OS ECCR examines the PowerExchange capture directory tables to determine if they support the DB2 catalog version that you use. The ECCR determined that the capture directory tables do not support your DB2 catalog version. In the message text, version is either the DB2 version.release.modification level or Vversion followed by the migration mode (for example, V11 NFM). The mode can be one of the following values: CM for conversion mode, ENFM for enabling new-function mode, or NFM for new-function mode.

System Action: The ECCR ends abnormally.

User Response: Run the jobs that upgrade the capture directory tables. For more information, see the PowerExchange CDC Guide for z/OS or PowerExchange Installation and Upgrade Guide.

224 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 225: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177556E UNACCEPTABLE ERROR WHILE ACCESSING THE DB2 LOG

Explanation: The DB2 ECCR issued an IFCID 306 READS call. An unacceptable combination of return code and reason code was returned. Additional messages are issued to indicate either the specific return code and reason code or the error based on the return code and reason code.

System Action: The DB2 ECCR ends without processing any additional DB2 log data.

User Response: To diagnose the problem, examine the other messages that were issued when the abend occurred. Then correct any errors and restart the ECCR. If the problem persists or cannot be identified, contact Informatica Global Customer Support.

PWXEDM177557E IFI RC=0 WITH IFCABM=0

Explanation: The DB2 ECCR issued an IFCID 306 READS call and received a return code of zero. However, while examining the data returned, the ECCR found that the length of the data returned (IFCABM) was zero. This situation indicates a logical error in the DB2-supplied IFCID 306 interface.

System Action: The DB2 ECCR ends without processing any additional DB2 log data.

User Response: To diagnose the problem, examine any other messages that were issued at the time of the abend, including messages for abends in the DB2 subsystem to which the DB2 ECCR connects.

Correct any errors that these messages describe, and then warm start the ECCR. If the problem persists or cannot be identified, contact Informatica Global Customer Support.

PWXEDM177559E UNEXPECTED {LENGTH|NUMBER|OFFSET} IN control_block_field

Explanation: The DB2 ECCR successfully issued a DB2 IFCID 306 READS call but found unexpected data formatting or content in the specified control block field of the returned log data. The control_block_field can be one of the following values:

• QWT01R1L

• QWT01R1N

• QWT01R1O

• QWT02R1L

• QWT02R1N

• QWT02R1O

System Action: The DB2 ECCR ends.

User Response: This message indicates that the data returned from the IFCID 306 READS call was incorrectly formatted. To diagnose the problem, look for other messages that might have been issued when the ECCR abend occurred, including messages for abends in the DB2 subsystem to which the DB2 ECCR connects. Then correct any errors that these messages describe and warm start the ECCR. If the problem persists or cannot be identified, contact Informatica Global Customer Support.

PWXEDM177560E ZERO RECORD OCCURRENCES IN QW0306CT

Explanation: The DB2 ECCR successfully issued an IFCID READS call but the QW0306CT count of data records in the returned log data was zero. This situation indicates a logical error in the DB2‑supplied IFCID 306 interface.

System Action: The DB2 ECCR ends.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 225

Page 226: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: To diagnose the problem, look for other messages that might have been issued when the ECCR abend occurred, including messages for abends in the DB2 subsystem to which the DB2 ECCR connects. Then correct any errors that these messages describe and warm start the ECCR. If the problem persists or cannot be identified, contact Informatica Global Customer Support.

PWXEDM177561E UNEXPECTED QWIWHDRL VALUE

Explanation: The DB2 ECCR successfully issued an IFCID 306 READS call but found that the returned QWIWHDRL value, which is length of all of the log data records returned, either was zero or did not match the length of the data returned. This situation indicates a logical error in the DB2‑supplied IFCID 306 interface.

System Action: The DB2 ECCR ends.

User Response: To diagnose the problem, look for other messages that might have been issued when the ECCR abend occurred, including messages for abends in the DB2 subsystem to which the DB2 ECCR connects. Then correct any errors that these messages describe and warm start the ECCR. If the problem persists or cannot be identified, contact Informatica Global Customer Support.

PWXEDM177562E IFI READS ERROR. WQALLMOD=parameter_value WQALLRBA=rba IFCARC1=return_code IFCARC2=reason_code.

Explanation: The DB2 ECCR issued an IFCID 306 READS call, but the resulting return code or reason code indicated an error. The WQALLMOD and WQALLRBA parameter values are input to the READS call. This message is also usually preceded by one or more additional ECCR messages that provide more information about the problem.

System Action: The DB2 ECCR ends.

User Response: To diagnose the problem, look for other messages that were issued when the ECCR abend occurred, including messages for abends in the DB2 subsystem to which the DB2 ECCR connects. Then correct any errors that these messages describe and warm start the ECCR. If the problem persists or cannot be identified, contact Informatica Global Customer Support.

226 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 227: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177563W In UOW uowid.data_sharing_member_id at log_rba_or_lrsn.data_sharing_member_id.sequence_number No Begin UOW for record_type

Explanation: While processing UR-type log records at startup, the DB2 ECCR encountered a UOW record for which a Begin UOW record does not exist.

In the message text, the record_type is one of the following values:

• Begin UOW

• Display Command

• Term Command

• End UOW

• Data Record

• Abort UOW

• Unknown type

• Find Oldest

• Build hash tab

• Stats display

• Begin Phase 1

• End Phase1

• Begin Phase2

• Phase 1/2 Tran

• End Todo

• End Phase2

• End Abort

• End Redo

• End Undo

Note: This situation can be normal unless you warm started the ECCR after a successful QUIESCE shutdown. If you did a cold start, a special start, or a warm start after a non-QUIESCE shutdown, in-flight UOWs might exist at the start point. In this case, the ECCR issues this warning message when it processes the UR records for these UOWs.

User Response: Processing continues.

System Action: If this message is issued at times other than restart, contact Informatica Global Customer Support.

PWXEDM177564W Possible missing End Commit2 for uowid.data_sharing_member_id at log_rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: The DB2 ECCR was processing a UR record for a UOW when it detected that a different UOW was in a questionable state and might be missing the End Commit2 record. For the ECCR to detect this situation, the specified outstanding UOW that is in a questionable state must have begun commit processing. That is, the ECCR encountered the Begin Phase2 UR record or Phase 1/2 Transition UR record for the UOW. This situation occurs only when the ECCR is reading at the very “edge” of the DB2 log data.

Subsequent message PWXEDM177565W identifies the last operation type that was encountered for this UOW, along with the DB2 log location at which the problem occurred.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 227

Page 228: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: Processing continues.

User Response: This situation can occur when the DB2 data-sharing member that is specified as part of the UOWID is not busy. This message can persist for up to three DB2 checkpoint cycles for the data-sharing member. If the message persists after the DB2 data-sharing member becomes busy or has gone through three DB2 checkpoint cycles, collect the following types of diagnostic information:

• An SVC dump for the DB2 ECCR and any started tasks for the DB2 subsystem or for data-sharing group members.

• JES output from the DB2 ECCR and the DB2 subsystem.

• Output from DB2 DSN1LOGP utility.

• Copies of the archive logs that contain the log data where this problem was encountered.

Then contact Informatica Global Customer Support.

PWXEDM177565W Last operation operation_type, at log_rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: This message provides information about the state of the DB2 change capture program at the point where either message PWXEDM177564W or PWXEDM177566W was issued. This message includes a description of the last operation or log record type that was processed for the UOW in question, along with the DB2 log location where the issue was detected.

In this message, the operation_type variable is one of the following values:

• Begin UOW

• Display Command

• Term Command

• End UOW

• Data Record

• Abort UOW

• Unknown type

• Find Oldest

• Build hash tab

• Stats display

• Begin Phase 1

• End Phase1

• Begin Phase2

• Phase 1/2 Tran

• End Todo

• End Phase2

• End Abort

• End Redo

• End Undo

System Action: Processing continues.

User Response: For more information, see message PWXEDM177564W or PWXEDM177566W.

228 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 229: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177566W No prior {Begin Phase2|Phase 1/2 Tran} for End Phase 2 for urid.data_sharing_member_id at log_rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: When processing a UR record of type End Phase 2 for a UOW, the DB2 ECCR detected that it had not received the proper sequence of UR records. This situation might mean that an intermediate UR record, such as a Begin Phase2 or Phase 1/2 Tran record, has not been encountered. This message includes the URID for the potentially incorrect UOW and the log location of the beginning of this UOW.

In the message text:

• "Begin Phase2" or "Phase 1/2 Tran" is the operation or record type that was expected but not encountered prior to the current record for this URID.

• "End Phase2" is the current record type.

• urid.data_sharing_member_id is the DB2-assigned URID. In a data-sharing environment, the member ID is included.

• log_rba_or_lrsn.data_sharing_member_id.sequence_number is the current log location where the Begin UR for this URID was encountered. In a data-sharing environment, the log LRSN and data-sharing member ID is reported.

Message PWXEDM177565W reports 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 record was found for this UOW, the UOW is captured correctly and available for further processing. However, because some of the expected UR records were not available, some data records might not have been captured.

User Response: Collect the following types of diagnostic information:

• An SVC dump for the DB2 ECCR and any started tasks for the DB2 subsystem or for data-sharing group members.

• JES output from the DB2 ECCR and the DB2 subsystem.

• Output from DB2 DSN1LOGP utility.

• Copies of the archive logs that contain the log data where this problem was encountered.

Then contact Informatica Global Customer Support.

PWXEDM177567E Capture Directory or DB2 catalog can not be properly accessed

Explanation: The DB2 ECCR cannot access a table either in the capture directory or in the DB2 catalog.

System Action: The DB2 ECCR abends.

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

PWXEDM177568E Rollback has failed

Explanation: The DB2 ECCR initialized a rollback process, and the DB2 rollback failed.

System Action: The DB2 ECCR abends.

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

PWXEDM177569E Internal error - Invalid call function for X029233

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 229

Page 230: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: The DB2 ECCR abends.

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

System Action: The DB2 ECCR abends.

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

System Action: The DB2 ECCR abends.

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

230 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 231: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177576E INTERNAL ERROR: UNEXPECTED RETURN CODE FROM PX029025

Explanation: The DB2 ECCR received an unexpected return code from the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177577W Capture for table creator.table_name deferred due to pending table alteration

Explanation: During DB2 for z/OS ECCR initialization processing after a warm start, special start, or REFRESH command, the ECCR detected a new table for which to capture change data. The ECCR retrieved the table definition from the DB2 catalog. However, when the ECCR was ready to start or resume processing of the DB2 log records, the ECCR determined that the new table was being altered. As a result, the ECCR did not have an accurate and consistent definition of the new table.

System Action: Processing continues. The ECCR does not capture change data for the new table until it encounters the DB2 log records that contain the latest DDL changes for the table.

User Response: No response is required. The ECCR issues this informational message for tracking the source tables of capture interest.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 231

Page 232: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177578I Clone creator.table_name is {added to | dropped from | exchanged with} table creator.table_name at timestamp

Explanation: When the DB2 for z/OS ECCR was processing DB2 log records, it detected that a clone table was added, dropped, or exchanged with its base table. The ECCR is currently capturing changes for the base table. This message provides the clone table name, base table name, and the timestamp for when the clone table change occurred. The timestamp format is yyy-mm-dd-hh.mm.ss.mmmmmm.

System Action: Processing continues. The ECCR continues to capture changes for the base table but does not capture changes for the associated clone table. If the clone table and base table have been exchanged, the ECCR captures changes from the new instance of the table.

User Response: The informational message is issued to help properly track the tables from which data is captured. If the clone table and base table have been exchanged, additional action might be required. The change data that the ECCR captures from the new instance of the table might be inconsistent with the change data that was captured from the previous instance of the table. If so, data inconsistency problems might occur when you attempt to apply the newly captured change data to the targets. To resolve this problem, rematerialize the targets.

PWXEDM177583W Table space file vsam_cluster_name allocation failed. RC=return_code, ERROR=error_code, INFO=info_code.

Explanation: During initialization, the DB2 for z/OS ECCR determined that it needed to get schema information for a table by dynamically allocating and reading the specified tablespace data set or partition data set that contains the table. However, the dynamic allocation request for the data set failed.

The ECCR issues this warning message to indicate a problem in capturing changes for this table might occur. This problem can occur only if you are using DB2 Version 9.1 or later.

This message includes the data set name, and the return code, error reason code, and information code returned from the dynamic allocation attempt. The ECCR also issues message PWXEDM177584W to identify the table, tablespace, and partition number that triggered the dynamic allocation request.

System Action: The ECCR terminates.

User Response: For more information about the error, see the subsequent error message PWXEDM177595E.

PWXEDM177584W Table table_name recalling vsam_cluster_data_set_name.

Explanation: The DB2 for z/OS ECCR determined that the specified VSAM cluster data set for a tablespace was migrated off disk. The cluster data set will be recalled.

System Action: The specified VSAM cluster data set is recalled.

User Response: No response is required.

232 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 233: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177585W Dynamic unallocation failed for dataset data_set_name, DDname=dd_name, RC=return_code, S99ERROR=error_code, S99INFO=info_code.

Explanation: During initialization, the DB2 for z/OS ECCR tried to get schema version information for a table. The ECCR gets this information by dynamically allocating and reading the tablespace data set or partition data set that contains the table. After processing the schema version information, the DB2 ECCR dynamically unallocates, or deallocates, the data set. However, the dynamic unallocation request failed. This error can occur only if you are using DB2 Version 9.1 or later.

This message includes the name of the data set that was being unallocated and the return code, error reason code, and information code returned from the dynamic unallocation request.

System Action: Processing continues. However, the failure to unallocate the data set might lead to resource problems in the ECCR later. For example, the TIOT entry that was used when the data set was allocated might not be freed, which could lead to the ECCR exhausting the available space in the TIOT.

User Response: To determine the reason for the unallocation failure, examine the return and reason codes that are reported in this message in conjunction with operating system documentation. You might need to recycle the ECCR to prevent future related problems. If you cannot determine the reason for the dynamic unallocation failure, contact Informatica Global Customer Support.

PWXEDM177586E Internal error - Invalid call function for X029234

Explanation: The DB2 ECCR encountered an invalid call function for the specified module. This is an internal error that causes the DB2 ECCR to abend.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177587E Internal error - Invalid {R2PTA | CCDTS | CCDTP} control block address or contents

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

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 233

Page 234: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177588E Table table_name file VSAM_cluster_data_set_name [pageset header|ODBREC record] error - error_description.

Explanation: During initialization, the DB2 for z/OS ECCR tried to get schema version information for the specified table by reading the tablespace data set or partition data set that contains the table. While processing the schema version information, the ECCR found invalid data in some data set pages.

This problem can occur only if you use DB2 Version 9.1 or later.

This message includes the type of record associated with the error, the tablespace or partition data set name, the fully-qualified table name, and a description of the error. The error_reason variable represents one of the following values:

• Inconsistent data in page

• 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: The ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the following diagnostic information:

• JES output from the ECCR.

• DB2 DSN1PRNT utility output for the tablespace or partition data set

To restart the ECCR, you need to remove the table from change capture processing and then perform a warm start.

234 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 235: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177589W Excessive schema version entries bypassed for creator.table_name in dataset data_set_name.

Explanation: During initialization, the DB2 for z/OS ECCR tried to get schema version information for the specified table by reading the tablespace data set or partition data sets for the table. While processing the schema version information, the ECCR found too many schema versions. The maximum number of schema versions is 100.

The ECCR records information for only the 100 most recent schema versions for the table. If the ECCR encounters log records with an older schema version, it issues this message to warn of a potential problem in capturing data for the table.

This problem can occur only if you use DB2 Version 9.1 or later.

This message includes the fully-qualified table name and the name of the tablespace or partition data set that was being processed when the problem occurred.

System Action: If the ECCR encounters log records with older schema versions, it might not interpret the log data correctly. In this case, the ECCR issues message PWXEDM177456E or PWXEDM177460E and reacts in one of the following ways, depending on the setting of the EC PERMIL statement in the REPL2OPT DD data set:

• If the EC PERMIL value is 0 or has been exceeded, the ECCR abends.

• If the EC PERMIL value has not be exceeded, the ECCR discards the log records.

Note: Normally, if you reorganized the tablespace or partition after making a schema change that incremented the schema version number, no rows in the table should been recorded with an older schema version.

User Response: If the ECCR encounters errors, follow the instructions in message PWXEDM177456E or PWXEDM177460E.

To prevent this problem from reoccurring in the future, reorganize the tablespace or partitions that contain this table. This action eliminates the older schema versions.

PWXEDM177590W Table table_name dataset VSAM_cluster_data_set_name access violation.

Explanation: During initialization, the DB2 for z/OS ECCR tried to get schema version information for the specified table by reading the tablespace data set or partition data set that contains the table. The ECCR could not open the specified data set. The ECCR issues this warning message to indicate that an access violation has occurred. This problem can occur only if you are using DB2 Version 9.1 or later.

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.

System Action: The ECCR ends.

User Response: For more information about the access violation, see the subsequent error message PWXEDM177595E.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 235

Page 236: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177592W Schema version entries bypassed for creator.table_name in dataset data_set_name - DSSIZE value unavailable.

Explanation: During initialization, the DB2 for z/OS ECCR tried to get information for determining the schema version for the specified table by reading the tablespace data set or partition data set that contains the table. However, the DSSIZE information was not available. This problem occurs because the columns in the PowerExchange capture directory tables for the supported schema version contain default values instead of the correct values from the DB2 catalog. The ECCR issues this warning message to indicate that it might encounter problems in capturing log data for the table.

This problem can occur only if you are using DB2 Version 9.1 or later.

The message text includes the fully-qualified table name, the name of the data set that the ECCR was processing, and the type of information that was not available.

System Action: Processing continues. The ECCR continues to capture changes for the table, even though some schema version information might be unavailable. If the ECCR reads log records for the table with an older schema version, the ECCR might not interpret that log data correctly. In this case, the ECCR issues message PWXEDM177456E or PWXEDM177460E and reacts in one of the following ways, depending on the setting in the EC PERMIL statement in the REPL2OPT DD data set:

• If the EC PERMIL value is 0 or has been exceeded, the ECCR abends.

• If the EC PERMIL value has not be exceeded, the ECCR discards the log records.

Note: Normally, if you reorganize the tablespace or partitions after making a schema change that increments the schema version, no rows in the table should be recorded with an older schema version.

User Response: If the ECCR encounters errors when capturing data for this table, follow the instructions in message PWXEDM177456E or PWXEDM177460E.

To prevent this problem from occurring in the future, use the sample SQL in the FIXTCAPC, FIXTCAPS and FIXTCAPT members of the PowerExchange SAMPLIB library to update the columns in the PowerExchange capture directory tables with the correct values from the DB2 catalog.

If this message persists after the SQL updates to the capture directory tables have been done, contact Informatica Global Customer Support.

PWXEDM177593E UNEXPECTED VALUE IN SCHEMA_VERSIONS COLUMN OF TCAPTABLES TABLE

Explanation: The DB2 ECCR found an incorrect value in the SCHEMA_VERSIONS column of the TCAPTABLES table. This is an internal error.

System Action: The DB2 ECCR abends.

User Response: Collect the complete DB2 ECCR job listing, including the SYSUDUMP output. Then, contact Informatica Global Customer Support.

236 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 237: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177594W Schema version processing bypassed for catalog tables: {Unable to find DSN6SPRM eyecatcher|Unable to find SPRMVCAT eyecatcher}

Explanation: During initialization, the DB2 ECCR could not find some information that is required to determine the schema version for the DB2 catalog tables. The ECCR tried to get this information from the DB2 DSNZPARM member. Verification checking of the returned information failed with this warning message, which identifies the information not found.

Although this schema version information is not required, it can help avoid ECCR abends. ECCR abends can occur if you use DB2 10 new-function mode or later and any of the DB2 catalog tables of interest to the ECCR are modified outside of a PowerExchange release boundary to either add columns or modify existing columns. For example, in DB2 Version 10, the catalog tables were modified to support reordered row format.

This warning message indicates that the ECCR might encounter problems processing DDL operations if the DB2 catalog tables have been modified.

System Action: Processing continues. If a DB2 catalog table has been modified in a manner that changes the fixed-length portion of its logged row image and Informatica is not aware of this schema change, the DB2 ECCR abends the first time it tries to process a DDL change for the catalog table.

User Response: Contact Informatica Global Customer Support.

PWXEDM177595E Failed to obtain RRF info for one or more tables. See previous warnings/errors.'

Explanation: During a DB2 ECCR start or refresh operation, the ECCR failed to obtain reordered row format (RRF) information for one or more tables.

System Action: DB2 ECCR processing ends.

User Response: Review the preceding error and warning messages. Then correct any issues that the messages identify and perform ECCR cold start, special start, warm start, or refresh operation again.

PWXEDM177596I Table 'creator.table_name' number_of_records compressed records skipped from rba1_or_lrsn1.data_sharing_member_id.sequence_number thru rba2_or_lrsn2.data_sharing_member_id.sequence_number

Explanation: The DB2 for z/OS ECCR skipped records for the specified table because they were not decompressed by DB2. This message identifies the number of compressed records that were skipped and the RBA or LRSN boundaries of the portion of the DB2 log that contain these records. This message is issued to the EDMMSG data set and as a WTO message.

System Action: ECCR processing continues because the ROWNOTDECOMPRESSED statement is set to NOFAIL in the REPL2OPT file.

User Response: No response is required. You can use this WTO message to automate alert notifications to the appropriate system users.

PWXEDM177597W Capture Directory table TCAPTABLES column SCHEMA_VERSIONS should be expanded to VARCHAR(768) FOR BIT DATA

Explanation: During initialization, the DB2 ECCR found that the SCHEMA_VERSIONS column in the TCAPTABLES capture directory table does not have the datatype VARCHAR(768).

System Action: Processing continues. Schema information might be discarded.

User Response: Contact Informatica Global Customer Support for instructions on how to run SQL to update table column.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 237

Page 238: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177598W Table creator.table_name schema information vv-nnnn discarded.

Explanation: The DB2 for z/OS ECCR discarded schema information for the specified table because the SCHEMA_VERSIONS column in the TCAPTABLES capture directory table is not VARCHAR(768). In the message text, vv is the schema version and nnnn is the fixed length of the schema version row.

System Action: Processing continues. The ECCR might not be able to process some change data.

User Response: Contact Informatica Global Customer Support for instructions on how to run SQL to update SCHEMA_VERSIONS column. You might also need to run SQL to recover the discarded schema version information.

PWXEDM177599E Table creator.table_name {before|normal} image version n is unknown at log_rba_or_lrsn.data_sharing_member_id.sequence_number

Explanation: When processing DB2 log records for the specified table, the DB2 for z/OS ECCR found data with an unknown image version at the specified location in the DB2 logs.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177601I DB2 {Product ID:|Catalog level:} global_variable_value

Explanation: This message reports the value of the PRODUCTID_EXT or CATALOG_LEVEL global variable that the DB2 for z/OS ECCR extracted.

System Action: CDC processing continues.

User Response: No response is required.

PWXEDM177605E Table creator.table_name version version: calculated value value1 does not match X029234 value value2

Explanation: For the schema version of the specified DB2 table, the calculated value does not match the value from the X029234 module.

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177606E Table creator.table_name could not find old schema version to discard

Explanation: The DB2 for z/OS ECCR encountered a new schema version for the specified table but could not find the old schema version to discard. The old schema version needs to be discarded so that the TCAPTABLES capture directory table can expand a column to VARCHAR(768).

System Action: Processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177611I LOG POSITION rba_or_lrsn.data_sharing_member_id

Explanation: This message reports the RBA or LRSN location of the last log record that the DB2 ECCR read. In a data-sharing environment, the message includes the data-sharing member ID. This message accompanies messages PWXEDM177612I and PWXEDM177613E and is related to the error reported in PWXEDM177613E.

System Action: After the DB2 ECCR generates messages PWXEDM177612I and PWXEDM177613E, the ECCR abends.

238 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 239: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: For information about the related error, see PWXEDM177613E.

PWXEDM177612I {QW0306ES|WQALLRBA|last returned} rba_or_lrsn

Explanation: This message reports one of the following the RBA or LRSN values for a DB2 for z/OS log location that was returned to the QW0306ES or WQALLRBA module or that was last returned:

• For QW0306ES, this value is the end-of-scope value that is returned by an IFI306 call.

• For WQALLRBA, this value is the location of the first-requested log record for an IFI306 'F' call (f).

• For last returned, this value is the location of the log record read just before the log record that is reported in the previous PWXEDM177611I message.

This message accompanies messages PWXEDM177611I and PWXEDM177613E and is related to the error reported in PWXEDM177613E.

System Action: After the DB2 ECCR generates message PWXEDM177613E, the ECCR abends.

User Response: For information about the related error, see PWXEDM177613E.

PWXEDM177613E DB2 READS LOGICAL FAILURE, LOG RECORDS(S) RETURNED {BEYOND END-OF-SCOPE|BEFORE READ POINT|BEFORE LAST RETURNED}

Explanation: The DB2 ECCR encountered out-of-sequence log records. The message indicates why the ECCR determined the records were out of sequence. Messages PWXEDM177611I and PWXEDM177612I, which immediately precede this one, provide more information about the error.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support. Provide Support with the complete DB2 ECCR job listing, including SYSUDUMP output.

PWXEDM177614E IFI RETURN AREA CONTAINS A DB2 LOG RECORD WITH INVALID LENGTH

Explanation: The DB2 for z/OS instrumentation facility interface (IFI) return area for a PowerExchange request contains a DB2 log record that has an invalid length.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177615E MORE THAN number_of_records LOG RECORDS WITH SAME LRSN lrsn

Explanation: The DB2 for z/OS ECCR detected that more than the specified number of log records have the same LRSN.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177617E INVALID TRACE OPTION option

Explanation: The DB2 ECCR does not recognize the specified trace option. This message is issued either when the ECCR reads the TRACE statements in the REPL2OPT DD data set at startup or when you enter the MVS F eccr_job_name,TR {ACT|INACT},trace_id command to start or stop a trace.

System Action: If a TRACE statement in the REPL2OPT data set contains an invalid option, the DB2 ECCR abends. If the TR command contains an invalid option, the ECCR ignores the command and continues processing.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 239

Page 240: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: In the REPL2OPT TRACE statement or the TR command, enter a valid option. For information about valid TRACE options, see the PowerExchange CDC Guide for z/OS. Alternatively, for the TR command, enter either the ACT or INACT option. For information about the TR command, see the PowerExchange Command Reference.

PWXEDM177618I TRACE OPTION {ACTIVE|INACTIVE|LEVEL n}

Explanation: This message reports the trace option that was used in a DB2 for z/OS ECCR TR command that completed successfully. This information is intended for use by Informatica Global Customer Support.

System Action: ECCR processing continues.

User Response: No response is required.

PWXEDM177619I table_name SQL routine failure. RSN=reason_code.

Explanation: The DB2 for z/OS ECCR encountered an internal error when executing an SQL routine for the specified source table. This message includes the reason code, which is a PowerExchange internal error code.

System Action: The SQL routine fails. ECCR error processing continues.

User Response: Contact Informatica Global Customer Support.

PWXEDM177653I Table creator.table_name {ADD|DROP} COLUMN column_name column_description at timestamp.

Explanation: The DB2 for z/OS ECCR encountered a DDL operation that added or dropped a column in the specified source table. This message includes the table name, the column name and description of the added or dropped column, and the DB2 timestamp at which the DDL operation occurred. The timestamp is in the format yyyy-mm-dd-hh.mm.ss.mmmmmm.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177654I Table creator.table_name ALTER COLUMN column_name column_description to new_description at timestamp.

Explanation: An ALTER COLUMN operation changed the definition of a column in the specified DB2 source table. This message includes the table name, the name of the altered column, the original column attribute, the new column attribute, and the DB2 timestamp at which the DDL operation occurred. The timestamp is in the format yyyy-mm-dd-hh.mm.ss.mmmmmm.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177655I Table owner.table_name ALTER COLUMN column_name puts table space in AREO* status.

Explanation: An ALTER COLUMN operation on a column in a source table caused the table space status to change to AREO*. This message is issued as a write-to-operator (WTO) message and written to the message log. The message includes the table name and the name of the altered column.

System Action: Processing continues.

User Response: No response is required.

240 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 241: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177656I Table owner.table_name ALTER COLUMN column_name1 RENAME to column_name2 at timestamp.

Explanation: An ALTER COLUMN RENAME operation on the specified source table renamed a column. The message includes the table name, the new column name, and the previous column name.

System Action: Processing continues.

User Response: No response is required.

PWXEDM177659E Table table_name column column_name column type column_type not recognized

Explanation: While calculating the fixed-length portion of DB2 table rows in reordered row format, the DB2 for z/OS ECCR encountered a column type that it does not recognize. This message specifies the table that contains the column and the column name.

System Action: The ECCR ends abnormally.

User Response: Contact Informatica Global Customer Support.

PWXEDM177674E UNEXPECTED QW0306RS AT rba_or_lrsn.data_sharing_member_id RC=return_code RS=reason_code DG=diagnostic_code

Explanation: The DB2 ECCR encountered an IF306 error when reading a log record at the specified location.

System Action: The DB2 ECCR ends.

User Response: Collect the following diagnostic information:

• SYSUDUMP, SYSABEND, or SYSMDUMP output from the job.

• Print output from the DB2 DSN1LOGP utility for the log record.

To determine if the error is transient, try to warm start the ECCR. If the restart fails, contact Informatica Global Customer Support. Provide Support with the diagnostic information that you collected.

PWXEDM177675I DB2 DBID database_identifier PSID page_space_identifier OBID object_identifier RID row_identifier

Explanation: This message supplements error message PWXEDM177674E. When the DB2 IFI detects an error with a log record that contains data, this message provides additional information from the record for diagnostic use. The reported values are in hexadecimal format. For more information about these fields, see the DB2 documentation.

System Action: DB2 ECCR processing continues.

User Response: No response is required.

PWXEDM177676I Table creator.table_name

Explanation: This message supplements error message PWXEDM177674E. When the DB2 IFI detects an error with a log record that contains data, this message provides additional information from the record for diagnostic use. This message identifies the table associated with the error.

System Action: DB2 for z/OS ECCR processing continues.

User Response: No response is required.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 241

Page 242: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM177680E EDM INTERFACE ERROR: RC=return_code RSN=reason_code FUNC=function request_type

Explanation: The change interface component (CIC) encountered an internal error and returned control to the DB2 ECCR. The CIC also passed the return code and reason code to the DB2 ECCR.

System Action: The DB2 ECCR abends.

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.

PWXEDM177681I ... internal diagnostics ...

Explanation: The DB2 ECCR encountered an unusual condition and generated the internal diagnostic information that this message reports.

System Action: DB2 ECCR processing continues.

User Response: No response is required.

PWXEDM177690E module1 received unexpected module2 return code hex_return_code

Explanation: An internal error occurred. The specified DB2 ECCR module or routine received a return code for an error from another module or routine.

System Action: The DB2 ECCR abends.

User Response: Contact Informatica Global Customer Support.

PWXEDM177691I DB2 ECCR ESTAE ENTERED. [ABEND CODE code PSW psw_value.]

Explanation: The DB2 for z/OS ECCR ended. This message is usually issued for an ECCR initialization error, such as one caused by an incorrect control card in the ECCR JCL. The message includes the abend code and PSW information only when appropriate.

System Action: Capture processing stops.

User Response: Contact Informatica Global Customer Support.

PWXEDM177692I Diagnostic information follows.

Explanation: This message introduces internal diagnostic information related to the DB2 for z/OS ECCR for Informatica Global Customer Support use.

User Response: No response is required.

PWXEDM177694E program_name called with invalid parameter_list value X'xx'

Explanation: An internal error occurred. The specified DB2 ECCR program was called with an invalid parameter list.

System Action: The DB2 ECCR abends.

User Response: Collect the SYSUDMP, SYSABEND, or SYSMDUMP output from the ECCR job. Then contact Informatica Global Customer Support.

PWXEDM177695E function_name INVALID CALL FUNCTION VALUE value

Explanation: An internal error occurred. The specified DB2 ECCR function was called with an invalid request.

System Action: The DB2 ECCR abends.

242 Chapter 5: PWXEDM176400 to PWXEDM177699

Page 243: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Collect the SYSUDMP, SYSABEND, or SYSMDUMP output from the ECCR job. Then contact Informatica Global Customer Support.

PWXEDM177696E function_name INVALID FUN2 VALUE subfunction_value FOR FUNCTION function_value

Explanation: An internal error occurred. The specified DB2 ECCR function was called with an invalid subfunction request.

System Action: The DB2 ECCR abends.

User Response: Collect the SYSUDUMP, SYSABEND, or SYSMDUMP output from the ECCR job. Then contact Informatica Global Customer Support.

PWXEDM177697E SQL ERROR: OPERATION sql_operation TABLE table_name

Explanation: The DB2 ECCR tried to execute the specified SQL operation for the table but the operation failed.

System Action: The DB2 ECCR abends.

User Response: To diagnose the failure, see the messages that precede this one in the DB2 ECCR EDMMSG output. If the problem is correctable, correct the problem and restart the ECCR. Otherwise, collect the SYSUDUMP, SYSABEND, or SYSMDUMP ouput from the ECCR job and then contact Information Global Customer Support.

PWXEDM177698E function_name detected missing or invalid block control_block at address

Explanation: An internal error occurred. The specified DB2 ECCR function determined that the specified control block was missing or contained invalid input for the ECCR.

System Action: The DB2 ECCR abends.

User Response: Collect the SYSUDUMP, SYSABEND, or SYSMDUMP ouput from the ECCR job. Then contact Informatica Global Customer Support.

PWXEDM177699W Table creator.table_name column column_name: column type default used in place of user default

Explanation: While processing the DEFAULTVALUE value for the specified column, the DB2 for z/OS ECCR determined that it could not use the user default value.

System Action: Processing continues.

User Response: Collect diagnostic information from the EDMMSG and REPL2TRA files. Then contact Informatica Global Customer Support.

PWXEDM177012I to PWXEDM177699W: DB2 ECCR 243

Page 244: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 6

PWXEDM181200 to PWXEDM181599

This chapter includes the following topics:

• PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent, 244

• PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities, 248

PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent

PWXEDM181200E module: Dynamic LPA operation_name operation for module module_name failed, RC=return_code, Rsn=reason_code

Explanation: A module, using the MVS dynamic LPA service (CSVDYLPA), failed while attempting to add a load module into the Link Pack Area (LPA).

System Action: The PowerExchange Agent processing ends.

User Response: See the MVS documentation for the CSVDYLPA service to determine the reason for the error, then take action to correct the error accordingly.

PWXEDM181201E module: Cannot locate CDE for module module_name after CSVDYLPA

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

System Action: The PowerExchange Agent subtask processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM181202I module: function QName=qname RName=rnamestatus

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

User Response: If the function was successful, no response is required. If the function failed, a subsequent message further describes the error.

244

Page 245: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM181203E module %%: Cannot change RepositoryMode on Agent warm startX. RepositoryMode=%% remains in effect.

Explanation: During a warm start of the PowerExchange Agent, 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.

System Action: The PowerExchange Agent continues, but the indicated RepositoryMode remains in effect.

User Response: If it is desired to change the RepositoryMode setting, shut down all other PowerExchange tasks that use this PowerExchange 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.

PWXEDM181204I module %%: Current RepositoryMode is %%.

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

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM181205E module %%: DYNALLOC deallocation failed. DDname=%%,RC=%%,ErX ror code=%%,Info code=%%

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

System Action: The dynamic deallocation fails and the function that issued the request may also fail.

User Response: If the cause of the error cannot be determined, contact Informatica Global Customer Support.

PWXEDM181206I module ##: %%

Explanation: This message is issued to augment and further describe one or more following messages.

System Action: Not affected directly by this message.

User Response: Depends on the circumstances that caused the message to be issued.

PWXEDM181207I module ##: Repository Configuration Parameters (%%):

Explanation: The repository configuration file is about to be processed.

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM181208E module ##: Error in repository configuration file %%

Explanation: An error was found in a repository configuration file. The error is described in subsequent messages.

System Action: The repository configuration is not used.

PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent 245

Page 246: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Determine the cause of the error, edit the repository configuration file and reopen the repository.

PWXEDM181209E module ##: Error with repository cache data sets:

Explanation: An error was found in a repository configuration file. The error is described in subsequent messages.

System Action: The repository configuration is not used.

User Response: If the cause of the error cannot be determined, contact Informatica Global Customer Support.

PWXEDM181210I module ##: Soft error in cache %% (%%)

Explanation: This message is issued when a soft error is detected in a cache.

System Action: Normal processing continues.

User Response: Depends on the circumstances that caused the message to be issued.

PWXEDM181211I module ##: Cache %% newer than %%

Explanation: This message is issued when caches are not the same.

System Action: Normal processing continues.

User Response: Depends on the circumstances that caused the message to be issued.

PWXEDM181212I module ##: Using cached capture registrations (%%)

Explanation: This message is issued when cached registrations are used.

System Action: Normal processing continues.

User Response: Depends on the circumstances that caused the message to be issued.

PWXEDM181213E module ##: Repository access error:

Explanation: An error was encountered accessing the repository. The error is described in subsequent message(s).

System Action: The currently loaded registrations (if any) continue to be used. The system retries every update interval.

User Response: If the cause of the error cannot be determined, contact Informatica Global Customer Support.

PWXEDM181214I module ##: Repository access (re)established

Explanation: Repository access has been established for the first time or has been reestablished after an error was encountered.

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM181215I module ##: New capture registrations (%%)

Explanation: New capture registrations have been loaded.

System Action: Normal processing continues.

User Response: No response is required.

246 Chapter 6: PWXEDM181200 to PWXEDM181599

Page 247: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM181216I module : Repository status follows:

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

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM181217I module : repository_status_information

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

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM181218I module : Repository status follows:

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

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM181219I module ##: Updated capture registrations (%%)

Explanation: This message is issued when registrations are updated as a part of open processing and the change identifier is the same.

System Action: Normal processing continues.

User Response: Depends on the circumstances that caused the message to be issued.

PWXEDM181220E module: Repository helper subtask ABENDed,Code=abend_code,Reason=reason_code

Explanation: This message is issued when the main repository task detects that the helper subtask has abnormally terminated.

System Action: Repository helper subtask is not restarted.

User Response: Determine the cause of the ABEND, issue REPCLOSE and REPOPEN commands to restore helper subtask or contact Product Support for assistance.

PWXEDM181221E module: Memory usage is increasing

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

System Action: Normal processing continues.

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

PWXEDM181200E to PWXEDM181223I: The PowerExchange Agent 247

Page 248: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM181222E module : Memory usage %% the line is %% percent of the region limit

Explanation: This message is issued when the main repository task detects that agent memory usage has increased to be too close to the limit. It is 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.

System Action: Normal processing continues.

User Response: A PWXEDM181117 message detailing current memory usage follows this message. The maximum region size of the PowerExchange Agent task should be increased.

PWXEDM181223I module : repository_module_build_information

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

System Action: Normal processing continues.

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

User Response: Contact Informatica Global Customer Support.

PWXEDM181301I module: DETAIL Service Aid. Version version.release.modification

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

User Response: No response is required.

PWXEDM181302I module: Processing terminated, RC=return_code

Explanation: The execution of the PowerExchange service aid utility ended with the specified return code.

System Action: The service aid utility processing ends.

User Response: Correct the error and run the job again.

PWXEDM181303E module: OPEN of ddname file failed

Explanation: A module made an unsuccessful attempt to open the specified file. Processing of the file ends.

248 Chapter 6: PWXEDM181200 to PWXEDM181599

Page 249: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

System Action: If the data definition name variable equals REPORT, then the PowerExchange service aid utility processing ends.

User Response: If the data definition name variable equals REPORT, supply a valid file name and run the job again. Otherwise, contact Informatica Global Customer Support.

PWXEDM181304E module: GETMAIN failed for initialization control block

Explanation: The PowerExchange service aid utility could not obtain the storage required for its initialization processing.

System Action: The PowerExchange service aid utility processing ends.

User Response: Increase the region size and restart the PowerExchange service aid utility.

PWXEDM181305E module: GETMAIN failed for Options area {EDMSDIR|EDMLEVEL|EDMUPARM}

Explanation: The PowerExchange service aid utility could not obtain the storage required for its options load module areas.

System Action: The PowerExchange service aid utility processing ends.

User Response: Increase the region size and restart the PowerExchange service aid utility.

PWXEDM181306E module: LOAD failed. Module=module_name, Code=abend_code, Reason=reason_code

Explanation: A module issued a load macro, but the MVS Contents Supervision program could not locate the specified module.

System Action: The PowerExchange service aid utility processing ends.

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

PWXEDM181307E module: Module compare: Old old_EDMLEVEL not in DD new_EDMLEVEL

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

User Response: Include an EDMLEVEL DD statement that points to the library that contains the old EDMLEVEL load module.

PWXEDM181308E module: Compare: Old=New DSN: data_set_name

Explanation: An EDMLEVEL compare request tried to compare the same data set. The PowerExchange service aid utility processing ends for the compare function.

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

PWXEDM181309E module: EDMLEVEL compare error

Explanation: An EDMLEVEL compare request abended in the EDMUREPC module. The PowerExchange service aid utility processing ends for the compare function.

User Response: Contact Informatica Global Customer Support.

PWXEDM181310E module: Invalid or duplicate input parm; must be: ALL, SDIR, UPRM, LEVL, CLEV, UBLD

Explanation: A module encountered an invalid or duplicate input parameter. The PowerExchange service aid utility processing ends for the function.

PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities 249

Page 250: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: Remove the duplicate parameter or enter a valid parameter.

PWXEDM181311E module: Unexpected EOD for DD ddname

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

System Action: The PowerExchange service aid utility processing ends.

User Response: Contact Informatica Global Customer Support.

PWXEDM181312I module: module_name NOT in DD ddname

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

User Response: Ensure that the $CNTL module exists in the data set.

PWXEDM181313I module: module_name source module build failed

Explanation: The build failed for the specified source module. The PowerExchange service aid utility does not build the EDMUDESC source module, and processing continues.

User Response: Correct the error by using the EXEC statement with the UBLD parameter.

PWXEDM181314I module: module_name source build completed successfully

Explanation: The build completed successfully for the specified source module. The PowerExchange service aid utility processing continues.

User Response: No response is required.

PWXEDM181315I module: ASM and Link source module: module_name

Explanation: The build process successfully completed for a source module. The PowerExchange service aid utility processing continues.

User Response: Assemble and link the specified module.

PWXEDM181316I module: Error in module_name. Can't build source source_name

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

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

PWXEDM181317I module: module_name failed for DD ddname

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

User Response: Correct the error and restart the PowerExchange service aid utility.

PWXEDM181318I module: DISP=OLD not specified for DD ddname

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

User Response: Correct the error and restart the PowerExchange service aid utility.

250 Chapter 6: PWXEDM181200 to PWXEDM181599

Page 251: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM181319I module: STOW failed during operation_name for DD ddname

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

User Response: Correct the error and restart the PowerExchange service aid utility.

PWXEDM181320I module: No descriptive ZAP and LMOD info available

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

User Response: If the $CNTL source module is available, execute the PowerExchange service aid utility with PARM=UBLD and assemble and link the EDMUDESC load module.

PWXEDM181500W Repository access through the agent, not by xxxxxxx DD statement

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

User Response: Remove the DD statement for the repository from the EDM Marker utility JCL.

PWXEDM181300W to PWXEDM181500W: PowerExchange Service Aid Utilities 251

Page 252: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 7

PWXEDM261000 to PWXEDM263999

This chapter includes the following topics:

• PWXEDM261000I to PWXEDM261010I: The Logger API, 252

• PWXEDM263000I to PWXEDM263039W: The Log Read API, 253

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}

Explanation: The Log Write API has initialized. The API initialization options are listed.

User Response: No response is required.

252

Page 253: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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 listUOW ------------------------------------SEQ ------------- Status----xxxxxxxx cccccccc ddddddddeeeeeeeeeeee {in-doubt|in-flight}No UOWs on active listNo 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.

User Response: No response is required.

PWXEDM263000I to PWXEDM263039W: The Log Read API

This section contains messages for the Log Read API function.

PWXEDM263000I Log Read API Initialized: Header Version nnn

Explanation: The Log Read API has initialized for header version nnn.

User Response: No response is required.

PWXEDM263001I Log Read API external parameters:

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

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM263002I echo_of_external_parameter

Explanation: This message echoes the control statement read from the EDMLPRM DD statement during initialization of the Log Read API.

System Action: Normal processing continues.

User Response: No response is required.

PWXEDM263000I to PWXEDM263039W: The Log Read API 253

Page 254: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM263003E Error in control card: error_description

Explanation: This message is issued when an error has been encountered in one of the control statements read from the EDMLPRM DD statement. It is issued after the 263002 message that echoed the text of the control statement. Error_description is 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: Correct the errors in the control statement and restart the Log Read API process.

PWXEDM263010I Logger xxxxxx (yyyyyyyy): Connecting using agent zzzz

Explanation: For PowerExchange logger xxxxxx using Read API token yyyyyyyy, the PowerExchange Log Read API connects to the logger using PowerExchange Agent zzzz.

User Response: No response is required.

PWXEDM263011I Logger xxxxxx (yyyyyyyy): Opening to read from aaaaaaaaaaaaaaaaaaa to bbbbbbbbbbbbbbbbbb.

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

In the message text, bbbbbbbbbbbbbbbbbb is one of the following values:

• All 0s. Indicates a request to read until EOF.

• All Fs. Indicates a non ending reader.

User Response: No response is required.

PWXEDM263012I Logger xxxxxx (yyyyyyyy): Disconnecting

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, is disconnecting from the Logger.

User Response: No response is required.

PWXEDM263013I Log Read API Terminating

Explanation: The PowerExchange Log Read API is ending.

User Response: No response is required.

254 Chapter 7: PWXEDM261000 to PWXEDM263999

Page 255: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

PWXEDM263014I Logger xxxxxx (yyyyyyyy): Closing

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

User Response: No response is required.

PWXEDM263015I Logger xxxxxx (yyyyyyyy): Logger selects starting sequence number

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, is requesting that the Logger determine the earliest available starting sequence number.

User Response: No response is required.

PWXEDM263020I Logger xxxxxx (yyyyyyyy): Incomplete segmented record discarded

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

User Response: No response is required.

PWXEDM263021I RBA range aaaaaaaaaaaaaaaaaaa to bbbbbbbbbbbbbbbbbb found by record at RBA ccccccccccccccccccc

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

User Response: No response is required.

PWXEDM263025I Logger xxxxxx (yyyyyyyy): EDMNAME filter list contains the following nnnn entries:

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

User Response: No response is required.

PWXEDM263026I Logger xxxxxx (yyyyyyyy): zzzz

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, has EDMNAME zzzz in the EDMNAME filter list.

User Response: No response is required.

PWXEDM263027I Logger xxxxxx (yyyyyyyy): empty EDMNAME filter list set

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, has an empty EDMNAME filter list. No change records are returned.

User Response: No response is required.

PWXEDM263028I Logger xxxxxx (yyyyyyyy): EDMNAME filter list cleared

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, has cleared the EDMNAME filter list. All change records are returned.

Note: This message can appear as a result of an explicit request to clear the list or in the course of setting a new list.

User Response: No response is required.

PWXEDM263000I to PWXEDM263039W: The Log Read API 255

Page 256: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

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.

User Response: No response is required.

PWXEDM263031E Logger xxxxxx (yyyyyyyy): SEDM EDMNAME list duplicate: zzzzz

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, encountered a duplicate EDMNAME, zzzzz, while building the EDMNAME filter list.

User Response: No response is required.

PWXEDM263032W Logger xxxxxx (yyyyyyyy): aaaa failed: rc=0xbbbbbbb rsn=0xcccccccc [reason_text]

Explanation: When the Log Read API for the specified Logger used a specific Read API token and call, the Logger failed with the reported return code and reason code. See message PWXEDM263033I for additional internal return codes.

In this message:

• xxxxxx is the Logger ID or the text "API."

• yyyyyyyy is the Log Read API token value.

• aaaa is the call.

• 0xbbbbbbb is the return code.

• 0xcccccccc is the reason code.

• reason_text is the reason code explanation.

Note: If "API" appears, the failure occurred before or during connection to the Logger.

User Response: Contact Informatica Global Customer Support.

PWXEDM263033W Logger xxxxxx (yyyyyyyy): (internal code 0xxaaaaaaa 0xxbbbbbbbb)

Explanation: A Log Read API function failed. This message provides diagnostic information for use by Informatica Global Customer Support. Often, the reported values are PowerExchange return and reason codes. In the message text:

• xxxxxx is the PowerExchange Logger identifier.

• yyyyyyyy is the LRAPI token.

User Response: Contact Informatica Global Customer Support.

PWXEDM263035I Logger xxxxxx (yyyyyyyy): Subtask ended; rc=0xaaaaaaaa

Explanation: The Log Read API, for Logger xxxxxx using Read API token yyyyyyyy, helper subtask ended with return code aaaaaaaa. See related message PWXEDM263032W.

User Response: Contact Informatica Global Customer Support.

PWXEDM263036E Logger xxxxxx (yyyyyyyy): Received ECMD aaaa reply with rc=0xbbbbbbbb rsn=0xcccccccc

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

256 Chapter 7: PWXEDM261000 to PWXEDM263999

Page 257: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

User Response: No response is required. unless message PWXEDM263032W is also issued. In this case, contact Informatica Global Customer Support.

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.

User Response: Contact Informatica Global Customer Support.

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.

User Response: Contact Informatica Global Customer Support.

PWXEDM263039W Logger xxxxxx (yyyyyyyy): Unsupported Service Record: aaaaa

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

User Response: Contact Informatica Global Customer Support.

PWXEDM263040I Logger xxxxxx (yyyyyyyy): using DDN_file for subsystem_dataset_name

Explanation: This informational message reports the DDN file and subsystem data set name that the PowerExchange Log Read API (LRAPI) uses to read data from the PowerExchange Logger for z/OS. In the message text:

• xxxxxx is the PowerExchange Logger identifier.

• yyyyyyyy is the LRAPI token.

User Response: No response is required.

PWXEDM263090E Unable to obtain or locate MVS Name/Token

Explanation: The PowerExchange Log Read API (LRAPI) was not able to establish an z/OS name or token for identifying itself.

System Action: The z/OS system produces an SVC dump. This message appears as the title of the dump.

User Response: Contact Informatica Global Customer Support.

PWXEDM263000I to PWXEDM263039W: The Log Read API 257

Page 258: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

C h a p t e r 8

Abend, Return, and Reason Codes in PowerExchange Messages

This chapter includes the following topics:

• Abend, Return, and Reason Codes Overview, 258

• IBM Product Return and Reason Codes, 259

• PowerExchange Abend Codes, 259

• PowerExchange Return Codes, 260

• PowerExchange Reason Codes, 263

Abend, Return, and Reason Codes OverviewSome 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.

258

Page 259: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

IBM Product Return and Reason CodesSome return and reason codes provided by PowerExchange are created by the z/OS operating system or by another IBM product. For explanations of these codes, see the appropriate IBM z/OS, IMS, VSAM, or DB2 documentation. Examples of IBM documents that contain explanations of return codes include:

• DFSMS: DFSMSdfp Diagnosis

• z/OS Programming: Authorized Assembler Services Guide

• z/OS Programming: Authorized Assembler Services Reference

• IMS Messages and Codes

• DB2 for z/OS Messages

• DB2 for z/OS Codes

PowerExchange Abend CodesAbend 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 z/OS operating system or another IBM product. For explanations of these abend codes, see the appropriate IBM z/OS, IMS, VSAM, or DB2 documentation.

Abend Code U0001 - PowerExchange AgentThe 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.

The following table describes the related reason codes for abend code U0001:

Reason Code Explanation

00000001 The PowerExchange Agent detected an invalid initialization work area (EDMSIWRK) or pointer.

00000002 The PowerExchange Agent detected an invalid agent global control area (EDMSCTRL) or pointer.

00000003 The PowerExchange Agent detected an invalid ACB or pointer.

00000004 The PowerExchange Agent detected an invalid RPL or pointer.

00000005 The PowerExchange Agent detected an invalid SUBSYS I/O work area (EDMSSIOW) or pointer.

00000006 The PowerExchange Agent detected an invalid subtask work area (EDMSSTSK) or pointer.

00000007 The PowerExchange Agent detected a corrupted storage area chain.

00000101 The PowerExchange Agent detected a zero length SUBSYS I/O PUT request.

IBM Product Return and Reason Codes 259

Page 260: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00000102 The PowerExchange Agent could not find a SUBSYS I/O buffer.

00000103 The PowerExchange Agent detected a locate mode SUBSYS I/O PUT request.

00000201 The PowerExchange Agent did not pass any parameters to the lock manager.

00000202 The PowerExchange Agent passed a bad function code or operand to the lock manager.

00000203 The lock manager could not obtain storage.

00000204 The PowerExchange Agent passed an invalid ASCB and/or TCB address to the lock manager.

00000205 The PowerExchange Agent made a request for a lock that was lower in the lock hierarchy than a lock already being held.

00000301 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 ECCRThe Batch VSAM environmental change capture routine (ECCR) issues the U356 abend code to indicate that Batch VSAM ECCR abended.

Abend Code U3035 - PowerExchange LoggerThe PowerExchange Logger for z/OS issues the U3035 user abend code to indicate the PowerExchange Logger abended.

Abend Code U3680 - DB2 ECCRThe DB2 environmental change capture routine (ECCR) issues the U3680 user abend code to indicate the DB2 ECCR abended.

The DB2 ECCR usually issues a related reason code. The DB2 ECCR generates this reason code based on the number or name of the module that issues 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.

PowerExchange Return CodesAfter 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.

260 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 261: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Some return codes provided by PowerExchange are created by the z/OS operating system or another IBM product. For explanations of these return codes, see the appropriate IBM z/OS, IMS, VSAM, or DB2 documentation.

Return Codes 0 to 12 - StandardLists values for the standard return codes. The return code values increase as the degree of severity increases.

The following table describes return codes 0 to 12:

Return Code

Explanation

0 Indicates successful execution of the program, component, or module without warnings or errors.

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

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

Return Codes 1 to 412 - CommonSome 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.

The following table lists these common return codes and provides an explanation of each code:

Decimal Return Code

Explanation

1 The requested item or function was not found.

2 The system found a duplicate of the requested function or item.

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

12 The system must not call PowerExchange again.

PowerExchange Return Codes 261

Page 262: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Decimal Return Code

Explanation

16 A critical error occurred.

17 A security error occurred.

411 A task abnormally ended (abended).

412 The shutdown timer ended.

Return Codes 0 to 12 - PowerExchange AgentThe PowerExchange Agent issues return codes from 0 through 12.

The following table lists the return codes that the PowerExchange Agent issues:

Decimal Return Code

Explanation

0 See “Return Codes 0 to 12 - Standard” on page 261.

4 See “Return Codes 0 to 12 - Standard” on page 261.

8 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 “Reason Codes 001 to 255 - PowerExchange Agent” on page 264 for these reason codes.

12 The PowerExchange Agent encountered a severe general error. The severity of the error prevented the PowerExchange Agent from returning a reason code.

Return Code 221: PowerExchange LoggerThe following table lists the return code that the PowerExchange Logger issues:

Hexadecimal Return Code

Explanation

00DD 221 A general error occurred.

The following table lists the return codes that the Batch VSAM environmental change capture routine (ECCR) issues:

Decimal Return Code

Explanation

0 The Batch VSAM ECCR change capture module is active.

4 The specified module is initialized but is not active.

8 The specified module has not been initialized.

262 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 263: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Return Codes 0 to 8 - Batch VSAM ECCRThe batch VSAM environmental change capture routine (ECCR) issues return codes from 0 through 8.

The following table lists the return codes that the Batch VSAM environmental change capture routine (ECCR) issues:

Decimal Return Code

Explanation

0 The Batch VSAM ECCR change capture module is active.

4 The specified module is initialized but is not active.

8 The specified module has not been initialized.

PowerExchange Reason CodesReason 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 z/OS operating system or another IBM product.

For explanations of these reason codes, see the appropriate IBM z/OS, 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 z/OS manual cited in the message that returns the reason code.

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 - CommonSeveral internal components of PowerExchange use a common set of reason codes.

The following table lists these reason codes with explanations for each code:

Reason Code Explanation

xxxx0800 A general program error occurred.

xxxx0801 An invalid function code was found.

xxxx0802 An invalid token was found.

xxxx0803 A common token was not found.

PowerExchange Reason Codes 263

Page 264: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

xxxx0804 A GETMAIN error occurred.

xxxx0805 A DD name was not found.

xxxx0806 A program LOAD error occurred.

xxxx0807 A circular queue problem occurred.

xxxx0808 You are not authorized for this function.

xxxx0809 An OPEN failed.

xxxx080A The component was not able to obtain the supervisory state.

xxxx080B An error occurred while processing a FREEMAIN function.

xxxx080C A program DELETE error occurred

Note: Because any module can issue these codes, the variable xxxx represents the first two bytes (four hexadecimal characters) of the reason code.

Reason Codes 001 to 255 - PowerExchange AgentThe PowerExchange Agent issues the following 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.

The following table describes this type of reason code:

Decimal Reason Code

Hexadecimal Reason Code

Explanation

001 001 A private STORAGE OBTAIN failed.

002 002 A private STORAGE OBTAIN for less than 16M bytes failed.

003 003 A common STORAGE OBTAIN failed.

004 004 A common STORAGE OBTAIN for less than 16M bytes failed.

005 005 MVS is not at the required SP level.

006 006 A RACROUTE AUTH call failed.

007 007 An AUTH call, which is not a RACROUTE AUTH call, failed.

008 008 An internal logic error occurred in the module that is calling the PowerExchange Agent. It did not send the correct password key.

264 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 265: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Decimal Reason Code

Hexadecimal Reason Code

Explanation

009 009 The required PowerExchange subsystem data space does not exist.

010 00A The PowerExchange subsystem could not be found.

011 00B A subsystem was found, but it is not an PowerExchange subsystem.

012 00C An attempt to load the EDMSDIR module failed.

013 00D The EDMXCIRQ circular queue returned an error.

014 00E The global queue does not exist.

015 00F The calling module did not pass an PowerExchange queue handle.

016 010 The calling module passed a queue handle, but the handle has an incorrect version number or format.

017 011 The calling module did not pass an PowerExchange handle.

018 012 The calling module passed an PowerExchange handle, but the PowerExchange handle has an incorrect version number or format.

019 013 The PowerExchange subsystem initialization (EDMSINIT) has not been performed.

020 014 An PowerExchange subsystem initialization (EDMSINIT) was attempted; however, it is already initialized.

021 015 An EDMSCTRL pointer is missing or invalid.

022 016 The address space creation macro (ASCRE) failed.

023 017 The address space creation macro (ASCRE) failed because another component sent the PowerExchange Agent an invalid address space name.

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

025 019 The PowerExchange Agent attempted to create the global queue; however, it already exists.

026 01A The PowerExchange Agent is processing a DRAIN command.

027 01B The PowerExchange Agent completed processing for a DRAIN command.

028 01C The EDMSASIN module terminated the address space creation macro (ASCRE).

029 01D The PowerExchange Agent received a SHUTDOWN COMPLETELY command and was completely shut down.

PowerExchange Reason Codes 265

Page 266: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Decimal Reason Code

Hexadecimal Reason Code

Explanation

030 01E A dynamic allocation (DYNALLOC) for the subsystem DD failed.

031 01F The global queue received a request from a program with an invalid ASID.

032 020 There was a mismatch with the global queue sequence number.

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

036 024 The PowerExchange Agent received an invalid repository command.

037 025 An error occurred with an RIOM call.

040 028 The PowerExchange Agent found that data was truncated.

045 02D The module currently holds or has obtained the lock.

046 02E The module does not currently hold the lock.

047 02F The requested lock was unavailable.

048 030 The lock is not held and cannot be obtained because of hierarchy rules.

060 03C The SIOW area could not obtain storage.

061 03D The resource manager could not obtain storage.

062 03E The task work area could not obtain storage.

063 03F The global queue handler could not obtain storage.

070 046 A bad STOKEN occurred during an EDMSRMGR call.

071 047 A bad TCB occurred during an EDMSRMGR call.

072 048 The EDMSRMGR TCB is not in the home ASID.

230 0E6 The PowerExchange Agent does not allow SRB mode callers.

239 0EF A request timed out.

240 0F0 An illogical function request occurred.

241 0F1 A required subsystem or subtask is not active.

242 0F2 An OPEN command failed.

243 0F3 A CLOSE command failed.

244 0F4 The PowerExchange Agent encountered and invalid data set name.

266 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 267: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Decimal Reason Code

Hexadecimal Reason Code

Explanation

245 0F5 A module LOAD failed.

246 0F6 The IBM timing macro (STIMERM) failed.

247 0F7 The PowerExchange Agent encountered a command with the incorrect number of operands.

248 0F8 Another component requested a function that is not available.

249 0F9 The PowerExchange Agent could not add data to a buffer or file, because the buffer or file was full.

250 0FA Another component sent a request to the PowerExchange Agent to find something, but the PowerExchange Agent could not find it.

251 0FB The PowerExchange Agent found a duplicate request or duplicate record.

252 0FC One module passed an incorrect operand to another module.

253 0FD An invalid function was requested or the function request had an incorrect number of errors.

254 0FE An unexpected error occurred.

255 0FF An abnormal termination (abend) occurred.

Reason Codes 00000601 to 00004499 - CommandPowerExchange issues reason codes from encoded commands that pass between program modules. Some of these reason codes are displayed in the messages that you see when an error occurs.

The following table describes these reason codes:

Reason Code Explanation

00000601 An unknown error occurred.

00000602 There is no schema registration.

00000603 There is no relational schema registration.

00000604 There is no object or schema that matches the specified EDMNAME.

00000605 The object or schema is not active for the time requested.

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

00000703 No logged‑on reader control block found for Terminate Process.

PowerExchange Reason Codes 267

Page 268: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00000704 Terminate Process request failed.

00000805 Client Control Block not found (client not already or no longer signed on to Logger).

00000813 Invalid XCF message (unrecognized encoded command).

00001506 Data Is No Longer Available (no RBA range can be found).

00001507 data is not present in inventory (requested timestamp does not yet exist).

00001508 Data Not Accessed Due To Error (for example, attempt to attach subtask failed).

0000150A Log reader disconnected from Logger before initialization was completed.

00001510 Tran Id Logger Name Not This Logger.

00001511 No logged‑on reader control block found for Request Data Transfer.

00001514 Stop location is before start location.

00001515 No such start location found.

00001601 No logged‑on reader control block found for Stop Data Transfer.

00001701 Registration request failed for unknown reason.

00001702 There are no database, data set, or subsystem registrations.

00001703 There are no registrations of the specified type.

00001704 There is no object or schema that matches the specified EDMNAME.

00001705 The object or schema is not active for the time requested.

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

00001708 Registration request for invalid object type.

00001901 The PowerExchange Logger is shutting down.

00001902 The PowerExchange Logger requires additional system resources.

00001903 The queue could not be opened.

00001904 Invalid signon request (requesting neither read mode nor write mode).

00001905 Already signed on (duplicate jobname).

00001906 An XCF connection failed.

00001907 The PowerExchange Logger is not ready.

268 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 269: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00001908 Logger on different CPU (Log Reader attempted to connect to Logger that was running on a different operating system instance).

00001909 Failed to add log reader control block (OUQQ).

0000190A Unable to start log reader subtask.

0000190B Could not log ECCR signon record.

0000190C Failed to add ECCR control block (INQQ).

0000190D Resume operation failed.

00002104 Invalid Resource Interest List command

00002105 Chain error processing IntLst command

00002111 No matching signed on reader

00002501 An unknown error occurred.

00002502 An unsupported data type was found.

00002503 A module found unsupported data definition language (DDL) code.

00002504 An object registration was not found.

00002505 A schema registration was not found.

00002506 There is no schema for the specified time.

00002507 A change request failed.

00002601 Could not log user data record

00002806 Column name with excessive length encountered.

00004701 Member Logger was already in quiesced status.

00004702 Member Logger was already in stopped status.

00004801 Member Logger was not in quiesced status.

00004802 Member Logger was already in stopped status.

PowerExchange Reason Codes 269

Page 270: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Codes 00000813 to 00001515 - Encoded CommandsThe Encoded Commands issue reason codes from 0000813 through 00001515.

The following table lists the Encoded Commands reason codes:

Reason Code Explanation

00000813 Invalid XCF message (unrecognized encoded command).

00000805 Client Control Block not found (client not already or no longer signed on to Logger).

00001506 DATA IS NO LONGER AVAILABLE (no RBA range can be found).

00001507 DATA IS NOT PRESENT IN INVENTORY (requested RBA does not yet exist).

00001508 DATA NOT ACCESSED DUE TO ERROR (for example, required dataset cannot be allocated).

00001510 TRAN ID LOGGER NAME NOT THIS LOGGER.

00001514 Stop location is before start location.

00001515 No such start location found.

Reason Codes 00000C00 to 00000C0E - Common ServicesPowerExchange common services provide functions to many of the PowerExchange components.

The following table describes the reason codes for errors that are encountered during common services processing:

Reason Code Explanation

00000C00 The module could not obtain storage.

00000C01 The lock manager could not create an anchor.

00000C02 There are no available lock manager entries.

00000C03 The lock manager received an invalid entry.

00000C0A The module received an invalid trace ID.

00000C0B An MVS ATTACH function failed.

00000C0C The MVS service parameter list number was invalid.

00000C0D The MVS STIMERM SET function failed.

00000C0E The MVS STIMERM CANCEL function failed.

270 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 271: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Codes 0033FF01 to 00FFFFFF - PowerExchange LoggerThe PowerExchange Logger issues reason codes from 0033FF01 through 00FFFFFF.

The following table lists the reason codes for the PowerExchange Logger:

Reason Code Explanation

0033FF01 The chainer module could not obtain a work area.

0033FF02 An initialization error occurred. There was an invalid function code.

0033FF03 An unknown return code was found during an attempt to move a record.

0033FF04 The reader processor (EDMLLRD0) was unable to get a buffer.

0033FF05 The reader processor (EDMLLRD0) detected an invalid record prefix.

0033FF06 A refreshed buffer was not available for the reader processor (EDMLLRD0).

0033FF07 The reader processor (EDMLLRD0) failed to get a refreshed buffer.

0033FF08 The reader processor (EDMLLRD0) detected an invalid record prefix.

0033FF09 There were entries in the read queue when the reader processor (EDMLLRD0) was expecting an empty queue.

0033FF0A There were no entries found in the available queue.

0033FF0B The reader processor (EDMLLRD0) failed to disconnect from PowerExchange common services.

0033FF0C The reader processor (EDMLLRD0) failed to connect to PowerExchange common services.

0033FF0D Available Queue empty when available buffer needed.

0033FF20 Physical reader initialization failed.

0033FF21 Error in GETBUFF.

0033FF22 I/O error in physical read.

0033FF23 I/O error in physical reread.

0033FF24 Physical reader termination failed.

0033FF25 During an unallocate call, physical reader termination failed.

00D5FF01 Logger invoked in non‑APF authorized state.

00D5FF02 Invalid function code supplied to EDMLPRD0.

00D5FF03 Dynamic allocation error for archive log dataset in EDMLPRD0.

00D5FF04 Open failed for archive log dataset in EDMLPRD0.

00D5FF05 RBA value has reached maximum permitted value (X'FFFFFFFFFFFF') in EDMLPRD0.

PowerExchange Reason Codes 271

Page 272: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00D5FF06 Unexpected RBA encountered in archive log in EDMLPRD0 (missing or duplicated block(s)).

00D5FF07 Close failed for archive log dataset in EDMLPRD0.

00D5FF08 Invalid LOGQ parameter supplied to EDMLPRD0 at initialization.

00D5FF09 EDMLPRD0 could not locate secondary archive log dataset.

00D5FF0A No buffers available at initialization in EDMLPRD0.

00D5FF0B No buffers available at start of read in EDMLPRD0.

00D5FF0C Dynamic un‑allocation error for archive log dataset in EDMLPRD0.

00D5FF0D Invalid LOGQ parameter supplied to EDMLPRD0 at start of read.

00D5FF0E Unexpected RBA encountered in archive log dataset at EOF in EDMLPRD0 (missing block(s)).

00D6FF01 The chainer module could not obtain a work area.

00D6FF02 Invalid function code supplied to EDMLPRD1.

00D6FF03 Dynamic allocation error for active log dataset in EDMLPRD1.

00D6FF04 Open failed for active log dataset in EDMLPRD1.

00D6FF07 Close failed for active log dataset in EDMLPRD1.

00D6FF08 Invalid LOGQ parameter supplied to EDMLPRD0 at initialization.

00D6FF09 EDMLPRD1 could not locate secondary active log dataset.

00D6FF0A No buffers available at initialization in EDMLPRD0.

00D6FF0B No buffers available at start of read in EDMLPRD0.

00D6FF0C The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00D6FF0D The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00D6FF0E The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00D6FF0F The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00D6FF10 Invalid LOGQ parameter supplied to EDMLPRD1 at start of read.

00D6FF11 Invalid LOGQ parameter supplied to EDMLPRD1 at start of reread.

00D6FF12 Error adding entry to GBLPH1QCB queue in EDMLPRD1.

00D6FF13 Primary active log stopped and dual active logs not available.

00D6FF14 Maximum retries (100) exceeded to successfully reread block from active log dataset in EDMLPRD1.

272 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 273: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00D7FF01 The chainer module could not obtain a work area.

00D7FF02 The chainer module could not release a work area.

00D7FF03 The MODCB macro failed to modify the RPL control block.

00D7FF04 The print ERDS command processor (EDMLPR50) failed to GET the master log control record.

00D7FF05 The print ERDS command processor (EDMLPR50) failed to GET the primary active log control record.

00D7FF06 The print ERDS command processor (EDMLPR50) failed to GET the secondary active log control record.

00D7FF07 The print ERDS command processor (EDMLPR50) failed to GET the primary archive log control record.

00D7FF08 The print ERDS command processor (EDMLPR50) failed to GET the secondary archive log control record.

00D7FF09 The print ERDS command processor (EDMLPR50) failed to GET the checkpoint control record.

00D7FF0A The print ERDS command processor (EDMLPR50) entered an ESTAE routine.

00D8FF01 The chainer module could not obtain a work area.

00D8FF02 The chainer module could not release a work area.

00D9FF01 The chainer module could not obtain a work area.

00D9FF02 The chainer module could not release a work area.

00DAFF01 The chainer module could not obtain a work area.

00DAFF02 The chainer module could not release a work area.

00DAFF04 SYNAD entered a spooled sysout file in EDMLPR20.

00DBFF01 The chainer module could not obtain a work area.

00DBFF02 The chainer module could not release a work area.

00DBFF03 Error connecting to Common Services.

00DCFF01 The chainer module could not obtain a work area.

00DCFF02 The chainer module could not release a work area.

00DDFF01 The chainer module could not obtain a work area.

00DDFF02 The chainer module could not release a work area.

00DDFF03 Cannot determine which ECB posted.

PowerExchange Reason Codes 273

Page 274: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00DDFF04 The chainer module could not LOCK the queue control block (QCB).

00DDFF05 The chainer module could not UNLOCK the queue control block (QCB).

00DDFF06 Log reader disconnected from Logger before initialization was completed.

00DDFF07 The PowerExchange Logger found an invalid log RBA.

00DDFF08 An attempt to initialize a log reader failed.

00DDFF09 An attempt to open a circular queue failed.

00DDFF0A A log reader READ command failed.

00DDFF0B An attempt to PUT to a circular queue failed.

00DDFF0C A circular queue end‑of‑file error occurred.

00DDFF0D An attempt to close a circular queue failed.

00DDFF0E An attempt to terminate a log reader failed.

00DDFF0F An attempt by the logger to connect to the common services failed.

00DDFF10 An attempt to send a SENDPIPE command to the log read processor (LRP) failed.

00DDFF11 Circular queue PUT error for Request Data Transfer reply.

00DDFF12 No token found for XCF circular queue.

00DDFF13 Attempt to open XCF circular queue failed.

00DEFF01 The chainer module could not obtain a work area.

00DEFF02 The chainer module could not release a work area.

00DEFF03 An attempt to initialize a logical log reader failed.

00DEFF04 An attempt by the logical log reader to perform a READ failed.

00DEFF05 The PowerExchange Logger was unable to add a unit‑of‑work (UOW) entry to an internal UOW queue.

00DEFF06 An attempt to terminate the logical log reader failed.

00DEFF07 The PowerExchange Logger was unable to find a logrba in the selected logs.

00DEFF08 The PowerExchange Logger could not find a UOW for begin_PHASE1.

00DEFF09 The PowerExchange Logger could not find a UOW for begin_PHASE2.

00DEFF0A The PowerExchange Logger could not find a UOW for end_PHASE1.

00DEFF0B The PowerExchange Logger could not find a UOW for end_PHASE2.

274 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 275: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00DEFF13 Cannot locate record prefix while repositioning in log on restart (EDMLPLG1).

00DFFF01 The chainer module could not obtain a work area for the write to operator with reply (WTOR) parameter list.

00DFFF02 The chainer module could not release a work area for the write to operator with reply (WTOR) parameter list.

00DFFF03 The chainer module could not release a work area for the write to operator with reply (WTOR) message text.

00DFFF04 The chainer module could not release a work area for the write to operator with reply (WTOR) output data area.

00DFFF05 The chainer module could not release the OPQ control block.

00E0FF01 The chainer module could not obtain a work area.

00E0FF02 The chainer module could not release a work area.

00E1FF01 The chainer module could not release a work area.

00E2FF01 An incorrect post code was detected by the receiving module.

00E2FF02 An attempt to find an element address failed.

00E2FF03 The PowerExchange Logger cannot free a latch that is not held.

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

00E2FF05 The PowerExchange Logger latching processor could not find any latch queue control block (QCB) entries.

00E3FF01 A normal dump has been requested.

00E4FF01 The chainer module could not obtain a work area.

00E4FF02 The chainer module could not release a work area.

00E5FF01 The chainer module could not obtain a work area.

00E5FF02 Error performing buffer Force_write operation.

00E5FF03 Error performing Trunc_Log operation.

00E5FF04 The chainer module could not release a work area.

00E5FF05 Archive Log operation already in progress.

00E5FF06 Error performing Trunc_Buff operation.

00E5FF07 Error connecting to Common Services.

PowerExchange Reason Codes 275

Page 276: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00E6FF01 An attempt by the chainer module to add a record to a queue failed.

00E6FF02 The chainer module is unable to obtain an area for a DATA COPY.

00E7FF01 The chainer module could not obtain a work area.

00E7FF02 The chainer module could not release a work area.

00E7FF03 An attempt to delete an old logger EDMUPARM module failed.

00E7FF04 An attempt to open the EDMPARMS data set failed.

00E8FF03 The pattern match processor found arguments with a length less than zero (0).

00E8FF04 The pattern match processor found a pattern larger than 256 bytes.

00E9FF01 Latch obtain error in EDMLOF20.

00E9FF02 The active log archive processor could not find an active log present in the LOGQ log queue.

00E9FF03 Dynamic allocation for the archive COPY1 data set failed.

00E9FF04 An attempt to perform an OPEN on the archive COPY1 data set failed.

00E9FF05 Dynamic allocation for the archive COPY2 data set failed.

00E9FF06 An attempt to perform an OPEN on the archive COPY2 data set failed.

00E9FF07 The PowerExchange Logger latching processor could not obtain the LOGQ COPY1 log queue.

00E9FF08 The PowerExchange Logger latching processor could not obtain the LOGQ COPY2 log queue.

00E9FF09 EDMLOF20 could not find COMMSRV connect token.

00E9FF0A The DIV ACCESS macro was unable to access the active logs.

00E9FF0B Primary (and secondary if applicable) active log dataset(s) stopped

00E9FF0C The DIV UNIDENTIFY macro was unable to unidentify the active log.

00E9FF0D A CLOSE command failed on an archive COPY1 data set.

00E9FF0E The RDJFCB macro failed on an archive COPY1 data set.

00E9FF0F A CLOSE command failed on an archive COPY2 data set.

00E9FF10 EDMLOF20 could not find secondary active log in LOGQ.

00E9FF11 An UNALLOCATE command failed on an archive COPY1 data set.

00E9FF12 An UNALLOCATE command failed on an archive COPY2 data set.

00E9FF13 An UNALLOCATE command failed on active log.

276 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 277: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00E9FF14 An internal DEFINE_LOG COPY1 command failed.

00E9FF15 An internal DEFINE_LOG COPY2 command failed.

00E9FF16 The chainer module could not release a work area.

00E9FF17 The chainer module could not add a local area.

00E9FF18 The chainer module could not initialize the OPQ control block.

00E9FF19 The chainer module could not find an entry in the GBLBLKQ11 queue.

00E9FF20 The chainer module could not find an entry in the GBLBLKQ12 queue.

00E9FF21 The chainer module could not find an entry in the GBLBLKQ21 queue.

00E9FF22 The chainer module could not find an entry in the GBLBLKQ22 queue.

00E9FF23 The chainer module was unable to find an entry for LOG2 in the LOGQ queue.

00E9FF24 The active log archive processor is using the last active log.

00E9FF25 The log archive processor was unable to find a LOG2 data set name.

00E9FF26 SYNAD entered for archive log 1.

00E9FF27 SYNAD entered for archive log 2.

00E9FF30 Latch release error in EDMLOF20.

00E9FF34 Update ERDS process failed.

00EAFF01 The chainer module could not obtain a work area.

00EAFF02 The chainer module could not release a work area.

00EBFF01 The chainer module could not obtain a work area.

00EBFF02 The chainer module could not release a work area.

00EC0040 The module receives an unexpected return code from the DBCTL subsystem interface. Contact your Informatica technical support analyst for assistance.

00ECFF01 The chainer module could not obtain a work area.

00ECFF02 The GETMAIN macro failed.

00ECFF03 The FREEMAIN macro failed.

00EDFF01 The chainer module could not obtain a work area.

00EDFF02 The chainer module could not release a work area.

00EEFF01 The chainer module could not obtain a work area.

PowerExchange Reason Codes 277

Page 278: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00EEFF02 The chainer module could not release a work area.

00EFFF01 The chainer module could not obtain a work area.

00EFFF02 The chainer module could not release a work area.

00F0FF01 The chainer module could not obtain a work area.

00F0FF02 The chainer module could not release a work area.

00F1FF01 The chainer module could not obtain a work area.

00F1FF02 The chainer module could not release a work area.

00F1FF03 The chainer module could not initialize the GCO queue.

00F1FF04 The chainer module could not add an entry to the GCO queue.

00F1FF05 The chainer module could not add or replace an entry on the GCO queue.

00F1FF06 The chainer module could not initialize the IMO queue.

00F1FF07 The chainer module could not add an entry to the IMO queue.

00F1FF08 The chainer module could not add or replace an entry on the IMO queue.

00F1FF09 The chainer module could not delete the GCO queue.

00F1FF0A The chainer module could not delete the IMO queue.

00F1FF0B The chainer module could not find the GCO queue.

00F1FF0C The EDMUPARM processor (EDMLDF20) could not load the modified options data set.

00F1FF0D The chainer module could not terminate the ICO queue.

00F1FF0E The chainer module could not terminate the GCO queue.

00F1FF0F The EDMUPARM processor (EDMLDF20) encountered an error when it attempted to delete one or more options.

00F1FF10 The EDMUPARM processor (EDMLDF20) was unable to find the DEFAULT SERVER OPTIONS module.

00F1FF11 The EDMUPARM processor (EDMLDF20) could not open the options data set.

00F2FF01 The chainer module could not obtain a work area.

00F2FF04 The chainer module could not return a work area.

00F2FF05 The define‑logger processor (EDMLDF10) could not find the options data set.

00F3FF01 The PowerExchange Logger found an incorrect version of the EDMLC020 control module.

278 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 279: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F3FF02 The PowerExchange Logger found an incorrect version of the EDMLC030 control module.

00F3FF03 The chainer module could not initialize the CSA tracking queue.

00F3FF04 The chainer module was unable to initialize an area for the GLOBAL control block.

00F3FF05 The chainer module was unable to create an area for the GLOBAL control block.

00F3FF06 The chainer module was unable to initialize a task control, TC, queue.

00F3FF07 The chainer module was unable to initialize a LOC=31 storage unit.

00F3FF08 The chainer module was unable to initialize a LOC=24 storage unit.

00F3FF09 The chainer module was unable to initialize the INPUT queue.

00F3FF0A The initialization processor could not find the address of the chainer module while building a write to operator with reply (WTOR) command.

00F3FF0B The chainer module could not add a local control block for a write to operator with reply (WTOR) command.

00F3FF0C The initialization processor could not find the address of the chainer module while building the PowerExchange physical logger.

00F3FF0D The chainer module could not add a local control block for the PowerExchange physical logger.

00F3FF0E The BLDL FIND macro was unable to locate the EDMLC030 module.

00F3FF0F An OPEN command failed for STEPLIB.

00F3FF10 Subsystem initialization failed.

00F3FF11 An attempt to LOAD the options module EDMUPARM failed.

00F3FF12 The message display routine FREEMAIN command failed.

00F3FF13 An EDMPARMS DD statement is missing.

00F3FF14 An EDMZPARM module was not found.

00F3FF15 The options module DD concatenation has an error.

00F3FF16 An attempt to LOAD the options module EDMUPARM failed.

00F3FF17 An error occurred while initializing the queue for 241 XCA GETMAINS.

00F3FF18 Too many EDMLC030 modules exist in extended CSA (ECSA).

00F3FF19 An attempt by the chainer module to create a latch queue control block (QCB) failed.

00F3FF1A The chainer was unable to create a latch area.

00F3FF1B The chainer module had an error while creating LOGQ COPY1 block queue.

PowerExchange Reason Codes 279

Page 280: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F3FF1C The chainer module had an error while creating BLKQ COPY1 block queue.

00F3FF1D The chainer module had an error while creating LOGQ COPY2 block queue.

00F3FF1E The chainer module had an error while creating the BLKQ COPY2 block queue.

00F3FF1F The chainer module had an error while creating LOGQ COPY1 block queue.

00F3FF20 The chainer module had an error while creating BLKQ COPY1 block queue.

00F3FF21 The chainer module had an error while creating LOGQ COPY2.

00F3FF22 The chainer module had an error while creating BLKQ COPY2.

00F3FF23 The chainer module had an error while adding a LOGF entry to the LATCH queue.

00F3FF24 The chainer module had an error while adding a CHKP entry to the LATCH queue.

00F3FF25 The chainer module had an error while initializing the unit‑of‑work (UOW) QCB queue control block.

00F3FF26 The chainer module was unable to initialize the CHK checkpoint queue control block (QCB).

00F3FF27 The chainer module was unable to initialize the ECCR INQ input queue control block (QCB).

00F3FF28 The chainer module was unable to initialize the LRP OUQ output queue control block (QCB).

00F3FF29 The PowerExchange Logger initialization processor (EDMLC015) was unable to create a latch circular queue.

00F3FF2A The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a phase 1 queue control block (QCB).

00F3FF2B The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a phase 2 queue control block (QCB).

00F3FF2C The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a termination queue control block (QCB).

00F3FF2D The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a packet queue control block (QCB).

00F3FF2E The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a global queue control block (QCB).

00F3FF2F The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a command queue control block (QCB).

00F3FF30 The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize an XCF queue control block (QCB).

00F3FF31 The PowerExchange Logger initialization processor (EDMLC015) was unable to initialize a trace queue control block (QCB).

280 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 281: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F3FF32 The PowerExchange Logger initialization processor (EDMLC015) encountered an incompatible EDMUPARM level.

00F4FF01 An attempt to load the initialization processor failed.

00F4FF02 The chainer module was unable to create the TC task control module.

00F4FF03 The ATTACH command passed a nonzero return code.

00F4FF04 The chainer module could not delete the LOC=31 storage unit.

00F4FF05 The chainer module was unable to obtain a work area for the ECB list.

00F4FF06 The chainer module could not delete the task control.

00F4FF07 The PowerExchange Logger initial checkpoint failed.

00F4FF08 The PowerExchange Logger final checkpoint failed.

00F4FF09 An attempt to initialize the common services environment failed.

00F4FF0A An attempt to connect to common services failed.

00F4FF0B The main subtask processor (EDMLC010) could not create the circular queue. A POST error occurred.

00F4FF0C The main subtask processor (EDMLC010) could not connect to the PowerExchange subsystem.

00F4FF0C The main subtask processor (EDMLC010) could not post a write packet trailer.

00F5FF01 The chainer module could not obtain a work area.

00F5FF02 The EDMLPAR0 reason code is too large.

00F5FF03 A previous chainer error occurred. A required work area does not exist.

00F5FF05 The chainer module could not terminate the command queue.

00F5FF06 The PARSER Error processor received an invalid return code from the PARSER analyzer.

00F6FF01 The chainer module could not obtain a work area.

00F6FF02 The chainer module could not release a work area.

00F6FF03 The chainer module could not obtain an area for a VSAM DELETE statement.

00F6FF04 The chainer module could not obtain an area for a VSAM DEFINE statement.

00F6FF05 The chainer module could not obtain an area for a VSAM JOURNAL HEADER statement.

00F6FF08 An attempt to delete a statement area failed.

00F6FF09 The data set name is missing from an input parameter.

PowerExchange Reason Codes 281

Page 282: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F6FF0D R0 contains an invalid entry code. It contains an entry other than DELETE, DEFINE, or JOURNAL HEADER.

00F6FF0E Either the ALCACB. or ALCRPL. area is corrupt.

00F6FF0F The ALCALCAD area is corrupt.

00F7FF01 The chainer module could not obtain a work area.

00F7FF02 An attempt to initialize the common services environment failed.

00F7FF03 An attempt to connect to common services failed.

00F7FF04 An attempt to initialize the XCF interface failed.

00F7FF05 An attempt to open the XCF interface failed.

00F7FF06 An attempt to create the XCF interface failed.

00F7FF07 $XCF GET failed for message.

00F7FF08 $XCF GET failed for group event (Logger group).

00F7FF09 $XCF GET failed for group event (Post‑Log Merge group).

00F7FF17 Failed adding log reader control block (OUQQ).

00F7FF18 Unable to start log reader subtask.

00F7FF19 ECCR is already connected to Logger.

00F7FF1A Unable to add PKT queue entry.

00F7FF1B Failed to add ECCR control block (INQQ).

00F7FF1C Invalid signon type (neither read nor write).

00F7FF1D Attempt to perform resume operation failed.

00F7FF1E Unable to locate log reader (OUQQ) control block.

00F7FF1F Could not write to global circular queue.

00F7FF20 Logger name in restart request does not match logger ID.

00F7FF21 End location in transfer request before start location.

00F7FF22 Terminate request did not complete successfully.

00F7FF23 Delete of log reader (OUQQ) control block fail.

00F8FF01 The chainer module could not obtain a work area.

00F8FF02 The chainer module is unable to delete the old ECB list.

282 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 283: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F8FF03 The chainer module is unable to obtain a new ECB list.

00F8FF04 The checkpoint processor received an unexpected termination of the QSAM I/O subtask.

00F8FF05 The checkpoint processor received an unexpected termination of the TIMER subtask.

00F8FF06 The checkpoint processor received an unexpected termination of the JOURNAL subtask.

00F8FF07 The checkpoint processor received an unexpected termination of the PROCESS subtask.

00F8FF08 The checkpoint processor received an unexpected termination of the RESTART subtask.

00F8FF09 The checkpoint processor received an unexpected termination of the LOGICAL subtask.

00F8FF0A The checkpoint processor received an unexpected termination of the PHYSICAL subtask.

00F8FF0B The checkpoint processor received an unexpected termination of the Checkpoint subtask.

00F8FF0C The checkpoint processor received an unexpected termination of the XCF subtask.

00F8FF0D The checkpoint processor received an unexpected termination of the VTAM I/O subtask.

00F8FF0E The checkpoint processor received an unexpected request for a checkpoint.

00F8FF0F The checkpoint processor received an unexpected request for a shutdown.

00F8FF10 The checkpoint processor received an unexpected operator reply.

00F8FF11 The checkpoint processor received an unexpected reload of EDMZPARM.

00F8FF12 The checkpoint processor received an unexpected termination of an MVS command.

00F8FF13 The chainer module was unable to delete a work area.

00F8FF14 The PowerExchange Logger found an invalid code. A WRITE to a restart data set (ERDS) failed.

00F9F701 The routine that determines the number of blocks available in the active LOG2 was unable to obtain a LOGQ latch.

00F9F702 The routine that determines the number of blocks available in active LOG2 was unable to release the LOGQ latch.

00F9F801 The routine that determines the number of blocks available in active LOG2 was unable to obtain the LOGQ latch.

00F9F802 The routine that determines the number of blocks available in active LOG2 was unable to release the LOGQ latch.

00F9F803 The chainer module could not obtain a read buffer.

00F9F804 The chainer module was unable to add an entry to the BLKQ COPY1 queue.

00F9F805 The chainer module was unable to add an entry to the active LOGQ COPY1 queue.

PowerExchange Reason Codes 283

Page 284: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F9F806 The chainer module was unable to add an entry to the archive BLKQ COPY1 queue.

00F9F807 The chainer module was unable to add an entry to the archive LOGQ COPY1 queue.

00F9F808 The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00F9F809 The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00F9F80A The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00F9F80B The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00F9F901 The routine that determines the number of blocks available in active LOG1 was unable to obtain the LOGQ latch.

00F9F902 The routine that determines the number of blocks available in active LOG1 was unable to release the LOGQ latch.

00F9F903 The chainer module could not obtain a read buffer.

00F9F904 The chainer module was unable to add an entry to the BLKQ COPY1 queue.

00F9F905 The chainer module was unable to add an entry to the active LOGQ COPY1 queue.

00F9F906 The chainer module was unable to add an entry to the archive BLKQ COPY1 queue.

00F9F907 The chainer module was unable to add an entry to the archive LOGQ COPY1 queue.

00F9F908 The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00F9F909 The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00F9F90A The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00F9F90B The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00F9FA01 The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00F9FA02 The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00F9FA03 The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00F9FA04 The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00F9FA05 A save error occurred in the physical logger processor (EDMLPLG0). The other log was already stopped.

00F9FA06 A save error occurred in the physical logger processor (EDMLPLG0). There is no secondary log.

00F9FA07 The secondary active log subtask (EDMLPLG2) has abended.

00F9FB01 The routine to terminate processing of active log could not obtain the LOGQ latch.

00F9FB02 The routine to terminate processing of active log could not release the LOGQ latch.

284 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 285: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F9FB03 The DIV UNACCESS macro could not stop accessing the LOG1 data set.

00F9FB04 The DIV UNIDENTIFY macro could not unidentify the LOG1 data set.

00F9FB05 The ALESERV DELETE macro could not delete the LOG1 data set.

00F9FB06 The DSPSERV DELETE macro could not delete the LOG1 data set.

00F9FB07 The DIV SAVE macro could not save the LOG2 data set.

00F9FB08 The DIV UNMAP macro could not unmap the LOG2 data set.

00F9FB09 The DIV UNACCESS macro could not stop accessing the LOG2 data set.

00F9FB0A The DIV UNIDENTIFY macro could not unidentify the LOG2 data set.

00F9FB0B The ALESERV DELETE macro could not delete the LOG2 data set.

00F9FB0C The DSPSERV DELETE macro could not delete the LOG2 data set.

00F9FB0D The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00F9FB0E The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00F9FB0F The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00F9FB10 The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00F9FC01 The routine to initialize processing of active log could not obtain the LOGQ latch.

00F9FC02 The routine to initialize processing of the active log could not release the LOGQ latch.

00F9FC03 Dynamic allocation for the active LOG1 data set failed.

00F9FC04 The routine to initialize processing of the active log could not release the LOGQ latch.

00F9FC05 Dynamic allocation for the active LOG2 data set failed.

00F9FC06 The routine to initialize processing of the active log could not release the LOGQ latch.

00F9FC07 The DSPSERV CREATE macro could not create a hyperspace for HSP LOG1 data set.

00F9FC08 The ALESERV OBTAIN macro could not obtain the access-list entry token (ALET) LOG1 data set.

00F9FC09 The DSPSERV CREATE macro could not create a hyperspace for HSP LOG2 data set.

00F9FC0A The ALESERV OBTAIN macro could not obtain the access-list entry token (ALET) LOG2 data set.

00F9FC0B The DIV IDENTIFY macro could not identify the LOG1 data set.

00F9FC0C The DIV ACCESS macro could not access the LOG1 data set.

00F9FC0D The DIV MAP macro could not map the LOG1 data set.

PowerExchange Reason Codes 285

Page 286: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F9FC0E The DIV IDENTIFY macro could not identify the LOG2 data set.

00F9FC0F The DIV ACCESS macro could not access the LOG2 data set.

00F9FC10 The DIV MAP macro could not map the LOG1 data set.

00F9FC11 The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00F9FC12 The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00F9FC13 The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00F9FC14 The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00F9FC15 The physical logger found that both the primary and secondary active logs are in a stopped state.

00F9FD01 The routine to obtain new active log could not obtain the LOGQ latch.

00F9FD02 The routine to obtain new active log could not release the LOGQ latch.

00F9FE01 The chainer module could not obtain a command buffer.

00F9FF01 The chainer module could not obtain a work area.

00F9FF02 The GETSTOC routine was unable to determine the number of available blocks for logging to the LOG1 data set.

00F9FF03 The GETSTOC routine was unable to determine the number of available blocks for logging to the LOG2 data set.

00F9FF04 A GETNEWL error occurred while attempting to get a new log during initialization.

00F9FF05 The PowerExchange physical logger was unable to determine if a new active LOG2 exists.

00F9FF06 The PowerExchange physical logger was unable to determine if a new active LOG1 exists.

00F9FF07 The INIACTL routine could not initialize a new log.

00F9FF08 The chainer module was unable to find an entry in the GBLBLKQ11 queue.

00F9FF09 The chainer module was unable to find an entry in the GBLBLKQ12 queue.

00F9FF0A The chainer module was unable to find an entry in the GBLBLKQ21 queue.

00F9FF0B The chainer module was unable to find an entry in the GBLBLKQ22 queue.

00F9FF0C The chainer module was unable to add a LOCAL control block.

00F9FF0D The chainer module could not initialize the OPQ queue.

00F9FF0E An attempt to obtain a LOGQ latch failed.

00F9FF0F An attempt to release the LOGQ latch failed.

286 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 287: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00F9FF10 No space is available in the active log.

00F9FF11 The physical logger processor (EDMLPLG0) was unable to build a UOW queue.

00F9FF12 The physical logger processor (EDMLPLG0) could not obtain the LOGS log queue.

00F9FF13 The physical logger processor (EDMLPLG0) entered an ESTAE routine.

00F9FF14 The physical logger processor (EDMLPLG0) encountered an invalid log RBA.

00F9FF15 The physical logger processor (EDMLPLG0) could not obtain a log queue latch.

00F9FF16 The physical logger processor (EDMLPLG0) could not release a log queue latch.

00F9FF17 The physical logger processor (EDMLPLG0) was unable to connect to PowerExchange common services.

00F9FF18 A write error occurred. There is no secondary log.

00F9FF19 A write error occurred. The other log was already stopped.

00F9FF1A Failure in attaching active log 2 subtask (EDMLPLG2).

00F9FF1B No available active log dataset.

00F9FF1C Number of secondary active log datasets does not match number of primary active log datasets.

00F9FF1D Archive log operation failed at initialization.

00F9FF1E Attempt to log data while logger is quiesced

00FAFF01 The chainer module could not obtain a work area.

00FAFF02 The chainer module was unable to obtain a buffer prefix.

00FAFF03 The chainer module was unable to obtain a buffer.

00FAFF04 A GETBUFF macro error occurred. It was unable to get a buffer.

00FAFF05 A MOVEREC macro error occurred, and it returned an unknown return code.

00FAFF06 The chainer module is unable to add a unit of work (UOW).

00FAFF07 The chainer module is unable to delete a unit of work (UOW).

00FAFF08 A WRITE to a restart data set (ERDS) failed.

00FAFF09 The MOVEREC macro could not write to a log begin_checkpoint record.

00FAFF0A The MOVEREC macro could not write to a log UOW_summary record.

00FAFF0B The MOVEREC macro could not write to a log end_checkpoint record.

00FAFF0C The chainer module was unable to add an entry to the CHK queue.

PowerExchange Reason Codes 287

Page 288: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FAFF0D The logical logger processor was unable to obtain a LOGQ latch.

00FAFF0E An attempt to connect to common services failed.

00FAFF0F The chainer module was unable to delete an entry from the CHK queue.

00FAFF10 The $DLICQPL macro could not open a circular queue.

00FAFF11 The PowerExchange logical logger processor (EDMLLLG0) was unable to obtain a LOGS latch.

00FAFF12 The PowerExchange logical logger processor (EDMLLLG0) was unable to read the global queue.

00FAFF13 The PowerExchange logical logger processor (EDMLLLG0) received a STIMERM SET error.

00FAFF14 The MOVEREC macro received a packet trailer error in the PowerExchange logical logger processor (EDMLLLG0) module.

00FAFF15 The PowerExchange logical logger processor (EDMLLLG0) module entered an ESTAE routine.

00FAFF16 The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a checkpoint (CHKPT).

00FAFF17 The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a checkpoint (CHKPT).

00FAFF18 The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a HARDN command.

00FAFF19 The PowerExchange logical logger processor (EDMLLLG0) received a physical logger error while attempting a HARDN command.

00FAFF1A The PowerExchange logical logger processor (EDMLLLG0) exceeded the maximum LOGRBA.

00FAFF1B The PowerExchange logical logger processor (EDMLLLG0) was unable to obtain a LOGQ latch.

00FAFF1C The PowerExchange logical logger processor (EDMLLLG0) received a STIMERM CANCEL error.

00FAFF1D The PowerExchange logical logger processor (EDMLLLG0) could not open the XCF message queue.

00FAFF1E The PowerExchange logical logger processor (EDMLLLG0) encountered an error in COMMUOW and could not complete a PUT command on the XCF message queue.

00FBFF01 The chainer module could not obtain a work area.

00FBFF02 The chainer module could not initialize the TC task control queue.

00FBFF03 The chainer module could not add an entry to the TCQ queue.

00FBFF04 The chainer module could not terminate the CMD queue.

00FBFF05 An error occurred while loading the dictionary.

00FBFF06 The chainer module could not delete the ECBLIST area.

288 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 289: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FBFF07 The chainer module could not obtain the ECBLIST area.

00FBFF08 The chainer module could not terminate the TCQ queue.

00FBFF0A The chainer module could not terminated the STR queue.

00FBFF0B The chainer module could not delete a work area.

00FBFF0C The chainer module could not terminate the GBLLIFPQ queue.

00FBFF0D The chainer module was unable to free an externalized CMD (EDMD) area.

00FBFF0E The chainer module could not delete the IPQ queue.

00FBFF0F The chainer module was unable to delete an entry from the LIFCMSQ queue.

00FBFF10 The chainer module could not add an entry to the TCQ queue.

00FBFF11 An ATTACH command returned a nonzero return code.

00FBFF13 The chainer module was unable to flush entries from the input CMD queue.

00FBFF14 The chainer module could not delete an entry from the TCQ queue.

00FCFF01 The chainer module could not obtain a work area.

00FCFF02 The chainer module could not delete a work area.

00FCFF03 The chainer module could not delete the JNL queue.

00FCFF04 The chainer module could not delete data.

00FCFF05 The chainer module could not obtain a JNL record area.

00FCFF06 The chainer module could not release a JNL record area.

00FCFF07 An attempt to CLOSE or UNALLOCATE a JOURNAL data set failed.

00FCFF09 The journal processor (EDMLJNL0) encountered a SHOWCB error after a PUT function.

00FCFF0A The journal processor (EDMLJNL0) encountered a SHOWCB error after a PUT function.

00FCFF0B The journal processor (EDMLJNL0) encountered a SHOWCB error after a PUT function.

00FCFF0C An attempt to obtain an area to build a JOURNAL HEADER statement failed.

00FDFF01 An attempt to flush inactive LOCAL control blocks failed.

00FDFF02 An attempt by the chainer module to delete a local area failed.

00FDFF03 An attempt by the chainer module to obtain a work area failed.

00FDFF04 An attempt by the chainer module to release a work area failed.

PowerExchange Reason Codes 289

Page 290: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FDFF05 The chainer module was unable to free unused areas from the GBLP24Q queue.

00FDFF06 The chainer module was unable to free unused areas from the GBLP31Q queue.

00FDFF07 The chainer module was unable to free unused areas from the GBLGBLQ queue.

00FDFF08 Cannot determine which ECB posted.

00FDFF09 Error sending to global circular queue.

00FEFF01 The chainer module could not obtain a work area.

00FEFF02 The PowerExchange Logger was unable to open SYSIN.

00FEFF03 The chainer module was unable to add a local area control block.

00FEFF04 The PowerExchange Logger was unable to open SYSPRINT.

00FEFF05 The chainer module was unable to obtain an area to build an input record.

00FEFF07 The chainer module was unable to delete an output data area.

00FEFF08 The chainer module was unable to delete an I/O queue.

00FEFF09 The chainer module was unable to delete a local area.

00FEFF0A The chainer module was unable to delete a work area.

00FEFF0B The chainer module was unable to initialize an output queue.

00FEFF0C The third parameter, which shows the number of lines on a printed page, is invalid.

00FFCF01 The chainer module could not obtain a work area.

00FFCF02 The chainer module could not obtain a buffer area.

00FFCF03 The MODCB macro failed to modify the RPL control block.

00FFCF04 An attempt by this module to GET the master log control record failed.

00FFCF05 An attempt by the chainer module to FIND the master log control record failed.

00FFCF06 An attempt by this module to GET the primary active log control record failed.

00FFCF07 An attempt by the chainer module to FIND the primary active log control record failed.

00FFCF08 An attempt by this module to GET the secondary active log control record failed.

00FFCF09 An attempt by the chainer module to FIND the primary archive log control record failed.

00FFCF0A An attempt by this module to GET the next archive log failed.

00FFCF0B An attempt by the chainer module to FIND the secondary archive log control record failed.

290 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 291: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FFCF0C The MODCB macro failed to modify the RPL control block.

00FFCF0D An attempt by this module to GET the checkpoint control record failed.

00FFCF0E An attempt by this module to PUT the checkpoint control record failed.

00FFDF01 The chainer module could not obtain a work area.

00FFDF02 The chainer module could not obtain a buffer area.

00FFDF03 The MODCB macro failed to modify the RPL control block.

00FFDF04 An attempt by this module to GET the master log control record failed.

00FFDF05 An attempt by the chainer module to FIND the master log control record failed.

00FFDF06 An attempt by this module to GET the primary active log control record failed.

00FFDF07 An attempt by the chainer module to FIND the primary active log control record failed.

00FFDF08 An attempt by this module to GET the secondary active log control record failed.

00FFDF09 An attempt by the chainer module to FIND the primary archive log control record.

00FFDF0A An attempt by this module to GET the next archive log failed.

00FFDF0B An attempt by the chainer module to FIND the secondary archive log control record failed.

00FFDF0C The MODCB macro failed to modify the RPL control block.

00FFDF0D An attempt by this module to GET the checkpoint control record failed.

00FFDF0E An attempt by this module to PUT the checkpoint control record failed.

00FFEF01 An attempt to obtain a buffer for the master log failed.

00FFEF02 An attempt to perform an OPEN of the ERDS01 restart data set failed.

00FFEF03 An attempt to perform an OPEN of the ERDS02 restart data set failed.

00FFF001 An attempt to obtain a read buffer failed.

00FFF002 An attempt to add a checkpoint to the internal checkpoint queue failed.

00FFF101 The chainer module was unable to initialize the LOGQ COPY1 queue.

00FFF102 The chainer module was unable to initialize the BLKQ COPY1 queue.

00FFF103 The chainer module was unable to obtain a read buffer.

00FFF104 The chainer module was unable to add an entry to the BLKQ COPY2 queue.

00FFF105 The chainer module was unable to add an entry to the active LOGQ COPY2 queue.

PowerExchange Reason Codes 291

Page 292: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FFF106 The chainer module was unable to add an entry to the archive BLKQ COPY2 queue.

00FFF107 The chainer module was unable to add an entry to the archive LOGQ COPY2 queue.

00FFF201 The chainer module was unable to initialize the LOGQ COPY1 queue.

00FFF202 The chainer module was unable to initialize the BLKQ COPY1 queue.

00FFF203 The chainer module was unable to obtain a read buffer.

00FFF204 The chainer module was unable to add an entry to the BLKQ COPY1 queue.

00FFF205 The chainer module was unable to add an entry to the active LOGQ COPY1 queue.

00FFF206 The chainer module was unable to add an entry to the archive BLKQ COPY1queue.

00FFF207 The chainer module was unable to add an entry to the archive LOGQ COPY1 queue.

00FFF301 The chainer module was unable to initialize the LOGQ COPY1 queue.

00FFF302 The chainer module was unable to initialize the BLKQ COPY1 queue.

00FFF303 The chainer module was unable to obtain a read buffer.

00FFF304 The chainer module was unable to add an entry to the BLKQ COPY2 queue.

00FFF305 The chainer module was unable to add an entry to the active LOGQ COPY2 queue.

00FFF306 The chainer module was unable to add an entry to the archive BLKQ COPY2 queue.

00FFF307 The chainer module was unable to add an entry to the archive LOGQ COPY2 queue.

00FFF401 The chainer module was unable to initialize the LOGQ COPY1 queue.

00FFF402 The chainer module was unable to initialize the BLKQ COPY1 queue.

00FFF403 The chainer module was unable to obtain a read buffer.

00FFF404 The chainer module was unable to add an entry to the BLKQ COPY1 queue.

00FFF405 The chainer module was unable to add an entry to the active LOGQ COPY1 queue.

00FFF406 The chainer module was unable to add an entry to the archive BLKQ COPY1 queue.

00FFF407 The chainer module was unable to add an entry to the archive LOGQ COPY1 queue.

00FFF501 When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present.

00FFF502 The chainer was unable to add a log to the internal log queue, LOGQ2.

00FFF601 When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present.

292 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 293: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FFF602 The chainer was unable to add a log to the internal log queue, LOGQ1.

00FFF701 When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present.

00FFF702 The chainer was unable to add a log to the internal log queue, LOGQ2.

00FFF801 When the logger attempted to add an active log to the ERDS01 restart data set, it found an active log already present.

00FFF802 The chainer was unable to add a log to the internal log queue, LOGQ1.

00FFFB01 The chainer module could not find an archive log to delete.

00FFFB02 The chainer module was unable to perform a DELETE on the archive log queue, LOGQ2

00FFFC01 The chainer module could not find an archive log to delete.

00FFFC02 The chainer module was unable to perform a DELETE on the archive log queue LOGQ1.

00FFFD01 The chainer module could not find an active log to delete.

00FFFE01 The chainer module could not find an active log to delete.

00FFFF01 The chainer module could not obtain a work area.

00FFFF02 The chainer module could not obtain an ERDS01 restart data set buffer.

00FFFF03 The chainer module could not obtain a ERDS02 restart data set buffer.

00FFFF04 The PowerExchange Logger is unable to build the LOGQ11 log queue.

00FFFF05 The PowerExchange Logger is unable to build the LOGQ12 log queue.

00FFFF06 The PowerExchange Logger is unable to build the LOGQ21 log queue.

00FFFF07 The PowerExchange Logger is unable to build the LOGQ22 log queue.

00FFFF08 The PowerExchange Logger is unable to determine which log is the current active log.

00FFFF09 The ERDS01 restart data set DD statement is missing.

00FFFF0A The PowerExchange Logger found an invalid restart data set (ERDS).

00FFFF0B An attempt by the GENCB module to obtain the ACB for ERDS01 restart data set failed.

00FFFF0C An attempt to OPEN the ERDS01 restart data set failed.

00FFFF0D An attempt by GENCB to obtain the ACB for ERDS02 restart data set failed.

00FFFF0E An attempt to OPEN the ERDS02 restart data set failed.

00FFFF0F The online and ERDS01 restart data set is empty.

PowerExchange Reason Codes 293

Page 294: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00FFFF10 An attempt by the GENCB macro to generate the RPL control block for the ERDS01 restart data set failed.

00FFFF11 An attempt by the GENCB macro to generate the RPL control block for the ERDS02 restart data set failed.

00FFFF12 An attempt to format the ERDS01 restart data set failed.

00FFFF13 An attempt to format the ERDS02 restart data set failed.

00FFFF14 An attempt to read the ERDS01 restart data set master log record failed.

00FFFF15 An attempt to read the ERDS02 restart data set master log record failed.

00FFFF16 An attempt by the MODCB macro to modify the ERDS01 restart data set RPL control block failed.

00FFFF17 An attempt by the MODCB macro to modify the ERDS02 restart data set RPL control block failed.

00FFFF18 The logger was unable to obtain the LOGQ latch.

00FFFF19 The logger was unable to build the checkpoint queue, CHKPT.

Reason Codes 01440600 to 060906FF - PowerExchange UtilitiesThe PowerExchange utilities issues reason codes from 01440600 through 060906FF.

The following table lists the reason codes issued by the PowerExchange utilities:

Reason Code Explanation

01440600 The DCB failed to open properly.

01440601 The PowerExchange Logger interface utility (EDMXLUTL) could not generate a required DCB.

01440602 The PowerExchange Logger interface utility (EDMXLUTL) could not open a data set.

01440603 The PowerExchange Logger interface utility (EDMXLUTL) could not close a data set.

01440604 The PowerExchange Logger interface utility (EDMXLUTL) could not free a data set.

01440609 A control card error was detected.

01450605 The event command processor was (EDMXLEVT) unable to obtain working storage.

01450606 The event command processor (EDMXLEVT) was unable to load the log utility process module.

01450607 A bad PowerExchange standard record was detected.

01450608 A bad PowerExchange canonical record was detected.

01450618 A PUT function for the output queue failed.

294 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 295: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0145061B The conversion buffer is too small.

01450624 A LOAD function failed for the event command processor (EDMXLEVT).

01450625 The build command service did not return an PowerExchange record.

01450626 The event command processor (EDMXLEVT) could not find any active EDMNAMEs for data capture.

01450627 Excessive number of descriptions (more than 5) to be added to event marker (from EDMXLEVT)

0145062E The event command processor (EDMXLEVT) could not initialize the log utility because a previous failure occurred.

01450651 A RETURN EDMNAME call failed.

01450652 A DB2 request for a list of table names failed.

01460605 The build command utility (EDMXIBCM) was unable to obtain working storage.

01460619 A bad encoded command was passed to the build command utility (EDMXIBCM).

0146061A No conversion buffer was passed to the build command utility (EDMXIBCM).

0146061B The conversion buffer is too small.

0146061C The conversion buffer length is zero.

0146061D The conversion buffer has a bad header record.

0146061E No worklist buffer was passed to the build command utility (EDMXIBCM).

0146061F The worklist buffer is too small.

01460620 The worklist buffer length is zero.

01460621 The worklist buffer has a bad header record.

01460622 A BUILD function failed for a pipe cleaner.

01460623 A BUILD function failed for process termination.

01460625 The build command utility (EDMXIBCM) did not return an PowerExchange record.

01460626 A BUILD function fail for a registration list.

01460627 The data set name is missing for a registration list request.

01460629 The build command utility could not locate a database descriptor.

0146062C A bad return code was received from a registration list request.

0146062D The request type entered is not supported by the command module.

PowerExchange Reason Codes 295

Page 296: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0146062F The requested object category is invalid.

06030646 A TESTCB function failed for the ACB.

Reason Codes 01800101 to 01FFFFFF - Change Interface Component

The Change Interface Component (CIC) issues reason codes from 01800101 through 01FFFFFF.

The following table lists the reason codes the Change Interface Component (CIC) issues:

Reason Code Explanation

01800101 An invalid data type was found during an OPEN call.

01800102 The GET and PUT functions require an open token.

01800103 An invalid IPC header was found.

01800104 A prior error requires CIC to stop. For more information, see the previous error.

01800105 No create token was provided.

01800106 A global queue error occurred.

01800107 The PowerExchange Agent is not active

01800108 The mailman task ended prematurely.

01800109 An error occurred in the mailman.

0180010A The 'mailman ended' flag is on.

0180010C The BUILD CDE function failed.

0180010D The DELETE CDE function failed.

01810101 CIC is being forced to terminate.

01810102 A global queue error occurred.

01810103 An error occurred during resync processing.

01810104 A cross‑memory post failed.

01810105 The PowerExchange Logger quit during the termination process.

01810106 The PowerExchange Logger is inactive, and the global directory (EDMSDIR) requested an abend. This code is returned during initialization in an offline environment.

01810107 The caller requested that CIC post all units of work.

296 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 297: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

01810108 The PowerExchange Logger has ended.

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

0181010A The PowerExchange Logger terminated before the ECCR could connect to the logger.

0181010B An XCF JOIN function failed.

0181010C An XCF LEAVE function failed.

0181010D An XCF PUT function failed.

0181010E An XCF GET function failed.

0181010F An XCF FREE BUFFER failed.

01810110 An error occurred when CIC attempted to open a logger queue.

01810111 The logger terminated during CIC initialization.

01820101 The module was unable to get into a supervisory state.

01820102 A name/token CREATE failed.

01820103 A name/token RETRIEVE failed.

01820104 A name/token DELETE failed.

01820105 The BUILD CDE function failed.

01820106 The DELETE CDE function failed.

01820107 An error occurred when connecting to common services.

01820108 A disconnect error from common services occurred.

01820109 CIC is loading the program to CSA.

0182010A Initialization for the module EDMCICLG failed.

0182010B The PUT function for the module EDMCICLG failed.

0182010C Termination for the module EDMCICLG failed.

0182010D A cross‑memory post failed.

01830101 An error was returned from the mailman.

01830102 A name/token RETRIEVE failed.

01830103 An invalid length was passed.

01830104 The object's profile was not found.

PowerExchange Reason Codes 297

Page 298: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

01830105 The mailman has ended.

01830106 The PowerExchange Agent was unavailable during initialization.

01830107 The PowerExchange Agent was unavailable during a registration call.

01840101 An error occurred when connecting to common services.

01840102 The SET STIMERM function failed.

01840103 The STIMERM CANCEL function failed.

01840104 An error occurred opening the mailman's queue.

01840105 An error occurred closing the mailman's queue.

01850101 An error was returned from the mailman.

01850102 An error was returned from the mailman.

01850103 The mailman abended.

01850104 The mailman abended.

01850105 The monitor subtask failed.

01850106 The PowerExchange Agent is not active.

01850107 An error occurred during a name/token RETRIEVE.

01850108 Initialization for PowerExchange common services failed.

01900101 Initialization for the module EDMCICIN failed.

01900102 Termination for the module EDMCICIN failed.

01900103 The mailman returned an error.

01900104 A previous error occurred. For more information, see the previous error.

01900105 The sync point 'begin phase 1' function failed.

01900106 The sync point 'end phase 2' function failed.

01900107 The logger stopped with abend U4094. The global directory (EDMSDIR) requested the abend.

01900108 The PowerExchange Agent was not active during initialization.

01900109 The PowerExchange Agent was not active during an OPEN call.

01910101 An invalid function was received from the DB2 ECCR.

01910102 No registration list was found for the table name.

298 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 299: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

01910103 The registration routine returned an error.

01910104 The module could not find a UOW entry, FREEUOW.

01910105 The module could not find UOW entry, RECORD

01910106 Sync point phase 1 failed.

01910107 Sync point phase 2 failed.

01910108 Initialization for the module EDMCICIN failed.

01910109 Termination for the module EDMCICIN failed.

0191010A The PowerExchange Agent is not active.

0191010B The PowerExchange Logger is not available.

0191010C Error in resync processing (receiving outstanding UOWs from Logger)

0191010D Error in count of outstanding UOWs received from Logger

01920101 A previous error occurred. For more information, see the previous error.

01920102 An invalid function code was encountered.

01920103 The INIT function was called twice.

01920104 CIC was not called for initialization.

01920105 The module could not find its entry in the UOW table.

01920106 The module is not capturing the specified file.

01920107 An invalid sync parameter was encountered.

01920109 Initialization for the module EDMCICIN failed.

0192010A Termination for the module EDMCICIN failed.

0192010B The registration routine returned an error.

0192010C The mailman returned an error.

0192010D The PowerExchange Agent is not active.

01930101 Initialization for the module EDMCICIN failed.

01930102 Termination for the module EDMCICIN failed.

01930103 The IMODULE GETMAIN function failed.

01930104 The IMODULE LOAD function failed.

PowerExchange Reason Codes 299

Page 300: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

01930105 The module was unable to get into a supervisory state.

01930106 The module could not find the PowerExchange Agent SSCT.

01930107 The module encountered an invalid agent control block.

01930108 The module could not find the IMS SSCT.

01930109 There are no DBDs to capture.

0193010A Initialization for the module $MSGX failed.

0193010B Termination for the module $MSGX failed.

0193010C The PowerExchange Agent is not active.

01940101 The input vector for the calling program is too high.

01940102 The module encountered an invalid UOW address.

01940103 The PowerExchange Logger stopped, and the global options module (EDMSDIR) requested that the ECCR abend.

01960101 An IMS ESS definition is required.

01970101 The database is not registered for capture.

01970102 The module was not passed the working storage address.

01970103 A name/token RETRIEVE failed.

01970104 Not an online region.

01990101 No databases to capture.

01990102 The module could not locate the DD name for the DBD in TIOT.

01990103 An error occurred in locating JFCB.

01990104 An error occurred when initializing the registration routine.

01990105 An error occurred during in a GET function from the registration routine

019B0101 The input vector for the calling program is too high.

019B0102 The module encountered an invalid UOW address.

019B0103 The PowerExchange Logger stopped, and the global options module (EDMSDIR) requested that the ECCR abend.

019D0101 An IMS ESS definition is required.

01A00101 A subsystem is required.

300 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 301: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

01A00102 A global queue error occurred.

01A00103 The $GENDCB module failed.

01A00104 An OPEN function from the $GENDCB module failed.

01A00105 A CLOSE function from the $GENDCB module failed.

01A00106 An FREE function from the $GENDCB module failed.

01A00107 The DD statement PWXEDMCC is missing.

01A00108 The OPEN function failed.

01A00109 SET STIMERM failed.

01A0010A STIMERM CANCEL failed.

01A0010B An error occurred while the module was connecting to PowerExchange common services.

01A0010C An XCF JOIN function failed.

01A0010D An XCF LEAVE function failed.

01A0010E An XCF DESTDEL function failed.

01A0010F An XCF GET function failed.

01A00110 An XCF PUT function failed.

01A00111 An XCF FREEBUFF function failed.

01A20102 A global queue error occurred.

01A30101 A CIC initialization error occurred.

01A30102 A CIC termination error occurred.

01B70101 The agent from the SSM member is not active.

01B70102 The EDMSCTRL control block is invalid.

01B70103 The program must run in an IMS control region.

01B70104 There is a loop in the "ESAF add" routine.

01A30103 An invalid IPC header was found in the record.

01C40101 The input vector for the calling program is too high.

01C40102 The module encountered an invalid UOW address.

PowerExchange Reason Codes 301

Page 302: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

01C40103 The PowerExchange Logger stopped, and the global options module (EDMSDIR) requested that the ECCR abend.

01C70101 An IMS ESS definition is required.

Function Codes 01 to 0A - Circular QueueThe circular queue issues reason codes that include several parts.

The circular queue reason codes, displayed in the format xxyyzzzz, include the following parts:

• xx is the hexadecimal return code.

• yy is the function code.

• zzzz is the reason code.

“Reason Codes 04050000 to 0812000C0 - Circular Queue” on page 303 lists the circular queue reason codes.

The following table describes the circular queue function codes:

Function Code Description

01 circular queue initialization (INIT)

02 circular queue termination (TERM)

03 circular queue open (OPEN)

04 circular queue close (CLOSE)

05 circular queue get (GET)

06 circular queue put (PUT)

08 circular queue delete (DELETE)

0A circular queue create (CREATE)

11 set end‑of‑file (SETEOF) on circular queue

12 circular queue find‑token (FNDTKN)

302 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 303: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Codes 04050000 to 0812000C0 - Circular QueueThe circular queue issues reason codes from 04050000 through 0812000C0.

The following table describes the circular queue reason codes:

Reason Code Explanation

04050000 The circular queue module (EDMXCIRQ) GET function found no records available and encountered the end‑of‑file.

04050004 The circular queue module (EDMXCIRQ) GET function found no records available from a conditional GET function.

04120004 The circular queue module (EDMXCIRQ) FNDTKN function could not find the $DLICQTS opened‑input control blocks.

08010004 The circular queue module (EDMXCIRQ) INIT function could not find the address for the $DLIGPPL parameter list.

08010040 The circular queue module (EDMXCIRQ) INIT function's virtual‑storage request for a circular queue initialization‑token area failed.

08020004 The circular queue module (EDMXCIRQ) TERM function could not find the address for the $DLIGPPL parameter list.

08020044 The circular queue module (EDMXCIRQ) TERM could not find the token value for the circular queue initialization control block.

08020048 The circular queue module (EDMXCIRQ) TERM function encountered an invalid circular queue initialization control‑block identifier.

08030004 The circular queue module (EDMXCIRQ) OPEN function could not find the address for the $DLIGPPL parameter list.

08030008 The circular queue module (EDMXCIRQ) OPEN function could not find the $DLICQMN control block.

08030010 The circular queue module (EDMXCIRQ) OPEN function encountered an invalid open‑request type.

08030020 The circular queue module (EDMXCIRQ) OPEN function encountered an unavailable GET TASK block because of too many open requests for input.

08030024 The circular queue module (EDMXCIRQ) OPEN function encountered an unavailable dynamic PUT TASK block because the virtual storage request failed.

08030028 The circular queue module (EDMXCIRQ) OPEN function encountered an unavailable static PUT TASK block because of too many open requests for output.

08030030 The circular queue module (EDMXCIRQ) OPEN function encountered a fixed‑length logical record length (LRECL) less than 8 bytes.

08030034 The circular queue module (EDMXCIRQ) OPEN function encountered a fixed‑length LRECL greater than the maximum value allowed for the queue.

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

PowerExchange Reason Codes 303

Page 304: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

08030038 The circular queue module (EDMXCIRQ) OPEN function does not allow the use of the WAIT=NO setting with a global queue.

08040004 The circular queue module (EDMXCIRQ) CLOSE function could not find the address for the $DLIGPPL parameter list.

08040008 The circular queue module (EDMXCIRQ) CLOSE function could not find the $DLICQTS control block.

08040010 The circular queue module (EDMXCIRQ) CLOSE function encountered an unopened $DLICQTS control block.

08040014 The circular queue module (EDMXCIRQ) CLOSE function found that another task opened the $DLICQTS control block.

08040018 The circular queue module (EDMXCIRQ) CLOSE function encountered an unknown $DLICQTS control‑block task type.

08050004 The circular queue module (EDMXCIRQ) GET function could not find the address for the $DLIGPPL parameter list.

08050008 The circular queue module (EDMXCIRQ) GET function could not find the token value for the $DLICQTS control block.

08050010 The circular queue module (EDMXCIRQ) GET function found that the current task control block (TCB) does not own the $DLICQTS control block.

08050014 The circular queue module (EDMXCIRQ) GET function found a $DLICQTS control block not opened for input.

08050018 The circular queue module (EDMXCIRQ) GET function found a $DLICQTS control block at the end‑of‑file.

08050020 The circular queue module (EDMXCIRQ) GET function encountered an invalid $DLICQEB control block.

08060004 The circular queue module (EDMXCIRQ) PUT function could not find the address for the $DLIGPPL parameter list.

08060008 The circular queue module (EDMXCIRQ) PUT function could not find the token value for the $DLICQTS control block.

08060010 The circular queue module (EDMXCIRQ) PUT function found that the current task control block (TCB) does not own the $DLICQTS control block.

08060014 The circular queue module (EDMXCIRQ) PUT function found a $DLICQTS control block not opened for output.

08060018 The circular queue module (EDMXCIRQ) PUT function encountered an invalid record size.

08060020 The circular queue module (EDMXCIRQ) PUT function encountered a non‑zero return code froma STATUS SET,MC,PROCESS macro call

08060024 The circular queue module (EDMXCIRQ) PUT function encountered a non‑zero return code froma STATUS RESET,MC,PROCESS macro call

304 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 305: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

08080004 The circular queue module (EDMXCIRQ) DELETE function could not find the address for the $DLICQPL parameter list.

08080008 The circular queue module (EDMXCIRQ) DELETE function could not find the address for the $DLICQMN control block.

08110004 The circular queue module (EDMXCIRQ) SETEOF function could not find the address for the $DLICQPL macro.

08110010 The circular queue module (EDMXCIRQ) SETEOF function encountered an invalid control‑block identifier for the $DLICQMN control block.

08110014 The circular queue module (EDMXCIRQ) SETEOF function found unclosed PUT tasks.

08110018 The circular queue module (EDMXCIRQ) SETEOF function found no available buffer space for the end‑of‑file indication.

08120004 The circular queue module (EDMXCIRQ) FNDTKN function could not find the address for the $DLIGPPL parameter list.

08120008 The circular queue module (EDMXCIRQ) FNDTKN function could not find the token value for the $DLICQMN control block.

08120010 The circular queue module (EDMXCIRQ) FNDTKN function encountered a missing TCB owner value.

08120014 The circular queue module (EDMXCIRQ) FNDTKN function found that the current address space did not create this queue.

08120018 The circular queue module (EDMXCIRQ) FNDTKN function could not find any input $DLICQTS control blocks for this queue.

0803000C The circular queue module (EDMXCIRQ) OPEN function encountered an invalid control‑block identifier for the $DLICQMN control block.

0803003C The circular queue module (EDMXCIRQ) OPEN function does not allow the use of the find‑token (FNDTKN=Y) parameter with a global queue.

0804000C The circular queue module (EDMXCIRQ) CLOSE function encountered an invalid control‑block identifier for the $DLICQTS control block.

0804001C The circular queue module (EDMXCIRQ) CLOSE function found that an incorrect task attempted to close the $DLICQTS control block (FNDTKN processing).

0805000C The circular queue module (EDMXCIRQ) GET function encountered an invalid control‑block identifier for the $DLICQTS control block.

0805001C The circular queue module (EDMXCIRQ) GET function encountered a COND=YES setting along with an incompatible WAIT=NO setting.

080500FF The circular queue module (EDMXCIRQ) GET function encountered a termination request from the CQTECB post code.

0806000C The circular queue module (EDMXCIRQ) PUT function encountered an invalid control‑block identifier for the $DLICQTS control block.

PowerExchange Reason Codes 305

Page 306: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0806001C The circular queue module (EDMXCIRQ) PUT function encountered an invalid $DLICQEB control block.

080600FF The circular queue module (EDMXCIRQ) PUT function encountered a termination request from the CQTECB post code.

0808000C The circular queue module (EDMXCIRQ) DELETE function encountered an invalid identifier for the $DLICQMN control block.

080A0004 The circular queue module (EDMXCIRQ) CREATE function could not find the address for the $DLIGPPL parameter list.

080A0010 The circular queue module (EDMXCIRQ) CREATE function encountered a subpool value outside 0 and 255 (inclusive).

080A0014 The circular queue module (EDMXCIRQ) CREATE function encountered a GET task‑count value outside 1 and 15 (inclusive).

080A0018 The circular queue module (EDMXCIRQ) CREATE function encountered a PUT task‑count value outside 0 and 255 (inclusive).

080A001C The circular queue module (EDMXCIRQ) CREATE function encountered a buffer count value outside 1 and 255 (inclusive).

080A0020 The circular queue module (EDMXCIRQ) CREATE function encountered a buffer size value outside 4096 and 32760 (inclusive).

080A0030 The circular queue module (EDMXCIRQ) CREATE function's virtual‑storage request for the $DLICQMN control block failed.

080A0034 The circular queue module (EDMXCIRQ) CREATE function's virtual‑storage request failed for the $DLICQTS control block (GET TASK function).

080A0038 The circular queue module (EDMXCIRQ) CREATE function's virtual‑storage request failed for the $DLICQTS control block (PUT TASK function).

080A003C The circular queue module (EDMXCIRQ) CREATE function's virtual‑storage request for circular queue buffers failed.

0811000C The circular queue module (EDMXCIRQ) SETEOF function could not find the token value for the $DLICQMN control block.

0812000C The circular queue module (EDMXCIRQ) FNDTKN function encountered an invalid control‑block identifier for the $DLICQMN control block.

306 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 307: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Codes 0A0A000E to 0A0B00D8 - Log Write APIThe Log Write API issues function reason codes from 0A0A000E through 0A0B00D8.

The following table lists the Log Write API function reason codes:

Reason Code Explanation

0A0A000E FirstThreeParmsIncomplete

0A0A0010 EdmcstubGetmainFailed

0A0A0011 LoadForEdmciapiFailed

0A0A0012 TokenFunctionMismatch

0A0A0013 InvalidToken

0A0B0001 TooManyParms

0A0B0002 RegTypeConflictWithAgent

0A0B0003 FunctionUnknownOrInvalidPerInitParms

0A0B0004 NotEnoughParmsForFunction

0A0B0005 FunctionProhibitedType0

0A0B0006 FunctionProhibitedMultiTasked

0A0B0007 UOWNameIsNotLoggerConnectName

0A0B0008 DataParmInvalid

0A0B0009 2ndDataParmInvalid

0A0B000A FunctionInvalidPerInitOptions

0A0B000B InvalidInitParm

0A0B000C InternalErrorHandlingRegistrations

0A0B000D InvalidAPIInitToken

0A0B000F NullParameterPassed

0A0B0014 NoAPIInitToken

0A0B0015 APIInitTokenFunctionMismatch

0A0B0016 TokenGetmainFailed

0A0B0017 LoggerDisconnectFailed

0A0B0018 TERM_indoubt_UOW

0A0B0019 RegistrationCheckFailed

PowerExchange Reason Codes 307

Page 308: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0A0B001A LoggerConnectionFailed

0A0B001B LoggerQueueOpenFailed

0A0B001C LoggerInterfaceWriteFailed

0A0B001D UOWAlreadyExists

0A0B001F SendingChangeAfterCHK1

0A0B0020 InternalErrorProcessingUOWs

0A0B0021 CommonSvcsInitFailed

0A0B0022 CommonSvcsConnectFailed

0A0B0023 ErrorObtainingLoggerResyncInfo

0A0B0024 ErrorTerminatingCommonSvcs

0A0B0025 HighSeqNotAscending

0A0B0026 LowSeqNotAscendingOrZero

0A0B0027 NameTokenFunctionFailed

0A0B0028 MissingAPIInitToken

0A0B0029 InconsistentMultiTaskInits

0A0B002A UOWNotFound

0A0B002B MustIssueCHK1First

0A0B002C TooMuchExtendedInfoInPkt

0A0B002D TooMuchExtendedInfoInChng

0A0B002E InvalidLCIReturnArea

0A0B002F MissingMSGDescTag

0A0B0030 InvalidDescTag

0A0B0031 EventMarkBuildFailed

0A0B0032 EvntMaxEdmnamesExceeded

0A0B0033 EvntMaxDescExceeded

0A0B0034 RegistrationInitializationFailed (this is new)

0A0B0035 AgentServicesUnavailable (this is new)

308 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 309: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0A0B0036 RegistrationConnectionFailed

0A0B0037 RegistrationDisconnectionFailed

0A0B0038 InitType1MultiTaskedProhibited

0A0B0039 ConnTokenLogicErrorOnInit

0A0B003A APIConnTokenNotFoundInChain

0A0B003B APIConnTokenLogicErrorAtTerm

0A0B003C FunctionProhibitedSingleTaskTerm

0A0B003D LoggerMultitaskDisconnectFailed

0A0B003E RegistrationMultitaskDisconnectionFailed

0A0B0080 RegistrationNameTooLong

0A0B0081 EccrNameTooLong

0A0B0082 Wrapper_InternalError

0A0B0083 Wrapper_TokenFunctionMismatch

0A0B0084 Wrapper_MemoryAllocationFailed

0A0B0085 Wrapper_InvalidToken

0A0B0086 Wrapper_UserIdTooLong

0A0B0087 Wrapper_MessageTooLong

0A0B00C0 XData_GNRS_Error

0A0B00C1 XData_RSTR_Error

0A0B00C2 XData_GHSQ_Error

0A0B00C3 XData_GLCI_Error

0A0B00D0 XData_LR_INIT_Error

0A0B00D1 XData_LR_CONN_Error

0A0B00D2 XData_LR_OPEN_Error

0A0B00D3 XData_LR_GETL_Error

0A0B00D4 XData_LR_BUOW_Missing

0A0B00D5 XData_LR_NoRecords

PowerExchange Reason Codes 309

Page 310: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0A0B00D6 XData_LR_BUOWsNotFound

0A0B00D7 XData_LR_PrematureEOF

0A0B00D8 XData_LR_SIGNON_Missing

Reason Codes 0A0D0300 to 0A0E0320 - Log Read APIThe Log Read API issues function reason codes from 0A0D0300 to 0A0E0320.

The following table lists the Log Read API function reason codes:

Reason Code Explanation

0A0D0300 EdmlrstbGetmainFailed

0A0D0301 LoadForEdmlrapiFailed

0A0D0302 TokenFunctionMismatch

0A0D0303 InvalidToken

0A0D02FE FirstThreeParmsIncomplete

0A0E0001 GETL_PROGRESS

0A0E0002 GETL_TIMEOUT

0A0E0003 GETL_EOF

0A0E0050 TooManyConnects

0A0E0051 InvalidSTDChgRec

0A0E0052 InvalidChgRecPFormat

0A0E0053 InvalidCRFChgRec

0A0E0054 InvalidSBCChgRec

0A0E0055 ConnectionIsOpen

0A0E0056 ConnectionNotOpen

0A0E0057 InvalidCONNParm

0A0E0058 LoggerConnectionFailed

0A0E0059 IncorrectHeaderVersion

0A0E005A ESTAEFailedInHelper

310 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 311: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0A0E005B HelperAttachFailed

0A0E005C MissingOrDupSegs

0A0E005D SegBufferSizeError

0A0E005E InvalidOpenRBASeg

0A0E005F ErrorManagingSegments

0A0E0060 ConnectionAlreadyOpen

0A0E0061 HelperTaskFailed

0A0E0062 LoggerDidNotRespondToCommand

0A0E0063 LoggerTerminatedConnection

0A0E0064 InvalidEventRec

0A0E0065 StorageObtainFailedInHelper

0A0E0066 OPENEndSEQltBeginSEQ

0A0E0067 InternalPlistError

0A0E0070 TimerSvcsActiveTimerInTransition

0A0E0071 TimerSvcsNoCONNToken

0A0E0072 TimerSvcsSTIMERMError

0A0E0073 TimerSvcsTimerAlreadyExists

0A0E0074 TimerSvcsTimerIDMismatch

0A0E0075 TimerSvcsNoActiveTimerInToken

0A0E0076 TimerSvcsTooManyTimers

0A0E0100 InvalidTokenType

0A0E0101 InvalidINITToken

0A0E0102 InvalidCONNToken

0A0E0103 ErrorCreatingLRAPILocalQueue

0A0E0104 ErrorOpeningLRAPILocalQueue

0A0E0105 ErrorLRAPILocalQueueNotOpen

0A0E0106 ErrorReadingLRAPILocalQueue

PowerExchange Reason Codes 311

Page 312: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0A0E0107 ErrorLRAPILocalQueueEOF

0A0E0108 MoreThanOneAPIPerTCB

0A0E0109 ModuleLoadFailed

0A0E010A ErrorWritingLRAPILocalQueue

0A0E010B ErrorCreatingINTLSTCommand

0A0E010C InterestListFailed

0A0E0110 ErrorDuringXCFJoin

0A0E0111 ErrorCreatingLoggerGlobalQueue

0A0E0112 ErrorOpeningLoggerGlobalQueue

0A0E0113 ErrorClosingLoggerGlobalQueue

0A0E0114 ErrorSendingCmdToLogger

0A0E0115 ErrorReadingLoggerGlobalQueue

0A0E0116 ErrorTerminatingCommonSvcs

0A0E0117 ErrorInXCFGetMsg

0A0E0118 ErrorInXCFGetGroup

0A0E0119 ErrorInXCFFreeBuff

0A0E011A RequestDataXferFailed

0A0E011B InvalidRecordFromLogger

0A0E011C StopDataXferFailed

0A0E011D InvalidLCIReturnArea

0A0E011E InvalidOpenParm

0A0E011F BeginSeqRequired

0A0E0120 SEDMInitError

0A0E0121 SEDMAddError

0A0E0122 SEDMAddDuplicateEdmname

0A0E0123 SEDMTermError

0A0E0124 SEDMInternalError

312 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 313: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

0A0E02F5 TooManyParms

0A0E02F6 FunctionUnknownOrInvalidPerInitParms

0A0E02F7 NotEnoughParmsForFunction

0A0E02FF NullParameterPassed

0A0E0304 TokenGetmainFailed

0A0E0317 CommonSvcsInitFailed

0A0E0318 CommonSvcsConnectFailed

0A0E0319 AgentServicesUnavailable

0A0E0320 ErrorProcessingExternalParameters

Reason Codes 10000001 to 1007FFFF - DB2 ECCRThe DB2 ECCR issues reason codes from 10000001 to 1007FFFF.

The following table lists the DB2 ECCR reason codes:

Reason Code Explanation

10000001 The PowerExchange initialization module (CCDINI0) encountered an error when it attempted to initialize PowerExchange common services.

10000002 The PowerExchange initialization module (CCDINI0) encountered an error when it attempted to connect to PowerExchange common services.

10000003 The PowerExchange initialization module (CCDINI0) encountered an error when it attempted to initialize the schema checker (CCDSCHE).

10030001 An attempt to get an EDMNAME failed.

10030002 An attempt to get a schema failed.

10030003 An attempt to change a schema failed.

10030004 An error occurred when the PDX interface (CCDRIOM) tried to acquire a command buffer.

10030005 An error occurred when the PDX interface (CCDRIOM) tried to acquire a reply buffer.

10030006 An error occurred when the PDX interface (CCDRIOM) received a call from the $RIOM macro.

10030007 The PDX interface (CCDRIOM) could not find the EDMNAME in the registration list.

10040001 The DB2 schema does not match the registration in the PowerExchange repository.

10040002 An attempt to build an RCD record failed.

PowerExchange Reason Codes 313

Page 314: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

10040003 A GETSCHEM call to the PDX interface (CCDRIOM) failed.

10040005 During initialization, the DB2 ECCR schema checker (CCDSCHE) could not find a schema that matched the schema specified in the message.

10060001 Schema verification failed.

10070001 The DB2 ECCR found and invalid log record type.

10070002 The DB2 ECCR could not locate the CREATE TIME field for the change record.

10070003 The DB2 ECCR could not locate the ALTER TIME field for the change record.

10070004 The DB2 ECCR (X029261) was unable to determine the DB2 version.

10070005 The DB2 ECCR could not locate the data definition language (DDL) record end.

10070006 The DB2 ECCR could not determine the data type for the column.

10070007 The DB2 ECCR could not locate the source type identification (SOURCETYPEID) in the SYSCOLUMNS row.

Reason Codes 00000004 to 00000054 - Chainer Module (EDMQMGR0)

The Chainer Module issues reason codes from 00000004 to 00000054.

The following table lists the Chainer Module reason codes:

Reason Code Explanation

00000004 Record Not Found

00000008 Insufficient Storage

0000000C Invalid Record Prefix (Bad Addr)

00000010 Invalid Flags or Key Addr

00000014 Invalid Function Code

00000018 Invalid Blksize/datal/lrecl

0000001C TOQ Is Invalid

00000020 Invalid Freespace Id

00000024 Broken Synonym Chain

00000028 KEYL Is Zero

0000002C Ver Failed - BLKSIZE

314 Chapter 8: Abend, Return, and Reason Codes in PowerExchange Messages

Page 315: Informatica PowerExchange - 10.2 HotFix 1 - Message Reference … Documentation... · 2018-08-07 · Preface P o w e r E x c h a n g e M e s s a g e R e f e r e n c e V o l u m e

Reason Code Explanation

00000030 Ver Failed - Record Prefix

00000034 Ver Failed - Ff000000 Not Last

00000038 Exit Returned Non-zero

0000003C Chain In Use

00000040 Chain Already Locked, Lock Fails

00000040 Chain Not Locked, Unlock Fails

00000048 Invalid Owner of Locked Chain

0000004C Serial Option Required Lock/unlk

00000050 Invalid Register Form Parms

00000054 Pagefix Unknown Return Code

PowerExchange Reason Codes 315


Recommended