Can I use a variable within the Path?

What I typically do is use the @ctr, but before using it in a path, copy it to an unused list variable

copy

@ctr          $%l1

Then you can use %l1 in your path with the value your were storing in @ctr.

Ryan

Greetings Cloverleafers!!!

V5.2 on AIX

Can I use a variable within the Path? As far as I know, %g1 is also a variable, but when I tried %ctr, @ctr, @%ctr or %@ctr, none of them works….

Did you initialize @ctr prior to referring to it?

Jim Kosloskey

The %g1 %s1, etc are not variables in the true sense.  That is why you can’t make substitutions as you want.

With that said, I do things llike you are trying to do all the time.  That is one of the main purposes of the CALL statement.  It allows for that kind of control.  Just use a CALL and do the xpmstore command within it.

The *ONlY* difference bewteen a COPY and a CALL is that with a COPY, there is *ALWAYS* something stored to xlateOutVals.  With a CALL, *NOTHING* is stored unless you explicitly store it.

That’s not how you would use it.  Get the variable you want to use to increment the address and use it as part of the address in the xmpstore.  The variable could be @cnt that you passed in.

Assume you are passing a value in and a cnt in @ cnt in that order.  The ob address is the base address to store the data plus @cnt for update.

# Get the value and the cout

lassign $xlateInVals val cnt

# Get the two OB addresses

lassign $xlateOutList valAddr cntAddr

# Assume you know address is something like :

# 0(0).PID(0).00133 and you want it to be

# 0(0).PID(CTR).00133

regsub — {PID(0)} $valAddr “PID($cnt)” valAddr

# Increment the counter

incr cnt

# store the count

xpmstore $xlateId $cntAddr c $cnt

# Store the value

xmpstore $xalteId $valAddr c $val

This is off the top of my head.  I think its right but I may have fat-fingered something.