On Mon, 25 Dec 2017 19:59:33 +0200, ITschak Mugzach wrote:
>tested with no conversion, does not convert http header, SO_ASCII is a
>must. I can't understand the issue with the { to : translation in TSO...
>
With CMS RXSOCKET, a quadrant of the Galaxy far away, I believe I have
sent commands with SO_ASCII, then switched to binary for message body.
(The TCPCLIENT stage is considerable argument for CMS/TSO Pipelines
on z/OS.)
>On Mon, Dec 25, 2017 at 7:47 PM, ITschak Mugzach wrote:
>>
>> - Protocol is HTTP
>>
Are you the client or the server?
>> - D UNI,A displays first 01047-1200(13488)-r first (but there others)
>> - not sure how to determine the unrecognized code point...
>> - True. I am using terminal type 3278 translation table.
>>
x3270 and probably many others provide dozens of terminal character sets.
For example, I can set host CCSID to IBM-1047 and client to UTF-8.
There's an ISPF command to display the terminal charset (as seen
by the host).
ISPF Edit/View is fairly clever at handling UNIX files tagged with CCSID
if the terminal CCSID matches.
>> - regrading the translation, this is a good idea to do that myself.
>> thanks, will try that.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
