(Version 9.1.0 and Hotfixes) Informatica Corporation ... Documentation/1/PWX_… · abend with...

Informatica Corporation PowerExchange(Version 9.1.0 and Hotfixes)

Cumulative Release Notes

Informatica Corporation PowerExchange Cumulative Release Notes

Version 9.1.0 and HotfixesDecember 2011

Copyright (c) 2011 Informatica Corporation. All rights reserved.

Part Number: PWX_RNC_910_0004

Table of Contents

Abstract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

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

Chapter 2: PowerExchange 9.1.0 HotFix 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

First-Time and Upgrade Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

HotFix Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Upgrade Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Rebind the DB2 for z/OS Plans and Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Upgrade Consideration for the IMS Synchronous ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

EDP DB2 Apply Consideration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3: PowerExchange 9.1.0 HotFix 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

First-Time and Upgrade Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

HotFix Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Upgrade Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Rebind the DB2 for z/OS Plan and Packages for the ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Upgrade Consideration for the IMS Synchronous ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

EDP DB2 Apply Consideration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 4: PowerExchange 9.1.0 HotFix 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14


First-Time and Upgrade Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

HotFix Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


PowerExchange 9.1.0 HotFix 1 Compatibility with PowerCenter 8.6.1 HotFix 13. . . . . . . . . . . . . . 17

Rebind the DB2 for z/OS Plan and Packages for the ECCR. . . . . . . . . . . . . . . . . . . . . . . . . . . 18


EDP DB2 Apply Consideration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18


Chapter 5: PowerExchange 9.1.0 Base Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


Table of Contents i


Advanced Encryption Standard (AES) 128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23



Chapter 6: Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

ii Table of Contents

AbstractThis document compiles the release notes that Informatica has issued to date for PowerExchange 9.1.0 and itshotfixes. The release notes are listed from latest to earliest with the 9.1.0 base release notes last.

iii

C H A P T E R 1

PowerExchange HotFix InstallationOverview

To install a PowerExchange hotfix, you can complete a first-time installation, an upgrade installation, or a hotfixinstallation. Use the install files that are listed in these release notes by installation type and operating system.

To determine which type of installation to perform, use the following criteria:

¨ If PowerExchange is not currently installed, complete a first-time installation. Use the install files that areprovided for a first-time or upgrade installation.

¨ If a PowerExchange version earlier than 9.1.0 is installed, complete an upgrade installation. Use the install filesthat are provided for a first-time or upgrade installation.

¨ If PowerExchange 9.1.0 or a 9.1.0 hotfix is currently installed, complete a hotfix installation. Use the hotfixinstall files.

PowerExchange hotfixes are cumulative. The latest hotfix includes changes from all previous hotfixes on thecurrent version.

Note: If you perform a first-time or upgrade installation on a Linux, UNIX, or Windows system, you can use alocalized version of the PowerExchange installer. When you run the installer, you get localized PowerExchangemessages. On Windows, you also get a localized version of the PowerExchange Navigator. If you copy thelocalized help files to the helpdoc folder, you can get localized help through the PowerExchange Navigator.

For more information about each installation procedure, see the latest PowerExchange Installation Guide. Forupgrade and migration considerations and software requirements, see the PowerExchange Planning Guide forInstallation and Migration.

1

C H A P T E R 2

PowerExchange 9.1.0 HotFix 3This chapter includes the following topics:

¨ Fixes, 2

¨ First-Time and Upgrade Installation Files, 4

¨ HotFix Installation Files, 5

¨ Upgrade Considerations, 5

¨ Known Limitations, 6

Fixes

CR Description

278222 When you warm start a CDC session on an HP-UX machine, the PowerExchange Listener might report a TCP/IP ACCEPT error.

278152 If a session is started with CURRENT_RESTART and processes exactly one UOW, the subsequent restartoccurs at the point of the CURRENT_RESTART for the session. The restart token values are updated onlyafter the second UOW is sent to the target.

278142 When you specify the Correlation ID connection property for a DB2 for z/OS connection in the PowerCenterWorkflow Manager or the Informatica Developer, the correlation ID is prefixed with PWX.

277866 If you cold start the IDMS log-based ECCR and it encounters any open units of work in the PowerExchangeLogger, the ECCR issues a series of error messages beginning with PWX-00999, indicating a program logicerror.With the fix, an explicit cold start using the COLDSTART=Y option now aborts any open units of work detectedon the PowerExchange logger at start up and then starts processing from the first journal encountered in thecatalog.

277023 To use multiple-row DB2 FETCH and INSERT statements when reading and writing data to DB2 tables for bulkdata movement operations, you must APF-authorize the PowerExchange LOADLIB library. Offload processingof DB2 for z/OS tables uses multiple-row FETCH and INSERT statements.

276233 If the data source In a bulk data movement session is a Windows flat that uses a line feed character as the end-of-file marker, PowerExchange returns an error message when you run the session.

276220 When the PowerExchange Navigator tries to access the PowerExchange repository on z/OS, thePowerExchange Listener subtasks abends with abend code SOC1.

2

CR Description

276073 If a PowerExchange Logger Service becomes disabled by means other than through the Administrator Consoleor the infacmd pwx command, the Administrator tool still reports the service as enabled.

275773 A heartbeat timeout occurs between the PowerExchange Listener and the associated Listener Service, causingthe PowerExchange Listener to shut down unexpectedly.

275668 If you use the DTLUCBRG utility to register tables for change data capture, you might receive the followingerror message:PWX-10652 DTLURDMO: Table table_name contains invalid characters and requires a prefix for registration.

275201 If you use an Adabas table for which you implement timezones as a data source in a bulk data movementsession, and the startup JCL does not include a //TZINFO DD statement, PowerExchange issues the followingunnumbered and undocumented error message:MVS 11 Unable to establish time zone. Any fields with the TZ option will cause error 55 subcode 30 on read

