|
On Fri, 2004-09-10 at 19:44, Joel Schibbelhute wrote: > Howdy Joel, > > This is that other Joel. I've started working on doing > the file encapsulation and so far I like how it's > working, but wow, it's a TON of work doing service > programs for hundreds of files. I can see the benefit > once you get it done, so I think I will continue. HOLD THE PRESSES... Yes it is a ton of work, no doubt about it. If you can wait for another week or so, I'm going to release an "RPGBean Creator" that will take any file and create the source, prototype /copy member, binder source, and Service Program. Obviously this will alleviate most of the up front work. > I am having a little problem with the updsrvpgm. If I > understand right I should be able to make a change to > a service program and then all I have to do is the > updsrvpgm command, but when I try this is doesn't seem > to take. In order for my changes to activate I have to > remove the service program from the binding directory > and then put it back, and re-compile the program(s) > using the service program. Any clues on what I might > be doing wrong? How are you creating the service programs? Do you use binder source? What activation group does the program run in? If you create a service program with binder source, using a single signature block (with a hardcoded signature), then you can add new procedures to that service program and run UPDSRVPGM (pointing to you binder source with *SRCFILE instead of *CURRENT) and the existing programs should find the changes. If the program is in a named activation group that is active when you recreate the service program, you may still be accessing the previous copy of the service program. Try UPDPGM MODULE(*NONE), or RCLACTGRP. If those don't help, signing off and back on should do the trick. Joel http://www.rpgnext.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.