I think a better question would be, what would you like to achieve from a
DDS to DDL conversion?
As long as the files are only DDS described new enhancements within the
CREATE TABLE statement cannot be used.
There is much more than LOBs!
For example a timestamp can be created with the ROW CHANGE TIMESTAMP
attribute. If a row is updated independent through which interface (native
I/O, embedded or interactive SQL, ODBC, JDBC, UPDDTA etc.) the timestamp
when the last update of the specific row occurs is automatically inserted.
With Release 7.3 TR 1 we get a couple of other GENERATED ALWAYS columns, for
example for automatically updating the session user who wrote or changed the
row, or for storing the Job, Connection information.
Indexes are much more powerful than DDS described logical files. New key
columns based on SQL scalar functions can be built.
Where conditions including multiple and/or/not conditions, scalar functions
and parenthesis, can be created and understood much easier than DDS
described files with SELECT/OMIT clauses.
I have seen a lot of companies converting fix format RPG to free format RPG
without changing anything else and everybody agreed the conversion is
important.
But the same guys insist, that they still can live with DDS described files
and are not willing to convert those files, isn't this a contradiction?
Even though conversion is very easy and there is not even a need to
recompile the RPG and/or Cobol programs with 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!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
midrange.com
