[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

2448.0. "Install ALL-IN-1 from batch?" by KERNEL::LOAT (Ahead groove factor 5! Yeah!) Mon Mar 22 1993 14:15

    
    A customer, who is a system manager for 17-18 systems on various sites
    is having a problem installing ALL-IN-1 from batch. He's got a command
    file which makes use of a stored answers file which works okay when he
    runs it interactively, but when he runs it in batch, it hangs. An
    extract from the log file is shown here:
    
%A1-I-A1LINK, Starting to link images

Building shared image modules
Shared image modules built
Linking the OA$MAIN image
%LINK-I-DATMISMCH, creation date of 17-JUN-1991 03:43 in shareable image
SYS$COMMON:[SYSLIB]FDVSHR.EXE;4 differs from date of 26-JAN-1989 18:22 in
shareable image library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1
Linking the Background Formatter
%LINK-I-DATMISMCH, creation date of 17-JUN-1991 03:43 in shareable image
SYS$COMMON:[SYSLIB]FDVSHR.EXE;4 differs from date of 26-JAN-1989 18:22 in
shareable image library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1
Linking the TM Server
%LINK-I-DATMISMCH, creation date of 17-JUN-1991 03:43 in shareable image SYS$COM
MON:[SYSLIB]FDVSHR.EXE;4   differs from date of 26-JAN-1989 18:22 in shareable i
mage library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1
Linking the OA$SUBMIT image
Linking the MAILCOUNT image
Linking the File Cabinet Server images
%LINK-W-OPENOUT, error opening MISSING:[MISSING]OAFC$MTS_PRIV_SHR.MAP; as output
-RMS-F-DEV, error in device name or inappropriate device type for operation
%LINK-W-WRNERS, compilation warnings   in module OAFC$MTS_PRIV_SHR file $1$DKA30
0:[INSTALL.A1030]OAFC$MTS_PRIV_SHR.EXE;1
%LINK-I-DATMISMCH, creation date of 17-JUN-1991 03:43 in shareable image SYS$COM
MON:[SYSLIB]FDVSHR.EXE;4   differs from date of 26-JAN-1989 18:22 in shareable i
mage library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1
%LINK-W-OPENOUT, error opening MISSING:[MISSING]OAFC$SERVER.MAP; as output
-RMS-F-DEV, error in device name or inappropriate device type for operation
Linking the RSD housekeeping procedure
Linking the Impersonation Services images

%A1-I-A1LINKED, Finished linking images
%OA-I-LASTLINE, "ALL-IN-1 running -- removing form libraries & TXL"
           SYSTEM finished using ALL-IN-1 at 18-Mar-1993 17:28
%A1-I-RNEPROF, Running command procedure EPROFIL.CA1
                                                      
    This is the point where the installation hangs. Is this valid to
    install ALL-IN-1 from a batch procedure? No-one here has heard of doing
    this before so I'm not sure that it a valid thing to try and do.
    
    Help?
    
    Steve.
    
T.RTitleUserPersonal
Name
DateLines
2448.1A very strange one indeedAIMTEC::WICKS_AOscar the Grouch is an Optimist!Mon Mar 22 1993 18:3419
    Steve,
    
    The FMS one is very strange since I haven't heard of a version of FMS
    created after Jan 1989 - does it happen if you relink the v2.4 system?
    on the couple of systems I have 1989 was the created date and 1992 
    the modified date (when ALL-IN-1 was installed).
    
    The last time I heard of a batch install was back in v2.3 days so
    that's definitely before the days of the File Cab Server which seems
    to be the second thing that complains - bit worrying to see compilation
    errors on that image and also it try to generate a MAP file.
    
    The third error I really don't have any ideas on - it's at the stage
    when it's about to run up ALL-IN-1 to do lots of CM conversions - would
    be nice to know what files were locked at the time.
    
    Regards,                                        
    
    Andrew.D.Wicks
2448.2LINK = "LINK/NOMAP"?SAHQ::WOLFEJohn Wolfe - (404)-924-6463Mon Mar 22 1993 19:048
	Not much help but the MAP problem is probably caused by /MAP being the
default for a batch mode link - see HELP LINK/MAP.  Defining 
LINK == "LINK/NOMAP" in LOGIN.COM would probably fix this piece of it.

HTH some

John
2448.3Missing /NOMAP is a bug IMO!IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Mar 24 1993 13:4520
    Re .2
    
    I didn't know (or actually, now I come to think about it, I knew, but
    I'd forgotten!!) that /MAP was the default for background links. I'll
    raise an internal bug so that we specifically add /NOMAP to all the
    links unless OPTIONS M has been specified to A1LNKDRV.
    
    I don't think that specifying the link symbol will help, because
    VMSINSTAL deletes (or "unscopes") all global symbols.
    
    Re .0
    
    The FDV errors are certainly interesting! Could there be something
    wrong with IMAGELIB.OLB?
    
    But anyway, don't batch installs have problems when we prompt for
    passwords? Since we don't use VMSINSTAL call backs to get the passwords
    (because we want to turn echo off) they don't use the auto-answer file.
    
    Graham

2448.4Sssssshhhhh . . .IOSG::SHOVEDave Shove -- REO2-G/M6Wed Mar 24 1993 17:334
    And putting passwords in the auto-answer file would break all kinds of
    security rules anyway!
    
    D.
2448.5KERNEL::LOATKeep passing the open windows...Fri Mar 26 1993 11:286
    
    Any ideas about why the installation hung or what info would help me
    find out?
    
    Steve.
    
2448.6Some thoughts...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeFri Mar 26 1993 19:1322
    I'd attempt to address the FDV version problem by reinstalling FMS. It
    would bprobably be worth trying a non-batch install on the same
    machine if possible to see if it is the batch environment that's causing
    the problem. If is is, then I couldn't say for sure that it was
    supported right now, although as I said in .-afew I see this particular
    error as a bug, since you could reasonably want to do a relink outside
    the install in batch, so we'll try to fix it in a PFR.
    
    If the customer wants to try and fix it. they'll have to open up the
    A1030.F saveset in the kit and modify the FCS link procedure to add a
    /NOMAP qualifier. It may be that the failing link is in fact causing
    something to break later.
    
    Alternatively, perhaps invocatrions of the image later in the install
    don't work because they're in batch and hence don't have a terminal,
    although since they're all /NOINIT, I don't see why...
    
    Perhaps it's the old problem with the deferred image stub builder
    failing for some reason, although we do enough links in batch that
    work!
    
    Graham