SamL | 1 Oct 03:03 2002
Picon

Re: WDSCi V5 available ?

Well, on this page http://www-3.ibm.com/software/ad/wds400/news/
the second bullet says:

WebSphere Development Studio for iSeries, Version 5 Release 2 Now
Available!
WebSphere Development Studio for iSeries, Version 5 Release 2
became available on August 30, 2002. The product includes both host
and workstation components. The workstation components are bundled
as WebSphere Development Studio Client for iSeries. See the IBM
WebSphere Development Studio for iSeries, Version 5 Release 2 Fact
Sheet (139KB) for more information.

I'm not exactly sure what this means.  Seems like only yesterday
that Version 4 was released.  Has IBM changed the numbering yet
again?

Sam

----- Original Message -----
From: <paul.nicolay@...>
To: <wdsci-l@...>
Sent: Monday, September 30, 2002 10:57 AM
Subject: [WDSCI-L] WDSCi V5 available ?

> Hi,
>
> I just read an article about "Websphere Studio Version 5" and it
also mentions "Eclipse 2.0" (see
http://www.e-ProMag.com/article.cfm?ID=2651).
_______________________________________________
(Continue reading)

Vernon Hamberg | 1 Oct 04:53 2002
Picon

Re: WDSCi V5 available ?

I'm betting that this is the host part, not the client. It's the new client
that is at version 4. WebSphere Development Studio has been around under
that name for a couple releases, anyway.

This is worse than Client Access - at least there, the host and client
parts have distinct enough names!

Vern

At 09:03 PM 9/30/02 -0400, you wrote:
>Well, on this page http://www-3.ibm.com/software/ad/wds400/news/
>the second bullet says:
>
>WebSphere Development Studio for iSeries, Version 5 Release 2 Now
>Available!
>WebSphere Development Studio for iSeries, Version 5 Release 2
>became available on August 30, 2002. The product includes both host
>and workstation components. The workstation components are bundled
>as WebSphere Development Studio Client for iSeries. See the IBM
>WebSphere Development Studio for iSeries, Version 5 Release 2 Fact
>Sheet (139KB) for more information.
>
>I'm not exactly sure what this means.  Seems like only yesterday
>that Version 4 was released.  Has IBM changed the numbering yet
>again?
>
>Sam

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) mailing list
(Continue reading)

coulthar | 1 Oct 05:01 2002
Picon

WDS, WDSC, 4.0 v 5.0, Eclipse 1.0 vs 2.0

I think what we need is a wizard to understand our naming and numbering
strategy :-)

Let me "try" to help, but I can understand that this is all very
confusing... ironically, we
are all this "rebranding" with the intent to make all this easier ... a
single family
name (WebSphere Studio xxx) and numbering scheme (tied to WAS). Please, no
comments from the peanut gallery, just repeat after me: "it is good. it is
good" :-)

Ok, ready? Here goes...

WDSC 4.0 is the client tools package. It remains the state of the art...
ie, it is our
current release of client-based tools for iSeries.

You can get WDSC 4.0 by buying it, or as is normally the case, as an
entitlement
when you by the overall package WDS ... this is the host package that
includes
the compilers, classic ADTS tools and entitlement to unlimited licenses of
WDSC.
This being an iSeries program product released in synch with OS/400, it is
numbered
with OS/400. So, when V5R2 of OS/400 went out on Aug 30th, a new release of
WDS
V5R2 went out. For the host, there are updated versions of all the
compilers.

(Continue reading)

Bill Layman | 2 Oct 17:45 2002

Distributed Debugger

The debugger will not let me sign on. I have WDSc 4.0 on a win98se
computer. When i try to get a job list i get the popup box to login I
type my AS400 user and password, it comes back with an error "LOGON
FAILED. CHECK YOUR USERID AND PASSWORD AND TRY AGAIN." I checked and i
have all the Authorities that the help said i needed. The AS400 is at
v5r1. Anybody have this happen? It does this if i'm in code and start it
or from the stand alone option or a command line. Thanks.

    Bill

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) mailing list
To post a message email: WDSCI-L@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or email: WDSCI-L-request@...
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

