|
The combination does work but according to the SPD is not
supported (the SPD lists the valid VMS versions). This
means that if they encounter a problem, we can decide not
to fix it. If the problem they encounter has been fixed
in a newer release, then the response would be to upgrade.
The only version of ACMS that supports OpenVMS V6.2 is
ACMS V4.1, but with the problems we've encountered
with the CMA threads and the timer problem, we are
not encouraging anyone to upgrade to 4.1. Instead,
they should wait for ACMS V4.2 which is scheduled to
be submitted to SBB in a couple of weeks.
The chances of them encountering a new problem with 3.3B
is very remote, it's been out there for 5 or so years.
Bill
|
|
Our goal is to support those versions that prove to be the
best ones. ACMS 3.3B is a classic release that has enjoyed
the longest history of support (it even runs on OpenVMS VAX
7.1, although I've been the only one to try it). ACMS
V4.0 is somewhat of a mess with the ECO 1 and ECO 2
releases but it is still a very stable release. ACMS V4.1
has had some bad press, but only in that we tried to make it
easy to accomodate the CMA environment only to be bitten
by the dreaded timers. ACMS V4.2 has exorcised CMA from
the processes that don't use them (it's only brought into
CP under certain circumstances).
Things are going to change, though. We are being pressed to
support only the previous version and the current version.
Prior version ( current - 2 or more) will only be done on
a best effort. OpenVMS has the same policy, so you're going
to see more pressure to get customers to upgrade. It's
not going to be eas. ACMS customers are very reluctant
to upgrade when the version they have running meets
their needs. We still have lots of customers running
ACMS V3.3B and 4.0 and the ECOs. I'll bet there are
still lots of customers still running ACMS V3.2 (which
is still compatible with ACMS V4.2).
Bill
|