Re: Maintaining Service Program signatures -- RPG400-L

× 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.

Kurt,

Aha!

I'm coming from the position of a software developer that makes my software
available to others - I provide a *SRVPGM object and copybooks and say
"Here is a service program with a bunch of useful procedures, defined in
this copybook. Go crazy!". But you're right that in a normal production
environment, even the copybook isn't needed.

Rory

On Wed, Feb 20, 2013 at 8:55 AM, Anderson, Kurt <KAnderson@xxxxxxxxxxxx>wrote:

You don't need to copy source files to production in order for the service
program to work. I guess ask yourself - what role do those items play, and
how are they different than modules that would make you want to also
promote them to production?

Oversimplification:
Binder Source + possible Copybook(s) + Module(s) + (possible other things)
= Service Program

In the above, only Service Program would need to be moved to a production
box if all of your compiling is occurring off the production box. (The
copybooks will be needed where other programs get compiled that are using
the service program.)

-Kurt

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.