Re: REXX access to SETPARM variables

[Martin Truebner]

Frank,

I would first search all levels by what you already have and then
issue a GETSYMB. That way you get the first instance of a local
variable or PWR- or system-level.

Martin Trübner; everything around "PoOps of z/arch"

_______________________________________________
VSE-L mailing list
VS...@lists.lehigh.edu
https://lists.lehigh.edu/mailman/listinfo/vse-l

[Frank M. Ramaekers]

Yeah, that's basically what I ended up doing (except I only check LEVEL0).
How to you traverse the levels? (I only know how to get to LEVEL0.

Frank M. Ramaekers Jr.

[Martin Truebner]

Frank,

>> How to you traverse the levels?

They do have a level-indicator somewhere in the header. But (to be
honest) I never felt the need to go beyond level 0 (or current via
GETSMB) - just like you.

Martin

[Frank M. Ramaekers]

Also, I wonder under what circumstances a new level is created? REXX
seems to create a new level (since any SETPARMs are not brought down
unless exposed via // EXEC statement).

Frank M. Ramaekers Jr.


-----Original Message-----
From: VSE-L
[mailto:vse-l-bounces+framaekers=ailif...@lists.lehigh.edu] On Behalf
Of Martin Truebner
Sent: Monday, August 08, 2016 6:48 AM
To: vs...@lists.lehigh.edu
Subject: Re: REXX access to SETPARM variables

[Martin Truebner]

Frank,

>> I wonder under what circumstances a new level is created?

The book is pretty obvious about it- each EXEC PROC and a EXEC REXX= is
handled same as a PROC.

now- if you ask me about the inner ongoings of REXX (lets call for
Ursula Braun-Krahl ), I have no clue- but i would bet that REXX just
follows its own rules of exposing variables (and not those of VSEs
PROC-handling)