×
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.
Hi, Crispin:
AFAIK, CREATE TABLE creates a physical file with only "arrival sequence"
(access path), so if you have a physical file that has keys, you cannot
create a direct equivalent with only a TABLE ...
You would have to create an SQL INDEX also, and so then, what would you
propose to do? Perhaps create the TABLE with a (slightly) different
name, and then create an SQL INDEX with the same name as the original
"keyed" physical file?
Would not that be the same as the previously suggested approach of
creating a Logical File with the same name as the original file, and
that has the necessary keys also defined? Then, CRTLF will create the
logical file which will also have the correct (possibly shared) access
path associated with it.
Mark
> On 8/6/2010 1:24 PM, Crispin Bates wrote:
As I said in my very first reply. At V5R4 you no longer need to replace the
PF with an LF because the RCDFMT clause was added to CREATE TABLE...
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.
midrange.com
