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.

Subject: Re: Avoiding CPF2973 and truncation
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 10 Feb 2022 08:47:57 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Thu, Feb 10, 2022 at 8:44 AM frank boke <fboxxx1958@xxxxxxxxx> wrote:

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...

Is it just flat, one field of 100 chars or something?
So you would split each 200 char row into two 100 char rows?
Sounds easy to do in Python.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Avoiding CPF2973 and truncation , John Yeung

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.