WebSphere logo Classic Federation Server for z/OS, Version 9.1
WebSphere logo Classic Replication Server for z/OS, Version 9.1
WebSphere logo Classic Data Event Publisher for z/OS, Version 9.1
WebSphere logo Data Integration Classic Connector for z/OS, Version 9.1


Mapping tables for Classic replication

Use Classic Data Architect to create relational tables and views that map to data sources in supported non-relational database management systems. In IBM® WebSphere® Classic Replication Server for z/OS®, you use these tables and views as sources for the Q subscriptions that you create in ASNCLP, a command-line interface for creating and administering objects that are used in Classic replication.

Before you begin

You must perform the following tasks on the data server where the correlation service will run:

About this task

You create the relational tables and views in a project in Classic Data Architect. Then, you promote these objects to a data server.

The final step in using Classic Data Architect in Classic replication is running DDL that creates control tables in a data server where a correlation service is configured. On the Q Apply server, you create another set of control tables. You create these Q Apply control tables by using the ASN command-line program (ASNCLP). Both sets of the control tables store the definitions of the replication queue maps and Q subscriptions that you create in the ASNCLP.

Procedure

To create tables and views that you can use as sources in Classic replication:

  1. Configure Classic Data Architect by creating prerequisite objects, creating connections to data servers, setting preferences, importing reference files, and granting privileges. See Configuring Classic Data Architect.
  2. Create tables and views that you can use as sources in Q subscriptions. See Mapping data for change capture and Creating views on existing tables.
  3. Optional: Modify your tables or views. See Viewing and modifying objects for Classic replication.
  4. Generate and run DDL to promote your tables and views to a data server. See Generating DDL.
  5. Optional: If you choose not to run the DDL from Classic Data Architect but from the metadata utility, export the DDL to a remote z/OS host. See Exporting SQL to remote z/OS hosts.
  6. On the data server where you plan to run the correlation service, run the DDL that is in member CACREPSP in the SCACSAMP data set. This DDL creates the structures that store the definitions of the replication queue maps and Q subscriptions that you create. These structures are called control tables. For every Classic replication configuration, there are two sets of control tables: the control tables that you create in a data server and control tables that you create on a Q Apply server. This DDL creates the control tables that go in the data server.
    1. Use FTP to copy the DDL in a file with an SQL extension into the directory where your data design project is located. For example, if the name of your project is MyProject, the directory for the project might be (on Windows®) C:\workspace\MyProject.
    2. In Classic Data Architect, right-click the folder for the project that you copied the file into. Select Refresh. The SQL file appears in the SQL Scripts folder in the data design project that you selected.
    3. Right-click the SQL file and select Run.
    4. In the Connection Selection window, select the connection to the data server where you want to run the DDL. This data server must be configured to run a correlation service. Click Finish. You can create a new connection to a data server if a connection does not yet exist.
    5. Look in the Data Output view to verify that the DDL ran correctly.
  7. Specify the WebSphere MQ manager that you created, as well as the message queue that you created to use as the restart queue and the message queue that you created to use as the administration queue. See Specifying the WebSphere MQ objects to use for change capture.
  8. Use the ASNCLP command-line interface to create your Q Apply control tables, replication queue maps, and Q subscriptions. ASNCLP is a separate application. When you install IBM WebSphere Classic Replication Server for z/OS, you can install ASNCLP on the same Linux® or Windows system as Classic Data Architect or on a different Linux or Windows system.
Related concepts
Introduction to Classic Data Architect
Populating metadata catalogs
Viewing and modifying objects
Specifying the WebSphere MQ objects to use for change capture
Related tasks
Mapping tables and creating publications for Classic event publishing
Mapping tables for Classic federation
Adding or replacing columns in tables based on data definition files
Related reference
Column properties
Table properties
View properties


Feedback

Update icon Last updated: 2007-07-11