Hi Folks !
Was wondering how folks define PF's when it comes to keyed or not.
Is there something I'm missing when it comes to NOT having the "most
common" field(s) in a PF defined in the PF a key field(s) ?
Then handle the less obvious stuff in LF's ?I had a S/38 customer years ago who did a *ALLOBJ backup on 6 tapes (6250), which I found to be highly suspicious. When I migrated them to their AS/400, I told them to be sure to specify ACCPTH(*YES), and they showed up with 30 tapes! Their "order detail" physical file had 125 LFs on it!
One less access path...
Why PF's with NO key fields ?
Also, I was told YEARS ago (on the S/38) that you should try to keep the
number of LF's over a PF to a minimum, say 3, 4 tops and let your
program handle the level breaks, etc. to help system performance. Even
on the AS/400 there has GOT to be some truth to that just due to the
fact that there aren't a BUNCH of access paths that have to be rebuilt.
I've seen some vendor packages with a hundred LF's over one PF !!!!
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.