craigs | 2 Oct 21:16 2002

Re: WDSCI causing InstallShield problem on XP


The techie gave me some more information on this but I had not gotten
around to posting yet.  I'm sorry for the delay Howard.  I cannot find out
the version of the Palm Desktop right now.  I don't think we should be
focusing on the PalmPilot but only WDSC and Lotus Notes on Windows XP.  I
say that because the techies searched every way they could think of for
Lotus Notes in the registry but could not find it.  Uninstalling Lotus
Notes and then installing Lotus Notes allowed them to search and find Lotus
Notes in the registry.  I think this is an issue that could affect anything
that relies on finding Lotus Notes in the registry.  I thought the techie
said they found research that would show that WDSC would cause a registry
problem with Lotus Notes, but it was just about how WDSC hacks up the
registry.  This led them to their hypothesis.  They said that someone
higher up asked them later if they had checked for Lotus Notes in the
registry before installing WDSC and they said no.  The person said that it
could be a fluke that has been known to happen sometimes.

My thought on this is, someone should try installing Lotus Notes then WDSC
on a PC with Windows XP.  Try finding Lotus Notes in the registry.
1. If you can find Lotus Notes in the registry, I would be very sure in
saying that this is probably a random fluke.
2. If you cannot find Lotus Notes in the registry, uninstall Lotus Notes
and then install Lotus Notes.  Look for Lotus Notes in the registry and you
should find it.  Not being able to find Lotus Notes probably means WDSC is
causing a registry problem but that is just my opinion.

I am comfortable in assuming that this was a random fluke but this should
probably still be there in our minds in case this happens to someone else.
Since you don't think WDSC changes the registry of Lotus Notes, I am
assuming WDSC is okay and it was just a random fluke.  If you want to test
(Continue reading)

howardl | 2 Oct 22:22 2002
Picon

Re: WDSCI causing InstallShield problem on XP

I tried the following but was unable to reproduce the problem.
1. Install WinXP Pro.
2. Apply WinXP SP1.
3. Install Notes client 5.0.11
4. Install WDSC v4.0

The following lotus notes' registries still exist without any
modifications.

[HKEY_LOCAL_MACHINE\SOFTWARE\Lotus]

[HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Components]

[HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Components\LotusScriptExtensions]

[HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Components\LotusScriptExtensions\2.0]
"Notes"="C:\\Lotus\\Notes\\nlsxbe.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Components\TeamMail]
"Description"="TeamMail Mail Enabling dll"
"Version"="1.0"
"KeyPath"="SOFTWARE\\Lotus\\Notes\\5.0"
"Application"="Notes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes]
"Description"="Lotus Notes"
"Path"="C:\\Lotus\\Notes\\"
"DataPath"="C:\\Lotus\\Notes\\Data\\"
"Name"="notes.exe"

(Continue reading)

yantzi | 3 Oct 18:39 2002
Picon

Re: Distributed Debugger

From the Debugger Team here at the lab:

The debugger in WDSC V4.0 has been changed to support long passwords and
startup when the workstation has more than one IP address.This support
requires an iSeries PTF. For V5R1 it is PTF SI03087, for V4R5 it is
SF67175.

Don Yantzi
WebSphere Development Studio Client for iSeries
IBM Toronto Lab

|---------+---------------------------->
|         |           Bill Layman      |
|         |           <blayman <at> tsomervi|
|         |           lle.com>         |
|         |           Sent by:         |
|         |           wdsci-l-admin <at> mid|
|         |           range.com        |
|         |                            |
|         |                            |
|         |           10/02/2002 11:45 |
|         |           AM               |
|         |           Please respond to|
|         |           wdsci-l          |
|         |                            |
|---------+---------------------------->
  >-------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                               |
  |       To:       "WDSCI-L@..." <WDSCI-L <at> midrange.com>                                                                 |
  |       cc:                                                                                                                     |
