ISPF edit session line commands to convert the line or block of lines to uppercase.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Thursday, April 9, 2020 11:01 AM To: [email protected] Subject: [External] Re: JCL & UNIX coding. On Thu, 9 Apr 2020 08:33:50 -0700, Charles Mills wrote: >I agree totally but FWIW I find that the line commands UC and UCC/UCC go a >long way toward making the process tolerable. > Context? ISPF Primary panel? TSO READY prompt? JCL? OMVS? Other (specify)? (No habla UCC.) I remember terminals with not CAPS LOCK but SHIFT LOCK, sometimes a mechanical latch on the SHIFT key. >-----Original Message----- >From: John McKown >Sent: Thursday, April 9, 2020 5:02 AM > >I like to use UNIX facilities. Especially some scripting languages, >such as awk. I use Co:Z instead of BPXBATCH. Anyway, sine UNIX is case >sensitive, my "embedded" scripts must be in lower case. I don't want to >keep my scripts in another file. So my JCL member has embedded lower >case. Which makes editing the actual JCL a mess if I forget to use CAPS >LOCK while editing the JCL portion. > >So, I kind of wish that the JCL converter or interpreter would accept >JCL in lower case. In particular, upper casing the JCL statements which >are not inclosed in ticks. It would just make my life easier. I.E JCL >should ignore case when not in ticks. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
