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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

123.0. "PCSI: how to move a product ?" by MUNICH::WWERNER (When in doubt, do as the INTs do) Fri Jan 31 1997 08:32

Assume SW product A on disk X, product B on disk Y, both installed with
/DESTINATION. Now one buys a new, large disk Z. Both products should be
moved to Z. No problem. But how to teach PCSI about this change ?
REMOVE and reINSTALL ? Use concealed devices with the old DISK$<label>
logical name ?

regards Wolfgang
T.RTitleUserPersonal
Name
DateLines
123.1re-INSTALLSTAR::HAMMONDCharlie Hammond -- ZKO3-04/S23 -- dtn 381-2684Fri Jan 31 1997 15:3612
123.2STAR::HAMMONDCharlie Hammond -- ZKO3-04/S23 -- dtn 381-2684Fri Jan 31 1997 16:5549
>Assume SW product A on disk X, product B on disk Y, both installed with
>/DESTINATION. Now one buys a new, large disk Z. Both products should be
>moved to Z. No problem. But how to teach PCSI about this change ?
>REMOVE and reINSTALL ? Use concealed devices with the old DISK$<label>
>logical name ?

.1 has been set hidden because I miss-spoke.  THIS is the correct scoop...

PCSI has a "feature" that causes it to IGNORE the /DESTINATION on an
upgrade.  Instead, it uses the original destination.  Therfore you cannot
move a product simply re reinstalling (a.k.a. upgrading) it.

(That this happens without notice/warning is a bug and is currently
being investigated by PCSI engineering.)

So the answer is:  

FIRST: PRODUCT REMOVE the product(s).  You must do this while the
old disk(s) are still present; otherwise the remove will fail.
If your product(s) create any configuration or work files that are NOT
installed by PCSI, you might want to preserve, copy and save them at this time.

NEXT: Remove the old disk(s) if you want to, and configure the new disk(s)
if you haven't already done so.

FINALLY: re-PRODUCT INSTALL the product(s).  You will have to re-do any
post-installation configuration tasks the product(s) require, possibly using 
the files you saved in step FIRST.


The current thinking tends to be that this is a relatively rare occurance
and that the REMOVE and re-INSTALL workaround is relatively easy.  So it
is unlikely that PCSI will be modified to provide any sort of "move" 
functionality.  If you disagree, please say so.


BTW -- of one of these old disks is the system disk, you can make an IMAGE
BACKUP of it, boot it, and then move the products form the other disk to the 
new system disk as described above.


CAUTION -- if you change the disk label of any disk on which PCSI has installed
products, you must execute a

    PRODUCT REGISTER LABEL <old-label> <device>

where <old-label> is the label that was on the disk at the time of the
PCSI installation, and <device> is the current physical device name.
(PCSI retrieves the new label from the device.)
123.3AUSS::GARSONDECcharity Program OfficeMon Feb 03 1997 16:417
re .2
    
>.1 has been set hidden because I mis-spoke.
    
    Notes> DEL NOTE[/NOCONFIRM]
    
    is preferable IMHO.