> There's an ISPF command that tells the CCSID in use by a TSO/ISPF session. > That's set by the LOGON handshaking protocol.
It's actually much more complicated than that. The 3270 data stream allows you to query the base CCSID of the terminal, but thee are also multiple levels of translation in the software, with facilities to control them, e.g., TSO TERMINAL TRAN(name), ISPF ISPTTDEF. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Friday, September 7, 2018 3:10 PM To: [email protected] Subject: Re: [EXTERNAL] Re: Co:Z question On Fri, 7 Sep 2018 14:53:59 +0000, Seymour J Metz wrote: >> Z/OS does not have a code page. > >But it does have *many* code pages and it does have a chcp command. > A z/OS UNIX command: https://secure-web.cisco.com/1Va_mojAZM56J02u0Wvea6hlLwwOpBhiUJcmtN0HG8s4Y1A3I-b4n-9uBqtmi7NX93Qbb4-UmF-OfnAS-nraxFQevKkgk_gGlSZdB6jDIVAHdLIRtAYA60AM7lTa8Q0iHG4clRr8jfGzXrPiabuXtlCU4dnuNTPPpg_vv4HO5fDnGd93N1c0YezABb1qdEaj7qBp_IoeJ2N4mebaDEGFpbhIeomTKNN4NgTqG28F06DdAeB33m8I6qcxflaoT3ARVC6yja3sW0o9k81fIQ7VEgE5Z2QSAWqmkmljdAsuHoYwQ56Pb-R3P8Ps88_4Y7kMypaIwQfPoImAqtg52nNAufkZCXVBcvoU-lp64OG2p3Y3VerCS00bACfdthvWSZH9o_K5OgNHR-wbIrUJ94Dt1X7uT7GksDNejGoAazdqzxp5tCG2nKu1p1ht81smX_Ngq/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.bpxa500%2Fip1.htm Format chcp [–r | –q] chcp [–s] [–a ASCII_cp] [–e EBCDIC_cp] Description chcp sets, resets, or queries the current ASCII/EBCDIC code conversion in effect for the controlling terminal. Use it when the terminal requires ASCII data and the shell application uses EBCDIC. Do not use chcp if you are logged on through the TSO/E OMVS command. The _BPX_TERMPATH environment variable enables shell scripts to tell if the user logged on from TSO, rather from rlogin or telnet. ... For a list of code pages supported by the shell, see z/OS XL C/C++ Programming Guide. https://secure-web.cisco.com/1r0ILdk1L-0beWmKT_ETL9Hh3FDGiWtHUeCSCpplEO30y8HZ7WRCQA8eeeZ53Ux8Cd14u1_qqdriVTH2p6J_MjEZ86l4BcHYpda1T7HGfwHYCD6iPXS7lEnQR5ZC8Jbd46SUmIc1Jo3-i3ju2phEGsTcAnNLYN2doXpUDr2YKWl6NyZ6XU1xtzUEy9b0S6iLuM_6lZBJPGNXob42Hb07BhbXfXVwync3swUQ4_p1Z7PlqNhwtfU_hssqABZd5ygFR6GxMp53JImjmn9552a-B7bW4SK7pmIyubr10MRVcL-s-ORzPWKpwIga-1QcdYeqFFEMu2A0JvJmmkfWS42EqNTDQUB5a3KDwIlJ_59V6TWEXgiDtEDgUoA5Pgaih_RqsyubeiBgTH1I-nswJrXQzuuu0GiJdDTFGgEjp9Ge3dNqrcWVX0HrzwRoj17u64r-b/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.cbcpx01%2Ftoc.htm%3Fview%3Dkc Which section? It's a thick document. ... OK. It says you're not supposed to use it from a 3270 session. It doesn't say what happens if you try. And the OP has already said he's uncomfortable with the restriction. Does it cause automatic tagging of files created with a code page in effect? Does it affect behavior of classic data sets? E.g.: cp "//'my.data.set(member)'" /dev/fd/1 There's an ISPF command that tells the CCSID in use by a TSO/ISPF session. That's set by the LOGON handshaking protocol. Does it have any (useful) effect to code in a (perhaps custom) LOGON PROC: //TSO EXEC PGM=IKJEFT01,CCSID=... Why not? (Some) terminal emulators let you set the desktop code page and the host code page (the one reported by ISPF) independently. I have had good success with xterm, setting the desktop code page to UTF-8 and using various host code pages. ISPF 3.17 nicely displays tagged UNIX files, even UTF-8, as long as all characters exist in the terminal's configured host code page. Characters not so available display as attribute bytes. I don't believe TSO/ISPF supports 1208 as a terminal code page. I don't know about other MBCS code pages. I hate EBCDIC! -- gil ---------------------------------------------------------------------- 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
