I just tested this. Here is what I did: Select a PDS/E member in Edit mode. Enter command PROFILE, which shows current ISPF Edit profile Enter command PROFILE UNLOCK (if the profile shows LOCK ON) Enter command CAPS OFF (or ON). Enter command PROFILE LOCK.
Cancel out of member edit. Logoff and then logon back on. (system will keep profile in memory until logoff. Repeat first two steps to verify correct profile was used. You may get message indicating "profile overridden". This message indicates the current edit profile does not match the system-wide edit profile. (Press PF1 to see message explanation) This will need to be performed for each PDS/E type (last HLQ of dataset name usually determines type) (JCL,COBOL, ASM, etc) Matthew On Thu, 5 Dec 2024 11:41:27 +0100, Radoslaw Skorupka <[email protected]> wrote: >...or simpler: >uuc >uuc > >Line command in block > >However changing all to uppercase is easy. >What is more complex is reverting from CAPS ON. For example I want to >keep my JCL code uppercase, however my unix pathnames need to be asis >(=neither uppercase nor lowercase). > > >BTW: I fully understand people who want automatic CAPS ON. However a >little knob called LOCK CAPS would be a solution for all. I would set >CAPS OFF and LOCK CAPS. Others would choose UNLOCK CAPS. >IMHO it is really small enhancement. Small, but useful. > >-- >Radoslaw Skorupka >Lodz, Poland > > > > >W dniu 05.12.2024 o 06:22, Mike Schwab pisze: >> X ALL;F ALL P'<' (find only lower case) >> C ALL P'<;' P'>'.(change all lower case to UPPER CASE). >> >> On Wed, Dec 4, 2024 at 10:59 PM Schmitt, Michael >> <[email protected]> wrote: >>> 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] with the message: INFO IBM-MAIN