274873 When you register a DB2 for i5/OS table for CDC processing in the PowerExchange Navigator or perform adatabase row test, PowerExchange might issue the following message:PWX-00271 DBAPI Error. DB_READ failed for file AS4_META.

274587 When you extract change data in continuous extraction mode, the extraction might not switch to a newly-created PowerExchange Logger for Linux, UNIX, and Windows log file until the PowerExchange Loggerperforms another file switch.

274147 When multiple file switches occur that are not separated by at least one second, the PowerExchange Loggershuts down.

274068 When you use PWXCMD to issue commands to the PowerExchange Logger for Linux, UNIX, and Windows,and you specify a four-digit port number in the SVCNODE and CMDNODE statements in the DBMOVERconfiguration files, PWXCMD fails to connect to the PowerExchange Logger.

273316 PowerExchange does not correctly process customized ICU code pages with an internal code page numbergreater than 282.

273224 When you use standard compression, the IDMS log-based ECCR might decompress compressed dataincorrectly. In addition, if you initialize the catalog and then warm start the ECCR, a loop condition can occur.With the fix, data compressed using standard compression is now decompressed correctly. The potentiallyexpensive loop condition is now trapped, and the ECCR terminates with a logic error.

273217 When the target of a bulk data movement session is an Adabas table with a large table layout, Adabas mightabend with abend code SOC4.

271862 Because some z/OS storage was mistakenly allocated below the line, high concurrency usage of thePowerExchange Listener might abend with abend code U4093 and reason code 0000001C.

270364 When you register a DB2 for i5/OS table for CDC processing in the PowerExchange Navigator or import thetable into the PowerCenter Designer, PowerExchange might issue a message indicating an error convertingcharacter data between CCSID 1208 and CCSID 65535.

270343 In a PowerCenter workflow with a nonrelational source and target, PowerExchange always interprets ahexadecimal '0' value as the end of a string and pads the remaining length of the string with spaces whenwriting the string to the target.

269918 If you change the Field Type to BIN and click OK in the Field Properties dialog box, the PowerExchangeNavigator might crash.

Fixes 3

CR Description

268061 If you run a PowerCenter workflow on a 64-bit Windows Integration Service machine, and if the workflowincludes a PowerExchange netport job with an ODBC connection, the workflow might fail without issuing anerror message.

267445 If you configure PowerExchange to run netport jobs, the PowerExchange Listener might spawn a netport jobfor a metadata request from PowerCenter instead of creating a subtask.

260852 During Datacom table-based ECCR processing, a hang condition might occur without clear diagnosticmessages.With the fix, new optional ECCR startup parameters now provide a monitoring capabilty to detect hangsituations and greater visibility to the cleanup task. In addition, the cleanup process no longer reads past thehigh key limit and therefore avoids RC=14 or RC=61 error codes.

First-Time and Upgrade Installation FilesUse the following files from the software folder of the CD image to perform a first-time or upgrade installation ofthe PowerExchange 9.1.0 software, including the latest hotfix:

Operating System File Name

AIX (64-bit) pwx910_03_aix64.tar

HP-UX Itanium (64-bit) pwx910_03_hpux_ipf64.tar

i5/OS pwx910_03_i5os.exe

Linux x86 (32-bit) pwx910_03_linux32_x86.tar

Linux x64 Opteron, EM64T (64-bit) pwx910_03_linux_em64t.tar

Solaris SPARC (64-bit) pwx910_03_solaris_sp64.tar

Solaris Opteron, EM64T (64-bit) pwx910_03_solarisx86_64.tar

Windows x86 (32-bit) pwx910_03_win32_x86.exe

Windows x64 Opteron, EM64T (64-bit) pwx910_03_win_x64.exe

z/Linux pwx910_03_zlinux.tar

z/OS pwx910_03_zos.exe

4 Chapter 2: PowerExchange 9.1.0 HotFix 3

HotFix Installation FilesIf you have PowerExchange 9.1.0 currently installed, use the following files from the patches folder of the CDimage to install 9.1.0 HotFix 3:


AIX (64-bit) pwx910_hotfix3_aix64.tar

HP-UX Itanium (64-bit) pwx910_hotfix3_hpux_ipf64.tar

i5/OS pwx910_hotfix3_i5os.exe

Linux x86 (32-bit) pwx910_hotfix3_linux32_x86.tar

Linux x64 Opteron, EM64T (64-bit) pwx910_hotfix3_linux_em64t.tar

Solaris SPARC (64-bit) pwx910_hotfix3_solaris_sp64.tar

Solaris Opteron, EM64T (64-bit) pwx910_hotfix3_solarisx86_64.tar

Windows (32-bit) pwx910_hotfix3_win32_x86.exe

Windows x64 Opteron, EM64T (64-bit) pwx910_hotfix3_win_x64.exe

z/Linux pwx910_hotfix3_zlinux.tar

z/OS pwx910_hotfix3_zos.exe

Upgrade Considerations

Rebind the DB2 for z/OS Plans and PackagesIf you perform an upgrade installation on z/OS, you must rebind the DB2 plans and packages. If you perform ahotfix installation on z/OS, you might need to rebind the DB2 plans and packages.

If you perform an upgrade installation, rebind the DB2 plans and packages by submitting the SETUDB2U job. Thisjob runs the XIDDB210 and XIDDB225 jobs. If you do not rebind packages, problems might occur. For example, ifyou do not rebind the X029113 and X029117 packages, whenever you drop a DB2 table that contains aFIELDPROC, the DB2 ECCR abends. If you do not rebind the X029155 package, the DB2 ECCR commit/rollbackprocessor might not work correctly. Normally, you rebind the DB2 plans and packages as part of the standardupgrade procedure. For more information, see the PowerExchange Installation Guide.

