RE: Debugging QIBM_QMH_REPLY

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Debugging QIBM_QMH_REPLY_INQ
From: Steve Hinrichs <Steve.Hinrichs@xxxxxxxxxxxxxxx>
Date: Fri, 2 Aug 2019 19:51:50 +0000
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

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?

Follow-Ups:

RE: Debugging QIBM_QMH_REPLY_INQ , Justin Taylor

This mailing list archive is Copyright 1997-2026 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.

RE: Debugging QIBM_QMH_REPLY_INQ