Conference iosg::all-in-1_v30

2917.0. "OpenVMS V6.0 and ALL-IN-1 V3.0" by TKOV50::NAKAYAMA (I'm Olympic Man) Fri Jun 25 1993 09:52

    Hi,

    I have a installation problem. I can NOT install Japanese ALL-IN-1 V3.0 
    on Japanese OpenVMS V6.0 (Any undefined symbol error cause). Im not so 
    sure, whether this problem is Japanese ALL-IN-1's bug or Japanese OpenVMS's 
    bug.

    This problem is getting more and more aggravated. Anyone have an 
    explanation	for this problem ?


--------------------------------------------------------------------------------


    Problem
    ===========================

    Japanese OpenVMS V6.0 and Japanese ALL-IN-1 V3.0
    (Japanese VAX/FMS V2.4 had already installed.)


$ @SYS$UPDATE:VMSINSTAL A1BJV030 device_name:
        	.
		.
		.

%A1BJV-I-A1LINK, Starting to link images

Linking the OA$LLVJAPANESE.EXE
Building shared image modules
Shared image modules built
Linking the OA$MAIN image
Linking the Background Formatter
%LINK-W-NUDFSYMS, 2 undefined symbols:
%LINK-I-UDFSYM, 	BTL$MAIL_RECEIVE (Weak Reference)
%LINK-I-UDFSYM, 	BTL$RECEIVEFAIL (Weak Reference)
%LINK-I-UDFSYM, 	CXP$GA_EOD (Weak Reference)
		.
		.
		.

%LINK-I-UDFSYM, 	OAN$GT_PROFILE_USER_AREA (Weak Reference)
%LINK-I-UDFSYM, 	OAN$GT_WRITE_PRIVILEGE (Weak Reference)
%LINK-I-UDFSYM, 	OAX$RDC_ACTION (Weak Reference)
%LINK-I-UDFSYM, 	OAX$SQLA_ACTION (Weak Reference)
%LINK-I-UDFSYM, 	WPSPLUS$_INSERT_MODE (Weak Reference)
%LINK-W-USEUNDEF, undefined symbol FDV$SCR_WIDTH referenced
	in psect $F2_CODE$ offset %X00001139
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$SCR_WIDTH referenced
	in psect $F2_CODE$ offset %X00001B80
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$SCR_WIDTH referenced
	in psect $F2_CODE$ offset %X00001C88
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$SCR_WIDTH referenced
	in psect $F2_CODE$ offset %X00001D08
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$SCR_WIDTH referenced
	in psect $F3_CODE$ offset %X000020A4
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$USER_REFRESH referenced
	in psect $F3_CODE$ offset %X000020B1
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$SCR_WIDTH referenced
	in psect $F3_CODE$ offset %X0000212A
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
%LINK-W-USEUNDEF, undefined symbol FDV$USER_REFRESH referenced
	in psect $F3_CODE$ offset %X00002131
	in module OALIST file JRDQ09$DUA6:[SYS0.SYSUPD.A1BJV030]OALIBR.OLB;1
Linking the TM Server
Linking the OA$SUBMIT image
Linking the MAILCOUNT image
Linking the File Cabinet Server images
Linking the RSD housekeeping procedure
Linking the Impersonation Services images

%A1BJV-I-A1LINKED, Finished linking images
		.
		.
		.

%A1IVP-W-IVPPFAIL,The IVPs for ALL-IN-1 V3.0 have failed.
%A1IVP-W-IVPPFAIL,Please investigate the IVP log file (see the System Manager's Guide).
	Installation of A1BJV V3.0 completed at 13:26

	VMSINSTAL procedure done at 13:26

--------------------------------------------------------------------------------




    Thanks for your response.

    Iwao Nakayama

    
    I don't know if this helps but we have ALL-IN-1 V3.0 SSB and VMS V6.0
    SSB together working fine.
    
    Mike

    Iwao,
    
    As i'm sure you spotted both undefined symbols are from FMS (they
    start FDV$) so I think ALL-IN-1 as such is innocent here.
    
    Do you a) have FMS installed correctly and b) assuming there's a
    Japanese version of FMS has it been certified on v6.0
    
    Regards,
    
    Andrew.D.Wicks

    Thanks, .1 and .2

>    As i'm sure you spotted both undefined symbols are from FMS (they
>    start FDV$) so I think ALL-IN-1 as such is innocent here.

     I think so, too.

>    Do you a) have FMS installed correctly and b) assuming there's a
>    Japanese version of FMS has it been certified on v6.0
    
     I had Japanese FMS V2.4 installed correctly and Japanese FMS V2.4
     has been certified on VMS V6.0.


     Iwao

    I know this is a very old problem, and you almost certainly have tried
    this, but I suppose you are *SURE* that the FMS images are installed?
    i.e. the appropriate edit has been made to the FMS startup procedure.
    
    Graham

Also even if the correct images are installed it is worth re-installing FMS.
This doesn't take long and fixed a similar problem for me recently.

Aston

     Hi,

>    I know this is a very old problem, and you almost certainly have tried
>    this, but I suppose you are *SURE* that the FMS images are installed?
>    i.e. the appropriate edit has been made to the FMS startup procedure.

     I had reinstalled FMS and FMS image was installed.
     But, ALL-IN-1 installation was failed.

     I'm going to install FMS images to SYS$LIBRARY:IMAGELIB.OLB and install
     ALL-IN-1 V3.0 on VMS V6.0.

     If you have any other good ideas, please write here.
     I'm waiting for your good help.


     Iwao

    
    I came across errors similar to this a few months back, I eventually
    traced the errors to  the system having two versions of imagelib and 	
    starlet, one in sys$sysroot:[syslib] and the other in sys$common:[syslib]
    The FMS installation updated modules into one of the versions while
    the ALL-IN-1 relink choose to pick up the other and not finding the 
    modules obviously failed......might help.
    
    regards,
    
    Pat.