T.R | Title | User | Personal Name | Date | Lines |
---|
3591.1 | Check the DNS images are installed correctly | GIDDAY::SETHI | Recompense injury with justice | Fri Nov 26 1993 09:58 | 21 |
| Hi Stefan,
Are the following images installed DNS$RTL.EXE and DNS$SHARE.EXE both
are in SYS$LIBRARY ? The DNS$SHARE.EXE has to be installed as a
protected image and here is an example from my system:
DISK$VAXVMSV055:<SYS0.SYSCOMMON.SYSLIB>.EXE
DNS$RTL;2 Open Shar Lnkbl
Entry access count = 14
Current / Maximum shared = 6 / 8
Global section count = 2
DISK$VAXVMSV055:<SYS0.SYSCOMMON.SYSLIB>.EXE
DNS$SHARE;2 Open Shar Prot Lnkbl
Entry access count = 48
Current / Maximum shared = 7 / 13
Global section count = 5
Regards,
Sunil
|
3591.2 | DNS*.EXE installed correctly | ZUR01::SSSZH1::MUELLERS | | Fri Nov 26 1993 10:11 | 11 |
| Hi Sunil,
The DNS images are installed correctly.
We changed the UIC before the upgrade. When setting the new owner on
the files in [ALLIN1...] we had some problems because of locking. One
of these files was OA$SUBMIT.EXE. We corrected this problems and are
installing now again.
Some other ideas?
Stefan
|
3591.3 | set watch file/class=major | IOSG::HALLC | Denser than a Black Hole Singularity | Fri Nov 26 1993 10:24 | 24 |
| Stefan,
The link is failing when building the shareable image stubs. It looks like one
of the images that we defer is not installed in memory, the installation should
check for all these but I suspect the checks might not be totally complete.
Can you relink the current ALL-IN-1 Version without this error? If you can
reproduce the error by just relinking the current version you'll save some time
debugging the problem!
I suggest doing:
$set watch file/class=major
Then either just doing a relink (if the problem shows up when relinking the
current system) or starting the upgrade again.
This will show the files accessed and should track down which image is causing
the problem.
Cheers,
Chris.
P.S. What version are you upgrading from and to?
|
3591.4 | $ SET WATCH doesn't work with VMSINSTAL | ZUR01::SSSZH1::MUELLERS | | Fri Nov 26 1993 15:24 | 14 |
| Chris,
Nice idea, but on this system it doesn't work during vmsinstal because
of
%DCL-W-SYMOVF, no room for symbol definitions - delete some symbols
Raising CLISYMTBL to 500 doesn't solve the problem so I assume it's
an undocumented feature of SET WATCH.
I'll reboot the system and do another try tomorrow.
Stefan
|
3591.5 | tracing/debugging with VMSINSTAL | GIDDAY::LEH | | Mon Nov 29 1993 01:03 | 10 |
| Stefan
Chris in .3 meant SET WATCH for a relink
Use $ @VMSINSTAL <product> <location> OPTIONS KCL, which turns tracing,
debugging on during instal. It helped me a lot despite the overhead of
extra diskspace.
Good luck
Hong
|
3591.6 | SET WATCH in KIIMAGES.COM? | IOSG::HALLC | Denser than a Black Hole Singularity | Mon Nov 29 1993 14:07 | 7 |
| Stefan,
You could put the $set watch just before the call to A1LINK in KIIMAGES.COM.
You will find KIIMAGES.COM in saveset A103*.A
Cheers,
Chris.
|
3591.7 | SYS$SHARE? | AIMTEC::WICKS_A | WC94 Dream died when Bodin missed | Thu Dec 09 1993 20:01 | 8 |
| stefan,
tried STARS? it suggests that your problem may be caused by SYS$SHARE
being defined as a search listed logical.
regards,
Andrew.D.Wicks
|
3591.8 | At least the installation was successful | BERN01::MUELLERS | Stefan A Mueller 761-4864 | Mon Dec 13 1993 14:24 | 12 |
| Thanks for all your replies!
I replaced all the files in OA$BUILD and OA$LLV with clean versions
from a V2.4 kit and it worked. This was possible because they will
reinstall all products that did some changes in these directories.
The system has also been rebooted before the successful installation,
so I don't exactly know the cause of my problems. But it seems that the
installation uses some objects from V2.4 to relink the V3.0 during
installation time. Can someone confirm?
Stefan
|
3591.9 | NO! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Dec 16 1993 10:08 | 7 |
| NO, I can categorically contradict that.
The V3.0 installation and link doesn't use any of the old object
libraries or files. Also, it takes great care not to use any files in
the SITE areas.
Graham
|