If you perform a hotfix installation, you must rebind DB2 plans and packages in the following cases:

¨ If the hotfix delivers a DBRMXMIT member in BINLIB, you must rebind the DB2 plan and packages for bulkdata movement processing.

¨ If the hotfix delivers a DBRM member in BINLIB, you must rebind the DB2 ECCR plan and packages.

Before you perform the binds, use the PRESTLIB job to restore the members from the hotfix BINLIB library into thehotfix libraries, and copy the supplied replacement members into the DBRMLIB.

HotFix Installation Files 5

After you perform a hotfix installation, use one of the following jobs to perform the binds:

¨ To rebind the bulk plan only, edit job XIDDB210 to add a job card and submit the job.

¨ To rebind the ECCR plan only, edit job XIDDB225 to add a job card and submit the job.

¨ To rebind both plans, run job SETUDB2U. This job submits jobs XIDDB210 and XIDDB225.

Upgrade Consideration for the IMS Synchronous ECCRThe PowerExchange CRG.LOAD library for IMS synchronous CDC contains a new version of the BMC SoftwareCHANGE RECORDING FACILITY and DATABASE INTEGRITY PLUS components.

If you use the CRG software, after you upgrade to 9.1.0 or a 9.1.0 hotfix from an earlier release, you must run theCRGUMOD or CRGCLINK job in the hlq.SAMPLIB library again. Use the hlq.CRG.LOAD library as input.Otherwise, events such as abends might cause change capture to fail in the DLIODDCx module when the IMSsynchronous ECCR tries to capture changes for a source segment.

You do not need to perform this action if you have a supported version of the BMC Software CHANGERECORDING FACILITY or DATABASE INTEGRITY PLUS product. Use the BMC Software product instead of theCRG software. Make sure that the BMC Software product version matches or is later than the minimum supportedversion for your PowerExchange version.

For more information about the CRGUMOD and CRGCLINK jobs and the minimum supported versions for theBMC Software products, see the PowerExchange CDC Guide for z/OS.

EDP DB2 Apply ConsiderationPowerExchange 9.1.0 HotFix 1 and later includes a fix that also affects the EDP DB2 Apply processes. If you runPowerExchange and EDP from the same set of libraries on z/OS and use the EDP DB2 Apply process, you mustrebind the DB2 plan for the EDP DB2 Apply process after you upgrade to PowerExchange 9.1.0 HF1 or later fromPowerExchange 9.1.0. To rebind the plan, use the commands in the APDxxxxP and APDxxxxB members of theEDP installation JCL library, where xxxx is the DB2 instance where the DB2 Apply process runs.

Known Limitations

CR Description

279287 If a bulk data movement session includes a VSTREAM NRDB data source, the session might fail with errormessage PWX-02143.

279078 In a PowerCenter session with an i5/OS data source, PowerExchange uses the default EBCDIC sort sequenceeven if you specify an override. As a result, PowerCenter transformations such as the Joiner transformation mayfail.

269124 If you run a PowerCenter session that includes PWXPC connections, a VSAM KSDS data source, and a VSAMKSDS target, and if the source file contains packed decimal fields with spaces, the session fails.Workaround: Enable data checking for packed decimal fields, and select the option to skip bad records.

269120 To create a source or target definition in PowerCenter, you can import a VSAM source or target fromPowerExchange. If you select more than one source or target object and do not select Multi-Record Datamaps,the resulting source or target objects have no columns.


CR Description

Workaround: Import multiple-record sources or targets one at a time.

269114 A PowerCenter session might fail under the following conditions:- You use a PowerExchange ODBC connection with a VSAM source or VSAM target.- You override the source or target data set name by specifying {dtldsn=output.dsn} at Table Owner.- You run the PowerExcxhange Listener on the z/OS system using code page 1026 (Turkısh EBCDIC).

258620 On i5/OS systems, an APPBUFSIZE parameter value greater than 7.9 MB can result in a memory allocationfailure during a read or write operation.Workaround: Specify a smaller APPBUFSIZE value in the DBMOVER configuration file or in the connectiondefinition.

257540 When you run a CDC session that has a password-protected Adabas data source and that uses the CAPXRTaccess method and offload processing, the session fails.

256670 If you restart a CDC session for which you did not enable recovery, the session fails and issues error messagePWX-06734, which indicates that capture processing started in the middle of a unit of work. To enable recoveryof a CDC session, select the Resume from last checkpoint option for the Recovery Strategy session attribute.

253703 When you run a Data Services mapping that writes data to an Adabas file, the mapping might fail with a seriesof error messages that indicate an SQL insert failure. This problem occurs when the number of records that arebeing written exceeds the number or records that the Adabas buffer can hold. You cannot specify a commitinterval to control it.Workarounds: Consider increasing the NISNHQ and NH nucleus parameter values. Also, adjust the size of theprotection area of the Work data set to accommodate the possibility that one transaction adds 10,000 records.

250521 When you run a Data Services mapping that includes an Update Strategy transformation and that writes data toa nonrelational target, the mapping might fail with an error message. The message indicates that the targettable has no keys, even though the data map for the target has keys defined.

239141 PowerExchange cannot process Adabas records larger than 32 KB on UNIX and Windows, because support forAdabas ACBX is not available on these operating systems.

236465 The PowerExchange Listener CLOSE FORCE command does not cancel active Listener subtasks on i5/OS andz/OS. After a CLOSE FORCE command is issued, PowerCenter workflow tasks shut down after they read thenext record. However, PowerExchange utility tasks and PowerExchange row test tasks remain active. ThePowerExchange Listener task remains active until the utility and row test subtasks are shut down.Workaround: Use operating system commands to cancel PowerExchange row test or PowerExchange utilitytasks and the associated PowerExchange Listener task.

