[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

4027.0. "Re-installing the SSB kit" by GIDDAY::LEH () Mon Mar 28 1994 01:56

One customer was planning to re-instal his IOS 3.0A system with official 
software to get rid of any possible remnants of fieldtest or incorrect 
components that had made into his system over a long period of time. This site 
participated in 3.0 EFT and later upgraded with supposedly SSB version; 
however, it wasn't sure if they had used the correct kit.

Australian sites are supposed to use Base + British lang + US market 
components and this combination has to be custom-made by local distribution. 
Some 2 or 3 incorrect kits presumably of wrong combination were sent out thus 
making not possible to determine if the correct kit had been installed at this 
site. They also couldn't rule out the possibility of a CDROM kit being used 
i.e. either (American) English or British English kit was used.

This re-instal plan was essentially to save data files and customizations 
prior to the installation, and restore them after. It was realized of many 
potential pitfalls, so a trial has been done and the plan is constantly 
revised; however, it was presented herein to seek more advices before the 
D-day, just a week a way. Please ignore the mentioning of those custom 
applications at this site.

Thanks for your comments

Hong
CSC Sydney

===============================================================================

Updated version in .1		GAP.

T.RTitleUserPersonal
Name
DateLines
4027.1The final version of check list. Used on a live systemGIDDAY::SETHIBetter to ask a question than remain ignorantMon Apr 11 1994 07:06368
    Hi GAP and All, 
    
    The customer did the upgrade this weekend and we have been very
    successful both in terms of getting the kit installed/tested and in
    saving time.  Basically we cut the time by half because we used rename
    rather then backup or delete commands, all will be revealed in the
    check list.
    
    Also listed in the check list are timings for each phase for a 6240
    processor.  I hope this check list is of some help to someone out
    there.  We chose the belt and braces approach so it may have additional
    steps for safty.
    
    Andy Joyce went over the check list just in case the customer and I
    had overlooked anything, so thanks Andy.
    
    Regards,
    
    Sunil
    

                                       Reinstall ALL-IN-1 on PEROS

                                                Checklist


REMOVE ALL-IN-1 AND ASSOCIATED PRODUCTS.

         PRIOR TO DAY OF RE-INSTALL:

1.       Clean up customisation areas

2.       Print out details of the following :

         2.1     Application Details (from ALLIN1 Manager: MA, PA)
         2.2     List of all live elements (also live location details)
         2.3     Account details (VMS and ALLIN1 and DDS) for the following :
                 2.3.1   ALLIN1, A1$XFER_IN, A1$XFER_OUT, A1$SCRIPT, 
    		         OAFC$DEFAULT, OAFC$SERVER, A1FETCHER, A1SENDER.
         2.4     WPCORP format details
         2.5     List of all ALLIN1 logicals
                 2.5.1   OA$*, WPL$*, SMBSRVSHR

3.       Login as ALLIN1 MANAGER and store all site customisations, package and
    	 send to self (and perhaps a separate ALLIN1 system, e.g. 
    	 MANAGER@A1@KAROS). Ensure that each is mail as a separate package -
         don't send as one otherwise cannot use FAE to restore later if 
    	 required). This step is for insurance in case we need to reload 
    	 customisations via the customisation management subsystem later.

         3.1     OA BRITISH and SHARE (site elements only)
         3.2     REM (reminders base elements only - may need to set OEG flag=1
    		 to allow storage)
         3.3     PMF (phone base elements only)
         3.4     MIG (migration base elements only - may need to set OEG flag=1)
         3.5     WPCORP elements

4.       Review installation guide and pre-requisites.

         ON DAY OF RE-INSTALL:

         Commence Backups

5.       Shut down system to release shadow sets (close all files).
6.       Standalone backup of all disks except DISK$USER13 and DISK$USER20 
    	 (perform minimum startup to keep open files to minimum). Use shadowed
    	 disks for backup purposes.

7.       Bring up system (one node only - PER1). Disable logins.
         (30 min)

         Prepare System

