Tru64 Managers:
Thanks for the replies from several people who responded. Here's a summary:
- CFX and ABAQUS runs on v5.0 (one respondent)
- FIELDVIEW 7: Vendor reports that the Supported version is version 4.0.
"Should function" under Tru64 Unix versions 5.0 and 5.1. Japanese
distributor of app reported running successfully on Tru64 5.1.
- Tru64 V5 -- new file system and device names. Applications expecting
/dev/rz23c will see /dev/disk/dsk23 instead
- Most applications that run under v4.x will NOT run under 5.x (especially
5.1) without re-writes.
Some additional comments from << alan at nabeth.cxo.dec.com >>
- In the SPD (Software Product Description), there should be a general
statement about upward compatibility. It will have exceptions attached to
it, but it will basically say that anything compiled and linked on a
previous version will continue to run on later versions. The usual
exceptions are:
o Programs that take advantage of undocumented and thus
unsupported behaviour of the system may find that
bug/feature fixed/broken in a future release. For
example, don't depend on the internal implementation
of malloc and family to remain constant across versions.
o Programs that depend on kernel data structures accessed
through undocumented and thus unsupported interfaces
shouldn't expect to have those interfaces remain
constant across major versions. Even across minor
versions changes can happen. For example, performance
monitors that read from /dev/kmem.
o Particular to V5, programs that depend on how special
device files are named or how those names are encoded,
will have to cope with the device name changes.
The vast majority of software shouldn't need to be changed
going from version to version. But, software vendors very
reasonably want to test their software on new versions to
verify that it works correctly. V5.0 has been out a while,
but vendors have reasons and excuses for waiting. What
you might want to consider is a benchmark of your existing
applications and problems to compare it with that software
running on other versions.
Since the ES40 is supported by V4.0F and later, it is
more likely that applications supporting V4.0D will
work fine there. You could even avoid reinstalling
the applications by copying the system disks, upgrading
from whatever version you have now to V4.0F or V4.0G
and then migrating that to the new system. You'll have
to get a V4.0G kit though.
R. Aldridge
AT&T Solutions / at McDermott Technology
-----Original Message-----
From: Aldridge, Robert E. (Rob) [mailto:realdridge_at_mcdermott.com]
Sent: Thursday, March 15, 2001 7:29 PM
To: 'tru64-unix-managers_at_ornl.gov'
Subject: Commercial Application Support on ES40 / v5.1/v5.0
Importance: Low
Tru64 Managers:
We're expecting to take delivery of AlphaServer ES40 systems, clustered with
the CCMAB memory channel and
sharing a StorageWorks SAN (fibre channel hub with HSG60 controllers).
I'd appreciate any responses as to whether you've seen any of the following
applications run successfully under either v5.0 or v5.1 of Tru64 Unix.
(I'd hate to have to drop back to v4.0G -- it sounds like I'll be in a jam
as far as being able to support TruCluster memory channel and the
StorageWorks SAN.)
AEA CFX4.3
Amtec Tecplot v8.0
HKS ABAQUS v6.1 or v6.2
MSC Patran 9.5 or Patran 2001
Intelligent Light Fieldview 7
For reference, here are each vendors' claims for supported versions of Tru64
Unix. Some of these vendors apparently are lagging way behind on the Alpha
platform support:
PRODUCT : TRU64 UNIX VERSION SUPPORTED
-----------------------------------------
AEA CFX4.3 : Digital Unix 4.0d
Amtec Tecplot v8.0 : DEC Alpha Digital UNIX 3.2 or higher
HKS ABAQUS v6.1 : Digital UNIX 4.0D
HKS ABAQUS v6.2 : Digital UNIX 4.0F
MSC Patran 9.5 : Digital Unix 4.0F
MSC Patran 2001 : Digital Unix 4.0F (last vendor release of product)
Intelligent Light Fieldview 7 : (not yet determined)
Thanks,
R. Aldridge
AT&T Solutions / at McDermott Technology
Received on Tue Mar 20 2001 - 18:23:45 NZST