Re: CCSID - RPG issues -- RPG400-L

Subject: Re: CCSID - RPG issues
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Thu, 26 Feb 2026 12:49:33 -0500
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

On 2026-02-26 8:40 a.m., Birgitta Hauser wrote:

SQL could always handle single byte and double byte character sets ... and
UTF-8 correctly. Transformation occurred automatically.
The problem was always RPG because the data is converted into the Job CCSID.
BTW what is your Job CCSID? 65535?

He has DATA(*NOCVT) for the file and CCSID(*EXACT) for the data structure, so it should not be converting the data to the job CCSID. With DATA(*NOCVT), it should get the data correctly even if the job CCSID is 65535.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

New IBM idea - Named Parameters at Program and Procedure Calls , Birgitta Hauser

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.