8.       Stop Message Router Transport Service to stop mail arriving in A1 
    	 mailbox then allow sender/fetcher to clear out mailbox. This mailbox 
         must be empty before it can be deleted later.

         8.1     $@SYS$MANAGER:MB$CONTROL STOP=TS

9.       Abort Fetcher and Sender.

10.      Stop OA$FORMATTER_node queues  (use MJQ under ALLIN1 manager or 
    	STOP/QUEUE/NEXT OA$FORMATTER_PER1 ...).

11.      Stop OA$BATCH queues (pause housekeeping procedures)

12.      Stop OA$SCRIPT_BRITISH queues.

13.      Shutdown ALL-IN-1.
         (30 min)

         Backup Data and LIB Areas

14.      Backup OA$DATA/OA$LIB
         14.1    DISK$SYS3:[ALLIN1...]*.*;*
         14.2    DISK$SYS6:[ALLIN1...]*.*;*

15.      Take copy of SYS$STARTUP:OAFC$STARTUP.COM. This file contains 
    	 the customers changes to set Filecabinet Server process quotas. When 
    	 reinstalling don't change this file.  Instead create logicals and put
         them in SYS$COMMON:[SYSMGR]SYLOGICALS.COM. (As per ALLIN1 Manager's 
    	 Guide - Tuning ALLIN1). (15 min)

         Remove ALLIN1

16.      Deinstall WordPerfect OA30 Integration (page 25 WordPerfect manual - 
    	 Integration for ALLIN1)

         16.1    @SYS$STARTUP:WPCORP$STARTUP "" DEINSTALL DEINTEGRATE
         (10 min)

17.      Remove the following usernames from the system UAF.  Be sure to take 
    	 a copy of information like quotas, etc, before removal.

         Usernames:
         .       ALLIN1
         .       A1$XFER_IN
         .       A1$XFER_OUT
         .       A1$SCRIPT
         .       OAFC$DEFAULT
         .       OAFC$SERVER

         Resource Identifiers (DON'T delete these , but print out details):
         .       OA$ADMIN
         .       OA$PRVAPP
         .       OA$MANAPP
         .       OA$MANAGER
         .       OA$MAIL_ACCESS
         .       OA$USER_QM
         .       OAFC$SYSMAN

18.      Note down DISKQUOTA entry on disks.

19.      Disable DISKQUOTA entry on disks.
         (30 min)

20.      Remove A1 mailbox from Message Router -

                 $MC MRMAN
                 >DELETE A1
         (5 min)

21.      Purge mail areas to reclaim space from old SDAF files :
         21.1    $PURGE OA$SHARE:*.*
         21.2    $PURGE OA$SHARA:*.*

22.      Rename the shared mail areas -

         OA$SHARA

         22.1    DISK$SYS6:[OA$SHARA]
         22.2    DISK$SYS7:[OA$SHARA]
         
         OA$SHARE

         22.3    DISK$SYS4:[ALLIN1]
         22.4    DISK$SYS4:[OA$SHARE]
         22.5    DISK$SYS3:[OA$SHARE]
         22.6    DISK$SYS6:[OA$SHARE]
         22.7    DISK$SYS7:[OA$SHARE]

23.      Rename ALL-IN-1 directory structures (including base, customisations, 
         etc If SUFFICIENT disk space
         available)
         23.1    DISK$SYS3:[ALLIN1]
         23.2    DISK$SYS6:[ALLIN1]

         If INSUFFICIENT disk space, delete the directory structures (must be 
    	 backed-up first !)
         23.3    $DELETE DISK$SYS6:[ALLIN1...]*.*;*
         23.4    $DELETE DISK$SYS3:[ALLIN1...]*.*;*

                 (Run several times to delete complete directory structure. 
    		  May need to change directory file protections to allow 
    		  deletions).
         
24.      Deassign logicals prior to install -
         24.1    $@deassign smbsrvshr_wpcorp/exec/table=LNM$SYSTEM_TABLE

                 SMBSRVSHR*
                 OA$*
                 WPL$*
         (20 min)

INSTALL ALL-IN-1

25.      Install ALL-IN-1 from CD-ROM (may need Mail Directory user agent 
    	 password and Message Router mail box password)

         25.1    Answer 0 to the following question to avoid the User Agent 
    		 being removed from the DDS. Will have to change the logical 
    		 OA$DDS_PRIME later.

                 25.1.1 What level of mail directory support do you want ? 0
         
         25.2 Device to hold ALLIN1 shared library files : DISK$SYS6
         25.3 Device to hold ALLIN1 shared data files : DISK$SYS3
         25.4 Device to hold ALLIN1 BRITISH language files : DISK$SYS6
         25.5 Device to hold mail files - irrelevant since will restore these 
    	      entirely

(5 hours for V3.0 install on VLC)

26.      Perform post-installation tasks if relevant (chapter 10 of 
    	 installation guide).
         26.1    DO NOT Set up mail directory as this will attempt to create 
    	         USER AGENT in DDS again (10.12)

INSTALL PATCHES

27.      NOTE: Do not use SITELINK since no customisations apply and 
    	 WordPerfect not integrated at this stage. Also don't need to 
    	 de/re-assign logical SMBSRVSHR since WordPerfect not yet integrated.

         27.1    Shut down ALLIN1 and follow instructions in release notes 
    	         (for MUPA this is section 3.3)
         27.2    Install patches (e.g. MUPA)
         27.3    Post-installation tasks (section 5.1 of release notes)
                 27.3.1  Log in as ALLIN1 MANAGER
                 27.3.2  $SET DEF OA$BUILD_LLV
                 27.3.3  @OA$BUILD_SHARE:A1_MUPA030_RELINK 
                 27.3.4  ...
                 27.3.5  Compile TXLs and form libraries (no site application 
    			 form libraries at this stage)
                 27.3.6  Run post-installation procedure
                         27.3.6.1    $@OA$BUILD_SHARE:A1_MUPA030_POST_INSTALL

(1 hour for V3.0A install on VLC)

         27.4    Restart ALL-IN-1
         27.5    Run IVPs
(30 min)

28.      Compare data files in new areas with customer's areas (use DIFF 
    	 utility).
         28.1    FORMAT.DAT
         28.2    OA$PRINTSTYLES.DAT
         28.3    etc