Known Limitations 7

C H A P T E R 3


¨ Fixes, 8

¨ Closed Enhancement Requests, 9





Fixes

CR Description

270461 If you edit the Codepage property of a DB2 data map to specify a code page that is different from the defaultand then merge the data map with an extraction map, the new code page is not assigned to the extraction map.

270201 If the active Datacom Mult-User Facility (MUF) fails during CDC processing and the workload is shifted to theshadow MUF, propagation of change data is disabled in the shadow MUF.

269639 The DELETE command of the ICUALIAS statement in the DBMOVER configuration file does not work correctlywhen the internal code page number is not between 41 and 340.

269440 When you install PowerExchange on i5/OS 5.4, the CRTPWXENV command fails. Also, PowerExchange writesan error message to the CRTPWXENV job log that indicates that the data type from the physical file was notconverted to the type specified.

269118 A PowerCenter workflow that extracts data that was captured by the Datacom table-based ECCR or the IDMSlogbased ECCR might take an excessive amount of time to read the data.

269027 When SECURITY=(0,Y) in the DBMOVER configuration file, selective sign-on authorization fails.

268642 When you run the DTLUAPPL utility to generate a restart token for a DB2 i5/OS CDC data source and specifya library name and file name that are each 10 characters in length in the DB parameter, the utility returns anerror message that indicates that the DB value is too long.

267339 When you use the CAPXRT access method and log change data from an IMS data source to aPowerExchange Logger for Linux, UNIX, or Windows, the values of any CCK_ fields are not transferredcorrectly to the Linux, UNIX, or Windows system.

8

CR Description

266990 If you delete capture registrations that have a status of History before you migrate a capture registration usingDTLURDMO, two active registrations might result on the target system.

266462 If you shut down IMS while the IMS log-based ECCR is still processing data, the ECCR might not correctlyprocess all of the data in the online log files.

265500 When you use the DTLURDMO utility to migrate a capture registration or extraction map that was created withan earlier PowerExchange release, you cannot open the migrated registration or extraction map in thePowerExchange Navigator.

265362 When you use the PowerExchange Navigator to import a COBOL copybook, the displacement and definition offields might be incorrect because the PowerExchange Navigator does not calculate the subgroup lengthscorrectly.

263214 The PowerExchange Navigator and the DTLUCBRG utility allow you to register Oracle virtual columns for CDCprocessing, but PowerExchange CDC cannot process them.

262492 If you enter only a journal name instead of a complete library/journal name value in the Journal Name attributeon an DB2i5OS application connection, workflows that use the connection fail. A message that clearlydescribes the error is not issued.

257928 If an extraction map for a source table maps array elements to multiple rows and you add a change indicator(CI) or before image (BI) column to the map, PowerExchange issues an error message when you try to savethe map.

254948 If you enable both SSL communication and selective sign-on security on Windows, selective sign-on fails.

249224 If the PowerExchange Logger for MVS stalls and no longer reads change data records from its input queue, aCICS/VSAM ECCR that is running with CCERR=CONT can cause the CICS region to enter a wait state and nolonger dispatch any work until the PowerExchange Logger resumes reading from its queue.

247658 If you select the Retrieve PWX log entries attribute on a PWX CDC application connection, the progressmessage PWX_04587 does not provide the correct count of processed records for CDC sessions that usegroup source processing.

Closed Enhancement Requests

CR Description

269233,269234

Provide support for DB2 for z/OS Version 10 CDC data sources.

268000 If you specify SECURITY=(2,x) in the DBMOVER member on a z/OS system where the PowerExchangeListener runs and set the Offload Processing attribute to Yes on a PWX CDC connection for a PowerCenterCDC session, PowerExchange now issues new messages such as PWX-03320 to notify you when theconnection fails because user credentials do not have the required SAF permissions.

Closed Enhancement Requests 9






Rebind the DB2 for z/OS Plan and Packages for the ECCRIf you use DB2 for z/OS CDC and complete a hotifix installation of 9.1.0 HotFix 2, you must rebind the DB2 planand packages for the DB2 ECCR. Edit the XIDDB225 job to add a job card and to point to the hotfix version of theDBRM libraries in the DBRMLIB concatenation. Then submit the XIDDB225 job to perform the rebind.

Note: For a hotfix installation, you need to rebind the DB2 plan and packages only if the hotfix delivers aDBRMXMIT file or DBRM file.

If you perform an upgrade, rebind the DB2 plan and packages by submitting the SETUDB2U job. This job runs theXIDDB225 job. If you do not rebind some packages, problems might occur. For example, if you do not rebind theX029113 and X029117 packages, whenever you drop a DB2 table that contains a FIELDPROC, the DB2 ECCRabends. If you do not rebind the X029155 package, the DB2 ECCR commit/rollback processor might not workcorrectly. Normally, you rebind the DB2 plan and packages as part of the standard upgrade procedure. For moreinformation, see the PowerExchange Installation Guide.





EDP DB2 Apply ConsiderationPowerExchange 9.1.0 HotFix 1 and later includes a fix that also affects the EDP DB2 Apply processes. If you runPowerExchange and EDP from the same set of libraries on z/OS and use the EDP DB2 Apply process, you mustrebind the DB2 plan for the EDP DB2 Apply process after you upgrade to PowerExchange 9.1.0 HF1 or later from

Upgrade Considerations 11

PowerExchange 9.1.0. To rebind the plan, use the commands in the APDxxxxP and APDxxxxB members of theEDP installation JCL library, where xxxx is the DB2 instance where the DB2 Apply process runs.

Known Limitations

CR Description

