Re: Weird CPYF behavior... ???

Sorry. I used the second example in that article with the 'X41' value 
concatenated into the variable. It works perfectly, and helps one to 
recover from a bug in the BPCS EAM module.


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





"Peter Vidal" <Peter_Vidal@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/05/2005 02:36 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange-l@xxxxxxxxxxxx
        cc: 
        Subject:        Weird CPYF behavior... ???


Hi list!

I have this:

START:      PGM        PARM(&TASK) 
 
            DCL        VAR(&TASK) TYPE(*CHAR) LEN(10) 
 
IF         COND(&TASK *NE '*ALL') THEN(DO) 
      DLTF       FILE(QTEMP/YAAVREP) 
      MONMSG     MSGID(CPF0000) 
      CPYF       FROMFILE(YAAVREP) TOFILE(QTEMP/YAAVREP) + 
                 CRTFILE(*YES) INCREL((*IF AVAQCD *EQ &TASK))
ENDDO 

END:        ENDPGM

If the value for &TASK is "ABC", then the file being builded end up with 
four records as follows:

1) ABC
2) ABCPRIME
3) ABCDIDS
4) ABC3

Why?  I just want the "ABC" record to be created in QTEMP?  What I am 
doing wrong?

TIA,

Peter Vidal
PALL Corporation / IT Development Group
10540 Ridge Rd., Ste 203
New Port Richey, FL 34654-5111
http://www.pall.com

"Knowledge is power." -- Francis Bacon (1561 - 1626)
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.