On Fri, 29 Aug 2025 12:43:14 +0000, Peter Relson <prel...@yahoo.com> wrote:
>I can tell you what I found most effective for reading the code: mixed-case Thanks for the insights. >I have never seen a z/OS-provided macro that uses UPPER for such things as the >MF value. > >not specific values, such as "L" within MF=L We have become so desensitized to our standards, that we no longer recognize when the standards are needed to support mixed case. >the notion of "unacceptable risk" might be thought to apply less to >development work You never know you're in a bubble until it pops. A sev 1 call arrives declaring automation is no longer trapping expected messages. People look for complicated instead of simple answers. I'm guessing the other vendor thought these are just messages and we can them more readable. I'm also guessing they issued a Hiper PTF or HOLD action. Our answer to the customer: stop panicking because automation is working fine for every other product and to regress the offending product until they understood the impact and changes needed to support mixed case events. That vendor ignored "if it isn't broke, don't fix it". Mixed case support didn't just happen otherwise you would not have standards and features to support mixed case (e.g. coding standards, profile lock, caps lock, upper functions and many more). > I don't know why you would change the change identifier. I would not do so. Our line change identifiers were fully automated. I'm surprised it's manual at IBM. The automated process makes it extremely difficult to justify style changes. ><snip>After all these years, there are still macros that do not fully support >mixed case.</snip> > >This probably has to do with the fact that "UPPER" has not "always" been >available for use, >There has never been sufficient business reason to make the investment. I'm not complaining. I'm trying to point out that we have become desensitized to the mixed case issues and that we have learned to live with those issues that still exist to this day. The solution to the problem changes the problem. USS file tags are an extension of mixed case issues. We ignore the impact of culture has on mixed case. After living in Germany, the German word Donaudampfschifffahrtselektrizitätenhauptbetriebswerkbauunterbeamtengesellschaft does not pose a challenge to read any more (funny note. its too long for HLASM without continuation line). After dealing with coding conventions for various languages, mixed case has taken on a definable meaning instead of grammatical syntax. > I never used "DC CU'xxx'" Sorry, my bad. I was thinking uppercase instead of unicode.
