×
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.
Thanks...
Ken... I'm not sure I can go back to the green screen debugger.
Brian... I'll take a look.
But IBM (if you're listening)... what the heck?
(I hate java applications)
-----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.
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.
midrange.com
