[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

1170.0. "Install 3.0 loops while linking/building shared images" by GIDDAY::SETHI (Man from Downunder) Tue Aug 04 1992 05:15

    G'day All,

    A customer has a problem installing ALL-IN-1 Version 3.0 on a VMS
    Version 5.5-1 system.  The installation procedure goes into a loop while 
    "Building shared image modules".  A $show proc/cont/id= shows us that
    it's linking and chewing up CPU time.
                            
    The customer was asked to enter the following options to help us debug
    the kit :- S - statistics, K - kit debug and C - Callback trace.
     
    What we have discovered so far :-)

    1. copy of the installation log file show the installation procedure
       looping at the following point 

        Installing the Linguistics Components Interface

    	Debug - KIIMAGES  for A1030 (A1 V3.0)
    	%A1-I-A1LINK, Starting to link images

    	Building shared image modules
     
    2. The Call Back Trace file A1030.CBT has the following information 

    FIND_FILE               <A1$DPESHR> <DPESHR.EXE> <VMI$ROOT:[SYSLIB]>
    <W,S> <> ~
                            <> <>
    FIND_FILE               <A1$XPT> <XPORT.OLB> <VMI$ROOT:[SYSLIB]> <W,S>
    <> <> <~
                            >

    3. Found A1LINK.COM in save_set A1LUS030.D.  There is a list of images
       to be  built called "a1$imagelist", the first image is called
       SYS$PROXY_SHR.  The list contains the following

    a1$imagelist = "SYS$PROXY_SHR|DPESHR|CONVSHR|FDLSHR|FORRTL|LBRSHR|" + -
                    "MTHRTL|SECURESHR|SMGSHR|SORTSHR|VAXCRTL|NMLSHR|LCI$SHARE"

    4. Directory of SYS$SHARE the LCI$SHARE and SYS$PROXY_SHR weren't
       created.  The other images in the list were created in SYS$SHARE.

    Should you require access to the .CBT and installation log file they
    can be found on RIPPER::USER$TSC:[SETHI].  They are called COLES_CBT.LIS
    and COLES_INSTALL.LOG respectively.  There is a session log file when I
    logged onto the customers system called COLES_2.LOG.  The file
    protection is W:R on them.

    Any suggestions would be gratefully accepted in solving this problem.

    Thanks for your help in advance

    Sunil
    
T.RTitleUserPersonal
Name
DateLines
1170.1PAJERO::RHOTONJohn Rhoton @TNO - DTN 871.7947Tue Aug 04 1992 09:557
    Re: .0
    
    It is "normal" for the linker to loop if it is unable to locate some of
    its files which seems to be the case as you mention in your fourth
    point.  Do you have any idea why those files are missing?
    
    John
1170.2More infoGIDDAY::SETHIMan from DownunderTue Aug 04 1992 10:1510
    Hi John,
    
    I was just going home when I saw your reply.  The said files are in the
    save set's I can't remember which ones.  That's why I am a bit lost as
    to why they were not copied.  I'll add the diskquota's etc have been
    checked and the free disk space all seems to be fine in this area.
    
    Better go now the train is coming in 5 mins.
    
    Sunil
1170.3OPTIONS D Does it for meAIMTEC::WICKS_ADEC Mail Works for ME sometimesWed Aug 05 1992 00:5520
    Firstly I would always use OPTIONS D to debug a link - could you try
    that.
    
    Secondly the reasons you find all the images except LCI and the
    SYS$PROXY is that all the others were there in v2.4 - they are the only
    two added to the deferred image activation list by v3.0 and they won't
    be there til the install completes.
    
    Thirdly, if the problem is really DPESHR and/or XPORT as the callback
    thingy suggests then note 1087 in the old notesfile may help (it was
    written by GAP) - and there's loads of STARS articles about interactive
    logins but that was fixed in VMS v5.4-3
    
    I'm sure OPTIONS D would help - it hasn't let me down yet
    
    Debug, Debug, Debug
    
    Regards,
    
    Andrew.D.Wicks
