This document describes how you can initiate synchronized and replay-only replay processing. This method involves a combination of the Adabas Event Replicator Subsystem and a batch ADARPL utility job or automated replay. You first use the Adabas Event Replicator Subsystem 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 .

To generate a synchronized or replay-only replay request using the Adabas Event Replicator Subsystem and the ADARPL utility, complete the following steps:

1. Select option A from the Adabas Event Replicator Subsystem Main Menu.

   The Administration menu appears.

   14:53:47 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28 Administration M-RP1100 Code Function ---- ------------------------------- D Database ID I Perform Initial-State P PLOG Information R Initiate Replay S System Functions T Target Adapter V Global Values ? Help . Exit ---- ------------------------------- Code ... _ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Menu

2. Select option R on the Administration menu.

   The Initiate Replication Replay menu appears.

   18:44:01 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28 Initiate Replication Replay M-RP2005 Mode Definition ---- ------------------------------- S Synchronized R Replay Only ? Help . Exit ---- --------------------------------- Mode ... _ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Menu

3. Select a mode on the Initiate Replication Replay menu. For more information about replay modes, read Understanding Replay Modes.

   An Initiate Replication Replay screen appears for the replay mode you selected. For example, if you selected S (synchronized) mode, the following screen appears:

   18:44:25 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28 Initiate Replication Replay M-RP2010 Synchronized DBID ........................... _____ Automated ...................... N (Y or N) Timeout ........................ 900_______ From Date/Time ................. __________ ________ To Date/Time ................... __________ ________ Start Date/Time ................ __________ ________ Destination Name List ..... _ * ________ ________ ________ Subscription Name List .... _ * ________ ________ ________ Command ==> Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Sub Sel Menu

4. Update the following fields on this screen as described in this table.

   Parameter Name	Specify	Default
   Automated	Indicate whether or not you want the replay automated or not. Valid values are "Y" (perform an automated replay) or "N" (do not perform an automated replay). An automated replay will automatically perform steps 6 through 8 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. Note: If the RECORDPLOGINFO parameter has been set to NO, you cannot run an automated replay.	N
   DBID	The database ID of the Adabas database from which you want replicated transactions replayed.	---
   Destination Name List	A list of destinations for which the replay request should be initiated. When the replay request is initiated, transactions will be replayed that were originally destined for the destinations on this list. Tab to the larger spaces for the Destination Name List field and type in the names of up to three destinations for replay processing. If you would prefer to select the names from a list, place the cursor on one of the three larger spaces and press PF6. If you want to select all destinations for replay processing, tab to the first large space for the Destination Name List field and enter an asterisk (*). Note that once you have entered an asterisk in the first field, you can no longer select any specific destinations (errors will occur if you try). Alternatively, if you need to enter more than three destinations or if you want to review the complete list of destinations selected for replay processing, type an "X" in the single-character space for the Destination Name List field and press Enter. A screen appears on which you can maintain the complete list of destinations. Using this screen: Type in the destination definition names in the spaces provided. If you would prefer to select the names from a list, place the cursor on one of the spaces and press PF6. A list appears from which you can select destinations. When you are satisfied with the list of destinations on the Destination List screen, press PF5 to accept them and return to the Initiate Replication Replay screen.	---
   From Date/Time	The date and time from which replicated transactions should be replayed. Dates should be specified in YYYY/MM/DD format; times should be specified in HH:MM:SS format. Replay processing will start with transactions in the PLOG that ended at or after this date and time. From dates and times must be earlier than the current date and time and earlier than the specified end date and time.	---
   Start Date/Time	The date and time of the PLOG entries that should be used as a starting point for the replay processing. This date and time are used to identify the PLOG with which to start replay processing. Dates should be specified in YYYY/MM/DD format; times should be specified in HH:MM:SS format. Replay processing will search the PLOG with this start date and time first for records that match the other replay processing criteria listed on this screen. A start date and time must be specified if an automated replay is requested.	---
   Subscription Name List	A list of subscriptions for which the replay request should be initiated. When the replay request is initiated, transactions will be replayed that were originally initiated by the subscriptions on this list. Tab to the larger spaces for the Subscription Name List field and type in the names of up to three subscriptions for replay processing. If you would prefer to select the names from a list, place the cursor on one of the three larger spaces and press PF6. If you want to select all subscriptions for replay processing, tab to the first large space for the Subscription Name List field and enter an asterisk (*). Note that once you have entered an asterisk in the first field, you can no longer select any specific subscriptions (errors will occur if you try). Alternatively, if you need to enter more than three subscriptions or if you want to review the complete list of subscriptions selected for replay processing, type an "X" in the single-character space for the Subscription Name List field and press Enter. A screen appears on which you can maintain the complete list of subscriptions. Using this screen: Type in the subscription definition names in the spaces provided. If you would prefer to select the names from a list, place the cursor on one of the spaces and press PF6. A list appears from which you can select subscriptions. When you are satisfied with the list of subscriptions on the Subscription List screen, press PF5 to accept them and return to the Initiate Replication Replay screen.	---
   Timeout	Optionally, specify the length of time, in seconds, at which the replay request should time out.	900 seconds
   To Date/Time	The date and time to which replicated transactions should be replayed. Dates should be specified in YYYY/MM/DD format; times should be specified in HH:MM:SS format. Replay processing will stop with transactions in the PLOG that ended before this date and time. End dates and times must be later than the specified start date and time. If no end date and time are specified, the end time is the current time (the time the replay request is issued).	The current time

5. When all fields on the Initiate Replication Replay screen have been filled in to your satisfaction, press PF5 to initiate the replay request.

   The replay request is generated and a replay token is assigned to it. This replay token is displayed in an Adabas Event Replicator Subsystem message and in the Event Replicator Server job log.

   Make a note of this token number as it is used in step 8 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.

6. This step should not be performed if an automated replay is requested (Automated = Y on the 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 = N on the screen).

7. This step should not be performed if an automated replay is requested (Automated = Y on the 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.

8. This step should not be performed if an automated replay is requested (Automated = Y on the screen).

   Run an ADARPL utility job, using the syntax described in Syntax for Initiating ADARPL With A Token. 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 5. 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 .

   The replay process is initiated using the replay request generated in the Adabas Event Replicator Subsystem.