VPUT Error
Dunn, Mal
me if I haven't used the correct protocol.
Running a REXX procedure at a site and when it does a VPUT of a
variable to the profile pool it returns a RC=8 (variable not found).
Have tried a simple REXX which does the following
/* REXX */
PARMX = 'HELLO'
ADDRESS ISPEXEC "VPUT (PARMX) PROFILE"
This command at this site will return a RC of 8. When we do the same
thing in a clist it works ok.
When I do the subcom command it says that tso and ispf are available.
All other functions run under ispexec work ok.
The trace shows that the variable is not being updated in the function
pool.
When this is run at other sites it works ok, just a problem at this one
site.
Has any one encountered a problem like this before ?
Mal Dunn
Flexcab Cost Reduction Team
Phone 9865 8358
Mobile 0408 050028
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX
Lindy Mayfield
The syntax is like this:
Parmx = 'Hello'
Address ISPEXEC "VPUT Parmx PROFILE"
cheers,
Lindy
Jeremy C B Nicoll
> Hi.
> The syntax is like this:
> Parmx = 'Hello'
> Address ISPEXEC "VPUT Parmx PROFILE"
That's misleading because neither the random capitalisation you've
applied nor the absence of brackets should make any difference. The
original was just as correct as this is.
--
Jeremy C B Nicoll - my opinions are my own.
Jeremy C B Nicoll
> This is my first entry into the Rexx list server world, so please exuse
> me if I haven't used the correct protocol.
> Running a REXX procedure at a site and when it does a VPUT of a
> variable to the profile pool it returns a RC=8 (variable not found).
> Have tried a simple REXX which does the following
> /* REXX */
> PARMX = 'HELLO'
> ADDRESS ISPEXEC "VPUT (PARMX) PROFILE"
> This command at this site will return a RC of 8. When we do the same
> thing in a clist it works ok.
> When I do the subcom command it says that tso and ispf are available.
> All other functions run under ispexec work ok.
> The trace shows that the variable is not being updated in the function
> pool.
> When this is run at other sites it works ok, just a problem at this one
> site.
Sorry; are you *sure* you've not typed VGET by accident?
--
Jeremy C B Nicoll - my opinions are my own.
----------------------------------------------------------------------
ADRIAN STERN, WM-DATA +
-> TSO-REXX(a)VM.MARIST.EDU
I'd like to see the whole rexx as it does not seem possible to get
an 8 from vput in a rexx exec.
Adrian
Gray, Alastair
VPUT as an option, so one must assume it is possible !)
As an alternative I'd like to see the output from a Trace I placed at the
begining of the little sample that was posted :
/* REXX */
Trace I
PARMX = 'HELLO'
ADDRESS ISPEXEC "VGET (PARMX) PROFILE"
That way we will see the variable resolution, the code and the return code.
Also can the original author confirm that this is being run in foreground
under a normal ISPF session ? (If not, what form does the environment take).
Also that he is not compiling the code.
Alastair Gray
Systems Type
> -----Original Message-----
> From: ADRIAN STERN, WM-DATA + [mailto:DGA.ZA...@MEMO.POSTEN.SE]
> Sent: Monday, August 13, 2001 1:57 PM
>
> --- Inkommet från DGA.ADST001 08-781 2657 01-08-13 13.57
> -> TSO-REXX(a)VM.MARIST.EDU
> I'd like to see the whole rexx as it does not seem possible to get
> an 8 from vput in a rexx exec.
----------------------------------------------------------------------
Dunn, Mal
pool.
Thanks for the responses everybody.
I tested the REXX at the site today by running from option 6/7 with ex
'library(test1)' which still gave the RC = 8 on the VPUT.
When I checked the variable in the variable pool it had the variable name
added to the pool but did not have a value. It had a I for the pool in which
the variable exists, which means it was Function,Implicit.
As a last resort I added the exec library into the Sysproc concatenation and
in option 6 did a %test1, which worked ok (Rc=0 and saved the correct
variable value).
Obviously some mismatch with profile pools but I don't know why. It now
works but I would like to know why?
Any ideas anybody?
Thanks
Mal
ADRIAN STERN, WM-DATA +
-> TSO-REXX(a)VM.MARIST.EDU
This seems quite fantastic! A failed vput to a profile pool cannot
result in a successful anything. If the variable was in the
function implicit pool I think it must have come from a displayed
panel. As far as I'm aware, the 8 return code would only occur in
for example a PL/1 program if you tried to do a vput without
having done a vdefine for the variable. For clist and rexx, by
definition, if the variable does not exist in the pool it will be
created, otherwise updated.
I don't think we've seen the whole picture yet.
Adrian
Jeremy C B Nicoll
[snip]
> It now works but I would like to know why?
By "works" presumably you mean that when you run the rexx exec again the
VPUTs that get done work, presumably overwriting the saved value written
by previous runs of the exec?
If you change the applid the exec is running under, so that a new profile
is created, does that work (I'd expect not).
If you change the variable's name does that work?
What happens if, when as far as you are concerned the variable has not
yet been VPUT, you VGET it (either with specific pool names, or ASIS)?
Is there something already stored in a table somewhere with that name -
perhaps something that's been VDEFINEd in a manner that mismatches with
the rexx exec's implicit definition...
You might be able to see that by running dialog trace with breakpoints on
VDEFINE VCLEAR VGET VPUT and V-anythingelse.
--
Jeremy C B Nicoll - my opinions are my own.
----------------------------------------------------------------------