Many things to consider but on the surface based on info provided...

1) leave screen pgms as *pgms separates as they currently are.
2) are there any subroutines or procedures that are repeated among the pgms? Or similar code that could easily be combined to make a subprocedure out of with appropriate designated parms. If so these are candidates for subprocedures to go in new service pgm to be shared among the *pgms.



Jay

On Feb 16, 2019, at 1:35 AM, Booth Martin <booth@xxxxxxxxxxxx> wrote:


This exercise is not going well. Lets say I have 4 programs, 3 of which have display screens, and each program has one to four specific activities. There are two data files used.

1. Do I combine all 3 display files into one?
2. Do I compile the programs as modules?
3. Do I write a service program, turning every activity into a procedure?

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.