Re: File conversion - Rebuild Access Paths

Hello Eric,

If you mean will the LF share the existing access path then the answer is no to 
both questions.

In the first scenario the sequence is different (although reversed) and the 
index must supply the records in 
the correct order when reading sequentially by key (also the LF is unnecessary 
for HLL processing because you 
can process the file backwards) although it may help with various query tools.

In the second scenario A,B,C,D is not a super-set of A,B,C,E (nor is the 
reverse true).

Regards,
Simon Coulter.

//----------------------------------------------------------
// FlyByNight Software         AS/400 Technical Specialists
// Phone: +61 3 9419 0175      Mobile: +61 0411 091 400
// Fax:   +61 3 9419 0175      E-mail: shc@flybynight.com.au
// 
// Windoze should not be open at Warp speed.
//--- forwarded letter -------------------------------------------------------
> X-Mailer: ccMail Link to SMTP R8.10.00
> Date: Mon, 26 Oct 98 14:06:41 -0600
> From: "Eric DeLong" <eric.delong@pmsi-services.com>
> To: midrange-l@midrange.com
> Reply-To: MIDRANGE-L@midrange.com
> Subject: File conversion - Rebuild Access Paths

> 
> 
> How versatile is the system with the following scenario?
> 
> Keyed PF: DIV, PMS#, REQ#, DATE(D), TIME(D) <-- Date/Time descending seq
> assoc LF: DIV, PMS#, REQ#, DATE(A), TIME(A)
> 
> Will the system use the existing AP for the keyed PF to build the LF AP? I'm 
> trying to optimize a file conversion job. Right now, we've got PF and LF 
>files 
> built, adding converted records. I want to convert to new PF then build LFs.
> 
> Also, what happens if I've got keyflds A,B,C,D in one LF and A,B,C,E in 
>another.
> Is that going to be able to base LF 2 on LF 1?
> 
> Eric

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