Birgitta,
I'd be very worried about converting everything at once.
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?
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Birgitta Hauser
Envoyé : vendredi 23 janvier 2009 19:06
À : 'Midrange Systems Technical Discussion'
Objet : AW: Binding Directory question
May be not over night but in a week end, assumed there are no duplicate exported procedure names:
1. create a binder source for each module, where the exported procedures are listed. (This can be done without changing anything) 2. create a service program for each module that is not directly called, i.e. bound to one or several programs (Service program name = module name)
As long as only the modules are bound to the programs there will be no problem.
3. Create a new binding directory where all your service programs are listed 4. Recreate your programs (all those modules that are directly called) by using this binding directory.
CRTBNDRPG with specifying the new binder directory will be enough.
5. Delete all your modules
It will work as long as you have no duplicated exported procedure names.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von David FOXWELL
Gesendet: Friday, 23. January 2009 15:55
An: Midrange Systems Technical Discussion
Betreff: RE: Binding directory question
Jon, I have understood the problem for quite a while now, thanks to this list.
But when you have already 2500 modules that are shared in this way, ie copied many times in many programs, how many exactly I don't know, you can't just change to service programs overnight. It's like a big ocean-going liner. 5 mile turning circle and all that.
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Jon Paris Envoyé : vendredi 23 janvier 2009 14:48 À : midrange-l@xxxxxxxxxxxx Objet : Re: Binding directory question
On 23-Jan-09, at 6:54 AM, midrange-l-request@xxxxxxxxxxxx wrote:
All our modules are bound by copy.
When a module is modified, all programs using that module are rebound
automatically by our installation tool.
This is causing more and more headaches, ...
Without wanting to sound rude - this question is really in the category of "Doctor, doctor - it hurts when I bang my head on the wall".
Binding by copy is primarily intended to provide the best call performance in a "one caller to one callee" situation. Bind by reference (Service
programs) is intended for the "Many callers one callee" situation - i.e.
code reuse of the kind you describe.
So the basic solution is the same as that to the doctor question "Stop doing it" and start using service programs.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
