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



On Wed, 8 May 2002, Smith, Nelson wrote:
>
> I agree that *CALLER would be preferable, but when the preponderance of
> existing programs are still running in OPM, *CALLER just does not work.
> Strange things occur and I get phone calls in the night. Due to the number
> of override problems, etc, I cannot safely use *CALLER without carefully
> tracing through every single job that might use the service programs. Since
> the service programs have no way of knowing who will call them, we had to
> put them in their own AG.

I'll agree with Scott.  As a general rule, *CALLER should always be used
with a service programs.  This does NOT mean that *CALLER should be
used EVERYWHERE, however.

Since you can't call a service program from an OPM program, using *CALLER
should be fine.




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.