Re: Avoiding CPF2973 and truncation -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks for the info folks and I want to copy from pf to pf where the input
is 200 recl and the output is 100 recl like Rob noted. We want to
automatically have all the data be put into the 100 recl file without
having to change the 100 recl file in any way...I didn't think that was
possible so I figured I'd ask you folks for options/possibilities...are
there any? The output file is a "flat" file. What's the syntax of the sql
insert...I'll try anything at this point. Mark/Rob/Vern, etc. thanks for
responding.
Frank

On Wed, Feb 9, 2022 at 3:45 PM frank boke <fboxxx1958@xxxxxxxxx> wrote:

Hi Folks, I'm looking for an easy way out or a trick that you folks might
have to avoid CPF2973 which is the commonly seen msg when copying from 1
file to another where the input file has a larger record length than the
output. Is there any way to keep the output file with a smaller recl and
avoid truncation? I didn't think so but I figured if anyone would have
ways around this or a quick way to avoid it I'd be happy to hear any.
Thanks, Frank

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.