Re: FW: Your comment on ISPF publication

2020-06-03 Thread Binyamin Dissen
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

2020-06-02 Thread Seymour J Metz
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

2020-06-02 Thread Steve Smith
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