|
Hi, I was excited to read that a new SP was available for WDSc, but after a look on the webpage, I could again not find any major changes or progress in the WDSc area ?! When will we see new features in this area, when will it be based on Eclipse 2.0, ... I promoted the product to quite some people... but all return to their previous development method after they find out that it is still a big work in progress. (I can't understand that still effort is invested in Code/400 for example). Kind regards, Paul -----Original Message----- From: wdsci-l-admin@midrange.com [mailto:wdsci-l-admin@midrange.com]On Behalf Of yantzi@ca.ibm.com Sent: Sunday, November 10, 2002 5:56 PM To: wdsci-l@midrange.com Subject: Re: [WDSCI-L] Lost Server Definition Sam, We believe that this problem is fixed in service pack 3 for WDSc (released on Friday.) Since we have not been able to reproduce the problem yet we cannot be 100% sure. Please apply the service pack and let us know if you still have this problem. To download SP3: Go to: http://www-3.ibm.com/software/ad/iseries/ Select WebSphere Development Studio Client for iSeries Click on Download (left hand side) SP3 should be the first item listed. Thanks. Don Yantzi WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@ca.ibm.com "SamL" <lennon_s_j@hotma To: <wdsci-l@midrange.com> il.com> cc: Sent by: Subject: Re: [WDSCI-L] Lost Server Definition wdsci-l-admin@mid range.com 11/10/2002 05:24 PM Please respond to wdsci-l I thought I recollected someone losing a server. In my case I seem to have no problem adding my server back. It's just annoying, especially at a time when we're trying to introduce other programmers to the product. Maybe the more info we get on the problem the more chance IBM has of solving it. Sam ----- Original Message ----- From: "Reeve Fritchman" <reeve@ltl400.com> To: <wdsci-l@midrange.com> Sent: Saturday, November 09, 2002 5:38 PM Subject: RE: [WDSCI-L] Lost Server Definition > Sam, I posted a similar problem a month ago after screwing around for a > non-billable week trying to figure out my problem (can't use a named > server). I still have my library list even though I can't name a server > (regardless of what I enter, it shows up as an "OS400x"). > > I don't think IBM has addressed this problem; it has to be corruption in > some registry-type entries somewhere. I'm in "OS400A" and OS400B" server > purgatory myself... > > Regards, > Reeve > > -----Original Message----- > From: wdsci-l-admin@midrange.com [mailto:wdsci-l-admin@midrange.com]On > Behalf Of SamL > Sent: Friday, November 08, 2002 8:56 PM > To: wdsci-l@midrange.com > Subject: [WDSCI-L] Lost Server Definition > > I'm using WDSC 4.0, SP2 applied. I set up a server named SAML and > added a bunch of libraries to the library list. Used it for a > couple of days. > > This morning I started the Code Editor and clicked on a member from > the recently used files list in the File/Open dialog. It said > server SAML couldn't be found. > > I right clicked on the communications daemon and properties, and > sure enough there was no definition for SAML. > > I added it back, and my library list magically reappeared. Things > began working as expected. > > But why did my server vanish? > > I remember yesterday I brought up the daemon properties for > something. Seems like a couple of times it took an awfully long > time to dismiss. If fact, task manager told me it was consuming > 90+% of the CPU. Does it get lost or confused some times? I'm > running a 1.8 ghz P4 with 256mb and XP. > > Sam > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > To post a message email: WDSCI-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l > or email: WDSCI-L-request@midrange.com > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l > or email: WDSCI-L-request@midrange.com > 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l or email: WDSCI-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l or email: WDSCI-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l or email: WDSCI-L-request@midrange.com 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 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.