[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

3032.0. "installing ALL-IN-1 V3.0" by WOTVAX::HUMPHRIESN () Tue Jul 20 1993 18:35

I'm an instructor in Warrington UK, and one of my students has a question 
about moving an installed v3.0 ALL-IN-1 system to another node. I cannot 
find a V3 conference; would you either answer my question, or point me to 
the correct place to ask it?

The student has an existing machine with ALL-IN-1 V3.0 installed. He is 
getting a new vax which will have a new version of VMS installed on the 
system disk. He wants to copy the ALL-IN-1 files and directories from the 
old node to the new. He does not want to reinstall ALL-IN-1 on the new 
system.

Is this possible? If so, which directories does he copy? Does he have to 
alter a config file and relink on the target? What are the potential 
pitfalls? Is this documented anywhere?

Many thanks,

Nicola Humphries
T.RTitleUserPersonal
Name		DateLines
3032.1It all depends on a number of factors, need more info.GIDDAY::SETHIAhhhh (-: an upside down smile from OZWed Jul 21 1993 02:5358
    Hi Nicola,
    
    >I cannot find a V3 conference; would you either answer my question, or 
    >point me to the correct place to ask it?
    
    You have found it :-).            
    
>The student has an existing machine with ALL-IN-1 V3.0 installed. He is 
>getting a new vax which will have a new version of VMS installed on the 
>system disk. He wants to copy the ALL-IN-1 files and directories from the 
>old node to the new. He does not want to reinstall ALL-IN-1 on the new 
>system.

    Is this new VAX doing replace the old one ?  Is the configuration going
    to be exactly the same, in terms of logical names for disks etc ?  Is
    the node name going to be the same as the old machine ?  Does he have
    DDS installed ?
    
>Is this possible? If so, which directories does he copy? Does he have to 
>alter a config file and relink on the target? What are the potential 
>pitfalls? Is this documented anywhere?
    
    I can not say if this is possible it depends alot on the answers we get
    to the above questions.  If it is and I must stress "IF", he will have
    to install ALL-IN-1 IOS on the new machine as there are a number of
    executables that are placed in SYS$LIBRARY, that are required by
    ALL-IN-1 IOS.  Simply copying over the ALL-IN-1 directory structure
    will *NOT* work. Also your DCLTABLES are modified to include the ALLIN1
    verb.
    
    As always when you upgrade OpenVMS to a new version or apply patches
    *YOU SHOULD/MUST* relink ALL-IN-1 IOS.  In the case of say the OpenVMS
    6.0 upgrade it's recommended that ALL-IN-1 is relinked, failure to do
    so will mean that ALL-IN-1 IOS will not work.
    
    The bottom line is that the customer *MUST* install ALL-IN-1 IOS on the
    new system, as the result of not doing so will mean that he does not
    have a supported installation.  The local CSC may not be able to
    support the customer.
    
    Copying over the ALL-IN-1 IOS system has the potential of causing
    problems with PARTITION's on the system and shared drawers etc.  I
    don't think there is any documentation available and in any case if
    they had 2.4 installed it would have been far easier to achive what
    they wanted.
    
    I have listed a few pitfalls here and I am sure others will be able to
    give you more feedback, unless I have covered all the important bit
    8^).
    
    It looks like Digital could earn a few bucks out of all of this.  Ask
    the customer to contact his Accounts Manager to get a DEC body on-site
    to do this.  Bottom line is that they may need to do alot of work
    before hand to get things to work.
    
    Regards,
    
    Sunil
3032.2A few ways to do this...WOTVAX::PC0866::DoranBrain the size of a planet... but I still work here!Wed Jul 21 1993 15:2717
Hello Nicola...

An answer could depend on what the customer actually wants to achieve at the 
end of the day.

If the new box is there to replace the old box (more power, newer technology 
etc..), it's probably easiest to upgrade VMS on the old system and simply 
backup old to new (ie wipe out the system on the new box).

This would save worries about new node names, new DDS configs, new logicals 
etc. etc.

If you want to give me a call, I'm in K2 on 1347.

Cheers,

Andy