269124 If you run a PowerCenter session that includes PWXPC connections, a VSAM KSDS data source, and a VSAMKSDS target, and if the source file contains packed decimal fields with spaces, the session fails.Workaround: Enable data checking for packed decimal fields, and select the option to skip bad records.

269120 To create a source or target definition in PowerCenter, you can import a VSAM source or target fromPowerExchange. If you select more than one source or target object and do not select Multi-Record Datamaps,the resulting source or target objects have no columns.Workaround: Import multiple-record sources or targets one at a time.

269114 A PowerCenter session might fail under the following conditions:- You use a PowerExchange ODBC connection with a VSAM source or VSAM target.- You override the source or target data set name by specifying {dtldsn=output.dsn} at Table Owner.- You run the PowerExcxhange Listener on the z/OS system using code page 1026 (Turkısh EBCDIC).

268061 If you run a PowerCenter workflow on a 64-bit Windows Integration Service machine, and if the workflowincludes a PowerExchange netport job with an ODBC connection, the workflow might fail without issuing anerror message.

266333 When you use the DTLURDMO utility to migrate an IMS capture registration and try to change the schemaname, the migrated capture registration is not usable.

258620 On i5/OS systems, an APPBUFSIZE parameter value greater than 7.9 MB can result in a memory allocationfailure during a read or write operation.Workaround: Specify a smaller APPBUFSIZE value in the DBMOVER configuration file or in the connectiondefinition.


256670 If you restart a CDC session for which you did not enable recovery, the session fails and issues error messagePWX-06734, which indicates that capture processing started in the middle of a unit of work. To enable recoveryof a CDC session, select the Resume from last checkpoint option for the Recovery Strategy session attribute.

253703 When you run a Data Services mapping that writes data to an Adabas file, the mapping might fail with a seriesof error messages that indicate an SQL insert failure. This problem occurs when the number of records that arebeing written exceeds the number or records that the Adabas buffer can hold. You cannot specify a commitinterval to control it.Workarounds: Consider increasing the NISNHQ and NH nucleus parameter values. Also, adjust the size of theprotection area of the Work data set to accommodate the possibility that one transaction adds 10,000 records.

250521 When you run a Data Services mapping that includes an Update Strategy transformation and that writes data toa nonrelational target, the mapping might fail with an error message. The message indicates that the targettable has no keys, even though the data map for the target has keys defined.


CR Description

239141 PowerExchange cannot process Adabas records larger than 32 KB on UNIX and Windows, because support forAdabas ACBX is not available on these operating systems.

236465 The PowerExchange Listener CLOSE FORCE command does not cancel active Listener subtasks on i5/OS andz/OS. After a CLOSE FORCE command is issued, PowerCenter workflow tasks shut down after they read thenext record. However, PowerExchange utility tasks and PowerExchange row test tasks remain active. ThePowerExchange Listener task remains active until the utility and row test subtasks are shut down.Workaround: Use operating system commands to cancel PowerExchange row test or PowerExchange utilitytasks and the associated PowerExchange Listener task.

Known Limitations 13

C H A P T E R 4


¨ Fixes, 14






Fixes

CR Description

265770 ODBC connections for PowerExchange netport jobs time out prematurely. For ODBC connections,PowerExchange does not provide a means to override the default connection timeout interval.

263935 A PowerCenter workflow writes corrupted data to a target VSAM data set on z/OS. This problem occurs whenthe target definition is based on a multiple-record data map that specifies a 0x00 low value in the Record IDfield for one record type and other record ID values for other record types.

263802 On a z/OS system, the PowerExchange Agent repeatedly issues error message PWX-00351, which indicatesthat the AES encryption and decryption modules, CSNBSYE and CSNBSYD, cannot be loaded. This problemoccurs when the Integrated Cryptographic Service Facility (ICSF) is not enabled and the CSF.SCSFMOD0library that contains the CSNBSYD and CSNBSYE modules is not in the system link list.

263299 The MVS Installation Assistant does not save the fully qualified IMS DBRC RECON data set names that youenter in the Data Set 1, Data Set 2, and Data Set 3 fields on the IMS CDC Parameters page.

262738 When registering DB2 for z/OS or DB2 for i5/OS tables in the PowerExchange Navigator, if you enter somenon-English characters, such as the Danish character Æ or Unicode character "LATIN CAPITAL LETTER AE,"in a table name, PowerExchange does not create the capture registration. If you enter these characters in acolumn name, the DB2 ECCR reports a schema mismatch when it encounters the first change record for theregistered table.

262122 PowerExchange does not report the correct return code and reason code in message PWX-35100 for failedcalls to the AES encryption and decryption modules, CSNBSYE and CSNBSYD.

14

CR Description

261643 A PowerExchange bulk data movement session can read a maximum of 2.147 billion rows from a DB2 for z/OSdata source. If a source has more rows, the session stops when the limit is reached, without issuing a messagethat indicates some rows were not processed. With this fix, PowerExchange sessions can read up to 4.295billion rows before starting this count over.

261250 On z/OS, PowerExchange Agent initialization and PowerExchange Listener ping operations fail with errormessage PWX-00231, which indicates that the user ID failed signon authorization. The error occurs under thefollowing conditions:- The DBMOVER member specifies either SECURITY=(1,N) or SECURITY=(2,N).- The Integrated Cryptographic Service Facility (ICSF) is not enabled.

261119 The IDMS log-based ECCR does not periodically close and reopen its special unit of work in thePowerExchange Logger log files during periods of no change activity. Because this UOW records the logrecord with the last change, it can reduce log scanning when you restart extraction processing.

260997 An Adabas database row test fails with response code 50 if you start an Adabas nucleus without a TIMEZONEDD statement that points to the member with the list of time zones. This error occurs even if you are not usingthe local time zone.

