Re: PF to .TXT & Trailing Blanks -- MIDRANGE-L

Subject: Re: PF to .TXT & Trailing Blanks
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Tue, 10 Jan 2017 21:37:30 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Justin:

Did you specify ENDLINFMT(*FIXED) on the CPYTOSTMF command?

Mark

> On 1/10/2017 8:17 PM, Justin Taylor wrote:

I have a command I created almost ten years ago that users use to copy PF's to fixed-width text files on the IFS. It uses CRTPF to create a QTEMP PF of the same length as the real PF. It then copies the real PF into the QTEMP PF, and finally uses CPYTOSTMF to copy the QTEMP PF into a stream file.

It's now been discovered that this trims trailing blanks, and this has been deemed as unacceptable. I'm hoping to find a way to accomplish this without doing it from scratch.

Any ideas?

Thanks

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: PF to .TXT & Trailing Blanks , Justin Taylor

This mailing list archive is Copyright 1997-2025 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.