Re: users pasting hex '41' into char fields...

On 05-Jul-2016 15:36 -0500, Gerald Magnuson wrote:

On 05-Jul-2016 15:14 -0500, Gerald Magnuson wrote:

I guess either I am very rare to have this trouble, or I can't
google right....

we are getting a hex x'41' at the end of some of the character
strings users are pasting into green screen fields..

So that pasted data. had been copied from where, for example?

The implication is that the IBM i program is receiving, as EBCDIC SBCS alphanumeric character data, the code-point 0x41, as a single-byte /character/ value in a character string pasted into the input\output field? And always\only at the end of the strings?

two questions:
one) how do I properly fix this?
two) how do I practically fix this?

Unclear if anything is actually incorrect; i.e. the code point 0x41 is valid EBCDIC data, for which nothing is inherently in need of a 'fix'.

I see in the new ACS emulator there is a "Translation Table", But
I wonder if that is just for file transfer?!? I can't seem to get
it to "convert x41 to x40"...

ok....
has anyone used this "translate table" feature of new ACS?

I said to translate 0x41 to 0x40..... now it turns my "A" (hex C1)
to Blanks....

Presumably the code point to be translated-from in ACS is ASCII, and the translation offered is into EBCDIC; i.e. ASCII 'A' (upper case A) as 0x41, having been requested to be translated into an EBCDIC ' ' (space) as 0x40, would seem to be the expected\correct effect.?

Given the 0x41 [in most EBCDIC code pages] is the Required Space (RSP) character [aka SP300000], and that same character in CP00437 is found at code point 0xFF, consider testing the effect from having set the translate table to effect translate 0xFF to 0x40; i.e. presumably, currently the effect is that ASCII 0xFF (RSP) translates to the EBCDIC 0x41 (RSP), but from the failed attempt "to translate 0x41 to 0x40", perhaps the intended effect is that ASCII 0xFF (RSP) translates to the EBCDIC 0x40 (SP) [aka ␠ aka SP010000].