The Adabas Event Replicator Subsystem provides an online interface you can use to maintain definitions for the Event Replicator for Adabas. These definitions are stored in the Replicator system file associated with a specific Event Replicator Server.
This document covers the following topics:
Maintaining Replication Definitions Using Adabas Event Replicator Subsystem
Identifying, Loading, and Unloading the Replicator System File
You can access the Adabas Event Replicator Subsystem with or without the Adabas Online System (AOS). The procedure described in this section describes how to access it without AOS. For information on accessing it from AOS, read Accessing the Adabas Event Replicator Subsystem from AOS.
To access the Adabas Event Replicator Subsystem without using AOS:
Verify that the Event Replicator Server and Replicator system file have been defined appropriately, as described in the Event Replicator for Adabas installation documentation.
Use ADALOD to load a Replicator system file into the Event Replicator Server. The Replicator system file is an Adabas system file. For more information about the ADALOD functions and parameters pertinent to Event Replicator for Adabas, read ADALOD LOAD Parameters. For more information about Adabas system files, read about the FILE parameter of the ADALOD LOAD function in your Adabas utilities documentation.
Specifically, you need to specify the REPLICATOR parameter on the ADALOD LOAD function:
ADALOD LOAD FILE=nnnn,REPLICATOR
where nnnn is the number of the Replicator system file. For example:
ADALOD LOAD FILE=89,REPLICATOR
The Replicator system file, when loaded, stores the Event Replicator Server initialization parameters. These parameters are defined in the Replicator system file using the online Adabas Event Replicator Subsystem. If the Replicator system file is not present, the Event Replicator initialization parameters are read from the DDKARTE of the Event Replicator Server job.
Start Natural with the Natural LFILE parameter set as follows:
LFILE=(89,dbid,file)
where dbid is the database ID of an Event Replicator Server you created during installation and file is a Replicator system file. The LFILE parameter can be specified either as a dynamic parameter or inside a Natural SYSPARM profile.
Logon to the SYSRPTR library by entering:
LOGON SYSRPTR
Enter the following command:
MENU
The Adabas Event Replicator Subsystem Main Menu appears.
You can control access to the Adabas Event Replicator Subsystem using the initialization exit, subprogram N-IEXIT. This exit is a Natural subprogram that runs automatically, whenever a user attempts to access the Adabas Event Replicator Subsystem. Based on Natural code you supply in the exit using the exit parameters, you can:
restrict specific users from accessing the Adabas Event Replicator Subsystem
identify the Replicator system file initially used by a user or users.
For complete information on coding Natural subprograms, read your Natural documentation. Once you have supplied code in the N-IEXIT subprogram, the ID of any user attempting to access the Adabas Event Replicator Subsystem is passed to the exit. If the #RESPONSE parameter is set to a non-zero value for that user, they cannot access the Adabas Event Replicator Subsystem .
A sample of the N-IEXIT is shown below.
0010 *************************** 0020 * INITIALIZATION EXIT * 0030 *************************** 0040 DEFINE DATA PARAMETER 0050 01 #USER (A08) /* USER ID 0060 01 #REPTOR-DBID (N05) /* REPTOR ID 0070 01 #REPTOR-FNR (N05) /* REPTOR SYSTEM FILE 0080 01 #PARM-1 (A40) /* DATA 0090 01 #RESPONSE (B02) /* USER EXIT RESPONSE CODE 0100 01 #VERSION (A04) /* ONLINE SYSTEM VERSION 0110 END-DEFINE 0120 * 0130 #RESPONSE = H'0000' /* NON-ZERO WILL TERMINATE 0140 ESCAPE ROUTINE 0150 END
You can use the following parameters while coding the Natural subprogram:
| Parameter | Description |
|---|---|
| #PARM-1 | Reserved for future use. |
| #REPTOR-DBID | The database ID of the Event Replicator Server whose Replicator system file you want to maintain when the Adabas Event Replicator Subsystem starts. Once you are using the Adabas Event Replicator Subsystem, you can change this setting using the Set LFILE Parameters screen. |
| #REPTOR-FNR | The file number of the Replicator system file you want to maintain when the Adabas Event Replicator Subsystem starts. Once you are using the Adabas Event Replicator Subsystem, you can change this setting using the Set LFILE Parameters screen. |
| #RESPONSE | A non-zero response code will cause the Adabas Event Replicator Subsystem to terminate. By setting this to a non-zero number you can restrict access to the Adabas Event Replicator Subsystem for the user identified in the USER parameter or for the Adabas Event Replicator Subsystem version specified in the VERSION parameter.. |
| #USER | The user ID of a potential Adabas Event Replicator Subsystem user. |
| #VERSION | The version of the Adabas Event Replicator Subsystem. |
From the main menu of the Adabas Event Replicator Subsystem screens, you can select options that allow you to maintain any Event Replicator for Adabas definitions you need. Definitions can be added, reviewed, modified, copied, or deleted.
14:49:23 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Vers 3.4.1 Main Menu M-RP0010
DBID 1954 File 89
Code Function
---- --------------------------------
A Administrator Functions
D Destination Definitions
F Transaction Filter Definitions
G Global Format Buffer Definitions
I Initial-State Definitions
Q Input Queue Definitions
R Resend Buffer Definitions
S Subscription Definitions
? Help
. Exit
---- --------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit |
The following table describes the options on this menu. To select an option, enter its associated code in the Code field on the screen.
| Code | Allows you to: |
|---|---|
| A | Specify global values for the Adabas Event Replicator Subsystem, identify Adabas databases to which connections should be attempted (or not be attempted), identify the Replicator system file you wish to maintain using the Adabas Event Replicator Subsystem, and load or unload definitions from that Replicator system file if you choose. |
| D | Maintain destination definitions. |
| F | Maintain transaction filter definitions. |
| G | Maintain global format buffer definitions. |
| I | Maintain initial-state definitions. |
| Q | Maintain IQUEUE definitions. |
| R | Maintain resend buffer definitions. |
| S | Maintain subscription definitions. |
| ? | Get help on this menu. |
| . | Exit the Adabas Event Replicator Subsystem. |
You can use the Adabas Event Replicator Subsystem to perform add, copy, modify, and delete replication definitions in a Replicator system file.
The relevant sections describing the individual maintenance tasks are the following:
| Maintaining Initial-State Definitions | Describes maintenance tasks for initial-state definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining Destination Definitions | Describes maintenance tasks for destination definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining Input Queue (IQUEUE) Definitions | Describes maintenance tasks for IQUEUE definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining Resend Buffer Definitions | Describes maintenance tasks for resend buffer definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining Transaction Filter Definitions | Describes maintenance tasks for transaction filter definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining Subscription Definitions | Describes maintenance tasks for subscription definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining SFILE Definitions | Describes maintenance tasks for SFILE definitions using the Adabas Event Replicator Subsystem screens. |
| Maintaining GFB Definitions | Describes maintenance tasks for global format buffer (GFB) definitions using the Adabas Event Replicator Subsystem screens. |
The Event Replicator for Adabas definitions are stored in the Replicator system file associated with a specific Event Replicator Server. While using the Adabas Event Replicator Subsystem, you can:
Change which Replicator system file's definitions you are updating.
Unload Replicator system file definitions to Natural workfile 1.
Load definitions from Natural workfile 1 to a Replicator system file.
Before you attempt any of these functions, verify that all Event Replicator Servers and Replicator system files are defined, as described in Event Replicator for Adabas Installation Steps for z/OS Systems.
This section covers the following topics:
To start working on the replication definitions for a different
Replicator system file and Event Replicator Server:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "S" from the Administration menu.
The System Functions submenu appears.
14:54:26 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
System Functions M-RP1000
Code Function
---- -------------------------------
L Set LFILE Parameters
U Unload Replication Definitions
I Load Replication Definitions
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "L" on the System Functions submenu.
The Set LFILE Parameters screen appears.
14:54:58 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Set LFILE Parameters M-RP1010
Replicator Server DBID ......... _1954
Replicator System File ......... __89
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Save Menu |
Tab to the Replicator Server DBID field and enter the database ID of the Event Replicator Server whose Replicator system file you want to maintain. The database must have been previously defined. For more information on defining an Event Replicator Server, read Event Replicator for Adabas Installation Steps for z/OS Systems.
Tab to the Replicator system file field and enter the number of the Replicator system file you want to maintain. This must be the number of the Replicator system file loaded into the Event Replicator Server you specified in the previous step.
Press PF5 to save your settings.
All updates you make using the Adabas Event Replicator Subsystem will now be made to the Replicator system file you specified on this screen.
This section provides instructions for running the RPULD utility from the Adabas Event Replicator Subsystem. For information on running it in batch mode, read RPULD and RPLOD Utilities.
To unload Replicator system file definitions to Natural
workfile 1:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "S" from the Administration menu.
The System Functions submenu appears.
14:54:26 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
System Functions M-RP1000
Code Function
---- -------------------------------
L Set LFILE Parameters
U Unload Replication Definitions
I Load Replication Definitions
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "U" on the System Functions submenu.
The Unload Replication Objects screen appears.
14:59:47 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Unload Replication Objects RPULD
Entity ........ __
Name .......... *_______
Replicator System File
DBID ....... 1954__ Fnr ........ 89____
Password ... Cipher .....
Options
Unload related objects ......... Y
Only subscriptions of status ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Exec Menu |
Fill in the fields on the Unload Replication Objects screen, as described in the following table.
| Field Name | Instructions | Required? |
|---|---|---|
| Entity | Optionally, identify a specific
definition type
to unload. Valid values are:
If no definition type is selected, all definitions with names that match the Name field specifications are unloaded. |
No |
| Name | Specify
the name of the definitions to select. Wildcards *, >, and < can be used.
For example, AB4* selects all definitions with names starting with
the letters "AB4". As another example,
AB4> selects all definitions with names that sort
(alphanumerically) before names starting with the letters
"AB4".
If no Name specifications are made, all definitions of the types specified by the Entity field are unloaded. |
No |
| DBID | Specify the database ID of the database with the Replicator system file containing definitions you want to unload to Natural workfile 1. | Yes |
| Fnr | Specify the file number of the Replicator system file containing definitions you want to unload to Natural workfile 1. | Yes |
| Password | Specify the password necessary to access the Replicator system file identified in the DBID and Fnr fields. If no password is specified, no password is used to access the Replicator system file. | No |
| Cipher | Specify the cipher code necessary to access the Replicator system file identified in the DBID and Fnr fields. If no cipher code is specified, no cipher code is used to access the Replicator system file. | No |
| Unload related objects | Indicate whether or not related definitions called by a selected definition should also be unloaded. Valid values are "Y" (all related definitions should also be unloaded) or "N" (all related definitions should not be unloaded unless they are selected directly through other field settings). | No |
| Only subscriptions of status | Identify the version of the selected definitions that should be unloaded. Valid values are "C" (current versions) or "S" (scheduled versions). If no value is entered, all versions of the selected definitions are unloaded. | No |
When all fields have been specified appropriately, press the PF5 key to run the program to unload the specified Replicator system file definitions to Natural workfile 1.
This section provides instructions for running the RPLOD utility from the Adabas Event Replicator Subsystem. For information on running it in batch mode, read RPULD and RPLOD Utilities.
To load a Replicator system file with definitions from Natural
workfile 1:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "S" from the Administration menu.
The System Functions submenu appears.
14:54:26 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
System Functions M-RP1000
Code Function
---- -------------------------------
L Set LFILE Parameters
U Unload Replication Definitions
I Load Replication Definitions
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "I" on the System Functions submenu.
The Load Replication Objects screen appears.
15:00:41 ***** A D A B A S REPLICATION SUBSYSTEM ***** 2013-02-28
Load Replication Objects RPLOD
Entity ........ __
Name .......... *_______
Replicator System File
DBID ....... 1954__ Fnr ........ 89____
Password ... Cipher .....
Options
Replace objects ................ N
Only subscriptions of status ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Quit Exec Exit |
Fill in the fields on the Load Replication Objects screen, as described in the following table.
| Field Name | Instructions | Required? |
|---|---|---|
| Entity | Optionally, identify a specific
definition type
to load. Valid values are:
If no definition type is selected, all definitions with names that match the Name field specifications are loaded. |
No |
| Name | Specify
the name of the definitions to select. Wildcards
"*", ">", and
"<" can be used. For example, AB4*
selects all definitions with names starting with the letters
"AB4". As another example, AB4>
selects all definitions with names that sort (alphanumerically) before names
starting with the letters "AB4".
If no Name specifications are made, all definitions of the types specified by the Entity field are loaded. |
No |
| DBID | Specify the database ID of the Replicator system file to which you want to load definitions. | Yes |
| Fnr | Specify the file number of the Replicator system file to which you want to load definitions. | Yes |
| Password | Specify the password necessary to access the Replicator system file identified in the DBID and Fnr fields. If no password is specified, no password is used to access the Replicator system file. | No |
| Cipher | Specify the cipher code necessary to access the Replicator system file identified in the DBID and Fnr fields. If no cipher code is specified, no cipher code is used to access the Replicator system file. | No |
| Replace Objects | Indicate whether or not existing definitions should be replaced with the newly loaded definitions. Valid values are "Y" (existing definitions should be replaced) or "N" (existing definitions should not be replaced). | No |
| Only subscriptions of status | Identify the version of the selected definitions that should be loaded. Valid values are "C" (current versions) or "S" (scheduled versions). If no value is entered, all versions of the selected definitions are loaded. | No |
When all fields have been specified appropriately, press the PF5 key to run the program to load the Replicator system file with the definitions from Natural workfile 1.
By default, Event Replicator for Adabas attempts to connect with any Adabas database encountered during an Event Replicator Server session. You may, however, prefer to control these connection attempts using an Adabas database connection definition. This section describes how to maintain these definitions using the Adabas Event Replicator Subsystem.
To list the connection definitions for Adabas databases in
theAdabas Event Replicator Subsystem:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "D" from the Administration menu.
The Database IDs screen appears showing all of the Adabas database connection definitions in the Adabas Event Replicator Subsystem.
15:01:27 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Database IDs M-RP1160
Sel DBID Connect Sel DBID Connect Sel DBID Connect Sel DBID Connect
---------------- ---------------- ---------------- ----------------
_ 42 Y _ _ _
_ 62 Y _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Add - + Menu |
To add a connection definition for an Adabas database:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option "D" from the Administration menu.
The Database IDs screen appears showing all of the Adabas database connection definitions in the Adabas Event Replicator Subsystem.
Press PF4 on the Database IDs screen.
A dialog appears.
Enter Database ID and Connect
Database ID ..... _____
Connect ......... _ (Y or N)
PF3 to Exit without saving
|
Tab to the Database ID field on the pop-up window and specify the database ID of the Adabas database to which this connection definition applies. This is the equivalent of specifying the DATABASE ID parameter in the Event Replicator Server startup job.
Tab to the Connect field and specify whether or not the Event Replicator Server should initiate an attempt to connect to the Adabas database at Event Replicator Server startup. Valid values are "Y" or "N".
If you specify "Y", the Event Replicator Server will initiate an attempt to connect to the Adabas database after the Event Replicator Server starts.
If you specify "N", the Event Replicator Server will not initiate an attempt to connect to the Adabas database. The database may connect with the Event Replicator Server at some point, but the Event Replicator Server will not initiate the connection at Event Replicator Server startup.
This is the equivalent of specifying the DBCONNECT parameter in the Event Replicator Server startup job.
Press the Enter key to save the connection definition and return to the Database IDs screen.
The database connection definition is added.
To modify a connection definition in the Adabas Event Replicator Subsystem:
List the connection definitions in the Adabas Event Replicator Subsystem, as described in Listing Adabas Database Connection Definitions.
The destinations are listed on the Database IDs screen.
Locate the definition you want to modify on the screen and enter an M in the Sel column for that definition.
A dialog pops up displaying the settings for the connection definition you selected. For information on modifying this screen, read the description of Adding a Connection Setting for an Adabas Database.
When all modifications have been made, press Enter to save the changes and return to the Database IDs screen.
You can use Adabas Online System (AOS) to activate and deactivate databases or individual files within a database. For more information, read Activating and Deactivating Replication Definitions and Databases
 |
