× 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. RPG400-L
  3. August 2019

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?


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.