Mike,
Cloverleaf 5.6, AIX.
I have experimented with this and got it to work. This was simply a proof of concept so it really did not do anything other than connect to a source and extract some information.
That was enough to convince me this was possible. Idid this in March of 2007 but we have not ever used this capability.
One of the reasons is there are considerations that we did not have time to work out that had nothing to do with the actual access.
Things like what do you do if the connection is refused? If you sleep to wait a while to try again, that blocks the entire process – not good if this is peak demand period on any volume integration – potential death on a constantly high volume integration.
How to handle lockouts (kind of the same as above).
What do you do if the DB never is available or there is an error on the message? Do you error out the message (this could happen with every message making working the Error DB problematic), do you send the message anyway with some kind of default, do you stop everything?
There are other issues (like what happens if the owner of the DB does not validate their changes – the ODBC activity won’t fail but the wrong data will potentially corrupt lots of messages).
I think you see the picture.
However, bottom line this should work for you.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
.
