My CL variable is getting whacked!!

I've got a wierd thing happening.

in a CLP, I have a CL variable that is defined with a VALUE() parameter.
it is 10 *char.

I step through the program via debug, (strdbg opmsrc(*yes) ) and my
variable has the same value all along.... it continues through various CL
stuff, calls, commands, etc, then it calls one particular program (not the
first program in the stream).

when it returns from this program, my variable gets whacked - the first
charactor is not blank.   The variable was not a parm in this particular
call, I haven't even used it in my CL program yet.

is this the mysterious CL variable address leak?  why would it affect a
variable that wasn't a parm to a call?

any ideas?

ttfn,

rick