RE: Debugging QIBM_QMH_REPLY_INQ

I found the same thing when I got to the correct docs. I ended up just writing a bunch a lines to the joblog.

Thanks



-----Original Message-----
From: Steve Hinrichs via RPG400-L [mailto:rpg400-l@xxxxxxxxxxxxxxxxxx]
Sent: Friday, August 02, 2019 2:52 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Cc: Steve Hinrichs <Steve.Hinrichs@xxxxxxxxxxxxxxx>
Subject: RE: Debugging QIBM_QMH_REPLY_INQ

Justin -

I worked with IBM on the creation of that exit point, and debug was blocked on purpose. What I did is code a logging/debug feature into our process for this purpose.

Steve

subject: Debugging QIBM_QMH_REPLY_INQ

I have an RPGLE program registered for exit point QIBM_QMH_REPLY_INQ that I'm trying to debug. It's running in a 5250 job. With an RDi SEP, the debugger starts but the 5250 session continues with the debug stopping. I tried STRDBG (IIRC, that's the correct 5250 debugger), and it does the same thing.

Any suggestions?