[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

3591.0. "SYSTEM-F-PROTINSTALL when relinking during Upgrade" by BERN01::MUELLERS (Stefan A Mueller 761-4864) Thu Nov 25 1993 20:52

    Hi
    
    I have problems during the relink phase of an upgrade installation. 
    After the message 
    
    	%A1-I-A1LINK, Starting to link images
    
    	Building shared image modules
    
    the following message appears on the screen:
    
     	Error in secondary activation
    	%SYSTEM-F-PROTINSTALL, protected images must be installed 
    
    A1LINK.OPT is open at this time and cannot be deleted by VMSINSTAL.
    After a $ close opt it shows the following contents:
    
    ! Initialization modules
    Cluster=initcluster
    Collect=initcluster,lib$initializdz,lib$initializd_,lib$initialize$,-
    lib$initialize
    ! Force DSAB Prototypes to be read-only
    PSECT=$DSAB_PROTOTYPE1$,NOWRT,SHR,EXE
    PSECT=$DSAB_PROTOTYPE2$,NOWRT,SHR,EXE
    PSECT=$DSAB_PROTOTYPE3$,NOWRT,SHR,EXE
    ! Merge SYMMSG data into same image section as main COR data
    PSECT=$F3_MSG_SYMBOL_TABLE$,EXE
    ! Use the following symbol to define a CSE (DEC internal use) script
    character
    SYMBOL=SCRIPT_CHAR,0
    ! Change PFC cluster size for FLC
    symbol=flc_pfc_size,32
    !Symbol to control number of DSABs in cache
    symbol=oa$dsa_text_cache_size,0
    symbol=oa$dsa_data_cache_size,15
    symbol=oa$dsa_form_cache_size,12
    !Symbol defining the EPC event number for meters
    symbol=oa$gk_epc_met_event_id,1
    !Symbol to determine number of buffers for indexed files
    !Multiply by number of keys for file
    symbol=oa$gk_rms_mbf_multiple,3
    !Symbol to control number of errors mail fetcher will tolerate
    symbol=oa$gk_fetcher_error_limit,5000
    
    Has somebody an idea where the problem could be found or how I could
    find the cause of it?  I am installing now with option D...
    
    Stefan
    
    
    
T.RTitleUserPersonal
Name
DateLines
3591.1Check the DNS images are installed correctlyGIDDAY::SETHIRecompense injury with justiceFri Nov 26 1993 09:5821
    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.2DNS*.EXE installed correctlyZUR01::SSSZH1::MUELLERSFri Nov 26 1993 10:1111
    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.3set watch file/class=majorIOSG::HALLCDenser than a Black Hole SingularityFri Nov 26 1993 10:2424
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 VMSINSTALZUR01::SSSZH1::MUELLERSFri Nov 26 1993 15:2414
    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.5tracing/debugging with VMSINSTALGIDDAY::LEHMon Nov 29 1993 01:0310
    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.6SET WATCH in KIIMAGES.COM?IOSG::HALLCDenser than a Black Hole SingularityMon Nov 29 1993 14:077
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.7SYS$SHARE?AIMTEC::WICKS_AWC94 Dream died when Bodin missedThu Dec 09 1993 20:018
    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.8At least the installation was successfulBERN01::MUELLERSStefan A Mueller 761-4864Mon Dec 13 1993 14:2412
    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.9NO!IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeThu Dec 16 1993 10:087
    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