Displays the previous page in the wizard.
Displays the next page in the wizard.
Opens the Run Now or Save SQL window, in which you can run the SQL scripts that will create your Q subscriptions, schedule the scripts to run as a task in the Task Center (unless you plan to run them on z/OS), or save the scripts to a file.
Cancels any changes that you made in the wizard and closes this window.
Specifies that you want to replicate committed changes made to one or more source tables to one or more target tables.
Specifies that you want to replicate between two servers. Committed changes made to a table on one server will be replicated to the corresponding table on the other server. You can choose which server takes precedence, or whether neither server should take precedence, if there are conflicts in the replicated data.
Specifies that you want to replicate between two servers. Committed changes made to a table on one server will be replicated to the corresponding table on the other server. Convergence of both physical tables in a logical table is guaranteed.
Specifies that you want to replicate among three or more servers. Committed changes made to a table on one server will be replicated to the corresponding tables on the other servers. Convergence of all physical tables in a logical table is guaranteed.
Specify the schema that identifies the Q Apply program that you want to apply changes to your targets.
Specify the schema that identifies the Q Capture program that you want to capture changes made to your source tables.
Displays the alias of the server on which your targets are located and where the Q Apply program will run. Click the button to open the Select Q Apply Server window.
Opens the Select Q Apply Server window.
Displays the alias of the server on which your sources are located and where the Q Capture program will run. Click the button to open the Select Q Capture Server window.
Opens the Select Q Capture Server window.
Displays the name of the replication queue map that will allow the Q Capture and Q Apply programs to communicate. You should use one replication queue map for a group of Q subscriptions that are logically related to each other, such as Q subscriptions whose target tables share referential integrity constraints. Click the button to open the Select Replication Queue Map window.
Opens the Select Replication Queue Map window.
Opens the Select Tables window.
Removes the selected table from the list of tables.
Lists the tables that you have chosen to use as source tables.
Specifies that you want to create a new target table for the Q subscription.
Type the schema or user ID to use when creating the table. See "Naming rules for Q replication and event publishing objects" in the DB2 Information Center if you need to know the maximum number of characters allowed for the schema of target tables.
Type the name that you want to give to the table. See "Naming rules for Q replication and event publishing objects" in the DB2 Information Center if you need to know the maximum number of characters allowed in the name of target tables.
Indicates whether the columns in the target table will have the same names as the columns in the source table. You can change the names of the columns that will be created in the target table by clicking the button to the right.
Opens a window that lets you change the names of the columns that will be created in the target table.
Displays the name of the table space in which the target table will be created. Click the button to open the Select Table Space window.
Opens the Select Table Space window. You can select an existing table space or create a new one.
Specifies that you want the target in your Q subscription to be an existing table on the Q Apply server.
Displays the name of the existing table that you want to use as the target in your Q subscription. Click the button to open the Select Target window.
Opens the Select Target window so that you can select an existing table to use as the target in your Q subscription.
Specifies that you want the target in your Q subscription to be a stored procedure. The stored procedure must already exist and be registered on the Q Apply server.
Displays the name of the stored procedure that you want to use as the target in your Q subscription. Click the button to open the Select Stored Procedure window.
Opens the Select Stored Procedure window so that you can select a stored procedure to use as the target in your Q subscription.
Specifies that the target for your Q subscription will be a consistent-change-data (CCD) table.
Displays the value of the condensed and complete properties for the CCD target table. Click the button to change these properties.
Opens the CCD Properties window so that you can specify settings for the CCD target table.
Specifies that you want to use an existing table as the Q subscription target.
Displays the name of an existing table. Click the button to search for a different existing table to use as the target table.
Opens a window so that you can search for an existing CCD table to use as the target table for the Q subscription.
Displays the value of the condensed and complete properties for the CCD target table. Click the button to change these properties.
Opens the CCD Properties window so that you can specify settings for the CCD target table.
Specifies that you want the Replication Center to create a new table as the Q subscription target.
Opens the Manage Target Object Profiles notebook so that you can modify the profile for target objects on the Q Apply server.
Specifies that the targets for your Q subscriptions will be tables on the Q Apply server.
Specifies that the targets for your Q subscriptions will be consistent-change-data (CCD) tables.
Displays the value of the condensed and complete properties for the CCD target table. Click the button to change these properties.
Opens a window so that you can specify properties for the CCD target tables.
Tells whether all columns or only a subset of columns from the source table will be replicated. Click the button to open the Select Columns window if you want to change the selection of columns to replicate. The Replication Center does not support column subsetting for Classic replication. For Classic, you can review which columns are included in the Q subscription by clicking the Column mapping button.
Opens the Select Columns window so that you can change the selection of source columns to replicate.
Tells whether or not you have selected columns to use a unique index or primary key for the target table. If your target is a stored procedure, select the source columns that match the key parameters in the stored procedure. Click the button to open the Select Index/Primary Key window to select columns.
Opens the Select Index/Primary Key window so that you can choose the columns of the target table that you want to use as a unique index or primary key. If your target is a stored procedure, select the source columns that match the key parameters in the stored procedure.
Tells whether all rows or only a subset of rows from the source table will be replicated. Click the button to open the Select Rows window if you want to change the selection of rows to replicate. The Replication Center does not support row subsetting for Classic replication.
Opens the Select Rows window so that you can change the selection of source rows to replicate.
Tells how source columns are mapped to columns in the target table or stored procedure parameters. When this wizard page first opens, the Replication Center tries to map the columns or columns and parameters together according to the rule displayed here. If the Replication Center cannot map all of the columns according to the rule and displays the message "Unmapped columns remaining" in this field, click the button to open the Column Mapping window and map the remaining columns yourself. You might also want to open the Column Mapping window if you want to change the column mapping rule.
Opens the Column Mapping window.
Tells whether or not you or the Replication Center have selected columns for the unique index or primary key of the target table. If your target is a stored procedure, select the source columns that match the key parameters in the stored procedure. Click the button to open the Select Index/Primary Key window to see what columns the Replication Center has recommended for the index or primary key or to select columns if the Replication Center cannot make a recommendation.
The Q Apply program needs a unique index or primary key on all target tables so that it can match rows in a target table with replicated data before it applies that data or so that it knows to insert new rows.
Opens the Select Index/Primary Key window so that you can choose the columns of the target table that you want to use as a unique index or primary key. If your target is a stored procedure, select the source columns that match the key parameters in the stored procedure.
Displays the alias of one of the servers that you want to participate in bidirectional replication, after you select that server. This server must contain physical tables that you want to include in the logical tables that you want to replicate. Click the button to open the Select Server window.
Opens the Select Server window.
Select the schema that identifies both the Q Capture and Q Apply programs that you want to use on this server.
Displays the alias of one of the servers that you want to participate in bidirectional replication, after you select that server. This server can already contain physical tables whose definitions are identical to the physical tables that you want to replicate on the first server or you can choose to have the Replication Center create the tables for you. Click the button to open the Select Server window.
Opens the Select Server window.
Select the schema that identifies both the Q Capture and Q Apply programs that you want to use on this server.
Displays the name of the replication queue map that lets the Q Capture program on the first server communicate with the Q Apply program on the second server, after you select that replication queue map. Click the button to open the Select Replication Queue Map window. Replication queue maps specify a group of WebSphere MQ message queues that together can be used as a means of transporting data messages from the Q Capture program to the Q Apply program and transporting administration messages from the Q Apply program to the Q Capture program.
Opens the Select Replication Queue Map window. From this window you can also create a replication queue map if the needed WebSphere MQ message queues exist.
Displays the name of the replication queue map that lets the Q Capture program on the second server communicate with the Q Apply program on the first server, after you select that replication queue map. Click the button to open the Select Replication Queue Map window. Replication queue maps specify a group of WebSphere MQ message queues that together can be used as a means of transporting data messages from the Q Capture program to the Q Apply program and transporting administration messages from the Q Apply program to the Q Capture program.
Opens the Select Replication Queue Map window. From this window you can also create a replication queue map if the needed WebSphere MQ message queues exist.
Displays the alias of one of the servers that you want to participate in peer-to-peer replication with two servers, after you select that server. This server must contain physical tables that you want to include in the logical tables that you want to replicate. Click the button to open the Select Server window.
Opens the Select Server window.
Select the schema that identifies both the Q Capture and Q Apply programs that you want to use on this server.
Displays the alias of one of the servers that you want to participate in peer-to-peer replication with two servers, after you select that server. This server can already contain physical tables whose definitions are identical to the physical tables that you want to replicate on the first server or you can choose to have the Replication Center create the tables for you. Click the button to open the Select Server window.
Opens the Select Server window.
Select the schema that identifies both the Q Capture and Q Apply programs that you want to use on this server.
Displays the name of the replication queue map that lets the Q Capture program on the first server communicate with the Q Apply program on the second server, after you select that replication queue map. Click the button to open the Select Replication Queue Map window. Replication queue maps specify a group of WebSphere MQ message queues that together can be used as a means of transporting data messages from the Q Capture program to the Q Apply program and transporting administration messages from the Q Apply program to the Q Capture program.
Opens the Select Replication Queue Map window. From this window you can also create a replication queue map if the needed WebSphere MQ message queues exist.
Displays the name of the replication queue map that lets the Q Capture program on the second server communicate with the Q Apply program on the first server, after you select that replication queue map. Click the button to open the Select Replication Queue Map window. Replication queue maps specify a group of WebSphere MQ message queues that together can be used as a means of transporting data messages from the Q Capture program to the Q Apply program and transporting administration messages from the Q Apply program to the Q Capture program.
Opens the Select Replication Queue Map window. From this window you can also create a replication queue map if the needed WebSphere MQ message queues exist.
List the servers that you want to participate in peer-to-peer replication. The first server that appears in the list is the server from which you opened the Create Q Subscription wizard.
Opens the Add Server window. With this window, you can specify a server to add to your peer-to-peer configuration and specify the replication queue maps that the server will use to communicate with the other servers in the configuration.
Click to change the replication queue maps that the selected server will use to communicate with the other servers in your configuration.
Click to remove the selected server from the list of servers that you want to use in your peer-to-peer configuration.
Specifies that you want the columns in your source tables to be mapped to the columns in corresponding, existing target tables, according to the names of the columns and their data types. If column names in a source table are identical to the column names in the corresponding target table, and the data types are compatible, they will be mapped together. Remember that names must be identical. Changes made to the source column will be replicated to the target column. If the Replication Center cannot map all of the columns from the source to columns in the target in a Q subscription, you will have to map the remaining columns manually. You will know whether you have to do so for a given Q subscription if it has a red border on the Review Q Subscriptions page of this wizard. If it does, select the Q subscription and click the Properties button. On the Subsetting page, open the Column Mapping window.
Note: This option applies only to Q subscriptions using target tables that already exist. If the Replication Center creates a target table for a Q subscription, all of the source columns automatically map to all of the target columns because the Replication Center creates the target tables as identical to the source table.
Specifies that you want the columns in your source tables to be mapped to the columns in corresponding, existing target tables, according to the order in which the columns appear in the source tables. For example, in a given Q subscription, the first column in the source table will be mapped to the first column in the target table. If there are fewer columns in a target table than in its corresponding source table, you will have to replicate more columns from the source table, use a different target table, or recreate the target table. You will know whether you have to do so for a given Q subscription if it has a red border on the Review Q Subscriptions page of this wizard. If it does, select the Q subscription and click the Properties button. On the Subsetting page, open the Column Mapping window.
Note: This option applies only to Q subscriptions using target tables that already exist. If the Replication Center creates a target table for a Q subscription, all of the source columns automatically map to all of the target columns because the Replication Center creates the target tables as identical to the source table.
Specifies that you want to create additional CCD table columns to store before values for all columns that support replication of before values. Before values are not supported for columns with large object (LOB) data-types.
Specifies that you want to create additional CCD table columns to store before values for key columns.
Specifies that you do not want to store before values in the CCD tables.
Opens the View Selected Columns window where you can view the source columns that have been chosen for replication and any source columns that cannot be replicated.
Opens the Column Mapping window where you can view the the mapping between source columns and target columns, and any unmapped columns.
Specifies that you want the Q Apply program to resolve conflicts between source and target data by forcing the changes from the source into the target. If an application makes changes made to your target tables that result in conflicts, those changes will be lost.
Specifies that you want the Q Apply program to respond to conflicts between source and target data according the option you next select.
Specifies that you want the Q Apply program to ignore conflicts between source and target data. Select this option if you do not expect conflicts within your data.
Specifies that you want to stop replicating the source data in a Q subscription if the Q Apply program finds that it conflicts with data in the corresponding target. By stopping the Q subscription, only replication between its source and target table is stopped. Use this option if you do not have dependencies among different Q subscriptions. To solve the conflict, delete the problem rows from the target table. Then, restart the Q subscription.
Specifies that you want the Q Apply program to stop reading data from the receive queue used for the Q subscription, if there is a conflict between the source and target data. If other Q subscriptions use the same receive queue, the Q Apply program will stop reading data for them, too. The Q Capture program will continue to send data to the receive queue. Select this option if you want to be sure that all Q subscriptions that use the receive queue are replicated together. To solve the conflict between the source and target data in the Q subscription, delete the problem rows from the target table. Then, restart the receive queue from the Manage Receive Queues window.
Specifies that you want the Q Apply program to stop if there is a conflict between the source and target data in the Q subscription. When you stop the Q Apply program, it stops reading data messages from all of its receive queues. Select this option if you want to be sure that all Q subscriptions processed by the Q Apply program are replicated together. To solve the conflict between the source and target data in the Q subscription, delete the problem rows from the target table. Then, restart the Q Apply program.
Specifies that you want the Q Apply program to apply source changes to the target table even if doing so overwrites conflicting or unexpected changes made to the target data by other applications.
Specifies that if the Q Apply program finds conflicting or unexpected changes in the target data, it will perform one of the following actions.
Specifies that you want the Q Apply program to keep the target data, even if it conflicts with the source data.
Specifies that you want stop replicating from the source table to the target table if there is a conflict between source and target data in the Q subscription. The Q Capture program stops capturing for the Q subscription and the Q Apply program stops applying data at the target. The type of load that you specify for the Q subscription determines what happens when you start the Q subscription again. If you chose an automatic load, the Q Apply program invokes a utility to replace the contents of the target with the current contents of the source. If you chose a manual load, use your preferred load method to load the target. If you chose not to require a load of the target, the error will persist when you restart the Q subscription, unless you delete the problem-causing rows from the target table.
Specifies that you want the Q Apply program to stop reading data from the receive queue used by the Q subscription if there is a conflict between the source and target data in the Q subscription. When you stop the receive queue, the Q Apply program stops reading data messages for all Q subscriptions that use the queue. The Q Capture program continues to send data messages to the receive queue. Select this option if you want to be sure that all Q subscriptions that use the receive queue are replicated together. To solve the conflict between the source and target data in the Q subscription, delete the problem rows from the target table. Then, restart the receive queue from the Manage Receive Queues window.
Specifies that you want the Q Apply program to stop if there is a conflict between the source and target data in the Q subscription. When you stop the Q Apply program, it stops reading data messages from all of its receive queues, which still receive messages from the Q Capture programs that feed them. Select this option if you want to be sure that all Q subscriptions processed by the Q Apply program are replicated together. To solve the conflict between the source and target data in the Q subscription, delete the problem rows from the target table. Then, restart the Q Apply program. If you do not want the receive queues filling up with data messages from the Q Capture programs that feed them, you could stop those Q Capture programs and then warm start them when you are ready to replicate again.
Specifies that you want to stop replicating the source data in a Q subscription if the Q Apply program encounters an SQL error that you did not tell it to ignore. When you start replicating the source data in the Q subscription again, the load mechanism that you selected when you created the Q subscription will load the target. If you chose always to load the target manually, you will need to do so before replication can begin. If you chose never to have the load performed automatically or manually, the SQL error will remain when replication begins, unless you fix it first.
Specifies that you want the Q Apply program to stop reading data from the receive queue used for the Q subscription if the Q Apply program encounters an SQL error. If other Q subscriptions use the same receive queue, the Q Apply program will stop reading data for them, too. The Q Capture program will continue to send data to the receive queue. Select this option if you want to be sure that all Q subscriptions that use the receive queue are replicated together.
Specifies that you want the Q Apply program to stop if it receives an SQL error while applying data to the target for a Q subscription. When you stop the Q Apply program, it stops reading data messages from all of its receive queues. Select this option if you want to be sure that all Q subscriptions processed by the Q Apply program are replicated together.
Click to specify any SQL states that you want the Q Apply programs to ignore.
Select if you want the Q Apply programs to check for conflicts between the source and target tables in your Q subscriptions by comparing the values of all columns in each source row that they try to apply to target tables.
Select if you want the Q Apply programs to check for conflicts between the source and target tables in your Q subscriptions by comparing the values of only changed, non-key columns in each source row that they try to apply to target tables.
Select if you want the Q Apply programs to check for conflicts between the source and target tables in your Q subscriptions by comparing the values of only key columns in each source row that they try to apply to target tables.
Select if you want the named server to take precedence if the Q Apply programs detect conflicts between source and target tables in your Q subscriptions. The tables on this server will always override conflicting data in the tables on the other server.
Select if you want the named server to take precedence if the Q Apply programs detect conflicts between source and target tables in your Q subscriptions. The tables on this server will always override conflicting data in the tables on the other server.
Select if you want neither server to take precedence. If the Q Apply programs detect conflicts between any of the source and target tables in your Q subscriptions, they will log the conflicts but will not override any data in the tables.
Specifies that you want the Q Apply program to invoke a utility to load the target table in each Q subscription.
Select a utility or combination of utilities to load the target table, or specify that you want the Q Apply program to choose the best available load option depending on the source and target platform.
Specify whether the load utility should delete all data in the target table before replacing it with data from the source, or append source data to the target table without deleting target table contents.
Specifies that you always want to load each target table yourself. You can choose this option if you have your own preferred method for loading tables, or if the target tables are on a non-DB2 relational database. When you start the Q subscription, you need to tell the Replication Center that you have finished the load before replication will begin.
Specifies that you never want each target table to be loaded before replication of source data in the Q subscriptions begins or that you plan to load the target tables outside the context of the Replication Center. Loading the target tables outside the context of the Replication Center means that you plan to load the target tables yourself and then start replication without the Q Apply program putting your Q subscriptions in load-pending state or trying to perform an automatic load. If you choose this option, make sure that the values of the primary key or unique index of the source table are also present in the primary key or unique index of the target table.
Specifies that if the Q Capture program detects a load operation at the source table, the Q subscription is stopped and then started, setting up a new load of the target table. The Q Apply program follows the load option that is specified for the Q subscription. If you select this option, be aware of possible mismatches between the load type at the source (replace or append) and the load type at the target.
Specifies that you want the Replication Center to create the nickname that refers to the source table for you.
Type the owner of the nickname that you want the Replication Center to create to refer to the source table.
Type the name of the nickname that you want the Replication Center to create to refer to the source table.
Specifies that you already have a nickname that refers to the source table.
Displays the owner and name of the nickname. Click the button to open the Select Nickname window and select the nickname.
Opens the Select Nickname window.
Specifies that you want the Replication Center to create the nicknames to refer to the source table for your Q subscriptions.
Displays the name of the server definition that defines the data sources to the federated database. Click the button to open the Select Server Definition window.
Opens the Select Server Definition window.
Specifies that you want to edit each Q subscription so that you can specify the existing nicknames to use to refer to the source table. On the Review Q Subscriptions page of the wizard, select a Q subscription, click the Properties button, and specify the nickname on the Load page of the Q Subscription Properties notebook. Repeat this procedure for each Q subscription that you are creating.
Specifies that you do not want the Q Apply program to consider the LOAD FROM CURSOR option of the LOAD utility, even though you selected the Best available radio button for automatic loads.
Select to have the Q subscription start when you start the Q Capture program.
Select to have the Q subscriptions start when you start the Q Capture program.
Select if you want the Q Apply programs to automatically load their respective target tables. By default, they will choose whether to call the EXPORT and LOAD utilities or the EXPORT and IMPORT utilities to perform the loads. If you want the Q Apply programs to consider using the LOAD FROM CURSOR option of the LOAD utility for the target table in one or more Q subscriptions, on the Review Q Subscriptions page of this wizard open the Q Subscription Properties notebook and change the options selected on the Load page.
Select if you want to load target tables yourself. After you load the target tables, you must inform the Q Apply programs that the loads are complete. After you do so, the Q subscriptions will be active.
Specifies that you never want each target table to be loaded before replication of source data in the Q subscriptions begins or that you plan to load the target tables outside the context of the Replication Center. Loading the target tables outside the context of the Replication Center means that you plan to load the target tables yourself and then start replication without the Q Apply program putting your Q subscriptions in load-pending state or trying to perform an automatic load. If you choose this option, make sure that the values of the primary key or unique index of the source table are also present in the primary key or unique index of the target table.
Select if you want all of the Q subscriptions that you are creating with this wizard to start automatically when you start the Q Capture program on the server that you select below.
Select if you want the tables on the named server to be used as the source tables for the initial load of target tables.
Select if you want the tables on the named server to be used as the source tables for the initial load of target tables.
Select if you want the Q Apply program to automatically load the target table. By default, the Q Apply program will choose whether to call the EXPORT and LOAD utilities or the EXPORT and IMPORT utilities to perform the load.
Select if you want to load the target table yourself, using whatever method you prefer.
Specifies that you never want each target table to be loaded before replication of source data in the Q subscriptions begins or that you plan to load the target tables outside the context of the Replication Center. Loading the target tables outside the context of the Replication Center means that you plan to load the target tables yourself and then start replication without the Q Apply program putting your Q subscriptions in load-pending state or trying to perform an automatic load. If you choose this option, make sure that the values of the primary key or unique index of the source table are also present in the primary key or unique index of the target table.
Specifies that you want the Q Apply program to load the target table by using the DB2 LOAD utility with the replace option. This option deletes all existing data from the table and inserts the loaded data.
Specifies that you want the Q Apply program to load the target table by using the DB2 LOAD utility with the insert option. This option adds the imported data to the table without changing the existing table data. Use this option if more than one Q subscription specifies the same target table.
Specifies that you want the Q Apply program to load the target table by using the DB2 IMPORT utility with the replace option. This option deletes all existing data from the table and inserts the imported data. Use this option when the Classic source database uses double-byte characters or a code page that is not converted by the DB2 LOAD utility. DB2 IMPORT handles the conversion.
Specifies that you want the Q Apply program to load the target table by using the DB2 IMPORT utility with the insert option. This option adds the imported data to the table without changing the existing table data. Use this option if more than one Q subscription specifies the same target table.
Specifies that you want the Q Apply program to load the target table by using the DB2 LOAD utility with the resume option. This option inserts only new rows and keeps existing rows in the table. Use this option if more than one Q subscription specifies the same target table.
Opens the Q Subscription Properties notebook for the selected Q subscription. You can use this notebook to make any changes to individual Q subscriptions before you create them. You must use this notebook for a Q subscription if there is an X displayed next to that Q subscription in the table on this page.
Lists the Q subscriptions that the Create Q Subscriptions wizard will generate the SQL scripts for when you click the Finish button. An X appears next to any Q subscriptions that are in error. To fix the errors in a Q subscription, you must select the Q subscription and click the Properties button. The Q Subscription Properties notebook opens.
Removes the selected Q subscription from the list. Q subscriptions that you remove will not be created.
Specifies that the Q subscription will replicate changes to tables in the non-DB2 relational server and will not pass the data to parameters in a stored procedure.
Type the name of a segment where the target table will be created in the Sybase database. The segment must already exist. If you do not type a segment, the table will be created in the default segment.
Type the name of a table space where the target table will be created in the Oracle database. The table space must already exist. If you do not type a table space, the table will be created in the default table space.
Type the name of a dbspace where the target table will be created in the Informix database. The dbspace must already exist. If you do not type a dbspace, the table will be created in the default dbspace.
Type the name of a filegroup where the target table will be created in the Microsoft SQL Server database. The filegroup must already exist. If you do not type a filegroup, the table will be created in the default filegroup.
Type a schema for the new nickname that will be created for the target table.
Type the name of the new nickname that will be created for the target table.
Displays the name of the model queue that is used as a spill queue for all Q subscriptions that you are creating. Type a valid model queue name, or click the ellipsis button to see a list of available queues. You can specify a different model queue for individual Q subscriptions by opening the Q Subscriptions Properties notebook from the Review page. The WebSphere MQ access function must be enabled and the queue manager must be running for you to see a list of queues.
Opens a window so that you can choose a model queue on the system where the Q Apply program runs as the spill queue for this Q subscription.
Checks the settings of the model queue that you specified and displays the results.