×
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.
On 2/13/2017 4:22 PM, Rob Berendt wrote:
Yes there are risks, and they're not to be discarded lightly.
But I'd like to discuss what is perceived as "significant operational
improvement".
I haven't found a good reason to convert an existing DDS table to DDL.
Instead, I find that I'm making brand new DDL tables, AND going along
with that, new HLL to take advantage of those new tables, that new
structure and capabilities.
Don't get me wrong; I'm not badmouthing DDS or my existing applications.
I think they work just fine -- for what they do. But when the business
needs more than that, I find myself turning to SQL more and more. I
don't find much value using RPG F-specs with DDL views or tables.
Someone else might, but unit record processing is less and less what the
business needs.
So, 'significant operational improvement' to me means delivering more
value to the business. It means being able to store 'just one more
attribute' and not having to recompile a dozen (or a hundred) programs
after hours. It means being able to build 'data warehouse' views that
power users can use to dig their own answers out of their data.
midrange.com
