RC/Extract for Db2 Modernization Guide

RC/Extract for Db2 extracts data based on SQL WHERE clause criteria. It can extract data from tables and views, and can follow referential constraints to extract related data across multiple tables. It supports various output formats, including sequential files and VSAM datasets.

The EXTRACT command is the primary command. Options include specifying the Db2 subsystem, tables to extract from, WHERE clause for filtering, and output dataset characteristics. For example: EXTRACT TABLE(table_name) WHERE(column_name = 'value') OUTFILE(dataset_name).

RC/Extract can integrate with Fast Unload for high-speed image copy access. It can also be integrated into batch jobs using JCL and REXX scripts. APIs are not directly exposed.

Configuration is primarily done through JCL parameters and control cards. There is no GUI. Parameters control dataset naming, buffer sizes, and other runtime options.

RC/Extract uses standard Db2 access methods. It connects to Db2 subsystems using the standard Db2 call attach facility (CAF).

The primary command is EXTRACT. It takes parameters for TABLE, WHERE, OUTFILE, and other options to control the extraction process. For example: EXTRACT TABLE(schema.table) WHERE(column > 100) OUTFILE(‘USER.EXTRACT.DATA’)

RC/Extract can use Fast Unload to directly read image copies, avoiding the need to access the Db2 tables directly. This improves performance and reduces the impact on Db2.

RC/Extract uses standard z/OS datasets for input and output. It supports sequential datasets and VSAM datasets.

RC/Extract can be used to create data subsets for testing or development, reducing the size of test databases and improving performance. It can also be used to archive historical data.

By extracting only the necessary data, RC/Extract reduces the storage requirements for test and development environments. It also reduces the time required for data refreshes.

RC/Extract allows users to create smaller, more manageable datasets for analysis and reporting. This improves the performance of reporting tools and reduces the time required to generate reports.

RC/Extract relies on Db2 security for data access. Users must have the necessary Db2 privileges to access the tables and views being extracted.

RC/Extract does not encrypt data during extraction. Encryption should be implemented at the dataset level using z/OS dataset encryption features.

RC/Extract logs all extraction activity to the z/OS system log. This includes the user ID, the tables extracted, and the WHERE clause used.

RC/Extract is typically run as a batch job using JCL. The JCL must include the necessary DD statements for the input and output datasets.

RC/Extract uses standard z/OS system messages for error reporting. These messages are written to the job log.

Monitoring is typically done by reviewing the job logs for errors and performance statistics. There is no dedicated monitoring interface.

Configuration parameters are specified in the JCL and control cards. These parameters control dataset naming, buffer sizes, and other runtime options.