This document describes how you can initiate synchronized and replay-only replay processing. This method involves a combination of Event Replicator Administration and a batch ADARPL utility job or automated replay. You first use Event Replicator Administration to generate a replay request. The replay request is assigned a token that you then use in the batch ADARPL utility job. For complete information about the ADARPL utility, read ADARPL Utility: PLOG Replication Replay in Event Replicator for Adabas Reference Guide provided with your Event Replicator for Adabas documentation.
To generate a synchronized or replay-only replay request using Event Replicator Administration
and the ADARPL utility, complete the following steps:
Select an Event Replicator Server in tree-view as described in Selecting Event Replicator Databases.
Click on Replay in the tree-view under Replicators.
A table listing the specifications you must make to initiate replay processing appears in detail-view.
Update the fields in detail-view as described in this table.
| Parameter Name | Specify | Default |
|---|---|---|
| DBID | The database ID of the Adabas database from which you want replicated transactions replayed. | --- |
| Automated | A check in this checkbox if you want the replay
automated or not.
An automated replay will automatically perform steps 11 through 13 of this procedure. A non-automated replay will not perform these steps automatically, and you will need to perform them manually. For complete information about automating replay processing, read Automating Replay Processing, in the Event Replicator for Adabas Administration and Operations Guide. Note: |
checked |
| Timeout | Optionally, specify the length of time, in seconds, at which the replay request should time out. | 900 seconds |
| From Date | The date from which replicated transactions should be replayed. Dates should be specified in YYYY/MM/DD format. Replay processing will start with transactions in the PLOG that ended at or after this date. The combination of From Date and From Time must be earlier than the current date and time and earlier than the specified From Date and Time. | --- |
| From Time | The time from which replicated transactions should be replayed. Times should be specified in HH:MM:SS format. Replay processing will start with transactions in the PLOG that ended at or after this time. The combination of From Date and From Time must be earlier than the current date and time and earlier than the specified From Date and Time. | --- |
| To Date | The date to which replicated transactions
should be replayed. Dates should be specified in YYYY/MM/DD format. Replay
processing will stop with transactions in the PLOG that ended before this date.
The combination of To Date and To Time must be later than the specified From
Date and Time.
If no end date is specified, the end date is the current date (the date the replay request is issued). |
The current date |
| To Time | The time to which replicated transactions
should be replayed. Times should be specified in HH:MM:SS format. Replay
processing will stop with transactions in the PLOG that ended before this time.
The combination of To Date and To Time must be later than the specified From
Date and Time.
If no end time is specified, the end time is the current time (the time the replay request is issued). |
The current time |
Click on the checkmark in the Value column of the Destination Name List field.
The destination list tables appear in detail-view.
Optionally, specify a list of destinations for replay processing in the Destinations Selected table. When the replay request is initiated, transactions will be replayed that were originally destined for the destinations on this list.
To select a destination, click on a destination name in the Destinations Available table and then click the right arrow. The selected destination will appear in the Destinations Selected table. You can use the and buttons to order the destinations in the list.
To remove a destination from the Destinations Selected table, select it and click the left arrow. The selected destination is moved back to the Destinations Available table.
When you are satisfied with the list of destinations in the Destinations Selected table, click to accept them and return to the Initiate Replication Replay screen.
Note:
The destinations you selected appear in the Destination
Name List field.
Click on the checkmark in the Value column of the Subscription Name List field.
The subscription list tables appear in detail-view.
Optionally, specify a list of subscriptions for replay processing on the Subscriptions Selected table. When the replay request is initiated, transactions will be replayed that were originally initiated by the subscriptions on this list.
To select a subscription, click on a subscription name in the Subscriptions Available table and then click the right arrow. The selected subscription will appear in the Subscriptions Selected table. You can use the and buttons to order the subscriptions in the list.
To remove a subscription from the Subscriptions Selected table, select it and click the left arrow. The selected subscription is moved back to the Subscriptions Available table.
When you are satisfied with the list of subscriptions in the Subscriptions Selected table, click to accept them and return to the Initiate Replication Replay screen.
Note:
The subscriptions you selected appear in the Subscription
Name List field.
When all fields on the Initiate Replication Replay screen have been filled in to your satisfaction, click or to initiate the appropriate replay request. Synchronized and Replay Only are two of the three possible replay modes in which ADARPL can run. For complete information about replay modes, read Understanding Replay Modes in the Event Replicator for Adabas Administration and Operations Guide.
The replay request is generated and a replay token is assigned to it. This replay token is displayed in an Event Replicator Administration message and in the Event Replicator Server job log.
Make a note of this token number as it is used in step 13 if you are initiating replication replay using a batch ADARPL job.
If you have automated replication replay processing, this token number is picked up automatically by the generated replay jobstream and you can skip the remaining steps in this procedure. For complete information about automating replay processing, read Automating Replay Processing, in the Event Replicator for Adabas Administration and Operations Guide.
This step should not be performed if an automated replay is requested (Automated is checked on the Initiate Replication Replay screen).
If necessary, issue a force-end-of-PLOG request to the Adabas database and wait until the resulting PLCOPY job has copied or merged the latest PLOG data set. This is necessary only when the PLOG for the selected replay end date and time has not yet been copied or merged, for example, if no end date and time were specified in the replay request. This is also only necessary if an automated replay was not selected (Automated is not checked on the Initiate Replication Replay screen).
This step should not be performed if an automated replay is requested (Automated is checked on the Initiate Replication Replay screen).
Identify the sequential PLOG data sets that contain the protection data for the replicated records you need replayed. The PLOG data sets must build a complete sequence from the PLOG that includes the replay processing start time to the latest PLOG you copied or merged in the previous step.
This step should not be performed if an automated replay is requested (Automated is checked on the Initiate Replication Replay screen).
Run an ADARPL utility job, using the syntax described in Syntax for Initiating ADARPL With A Token in Event Replicator for Adabas Reference Guide provided with your Event Replicator Administration documentation. Be sure to specify:
A concatenated list of the PLOG data sets you identified in the previous step.
The replay request token assigned in step 10. This token should be specified in the ADARPL TOKEN parameter.
The Event Replicator Server ID of the Event Replicator Server to which the replayed transactions should be sent. This token should be specified in the ADARPL RPLTARGETID parameter.
For more information about using the ADARPL utility, in general, read ADARPL Utility: PLOG Replication Replay in Event Replicator for Adabas Reference Guide provided with your Event Replicator Administration documentation.
The replay process is initiated using the replay request generated in Event Replicator Administration.
