Skip to main content

Db2 for z/OS operational considerations

Limitations

  • Each Striim Agent for Db2 for z/OS pipeline requires a separate Striim application. Each Striim application can read from only a single Striim Agent for Db2 for z/OS pipeline.

  • Tables without primary keys cannot be read.

  • Tables with names beginning with DB2_GENERATED_ cannot be read.

  • Due to a limitation in Striim Agent for Db2 for z/OS, Inserts and updates larger than 1 MB cannot be captured.

  • Primary key updates are not supported if the table contains an LOB or XML column. The application may halt or terminate, and data may be corrupted. However, this limitation does not apply when using a PartialRecordPolicy, which skips LOB/XML fields during processing.

  • Dropping a Striim application containing a Kafka-persisted stream being written to by Striim Agent for Db2 for z/OS will delete the associated Kafka topic. Before dropping such an application, stop the Striim Agent for Db2 for z/OS pipeline and anything else that is writing to the associated Kafka topic.

Striim Agent for Db2 for z/OS pipeline commands

See 10. Populate the Striim Agent for Db2 for z/OS configuration file for additional information.

Start a pipeline:

setupRDRS_DB2zOS.sh -a start -f <path to configuration file>

Stop a pipeline:

setupRDRS_DB2zOS.sh -a stop -f <path to configuration file>

Drop a pipeline (stop the pipeline first):

setupRDRS_DB2zOS.sh -a drop -r <Striim Agent for Db2 for z/OS repository password> -f <path to configuration file>

Get a list of all pipelines and their statuses:

setupRDRS_DB2zOS.sh -a get -r <Striim Agent for Db2 for z/OS repository password> -f <path to configuration file>

Handling schema evolution

Schema evolution must be handled manually. See Handling planned DDL changes.

Reading the Striim Agent for Db2 for z/OS Agent log

The log file is in the Striim Agent for Db2 for z/OS directory at <Striim Agent for Db2 for z/OS directory>/log/tcAgent.log.

Backing up Striim Agent for Db2 for z/OS

To be able to restore Striim Agent for Db2 for z/OS in the event of a failure, back up the Striim Agent for Db2 for z/OS directory and the PostgreSQL or Oracle repository.

Troubleshooting

Scenario

Solution

Striim Agent for Db2 for z/OS pipeline and Striim application are running but no events are appearing in the output of the external source.

Check the Striim Agent for Db2 for z/OS dashboard and the Striim Agent for Db2 for z/OS Agent log.

Striim Agent for Db2 for z/OS is having connection failures.

Check the Striim Agent for Db2 for z/OS Agent log.

Striim Agent for Db2 for z/OS pipeline does not work after stop and restart.

Rename the Striim Agent for Db2 for z/OS process and delete the files in the RDRS/tmp directory for the old process.