|
I've read the IBM stuff, but it's still confusing... I've been using RPG/IV without its ILE components (binding, procedures, modules, etc.) because of RPG/III compatibility requirements (vendor software). I'm at the point now where I have a lot of shared code between my programs. >From what I read, I can create procedures with prototypes, and bundle all these together in a service program, and reference the service program from RPG. So, could someone please verify the way I think this works. 1. I write subprocedures and compile with PDM option 15 (CRTRPGMOD). I then have lots of module objects on the system. Do I keep these after creating a service program? 2. (I don't know the specifics) create a service program from all the modules (CRTSRVPGM?) 3. Insert /COPY members into my code for the procedure calling interface (P specs) Is there an advantage of having one large service program versus service programs segmented by function? What steps are necessary when a service program module needs updating? How does this change how I create my RPG/IV programs? For compatibility, I have compiled using option 14 (CRTBNDRPG). Do I have to abandon this setup and create program modules instead? How do I interact with the service program? Do I need to worry about activation groups when I use the service program? I know I should get a book. Which RPG/IV books have decent information regarding procedures and prototyping, and the other "fun" ILE stuff? Thanks, Loyd -- "You can nail me, but not to a tree." lgoodbar@watervalley.net ICQ#504581 http://www.watervalley.net/users/lgoodbar/ +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.