Replicator and the Network

, , , ,
1

Based on very slow replication (SLOG piled up - 20 replications per second - unstable Reptor) of mass data from Adabas on the mainframe to Adabas on Windows, I would like to know the following:

  1. Is the Adabas Event Replicator latency sensitive and what are acceptable latency thresholds to keep the application from backlogging significantly enough to cause the mainframe process to become unstable?

  2. Does the Replicator employ any slow start methodology or other way to optimize network performance?

  3. How does the Replicator handle lost data within the replication stream or lost/retransmitted TCP/UDP packets?

  4. Considering the Replicator, can the data sent between the host and client be safely encrypted with IPSec?

  5. Do you have other customers successfully using the Replicator over an IPSec VPN tunnel?

ADABAS 8.1.3
ADABAS 6
Replicator ARF 3.1.1
WCP 6.1

Thanks,
Dieter Storr

2

Hi Dieter

The event replicator is designed not to impact the mainframe source process.
If the target can not keep up with the load, replication can be written to SLOG instead and the assumption is that this should be faster than the source can create new replication data.
However, there have been enhancements and important corrections in ARF321, which addresses problems in this area and I recommend that you move to this version
The questions you raise with regard to Net-work issues are to the wrong product
Reptor uses WCP like any other Adabas client
Currently the reptor does not do special optimizations
In future it is likely that there will be optimizations like multicalls etc.
Lost data is handled by the Net-work protocol, not by the client (reptor)
Encryption (e.g. SSL in Version 6.2) must again be supported by the Net-work version not by the client.
So check the version of your net-work documentation what is supported.

Rainer Herrmann

3

Hi Rainer,

Thank you for the information.

We are on ARF321, sorry for the typo.

And it seems that the Reptor is overwhelmed with work and stops communicating with SYSAOS and ADAREP, for example.

I will post the same questions to the WCP forum.

Dieter Storr

ADABAS 8.1.3
ADABAS 6
Replicator ARF 3.2.1
WCP 6.1

4

Hi Dieter,

please check whether you have
AZ321048 and AZ321049 applied to your reptor.

They are fairly new and describe a CPU problem the reptor can run into during high load situation during the input phase.

You may or may not have run into this problem.

Cheers
Rainer

5

Hi Rainer,

Thanks for the ZAP info. We will apply the recommended ZAPS.

ADARPS Date 2009-02-20, Version 3.2, SM 1, Base AZ321000
Zaps AZ321008 AZ321009 AZ321010 AZ321012 AZ321015
AZ321017 AZ321019 AZ321020 AZ321022 AZ321026
AZ321035
ADARAG Date 2006-06-09, Version 8.1, SM 3, Base AO813000
Zaps AO813020
ADARPD Date 2009-02-20, Version 3.2, SM 1, Base AZ321000
Zaps AZ321006 AZ321023
ADARPT Date 2009-02-20, Version 3.2, SM 1, Base AZ321000

Gruss aus Sacramento,
Dieter