I'd try it once with the file upload wizard (in IBM file transfer product) to analyze the csv and create a compatible upload file. If the wizard finishes successfully, then compare your file to the one the wizard built...
Also, note the you can save the "FDF" definitions, and use that in the CPYFRMIMPF command. There's a parm on that command (FLDDFNFILE) that accepts a file and member reference to this FDF definition. This could help the CPYFRMIMPF command with its data conversion chores, but I don't really know for sure...
Personally, I'd use the IFS file api's to read the csv file directly, parsing out the data myself. It seems much safer than using the CPY*IMPF commands...
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Kuznitz
Sent: Monday, February 10, 2014 4:46 PM
Subject: Transferring a CSV file to i5
I'm trying to transfer a .CSV file to an i5.
I tried using this cmd:
CPYFRMIMPF FROMSTMF('/home/garyt/LU127720140115.csv') +
MBROPT(*REPLACE) RCDDLM(*CRLF) +
I'm getting this error:
Message ID . . . . . . : CPF2885 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 02/10/14 Time sent . . . . . . : 14:35:04
Message . . . . : Field Definition or Error file AUDITERORS in KDICHANGES not
Cause . . . . . : File AUDITERORS 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
I have the TOFILE created as:
The file is 130chs long.
I have created an error file called AUDITERORS
I have created the error file as:
It has a member.
Does anyone have any ideas what could be wrong with the type of the error file?
Or what I am doing wrong?