> Semicolon is not a command separator in TSO; That depends on whether you consider CLIST to be TSO.
At the READY prompt, ; ends the line - except when it doesn't. > there is no facility to put more than one command on a line. Are you a betting man? > Semicolon does end the command, Except when it doesn't. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tony Harminc [t...@harminc.net] Sent: Friday, May 15, 2020 3:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: USS: su: User ID "SH" does not exist On Fri, 15 May 2020 at 12:38, Seymour J Metz <sme...@gmu.edu> 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. Semicolon is not a command separator in TSO; there is no facility to put more than one command on a line. Semicolon does end the command, and behaves a lot like a trailing /* does. READY listd test.asm ; any old junk C702TOH.TEST.ASM --RECFM-LRECL-BLKSIZE-DSORG FB 80 3120 PO --VOLUMES-- A3USR3 READY send 'Hello' user(*) ; some stuff Hello C702TOH READY send 'Hello' user(*) some stuff IKJ56712I INVALID KEYWORD, SOME IKJ56703A REENTER THIS OPERAND - (I hit enter here) IKJ56712I INVALID KEYWORD, STUFF IKJ56703A REENTER THIS OPERAND - (I hit enter here) Hello C702TOH READY Of course ISPF has very different behaviours, and it doesn't help that so many people think that ISPF *is* TSO. Tony H. ---------------------------------------------------------------------- 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