1170.4GIDDAY::SETHIMan from DownunderWed Aug 05 1992 09:2620
    G'day Andrew,

    Re .3

    Well after reading your reply I was well and truely confused concerning
    the ALL-IN-1 2.4 images.  The customer is installing ALL-IN-1 on a
    virgin VMS 5.5-1 system, the system never had ALL-IN-1 installed.  The 
    customer is not doing an upgrade it's an install.  
    
    The customer left a vital bit of information out in that he copied the
    system disk from another system that had ALL-IN-1 2.4 installed.  I
    have asked him to install 3.0 on a system that has NEVER had ALL-IN-1
    installed.  My guess is that the installation procedure may have got a
    bit confused doing an install, because of various images and .olb's on
    the system disk.  I'll make sure that I post the results here to round
    things of.
    
    Thanks for pointing me in the right direction in around about way :-).
    
    Sunil
1170.5Review the prerequisitesWAYLND::HOWARDOur business is computers not moneyThu Aug 06 1992 20:31181
    Actually, I doubt that the installation would get confused that way. 
    What has probably happened is that one of the (many) checks at the
    beginning has missed a problem, such as an image not being installed
    correctly.  This can happen, for example, when the installation
    procedure checks for "KNOWN" with F$FILE_ATTRIBUTE, the image may be
    installed but not have the correct privileges.  You need to carefully
    check the system against the prerequisites in the installation guide. 
    People assume that since ALL-IN-1 fails to install so easily with a
    polite error message, that it has checked everything thoroughly. 
    Actually, there are many things that can still be wrong, and there are
    some things that it never checks at all.  After the form feed is what I
    use.  Of course, it still has the limitation I mentioned above, so you
    might want to check the images with the INSTALL command.
    
    The safety mode value is wrong, but I can't remember where I saw
    the correct value.  I should have used F$FAO for formatting, but I
    didn't.
    
    
