HP e3000 MPE/iX System Software Maintenance Manual (Release C.70.00) HP e3000 MPE/iX Computer Systems Edition 6 30216-90317 E0201 Printed in: U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction Manual Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Patch/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Stage/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removal of Support for Servers and HP-IB in MPE/iX . . . . . . . . .
Contents 4.10 Qualifying Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 4.11 Creating a Patch Tape or Staging Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 4.12 Reserving Disk Space for CD-ROM Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 5. Modifying Your System 5.1 Securing and Backing Up the System for Tape Tasks. . . . . . . . . . . . . . . . . . . . . . . .
Contents Menus and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting Result Information (Logs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Adding a CD-ROM Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 F. HP Patch/iX Reference Using HP Patch/iX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 HP Patch/iX Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 Creating a Patch Tape or Stage Tape . . . . . . . . . . . . . . . . . . . .
Tables Table 1.. Cross Reference to Documentation Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Table 2-1.. Select Your Task Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Table 3-1.. System Software Media Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Table 3-2.. OS Version Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Table 3-3..
Tables 8
Figures Figure 5-1.. Sample Listing MAPPER Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-1.. mstm System Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-2.. cstm System Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-3.. mstm Menu Bar and Softkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-4.. mstm Pulldown Menu Example .
Figures 10
Preface This manual describes how to install, update, add-on purchased subsystems, or apply patches to Release 7.0 of the MPE/iX Operating System using either tape or CD-ROM source media. It is an update to the following manual from release 6.5: • HP e3000 MPE/iX System Software Maintenance Manual Release 6.5 This manual is written for experienced MPE/iX system managers.
Chapter 6 , “Finishing the Process,” describes the closing steps required to bring your system back to full operating condition. Appendix A , “Manually Installed Products.” Appendix B , “Configuration Tables.” Appendix C , “Managing Disk Space.” Appendix D , “Backdating Your System.” Appendix E , “CD-ROM Resources.” Appendix F , “HP Patch/iX Reference.” Appendix G , “HP Stage/iX Reference.” Appendix H , “Error Messages and Warnings.” Glossary defines terms used in this manual.
Table 1. Cross Reference to Documentation Products System Software Subject Recommended Manuals Type of Installation Power -Patch Only Add-On, Power -Patch Update , Power -Patch Install, Power -Patch For DTS (Terminal I/O) and DTCs and PC-based networks.
1 Introduction This manual describes how to install or update the operating system, add-on purchased sub-system products, and/or apply patches to your HP e3000 system software using either CD-ROM or tape as source media and tape or stage (disk) media to apply the changes to your system.
Introduction Manual Layout Manual Layout Each chapter is divided into sections, and each section was designed to deliver the information you need quickly and easily. Task checklists provide the sequence of sections that you need to complete for your task. Task Process This manual combines all the system software modification tasks into one process. The basic process is divided into four parts: 1. Chapter 3 , “Planning for Your Task.” 2. Chapter 4 , “Preparing Your System.” 3.
Introduction Manual Layout actions described in the exception step. If the exception does not apply to your task, skip the actions described in the exception and proceed to the next step for your task.
Introduction HP Patch/iX HP Patch/iX HP Patch/iX is a tool for managing your patches. Use it to apply the following to your system: • Reactive patches • PowerPatches • Express Add-on SUBSYS products with PowerPatches The HP Patch/iX tool allows you to: • Qualify all patches in a set of patches, including Reactive patches. This reduces the chance of a patch removing a previously installed patch. • Install Reactive and PowerPatch patches simultaneously. • Selectively apply patches from a PowerPatch.
Introduction HP Stage/iX HP Stage/iX HP Stage/iX is an operating system facility for applying and managing MPE/iX patches on your system. Using HP Stage/iX reduces system downtime and provides an easy and reliable method for backing out patches. Refer to Appendix G , “HP Stage/iX Reference,” for information on HP Stage/iX commands and staging area handling.
Introduction HP Stage/iX a cumulative fashion. This means that if you create a new staging area while a staging area is active, the new staging area will contain all the changes between the Base and the active staging area, plus the new patches applied to the new staging area. HP Stage/iX Task Overview The following is a summary of the HP Stage/iX process. Refer to Appendix G , “HP Stage/iX Reference,” for information on the full HP Stage/iX command set and staging area handling. 1.
Introduction Removal of Support for Servers and HP-IB in MPE/iX Removal of Support for Servers and HP-IB in MPE/iX In order to streamline the development and test of future MPE/iX releases, the PBA-IB HP-IB Device Adapter (A1747A) and old CIB I/O based HP e3000 Servers will not work with MPE/iX Release 6.5 and later releases. The PBA-IB HP-IB Device Adapter was discontinued in May 1999 and has an end of support date of November 1, 2001.
Introduction Discontinuance of High Availability Fiber Link Disk Drives Discontinuance of High Availability Fiber Link Disk Drives In May 1993, Hewlett-Packard Company introduced a family of High Availability Fiber Link disk arrays. Those Fiber Link (HP-FL) disk arrays were discontinued in August of 1997, along with other standalone Fiber link disk drives. The Fiber Link disk arrays were HP’s first RAID devices built for high availability, high performance, high capacity and distances up to 500 meters.
Introduction Summary of Changes to This Manual Summary of Changes to This Manual Changes made since the last version of this manual are as follows: • Revisions were made in response to customer feedback. • Edits were based on Service Requests for documentation changes. • “Jump Tables” were removed. • A capital letter now identifies each checklist for easier reference. • Checklists were simplified to make it easier to track your way through the instructions.
Introduction Summary of Changes to This Manual 24 Chapter 1
2 Task Checklists This chapter describes how to select your task checklist and contains each possible task checklist. Each checklist is a list of the specific sections in this manual that you need to read and follow to complete your task. All tasks require one or more of the checklists in this chapter: • Checklist A. Manage Patches • Checklist B. Manage Patches by Staging Area • Checklist C. Distributing Staging Areas to Remote Systems • Checklist D. Add-on with Tape • Checklist E.
Task Checklists Selecting Checklists Selecting Checklists To perform your task correctly, you must do the following: 1. Select your task checklist(s). Use Table 2-1 to identify which checklist(s) you need. If you see two or three checklist titles at the end of the row for your task, media, and patching situation in Table 2-1 with “and” separating them, perform the activities on the checklists in the order listed.
Task Checklists Selecting Checklists Table 2-1. Select Your Task Checklist Task Option Target System Source Mediaa Modifying Media Patch Option Checklist(s) to Use PowerPatch & Reactive Add-on SUBSYS products Local system Tape Tape None D. Add-on with Tape PowerPatch E. Add-on with Tape and Manage Patches or M. Using AUTOINST to Add-on and Apply PowerPatch Reactive D. Add-on with Tape and A. Manage Patches CD-ROM Tape PowerPatch & Reactive E. Add-on with Tape and Manage Patches None F.
Task Checklists Selecting Checklists Table 2-1. Select Your Task Checklist Task Option Target System Source Mediaa Modifying Media Patch Option Checklist(s) to Use PowerPatch & Reactive Remote system CD-ROM Tape None H. Update with CD-ROM & I. Modify Remote Systems PowerPatch Reactive H. Update with CD-ROM & I. Modify Remote Systems & A. Manage Patches PowerPatch & Reactive Reinstall OS Local system CSLT Tape None J.
Task Checklists Checklist A. Manage Patches Checklist A. Manage Patches Use this task checklist if your source material is on tape and/or electronically downloaded files, you are managing your patches, and you are using a tape to apply: • PowerPatch patches • Reactive patches • PowerPatch and Reactive patches together Print a copy of this checklist for each system that you are applying patches to. Read and perform the steps only in the following sections: Begin Preparation Tasks.
Task Checklists Checklist A. Manage Patches not required; proceed to 5.17, “Rerunning HP Patch/iX.” If the installer utility created a CSLT/STORE tape combined, perform the steps in this section. — 5.14 Restarting the System If the installer utility created a STORE tape only, this section is not required; proceed to 5.17, “Rerunning HP Patch/iX.” If the installer utility created a CSLT/STORE tape combined, perform the steps in this section. — 5.17 Rerunning HP Patch/iX Chapter 6 , “Finishing the Process.
Task Checklists Checklist B. Manage Patches by Staging Area Checklist B. Manage Patches by Staging Area Use this task checklist if your source material is on tape and/or electronically downloaded files, you are managing your patches, and you are using a staging area on disk to apply: • Reactive patches NOTE Not all patches are stageable. For more information, refer to item 19 in section 3.2, “General Planning Tasks.” Print a copy of this checklist for each system that you are applying patches to.
Task Checklists Checklist B. Manage Patches by Staging Area Record temporary filename for the COMMAND.PUB.SYS file: — 5.12 Shutting Down the Remote System — 5.14 Restarting the System Chapter 6 , “Finishing the Process.” — 6.4 Setting Passwords, Lockwords, and UDCs — 6.8 Restarting Selected System Functions — 6.9 Backing Up Your System — 6.10 Permanently Applying a Staging Area-optional. — 6.11 Finishing Up Checklist B tasks completed.
Task Checklists Checklist C. Distributing Staging Areas to Remote Systems Checklist C.
Task Checklists Checklist C. Distributing Staging Areas to Remote Systems Preparation Tasks completed. Schedule downtime for exclusive access. Begin Exclusive Access Tasks. — 5.11 Securing the System Record terminated logging processes: Record temporary filename for the COMMAND.PUB.SYS file: — 5.12 Shutting Down the Remote System — 5.14 Restarting the System Chapter 6 , “Finishing the Process.” — 6.4 Setting Passwords, Lockwords, and UDCs — 6.8 Restarting Selected System Functions — 6.
Task Checklists Checklist D. Add-on with Tape Checklist D. Add-on with Tape Use this task checklist if your source material is on tape and you are using a CSLT tape to: • Add-on purchased products. NOTE • If you are adding-on purchased products and applying PowerPatch patches, or PowerPatch and Reactive patches, instead use Checklist E, “Add-on with Tape and Manage Patches.” • If you are adding-on purchased products and applying Reactive patches: a. Perform the activities in this checklist D. b.
Task Checklists Checklist D. Add-on with Tape Record temporary filename for the COMMAND.PUB.SYS file: — 5.7 Creating the CSLT Using AUTOINST—Select option 5 Add-on (SUBSYS only). Record manually installed products: Record data communication products: — 5.13 Applying the CSLT Modification — 5.14 Restarting the System Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.5 Configuring Manually Installed Products — 6.
Task Checklists Checklist E. Add-on with Tape and Manage Patches Checklist E. Add-on with Tape and Manage Patches Use this task checklist if your source material is on tape and/or electronically downloaded files, you are managing your patches, and you are using a CSLT tape to: • Add-on purchased products and apply PowerPatch patches • Add-on purchased products, apply PowerPatch and Reactive patches together This checklist uses HP Patch/iX.
Task Checklists Checklist E. Add-on with Tape and Manage Patches Record terminated logging processes: Record temporary filename for the COMMAND.PUB.SYS file: — 5.13 Applying the CSLT Modification — 5.14 Restarting the System — 5.17 Rerunning HP Patch/iX Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.5 Configuring Manually Installed Products — 6.7 Performing the Final Reboot — 6.8 Restarting Selected System Functions — 6.
Task Checklists Checklist F. Add-on with CD-ROM Checklist F. Add-on with CD-ROM Use this task checklist if your source material is on CD-ROM and you are using CSLT tape to: • Add-on purchased products • Add-on purchased products and apply PowerPatch patches NOTE You cannot apply Reactive patches at the same time you are using CD-ROM source material to add-on purchased products to your system. You must apply Reactive patches after you update the system.
Task Checklists Checklist F. Add-on with CD-ROM — 5.11 Securing the System Record terminated logging processes: Record temporary filename for the COMMAND.PUB.SYS file: — 5.13 Applying the CSLT Modification — 5.14 Restarting the System — 5.16 Rerunning HPINSTAL Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.5 Configuring Manually Installed Products — 6.7 Performing the Final Reboot — 6.8 Restarting Selected System Functions — 6.
Task Checklists Checklist G. Update with Tape Checklist G. Update with Tape Use this task checklist if your source material is on tape and you are using a CSLT tape to: • Update your system software version level • Update your system software version level and apply PowerPatch patches NOTE You cannot apply Reactive patches at the same time you are updating the system. You must apply Reactive patches after you update the system.
Task Checklists Checklist G. Update with Tape PowerPatch if you have a PowerPatch tape, or if no PowerPatch, select option 4 FOS and SUBSYS. Record manually installed products: Record data communication products: — 5.13 Applying the CSLT Modification — 5.14 Restarting the System — 5.15 Rerunning AUTOINST—Required only if applying PowerPatch. Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.
Task Checklists Checklist H. Update with CD-ROM Checklist H. Update with CD-ROM Use this task checklist if your source material is on CD-ROM and you are using a CSLT tape to: • Update your system software version level • Update your system software version level and apply PowerPatch patches NOTE You cannot apply Reactive patches at the same time you are updating the system. You must apply Reactive patches after you update the system.
Task Checklists Checklist H. Update with CD-ROM Begin Exclusive Access Tasks. Chapter 5 , “Modifying Your System.” — 5.11 Securing the System Record terminated logging processes: Record temporary filename for the COMMAND.PUB.SYS file: — 5.13 Applying the CSLT Modification — 5.14 Restarting the System — 5.16 Rerunning HPINSTAL Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.5 Configuring Manually Installed Products — 6.
Task Checklists Checklist I. Modify Remote System Checklist I. Modify Remote System Use this task checklist if your source material was on CD-ROM and you are now using a CSLT tape to: • Update your remote system software version • Update your remote system software version and applying PowerPatch patches NOTE • Before performing the activities in this checklist, you must have completed the appropriate activities on the checklist H, “Update with CD-ROM.
Task Checklists Checklist I. Modify Remote System Chapter 5 , “Modifying Your System.” — 5.11 Securing the System Record terminated logging processes: Record temporary filename for the COMMAND.PUB.SYS file: — 5.13 Applying the CSLT Modification — 5.14 Restarting the System — 5.16 Rerunning HPINSTAL Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.5 Configuring Manually Installed Products — 6.6 Setting Up the TAR Utility — 6.
Task Checklists Checklist J. Reinstall Using a CSLT Checklist J. Reinstall Using a CSLT If your system has a major system level problem or crash, and you need to reinstall the operating system, use this task checklist. Use your most recent CSLT tape to: • Reinstall your current system software version level CAUTION This reinstall process will DESTROY all existing files on the system.
Task Checklists Checklist J.
Task Checklists Checklist K. Install a New System Checklist K. Install a New System Use this task checklist if your source material is on tape and you are using a CSLT tape to: • Install your system software on new hardware • Install your system software on new hardware and apply PowerPatch patches NOTE • Perform a new installation when new hardware has been shipped to you and the operating system software is not already installed. This is performed only once in the lifetime of a computer.
Task Checklists Checklist K. Install a New System — 5.5 Configuring the System — 5.6 Checking Volumes — 5.7 Creating the CSLT using AUTOINST—Select option 3 FOS, SUBSYS, PowerPatch if you have a PowerPatch tape, or if no PowerPatch, select option 4 FOS and SUBSYS. — 5.13 Applying the CSLT Modification — 5.14 Restarting the System — 5.15 Rerunning AUTOINST—Required only if applying PowerPatch. Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.
Task Checklists Checklist L. Using AUTOINST to Apply PowerPatch Only Checklist L. Using AUTOINST to Apply PowerPatch Only Use this task checklist if your source material is on tape and/or electronically downloaded files, you are managing your patches, and you are using AUTOINST apply: • PowerPatch patches only Patch/iX is the recommended method for installing patches because Patch/iX will qualify patches for you.
Task Checklists Checklist L. Using AUTOINST to Apply PowerPatch Only If AUTOINST created a CSLT/STORE tape combined, perform the steps in this section. — 5.15 Rerunning AUTOINST Chapter 6 , “Finishing the Process.” — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.7 Performing the Final Reboot — 6.8 Restarting Selected System Functions — 6.9 Backing Up Your System — 6.11 Finishing Up Checklist L tasks completed.
Task Checklists Checklist M. Using AUTOINST to Add-on and Apply PowerPatch Checklist M. Using AUTOINST to Add-on and Apply PowerPatch Use this task checklist if your source material is on tape and you are using AUTOINST with a CSLT tape to: • Add-on purchased products and apply PowerPatch patches Patch/iX is the recommended method for installing patches because Patch/iX will qualify patches for you.
Task Checklists Checklist M. Using AUTOINST to Add-on and Apply PowerPatch — 6.1 Configuring Datacomm and UPS — 6.4 Setting Passwords, Lockwords, and UDCs — 6.5 Configuring Manually Installed Products — 6.7 Performing the Final Reboot — 6.8 Restarting Selected System Functions — 6.9 Backing Up Your System — 6.11 Finishing Up Checklist M tasks completed.
3 Planning for Your Task Before you modify your operating system software, you need to plan for the process. Planning includes collecting all the required materials, scheduling the modification, and notifying affected personnel. Perform the activities in this section before you begin to modify the system software. CAUTION You must use a checklist to determine which tasks to perform.
Planning for Your Task 3.1 Verifying Required Materials 3.1 Verifying Required Materials Perform the activities in this section for all the checklists. Be sure to read all of these subsections: • Source Material Components • Tool Options • Media Requirements • Operating System Version Requirements Verify that you have all the required materials.
Planning for Your Task 3.1 Verifying Required Materials Table 3-1.
Planning for Your Task 3.1 Verifying Required Materials Media Requirements When you apply a modification to the system software, you need specific media to prepare for and apply the modification. The media requirements are: • For all tasks creating an SLT, CSLT, or STORE tape, you need one DAT tape. • For all CD-ROM tasks, the master keyword is included on your keyword certificate. Check the keyword certificate to ensure that: — The list of products is what you expected.
Planning for Your Task 3.1 Verifying Required Materials • Verifying Required Materials completed. Go to the next section on your checklist.
Planning for Your Task 3.2 General Planning Tasks 3.2 General Planning Tasks If you are using any checklist, except K, perform the steps in this section. These steps are not required when installing a new system, Checklist K. To plan for any change to your system software: 1. Check and verify compatibility of third-party software. Verify that any third-party software products you are running are compatible with the latest version of the operating system software. Do this before you modify the system. 2.
Planning for Your Task 3.2 General Planning Tasks Do not use the SYSFILE> RSPROG command in the SYSGEN utility to rename HP supplied MPE/iX HP e3000 system files. A renamed system file can corrupt your system during an update. This problem can occur if you have third-party software installed on your system, and you have renamed some system files to run that software. 11.Record and store customized HP configuration information.
Planning for Your Task 3.2 General Planning Tasks Communicator e3000. 17.Document your current system configuration. Keep a listing of output from: • DSTAT ALL command for volume set and volume names. • DISCFREE C for a percentage of permanent and transient space used on your system. • SYSINFO for your system configuration. If you have mirrored disks and users are logged on, do not run SYSINFO.
Planning for Your Task 3.3 CD-ROM Planning Tasks 3.3 CD-ROM Planning Tasks To plan for CD-ROM related tasks: 1. Review Appendix E , “CD-ROM Resources.” If you are using the CD-ROM media option and you are new to the process, refer to Appendix E , “CD-ROM Resources,” for reference information that will help simplify your task. 2. Plan to log onto a console for Phase 2. For some phases of the modification process, you can run HPINSTAL from any terminal.
Planning for Your Task 3.4 Checking Tape Media 3.4 Checking Tape Media Collect the tape media you will be using as source material to modify the system software. The tapes vary depending on your task, but may include PowerPatch, Reactive Patch, FOS, factory SLT, and CSLT tapes. Check your tapes to ensure they are not damaged. If any files are not verified, or if you receive any errors or warnings, clean your tape drive. (Run the cleaning cartridge through your DDS drive at least three times.
Planning for Your Task 3.4 Checking Tape Media Add-on (SUBSYS) Tape 6. Mount the SUBSYS tape for your ordered products. a. Restore the T-file. This file contains the listing of files of the purchased products. :RESTORE *TAPE;T#####.PROD.SOFTREP;CREATE;SHOW RESTORE returns a T-file, note the T-file filename. If the T-file is not on the tape: :RESTORE *TAPE;PRODLIST.MITBLD.SUPPORT b. View the T-file using a text editor or word processor. c. Print the list of products on the SUBSYS tape.
Planning for Your Task 3.4 Checking Tape Media 6 - Check the tape and display the contents of one file in hex. 7 - Check the tape and display summary of tape and disk use statistics. 8 - Information. 9 - Exit program. Which level? __ c. Select level 1. d. Reply to tape request, as required. checkslt displays a listing of verified files. • Checking Tape Media completed. Go to the next section on your checklist.
Planning for Your Task 3.5 Checking Peripherals 3.5 Checking Peripherals Proceed to the subsection for your device: • CD-ROM Disk Drive • SCSI Tape Devices Then review the following subsections: • LDEV1 Disk Minimum Capacity • LDEV1 Disk Maximum Capacity CD-ROM Disk Drive To update or add-on to your system software using a CD-ROM, you must have a CD-ROM drive installed and configured. Refer to Appendix E , “CD-ROM Resources.
Planning for Your Task 3.5 Checking Peripherals • Checking Peripherals completed. Go to the next section on your checklist.
Planning for Your Task 3.6 Estimating Disk Space 3.6 Estimating Disk Space Read the subsections in this section: • Non-Contiguous Disk Space Requirements • Contiguous Disk Space Requirements • Disk Space Error Messages Before you begin to modify your system software make sure that you have enough disk space to update your system. Modifying system software includes: updating the version, reinstalling your system software, adding on purchased products from the SUBSYS tape, or applying patches.
Planning for Your Task 3.6 Estimating Disk Space room on LDEV 1 for all the SLT files. The FOS files do not have to go onto LDEV 1. Table 3-5. Non-Contiguous Disk Space Sectors System Software Components Version C60.00 C.65.00 C70.00 Peak Net Peak Net Peak Net SLT onlya n/a 1,274.000 n/a 1,287,000 n/a 1,273,000 SLT and FOS 2,821,000 2,533,000 2,987,000 2,660,000 3,197,000 2,846,000 SLT, FOS, Full SUBSYS 3,926,000 3,489,000 4,111,000 3,689,000 4,054,000 3,604,000 a.
Planning for Your Task 3.6 Estimating Disk Space Record the estimated disk space required for SUBSYS products on your checklist. Disk Space Estimate for PowerPatch or Express The disk space required is listed in the section, “Disk Space Requirements,” in the Read Before Installing that comes with the PowerPatch or Express media. Record the disk space required for the PowerPatch or Express on your checklist.
Planning for Your Task 3.6 Estimating Disk Space (20 × 1,000,000) ---------------------- = 78,125 sectors 256 • Example of sectors to MBytes: If a disk has a device size of 7,824,336: 7,824,336 × 256 --------------------- = 2,003 megabytes 1,000,000 Therefore the disk is a 2,000 Mbyte disk, (also known as 2 GByte disk). For a closer estimate, use the value 1,048,576 instead of 1,000,000. For a quick estimate, use the value 4,000 instead of 1,000,000/256.
Planning for Your Task 3.6 Estimating Disk Space -------------------------------L E V E L - N U M B E R S -------------------------------1 - Check the tape. Display errors and file names. 2 - Check the tape. Display errors, file names and size. 3 - Check the tape and display all information for each section. 4 - Recover a TAPE BOOT file. NOT AVAILABLE 5 - Recover a DISK file from the tape and copy it to a disk file. 6 - Check the tape and display the contents of one file in hex.
Planning for Your Task 3.
4 Preparing Your System This chapter describes preparing the modification tools and the data that is going to be applied to your system. There are three methods for applying the modification to your system: • Create a Customized System Load Tape (CSLT). • Create a STORE tape. • Create a staging area. You must use a checklist to determine which tasks to perform. If you started without a checklist, return to Chapter 2 , “Task Checklists,” and select the checklist that is appropriate for your task.
Preparing Your System 4.1 Reserving Disk Space for Tape Tasks 4.1 Reserving Disk Space for Tape Tasks The update and add-on process requires a minimum number of contiguous and non-contiguous disk space sectors. Ensure that you have enough contiguous disk space on LDEV 1 to complete your task. The total amount of non-contiguous disk space does not need to fit entirely on LDEV 1. Refer to Chapter 3 , “Planning for Your Task.” To reserve disk space: 1. Log onto the console: :HELLO MANAGER.
Preparing Your System 4.2 Reserving Disk Space for Distributing Staging Areas 4.2 Reserving Disk Space for Distributing Staging Areas A staging area requires a minimum amount of non-contiguous disk space sectors. Ensure that you have enough non-contiguous disk space on LDEV 1 to complete your task. To verify the remote system has enough disk space: 1. Log onto the console on the remote system with the following conditions: :HELLO MANAGER.
Preparing Your System 4.3 Preparing to Run HPINSTAL 4.3 Preparing to Run HPINSTAL This section lists procedures for preparing to use the CD-ROM update and add-on tool, HPINSTAL. Refer to Appendix E , “CD-ROM Resources,” for additional CD-ROM set up information. To prepare your local system to create a CSLT using HPINSTAL: 1. Log on. :HELLO MANAGER.SYS,INSTALL;HIPRI If you are not working at the console, allow yourself the VSCLOSE and VSOPEN commands. :ALLOW MANAGER.SYS;COMMANDS=VSCLOSE,VSOPEN 2.
Preparing Your System 4.3 Preparing to Run HPINSTAL MPE_v.uu.ff_1. :LISTGROUP INSTUTIL 8. If the INSTUTIL group is non-existent, create the INSTUTIL group and set home volume set. :NEWGROUP INSTUTIL;HOMEVS=MPE_v.uu.ff_1 9. If the home volume set field displays a different v.uu.ff than the new version: :ALTGROUP INSTUTIL.SYS;HOMEVS=MPE_v.uu.ff_1 10.If you are performing an Update task, proceed to Step 11. If you are performing an Add-On task, proceed to Step 12. Update Tasks 11.This step is optional.
Preparing Your System 4.3 Preparing to Run HPINSTAL :SETUP.INSTUTIL Execute SETINIT command to cleanup any previous HPINSTAL accounting structure, if prompted. :SETINIT A series of messages display. The process takes about five minutes. The final message is: setup is complete 15.If you are performing a PowerPatch task, proceed to Step 16. If you are performing an Add-on or Update task without a PowerPatch, proceed to the next section on your checklist. PowerPatch Tasks 16.
Preparing Your System 4.4 Initializing HP Stage/iX 4.4 Initializing HP Stage/iX HP Stage/iX is part of the FOS. It is installed when the system software is updated to version 5.5 or 6.0. You must be on version 5.5 or greater before you can use HP Stage/iX. You cannot use HP Stage/iX to update from version 5.5 to 6.0. NOTE Not all patches are stageable. At the time of release 6.5, Stage/iX cannot handle patches which involve System configuration files, MMSAVE.MPEXL.
Preparing Your System 4.5 Backing Up Your System for Reinstall 4.5 Backing Up Your System for Reinstall If you are using checklist J, and if you are performing a reinstall because your system is not operating, it is in a “crash” state, and you do not want a backup in this state, then proceed to “Applying the Modification.” If you are using checklist J, and if you are planning to reinstall your system software, proceed with this section.
Preparing Your System 4.5 Backing Up Your System for Reinstall • Backing Up Your System for Reinstall completed. Proceed to the next section on your checklist.
Preparing Your System 4.6 Creating the CSLT using HPINSTAL 4.6 Creating the CSLT using HPINSTAL This section describes how to create your Customized System Load Tape (CSLT) from CD-ROM source media using the CD-ROM tool, hpinstal. To create the CSLT using hpinstal 1. Start HPINSTAL. :RUN HPINSTAL.INSTALL.SYS 2. Select the appropriate option. If you select a subsys option, your system software must be on the same release level as the subsys product.
Preparing Your System 4.6 Creating the CSLT using HPINSTAL “CD-ROM Resources,” for directions on creating a Base Group.) When ready to create the CSLT, HPINSTAL will copy your current configuration group to HPCONFIG.SYS and use that as the base group. If you have customized a configuration group that you would like HPINSTAL to use as the base group while creating the CSLT, please provide it now. Base group (RETURN for default) >> c. Proceed to Step 6. 6. If needed, edit or create a PRODLIST.PUB.SYS file.
Preparing Your System 4.6 Creating the CSLT using HPINSTAL Your keyword >> NOTE Add-on product keyword can only be entered interactively. 9. Select to install all or a portion of the listed products: Enter Y to select all products on the list. Enter N to select a subset of the products, proceed to Step 10. Do you want to install all of the above products? (Y/N)>> If you accidentally type N, are viewing the list of products, and you do not wish to make any changes to the list: a.
Preparing Your System 4.6 Creating the CSLT using HPINSTAL c. Respond Y to accept the list of qualified patches, as prompted: Do you wish to continue with the installation of the patches listed above(Y)?>> d. Remount the PowerPatch tape, as prompted; Mount the POWERPATCH tape and put the tape drive online. The files from the POWERPATCH tape will now be restored. e. Reply to the tape request. f. Proceed to Step 13. 13.Create the CSLT.
Preparing Your System 4.6 Creating the CSLT using HPINSTAL Thank You Verifying the second CD-ROM . . . Done. The second CD-ROM volume has been mounted. Continuing with installing from the CD-ROM volume MPE_v.uu.ff_2. 14.After the CSLT is created, dismount the tape, label it CSLT v.uu.ff, and set it to read only. The final response messages vary depending upon the CSLT option you selected. Basically, the response is: Phase I of HPINSTAL is now complete: 15.A warning message displays, if applicable.
Preparing Your System 4.7 Starting the Patch Management Tools 4.7 Starting the Patch Management Tools Overview HP Patch/iX is the recommended method for applying patches and is required for applying Reactive patches. It is delivered with each PowerPatch tape set and each Reactive patch. Hewlett-Packard recommends that you always restore HP Patch/iX from the patch tape. This ensures that you are using the most recent version of HP Patch/iX. HP Patch/iX is a screen-based, menu-driven patch management tool.
Preparing Your System 4.7 Starting the Patch Management Tools following command works for window terminal emulators, but is not required for standard HP terminals. :SETVAR LINES # where # is the number of lines per screen. There is no option for adjusting screen width. 3. Type at the MPE/iX prompt. :PATCHIX The Logon screen displays. 4. Type your HP Patch/iX logon name at the prompt.
Preparing Your System 4.7 Starting the Patch Management Tools • Starting the Patch Management Tools completed. Go to the next section on your checklist.
Preparing Your System 4.8 Selecting HP Patch/iX Activities 4.8 Selecting HP Patch/iX Activities Review all subsections in this section: • Overview • Selecting Type of Patching Task • Preparing Your System with HP Patch/iX Overview On the HP Patch/iX Main menu, Select Activities is the first option. This is a required action for patch installation. This option provides two functions: • Allows you to select the type of patching activity you are planning to perform.
Preparing Your System 4.8 Selecting HP Patch/iX Activities 3. Press [F4] Process List, when you have marked all the activities you plan to perform. HP Patch/iX proceeds to prepare the system for creating the CSLT or store tape, or staging area. Preparing Your System With HP Patch/iX Preparing the system for creating the CSLT is tailored to the specific type of patch processes selected.
Preparing Your System 4.8 Selecting HP Patch/iX Activities Insert tapes and reply to the tape requests as required. HP Patch/iX restores files and displays the status as the preparation phase progresses. When all setup activities are completed, HP Patch/iX automatically returns you to the Main menu. The status area indicates the type of patch activity that you selected. If you selected Adding (SUBSYS) Products, the Main menu displays Create [Tape]; you will not be able to select Create [Stage] [Tape]. 3.
Preparing Your System 4.8 Selecting HP Patch/iX Activities CAUTION When you select customized patch preparation, and alter from the defaults, you are overriding the Hewlett-Packard recommended operations unless you are applying patches downloaded from the HP SupportLine web site. To customize the patch preparation process: 1. After you mark your patch activities on the Select Activities screen and press [F4] Process, you will get a prompt to accept defaults.
Preparing Your System 4.9 Viewing Patches 4.9 Viewing Patches Overview On the HP Patch/iX Main menu, View Patches is the second option. It is an optional step for patch installation. The list of patches displayed in the View Patches screen varies depending upon the filter selected. The default View Patches filter displays installed patches. The current View Patches filter setting is displayed at the top right corner of the View Patches window.
Preparing Your System 4.9 Viewing Patches NOTE Patch/iX will NOT have a record for any patches installed by AUTOPAT. • Viewing Patches tasks completed. Go to the next section on your checklist.
Preparing Your System 4.10 Qualifying Patches 4.10 Qualifying Patches Overview Qualify Patches is the third option on the HP Patch/iX Main menu. It is a required step for patch installation when using HP Patch/iX. This option provides three functions: • Automatically reviews the available patches and determines which patches are compatible with your system. • Allows you to force or veto individual patches. Forcing a patch tells HP Patch/iX to include (add) the selected patch in the patch installation.
Preparing Your System 4.10 Qualifying Patches • Return to the Main menu. Qualifying Patches Steps To qualify patches: 1. From the HP Patch/iX Main menu, highlight Qualify Patches and press [Return]. The Qualify Patches prompt displays. 2. Respond Yes to the prompt: Are you ready to begin this full qualification? (y/n) _ An information window lists the types of patches, number of patches, and an estimate of time to perform the qualification.
Preparing Your System 4.10 Qualifying Patches Modifying the List of Qualified Patches HP Patch/iX allows you to change the list of qualified patches that will be applied to your system through the patch process. CAUTION Forcing a patch that does not automatically qualify for your system is strongly discouraged by Hewlett-Packard, EXCEPT if it is an enhancement or under the recommendation of the HP Response Center. To modify the list of qualified patches: 1.
Preparing Your System 4.10 Qualifying Patches When you press [F8] you automatically return to the Main menu. The status lists the number of patches that have qualified. All patches with a Yes in the Qualified column will be applied to your system; this includes Forced patches. Those patches with a No in the Qualified column will not be applied to your system. • Qualifying Patches Tasks completed. Go to the next section on your checklist.
Preparing Your System 4.11 Creating a Patch Tape or Staging Area 4.11 Creating a Patch Tape or Staging Area Overview On the HP Patch/iX Main menu, the Create [Stage] [Tape] option displays if HP Stage/iX is initialized. If HP Stage/iX is not initialized or, if one or more qualified patches is not stageable, the Create [Tape] option displays.
Preparing Your System 4.11 Creating a Patch Tape or Staging Area B Create both a staging area and a CSLT/STORE tape. Hewlett-Packard recommends that you select T to create a CSLT/STORE tape for backup purposes. HP Patch/iX allows you to create a patch installation (S)taging area, (T)ape, or (B)oth. What is your selection? (S, T, B) 3. If you are creating a staging area, respond to the prompt for a staging area name. The staging area name can be up to 16 characters.
Preparing Your System 4.11 Creating a Patch Tape or Staging Area 7. HP Patch/iX automatically returns you to the Main menu. The status indicates “Stage Created,” “CSLT/STORE Tape Created,” or “Stage and Tape Created,” as appropriate for your selection. NOTE Exiting HP Patch/iX is a required action for patch installation. To exit HP Patch/iX: 1. From the HP Patch/iX Main menu, highlight the fifth option, Exit HP Patch/iX and press [Return]. Do not just press [F8].
Preparing Your System 4.12 Reserving Disk Space for CD-ROM Tasks 4.12 Reserving Disk Space for CD-ROM Tasks Ensure that you have enough contiguous disk space on LDEV 1 to complete your task. The total amount of non-contiguous disk space does not need to fit entirely on LDEV 1. To reserve disk space: 1. Estimate contiguous disk space required to update your system. Mount the CSLT created by HPINSTAL. :CHECKSLT.MPEXL.TELESUP **************************CHECKSLT 1.
Preparing Your System 4.
5 Modifying Your System This chapter describes tasks that require exclusive access to your system. Use only the sections on your checklist for the process of securing, shutting down, and applying the changes to your system. CAUTION You must use a checklist to determine which tasks to perform. If you started without a checklist, return to Chapter 2 , “Task Checklists,” and select the checklist that is appropriate for your task. Perform only the steps in the sections that appear on your checklist.
Modifying Your System 5.1 Securing and Backing Up the System for Tape Tasks 5.1 Securing and Backing Up the System for Tape Tasks To prepare and secure the system for updating: 1. From the console, log on with the following conditions, or if already logged on, change group to PUB. :HELLO MANAGER.SYS,PUB;HIPRI or :CHGROUP PUB 2. If you are performing an Update, go to Step 3. If you are performing an Add-on, go to Step 4. Update Tasks 3. Run HP Predictive Support and turn it off.
Modifying Your System 5.1 Securing and Backing Up the System for Tape Tasks 5. Warn, then log users off. :WARN@ PLEASE LOG OFF! SYSTEM UPDATE ABOUT TO BEGIN Wait approximately five minutes. Make sure users have saved their work and logged off, then abort jobs or sessions still executing. Use the SHOWJOB command to determine session and job numbers. For each job and session still executing (except yours) type: :ABORTJOB #Jnn :ABORTJOB #Snnn where: Jnn — the ID number for each job to be aborted.
Modifying Your System 5.1 Securing and Backing Up the System for Tape Tasks DBEnvironment. • Log files are not stored using this command. In addition, you should use the SHOWDBE command to ensure that all parameters are OK. b. If you have ALLBASE/4GL already on your system, unload all existing ALLBASE/4GL applications. For information on unloading ALLBASE/4GL applications, refer to the HP ALLBASE/4GL Developer Administration Manual. c.
Modifying Your System 5.1 Securing and Backing Up the System for Tape Tasks :PURGE HPINSTFL.INSTALL.SYS 12.Purge spool files. :SPOOLF @;DELETE 13.Purge staging groups. :PURGEGROUP UNL :PURGEGROUP USL :PURGEGROUP UXL Verify each purge, type Y, at the prompt. Do not purge the group install.sys or the file supacct.pub.sys; they are needed for future patch and add-on processes. 14.If you are performing an Update task, go to Step 15. If you are performing an Add-on task, go to Step 16. Update Tasks 15.
Modifying Your System 5.2 Applying the SLT 5.2 Applying the SLT In this section, you apply changes to the operating system kernel and start the system. The steps in this section do modify your system software. However, this section does not complete the modification task. To apply the factory SLT to the system: 1. From the console, mount the factory supplied System Load Tape (SLT) and put the tape drive online. Wait until a message displays on the system console verifying that the tape mounted. 2.
Modifying Your System 5.2 Applying the SLT Enter Y to confirm restarting the system. 5. Boot the system from the alternate boot path. a. Boot messages vary depending on the system model. • If you have AUTOBOOT enabled, follow the instructions on the screen and strike any key within 10 seconds. If you do not override AUTOBOOT, the system boots from the primary boot path. If your system does boot from the primary boot path, return to Step 3 and reset the system with the CTRL-B and RS commands.
Modifying Your System 5.2 Applying the SLT Set clock to Greenwich Mean Time. This takes about six minutes. CAUTION DO NOT DO THIS UNLESS YOU ARE PERFORMING A NEW INSTALL TASK. IT DESTROYS ALL THE EXISTING SYSTEM AND USER FILES IN THE MPEXL_SYSTEM_VOLUME_SET! b. Type at the prompt: ISL>INSTALL c. Go to Step 10. 10.Confirm the date and time. If the date and time displayed are not correct, enter N, and enter the correct date and time. If you do not respond within 15 seconds, the system continues.
Modifying Your System 5.3 Listing the System Configuration 5.3 Listing the System Configuration This section describes how to determine your system configuration group. The factory System Load Tape (SLT) does not contain a default I/O configuration. During an installation, you must specify the appropriate factory configuration group when booting the system immediately after installing the factory SLT. Listing the system configuration uses the off-line diagnostic tool, Mapper.
Modifying Your System 5.3 Listing the System Configuration Floating Point Co-processor is installed I/O Configuration: Path Component Name Type ID HW Mod SW Mod Revisions Hdwr Firm --------- ---------------------------------- ----- ----- ----- ----- ----8 I/O Adapter CH 580H BH 15 1 8/63 GSC+ Port 7H 501H CH 1 3 10 I/O Adapter CH 580H BH 15 1 10/4 Upper Bus Converter 7H 500H CH 0 0 10/4/0 HP-PB LAN/Console 2H 5H 60H 0 1 10/4/4 HP-PB Fast Wide SCSI 4H 4H 3BH 0 0 10/4/4.2.
Modifying Your System 5.4 Starting the System bank 13: 64MB RUN COMPLETED. • Listing the System Configuration completed. Go to the next section on your checklist. 5.4 Starting the System When the update is complete, autoboot begins. Perform the following steps to ensure the system is up and running. To start the system: 1. Start the system. ISL>START NORECOVERY NOSYSSTART If you are Installing a New System, add group=configname to the command string.
Modifying Your System 5.5 Configuring the System 3. Dismount the System Load Tape (SLT). • Starting the System completed. Go to the next section on your checklist. 5.5 Configuring the System You need to configure the following devices for AUTOINST to work properly: • LP device class • streams device (usually 10) • tape drive (that matches the FOS and SUBSYS media type) If you need information about hardware device IDs, print the file IODFAULT.PUB.SYS on your screen.
Modifying Your System 5.5 Configuring the System CTRL-B CM>SP SP>RS Enter Y to HARD BOOT the computer system. Do not respond to the question: Press any key within 10 seconds to cancel boot with this configuration. There are 5 to 10 minutes of system activity, then the Processor Dependent Code (PDC) screen displays. b.
Modifying Your System 5.6 Checking Volumes 5.6 Checking Volumes If necessary, use the VOLUTIL utility to add system volumes, that is, the system domain (MPEXL_SYSTEM_VOLUME_SET) disk drives (except LDEV1). For more information on VOLUTIL commands, refer to the Volume Management Reference Manual. To check volumes: 1. From the console, log on with the following conditions (if you are not already logged on). :HELLO MANAGER.
Modifying Your System 5.7 Creating the CSLT Using AUTOINST 5.7 Creating the CSLT Using AUTOINST AUTOINST sets up the necessary environment, restores files, and creates the accounting structure for the installation. To create the CSLT using AUTOINST: 1. From the console, log on and reset system utilities. :HELLO MANAGER.SYS,INSTALL;HIPRI :SPOOLER LP;OPENQ :STREAMS streams_device A common streams_device value is 10. An LP device must be configured in SYSGEN.
Modifying Your System 5.7 Creating the CSLT Using AUTOINST Disk Space,” for actions. b. When you find the required disk space, run AUTOINST again. 7. Select the option that matches your task. :run autoinst MPE/iX AUTOINST E.11.02 (C) HEWLETT-PACKARD CO. Please choose and enter the number corresponding to the software you want to install. 1 2 3 4 5 6 PowerPatch SUBSYS (Add-On) and PowerPatch FOS, SUBSYS, PowerPatch FOS and SUBSYS Add-On (SUBSYS only) Exit Enter your choice_ 8.
Modifying Your System 5.7 Creating the CSLT Using AUTOINST Was a SUBSYS tape included in your installation package (y/n)? If you do not have a SUBSYS tape, enter N and go to Step 14. If you have a SUBSYS tape, enter Y. AUTOINST creates the accounting structure. Progress messages display throughout this 5 minute process Add-on and Update Tasks 12.Restore SUBSYS files. This step takes about 20–45 minutes. a.
Modifying Your System 5.7 Creating the CSLT Using AUTOINST Typing Y accepts the qualified patches. AUTOINST includes them in the CSLT, and continues with creating the CSLT. Typing N rejects the qualified patches, AUTOINST does not include the patches in the CSLT, but does continue with creating the CSLT. Do you wish to continue with installation of the patches listed above (y/n)? The final patch processing takes about 20–45 minutes.
Modifying Your System 5.8 Preparing a Staging Area for Remote Distribution v.uu.ff and include the current date. You can find the SUBSYS v.uu.ff on the FOS, SLT, and/or SUBSYS tape labels. You can find the PowerPatch v.uu.ff on the PowerPatch tape labels. • Creating the CSLT Using AUTOINST completed. Go to the next section on your checklist. 5.8 Preparing a Staging Area for Remote Distribution Perform the steps in this section only if you are planning to Distribute a Staging Area to a Remote system.
Modifying Your System 5.9 Installing a Distributed Staging Area PACK creates a single packaged file in the directory /SYS/hpstage/export with the staging area name as the filename. NOPACK places all files related to the staging area in the /SYS/hpstage/export directory. • Preparing a Staging Area for Remote Distribution completed. Go to the next section on your checklist. 5.
Modifying Your System 5.10 Setting a Staging Area option-matches the option used to export the staging area. The default for EXPORT is NOPACK. The IMPORT options are: TAPE—For the tape option, reply to the tape request. UNPACK—For the pack option, specify the staging area name. NOUNPACK—The distributed staging area is created on the remote system. 5. Validate the new staging area. STAGEMAN>VALIDATE sa_name • Installing a Distributed Staging Area completed. Go to the next section on your checklist. 5.
Modifying Your System 5.11 Securing the System • Setting a Staging Area completed. Go to the next section on your checklist. 5.11 Securing the System This section includes logging off users and shutting down the system. To prepare and secure the system for updating: 1. If you are performing a Distributing Staging Area, or Modify Remote System task, log on from the remote system console. If you are performing a Manage Patch, Add-on, Update, or Re-Install task, log on from the local system console.
Modifying Your System 5.11 Securing the System Hewlett-Packard Response Center. If a transfer is needed, be sure it completes because the system update overwrites the information in the file PSDCFILE.PRED.SYS. b. Select item 4, Configuration, from the Main menu. c. Select item 5, Schedule, from the Configuration Options menu. d. Select item 1, Schedule (on/off), from the Schedule menu. e. Set the preference, at the prompt, type OFF: Type schedule preference (on/off) or // to cancel: __ f.
Modifying Your System 5.11 Securing the System If no logging processes are running, go to Step 10. c. Terminate logging processes as shown below. :LOG logid,STOP where logid — the ID number for each logging process to be stopped. Record the names of the logging processes, if you want to restart them later. Record the names on your checklist. 10.Prepare additional manually installed products. a.
Modifying Your System 5.11 Securing the System c. If you are prompted for lockwords on system files, record the names of each system file as prompted, then type the lockword and continue with the backup. You will need to restore these lockwords later in “Setting Passwords and Lockwords.” Record the names on your checklist. d. Dismount the tape, label as SLT with date, time and system version. e. Mount another blank tape and backup your user files. :FILE T;DEV=TAPE :STORE @.@.SYS,@.@.@-@.@.
Modifying Your System 5.11 Securing the System the numeric release number (for example, OSA10.TELESUP and 0SB23.TELESUP). nn Go to Step 17. 17.Rename the COMMAND.PUB.SYS file, except checklists L and M which included this step in section 5.7 :RENAME COMMAND.PUB.SYS,command_name where command_name is a temporary name you are assigning the file. This preserves your UDC information for later use. Record the temporary name on your checklist. 18.
Modifying Your System 5.12 Shutting Down the Remote System 5.12 Shutting Down the Remote System To shut down the remote system: 1. Log onto the remote system console. :HELLO MANAGER.SYS,INSTALL;HIPRI :SPOOLER LP;START :STREAMS streams_device A common streams_device value is 10. An LP device must be configured in SYSGEN. Already spooled and streamed messages might display. 2. Shutdown the system. CTRL-A =SHUTDOWN 3. Reset the system after the last shutdown message (SHUT6). a.
Modifying Your System 5.13 Applying the CSLT Modification 5.13 Applying the CSLT Modification This section is for applying the Customized System Load Tape (CSLT) created by AUTOINST, HPINSTAL, or HP Patch/iX. For Manage Patch tasks, this is the CSLT/STORE tape (not a STORE only tape). For re-installations, it is the CSLT created most recently in SYSGEN. To apply the CSLT tape: 1. From the console, mount reel one of the CSLT tape on the tape drive, and put the tape drive online.
Modifying Your System 5.13 Applying the CSLT Modification e. Enter Y to confirm restarting the system. 5. Boot the system from the alternate boot path where the CSLT is mounted. a. Boot messages can vary, depending on the system model. • If you do not override AUTOBOOT, the system boots from the primary boot path. If your system does boot from the primary boot path, return to Step 3 and reset the system with the CTRL-B and RS commands.
Modifying Your System 5.13 Applying the CSLT Modification ISL>AUTOBOOT OFF b. Type at the ISL prompt: ISL>UPDATE The system displays initialization and restore messages. c. Go to Step 11. Reinstall Tasks 10.Proceed with the re-installation. CAUTION DO NOT DO THIS UNLESS YOU ARE PERFORMING A REINSTALL. IT DESTROYS ALL THE EXISTING SYSTEM AND USER FILES IN THE MPEXL_SYSTEM_VOLUME_SET! a. Type at the ISL prompt: ISL>install The system displays initialization and restore messages. b. Go to Step 11. 11.
Modifying Your System 5.14 Restarting the System 5.14 Restarting the System If you just completed an update or install task, the system has reset itself. Otherwise, reboot the system. To restart the system: 1. Boot the system from the primary boot path. a. Boot messages can vary, depending on the system model. • If you have AUTOBOOT enabled, the system boots from the primary boot path automatically unless you override AUTOBOOT. • If your system prompts to enter the boot path, enter the primary boot path.
Modifying Your System 5.14 Restarting the System A common streams_device value is 10. An LP device must be configured in SYSGEN. 7. If you are performing a reinstall task, go to Step 8. If you are performing a staging area task, go to Step 9. If you are performing an Install, Update, Add-on, Manage Patch, Remote with CD-ROM, or Staging Area task for a local system only using the TAPE option, go to the next section on your checklist. Reinstall Tasks 8.
Modifying Your System 5.14 Restarting the System section, “Distributing a Staging Area Preparation,” in this chapter for information on the use of PACK and UNPACK.) CAUTION Perform this on your local system only after you have imported the distributed staging area to your remote systems. To clean up the staging area files on your local system. a. Logon to the local system. :HELLO MANAGER.SYS,INSTALL;HIPRI b. Purge the files in the EXPORT directory. :PURGE /SYS/HPSTAGE/EXPORT/@ c.
Modifying Your System 5.15 Rerunning AUTOINST 5.15 Rerunning AUTOINST To rerun AUTOINST and finish applying the CSLT: 1. Remount the combined CSLT/store tape created during the first run of AUTOINST. If the CSLT is two reels, begin by loading the second reel because the STORE files are appended to the CSLT. The program will prompt you if the first reel is also required. 2. Reset the outfence. :OUTFENCE 14 3. Run AUTOINST to resume previous installation. :RUN AUTOINST.INSTALL.SYS 4.
Modifying Your System 5.15 Rerunning AUTOINST Begin processing installation files. Processing n installation files. . . . * the number of dots equals n * The message may indicate zero installation files. This only means that the products you are installing do not require an installation file. AUTOINST continues with the product installation. b. When all installation jobs are complete, the following message displays: All product installation jobs have been streamed successfully. c.
Modifying Your System 5.16 Rerunning HPINSTAL 5.16 Rerunning HPINSTAL To rerun hpinstal and finish applying the CSLT: 1. Remount the CSLT created by HPINSTAL. 2. Reinvoke HPINSTAL and resume previous installation. :HPINSTAL 3. If you are performing an Add-on or Update task, go to Step 4. If you are performing a Modify Remote System task, go to Step 5. Add-on Tasks, Update Tasks 4. Resume previous installation. a. Type YES at the prompt.
Modifying Your System 5.16 Rerunning HPINSTAL 3 Create a CSLT for another system 4 Create a CSLT with PowerPatch patches for another system 5 Complete the update of this system using a CSLT created on another system 6 Add SUBSYS products to this system 7 Add SUBSYS products and install patches from a Powerpatch tape Enter your choice >>5 Go to Step 8. 8. Restore the STORE portion of the CSLT. Mount the CSLT tape and put the tape drive online. If using DDS tape, remove the tape and reinsert it now.
Modifying Your System 5.17 Rerunning HP Patch/iX 5.17 Rerunning HP Patch/iX For Phase II of HP Patch/iX, you must log onto the system Console and have exclusive access to your system. To rerun HP Patch/iX and finish applying the CSLT or STORE tape: 1. Log onto the Console. :HELLO MANAGER.SYS,INSTALL;HIPRI 2. Lower session and job limits. :LIMIT 1,1 3. Warn, then log off users. :WARN@ PLEASE LOG OFF! SYSTEM UPDATE ABOUT TO BEGIN Use the SHOWJOB command to determine session and job numbers.
Modifying Your System 5.17 Rerunning HP Patch/iX HP Patch/iX (y/n)? NOTE This prompt is provided to allow you to continue, in the event that you halted the HP Patch/iX process prior to completing the CSLT creation (Phase I). If you accidentally type NO, HP Patch/iX purges all audit files and rebuilds them. If you did not complete the CSLT/STORE or STORE only creation (Phase I), you will have to start your patching process from the beginning.
Modifying Your System 5.
6 Finishing the Process This chapter describes all the finishing steps to bring your system back up after applying the changes to your system.
Finishing the Process 6.1 Configuring Datacomm and UPS 6.1 Configuring Datacomm and UPS No matter what your network configuration is, or even if you have no networked devices, you still must perform the activities described in this section if it is on your checklist. You must convert the data communications configuration files after modifying a system (regardless of whether you use data communications products).
Finishing the Process 6.1 Configuring Datacomm and UPS • Copy the NMCONFIG file from another system. The other system must be on the same release as the system you are working on and must have a similar configuration. Proceed to Step 2. 2. If you are getting a copy of the NMCONFIG file from another system: a. Log onto the other system and store the file. :HELLO MANAGER.SYS;HIPRI :FILE T;DEV=TAPE :STORE NMCONFIG.PUB.SYS; *T;SHOW b. Return to the system you are modifying and restore the file.
Finishing the Process 6.1 Configuring Datacomm and UPS • Through a LAN console card • Through a DTC Refer to Performing System Management Tasks for information on configuring UPS devices. Configuring Systems for Terminals, Printers, and Other Serial Devices also describes using NMMGR for configuring UPS devices. Go to Step 6. Cross Validating Task 6. If your files were not converted, you did not copy or create a new NMCONFIG file, and you are not changing your configuration file, proceed to Step 14.
Finishing the Process 6.1 Configuring Datacomm and UPS When DTS/LINK is validated, NMMGR automatically invokes SYSGEN to cross-validate the system and datacomm configurations. You have the option to customize the cross-validation steps by modifying the commands in the file NMGRXVAL.PUB.SYS. Comment information is contained in braces, {}. Refer to Performing System Management Tasks and Manager's Guide to MPE/iX Security.
Finishing the Process 6.2 Restoring User Files 6.2 Restoring User Files To restore your user files, perform either of these processes: • If you ran BULDACCT.PUB.SYS and did NOT use the STORE command DIRECTORY option as part of your backup, proceed to “Restore with BULDACCT files.” • If you ONLY did the STORE command with the DIRECTORY option, proceed to “Restore without BULDACCT files.” DO NOT perform both processes. Restore with BULDACCT Files If you ran BULDACCT.PUB.
Finishing the Process 6.3 Recovering Staging Areas 6.3 Recovering Staging Areas Recover staging areas, if they existed and if you need the previously existing staging areas. To recover your staging areas: 1. Check that HP Stage/iX is not already initialized. :STAGEMAN STATUS The following message displays if HP Stage/iX is not initialized: STAGEMAN A.00.00, (C) Hewlett-Packard Co., 1995. All Rights Reserved.
Finishing the Process 6.4 Setting Passwords, Lockwords, and UDCs 6.4 Setting Passwords, Lockwords, and UDCs To set passwords, lockwords, and UDCs: 1. Review account security. Refer to Manager’s Guide to MPE/iX Security and the HP Security Monitor/iX Managers Guide. 2. Set passwords for HP recommended accounts, if these accounts do not have passwords, see Table 6-1.. :ALTACCT acctname;PASS=password Password recommended accounts. Table 6-1.
Finishing the Process 6.4 Setting Passwords, Lockwords, and UDCs temporary COMMAND file. :PURGE COMMAND.PUB.SYS :RENAME command_name,COMMAND.PUB.SYS 8. If your users plan to use POSIX features on MPE/iX, and if it is not already set, set a special UDC. :SETCATALOG HPPXUDC.PUB.SYS;SYSTEM;APPEND 9. Log on to activate the UDCs. :HELLO MANAGER.SYS,PUB;HIPRI • Setting Passwords, Lockwords, and UDCs completed. Go to the next section on your checklist.
Finishing the Process 6.5 Configuring and Updating Manually Installed Products 6.5 Configuring and Updating Manually Installed Products Some products require additional configuration steps. Refer to your checklist for the products that were identified during previous procedures. 1. Refer to Appendix A , “Manually Installed Products,” and the appropriate product manual for these instructions. The products will not be operational until you perform the necessary configuration changes or update utilities.
Finishing the Process 6.6 Setting Up the TAR Utility 6.6 Setting Up the TAR Utility To perform the final steps: 1. Determine if the TAR utility is set up. :LISTFILE /dev/tape,2 If the output is similar to this: PATH= /dev/ CODE ---------LOGICAL RECORD---------- ----SPACE---- FILENAME SIZE TYP EOF LIMIT R/B SECTORS #X MX 128W BBd 0 1 1 0 0 * tape Then the TAR set up file already exists. Proceed to the next section on your checklist. If the output does not show a tape file, proceed to Step 2. 2.
Finishing the Process 6.7 Performing the Final Reboot 6.7 Performing the Final Reboot To reboot and restart the system: 1. Shut down the system. CTRL-A =SHUTDOWN 2. Reset the system after the last shutdown message (SHUT6). a. If you have an HP e3000 Series 991, 995 or 99x, connect to the service processor before you can restart the system. Type the following: CTRL-B CM>SP CM>RS Enter Y to HARD BOOT the computer system.
Finishing the Process 6.7 Performing the Final Reboot The system boots from disk. After some activity the ISL prompt displays. 4. At the ISL prompt, enter: ISL>START NORECOVERY 5. Confirm the date and time. If the date and time displayed are not correct, enter N, and enter the correct date and time. If you do not respond within 15 seconds, the system continues. MPE/iX launch facility Initialize_genesis - Version: <<870204.
Finishing the Process 6.8 Restarting Selected System Functions 6.8 Restarting Selected System Functions To restart selected system functions: 1. Log on. :HELLO MANAGER.SYS;HIPRI On local systems power cycle the DTCs. If you are using OpenView DTC Manager, the DTCs do not need to be power cycled. On remote systems reset DTCs. To power cycle all DTCs: a. Turn DTC off. b. Turn DTC on. Power cycling each DTC enables the new download file and the DTC configurations to be downloaded to the DTC(s). 2.
Finishing the Process 6.8 Restarting Selected System Functions a. Type: :cstm cstm> ru termdsm b. At the termdsm prompt, Type R: Connect DIag DTc DUmp EEprom Help Reset Status Trace EXit ?R c. For each DTC, Type: (reset) Ldev# POrt#,#,# SNp #,# (X.25 card in DTC) VC #,#,#, Slc #,# (multiplexer card in DTC) DTc # (carriage return to exit) ?DTCnn where nn is the DTC number. 5. Start Internet Services. If you have any Internet Services configured (telnet, ftp, etc.), stream the Internet Super Daemon job.
Finishing the Process 6.8 Restarting Selected System Functions Type an item number, an item key, or a command: __ g. Save the values, at the prompt, type YES: Do you wish to save these values (Y/N)? __ • Restarting Selected System Functions completed. Go to the next section on your checklist.
Finishing the Process 6.9 Backing Up Your System 6.9 Backing Up Your System To back up the system. 1. Mount a write-enabled tape to create a backup SLT. :SYSGEN sysgen>TAPE sysgen>EXIT 2. Dismount the tape, label as SLT with date, time and system version. 3. We recommend that you stop running the STM diagnostics daemon in oreder to back up the files associatedd with it. To do this, call up cstm and execute the “stmshutdown” command (shortcut “ssd”).
Finishing the Process 6.10 Permanently Applying a Staging Area 6.10 Permanently Applying a Staging Area You have these two options: • If you want to continue testing the set of patches you applied with the booted staging area, proceed to “Finishing Up.” • If you have tested and confirmed that you want to keep the set of patch changes, and if you have determined that you will not want to back out the patches, then proceed to Step 1 and commit to the staging area.
Finishing the Process 6.11 Finishing Up 6.11 Finishing Up Perform the steps in this section for all checklists. To perform the closing steps of your task: 1. The system is ready for normal production. 2. Display the first part of the HPSWINFO file to confirm the SUBSYS, PowerPatch, and Date code: :PRINT HPSWINFO 3. Record the date and release of the System Installation, Update, Add-on, and Patch in the system log book, as appropriate.
Finishing the Process 6.
Support Tools Manager (STM) for MPE/iX 7 Support Tools Manager (STM) for MPE/iX Support Tools Manager (STM) provides a set of support tools for troubleshooting computer system hardware, including CPUs, memory, interface cards, mass storage devices, etc.
Support Tools Manager (STM) for MPE/iX MPE/iX Version of STM MPE/iX Version of STM With MPE/iX 6.5, the Support Tools Manager (STM) replaced the sysdiag diagnostic system on HP e3000 computer systems. STM has been the diagnostic platform for HP-UX since 1996. STM was ported to MPE/iX to provide a common diagnostics platform for MPE/iX and HP-UX systems. This common platform will reduce the cost to support new systems and peripherals, and make it possible to bring new tools to MPE/iX 6.5 and beyond.
Support Tools Manager (STM) for MPE/iX Running STM (Summary) For EARLY VERSIONS of the pages, refer to the internal HP site at http://wojo.rose.hp.com/bea/systems/ Running STM (Summary) To start STM and run support tools: 1. Enter the command for the desired interface. Enter mstm (menu-based version) or cstm (command-line version) 2. If you want to test a remote machine, select the computer system to test. The remote machine must be running a compatible version of STM (i.e.
Support Tools Manager (STM) for MPE/iX Two Interfaces — Command: cstm Displays from the two interfaces are shown in the rest of this chapter.
Support Tools Manager (STM) for MPE/iX System Map and Device Icons System Map and Device Icons When you first connect to a computer system, you see a system map showing all the hardware entities in the system (CPU, memory, device adapters, and I/O devices). In mstm, the map appears automatically. In cstm, you must enter the map command. You use the system map to select the devices to test. After a test runs, the system map displays the results.
Support Tools Manager (STM) for MPE/iX System Map and Device Icons Navigation of the system map is done by using the Up/Down/Left/Right arrow keys and the Prev/Next or Page Up/Page Down keys. To select a specific device for testing, place the cursor on the specific device and press Return; all other devices are unselected. (To select a device and leave all other selected devices in their current state, place the cursor on the specific device and press the space bar.
Support Tools Manager (STM) for MPE/iX Kinds of Support Tools Kinds of Support Tools To use the diagnostics and support tools, the user first invokes one of the user interface modules (mstm or cstm), selects one or more devices, and invokes one of the following tools to specify what type of operation is to be performed on the device(s): NOTE Not all tool types are supported on all devices on all operating systems.
Support Tools Manager (STM) for MPE/iX Menus and Commands Menus and Commands The mstm and cstm interfaces have different ways to display menus and accept commands from the user. The following subsections detail the mstm and cstm menus and commands. mstm Menus and Commands In mstm, you traverse screens and menus, and select commands from pulldown menus: Figure 7-3.
Support Tools Manager (STM) for MPE/iX Menus and Commands Figure 7-4. mstm Pulldown Menu Example Screen Navigation There are two types of screen navigation: • Navigating between screens • Navigating within screens To navigate between one screen and another, use the Tab key. To navigate from one portion to another portion of the same screen, use the Prev and Next keys (or, alternatively, the Cursor Up and Cursor Down keys). Menu Bar The following table summarizes the use of the menu bar. Table 7-1.
Support Tools Manager (STM) for MPE/iX Menus and Commands Table 7-1. Menu Bar Navigation To do this: Do this: Perform a command Use the Return key. Invoke a menu directly: Use Alt function key; then hit non-underlined character in menu title. Activate a menu command/expand pulldown sub-menu: Hit the letter which is underlined in the command or sub-menu. Figure 7-5.
Support Tools Manager (STM) for MPE/iX Menus and Commands mstm Shortcut Keys A new 'shortcuts' feature has been added to mstm which lets you do frequently performed operations quickly. For example, to select all disks and then run the verify tool on them, the user would hit the keys 'dv' then while the mstm map is displayed.
Support Tools Manager (STM) for MPE/iX Getting Result Information (Logs) localmaplog (lml) localsysactlog (lsal) syslog (sl) os (os) exit (ex) daemonshutdown (dsd) daemonkill (dk) daemonactlog (dacl) map (map) Tools: information (info) infolog (il) infoactlog (ial) infofaillog (ifl) infoinfo (iinf) verify (ver) veractlog (val) verfaillog (vfl) verinfo (vinf) diagnose (dgn) diagactlog (dal) diagfaillog (dfl) diaginfo (dinf) exercise (exc) exeractlog (eal) exerfaillog (efl) exerinfo (einf) firmwareupdate (f
Support Tools Manager (STM) for MPE/iX Remote Execution Started: Tue Sep 28 08:31:05 1999 Failed: Tue Sep 28 08:31:05 1999 A UNIT ATTENTION was received as a result of the SCSI Read Capacity command. This is not necessarily an error, but indicates the device was undergoing built-in test or was previously reset. Possible Causes(s)/Recommended Action(s): The disk drive has been reset or the Mode Select parameters have been changed. Rerun the information module.
Support Tools Manager (STM) for MPE/iX Remote Execution Figure 7-7. Possible UI and UUT Connections Distributed Structure Efficient remote execution is possible because STM has a distributed structure. Figure 7-8. shows how the parts of STM are distributed between the UI machine and the UUT. (This diagram also shows xstm, which is only available on HP-UX.
Support Tools Manager (STM) for MPE/iX Getting Help Figure 7-8. Diagram of STM's Distributed Structure The UI system contains the binaries for the graphical, menu, and command line interfaces, as well as for the Core UI which underlies them. The UI also contains the text to be displayed (message catalogs and help volumes). The Unit Under Test (UUT) contains the binaries for the support tools (Diagnose, FW Update, Exercise, Expert, etc.) and the libraries which support them.
Support Tools Manager (STM) for MPE/iX Getting Help Figure 7-9. Sample Online Help Help Get Information on a Device To get information about a hardware device(s), run an information tool: 1. 2. 3. 4. 5. 6. device, Select Device(s). If desired, Select/Deselect Test Options. Select the “tools” pulldown menu. Run Information and consult the Information Log. Go back to the top level menu, and select the “device” pulldown menu.
Support Tools Manager (STM) for MPE/iX Common Problems Common Problems A device in the STM map is “Unknown” (MPE/iX) Many MPE/iX systems are “over-configured,” that is, their configuration files have more entries than are physically present on the system. STM lists these phantom entries on the system map, but cannot get any information from the non-existent devices to which they point. Consequently STM has to label these entries as “Unknown.
Support Tools Manager (STM) for MPE/iX Common Problems The “Device — >Select Class” command did not work. This is usually because the “Device Type” and “Qualifier Type” you selected don't both match a device in the system. For example, selecting a type of “Disk” and a qualifier of “SCSI” will not select any devices because SCSI disks use qualifiers of “Hard,” “Floppy,” etc. Use the “Device — >Current Device Status” command to determine the valid type and qualifier that apply to a specific device.
A Manually Installed Products Some products that you have installed require additional steps to be performed before they are fully functional. These products are referred to as manually installed products. When you install or update a manually installed product, system messages inform you that additional steps are required.
Manually Installed Products Installing ALLBASE/ SQL or IMAGE/SQL Installing ALLBASE/ SQL or IMAGE/SQL This applies to ALLBASE/SQL only if you have created SQL data using an earlier release of ALLBASE/SQL. If you are updating from an earlier release of ALLBASE/SQL, you must perform the ALLBASE/SQL migration to migrate your DBEnvironments to the G.3 format. The method used depends upon the version of ALLBASE/SQL you are currently running.
Manually Installed Products Installing ALLBASE/ SQL or IMAGE/SQL Updating from Version E.1 or F.0 If your old release of ALLBASE/SQL is E.1 or F.0, use SQLMigrate to migrate to version G.3. Backup the DBEnvironment prior to running SQLMigrate. The steps listed below also appear in the ALLBASE/SQL Database Administration Guide. Use the following procedure to convert a DBEnvironment from either an E.1 or F.0 format to the G.3 format: 1.
Manually Installed Products Installing ALLBASE/ SQL or IMAGE/SQL stored in the DBECON file. The following is a sample listing. START DBE NEWLOG BEGINNING (MON, JUL 19, 1995, 4:12 PM) START DBE 'DBENAME' NEWLOG BUFFER = (100,24), TRANSACTION = 2, MAXIMUM TIMEOUT = NONE, DEFAULT TIMEOUT = MAXIMUM, RUN BLOCK = 37 LOG DBEFILE LOG1 WITH PAGES = 250, NAME = 'DBELOG1'; START DBE NEWLOG SUCCEEDED (MON, JUL 19, 1995, 4:13 PM) 7. Exit SQLMigrate: SQLMIGRATE=> EXIT; 8.
Manually Installed Products Installing ALLBASE/ SQL or IMAGE/SQL 2. Perform the ALLBASE/SQL migration update to release G.3 from E.1 or F.0. Additional ALLBASE/SQL References For additional information, please refer to the following ALLBASE/SQL reference materials.
Manually Installed Products Preparing OpenView Console/System Manager Preparing OpenView Console/System Manager The HP OpenView Console/System Manager (OVC/SysMgr) product uses a client/server design that includes software that resides on both the PC and HP e3000. The software component on the HP e3000 is MPE/iX version independent. You will receive special patch updates when new OVC/SysMgr’s HP e3000 software is released. 1.
Manually Installed Products Preparing OpenView Console/System Manager managed node software version is A.01.03. :VERCHECK.EMS.SYSMGR 6. On the management node, use the VERCHECK.PUB.SYSMGR program to verify that the management node software version is A.01.03. :VERCHECK.PUB.
Manually Installed Products Installing SNA IMF/iX Installing SNA IMF/iX Follow the steps below using the TTSINST command file to complete the installation of SNA IMF/iX (HP30293). You can also access the online instructions by typing TTSINST.PUB.SYS at the colon prompt without specifying any parameters. To install the English language option for the United States and European sites: 1. Type the following commands: :HELLO MANAGER.SYS;HIPRI :TTSINST 000 2.
Manually Installed Products Configuring HP Predictive Support Configuring HP Predictive Support NOTE The job JPSMON.PRED.SYS needs to be running or Predictive Support will not perform its daily scheduled run to monitor your system. The directions in this section only describes how to update an existing version of HP Predictive Support.
Manually Installed Products Java/iX Installation Instructions Java/iX Installation Instructions To install Java/iX after the update or install of MPE/iX 7.0: 1. Remove any passwords from MANAGER.SYS. 2. Read README.INSTALL.JAVA for any last-minute changes or additions to the installation process, and for general usage instructions. 3. Stream the installation job: :STREAM JINSTJDK.INSTALL.
Manually Installed Products Configuring File Transfer Protocol (FTP) Configuring File Transfer Protocol (FTP) To configure FTP so it is enabled after the update or install of the latest version of MPE/iX: 1. Remove any passwords from MANAGER.SYS. 2. Stream FTPCNFJ.ARPA.SYS. :STREAM FTPCNFJ.ARPA.SYS. This will add FTP entries to the appropriate Internet Super Daemon files.
Manually Installed Products ODBCLink Installation ODBCLink Installation Traditionally, ODBCLink/SE was included in patches for ALLBASE/SQL and IMAGE/SQL products. The product structure has been changed in MPE/iX 6.0 Express 1, so that ODBCLink/SE is delivered as a separate patch, resulting in more flexibility in upgrading the product. When the ODBCLink/SE patch is applied, the following files are placed in ODBCSE.SYS: HFSFILES.ODBCSE.SYS I00IODBC.ODBCSE.SYS HPREADME.ODBCSE.SYS Stream I00IODBC.ODBCSE.
B Configuration Tables Table B-1., “Configname,” on page 197 show the configuration names available for the models of the HP e3000 series. All the groups shown are in the SYS account. Table B-1.
Configuration Tables Table B-2. N-Class and A-Class configurations System DEVICE TYPE SCSI PATH CONFACL1 LDEV#1 INTERNAL DISK 0/0/2/1.15.0 LDEV#7 EXTERNAL TAPE 0/0/2/0.6.0 LDEV#1 EXTERNAL (ARRAY) 0/2/0/0.0.6 LDEV#7 EXTERNAL TAPE 0/0/2/0.6.
C Managing Disk Space This chapter includes the following information: • Determining Available Disk Space • Recovery from “Out of Disk Space” during Update • Using the ShowUSAGE Command • Using the ALTERVOL Command • Using Alternative Disk Space Allocation If you are on release 5.0 or later and do not have sufficient contiguous disk space on LDEV 1, follow the instructions in this Appendix. If you are on a release earlier than 5.0, first upgrade to release 5.0 or 5.
Managing Disk Space Determining Available Disk Space Determining Available Disk Space If you do not have enough disk space, determine how much disk space you do have available before you proceed with clearing more space. 1. Determine available contiguous disk space on your system. :run discfree.pub.sys;info=”B,ldev,volume_set_name” Use option C to see each drive separately. where: ldev is the device number assigned to LDEV 1. volume_set_name is the name assigned to the MPE system volume set.
Managing Disk Space Recovery from “Out of Disk Space” during Update Recovery from “Out of Disk Space” during Update It is now possible to recover from “Out of Disk Space” during an Update. UPDATE will skip any file if it cannot be added to LDEV 1. You will see error and status messages on the console at the point the file is skipped and at the end of UPDATE. At the end of the UPDATE, when the system normally boots, the system will stop. The operator must boot the machine manually.
Managing Disk Space Recovery from “Out of Disk Space” during Update 5. Redo the UPDATE from the same tape. (The files ISL.MPEXL.SYS and MMSAVE.MPEXL.SYS are small so there should not be a problem restoring them. The file START.MPEXL.SYS is large, but under reasonable conditions instead of just skipping it, the file DUMPAREA.MPEXL.SYS is purged by UPDATE to make room for START.MPEXL.SYS. If DUMPAREA.MPEXL.SYS is purged, it will be replaced by UPDATE when enough disk space is available.
Managing Disk Space Using the SHOWUSAGE Command Using the SHOWUSAGE Command After you have updated your system to Release 5.0 or later, you should no longer use the CONTIGXL utility to locate contiguous disk space on LDEV 1. Instead use the SHOWUSAGE command in the VOLUTIL utility. SHOWUSAGE provides the same information as CONTIGXL. To locate contiguous disk space using VOLUTIL: 1. Return to the ISL prompt. Enter the following to start the system from the disk: ISL> START NORECOVERY 2.
Managing Disk Space Using the SHOWUSAGE Command :BUILD AXLDEV1.PUB.SYS;DISC=n,1,1;DEV=1 Where n is the amount of contiguous disk space required on your system. 8. Refer to “Determining Available Disk Space” earlier in this Appendix to determine if you have enough disk space to continue with your task. If you do have enough disk space, return to the procedure you were working on and continue with the instructions. If you do not have enough disk space, proceed to “Using the ALTERVOL Command.
Managing Disk Space Using the ALTERVOL Command Using the ALTERVOL Command Use ALTERVOL to clear additional disk space for use during the modification (patch, add-on, update, or install) process. The ALTERVOL command sets the percentage of allowable use for each disk. CAUTION If you use the ALTERVOL command to increase the allowable percentage of use for LDEV 1, you MUST return the disk usage percentage back to its original settings after you perform the system modification.
Managing Disk Space Using the ALTERVOL Command CAUTION You MUST reset the ALTERVOL values after you complete your system modification. 9. Refer to “Determining Available Disk Space” earlier in this appendix to determine is you have enough disk space to continue with your task. If you have enough disk space, return to the procedure you were working on and continue with the instructions. If you do not have enough disk space, proceed to “Using Alternative Disk Space Allocation.
Managing Disk Space Using Alternative Disk Space Allocation Using Alternative Disk Space Allocation Before starting UPDATE, reserve contiguous disk space in the file AXLDEV1.PUB.SYS. This amount is at least 60,000 sectors but may be larger. The prudent way to reserve this space is in one contiguous block.
Managing Disk Space Using Alternative Disk Space Allocation available and the time to REINSTALL your system. If UPDATE runs out of space on LDEV1, you risk having to REINSTALL. Override this warning message [OVERRIDE/NO; default = NO]? 4. Return to the procedure you were working on and continue with the instructions.
D Backdating Your System This appendix contains instructions for returning your system software to a previous release (backdating).This chapter describes general backdating methods that will work in most cases. WARNING If you are on an N-Class or A-Class system you cannot backdate to software before 7.0. CAUTION Perform a backdate when you have updated your operating system version and have serious problems. Only do this under direction from your HP representative or Response Center.
Backdating Your System Planning Your Backdate Planning Your Backdate Planning can and should be done prior to performing your backdate. The backdate requires downtime and planning it ensures that all the requirements are met.
Backdating Your System Planning Your Backdate Response Center, if you have a software support contract, or your HP representative, before deciding to backdate your system. If your Hewlett-Packard representative and you both agree that backdating your operating system is necessary, follow the steps below. Please read all the instructions in this chapter before you begin your backdate. Determine what prior IO devices you will back date to.
Backdating Your System Planning Your Backdate certain purchasable products. Before you proceed, we recommend that you read: • The Communicator 3000 for the release you are backdating to, as well as the copy you received with your new release. These documents provide additional information on backdating specific products. • Check that any new disk drive in the configuration is supported on the release you are backdating to. Patch Considerations If you have applied patches to your level 6.0 or 5.
Backdating Your System Planning Your Backdate Method 3: Using an FPT If any patches were applied to your 6.0 or 5.5 system, they must be reapplied from the PowerPatch tape(s) after the backdate. Follow the appropriate manual for the release you are backdating to. Check Patch Tape Media To verify the patch tape source media and contents: 1. Log on from the console with the following conditions. :HELLO MANAGER.SYS,INSTALL;HIPRI :OPENQ LP :STREAMS streams_device An LP device must be configured in SYSGEN.
Backdating Your System Planning Your Backdate Validate Your System Backup (Method 1) If you are using a CSLT (Method 1) to backdate your system, perform the steps in this section. If you are using a Factory SLT (Method 2) or a Factory Preload Tape (Method 3), proceed to “Check for Disk Space.” Before you begin the process of backdating, log on and verify that your backup tape is valid. 1. From the console, log on with the following conditions. :HELLO MANAGER.
Backdating Your System Planning Your Backdate 3. If you do not have enough disk space, either contiguous (AXLDEV) or non-contiguous (AXLSPACE): • Store files to tape. Purge the stored files from the system. • Purge the files and groups as directed in Steps 8 through 10 of the next section, “Securing Your System.” • Refer to Appendix C , “Managing Disk Space,” for directions on clearing space.
Backdating Your System Securing Your System Securing Your System Securing your system prepares it and your users for a shutdown. Refer to “Securing the System for Tape Tasks” in Chapter 5 , “Modifying Your System,” for additional information about these steps. 1. If you are not already in the PUB group, change groups now. :CHGROUP PUB 2. Lower limits. :LIMIT 0,0 :WARN@ PLEASE LOG OFF! SYSTEM UPDATE ABOUT TO BEGIN 3. Log users off.
Backdating Your System Securing Your System a. If you have ALLBASE/SQL, issue starts for each DBEnvironment that you want to migrate before you back up the system. Refer to the ALLBASE/SQL Database Administration Guide for more information. b. If you have ALLBASE/4GL, unload all existing ALLBASE/4GL applications, if you have them on your system. Refer to the HP ALLBASE/4GL Developer Administration Manual for more information. c.
Backdating Your System Performing the Backdate Performing the Backdate In this section you backdate your system. The procedures vary depending upon the backdate method you are using. Refer to the appropriate section.
Backdating Your System Performing the Backdate CTRL-B CM>RS If the system does not respond, press the reset button, key switch, or on/off switch as appropriate for your system. Enter Y to confirm restarting the system. d. Boot the system from the alternate boot path, where the CSLT is mounted. a. Boot messages can vary, depending on the system model. b. Enter Y to the Interact with IPL? prompt, if it appears on your screen. The system boots from the alternate source (tape).
Backdating Your System Performing the Backdate 5. Confirm the date and time. 6. Dismount the CSLT. 7. Log on, start the spooler, and streams device. :HELLO MANAGER.SYS,INSTALL;HIPRI :LIMIT 1,1 :SPOOLER LP;OPENQ :STREAMS streams_device where streams_device is the device number. A common streams_device value is 10. An LP device must be configured in SYSGEN. Already spooled and streamed messages might display.
Backdating Your System Performing the Backdate Mount the FOS tape and put the tape drive online. The files from the FOS tape will now be restored. **** PLEASE STAND BY **** The FOS tape files are being restored. `CREATE' OPTION DEFAULTING TO `CREATE=ACCOUNT,GROUP,CREATOR' BASED ON YOUR CAPABILITIES (S/R 502) STORE/RESTORE VERSION A.nn.nn (C) HEWLETT-PACKARD CO. b. Dismount the FOS tape when the restore complete message displays. The files from the FOS tape were successfully restored.
Backdating Your System Performing the Backdate AUTOINST automatically streams the installation jobs that complete the installation of most products. Begin processing installation files. Processing n installation files. ... *the number of dots equals n* The message may indicate zero installation files. This only means that the products you are installing do not require an installation file. AUTOINST continues with the product installation.
Backdating Your System Performing the Backdate :FILE T;DEV=TAPE :RESTORE *T;NMCONFIG,HPSWINFO;OLDDATE;DEV=1;SHOW c. Decide if you need to modify the configuration to configure devices not configured in the restored file. 9. Proceed to “Finishing Up.” Method 2: Using Factory SLT To perform a backdate using your Factory SLT (Method 2), perform the steps in this section. Apply the SLT Applying the SLT modifies your system and begins the backdate process.
Backdating Your System Performing the Backdate 2. Enter Y to the Interact with IPL? prompt, if it appears on your screen. The system boots from tape. After some activity the ISL prompt displays. 5. Check FASTSIZE value: ISL>DISPLAY If the value is not F, then change it to F: ISL>FASTSIZE F If you changed the FASTSIZE value: a. Reset the system again to set the new Fastsize value. b. Reboot from the alternate boot path. 6. Update the system with the factory SLT. ISL>UPDATE 7. Confirm the date and time.
Backdating Your System Performing the Backdate Start the System When the update is complete, autoboot begins. Perform the following steps to ensure the system is up and running. Refer to “Starting the System” in Chapter 5 , “Modifying Your System,” for additional information about these steps. 1. Start the system. ISL>START NORECOVERY NOSYSSTART group=configname configname—the configuration group for your system. Refer to Appendix B , “Configuration Tables,” for a list of configuration groups. 2.
Backdating Your System Performing the Backdate If you modified your configuration after updating to the latest Release, you must reenter these modifications at this point. This includes I/O changes, and any modifications made to logging events, system files (SYSFILE), or miscellaneous (MISC) items. sysgen> KEEP Purge old config? YES sysgen> EXIT If you do not have a backup of your old CONFIG.SYS group, modify your configuration manually as described in Step 2. Otherwise, skip to Step 3. 2.
Backdating Your System Performing the Backdate If the system does not respond, press the reset button, key switch, or on/off switch as appropriate for your system. Enter Y to confirm restarting the system. 5. Boot the system from the primary boot path. 1. Boot messages can vary, depending on the system model. 2. Enter Y to the Interact with IPL? prompt, if it appears on your screen. The system boots from disk. After some activity the ISL prompt displays. 6. Start the system.
Backdating Your System Performing the Backdate :CHGROUP INSTALL 2. Run AUTOINST. :RUN AUTOINST.INSTALL.SYS 3. If you receive a missing capabilities message: Program requires more capabilities than group is allowed. (LDRERR505) Native mode loader message 505 UNABLE TO LOAD PROGRAM TO BE RUN. (CIERR 625) a. Use CHGROUP to change to the PUB.SYS group. :CHGROUP PUB b. Use ALTGROUP to add the BA, IA, PM, MR, DS, and PH capabilities to the INSTALL group :ALTGROUP INSTALL; CAP=BA,IA,PM,MR,DS,PH c.
Backdating Your System Performing the Backdate a. Refer to the action statement of the error message in Appendix H , “Error Messages and Warnings.” b. When you find the required disk space, issue the Autoinst command again. 8. Restore FOS files. This step takes about 20–45 minutes. a. Mount FOS tape and reply to tape request when the following message displays. Mount the FOS tape and put the tape drive online. The files from the FOS tape will now be restored.
Backdating Your System Performing the Backdate The SUBSYS tape has been successfully restored. • AUTOINST automatically streams the installation jobs that complete the installation of most products. The message may indicate zero installation files. This only means that the products you are installing do not require an installation file. AUTOINST continues with the product installation. • AUTOINST creates a copy of the system libraries and displays: • AUTOINST processes the files.
Backdating Your System Performing the Backdate configuration file that will be restored will require conversion using the NMMGRVER.PUB.SYS utility after the installation. Apply the CSLT Refer to “Applying the Modification” in Chapter 5 , “Modifying Your System,” for additional information about these steps. To apply the CSLT: 1. From the console, mount the CSLT created from the factory SLT, FOS and SUBSYS of the release to which you want to backdate. Refer to “Restore FOS and SUBSYS”.
Backdating Your System Performing the Backdate ISL>UPDATE 6. Monitor progress messages. While the UPDATE process is taking place, it is important that you monitor the process at the console. Note any errors that may be reported to the screen for future action. If you modified your configuration after updating to Release 5.5, you may need to check the configuration when the backdated system is up and running normally.
Backdating Your System Performing the Backdate Apply the FPT Refer to “Applying Modifications” in Chapter 5 , “Modifying Your System,” for additional information about these steps. 1. From the console, mount the Factory Preload Tape for this system. Place it into the DDS device. Put the tape drive online. Wait until the tape is mounted. A message displays on the system console verifying that the tape mounted. 2. Shut down the system. CTRL-A =SHUTDOWN 3. Reset the system.
Backdating Your System Performing the Backdate 6. Monitor progress messages. While the UPDATE process is taking place, it is important that you monitor the process at the console. Note any errors that may be reported to the screen for future action. If you modified your configuration after updating to Release 5.5, you may need to check the configuration when the backdated system is up and running normally.
Backdating Your System Performing the Backdate • an LP device class • a streams device • a tape drive (that matches the FOS and SUBSYS media type) If you need information about hardware device IDs, print the file IODFAULT.PUB.SYS on your screen. This file contains ID numbers and associated parameters for hardware devices. You can display this file when the system is up and you have the system prompt. To configure your I/O and save the customized set of configuration files, perform the following steps: 1.
Backdating Your System Performing the Backdate CM>SP SP>RS Enter Y to HARD BOOT the computer system. b. For HP e3000 N-Class, A-Class CTRL-B GSP>RS c. For all other systems: CTRL-B CM>RS If the system does not respond, press the reset button, key switch, or on/off switch as appropriate for your system. Enter Y to confirm restarting the system. 5. Boot the system from the primary boot path. a. Boot messages can vary, depending on the system model. b.
Backdating Your System Performing the Backdate • HPINSTAL automatically streams the installation jobs that complete the installation of most products. The message may indicate zero installation files. This only means that the products you are installing do not require an installation file. HPINSTAL continues with the product installation. The time it takes to restore the software files varies depending on how many and which specific subsystems you have on your system. 4.
Backdating Your System Finishing Up Finishing Up To restart your system on the backdated version, perform all the sub-sections in this section. Configure Data Communication Refer to “Configuring Datacomm and UPS” and “Cross Validating” in Chapter 6 , “Finishing the Process,” for additional information about these steps. CAUTION No matter what your particular networking configuration is, whether you even have networked devices, you still must perform the activities described in this section.
Backdating Your System Finishing Up used to create the backup. Then proceed to Step2. 2. Run the NMMGRVER conversion utility. :RUN NMMGRVER.PUB.SYS 3. Enter NMCONFIG.PUB.SYS at the prompt: FILESET TO BE SCANNED? NMCONFIG.PUB.SYS OK TO CONVERT NMCONFIG? Y • If the return message is no need to convert, proceed to “Restart System Functions.
Backdating Your System Finishing Up d. If you need to configure new DTCs on your system or if you need more information on host-based network management, refer to Configuring Systems for Terminals, Printers, and Other Serial Devices. 4. Display the Validate screen and validate the DTSLINK, NS links, and any other configurations you have changed. The specific method you use to view the Validate screen varies depending upon the procedures you used to modify the configuration file.
Backdating Your System Finishing Up CONV HPPL85 INDHPE SAMBA SYSMGR HPLANMGR HPPL87 INTSETUP SNADS TELESUP HPNCS HPPL89 ITF3000 SUPPORT WWW SOFTREP 2. Set passwords for HP recommended users. :ALTUSER username;PASS=password These users were created or modified to have OP (System Supervisor) and/or PM (Privilege Mode) capabilities. Hewlett-Packard recommends that you set passwords for these users. MANAGER.SYS FIELD. HPPL85 MGR.SNADS MGR.HPOFFICE MGR.TELESUP MGR.SYSMGR MGR.JAVA 3.
Backdating Your System Finishing Up Where command_name is a temporary name you assigned the file. Refer to your task checklist for the temporary name of this file. 3. Set special UDCs, if your users plan to use POSIX features on MPE/iX. :SETCATALOG HPPXUDC.PUB.SYS;SYSTEM;APPEND 4. Log on to activate the UDCs. :HELLO MANAGER.SYS,INSTALL Configure Manually Installed Products Refer to Appendix A , “Manually Installed Products,” and the appropriate product manual for instructions.
Backdating Your System Finishing Up CM>RS If the system does not respond, press the reset button, key switch, or on/off switch as appropriate for your system. Enter Y to confirm restarting the system. 3. Boot the system from the primary boot path. a. Boot messages can vary, depending on the system model. b. Enter Y to the Interact with IPL? prompt, if it appears on your screen. The system boots from disk. After some activity the ISL prompt displays. 4. At the ISL prompt, enter: ISL>START NORECOVERY 5.
Backdating Your System Finishing Up DTc # (carriage return to exit) ?DTCnn where nn is the DTC number. 2. Purge groups. :PURGEGROUP USL :PURGEGROUP UXL :PURGEGROUP UNL 3. Start data communications. If you have NS 3000/iX configured, bring up the configured network interfaces. For more information, refer to the HP e3000/iX Network Planning, and Configuration Guide. NOTE Use the same names for the network interfaces that were used in your configuration.
E CD-ROM Resources This Appendix provides additional reference material for using CD-ROMs. It includes: • Further background on the information required as you are updating MPE/iX.
CD-ROM Resources HP Release Version Numbers (v.uu.ff) HP Release Version Numbers (v.uu.ff) HP version numbers specify the exact version of the software with which you are working. Version numbers have the format: v.uu.ff where: v the version of the software used to represent significant changes. uu the update number. ff the fix level. For example, Release 5.5 has the following version number: C.55.
CD-ROM Resources CD-ROM Disk Volume Set Names CD-ROM Disk Volume Set Names HP sends you two CD-ROM disks containing the latest software. The release version numbers are used as part of the name for the CD-ROM volume sets that contain the software you will use to update a system. The volume set names for the disks appear on the label. CD-ROM disk volume set names have the following form: MPE_ v.uu.ff_n where: v.uu.ff the release version number such as C.55.00. n the volume set number within the release.
CD-ROM Resources Loading and Mounting CD-ROM Disks Loading and Mounting CD-ROM Disks HPINSTAL supports two types of CD-ROM drives: HP-IB and SCSI drives. SCSI drives are the only ones available for purchase at this time. Loading CD-ROM Disks The CD-ROM disk volumes are sent in a plastic case. If your system has a caddy, you need to remove the disk from the case and put it into the appropriate caddy for your CD-ROM drive. You can then load the CD-ROM disk into the drive.
CD-ROM Resources Loading and Mounting CD-ROM Disks To dismount a CD-ROM disk from an HP-IB drive: :VSCLOSE volume_set_name Checking Volume Set Status To check on the status of the CD-ROM disks, you can use the DSTAT command. For example: : DSTAT LDEV-TYPE STATUS VOLUME (VOLUME SET - GEN) ---------- -------- -------------------------11- 017070 LONER HPINSTAL (MPE_C.55.00_1-0) 12- 017070 LONER HPINSTAL (MPE_C.55.
CD-ROM Resources Creating a Product List Creating a Product List To simplify the update process, you can manually create a product list. HPINSTAL uses the product list to determine which products to update. Two types of product lists are useful when using HPINSTAL: • Master Product List —PRODLIST.PUB.SYS—lists all products that are on your Hewlett-Packard Software Support contract. These products are also listed on the product list included with the keyword certificate that comes with the CD-ROM disks.
CD-ROM Resources Creating a Product List Figure E-1 shows a sample PRODLIST file. Figure E-1. Sample PRODLIST File B1710A B1720A B1721A B1722A B1723A HP32106 HP36578 To make a product list using HPINSTAL, reply with the list of product numbers when prompted for them. After you finish entering the list, HPINSTAL asks you to verify that the list of products is correct and then saves the list in the file PRODLIST.PUB.SYS.
CD-ROM Resources Including Additional STORE Files on the CSLT Including Additional STORE Files on the CSLT HPINSTAL allows you to specify additional STORE files to be included on a CSLT to be distributed to another system. These files could be any files such as a third-party software package or data files required by an application. They must be STORE files because they are appended to the STORE portion of the CSLT. You need to set up a file listing the additional files to be included on the CSLT.
CD-ROM Resources Specifying the Base Configuration Group Specifying the Base Configuration Group MPE/iX provides default configuration groups for each hardware model. For example, names of some of the groups are confg950, confg930, and confg922 and they are located in the SYS account. When you set up your system, you normally use one of the default configuration groups to begin with and modify it so it matches the exact configuration of the system.
CD-ROM Resources Preparing a Base Group for a Remote System Preparing a Base Group for a Remote System If you are creating a CSLT for distribution to another system, HPINSTAL allows you to include your own installation-specific system files on the CSLT. You can specify these files in a base group. The base group must be a valid configuration group created using SYSGEN.
CD-ROM Resources Preparing a Base Group for a Remote System no NMCONFIG file in this configuration. WARNING NMCONFIG.PUB.
CD-ROM Resources Selecting an Output Device Selecting an Output Device HPINSTAL sets the output device where the CSLT is created to device class TAPE. If you use the default, HPINSTAL will write to any device of class TAPE. You can change the default when HPINSTAL requests the information. You need to know the LDEV number of the tape device where you want to create the CSLT.
CD-ROM Resources Selecting an Output Device LDEV: 8 DEVNAME: ID: HPC1501A PATH: 4.3.5 CLASS: TAPE OUTDEV: 0 RSIZE: 128 MPETYPE: 24 MODE: R DEVTYPE: TAPE MPESUBTYPE: 6 The R after MODE signifies that AUTOREPLY is on.
CD-ROM Resources Locating Your Keyword Locating Your Keyword HP provides a keyword certificate with each release of the software. The keyword certificate includes the following information: • Your keyword • System handle • System HPSUSAN • Release version • Instructions • Entitlement certification that lists all products purchased The system handle is a name used to identify the system. The system HPSUSAN is a number that specifies the hardware ID (for the system CPU).
CD-ROM Resources Locating Your Keyword Incorrect Keyword Entry If you choose not to create KEYFILE.PUB.SYS, HPINSTAL gives you three interactive attempts to enter the keyword correctly. If you fail to enter the keyword correctly by the third try, HPINSTAL terminates. Double check that you have entered the correct keyword as shown on the keyword certificate and try again.
CD-ROM Resources Copying Tapes for Distribution Copying Tapes for Distribution This Appendix describes how to use the SLTCOPY tool that allows you to copy CSLTs for distribution to other sites. SLTCOPY is intended only for copying CSLT/STORE tapes generated by HPINSTAL.
CD-ROM Resources Copying Tapes for Distribution Copying the CSLT from Tape to Tape You can use SLTCOPY to copy the CSLT/STORE tapes created for distribution to another system. The number of tape volumes that make up the CSLT varies depending on the type of tape you are using and the size of the system. You have to copy each tape volume separately. Depending on the number of tape drives you have, you can make up to nine copies of each tape at a time.
CD-ROM Resources Copying Tapes for Distribution the PIN is 74 and the LDEV number is 7. ?15:19/#S2/74/LDEV# FOR “MASTER” ON TAPE (NUM)? CTRL A =reply 74,7 8. Next you will see the following message on the terminal where you ran SLTCOPY: Reply for COPY1 is needed. On the system console, you need to reply with the PIN number and the LDEV number of the device to which you are copying. Following is an example tape reply performed at the system console. In the example, the PIN is 74 and the LDEV number is 8.
CD-ROM Resources Copying Tapes for Distribution account. For example: :HELLO MANAGER.SYS,INSTALL To copy each CSLT tape volume into a separate disk file: 1. Load the tape you want to copy from. Start with the first tape volume of the CSLT if you have more than one. Be sure that the write enable ring is removed from the tape or that the tape is otherwise write-protected. Note the LDEV number of the tape drive. 2. Invoke SLTCOPY on any terminal. You do not need to be on the system console.
CD-ROM Resources Copying Tapes for Distribution 7. It takes approximately one hour to copy a DDS tape. SLTCOPY informs you how long it actually took to make the file. It then redisplays the main SLTCOPY menu. When you finish making a separate disk file for each tape volume in the CSLT tape set, you can copy each file to tape, making as many copies as you need to support additional systems.
CD-ROM Resources Copying Tapes for Distribution Old disk file name? TAPE1R55 Description: File contains tape 1 Release 5.5 CSLT. Version: 1 Create date: FRI, MAR 25, 1994, 5:58 PM MPE/iX SLT TAPE Correct [YES]? [RETURN] If you press [RETURN] in response to “Old disk file name?”, you will return to the main SLTCOPY menu. 6. SLTCOPY then asks for the number of copies. Type the number of copies you are making at this time. (This number must correspond to the number of tapes you have mounted on tape drives.
CD-ROM Resources Copying Tapes for Distribution you want to copy. Copying to or from Remote Disk Files You can use the procedures described in the sections “Copying the CSLT from Tape to Disk” and “Copying from Disk to Tape” when copying to or from a remote disk file. Your system must have access to networking software (such as NS 3000) to connect remotely with other systems. You need to know the node name of the remote system on which the disk file is or will be placed.
CD-ROM Resources Copying Tapes for Distribution remote tape drive on a system called REMSYS. Only the part of the procedure that differs from the normal procedure for copying is shown. :DSLINE REMSYS :REMOTE HELLO username.account,group :FILE MASTER=MASTER:REMSYS;DEV=TAPE :SLTCOPY Select mode (? = help) Select mode 1 or 3 1 Copy tape to disk file 2 Copy disk file to tape 3 Copy tape to tape Which option do you wish to use < Enter 'E' to exit>? 3 ... SLTCOPY redirects MASTER according to the file equation.
CD-ROM Resources Copying Tapes for Distribution When you run the job stream, replies for the tape devices will still be required at the console. If an error occurs, SLTCOPY will write the cause of the error to the spoolfile, and the job will abort. The following is an example job stream called COPYJOB used for copying tape to tape: !JOB COPYJOB, MANAGER.
CD-ROM Resources Adding a CD-ROM Drive Adding a CD-ROM Drive This section describes how to configure HP-IB and SCSI CD-ROM drives as disk devices to an MPE/iX system. It describes software configuration only. Refer to the documentation supplied with your CD-ROM drive for information about the hardware. If you need further assistance, contact your HP representative. Prerequisites This section describes connecting the CD-ROM drives to an existing MPE/iX system.
CD-ROM Resources Adding a CD-ROM Drive 5. Invoke the IO configurator in SYSGEN to modify the configuration: :SYSGEN sysgen>IO Add the device: io>AD LDEV= ldev PATH= path ID= prod# where: ldev logical device number of the CD-ROM drive. path hardware path to the CD-ROM drive (e.g., 36.1.3 or 52.4). prod# identification number of the CD-ROM drive (i.e., for HP-IB: HPC1707A; for HP SCSI: HPA1999A; for Toshiba 3401 SCSI: CD-ROM-XM-3401TA or CD-ROM-XM-4101TA).
CD-ROM Resources Adding a CD-ROM Drive be set correctly. 10.If installing a SCSI CD-ROM drive, be sure that the SCSI bus is terminated properly at each end of the bus. 11.Power on the CD-ROM drive. 12.Power on the computer and boot the system from the primary path. The boot message varies depending on the system model. If you system asks you to enter the boot path, enter the primary boot path. If your system asks “Boot from primary path?” respond Y.
CD-ROM Resources Adding a CD-ROM Drive This program has the capability to identify the configuration of the system and its I/O paths and devices. Many of the components of the I/O system can be tested with selftest and loopback diagnostics. . . . Do you wish to modify any program parameters? N Record or print the I/O configuration table displayed on the screen. This display shows all path names of the I/O components. These pathnames will be needed later to add to the SYSGEN I/O configuration.
CD-ROM Resources Adding a CD-ROM Drive 14.Start the system: ISL>START NORECOVERY You can now proceed to use the CD-ROM drives on your system.
CD-ROM Resources Adding a CD-ROM Drive 274 Appendix E
F HP Patch/iX Reference This appendix provides a detailed description of the HP Patch/iX tool and options and includes these sections: • Using HP Patch/iX • HP Patch/iX Main Menu • Selecting Activities • Viewing Patches • Qualifying Patches • Creating a Patch or Stage Tape • Exiting HP Patch/iX Hewlett-Packard recommends that you always restore HP Patch/iX from the patch tape. This ensures that you are using the most recent version of HP Patch/iX. For installation instructions, refer to section 4.
HP Patch/iX Reference Using HP Patch/iX Using HP Patch/iX This section describes how to move within HP Patch/iX. To select a menu item: 1. From a HP Patch/iX screen or window, highlight an option. Use either the arrow keys or the [j] and [k] keys to move up and down the list. 2. Press [Return]. Lists of patches display in the data area of screens. You can Mark or Unmark an item. Marked items are included in the processing activity. Unmarked items are not included in the processing activity.
HP Patch/iX Reference Using HP Patch/iX Table F-1.
HP Patch/iX Reference Using HP Patch/iX Selecting Filter and View Options There are several filter and view options for viewing patch information. The current filter or view being displayed is listed in the upper right corner of the HP Patch/iX screen. To select a specific filter or view, press the function key to toggle between the filter or view options, or press the number key that corresponds to the filter or view. Information Windows Information windows do not require a response from you.
HP Patch/iX Reference Using HP Patch/iX • To use Help, press [F1]. A message displays with information about the current screen or error message. • To exit Help, press [F8].
HP Patch/iX Reference HP Patch/iX Main Menu HP Patch/iX Main Menu The HP Patch/iX Main menu displays the following list of available activities: Select Activities lists the type of patching options you can apply to your system using HP Patch/iX. View Patches displays lists of patches. There are several filters defined that allow you to view selected patches. Qualify Patches Evaluates the submitted patches for compatibility with your system.
HP Patch/iX Reference HP Patch/iX Main Menu Adding (SUBSYS) Products Select Adding (SUBSYS) Products if you have a SUBSYS product tape that was shipped with your PowerPatch tape. SUBSYS products are subsystem products that you specifically order. This option can be used only when a new product is being added to the system at the same time a PowerPatch is applied. Applying SUBSYS products to your system is known as the Add-On process.
HP Patch/iX Reference HP Patch/iX Main Menu HP Patch/iX purges all files found in the groups as selected. These files are typically left over from a previous product installation and can cause either HP Patch/iX or AUTOINST to fail. This is recommended for the Add-on activity. • Restore files from reactive patch tape. HP Patch/iX restores the patch files from the mounted tape and copies them into the patchxl.sys group. Unmark this item if you have downloaded Reactive patch files to the PATCHXL.SYS group.
HP Patch/iX Reference HP Patch/iX Main Menu displays only if you have completed the Select Activities portion of the patch process. • Available SUBSYS products. If you are performing an add-on task, we recommend that you view the list of available products to confirm that you received what you ordered. The list of patches displayed in the View Patches screen varies depending upon the filter selected for the viewer. The default View Patches filter displays Installed Patches.
HP Patch/iX Reference HP Patch/iX Main Menu Qualified (2) Displays all patches that qualify for the system. Disqualified (3) Displays all patches that failed to qualify for the system. Difference (4) Displays the difference in the list of qualified patches between the two most recent qualifications. Vetoed (5) Displays all patches marked for veto from the default qualification. They are marked with V. Forced (6) Displays all patches marked for force from the default qualification.
HP Patch/iX Reference HP Patch/iX Main Menu Patch Recommendation—indicates when a patch should be installed. An alphabetic code displays in the Flags column of the Qualify Patches screen. The code is expanded in the Detailed Summary view. The Summary Detailed View Patch Recommendation Codes are: A FOS patch that is recommended for installation on all systems. B FOS patch that is recommended for installation if appropriate. There are special circumstances that are described in the General Release text.
HP Patch/iX Reference HP Patch/iX Main Menu View (4) — Product Number Displays a list of products that are affected by the selected patch. View (5) — Known Problem Report (KPR) Numbers Displays a list of the KPR (Known Problem Report) numbers that are referenced by the patch. This is provided as cross reference information to determine what known problems are fixed by this patch. These are also known as Service Request (SR) numbers. View (6) — Patch Supersedes Displays the history of this patch.
HP Patch/iX Reference Creating a Patch Tape or Stage Tape Creating a Patch Tape or Stage Tape On the HP Patch/iX Main menu, the Create [Stage] [Tape] option displays if HP Stage/iX is initialized. If HP Stage/iX is not initialized or, if one or more qualified patches is not stageable, the Create [Tape] option displays.
HP Patch/iX Reference Exiting HP Patch/iX Exiting HP Patch/iX To exit HP Patch/iX: 1. Use [F8] to return to the HP Patch/iX Main menu. 2. From the HP Patch/iX Main menu, highlight the fifth option, Exit HP Patch/iX and press [Return]. The messages displays: Patch Management completed successfully. **EXITING HP PATCH/iX** The MPE/iX prompt displays. 3. If you downloaded reactive patches from the HP SupportLine web site, respond to the prompt to remove those files from your disk.
G HP Stage/iX Reference This Appendix describes how to use HP Stage/iX in command mode and how to use STAGEISL. Most HP Stage/iX functions can be performed through the command line interface in addition to the HP Patch/iX interface. Normally, to create, fill, and validate staging areas, use HP Patch/iX which performs these functions automatically in addition to qualifying patches. Then to use and permanently apply the files in a staging area, execute HP Stage/iX commands from the STAGEMAN prompt.
HP Stage/iX Reference HP Stage/iX Concepts HP Stage/iX Concepts Your operating system normally resides in what HP Stage/iX calls the Base. The Base is the set of files laid down by the last UPDATE or INSTALL, and RESTORE from tape. The “base location” or “natural location” is where a file officially resides (for example, NL.PUB.SYS). HP Stage/iX creates, fills, and validates staging areas. A staging area is an HFS directory: /SYS/hpstage/stage_name.
HP Stage/iX Reference HP Stage/iX Concepts a staging area, HP Stage/iX: 1. Moves the staging area files back to the staging area. 2. Moves the Base archive files back to their Base location. 3. Boots the system using the staging area files. Refer to Figure G-2. for more information. Figure G-2. Backing Out Patch Changes Phase I Create Staging patches OS in Base Phase II Activate Staging Introduce patches archive Move staging area files to Base location. Reboot starts system with stage_1 changes.
HP Stage/iX Reference HP Stage/iX Concepts Figure G-3. Permanently Applying Patch Changes Phase I Create Staging patches OS in Base Phase II Activate Staging archive Move staging area files to Base location. Reboot starts system with stage_1 changes. OPTION Make changes permanent: COMMIT changes to Introduce patches Copy Base files that are replaced with changed files to the Base file archive empty stage_1 Create staging area. Contains copies of changed OS files stage_1 Staging area empty.
HP Stage/iX Reference HP Stage/iX Concepts Figure G-4. Creating Another Staging Area, from the Base Location Phase I Create Staging patches OS in Base Option Create another Staging Area: Introduce patches patch_set_ Introduce patches OS in Base patch_set_ Introduce additional Sample Activate stage_2 Additional patches only stage_1 Create staging area. Contains copies of changed OS files stage_1 Stage_1 files in stage location stage_2 Create staging area.
HP Stage/iX Reference HP Stage/iX Concepts Figure G-5. Creating Another Staging Area from an Existing Staging Area Phase I Create Staging patch_set_ Introduce patches OS in Base stage_1 Create staging area. Contains copy of changed OS file that result from Phase II Activate Staging archive Move staging area files to Base location. Reboot starts system with stage_1 changes.
HP Stage/iX Reference Using HP Stage/iX Using HP Stage/iX This section describes typical HP Stage/iX processes and definitions. • Installing and Initializing HP Stage/iX • Staging Area Handling • Using STAGEISL • Uninstalling HP Stage/iX • Using HP Stage/iX Help Installing and Initializing HP Stage/iX HP Stage/iX is automatically installed as part of your Fundamental Operating System (FOS) when you update to the latest version of MPE/iX. It is used in conjunction with HP Patch/iX.
HP Stage/iX Reference Using HP Stage/iX Typically, this is done using HP Patch/iX. The following HP Stage/iX command line option is available, but should be used by experienced users only! a. To start HP Stage/iX, type at the MPE/iX prompt: :STAGEMAN b. Create an empty staging area. STAGEMAN> CREATE stagename Where stagename is the name for the new staging area. c. Change to expert mode. STAGEMAN> EXPERT ON d. Fill the staging area. Refer to the Expert Mode commands stagefile and deletefile. e.
HP Stage/iX Reference Using HP Stage/iX a. Specify base to change the booting location to the Base. b. Reboot your system. This activates the staging area. 9. Commit a staging area to the Base location. a. Boot from the staging area to permanently apply it to the Base system software. b. Execute the COMMIT command. STAGEMAN> COMMIT The current staging area becomes the new Base. The staging area itself is removed. Using STAGEISL STAGEISL contains a subset of the HP Stage/iX functions.
HP Stage/iX Reference Using HP Stage/iX :STAGEMAN 2. At the STAGEMAN prompt, type: STAGEMAN> UNINSTALL All files, directories, and data structures created by HP Stage/iX are deleted. 3. Respond to the prompt. Are you sure? Using Help Help is available for all HP Stage/iX Normal mode, Expert mode, and STAGEISL commands. The Help information that displays is specific to the tool and mode. To use HP Stage/iX Help: • For a list of commands, type HELP at the STAGEMAN prompt.
HP Stage/iX Reference Using HP Stage/iX • After staging area was created, but prior to applying (SET and boot) a staging area. • After applying (SET and boot) from a staging area. 2. Identify the staging area condition at the time of the disaster. • Staging area created but not booted. • Staging area created and applied (SET and boot) from the staging area. 3. Perform a reinstall of your current operating system.
HP Stage/iX Reference HP Stage/iX Commands HP Stage/iX Commands This section lists and describes all the HP Stage/iX and STAGEISL commands. • HP Stage/iX is executed from the MPE/iX prompt. • STAGEISL is executed from the ISL prompt. STAGEISL is limited to the following commands: status same capabilities as HP Stage/iX list nofiles/files and nopatches/patches option not available set same capabilities as HP Stage/iX help keyword option not available.
HP Stage/iX Reference HP Stage/iX Commands Table G-1.
HP Stage/iX Reference HP Stage/iX Commands Table G-1. HP Stage/iX Commands by Interface Activity HP Patch/iX Menu/Option Display Current Staging Area STAGEISL Commands HP Stage/iX Commands STAGEISL STATUS STAGEMAN STATUS Displays staging area used in last boot. Commit To Current Stage Displays staging area currently booted and running. STAGEMAN COMMIT HP Stage/iX Command Summary Table G-2. lists the Staging Area management commands, general operation commands, and STAGEMAN Expert Mode commands.
HP Stage/iX Reference HP Stage/iX Commands Table G-3. lists the general operating commands. Table G-3. General Operation Commands Required Command (Abbrev) Capabilities Description HELP (H) SM | OP Get help for an STAGEMAN command. ERRMSG SM | OP Display cause/action text for a STAGEMAN error. EXIT (E) (none) Exit STAGEMAN. LISTREDO (none) Display the STAGEMAN command history. REDO (none) Re-execute (and edit) a previous STAGEMAN command.
HP Stage/iX Reference HP Stage/iX Commands Syntax CHANGE [STAGE=]stage_name [[;NAME=]new_name] [[;DESC=]quoted_string] Parameters [STAGE=]stage_name (required) The current name of the HP Stage/iX staging area. This must be a valid staging area name for a pre-existing staging area. The staging area cannot be in use, or designated for use on the next boot (see the SET command). Staging area names are case sensitive. “STAGE1” is not equivalent to “stage1” or “Stage1”.
HP Stage/iX Reference HP Stage/iX Commands Parameters (none) Example STAGEMAN will ignore both of these comment lines: STAGEMAN> COMMENT this is just a comment STAGEMAN> # this is another comment COMMIT The HP Stage/iX subsystem allows system managers to activate patched system software without overwriting the pre-existing system software environment.
HP Stage/iX Reference HP Stage/iX Commands Example To “commit” to the current staging area (“stage1” in the example below): STAGEMAN> STATUS Currently active staging area: stage1 Staging area to be used for next boot: stage1. STAGEMAN> COMMIT ;NOCONFIRM COMPLETE The COMPLETE command marks a staging area as complete. When a staging area is marked as complete, it tells STAGEMAN that all files that should belong to it have successfully been staged, and the staging area is now a complete unit.
HP Stage/iX Reference HP Stage/iX Commands Syntax CREATE [STAGE=]stage_name [[;DESC=]quoted_string] Parameters [STAGE=]stage_name (required) This parameter specifies the name to be given to the newly created staging area. The staging area name can be up 16 characters in length. The staging area name must be a valid MPE/iX directory name. For this reason, the staging area name cannot contain a “/” character. It may contain letters (upper or lower case), numbers, and the special characters “_”, “-”, and “.
HP Stage/iX Reference HP Stage/iX Commands The ;CONFIRM or ;NOCONFIRM option specifies whether or not the DELETE command will prompt you for confirmation. If you specify ;NOCONFIRM, then STAGEMAN will NOT prompt for confirmation. The default is ;CONFIRM. Example STAGEMAN> DEL OLD_STAGING_AREA;NOCONFIRM DELETEFILE (DELETEF,DF) The DELETEFILE command removes a file from a staging area.
HP Stage/iX Reference HP Stage/iX Commands additional information on the MPE/iX DISKUSE command, use the MPE/iX help facility. This can be done with STAGEMAN by typing: :HELP DISKUSE The DISKUSE command can be abbreviated DU. Syntax DISKUSE [STAGE=]stage_name Parameters [STAGE=]stage_name (required) This parameter designates which staging area will be displayed. The staging area name must be a valid HP Stage/iX staging area name.
HP Stage/iX Reference HP Stage/iX Commands DUPLICATE The DUPLICATE command copies one staging area to another. All files from the original staging area are copied, and the resulting staging area — except for the name — is an exact duplicate of the original. The EXCEPT parameter allows an indirect file to be passed that contains a list of files in the original staging areas that should not be duplicated. The DUPLICATE command can be abbreviated DUP.
HP Stage/iX Reference HP Stage/iX Commands STAGEMAN> errmsg 1170 MESSAGE: The HP Stage/iX Globals file is temporarily in use by another process. Can't complete command. (STAGEMAN 1170) CAUSE: STAGEMAN could not open the HP Stage/iX Globals file because it was held open exclusively by another process at the time. The other process was most likely STAGEMAN (or HP Patch/iX) being run in another job or session (STAGEMAN always opens the Globals file for exclusive access).
HP Stage/iX Reference HP Stage/iX Commands The following commands are allowed in expert mode only: Table G-5. Commands Only Available in Expert Mode Command Description STAGEFILE (SF) Put a file in a staging area. DELETEFILE (DF) Delete a file from a staging area. CHANGEFILE (CF) Change the attributes of a staged file. SETDEFAULT (SETD) Set the default attributes for a particular file. SHOWDEFAULT (SHOWD) Display the default attributes for a file.
HP Stage/iX Reference HP Stage/iX Commands Syntax EXPORT [STAGE=]stage_name [;{NOPACK}] {TAPE } {PACK } Parameters [STAGE=]stage_name (required) The name of the staging area to be exported. [;{NOPACK}] (optional) {TAPE } {PACK } Default: NOPACK The export option to be used. Three options are currently supported: NOPACK—All files belonging to the staging area are simply copied to the Export directory (/SYS/hpstage/export/).
HP Stage/iX Reference HP Stage/iX Commands The name of the command. This parameter is optional. If you omit the command name, STAGEMAN displays information about all commands. (keyword) : (optional) Default: DESC Defines which part of the help text you would like printed. DESC — Show the command’s description and syntax. PARMS — Show the command’s parameters only. EXAMPLE- — Show command usage examples only. ALL — Show all help text related to the command.
HP Stage/iX Reference HP Stage/iX Commands HP Stage/iX should some file, directory, or data structure become corrupted. It will not delete any staging areas or affect the contents of any staging area in any way. The INITIALIZE command can be abbreviated INIT. Syntax INITIALIZE Parameters (none) Example :STAGEMAN STAGEMAN A.00.00, (C) Hewlett-Packard Co., 1995. All Rights Reserved. *Warning: The HP Stage/iX environment is not initialized.
HP Stage/iX Reference HP Stage/iX Commands are accepted when listing staging areas. By default the LIST command will display the name of the staging area, the last modified date, a flag indicating whether or not the staging area is valid or invalid (see VALIDATE/INVALIDATE commands), and the brief description associated with the staging area.
HP Stage/iX Reference HP Stage/iX Commands includes any patches installed in the Base, as well as in the staging area.
HP Stage/iX Reference HP Stage/iX Commands NOTE: Staging area names are case sensitive, so the above command will display staging areas that start with “st”, but not staging areas that start with “ST”. LISTREDO The LISTREDO command is used to display the command history stack. The output order is from the least to the most recent command with absolute command reference numbers preceding each command.
HP Stage/iX Reference HP Stage/iX Commands LIST option is NOLIST. To see the output of a command executed from a command file, either type OPTION LIST prior to executing (via USE) that command file, or put an explicit OPTION LIST command inside the command file. The CONTINUE option specifies whether or not STAGEMAN will continue to process commands within a command file if an error is encountered. The default value for the continue option is NOCONTINUE.
HP Stage/iX Reference HP Stage/iX Commands updates the system's HP Stage/iX Globals file with all appropriate information about the staging area. Syntax RECOVER [STAGE=]stage_name Parameters [STAGE=]stage_name (required) The name of the existing staging area to be recovered. Example To recover staging area “stage_1”: STAGEMAN> RECOVER stage_1 REDO The REDO command is identical in function to the MPE/iX redo command. It allows a command in the command history stack to be edited and re-executed.
HP Stage/iX Reference HP Stage/iX Commands same staging area as was used on the previous reboot, unless the system manager changes the default by using the SET command. You must specify the name of a validated HP Stage/iX staging area to the SET command. The SET command will accept the string “BASE” to indicate that the system should be booted from the BASE on the next reboot. The SET command cannot be abbreviated.
HP Stage/iX Reference HP Stage/iX Commands [;VAL={BASIC} ] {EXISTENCE} {CHECKSUM} [;VALINFO="validation_info"] [;LIFTYPE={NONE} ] {BOOT} {IPL} {DATA} {AUTOF} [;OWNER="owner_name"] [;FILEGROUP={LDEV1} ] {SLT} {OTHER} Parameters [FILE=]file_name (Required) The fully qualified filename for the file which the subsequent defaults should be set.
HP Stage/iX Reference HP Stage/iX Commands Default: WARN (see also SETDEFAULT) If an error occurs while processing a file, the error_action for that file will dictate what the start code will do. WARN — start will continue. An error message will be printed. IGNORE — start will continue, no error message will be printed.
HP Stage/iX Reference HP Stage/iX Commands SLT—This is the normal file group for most of the files found on the System Load Tape. Files in this group are switched ahead of files in the OTHER group. OTHER—This is the default file group. Files here are switched after the system is almost completely up and running. Example STAGEMAN$ SETDEFAULT START.MPEXL.SYS;disk=C;disp=R;val=E;onerr=W STAGEMAN$ SETD USERFILE.PUB.
HP Stage/iX Reference HP Stage/iX Commands [;DISK={NONE}] {CONTIG} {LDEV1} [;DISP={IGNORE}] {REPLACE} {ADD} {DELETE} [;ONERR={IGNORE}] {WARN} [;VAL={BASIC}] {EXISTENCE} {CHECKSUM} [;VALINFO="validation_info"] [;LIFTYPE={NONE} ] {BOOT} {IPL} {DATA} {AUTOF} [;OWNER="owner_name"] [;{MOVE}] {COPY} Parameters [STAGE=]stage_name (Required) The name of the HP Stage/iX staging area. This must exist, cannot be in use, and cannot be the staging area designated for use on the next boot.
HP Stage/iX Reference HP Stage/iX Commands Default: NONE (see also SETDEFAULT) CONTIG — Implies that the file must be on LDEV1 and that the file requires contiguous disk space. (MOST RESTRICTIVE) LDEV1 — Implies that the file must be on LDEV1. NONE — Implies that there are no disk space restriction on the file. Files with no restrictions can be placed anywhere within the MPEXL_SYSTEM_VOLUME_SET.
HP Stage/iX Reference HP Stage/iX Commands The VALINFO parameter is not currently supported. [;LIFTYPE=lif_type] (Optional) Values: NONE, BOOT, IPL, DATA, AUTOF Default: NONE (see also SETDEFAULT) Determines whether or not the file belongs in the system LIF Directory, and if so, what file type it should be placed in the directory as. [;OWNER="owner_name"] (Optional) Default: “MANAGER.SYS” The owner name that should be assigned to the staged file.
HP Stage/iX Reference HP Stage/iX Commands Next boot will be with: stage_1 UNINSTALL The UNINSTALL command COMPLETELY uninstalls the HP Stage/iX facility. If you type UNINSTALL, then ALL HP Stage/iX staging areas will be deleted. In addition ALL HP Stage/iX directories, files, and data structures will be deleted. The HP Stage/iX facility will be considered uninitalized after doing an UNINSTALL command.
HP Stage/iX Reference HP Stage/iX Commands Syntax USE [FILENAME=]filename Parameters [FILENAME=]filename (required) Any valid MPE/iX file for which you have READ access. Example To use the USE command to process an ASCII file in STAGEMAN, enter: STAGEMAN> VALIDATE VALIDATE (VAL) An HP Stage/iX staging area must be validated before it can be used. The VALIDATE command is used to validate a staging area.
HP Stage/iX Reference HP Stage/iX Commands file basis (see the STAGEFILE command). The default value for this parameter is ;NOOVERRIDE.
H Error Messages and Warnings This Appendix provides suggested resolutions to error messages that can occur when running AUTOINST, HPINSTAL, Patch/iX, or Stage/iX. Some of the messages are common to both HPINSTAL and AUTOINST. In these cases, the installation program is referred to generically as “the installer.
Error Messages and Warnings Common Modification Process Errors Common Modification Process Errors Throughout the activities described in Chapter 5 , “Modifying Your System,” several types of messages may display. Below is a description of some of the more common error and warning messages and a general description of the appropriate response to those messages. Disk Space Messages At different stages, AUTOINST searches for required amounts of non-contiguous and contiguous disk space. In the section “3.
Error Messages and Warnings Common Modification Process Errors To recover from the above two messages, ensure that you have sufficient disk space before proceeding with your modification task. UPDATE Disk Space Message The following message is generated by the UPDATE utility. UPDATE was not able to put all the files on disk. UPDATE skips non-critical files and exists. WARNING: UPDATE tried to find 60,000 sectors of contiguous disk space on LDEV1 for its work, but it could only find nnnnnnn sectors.
Error Messages and Warnings Common Modification Process Errors If this message appears on the console where AUTOINST is invoked, use CHGROUP to change to the PUB.SYS group, use ALTGROUP to add the BA, IA, PM, MR, DS, and PH capabilities to the INSTALL group. Use CHGGROUP to return to your original group. Zero Installation Files When installation files are streamed, progress messages display. The message may indicate zero installation files.
Error Messages and Warnings HP Patch/iX and Stage/iX Error Handling HP Patch/iX and Stage/iX Error Handling Stage/iX errors that occur during Patch/iX display through the Patch/iX error handling system. For information on Stage/iX errors that occur outside of Patch/iX, refer to “Stage/iX Messages (STAGEMAN).” There are three error levels in the HP Patch/iX utility. • Warning Level—warnings are given if a condition exists that could hinder your ability to complete the task.
Error Messages and Warnings HP Patch/iX and Stage/iX Error Handling HP Patch/iX exits gracefully and prints important error information to the terminal window. If HP Patch/iX experienced an installation tools library error it also prints the error message associated with that error. Below are sample messages: ************** INTERNAL ERROR MESSAGE ******************* HP Patch/iX experienced the following library status RL STATUS.SUBSYS = INSTALLATION TOOLS LIBRARY RL STATUS.
Error Messages and Warnings HP Patch/iX and Stage/iX Error Handling complete it displays a prompt window that describes how to continue. 5. Press the [RETURN] key to continue. HP Patch/iX displays the Main Menu, with the recommended menu action highlighted. HP Patch/iX allows you control over how to continue. You can choose to continue from where you left off or select any of the previous menu items to start at an earlier step. 6.
Error Messages and Warnings HP Patch/iX and Stage/iX Error Handling • INTLOG.INSTALL.SYS — A log file of most of the activity carried out by calls to the common installation tools library from the Create Tape screen. Whereas AUTOLOG contains the output of stand alone utilities, INTLOG contains the output from the common installation tools library itself. This file can be checked for error messages that occur during the Create Tape screen of HP Patch/iX.
Error Messages and Warnings SETUP Error Messages (SETERR) SETUP Error Messages (SETERR) 1 Message You must be logged on to MANAGER.SYS,INSTALL to set up for HPINSTAL. SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #1) Cause You have either logged on as someone other than MANAGER.SYS, or you are not in the INSTALL group. Action • Log on as MANAGER.SYS,INSTALL and execute SETUP.INSTUTIL. • Contact the Response Center if further assistance is required.
Error Messages and Warnings SETUP Error Messages (SETERR) Response Center. 4 Message You must execute SETINIT to complete the SETUP. SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #4) Cause An old accounting structure was encountered when executing SETUP. SETUP cannot process successfully, therefore, you will be required to execute an additional script, SETINIT. SETINIT will purge the old accounting structure, then automatically execute SETUP.
Error Messages and Warnings SETUP Error Messages (SETERR) • If GRPNAMES still has an invalid format, contact the Response Center for further assistance. 7 Message GRPNAMES has an invalid format. This account has no VOLUME ID. SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #7) Cause The GRPNAMES data file on the compact disk has an invalid format.
Error Messages and Warnings SETUP Error Messages (SETERR) • Contact the Response Center if further assistance is required. 10 Message Unable to successfully bind to the group group.account . SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #10) Cause SETUP was unable to create a group that was listed in the GRPNAMES data file. Action • Type the following command to ensure that the group does not exist. :LISTGROUP GROUP.
Error Messages and Warnings SETUP Error Messages (SETERR) INSTALL.SYS group. SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #12) Cause SETUP was unable to purge a file from the INSTALL.SYS group prior to copying a newer version of the file from the CD vuuff .SYS group. Action • Perform the following command to determine if the file is busy: :LISTF FILENAME .INSTALL.SYS,2 • Determine the process accessing the file. • Kill the process. • Execute SETINIT.
Error Messages and Warnings SETUP Error Messages (SETERR) • Execute SETUP.INSTUTIL. • If you have no other compact disks, contact the Response Center for further assistance. 15 Message volname is not a valid volume set name. (“_” must precede the VUF and vol ID). (SETERR #15) Cause The disk from which SETUP.INSTUTIL is executing is not a valid Hewlett-Packard MPE-formatted compact disk. Action • VSCLOSE the volume set containing SETUP.INSTUTIL. • Purgegroup INSTUTIL.
Error Messages and Warnings SETUP Error Messages (SETERR) attempting to VSCLOSE an open compact disk. Action • The associated CI error message is displayed. The disk can only be closed if no files on the disk are being accessed. If the disk cannot be closed, determine the files being used, kill any processes accessing the disk, then execute SETINIT again. • Contact the Response Center if further assistance is required. 18 Message This disk is in an invalid state for this process.
Error Messages and Warnings SETUP Error Messages (SETERR) 21 Message You must execute SETUP.INSTUTIL prior to executing SETINIT. (SETERR #21) Cause SETINIT uses a secondary CI script called OLDACCTS to establish MPE release-dependent variables. This script is built by SETUP.INSTUTIL, and is deleted by SETUP.INSTUTIL upon normal termination. Therefore, SETUP.INSTUTIL must be executed first, and it must fail prior to SETINIT. Action • Ensure that the CD containing the INSTUTIL.SYS group is online.
Error Messages and Warnings SETUP Error Messages (SETERR) Action • Do a LISTEQ to determine the file equations that have been set. • Reset the files for which you no longer need file equations. (If no file equations are needed, do a RESET @.) • Execute SETINIT.INSTALL. • Contact the Response Center if further assistance is required. 24 Message Unable to set file equation for the file PEXL.INSTALL. SETUP will terminate. Follow the instructions in your installation manual to continue.
Error Messages and Warnings SETUP Error Messages (SETERR) SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #26) Cause SETUP.INSTUTIL failed when attempting to set a file equation for OLDACCTS. Action • Do a LISTEQ to determine which file equations have been set. • Reset the files for which you no longer need file equations. (If no file equations are needed, do a RESET @.) • Contact the Response Center if further assistance is required.
Error Messages and Warnings SETUP Error Messages (SETERR) SETUP will terminate. Follow the instructions in your installation manual to continue. (SETERR #29) Cause A INITCIVR existed from a previous execution of SETUP.INSTUTIL, and it could not be purged. Action • Ensure that the file is not busy. • Ensure that the file is not a temporary file. • Purge INITCIVR. • Execute SETUP.INSTUTIL. • Contact the Response Center if further assistance is required.
Error Messages and Warnings SETUP Error Messages (SETERR) instructions in your installation manual to continue. (SETERR #32) Cause A SETINIT existed from a previous execution of SETUP.INSTUTIL, and it could not be purged. Action • Ensure that the file is not busy. • Ensure that the file is not a temporary file. • Purge SETINIT. • Execute SETUP.INSTUTIL. • Contact the Response Center if further assistance is required. 33 Message Failed to copy initialization file SETUPYES. SETUP will terminate.
Error Messages and Warnings SETUP Error Messages (SETERR) 35 Message 35 Not used 36 Message Unable to purge the account mpe_hpslt. (SETERR #36) Cause SETINIT failed when attempting to purge the account mpe_hpslt. Action • Ensure that no files are open in the account. • Purge the account from your terminal. • Execute SETINIT.INSTALL. • Contact the Response Center if further assistance is required. 37 Message Unable to purge the account mpe_hpupdate.
Error Messages and Warnings SETUP Error Messages (SETERR) from your terminal. If the script fails again, the CI variable table may be full. Delete user variables by entering DELETEVAR @ . • Execute SETINIT.INSTAL again.
Error Messages and Warnings Installer Error Messages (INSTERR) Installer Error Messages (INSTERR) 1 Message Installation can only be performed by MANAGER.SYS,INSTALL. (INSTERR #1) Cause The installer verifies the user during start up using the WHO intrinsic. If the returned values for user name, local group, and account name do not match MANAGER, INSTALL and SYS, respectively, the installer terminates with this error. Action Log on as follows, and run the installer again: :HELLO MANAGER.
Error Messages and Warnings Installer Error Messages (INSTERR) restored. To continue with the installation, consult the customer installation procedures. (INSTERR #4) Cause The JCW STOREJCW was nonzero after the installer executed the following STORE command to restore the FOS tape: :RUN STORE.PUB;info= RESTORE & FOS;!IFHPIBFS.PUB;CREATE;SHOW=OFFLINE Action • Ensure that a device with class LP is included in your configuration.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center if further assistance is required. 5 Message The SUBSYS tape has not been successfully restored. To continue with the installation, consult the customer installation procedures. (INSTERR #5) Cause The JCW STOREJCW was nonzero after the installer executed the following STORE command to restore the SUBSYS or ADDON tape: :RUN STORE.PUB;INFO= RESTORE & SUBSYS;@.@.
Error Messages and Warnings Installer Error Messages (INSTERR) encountered a DDS firmware problem. Contact your HP representative for further assistance. • Take appropriate corrective measures, and run the installer again. • Contact the Response Center if further assistance is required. 6 Message 6 Not used 7 Message The files from the POWERPATCH tape were not successfully restored. To continue with the installation, consult the customer installation procedures.
Error Messages and Warnings Installer Error Messages (INSTERR) • Corrupt files - Manually RESTORE the corrupt files from the PowerPatch tape. If successful, this indicates there were transmission errors. • Take appropriate corrective measures, and run the installer again. • Contact the Response Center if further assistance is required. 8 Message Add-on cannot be done without an ADD-ON tape.
Error Messages and Warnings Installer Error Messages (INSTERR) 12 Message This installer is supported on Release 2.2 or later ONLY. (INSTERR #12) Cause Occurs in AUTOINST only: the MPE version is pre-2.2, or AUTOINST cannot retrieve the current version number. Action • Ensure your system is on MPE release 2.2 (A.41.00) or later. Pre-2.2 or non-released versions of 2.2 are unsupported. • Ensure you have updated with the factory SLT if you are performing an UPDATE. • Ensure you have restored A@.
Error Messages and Warnings Installer Error Messages (INSTERR) • LDEV 1 disk space could also be an issue since the AIFs create files on LDEV 1. Ensure that there was 60000 sectors of contiguous disk space reserved on LDEV 1. • Take appropriate corrective measures, and run the installer again. • Contact the Response Center if further assistance is required. 15 Message FINDJCW failure on STOREJCW.
Error Messages and Warnings Installer Error Messages (INSTERR) Action • Attempt the file command manually outside of the installer. • Take appropriate corrective measures, and run the installer again. • Contact the Response Center if further assistance is required. 18 Message The installer failed to copy SL.PUB.SYS. (INSTERR #18) Cause The installer failed to execute the command COPY SL.PUB.SYS, SL to obtain a local copy of the SL. Action • Ensure the file equation FILE SL.PUB.
Error Messages and Warnings Installer Error Messages (INSTERR) Restore the files from tape at the end of the installation. • Check if target file XL.INSTALL.SYS already exists. Purge the XL.INSTALL.SYS file. • Take appropriate corrective measures, and run the installer again. • Contact the Response Center if further assistance is required. 20 Message The installer failed to copy NL.PUB.SYS. (INSTERR #20) Cause The installer failed to execute the command COPY NL.PUB.
Error Messages and Warnings Installer Error Messages (INSTERR) 22 Message Invalid job encountered. Job processing: ifilename (INSTERR #22) Cause An invalid JOB CARD has been detected. An invalid STREAM,# command has been detected. Action If the USL, UXL, UNL groups were not purged prior to starting the installation, purge them and restart the installation procedures. Type: :LISTF I???????.USL.SYS. • If the file INDIRECT exists, purge it.
Error Messages and Warnings Installer Error Messages (INSTERR) permanent and transient space allocation assignments to 100% on all system volumes except LDEV 1. — Store user files to tape and them purge them. Restore the files from tape at the end of the installation. • Take appropriate corrective measures, and run the installer again. • Contact the Response Center if further assistance is required. 26 Message Unable to recover installation file processing.
Error Messages and Warnings Installer Error Messages (INSTERR) #28) Cause The installer was unable to find information on a streamed job. Either SUPACCT or one of the installation jobs failed to produce a spool file for the installer to find or the installer lost track of the JOB number. The location number specified in the error message is a location number within the installer code and should be included with all communications with the Response Center.
Error Messages and Warnings Installer Error Messages (INSTERR) file is missing or the indirect store file, TMPSTR02.INSTALL.SYS, is missing or is empty. Action • Type LISTF TMPSTR02.INSTALL.SYS,2 to verify it exists and is not empty. • Type LISTF AUTOPSTR.INSTALL.SYS to verify it exists. If not, restore AUTOPSTR from the SUBSYS tape. • Contact the Response Center if further assistance is required. 31 Message Installation can only be performed from the CONSOLE.
Error Messages and Warnings Installer Error Messages (INSTERR) is accessed immediately. This error can occur if the file is purged, or its name is somehow corrupted. Action • Run the installer again to re-create the file. • Contact the Response Center if further assistance is required. 34 35 Message The installer failed while trying to sort filename (INSTERR #34) Cause An intrinsic failed while attempting to sort filename.
Error Messages and Warnings Installer Error Messages (INSTERR) 37 Message The installer could not read filename file. (INSTERR #37) Cause This error occurs while trying to read the AUTOGEN, AUTODEP, or AUTORLNK files. The files may be corrupted. Action • For AUTOINST: • Restore AUTOGEN, AUTODEP, and AUTORLNK from the correct PowerPatch tape. • Run the installer again. • Contact the Response Center if further assistance is required. • For HPINSTAL: Restart HPINSTAL.
Error Messages and Warnings Installer Error Messages (INSTERR) :SEGMENTER -SL SL.INSTALL.SYS -LISTSL Press [[CTRL]] [[Y]] to stop listing all the SL segments. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 41 Message AUTOGEN, AUTODEP VUF MISMATCH (INSTERR #41) Cause AUTOGEN and AUTODEP from the PowerPatch tape should have the same file VUF. This error can only be caused if two different PowerPatch tapes are in use.
Error Messages and Warnings Installer Error Messages (INSTERR) CREATEPROCESS error or use the displayed error. • Check the returned CREATEPROCESS error in the MPE/iX Intrinsics Reference Manual. • Perform corrective action for SOMPATCH. • Ensure group for SOMPATCH has sufficient capabilities. (need CAP=PH). • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 44 Message Error occurred while executing SOMPATCH commands.
Error Messages and Warnings Installer Error Messages (INSTERR) The installer invoked SYSGEN to build the CSLT. SYSGEN encountered an error and the installer trapped on the error condition. Action • Print file AUTOLOG.INSTALL.SYS to view detailed error from SYSGEN. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 47 Message Error executing SAINT commands while building START IMAGE.
Error Messages and Warnings Installer Error Messages (INSTERR) installer again. • Contact the Response Center if further assistance is required. 50 Message An error occurred in translating the SL. (INSTERR #50). Cause OCT encountered an error in translating the SL. The installer invoked OCT to translate newly installed segments in the staged system SL. OCT encountered an error and the installer trapped on the error condition. Action • Print the file AUTOLOG.INSTALL.SYS to check OCT error.
Error Messages and Warnings Installer Error Messages (INSTERR) specific error. • Check for additional errors in file SLOUTPUT.OUT.HPSPOOL. • Take appropriate corrective measures and run the installer again. • If you are patching an MPE/iX system release 4.0 or later, ensure that the version of AUTOINST you are running is D.00.05 or later. If the AUTOINST version is earlier than D.00.05, restore A@.F@ from the PowerPatch tape, and run AUTOINST again.
Error Messages and Warnings Installer Error Messages (INSTERR) intrinsic patcher ABLDINTX.INSTALL.SYS failed. Action • FILE Command Table is possibly full. • Check if any further file commands can be entered with the FILE command. • RESET any USER file equations. • Take appropriate corrective measures and run the installer again. The installer will reissue any needed file equations. • Contact the Response Center if further assistance is required. 57 Message Error trying to RUN ABLDINTX.INSTALL.SYS.
Error Messages and Warnings Installer Error Messages (INSTERR) • Ensure group for BUILDINT has sufficient capabilities. (need CAP=PH). • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 59 Message Setting file equation SPLINTR failed. (INSTERR #59) Cause Setting the SPLINTR file equation required by the CM intrinsic builder/patcher BUILDINT failed. Action • FILE Command Table is possibly full.
Error Messages and Warnings Installer Error Messages (INSTERR) possible detailed error from either BUILDINT or ABLDINTX. • Take appropriate corrective measures and run the installer again. If the error cannot be corrected, please document all messages prior to the error. Save the file AUTOLOG.INSTALL.SYS, and then report the problem to the Response Center for assistance. 62 63 64 65 66 Appendix H Message Resetting file equation SYSINTR failed.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause The installer attempted to purge an old SYSINTR file before beginning to patch NM intrinsics. Action • Examine file for accessors other than the installer. • If file is being accessed, free up file. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 67 Message Purge of SPLINTR.INSTALL.SYS failed.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center if further assistance is required. 69 Message Copy of SPLINTR.PUB.SYS to SPLINTR.INSTALL.SYS failed. (INSTERR #69) Cause The installer was attempting to copy SPLINTR.PUB.SYS to SPLINTR.INSTALL.SYS. Action • Examine file SPLINTR.INSTALL.SYS for accessors other than the installer. • If file is being accessed, free up file. • Check for free disk space to copy file, and if needed free up disk space.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause The installer was attempting to purge an old work nl, TEMPNL.INSTALL used when patching the OS SOM. Action • Examine file TEMPNL.INSTALL.SYS for accessors. • If accessors, free up file. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 72 Message Copy of NL.INSTALL to TEMPNL failed when patching the OS SOM.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center if further assistance is required. 74 Message CLEANXL of TEMPNL failed in patching the OS SOM. (INSTERR #74) Cause The installer called the link editor to perform a CLEANXL on TEMPNL.INSTALL in preparation for replacing the OS SOM with a patched OS SOM. Action • Print file AUTOLOG.INSTALL.SYS to view detailed error from link editor.
Error Messages and Warnings Installer Error Messages (INSTERR) 77 Message COPYXL from TEMPNL to NL.INSTALL.SYS failed when patching the OS SOM. (INSTERR #77) Cause The installer called the link editor to perform a COPYXL of all non-OS SOMs from TEMPNL.INSTALL to NL.INSTALL. Action • Print file AUTOLOG.INSTALL.SYS to view detailed error from link editor. • Check error message cause and action in the HP Link Editor/iX Reference Manual. • Take appropriate corrective measures and run the installer again.
Error Messages and Warnings Installer Error Messages (INSTERR) required. 80 Message Build of the RELINKER patch file RELINKFL.INSTALL.SYS failed. (INSTERR #80) Cause The installer was attempting to build the file RELINKFL.INSTALL.SYS, to then write the link editor relink procedure commands into the file. Action • If old RELINKFL.INSTALL.SYS exists, purge it. • Check for enough free disk space to build files.
Error Messages and Warnings Installer Error Messages (INSTERR) • If file is being accessed, free up file. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 83 Message Build of the RELINKER patch file INDIRREL.INSTALL.SYS failed. (INSTERR #83) Cause The installer was attempting to build the file INDIRREL.INSTALL.SYS, to then write the link editor relink procedure names into the file. Action • If old INDIRREL.INSTALL.
Error Messages and Warnings Installer Error Messages (INSTERR) the RELINKER PROCEDURE. (INSTERR #85) Cause RELINKING of Procedures by the link editor failed. Action • This error represents a problem with an internal link editor error while relinking procedures in the OS SOM. • If this error is produced, please document all messages prior to the error. Save the file AUTOLOG.INSTALL.SYS, and the file INTLOG.INSTALL.SYS, and then report the problem to the Response Center for assistance.
Error Messages and Warnings Installer Error Messages (INSTERR) command to determine which USER file equations can be RESET. RESET any USER file equations. Take appropriate corrective measures and run the installer again. The installer will reissue any needed file equations. • HPPATH variable is a non-standard path. Issue the following command: :SETVAR HPPATH “!HPPATH,PUB,PUB.SYS,ARPA.SYS” Take appropriate corrective measures and run the installer again.
Error Messages and Warnings Installer Error Messages (INSTERR) required. 91 Message Error while issuing file equation for the SL library. (INSTERR #91) Cause The installer attempted to issue the file equation: :FILE SL.PUB.SYS=SL (SL being in the local group INSTALL.SYS), prior to calling SYSGEN to create the CSLT. Action • FILE Command Table is possibly full. Do a LISTEQ command to determine which USER file equations can be RESET. RESET any USER file equations.
Error Messages and Warnings Installer Error Messages (INSTERR) • Take appropriate corrective measures and run the installer again. The installer will reissue any needed file equations. • Contact the Response Center if further assistance is required. 94 95 Message The current INSTALL file is blank or nil. (INSTERR #94) Cause An internal installer variable is corrupt. This error represents a serious problem with an internal variable passed to the module that updates the staged system libraries.
Error Messages and Warnings Installer Error Messages (INSTERR) installer again. • Contact the Response Center if further assistance is required. 98 Message The installer encountered an error while monitoring a streamed job. Error status returned by JobInfo intrinsic: status . (INSTERR #98) Cause A call to the JOBINFO intrinsic failed while the installer was attempting to obtain the number of a given job name or to obtain the state of a job. The job in question should be the last job streamed.
Error Messages and Warnings Installer Error Messages (INSTERR) • Restart the installer. 100 Message The patched program and data files were not successfully stored. To continue with the installation, refer to the installation manual. (INSTERR #100) Cause The JCW STOREJCW contained an error value after execution of AUTOPSTR.INSTALL.SYS to store the patch program and data files.
Error Messages and Warnings Installer Error Messages (INSTERR) required. 103 Message The installer failed to build AUTOLOG.INSTALL. (INSTERR #103) Cause The installer failed to build the file AUTOLOG.INSTALL. Action • Check for free disk space to build file. There are two methods for obtaining additional disk space: — Use the ALTERVOL command in VOLUTIL to set the permanent and transient space allocation assignments to 100% on all system volumes except LDEV 1.
Error Messages and Warnings Installer Error Messages (INSTERR) installation/update/patch process the CLEANXL was issued. • Check error message cause and action in the HP Link Editor/iX Reference Manual. • Take appropriate corrective measures and run the installer again. 106 Message Error trying to RUN AUTOLED. (INSTERR #106) Could not create AUTOLED process. Createprocess error: status Cause The CREATEPROCESS intrinsic returned an error status when attempting to execute LINKEDIT.PUB.SYS or AUTOLED.
Error Messages and Warnings Installer Error Messages (INSTERR) Action • The CREATEPROCESS intrinsic returned an error status when attempting to execute SAINT.MPEXL.SYS. • Check the returned CREATEPROCESS error in the MPE/iX Intrinsics Reference Manual. • Print file AUTOLOG.INSTALL.SYS to check for further errors. • Perform corrective action for SAINT. • Ensure ASAINTFL.INSTALL.SYS exists. • Ensure group for SAINT has sufficient capabilities. (need CAP=PH).
Error Messages and Warnings Installer Error Messages (INSTERR) • If using a PRODLIST file, modify the incorrect product number. 111 Message Unable to build file filename. (INSTERR #111) Cause CUSTOM was unable to build the specified file. This may be due to an existing file of the same name, or a lack of disk space to build the file. Action • Ensure that no file of that name exists.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center for further assistance if required. 116 Message Error occurred while reading the PRODINFO file. (INSTERR #116) Cause CUSTOM failed while trying to access the appropriate PRODINFO. Action • Initialize the system by using the SETUP initialization process. • Run HPINSTAL. • Contact the Response Center if further assistance is required. 119 Message 117-118 Not used Message Unable to open file filename.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause A call to the intrinsic FGETINFO failed from CUSTOM. Action • Ensure that the specified file exists. • Document any error message text prior to the error. • Run HPINSTAL again. • Contact the Response Center for further assistance if required. 126 Message Unable to expand file filename. (INSTERR #126) Cause CUSTOM failed while copying an existing file for expansion.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause Patch Selector failed while trying to access the appropriate FILEINFO. Action • Document all messages prior to the error. • Note names of all F@.INSTALL.SYS files. • Save the HPSWINFO.PUB.SYS, PATCHAUD.INSTALL.SYS, and INSTERRS.INSTALL.SYS files. • Report the problem to the Response Center for assistance. # 132 Message Failed to convert the CHECKSUM from FILEINFO file. (INSTERR #131) Cause A call to the intrinsic DBINARY failed.
Error Messages and Warnings Installer Error Messages (INSTERR) space on the System Volume set to stage the files for building a customized SLT. You do not have that space available. Please consult the Error messages section for alternatives to resolve this problem. (INSTERR #134) Cause The installer verifies it has enough disk space for the creating the CSLT by building a 787,000 sector file. If the build fails, the installer prints this message and terminates.
Error Messages and Warnings Installer Error Messages (INSTERR) Response Center for assistance. 137 Message BA-BI count mismatch. (INSTERR #137) Cause Error while processing Binary patches. Action Save PATCHAUD.INSTALL.SYS and contact the Response Center for assistance. 138 Message 138 Not used 139 Message The installer could not find filename in DLGINFO. (INSTERR #139) Cause The installer could not find filename in the DLGINFO file. This is typically caused by not purging the UNL.SYS, USL.
Error Messages and Warnings Installer Error Messages (INSTERR) to 100% on all system volumes except LDEV 1. — Store user files to tape and them purge them. Restore the files from tape at the end of the installation. — Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 143 144 Message Rename of filename1 to filename2 failed.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause The installer was attempting to build a workfile: ASYSGNFL, and failed. Action • Check and correct errors reported to terminal screen. • Check for free disk space on system. There are two methods for obtaining additional disk space: • Use the ALTERVOL command in VOLUTIL to set the permanent and transient space allocation assignments to 100% on all system volumes except LDEV 1. — Store user files to tape and them purge them.
Error Messages and Warnings Installer Error Messages (INSTERR) PowerPatch tape again. If the error occurs again, contact the Response Center for further assistance. 149 150 151 Message Patch Selector internal error. (INSTERR #149) Cause Patch Selector encountered an internal error which is displayed prior to this message. Action Note all displayed error messages. Save the files, PATCHAUD and INSTERRS. Contact the Response Center for assistance.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause AUTOGEN and AUTORLNK from the PowerPatch tape should have the same file vuuff. This error can only be caused if two different PowerPatch tapes are in use. Action For AUTOINST: • Restore A@,F@ from the correct PowerPatch. • Take appropriate corrective measures and run AUTOINST to start installation again. • Contact the Response Center if further assistance is required.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center if further assistance is required. 159 Message File command error occurred for filename file. (INSTERR #159) Cause Setting a file equation required by Patch selector failed. Action • FILE Command Table is possibly full. • Check if any further file commands can be entered with the file command. • RESET any USER file equations. • Take appropriate corrective measures and run the installer again.
Error Messages and Warnings Installer Error Messages (INSTERR) intrinsic and based on the status value displayed, take corrective action. • Run the installer again. • Contact the Response Center if further assistance is required. 163 164 Message OSSOM replacement patch VUF is < or = the current OS id (INSTERR #163) Cause There is an OSSOM replacement patch on the PowerPatch tape, which has a vuuff that is older than the OSSOM on the system being patched.
Error Messages and Warnings Installer Error Messages (INSTERR) with the keyword exactly as it appears on the certificate. • Ensure that the products listed in PRODLIST.PUB.SYS matches the product list received from Hewlett-Packard. • Run HPINSTAL again. • Contact the Response Center if further assistance is required.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center if further assistance is required. 172 Message Purge of Relinker option file failed. (INSTERR #172) Cause Purge of a file with relinker options failed. Action • Document any error message text prior to the error. • Examine file for other accessors. • If file is being accessed, free up file. • Take appropriate corrective measures and run installer again.
Error Messages and Warnings Installer Error Messages (INSTERR) installer again. • Contact the Response Center if further assistance is required. 175 Message The installer encountered a corrupt ASYSUTIL file. (INSTERR #175) Cause The installer encountered a corrupt ASYSUTIL file while reading the file. Action • If running the installer with a non-PowerPatch option, then purge the file and run the installer again.
Error Messages and Warnings Installer Error Messages (INSTERR) required. 178 Message The installer encountered an error purging a library file. (INSTERR #178) Cause The installer was attempting to purge a library SOM after adding or copying it to a library. Action • Document any error message text prior to the error. • Purge the file and run the installer again. • Contact the Response Center if further assistance is required. 179 Message Error encountered setting SYSGEN file equation.
Error Messages and Warnings Installer Error Messages (INSTERR) 181 Message Error encountered setting CATALOG file equation. (INSTERR #181) Cause The installer attempted to issue the file equation: :FILE CATALOG.PUB.SYS=CATALOG.INSTALL.SYS Action • Document any error message text prior to the error. • FILE Command Table is possibly full. • Do a LISTEQ command to determine which USER file equations can be RESET. • RESET any USER file equations.
Error Messages and Warnings Installer Error Messages (INSTERR) (INSTERR #184) Cause The installer invoked SYSGEN to make a modification to a SYSGEN internal file. Action • Print file AUTOLOG.INSTALL.SYS to view detailed error from SYSGEN. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 185 Message The installer encountered an error purging TARGVUF.
Error Messages and Warnings Installer Error Messages (INSTERR) corrupt. Action • Document any error message text prior to the error. • Use SHOWVAR MPE_TARG_VUF to check the status of the variable. • Print the INITCIVR.INSTALL. There should be a line with a SETVAR command for the indicated variable. If the line does exist, execute INITCIVR and run HPINSTAL again. • If INITCIVR.INSTALL.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact the Response Center if further assistance is required. 190 Message The installer encountered an error building the file SYSGLOG. (INSTERR #190) Cause The installer was attempting to build the file SYSGLOG. Action • Document any error message text prior to the error. • If old SYSGLOG exists, purge it. • Check for enough free disk space to build files.
Error Messages and Warnings Installer Error Messages (INSTERR) • Examine file for accessors other than the installer. • If file is being accessed, free up file. • Take appropriate corrective measures and run the installer again. • Contact the Response Center if further assistance is required. 193 Message Error encountered while redirecting input to SYSPROGF. (INSTERR #193) Cause The installer attempted to issue the command: :LISTF MISCP.@.
Error Messages and Warnings Installer Error Messages (INSTERR) 199 Message 199 Not used 200 Message Failed to retrieve the OS build ID. (INSTERR #200) Cause The installer failed to access the MPE/iX Operating System and Release IDs of your system. Action • Log on as MANAGER.SYS,INSTALL to your MPE/iX environment. • Rerun the tool. • Contact the Response Center if further assistance is required.
Error Messages and Warnings Installer Error Messages (INSTERR) • Once the system is up, log on to the system as MANAGER.SYS,INSTALL, start the spooler, and enable the streams device. • Run HPINSTAL again. • Contact the Response Center if further assistance is required. 203 Message The file TARGVUF.PUB.SYS is missing. (INSTERR #203) Cause This file is installed on a system as a result of performing an UPDATE with the CSLT/STORE tape created during Phase 1 of HPINSTAL.
Error Messages and Warnings Installer Error Messages (INSTERR) 205 Message Failed to copy filename to the local group. (INSTERR #205) Cause HPCICOMMAND intrinsic failed on the COPY command. Action • Document any error message text that occurred prior to the error. • If the target file exists, purge it. • Run HPINSTAL again. • Contact the Response Center if further assistance is required. 206 Message Failed to decrypt filename. (INSTERR #206) Cause CUSTOM failed to decrypt an encrypted file.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause An attempt to set the HPINSTAL environment variables though the command script, INITCIVR.INSTALL.SYS, failed. Action • Check the CI error message preceding the INSTERR #209 message and take appropriate corrective action. • If INITCIVR.INSTALL.SYS does not exist, VSCLOSE both CD-ROM volumes and follow the setup procedures in the HPINSTAL manual. 210 Message HPVOLINFO error while attempting to access volume name .
Error Messages and Warnings Installer Error Messages (INSTERR) • Take appropriate corrective measures and run HPINSTAL again. HPINSTAL will reissue any required file equations. • Contact the Response Center if further assistance is required. 213 Message HPINSTAL failed to copy over filename from CD-ROM (INSTERR #213) Cause The installer attempted to copy filename from CD-ROM and was unable to do so. Action • See if filename already exists in the local group/account. If so purge it.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause An attempt to set a file equation for the link editor help and catalog files through the HPICICOMMAND intrinsic failed. The FILE Command Table is possibly full. Action • Check if any further FILE commands can be entered with the FILE command. • RESET any user file equations. • Take appropriate corrective measures and run HPINSTAL again. HPINSTAL will reissue any required file equations.
Error Messages and Warnings Installer Error Messages (INSTERR) required. 221 Message Encountered an error while retrieving the CI variable, variable name. (INSTERR #221) Cause Could not retrieve the value of the indicated CI variable. Action • Use SHOWVAR variable name to check the status of the variable. • Print the INITCIVR.INSTALL. There should be a line with a SETVAR command for the indicated variable. If the line does exist, execute INITCIVR and run HPINSTAL again. • If INITCIVR.INSTALL.
Error Messages and Warnings Installer Error Messages (INSTERR) • VSCLOSE both CD-ROM volumes and follow the setup procedures in the HPINSTAL manual. Run HPINSTAL from the start. • Save all messages on the screen and check the messages in the bottom of AUTOLOG. Call the Response Center for further assistance. 224 225 230 Message Error reading from terminal with READX (INSTERR #224) Cause A physical I/O error occurred.
Error Messages and Warnings Installer Error Messages (INSTERR) Cause The PowerPatch tape being installed includes patches that are older than those that were included with the last PowerPatch installation. Action • Print the file HPSWINFO.PUB.SYS and refer to line 4 of the file to determine the V.U.F. of the last installed PowerPatch tape. Compare this V.U.F. to the V.U.F. on the tape label of the PowerPatch tape being installed. • The V.U.F.
Error Messages and Warnings Installer Error Messages (INSTERR) except LDEV 1. • Store user files to tape and then purge them. Restore the files from tape at the end of the installation. — Transmission errors - Clean tape heads and check for hardware errors. — Corrupt files - Manually RESTORE the corrupt files from the CSLT/STORE tape. If successful, this indicates there were transmission errors. • Take appropriate corrective measures, and run AUTOINST again.
Error Messages and Warnings Installer Error Messages (INSTERR) • Contact your Response Center if further assistance is required. 239 Message Invalid Catalog AICAT000 in the INSTALL.SYS group. The Catalog VUF could not be recovered (INSTERR #239) Cause The catalog, AICAT000, is missing its VUF. Action • If you are installing a PowerPatch tape, RESTORE AUTOINST and AICAT000 from the PowerPatch tape.
Error Messages and Warnings Installer Error Messages (INSTERR) the command is returning an error. • If LIMIT can be set manually, run AUTOINST again. • Contact your Response Center if further assistance is required. 243 Message The Installer could not close filename. (INSTERR #243) Cause The Installer failed while trying to close the file filename. Action • Make sure the file exists. • If the file exists, examine it for accessors other than AUTOINST. • If the file is being accessed, free up the file.
Error Messages and Warnings Installer Error Messages (INSTERR) • Ensure that the file is in the appropriate format. (Each record must contain the name of an MPE file that contains the library replacement, and a unique entry point into the library component. The file name and the entry point must be separated by a comma). • Run the installer again. • Contact the Response Center for further assistance. 253 Message The installer failed to open !1. No components have been added to the !2 library.
Error Messages and Warnings Installer Error Messages (INSTERR) BASE-VERSION. You cannot continue with installation (INSTERR #255) 256 Cause The system OS version is newer than the CS OS version. HPINSTAL allows CSLT creation under this condition only for remote systems. Action Use HPINSTAL to create CSLT for local systems with only newer versions OS CDs. Message HPCIGETVAR failed in create CSLT (INSTERR #256) Cause The installer issued the HPCIGETVAR intrinsic and failed.
Error Messages and Warnings Warning Messages (INSTWARN) Warning Messages (INSTWARN) 1 2 3 4 5 6 7 Appendix H Message Warning -- This program cannot install the products listed below. (INSTWARN #1) Action The SUBSYS tape has non-AUTOINSTallable products. Install all of these products after updating with the CSLT created by the installer. Message Expected a YES or NO. (INSTWARN #2) Action The input to the prompt is invalid. Respond YES or NO at the prompt.
Error Messages and Warnings Warning Messages (INSTWARN) 8 Action No corrective action is required. Message Unable to close CD-ROM volume name (INSTWARN #8) Cause VSCLOSE failed on a mounted CD-ROM volume. Action • From the console, manually VSCLOSE and dismount the volume. If the drive is a SCSI drive, run AVRSCSI to dismount the volume. • Follow the instructions on the screen to continue with the installation.
Error Messages and Warnings Warning Messages (INSTWARN) 21 Message Keyword incorrect. Retype your keyword. (INSTWARN #21) Cause An invalid keyword was entered. Action • Ensure the key entered matches the keyword certificate received from Hewlett-Packard. • Ensure that the product list entered is correct. • Run HPINSTAL again from the beginning. • Contact the Response Center for further assistance if required. 22 Message Exactly fourteen (14) characters must be entered.
Error Messages and Warnings SLTCOPY Messages SLTCOPY Messages Message Invalid file name. Cause The file name that you entered does not meet the MPE syntax requirements for file names. Note that you cannot use HFS syntax (such as /SYS/PUB/tapefile) for file names supplied to SLTCOPY. Action Enter a different file name that meets MPE syntax requirements. Message Undefined system file. Cause File name entered is undefined to the system.
Error Messages and Warnings SLTCOPY Messages Appendix H Message Failed to read tape! No records processed. Cause Error occurred while reading the master tape. This message only occurs after the tape drive has been open for reading. Action Check the tape drive cable connections, its configuration, and whether or not the availability of the tape drive changed after the tape reply. When the error is found, restart SLTCOPY from the beginning.
Error Messages and Warnings SLTCOPY Messages opportunity to enter a different file name. 432 Cause After you entered the disk file name for Option 1 (Copy tape to disk), the test closing of the file failed. The reason it failed is shown in a File Information Display. Action You will see the main menu after receiving this message. You can then choose to exit the program (so you can adjust your capabilities), or choose Option 1 again and specify a different file that will not cause the same error.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Stage/iX Messages (STAGEMAN) This section lists the Stage/iX Error Messages, cause and action. 1001 Message Unable to execute USE file “name”. (STAGEMAN 1001) 1002 1003 1004 1005 1006 1007 Appendix H Cause STAGEMAN was unable to open and/or execute the file that the user specified for the USE command. Action Check the file system error message associated with the command, and take the appropriate action.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1008 Message Illegal value. (STAGEMAN 1008) Cause An unexpected and inappropriate value was supplied for this parameter. Re-enter the command with an appropriate value for the parameter. Do a HELP on the command to determine appropriate values if necessary. 1009 Message 1009 not used. 1010 Message Transaction aborted per user request. (STAGEMAN 1010) Cause The user specified “No” to a confirmation of a command.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1015 1016 1017 1018 1019 Appendix H Message Output from SORT/iX failed. SORT status: Subsys: value, Info: value (STAGEMAN 1015) Cause STAGEMAN received an error from the HPSORTOUTPUT intrinsic of the SORT/iX subsystem. Action Determine why the HPSORTOUTPUT intrinsic failed. Contact your Hewlett-Packard Response Center for assistance. Message No staging areas exist.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1020 1021 1022 1023 1024 436 Action. Determine why the open of the contents file failed. Contact your Hewlett-Packard Response Center for assistance. Message “/” not allowed in staging area names. (STAGEMAN 1020) Cause A slash (“/”) was found in the staging area parameter. STAGEMAN uses the staging area name for building a directory under /SYS/hpstage/ (/SYS/hpstage/stage_name).
Error Messages and Warnings Stage/iX Messages (STAGEMAN) was done to that staging area). Since critical changes have been made to the HP Stage/iX environment based on the structure of that staging area, STAGEMAN does not allow any changes to the staging area to avoid the possibility of corrupting the environment and/or the system.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) command. (STAGEMAN 1029) 1030 1031 1032 1033 438 Cause STAGEMAN found a directory under /SYS/hpstage/ of the same name that was used for the staging area parameter. Since STAGEMAN uses the staging area name for building a directory under /SYS/hpstage/ (/SYS/hpstage/stage_name), it fails on this condition to avoid corrupting the user's environment.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) to store a staging area to tape. This error will always be reported if a REPLY ,0 was done to the tape request. 1034 1035 1036 1037 Appendix H Action Determine why the STORE command failed, fix the problem, and redo the command. Message Can't use reserved word “IMPORT” for staging area name. (STAGEMAN 1034) Cause The user specified the string “IMPORT” for the staging area parameter.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1038 1039 1040 1041 1042 1043 440 Action If a staging area is or should be active, contact you Hewlett-Packard Response Center for assistance. Message The Stage/iX environment is in an inconsistent state.Can't commit. (STAGEMAN 1038) Cause An error occurred during the last bootup, so that the state of the HP Stage/iX environment - as well as the integrity of the active staging area - is in question.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1044 1045 1046 1047 1048 Appendix H Cause STAGEMAN got an error while attempting to run the unpack utility, MOVER.PRVXL.TELESUP, to unpack the staging area files. Action Determine the cause of the MOVER error. Contact your Hewlett-Packard Response Center for assistance. Message Failed to move to the staging area directory for “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) used as a staging area name. To avoid confusion, the check for “BASE_ARCHIVE” is not case sensitive. 1049 1050 1051 1052 1053 Action Choose another staging area name. You may you the string “BASE_ARCHIVE” within a staging area name (e.g., “Base_Archive_1”). Message Failed to copy the contents file for staging area “name” to the Export directory.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1054 Message Found illegal onerr parameter. (STAGEMAN 1054) Cause A value was passed to a command's ONERR parameter that STAGEMAN does not understand. This indicates a problem with the STAGEMAN utility. If you encounter this error, report it to your Hewlett-Packard Response Center. 1055 1056 1057 1058 1059 1060 Appendix H Message Found illegal validate type parameter.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1061 Cause The filename supplied to the parameter had a trailing “/”, meaning that it is really a directory. STAGEMAN cannot stage directories, so the operation (command) failed. Action Re-execute the command without the trailing “/”. Message Found illegal filegroup parameter. (STAGEMAN 1061) Cause A value was passed to a command's FILEGROUP type parameter that STAGEMAN does not understand. This indicates a problem with the STAGEMAN utility.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1065 1066 1067 1068 Message Warning: Staged file as “name” (convertedfrom a POSIX to an MPE name). (STAGEMAN 1065) Cause The user specified the filename in POSIX (HFS) syntax when the filename is expressible in MPE syntax (an example is expressing NL.PUB.SYS as /SYS/PUB/NL). Whenever possible, STAGEMAN converts HFS filenames to MPE syntax to avoid the possibility of the same file being staged under two different names (for example, NL.PUB.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) STAGEFILE for more information). 1070 1071 1072 1073 1074 446 Message Staging area “name” failed validation due to previous errors. (STAGEMAN 1070) Cause STAGEMAN found one or more specific errors while attempting to validate the files in a staging area. Action Refer to the errors that were displayed previous to this error for information on which files had problems. Message File “name” is missing from the staging area.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) the discrepancy. An easy way to fix this problem is to re-stage the original file (do an Expert Mode HELP on STAGEFILE for more information). 1075 1076 1077 1078 1079 1080 Appendix H Message The staging area is empty. (STAGEMAN 1075) Cause STAGEMAN found no known files in the staging area. Action If the staging area was expected to be empty at validation time then this warning can be ignored.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) parameter does not exist. 1081 1082 1083 1084 1085 448 Action Check your spelling on the indirect file name. Message Unable to open indirect file “name”. (STAGEMAN 1081) Cause The ;EXCEPT parameter was used on a DUPLICATE command, and STAGEMAN received a file system error from an HPFOPEN intrinsic call to open the indirect file. Action Determine why the HPFOPEN intrinsic call failed, correct the problem, and re-execute the command.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) preceded this one to help determine the cause of the problem. 1086 1087 1088 1089 1090 1091 Appendix H Message Failed to delete bad staging area “name”. (STAGEMAN 1086) Cause The DUPLICATE operation failed, and to remove the possibility of leaving behind a corrupt target (TO) staging area, STAGEMAN attempted to delete the target staging area. However, an error occurred during the delete operation.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) processing the STAGEDEF file. (STAGEMAN 1091) Cause STAGEMAN could not process the file STAGEDEF.PUB.SYS at startup time. STAGEDEF is used by STAGEMAN to get default attributes of known system files. This is a warning because it will not interfere with most STAGEMAN commands or operations. However, if files need to be staged (for instance, if Patch/iX is creating staging areas), this is a serious error.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) normally prints after an initial IMPORT error is printed, and is therefore issued for information purposes only. 1096 1097 1098 1099 Appendix H Action Reference the IMPORT error that immediately preceded this one to help determine the cause of the problem. Message Failed to delete bad staging area “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1102 1103 1104 1105 1106 1107 452 Action Contact your Hewlett-Packard Response Center for assistance. Message 1100 and 1101 not used. Message Attempted to add more than the maximum number of staging areas allowed. (Max = ) (STAGEMAN 1102) Cause The maximum number of staging areas supported by the HP Stage/iX facility has been reached, so STAGEMAN cannot add another staging area.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) (STAGEMAN 1107) 1108 1109 1110 1111 1112 Appendix H Cause STAGEMAN found an unexpected file error action value for the file (the error action should be WARN or IGNORE). This indicates a problem with the HP Stage/iX facility, and should be reported to Hewlett-Packard. Action Contact you Hewlett-Packard Response Center for assistance. Message Failed to open file “name” in the staging area.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1115 1125 1126 1127 1131 1132 454 Message Failed to find the staging area in the Globals file. (STAGEMAN 1115) Cause STAGEMAN failed to find an entry for the staging area in the HP Stage/iX Globals file when it expected to find one. This indicates a problem with the HP Stage/iX facility, and should be reported to Hewlett-Packard. Action Contact you Hewlett-Packard Response Center for assistance.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) process). 1133 1134 Message Failed to purge file “name” after staging it. CIERROR = value (STAGEMAN 1133) Cause STAGEMAN received a Command Interpreter (CI) error in attempting to purge a file after it was staged. Action Determine why the PURGE command failed, then purge the file manually. There is no need to re-execute the command. However, if this failure occurred during a run of Patch/iX, the Patch/iX process may need to be restarted.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1139 1140 1141 1142 1143 456 Cause STAGEMAN received a bad status from the HPFOPEN intrinsic while attempting to open a staged file for getting data on the file. Action Determine why the file open failed. If you can determine and fix the problem re-execute the command (or restart the Patch/iX process). Otherwise, contact your Hewlett-Packard Response Center for assistance. Message Failed in FFILEINFO call for file “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) entry for the file in the system LIF Directory so that the file is accessible from the ISL prompt). 1144 1145 1146 1147 1148 Appendix H Action Contact your Hewlett-Packard Response Center for assistance. Message File “name” has a zero EOF. Can't place in bootable file directory (LIF).
Error Messages and Warnings Stage/iX Messages (STAGEMAN) preceding this one. 1150 1160 1170 1171 458 Action Determine why the open call failed, correct the problem, then re-execute the command (or restart the Patch/iX process). Message Failed to alter the security on file “name”. FALTSEC status = value (STAGEMAN 1150) Cause STAGEMAN received a bad status from an internal routine while trying to add or remove write/purge protection security on the file.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) problem, then re-execute the command (or restart the Patch/iX process). 1172 1173 1174 1180 Appendix H Message The contents file for “name” is temporarily in use by another process. Can't complete command.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1181 1182 1183 1184 1185 1186 460 Message “name” is not currently a STAGEMAN error number. (STAGEMAN 1182) Cause STAGEMAN received a bad status from the DBINARY intrinsic call while attempting to convert the user's ERRMSG input to an integer. Action Contact your Hewlett-Packard Response Center for assistance. Message “name” is not currently a STAGEMAN error number.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) assistance. 1187 Message This file/directory must be on SYSTEM VOLUME SET must be on LDEV1 but is not (STAGEMAN 1187) Cause STAGEMAN found that the file or directory that was supposed to be on LDEV1 is not there. Action See the next error message that gets printed by STAGEMAN and take the appropriate action. Message Refer the System Software Maintenance Manual for correcting the situation.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1309 1310 1311 1312 1313 1318 462 Action None Message This command has no associated functionality. (STAGEMAN 1309) Cause The user has selected a command which should be valid, but is not internally recognized by STAGEMAN. This signifies a problem with the STAGEMAN utility. Action Report this problem to your Hewlett-Packard Response Center. Message Error in accessing message catalog.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) interactive mode. Action Execute the command in interactive mode. 1319 Message 1319 not used. 1320 Message Invalid command edit operation. (STAGEMAN 1320) Cause STAGEMAN is confused by the command edit operation attempted by the user. Action Try editing the command in another way, or re-type the command. Message 1321-1501 not used. Message The HP Stage/iX Root Directory already exists.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1507 1508 1509 1510 1511 1512 1513 464 Message Failed to create the Stage/iX Base Archive Directory. (STAGE 1507) Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to create the HFS directory for the staging area.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. 1514 Message The directory for staging area “name” is not empty. Couldn't purge. (STAGE 1514) 1515 1516 1517 1518 1519 1520 Appendix H Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) (STAGE 1520) 1521 Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to create contents file for staging area. (STAGE 1521) Cause This is an HP Stage/iX internal error which the user should not normally see. If you get this error, contact your Hewlett-Packard Response Center for assistance.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) should not normally see. 1527 1528 1529 1530 1531 1532 Appendix H Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to write contents file header for staging area. (STAGE 1527) Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1533 1534 1535 1536 1537 1540 468 Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to FREAD contents file for staging area. (STAGE 1533) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1541 1542 1543 1550 1551 1590 Appendix H Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to purge the HP Stage/iX Import Directory. (STAGE 1541) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Response Center for assistance. 1600 1601 1602 1603 1604 1605 470 Message 1591-1599 not used. Message HP Stage/iX refused to rename a file during bootup. (STAGE 1600) Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message A problem occurred switching a file during bootup.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Response Center for assistance. 1606 1607 1608 1609 1610 1611 1612 Appendix H Message Failed to write to or read from the HP Stage/iX Globals file. (STAGE 1606) Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to write to the XM post file.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) HP Stage/iX Globals file. (STAGE 1612) 1613 1614 Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Internal Error: Found an unexpected OTHERWISE case. (STAGE 1613) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1619 1620 1621 1622 Appendix H Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Internal Error: Attempted to delete an already deleted LIF Directory entry. (STAGE 1619) Cause This is an HP Stage/iX internal error which the user should not normally see. Action If you get this error, contact your Hewlett-Packard Response Center for assistance.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 474 Appendix H
Glossary A Activity A subset of steps performed for an individual task. For example, an activity would be qualifying patches using HP Patch/iX or Creating a CSLT. Activities are divided into steps. Add-on Adding purchased sub-system products to the operating system. Purchased sub-system products are also know as SUBSYS products. Modifications to already installed SUBSYS products is called an Update. AUTOINST Tool used to install, update, add-on, and apply patches to the operating system.
E Express Process for distributing PowerPatch releases. Typically an express contains a PowerPatch tape and a SUBSYS tape. Expresses are cumulative and are specific to an operating system version level. F Factory Preload Tape If the system is delivered with the ordered software factory loaded onto the internal disk, a tape containing a copy of the loaded software is supplied with the system. This tape is referred to as a factory preload tape (FPT).
Install Installing the operating system. The install variations are: new install and re-install. This process DESTROYS all existing files. INSTALL An ISL utility that replaces all files on the system disk with files from the boot tape, typically an SLT. L LDEV Logical Device. Value that points to a hardware device address. LDEV 1 is the hard disk on which the system software is located. A typical value for LDEV 1 is 1.
• Tasks are divided into Activities. • Activities are divided into Steps. R Re-Install Installing the system software over the existing system software. This process DESTROYS all existing files. If you have your files on backup, you can restore them. Do a re-install when a disk containing the MPEXL_system_volume_set is replaced. Reactive Patch A patch that is sent to you from the Hewlett-Packard Response Centers or downloaded from HPSL.
U Update Changing the current operating system version to a more recent operating system version. UPDATE An ISL utility that replaces existing operating system files with files from tape, typically a CSLT. Primarily used to replace a current version of the operating system with another version. V Veto An option when using the HP Patch/iX patch management tool. Vetoing a patch tells HP Patch/iX to not include (remove) the selected patch from the set of patches to be installed.
Index A ABORTJOB command, 109, 129, 144 account recommended passwords, 154 accounting structure create, 123, 143, 145 rebuild, 82 accounts HP defined, 61 activate staging area, 19, 127 UDC, 155 Adding (SUBSYS) Products Main menu, 94 option, 92 Adding a PowerPatch option, 92 Adding a Reactive Patch option, 92 add-on checklist, 26 Add-on with CD-ROM checklist, 39, 43 Add-on with Tape and Manage Patches checklist, 37, 39 Add-on with Tape checklist, 35 ALLBASE/4GL secure the system, 110, 130 ALLBASE/SQL secure
Index MOUNT, 78 NETCONTROL, 129, 144, 160 NEWGROUP, 79 NEWVOL, 120, 138 NMMGR, 150 NSCONTROL, 129, 144 ODE, 115 OPENQ, 137, 144 PURGE, 76, 105 PURGEGROUP, 111, 131, 160 RDCC, 150 RENAME, 154 REPORT, 111, 131 RESTORE, 89 RESTORE PowerPatch, 80 SCRATCHVOL, 120, 138 SET STAGE, 127 SETCATALOG, 111, 132 SETINIT, 80 SETUP, 80 SHOWDBE, 110, 130 SHOWJOB, 129, 144 SHOWLOGSTATUS, 129 SHUTDOWN, 112, 118, 133, 134 SLTCOPY, 88 SPOOLER, 125, 126, 127 STAGEMAN, 81, 127, 153, 164 START, 117, 119, 159 STARTDBE, 109, 130 ST
Index Detail Summary screen, 96 device class, 84, 122 device icons, 171 diagnose tool (STM), 173 diagnostic tool MAPPER, 115 directory structure rebuild, 152 disable UDC, 111, 132 disk drive requirements, 67 limitations, 67 system domain, 120 disk space contiguous, 72 conversion, 71 default, 73 error message, 73 estimating, 69 net, 69 non-contiguous, 69, 70 reserving, 76, 77 Distributing Staging Areas to Remote Systems checklist, 33 downtime planning, 62 drive CD-ROM, 67 drive status DSTAT command, 78 LONE
Index Install a New System checklist, 49 INSTALL command, 114, 136 INSTALL.
Index menus and commands, 174 shortcut keys, 177 system map, 171 N net disk space, 69 NETCONTROL command, 129, 144, 160 NetWare, 60 network addresses, 150 configuration, 150 names for interfaces, 160 planning, 60 router, 160 new system checklist, 49 NEWGROUP command, 79 NEWVOL command, 120, 138 Next Filter function key, 96 NIO system LDEV 1 usage, 67 NMCONFIG configuration changes, 118 file, 148 file recovery, 148 NMMGR utility, 148 NMMGRVER utility, 149 non-contiguous disk space, 69, 76, 77 NOSYSSTART opt
Index primary boot path, 114, 119, 137, 158 print_device, 76, 77, 78, 82, 120, 121, 125, 127, 128, 133, 137, 144 Process function key, 93, 95 process installation files, 143, 145 PRODLIST, 79 product available, 96 numbers, 85 references, 79 remote system, 86 product (SUBSYS) information file restore, 94 product list, 85 progress messages, 140 PSDCFILE, 108, 129, 161 PSIDNLD secure the system, 131 purge AXLSPACE, 76 HPINSTFL, 132 INSTALL.SYS files, 94 patch and installation files, 93 PATCHXL files, 94 USL.
Index set lockwords, 154 passwords, 154 SET command, 127 SETCATALOG command, 111, 132, 155 SETINIT command, 80 SETUP command, 80 SETVAR command, 90 SHOWDBE command, 110, 130 SHOWJOB command, 129, 144 SHOWLOGSTATUS command, 129 shutdown planning, 62 SHUTDOWN command, 118, 133 SLT, 115 SLTCOPY command, 88 special accounts customized, 61 spool files secure the system, 111, 131 SPOOLER command, 125, 126, 127 SPUINFOP file, 137, 159 SQLUTIL, 110 secure the system, 130 stage compatible patches, 99 patch checklis
Index user interfaces, 169 SYSDIAG utility, 160 SYSFILE command, 154 SYSGEN, 118, 130, 150, 154, 163 system backup, 130, 163 clock, 113 domain, 120 libraries, 87 libraries copying, 94, 123, 124 lockwords, 154 reboot, 158 reset, 118, 133, 134 restart, 158 security, 152 shutdown, 118, 133, 134 start up, 117, 119, 137 volumes, 120 system file identify, 154 System Manager activate stage area, 127 system map, 171 system volume configure, 138 T tape media checklist, 26 TAR utility, 157 terminal Patch/iX, 90 VSCL
