Re: Debug a CL program -- WDSCI-L

Subject: Re: Debug a CL program
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Fri, 3 Feb 2017 14:02:56 +0000
List-archive: <http://archive.midrange.com/wdsci-l/>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

"This is one of the things I dislike about RDi and debugging"

I think you're pointing the finger the wrong direction there.

-----Original Message-----
From: Greg Wilburn [mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, February 02, 2017 1:08 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug a CL program

Those are the steps I took before posting this message. I'm the one calling the CLP. It did not come up in debug.

This is one of the things I dislike about RDi and debugging. It's awesome if you're dealing with SEPs and ILE programs. But with CL and OPM programs it's significantly more difficult than reverting to green screen debuggers.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Debug a CL program , Greg Wilburn

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.