RE: RLU (vs) handcoded prtf DDS

> What, exactly, is DSU?

Sorry, the correct name is CODE/Designer. DSU is the earlier name of the 
product.
I get too use to thinking in TLNs (three letter acronyms) at times.

> What is it that appeals to you most?

First impressions are important with software just like they are with people. My
first test for software is intuitiveness. Does it work like something else I 
know or
does it work like I expect. I rarely have excess time to sit down and read a 
book
to learn the product. I will experiment and read as time goes on, but I need to 
be
able to make it work with a minimum of time at first. CODE/400 works like
SEU + Windows. There are many things you can do with it, but initially it worked
just like I expected. I will continue to learn about additional features in the 
future
and I've bought a book on REXX now, so I can start to extend the product with
macros. CODE/Designer is also intuitive. The mouse does the things that you
would expect it to do (or at least what I expect it to do). The one thing it 
doesn't
do to my satisfaction is work with internally defined O-specs as well as
externally defined DDS. I am pretty neutral on the O-spec vs DDS battle. I can
use either and haven't found any reason other than barcoding to tip the scale.
A tool should support both because of the wide spread use of both. This is not
true of internally defined database and workstation files because I do not see
either of these very often.

Joe Teff
Information Technology Consultant
IBM Certified Specialist - AS/400 RPG Programmer
Quality Data Systems
Minneapolis, MN

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---