| In general, the default Datatrieve sharable image is DTRSHR.
However, Datatrieve lets you run multiple versions on the same
system. When you install multiple copies of Datatrieve, it lets
you pick the name of the sharable image. This is why you are
asked the image name to use.
I don't know why your Datatrieve link has slowed down and I also
don't know what DTRSHRFM is. I could just be an alternate version
of Datatrieve.
_Mike
|
| Hi,
I've just taken over system managing a machine with ALL-IN-1. I need to re-link
ALL-IN-1 with Datatrieve, but am experiencing some problems. Can anyone help ?
I tried to re-link ALL-IN-1 V2.4 from a privileged account using A1LNKDRV.COM
in order to incorporate Datatrieve. The questions were answered in the usual
way, but fell over with error messages :
"error opening [TESTINSTALL5]OADPESHR.OBJ "
"error opening MISSING:[MISSING]OA$MAIN.EXE"
"error opening MISSING:[MISSING]XPORT.OLB
"error opening SYS$COMMON:[SYSLIB]DPESHR.EXE
MISSING:[MISSING]XPORT.OLB
I found that DPESHR.EXE was not in SYS$COMMON:[SYSLIB]. Why this is I don't
know.
Thinking this was the problem, I copied over this image from another
machine and re-linked. All error messages were resolved, and I got the message
"relinking ALL-IN-1". Fine. But then it just hangs. I left over night,
thinking it just takes a long time. But no luck. Can anyone help ?
I have checked :
(a) same versions of ALL-IN-1 on this and the machine I copied the image from.
(b) diskquotas, security of DPESHR.EXE.
(c) running the procedure from [ALLIN1.SOURCES]
All .OPT, .OBJ, .OLB files etc. are produced OK in the account I am linking
from. Unfortunately, the machine is unavailable for a week now, so I guess
it's time to ask for help having tried several things.
Regards,
Rob
|
| The linker hangs usually when it can't find a file.
To find out which file it's missing, set the DCL symbol A1$DEBUG to 1
before running A1LNKDRV
$a1$debug==1
$@a1lnkdrv
You'll then get a fair amount of extra output, at the end of which youn
will see the linker options file. The line it stops at is (probably)
the missing file.
Also, the linker is apt to get upset if the files it's processing are
referred to by logical search lists (unless they're in the first
translation of the logical).
D.
|