Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: PowerExchange Client for PowerCenter (PWXPC)
  4. Part 3: PowerExchange ODBC
  5. Appendix A: PowerExchange Interfaces for PowerCenter Tips
  6. Appendix B: Datatypes and Code Pages
  7. Appendix C: PowerExchange Interfaces for PowerCenter Troubleshooting

PowerExchange Interfaces for PowerCenter

PowerExchange Interfaces for PowerCenter

Db2 Relational Connections

Db2 Relational Connections

Configure relational connections to extract data from and load data to Db2 for z/OS, Db2 for i5/OS, and Db2 for Linux, UNIX, and Windows sources and targets in bulk data movement sessions. Also use relational connections to apply change data to Db2 relational targets in CDC sessions.
The following table describes the connection attributes for the PWX DB2zOS, PWX DB2i5OS, and PWX DB2LUW relational connection types:
Connection Attribute
Required
DB2zOS, DB2i5OS, DB2LUW Types
Description
Name
Yes
All
The name of the relational connection.
Code Page
Yes
All
The code page that the PowerCenter Integration Service uses to extract data from the source database.
In Unicode mode, PWXPC sets the code page with this value overriding any code page specification in the PowerExchange dbmover configuration file.
Location
Yes
All
The location of the source or target database as specified as specified in a NODE statement in the PowerExchange dbmover configuration file.
Database Name
Yes
All
The Db2 subsystem or database name.
User Name
Yes
All
A user name that can be used to access the database.
For databases on supported Linux, UNIX, or Windows systems, if you have enabled PowerExchange LDAP user authentication and disabled relational pass-through authentication, the user name is the enterprise user name. For more information, see the
PowerExchange Reference Manual
.
Password
Yes
All
A password for the specified user. Passwords that are less than nine characters in length are not validated.
To avoid errors that might arise due to code page differences, Informatica recommends that the password includes only those characters that are allowed for passphrases.
For DB2i5OS and DB2zOS relational connections, you can enter a valid PowerExchange passphrase instead of a password. An i5/OS passphrase can be from 9 to 31 characters in length when you use a PWXPC connection. A z/OS passphrase can be from 9 to 128 characters in length. A passphrase can contain the following characters:
  • Uppercase and lowercase letters
  • The numbers 0 to 9
  • Spaces
  • The following special characters:
    ’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?
    The first character is an apostrophe.
Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.
On z/OS, the allowable characters in the IBM IRRPHREX exit do not affect the allowable characters in PowerExchange passphrases.
On z/OS, a valid RACF passphrase can be up to 100 characters in length. PowerExchange truncates passphrases longer than 100 characters when passing them to RACF for validation.
To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER member. For more information, see "SECURITY Statement" in the
PowerExchange Reference Manual
.
Isolation Level
Yes
DB2i5OS
The commit scope of the transaction.
Valid values:
  • None
  • CS
    . Cursor stability.
  • RR
    . Repeatable Read.
  • CHG
    . Change.
  • ALL
Default is CS.
Database file overrides
No
DB2i5OS
Override for the i5/OS database file. The format is:
from_file/to_library/to_file/to_member
Where:
  • from_file
    is the file to be overridden.
  • to_library
    is the new library to use.
  • to_file
    is the file in the new library to use.
  • to_member
    is optional and is the member in the new library and file to use. If no value is specified, *FIRST is used.
