|
>However, if a >program was already open and calling a procedure at the time a service >program gets replaced with a new version, the calling program >will get a >pointer error when it tries to call the same procedure again. >Once that >calling program is shut down, of course, and is re-invoked, it >then finds >the new version of the service program just fine. Okay, I haven't run in to this. I assumed the *ActGrp would have a copy of the *SRVPGM modules. >Are you saying you delete and re-enter the service program in >your binding >directory each time you modify it? Usually 'No'. If the modification is to an existing *MODULE in the *SRVPGM, then I just run UPDSRVPGM. If I am adding a *MODULE, then yes I would, although in these cases I usually make a new *SRVPGM for the new module and leave the old one as is. I know this can be simplified through Binder Source, but I haven't learned it yet. Joel R. Cochran Director of Internet Services VamaNet.com 800-480-8810 (va toll free) 540-885-8050 (phone) 540-886-1589 (fax) www.vamanet.com mailto:custservice@vamanet.com
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.