× 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.



That (and clearing the cache) fixed the problem.  I guess I can leave that 
Max cache size at 0, or clear the cache when I make a similar change 
between debugs.

Does the cache work differently when you use the RSE jLpeg editor?

Kirk


wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/30/2005 02:29:09 PM:

> Kirk,
> 
> Could you please try to disable the file caching and see if you still 
get
> the same problem?  To do that, please follow the steps below:
> 
>    Bring up the Preference dialog by Windowns -> Preference.
>    Got to Remote Systems -> File Cache page of the Preference dialog. 
Set
>    the Max cache size to 0.
> 
> Thanks,
> 
> Xuan Chen,  Problem Determination Tools for iSeries
> (905) 413-3769 T/L 969-3769
> xuanchen@xxxxxxxxxx
> 
> 
> 
> 
>  
>              Kirk.Palmer@Walsw  
>              orth.com  
>              Sent by: To 
>              wdsci-l-bounces@m         Websphere Development Studio 
Client 
>              idrange.com               for iSeries 
<wdsci-l@xxxxxxxxxxxx> 
> cc 
>  
>              03/30/2005 02:37 Subject 
>              PM                        Re: [WDSCI-L] Debugger  
>  
>  
>              Please respond to  
>                  Websphere  
>                 Development  
>              Studio Client for  
>                   iSeries  
>  
>  
> 
> 
> 
> 
> Version: 5.1.2.4
> Build id: 20050104_2139
> 
> Because we haven't yet been able to apply the correct PTFs for RSE on 
our
> iSeries (therefore not able to run STRRSESRV), I am using RSE (just like 
I
> used PCO) to open my source members in the Classic CODE editor, and
> compiling from that editor.
> 
> I debug by starting the debugger and connecting to a separate iSeries
> session to run the program.  When the source comes up in the debug 
editor,
> it doesn't reflect the changes I just made.  Because I compile the RPG
> program with DBGVIEW(*ALL), I am able to switch to the Listing view and
> continue, but I usually work from the Source view.
> 
> Kirk
> 
> wdsci-l-bounces+kirk.palmer=walsworth.com@xxxxxxxxxxxx wrote on 
03/30/2005
> 12:49:17 PM:
> 
> > Kirk,
> >
> > What is the version of WDSC you used?  Could you please describe your
> > scenario with more details?  Thanks.
> >
> > For WDSC 5.1.2, you use the iSeries editor for your development in 
RSE.
> > And when you invoke the debugger, the source will be displayed in
> another
> > editor (with a bug icon on its tab), and in browse mode.  Is it the 
case
> > for you?
> >
> > Regards,
> >
> > Xuan Chen,  Problem Determination Tools for iSeries
> > (905) 413-3769 T/L 969-3769
> > xuanchen@xxxxxxxxxx
> >
> >
> >
> >
> >
> >              Kirk.Palmer@Walsw
> >              orth.com
> >              Sent by: To
> >              wdsci-l-bounces@m         wdsci-l@xxxxxxxxxxxx
> >              idrange.com cc
> >
> > Subject
> >              03/30/2005 12:22          [WDSCI-L] Debugger
> >              PM
> >
> >
> >              Please respond to
> >                  Websphere
> >                 Development
> >              Studio Client for
> >                   iSeries
> >
> >
> >
> >
> >
> >
> > I have a problem with the source that the debugger uses.
> >
> > Here is the situation:  I debug an iSeries program (RPG IV). I find a
> bug.
> >  I fix the source and recompile.  When I go back into the debugger, it
> is
> > still showing the older version of the source, without the fixes.  It
> will
> > run the newer version of the program, but when lines have been moved 
or
> > changed, it is extremely difficult to debug this way.
> >
> > How do I get the debugger to retrieve the source from the iSeries
> instead
> > of from the cache?  (Assuming the source is cached)
> >
> > Thanks,
> > Kirk
> > --
> > This is the Websphere Development Studio Client for 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.
> >
> >
> > --
> > This is the Websphere Development Studio Client for 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.
> --
> This is the Websphere Development Studio Client for 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.
> 
> 
> -- 
> This is the Websphere Development Studio Client for 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.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.