Warning: Be careful when you activate and deactivate replication definitions and databases, especially if replication is ongoing at the time. Whenever you activate or deactivate definitions or databases, you run the risk of altering what data is replicated and how that replication occurs. If the Event Replicator Server receives data from an Adabas database for which it has no active definitions, replication simply does not occur. |
To copy a connection definition in the Adabas Event Replicator Subsystem:
List the connection definitions in the Adabas Event Replicator Subsystem, as described in Listing Adabas Database Connection Definitions.
The destinations are listed on the Database IDs screen.
Locate the definition you want to copy on the screen and enter a C in the Sel column for that definition.
A dialog appears.
Enter Database ID and Connect
Database ID ..... ___12
Connect ......... N (Y or N)
PF3 to Exit without saving
|
Specify a new, unique Adabas database ID for the copy of the definition and press Enter.
The connection definition is copied and the copy appears on the Database IDs screen.
To delete a connection definition in the Adabas Event Replicator Subsystem:
List the connection definitions in the Adabas Event Replicator Subsystem, as described in Listing Adabas Database Connection Definitions.
The destinations are listed on the Database IDs screen.
Locate the definition you want to delete on the screen and enter a D in the Sel column for that definition.
A pop-up dialog appears prompting you to indicate whether you really want the definition deleted or not.
Delete 10? (Y or N) _
(PF3 to exit without deleting)
|
Specify either "Y" or "N" to indicate whether you really want the definition deleted. Then press Enter.
The definition is deleted if you specify "Y"; otherwise it is not.
In addition to submitting requests for initial-state data from your application, you can submit initial-state requests from the Adabas Event Replicator Subsystem. (For information on submitting initial-state data requests from your application, read Event Replicator Client Requests.)
To submit a request for initial-state data from the
Adabas Event Replicator Subsystem:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option from the Adabas Event Replicator Subsystem Administration menu.
The Perform Initial-State screen appears.
15:03:47 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Perform Initial-State M-RP4010
Please enter the Initial-State name ________
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Sel Menu |
Type the name of the initial-state definition you want used to populate the database and press Enter. You can also use the PF6 function key to select an initial-state definition from a list of the available definitions.
The Perform Initial-State screen appears.
15:04:41 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Perform Initial-State M-RP4012
Initial-State Name ....... I040155
Sel IDBID IFile I Selection Criteria or ISN List
--- ------ ----- - ------------------------------------------------------------
_ + 40 155 I
_
_
_
_
_
_
_
_
_
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Sub Menu |
The Perform Initial-State screen lists all of the files in the initial-state definition. All files that are ready to have the initial-state run on their data appear in the list with a plus sign (+) before their associated database ID (IDBID field). If they are not ready, a plus sign does not appear.
If any files in this list require an ISN filter (they appear in the list with an "I" in the I column), they will not be ready for the initial-state run until you specify an ISN or ISN list. To do this, complete the following steps:
Type an "E" in the Sel column corresponding to the file that requires an ISN filter.
A Specify ISNs screen appears.
15:04:41 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Specify ISNs M-RP4013
Initial-State Name ....... I040155
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Accpt Menu |
On the blank lines on this screen, type in the ISN or list of ISNs you want to use as a filter for the file. Separate multiple ISNs using commas (no blanks). If you want to specify a range of ISNs, specify them in ascending order in matched (open and closed) parentheses. For example, the following ISN list selects ISNs 111 and 222, all the ISNs between 333 and 666, and ISN 9999.
111,222,(333,666),9999
When all ISNs have been specified as you like, press the PF5 function key to accept the list and return to the Perform Initial-State screen.
If any files in this list require a value buffer (they appear in the list with an "S" in the I column), they will not be ready for the initial-state run until you specify value buffer. To do this, complete the following steps:
Type an "E" in the Sel column corresponding to the file that requires a value buffer.
A Specify Value Buffer screen appears.
15:04:41 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2013-02-28
Specify Value Buffer M-RP4015
Initial-State Name ....... I040155 Value Buffer Length....... _____
______________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Mode Accpt Menu |
On the blank lines on this screen, type in the value buffer, using all of the characters required by each field in the corresponding initial-state definition's search buffer. Use blanks to fill out the values in the value buffer for each field specified by the search buffer. For example, if a field in the search buffer can be ten bytes long, but the actual value is only three bytes long, use blanks to fill out the remaining seven bytes in the value buffer specification.
Note:
You can use the PF4 function key to select character or
hexadecimal mode.
In the Value Buffer Length field, specify the total length of the value buffer. Be sure to get this total from the total possible sizes of all the fields in the search buffer. This field is required.
When the value buffer and length have been specified as needed, press the PF5 function key to accept it and return to the Perform Initial-State screen.
When all files have a plus sign (+) in front of them, press the PF5 function key to submit the initial-state request. Messages will appear describing the success or failure of the request.
You can set the following global values in the Replicator system file using the Adabas Event Replicator Subsystem screens.
To set global values for the Adabas Event Replicator Subsystem:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option from the Adabas Event Replicator Subsystem Administration menu.
The Global Values screens appear.
15:46:32 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2018-08-13
Global Values M-RP1110
---------- General Values ----------- ----------- General Values -----------
Subtasks ................. ___0 EntireX Broker Stub Name .. BROKER__
Max Output Size .......... ____100000 Verify Mode ............... N
Input Request Msg Limit .. ________10 Format Buffer Validation .. N
Input Request Msg Intrvl . ________60 Record PLOG information ... N
Max Record Size .......... _____32767 Log Input Transaction ..... 080
Max Variable Record Size . _____32767 Subtask Activation Wait ... __10
Retry Interval............ _________0 Open at Start ............. Y
Retry Count............... ________10 Num Parallel Adabas Calls . _3
SLOGCHECKINTERVAL ........ _________0 Queue Full Delay .......... _60
ASSOTHRESHOLD ........... _80 STATINTERVAL .............. _________0
DATATHRESHOLD ........... _80 Log Output Transaction .... NO_
SLOGACTHRESHOLD ......... _70
SLOGDSTHRESHOLD ......... _70
SLOGNITHRESHOLD ......... _70
SLOGUITHRESHOLD ......... _70
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Save + Menu |
15:46:54 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2018-08-13
Global Values M-RP1110
-------- TLOG Values ------------
Maximum RPL Usage ........ _50 %
Restart RPL Usage ......... 40 %
Input Queue Level ............ 0
No Match Level ............... 0
Queue Completion Level ....... 0
Completion Level ............. 0
Request Received Level ....... 0
Request Rejected Level ....... 0
Request Error Level .......... 0
Status Request Level ......... 0
I-State Start Request Level .. 0
I-State Completion Level ..... 0
Retransmit Request Level ..... 0
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Save - Menu |
Update the global parameters on this screen as described in the following table.
| Parameter Name | Specify | Default |
|---|---|---|
| Completion Level | The level of transaction logging that should occur when a transaction has been fully processed and Adabas has been informed that the transaction was successfully replicated. Valid values are "0" (no logging) or "1" (log event and input transaction data). This is the equivalent of specifying the TLCOMP parameter directly in the Event Replicator Server startup job. | 0 |
| EntireX Broker Stub Name | The default EntireX Broker stub name to be used by the Event Replicator Server if no other name is specified. This is the same as specifying the ETBBROKERNAME parameter directly in the Event Replicator Server startup job. EntireX Broker is a component of webMethods EntireX. | BROKER |
| Format Buffer Validation | Indicates the level of format
buffer validation that should occur for subscriptions. Valid values are a
blank, "A", "D",
"N", or "W".
This is the same as specifying the FBVALIDATION parameter directly in the Event Replicator Server startup job. |
N |
| I-State Completion Level | The level of transaction logging that should occur when an initial-state information request has completed. Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI, if available), or "3" (log event, URBS, and URBI, if available). This is the equivalent of specifying the TLISTATECOMP parameter in the Event Replicator Server startup job. | 0 |
| I-State Start Request Level | The level of transaction logging that should occur when a user request for initial-state information for a file has started. Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI). This is the equivalent of specifying the TLISTATE parameter in the Event Replicator Server startup job. | 0 |
| Input Queue Level | The level of transaction logging that should occur when a transaction is taken off the input queue and put on the transaction assignment queue. Valid values are "0" (no logging), "1" (log event and input transaction data), "2" (log event, input transaction, and file/ record information), or "3" (log event and all available input information for the event). This is the equivalent of specifying the TLINPUT parameter in the Event Replicator Server startup job. | 0 |
| Input Request Msg Interval | The interval during which the message limit specified by the Input Request Message Limit field applies. This is the equivalent of specifying the IRMSGINTERVAL parameter directly in the Event Replicator Server startup job. | 60 |
| Input Request Msg Limit | The maximum number of input request error messages issued by the Event Replicator Server during the interval set by the Input Request Message Interval field (also on this screen). This is the equivalent of specifying the IRMSGLIMIT parameter directly in the Event Replicator Server startup job. | 10 |
| Log Input Transaction |
Whether or not the Event Replicator should use its SLOG system file as a temporary storage location for incoming compressed replication transactions, before they are queued for processing. Once transactions have been written to the SLOG system file, the Event Replicator Server processes them using a throttling mechanism so that only a limited amount of Event Replicator Server replication pool space is used at a time. Valid values are
This is the equivalent of specifying the LOGINPUTTRANSACTION parameter directly in the Event Replicator Server startup job. |
NO |
| Log Output Transaction |
Whether or not the Event Replicator should use its SLOG system file as a temporary storage location for output items, before they are queued for processing. Once output items have been written to the SLOG system file, the Event Replicator Server processes them using a throttling mechanism so that only a limited amount of Event Replicator Server replication pool space is used at a time. Valid values are
This is the equivalent of specifying the LOGOUTPUTTRANSACTION parameter directly in the Event Replicator Server startup job. |
NO |
| Max Output Size | The maximum output message size for
the Event Replicator for Adabas. This is the equivalent of specifying the
MAXOUTPUTSIZE parameter directly in
the Event Replicator Server startup job. The minimum value you can specify for this field is
32768.
This parameter may be specified in bytes or it may be specified with the suffix K to indicate kilobytes. The maximum value is 2,147,483,647 bytes. The practical maximum is limited by the region size of the Event Replicator Server. One output buffer is acquired for each output task. |
100,000 |
| Max Record Size | The maximum length (in bytes) of
any decompressed record that can be processed by the Event Replicator Server. This is the
equivalent of specifying the MAXRECORDSIZE parameter directly in
the startup job.
The minimum value you can specify for this field is 1. For an Event Replicator Server running with Adabas 7, the maximum value that can be specified for MAXRECORDSIZE is 32,767 bytes. However, in Adabas 8 systems, this limit has been lifted; the size of a decompressed record may be much larger than 32,767 bytes. Therefore, for an Event Replicator Server running with Adabas 8, the maximum value that can be specified for MAXRECORDSIZE is the larger of either 32,767 bytes or 50% of the setting of the ADARUN LRPL parameter. |
32,767 bytes |
| Max Variable Record Size | The maximum length (in bytes) of
variable decompressed records that can be processed by the Event Replicator Server. This is
the equivalent of specifying the
MAXVARRECORDSIZE parameter directly in
the startup job.
The value specified for MAXVARRECORDSIZE must be less than or equal to the setting of the MAXRECORDSIZE setting. The minimum value you can specify for this field is 1. For an Event Replicator Server running with Adabas 7, the maximum value that can be specified for MAXRECORDSIZE or MAXVARRECORDSIZE is 32,767 bytes. However, in Adabas 8 systems, this limit has been lifted; the size of a decompressed record may be much larger than 32,767 bytes. Therefore, for an Event Replicator Server running with Adabas 8, the maximum value that can be specified for MAXRECORDSIZE or MAXVARRECORDSIZE is the larger of either 32,767 bytes or 50% of the setting of the ADARUN LRPL parameter. |
32,767 bytes |
| Maximum RPL Usage | The maximum percentage of the Event Replicator Server replication pool that can be used for transaction log (TLOG) processing. Valid values range from "0" through "100". This is the equivalent of specifying the TLMAX parameter in the Event Replicator Server startup job. | 50 |
| No Match Level | The level of transaction logging that should occur when a transaction is not queued to any subscription in the Event Replicator Server. Valid values are "0" (no logging), "1" (log event and input transaction data), "2" (log event, input transaction, and file/record information), or "3" (log event and all available input information for the event). This is the equivalent of specifying the TLNOSUB parameter in the Event Replicator Server startup job. | 0 |
| Num Parallel Adabas Calls | The maximum number of parallel
Adabas calls that can be made. Valid values are integers in the range from 1
through 50. Use this parameter to improve throughput of data replication to
your Adabas destinations.
This is the equivalent of specifying the NPADACALLS parameter in the Event Replicator Server startup job. |
3 |
| Open at Start | Indicates whether or not
destinations with Open at Start (DOPEN) set to
"G" or input queues with Open
Queue at Start (IQOPEN) set to "GLOBAL"
in their definitions should be opened at Event Replicator Server startup. This parameter
specifies the global policy for determining whether destinations with
Open at Start set to
"G" or input queues with Open
Queue at Start set to "GLOBAL" are opened
at Event Replicator Server startup. Valid values are "Y" or
"N", with "Y" as the
default.
When this parameter is set to "Y", any destinations with Open at Start set to "G" or input queues with Open Queue at Start set to "GLOBAL" are opened at Event Replicator Server startup. When this parameter is set to "N", any destinations with Open at Start set to "G" or input queues with Open Queue at Start set to "GLOBAL" are not opened at Event Replicator Server startup. This is the equivalent of specifying the GOPEN parameter in the Event Replicator Server startup job. |
Y |
| Queue Completion Level | The level of transaction logging that should occur prior to a transaction being assigned to the completion queue. Valid values are "0" (no logging), "1" (log event and input transaction data, "2" (log event, input transaction, and file/record information), or "3" (log event and all input information available for the event). This is the same as specifying the TLQCOMP parameter directly in the Event Replicator Server startup job. | 0 |
| Queue Full Delay | The number of seconds between retry
attempts when resending output transactions to a previously-full webMethods
EntireX or MQSeries destination. Valid values are integers in the range from
"5" through "300".
This is the same as specifying the GQFULLDELAY parameter directly in the Event Replicator Server startup job. |
60 |
| Record PLOG Information | Indicates whether or not PLOG
information is saved in the Replicator system file. Valid values are
"Y" (store the information) or
"N" (do not store the information). This is the same
as specifying the RECORDPLOGINFO parameter directly in
the Event Replicator Server startup job.
If you plan on using the automated replay facility provided with Event Replicator, you must set this parameter to "Y". The related information is collected when the source Adabas nucleus processes the SYNP checkpoint created by ADARES PLCOPY. Note: |
N |
| Request Error Level | The level of transaction logging that should occur when a user request is rejected due to an error in carrying out the request. Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI). This is the equivalent of specifying the TLREQERR parameter in the Event Replicator Server startup job. | 0 |
| Request Received Level | The level of transaction logging that should occur when a user request has been received. Valid values are "0" (no logging), "1" (log event but no data), or "2" (log event and the entire input buffer before and after translation if appropriate). This is the equivalent of specifying the TLREQRECV parameter in the Event Replicator Server startup job. | 0 |
| Request Rejected Level | The level of transaction logging that should occur when a user request is rejected due to an error in interpreting the request. Valid values are "0" (no logging), "1" (log event but no data), or "2" (log event, error code, and entire input buffer). This is the equivalent of specifying the TLREQREJECT parameter in the Event Replicator Server startup job. | 0 |
| Restart RPL Usage | The amount of available Event Replicator Server replication pool storage that must be available before transaction logging (TLOG logging) can restart. Valid values range from "0" through "99". This is the equivalent of specifying the TLRESTART parameter in the Event Replicator Server startup job. | 40 |
| Retransmit Request Level | The level of transaction logging that should occur when a user request to retransmit a specific transaction has been processed. Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI). This is the equivalent of specifying the TLRETRANS parameter in the Event Replicator Server startup job. | 0 |
| Retry Count | The default number of times that an
attempt to open a destination or input queue will be retried at the interval
specified by the Retry Interval parameter. This is the equivalent of specifying
the RETRYCOUNT parameter in the Event Replicator Server
startup job. Valid values range from 0 through 2,147,483,647.
A value of zero indicates that no retry processing should occur for any affected destinations. |
10 |
| Retry Interval | The default number of seconds
between retry attempts that will be performed for any destination on input
queue for which no specific retry interval has been specified. This is the
equivalent of specifying the RETRYINTERVAL parameter in the
Event Replicator Server startup job. Valid values range from 0 through 2,147,483,647.
A value of zero indicates that no retry processing should occur for any affected destinations. |
0 |
| SLOGCHECKINTERVAL |
The interval (in minutes) between checks of the Associator and Data file space usage. The
Once a value is specified, the settings of the
thresholds specified by the |
0 |
| ASSOTHRESHOLD |
The percentage of the Event Replicator database Associator space that can be used before threshold warning messages are issued. Associator space usage must meet or exceed this threshold value to trigger the warning messages. Valid values are 0-100. The
Note: |
80 |
| DATATHRESHOLD |
The percentage of the Event Replicator database Data space that can be used before threshold warning messages are issued. Data space usage must meet or exceed this threshold value to trigger the warning messages. Valid values are 0-100. The
Note: |
80 |
| SLOGACTHRESHOLD |
The percentage of the SLOG address converter space that can be used before threshold warning messages are issued. Address converter space usage must meet or exceed this threshold value to trigger the warning messages. Valid values are 0-100. The
(TOPISN-MINISN+1)/(MAXISN-MINISN+1) If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG address converter space. Note: |
70 |
| SLOGDSTHRESHOLD |
The percentage of the SLOG Data Storage space that can be used before threshold warning messages are issued. Data Storage space usage must meet or exceed this threshold value to trigger the warning messages. Valid values are 0-100. The
(acyl - uncyl - unbytes) / acyl If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG Data space. Note: |
70 |
| SLOGNITHRESHOLD |
The percentage of the SLOG normal index space that can be used before threshold warning messages are issued. Normal index space usage must meet or exceed this threshold value to trigger the warning messages. Valid values are 0-100. The
(ucyl / acyl) If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG normal index space. Note: |
70 |
| SLOGUITHRESHOLD |
The percentage of the SLOG upper index space that can be used before threshold warning messages are issued. Upper index space usage must meet or exceed this threshold value to trigger the warning messages. Valid values are 0-100. The
(ucyl / acyl) If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG upper index space. Note: |
70 |
| STATINTERVAL |
The interval (in seconds) at which Event Replicator statistics should be published by the Event Replicator Server. Valid values are 0, or any numbers in the range of 60 to 86400 (24 hours). The |
0 |
| Status Request Level | The level of transaction logging that should occur when a user request for status on an Event Replicator Server resource has been processed. Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI). This is the equivalent of specifying the TLSTATUS parameter in the Event Replicator Server startup job. | 0 |
| Subtask Activation Wait | The number of seconds that can be used to override the default time to wait for a subtask to finish initialization and activate. Valid values are from 1 to 3600 seconds. This is the equivalent of specifying the SUBTASKWAIT parameter in the Event Replicator Server startup job. | 10 |
| Subtasks | The number of subtasks in the Event Replicator Server. This is the equivalent of specifying the SUBTASKS parameter in the Event Replicator Server startup job. | 3 |
| Verify Mode | Whether the Event Replicator for Adabas should run in verify (test) mode or not. Valid values are "Y" (run in verify mode) or "N" (do not run in verify mode). This is the equivalent of specifying the VERIFYMODE parameter in the Event Replicator Server startup job. | N |
Press PF5 to save your settings.
You can directly access SYSAOS Replicator Management, using the Replicator DBID as the Database ID.
To access SYSAOS Replicator Management:
Select option from the Adabas Event Replicator Subsystem Main Menu.
The Administration menu appears.
19:30:31 ***** A D A B A S EVENT REPLICATOR SUBSYSTEM ***** 2017-03-15
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
X SYSAOS Replicator Management
? Help
. Exit
---- -------------------------------
Code ... _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select option from the Adabas Event Replicator Subsystem Administration menu.
The Replicator Management screen appears.
19:52:15 ***** A D A B A S BASIC SERVICES ***** 2017-03-15
Replicator 1954 - Replicator Management - PRPT002
Code Service
---- --------------------------
A Activate/deact/open/close
D Display Reptor definitions
F Display Reptor statistics
H Perform RPLCheck
L Perform RPLCleanup
P Perform RPLRefresh
R Parameter subsystem
? Help
. Exit
---- --------------------------
Code ......... _
Database ID .. 1954 (REP1954)
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help File Serv Exit Menu |
View or update the parameters on this screen as described in section Managing Replication from AOS.
If you enter option in this screen, you will be taken to the Parameter subsystem main menu of SYSRPTR.
Online help is provided for every Adabas Event Replicator Subsystem screen and message that appears in the Adabas Event Replicator Subsystem. This section covers the following topics:
To get screen-level help for any Adabas Event Replicator Subsystem screen:
Be sure the screen you want help for is displayed. Navigate to it if you need to.
Press the PF1 key.
Help for the screen displays.
To get help for Adabas Event Replicator Subsystem messages:
At the Command prompt, enter:
msg nnn
where nn is the valid two- or three-digit message number (omit the leading zeros). For example, to get help on message ARF00013, you would enter:
msg 13
The following table describes the function keys available while using the Adabas Event Replicator Subsystem screens. Note that not all function keys are available on all screens and some PF keys have meanings only to specific screens (these PF keys are not described here, but are described with the screen to which they apply).
| Function Key | Display Title | Description |
|---|---|---|
| PF1 | Help | Provides help on the current screen. |
| PF2 | Repos | Displays a pop-up screen allowing you to specify the definition name to which you want a list of definitions repositioned. This is useful if you have many definitions listed on one of the Adabas Event Replicator Subsystem list screens. |
| PF3 | Exit |
Exits the current screen without saving any changes you might have made. If the current screen is the Main Menu, this function key has no effect. |
| PF4 | Add | Displays a screen that allows you to add a definition. |
| PF5 | Save or Exec | Saves the changes you have made or allows you to execute the program corresponding to the Adabas Event Replicator Subsystem screen displayed. |
| PF7 | - | Scrolls backwards through the data on a screen. |
| PF8 | + | Scrolls forward through the data on a screen. |
| PF12 | Menu | Leaves the Adabas Event Replicator Subsystem screens. |
To leave the Adabas Event Replicator Subsystem screens, press PF12 from any screen. If you are on a menu screen in the Adabas Event Replicator Subsystem, you can select the dot (.) option to leave.
Note:
When you leave the Adabas Event Replicator Subsystem screens, any modifications to the
subsystem since the last save will not be stored.