PWX 86 Installation Guide

Informatica® PowerExchange®

(Version 8.6)

Installation Guide

Informatica PowerExchange Installation Guide

Version 8.6 June 2008

Copyright (c) 1998–2008 Informatica Corporation. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

Copyright, Byte Designs Ltd. All rights reserved.

This product includes ICU software which is copyright (c) 1995-2003 International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://www-306.ibm.com/software/globalization/icu/license.jsp.

The product includes the zlib library copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler.

DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

Part Number: PWX-INS-860-0003

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiScope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1: PowerExchange Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PowerExchange Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PowerExchange Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2: Preparing to Install PowerExchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Preparation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Release and Maintenance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PowerExchange Base: MVS and DB2 for z/OS Maintenance Requirements . . . . . . . . . . . . 6

PowerExchange Bulk Data Movement: Database Requirements by Platform . . . . . . . . . . . . 6

PowerExchange Change Data Capture: Requirements on MVS . . . . . . . . . . . . . . . . . . . . . 7

PowerExchange Change Data Capture: Requirements on Other Platforms . . . . . . . . . . . . 11

Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Using PowerExchange with Earlier Versions of PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using Multiple Versions of PowerExchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3: Installing PowerExchange on i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing PowerExchange on i5/OS for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Task Flow for a First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Install PowerExchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 4: Installing PowerExchange on Linux and UNIX . . . . . . . . . . . . . . . . . . . . . 23Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing PowerExchange on Linux or UNIX for the First Time . . . . . . . . . . . . . . . . . . . . . . 23

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23


Install PowerExchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


Applying a Service Pack for PowerExchange on Linux or UNIX . . . . . . . . . . . . . . . . . . . . . . . 29

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Task Flow for a Installing a Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table of Contents iii

Install the PowerExchange Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5: Installing PowerExchange on MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Understanding MVS Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Installing PowerExchange on MVS for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


Space Requirements for PowerExchange Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Phase I: Install the PowerExchange Base Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Phase II. Install the PowerExchange Change Data Capture Software . . . . . . . . . . . . . . . . 48

Phase III: Install the PowerExchange Software for Specific Data Sources . . . . . . . . . . . . . 50


Upgrading PowerExchange on MVS to a New Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Task Flow for Upgrading to a New Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Phase I: Upgrade the PowerExchange Base Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Phase II: Upgrade the PowerExchange Change Data Capture Software . . . . . . . . . . . . . . . 62

Phase III: Upgrade the PowerExchange Software for Specific Data Sources . . . . . . . . . . . . 63

Phase IV: Post-Upgrade Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65


Installing a Service Pack for PowerExchange on MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Task Flow for a Installing a Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Phase I: Install the PowerExchange Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Phase II: Update the PowerExchange Software for Specific Data Sources . . . . . . . . . . . . . 71

Phase III: Post-Service-Pack Install Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 6: Installing PowerExchange on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 73Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Installing PowerExchange on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Installation Task Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Step 1. Log In as a User with the Required Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Step 2. Run the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Step 3. Set Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Step 4. Install the PowerExchange ODBC Drivers (Optional) . . . . . . . . . . . . . . . . . . . . . 76

Step 5. Test the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77


Applying a Service Pack for PowerExchange on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Step 1. Run the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Step 2. Copy the License and Configuration Files to the Service Pack Directory . . . . . . . . 78

Step 3. Test the Service Pack Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

iv Table of Contents

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

v Table of Contents

vi Table of Contents

Preface

This guide describes how to install the PowerExchange® base product and service packs. It also describes how to upgrade PowerExchange to a new release.

ScopeThe guide covers installation for the following PowerExchange 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)

TerminologyIn this guide, the term MVS refers to both z/OS and OS/390 operating systems.

For additional terminology, see the glossary in the PowerExchange Reference Manual.

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

vii

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

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.

Informatica Global Customer SupportThere are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone, email, or the WebSupport Service.

Use the following email addresses to contact Informatica Global Customer Support:

♦ [email protected] for technical inquiries

