×
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.
I agree. All our new PF's are DDL, but we're not going out of our way to replace existing DDS PF's.
IF you have a compelling reason to store DDL source, keeping it with your DDS source makes the most sense to me. We don't have any reason to keep DDL source at all.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Friday, February 24, 2017 12:28 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Storing source as DDL instead of DDS
My thoughts on this.
Doing a wholesale migration from DDS to DDL has some benefits but I am not certain it would be the best use of your companies money at this time.
Doing all new development using DDL instead of DDS is a reasonable approach.
Since you would be supporting a mixed environment one option would be to put the DDL into the same QDDSSRC pf. While this may drive a purist mad I believe it would make the transition for a new employee the easiest.
Hopefully, they would look for the DDS for the file, find the source member and quickly realize that it's in DDL and they need to switch gears.
If they can't figure that out, you've made a hiring mistake.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
midrange.com
