HP 3000 Manuals HP 3000 Manuals
Moving Back to Release 2.0 by Maria Molinos Commercial Systems Division INTRODUCTION This article documents the supported methods for moving from Release 2.1 back to Release 2.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 HP 3000 MPE XL Installation And Update Manual (P/N 36123-90001 R2943 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 2.0 system (System Load Tape and full system STORE) be performed before updating to Release 2.1. * Before updating or installing with the Factory System Load Tape (FSLT), FOS and SUBSYS tapes, check with your SE for patch information.
There are two basic situations which may invoke a move back to Release 2.1. First, you are unable to successfully complete the move from Release 2.0 to Release 2.1 and now wish to return to Release 2.0. Second, after being up on Release 2.1, circumstances warrant a decision to move back to Release 2.0. Instructions for handling these situations are provided in this article. The instructions for moving back to Release 2.0 are divided into 5 sections. The first section provides instructions for moving back to Release 2.0 after an incomplete move to Release 2.0. The second section describes how to perform a complete backup and shutdown. The third section documents the individual UPDATE and INSTALL methods. The fourth section describes the restoring of other system components. The last section contains issues and compatibility problems for different products. I. AN INCOMPLETE MOVE TO RELEASE 2.1 This section provides instructions on how to move back to Release 2.0 after an incomplete move to Release 2.1. The necessary steps to move back to Release 2.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 2.1 UPDATE from the FSLT fails due to an out of disk space condition: 1. You can attempt an UPDATE with: 1.1 First, the 2.0 CSLT 1.2 Second, the 2.0 FSLT 1.3 If neither UPDATE works, then do an INSTALL. Refer to section 3 of this article for UPDATE and INSTALL instructions. b. If the initial Release 2.1 UPDATE from the FSLT fails due to I/O failures: 1. Have the I/O problem corrected and try this UPDATE over again. c. If the initial Release 2.1 UPDATE from the FSLT succeeds and the system was started but you never started AUTOINST: 1. Shutdown the Release 2.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 2.0 CSLT. 3. Rename the file SYSSTART to its original name :RENAME filename, SYSSTART 4. Set system passwords and reset catalogs. d. If you ever started AUTOINST on your Release 2.1 system, you can consider your system up on Release 2.1. Proceed to section II of this document for instruction on moving back to Release 2.0. II. BACKUP AND SHUTDOWN The first step in moving back to Release 2.0 is to perform a backup of the Release 2.1 system. 1. Make sure that all members of the system volume set are mounted. 2. Make sure that all mountable 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 2.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 mountable volume set. Repeat as needed. _________________________________________________________________ NOTE While mounting each mountable volume set, you will want to properly close all databases contained within. _________________________________________________________________ 3. Close all databases properly. 4. Follow instructions on section 2 of the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2943 or earlier). 5. Purge the file NMCONFIG as follows: (optional) :PURGE NMCONFIG.PUB.SYS 6. Shutdown the system by entering: CONTROL = SHUTDOWN Wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. 7. Continue with section III of this document for an UPDATE or INSTALL. III. PERFORMING AN UPDATE OR INSTALL Currently, there are five methods supported for moving from Release 2.1 back to Release 2.0. They are: a. An UPDATE using Release 2.0 Factory tapes only (FSLT, FOS and SUBSYS tapes) b. An UPDATE using Release 2.0 Customized System Load Tape (CSLT) and Release 2.0 full system STORE tapes. c. An UPDATE using Release 2.0 Factory Tapes (FSLT, FOS and SUBSYS tapes) and Release 2.0 full system STORE tapes. d. An INSTALL using Release 2.0 CSLT and Release 2.0 full system STORE tapes. e. An INSTALL using Release 2.0 Factory tapes (FSLT, FOS and SUBSYS tapes) and Release 2.0 full system STORE tapes. If you have successfully shutdown your Release 2.1 system, you may UPDATE back to Release 2.0. The type of UPDATE depends on the availability of specific backup tapes. Use AUTOINST to build the Release 2.0 system. Refer to the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2943)
NOTE The Release 2.1 configuration files are not compatible with the 2.0 configuration files. If you CANNOT use your backup tapes, you MUST build the configuration from scratch, as it is a first-time installation.
IV. RESTORING OTHER SYSTEM COMPONENTS FOR UPDATE ONLY ----------------- 1. Log on the console as MANAGER.SYS,PUB and make sure everyone stays off the system. 2. If you renamed the file SYSSTART, reinstate the original name by entering: :RENAME filename,SYSSTART 3. RESTORE the NMCONFIG file by mounting your Release 2.0 full system STORE tapes and entering: :RESTORE ;NMCONFIG.PUB.SYS;DEV=1 4. Run NMMGR and validate your network configuration. Obtain a print out of the 2.1 critical summary before attempting to go back to Release 2.0. Use this print out to manually add the devices which have been added to your system since the update to Release 2.1. :NMMGR 5. Run SYSGEN to cross validate the network configuration against the system configuration by entering: :SYSGEN CONFIG (To ensure config files are on ldev1) At this time, get into the sysfile configurator and execute the SHOW command by entering: sysgen> SY sysfile> SH DCC If in the resultant display is NMCONFIG FILE = NONE then add your network configuration, so that it will be on your CSLT, by entering: sysfile> RDCC NMCONFIG.PUB.SYS Leave the Sysfile Configurator and quit SYSGEN by entering the following: sysfile> HOLD sysfile> EXIT sysgen> KEEP (DO a KEEP even if you have not changed anything) sysgen> EXIT 6. RESTORE the Release 2.0 configuration files from your back up tapes: :RESTORE;@.CONFIG.SYS;DEV=1 FOR BOTH UPDATE AND INSTALL ------------------------------ 1. Shut the system down CONTOL = SHUTDOWN Wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. 2. Reset the system, boot from disk (i.e., the primary boot path), and enter on the console: ISL>START NORECOVERY or ISL>START NORECOVERY This will default to the CONFIG.SYS group. 3. RESTORE spoolfiles if you wish at this point. (Refer to Section V of this manual for information on new spooler commands.) V. ISSUES AND COMPATIBILITY PROBLEMS This section describes all the issues and compatibility problems you should be aware of when moving back to Release 2.0 from Release 2.1. Languages New versions of most compilers and run-time libraries have been submitted to Release 2.1. This may cause some backward compatibility problems with programs compiled on Release 2.1. If the system is back-dated to 2.0, all programs in any language need to be recompiled and relinked or restored from 2.0 back-up tapes. MPE XL Subsystems NM SPooler In order to migrate spoolfiles back to Release 2.1, use the new spooler utility SPFXFER (SpoolFile Tape Transfer). This utility will transfer spoolfiles to tape with a format that is capable of being input by SPOOK on the CM Spooler from previous XL releases to 2.1. :FILE SPTAPE;DEV=TAPE :SPFXFER >INPUT @.@;*SPTAPE >EXIT Database Management The database management products available on Release 2.0 and Release 2.1 are the following: -------------------------------------------------------------------------------------------------- | | | | | | | On 2.0? | On 2.1? | Structural | | | | | Changes? | | | | | | -------------------------------------------------------------------------------------------------- | | | | | | TURBO/XL | Yes | Yes | No | | | | | | | TURBO QUERY/XL | Yes | Yes | No | | | | | | | DBCHANGE/XL | Yes | Yes | No | | | | | | | ALLBASE HP SQL/XL | Yes | Yes | Yes | | | | | | | ALLBASE QUERY/XL | Yes | Yes | Yes | | | | | | | ALLBASE 4GL/XL | Yes | Yes | Yes | | | | | | | ALLBASE NET/XL | Yes | Yes | No | | | | | | -------------------------------------------------------------------------------------------------- Depending on the product, you may or may not have to follow special instructions. So here is a productwide listing: a. For TURBO/XL, there are no structural changes between Release 2.0 and 2.1. So TURBO will not cause any compatibility problems. Simply RESTORE from the 2.1 back-ups all TURBO data and application files. b. For TURBO QUERY/XL, there are no structural changes between 2.0 and 2.1. But this product does use NLS features. This implies that the pertinent version of 2.0 must have all the NLS fixes that are available in the 2.1 version. c. DBCHANGE/XL does not have any structural changes. There are no issues when moving back from Release 2.1 and Release 2.0. d. For HP SQL/XL, please note the following: * The DBECon file has defined a new field for 2.1 HP SQL. This does not mean a format change, but it implies that some SQLUTIL scripts written for 2.1 DBEnvironments will not work with 2.0 SQL and vice versa. * Further, 2.1 SQL has new functionality like concurrency enhancements, date time, etc. If, after moving to 2.1, the user has started to use these features, a regression to 2.0 will render these new applications unusable. * A migration tool called ALLBASE/SQLMIGRATE is available to perform the backward migration from Release 2.1 to Release 2.0. Please refer to the ALLBASE/DATABASE Administration Guide for more information. e. For the ALLBASE/QUERY product, there are no additional issues. f. For ALLBASE 4GL applications unloaded from Release 2.1 are not backward compatible with Release 2.0. There have been structure changes for the new TurboImage interface and for the support of binary data types. The source for applications can be migrated backward from Release 2.1 to Release 2.0 with some modifications using HP4STOA and HP4ATOS. Application Tools The following information addresses backward compatibility issues with Release 2.0 for application product versions on Release 2.1 TRANSACT/V Compatible on Release 2.0 and 2.1. TRANSACT/XL Compatible on Release 2.0 and 2.1. INFORM/V Compatible on Release 2.0 and 2.1. REPORT/V Compatible on Release 2.0 and 2.1. DICTIONARY/V Compatible on Release 2.0 adn 2.1. VPLUS This subsystem is in CM in the SL and compiled in NM in the XL. Run HP32309S to see the "VPLUS native mode enabled" message. NM applications will automatically use NM VPLUS; CM applications stay on the CM "side" and use CM VPLUS. NM applications can be forced to use the CM VPLUS with a JCW, VSWITCHTOCM=1. A formfile or program developed on Release 2.1 should run fine on Release 2.0. The DHCF enhancement/product is only on Release 2.1. HI-LI Runs in CM only, because of requirements of HI-LI internal structures. EDITOR Compatible on Release 2.0 and 2.1. HPEDIT/XL Compatible on Release 2.0 and 2.1. TOOLSET/XL Workspaces built under 2.1 should be fine going back to 2.0. Before using Toolset/XL to debug your application compiled or linked on 2.1, the application need to be recompiled and relinked or restored from your Release 2.0 backup tapes. BRW/V See BRW/XL. BRW/XL BRW specifications and execution files are backward compatible. VIRTUOSO No issues. HP SRC The HP SRC Stat file for @.1 is not backward compatible with the stat file for 2.0. You must restore the HP SRC stat file and delta files from your Release 2.0 backup tapes. Data Communication No issues. Office Tools No issues.