Rob,

You are a life saver. I can't thank you enough.
I was working on this trying to get it running all day yesterday.
I found the link you included in your email and a whole bunch more about this subject
yesterday.
I'm not sure what fixed it but after your email I made some changes that I should have
made long ago.
It is running now.
Changes I made:
1. I was reading this file out of /tmp. The last time I ran into this I had the file in
/home/garyt. I don't know if it makes a difference but I changed it to /home/garyt.
2. I recalculated the error file length. It's now correct.

Thank you for sparking my thoughts to resolve this issue.

Gary Kuznitz
On 18 Dec 2014 at 7:19, rob@xxxxxxxxx (rob@xxxxxxxxx <midrange-l@xxxxxxxxxxxx>)
commented about Re: Transferring a CSV file to i5:

It took me some time to really read this.
The problem is not in the file you are trying to import it to, although I
wouldn't use a source physical file either.
The problem is in the error record file.
And this same error message regarding this same file in this same library
has been on this list before.
http://archive.midrange.com/midrange-l/201402/msg00209.html

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Gary Kuznitz " <docfxit@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/17/2014 09:56 PM
Subject: Transferring a CSV file to i5
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I can't figure out what I am doing wrong in this exact same problem I had
once before.

I'm trying to import a CSV file into an AS/400 PF.

CRTF: CRTSRCPF FILE(KDICHANGES/MBRPAY1ERS) RCDLEN(959) +
MBR(*FILE)
MONMSG MSGID(CPF7302) EXEC(DO)
DLTF FILE(KDICHANGES/MBRPAY1ERS) /* File Already +
exists */
GOTO CMDLBL(CRTF)
ENDDO

CPYFRMIMPF +
FROMSTMF('/tmp/ATU_PAYROLL_DATA_FY14_372_39+
8.txt') TOFILE(KDICHANGES/MBRPAYATU) +
MBROPT(*ADD) RCDDLM(*CRLF) STRDLM('"') +
FLDDLM('|') FROMRCD(*FIRST 20) +
ERRRCDFILE(KDICHANGES/MBRPAY1ERS +
MBRPAY1ERS) ERRRCDOPT(*ADD)

I'm getting this error:
Message ID . . . . . . : CPF2885 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 12/17/14 Time sent . . . . . . : 18:56:38


Message . . . . : Field Definition or Error file MBRPAY1ERS in
KDICHANGES
not allowed.
Cause . . . . . : File MBRPAY1ERS in KDICHANGES is not the correct file
type
for the copy command.
-- The Copy From Import File (CPYFRMIMPF) command require a source,
DDM,
program described physical, or externally described physical file for
the
Field Definition File (FLDDFNFILE) and the Error Record File
(ERRRCDFILE).
Recovery . . . : Do one of the following to change the file name on the

parameter and try the request again:
-- Specify the correct file type on the FLDDFNFILE, or ERRRCDFILE
parameter.

Does anyone have any idea what I am doing wrong?

Thanks,

Gary Kuznitz
--
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.


--
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.




This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].