RE: More Stream File and DBCS issues...

Hi Brad,

FWIW text for CPE3490 is Conversion error. One or more characters could not
be converted from the source CCSID to the target CCSID. 

What is the from CCSID? What is the to CCSID? Are they both DBCS (or more
probably mixed)?

Regards,

Kevin Wright. 

-----Original Message-----
From: Brad Stone [mailto:brad@xxxxxxxxxxxx]
Sent: Thursday, 2 November 2006 2:36 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: More Stream File and DBCS issues...


Even more information.

EVERY time it writes DBCS data it returns 3490..  A return
code perhaps?  :)

Brad

On Wed, 01 Nov 2006 21:43:30 -0500
 "Brad Stone" <brad@xxxxxxxxxxxx> wrote:

I found more information on this doing a debug.  It may
or
may not relate to my socket CCSID issue I am having.

On the call to the write() API, I'm writing out 128
bytes.
 The return code after the call is saying it wrote 3490
bytes.  There are probably 10 DBCS character in this
data..
the rest is SBCS.  But every write after this, even
containing SBCS is corrupted.  And the RC for SBCS data
write() calls shows the same amount of bytes written as I
told it to write.

It's almost like it's totally messing up my pointer
position as I am using %addr() for the data parm on the
write() API.

Any ideas, I'm open ... off to scour the docs now.. 

Brad

On Tue, 31 Oct 2006 22:32:16 -0500
 "Brad Stone" <brad@xxxxxxxxxxxx> wrote:

Ok, this one really is weird.

I am converting files to different formats.  The data
contains DBCS data and SBCS data.

We got past the point of making a plain text or .doc

file

working (.doc being basically a plain text with CRLF

for

the lines).

Now we're doing PDF.  Which technically should make

zero

difference.

We read the data in (a line of text), then write it out
to
a stream file using the write() API.

When it hits the line with the DBCS data in it, it just
freaks out and starts writing garbage to the file.

The ONLY difference in the text we're writing out is it
is
enclosed in ( and ) ends with a single quote.

I checked the data right before the Write(), checked

the

length it was passing in, and everything is fine!  It
writes 12 lines before this one just fine, but once it
hits
the DBCS data, boom.

Makes no sense to me.  It is PDF data, but it's really
"just plain text".  And all data after it, even straigh
SBCS data is also garbage.

The only thing I could find was the hex value for the
line
that it starting bombing out on, instead of writing the
real data, it was x'FEFE'

The only thing I can think of here is a bug in the OS
with
the write() API.

Anyone else seen anything like this, or have any ideas?

So:

eval Data = 'This is DBCS Data'

if I write just Data, it is fine, even the DBCS data.

If I do:

eval Data = '(' + %trimr(Data) + ') '''

It starts writing just garbage.. and not even the same
length of string garbage.  :)

Argh  [pulling hair out]

Thanks in advance!
-- 
This is the RPG programming on the AS400 / iSeries
(RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/rpg400-l.

Bradley V. Stone
BVS.Tools
www.bvstools.com
-- 
This is the RPG programming on the AS400 / iSeries
(RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/rpg400-l.

Bradley V. Stone
BVS.Tools
www.bvstools.com
-- 

This is the RPG programming on the AS400 / iSeries (RPG400-L) 
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.