Re: CPYFRMIMPF fails since V5R3

[Steve Richter <stephenrichter@xxxxxxxxx>]

cpyfrmimpf bombs on me when I code the EOR parm incorrectly.  I used
the default value for that parm when I should have said *CR - the
result was pages and pages of machine code errors in the joblog. Then
another file I used *CR instead of *CRLF and I got some sort of field
conversion error.

-Steve

On 9/13/05, Titus Kruse <t_kruse@xxxxxxxxx> wrote:
> 
> Thank you for this! But I've read the documentaion to these PTFs and APAR
> and they all don't match my problem. We will allthough install them.
> 
> Titus
> 
> 
> 
> <michael@xxxxxxxxxxxxxxxxxx> schrieb im
> Newsbeitrag
> news:20050913032209.1cba8986f1dca4f8555220876195c2e0.c162a575de.wbe@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Check out these PTFs...SI18900 and SI18637 and this APAR...SE17667.
> >
> >
> > > -------- Original Message --------
> > > Subject: CPYFRMIMPF fails since V5R3
> > > From: "Titus Kruse" <t_kruse@xxxxxxxxx>
> > > Date: Tue, September 13, 2005 5:00 am
> > > To: midrange-l@xxxxxxxxxxxx
> > >
> > > Hi!
> > >
> > > I'm using CPYFRMIMPF to import a CSV-file to a database file for a
> couple of
> > > month now. Since we have updated to V5R3 the command fails with a lot of
> > > MCH0601 messages. I think some input fields are longer than the
> > > corresponding database-fields. But on previous releases this wasn't a
> > > problem. And the documenation for the command also says: "Fields in the
> > > from-file that are longer than the corresponding fields in the to-file
> will
> > > be truncated (on the right)." Creating the dataarea QCPFRMIMPF in QSYS
> > > solves the problem but is no solution to me. Does anybody have another
> idea?
> > > Is a PTF available?
> > >
> > > T. Kruse
> > >
> > >
> > >
> > > --
> > > 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 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.
> 
>