Journal Reciever Question

Hi All,
Just another question lads
We use DataMirror Transformation server for As/400 to replicate DB2 database
files to SQL or Oracle host databases
The Datamirror product requires all files required mirroring to be journaled
first
Data Mirror then reads the current attached journal reciever and sends the
information down to your NT / Unix hosts via TCP/IP

Now our journal reciever fills up quite quickly 2 to 3 times a day, this
causes DataMirror jobs to hog alot of CPU as they run at priorty 20, we
usually drop priorty on these jobs to priorty 99, but this does not ease the
problem


What I would like to know is how to figure out what journaled files populate
the journal reciever so quickly everyday, and if anybody is familiar with
DataMirror, how to load balance the subsystem for optimum performace during
the day. Should we stick the datamirror subsystem in it's own shared memory
pool etc...
Any ideas?

Regards
Paudie O'Riordan
Email: oriordan_paudie@emc.com  

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---