Lukas,

You said:

... We're an IBM Premier Level BP. ...
... Even if it we could have access to prerelease Versions of V6R1,...

Have you tried Virtual Loaner program? You could get access to an LPAR for
testing (I haven't asked them for V6R1, but I don't see why they couldn't
provide it).

You said:

We bought an IBM System x3250 for this purpose. Runs well.

So it's ok to buy a PC for testing but not a System i?

Tested everything. Testing Vista was a breeze to.
We just needed a normal PC.
Is testing on System i less of a breeze?
In my experience, IBM makes every possible effort not to break backward
compatibility, result being vendor software that most of the time doesn't
require any changes to run on new release. This has not been my experience
with Microsoft. Actually, I don't understand the windows vendor culture
that doesn't resist incompatibilities in new versions of Windows. I take
that back, I understand it. It forces the customer to upgrade... oh well.

I work for a vendor in US and while I can see that European vendor would
have more challenges, I don't think they're insurmountable.
Perhaps you should charge more for your System i software? I mean, if it
costs more to develop and test, why not? Seems reasonable to me, of course
if market can bear it.
If not, they'll have to be wait for you to test it when you get to it :(

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i5/OS and OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Re: V6R1

On Feb 8, 2008 6:13 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
At least IBM's better than Microsloth, which has a long-established
habit of intentionally and maliciously treating third-party software
vendors like mushrooms (i.e., keeping them in the dark and feeding them
a lot of . . . ).

I heavily disagree with you. Our Server Software runs on the System i,
the Client runs on Windows Systems.

We're an IBM Premier Level BP.

We don't have ANY possibility to test our Software on V6R1. None.
Zilch. Nada. Only for specially privileged people in the US. ANZOBJCVN
on non-#2929 systems took HALF A YEAR to come out after the #2929
version, leaving us with only a redbook that specified PTFs for OS
versions we don't use or support.

After the PTFs were finally out, we still didn't have any possibility
to actually test our software on V6R1.

Even if it we could have access to prerelease Versions of V6R1,
testing them would be very expensive. We'd need to buy a seperate
Model 515 just to be able to run V6R1 (we don't have any Big Beef
machines like others on thist lis)

Not so with Microsoft. As a normal "Microsoft Partner", we had access
to Windows Vista Betas/RCs for several years leading up to the
release. With each new Beta, we verified that our Client Software
still worked as intended, fixed any issues that cropped up, and when
Vista was finally released in November 06 for Companies, we just
installed our software, ran our test suite, and voila: We we're ready
for the Windows Vista GA in Jan 07.

The same thing happened with Windows Server 2008. We support our
Software running in Terminal Server Environments. Again, we had the
same experience as with Vista. As the difference between WS2008 and
Vista weren't as big as between XP and Vista, we didn't encounter any
problems. Now, Windows Server 2008 was available for us again, 30 days
before GA. We can now say confidently that our software works
correctly on Windows Server 2008.

Testing WS2008 was a breeze. We just needed an EMT64 capable Intel CPU
and a few disks. We bought an IBM System x3250 for this purpose. Runs
well. Tested everything. Testing Vista was a breeze to. We just needed
a normal PC.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.