RE: copy file problems / documented "feature"

Rick,

I'm pretty sure it worked this way when I started on the S/38 at release 7.
I imagine it's worked this way since the beginning of time.  I'm certain
that you'd get a "working as designed" response back from IBM on it.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

-----Original Message-----
From: RBBaird@premsys.com [mailto:RBBaird@premsys.com]

Peter,
Not very elegant, but not only do I not see a better way, I don't see ANY
other way.
something like this?
        DCL  &CMD *CHAR 256
       DCL  &CMDLEN *DEC  (15 5) VALUE(256)
       DCL  &NAME   *CHAR (10)
          CHGVAR &CMD 'CPYF FROMFILE(file1) TOFILE(lib1/file2)
             MBROPT(*REPLACE) CRTFILE(*YES)
             INCREL((*IF DQNAME *EQ ''' *CAT &NAME *BCAT '''))'
       CALL QCMDEXC (&CMD &CMDLEN)
thanks for the hand!
Bottom line though, even if you key in the command from a command line, you
still have to imbed a space in quotes.  The problem I have with IBMs
implementation is that the operator is *EQ for EQUAL not *LK for LIKE!  If
you want to check positions of a field rather than the whole field, you can
use the INCCHAR parameter.  OPNQRYF, SQL, QRY/400, et al do not behave this
way.  why should copyfile?
Has this always been the case with this command?  Doesn't it seem VERY wrong
to anyone else?
Thanks again,
Rick
+---
| 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
+---