| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1677.1 | Things to try... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Oct 28 1992 13:33 | 23 |
| Can you arrange to get VERIFY turned on A1LINK. Don't post all the log
here! I was wondering whereabouts it was in the deferred stub building.
The stub builder is a BLISS program that reads an RTL image, makes a
little MACRO program and then compiles it into an OBJ that we link into
the main image. Perhaps you could watch the looping process with SHO
PROC/CONT from another session and see what image it's running.
Snce yopu say all the files were left after the install was halted, was
this a safety mode install? Or are you doing the link in the kit
working directory under SYS$UPDATE?
Of course you could always turn off deferred image activation and see
if that solves the loop. It won't be something you can do at install
time, but it may help us locate the problem.
The link will loop if it can't find any object file or library that is
referenced via a search list. Since you can do the link outside the
installation you may want to try the SET WATCH FILE/CLASS=MAJOR
sledgehammer before doing the link. You'll get loads of output but it
may give a clue.
Graham
|
| 1677.2 | | KERNEL::OTHENJ | | Wed Oct 28 1992 15:19 | 28 |
| Hi,
Thanks for getting back to me so quickly,
Before the customer killed off the process during installation, the
process was hibernating on the file [allin1.sources_share]oashrbld.exe.
This file does actually exist in that directory after the installation
was stopped.
I have a fax of the log file of the installation, and it showed
that the installaton had to run in non-safety mode as ther was only
68742 block free on sys$disk.
If you try to run the link manually after the installation, it
fails after you answer language=BRITISH as it explains that this
language variant is not present on the system (it also fails if choose
langauge english), so some files must have been cleared up after the
installation.
As we cannot rerun the link procedure, I cannot try it out without
deferred image activation.
The only other option I can think of is to have another go at
installation with options D. Does anyone have any other ideas??
Thanks,
Julie
|
| 1677.3 | Snap - we've got one of those | AIMTEC::WICKS_A | Liverpool 4 Norwich 1 | Wed Oct 28 1992 16:48 | 21 |
| Julie,
OPTIONS D is definitely the way to go.
At the time the link hangs use $SH DEV/FILES on the ALL-IN-1 disk to see
what files are open. We have one call ongoing at the moment I think where
the link hangs at the same point as yours and it claims to be looking for
VAXCRTL.
remember that A1LINK is looking for a set of images defined by the
symbol a1$imagelist - see the section in A1LINK.COM below the label
BUILD_IMAGE_STUBS and make sure all those images are on the system
(particularly watch out for the CDA or DDIF images being missing)
Let us know how you get on - we're still waiting for dial-in to work on
ours so you could save us some time.
Regards,
Andrew.D.Wicks
|
| 1677.4 | It's sys$share and 2.4 .olb's and .exe's I still feel | OUTBCK::SETHI | | Wed Oct 28 1992 23:12 | 54 |
| Hi Julie,
>Although this problem is during a clean installation, the machine
>in question has had v2.4 on it, but he assures me that he cleaned this off
>the system prior to the install.
Did he clean the SYS$SHARE directory of the .olb's and .exe's installed
by 2.4. I feel this is the cause of the problem, as you have already
read my note 1170 my customer was in the same situation. The customer
installed VMS from scratch and the installation went through without a
problem.
One suggestion I would make to check to see what files are being
accessed the two methods being mentioned are very good ie $ set
watch... and $ sh dev/files. They give you alot of information and you
have to sift through it. Use the system analyzer as follows :-)
1. $ analyze/system
2. SDA> show summary ! will give you alot more info than show sys for
example
Current process summary
-----------------------
Extended Indx Process name Username State Pri PCB PHD Wkset
-- PID -- ---- --------------- ----------- ------- --- ---------------- ------
00000101 0001 SWAPPER HIB 16 802AA398 802AA200 0
00001503 0003 SETHI SETHI LEF 6 80551F20 8142CA00 207
3. SDA> set process/index=0003 !set the process context
4. SDA> show process/channel ! will display all the files that are
opened and devices being accessed by the
process at that time for example
Process active channels
-----------------------
Channel Window Status Device/file accessed
------- ------ ------ --------------------
0010 00000000 DISK0$DIA0:
0020 80C60380
DISK0$DIA0:[VMS$COMMON.SYSEXE]TPSERV.EXE;1
0030 80C71580
DISK0$DIA0:[VMS$COMMON.SYSLIB]LIBRTL.EXE;1 (section file)
0040 80C73100
DISK0$DIA0:[VMS$COMMON.SYSLIB]DTI$SHARE.EXE;1 (section file)
I have a feeling it's and old 2.4 image, library that is causing the
problem.
From an old time system mangler :-)
Sunil
|
| 1677.5 | | KERNEL::OTHENJ | | Thu Oct 29 1992 17:21 | 17 |
| Hi,
Just to let you know, after reading all your notes/investigating
info here for X many hours, I rung the customer and he said 'it looked
like the installation worked this time'.
The customer is currently running the IVP and relinking to ensure
everything is O.K., but unfortunately this means we cannot track where
the problem was occuring. He assures me that he did not do anything
different this time (and did not remove any files from sys$share).
I will let you know when he rings me up to let me know how the
relink went.
Thanks for all the help though,
Julie
|