Re: AS400 + Client Access EBCDIC to ASCII translation error: pipe to shriek

Thanks for your suggestion FT. The focus of the RPM product appears to
be geared to print jobs/queues. Apart from the translation error, I am
happy with the performance of reading data from an AS400 data queue and
am committed to staying with the tecnology in the short-medium term.

It may be possible that I could read data down from the data queue as
EBCDIC and write a custom EBCDIC-ASCII conversion routine to avoid what
corruption may be happening in Client Access....but, there must be
someone out there who has seen something like this before??



FT wrote:
Hi Gattsi,

We've used RPM over the years for the EBCDIC to ASCII conversion. Check
it out at http://lpd.brooksnet.com/convert-EBCDIC-to-ASCII.html. just
call their support if you run into problems.

Best of luck!

FT


gattsi wrote:
I have a VB app connecting to an AS400 via a data queue using client
access express objects. Messages read from the data queue to the PC
invariably contain pipe "|" characters as a delimiter for further
processing in the VB app.

Quite spontaneously, the pipe will be translated to a shriek character
"!" with no indication as to the cause. Only un-installing Client
Access and SP on the PC and then re-installing appears to fix the
issue. This has happend on a handful of sites each with varying mixes
of AS400 o/s and client access installations. It was first noticed in
AS400 o/s 5.1.

Only the pipe character in the message appears to be affect by this
translation error. The error can not be tracked back to the application
of PTFs or PC upgrades.

Has anyone witnessed this error before or have any clues to the cause?

.