HP 3000 MPE/iX Release 6.0 System Software Maintenance Manual (Release C.60.00) HP 3000 MPE/iX Computer Systems Edition 4 30216-90272 E1098 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.
Introduction 13 Task Checklists 21 Planning for Your Task 51 Preparing Your System 69 Modifying Your System 99 Finishing the Process 141 Manually Installed Products 159 Configuration Tables 177 Managing Disk Space 181 Backdating Your System 191 CD-ROM Resources 227 HP Patch/iX Reference 257 HP Stage/iX Reference 271 Error Messages and Warnings 313 A 457
Sample Listing MAPPER Output 107 Sample PRODLIST File 233 Creating and Activating a Staging Area 272 Backing Out Patch Changes 273 Permanently Applying Patch Changes 274 Creating Another Staging Area, from the Base Location 275 Creating Another Staging Area from an Existing Staging Area 276
System Software Subject 12 Select Your Task Checklist 22 System Software Media Requirements 52 OS Version Requirements 54 HP Defined Special Accounts 56 NIO/CIO Systems 63 Non-Contiguous Disk Space Sectors 65 Update Tool Disk Space Default Requirements 68 Password Recommended HP Accounts 148 Password Recommended Users 148 Configname 177 Configname 178 Physical Path Values 178 Required Backdating Materials 193 Password Recommended HP Accounts 222 Password Recommended Users 223 SLTCOPY Defaults 251 Screen Fun
Preface This manual describes how to install, update, add-on purchased subsystems, or apply patches to Release 6.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 5.5: • HP 3000 MPE/iX System Software Maintenance Manual Release 5.5 This document replaces the following three manuals from release 5.0: • HP 3000 MPE/iX Installation, Update, and Add-On Manual MPE/iX Release 5.
About MPE/iX MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX.
Organization of This Manual This manual contains the following chapters and appendices: Chapter 1 , “Introduction,” provides basic concepts and describes how to use this manual. Chapter 2 , “Task Checklists,” provides checklists for performing the processes described in this manual. These are not keystroke summaries, instead the checklists list what sections in the manual you do to accomplish any system modification task.
Additional References This section contains a cross reference of the documentation of products and tools called out in this book. System Software Subject Type of Installation Power-PAdd-On, atch Power Only -Patch For the UPDATE utility, system System Startup, Configuration, x x activities, system startup and Shutdown Reference functions, and SYSGEN Manual information. For reviewing accounts, Performing System x x checking passwords, and Management Tasks security information.
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 3 system software using either CD-ROM or tape as source media and tape or stage (disk) media to apply the changes to your system. Starting with MPE/iX release 5.5, this manual has a completely new format and structure.
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 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 List of Terms List of Terms Refer to the Glossary at the end of this manual for definitions of terms used in this manual.
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 5 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 5, 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 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 and I. Modify Remote Systems PowerPatch Reactive H. Update with CD-ROM and I. Modify Remote Systems and 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: • PowerPatch patches • Reactive patches • PowerPatch and Reactive patches together NOTE Not all patches are stageable. For more information, refer to item 19 in section 3.2, “General Planning Tasks.
Task Checklists Checklist B. Manage Patches by Staging Area — 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.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 Record EXPORT option used: — 5.9 Installing a Distributed Staging Area-Required only if you are installing a staging area to a remote site. — 5.10 Setting a Staging Area 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.
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 — 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.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 • For all tasks creating an SLT, CSLT, or STORE tape, you need two or more blank 2400 foot, 1/2 inch reel tapes or 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.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 column to match the filename in the first column. Do not use the SYSFILE> RSPROG command in the SYSGEN utility to rename HP supplied MPE/iX HP 3000 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 performing the Update or Install for 6.0. For further information, see the Communicator 3000. 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 LDEV 1 Disk Minimum Capacity LDEV 1 requires a minimum capacity of 500 MBytes. As of Release 5.0, you cannot use the older HP7933 or HP7935 disk drives as LDEV 1 (the system disk). When you update to MPE/iX Release 6.0, you may still use HP7933 and HP7935 drives elsewhere on your system, but these drives do not have a large enough capacity to serve as the system disk.
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 5.0 5.5 C.60.00 Peak Net Peak Net SLT onlya 1,318,000 n/a 1,268,000 n/a 1,274.000 SLT and FOS 2,027,000 2,378,000 2,092,000 2,821,000 2,533,000 SLT, FOS, Full SUBSYS 3,226,000 3,637,000 3,170,000 3,926,000 3,489,000 a. Provided for reference only.
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.
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 14.Set up the HPINSTAL environment by invoking the SETUP script. :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.
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.0, 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? (YES/NO)>> 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 want to incorporate these patches (Y/N)? d. Remount the PowerPatch tape, as prompted; Please remount the PowerPatch tape and put it on line so that HPINSTAL can retrieve the patch files selected. e. Reply to the tape request. f. Proceed to Step 13. 13.Create the CSLT. Mount a write-enabled tape on the appropriate tape drive and reply to the tape request, as prompted.
Preparing Your System 4.6 Creating the CSLT using HPINSTAL 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 3. Type at the MPE/iX prompt. :PATCHIX The Logon screen displays. 4. Type your HP Patch/iX logon name at the prompt. The text entered in this field (25 characters, no spaces) is referenced in the Installed Patches filter of the View Patches screen. You may use this field to identify individuals from the generic manager.sys logon.
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 • 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 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. For example: Patch Qualification in Progress PowerPatch Patches: 17 Estimated Time: 15.
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.
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 • 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. • If your system prompts, Boot from primary boot path?, enter N. • When the system prompts, Boot from alternate boot path?, enter Y.
Modifying Your System 5.2 Applying the SLT 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. The install process displays an initialization message similar to: MPE/iX launch facility Install x.nn.
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 Path 8 8.0 16 16.0 52 Component Name ID CIO Adapter 8H HP-IB card 2H CIO Adapter 8H HP-IB card 2H HP-IB SCSI 4H Resetting SCSI Bus ... 52.0.0 HPC1503 (X) /HPC1520B DDS tape 52.2.0 HPA1999A CD-ROM drive 52.5.0 HPC3010M1 disc drive 52.6.0 HPC2247M1 disc drive 56 HP-PB LAN/Console 62 Processor 63 Memory (128 M bytes) Slot 1A - 32M Slot 1B - 32M Slot 5A - 32M Slot 5B - 32M Resetting the Boot Device . . . Done. RUN COMPLETED.
Modifying Your System 5.4 Starting the System 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. ISL>START NORECOVERY NOSYSSTART GROUP=configname where configname is the configuration group for your system.
Modifying Your System 5.5 Configuring the System 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. This file contains ID numbers and associated parameters for hardware devices.
Modifying Your System 5.5 Configuring the System 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. For all other systems, enter the following commands to reset the system: CTRL-B CM>RS If the system does not respond to the CTRL-B entry within ten seconds, press the reset button, key switch, or on/off switch as appropriate for your system.
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 a. Refer to Appendix H , “Error Messages and Warnings,” and Appendix C , “Managing Disk Space,” for actions. b. When you find the required disk space, run AUTOINST again. 7. Select the option that matches your task. Please choose and enter the number corresponding to the software you want to install. 1 PowerPatch 2SUBSYS (Add-On) and PowerPatch 3 FOS, SUBSYS, PowerPatch 4 FOS and SUBSYS 5 Add-On (SUBSYS only) 6 Exit Enter your choice_ 8.
Modifying Your System 5.7 Creating the CSLT Using AUTOINST 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. 12.Go to Step 13. Add-on and Update Tasks 13.Restore SUBSYS files. This step takes about 20–45 minutes. a. Mount SUBSYS tape and reply to tape requests when the following message displays: Mount the SUBSYS tape and put the tape drive online.
Modifying Your System 5.7 Creating the CSLT Using AUTOINST b. If it appears, reply to the prompt to continue processing patches. 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.7 Creating the CSLT Using AUTOINST To complete the installation, perform an Update from CSLT. 20.When the CSLT is created, dismount the CSLT, write-disable it, and label it with the 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.
Modifying Your System 5.8 Preparing a Staging Area for Remote Distribution 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. If you are performing a Manage Patch by Staging Area for only a Local system, skip sections 5.8 and 5.9, and proceed to “5.10 Setting a Staging Area.
Modifying Your System 5.9 Installing a Distributed Staging Area 5.9 Installing a Distributed Staging Area Perform the steps in this section only if you are planning to Distribute a Staging Area to a Remote system. If you are performing a Manage Patch by Staging Area for a Local system, skip this section and proceed to “5.10 Setting a Staging Area.” To install a distributed staging area on a remote system: 1.
Modifying Your System 5.9 Installing a Distributed Staging Area • Installing a Distributed Staging Area completed. Go to the next section on your checklist.
Modifying Your System 5.10 Setting a Staging Area 5.10 Setting a Staging Area In this section you set a staging area, that is, you select the staging area that the system will boot and operate from on the next reboot. This activity requires system manager capabilities. To set a staging area: 1. Log on from the console (if you are not already logged on) and start the spooler and streams device. :HELLO MANAGER.
Modifying Your System 5.11 Securing the System 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. :HELLO MANAGER.
Modifying Your System 5.11 Securing the System 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. Exit the program, at the prompt, type EXIT: Type an item number, an item key, or a command: __ g.
Modifying Your System 5.11 Securing the System :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. If you have ALLBASE/SQL already installed on your system, issue starts for each DBEnvironment before you back up the system. Refer to the ALLBASE/SQL Database Administration Guide for more information.
Modifying Your System 5.11 Securing the System 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,@.@.@-@.@.SYS;*T;DIRECTORY;SHOW or :STORE /SYS/, / - /SYS/;*T;DIRECTORY;SHOW; & ONVS=volume_set_name1, volume_set_name2, ... where volume_set_name is the name for each user volume set you want to backup. f. Dismount the tape, label as backup with date, time and system version.
Modifying Your System 5.11 Securing the System Go to Step 17. 17.Rename the COMMAND.PUB.SYS file. :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.If you are performing a Remote system task or CD-ROM task, go to Step 19. If you are performing an Add-on, Manage Patch, or Staging Area task with tape or disk on a local system, go to Step 20.
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 • 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. • If your system prompts Continue with primary boot path?, Primary Boot (y/n)?, enter N. or Boot from If your system prompts Continue with alternate boot path? or Boot from Alternate Boot (y/n)?, enter Y.
Modifying Your System 5.13 Applying the CSLT Modification 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.Confirm the date and time.
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 . :ALTACCT acctname;PASS=password Table 6-1.
Finishing the Process 6.4 Setting Passwords, Lockwords, and UDCs :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 3000 Series 991 or 995, 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 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.1552>> TUE, APR 19, 1994, 10:20:03 AM (y/n)? Y/N [TMUX_DAM] n n n n Initialize genesis completed. The system displays initialization and restore messages for 5 to 6 minutes.
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).
Finishing the Process 6.8 Restarting Selected System Functions :NETCONTROL START;NET=ROUTER1 :NSCONTROL START NOTE JFTPSTRT.ARPA.SYS is no longer part of the FTP product. It is no longer necessary to stream JFTPSTRT.ARPA.SYS. For FTP to work, you DO need to follow the instructions in Appendix A “Configuring File Transfer Protocol FTP”. 4. Start Internet Services. If you have any Internet Services configured (telnet, ftp, etc.), stream the Internet Super Daemon job. :STREAM JINETD.NET.
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 two running diagnostics daemons in order to back up their files. :SYSDIAG DUI>DIAGSYSTEM This gives the MEMLOGP.
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.
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 HP ALLBASE/4GL Installing HP ALLBASE/4GL To complete the installation of HP ALLBASE/4GL some additional steps must be performed. You must complete these installation procedures on a terminal other than the system console. You cannot run HP ALLBASE/4GL on the system console. First Time Install To complete the installation of the HP ALLBASE/4GL Developer system or the HP ALLBASE/4GL Run-Time system, perform the following steps after updating the system with the CSLT.
Manually Installed Products Installing HP ALLBASE/4GL Upgrade Existing Systems This section describes how to update HP ALLBASE/4GL systems. Before attempting an update, you must understand the following precautionary conditions. Developer System: • If you are using the HP ALLBASE/4GL Developer system, you must save your applications and system definitions usingHP4STOA before you upgrade to the new version of HP ALLBASE/4GL. Applications and system definitions will be lost if they are not saved.
Manually Installed Products Installing HP ALLBASE/4GL • Master titles Once the upgrade is complete, each of the files created with HP4STOA must be input to HP4ATOS. The applications need to be fully regenerated before they can be run. Refer to the HP ALLBASE/4GL Developer Reference Manual Volume 2 for details on HP4STOA and HP4ATOS. NOTE The following steps assume that your HP ALLBASE/4GL account is called HP4GL. If you used another name, substitute it for HP4GL in these instructions. 1.
Manually Installed Products Installing HP ALLBASE/4GL • tutorial 4. Use the following commands to create a new group and to copy any existing HP ALLBASE/4GL system files from the current S-file group to this new group. The S-file group is then purged so the updated S-files can be copied into the HP4S group. The existing S-files are saved in case you forget to save all your applications. :NEWGROUP HP4OLDS :HP4SCOPY.HP4GL.
Manually Installed Products Installing HP ALLBASE/4GL • User names and passwords • Menu item security definitions • System specifications for date and decimal number format, the currency float symbol, and the HP-UX environment specifications • Logic command synonyms and communication area synonyms • Master titles NOTE You should perform the following step before running AUTOINST.
Manually Installed Products Installing HP ALLBASE/4GL Following is an example of using VALIDATE: :ISQL isql> CONNECT TO 'DBEnvironmentName'; isql> VALIDATE ALL MODULES; isql> VALIDATE ALL PROCEDURES: Applications that use HP ALLBASE/4GL need to be regenerated using the new version of HP ALLBASE/4GL before they can be run. Contact your application developer.
Manually Installed Products Installing ALLBASE/ SQL or IMAGE/SQL Installing ALLBASE/ SQL or IMAGE/SQL This applies to IMAGE/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.1 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 HP3000. The software component on the HP3000 is MPE/iX version independent. You will receive special patch updates when new OVC/SysMgr’s HP 3000 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 The directions in this section only describes how to update an existing version of HP Predictive Support. To configure HP Predictive Support for the first time, please contact your Hewlett-Packard Customer Engineer who will do the initial configuration and provide the HP Predictive Support User’s Guide and the HP Predictive Support User’s Guide Addendum.
Manually Installed Products Java/iX Installation Instructions Java/iX Installation Instructions To install Java/iX after the update or install of MPE/iX 6.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 MPE/iX 6.0: 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 Installing Non-HP (Third Party) Software Installing Non-HP (Third Party) Software Consult the appropriate manuals for installation procedures for non-HP software products. Problems can occur if you install third-party products on your system and rename system files to run the software. Do not use the SYSFILE> RSPROG command in the SYSGEN utility to rename HP-supplied MPE/iX system files. A renamed system file can corrupt your system during an update.
B Configuration Tables Table and Table show the configuration names available for the models of the HP 3000 series. All the groups shown in Table are in the SYS account. Table B-1.
Configuration Tables Table B-1. Configname System SCSI Group HP-IB Group HP-FL (Alink) Group Model 996 CONFG995 -- ALINK995 Model 997 CONFG997 -- ALINK997 Model 9x7LX or RX CONF9x7n -- -- Model 9x8LX or RX CONFG9x8 -- -- Model 9x9KS CONFG9x9 -- -- Model 9x9KS with HP-PB I/O bus converter A3699A CONFK9x9 -- -- All HP 3000 Model 9x8LX and 9x8RX systems use only one configuration.
Configuration Tables Table B-3. Physical Path Values System DTSLINK\Phys. Path SYSLINK\Phys. Path Model 932 4.3 4.3 4.3 4.3 Model 935 4.3 4.2 4.4 4.3 EXPANDED Model 935 4.3 4.2 36.2 36.2 Model 948 4.1 4.1 4.1 4.1 Model 949 4.3 4.2 4.4 4.3 Model 950 2/4.2 2/4.2 6/4.2 6/4.2 Model 955 2/4.2 2/4.2 6/4.2 6/4.2 Model 958 4.1 4.1 4.1 4.1 Model 960 2/4.2 2/4.2 6/4.2 6/4.2 Model 980/100 2/4.2 2/4.2 6/4.2 6/4.2 Model 980/200 2/4.2 2/4.2 6/4.2 6/4.
Configuration Tables 180 Appendix B
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 D, 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. 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. Do not use the directions in this appendix to backout patches.
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 5.0 or 5.
Backdating Your System Planning Your Backdate Method 3: Using an FPT If any patches were applied to your 5.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 Enter Y to confirm restarting the system. c. 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). After some tape activity, the ISL prompt displays. d. Update with your backup CSLT.
Backdating Your System Performing the Backdate :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. Restore FOS and SUBSYS Refer to “Creating the CSLT Using AUTOINST” in Chapter 5 , “Modifying Your System,” for additional information about these steps. 1. Run AUTOINST. :RUN AUTOINST.Install.SYS 2.
Backdating Your System Performing the Backdate 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. AUTOINST creates the accounting structure. Progress messages display throughout this 5 minute process.
Backdating Your System Performing the Backdate 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. When the installation files have been streamed, you will see a message similar to the following on the system console. All product installation jobs have been streamed successfully.
Backdating Your System Performing the Backdate 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. Refer to “Applying the SLT” in Chapter 5 , “Modifying Your System,” for additional information about these steps. 1. From the console, mount the factory supplied System Load Tape (SLT) and put the tape drive online.
Backdating Your System Performing the Backdate 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. 8. Boot the system from the primary boot path. 1. Boot messages can vary, respond as appropriate 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.
Backdating Your System Performing the Backdate 2. Confirm the date and time. During the startup process, the system makes several configuration checks and may display warning messages. This is normal for system startup, and will not affect system operation. 3. Dismount the System Load Tape (SLT). Restore Configuration Files Restore your customized configuration group. This includes the configuration files: nmconfig, nminit, and hpswinfo. 1. Mount your 5.0 or 5.5 backup or STORE tape.
Backdating Your System Performing the Backdate a. Type at the prompt. :sysgeN sysgen>io io>lpath b. Record configuration and compare to the configuration listed by ODE. Refer to “Listing System Configuration” earlier in this appendix. c. Change the configuration to match the ODE listing. d. Save changes. io>HOLD io>EXIT sysgen>KEEP CONFIG purge old configuration? YES sysgen>EXIT A warning message displays regarding nmconfig. Ignore it. 3. Shutdown the system. CTRL-A =SHUTDOWN 4. Reset the system.
Backdating Your System Performing the Backdate Check Volumes Refer to “Checking Volumes” in Chapter 5 , “Modifying Your System,” for additional information about these steps. For more information on VOLUTIL commands, refer to the Volume Management Reference Manual. If necessary, use the VOLUTIL utility to add system volumes, including the system domain (MPEXL_SYSTEM_VOLUME_SET) disk drives (except LDEV1). 1. Log on, start the spooler, and streams device. :HELLO MANAGER.
Backdating Your System Performing the Backdate :ALTGROUP INSTALL; CAP=BA,IA,PM,MR,DS,PH c. Use CHGROUP to return to the INSTALL.SYS group. :CHGROUP INSTALL 4. If you receive an out of disk space message. 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 command again. 5. Select option 4 “FOS, SUBSYS” and reply to the tape request.
Backdating Your System Performing the Backdate STORE/RESTORE VERSION A.nn.nn (C) HEWLETT-PACKARD CO. b. Reply to the tape request. c. Dismount the FOS tape when the restore complete message displays. The files from the FOS tape were successfully restored. AUTOINST creates the accounting structure. Progress messages display throughout this 5 minute process. The ending message is: The accounting structure has been successfully created. 9. Respond to SUBSYS prompt.
Backdating Your System Performing the Backdate AUTOINST updates temporary copies of the System Libraries then creates the CSLT. This can take up to 2 hours. Creating the CSLT ... done Phase I of AUTOINST is now complete. Dismount and label the CSLT "AUTOINST CSLT HPVERSION %%v.uu.ff%%". Ensure that the write is now DISABLED. AUTOINST process Phase II requires exclusive access. To begin Phase II, SHUTDOWN your system, UPDATE from the CSLT, then log on as `MANAGER.
Backdating Your System Performing the Backdate 2. Shut down the system. CTRL-A =SHUTDOWN 3. Reset the system. As appropriate to your system, do either Step a or Step b: a. For HP 3000 Series 991 or 995: CTRL-B CM>SP SP>RS Enter Y to HARD BOOT the computer system. b. For all other systems: CTRL-B SP>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. 4.
Backdating Your System Performing the Backdate 7. Confirm the date and time. 8. 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. 9. Start the system. ISL>START NORECOVERY NOSYSSTART 10.Confirm the date and time. 11.Dismount the CSLT/FPT. 12.Log on, start the spooler, and streams device. :HELLO MANAGER.
Backdating Your System Performing the Backdate CM>SP SP>RS Enter Y to HARD BOOT the computer system. b. For all other systems: CTRL-B SP>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. 4. 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.
Backdating Your System Performing the Backdate with IPL? prompt, if it appears on your screen. The system boots from disk. After some activity the ISL prompt displays. 9. Start the system. ISL>START NORECOVERY NOSYSSTART 10.Confirm the date and time. 11.Dismount the CSLT/FPT. 12.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.
Backdating Your System Performing the Backdate 2. Modify or restore configuration files. a. Type at the prompt. :SYSGEN sysgen>IO io>LPATH b. Record configuration and compare to the configuration listed by ODE. c. Change the configuration to match the ODE listing. d. Save changes. io>HOLD io>EXIT sysgen>KEEP CONFIG purge old configuration? YES sysgen>EXIT A warning message displays regarding nmconfig. Ignore it. 3. Shutdown the system. CTRL-A =SHUTDOWN 4. Reset the system.
Backdating Your System Performing the Backdate Restore FOS and SUBSYS Refer to “Rerunning HPINSTAL” in Chapter 5 , “Modifying Your System,” for additional information about these steps. 1. Remount the Factory Preload Tape (FPT). 2. Invoke HPINSTAL. :HPINSTAL;INFO="RECOVERY" The following is a sample system response: MPE/iX HPINSTAL B.10.00 (c) Hewlett-Packard CO. Mount the CSLT and put the tape/DDS drive online The HP-supported software files will be restore.
Backdating Your System Performing the Backdate WARNING -- This program cannot install the products listed below. (INSTWARN #1) Record any product names that the program cannot install. 7. When the CSLT is created, dismount the CSLT, write-disable it, and label it CSLT (v.uu.ff) and include the current date. You can find the v.uu.ff on the FPT label. When HPINSTAL finishes the task you initially specified, you will see the following message: The installation is now complete.
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 Table D-2. Password Recommended HP Accounts CLL HPOPTMGT HPSPOOL RJE SYSLOG NETWARE CONV HPPL85 INDHPE SAMBA SYSMGR SOFTREP HPLANMGR HPPL87 INTSETUP SNADS TELESUP HPNCS HPPL89 ITF3000 SUPPORT WWW 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.
Backdating Your System Finishing Up :PURGE COMMAND.PUB.SYS 2. Enable UDCs. :RENAME command_name,COMMAND.PUB.SYS 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.
Backdating Your System Finishing Up SP>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 more information, refer to the HP 3000/iX Network Planning, and Configuration Guide. NOTE Use the same names for the network interfaces that were used in your configuration. • For example, if you have configured network interfaces with the names LOOP and LAN1, enter: :NETCONTROL START;NET=LOOP :NETCONTROL START;NET=LAN1 :NSCONTROL START :STREAM JFTPSTRT.ARPA.
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, load them into the CD-ROM drive, 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 approximately 10 minutes. You will see a series of messages and finally the message: SETUP IS COMPLETE You can then run SLTCOPY. 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.
CD-ROM Resources Copying Tapes for Distribution Select mode (? = help): 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>? 5. Type 3 in response to the prompt about which option you want to use: Which option do you wish to use < Enter 'E' to exit>? 3 6. SLTCOPY asks for the number of copies. Type the number of copies you are making at this time.
CD-ROM Resources Copying Tapes for Distribution Number of records 9877 Number of tape marks 135 Select mode (? = help) 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>? To copy another tape, select 3. If you are finished, type E to exit the program. You need to repeat the above procedure for each tape volume that makes up the CSLT you want to copy.
CD-ROM Resources Copying Tapes for Distribution After you enter the information, you are able to verify that it is correct. Enter file description: FILE CONTAINS TAPE 1 RELEASE 5.5 CSLT. Enter version number: 1 Description: FILE CONTAINS TAPE 1 RELEASE 5.5 CSLT. Version: 1 Correct [YES]? [RETURN] 6. You will see the following message on the terminal where you ran SLTCOPY: Reply for MASTER is needed.
CD-ROM Resources Copying Tapes for Distribution 2. Load the tape or tapes on which you want to make the copy. Be sure that the tapes you are copying to are write-enabled. Note the LDEV number or numbers of the tape drive or drives. NOTE For half-inch magnetic tapes only: When copying from a master CSLT tape to a disk file then to another tape, the copy tape must be the same length or greater than the original master tape from which the disk file was made.
CD-ROM Resources Copying Tapes for Distribution 7. 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. ?15:19/#S2/49/LDEV# FOR “COPY1” ON TAPE (NUM)? CTRL A =reply 49,7 Writing tape.
CD-ROM Resources Copying Tapes for Distribution filename2 The name of the file on the remote system. nodename The name used to specify the remote system. The following example shows how to create a remote disk file called CSLTVOL1 on a remote system called REMSYS. Only the part of the procedure that differs from the normal procedure for copying a tape into a disk file is shown. :DSLINE REMSYS :REMOTE HELLO USERNAME.ACCOUNT,GROUP :FILE CSLTVOL1=CSLTVOL1:REMSYS ...
CD-ROM Resources Copying Tapes for Distribution :FILE COPYn =COPYn:nodename;DEV=TAPE where: n number of copies. nodename name used to specify the remote system. NOTE You can only copy to multiple remote tapes if you invoke SLTCOPY with the WAITIO option. Refer to “Overriding Defaults.” The following example shows how to copy from a master CSLT on a local tape drive to a remote tape drive on a system called REMSYS.
CD-ROM Resources Copying Tapes for Distribution Overriding Defaults Two options for SLTCOPY are provided to allow additional control over the utility. The options are INFO=NOWAITIO and INFO=WAITIO. You only need to use these options if you want to override the SLTCOPY defaults. Refer to Table for SLTCOPY defaults. Table E-1. SLTCOPY Defaults No. of Copies Default Option 1 WAITIO 2-9 NOWAITIO To override the defaults, you should be very familiar with MPE/iX I/O operations.
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 (then add the devices; `.0' is appended to path identifier) io> ADEVICE LDEV=11 PATH=52.3.0 CLASS=DISC ID=HPA1999A LMGR=LOGICAL_DEVICE_MANAGER PMGR=SCSI_DISC_DM (then do the same for LDEV 12) io> ADEVICE LDEV=12 PATH=52.4.0 CLASS=DISC ID=HPA1999A LMGR=LOGICAL_DEVICE_MANAGER PMGR=SCSI_DISC_DM 6.
CD-ROM Resources Adding a CD-ROM Drive recognizes them. Example hardware configuration paths for HP-IB CD-ROM drives are shown below. Note the paths for your drives are likely to have different values, but the paths listed in your MAPPER output need to match the paths you entered with the AD command in the SYSGEN IO configurator. Type Path Component Name ID ----------------------------- -----52.3.0 CD-ROM Drive HPA1999A 52.4.0 CD-ROM Drive HPA1999A ODE>EXIT • If you are on a 4.0 or 4.
CD-ROM Resources Adding a CD-ROM Drive 2/4 CIO Channel Adapter 8H 2/4.0 HP-IB card 2H 2/4.0.0 7937 disk drive 214H 2/4.1 Console Device adapter 2/4.2 HP-IB card 2H 2/4.2.3 7978A/B mag tape 178H 6 Bus Converter 7H 6/4 CIO Channel Adapter 8H 16 PDH with AP Card 9H Identify Loop 1 (1H) complete 10H 0 3 - 0 261 2 ST LB - - 261 2 ST LB 2 0 0 0 10H 1H 1 0 0 Respond YES to the prompt. Do you want to exit this program and return to ISL? Y IOMAP Exiting. ISL> 14.
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 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. There are two types of Information windows. Pop-up Information windows close themselves out when they are completed.
HP Patch/iX Reference Using HP Patch/iX • 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 MPE/iX version 6.0. 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 lists the Staging Area management commands, general operation commands, and STAGEMAN Expert Mode commands.
HP Stage/iX Reference HP Stage/iX Commands Table G-2. Staging Area Management Commands Required Command (Abbrev) Capabilities Description RECOVER (REC) SM Recovers a staging area that is not recognized in the environment. Table lists the general operatin 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.
HP Stage/iX Reference HP Stage/iX Commands Table G-4. Expert Mode Commands Required Command (Abbrev) Capabilities Description SHOWDEFAULT (SHOWD) SM Display the default attributes for a particular file. COMPLETE (COMP) SM Mark a staging area as complete. EXPERT SM Put STAGEMAN in expert mode. CHANGE (CH) The CHANGE command will allow you to change various attributes of an HP Stage/iX staging area. Specifically, CHANGE will allow you to change: • The name of the staging area.
HP Stage/iX Reference HP Stage/iX Commands This parameter must be a quoted string if it contains any delimiter characters (like blanks, commas, semi-colons, or any other punctuation characters). The description can be any string up to 128 characters in length.
HP Stage/iX Reference HP Stage/iX Commands The COMMIT command will perform several steps. It will first prompt you for confirmation to commit to the current software environment. (The ;NOCONFIRM option can be used to suppress the confirmation prompt.) The COMMIT command makes all of the necessary changes to the system software environment so that the current system software becomes the new Base. Finally, the COMMIT command deletes the HP Stage/iX staging area.
HP Stage/iX Reference HP Stage/iX Commands CREATE (CR) The CREATE command will create an empty HP Stage/iX staging area. At the time the staging area is created, you are allowed to specify a brief description for the staging area. Staging areas are normally created by HP Patch/iX. A default description is associated with the staging area at that time, but you can change that description using the CHANGE command. When a staging area is initially created, it will be considered “invalid”.
HP Stage/iX Reference HP Stage/iX Commands SET command), then it cannot be deleted. The DELETE command will prompt you for confirmation to delete the staging area before it is deleted. You will not be prompted if the ;NOCONFIRM option is specified. It is acceptable to delete a staging area that another staging area was created from. Each staging area has all the information to function from the committed Base.
HP Stage/iX Reference HP Stage/iX Commands [FILE=]file_name (required) The name of the file to be deleted. The file name can be wildcarded. The filename in this command is case sensitive. Example STAGEMAN> DELETEFILE stage1, SYSGEN.PUB.SYS STAGEMAN> DF stage1, SYSG@ DISKUSE (DU) The DISKUSE command can be used to determine how much disk space is currently being used by an HP Stage/iX staging area.
HP Stage/iX Reference HP Stage/iX Commands Syntax DO [COMMAND=]command_id Parameters command_id: The command from the redo stack which we want to re-execute. The command may be specified by its relative or absolute order in the command line history stack, or by name (as a string), in whole or in part. The default -1 is the most recent command. This parameter is optional.
HP Stage/iX Reference HP Stage/iX Commands Example STAGEMAN> DUPLICATE stage1, stage2 ERRMSG The ERRMSG command allows you to display cause/action text related to a specific STAGEMAN error. Syntax ERRMSG [ERROR=]error_number Parameters [ERROR=]error_number (required) The error number associated with the STAGEMAN error. This number is always displayed in parenthesis immediately following the error message text.
HP Stage/iX Reference HP Stage/iX Commands Manager (SM) or System Operator (OP) capability to execute this command. Syntax EXIT Parameters (none) Example To exit from STAGEMAN, enter: STAGEMAN> EXIT EXPERT The EXPERT command is used to put STAGEMAN into expert mode. There are several STAGEMAN commands that extend the basic STAGEMAN functionality which require you to be in EXPERT mode. All expert mode commands require SM capability. The EXPERT command itself requires SM capability to execute.
HP Stage/iX Reference HP Stage/iX Commands man into expert mode if ON is specified, and normal mode if OFF is specified. Example To see what mode STAGEMAN is currently executing in STAGEMAN> EXPERT STAGEMAN is currently operating in NORMAL (non-expert) mode. To put STAGEMAN into expert mode STAGEMAN> EXPERT ON To put STAGEMAN into normal mode STAGEMAN$ EXPERT OFF EXPORT The EXPORT command prepares a staging area to be exported to another system.
HP Stage/iX Reference HP Stage/iX Commands Example STAGEMAN> EXPORT STAGE1;PACK HELP The HELP command (abbreviated H or HE) displays information about a STAGEMAN command. You must have System Manager (SM) or System Operator (OP) capability to execute this command. Syntax HELP [command_name] [{DESC }] {PARMS } {EXAMPLE} {ALL } Parameters command_name: (optional) The name of the command. This parameter is optional. If you omit the command name, STAGEMAN displays information about all commands.
HP Stage/iX Reference HP Stage/iX Commands Parameters [STAGE=]stage_name (required) The name of the staging area to be imported. [;{NOUNPACK}] (optional) {TAPE } {UNPACK } The import option. The default is NOUNPACK. Example STAGEMAN> IMPORT STAGE1;TAPE INITIALIZE (INIT) The INITIALIZE command is used to set up the various data structures and directories that the HP Stage/iX facility requires to operate. STAGEMAN always verifies that the HP Stage/iX facility is correctly initialized.
HP Stage/iX Reference HP Stage/iX Commands The INVALIDATE command can be abbreviated INVAL. Syntax INVALIDATE [STAGE=]stage_name Parameters [[STAGE=]stage_name (required) The name of the HP Stage/iX staging area to be invalidated. This must be a legal 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 This parameter specifies whether or not the LIST command will display information about specific files within a given staging area. The default value for this parameter is ;NOFILES.
HP Stage/iX Reference HP Stage/iX Commands ** FILE INFO FOR “mike1”: FILE NAME REST DISP FCODE EOF LIMIT ---------------------------------- ------ ---- ----- -----------------NL.PUB.SYS LDEV1 REPL NMPRG 114519 4& START.MPEXL.SYS CONTIG REPL 3791 & 8192 ** PATCH INFO FOR “mike2”: Patch Date and Time Description --------- ----------------- ------------------------------------------ MPEQX999 5.
HP Stage/iX Reference HP Stage/iX Commands Parameters [FILENAME=]filename (required) Any valid MPE/iX file to which you have READ and WRITE access. If the file doesn't exist, it is created. Example To enable logging and log all input and output to the file “logfilea”, enter: STAGEMAN> LOG LOGFILEA OPTION The OPTION command is used to set various STAGEMAN options. These options effect how STAGEMAN handles command files (also see the USE command).
HP Stage/iX Reference HP Stage/iX Commands [{ CONTINUE}] (optional) {NOCONTINUE} If this parameter is omitted, the value of the CONTINUE option is unchanged. Otherwise the value of the CONTINUE option is set to the value specified. Example To see what options are currently set: STAGEMAN> OPTION The following options are currently set: NOLIST, NOCONTINUE.
HP Stage/iX Reference HP Stage/iX Commands absolute order in the command line history stack, or by name (as a string). The default is -1, the most recent command. This parameter is optional.
HP Stage/iX Reference HP Stage/iX Commands There is a file, STAGEDEF.PUB.SYS, that contains all of the default values for files that make up HP software products. This file contains multiple SETDEFAULT commands. The STAGEDEF file is implicitly executed whenever STAGEMAN is run. The SETDEFAULT command can be abbreviated as SETD.
HP Stage/iX Reference HP Stage/iX Commands 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 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 Example To show all defaults: STAGEMAN$ SHOWDEFAULT To show the defaults for all files in PUB.SYS type: STAGEMAN$ SHOWD @.PUB.SYS STAGEFILE (STAGEF,SF) The STAGEFILE command is used to put a file into a staging area. The file can be anywhere initially (referred to as its pre-stage location). You are required to specify the final target filename for the file. This is the name that the file will ultimately have when the system is booted from the staging area.
HP Stage/iX Reference HP Stage/iX Commands {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. [FROM=]from_file_name (Required) The name of the file in its current (pre-staged) location. This can be expressed in either POSIX (HFS) or MPE syntax ((example: /SYS/PUB/NL and NL.PUB.SYS are equivalent). [TO=]to_file_name (Required) The final target name for the file.
HP Stage/iX Reference HP Stage/iX Commands If an error occurs while processing a file, the error_action for that file will dictate what the bootup code will do. WARN — Bootup will continue. An error message will be printed. IGNORE — Bootup will continue, no error message will be printed.
HP Stage/iX Reference HP Stage/iX Commands STATUS (ST) The STATUS command can be used to display the current status of the HP Stage/iX environment. If HP Stage/iX is initialized, then the STATUS command will give some basic information about the HP Stage/iX subsystem (including the name of the staging area that is currently in use, and the name of the staging area that is to be used on the next restart of the system).
HP Stage/iX Reference HP Stage/iX Commands Parameters [;{ CONFIRM}] (optional) {NOCONFIRM} The ;CONFIRM or ;NOCONFIRM option specifies whether or not the UNINSTALL command will prompt for confirmation. If you specify ;NOCONFIRM, then STAGEMAN will NOT prompt for confirmation. The default is ;CONFIRM. Example To uninstall HP Stage/iX: STAGEMAN> UNINSTALL This will destroy your HP Stage/iX environment. Are you sure [Y/N]? y Successfully uninstalled the HP Stage/iX environment.
HP Stage/iX Reference HP Stage/iX Commands Syntax Normal Mode: VALIDATE [[STAGE=]stage_name] Expert Mode: VALIDATE [[STAGE=]stage_name] [;NOOVERRIDE] [;OVERRIDE ] Parameters [[STAGE=]stage_name (required) The name of the HP Stage/iX staging area to be VALIDATED. This must be a legal 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.
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 !HPGROUP,PUB,PUB.SYS Take appropriate corrective measures and run the installer again. The installer will reissue any needed file equations.
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 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 Action Reenter the correct product number. 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.
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. 414 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 Message Output from SORT/iX failed. SORT status: Subsys: value, Info: value (STAGEMAN 1015) 1016 1017 1018 1019 Appendix H 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 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. Action To make changes to the staging area you must do a SET back to the Base (or another staging area), and execute the desired command(s).
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1029 Message A directory by the name of “name” already exists. Can’t command. (STAGEMAN 1029) 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) 1034 1035 Cause STAGEMAN got an error back from STORE while trying to store a staging area to tape. This error will always be reported if a REPLY ,0 was done to the tape request. 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) the system is booted from a staging area. 1038 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) then re-execute the command. 1043 Message Failed to unpack staging area “name”. CIERROR = value (STAGEMAN 1043) 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. 1044 Message Failed to move to the staging area directory for “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) building a directory under /SYS/hsptage/ (/SYS/hpstage/stage_name). Since /SYS/hpstage/base_archive is a reserved directory in the HP Stage/iX environment, “BASE_ARCHIVE” cannot be used as a staging area name. To avoid confusion, the check for “BASE_ARCHIVE” is not case sensitive. Action Choose another staging area name. You may you the string “BASE_ARCHIVE” within a staging area name (e.g., “Base_Archive_1”).
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 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. 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.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) exceeded the maximum filename length. 1060 1061 Action The file under its present name cannot be staged. The only option is to shorten the name of the file. Message Filename cannot be a directory. (STAGEMAN 1060) 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 “/”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) system bootup time, STAGEMAN enforces this when files are staged. Action 1065 Re-execute the command using the fully qualified filename. Message *Warning: Staged file as “name” (converted from a POSIX to an MPE name). (STAGEMAN 1065) 1066 1067 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).
Error Messages and Warnings Stage/iX Messages (STAGEMAN) file (meaning that the file exists as a single extent on disk), but the staged version of the file is not contiguous. Action The file must be made contiguous in the staging area. The easiest way to do this is to re-stage the file with the STAGEFILE command (do an Expert Mode HELP on STAGEFILE for more information). 1070 Message Staging area “name” failed validation due to previous errors.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) same that was originally staged. 1075 Action You can do a STAGEMAN LIST ;FILES on the staging area to determine what the attributes of the file should be, and compare this against the :LISTFILE /SYS/hpstage/stage_name/file_name,2 output to help find 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). Message The staging area is empty.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Action None 1080 Message Indirect file “name” does not exist. (STAGEMAN 1080) Cause The ;EXCEPT parameter was used on a DUPLICATE command, however the indirect file specified for the parameter does not exist. Action Check your spelling on the indirect file name. 1081 Message Unable to open indirect file “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Cause A DUPLICATE operation failed, and to remove the possibility of leaving behind a corrupt target (TO) staging area, the target staging area was deleted. This error normally prints after an initial DUPLICATE error is printed, and is therefore issued for information purposes only. Action Reference the DUPLICATE error that immediately preceded this one to help determine the cause of the problem.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1091 Cause This is a warning issued by STAGEMAN at startup time to tell the user that the environment is not initialized. This is normal the first time STAGEMAN is run on a newly installed system. Action None necessary. Do a HELP on INITIALIZE for more information. Message One or more problems were encountered while processing the STAGEDEF file. (STAGEMAN 1091) Cause STAGEMAN could not process the file STAGEDEF.PUB.SYS at startup time.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) command (do an Expert Mode HELP on COMPLETE for more information). 1095 Message Import failed. Deleted incomplete staging area “name”. (STAGEMAN 1095) Cause An IMPORT operation failed, and to remove the possibility of leaving behind a corrupt target (TO) staging area, the target staging area was deleted. This error normally prints after an initial IMPORT error is printed, and is therefore issued for information purposes only.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) you need assistance. 1099 Message Encountered an unexpected error: Subsys = value, Info = value 1102 Cause STAGEMAN encountered an error that is not recognized by the HP Stage/iX facility, and has no matching error message in the system catalog. This normally indicates a problem within the HP Stage/iX subsystem that should be reported to Hewlett-Packard. Action Contact your Hewlett-Packard Response Center for assistance.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1106 Message Found a bad file disposition value for file “name”. (STAGEMAN 1106) Cause STAGEMAN found an unexpected file disposition value for the file (the file disposition should be ADD, REPLACE, or DELETE). 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. 1107 Message Found a bad error action value for file “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) staging area (FCLOSE ,PURGE option). Action Determine why the FCLOSE failed, correct the problem, then re- execute the command. 1112 Message Failed to close file “name” in the staging area. (STAGEMAN 1112) 1115 Cause STAGEMAN received a bad status from the FCLOSE intrinsic while attempting the close the file. Action Determine why the FCLOSE failed, correct the problem, then re-execute the command. Message 1113 and 1114 not used.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1131) Cause STAGEMAN received a Command Interpreter (CI) error in attempting to copy the file into a staging area. The most likely reason for the copy to fail is an out of disk space condition (this is especially true if the file is restricted to LDEV1). Action Determine why the COPY command failed, correct the problem, then re-execute the command (or Patch/iX process). 1129 Message Rename command failed in moving file “name” to the staging area.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) the file specified in the FROM parameter does not exist, but a version of the file does already exist in the staging area. This is a normal occurrence when Patch/iX is using STAGEMAN to stage files into a staging area while Patch/iX is in recovery mode (for instance, if it previously failed in the middle of staging files). Action None 1134 Message Failed to set the ACD on file “name”.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Action Contact your Hewlett-Packard Response Center for assistance. 1139 Message Failed to get the sector address of file “name”. (STAGEMAN 1142) Cause STAGEMAN received a bad status from an internal routine while attempting to get the sector address of the file (this address is needed for placing an entry for the file in the system LIF Directory so that the file is accessible from the ISL prompt).
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1144 1145 1146 Action Contact your Hewlett-Packard Response Center for assistance. Message Failed to convert date with ALMANAC. (STAGEMAN 1147) Cause STAGEMAN received a bad status from the ALMANAC intrinsic while attempting to convert the date and time stamp for output. Action Contact your Hewlett-Packard Response Center for assistance. Message Failed to open the LIF Directory.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Globals file (/SYS/hpstage/stage_globals), which stores critical information about the HP Stage/iX environment and all known staging areas. The Globals file could not be opened however because it was being held open exclusively by another process at the time.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) /SYS/hpstage/stage_name/stage_contents). Action Determine the cause of the file open failure, correct the problem, then re-execute the command (or restart the Patch/iX process). 1174 Message No contents file found in “name”. Can't do command.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Action Contact your Hewlett-Packard Response Center for assistance. 1184 Message Found no cause/action text corresponding to “name”. (STAGEMAN 1184) Cause STAGEMAN expected to find cause/action text for the error number given with ERRMSG, but no corresponding text exists in the catalog. Action Please report this problem to your Hewlett-Packard Response Center. Message 1185-1302 not used. Message Invalid parameter length.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) Action Report this problem to your Hewlett-Packard Response Center. Message Error in accessing message catalog. (STAGEMAN 1310) Cause STAGEMAN could not access its message catalog file, STAGE000.PUB.SYS. Action Make sure the catalog file exists and is not opened exclusively by another process. Message Invalid numeric index into command history stack.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) attempted by the user. 1502 1503 1504 1505 1506 1507 Appendix H 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. (STAGE 1502) 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) Response Center for assistance. 1508 1509 1510 1511 1512 1513 1514 446 Message Failed to create the HFS directory for the staging area. (STAGE 1508) 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 HFS directory for the staging area.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 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. Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message The HP Stage/iX Import directory already exists. (STAGE 1515) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1521 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. 1522 1523 1524 1525 1526 1527 448 Message Failed to open contents file for staging area. (STAGE 1522) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1528 1529 1530 1531 1532 1533 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 clear write protection on the contents file. (STAGE 1528) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1534 1535 1536 1537 1540 1541 450 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 FWRITE to contents file for staging area. (STAGE 1534) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) 1542 1543 1550 1551 1590 1600 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 The HP Stage/iX Export directory does not exist. (STAGE 1542) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) should not normally see. 1601 1602 1603 1604 1605 1606 452 Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message A problem occurred switching a file during bootup. (STAGE 1601) 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) 1607 1608 1609 1610 1611 1612 1613 Appendix H Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Failed to write to the XM post file. (STAGE 1607) 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: FCONTROL of a file failed.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) case. (STAGE 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: A string size of < 1 was passed to a procedure. (STAGE 1614) Cause This is an HP Stage/iX internal error which the user should not normally see.
Error Messages and Warnings Stage/iX Messages (STAGEMAN) should not normally see. 1620 1621 1622 Appendix H Action If you get this error, contact your Hewlett-Packard Response Center for assistance. Message Internal Error: No START or STARTBASE entry was found in the LIF Directory. (STAGE 1620) 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) 456 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, 101, 123, 138 account recommended passwords, 148 accounting structure create, 115, 137, 139 rebuild, 76 accounts HP defined, 56 activate staging area, 17, 121 UDC, 149 Adding (SUBSYS) Products Main menu, 87 option, 85 Adding a PowerPatch option, 85 Adding a Reactive Patch option, 85 add-on checklist, 22 Add-on with CD-ROM checklist, 35, 39 Add-on with Tape and Manage Patches checklist, 33, 35 Add-on with Tape checklist, 31 ALLBASE/4GL secure the system, 102, 124 ALLBASE/SQL secure
Index logon, 71, 76, 112, 113, 122 contiguous disk space, 64, 67, 70 conversion disk space to megabytes, 66 NMMGRVER, 143 create accounting structure, 115 CSLT with AUTOINST, 116 Stage Tape menu option, 85 CSLT add customized files, 78 apply, 128 base group file, 79 mount, 128 PowerPatch for remote system, 78 re-install checklist, 43 update, 129 CSLT creating for patches, 92, 95 for remote system, 78 with AUTOINST, 113, 116 with HPINSTAL, 81 with Patch/iX, 95 customize file added to CSLT, 78 HP files, 56 p
Index K KEYFILE, 73, 79 keyword certificate, 79 master product, 79 references, 73 L LAN console card, 144 LDEV hard disk requirements, 63 PowerPatch tape, 86, 88, 96 Reactive tape, 86, 88 SUBSYS tape, 86, 88, 96 LDEV 1 capacity, 63 disk space, 70, 71 limitations, 63 maximum usage, 63 libraries copying, 86 modify, 96 LIMIT command, 100, 118, 119, 121, 131 limitations LDEV1 disk, 63 local system, 72 lockword reapply, 148 set, 148 log off users, 100, 123, 138 log on Patch/iX, 84 logging processes record names
Index DTCs, 154 power failure protection, 143 PowerPatch, 52 AUTOINST option, 114 information file restoring, 87 Patch/iX, 85 Patch/iX tape request, 96 restore, 80, 115, 126 restore files, 96 restore with AUTOINST, 113 PowerTrust, 143 pre-4.
Index STAGEMAN command, 75, 157 staging area, 17 activate, 121 contents, 121 create, 83, 95 create for patches, 92, 95 name, 96 permanent, 157 reboot, 157 staging group secure the system, 103, 125 start data communications, 154 Patch/iX, 83 system, 109 START command, 109, 111, 131, 153 START PME create, 96 start the system, 111, 131 STARTDBE command, 101, 124 startup messages, 106, 109 STORE create tape for patches, 95 files for backup, 76 NMCONFIG file, 143 STORE command, 76, 124 store tape create for pat