260467 When a PowerExchange bulk data movement session runs on an Integration Service system that uses aUnicode code page, the PowerExchange Client for PowerCenter (PWXPC) truncates trailing zeroes in binarystrings in character columns. This truncation causes errors when the session writes data to Oracle targets andsome other target types.

260168 When you run the ICU makeconv utility on i5/OS to create a user-defined code page, i5/OS issues an errormessage that indicates the PMIUCBLD library or LIBPMICUUC service program is not found.

258858 If you specify the CRGNAME parameter for the DTLUCBRG utility to add capture registrations under specificregistration names and also specify either the REPLACE or REPLACEACTIVE parameter, the utility issueserror message PWX-10644, which indicates conflicting parameters. As a result, the utility cannot replaceregistrations under their original registration names.

258653 On a z/OS system with a storage limit such as REGION=100M, the DTLUCBRG utility might abend with anout-of-memory error before it processes all capture registrations.

257732 If you add a Filter transformation to an Informatica Developer mapping that has a nonrelational source and thefilter condition returns TRUE based on default behavior, the Developer tool issues an error message when youtry to preview the data.

257515 On z/OS 1.12 systems, message output for various PowerExchange components, including thePowerExchange Logger and ECCRs, is not always displayed in the EDMMSG data set. This problem is causedby a JES2 issue, which can be fixed by IBM APAR OA35182.

257476 When you drop a DB2 table that contains columns that are defined with a FIELDPROC, the DB2 ECCR mightabend.

257312 A PowerCenter CDC session might fail if you use the CAPXRT access method, offload processing, workerthreads, and SSL communication and also set the Retrieve PWX Log Entries attribute to Y on the connection.This attribute setting causes PWXPC to write PowerExchange messages to the PowerCenter session log.

256436 If you create a data map for an Adabas file that contains multiple groups and multiple redefines, data mapverification fails when you try to modify it or send it to a remote system.

254535 When a DB2 for z/OS bulk data movement session completes with a non-zero return code that indicates anerror, PWXPC does not pass the return code to PowerCenter. As a result, the session continues processinginstead of terminating.

Fixes 15

CR Description

249647 If you create a data map based on a COBOL copybook that includes large PIC +9 (n) clauses, PowerExchangegenerates datatypes for the data map fields, which correspond to the underlying field sizes of the PIC clauses.If you also select the data map option to replace bad field data with data defaults, PowerExchange errorhandling logic might fail to determine the default values to use for some of the generated field types.

206968 The CICS/VSAM ECCR prevents Open operations on registered VSAM data sets that are defined withRECOVERY(NONE).


CR Description

260353 You can specify the CRGNAME parameter for the DTLUCBRG utility to specify an entire capture registrationname when you want to replace or regenerate a capture registration under its original registration name.

242814 PowerExchange adds support for CDC sources on CICS Transaction Server (CICS/TS) version 4.1.






























PowerExchange 9.1.0 HotFix 1 Compatibility with PowerCenter 8.6.1HotFix 13

PowerExchange 9.1.0 HotFix 1 is certified for use with PowerCenter 8.6.1 HotFix 13.

HotFix Installation Files 17

Rebind the DB2 for z/OS Plan and Packages for the ECCRIf you use DB2 for z/OS CDC and upgrade PowerExchange software, rebind the DB2 plan and packages after youinstall the software. Otherwise, problems might occur. For example, if you do not rebind the X029113 andX029117 packages, whenever you drop a DB2 table that contains a FIELDPROC, the DB2 ECCR abends. Inaddition, to ensure that the DB2 ECCR commit/rollback processor works correctly, rebind the X029155 package.

Normally, you rebind the DB2 plan and packages as part of the standard upgrade or hotfix installation procedure,as described in the PowerExchange Installation Guide. In the installation step for DB2 data sources, you submitthe SETUPDB2 job, which runs the XIDDB225 job that rebinds the DB2 plan and packages.





EDP DB2 Apply ConsiderationPowerExchange 9.1.0 HotFix 1 and later includes a fix that also affects the EDP DB2 Apply processes. If you runPowerExchange and EDP from the same set of libraries on z/OS and use the EDP DB2 Apply process, you mustrebind the DB2 plan for the EDP DB2 Apply process after you upgrade to PowerExchange 9.1.0 HF1 or later fromPowerExchange 9.1.0. To rebind the plan, use the commands in the APDxxxxP and APDxxxxB members of theEDP installation JCL library, where xxxx is the DB2 instance where the DB2 Apply process runs.

Known Limitations

CR Description

258620 On i5/OS systems, an APPBUFSIZE parameter value greater than 7.9 MB can result in a memory allocationfailure during a read or write operation.Workaround: Specify a smaller APPBUFSIZE value, either in the DBMOVER configuration file or in theconnection definition.

257928 If an extraction map for a source table maps array elements to multiple rows and you add a change indicator(CI) or before image (BI) column to the map, PowerExchange issues an error message when you try to save themap.


CR Description


254948 If you enable both SSL communication and selective sign-on security on Windows, selective sign-on fails. Toenable selective sign-on security, specify the SECURITY=(0,Y) statement in the DBMOVER configuration file.

253703 When you run a Data Services mapping that writes data to an Adabas file, the mapping might fail with a seriesof error messages that indicate a SQL insert failure. This problem occurs when the number of records that arebeing written exceeds the number or records that the Adabas buffer can hold. You cannot specify a commitinterval to control it.Workarounds: Consider increasing the NISNHQ and NH nucleus parameter values. Also, adjust the size of theprotection area of the Work data set to accommodate the possibility that one transaction adds 10,000 records.

250521 When you run a Data Services mapping that includes an Update Strategy transformation and that writes to anonrelational target, the mapping might fail with an error message. The message indicates that the target tablehas no keys, even though the data map for the target has keys defined.

