[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

4067.0. "Approach to ALL-IN-1 upgrade. Sanity check" by SEDOAS::DAVIES_G (GLYN DAVIES @ESO) Mon Apr 11 1994 15:32

    I am in the process of putting together a plan to upgrade a customer
    from ALL-IN-1 V2.4 to V3.0.
    
    I would appreciate a quike sanity check of what my current approach
    will be to see if anybody can find any problems.
    
    The customer has ALL-IN-1 which has been customised running on a live
    cluster.
    
    They also have a non customised version of ALL-IN-1 on a development
    system.
    
    My general approach is as follows:
    
    - Copy SITE directories from live to development system.
    	- Dont copy DAF file, PROFILE.DAT, PENDING but copy accross CM
          datafiles.
    
    - Perform an upgrade on the development system.
    	- Tidy up customisations
    	- Run CART
    	- Do pre-upgrade resolution
    	- Upgrade
    	- Post upgrade CART resolution
    	- Apply any re-customisations
    	- Test
    
    - Upgrade live system
    	- Perform a standard upgrade.
    	- After upgrade, blow away the site directories (exceot
          OA$SITE_DATA:
    	- Copy site areas from development system (SCP,LIB,BLP,HLP)
    	- Copy CM*.DAT files from developmement system
    	- Recompile TXL, Libraries etc
    
    I beleive that as long as the development system has been fully tested,
    the above should work?
    
    Any comments would be appreciated.
    
    Regards,
    
    Glyn

T.R Title User Personal
Name Date Lines

4067.1 IOSG::PYE Graham - ALL-IN-1 Sorcerer's Apprentice Tue Apr 12 1994 18:44 8

T.R	Title	User	Personal Name	Date	Lines
4067.1		IOSG::PYE	Graham - ALL-IN-1 Sorcerer's Apprentice	`Tue Apr 12 1994 18:44`	8
	See other notes here describing similar strategies. Your test system would probably need to have fairly identical disc names etc., to make the CM files work OK. Perhaps this isn't a problem if you keep the CM files which define the logicals to their own systems. Graham

    See other notes here describing similar strategies.
    
    Your test system would probably need to have fairly identical disc
    names etc., to make the CM files work OK. Perhaps this isn't a problem
    if you keep the CM files which define the logicals to their own
    systems.
    
    Graham