You can enter up to eight unique file overrides on a single connection. A single override applies to a single source or target. When you specify multiple file overrides, include a space between each file override and enclose the entire string of file overrides in double quotation marks.
If both
Library List
and
Database file overrides
are specified and a table exists in both,
Database file overrides
takes precedence.
Library List
No
DB2i5OS
A list of the libraries that PowerExchange searches to qualify a table name for Select, Insert, Delete, or Update statements or to qualify a stored procedure name when the procedure is called for execution. PowerExchange searches the list if a table name or stored procedure name is not qualified with a schema name.
If you specify multiple libraries, separate the library names with spaces and enclose the list in double quotation marks, for example, "TGTLIB1 TGTLIB2 TGTLIB3".
If both
Library List
and
Database file overrides
are specified and a table exists in both,
Database file overrides
takes precedence.
Environment SQL
No
All
SQL commands that run in the database environment.
Compression
No
All
Select this option to compress source data during the PowerCenter session.
Encryption Type
Yes
All
The encryption type. For information about supported encryption types, see Configuring Encryption and Compression.
Default is None.
Encryption Level
No
All
The encryption level. For information about supported encryption levels, see Configuring Encryption and Compression.
Default is 1.
Pacing Size
Yes
All
The pacing size. For information about setting the pacing size, see Configuring Pacing.
Default is 0.
Interpret as Rows
No
All
Controls whether the pacing size is in number of rows.
Bulk Load
No
DB2zOS
Controls whether PowerExchange loads data to Db2 for z/OS targets with the Db2 LOAD utility. If you select this option, you can configure the remaining connection attributes that apply to the Db2 LOAD utility. Otherwise, PowerExchange ignores these attributes.
Filename
No
DB2zOS
The data set prefix that PowerExchange uses to create the temporary files that the Db2 LOAD utility uses to load data to a Db2 table.
Space
Yes
DB2zOS
Controls whether to allocate z/OS space in tracks or cylinders.
Valid values:
  • TRACK
  • CYLINDER
Default is TRACK.
Primary Space
Yes
DB2zOS
The primary space on z/OS to use for LOAD operations. Default is 0.
Secondary Space
Yes
DB2zOS
The secondary space on z/OS to use for LOAD operations. Default is 0.
Delete Temporary Files
Yes
DB2zOS
Determines how PowerExchange handles the temporary files it creates for the Db2 LOAD utility to load data into a Db2 table.
Valid values:
  • NO
    . Do not delete the temporary files.
  • BEFORE
    . Delete the temporary files before running the utility.
  • AFTER SUCCESS ONLY
    . Delete the temporary files if the utility ends successfully with return code 0.
  • AFTER
    . Delete the temporary files after the utility runs.
Default is NO.
JCL Template
Yes
DB2zOS
The name of the JCL template for the Db2 LOAD utility on the PowerExchange target system.
Default is DB2LDJCL.
CTL Template
Yes
DB2zOS
The name of the control file template for the Db2 LOAD utility on the PowerExchange on the target system.
Default is DB2LDCTL.
Load Options
Yes
DB2zOS
Indicates how the data that PowerExchange provides to the Db2 LOAD utility is loaded into a Db2 table.
Valid values:
  • RESUME
    . Generate a LOAD RESUME statement.
  • REPLACE
    . Generate a LOAD REPLACE statement.
Default is RESUME.
Mode Type
Yes
DB2zOS
Indicates how PowerExchange runs the Db2 LOAD utility to load data into a Db2 table.
Valid values:
  • TASK
    . Run the LOAD utility as a subtask under the PowerExchange Listener.
  • JOB
    . Submit a separate job to run the Db2 LOAD utility.
  • NOSUBMIT
    . Create the files and JCL to run the Db2 LOAD utility (unless
    Mode Time
    is set to
    DATAONLY
    ) but do not submit the load job. You must submit the job manually.
Default is TASK.
Mode Time
Yes
DB2zOS
Determines how PowerExchange handles the execution of the Db2 LOAD utility.
Valid values:
  • WAIT
    . Wait for the job to end before returning control to PowerCenter. This option can be specified only when the
    Mode Type
    is
    JOB
    or
    TASK
    .
  • NO WAIT
    . Return to PowerCenter without waiting for the job to end. This option can be specified only when
    Mode Type
    is set to
    JOB
    or
    NOSUBMIT
    .
  • TIMED
    . Wait the number of seconds that is specified in the
    Time
    attribute before returning control to PowerCenter. The TIMED option can be specified only when
    Mode Type
    is set to
    JOB
    .
  • DATAONLY
    . Create the data file only. Do not create the files and JCL for running the Db2 LOAD utility. Usually, this option is used when
    Mode Type
    is set to
    NOSUBMIT
    .
