|
I too had problems with this and finally gave up on getting the IBM error file to work. The problem occurred when the delimited text file had text longer than one of the fields into which it was supposed to go in the database file that was to be the result for the CPYFRMIMPF. 1. IBM's command is supposed to ignore these errors - but doesn't always 2. When the error does occur, IBM's error record file doesn't work as I understood it should after I "RTFMed". Result was I wrote a program to count the records in the import file, then count the records that resulted from the copy, and where the results were not equal, I now send a message (as an email) notifying our help-desk that there is an error and that a developer is needed to investigate the cause of the problem. Sorry this doesn't directly answer your question, but basically, it tells you that you are not alone with the problem, and that at least one other developer had to build his own workaround. Andy Leisk Senior Programmer Analyst Banta Global Turnkey 1457 Earl Street Menasha, WI 54952 ph: 920-751-4434 web: www.banta.com -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Todd Daniels Sent: Wednesday, June 08, 2005 10:46 AM To: midrange-l@xxxxxxxxxxxx Subject: CPYFRMIMPF & ERRRCDFILE I am using CPYFRMIMPF to get data from a comma separate file to a database file. I have specified an Error record file on the copy command. However, when I do get errors, I am unable to read the records. Does anyone know how to make the data in the error file readable? Operating system is at V5R3. I created the error file with a record lenght = TOFILE record length + TOFILE number of fields + 813 (779+48+813=1640). Here is the CRTPF command I used. CRTPF FILE(MYLIB/ERRORFILE) RCDLEN(1640) FILETYPE(*SRC) Here is the CPYFRMIMPF command I used. CPYFRMIMPF FROMSTMF('/home/mycsv.csv') TOFILE(MYLIB/MYFILE) MBROPT(*REPLACE) RCDDLM(*CRLF) ERRLVL(*NOMAX) ERRRCDFILE(MYLIB/ERRORFILE) ERRRCDOPT(*REPLACE) RPLNULLVAL(*FLDDFT) -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.