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



Jon Paris wrote:
On 26-Jan-09, at 8:55 AM, midrange-l-request@xxxxxxxxxxxx wrote:

After having changed from 1 big bound pgm to one smaller pgm bound to several srvpgm, won't there be differences in behaviour?
What about things like Static variables, files staying open, etc?

Nope - why would there be?


That's true if there's only 1 big bound program, but if there's several big bound programs changed into several small programs calling several service programs, there might be differences.

If the same module is currently bound to several programs, and the module opens a file, then there might be a behaviour difference if all those bound modules were changed to be bound to a single service program.

In the bound module case, each module would have a separate independent open of the file. When these bound modules are replaced by a single bound service program, there's only one open per activation group. That can lead to inadvertent file "sharing" between programs. Not necessarily a bad thing, but I think it requires investigation for each module.

This is one of the scenarios where file parameters (new for RPG in V6R1) can be useful. The programs all call the same service programs, but instead of the service program having the F spec for the file, each program has the F spec and passes the file as a parameter to the service program. So the programs are independent the same way they would be if they were using bound modules.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.