Re: WDSCi 7.0 on Windows 7 64-bit

Sean,

I know you've received a couple other replies and perhaps I'm mistaken,
but IIRC the version of Eclipse on which WDSC 7.0 is based (3.2) does not
support 64-bit Windows. There were some fundamental libraries which were
never going to be ported at that level.

If I'm wrong and it can be installed on 64-bit, there's a page in the
midrange wiki at :
http://wiki.midrange.com/index.php/WDSC_installation_on_Windows_7

We, too, are still at V5R4M5 because of the licensing issues. There's
some good news on that. Last we checked, our BP can still get the
discounted "conversion" pricing from ADTS license seats to RDP. And the
maintenance on ADTS and all the individual compiler seats is all included
in the standard SWMA--only RDP seats require separate maintenance. That
helps some. I believe we're looking to upgrade to IBM i 7.1 sometime in
the next year or so.

First you'll want to download and install a recent version of Installation
Manager. I used version 1.4.2. The latest version (1.5.1) is available
at
http://www-01.ibm.com/support/docview.wss?uid=swg24031048&myns=swgrat&mynp=OCSSDV2W&mync=E
Here's a shorter link: http://tinyurl.com/7974mgn

Disclaimer: I have not installed using that version. YMMV.

Anyway if I recall correctly again, you have to install with the package
from the download link at the bottom of the wiki page. I believe there is
something different in that package which will unofficially allow you to
install on Windows 7. Perhaps I should update the page, but it's been a
while since I had to do an install so I could be wrong. I did *NOT*
install to the default directories. I believe there were some optional
components I could not get to install correctly, but I do have a basic
edit, compile, test installation working on Win 7. And I do not run it in
XP mode or as XP compatible. (Note: I do see some odd behavior from time
to time, but it works about 99% of the time. I attribute these oddities
to Windows 7 incompatibilities, but I could be wrong.)

Again, YMMV--good luck!

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/04/2012 01:00:10 PM:

----- Message from "Porterfield, Sean"
<SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx> on Wed, 4 Jan 2012 11:50:46 -0500

-----

To:

"wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] WDSCi 7.0 on Windows 7 64-bit

We're still on i5/OS V5R4M5, so we haven't dealt with the licensing
issue to get the newer RDi/RDP/etc. I'm trying to get WDSCi 7.0
working in the mean time.

I installed the IBM Installation Manager and WDSCi 7.0 from the
discs I have. The first time, I tried installing with updates, but
that failed miserably. I forget the details...

I went through a second time and just installed the base version.
No obvious problems during installation. I then created an iSeries
connection and some source filters. When I expand the source
filter, I get an error: Connection to x.x.x.x could not be
established. An unknown error occurred connecting to x.x.x.x.
Check if you have connection to the host. If the connection is not
broken, check that TCP/IP is configured correctly on the local
machine and all host servers are started on x.x.x.x.

That's not very helpful. I get the same result whether I run as
myself or as administrator, so I don't think it's a permission
issue. It still works on my old computer, so I know it's not a server

issue.

I thought maybe it was because I just installed the base version,
and the old computer has 7.0.0.8 (I think; I can't find that version
number.) I downloaded the 7.0.0.8 patch, extracted it, added it to
the Installation Manager repositories. I've tried with Update
Packages and Install Packages, but it won't install. It shows up on
the list for Install Packages, but nothing happens when I check the
box and click Next. I get the same nothing when I check for updates
in Update Packages.

The really odd thing is sometimes my member list expands to show
members, even though I still get the connection error. That means
it must have connected at some point.

My Installation Manager is version 1.0, and I was unable to find an
update applicable to that version.

Any thoughts on how to fix this? (Other than purchase the new version.)
--
Sean Porterfield