Re: Indexed PF vs. LF performance

[Alan Campin <alan0307d@xxxxxxxxx>]

When you say index PF if you mean the index was created using SQL,
then the index is faster. SQL indexes use a larger page size and are
faster. If you just mean the index was created as part of the CRTPF
process than absolutely none.

Also, you can delete a LF, create an index using SQL and then
re-create the LF the OS will see the existing index and use it.

On Mon, Jul 30, 2012 at 2:19 PM, Tim Adair <tadair@xxxxxxxxxxxxxxxx> wrote:
> A colleague asked me about this and I haven't been able to find any
> definitive information.
>
> For RPG (IV, but not ILE) doing CHAINs, SETLLs, and READs - which is faster,
> an indexed PF or a flat PF with an LF defined with the key?  For the sake of
> this question, let's assume we're talking about a single key field.  The
> file is DDS-defined, and must remain that way for now.  And for this example
> we're not interested in rewriting the RPG using SQL.
>
> We're on 7.1.
>
>
> Thoughts please?
>
> TIA.
>
>
> ~TA~
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.