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



Greetings -

We are trying to implement ILE concepts along with modularization.  My
question is, when have you taken binding do far?

Here's what we have:

PgmA contains the following modules:
PgmA = RPG entry point program
PgmAc = CL program to start commitment control
PgmAs1 = subfile server in order number sequence
PgmAs2 = subfile server in customer name sequence
PgmAs3 = subfile server in customer number sequence
PgmB = Flat panel maintenance for the order header
PgmBedt = Editing server program for order header
PgmC = Order detail subfile
PgmCs1 = subfile server for order detail
PgmD = Flat panel maintenance for order detail
PgmDedt = Editing server for order detail

Beings that there isn't any reason to access the detail data without the
header information, where do you draw the line at binding modules into one
program?  Is there a rule of thumb for the number of modules bound into one
program?

Any info would be appreciated.

TIA,
Jade Richtsmeier
Analyst/Programmer
MN Counties Information Systems
Grand Rapids, MN

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.