You can also glean such data by use of DBINFO calls in your program.  More
programming work, but very educational.

-Dave

> -----Original Message-----
> From: LES BUREAUX DE CRÉDIT DU NORD INC [mailto:[log in to unmask]]
> Sent: Wednesday, January 03, 2001 7:42 AM
> To: [log in to unmask]
> Subject: Re: Transact database program getting slower
> 
> 
> You may want to try the HOWMESSY program by Robelle.  It will 
> tell you if
> you have any problems with secondary HASHING.
> 
> 
> Jean
> 
> ----- Original Message -----
> From: "Chris Schofield" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Wednesday, January 03, 2001 6:46 AM
> Subject: Re: [HP3000-L] Transact database program getting slower
> 
> 
> > Hello everyone
> >
> > Thanks for the replies.
> >
> > My master set is 3 million records in a capacity of 6 
> million.  The set is
> > therefore only 50 percent full.
> >
> > The key item (SYGEKSNR) X10 is a 10 digit number built as follows
> > DDMMYYNNNN.  The whole thing satisfies some modulo 11 
> arithmetic.  It
> could
> > be possible that I am getting secondaries.  How can I check 
> ?  Are there
> > tools available for checking ?
> >
> > I am splitting my program into updating and adding and will 
> perform some
> > timing tests.  I really don't know where the bottleneck is.
> >
> > The updates to the database are received every 15 minutes.  
> How safe would
> > output deferred mode be in this case ?
> >
> > I am using entry level locking to update existing records.
> >
> > We have 37 machines with varying memory configurations and Operating
> system
> > versions, but the majority are 6.0 or higher.
> >
> > Thanks again for the help
> >
> > Chris
> >
>