Re: Questionable practice in file handling in CL

I'd have *thought* that you only need to recreate in the correct order once, if that is the logic behind the CL.

You could look at the order that the files are created: Where there are common key fields, then the logicals with the most key fields will be created first, and the ones with the fewer key field will share the access path. (E.g., if LGLA has key fields FLDA, FLDBB and LGLB has a key field of FLDA, then LGLB will share the access path of LGLA.)

However, re-creating the logicals may be more efficient than the automatic maintenance that occurs with the physical being rebuilt. However, given that you mentioned 20-30K records, unless you are on a very small or old machine, you may not notice all that much difference. (Bearing in mind that the rebuild of the logicals will likely take place in separate tasks--name of the job(s) where this happens eludes me.)

Sam



On 10/20/2017 2:08 PM, Duane Scott wrote:

Interesting concept. I want to argue, but I just can't.

At some point, I think I heard that argument before, but as it doesn't TYPICALLY come up that a complete set of files are deleted and recreated each night, I can't think that I would think of that as an excuse.

Using the same logic, should all logicals be deleted and then recreated on a regular basis so as to ensure that the most efficient pathing is used? Or should it be a "Once and Done"?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus