On Thu, 28 Aug 2025 01:44:32 +0000, Seymour J Metz <sme...@gmu.edu> 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!
