If you did not choose to use a table for change capture when you
created it, you can alter the table so that you can use it for change capture.
Restrictions
- You cannot alter a table for change capture if the table contains record
arrays.
- You cannot capture changes from tables for CA-Datacom, DB2®, and sequential
data sources.
- For CA-IDMS tables, all set relationships in the path must be owner-to-member
relationships.
- For IMS™ tables,
the following restrictions apply:
- The DBD cannot be defined as a Logical or INDEX database.
- The DBD must have IMS data capture turned on.
- A non-sequence field cannot be included in the table definition if the
DBD change-capture option of KEY is specified. IMS captures changes only to key data. Therefore,
your IMS table
can include only columns that map to that key data.
- All columns must map to the leaf segment if the IMS DBD change-capture option of DATA only
is specified.
- All columns must map to non-leaf segments if the IMS DBD change-capture option of PATH only
is specified.
- For CICS® VSAM
and native VSAM tables, the following restrictions apply:
- The VSAM file cannot reference an alternate index.
- If you want to capture changes from native VSAM, the VSAM file must be
defined as a DS data set, not as a DD data set.
- For native VSAM tables, you must define a Cross Memory URL.
Procedure
To alter a table for change capture:
- To alter a table in a data design project:
- In the Data Project Explorer, select the table.
- On the General page of the Properties view, set the DATA CAPTURE
flag to CHANGES.
- Generate the DDL for the table and run the DDL on a data server.
- To alter a table that already exists in a metadata catalog:
- In the Database Explorer, expand the connection to your data
server until you locate the table.
- Right-click the table and select Enable Change Capture.
The change to the table takes effect immediately.