Skip to main content

Setting general connection properties

This section describes how to configure general connection properties. For an explanation of how to configure advanced connection properties, see Setting advanced connection properties.

Information note

You can also use IBM DB2 for z/OS File Channel files as a source. For more information, see Using the Qlik Replicate file channel.

To add an IBM DB2 for z/OS source endpoint to Qlik Replicate:

  1. In the Qlik Replicate Console, click Manage Endpoint Connections to open the Manage Endpoints Connections dialog box. Then click the New Endpoint Connection button. For more information on adding an endpoint to Qlik Replicate, see Defining and managing endpoints.
  2. In the Name field, type a name for your database. This can be any name that will help to identify the database being used.
  3. In the Description field, type a description that helps to identify the Microsoft SQL Server database. This is optional.
  4. Select Source as the database role.
  5. Select IBM DB2 for z/OS as the database Type.

    Information note

    When this endpoint is used as a duplicated source in a Log Stream Staging setup, select the Read changes from log stream check box and then select the relevant Log Stream Staging task from the drop-down list.

    For information on setting up and managing Log Stream Staging tasks, see Using the Log Stream.

  6. Choose one of the following:

    • Use database alias (DSN) - Specify the database alias you defined using the DB2 Configuration Assistant or the DB2 Command Line Processor.
    • Use these connection properties - If you choose this option, enter the IBM DB2 for z/OS Server (hostname or IP address), Port and Location in the designated fields.

      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 Replicate processing). In this case, the port numbers must be identical for all members.

      The Location should be the DB2 location name defined during the installation. This should be a relational database management system – under z/OS, 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 SQL CONNECT instruction, or placing it as a qualifier of a table (preceding the schema name).

      To see the location name, use “-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.

  7. Enter the User name and Password for an authorized user of the specified IBM DB2 for z/OS database. For a list of the permissions that need to be granted to this user, see Required permissions.

    If you do not know this information, consult with your IBM DB2 for z/OS database administrator (DBA).

Information note
  • This information is case sensitive

  • Make sure that the specified user has the required access privileges

  1. Provider: Leave the default unless it was changed during the driver installation. Note that this should be the same as the name specified in the ODBC Data Source Administrator.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!