I worked as a contractor for a few busy years, and based on my (admittedly limited) experience (including banks and insurance) it was almost 50:50 mixed case:all upper case.
I can quite happily type mixed case assembly, but one thing I learned during those contracts was respect. Respect for the team, respect for local standards. And I'd never upper case someone else's work without asking first. But this all looks like a moot point when code and comments are all upper case, apart from a MSG DC C'This text is for the User'. Yes, I used ISPF edit "nulls on", "caps off", "profile lock" and from memory "tabs on \" for assembly just for speed, with soft tabs at 10, 16 and 41. Roops --- "Mundus sine Caesaribus" On Thu, 28 Aug 2025, 13:37 Seymour J Metz, <[email protected]> wrote: > You are the one that is wasting time, by making things up about what > others like or do not like. Claiming that someone is the only one to be > comfortable with lower case brands you as either a liar or a fool. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > עַם יִשְׂרָאֵל חַי > נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר > > > > > ________________________________________ > From: IBM Mainframe Assembler List <[email protected]> on > behalf of Jon Perryman <[email protected]> > Sent: Thursday, August 28, 2025 3:38 AM > To: [email protected] <[email protected]> > Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector > instruction performance > > > External Message: Use Caution > > > 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. > > Once again, I'm begging Metz to stop wasting my time with his ignorance. > > Some have mentioned using separate datasets to isolate lowercase. The only > solution is to lock edit profiles because lowercase will find its way into > most datasets. Look no farther than PARMLIB(BPXPRM) where mount points are > lowercase. I suspect most parmlib members can't tolerate lowercase. > > Peter Relson's advocating for lowercase surprised me. Working on existing > products, we have standards that must be followed. You're not allowed to > lowercase all comments because that introduces unacceptable risk and you > lose the line change identifier (PTF) by ptf identifier. I've never seen > lowercase comments because of most people don't want to see a hodgepodge of > uppercase / lowercase comments. > > I would also remind people that WTO does not change the message text in > any way. Automation will not be happy with lowercase when your uppercase is > expected. As a useful FYI, WTO happily writes x'00' - x'ff' to the syslog. > Turn hex on while viewing ulog or syslog to see hex dump of a small part of > storage without using snap, trace, logging to a dataset or ???. > > How many failed attempts does this make by Metz demanding that I'm wrong. > Please Metz, stop wasting my time! > > >
