Re: SQL issue with CCSID 65535 -- RPG400-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.

All is true and I think, IRC, that the OP said this program would be running on other systems - maybe it's a software vendor's product.

So I had responded that he could save the existing job CCSID, set the job CCSID to some non-HEX CCSID (65535), then restore the saved one. He was concerned that something would happen to the job before the CCSID could be changed back, I responded that there are exit and other error that might take care of that concern.

Anyway, this is my attempt to bring the thread back to mid-stream. :)

Vern

On 12/14/2019 2:37 PM, David Gibbs via RPG400-L wrote:

On Sat, Dec 14, 2019 at 8:41 AM <smith5646midrange@xxxxxxxxx> wrote:

Care to elaborate on that answer?

CCSID 65535 means no translation ... characters in other CCSIDs will
not be translated into the target CCSID.

If you are working with US english data, you should use CCSID 37 so it
can be translated to and from 1200.

In the multi-national, unicode enabled, world ... it's probably a good
idea to have your jobs running in the appropriate CCSID for your
locale.

david

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.