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. 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.
Data type CU is Unicode, which has nothing to do with upper case. A macro can convert a string to upper case using the UPPER built-in function. Jonathan Scott -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Jon Perryman Sent: 28 August 2025 06:27 To: [email protected] Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector instruction performance On Thu, 28 Aug 2025 01:44:32 +0000, Seymour J Metz <[email protected]> wrote: >There you go again, making things up. You don't have a clue as to what is or >is not painful to whom. Peter Relson & Paul Gilmartin. What are your coding standards for HLASM (or PLS) with regards to lowercase? You both advocated lowercase comments. Are labels, instructions and operands also in lowercase? It's been a very long time but I thought there were problems with macros where mf=l failed but mf=L was acceptable. Are you coding uppercase char constants using DC CU'xxx' instead of DC C'xxx' to guarantee they are uppercase?
