×
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.
The job in question cannot be submitted... it drives a user screen.
I'm of the opinion that if it takes that many steps to get RDi to work, I'll continue to use STRISDB.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Friday, February 03, 2017 8:24 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debug a CL program
See responses embedded below:
Michael Quigley
Computer Services
The Way International
www.TheWay.org
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 02/02/2017 03:13:27 PM:
----- Message from Jeff Young <jyoung0950@xxxxxxxxx> on Thu, 2 Feb
2017 14:58:01 -0500 -----
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
Greg,
As far as the No Debug data available, you might try to recompile your
CLP
with the option(*srcdbg) keyword, then (not sure how in rdi) specify
opmsrc(*yes) on the STRDBG command.
Jeff Young
Sr. Programmer Analyst
Jeff,
The OP asked about debugging in RDi, your response is not an RDi/WDSc answer.
-----Original Message-----
From: Greg Wilburn [mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, February 02, 2017 10:31 AM
To: Rational Developer for IBM i / Websphere Development Studio
Client
for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Debug a CL program
Stupid Question:
Can I use RDi to debug a non-ILE CL program?
If so, how do I go about doing that?
Greg,
If you want to debug a batch OPM program, the easiest way is to submit it on hold--e.g., SBMJOB xxxxxxxx HOLD(*YES). I usually do this by way of the *JOBD with which I'm submitting (e.g., CHGJOBD smbjobdname HOLD(*YES)--or I create a *JOBD in my library with the same name as the one used by the submitting process). Then I go into the Debug perspective and select 'Debug Configurations...'. Then I set up a new "IBM i: Debug Job". I code the Job Name and User and set the Number to * (a single asterisk); then I specify the program I want to debug; and click 'Debug'. RDi (and the host server jobs) see a job for the user on hold, the job is released and RDi stops on the first executable statement in the program. This isn't quite as good as a SEP, but it works well for me when I have to debug OPM programs.
One additional point to make: someone suggested converting the program to CLLE and recompiling. You have to be careful with that as it can impact override scoping. The scoping of overrides is the area that really takes some thought when converting an application to ILE. (That and *NOTIFY messages no longer server much purpose--at least not the same purpose.)
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.