|
There's nothing wrong with service program running in its own activation group. But from general point of view I would say that it's better, when original program runs in a named activation group and service program runs in activation group *CALLER. In this way if later you will have another application running in another activation group, then both applications may use the same service program and still be isolated from each other. Best regards Alexei Pytel "Mark Walter" <mwalter@netrax.net> on 12/08/99 01:20:01 PM Please respond to RPG400-L@midrange.com To: RPG400-L@midrange.com cc: Subject: RE:Procedure Failing All, Thanks to the list for all of the help. I created the service program to run in the QILE activation group and left the ILE RPG program to which the service program is bound as ACTGRP(*CALLER) and all seems to be working fine. If any of you ILE gurus see a potential problem with this scenerio, please let the list know. I would like any to know any potential pitfalls before I start more ILE development. Thanks again Mark
All,
Thanks to the list for all of the help. I created the service
program to run in the QILE activation group and left the ILE RPG program to
which the service program is bound as ACTGRP(*CALLER) and all seems to be
working fine. If any of you ILE gurus see a potential problem with this
scenerio, please let the list know. I would like any to know any potential
pitfalls before I start more ILE development.
Thanks again
Mark
|
As an Amazon Associate we earn from qualifying purchases.
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.