HP 3000 Manuals HP 3000 Manuals
Moving Back to Release 2.1, 2.0, 1.25 by Craig Benardo--Commercial Systems Division INTRODUCTION This article documents the supported methods for moving from Release 2.2 back to a prior release (i.e., 1.25, 2.0, 2.1). 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 R3040) 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 prior release (i.e., 1.25, 2.0, 2.1) system (System Load Tape and full system STORE) be performed before updating to Release 2.2. * 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 your prior release. First, you are unable to successfully complete the move from previous release to Release 2.2 and now wish to return to the previous release. Second, after being up on Release 2.2, circumstances warrant a decision to move back to the previous release. Instructions for handling these situations are provided in this article. The instructions for moving back to the previous release are divided into 5 sections. The first section provides instructions for moving back to the previous release after an incomplete move to Release 2.2. 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. ISSUES AND COMPATIBILITY PROBLEMS This section describes issues and compatibility problems you should be aware of when moving back from Release 2.2 to 2.1, 2.0, or 1.25. Languages All compilers and runtime libraries are compatible on Release 2.1 and 2.2. Therefore, there are no languages issues when backdating from 2.2 to 2.1. New versions of most compilers and run-time libraries were submitted to Release 2.2. If the system is backdated to a release prior to 2.1, programs that were compiled on Release 2.2 in any language need to be recompiled and relinked or restored from the back-up tapes from the prior release. As noted in the introduction to this article, before backdating with the FSLT, FOS and SUBSYS tapes, check with your SE for patch information about language products. Native Mode KSAM Files On release 2.2 and 2.1, the customer has the option to implement Native Mode KSAM files (KSAMXL) in which the key and data information are contained in a single file. If the customer has made use of this feature, they must convert the files back to Compatibility Mode BEFORE attempting the backdate. The steps to convert a KSAMXL file back to Compatibility Mode are: :FCOPY FROM=<nmksamfile>;TO=(<cmdatafile>,<cmkeyfile>) where <nmksamfile> = The Native Mode KSAM file <cmdatafile> = The new Compatibility Mode KSAM data file <cmkeyfile> = The new Compatibility Mode KSAM key file Command I/O Redirection (CIOR) CIOR is a new feature of 2.1 that allows a user to direct input and output for a CI command to a file. For example, the output of a SHOWJOB command can be directed to a file called ABC with the command :SHOWJOB >ABC If the customer has made use of this feature in any jobs or command files, then any uses of it will need to be removed. Native Mode Spoolfiles If customers wish to save any spoolfiles currently on the system, they will need to transfer the spoolfiles to tape. This should be done with the new spooler utility SPFXFER (SpoolFile Tape Transfer). This utility will transfer spoolfiles to tape with a format that is compatible with the Compatibility Mode SPOOK on the pre-2.1 system. :FILE SPTAPE;DEV=TAPE :SPFXFER >OUTPUT @.@;*SPTAPE >EXIT
NOTE You must purge all 2.2/2.1 spoolfiles from your system before backdating to a pre-2.1 release; this includes spoolfiles outside of the HPSPOOL account. If the system is backdated to a pre-2.1 release and 2.2/2.1 spoolfiles are present on the system, you will be unable to purge them using SPOOK or the PURGE command. Before backdating, use the follwing command to check for the existence of any NM spoolfiles: :LISTFILE @.@.@,2;SELEQ=[FTYPE=SPOOL] Now use either the PURGE command or the SPOOLF...;DELETE command to get rid of these files. You may ignore any files found in the HPSPOOL account since they will be purged when you purge this account (see a following paragraph regarding purging the HPSPOOL account).
3000devs Account The biggest problem in backdating from 2.2 and 2.1 is the presence of the "3000devs" account. This account was added to 2.1 as a native mode means of obtaining device information. Because of the unique naming convention, it is impossible to purge this account by standard methods. Once on a pre-2.1 system, this account will cause problems for STORE/RESTORE and other subsystems. Patch MPECXZ4 (a program called P3000DEV) is available for this problem. P3000DEV is a native mode program to purge the account 3000devs on releases prior to 2.1. It must be restored into a group that has privilege-mode capability and the user running it must have SM capability. It prints the following messages: This utility purges the account 3000devs on release 2.0 and below. Do you wish to purge the account 3000devs? (Y/N): Purging the account 3000devs. If the group that P3000DEV resides in does not have PM, the program will not load. If the user that runs P3000DEV does not have SM capability the program will print the message: "This utility requires SM capability." HPSPOOL Account The HPSPOOL account must be purged when backdating to a pre-2.1 release. The last thing you do before typing CTL-A SHUTDOWN to shut your system down in preparation for the backdate, type the following: :PURGEACCT HPSPOOL SPOOK You need to restore SPOOK.PUB.SYS from your previous release backup when backdating to a pre-2.1 release. :RESTORE SPOOK.PUB.SYS FCOPY You need to restore FCOPY.PUB.SYS from your previous release backup when backdating to a pre-2.1 release. :RESTORE FCOPY.PUB.SYS AIF If using any AIF utilities or any utilities using AIF intrinsics, they will not load on pre-2.1 releases. Configuration Files The SYSGEN configuration files on 2.2 and 2.1 are not compatible with previous releases. Therefore, when doing the UPDATE from a pre-2.1 SLT, be sure to specify UPDATE CONFIG, which will bring back the old configuration files. The datacomm configuration in NMCONFIG.PUB.SYS will also have changed. To address this issue, restore the old configuration file with the command: :FILE T;DEV=TAPE :RESTORE *T;NMCONFIG.PUB.SYS;DEV=1 After restoring the file, go into NMMGR to validate the configuration and then cross-validate in SYSGEN with the RDCC command. HP Predictive Support XL If you are running HP Predictive Support XL and have used the HP Predictive Support XL product tape included in your FOS package to install version B.00.03, if you need to backdate to the previous version, contact your account CE to have HP Predictive Support XL, version B.00.02, reinstalled. It should be installed as an update. See the installation instructions that acompany the B.00.03 product tape included with your MPE XL 2.2 FOS package. Performance Tools Performance tools submitted to Release 2.2 include GlancePlus/XL, SCOPEXL (host collector component of HP LaserRX), and the new Software Performance Tuner/XL product (SPT/XL). All of these products are release dependent and not backward compatible. Therefore, backdating of the operating system will also require backdating to the proper version of Glance/XL, SCOPEXL, and in the future, SPT/XL. Database Management The database management products available on Release 2.1 and Release 2.2 are the following: -------------------------------------------------------------------------------------------------- | | | | | | | On 2.1? | On 2.2? | Structural | | | | | Changes? | | | | | | -------------------------------------------------------------------------------------------------- | | | | | | TURBO/XL | Yes | Yes | No | | | | | | | TURBO QUERY/XL | Yes | Yes | No | | | | | | | DBCHANGE/XL | Yes | Yes | No | | | | | | | ALLBASE/SQL | Yes | Yes | No | | | | | | | ALLBASE QUERY/XL | Yes | Yes | Yes | | | | | | | ALLBASE 4GL/XL | Yes | Yes | Yes | | | | | | | ALLBASE/NET | Yes | Yes | No | | | | | | -------------------------------------------------------------------------------------------------- Depending on the product, you may or may not have to follow special instructions. So here is a productwide listing: * For TURBO/XL, there are no structural changes between Release 2.1 and 2.2. So TURBO will not cause any compatibility problems. Simply RESTORE from the 2.2 back-ups all TURBO data and application files. * For TURBO QUERY/XL, there are no backdating issues. * DBCHANGE/XL, there are no backdating issues. * For ALLBASE/SQL, there are no structural changes between 2.1 and 2.2. * For the ALLBASE/QUERY product, there are no additional issues. * For ALLBASE 4GL applications unloaded from Release 2.2 are not backward compatible with Release 2.1. 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.2 to Release 2.1 with some modifications using HP4STOA and HP4ATOS. Application Tools The following information addresses backward compatibility issues with previous releases for application product versions on Release 2.2 TRANSACT/V If the customer has used the Language enhancements for Transact introduced in release 2.0, then the programs need to be recompiled when backdating to a previous release of the operating system. TRANSACT/XL Compiled on Release 2.2. Before running on a previous release, TRANSACT/XL applications should be recompiled. INFORM/V No issues. REPORT/V No issues. DICTIONARY/V No issues. 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.2 should run fine on Release 2.1. The DHCF enhancement/product is only on Release 2.0. HI-LI Runs in CM only, because of requirements of HI-LI internal structures. EDITOR No issues. HPEDIT/XL No issues. TOOLSET/XL Toolset/XL relies on information from COBOL, FORTRAN, Pascal, and PXDB in order to debug user programs. PXDB made a major change to the format of the debug information on release 2.0. Therefore, pre-2.0 user programs must be recompiled on later operating systems. Conversely, any programs compiled on 2.0 and later MUST be re-compiled if taken to a pre-2.0 operating system. However, from a support standpoint it is recommended that the programs being debugged by Toolset/XL have been compiled on that system. This prevents confusion if there is a problem with the compilers or PXDB. BRW/V See BRW/XL. BRW/XL BRW specifications and execution files are backward compatible. VIRTUOSO No issues. HP SRC/XL For HP SRC/XL the A.00.xx version is not compatible with the A.01.xx version. When a customer updates to a A.01.xx version of HP SRC, HP SRC automatically converts all of the files used by the product to a new format, therefore, making it impossible to backdate to any of the A.00.xx versions. The A.00.xx version was put on the 1.2 thru the 1.25 MPE/XL releases. HP SRC versions A.01.xx are on the MPE/XL releases 2.0 thru 2.2. With this information, customers can back down from MPE/XL 2.2 to 2.0 (or anything inbetween without affecting HP SRC), but HP SRC customers cannot go from a 2.0 - 2.2 release of MPE/XL to 1.25. Data Communication For an XL host, moving from Release 2.2 back to Release 2.1, 2.0, or 1.25 requires the same procedures. The user should ensure that the old NMCONFIG.PUB.SYS file is properly restored AND validated after backdating to the desired release. For PC-based DTC management in Release 2.2, 2.1, and 2.0, the user can retain the latest OpenView DTC Manager (HP D2355A) software without backdating the software to the old version. The new version software of the OpenView DTC Manager and the DTC download files function well with the old version of XL FOS. Should the user choose to roll back the DTC Manager software, the user will need to restore the OpenView DTC Manager to the corresponding version. The user will also need to restore the DTC configuration directories/files from the backup floppies. The DTC(s) would need to be re-downloaded. Office Tools No issues. II. AN INCOMPLETE MOVE TO RELEASE 2.2 This section provides instructions on how to move back to your previous release after an incomplete move (unsuccessful update) to Release 2.2. The necessary steps to move back to your previous release depend on where the system was during the update process when the problem occurred. Follow the instructions that match your situation. * If the initial Release 2.2 UPDATE from the FSLT fails due to an out of disk space condition: * Purge unneeded files to attempt to free up some disc space and try to update to 2.2 again or, * You can attempt an UPDATE with: 2.1 First, the previous release Customized System Load Tape (CSLT) 2.2 Second, the previous release FSLT 2.3 If neither UPDATE works, then do an INSTALL. Refer to section 3 of this article for UPDATE and INSTALL instructions. * If the initial Release 2.2 UPDATE from the FSLT fails due to I/O failures: * Have the I/O problem corrected and try this UPDATE over again. * If the initial Release 2.2 UPDATE from the FSLT succeeds and the system was started but you never started AUTOINST: * Shutdown the Release 2.2 system and wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. * Reset the system, boot from the alternate boot path and perform an UPDATE using your previous release CSLT. * Rename the file SYSSTART to its original name :RENAME filename, SYSSTART * Set system passwords and reset catalogs. * If you ever started AUTOINST on your Release 2.2 system, you can consider your system up on Release 2.2. III. BACKUP AND SHUTDOWN Obtain a print out of the 2.2 critical summary from NMMGR before attempting to go back to your previous release. The first step in moving back to your previous release is to perform a backup of the Release 2.2 system. * Make sure that all members of the system volume set are mounted. * 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.2, you will have to mount all members of each set. To close them, do either: * Leave them online so that they will be closed during the subsequent shutdown or * 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. ________________________________________________________________ * Close all databases properly. * Follow instructions in Section 2 of the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R3040). * Purge the file NMCONFIG as follows: :PURGE NMCONFIG.PUB.SYS * Shutdown the system by entering: CONTROL = SHUTDOWN Wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. * Continue with section III of this document for an UPDATE or INSTALL. IV. PERFORMING AN UPDATE OR INSTALL Currently, there are five methods supported for moving from Release 2.2 back to your previous release. They are: * An UPDATE using your previous release Factory tapes only (FSLT, FOS and SUBSYS tapes) * An UPDATE CONFIG using your previous release Customized System Load Tape (CSLT) and previous release full system STORE tapes. * An UPDATE using your previous release Factory Tapes (FSLT, FOS and SUBSYS tapes) and your previous release full system STORE tapes. * An INSTALL using your previous release CSLT and previous release full system STORE tapes. * An INSTALL using your previous release Factory tapes (FSLT, FOS and SUBSYS tapes) and your previous release full system STORE tapes. For more information with regards to updating and installing, refer to Section 3 in the "HP 3000 MPE XL Installation and Update Manual" when using Factory tapes and, Section 6 when using Customized SLT. If you have successfully shutdown your Release 2.2 system, you may UPDATE back to your previous release. The type of UPDATE depends on the availability of specific backup tapes. Use AUTOINST to build the previous release accounting structure. Refer to the HP 3000 MPE XL Installation and Update Manual (P/N 36123-90001 R3040) V. RESTORING OTHER SYSTEM COMPONENTS FOR UPDATE ONLY ----------------- * Log on the console as MANAGER.SYS,PUB and make sure everyone stays off the system. * If you renamed the file SYSSTART, reinstate the original name by entering: :RENAME filename,SYSSTART * RESTORE the NMCONFIG file by mounting your previous release full system STORE tapes and entering: :RESTORE ;NMCONFIG.PUB.SYS;DEV=1 * Run NMMGR and validate your network configuration. Use the 2.2 critical summary print out to manually add the devices which have been added to your system since the update to Release 2.2. :NMMGR * 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 FOR BOTH UPDATE AND INSTALL ------------------------------ * Shut the system down CONTROL = SHUTDOWN Wait for the "SHUTDOWN OF OPERATING SYSTEM COMPLETE" message to appear on the console. * Reset the system, boot from disk (i.e., the primary boot path), and enter on the console: ISL>START NORECOVERY This will default to the CONFIG.SYS group.