| Title: | BASEstar Classic |
| Notice: | BASEstar Classic Kit Listings in Note 1407.* |
| Moderator: | BASEX::EISENBRAUN |
| Created: | Mon Jan 19 1987 |
| Last Modified: | Thu May 15 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1566 |
| Total number of notes: | 6666 |
Hi ! Is it possible/supported, to run BASEstar/Classic V3.3 and V3.4 within the same domain ? (I don't think so.) One of our customers tried to do a "BS SHO POINT <V3.3_system>::*" from a system running V3.4. The result was, that BCC$DISPATCHER on the target (V3.3) system did crash with a "decimal overflow" error. I also remember a 6000-byte limitation on accessing remote data structures, mentioned in the V3.4 release notes. - Thanks & regards, Tom.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1555.1 | Can't run V3.3 and V3.4 in the same domain. | BASEX::EISENBRAUN | John Eisenbraun | Mon Jan 27 1997 08:04 | 9 |
>Is it possible/supported, to run BASEstar/Classic V3.3 and V3.4 within the same
>domain ? (I don't think so.)
NO. Absolutely not. Internal data structures in V3.4 were changed
which prevent interoperablity with prior versions.
However, applications written for V3.3 will run on V3.4 without any
changes (or recompiling/relinking).
| |||||
| 1555.2 | DASes must be rebuilt | CAM::JOHNSON | imagine... sharing all the world | Tue Jan 28 1997 07:36 | 8 |
>> However, applications written for V3.3 will run on V3.4 without any >> changes (or recompiling/relinking). NOT including DASes... every DAS (custom, or done by Digital) must be re-compiled and re-linked for V3.4... make sure you have V3.4 DASes... FYI, the release notes have a section on the fact that V3.3 and V3.4 can not operate in the same domain... | |||||