While there is automatic upper casing for TSO command and subcommand names, there are still plenty of cases ;-) where case matters. Consider generating SYSIN for an IBM service aid or utility. Or generating edit subcommands with case-sensitive operands.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Jon Perryman <jperr...@pacbell.net> Sent: Monday, April 22, 2024 5:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: REXX vs other languages WAS: Rexx numeric digits and scientific notation question On Mon, 22 Apr 2024 14:01:23 +0000, Seymour J Metz <sme...@gmu.edu> wrote: >delete foo >rather than >'DELETE' foo >is a simple example. In practise I often need multiple upper case constants in >a single expression. This isn't a valid example because 'delete' will also work. As Andrew said, rarely will you find a real need for REXX to uppercase an undefined REXX variable name. All parsers handle uppercase as needed. In this case, you're ignoring the TSO parser. Consider "alloc dsn('my.dataset') path('/my/unix/file')" where everything is specified in lowercase. Lowercase TSO commands, command option names, DSN and more are not valid. In this example, everthing except '/my/unix/file' will be automatically uppercased instead of failing the command because of lowercase. Truthfully, REXX uppercasing rarely provides real advantages for most z/OS environments and is a problem for z/OS Unix where lowercase is the norm. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
