|
I hate to beat a dead horse Mike, but did you in fact CRTSRVPGM after you changed the module? If so, you could have re-ordered the modules which would create a different signature and lead to a signature violation. With Binder Source and UPDSRVPGM you would be able to avoid this in the future. 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 3:49 PM > To: 'rpg400-l@midrange.com' > Subject: RE: Grrr... signature violation > > > So basically somehow in my editing, I changed the signature > in the program > even though I didn't touch the parameters. Hmm... so much to learn.... > > Perhaps I will put in a request to get that RPG Redbook after all. > > -----Original Message----- > From: Scott Mildenberger [mailto:Smildenber@Washcorp.com] > Sent: Friday, May 03, 2002 2:21 PM > To: 'rpg400-l@midrange.com' > Subject: RE: Grrr... signature violation > > > You can add a parameter to a procedure and it does not change > the signature > of the service program. You will not need to set up a new > version in the > binder source. Programs will not get a signature violation, > they will get > an error if the parameter is not set up to be optional. Any > programs that > need to use the new parameter will have to be recompiled > (edited for that > matter to add the parm). > > Scott Mildenberger > > > -----Original Message----- > > From: Bartell, Aaron L. (TC) [mailto:ALBartell@taylorcorp.com] > > Sent: Friday, May 03, 2002 1:06 PM > > To: 'rpg400-l@midrange.com' > > Subject: RE: Grrr... signature violation > > > > > > <snip> > > No. Changing the parameters will not change the signature, > unless you > > also change the name of the procedure, or change the order, etc. > > </snip> > > > > That's what I said in more words or less. If you change the > > parameters, so > > let's say I added one onto the end of a sub procedure, you > > indirectly change > > the signature because you will now have to create a new > version in the > > binder language or recompile all of the programs that were > previously > > compiled to the old parameter list to now look at the new > > parm list. Or am > > I still off. I can't see a difference in what I said > > compared to what you > > said, Scott. > > > > Aaron Bartell > > > _______________________________________________ > 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.