RE: Modules in a service program - How many is too many? -- RPG400-L

uhhh yeah....did i mention earlier today I'm brain-fried lol

Thanks,
Tommy Holden


-----Original Message-----
From: Bob Cozzi [mailto:cozzi@xxxxxxxxx]
Sent: Friday, February 18, 2005 3:27 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Modules in a service program - How many is too many?


Tommy,
>>I would use one source member per module.
You have to use one source member per module.
Unless you go creative with /COPY's you are restricted to one source member
per module.
-Bob


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Holden Tommy
Sent: Friday, February 18, 2005 3:18 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Modules in a service program - How many is too many?

IMO I would use one service program per application set. Using order entry
for an example..

Service Program: ORDERENTRY 

Modules: ORDHDR - Order Header File Processing
         ORDDTL - Order Detail File Processing
         ORDERENTRY_UTILS - Commonly Used Calculations Module

I would use one source member per module.  I know this is a simplistic view
but hopefully it helps...

Thanks,
Tommy Holden


-----Original Message-----
From: Rick.Chevalier@xxxxxxxxxxxxxxx
[mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]
Sent: Friday, February 18, 2005 3:09 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Modules in a service program - How many is too many?



I started a different thread as the topic has changed somewhat.

Based on the last two posts to the procedure name vs. production support
thread and seeing this theme run through the prior posts I'm going to go for
the gusto and try to get the approval to combine multiple procedure into a
module and, if I understand correctly, multiple modules into a service
program.

The question I have now is where to draw the line on how to do the general
design.  First some background.  Our applications can be separated into
different areas; payments, collections, funding, etc.  Should I have a
single service program for each application area or would there be more than
one per area?  I presume one for everything is not a good idea.

Even though most of the suggestions from the other thread advocated multiple
procedures in a single module I wasn't picking up much on multiple modules
in a service program (probably my thick skull) but that seems to make sense.

Thoughts?

Rick


Privileged and Confidential.  This e-mail, and any attachments there to, is
intended only for use by the addressee(s) named herein and may contain
legally privileged or confidential information.  If you have received this
e-mail in error, please notify me immediately by a return e-mail and delete
this e-mail.  You are hereby notified that any dissemination, distribution
or copying of this e-mail and/or any attachments thereto, is strictly
prohibited.
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




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