× 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.



James,

You're right  Yours and Mine are both just opinions and each will stand on
their own merit.

First my apology for not being a Linux/Unix erudite and not knowing that
piping is output of one command as input to another.

On your point of;

<SNIP>
>Now maybe I won't *have* to
>press that *@#$ F4 key all the time just to get some work done.
>I don't have fingers to waste on typing those stupid keywords.
<SNIP>

I don't quite understand that.  You can key in a CMD without prompting and
without keywords if you want.
It isn't mandatory.  However they are there if you need them.
But with Unix commands you don't have a choice.


But your comment seems to reveal another difference of view.
They lead me to believe that you think the paramount importance
is the programmers time while KEYING IN the program or command.

My experience tells me that (aside from interactive command line usage)
Commands in a Program are read by other programmers a thousand times while
they are keyed in just once.

Meaning,  Yes, I would prefer in a program to read the following
(BTW, I don't care how long it took the programmer to key it in).


CPYF FROMFILE(*LIBL/DCPFTCF)             +
     TOFILE(DCLISTG/DCPFTCF)             +
     MBROPT(*ADD)                  +
     CRTFILE(*YES)                 +
     INCREL((*IF  TCFCDAT *EQ &L1FRDATE)      +
          (*AND TCFCMPY  *EQ &L1CMPY)    +
          (*AND TCFCTIM  *EQ &L1TRTM))



Instead of seeing something like;

lavrec -f a -i P -d 1 -q 100 -R l -c 2 -s -r 44100 -a 16 -v 2 svcd.avi

It is SO apparent what the above line it's doing.




I don't see your grip ( or is that grep).

>I come from a unix background so of course I have that bias, but I think
>the "standard" AS/400 commands are clunky and hard to use.  Prompting is
>nice, but not really any better than <command --help>.

Ah, again you don't have to prompt.  I'm surprised you do.

On second thought,  why do you?   Is it you can't remember the Parameters?
If so, why not pretend it was unix and not prompt and just key them in and
Hope?

Again I just think it is nice to be able to do both


cpyf file1     file2

OR  (big word there, that OR)

CPYF FROMFILE(oldfile)        TOFILE(newfile)

Don't like prompting or using F4 ?  Don't use them.

And Unix's lavrec probably IS much more intuitive than  something like the
cryptic WRKUSRJOB

(lavrec:  is that a Record taking a leak?) (that's using the water closet
Simon).

IHO  So I guess we will agree to disagree.

John











As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.