Re: Maintaining Service Program signatures -- RPG400-L

Subject: Re: Maintaining Service Program signatures
From: Rory Hewitt <rory.hewitt@xxxxxxxxx>
Date: Wed, 20 Feb 2013 08:51:35 -0800
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

RPGLIST,

You only need the binder file at 'compilation' time (when the CRTSRVPGM
command is run), so the only things you need to promote to production are
the *SRVPGM itself and any copybooks that define the procedures exported
from it.

Rory

On Wed, Feb 20, 2013 at 7:50 AM, RPGLIST <rpglist@xxxxxxxxxxx> wrote:

I would also assume that binder file as well as the prototype copybook
must be promoted to a production box along with the service program, but
the module would not since its incorporated into the service program,
unless of course the objects are recompiled when promoting which isn't the
case with all systems.

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.