How about a language sensitive command that capitalizes what needs to be upper case while leaving comments and constants alone?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Schmitt, Michael <[email protected]> Sent: Wednesday, December 4, 2024 11:59 PM To: [email protected] Subject: Re: ISPF Edit - how to switch off CAPS ON? External Message: Use Caution I’ve had users complain that my application generated JCL with some lower case comments, because it turned CAPS OFF when they edited the JCL, and then they got JCL errors because they were entering key words in lower case. From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Reply-To: IBM Mainframe Discussion List <[email protected]> Date: Wednesday, December 4, 2024 at 7:23 PM To: "[email protected]" <[email protected]> Subject: Re: ISPF Edit - how to switch off CAPS ON? On Wed, 4 Dec 2024 21:19:12 +0100, Radoslaw Skorupka wrote: ...: I want to have CAPS OFF in my ISPF Edit profile. Unfortunately whenever I edit/view any member with no lowercase characters the profile is automatically changed to CAPS ON. I understand such behaviour may be useful, however I need to have CAPS OFF despite of characters in currently edited member. . <https://www.ibm.com/docs/en/zos/3.1.0?topic=environment-initial-macros><https://www.ibm.com/docs/en/zos/3.1.0?topic=environment-initial-macros> For example, if you want caps mode on even if the data contains lowercase data, create an initial macro with a CAPS ON command. The editor first reads the edit profile and the data, then it sets caps mode to correspond to the data. Next, it runs your initial macro, which overrides the edit profile setting of caps mode. But would you need to specify such an initial macro in multiple profiles? Is there no provision for a default or "otherwise" profile in which you could code a SELECT instruction to cover multiple data set types? I'm a strong advocate of minimal munging -- Leave my data alone! The default should always be ASIS. In the past I've used Teletype-oriented editors which reversed the 3270-culture conventions: "lower" meant convert all input to lower case, and"caps" meant "asis". -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
