× 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 4/4/2016 1:34 PM, Needles,Stephen J wrote:
Here is the scenario...

Existing code has a program (bound *MODULE) that is the registered Error Handler. Other bound *MODULES are also bound to the same Error Handler.

New Condition Handler that attaches as a Bind service program. It is registered in place of the original *MODULE in the caller.

Because the other bound *MODULES use the original, both Condition Handlers need to be included in the CRTPGM statement.

Provided that each module registers its particular flavor of condition handler, is there any hierarchical processing that might trip up?

Is there any particular harm in including both condition handlers in the *PGM?


Steve, assuming the new condition handler has a different name from the original one, there should be no problem. When procedure H1 is registered as condition handler for procedure P1, that connection is specific to H1 and P1. If there is some other procedure H2 that is registered as a condition handler to some other procedure P2, that relationship is irrelevant to P1 and H1.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.