Neither the documentation of EXEC nor the documentation of IKJSCAN says anything about that. I suspect that it's something specific to implicit EXEC. Is anybody in a position to make a formal query to IBM?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Steve Smith [sasd...@gmail.com] Sent: Tuesday, June 2, 2020 11:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FW: Your comment on ISPF publication I'm not sure this is relevant, but today I ran into this: EX 'yadda.zadda.exec(blah)' ',,foo' /* works */ but %blah ,,foo /* does not work */ "blah" starts with parse arg a ',' b ',' c The leading commas disappear with the so-called indirect invocation, and so 'foo' is assigned to a, not c. According to the REXX reference, this is what TSO does. For some reason. I'm sure it's a good reason. Possibly a really good and wonderful reason. But it interferes somewhat with maintaining my sanity. sas On Tue, Jun 2, 2020 at 11:28 PM Seymour J Metz <sme...@gmu.edu> wrote: > Does anybody know of other characters that are problematical in the TSO > command? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ---------------------------------------------------------------------- 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
