---------------------<snip>----------------------
I would suggest that software product find a better way. Expecting anyone to
enter a command that long without an error has ignored the human interface
factors. Even DUMP lets me point to a parmlib member where I can take my
time and get it right. I rarely use a 'real' console, so finding the key to pull up
the last command I entered so I can try to correct my mistake means trying
to retype the command all over again. Another chance to have a typo an
start all over again.
---------------------<unsnip>-------------------
Isn't that why control card scanners/parsers were developed? <sarcasm
intended!>
Certainly made sense to me when I developed ARCHIVER (CBTTAPE.org, file
147) (sorry for the plug!) ARCHSCAN, the control statement parser,
isn't perfect; it's not even very good; but it's functional and anyone
is welcome to borrow bits, pieces and ideas for their own (nonexclusive)
use. Or you can look at the OS/360 source, at the various utilities, for
ideas as well. Control card processors are a dime a dozen, some good,
some bad and some indifferent at best.
I, for one, deplore the use of the parm field OR the operator command
interface. I'll accept operator command interfaces ONLY when there's a
mechanism for handling and processing a complete parm set.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
