I hear you. If it were an app written by some guy down the hall I would totally agree with you. But blanks in START command parameters have to be pretty commonly used, and the syntax has not changed in decades, so I think it must be something more subtle than that, or in addition to that.
Yes, the blank is apparently a factor (as you note). But I think it has to be more than just a simple naïve scan (TRT or otherwise; TRT is just a software loop written in micro- or millicode) for a blank. If it is a bug IBM is not going to fix it in time to get his task started, so a workaround is the key. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, July 7, 2022 7:34 AM To: [email protected] Subject: Re: How do I issue a command with a blank in it? On Thu, 7 Jul 2022 06:58:47 -0700, Charles Mills wrote: > >Maybe too many commas? > ... Too many blanks. The OP reports that the error does not occur if he changes one blank to an underscore. I deem this the malign progeny of TRT. The designer knew (correctly) that every command ends with a blank so reasoned (fallaciously) that any blank ends a command. (Aristotle knew better.) And believed that using a TRT to find the first blank would avoid the expense of a left-to-right lexical parse. It doesn't; it actually adds the cost of the TRT. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
