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


  • Subject: RE: Design question re: SrvPgm Modules & Procedures
  • From: Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>
  • Date: Wed, 16 Feb 2000 11:42:06 -0500

Paul Jackson wrote:

>So within SCRAMSRV I will have the following procedures:
>
>Scramble -- available outside srvpgm
>Unscramble -- available outside srvpgm
>ProcA
>ProcB
>
>My question is: Should I have these procedures 
>in separate source members and compile as 
>separate modules or should I throw everything 
>into one source member?

Reasons to go with one member = one service program: sharing global (ugh)
data and "internal" subprocedures, ability to locate all related functions
easily and the ability to save/restore all the source required to re-build
your service program in one operation.

Reasons to go with one member = one subprocedure: enforces mental discipline
and more granularity (you can use PROCA in another service program).

Personally, I'd go with putting all the subprocedures into one member.

Buck Calabro
+---
| 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 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.