Our 3270 emulator is IBM's Personal Communications V5.0 for Windows, commonly known as PCOMM I believe. We use "0037 United States" as the host code page. the "NOT SIGN" is x'5F' in codepage 0037. All evidence I can find says that the "NOT SIGN" is x'AC' in unicode and on unix environments. If I use PCOMM to do a "text" conversion file transfer of the "NOT SIGN" from z/os 1.11 to ascii it translates correctly from x'5F' to x'AC'.
However, if I use the z/os 1.11 TCP/IP FTP the x'5F' translates to a x'5E' and does not retain itself as a "NOT SIGN". I cannot find any translation table in SEZAINST or SEZATCPX for codepage 0037 or any other codepage that translates an EBCDIC x'5F' into an ascii x'AC', in other words NOT SIGN to NOT SIGN. If I look at ascii back to EBCDIC tables in those libraries a x'AC' seems to translate back to a x'B7' in EBCDIC which makes no sense to me as a NOT SIGN. Even in codepage 1047 a NOT SIGN is x'B0'. Is there any translation table in z/os 1.11 that translates the "NOT SIGN" x'5F' to an ascii x'AC', the same as PCOMM accomplishes? There are other characters having issues as well, but I'm happy to concentrate on this one for now. Thanks, Tom ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
