Re: WDSCI-L Digest, Vol 2, Issue 289

Subject: [WDSCI-L] Problem with the verify.

Which version of WDSC are you using, I believe with WDSC v5.1 the
cache issue has been resolved.  I don't have my PC with WDSC installed
on it right now, but if you have v5.0 you can set the cache size to 0
and it will no longer cache during the verify.  If you are still
having problems with this it would be best to contact IBM iSeries
support their LPEX developer will resolve this issue if there is a
problem.

On Fri, 23 Jul 2004 12:00:41 -0500, wdsci-l-request@xxxxxxxxxxxx
<wdsci-l-request@xxxxxxxxxxxx> wrote:
> Send WDSCI-L mailing list submissions to
>        wdsci-l@xxxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.midrange.com/mailman/listinfo/wdsci-l
> or, via email, send a message with subject or body 'help' to
>        wdsci-l-request@xxxxxxxxxxxx
> 
> You can reach the person managing the list at
>        wdsci-l-owner@xxxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WDSCI-L digest..."
> 
> Today's Topics:
> 
>   1. RE: Problem with the verify. (Kelly Cookson)
>   2. RE: Problem with the verify. (Vitale, Daniel)
> 
> ----------------------------------------------------------------------
> 
> message: 1
> date: Fri, 23 Jul 2004 11:46:35 -0500
> from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> Clearing the cache did not work. Thanks for the suggestion, though. Worth a
> shot.
> 
> We have a very definite pattern:
> 
> All programmers running 1G RAM on Windows XP can verify ILE and OPM programs
> of any size (that we have).
> 
> All programmers running 512MB RAM on Windows 2000 can verify short (100-200
> line) ILE programs no problem, short OPM programs with a 5-10 minute delay,
> and no long programs.
> 
> I'm assuming at this point the verify option basically does not work with
> the IBM minimum accepted RAM and OS requirements.  Until I hear differently,
> I'm going to tell the programmers with 512MB to avoid verify and simply
> compile.
> 
> Thanks,
> Kelly
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 11:08 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Bob,
> 
> >From the menu bar:
> Window, Preferences, Remote Systems, iSeries, Cache.  The last option is to
> "Clear the current cache".  Press clear and a confirmation window will pop
> up, press OK and the cache will be cleared.
> 
> Mike
> 
> -----Original Message-----
> From: Bob Anderson [mailto:banderson@xxxxxxxxxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 10:33 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Mike,
>        How do you go about clearing the cache. Inquiring minds with 512 RAM
> would
> love to know.
> 
> Bob
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Tobey
> Sent: Friday, July 23, 2004 11:21 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Kelly,
> 
> I have 512 RAM and occasionally encounter the situation you have described.
> I have found that this happens when I haven't cleared the cache in awhile.
> Once I clear the cache the verifies run fine.
> 
> Mike.
> 
> -----Original Message-----
> From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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.
> 
> ------------------------------
> 
> message: 2
> date: Fri, 23 Jul 2004 12:53:52 -0400
> from: "Vitale, Daniel" <Daniel.Vitale@xxxxxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> This is an old IBM story about WDSc; always the hardware is "helping"
> the bad performance of the software....
> 
> Dan
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Kelly Cookson
> Sent: Friday, July 23, 2004 12:47 PM
> To: 'Websphere Development Studio Client for iSeries'
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Clearing the cache did not work. Thanks for the suggestion, though.
> Worth a
> shot.
> 
> We have a very definite pattern:
> 
> All programmers running 1G RAM on Windows XP can verify ILE and OPM
> programs
> of any size (that we have).
> 
> All programmers running 512MB RAM on Windows 2000 can verify short
> (100-200
> line) ILE programs no problem, short OPM programs with a 5-10 minute
> delay,
> and no long programs.
> 
> I'm assuming at this point the verify option basically does not work
> with
> the IBM minimum accepted RAM and OS requirements.  Until I hear
> differently,
> I'm going to tell the programmers with 512MB to avoid verify and simply
> compile.
> 
> Thanks,
> Kelly
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 11:08 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Bob,
> 
> >From the menu bar:
> Window, Preferences, Remote Systems, iSeries, Cache.  The last option is
> to
> "Clear the current cache".  Press clear and a confirmation window will
> pop
> up, press OK and the cache will be cleared.
> 
> Mike
> 
> -----Original Message-----
> From: Bob Anderson [mailto:banderson@xxxxxxxxxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 10:33 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Mike,
>        How do you go about clearing the cache. Inquiring minds with 512
> RAM
> would
> love to know.
> 
> Bob
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Tobey
> Sent: Friday, July 23, 2004 11:21 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Kelly,
> 
> I have 512 RAM and occasionally encounter the situation you have
> described.
> I have found that this happens when I haven't cleared the cache in
> awhile.
> Once I clear the cache the verifies run fine.
> 
> Mike.
> 
> -----Original Message-----
> From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified
> programs
> using the Verify option in the Source menu. This week, three of us could
> no
> longer verify programs, but one of us still can. (I've asked all
> programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing
> at
> all changes on the screen--no status bar or status message, nothing. If
> you
> look at the task manager, WDSCi is using about 90-99% of the CPU during
> this
> delay. Then the status bar finally comes up. The status bar runs
> endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end.
> Hitting
> the cancel button on the status bar does not end the verify. We have had
> to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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.
> _______________________________________________
> 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) digest 
> 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.
> 
> End of WDSCI-L Digest, Vol 2, Issue 289
> ***************************************
>