Stage properties (DB2 connector)

Stage properties control session-level functions.

Name of the DB2 connector

Modify the default name of the connector. You can enter up to 255 characters. Alternatively, you can modify the name of the stage on the canvas.

Variant

This list contains the library files that provide the stage editor properties for this connector. The variant name indicates the minimum version of DB2 supported by that variant of the connector. For example, the 9.1 variant indicates support for DB2 9.1 and higher. The values for this field are application-specific, as is the default value. Select the library that you want to use for this stage.

Description

Enter an optional description of the stage.

Isolation level

Specify the degree to which the data that is being accessed by the DB2 connector stage is locked or isolated from other concurrently executing transactions, units of work, or processes. (Transactions or units or work are committed in a target stage when the end of wave marker is detected.) Choose one of the following:

Cursor stability: This is the default value. Takes exclusive locks on modified data and sharable locks on all other data. Exclusive locks are held until a commit or rollback is executed. Uncommitted changes are not readable by other transactions. Sharable locks are released immediately after the data has been processed, allowing other transactions to modify it.
Read uncommitted: Takes exclusive locks on modified data. Locks are held until a commit or rollback is executed. No other locks are taken. However, other transactions can still read but not modify the uncommitted changes.
Read stability: Takes exclusive locks on modified data and takes sharable locks on all other data. All locks are held until a commit or rollback is executed, preventing other transactions from modifying any data that has been referenced during the transaction.
Repeatable read options: Takes exclusive locks on all data. All locks are held until a commit or rollback is executed, preventing other transactions from modifying any data that has been referenced during the transaction.

For more information on the Isolation level property see Isolation levels in DB2 documentation for Linux, UNIX, and Windows.

Auto commit mode

Specifies whether the connector commits transactions manually or allows the database to commit transactions automatically at its discretion. Choose one of the following:

Off: Set this property to Off for the connector to commit transactions manually after processing the number of records specified by the Record count property.
On: Set this property to On for the database to commit transactions automatically at its discretion.

Record ordering

Specify how to process records from multiple links. Choose one of the following:

All records: All records from the first link are processed; then all records from the second link are processed; and so on.
First record: One record from each link is processed until all records from all links have been processed.
Ordered: Records are selected from the input links based on the order that you specify by using the Column name, Sort order, Null order, and Case sensitive properties.

Reoptimization

Specify the type of optimization that is done by DB2 on the SQL statements executed by the DB2 Connector stage. Choose one of the following:

None: Select None to specify no SQL statement optimization.
Once: Select Once to indicate optimization should occur the first time the SQL statement is executed.
Always: Select to indicate optimization should occur every time the SQL statement is executed.

For more information on how Reoptimization affects DB2, refer to the SQL_ATTR_REOPT connection attribute in the IBM DB2 Database for Linux, UNIX, and Windows Knowledge Center.

Lock wait mode

Specify the lock wait strategy that is used when a lock cannot be obtained immediately. Choose one of the following:

Return an SQLCODE and SQLSTATE: Select Return an SQLCODE and SQLSTATE to indicate that if a lock is encountered, DB2 should not wait and instead return a SQLCODE and SQLSTATE immediately.
Use the lock timeout database configuration: Select Use the lock timeout database configuration parameter to use the DB2's locktimeout database configuration parameter when waiting for a lock.
Wait indefinitely: Select Wait indefinitely to indicate DB2 should wait until the lock is released or a deadlock occurs.
User specified: Select User specified to enable the Lock wait time sub-property where you can specify time in seconds, between 1 and 32767, for DB2 to wait for the lock to be released. If the time expires before the lock is released, a SQLCODE and SQLSTATE is returned.

For more information on how Lock wait mode property affects DB2, refer to the details on SET CURRENT LOCK TIMEOUT statement in the IBM DB2 Database for Linux, UNIX, and Windows Knowledge Center.