HP 3000 Manuals HP 3000 Manuals
Moving Back to Release 1.0 by Carl Cicero, Commercial Systems Division INTRODUCTION This article documents the supported methods for moving from Release 1.1 back to Release 1.0. These instructions have been provided in case an unlikely situation occurs where it becomes necessary to make this type of move. Please note that The MPE XL Installation And Update Manual (P/N 36123-90001 R2815 or earlier) is referenced in this article and should be used in conjunction with these instructions.
NOTE It is highly recommended that a complete backup of the Release 1.0 system be performed before updating to Release 1.1.
There are two basic situations which may invoke a move back to Release 1.0. First, you are unable to successfully complete the move from Release 1.0 to Release 1.1 and now wish to get back to Release 1.0. Second, after being up on Release 1.1, circumstances warrant a decision to move back to Release 1.0. Instructions for handling these situations are provided in this article. Currently, there are four basic methods being supported for moving from Release 1.1 back to Release 1.0. They are: a. An UPDATE using no Release 1.0 backup tapes b. An UPDATE using Release 1.0 Customized System Load Tape and Release 1.0 backup tapes. c. An UPDATE using Release 1.0 Factory System Load Tape and Release 1.0 backup tapes. d. An INSTALL using Release 1.0 tapes. In order to perform an UPDATE back to Release 1.0, the system must have been successfully shutdown on Release 1.1 (i.e., The SHUTDOWN COMPLETE message displayed on the console.) The type of UPDATE depends on the availability of specific backup tapes. For systems that cannot be completely shutdown on Release 1.1, an INSTALL is required to get back to Release 1.0. The instructions for moving back to Release 1.0 are divided into 4 sections. The first section provides instructions for moving back to Release 1.0 after an unsuccessful move to Release 1.1. The second section describes how to perform a complete backup and shutdown. The third section documents the individual UPDATE and INSTALL methods. And the last section describes the restoring of other system components. I. AN UNSUCCESSFUL MOVE TO RELEASE 1.1 This section provides instructions on how to move back to Release 1.0 after being unable to successfully complete the move to Release 1.1. The necessary steps to move back to Release 1.0 depend on where the system was during the update process when the problem occurred. Follow the instructions that match your situation. a. If the initial Release 1.1 UPDATE from the Factory System Load tape fails due to an out of disc space condition: 1. You can either INSTALL Release 1.1 or Release 1.0. If you want to INSTALL Release 1.0 refer to "An INSTALL To Release 1.0" in section 3 of this article. b. If the initial Release 1.1 UPDATE from the Factory System Load tape fails due to I/O failures: 1. Have the I/O problem corrected and try this UPDATE over again. c. If the initial Release 1.1 UPDATE from the Factory System Load tape succeeds and the system was started but you never started AUTOINST: 1. Shutdown the Release 1.1 system and wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. 2. Reset the system, boot from the alternate boot path and perform an UPDATE using your Release 1.0 Customized or Factory System Load Tape. *** GO TO SECTION IV *** d. If you ever started AUTOINST on your Release 1.1 system, you can consider your system up on Release 1.1. Proceed to section II of this document for instruction on moving back to Release 1.0. II. BACKUP AND SHUTDOWN The first step in moving back to Release 1.0 is to perform a backup of the Release 1.1 system. 1. Log on the console as MANAGER.SYS,PUB and make sure everyone stays off the system. 2. Make sure that all members of the system volume set are mounted. 3. Make sure that all dismountable volume sets have been properly closed. If a dismounted volume set was mounted at the time of a system abort or a shutdown that did not complete on Release 1.1, you will have to mount all members of each set. To close them, do either: a. Leave them online so that they will be closed during the subsequent shutdown or b. Explicitly close them now by entering: :VSCLOSE xxx;NOW where xxx is the name of a dismountable volume set. Repeat as needed. NOTE: While mounting each dismountable volume set, you will want to properly close all databases contained within. Instructions are listed below. 4. Close all databases properly. *** DATA BASE NOTES *** For TurboIMAGE/XL, the MPE/V system-level control block (DBS) has been replaced by a permanent file in PUB.SYS, namely TURBODBS. The structure of this file is forward compatible from Release 1.0 to 1.1, but NOT backward compatible. To move from Release 1.1 back to 1.0, PURGE the TURBODBS.PUB.SYS file. This can be accomplished via a special entry point provided in DBDRIVER. From MANAGER.SYS: a. RUN DBDRIVER.PUB.SYS,OOPS b. Respond 'Y' to the prompt. The same "OOPS" entry point of DBDRIVER.PUB.SYS can be used by a database creator to purge '-GB' files. As of TurboIMAGE/XL, the database globals and database buffers control blocks are contained in a permanent file which has the format "<dbname>GB.<dbgrp>.<dbacct>". The '-GB' files exist only while the database is open, so '-GB' files should NOT exist unless some type of system interruption had occurred, and the database had not since been opened. The format of '-GB' files between 1.0 and 1.1 is different and will prevent a successful opening of a database if the wrong version exists. As the database creator: a. RUN DBDRIVER.PUB.SYS,OOPS b. Respond 'N' to the first prompt. c. Respond 'Y' to the second prompt. d. Supply the database name to the final prompt. 5. Shutdown user logging. a. Enter the following command to determine if user logging processes are running: :SHOWLOGSTATUS b. If logging processes are running on your system, a message similar to the following will be displayed: -------------------------------------------------------------- | | | LOGID CHANGE AUTO USERS STATE CUR REC MAX REC % USED | | | | SHPLOGID YES YES 1 ACTIVE 120 10016 1% | | ORBLOGID YES YES 9 ACTIVE 3812 10016 38% | | | -------------------------------------------------------------- c. If logging processes are running, terminate them, as shown below. (Substitute the logid(s) shown in Step 5b for logid.) :LOG logid,STOP 6. Ensure that as much system logging information can be backed up as possible by entering: :SWITCHLOG 7. Shutdown any networks by entering: a. :NSCONTROL ABORT b. :NETCONTROL STOP c. :RUN NMMAINT.PUB.SYS,SHUTDOWN (This will shutdown logging, tracing and NMMON) 8. Backup system and user files by entering: :STORE @.@.SYS,@.@.@-@.@.SYS ; ; DIRECTORY;SHOW=OFFLINE 9. Backup spool files by entering: a. Stop all spoolers via STOPSPOOL ldev commands NOTE: If you have started a spooler on an ldev that does not have an actual printer attached to it, you will have to ABORTIO on the ldev until the spooler stops. b. Store spool files to tape. :FILE SPTAPE;DEV=TAPE :SPOOK >OUTPUT @.@;*SPTAPE [;PURGE] >EXIT NOTE: The brackets indicate that the purge option is optional. Using it gains additional disc space for the update if you are running low on space. 10. Purge the file NMCONFIG as follows: :PURGE NMCONFIG.PUB.SYS 11. Purge the DTC download file as follows: :PURGE DTCSW001.PUB.SYS 12. Purge the AUTOINST staging file and groups as follows: :PURGE HPINSTFL :PURGEGROUP USL :PURGEGROUP UXL :PURGEGROUP UNL 13. Rename the SYSSTART file as follows: :RENAME SYSSTART.PUB.SYS,filename (record this filename for later use) 14. Power down all DTCs. 15. Shutdown the system by entering: cntl-A = SHUTDOWN Wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. III. PERFORMING AN UPDATE OR INSTALL If you have successfully shutdown your Release 1.1 system, you may UPDATE back to Release 1.0. The type of UPDATE depends on the availability of specific backup tapes. If you cannot completely shutdown Release 1.1, an INSTALL is required to go back to Release 1.0. Choose the appropriate set of instructions provided below. An UPDATE Using No Backup Tapes. If you want to do an UPDATE back to Release 1.0 from your successfully shutdowned Release 1.1 system, but DO NOT have a complete system backup of Release 1.0, you will have to do the following: 1. UPDATE the system with your Release 1.0 Factory System Load Tape (FSLT) and use AUTOINST to build the Release 1.0 system from the FOS and SUBSYS tapes. Refer to section 3 of the HP3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2815 or earlier) *** END OF INSTRUCTIONS. DO NOT CONTINUE. *** An UPDATE Using Customized System Load Tape And Backup Tapes. If you want to do an UPDATE back to Release 1.0 from your successfully shutdowned Release 1.1 system using Release 1.0 backup tapes and a Customized System Load Tape (CSLT), do the following: 1. If you kept your customized configuration in CONFIG.SYS, a. Mount the CSLT on the tape drive and boot from the alternate boot path and enter at the console: ISL>UPDATE CONFIG b. Boot from disc and enter: ISL>START NORECOVERY 2. If you kept your customized configuration in some other group in the SYS account that has been saved on your CSLT (such as CONFG930, CONFG950, etc.): a. Mount the CSLT on the tape drive and boot from the alternate boot path and enter at the console: ISL>UPDATE b. Boot from disc and enter: ISL>START GROUP=xxx NORECOVERY where xxx is the appropriate group name. (for example: GROUP=CONFG950) *** GO TO SECTION IV *** An UPDATE Using Factory System Load Tape and Backup Tapes. If you want to do an UPDATE back to Release 1.0 from your successfully shutdowned Release 1.1 system using backup tapes and a Release 1.0 Factory System Load Tape (FSLT), do the following: 1. Mount the FSLT on the tape drive and boot from the alternate boot path and enter at the console: ISL>UPDATE 2. Boot from disc and enter: ISL>START GROUP=CONFG9xx NORECOVERY where 9xx is the appropriate series number. *** GO TO SECTION IV *** An INSTALL To Release 1.0. If you cannot completely shutdown your Release 1.1 system, then you must do an INSTALL using the following steps: 1. Mount either a Release 1.0 Customized SLT or a Release 1.0 Factory SLT on the tape drive and boot from the alternate boot path and enter at the console: ISL>INSTALL 2. Boot from disc. a. If you installed from a CSLT with a customized configuration in CONFIG.SYS, boot from the disc and enter: ISL>START NORECOVERY b. If you kept your customized configuration in some other group in the SYS account that was saved on your CSLT, boot from disc and enter: ISL>START GROUP=xxx NORECOVERY where xxx is the appropriate group name. c. If you installed from a FSLT, boot from the disc and enter: ISL>START GROUP=CONFG9xx NORECOVERY where 9xx is the appropriate series numbers. *** GO TO SECTION IV ***