PowerExchange Interfaces for PowerCenter

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

Back Next

Configuring Batch Mode Sessions for Nonrelational Sources

When you configure a session to extract data from a nonrelational source in batch mode, you can override data map information for the source. PWXPC and PowerExchange use this information to extract the source data.

In the Task Developer, double-click a session with a nonrelational source.

On the

Mapping

tab, expand the

Sources

node in the

Transformations

tree. Then click a nonrelational source.

Under

Readers

, PowerCenter sets the PowerExchange batch reader for the source type. For nonrelational batch sources, the reader name has one of the following formats:

PowerExchange Batch Reader for database_type 
PowerExchange Reader for database_type

The database_type variable represents one of the following values:

ADABAS

ADABAS Unload Files

DB2 Datamaps

DB2 Unload Datasets

DATACOM

IDMS

IMS

Sequential Files

VSAM Files

The name of the reader cannot be altered. The only exception to this rule is for Adabas. You can use either ADABAS or ADABAS Unload Files.

Under

Connections

, in the

Value

field, select a PWX NRDB Batch connection.

Under

Properties

, set the session attributes that apply to the source type, as needed.

The following table describes these attributes:

Attribute Name	Description
Schema Name Override	Overrides the schema name in the source PowerExchange data map.
Map Name Override	Overrides the data map name of the source PowerExchange data map.
File Name	For the ADABAS Unload source type, specifies the file name of the unloaded Adabas database. Required for the ADABAS Unload source type.
ADABAS Password	For the ADABAS source type, the database password. If the ADABAS FDT for the source file is password-protected, enter the ADABAS FDT password. PowerCenter encrypts the password and displays the encrypted password in the XML file that it generates for the workflow.
Database Id Override	For the ADABAS and ADABAS Unload source types, overrides the ADABAS Database ID in the PowerExchange data map.
File Id Override	For the ADABAS and ADABAS Unload source types, overrides the Adabas file ID in the PowerExchange data map.
DB2 Sub System Id	For the DB2 Datamaps source type, overrides the DB2 subsystem ID in the PowerExchange data map.
DB2 Table name	For the DB2 Datamaps source type, overrides the DB2 table name in the PowerExchange data map.
Unload File Name	For the DB2 Unload Datasets source type, overrides the DB2 unload file name in the PowerExchange data map.
Filter Overrides	Filters the source data that PowerExchange reads based on specific conditions that you define. PWXPC adds the filter conditions in a WHERE clause on a SELECT SQL statement and then passes the SQL statement to PowerExchange for processing. You can use any filter condition syntax that PowerExchange supports for NRDB SQL. For a single-record source, use the following syntax: `filter_condition` For example, the following filter condition selects records where a column called TYPE has a value of A or D: TYPE=‘A’ or TYPE=‘D’ For a multiple-record source, use one of the following syntax alternatives: `filter_condition` `group_name1`=`filter`; `group_name2`=`filter`;... The `group_name` syntax limits the SQL query condition to a specific record in a multi-record source definition. If you do not use the `group_name` syntax, the SQL query condition applies to all records in the multi-record source definition. For example, to select only records that contain an ID column value of "DBA" for a multi-record source that has USER1 and USER2 records, specify one of the following SQL query conditions: USER1=ID=’DBA’;USER2=ID=’DBA’ ID=’DBA’ 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`
IMS Unload File Name	For the IMS source type, an IMS database unload file name. Required if you want to read source data from the backup file instead of from the IMS database. For a multiple-record write to an IMS unload file, required for both the source and target.
IMS AM Override	For the IMS source type, overrides the IMS access method in the imported data map for the source with the other available access method. The session then uses the override access method at run time. If you imported a source data map that specifies the DL/1 BATCH access method, enter O to override it with the IMS ODBA access method. For ODBA access, you must also specify the IMS PSBNAME Override and IMS PCBNAME Override attributes. If you imported a source data map that specifies the IMS ODBA access method, enter D to override it with the DL/1 BATCH access method, which provides DL/I or BMP access. You must also specify the IMS PCBNUMBER Override attribute. Before you run the session with an access method override, ensure that you complete the PowerExchange configuration tasks for the new access method. For example, if the override is DL/1 BATCH, you must configure LISTENER and NETPORT statements in the DBMOVER member and configure the netport JCL. If the override is IMS ODBA, you must perform other configuration tasks. For more information, see "IMS Data Maps" in the PowerExchange Navigator User Guide .
IMS SSID Override	For the IMS source type, if you imported an IMS ODBA data map for the source and did not override the access method, use this attribute to override the IMS subsystem ID (SSID) from the data map for the session. If you specified ODBA access as an override in the IMS AM Override session attribute, you must enter this value. An SSID is required for ODBA access. If the session has an IMS unload file source, you can use this override to point to another IMSID statement in the DBMOVER member for the purpose of changing from one DBD library to another DBD library. By using the override, you can switch DBD libraries without editing or adding any IMSID statement and restarting the PowerExchange Listener. For example, use this override to test changes that you made to a DBD library against an unload file. If you use a netport job with BMP access to IMS, you can use this override with the %IMSID substitution variable in the netport JCL to specify an IMS SSID to use for the session. This override replaces the substitution variable. By using the override with the substitution variable, you can use the same netport JCL to access multiple IMS environments, such as development, test, and production environments. An IMS SSID is not required for DL/I batch access to IMS data or for access to an IMS unload file.
IMS PSBNAME Override	For the IMS source type, if you imported an IMS ODBA data map for the source and did not override the access method, this value overrides the PSB name from the data map. If you specified ODBA access as an override in the IMS AM Override attribute, you must enter this value. A PSB name is required for ODBA access. If you use DL/I batch or BMP access and specify this override, you must also specify the PSB=%PSBNAME substitution variable in the netport JCL. The override value then replaces the substitution variable in the JCL. If you specify the PSB=%1 substitution variable instead of PSB=%PSBNAME in the netport JCL, the session uses the PSB name from the NETPORT statement, if specified. In this case, you need a separate NETPORT statement for each PSB. To avoid exceeding the limit of ten NETPORT statements in the DBMOVER member, use this override with %PSBNAME substitution variable instead. A PSB name is not used for access to an IMS source unload file.
IMS PCBNAME Override	For the IMS source type, if you imported an IMS ODBA data map for the source and did not override the access method, this value overrides the PCB name from the data map. If you specified ODBA access as an override in the IMS AM Override attribute, you must enter this value. A PCB name is required for ODBA access. A PCB name is not used for DL/I batch or BMP access or for access to an IMS unload file.
IMS PCBNUMBER Override	For the IMS source type, if you imported a DL/1 BATCH data map for the source and did not override the access method, this value overrides the PCB number from the data map. If you specified DL/I access as an override in the IMS AM Override attribute, you must enter this value. A PCB number is required for DL/I or BMP access. A PCB number is not used for IMS ODBA access or for access to an IMS unload file.
File Name Override	For the VSAM Files and Sequential Files source types, overrides the data set or file name in the PowerExchange data map. Enter the complete data set or file name. For the i5/OS, the format is: `library_name`/`file_name`. If you select the Filelist File check box, enter the name of a filelist file in this attribute. A filelist file is a list of files.
Filelist File	For the VSAM Files and Sequential Files source types, identifies the file that contains a list of files. Select this attribute only if you entered a filelist file in the File Name Override field.
SQL Query Override	Overrides the SQL query sent to PowerExchange. PWXPC replaces the default SQL query with the SQL statement that you enter and passes the SQL statement to PowerExchange for processing. You can enter any SQL statement that PowerExchange supports for NRDB SQL. For example, you can select records from table USER where a column called TYPE has a value of A or D by specifying the following SQL query override: Select ID, NAME from USER where TYPE=‘A’ or TYPE=‘D’; For a multiple-record source, use the following syntax: `group_name1`=`sql_query_override1`; `group_name2`=`sql_query_override2`;... For example, you can select only records with ID column values that contain DBA for a multi-record source with two records called USER1 and USER2 by specifying the following SQL query override: USER1=Select ID, NAME from USER1 where ID='DBA'; USER2=Select ID, NAME from USER2 where ID='DBA'; 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`
PWX Partition Strategy	For offloaded DB2 Unload, VSAM Files, and Sequential Files source types, specifies one of the following partitioning strategies: Single Connection . PowerExchange creates a single connection to the data source. Any overrides specified for the first partition are used for all partitions. With this option, if you specify any overrides for other partitions that differ from the overrides for the first partition, the session fails with an error message. Overrides Driven . If the specified overrides are the same for all partitions, PowerExchange creates a single connection to the data source. If the overrides are not identical for all partitions, PowerExchange creates multiple connections.
Flush After N Blocks	For multiple-record sources, specifies the maximum number of block flushes that can occur without any one block being flushed. For bulk multiple-record sources, by default, PWXPC flushes blocks of data only when the buffers are completely full or at end-of-file. If some record types do not have as much data as others, flushing might not occur often. In this case, the record types might not have data on the target for a long time, thereby blocking flushes on the writer side. To ensure that buffers for all record types are flushed at a regular interval, define this Flush After N Blocks session property. This property specifies the maximum number of block flushes that can occur across all record types without any one block being flushed. A value of zero disables this feature and causes flushing to occur only when blocks are full. Valid values for the property are -1 to 100000. The default value of -1 works in the following manner: For all multiple-record sources that do not use sequence fields, process the same as Flush After N Blocks = 0, which disables this feature and flushes only when blocks are full . For all multiple-record sources that use sequence fields, use Flush After N Blocks = 7 * (number of record types in the source).