IBM DB2 for z/OS

This section explains how to set up an IBM DB2 for z/OS source in a data task. Before you start the data task, make sure that you have fulfilled the Prerequisites, and familiarized yourself with the Limitations and considerations.

Setting connection properties

This section describes the available connection properties. All properties are required unless otherwise indicated.

To open the connector, do the following:

1. In Connections, click Create connection.

2. Select the IBM DB2 for z/OS source connector and then provide the following settings:

Data source

• Data gateway

Select a Data Movement gateway to use for moving data.

• Server: The IP address or host name of the IBM DB2 for z/OS server.

• Port: The port through which to access the IBM DB2 for z/OS server.

  Information noteIf the Server is a parallel SysPlex and data sharing members reside on multiple LPARs, the host address may specify a DVIPA - a Dynamic Virtual IP Address (to utilize the system redundancy and load-balancing in Data Movement gateway processing). In this case, the port numbers must be identical for all members.

Account properties

• User name: The user name required to access the IBM DB2 for z/OS server.

• Password: The password required to access the IBM DB2 for z/OS server.

Database properties

The Location should be the DB2 location name defined during the installation. This should be a relational database management system under z/OS, which can be either a subsystem or a group connection. This is the logical name which serves applications in order to designate resources managed by this system, either using the SQL CONNECT instruction, or placing it as a qualifier of a table (preceding the schema name).

To see the location name, use the “-DIS DDF” DB2 command (option 7 under the DB2I panel in ISPF), or look in message DSNL004I in the job log of the <ssid>MSTR address space.

CDC properties

• To enable data capture from IBM DB2 for z/OS, the source tables need to be created as follows:

  CREATE / ALTER TABLE table-name …. DATA CAPTURE CHANGES [INCLUDE LONGVAR COLUMNS];

  You can either configure Data Movement gateway to perform this operation by selecting Automatically enable DATA CAPTURE CHANGES (requires admin privilege) in the connector settings or you can do this manually.

• Check for changes every (sec): How often to check the source database for changes.
• CDC reader UDTF name: The name of the Qlik-supplied User-Defined Table Function, which is used for CDC. Specify the two-part name using the values you have chosen for schema name, &R4ZSCNM, and the function name, &R4ZIFITF.
• UDTF result set size (MB): Specify the maximum size to be accumulated by result rows returned by the Qlik-supplied User-Defined Table Function, through CDC landing tasks using this connector. A larger result set will cause less overhead time establishing the IFI session, but will result in greater memory consumption by DB2. Specifically, because the result set is a LOB, you might need to increase the LOBVALA limit in the DB2 configuration (DSNZPARM), specifying the maximum LOB size allowed per user. Assuming all CDC tasks are configured with the same ODBC user-ID, to accommodate for all tasks running concurrently, set LOBVALA to 2 × 1024 × the following size:SUM[(i=all endpoints) : resultset size in endpoint(i) × #_tasks using endpoint(i)](Resultset size is in Mbytes, so it needs to be multiplied by 1024 to reflect LOBVALA size, which is in Kbytes).Another DSNZPARM limit, LOBVALS, specifies the total size when across all user-IDs; so, if there are multiple user IDs, you need to monitor this value as well. Note, however, that LOBVALS is specified in Mbytes, unlike LOBVALA.

SSL options

• Enable SSL: Select to enable SSL
• Keystore database file: (Optional) The keystore database file (containing your private key) on the Data Movement gateway machine. The file must be in CMS format (<filename>.kdb), which is usually the default.
• Stash file: (Optional) A file with an encrypted version of the keystore database password.
• Keystore database password: (Optional) The Keystore database file can be access using either the password that is set here or the stash file that is specified in the Stash file field.

Override CCSID mapping to code page

In the CCSID to character set mapping field enter the CCSID(s) and code page(s) in the following format (separated by commas with no spaces):

CCSID1,codepage1,CCSID2,codepage2,...

The Character set (code page) must be specified in the proper format (e.g. ibm-1148_P100-1997). For a list of valid formats, see the ICU Converter Explorer.

Internal properties

Internal properties are for special use cases and are therefore not exposed in the dialog. You should only use them if instructed by Qlik Support.

Use the and buttons to the right of the fields to add or remove properties as needed.

Supported internal properties

The following table provides a list of internal parameters that can be used as required.

Name

The display name for the source connection.

R4Z configuration dependency on host

This table in this section provides a list of R4Z configuration values, which can be set during installation or as part of the CDC service setup, or as part of the endpoint definition.