Documente Academic
Documente Profesional
Documente Cultură
Informatica® PowerExchange®
(Version 8.6)
Informatica PowerExchange Installation Guide
Version 8.6
June 2008
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.
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.
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.
Scope
The 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)
Terminology
In 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 Portal
As 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 Site
You can access the Informatica corporate web site at http://www.informatica.com. The site contains
information about Informatica, its background, upcoming events, and sales offices. You will also find product
and partner information. The services area of the site includes important information about technical support,
training and education, and implementation services.
North America / South America Europe / Middle East / Africa Asia / Australia
viii Preface
CHAPTER 1
PowerExchange Installation
Overview
This chapter includes the following topics:
♦ PowerExchange Overview, 1
♦ PowerExchange Components, 1
PowerExchange Overview
PowerExchange 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 Components
PowerExchange 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 Listener
Manages 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 Agent
On 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 Logger
On 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 Condense
Optionally 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:
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 Components 3
4 Chapter 1: PowerExchange Installation Overview
CHAPTER 2
Preparation Overview
Before 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
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.
OS/390 2.10, PQ75394 DLL implicit load use count exceeded never decremented.
z/OS 1.1 - 1.5
z/OS 1.6 PK12893 Poor TCP performance when using TCP Segmentation Offload and
applications
with 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
applications
with small data writes.
z/OS 1.8 and PK46403 The SSL connection code has been updated to properly handle an
1.9 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.
7.1 PQ50802 Resolution for Listener 978-04 when the PowerExchange Listener is using
RRSAF.
Datacom 10
IDMS 14.1
IMS 7.1
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
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
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
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
OS/390 2.10, OW40736 Invalid Search for largest block size for EXCP DCB.
z/OS 1.1 - 1.4
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.
z/OS 1.1 - 1.5 OA01585 z/Architecture mode DIV SAVE HIPERSPACE pages in real.
z/OS 1.4 - 1.6 PQ94363 Repositioning performance degradation multi-volume FBS data set
z/OS 1.8 - 1.9 PK50785 Poor performance with C/C++ I/O users of data sets allocated with
candidate volumes.
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:
CICS TS
APAR Number APAR Description
Version
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.
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.
6.1 II11809 Recommended DB2 fixes for Data Propagator Capture and Apply.
PQ53014 Not all log records returned for IFI IFCID 306 log read.
PQ53869 Wrong records returned from IFI READS IFCID 306 call.
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).
7.1 PQ53014 Not All Log Records Returned For IFI IFCID 306 log read.
PQ53869 Wrong records returned from IFI READS IFCID 306 call.
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).
PK25167 Capture job got ABEND04E RC00C9007E after other member executed
ALTER TABLE ADD COLUMN.
PK46871 IFCID306 call has incorrect value for QW0306RS and QW0306DG when
compression dictionary is unavailable.
PK08078 Mixed schema log records following ALTER DATATYPE on Changed Data
Capture tables.
PK25167 Capture job got ABEND04E RC00C9007E after other member executed
ALTER TABLE ADD COLUMN.
Adabas
CDC 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.
Datacom
CDC requires Datacom version 10 or later.
IDMS
CDC requires IDMS 14.1 or later.
IMS
IMS 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:
9.1 PK24491 ABEND0C1 in DFSDLDD0 during cascade delete due to old PSTCURWA
value.
AIX
CDC requires AIX 5.2 or later. CDC also requires the following AIX maintenance:
IY75338 Lack of serialization within the loadAndInit AIX function. Application fails on dlopen.
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
Windows
On Windows, CDC has the following minimum requirements for DB2, Microsoft SQL Server, and Oracle. For
Oracle, you must apply the specified maintenance patches.
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
Note: Previously, PowerExchange used 44-character license keys. PowerExchange still accepts 44-character keys
that have not expired.
Overview
Install 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.
User ID Requirements
Optionally, 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 Requirements
Verify 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 Key
To 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.
Table 3-1. PowerExchange Installation Task Flow and Checklist for i5/OS
Step Complete
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)
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:\> ftp
ftp> open mysystem
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
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)
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:
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.
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')
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.
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).
X 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.
Overview
Install 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.
23
User ID Requirements
1. 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.
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.
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.
Install PowerExchange
Table 4-2. Linux and UNIX TAR File Names and Subdirectories
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
4. Use FTP in BINARY mode to transfer the TAR file to the current working directory.
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.
3. At the command prompt, enter the following command:
sh install.sh -i gui
To verify that the environment variables are correct, log off and log in again.
For example:
export ADAVERS=v33102
export ADADIR=/home/sag/ada
export ADALNK=$ADADIR/$ADAVERS/adalnk.sl
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"
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
Linux pwxlinux_vxxx_spn.tar
zLinux pwxzlinux_vxxx_spn.tar
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.
Step Complete?
“Step 2. Copy the License and DBMOVER Configuration Files from the Backup”
on page 30.
Step 2. Copy the License and DBMOVER Configuration Files from the Backup
X Copy the license.key and dbmover.cfg files from the backup to the directory where you applied the service
pack.
Overview
This 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.
Error Messages
PowerExchange 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 Time
Run 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.
Installation Requirements
Verify that your system meets installation requirements. For more information, see “Preparing to Install
PowerExchange” on page 5.
License Key
To 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.
Table 5-1. PowerExchange Installation Task Flow and Checklist for MVS
Step Complete
“Step 1. Allocate the BINLIB and RUNLIB Libraries” on page 35. gggg
“Step 3. Run the MVS Installation Assistant for a Full Install” on page 36.
“Step 6. Add the PowerExchange Load Library to the APF List” on page 48.
“Step 9. Add the PowerExchange Load Libraries to the APF List” on page 49.
Step Complete
“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
Space Space
Directory DCB
Data Set Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
BLKSIZE 27920
LRECL 80
BLKSIZE 27920
Alternative PowerExchange
logging can also be used. For
more information, see the
PowerExchange Reference
Manual.
BLKSIZE 23476
Space Space
Directory DCB
Data Set Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
BLKSIZE 27920
BLKSIZE 27920
Table 5-3 describes the data sets that the PowerExchange installation allocates for change data capture:
Table 5-3. Data Sets Allocated for PowerExchange Change Data Capture
Space Space
Directory DCB
Data Set Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
Space Space
Directory DCB
Data Set Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
BLKSIZE 23476
BLKSIZE 23476
Space Space
Directory DCB
Library Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
BLKSIZE Any
valid
value
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.
Property Description
PowerExchange Prefix for the PowerExchange Agent and PowerExchange Logger. The MVS
Agent / Logger Installation Assistant appends the following characters to the prefix:
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.
Property Description
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.
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.
Storage Class for SMS storage classes for PowerExchange data sets. These fields are relevant only
Seq, VSAM, and if you use SMS. If you specify an SMS storage class, you do not need to specify
Archive 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 SMS management classes for PowerExchange data sets. These fields are
Seq, VSAM, and relevant only if you use SMS.
Archive 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, SMS data classes for PowerExchange data sets. These fields are relevant only if
VSAM, and Archive 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.
Check Point VOLSERs for the checkpoint data sets, which map to the CHKPT_VOLSERS
Volumes 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.
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.
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:
Property Description
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
LOGGER Started Name for the PowerExchange Logger started task. This name can be the same
Task ID (LLGNAME) as or different from the Logger ID value.
Default is PWXL.
Agent Name PowerExchange Agent ID value. This value must comply with the following
(AgentID) 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 name
You 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 Name for the PowerExchange Agent started task proc. This name can be the
(STARTID) same as or different from the Agent Name.
Default is PWXA.
Logger DataSet Size Number of cylinders to allocate for the PowerExchange Logger primary log, the
(in Cylinders) 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 Action that PowerExchange takes when a DB2, IMS synchronous, batch
(CCERR) 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.
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_INTERVAL
For more information about configuring Post-Log Merge, see the
PowerExchange Change Data Capture Guide for z/OS.
The suffix is used as in the data set name for USERLIB and in the XCF
members created by the PowerExchange Logger.
9. If you selected Adabas as a data source, the Select ADABAS Parameters page appears. Enter the following
information and then click Next:
Property Description
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.
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.
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.
10. If you selected Datacom as a data source, the Select Datacom Parameters page appears. Enter the following
information and then click Next:
Property Description
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 Check box that controls whether Datacom is used as a data source for
Capture change data capture. Clear this check box to not use Datacom as a data
source for change data capture.
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.
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.
11. If you selected DB2 as a data source, the Select DB2 Parameters page appears. Enter the following
information and then click Next:
Property Description
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.
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.
12. If you selected DB2 Capture, the Select DB2 CDC Parameters page appears. Enter the following
information and then click Next:
Property Description
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 Package Collection ID that is used for the DB2 ECCR packages.
Name Default is PWXCPV85.
Change Data Capture Database Name of the DB2 database to contain the DB2 ECCR capture
Name 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 Creator name for all DB2 ECCR objects that PowerExchange creates
Name 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, ..., BP16K9
32KB: BP32K, BP32K1, BP32K2, ..., BP32K9
Default 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.
Property Description
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.
3rd Party Library Data set name of the IDMS third party library.
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).
14. If you selected IDMS Change Capture, the Select IDMS CDC Parameters page appears. Enter the
following information and then click Next:
Property Description
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 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.
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.
15. If you selected IMS as a data source, the Select IMS Parameters page appears. Enter the following
information and then click Next:
Property Description
IMS Select this check box to use IMS as a data source. Clear this check
box to not use IMS as a data source.
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.
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:
Property Description
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 RECON Datasets IMS Database Recovery Control (DBRC) RECON data sets for IMS
log-based change data capture.
IMS Synchronous ECCR Data sets that will be concatenated to existing DFSESL DD
DFSESL Datasets 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.
Property Description
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.
18. If you selected VSAM as a data source, the Select VSAM Parameters page appears. Enter the following
information and then click Next:
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.
19. On the Select Additional Parameters page, enter the following information and then click Next:
Property Description
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.
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
CDC Netport tasks.
If you select this option, enter the port on which Netport will listen and
IMS Netport
the name of the Netport job.
To specify more than one Netport job, manually edit the DBMOVER
configuration member of the RUNLIB library.
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 USS directory where the ICU installation tar files are copied and
programs should be unpacked unpacked.
to
USS directory where the ICU USS directory where the ICU CNV files are to be located. This option
CNV files will be located sets the ICUDATADIR parameter in the PowerExchange DBMOVER
configuration file.
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:
Property Description
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.
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:
Property Description
IP Address / Node IP address of the MVS system on which you want to install
PowerExchange.
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.
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.
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.
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.
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.
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.
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.
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 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.
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
Installation Requirements
Review “Preparing to Install PowerExchange” on page 5 before starting the installation process.
License Key
If 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.
Step Complete
“Step 7. Add the PowerExchange Load Library to the APF List” on page 62.
“Step 9. Add the PowerExchange Load Libraries to the APF List” on page 62.
“Step 11. Upgrade Software for DB2 Data Sources” on page 63.
“Step 12. Upgrade Software for IDMS Data Sources” on page 64.
X 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.
Space Space
Directory DCB
Library Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
BINLIB PDS that contains the software CYLS (100, 20) 10 RECFM FB
libraries in TSO/E transmitted
format. LRECL 80
BLKSIZE Any
valid
value
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.
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.
3. On the Software Only Upgrade page, select one of the following options and then click Next:
Upgrade using existing data set names
Select 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 names
Select 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.
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.
Property Description
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.
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.
Property Description
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 HLQ of the current sequential and PDS data sets that you are using
PDS) 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.
7. On the Create Runlib JCL page, verify the following information and then click Next:
Property Description
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.
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.
8. On the FTP to Mainframe page, enter the following information and then click Next:
Property Description
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 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.
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.
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:
Property Description
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.
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.
5. On the Review Dataset Volume \ Unit page, enter the following information and then click Next:
Property Description
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.
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 SMS storage classes for PowerExchange data sets. These fields are relevant only
Seq, VSAM, and if you use SMS. You do not need to specify any values for Volume or Unit if you
Archive 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 SMS management classes for PowerExchange data sets. These fields are
Seq, VSAM, and relevant only if you use SMS.
Archive 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, SMS data classes for PowerExchange data sets. These fields are relevant only if
VSAM, and Archive 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.
Check Point VOLSERs for the checkpoint data sets, which map to the CHKPT_VOLSERS
Volumes for Seq, statement in the PowerExchange Condense configuration file.
VSAM, and Archive
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.
6. The Review Data Sources and Targets page appears. Optionally, select additional data sources and targets
and click Next.
8. On the Backup Datasets page, enter the following information and then click Next:
Property Description
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 HLQ of the current sequential and PDS data sets that you are using
PDS) 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.
Property Description
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.
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.
10. On the FTP to Mainframe page, enter the following information and then click Next:
Property Description
Mixed Case Password Select this option to use a mixed case password.
If you clear this option, the password is changed to uppercase.
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 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.
11. The Check FTP Status page appears and displays the status of the latest FTP transfer operation. After the
FTP transfer completes, click Next.
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.
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.
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.
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
that the Adabas ECCR uses.
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:
♦ 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.
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 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:
♦ 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.
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:
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:
XIDIDM14
Runs 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.
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.
XIDIDL10
Runs 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.
License Key
If 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.
Table 5-9. PowerExchange Service Pack Installation Task Flow and Checklist
Step Complete
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.
X 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:
Space Space
Directory DCB
Library Description Units Quantity
Blocks Characteristics
(3390) (pri,sec)
BINLIB PDS that contains the software CYLS (100, 20) 10 RECFM FB
libraries in TSO/E transmitted
format. LRECL 80
BLKSIZE Any
valid
value
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.
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 files:
♦ pbinary
♦ prunlib
4. Click OK.
Property Description
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.
5. On the Create Runlib JCL page, verify the following information and then click Next:
Property Description
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.
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.
Property Description
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 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.
7. The Check FTP Status page appears, which displays the status of the FTP transfer operation. After the FTP
completes, click Next.
1. Add a JOB card to the PRESTLIB member in the service pack RUNLIB library.
2. Submit the PRESTLIB job.
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.
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.
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:
XIDIDM14
Runs 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.
Installing PowerExchange on
Windows
This chapter includes the following topics:
♦ Overview, 73
♦ Installing PowerExchange on Windows, 74
♦ Applying a Service Pack for PowerExchange on Windows, 77
Overview
PowerExchange 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.
73
The following table shows the specific 64-bit executable that you must use by type of 64-bit Windows platform:
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
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:
Extract data using PowerExchange when the PowerCenter Run the PowerExchange 32-bit executable
Integration Service is running on a Windows 32-bit system. on the Windows 32-bit system where
PowerCenter Integration Service is
running.
Extract data using PowerExchange when the PowerCenter Run the PowerExchange 64-bit executable
Integration Service is running on a Windows 64-bit system. on the Windows 64-bit system where
PowerCenter Integration Service is
running.
PowerExchange 200 MB
Temporary files 150 MB The installer writes the files to the default temporary directory.
Description Complete?
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.
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.
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.
X 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.
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.
A
active log dataset 49 E
Adabas 50, 63 environment variables
Agent 3 Path (Windows) 76
Authorize 20
F
B FTP Binary file to AS/400 17
BINLIB 35, 53, 67
BINLIB library 36, 54, 68
I
C IASP 18, 19
Independent Auxiliary Storage Pool (IASP) 18, 19
CCT library 34 Install Library 18
CDCT library 34 installation
CDEP library 34 running (Windows) 75
condlib 17 task flow, all platforms 5
CRTPWXENV 19 testing (Windows) 77
installing PowerExchange (Windows) 74
D
datalib 17 J
DATAMAPS library 33 JOBCARD 47, 61
DBRM library 34
DBRMLIB library 33
disk space requirements L
Windows 74
LD_LIBRARY_PATH 26, 27
DS01 35
LIBPATH 26
DTLCAMAP library 34
libraries
DTLDATA library 33
BINLIB 36, 54, 68
DTLDEMO library 33
CCT 34
DTLEXPL library 33
CDCT 34
DTLINFO
CDEP 34
MVS 72
DATAMAPS 33
dtlinfo
DBRM 34
UNIX 30
DBRMLIB 33
DTLCAMAP 34
DTLDATA 33
DTLDEMO 33
DTLEXPL 33
DTLLOG 33
79
DTLMSG 33 PRILOG.DS01 library 35
LOAD 35 PRILOG.DS02 library 35
LOADCRG 34 PRILOG.DS03 library 35
LOADLIB 34 PROCLIB library 34
LOGGERNAME.ERDS01 34 PWX_HOME 26
LOGGERNAME.ERDS02 34
LOGGERNAME.USERLIB 35
PRILOG.DS01 35 Q
PRILOG.DS02 35
QSECOFR 15
PRILOG.DS03 35
PROCLIB 34
RUNLIB 36, 54, 68
SAMPLIB 35
R
SECLOG.DS01 35 RACF 31
SECLOG.DS02 35 Relational Database Directory Entry 20
SECLOG.DS03 35 RUNLIB 35, 53, 67
SR2OUT 35 RUNLIB library 36, 54, 68
SRCLIB 34
SRT2TOTAL 35
library SAVE file 17 S
license key 12, 32 SAMPLIB library 35
License Key File 18 SECLOG.DS01 library 35
LOAD library 35 SECLOG.DS02 library 35
LOADCRG library 34 SECLOG.DS03 library 35
LOADLIB library 34 Security 31
LOGGERNAME.ERDS01 library 34 SETUPBLK JCL 47
LOGGERNAME.ERDS02 library 34 SHLIB_PATH 27
LOGGERNAME.USERLIB library 35 SR2OUT library 35
SRCLIB library 34
M SRT2TOTAL library 35
supported operating systems 5
MVS Components 36, 54, 68
MVS Installation Assistant 36, 54, 69
T
O TAR File to UNIX 25
TCPADM 16
Object Ownership 20 Testing the Installation 21, 28
obtaining
license key 12
ODBC driver 76 U
operating system requirements 5 uninstalling
PowerExchange on Windows 74
P UNIX Installation
Code Pages 27
Path environment variable Oracle and UDB Considerations 27
verifying 76
PATH environment variable (UNIX) 26
PM_HOME W
UNIX Environment Variables 28 Windows installation
PowerExchange 1 overview 73
using with earlier versions of PowerCenter 13
PowerExchange ODBC drivers
installing 76
Pre-Installation Steps
MVS 66
prerequisites
for installation 12
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.