Statically binding multiple MAIN modules with display files -- RPG400-L

Subject: Statically binding multiple MAIN modules with display files
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Date: Tue, 20 Jan 2004 11:14:25 -0600
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / 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>

General question:

Is there a good reason to bind together multiple application programs
each with their own display files, or is the recommendation still to use
dynamic CALLs?

What are the pros and cons of binding multiple programs together that
have their own display files?  It seems to me that this is a place where
the dynamic CALL still makes sense.

Joe

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Statically binding multiple MAIN modules with display files , James Rich
Re: Statically binding multiple MAIN modules with display files , Scott Klement
Re: Statically binding multiple MAIN modules with display files , Scott Mildenberger

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.