× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2017

Re: SQL & CCSID's

Hi, Barbara:

Thanks for clarifying that.

All the best,
Mark S. Waterbury

> On 3/27/2017 4:27 PM, Barbara Morris wrote:
On 2017-03-27 3:43 PM, Mark S Waterbury wrote:

Do you have this H-spec in your RPG IV code?

H CCSID(*CHAR:*JOBRUN)


That would only help with conversions between alphanumeric and Unicode within the RPG code. If the job CCSID only supports single-byte data, the (bizarre) default for the CCSID of alphanumeric data is the mixed-byte CCSID related to the job CCSID.

So if your job CCSID is 37, then by default, RPG assumes that your alphanumeric data has CCSID 937, so it interprets x'0E' and x'0F' as the DBCS shift in/out characters. With CCSID(*CHAR:*JOBRUN), RPG assumes that your alphanumeric data has CCSID 37 and x'0E' and x'0F' are just ordinary characters.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.