HP 3000 Manuals HP 3000 Manuals
Moving Back to Release 1.2 (A.21.00) by Maria Molinos Commerical Systems Division INTRODUCTION This article documents the supported methods for moving from Release 2.0 back to Release 1.2. 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 R2830 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.2 system (System Load Tape and full system STORE) be performed before updating to Release 2.0. * 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.0. First, you are unable to successfully complete the move from Release 1.2 to Release 2.0 and now wish to return to Release 1.2. Second, after being up on Release 2.0, circumstances warrant a decision to move back to Release 1.2. Instructions for handling these situations are provided in this article. The instructions for moving back to Release 1.2 are divided into 5 sections. The first section provides instructions for moving back to Release 1.2 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.0 This section provides instructions on how to move back to Release 1.2 after an incomplete move to Release 2.0. The necessary steps to move back to Release 1.2 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.0 UPDATE from the FSLT fails due to an out of disk space condition: 1. You can attempt an UPDATE with: 1.1 First, the 1.2 CSLT 1.2 Second, the 1.2 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.0 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.0 UPDATE from the FSLT succeeds and the system was started but you never started AUTOINST: 1. Shutdown the Release 2.0 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.2 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.0 system, you can consider your system up on Release 2.0. Proceed to section II of this document for instruction on moving back to Release 1.2. II. BACKUP AND SHUTDOWN The first step in moving back to Release 1.2 is to perform a backup of the Release 2.0 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.0, 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 R2830 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.0 back to Release 1.2. They are: a. An UPDATE using Release 1.2 Factory tapes only (FSLT, FOS and SUBSYS tapes) b. An UPDATE using Release 1.2 Customized System Load Tape (CSLT) and Release 1.2 full system STORE tapes. c. An UPDATE using Release 1.2 Factory Tapes (FSLT, FOS and SUBSYS tapes) and Release 1.2 full system STORE tapes. d. An INSTALL using Release 1.2 CSLT and Release 1.2 full system STORE tapes. e. An INSTALL using Release 1.2 Factory tapes (FSLT, FOS and SUBSYS tapes) and Release 1.2 full system STORE tapes. If you have successfully shutdown your Release 2.0 system, you may UPDATE back to Release 1.2. The type of UPDATE depends on the availability of specific backup tapes. Choose the appropriate set of instructions provided below. a) An Update Using Factory Tapes If you want to do an UPDATE back to Release 1.2 from your successfully shutdown Release 2.0 system, but DO NOT have a complete system backup of Release 1.2, you will have to do the following: UPDATE the system with your Release 1.2 FSLT and use AUTOINST to build the Release 1.2 system from the FOS and SUBSYS tapes. Refer to section 3 and 4 of the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2830 or earlier) *** END OF INSTRUCTIONS. DO NOT CONTINUE. *** b) An UPDATE Using CSLT And Full System STORE Tape If you want to do an UPDATE back to Release 1.2 from your successfully shutdown Release 2.0 system using Release 1.2 backup tapes and a CSLT, do the following: 1. Mount the CSLT on the tape drive and boot from the alternate boot path. Enter the following at the console: ISL>UPDATE CONFIG 2. Boot from disk and enter: ISL>START NORECOVERY GROUP = X where X is the desired config group 3. RESTORE the following file sets: :RESTORE @.@.SYS, @.@.TELESUP;OLDDATE;SHOW;CREATE;KEEP *** GO TO SECTION IV *** c) An UPDATE Using Factory Tapes and Full System STORE Tapes If you want to do an UPDATE back to Release 1.2 from your successfully shutdowned Release 2.0 system using backup tapes and a Release 1.2 FSLT, do the following: Update the system with your Release 1.2 FSLT and use AUTOINST to build the Release 1.2 system from the FOS and SUBSYS tapes. Refer to section 3 of the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2830 or earlier). *** GO TO SECTION IV *** d) An INSTALL Using CSLT and Full System STORE Tapes If you cannot completely shutdown your Release 2.0 system, then you must do an INSTALL with the Release 1.2 CSLT using the following steps: 1. Mount Release 1.2 CSLT on the tape drive and boot from the alternate boot path and enter at the console: ISL>INSTALL 2. Boot from disk. ISL>START NORECOVERY GROUP = X where X is the desired config group 3. Format discs (refer to the VOLUTIL manual). 4. RESTORE all files in the system. a. If you are using NM STORE, then :RESTORE; @.@.@; DIRECTORY; OLDDATE; KEEP; SHOW b. If you are using CM STORE, then :RESTORE; @.@.@; CREATE; OLDDATE; KEEP; SHOW 5. Verify UDC and account structure. *** GO TO SECTION IV *** e) An INSTALL Using Factory Tapes and Full System STORE Tapes If you have to do an INSTALL using the Release 1.2 Factory tapes (FSLT, FOS and SUBSYS tapes) do the following: Refer to section 3 of the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2830 or earlier). *** GO TO SECTION IV *** 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 1.2 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.0 critical summary before attempting to go back to Release 1.2. Use this print out to manually add the devices which have been added to your system since the update to Release 2.0. :NMMGR 5. Run SYSGEN to cross validate the network configuration against the system configuration by entering: :SYSGEN At this time, get into the sysfile configurator and execute the SHOW command by entering: sysgen> SY sysfile> SH sysgen> IO 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 Quit SYSGEN by entering the following: sysfile> HOLD sysfile> EXIT sysgen> KEEP sysgen> EXIT FOR INSTALL ONLY 1. Follow the INSTALL instructions beginning in section 4 of the HP3000 MPE XL Installation and Update Manual (P/N 36123-90001 R2830 or earlier) FOR BOTH UPDATE AND INSTALL 1. Shut the system down CONTROL = 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 GROUP=<configname> NORECOVERY Where <configname> is the appropriate configuration group name. 3. RESTORE spool files if you wish at this point by entering: :FILE SPTAPE;DEV=TAPE :SPOOK >INPUT @.@;*SPTAPE >EXIT V. ISSUES AND COMPATIBILITY PROBLEMS This section describes all the issues and compatibility problems you should be aware of when moving back to Release 1.2 from Release 2.0. Languages New versions of most compilers and run-time libraries have been submitted to Release 2.0. This may cause some backward compatibility problems with programs compiled on Release 2.0. If the system is back-dated to 1.2, all programs in any language need to be recompiled and relinked or restored from 1.2 back-up tapes. Database Management The database management products available on Release 1.2 and Release 2.0 are the following: -------------------------------------------------------------------------------------------------- | | | | | | | On 1.2? | On 2.0? | 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 | No | | | | | | | 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 1.2 and 2.0. So TURBO will not cause any compatibility problems. Simply RESTORE from the 2.0 back-ups all TURBO data and application files. b. For TURBO QUERY/XL, there are no structural changes between 1.2 and 2.0. But this product does use NLS features. This implies that the pertinent version of 1.2 must have all the NLS fixes that are available in the 2.0 version. c. DBCHANGE/XL does not have any structural changes. There are no issues when moving back from Release 2.0 and Release 1.2. d. For HP SQL/XL, please note the following: * The DBECon file has defined a new field for 2.0 HP SQL. This does not mean a format change, but it implies that some SQLUTIL scripts written for 2.0 DBEnvironments will not work with 1.2 SQL and vice versa. * 2.0 SQL databases containing saved items will need to be migrated to Release 1.2 (if any action is required to migrate SQL databases). * Further, 2.0 SQL has new functionality like concurrency enhancements, date time, etc. If, after moving to 2.0, the user has started to use these features, a regression to 1.2 will render these new applications unusable. e. For the ALLBASE/QUERY product, there are no additional issues. f. For ALLBASE 4GL applications an unload from Release 2.0 and a reload into Release 1.2 is required. Application Tools The following information addresses backward compatibility issues with Release 1.2 for application product versions on Release 2.0 TRANSACT/V (A.06.04) Compatible on Release 1.2 and 2.0. TRANSACT/XL (A.02.00) Can only run on Release 2.0. INFORM/V (A.06.xx) Compatible on Release 1.2 and 2.0. REPORT/V (A.06.xx) Compatible on Release 1.2 and 2.0. VPLUS (B.05.12) 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.0 should run fine on Release 1.2. The DHCF enhancement/product is only on Release 2.0. HI-LI (A.00.09) Runs in CM only, because of requirements of HI-LI internal structures. EDITOR (A.07.17) Compatible on Release 1.2 and 2.0. HPEDIT/XL (A.00.07) Can only run on Release 2.0. TOOLSET/XL (A.02.02) Workspaces built under 2.0 should be fine going back to 1.2. BRW/V (A.02.10) See BRW/XL. BRW/XL (A.00.20) BRW specifications and execution files are backward compatible. VIRTUOSO (A.01.00) No issues. HP SRC (A.00.00) Can only run on Release 2.0. Data Communication No issues. Office Tools The following information describes the compatibility issues with Release 1.2 for office products versions on Release 2.0 INFORMATION ACCESS (A.04.10) Compatible on Release 1.2. No special conversions for utilities are required. There are no issues for other office products.