Db2 for z/OS connection properties

Property	Description
Connection Name	A name for the Db2 for z/OS connection. This name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + - Spaces at the beginning or end of the name are trimmed and are not saved as part of the name. Maximum length is 100 characters. Connection names are not case sensitive.
Description	Description of the Db2 for z/OS connection. Maximum length is 4000 characters.
Type	Type of connection. For Db2 for z/OS, the type must be Db2 for z/OS.
Runtime Environment	Name of the runtime environment that contains the Secure Agent that you want to use to run mapping tasks.
Listener Location	Host name or IP address of the system where the PowerExchange Listener that processes requests for Db2 for z/OS runs. Also include the Listener port number. Enter the value in the following format, where host_name can be a host name or IP address: host_name:port_number For example: LSNR1:1467?
DB2 Subsystem ID	The Db2 subsystem or database name.
User Name	A user name that can be used to access the PowerExchange Listener when PowerExchange Listener security is enabled. For more information, see the SECURITY statement in the PowerExchange Reference Manual.
Password	Password that is associated with the user name that is specified in the User Name property.
Schema Name	Schema used for the source or target.
Code Page	The code page that the Secure Agent for the Data Integration Service uses to extract data from the source database.
Environment SQL	SQL commands that run in the database environment.
Correlation ID	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	Controls whether to use offload processing. Offload processes transfers bulk data processing from the source system to the target system. Options are: - Auto. Cloud Data Integration determines whether to use offload processing. - Filter After. Offloads the bulk data processing to the target, including the filtering of data. - Filter Before. Offloads processing to the target but continues to filter data on the source system. - No. Disables offload processing. Default is No.
Offload Threads	The number of threads that Cloud Data Integration uses to process bulk data. For optimal performance, this value should not exceed the number of installed or available processors on the Integration Service machine. Valid values are 1 through 64. Default is 0, which disables multithreading. If you use reader or writer pipeline partitioning, accept the default value of 0. You cannot use both multiple offload threads and partitioning. Not all connection types support offload threads. If the Offload Threads connection attribute for one of these connections is set to a nonzero value, processing continues without threads.
Array Size	Valid values are from 1 through 5000. Default is 25.
Replace Low Values with Spaces	Controls whether to replace embedded nulls in character data with spaces. Select this property to replace embedded nulls. By default, this property is selected.
Connection Retry Period	Number of seconds that the PowerExchange Bulk Reader tries to reconnect to the PowerExchange Listener after the initial connection attempt fails. If a connection cannot be established within the retry period, the mapping task fails. The default is 0, which disables connection retries.
Custom Properties	Custom properties that you can specify to override PowerExchange default settings. You can enter multiple properties by using a semicolon (;) as the separator. Normally, you set custom properties only at the direction of Informatica Global Customer Support. Note: These properties are equivalent to the PWX Override options for the PowerExchange Client for PowerCenter (PWXPC) Db2 for z/OS connections in PowerCenter.
Asynchronous With Fault Tolerance	Combines the speed of Confirm Write Off with the error detection of Confirm Write On. This mode buffers the data and sends it asynchronously to the PowerExchange Listener. When an SQL error occurs, PowerExchange creates a reject file on the target machine, which contains the rows that the writer could not write to the target. View the file contents to identify and correct the errors without reloading the entire table. You can also specify how to handle specific SQL return codes. To stop session execution when the session encounters non-fatal errors, specify a value greater than 0 in the Stop on errors session attribute on the Config Object tab of the Edit Tasks dialog box. Default is Confirm Write On.
Write Properties	Write Mode. Options are: - Confirm Write On. Sends data to the PowerExchange Listener and waits for a success or no success response before sending more data. This mode sends data synchronously to the PowerExchange Listener rather than buffering the data. - Confirm Write Off. Sends data asynchronously to the PowerExchange Listener by buffering the data. This mode does not wait for a success or no success response.
Reject File	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. Note: Enter PWXDISABLE to prevent creation of the reject files.