Re: Moving bytes from a SBCS EBCDIC field to a DBCSUnicodefieldwithout translation

James H H Lampert wrote:
> 
> Type C? /free? Remember, we're using a V4R4 RPG compiler.
> Most of our customers are probably on V5, but not
> necessarily all, and we only have one test box, with no
> compilers at all, running V5.
> 
> Your other idea, of constructing the RPG VARLEN string
> from C would work extremely well, except for one problem:
> the C module doesn't know anything about the structure of
> the data. It's just passing a block of bytes. But thanks.
> 

Oops, didn't remember seeing anything about you using a V4R4 compiler. 
But type C is available for RPG starting in V4R4.  The fancy %TRIM isn't
available then, but you could trim the blanks and nulls using a loop
(ah, I see you already did that).

Regarding the C module, I guess I misunderstood this statement in one of
your posts.  I thought that your C server comm module might know the
length of data it was passing, and could build your varying length
unicode string for you.
   > ... Something simple I can do in the C server
   > communication module that passes the unicode from the
   > client to the RPG? At this point, I don't know whether I'm
   > going to be dealing with null-terminated or blank-padded.