|
Actually, I just tested this and the same thing happens on V3R1, V3R2, V3R7 & V4R1. That's what it's supposed to do. When you enter the OVRDBF you give it ONLY the file name, so it overrides that file regardless of what library you specify. Neil Palmer AS/400~~~~~ NxTrend Technology - Canada ____________ ___ ~ Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||= Phone: (905) 731-9000 x238 |__________|_|______|_|______) Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\ Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ mailto:NPalmer@NxTrend.com AS/400 The Ultimate Business Server http://www.NxTrend.com > -----Original Message----- > From: Bob Luebbe [SMTP:bluebbe@conn2000.com] > Sent: Tuesday, July 07, 1998 10:00 AM > To: MIDRANGE-L@midrange.com > Subject: CPYF oddity > > We have a problem with a CPYF on V4R1 and V4R2. It does not appear to > be a > problem on V3R7 and earlier. > > First we run the command: > OVRDBF FILE(CUSTP01) TOFILE(QTEMP/CUSTP01) > > Then we run the command: > CPYF FROMFILE(WBLUEBBE/CUSTP01) TOFILE(QGPL/CUSTP01) CRTFILE(*YES) > > The following messages are generated by the CPYF command: > File CUSTP01 overridden to CUSTP01 in QTEMP. > From-file CUSTP01 in QTEMP not found. > Copy command ended because of error. > > Since we qualify the CPYF statement with the library on both the > FROMFILE > and TOFILE, why is the preceeding OVRDBF overriding the FROM library? > Why > isn't this a problem on V3R7 and earlier? > > Thanks in advance. > +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.