Good guess Simon.  According to IBM ...

"In R410, the default for Access path size (ACCPTHSIZ) changed to *MAX1TB
rather than *MAX4GB on the CRTLF and CRTPF commands and in the SQL CREATE
INDEX statement. Most existing access paths have an attribute of *MAX4GB.
These access paths cannot be shared by access paths with an attribute of
*MAX1TB. For access path sharing to occur, change existing access paths to
ACCPTHSIZ(*MAX1TB) or specify ACCPTHSIZ(*MAX4GB) on the new access paths."

Reference the following multi-line URL:
http://www-912.ibm.com/s_dir/slkbase.NSF/ce197905697c4c6086256a4f007978f7/a2
00275166fcdd83862565e00060315c?OpenDocument&ExpandSection=1

-Dave K.

----- Original Message -----
From: "Simon Coulter" <shc@flybynight.com.au>
To: <midrange-l@midrange.com>
Sent: Thursday, January 03, 2002 8:05 PM
Subject: Re: ACCPTHSIZ perfomance - *MAX1TB vs *MAX4GB


>
> Hello Phil,
>
> You wrote:
> [SNIP]
> >logicals related to a physical should be 1TB or 4GB, but do not mix
> >them.  It refers to performance issues if you mix them, but it is not
> >clear if they are referring to overall performance, or performance in a
> >specific program.
>
> My guess is that since 4GB and 1TB indices are physically different in
> structure you would reduce the likelyhood of sharing access paths and
> could thus experince poor performance when adding or deleting records or
> when updating key values in existing records due to the extra access
> paths.
>
> Regards,
> Simon Coulter.
>
> --------------------------------------------------------------------
>    FlyByNight Software         AS/400 Technical Specialists
>    http://www.flybynight.com.au/
>
>    Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
>    Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
>                                                              X
>                  ASCII Ribbon campaign against HTML E-Mail  / \
> --------------------------------------------------------------------
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.