As long as the key in the DDS described physical file was unique, a primary
key constraint with the original key fields can be added to the SQL table.
This new table can be read with the primary key constraint keys from native
I/O.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mark S. Waterbury
Gesendet: Friday, 06. August 2010 20:14
An: Midrange Systems Technical Discussion
Betreff: Re: convert dds to ddl
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...
midrange.com
