See also my questions under the forum EntireX.
SAG recommended to use EntireX over WCP to replicate Adabas from the mainframe to Adabas on Windows. SAG supports for other databases an adapter, for example SQL, but not for their own products. That’s unusual.
I experienced the following problems with WCP, for example
RC 148: Adabas nucleus not active – subcode 8224 - even ADABAS was up and running on the Windows side
RC 224: Entire Net-Work (WCP) – reply timeout
WCP0602E Node is unreachable
It may not active or there may be a configuration problem.
Detailed error response was: XTS1061E: TCP/IP Connection refused
If WCP stops working, I got a jam and an overflow in the replication engine (RPL buffer and/or SLOG).
It seems that the errors are caused by a bottleneck in WCP, when many files (100) were replicated - intitial state. At the end we will have more than 200 files replicated in production.
Organizations experienced better response and efficiency with EntireX, for example with RPC servers. I can agree with this.
WCP (Entire Net-Work) doesn’t give me the warm and fuzzy feeling to use in production.