It is my understanding that if you use Suprtool to serially
read an entire data set (or use Cobol for that matter)
that the entire data set is going to be transferred to memory.

Once it is in memory, other programs may fight for memory can
cause some swapping. Not much you can do about that besides
add more memory.

I use Suprtool and Netbase, and am not sure why one affects the other
as you state. I do run lots of Suprtool extracts on the shadowed copy
of data to reduce the load on the production machine.

The prefetch of Suprtool may add additional memory pressure
if done to an extreme, so turning it down or off may
help your situation (or may just make the Suprtool part run longer.)
Of course what you are trying to avoid is to pre-fetch so much
data that it get swapped back out before it is processed by Suprtool.

If you are running multiple active jobs at the same time then
you might try scheduling them one at a time, so they don't
fight over the limited memory. Fortunately, memory is pretty cheap
these days, especially for used or third party memory. Add another
gigabyte or two and see how that helps things.

-----Original Message-----
From: Ronald R Horner [mailto:[log in to unmask]]
Sent: Thursday, March 22, 2001 1:02 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Tuning the Suprtool Beast


Let's take a step back here.  These databases that I'm working with were
designed by a 3rd party that we bought the software from.  So any ideas
about
redesigning the databases are out.  I'd like to, but I have to stay in
business.

Now with that out of the way.  We shall continue...

I'm just trying to find a way to limit the amount of data Suprtool places in
memory.  I have set the prefetch to 0 because I am also using Netbase to
shadow
the data.  I have not a lot of memory, in fact I'm looking to purchase some.
But for now, these are the cards I have been dealt.

Th