Re: Strange behavior -- RPG400-L

× 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.

Yes, (duh) it was parameter size. the program could return different sized
parms and I just assumed....

thanks for jogging my memory everyone.

On Fri, Jun 27, 2014 at 4:47 PM, rick baird <rick.baird@xxxxxxxxx> wrote:

I have a very simple program I can call from a CLP that just retrieves and
returns a value based on the value passed - use example:

CALL PGM(SU22A1) PARM('FROMVERS3 ' &OLDVERS )
CALL PGM(SU22A1) PARM('OBJLIB ' &NJOBDL )
CALL PGM(SU22A1) PARM('JOBD ' &NJOBD )

I use the different variables in commands thereafter. As I step through
each step in debug, after the first call, the variable &OLDVERS has the
value I expect. After the second call, variable &NJOBDL has the value I
expect, but &OLDVERS is now blank, and after the third call, &NJOBD has the
value I expect, but &NJOBDL is blank too.

what gives? I'm guessing it's an issue with the called program reusing the
same pointer space in memory, but how can I keep this from happening short
of saving off the value before calling the next one?

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.