× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2008

Re: Why non-keyed PFs back then? Why today? ( was Re: Which of the SYSIBM tables/views show the row count for )

For what it's worth, these days at least, you can read a keyed PF in arrival sequence with RPG by leaving the "K" off of the F-spec position 34 (Record Address Type).

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Tom Liotta wrote:
Mike Cunningham wrote:

This may be a left over from the old days but we never put a key on any table (Physical file) directly

IIRC (and _only_ IIRC), way back when, there were a couple elements that combined to bring a small amount of risk to having keys on PFs.

1. Non-keyed LFs were not allowed. (Possibly irrelevant.)
2. Damage to a PF index could make it impossible to read the PF even in arrival sequence.

Back on the S/38 and in early OS/400, damage to files was far more common than it is today. Power requirements were higher, UPSs were less common, stability could be affected more easily than in later releases, etc.


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-2025 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.