RE: CPYF with V5R3

This is correct.  MBROPT parm value of *ADD or *REPLACE is irrelevant
for a newly-created to-file, but when the default value of *NONE is
used, it is assumed that the to-file should NOT exist.  Using *ADD or
*REPLACE provides the most flexibility:  ADD/REPLACE without error if
found, else create the to-file. 

Randy

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Doug_McLauchlan@xxxxxxxxxx
Sent: Monday, August 28, 2006 4:00 PM
To: Midrange Systems Technical Discussion
Subject: Re: CPYF with V5R3

No error on V5R2 as long as MBROPT is specified.  If MBROPT is *NONE
then 
I get an error.


Doug McLauchlan






"Shannon O'Donnell" <sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/28/2006 12:58 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Subject
CPYF with V5R3






On our V5R3 system, when we issue a CPYF command and specify
CRTF(*YES)... 
 And the target file already exists, the command completes normally and 
without errors.  This command should fail, shouln't it, since I am
telling 
it to create the file but the file already exists?  It used to fail on 
V5R2 and below.  Can someone please try this on a V5R2 or older system 
ands tell me if it does fail?  Also, if someone on a V5R3 system could
try 
it and confirm that it did not fail for you too, I would appreciate it.

Thank you

Shannon O'Donnell