System Startup, Configuration, and Shutdown Reference Manual HP e3000 MPE/iX Computer Systems Edition 7 Manufacturing Part Number : 32650-90907 E0802 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction What Is System Startup?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How System Startup is Carried Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Is System Configuration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How System Configuration Is Performed . . . . . . . . . . . .
Contents Updating to Recover from System Failure: a Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up the System and Retaining the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the INSTALL Utility to Recover a Lost System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Adding a Device Class with IOCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Device Class with IOCONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing One or More Device Classes with IOCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Device Class with IOCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Clearing SYSFILE Configurator Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Holding and Saving Configuration Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering an MPE Command from the SYSFILE Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting the SYSFILE Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Copying Default Configuration File Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Using SYSGEN to Copy the Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 E. Verifying Attached Devices Overview. . . . . . . . . . . . . .
Contents Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table 2-1. AP Reset Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table 3-1. ISL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Table 3-2. Execution of SYSSTART File Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Table 3-3. Utility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 10
Figures Figure C-1. Stable Storage Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Figure C-2. NVM Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 12
Preface 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 e3000 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.
• Appendix F, “Adding Peripherals to a System,” explains how to define device paths for peripherals connected to a system via several different kinds of device adapters. • Appendix G, “UPS and UPS Monitor/iX Software,” explains the new method of power failure protection available on HP e3000 systems. The Glossary defines the important terms introduced in system management. The Index is an alphabetical listing of subjects, cross-referenced with their location in the manual.
Introduction 1 Introduction This chapter defines system startup, system configuration, and system shutdown. It also briefly describes the procedures for starting, configuring, and shutting down a HP e3000 (Series 900) computer system. The details for these procedures are discussed throughout the following chapters.
Introduction What Is System Startup? What Is System Startup? System startup refers to the procedure for starting the computer software, namely the operating system, and other programs. System startup does not refer to installing the system for the first time. (A separate installation guide for your first loading of the new fundamental operating software (FOS) comes with each FOS tape. See below.
Introduction What Is System Configuration? What Is System Configuration? System configuration is the means by which you define, in terms meaningful to the operating system, any or all of the peripheral devices attached to the computer for the input (entering) or output (storing or displaying) of data. Such devices include terminals, printers, disk drives, and tape drives.
Introduction What Is System Shutdown? What Is System Shutdown? System shutdown refers to stopping the computer’s software, operating system, and other programs. (Stopping system activity makes the computer inaccessible to users.) A system shutdown does not imply turning off power to the computer hardware.
Initiating System Activity 2 Initiating System Activity Separate firmware routines of processor-dependent code (PDC) and input/output-dependent code (IODC) perform the system self-test and initialization after resetting HP Precision Architecture hardware. The initial program load (IPL), the first software retrieved from the boot device, implements the operating-system-independent portion of the bootstrap process.
Initiating System Activity Resetting the System Resetting the System There are two general types of resets for the HP 3000 (Series 900): a soft reset and a hard reset. Soft Reset A soft reset, the type of reset used most often, preserves the current processor state. This type of reset performs a nondisruptive memory test and terminates all I/O operations before executing recovery software for starting the boot device and console selection process.
Initiating System Activity Resetting the System To reset the system using the access port (AP), or Guardian Service Processor (GSP), follow the directions listed below: 1. Place the console in control mode by entering CTRL B at the system prompt. The console responds by displaying the control mode prompt (CM>) and activating the system status line at the bottom of the screen: CM> . . .
Initiating System Activity Resetting the System Execution of this command irrecoverably halts all system processing and I/O activity and restarts the computer system.
Initiating System Activity Resetting the System 1 540 MHz 3 Unknown Active Functional 512 KB 1 MB Stopped:Deconfigured Unknown 512 KB 1 MB Central Bus Speed (in MHz) : 133 Available Memory : 2097152 Good Memory Required : Not initialized. Defaults to 32 MB. Primary boot path: 0/0/2/0.6 Alternate boot path: 0/12/0/0.2 Console path: 0/0/4/0.0 Keyboard path: 0/0/4/0.
Initiating System Activity Resetting the System Example 2-2 Resetting an N class System Using AP/GSP Commands Autoboot Enabled : GSP Host Name: csyprel18(csysas18) GSP> tc TC Execution of this command irrecoverably halts all system processing and I/O activity and restarts the computer system. Type Y to confirm your intention to restart the system: (Y/[N]) y y -> SPU hardware was successfully reset.
Initiating System Activity Resetting the System I/O test 8107 I/O test 8107 processor test 1142 platform test 612A I/O config 8238 ***************************************** ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** Firmware Version 21.
Initiating System Activity Resetting the System Trying Primary Boot Path -----------------------Booting... Boot IO Dependent Code (IODC) revision 1 SOFT Booted. MMSAVE Version 2.5 DUMPAREA found, save main memory to disc ISL loaded ISL Revision A.00.43 Apr 12, 2000 [insert autoboot past isl) If you do not press a key to interrupt the sequence, the system displays messages as it automatically boots the processor and operating system.
Initiating System Activity Determining and Selecting Input and Output (I/O) Paths Determining and Selecting Input and Output (I/O) Paths The system identifies adapter interfaces to a system bus and the associated devices by an I/O path. The I/O path is the address of the interface hardware and the physical path to reach a device. When the system is reset or the power is turned on, hardware routines read and initialize the I/O paths needed to boot the system.
Initiating System Activity Testing the System Testing the System A HP e3000 (Series 900) system undergoes a self-test upon reset.: After resetting and testing, the system either autoboots or initiates an interactive boot sequence. Whether or not the system autoboots depends on how the autoboot flag is set and the presence of an autoboot file. For information on using the AUTOBOOT command, refer to Chapter 3, “System Startup Functions.
Initiating System Activity The Booting Process The Booting Process The process of booting the processor-dependent code (PDC) and the input/output-dependent code (IODC) takes place immediately after the system self-test. The initialization process is hardware-driven and begins automatically. After the system is reset, the PDC and IODC boot sequence messages indicate or prompt for the I/O paths required for successful completion.
Initiating System Activity The Booting Process MMSAVE Version 2.2 DUMPAREA found, save main memory to disc ISL loaded ISL Revision A.00.28 July 15, 1993 ISL booting START AUTO , . , In Example 2-5, autoboot must be turned on, and an autoboot file (also known as an autoexecute file) must reside in the logical interchange format (LIF) directory for ISL to autoboot. If not, you get the message Cannot find an autoexecute file. AUTOBOOT ABORTED.
Initiating System Activity The Booting Process Primary boot path: 0/0/2/0.6 Alternate boot path: 0/0/1/0.6 Console path: 0/0/4/0.0 Keyboard path: 0/0/4/0.0 Processor is booting from first available device. To discontinue, press any key within 10 seconds.
Initiating System Activity The Booting Process SOFT Booted. MMSAVE Version 2.5 DUMPAREA found, save main memory to disc ISL loaded ISL Revision A.00.
Initiating System Activity The Booting Process ------- ----------- BOot [PRI|ALT|] Boot from specified path PAth [PRI|ALT] [] Display or modify a path SEArch [DIsplay|IPL] [] Search for boot devices COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [
Initiating System Activity The Booting Process ***************************************** ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** Firmware Version 21.
Initiating System Activity The Booting Process DIsplay Redisplay the current menu HElp [
Initiating System Activity The Booting Process Interactively Booting the System with Autoboot Disabled Interactively booting the system with autoboot disabled allows you to select a particular boot path or to activate ISL from the keyboard. The initial interactive sequence is similar to the initial autoboot sequence, except in the interactive sequence, the system does not prompt the user with the option to override the process. Example 2-7 demonstrates the interactive boot sequence for an N-Class system.
Initiating System Activity The Booting Process Firmware Version 21.
Initiating System Activity The Booting Process Booting... Boot IO Dependent Code (IODC) revision 1 SOFT Booted. In this example, the system halts at ISL and then waits for the operator to issue an ISL command. For more information on ISL and ISL utilities, refer to Chapter 3, “System Startup Functions.” Bypassing the Disabled Autoboot Setting Answering NO to the prompt Interact with IPL (Y or N)? causes the system to ignore a disabled autoboot flag setting and attempt to autoboot.
Initiating System Activity The Booting Process ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** Firmware Version 21.
Initiating System Activity The Booting Process Main Menu: Enter command or menu > bo 0/0/2/0.6 Interact with IPL (Y, N, or Cancel)?> n Booting... Boot IO Dependent Code (IODC) revision 1 SOFT Booted. MMSAVE Version 2.5 DUMPAREA protected, proceeding to ISL without memsave ISL loaded ISL Revision A.00.43 Apr 12, 2000 Cannot find an auto-execute file. AUTOBOOT ABORTED.
Initiating System Activity System Startup Procedure System Startup Procedure The following procedure is an example of what to enter and what it looks like to start a system. To initiate the startup process enter: CTRL B If you have a 99X system, you must transfer to the service processor before you reset the system. NOTE CM> SP If you have an N-Class system, a PDC screen is displayed. Type BO to boot from the primary path.
Initiating System Activity System Startup Procedure I/O test 8107 I/O test 8107 processor test 1142 platform test 612A I/O config 8238 ***************************************** ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** Firmware Version 21.
Initiating System Activity System Startup Procedure COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [
Initiating System Activity System Startup Procedure For further information about system startups, refer to Chapter 3, “System Startup Functions.
System Startup Functions 3 System Startup Functions The initial system loader (ISL) provides a command-driven user interface for accessing boot utilities or issuing ISL commands to display or change system startup functions. When the system is booted from tape (tape boots), processor-dependent code (PDC) directly loads the ISL. When the system is booted from disk (disk boots), PDC and input/output-dependent code (IODC) boot the utility MMSAVE, which in turn boots ISL.
System Startup Functions Initial System Loader (ISL) Initial System Loader (ISL) On tape boots, the ISL is loaded directly by the processor-dependent code (PDC). ISL reads the logical interchange format (LIF) directory from tape and uses this directory to find other files on the tape. On disk boots, the PDC and IODC boot the utility MMSAVE, which in turn boots the ISL. PDC and IODC read the first record or sector of the boot device, which is the LIF label.
System Startup Functions Initial System Loader (ISL) Table 3-1 ISL Commands (Continued) Command EST Meaning Execute commands in EST (Extended Self Test) file For more information on the contents of stable storage and NVM, refer to Appendix C, “Reading Stable Storage and Nonvolatile Memory.” Using the Help Facility for ISL Commands Example 3-1 demonstrates using the ISL command, HELP.
System Startup Functions Initial System Loader (ISL) Listing Available ISL Utilities Example 3-2 demonstrates using the ISL LS command to display available ISL utilities. To generate a list of the utilities available on the boot medium, enter LISTF or LS at the ISL prompt.
System Startup Functions Initial System Loader (ISL) BCDIAG -12864 510416 704 00/02/12 08:36:27 CAEXR -12864 511120 672 00/02/12 08:36:30 XMAP -12864 511792 1568 00/02/12 08:36:36 CLKUTIL -12864 513360 352 00/10/20 02:32:08 SADPATCH -12864 513712 784 00/10/20 02:32:14 ODEDATA2 -12864 1454928 7712 00/09/25 05:16:35 ISL> Chapter 3 49
System Startup Functions Activating and Deactivating Autoboot and Autosearch Functions Activating and Deactivating Autoboot and Autosearch Functions Enabling and disabling the autoboot and autosearch flags determines one of four boot device and console selections for system initialization. Hardware interprets the selections as follows: Manual (autoboot off and autosearch off). Ask for the path to the boot device. Use the path that is indicated. Initialize the path given, and boot from it.
System Startup Functions Activating and Deactivating Autoboot and Autosearch Functions CAUTION The commands described in the above paragraph may disrupt normal system functions if used inappropriately. For this reason, do not attempt to use these commands without assistance from Hewlett-Packard service personnel. To execute any of these three commands, enter the command with its appropriate parameter or enter Return after the command and wait to be prompted for further input: ISL> altpath 0/0/1/0.
System Startup Functions Activating and Deactivating Autoboot and Autosearch Functions Primary boot path is 0/0/2/0.6.0.0.0.0.0 Primary boot path is (hex) 0/0/2/0.6.0.0.0.0.0 Alternate boot path is 0/0/1/0.6.0.0.0.0.0 Alternate boot path is (hex) 0/0/1/0.6.0.0.0.0.0 System console path is 0/0/4/0.0.0.0.0.0.0 System console path is (hex) 0/0/4/0.0.0.0.0.0.0 ISL> Setting Fastsize If fastsize is set to the wrong value, you cannot do installs or updates. The only value that is acceptable is “F.
System Startup Functions Reading Nonvolatile Memory (NVM) Reading Nonvolatile Memory (NVM) Not available on N-Class and A-Class systems NOTE Nonvolatile memory stores system activity parameters, including a circular queue of the last six ISL utilities executed. This information remains intact, even through system failures.
System Startup Functions Reading Nonvolatile Memory (NVM) **************************************************************** ****** ****** ****** CLKUTIL ****** ****** ****** ****** (C) Copyright Hewlett-Packard Co 1987, 1988, 1990 ****** ****** ****** All Rights Reserved ****** ****** ****** HP shall not be liable for any damages resulting ****** ****** from the use of this program. ****** ****** ****** ****** Version A.02.
System Startup Functions ISL Boot Utilities ISL Boot Utilities The system uses bootable ISL utilities to either load the system from tape or to start the system from disk. The current boot utilities are START, UPDATE, INSTALL, and DUMP. There are additional utilities for system management: SADPATCH, DISCUTIL, CLKUTIL, and SAT. The START utility starts the system from disk. Use this utility to recover from a system hang or failure or to reboot the system after scheduled downtime.
System Startup Functions Starting the System Starting the System This section discusses using the initial system loader utility, START, that activates the operating system. START is the ISL utility used most often, whether to boot the system from disk after a reset, to automatically reboot after the completion of the UPDATE, INSTALL, or DUMP utility, or to bring up the operating system after a shutdown. START execution differs depending on the previously executed boot command.
System Startup Functions Starting the System These default options instruct the system to boot from disk, to use the configuration information last used to boot the system, attempts to log on as OPERATOR.SYS (if the OPERATOR user has been created), to restart all jobs and allow all users access to the system, to bring up all volumes present on the system, and to execute commands found in the SYSSTART file, SYSSTART.PUB.SYS.
System Startup Functions Starting the System ALLOCATE COBOLII.PUB.SYS LIMIT 8,16 JOBFENCE 6 OUTFENCE 6 OUTFENCE 12;LDEV=14 FILE T;DEV=TAPE *** WARMSTART STREAMS 10 ALLOW @.@;COMMANDS=REPLY ALLOCATE COBOLII.PUB.SYS LIMIT 8,16 JOBFENCE 6 OUTFENCE 6 OUTFENCE 12;LDEV=14 FILE T;DEV=TAPE *** COOLSTART STREAMS 10 ALLOW @.@;COMMANDS=REPLY ALLOCATE COBOLII.PUB.SYS LIMIT 8,16 JOBFENCE 6 OUTFENCE 6 OUTFENCE 12;LDEV=14 FILE T;DEV=TAPE *** UPDATE LIMIT 1,1 JOBFENCE 14 OUTFENCE 14 STARTSESS 20;MANAGER.
System Startup Functions Starting the System HELLO MANAGER.SYS FILE SYSSTART;DEV=1 FCOPY FROM=tempfilename;TO=*SYSSTART;NEW If an error exists in the SYSSTART file, the startup process ignores it and continues execution. Starting a HP e3000 (Series 900) The following steps comprise a procedure for booting MPE/iX on a HP e3000 (Series 900) computer system using START following a reset. To start the system, perform the following steps: 1.
System Startup Functions Starting the System PDH config 3277 PDH config 3278 platform config 626F processor test 1142 processor test 1100 processor test 1100 memory test 71A4 memory test 71A4 memory test 71A4 . . . ***************************************** ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** Firmware Version 21.
System Startup Functions Starting the System Command Description ------- ----------- BOot [PRI|ALT|] Boot from specified path PAth [PRI|ALT] [] Display or modify a path SEArch [DIsplay|IPL] [] Search for boot devices COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [
System Startup Functions Starting the System Scanning PCI BUS D0 ................................ Scanning PCI BUS E0 ................................ Initialize_genesis - Ver bld1: <> FRI, JAN 18, 2002, 11:19:14 AM (y/n)? Initialize_genesis = Ready to configure I/O [CDM]8 8 0 18 Initialize genesis completed. Create Console Messages kso completed. Initialize memory manager completed. Initialize resident kernel completed.
System Startup Functions Starting the System The path 0/0/1/0.8.0 was configured but is not available. The path 0/0/1/0.9.0 was configured but is not available. The path 0/12/0/0.2.0 was configured but is not available. The path 0/12/0/1.2.0 was configured but is not available. The path 0/2/0/1.2.0 was configured but is not available. The path 0/4/0/1.2.0 was configured but is not available. Leaving - System I/O configuration. SYSTEM I/O AT BOOT TIME ldev: 1 HPC2490WD configured available 0/0/2/0.6.
System Startup Functions Starting the System 11:20/37/The system has finished rebuilding the output spoolfile directory. SYSTEM LOG FILE #83 IS ON Initializing Job & Session SESSION Scheduling Initialized JOB Scheduling Initialized Did not find a keyword in the first record of the SYSSTART file. Initiate Operator Log On MPE/iX:Successfully launched diagnostic monitor process. Successfully launched System UPS Monitor process.
System Startup Functions Starting the System processor . . . I/O test 8107 I/O test 8107 processor test 1142 platform test 612A I/O config 8238 ***************************************** ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** Firmware Version 21.
System Startup Functions Starting the System PAth [PRI|ALT] [] Display or modify a path SEArch [DIsplay|IPL] [] Search for boot devices COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [
System Startup Functions Starting the System FRI, JAN 18, 2002, 11:24:51 AM (y/n)? Initialize_genesis = Ready to configure I/O [CDM]8 8 0 18 Initialize genesis completed. Create Console Messages kso completed. Initialize memory manager completed. Initialize resident kernel completed. Initialize volume management and mount the System Disk Initialize volume management completed. Opening the native system library completed. Initialize loader completed. I/O boot path managers frozen in memory completed.
System Startup Functions Starting the System The path 0/4/0/1.2.0 was configured but is not available. Leaving - System I/O configuration. SYSTEM I/O AT BOOT TIME ldev: 1 HPC2490WD configured available 0/0/2/0.6.0 ldev: 6 HP5000/F100 configured not-available 0/0/1/0.8.0 ldev: 7 HPC1537A configured not-available 0/12/0/0.2.0 ldev: 8 HPC1537A configured not-available 0/12/0/1.2.0 ldev: 10 HP7978A configured not-available 0/0/1/0.9.
System Startup Functions Starting the System Did not find a keyword in the first record of the SYSSTART file. Initiate Operator Log On MPE/iX:Successfully launched diagnostic monitor process. Successfully launched System UPS Monitor process.
System Startup Functions Updating the Operating System Updating the Operating System This section provides general information on using the MPE/iX and initial system loader (ISL) commands, options, and utilities to update the operating system of a HP e3000 (Series 900). CAUTION Specific update and installation instructions are subject to change. This manual provides you with an overview of the procedures involved.
System Startup Functions Updating the Operating System Using the UPDATE Utility and Options The command to invoke the UPDATE utility is UPDATE.
System Startup Functions Updating the Operating System Updating the Operating System: a Preview NOTE Each customer installation or update is somewhat different. Examine the processes described for areas you may need to customize to fit your system.
System Startup Functions Updating the Operating System Updating to Recover from System Failure: a Preview If your system fails, you have many options to use to help recover your system. Use the UPDATE utility as a recovery method only after doing the following: 1. attempting a START RECOVERY 2. attempting a START NORECOVERY 3. ensuring the validity of your START procedure 4. ensuring your hardware, hardware code, and current software are functioning properly 5.
System Startup Functions Installing the Operating System Installing the Operating System This section provides a general overview on using operating system and initial system loader (ISL) commands, options, and utilities to install the operating system of a HP e3000 (Series 900) system. CAUTION Specific update and installation instructions are subject to change. This section provides you with an overview of the procedures involved. Do not use these instructions to update your system.
System Startup Functions Installing the Operating System In the event of a major system failure caused by corrupted files or other possible causes, you can use the INSTALL utility to reload your system. In this procedure, the system is recovered through the use of backup tapes. You use a system load tape created as part of your system backup procedure. Alternately, you may instead use the SLT that the AUTOINST program created when the system was last installed or updated.
System Startup Functions Installing the Operating System ISL> INSTALL START GROUP=CONFIG LOGON=OPERATOR.& SYS MULTI-DISC MULTI-USER SYSSTART The INSTALL process with its default options instructs the system to perform the following tasks if an autoboot file exists, the autoboot file is enabled, and the START option is specified: • Install the operating system, and autoboot the system from disk after the installation is completed. • Use the configuration group, CONFIG.SYS.
System Startup Functions Installing the Operating System Back up the System and Retain the Current Configuration If you are installing over an existing system, ensure that it has been thoroughly backed up. If up-to-date backups do not exist, reschedule the installation. The backups provide a method of restoring your data. Please refer to the HP e3000 MPE/iX System Software Maintenance Manual if you need additional information on backing up your system.
System Startup Functions Dumping System Memory and Secondary Storage Dumping System Memory and Secondary Storage This section discusses using MPE/iX and initial system loader commands, options, and utilities to dump system memory and secondary storage to tape. What is the Function of the DUMP Utility? The DUMP utility saves the current state of the system’s main memory and secondary storage to tape for later analysis.
System Startup Functions Dumping System Memory and Secondary Storage Entering the DUMP Utility and Starting the System A procedure for performing a dump and booting a system includes the following steps: 1. Mount a tape on the tape drive. 2. Soft reset the system using the access port method, boot from the primary path, and enter the DUMP command at the ISL prompt. NOTE If you have a 99X system, you must transfer to the service processor before you can soft reset the system.
System Startup Functions Dumping System Memory and Secondary Storage GSP Host Name: csyprel18(csysas18) GSP> ********** VIRTUAL FRONT PANEL ********** System Boot detected ***************************************** LEDs: RUN ATTENTION FAULT REMOTE POWER ON FLASH OFF ON ON platform config 626F processor test 1142 processor test 1100 memory config 7280 I/O test 8107 I/O test 8107 processor test 1142 platform test 612A I/O config 8238 . . .
System Startup Functions Dumping System Memory and Secondary Storage MB 3 Unknown Stopped:Deconfigured Unknown 512 KB 1 MB Central Bus Speed (in MHz) : 133 Available Memory : 2097152 Good Memory Required : Not initialized. Defaults to 32 MB. Primary boot path: 0/0/2/0.6 Alternate boot path: 0/0/1/0.6 Console path: 0/0/4/0.0 Keyboard path: 0/0/4/0.
System Startup Functions Dumping System Memory and Secondary Storage ISL Revision A.00.43 Apr 12, 2000 ISL> dump MPE/iX launch facility Scanning PCI BUS 0 ++*..++.......................... Scanning PCI BUS 8 ................................ Scanning PCI BUS 10 *................................ Scanning PCI BUS 20 *................................ Scanning PCI BUS 28 +............................... Scanning PCI BUS 40 ................................ Scanning PCI BUS 50 .....................
System Startup Functions Dumping System Memory and Secondary Storage Begin dump of Processor Internal Memory. Processor Internal Memory dump complete. Begin dump of main memory. 177 Megabytes of main memory will be dumped ................................................................ Dump of memory save area complete. ................................................ ................................................................ Main memory dump complete.
System Startup Functions Dumping System Memory and Secondary Storage [{ ;SINGLE-DISC ;MULTI-DISC }] [{ ;SINGLE-USER ;MULTI-USER }] [{ ;SYSSTART ;NOSYSSTART }] When the START option of the UPDATE utility is selected, the remaining options are available.
System Startup Functions Dumping System Memory and Secondary Storage Table 3-3 Utility Options (Continued) Options Functions GROUP= configname Default: GROUP = CONFIG When the system is booted with NORECOVERY, the group specified after GROUP= is the source of configuration information. When performing an UPDATE, INSTALL, or DUMP, this group is only in effect if START is specified or defaulted.
System Startup Functions Dumping System Memory and Secondary Storage Table 3-3 Options SUBSET = ALL or SUBSET = MEMORY Default: SUBSET = ALL SYSSTART or NOSYSSTART Default: SYSSTART Utility Options (Continued) Functions During a dump, this option indicates whether the contents of main memory alone or main memory and secondary storage is dumped to tape for later analysis. If the subset is not specified, it defaults to ALL (main memory and secondary storage).
System Startup Functions Dumping System Memory and Secondary Storage Table 3-4 MPE/iX Utility Summary of System Startup Function (Continued) MPE/iX Function (When To Use) Spool file Recover y Permanent User Files INSTALL NOSTART Performs similarly to INSTALL or INSTALL START, but INSTALL NOSTART does not attempt to start the system after completing the install. No Lost from system disks. User files remain on nonsystem volumes. DUMP Boots system from disk.
System Startup Functions Dumping System Memory and Secondary Storage 88 Chapter 3
Using the System Generator (SYSGEN) 4 Using the System Generator (SYSGEN) SYSGEN is a utility used to modify the system configuration. System configuration changes are kept to disk in a configuration group or to a tape called a system load tape (SLT). The SYSGEN utility requires system supervisor (OP) capability to view system configuration and system manager (SM) capability to save changes or create an SLT. SYSGEN contains a global module and four configurators: • Input/Output (IO) Configurator.
Using the System Generator (SYSGEN) Entering the SYSGEN Global Module Entering the SYSGEN Global Module The command for the SYSGEN utility is SYSGEN. SYSGEN has four positional parameters: SYSGEN [ basegroup] [ ,newgroup ] [ ,inputfile [ ,outputfile ] ] The basegroup parameter specifies the group in the SYS account that contains the configuration data file set to be used or changed. The default base group is the group used to boot the system (usually CONFIG).
Using the System Generator (SYSGEN) Entering the SYSGEN Global Module io log (lo) misc (mi) basegroup (ba) show (sh) tape (ta) keep (ke) permyes (pe) clear (cl)(c) oclose (oc) redo sysgen> exit (ex)(e) help (he)(h) spu (sp) sysfile (sy) Chapter 4 91
Using the System Generator (SYSGEN) Using the Help Facility in SYSGEN’s Global Module Using the Help Facility in SYSGEN’s Global Module The help facility provides a list of the commands available at each functional level of SYSGEN. In addition, help provides the syntax of an individual command or the syntax of each command in the configurator or at the first-level menu. To obtain a list of the first-level commands, enter HELP (abbreviated HE or H) at the SYSGEN prompt as shown in the following example.
Using the System Generator (SYSGEN) Using the Help Facility in SYSGEN’s Global Module help (he)(h) hold (ho) oclose (oc) redo [command = ALL | command-name] sysgen> To display a listing of the syntax for a first-level command, enter HELP commandname as shown in the following example: sysgen>HELP BASEGROUP basegroup Chapter 4 (ba) [name=groupname] 93
Using the System Generator (SYSGEN) Using First-Level (Global Module) Commands Using First-Level (Global Module) Commands The first-level commands, displayed after entering SYSGEN, allow you to activate one of the four configurators (I/O, LOG, MISC, SYSFILE) or to keep, show, or clear changes made from the configurators. In addition, you can use first-level commands to call the SYSGEN help facility, alter basegroups, store configuration changes to tape, or exit the SYSGEN utility.
Using the System Generator (SYSGEN) SYSGEN Command Syntax SYSGEN Command Syntax Commands can be classified as either command only or command with parameters(s). Commands with parameters can be specified in one of the following ways: positional parameters keyword parameters options NOTE The command structure established by SYSGEN enables the user to select the manner in which parameters accompany the command. Positional parameters are assigned a position in the parameter sequence.
Using the System Generator (SYSGEN) Confirming Potentially Serious Actions Also, you can enter the SYSGEN global module and use the first-level command BASEGROUP: sysgen>BASEGROUP groupname The syntax for the BASEGROUP command (abbreviated BA) is: BASEGROUP [ [NAME=] groupname] The groupname parameter is a string of up to eight characters.
Using the System Generator (SYSGEN) Confirming Potentially Serious Actions Example 4-4 PERMYES OFF Action :SYSGEN SYSGEN version D.01.01 : catalog version D.01.01 TUE, SEP 14, 1993 Copyright 1987 Hewlett-Packard Co.
Using the System Generator (SYSGEN) Confirming Potentially Serious Actions rnmlib (rn) rsprog (rs) show (sh) clear (cl)(c) exit (ex)(e) help (he)(h) sysfile> sysfile>ASPROG FCOPY.PUB.SYS FCOPY.PUB.
Using the System Generator (SYSGEN) Showing the State of Configurators Showing the State of Configurators The SHOW command (abbreviated SH) displays the current state of the SYSGEN global facilities. SHOW has the following syntax: SHOW [TYPE = [ [ [ [ [ [DEST = BASEGROUP NEWGROUP VERSION PERMYES CONFIGURATOR ALL OFFLINE ] ] ] ] ] ] ] BASEGROUP lists the name of the current working configuration’s base group. NEWGROUP lists the name of the current new configuration group.
Using the System Generator (SYSGEN) Activating the Configurators Activating the Configurators The commands for entering each of the configurators (IO, LOG, MISC, SYSFILE) are SYSGEN first-level commands. To activate the configurators, you must first enter the SYSGEN Global module. Once you have the SYSGEN prompt, enter either IO, LOG, MISC, or SYSFILE to activate the Input/Output, Logging, Miscellaneous, or System File configurators, respectively.
Using the System Generator (SYSGEN) Clearing Configuration Changes Clearing Configuration Changes The SYSGEN global module CLEAR command (abbreviated CL) removes all temporary changes made from the four configurators. If, for example, you make IO and SYSFILE configurator changes and decide not to keep them, issue the global module CLEAR command to remove the changes made in both configurators.
Using the System Generator (SYSGEN) Generating a System Load Tape sysgen>KEEP FEUDAL purge old configuration (yes/no) ?NO ** configuration files not saved ** Answering NO cancels the command. If insufficient space exists on the main system disk to accommodate the creation of a new configuration group, SYSGEN issues a message indicating this. SYSGEN then terminates, losing the temporary files and the changes.
Using the System Generator (SYSGEN) Generating a System Load Tape STORE allows the user files that are specified in the file set list to be stored after the SLT. (The filesetliststring parameter is the same as the parameter specified with the STORE utility. All configuration changes made are reflected on the tape. (The temporary changes remain valid after SYSGEN has generated a tape.) Tapes created by the TAPE command do not contain the system file directory.
Using the System Generator (SYSGEN) Generating a System Load Tape The HOLD command saves changes (to a temporary file) made in the configurator at the time that the HOLD is issued. 5. Decide which files to dump to tape. SYSGEN allows you to choose which files to store to a boot tape. You may store autoboot images, boot images, and system programs. The SYSFILE configurator provides the utilities and commands that alter boot tape contents.
Using the System Generator (SYSGEN) Redirecting SYSGEN Input and Output Redirecting SYSGEN Input and Output By using SYSGEN’s file designators, you can redirect SYSGEN’s input and output. Redirecting SYSGEN’s input and output enables you, for example, to issue commands to SYSGEN using command files that can operate without user intervention or interactive keyboard input. SYSGEN uses three formal file designators for input, output, and listing: • SYSGIN.
Using the System Generator (SYSGEN) Redirecting SYSGEN Input and Output Example 4-10 lists the contents of the command file (LISTIT), which, when run, prints SYSGEN information on the system printer. Example 4-10 1 2 3 4 5 6 7 8 SYSGEN Command File (LISTIT) PERMYES ON IO LDEV DEST=OFFLINE LPATH DEST=OFFLINE LCLASS DEST=OFFLINE OCLOSE EXIT EXIT Table 4-3 explains the actions performed by the lines of the command file example.
Using the System Generator (SYSGEN) Exiting SYSGEN Exiting SYSGEN Use the EXIT command (abbreviated EX or E) to exit from a configurator and return to the SYSGEN global module, or to terminate SYSGEN and return to the MPE prompt. To exit either a configurator or SYSGEN, enter EXIT at the prompt: log>EXIT sysgen> or sysgen>EXIT : Note that the MPE prompt returns after SYSGEN ends.
Using the System Generator (SYSGEN) Exiting SYSGEN 108 Chapter 4
Modifying Input/Output (I/O) Configurations 5 Modifying Input/Output (I/O) Configurations With the introduction of version C.55.00 of MPE/iX, there are two ways to define input and output devices on a system: using SYSGEN’s I/O Configurator or using the IOCONFIG utility. Both methods provide information about the input and output devices configured on a system and let you make changes to the configuration as necessary.
Modifying Input/Output (I/O) Configurations I/O Paths I/O Paths An I/O path is the system address assigned to the device interface hardware and the physical path used to reach an I/O device. I/O Paths Used to Boot a System When a system is powered on or reset, the processor-dependent code (PDC) and I/O-dependent code (IODC) hardware routines read and initialize the I/O paths used to boot or reboot the system. The I/O paths that are used to load the system from disk or tape are referred to as boot paths.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator oclose (oc) redo io> Getting Help with I/O Configurator Commands The help facility enables you to identify quickly the function and syntax of those I/O configurator commands and options required to perform the multiple operations that define or change device-dependent information. To see a list of the commands available for use in the I/O configurator and their abbreviations, enter HELP at the I/O configurator prompt.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator path id [rsize [outdev [mode = = = = = [class [cmode = = [pmgr = [lmgr = [pmgrpri = [mpetype = [mpesubtype= [devname = devicepath productid recordsize] outputdevice] JOB|DATA|INTERACTIVE| DUPLICATIVE| INPUT|OUTPUT|AUTOREPLY|NLIO|NONE] classname,...
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator Table 5-2 Command I/O Configurator List Commands Definition Examples LCLASS Lists the class name or names you specify with the command, the class modes, and the devices associated with the classes in the I/O configuration. A class name is an identifier to which numerous devices can be assigned. Unlike LDEV numbers, device class names are not unique to each device.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator io>LCLASS (DISC,LP) OFFLINE 2. To close the file SYSGLIST and print the information, enter io>OCLOSE Sample Configuration Data Example 5-4 shows the kind of information you might see if you entered the LDEV command, without additional parameters, at the I/O configurator prompt on an N-Class system. Example 5-4 Listing Configured Devices: N-Class System io> ld LDEV: 1 DEVNAME: OUTDEV: ID: ST39103LC RSIZE: PATH: 0/0/2/0.6.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator Adding Objects in SYSGEN When you use SYSGEN to add objects to the system configuration, there are four I/O Configurator commands available: ACLASS, ADEV, APATH and AVOL. They are defined in Table 5-3. For more detailed information read Performing System Manager Tasks. Table 5-3 Command I/O Configurator Add Commands Definition Examples ACLASS Creates a new class name and associates devices to the new class.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator You use the NMMGR program to add non-local devices such as terminals, serial printers, UPS hardware and other objects to a system. To learn how to configure UPS devices, read “Introducing the UPS and UPS Monitor/iX Software” later in this chapter. To learn how to use NMMGR to configure other devices, read Configuring Systems for Terminals, Printers, and Other Serial Devices.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator Deleting Objects in SYSGEN When you use SYSGEN to delete objects from the system configuration, there are four I/O Configurator commands available to you: DCLASS, DDEV, DPATH, and DVOL. They are defined in Table 5-5 and explained in the following sections. Table 5-5 I/O Configurator Delete Commands Command Definition Examples DCLASS Removes one or more class names from the system.
Modifying Input/Output (I/O) Configurations Using the SYSGEN I/O Configurator The DOIONOW command creates a log file, ONLNOLOG.PUB.SYS, which is used to record the commands executed by IOCONFIG. If the DOIONOW command generates an error, you may view this same log file to determine the cause. This log file is purged and a new one is created prior to invoking the new configuration, which means that it only contains information for the last execution of IOCONFIG.
Modifying Input/Output (I/O) Configurations Using the IOCONFIG Utility Using the IOCONFIG Utility With the release of version C.55.00 of MPE/iX, system managers can now use a new utility, IOCONFIG, to change the I/O configuration and implement the changes immediately without rebooting the system. The IOCONFIG utility automatically updates SYSGEN’s base configuration.
Modifying Input/Output (I/O) Configurations Using the IOCONFIG Utility Table 5-6 Command IOCONFIG Commands Abbreviations Description ADDDEVICE adev, ad Adds a device from the physical configuration to the active configuration. LISTDEVICE ldev, ld Lists the active device configuration. DELETEDEVICE ddev, dd Deletes a device from the active configuration. ADDCLASS aclass, ac Adds a device class to the active configuration.
Modifying Input/Output (I/O) Configurations Using the IOCONFIG Utility INTERACTIVE DUPLICATIVE INPUT OUTPUT AUTOREPLY NLIO NONE }] [[CLASS =]classname] [ [CMODE =]{IN OUT CIO NCIO RANDOM DEFAULT}] [[PMGR =]physicalmanagername] [[LMGR =]logicalmanagername] [[PMGRPRI =]physicalmanager priority] [[MPETYPE =]compmodetype] [[MPESUBTYPE =]compmodesubtype] [[DEVNAME =]devicename] To configure a SCSI device, it must be physically connected to the specified path, it must be operational, and there must be a device-de
Modifying Input/Output (I/O) Configurations Using the IOCONFIG Utility Deleting a Device with IOCONFIG The system manager or operator may delete a device from the configuration using the DELETEDEVICE or DDEV command. A device is considered to be completely deconfigured when all its system-related resources are recovered. DDEV, at this time, can only deconfigure two kinds of devices completely: network printers and disks that are attached to single-ended SCSI adapters.
Modifying Input/Output (I/O) Configurations Using the IOCONFIG Utility [[DLDEV]=logical device #,...] [[MODE =]{IN OUT CIO NCIO RANDOM DEFAULT}] Currently, the system allows any device in the system to belong to only one associated class at any time. For example, if a device X belongs to a class Y and Y is associated to some user, then the MODIFYCLASS command prevents you from adding X to another class Z which is also associated to any user at the time.
Modifying Input/Output (I/O) Configurations Using the IOCONFIG Utility [[LMGR =]logicalmgrname] [[MAXIOS =] maxconcurrentchannelIOs] Listing an I/O Path with IOCONFIG An I/O path is the system address assigned to the device interface hardware and the physical path used to reach an I/O device. The system manager or operator can use the LISTPATH command to display information about adapters and I/O devices on a specified path in the active configuration.
Modifying Logging Configurations 6 Modifying Logging Configurations The LOG configurator enables the system manager to change the attributes of user and system logging processes. System logging records the use of certain system resources by accounts, groups, and users on a job or session basis. The system manager determines which events are logged. User logging allows users and subsystems to record additions and modifications to databases and other files used in applications programs.
Modifying Logging Configurations Entering the LOG Configurator Entering the LOG Configurator To access the LOG configurator, enter the LOG command (abbreviated LO) at the SYSGEN prompt as shown in the Example 6-1: Example 6-1 Activating the LOG Configurator sysgen>LOG ** LOG configurator commands ** show (sh) slog (sl) ulog (ul) clear (cl)(c) exit (ex)(e) help (he)(h) oclose (oc) log> hold (ho) redo Using the LOG Configurator Help Facility The help facility enables you to quickly identify the fu
Modifying Logging Configurations Entering the LOG Configurator log>HELP SHOW show (sh) [command [dest = SLOG|ULOG|ALL] = OFFLINE] Showing Current LOG Values The SHOW command displays the LOG values as currently set. SHOW has the following parameters: SHOW [COMMAND = [DEST = SLOG ULOG ALL OFFLINE ] ] ] ] SLOG lists the state of the system logging events. ULOG lists the number of user logging processes and users per logging process currently configured.
Modifying Logging Configurations Entering the LOG Configurator Console Log 115 Program File Event 116 Native Mode Spooling 120 File Quarantine Event 121 Chdir 127 Process Adoption 128 File Owner Change 129 Architected Interface 130 Additional Processor Launch 131 Password Change 134 System Logging Configuration 135 Restore 136 Printer Access Failure 137 ACD Change 138 Stream Initiation 139 User Logging 140 Process Creation 141 Security Configuration Change 142 Chgroup 143 File Open 144 CI Command Logging 14
Modifying Logging Configurations Entering the LOG Configurator NOTE Some events are permanently set to ON. Currently, events 101, 111, 146, and 150 are forced on by MPE/iX. NOTE MPE/iX is shipped from the factory with event number 116 "Program File Event" turned ON. Hewlett-Packard recommends that customers leave this event turned ON, as it can be useful for detecting potentially incompatible (and rare) runtime events.
Modifying Logging Configurations Entering the LOG Configurator Saving configuration changes is a two-step procedure. After you alter a configuration, you must, first, hold the changes before exiting the configurator. Second, use the global module KEEP command to save the changes. To hold changes, enter the HOLD command at the LOG configurator prompt: log>HOLD You can work in a SYSGEN configurator, hold the changes, and continue working in other SYSGEN configurators before saving the changes.
Modifying Logging Configurations Entering the LOG Configurator If you do not specify the OUTFILE parameter, the log prints on your terminal screen. Typically this report is very long and ties up your terminal for quite some time. If this does happen, you can enter CTRL Y to break the process. Printing a Subset of a Log File If you like, you can filter the output of LOGTOOL utility to show you information about only a specific user or users. The syntax for this is shown below.
Modifying Logging Configurations Entering the LOG Configurator 132 Chapter 6
Modifying Miscellaneous Configuration Elements 7 Modifying Miscellaneous Configuration Elements The MISC configurator provides commands to configure various types of file information difficult to categorize elsewhere. The MISC configurator handles changes to job-related and session-related items, processes, system resource allocations, spool parameters, stack and heap sizes, and miscellaneous system information.
Modifying Miscellaneous Configuration Elements Entering the MISC Configurator Entering the MISC Configurator To access the MISC configurator, enter the MISC command (abbreviated MI) at the SYSGEN prompt, as shown in Example 7-1.
Modifying Miscellaneous Configuration Elements Using the MISC Configurator Help Facility Using the MISC Configurator Help Facility The help facility enables you to identify quickly the function and syntax of MISC configurator commands. To obtain a list of the commands available for use in the MISC configurator, enter HELP at the MISC configurator prompt, as shown in Example 7-2.
Modifying Miscellaneous Configuration Elements Using the MISC Configurator Help Facility Entering HELP ALL produces a list of all MISC configurator commands and syntax. Example 7-3 displays the output.
Modifying Miscellaneous Configuration Elements Using the MISC Configurator Help Facility You can request help for a specific MISC configurator command by entering HELP commandname at the MISC configurator prompt: misc>HELP RESOURCE resource (re) Chapter 7 [grins [rins [iomont [maxcmcode [cmsegs [maxxdata [xdataperproc = = = = = = = globalrinallocation] totalrinallocation] iomonitortablesize] cmcodesegmentsize] cmcodesegsperproc] maxsizeofxdataseg] maxdatasegsproc] 137
Modifying Miscellaneous Configuration Elements Showing Values of Current Configurable Items Showing Values of Current Configurable Items The SHOW command, abbreviated SH, displays the values of the current configurable items referenced by it. SHOW has the following parameters: SHOW (SH) [ [COMMAND =] [ [ [ [ [ [ [ [ [DEST =] IO JOB RESOURCE SESSION STACK SYSTEM ALL OFFLINE ] ] ] ] ] ] ] ] JOB displays the job-related limits and default operating points.
Modifying Miscellaneous Configuration Elements Showing Values of Current Configurable Items Example 7-4 MISC Configurator SHOW ALL Output misc>SHOW ALL IO command ----------------DYNAMIC INPUT DEVS DYNAMIC OUTPUT DEVS DYNAMIC IO DEVS parameter MAX --------------maxdyninput 999 maxdynoutput 999 msxdynio 999 MIN ------0 0 0 CURRENT ------2 4 332 JOB command ----------------DEFAULT CPU LIMIT MAXIMUM LIMIT POOL SIZE parameter --------cputime maxlimit pool MAX ------32767 3010 200 MIN ------0 0 1 CURR
Modifying Miscellaneous Configuration Elements Showing Values of Current Configurable Items Example 7-5 demonstrates using the SHOW command to see the values allocated to a particular parameter: Example 7-5 MISC Configurator SHOW Output misc>SHOW JOB JOB command ----------------DEFAULT CPU LIMIT MAXIMUM LIMIT POOL SIZE 140 parameter --------cputime maxlimit pool MAX ------32767 3010 200 MIN ------0 0 1 CURRENT ------0 60 1 Chapter 7
Modifying Miscellaneous Configuration Elements Deleting Global Resource Identification Numbers (RIN) Deleting Global Resource Identification Numbers (RIN) A resource identification number (RIN) identifies a user-defined resource. A RIN allows a user to exclusively access resources including I/O devices, disk files, and programs. The DRIN command (abbreviated DR) removes allocated global resource identification numbers.
Modifying Miscellaneous Configuration Elements Configuring Job-Related Limits Configuring Job-Related Limits The JOB command (abbreviated JO) configures job-related limits and default operating modes. JOB has the following parameters: JOB (JO) [CPUTIME [MAXLIMIT [POOL = secondcount ] = maximumjoblimit ] = poolsize ] CPUTIME sets the default CPU time limit for batch jobs. MAXLIMIT sets the maximum job limit that may be set through the LIMIT command.
Modifying Miscellaneous Configuration Elements Displaying Allocated Global RINs Displaying Allocated Global RINs The LRIN command (abbreviated LR) displays allocated global RINs that are currently allocated either to the console or offline. LRIN has the following parameter: LRIN (LR) [[DEST =] OFFLINE ] OFFLINE redirects the output of the LRIN to the SYSGEN listing file, SYSGLIST. Using OFFLINE does not immediately generate a printout.
Modifying Miscellaneous Configuration Elements Setting Resource Allocations Setting Resource Allocations The RESOURCE command (abbreviated RE) sets system resource allocations.
Modifying Miscellaneous Configuration Elements Setting Resource Allocations To set one of the system resource allocations, enter the RESOURCE command and at least one parameter that is to change: misc>RESOURCE GRINS=40 ** Keyword ** misc>RE,,80 1024 ** Positional ** misc>RE 50,,80 1024 CMSEGS=50 ** Combination ** NOTE Chapter 7 Setting IOMONT too low (below 10) prevents the system from booting.
Modifying Miscellaneous Configuration Elements Setting Session-Related Limits Setting Session-Related Limits The SESSION command (abbreviated SE) configures session-related limits and default operating points. SESSION has the following parameters: SESSION (SE) [MAXLIMIT [LOGONTIMEOUT [CITIMEOUT [POOL = = = = maximum session limit] time in seconds] time in minutes] pool-size] MAXLIMIT sets the maximum session limit. LOGONTIMEOUT sets the number of seconds a user has to log on to the system.
Modifying Miscellaneous Configuration Elements Setting Sizes of Native Mode and Compatibility Mode Stacks Setting Sizes of Native Mode and Compatibility Mode Stacks The STACK command (abbreviated ST) configures the default sizes of the NM and CM stacks and the heap.
Modifying Miscellaneous Configuration Elements Setting Strings and String Parameters Setting Strings and String Parameters The SYSTEM command (abbreviated SY) sets various strings and parameters. SYSTEM has the following parameters: SYSTEM (SY) [ [USERVERSION =] x.yy.zz] [ [LOGONPROMPT =] prompt string] [ [CIPROMPT =] prompt string] USERVERSION allows the system manager to identify the system with a version meaningful to your environment. This might identify some combination of third-party products.
Modifying Miscellaneous Configuration Elements Clearing MISC Configuration Changes Clearing MISC Configuration Changes If you desire to clear all MISC configuration changes made, enter the CLEAR command at the MISC configurator prompt. misc>CLEAR Once a SYSGEN> KEEP is done, the changes become permanent and CLEAR does not remove them.
Modifying Miscellaneous Configuration Elements Holding and Saving Configuration Changes Holding and Saving Configuration Changes Using the MISC configurator commands described in the previous sections changes the configuration specified in the SYSGEN command line or global BASEGROUP command. These changes are temporary and are lost if not properly saved. Saving configuration changes is a two-step procedure. After you alter a configuration, you must first hold the changes before exiting the configurator.
Modifying Miscellaneous Configuration Elements Entering an MPE Command from the MISC Configurator Entering an MPE Command from the MISC Configurator Use the colon (:) to introduce an MPE command while in the MISC configurator. To issue an MPE command, enter the command along with the colon.
Modifying Miscellaneous Configuration Elements Exiting the MISC Configurator Exiting the MISC Configurator Use the EXIT command to terminate the MISC configurator and return to the SYSGEN Global module. EXIT may be abbreviated EX or E.
Modifying System File Configurations 8 Modifying System File Configurations The SYSFILE configurator enables the system manager to change system libraries, programs, and the system message catalog. The changes are made to a list of the files. SYSFILE has many of the features of the IO configurator that permit the user to add, delete, and replace objects through a series of related commands. NOTE Chapter 8 In order for SYSFILE configurator changes to become permanent, you must generate a boot tape.
Modifying System File Configurations Entering the SYSFILE Configurator Entering the SYSFILE Configurator Example 8-1 demonstrates activating the SYSFILE configurator.
Modifying System File Configurations Entering the SYSFILE Configurator file [mode prog file [sl type image seg prog [seg file type image file type name seg file [mode file image file type file prog file [file asprog (as) cmsl (cm) dauto (da) dboot (db) dcmsl (dc) dsprog (ds) lcmsl (lc) rauto (ra) rboot (rb) rcat (rc) rcmsl (rcm) rdcc (rd) ripl (ri) rnmlib (rn) rsprog (rs) show (sh) [dest = = = = = = = = = = = = = = = = = = = = = = = = = = = filename S|C|P|U] program-name filename sl-name] DISC|TAPE|B
Modifying System File Configurations Entering the SYSFILE Configurator Table 8-1 SYSFILE Configurator Command Matrix (Continued) ADD SYSTEM PROGRAM ASPROG DELETE DSPROG REPLACE LIST SPECIFY RSPROG SYSTEM CATALOG RCAT NETWORK CONFIG RDCC IPL IMAGE RIPL NM LIBRARY RNMLIB All commands have a two- or three-character abbreviation. CAUTION Do not use the SYSFILE> RSPROG command to rename Hewlett-Packard supplied MPE/iX HP e3000 system files.
Modifying System File Configurations Entering the SYSFILE Configurator NOTE The examples used to demonstrate SYSFILE configurator commands may produce display screens that do not exactly match output from your system. What SYSGEN displays depends entirely on how your system is configured. Displaying Current File Information The SHOW command (abbreviated SH) displays the file information currently set through SYSFILE.
Modifying System File Configurations Entering the SYSFILE Configurator Example 8-5 SYSFILE Configurator SHOW ALL Output sysfile>SHOW ALL DISC AUTOBOOT TAPE AUTOBOOT SYSTEM CATALOG CM SL NMCONFIG FILE NM LIB = = = = = = NONE NONE CATALOG.PUB.SYS SL.PUB.SYS NONE NL.PUB.SYS BOOT FILE --------ISL.MPEXL.SYS DUMP.MPEXL.SYS START.MPEXL.SYS INSTALL.MPEXL.SYS UPDATE.MPEXL.SYS A1002AI.MPEXL.SYS A1002AM.MPEXL.SYS A1002AP.MPEXL.SYS A1100AI.MPEXL.SYS A1100AM.MPEXL.SYS A1100AP.MPEXL.SYS CAEXR.MPEXL.SYS IOMAP.MPEXL.
Modifying System File Configurations Entering the SYSFILE Configurator Adding Autoboot Files The AAUTO command (abbreviated AA) adds an autoboot file to the list of files dumped onto SYSGEN’s tape. The command has the following parameters: AAUTO (AA) [FILE [TYPE =] = autobootfilename DISC ] [ TAPE ] [ BOTH ] FILE specifies the file name that contains autoboot commands. If it is not fully qualified with group and account name, it defaults to the current group and account.
Modifying System File Configurations Entering the SYSFILE Configurator Adding a Segment to the Compatibility Mode Segmented Library (CMSL) The ACMSL command (abbreviated AC) adds a segment to the CMSL. The command has the following parameters: ACMSL (AC) [SEG =] [FILE =] [MODE = segmentname filename S ] [ C ] [ P ] [ U ] SEG specifies a new segment name with a maximum of eight characters. If an existing segmentname is specified, an error occurs. FILE specifies a file name to be added to the CMSL.
Modifying System File Configurations Entering the SYSFILE Configurator Deleting Autoboot Images The DAUTO command (abbreviated DA) deletes the specified autoboot type from the list of files dumped onto SYSGEN’s tape. The command has the following parameter: DAUTO [TYPE = DISC ] [ TAPE ] [ BOTH ] TYPE specifies the type of autoboot file deleted. The following types are allowed: DISC Specifies that the file applies to disk only. TAPE Specifies that the file applies to tape only.
Modifying System File Configurations Entering the SYSFILE Configurator Deleting a system program does not remove it from the disk. To remove it from disk, an ISL INSTALL must be performed. Replacing Objects on the SYSGEN Tape The replace commands (RAUTO, RBOOT, RCAT, RCMSL, RDCC, RIPL, RNMLIB, and RSPROG) replace or modify information in the list of SYSGEN dump files. RAUTO replaces an existing autoboot image or modifies the autoboot type. RBOOT replaces an existing boot image or modifies the boot type.
Modifying System File Configurations Entering the SYSFILE Configurator IMAGE specifies an existing boot image name to be modified or replaced. If the specified boot image does not exist, an error occurs. FILE specifies a file name to replace the designated boot image. If it is not fully qualified with group and account name, it defaults to the current group and account. If the specified file does not exist, an error occurs. TYPE specifies the boot image type.
Modifying System File Configurations Entering the SYSFILE Configurator FILE specifies a file name to be added to the CMSL. The filename parameter can be fully qualified with group and account. If not, it defaults to the current group and account. If the file name cannot be found, an error occurs. MODE indicates where the added SL segment is to reside. It expects one of the four options listed below. Other input causes an error. P Declares a segment to be a permanently allocated user segment.
Modifying System File Configurations Entering the SYSFILE Configurator There can be only one disk and one tape IPL, each of which is replaced by its image name. Both IPL files must reside on the tape. To replace an IPL image, enter the command and the image and file names: sysfile>RIPL imagename filename Replacing the Native Mode Library The RNMLIB command (abbreviated RN) replaces the system NM library that resides in NL.PUB.SYS.
Modifying System File Configurations Entering the SYSFILE Configurator Enter the command and a fully qualified SL name to change the default, SL.PUB.SYS, as shown in the following example. sysfile>CMSL NEWSL.PUB.SYS Listing CMSL Contents The LCMSL command (abbreviated LC) lists the contents of the CMSL or a single segment in the CMSL. LCMSL has the following parameter: LCMSL (LC) [SEG =] segmentname The segment name designates which segment to list.
Modifying System File Configurations Entering the SYSFILE Configurator Entering an MPE Command from the SYSFILE Configurator Use the colon (:) to introduce an MPE command while in the SYSFILE configurator. To issue an MPE command, enter the command following the colon. For example: sysfile>:SHOWTIME THU, APR 20, 1989, 2:55PM sysfile> Exiting the SYSFILE Configurator Use the EXIT command (abbreviated EX or E) to deactivate the SYSFILE configurator and to return to the SYSGEN global module.
Modifying System File Configurations Entering the SYSFILE Configurator 168 Chapter 8
Halting System Activity 9 Halting System Activity A system shutdown does not imply turning off power to the computer hardware. Instead, system shutdown means stopping the computer’s operating system. Stopping system activity makes the computer inaccessible to users. You would need to shut down the system for maintenance, for a physical move, for changing the system configuration, or for security reasons. If done properly, a shutdown preserves all system and user files.
Halting System Activity Including Shutdown Information in the Welcome Message Including Shutdown Information in the Welcome Message Include shutdown information in the welcome message. Remember to include information about the time of the shutdown and whom a user should contact with questions. Enter: :WELCOME #Return This erases the present WELCOME message. Enter for a second time: :WELCOME # When the pound sign prompt (#) appears, enter the message line by line, terminating each line with Return.
Halting System Activity Including Shutdown Information in the Welcome Message Entering the SHUTQ command shuts down the spool queues to prevent users from sending reports to the printer. Enter: :SHUTQ nn (nn is your printer’s ldev number.) or :SHUTQ devname (devname is the device name of the spooled device) 3. List the backlog of existing reports. Enter: :LISTSPF This lists all spool files. If the system responds NO SUCH FILE(S), you have no spool files.
Halting System Activity Including Shutdown Information in the Welcome Message You can use these options to indicate the reason that you are shutting down the system. For example, if you shut down to clear a DTC hang, use the DTC option. CTRL A =SHUTDOWN DTC The console responds by listing shutdown messages similar to these: Shutdown Shutdown Shutdown Spoolers of operating system begins. (Shut 1) of user processes begins (Shut 2) of jobs & sessions begins. (Shut 3) notified of a shutdown. (Shut 16) . . .
Using the Access Port (AP) A Using the Access Port (AP) This section describes the access port (AP) commands and provides the procedures for enabling a remote console, for configuring a system remote support modem port, and for performing the AP self-test.
Using the Access Port (AP) Configuring the Console Configuring the Console Some of the terminal configuration parameters are important for proper AP operation.
Using the Access Port (AP) Configuring the Console Interpreting the System Status Line When in control mode, the AP displays the system status line across the softkey labels of the system console. The system status line has this format: CODE: xxxx REMOTE: < 1 > < 2 > < 3 > ACCESS FAULT: yy Table A-1 describes the information presented in the status line. Table A-1 Status Line Display Field Meaning xxxx Represents the four digit LED error code display.
Using the Access Port (AP) Configuring the Console Table A-2 Access Port Commands (Continued) Command Function RS Stops all processing, initiates SPU self-test, and loads software from load device if enabled for autoboot. SE Transfers remote terminal from console/control mode to session mode. TA Initiates access port self-test. TC Transfers processor execution to operating-system-specific routine. Initiates a system soft reset.
Using the Access Port (AP) Configuring the Console Using the CA command generates the following prompts: CM>CA Return Current remote support modem port configuration: Bit rate Rate Select/CCITT 111 System identification: 9600 bits/sec High rate (ON) Joe’s Sink and Pipe Shop Do you wish to change the configuration? (Y/N): Y Return Enter your changes. retains the current value. Current bit rate is 9600 bits/sec. Select the new bit rate.
Using the Access Port (AP) Configuring the Console The system identification is a displayable character ASCII string (24 characters maximum) that is stored on the AP, for the AP’s exclusive use. The AP identification has absolutely nothing whatsoever to do with any other system identification stored elsewhere in the SPU. No other entity has access to it, and the AP has no access to any other system identification. Enter up to 24 characters as the system identification.
Using the Access Port (AP) Configuring the Console Password: Password faults: The quick brown fox 5 Remote console access is now enabled. CM> The new access status settings do not take effect until you finally answer the change query with NO.
Using the Access Port (AP) Configuring the Console Connecting the Remote Support Modem to a Session Port This command is valid from the remote support modem port only. Entering SE causes the remote support modem port to connect through to a session port. If DTR is on, the remote support port’s modem remains connected. The remote support modem is able to initiate a session using a normal connection protocol, as if a new modem connection had just been established.
Using the Access Port (AP) Configuring the Console If the AP command interpreter encounters errors or inappropriate input during the reset (RS) process, it may display a combination of the following messages: Expecting ”Y” or ”N” (APERR 11) Unable to verify assertion of RESET_SYS backplane signal (APERR 01). RESET SYS backplane signal asserted, but unable to verify SPU deassertion of PPON backplane signal (APERR 02). PPON not reasserted by SPU after RESET_SYS deassertion (APERR 03).
Using the Access Port (AP) Configuring the Console During the execution of self-test, some of the test numbers shown above may have the mnemonics NC, NT1H, or NS1H appended to them. Whether or not these appear depends upon the test hood configuration present at the time of test execution. NOTE The master terminal after the completion of the self-test is the terminal that was master when the test was initiated.
Using the Access Port (AP) Configuring the Console Failure of the AP drive circuitry causes this error to be detected, and the SPU is not reset. The circuitry that permits the AP to read this line may have failed. If this is the case, the error message is displayed, but the SPU is reset in the proper manner. The CIO backplane may contain a short between the RESET_SYS- line and another low impedance line that is driving a high-logic level.
Using the Access Port (AP) Configuring the Console CAUSE: This message is displayed when the AP has exhausted the permitted number of accesses to all blocks of NVM. The default settings for NVM parameters are used. Notify your HP service personnel. The AP must be replaced. MESSAGE: Illegal command, type HE for help. (APERR 10) CAUSE: The first two characters entered in a command line for the AP command interpreter are not an AP command. Help displays all legal commands.
Using the Access Port (AP) Configuring the Console AP self-test detects only approximately 70 percent of the faults on the AP. MESSAGE: SPU hardware was successfully reset. (APMSG 02) CAUSE: This message indicates that the AP did not enter the three possible error states. It does not mean that the AP has somehow detected that the processor has restarted or that it was cleared, for example. The AP has no way to determine the internal state of any other assembly in the SPU.
Using the Access Port (AP) Configuring the Console 186 Appendix A
Startup, Dump, and Shutdown Listings B Startup, Dump, and Shutdown Listings This appendix lists or references the messages received at the console during successful ISL startup (START), dump (DUMP), and shutdown (SHUTDOWN) operations.
Startup, Dump, and Shutdown Listings START Sequence START Sequence Refer to Chapter 3, “System Startup Functions,” for information on the steps involved in the startup process.
Startup, Dump, and Shutdown Listings DUMP Sequence DUMP Sequence Refer to Chapter 3, “System Startup Functions,” for information on the steps involved in the DUMP process. See Example 3-7 for the output from a DUMP sequence. CAUTION Appendix B Do not use the RS command from the console or push the reset button on the front panel to reset the system for a dump. Hard resetting the system initiates a processor self-test that invalidates dump data.
Startup, Dump, and Shutdown Listings Shutdown Sequence Shutdown Sequence This sequence, unlike the previous four, begins at the MPE prompt. (Presumably, the system is up and running before it is shut down.) Refer to Chapter 9, “Halting System Activity,” for information on the steps involved in shutting down the system. The following represents a shutdown sequence for the N-Class systems received at the console. Sequences from other installations may vary. :TELL @S;SHUTDOWN IN 15 MINUTES.
Reading Stable Storage and Nonvolatile Memory C Reading Stable Storage and Nonvolatile Memory Certain types of system errors and failures may indicate problems with the stable storage or nonvolatile memory (NVM). In these cases, your HP customer engineer may request that you note the contents of certain locations in these storages. ISL provides two commands, READSS and READNVM, that read the contents of storage addresses in stable storage and nonvolatile memory (NVM).
Reading Stable Storage and Nonvolatile Memory Reading Stable Storage Contents Reading Stable Storage Contents Stable storage contains the boot path information along with other critical file system parameters in a minimum area of 96 bytes of high-reliability memory. The storage maintains the critical parameters even if the storage card is removed from the backplane.
Reading Stable Storage and Nonvolatile Memory Reading Stable Storage Contents The console path and alternate paths are stored in the same format as the primary boot path. Unlike the primary boot path, the first byte of the first word of the console and alternate boot paths is set to hex 00. The autoboot and autosearch flags are not stored with these paths.
Reading Stable Storage and Nonvolatile Memory Reading Nonvolatile Memory (NVM) Reading Nonvolatile Memory (NVM) (Not applicable to N-Class and A-Class ) NVM stores system activity parameters, including a circular queue of the last six ISL utilities executed, which is useful as a diagnostic aid in the event of a system crash or failure. NVM contains initialization information in a 92-byte block starting at decimal byte address 36. NVM stores this information as shown in Figure C-2.
Reading Stable Storage and Nonvolatile Memory Reading Nonvolatile Memory (NVM) To read an NVM location, enter the ISL READNVM command and enter the hexadecimal or decimal address. The output is always in hexadecimal. In the following examples, addresses are referred to in decimal notation and the output is in hexadecimal notation. The last boot path, starting at byte address decimal 36, contains the status of the autoboot and autosearch flags during the boot sequence.
Reading Stable Storage and Nonvolatile Memory Reading Nonvolatile Memory (NVM) Table C-1 lists the ISL utility names and the hexadecimal representation for both uppercase and lowercase spellings.
Default Configurations Used by INSTALL and UPDATE D Default Configurations Used by INSTALL and UPDATE The INSTALL utility on a factory system load tape replaces a system’s configuration files with a default configuration. These defaults allow the system manager or system supervisor to boot the system to a fully operational level. You should then alter the functioning configuration to meet your system’s needs using SYSGEN. START uses CONFIG as its default configuration group.
Default Configurations Used by INSTALL and UPDATE Table D-1 Default Configurations for the HP e3000 (Continued) Group Name System Description Cards CONFNCL2 N-Class with external disk PCI/SCSI CONFNCL3 PA-8700 N-Class with 2 internal disks PCI/SCSI CONFNCL4 PA-8700 N-Class with external disk PCI/SCSI NOTE The PB-FL card is the FL card that is used in precision bus systems, such as 99X systems.
Default Configurations Used by INSTALL and UPDATE Copying Default Configuration File Groups Copying Default Configuration File Groups This section discusses renaming the default configuration files groups used by the UPDATE and INSTALL utilities mentioned in Chapter 3, “System Startup Functions.”. Overview The INSTALL utility replaces a system’s configuration files with a default configuration. These defaults allow the system manager or system operator to boot the system to a fully operational level.
Default Configurations Used by INSTALL and UPDATE Using SYSGEN to Copy the Files Using SYSGEN to Copy the Files You must use SYSGEN to copy configuration groups. Using other methods to copy configuration files removes key elements and corrupts the files. To copy a default configuration group into the configuration group CONFIG, follow the instructions outlined below: 1. Activate SYSGEN. Entering SYSGEN activates SYSGEN’s global module. :SYSGEN SYSGEN version B.06.01 : catalog version B.06.
Default Configurations Used by INSTALL and UPDATE Using SYSGEN to Copy the Files 5. Generate a system load tape (SLT) if desired. To create an SLT that contains the new configuration, use CONFIG as the base group, and save it to tape, as discussed in Chapter 3, “System Startup Functions.” 6. Use the new configuration and restart the system. If you modified the configuration and now desire to implement it on the system, shut down and restart the system. To shut down the system enter: :CTRL A =SHUTDOWN 7.
Default Configurations Used by INSTALL and UPDATE Using SYSGEN to Copy the Files 202 Appendix D
Verifying Attached Devices Overview E Verifying Attached Devices This section discusses using the initial system loader’s ODE utility to verify which devices are attached and configured to a HP e3000 computer system. Overview SYSGEN provides utilities for listing the configured paths and associated devices of a system. It does not, however, provide a utility for listing the devices actually attached to the system. (A valid configured path does not require an associated device.
Verifying Attached Devices Displaying Configured Devices 1. Remove all users from the system. If your system is not currently in use, skip to step 2. a. Log on at the system console as MANAGER.SYS. Enter: :HELLO MANAGER[/userpass].SYS[/acctpass] b. Tell users of the approaching shutdown. Notice that entering ISL makes the system inaccessible to users. Use the TELL command to alert users (except those in quiet mode) to the impending system shutdown. Ten minutes beforehand, ask users to log off.
Verifying Attached Devices Displaying Configured Devices ISL>ODE 5. Initiate the mapper2 module: ISL>RUN mapper2 mapper2 displays the current configuration (see Example E-1 for an example display). Example E-1 Mapper2 Main Menu: Enter command or menu > bo pri Interact with IPL (Y, N, or Cancel)?> yy Booting... Boot IO Dependent Code (IODC) revision 1 HARD Booted. MMSAVE Version 2.5 DUMPAREA found, save main memory to disc ISL loaded ISL Revision A.00.
Verifying Attached Devices Displaying Configured Devices Type HELP for command information. ODE>run mapper2 *************************************************************************** ****** ****** ****** MAPPER2 ****** ****** ****** ****** Copyright (C) 1998-2000 by Hewlett-Packard Company ****** ****** All Rights Reserved ****** ****** ****** ****** HP shall not be liable for any damages resulting from the ****** ****** use of this program. ****** ****** ****** ****** Version B.
Verifying Attached Devices Displaying Configured Devices Path Component Name Type HW SW Revisions ID Model Model Hdwr Firm ---------- ----------------------------------- ----- ----- ----- ----- ----0 IKE I/O Bus Converter 7H 803H CH 0 0 0/0 Elroy PCI Bridge DH 782H AH 0 0 0/0/0/0 Ethernet Controller 1011H 0019H 103CH 104FH 30H 0/0/1/0 Symbios SCSI Controller 1000H 000CH 0000H 0000H 02H 0/0/1/0.1.
Verifying Attached Devices Displaying Configured Devices 33 Processor 0H 5CCH 4H 0 0 36 DEW Bus Converter 7H 584H CH 0 0 37 Processor 0H 5CCH 4H 0 0 40 DEW Bus Converter 7H 584H CH 0 0 41 Processor 0H 5CCH 4H 0 0 192 Memory (2 Gbytes) 1H 90H 9H 0 0 Ext --> 0 Absent 1 Absent 2 Installed 3 Absent Slot 0a - - - - 1024M Active - - Slot 0b - - - - 1024M Active - - Slot 1a - - - - - - - - Slot 1b - - - - - - - - Slot 2a - - - -
Adding Peripherals to a System F Adding Peripherals to a System Before a device can be used on your system you must define a pathway, consisting of various interface components, from the system to the device. Each pathway component, and the device itself, is defined (or configured) by specifying the IO Configurator APATH or ADEV command, the component’s address, and the component's identifier. This section also provides a procedure for configuring additional other devices.
Adding Peripherals to a System N-Class and A-Class Systems N-Class and A-Class Systems These systems an address consisting of the bus converter number, the device adapter number, and the device address, and some SCSI devices are supported.
Adding Peripherals to a System Adding a Peripheral to Any System Adding a Peripheral to Any System Adding a disk drive, tape drive, or printer to a system’s configuration includes the following steps: • Enter SYSGEN • View the system’s current configuration • Activate the IO configurator • Make the necessary I/O configuration changes • Hold the changes • Save the changes • Verify the accuracy of the new configuration 1. Activate SYSGEN’s global module.
Adding Peripherals to a System Adding a Peripheral to Any System sysgen> io ** IO configurator commands ** aclass (ac) adev (ad) apath (ap) avol (av) dclass (dc) ddev (dd) dpath (dp) dvol (dv) lclass (lc) ldev (ld) lpath (lp) lvol (lv) maddress(ma) mclass (mc) mdev (md) mpath (mp) clear (cl)(c) exit (ex)(e) help (he)(h) hold (ho) oclose (oc) redo mvol (mv) io> 4. Obtain I/O configuration listings.
Adding Peripherals to a System Adding a Peripheral to Any System Use the ADEV command to add the device, including the device address, to the path specified with the APATH command. Enter: io> adev 14 1/0/0/0.6.0 ST39103LC class=(DISC,SPOOL) Refer to Chapter 5, “Modifying Input/Output (I/O) Configurations,” for additional information on using the ADEV command. 9. Hold all changes.
Adding Peripherals to a System Adding a Peripheral to Any System 214 Appendix F
UPS and UPS Monitor/iX Software Advanced UPS Monitor/IX Features G UPS and UPS Monitor/iX Software A new method of power failure protection was implemented as of MPE/iX Release 5.0. Instead of battery backup units, they have one or more PowerTrust UPS (Uninterruptible Power Supply) devices. Like the battery backup method of power failure, the UPS devices protect the HP e3000 system against the loss of work in progress in cases of utility AC power failures of up to fifteen minutes in duration.
UPS and UPS Monitor/iX Software Configuring a UPS Device Configuring a UPS Device You use one of two configuration methods to add UPS devices to a Series 9X8, 9X9, N-Class or A-Class systems. For the first or only UPS, which is attached to the third serial port on the system’s LAN/Console I/O interface card, you use NMMGR to set the data preconfigured in the default configuration group supplied with the FOS tape. You perform this procedure once, immediately after you install a new system.
UPS and UPS Monitor/iX Software Configuring a UPS Device a. At the MPE prompt, start the sysgen program. Enter: :SYSGEN CONFIG b. Go into the IO menu and use the list device (LD) command to determine if the UPS device is configured. Go go step c if the device does not exist or step d if it does exist but parameters are incorrect. io> ld 22 LDEV: 22 DEVNAME: ID: C1099A PATH: 0/0/4/1.
UPS and UPS Monitor/iX Software Configuring a UPS Device g. Save this Sysgen configuration: io> ho io> ex sysgen> keep keeping to group CONFIG.SYS Purge old configuration (yes/no)?yes ** configuration files successfully saved ** sysgen> ex 3. Configure the UPS port parameters in NMMGR a. At the MPE prompt, start the NMMGR program. Enter: :RUN NMMGR.PUB.SYS b. Press the Open Config softkey. If the file doesn’t exist, NMMGR will report that the NMCONFIG file doesn’t exist.
UPS and UPS Monitor/iX Software Configuring a UPS Device :RUN NMMGR.PUB.SYS 2. Press the Open Config softkey twice and wait while NMMGR opens a configuration file. 3. Press DTS to enter the DTS configurator. 4. Press Go to DTC and choose the appropriate DTC configurator for the system (DTC16ix, DTC16MX, DTC16, DTC48, etc.). 5. Choose an available LDEV number for the UPS you are configuring, and determine which DTC port (DTC card number and port number) the UPS is connected to. 6.
UPS and UPS Monitor/iX Software Configuring a UPS Device System Behavior When AC Power Fails Whenever input AC power to any UPS device fails, the UPS hardware switches to internal battery operation to continue to deliver output AC power to the computer equipment. No actual power failure occurs at the computer equipment itself and, as a result, the SPU continues to operate. However, the actual behavior of the system will vary depending on how much of the system equipment is provided with UPS power.
UPS and UPS Monitor/iX Software Configuring a UPS Device To Enable Logging of UPS Activity The UPS Monitor/iX program posts UPS status and alarm messages to the system log files. If system logging for the UPS Monitor/iX (which is event number 148) is turned on, you can review the messages to troubleshoot your system configuration and evaluate system performance. As the default, event 148 is ON. To verify that it is or, if necessary, to turn it on, do the following: 1.
UPS and UPS Monitor/iX Software Configuring a UPS Device Chdir Process Adoption File Owner Change 161 162 163 OFF OFF OFF log> To Review UPS Activity Recorded in the System Log File UPS Monitor/iX status and alarm messages are recorded in the system log files as event number 148. You can use the LOGTOOL utility to review entries in the system log file about the performance and condition of UPS devices on your system. To do so, follow these steps: 1.
Using the Guardian Service Processor (GSP) H Using the Guardian Service Processor (GSP) This section describes the Guardian Service Processor (GSP) commands and functions. The Guardian Service Processor is an independent support processor built into the N and A class Core I/O card for the system console that provides some major system manageability features • Always-on capability: The GSP is alive if the power cord is plugged in.
Using the Guardian Service Processor (GSP) GSP Modes GSP Modes When first logging on, the user is part of the mirrored GSP session. The mirrored GSP session has three major modes: • GSP Command Mode: This is the mode that is active when you enter [ctrl]-B. It is where you enter the GSP commands. • Console Mode: This mode is active when you enter the GSP CO command. If the OS is booted you will have access to the MPE Command Interpreter.
Using the Guardian Service Processor (GSP) GSP Modes Entering GSP Command Mode When the console is in GSP Command mode you have access to the GSP commands and functions. Command mode is activated when you enter [ctrl] B at the system console or it can be activated when you access the system via the remote console port or via a connection to the GSP LAN Console port.
Using the Guardian Service Processor (GSP) GSP Modes ==== GSP Help ============================================(Administrator)=== AC :Alert display Configuration PC :Remote Power Control AR :Automatic System Restart config. PG :PaGing parameter setup CA :Configure asynch/serial ports PS :Power management module Status CL :Console Log- view console history RS :Reset System through RST signal CO :COnsole- return to console mode SDM:Set Display Mode (hex or text) CSP:Connect to remote Service Proc.
Using the Guardian Service Processor (GSP) GSP Modes [Read only - use ^Ecf for console write access.
Using the Guardian Service Processor (GSP) Configuring the GSP Configuring the GSP The GSP has several features that must be configured in order for them the be available. The following sections give a description of each feature and the command used to configure that feature. See the online help for details about the options that are available. The GSP configurations require you to enter commands in a dialog format. Pay close attention to the prompts.
Using the Guardian Service Processor (GSP) Configuring the GSP Remote Console Serial Port Modem Flow Control: Software Remote Console Serial Port Modem Transmit Configuration Strings: Enabled Remote Console Serial Port Modem Presence: always connected Do you want to modify the Local Console Serial Port settings? (Y/[N]) n n Do you want to modify the Remote Console Serial Port Modem settings? (Y/[N]) n n GSP Host Name: GSP> The ER Command is used to enable or disable remote serial port modem acc
Using the Guardian Service Processor (GSP) Configuring the GSP NOTE The configuration for the Hp e3000 PA-8700 N-Class and A-Class servers uses the hardware path of 0/0/4/1.1 3. Run NMMGR. Press the following function keys: F1 [Open Config], F1 [DTS], F4 [Go to UserPort]. Verify the settings are as follows (same for both theA-Class and N-Class): Logical Device Line Speed Modem Type Parity [21 ] [9600] [1] [NONE] Make sure the the upper right corner of the screen is ’Data: Y’.
Using the Guardian Service Processor (GSP) Configuring the GSP There is always one user listed for the local serial port. This is a default user name ("local user") if the local console client user didn’t originate the GSP Command Interface session. If the local console operator typed CTRL-B, then the login name that the local operator typed is displayed instead. SEE ALSO: TE (TEll) Security Options & access control (SO) This command is used to modify the security parameters of the GSP.
Using the Guardian Service Processor (GSP) Configuring the GSP When the command is initiated, the LAN and modem connections will be dropped. The XU command can only be run from the local port. If the upgrade is successful, the GSP will reboot and come up using the new software. If the upgrade fails, the GSP will return to the prompt with instructions on what went wrong, and what to do next.
Using the Guardian Service Processor (GSP) Accessing the Secure Web Console Accessing the Secure Web Console The Secure Web Console (SWC) is built into the GSP processor on the PA-8700 N-Class and A-Class servers. The SWC can be used with either Microsoft Internet Explorer or Netscape Internet browsers. Once the GSP LAN console access has been configured with the LC command, the SWC access can be enabled with the GSP EL command.
Using the Guardian Service Processor (GSP) Accessing the Secure Web Console 234 Appendix H
Glossary automatic restart Glossary abort A procedure that terminates a program or session if an irrecoverable error, mistake, or malfunction occurs. access The process of obtaining data from files or acquiring the use of a device. Access implies an input/output (I/O) operation, and is used as a synonym for I/O.
Glossary backup backup The process that duplicates computer data to offline media, such as magnetic tape. Backups protect data if a system problem should occur. channel I/O bus (CIB) A device that provides a synchronous bi-directional data path between the central bus (CTB) and I/O devices. batch access capability (BA Capability) A default capability assigned to accounts and users that allows users to submit batch jobs.
Glossary device class customers to move applications and data to the 900 Series HP 3000 system without changes or recompilation. CPU time The amount of time, in seconds, that a user, group, or account has used the CPU. It can be displayed by executing the MPE REPORT command. configuration 1) The way in which computer and peripheral devices are programmed to interact with each other. 2) The layout of the computer system, including MPE table, memory, and buffer sizes.
Glossary device file device file A file associated with a non shareable device (a spool file). Input and output spool files are identified by a number in the DFID (device file identification) column of the SHOWIN and SHOWOUT command displays. A device file can also refer to any non-disk device, such as $STDIN and $STDLIST, the default input and output device files for a terminal.
Glossary help facility extent A group of one or more contiguous sectors on a volume used to allocate permanent disk space. Extents can be variable length; any number of extents can exist for a given file. file A group of related records that represents ASCII text (text files) or binary data (such as executable code). Every file must have a file name so the user can access the file’s contents. file code A four-digit integer that identifies the special function of a file.
Glossary Hewlett-Packard Data-Link Control II (HP-DLC-II) Hewlett-Packard Data-Link Control II (HP-DLC-II) A standard that defines the elements and procedures for a balanced, bit-oriented, Level II protocol of the Open Systems Interconnection (OSI) model. Hewlett-Packard Graphics Language (HP-GL) The graphics instruction set for Hewlett-Packard film recorders and plotters.
Glossary logoff I/O dependent code (IODC) The portion of the operating system software that contains I/O module dependent data and code used by Processor Dependent Code (PDC) in configuring the I/O module and in booting the system. I/O path The address of the interface hardware and the physical path to reach a device. It is constructed top down from where the device is physically attached to the system.
Glossary logon logon A method of initiating a session. To log on to MPE/iX, enter the HELLO command and a valid user and account name, plus a group name if necessary, and any required passwords. logon group The group specified when logging on using the HELLO command. The syntax is username.accountname, groupname. Once the desired group is accessed, resident files can be referred to without fully qualifying them. logon identity A security device used to verify users to the system.
Glossary priority request non-shareable device capability (ND capability) A capability assigned to accounts and users allowing account members to own non-shareable devices such as unspooled tape drives and line printers, serial disks, private volumes (on MPE V/E), and foreign disks. nonsystem volumes Volumes that are member volumes of a volume set. They do not need to be mounted for the operating system to run. operating system The software that allows the computer to operate.
Glossary private volumes private volumes MPE V/E removable disk volumes that are not included in the system I/O configuration table and, therefore, must be brought online with an explicit LMOUNT command. To access a private volume, a user’s logon group and account must be assigned to a specific volume set with the VS parameter of the ALTGROUP and ALTACCT commands. Private volumes are nonsystem domain devices. Equivalent to MPE/iX mountable or nonsystem volumes.
Glossary spooling required parameter A parameter that is required when entering a command or calling an intrinsic. In reference manuals, required parameters are surrounded by braces ({}). resource Any device or item used by a computer, for example I/O devices, disk files, or programs. resource identification number (RIN) A number identifying a user-defined resource.
Glossary spool queue nonshareable device, such as a tape drive or line printer, their output is directed to spool files on disk. The output is printed on a priority basis as the printer becomes available and the users can proceed with other processing activities without waiting for the printer. Multiple batch jobs can also be submitted concurrently. The jobs are spooled to disk and executed according to the priority level specified by its submitter with the JOB command.
Glossary terminal type system disk The disk volume mounted as logical device 1. It contains MPE, I/O configuration information, the account structure and file directory, and utilities and subsystems. It also contains an area reserved for virtual memory and can be used to store user files. system domain An MPE V/E configuration for disk drives. System domain disks contain only shareable files, and remain online until the system is shut down.
Glossary throughput throughput A measurement of a computer system’s speed and productivity. transaction A logical unit of work. transaction logging A method of tracking each unit of work to facilitate recovery from the abnormal end of transaction processing and system failures. A transaction log file is automatically generated and maintained by the transaction management facility. Files can be restored to a consistent state by copying the contents of the log file into the data file.
Glossary write-protect volume set information table (VSIT) A part of a master volume of a volume set containing the volume set configuration data. volume testing The verification that the system continues to operate when loaded to each limit, the determination of what occurs when those limits are exceeded, and the determination of what occurs when the system is emptied after being in a full state.
Glossary volume set information table (VSIT) 250 Glossary
Index Symbols $STDINX formal file designator, 90 $STDLIST formal file designator, 90 A AAUTO SYSFILE configurator command, 158 ABOOT SYSFILE configurator command, 158, 159 ABORTJOB MPE/iX command, 204 access port configuring, 176 access port (AP), 20 support interface, 20 testing, 181 using, 173 access port commands, 175 RS, 20 TC, 20 Using, 175 access port(AP) using, 20 account SYS, 89 accounts used to store configuration data, 89 ACLASS I/O Configurator command, 115 A-Class default configuration, 197 ACMS
Index LOG configurator command, 129 MISC configurator command, 149 SYSGEN command, 89, 101 clearing configuration changes, 129, 149 SYSGEN utility, 101 CMSL, 158 adding a segment to, 160 replacing a segment of, 163 see compatibility mode segment library, 158 codes for ISL utility names, 196 command interpreter using, 174 command syntax SYSGEN utility, 95 commands I/O configurator, 112 commands - I/O Configurator ACLASS, 115 ADEV, 115 APATH, 115 AVOL, 115 DCLASS, 117 DDEV, 117 DPATH, 117 DVOL, 117 MADDRESS,
Index TC, 20 compatibility mode segment library, 158 see CMSL, 158 CONFIG UPDATE option, 71 CONFIG group, 89 CONFIG.
Index I/O Configurator command, 117 DRIN MISC configurator command, 141 DSPROG SYSFILE configurator command, 160, 161 DUMP, 20 dump listing, 187 DUMP sequence, 188 DUMP utility, 55, 78 default options, 78 SUBSET option, 78 DUMPAREA, 46 dumping a system, 55 DVOL I/O Configurator command, 117 E enabling and disabling the autoboot flag, 50 enabling and disabling the autosearch flag, 50 entering an MPE command from the LOG configurator, 130 entering an MPE command from the MISC configurator, 151 entering ODE, 2
Index I/O path alternate boot path, 27 console boot path, 27 definition, 27 primary boot paths, 27 I/O paths determining, 110 identify test, 203 informational messages, 184 initial program load (IPL), 19, 28 initial system loader, 19, 90 input/output (I/O) configurator, 109, 110 input/output (IO) configurator, 89 input/output dependent code (IODC), 19, 29, 45 INSTALL, 20 ISL utility, 199 using to recover system, 74 INSTALL options, 75 INSTALL utility, 55, 74, 197 installing the operating system, 74 prelimin
Index load listing, 187 loading a system, 55 local devices configuring, 109 LOG SYSGEN command, 126 LOG configurator, 125 entering an MPE command from, 130 exiting, 130 HELP facility, 126 see logging configurator, 125 LOG configurator commands CLEAR, 129 EXIT, 130 HELP, 126 HOLD, 129 OCLOSE, 127 SHOW, 127 SLOG, 128 ULOG, 129 LOG values showing, 127 logging system, 125 user, 125 logging (LOG) configurator, 89, 125 see LOG configurator, 89, 125 logical interchange format (LIF), 29 logical interface format (LI
Index IO configurator command, 212 LOG configurator command, 127 MISC configurator command, 143 SYSGEN command, 99, 102 ODE exiting, 208 ISL command, 204 ODE utility activating, 203 Online device configuration, 119 P path information stable storage, 50 PDC, 203 PDC See processor dependent code, 19 peripheral devices defined, 17 permanent configuration files, 89 PERMYES SYSGEN command, 96 PERMYES in batch mode, 106 PERMYES in command files, 106 positional parameters SYSGEN utility, 95 primary boot paths, 110
Index default configuration, 197 Series 960 default configuration, 197 Series 980 default configuration, 197 Series 990 default configuration, 197 Series 991 default configuration, 197 Series 992 default configuration, 197 Series 995 default configuration, 197 Series 9X7 default configuration, 197 SESSION MISC configurator command, 146 sessions setting related limits, 146 setting resource allocations, 144 setting session related limits, 146 setting sizes of native mode and compatibility mode stacks, 147 set
Index HOLD, 101 IO, 211 KEEP, 89, 101, 129, 150, 211, 213 LOG, 126 MISC, 134 OCLOSE, 99, 102 PERMYES, 96 SHOW, 99 SYSFILE, 154 TAPE, 102, 213 SYSGEN global module help facility, 92 SYSGEN tape deleting compatibility mode segments from, 161 deleting objects from, 160 placing objects on, 162 removing system programs from, 161 SYSGEN Utility command syntax, 95 SYSGEN utility, 17, 200 activating, 90, 105 activating the configurators, 100 clearing configuration changes, 101 confirming serious actions, 96 display
Index SYSGEN, activating, 90, 105 SYSGEN, global module, 89 utilities - ISL INSTALL, 199 IOMAP, 203 START, 89 UPDATE, 199 utilities - MPE XL SYSGEN, 200 V verifying attached devices, 203 W WARN MPE/iX command, 204 WARN command, 171 WELCOME command, 170 260
