Re: Debug just randomly stops communicating -- WDSCI-L

Subject: Re: Debug just randomly stops communicating
From: Brian Parkins <goodprophet.bp@xxxxxxxxx>
Date: Wed, 24 Jun 2020 17:50:40 +0100
List-archive: <https://archive.midrange.com/wdsci-l/>
List-help: <mailto:wdsci-l-request@lists.midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.lists.midrange.com>
List-post: <mailto:wdsci-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@lists.midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Debug just randomly stops communicating , Greg Wilburn

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