RE: Choice Programs

>>Since so few people use commands, what does everyone do, write CLP's that
>>prompt using DSPF's?
>>
>>Art Tostaine, Jr.
>
......
>I learned long ago that a command provides a better interface a whole lot
>quicker than trying to spiffy up a DSPF on short notice!  (:
>
>We've got a whole buncha home-brew commands that get embedded and reused
>all over the place.  Is that Object Oriented?  (;
>
>--Paul E Musselman

I'd fall into the same camp as Paul... why write a display file when a
command is perfectly suited for the job ? 

Then again, many of the developers I work with seem to have no idea how to
create anythign other than the most basic command, and my experience over
the years has been that most developers will make what could be a command
driven report or enquiry look like their other data entry etc screens to
maintain an application look and feel. Fair enough too.

I wonder if those that do the systems programmers end up writing more
commands than those that concentrate on application development ? I find
that I end up creating commnds because I know that what I am doing is
usually going to end up in a CL operation procedure or be used from the
command line for some reason or another. 

One other thing - the command interface should cause IBM to bow it's head
in shame IMHO. Maybe if it had a few more examples or actually tried to
tell you HOW to create a command there would be a whole lot more commands
in general use.
+---
| 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
+---