There are a few layers to getting the codepages right for using a terminal
emulator and ISPF Edit and Browse on the host.
For example, in Personal Communications I first define my host codepage.  I
have a lot of choices. From 420 (Arabic) to 1130 (Vietnamese).  I tend to
use 1047 (U.S.) to get my square brackets right.
Reference:
https://www.ibm.com/docs/en/personal-communications/15.0?topic=pages-contents#ToC

Then, on the host side. If you are using the ISPF UDLIST interface to Unix
(OMVS) you can use either EBCDIC, ASCII, or UTF8 for EDIT or VIEW.
Reference:
https://www.ibm.com/docs/en/zos/3.1.0?topic=317-zos-unix-directory-list-utility-line-commands

If you are not editing/viewing a Unix file, then you can use the primary
command SOURCE ASCII if you need to.

In ISPF Browse, you can use the DISPLAY command to view data as UTF8,
UTF32, UCS2, UNICODE, ASCII, USASCII, and EBCDIC, or specify the numeric
CCSID.
Reference:
https://www.ibm.com/docs/en/zos/3.1.0?topic=information-pdf-browse-primary-commands



On Tue, Oct 10, 2023 at 2:22 PM Seymour J Metz <[email protected]> wrote:

> Mostly not ASCII, which is where the trouble lies, at least until
> everybody is Unicode and the code page madness goes away.  Only 0-127 are
> ASCII, and even there it is common to repurpose 0-31.
>
> ________________________________________
> From: IBM Mainframe Discussion List <[email protected]> on behalf
> of Rick Troth <[email protected]>
> Sent: Tuesday, October 10, 2023 4:15 PM
> To: [email protected]
> Subject: Re: TN3270, EBCDIC and ASCII
>
> Not late at all.
>
> The copy-n-paste point makes me wonder if the fonts are actually mapped
> to ASCII values.
> I don't know graphical environments well enough to analyze it. But it
> would mean that, yes, there *is* A/E translation happening even in the
> graphical 3270 emulators. (In hopes of not steering Juan wrong with what
> I said before.)
>
> -- R; <><
>
>
> On 10/10/23 14:19, Steve Thompson wrote:
> > I am replying a bit late to this.
> >
> > However, when you do a copy/paste from the TN3270 screen to Notepad
> > (as an example), it then becomes "ASCII". Same for copy to Word.
> >
> > Now, if you copy from your workstation and paste into the TN3270
> > emulator, it gets converted/translated to "EBCDIC" and watch out for
> > the ] [, and others becoming goofy.
> >
> > Just thought you might need that bit of info.  I've used QWS3270,
> > EXTRA, VISTA, HOD (Host On Demand), and one or two others.
> >
> > Steve Thompson
> >
> > On 10/10/2023 12:18 PM, [email protected] wrote:
> >> Hi!
> >> I want to understand how TN3270 emulation works regarding convertion
> >> of characters (between EBCDIC and ASCII, and viceversa).
> >> This is how I think it works (more or less), but I am not sure at
> >> all. So please let me know about any mistakes.
> >> Let suppose that you use a TN3270 emulator program to access the ISPF
> >> browser to display a dataset. Let also assume, to simplify, that it
> >> contains just a single character, an "A".In DASD, what is indeed
> >> stored is X'C1' or, to be more accurate, BINARY'1100 0001'. When you
> >> BROWSE the dataset, then the Mainframe sends to the TN3270 PC client
> >> exactly X'C1' (BIN'1100 0001'). No convertion is done at the
> >> Mainframe side. Then, when the TN3270 client receives X'C1', because
> >> it knows that this is a TN3270 session and that its configured
> >> CODEPAGE is say 500, it realizes that X'C1' corresponds to an "A"
> >> displayable character. And, before sending the instruction to display
> >> it on the PC screen, it converts X'C1' to X'41'.
> >> Is this more or less how this works?
> >> Thanks in advnace for your help,
> >>
> >> Juan Mautalen
> >>
> >> ----------------------------------------------------------------------
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to [email protected] with the message: INFO IBM-MAIN
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to