Re: Service programs

In this case no point in using Service Programs compared with a stand-alone program as long as the called routine actually outputs the response. Any potential performance improvement is meaningless in this kind of "may never be called or if it is only rarely" type of scenario.

Only time I would consider it in the case of infrequently called code is when the called routine returns a response that I'm going to test/store/output. In that case the benefit of being able to code:

X = my routine(parms);
or
If my routine(parms) > maxValue;

makes it worthwhile in terms of readability.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On May 15, 2017, at 3:24 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

Why would one use a service program instead of a stand-alone program? and the opposite?

For the sake of discussion, lets use a FAQ program that is for the F1 key in programs and is system wide. Its the same everywhere - the only change being the FAQ data file which is determined by the library list. It displays FAQs and can be edited to add, delete, and update questions. Its an actual application I use, as a standalone program.

So, I see Service Programs mentioned and think I should change how I do it. Then I look at the process and scratch my head. Why would I make the change? What is the benefit? The more I read about it, the faster I scratch.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD