Re: QSHELL commands (was: Stmf copy with add)

I can -already- type  CPYF  FILE1  FILE2.

This assumes that my library list is properly set, and that the
defaults for the command do what I want.

Once you add in MBROPT(*ADD|*REPLACE)  or maybe a FROMMBR/TOMBR (yes,
yes, I know--  the concept of a member is a purely IBM AS/400
creature and that no programmer in his right mind would ever think of
using such a thing in this day and age), or CRTFILE(*YES), I'd much
rather see the parameters.

As far as a cpyf goes, I can key:

        CPYF  LIB1/FILE1  LIB2/FILE2   MBROPT(*ADD)  FMTOPT(*MAP *DROP)

and not need to press F4 to prompt.  But, if I'm keying in  program
rather than a one-time command, at this point I'll usually press F4 /
ENTER to put all of the parameters around it and make it look pretty.

For a once-and-done command, I still like the option of prompting to
make sure I get the parms in the right spots, -=especially=- since I
have the task of making the authorized patches to our live data.
Poking at live data makes promptable commands more desireable.

--Paul E Musselman
PaulMmn@ix.netcom.nospam.com





>On Sat, 13 Oct 2001 jpcarr@tredegar.com wrote:
>
>  > I wish I had a sanitized, Keyword Driven, visible Default Value,  F1 F4
>>  aware,   interface for them.
>>  The ( jar -cfM myfile.zip file1.csv.......) is a good example  Just look at
>>  it.  letting the F1 F4 issue aside for a moment,  wouldn't it be better to
>  > have that function look like
>>
>>  CPYF  FROMFILE(mylib/myfile) TOFILE(somelib/somefile)   etc  ???
>
>You are kidding here, right?  You would really rather type:
>
>CPYF  FROMFILE(mylib/myfile) TOFILE(somelib/somefile)
>
>than
>
>cp file1 file2
>
>?