(Continue reading)

Westdorp, Tom | 3 Oct 20:41 2002

re: My servers have vanished...

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
On Sept 1 Reeve Fritchman reported that:
>I've had a couple of defined servers (TTG, TTGBNA, VOLT, etc.) for CODE
>running under WDSC 4.0 with the recent SP on Win2000 for months.  They
>worked yesterday at 1900.
>
>Today I show up and try to use my default server, TTG.  "Not
> found"...interesting.  So I check the communications console and find my
>servers are now OS400A, OS400B, and so on.  They work (i.e. I can get
>through to the server)...
>
>I'd like to use my friendly names but renaming the servers hasn't worked:
>EVFCSVRD.exe blows up when I rename and click for the PTF check.  If I
don't
>check to PTF's, EVFCSVRD.exe closes normally but the OS400* names are back
>when I open the comm. console again.  I've deleted the OS400* servers,
>rebooted, added them back, rebooted, sacrificed a chicken, all to no avail.

Late yesterday the same thing happened on my ThinkPad running WDSc 4.0 + FP2
on WinXP + SP1.  It had been working fine, just as Reeve's, in fact the MRU
file list referred to the correct server names and trying to reference an
entry on the MRU files list fails because of the server name change.  I'm in
one chicken, plus Reeve's one... No Joy.  There's an egg shortage looming.
I get the same error on the ptf check, even though I've run it successfully
many times in the recent past.

Any ideas?  I'm only using Code at this point, no designer, no projects, no
(Continue reading)

Reeve Fritchman | 7 Oct 19:57 2002

Library list problems

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
VERIFY isn’t working; it can’t find any files after I juggled my iSeries
library lists (from V36 to V37) over the weekend.  The files are now in V37
but not in V36; the program(s) compile properly on the green-screen side in
V37.

I’ve changed everything application-wise on the iSeries I need to, including
job descriptions and startup programs (QUSRLIBL isn’t used).  I’ve changed
my CODE autostart server library list, cleared the cache, and deleted the
CODE user spaces in my current library.  The QUSRWRK jobs that appear to be
handling VERIFY tasks shows the right library list (V37) but the VERIFY
listing shows all V36 files and objects.

Then…*inspiration*: the library list is buried (like everything else)
somewhere in WDSC.  But I don’t seem to have a connection defined to my
iSeries.  So I create a connection to my box, go through the steps, and a
connection is created…but the connection has the wrong (old) library list,
meaning there’s something hidden somewhere in WDSC.

Now, I’m looking at the Server|iSeries Objects|Default Filter Pool|Library
list and haven’t a clue how to change this “filter”.  I’ve double-clicked,
right-clicked, and “Properties”’ed it for the last 30 minutes and remain
baffled.

Can anybody set me straight?

Thanks,
Reeve
(Continue reading)

Dave Boettcher | 7 Oct 20:08 2002
Picon
Picon

RE: Library list problems

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
It seems that when we went through this something had to be re-booted.  I
don't remember if it was the iSeries or the PC.

HTH

Dave Boettcher

-----Original Message-----
From: Reeve Fritchman [mailto:reeve@...]
Sent: Monday, October 07, 2002 12:58 PM
To: Wdsci-L <at> Midrange. Com
Subject: [WDSCI-L] Library list problems

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
VERIFY isn't working; it can't find any files after I juggled my iSeries
library lists (from V36 to V37) over the weekend.  The files are now in V37
but not in V36; the program(s) compile properly on the green-screen side in
V37.

I've changed everything application-wise on the iSeries I need to, including
job descriptions and startup programs (QUSRLIBL isn't used).  I've changed
my CODE autostart server library list, cleared the cache, and deleted the
CODE user spaces in my current library.  The QUSRWRK jobs that appear to be
handling VERIFY tasks shows the right library list (V37) but the VERIFY
(Continue reading)


Gmane