Generates the SQL script and opens the Run Now or Save SQL window.

Closes the window without saving your changes.

Type a name for this replication queue map.

Optional: Type descriptive information about this replication queue map that might be useful later.

Specify the name of an existing server to use with this replication queue map. Specify a Q Capture server if you opened this window from a Q Apply schema. Specify a Q Apply server if you opened this window from a Q Capture schema.

Click to select from a list of available servers. The list shows available Q Capture servers if you opened this window from a Q Apply schema. Available Q Apply servers are shown if you opened this window from a Q Capture schema.

Select which schema to associate with this replication queue map. The list shows available Q Capture schemas if you opened this window from a Q Apply schema. Available Q Apply schemas are shown if you opened this window from a Q Capture schema.

Displays the queue that is used to send data for replication. Type a valid queue name, or click the ellipses button to see a list of available queues. The WebSphere MQ access function must be enabled and the queue manager must be running for you to see a list of queues. This function is not available for Classic replication or Oracle sources.

Displays the queue that is used to send data for replication. Type a valid queue name, or click the ellipses button to see a list of available queues. The WebSphere MQ access function must be enabled and the queue manager must be running for you to see a list of queues. This function is not available for Classic replication sources.

Opens a window so that you can choose a send queue.

In a remote configuration this queue points to the receive queue on the system where the Q Apply program runs.

Displays the queue that is used to receive data for replication. Type a valid queue name, or click the ellipses button to see a list of available queues. 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 receive queue. The receive queue is a local queue on the system where the Q Apply program runs.

Displays the queue that the Q Apply program uses to communicate with the Q Capture program. Type a valid queue name, or click the ellipses button to see a list of available queues. 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 an administration queue.

In a remote configuration this queue points to the administration queue on the system where the Q Capture program runs.

Opens a window so that you can check the settings of the send queue, receive queue, and administration queue that you specified. You can also send test messages.

Specify the maximum size for messages. If you specify a smaller size, more messages are sent. Do not specify a message length greater than the maximum message length of the WebSphere MQ queue.

Select how you want to handle errors found in the queues. Select Stop send queue to prompt the Q Capture program to stop putting messages on this send queue but continue putting messages on other send queues. Select Stop Q Capture program to stop the Q Capture program when there is an error with the send queue. The Stop send queue option is not available for Classic replication.

Type the maximum number of Q Apply agents to use. Type 1 to always process transactions in the same order that they were processed at the source. Type a number greater than 1 to process transactions in parallel.

Specify the memory limit for each receive queue of the Q Apply program. This value controls how many transactions are buffered for the Q Apply agent to apply.

The default is 2 MB. The best value for your system depends on its configuration and load. If you set the value low, the agents might be idle and waiting for work.

Select this check box for the Q Capture program to periodically send a message to indicate that the Q Capture program is still running.

You can also send heartbeat messages to keep the MQ channel from timing out. If the MQ channel times out, the Q Capture program cannot place messages on the send queue after the transmit queue is full. The default timeout value for an MQ channel disconnect interval (DISCINT) is 6000 seconds. A value of 0 indicates that the MQ channel never times out. To keep the MQ channel open, specify a heartbeat interval that is less than the disconnect interval.

Specify how often (in seconds) to send a message to indicate that the Q Capture program is running. You must select the Allow the Q Capture program to send heartbeat messages check box to enable heartbeat messages.

You can also send heartbeat messages to keep the MQ channel from timing out. If the MQ channel times out, the Q Capture program cannot place messages on the send queue after the transmit queue is full. The default timeout value for an MQ channel disconnect interval (DISCINT) is 6000 seconds. A value of 0 indicates that the MQ channel never times out. To keep the MQ channel open, specify a heartbeat interval that is less than the disconnect interval.

Select to limit the number of Q Apply agent threads that are used to concurrently apply transactions with the same correlation ID (normally a job name). Limiting the number of agents reduces parallel processing but can prevent lock timeouts and deadlocks for large batch workloads.

Specify the number of Q Apply agent threads that are used to concurrently apply transactions with the same correlation ID. A value of 1 means transactions will be applied serially (one after the other).

Click to open the Save ASNCLP Script window, where you can view and save the generated ASNCLP command script for creating the queue map.