| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hi,
my customer upgraded his ALL-IN-1 from version V3.0 to V3.0a (ITALIAN) .
The VMS version is 5.4-3 . At the relink phase he got some anomalous messages ,
here is the log...
$ set def oa$build
$ @oa$build_share:a1_mupa030_relink.com
A1_MUPA030_RELINK.COM started at 13-JAN-1994 16:23:46.20
Specify which language version of ALL-IN-1 you wish to link [ENGLISH]? italian
%A1 -I-SAVED_ANS_1, Default answers are being taken from saved answers file
%A1 -I-SAVED_ANS_2, which was created on 13-JAN-1994 15:49:53.18
* Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]?
%A1 -I-DTRNOLINK, DATATRIEVE will not be linked with ALL-IN-1
%A1 -I-SAVED_ANS_1, Default answers are being taken from saved answers file
%A1 -I-SAVED_ANS_2, which was created on 13-JAN-1994 15:49:53.18
* Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]?
%A1 -I-DTRNOLINK, DATATRIEVE will not be linked with ALL-IN-1
* Do you want to link WPS-PLUS with ALL-IN-1 [YES]?
%A1 -I-WPSLINK, The WPS-PLUS editor will be linked with ALL-IN-1
* Do you want to integrate ACMS with ALL-IN-1 [NO]?
%A1 -I-ACMSNOLINK, ACMS will not be linked with ALL-IN-1
* Do you want to build a MULTI-LANGUAGE system [NO]?
%A1 -I-NOMLLINK, ALL-IN-1 will be linked as a single language system
* Which date format do you require [2]:
%A1 -I-DATEFORMAT, Date format DD-MMM-YYYY and DD/MM/YY (2) has been selected
%A1 -I-MRVEROK, Your Message Router version is V3.2
%A1 -I-DDS, DDS support will be included in the link
%DCL-I-SUPERSEDE, previous value of VMI$KWD has been superseded
Building shared image modules
Shared image modules built
Linking the OA$MAIN image
Linking the Background Formatter
Remember to move the OA$MAIN image to OA$LIB_SHARE and re-install
the image prior to attempting to run ALL-IN-1.
Linking the File Cab Server image
**************START ANOMALOUS MESSAGES****************************
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\ARCH_TYPE\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\VERSION_STATUS\
%LINK-W-NUDFSYMS, 3 undefined symbols:
%LINK-I-UDFSYM, DOTS$FREE_OUTPUT_LIST
%LINK-I-UDFSYM, DOTS$PACK
%LINK-I-UDFSYM, DOTS$UNPACK
%LINK-W-USEUNDEF, undefined symbol DOTS$PACK referenced
in psect $CODE offset %X000035C8
in module ESISUP file SYS$SYSDEVICE:[ALLIN1.SOURCES_SHARE]OAFC$SERVER.OLB;2
%LINK-W-USEUNDEF, undefined symbol DOTS$FREE_OUTPUT_LIST referenced
in psect $CODE offset %X00003655
in module ESISUP file SYS$SYSDEVICE:[ALLIN1.SOURCES_SHARE]OAFC$SERVER.OLB;2
%LINK-W-USEUNDEF, undefined symbol DOTS$UNPACK referenced
in psect $CODE offset %X00004A13
in module ESISUP file SYS$SYSDEVICE:[ALLIN1.SOURCES_SHARE]OAFC$SERVER.OLB;2
%LINK-W-USEUNDEF, undefined symbol DOTS$FREE_OUTPUT_LIST referenced
in psect $CODE offset %X00004A67
in module ESISUP file SYS$SYSDEVICE:[ALLIN1.SOURCES_SHARE]OAFC$SERVER.OLB;2
%LINK-W-USEUNDEF, undefined symbol DOTS$UNPACK referenced
in psect $CODE offset %X00004F41
in module ESISUP file SYS$SYSDEVICE:[ALLIN1.SOURCES_SHARE]OAFC$SERVER.OLB;2
%LINK-W-USEUNDEF, undefined symbol DOTS$FREE_OUTPUT_LIST referenced
in psect $CODE offset %X00004F93
in module ESISUP file SYS$SYSDEVICE:[ALLIN1.SOURCES_SHARE]OAFC$SERVER.OLB;2
*************END ANOMALOUS MESSAGES*************************************************
You have relinked selected image files and now need to COPY
them to their respective target directories. In addition
to the above images, the following must also be moved:
File Destination
---- -----------
OA$FORMATTER.EXE SYS$COMMON:[SYSEXE]
OAFC$SERVER.EXE SYS$COMMON:[SYSEXE]
OAFC$MTS_PRIV_SHR.EXE SYS$COMMON:[SYSLIB]
A1_MUPA030_RELINK.COM completed at 13-JAN-1994 16:30:54.54
I know , they are warning and information messages but the customer wants to know
something more ....
CAN ANYBODY GIVE ME ANY ADVICE..?
MANY THANKS IN ADVANCE ,
PAOLO ZAGHI .
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3789.1 | CDA checks in FCS link | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Thu Jan 20 1994 18:12 | 14 |
paolo,
take a look at OAFC$SERVER_LINK.COM in OA$BUILD: you will see it doing
various checks against CDA which appear to be the cause of your
problem.
rereun oafc$server_link with set verify on and you should see more
You cannot run a pre-v3.0A FCS image with a v3.0A system so you need
to resolve these errors.
Regards,
Andrew.D.wicks
| |||||
| 3789.2 | One other thing | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Thu Jan 20 1994 18:19 | 7 |
also make sure you do the correct set def at the start
I just noticed that you set def to OA$BUILD not OA$BUILD_LLV as you
are supposed to.
regards,
Andrew.D.Wicks
| |||||
| 3789.3 | wrong relink.com being used? | IOSG::STANDAGE | Thu Jan 20 1994 19:34 | 14 | |
Also check you have the correct SSB version of MUPA.
Those ARCH_TYPE errors look like you have a kit with an ALPHA
related server relink.com - this was a problem with a VERY early
base level of MUPA I seem to remember.
Make sure the OAFC$SERVER_LINK.COM you're using is the latest version
hanging around in the OA$BUILD directories.
Kevin.
| |||||
| 3789.4 | another check on relink... | MLNTSC::ZAGHI | Fri Jan 28 1994 09:12 | 81 | |
Hi ,
First of all excuse me for the late , but our group is bombarded with
customer's problems ......
Before reading your advices I did another chek.
I observed that the key ARCH_TYPE is called in OAFC$SERVER_LINK.COM....
***********
$ define/user sys$error NL:
$ a1$arch_type = f$getsyi("ARCH_TYPE") <---------problem
$ if .not. $STATUS then a1$arch_type = 1
$ deassign/user sys$error
$!
$ if a1$arch_type .eq. 1 ! 1=VAX, 2=AXP
$ then
$ idoff = f$cvui(0,16,f$extract(6,2,hdr)) ! Get image name offset
$ idoff = idoff + 40 ! Add the default offset
$ idlen = f$cvui(0,8,f$extract(idoff,1,hdr)) ! Get length of image id.
$ else
$ idoff = f$cvui(0,32,f$extract(24,4,hdr)) ! Get image name offset
$ idoff = idoff + 56 ! Add the default offset
$ idlen = f$cvui(0,8,f$extract(idoff,1,hdr)) ! Get length of image id.
$ endif
*************
I tried the command "$ a1$arch_type = f$getsyi("ARCH_TYPE")" in
interactive way and it failed (of course....). The message was the same
"%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\ARCH_TYPE\ "
I tried this command on my system , it was OK (of course...).
The difference from my system and customer's system is the VMS version .
CUSTOMER'S SYSTEM ----> V 5.4-3
MY SYSTEM ------> V 5.5-2
The key ARCH_TYPE is not present on VMS 5.4-3 .
Then.....
I commented the line "$ a1$arch_type = f$getsyi("ARCH_TYPE")" and
with "a1$arch_type" defined to 1 (in interactive way), A1_MUPA030_RELINK.COM
procedure ran without anomalous messages .
Anymore idea ??
In response at your advices:
> take a look at OAFC$SERVER_LINK.COM in OA$BUILD: you will see it doing
> various checks against CDA which appear to be the cause of your
> problem.
> rereun oafc$server_link with set verify on and you should see more
"Set verify" idea is very helpfull but in this moment customer can't run
A1_MUPA030_RELINK.COM (he will do it as soon as possible).
> also make sure you do the correct set def at the start
> I just noticed that you set def to OA$BUILD not OA$BUILD_LLV as you
> are supposed to
Customer will try the correct "set def" as soon as possible.
> Also check you have the correct SSB version of MUPA.
> Those ARCH_TYPE errors look like you have a kit with an ALPHA
> related server relink.com - this was a problem with a VERY early
> base level of MUPA I seem to remember.
I installed the same MUP kit on my system (it isn't ALPHA) and all was ok.
> Make sure the OAFC$SERVER_LINK.COM you're using is the latest version
> hanging around in the OA$BUILD directories
I'll tell the customer to check this.
Many thanks too,
Paolo.
| |||||
| 3789.5 | not the ssb kit | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Fri Jan 28 1994 16:57 | 11 |
Paolo,
It certainly looks as if the customer doesn't have the SSB version of
the MUP. Kevin was right when said that the ALPHA stuff was in the EFT2
kit and not in the SSB. Double check that the customer really does have
an SSB kit and maybe copy the offending OA$FCSERVER_LINK file from your
system over to theirs. and try again.
Regards,
Andrew.D.Wicks
| |||||