Thank you all for your great suggestions. I finally got it working.



On 10 Feb 2014 at 15:50, CRPence (CRPence <midrange-l@xxxxxxxxxxxx>) commented
about Re: Transferring a CSV file to i5:

On 10-Feb-2014 15:06 -0800, CRPence wrote:
On 10-Feb-2014 14:46 -0800, Gary Kuznitz wrote:

I'm trying to transfer a .CSV file to an i5.

I tried using this cmd:
CPYFRMIMPF FROMSTMF('/home/garyt/LU127720140115.csv') +
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 allowed.
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 parameter.


I only ever remember using source-physical-files for the Error
Record File (ERRRCDFILE); possibly I had also used on occasion, a
program-described if I intended for no character translations. I
would suggest trying instead of the CRTPF KDICHANGES/AUDITERORS
MBR(*FILE) SRCFILE(source-for-AuditErors), for which the failure
transpires, to use the following as output for the error records:

Conspicuously missing from that version of the CPF2885 Recovery text
[at least what was included in the OP] is this text that I found in a
v5r3 copy, which seems consistent with my experience of having used
[IIRC] only a SRC-PF [emphasis with asterisks by me]:
"-- When using the FROMSTRMF parameter with the ERRRCDFILE parameter,
*the ERRRCDFILE must be a source physical file*. If the records in the
FROMSTRMF are fixed, the ERRRCDFILE must be greater than or equal to the
record length of the tofile. *If the records in the FROMSTRMF are*
*delimited, the ERRRCDFILE must have a minimum record length* equal to
the sum of the TOFILE record length, the number of fields in the TOFILE
and 813."

From that, I infer that with the effective DDS given in the OP [nine
fields with apparent alpha rcdlen=137; though 130 was stated], the
request to CRTSRCPF may need to be modified from what I offered above:

Regards, Chuck
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page