239141 Because support for Adabas ACBX is not available on UNIX/PC, PowerExchange cannot process Adabasrecords larger than 32 KB on UNIX and Windows.

Known Limitations 19

C H A P T E R 5

PowerExchange 9.1.0 BaseRelease

This chapter includes the following topics:

¨ Fixes, 20




Fixes

CR Description

247844 If you try to add a capture registration for a Microsoft SQL Server database that uses a Cyrillic code page andhas a collation name of greater than 30 characters, the registration fails.

246759 IBM APAR PK71816 changed the maximum length of the work area passed to DB2 EDITPROCs from 256 to512. When the smaller work area is passed, various abends occur when the DB2 ECCR calls the EDITPROC.

244651 The IMS synchronous ECCR might encounter problems capturing a DL/I delete from a HISAM database whenthe segment that is the target of the delete is in the overflow portion of the database. The problems might resultin an IMS U806 abend or infinite loop.

241191 If you have multiple CAPI connection definitions in the dbmover.cfg file on the PowerCenter client and try topreview data in the Designer for a remote source, the preview operation might fail.

241184 If you enable offload processing for a real-time extraction session for which you specify an i5/OS library or fileoverride, the sessions fails.

240264 After patch P526398 is applied, the DB2 ECCR might abend or issue message PWXEDM177588E whileprocessing a non-EA-enabled partitioned tablespace.

235951 If you import a COBOL copybook when you create a data map in the PowerExchange Navigator,PowerExchange incorrectly creates a dummy column named FILLER_REDEF_1 if it encounters a REDEFINESclause within an OCCURS clause. When you run a database row test on the data map, an error occurs.

20

CR Description

235950 A bulk data movement session that writes to a VSAM relative record data set might fail with messagePWX-00784, indicating that update mode is not supported, even though the transaction type for the PWX NRDBBatch connection is defined as insert only.

235007 During a cold start of the Datacom table-based ECCR, an inflight dummy UOW (FFFFFFFFFFFFFFFFF0000)causes the ECCR to fail.

233627 For DB2 for i5/OS CDC in real-time extraction mode, PowerExchange incorrectly sets the value of theDTL_CAPXRRN column in many change records to 2147483647 when offload processing is enabled.

233219 PowerExchange issues error message PWX-10232 during an Oracle CDC session that extracts changes incontinuous extraction mode from PowerExchange Logger for Linux, UNIX, and Windows log files.

232461 If you try to register a DB2 for i5/OS table that was created in the i5/OS SQL interface and has a long file namein mixed case, the PowerExchange registration process fails. PowerExchange expects the long file name to bein uppercase.

231543 When you run a PowerCenter session with a flat file target and a z/OS source that uses a German code pagefor the source application connection, fields that are defined as ZONED and UNZONED are converted to zeros.

230693 Oracle sends backout records for a failed update to the PowerExchange UOW Cleanser for CDC in an orderthat PowerExchange does not expect. As a result, extraction processing stops.

230539 When a CDC session tries to extract changes from a PowerExchange Logger for Linux, UNIX, or Windows logfile in continuous extraction mode, it might fail with error messages PWX-10232 and PWX-23046 because ofunnecessary checking of sequence information.

228144 In a PowerExchange Navigator database row test and in a PowerCenter session run, Hebrew characters aredisplayed in reverse order.

227871 During a change from daylight savings time to standard time, PowerExchange Condense processing fails withthe message PWX-10232, which indicates an internal error occurred.

227385 The default DB Type for database row tests should be CAPXRT.

227232 The IDMS ECCR abends with message PWX-00999 when processing a journal. The message indicates thefollowing program logic error: "UOW Hash Table - Unexpected primary AREA duplicate for run unit id."

226398 The DB2 for z/OS ECCR abends with message PWXEDM177588E when reading the catalog for a table spacedefined in a storage group that uses an extended-addressing-enabled SMS data class.

226322 When a PowerCenter workflow includes a Lookup transformation for a PowerExchange source with a !=condition in a SQL WHERE clause, PowerExchange issues an error message indicating that the != condition isnot supported.

225074 The IDMS ECCR abends with an EC6 error code, indicating a CPU usage timeout, when processing a journal.

225031 During DB2 for z/OS ECCR processing, share locks that the DB2 IFI306 interface obtains on the catalog, thework table space, and various customer table spaces are not released.

224554 IMS synchronous CDC processing abends after you apply P519776.

224547 When you enable the security feature for both the source and target PowerExchange Listeners, the DTLURDMOutility requires the same USER and PASSWORD values for both the source and target. To enable the securityfeature, set the first parameter in the SECURITY statement to 1 or 2 in the DBMOVER file.

Fixes 21

CR Description

224236 The PRESTLIB JCL that you run when installing a hotfix on z/OS does not reflect changes to DB2 for z/OSmembers in the DBRM library. As a result, a bind error occurs.

223210 In a UOW containing DDL that is tracked by the ECCR, when the DDL is rolled back to a SAVEPOINT in acommitted transaction, the DB2 ECCR might abend or issue various error messages.

222198 Some SQL Server registrations that you create with the DTLUCBRG utility do not appear in the PowerExchangeNavigator.

221990 After you restart a PowerExchange Logger for Linux, UNIX, and Windows process that ended abnormally, theprocess fails with message PWX-10232, which indicates a sequence error.

221371 Workflows might fail to restart when you define RESTART1=CURRENT_RESTART andRESTART2=CURRENT_RESTART in the restart token file.

220028 Multiple CDC sessions that use the CAPXRT access method and have Oracle sources might write the Oraclecatalogs to the log files at the same time, resulting in reduced performance and unnecessary write activity.

219964 When an Oracle database uses a Japanese code page, Oracle messages that are issued during PowerCentersessions to indicate a connection error are not translated correctly.

