If the target database sends back Adabas response code 153, the Replicator lost some records, which were part of a transaction.
The path of replication:
- Source or subscription database on the mainframe Adabas V8.1.3
- Replicator for Adabas on the mainframe V8.1.3 and 3.2.1
- Entire Net-Work (WCP) on the mainframe V6.2.1
- Entire Net-Work (WCP) on Windows V7.3.3
- Target database Adabas on Windows V6.2.1.1
During the replication and each hour, another batch job is pinging from the mainframe the target database (read one record / L1) to make sure the connection is OK. This job receives RC153 but this response code cannot be found in the command log of the target database.
DDPRINT of Reptor displays:
11:07:34 ADAF54 00302 Replication error: Adabas destination D251011
11:07:34 ADAF54 00302 Source DBID 39 FNR 11, Target DBID 251 FNR 11
ADAF18 N2 cmd to DBID 251 FNR 11 RSP 153 subcode 16448 ISN 75423
13:00:04 ADAF54 00302 Replication error: Adabas destination D251044
13:00:04 ADAF54 00302 Source DBID 39 FNR 44, Target DBID 251 FNR 44
ADAF18 N2 cmd to DBID 251 FNR 44 RSP 153 subcode 16448 ISN 522015
ADAF54 2010-11-22 13:00:04 Replication error: Adabas destination D251044
ADAF54 Source DBID 39 FNR 44, Target DBID 251 FNR 44
ADAF18 N2 cmd to DBID 251 FNR 44 RSP 153 subcode 16448 ISN 522016
ADAF54 2010-11-22 13:00:04 Replication error: Adabas destination D251044
ADAF54 Source DBID 39 FNR 44, Target DBID 251 FNR 44
ADAF18 N2 cmd to DBID 251 FNR 44 RSP 153 subcode 16448 ISN 522017
ADAF54 2010-11-22 13:00:04 Replication error: Adabas destination D251044
ADAF54 Source DBID 39 FNR 44, Target DBID 251 FNR 44
ADAF18 N2 cmd to DBID 251 FNR 44 RSP 153 subcode 16448 ISN 522018
ADAF54 2010-11-22 13:00:04 Replication error: Adabas destination D251044
ADAF54 Source DBID 39 FNR 44, Target DBID 251 FNR 44
ADAF18 N2 cmd to DBID 251 FNR 44 RSP 153 subcode 16448 ISN 522019
Command Log:
DATE DURATION USER-ID NODE-ID LOGIN-ID CMD RSP AD2(HEX)/AD2 COP X FILE ISN TH IOA IOD IOW
(snip)
2713174 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 00000140/@… 44 522008 7 0 0 0
2713175 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013B/;… 44 522009 2 0 0 0
2713176 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013E/>… 44 522010 15 0 0 0
2713177 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 00000135/5… 44 522011 6 0 0 0
2713178 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013C/<… 44 522012 13 0 0 0
2713179 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 00000140/@… 44 522013 4 0 0 0
2713180 22-NOV-2010 13:00:05 0 STCHK251 …B…B. …/~… OP 0 00000000/… … 0 0 5 0 0 0
2713181 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013C/<… 44 522014 14 0 0 0
2713182 22-NOV-2010 13:00:05 62 STCHK251 …B…B. …/~… L1 0 003A012B/+.:. .I 44 1 9 1 1 0
2713183 22-NOV-2010 13:00:05 0 STCHK251 …B…B. …/~… RC 0 00000000/… SI 0 0 20 0 0 0
2713184 22-NOV-2010 13:00:05 0 STCHK251 …B…B. …/~… RC 0 00000000/… F. 0 0 12 0 0 0
2713185 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013B/;… 44 522030 10 0 0 0
2713186 22-NOV-2010 13:00:05 0 STCHK251 …B…B. …/~… CL 0 00000000/… … 0 0 17 0 0 0
2713187 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 00000150/P… 44 522031 3 0 0 0
2713188 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 00000150/P… 44 522032 19 0 0 0
2713189 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013F/?.. 44 522033 16 0 0 0
2713190 22-NOV-2010 13:00:05 0 …B…B. …~… N2 0 0000013D/=… 44 522034 8 0 0 0
(snip)
Another customer receives also the RC153 if two batch jobs read the target database and NO replication takes place.
All customers can repeat the error. Maybe SAG should do the same?
Now, two customers are very concerned to continue with production replication.
Yes, SAG knows about this problem, see service requests 5033869, 5033877, SR5005915.
Dieter Storr