Re: IFS stream file CCSID problem -- MIDRANGE-L

Subject: Re: IFS stream file CCSID problem
From: Pete Hall <pbhall@xxxxxxxxxxxxx>
Date: Thu, 29 Jul 2004 17:46:05 -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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

At 15:39 7/29/2004, James Lampert wrote:

I thought I was already doing everything I could to force the file to be
created with the correct CCSID. What could I be doing wrong? (I'd include
the appropriate source fragments, but the box those source members are on
is currently powered down).

I vaguely recall a parameter on the open call that specifies if it's a text file or not. If not, I'm pretty sure it's just considered binary, and no character translation takes place. It's been a while, but when last I tried, setting the CCSID on an NT share didn't do anything. It's just iso-8859-1, or whatever the Windows blinking code page is on Windows.

hth

Pete Hall http://www.pbhall.us

Follow-Ups:

RE: IFS stream file CCSID problem , Elvis Budimlic

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