Re: CPYFRMIMPF Error CPF2973

On 25-Dec-2014 12:18 -0600, Gary Kuznitz wrote:

I'm trying to copy a file from the IFS to a DB file. I'm getting
errors on every record. The error is CPF2973

The from-program and to-program were not included in the information below. The partial symptom string is msgCPF2973 F/QCPIMPRT FM/QCPIMPRT FP/Send_type_msg stmt/15 ... TM/QDBCTHTWRK

From module . . . . . . . . : QCPIMPRT
From procedure . . . . . . : Send_type_msg
Statement . . . . . . . . . : 15
To module . . . . . . . . . : QDBCTHTWRK
To procedure . . . . . . . : start__17qdbcth_ThreadWorkFP17...
Statement . . . . . . . . . : 10
Message . . . . : Data from
file in truncated to 20 characters.
Cause . . . . . : The maximum record length for
member in from-file in
library is longer than the
maximum record length for to-file MBRPAYATU in library GARY2.
Technical description. . . : If the from-file is a tape file
with variable length records or if multiple record formats are copied
from a logical file, only the records that are longer than 20
characters are truncated. <<SNIP>>

An APAR for v5r2 described a similar issue; at least having noted the missing replacement text for that message.

In the CLP I have:
CHGJOB CCSID(37)
Message . . . . : 5700 - CPYFRMIMPF
FROMSTMF('/home/Payroll/ATU_PAYROLL_DATA_FY14_372_398.txt')
TOFILE(GARY2/MBRPAYATU) MBROPT(*ADD) RCDDLM(*CRLF) STRDLM('"')
FLDDLM('|')
FROMRCD(2 *END) ERRRCDFILE(GARY2/MBRPAY1ERS) ERRRCDOPT(*ADD)
RPLNULLVAL(*FLDDFT)

I am getting no records in the error file.
I don't have any double quotes in the file past the first record.
This is one record of the input file from the IFS:
372|7/12/2013|000027857|Last Name, Brian
J|3926|00001|A3|6/22/2013|000764|SIGNAL
INSPECTOR|A|AWD|AWARD|1|1|20|20

The above is all on one line. = One record.

Does anyone have any idea why I would be getting the error?

PS: V5R3

Is the Copy From Import File (CPYFRMIMPF) running using the v5r2 support; i.e. is there a Data Area (DTAARA) named QCPFRMIMPF in QSYS with the string value 'CPV5R2'? If so, then allowing the feature to use the actual V5R3 support might assist; i.e. delete the data area, or modify the value of the string data, because the v5r2 code path had an almost identical symptom.

Note that the date data values are in *USA format, but the default for the command tells the import feature that the date data values should be *ISO. The command suggests the strings are delimited with the double quote, but the items in the given record clearly are not.

Performing the request from the command-line in a new job rather than via the CLP and in a job that has performed other work might exhibit a different effect; may be worth a test attempt.

That same request made with the given record on the PUB1.DE public v5r3 system functioned without any errors.

If none of that is helpful, then ...

The means to create the target of the import and the error record file were not included, but those could be helpful to identify the issue. Also helpful would be the first few stream records of the STMF, regardless the /first/ record was asked to be skipped; much more relevant, given "every record" gets the error. A sample of just a few redacted records that still exhibit the errors would be ideal, along with the hexadecimal code points of the data; plus the CCSID of the STMF and the CCSID of the fields of the DBF.