[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

1494.0. "ALL-IN-1 on a mixed VMS version Cluster" by MSDSWS::DUNCAN (Things can't get much worse..I Hope!) Thu Sep 24 1992 03:22

    I have the following problem:
    
    My customer just received a VAX 7000-610 and they have installed it in
    their existing cluster.  The 7000 requires VMS V5.5-2HW and the rest of
    the cluster is at VMS V5.4-x.  Everything is shared, but of course the
    system pack.  All the network and uaf data files are the same.  
    
    They have ALL-IN-1 on a VAX 9000-210 which runs at 100% all day and
    they need/want to move some of the ALL-IN-1 users to the 7000.
    
    First problem.  VMS V5.5-2HW will not allow a Cluster alais in a mixed
    versin cluster. So, I don't think I would want to run Message Router on
    it.  We do not allow EXPRESS mail so I don't think this would be a
    problem so long as the FETCHER and SENDER run on the other nodes in the
    cluster.
    
    Is there any problem with running ALL-IN-1 like this.  I figure it's
    not supported, BUT WILL IT WORK?
    
    After all, they have just bought our latest and greatest and now they
    want to use it.  It will only run like this for a month at which time
    the rest of the cluster will be upgraded to VMS V5.5-2.
    
    
    Thanks in advance (I hope),
    Darryl
T.RTitleUserPersonal
Name		DateLines
1494.1By George, I think it might work!IOSG::TALLETTArranging bits for a living...Thu Sep 24 1992 09:4522
    
    	Hmmm, this is an interesting one! You'd have to run the old
    	queue manager of course and I would do the ALL-IN-1 installation
    	or link or whatever on a V5.4 system so that the code thinks its
    	running on V5.4 and doesn't try to use any V5.5 features, but my
    	guess is that it would probably work. I've never heard of anyone
    	doing this so you are on your own, but you knew that already! :-)
    
    	The things I'm thinking of, just for others to check my logic:
    
    		OA$FORMATTER - should be okay as long as you don't mix
    				queue managers.
    		UAI$/set_password - links SYS.STB which shouldn't have
    				changed
    		FileCab Server - uses its own threads package, not the V5.5
    				one
    		Deferred image activation - should be ok, works on 5.4 & 5.5
    
    	Maybe someone can think of something that wouldn't work?
    
    Regards,
    Paul
1494.2Missed the second system disk on the first passIOSG::TALLETTArranging bits for a living...Thu Sep 24 1992 09:498
    
    	Just noticed that you would, of course, have a separate system
    	disk. Would you have a separate ALL-IN-1 installation and
    	separate UAF files? You might notice the inconsistency but
    	I still think it would work.
    
    Regards,
    Paul
1494.3system disk should be the sameMSDSWS::DUNCANThings can't get much worse..I Hope!Thu Sep 24 1992 11:1325
    I forgot to say this was ALL-IN-1 V2.4.
    
    
    I will have to double check how they built the system disk, but a lot
    of the second system disk files came from the first system disk.  
    
    No problem with the queue manager, they are at A5.5-2HW.  I forgot
    about the "A".
    
    The only thing I can think of that might cause a problem is if any of
    the sys$share files are not there, but I think I could take care of
    this.
    
    Note that I do not want to do a new installation.  I want to use all
    the existing ALL-IN-1 files which are available to both the A5.5-2HW
    node and the V5.4-x nodes.  The UAF, NETPROXY... are all the same as
    they were copied form the 5.4 systems.
    
    Again, I think is should work and of course will test before we turn
    users loose.  I just want to make sure that nothing major will break
    and screw up the entire cluster.
    
    
    Thanks,
    Darryl
1494.4Common UAF seems to make senseIOSG::TALLETTArranging bits for a living...Thu Sep 24 1992 17:488
    
    	I would define SYSUAF etc. to point to common files rather than
    	taking a copy.
    
    	Let us know how you get on.
    
    Regards,
    Paul