Even if you accept "the sky's the limit" for undefined behavior, there's still
the undocumented issue of whether it is permissible to include a leading
ampersand or a trailing period with the symbol, which is permissible in the
SYMDEF statement. Also, I'd like to see whether the following behaves as
documented:
foo = SYSNAME
say MVSVAR('SYMDEF','foo')
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Dale R. Smith [[email protected]]
Sent: Friday, March 27, 2020 1:16 PM
To: [email protected]
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020 16:28:30 +0000, Seymour J Metz <[email protected]> wrote:
>> Read the much improved doc in the z/OS V2.4 TSO/E REXX Reference for
>> MVSVAR(SYMDEF,xxx).
>
>That's what I was quoting.
>
>> I think everything will be clearer.
>
>Clear, but it matches neither my expectations nor the output that Bruce Hewson
>described.
>
>
>--
>Shmuel (Seymour J.) Metz
>http://mason.gmu.edu/~smetz3
That's because he was using it incorrectly. A single word for each System
Symbol name, not a string with multiple words in it.
SYMDEF,symbolic-name
returns the value associated with the symbolic-name defined in an IEASYSxx
member of
SYS1.PARMLIB on a SYSDEF ... SYMDEF statement.
Or, symbolic-name can also be one of the system static or dynamic symbols as
defined in z/OS MVS
Initialization and Tuning Reference.
...
Any other values including REXX delimiters might cause unpredictable results.
Seems pretty clear to me. GIGO
--
Dale R. Smith
Factotum
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
