Re: CCSID issue? -- 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: CCSID issue?
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Mon, 19 Aug 2019 15:50:48 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
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 Mon, Aug 19, 2019 at 2:35 PM Art Tostaine, Jr. <atostaine@xxxxxxxxx> wrote:

The first step that I do is CPYSPLF
Is it possible it's a bug when doing CPYSPLF to a flat file in QTEMP, then
CPYTOSTMF from Qtemp? The CCSID on CRTPF is *JOB.

A CPYSPLF bug is certainly possible, but is there a reason you're not
just copying directly to a stream file in the first place? (See the
*TOSTMF special value for TOFILE.)

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CCSID issue? , Art Tostaine, Jr.

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.