AW: When to make a service pgm

Hi,

Any procedure or function that is not directly called from either a command
line, a menue or is submitted should be bound to a service program (and the
module deleted after binding). The same procedure should only be bound
(directly) to a single service program, but it can be called from any
proceudre in any program or service program.

If the proceudre must be changed, the module with the procedure must be
compiled and the service program must be updated.
You do not have care if there are several programs that use this function or
not.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Jeff Young
Gesendet: Monday, March 03, 2008 19:20
An: midrange-l@xxxxxxxxxxxx
Betreff: When to make a service pgm


All -
I have a function that will perform DB I/O and possible require a display
window. This function will accept 1 parameter and return 1 parameter. This
function will be called from a number of programs.

Should I -
A. Make it a service program
B. Make it a bound modue
C. Make it a stand alone program called by others as needed.

TIA

Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions
V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3 IBM Certified Specialist- e(logo)server i5Series Technical
Solutions Implementer V5R3