900 Series HP 3000 Computer Systems System Startup, Configuration, and Shutdown Reference Manual ABCDE HP Part No. 32650-90042 Printed in U.S.A.
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 tness 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.
Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions.
iv
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 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX.
Chapter 9 Halting System Activity describes how to shut down the system. Appendix A Using the Access Port (AP) explains how to enable a remote console and con gure a remote modem port for system support. Appendix B Startup, Dump, and Shutdown Listings lists the console messages you will see during a successful startup, load, dump and shutdown of the system.
Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase.
Conventions (continued) [ ... ] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...
Contents 1. Introduction What Is System Startup? . . . . . . . How system startup is carried out . . What Is System Con guration? . . . . How System Con guration Is Performed What Is System Shutdown? . . . . . . How system shutdown is carried out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Initiating System Activity Resetting the System . . . . . . . . . . . . . . Soft Reset . . . . . . . . . . . . . . . . . . Hard Reset . . . . . . . . . . . . . . . . .
ISL Boot Utilities . . . . . . . . . . . . . . . Starting the System . . . . . . . . . . . . . . Using START and its options . . . . . . . . . Executing commands during system startup . . . Starting a 900 Series HP 3000 . . . . . . . . . Updating the Operating System . . . . . . . . . The ISL utility . . . . . . . . . . . . . . . . Scheduling a System Update . . . . . . . . . . Using the UPDATE utility and options . . . . . Updating the operating system: a preview . . . .
5. Modifying Input/Output (I/O) Con gurations I/O Paths . . . . . . . . . . . . . . . . . . . I/O paths used to boot a system . . . . . . . . Selecting I/O paths . . . . . . . . . . . . . . Series 922 through Series 949 systems . . . . . Series 950 through Series 980 systems . . . . . Adapting systems for ber optic data links . . Using the SYSGEN I/O Con gurator . . . . . . . Getting help with I/O Con gurator commands . . Using I/O Con gurator commands . . . . . . . Viewing the current con guration . . . .
7. Modifying Miscellaneous Con guration Elements Entering the MISC Con gurator . . . . . . . . . Using the MISC Con gurator Help Facility . . . . Showing Values of Current Con gurable Items . . . Deleting Global Resource Identi cation Numbers (RIN) Con guring Job-Related Limits . . . . . . . . . Displaying Allocated Global RINs . . . . . . . . Setting Resource Allocations . . . . . . . . . . . Setting Session-Related Limits . . . . . . . . . . Setting Sizes of Native Mode and Compatibility Mode Stacks . . .
9. Halting System Activity Including Shutdown Information in the Welcome Message . . . . . . . . . . . . . . . . . . Telling Users about the Shutdown . . . . . . . . Limiting System Use . . . . . . . . . . . . . . Shutting the Spool Queues and Handling the Remaining Reports . . . . . . . . . . . . . Warning Users Two Minutes Before Shutting Down the System . . . . . . . . . . . . . . . . . . . Closing Any Open Communication Lines . . . . . Shutting Down the System . . . . . . . . . . . A.
B. Startup, Dump, and Shutdown Listings START Sequence . . . . . . . . . . . . . . . . DUMP Sequence . . . . . . . . . . . . . . . . Shutdown Sequence . . . . . . . . . . . . . . . B-1 B-6 B-9 C. Reading Stable Storage and Nonvolatile Memory Reading Stable Storage Contents . . . . . . . . . Reading Nonvolatile Memory (NVM) . . . . . . . C-1 C-3 D. Default Con gurations Used by INSTALL and UPDATE Copying Default Con guration File Groups . . . . D-3 Overview . . . . . . . . . . . . . . . . . .
G. UPS and UPS Monitor/iX Software Con guring a UPS device . . . . . . . . . . . . To con gure the rst UPS on a Series 9X8 . . . . To con gure a UPS connected via a DTC port . . To use UPS Monitor/iX software . . . . . . . . System behavior when AC power fails . . . . . . System Behavior When AC Power Returns . . . To enable logging of UPS activity . . . . . . . To review UPS activity recorded in the system log le . . . . . . . . . . . . . . . . . . .
Figures 2-1. Location of Series 922 through Series 949 Systems Reset Switch . . . . . . . . . . . . . . . 2-2. Location of Series 950 through Series 980 Systems Reset Button . . . . . . . . . . . . . . . 2-3. Series 922 through Series 935 I/O Device Paths . 2-4. Series 950 through Series 980 I/O Device Paths . C-1. Stable Storage Contents . . . . . . . . . . . . C-2. NVM Contents . . . . . . . . . . . . . . . . 2-5 2-6 2-9 2-10 C-2 C-4 Tables 2-1. 3-1. 3-2. 3-3. 3-4. 3-5. 4-1. 4-2. 4-3. 5-1. 5-2. 5-3.
1 Introduction This chapter de nes system startup, system con guration, and system shutdown. It also brie y describes the procedures for starting, con guring, and shutting down a 900 Series HP 3000 computer system. The details for these procedures are discussed throughout the following chapters. What Is System Startup? How system startup is carried out System startup refers to the procedure for starting the computer software, namely the operating system, and other programs.
Note If you are installing the operating system for the rst time, or if you are updating your current system, please follow the instructions in the HP 3000 MPE/iX Installation, Update, and Add-On Manual (36123-90001). This manual is packaged with the FOS and system load tape (SLT) that you receive from Hewlett-Packard. There are two booting sequences available for the 900 Series HP 3000: autoboot and interactive.
Note What Is System Shutdown? How system shutdown is carried out SYSGEN does not support con guring terminals into the system. For information on terminal con guration, refer to the HP 3000/iX Network Planning and Con guration Guide (36922-61023). 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 o power to the computer hardware.
2 Initiating System Activity Separate rmware 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 rst software retrieved from the boot device, implements the operating-system-independent portion of the bootstrap process.
switch on the Series 922 through Series 949 systems, shown in gure 2-1, initiates a soft reset.) More information on issuing resets from the console is provided later in this chapter. Resetting the system using the console The console interfaces with the 900 Series HP 3000 through the access port (AP) located in the channel I/O (CIO) section of the system card cage.
To reset the system using the access port (AP), follow the directions listed below: 1. Place the console in control mode by entering 4CTRL5 4B5 at the system prompt. d c The console responds by displaying the control mode prompt (CM>) and activating the system status line at the bottom of the screen: CM> . . . Code: F1FF REMOTE: disabled inactive multiple ACCESS FAULT:00 a b 2. Issue the reset command.
d CM> TC a Processor Dependent Code (PDC) revision 2.2 Console Path = 4.2.0.0.0.0.0 Primary boot path = 4.1.0.0.0.0.0 Alternate boot path = 4.5.0.0.0.0.0 c Boot from primary boot path (Y or N)?> Example 2-1. Resetting Series 949 System Using AP Commands: Autoboot & Disabled b Answering NO to the boot path prompt initiates other prompts that query for the proper path to the boot device.
If you do not press a key to interrupt the sequence, the system displays messages as it automatically boots the processor and operating system. The autoboot ag setting determines whether the system searches for an autoexecute le with which to boot the operating system automatically. Note Resetting the system with the front panel switches If an autobooting system cannot locate a valid autoexecute le, it boots to ISL; therefore, you see the statement Cannot find an autoexecute file. AUTOBOOT ABORTED.
Figure 2-2. Location of Series 950 through Series 980 Systems Reset Button Caution Pressing the reset button on Series 950 through 980 systems initiates a hard reset. Hard resets are disruptive resets that terminate all I/O operations and reset system memory. For this reason, reset Series 950 through Series 980 systems with the reset button only when other attempts to clear system failures have failed or when the data in memory and I/O processes are expendable.
d Processor Dependent Code (PDC) revision 2.9 a Console Path = 4.2.0.0.0.0.0 Primary boot path = 4.1.0.0.0.0.0 Alternate boot path = 4.5.0.0.0.0.0 c Enter boot path, command, or ?> Example 2-3. Resetting a Series 949 System Using the Reset Switch & Autoboot Disabled Note b Disabling and enabling autoboot is explained in Chapter 3. Answering NO to the boot path prompt initiates other prompts that query for the proper path to the boot device.
Determining and Selecting Input and Output (I/O) Paths The system identi es 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.
Figure 2-3. Series 922 through Series 935 I/O Device Paths Series 950 through Series 980 boot paths On Series 950 through Series 980 systems, I/O path construction begins with the bus converter (BUS CONV), which connects the system's main bus (SMB) and central bus (CTB). The channel adapter connects the central bus and the channel I/O bus (CIB). The logical construction concludes with the device adapter, which connects the I/O device to the CIB.
magnetic tape device address is 3. This establishes an I/O path for the tape drive as 6/4.3.3.0.0.0. Figure 2-4. Series 950 through Series 980 I/O Device Paths There are several ways to determine the I/O path for devices that are attached to the system: Refer to gures 2-3 and 2-4 for address and physical connection information. Generate a list of paths for devices that have already been con gured by using the LPATH command of the SYSGEN utility IO Con gurator.
active or available. During the system boot (using the ISL START command), information on which paths have been con gured and which devices are available or not available is listed as the "System State at Boot Time." (For more information on the system state, refer to Chapter 3 and Appendix B. For more information on SYSGEN, refer to Chapter 4.) Use the ISL utility, IOMAP, to list the devices on the system. (For more information on IOMAP, refer to Appendix E.
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. For more information on proper I/O paths for startup, refer to the previous section.
d a CM> TC Processor Dependent Code (PDC) revision 3.2 Console path = 4.2.0.0.0.0.0 Primary boot path = 4.1.0.0.0.0.0 Alternate boot path = 4.5.0.0.0.0.0 Autoboot from primary boot path enabled. To override, press any key within 10 seconds. 10 seconds expired -- proceeding with autoboot. Booting from primary boot path = 4.1.0.0.0.0.0 Console IO Dependent Code (IODC) revision 4 Boot IO Dependent Code (IODC) revision 4 Soft Booted. MMSAVE Version 2.
d a CM> TC Processor Dependent Code (PDC) revision 3.2 Console path = 4.2.0.0.0.0.0 Primary boot path = 4.1.0.0.0.0.0 Alternate boot path = 4.5.0.0.0.0.0 Autoboot from primary boot path enabled. To override, press any key within 10 seconds. ** A key is pressed ** Boot from primary boot path (Y or N)?> n Boot from alternate boot path (Y or N)?> n Enter boot path, command, or ?> 4.1.0 Booting.
d Use BC/1.2.3 format for boot path. The following RESTART BOOT INFO LANG MEM_DUMP FASTBOOT TESTBOOT HELP c a commands are available: Restart the boot device selection Boot the system again (hard boot) Display boot information/warnings Select Language for boot messages Read/Write address locations Enable/Disable memory testing Enable/Disable test boot sequence Print this help list Enter boot path, command, or ?> Example 2-7.
d a CM> TC Processor Dependent Code (PDC) revision 3 Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.1.0.0.0.0.0 Alternate boot path = 6/4.3.0.0.0.0.0 Autoboot from primary boot path enabled. To override, press any key within 10 seconds. ** A key is pressed ** Boot from primary boot path (Y or N)?> n Boot from alternate boot path (Y or N)?> n Enter boot path, command, or ?> 8.2.4 Interact with IPL (Y or N)?> y Booting. Boot error on path 8.2.4.0.0.0.
Interactively booting the system with autoboot disabled Note d c 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-9 demonstrates the interactive boot sequence for a Series 922 system.
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. Bypassing the disabled autoboot setting Answering NO to the prompt Interact with IPL (Y or N)? causes the system to ignore a disabled autoboot ag setting and attempt to autoboot. Example 2-10 demonstrates bypassing a current disabled autoboot ag setting in order to autoboot. d a CM> TC Processor Dependent Code (PDC) revision 3.
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: System Startup Procedure 4CTRL54B5 Note d c If you have a 99X system, you must transfer to the service processor before you reset the system. a b CM> SP If you have a 9X8LX or 9X8RX system, a PDC screen is displayed. Type BO to boot from the primary path. d a CM> TC Processor Dependent Code (PDC) revision 3.2 Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.
Note Currently there is no autoexecute le available; therefore, you must ignore the statement Cannot find an auto-execute file. AUTOBOOT ABORTED. This does not present any problems; just continue with the START commnand in ISL. For further information about system startups, refer to Chapter 3.
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.
Using initial system loader (ISL) commands ISL commands change or display boot path information and ISL utility names. Table 3-1 lists commands that do not execute a utility function. ISL utilities and options are described later in this chapter. Table 3-1. ISL Commands. Command Meaning HELP or ? Lists ISL commands and de nitions, along with the ISL utilities available through the selected boot media. LISTF or LS Lists the ISL utilities available through the selected boot media.
Using the help facility for ISL commands d a ISL> HELP ? HELP LISTF LS AUTOBOOT AUTOSEARCH PRIMPATH ALTPATH CONSPATH DISPLAY LSAUTOFL LISTAUTOFL FASTSIZE SUPPORT SUPPORTCD READNVM READSS LSBATCH LISTBATCH BATCH LSEST LISTEST EST c Example 3-1 demonstrates using the ISL command, HELP. To display help listings for all ISL commands, enter either HELP, HE, or the symbol "?" at the ISL prompt: The display on your screen may vary depending on the model of HP 3000 you have.
d c Utilities on this system are: filename type start size created ==================================================== START -12864 992896 27208 89/11/37 10:34:44 SAT -12864 481344 25528 89/11/37 08:25:51 ISL -12864 419936 152 89/11/37 08:25:27 DISCUTIL -12864 463872 17464 89/11/37 08:25:36 DUMP -12864 963904 16424 89/11/37 09:44:12 ISL -12864 419936 152 89/11/37 08:25:27 A1002AI -12864 480256 544 89/11/28 16:21:50 A1002AM -12864 480800 408 89/11/28 16:21:51 A1002AP -12864 481216 4600 89/11/28 16:21:54 A
Listing Available ISL Utilities Example 3-2 demonstrates using the ISL LISTF 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.
Activating and Deactivating Autoboot and Autosearch Functions Enabling and disabling the autoboot and autosearch ags determines one of four boot device and console selections for system initialization. Hardware interprets the selections as follows: Manual (autoboot o and autosearch o ). Ask for the path to the boot device. Use the path that is indicated. Initialize the path given, and boot from it. Bootsearch (autoboot o and autosearch on). Search for a boot device.
Autosearch is OFF (disabled). For more information on the autoboot and autosearch ags, refer to Appendix C. Modifying boot paths in stable storage Caution The ISL commands PRIMPATH, ALTPATH, and CONSPATH are available for placing new primary boot path, alternate boot path, or console boot path information in stable storage. The changes need to be in stable storage to execute the autoboot sequence properly in the event of a power outage or other serious failure.
Displaying current boot path, autoboot, and autosearch settings Since an improper path keeps the system from booting, use the DISPLAY command to check the paths entered. Double check these entries against a recent I/O map from the ISL IOMAP utility or a con guration listing from the SYSGEN utility. For more information on SYSGEN, refer to Chapter 4.
ISL> FASTSIZE F If you changed the value of fastsize, you must reset the system for the new value to take e ect. For more information on resetting the system, refer to Chapter 2. Listing autoboot file contents To list the contents of the current autoboot le, enter either LISTAUTOFL or LSAUTOFL at the ISL prompt: ISL> LISTAUTOFL Reading Nonvolatile Memory (NVM) Nonvolatile memory stores system activity parameters, including a circular queue of the last six ISL utilities executed.
The hardware clock should be set to GMT if the clock displays are to be correct on the booted system. The hardware clock provides the basis for time displays that are part of some ISL utilities. When the local time is entered during particular ISL utilities, the system computes an o set and stores it in stable storage. During a boot, the GMT and this o set are combined to produce the local time, displayed on the console.
Pressing 4Return5 at the enter command prompt returns you to the ISL prompt. 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, SAT, CAEXR, and IOMAP. The START utility starts the system from disk.
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 di ers depending on the previously executed boot command.
Note bootup contains the CONFIG le that was used by the previous START NORECOVERY command. RECOVERY starts the system, but sets the fence at 14 which prevents any jobs or sessions from automatically starting. These default options instruct the system to boot from disk, to use the con guration information last used to boot the system, attempts to log on as OPERATOR.
ACCEPT ALLOCATE ALLOW ALTLOG COMMENT CONSOLE DEALLOCATE DISALLOW DISCRPS DOWN DOWNLOAD HEADOFF HEADON JOBFENCE JOBPRI JOBSECURITY LDISMOUNT LIMIT LMOUNT LOG MRJECONTROL OUTFENCE REFUSE STARTSESS STARTSPOOL STOPSPOOL STREAM STREAMS SUSPENDSPOOL TELL TELLOP TUNE UP VMOUNT Create a SYSSTART le with any text editor. A properly formatted SYSSTART le is composed of ve modules, labeled and placed in the following order: startup, warmstart, coolstart, update, and reload.
d c a STARTUP STREAMS 10 ALLOW @.@;COMMANDS=REPLY 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.
The STARTUP module is executed whenever the SYSSTART le is accessed. Place commands and parameters speci c to an operation under the appropriate heading. If, for instance, you do not wish users to be able to log on immediately following an UPDATE (START) or INSTALL (START), insert commands in the update and install modules to limit the jobs and sessions and raise the jobfence. Table 3-2 describes how each module is executed. Table 3-2.
Note d c CM> SP If you have a 99X system, you must transfer to the service processor before you reset the system. a b Examples 3-5 and 3-6 demonstrate the messages received at the console of the 900 Series systems. Note The components of the system startup messages on all of the systems are similar; however, the messages can vary in I/O path descriptions depending on the system.
d a CM> RS 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 SPU hardware was successfully reset. (APMSG 02) Processor Dependent Code (PDC) revision 3.2 Console path = 4.2.0.0.0.0.0 Primary boot path = 4.1.0.0.0.0.0 Alternate boot path = 4.5.3.0.0.0.0 Enter boot path, command, or ?> 4.1 Booting.
d a 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. Vsm make no longer resident completed. Initialize process management completed. Initialize debug subsystem completed. Initialize file system completed. Initialize temporary UID/GID Databases completed. Initialize non-resident services completed.
d a SYSTEM I/O AT BOOT TIME ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: 1 2 3 4 5 6 7 10 19 20 28 29 HP7937H HP7937H HP7937H HP7937H HP7937H HP2566A HP7980A HP7980A HP2680A HP2392A HP2688A HP2688A configured configured configured configured configured configured configured configured configured configured configured configured available available available available not-available available available not-available not-available available not-available not-available 4.1.0 4.
d ============================================================ STARTUP startup block processing ============================================================ SESSION Scheduling Initialized ALLOW @.@;COMMANDS=LOG JOB Scheduling Initialized limit 10,60 jobfence 7 startspool lp streams 10 outfence 7 16:52/38/Output spooler, LDEV #6: The File System reported a warning while acquiring the spooled device. The spooler will continue. 16:52/38/Output spooler, LDEV #6: Started. Startup processing is complete.
d a CM> TC Processor Dependent Code (PDC) revision 3.2 Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.0.0.0.0.0.0 Alternate boot path = 6/4.3.0.0.0.0.0 32 MB of memory configured and tested. Soft Booted--memory state is valid Autoboot from primary path enabled. To override, press any key within 10 seconds. 10 seconds expired--proceeding with autoboot Console IO Dependent Code (IODC) revision 4 Boot IO Dependent Code (IODC) revision 4 Booted. MMSAVE Version 2.
d a [TMUX_DAM] 15 7 12 14 Initialize genesis completed. Create Console Messages kso completed. Initialize memory manager completed. Initialize resident kernel completed. beginning recovery setup complete - beginning recovery of free space map and label table completed recovery of free space map and label table completed recovery of files begin posting of recovered files recovery completed NEW and TEMP files deallocated for MPEXL_SYSTEM_VOLUME_SET:MEMBER1 LDEV1 Initialize volume management completed.
d The path 2/8.0.0 was configured but is The path 2/8.0.1 was configured but is The path 2/8.0.2 was configured but is The path 2/8.0.3 was configured but is The path 2/8.1.0 was configured but is The path 2/8.1.1 was configured but is The path 2/8.1.2 was configured but is The path 2/8.1.3 was configured but is The path 6/4.0.0 was configured but is The path 6/4.0.1 was configured but is The path 6/4.0.2 was configured but is The path 6/4.3.4 was configured but is The path 6/4.3.
d a Entering - Initialize system member volumes Leaving - Initialize system member volumes Entering - Mount all volumes VOLUME ALREADY MOUNTED ON LDEV 1 (AVR 10) A volume has been mounted on ldev 1 LONER VOLUME MOUNTED ON LDEV 2 (AVR 11) A volume has been mounted on ldev 2 c Warning - Volume is not available for mounting. The ldev is Warning - Volume is not available for mounting. The ldev is Warning - Volume is not available for mounting. The ldev is Warning - Volume is not available for mounting.
Updating the Operating System Caution 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 900 Series HP 3000. Speci c update and installation instructions are subject to change. This manual provides you with an overview of the procedures involved.
Scheduling a System Update If you are using the UPDATE facility as a recovery method, the opportunity to schedule your system's UPDATE is probably not available to you. Take time to thoroughly examine the UPDATE process before using it as a recovery method. Understanding the UPDATE process can reduce system operator and system manager errors and, therefore, reduce your system's downtime.
The UPDATE utility with its default options instructs the system to perform these tasks: update the existing operating system without replacing the con guration data les on disk autoboot the system from disk after the update is completed use the con guration group CONFIG.SYS attempt to log on in the user account OPERATOR.SYS (if there is no OPERATOR.SYS user, you will see the MPE prompt) bring up all volumes present on the system.
Once you are ready to begin the operating system update, the following are required steps of the process: 6. updating from the system load tape 7. restoring the FOS tape 8. restoring the SUBSYS tape 9. creating a customized system load tape 10. updating with the customized system load tape 11.
Caution Backing up the system and retaining the current configuration Do not attempt to use UPDATE to restore your system without reading the Backdating Your System appendix in HP 3000 MPE/iX Installation, Update, and Add-On Manual (36123-90001). Before updating your system, ensure that you have complete backup tapes. If up-to-date backups do not exist, reschedule the update. The backups provide a method of restoring your data if di culties arise during the update.
sector table, the disk free space map, the system directory (null directory), boot les, and all base system les. The INSTALL utility builds a null system directory that contains the account SYS. The groups CONFIG, DIAG, MPEXL, and the default con guration groups are added by the INSTALL utility later. Installing a new version of the operating system can be accomplished by the system manager, except where specially customized software is to be installed.
Note Do not use these intructions to install your system. They are an overview only, and not a complete listing of tasks. Please refer to the HP 3000 MPE/iX Installation, Update, and Add-On Manual (36123-90001) for full instructions on installing the system. The following is an overview of the steps to perform.: Install from the backup or AUTOINST-created SLT and start the system. Use VOLUTIL to initialize additional system volumes (if any). Restore the latest partial and full backup tapes.
is the same as specifying the following default options: 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 le exists, the autoboot le is enabled, and the START option is speci ed: Install the operating system, and autoboot the system from disk after the installation is completed. Use the con guration group, CONFIG.SYS.
HP 3000 MPE/iX Installation, Update, and Add-On Manual (36123-90001) MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364) Con guring Systems for Terminals, Printers, and Other Serial Devices (32022-61000) HP 3000/iX Network Planning and Con guration Guide (36922-61023) 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.
Using the DUMP utility and options The DUMP utility has one basic option, SUBSET=ALL/MEMORY. Because START/NOSTART are also options, DUMP can use several START command options: DUMP SUBSET= ALL MEMORY ;START ;NOSTART Where options are: ;RECOVERY ;NORECOVERY ;SINGLE-USER ;MULTI-USER ;SINGLE-DISC ;MULTI-DISC ;SYSSTART ;NOSYSSTART 2 options 3 To perform a complete memory dump, enter the DUMP command.
Caution Caution Do not issue the RS command from the console or push the RESET button on the front panel. Hard resetting the system initiates a destructive processor self-test that invalidates dump data. There will be a one- to two-second delay between typing TC and getting the message Processor Dependent Code (PDC) revision X.X. During this time no keys should be pressed on the console.
d a CM> TC Processor Dependent Code (PDC) revision 3.2 Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.0.0.0.0.0.0 Alternate boot path = 6/4.3.0.0.0.0.0 32 MB of memory configured and tested. Autoboot from primary boot path enabled. To override, press any key within 10 seconds. ** A key is pressed ** Boot from primary boot path (Y or N)?> Y Interact with IPL (Y or N)?> Y Booting. Console IO Dependent Code (IODC) revision 4 Boot IO Dependent Code (IODC) revision 4 Booted. MMSAVE Version 2.
d Initialize_genesis - Version : <<870204.1552>> WED, JUN 8, 1988, 2:30:04 PM (y/n)? a [TMUX_DAM] 15 7 12 14 Initialize memory manager completed. MPE/XL Dump Facility Version A.00.00 Determine pre-compression size of secondary storage for ldev1 (52 Megabytes of transient objects will be dumped for this device.) Determine pre-compression size of secondary storage for ldev2 6 Megabytes of transient objects will be dumped for this device Tape compression enabled.
d a Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.0.0.0.0.0.0 Alternate boot path = 6/4.3.0.0.0.0.0 32 MB of memory configured and tested. Soft Booted- -memory state is valid Autoboot from primary path enabled. To override, press any key within 10 seconds. 10 seconds expired- -proceeding with autoboot Console IO Dependent Code (IODC) revision 4 Boot IO Dependent Code (IODC) revision 4 Booted. MMSAVE Version 2.2 DUMPAREA protected, proceeding to ISL without memsave ISL loaded ISL Revision A.00.
ISL Summary There are various options available with each utility, as shown below. These options may be entered in any order and must be separated by a blank or a semicolon. Keywords must be entered as shown. 2 START ;GROUP=cgn ;SINGLE-DISC ;MULTI-DISC ;SYSSTART ;NOSYSSTART 32 ;LOGON=acct 3 ;RECOVERY ;NORECOVERY ;SINGLE-USER ;MULTI-USER When the START option of the UPDATE utility is selected, the remaining options are available.
All available options are de ned in Table 3-3. Table 3-3. Utility Options Options Functions During an UPDATE, this option speci es whether or not the con guration data les on disk (CONFIG group), are replaced by those on tape (CONFIG). If this option is not speci ed, the default is NOCONFIG. When the system is booted with NORECOVERY, the group speci ed after GROUP= is GROUP= con gname Default: GROUP = CONFIG the source of con guration information.
Table 3-4. Utility Options Options Functions During a dump, this option indicates whether the contents SUBSET = ALL or SUBSET = MEMORY of main memory alone or main memory and secondary Default: SUBSET = storage is dumped to tape for later analysis. If the subset is not speci ed, it defaults to ALL (main memory and ALL secondary storage).
Table 3-5. Summary of System Startup Functions MPE/iX Utility START or START RECOVERY START NORECOVERY UPDATE or UPDATE NOCONFIG UPDATE CONFIG INSTALL or INSTALL START INSTALL NOSTART DUMP Permanent Spool le MPE/iX Function User Files Recovery (When To Use) Yes Retained Starts system from disk. If RECOVERY is used immediately after changing system con guration, the system recovers restartable jobs by using the previous system con guration and ignores the new system con guration.
4 Using the System Generator (SYSGEN) SYSGEN is a utility used to modify the system con guration. System con guration changes are kept to disk in a con guration group or to a tape called a system load tape (SLT). The SYSGEN utility requires system supervisor (OP) capability to view system con guration and system manager (SM) capability to save changes or create an SLT. SYSGEN contains a global module and four con gurators: Input/Output (IO) Con gurator. Con gures the local devices for the target system.
The changes take e ect once the system is rebooted with START NORECOVERY. SYSGEN also provides a CLEAR command to erase changes made through one or more of the con gurators. Note Entering the SYSGEN Global Module When SYSGEN generates a boot tape, it writes the current con guration data as the group CONFIG.SYS, regardless of the group name on disk. CONFIG is the group selected by default by the START utility and used to start a system. For more information on the START utility, refer to Chapter 3.
When using parameters with the SYSGEN command, place them immediately following the command: :SYSGEN[basegroup][,newgroup][,input le] [,output le] When using parameters with RUN SYSGEN.PUB.SYS, you must specify them in the phrase INFO=" ": RUN SYSGEN.PUB.SYS;INFO= "[basegroup][,newgroup] [,input le][,output le]" d Example 4-1 illustrates activating SYSGEN's global module. Activate the SYSGEN global module by entering the command SYSGEN or by entering RUN SYSGEN.PUB.SYS. :SYSGEN a SYSGEN version C.02.
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 con gurator or at the rst-level menu. To obtain a list of the rst-level commands, enter HELP (abbreviated HE or H) at the SYSGEN prompt as shown in the following example.
d To display the syntax for each available command at the current level, enter HELP ALL as shown in the following example: sysgen>HELP ALL command (abb) ------------io misc (mi) log (lo) spu (sp) sysfile (sy) basegroup (ba) keep (ke) (k) show (sh) a parameter=value --------------- [name = groupname] [name = groupname] [type = BASEGROUP|NEWGROUP|VERSION| PERMYES|CONFIGURATOR|ALL] [dest = OFFLINE] permyes (pe) [mode = ON|OFF] tape (ta) [mode = VERBOSE|NOCHANGE|NOCONFIG|NODIAG| NOLOGNUM|LOGNUM] [dest = OFF
Using First-Level (Global Module) Commands The rst-level commands, displayed after entering SYSGEN, allow you to activate one of the four con gurators (I/O, LOG, MISC, SYSFILE) or or to keep, show, or clear changes made from the con gurators. In addition, you can use rst-level commands to call the SYSGEN help facility, alter basegroups, store con guration changes to tape, or exit the SYSGEN utility.
Table 4-1. Using First-Level Commands Command Meaning IO Activates the I/O Con gurator. For additional information on the IO command, refer to \Entering the I/O Con gurator." LOG or LO Provides access to the LOG con gurator commands. MISC or MI Provides access to the MISC con gurator commands. SPU or SP Provides access to the SPU con gurator commands SYSFILE or SY Provides access to the SYSFILE con gurator commands. BASEGROUP or BA Changes the default group after the utility is activated.
SYSGEN Command Syntax Note Commands can be classi ed as either command only or command with parameters(s). Commands with parameters can be speci ed in one of the following ways: positional parameters keyword parameters options 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.
Specifying the Base Group When altering or viewing a con guration through SYSGEN, you must rst select the con guration group for the operation. Select this basegroup by using the basegroup parameter or the BASEGROUP command. You can specify the group only from the global module in SYSGEN, but you can accomplish this in two ways.
Confirming Potentially Serious Actions SYSGEN is initially set to con rm a potentially serious action. If, for example, you make con guration changes and attempt to exit without saving the changes, SYSGEN warns you that you are about to lose your changes. You can enable PERMYES to automatically accept all decisions entered at the terminal or disable it to ask if the user wishes to change a command that seems improper. The abbreviated command for PERMYES is PE.
d a :SYSGEN SYSGEN version D.01.01 : catalog version D.01.01 TUE, SEP 14, 1993 Copyright 1987 Hewlett-Packard Co.
Example 4-5 shows how SYSGEN overrides user input with PERMYES enabled.
d a :SYSGEN SYSGEN version D.01.01 : catalog version D.01.01 TUE, SEP 14, 1993 Copyright 1987 Hewlett-Packard Co.
Enabling PERMYES saves time and e ort by answering YES to all prompting, particularly when a command input le is used or a batch job is executed. Enabling PERMYES can also allow mistakes. In the previous example, the changes are not kept because the HOLD command was not entered, and the system automatically answered YES to the (YES/NO) exit con rmation. Showing the State of Configurators The SHOW command (abbreviated SH) displays the current state of the SYSGEN global facilities.
d c sysgen>SHOW ALL base configuration group = CONFIG new configuration group = SYSGEN version D.01.01 : catalog version D.01.01 permyes is false--system will have to answer questions ** no configurators are modified** Activating the Configurators Example 4-6. Using the Global Module SHOW ALL a b The commands for entering each of the con gurators (IO, LOG, MISC, SYSFILE) are SYSGEN rst-level commands. To activate the con gurators, you must rst enter the SYSGEN Global module.
d a :SYSGEN SYSGEN version D.01.01 : catalog version D.01.00 TUE, SEP 14, 1993 Copyright 1987 Hewlett-Packard Co. All Rights Reserved.
Clearing Configuration Changes The SYSGEN global module CLEAR command (abbreviated CL) removes all temporary changes made from the four con gurators. If, for example, you make IO and SYSFILE con gurator changes and decide not to keep them, issue the global module CLEAR command to remove the changes made in both con gurators.
To keep changes to a group other than the current working con guration group, enter the KEEP command and a new group name: sysgen>KEEP NEWCONFG (Sample name only) If changes are being saved to a group that has existing con guration les, SYSGEN asks if that group should be overwritten: sysgen>KEEP FEUDAL purge old configuration (yes/no) ?NO ** configuration files not saved ** Answering NO cancels the command.
NODIAG prevents SYSGEN from dumping the diagnostic les as it makes the tape. Note Using this parameter creates a tape that does not contain a complete system. Installing from this tape may not produce a bootable system. NOLOGNUM resets the system and datacom log numbers to zero (0). LOGNUM is the default. It speci es that SYSGEN should carry forward the system and datacom log numbers and not reset to zero (0). OFFLINE directs the listing created by VERBOSE to SYSGEN's listing le, SYSGLIST.
d 2. Activate SYSGEN and access the con guration group that you want to store on the boot tape. Enter: a :SYSGEN groupname SYSGEN version D.01.01 : catalog version D.01.00 TUE, SEP 14, 1993 Copyright 1987 Hewlett-Packard Co. All Rights Reserved. ** First level command ** log (lo) misc (mi) basegroup (ba) show (sh) tape (ta) keep (ke) permyes (pe) clear (lc)(c) oclose (oc) redo sysgen> exit (ex)(e) help (he)(h) spu (sp) c io sysfile (sy) Example 4-8. Accessing a Configuration Group b 3.
6. Hold any changes made in step 6. After completing any changes, but before exiting the con gurator, enter: sysfile>HOLD 7. Exit the SYSFILE con gurator. Enter: sysfile>EXIT 8. Issue the KEEP command to store all changes to a set of permanent disk les by entering: sysgen>KEEP groupname 9. Mount a write-enabled tape on the tape drive. When you mount the tape on the tape drive, the system issues a message similar to the following: 10:15/10/Vol (unlabeled) mounted on LDEV# 7 10. Generate the tape.
Redirecting SYSGEN Input and Output By using SYSGEN's le 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 les that can operate without user intervention or interactive keyboard input. SYSGEN uses three formal le designators for input, output, and listing: SYSGIN. The formal le designator for the standard SYSGEN input le. By default, this le is set to $STDINX. SYSGOUT.
Table 4-2. Actions Performed by Command File Example Line d Action 1 Log on to the le SYSGENON as MANAGER.SYS with all accompanying system manager capabilities. 2 Activate SYSGEN and redirect input so that SYSGEN uses the le named LISTIT as the input le. 3 End the job le after SYSGEN has completed the tasks outlined by the SYSGEN command le LISTIT. Example 4-10 lists the contents of the command le (LISTIT), which, when run, prints SYSGEN information on the system printer.
When using SYSGEN in a noninteractive mode (such as a batch job or a command le), certain conditions may occur that cause SYSGEN to ask for con rmation. For example, if a KEEP is attempted on top of an already existing con guration group, SYSGEN asks for con rmation. If no con guration exists, no questions are asked. When you set up the input to SYSGEN you may not know if the question will be asked.
5 Modifying Input/Output (I/O) Configurations With the introduction of version C.55.00 of MPE/iX, there are two ways to de ne input and output devices on a system: using SYSGEN's I/O Con gurator or using the IOCONFIG utility. Both methods provide information about the input and output devices con gured on a system and let you make changes to the con guration as necessary.
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 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 .
Series 925 CIO expander) or 36 or 40 for a 949 (device adapters in Series 935 CIO expander). DA CIO section slot numbers range from 0 to 13. It is recommended you use slots 0 through 7. The address of the device itself depends on the adapter. In addition, a data communications device can have an additional logical or virtual device number in the I/O path speci cation.
Adapting systems for fiber optic data links The HP 27115A Interface Card (HP-FL) is a device adapter printed circuit assembly designed for use with HP Precision Architecture computer systems that use channel input/output (CIO). The HP-FL card provides the computer system with a high-speed serial connection to peripherals over a ber optic data link. Device-speci c data is converted to a format compatible with the CIO bus.
Using the SYSGEN I/O Configurator d To view and modify the I/O con guration from within SYSGEN, you use the I/O con gurator module. To do so, start SYSGEN and enter IO at the SYSGEN prompt. SYSGEN displays the commands available to you. To issue a command, you can enter either the full command name or the abbreviation shown in parentheses.
d a io>HELP ALL c command (abb) ------------- parameter=value --------------- aclass (ac) class ldev [mode adev (ad) ldev [path id [rsize [outdev [mode mpath (mp) path [id [pmgr [lmgr [pmgrpri [maxios = = = = = = devicepath productid] managername] managername] managerpriority] maxconcurrentchannelI/Os] mvol (mv) vname [newname [ldev [transient [permanent [vclass = = = = = = volumename newvolumename] logicaldevice#] %ofdiscfortransientobjects] %ofdiscforpermanentobjects] volumeclass] = name
To view the syntax for a speci c I/O con gurator command, enter HELP commandname at the I/O con gurator prompt. For example, to get information about the ADEV command, you would enter HELP ADEV. d a io>HELP ADEV adev (ad) c ldev path id [rsize [outdev [mode = = = = = = [class [cmode = = [pmgr = [lmgr = [pmgrpri = [mpetype = [mpesubtype= [devname = io> #/#,#,... devicepath productid recordsize] outputdevice] JOB|DATA|INTERACTIVE| DUPLICATIVE| INPUT|OUTPUT|AUTOREPLY|NLIO|NONE] classname,...
Viewing the current configuration To get information about the current con guration, either displayed on screen or printed, using the LCLASS, LDEV, LPATH, and LVOLcommands as described in the following table. Table 5-2. I/O Configurator List Commands Command De nition Examples LCLASS LCLASS DISC Lists the class name or names you specify with the command, the class modes, and the devices LCLASS (DISC,LP) associated with the classes in the I/O con guration.
Printing the configuration information You can use the OFFLINE option to send the output of the listing commands, LCLASS, LDEV, LPATH or LVOL, to the le SYSGLIST. Using OFFLINE does not immediately generate printed output. The information is sent to SYSGLIST until you either enter the OCLOSE command or exit SYSGEN. Exiting SYSGEN or using OCLOSE closes SYSGLIST and prints the le. For example, to print information about all devices with device class DISC and LP on your system, do the following: 1.
d io>LDEV LDEV: 1 DEVNAME: ID: HP7937H PATH: 4.1.0 CLASS: DISC SPOOL a OUTDEV: 0 RSIZE: 128 MPETYPE: 3 MODE: DEVTYPE: DISC MPESUBTYPE: 10 LDEV: 2 DEVNAME: ID: HP7937H PATH: 4.1.1 CLASS: DISC SPOOL OUTDEV: 0 RSIZE: 128 MPETYPE: 3 MODE: DEVTYPE: DISC MPESUBTYPE: 10 LDEV: 3 DEVNAME: ID: HP7937H PATH: 4.1.2 CLASS: DISC SPOOL OUTDEV: 0 RSIZE: 128 MPETYPE: 3 MODE: DEVTYPE: DISC MPESUBTYPE: 10 LDEV: 4 DEVNAME: ID: HP7937H PATH: 4.1.
Adding Objects in SYSGEN When you use SYSGEN to add objects to the system con guration, there are four I/O Con gurator commands available: ACLASS, ADEV, APATH and AVOL. They are de ned in the table below. For more detailed information read Performing System Manager Tasks (32650-90004). Table 5-3. I/O Configurator Add Commands Command De nition Examples ACLASS Creates a new class name and associates devices ACLASS EPOC 19 to the new class.
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 con gure UPS devices, read \Introducing the UPS and UPS Monitor/iX Software" later in this chapter. To learn how to use NMMGR to con gure other devices, read Con guring Systems for Terminals, Printers, and Other Serial Devices (32022-61000).
Deleting Objects in SYSGEN When you use SYSGEN to delete objects from the system con guration, there are four I/O Con gurator commands available to you: DCLASS, DDEV, DPATH, and DVOL. They are de ned in the table below and explained in the following sections. Table 5-5. I/O Configurator Delete Commands Command De nition Examples DCLASS Removes one or more class names from the system.
3. At the CI prompt, execute the DOIONOW command by entering: :DOIONOW 4. DOIONOW passes the LOG4ONLN le, which contains the new con guration information, to IOCONFIG, which begins making the changes. If LOG4ONLN is not found, you will see the following error message displayed on the console: NO PENDING SYSGEN CONFIG CHANGES The DOIONOW command creates a log le, ONLNOLOG.PUB.SYS, which is used to record the commands executed by IOCONFIG.
You may use IOCONFIG in one of two ways: interactively or non-interactively which is sometimes called \command mode". To use IOCONFIG interactively, you issue the IOCONFIG command, without command parameters, at the CI prompt. This starts the IOCONFIG utility, at which point you may enter any of the commands shown in the following table at the special prompt. When you are through using IOCONFIG, you must explicitly exit the utility.
Device and device class con guration with the IOCONFIG utility is just like SYSGEN's. You can list device and device class information, or add and delete a device or a device class. You can also modify an existing device class to add or delete devices in the class, or to rename the class. All commands take e ect immediately. As a side-e ect, those commands that update the con guration also update the current SYSGEN boot con guration.
To con gure a SCSI device, it must be physically connected to the speci ed path, it must be operational, and there must be a device-defaults-data entry for the product ID (which is obtained from the device during con guration). If you omit the ID parameter, the IOCONFIG utility interrogates the hardware to identify the device. It then validates the ID that it retrieves by checking it against the list of supported devices.
Adding a device class with IOCONFIG Note To create a new device class in the system, the system manager or operator uses the ADDCLASS or ACLASS command. The syntax of the ACLASS command is identical to that of ACLASS in SYSGEN. All devices that you designate as members of the class (using the LDEV parameter) must be con gured before issuing this command. With the release of version C.55.00 of MPE/iX, the maximum number of devices that you can con gure has substantially increased.
Listing one or more device classes with IOCONFIG The system manager or operator can list all device classes in the system, or one or more speci ed device classes, with their con guration information using the LISTCLASS or LCLASS command. When no parameter is used with this command, all device classes currently con gured in the system are listed. By providing the names of those device classes with the CLASS keyword, you can view information about particular device classes.
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 speci ed path in the active con guration. The command lists the con gured I/O paths according to their paths or to their associated I/O manager.
6 Modifying Logging Configurations The LOG con gurator 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 modi cations to databases and other les used in applications programs.
The help facility enables you to quickly identify the function and syntax of those LOG con gurator commands and options for performing the multiple operations that de ne or change logging processes.
Entering HELP commandname provides help for a speci c command: log>HELP SHOW show (sh) [command [dest = SLOG|ULOG|ALL] = OFFLINE] Showing Current The SHOW command displays the LOG values as currently set. LOG Values 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 con gured.
d c log>SHOW ALL configurable item ----------------# of user logging processes # users per logging process a max ------128 1024 system log events event # ----------------------System Logging 100 System Up 101 Job Initiation 102 Job Termination 103 Process Termination 104 NM File Close 105 System Shutdown 106 Power Failure 107 I/O Error 111 Physical Mount/Dismount 112 Logical Mount/Dismount 113 Tape Label 114 Console Log 115 Program File Event 116 Native Mode Spooling 120 Chdir 127 Process Adoption 128 F
Logging System Events System logging records the use of certain resources by accounts, groups, and users. System logging can be used for several purposes, such as billing or obtaining an overview of system use. System logging describes system use by creating a running log of actual events, correlating the event with a job and session. The system manager chooses which events to enable or disable by setting an event number to ON or OFF.
Logging User Events User logging provides a means for system users and subsystems to record additions and modi cations to databases and other les using application programs. The system manager determines the maximum number of logging processes and the maximum number of users per logging process. The ULOG command con gures the user logging process parameters.
Holding and Saving Configuration Changes Using the system logging and user logging commands described in the following sections changes the LOG con guration speci ed in the SYSGEN command line or global BASEGROUP command. These changes are temporary and are easily lost if not properly saved. Saving con guration changes is a two-step procedure. After you alter a con guration, you must, rst, hold the changes before exiting the con gurator. Second, use the global module KEEP command to save the changes.
Exiting the LOG Configurator Use the EXIT command to terminate the LOG con gurator and return to the SYSGEN global module. Exit may be abbreviated EX or E. To end working in the LOG con gurator, enter EXIT at the LOG con gurator prompt: log>EXIT sysgen> Printing a Log File To analyze your logs and to read what you are logging, you must print your log les. To do this, use the LOGTOOL utility program. The LOGTOOL utility runs under the online diagnostic system, and can be invoked by entering SYSDIAG.
Printing a subset of a log file If you like, you can lter the output of LOGTOOL utility to show you information about only a speci c user or users. The syntax for this is shown below. 2 LIST 8 3 ;JSNAME=job/session name 2 5 ... LOG=log name 4 ;USER=user name ;ACCOUNT=account name 9 3 The input for these commands should be no longer than 80 characters. Default for all parameters is the wildcard @.
7 Modifying Miscellaneous Configuration Elements The MISC con gurator provides commands to con gure various types of le information di cult to categorize elsewhere. The MISC con gurator handles changes to job-related and session-related items, processes, system resource allocations, spool parameters, stack and heap sizes, and miscellaneous system information. Entering the MISC Configurator To access the MISC con gurator, enter the MISC command (abbreviated MI) at the SYSGEN prompt.
Using the MISC Configurator Help Facility d The help facility enables you to identify quickly the function and syntax of MISC con gurator commands. To obtain a list of the commands available for use in the MISC con gurator, enter HELP at the MISC con gurator prompt. a misc>HELP ** MISC configurator commands ** c drin (dr) resource (re) system (sy) io session (se) clear (cl)(c) oclose (oc) misc> exit (ex)(e) redo job (jo) show(sh) help (he)(h) lrin (lr) stack (st) hold (ho) Example 7-2.
d a misc>HELP ALL c commands (abb) -------------- parameter=value --------------- drin (dr) global io (io) [maxdyninput = dynamic input devs] [maxdynoutput = dynamic output devs] [maxdynio = dynamic I/O devs] job (jo) [cputime [maxlimit [pool = second-count] = maximum job limit] = pool-size] lrin (lr) [dest = OFFLINE] resource (re) [grins [rins [iomont [maxcmcode [cmsegs [maxxdata [xdataperproc = = = = = = = global-rin-allocation] total-rin-allocation] io-monitor-table size] cm code segmen
You can request help for a speci c MISC con gurator command by entering HELP commandname at the MISC con gurator prompt: misc>HELP RESOURCE resource (re) Showing Values of Current Configurable Items [grins [rins [iomont [maxcmcode [cmsegs [maxxdata [xdataperproc = = = = = = = globalrinallocation] totalrinallocation] iomonitortablesize] cmcodesegmentsize] cmcodesegsperproc] maxsizeofxdataseg] maxdatasegsproc] The SHOW command, abbreviated SH, displays the values of the current con gurable items referenc
enter the OCLOSE command or exit the con gurator. Exiting the con gurator or using OCLOSE closes SYSGLIST and prints the le. Entering SHOW without a parameter is the same as specifying SHOW ALL, which lists all current values. To see the resources allocated through the MISC con gurator, enter SHOW or SHOW ALL at the MISC con gurator prompt.
d c a STACK command ----------------DEFAULT NM STACK MAXIMUM NM STACK DEFAULT CM STACK MAXIMUM CM STACK DEFAULT HEAP MAXIMUM NM HEAP parameter MAX --------------nm 262144 maxnm 1068498944 cm 4096 maxcm 31232 heap 524288 maxheap 524288 SYSTEM command -------------USER VERSION LOGON PROMPT CI PROMPT RELEASE ENFORCE LOGON UDCS parameter --------userversion logonprompt ciprompt MIN CURRENT ------- ------262144 262144 262144 262144 256 1200 256 31232 524288 524288 524288 524288 VALUE ----X.50.
Deleting Global Resource Identification Numbers (RIN) A resource identi cation number (RIN) identi es a user-de ned resource. A RIN allows a user to exclusively access resources including I/O devices, disk les, and programs. The DRIN command (abbreviated DR) removes allocated global resource identi cation numbers.
misc>JOB CPUTIME=500 ** Using Keyword Parameter misc>JOB 5 8 150 ** ** Using Position Parameters ** In the preceding example, the rst command sets the CPU execution time to 500 seconds. The second command sets the CPU execution time to 5 seconds, the maximum job limit to 8, and the pool size to 150. Displaying Allocated Global RINs The LRIN command (abbreviated LR) displays allocated global RINs that are currently allocated either to the console or o ine.
Setting Resource Allocations The RESOURCE command (abbreviated RE) sets system resource allocations. RESOURCE has the following parameters: RESOURCE (RE) [GRINS [RINS [IOMONT [MAXCMCODE [CMSEGS [MAXXDATA [XDATAPERPROC = = = = = = = global-rin-allocation] total-rin-allocation] io-monitor-table-size] cm code segment size] cm code segs per proc] max size of xdata seg] max data segs/proc] GRINS sets the number of global RINs to be allocated.
Note Setting Session-Related Limits misc>RESOURCE GRINS=40 ** Keyword ** misc>RE,,80 1024 ** Positional ** misc>RE 50,,80 1024 CMSEGS=50 ** Combination ** Setting IOMONT too low (below 10) prevents the system from booting. The SESSION command (abbreviated SE) con gures session-related limits and default operating points.
misc>SE 200 150,,8 misc>SE 200 10 POOL=8 Setting Sizes of Native Mode and Compatibility Mode Stacks The STACK command (abbreviated ST) con gures the default sizes of the NM and CM stacks and the heap. STACK has the following parameters: STACK (ST) [NM [MAXNM [CM [MAXCM [HEAP [MAXHEAP = = = = = = default nm stack size] max size of nm stack size] default cm stack size] max size of cm stack] default nm heap-size] max size of nm heap] NM sets the default NM stack size, which is expressed in bytes.
Table 7-4. Min. and Max. Values for STACK Parameters Parameter Setting Strings and String Parameters Minimum Maximum NM 262144 1068498944 MAXNM 262144 1068498944 CM 256 4096 MAXCM 256 31232 HEAP 524288 1068498944 MAXHEAP 524288 1068498944 The SYSTEM command (abbreviated SY) sets various strings and parameters. SYSTEM has the following parameters: SYSTEM (SY) [ [USERVERSION =] x.yy.
Note Clearing MISC Configuration Changes A changed USERVERSION, as in the previous example, is lost if the MISC con gurator information is saved to the group CONFIG.SYS. The ID information is retained if it is saved to any group other than CONFIG.SYS. To change user version, generate a system load tape (SLT) and update with it. If you desire to clear all MISC con guration changes made, enter the CLEAR command at the MISC con gurator prompt.
Entering an MPE Command from the MISC Configurator Exiting the MISC Configurator Use the colon (:) to introduce an MPE command while in the MISC con gurator. To issue an MPE command, enter the command along with the colon. For example: misc>:SHOWTIME THU, APR 20, 1989, 2:55PM misc> Use the EXIT command to terminate the MISC con gurator and return to the SYSGEN Global module. EXIT may be abbreviated EX or E.
8 Modifying System File Configurations The SYSFILE con gurator enables the system manager to change system libraries, programs, and the system message catalog. The changes are made to a list of the les. SYSFILE has many of the features of the IO con gurator that permit the user to add, delete, and replace objects through a series of related commands. Note In order for SYSFILE con gurator changes to become permanent, you must generate a boot tape.
Using the SYSFILE Configurator Help Facility d The help facility enables you to identify quickly the function and syntax of SYSFILE con gurator commands and options. The help facility operates similarly to the global help facility. Example 8-2 demonstrates using the SYSFILE con gurator's help facility to list all available SYSFILE commands.
Example 8-3 demonstrates using the SYSFILE con gurator's help facility for listing all SYSFILE commands and their syntax.
d To request help for a speci c SYSFILE con gurator command, enter HELP commandname at the SYSFILE con gurator prompt: aboot (ab) c a sysfile>HELP ABOOT sysfile> Using SYSFILE Configurator Commands image file type = boot image name = filename = DISC|TAPE|BOTH Example 8-4.
Table 8-1. SYSFILE Configurator Command Matrix ADD DELETE REPLACE AUTO BOOT IMAGE AAUTO DAUTO RAUTO BOOT IMAGE ABOOT DBOOT RBOOT CM SL ACMSL SEGMENT DCMSL RCMSL ASPROG SYSTEM PROGRAM DSPROG RSPROG SYSTEM CATALOG RCAT NETWORK CONFIG RDCC IPL IMAGE RIPL NM LIBRARY RNMLIB LIST SPECIFY LCMSL CMSL All commands have a two- or three-character abbreviation.
Displaying Current File Information The SHOW command (abbreviated SH) displays the le information currently set through SYSFILE. SHOW has the following parameters: SHOW (SH) [FILE = AUTO ] [ BOOT [ CATALOG [ CMSL [ DCC [ IPL [ NMLIB [ SPROG [ ALL [DEST = OFFLINE ] ] ] ] ] ] ] ] ] AUTO shows all the autoboot images. BOOT shows all the boot images currently con gured. CATALOG shows the system catalog in use. CMSL shows the CMSL (compatibility mode segmented library) in use.
d a sysfile>SHOW ALL DISC AUTOBOOT TAPE AUTOBOOT SYSTEM CATALOG CM SL NMCONFIG FILE NM LIB c = = = = = = 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.SYS CLKUTIL.MPEXL.SYS DISCUTIL.MPEXL.SYS SADPATCH.MPEXL.SYS SAT.MPEXL.SYS MPROC.MPEXL.SYS UNIPROC.MPEXL.SYS MDIAG.
d a SYSTEM PROGRAM -------------IFHPIBFS.PUB.SYS XL.PUB.SYS PSIMDBDL.DIAG.SYS PSINIODL.DIAG.SYS SYSDIAG.PUB.SYS . . DTCSWI04.PUB.SYS DTCSWJ04.PUB.SYS DTCSWK04.PUB.SYS DTCSWL04.PUB.SYS DTCSWM04.PUB.SYS c FILENAME -------IFHPIBFS.PUB.SYS XL.PUB.SYS PSIMDBDL.DIAG.SYS PSINIODL.DIAG.SYS SYSDIAG.PUB.SYS . . DTCSWI04.PUB.SYS DTCSWJ04.PUB.SYS DTCSWK04.PUB.SYS DTCSWL04.PUB.SYS DTCSWM04.PUB.SYS TYPE ---system system system system system . .
DISC Speci es that the le is applicable to a disk boot only. TAPE Speci es that the le is applicable to a tape boot only. BOTH Speci es that the le is applicable to both disk boot and tape boot. There can be only one disk and one tape autoboot le, although neither is required. The tape and disk autoboot les become TAPEAUTO.MPEXL.SYS and AUTOBOOT.MPEXL.SYS, respectively. Adding boot files The ABOOT command (abbreviated AB) adds a boot image to the system le con guration.
Adding a segment to the compatibility mode The ACMSL command (abbreviated AC) adds a segment to the CMSL. The command has the following parameters: ACMSL (AC) segmented library (CMSL) [SEG =] segmentname [FILE =] lename [MODE = S ] [ C ] [ P ] [ U ] SEG speci es a new segment name with a maximum of eight characters. If an existing segmentname is speci ed, an error occurs. FILE speci es a le name to be added to the CMSL. The lename parameter can be fully quali ed with group and account.
Deleting Objects from the SYSGEN Tape The delete commands (DAUTO, DBOOT, DCMSL, and DSPROG) delete objects from the list of les dumped to tape with SYSGEN's global module TAPE command: DAUTO deletes the speci ed autoboot type from the list of les. DBOOT deletes boot images from the list of les. DCMSL deletes segments from the CMSL. DSPROG removes system programs or les from the con guration.
Use the SHOW command to display a listing of the applicable boot image le names. To delete one or more boot image le names, enter DBOOT and the le name(s) to be removed at the SYSFILE prompt: sysfile>DBOOT Deleting compatibility mode segments from a SYSGEN tape lename The DCMSL command (abbreviated DC) deletes segments from the compatibility mode segmented library (CMSL). The DCMSL command has the following parameter: DCMSL (DC) [SEG =] segment-name, . . .
RCMSL replaces a segment in the temporary copy of the CMSL. RDCC replaces network con guration le dumped to the SYSGEN tape. RIPL replaces an existing IPL image. RNMLIB replaces a native mode (NM) library. RSPROG replaces an existing system program or other le. Replacing autoboot images The RAUTO command (abbreviated RA) replaces an existing autoboot image in the list of les dumped to SYSGEN's tape.
Replacing boot images The RBOOT command (abbreviated RB) modi es the boot type of an existing boot image le name or replaces the boot image le name with another boot image le name. The command has the following parameters: RBOOT (RB) [IMAGE =] [FILE =] [TYPE = boot-image-name lename DISC ] [ TAPE ] [ BOTH ] IMAGE speci es an existing boot image name to be modi ed or replaced. If the speci ed boot image does not exist, an error occurs. FILE speci es a le name to replace the designated boot image.
Configuring a message catalog The RCAT command (abbreviated RC) con gures the message catalog to be used on the target system. RCAT has the following parameter: RCAT (RC) [NAME =] lename The system message catalog contains all the system and subsystem messages. It is retained under a known le name (CATALOG.PUB.SYS). NAME speci es a catalog le name. If the name is not fully quali ed, it defaults to the current group and account. To replace the default catalog name CATALOG.PUB.
Use the LCMSL command to display the segments maintained in the CMSL. Replacing or defining a network configuration file The RDCC command (abbreviated RD) de nes the network con guration le to be used. This command also checks for con icts with SYSGEN's I/O con guration. The le named becomes NMCONFIG.PUB.SYS for SYSGEN's tape only. The user must install or update the system from tape before the le can be used by the network software.
To replace an IPL image, enter the command and the image and le names: sysfile>RIPL imagename Replacing the native mode library lename The RNMLIB command (abbreviated RN) replaces the system NM library that resides in NL.PUB.SYS. The RNMLIB command has the following parameters: 2 RNMLIB (RN) FILE = 3 lename FILE is the le name of the library to replace the current one. If the le name is not fully quali ed, it defaults to the current group and account. If the le name does not exist, an error occurs.
Using a Segmented Library File as CMSL The CMSL command (abbreviated CM) speci es an SL le to be used as the compatibility mode SL. CMSL has the following parameter: 2 3 CMSL (CM) SL = slname The slname parameter is an SL le name. If the SL le name is not fully quali ed, it defaults to the current group and account. If an SL name is not speci ed, the default is SL.PUB.SYS. Enter the command and a fully quali ed SL name to change the default, SL.PUB.SYS, as shown in the following example.
Clearing SYSFILE Configurator Changes If you desire to clear all SYSFILE con guration changes made, enter the CLEAR command at the SYSFILE con gurator prompt: sysfile>CLEAR Once a SYSGEN> KEEP is done, the changes become permanent and CLEAR does not remove them. Holding and Saving Configuration Changes Using the SYSFILE con gurator commands described in the previous sections changes the con guration speci ed in the SYSGEN command line or global BASEGROUP command.
Exiting the SYSFILE Configurator Use the EXIT command (abbreviated EX or E) to deactivate the SYSFILE con gurator and to return to the SYSGEN global module.
9 Halting System Activity A system shutdown does not imply turning o 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 con guration, or for security reasons. If done properly, a shutdown preserves all system and user les.
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 #4Return5 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 4Return5. Enter 4Return5 at the prompt to terminate the WELCOME message facility.
Shutting the Spool Queues and Handling the To verify that the printer is available, to shut down spool queues, and to begin removing backlogged reports, complete the following steps: 1. Verify the printer is active. Enter: :SHOWDEV nn (nn is your printer's ldev number.) Remaining Reports 2. Shut down the spool queue. 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.
Closing Any Open Communication Close any of the system's open communication lines. Enter both of the following to deactivate the NS3000/XL product: :NSCONTROL ABORT :NETCONTROL STOP Lines Note NSCONTROL ABORT ensures that all network management processes are shut down. If you have any other communications products, consult their manuals for instructions on deactivating them.
A Using the Access Port (AP) This section describes the access port (AP) commands and provides the procedures for enabling a remote console, for con guring a system remote support modem port, and for performing the AP self-test. Configuring the Console Some of the terminal con guration parameters are important for proper AP operation.
Entering Control Mode and Using the Command Interpreter Control mode is the mode of operation needed to use the access port commands. Activate the AP control mode interface by entering 4CTRL5 4B5 at the system console: :4CTRL5 4B5 CM> To use the access port command interpreter, enter a two-character AP command at the control mode prompt (CM>), followed by a carriage return: CM>RS Execution of this command irrecoverably halts all system processing and I/O activity and restarts the computer system. . . .
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. 1 May have one of three values: enabled, pending, or disabled. These correspond to the status of the remote console accessibility. The remote console can either be accessed (enabled), disconnected (disabled ), or waiting for a user session to end (pending). 2 May be either active or inactive .
Using Access Port Commands The AP has several commands for manipulating its activities. Table A-2 lists these commands and their functions. Table A-2. Access Port Commands Command A-4 Using the Access Port (AP) Function CA Con gure system remote support modem port. CO Returns console from control mode to console mode. DI Disconnects line to remote console. DR Disables access to the system by a remote console. DS Disables display of system status line during console mode.
Using the AP Help Facility Obtain online help by entering either HELP or the abbreviated command, HE. The command issues the following display: CM>HELP Access Port Revision xxx CA CO DI DR DS ER ES HE RS SE TA TC TE m.d.y Configure system remote support modem port. Enter console mode. Disconnect line to remote console terminal. Disable access by a remote console terminal (enables session access). Disable display of system status line during console mode.
Issuing the AP command, CA, allows either the local or remote console operator to recon gure the baud rate for the remote support modem port, the setting of the T1 RATE line, and the system identi cation. The AP accepts any con guration, making no judgment on the validity.
The system identi cation is a displayable character ASCII string (24 characters maximum) that is stored on the AP, for the AP's exclusive use. The AP identi cation has absolutely nothing whatsoever to do with any other system identi cation stored elsewhere in the SPU. No other entity has access to it, and the AP has no access to any other system identi cation. Enter up to 24 characters as the system identi cation. Characters 00 hex through 1F hex are control characters and are not considered displayable.
The command ER enables remote access to control and console modes through the remote support modem port. The command is only valid from the system console. ER allows you to set the remote access password, the number of password tries, and single or multiple access.
If, during the process of updating the access status settings, the AP encounters any unexpected or inappropriate input, it may respond with a combination of the following messages: Expecting "Y" or "N" (APERR 11) Expecting "S" or "M" (APERR 16) String was truncated to 24 characters. (APMSG 04) Your selection is outside of the legal range. (APERR 14) Command may not be executed by a remote user.
Disconnecting the Remote Line Entering the DI command initiates a clean disconnect from the telephone line connected to the remote support modem port. This command is valid only from a remote console. If a local operator attempts to use this command, the system issues a message: Command may not be executed by a local user. (APERR 15) The system displays the message, Remote line is disconnected , when the line is disconnected.
To minimize the e ect, the entire system status line is not displayed. In console mode, the following display is shown: CODE: xxxx The status line is placed over the softkey labels. To temporarily view the soft keys display, enter a 4Return5. After successfully executing the command, the following message is displayed: System status display during console mode is enabled.
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).
Entering TA executes the AP self-test. The system displays a message during self-test: Testing the AP CM>TA 4Return5 Console data arriving during self-test execution will be lost. Type Y to confirm your intention to execute AP Self-Test (Y/N): Y Starting AP Self-Test. Last subtest will be 30. Executing test number: 00 10 20 30 01 11 21 02 12 22 03 13 23 04 14 24 05 15 25 06 16 26 07 17 27 08 18 28 09 19 29 AP Self-Test passed.
Using Control Commands Entering control mode Halting scrolling Allowing scrolling Entering escape characters Changing master consoles The following section describes additional commands that can be executed with the simultaneous use of the control key. Both a local and remote user can enter 4CTRL5 4B5 to initiate a mode change from console mode to control mode. Entering 4CTRL5 4S5 causes the AP to stop passing characters from its port queues to the consoles.
Interpreting AP Error and Informational Messages The AP provides two classes of messages. A message that is followed by (APERR XX) is an error message. "XX" indicates the error number. A message that is followed by (APMSG XX) is an informational message, although it can indicate a potential error. Error and informational numbers may be duplicated; for example, there is both an APERR 01 and an APMSG 01.
MESSAGE Unable to verify assertion of TOC_SYS backplane signal (APERR 04) CAUSE Information not currently available. MESSAGE AP Self-Test failed subtest xx (APERR 05) CAUSE This message is displayed when a failure occurs during the execution of AP self-test. XX gives the decimal number of the failing subtest. MESSAGE AP failed subtest xx of idle Self-Test. (APERR 06) CAUSE This message is displayed when the idle self-test fails.
MESSAGE Command may not be executed by a remote user. (APERR 13) CAUSE The command entered is a valid AP command, but is intended for use from the local console port (port T0) only. No action has been taken. MESSAGE Your selection is outside of the legal range. (APERR 14) CAUSE Either numeric data has been entered when alphabetic input is expected (or vice versa), or the value of numeric data entered is outside of the permissible range of values. MESSAGE Command may not be executed by a local user.
Informational Messages MESSAGE AP self-test passed. (APMSG 01) CAUSE AP self-test was executed, and it has passed. The message is accurate in almost all cases; however, it is possible that the message will appear without the test having executed to completion. This case can be detected by observing whether the full complement of subtests has been executed in the proper order. AP self-test detects only approximately 70 percent of the faults on the AP. MESSAGE SPU hardware was successfully reset.
B Startup, Dump, and Shutdown Listings This appendix lists the messages, received at the console during successful ISL startup (START), load (UPDATE and INSTALL), dump (DUMP), and shutdown (SHUTDOWN) operations. The START listing begins at the control mode prompt and illustrates the system reset, processor-dependent code (PDC), and input/output-dependent code (IODC) messages.
10 seconds expired--proceeding with autoboot console IO Dependent Code (IODC) revision 3 Boot IO Dependent Code (IODC) revision 3 Booted. MMSAVE Version 9.90 DUMPAREA protected, proceeding to ISL without memsave ISL loaded ISL Revision 2738 September, 1987 Cannot find an auto-execute file. AUTOBOOT ABORTED. ISL> START MPE/XL launch facility Initialize_genesis - Version : <<870204.1552>> THU, MAY 26, 1988, 4:28:32 PM (y/n)? [TMUX_DAM] 15 7 12 14 Initialize genesis completed.
failed. Protection of system files has been completed. The following is a list of the boot options last boot command: INSTALL last configuration group: CONFIG current boot command: START current configuration group: CONFIG logon = OPERATOR.SYS NORECOVERY MULTI-USER MULTI-DISK SYSSTART Entering - System I/O configuration. The path 2 has already been configured. The path 2/4 has already been configured. The path 2/4.0 has already been configured. The path 2/4.0.0 has already been configured. The path 2/4.0.
SYSTEM I/O AT BOOT TIME ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: ldev: 1 2 3 6 7 8 10 19 20 21 22 23 25 26 27 28 29 30 31 32 33 34 39 HP7937H HP7937H HP7933H HP2567A HP7980A HP7978B HP7980A HP2680A HP2392A HP7937H HP7937H HP7937H HP7937H HP7937H HP7933H HP7933H HP2688A HP2688A HP7937H HP7937H HP7935H HP7935H HP2688A configured configured configured configured configured configured configured configured configured c
The current boot command has been saved on the system master. NMLG FILE NUMBER 0 ON. [PSI_DUMP_SURR] Version A.00.01.026 16:30/11/DCC STARTUP - ENTER - version C0005105 compiled 880322 16:30/11/DCC warning 128-1, (Startup) can not open NMCONFIG, status FF09008F. 16:30/18/DCC ERROR 14-1, Configuration file open error 001000B4. 16:30/11/DCC STARTUP - ERROR System State: Initializing Mode. Reply Information Table has been initialized! System State: Multiuser Mode.
DUMP Sequence Caution Refer to Chapter 3 for information on the steps involved in the DUMP process. The following represents a DUMP sequence for Series 950 through Series 955 systems received at the console. DUMP sequences for other installations may vary. 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.
MPE/XL launch facility MPE/XL Dump Version A.00.00 - initialization A full dump, including secondary storage, was requested. Enter user identification string for this dump (80 chars or less): TEST DUMP 6/9/88 Initialize_genesis - Version : <<870204.1552>> WED, JUN 8, 1988, 2:30:04 PM (y/n)? [TMUX_DAM] 15 7 12 14 Initialize memory manager completed. MPE/XL Dump Facility Version A.00.
Processor Dependent Code (PDC) revision 2.8 Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.0.0.0.0.0.0 Alternate boot path = 6/4.3.0.0.0.0.0 32 MB of memory configured and tested. Soft Booted- -memory state is valid Autoboot from primary path enabled. To override, press any key within 10 seconds. 10 seconds expired- -proceeding with autoboot Console IO Dependent Code (IODC) revision 3 Boot IO Dependent Code (IODC) revision 3 Booted. MMSAVE Version 9.
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 for information on the steps involved in shutting down the system. The following represents a shutdown sequence for Series 950 through Series 980 systems received at the console. Sequences from other installations may vary. :TELL @S;SHUTDOWN IN 15 MINUTES. PLEASE LOG OFF.
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).
The stable storage contents are allocated as shown in the following gure. Figure C-1. Stable Storage Contents Note Byte addresses are numbered beginning with 0. For example, 0 is the rst byte, 1 is the second. Decimal byte address 0 contains the status of the autoboot and autosearch ags. The byte contains two hexadecimal values. The rst two binary digits of the rst value show the ag status as either ON (1) or OFF (0). Byte 7, obtained by reading decimal address 4, contains the logical module index.
To read one word (4 bytes) of stable storage, use the ISL command READSS: ISL> READSS x 4Return5 or ISL> READSS 4Return5 Input SS address: 4 Address 4 contains 0xFFFFFF08 In the last byte (number 7), 08 indicates the module number, 8. Reading Nonvolatile Memory (NVM) 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.
Figure C-2. NVM Contents 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 ags during the boot sequence. Address decimal 68 contains the ISL revision number in ASCII.
Locations 76 through 123 contain the names of the utilities booted. They are placed into a circular queue. The pointer at location 124 ( rst two digits) is positioned to the last utility executed. The pointer ranges from 1-6 (decimal) or 01-06 (hexadecimal), indicating which utility (1-6 - top to bottom on gure C-2) was last executed.
D Default Configurations Used by INSTALL and UPDATE The INSTALL utility on a factory system load tape replaces a system's con guration les with a default con guration. These defaults allow the system manager or system supervisor to boot the system to a fully operational level. You should then alter the functioning con guration to meet your system's needs using SYSGEN. START uses CONFIG as its default con guration group.
Table D-1.
Table D-2. Default Configurations for the 900 Series (continued) GROUP NAME Note Note SYSTEM DESCRIPTION CARDS CONFG990 990 PB-FL and SCSI ALINK990 990 PB-FL CONFG991 991 PB-FL and SCSI ALINK991 991 PB-FL CONFG992 992 PB-FL and SCSI ALINK992 992 PB-FL CONFG995 995 PB-FL and SCSI ALINK995 995 PB-FL The PB-FL card is the FL card that is used in precision bus systems, such as 99X systems.
Before a system can properly use its START command, a functioning set of con guration les must reside in the con guration group CONFIG. The START command uses CONFIG as its default con guration group. Since multiple con guration groups reside on a system load tape (SLT), CONFIG is empty until the system manager copies an appropriate con guration group into it. Using SYSGEN to Copy the Files You must use SYSGEN to copy con guration groups.
make. After making any changes, hold them (issue the HOLD command in each con gurator used to make changes), and return to SYSGEN's global module. 4. Save the con guration to disk as CONFIG. After you have completed making changes, if any, save the con guration to the CONFIG group.
5. Generate a system load tape (SLT) if desired. To create an SLT that contains the new con guration, use CONFIG as the base group, and save it to tape, as discussed in Chapter 3. 6. Use the new con guration and restart the system. If you modi ed the con guration and now desire to implement it on the system, shut down and restart the system. To shut down the system enter: :4CTRL5 A =SHUTDOWN d c 7.
E Verifying Attached Devices This section discusses using the initial system loader's IOMAP or ODE utility to verify which devices are attached and con gured to a 900 Series HP 3000 computer system. Overview SYSGEN provides utilities for listing the con gured 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 con gured path does not require an associated device.
When running with default options, IOMAP and ODE running MAPPER perform the following operations: displays the current con guration of the processor, including the presence of coprocessor boards, analyzer cards, memory sizes of cache and translation look-aside bu er (TLB) cards, the processor model number, and the processor-dependent code (PDC) rmware revision checks all possible I/O paths to determine if a component is present, and identi es every component (such as a module, bus converter, adapter, device
Running IOMAP Note For 9X8LX and 9X8RX systems, you must run ODE instead of IOMAP. Refer to Running ODE later in this chapter. To run IOMAP: 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.
c. Prevent new system activity. Enter: :LIMIT 0,0 :JOBFENCE 14 The command LIMIT 0,0 limits the number of concurrently running jobs and sessions. The two parameters x, x de ne the allowed number of jobs and sessions, respectively. The command JOBFENCE de nes the minimum input priority that a job or session must have to execute. The parameter, 14, raises the jobfence to the highest level. d. Warn users ve minutes prior to the system shutdown to end their sessions.
4. Enter the ISL IOMAP command at the ISL prompt. Enter: ISL>IOMAP 5. The system responds: d a IOMAP Revision A.01.63 July 23, 1993 IOMAP Running: ce81 This program has the capability to identify the configuration of the system and its I/O paths and devices. Many of the components of the I/O system can be tested with selftest and loopback diagnostics. Without changing any parameters, this program will map all existing I/O components in the system, but will not perform any other diagnostics.
d a I/0 Configuration: Path Component Name ------------ -------------------------------0 Native Processor 4 CIO Channel Adapter 4.1 HP-IB card 4.1.0 7937H disc drive 4.1.1 7937H disc drive 4.1.2 7937H disc drive 4.1.3 7937H disc drive 4.1.4 7937H disc drive 4.2 Console Device Adapter 4.3 LAN card 4.4 LAN card 4.5 HP-IB card 4.5.2 HPC1707A CD-ROM drive 4.5.3 7980 mag tape unit 4.6 HP-IB card 4.6.
Running ODE To run ODE : 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 o . Enter: :TELL @S;SYSTEM SHUTDOWN IN 10 MIN.
c. Prevent new system activity. Enter: :LIMIT 0,0 :JOBFENCE 14 The command LIMIT 0,0 limits the number of concurrently running jobs and sessions. The two parameters x, x de ne the allowed number of jobs and sessions, respectively. The command JOBFENCE de nes the minimum input priority that a job or session must have to execute. The parameter, 14, raises the jobfence to the highest level. d. Warn users ve minutes prior to the system shutdown to end their sessions.
4. Type the following to run ODE: ISL>ODE 5. Initiate the MAPPER module: ISL>RUN MAPPER MAPPER displays the current con guration using the same format as IOMAP (see example E-1 for an example display).
F Adding Peripherals to a System Three types of device adapters are available on HP 3000 systems: HP-IB Hewlett-Packard Interface Bus HP-FL Hewlett-Packard Fiber-optic Link SCSI Small Computer System Interface Before a device can be used on your system you must de ne a pathway, consisting of various interface components, from the system to the device.
HP-FL/SCSI Devices The rst two con guration levels consist of the device adapter address and the device address. To con gure a device adapter with a path of 48, for example, enter: APATH 48,ID=nnnnn Where nnnnn is a valid device adapter identi er such as HP28616A or HP28642A-SCSI. HP-FL Devices To con gure the device use the ADEV command and the device address. For example, for a device address of 2, you would enter: ADEV 48.2,ID=nnnnn where nnnnn is a device identi er such as HP7937FL or HPC2474R.
Series 920, 922, 932, 948, 958, 925, 935, 949 CIO Systems Note Channel Adapter You can con gure these systems with HP-IB, HP-FL and some SCSI interfaces. Three or four levels of addressing are required: a channel adapter module number (or interface slot number), the device adapter address the device address and possibly a unit address. The operating system will not boot from a CIO SCSI device. The rst address level is the channel adapter module number.
Unit Identifier The fourth-level provides the unit address for multi-unit devices. It is required for SCSI devices regardless of whether they are single or multi-unit. It is required for HP-FL and HP-IB devices only when they are con gured as multi-unit devices. To con gure a unit address of 3, for example, on the device con gured above, enter: ADEV 4.3.1.3,ID=nnnnn where nnnnn is a valid device identi er.
SCSI Devices For a SCSI interface you must use the word PSEUDO as the device identi er as follows: APATH 48.2,ID=PSEUDO Unit Identifier The third level provides the unit address for multi-unit devices. It is required for SCSI devices regardless of whether they are single or multi-unit. To con gure a unit address of 3, for example, on the device con gured above, enter: ADEV 48.2.3,ID=nnnnn where nnnnn is a valid device identi er.
Device Adapter To con gure a device adapter with an address of 3 to the channel adapter module identi er: ADEV PATH 6/4.3,ID=nnnnn where nnnnn is a device adapter identi er such as HP28616A. HP-FL/HP-IB Devices To con gure a device with an address of 1 to the device adapter: ADEV PATH 6/4.3.1,ID=nnnnn where nnnnn is a device identi er such as HP7937FL or HP7937H.
HP-FL Peripherals The HP-FL card provides the computer system with a high-speed serial connection to peripherals over a ber optic data link. Device speci c data is converted to a format compatible with the CIO bus. The high-speed data transfers of HP-FL cards requires that HP-FL devices occupy the lowest-priority CIB slots on CIO machines. Therefore, HP-IB systems (which can only be CIO because HP-IB is not supported on NIO) may require recon guration to accommodate HP-FL cards.
Adding a Peripheral to Any System d Adding a disk drive, tape drive, or printer to a system's con guration includes the following steps: enter SYSGEN view the system's current con guration activate the IO con gurator make the necessary I/O con guration changes hold the changes save the changes verify the accuracy of the new con guration 1. Activate SYSGEN's global module. Enter the SYSGEN command at the system prompt. :SYSGEN SYSGEN 1988 version B.06.01 : catalog version B.06.
After deciding which copied con guration group to modify, use the global module BASEGROUP command to activate the group: sysgen>BASEGROUP groupname Use the I/O con guration contained in CONFG935 as an example con guration for this exercise. 3. Activate the IO con gurator.
6. Decide on the class of the added peripheral. View the LCLASS listing. If it contains a class (DISC) assigned to a particular type of peripheral (in this case, a disk drive), use that class for your addition. Remember, each device can simultaneously belong to up to eight classes. If your con guration does not contain a class name for the additional peripheral, the system will create a class name for you if you use a name that does not exist.
10. Exit the IO con gurator. Enter the EXIT command at the IO con gurator prompt: io>EXIT sysgen> 11. Save changes in a permanent le. Enter the global module KEEP command at the SYSGEN prompt: sysgen>KEEP CONFIG CONFIG is the group name under which you save the modi ed les. Each time you start up the system, the group CONFIG will then be the default. Refer to Chapter 4 for additional information on using the KEEP command. 12. Generate a boot tape. Mount a write-enabled tape on the tape drive.
In this procedure, the system manager chains (con gures) a tape drive to another con gured device, (commonly referred to as a host device). The host device doesn't have to be physically attached to the system to con gure the tape drive but when the tape drive is connected, the host device must be present.
G UPS and UPS Monitor/iX Software A new method of power failure protection is available on the HP 3000 Series 991 and 995 computer systems and the Series 9X8 systems. Instead of battery backup units, they will have one or more HP model A2998A PowerTrust UPS (Uninterruptible Power Supply) devices. Like the battery backup method of power failure, the UPS devices protect the HP 3000 system against the loss of work in progress in cases of utility AC power failures of up to fteen minutes in duration.
Configuring a UPS device You can use one of two con guration methods to add UPS devices to a Series 9X8 systems. For the rst 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 precon gured in the default con guration group supplied with the FOS tape. You perform this procedure once, immediately after you install a new system.
9. Press Prior Screen twice and at the Main screen, press Utility . NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNN 10. At the Utility screen, press Validate Link/DTS to cross-validate the DTC con guration with the SYSGEN con guration. 11. Once validation is complete, press Prior Screen three times and at the Open Con guration File screen, press Exit Program to exit NMMGR. 12. Reboot the system to make the new con guration e ective. 13.
7. Add each UPS by entering its logical device number in the Ldev eld and UP10D12 in the Pro le Name eld. When you have added all UPS devices, press Save Data NNNNNNNNNNNNNNNNNNNNNNNNNNNNN 8. Press the Validate Link/DTS softkey to cross-validate the DTC con guration with the SYSGEN con guration. 9. Once validation is complete, press Prior Screen until you see the Open Con guration File screen, and then press Exit Program to exit NMMGR.
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.
System Behavior When AC Power Returns The behavior of the system when AC input power returns to the UPS is very similar to that of the battery backup method systems. One of two things will happen: a recovery from power failure (if AC power returns before the UPS battery that backs up the SPU becomes exhausted) or a system crash.
d c a log>SHOW SLOG log> system log events ----------------System logging enabled System up record Job initiation record Job termination record Process termination record NM file close record System shutdown record Power failure record Spooling log record I/O error record Physical mount/dismount Logical mount/dismount Tape labels record Console log record Program file event NCS spooling log record Architected interface record Password changes System logging configuration Restore logging Printer access
To review UPS activity recorded in the system log file UPS Monitor/iX status and alarm messages are recorded in the system log les as event number 148. You can use the LOGTOOL utility to review entries in the system log le about the performance and condition of UPS devices on your system. To do so, follow these steps: 1. List the names of the log les currently on your system. At the MPE prompt, enter: :LISTFILE LOG@.PUB.SYS Note the number of the last log le in the list (other than LOGDCC).
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 les or acquiring the use of a device. Access implies an input/output (I/O) operation, and is used as a synonym for I/O. access port (AP) The port located in the channel I/O (CIO) section of the system card cage that provides a user support interface for issuing hard and soft resets through software commands from the console.
account manager capability (AM capability) A capability assigned by the system manager to one user within each account who is then responsible for establishing users and groups. account member A person who has been granted access to the system through the use of a valid user name within an account. Account members are created by the account manager, who de nes the user name and assigns the appropriate capabilities and security restrictions for the user.
autoboot The process of automatically starting the system. automatic restart Main memory battery backup to automatically restart the system after a power failure. Temporary power line interruptions can be tolerated with no data loss and without needing to restart the system. backup The process that duplicates computer data to o ine media, such as magnetic tape. Backups protect data if a system problem should occur.
channel I/O (CIO) Input/output instructions for a channel. channel I/O adapter A device that provides the interface between the central bus (CTB) and the channel I/O buses. Each channel I/O adapter serves as a high performance channel multiplexer providing a full direct memory access (DMA) for all HP-IB and LAN I/O channels and synchronizing the di ering speeds and bandwidths of the CTB and channel I/O buses.
communication link The software and hardware that moves data from the driver and card of one computer to the driver of an adjacent computer. compatibility The ability of software developed for one computer to work on another computer. See compatibility mode. compatibility mode (CM) A method of providing object code compatibility between MPE V/E-based systems and the 900 Series HP 3000 system.
continuation character An ampersand (&) character entered as the last character of a command line. A continuation character tells the command interpreter that the command is longer than one line and is continuing onto a second or more subsequent lines. control-Y A break function activated by simultaneously pressing the 4CTRL5 key and the 4Y5 key on a terminal's keyboard. It is typically a subsystem break and does not a ect MPE commands. In documentation this two-key sequence is shown as 4CTRL5 4Y5.
device adapter A device that manages communications between the computer and a peripheral device. It is the same as an I/O interface card. device class A collection of devices that have some user-de ned relation. The le system supports a means of maintaining collections of devices but is cognizant of the relation only for certain device class names. device le A le associated with a non shareable device (a spool le).
DISCFREE A utility that supplies information about a system's unused disk space, transient and permanent space, and the volume's total space capacity. The information is supplied in either a histogram or a condensed format. Equivalent to the MPE V/E FREE5 utility. disk A circular plate of magnetically coated material used to store computer data. A disk may be xed, removable, hard, or exible. disk drive A peripheral device that reads information from and writes information to the disk.
EXCLUSIVE access A restriction limiting le access to one user at a time. EXCLUSIVE access is particularly important during le updates, when two or more people modifying the same record within a le, at the same time, could destroy data consistency. execute To carry out the instructions or to perform the routine indicated by entering a command or program name. executing state The state of a job or session when it is in progress. Other possible states are INTRO, WAIT, EXEC*, and SUSP.
le space The number of sectors of disk space that a user, group, or account is using. It is determined by executing the REPORT command. foreign disk A non-system domain disk that MPE V/E does not recognize as a private volume or serial disk. Foreign disks are non shareable devices, and can be formatted either sequentially or for direct record access. Foreign disks, such as private volumes and serial disks, do not have entries in the system volume table.
group librarian capability (GL capability) A capability assigned by the account manager to a user within an account. A group librarian is allowed special le access modes for the maintenance of certain les within the user's home group. hard reset A method of resetting the computer or a terminal. A hard reset erases all information in memory. hardware All the physical components of the computer, including the CPU cabinet, tape drives, disk drives, terminals, and other peripherals.
host computer 1) The primary or controlling computer in a multiple computer installation. 2) In a network, the computer that primarily provides services such as computation, database access, or special programs or programming languages, to other users on the network. implied run The ability to run a program without explicitly using the RUN command. In MPE/iX it is not necessary to specify RUN FCOPY.PUB.SYS to invoke and run the FCOPY program. It is only necessary to enter FCOPY.
interactive access capability (IA capability) A capability assigned to accounts and users allowing users to initiate sessions with the HELLO command. interactive user A user who enters commands at a terminal. I/O bay A cabinet containing the card cages and device controller boards for peripherals connected to the HP 3000.
LAN 3000/XL LINK The hardware and communications software needed to connect 900 Series HP 3000 machines to a network for system-to-system communication. LAN cables Cables used to connect the distributed terminal controller (DTC) and the system. LDEV number See logical device number. library A le containing a set of procedures and variables that can be accessed by programs. Local Area Network (LAN) A computer network con ned to a single location.
state prior to the failure. 2) The process used by DBCore to record the activity of a DBEnvironment to enable either rollback or rollforward recovery if necessary. logging shutdown A shutdown marking the end of the logging cycle. In most cases, it is performed just prior to either system or database backup. logical device (LDEV) A disk le, a set of disk les, or a physical device associated with a data stream between a host and a remote system.
member volume A volume containing a volume label indicating that it belongs to a volume set. It may be used by one or more volume classes. memory error logging A facility that records all memory errors. It begins automatically when the system is initialized. memory mapped I/O A con guration in which each device or I/O interface card is assigned a set of memory locations, or memory mapped I/O registers. menu A display on the terminal screen showing the options available within a program.
network architecture A structured, modular design for networks. network services (NS) A group of software products that provide the user interface to the network. They allow batch jobs submittals, le transfers, virtual terminal access, and other services. node One end of a communications link or a computer system in a network. For example, if two HP 3000 computers are connected via a DS line, each system is considered a node.
optional parameter A parameter that is not required when entering a command or calling an intrinsic. In reference manuals, optional parameters are surrounded by square brackets ([ ]). outfence A number in the range of 1 (lowest priority) to 14 (highest priority), used to control access to the system printer. If a job does not have an input priority higher than the system outfence (default 7), it will not print. output Data transferred from internal to secondary (external) storage in a computer.
power down To turn the system power o . power up To turn the system power on. preventive maintenance (PM) The regular housecleaning chores performed to keep the system from su ering performance degradation and to prevent problems from developing on the system. primary boot path The path used to boot the system from disk-resident software. priority request The use of the optional parameter ;HIPRI in the HELLO and JOB commands.
process identi cation number (PIN) A number assigned to a process by MPE when the process is created. It is used internally by MPE (in the process control block (PCB) table) and during requests for system resources at the console (when the operator responds to requests by referencing the PIN in the REPLY command). processor dependent code (PDC) An MPE/iX hardware routine to read and initialize the I/O paths used for booting or rebooting the system.
remote node A node that is not physically located where you are and which you communicate with via data communication. remote session A session initiated from an area physically separated from the computer. remote system A computer system physically separated from other computer systems. remote system console A terminal which provides remote access to the SPU as a system console or terminal session. remote terminal A terminal that is indirectly connected to the computer, using a modem and telephone hook up.
restricting data A way of limiting access to data by grouping data into volumes, volume classes, and volume sets. run To execute a program. run time The environment in which a process is running or executing. save les capability (SF capability) The capability allowing users to save the les they create. It is assigned by default to accounts and users. search path A mechanism that controls which le is opened once a command is determined not to be a UDC nor an MPE command.
single-user mode A DBEnvironment startup mode that allows only one DBE session to be active at a time. single-user state A condition of the MPE/iX operating system in which the system console provides the only communication mechanism between the system and its user. single-user system A system that can communicate with only one xed terminal. soft reset A reset that initializes a variety of terminal functions but does not reset the memory.
$STDLIST A system-de ned le name indicating the standard job or session listing le corresponding to the particular input device being used. The listing device is usually a printer for batch jobs and a terminal for sessions. storage device A device (such as a disk pack, a disk cartridge, a exible disk, magnetic tape, or cartridge tape) onto which data can be stored and subsequently retrieved. STORE 1) The process of saving HP 3000 les to tape or serial disk. Storing is executed by using the STORE command.
system console 1) A workstation given a unique status by the operating system. It is used by the operator to execute speci c commands for the purpose of managing sessions, jobs, and system resources. It is associated with all boot or system loader error messages, system error messages, and certain system status messages. 2) The terminal, usually logical device 20, that the system operator uses to monitor system activity, respond to resource requests, and send messages to user's terminals.
create a boot tape to bring up an MPE/iX system with the new con guration. Equivalent to MPE V/E SYSDUMP and INITIAL utilities. system halt The condition following a system shutdown or system failure, indicated by no response at the system console or to any user command. system load tape A tape that contains the system load utilities, base system les, and user les. It is generated with the SYSGEN utility. Equivalent to the MPE V/E coldload tape.
system volume An MPE/iX system volume set. It contains a bootable system image and system con guration on its master volume. It is the only volume needed to load and start the system. It is always mounted and named MPEXL_SYSTEM_VOLUME_SET. temporary le A le that exists only for the duration of a session or job. terminal A hardware device connected to a computer and used for entering and receiving data. A terminal consists of a keyboard and a display screen.
computer. Equivalent to the MPE/iX ISL UPDATE utility UPDATE NOCONFIG option. use communications subsystems capability (CS capability) A capability assigned to accounts and users allowing access to the MPE communications subsystems. user command A set of MPE/iX commands that a user has grouped together to perform a speci c task. A user command is stored in a command le and does not have to be entered into a catalog. User commands are last in MPE's search path for commands.
to eight alphanumeric characters, beginning with an alphabetic character. volume number The part of an address used for a device number whose meaning is software and device dependent, but is often used to specify a particular volume on a multivolume disk drive. volume set A group of up to 255 related disk packs. One volume of the volume set must be designated as the master volume for the set. Each volume set is assigned a name by which it is identi ed and referenced.
Index A AAUTO SYSFILE con gurator command, 8-8 ABOOT SYSFILE con gurator command, 8-8, 8-9 ABORTJOB MPE/iX command, E-4, E-8 access panel lock, 2-5 access port con guring, A-6 access port (AP), 2-2 support interface, 2-2 testing, A-13 using, A-1 access port(AP) using, 2-2 access port commands, A-4 RS, 2-1 TC, 2-1 Using, A-4 account SYS, 4-2 accounts used to store con guration data, 4-2 ACLASS I/O Con gurator command, 5-11 ACMSL SYSFILE con gurator command, 8-10 SYSFILE Con gurator command, 8-8 activating
I/O Con gurator command, 5-11 AP error messages interpreting, A-15 AP help facility using, A-5 AP informational messages interpreting, A-15 AP.
boot paths, 2-7, 5-2 alternate, 5-2 console, 5-2 primary, 5-2 boot tape, 1-2, 4-2 boot utilities.
DDEV, 5-13 DPATH, 5-13 DVOL, 5-13 MADDRESS, 5-12 MCLASS, 5-12 MDEV, 5-12 MPATH, 5-12 MVOL, 5-12 commands - IO con gurator ADEV, F-1{11 APATH, F-1{11 EXIT, F-11 HOLD, F-10 LCLASS, F-9 LDEV, F-9 LPATH, F-9 OCLOSE, F-9 commands - ISL IOMAP, E-4 ODE, E-8 START, 4-2, 5-4, D-3 commands - LOG con gurator CLEAR, 6-6 EXIT, 6-8 HELP, 6-2 HOLD, 6-7 OCLOSE, 6-3 SHOW, 6-3 SLOG, 6-5 ULOG, 6-6 commands - MISC con gurator CLEAR, 7-13 DRIN, 7-7 EXIT, 7-14 help, 7-2 HOLD, 7-13 JOB, 7-7 LRIN, 7-8 OCLOSE, 7-8 RESOURCE, 7-9 SES
commands - SYSFILE con gurator AAUTO, 8-8 ABOOT, 8-8, 8-9 ACMSL, 8-8, 8-10 ASPROG, 8-8, 8-10 DAUTO, 8-11 DBOOT, 8-11 DCMSL, 8-11, 8-12 DSPROG, 8-11, 8-12 help, 8-2 RAUTO, 8-12 RBOOT, 8-12, 8-14 RCAT, 8-12, 8-15 RCMSL, 8-12, 8-15 RDCC, 8-12, 8-16 RIPL, 8-12 RNMLIB, 8-12 RSPROG, 8-12 SHOW, 8-6 commands - SYSGEN BASEGROUP, 4-9, 6-7, F-8 CLEAR, 4-2, 4-17 EXIT, 4-24 HOLD, 4-17 I/O, 5-5 IO, F-9 KEEP, 4-1, 4-17, 6-7, 7-13, F-8, F-11 LOG, 6-1 MISC, 7-1 OCLOSE, 4-14, 4-19 PERMYES, 4-10 SHOW, 4-14 SYSFILE, 8-1 TAPE,
modifying, 5-1 storing, 1-2 con guration les copying, D-4 creating, 4-1 permanent, 4-1 temporary, 4-1 con guration group, 4-1 con guring a message catalog, 8-15 con guring job related limits, 7-7 con guring local devices, 5-1 con guring terminals, 1-2 con guring the console, A-1 con rming potentially serious actions SYSGEN utility, 4-10 console messages sending, A-9 console mode returning from control mode, A-5 console path, 5-2 example, 2-7 constructing I/O paths, 5-2 control mode entering, 2-3, A-2, A-14
CONF9X72, D-1 CONF9X73, D-1 CONF9X74, D-1 CONF9X75, D-1 CONFE925, D-1, D-4 CONFE950, D-1, D-4 CONFG920, D-1 CONFG922, D-1 CONFG925, D-1, D-4 CONFG932, D-1 CONFG935, D-1, D-4 CONFG948, D-1 CONFG950, D-1, D-4 CONFG958, D-1 CONFG990, D-1 CONFG991, D-1 CONFG992, D-1 CONFG995, D-1 CONFSCS0, D-1 default options INSTALL utility, 3-32 START utility, 3-12 UPDATE utility, 3-27 de ning a network con guration le, 8-16 de ning system parameters, 1-2 deleting autoboot images, 8-11 deleting boot images, 8-11 deleting clas
DUMP, 2-1 DUMPAREA, 3-1 dumping a system, 3-11 dump listing, B-1 DUMP sequence, B-6 DUMP utility, 3-11, 3-34, 3-35 default options, 3-35 SUBSET option, 3-35 DVOL I/O Con gurator command, 5-13 E F Index-8 enabling and disabling the autoboot ag, 3-6 enabling and disabling the autosearch ag, 3-6 entering an MPE command from the LOG con gurator, 6-7 entering an MPE command from the MISC con gurator, 7-14 entering IOMAP, E-3 entering ODE, E-7 entering the I/O con gurator, 5-5 entering the LOG con gurator, 6-1
G H I generating a boot tape, 4-18 global resource identi cation numbers deleting, 7-7 see GRINS, 7-7 GRIN, 7-7 see global resource identi cation numbers, 7-7 group CONFIG, 4-2 halting commands SYSGEN utility, 4-8 halting SYSGEN command actions, 4-8 hard reset, 2-1, 2-2 hardware clock, 3-9 HELLO MPE/iX command, E-3, E-7 help facility I/O con gurator, 5-5 MISC con gurator, 7-2 SYSFILE con gurator, 8-2 SYSGEN global module, 4-4 HELP facility LOG con gurator, 6-2 Hewlett-Packard Fiber-optic Link, F-1{11 Hew
I/O con guration modifying, 5-1 I/O con guration changes online, 5-14 I/O con gurator, 5-1 help facility, 5-5 I/O con gurator commands HELP, 5-5 LCLASS, 5-8 LDEV, 5-8 LPATH, 5-8 LVOL, 5-8 MADDRESS, 5-7 OCLOSE, 5-9 I/O Con gurator commands ACLASS, 5-11 ADEV, 5-11 APATH, 5-11 AVOL, 5-11 DCLASS, 5-13 DDEV, 5-13 DPATH, 5-13 DVOL, 5-13 MADDRESS, 5-12 MCLASS, 5-12 MDEV, 5-12 MPATH, 5-12 MVOL, 5-12 IO con gurator commands ADEV, F-1{11 APATH, F-1{11 EXIT, F-11 HOLD, F-10 LCLASS, F-9 LDEV, F-9 LPATH, F-9 OCLOSE, F-9
series 922-949, 2-8 IPL.
J K L Index-12 JOB MISC con gurator command, 7-7 JOBFENCE MPE/iX command, E-3, E-7 JOBFENCE command, 9-2 KEEP SYSGEN command, 4-1, 4-17, 6-7, 7-13, F-8, F-11 keeping con guration changes, 4-17 keyword parameters SYSGEN utility, 4-8 LCLASS I/O con gurator command, 5-8 IO con gurator command, F-9 LDEV I/O con gurator command, 5-8 IO con gurator command, F-9 LDEV number, 5-8 see logical device number, 5-8 LIF.
logging system, 6-1 user, 6-1 logging (LOG) con gurator, 4-1, 6-1 see LOG con gurator, 4-1, 6-1 logical device number see LDEV number, 5-8 logical interchange format (LIF), 2-13 logical interface format (LIF), 3-1 LOG values showing, 6-3 loopback test, E-2 LPATH I/O con gurator command, 5-8 IO con gurator command, F-9 LRIN MISC con gurator command, 7-8 LVOL I/O con gurator command, 5-8 M MADDRESS I/O con gurator command, 5-7 I/O Con gurator command, 5-12 MAPPER exiting, E-9 master consoles changing, A-14 M
help, 7-2 SHOW, 7-4 miscellaneous (MISC) con gurator, 4-1, 7-1 see MISC con gurator, 4-1, 7-1 MMSAVE, 3-1 modifying addresses in SYSGEN , 5-12 modifying classes in SYSGEN , 5-12 modifying devices in SYSGEN , 5-12 modifying I/O con gurations, 5-1 modifying paths in SYSGEN , 5-12 modifying system parameters, 1-2 MPATH I/O Con gurator command, 5-12 MPE/iX commands ABORTJOB, E-4, E-8 HELLO, E-3, E-7 JOBFENCE, E-3, E-7 LIMIT, E-3, E-7 SHOWJOB, E-4, E-8 TELL, E-3, E-7 WARN, E-4, E-8 MPE XL commands REPLY, F-11 SH
P R path information stable storage, 3-7 PDC, 5-2, E-1 see processor dependent code, 5-2 PDC See processor dependent code, 2-1 peripheral devices de ned, 1-2 permanent con guration les, 4-1 PERMYES SYSGEN command, 4-10 PERMYES in batch mode, 4-23 PERMYES in command les, 4-23 positional parameters SYSGEN utility, 4-8 primary boot paths, 5-2 example, 2-7 processor dependent code (PDC), 2-1, 2-12, 3-1 processor test series 950-980, 2-11 RAUTO SYSFILE con gurator command, 8-12 RBOOT SYSFILE con gurator comman
reset button series 950-980, 2-5 RESET buttons, 2-5 reset switch series 922 through 949, 2-5 resetting a series 922-949, 2-6 resetting a series 950-980, 2-6 resetting Series 949 systems (example) autoboot enabled, 2-7 resetting the system, 2-1, 2-2, 2-5 hard reset, 2-1 soft reset, 2-1 via the front panel switches, 2-5 RESOURCE MISC con gurator command, 7-9 resource allocations setting, 7-9 resource identi cation numbers deleting, 7-7 see RIN, 7-7 resources allocating, 7-9 retaining current con guration, 3-3
Series 922RX default con guration, D-1 Series 925 default con guration, D-1 Series 925LX default con guration, D-1 Series 932 default con guration, D-1 Series 935 default con guration, D-1 Series 948 default con guration, D-1 Series 949 default con guration, D-1 Series 950 default con guration, D-1 Series 950-980, 2-6 Series 958 default con guration, D-1 Series 960 default con guration, D-1 Series 980 default con guration, D-1 Series 990 default con guration, D-1 Series 991 default con guration, D-1 Series
shutdown abbreviated list of steps, 1-3 de nition, 1-3 SHUTDOWN command, 1-3, 9-4 shutdown listing, B-1 shutdown sequence, B-9 SHUTQ command, 9-3 shutting down the system, 1-3 SLOG LOG con gurator command, 6-5 slot number, 5-2 SLT, 4-18, 4-19, D-4 see system load tape, D-4 Small Computer System Interface, F-1{11 soft reset, 2-1, 2-2, A-12 soft reset.
setting, 7-12 subparameters SYSGEN utility, 4-8 support, 3-2 SYS account, 4-2 SYSFILE SYSGEN command, 8-1 SYSFILE con gurator, 4-20, 8-1 entering, 8-1 help facility, 8-2 see system le con gurator, 8-1 SYSFILE con gurator commands AAUTO, 8-8 ABOOT, 8-8, 8-9 ACMSL, 8-8, 8-10 ASPROG, 8-8, 8-10 DAUTO, 8-11 DBOOT, 8-11 DCMSL, 8-11, 8-12 DSPROG, 8-11, 8-12 he,p, 8-2 RAUTO, 8-12 RBOOT, 8-12, 8-14 RCAT, 8-12, 8-15 RCMSL, 8-12, 8-15 RDCC, 8-12, 8-16 RIPL, 8-12 RNMLIB, 8-12 RSPROG, 8-12 SHOW, 8-6 SYSGEN, 3-30, 3-34,
placing objects on, 8-12 removing system programs from, 8-12 SYSGEN utility, 1-2, D-4 activating, 4-2 activating the con gurators, 4-15 clearing con guration changes, 4-17 con rming serious actions, 4-10 displaying state of con gurators, 4-14 entering the I/O con gurator, 5-5 entering the LOG con gurator, 6-1 exiting, 4-24 generating a boot tape, 4-18 global module, 4-1 halting commands, 4-8 holding con guration changes, 4-17 keyword parameters, 4-8 positional parameters, 4-8 redirecting input and output, 4
see SLT, D-4 system load tape (SLT), D-1 system logging, 6-1, 6-5 system main bus (SMB), 2-9 system parameters de ning, 1-2 modifying, 1-2 system reload (INSTALL), 3-31 system shutdown overview, 9-1 system shutdown. See shutdown, 1-3 system startup.
SYSGEN, activating, 4-2 SYSGEN, global module, 4-1 utilities - ISL INSTALL, D-3 IOMAP, 5-4, E-1 START, 4-2 UPDATE, D-3 utilities - MPE XL SYSGEN, D-4 V W Index-22 verifying attached devices, E-1 WARN MPE/iX command, E-4, E-8 WARN command, 9-3 WELCOME command, 9-2