Default is WAIT.
  • If you enter WAIT, PowerExchange uses 99,999 seconds as the network operation timeout value instead of the value specified by the TCPIP_OP_TIMEOUT parameter of the PWX Override connection attribute. If you enter TIMED, PowerExchange adds 5 minutes to the network operation timeout value specified by the connection attribute.
  • If you enter WAIT and the submitted job fails when you run the workflow, the PowerExchange Listener on the z/OS system continues to run. To stop the Listener, perform one of the following actions:
    • Enter the following command from the z/OS operator console:
      F
      task_name
      ,STOPTASK TASKID=
      task_id
      For more information, see the "STOPTASK Command" topic in the
      PowerExchange Command Reference
      .
    • Enter the STOPTASK command in the
      Database Row Test
      dialog box of the PowerExchange Navigator. Select
      TASK_CNTL
      in the
      DB Type
      list, and select
      Stop Task
      in the
      Fetch
      box. The
      SQL Statement
      box displays
      stoptask taskid=
      . Enter a task ID.
      For more information, see the topic, "Issuing PowerExchange Listener Commands in a Database Row Test," in the
      PowerExchange Navigator User Guide
      .
Time
Yes
DB2zOS
The wait time, in seconds, that is in effect when you set
Mode Type
to
JOB
and
Mode Time
to
TIMED
.
Valid values are 1 to 99998.
Default is 0.
Convert character data to string
No
All
Controls whether character fields are converted to string fields so that embedded nulls in data are processed as spaces.
By default, this attribute is not selected.
For more information, see Converting Character Data to Strings.
Write Mode
No
All
The write mode. For information about
Write Mode
options, see Configuring Write Mode.
Default is
Confirm Write On
.
Reject File
No
All
Overrides the default prefix of PWXR for the reject file.
PowerExchange creates the reject file on the target machine when the
Write Mode
is
Asynchronous with Fault Tolerance
.
Enter PWXDISABLE to prevent creation of the reject files.
Correlation Id
No
DB2zOS
A value to use as the Db2 Correlation ID for Db2 requests.
This value overrides the value in the SESSID statement in the PowerExchange DBMOVER configuration file.
Offload Processing
No
DB2zOS
Indicates whether to use offload processing to move PowerExchange bulk data processing from the source system to the PowerCenter Integration Service machine.
Valid values:
  • No
    . Do not use offload processing.
  • Yes
    . Use offload processing.
  • Auto
    . PowerExchange determines whether to use offload processing.
Default is No.
Worker Threads
No
DB2zOS
When offload processing is enabled, specifies the number of threads that PowerExchange uses on the PowerCenter Integration Service machine to process bulk data.
For optimal performance, this value should not exceed the number of installed or available processors on the PowerCenter Integration Service machine.
Valid values are 1 through 64.
Default is 0, which disables multithreading.
Array Size
No
DB2zOS, DB2i5OS
The Db2 fetch array size, in number of rows, for Db2 bulk data movement operations that use the Db2 access method. The array size pertains to the Db2 multiple-row FETCH statements that PowerExchange uses to read data from Db2 source tables.
Valid values are from 1 through 5000. Default is 25.
For Db2 for i5/OS bulk data movement operations, Informatica recommends that you enter an array size no greater than 100.
PowerExchange dynamically lowers the array size when all the following conditions are true:
  • The table contains LOB columns.
  • The
    Array Size
    value is greater than 1.
  • Row size *
    Array Size
    is greater than 16000000 bytes.
