PowerExchange Interfaces for PowerCenter

10.5
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Configuring Session Properties for Relational Batch Mode Sessions

To extract data from a relational source in batch mode, select a PWXPC relational database connection. Then configure the session properties.

Some session properties are unique to PowerExchange.

In the Task Developer, double-click a session with a relational source to open the session properties.

Click the

Sources

view on the

Mapping

tab.

In the

Reader

field of the

Readers

settings, select

Relational Reader

. For DB2 for z/OS, you can also select a PowerExchange Reader for DB2 Image Copy reader.

If you use the relational reader, select one of the following relational database connections:

For DB2 for i5/OS, select PWX DB2i5OS.

For DB2 for Linux, UNIX, and Windows, select PWX DB2LUW for DB2.

For DB2 for z/OS, select PWX DB2zOS.

For Microsoft SQL Server, select PWX MSSQLServer.

For Oracle, select PWX Oracle.

If you use the DB2 Image Copy reader, select a PWX NRDB Batch application connection.

Optionally, click the

Sources

view on the

Mapping

tab, and set attributes in the

Properties

area.

The following table describes the attributes that you can configure:

Attribute Name	Description
Schema Name Override	Overrides the source schema name.
Map Name Override	Overrides the source table name.
DB2 Sub System Id	Overrides the DB2 instance name in the PowerExchange data map.
Image Copy Dataset	For DB2 image copy sources, provides the image copy data set name. If not specified and the table is in a non-partitioned table space, the most current image copy data set with TYPE=FULL and SHRLEVEL=REFERENECE is used. If the table is in a partitioned table space, you must specify the Image Copy Dataset attribute.
Disable Consistency Checking	If cleared for a DB2 image copy source, PowerExchange reads the catalog to verify that the DSN of the specified image copy data set is defined with SHRLEVEL=REFERENCE and TYPE=FULL and is an image copy of the specified table. If the DSN is not defined with these properties, the session fails. If selected, PowerExchange reads the Image Copy Dataset regardless of the values of SHRLEVEL and TYPE and without verifying that the object ID in the image copy matches the object ID in the DB2 catalog.
Filter Overrides	Filters the source data that PowerExchange reads based on specified conditions. PWXPC adds filter conditions specified to the WHERE clause on the SELECT SQL statement and passes the SQL statement to PowerExchange for processing. You can use any filter condition syntax that PowerExchange supports for NRDB SQL. For more information, see the PowerExchange Reference Manual . For example, you can select records where a column called TYPE has a value of A or D by specifying the following filter condition: TYPE=‘A’ or TYPE=‘D’ If you specify both the Filter Overrides attribute and a SQL Query Override attribute that contains a filtering WHERE clause, the resulting SELECT statement contains a WHERE clause that uses the AND operator to associate the Filter Overrides filter conditions with the SQL Query Override conditions. For example: SELECT * from `schema`.`table` WHERE `Filter_Overrides_conditions` AND `SQL_Query_Override_conditions`
SQL Query Override	Overrides the SQL query sent to PowerExchange. For DB2 for z/OS data sources, PowerExchange automatically appends FOR FETCH ONLY to SQL SELECT statements. If you include FOR FETCH ONLY in the Sql Query Override attribute in the Properties area, the expression is included twice in the SELECT statement. In this case, PowerExchange issues an error. If you specify both the Filter Overrides attribute and a SQL Query Override attribute that contains a filtering WHERE clause, the resulting SELECT statement contains a WHERE clause that uses the AND operator to associate the Filter Overrides filter conditions with the SQL Query Override conditions. For example: SELECT * from `schema`.`table` WHERE `Filter_Overrides_conditions` AND `SQL_Query_Override_conditions`