| Title: | ACMS comments and questions |
| Notice: | This is not an official software support channel. Kits 5.* |
| Moderator: | CLUSTA::HALL AN |
| Created: | Mon Feb 17 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4179 |
| Total number of notes: | 15091 |
There has been an open call for some time asking the following
question.
"our goal is to upgrade the production cluster in
our Data Center with ACMS v4.1 and keep our 100+ remote sites running
ACMS v3.2."
My gut feeling is that the ACC's will still communicate with one
another but I do not want to base a response on an assumption. The SPD
for 4.1 makes no claims to backward compatibility to 3.2. I would like
to close this call ASAP. Any pointers/answer appreciated.
Dave...
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4128.1 | ACMS::HALL | Bill Hall - ACMS Engineering - ZKO2-2 | Tue Mar 18 1997 15:01 | 27 | |
First, ACMS V3.2 is no longer supported although it will still
work.
The ACMS V4.0 release notes state:
When using ACMS Version 4.0 in a distributed environment,
all the nodes in the configuration must be using ACMS
Version 3.2 or greater. Any combination of ACMS Version
3.2, ACMS Version 3.3, ACMS Version 3.3B, or ACMS Version
4.0 nodes is supported. For example, you could have a
distributed ACMS configuration of three nodes where two
submitter nodes are running ACMS Version 3.3 on OpenVMS
VAX and an application node running ACMS Version 4.0 on
OpenVMS AXP.
The release notes are not a legal document so if they run into any
problems, we are under no obligation to fix them in the release they
are using.
I'd also stay away from ACMS V4.1 because of the CMA problems we've
seen. They are better off waiting until ACMS V4.2 (w/o CMA) is
available later this spring.
Bill
| |||||