Current Product Versions
| Product | Versions, Support-Until * |
| VitalSigns for Network Automation & Control | 1.1.3 current |
| VitalSigns for IP | 7.1.9 current; 7.0 indefinitely. For zOS/1.11, get 7.1.2+. For z/OS 1.12, get 7.1.8+ 5.0 & 6.0 discontinued. |
| VitalSigns for VTAM | 5.1.4 current; 5.1 indefinitely For z/OS 1.11, ask SDS for a software “zap” for VSV 5.1.3 or 5.1.4 |
| VitalSigns for FTP | 2.0.1 current; 1.0 indefinitely |
| SMART TS XL | —- |
| DynaPrint/MVS | 1.6a current; 1.6 indefinitely |
| DynaPrint/VSE | 1.6a current; 1.6 indefinitely |
| IPCP Plus/MVS | 4.6a current; 4.6 indefinitely z/OS 1.10+ requires v4.6a, put level 0801 |
| IPCP Plus/VSE | 4.4a current; 4.4 indefinitely |
| Maxback/VM | 1.1.3 current; 1.1 indefinitely |
| Maxback/VSE | 2.2.16 current; 2.2.15 indefinitely; 2.2.14 discontinued |
| MultiPrint/VM | 3.1.1 current, indefinitely |
| MultiTerm/MVS | 2.6.6 current, indefintely; 2.6.5 indefinitely |
| MultiTerm/GCS | 2.6.5 current, indefinitely |
| MultiTerm/VSE | 2.6.5 current, indefinitely |
| MultiTerm/VM | 5.4.3 current, indefinitely |
| MultiTerm/VM CMS Access Option | 5.4.3 current, indefinitely |
| OHF/MVS: Online Help Facility for MVS | 4.0.3 current; 4.0 indefinitely CICS/TS v3.1+ requires OHF v4.0 |
| OHF/VSE: Online Help Facility for VSE | 3.8.0 current, indefinitely |
| PC Workmate | 3.5a current; 3.5 indefinitely |
| Powertools Plus/VSE | 3.5a current; 3.5 indefinitely |
| SmartMail/MVS | 2.0A current; 2.0 indefinitely; 1.4 indefinitely |
| SmartMail/VSE | 1.4 current, indefinitely |
| Stash/MVS | 3.3a current; 3.3 indefinitely |
| Stash/VM | 3.3a current; 3.3 indefinitely |
| Stash/VSE | 3.2a current; 3.2 indefinitely |
| SuperDirectory/VSE | 0.1c current, indefinitely |
| SuperSender/MVS | 2.0 current, indefinitely |
| SuperSender/VSE | 1.4a current; 1.4 indefinitely |
| VSV/GCS: VitalSigns for GCS | 4.2.1 current, indefinitely |
| VSV/VSE: VitalSigns for VSE | 4.2.1 current, indefinitely |
| VS/VM: VitalSigns for VM | 4.4.3 current, indefinitely; 4.4.0 indefinitely; 4.3.3 indefinitely |
*Policy: Duration of Support for Older Software Versions
The seperate generations of SDS products are identified in the form v.r.m, where v is the version number, r is the release number, and m is the modification level. Note that the policy listed below speaks of the release, not the version or modification.
Software Diversified Services provides technical support for the current release level and a limited number of previous release levels of our software products, as follows:
Current (v.r.m) releases will be supported indefinitely. Their support status changes when they are supplanted by a new release. Or when a product is discontinued. SDS will provide one-year’s notice before discontinuing a product.
Current-1 (v.r-1.m) releases, i.e. releases immediately prior to current releases, are supported indefinitely, or until the expiration date specified above. Expiration dates are entirely at SDS’ discretion. But SDS will always set expiration dates with at least one-year lead time. In other words, if SDS first publishes an expiration date today, that expiration date will be no sooner than one year from today.
Current-2 (v.r-2.m) releases, i.e. releases that have twice been supplanted by newer ones, will be supported for at-least one (1) year and typically no longer than one (1) year beyond the generally available release date of the current release. Extension of support beyond that limit for any particular release is at Software Diversified Services’ discretion alone.
For purposes of this policy, the end-of-support dates are those listed at the URL http://www.sdsusa.com/support/table
After support for a given product release has expired, SDS will provide technical support on a “best-effort” basis: Maintenance created while the release was supported will remain available to customers with up-to-date maintenance contracts. And SDS will respond to support questions. But no new maintenance or fixes will be developed once a release-level has left supported status. Users of such software are encouraged to upgrade to the latest version/release.
This policy was instituted in December 2007 and honors a one-year grace period—hence a large number of releases left support in December 2008.