×
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.
So it seems your program did not have *LISTING view. Otherwise, you could
switch to *LISTING view.
One workaround I could think of is that you could copy the source for RPG
into one of your local folder, for example, "d:\tmp\MYRPG.RPGLE".
Then when the debugger startup, you could click on the button "Change Text
File...". Then you could click on the Browse button there to find the
copied RPG source (e.g., "d:\tmp\MYRPG.RPGLE"). This way, it should not
take too long. Please be awared that the source will be displayed in the
Debug Editor (with bug icon) instead of the i5/OS LPEX editor (with a pen
icon). So no tokenization or outline view support will be available for
this edtor.
Thanks,
Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Bailey Paul" <paul.bailey@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/02/2008 09:05 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] Source defaults for SEP
Thanks Xuan,
It may be that it was me who requested it before, but I have a mind like
a swiss cheese!
Is there a quick way of locating the source files that I need to add to
the source lookup table while the SEP is active? At the moment I need
to: click "Edit Source Lookup...", click "Add", double-click "iSeries
Source File", expand my connection, expand "Work with libraries...",
type or select my library, then (when the filter is complete) expand the
filter and select the source file(s) I need. This last step is taking
the longest, but the whole process can take up to 40 seconds. Is this
the wrong way of doing it?
Best regards,
Paul
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Xuan Chen
Sent: 2 May 2008 12:59
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Source defaults for SEP
Paul,
I don't think it is possible right now. It is in the list of our
requirements.
Thanks,
Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Bailey Paul" <paul.bailey@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/02/2008 06:41 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
[WDSCI-L] Source defaults for SEP
Hi,
I have a situation which is time critical. A small RPGLE program is
called to receive information from another system. If there is too much
time between each part of the conversation with the other system (e.g.
start, get, confirm, end), the connection resets and you need to start
all over again. I do not know all the job details beforehand, so I need
to use an SEP but if I try to use an SEP to debug this small interface
program then I need to edit the source lookup entries to tell it where
to find the source. This takes too long, and the connection fails before
I can start debugging.
When an SEP fires, a file called tmp.launch is created in the
"<workspace>\.metadata\.plugins\org.eclipse.debug.core\.launches"
folder. This file contains (among other things) the source lookup table
for the SEP. Does anyone know where the defaults for this file are kept?
If not, does anyone know of a way I can override these defaults somehow?
Thanks in advance for your help.
Paul.
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.