×
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.
If you don't have the green play button in the toolbar go to the RUN drop
down menu and you can hit the "(Green play button (Shortcut F8)) called
Resume" from there. The Terminate button (Shortcut Ctrl +F2) is there
also.
Jeff Buening
Sr. Developer
P: 419.586.8599
| F: 419.586.8997
The information contained in this message (including any attachments) is
confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited and
may be unlawful.
If you are not the intended recipient, please delete this message and notify
the sender.
From: "Jeff Buening" <Jeff.Buening@xxxxxxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 02/02/2017 03:11 PM
Subject: Re: [WDSCI-L] Debug a CL program
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
After I hit OK on the "Use Step or Resume to continue your debug session
and start your application on the server." It also brings up the
"QT3REQIO.STATEMENT". Inside the tab, it says "No debug data available".
You should have a green triangle play button and a red square Terminate
button in a toolbar somewhere. You need to hit the green play
button...when you do that it will go grey...then you are ready to call
your CLP program and let the job continue from whatever job you are
running. To stop debug you hit the RED square box, but be aware the
terminate doesn't mean it stops your job, the job will complete to
finish(you are just terminating debug). To stop the job you need to go to
the System I and end it immediately if that is what you want.
Jeff Buening
Sr. Developer
P: 419.586.8599
| F: 419.586.8997
The information contained in this message (including any attachments) is
confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited
and
may be unlawful.
If you are not the intended recipient, please delete this message and
notify
the sender.
From: Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 02/02/2017 02:50 PM
Subject: Re: [WDSCI-L] Debug a CL program
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
So here is what I'm doing.
1. Find my interactive job, right click and select Debug (prompt)
2. On the "What to debug" tab, click Add, then Enter the program object
library and name - then click debug
I get the message window: "Use Step or Resume to continue your debug
session and start your application on the server."
I also get a tab that opens with the title: "QT3REQIO.STATEMENT". Inside
the tab, it says "No debug data available"
Could this be an issue with the way the source was compiled?
Second question.. Now, how do I STOP debugging the job?
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff
Buening
Sent: Thursday, February 02, 2017 2:18 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
I agree would like to get all our programs to ILE. I just compiled a CLP
program in my library form RDI. Did a Debug(Prompt) IBM-i job on my
Interactive SDS session, then called the CLP program from the command line
and it came up in the RDI debugger. So not for sure why yours would not
work? You are hitting the triangle green Play button in the debugge,
before you let the job go or call it correct?
Jeff Buening
Sr. Developer
P: 419.586.8599
| F: 419.586.8997
The information contained in this message (including any attachments) is
confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited
and may be unlawful.
If you are not the intended recipient, please delete this message and
notify the sender.
From: Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 02/02/2017 02:09 PM
Subject: Re: [WDSCI-L] Debug a CL program
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
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.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff
Buening
Sent: Thursday, February 02, 2017 1:42 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
I have debugged batch OPM CBL or CL jobs by jumping into the job, but in
order to do that I have had to set up a couple of things....
1. The source needed to be compiled with OPTION(*SRCDBG). If compiling
from RDI it is set by default, but in our environment if compiled from
PDM(other programmers that don't use RDI :(. ), that is not set by
default. So I usually end up compiling it myself thru RDI to make sure
that setting is correct.
2. Make sure the Source is in the same location that you compiled from so
the debugger finds it, unless you have the source in the object.
3. Who ever is running the job you need *Use authority to that user
account. I my self needed *Service control also. (Don't ask me any
questions about this just something I told my administrator).
4. Then I usually do Debug(Prompt)-IBM i job, and as long as you get that
setup before the job hits the program you want to debug, it should come up
in RDI. Sometimes I will have them hold the JOBQ so I have time to get
this setup, then they release the JOBQ when I am ready.
This is how I have done it, if anyone else has any easier ways or more
comments would like to hear them.......
Thanks,
Jeff
Jeff Buening
Sr. Developer
P: 419.586.8599
| F: 419.586.8997
The information contained in this message (including any attachments) is
confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited
and
may be unlawful.
If you are not the intended recipient, please delete this message and
notify
the sender.
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 02/02/2017 01:04 PM
Subject: Re: [WDSCI-L] Debug a CL program
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Can debug a running CL by doing a "Debug As"=>"IBM I job" on the job
itself?
-----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?
As an Amazon Associate we earn from qualifying purchases.
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
