Re: Strange WDSC problem

Try updating to version 6.5.722.000 of ZoneAlarm. :)

---
Scott Klement  http://www.scottklement.com


On Wed, 21 Jun 2006, Juracich, Jon wrote:

I recently upgraded WDSC 6 to 6.0.1. It now appears that I cannot update 
existing source file members! If I save the source as a different member name, 
then I am able to update the new member, but not consistently. What's more, I 
can close the member, close WDSC, re-open everything and WDSC thinks that all 
of the changes are in place. But the member on the System i has none of the 
changes. It's as if I'm just updating the local copy. But I don't know how to 
tell WDSC to *not* do that!!

I've also tried deleting the workspace and creating a new one with a different 
name, also to no avail.

Possibly related, on or about the same time, I switched from Symantec to 
ZoneAlarm (don't ask), but I don't THINK ZoneAlarm is the problem, because I've 
disabled ZoneAlarm and the effect is the same.

The systems that I'm working on are both at V5R3 - one is a client machine that 
I would have NO control over, the other is our system, which I could load 
necessary PTFs, etc. on, if necessary. But I think the problem is local to my 
PC and is probably a configuration issue. And I don't know how to fix it.

If anyone can help me on this, I would really appreciate it!

Jon Juracich, IBM Certified Specialist: RPG IV Developer
Sr. Staff Consultant, IBM Development Practice

Affiliated, Inc.
(614)889-6555, ext 355

www.aresgrp.com

We help companies use technology and resources to identify and solve the 
business issues that drive bottom-line results

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