Re: Service program signatures, and how to avoid unnecessarilyrecompiling programs that call service programs -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Service program signatures, and how to avoid unnecessarilyrecompiling programs that call service programs
From: dlclark@xxxxxxxxxxxxxxxx
Date: Thu, 14 Sep 2017 15:49:09 -0400
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 09/14/2017 03:44:03
PM:

This raised another question, to which I think I know the answer, but
confirmation is appreciated.

When deploying program / service program objects to a production system,

never need to include *MODULE and *BNDDIR objects. Correct? (We do not
compile anything on the production system.)

Correct. But we do keep our *MODULE objects on the production
system in case we want to do an UPDPGM or UPDSRVPGM. The binding
directory is not needed on production -- even for UPDPGM or UPDSRVPGM (we
use explicit references with the BNDSRVPGM parameter in this case).

Sincerely,

Dave Clark

This mailing list archive is Copyright 1997-2026 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.