$ if p1 .nes. "VER" 
$ 	THEN VER = F$VERIFY(0)
$ 	ELSE SET VERIFY
$ ENDIF
$ if f$edit(p2,"upcase") .eqs. "BATCH" 
$    then mode := "BATCH"
$    ELSE mode = "''F$MODE()'" 
$ ENDIF
$ ON CONTROL_Y THEN EXIT
$ TAB[0,8] = 9
$ ESC[0,8] = 27
$ BOLD = ESC  + "[1m"
$ CLEAR = ESC + "[0m"
$ user = f$edit(f$getjpi("","username"),"trim")
$ SAY := WRITE SYS$OUTPUT
$ JPINUM = 0
$ SYINUM = 0
$! JPILIST = -
$ say bold
$ say "Checking various quotas for installing ALL-IN-1 V3.0 from this account (", user, ")"
$ SAY "These values include Message Router V3.2"
$ if user .nes. "SYSTEM" then SAY "(ALL-IN-1 should be installed from SYSTEM account)"
$ say clear
$ FREE = F$GETDVI("SYS$SYSDEVICE:","FREEBLOCKS")
$ if  FREE .LT. 65000 
$	THEN SAY BOLD,"Only ''FREE' available on SYS$SYSDEVICE; 65,000 required)"
$	     SAY  "ALL-IN-1 will not be installed in Safety mode", CLEAR
$	ELSE SAY "ALL-IN-1 will be installed in Safety mode"
$	     SAY  "(''FREE' blocks available on SYS$SYSDEVICE; 65,000 required)"
$   ENDIF
$ IF MODE .EQS. "INTERACTIVE" 
$    THEN READ/PROMPT="Press RETURN to continue" SYS$COMMAND DUMMY
$	ENDIF
$ SYILIST = -
"CTLPAGES*75/FREE_GBLPAGES*29080/FREE_GBLSECTS*370/GBLPAGFIL*1724/LOCKIDTBL*340" + -
"/MAXBUF*6000/MPW_LOLIMIT*750/MPW_HILIMIT*1500/MPW_THRESH*1000/MPW_WAITLIMIT*1520" + -
"/PIOPAGES*350/PQL_DENQLM*150/PQL_MENQLM*150" + -
"/PQL_DASTLM*24/PQL_DBIOLM*18/PQL_DBYTLM*35000/PQL_DDIOLM*18/PQL_DENQLM*400" + -
"/PROCSECTCNT*45/RESHASHTBL*85/RMS_DFMBC*16/RMS_DFMBFIDX*2/TTY_ALTYPAHD*1500" + -
"/TTY_BUF*200/TTY_TYPAHDSZ*1500/VIRTUALPAGECNT*20000" 
$SYILOOP:
$! TABS = TAB
$ SYIITEM = F$ELEMENT(SYINUM,"/",SYILIST)
$ IF SYIITEM .EQS. "/" THEN GOTO SYIFINISH
$ AST = F$LOCATE("*",SYIITEM)
$ SYIITEM_NAME = F$EXTRACT(0,AST,SYIITEM)
$ SYSITEM_LENGTH = F$LENGTH(SYIITEM_name) 
$ SPACES = "                "
$ TAB_LENGTH = 16 - SYSITEM_LENGTH
$ TABS = F$EXTRACT(0,TAB_LENGTH,SPACES)
$! IF SYSITEM_LENGTH .LE. 6 THEN TABS = TAB + TAB + TAB
$ VALUE_LOC = AST + 1
$ SYIITEM_VALUE = F$EXTRACT(VALUE_LOC,99,SYIITEM)
$ SYI_ACTUAL = F$GETSYI(SYIITEM_NAME)
$ SPACES_ACTUAL = "        "
$ ACTUAL_LENGTH = F$LENGTH(SYI_ACTUAL)
$ ACTUAL_TAB_LENGTH = 8 - ACTUAL_LENGTH
$ AC_TAB = F$EXTRACT(0,ACTUAL_TAB_LENGTH,SPACES_ACTUAL)
$ IF SYI_ACTUAL .GE. SYIITEM_VALUE 
$ 	THEN SAY SYIITEM_NAME, TABS, " (", SYI_ACTUAL, ")", AC_TAB, "OK. Req.: (", SYIITEM_VALUE, ")"
$	ELSE SAY SYIITEM_NAME, TABS, " (", SYI_ACTUAL, ")", AC_TAB, BOLD, "Increase to ",SYIITEM_value,clear
$	ENDIF
$ IF SYIITEM_NAME .EQS. "FREE_GBLPAGES" THEN $ SAY " (GBLPAGES is ",F$GETSYI("GBLPAGES"), ")"
$ IF SYIITEM_NAME .EQS. "FREE_GBLSECTS" THEN $ SAY " (GBLSECTIONS is ", F$GETSYI("GBLSECTIONS"), ")"
$ SYINUM = SYINUM + 1
$ GOTO SYILOOP
$SYIFINISH:
$ !SAY " "
$ IF F$GETSYSI("STARTUP_P1") .EQS. "    " 
$    	THEN SAY "STARTUP_P1       (null)    OK."
$ 	ELSE SAY "STARTUP_P1 is ", TAB, F$GETSYSI("STARTUP_P1"), "; Should be null"
$ 	ENDIF    
$ GOTO WSMAX
$ IF F$GETSYSI("STARTUP_P2") .EQS. "    " 
$    	THEN SAY "STARTUP_P2       (null)    OK."
$ 	ELSE SAY "STARTUP_P2 is ", TAB, F$GETSYSI("STARTUP_P2"), "; Should be null"
$ 	ENDIF    
$WSMAX:
$ SAY "WSMAX            ", F$GETSYSI("WSMAX"), " (Needs to be higher than largest user WS)
$ SAY " "
$ IF MODE .EQS. "INTERACTIVE" 
$    THEN READ/PROMPT="Press RETURN to continue" SYS$COMMAND DUMMY
$	ENDIF
$ SAY "Process quotas.  Check JTQUOTA in SYSUAF. . . "
$!EXIT
$ JPINUM = 0
$ JPILIST = -
"ASTLM*100/BIOLM*50/BYTLM*36000/DIOLM*50/ENQLM*200/FILLM*100/PGFLQUOTA*20000" + -
"/PRCLM*10/TQLM*50/WSEXTENT*3000/WSQUOTA*800/WSSIZE*600"
$JPILOOP:
$! TABS = TAB
$ JPIITEM = F$ELEMENT(JPINUM,"/",JPILIST)
$ IF JPIITEM .EQS. "/" THEN GOTO SYISTART
$ AST = F$LOCATE("*",JPIITEM)
$ JPIITEM_NAME = F$EXTRACT(0,AST,JPIITEM)
$ JPIITEM_LENGTH = F$LENGTH(JPIITEM_NAME)
$ SPACES = "                "
$ TAB_LENGTH = 16 - JPIITEM_LENGTH 
$ TABS = F$EXTRACT(0,TAB_LENGTH,SPACES)
$ VALUE_LOC = AST + 1
$!
$ JPIITEM_VALUE = F$EXTRACT(VALUE_LOC,99,JPIITEM)
$ JPI_ACTUAL = F$GETJPI("",JPIITEM_NAME)
$ SPACES_ACTUAL = "        "
$ ACTUAL_LENGTH = F$LENGTH(JPI_ACTUAL)
$ ACTUAL_TAB_LENGTH = 8 - ACTUAL_LENGTH
$ AC_TAB = F$EXTRACT(0,ACTUAL_TAB_LENGTH,SPACES_ACTUAL)
$ IF JPI_ACTUAL .GE. JPIITEM_VALUE 
$ 	THEN SAY JPIITEM_NAME, TABS, " (", JPI_ACTUAL, ")", AC_TAB, "OK. Req.: (", JPIITEM_VALUE, ")"
$	ELSE SAY JPIITEM_NAME, TABS, " (", JPI_ACTUAL, ")", AC_TAB, bold, "Increase to ", JPIITEM_value, CLEAR
$	ENDIF
$ JPINUM = JPINUM + 1
$ GOTO JPILOOP
$SYISTART:
$!set verify
$!ben = FD$VERIFY(1)
$ IF MODE .EQS. "INTERACTIVE" 
$    THEN READ/PROMPT="Press RETURN to continue" SYS$COMMAND DUMMY
$	ENDIF
$ SAY "Checking required INSTALLed files . . . "
$ SAY ""
$! exit
$ FILESNUM = 0
$ FILESLIST = -
"SYS$MESSAGE:FDVMSG.EXE/SYS$SHARE:CONVSHR.EXE/SYS$SHARE:FDLSHR.EXE" + -
"/SYS$SHARE:FDVSHR.EXE/SYS$SHARE:LBRSHR.EXE/SYS$SHARE:MTHRTL.EXE" + -
"/SYS$SHARE:NMLSHR.EXE/SYS$SHARE:PASRTL.EXE/SYS$SHARE:SCNRTL.EXE" + -
"/SYS$SHARE:SCRSHR.EXE/SYS$SHARE:VMSRTL.EXE/SYS$SHARE:VAXCRTL.EXE" + -
"/SYS$SHARE:DNS$SHARE.EXE/SYS$SHARE:DNS$RTL.EXE"
$FILESLOOP:
$ TABS = TAB
$ FILESITEM = F$ELEMENT(FILESNUM,"/",FILESLIST)
$ IF FILESITEM .EQS. "/" THEN GOTO FILESFINISH
$ IF F$LENGTH(FILESITEM) .LE. 7 THEN TABS = TAB + TAB
$! VALUE_LOC = AST + 1
$! FILESITEM_VALUE = F$EXTRACT(VALUE_LOC,99,FILESITEM)
$ IF FILESITEM .eqs. "SYS$SHARE:MTHRTL.EXE" THEN GOTO MTH
$ IF F$SEARCH(FILESITEM) .EQS. "" 
$  	THEN SAY FILESITEM, TABS, BOLD, "Not found ",clear
$	GOTO INCREMENT_FILESNUM
$	ENDIF
$ IF F$FILE_ATTRIBUTE(FILESITEM,"KNOWN") .EQS. "TRUE" 
$ 	THEN SAY FILESITEM, TABS, "OK.
$	ELSE SAY FILESITEM, TABS, BOLD, "Needs to be INSTALLed ",clear
$	ENDIF
$INCREMENT_FILESNUM:
$ FILESNUM = FILESNUM + 1
$ GOTO FILESLOOP
$MTH:
$ IF F$FILE_ATTRIBUTE(FILESITEM,"KNOWN") 
$  THEN SAY FILESITEM, TABS, "OK.
$	ELSE IF F$FILE_ATTRIBUTE("SYS$SHARE:UVMTHRTL.EXE","KNOWN") 
$  	THEN SAY FILESITEM, " (actually SYS$SHARE:UVMTHRTL.EXE)", TABS, " OK.
$	ELSE SAY "Correct version of ", FILESITEM, TABS, BOLD, "Needs to be installed ",clear
$	ENDIF
$    ENDIF
$ FILESNUM = FILESNUM + 1
$ GOTO FILESLOOP
$ FINISH = F$VERIFY(VER)
$FILESFINISH:
$ EXIT
$! 65K Blocks on system disk for safety mode
1170.6GIDDAY::SETHIMan from DownunderTue Aug 11 1992 04:3917
    Hi,
    
    Re .5, thanks for your suggestions I asked the customer to go through
    the pre-installation checks throughly.  He assured me that everything
    was in order.
    
    The customer re-installed VMS 5.5-1 and Mailbus 3.2-1 than all the required
    layered products such as FMS. The backup copy of MODPARAMS.DAT from the 
    previous installation was used to generate the new SYSGEN parameters.  
    
    The installation of ALL-IN-1 was successful.  I wonder if those Version
    2.4 files caused the problem ?  I just can't think of anything thing
    else maybe I am wrong.
    
    Thanks for all your help 
    
    Sunil
