I'm not suggesting redesigning your database. Tools that do dataset
repacking allow you to specify the path to use for the repack without
changing the primary path. In fact, you can change the primary path without
affecting your application at all. The only thing primary path is used for
is determining how to reorganize records during a repack or DBUNLOAD/DBLOAD.
It does not affect the way entries are added to or retrieved from that
dataset.
As already stated, tuning Suprtool's memory usage is done with SET BUFFER
and SET PREFETCH.
-----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: 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.
Thanks!!!
Denys Beauchemin wrote:
> What???
>
> This makes no sense. I submit that you are doing something wrong. Either
> you have assigned the primary path incorrectly or you are not sure what
you
> are trying to accomplish.
>
> Let's talk primary path for a second. If you do not assign a primary path
> at creation time, IMAGE will do that for you and you may not like the
> results. Take for example an order entry system. If you do not assign
the
> primary path, IMAGE may pick the primary path to be the order number.
> Totally useless. There is probably a single detail for that order
number.
> It would be much more advantageous to have the primary path assigned to
> the customer number, so that when you do a reorg, your order header detail
> would assign all the orders for a specific customer to be contiguous. You
> probably have a program that displays or prints the orders by customer
> numbers. This would accelerate it greatly.
>
> Depending on the tool you use, you might want to assign the primary path
to
> the longest, most used path into each detail dataset. Do not assign it to
> a short path, especially one with a single entry.
>
> Kind regards,
>
> Denys. . .
>
> Denys Beauchemin
> HICOMP
> (800) 323-8863 (281) 288-7438 Fax: (281) 355-6879
> denys at hicomp.com www.hicomp.com
>
> -----Original Message-----
> From: Ronald R Horner [SMTP:[log in to unmask]]
> Sent: Thursday, March 22, 2001 1:58 PM
> To: [log in to unmask]
> Subject: Re: Tuning the Suprtool Beast
>
> I did, but when I would reorg the primary of a detail set, other paths
> would
> become messy. So I abanded HOWMESSY.
>
> Later
>
> Donald Frantum wrote:
>
> > Try using HowMessy. Robelle has information on their site
> www.robelle.com
> >
> > >>> Ronald R Horner <[log in to unmask]> 03/22/01 09:04AM >>>
> > Being a MACS shop, we use Suprtool like it's water. I've noticed that
> > there are times when my system has to perform multiple reads do to page
> > faults. Can Suprtool be tuned to not store so much into memory? If it
> > can, how?? I'm just trying to reduce the number of reads to disk (page
> > faults).
> >
> > Later and Thanks!!
> >
> > --
> > Ron Horner
> > HP3000 Systems Administrator
> > JCPenney Logistics
> > [log in to unmask]
> > (414) 259-2274
>
> --
> Ron Horner
> HP3000 Systems Administrator
> JCPenney Logistics
> [log in to unmask]
> (414) 259-2274
--
Ron Horner
HP3000 Systems Administrator
JCPenney Logistics
[log in to unmask]
(414) 259-2274
|
