emy Nicoll [jn.ls.mfrm...@letterboxes.org]
Sent: Sunday, March 29, 2020 6:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Sun, 29 Mar 2020, at 00:08, Seymour J Metz wrote:
> SYMSUB is a REXX routine that he wrote to pass the argument to
> MVSVAR('SYMD
On Sun, 29 Mar 2020, at 00:08, Seymour J Metz wrote:
> SYMSUB is a REXX routine that he wrote to pass the argument to
> MVSVAR('SYMDEF',*) and display or return the result.
Yes of course, I understand that. What I don't understand is where
the ampersand and dot are coming from in the displayed
, March 28, 2020 10:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
Hello Jeremy,
I have been coding the single quote around 'MVSVAR' and other TSO External
Functions seemingly forever.
I assume that I have to do that as I run with SIGNAL NOVALUE enabled.
On Thu, 26 Mar
Hello Jeremy,
I have been coding the single quote around 'MVSVAR' and other TSO External
Functions seemingly forever.
I assume that I have to do that as I run with SIGNAL NOVALUE enabled.
On Thu, 26 Mar 2020 19:09:40 +, Jeremy Nicoll
wrote:
>
>Apart from the documented behaviour of
of
Jeremy Nicoll [jn.ls.mfrm...@letterboxes.org]
Sent: Saturday, March 28, 2020 1:46 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Sat, 28 Mar 2020, at 04:28, Bruce Hewson wrote:
> Hi,
>
> examples using the code I posted.
>
> %SYMSUB 'testing in '
&
On Sat, 28 Mar 2020, at 04:28, Bruce Hewson wrote:
> Hi,
>
> examples using the code I posted.
>
> %SYMSUB 'testing in '
> &'TESTING TSYS IN PLEX40'.
> READY
> %SYMSUB 'Foo'
>
Hi,
examples using the code I posted.
%SYMSUB 'testing in '
&'TESTING TSYS IN PLEX40'.
READY
%SYMSUB 'Foo'
READY
Hello,
here is the code:-
/*REXX/
Trace 'o'
Parse Source opsys calltype execname .
: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Jeremy Nicoll [jn.ls.mfrm...@letterboxes.org]
Sent: Friday, March 27, 2020 5:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020, at 21:17, Seymour J Metz wrote:
> Well, you could
On Fri, 27 Mar 2020, at 21:17, Seymour J Metz wrote:
> Well, you could do
>
>symvalue = 'MVSVAR'('SYMDEF','SYMNAME')
>
> I doubt that it will pass code review.
What do you mean by "code review"? Informal checks by
colleagues, or something else?
The point though is that in the OP's
[jn.ls.mfrm...@letterboxes.org]
Sent: Friday, March 27, 2020 5:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020, at 20:07, Seymour J Metz wrote:
> MVSVAR is not an external functions
If someone was foolish enough to write their own one, perhaps
hav
@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Friday, March 27, 2020 4:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020 20:07:06 +, Seymour J Metz wrote:
>MVSVAR is not an external functi
On Fri, 27 Mar 2020, at 20:07, Seymour J Metz wrote:
> MVSVAR is not an external functions
If someone was foolish enough to write their own one, perhaps
having it call the built-in MVSVAR() wouldn't it be possible for
an exec to call the local one in preference to the built-in one?
--
Jeremy
On Fri, 27 Mar 2020 20:07:06 +, Seymour J Metz wrote:
>MVSVAR is not an external functions.
>
It's documented as among TSO/E external functions in
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ikja300/tsofunc.htm
Is a clarification RCF needed?
>Further,
Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Friday, March 27, 2020 1:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020 12:16:50 -0500, Dale R. Smith wrote:
>On Fri,
] on behalf of
Dale R. Smith [dale-sm...@columbus.rr.com]
Sent: Friday, March 27, 2020 3:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020 18:48:58 +, Seymour J Metz wrote:
>That's the right answer to the wrong question. You removed the apostrop
-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
foo = SYSNAME
. REXXTRY on TSO
say 'Foo:' MVSVAR('SYMDEF','foo')
Foo:
. REXXTRY on TSO
On Fri, 27 Mar 2020 17:42:30 +
On Fri, 27 Mar 2020 18:48:58 +, Seymour J Metz wrote:
>That's the right answer to the wrong question. You removed the apostrophes
>around foo, so the results are irrelevant. Try my code as written and I
>suspect that you will get results that differ from what's in the manual.
>
>
>--
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Dale R. Smith [dale-sm...@columbus.rr.com]
Sent: Friday, March 27, 2020 2:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020 17:42:30 +, Seymour J
On Fri, 27 Mar 2020 12:59:44 -0500, Paul Gilmartin wrote:
>But I wonder if a 23:59:59 error is possible if the date changes between
>iterations of the loop?
>
>I raised this question a while ago concerning use of symbols in JCL.
>Peter Relson replied, simply, "Yes". No circumvention suggested.
foo = SYSNAME
. REXXTRY on TSO
say 'Foo:' MVSVAR('SYMDEF','foo')
Foo:
On Fri, 27 Mar 2020 17:42:30 +, Seymour J Metz wrote:
>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
On Fri, 27 Mar 2020 12:16:50 -0500, Dale R. Smith wrote:
>On Fri, 27 Mar 2020 16:28:30 +, Seymour J Metz 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.
>>
.com]
Sent: Friday, March 27, 2020 1:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Fri, 27 Mar 2020 16:28:30 +, Seymour J Metz wrote:
>> Read the much improved doc in the z/OS V2.4 TSO/E REXX Reference for
>> MVSVAR(SYMDEF,xxx).
>
>That's what
On Fri, 27 Mar 2020 16:28:30 +, Seymour J Metz 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
Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Dale R. Smith [dale-sm...@columbus.rr.com]
Sent: Friday, March 27, 2020 12:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavo
Read the much improved doc in the z/OS V2.4 TSO/E REXX Reference for
MVSVAR(SYMDEF,xxx). I think everything will be clearer.
I wrote a REXX Program a few years ago to extract and display the various
Static and Dynamic System Symbols that are defined in z/OS. I also included
our inhouse
mented that MVSVAR treats
ampersand as anything but just another character?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Bruce Hewson [bruce_hew...@hotmail.com]
S
On Fri, 27 Mar 2020, at 04:25, Bruce Hewson wrote:
> Guys,
>
> the code receives ...
> The MVSVAR external function provides for this case, so it will
> substitute for any symbols in the text string, thus building a new
> SYMBOL name, repeating until all symbols are resolved, if possible.
Are
Guys,
the code receives a text string which may contain one or more symbols, denoted
by prefix "&" and optional suffix ".", as per my reading of how Z/OS handles
symbol substitution.
Say we have these symbols defined in IEASYM00:-
= '01'
= 'TEST
= 'FOOBAR'
text string contains ""
After
26, 2020 5:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Wed, 25 Mar 2020 13:28:12 +, Seymour J Metz wrote:
>"The MVSVAR('SYMDEF',string) function goes through REXX substitution for
>string first, the result of which must be a 1-8 character sy
On Wed, 25 Mar 2020 04:43:52 -0500, Bruce Hewson wrote:
>
>Say 'MVSVAR'("SYMDEF",'testing in ')
>
>which provides an unexpected result
>
>&'TESTING SYSA IN PLEX01'.
>
>The symbols and were replaced.
>And, sadly, the whole lot was uppercased.
>
>Couldn't find this behaviour documented.
>
I
On Thu, 26 Mar 2020, at 19:18, Paul Gilmartin wrote:
> On Thu, 26 Mar 2020 19:09:40 +, Jeremy Nicoll wrote:
>
> >On Thu, 26 Mar 2020, at 04:23, Bruce Hewson wrote:
> >
> >> So far I have not seen anyone identify where this is fully documented.
> >
> >Apart from the documented behaviour of
On Wed, 25 Mar 2020 13:28:12 +, Seymour J Metz wrote:
>"The MVSVAR('SYMDEF',string) function goes through REXX substitution for
>string first, the result of which must be a 1-8 character symbolic-name
>specifying the symbol that has been defined in the SYMDEF statement. Any other
>values
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, March 26, 2020 9:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Wed, 25 Mar 2020 04:43:52 -0500, Bruce Hewson
On Thu, 26 Mar 2020 19:09:40 +, Jeremy Nicoll wrote:
>On Thu, 26 Mar 2020, at 04:23, Bruce Hewson wrote:
>
>> So far I have not seen anyone identify where this is fully documented.
>
>Apart from the documented behaviour of MVSVAR (which I found with Google)
>
Cite?
>there's maybe the point
On Thu, 26 Mar 2020, at 04:23, Bruce Hewson wrote:
> So far I have not seen anyone identify where this is fully documented.
Apart from the documented behaviour of MVSVAR (which I found with Google)
there's maybe the point that in your code you've got single quotes around
"mvsvar". That, IIRC,
On Wed, 25 Mar 2020 04:43:52 -0500, Bruce Hewson wrote:
>
>In a REXX exec I was building I stumbled onto:-
>
>Say 'MVSVAR'("SYMDEF",'testing in ')
>
>which provides an unexpected result
>
>&'TESTING SYSA IN PLEX01'.
>
>The symbols and were replaced.
>And, sadly, the whole lot was
Hi,
I am writing a general subroutine that would replace system symbols in any text
string.
I had a fairly complicated piece of code to do the correct symbol replacement,
including possible symbol concatenation, obeying all the replacement rules I
could remember. My code still had somewhere to
ERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, March 25, 2020 12:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Wed, 25 Mar 2020 16:13:22 +, Seymour J Metz wrote:
>If MFC doesn't know then it's probab
On Wed, 25 Mar 2020 16:13:22 +, Seymour J Metz wrote:
>If MFC doesn't know then it's probably impossible to find out why.
>
>BTW, I submitted and RCF on the conflict between text and example.
>
Thanks. Of course, no such problem exists if LONG_SYMBOL_NAME
has been assigned a value no longer
] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, March 25, 2020 12:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Wed, 25 Mar 2020 15:43:47 +, Seymour J Metz wrote:
>Why? I suspect that only Mike knows.
>
M
On Wed, 25 Mar 2020 15:43:47 +, Seymour J Metz wrote:
>Why? I suspect that only Mike knows.
>
MFC? I suspect it was out of his control before that happened.
>Worse, the same manual has an example where the name is longer than 8
>characters.
>
Oh, don't you make me search for it. ITYM:
On Wed, 25 Mar 2020 11:24:30 -0400, Ken Smith wrote:
>Useful, but this is closer and more clear (don't have a system to test)
>
>sysname = MVSVAR('SYMDEF','SYSNAME')
>sysplex = MVSVAR('SYMDEF','sysplex')
>
>say 'Testing on' system 'in' sysplex
>
If, as described in the Ref.:
The
] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, March 25, 2020 11:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX MVSVAR SYMDEF behavoiur
On Wed, 25 Mar 2020 13:28:12 +, Seymour J Metz wrote:
>"The MVSVAR('SYMDEF',string) function goes
On Wed, 25 Mar 2020 13:28:12 +, Seymour J Metz wrote:
>"The MVSVAR('SYMDEF',string) function goes through REXX substitution for
>string first, the result of which must be a 1-8 character symbolic-name
>specifying the symbol that has been defined in the SYMDEF statement. Any other
>values
Useful, but this is closer and more clear (don't have a system to test)
sysname = MVSVAR('SYMDEF','SYSNAME')
sysplex = MVSVAR('SYMDEF','sysplex')
say 'Testing on' system 'in' sysplex
Ken Smith
Retired Sysprog
On Wed, Mar 25, 2020 at 11:01 AM Gerardo Toro wrote:
> First excuse my English it
First excuse my English it is so bad.
I put these sentences:
I = MVSVAR('SYMDEF','SYSNAME')
j = MVSVAR('SYMDEF','sysplex')
SAY 'Testing MVSVAR(SYMDEF,sysname)' i 'in sysplex ' j
and I obtained this ...
Testing
On Wed, 25 Mar 2020, at 09:43, Bruce Hewson wrote:
> Hi,
>
> In a REXX exec I was building I stumbled onto:-
>
> Say 'MVSVAR'("SYMDEF",'testing in ')
>
> which provides an unexpected result
>
> &'TESTING SYSA IN PLEX01'.
>
> The symbols and were replaced.
> And, sadly, the whole lot
"The MVSVAR('SYMDEF',string) function goes through REXX substitution for string
first, the result of which must be a 1-8 character symbolic-name specifying the
symbol that has been defined in the SYMDEF statement. Any other values
including REXX delimiters might cause unpredictable results."
50 matches
Mail list logo
