Re: Writing an Open Access handle that will either read/write to the Db2 file or make a REST call
Subject: Re: Writing an Open Access handle that will either read/write to the Db2 file or make a REST call
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Tue, 15 Jan 2019 17:59:16 +0100
Arc-authentication-results: i=1; mx.google.com; spf=neutral (google.com: 184.108.40.206 is neither permitted nor denied by best guess record for domain of dieter.bender@xxxxxxxxxxxx) smtp.mailfrom=dieter.bender@xxxxxxxxxxxx
ArdGate isn't an option as I don't have direct access to the other DB...
this wouldn't be the real problem, as we decoupled the trigger layer from
the replication to work around silly restrictions of DB2/400 (you can't
connect to a remote database inside a trigger or down the call stack of a
trigger and 3 part alias is limited too) trigger sends to dataq and listener
makes the replication. It wouldn't be too hard to replace the remote sql
stuff by your REST call.
The benefit for the trigger way is, that the black box application stays
untouched - but you can't redirect reads doing it this way.
This thread ...
Re: Writing an Open Access handle that will either read/write to the Db2 file or make a REST call, (continued)
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact