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



Kelly,
        I have an old PIII with 512 RAM and Win 2000. I can verify a fairly big 
ILE
program but anything else doesn't even have the option to Verify.

Bob Anderson
EDI Coordinator
Kent Watersports
banderson@xxxxxxxxxxxxxxxxxxx
419.929.7021 x315
Fax 419.929.1380

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Kelly Cookson
Sent: Friday, July 23, 2004 10:53 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: RE: [WDSCI-L] Problem with the verify.


Update:

Programmers with new PCs (1G RAM, Windows XP) have no problems verifying
source.

Programmers with older PCs (512 RAM, Windows 2000) can verify short ILE
programs, but cannot verify long ILE programs or any OPM programs.

Should we even be using verify on OPM? And does verify require more than
512RAM for larger (over 150 source lines) programs?

Thanks,
Kelly


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@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.


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.