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
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
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.
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,
