|
Rob, Our approach is to compile programs to run in a named activation group such as QILE and for all service programs to run in *CALLER so they run in the same activation group as the program that is using them. Scott Mildenberger > -----Original Message----- > From: rob@dekko.com [mailto:rob@dekko.com] > Sent: Friday, September 21, 2001 7:20 AM > To: rpg400-l@midrange.com > Subject: H ActGrp('QILE') vs H ActGrp(*caller) > > > > When I first started using a service program I set up some > default H spec's > to be copied in using /copy for the programs using the > service program, and > for RPGLE programs in general. In this copy member I have > the following: > H ActGrp('QILE') > > Some developers have requested that we be able to change this to > H ActGrp(*CALLER) > This will help make > ErrorFlag=system(cmd); > work better. In cases where cmd is an OVRDBF. I know I can > workaround > with OVRSCOPE. > > Any comments on the ramifications of this change? > > The concepts of service programs, subprocedures and the like > are catching > on here and I want to do everything I can to not stand in the way. > > Who would have thought to document their H specs? :-) > > > Rob Berendt > > ================== > A smart person learns from their mistakes, > but a wise person learns from OTHER peoples mistakes. > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) > mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.