At this point will have clean, uncustomised ALL-IN-1 system running at
    version 3.0A

RESTORE CUSTOMERS ENVIRONMENT

RESTORE DATA AREAS

         NOTE:   IF USING BACKUP, Use BACKUP input output/BY_OWNER=ORIGINAL 
    		 when restoring files

         If data directories were renamed previously,  should be able to 
    	 merely rename directories back to new structure.

29.      Shut down system and perform minimum startup - ALLIN1 files all closed.

30.      Rename OA$DATA directories (new installed versions) to ..._new

31.      Restore original OA$DATA directories (rename back)
         31.1    DISK$SYS3:[ALLIN1.DATA_SHARE]
         31.2    DISK$SYS6:[ALLIN1.DATA_BRITISH]

32.      Restore Shared Mail areas (rename back)
         32.1    OA$SHARE, OA$SHARA

33.      Restore Admin data
         33.1    DISK$SYS6:[ALLIN1.ADMIN_DATA]

34.      Restore OA$GROUP (system groups)
         34.1    DISK$SYS6:[ALLIN1.GROUP_SHARE]

35.      Restore OA$SYSTEM_LISTS (system distribution lists)
         35.1    DISK$SYS6:[ALLIN1.SYSTEM_LISTS]

36.      Restore OA$LOG (ALLIN1 log files) 
         36.1    DISK$SYS6:[ALLIN1.LOG]

37.      Restore ALLIN1 MANAGER's profile and transfer directories.
         37.1    DISK$SYS3:[ALLIN1.MGR]
         37.2    DISK$SYS3:[ALLIN1.TRANSFER_INCOMING]
         37.3    DISK$SYS3:[ALLIN1.TRANSFER_OUTGOING]
         37.4    DISK$SYS3:[ALLIN1.A1FETCHER]
         37.5    DISK$SYS3:[ALLIN1.A1SENDER]

