On 21/04/2010, at 7:47 AM, James Perkins wrote:
I did recently read a presentation of yours about service programs. It
seems adding the new procedures after any current ones seems to be
what I would need to do.
A service program discussion really belongs in MIDRANGE-L or perhaps  
RPG400-L but ...
You can stick new procedures anywhere in the service program source.  
What you cannot do is insert public exports anywhere you like in the  
binding source. In the binding source, all new exports must go after  
any existing exports.
There are other 'tricky' things you can do with binding source to  
rename existing procedures yet not have to recompile consumers and  
similar things but those techniques have been discussed previously so  
search the archives if you're interested.
Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists
   
http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------
 
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.