Nice description Nathan.
I've had that same discussion with countless customers over the years. Most
of them think they have to "convert to SQL" it has to be all at once and
would be a nasty project. (it's not really but that's another discussion)
When I educate them on why that's a gradual process done as you touch each
database object in a development process the apprehension level drops
considerably. It drops further when they learn they can start to use
imbedded SQL right away without any database changes. That leads right
into the use of RDI.
The whole thing could be simple if folks allow it to be.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Nathan Andelin
Sent: Saturday, February 11, 2017 9:13 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL statements for physical and logical files
Does the file have to have been originally created with SQL instead of
DDS for this kind of information to even be kept anywhere or is it
stored somewhere for all files?
Regarding the question of "SQL instead of DDS", I've run across a number of
people who perpetuate the myth that there are 2 distinct database management
systems under IBM i, and that the database objects that are created from DDS
are materially different from the ones created by DDL.
For database objects created from DDS, some refer to that as an ISAM
database, while database objects created from DDL are part of a relational
database management system. As I say, that's a material misperception, or
misrepresentation.
The physical files (aka physical database objects) created via DDS are
essentially identical to the ones created by DDL. That becomes quite
apparent via output from the DSPFD command, system APIs, SQL catalogs, and
object dumps. And the database objects created by DDS and DDL pertain to the
same database management system.
Regarding RLA, which is similar to access methods under ISAM, the IBM i SQL
Query Engine (aka SQE) uses that under the covers.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
