Re: My CL variable is getting whacked!!

["Patrick Townsend" <patownsend@xxxxxxxxxxxxxx>]

Richard,

Check that the variables that are passed as parameters are defined with the
same lengths in all of the programs. CL program variables will get whacked
if they are not the same in all called programs.

Patrick

----- Original Message -----
From: "Richard B Baird" <rbaird@esourceconsulting.com>
To: <midrange-l@midrange.com>
Sent: Thursday, February 21, 2002 12:32 PM
Subject: 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
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>