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


  1.  Home
  2. MIDRANGE-L
  3. May 2017

Re: Service programs

On Mon, May 15, 2017 at 2:05 PM, Mark S Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Reasons to use a *PGM:
===================

1. it is to be invoked from a command-line, e.g. via a COMMAND
interface, or from a menu.
2. it will be submitted to run as a batch job, to:
* generate a report
* perform an end-of-day consolidation process (like in banking)
* perform some kind of "merge/purge" processing
* etc.
3. it will be called from some "client/server" interface that expects
to CALL a *PGM


​Note that it's quite easy to create a *PGM wrapper around a procedure in a
service program​. ILE CL works well quick nicely (as does ILE RPG of
course)
pgm
callprc myprocedure)
endpgm


So don't think that just because you need (or may want) to submit a process
to batch stop you from putting the logic into a procedure.

The converse is not true, you can't really put a procedure wrapper on a
*PGM.

Charles

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.