# Millions of error messages if the receiver is not available

**URL:** <https://techcommunity.softwareag.com/t/millions-of-error-messages-if-the-receiver-is-not-available/79501>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Windows-UNIX, Adabas-Add-on-Products, Event-Replicator-for-Adabas\
**Created:** [November 15, 2008, 7:18am UTC](https://techcommunity.softwareag.com/t/millions-of-error-messages-if-the-receiver-is-not-available/79501 "2008-11-15T07:18:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dieter\_W\_Storr](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/dieter_w_storr/32/91_2.png) [@Dieter\_W\_Storr](https://techcommunity.softwareag.com/u/Dieter_W_Storr)\
**Post date:** [November 15, 2008, 7:18am UTC](https://techcommunity.softwareag.com/t/millions-of-error-messages-if-the-receiver-is-not-available/79501/1 "2008-11-15T07:18:00Z")

</div>

We replicate 150 million records from the mainframe (ADABAS) to Windows (ADABAS) and the replication server is located on the mainframe also.

If the replication fails, for example ADABAS on Windows is not available or the network is down, the replication server is sending out millions of error messages, 12 lines of output for one failed record.

How can we suppress these amount of error messages and avoid that the replication server will abend. OK, dummy is one possibility.

ADAF18 OP cmd to DBID 187 FNR RSP 148 subcode 16448  
ADAF54 2008-11-04 00:15:24 Replication error: Adabas destination D187044  
ADAF54 Source DBID 134 FNR 44, Target DBID 187 FNR 44  
ADAF18 A1 cmd to DBID 187 FNR 44 RSP 148 subcode 16448 ISN 143917916  
ADAF54 2008-11-04 00:15:24 Replication error: Adabas destination D187044  
ADAF54 Source DBID 134 FNR 44, Target DBID 187 FNR 44  
ADAF18 ET cmd to DBID 187 FNR RSP 148 subcode 16448  
ADAF54 2008-11-04 00:15:24 Replication error: Adabas destination D187044  
ADAF54 Source DBID 134 FNR 44, Target DBID 187 FNR 44  
ADAF18 CL cmd to DBID 187 FNR RSP 148 subcode 16448  
ADAF54 2008-11-04 00:15:47 Replication error: Adabas destination D187044  
ADAF54 Source DBID 134 FNR 44, Target DBID 187 FNR 44

Is this a feature or an error or an forgotten parameter?

Thanks,  
Dieter Storr

---

<div class="post-metadata">

**Author:** ![Marbod\_Mueller1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/marbod_mueller1/32/97_2.png) [@Marbod\_Mueller1](https://techcommunity.softwareag.com/u/Marbod_Mueller1)\
**Post date:** [November 17, 2008, 8:49pm UTC](https://techcommunity.softwareag.com/t/millions-of-error-messages-if-the-receiver-is-not-available/79501/2 "2008-11-17T20:49:41Z")

</div>

Hello Herr Storr,

there are destination parameters to change the reaction on target errors.  
On DAERROR=ALTACTION (default) processing continues with the next update in the transaction.

I would recommend using DAERROR=CLOSE because it doesn’t make sense to continue endlessly. With CLOSE the destination is closed and updates will be logged in the Reptor (DLOG=YES).

With DRETRYCOUNT and DRETRYINTERVAL parameters you can set wait time and how often a retry should be undertaken to reopen the destination and resume replication.

As an example a complete set of parameters for a destination:

ADARPD DESTINATION NAME=ADA1  
ADARPD DTYPE=ADABAS  
ADARPD DLOG=YES  
ADARPD DAERROR=CLOSE,DRETRYCOUNT=4,DRETRYINTERVAL=15  
ADARPD DAIFILE=16,DAIDBID=8,DATDBID=12,DATFILE=16

HTH,  
Marbod Mueller

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:51pm UTC](https://techcommunity.softwareag.com/t/millions-of-error-messages-if-the-receiver-is-not-available/79501/3 "2021-04-02T14:51:09Z")

</div>