On 2014-09-08 12:26, Thomas Berg wrote:
>> -----Original Message-----
>> From: Paul Gilmartin
>> Sent: Monday, September 08, 2014 7:26 PM
>
>> CMS EXECIO provides an "EXECIO ... (VAR" as well as stem. I wonder why
>> z/OS lacks the former. CMS also provides "EXECIO ... (STRING", but I
>> suspect z/OS balked at the parsing considerations.
>
> I can't see that to be a problem really (or do miss something?), they could
> just use the standard string routines when "parsing" the input for EXECIO.
>
Remember that a host command argument is always a single string.
I can code:
address CMS 'EXECIO 1 DISKW' FileID '(string ))) ((( ))) '
... in which the string written is " ))) ((( ))) "
I suspect the TMP parser might be uncomfortable with:
address TSO 'EXECIO 1 DISKW' FileID '(string ))) ((( ))) '
> If you restrict the name of the variable to end with a numeric you have (just
> guessing how ..(VAR works in CMS) something alike ..(VAR:
>
> r1 = 'foo'
> 'EXECIO 1 DISKW xxx (STEM R FINIS' [apostrophe added -- gil]
>
I believe you're right. That and:
'EXECIO 1 DISKW xxx (VAR R1 FINIS'
'EXECIO 1 DISKW xxx (FINIS STRING' R1
... the attraction of STRING is that it may introduce an evaluated
expression (which extends to the end of the command), often eliminating
the need for an assignment or stacking:
'EXECIO 1 DISKW xxx (FINIS STRING' 2 + 2
... writes '4' to xxx.
EXECIO is among very few command environments that uses the
Direct rather than Symbolic interface to Rexx variables.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
