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


  • Subject: Re: Passing variables from program to program.
  • From: watern@xxxxxxxxxxxxxx
  • Date: Wed, 1 Dec 1999 03:56:55 -0500



>i have about 10 variables that are being used in about 3 CL and 1 RPG
program.   what is the best way or the "standard >method"  by parming them
or using a data area?

Not much in it for me. The advantage of using parameters is that it is more
obvious what is going on. The  CL programs would be (marginally) less
complicated as you would not need to map the data area to the 10 variables
with chgvar. The only disadvantage I can see is a longer parameter list for
the pgms, which may also have a slight performance overhead on the calls,
(I imagine it wouldnt be noticeable.) (but then you wouldnt be doing 10
chgvars either).

If they were all rpg pgms, then I would consider using an externally
defined data structure and passing the data structure as one parm block.

I would go for the parm list option myself.

Nigel.


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.