Informatica

Corporation
PowerExchange

Version 9.5.1 HotFix 4

Release Notes
February 2014
Copyright (c) 2014 Informatica Corporation. All rights reserved.
Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
PowerExchange HotFix Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
First-Time and Upgrade Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
HotFix Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
EDP Patches in PowerExchange 9.5.1 HotFix 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Upgrade Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Avoid PowerExchange Listener Hangs on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Environment Variable Incompatibilities Between PowerExchange and PowerCenter. . . . . . . . . . . . . . . . . 10
Setting the PowerExchange Environment and Starting PowerExchange. . . . . . . . . . . . . . . . . . . . . . 11
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Introduction
This document contains important information about PowerExchange 9.5.1 HotFix 4.
For more information about the product, see the PowerExchange PDFs and online help. Informatica
updates the PowerExchange PDFs, as needed. To get the latest documentation, navigate to
PowerExchange Product Documentation from http://mysupport.informatica.com.
PowerExchange HotFix Installation Overview
To install a PowerExchange hotfix, you can complete a first-time installation, an upgrade installation, or
a hotfix installation. Use the install files that are listed in these release notes by installation type and
operating system.
PWX-RLN-951HF4-0001 1
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
are provided for a first-time or upgrade installation.
If a PowerExchange version earlier than 9.5.1 is installed, complete an upgrade installation. Use the
install files that are provided for a first-time or upgrade installation.
If PowerExchange 9.5.1 is currently installed, complete a hotfix installation. Use the hotfix install files.
PowerExchange hotfixes are cumulative. The latest hotfix includes changes from all previous hotfixes
on the current version.
Note: If you perform a first-time or upgrade installation on a Linux, UNIX, or Windows system, you can
use a localized version of the PowerExchange installer. When you run the installer, you get localized
PowerExchange messages. On Windows, you also get a localized version of the PowerExchange
Navigator. If you copy the localized help files to the helpdoc folder, you can get localized help through
the PowerExchange Navigator.
For more information about installation procedures, upgrade considerations, and software requirements,
see the latest PowerExchange Installation and Upgrade Guide.
First-Time and Upgrade Installation Files
Use the files from the software folder of the CD image to perform a first-time or upgrade installation of
the PowerExchange 9.5.1 software, including the latest hotfix.
The following table provides the installation file name for each operating system:
Operating System File Name
AIX (64-bit) pwx951_04_aix64.tar
HP-UX Itanium (64-bit) pwx951_04_hpux_ipf64.tar
i5/OS pwx951_04_i5os.exe
Linux x86 (32-bit) pwx951_04_linux32_x86.tar
Linux x64 Opteron, EM64T (64-bit) pwx951_04_linux_em64t.tar
Solaris SPARC (64-bit) pwx951_04_solaris_sp64.tar
Solaris Opteron, EM64T (64-bit) pwx951_04_solaris_x86_64.tar
Windows x86 (32-bit) pwx951_04_win32_x86.exe
Windows x64 Opteron, EM64T (64-bit) pwx951_04_win_x64.exe
z/Linux pwx951_04_zlinux.tar
z/OS pwx951_04_zos.exe
2 PWX-RLN-951HF4-0001
HotFix Installation Files
If you have PowerExchange 9.5.1 or an earlier 9.5.1 hotfix currently installed, use the files from the
patches folder of the CD image to install 9.5.1 HotFix 4.
The following table provides the installation file name for each operating system:
Operating System File Name
AIX (64-bit) pwx951_hotfix4_aix64.tar
HP-UX Itanium (64-bit) pwx951_hotfix4_hpux_ipf64.tar
i5/OS pwx951_hotfix4_i5os.exe
Linux x86 (32-bit) pwx951_hotfix4_linux32_x86.tar
Linux x64 Opteron, EM64T (64-bit) pwx951_hotfix4_linux_em64t.tar
Solaris SPARC (64-bit) pwx951_hotfix4_solaris_sp64.tar
Solaris Opteron, EM64T (64-bit) pwx951_hotfix4_solaris_x86_64.tar
Windows (32-bit) pwx951_hotfix4_win32_x86.exe
Windows x64 Opteron, EM64T (64-bit) pwx951_hotfix4_win_x64.exe
z/Linux pwx951_hotfix4_zlinux.tar
z/OS pwx951_hotfix4_zos.exe
Enhancements
The following table describes closed enhancement requests:
CR Description
364329 PowerExchange now supports for CICS Transaction Server 5.1 for CDC sessions.
PWX-RLN-951HF4-0001 3
Fixes
The following table describes fixed limitations:
CR Description
379830 The IDMS log-based ECCR ends with the following program logic error message:
PWX-00999 Program logic error. Prog="DTLAMCSP". Line=17530. P1="The
start of chain pointer is NULL". P2=-1.
This internal error occurs because the ECCR encountered an unexpected sequence of journal
records.
379639 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows fails with the following error message:
PWX-36475 ORAD: PowerExchange encountered a redo log assembly error
in a committed transaction.
379637 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows fails with one of the following error messages:
PWX-36000 ORAD: Internal error NULL pointer encountered in module
PwxOrlCmnCV:3723.
PWX-36200 ORAD: Column conversion error: [error_code] error_text for
Table name=table_name, column[column_number] segment[column_segment]
column_name. Detail Type = pwx_datatype, Oracle Type =
oracle_datatype.
The error occurs when the source table is defined with the ROWDEPENDENCIES property and is
loaded with either SQL*Loader or an INSERT INTO SELECT FROM operation, also called an
arrayed insert.
379635 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows fails with the following error message:
PWX-36046 ORAD Mbr rac_members: Log parser found unexpected error.
Changed Vector Array error.
379578 The PowerExchange Listener fails with TCP/IP BIND error messages that report the IP address is
already in use, even though the Listener port is available.
379475 The DTLURDMO utility fails to copy Microsoft SQL Server capture registrations when the
REG_COPY control statement includes the SELECT DBTYPE=MSS parameter.
377401 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows fails with the following message:
PWX-36200 ORAD: Column conversion error NULL value found for column
that is not nullable.
This problem might occur if you use Oracle 11.2.0.2 or 11.2.0.3 with the COMPATIBLE parameter
set to the current version. This problem is related to Oracle Bug 14305552, which is fixed in the
Oracle 11.2.0.4 patch set.
376934 During DB2 for Linux, UNIX, and Windows CDC processing, the PowerExchange Logger for Linux,
UNIX, and Windows might fail with error message PWX-20068 when processing a ROLLBACK on a
UPDATE operation.
4 PWX-RLN-951HF4-0001
CR Description
376926 The SNAPSHOT command of the DTLUCUDB utility fails with an internal error when processing DB2
for Linux, UNIX, and Windows source tables that were created with both the VALUE COMPRESSION
clause for value compression and the COMPRESS YES clause for row compression. In the
SYSIBM.SYSTABLES table, the COMPRESSION column has a value of B for these tables.
371999 For Microsoft SQL Server sources, the PowerExchange capture process might skip change data or
read uncommitted change data because of an internal error. In this case, the target does not receive
all of the change data of CDC interest that is stored in the SQL Server distribution database.
371904 After you install PowerExchange 9.5.1 HotFix 1 or a later hotfix, the PowerExchange Logger for
Linux, UNIX, and Windows CDCT file is converted to the new format. However, under some
circumstances, the conversion incorrectly identifies the restart point for the PowerExchange Logger.
370962 On z/OS, a PowerExchange Condense subtask fails with the PWX-06108 error message and a
U4039 abend.
370959 If you perform an uncached lookup of a DB2 for z/OS table by using a PowerExchange relational
connection, and you select Report Error for the Lookup policy on multiple match transformation
attribute, the workflow incorrectly reports a multiple-match error condition.
370202 After a write error occurs during a PowerCenter session that writes to a PowerExchange SEQ target
on Linux, UNIX or Windows, PowerExchange issues an extra PWX-31041 message with the errno
value to show the cause of the problem. PowerExchange issues this message in addition to the
standard PWX-00152 error message.
369521 Informatica Developer fails to import column metadata for a table that was created prior to DB2 for
z/OS Version 6.
369136 In Informatica Developer, the scale is dropped for decimal columns in a generated source when the
Optimizer level property is set to Normal or Full and the data source is nonrelational.
368266 If you try to restart the PowerExchange Logger for Linux, UNIX, and Windows for PowerExchange
Express CDC for Oracle processing while an Oracle RAC member is down and the archive logs are
unavailable, the PowerExchange Logger fails to restart.
367815 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows ends abnormally because of a problem with processing a backout of a DML
trigger sequence.
367573 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows ends with error message PWX-06406 and return code 9980. If the
PowerExchange Logger was processing a rollback of a partial transaction, error message
PWX-36465 is also issued.
365760 When the PowerExchange Logger for Linux, UNIX, and Windows deletes expired log files for defined
groups of tables based on the COND_CDCT_RET_P retention period, it might incorrectly delete an
open log file.
364050 If the ASM_DBREADER parameter is set to Y in the READER statement of the PowerExchange
Express CDC for Oracle pwxorad.cfg file, the log reader might stop reading data when database
activity is high and the active log file is overwritten before the archive log is available.
363973 When you import a PL/I copybook that contains unsigned zoned decimal fields into the
PowerExchange Navigator, these fields are incorrectly imported as ZONED instead of UZONED.
PWX-RLN-951HF4-0001 5
CR Description
363340 If the ASM_DBREADER parameter is set to Y in the READER statement of the PowerExchange
Express CDC for Oracle pwxorad.cfg file, the log reader might stop reading data when database
activity is high and the active log file is overwritten before the archive log is available.
361919 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux,
UNIX, and Windows tried to process a DDL change on an Oracle 11.2.0.3 materialized view that
includes a column that is defined as NOT NULL but that contains a null value. As a result, the
Logger failed and a subsequent cold start of the Logger did not succeed.
361617 If you execute a DDL ALTER TABLE DETACH PARTITION statement on a DB2 for Linux, UNIX, and
Windows database during PowerExchange CDC processing, the PowerExchange Logger for Linux,
UNIX, and Windows might end abnormally.
360552 The IDMS log-based ECCR ends with the following program logic error message:
PWX-00999 Program logic error. Prog="DTLAMCSP". Line=6791. P1="SR1
expected during processing SR4 chain but data record encountered.".
P2=-1
This internal error occurs because the ECCR encountered an unexpected sequence of journal
records.
359877 If you are using PowerExchange with PowerCenter 9.5.1 HotFix 1, 2, or 3, and the Enable High
Precision session property is set, PWXPC might zeroize some or all rows for certain numeric
columns when writing to a PowerExchange nonrelational target.
359167 When a PowerCenter PWXPC session name includes a Turkish character, the session fails with a
series of error messages that indicate a conversion error.
358212 If you specify SECURITY=(2,Y) in the DBMOVER configuration file on z/OS but the operating system
case settings are incorrect, PowerExchange writes an error message every minute to the log file to
indicate that selective sign-on authorization failed.
357967 When performing a multiple-record write to an IMS unload file for a Fast Path DEDB database in a
PowerCenter session, PowerExchange might truncate the last byte from variable length segments
that are exactly 1 byte less than the minimum length, as defined in the DBD.
353476 If you select Filter Before for the Offload Processing attribute for a source NRDB application
connection in a PowerCenter workflow that performs multiple-record writes, PowerExchange
disables offload processing and performs the processing on the z/OS source system, rather than
changing the setting to Filter After.
Also, if you select Filter After for the Offload Processing attribute for a source NRDB application
connection in a PowerCenter workflow that performs multiple-record writes to an IMS unload file,
core dump errors might occur on HP-UX 64-bit Itanium and Solaris 64-bit SPARC systems.
353195 The PowerExchange Logger Service might shut down unexpectedly with an out-of-memory error.
352920 When PowerExchange connects to a CDC source to validate metadata during a PowerCenter
session, the TCPIP_CON_TIMEOUT value in the PWX Override connection attribute is ignored.
339320 If alternative logging is enabled with the TRACING statement and PowerCenter workflows end
abnormally, the semaphores that PowerExchange uses are not removed.
310137 If you delete multiple i5/OS libraries that contain DB2 for i5/OS table instances that use the same
structure and journal and then add back these same libraries, the SNDPWXJRNE request for the
add-library operation fails to update the CDC interest list without issuing a warning.
6 PWX-RLN-951HF4-0001
EDP Patches in PowerExchange 9.5.1 HotFix 4
The PowerExchange and Enterprise Data Propagation (EDP) products have some code in common.
Although the EDP product is no longer sold, Informatica occasionally issues maintenance patches for
existing customers. The EDP patches that affect the common code are incorporated into
PowerExchange releases and hotfixes.
The following table lists the EDP patches included in PowerExchange 9.5.1 HotFix 4:
EDP Patch Number Patch Title
P664329 CCC: NEED POWEREXCHANGE TO SUPPORT
CICS/TS V5.1
P663304 CCD: PWXEDM177535W POINTING TO UOWID OF
DB2 ECCR
P661271 AGENT: PWX LISTENER HANG; EXTRACTION
TASKS ABEND S13E
P660628 LOGGER: SA03 IN EDMLIPC0 EVEN AFTER 628988
P618829 CCV: ADD DTLCCIM* TO EXCEPTION LIST
Upgrade Considerations
Avoid PowerExchange Listener Hangs on z/OS
On z/OS, the PowerExchange Listener task might hang during shutdown processing. In this situation, all
tasks that communicate with the Log Read API (LRAPI) end with abend code S13E/U0001.
To prevent this problem, before you install PowerExchange 9.5.1 HotFix 4 or a later hotfix, shut down
the PowerExchange change capture components, including the PowerExchange Agent, PowerExchange
Logger for MVS, PowerExchange Condense, and the ECCRs. To shut down the PowerExchange Agent,
you must use the DRAIN and SHUTDOWN COMPLETELY commands. Otherwise, various abends might
occur when you restart the change capture components after the hotfix installation.
PWX-RLN-951HF4-0001 7
Known Limitations
The following table describes known limitations:
CR Description
372116 The Library List attribute on a PowerCenter DB2i5OS relational connection does not work with a
Stored Procedure transformation that uses a stored procedure that exists in multiple i5/OS
libraries but that is not qualified with a schema or library name.
Workaround: Ensure that the stored procedure name is unique across all of the i5/OS libraries.
366922 When you synchronize a nonrelational data object in the Developer tool, the following limitations
apply:
- If you remove or rename an imported table in the data map, you must remove and, if applicable, reinsert the
nonrelational operation on the Overview tab before you synchronize the nonrelational object.
- Synchronization updates the properties of a nonrelational data object only if the column metadata has changed. These
changes include adding, deleting, or renaming a column or changing the data type, precision, or scale.
- If you modify a nonrelational data object by synchronizing it, you must reopen the nonrelational data object to see the
changes on the Advanced tab and in the record field properties.
350646 When you import a copybook that contains certain German-language characters, such as ' ' or
vowels with umlauts, into a PowerExchange data map, lines that contain these characters are not
imported.
Workaround: If the problematic characters appear within comments, edit the comments to remove
or replace these characters.
349138 If you set the DB2 for Linux, UNIX, and Windows logarchmeth1 parameter to OFF and the
logarchmeth2 parameter to a value other than OFF, PowerExchange issues message
PWX-20622, which warns that DB2 is not configured for archive logging. Change capture
processing continues.
347767 In the Informatica Developer tool, if you import a PowerExchange data map for a VSAM or
sequential data set source that contains optional record properties for multiple-record writes, the
import operation fails. These record properties include the parent record name, the name of a
record that the current record redefines, and whether the record is a header or trailer record.
Workaround: Create a new data map that does not include these optional properties.
337160 If you use an Informatica Data Services SQL query to view DB2 for z/OS fields that have the
TIME datatype, the Data Viewer displays the result as a time stamp. The date portion of the time
stamp is incorrectly populated with the current date instead of the default date of 1980-01-01.
331003 If you import a PL/I copybook to create a data map in the PowerExchange Navigator and enter
the Start and End values that define a column range that includes line sequence numbers, the
PowerExchange Navigator might add an extraneous "NEW_RECORD__" record and then either
fail or yield unpredictable results.
Workaround: When importing a PL/I copybook, do not define a column range or accept a default
column range that includes line sequence numbers.
322679 If you import a PowerExchange DB2 for i5/OS or DB2 for z/OS data object in the Informatica
Developer tool and PowerExchange is not in the local PATH environment variable, the import
fails with a lengthy stack dump instead of a concise error message.
Workaround: Ensure that the PowerExchange application is specified in the PATH environment
variable on the Developer tool system.
8 PWX-RLN-951HF4-0001
CR Description
306143 In the Informatica Developer tool, if you specify the Library List property for a DB2 for i5/OS
connection and the SQL that is submitted on the connection contains a table name that is quoted
to escape special characters, PowerExchange does not find the i5/OS files to process. The
quotation marks might have been generated as a result of the SQL Identifier Character and
Support Mixed-case Identifiers connection properties or manually specified in the SQL.
Workaround: For table names that do not contain special characters, set the SQL Identifier
Character connection property to None and do not select the Support Mixed-case Identifiers
connection property.
303305 If you try to import metadata for some PowerExchange sources into PowerCenter by using the
value Local for the Location connection attribute, the import operation might fail. This problem
occurs for DB2 for Linux, UNIX, and Windows, Microsoft SQL Server, Oracle, Sybase, and
PowerExchange ODBC sources.
Workaround: In the Location connection attribute, enter the node name that is defined in the
NODE statement for the PowerExchange Listener on the source system.
277298 If you create an alias for an i5/OS physical file and import the object into the Informatica
Developer, the Developer tool does not successfully import the metadata for the object.
Workaround: Import the physical file and then rename it to match the alias.
269936 When you try to add a capture registration for a Microsoft SQL Server data source, the
PowerExchange Navigator fails with a license key error. This failure occurs even if the
PowerExchange Listener is running with a license.key file that includes Microsoft SQL Server
CDC as a data source.
Workaround: Open a Service Request of Type=Shipping, and ask for a PowerExchange
Navigator license key that includes SQL Server CDC.
269124 If you run a PowerCenter session that includes PWXPC connections, a VSAM KSDS data source,
and a VSAM KSDS 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
from PowerExchange. 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.
257540 When you run a CDC session that has a password-protected Adabas data source and that uses
the CAPXRT access method with offload processing, the session fails.
253703 When you run a Data Services mapping that writes data to an Adabas file, the mapping might fail
with a series of error messages that indicate an SQL insert failure. This problem occurs when the
number of records that are being written exceeds the number or records that the Adabas buffer
can hold. You cannot specify a commit interval to control it.
Workaround: Consider increasing the NISNHQ and NH nucleus parameter values. Also, adjust
the size of the protection area of the Work data set to accommodate the possibility that one
transaction adds 10,000 records.
PWX-RLN-951HF4-0001 9
CR Description
250521 When you run a Data Services mapping that includes an Update Strategy transformation and
writes data to a nonrelational target, the mapping might fail with an error message. The message
indicates that the target table has no keys, even though the data map for the target has keys
defined.
236465 The PowerExchange Listener CLOSE FORCE command does not cancel active Listener
subtasks on i5/OS and z/OS. After a CLOSE FORCE command is issued, PowerCenter workflow
tasks shut down after they read the next record. However, PowerExchange utility tasks and
PowerExchange row test tasks remain active. The PowerExchange 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 utility tasks
and the associated PowerExchange Listener task.
Environment Variable Incompatibilities Between
PowerExchange and PowerCenter
When PowerCenter and PowerExchange are installed on the same Linux, UNIX, or Windows machine, in
certain cases, they have conflicting requirements for the PATH and LD_LIBRARY_PATH environment
variables. To run correctly in these cases, PowerExchange and PowerCenter must run in separate
environments.
This requirement applies when the PowerCenter Integration Service or PowerCenter Repository Service
runs on the same machine as one of the following PowerExchange components:
PowerExchange Listener
PowerExchange Logger for Linux, UNIX, and Windows
PowerExchange Navigator
Any PowerExchange utility
The following table describes the restrictions that apply to the PATH and LD_LIBRARY_PATH variables
in the PowerExchange and PowerCenter environments:
Environment PATH LD_LIBRARY_PATH
PowerExchange $INFA_HOME must not precede
$PWX_HOME. Otherwise, you
cannot start the PowerExchange
Listener or Logger from the
command line.
LD_LIBRARY_PATH must not contain an entry for
PowerCenter. This requirement ensures that
PowerExchange utilities pick up their libraries from
$PWX_HOME only.
PowerCenter The $PWX_HOME entry must not
precede the $INFA_HOME entry.
The $LD_LIBRARY_PATH variable definition must
include both $INFA_HOME and $PWX_HOME, and
$INFA_HOME must precede $PWX_HOME. For
example:
$INFA_HOME/server/bin:$PWX_HOME:
$LD_LIBRARY_PATH
10 PWX-RLN-951HF4-0001
To set the correct environment for PowerExchange or PowerCenter instances on the same machine, use
one of the following strategies:
Always start PowerExchange and PowerCenter using separate user accounts, and set the
environment variables appropriately for each account.
Run the pwxsettask.sh or pwxsettask.bat script each time you start a PowerExchange component.
Setting the PowerExchange Environment and Starting PowerExchange
If you run PowerExchange and PowerCenter using the same user account and need to create separate
environments for each, run the pwxsettask.sh or pwxsettask.bat script each time you start a
PowerExchange component. The script sets the PATH and LD_LIBRARY_PATH variables correctly for
PowerExchange. You can also include parameters to start certain PowerExchange components.
The following syntax descriptions are for Windows. The syntax for Linux and UNIX is different from the
syntax for Windows in the following ways:
When you run the script on Windows, you must include each parameter=value expression in double
quotation marks. On Linux and UNIX, the quotation marks are optional.
When you enter the pwxsettask command on Linux or UNIX, include the .sh extension:
pwxsettask.sh parameters
On Windows, enter the command name without the extension:
pwxsettask parameters
Note: To start a PowerExchange Listener Service or PowerExchange Logger Service in the Informatica
domain, you do not need to first run the pwxsettask.sh or pwxsettask.bat script. The Informatica domain
sets the environment variables appropriately.
PowerExchange Listener
To set the PowerExchange environment and start the PowerExchange Listener from the command line,
issue the following command:
pwxsettask dtllst node_name ["config=directory/config_file"] ["license=directory/
license_key_file"]
PowerExchange Logger for Linux, UNIX, and Windows
To set the PowerExchange environment and start the PowerExchange Logger from the command line,
issue the following command:
pwxsettask pwxccl
["coldstart={Y|N}"]
["config=path/pwx_config_file"]
["cs=path/pwxlogger_config_file"]
["license=path/license_file"]
PowerExchange Utilities
To set the PowerExchange environment and start a PowerExchange utility, issue the following
command:
pwxsettask utility_name parameter_list
PWX-RLN-951HF4-0001 11
For example, to start the DTLUCBRG utility:
pwxsettask dtlucbrg "cs=filename"
PowerExchange Navigator
To set the PowerExchange environment and start the PowerExchange Navigator:
1. Issue the following command:
pwxsettask setpwxenv
2. From the Start menu, start the PowerExchange Navigator.
Informatica Global Customer Support
You can contact a Customer Support Center by telephone or through the Online Support.
Online Support requires a user name and password. You can request a user name and password at
http://mysupport.informatica.com.
The telephone numbers for Informatica Global Customer Support are available from the Informatica web
site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.
12 PWX-RLN-951HF4-0001