I may not be asking this question correctly, but hopefully, the question comes across.

We run DB2 on iSeries and things are very slow for us. One reason is how many libraries we have going into one journal. There are reasons we do it this way. It's slow because each time the product has to do a bunch of work to find the checkpoint it left off at and then go forward from there. It's the way it is.

Is there a way to "listen" to the journal and process as the journal is written, or is the "seek and process" method I'm currently using the only way?

Thanks in advance.

This message has been edited. Last edited by: FP Mod Chuck,

Michael

Looks like you will need to open a case with techuspport to get an answer to this one.