×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
hi John,
UPDSRVPGM is to replace a module in an *existing* service program. So
if you had SRVPGM1 and it was made up of MODULEA, MODULEB, MODULEC you
might want to recompile just MODULEB without changing the other two, and
replace just that part of the service program. So you'd CRTRPGMOD
MODULEB, and then UPDSRVPGM SRVPGM1 MODULE(MODULEB) and presto, you've
recompiled just one part of the service program, and replaced it without
having to touch the other two modules.
However -- if the service program doesn't yet exist, UPDSRVPGM won't
work. Again, as the name "update" implies -- it's there to update an
existing one, not create a new one.
To create a new one, use the CRTSRVPGM command.
On 2/19/2010 4:54 PM, Kelly, John (Limerick) wrote:
This where I get confused with the binding directory stuff. I created
the module program successfully (via CRTRPGMOD). I then ran the
UPDSVRPGM. The message tells me that UTILITY service program does not
exist. With just running the CRTRPGMOD and UPDSRVPGM I cannot see were
the UTILITY service program object gets created.
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.
midrange.com