♦ [email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Informatica Corporation Headquarters100 Cardinal WayRedwood City, California 94063United States

Toll Free +1 877 463 2435

Standard RateBrazil: +55 11 3523 7761 Mexico: +52 55 1168 9763 United States: +1 650 385 5800

Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

Toll Free 00 800 4632 4357

Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

Informatica Business Solutions Pvt. Ltd.Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008India

Toll Free Australia: 1 800 151 830Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

viii Preface

C H A P T E R 1

PowerExchange Installation Overview

This chapter includes the following topics:

♦ PowerExchange Overview, 1

♦ PowerExchange Components, 1

PowerExchange OverviewPowerExchange can perform the following functions to synchronize a data source and data target:

♦ Bulk data movement to materialize or entirely refresh a data target.

♦ Change data capture to keep a data source and data target synchronized.

PowerExchange bulk data movement can move large amounts of data between different platforms efficiently. However, frequent bulk data movement operations can be costly in terms of space, time, and staff resources.

With PowerExchange change data capture (CDC), you can capture only the insert, update, and delete changes that are made to a data source. PowerExchange CDC has minimal impact on the performance and availability of the source database, tables, and files. PowerExchange provides two methods of change data capture:

♦ Synchronous change data capture, which occurs in real time by integrating into the transaction performing the change

♦ Asynchronous change data capture, which captures the changes from database log files

PowerExchange works with PowerCenter to enable you move bulk data and change data to a variety of data targets.

PowerExchange ComponentsPowerExchange uses some or all of following components to perform its functions, depending on the platform that you are using:

PowerExchange Navigator The graphical user interface from which you define and manage data maps, capture registrations, and extraction maps for the data sources from which you want to extract bulk data or capture change data.

1

PowerExchange uses these definitions to determine the data sources to process. Capture registrations and extraction maps pertain to change data capture (CDC) only.

PowerExchange ListenerManages data maps for nonrelational files and DB2 tables, and capture registrations and extraction maps for all data sources. The PowerExchange Listener maintains these definitions in the following files: data maps in the DATAMAPS file, capture registrations in the CCT file, and extraction maps in the DTLCAMAP or CAMAPS file. The PowerExchange Listener also handles extraction requests for bulk data and change data.

If a data source or data target is remote from the system on which you are using PowerExchange, you must also run a PowerExchange Listener on the remote data source or target to communicate with PowerExchange.

PowerExchange AgentOn an MVS system, provides capture registration information to the following ECCRs during CDC:

♦ DB2

♦ IMS synchronous

♦ Batch VSAM

♦ CICS/VSAM

Other ECCRs read capture registration information directly from the CCT data set. For all of the ECCRs, the PowerExchange Agent verifies the capture registration information.

The PowerExchange Agent also manages global queues and data flow among various PowerExchange CDC components.

PowerExchange LoggerOn an MVS system, receives captured change data from the ECCRs that are connected to it and stores the change data in log data sets. The change data is then available for real-time extractions or PowerExchange Condense jobs.

PowerExchange Environmental Change Capture Routine (ECCR) On an MVS system, captures change data from a data source and passes the captured changes to the PowerExchange Logger for recording. PowerExchange provides an ECCR for each type of data source. Depending on the source type, the ECCR captures changes synchronously as they are made or asynchronously from database logs.

PowerExchange CondenseOptionally creates condense files that contain a condensed version of the change data in the change stream. If you use this optional feature, PowerExchange extracts change data from condense files rather than from log files. You can run multiple Condense jobs at a time.

The PowerExchange components that you install and the installation steps that you must perform depend on the PowerExchange functions that you want to perform: bulk data extraction, change data capture, or both. The following table shows which components are involved in bulk data extraction and change data capture and which PowerExchange documents to refer to when customizing these components:

Component Bulk Data Movement

Change Data Capture Customization Reference

PowerExchange Navigator

X X - PowerExchange Reference Manual- PowerExchange Navigator User Guide

PowerExchange Listener

X X - PowerExchange Reference Manual- PowerExchange Bulk Data Movement

Guide- PowerExchange Change Data Capture

Guide for i5/OS- PowerExchange Change Data Capture

Guide for z/OS

2 Chapter 1: PowerExchange Installation Overview

The flexibility of the PowerExchange architecture enables you to design many alternative configurations of these components. For CDC, you can use multiple instances of the PowerExchange CDC components on a single system to handle large volumes of change data. For example, you might want to use one PowerExchange Logger for each different change data source. For more information about change data capture configuration, see the PowerExchange Change Data Capture Guide for z/OS, PowerExchange Change Data Capture Guide for i5/OS, and the adapter guides for Microsoft SQL Server, Oracle, and DB2 for Linux, UNIX, and Windows.

PowerExchange Agent

X PowerExchange Change Data Capture Guide for z/OS

PowerExchange Logger


Environmental Change Capture Routine (ECCR) for each data sources


PowerExchange Condense

X - PowerExchange Change Data Capture Guide for i5/OS

- PowerExchange Change Data Capture Guide for z/OS

- PowerExchange DB2 for Linux, UNIX, and Windows Adapter Guide

- PowerExchange Oracle Adapter Guide- PowerExchange SQL Server Adapter

Guide

Component Bulk Data Movement

Change Data Capture Customization Reference

PowerExchange Components 3

4 Chapter 1: PowerExchange Installation Overview

C H A P T E R 2

Preparing to Install PowerExchange


♦ Preparation Overview, 5

♦ Release and Maintenance Requirements, 5

♦ Obtaining a License Key, 12

♦ Using PowerExchange with Earlier Versions of PowerCenter, 13

♦ Using Multiple Versions of PowerExchange, 13

Preparation OverviewBefore installing PowerExchange on any platform, perform the following tasks:

♦ Verify that your source systems have all of the required maintenance for the operating system and data management software for the PowerExchange function that you intend to perform.

♦ Get a license key.

♦ If you plan to use this PowerExchange installation with an earlier version of PowerExchange or PowerCenter, review the following topics:

− Using PowerExchange with Earlier Versions of PowerCenter, 13

− Using Multiple Versions of PowerExchange, 13

Release and Maintenance RequirementsApply all recommended maintenance for the operating system and data management software on each of your source systems, as described in the following topics:

♦ PowerExchange Base: MVS and DB2 for z/OS Maintenance Requirements, 6

♦ PowerExchange Bulk Data Movement: Database Requirements by Platform, 6

♦ PowerExchange Change Data Capture: Requirements on MVS, 7

♦ PowerExchange Change Data Capture: Requirements on Other Platforms, 11

5

PowerExchange Base: MVS and DB2 for z/OS Maintenance Requirements

The PowerExchange base product requires certain maintenance for the following MVS and DB2 for z/OS versions. You must apply this maintenance to perform PowerExchange bulk data movement or change data capture.

z/OS and OS/390

DB2 for z/OS

PowerExchange Bulk Data Movement: Database Requirements by Platform

To perform bulk data movement, PowerExchange requires the data source to have a minimum database version or a version later than the minimum. The following table shows the minimum database versions by platform:

Version APAR Number APAR Description

OS/390 2.10, z/OS 1.1 - 1.5

PQ75394 DLL implicit load use count exceeded never decremented.

z/OS 1.6 PK12893 Poor TCP performance when using TCP Segmentation Offload and applicationswith small data writes.

z/OS 1.7 PK50222 The SSL connection code has been updated to properly handle an empty SSL fragment when an AT-TLS policy file is used to implement SSL protocol for PowerExchange.

PK12893 Poor TCP performance when using TCP Segmentation Offload and applicationswith small data writes.

z/OS 1.8 and 1.9

PK46403 The SSL connection code has been updated to properly handle an empty SSL fragment when an AT-TLS policy file is used to implement SSL protocol for PowerExchange.


6.1 PQ50802 Resolution for Listener 978-04 when the PowerExchange Listener is using RRSAF.

PQ73222 DSNT501I Resource unavailable (timeout) with reason code 00C9008E using tablespace generated with LOCKMAX 0

7.1 PQ50802 Resolution for Listener 978-04 when the PowerExchange Listener is using RRSAF.

PQ73222 DSNT501I Resource unavailable (timeout) with reason code 00C9008E using tablespace generated with LOCKMAX 0

Platform Database Minimum Database Version

MVS Adabas 6.2Predict 4.1.2Natural 2.2.8

Datacom 10

DB2 for z/OS 5.1

IDMS 14.1

IMS 7.1

6 Chapter 2: Preparing to Install PowerExchange

PowerExchange Change Data Capture: Requirements on MVSTo perform change data capture (CDC) on MVS systems, PowerExchange requires specific MVS, CICS TS, and DB2 for z/OS versions and maintenance levels.

AIX DB2 for Linux, UNIX, and Windows

8.1 with FixPack 11

Informix 7.3

Oracle 9i

Client requirements:- For 11g: 9.2.04 client.- For 11g support for BINARY_FLOAT and BINARY_DOUBLE:10.2.0.1 or higher

Sybase 12.5

HP-UX DB2 for Linux, UNIX, and Windows

8.1 with FixPack 11

Informix 7.3

Oracle 9i

Client requirements:- For 11g: 9.2.04 client.- For 11g support for BINARY_FLOAT and BINARY_DOUBLE:10.2.0.1 or higher

Sybase 12.5

Sun Solaris DB2 for Linux, UNIX, and Windows

8.1 with FixPack 11

Informix 7.3

Oracle 9i

Client requirements:- For 11g: 9.2.04 client.- For 11g support for BINARY_FLOAT and BINARY_DOUBLE:10.2.0.1 client or higher

Sybase 12.5

Windows DB2 for Linux, UNIX, and Windows

8.1 with FixPack 11

Microsoft SQL Server

SQL Server 2000

Oracle 9i

Client requirements:- For 11g: 9.2.04 clientFor 11g support for BINARY_FLOAT and BINARY_DOUBLE: 10.2.0.1 client or higher

Platform Database Minimum Database Version

Release and Maintenance Requirements 7

z/OS and OS/390 Operating SystemCDC requires OS/390 2.10.0 or later or any z/OS version. Also, you must apply the following PTFs in addition to those listed in “PowerExchange Base: MVS and DB2 for z/OS Maintenance Requirements” on page 6.

CICS Transaction Server (CICS TS)CDC requires CICS TS 1.2 or later. If you use any of the following CICS TS versions, you must apply the PowerExchange patch for that version:

♦ CICS TS 2.2: Apply PowerExchange 5.0 Patch 10 or a later patch.

♦ CICS TS 2.3: Apply PowerExchange 5.1.0 Patch 7 or a later patch.

♦ CICS TS 3.1: Apply PowerExchange 5.2.2 Patch 4 or a later patch.

Note: Function Shipping of File Requests is supported for all CICS TS releases from 1.2 except 2.1.

Also, you might need to apply CICS/TS PTFs. The following table shows the PTFs that are required for CDC, if any, by CICS TS version:


OS/390 2.10, z/OS 1.1 - 1.4

OW40736 Invalid Search for largest block size for EXCP DCB.

OW53212 DIV SAVE ABEND08B RC00510805 in z/Architecture mode.

z/OS 1.1 - 1.4 OW56713 HSPSERV SREAD invalidly returns page of zeros when SWRITE to the same page is deferred.

PQ75394 DLL implicit load use count exceeded never decremented.

z/OS 1.1 - 1.5 OA01585 z/Architecture mode DIV SAVE HIPERSPACE pages in real.

OA03727 z/Architecture mode DIV SAVE HIPERSPACE pages in real SRM support for RSM APAR OA01585.

z/OS 1.4 - 1.6 PQ94363 Repositioning performance degradation multi-volume FBS data set

z/OS 1.4 - 1.7 OA10852 Deadlock between SYSZTIOT and SYSVSAM.

z/OS 1.8 - 1.9 PK50785 Poor performance with C/C++ I/O users of data sets allocated with candidate volumes.

CICS TS Version APAR Number APAR Description

1.3 PQ90035 Global user exit XFCSREQC does not get driven for file reopen processing.

2.2 PQ69434 Results the same for UEP_FC_RECORD_ID_L when keylength is set to zero or if it is committed while writing XFCFRIN exit.

PQ72126 RLS function ship from R620 to R530 results in INVALID_UPDATE_TOKEN RESP2=47 INVREQ.

PQ82269 Token not supplied to XFCFROUT exit on READNEXT with UPDATE.

PQ80138 Global user exit XFCSREQC does not get driven for file reopen processing.

2.3 PQ82116 Global user exit XFCSREQC does not get driven for file reopen processing.

3.1 No maintenance required.

3.2 No maintenance required.


DB2 for z/OSCDC requires DB2 for z/OS 6.1 or later. Also, you must apply the PTFs that are associated with the APARs listed in the following table for your DB2 version:

Table 2-1. DB2 for z/OS Required APAR Fixes (Sheet 1 of 3)


6.1 II11809 Recommended DB2 fixes for Data Propagator Capture and Apply.

PQ29170 IFCID306 READ CLAIM while reading compressed log records.

PQ41926 Cached dynamic (CACHEDDYN) statement loops after running RUNSTATS.

PQ42760 ABEND0C4 DSNIDLGR +X'1F70'.

PQ44148 ABEND0C4-4 in DSNIDLGR + 1764.

PQ50821 Various abends in DSNIDCML due to bad compression dictionary address.

PQ53014 Not all log records returned for IFI IFCID 306 log read.

PQ53869 Wrong records returned from IFI READS IFCID 306 call.

PQ60816 ABEND0C4 in DSNIDCML +'12EA' during DPROPR Capture processing XRUI.

PQ61030 DSNIDLGR ABEND0C4 RC00000004 (RSN04) at offset +F3A.

PQ61421 MSGDSNJ113E is issued while reading the logs for DPROPR Capture DSNJ113E LOG.

PQ65887 ABEND0C4 DSNIDCML +1CDC when decompressing log record during IFC 306 READ request after PAGESET OPEN request failed (Datasharing).

PQ67803 ABEND04E RC00E20005 DSNSVBK +08F2 IN DSNIDALC while freeing the storage for control block for Merged Parameter List (MLST) (Datasharing).


7.1 PQ53014 Not All Log Records Returned For IFI IFCID 306 log read.

PQ53869 Wrong records returned from IFI READS IFCID 306 call.

PQ60816 ABEND0C4 in DSNIDCML +'12EA' during DPROPR Capture processing XRUI.

PQ61030 DSNIDLGR ABEND0C4 RC00000004 (RSN04) at offset +F3A.

PQ61421 MSGDSNJ113E is issued while reading the logs for DPROPR Capture DSNJ113E LOG.

PQ65887 ABEND0C4 DSNIDCML +1CDC when decompressing log record during IFC 306 READ request after PAGESET OPEN request failed (Datasharing).

PQ67803 ABEND04E RC00E20005 DSNSVBK +08F2 IN DSNIDALC while freeing the storage for control block for Merged Parameter List (MLST) (Datasharing).

PQ82224 Missing log records on IFCID306 request - Data Sharing.

PQ93306 ABEND04E RC00C90207 DSNIOW ERQUAL5002 after APARs PQ78544 (UQ87356) and PQ89051 (UQ89609).

PQ96356 RC00C90063 DSNIDCML ERQUAL5004 log variation numbers unknown.

PQ96933 DSNT376I 010.PFTXTN01 PREFORMAT LOCK TIMEOUT (Abend0C4 in DSNIDCML).

PK17147 DPROPR Capture CLAIMS not released.

PK14645 ABEND0C4 DSNIDCML +B40.

PK21687 00E60864 returned on a READS reading compressed log records.

PK25167 Capture job got ABEND04E RC00C9007E after other member executed ALTER TABLE ADD COLUMN.

PK38473 ABEND04E RC00C90101 DSNIDCML VRACE5003 while processing variation 1 or 3 record pairs.

PK46871 IFCID306 call has incorrect value for QW0306RS and QW0306DG when compression dictionary is unavailable.

8.1 PQ92288 Restriction for Compatibility Mode being removed.

PQ96933 DSNT376I 010.PFTXTN01 PREFORMAT LOCK timeout (Abend0C4 in DSNIDCML).

PK08078 Mixed schema log records following ALTER DATATYPE on Changed Data Capture tables.

PK17147 DPROPR Capture CLAIMS not released.

PK14645 ABEND0C4 DSNIDCML +B40

PK20136 IF 306 missing commit record in data sharing.

PK21687 00E60864 returned on a READS reading compressed log records.

PK25167 Capture job got ABEND04E RC00C9007E after other member executed ALTER TABLE ADD COLUMN.

PK35583 Invalid value in QW0306RS when using IFCID306 with compressed tablespaces.

PK35606 ABEND0C7 or INCORROUT when a REORG SHRLEVEL CHANGE is run on a compressed table space while the data is being propagated.

PK38473 ABEND04E RC00C90101 DSNIDCML VRACE5003 while processing variation 1 or 3 record pairs.

PK56336 Make LGBEDITPROC flag consistent with IFC306 processing.




AdabasCDC requires Adabas 6.2 or later. The minimum requirements for Natural and Predict are: Natural 2.2.8 or later, and Predict 4.1.2 or later.

Also, CDC requires that you apply the following Adabas ZAPs if you use Adabas 8.1.2 or 8.1.3:

♦ For Adabas 8.1.2, apply AO812024.

♦ For Adabas 8.1.3, apply AO813011.

DatacomCDC requires Datacom version 10 or later.

IDMSCDC requires IDMS 14.1 or later.

IMSIMS log-based CDC requires IMS 7.1 or later.

IMS synchronous CDC requires IMS 8.1 or later. If you use the PowerExchange CRG software, you must IPL the system on which IMS synchronous CDC runs in z/Architecture® mode. IMS synchronous CDC also requires the following IMS maintenance:

PowerExchange Change Data Capture: Requirements on Other Platforms

To perform CDC on platforms other than MVS, PowerExchange requires specific operating system or database versions and maintenance.

AIXCDC requires AIX 5.2 or later. CDC also requires the following AIX maintenance:

OS/400 and i5/OSDB2 for i5/OS CDC requires OS/400 or i5/OS 4.5 or later.

9.1 PK35606 ABEND0C7 or INCORROUT when a REORG SHRLEVEL CHANGE is run on a compressed table space while the data is being propagated.

PK56336 Make LGBEDITPROC flag consistent with IFC306 processing.


9.1 PK24491 ABEND0C1 in DFSDLDD0 during cascade delete due to old PSTCURWA value.

APAR Number APAR Description

IY75338 Lack of serialization within the loadAndInit AIX function. Application fails on dlopen.




UNIXOn UNIX, CDC has the following minimum requirements for DB2 and Oracle. For Oracle, you must apply the specified maintenance patches.

WindowsOn Windows, CDC has the following minimum requirements for DB2, Microsoft SQL Server, and Oracle. For Oracle, you must apply the specified maintenance patches.

Obtaining a License KeyTo run PowerExchange components, you need a license key. The license key is a 64-character string comprised of hexadecimal characters, which are separated by hyphens every four characters, such as:

1234-ABCD-1234-EF01-5678-A9B2-E1E2-E3E4-A5F1-A9B2-1234-E3D4-95F1

Note: Previously, PowerExchange used 44-character license keys. PowerExchange still accepts 44-character keys that have not expired.

Database Minimum Version

DB2 for Linux, UNIX, and Windows

8.1 with FixPack 11

Oracle For 9i: - 9.2.0.6 with patches 4061535 and 4091906- 9.2.0.7

For 10g: - 10.1.0.4 with patches 4061535 and 4091906.- 10.2.0.1 or 10.1.0.5.

Client requirements:- For 11g: 9.2.04 client.- For 11g support for BINARY_FLOAT and BINARY_DOUBLE:10.2.0.1 client

Database Minimum Version

DB2 for Linux, UNIX, and Windows

8.1 with FixPack 11

Microsoft SQL Server

Microsoft SQL Server 2000:

- Enterprise Edition- Standard Edition - Development Edition

You cannot use Personal Edition.

Oracle For 9i: - 9.2.0.6 with patches 4061535 and 4091906- 9.2.0.7

For 10g: - 10.1.0.4 with patches 4061535 and 4091906.- 10.2.0.1 or 10.1.0.5.

Client requirements:- For 11g: 10.2.0.1 client


The license key is not case-sensitive.

License keys are valid for specific time periods. Usually, a license key is linked to an exact or generic TCP/IP address. You can use license keys to control access to certain databases. Do not attempt to install the PowerExchange software until you have a valid license key for all required components.

Warning: You might encounter license key problems if you copy PowerExchange software from another computer, such as from a backup site.

If you do not have a license key or have problems with an existing license key, contact Informatica Global Customer Support.

Using PowerExchange with Earlier Versions of PowerCenter

If you run PowerExchange with a PowerCenter installation of the same version and release, you have complete access to all new PowerExchange functionality. However, you do not have to upgrade both PowerCenter and PowerExchange to the same version at the same time. PowerExchange 8.x tolerates PowerCenter versions earlier than 8.x with the following restrictions:

♦ For the PowerExchange Client for PowerCenter (PWXPC) to provide access to PowerExchange from PowerCenter, you must use PowerCenter 7.1.3 or later. For more information, see the PowerExchange Migration Guide.

Note: On HP-UX systems, you must apply a PowerExchange 8.x hot fix to use PWXPC with the PowerCenter 7.x Server. After you upgrade PowerCenter to 8.x, you must remove this PowerExchange hot fix. Contact Informatica Global Customer Support for assistance.

♦ ODBC access to PowerExchange from PowerCenter is available only with supported releases of PowerCenter.

♦ The PowerCenter Server bin directory must be before the PowerExchange directory in any path and library path environment variables on the PowerCenter Integration Service platform.

♦ The PowerCenter Server bin directory must not be in any path and library path variables that the PowerExchange Listener uses.

♦ You cannot use location “local” when accessing any PowerExchange source or target through PowerCenter. Instead, you must access them through the PowerExchange Listener.

Using Multiple Versions of PowerExchangeInformatica recommends that you install each PowerExchange release in a separate disk area. This practice enables different releases to coexist and prevents a new release from overwriting an existing installation. For example, you might want to install a new release in one area for testing while allowing your production installation to continue to run.

Note: PowerExchange does not allow communication among PowerExchange installations of different versions. For example, the PowerExchange 8.5.x Navigator and Listener communicate only with PowerExchange Listeners of the same version.

Using PowerExchange with Earlier Versions of PowerCenter 13

C H A P T E R 3

Installing PowerExchange on i5/OS


♦ Overview, 15

♦ Installing PowerExchange on i5/OS for the First Time, 15

OverviewInstall PowerExchange on a i5/OS system to extract data from or write data to flat files or DB2 for i5/OS tables on the system. If you have a license for PowerExchange Change Data Capture, you can capture and move change data as well as bulk data.

Installing PowerExchange on i5/OS for the First Time

Before You Begin

Installation RequirementsReview “Preparing to Install PowerExchange” on page 5 before starting the installation process.

Make sure that PowerExchange supports the version and release levels of your operating system and DB2 for i5/OS databases. For more information, see “Release and Maintenance Requirements” on page 5.

User ID RequirementsOptionally, create a user ID for the owner or administrator of the PowerExchange installation. Make sure that the user ID has the sufficient rights and privileges to access source and target data from different locations on the i5/OS platform.

To install the product, you must be logged in with a user profile that has one of the following authorities:

♦ QSECOFR authority

♦ *ALLOBJ and *SECADM authority

15

Disk Space RequirementsVerify that you have sufficient disk space. PowerExchange requires about 60 MB of disk space. Additional disk space might be needed depending on the files and databases being sent and received.

If you run PowerExchange with multibyte data support, you need about 30 MB of additional disk space. Multibyte support is available only for OS/400 V5.1 and later.

License KeyTo install PowerExchange you need a valid license key. Usually, a license key is specific to an IP address. Make sure that a key for the correct host IP address has been requested. For more information, see “Obtaining a License Key” on page 12.

Before you obtain a license key for an IP address, verify that your i5/OS host has a valid IP address. You can use the following procedure.

To verify that the i5/OS host has a valid IP address:

1. Issue the command GO TCPADM.

2. Select Option 1 and press Enter.


The host and domain names for the i5/OS host system appears. Note these names.

4. Issue the command GO TCPADM.


6. Select Option 10.

The IP address that is linked to the host or domain name appears.

This IP address must be associated with the PowerExchange license key. If the IP address is 0.0.0.0, change it before requesting the license key for your IP address. However, you do not need to change this IP address if you are using an evaluation license key, which is not specific to an IP address.

Do not reboot the i5/OS system.

Task Flow for a First-Time InstallationTable 3-1 shows the high-level steps for installing PowerExchange on i5/OS. Use this table as a checklist to track your installation progress.

Table 3-1. PowerExchange Installation Task Flow and Checklist for i5/OS

Step Complete

“Step 1. Create the PowerExchange Libraries” on page 17.

“Step 2. Create a Library Save File for Restores” on page 17.

“Step 3. Transfer the Binary Executable File” on page 17.

“Step 4. Restore the Installation Library” on page 18.

“Step 5. Edit the License Key File” on page 18.

“Step 6. Create the PowerExchange Environment” on page 18.

“Step 7. Change Object Ownership” on page 20.

“Step 8. Create a Relational Database Directory Entry (Optional)” on page 20.

“Step 9. Authorize PowerExchange User Security Settings” on page 20.

“Step 10. Test the Installation” on page 21.

16 Chapter 3: Installing PowerExchange on i5/OS

Install PowerExchangeThe installation instructions include the following variables:

♦ condlib for the library that contains condense files.

♦ datalib for the PowerExchange data library.

♦ dtllib for the PowerExchange software library.

♦ dtlusr for the user ID.

Wherever you see these variables, replace them with the names that you want to use in your installation.

If you plan to run multiple PowerExchange releases, such as for testing and production, ensure that each release is installed in a separate library. This practice allows different releases to coexist and prevents overwriting an existing release with the new release that you are installing.

Step 1. Create the PowerExchange LibrariesCreate the dtllib software library by issuing the following command:

CRTLIB LIB(dtllib) CRTAUT(*CHANGE)

Include CRTAUT(*CHANGE) in the command if it is not the default.

If you plan to use flat or sequential files on the i5/OS system as data sources or targets, also create a data maps library:

CRTLIB stdatamaps

Note: If you specify a different name for your datamaps library, you must specify that name in the DMX_DIR parameter of the DBMOVER configuration file in the datalib library.

If you plan to run PowerExchange within an Independent Auxiliary Storage Pool (IASP), you must issue the following command instead:

CRTLIB LIB(dtllib) CRTAUT(*CHANGE) ASP(*ASPDEV) ASPDEV(youraspdev)

Step 2. Create a Library Save File for RestoresUse the following command to create a library save file that will store the install distribution media for restore operations:

CRTSAVF FILE(library/save_file_name)

This file can be created in any library, for example, qgpl/libres.

If you intend to run PowerExchange with multibyte data support, create a second save file in the library:

CRTSAVF FILE(library/save_ile_name2)

For example, create qgpl/libresicu.

Step 3. Transfer the Binary Executable FileUse FTP to transfer the single, self-extracting executable file for the PowerExchange for i5/OS installation to a Windows system:

pwxnnn_i5os.exe

The nnn variable represents the PowerExchange version and release number. For example, pwx86_i5os.exe is the executable file for the PowerExchange 8.6 installation for i5/OS.

When you extract the executable file, you must specify a temporary target directory on the i5/OS computer to which to unzip the file.

First enter the following commands to start FTP and log in to your i5/OS system:

c:\> ftpftp> open mysystem

Installing PowerExchange on i5/OS for the First Time 17

The mysystem variable is the name of your i5/OS system.

To transfer and extract the executable file, enter the following FTP commands:

ftp> binaryftp> put pwxas4.vnnn library/save_file_nameftp> bye

If you intend to run PowerExchange with multibyte data support, you must include a second PUT command before the bye command:

ftp> put pwxas4.vnnn.icu library/save_file_name2

Step 4. Restore the Installation LibraryUse the following restore command to decompress the library that was transferred:

RSTLIB SAVLIB(DTLVvrm) DEV(*SAVF) SAVF(library/save_file_name) RSTLIB(dtllib) MBROPT(*ALL) ALWOBJDIF(*ALL)

where DTLVvrm is the library that contains the save file and vrm is the version, release, modification level of that library.

After the restore completes, you can delete the save file:

DLTF File(library/save_file)

Multibyte Data

If you intend to run PowerExchange with multibyte data support, you must restore additional objects by entering the following command:

RSTOBJ OBJ(*ALL) SAVLIB(DTLVvrm) DEV(*SAVF) OBJTYPE(*ALL) SAVF(library/save_file_name2) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(dtllib)

After the restore command completes, you can delete the save file for multibyte support by entering the following command:

DLTF FILE(library/save_file_name2)

Independent Auxiliary Storage Pool (IASP)

You can run PowerExchange within an Independent Auxiliary Storage Pool (IASP).

If you want to do so, you must specify the details for the IASP into which you will restore the objects using the RSTASPDEV(youraspdev) parameter. The following example shows the restore syntax with the RSTASPDEV parameter and the additional statements for multibyte data support:

RSTLIB SAVLIB(DTLVvrm) DEV(*SAVF) SAVF(library/save_file_name) MBROPT(*ALL) ALWOBJDIF(*NONE) RSTLIB(dtllib) RSTASPDEV(youraspdev)RSTOBJ OBJ(*ALL) SAVLIB(DTLVvrm) DEV(*SAVF) OBJTYPE(*ALL) SAVF(library/save_file_name2) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(dtllib) RSTASPDEV(youraspdev)

Step 5. Edit the License Key FilePowerExchange requires a license key to run. The license key is usually specific to an IP address.

You must enter the license key in the dtllib/LICENSE(KEY) file. This file must be in the same library as the PowerExchange Listener program dtllst. In the file, update the single record member with your 64-byte license key using a hyphen every four bytes, such as:

1234-ABCD-1234-EF01-5678-A9B2-E1E2-E3E4-A5F1-A9B2-1234-E3D4-95F1

Step 6. Create the PowerExchange EnvironmentCreate a PowerExchange environment that consists of the following libraries:

♦ dtllib. PowerExchange software library.

♦ datalib. Library that contains data files such as the CCT file for capture registrations; PowerExchange configuration parameters; and message queues.


♦ condlib. Library that contains condense files, condense parameters, message queues, and lock files. This library is required only for change data capture processing. PowerExchange deletes files in this library during normal operation. Do not place your own files in this library without contacting Informatica Global Customer Support.

♦ cpxlib. Library that contains extraction maps. This library is required only for change data capture processing.

To create the PowerExchange environment:

1. Issue the following command:

ADDLIBLE dtllib POSITION(*FIRST)

2. If you use change data capture, issue the following command:

CRTPWXENV DESC('user_description') DATALIB(datalib) CONDLIB(condlib) ASPDEV(*NONE) CRTSYSOBJ(*YES) CPXLIB(cpxlib) JRNEXTSEQ(nnnn)

In the JRNEXTSEQ(nnnn) parameter, replace the nnnn variable with a unique four-digit number that is not registered against the exit point QIBM_QJO_DLT_JRNRCV. The minimum value for JRNEXTSEQ is 100 and the maximum value is 9999. To determine the numbers that are currently registered against the exit point, issue the WRKREGINF command and then choose option 8.

If you use bulk data movement only, use the following command:

CRTPWXENV DESC('user_description') DATALIB(datalib) CONDLIB(*NONE) ASPDEV(*NONE) CRTSYSOBJ(*YES)

If you restored dtllib into an IASP, specify the name of the IASP device in the CRTPWXENV command. For example:

CRTPWXENV DESC('user_description') DATALIB(datalib) CONDLIB(*NONE) CRTSYSOBJ(*YES) ASPDEV(youraspdev)

The CRTSYSOBJ parameter creates objects that enable PowerExchange to run in its own subsystem. Table 3-2 identifies these objects:

This default installation is preferable.

Changing the Default Library

Some objects are created by default in the qgpl library. You can move these objects to other libraries.

Note: You might not be able to move objects to an alternative library in an Independent Auxiliary Storage Pool (IASP). i5/OS does not permit certain object types, such as output queues and job queues, to reside in libraries within an IASP.

The following example shows the commands for moving objects to the alternative library yourlib:

ENDSBS SBS(datalib) MOVOBJ OBJ(save_file_library/datalib) OBJTYPE(*OUTQ) TOLIB(yourlib) MOVOBJ OBJ(save_file_library/datalib) OBJTYPE(*JOBQ) TOLIB(yourlib) MOVOBJ OBJ(save_file_library/datalib) OBJTYPE(*SBSD) TOLIB(yourlib) CHGJOBD JOBD(datalib/DTLLIST) JOBQ(yourlib/datalib) OUTQ(yourlib/datalib) RMVJOBQE SBSD(yourlib/datalib) JOBQ(save_file_library/datalib)

Table 3-2. Objects Created by CRTSYSOBJ

Object Type Object Name Library

*CLS DTLLIST datalib

*OUTQ datalib save_file_library

*SBSD datalib save_file_library

*JOBQ datalib save_file_library

*JOBD DTLLIST datalib


ADDJOBQE SBSD(yourlib/datalib) JOBQ(yourlib/datalib) MAXACT(*NOMAX) SEQNBR(1) MAXPTY1(*NOMAX) MAXPTY2(*NOMAX) MAXPTY3(*NOMAX) MAXPTY4(*NOMAX) MAXPTY5(*NOMAX) MAXPTY6(*NOMAX) MAXPTY7(*NOMAX) MAXPTY8(*NOMAX) MAXPTY9(*NOMAX) STRSBS SBSD(yourlib/datalib)

Note: If you specify CRTSYSOBJ(*NO) on the CRTPWXENV command, make sure the subsystem and job queue where you intend to run the PowerExchange Listener can support multiple concurrent jobs. If you are using change data capture, the subsystem and job queue should support a minimum of six concurrent jobs.

Step 7. Change Object OwnershipAll components that were created from the shipped library and that are owned by the user ID used for the installation (pwxusr). You can change this user ID for the dtllib and datalib libraries by issuing the following commands:

call pgm(dtllib/chgallobj) parm('dtllib' 'new_pwxusr')call pgm(dtllib/chgallobj) parm('datalib' 'new_pwxusr')

If PowerExchange Change Data Capture is installed, you can change the user ID for the condlib and cpxlib libraries by issuing the following commands:

call pgm(dtllib/chgallobj) parm('condlib' 'new_pwxusr')call pgm(dtllib/chgallobj) parm('cpxlib' 'new_pwxusr')

Step 8. Create a Relational Database Directory Entry (Optional)Perform this step only if you want to use the DB2400C DB2 Call Level Interface (CLI) access method.

Use the following command to specify that the Relational Database Directory entry or entries with which you want to work:

WRKRDBDIRE

A Relational Database Directory entry can be a local database or a remote database on an i5/OS system on which the PowerExchange Listener running. This command specifies all local and remote entries on the i5/OS system, including *LOCAL.

If a Relational Database Directory entry does not exist, you must create one. The CLI access method requires a Relational Database Directory entry to obtain the name of the database to access.

Step 9. Authorize PowerExchange User Security SettingsIf you want to run the PowerExchange Listener interactively, ensure that the library list for the current job includes the dtllib and datalib libraries before running the commands shown.

If you want the PowerExchange Listener to use the user ID and passwords supplied from the remote platform for security checking, change the first SECURITY parameter in the DBMOVER configuration file to a nonzero value. However, before running jobs, make sure the user ID that was created in Step 1 (dtlusr) has *EXECUTE authority for the following objects:

♦ QSYGETPH

♦ QSYRLSPH

♦ QWTSETP

♦ QCLRPGMI

This can be achieved by entering the following commands:

GRTOBJAUT OBJ(QSYGETPH) OBJTYPE(*PGM) AUT(*EXECUTE) USER(pwxusr)GRTOBJAUT OBJ(QSYRLSPH) OBJTYPE(*PGM) AUT(*EXECUTE) USER(pwxusr)GRTOBJAUT OBJ(QWTSETP) OBJTYPE(*PGM) AUT(*EXECUTE) USER(pwxusr)GRTOBJAUT OBJ(QCLRPGMI) OBJTYPE(*PGM) AUT(*EXECUTE *READ) USER(pwxusr)

Also, the user ID used to run the PowerExchange Listener must have *READ authority for all the user profiles (i.e. remoteid as given in the example below) supplied from the remote platform (e.g. the remote client running PowerExchange Navigator).


This can be achieved with the following command:

GRTOBJAUT OBJ(remote_id) OBJTYPE(*USRPRF) AUT(*READ) USER(pwxusr)

Step 10. Test the InstallationTo verify that the installation was successful, test it using the DTLINFO utility.

To test the installation:

Run the PowerExchange DTLINFO utility, which is located in the PowerExchange LOADLIB library, by entering the following command:

CALL DTLINFO

The following information is displayed for the current PowerExchange installation: version, release and release level, and build date and time. For more information about DTLINFO, see the PowerExchange Utilities Guide.

Where to Go from HereConfigure PowerExchange prior to performing bulk data movement or change data capture. For more information, see the following documents:

♦ For bulk data movement configuration, see the PowerExchange Bulk Data Movement Guide.

♦ For change data capture configuration, see the PowerExchange Change Data Capture Guide for i5/OS.

♦ For DBMOVER configuration file parameters, see the PowerExchange Reference Manual.

Once you have configured PowerExchange, you can start the PowerExchange Listener and, if required, PowerExchange Condense. For more information about starting and stopping PowerExchange tasks, see the PowerExchange Command Reference.


C H A P T E R 4

Installing PowerExchange on Linux and UNIX


♦ Overview, 23

♦ Installing PowerExchange on Linux or UNIX for the First Time, 23

♦ Applying a Service Pack for PowerExchange on Linux or UNIX, 29

OverviewInstall the PowerExchange Linux or UNIX component to extract data from and load data to a file or a supported database on a Linux or UNIX system.

Note: The PowerExchange installation instructions apply to both Linux and UNIX unless otherwise noted.

Installing PowerExchange on Linux or UNIX for the First Time

Before You Begin

General Installation RequirementsReview “Preparing to Install PowerExchange” on page 5 before starting the installation process.

Verify that PowerExchange supports the versions and release levels of your operating system and of the databases to be accessed. See “Release and Maintenance Requirements” on page 5.

Also, get a valid license key. You cannot install PowerExchange until you have a valid key. Usually, a license key is specific to an IP address. Make sure that you get a license key for the correct host IP address. For more information, see “Obtaining a License Key” on page 12.

23

User ID Requirements1. Create a new user ID for the installation to become the owner or administrator of the software.

In the following steps, this user ID is called pwxuser.

2. Using the correct System Administration tool, create the pwxuser user ID.

3. Define a home disk.

4. Grant rights and privileges to pwxuser that are sufficient to access data from different locations on the Linux or UNIX platform.

Disk Space RequirementsThe PowerExchange installation requires about 150 MB of disk space. Other disk space requirements depend on the files and database records being sent and received.

The PowerExchange installation also requires 200 MB of disk space for temporary files. On UNIX, the installer writes the temporary files to the /tmp directory. You can set the TMP or the InstallAnywhere IATEMPDIR environment variable to specify the location of these files.

X Window Server The graphical user interface (GUI) for PowerExchange installation requires a graphics display server to display graphics. Without the graphics display server, the installer generates error messages.

On UNIX, the graphics display server is typically an X Window server. If a X Window server is not installed on the computer where you plan to install PowerExchange using the GUI, you can use an X Window server that is installed on another computer. To do so, redirect the DISPLAY environment variable to the X Window server on the other computer.

To redirect the DISPLAY environment variable to a X Window server on another computer, use one of the following commands:

♦ C shell:

setenv DISPLAY=<TCP/IP node of XWindows server>:0

♦ Bourne/Korn shell:

export DISPLAY="<TCP/IP node of XWindows server>:0"

For example, if you have the X Window server installed on a computer that has a TCP/IP node of 10.1.50.23, use the following commands:

♦ C shell:

setenv DISPLAY 10.1.50.23:0

♦ Bourne/Korn shell:

export DISPLAY="10.1.50.23:0"

If you do not know the IP address of a computer where the X Window server is installed, ask your network administrator. For more information about redirecting the DISPLAY environment variable, see the documentation from the UNIX vendor.

If the X Window server does not support the font that the PowerExchange installer uses, the installer might not display labels on buttons correctly.

Using PowerExchange with Earlier Versions of PowerCenterRunning the same version and release of PowerExchange and PowerCenter is the preferred configuration because this provides complete access to all new functionality. However, it is not necessary to upgrade both PowerCenter and PowerExchange at the same time. PowerExchange tolerates earlier versions of PowerCenter as a migration path. Some restrictions exist when operating in this toleration environment. For more information about these restrictions, see the PowerExchange Migration Guide.

24 Chapter 4: Installing PowerExchange on Linux and UNIX

Task Flow for a First-Time InstallationTable 4-1 shows the high-level steps for installing PowerExchange on Linux or UNIX. Use this table as a checklist to track your installation progress.

Install PowerExchange

Step 1. Transfer the TAR File to the Linux or UNIX SystemPowerExchange provides a single TAR file that contains the appropriate PowerExchange version. The TAR file is located in the software/unix directory of the CD image.The name of the TAR file varies by platform.

Table 4-2 lists, for each platform, the subdirectories that contain the TAR file and the TAR file name and install type:

The variable nnn is the PowerExchange version number.

Table 4-1. PowerExchange Installation Task flow and Checklist for Linux and UNIX

Step Complete

“Step 1. Transfer the TAR File to the Linux or UNIX System” on page 25.

“Step 2. Extract Files from the TAR File” on page 26.

“Step 3. Install PowerExchange” on page 26.

“Step 4. Set Up Path Environment Variables” on page 26.

“Step 5. Set Adabas Environment Variables (Optional)” on page 27.

“Step 6. Set Oracle and DB2 Environment Variables (Optional)” on page 27.

“Step 7. Perform Platform-Specific Tasks for Oracle (Optional)” on page 28.


Table 4-2. Linux and UNIX TAR File Names and Subdirectories

Subdirectory File Name Description

aix pwxnnn_aix32.tar AIX 32-bit

aix pwxnnn_aix64.tar AIX 64-bit

hpux pwxnnn_hpux_parisc32.tar HP/UX PA-RISC 32-bit

hpux pwxnnn_hpux_parisc64.tar HP/UX PA-RISC 64-bit

hpux_itanium pwxnnn_hpux_ipf64.tar HP/UX Itanium 64-bit

linux pwxnnn_linux32_x86.tar RedHat/Suse Linux 32-bit

linux pwxnnn_linux_em64t.tar RedHat/Suse Linux 64-bit

linux pwxnnn_linux_ipf64.tar RedHat/Suse Linux for Itanium 64-bit

linux pwxnnn_zlinux.tar z/Linux 64-bit

solaris pwxnnn_solaris_sp32.tar Sun Solaris 32-bit

solaris pwxnnn_solaris_sp64.tar Sun Solaris 64-bit

solaris pwxnnn_solarisx86_64.tar Sun Solaris x86 64-bit

Installing PowerExchange on Linux or UNIX for the First Time 25

To transfer the TAR file to the Linux or UNIX system:

1. Log in as pwxuser and edit the .profile, as needed, to support the files and databases that will be accessed.

2. Create a temporary directory for this PowerExchange installation, for example:

mkdir pwx_install

3. Make this directory the current working directory:

cd pwx_install

4. Use FTP in BINARY mode to transfer the TAR file to the current working directory.

Step 2. Extract Files from the TAR FileUse the tar command to extract all of the files in the TAR file to a temporary directory. The exact syntax might vary by type of Linux or UNIX platform. However, the following general syntax applies to most platforms:

tar -xvf pwxplatformtype_Vxxx.tar

Step 3. Install PowerExchangeYou can install PowerExchange in console mode from a command prompt or in graphical mode using the PowerExchange installation graphical user interface (GUI). To install PowerExchange in graphical mode, a X Window server must be configured and running. For more information about the X Window System, see the X Window documentation.

To install PowerExchange in console mode:

1. Locate the install.sh file.

2. At the command prompt, enter the following command:

sh install.sh

3. Follow the instructions in the non-graphical version of the installation wizard.

To install PowerExchange in graphical mode:

1. Ensure that the X Window System is running. For more information, see “X Window Server” on page 24.

2. Locate the install.sh file.


sh install.sh -i gui

4. Follow the instructions in the installation wizard GUI.

Step 4. Set Up Path Environment VariablesTo successfully load executable files and shared libraries at run time, edit the path and library path environment variables on the Linux or UNIX system so that they point to the directories where the files and libraries reside.

Also, set the PWX_HOME environment variable so that PowerExchange can locate various run-time components.

Table 4-3 describes the Linux and UNIX environment variables that you need to set:

Table 4-3. Linux and UNIX Environment Variables

Variable Platform Example

PWX_HOME all PWX_HOME=/usr/pwxuser/v851

PATH all PATH=/usr/pwxuser/v851

LIBPATH AIX LIBPATH=/usr/pwxuser/v851

LD_LIBRARY_PATH SUN LD_LIBRARY_PATH=/usr/pwxuser/v851


To verify that the environment variables are correct, log off and log in again.

Step 5. Set Adabas Environment Variables (Optional)For PowerExchange to be able to access Adabas databases on your Linux or UNIX platform, you must update the login profile to include the following environment variables.

export ADAVERS=Adabas _versionexport ADADIR=Adabas_directoryexport ADALNK=Adabas_link_module

For example:

export ADAVERS=v33102export ADADIR=/home/sag/adaexport ADALNK=$ADADIR/$ADAVERS/adalnk.sl

For HP systems, use adalnk.sl instead of adalnk.so. For example:

export ADALNK=$ADADIR/$ADAVERS/adalnk.sl

Step 6. Set Oracle and DB2 Environment Variables (Optional)To use PowerExchange with Oracle and DB2 databases on your Linux or UNIX platform, you must set some environment variables.

Environment Variables for UNIX Code Pages

By default, Linux and UNIX operating systems usually have more than one code page installed and use one of these code pages.

You can change the code page on Linux and UNIX systems by changing the LANG, LC_CTYPE, or LC_ALL environment variable. For example, if you want to find the code page that an HP-UX system uses, you can issue the following command in the C shell to view information about your environment:

LOCALE

The following output is produced:

LANG="C"LC_CTYPE="C"LC_NUMERIC="C"LC_TIME="C"LC_ALL="C"

In this sample output, “C” implies “ASCII.”

If the LOCALE command shows that LANG and LC_ALL are not set, contact your UNIX administrator to determine the correct settings for these environment variables. Also, make sure these environment variables have been exported.

To change the language to English and require the system to use the Latin1 code page, issue the following command:

setenv LANG en_US.iso88591

The locale is changed to Latin1 (ISO 8859-1), as shown in the following sample output:

LANG="en_US.iso88591"LC_CTYPE="en_US.iso88591"LC_NUMERIC="en_US.iso88591"LC_TIME="en_US.iso88591"LC_ALL="en_US.iso88591"

LD_LIBRARY_PATH Linux LD_LIBRARY_PATH=/usr/pwxuser/v851

SHLIB_PATH HP10/11 SHLIB_PATH=/usr/pwxuser/v851

Table 4-3. Linux and UNIX Environment Variables

Variable Platform Example

Installing PowerExchange on Linux or UNIX for the First Time 27

For more information about changing the locale or code page of your UNIX system, see your UNIX documentation.

PM_HOME Environment Variable

If you are installing PowerExchange on a computer that does not have PowerCenter, export the PM_HOME environment variable so that it points to the directory where PowerExchange is installed. However, you do not need to set this environment variable under the following conditions:

♦ The PowerExchange Listener is started from within the PowerExchange directory.

♦ PowerCenter is installed on the same Linux or UNIX server as PowerExchange.

Step 7. Perform Platform-Specific Tasks for Oracle (Optional)You must perform some additional tasks if you are running Oracle on a HP/UX Itanium 64-bit system or a zLinux system.

On a HP-UX Itanium 64-bit system, check the file extension of the libclntsh module. If the file extension is .so, change it to .sl. To change the extension, issue the following command from the PowerExchange directory:

ln -s oracle_path/libclntsh.so libclntsh.sl

Replace oracle_ path with the actual path to the libclntsh module on your system.

On zLinux, preload the libnnz10.so and libclntsh.so libraries by issuing the following export command:

export LD_PRELOAD=$ORACLE_HOME/lib/libnnz10.so:$ORACLE_HOME/lib/libclntsh.so

Step 8. Test the Installation

To test the installation:

Run the PowerExchange DTLINFO utility by entering the following command:

dtlinfo

The following information is displayed for the current PowerExchange installation:

♦ version

♦ release and release level

♦ build date and time.

For more information about DTLINFO, see the PowerExchange Utilities Guide.

Where to Go from HereConfigure PowerExchange prior to performing bulk data movement or change data capture. For configuration information, see the following documents:


♦ For change data capture configuration, see the PowerExchange adapter guides for your data sources.

♦ For dbmover.cfg configuration parameters, see the PowerExchange Reference Manual.

Once you have configured PowerExchange, you can start the PowerExchange Listener and, if required, PowerExchange Condense. For more information about starting and stopping PowerExchange tasks, see the PowerExchange Command Reference.


Applying a Service Pack for PowerExchange on Linux or UNIX

Before You BeginThe Linux or UNIX service pack installation file depends on the installation platform. The following table identifies the service pack file name for each platform:

The variable xxx is the version number and the variable n is the service pack number.

Before installing the service pack, complete the following tasks:

1. Stop all PowerExchange tasks.

2. Back up the PowerExchange installation directory.

Task Flow for a Installing a Service PackTable 4-4 shows the high-level steps for installing a service pack. Use this table as a checklist to track your installation progress.

Install the PowerExchange Service Pack

Step 1. Untar the Service Pack Installation File1. Use FTP to transfer the service pack installation TAR file in BINARY mode to the Linux or UNIX system.

2. Untar the TAR file into the PowerExchange installation directory.

Platform Service Pack File

AIX 32-bit pwxaix_vxxx_spn.tar

AIX 64-bit pwxaix64_vxxx_spn.tar

HP-UX 11 32-bit pwxhp11_vxxx_spn.tar

HP-UX 11 64-bit pwxhp1164_vxxx_spn.tar

Itanium HP-UX 11 64-bit pwxhp11ia64_vxxx_spn.tar

Linux pwxlinux_vxxx_spn.tar

Linux 64-bit pwxlinux64_vxxx_spn.tar

zLinux pwxzlinux_vxxx_spn.tar

Sun Solaris 32-bit pwxsun_vxxx_spn.tar

Sun Solaris 64-bit pwxsun64_vxxx_spn.tar

Sun Solaris Intel 64-bit pwxsunint64_vxxx_spn.tar

Table 4-4. PowerExchange Service Pack Installation Checklist

Step Complete?

“Step 1. Untar the Service Pack Installation File” on page 29.

“Step 2. Copy the License and DBMOVER Configuration Files from the Backup” on page 30.

“Step 4. Resume Access to PowerExchange” on page 30.

Applying a Service Pack for PowerExchange on Linux or UNIX 29

3. If you are installing the service on a HP-UX system, you need to provide executable permissions on the shared libraries. To do so, run the following command from the bin directory where PowerExchange is installed after copying the TAR file to that directory:

chmod 755 *.sl

Step 2. Copy the License and DBMOVER Configuration Files from the BackupCopy the license.key and dbmover.cfg files from the backup to the directory where you applied the service pack.

Step 3. Check the Installation Run the DTLINFO utility to confirm that the current version of PowerExchange matches the version to which the service pack applies. For more information on the DTLINFO utility, see the PowerExchange Utilities Guide.

Step 4. Resume Access to PowerExchangeTo resume access to PowerExchange, restart the PowerExchange tasks for the PowerExchange Listener, PowerExchange Condense, and PowerCenter workflows that extract data from or write data to PowerExchange.


C H A P T E R 5

Installing PowerExchange on MVS


♦ Overview, 31

♦ Installing PowerExchange on MVS for the First Time, 32

♦ Upgrading PowerExchange on MVS to a New Release, 51

♦ Installing a Service Pack for PowerExchange on MVS, 66

OverviewThis chapter provides instructions for the installing PowerExchange on MVS, including instructions for a first-time installation, an upgrade, and a service pack installation.

Note: If you are upgrading from PowerExchange 5.2.1 or earlier, you must perform the procedure to install PowerExchange for the first time.

To install, upgrade, or apply a service pack, run the MVS Installation Assistant and then complete the subsequent steps to install the PowerExchange components.

Understanding MVS SecurityPowerExchange requires access to MVS databases and files that are typically protected by security products like RACF, CA ACF2, and CA Top Secret. Use a specific user ID for the PowerExchange administrator. The PowerExchange administrator defines the libraries, runs the installation jobs, customizes data sources, and authorizes libraries.

For more information about PowerExchange security options and the SECURITY statement in the DBMOVER configuration member, see the PowerExchange Reference Manual.

Error MessagesPowerExchange error messages contain a lot of information about the causes of installation failures. The most common causes of failure after installing PowerExchange initially are incorrect IP address and port number values in the NODE and the LISTENER statements of the DBMOVER configuration member.

31

Installing PowerExchange on MVS for the First TimeRun the MVS Installation Assistant to tailor PowerExchange parameters and data set names. The MVS Installation Assistant transmits the MVS data sets to the MVS system. To complete the installation, you then submit a series of jobs on the MVS system.

Before You Begin

Installation RequirementsVerify that your system meets installation requirements. For more information, see “Preparing to Install PowerExchange” on page 5.

License KeyTo start PowerExchange, you need a valid license key. A license key is usually associated with a specific IP address. Verify that a license key for the correct host IP address has been requested. For more information, see “Obtaining a License Key” on page 12.

Task Flow for a First-Time InstallationTable 5-1 lists the high-level steps that you need to perform to install PowerExchange. These steps are grouped into the following phases:

♦ Phase I: Install the PowerExchange base software. Required for all PowerExchange users.

♦ Phase II: Install the PowerExchange Change Data Capture software. Required for users who purchased the CDC option.

♦ Phase III: Install PowerExchange software for specific data sources. Required for users of the data sources.

Use this table as a checklist to track your installation progress.

Table 5-1. PowerExchange Installation Task Flow and Checklist for MVS

Step Complete

Phase I: Install PowerExchange Base Software

“Step 1. Allocate the BINLIB and RUNLIB Libraries” on page 35. gggg

“Step 2. Prepare the MVS Components on Windows” on page 36.

“Step 3. Run the MVS Installation Assistant for a Full Install” on page 36.

“Step 4. Edit the JOBCARD Member in RUNLIB” on page 47.

“Step 5. Submit the SETUPBLK Job” on page 47.

“Step 6. Add the PowerExchange Load Library to the APF List” on page 48.

Phase II: Install PowerExchange Change Data Capture Software

“Step 7. Submit Change Data Capture Jobs” on page 48.

“Step 8. Copy the PowerExchange Agent Procedure” on page 49.

“Step 9. Add the PowerExchange Load Libraries to the APF List” on page 49.

“Step 10. Start the PowerExchange Agent” on page 49.

“Step 11. Submit the SETUPCC2 Job” on page 49.

Phase III: Install PowerExchange Software for Specific Data Sources

“Step 12. Install Software for Adabas CDC” on page 50.

32 Chapter 5: Installing PowerExchange on MVS

Space Requirements for PowerExchange Data SetsPowerExchange installation creates a number of MVS data sets for both bulk data movement and change data capture when you run the installation jobs on MVS. These data sets contain JCL, examples, messages, load modules, and operational data.

Table 5-2 describes the data sets that are allocated during the PowerExchange base software installation process. If you intend to use PowerExchange Change Data Capture, the installation creates additional data sets, which are described in Table 5-3 on page 34.

“Step 13. Install Software for DB2 Data Sources” on page 50.

“Step 14. Install Software for IDMS Data Sources” on page 50.

Table 5-2. Data Sets Allocated for PowerExchange Bulk Data Movement

Data Set DescriptionSpace Units (3390)

Space Quantity(pri,sec)

Directory Blocks

DCB Characteristics

DATAMAPS VSAM data set that contains PowerExchange data maps.

TRK (15,15) VSAM

DBRMLIB PDS that contains PowerExchange DB2 DBRMs for bulk and change data capture.

TRK (10,10) 10 RECFM FB

LRECL 80

BLKSIZE 27920

DTLDATA PDS that contains demo data for the demos in DTLDEMO.

CYL (5,5) 10 RECFM FB

LRECL 80

BLKSIZE 27920

DTLDEMO PDS that contains demo JCL. CYL (5,5) 5 RECFM FB

LRECL 80

BLKSIZE 27920

DTLEXPL PDS that contains sample JCL for maintenance activities, fault resolution, and PowerExchange utilities.

The AAYINDEX member describes each member in DTLEXPL.


LRECL 80

BLKSIZE 27920

DTLLOG Sequential data set that can be used as the PowerExchange Listener message log.

Alternative PowerExchange logging can also be used. For more information, see the PowerExchange Reference Manual.

CYL (5,5) 0 RECFM VB

LRECL 1024

BLKSIZE 23476

DTLMSG Sequential data set that contains PowerExchange messages.

TRK (5,15) 0 RECFM VB

LRECL 1024

BLKSIZE 23476

Table 5-1. PowerExchange Installation Task Flow and Checklist for MVS

Step Complete

Installing PowerExchange on MVS for the First Time 33

Table 5-3 describes the data sets that the PowerExchange installation allocates for change data capture:

LOADLIB Load library that contains PowerExchange load modules required for bulk access, as well as some of the change data capture load modules.

CYL (45,10) 60 RECFM 0

LRECL U

BLKSIZE 23476

PROCLIB PDS that contains the PowerExchange started task procedures.


LRECL 80

BLKSIZE 27920

SRCLIB PDS that contains code samples and sample exits.


LRECL 80

BLKSIZE 27920

Table 5-3. Data Sets Allocated for PowerExchange Change Data Capture



Directory Blocks

DCB Characteristics

CCT VSAM data set that contains capture registrations.

TRK (15,15) VSAM

CDCT VSAM data set that contains PowerExchange Condense information.

TRK (15,15) VSAM

CDEP VSAM data set that contains capture extraction history information.

TRK (15,15) VSAM

CRG.LOAD Load library that contains load modules for IMS synchronous change data capture.

CYL (15,15) 90 RECFM U

LRECL 0

BLKSIZE 23440

DBRM Temporary load library that contains DB2 DBRM modules for DB2 change data capture. Contents are copied to DBRMLIB during installation.


LRECL 80

BLKSIZE 27920

DTLCAMAP VSAM data set that contains extraction maps.

TRK (15,15) VSAM

ERDS01 VSAM data set used by the PowerExchange Logger as an emergency restart data set.

TRK (30,0) VSAM

ERDS02 VSAM data set used by the PowerExchange Logger as an emergency restart data set.

TRK (30,0) VSAM

Table 5-2. Data Sets Allocated for PowerExchange Bulk Data Movement



Directory Blocks

DCB Characteristics


Phase I: Install the PowerExchange Base SoftwareComplete the following steps to install the PowerExchange base software.

Step 1. Allocate the BINLIB and RUNLIB LibrariesYou must preallocate two libraries to receive data from the installation. Use the predefined library suffixes of BINLIB and RUNLIB and any prefix you choose. Installation jobs allocate additional data sets during the installation process.

To allocate the BINLIB and RUNLIB libraries:

On the MVS system, use ISPF Option 3.2 to allocate the BINLIB and RUNLIB libraries. You can also use JCL to allocate the libraries.

Tip: When allocating these libraries, note the high-level qualifier (HLQ) that you use. You will need to enter this high-level qualifier on the Select Dataset Names page of the MVS Installation Assistant in step 5 on page 37.

LOAD Load library that contains load modules for PowerExchange change data capture.

CYL (75,15) 100 RECFM 0

LRECL 100

BLKSIZE U

PRILOG.DS01 VSAM data sets used by the PowerExchange Logger as primary active log data sets.

CYL (15,0) VSAM

PRILOG.DS02 CYL (15,0) VSAM

PRILOG.DS03 CYL (15,0) VSAM

SAMPLIB PDS that contains sample JCL and parameters for PowerExchange change data capture.


LRECL 80

BLKSIZE 27920

SECLOG.DS01 VSAM data sets used by the PowerExchange Logger as secondary active log data sets.

CYL (15,0) VSAM

SECLOG.DS02 CYL (15,0) VSAM

SECLOG.DS03 CYL (15,0) VSAM

SRT2TOTAL Sequential data set that contains IDMS change data capture information.


LRECL 80

BLKSIZE 23476

SR2OUT Sequential data set that contains IDMS change data capture information.


LRECL 80

BLKSIZE 23476

USERLIB Load library that contains control parameters for PowerExchange change data capture.

TRK (5,15) 45 RECFM U

LRECL 0

BLKSIZE 23440

Table 5-3. Data Sets Allocated for PowerExchange Change Data Capture



Directory Blocks

DCB Characteristics


Table 5-4 describes the BINLIB and RUNLIB libraries and the parameters for allocating them:

Step 2. Prepare the MVS Components on WindowsPowerExchange for MVS is shipped as a self-extracting executable.

To prepare the MVS components on Windows:

1. From a Windows command prompt, make a temporary directory into which the MVS components are to be extracted. For example:

mkdir pwx_mvs

2. Find and run the product installation executable for MVS that has the following name:

pwxnnn_zos.exe

The nnn variable is the PowerExchange version number. For example, pwx86_zos.exe is the name of the executable for the PowerExchange 8.6 MVS installation.

3. The WinZip Self-Extractor prompts you for a directory to which to unzip the files. Browse to the directory that you created in step 1. Then click Unzip.

The WinZip Self-Extractor places several files in the root directory and creates the following subdirectories that also contain files:

♦ binary

♦ runlib

4. Click OK.

5. On the WinZip Self-Extractor dialog box, click Close.

Step 3. Run the MVS Installation Assistant for a Full InstallUse the MVS Installation Assistant wizard to complete the following tasks:

♦ Set the variables for your MVS installation and submit them through a single process.

♦ Move the software library binary files to the BINLIB library on the MVS system.

♦ Move customized run-time library members to the RUNLIB library on the MVS system.

After running the MVS Installation Assistant, you must submit at least the SETUPBLK job manually. The other necessary jobs will be submitted automatically if you select the Auto Submit On option in the wizard.

Table 5-4. BINLIB and RUNLIB Allocation

Library DescriptionSpace Units (3390)


Directory Blocks

DCB Characteristics

BINLIB PDS that contains the software libraries in TSO/E transmitted format.


LRECL 80

BLKSIZE Any valid value

RUNLIB PDS that contains the jobs to install PowerExchange, jobs to set up and run PowerExchange, and configuration data.

The AAINDEX member describes each member in RUNLIB.


LRECL 80



To run the MVS Installation Assistant:

1. From the pwx_mvs directory, double-click MVS_Install.exe.

2. A default InstParm file is shipped with PowerExchange. If the InstParm file does not exist, you are prompted to create it with default values. Click OK.

The MVS Installation Assistant wizard will update the InstParm file with the customization values that you specify in the wizard. Keep the customized InstParm file that is created during the full install so that you can use it when upgrading PowerExchange or applying service packs.

3. On the MVS Installation Assistant, select Full Install and click Next.

Tip: On any page in the MVS Installation Assistant, click Save to save your installation selections to the InstParm file.

4. On the Full Install page, click Next.

5. On the Select Dataset Names page, enter the following information and then click Next:

Property Description

Logon ID MVS user ID that enables connection to the MVS system.

PowerExchange Agent / Logger Prefix

Prefix for the PowerExchange Agent and PowerExchange Logger. The MVS Installation Assistant appends the following characters to the prefix:- A for the PowerExchange Agent- L for the PowerExchange Logger

Default is PWX.Maximum length is three characters.

High-Level Qualifiers

Default HLQ Default high-level qualifier (HLQ). To change the default HLQ, you must select the Use Defaults check box. You can use as many qualifier levels as required. For example, the following are both valid HLQs:- PWX.SYSTEMA.PROD- SYS3.SYSA.PWX.TEST.A1

Default is PWX. Maximum length is 26 characters, including periods.

Use Defaults Select this check box to use the default HLQ for the PowerExchange data sets. Clear this check box to specify other HLQs in the following fields:- Seq \ Install Library- VSAM- Archive

Seq \ Install Library HLQ for the PowerExchange non-VSAM libraries. The non-VSAM data sets for the PowerExchange products include the PowerExchange load libraries. To change this HLQ, you must clear the Use Defaults check box.

Default is PWX.Maximum length is 26 characters, including periods.

VSAM HLQ for the PowerExchange VSAM data sets. To change this HLQ, you must clear the Use Defaults check box.

Default is PWX.V1.Maximum length is 23 characters, including periods.

Archive Prefix for the PowerExchange Logger archive log data sets. To change the Archive prefix, you must clear the Use Defaults check box.

Default is PWX.V2.Maximum length is 17 characters, including periods.

License Key License key for your installation.For more information, see “Obtaining a License Key” on page 12.


6. On the Select Dataset Volume \ Unit page, enter the following information and then click Next:

7. On the Select Data Sources page, select the data sources that will be used for bulk data movement and for change data capture. You must select a data source to be able to select the Capture option for that data source.

Your selections determine which pages subsequently appear in the MVS Installation Assistant. Click Next to continue.


Default Volume Volume serial number (VOLSER) of the DASD volume on the MVS system on which you want to install the PowerExchange libraries. To change this property, clear the Use Defaults check box.

Default Unit A generic or esoteric unit name on the MVS system on which you want to install PowerExchange. To change this property, clear the Use Defaults check box.

Use Defaults Select this check box to use the values in the Default Volume and Default Unit fields for PowerExchange data sets. Clear this check box to specify other volumes and units in the subsequent fields.

Permanent DataSet Options

Volume (Seq) A valid VOLSER for the PowerExchange non-VSAM data sets.

Volume (VSAM) A valid VOLSER for the PowerExchange VSAM data sets or an asterisk (*) if you are using SMS.

Unit (Seq) A generic or esoteric unit name for the non-VSAM data set VOLSER that you specified.

Unit (Archive) A generic or esoteric unit name for the PowerExchange Logger archive log data sets. Informatica Corporation recommends that you write the archive log data sets to DASD.

Note: This parameter is one of many PowerExchange Logger EDMUPARM parameters that control archive logging. For more information about EDMUPARM parameters, see the PowerExchange Change Data Capture Guide for z/OS.

Storage Class for Seq, VSAM, and Archive

SMS storage classes for PowerExchange data sets. These fields are relevant only if you use SMS. If you specify an SMS storage class, you do not need to specify any Volume or Unit values. Note: The SMS ACS routines in your installation might not allow specification of SMS classes or might override the values that you specify.

Mgmt. Class for Seq, VSAM, and Archive

SMS management classes for PowerExchange data sets. These fields are relevant only if you use SMS.Note: The SMS ACS routines in your installation might not allow specification of SMS classes or might override the values that you specify.

Data Class for Seq, VSAM, and Archive

SMS data classes for PowerExchange data sets. These fields are relevant only if you use SMS.Note: The SMS ACS routines in your installation might not allow specification of SMS classes or might override the values that you specify.

PowerExchange Condense Parameters

Check Point Volumes

VOLSERs for the checkpoint data sets, which map to the CHKPT_VOLSERS statement in the PowerExchange Condense configuration file.

Volume VOLSER for full condense files, which maps to the CONDF_VOL statement in the PowerExchange Condense configuration file.

Unit Unit for full condense files, which maps to the CONDF_UNIT statement in the PowerExchange Condense configuration file.


Use the following table to navigate to the steps for the data sources that you selected:

8. If you selected a capture data source on the Select Data Sources page, the Select CDC Common Parameters page appears. Enter the following information and then click Next:

Data Source Step Number Page

Change data capture common. Required if you select any CDC data sources.

step 8 page 39

Adabas step 9 page 40

Datacom step 10 page 41

DB2 bulk data movement step 11 page 41

DB2 change data capture step 12 page 42

IDMS bulk data movement step 13 page 43

IDMS change data capture step 14 page 43

IMS bulk data movement step 15 page 44

IMS change data capture step 16 page 44

MQ Series step 17 page 45

VSAM step 18 page 45


PowerExchange Agent / Logger Options

Logger ID (LOGGER) PowerExchange Logger ID value. This value must comply with the following rules:- Be one to four characters in length- Begin with an alphabetic character or a #, @, or $ character- Be composed of alphanumeric characters and the #, @, and $ characters

The Logger ID value maps to the LOGGER_NAME parameter in the PowerExchange Logger EDMUPARM options module and to the LOGGER parameter in the PowerExchange Agent EDMSDIR options module. For more information about the EDMUPARM and EDMSDIR parameters, see the PowerExchange Change Data Capture Guide for z/OS.Default is PWXL.

LOGGER Started Task ID (LLGNAME)

Name for the PowerExchange Logger started task. This name can be the same as or different from the Logger ID value.Default is PWXL.

Agent Name (AgentID)

PowerExchange Agent ID value. This value must comply with the following rules:- Be four characters in length- Begin with an alphabetic character or a #, @, or $ character- Be composed of alphanumeric characters and the #, @, and $ characters- Be different from any existing MVS subsystem nameYou can use the same Agent ID value for multiple PowerExchange Agents provided each PowerExchange Agent runs on a separate MVS system.

The Agent Name value maps to the AgentID option in the PowerExchange Agent AGENTCTL member and to the AGENTID parameter in the EDMSDIR options module. For more information about the AGENTCTL and EDMSDIR parameters, see the PowerExchange Change Data Capture Guide for z/OS.Default is PWXA.

Agent Started Task ID (STARTID)

Name for the PowerExchange Agent started task proc. This name can be the same as or different from the Agent Name. Default is PWXA.


9. If you selected Adabas as a data source, the Select ADABAS Parameters page appears. Enter the following information and then click Next:

Logger DataSet Size (in Cylinders)

Number of cylinders to allocate for the PowerExchange Logger primary log, the secondary log, and the primary space for the archive log data sets.

If the active log data set is larger than permitted by the DSPSERV CREATE function, the Log Format utility (EDMLUTL0) issues the error message:PWXEDM172782E ACTIVE LOG DATASET IS TOO LARGE.

Maximum size is 2912 cylinders (3390 device) or 3495 cylinders (3380 device).

Change Capture Error (CCERR)

Action that PowerExchange takes when a DB2, IMS synchronous, batch VSAM, or CICS/VSAM ECCR is unable to capture changes for a source. Valid values are: - Continue. Stop change capture but allow the job or transaction to continue.

Changes to the source are not captured. - Abend. Cause the job or transaction to terminate abnormally. Transactions

cannot update the source.Change Capture Error maps to the CCERR parameter in the EDMSDIR options module. For more information about the EDMSDIR options, see the PowerExchange Change Data Capture Guide for z/OS.

Post-Log Merge Options

Use Post -Log Merge Option that enables or disables the PowerExchange Logger Post-Log Merge environment. If you select this option, complete the fields:- Suffix- TIME_CHKPT_FREQ- TIMER_INTERVALFor more information about configuring Post-Log Merge, see the PowerExchange Change Data Capture Guide for z/OS.

Suffix A unique suffix for a PowerExchange Logger member in a Post-Log Merge group. This value is a single numeric character.

The suffix is used as in the data set name for USERLIB and in the XCF members created by the PowerExchange Logger.

Minimum value is 1. Maximum value is 9.

TIME_CHKPT_FREQ (5-60)

How frequently the PowerExchange Logger creates time-based checkpoint records in a Post-Log Merge environment. This value is the number of TIMER_INTERVAL periods.

Minimum value is 5. Maximum value is 60.Default is 100.

TIMER_INTERVAL (50-6000)

How frequently the PowerExchange Logger performs internal management operations, such as freeing unused virtual storage or detecting inactive tasks that need to be reactivated. This value is specified in hundredths of seconds.

Minimum value is 50 (.5 seconds). Maximum is 6000 (1 minute).


ADABAS Check box that controls whether you use Adabas as a data source. Clear this check box to not use Adabas as a data source.

ADABAS Capture Check box that controls whether you use Adabas as a data source for change data capture. Clear this option to not use Adabas as a data source for change data capture.

Load Library Name of the Adabas load library.

Database ID The Adabas DBID.



10. If you selected Datacom as a data source, the Select Datacom Parameters page appears. Enter the following information and then click Next:

11. If you selected DB2 as a data source, the Select DB2 Parameters page appears. Enter the following information and then click Next:

OUSP Check box that controls if security is used for an Adabas data source. With OUSP and PowerExchange security enabled, PowerExchange creates a UNIX User Security Packet (USP) for Adabas users, which allows Adabas to verify user security access.

Change Data Capture Information

Associator Associator data set that corresponds to the database ID. To edit this property, select the Adabas Capture check box.

Work Work data set that corresponds to the given database ID. To edit this property, select the Adabas Capture check box.

DataStorage Data storage data set that corresponds to the given database ID. To edit this property, select the Adabas Capture check box.

Unit Adabas unit name for the specified database ID. PowerExchange uses this value in the ADARUN card.


Datacom Check box that controls whether Datacom is used as a data source. Clear this check box to not use Datacom as a data source.

Datacom Change Data Capture

Check box that controls whether Datacom is used as a data source for change data capture. Clear this check box to not use Datacom as a data source for change data capture.

Load Library Data set name of the Datacom load library.

Customized Load Data set name of the Datacom customized load library.

Service Pack Library Data set name of the Datacom service pack library, if one exists.

IPC Library Data set name of the Inter-Product Components (IPC) library. This library is a collection of common routines, similar in nature to the CA90s or TNG framework. It allows the product to be insulated from the environment to facilitate speed of development.

CA90 / TNG Library Data set name of the CA90s or the TNG library.

CXX Directory Data set name of the Datacom CXX Communication library.

Change Data Capture Information

Registration Location Location of the PowerExchange Listener where the capture registrations reside. The location must be identified in a NODE statement of the DBMOVER configuration file that is specified in the Datacom Change Controller address space.

Datacom MUF Name Name of the Datacom Multi-User Facility (MUF).


DB2 Check box that controls whether DB2 is used as a data source. Clear this check box to not use DB2 as a data source.

DB2 V8+ New Function Mode Select this option if one of the following conditions are true:- The DB2 subsystem is running V8 in New Function Mode. - The DB2 subsystem version is later than version 8.

DB2 Subsystem ID DB2 subsystem ID (SSID) or data-sharing group name that contains the source DB2 tables.



12. If you selected DB2 Capture, the Select DB2 CDC Parameters page appears. Enter the following information and then click Next:

Load Library Data set name of the DB2 SDSNLOAD load library. This value is optional if the MVS LNKLST concatenation includes the DB2 load library.

DB2 Exit Library Data set name of the DB2 SDSNEXIT load library. This value is optional if the MVS LNKLST concatenation includes the DB2 exit library.

Bulk Plan Name DB2 plan name fro PowerExchange bulk data movement. Default is PWXBKV85.

Creator Name for All Objects Creator name for DB2 objects that PowerExchange creates during the installation process.Default is the Logon ID value.

DSNTEP2

DB2 Runlib Data set name of the load library that contains the DSNTEP2 program. PowerExchange uses the DSNTEP2 program to run DB2 commands.Default is DSN710.RUNLIB.LOAD.

Name DSNTEP2 program name.Default is DSNTEP2.

Plan DSNTEP2 plan name.Default is DSNTEP71.


DB2 Capture Check box that controls whether DB2 is used as a data source for change data capture. Clear this check box to not use DB2 as a data source.

Change Data Capture Plan DB2 ECCR plan name.Default is PWXCPV85.

Change Data Capture Package Name

Collection ID that is used for the DB2 ECCR packages.Default is PWXCPV85.

Change Data Capture Database Name

Name of the DB2 database to contain the DB2 ECCR capture directory tables.Default is PWXCCDDB.

STOGROUP DB2 STOGROUP for the DB2 ECCR capture directory tables, table spaces, and indexes. You can choose an existing STOGROUP name. If you do not specify a STOGROUP, the DB2 defaults apply.

Change Data Capture Owner Name

Creator name for all DB2 ECCR objects that PowerExchange creates during the installation process.

TCAPWORK Bufferpool Name Name of the DB2 buffer pool to be used for the DB2 ECCR TCAPWORK table space. This buffer pool must be at least 16 KB in size. You can enter one of the following names for it: 16KB: BP16K0, BP16K1, BP16K2, ..., BP16K932KB: BP32K, BP32K1, BP32K2, ..., BP32K9Default name is BP16K0.

CA Name Name of the DB2 ECCR, which is used to identify the DB2 ECCR to the PowerExchange Logger. This value is set in the CA NAME statement in the REPDB2CT member of the RUNLIB library.This value must be unique within a sysplex because the DB2 ECCR uses this name to request a global resource lock.



13. If you selected IDMS as a data source, the Select IDMS Parameters page appears. Enter the following information and then click Next:

14. If you selected IDMS Change Capture, the Select IDMS CDC Parameters page appears. Enter the following information and then click Next:


IDMS Check box that controls whether IDMS is used as a data source. Clear the check box to not use IDMS as a data source.

Primary Library Data set name of the primary IDMS library.

DBA Library Data set name of the IDMS DBA library.

SYSCTL Library Data set name of the IDMS SYSCTL library.

3rd Party Library Data set name of the IDMS third party library.

DMCL Member Data set name of the IDMS DMCL member.

Mode If you selected IDMS but not IDMS Capture on the Select Data Sources and Targets page, the following Mode options are available: - Central: Use centrally defined databases and the SYSCTL data set.- Local: Use the IDMS dictionary and database file entries that you

specify in the IDMSDICT and IDMSFILE members of the PowerExchange RUNLIB library. This information overrides the data in SYSCTL data set (CV mode).


IDMS Change Data Capture Check box that controls whether IDMS is used as a data source. Clear this check box to not use IDMS as a data source.

IDMS Capture Type The type of IDMS change data capture environment to install:- Synchronous- Log-based

IDMS CV Name IDMS Central Version (CV) name.

IDMS Synchronous

IDMS Version >= 15 This option is selected if you selected Synchronous for the IDMS Capture Type. You must select this option if you have IDMS version 15 or later.

Registration Location This field is available if you selected Synchronous for the IDMS Capture Type. Enter the location of the PowerExchange Listener where the capture registrations reside. This location must be identified in a NODE statement of the DBMOVER configuration file that is specified in the IDMS Change Controller address space.

IDMS Log-Based

Log Location This property is always set to LOCAL. The location specifies where the IDMS log files are stored. This value must be specified in the NODE statement of the PowerExchange DBMOVER configuration file on the MVS system. This value also corresponds to the second parameter (listener_node) in the LOGSID statement in the DBMOVER configuration file.For more information on LOGSID, see thePowerExchange Change Data Capture Guide for z/OS and PowerExchange Reference Manual.


15. If you selected IMS as a data source, the Select IMS Parameters page appears. Enter the following information and then click Next:

16. If you selected IMS Log Based Capture or IMS Synchronous Data Capture, the Select IMS CDC Parameters page appears. Enter the following information and then click Next:

LOGSID This field is available if you selected Log-Based for the IDMS Capture Type. Enter the name of the IDMS LOGSID. This name corresponds to the first parameter (registration_logsid) in the LOGSID statement in the DBMOVER configuration file. For more information on LOGSID, see thePowerExchange Change Data Capture Guide for z/OS and PowerExchange Reference Manual

Media Type This field is available if you selected Log-Based for the IDMS Capture Type. Specify whether the IDMS logs reside on tape or disk.


IMS Select this check box to use IMS as a data source. Clear this check box to not use IMS as a data source.

IMS Region IMS ID for the IMS region.

PSB Member Data set name of the PSB member.

Procedure Library Data set name of the IMS procedure library that contains the DLIBATCH PROC.

PSB Library Data set name of the PSB library that is specified in the IMS NETPORT statement of the DBMOVER configuration file. This name is used to customize the IMS JCL members in the RUNLIB library.

RESLIB Data set name of the IMS SDFSRESL library. This name is used to customize the IMS JCL members in the RUNLIB library.

DBD Library Data set name of the DBD library. This name is used to customize the IMS JCL members in the RUNLIB library.

Access via ODBA Select this option to enable access to IMS data through the Open Database Access (ODBA) method. Clear this option to not use ODBA.


IMS Log-Based Capture Check box that controls whether IMS is used as a data source for log-based change data capture. Clear this check box to not use IMS log-based change data capture.

IMS Synchronous Capture Check box that controls whether IMS is used as a data source for synchronous change data capture. Clear this check box to not use IMS synchronous change data capture.

IMS Version Version of the installed IMS system.

IMS RECON Datasets IMS Database Recovery Control (DBRC) RECON data sets for IMS log-based change data capture.

IMS Synchronous ECCR DFSESL Datasets

Data sets that will be concatenated to existing DFSESL DD statements in your IMS dependent region or IMS control region when IMS synchronous change data capture is used.You can enter up to five data sets.

Note: These data sets are for IMS synchronous change data capture only and are placed in the ESLLIB parameter of the EDMSDIR options module. For more information about these data sets, see the PowerExchange Change Data Capture Guide for z/OS.



17. If you selected MQ Series Access as a data source, the Select MQ Series Parameters page appears. Enter the following information and then click Next:

18. If you selected VSAM as a data source, the Select VSAM Parameters page appears. Enter the following information and then click Next:

19. On the Select Additional Parameters page, enter the following information and then click Next:


MQ Series Access Check box that controls whether IBM Websphere MQ is used as a data source or target. Select this check box if you want to use Websphere MQ as a source or target.

MQ Load Library 1 Data set name of the SCSQLOAD MQ load library that provides connectivity to Websphere MQ.

MQ Load Library 2 Data set name of the SCSQANLE MQ load library that provides connectivity to Websphere MQ.

MQ Load Library 3 Data set name of the SCSQAUTH MQ load library that provides connectivity to Websphere MQ.

Option Description

VSAM Select this heck box to use VSAM as a data source for bulk data movement.

Batch Change Data Capture Select this check box if you are installing batch VSAM change data capture.

CICS Change Data Capture Select this check box if you are installing CICS/VSAM change data capture.


LE Run Library Data set name of the LE run library.Default is SYS1.SCEERUN.

Delete Install Members Check box for running the XIZZZ999 job. This job deletes members that have been moved from the RUNLIB library to other libraries by the XIZZZ998 job. If you clear this option, these members remain in the RUNLIB library.

Auto Submit On Check box for automatically submitting the PowerExchange installation jobs. - Select this check box to have the setup process submit installation

jobs automatically after you submit the initial job. Specify TYPRUN=HOLD in the JOB card that you set up in “Step 4. Edit the JOBCARD Member in RUNLIB” on page 47. All jobs should end with a return code less than 4.

- Clear this check box if you want to manually submit the jobs.

Informatica recommends that you manually submit the installation jobs. Manual submission allows you to verify that the jobs run in the correct order and on the correct system.

Change Listener Port Option for installing the PowerExchange Listener on a port other than the default port. If you select this option, you must enter a port number.

Use Tape / GDG Netport Option for using a Netport job. Netport jobs are often used in conjunction with long-running tasks such as tape storage or IMS tasks.If you select this option, enter the port on which Netport will listen and the name of the Netport job. To specify more than one Netport job, manually edit the DBMOVER configuration member of the RUNLIB library.

CDC Netport

IMS Netport


Warning: Do not select Auto Submit On if you are installing PowerExchange for DB2 or PowerExchange Change Data Capture. During PowerExchange installation, you must run a job to BIND DB2 plans. If you do not have the appropriate DB2 authority, the BIND job fails. The installation of PowerExchange Change Data Capture components requires manual intervention between the execution of various installation jobs.

20. On the Create Runlib JCL page, enter the following information and then click Next:

The MVS Installation Assistant creates the XRunlib folder. The XRunlib folder contains the files from the runlib folder, which are customized with the values you entered in the installation wizard.

21. On the FTP to Mainframe page, enter the following information and then click Next:

22. The Check FTP Status page appears, which displays the status of the FTP transfer operation. After the FTP transfer completes, click OK.

23. Click Finish.

The MVS Installation Assistant saves your installation selections to the InstParm file.

ICU Option for enabling the following fields for ICU installation:- USS directory where the tar file programs will be unpacked- USS directory where the ICU CNV files will be located

USS directory where the tar file programs should be unpacked to

USS directory where the ICU installation tar files are copied and unpacked.

USS directory where the ICU CNV files will be located

USS directory where the ICU CNV files are to be located. This option sets the ICUDATADIR parameter in the PowerExchange DBMOVER configuration file.


Runlib Fully-qualified name of the RUNLIB library to which the install JCL is transferred. The install JCL is customized to use this name. Note: You must preallocate this library.

Binary Fully-qualified name of the BINLIB library to which the modules and load libraries are transferred. The install JCL is customized to use this name. Note: You must preallocate this library.


IP Address / Node IP address of the MVS system on which you want to install PowerExchange.

Mixed Case Password Option for using a mixed-case password.If you clear this option, the password is changed to uppercase.

Logon ID Logon user ID that is used to connect to the MVS system.

Password Password that is used to connect to the MVS system.

Notify upon FTP Connection Option that controls whether a pop-up notification window is displayed when the FTP transfer completes. Select this option to receive notification.

Runlib Select this option to use FTP to transfer the contents of XRunlib folder to the RUNLIB library that you specify.

Binary Select this option to use FTP to transfer the contents of XRunlib folder to the BINLIB library that you specify.



Step 4. Edit the JOBCARD Member in RUNLIB

To edit the JOBCARD member:

1. Edit the JOBCARD member in the RUNLIB library to make any necessary changes, such as to the CLASS or MSGCLASS parameters.

2. If you selected Auto Submit On on the Select Additional Parameters page, add TYPRUN=HOLD to the JOBCARD member to control the execution of the jobs. You must release each job manually.

Step 5. Submit the SETUPBLK JobThe SETUPBLK job completes the installation of the PowerExchange base product on MVS by performing the following tasks:

♦ Allocates the following PowerExchange data sets: DBRMLIB, DTLDATA, DTLDEMO, DTLEXPL, DTLLOG, DTLMSG, LOADLIB, PROCLIB, and SRCLIB. For information about the space requirements and DCB attributes of these data sets, see Table 5-2 on page 33.

♦ Expands the following distributed libraries using TSO/E RECEIVE: DTLDATA, DTLMSG, LOADLIB, and SRCLIB.

♦ Copies the following DB2 bulk DBRM files to the DBRMLIB library: DTLAMDB2 and DTLAMV8F.

♦ Optionally submits additional installation jobs.

− If you selected Auto Submit On in the MVS Installation Assistant, the SETUPBLK job submits additional jobs based on the options you selected.

− If you did not select Auto Submit On, you must manually submit all jobs.

♦ Adds the JOB card in the JOBCARD member of RUNLIB library to the additional installation jobs.

To run the SETUPBLK job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUPBLK job.

2. Submit the SETUPBLK job.

The job adds the JOB card that is in JOBCARD member to the other installation jobs.

If you selected the Auto Submit On option, the SETUPBLK submits the XIBLK100 job automatically. This job deletes the VSAM data set for data maps if it exists and then allocates and initializes a new copy of data map data set.

3. If you did not select the Auto Submit On option in the MVS Installation Assistant, manually submit the XIBLK100 job.

Although all jobs are expected to complete with a return code of 0, VSAM file allocations might complete with a return code of 8 if a file deletion is attempted before the allocation. Also, some jobs might complete successfully with a return code of 1.

4. If you did not select DB2, IDMS, or any change data capture sources, submit the following jobs after the XIBLK100 job completes:

XIZZZ998 job Populates DTLDATA, DTLDEMO, DTLEXPL, and PROCLIB with the appropriate members from RUNLIB.

XIZZZ999 job Deletes the members from RUNLIB copied to other libraries in job XIZZZ998.

Otherwise, refer to the XJOBS member in the RUNLIB library to determine which jobs to run next. The MVS Installation Assistant places the XJOBS member in the RUNLIB library. View the XJOBS member to see the names of the members containing the jobs that you must submit from RUNLIB.


Step 6. Add the PowerExchange Load Library to the APF ListOptionally, you can add the PowerExchange LOADLIB library to the APF list. PowerExchange requires that the LOADLIB library be APF-authorized to perform the following tasks:

♦ Issue RACROUTE security calls to check permissions.

♦ Wait for tape mounts when no tape drives are available.

♦ Wait for user data sets currently in-use by other users.

♦ Acquire IDMS schema and sub-schema information.

For more information about updating the APF list, see your MVS systems programming team.

Review the STEPLIB DD statement in any PowerExchange JCL, especially the PowerExchange Listener JCL in the STARTLST and PSTRTLST members of the RUNLIB library. All of the libraries that are concatenated in the STEPLIB DD statement must be authorized. Otherwise, authorization is not in effect and failures will occur.

Phase II. Install the PowerExchange Change Data Capture SoftwareThis section covers change data capture installation procedures that are generic to any MVS-based capture environment. If you did not select change data capture for any data sources, proceed to “Phase III: Install the PowerExchange Software for Specific Data Sources” on page 50.

The MVS change data capture environment requires the following components:

♦ PowerExchange Listener

♦ PowerExchange Agent

♦ PowerExchange Logger

♦ At least one Environmental Change Capture Routine (ECCR)

The PowerExchange base software installation installs the PowerExchange Listener elements. You must install the other components. You also must start the PowerExchange Agent to run the final setup job for the PowerExchange Logger.

Step 7. Submit Change Data Capture JobsTo install change data capture, submit the following jobs that are in the RUNLIB library:

SETUPCC1 job Allocates and populates the common change data capture component data sets. For information about the space requirements and DCB attributes of these data sets, see Table 5-3 on page 34.

XICDC100 jobAllocates the CCT data set for capture registrations.

XICDC200 job Allocates the CDCT data set for PowerExchange Condense information.

XICDC300 job Allocates the CDEP data set for tracking CDC extraction information.

XICDC400 job Allocates the DTLCAMAP data set for extraction maps.

XICDC500 jobAllocates the PowerExchange Logger active log and emergency restart data sets.

XICDC600 jobAssembles the EDMSDIR options module and writes it to the USERLIB.


The XICDC100 through XICDC500 jobs create a number of VSAM data sets for capture processing using the data set specifications in Table 5-3 on page 34. These data set sizes are adequate to build a test PowerExchange environment on a single MVS image.

For an efficient CDC implementation in a production environment, consider the number and size of the PowerExchange Logger active log and archive log data sets. Review data set sizes and parameters for the all change data capture components after the installation is complete. For more information about configuring the change data capture components, see the PowerExchange Change Data Capture Guide for z/OS.

Step 8. Copy the PowerExchange Agent ProcedureThe installation creates a sample procedure for the PowerExchange Agent called AGENTSTP. The XIZZZ998 job copies this procedure to the PROCLIB library and renames it to the Agent Started Task ID value that was specified in the MVS Installation Assistant.

Copy the PowerExchange Agent procedure to the appropriate system PROCLIB library for started tasks.

Step 9. Add the PowerExchange Load Libraries to the APF ListFor change data capture, you must add the following load libraries to the APF list:

♦ hlq.LOAD

♦ hlq.LOADLIB

♦ hlq.CRG.LOAD, if using IMS synchronous capture

The hlq variable is the high-level qualifier specified for Seq \ Install Library in the MVS Installation Assistant. For more information about updating the APF list, see your MVS systems programming team.

Review the STEPLIB DD statement in PowerExchange JCL, such as the PowerExchange Listener JCL. All libraries that are concatenated in the STEPLIB DD statement must be authorized. Otherwise, authorization is not in effect and failures will occur.

Step 10. Start the PowerExchange AgentStart the PowerExchange Agent by using the MVS START command:

START | S agent_name

The agent_name variable is the member name of the PowerExchange Agent procedure in the started task PROCLIB library.

The PowerExchange Agent started task name can be up to eight characters in length and can be different from the AgentID parameter defined in the AGENTCTL member of RUNLIB library.

Step 11. Submit the SETUPCC2 JobThe SETUPCC2 job creates the PowerExchange Logger EDMUPARM module using the options that you specified and also defines the active log data sets in the PowerExchange Logger emergency restart data sets.

To run the SETUPCC2 job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUPCC2 JCL. You can change the job name, if necessary.

2. Submit the SETUPCC2 job.


Phase III: Install the PowerExchange Software for Specific Data Sources

The following steps describe how to install PowerExchange software for Adabas CDC, DB2, and IDMS data sources. If you did not select any of these data sources, proceed to “Where to Go from Here” on page 51.

Step 12. Install Software for Adabas CDCThe SETUPADA job creates a file that is required for PowerExchange for Adabas Change Data Capture. If you intend to use PowerExchange for Adabas bulk data movement only, do not submit this job.

To run the SETUPADA job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUPDB2 JCL. You can change the job name, if necessary.

2. Submit the SETUPADA job. This job allocates the PowerExchange PLOG Catalog (PCAT) VSAM data set to be used by the Adabas ECCR.

Step 13. Install Software for DB2 Data SourcesThe SETUPDB2 job submits jobs that install PowerExchange for DB2 based on the options you specified in the MVS Installation Assistant.

To run the SETUPDB2 job:


2. Submit the SETUPDB2 job.

This jobs submits the XIDDB210 job. The XIDDB210 job performs the DB2 bind for PowerExchange for DB2 bulk data processing. You must have DB2 BINDADD authority to run this job.

If you selected DB2 Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, the SETUPDB2 job also submits the XIDDB220 job. The XIDDB220 job performs the following tasks:

♦ Creates the capture directory database, table spaces, tables, and indexes for PowerExchange for DB2 CDC

♦ Submits the XIDDB225 job, which performs the DB2 binds for the DB2 ECCR. You must have SYSCTRL authority to run this job.

3. Authorize the appropriate users to access the DB2 plans. The following PowerExchange address spaces require access to the PowerExchange for DB2 plans:

♦ PowerExchange Listener requires access to the plan that is specified in the XIDDB210 job.

♦ PowerExchange DB2 ECCR requires access to the plan that is specified in the XIDDB225 job.

Step 14. Install Software for IDMS Data SourcesThe SETUPIDM job submits jobs that install PowerExchange for IDMS based on the options you specified in the MVS Installation Assistant.

To run the SETUPIDM job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUPIDM JCL. You can change the job name, if necessary.

2. Submit the SETUPIDM job.

This job submits the XIDIDM10 job. The XIDIDM10 job copies the system IDMS load libraries to the PowerExchange copies of these libraries, called hlq.IDMS.LOADLIB and the hlq.IDMS.DBA.LOADLIB. By default, PowerExchange uses these copies to import IDMS schemas and subschemas. For more


information about alternatives and configuring PowerExchange for IDMS schema imports, see the PowerExchange Bulk Data Movement Guide.

If you selected IDMS Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, the SETUPIDM job also submits one of the following jobs:

XIDIDM14Runs if you selected IDMS Capture Type Synchronous but cleared the IDMS Version >= 15 check box. This job creates the PowerExchange DR14DBIO module for IDMS Version 14 and earlier.

XIDIDM15 Runs if you selected IDMS Capture Type Synchronous and the IDMS Version >= 15 check box. This job creates the PowerExchange DR15DBIO module for IDMS Version 15 and later.

XIDIDL10Runs if you selected IDMS Capture Type Log-Based. This job creates the Log Catalog VSAM data set for use by the PowerExchange IDMS log-based ECCR.

Where to Go from HereAfter completing installation, you must configure PowerExchange. For more information, see the following documents:


♦ For change data capture configuration, see the PowerExchange Change Data Capture Guide for z/OS.

♦ For DBMOVER configuration file parameters, see the PowerExchange Reference Manual.

Once you have configured PowerExchange, you can start the PowerExchange Listener and, if required, the PowerExchange Aget, PowerExchange Logger, PowerExchange ECCRs, and PowerExchange Condense. For more information about starting and stopping PowerExchange tasks, see the PowerExchange Command Reference.

Upgrading PowerExchange on MVS to a New ReleaseThis section describes how to upgrade PowerExchange for MVS to a new release. If you use the upgrade options in the MVS Installation Assistant, PowerExchange upgrades the message, sample, and load libraries. PowerExchange does not create new operational data libraries, such as those containing data maps, capture registrations, extraction maps, and captured change data. As a result, you do not need to migrate the contents of these data sets to the newly allocated data sets, which makes the upgrade process simpler.

If you need to add new data sources to an existing PowerExchange environment, use the new data set names upgrade option.

The upgrade options do not create a complete PowerExchange environment. If you need to run the new PowerExchange release concurrently with the existing PowerExchange release, you must perform a full install as described in “Installing PowerExchange on MVS for the First Time” on page 32.

For a PowerExchange change data capture environment, Informatica recommends using the upgrade option to prevent potential loss of captured change data.

Upgrading PowerExchange on MVS to a New Release 51

Before You Begin


License KeyIf you have an existing InstParm file, the license key is stored there. You import the InstParm file as part of the upgrade procedure. If you are adding new features, you might need to obtain a new license key. For more information, see “Obtaining a License Key” on page 12.

Task Flow for Upgrading to a New ReleaseTable 5-5 lists the high-level steps that you need to perform to upgrade PowerExchange. These steps are grouped into the following phases:

♦ Phase I: Upgrade the PowerExchange base software. Required of all PowerExchange users.

♦ Phase II: Upgrade the PowerExchange Change Data Capture software. Required for users who have purchased the CDC option.

♦ Phase III: Update the PowerExchange software for specific data sources. Required for users of Adabas CDC, DB2 bulk data movement and CDC, and IDMS bulk data movement and CDC.

♦ Phase IV: Post-upgrade activities. Required for all PowerExchange users.

Table 5-5. PowerExchange Upgrade Task Flow and Checklist

Step Complete

Phase I: Upgrade Base PowerExchange Software

“Step 1. Stop Access to PowerExchange” on page 53.

“Step 2. Allocate the BINLIB and RUNLIB Libraries” on page 53.


“Step 4. Run the MVS Installation Assistant to Upgrade to a New Release” on page 54.

“Step 5. Edit the JOBCARD Member in RUNLIB” on page 61.

“Step 6. Submit the SETUBL1E or SETUBL1N Job” on page 61.

“Step 7. Add the PowerExchange Load Library to the APF List” on page 62.

Phase II: Upgrade PowerExchange Change Data Capture Software

“Step 8. Submit Change Data Capture Jobs” on page 62.

“Step 9. Add the PowerExchange Load Libraries to the APF List” on page 62.

Phase III: Upgrade PowerExchange Software for Specific Data Sources

“Step 10. Upgrade Software for Adabas CDC” on page 63.

“Step 11. Upgrade Software for DB2 Data Sources” on page 63.

“Step 12. Upgrade Software for IDMS Data Sources” on page 64.

Phase IV: Post-Upgrade Activities

“Step 13. Review Post-Upgrade Documentation” on page 65.

“Step 14. Copy Started Task Procedures” on page 65.



Phase I: Upgrade the PowerExchange Base SoftwareComplete the following steps to upgrade the PowerExchange base software.

Step 1. Stop Access to PowerExchangeStop the tasks that are using the PowerExchange environment to be upgraded prior to submitting any upgrade jobs.

♦ If you are using PowerExchange bulk data movement only, stop the following tasks:

− All PowerCenter workflows extracting data from or writing data to PowerExchange

− All PowerExchange Listener address spaces

♦ If you are using PowerExchange Change Data Capture, stop the following tasks:



− All ECCR address spaces

− All PowerExchange Condense address spaces

− All PowerExchange Logger address spaces

− All PowerExchange Agent address spaces

Step 2. Allocate the BINLIB and RUNLIB LibrariesYou must preallocate the BINLIB and RUNLIB libraries that are to receive the data from the PowerExchange upgrade. These libraries must have the same attributes as the libraries that you allocated for the first-time installation. However, their fully qualified library names can be different from those of the first-time installation libraries.

The libraries for the upgrade must have the predefined suffixes of BINLIB and RUNLIB. You can define a prefix for these libraries in the MVS Installation Assistant. Depending on which upgrade option you select, PowerExchange either allocates staging libraries or new libraries.

♦ If you select the upgrade option for using existing data set names, PowerExchange allocates staging libraries to hold the data for the new release. PowerExchange provides jobs that copy the contents of the staging libraries to the existing libraries.

♦ If you select the upgrade option for using new data set names, PowerExchange allocates new libraries with the high-level qualifier (HLQ) that you specify in the MVS Installation Assistant.

Verify that the HLQ that you use for allocating the BINLIB and RUNLIB libraries matches the appropriate HLQ on the Review Dataset Names page:

♦ If you are upgrading using existing data set names, this HLQ is the Staging Library HLQ. It must be different from the HLQ that was specified for the original installation.

♦ If you are upgrading using new data set names, this HLQ is the New HLQ.

To allocate the BINLIB and RUNLIB libraries:

On the MVS system, use ISPF Option 3.2 to allocate the BINLIB and RUNLIB libraries. You can also use JCL to allocate the libraries.


Table 5-6 describes the BINLIB and RUNLIB libraries and the parameters for allocating them:

The following additional libraries will be allocated during the PowerExchange upgrade process:

♦ All of the libraries described in Table 5-2 on page 33 except DATAMAPS.

♦ CRG.LOAD, DBRM, LOAD, and SAMPLIB libraries. For descriptions of these libraries, see Table 5-3 on page 34.



1. From a Windows command prompt, make a temporary directory in which to install the MVS components. For example:

mkdir pwx_mvs_vxxx

2. Find and run the product upgrade installation executable that has a name such as:

pwxos26_Vxxx.exe

The xxx variable is the version number. For example, pwxos26_v852.exe is the name of the executable for the PowerExchange version 8.5.2 installation on MVS.


The WinZip Self-Extractor places several files in the root directory and creates the following subdirectories that also contain files:

♦ binary

♦ runlib

4. Click OK.


Step 4. Run the MVS Installation Assistant to Upgrade to a New ReleaseUse the MVS Installation Assistant to complete these tasks:

♦ Set the variables for your MVS installation and submit them through a single process.




Directory Blocks

DCB Characteristics


CYLS (100, 20) 10 RECFM FB

LRECL 80



The AAINDEX member describes each member in the RUNLIB library.

CYLS (20,10) 50 RECFM FB

LRECL 80



♦ Move the software library binary files to the MVS system into the BINLIB library.

♦ Move customized MVS library members to the MVS system into the RUNLIB library.

After running the MVS Installation Assistant, you must submit several jobs that PowerExchange supplies manually on the MVS system.

To run the MVS Install Assistant:


2. On the MVS Installation Assistant, select Upgrade to a New Release and click Next.

Tip: On any page, click Save to save your installation selections.

3. On the Software Only Upgrade page, select one of the following options and then click Next:

Upgrade using existing data set namesSelect this option to use the same names as the existing installation for the message, sample, and load libraries. You cannot add or change data sources if you select this upgrade option.

The MVS Installation Assistant performs these steps:

♦ Populates the staging RUNLIB and BINLIB libraries.

♦ Backs up existing execution, sample, and load libraries.

♦ Copies upgrade libraries to the existing library names.

♦ Maintains existing data set names for VSAM files, the USERLIB data set, PowerExchange Logger logs, PowerExchange Condense data sets, and the PowerExchange Agent cache data set.

If you use this upgrade option, you do not have to change any existing JCL. Proceed to “To upgrade using existing data set names:” on page 55.

Upgrade using new data set namesSelect this option to use new data set names for the message, sample, and load libraries. You can also add or change data sources.

The MVS Installation Assistant performs these steps:

♦ Creates new load and sample libraries.

♦ Maintains existing data set names for VSAM files, the USERLIB, PowerExchange Logger logs, PowerExchange Condense data sets, and the PowerExchange Agent cache data set.

If you select this option, you must edit existing JCL to specify the new library names. PowerExchange provides new, customized versions of PowerExchange procedures in the new PROCLIB library. Proceed to “To upgrade using new data set names:” on page 58.

To upgrade using existing data set names:

1. On the Import Previous Parms page, select the version of PowerExchange from which you are importing parameters from the Old Version list.

You must select the old version for the following reasons:

♦ If the old version is earlier than 5.2.2, the MVS Installation Assistant prompts you to perform a full install instead of an upgrade because too much has changed.

♦ The upgrade jobs use the old version as part of the prefix for the backup data sets by appending “.Vversion” to the end of the HLQ you specify.

2. From the New Version list, select the PowerExchange version to which you are upgrading.

3. If you have not copied the customized InstParm file from the previous full install to the new install directory, click Import Previous Parms. By importing parameters from the previous InstParm file, you preserve any customization that was done for your data sources and data set names.

Browse to the location of the customized InstParm file and click OK. The customized InstParm file can have any name. After you select the customized InstParm file, save operations in the MVS Installation Assistant store the imported parameters in the InstParm file that is in the new install directory.


Warning: After you select an upgrade option and progress through the MVS Install Assistant pages, you cannot switch to the other upgrade option without first restoring the InstParm file to the new install directory.

Click Next.

4. On the Review Dataset Names page, enter the following information and then click Next:

5. Review the information on the subsequent “Review” pages and then click Next. These pages depend on the data sources and targets that you selected during your previous install, as shown in Table 5-7:

Note: The Upgrade using existing data set names option does not enable you to change data source information. To change these data sources, select either the Upgrade using new data set names option or the Full Install option.


Logon ID Logon ID that enables connection to the MVS system.

Agent / Logger Prefix Read-only. Prefix used for the PowerExchange Agent and PowerExchange Logger.

Staging Library HLQ High-level qualifier (HLQ) for the staging libraries. Use as many qualifier levels as required. Default is PWX.Vnew_versionSTG.Maximum length is 26 characters.

License Key PowerExchange license key that you used for the last installation. Enter a new license key if you have a new one. Otherwise, accept the previous license key.

Table 5-7. Review Data Source Parameters

Data Source Review This Page

All Review Dataset Volume \ Unit

All Review Data Sources and Targets

Any capture data source Review CDC Common Parameters

Adabas Review ADABAS Parameters

Datacom Review Datacom Parameters

DB2 Review DB2 Parameters

DB2 CDC Review DB2 CDC Parameters

IDMS Review IDMS Parameters

IDMS CDC Review IDMS CDC Parameters

IMS Review IMS Parameters

IMS CDC Review IMS CDC Parameters

MQ Series Review MQ Series Parameters

VSAM Review VSAM Parameters

All Review Additional Parameters


6. On the Backup Datasets page, enter the following information and then click Next:

7. On the Create Runlib JCL page, verify the following information and then click Next:

The MVS Installation Assistant creates the XRunlib folder. The XRunlib folder contains the files from the runlib folder, which are customized with the values that you entered in the wizard.



Create Backup \ Restore Jobs Select this option to create a backup of the current installation from the location information that you enter in the From HLQ and To HLQ boxes.

From HLQ (Sequential and PDS)

HLQ of the current sequential and PDS data sets that you are using in the PowerExchange environment that is currently running.

To HLQ HLQ of the backup sequential and PDS data sets that PowerExchange creates during the upgrade process to save a copy of the currently running data sets. If necessary, use these data sets to restore the PowerExchange environment back to the pre-upgrade state.

From HLQ (VSAM) HLQ of the current VSAM data sets that you are using in the PowerExchange environment that is currently running.

To HLQ HLQ of the backup VSAM data sets that PowerExchange creates during the upgrade process to save a copy of the currently running data sets. If necessary, use these data sets to restore the PowerExchange environment back to the pre-upgrade state.

Select Datasets to Backup Select the All option to back up all data sets, or select one or more of the other data set options to back up specific data sets.

Informatica recommends you select All to back up all data sets. This option allows the PowerExchange environment to be restored to the pre-upgrade state if fallback is necessary after upgrading.


Runlib Data set name of the RUNLIB library that is in the imported InstParm file. This data set name should match the RUNLIB data set name that is used by the currently running PowerExchange environment and be different from the staging RUNLIB data set name. Note: The MVS Installation Assistant does not update this library. This library is used in customizing JCL written to the staging RUNLIB library that is allocated for the upgrade.

Binary Data set name of the BINLIB library that is in the imported InstParm file. This data set name should match the BINLIB data set name that is used by the currently running PowerExchange environment and be different from the staging BINLIB data set name.Note: The MVS Installation Assistant does not update this library. This library is used in customizing JCL written to the staging BINLIB library that is allocated for the upgrade.


IP Address/Node IP address of the MVS system on which you want to install PowerExchange.

Mixed Case Password Option for using a mixed-case password.If you clear this option, the password is changed to uppercase.

Logon ID Logon user ID to use for connecting to the MVS system.

Password Password to use for connecting to the MVS system.


9. The Check FTP Status page appears, which displays the status of the FTP transfer operation. After the FTP transfer completes, click Next.

10. Proceed to “Step 5. Edit the JOBCARD Member in RUNLIB” on page 61.

To upgrade using new data set names:

1. On the Import Previous Parms page, select the PowerExchange version from which you are importing parameters in the Old Version list.

You must select the old version for the following reasons:

♦ If the old version is older than 5.2.2, the MVS Installation Assistant prompts you to perform a full install instead of an upgrade because too much has changed.

♦ The upgrade jobs use the old version as part of the prefix for the backup data sets by appending “.Vversion” to the end of the HLQ you specify.

2. From the New Version list, select the PowerExchange version to which you are upgrading.

3. If you have not copied the customized InstParm file from the previous full install to the new install directory, click Import Previous Parms. By importing parameters from the previous InstParm file, you preserve any existing customization that was done for data sources and data set names.

Browse to the location of the customized InstParm file and click OK. The customized InstParm file can have any name. After you select the customized InstParm file, save operations in the MVS Installation Assistant store the imported parameters in the InstParm file that is in the new install directory.

Warning: After you select an upgrade option and progress through the MVS Install Assistant pages, you cannot switch to the other upgrade option without first restoring the InstParm file to the new install directory.

Click Next.

4. On the Review Dataset Names page, enter the following information and then click Next:


Runlib Displays the staging RUNLIB data set name that is the target of the FTP transfer of XRunlib folder contents. Verify that this data set name is different from the RUNLIB data set name displayed on the Create Runlib JCL page.

Binary Displays the staging BINLIB data set name that is the target of the FTP transfer of the binary folder contents. Verify that this data set name is different from the BINLIB data set name displayed on the Create Runlib JCL page.


Logon ID Logon ID that will allow connection to the MVS system.

Agent / Logger Prefix Read-only. Prefix used for the PowerExchange Agent and PowerExchange Logger in the original installation.

High-Level Qualifiers

New HLQ High-level qualifier (HLQ) for the new data set names. Use as many qualifier levels as required.Default is PWX.NEW. Maximum length is 26 characters.

Old HLQ Read-only. Old HLQ.

VSAM Read-only. HLQ for the VSAM library.



5. On the Review Dataset Volume \ Unit page, enter the following information and then click Next:

6. The Review Data Sources and Targets page appears. Optionally, select additional data sources and targets and click Next.

Archive Read-only. HLQ for the archive library.

License Key PowerExchange license key that you used for the last installation. Enter a new license key if you received a new license key or are installing new features. Otherwise, accept the previous license key.


Default Volume Volume serial number (VOLSER) of the DASD volume on the MVS system on which you want to install the PowerExchange libraries.

Default Unit Generic or esoteric unit name that is used on the MVS system on which you want to install PowerExchange.

Use Defaults Select this check box to use the values in the Default Volume and Default Unit fields for PowerExchange data sets. Clear this check box to specify other volumes and units in the subsequent fields.

Permanent Data Set Options

Volume (Seq) A valid VOLSER for the PowerExchange non-VSAM data sets.

Volume (VSAM) A valid VOLSER for the PowerExchange VSAM data sets or an asterisk (*) if you are using SMS.

Unit (Seq) A generic or esoteric unit name for the non-VSAM data set volume that you specified.

Unit (Archive) A generic or esoteric unit name for the PowerExchange Logger archive log data sets. Informatica Corporation recommends that you write the archive log data sets to DASD.

Note: This parameter is one of many parameters that control archive logging. For more information about the PowerExchange Logger EDMUPARM parameters, see the PowerExchange Change Data Capture Guide for z/OS.

Storage Class for Seq, VSAM, and Archive

SMS storage classes for PowerExchange data sets. These fields are relevant only if you use SMS. You do not need to specify any values for Volume or Unit if you specify an SMS storage class. Note: The SMS ACS routines in your installation might not allow specification of SMS classes or might override the values that you specify.

Mgmt. Class for Seq, VSAM, and Archive

SMS management classes for PowerExchange data sets. These fields are relevant only if you use SMS.Note: The SMS ACS routines in your installation might not allow specification of SMS classes or might override the values that you specify.

Data Class for Seq, VSAM, and Archive

SMS data classes for PowerExchange data sets. These fields are relevant only if you use SMS.Note: The SMS ACS routines in your installation might not allow specification of SMS classes or might override the values that you specify.

PowerExchange Condense Parameters

Check Point Volumes for Seq, VSAM, and Archive

VOLSERs for the checkpoint data sets, which map to the CHKPT_VOLSERS statement in the PowerExchange Condense configuration file.

Volume VOLSER for full condense files, which maps to the CONDF_VOL statement in the PowerExchange Condense configuration file.

Unit Unit for full condense files, which maps to the CONDF_UNIT statement in the PowerExchange Condense configuration file.



Note: The Upgrade using new data set names option does not allow you to remove data sources. To remove data sources, select the Full Install option.

7. Review or add information on the subsequent “Review” pages. These pages depend on the data sources and targets that you selected, as shown in Table 5-8.

If you added a data source, enter information about that data source and click Next. For information about the data source options, see the descriptions under the Full Install option.

For existing data sources, review the information on the pages that appear and then click Next.

8. On the Backup Datasets page, enter the following information and then click Next:

Table 5-8. Review Data Source Parameters

Data source Page

Any capture data source Review CDC Common Parameters

Adabas Review ADABAS Parameters

Datacom Review Datacom Parameters

DB2 Review DB2 Parameters

DB2 CDC Review DB2 CDC Parameters

IDMS Review IDMS Parameters

IDMS CDC Review IDMS CDC Parameters

IMS Review IMS Parameters

IMS CDC Review IMS CDC Parameters

MQ Series The Review MQ Series Parameters

VSAM The Review VSAM Parameters

All Review Additional Parameters


Create Backup \ Restore Jobs Select this option to create a backup of the current installation from the location information that you enter in the From HLQ and To HLQ boxes.

From HLQ (Sequential and PDS)

HLQ of the current sequential and PDS data sets that you are using in the PowerExchange environment that is currently running.

To HLQ HLQ of the backup sequential and PDS data sets that PowerExchange creates during the upgrade process to save a copy of the currently running data sets. If necessary, use these data sets to restore the environment back to the pre-upgrade state.

From HLQ (VSAM) HLQ of the current VSAM data sets that you are using in the PowerExchange environment that is currently running.

To HLQ HLQ of the backup VSAM data sets that PowerExchange creates during the upgrade process to save a copy of the currently running data sets. If necessary, use these data sets to restore the environment back to the pre-upgrade state.

Select Datasets to Backup Select the All option to back up all data sets, or select one or more of the other data set options to back up specific data sets.

Informatica recommends you select All to back up all data sets. This option allows the environment to be restored to the pre-upgrade state if fallback is necessary after upgrading.



The MVS Installation Assistant creates the XRunlib folder. The XRunlib folder contains the files from the runlib folder, which are customized with the values that you entered in the installation wizard.


11. The Check FTP Status page appears and displays the status of the latest FTP transfer operation. After the FTP transfer completes, click Next.

Step 5. Edit the JOBCARD Member in RUNLIBThe MVS Installation Assistant places the XJOBSU member in the upgrade RUNLIB library. View the XJOBSU member to see the names of jobs that you must submit from the RUNLIB library.

To edit the JOBCARD member:

1. Edit the JOBCARD member in the upgrade RUNLIB library to make any necessary changes, such as to the CLASS or MSGCLASS parameters.

2. If you selected Auto Submit On on the Select Additional Parameters page, add TYPRUN=HOLD to the JOBCARD member to control the execution of the jobs. You must release each job manually.

Step 6. Submit the SETUBL1E or SETUBL1N JobUse either of the following jobs to install the libraries for bulk data movement:

♦ If you selected the Upgrade using existing data set names option, use the SETUBL1E job.

♦ If you selected the Upgrade using new data set names option, use the SETUBL1N job.


Runlib Displays the RUNLIB data set name that is the target of the FTP transfer of the XRunlib folder contents.The Install JCL is customized to use this name. Note: You must preallocate this library.

Binary Displays the BINLIB data set name that is the target of the FTP transfer of the binary folder contents. The install JCL is customized to use this name. Note: You must preallocate this library.



Mixed Case Password Select this option to use a mixed case password.If you clear this option, the password is changed to uppercase.




Runlib RUNLIB data set name that is the target of the FTP transfer of the XRunlib folder contents. Verify that this data set name is the same as the RUNLIB data set name displayed on the Create Runlib JCL page.

Binary BINLIB data set name that is the target of the FTP transfer of the binary folder contents. Verify that this data set name is the same as the BINLIB data set name displayed on the Create Runlib JCL page.


To run the SETUBL1E or SETUBL1N job:

1. In the upgrade RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUBL1E or SETUBL1N job.

2. Verify that the HLQ value in the GENBULK member in the existing RUNLIB library differs from the HLQ value in the GENBULK member in the upgrade RUNLIB library.

3. Submit the SETUBL1E or SETUBL1N job.

This job adds the JOB card to other jobs.

Step 7. Add the PowerExchange Load Library to the APF ListIf you selected the Upgrade using new data set names option and previously authorized the LOADLIB library, you must add the new LOADLIB library to the APF list.

PowerExchange requires APF-authorization for the LOADLIB library to perform the following tasks:

♦ Issue RACROUTE security calls to check permissions.

♦ Wait for tape mounts when no tape drives are available.

♦ Wait for data sets currently in-use by other users.

♦ Acquire IDMS schema and sub-schema information.

Phase II: Upgrade the PowerExchange Change Data Capture Software

This section describes how to upgrade PowerExchange Change Data Capture software to a new release. If you did not select any change data capture data sources, proceed to “Phase III: Upgrade the PowerExchange Software for Specific Data Sources” on page 63.

The PowerExchange base software upgrade upgraded the necessary PowerExchange Listener elements. This section describes how to upgrade the remaining components.

Step 8. Submit Change Data Capture JobsUse the jobs in the RUNLIB library that was allocated for the upgrade.

To submit change data capture jobs:

1. Submit the SETUCC1E or SETUCC1N job. These jobs allocate the data sets that are required for change data capture.

2. Submit the BKUPDS00 job. This job makes backup copies of the data sets that are selected on the Backup Datasets page.

3. If you selected the Upgrade using existing data set names option, submit the INSPWXUE job after BKUPDS00 completes successfully.

4. If you selected the Upgrade using new data set names option, submit the XIZZZ998 job followed by the XIZZZ999 job.

Step 9. Add the PowerExchange Load Libraries to the APF ListIf you selected the Upgrade using existing data set names option, proceed to “Phase III: Upgrade the PowerExchange Software for Specific Data Sources” on page 63.

If you selected the Upgrade using new data set names option, APF-authorize the required libraries. For change data capture, you must add the new versions of the following load libraries to the APF list:

♦ hlq.LOAD

♦ hlq.LOADLIB


♦ hlq.CRG.LOAD, if using IMS synchronous capture

The hlq variable is the value specified for Seq \ Install Library in the MVS Installation Assistant. For more information about updating the APF list, see your MVS systems programming team.

Review the STEPLIB DD statement in PowerExchange JCL, including the JCL for the PowerExchange Listener. All of the libraries that are concatenated in the STEPLIB DD statement must be authorized. Otherwise, authorization will not be in effect and failures will occur.

If you did not select Adabas CDC, DB2, or IDMS data sources, proceed to “Step 13. Review Post-Upgrade Documentation” on page 65.

Phase III: Upgrade the PowerExchange Software for Specific Data Sources

The following steps describe how to upgrade the PowerExchange software for Adabas CDC, DB2, and IDMS data sources. If you did not select any of these data sources, proceed to “Phase IV: Post-Upgrade Activities” on page 65.

If you selected the Upgrade using existing data set names option, perform the following steps for the applicable data sources:

♦ If you are an existing user of DB2 bulk data movement and CDC, perform “Step 11. Upgrade Software for DB2 Data Sources” on page 63.

♦ If you are an existing user of IDMS synchronous CDC, perform “Step 12. Upgrade Software for IDMS Data Sources” on page 64.

If you selected the Upgrade using new data set names option, perform the following steps for the applicable data sources:

♦ If you are a new user of Adabas CDC, perform “Step 10. Upgrade Software for Adabas CDC” on page 63.

♦ If you are a new or existing user of DB2 bulk and CDC, perform “Step 11. Upgrade Software for DB2 Data Sources” on page 63.

♦ If you are a new or existing user of IDMS bulk data movement and synchronous CDC, perform “Step 12. Upgrade Software for IDMS Data Sources” on page 64.

Step 10. Upgrade Software for Adabas CDCIf you selected Adabas CDC as a new data source during the upgrade process, submit the SETUPADA job to create a file that is required for Adabas CDC. If you use PowerExchange for Adabas for bulk data movement only, do not submit this job.

To run the SETUPADA job:


2. Submit the SETUPADA job. This job allocates the PowerExchange PLOG Catalog (PCAT) VSAM data set that the Adabas ECCR uses.

Step 11. Upgrade Software for DB2 Data SourcesUse either the SETUDB2U or SETUPDB2 job to submit jobs that install PowerExchange for DB2 based on the options you selected in the MVS Installation Assistant.

♦ If you used PowerExchange for DB2 prior to the upgrade process, use the SETUDB2U job.

♦ If you selected DB2 as a new data source during the upgrade process, use the SETUPDB2 job.


To run the SETUDB2U job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUDB2U JCL. You can change the job name, if necessary.

2. Submit the SETUDB2U job.

The SETUDB2U job submits the XIDDB210 job. The XIDDB210 job performs the DB2 bind for PowerExchange for DB2 bulk data movement processing. You must have DB2 BINDADD authority to run this job.

If you selected DB2 Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, SETUDB2U also submits the XIDDB225 job. The XIDDB225 job performs the DB2 binds for the DB2 ECCR. You must have SYSCTRL authority to run this job.

3. If you selected new DB2 plan names during the upgrade, authorize the appropriate users to access the DB2 plans. The following PowerExchange address spaces require access to the PowerExchange for DB2 plans:



To run the SETUPDB2 job:


2. Submit the SETUPDB2 job.

This job submits the XIDDB210 job. The XIDDB210 job performs the DB2 bind for PowerExchange for DB2 bulk data processing. You must have DB2 BINDADD authority to run this job.

If you selected DB2 Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, SETUPDB2 also submits the XIDDB220 job. The XIDDB220 job does the following tasks:

♦ Creates the capture directory database, table spaces, tables, and indexes for PowerExchange for DB2 CDC.

♦ Submits the XIDDB225 job, which performs the DB2 binds for the DB2 ECCR. You must have SYSCTRL authority to run this job.

3. Authorize the appropriate users to access the DB2 plans. The following PowerExchange address spaces require access to the PowerExchange for DB2 plans:



Step 12. Upgrade Software for IDMS Data SourcesUse either the SETUIDMU or SETUPIDM job to submit jobs that install PowerExchange for IDMS based on the options that you selected in the MVS Installation Assistant.

♦ If you used PowerExchange for IDMS synchronous CDC prior to the upgrade process, use the SETUIDMU job.

♦ If you selected IDMS as a new data source during the upgrade process, use the SETUPIDM job.

Note: If you used PowerExchange for IDMS bulk data movement only or log-based CDC prior to the upgrade process, no additional installation is required.

To run the SETUIDMU job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUIDMU JCL. You can change the job name, if necessary.

2. Submit the SETUIDMU job.

If you selected IDMS Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, SETUIDMU submits one of the following jobs:


XIDIDM14Runs if you selected IDMS Capture Type Synchronous and cleared the IDMS Version >= 15 check box. This job creates the PowerExchange DR14DBIO module for IDMS Version 14 and earlier.


To run the SETUPIDM job:

1. In the RUNLIB library, add the JOB card that is in the JOBCARD member to the SETUPIDM JCL. You can change the job name, if necessary.

2. Submit the SETUPIDM job.

This job submits the XIDIDM10 job. The XIDIDM10 job copies the system IDMS load libraries to the PowerExchange copies of these libraries, called hlq.IDMS.LOADLIB and hlq.IDMS.DBA.LOADLIB. By default, PowerExchange uses these copies to import IDMS schemas and subschemas. For more information about alternatives and configuring PowerExchange for IDMS schema imports, see the PowerExchange Bulk Data Movement Guide.

If you selected IDMS Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, the SETUPIDM job submits one of the following jobs:



XIDIDL10Runs if you selected IDMS Capture Type Log-Based. This job creates the Log Catalog VSAM data set for use by the PowerExchange IDMS log-based ECCR.

Phase IV: Post-Upgrade Activities

Step 13. Review Post-Upgrade DocumentationAfter completing the upgrade of the PowerExchange software, review the following items:

♦ PowerExchange Migration Guide

♦ PowerExchange Release Notes for additional installation, configuration, or migration information

♦ The upgraded RUNLIB library for any new or changed members

Step 14. Copy Started Task ProceduresIf you selected the Upgrade using new data set names option, you must copy any new or changed procedures for started tasks from the upgrade PowerExchange PROCLIB library to a system started task PROCLIB library.

Step 15. Resume Access to PowerExchangeTo resume access to PowerExchange, you must start the tasks for bulk data movement and change data capture in the upgraded PowerExchange environment.

♦ If you are using PowerExchange bulk data movement, start the following tasks:



♦ If you are using PowerExchange Change Data Capture, start the following tasks:








Where to Go from HereIf you selected the Upgrade using new data set names option and additional data sources, you must configure PowerExchange prior to using those data sources for bulk data movement or change data capture. For configuration information, see the following documents:


♦ For change data capture configuration, see the PowerExchange Change Data Capture Guide for z/OS.

Installing a Service Pack for PowerExchange on MVSThis section describes how to install a service pack to an existing PowerExchange installation on MVS. If you need to apply a service pack to a new installation, see “Installing PowerExchange on MVS for the First Time” on page 32.

Service packs provide only the message, sample, and load libraries. PowerExchange does not create new data libraries, such as those containing data maps, capture registrations, and extraction maps. As a result, you do not need to migrate the contents of these data sets to new data sets, which makes the service pack install process simpler.

You cannot add new data sources to an existing PowerExchange environment using a service pack. To add new data sources, you must use the full install or upgrade procedure.

PowerExchange service packs are cumulative so you need to install only the latest service pack to update software to that level.

Before You Begin


License KeyIf you have an existing InstParm file, the license key is stored there. You import the InstParm file as part of the service pack installation procedure. If you are adding new features, you might need to obtain a new license key. For more information, see “Obtaining a License Key” on page 12.

Task Flow for a Installing a Service PackTable 5-9 describes the high-level steps that you need to perform to install a PowerExchange service pack. You can use this table as a checklist to track your progress in applying a service pack.

These steps are grouped into the following phases:

♦ Phase I: Install the PowerExchange service pack.

♦ Phase II: Upgrade the PowerExchange software for specific data sources.


♦ Phase III: Perform post-service-pack upgrade activities.

Phase I: Install the PowerExchange Service PackComplete the following steps to apply a service pack to PowerExchange.

Step 1. Stop Access to PowerExchangeStop the tasks that are using the PowerExchange environment to which you want to apply the service pack prior to running any service pack jobs.

♦ If you are using PowerExchange bulk data movement only, stop the following tasks:



♦ If you are using PowerExchange Change Data Capture, stop the following tasks:







Step 2. Allocate the BINLIB and RUNLIB LibrariesYou must preallocate the BINLIB and RUNLIB libraries that are to receive the data from the PowerExchange service pack. These libraries must have the same attributes as the libraries that you allocated for the first-time installation or last upgrade installation. However, their fully qualified library names can be different from those of the previous libraries.

Table 5-9. PowerExchange Service Pack Installation Task Flow and Checklist

Step Complete

Phase I: Install the PowerExchange Service Pack

“Step 1. Stop Access to PowerExchange” on page 67.

“Step 2. Allocate the BINLIB and RUNLIB Libraries” on page 67.


“Step 4. Run the MVS Installation Assistant” on page 69.

“Step 5. Run the PRESTLIB Job” on page 70.

“Step 6. Back Up Existing Libraries” on page 70.

“Step 7. Update the PowerExchange Libraries” on page 70.

Phase II: Upgrade the PowerExchange Software for Specific Data Sources

“Step 8. Update the Software for DB2 Data Sources” on page 71.

“Step 9. Update the Software for IDMS Data Sources” on page 71.

Phase III: Post-Service-Pack Upgrade Activities

“Step 10. Review Post-Update Documentation” on page 72.



Installing a Service Pack for PowerExchange on MVS 67

The libraries that you allocate must have the predefined suffixes of BINLIB and RUNLIB. You can define a prefix for these libraries in the MVS Installation Assistant. Specify a high-level qualifier (HLQ) that is different from that being used in the existing PowerExchange environment.

To allocate the RUNLIB and BINLIB libraries:

On the MVS system, use ISPF Option 3.2 to allocate the libraries. You can also use JCL to allocate the libraries. When allocating these libraries, enter a high-level qualifier (HLQ) that matches the Service Pack HLQ that you enter on the Select Dataset Names page of the MVS Installation Assistant.

Table 5-10 describes these libraries and how to allocate them:

The following additional libraries will be allocated by the PowerExchange service pack install process:

♦ DBRMLIB, DTLMSG, LOADLIB, and SRCLIB libraries. For descriptions of these libraries, see Table 5-2.

♦ CRG.LOAD, LOAD, and SAMPLIB libraries. For descriptions of these libraries, see Table 5-3.



1. From a Windows command prompt, make a temporary directory in which to install the MVS service pack components. For example:

mkdir pwx_mvs_sp

2. Find and run the service pack installation executable which has a name such as:

pwxnnnspx_zos.exe

The nnn variable is the version number, and x is the service pack number. For example, pwx86sp1_zos.exe is the name of the executable for the PowerExchange 8.6 Service Pack 1 installation for MVS.


The WinZip Self-Extractor places several files in the root directory and creates the following subdirectories that also files:

♦ pbinary

♦ prunlib

4. Click OK.




Directory Blocks

DCB Characteristics


CYLS (100, 20) 10 RECFM FB

LRECL 80



The AAINDEX member describes each member in RUNLIB.

CYLS (20,10) 50 RECFM FB

LRECL 80




6. Copy the InstParm file from the current product installation directory to the temporary directory. Replace the current product version provided with the service pack version. The InstParm file has all of your customized settings.

Step 4. Run the MVS Installation AssistantUse the MVS Installation Assistant to perform the following tasks:

♦ Move any changed software library binary files to the BINLIB library.

♦ Move any new or changed RUNLIB members to the RUNLIB library.

After running the MVS Installation Assistant, you must manually submit at least the PRESTLIB job on the MVS system.

To run the MVS Install Assistant:


2. On the MVS Installation Assistant, select Install Service Pack and click Next.

Note: On any page, click Save to save your installation selections.

3. On the Install Service Pack page, click Next.

4. On the Select Dataset Names page, enter the following information, and then click Next:


The MVS Installation Assistant creates the PXRunlib folder. The PXRunlib folder contains the files from the prunlib folder, customized with the values entered in the wizard.


Logon ID Logon ID that enables connection to the MVS system.

Agent / Logger Prefix Read-only. Prefix that is used for the PowerExchange Agent and PowerExchange Logger.

Service Pack HLQ High-level qualifier (HLQ) for the service pack libraries. Use as many qualifier levels as required.

Default is PWX.SP.Maximum length is 26 characters.

License Key PowerExchange license key that you used for the last installation. Enter a new license key if you received a new one. Otherwise, accept the previous license key.


Runlib Data set name of the RUNLIB library to which the service pack data will be transferred using FTP. Note: Verify that this data set name does not match the existing RUNLIB data set name that is used by the current PowerExchange environment.

Binary Data set name of the BINLIB library to which the service pack data will be transferred using FTP. Note: Verify that this data set name does not match the existing BINLIB data set name that is used by the current PowerExchange environment.



7. The Check FTP Status page appears, which displays the status of the FTP transfer operation. After the FTP completes, click Next.

Step 5. Run the PRESTLIB JobUse the PRESTLIB job to install the service pack from the service pack BINLIB library into the service pack libraries.

To run the PRESTLIB job:

1. Add a JOB card to the PRESTLIB member in the service pack RUNLIB library.

2. Submit the PRESTLIB job.

Step 6. Back Up Existing LibrariesBack up the following libraries in the current PowerExchange environment:

♦ CRG.LOAD

♦ DBRMLIB

♦ DTLMSG

♦ LOAD

♦ LOADLIB

♦ RUNLIB

♦ SAMPLIB

♦ SRCLIB

Step 7. Update the PowerExchange LibrariesTo implement the service pack changes, you must copy the contents of the service pack libraries to the current PowerExchange environment libraries. In some cases, the service pack libraries contain only new or changed members. In other cases, the service pack libraries contain a complete reshipment of all members.

All service pack libraries are PDS data sets except for DTLMSG, which is a sequential data set. You can use IEBCOPY to copy PDS data sets and IEBGENER to copy sequential data sets. You can also use ISPF Option 3.3 to copy both PDS and sequential data sets.

The following example shows how to use IEBCOPY to copy one library to another:



Mixed Case Password Select this option to use a mixed-case password.Clear this option to have a mixed-case password changed to uppercase.




Runlib RUNLIB data set name that is the target of the FTP transfer of the PXRunlib folder contents.

Binary BINLIB data set name that is the target of the FTP transfer of the pbinary folder contents.


//COPY EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//INDD1 DD DISP=SHR,DSN=hlq_sp.LOAD Service Pack LOAD//OUTDD1 DD DISP=SHR,DSN=hlq.LOAD Current Execution LOAD//SYSIN DD * COPY INDD=((INDD1,R)),OUTDD=OUTDD1/*

The following example shows how to use IEBGENER to copy one sequential data set to another:

//IEBGENER EXEC PGM=IEBGENER//SYSPRINT DD SYSOUT=*//SYSUT1 DD DISP=OLD,DSN=hlq_sp.DTLMSG Service Pack DTLMSG//SYSUT2 DD disp=OLD,DSN=hlq.DTLMSG Current Execution DTLMSG//SYSIN DD DUMMY/*

In both examples, the hlq_sp variable represents the HLQ that you specified in the MVS Installation Assistant for the service pack libraries and the hlq variable represents the HLQ of the current PowerExchange environment.

Phase II: Update the PowerExchange Software for Specific Data Sources

These steps describe how to use service pack jobs to upgrade the PowerExchange software for DB2 and IDMS synchronous CDC data sources. If you did not select either of these data sources, proceed to “Phase III: Post-Service-Pack Install Activities” on page 72.

Step 8. Update the Software for DB2 Data SourcesThe SETUDB2U job submits other jobs that perform DB2 binds for PowerExchange for DB2 based on the options that you selected in the MVS Installation Assistant.

To run the SETUDB2U job:

1. Edit the SETUDB2U JCL in the service pack RUNLIB library by adding the JOB card from the JOBCARD member of the current RUNLIB library. You can change the job name, if necessary.

2. Submit the SETUDB2U job.

This job submits the XIDDB210 job. The XIDDB210 job performs the DB2 bind for PowerExchange for DB2 bulk processing. You must have DB2 BINDADD authority to run this job.

If you selected DB2 Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, SETUDB2U also submits the XIDDB225 job. The XIDDB225 job performs the DB2 binds for the DB2 ECCR. You must have SYSCTRL authority to run this job.

Step 9. Update the Software for IDMS Data SourcesThe SETUIDMU job submits other jobs that install code for PowerExchange for IDMS synchronous CDC based on the options that you selected in the MVS Installation Assistant.

To run the SETUIDMU job:

1. Edit the SETUIDMU JCL in the service pack RUNLIB library by adding the JOB card from the JOBCARD member of the current RUNLIB library. You can change the job name, if necessary.

2. Submit the SETUIDMU job.

If you selected IDMS Change Data Capture on the Select Data Sources page in the MVS Installation Assistant, SETUIDMU submits one of the following jobs:




Phase III: Post-Service-Pack Install Activities

Step 10. Review Post-Update DocumentationAfter you successfully install the PowerExchange service pack, review the following items:

♦ PowerExchange Release Notes for additional installation, configuration, or migration information.

♦ Service pack RUNLIB library for any new or changed members.

Step 11. Resume Access to PowerExchangeTo resume access to PowerExchange, you must start the tasks for bulk data movement and change data capture in the upgraded PowerExchange environment.

♦ If you are using PowerExchange bulk data movement only, start the following tasks:



♦ If you are using PowerExchange change data capture, start the following tasks:







Step 12. Test the InstallationRun the DTLINFO job in the RUNLIB library to verify that the PowerExchange version matches the level of the service pack that was installed.


C H A P T E R 6

Installing PowerExchange on Windows


♦ Overview, 73

♦ Installing PowerExchange on Windows, 74

♦ Applying a Service Pack for PowerExchange on Windows, 77

OverviewPowerExchange provides executable files for installing PowerExchange on a Windows 32-bit system and a Windows 64-bit system. You can use these executable files to install or upgrade PowerExchange.

The following table shows the PowerExchange features that the 32-bit executable and the 64-bit executable install:

Note: To install the PowerExchange Navigator on a Windows 64-bit system, you must use the Windows 32-bit executable. The PowerExchange Windows 32-bit executable runs on either a Windows 32-bit or 64-bit system. The PowerExchange Navigator is required for registering data sources and creating data maps.

PowerExchange Software or Feature Description 32-bit executable

for Windows64-bit executable for Windows

PowerExchange Navigator Use to register data sources on Windows and non-Windows systems. You can access the source data that is on the Windows system where the PowerExchange Navigator is installed.

X

PowerExchange bulk data movement

Accesses bulk data in flat files. X X

PowerExchange change data capture

Captures changes from the following source types on Windows:- Oracle- DB2 for Linux, UNIX, and

Windows- Microsoft SQL Server

X X

73

The following table shows the specific 64-bit executable that you must use by type of 64-bit Windows platform:

Also, to help you determine your installation strategy, the following table identifies which executable to use and where to run it for several PowerExchange usage scenarios:

Installing PowerExchange on Windows

Before You BeginVerify that you meet the prerequisites to install PowerExchange.

General Installation RequirementsReview “Preparing to Install PowerExchange” on page 5 before starting the installation process.

Make sure that PowerExchange supports your Windows operating system and the databases to be accessed by PowerExchange. See “Release and Maintenance Requirements” on page 5.

Also, obtain a valid license key. You cannot install PowerExchange until you have a valid key. Usually, a license key is specific to an IP address. Make sure that you get a license key for the correct host IP address. For more information, see “Obtaining a License Key” on page 12.

Disk Space RequirementsThe following table lists the disk space requirements for a Windows 32-bit or Windows 64-bit installation:

Uninstall Earlier Versions of PowerExchange on WindowsIf you are upgrading PowerExchange, remove the earlier PowerExchange version by selecting Add or Remove Programs from the Control Panel.

Software Platform

PowerExchange for Windows 64-bit with x86 Windows 64-bit operating system running on x86 hardware

PowerExchange for Windows 64-bit with Itanium Windows 64-bit operating system running on HP-UX Itanium hardware

Scenario Install Strategy

Register data sources. Run the PowerExchange 32-bit executable on a Windows 32-bit or 64-bit system to install the PowerExchange Navigator.

Extract data using PowerExchange when the PowerCenter Integration Service is running on a Windows 32-bit system.

Run the PowerExchange 32-bit executable on the Windows 32-bit system where PowerCenter Integration Service is running.

Extract data using PowerExchange when the PowerCenter Integration Service is running on a Windows 64-bit system.

Run the PowerExchange 64-bit executable on the Windows 64-bit system where PowerCenter Integration Service is running.

Product Requirement Comments

PowerExchange 200 MB

Temporary files 150 MB The installer writes the files to the default temporary directory.

74 Chapter 6: Installing PowerExchange on Windows

Run only one PowerExchange version on a Windows system.

Installation Task FlowTable 6-1 lists the high-level steps for installing PowerExchange on a Windows system. Use this table as a checklist to track your installation progress.

Step 1. Log In as a User with the Required AuthorityTo run the installation program, log in as the Administrator user or with a user ID that belongs to the Administrators group. If you do not have Administrator authority, the installation program does not install the PowerExchange Listener service.

Step 2. Run the Installation ProgramThe installation program:

♦ Loads the software into a user-defined directory.

♦ Adds the PowerExchange Listener as a Windows service.

To install PowerExchange on a Windows 32-bit or 64-bit system:

1. Double-click the executable file for your platform. The following table lists the executable files by platform:

The variable nnn is the PowerExchange version number. For example, double-click pwx86_win32_x86.exe to install PowerExchange 8.6.

The executable extracts the files for the installation.

2. Run install.bat from the temporary folder.

3. On the PowerExchange Installer initial page, select a language and click OK.

4. On the Introduction page, click Next.

5. On the Enter License Key page, enter the license key and click Next.

If you do not know your license key, see “Obtaining a License Key” on page 12.

6. On the Choose Shortcut Folder page, select an option to identify the location where you want to create product icons. Then click Next.

7. On the Installation Directory page, accept the default installation directory, or click Choose to browse to an installation directory. Then click Next.

Table 6-1. Windows Installation Task Flow and Checklist

Description Complete?

“Step 1. Log In as a User with the Required Authority” on page 75.

“Step 2. Run the Installation Program” on page 75.

“Step 3. Set Environment Variables” on page 76.

“Step 4. Install the PowerExchange ODBC Drivers (Optional)” on page 76.


Platform Executable file

Windows 32-bit x86 pwxnnn_win32_x86.exe

Windows 64-bit x86 pwxnnn_win_em64t.exe

Windows 64-bit Itanium pwxnnn_win_ia64.exe

Installing PowerExchange on Windows 75

8. On the Pre-Installation Summary page, review the installation information. If the information is correct, click Install.

9. In the PowerExchange Listener Service message box, click OK.

10. On the Install Complete page, select Yes, restart my system and click Done.

Step 3. Set Environment VariablesThe Path environment variable must include the path to the directory where PowerExchange is installed.

Also, if you are running PowerExchange with a local Windows installation of Oracle, you must set the ORACLE_SID and ORACLE_HOME environment variables.

To set or verify environment variables:

1. Click Start > Control Panel.

2. On the Control Panel window, double-click System.

3. On the System Properties window, click the Advanced tab.

4. Click Environment Variables.

5. In the System variables list, select Path and click Edit.

Make sure that the PowerExchange installation path occurs in the comma-separated list of paths. If you accepted the default installation location, use the following default path:

C:\Informatica\PowerExchange

6. In the Path environment variable, include the correct path to the PowerExchange installation directory.

Note: Whenever you change the Path environment variable, you must restart the computer.

7. If you are planning to use PowerExchange with Oracle on this computer, set the ORACLE_SID and ORACLE_HOME environment variables.

Step 4. Install the PowerExchange ODBC Drivers (Optional)Install the PowerExchange Open Database Connectivity (ODBC) drivers if you plan to use ODBC to access PowerExchange from PowerCenter.

To install the ODBC drivers on Windows Vista, you must run the dtlodbci.exe executable with the User Account Control (UAC) administrator privilege. Otherwise, you will not be able to select Informatica PowerExchange from the list of available drivers when creating the ODBC data source on Vista. For more information about creating ODBC data sources, see the PowerExchange Reference Manual.

Tip: To integrate PowerCenter with PowerExchange, Informatica recommends that you use the PowerExchange Client for PowerCenter (PWXPC) instead of PowerExchange ODBC. PWXPC offers additional functionality. For more information, see PowerExchange Interfaces for PowerCenter.

PowerExchange ships with the following thin ODBC drivers:

♦ Informatica PowerExchange Unicode driver. Use this driver to retrieve metadata that contains multibyte characters.

♦ Informatica PowerExchange driver. Use this driver to access the data source.

To install PowerExchange ODBC drivers on systems other than Windows Vista:

At a command prompt, enter the following command:

dtlodbci add

This command installs both ODBC drivers and issues the following messages:

PWX-00607 DTLODBCI VRM x.x.x Build Vxxx started.PWX-02322 ODBC driver "Informatica PowerExchange" added.PWX-02322 ODBC driver "Informatica PowerExchange Unicode" added.


To install PowerExchange ODBC drivers on Windows Vista:

1. Locate the PowerExchange file called dtlodbci.exe.

2. Right-click dtlodbci.exe and select Properties.

3. On the Compatibility tab, select the Run this program as an administrator option.


dtlodbci add

Step 5. Test the InstallationTo test the PowerExchange installation on a Windows client:

Run the DTLINFO utility by entering the following command at the command prompt:

dtlinfo

This command displays the following information for the current installation of PowerExchange: version, release and release level, and build date and time. For more information about DTLINFO, see the PowerExchange Utilities Guide.

Where to Go from HereConfigure PowerExchange prior to performing bulk data movement or change data capture. For configuration information, see the following documents:


♦ For change data capture configuration, see the PowerExchange adapter guides for your data sources.

♦ For dbmover.cfg configuration parameters, see the PowerExchange Reference Manual.

Once you have configured PowerExchange, you can start the PowerExchange Listener service or PowerExchange Listener and, if required, PowerExchange Condense. For more information about starting and stopping PowerExchange tasks, see the PowerExchange Command Reference.

Applying a Service Pack for PowerExchange on Windows

The Windows service pack installation file that you use depends on your installation platform:

Before You BeginBefore applying the service pack, complete the following tasks:

1. Stop all of the following PowerExchange tasks that are running:

♦ PowerExchange Listener

♦ PowerExchange Listener Service

♦ PowerExchange Navigator

Platform Service Pack File

Windows 32-bit pwxwin32_vxxx_spx.exe

Windows 64-bit x86 pwxwin64_vxxx_spx.exe

Windows 64-bit Itanium pwxwinia64_vxxx_spx.exe

Applying a Service Pack for PowerExchange on Windows 77

♦ PowerExchange Condense

♦ PowerCenter extractions using PowerExchange on this computer

2. Back up the PowerExchange installation. By default, PowerExchange is installed in the following location:

c:\Informatica\PowerExchange

Step 1. Run the Installation ProgramUnzip the self-extracting installation file into the PowerExchange installation directory.

Step 2. Copy the License and Configuration Files to the Service Pack Directory

Copy the license.key and dbmover.cfg files from the backup directory to the directory where you applied the service pack.

Step 3. Test the Service Pack InstallationRun dtlinfo.exe to confirm the current version of PowerExchange.


I N D E X

Symbols*ALLOBJ 15*SECADM 15

Aactive log dataset 49Adabas 50, 63Agent 3Authorize 20

BBINLIB 35, 53, 67BINLIB library 36, 54, 68

CCCT library 34CDCT library 34CDEP library 34condlib 17CRTPWXENV 19

Ddatalib 17DATAMAPS library 33DBRM library 34DBRMLIB library 33disk space requirements

Windows 74DS01 35DTLCAMAP library 34DTLDATA library 33DTLDEMO library 33DTLEXPL library 33DTLINFO

MVS 72dtlinfo

UNIX 30

dtlinfo.exe (Windows) 78dtllib 17DTLLOG library 33DTLMSG library 33dtlusr 17

Eenvironment variables

Path (Windows) 76

FFTP Binary file to AS/400 17

IIASP 18, 19Independent Auxiliary Storage Pool (IASP) 18, 19Install Library 18installation

running (Windows) 75task flow, all platforms 5testing (Windows) 77

installing PowerExchange (Windows) 74

JJOBCARD 47, 61

LLD_LIBRARY_PATH 26, 27LIBPATH 26libraries

BINLIB 36, 54, 68CCT 34CDCT 34CDEP 34DATAMAPS 33DBRM 34DBRMLIB 33DTLCAMAP 34DTLDATA 33DTLDEMO 33DTLEXPL 33DTLLOG 33

79

DTLMSG 33LOAD 35LOADCRG 34LOADLIB 34LOGGERNAME.ERDS01 34LOGGERNAME.ERDS02 34LOGGERNAME.USERLIB 35PRILOG.DS01 35PRILOG.DS02 35PRILOG.DS03 35PROCLIB 34RUNLIB 36, 54, 68SAMPLIB 35SECLOG.DS01 35SECLOG.DS02 35SECLOG.DS03 35SR2OUT 35SRCLIB 34SRT2TOTAL 35

library SAVE file 17license key 12, 32License Key File 18LOAD library 35LOADCRG library 34LOADLIB library 34LOGGERNAME.ERDS01 library 34LOGGERNAME.ERDS02 library 34LOGGERNAME.USERLIB library 35

MMVS Components 36, 54, 68MVS Installation Assistant 36, 54, 69

OObject Ownership 20obtaining

license key 12ODBC driver 76operating system requirements 5

PPath environment variable

verifying 76PATH environment variable (UNIX) 26PM_HOME

UNIX Environment Variables 28PowerExchange 1

using with earlier versions of PowerCenter 13PowerExchange ODBC drivers

installing 76Pre-Installation Steps

MVS 66prerequisites

for installation 12

PRILOG.DS01 library 35PRILOG.DS02 library 35PRILOG.DS03 library 35PROCLIB library 34PWX_HOME 26

QQSECOFR 15

RRACF 31Relational Database Directory Entry 20RUNLIB 35, 53, 67RUNLIB library 36, 54, 68

SSAMPLIB library 35SECLOG.DS01 library 35SECLOG.DS02 library 35SECLOG.DS03 library 35Security 31SETUPBLK JCL 47SHLIB_PATH 27SR2OUT library 35SRCLIB library 34SRT2TOTAL library 35supported operating systems 5

TTAR File to UNIX 25TCPADM 16Testing the Installation 21, 28

Uuninstalling

PowerExchange on Windows 74UNIX Installation

Code Pages 27Oracle and UDB Considerations 27

WWindows installation

overview 73

80 Index

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software Corporation (“DataDirect”) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

PWX 86 Installation Guide

Documents

Transcript of PWX 86 Installation Guide