1170.7it's option "S" !FROIS1::HOFMANNStefan Hofmann, LC Frankfurt, ISEWed Aug 12 1992 18:5416
    Hello,
    
    sorry I didn't reply earlier, must have missed this topic.
    I'm working in the Localization Center in Frankfurt and we are
    currently installing about 20 ALL-IN-1 versions a week, since we are
    building the 10 non-English languages of ALL-IN-1. For the final SQM
    evaluation we were supposed to create LOG files from installations with
    option S. In the meantime we found out that the option S is the reason
    for these loops, and we agreed on a different option with SQM and
    everything works fine. 
    
    Obviously ALL-IN-1 V3 and VMSINSTAL option "S" do not go together under
    the latest VMS releases. I can't give you more details.
    
    	hope that helps,
    	Stefan                         
1170.8Tailored system may cause this problem use options kclBUSHIE::SETHIMan from DownunderFri Jan 29 1993 00:3134
    Hi,                                     
    
    A customer reported that the installation was looping when linking the
    ALL-IN-1 image.  I have managed to solve this problem by asking the
    customer to do the following:
    
    Install/upgrade using the options kcl as ie 
    			$ @vmsinstal a1030 <disk> options kcl
    
    The trace produced the line that was causing the problem and it was
    
    A1$BUILD:OAFC$SMUIAL
    SYS$LIBRARY:VAXCRTL/LIBRARY/INCLUDE=(C$CTYPE)
    
    I asked the customer to do a $library/list SYS$LIBRARY:VAXCRTL.OBL and
    it came back with the error message file not found.  The customer had
    tailored off the VAX C rtl's.
    
    There are two other notes concerning looping problems in this
    conference topics 1677 and 1220 for your reference.
    
    Finally a suggestion in the installation guide is it possible to
    inform the customers not to install/upgrade ALL-IN-1 IOS on a tailored
    system.  What I would like to see is that the customer MUST tailor on
    and after the installation tailor off.  This would hopefully cut back
    on the number of calls regarding the looping problem and time wasting
    on the customers part.
    
    Regards,
    
    Sunil
    
    PS - Hong Le is our VMSINSTAL expert in this part of the world.  I
    shall call him Mr. KCL from now onwards.
1170.9The Installation Guide already has the necessary words...SCOTTC::MARSHALLSpitfire Drivers Do It ToplessFri Jan 29 1993 09:137
    Sunil,
    
    The Installation Guide, page 4-1, states that the system on which you
    are installing ALL-IN-1 "must be a full, untailored system."  This
    would appear to satisfy your request in .8.
    
    Scott