|
I'm not sure where that's contrary... Mike said he recreated the service program which I don't think is not the same thing as recompiling a module that exists in a service program... Joel R. Cochran Director of Internet Services VamaNet.com (800)480-8810 mailto:webmaster@vamanet.com > -----Original Message----- > From: Bartell, Aaron L. (TC) [mailto:ALBartell@taylorcorp.com] > Sent: Friday, May 03, 2002 11:19 AM > To: 'rpg400-l@midrange.com' > Subject: RE: Grrr... signature violation > > > Contrary to Joel I have recompiled existing modules into > service programs > where I only changed the inner code and it worked fine. > > Aaron Bartell > > > > -----Original Message----- > From: Joel R. Cochran [mailto:jrc@masi-brac.com] > Sent: Friday, May 03, 2002 10:17 AM > To: 'rpg400-l@midrange.com' > Subject: RE: Grrr... signature violation > > > You recreated the SRVPGM... to attain the behavior you are > looking for you > need to UPDATE the SRVPGM instead. By Recreating the SRVPGM, > the SRVPGM's > signature that the program referenced when it was created no > longer exists. > When you update, however, the UPD command rewrites the > signatures (as I > understand it...) > > Joel R. Cochran > Director of Internet Services > VamaNet.com > (800)480-8810 > mailto:webmaster@vamanet.com > > > > -----Original Message----- > > From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com] > > Sent: Friday, May 03, 2002 11:10 AM > > To: 'rpg400-l@midrange.com' > > Subject: Grrr... signature violation > > > > > > Help! I have it fixed but know I want to know why and how to > > prevent it. I > > just added a couple lines to my subproceedure, that is it. > > Then after I > > recompiled the module and recreated the service program, I > > got a signature > > violation. After recompiled the calling program it works > > fine. Do I not > > understand how this all works correctly? I thought, as long > as I don't > > change the parameters, I don't have to recompile all of my > > programs. Is this > > a wrong assumption? > > > > A very confused Mike > > _______________________________________________ > > 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. > _______________________________________________ > 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.