derstad@CIM-VAX.HONEYWELL.COM ("DAVE ERSTAD") (07/11/89)
This is being cross-posted to dsee-list and info-apollo; I'm
not sure if the membership is a complete overlap.
Here's a laundry list of DSEE problems Apollo didn't tell you about...
(Or at least didn't tell *me* about). Most are various version
compatibility problems.
1) DSEE 3.2.1 is supposed to be compatible with SR9.7 or later.
Actually, you need SR9.7.0.4 or later. If you are running 9.7.0.3,
the D3M server will abort with a message telling you that the
node is not at 9.7 or later. This is due to some naming
call added at 9.7.0.4 which needs to be present.
2) DSEE 3.3.1 does not appear to be as compatible with 3.2.1 as
advertised. Specifically, we have found that if one has a
DSEE shell node at 9.7
DSEE builder node at 10.0
DSEE reference node at 9.7
OR
DSEE shell node at 10.0
DSEE builder node at 9.7
DSEE reference node at 9.7
then DSEE is sometimes (possibly always; I just can't prove/disprove
that) unable to locate derived objects from previous builds
for use in current builds (our specific derived objects are insert
files for Pascal applications).
This is not a case sensitivity problem, and we do have DOWNCASE
set in the ENVIRONMENT section. It should be noted that this
problem disappears with DSEE 3.3.2.p, and presumably with DSEE
3.3.2 although we don't have that yet.
3) The compiled models used by 3.3.2.p are not compatible with
3.2.1. Presumably, this also means 3.3.2 is not compatible
with 3.2.1, although again we haven't verified that.
Dave Erstad
Principal DA Engineer
Honeywell SSEC