PWX Override
No
All
PowerExchange connection overrides, separated by a semicolon. You can enter one or more of the following optional overrides:
  • APPBUFSIZE=
    app_buf_size.
    Specifies the initial size of the application buffer for the connection. Overrides the APPBUFSIZE statement in the DBMOVER configuration file.
  • CNV_ERROR_OK= {
    N
    |Y}. If you use a Db2 relational connection to write data to a Db2 target, set this parameter to Y to allow the workflow continue after a PWX-00143 message reports a DBAPI illegal null conversion error. This error occurs when the workflow tries to write null data to a target NOT NULL column. Set this parameter to N to have the workflow end abnormally when this type of error occurs. Default is N.
  • CONNECTSTRINGCODEPAGE=
    code_page
    . Code page of the characters in the connection string. Enter this override if PowerExchange issues message PWX-07610.
  • CONNSHARE={N|
    Y
    }. By default, all Db2 lookups in a workflow use the same connection, and the PowerExchange Listener performs them in a single task.
    To preserve the behavior in effect for Db2 lookups in PowerExchange releases earlier than 9.6.0, specify CONNSHARE=N.
    If the Db2 connection is used as a target in a CDC workflow, do not change the default behavior. Otherwise, internal PowerCenter state tables that require connection sharing might not be updated correctly.
    Db2 lookups that share a connection do not use offload processing, partitioning, or threading.
  • DB2TRUNCASDEL={
    N
    |Y}. Applies to DB2zOS target connections only. With the default of N, when the PowerCenter Integration Service requests a TRUNCATE statement, PowerExchange issues a TRUNCATE statement.
    If you set this override to Y, when the PowerCenter Integration Service requests a TRUNCATE statement, PowerExchange issues a DELETE statement.
    The DB2TRUNCASDEL override applies only to DB2zOS target connections. For DB2i5OS target connections, PowerExchange always issues a DELETE statement. For DB2LUW target connections, PowerExchange always issues a TRUNCATE statement.
  • LOWVALUES={Y|
    N
    }. Indicates whether PowerExchange preserves hexadecimal '0' values, called
    low values
    , in source character fields when passing these values to a PowerCenter session. Enter Y to preserve low values. When the session runs, PWXPC can write these values to a VSAM target on z/OS or to a sequential file target on Linux, UNIX, Windows, or z/OS. Overrides the LOWVALUES statement in the DBMOVER configuration file.
  • PWXNOQUOTES={
    Y
    |N}. By default, in the SQL SELECT statements that PWXPC uses to select data for session processing, PWXPC adds double-quotation marks (") around every table name and field name that includes spaces or special characters. These special characters are
    /+-=~`!%^&*()[]{}';?,< >\\|
    . If a table is identified by both a schema name and table name in the format
    schema
    .
    table_name
    , PWXPC places the quotation marks only around the "
    table_name
    " value.
    If for any reason, you cannot use quoted table names or field names in your environment, set PWXNOQUOTES to Y to override the default behavior.
  • QAQQINILIB=
    library_name
    Specify the library name on the IBM i (i5/OS) system that contains the QAQQINI query options file. If the DBMOVER configuration file on the IBM i system includes the optional QAQQINILIB statement, this override takes precedence over the value specified in the DBMOVER file. This override only applies to IBM i systems.
  • RETLOGINFOMSG={
    N
    |Y}. By default, PWXPC writes PowerExchange error and warning messages but not informational messages to the session log. If you specify RETLOGINFOMSG=Y, PWXPC writes informational messages as well as error and warning messages to the session log.
  • RTNBUFFSIZE={
    kilobytes
    |
    960
    }. The size of the buffer, in kilobytes, that is used to collect journal entries for CDC as a result of PowerExchange calls to the IBM QjoRetrieveJournalEntries API. Adjust this parameter to tune performance based on your environment.
    Valid values are 128 through 12288. Default is 960 KB.
    If you also specified the RTNBUFFSIZE parameter in the PowerExchange AS4J CAPI_CONNECTION statement, this override takes precedence for the sessions that use the Db2 connection.
  • TCPIP_OP_TIMEOUT=
    network_operation_timeout
    . A network operation timeout interval in seconds. For more information about this timeout override, see Asynchronous Network Communication.
  • TCPIP_CON_TIMEOUT=
    connection_timeout
    . A connection timeout interval in seconds. For more information about this timeout override, see Asynchronous Network Communication.
  • USE_CATALOG_METADATA={
    N
    |Y}. Specify Y to read metadata from the Db2 catalog during a Db2 bulk load session rather than issuing a SELECT statement. PowerExchange then does not require SELECT privileges on the target table to get the metadata that is required for creating the Db2 load statement.
Connection Retry Period
No
All
The number of seconds the PowerCenter Integration Service attempts to reconnect to the PowerExchange Listener after the initial connection attempt fails. If the Integration Service cannot connect to the PowerExchange Listener within the retry period, the session fails.
Default value is 0, which disables connection retries based on this PWXPC connection attribute.
PowerExchange Listener connections to source databases do not have connection resilience.

0 COMMENTS

We’d like to hear from you!