The main difference among the various flavors of EBCDIC is where the square brackets are. The rest is mostly accented letters. Who knows how that came about, but I'm sure it's not interesting.
It seems that HLASM may have wandered into the code-page swamp without a complete plan. sas On Mon, Jan 13, 2014 at 5:12 PM, Paul Gilmartin <[email protected]>wrote: > On 2014-01-12 17:58, Gainsford, Allen wrote: > >>>> I get: > >>>> > >>>> //SYSIN DD PATHOPTS=ORDONLY,FILEDATA=TEXT,RECFM=FB,LRECL=80, > >>>> // BLKSIZE=8000,PATH='/tmp/user/Polyglot.s' > >>>> > >>>> 1 High Level Assembler Option Summary (PTF UK97444) Page > 1 > >>>> ... > >>>> 000000 ADBD 2 DC C'[]' 037: BA > BB 1047: AD BD 1148: 4A 5A > >>>> 000002 ADBD 3 DC CA'[]' 5B 5D > > > > Yes, but what you're seeing as "[]" in your listing above is the > codepage-1047 [] characters (hex AD/BD). But the Assembler expects > codepage-037 characters. AD and BD don't correspond to printable > characters in codepage 037 (or at least not ones that HLASM seems to want > to handle; it looks to me like they're a capital Y-acute and an umlaut), so > it looks like it just leaves them alone. > > > Looking at: > > CODEPAGE > > HLASM Programmer's Guide > SC26-4941-06 > > Read syntax diagramSkip visual syntax diagram > .-CODEPAGE(1148|X'47C')---. > >>-+-------------------------+--------------------------------->< > '-CODEPAGE(nnnnn|X'xxxx')-' > > Default > CODEPAGE(1148|X'47C') > > ... and looking elsewhere, it seems that CP1148 maps AD and BD to the > same Ý and ¨. And the ISO8859-1/CP819 for those are hex DD and A8. > Why weren't the AD converted to DD and BD to A8. Where is it documented > what ASCII code page CA'...' converts to? I haven't found it yet. > Might it be because DD and A8 lie outside the USASCII half of CP819? > Is there a restriction here documented somewhere? I haven't found > it yet. > > I hate EBCDIC! > > -- gil > -- sas
