From my experience working with this type of process, you cannot have a file defined by DDS. When you create the file give only the filename and the record length. This creates a different type of physical file that the command detects and can use. Just make sure you make the record length sufficiently long.
And don't forget that after you transfer the file, it will still have the commas and quotes. I have some examples of how I parse the file, if you want a leg-up.
date: Mon, 10 Feb 2014 14:46:27 -0800
from: "Gary Kuznitz " <docfxit@xxxxxxxxxxxx>
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?
Notice: This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. This message may also contain Protected Health Information (PHI) and must be treated confidentially and handled in accordance with HIPAA and other federal and state privacy laws. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately and delete this e-mail (and any accompanying attachments).