On Thu, 19 Nov 2020 20:24:25 +0000, Jesse 1 Robinson wrote:
>No argument. Still, it's hard to beat the flexibility of TSO/CLIST parameter
>handling. I wrote a TSO command once partly for kicks. Really complicated.
>Pointers to pointers to pointers. When it was done, it was super easy to use.
>Sigh.
>
I encountered a flexibility limitation long ago. I had a Rexx exec
such that:
o I wanted to execute it from the SYSEXEC/SYSPROC concatenation
rather than specifying a data set name.
o I wanted to pass it an unconventional argument.
"%myrexx argument" failed because IKJPARS reported a syntax
error in "argument"
exec 'gil.my/sysexec(myrexx)' 'argument' worked but required that
users code a data set name.
I earnestly wished for a construct,
exec *(myrexx) 'argument'
by analogy to,
call *(mypgm) 'parm'
which uses the conventional TASKLIB/STEPLIB/LINKLST search order.
Alas, such a form of 'exec' doesn't exist.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
