There's an interesting paragraph in an article by Ed Fishel...
http://www.ibmsystemsmag.com/ibmi/november03/administrator/8118p4.aspx
Testing and Debugging
The process is masked when a reply handling exit program is called to
prevent events from being handled because some of those events could
cause problems for the message handler. A side effect of this masking is
that debug events cant be handled until the process is unmasked. This
means that the system debugging interfaces cant be used to debug a reply
handling exit program. I did two things to get around this limitation:
1. I wrote and tested just a few lines of code at a time. For
example, each time I used an API that I hadnt used before, I stopped and
tested its results.
2. I used the Dump Control Language Program (DMPCLPGM) command to
dump the variables of the program before and after the code being
tested. One good place to use DMPCLPGM is after moving some of the
information retrieved from an API to CL variables.
Hth,
-Eric DeLong
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Justin Taylor
Sent: Tuesday, February 02, 2010 1:38 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] SEP for Reply Handling Exit Program
I'm trying to debug a "Reply Handling Exit Program" (exit point
QIBM_QMH_REPLY_INQ) with an SEP. Debug seems to start (i.e. it switches
to the Debug perspective and the job loads in the Debug view), but then
the debug stops. The program executes without debugging.
Any ideas?
midrange.com
