RE: Seize/Lock Issues

["Shaw, David" <dshaw@xxxxxxxxxxx>]

> -----Original Message-----
> From: R. Bruce Hoffman, Jr. [mailto:rbruceh@attglobal.net]
> 
> -----Original Message-----
> From: Graap, Ken <keg@exchange.gasco.com>
> To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com>
> Date: Friday, June 02, 2000 3:50 PM
> Subject: RE: Seize/Lock Issues
> 
> 
> >But the point is that the access path has to be recreated. We need to
> change
> >it from *MAX4GB to *MAX1TB. My guess is that under this 
> circumstance there
> >won't be any access path sharing...
> >
> 
> 
> Sharing still works with the new indexes.  But it is still 
> based on the
> order of the builds.

Bruce,

Yeah, sharing works, however a *MAX1TB access path is different from a
*MAX4GB access path and thus will NOT share, which is the point Ken was
making.  To make his change, each one of the current *MAX4GB access paths
will have to have a new *MAX1TB access path built to replace it.  He can
greatly reduce his downtime by building them ahead of time, but he still has
to do all the processing to build them.

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
+---