×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
<Charles>
In my case, we can have multiple worker jobs pulling off the queue, but in
your case, you probably want just a single job to keep the transactions
ordered.
You might want to multiple queues for sets of tables, or even one queue per
table if there's enough changes.
<snip>
I'd probably go with a 100% Java application, running on the i, reading
from the DTAQ and writing to the table.
</Charles>
There might be a pitfall. Each as400 Java Job starts a JVM and having lots
of JVMs is eating up all ressources, even on a big iron (one of the problems
of JDBCR4 and other RPG calling Java stuff. Writing Java listener for
multiple DataQs, this should be done in one as400 Job with multiple
listeners using one Thread pool. This needs some java experience and would
be the cleanest solution.
From the RPG perspective it would be easier to have RPG listeners using
ArdGate to talk to the PostgreSQL database. AppServer4RPG will use one
prestarted JVM and each RPG listener Job will have a thread of its own to
send the data to the remote database.
The trigger programms could simply send the before and after buffers (and
the null byte maps, if needed). The listener Jobs would use external
datastructures and do the cleaning of the data (blanks in zoned fields) and
whatever needed and propagate the data to the remote database, using normal
embedded SQL.
D*B
midrange.com
