On Thu, 9 Jan 2014 22:44:19 -0500, Don Poitras wrote: >As of z/OS 2.1, ISPF supports UTF-8, so a binary transfer will still show an A >if it >was an A on the PC. ... > Does this support both UNIX and legacy files? If the latter, does it require RECFM=V? Using a variable-length character encoding in fixed length records seems pretty inconsistent.
How does it report invalid UTF-8 byte sequences? Does it still automatically switch to CAPS ON? What does it recognize as majuscule or minuscule with CAPS ON in Cyrillic characters, e.g.? >I don't know which emulators will show all the other bazillion >glyphs though... > Indeed. Emulators? What about hardware for the emulators to emulate? Or does it require WSA? What representation does it use in the 3270 data streams? Is this well documented in the Data Streams reference? What must it do to avoid embedded 3270 command bytes? Is this compatible with Yale/7271/IND$FILE/Kermit conventions? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
