RE: New application using remote databases from RPG program

It may be even worse than that. Each record may be encoded differently.

Where I work, our files have a CCSID other than 65535 defined but our
users jobs are CCSID 65535, and they use iSeries Access for Windows with
different code pages specified. There is no conversion functionality
built into the application(s) that use the files, so variant characters
in each record can only be viewed correctly by users who have the same
iSeries Access for Windows code page as whoever entered/maintained the
record data.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of sjl
Sent: 05 February 2010 15:03
To: midrange-l@xxxxxxxxxxxx
Subject: Re: New application using remote databases from RPG program

Which in itself raises another interesting question. All of the fields
in
all of the files on all systems are described with CCSID(65535).
Regardless
of whether I use DRDA or DDM, it will be up to /me/ to know how the text

fields are encoded in each file on each system, right?

- sjl



I wrote:
There is one slight complication.

One of the systems is double-byte, so, if using traditional I/O and
overriding the files within the program to DDM files, at a minimum
there
would need to be two sets of files defined in the RPG program - one
set to
use against the single-byte files, and another to use against the
double-byte files...