× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Leif and Andy,

I moved the DCL statement to the end (it was somewhere in the middle of my
declares) and it didn't get clobbered.  I'll next check the parm lengths to
be sure they are consistant in all programs.

thanks for the help,

rick

--original messages--
Message: 5
From: "Leif Svalgaard" <leif@leif.org>
To: <midrange-l@midrange.com>
Subject: Re: My CL variable is getting whacked!!
Date: Thu, 21 Feb 2002 14:38:03 -0600
Reply-To: midrange-l@midrange.com

From: Richard B Baird <rbaird@esourceconsulting.com>
> when it returns from this program, my variable gets whacked - the first
> charactoe 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?
>

Possibly the variable just before your variable *is* a parameter to
one of your calls. Try to insert a dummy few hundred bytes just
before your variable and see if they get clobbered.



--__--__--

Message: 6
From: "Andy Nolen-Parkhouse" <aparkhouse@attbi.com>
To: <midrange-l@midrange.com>
Subject: RE: My CL variable is getting whacked!!
Date: Thu, 21 Feb 2002 15:45:17 -0500
Reply-To: midrange-l@midrange.com

Rick,

Can you verify that the passed parameters in the called program are
exactly the same length in both programs?

Regards,
Andy Nolen-Parkhouse




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.