219776 A memory leak occurs during IMS synchronous CDC processing when units of work (UOWs) from an externalsubsystem are mixed with BMP processing in a DBCTL environment.

218743 PowerExchange does not support IMS 7 for CDC processing.

217825 PowerExchange Logger processing contains bottlenecks.

214526 If you use PowerExchange Condense or the PowerExchange Logger for Linux, UNIX, and Windows and set itsNO_DATA_WAIT parameter to a time interval, in seconds, that is less than the FILE_SWITCH_VAL timeinterval, in minutes, condense processing might become erratic.

211661 The PowerExchange Condense task might end abnormally on i5/OS if you receive the following message andenter a response other than Y or N:PWX: Error 1 on Delete of file PWX860CND2CHKPT(V0). Retry? (Y/N)

203745 If you use PWXPC with an extraction map source that contains BI or CI columns and attempt to extract changedata from full condense files that contain before and after images, PowerExchange incorrectly issues messagePWX-04548.


CR Description

243295 The PowerExchange installation program now installs the openssl.exe file on Windows 32-bit systems.

237505 PowerExchange SSL processing is significantly faster than in previous versions.

22 Chapter 5: PowerExchange 9.1.0 Base Release


Advanced Encryption Standard (AES) 128In response to customer feedback and market requirements, Informatica implemented AES-128 user ID andpassword encryption and decryption in Informatica platform products, including PowerExchange. AES-128encryption and decryption replaced PowerExchange custom encryption and decryption. The adoption of AES-128encryption and decryption is a significant advance in security for the PowerExchange product and makes theproduct compliant with many security standards, including that of the United States federal government.

On most systems, you do not have to complete any configuration task to enable AES-128 encryption anddecryption. However, on z/OS systems when SECURITY=(1,x) or (2,x) in the DBMOVER configuration file, youmust configure the Integrated Cryptographic Service Facility (ICSF). ICSF might already be configured on yoursystem, because it is required for certain IBM maintenance features.

PowerExchange encryption and decryption do not work on IBM z890/z990, z9, z10 or z196 servers if IBM has notenabled the standard CP Assist for Cryptographic Function (CPACF ) DES/TDES feature (feature code 3863).This feature is export controlled. For z800 or z900 servers, feature code 800 is required instead.





Known Limitations

CR Description

258620 On i5/OS systems, a value of APPBUFSIZE greater than 7.9 MB can result in a memory allocation failure duringa read or write operation.Workaround: Specify a smaller value for APPBUFSIZE, either in the DBMOVER configuration file or in theconnection definition.

257928 If an extraction map for a source table maps array elements to multiple rows, and you add a change indicator(CI) or before image (BI) column to the map, PowerExchange issues an error message when you try to save themap.

Upgrade Considerations 23

CR Description

257732 When you add a Filter transformation with the default setting of TRUE to an Informatica Developer mapping witha nonrelational source, the Developer tool issues an error message when you try to preview the data.Workaround: Delete the Filter transformation from the mapping.

257540 When you run a CDC session that has a password-protected Adabas data source and uses the CAPXRT accessmethod and offload processing, the session fails.

257515 On z/OS 1.12 systems, log output messages for various PowerExchange components, including thePowerExchange Logger and ECCRs, are not always displayed. The problem is a result of a a JES2 issue that isfixed by JES2 APAR OA35182.Workaround: Add an //EDMMSG DD SYSOUT=* DD statement to the JCL for the PowerExchange component.

257312 When you run a CDC session that uses the CAPXRT access method, offload processing, worker threads, andSSL communication and retrieves informational messages (RETLOGINFOMSG=Y), the session might fail.Workaround: Set RETLOGINFOMSG=N in the connection definition.

254948 If you enable both SSL communication and selective sign-on security on Windows, selective sign-on fails. Youenable selective sign-on security by including the SECURITY=(0,Y) statement in the DBMOVER configurationfile.

253703 When you run a Data Services mapping to write to an Adabas file, the mapping might fail with a series of errormessages indicating a SQL insert failure. Because it is not possible to specify the commit interval, this problemcan occur when the number of records being written exceeds the number that the Adabas buffer can hold.Workarounds: Consider increasing the NISNHQ and NH nucleus parameters. In addition, review the size of theprotection area of the WORK dataset to accommodate the possibility of 10,000 records being added in onetransaction.

250521 When you run a Data Services mapping that includes an Update Strategy transformation to write to anonrelational target, the mapping might fail with an error message indicating that the target table has no keysspecified, even though the data map for the target has keys defined.

239141 Because support for Adabas ACBX is not available on UNIX/PC, PowerExchange cannot process Adabasrecords larger than 32 KB on UNIX and Windows.

24 Chapter 5: PowerExchange 9.1.0 Base Release

C H A P T E R 6

Informatica Global CustomerSupport

You can contact a Customer Support Center by telephone or through the Online Support. Online Support requiresa user name and password. You can request a user name and password at http://mysupport.informatica.com.

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

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

Toll FreeBrazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435

Toll FreeFrance: 0805 804632Germany: 0800 5891281Italy: 800 915 985Netherlands: 0800 2300001Portugal: 800 208 360Spain: 900 813 166Switzerland: 0800 463 200United Kingdom: 0800 023 4632

Standard RateBelgium: +31 30 6022 797France: +33 1 4138 9226Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511445

Toll FreeAustralia: 1 800 151 830New Zealand: 09 9 128 901

Standard RateIndia: +91 80 4112 5738

25

http://mysupport.informatica.com

(Version 9.1.0 and Hotfixes) Informatica Corporation ... Documentation/1/PWX_… · abend with...

Documents

Transcript of (Version 9.1.0 and Hotfixes) Informatica Corporation ... Documentation/1/PWX_… · abend with...