Two things. Not all mainframes were EBCDIC based. Some were field data based 
yet handled the translation to/from ASCII and to/from EBCDIC. Burroughs used 
EBCDIC but sign bits were on the opposite end of a word as I recall. 

S/360 machines I worked on had a switch in the PSW to set them in ASCII mode. I 
don’t remember or know of any software that made use of this. So that bit was 
eventually required to be ON to force DAT or XA. I have forgotten what that bit 
was “stolen” for now. 

Just some more architecture history. 

Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct 
mistaks 


> On Nov 19, 2018, at 4:11 PM, Pew, Curtis G <[email protected]> 
> wrote:
> 
>> On Nov 19, 2018, at 2:52 PM, Tony Harminc <[email protected]> wrote:
>> 
>> I'd say it's an "EBCDIC in an ASCII world" problem; not anything
>> fundamentally wrong with EBCDIC. Imagine if the original IBM PC had
>> been an EBCDIC machine. OS/2 and Windows would surely have followed,
>> Unicode would've been EBCDIC-based, and we'd live in a different but
>> not necessarily worse world.
>> 
> 
> What’s “fundamentally wrong” with EBCDIC is it’s non-standard. Sure, 
> as far as just one set of mappings of codes to characters there’s nothing 
> inherently superior about ASCII, but being a standard across different 
> vendors and operating systems makes ASCII superior.
> 
> By the time the IBM PC came along, everybody outside the mainframe world had 
> standardized on ASCII; if it had used EBCDIC it probably wouldn’t have had 
> as much uptake.
> 
> The truly sad thing is that Bob Bemer was working for IBM and had convinced 
> upper management of the importance of ASCII during the development of 
> System/360, but this understanding wasn’t communicated to the engineers, 
> programmers, and (notably) customers who needed to implement it. As a result, 
> those of us who work with z/OS, z/VM, and z/VSE are burdened by character 
> encoding issues that don’t face people on other systems/OS’s.
> 
> I just spent an hour this very morning explaining to a developer why a 
> EBCDIC->ASCII process wasn’t translating square brackets and a few other 
> special characters the way he expected. If the System/360 community had 
> embraced ASCII, as IBM’s management had intended, I could have spent that 
> time doing something useful.
> 
> -- 
> Pew, Curtis G
> [email protected]
> ITS Systems/Core/Administrative Services
> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
> Ûˆ›ÝˆNKŒN]
> ŽLˆKÛžH\›Z[˜ÈÛžPT“RSË“‘UˆÜ›ÝNƒBˆBˆIÙØ^H]    
> ÜÈ[ˆ‘PÑPÈ[ˆ[ˆTÐÒRHÛÜ›ˆ›Ø›[NÈ›Ý[ž][™ÃBˆ[™[Y[[HܛۙÈÚ]PÑPˈ[XYÚ[™HYˆHÜšYÚ[˜[P“HÈYBˆ™Y[ˆ[ˆPÑPÈXXÚ[™KˆÔË̈[™Ú[™ÝÜÈÛÝ[Ý\™[H]™H›ÛÝÙY
> Bˆ[šXÛÙHÛÝ[    Ý™H™Y[ˆPÑPËX˜\ÙY
> [™ÙIÙ]™H[ˆHY™™\™[]Bˆ›Ý™XÙ\ÜØ\š[HÛÜœÙHÛÜ›
> ƒBˆBƒB•Ú]8 &\È8 '[™[Y[[Hܛۙø 'HÚ]PÑPÈ\È]8 &\țۋ\Ý[™\™
> ˆÝ\™K\Ș\ˆ\ȝ\ÝÛ™HÙ]ÙˆX\[™ÜÈÙˆÛÙ\ÈÈÚ\˜XÝ\œÈ\™x 
> &\È›Ý[™È[š\™[HÝ\\š[܈X›Ý]TÐÒRK]™Z[™ÈHÝ[™\™XÜ›ÜÜÈY™™\™[™[™ÜœÈ[™Ü\˜][™ÈÞ\Ý[\ÈXZÙ\ÈTÐÒRHÝ\\š[Ü‹ƒBƒBžHH[YHHP“HÈØ[YH[Û™Ë]™\žX›ÙHÝ]ÚYHHXZ[™œ˜[YHÛÜ›YÝ[™\™^™YÛˆTÐÒRNÈYˆ]Y\ÙYPÑPÈ]›Ø˜X›HÛÝ[¸
>  
> &]]™HY\È]XÚ\ZÙKƒBƒB•H[HØY[™È\È]›Øˆ™[Y\ˆØ\ÈÛÜšÚ[™È›ÜˆP“H[™YÛ۝š[˜ÙY\\ˆX[˜YÙ[Y[ÙˆH[\ܝ[˜ÙHÙˆTÐÒRH\š[™ÈH]™[ÜY[ÙˆÞ\Ý[KÌÍŒ
> ]\È[™\œÝ[™[™ÈØ\Û¸ 
> &]ÛÛ[][šXØ]YÈH[™Ú[™Y\œË›Ùܘ[[Y\œË[™
> ›ÝX›JHÝ\ÝÛY\œÈÚÈ™YYYÈ[\[Y[]ˆ\ÈH™\Ý[
> ÜÙHÙˆ\ÈÚÈÛÜšÈÚ]‹ÓÔˋՓK[™‹Õ”ÑH\™H\™[™YžHÚ\˜XÝ\ˆ[˜ÛÙ[™È\ÜÝY\È]Û¸
>  &]˜XÙH[ÜHÛˆÝ\ˆÞ\Ý[\ËÓÔø 
> &\˃BƒB’H\ÝÜ[[ˆÝ\ˆ\È™\žH[Ü›š[™È^Z[š[™ÈÈH]™[Ü\ˆÚHHPÑPËOTÐÒRH›ØÙ\ÜÈØ\Û¸
>  
> &]˜[œÛ][™ÈÜ]X\™Hœ˜XÚÙ]È[™H™]ÈÝ\ˆÜXÚX[Ú\˜XÝ\œÈHØ^HH^XÝY
> ˆYˆHÞ\Ý[KÌÍŒÛÛ[][š]HY[Xœ˜XÙYTÐÒRK\ÈP“x 
> &\ÈX[˜YÙ[Y[Y[[™Y
> HÛÝ[]™HÜ[][YHÚ[™ÈÛÛY][™È\ÙY[
> ƒBƒB‹KHB”]ËÝ\\ÈÃB˜Ý\\Ëœ]Ð]\Ý[‹]^\Ë™YCB’UÈÞ\Ý[\ËÐÛÜ™KÐYZ[š\ݘ]]™HÙ\šXÙ\ÃBƒBƒB‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB‘›ÜˆP“KSPRSˆÝXœØÜšX™H
> ÈÚYÛ›Ù™ˆ
> È\˜Ú]™HXØÙ\ÜÈ[œÝXÝ[ÛœËBœÙ[™[XZ[È\ÝÙ\\ÝÙ\‹XK™YHÚ]HY\ÜØYÙNˆS‘“ÈP“KSPRSƒB

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

Reply via email to