Re: Future of RPG was: Open Access for RPG

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Aaron

It should not be necessary to change CCSID of source and recompile - 
that is one solution, but it is needed only if you use character 
literals in the source. We have done that here with one of our products.

As I understand it - and Bruce Vining can say more and correct me - if 
you have text in PFs and MSGFs and it's flagged with a CCSID, the system 
just converts it as needed. This is very cool and the secret to simple 
national language processing.

That's a very simplistic description, but I think it's essentially 
correct. But please, others need to weigh in here.

Vern

On 7/29/2010 7:23 AM, Aaron Bartell wrote:
> I will try your method Henrik.  Thanks for the note.
>
> Aaron Bartell
> http://mowyourlawn.com
> http://mowyourlawn.com/blog/
>
>
>
> On Thu, Jul 29, 2010 at 1:10 AM,<hr@xxxxxxxxxxxx>  wrote:
>    
> > This is a well known distribution problem.
> >
> > When you compile a program the hexadecimal values of characters
> > in the module is the value according to the source file CCSID.
> >
> > If you have other sourcefiles with a different CCSID the hex
> > value will be different in the main program and because programs
> > communicates in hex this will never work.
> >
> > To avoid this problem, the easy way is:
> >
> > When you install, create new empty sourcefiles with the system
> > CCSID. Then copy the delivered sourcefiles to the new empty
> > sourcefiles (this will translate hex values) and recompile the
> > delivered service programs. The hex value will now be the same
> > in the service program that they will be in the main programs.
> >
> > Henrik
> >