I agree with Simon. I use multiple modules within one program (not a
service program) all the time. We have one rule that states every
screen is to be an individual "process". We had to change the word to
process instead of program because we switched from programs to modules.
Sharon Wintermute
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Thursday, October 15, 2009 3:08 PM
To: RPG programming on the IBM i / System i
Subject: Re: Service programs and QSRVSRC
On 16/10/2009, at 5:08 AM, Lim Hock-Chai wrote:
I don't ever think of a situation where I would want to create a
program
using multiple *MODULE. If there are common functions that needed by
other programs, I put those functions in a service program and bind
them
with the service program.
How about the classic MVC arrangement?
o Module for screen handling
o Module for control flow
o Module for data access
The data access module will likely call functions in a service program
to perform the real work but this approach (if done properly allows
you plug in a different screen handler (e.g., CGI) or different
database access. None of these modules would be common to other
programs but by using separate modules I gain more flexibility at the
cost of a slight increase in complexity.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
