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



Thanks Nazmin:

I thought I had tried that, perhaps I didn't clear both caches. I fired
up the old workspace and clearing the caches worked!!! Beats my theory of
creating a new workspace!

Making the caches bigger helps to. Don't go overboard. I did, a large
enough cache area causes its own set of problems. 1 gig seems to be fine
and takes a while to overfill.

Bill Blalock





Nazmin Haji <haji@xxxxxxxxxx>
06/28/2007 02:25 PM
Please respond to Websphere Development Studio Client for iSeries

To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
cc: (bcc: Bill Blalock/TUS/US/Certegy)
Subject: Re: [WDSCI-L] LPEX Editor - Cancel Verfiy


Hi,
We are aware of the caching problems and are working on it (I guess not
very successfully yet).
You do not have to create a new workspace. You can clear the cache. There
are two places you will
find cache preference:
1. under Remote Systems->iSeries->Cache
2. under Remote Systems->File Cache
Clear both of them. Hope this helps.
Regards,
Nazmin Haji



bill.blalock@cert
egy.com
Sent by: To

wdsci-l-bounces@m "Websphere Development Studio
idrange.com Client for iSeries"
<wdsci-l@xxxxxxxxxxxx>
cc

06/28/2007 02:40
PM Subject

Re: [WDSCI-L] LPEX Editor - Cancel
Verfiy
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>





Is creating a new workspace practical? It works for me. Not sure why but

I think its a caching problem.




Jeff Young <cooljeff913@xxxxxxxxx>
06/28/2007 01:29 PM
Please respond to Websphere Development Studio Client for iSeries
To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
cc: (bcc: Bill Blalock/TUS/US/Certegy)
Subject: Re: [WDSCI-L] LPEX Editor - Cancel Verfiy

Thanks for the info Bill.
In my case, the creation of a smaller library is not pratical, but I will
hope that they get the fix soon.

Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions
V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions
Implementer V5R3






----- Original Message ----
From: "bill.blalock@xxxxxxxxxxx" <bill.blalock@xxxxxxxxxxx>
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>

Sent: Thursday, June 28, 2007 1:32:51 PM
Subject: Re: [WDSCI-L] LPEX Editor - Cancel Verfiy
Jeff:
I openned a PMR about this problem, taking minutes. 82443,005. The
sympton was log verifies and outlines and task manager showing near 100%
CPU utilization while the verify or outline works. Cancel was ignored for

the verify as you reported.
In my case I have a very large production library which keeps the
development copies of files, COPY members, service program, etc.
The long and the short of it is that the PMR got rolled into an APAR for a

future release.
I discovered that if I moved just what the outline / verify needed from
the very large production library into a small library the outline and
verify went much faster. Not a practical work around, especially for
complicated programs.
I later discovered that if I created a new workspace the problem would go
away for a while. I have done this three times. A 10 minute verify from
the cache on the previous workspace took less than one minute building the

cache. Once the cache was built the verifies became even faster. This is

more practical.
If you decide to try this please let me know if it works or doesn't work
for you.
Bill Blalock



Jeff Young <cooljeff913@xxxxxxxxx>
06/28/2007 11:46 AM
Please respond to Websphere Development Studio Client for iSeries
To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
cc: (bcc: Bill Blalock/TUS/US/Certegy)
Subject: Re: [WDSCI-L] LPEX Editor - Cancel Verfiy
Depending on the size of the program, it can take minutes.
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions
V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions
Implementer V5R3




----- Original Message ----
From: "bill.blalock@xxxxxxxxxxx" <bill.blalock@xxxxxxxxxxx>
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>

Sent: Thursday, June 28, 2007 9:33:57 AM
Subject: Re: [WDSCI-L] LPEX Editor - Cancel Verfiy
I have observed the same behaviour.
How long is the verification taking?


Jeff Young <cooljeff913@xxxxxxxxx>
06/27/2007 03:27 PM
Please respond to Websphere Development Studio Client for iSeries
To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
cc: (bcc: Bill Blalock/TUS/US/Certegy)
Subject: [WDSCI-L] LPEX Editor - Cancel Verfiy
In the LPEX editor, once I request the verify function for a source
member, it seems that there is still no way to stop it before completion.
I click on the red box at the bottom of the window and it changes to grey,

but the verify function still continues.
This has been a problem since V5 or WDSc, and I am now on V7 with the
latest fix pack.
Is this a known issue, and if so, is anything being done to address it?
Thanks,
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions
V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions
Implementer V5R3

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.