Table of Contents

Search

  1. Preface
  2. Introduction to TDM Administration
  3. User and Role Administration
  4. Security Administration
  5. System Preferences
  6. TDM Server Administration
  7. Connections
  8. Pass Phrases
  9. Global Parameters
  10. Dictionaries
  11. User-Defined Datatypes

Administrator Guide

Administrator Guide

PowerExchange DB2 for z/OS Connections

PowerExchange DB2 for z/OS Connections

You can create a PowerExchange DB2 for z/OS connection in Test Data Manager to perform data subset and data masking operations.
The following table describes the database connection properties for a PowerExchange DB2 for z/OS database:
Property
Description
Name
Required. Name of the connection. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters, start with a number, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
Connection Type
Required. The connection type. Select PWX DB2 for z/OS.
Description
The description of the connection. The description cannot exceed 255 characters.
User Name
Required. The database user name.
Password
Required. The password for the database user name.
Owner
The owner of the connection. Default is the user who creates the connection. You can change the owner of the connection.
Code Page
The code page that the Integration Service uses to extract data from the source database.
DB2 Subsystem ID
Required. Name of the DB2 subsystem.
Correlation ID
Value to use as the DB2 Correlation ID for DB2 requests. This value overrides the value that you specify for the SESSID statement in the DBMOVER configuration file.
Array Size
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 the DB2 source tables. Valid values are from 1 through 100000.
Default is 25.
You must have DB2 Version 8 new-function mode or a later DB2 version to use multiple-row FETCH statements.
Off Load Processing
For DB2 Version 8 new-function mode and later, specifies whether to use offload processing to move PowerExchange bulk data processing from the source system to the Integration Service machine. Select one of the following values:
  • No. Do not use offload processing.
  • Yes. Use offload processing.
  • Auto. PowerExchange determines whether to use offload processing.
Default is No.
Worker Threads
When offload processing is enabled, specifies the number of threads that PowerExchange uses on the Integration Service machine 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.
Environment SQL
SQL commands to set the database environment when you connect to the database. The PowerCenter Integration Service runs the connection environment SQL each time it connects to the database.
Connection Retry Period
Number of seconds the Integration Service attempts to reconnect to the data source or target if the connection fails. If the Integration Service cannot connect to the database in the retry period, the operation fails.
Default is 0.
Database Name
DB2 subsystem or database instance name.
Compression
Select to compress source data during the PowerCenter session.
Encryption Type
The type of encryption that the Integration Service uses. Select one of the following values:
  • None.
  • RC2.
  • DES.
Default is None.
Encryption Level
The level of encryption that the Integration Service uses. If you select RC2 or DES for Encryption Type, select one of the following values to indicate the encryption level.
  • 1. Uses a 56-bit encryption key for DES and RC2.
  • 2. Uses a 168-bit triple encryption key for DES. Uses a 64-bit encryption key for RC2.
  • 3. Uses a 168-bit triple encryption key for DES. Uses a 128-bit encryption key for RC2.
Ignored if you do not select an encryption type.
Default is 1.
Interpret As Rows
Interprets the pacing size as rows or kilobytes. Select to represent the pacing size in number of rows. If you clear this option, the pacing size represents kilobytes.
Default is disabled.
Convert Character Data As String
Convert character fields to string fields so that embedded nulls in data are processed as spaces.
Default is disabled.
Write Mode
Mode in which the Integration Service sends data to the PowerExchange Listener. Configure one of the following write modes:
  • Confirm Write On. Sends data to the PowerExchange Listener and waits for a response before sending more data. Select if error recovery is a priority. This option might decrease performance.
  • Confirm Write Off. Sends data to the PowerExchange Listener without waiting for a response. Use this option when you can reload the target table if an error occurs.
  • Asynchronous With Fault Tolerance. Sends data to the PowerExchange Listener without waiting for a response. This option also provides the ability to detect errors. This provides the speed of Confirm Write Off with the data integrity of Confirm Write On.
Default is Confirm Write On.
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. To prevent the creation of the reject files, specify PWXDISABLE.
PWX Override
Specifies PowerExchange connection override values, separated by semicolons, including the following overrides:
  • TCPIP_OP_TIMEOUT= network_operation_timeout ;
  • TCPIP_CON_TIMEOUT= connection_timeout
Pacing Size
Amount of data that the source system can pass to the PowerExchange Listener. Configure the pacing size if an external application, database, or the Integration Service node is a bottleneck. The lower the value, the faster the performance. Enter 0 for maximum performance.
Default is 0.
Location
Required. Location of the PowerExchange Listener node. The location is defined in the first parameter of the NODE statement in the PowerExchange dbmover.cfg configuration file.
Bulk Load
Whether PowerExchange loads data to the 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.
Default is disabled.
File Name
The data set prefix PowerExchange uses to create the temporary files needed with the DB2 LOAD utility to load data into a DB2 table.
Space
Whether to allocate MVS space in tracks or cylinders:
  • TRACK.
  • CYLINDER.
Default is TRACK.
Primary Space
Value for the primary space on MVS.
Default is 5.
Secondary Space
Value for the secondary space on MVS.
Default is 0.
Delete Temporary Files
How PowerExchange should handle the temporary files it creates with the DB2 LOAD utility to load data into a DB2 table. Select one of the following values:
  • NO. Does not delete the temporary files.
  • BEFORE. Deletes the temporary files before running the utility.
  • AFTER SUCCESS. Deletes the temporary files after running the utility if it ends with a return code 0.
  • AFTER. Deletes the temporary files after running the utility.
Default is NO.
JCL Template
The name of the JCL template for the DB2 LOAD utility on the PowerExchange target system.
Default is DB2LDJCL.
CTL Template
The name of the control file template for the DB2 LOAD utility on the PowerExchange target system.
Default is DB2LDCTL.
Load Options
How PowerExchange should handle the data with the DB2 LOAD utility to load data into a DB2 table. Select one of the following values:
  • INSERT.
  • REPLACE.
Default is INSERT.
Mode Type
How PowerExchange should run the DB2 LOAD utility to load data into a DB2 table. Select one of the following values:
  • TASK. Runs the LOAD utility as a sub-task under the PowerExchange Listener.
  • JOB. Submits a separate job to run the DB2 LOAD utility.
  • NOSUBMIT. Creates the files and JCL to run the DB2 LOAD utility, unless Mode Time is DATAONLY. Does not submit the load job. You must submit the job manually.
Default is TASK.
Mode Time
How PowerExchange handles the execution of the DB2 LOAD utility. Select one of the following values:
  • WAIT. Waits for the job to end before returning control to PowerCenter. WAIT can only be specified with Mode Type JOB or TASK.
  • NO WAIT. Returns to PowerCenter without waiting for the job to end. NO WAIT can only be specified with Mode Type JOB or NO SUBMIT.
  • TIMED. Waits the number of seconds specified in Time before returning control to PowerCenter. TIMED can only be specified with Mode Type JOB.
  • DATA ONLY creates the data file only. Does not create the files and JCL to run the DB2 LOAD utility. Usually, this option is used with a Mode Type of 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.
Time
The wait time in seconds when you select JOB for the Mode Type and TIMED for Mode Time. Valid values are 1 to 99998.
Default is 0.

0 COMMENTS

We’d like to hear from you!