Re: How many sites still on V1.5 or earlier?

On Sun, 1 Apr 2007 18:37:42 +0000, Dave Salt <dsalt@xxxxxxxxxxx> wrote:

<snip>

The nice thing about having a single product version for all versions of the
operating system is that as customers upgrade their older systems, new
features become available 'automatically' without the customer having to
install newer versions of the product.

Dave, I think you are oversimplifying. Perhaps not an issue for the ISPF
product you support, but for software that has more dependencies and / or
hooks into the OS, this may not be a good option. You have to consider all
the multiple code paths, testing / verification of the code on lower level
systems and the cost associated with maintaining those lower level
systems in order to do that testing. I admit I don't like ISV products that
seem to require a version upgrade with every OS upgrade, but I can
understand why they might based on what I wrote above.


If a customer on an older system tries to do something they can't do, they
might see a message along the lines of "This feature requires z/OS version
1.x".

Cart? Horse? How would something written years ago warn about a new
feature not being available. Unless you are assuming the software involved
was kept up to date. And how could that happen "without the customer having
to install newer versions of the product."

But to me, this is no different than a customer wanting to take
advantage of new features in DB2 (or whatever); they obviously have to
install the new version of DB2 before they can use the new features.

Yes, but they also may have to install PTFs for supported versions to run at
all when the OS is upgraded and some older versions won't function period.

Regards,

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group: G-ITO
mailto:mark.zelden@xxxxxxxxxxxx
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • Re: Office 2007 Final setup issue
    ... I'm open Value customer and I'm logged on with my Passport account and trust ... But I have the install source here 100% sure of what I say ... ... I'm trying to upgrade to Office 2007 Final version. ... I check the proposed folder but it seems ...
    (microsoft.public.office.setup)
  • Re: Uupgrade to Server 2003 R2 AD
    ... DC to Server 2003 R2 you must prepare the forest schema using ADprep.exe ... use the R2 features you have to run AD prep from the second disk of the R2 ... set then you would install the R2 update on only the servers you want to use ... Upgrade to Win 2k3 or R2 at your leisure. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading Office X
    ... What would I like to see Microsoft do on the upgrade CD? ... I would actually pay another $25 just to see you provide a new CD ... >> requirement of keeping up with the additional CD install for the upgrade ... >second-tier features and software. ...
    (microsoft.public.mac.office)
  • Re: 2003 Enteprise SP2 or 2003 Enteprise R2
    ... that mean I can just insert the R2 #2 CD and install the features onto ... the R2 set and when it finished the install and rebooted it displayed ... to replicate data back here to our hub server. ... after the upgrade it will contain all the features as W2K3 R2? ...
    (microsoft.public.windows.server.general)
  • Re: 2003 Enteprise SP2 or 2003 Enteprise R2
    ... We use R2 for the updated DFSR features. ... to replicate data back here to our hub server. ... after the upgrade it will contain all the features as W2K3 R2? ... example) you install those update features on your Win 2k3 SP 1 servers ...
    (microsoft.public.windows.server.general)