Calling DB/400 gurus - where to put DB keys physical or logical? -- MIDRANGE-L

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

Subject: Calling DB/400 gurus - where to put DB keys physical or logical?
From: "Villa, Mark" <mvilla@xxxxxxxxxxxxxxxxxx>
Date: Wed, 16 Oct 2002 09:32:06 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Thread-index: AcJ1Euwtpb70NxTrSCmY60Bnyu2NigABFjHg
Thread-topic: Calling DB/400 gurus - where to put DB keys physical or logical?

I have always designed physical files with keys (unique ones).
Now my eyes have been opened to a world of PF's that have no key that
are always accessed with keyed logicals. To my surprise, this seems to
be method of choice for some very common large scale software providers.

I am thinking this matters greatly for future proofing, performance, and
possible integration with other databases.

My question: Is one way better than the other and what are the reasons?


Mark Villa in Charleston SC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Calling DB/400 gurus - where to put DB keys physical or logical? , R. Bruce Hoffman, Jr.

This mailing list archive is Copyright 1997-2024 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.