July 22, 2008
Dear Valued Sybase Customer:
This letter provides notification of the end of engineering support for the following versions of Sybase product(s).
|
Product |
Version | Platform | Language | End ofEngineeringSupport | Migration Path | Comments |
| EAServer Developer, IBM-AIX | 4.x | IBM-AIX | English | 7/22/09 | EAServer Developer IBM-AIX 5.x or earlier | See Entitlement A below |
| EAServer Developer Academic, IBM-AIX | 4.x | IBM-AIX | English | 7/22/09 | EAServer Developer IBM-AIX 5.x or earlier | See Entitlement A below |
| EAServer Deploy Advanced CPU IBM-AIX | 4.x | IBM-AIX | English | 7/22/09 | EAServer Advanced CPU IBM-AIX 5.x or earlier | See Entitlement A below |
| EAServer Deployment Adv, concurrent IBM-AIX | 4.x | IBM-AIX | English | 7/22/09 | EAServer Advanced CPU IBM-AIX 5.x or earlier | See Entitlement A below |
| EAServer Deploy Enterprise CPU AIX | 4.x | IBM-AIX | English | 7/22/09 | EAServer Advanced CPU IBM-AIX 5.x or earlier | See Entitlement A below |
| EASvr Deploy Enterprise concurrent IBM-AIX | 4.x | IBM-AIX | English | 7/22/09 | EAServer Advanced CPU IBM-AIX 5.x or earlier | See Entitlement A below |
| EAServer Developer, HP-UX | 4.x | HP-UX | English | 7/22/09 | EAServer Developer HPItan 5.x or earlier | See Entitlement A below |
| EAServer Developer Academic, HP-UX | 4.x | HP-UX | English | 7/22/09 | EAServer Developer HPItan 5.x or earlier | See Entitlement A below |
| EAServer Deploy Advanced CPU HP-UX | 4.x | HP-UX | English | 7/22/09 | EAServer Advanced CPU HPItan 5.x or earlier | See Entitlement A below |
| EAServer Deployment Adv, concurrent HP-UX | 4.x | HP-UX | English | 7/22/09 | EAServer Advanced CPU HPItan 5.x or earlier | See Entitlement A below |
| EAServer DeployEnterprise CPU HP-UX | 4.x | HP-UX | English | 7/22/09 | EAServer Advanced CPU HPItan 5.x or earlier | See Entitlement A below |
| EASvr Deploy Enterprise concurrent HP-UX | 4.x | HP-UX | English | 7/22/09 | EAServer Advanced CPU HPItan 5.x or earlier | See Entitlement A below |
| EAServer Developer, Windows | 4.x | Windows | English | 7/22/09 | EAServer Developer 5.x or earlier | See Entitlement A below |
| EAServer Developer Academic, Win | 4.x | Windows | English | 7/22/09 | EAServer Developer 5.x or earlier | See Entitlement A below |
| EAServer Deployment Sm Business, Win | 4.x | Windows | English | 7/22/09 | EAServer Workgroup, Windows 5.x or earlier | See Entitlement A below |
| EAServer Deploy Advanced, Win CPU | 4.x | Windows | English | 7/22/09 | EAServer Deploy Advanced,Win CPU 5.x or earlier | See Entitlement A below |
| EAServer Deployment Advanced, Win | 4.x | Windows | English | 7/22/09 | EAServer Deploy Advanced, Win CPU 5.x or earlier | See Entitlement A below |
| EAServer Deploy Enterprise, WIN Cpu | 4.x | Windows | English | 7/22/09 | EAServer Deploy Advanced, Win CPU 5.x or earlier | See Entitlement A below |
| EASvr Deploy Enterprise, Win | 4.x | Windows | English | 7/22/09 | EAServer Deploy Advanced, Win CPU 5.x or earlier | See Entitlement A below |
| EAServer Developer, Solaris | 4.x | Solaris | English | 7/22/09 | EAServer Developer, Solaris 5.x or earlier | See Entitlement A below |
| EAServer Dev Academic, Solaris | 4.x | Solaris | English | 7/22/09 | EAServer Developer, Solaris 5.x or earlier | See Entitlement A below |
| EAServer Deploy Sm Business, Solaris | 4.x | Solaris | English | 7/22/09 | EAServer Workgroup, Solaris 5.x or earlier | See Entitlement A below |
| EAServer Deploy Advancd, Solaris CPU | 4.x | Solaris | English | 7/22/09 | Easerver Advanced Sol SPARC 5.x or earlier | See Entitlement A below |
| EAServer Deployment Advanced, Sol | 4.x | Solaris | English | 7/22/09 | Easerver Advanced Sol SPARC 5.xor earlier | See Entitlement A below |
| EAServer Deploy Enterprise, Sol CPU | 4.x | Solaris | English | 7/22/09 | Easerver Advanced Sol SPARC 5.x or earlier | See Entitlement A below |
| EASvr Deploy Enterprise, Solaris | 4.x | Solaris | English | 7/22/09 | Easerver Advanced Sol SPARC 5.x or earlier | See Entitlement A below |
| EAServer Developer, LINUX | 4.x | Linux | English | 7/22/09 | EAServer for Linux Developer 5.x or earlier | See Entitlement A below |
| EAServer Developer Academic, LINUX | 4.x | Linux | English | 7/22/09 | EAServer for Linux Developer 5.x or earlier | See Entitlement A below |
| EAServer Deploy Advanced CPU LINUX | 4.x | Linux | English | 7/22/09 | EAServer Deploy Adv Linux CPU 5.x or earlier | See Entitlement A below |
| EAServer Deployment Adv, concurrent LINUX | 4.x | Linux | English | 7/22/09 | EAServer Deploy Adv Linux CPU | See Entitlement A below |
| EAServer Deploy Enterprise CPU LINUX | 4.x | Linux | English | 7/22/09 | EAServer Deploy Adv Linux CPU | See Entitlement A below |
| EASvr Deploy Enterprise concurrent LINUX | 4.x | Linux | English | 7/22/09 | EAServer Deploy Adv Linux CPU | See Entitlement A below |
| USP EAServer Deploy Sm Business Win | 4.x | Windows | English | 7/22/09 | Support Plan | See Entitlement A below |
| USP EAServer DeploySm Business Sol | 4.x | Solaris | English | 7/22/09 | Support Plan | See Entitlement A below |
Entitlement A:
EAServer 4.x customers are entitled to migrate to EAServer 5.x or later subject to the following:
EAServer 4.x is licensed per Server, unlike EAServer 5.x and later which are licensed on a CPU basis. Customers who migrate from EAServer 4.x to EAServer 5.x or later will receive a “one-to-one” Server to CPU conversion entitlement. Specifically, customers who migrate to EAServer 5.x or later shall receive a license entitlement of one (1) CPU for each valid Server license purchased by the customer for EAServer 4.x.
CPU and Related Definitions:
“Core” is a functional unit within a computing device that interprets and executes software instructions.
“CPU” is the unit of measurement used in the CPU License type (see “CPU License”). The number of CPUs is equal to the number of Processors or Cores on a Machine.
“CPU License” is the limited right to install the Program on a Machine on which the number of CPUs is no greater than the number of licenses purchased. The number of Seats that may access the Program shall be limited only by the capacity of the licensed CPUs, and may include internal usage by Seats within the customer’s organization, and external usage by Seats outside of the customer’s organization accessing the Program via the Internet (“Internet Users”). Internet Users may not Use the Program to develop or modify applications or perform other programming tasks, and may only Use the Program in conjunction with customer’s applications. The license fee payable by customer for each copy of the Program installed on a Machine shall be determined by multiplying the number of CPUs on the Machine by the applicable rate as specified in an Order. In the event that the number of CPUs on the Machine is increased, customer shall report such increase, execute a new Exhibit A and pay an additional amount determined by multiplying the incremental CPUs by the then applicable rate per CPU set forth in the Price List.
"Machine" – A single computer hardware system identified on the applicable Order running a single copy of the Operating System Software.
“Networked License” – The limited right for the number of Seats equal to the quantity of such licenses purchased, as specified in the Order, to directly or indirectly access a Program installed on a licensed Server or Servers in a single network.
"Operating System Software" - The operating system software on which the Program is licensed to be Used, as specified on the Order.
“Order” – A Purchase Order or Exhibit A signed by customer and accepted by Sybase.
"Price List" - Sybase’s then current price list for the country in which the Program is to be installed.
“Processor” means “Core”.
"Program" -The object code version of the software product(s) listed in the Order, as well as any and all Updates and authorized copies. Although the Program media may contain other software products, customer is licensed to install and Use only the designated Program.
"Purchase Order" - A purchase order or other purchase-authorizing document issued by Customer for Sybase products and/or services and accepted by Sybase, as confirmed by a Sybase invoice.
"Seat", or “ST” - A specific, identifiable, unique input/output device capable of directly or indirectly accessing and using a Program such as (without limitation) a terminal, personal computer, single user workstation, personal digital assistant (“PDA”), wireless device or real time device. See “Networked License”.
“Server” – A computer containing software, which permits it to await and fulfill services to other computers.
"Use" – means to install, load, view, print, update, access, utilize, or store the Program.
Sybase encourages you to begin migration plans as soon as possible to upgrade your software before the end of engineering support to the supported version identified in the "Migration Path" column as shown in the table above.
For customers having a current Support Agreement who have elected not to migrate to a supported release by the end of engineering support, continued limited technical support assistance will be made available, subject to the availability of resources. This limited assistance after the end of engineering support consists of providing existing interim releases (i.e., updates, if any, developed for the product prior to the end of engineering support), telephone and electronic assistance, and migration advice to customers upgrading to Sybase supported products. It does not include engineering support, new bug fixes or integration of any bug fixes into previous updates. If you have any questions, please call your local Sybase Technical Support Center. One of our Customer Service representatives will respond to your questions or direct your call to someone who can.
For the number of your closest Technical Support Center, please go to: www.sybase.com/contactus/support. Thank you for your cooperation in this product transition. We are very excited about the new product releases and look forward to helping you to deploy and get the most out of them.
Sincerely,
Loren Corbridge
Senior Product Manager, PTO
Sybase, Inc.

Back to Top