×
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.
Love this! The Paid version of the IBM Debug does not work. So, use the IBM "FREE" Debugger. This is TOO FUNNY! <LOL>
PS. I wonder if Microsoft would do the same sort of post. Would they day our Professional debugger does not work, try the "free" version and see if that works. Hmmmmmmm, makes me wonder what is different between customer support on Microsoft & IBM... Just a thought....
I have been using the green screen debugger, and my stress is GONE! It just works! IBM i know "GREEN SCREEN" technology! Awesome! It works EVERYTIME without FAIL! Bravo IBM! <Big Happy Smile>
Ken Killian
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Brian Parkins
Sent: Wednesday, June 24, 2020 12:51 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug just randomly stops communicating
If it helps anyway, (and it probably doesn't) there is a third alternative. You could also use the graphical IBM i System Debug tool.
https://www.ibm.com/developerworks/ibmi/library/i-debug/index.html
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzamq/rzamqmain.htm
The easiest way to access it is through the Run SQL Scripts function in Access Client Solutions (ACS). Select RUN from the menu bar to find it.
(Still don't understand why it's tucked away in such an obscure location.)
HTH,
Brian.
On 24/06/2020 17:23, Ken Killian wrote:
Just use Green Screen debug, at least it is reliable.
midrange.com
