RE: Journal Reciever Question

-----Original Message-----
From: ORiordan_Paudie@emc.com [mailto:ORiordan_Paudie@emc.com]

<snip>

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?

------------------------------

To figure out which files are being updated so often, do a DSPJRN to an
outfile for a typical hour or two, then query the outfile for counts of the
number of "hits" per file.

I used to work with Transformation Server at my old job.  If it's really
consuming a substantial amount of your capacity, then isolating it to its
own memory pool probably would reduce its impact on your other normal
processes, and may allow it to run more efficiently as well.  This presumes,
of course, that you have sufficient memory in the box to be able to support
this properly.  We didn't run DTS in its own pool, although we did set the
jobs' run priority to 50 and put it in the batch pool with other production
batch jobs.  It ran okay for us that way.  We did have virtually all
non-system jobs in pools other than *BASE, and that helped us quite a bit.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC
+---
| 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
+---