38.      Restore UAF entries to reset process quotas, privileges and 
    	 identifiers etc.
         38.1    ALLIN1
         38.2    A1$XFER_IN
         38.3    A1$XFER_OUT
         38.4    A1$SCRIPT
         38.5    OAFC$DEFAULT
         38.6    OAFC$SERVER

39.      Restore customisations
         39.1    DISK$SYS3:[ALLIN1.SITE]
         39.2    DISK$SYS6:[ALLIN1.SITE]
         39.3    DISK$SYS3:[ALLIN1.MIG]
         39.4    DISK$SYS3:[ALLIN1.PMF]
         39.5    DISK$SYS3:[ALLIN1.REMINDERS]

40.      Bring up system

41.      Shut down ALLIN1. Note: When system is brought up it will define 
    	 OA$DDS_PRIME = 2 again. Redefine OA$DDS_PRIME = 0 before attempting 
    	 to shutdown ALLIN1, otherwise you will get the error "..form USERAGENT
    	 not in library" since ALLIN1 has been linked without DDS support. Also
    	 will need to reset MRM Mailbox password if this was changed during 
    	 re-install since ALLIN1 will only know about the old password because
    	 we have restored the data areas now (use manager's CMP option to do 
    	 this).
         
42.      Adopt the MAIL directory as the primary (since we did not during the 
    	 install to avoid changing the DDS in any way). Refer to Mail Manager's
    	 Guide p3-10.
         42.1    $DEFINE /SYSTEM /EXEC OA$DDS_PRIME 2
         42.2    ALLIN1 must now be re-linked (see ALLIN1 Manager's Guide for 
    	         procedure).

43.      Restart ALL-IN-1
                 43.0.1  @SYS$STARTUP:A1V30START DISK$SYS3:[ALLIN1.DATA_SHARE]

INSTALL WORDPERFECT INTEGRATION, INCLUDING PATCHES.

44.      Log in as SYSTEM
45.      @SYS$STARTUP:WPCORP$STARTUP "" REINSTALL REINTEGRATE (installs images
    	 and integrates queues)

46.      Log in as ALLIN1 manager
47.      @WPCORP$OA30DIR:WPCORP$OA30_INTEGRATE (integrates WordPerfect into 
    	 ALLIN1, installs WordPerfect customisations and does re-link.)
(45 minutes on a VLC)

48.      Restore WordPerfect customisations (Customers versions) since the step
    	 to integrate WordPerfect loads the default versions. Recompile form 
    	 libraries and TXL as instructed by ALLIN1.

49.      Re-run ALLIN1 IVPs and perform any corrective actions until IVPs run 
    	 clean

         49.1    Note: The owner of OA$DATA:PROFILE.DAT must be the same as the
    		 owner of OA$LIB:MUA_CREATE.COM ([ALLIN1]), otherwise account 
    		 create IVP will fail when attempting to submit job to batch 
    		 using A1SUBMIT. To change, do set file oa$data:profile.dat
    		 /owner=[ALLIN1] when ALLIN1 is shut down.

         49.2    Check ownership of housekeeping procedures since these may 
    		 have changed, especially check the following site procedures 
    		 whose ownership was [OA$MANAPP] but should have been [ALLIN1]
                 :
                 49.2.1  OA$LIB:SM_UUC.COM, SMSCHREO.COM, SM_MRJU.COM
         
         49.3    Check version of OA$LIB:SMJACKET.COM. If version number has 
    		 changed, housekeeping jobs currently submitted to batch will 
    		 fail. RESUBMIT housekeeping procedures (or rename to expected
    		 version number if necessary).

         49.4    Check that Mailbus Conversion Manager runs ok - may have 
    		 problem with protection on file OA$LIB:WPSDEF.WPL. If so, 
    		 change to W:RE.

50.      Check Formats (WPCORP, etc) and profiles

51.      Reboot and perform testing according to test plan.

52.      Check Housekeeping Procedures and re-submit any which failed to run 
    	 during the re-install.

53.      Hand system over to users.