Re: Double Byte -- BPCS-L

Hello,

I suggest that you call the SSA GT Support Line in Australia so that they
can make sure you have all available BMRs for Double-byte issues with the
Fat Client (ALAUNCH) programs.

In Fat Client applications, the software on the PC will sense when you have
a DBCS character input in ASCII. When it sends the data in EBCDIC format to
the AS/400 it will put in automatically the hex Shift/In and Shift/Out
characters around the DBCS sections using a special program to translate the
ASCII hex characters into EBCDIC hex characters (PC to AS/400). You do not
need to do this yourself in the PC Windows BPCS applications.

There have been some BMRs for Client/Server programs. I do know that one
issue we corrected was a problem that if the user types in too many DBCS
characters for the existing spaces in the AS/400 field (such as single byte
characters, double byte, then again single byte, then again double byte),
the Fat Client (ALAUNCH) applications did not always count the number of
bytes this string would have on the AS/400 side, and would not 'see' that
the string had become too long to fit into the BPCS files. So, it would send
too much data down to the server. It did not calculate the extra space taken
by all the required 'Shift/In' and 'Shift/Out' characters.

On the server side, this data string that was now too long then got put into
the BPCS file, and this became corrupted data because it could not fit
properly into the BPCS file field. In this case, some part of the end of the
string gets cut off (often 1/2 of a double-byte character set )  - this is
the corruption. This problem was corrected in a BMR, by sending warnings to
the user when they put in too many DBCS characters for the field on the
server to hold the data.

Please contact the SSA GT Support Line for more details about the available
BMRs for your release of BPCS.

Thanks,

Genyphyr Novak
SSA GT

----- Original Message -----
From: "Ren Fu Ping" <fupingren@yeah.net>
To: <bpcs-l@midrange.com>
Sent: Thursday, May 16, 2002 3:44 AM
Subject: Double Byte


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Dear Guys,
        We are As/400 box 820 and BPCS V6.1.01 MM.
        Double Byte problem is facing on my desk!
       we find some data has been corrupt through SQL, RPG report, and
UPDDTA tools etc, but displayed normally in CEA mode, any BMR to fix this
problem? or any suggestion to handle with. as we know, when in green mode,
we should press 'CTRL + F1' to frame the beginning chinese character and the
end character in order to avoid double byte corrupting, but in window mode,
we can't. How to handle it and Why?

thanks in advance for any help.
Ping
China

--

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.