Or they have other fish to fry. I doubt that IBM is immune to the COVID-19 chaos.
"Defending BPXBATCH is not in my job description." -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Friday, May 15, 2020 12:47 PM To: [email protected] Subject: Re: USS: su: User ID "SH" does not exist On Fri, 15 May 2020 16:38:04 +0000, Seymour J Metz wrote: >I thought that you could turn off TSO recognition of semicolon with PROFILE or >TERMINAL but, no, you can't. I'm not sure what happens if CLIST or REXX code >passes a semicolon. OTOH, TSO will accept a semicolon in a quoted string. > I couldn't turn it off for ISPF. I set it to '¾' and hope I never need it. >The TSO command is OMVS and it is documented in z/OS UNIX System Services >Command Reference. > "TSO SH" causes TSO TMP to execute an "SH" command, and I can't find documentation of the latter. IBM representatives have been conspicuously silent on two ongoing related threads. Perhaps they recognize BPXBATCH is indefensible. >________________________________________ >From: Paul Gilmartin >Sent: Friday, May 15, 2020 12:22 PM (in whatever timezone) > >On Fri, 15 May 2020 14:02:25 +0000, Seymour J Metz wrote: > >>Semicolon is a separator for TSO SH as well, but you have to keep TSO from >>recognizing it. -- gil ---------------------------------------------------------------------- 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
