Skip to main content

Db2 for z/OS initial load

Use Database Reader for initial load to create a point-in-time copy of your existing source Db2 for z/OS dataset at the target. This establishes a baseline for subsequent continuous updates.

Db2 for z/OS setup for initial load

  1. In Db2 for z/OS, create a user for use by Striim with SELECT privileges on the tables to be read and the SYSCOLUMNS, SYSTABLES, and SYSVIEWS catalog tables.

  2. In Striim, install the Db2jcc4.jar driver and Db2jcc_license.jar license file in striim/lib and restart Striim (or, if using a Forwarding Agent, install the files in agent/lib and restart the Forwarding Agent). Contact IBM for these files. They may be available through your existing Db2 Connect license.

Using TLS with Db2 for z/OS

Transport layer security is supported for the TCP connection between Database Reader and IBM Db2 for z/OS. See IBM Data Server Driver for JDBC and SQLJ support for SSL for instructions.

Database Reader properties for Db2 for z/OS sources

property

type

default value

notes

Connection Profile Name

enum

Not applicable to Db2 for z/OS in this release.

Connection URL

String

When connecting through an SSH tunnel (see Using an SSH tunnel to connect to a source or target), specify the IP address of the tunnel.

Specify jdbc:db2://<host name>:<port>/<DATABASE NAME>. See Runtime considerations when using Database Reader with Db2 sources for more information.

Create Schema

Boolean

False

If set to True, when Database Reader's output stream is the input stream of an Azure Synapse Writer, BigQuery Writer, Database Writer (for MariaDB, MariaDB Xpand, MySQL, Oracle, PostgreSQL, SQL Server, or YugabyteDB only), Databricks Writer, Fabric Data Warehouse Writer, Fabric Mirror Writer, Iceberg Writer, Snowflake Writer, or Spanner Writer target, the schema(s) and tables specified in the Tables property in the writer will be created in the target.

For example, if the Tables property in the writer is sourceschema1.%,targetschema1.%;sourceschema2.%,targetschema2.% then the schemas targetschema1 and targetschema2 will be created in the target, and all the tables in sourceschema1 and sourceschema2 will be created in the corresponding target schema.

Data types will be mapped as per Target data type support & mapping for Db2 for z/OS sources. Single-column PRIMARY KEY constraints will be replicated in the target. DEFAULT, FOREIGN KEY, NOT NULL, composite PRIMARY KEY, and UNIQUE KEY constraints will not be replicated.

If a table already exists in the target, Striim will verify that the source and target structure match. If they do not, the application will halt and log a TargetTableSchemaMismatchException.

MON output for the target tables will include a schemaCreationStatus of Pending, InProgress, Success, or Failed.

Database Provider Type

String

Default

Set to Db2 zOS. Controls which icon appears in the Flow Designer.

Excluded Tables

String

Data for any tables specified here will not be returned. For example, if Tables uses a wildcard, data from any tables specified here will be omitted. Multiple table names (separated by semicolons) and wildcards may be used exactly as for Tables.

Fetch Size

Integer

100

Sets the maximum number of records to be fetched from the database in a single JDBC method execution (see the discussion of fetchsize in the documentation for your JDBC driver).

JAAS Configuration

String

Not applicable to Db2 for z/OS in this release.

Password

encrypted password

The password for the specified user. See Encrypted passwords.

Parallel Threads

Integer

1

For Fast Snapshot Loading to Azure Synapse, BiqQuery, Databricks, Fabric Data Warehouse, Microsoft Dataverse, or Snowflake, specify the number of threads Database Reader will use. This value should not be higher than the number of tables to be read. For other targets, leave set to the default of 1.

When Database Reader is started, the tables will be distributed among the threads in round-robin fashion, then each thread will read one table at a time. When the Tables property is a list of tables, the tables are read in that order. If the Tables property uses a wildcard, the sequence is determined by the order in which the JDBC driver gives Database Reader the list of tables.

Known issue DEV-49013: the maximum number of tables supported by Parallel Threads is 255.

Query

String

Optionally, specify a single SQL SELECT statement specifying the data to return. You may query tables, aliases, synonyms, and views.

Query is not supported when Create Schema is True, Parallel Threads is greater than 1, or Restart Behavior on IL Interruption is Truncate_target_table or Replace_target_table.

When Query is specified and Tables is not, the WAEvent TableName metadata field value will be QUERY. When both Query and Tables are specified, the data specified by Query will be returned, and the Tables setting will be used only to populate the TableName field.

If the query includes a synonym containing a period, it must be enclosed in escaped quotes. For example: select * from \"synonym.name\"

If using a query when the output of a DatabaseReader source is the input of a DatabaseWriter target, specify the target table name as the value of DatabaseReader's Tables field.

Quiesce on IL Completion

Boolean

False

Restart Behavior on IL Interruption

Enum

Keep target table data

See Fast Snapshot Recovery during initial load.

Return DateTime As

String

Joda

Set to java8datetime.

SSL Config

String

Not applicable to Db2 for z/OS in this release.

Tables

String

Specify the tables, views, or materialized query tables to be read using the syntax <schema name>.<table name>.

You may specify multiple tables and views as a list separated by semicolons or with the % wildcard. For example, HR% would read all the tables whose names start with HR. You may use the % wildcard only for tables, not for schemas or databases. The wildcard is allowed only at the end of the string: for example, mydb.prefix% is valid, but mydb.%suffix is not.

If you are using the Query property, specify QUERY as the table name.

Modifying this property can interfere with recovery. If recovery is enabled for the application and it is necessary to modify the tables list, export the application (see Apps page), drop it, update the exported TQL with the new values, and import it (see Apps page).

Use Connection Profile

Boolean

False

Not applicable to Db2 for z/OS in this release.

Username

String

Specify the name of the user you created as described in Db2 for z/OS setup for initial load.

Vendor Configuration

Striing

Not applicable to Db2 for z/OS in this release.

Sample Database Reader WAEvent

For the following row:

id  first_name  last_name  phone  street          city          state  zip_code
1   Deborah     Burks      NULL   9273 Thorne AV  Orchard Park  NY     14127

The WAEvent would be similar to:

WAEvent{
  data: [1,"Deborah","Burks",null,"9273 Thorne AV","Orchard Park","NY","14127"]
  metadata: {"TableName":"BikeStores.sales.customers","ColumnCount":8,
    "OperationName":"SELECT","OPERATION_TS":1681412863364}
  userdata: null
  before: null
  dataPresenceBitMap: "fwM="
  beforePresenceBitMap: "AAA="
  typeUUID: {"uuidstring":"01edda2e-77f7-9b21-83c2-8e859085da65"}
};

The operation name for Database Reader WAEvents is always SELECT.

For more information about WAEvent, see WAEvent contents for change data.

Database Reader data type support and correspondence for Db2 for z/OS sources

See Db2 for z/OS data type support and correspondence.