On Mon, 11 Nov 2013 14:03:22 -0500, John Gilmore wrote: >John McKown's description of how the assembler handles alphabetic case >characterizes its default behavior correctly. > >Finer control is, however, available. Specifying either or both of >the keyword values NOCASE and NOMACROCASE of the COMPAT assembler >option instructs the assembler NOT to make the replacements of >minuscules with majuscules that it would oitherwise make, in the >corresponding places. > With the paradoxical consequence that COMPAT(NOMACROCASE) yields behavior compatible with Assembler H, and COMPAT(MACROCASE) yields incompatible behavior.
On Mon, 11 Nov 2013 13:52:21 -0500, Gerhard Postpischil wrote: > >AFAIK the 026 was useful only for S/360 predecessors, and the 029 was >the first supporting the S/360. An 026 ) + ( = ' were treated as < & % # >@ respectively, and I wrote a little conversion routine to translate all > Whatever they were "treated as" worked fine for FORTRAN on the 709. It's just a code page phenomenon. >my decks to the S/360 equivalents. As to lower case, it was possible, >but not pleasant. The 026 and 029 will produce overpunches if you firmly >press down on the card while punching, preventing it from advancing to >the next column. > IIRC, the 026 had a MULT PCH key which simulated the effect of thumb. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
