Skip to Main Content
ADD A NEW IDEA

Event Replicator Server (ARF)

Showing 11 of 401

Securing online Event Replicator functions

As suggested in Support Incident 5220314, we would like to use ADASAF to secure Event Replicator Subsystem functions as is currently done with AOS. Specifically, we would like to secure access to SYSRPTR, as well as Administration Functions - Data...
Guest almost 3 years ago in Adabas for z/OS / Event Replicator Server (ARF) / Security 0 Under development

Long-Alpha field support in Replicator

“ADABAS currently supports Long-Alpha fields. We are now using Replicator to replicate from our Adabas files into Sql Server tables. Unfortunately at this time, Replicator does not seem to support replicating the long alpha fields. We would like t...
David Wilbur almost 2 years ago in Adabas for z/OS / Adabas (ADA-zOS) / Event Replicator Server (ARF) 0 New

Introduce a grace period for the DCOMMITTHRESHOLD.

Introduce a new feature and parameter DCOMMITWAIT which will have the REPTOR not commit messages with less than DCOMMITTHRESHOLD transactions until DCOMMITWAIT milliseconds have passed. While it will introduce a small delay - it will allow greater...
Bjarne Soerensen almost 2 years ago in Adabas for z/OS / Event Replicator Server (ARF) 0 New

Message if REPLICATION gets turned on/off for a file

When working with the Event Replicator for Adabas you can turn replication on and of for certain Adabas files. A change of the status of the file is logged in the checkpoint file of the database. However, there's no message in DDPRINT, Job-Output ...
Hermann Pfeiffer almost 3 years ago in Adabas for z/OS / Event Replicator Server (ARF) / Security 0 Future consideration

Feature to shut down REPTOR waiting first for all source nuclei to disconnect

Issuing ADAEND to a REPTOR should not be done before the connected source nuclei have ended. When shutting down a production environment (typically before an IPL) - you can automate that the source nuclei (EG DB1,DB2,DB3) tasks have ended before A...
Bjarne Soerensen 9 days ago in Adabas for z/OS / Event Replicator Server (ARF) 0 New

Deactivate subscription on ADAF7F to avoid inconsistent target.

The message ADAF7F is issued when a response code comes from the decompression of a record. Such errors can be sporadic in the case of rsp 42/2 caused by a too small LFP. As a result - sporadically - changed records are not replicated. This causin...
Bjarne Soerensen about 2 months ago in Adabas for z/OS / Event Replicator Server (ARF) 0 New

Change misleading messages for SLOGging.

The messages "ADAFRX SLOG turned on for destination dest-name" and "ADAFRY SLOG turned off for destination dest-name" are misleading. They indicate that the SLOG parameter has been turned on or off - which would impact the replication consistency....
Bjarne Soerensen 10 months ago in Adabas for z/OS / Event Replicator Server (ARF) 0 New

Allow user-defined name for target structure.

If a GFB is generated from PREDICT for SAGTARG destination - the target structure name will be that of the imported structure - like "ADDRESS-U". If you want to change the target structure name to EG "ADDR" - you have to change it with the Data Ma...
Bjarne Soerensen 12 months ago in Adabas for z/OS / Event Replicator Server (ARF) 0 New

Enable checking of parameter consistency in SYSRPTR

Event Replicator for Adabas Please develop a function in SYSPRTR to check the consistency of the configuration as held in LFILE. To be used after changing the configuration to ensure that the next ARK starting will not immediately crash with EG. A...
Bjarne Soerensen almost 3 years ago in Adabas for z/OS / Event Replicator Server (ARF) 0 Under Review

Add Direct Commands to SYSRPTR application

Similar to applications like SYSAOS and SYSDIC, SYSRPTR would benefit greatly if it supported direct commands. For example, GEN GFB NAME=G054151 FILE-ID=EMPLOYEES-FILE ADA-VER=I9 OCCUR=YES FULL-FORMAT=YES [OVERWRITE]. This would allow the creation...
Wayne Campos almost 3 years ago in Adabas for z/OS / Event Replicator Server (ARF) 0 Future consideration