|
I was going to suggest the STATIC keyword as well, however based on the rest of Slava's message I'm guessing he took this model: PGM A CALL's PGM B And turned it into this model in RPG IV: PGM A CALLB MODULE B And what may be happening is that the ILE program is running in a *NEW activation group. Therefore, STATIC won't help. The activation group would need to be changed to a named activation group in order for it to stick around. If, however, Slava actually converted "PGM B" to a Procedure, using P specs, then indeed the STATIC keyword on all the D specification fields would keep them around. However, the Calc-spec defined fields would still by automatic. Bob Cozzi cozzi@rpgiv.com Visit the new on-line iSeries Forums at: http://www.rpgiv.com/forum > -----Original Message----- > From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com] On > Behalf Of Andy Leisk > Sent: Wednesday, September 26, 2001 9:53 AM > To: 'rpg400-l@midrange.com' > Subject: RE: ILE procedure initialization question. > > Use the "STATIC" keyword on any variables local to the procedure that you do > not want re-initialized > > Andy Leisk > Senior Programmer Analyst > Banta Global Turnkey Group > Menasha WI USA > Phone: 920-751-4434 > > > > > -----Original Message----- > From: Slava Zharichenko [mailto:Slava.Zharichenko@exel.com] > Sent: Wednesday, September 26, 2001 9:46 AM > To: rpg400-l@midrange.com > Subject: ILE procedure initialization question. > > > > Hi, > is it a way to make procedure to NOt reinitialize the variables? > > i converted rpgiii program to ILE module. Program was called with Call > command before and it did not turn *on LR so all the variables were not > initialized next time this program being call. Once the program was > converted to ILE it reinitializing all the variables every time it being > called. ILE program used as a procedure. > > > > > > > ______________________________________________________________________ > Important Email Information > > The information in this email is confidential and may be legally > privileged. It is intended solely for the addressee. Access to this email > by anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be > taken in reliance on it, is prohibited and may be unlawful. If you are not > the intended addressee please contact the sender and dispose of this > e-mail. > > _______________________________________________ > 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. > > > > _______________________________________________ > 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-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.