I was dealing with mixed case long before HLASM; the issues were manageable. YMMV.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Jon Perryman <jperr...@pacbell.net> Sent: Thursday, August 28, 2025 5:09 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector instruction performance External Message: Use Caution On Thu, 28 Aug 2025 09:20:55 +0100, Jonathan Scott <jonathan.scott...@gmail.com> wrote: >HLASM itself contains a lot of mixed-case assembler source, >and the HLASM operating system interfaces for MVS, CMS and Linux >are mostly written in mixed-case PL/X. I think most people forget the impact mixed case had on them personally. Those who called in a SEV1 caused by mixed case probably won't forget nor product support that handled those sev1. I doubt anyone involved in hiper ptfs caused by mixed case will likely forget. Remembering the impact of mixed case depends upon how much a person was annoyed by it's problems. I suspect there was a point in time when mixed case became possible in HLASM, MVS and others products. Standards had to evolve and products were change because of mixed case. It diverted attention away from the product. I think development of z/OS Unix had IBM solving mixed case long before vendors and customers were exposed. >There are indeed some limitations on macro keyword values, >but an increasing proportion of macros have been coded or modified to support >lower case values. In the beginning, most macros needed mixed case changes. After all these years, there are still macros that do not fully support mixed case. >Data type CU is Unicode, which has nothing to do with upper case. Sorry, my bad. I knew that but had a brain freeze. >A macro can convert a string to upper case using the UPPER built-in function. Upper simplified the conversion but design considerations were a far greater impact..
