× 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. April 2019

Re: System debugger.

Yup, it has been around for a long time. The easiest way to access the tool - strange though it may be - is through the Run SQL Scripts (RSS) component of Access Client Solutions. (Previously found in Client Access for Windows).

From the menu bar of RSS, select RUN > SYSTEM DEBUGGER (Ctl+Shift+D).

Handy if you don't have RDi. But SEP debug rules, OK?

Brian.

On 24/04/2019 14:35, Jason Olson wrote:
Has anyone used the system debugger contained in the JT400 IFS directory? I
found some documentation on this and the software is located in

/QIBM/ProdData/HTTP/Public/jt400/lib

I moved the jt400.jar & the tes.jar file to my local PC, and if you
run utilities.DebugMgr you have a graphical debugger. I had never seen
this before but it's working OK. It's not RDi, but if you don't have RDi
and want a graphical debugger this one seems to work. To get the help to
work you need to find a copy of jhall.jar but that was easy to find on the
web.


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.