|
Claudia,
I've just returned from a trip. No, I don't recall that we have tested
with VMS 7.0 yet. One thing I know that Rdb had to do for one of the
earlier VMS versions was to register its privileged images with VMS
so that new Rdb kits did not have to be built. Maybe the same is true
for VMS 7.0, and maybe this now applies to the DDD privileged images.
This is just a guess on my part. Assuming that VMS 7.0 has such an
image registration facility, they could try to register the
DDAL$TR_MON.EXE and DDAL$COPY_PROCESS.EXE iamges to see if that makes
the problem go away.
Claude
|
|
Well, I'm starting to get over my jet lag.
There may well be a change in VMS 7.0 that requires a relink of DDD.
We link with SYS.STB, and whenever there's a major change in system
data structures, we can be affected. In the 10 year history of DDD
with VMS, this has only happened once before.
We'll have to look into this at some point, but I'm not in a position
right now to say when you might see a change in the product to support
VMS 7.0.
|
| fwiw, in Rdb land I am not aware of any problems running older images
on VMS V7 that were linked /SYS against the older versions of VMS.
However, we did link in LIBRTL.OLB which caused problems due to changes
in VMS exception handling. Rdb now links against LIBRTL.EXE instead of
linking it in.
|