Re: External Data Structures -- JAVA400-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: External Data Structures
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 12 Feb 2020 14:04:16 -0700
List-archive: <https://archive.midrange.com/java400-l/>
List-help: <mailto:java400-l-request@lists.midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.lists.midrange.com>
List-post: <mailto:java400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/java400-l>, <mailto:java400-l-request@lists.midrange.com?subject=unsubscribe>

Ah, I see.

On Wed, Feb 12, 2020 at 2:03 PM David Gibbs via JAVA400-L <
java400-l@xxxxxxxxxxxxxxxxxx> wrote:

On 2/12/20 2:56 PM, Jack Woehr wrote:

The first issue is the fact that Java uses unicode and the native

encoding

on IBM i is EBCDIC. You will have to deal with data conversion.

Gonna write on this next?

The technique I write about handles mapping the data to appropriate Java
types
and character conversion.

As an Amazon Associate we earn from qualifying purchases.

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.