Re: FW: Your comment on ISPF publication
It would appear that IKJSCAN considers leading commas to be similar to leading blanks in ignoring them when calculating the parameter offset. TSO/E Programming Services states: The Command Scan Service Routine examines the command buffer and performs the following functions: It translates all lowercase characters in the subcommand name to uppercase. If a valid operand is present, it resets the offset to the number of text bytes preceding the first non-blank character in the operand field. If a valid operand is not present, the offset equals the length of the text portion of the buffer. It returns a pointer to the subcommand name, the length of the subcommand name, and a code explaining the results of its scan to the calling routine. It optionally checks the syntax of the subcommand name. It recognizes an implicit EXEC command that has a percent sign as the first character. It handles leading blanks and embedded comments. It appears that the second clause is not precise. Probably will be closed by IBM with a DOC APAR. On Tue, 2 Jun 2020 23:44:50 -0400 Steve Smith wrote: :>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 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 -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FW: Your comment on ISPF publication
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 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
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 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
FW: Your comment on ISPF publication
Does anybody know of other characters that are problematical in the TSO command? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: Yi Chen Zhang [zhang...@cn.ibm.com] on behalf of COMSVRCF EMAIL [comsv...@us.ibm.com] Sent: Tuesday, June 2, 2020 11:22 PM To: Seymour J Metz Cc: Bud Deitrich; Alan Packett; Marvin Knight Subject: Your comment on ISPF publication Hi Shmuel, This is Erin from z/OS ISPF team. Thanks for your comments and suggestions! My colleague Bud, on copy, from development team, is investigating the issue. We'd like to understand more about the issue to ensure we cover it properly. Are there other special characters which have an issue? Is this only seen with parameter lists? You mentioned the concern is general. So we are wondering if you are aware of other specific cases? It would be very helpful if you could provide a couple of specific examples. Thanks again for writing to us! -- From: Seymour J Metz mailto:sme...@gmu.edu>> To: "RCF mailto:mhvr...@us.ibm.com>>" mailto:mhvr...@us.ibm.com>> Date: 05/11/2020 06:34 PM Subject: [EXTERNAL] RCF ISPF User'sGuide z/OS Version 2 Release 4 ISPF User's Guide Volume I, SC19-3627-40, and z/OS Version 2 Release 4 ISPF User's Guide Volume II, SC19-3628-40, do not specify the syntax of the TSO command. There are commands that will execute correctly from the READY prompt but not as operands of the TSO command, and absent documentation it is impossible to know whether that is working as designed. The specific issue that prompted this RCF is the handling of unmatched apostrophes, but the concern is more general. -- Shmuel (Seymour J.) Metz -- Erin Zhang for ISPF Customer Information IBM China Development Laboratory in Shanghai -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
