|
Hi Bob, Can you check the commtrace.txt and rsecomm.log files in the following directory: C:\Documents and Settings\%windowsUserID%\.eclipse\RSE And append anything from them here (they may or may not be empty). Also check for errors in the workspace .log file from the workspace\.metadata folder (the workspace location is the path you are prompted for when starting WDSC). If the file is large then just send it directly to me. You may also want to try stopping and restarting the TCP/IP *DDM server. Don Yantzi Technical Lead WebSphere Development Studio Client for iSeries IBM Toronto Lab David Gibbs <david@xxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 03/14/2007 02:49 PM Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> cc Subject [WDSCI-L] Connection problems (was: WDSC dual screen) Bob Cozzi wrote:
I have SI26285 and SI20905 (SI26285 supersedes SI23395).
Well, specifically, did you run the Verify Connection option to make sure that you have the PTF's that WDSC thinks you should have? My suggestion is to make sure you have all the necessary PTF's and then IPL the system. On my V5R2 system, even after I applied the PTF (which were Immediate and had no extra instructions for application), I still had problems until the system re-ipled. I probably just had to stop & start some subsystems, so that the ptfed code would be used, but I couldn't figure out what subsystems to restart. david
As an Amazon Associate we earn from qualifying purchases.
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.