HP 900 Series 3000 computer system Reference manual

900 Series HP 3000 Computer Systems
System Startup,
Configuration, and Shutdown
Reference Manual
ABCDE
HP Part No. 32650-90042
Printed in U.S.A. 1996
Fifth Edition
E0796
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.
Hewlett-Packard assumes no responsibility for the use or reliability of
its software on equipment that is not furnished by Hewlett-Packard.
This document contains proprietary information which is protected
by copyright. All rights are reserved. Reproduction, adaptation, or
translation without prior written permission is prohibited, except as
allowed under the copyright laws.
c 1996 by Hewlett-Packard Company
Copyright Use, duplication, or disclosure by the U.S. Government is subject
to restrictions as set forth in subparagraph (c) (1) (ii) of the
Rights in Technical Data and Computer Software clause at DFARS
252.227-7013. Rights for non-DoD U.S. Government Departments and
agencies are as set forth in FAR 52.227-19 (c) (1,2).
Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.
Restricted Rights Legend
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.
Edition
Date
Software
Version
First Edition
Second Edition
Third Edition
Fourth Edition
Fifth Edition
October 1989
April 1990
June 1992
April 1994
July 1996
A.20.00
A.40.00
B.40.00
C.50.00
C.55.00
iii
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. You can continue to
use MPE XL system documentation, although it may not refer
to features added to the operating system to support POSIX (for
example, hierarchical directories).
Finally, you may encounter references to MPE V, which is the
operating system for HP 3000s, not based on PA-RISC architecture.
MPE V software can be run on the PA-RISC (Series 900) HP 3000s
in what is known as compatibility mode .
In This Book
This manual is your guide to starting, shutting down, and conguring
the 900 Series HP 3000.
Chapter 1 Introduction provides an overview of system startup,
conguration, and shutdown procedures.
Chapter 2 Initiating System Activity explains the initial portions
of the system bootup procedures including soft resets, hard resets,
system self testing, boot paths and working with AUTOBOOT.
Chapter 3 System Startup Functions explains the Initial System
Loader, starting, updating and installing the operating system, and
how to dump system memory.
Chapter 4 Using the System Generator (SYSGEN) introduces you to
SYSGEN and its congurator modules and explains how to generate
a System Load Tape.
Chapter 5 Modifying Input/Output (IO) Congurations explains how
to use SYSGEN's I/O Congurator and how to use the IOCONFIG
utility to make changes to the input and output devices used on the
system.
Chapter 6 Modifying Logging Congurators explains how to use the
LOG congurator to change the attributes of user and system logging
processes.
Chapter 7 Modifying Miscellaneous Conguration Elements explains
how to congure various system elements using SYSGEN's MISC
congurator.
Chapter 8 Modifying System File Congurations describes how to use
the SYSFILE congurator to change system libraries, programs, and
the system message catalog.
v
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 congure 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.
Appendix C Reading Stable Storage and Nonvolatile Memory
explains how to use the READSS and READNVM commands to provide
information to your Customer Engineer in case of system problems.
Appendix D Default Congurations Used by INSTALL and UPDATE
explains default conguration groups.
Appendix E Verifying Attached Devices explains two ISL utitilities,
IOMAP and ODE.
Appendix F Adding Peripherals to a System explains how to dene
device paths for peripherals connected to a system via three dierent
kinds of device adapters.
Appendix G UPS and UPS Monitor/iX Software explains the new
method of power failure protoection available on some Series 900
systems.
The Glossary denes the important terms introduced in system
management. The Index is an alphabetical listing of subjects,
cross-referenced with their location in the manual.
This manual contains information subject to change without notice.
vi
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. For example:
COMMAND
can be entered as any of the following:
command
Command
COMMAND
It cannot, however, be entered as:
comm
italics
com_mand
comamnd
In a syntax statement or an example, a word in italics represents a
parameter or argument that you must replace with the actual value.
In the following example, you must replace lename with the name
of the le:
COMMAND lename
bold italics
In a syntax statement, a word in bold italics represents a parameter
that you must replace with the actual value. In the following
example, you must replace lename with the name of the le:
COMMAND(lename)
punctuation
In a syntax statement, punctuation characters (other than brackets,
braces, vertical bars, and ellipses) must be entered exactly as shown.
In the following example, the parentheses and colon must be entered:
(lename):(lename)
underlining
Within an example that contains interactive dialog, user input and
user responses to prompts are indicated by underlining. In the
following example, yes is the user's response to the prompt:
Do you want to continue? >> yes
{
}
In a syntax statement, braces enclose required elements. When
several elements are stacked within braces, you must select one. In
the following example, you must select either ON or OFF:
COMMAND
[
]
ON
OFF
In a syntax statement, brackets enclose optional elements. In the
following example, OPTION can be omitted:
COMMAND lename [OPTION]
When several elements are stacked within brackets, you can select
one or none of the elements. In the following example, you can select
OPTION or parameter or neither. The elements cannot be repeated.
COMMAND lename
OPTION
parameter
vii
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][...]
In the example below, you only use the comma as a delimiter if
parameter is repeated; no comma is used before the rst occurrence
of parameter :
[parameter][,...]
| ... |
In a syntax statement, horizontal ellipses enclosed in vertical bars
indicate that you can select more than one element within the
immediately preceding pair of brackets or braces. However, each
particular element can only be selected once. In the following
example, you must select A, AB, BA, or B. The elements cannot be
repeated.
A
| ... |
B
...
In an example, horizontal or vertical ellipses indicate where portions
of an example have been omitted.
In a syntax statement, the space symbol 1 shows a required blank.
In the following example, parameter and parameter must be
separated with a blank:
1
(parameter)1(parameter)
The symbol 4 5 indicates a key on the keyboard. For example,
4RETURN5 represents the carriage return key or 4Shift5 represents the
shift key.
4CTRL5character 4CTRL5character indicates a control character. For example, 4CTRL5Y
means that you press the control key and the Y key simultaneously.
4
viii
5
Contents
1. Introduction
What Is System Startup? . . . . . . .
How system startup is carried out . .
What Is System Conguration? . . . .
How System Conguration Is Performed
What Is System Shutdown? . . . . . .
How system shutdown is carried out .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2. Initiating System Activity
Resetting the System . . . . . . . . . . . . . .
Soft Reset . . . . . . . . . . . . . . . . . .
Hard Reset . . . . . . . . . . . . . . . . .
Resetting the system using the console . . . . .
Resetting the system with the front panel switches
Determining and Selecting Input and Output (I/O)
Paths . . . . . . . . . . . . . . . . . . .
Series 922 through Series 949 boot paths . . . .
Series 950 through Series 980 boot paths . . . .
Testing the System . . . . . . . . . . . . . . .
The Booting Process . . . . . . . . . . . . . .
Autobooting the system . . . . . . . . . . . .
Interrupting an autobooting system . . . . . . .
Interactively booting the system with autoboot
disabled . . . . . . . . . . . . . . . . .
Bypassing the disabled autoboot setting . . . . .
System Startup Procedure . . . . . . . . . . . .
3. System Startup Functions
Initial System Loader (ISL) . . . . . . . . . . .
Using initial system loader (ISL) commands . . .
Using the help facility for ISL commands . . . .
Listing Available ISL Utilities . . . . . . . . .
Activating and Deactivating Autoboot and Autosearch
Functions . . . . . . . . . . . . . . . . .
Modifying boot paths in stable storage . . . . .
Displaying current boot path, autoboot, and
autosearch settings . . . . . . . . . . . .
Setting fastsize . . . . . . . . . . . . . . . .
Listing autoboot le contents . . . . . . . . .
Reading Nonvolatile Memory (NVM) . . . . . . .
Reading stable storage . . . . . . . . . . . .
Reading and setting the hardware clock . . . . .
1-1
1-1
1-2
1-2
1-3
1-3
2-1
2-1
2-1
2-2
2-5
2-8
2-8
2-9
2-11
2-12
2-12
2-13
2-17
2-18
2-19
3-1
3-2
3-3
3-5
3-6
3-7
3-8
3-8
3-9
3-9
3-9
3-9
Contents-1
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 . . . .
Updating the system conguration: a preview . .
Updating to recover from system failure: a preview
Backing up the system and retaining the current
conguration . . . . . . . . . . . . . . .
Installing the Operating System . . . . . . . . .
Using the INSTALL utility to recover a lost system
Scheduling an INSTALL . . . . . . . . . . . .
Using the INSTALL utility and options . . . . .
Installing the operating system: a preview . . . .
Back up the system and retain the current
conguration . . . . . . . . . . . . . . .
Dumping System Memory and Secondary Storage .
What is the function of the DUMP utility? . . .
Using the DUMP utility and options . . . . . .
Entering the DUMP utility and starting the system
ISL Summary . . . . . . . . . . . . . . . .
4. Using the System Generator (SYSGEN)
Entering the SYSGEN Global Module . . . . . . .
Using the Help Facility in SYSGEN's Global Module
Using First-Level (Global Module) Commands . . .
SYSGEN Command Syntax . . . . . . . . . . .
Halting SYSGEN Command Actions . . . . . . .
Specifying the Base Group . . . . . . . . . . . .
Conrming Potentially Serious Actions . . . . . .
Showing the State of Congurators . . . . . . . .
Activating the Congurators . . . . . . . . . . .
Clearing Conguration Changes . . . . . . . . .
Saving Conguration Changes . . . . . . . . . .
Generating a System Load Tape . . . . . . . . .
Redirecting SYSGEN Input and Output . . . . . .
Exiting SYSGEN . . . . . . . . . . . . . . . .
Contents-2
3-11
3-12
3-12
3-13
3-16
3-26
3-26
3-27
3-27
3-28
3-29
3-29
3-30
3-30
3-31
3-32
3-32
3-33
3-34
3-34
3-34
3-35
3-35
3-40
4-2
4-4
4-6
4-8
4-8
4-9
4-10
4-14
4-15
4-17
4-17
4-18
4-22
4-24
5. Modifying Input/Output (I/O) Congurations
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 Congurator . . . . . . .
Getting help with I/O Congurator commands . .
Using I/O Congurator commands . . . . . . .
Viewing the current conguration . . . . . . .
Printing the conguration information . . . .
Sample conguration data . . . . . . . . . .
Adding Objects in SYSGEN . . . . . . . . . .
Changing Congurations in SYSGEN . . . . . .
Deleting Objects in SYSGEN . . . . . . . . .
Changing the conguration online . . . . . . .
Using the IOCONFIG Utility . . . . . . . . . .
Adding a device with IOCONFIG . . . . . . .
Listing one or more devices with IOCONFIG . .
Deleting a device with IOCONFIG . . . . . . .
Adding a device class with IOCONFIG . . . . .
Modifying a device class with IOCONFIG . . . .
Listing one or more device classes with IOCONFIG
Deleting a device class with IOCONFIG . . . . .
Conguring a device adapter with IOCONFIG . .
Listing an I/O path with IOCONFIG . . . . . .
Deleting an I/O path with IOCONFIG . . . . .
Updating the device class association table with
IOCONFIG . . . . . . . . . . . . . . . .
6. Modifying Logging Congurations
Entering the LOG Congurator . . . . .
Using the LOG Congurator Help Facility .
Showing Current LOG Values . . . . . .
Logging System Events . . . . . . . . .
Logging User Events . . . . . . . . . .
Clearing Log Conguration Changes . . .
Holding and Saving Conguration Changes
Entering an MPE Command from the LOG
Congurator . . . . . . . . . . . .
Exiting the LOG Congurator . . . . . .
Printing a Log File . . . . . . . . . . .
Printing a subset of a log le . . . . . . .
5-2
5-2
5-2
5-2
5-3
5-4
5-5
5-5
5-7
5-8
5-9
5-9
5-11
5-12
5-13
5-13
5-14
5-16
5-17
5-17
5-18
5-18
5-19
5-19
5-19
5-20
5-20
5-20
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-1
6-2
6-3
6-5
6-6
6-6
6-7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-7
6-8
6-8
6-9
Contents-3
7. Modifying Miscellaneous Conguration Elements
Entering the MISC Congurator . . . . . . . . .
Using the MISC Congurator Help Facility . . . .
Showing Values of Current Congurable Items . . .
Deleting Global Resource Identication Numbers (RIN)
Conguring Job-Related Limits . . . . . . . . .
Displaying Allocated Global RINs . . . . . . . .
Setting Resource Allocations . . . . . . . . . . .
Setting Session-Related Limits . . . . . . . . . .
Setting Sizes of Native Mode and Compatibility Mode
Stacks . . . . . . . . . . . . . . . . . . .
Setting Strings and String Parameters . . . . . . .
Clearing MISC Conguration Changes . . . . . .
Holding and Saving Conguration Changes . . . .
Entering an MPE Command from the MISC
Congurator . . . . . . . . . . . . . . . .
Exiting the MISC Congurator . . . . . . . . . .
8. Modifying System File Congurations
Entering the SYSFILE Congurator . . . . . . .
Using the SYSFILE Congurator Help Facility . . .
Using SYSFILE Congurator Commands . . . . .
Displaying Current File Information . . . . . . .
Adding autoboot les . . . . . . . . . . . . .
Adding boot les . . . . . . . . . . . . . . .
Adding a segment to the compatibility mode
segmented library (CMSL) . . . . . . . . .
Adding le names to dump to tape . . . . . . .
Deleting Objects from the SYSGEN Tape . . . . .
Deleting autoboot images . . . . . . . . . . .
Deleting boot images . . . . . . . . . . . . .
Deleting compatibility mode segments from a
SYSGEN tape . . . . . . . . . . . . . .
Removing system programs from a SYSGEN tape
Replacing Objects on the SYSGEN Tape . . . . .
Replacing autoboot images . . . . . . . . . .
Replacing boot images . . . . . . . . . . . .
Conguring a message catalog . . . . . . . . .
Replacing a CMSL segment . . . . . . . . . .
Replacing or dening a network conguration le .
Replacing an IPL image . . . . . . . . . . . .
Replacing the native mode library . . . . . . .
Replacing a system program . . . . . . . . . .
Using a Segmented Library File as CMSL . . . . .
Listing CMSL Contents . . . . . . . . . . . . .
Clearing SYSFILE Congurator Changes . . . . .
Holding and Saving Conguration Changes . . . .
Entering an MPE Command from the SYSFILE
Congurator . . . . . . . . . . . . . . . .
Exiting the SYSFILE Congurator . . . . . . . .
Contents-4
7-1
7-2
7-4
7-7
7-7
7-8
7-9
7-10
7-11
7-12
7-13
7-13
7-14
7-14
8-1
8-2
8-4
8-6
8-8
8-9
8-10
8-10
8-11
8-11
8-11
8-12
8-12
8-12
8-13
8-14
8-15
8-15
8-16
8-16
8-17
8-17
8-18
8-18
8-19
8-19
8-19
8-20
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. Using the Access Port (AP)
Conguring the Console . . . . . . . . . . . . .
Entering Control Mode and Using the Command
Interpreter . . . . . . . . . . . . . . . . .
Interpreting the System Status Line . . . . . . .
Using Access Port Commands . . . . . . . . . .
Using the AP Help Facility . . . . . . . . . . .
Returning from Control Mode to Console Mode . .
Conguring the Access Port . . . . . . . . . . .
Enabling Remote Console Access . . . . . . . . .
Sending Messages to Both Consoles . . . . . . . .
Disabling Remote Console Access . . . . . . . . .
Disconnecting the Remote Line . . . . . . . . . .
Connecting the Remote Support Modem to a Session
Port . . . . . . . . . . . . . . . . . . . .
Enabling the SPU Hex Status Display . . . . . . .
Disabling the SPU Hex Status Display . . . . . .
Hard Resetting the SPU . . . . . . . . . . . . .
Transferring Control (Soft Reset) . . . . . . . . .
Testing the AP . . . . . . . . . . . . . . . . .
Using Control Commands . . . . . . . . . . . .
Entering control mode . . . . . . . . . . . .
Halting scrolling . . . . . . . . . . . . . . .
Allowing scrolling . . . . . . . . . . . . . .
Entering escape characters . . . . . . . . . . .
Changing master consoles . . . . . . . . . . .
Interpreting AP Error and Informational Messages .
Error Codes and Error Messages . . . . . . . .
Informational Messages . . . . . . . . . . . .
9-2
9-2
9-2
9-3
9-3
9-4
9-4
A-1
A-2
A-2
A-4
A-5
A-5
A-6
A-8
A-9
A-9
A-10
A-10
A-10
A-11
A-11
A-12
A-13
A-14
A-14
A-14
A-14
A-14
A-14
A-15
A-15
A-18
Contents-5
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 Congurations Used by INSTALL and UPDATE
Copying Default Conguration File Groups . . . .
D-3
Overview . . . . . . . . . . . . . . . . . .
D-3
Using SYSGEN to Copy the Files . . . . . . . .
D-4
E. Verifying Attached Devices
Overview . . . . . . . . .
Displaying Congured Devices
Running IOMAP . . . . .
Exiting IOMAP . . . . .
Running ODE . . . . . .
Exiting MAPPER . . . .
Exiting ODE . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F. Adding Peripherals to a System
Series 917LX through Series 977 Systems . . .
HP-FL/SCSI Devices . . . . . . . . . . .
HP-FL Devices . . . . . . . . . . . . .
SCSI Devices . . . . . . . . . . . . .
Unit Identier . . . . . . . . . . . . . .
Series 920, 922, 932, 948, 958, 925, 935, 949 CIO
Systems . . . . . . . . . . . . . . . .
Channel Adapter . . . . . . . . . . . . .
Device Adapter . . . . . . . . . . . . .
HP-FL/HP-IB Devices . . . . . . . . . .
SCSI Devices . . . . . . . . . . . . . .
Unit Identier . . . . . . . . . . . . . .
Series 920, 922, 932, 948, 958 NIO Systems . .
Device Adapter . . . . . . . . . . . . .
HP-FL Devices . . . . . . . . . . . . . .
SCSI Devices . . . . . . . . . . . . . .
Unit Identier . . . . . . . . . . . . . .
Series 950 Through Series 980 Systems . . . .
Bus Converter . . . . . . . . . . . . . .
Channel Adapter . . . . . . . . . . . . .
Device Adapter . . . . . . . . . . . . .
HP-FL/HP-IB Devices . . . . . . . . . .
SCSI Devices . . . . . . . . . . . . . .
Unit Identier . . . . . . . . . . . . . .
HP-FL Peripherals . . . . . . . . . . . . .
Adding a Peripheral to Any System . . . . . .
Contents-6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
E-1
E-1
E-3
E-6
E-7
E-9
E-9
.
.
.
.
.
.
.
.
.
.
F-1
F-2
F-2
F-2
F-2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F-3
F-3
F-3
F-3
F-3
F-4
F-4
F-4
F-4
F-5
F-5
F-5
F-5
F-5
F-6
F-6
F-6
F-6
F-7
F-8
G. UPS and UPS Monitor/iX Software
Conguring a UPS device . . . . . . . . . . . .
To congure the rst UPS on a Series 9X8 . . . .
To congure 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 . . . . . . . . . . . . . . . . . . .
G-2
G-2
G-3
G-4
G-5
G-6
G-6
G-8
Glossary
Index
Contents-7
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.
5-4.
5-5.
7-1.
7-2.
7-3.
7-4.
7-5.
8-1.
A-1.
A-2.
C-1.
D-1.
D-2.
Contents-8
AP Reset Commands . . . . . . . . . . . . .
ISL Commands. . . . . . . . . . . . . . . .
Execution of SYSSTART File Modules . . . . .
Utility Options . . . . . . . . . . . . . . . .
Utility Options . . . . . . . . . . . . . . . .
Summary of System Startup Functions . . . . .
Using First-Level Commands . . . . . . . . .
Actions Performed by Command File Example . .
Actions Performed by Command File LISTIT . .
IO Congurator Command Matrix . . . . . . .
I/O Congurator List Commands . . . . . . .
I/O Congurator Add Commands . . . . . . .
I/O Congurator Modify Commands . . . . . .
I/O Congurator Delete Commands . . . . . .
Minimum and Maximum Values for JOB Command
Parameters . . . . . . . . . . . . . . . .
Minimum and Maximum Values for RESOURCE
Parameters . . . . . . . . . . . . . . . .
Minimum and Maximum Values for SESSION
Parameters . . . . . . . . . . . . . . . .
Min. and Max. Values for STACK Parameters . .
Default Values for SYSTEM Parameters . . . . .
SYSFILE Congurator Command Matrix . . . .
Status Line Display . . . . . . . . . . . . .
Access Port Commands . . . . . . . . . . . .
Codes for ISL Utility Names. . . . . . . . . .
Default Congurations for the 900 Series . . . .
Default Congurations for the 900 Series (continued)
2-2
3-2
3-16
3-41
3-42
3-43
4-7
4-23
4-23
5-7
5-8
5-11
5-12
5-13
7-7
7-9
7-10
7-12
7-12
8-5
A-3
A-4
C-5
D-2
D-3
1
Introduction
This chapter denes system startup, system conguration, and
system shutdown. It also briey describes the procedures for starting,
conguring, 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. System
startup does not refer to installing the system for the rst time.
(A separate installation guide for your rst loading of the new
fundamental operating software (FOS) comes with each FOS tape.
See note below.) Also, system startup does not refer to turning on
the power to the computer, disk drives, tape drives, printers, or the
system console. Normally, computer hardware remains powered on
continuously.
System startup involves several steps:
resetting the system
placing system les on the system disk, if the les do not already
reside there
starting the system using an autoboot or interactive sequence
Starting procedures are administered and controlled through initial
system loader (ISL) utilities.
The initial system loader is software that provides a command-driven
user interface for accessing boot utilities or issuing commands to
display or change system startup functions. You can access ISL
by resetting the system. (Refer to Chapter 2 for information on
resetting the system.)
The START utility enables the system operator or system manager
to start (boot or initialize) the system after system les have been
placed on disk by the ISL INSTALL or UPDATE utilities, or after
system memory has been stored to tape by the ISL DUMP utility.
Introduction 1-1
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. The autoboot sequence takes
its utility commands from an autoexecute le, also referred to as
an autoboot le, and requires no operator intervention to start the
operating system. The interactive sequence prompts the system
manager or system operator for the utility commands and options to
start the operating system.
Autoboot and interactive sequences are discussed in detail in
Chapter 2 and Chapter 3.
What Is System
Configuration?
System conguration is the means by which you dene, in terms
meaningful to the operating system, any or all of the peripheral
devices attached to the computer for the input (entering) or output
(storing or displaying) of data. Such devices include terminals,
printers, disk drives, and tape drives.
System conguration also includes the denition or modication
of system parameters other than the input/output (I/O) device
conguration. These parameters include system tables, the message
catalog, user logging processes, system logging events, and other
system resources.
How System
Configuration Is
Performed
System conguration and generation procedures are administered and
controlled through the system generator (SYSGEN) utility.
SYSGEN is a program that enables a user with system manager
(SM) capability to view, create, modify, and save system I/O
conguration data. (A user with system supervisor (OP) capability
may only view I/O conguration data.) In addition, the system
manager can add, remove, and replace system boot les and system
libraries by creating a system load tape (SLT).
The system stores conguration data in groups and allows for
multiple groups to reside on disk. SYSGEN builds on an existing
conguration group to change that conguration or to create a new
conguration. The new conguration data can be stored on disk or
tape. This SLT tape can then be used to install an entirely new copy
of the operating system or to update an existing copy.
1-2 Introduction
Note
What Is System
Shutdown?
How system shutdown
is carried out
SYSGEN does not support conguring terminals into the system.
For information on terminal conguration, refer to the HP 3000/iX
Network Planning and Conguration 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.
Shutdown procedures are performed by the system console command:
4CTRL5A
=SHUTDOWN
The =SHUTDOWN command logs o all remaining sessions, including
the session logged on at the console. All system processes are
stopped in an orderly manner. Completing all system activity and
processing before shutdown, maintains the integrity of all system
tables and directories.
Shutting down the system consists of several steps:
telling users well in advance of a planned shutdown
warning users a few minutes before the shutdown
preventing anyone from starting a new job or session, or printing
new reports
clearing the backlog of reports before the shutdown
answering any console requests
shutting open communication lines
suspending or aborting any jobs, and aborting sessions
entering the =SHUTDOWN command
Chapter 9 outlines detailed procedures for shutting down the system.
Introduction 1-3
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. The initial system loader (ISL), a boot-devicebased IPL utility, provides the user interface for displaying or
modifying system startup functions.
Resetting the
System
Soft Reset
There are two general types of resets for the 900 Series HP 3000: a
soft reset and a hard reset.
A soft reset , the type of reset used most often, preserves the current
processor state. This type of reset performs a nondisruptive memory
test and terminates all I/O operations before executing recovery
software for starting the boot device and console selection process. A
soft reset can also occur during a software reboot at the completion
of a bootable ISL utility, such as INSTALL, UPDATE, or DUMP.
More information on issuing resets from the console is provided later
in this chapter.
Note
Hard Reset
You can also initiate soft resets on the Series 922 through Series 949
systems by using the front panel RESET switch, which is described
later in this chapter.
A hard reset is disruptive. It initiates the processor self-test that
resets memory and terminates all I/O operations. A hard reset is
necessary after a hardware failure or after an error from which the
system cannot recover.
A hard reset is initiated when the CPU is powered on. If the system
is powered on already, then entering the reset command, RS, at the
system console initiates the hard reset process. Using the front panel
RESET switch on the Series 950 through Series 980 systems, shown
in gure 2-2, also performs a hard reset; however, you should use this
switch for a hard reset only if the RS command fails. (The RESET
Initiating System Activity 2-1
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. In addition to providing other features and
commands, the AP allows the system manager or system operator
(OP capability) to issue hard or soft resets from the console keyboard
instead of using the front panel reset switch. (The system is secured
from anyone accidentally entering an AP command. It responds to
AP commands only when the console is placed in control mode by
entering 4CTRL5 4B5.)
The access port supports two two-character commands for resetting
the system, as described in Table 2-1.
Table 2-1. AP Reset Commands
Command
Description
RS
Reset SPU (hard reset). This command, is equivalent to
using the RESET switch on Series 950 through 980 systens
or to powering on Series 922 through Series 949 systems. RS
initiates a processor self-test that resets memory and
terminates all I/O operations. Do not use this type of reset
in preparation for a dump.
TC
Transfer of control (soft reset). This command, equivalent to
using the RESET switch on Series 922 through 949 systems,
initiates a reset that preserves the current processor state,
terminates all I/O operations, and performs a nondisruptive
memory test.
Refer to Appendix A for details about using the AP support interface
for functions other than resetting the system.
2-2 Initiating System Activity
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. Enter:
Note
If you have a 99X system, you must transfer to the service processor
before you reset the system.
CM> SP
d
a
CM> RS ** Hard reset **
or
c
CM> TC ** Soft reset **
b
If you have a 9X8LX or 9X8RX system, a PDC menu is displayed
when you issue 4CTRL5 4B5. From that menu, you can proceed to boot
your system by typing BO. No specic reset is required.
Example 2-1 demonstrates a soft reset of the system with autoboot
disabled using the console and AP commands for a Series 949 system.
The reset screen may a contain dierent boot path and additional
information, depending on the system you are using.
Initiating System Activity 2-3
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 answer YES to
the primary path prompt, the system displays additional messages as
it boots the processor and operating system.
Example 2-2 demonstrates a soft reset of the system with autoboot
enabled, using console and AP commands for a Series 949 system.
The reset screen may contain a dierent boot path display and
additional information, depending on the system you are using.
Note
If you have a 99X system, you must transfer to the service processor
before you reset the system.
CM> SP
If you have a 9X8LX or 9X8RX system, you need to type BO to boot
the system from the primary path.
d
CM> TC
a
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
c
2-4 Initiating System Activity
Autoboot from primary path enabled.
To override, press any key within 10 seconds.
Example 2-2. Resetting a Series 949 System Using AP Commands
Autoboot & Enabled
b
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. This does not present any
problems; just continue with the START command in ISL.
As indicated above, it is recommended that hard resets be done from
the console rather than from the RESET switch whenever possible.
The following information discusses using the RESET buttons.
The reset switch (a lock labeled "ENABLED, SECURED, and
RESET") for the Series 922 through Series 949 systems is located
behind the cover on the right end of the access panel. Figure 2-1
indicates the location of the switch on these systems.
Figure 2-1.
Location of Series 922 through Series 949 Systems Reset Switch
The reset button (a gray button marked Reset) for the Series 950
through 980 systems is located underneath the cover of the horizontal
portion of the system control panel. Figure 2-2 indicates the location
of this button on these systems.
Initiating System Activity 2-5
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.
Do not use the reset button to reset Series 950 through Series 980
systems for a dump. Resetting these systems with the reset button
invalidates dump data.
Pressing the reset button on Series 950 through Series 980 systems
initiates a hard reset.
Resetting Series 922 through Series 949 systems by placing the key in
the reset switch and turning the key to RESET initiates a soft reset.
The system responds by self-testing its components and issuing
messages. Example 2-3 demonstrates the messages received at the
consoles of a Series 949 system. The reset screen may contain a
dierent boot path display and additional information, depending on
the system you are using.
2-6 Initiating System Activity
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. If you answer YES to
the primary path prompt, the system displays additional messages
as it boots the processor and operating system. (Information on
appropriate boot paths is provided later in this chapter.)
The messages received after a system is reset depend on whether
autoboot is enabled. Recall that autoboot describes the system's
capability to boot itself (without operator intervention) after it has
been reset. Messages from a system with autoboot enabled dier
from the messages received at a system with autoboot disabled.
Example 2-4 demonstrates the messages received from a Series 949
system.
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
Autoboot from primary path enabled.
To override, press any key within 10 seconds.
Example 2-4. Resetting a Series 949 System Using the Reset
Switch: Autoboot Enabled
If you do not press a key to interrupt the autoboot sequence, the
system displays messages as it automatically boots the processor and
the operating system.
Initiating System Activity 2-7
b
Determining and
Selecting Input and
Output (I/O) Paths
The system identies 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.
These boot paths consist of the primary boot path, for booting from
disk-resident software; the alternate boot path, for booting from a
system load tape; and the console boot path, for locating console
operator intervention.
Boot paths for the primary boot device, the alternate boot device,
and the console are shown as numbers separated by periods.
Series 922 through
Series 949 boot paths
Each I/O path is constructed "top down" from where the device is
physically attached to the system. The Series 922 through Series 949
I/O path is determined by the channel adapter (CA) module number,
the device adapter (DA) slot number, and the device address:
CA Module Number.DA Slot Number.Device Address
The CA module number species the number of card slots in the
central bus (CTB) that the channel adapter is attached to, multiplied
by four. The Series 922 through Series 932 CA modules are assigned
a numerical value of 4 or 8. The Series 935 CA module is assigned a
numerical value of 4 or 36. The Series 949 CA module is assigned a
numerical value of 8 or 40.
DA slot numbers range from 0 to 13. Slots 0 through 7 are
recommended for use.
The address of the device itself depends on the adapter. In addition,
data communication devices may have an additional logical or virtual
device number in the I/O path specication.
For example, in gure 2-3 the CA module number is 4, the HP-IB
channel CIB interface slot is 5, and the magnetic tape device address
is 0. This establishes an I/O path for the tape drive as 4.5.0.0.0.0.0.0.
Trailing zeros (those occurring after the third digit) are intended for
future use.
2-8 Initiating System Activity
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. An I/O device connects to a
device adapter card through an interface cable.
A Series 950 through Series 980 I/O path is specied as follows:
BUS CONV/CA Module Number.DA Slot Number.Device Address
The bus converter species the number, either 2 or 6, of the interface
slot that contains the adapter boards for the SMB and the central
bus.
The CA module number species the number of the interface slot
that contains the adapter boards for the central bus and the CIB.
The CA module number is assigned a numerical value of 4, 8, 16, 20,
or 24.
DA CIO section slot numbers range from 0 to 4.
The address of the device itself depends on the adapter. In addition,
data communication devices may have an additional logical or virtual
device number in the I/O path specication.
In gure 2-4, for example, the bus converter is 6, the CA module
number is 4, the HP-IB channel CIB interface slot is 3, and the
Initiating System Activity 2-9
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
congured by using the LPATH command of the SYSGEN utility IO
Congurator. SYSGEN does not tell you if the congured device is
2-10 Initiating System Activity
active or available. During the system boot (using the ISL START
command), information on which paths have been congured 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.) For 9X8LX and
9X8RX systems, use the ODE utility to list devices on the system.
Testing the System
A 900 Series HP 3000 system undergoes a self-test upon reset.
The Series 922 through Series 949 systems test various system
components including:
central processing unit (CPU)
instruction unit
execution unit
oating-point coprocessor
register le
translation look-aside buer (TLB)
cache boards
installed memory controllers and arrays
all I/O cards that have built-in, executable test routines
The self-test also initializes the channel I/O adapter (CA) and device
adapter (DA) boards along with the rst memory controller.
The Series 950 through Series 980 systems verify that enough
hardware is functioning to load and execute extended diagnostic
programs from initial program load (IPL). This involves testing the
processor, the rst memory controller, the console and boot devices,
and the I/O paths to the console and boot devices.
If the initial Series 950 through Series 980 self-test is successful, the
code performs a full processor test by testing the following:
nonvolatile memory (NVM)
stable storage
central processing unit (CPU)
system interface unit (SIU)
cache boards
translation look-aside buer (TLB)
After resetting and testing, the system either autoboots or initiates
an interactive boot sequence. Whether or not the system autoboots
depends on how the autoboot ag is set and the presence of an
autoboot le. For information on using the AUTOBOOT command, refer
to Chapter 3.
Initiating System Activity 2-11
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.
Autobooting the system
Autobooting allows you to boot the system from the primary boot
path without the need to make any keyboard entries.
Boot messages vary slightly depending on whether autoboot is
enabled. The following examples show some typical boot sequences
and illustrate use of the material covered up to this point (resetting
the system, system self- test, and using I/O paths).
Autobooting a system is usually accomplished by enabling autoboot
with the ISL AUTOBOOT command, resetting the system, and following
the system's prompts. For information on the AUTOBOOT command,
refer to Chapter 3.
Even when autoboot is disabled (or you have interrupted an enabled
autoboot sequence as described in the next section), the system still
allows you the option of autobooting by issuing an Interact with
IPL (Y or N)?> message. (Bypassing a disabled autoboot ag setting
to autoboot a system is discussed later in this chapter.)
Example 2-5 demonstrates autobooting a Series 925 system. The
example is a partial listing of an uninterrupted autoboot (autoboot
enabled) sequence. The screen may contain a dierent boot path
display and additional information, depending on the system you are
using.
Note
2-12 Initiating System Activity
If you are using a Series 949 system, your primary boot path is 8.1.0.
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.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
c
ISL
booting START AUTO
.
.
.
Example 2-5. Autobooting a Series 925 System
In example 2-5, autoboot must be turned on, and an autoboot
le (also known as an autoexecute le) must reside in the logical
interchange format (LIF) directory for ISL to autoboot. If
not, you get the message Cannot find an autoexecute file.
AUTOBOOT ABORTED. For information on turning on autoboot, refer
to Chapter 3. For information on replacing autoboot les using
SYSGEN, refer to Chapter 8.
Interrupting an
autobooting system
Even with the autoboot sequence in eect, you can override it
to select an alternate boot medium (for example, a tape drive or
another disk drive), to activate a dierent ISL utility, or to enter a
dierent set of options. This is accomplished by pressing any key
within 10 seconds after receiving the message that autoboot has been
enabled.
Example 2-6 provides a partial listing of an interrupted autoboot
sequences for a Series 925. Other systems may display dierent
messages and boot paths.
Initiating System Activity 2-13
b
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.
Console IO Dependent Code (IODC) revision 4
Boot
IO Dependent Code (IODC) revision 4
Interact with IPL (Y or N)?> y
Soft Booted.
MMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
c
ISL>
Example 2-6. Interrupting Autobooting Series 925 System.
b
When the sequence is interrupted, you are asked to select whether
the system should boot from the primary system disk or from a
system load tape on the alternate boot path. A third prompt allows
you to enter a dierent boot path interactively. As another option, if
you enter a "?" at the Enter boot path, command, or ? prompt, you
see a menu of boot command options.
The menu and boot command options can dier depending on your
system. Example 2-7 shows the menu for a Series 925 System.
2-14 Initiating System Activity
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. Boot Command Options for a Series 925 System
If you enter an improper boot path, forget to place the boot device
online, or if the disk or tape medium is defective, the system displays
a boot device status along with one or more four-character boot error
codes on the system console. Example 2-8 demonstrates a system's
possible response to an improper boot path.
Initiating System Activity 2-15
b
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.0
No device at indicated physical module -- check path
c
Boot from primary boot path (Y or N)?>
Example 2-8. A System's Response to an Improper Boot Path
A Series 950 system was used in example 2-8. Other 900 Series HP
3000 systems perform similarly, although their boot paths may be
dierent from the example shown. For an explanation of boot error
codes, refer to MPE/iX Error Message Manual Volumes I, II, and III
(32650-90066, 32650-90152, and 32650-90368).
The message Interact with IPL (Y or N)? gives you an additional
chance to autoboot even if you previously indicated an autoboot
override (or have autoboot disabled). Answering NO to the Interact
message returns the system to attempt an autoboot.
2-16 Initiating System Activity
b
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.
The screen display may contain a dierent boot path and additional
information, depending on the system you are using.
If you have a 99X system, you must transfer to the service processor
before you reset the system.
a
b
CM> SP
d
a
CM> TC
Processor Dependent Code (PDC) revision 3.2
Console path = 4.3.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
Boot from primary boot path (Y or N)?> y
Booting
Console IO Dependent Code (IODC) revision 4
Boot
IO Dependent Code (IODC) revision 4
Interact with IPL (Y N)?> y
Soft Booted.
NMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
c
ISL>
Example 2-9. Interactively Booting a Series 922 System
Initiating System Activity 2-17
b
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.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
48 MB of memory configured and tested.
Soft-Booted--memory state is valid
Boot from primary boot path (Y or N)?> n
Boot from alternate boot path (Y or N)?> n
Enter boot path, commands, or ?> 2/4.0.0
Interact with IPL (Y or N)?> n
Booting
Console IO Dependent Code (IODC) revision 4
Boot
IO Dependent Code (IODC) revision 4
Booted.
NMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.00 July 15, 1993
Cannot find an auto-execute file.
c
AUTOBOOT ABORTED.
ISL>
Example 2-10. Bypassing the Disabled Autoboot Setting When Booting a
System
2-18 Initiating System Activity
b
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.0.0.0.0.0.0
Alternate boot path = 6/4.3.0.0.0.0.0
Boot from primary boot path (Y or N)?> y
Interact with IPL (Y or N)?> Y
NMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
Cannot find an auto-execute file. AUTOBOOT ABORTED.
c
ISL>start recovery
Initialize_genesis - Version : <<870204.1552>>
THU, APR 27, 1989, 2:23:36PM (y/n)? y
.
.
.
Example 2-11. System Startup Procedure
b
Initiating System Activity 2-19
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.
2-20 Initiating System Activity
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.
When loaded, the ISL displays its revision number and prompts for
input:
ISL Revision A.00.07 September 12, 1990
ISL>
Note
Initial System
Loader (ISL)
The prompt changes to ISL>, indicating the ISL is active.
On tape boots, the ISL is loaded directly by the processor-dependent
code (PDC). ISL reads the logical interchange format (LIF) directory
from tape and uses this directory to nd other les on the tape.
On disk boots, the PDC and IODC boot the utility MMSAVE, which
in turn boots the ISL. PDC and IODC read the rst record or sector
of the boot device, which is the LIF label. The LIF label contains
a pointer to the MMSAVE boot image. PDC reads and launches
MMSAVE. MMSAVE writes a 16-megabyte section of main memory to
the DUMPAREA le, whose address is found in the LIF directory. This
allows memory space for the ISL and DUMP utilities to be loaded.
MMSAVE boots ISL, which then uses the LIF label to nd the LIF
directory. As a last step, ISL uses the directory to nd other les it
needs.
The system displays messages indicating the completion of the
booting and loading routines as they occur.
System Startup Functions 3-1
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 denitions, along with the
ISL utilities available through the selected boot
media.
LISTF or LS
Lists the ISL utilities available through the selected
boot media.
AUTOBOOT
Sets or clears the autoboot ag in stable storage.
(Stable storage is memory that retains its
information until overwritten. Stable storage stores
boot path information along with other critical
system parameters.)
AUTOSEARCH
Sets or clears the autosearch ag in stable storage.
PRIMPATH
Modies the primary boot path in stable storage.
ALTPATH
Modies the alternate boot path in stable storage.
CONSPATH
Modies the system console boot path in stable
storage.
DISPLAY or DI
Displays the current paths in stable storage for the
primary, alternate, and the console boot paths.
DISPLAY also shows the status of the autoboot and
autosearch ags.
LISTAUTOFL or
LSAUTOFL
Lists the contents of the current autoboot le.
FASTSIZE
Sets or displays FASTSIZE.
SUPPORT
Boots the support tape from the boot device.
READNVM
Displays the contents of 1 word (4 bytes) of
nonvolatile memory (NVM). (NVM is memory that
retains its information, in standard hexadecimal
format, until overwritten.) Specify the word address
in either decimal or hexadecimal.
READSS
Displays the contents of 1 word (4 bytes) of stable
storage. Specify the word address in either decimal or
hexadecimal. The display is in standard hexadecimal
format.
For more information on the contents of stable storage and NVM,
refer to Appendix C.
3-2 System Startup Functions
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.
Help Facility
Help Facility
List ISL utilities
List ISL utilities
Set or clear autoboot flag in stable storage
Set or clear autosearch flag in stable storage
Modify primary boot path in stable storage
Modify alternate boot path in stable storage
Modify system console path in stable storage
Display boot and console paths in stable storage
List contents of autoboot file
List contents of autoboot file
Sets or displays FASTSIZE
Boot the Support Tape from the boot device
Boot the Support Tape from the CDROM
Displays contents of one word of NVM.
Displays contents of one word of stable storage
List contents of batch file
List contents of batch file
Execute commands in batch file
List contents of EST (Extended Self Test) file
List contents of EST (Extended Self Test) file
Execute commands in EST (Extended Self Test) file
Example 3-1. Using the HELP Command
b
System Startup Functions 3-3
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
A1100AI
-12864 485824 856
89/11/28 16:21:54
A1100AM
-12864 486688 496
89/11/28 16:21:55
A1100AP
-12864 487184 3400
89/11/28 16:21:58
EDBC
-12864 537024 2080
94/11/53 16:43:49
EDPROC
-12864 539104 8848
94/11/53 16:43:55
LASIDIAG -12864 516688 752
94/11/53 16:43:56
LDIAG
-12864 517440 5808
94/11/53 16:44:00
MAPFILE
-12864 421600 16
94/11/53 16:44:00
MAPPER
-12864 523248 336
94/11/53 16:44:01
MDIAG
-12864 523584 6240
94/11/53 16:44:05
MEMTEST
-12864 421616 321
94/11/53 16:44:05
MPROC
-12864 447760 1408
94/11/53 16:44:07
ODE
-12864 421936 432
94/11/53 16:44:07
SYSLIB
-12864 422368 688
94/11/53 16:44:08
TDIAG
-12864 529824 7200
94/11/53 16:44:13
UNIPROC
-12864 453504 4464
94/11/53 16:44:16
BCDIAG
-12864 423056 960
94/11/53 16:44:17
CAEXR
-12864 444720 672
94/11/53 16:44:18
IOMAP
-12864 445392 1536
94/11/53 16:44:19
CLKUTIL
-12864 424016 312
94/11/53 16:44:20
SADPATCH -12864 446928 832
94/11/53 16:44:20
Example 3-1. Using the HELP Command (continued)
Note
3-4 System Startup Functions
a
b
The list of ISL utilities diers, depending upon whether they have
been loaded from tape or disk and upon which model of HP 3000 you
have. The utilities listed in examples 3-1 and 3-2 were loaded from
disk.
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.
d
a
ISL> LISTF
Utilities on this system are:
c
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
A1100AI
-12864 485824 856
89/11/28 16:21:54
A1100AM
-12864 486688 496
89/11/28 16:21:55
A1100AP
-12864 487184 3400
89/11/28 16:21:58
EDBC
-12864 537024 2080
94/11/53 16:43:49
EDPROC
-12864 539104 8848
94/11/53 16:43:55
LASIDIAG -12864 516688 752
94/11/53 16:43:56
LDIAG
-12864 517440 5808
94/11/53 16:44:00
MAPFILE
-12864 421600 16
94/11/53 16:44:00
MAPPER
-12864 523248 336
94/11/53 16:44:01
MDIAG
-12864 523584 6240
94/11/53 16:44:05
MEMTEST
-12864 421616 321
94/11/53 16:44:05
MPROC
-12864 447760 1408
94/11/53 16:44:07
ODE
-12864 421936 432
94/11/53 16:44:07
SYSLIB
-12864 422368 688
94/11/53 16:44:08
TDIAG
-12864 529824 7200
94/11/53 16:44:13
UNIPROC
-12864 453504 4464
94/11/53 16:44:16
BCDIAG
-12864 423056 960
94/11/53 16:44:17
CAEXR
-12864 444720 672
94/11/53 16:44:18
IOMAP
-12864 445392 1536
94/11/53 16:44:19
CLKUTIL
-12864 424016 312
94/11/53 16:44:20
SADPATCH -12864 446928 832
94/11/53 16:44:20
Example 3-2. Listing Available ISL Utilities
System Startup Functions 3-5
b
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. (Devices are searched from the smallest to the largest
physical address on the processor's bus.) If the boot device has an
incorrect data format, search for the next boot device. If no boot
device exists, or all have the incorrect data format, execute manual
selection.
Autoboot (autoboot on and autosearch o). Try to boot from the
primary boot device specied in stable storage. If the boot device
does not exist or has an incorrect data format, execute manual
selection. Once booted, execute (performed by ISL) an autoboot
le, which contains a command sequence, to bring up the operating
system without operator intervention. If the autoboot le does not
exist, prompt the operator for the utility command.
Autosearch (autoboot on and autosearch on). Try to boot from the
boot device path stored in stable storage. If the boot device does
not exist or has an incorrect data format, execute the boot search
selection. Once booted, execute (performed by ISL) an autoboot
le, which contains an autoboot sequence, to bring up the operating
system without operator intervention. If the autoboot le does not
exist, prompt the operator for the utility command.
To enable or disable these features, use the AUTOBOOT and
AUTOSEARCH commands. Enter one or both of the commands and the
desired setting (ON/OFF) at the ISL prompt. The system responds
with a message indicating the ag status:
ISL> AUTOBOOT ON
Autoboot is ON (enabled).
ISL> AUTOBOOT OFF
Autoboot is OFF (disabled).
ISL> AUTOSEARCH ON
Autosearch is ON (enabled).
ISL> AUTOSEARCH OFF
3-6 System Startup Functions
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.
The commands described in the above paragraph may disrupt
normal system functions if used inappropriately. For this reason,
do not attempt to use these commands without assistance from
Hewlett-Packard service personnel.
To execute any of these three commands, enter the command with its
appropriate parameter or enter 4Return5 after the command and wait
to be prompted for further input:
ISL> ALTPATH 6/4.3.0
or
ISL> ALTPATH
Enter alternate boot path: 6/4.3.0
To withdraw a command (without changing the path), enter 4Return5
after entering the command without any parameter. For example,
ISL> ALTPATH
Enter alternate boot path:
Invalid Input.
4Return5
Trailing zeros are not required when a boot path is entered:
ISL> PRIMPATH 2/4.0.0
ISL> CONSPATH 2/4.1.0
If an improper path format is entered, or you have withdrawn a
command as shown above, the system issues an Invalid Input
message. Then ISL prompts for a new command:
ISL> PRIMPATH 240
Invalid Input.
System Startup Functions 3-7
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
conguration listing from the SYSGEN utility. For more information
on SYSGEN, refer to Chapter 4.
The DISPLAY or DI command lists the autoboot and autosearch
settings, the primary boot path, the alternate boot path, and
the system console path held in stable storage. Use the DISPLAY
command to verify that correct information resides in stable storage.
Example 3-3 demonstrates using the ISL DISPLAY command. This
is an example from a Series 949 system. The boot paths may vary,
depending on the system.
d
ISL> DISPLAY
a
Fastsize value is 0000000F
Autoboot is ON (enabled)
Autosearch is OFF (disabled)
Primary boot path is 4.1.0.0.0.0.0
Primary boot path is (hex) 4.1.0.0.0.0.0
Alternate boot path is 4.5.0.0.0.0.0
Alternate boot path is (hex) 4.5.0.0.0.0.0
System console path is 4.2.0.0.0.0.0
System console path is (hex) 4.2.0.0.0.0.0
c
Setting fastsize
ISL>
Last utility launched from ISL was START
Example 3-3. Displaying an example of ISL Settings
If fastsize is set to the wrong value, you cannot do installs or
updates. The only value that is acceptable is \F." If you try to do an
update or install with fastsize set to the wrong value, you will receive
an error message that reads UTILITY REQUIRES MORE MEMORY THAN IS
CONFIGURED.
Consider the following example.
ISL> DISPLAY
Fastsize
value is 00000003
.
.
.
This fastsize value is invalid. You must reset it to \F"; therefore, at
the ISL prompt, enter Fastsize F, as in the following example.
3-8 System Startup Functions
b
ISL> FASTSIZE F
If you changed the value of fastsize, you must reset the system for
the new value to take eect. 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. This information
remains intact, even through system failures.
To read the contents of NVM, enter READNVM nn at the prompt,
where nn is the location to be read:
ISL> READNVM 68
Address 68 contains 0x32363334
For information on the contents and locations of NVM, refer to
Appendix C.
Reading stable storage
Stable storage stores boot path information along with other
critical system parameters. Like NVM, stable storage maintains its
information through system crashes and failures. Unlike NVM, stable
storage maintains its information even if the memory card, containing
stable storage, is removed from the backplane.
To read the contents of stable storage, enter READSS nn at the
prompt, where nn is the location to be read:
ISL> READSS 40
Address 40 contains 0XFFFFFF08
For information on the contents and locations of stable storage, refer
to Appendix C.
Reading and setting the
hardware clock
The ISL utility CLKUTIL reads and sets the battery backed-up
hardware clock. This clock maintains Greenwich Mean Time (GMT)
independently of the software clock that is displayed when you enter
the ISL START utility or any of the other ISL utilities that support
the software clock. (Refer to example 3-7 for an example of the
software clock interaction.). The CLKUTIL utility, therefore, reads the
date and time that were previously set with CLKUTIL, but does not
itself reect the changes that you may make while in any other ISL
utility.
System Startup Functions 3-9
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 oset and stores it in stable storage. During a
boot, the GMT and this oset are combined to produce the local
time, displayed on the console.
To read or set the hardware clock, enter:
ISL> CLKUTIL
The system responds with the following banner:
SYSTEM FOR ISL STAND ALONE UTILITIES. [IHO, SPU LAB]
Version 1.0
****** clock utility ************ ver 1.0 ***** 11/6/86
enter command : (r) read clock, (s) set clock >
To read the clock, enter r at the CLKUTIL prompt:
enter command :
(r) read clock, (s) set clock > r
The system responds with a message similar to the following:
THU, JAN 1, 1988, 9:00:16 AM
To set the clock, enter s at the CLKUTIL prompt:
enter command :
(r) read clock, (s) set clock > s
The system responds with a message similar to the following:
enter date
mm/dd/yyyy
When the enter date prompt appears, enter the date in the correct
format: mm is a two-digit number, 1-12, representing the month; dd
is a two-digit number, 1-31, representing the day of the month; and
yyyy is a four-digit number representing the year. (You can also
enter just the last two digits for the year.)
The system continues by issuing the following prompt:
enter time hh:mm:ss
Enter the time using Greenwich Mean Time in 24-hour format.
The system requests verication of the adjusted date and time by
issuing a message similar to the following:
THU, JAN 7, 1988, 11:17:00 PM
ok (y/n)?
Entering Y returns a message of:
clock set!
Entering N returns you to the enter date prompt.
3-10 System Startup Functions
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. Use this utility to
recover from a system hang or failure or to reboot the system after
scheduled downtime.
Bringing in the system from tape is referred to as a system load. The
system uses two utilities to perform a system load, which builds
essential operating system les and data structures on disk. The
two load utilities, UPDATE and INSTALL, have the option to boot the
system from disk once the load operation is complete.
The INSTALL utility completely replaces the contents of the disk
and places the base operating system les, including the system
conguration les, on disk. If you have installed a new system over
an already existing system, you can use the STORE/RESTORE utility to
restore the original system dictionary, other subsystem les, and user
les to the new system after the INSTALL is complete.
The UPDATE utility replaces the current base system les on disk and
optionally replaces system conguration les (if you name a dierent
conguration le when you use the UPDATE utility). If you do not
name another conguration le, the original le will remain after the
update.
The base system les contain the copy of the operating system to be
placed on disk. As part of every system, these les make a minimal
or base system. INSTALL and UPDATE utilities, optionally, attempt a
software reboot from disk.
The DUMP utility writes the current state of the system main memory
and secondary storage to tape for analysis. DUMP, also optionally,
attempts a software reboot from disk.
Depending on the utility and the options specied, the system either
halts at the end of the utility's execution or reboots from disk.
If you want to see a list of command options along with an
explanation of correct usage and default values, enter help at the ISL
prompt.
System Startup Functions 3-11
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 diers depending on the previously executed
boot command. For example, a START after an INSTALL executes
dierently than a START after a shutdown or reset. START after an
INSTALL may initialize the system member volumes. A START option
after an INSTALL or UPDATE does not restart jobs.
There are, primarily, six load and start utilities for the operating
system.
START or START RECOVERY
START NORECOVERY
UPDATE or UPDATE NOCONFIG
UPDATE CONFIG
INSTALL
DUMP
Using START and its
options
The ISL command for the START utility is START. The utility has
several options:
2
START ;GROUP=cgn
;SINGLE-DISC
;MULTI-DISC
;SYSSTART
;NOSYSSTART
32
;LOGON=acct
3
;RECOVERY
;NORECOVERY
;SINGLE-USER
;MULTI-USER
Specify START alone or with alternate options. Separate the options
from the command and other options with a blank or semicolon.
Using the ISL START command without listing any options:
ISL> START
is the same as specifying the following default options:
ISL> START GROUP=bootup LOGON=OPERATOR.SYS RECOVERY&
MULTI-USER MULTI-DISC SYSSTART
3-12 System Startup Functions
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 conguration information last used to boot the system, attempts
to log on as OPERATOR.SYS (if the OPERATOR user has been
created), to restart all jobs and allow all users access to the system,
to bring up all volumes present on the system, and to execute
commands found in the SYSSTART le, SYSSTART.PUB.SYS.
Enter an alternate option through a keyword parameter, or several
alternate options in groups of keyword parameters. The following
command line shows an example of using multiple alternate options:
ISL> START GROUP=CONFG950 LOGON=JOHN.SMITH NORECOVERY&
SINGLE-USER SINGLE-DISC
Executing commands
during system startup
The le SYSSTART.PUB.SYS executes automatically at system startup
if the SYSSTART parameter is specied in the START command. This
le can be used to set up the normal user environment automatically
when the system starts up. The contents of this le should include
command parameters appropriate for your environment, such as the
standard limits for jobs and sessions, spooler start commands, stream
device identication, outfence priorities, event logging, and so on.
These commands are then performed automatically for you whenever
the system is restarted.
A SYSSTART le can contain selected MPE commands (and their
parameters) that the system manager is allowed to execute except
networking commands. (Networking commands should be executed
from a job that is streamed from SYSSTART, or from a logon UDC for
OPERATOR.SYS .) You can use the following commands in a SYSSTART
le:
System Startup Functions 3-13
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.
Notice that each module must be separated by one or more asterisks.
The following SYSSTART le sample is an example of the type of
commands you might want to include in a SYSSTART le. It is not
intended to suggest entries for your system's SYSSTART le.
3-14 System Startup Functions
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.SYS/PASSWORD;HIPRI;NOWAIT
***
RELOAD
LIMIT 1,1
JOBFENCE 14
OUTFENCE 14
STARTSESS 20;MANAGER.SYS/PASSWORD;HIPRI;NOWAIT
Example 3-4. A Properly Formatted SYSSTART File
b
System Startup Functions 3-15
The STARTUP module is executed whenever the SYSSTART le is
accessed. Place commands and parameters specic 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. Execution of SYSSTART File Modules
Boot Utility Used
SYSSTART Module Executed
ANY
startup
START (RECOVERY)
warmstart
START (NORECOVERY)
coolstart
UPDATE (START)
update
INSTALL (START)
reload
The SYSSTART le must be created by MANAGER.SYS and needs to
reside on LDEV 1 to function properly. Once the le is created, use
the following commands to copy the le to the appropriate location:
HELLO MANAGER.SYS
FILE SYSSTART;DEV=1
FCOPY FROM=templename;TO=*SYSSTART;NEW
If an error exists in the SYSSTART le, the startup process ignores it
and continues execution.
Starting a 900 Series
HP 3000
The following steps comprise a procedure for booting MPE/iX on a
900 Series HP 3000 computer system using START following a reset.
To start the system, perform the following steps:
1. Power on all attached peripheral devices, and ensure that the
system disks are powered on.
2. Place the console in control mode. Enter:
4CTRL5 4B5
The console control mode prompt (CM>) should appear on the
console screen.
3. Reset the system using AP commands, boot from the primary
path, and enter the START command at the ISL prompt.
/need begin>
3-16 System Startup Functions
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.
System Startup Functions 3-17
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.
Console IO Dependent Code (IODC) Revision
Boot
IO Dependent Code (IODC) Revision
4
4
Interact with IPL (Y or N)?> Y
HARD Booted.
MMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
c
ISL> START
MPE/iX launch facility
Initialize_genesis - Version : <<870204.1552>>
TUE, JUN 27, 1990, 4:15:24 AM (y/n)? Y
[TMUX_DAM] 15 7 12 14
Initialize genesis completed.
Create Console Messages kso completed.
Initialize memory manager completed.
Initialize resident kernel completed.
Example 3-5. Example of a Hard Reset from a Series 935 System
3-18 System Startup Functions
b
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.
Begin binding compatibility mode SL
Compatibility mode SL binding complete
Create port process has been completed.
The following is a list of the boot options last boot command:
START
last configuration group:
CONFIG
current boot command START
current configuration group: CONFIG
last configuration group actually used by START: CONFIG
logon = OPERATOR.SYS
RECOVERY
MULTI-USER
MULTI-DISK
SYSSTART
c
Begin launching additional processors:
.
.
.
Entering - System I/O configuration.
The path 4 has already been configured.
The path 4.1 has already been configured.
The path 4.1.0 has already been configured.
The path 4.2 has already been configured.
The path 4.2.0 has already been configured.
The path 4.5.3 was configured but is not available.
The path 4.5.4 was configured but is not available.
The path 4.5.5 was configured but is not available.
The path 4.5.6 was configured but is not available.
The path 4.6.0 was configured but is not available.
The path 4.6.5 was configured but is not available.
The path 4.6.6 was configured but is not available.
The path 4.6.7 was configured but is not available.
Leaving - System I/O configuration.
Example 3-5. Example of a Hard Reset from a Series 935 System (continued)
System Startup Functions 3-19
b
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.1.1
4.1.3
4.1.4
4.6.5
4.5.7
4.5.0
4.5.3
4.5.5
4.2.0
4.5.6
4.5.4
MEMORY AVAILABLE FOR USE (bytes): 3554432
Entering
Mounting
Mounting
Mounting
Mounting
c
- Mount all volumes
MASTER on LDEV
MEMBER on LDEV
MEMBER on LDEV
MEMBER on LDEV
1
2
3
4
START AGGREGRATE RECOVERY of MPEXL_SYSTEM_VOLUME_SET
SYSTEM RECOVERY COMPLETED for
MPEXL_SYSTEM_VOLUME_SET
USERLOG RECOVERY COMPLETED for
MPEXL_SYSTEM_VOLUME_SET
NO PARALLEL PROCESSES FOR MOUNT_ALL_VOLUMES
-- Time spent in MOUNT_ALL_VOLUMES
15
Leaving - Mount all volumes
The current boot command has been saved on the system master.
NMLG FILE NUMBER 20 ON.
14:04/23/DCC STARTUP - ENTER - version C0104504 compiled 930712
14:04/23/ WARNING: I/O config from last START RECOVERY will be used (DCCWARN
=100)
[NETWORK_DUMP_SURR] Version A.00.47.03A
14:04/23/DCC STARTUP - OK
14:05/40/NRJE CANNOT CONFIGURE LDEV 12 INTO THE I/O SYSTEM
14:05/40/40DEVICE IS ALREADY CONFIGURED
14:05/40/NRJE CANNOT CONFIGURE VIRTUAL READER FOR WSID: R20
System State: Initializing Mode.
Reply Information Table has been initialized!
System State: Multiuser Mode.
14:05/1/Spooling of initally spooled devices is complete.
14:05/1/Set-up of Spooling Subsystem is complete.
Initializing Job & Session
Startup processing has begun.
Example 3-5. Example of a Hard Reset from a Series 935 System (continued)
3-20 System Startup Functions
b
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.
a
Initiate Operator Log On
Successfully launched diagnostic monitor process.
Warning - Protection of the system file
'AUTOBOOT.MPEXL.SYS', failed.
c
16:54/36/INVALID PASSWORD FOR "OPERATOR.SYS,OPS" DURING
LOGON ON LDEV #20. (js 65)
ENTER ACCOUNT PASSWORD:
MPE XL:
Example 3-5. Example of a Hard Reset on a Series 935 System (continued)
System Startup Functions 3-21
b
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.2
DUMPAREA protected, proceeding to ISL without memsave
ISL loaded
ISL Revision A.00.28 July 15, 1993
Cannot find an auto-execute file.
AUTOBOOT ABORTED.
ISL> START
MPE/iX launch facility
Initialize_genesis - Version : <<870204.1552>>
c
THU, MAY 24, 1990, 4:28:32 PM (y/n)?
Example 3-6. Example of a Soft Reset on a Series 950 System
3-22 System Startup Functions
b
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.
Opening the native system library completed.
Initialize process management completed.
Initialize debug subsystem completed.
Initialize file system completed.
Initialize loader completed.
Initialize non-resident services completed.
Begin binding compatibility mode SL
Compatibility mode SL binding complete
Create port process has been completed.
Warning - Protection of the system file
`AUTOBOOT.MPEXL.SYS', 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
c
Entering
The path
The path
The path
The path
The path
The path
The path
The path
The path
The path
- System I/O configuration.
2 has already been configured.
2/4 has already been configured.
2/4.0 has already been configured.
2/4.0.0 has already been configured.
2/4.0.2 was configured but is not available.
2/4.1 has already been configured.
2/4.1.0 has already been configured.
2/4.3.0 was configured but is not available.
2/4.3.4 was configured but is not available.
2/4.3.5 was configured but is not available.
Example 3-6. Example of a Soft Reset on a Series 980 System (continued)
System Startup Functions 3-23
b
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.5 was configured but is
The path 6/4.3.7 was configured but is
Leaving - System I/O configuration.
not
not
not
not
not
not
not
not
not
not
not
not
not
not
available.
available.
available.
available.
available.
available.
available.
available.
available.
available.
available.
available.
available.
available.
a
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:
c
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
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
available
available
not-available
available
available
not-available
not-available
not-available
available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
MEMORY AVAILABLE FOR USE (bytes)
2/4.0.0
2/4.0.1
2/4.0.2
6/4.3.6
6/4.3.0
2/4.3.0
6/4.3.7
6/4.3.4
2/4.1.0
6/4.0.0
6/4.0.1
6/4.0.2
2/8.0.0
2/8.0.1
2/8.0.2
2/8.0.3
6/4.3.5
2/4.3.4
2/8.1.0
2/8.1.1
2/8.1.2
2/8.1.3
2/4.3.5
: 33554432
Example 3-6. Example of a Soft Reset on a Series 980 System (continued)
3-24 System Startup Functions
b
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. 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. 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. The ldev is
Warning
- Volume is not available for mounting. The ldev is
Warning
- Volume is not available for mounting. The ldev is
Leaving - Mount all volumes
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.
SYSTEM LOG FILE #1 IS ON
Initializing Job & Session
Initiate Operator Log On
SESSION Scheduling Initialized
JOB Scheduling Initialized
Successfully launched diagnostic monitor process.
ACCT EXISTS, USER NAME DOESN'T. (CIERR 1438)
16:31/24/MISSING USER NAME DURING LOGON ON LDEV #20. (js 11)
MPE XL:
3
25
26
27
28
31
32
33
34
21
22
23
Example 3-6. Example of a Soft Reset on a Series 980 System (continued)
System Startup Functions 3-25
b
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.
Specic update and installation instructions are subject to change.
This manual provides you with an overview of the procedures
involved.
For more specic information on using MPE/iX and initial system
loader (ISL) commands, options, and utilities to update your
operating system for a particular new release, refer to the appropriate
version of HP 3000 MPE/iX Installation, Update, and Add-On
Manual (36123-90001). This manual is included with the software
tapes for each new release and contains information specic for that
release.
The ISL utility
The ISL utility UPDATE is more commonly used than INSTALL. The
UPDATE utility replaces the base system les on the system disk with
those from a boot tape. Optionally, you can update the conguration
data les in the group CONFIG.SYS.
Before any other les are restored, UPDATE veries that the system
disk is a valid main system disk. If not, UPDATE halts with an error
message.
The UPDATE utility is primarily used to replace a current version of
the operating system with another version, but you can also use the
UPDATE utility to aid in recovering from a severe system failure.
If your system fails, you have many options to use to help recover
your system. Use UPDATE as a recovery method only after doing the
following:
attempting a START RECOVERY
attempting a START NORECOVERY
ensuring the validity of your START procedure
ensuring that your hardware, hardware code, and current software
are functioning properly
Caution
3-26 System Startup Functions
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).
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.
If you are using the UPDATE utility to replace a current version of
the operating system with a newer version, schedule the update for
o-peak hours. The update procedure can take up to four hours,
depending on the system and the number of subsystem products you
have purchased. To reduce the time involved in ensuring the integrity
of your backups, schedule the UPDATE immediately after a full system
backup.
Using the UPDATE
utility and options
The command to invoke the UPDATE utility is UPDATE. The utility
has two initial options, CONFIG/NOCONFIG and START/NOSTART, with
additional options if START is selected:
UPDATE
;CONFIG
;NOCONFIG
where options are:
;SINGLE-DISC
;MULTI-DISC
;SYSSTART
;NOSYSSTART
2
;START
;NOSTART
32
2
options
;LOGON=acct GROUP=cgn
;SINGLE-USER
;MULTI-USER
3
3
The CONFIG/NOCONFIG option allows you to indicate whether you
wish to replace the conguration les in the group CONFIG.SYS on
disk with any that may exist in the group CONFIG.SYS on the tape.
(The CONFIG.SYS group on a factory tape is empty; however, a
customer-generated tape may contain conguration data.)
The START/NOSTART option allows you to choose whether or not to
autoboot once the update is complete. If you specify START as an
option, or accept it as the default, the remaining START options
become available.
Refer to table 3-4 for more information on the START options
available for an update. Enter the options in any order, and separate
them from the command and other options by a blank or semicolon.
Entering the command UPDATE without listing any options
ISL> UPDATE
is the same as specifying the following default options:
ISL> UPDATE NOCONFIG START GROUP=CONFIG LOGON=&
OPERATOR.SYS MULTI-DISC MULTI-USER SYSSTART
System Startup Functions 3-27
The UPDATE utility with its default options instructs the system to
perform these tasks:
update the existing operating system without replacing the
conguration data les on disk
autoboot the system from disk after the update is completed
use the conguration 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.
allow access to all mounted volumes by all users
execute the commands in the system startup le,
SYSSTART.PUB.SYS, if it is present
Restarting of jobs is not permitted after either an UPDATE or an
INSTALL, because no jobs exist after an UPDATE or an INSTALL.
Updating the operating
system: a preview
Note
Each customer installation or update is somewhat dierent. Examine
the processes described for areas you may need to customize to t
your system. The following Hewlett-Packard publications will prove
useful for updating your system:
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)
Conguring Systems for Terminals, Printers, and Other Serial
Devices (32022-61000)
HP 3000/iX Network Planning and Conguration Guide
(36922-61023)
Booting the system to MPE/iX using the UPDATE utility may involve
preliminary steps depending upon the particulars of your system and
its usage.
Some of the preliminary steps are listed below:
1. backing up system data
2. limiting system use
3. deactivating network services
4. renaming any system les you wish to maintain
5. reserving adequate disk space
3-28 System Startup Functions
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. returning to normal operation
Updating the system
configuration: a preview
If you are updating just the conguration of your system and not
the operating system, then you have already created the customized
SLT, as in step 9 above. You did this when you made your
conguration changes in SYSGEN and did a KEEP. This information
was transferred to the CSLT at the end of the update process. The
following steps are a subset of an operating system update:
1. backing up system data
2. limiting system use
3. deactivating network services
4. renaming any system les you wish to maintain
Once you are ready to begin the conguration update, the following
are required steps of the process:
5. updating with the customized system load tape
6. returning to normal operation
Updating to recover
from system failure: a
preview
If your system fails, you have many options to use to help recover
your system. Use the UPDATE utility as a recovery method only after
doing the following:
1. attempting a START RECOVERY
2. attempting a START NORECOVERY
3. ensuring the validity of your START procedure
4. ensuring your hardware, hardware code, and current software are
functioning properly
5. reserving adequate disk space
Once you are ready to begin the recovery update, the following
are required steps of the process. These steps are a subset of an
operating system update.
6. updating with the customized system load tape
7. restoring the backup tapes
8. returning to normal operation
System Startup Functions 3-29
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 diculties
arise during the update.
You should also retain a hard copy of your system's current
conguration. If you use the CONFIG option with UPDATE, UPDATE
replaces the conguration les in the group CONFIG.SYS on disk
with any that may exist in the CONFIG.SYS on the system load
tape (SLT). If you use this option, you can unintentionally replace
your system's current conguration les with the ones that UPDATE
provides. In the event of an unintended replacement, if you have a
listing of your current conguration, you can easily regenerate your
system's current conguration.
Use SYSGEN to generate current conguration listings. For
information on using SYSGEN, refer to Chapter 4.
The above information has provided you with an overview of the
update process. If you are planning to update your system, please
follow the instructions in the HP 3000 MPE/iX Installation, Update,
and Add-On Manual (36123-90001) which came with the system
tapes.
Installing the
Operating System
Caution
This section provides a general overview on using operating system
and initial system loader (ISL) commands, options, and utilities to
install the operating system of a 900 Series HP 3000 system.
Specic update and installation instructions are subject to change.
This section provides you with an overview of the procedures
involved. Do not use these instructions to update your system.
For specic information on using operating system and initial
system loader (ISL) commands, options, and utilities to install
your operating system using new factory release tapes, refer to the
appropriate version of HP 3000 MPE/iX Installation, Update, and
Add-On Manual (36123-90001). This manual is included with the
software tapes for each new release and contains information specic
for that release.
The INSTALL utility replaces all les on the system disk with les
from the boot tape. These les include the disk logical interface
format (LIF) label and directory, the system volume label, the bad
3-30 System Startup Functions
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
conguration 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. In this case, installation requires a Hewlett-Packard
Service Representative.
After completion, the default option (INSTALL START) boots the
system from disk.
The INSTALL utility is primarily used to do a rst-time installation of
the MPE/iX operating system. If you are installing a new release, be
sure to follow the exact directions provided in the HP 3000 MPE/iX
Installation, Update, and Add-On Manual (36123-90001).
The INSTALL utility can also be used to replace current versions of
the operating system, boot les, and base system les. Finally, the
INSTALL utility can be used as a last resort in system recovery to
reload the software.
This section begins with a description of using the INSTALL utility to
recover a lost system. The remaining sections provide information on
doing a rst-time installation or a reinstallation when the system was
previously in use.
Using the INSTALL
utility to recover a lost
system
If your system fails, you have many options to use to help recover
your system. Use the INSTALL utility as a recovery method only after
doing the following:
attempting a START RECOVERY
attempting a START NORECOVERY
ensuring the validity of your START procedure
ensuring that your hardware and hardware code, and current
software are functioning properly
attempting an update
In the event of a major system failure caused by corrupted les or
other possible causes, you can use the INSTALL utility to reload your
system. In this procedure, the system is recovered through the use
of backup tapes. You use a system load tape created as part of your
system backup procedure. Alternately, you may instead use the
SLT that the AUTOINST program created when the system was last
installed or updated.
System Startup Functions 3-31
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.
Shut down the system with the SHUTDOWN command, and reboot
the system with START NORECOVERY.
The reinstallation process is now complete.
Scheduling an INSTALL
If you are using the INSTALL utility as a recovery method, the
opportunity to schedule your system's installation is probably not
available to you. Take time to thoroughly examine the INSTALL
process before using it as a recovery method. Understanding the
INSTALL process can reduce system operator and system manager
error and, therefore, reduce your system's downtime.
Normal operating system replacement should be scheduled for
o-peak hours. The INSTALL procedure can take up to ve hours,
depending on your system and the number of subsystems you have
purchased. Schedule the installation immediately after a full backup,
if you are not doing a rst-time installation.
Using the INSTALL
utility and options
The command to invoke the INSTALL utility is INSTALL. The utility
has one initial option, START/NOSTART, with additional options if
START is selected.
INSTALL
;START
;NOSTART
where options are:
2
options
2
START ;GROUP=cgn
;SINGLE-DISC
;MULTI-DISC
;SYSSTART
;NOSYSSTART
3
;SINGLE-USER
;MULTI-USER
32
LOGON=acct
3
To use INSTALL, enter the INSTALL command with or without
START/NOSTART and its options. Separate options from the INSTALL
command and other options with a space or semicolon.
Entering the command INSTALL at the ISL prompt without listing
any options:
ISL> INSTALL
3-32 System Startup Functions
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 specied:
Install the operating system, and autoboot the system from disk
after the installation is completed.
Use the conguration 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.
Allow access to all mounted volumes by all users.
Execute the commands in the system startup le,
SYSSTART.PUB.SYS, if it is present.
Installing the operating
system: a preview
Booting the system to MPE/iX by using the INSTALL utility may
involve preliminary steps if your system has previously been in use.
When installing a system for the rst time, you do not need to be
concerned with these preliminary steps discussed below.
Some of the preliminary steps include the following:
Backing up system data.
Removing users and jobs from the system.
Storing to tape any system les that you wish to maintain.
Once you are ready to begin the installation proper, the following are
required steps of the process:
installing from the system load tape
restoring the FOS tape
restoring the SUBSYS tape
creating a customized system load tape
updating with the customized system load tape
restoring user les, if any
starting system for normal operation
Note
Each customer installation is somewhat dierent. Examine the
processes described for areas you may need to customize to t your
system. The following Hewlett-Packard publications will prove useful
for updating your system:
System Startup Functions 3-33
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)
Conguring Systems for Terminals, Printers, and Other Serial
Devices (32022-61000)
HP 3000/iX Network Planning and Conguration 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. The backups provide a method of restoring your
data. Please refer to the HP 3000 MPE/iX Installation, Update, and
Add-On Manual (36123-90001) if you need additional information on
backing up your system.
You should also retain a hard copy of your system's current
conguration. If you have a listing of your current conguration,
you can easily regenerate your system's current conguration, if
necessary. A customer-generated tape may contain conguration data
in the CONFIG.SYS group.
Use SYSGEN to modify the sample conguration le you used when
you started the system from the disk. For information on using
SYSGEN, refer to Chapter 4 through Chapter 8.
Note
Dumping System
Memory and
Secondary Storage
What is the function of
the DUMP utility?
3-34 System Startup Functions
Do not use these instructions to install your system. This
information is only an overview. Please refer to the HP 3000
MPE/iX Installation, Update, and Add-On Manual (36123-90001) for
complete installation information.
This section dicusses using MPE/iX and initial system loader
commands, options, and utilities to dump system memory and
secondary storage to tape.
The DUMP utility saves the current state of the system's main memory
and secondary storage to tape for later analysis. Perform a memory
dump after a system failure or hang, for a recurring system problem,
or when the system fails to boot properly. Have the tape analyzed
by your Hewlett-Packard Representative or your Hewlett-Packard
Response Center.
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.
The SUBSET=ALL option is the default option and dumps both main
and virtual memory. The SUBSET=MEMORY option is required to dump
main memory contents only.
Issuing the command DUMP without any options
ISL> DUMP
is the same as specifying the following default options:
ISL> DUMP GROUP=CONFIG LOGON=OPERATOR.SYS MULTI-DISC &
MULTI-USER RECOVERY START SUBSET=ALL SYSSTART
The DUMP command and its default options instruct the system to
perform the following tasks if an autoboot le exists, the autoboot
le is enabled, and the START option is specied:
1. Dump all memory and disk-based system data to tape.
2. Boot the system from disk after the dump is completed.
3. Boot with the conguration group CONFIG.SYS.
4. Log on in the user OPERATOR.SYS . (If there is no
OPERATOR.SYS user, you will see the MPE prompt).
5. Allow access to all mounted volumes by all users.
6. Restart jobs that are intact.
Entering the DUMP
utility and starting the
system
Note
A procedure for performing a dump and booting a system includes
the following steps:
1. Mount a tape on the tape drive.
2. Soft reset the system using the access port method, boot from the
primary path, and enter the DUMP command at the ISL prompt.
If you have a 99X system, you must transfer to the service processor
before you can soft reset the system.
CM> SP
System Startup Functions 3-35
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.
The system prompts for a user identication string and for
the correct date and time shortly after receiving the DUMP
command. The user can enter up to 80 characters, which can
later be displayed by DAT when analyzing the dump. There is
a 60-second timeout on this prompt. Once a key is pushed on
the console keyboard, the timeout is aborted and a carriage
return is required to continue with the dump. If a key is not
pushed within 60 seconds, the prompt times out, and the dump
proceeds with a blank user dump ID in the label. If the date
and time are correct, press 4Return5 at the date prompt. If the
date or the time are incorrect, respond as requested with the
correct date and time in 24-hour format.
Note
3-36 System Startup Functions
The DUMP procedure shown in example 3-7 was performed on a
Series 950 through Series 980 system. The procedure assumes that
autoboot is enabled. Make necessary adjustments to the procedure
if autoboot is disabled on your system. Sequences from other
installations may vary.
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.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
ISL> DUMP
MPE/XL launch facility
MPE/XL Dump Version A.00.00 - initialization
A full dump, including secondary storage, was requested.
c
Enter user identification string for this dump (80 chars or less):
TEST DUMP 6/9/88
Example 3-7. Dumping the System
System Startup Functions 3-37
b
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.
Density set at 6250 BPI on tape drive
tape is ready
Begin dump of Processor Internal Memory.
Processor Internal Memory dump complete.
Begin dump of main memory.
32 Megabytes of main memory will be dumped
.... .... .... ....
Dump of memory save area complete.
.... .... .... ....
Main memory dump complete.
Begin dump of secondary storage for ldev1
52 Megabytes of transient objects will be dumped for this device
.... .... .... .... .... .... .... .... .... .... .... .... ....
Secondary storage dump for ldev1 complete.
Begin dump of secondary storage for ldev2
7 Megabytes of transient objects will be dumped for this device
....
Secondary storage dump for ldev2 complete.
Dump completed - autoboot in progress.
c
Processor Dependent Code (PDC) revision 3.2
Example 3-7. Dumping the System (continued)
3-38 System Startup Functions
b
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.28 July 15, 1993
Cannot find an auto-execute file. AUTOBOOT ABORTED.
c
ISL>
Example 3-7. Dumping the System (continued)
3. Start the system. Enter the START command at the ISL prompt
ISL> START
and any desired options.
Examples 3-5 and 3-6 and Appendix B list the messages received
at the console during a START.
System Startup Functions 3-39
b
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.
UPDATE
;CONFIG
;NOCONFIG
where options are:
;SINGLE-DISC
;MULTI-DISC
;SYSSTART
;NOSYSSTART
2
;START
;NOSTART
;LOGON=acct
32
2
options
GROUP=cgn
;SINGLE-USER
;MULTI-USER
3
3
When the START option of the INSTALL utility is selected, the
remaining options are available.
INSTALL
;START
;NOSTART
where options are:
;SINGLE-DISC
;MULTI-DISC
;SYSSTART
;NOSYSSTART
2
2
options
3
;GROUP=cgn
32
LOGON=acct
;SINGLE-USER
;MULTI-USER
3
When the START option of the DUMP utility is selected, the remaining
options are available.
DUMP SUBSET=
ALL
MEMORY
;START
;NOSTART
Where options are:
3-40 System Startup Functions
;RECOVERY
;NORECOVERY
;SINGLE-USER
;MULTI-USER
;SINGLE-DISC
;MULTI-DISC
;SYSSTART
;NOSYSSTART
2
options
3
All available options are dened in Table 3-3.
Table 3-3. Utility Options
Options
Functions
During an UPDATE, this option species whether or not the conguration data les
on disk (CONFIG group), are replaced by those on tape (CONFIG). If this option is
not specied, the default is NOCONFIG.
When the system is booted with NORECOVERY, the group specied after GROUP= is
GROUP= congname
Default: GROUP = CONFIG the source of conguration information. When performing an UPDATE, INSTALL, or
DUMP, this group is only in eect if START is specied or defaulted. When a START
command is entered, the group specied (or defaulted) for it overrides any
previous specication. Since conguration groups reside in the SYS account, you
do not specify the account name.
The logon account contains a standard logon. When the system is booted, the
LOGON= accountname
account specied after LOGON= is used to initiate a session. When SINGLE-USER
Default: LOGON=
has been specied, the account specied in LOGON= is used as the single user. If
OPERATOR.SYS
LOGON= is not specied on the command line, the logon defaults to OPERATOR.SYS
(if the OPERATOR.SYS user has been created).
RECOVERY or NORECOVERY During a START or an autoboot after a DUMP, this option indicates whether or not
Default: RECOVERY (except restartable jobs are restarted. On DUMP, this option is in eect only if START is
with START after INSTALL specied or defaulted. If this option is not specied, the default is RECOVERY . Note
on an INSTALL or UPDATE, jobs cannot be restarted, and the next START defaults to
or UPDATE)
NORECOVERY.
CONFIG or NOCONFIG
Default: NOCONFIG
SINGLE-DISC or
MULTI-DISC (Primarily
Used for Diagnostics)
Default: MULTI-DISC
SINGLE-USER or
MULTI-USER (Primarily
Used for Diagnostics)
Default: MULTI-USER
START or NOSTART
Default: START
Use NORECOVERY if the system conguration has changed. If RECOVERY is specied
and the system conguration has changed, the system recovers restartable jobs by
using the previous system conguration and ignores the new system conguration
and any GROUP= specication.
This option determines whether or not the system initiates with all of the volumes
mounted (MULTI-DISC) or only the system master volume mounted
(SINGLE-DISC). If neither is specied, MULTI-DISC is the default. SINGLE-DISC can
be specied only if SINGLE-USER has also been selected. If the SINGLE-DISC option
is selected with MULTI-USER, the system issues a warning message and changes the
SINGLE-DISC option to MULTI-DISC. If the START parameter is not specied or
defaulted on an INSTALL, UPDATE, or DUMP, the SINGLE-DISC parameter is ignored.
This option boots the system with either single user capability or with multiuser
capability and all congured terminals available. MULTI-USER is the default.
SINGLE-USER is used primarily for diagnostic support. For the INSTALL , UPDATE,
and DUMP utilities, the SINGLE-USER/MULTI-USER option is available only if START
is specied or defaulted as an option.
This option instructs UPDATE, INSTALL, or DUMP whether or not to autoboot
(START) after the utility has completed its job. If neither START nor NOSTART is
specied, START is the default.
System Startup Functions 3-41
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 specied, it defaults to ALL (main memory and
ALL
secondary storage).
On an INSTALL, UPDATE, START, or DUMP, this option
SYSSTART or
determines whether or not the system startup le is used
NOSYSSTART
Default: SYSSTART during the current boot. If neither SYSSTART nor
NOSYSSTART is selected, SYSSTART (using the system startup
le) is the default. If the START parameter is not specied or
defaulted on an INSTALL, UPDATE, or DUMP, this parameter is
ignored.
Table 3-5 summarizes system startup utilities with their more
commonly used options.
3-42 System Startup Functions
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 conguration, the
system recovers restartable jobs by using the previous
system conguration and ignores the new system
conguration.
Yes
Retained
Starts system from disk. Use after changing system
output
conguration. Use to recover from system hang or
failure.
only
Retained
Yes
Boots system from the SLT. Replaces system les on
output
disk with those from SLT. System uses conguration
only
les from disk. Use to update current version of
operating system while maintaining current
conguration. Use to recover from system hang or
failure.
Retained
Yes
Boots system from the SLT. Replaces system les with
output
those on the SLT. Replaces the conguration les on
only
disk (in the group CONFIG.SYS) with those from the
SLT.
No
Lost from system
Boots system from SLT. Replaces all system boot les
disks. User les
and base system les on the system volume (LDEV 1)
remain on
with the information on the SLT. Replaces
nonsystem volumes.
conguration les with SLT defaults. Autoboots
system after completing install. Use to install a
version of the operating system or to recover from a
disk crash or severe system failure.
No
Lost from system
Performs similarly to INSTALL or INSTALL START, but
disks. User les
INSTALL NOSTART does not attempt to start the
system after completing the install.
remain on
nonsystem volumes.
Yes
Retained
Boots system from disk. Stores current state of system
output
main memory and optionally secondary memory to
tape for later analysis. Use to analyze causes of
only
system failure.
System Startup Functions 3-43
4
Using the System Generator (SYSGEN)
SYSGEN is a utility used to modify the system conguration.
System conguration changes are kept to disk in a conguration
group or to a tape called a system load tape (SLT). The SYSGEN
utility requires system supervisor (OP) capability to view system
conguration and system manager (SM) capability to save changes or
create an SLT.
SYSGEN contains a global module and four congurators:
Input/Output (IO) Congurator. Congures the local devices for
the target system.
Logging (LOG) Congurator. Changes the attributes of the user
logging and system logging processes.
Miscellaneous (MISC) Congurator. Focuses on system limits
and startup values, especially those related to jobs, sessions, and
processes.
System File (SYSFILE) Congurator. Changes the list of les
dumped to an SLT.
Each congurator provides an interface to make changes to an
independent portion of the conguration data and oers a menu
of commands and online syntax help. Command names and
abbreviations are easily identied. For example, the command to add
a device is ADEV (abbreviated AD), while the command to delete a
device is DDEV (abbreviated DD).
The congurators operate on information contained in the base
conguration group. This basegroup is the group used to begin
making changes to the system conguration. The basegroup includes
a permanent set of conguration les that contain information
on device classes, assigned I/O paths, assigned logical device
(LDEV) numbers, current volume names, and various other system
parameters.
Activating SYSGEN creates a set of temporary conguration
les that correspond to the permanent le set specied with the
BASEGROUP command. Conguration changes are made to the
temporary conguration les. Once the changes are complete, the
system manager uses the KEEP command to overwrite the permanent
le set with the temporary le set or to save the temporary les to
another permanent le set.
When KEEP is used to save changes to a new group name, SYSGEN
stores the modied base group les in a group in the SYS account.
Using the System Generator (SYSGEN) 4-1
The changes take eect once the system is rebooted with START
NORECOVERY.
SYSGEN also provides a CLEAR command to erase changes made
through one or more of the congurators.
Note
Entering the
SYSGEN Global
Module
When SYSGEN generates a boot tape, it writes the current
conguration 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.
The command for the SYSGEN utility is SYSGEN. SYSGEN has four
positional parameters:
SYSGEN
[
[
[
[
basegroup
,newgroup
,inputle
,outputle
]
]
]
]
The basegroup parameter species the group in the SYS account that
contains the conguration data le set to be used or changed. The
default base group is the group used to boot the system (usually
CONFIG). The default base group is the group specied in the
initial system load (ISL) START command line. (For information on
specifying conguration groups during START, refer to Chapter 3.)
If you attempt to specify a nonexistent group using the BASEGROUP
command, SYSGEN issues the following message:
**error** group groupname does not exist
The newgroup parameter species the group used to store data. If
you do not specify newgroup , SYSGEN stores any conguration
changes in the base group by default.
If the group specied by newgroup already exists, SYSGEN asks,
at keep time, whether or not it should overwrite that group with
new information. At keep time, if the user does a KEEP with
no parameters, SYSGEN keeps the current base group unless
newgroup was specied, in which case the group given is used. More
information on using the KEEP command is provided later in this
chapter.
The inputle parameter species the le designator of the le for
command input. The formal le designator is SYSGIN. The default is
$STDINX.
The outputle parameter species the le designator of the le for
SYSGEN output. The formal le designator is SYSGOUT. The default
is $STDLIST.
4-2 Using the System Generator (SYSGEN)
When using parameters with the SYSGEN command, place them
immediately following the command:
:SYSGEN[basegroup][,newgroup][,inputle]
[,outputle]
When using parameters with RUN SYSGEN.PUB.SYS, you must specify
them in the phrase INFO=" ":
RUN SYSGEN.PUB.SYS;INFO=
"[basegroup][,newgroup]
[,inputle][,outputle]"
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.05 : catalog version C.02.05 FRI, MAY
20, 1990
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 (cl)(c)
oclose (oc)
redo
sysgen>
exit (ex)(e)
help (he)(h)
spu (sp)
c
io
sysfile (sy)
Example 4-1. Activating SYSGEN's Global Module
b
Using the System Generator (SYSGEN) 4-3
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
congurator 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
a
sysgen>HELP
** First level command **
log (lo)
misc (mi)
basegroup (ba)
show (sh)
tape (ta)
keep (ke)
permyes (pe)
clear (cl)(c)
oclose (oc)
redo
sysgen>
exit (ex)(e)
help (he)(h)
spu (sp)
c
io
sysfile (sy)
Example 4-2. SYSGEN's Global Module Help Facility
4-4 Using the System Generator (SYSGEN)
b
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 = OFFLINE]
** Common configurator commands **
clear (cl)(c)
exit (ex)(e)
help (he)(h)
hold (ho)
oclose (oc)
redo
c
[command = ALL | command-name]
sysgen>
Example 4-3. SYSGEN Global Module HELP ALL
b
To display a listing of the syntax for a rst-level command, enter
HELP commandname as shown in the following example:
sysgen>HELP BASEGROUP
basegroup
(ba) [name=groupname]
Using the System Generator (SYSGEN) 4-5
Using First-Level
(Global Module)
Commands
The rst-level commands, displayed after entering SYSGEN, allow
you to activate one of the four congurators (I/O, LOG, MISC,
SYSFILE) or or to keep, show, or clear changes made from the
congurators. In addition, you can use rst-level commands to call
the SYSGEN help facility, alter basegroups, store conguration
changes to tape, or exit the SYSGEN utility. The following table
describes the commands and their actions:
4-6 Using the System Generator (SYSGEN)
Table 4-1. Using First-Level Commands
Command
Meaning
IO
Activates the I/O Congurator. For additional
information on the IO command, refer to \Entering
the I/O Congurator."
LOG or LO
Provides access to the LOG congurator commands.
MISC or MI
Provides access to the MISC congurator commands.
SPU or SP
Provides access to the SPU congurator commands
SYSFILE or SY
Provides access to the SYSFILE congurator
commands.
BASEGROUP or BA
Changes the default group after the utility is
activated. Previous changes, if any, are lost. The
conguration begins anew.
KEEP or KE or K
Saves conguration changes that were made in the
congurators and temporarily stored with the HOLD
command.
PERMYES or PE
Controls SYSGEN's interactive conrmation for
potentially serious action, such as an EXIT before a
KEEP.
SHOW or SH
Shows the state of individual congurators, combined
congurators, or all congurators.
TAPE or TA
Generates a boot tape. All conguration changes
made are reected on the tape.
CLEAR or CL or C
Clears all changes made from all congurators.
EXIT or EX or E
Exits the global module and returns to the operating
system prompt.
HELP or HE or H
Displays the list of commands, the individual
command syntax, or the syntax of all the rst level
commands.
OCLOSE or OC
Closes the oine listing le, SYSGLIST.
REDO
Used for making corrections. Follows the command
interpreter REDO conventions.
:command
Allows you to enter various MPE/iX command
interpreter commands.
Using the System Generator (SYSGEN) 4-7
SYSGEN Command
Syntax
Note
Commands can be classied as either command only or command
with parameters(s). Commands with parameters can be specied 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. Separate parameters by semicolons or blanks, or exclude
them by using consecutive semicolons. Enclose subparameters and
repeated parameters in parentheses, and separate them by commas or
blanks.
A subparameter can be either strings or numeric values separated by
blanks or commas. Enclose them in parentheses if more than one
is present. Always specify subparameters by xed position within
the subparameter list. You can omit subparameters by entering
consecutive commas.
A repeated parameter is a single parameter value that can be
repeated an arbitrary number of times. Separate parameters by
commas or blanks, and enclose them in parentheses () if more than
one is present.
Halting SYSGEN
Command Actions
Entering 4CTRL5 4Y5 stops listings or cancels partially entered
SYSGEN commands.
Issue 4CTRL5 4Y5 at any point in SYSGEN. SYSGEN terminates
the current action and returns its prompt. If you enter 4CTRL5 4Y5
while SYSGEN is generating a boot tape, you have the option of
terminating or continuing the tape generation process.
is eective if the SYSGEN output and input has not been
redirected and if SYSGEN is being run from a session.
4CTRL5 4Y5
4-8 Using the System Generator (SYSGEN)
Specifying the Base
Group
When altering or viewing a conguration through SYSGEN, you
must rst select the conguration 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. You can use the basegroup
optional parameter in the SYSGEN command line:
:SYSGEN[basegroup][,newgroup][,inputle]
[,outputle]
Also, you can enter the SYSGEN global module and use the
rst-level command BASEGROUP:
sysgen>BASEGROUP groupname
The syntax for the BASEGROUP command (abbreviated BA) is:
BASEGROUP [ [NAME=] groupname]
The groupname parameter is a string of up to eight characters. For
example, to use BASEGROUP, enter the command and its parameter as
shown:
sysgen>BASEGROUP CONFG935
or
sysgen>BA MYCONFIG
BA switches you to a dierent conguration group. (List
conguration information through the LIST and SHOW commands of
the various congurators.)
If you specify a nonexistent group, SYSGEN issues an error message:
sysgen>BASEGROUP FEUDAL
**error** group "FEUDAL" does not exist
sysgen>
Using the System Generator (SYSGEN) 4-9
Confirming
Potentially Serious
Actions
SYSGEN is initially set to conrm a potentially serious action. If,
for example, you make conguration 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. This command is particularly useful when SYSGEN
receives input commands from a le or batch job.
If PERMYES is OFF (the default), SYSGEN prompts you for a
YES/NO response whenever a potentially serious action, such as
exiting SYSGEN without saving conguration changes, is initiated.
If you respond negatively, the action does not take place and the
command is ignored. If PERMYES is ON, you are not prompted for
conrmation. SYSGEN executes the command exactly as entered.
To enable PERMYES, enter PERMYES ON at the SYSGEN prompt:
sysgen>PERMYES ON
To disable PERMYES, enter PERMYES OFF at the SYSGEN prompt:
sysgen>PERMYES OFF
Once PERMYES is disabled, SYSGEN issues messages to prompt for
conrmation. Example 4-4 demonstrates PERMYES OFF action.
Note
PERMYES should always be set ON in command les to allow
SYSGEN to continue where conrmation would be requested.
4-10 Using the System Generator (SYSGEN)
d
a
:SYSGEN
SYSGEN version D.01.01 : catalog version D.01.01
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 (cl)(c)
oclose (oc)
redo
sysgen>
sysgen>PERMYES OFF
sysgen>SYSFILE
exit (ex)(e)
help (he)(h)
spu (sp)
io
sysfile (sy)
** SYSFILE configurator commands **
aauto (aa)
asprog (as)
cmsl (cm)
dcmsl (dc)
dsprog (ds)
rboot (rb)
rcat (rc)
ripl (ri)
rnmlib (rn)
aboot (ab)
acmsl (ac)
dauto (da)
dboot (db)
lcmsl (cl)
rauto (ra)
rcmsl (rcm)
rdcc (rd)
rsprog (rs)
show (sh)
clear (cl)(c)
exit (ex)(e)
help (he)(h)
hold (ho)
sysfile>
sysfile>ASPROG FCOPY.PUB.SYS FCOPY.PUB.SYS ** Add
FCOPY to SYSGEN tape **
sysfile>E
*** Exit without saving ***
c
sysfile>
configuration changes are not kept yet!
still want to exit (yes/no) ?NO
Example 4-4. PERMYES OFF Action
b
Using the System Generator (SYSGEN) 4-11
Example 4-5 shows how SYSGEN overrides user input with PERMYES
enabled.
4-12 Using the System Generator (SYSGEN)
d
a
:SYSGEN
SYSGEN version D.01.01 : catalog version D.01.01
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 (cl)(c)
oclose (oc)
redo
sysgen>
sysgen>PERMYES ON
sysgen>SYSFILE
exit (ex)(e)
help (he)(h)
spu (sp)
io
sysfile (sy)
** SYSFILE configurator commands **
aauto (aa)
asprog (as)
cmsl (cm)
dcmsl (dc)
dsprog (ds)
rboot (rb)
rcat (rc)
ripl (ri)
rnmlib (rn)
aboot (ab)
acmsl (ac)
dauto (da)
dboot (db)
lcmsl (cl)
rauto (ra)
rcmsl (rcm)
rdcc (rd)
rsprog (rs)
show (sh)
clear (cl)(c)
exit (ex)(e)
help (he)(h)
hold (ho)
sysfile>
sysfile>ASPROG FCOPY.PUB.SYS FCOPY.PUB.SYS ** Add
FCOPY to SYSGEN tape **
sysfile>E
*** Exit without saving ***
c
sysgen>
configuration changes are not kept yet!
still want to exit (yes/no) ?Automatic yes
Example 4-5 PERMYES ON Action
b
Using the System Generator (SYSGEN) 4-13
Enabling PERMYES saves time and eort 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 conrmation.
Showing the State
of Configurators
The SHOW command (abbreviated SH) displays the current state of the
SYSGEN global facilities.
SHOW has the following syntax:
SHOW
[TYPE =
[DEST =
[
[
[
[
[
BASEGROUP
NEWGROUP
VERSION
PERMYES
CONFIGURATOR
ALL
OFFLINE
]
]
]
]
]
]
]
BASEGROUP lists the name of the current working conguration's base
group.
NEWGROUP lists the name of the current new conguration group.
VERSION displays the version number of SYSGEN. The version
number is also displayed in the SYSGEN banner.
PERMYES shows whether SYSGEN prompts you for conrmation
before performing potentially serious commands.
CONFIGURATOR lists all modied congurators.
ALL provides a combined listing of the conguration information
provided by the TYPE parameters dened above.
OFFLINE sends output to SYSGEN's listing le, SYSGLIST. Using
OFFLINE in the SHOW command line does not immediately generate a
printout. 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.
Entering SHOW without TYPE parameters is the same as specifying
SHOW ALL. Example 4-6 demonstrates using the SHOW ALL command.
4-14 Using the System Generator (SYSGEN)
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 congurators (IO, LOG,
MISC, SYSFILE) are SYSGEN rst-level commands. To activate the
congurators, you must rst enter the SYSGEN Global module.
Once you have the SYSGEN prompt, enter either IO, LOG, MISC, or
SYSFILE to activate the Input/Output, Logging, Miscellaneous, or
System File congurators, respectively. Example 4-7 demonstrates
activating a congurator:
Using the System Generator (SYSGEN) 4-15
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.
** First level command **
log (lo)
misc (mi)
basegroup (ba)
show (sh)
tape (ta)
keep (ke)
permyes (pe)
clear (cl)(c)
oclose (oc)
redo
sysgen>
sysgen>IO
exit (ex)(e)
help (he)(h)
spu (sp)
io
sysfile (sy)
** IO configurator commands **
(av)
(dv)
(lv)
aclass (ac)
adev (ad)
apath (ap)
avol
dclass (dc)
ddev (dd)
dpath (dp)
dvol
lclass (lc)
ldev (ld)
lpath (lp)
lvol
mclass (mc)
mdev (md)
exit (ex)(e)
help (he)(h)
maddress (ma)
mpath (mp)
mvol (mv)
clear (cl)(c)
(ho)
c
io>
oclose (oc)
hold
redo
Example 4-7. Activating a SYSGEN Configurator
b
For information on a particular congurator, refer to the chapter that
discusses the congurator.
4-16 Using the System Generator (SYSGEN)
Clearing
Configuration
Changes
The SYSGEN global module CLEAR command (abbreviated CL)
removes all temporary changes made from the four congurators. If,
for example, you make IO and SYSFILE congurator changes and
decide not to keep them, issue the global module CLEAR command to
remove the changes made in both congurators.
To clear all temporary changes made from the IO, LOG, MISC, and
SYSFILE congurators, enter CLEAR at the SYSGEN prompt:
sysgen>CLEAR
Saving Configuration
Changes
Saving conguration changes is a two-step process. After making the
changes in any of the congurators, you must hold those changes
before exiting the congurator to continue your work.
Use the HOLD command to temporarily hold the changes made
in a congurator. Holding changes allows you to move among
congurators or between a congurator and the global module
without losing changes.
Refer to the sections on the IO, LOG, MISC, or SYSFILE
congurators for information on using HOLD within each congurator.
The KEEP command (abbreviated KE or K) saves (stores to disk les)
changes held from any of the SYSGEN congurators.
KEEP has the syntax:
KEEP
[ [NAME=]groupname ]
Groupname may be eight characters or fewer and must begin with an
alphabetic character.
SYSGEN keeps track of the current conguration group, whether
it is the default group with which you booted the system, a group
specied by the basegroup parameter on the initial SYSGEN
command line, or a group switched to by the BASEGROUP global
congurator command. If you do not specify a basegroup with the
KEEP command and did not specify a group with the newgroup
parameter on the initial SYSGEN command line, SYSGEN uses the
current working base group (either the default or the one set by a
method listed above) to save the conguration changes.
The KEEP command can be used to save conguration changes to
a group other than the current working group. In addition, if the
desired group does not already exist, the KEEP command creates it
and then saves the conguration changes to it. All groups are saved
in the SYS account.
Using the System Generator (SYSGEN) 4-17
To keep changes to a group other than the current working
conguration 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 conguration
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.
If insucient space exists on the main system disk to accommodate
the creation of a new conguration group, SYSGEN issues a message
indicating this. SYSGEN then terminates, losing the temporary les
and the changes.
Generating a
System Load Tape
The TAPE command (abbreviated TA) generates an SLT from system
conguration information. The conguration is written to the CONFIG
group of the SYS account on the tape.
TAPE has the following syntax:
8
>
>
>
>
>
>
>
<2
2
39
VERBOSE >
>
6 NOCHANGE 7 >
>
6
7>
>
>
6
7
36 NOCONFIG 7 = 8 2
3
MODE = 6
DEST = OFFLINE
TAPE
7
6 NODIAG 7 >
>
>
6
7>
>
>
>
>
>
4
5>
NOLOGNUM
>
>
>
>
:
;
LOGNUM
82
3
9
STORE = "filesetliststring"
9
VERBOSE prompts the TAPE command to list the number of nonuser
les to be dumped and lists the name of each le as it is dumped to
the boot tape.
By default, SYSGEN changes SYSFILE congurations as they are
dumped to tape, so source name equals the destination name.
NOCHANGE prevents SYSGEN from changing the names in the
SYSFILE congurator as it makes the boot tape.
NOCONFIG prevents SYSGEN from dumping the current conguration
les as it makes the tape.
4-18 Using the System Generator (SYSGEN)
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 species 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.
Using OFFLINE in the TAPE command line does not immediately
generate a printout. The information is sent to SYSGLIST until you
enter the global module OCLOSE command or exit SYSGEN. Exiting
SYSGEN or using OCLOSE closes SYSGLIST and prints the le.
STORE allows the user les that are specied in the le set list to be
stored after the SLT. (The lesetliststring parameter is the same as
the parameter specied with the STORE utility.
All conguration changes made are reected on the tape. (The
temporary changes remain valid after SYSGEN has generated a
tape.) Tapes created by the TAPE command do not contain the
system le directory.
Note
SYSGEN detects all system-independent errors; however, due to
SYSGEN's lack of knowledge of the physical attributes of a target
system, system-dependent errors cannot be detected when a system
load tape is generated.
To generate a system load tape (SLT), perform the following tasks:
1. Log on to the console as MANAGER.SYS. Enter:
:HELLO MANAGER[/userpass].SYS[/acctpass]
Note
If the user has system supervisor (OP) capability, but not system
manager (SM) capability, an SLT can still be made; however no
conguration changes can be made. Follow steps 2, 3, 10, and 11.
Using the System Generator (SYSGEN) 4-19
d
2. Activate SYSGEN and access the conguration 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. Make any desired changes from the IO, LOG, or MISC
congurators.
Refer to Chapter 5, and Chapter 7 for information on using
the IO, LOG, and MISC congurators to alter the system
conguration.
4. After completing any changes, but before exiting a congurator,
enter:
HOLD
The HOLD command saves changes (to a temporary le) made in
the congurator at the time that the HOLD is issued.
5. Decide which les to dump to tape.
SYSGEN allows you to choose which les to store to a boot
tape. You may store autoboot images, boot images, and system
programs.
The SYSFILE congurator provides the utilities and commands
that alter boot tape contents. For information on the commands
available for adjusting boot tape contents, refer to Chapter 8.
4-20 Using the System Generator (SYSGEN)
6. Hold any changes made in step 6.
After completing any changes, but before exiting the
congurator, enter:
sysfile>HOLD
7. Exit the SYSFILE congurator. 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.
To create only a system load tape (SLT), enter the following
command:
sysgen>TAPE
This is a tape containing the operating system and specied
conguration information.
To create a system load tape with user les stored after it,
enter the following command:
sysgen>TAPE STORE="lesetlist"
You can list the user les that you wish to store as input to
the STORE= parameter. Note that the string of le names to
be stored after the SLT must be enclosed in quotes. You can
also use the wildcard @ to include all users les on the system
(@.@.@), in specic accounts (@[email protected], @[email protected]), and in
specic groups of accounts (@.PUB.SYS, @.CURRENT.AR).
The system responds by issuing a message similar to the
following:
?10:15/#92/46/LDEV# FOR "SYSGTAPE" ON TAPE (NUM)
Respond to the tape request to start the STORE when the system
issues the above message. When the store is complete, the
system issues a message indicating that it has completed the
tape:
**Boot tape is successfully built**
11. After all the les are stored, unload the tape and write- protect
it. Label the tape and store it in a secure location with other
backup materials.
Using the System Generator (SYSGEN) 4-21
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. The formal le designator for the standard SYSGEN
output le. By default, this le is set to $STDLIST.
SYSGLIST. The formal le designator for the standard SYSGEN
listing le. By default, this le is set to any device in the class LP.
$STDINX and $STDLIST are the le names for the terminal from
which SYSGEN is run. The device in class LP is your system printer.
Redirect SYSGEN input and output by using the FILE command and
equating some other les to SYSGIN, SYSGOUT, and SYSGLIST, or by
using the INFO parameter and options in the SYSGEN command line.
For example, the commands FILE SYSGIN=NEWIN and SYSGEN,,NEWIN
accomplish the same task. When SYSGEN is activated, they
utilize NEWIN as the input le. Likewise, the commands FILE
SYSGOUT=NEWOUT and SYSGEN,,,NEWOUT equate NEWOUT to the formal
le designator, SYSGOUT, so SYSGEN utilizes NEWOUT as the output
le.
With redirection you can use a command input le to complete
common routines that you perform frequently. Example 4-9 lists
a three-line job stream (named SYSGENON) which, when run using
the STREAM command, logs on to the system, enters SYSGEN, and
executes the SYSGEN command le (LISTIT) in example 4-10.
Refer to MPE/iX Commands Reference Manual Volumes 1 and
2 (32650-90003 and 32650-90364) for information on the STREAM
command.
d
c
a
1
2
3
!JOB SYSGENON,MANAGER/userpass.SYS/acctpass,groupname
!SYSGEN,,LISTIT
!EOJ
Example 4-9. Command File (SYSGENON) Created With EDITOR
b
Table 4-2 explains the actions performed by each line of the
preceding command le.
4-22 Using the System Generator (SYSGEN)
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.
1
2
3
4
5
6
7
8
c
PERMYES ON
IO
LDEV DEST=OFFLINE
LPATH DEST=OFFLINE
LCLASS DEST=OFFLINE
OCLOSE
EXIT
EXIT
Example 4-10. SYSGEN Command File (LISTIT)
Table 4-3 explains the actions performed by the lines of the command
le example.
Table 4-3. Actions Performed by Command File LISTIT
Line
Action
1
Set PERMYES ON. Recommended for all command les.
2
Activate the IO congurator.
3
Send the characteristics of congured I/O devices to the listing le
SYSGLIST.
4
Send the characteristics of congured I/O paths to the listing le.
5
Send the class name, class mode, and devices associated with each
class to the listing le.
6
Close (print) the listing le.
7
Exit the IO congurator.
8
Exit SYSGEN.
Using the System Generator (SYSGEN) 4-23
a
b
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 conrmation. For example, if a KEEP is
attempted on top of an already existing conguration group,
SYSGEN asks for conrmation. If no conguration exists, no
questions are asked.
When you set up the input to SYSGEN you may not know if
the question will be asked. To ensure the operation's success, set
PERMYES ON at the beginning of any set of noninteractive commands
as shown in step 1 above.
Exiting SYSGEN
Use the EXIT command (abbreviated EX or E) to exit from a
congurator and return to the SYSGEN global module, or to
terminate SYSGEN and return to the MPE prompt.
To exit either a congurator or SYSGEN, enter EXIT at the prompt:
log>EXIT
sysgen>
or
sysgen>EXIT
:
Note that the MPE prompt returns after SYSGEN ends.
4-24 Using the System Generator (SYSGEN)
5
Modifying Input/Output (I/O) Configurations
With the introduction of version C.55.00 of MPE/iX, there are
two ways to dene input and output devices on a system: using
SYSGEN's I/O Congurator or using the IOCONFIG utility. Both
methods provide information about the input and output devices
congured on a system and let you make changes to the conguration
as necessary. The key dierence is that using IOCONFIG changes
the conguration while the system remains online, whereas to
activate conguration changes made with SYSGEN, you must issue a
separate command (DOIONOW) after making the changes, or reboot the
system with the START NORECOVERY option, or generate a new System
Load Tape to update this (or another) system.
SYSGEN's I/O congurator and the IOCONFIG utility congure the
local devices of the system only. Remote devices, such as terminals
on a distributed terminal subsystem and remote serial printers, are
congured through the network management congurator.
This chapter begins with a general discussion of I/O paths and
then explains how to congure devices using SYSGEN and the
IOCONFIG utility. For additional information, read chapter 3 of
Performing System Manager Tasks (32650-90004).
Modifying Input/Output (I/O) Configurations 5-1
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 . They consist of:
the primary boot path, for booting from disk
the alternate boot path, for booting from a tape
the console boot path, which determines whether or not the console
can boot itself (\autoboot") without operator intervention
Each device congured for the boot path has been assigned a unique
LDEV number which identies a physical device associated with
a system. Two of the boot paths, the primary boot path and the
console boot path, require a specic LDEV. The system master
volume must be mounted on LDEV 1 for the operating system to
be booted from disk and LDEV 20 must be assigned to the system
console.
At system installation, these devices are assigned a default boot path,
which the system manager may redirect either through the system
initialization prompts or the initial system load (ISL) interface. For
more information on system initialization and ISL, refer to chapter 3
of this manual.
Selecting I/O paths
An I/O path is determined by the channel adapter (CA) module
number, the device adapter (DA) slot number, and the device
address.
Series 922 through Series 949 systems
Each I/O path is constructed \top down." On the HP 3000 Series
922 through Series 949 systems, I/O path construction begins with
the channel adapter, which connects the system central bus and the
channel I/O (CIO) bus. The logical construction concludes with the
device adapter, which connects the CIO bus and I/O device. An I/O
device connects to a device adapter card through an interface cable.
An HP 3000 Series 925 through Series 949 I/O path is specied as
follows:
CA Module Number.DA Slot Number.Device Address
The CA module species the number of the interface slots that
contain the two adapter boards for the channel I/O bus (CIO) and
central bus (CTB). The interface slot is assigned a numerical value
of 4 or 8 for a 949 (device adapters in SPU) or 8 (device adapters in
5-2 Modifying Input/Output (I/O) Configurations
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 specication.
For example, if the CA module number is 4, the HP-IB channel CIO
interface slot is 5, and the magnetic tape device address is 0, the I/O
path for the tape device is 4.5.0.
Series 950 through Series 980 systems
On the HP 3000 Series 950 through 980 systems, I/O path
construction begins with the bus converter (BUS CONV), which
connects the system memory bus (SMB) and the system mid-bus.
The channel adapter connects the mid-bus and the CIO bus. The
logical construction concludes with the device adapter, which
connects the I/O device to the CIO bus. An I/O device connects to a
device adapter card through an interface cable.
An HP 3000 Series 950 through Series 980 I/O path is specied as
follows:
BUS CONV/CA Module Number.DA Slot Number.Device Address
F
The bus converter species the number, either 2 or 6, of the interface
slot which contains the adapter boards for the SMB and the mid-bus.
The CA module species the number of the interface slots that
contain the adapter boards for the mid-bus and the CIO bus. The
interface slot is assigned a numerical value of 4, 8, 16, 20, or 24.
DA CIO section slot numbers range from 0 to 4.
The address of the device itself depends on the adapter. In addition,
data communications devices may have an additional logical or
virtual device number in the I/O path specication.
For example, if a bus converter is 2, the CA module number is 4, the
HP-IB channel CIO interface slot is 2, and the magnetic tape device
address is 3, the I/O path for the tape device is 2/4.2.3.
Modifying Input/Output (I/O) Configurations 5-3
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-specic data is converted to a format compatible with the
CIO bus.
The high-speed data transfers of HP-FL cards require that HP-FL
devices occupy the lowest-priority CIB slots; therefore, HP-IB
systems may require reconguration to accommodate HP-FL cards.
The reconguration also requires that the primary, secondary, and
alternate boot paths be changed. Systems initially congured to
accommodate HP-FL cards may not require signicant modication
to accept additional HP-FL cards.
Appendix D lists the default I/O paths provided for use with HP-FL
systems. Contact your HP representative for additional information
on using HP-FL cards in your system.
There are several ways to determine the I/O paths for devices that
are attached to the system:
If the system is running or not, you can look at the address and
physical connection of the device.
The START command, which initiates the booting of the system,
automatically identies the system state at boot time. This
information includes which paths have been congured and which
drives are available.
When you are booting the system, you can run the IOMAP utility
from the ISL.
Once the system is running, you can use either of two methods
to check I/O path information for congured devices: SYSGEN's
I/O Congurator, or the IOCONFIG utility that was released on
version C.55.00 of MPE/iX. (Note that SYSGEN and IOCONFIG
do not indicate if the congured device is active or available. For
this information, use the SHOWDEV command.)
5-4 Modifying Input/Output (I/O) Configurations
Using the SYSGEN
I/O Configurator
d
To view and modify the I/O conguration from within SYSGEN,
you use the I/O congurator 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.
a
:SYSGEN
sysgen>IO
** I/O configurator commands **
c
aclass (ac)
dclass (dc)
lclass (lc)
maddress(ma)
mvol (mv)
adev (ad)
ddev (dd)
ldev (ld)
mclass (mc)
apath (ap)
dpath (dp)
lpath (lp)
mdev (md)
avol (av)
dvol (dv)
lvol (lv)
mpath (mp)
clear (cl)(c)
oclose (oc)
exit (ex)(e)
redo
help (he)(h)
hold (ho)
io>
Getting help with I/O
Configurator commands
Example 5-1. Starting the I/O Configurator
b
The help facility enables you to identify quickly the function
and syntax of those I/O congurator commands and options
required to perform the multiple operations that dene or change
device-dependent information.
To see a list of the commands available for use in the I/O
congurator and their abbreviations, enter HELP at the I/O
congurator prompt. To display the syntax for each available
command at the current level, enter HELP ALL, as shown in the
example below:
Modifying Input/Output (I/O) Configurations 5-5
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
= #/#,#,...
= IN|OUT|CIO|NCIO|RANDOM|
DEFAULT]
= #/#,#,...
= devicepath]
= productid
= recordsize]
= outputdevice]
= JOB|DATA|INTERACTIVE|DUPLICATIVE|
INPUT|OUTPUT|AUTOREPLY|NLIO|NONE]
[class
= classname,...|NONE]
[cmode
= IN|OUT|CIO|NCIO|RANDOM|
DEFAULT]
[pmgr
= physicalmanagername]
[lmgr
= logicalmanagername]
[pmgrpri
= physicalmanagerpriority]
[mpetype
= compmodetype]
[mpesubtype= compmodesubtype]
[devname
= devicename]
.
.
Example 5-3. I/O Configurator HELP ALL Command Output
5-6 Modifying Input/Output (I/O) Configurations
b
To view the syntax for a specic I/O congurator command, enter
HELP commandname at the I/O congurator 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,...|NONE]
IN|OUT|CIO|NCIO|RANDOM|
DEFAULT]
physicalmanagername]
logicalmanagername]
physicalmanager priority]
compmodetype]
compmodesubtype]
devicename]
b
Example 5-4. I/O Configurator Command HELP Output
Using I/O Configurator
commands
The I/O congurator commands let you list, modify, add, and
delete four types of objects: classes, devices, paths, and volumes.
You can also use the I/O congurator to modify addresses with the
MADDRESS command. In addition to these specic functions, the I/O
congurator includes the commands that are common to all SYSGEN
congurators: CLEAR, EXIT, HELP, HOLD, and OCLOSE.
Table 5-1. IO Configurator Command Matrix
List
Modify
Add
Delete
Class
LCLASS MCLASS
ACLASS DCLASS
Device
LDEV
MDEV
ADEV
DDEV
Path
LPATH
MPATH
APATH
DPATH
Volume
LVOL
MVOL
AVOL
DVOL
Address
MADDRESS
Modifying Input/Output (I/O) Configurations 5-7
Viewing the current
configuration
To get information about the current conguration, 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
Denition
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
conguration. A class name is an identier to
which numerous devices can be assigned. Unlike
LDEV numbers, device class names are not
unique to each device. For example, all of your
system's printers could be assigned the class
name LP. (LP, which stands for \line printer," is a
common device class name.) For more
information, refer to the Controlling System
Activity (32650-90155). It provides detailed
information about device class names, their
modes of operation, and how they are assigned in
the system.
LDEV
Lists the attributes of the specied logical device LDEV CLASS=(LP,EPOC)
or devices. If you omit the LDEV number, all of LDEV (4/9,11/14)
the I/O devices and their characteristics are
listed. Each congured logical device (LDEV) has
a uniquely assigned LDEV number which
identies a physical device associated with a
system.
LPATH
Lists information about the adapters and I/O
devices on a specied path level. You can list a
specic path, list paths a specic level, or list all
paths associated with an I/O manager.
LVOL
Lists the attributes of the specied volume, which LVOL MEMBER1
is one disk pack. Each volume is a member of a
volume set and contains a volume label, a label
table, and a free space map. When you enter the
LVOL command for a specic volume, you will
see the volume's LDEV number, the amount of
transient and permanent space it has, its class
status, and the volume class it belongs to.
5-8 Modifying Input/Output (I/O) Configurations
LPATH PATH=4
LPATH,1
LPATH MANAGER=CIPER_DM
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. At the I/O Congurator prompt (>io) enter:
io>LCLASS (DISC,LP) DEST=OFFLINE
Or, you can enter the command this way:
io>LCLASS (DISC,LP) OFFLINE
2. To close the le SYSGLIST and print the information, enter
io>OCLOSE
Sample configuration data
Below is an example of the kind of information you might see if you
entered the LDEV command, without additional parameters, at the
I/O congurator prompt on a Series 925 system.
Modifying Input/Output (I/O) Configurations 5-9
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.3
CLASS: DISC
SPOOL
OUTDEV:
0
RSIZE:
128
MPETYPE:
3
MODE:
DEVTYPE: DISC
MPESUBTYPE: 10
LDEV:
6
DEVNAME:
ID: HP2566A
PATH: 4.5.6
CLASS: LP
OUTDEV:
RSIZE:
MPETYPE:
0
66
32
MODE:
DEVTYPE: LP
MPESUBTYPE: 9
LDEV:
7
DEVNAME:
ID: HP7980A
PATH: 4.5.3
CLASS: TAPE
OUTDEV:
0
RSIZE:
128
MPETYPE: 24
MODE:
DEVTYPE: TAPE
MPESUBTYPE: 5
LDEV:
10
DEVNAME:
ID: HP7980A
PATH: 4.5.4
OUTDEV:
LP
RSIZE:
128
MPETYPE: 24
MODE: JA
DEVTYPE: TAPE
MPESUBTYPE: 5
OUTDEV:
RSIZE:
MPETYPE:
MODE: JAID
DEVTYPE: TERM
MPESUBTYPE: 0
LDEV:
20
DEVNAME:
ID: HP2392A
PATH: 4.2.0
CLASS: CONSOLE
20
40
16
LDEV: 100/111 NMMGR
c
io>
Example 5-8. Listing Configured Devices: Series 925 System
5-10 Modifying Input/Output (I/O) Configurations
b
Adding Objects in
SYSGEN
When you use SYSGEN to add objects to the system conguration,
there are four I/O Congurator commands available: ACLASS,
ADEV, APATH and AVOL. They are dened in the table below. For
more detailed information read Performing System Manager Tasks
(32650-90004).
Table 5-3. I/O Configurator Add Commands
Command
Denition
Examples
ACLASS
Creates a new class name and associates devices ACLASS EPOC 19
to the new class. You use the ACLASS command ACLASS PLATES 31/34
to add a class name designation to a device that MODE=RANDOM
is already congured with the ADEV command.
You also specify the mode with this command,
which can be one of JOB (accepts jobs and
sessions), IN (input only), OUT (output only), CIO
(concurrent I/O), NCIO (nonconcurrent I/O),
RANDOM (direct-access device such as a disk), and
DEFAULT (a mode assigned when the system is
initialized).
ADEV
Adds a device to an existing I/O path that is
congured to the device adapter level. At a
minimum, you must specify the LDEV, the path,
and ID number, but you may also specify the
record size, an output device associated with the
device, the device operation mode, the class, a
class mode (other than the default assigned to
the device), physical and logical device managers,
the priority level of the physical device manager,
the compatability mode type and subtype,and a
device name.
APATH
APATH PATH=4.2
Denes the I/O path to an adapter, not to a
ID=HP27113A
device. (To add device level paths, you use the
ADEV command.) If the path has already been
dened, you will get an error. At a minimum,
you must enter the path and an ID, which is
either the Hewlett-Packard product number or a
mnemonic name that designates dierent uses of
the same product. You may also specify the
physical and logical device managers, the
execution priority of the physical device manager,
and the maximum number of concurrent I/Os to
expect.
AVOL
AVOL VNAME=MEMBER2
Adds a new volume to the system volume set
LDEV=4 VCLASS=PROD
conguration. You must specify a unique name
you give to each volume member and its logical
device number. In addition, you may also specify
the volume class and the amounts of transient
and permanent disk space allocated on the
volume.
ADEV LDEV=30 PATH=4.5.9
ID=HP2688A
ADEV 8 PATH=2/4.2.1
ID=HP7978B RSIZE=132
Modifying Input/Output (I/O) Configurations 5-11
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 congure UPS devices, read \Introducing
the UPS and UPS Monitor/iX Software" later in this chapter.
To learn how to use NMMGR to congure other devices, read
Conguring Systems for Terminals, Printers, and Other Serial
Devices (32022-61000).
Changing
Configurations in
SYSGEN
When you use SYSGEN to change the system conguration, there
are ve I/O Congurator commands available: MADDRESS, MCLASS,
MDEV, MPATH, and MVOL. They are dened in the table below and
explained in the following sections.
Table 5-4. I/O Configurator Modify Commands
Command
Denition
Examples
MADDRESS
Modies the I/O path from one that exists to a MADDRESS 2/4.0.2 6/4.0.3
new path that does not already exist. You specify
the old path and the new path, both of which
must have the same number of levels.
MCLASS
Changes I/O class information including the class MCLASS CLASS =LP
mode, the class name, and the devices associated NEWCLASS=BIGPRN MODE=OUT
with the class.
MCLASS BONSAI SMALLPRN
28/29
MDEV
MDEV 8 18 HP7978H 4.3.0
Changes the attributes of a congured device.
You specify the LDEV number of the device you MODE=JOB
want to modify, then enter the new paramaters.
This commands changes the LDEV number itself,
the device ID, the device path, class, mode,
record size, physical and logical device manager,
the compatability mode type and subtype, and
the device name.
MPATH
Changes the attributes of an I/O path. You can MPATH 4.1 HP27113A
MPATH 2/4.3
modify the path name, the product ID, the
PMGR=HPIB_DAM
physical and logical device managers, the
execution priority of the physical device manager,
and the maximum number of concurrent I/Os to
expect.
MVOL
Modies the attributes of a volume set member. AVOL VNAME=MEMBER2
You can modify the volume name, volume class TRANSIENT=30
and the amounts of transient and permanent disk PERMANENT=70
space allocated on the volume.
5-12 Modifying Input/Output (I/O) Configurations
Deleting Objects in
SYSGEN
When you use SYSGEN to delete objects from the system
conguration, there are four I/O Congurator commands available to
you: DCLASS, DDEV, DPATH, and DVOL. They are dened in the table
below and explained in the following sections.
Table 5-5. I/O Configurator Delete Commands
Command
Denition
Examples
DCLASS
Removes one or more class names from the
system. If the class does not exist, or if you
attempt to delete the DISC, CONSOLE, or
TAPE classes, SYSGEN displays an error
message.
DCLASS EPOC
DCLASS (EPOC,FASTLP)
DDEV
Removes a specic device, range of devices, all
products of a given product identication, all
devices of a given type, or all devices of a given
class name. You cannot delete the system disk
(LDEV 1) or the system console (LDEV 20).
DDEV LDEV=123
DDEV ID=HP2932A
DPATH
Deletes an I/O path and, optionally, all the I/O DPATH 4.2
paths below it in the conguration. If there are DPATH 2/8.2
I/O paths below the one you are deleting,
SYSGEN prompts you to conrm the action
before deleting them. If an I/O path is currently
used by a congured device, SYSGEN issues an
error and does not delete the path.
DVOL
Deletes a volume member from the system
conguration. To implement the change, you
must create a system load tape with the new
conguration and then use it to do an INSTALL.
Changing the
configuration online
DVOL MEMBER2
A new command le, DOIONOW, has been added to MPE/iX which
allows the system manager to immediately implement device
conguration changes made with SYSGEN. This command allows
you to keep the system online and available to users more of the
time, and gives you the exibility to change the conguration on an
\as needed" basis.
To change the conguration while the system is online, do the
following:
1. Make the necessary changes to the conguration with the I/O
Congurator. (This process is no dierent than it was before; for
more information, read the previous section of this chapter \Using
SYSGEN's I/O Congurator".
2. Keep the conguration changes and exit SYSGEN. The
information is saved in the le LOG4ONLN.PUB.SYS, which is
used by the DOIONOW command.
Modifying Input/Output (I/O) Configurations 5-13
3. At the CI prompt, execute the DOIONOW command by entering:
:DOIONOW
4. DOIONOW passes the LOG4ONLN le, which contains the new
conguration 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. If
the DOIONOW command generates an error, you may view this same
log le to determine the cause. This log le is purged and a new one
is created prior to invoking the new conguration, which means that
it only contains information for the last execution of IOCONFIG.
Once you have found the problem, you can then edit the input le for
the DOIONOW command, LOG4ONLN.PUB.SYS, to avoid duplicating
the events that created the error.
Using the IOCONFIG
Utility
With the release of version C.55.00 of MPE/iX, system managers can
now use a new utility, IOCONFIG, to change the I/O conguration
and implement the changes immediately without rebooting the
system.
The IOCONFIG utility automatically updates SYSGEN's base
conguration. IOCONFIG can completely replace the use of
SYSGEN for device conguration, especially when you need to make
conguration changes immediately; that is, without rebooting the
system. However, you should continue to use SYSGEN to congure
devices to have the changes take eect at the next reboot.
There is one occasion when you cannot use IOCONFIG in place of
SYSGEN's I/O Congurator: when the current base conguration
group is BOOTUP. IOCONFIG cannot modify conguration les
in the BOOTUP group, since these les are designed to maintain
a backup copy of the conguration les used in the last successful
START NORECOVERY which includes INSTALL and UPDATE. Therefore,
when BOOTUP is the current base conguration group, you must
use SYSGEN to make the conguration changes on the next START
NORECOVERY.
Note
There is another new option for online device conguration
introduced with Version C.55.00 of MPE/iX. The system manager
can use the I/O Congurator in SYSGEN, and then issue the
DOIONOW command to immediately begin making the changes online.
This command is described earlier in this chapter.
5-14 Modifying Input/Output (I/O) Configurations
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.
IOCONFIG Commands
Command
Abbreviations
Description
ADDDEVICE
adev, ad
Adds a device from the physical
conguration to the active conguration.
LISTDEVICE
ldev, ld
Lists the active device conguration.
DELETEDEVICE ddev, dd
Deletes a device from the active
conguration.
ADDCLASS
Adds a device class to the active
conguration.
aclass, ac
MODIFYCLASS mclass, mc
Modies a device class in the active
conguration.
LISTCLASS
Lists the active device class conguration.
lclass, lc
DELETECLASS dclass, dc
Deletes a device class from the active
conguration.
ADDPATH
apath, ap
Adds an intermediate path to the active
conguration.
LISTPATH
lpath, lp
Lists I/O paths for the active conguration.
DELETEPATH
dpath, dp
Deletes an I/O path from the active
conguration.
REDO
redo
Re-executes the command previously
executed.
HELP
he, h
Displays information about all commands or
about the specic command entered
following the HELP.
EXIT
ex, e
Exits IOCONFIG.
To use IOCONFIG in command mode, you enter IOCONFIG followed
by a single command passed as an INFO string at the CI prompt.
For example, you might want to list the devices or device classes in
the current conguration without executing any other command. To
do so, you would enter:
:IOCONFIG "lc"
Modifying Input/Output (I/O) Configurations 5-15
Device and device class conguration 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 eect immediately. As
a side-eect, those commands that update the conguration also
update the current SYSGEN boot conguration.
Adding a device with
IOCONFIG
To congure a tape drive, disk or a system printer into the system,
the system manager or operator uses the ADDDEVICE or ADEV
command. The syntax of the command is identical to that of
SYSGEN's ADEV command in IO level, except that the ID parameter
is optional. The command syntax is as follows:
ADDDEVICE
22
22
82
3
LDEV = #/#,#, . . .
3 22
3
98 2
3
3
PATH = devicepath
RSIZE
= recordsize
ID = productid
3
3
OUTDEV = outputdevice
93
8
JOB
>
>
>
>
>
>
7
6
>
>
DATA
>
>
>
>
7
6
>
>
7
6
>
>
>
INTERACTIVE >
7
6
>
>
>
>
7
6
>
>
>
>
DUPLICATIVE
72 2
62
=
<
3
7
6
INPUT
7 CLASS
6 MODE =
7
6
>
>
>
>
7
6
>
>
OUTPUT
>
>
7
6
>
>
>
>
7
6
>
>
AUTOREPLY >
>
7
6
>
>
>
>
>5
> NLIO
4
>
>
>
>
;
:
NONE
8
93
2
IN
>
>
>
>
>
>
6
7
>
>
OUT
>
>
6
7
>
>
<
=
62
7
3 CIO
6 CMODE =
7
6
7
NCIO
>
>
6
7
>
>
>
>
>
>
4
5
>
>
RANDOM
>
>
:
;
2
22
22
22
22
22
22
DEFAULT
3
PMGR = physicalmanagername
3
LMGR = logicalmanagername
3
3
3
PMGRPRI = physicalmanager priority
3
MPETYPE = compmodetype
3
3
MPESUBTYPE = compmodesubtype
3
DEVNAME = devicename
5-16 Modifying Input/Output (I/O) Configurations
3
3
3
3
3
= classname
3
9
To congure a SCSI device, it must be physically connected to
the specied 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 conguration). 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.
When adding a printer to the conguration that has the class SPOOL,
the spooler process for that device will automatically be started and
a message indicating this will appear on the console.
Listing one or more
devices with IOCONFIG
The system manager or operator can list all devices in the system
or one or more specied devices along with their conguration
information using the LISTDEVICE or LDEV command. When you
enter either command without parameters, information about all
devices currently congured in the system is listed. By providing one
or more parameters as the selection criteria, you can see information
about particular devices.
The command syntax is as follows:
LISTDEVICE
22
22
22
22
Deleting a device with
IOCONFIG
22
3
3
LDEV = #/#,#, . . .
ID = product number
3
TYPE = device type
3
3
3
CLASS = classname, . . .
3
DEST = OFFLINE
3
3
3
The system manager or operator may delete a device from the
conguration using the DELETEDEVICE or DDEV command. A device is
considered to be completely decongured when all its system-related
resources are recovered. DDEV, at this time, can only decongure two
kinds of devices completely: network printers and disks that are
attached to single-ended SCSI adapters.
The syntax of the DDEV command is identical to that of SYSGEN's
DDEV command in IO level. The command syntax is as follows:
DELETEDEVICE
22
22
22
3
82
ID = deviceid
3
3
3
LDEV = #/#,#, . . .
TYPE = devicetype
3
9
3
CLASS = classname
3
Modifying Input/Output (I/O) Configurations 5-17
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 congured before issuing this command.
With the release of version C.55.00 of MPE/iX, the maximum
number of devices that you can congure has substantially increased.
When there is a large number of congured devices, you may notice
a slight delay in system response as you add more. For example,
when the number of devices congured exceeds approximately 2,000,
the delay will be evident. It is not, however, indicative of a system
problem.
The syntax of the ADDCLASS command is as follows:
ADDCLASS
82
2
6
6
62
6 MODE
6
6
4
Modifying a device
class with IOCONFIG
=
3
3
CLASS = classname
8
IN
>
>
>
>
OUT
>
>
<
CIO
NCIO
>
>
>
>
>
RANDOM
>
:
DEFAULT
98 2
3
LDEV = #/#,#, . . .
9
93
>
>
>
7
>
>
>
=7
7
7
7
>
7
>
>
>
5
>
>
;
The system manager or operator can modify a device class by adding
or deleting one or more devices in it or by renaming it using the
MODIFYCLASS or MCLASS command. The syntax of this command is
identical to that of MCLASS in SYSGEN. The command syntax is as
follows:
MODIFYCLASS
22
22
22
3
82
3
CLASS = classname
NEWCLASS = classname
3
3
3
3
3
ALDEV = logical device #, . . .
DLDEV = logical device #, . . .
2
6
6
62
6 MODE
6
6
4
=
3
8
IN
>
>
>
>
OUT
>
>
<
CIO
>
> NCIO
>
>
>
RANDOM
>
:
DEFAULT
9
93
>
>
>
7
>
>
>
=7
7
7
7
>
>7
>
>
5
>
>
;
Currently, the system allows any device in the system to belong
to only one associated class at any time. For example, if a device
X belongs to a class Y and Y is associated to some user, then the
MODIFYCLASS command prevents you from adding X to another class
Z which is also associated to any user at the time.
5-18 Modifying Input/Output (I/O) Configurations
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 specied device classes, with their
conguration information using the LISTCLASS or LCLASS command.
When no parameter is used with this command, all device classes
currently congured 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.
The command syntax is as follows:
LISTCLASS
22
Deleting a device class
with IOCONFIG
22
3
3
CLASS = classname, . . .
DEST = OFFLINE
3
3
The system manager or operator can use the DELETECLASS or DCLASS
command to delete a device class that is not currently associated to
a user. To disassociate the device class from the user, the user must
execute the DISASSOCIATE command at the Command Interpreter
prompt.
The command syntax is as follows:
DELETECLASS
Configuring a device
adapter with IOCONFIG
82
3
CLASS = classname,...
9
It is often necessary to congure intermediate paths before a device
can be congured into the system. For example, you must congure
a SCSI device adapter before the rst device on that SCSI bus can
be congured. Intermediate path conguration is done just like
in SYSGEN. At this time, the command to delete a path is only
supported for the single-ended SCSI adapter. All other cases will fail
with an error.
The command syntax is as follows:
ADDPATH
22
22
22
22
82
3
3
PATH = devicepath
PMGR = physicalmgrname
3
3
PMGRPRI = physicalmgrpri
3
LMGR = logicalmgrname
3
98 2
3
ID = productid
9
3
3
MAXIOS = maxconcurrentchannelIOs
3
Modifying Input/Output (I/O) Configurations 5-19
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 specied
path in the active conguration. The command lists the congured
I/O paths according to their paths or to their associated I/O
manager. The syntax of the LISTPATH command appears below:
3
2
2
3
PATH= 2path3
7
6 LEVEL= #
2
37
LISTPATH 6
4 MANAGER= manager name,... 5
2
3
DEST= OFFLINE
The LEVEL parameter lists I/O paths at the level you specify:
Enter 1 to display channel adapter information
Enter 2 to display device adapter information
Enter 3 to display device information
The MANAGER parameter lists the I/O paths associated with
the given manager or managers, if the manager(s) exist. If not,
IOCONFIG displays a warning message.
Use the DEST parameter to send LISTPATH output to the le
IOCLIST. This le remains open until you exit IOCONFIG, at which
point the le is closed and printed.
Deleting an I/O path
with IOCONFIG
The system manager or operator can delete an I/O path and
all paths below it from the conguration with the DELETEPATH
command. IOCONFIG will only delete a path if it is not currently in
use or if it does not have an associated device. If either is true when
you issue the DELETEPATH command, a warning message appears.
The syntax of the command is:
2
3
DELETEPATH PATH = device path
Currently, the only paths that can be completely deleted are those
using a single-ended SCSI adapter.
Updating the device
class association table
with IOCONFIG
Many of the conguration commands implicitly update one or more
system reserved device classes. For example, the ADEV command
when used to congure a tape device, implicitly adds the new device
in TAPE device class. Also, these commands explicitly update one or
more device classes specied with the command.
The device class association information used by the ASSOCIATE
and DISASSOCIATE commands is stored in ASOCIATE.PUB.SYS.
This le is built when the system manager runs the program
ASOCTBL.PUB.SYS. Therefore, after you have issued IOCONFIG
commands, it is a good idea to update the le ASOCIATE.PUB.SYS
by running ASOCTBL.
5-20 Modifying Input/Output (I/O) Configurations
6
Modifying Logging Configurations
The LOG congurator 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
modications to databases and other les used in applications
programs. The system manager determines the maximum number
of logging processes and the maximum number of users per logging
process.
To access the LOG congurator, enter the LOG command
(abbreviated LO) at the SYSGEN prompt as shown in the following
example:
Entering the LOG
Configurator
d
sysgen>LOG
a
** LOG configurator commands **
c
show (sh)
slog (sl)
ulog (ul)
clear (cl)(c)
exit (ex)(e)
help (he)(h)
oclose (oc)
log>
hold (ho)
redo
Example 6-1. Activating the LOG Configurator
b
Modifying Logging Configurations 6-1
The help facility enables you to quickly identify the function and
syntax of those LOG congurator commands and options for
performing the multiple operations that dene or change logging
processes.
Using the LOG
Configurator Help
Facility
d
To obtain a list of the commands available for use in the LOG
congurator, enter HELP at the LOG congurator prompt as shown in
the following example:
a
log>HELP
** LOG configurator commands **
c
d
show (sh)
slog (sl)
ulog (ul)
clear (cl)(c)
exit (ex)(e)
help (he)(h)
oclose (oc)
redo
hold (ho)
log>
Example 6-2. LOG Configurator Help
To display the syntax for each available command, enter HELP ALL as
shown in the following example:
log>HELP ALL
b
a
command (abb) parameter=value
------------- ---------------
c
show (sh)
[command
[dest
= SLOG|ULOG|ALL]
= OFFLINE]
slog (sl)
[on
[off
= event#,...]
= event#,...]
ulog
[nlogprocs
= number processes allowed]
[usersperproc = users per logging process]
log>
Example 6-3. LOG Configurator HELP ALL
6-2 Modifying Logging Configurations
b
Entering HELP commandname provides help for a specic 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 congured.
ALL lists all the information associated with the LOG congurator.
OFFLINE redirects the output of the SHOW command to the SYSGEN
listing le, SYSGLIST. Using OFFLINE does not immediately generate
a printout. The information is sent to SYSGLIST until you either
enter the OCLOSE command or exit the congurator. Exiting the
congurator or using OCLOSE closes SYSGLIST and prints the le.
Using SHOW without using any parameters, is the same as specifying
SHOW ALL. In addition, the value entered for the ULOG parameter
includes the minimum, maximum, current, and default values.
d
c
To show the current user logging process, enter SHOW ULOG:
log>SHOW ULOG
configurable item
----------------# of user logging processes
# users per logging process
max
------128
1024
min
------2
1
current
------64
128
Example 6-4. Showing User Logging Processes
a
b
To view all currently congured values, enter SHOW ALL:
Modifying Logging Configurations 6-3
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
File Owner Change
129
Architected Interface
130
Additional Processor Launch
131
Password Change
134
System Logging Configuration
135
Restore
136
Printer Access Failure
137
ACD Change
138
Stream Initiation
139
User Logging
140
Process Creation
141
Security Configuration Change 142
Chgroup
143
File Open
144
CI Command Logging
145
Maintenance Request
146
UPS Monitor Event Logging
148
Diagnostic Information
150
High Priority Machine Check
151
Low Priority Machine Check
152
Directory Open/Close Logging
155
CM File Close
160
min
------2
1
current
------64
128
status
-----ON
ON
OFF
OFF
OFF
OFF
ON
ON
ON
OFF
OFF
OFF
ON
ON
ON
OFF
OFF
OFF
OFF
ON
OFF
OFF
ON
OFF
ON
ON
ON
OFF
OFF
ON
OFF
OFF
OFF
OFF
ON
ON
ON
OFF
OFF
Example 6-5. Showing All Configured Values
6-4 Modifying Logging Configurations
b
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. (Refer to the preceding example for a
list of event numbers and their denitions.)
The SLOG command enables and disables the selected system logging
events. SLOG has the following parameters:
[ON = event#, . . . ]
SLOG (SL)
[OFF = event#, . . . ]
Enable the logging of an event by entering SLOG event#, . . . :
log>SLOG 100
(Event 100 enabled)
log>SLOG ON=100
(Event 100 enabled)
or
Disable the logging of an event by entering SLOG OFF=event# , . . . :
log>SLOG OFF=100
(Event 100 disabled)
Entering SLOG without ON enables logging. Entering SLOG without an
event number causes an error:
log>SLOG
(error - no parameters are specified)''
Logging event 100 is a special case. If 100 is o, no logging (except
that forced on by MPE/iX) takes place.
Note
Some events are permanently set to ON. Currently, events 101, 111,
135, 146, and 150 are forced on by MPE/iX.
Modifying Logging Configurations 6-5
Logging User Events
User logging provides a means for system users and subsystems to
record additions and modications 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 congures the user logging process parameters.
ULOG has the following parameters:
ULOG (UL) [NLOGPROCS = numberprocesses allowed ]
[USERSPERPROC = usersperloggingprocess ]
NLOGPROCS controls the user logging ID (LID) table size. Lowering
NLOGPROCS loses all current logging ID information from the
tape created by SYSGEN. If NLOGPROCS remains unchanged or
increases, the current logging ID information is copied to tape. The
minimum and maximum number of processes allowed are 2 and 128,
respectively.
USERSPERPROC species the maximum number of users assigned
to each congured logging process. The minimum and maximum
number of users per logging process are 1 and 1024, respectively.
Note
Changing NLOGPROCS takes eect when a tape is created and an
UPDATE CONFIG or INSTALL is conducted. Refer to Chapter 3 for
information on installing or updating the operating system.
To set the number of processes or users per process, enter ULOG
followed by the number of processes or users:
log>ULOG 40 ** Number of Processes **
or
log>ULOG USERSPERPROC=40
Clearing Log
Configuration
Changes
** Number of Users per Process **
If you desire to clear all LOG conguration changes made, enter the
CLEAR command at the LOG congurator prompt.
log>CLEAR
Once a SYSGEN> KEEP is done, the changes kept become permanent
and CLEAR does not remove them.
6-6 Modifying Logging Configurations
Holding and Saving
Configuration
Changes
Using the system logging and user logging commands described in
the following sections changes the LOG conguration specied in
the SYSGEN command line or global BASEGROUP command. These
changes are temporary and are easily lost if not properly saved.
Saving conguration changes is a two-step procedure. After you alter
a conguration, you must, rst, hold the changes before exiting the
congurator. Second, use the global module KEEP command to save
the changes.
To hold changes, enter the HOLD command at the LOG congurator
prompt:
log>HOLD
You can work in a SYSGEN congurator, hold the changes, and
continue working in other SYSGEN congurators before saving the
changes.
To save the changes, hold all desired changes, exit to SYSGEN's
global module, and issue the KEEP command:
sysgen>KEEP newgroupname
Refer to Chapter 4 for additional information on using the KEEP
command.
Entering an MPE
Command from the
LOG Configurator
Use the colon (:) to introduce an MPE command from the LOG
congurator. To issue an MPE command, enter the command along
with the colon. For example,
log>:SHOWTIME
THU, APR 20, 1989, 2:55PM
log>
Modifying Logging Configurations 6-7
Exiting the LOG
Configurator
Use the EXIT command to terminate the LOG congurator and
return to the SYSGEN global module. Exit may be abbreviated EX
or E. To end working in the LOG congurator, enter EXIT at the
LOG congurator 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. When the diagnostic user interface
prompt (DUI>) appears, enter RUN LOGTOOL.
In order to print a log, issue the following:
1. :SYSDIAG
2. DUI>RUN LOGTOOL
3. LOGTOOL>LIST LOG=log# OUTFILE=LP
4. LOGTOOL>EXIT
5. DUI>EXIT
Enter HELP after the LOGTOOL prompt for more information. The
STATUS command reports on the status of all system log les.
The following example shows the use of the STATUS command in the
sequence of printing a log.
d
c
:SYSDIAG
DUI >RUN LOGTOOL
LOGTOOL>status
LOGTOOL>list log=0027 outfile=LP
DUI >EXIT
If you do not specify the OUTFILE parameter, the log prints on your
terminal screen. Typically this report is very long and ties up your
terminal for quite some time. If this does happen, you can enter
4CTRL5 Y to break the process.
6-8 Modifying Logging Configurations
a
b
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 specic 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 @.
For example, to select log records from log les 1 through 5, with
log information about password changes (log type 134), and user
identication JTEST,MARIA.PAYROLL, you would enter the
following.
>LIST LOG=1/5;TYPE=134;JSNAME=JTEST;USER=MARIA;ACCOUNT=PAYROLL
This selection option is valid for the log types listed below:
102 Job Initiation
103 Job Termination
104 Process Termination
105 NM File Close (also 160)
108 Spooling Log
112 Physical Mount/Dismount
113 Logical Mount/Dismount
114 Tape Label
115 Console Log
116 Program File Event
120 Native Mode Spooling
130 Architected Interface
134 Password Change
135 System Logging Conguration
136 Restore
137 Printer Access Failure
138 ACD Change
139 Stream Initiation
140 User Logging
141 Process Creation
143 Chgroup
144 File Open
Modifying Logging Configurations 6-9
7
Modifying Miscellaneous Configuration Elements
The MISC congurator provides commands to congure various
types of le information dicult to categorize elsewhere. The MISC
congurator 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 congurator, enter the MISC command
(abbreviated MI) at the SYSGEN prompt.
d
a
sysgen>MISC
** MISC configurator commands **
c
misc>
drin (dr)
resource (re)
system (sy)
io
session (se)
clear (cl)(c)
oclose (oc)
exit (ex)(e)
redo
job (jo)
show(sh)
help (he)(h)
Example 7-1. Activating the MISC Configurator
lrin (lr)
stack (st)
hold (ho)
b
Modifying Miscellaneous Configuration Elements 7-1
Using the MISC
Configurator Help
Facility
d
The help facility enables you to identify quickly the function and
syntax of MISC congurator commands.
To obtain a list of the commands available for use in the MISC
congurator, enter HELP at the MISC congurator 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. MISC Configurator HELP
Entering HELP ALL produces a list of all MISC congurator
commands and syntax. Example 7-3 displays the output.
7-2 Modifying Miscellaneous Configuration Elements
b
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 segment size]
cm code segs per proc]
max size of xdata seg]
max data segs/proc]
session (se)
[maxlimit
[logontimeout
[citimeout
[pool
=
=
=
=
maximum session limit]
time in seconds]
time in minutes]
pool-size]
show (sh)
[command
[dest
= JOB|RESOURCE|SESSION|
STACK|SYSTEM|ALL
= OFFLINE]
stack (st)
[nm
[maxnm
[cm
[maxcm
[heap
[maxheap
=
=
=
=
=
=
system (sy)
[userversion
[logonprompt
[ciprompt
[enforcelogonudcs
= global-rin#,...
default nm stack size]
max size of nm stack]
default cm stack size]
max size of cm stack]
default heap size]
max size of nm heap]
= x.yy.zz]
= max-255-characters]
= max-255-characters]
= ON|OFF]
Example 7-3. MISC Configurator HELP ALL Output
b
Modifying Miscellaneous Configuration Elements 7-3
You can request help for a specic MISC congurator command by
entering HELP commandname at the MISC congurator 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 congurable items referenced by it. SHOW has the following
parameters:
SHOW (SH)
[ [COMMAND =] [
[
[
[
[
[
[
[ [DEST
=]
IO
JOB
RESOURCE
SESSION
STACK
SYSTEM
ALL
OFFLINE
]
]
]
]
]
]
]
]
JOB displays the job-related limits and default operating points. The
displayed information includes: the CPU time limit for batch jobs,
the maximum system job limit, and the number of preinitialized
job processes (POOL). Refer to the MPE/iX Commands Reference
Manual Volumes 1 and 2 (32650-90003 and 32650-90364) for
information on the JOB command.
Each of the remaining parameters has a corresponding command
dened in this chapter.
RESOURCE displays system resource allocation values.
SESSION displays the session-related limits of the system and the
default operating points.
STACK displays the sizes of the NM stack, CM stack, and the heap.
SYSTEM displays the settings of various system resource values, the
system ID, and logon and command interpreter prompts.
ALL lists all of the information described above.
OFFLINE redirects the output of the SHOW command to the SYSGEN
listing le, SYSGLIST. Using OFFLINE does not immediately generate
a printout. The information is sent to SYSGLIST until you either
7-4 Modifying Miscellaneous Configuration Elements
enter the OCLOSE command or exit the congurator. Exiting the
congurator 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 congurator, enter SHOW or SHOW ALL at the MISC
congurator prompt.
Example 7-4demonstrates the output from SHOW ALL:
d
a
misc>SHOW ALL
c
IO command
----------------DYNAMIC INPUT DEVS
DYNAMIC OUTPUT DEVS
DYNAMIC IO DEVS
parameter
MAX
--------------maxdyninput
999
maxdynoutput
999
msxdynio
999
MIN
------0
0
0
CURRENT
------2
4
332
JOB command
----------------DEFAULT CPU LIMIT
MAXIMUM LIMIT
POOL SIZE
parameter
--------cputime
maxlimit
pool
MAX
------32767
999
200
MIN
------0
0
1
CURRENT
------0
60
1
RESOURCE command
----------------GLOBAL RIN LIMIT
TOTAL RIN LIMIT
IOMONT LIMIT
MAX CM CODE SIZE
CM SEGS PER PROC
MAX XDATA
MAX XDATA PER PROC
parameter
MAX
--------------grins
1365
rins
5459
iomont
100
maxcmcode
16384
cmsegs
255
maxxdata
32764
xdataperproc
255
MIN
------0
5
10
1024
1
0
0
CURRENT
------48
150
20
16384
63
32764
255
SESSION command
----------------MAXIMUM LIMIT
SECONDS TO LOGON
CI TIMEOUT (MIN)
POOL SIZE
parameter
MAX
--------------maxlimit
999
logontimeout
600
citimeout
546
pool
200
MIN
------1
10
0
1
CURRENT
------60
180
0
1
Example 7-4. MISC Configurator SHOW ALL Output
b
Modifying Miscellaneous Configuration Elements 7-5
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.10
MPE/iX:
:
X.50.10
enforcelogonudcs OFF
Example 7-4 MISC Configurator SHOW ALL Output (continued)
b
Example 7-5 demonstrates using the SHOW command to see the values
allocated to a particular parameter:
d
a
misc>SHOW JOB
c
JOB command
----------------DEFAULT CPU LIMIT
MAXIMUM LIMIT
POOL SIZE
parameter
--------cputime
maxlimit
pool
MAX
------32767
999
200
MIN
------0
0
1
Example 7-5. MISC Configurator SHOW Output
7-6 Modifying Miscellaneous Configuration Elements
CURRENT
------0
60
1
b
Deleting Global
Resource
Identification
Numbers (RIN)
A resource identication number (RIN) identies a user-dened
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 identication numbers. DRIN has the following parameter:
DRIN (DR)
[GLOBAL
=] global-rin number
To delete a global RIN or a range of global RINs, enter DRIN and the
RIN at the MISC congurator prompt:
misc>DRIN 4
** Deletes single RIN **
misc>DRIN (1,2,3,4,15,84)
** Deletes group of RINs **
The changes made using the DRIN command take eect only if a tape
containing the changes is generated and the newly created tape is
used to update the conguration or install the system.
Configuring
Job-Related Limits
The JOB command (abbreviated JO) congures job-related limits and
default operating modes. JOB has the following parameters:
JOB (JO)
[CPUTIME = secondcount ]
[MAXLIMIT = maximumjoblimit ]
[POOL
= poolsize ]
CPUTIME sets the default CPU time limit for batch jobs.
MAXLIMIT sets the maximum job limit that may be set through the
LIMIT command.
POOL is the number of precreated JSMAIN processes ready to be used
when someone logs on.
Table 7-1 shows the minimum and maximum numbers for the JOB
command parameters:
Table 7-1.
Minimum and Maximum Values for JOB Command
Parameters
Parameter
Minimum
Maximum
CPUTIME
0
32767
MAXLIMIT
0
2700
POOL
1
200
To change a job-related parameter value, enter the JOB command and
at least one parameter to change:
Modifying Miscellaneous Configuration Elements 7-7
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 oine. LRIN has
the following parameter:
LRIN (LR)
[[DEST
=] OFFLINE ]
OFFLINE redirects the output of the LRIN to the SYSGEN listing le,
SYSGLIST. Using OFFLINE does not immediately generate a printout.
The information is sent to SYSGLIST until you either enter the
OCLOSE command or exit the congurator. Exiting the congurator
or using OCLOSE closes SYSGLIST and prints the le.
To display the RIN ownership on the console screen, enter LRIN
without a parameter:
misc>LRIN
rin
____
3
148
149
150
Note
username
_______________
MANAGER .SYS
MANAGER .QASYS
MANAGER .QASYS
MANAGER .QASYS
This example may vary depending on which system you have.
7-8 Modifying Miscellaneous Configuration Elements
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.
RINS sets the total number of global and local RINs to be allocated.
IOMONT sets the size of the I/O monitor area.
MAXCMCODE sets the maximum CM code segment size allowed for any
given process.
MAXXDATA sets the maximum extra data segment size allowed.
XDATAPERPROC sets the maximum number of extra data segments for
any given process.
Note
Changes to GRINS and RINS take eect only if a tape containing the
changes is generated and the newly created tape is used to update
the conguration or install the system.
Table 7-2 shows the minimum and maximum values for the RESOURCE
command parameters.
Table 7-2.
Minimum and Maximum Values for RESOURCE
Parameters
Parameter
Minimum
Maximum
GRINS
1
1365
RINS
5
5459
IOMONT
10
100
1024
16384
CMSEGS
1
255
MAXXDATA
0
32764
XDATAPERPROC
0
255
MAXCMCODE
To set one of the system resource allocations, enter the RESOURCE
command and at least one parameter that is to change:
Modifying Miscellaneous Configuration Elements 7-9
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) congures session-related
limits and default operating points. SESSION has the following
parameters:
SESSION (SE)
[MAXLIMIT
[LOGONTIMEOUT
[CITIMEOUT
[POOL
=
=
=
=
maximum session limit]
time in seconds]
time in minutes]
pool-size]
MAXLIMIT sets the maximum session limit.
LOGONTIMEOUT sets the number of seconds a user has to log on to the
system.
CITIMEOUT sets the number of minutes a user may be inactive at the
terminal before being automatically logged o the system. A value of
zero prevents automatic log o.
POOL is the number of precreated JSMAIN processes ready to be used
when someone logs on.
Table 7-3 show the minimum and maximum values for SESSION
command parameters.
Table 7-3.
Minimum and Maximum Values for SESSION Parameters
Parameter
Minimum
Maximum
MAXLIMIT
1
2700
LOGONTIMEOUT
10
2700
CITIMEOUT
0
546
POOL
1
200
To congure a session-related limit, enter the SESSION command and
at least one parameter to change. Here are three examples of the
SESSION command. They show parameters in keyword, positional,
and in combination formats, respectively.
misc>SESSION MAXLIMIT=80 LOGONTIMEOUT=300
7-10 Modifying Miscellaneous Configuration Elements
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) congures 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. The
NM value must be less than the values of MAXNM (see below).
MAXNM sets the maximum NM stack size, which is expressed in bytes.
CM sets the default CM stack size, which is expressed in words (16
bits in length). The value set for the CM parameter must be less than
the value set for the MAXCM parameter (see below).
MAXCM sets the maximum allowable CM stack size.
HEAP sets the default heap size, which is expressed in bytes. The
value must not exceed MAXHEAP (see below).
MAXHEAP sets the maximum heap size, which is expressed in bytes.
To change one of the STACK parameters, enter the STACK command
and at least one parameter to change. Here are two examples. The
rst is keyword and the second is positional.
mi>STACK NM=262144 CM=4096
mi>STACK 262144 262144,,20000
Table 7-5 shows the minimum and maximum values of the STACK
command parameters.
Modifying Miscellaneous Configuration Elements 7-11
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.zz]
[ [LOGONPROMPT =] prompt string]
[ [CIPROMPT
=] prompt string]
USERVERSION allows the system manager to identify the system with
a version meaningful to your environment. This might identify some
conbination of third-party products.
LOGONPROMPT sets the system prompt.
CIPROMPT sets the prompt used by the command interpreter.
Table 7-6 shows the default values for the SYSTEM command
parameters:
Table 7-5. Default Values for SYSTEM Parameters
Parameter
Value
USERVERSION
A.50.00
PROMPT
MPE/iX:
CIPROMPT
:
To set one of the parameters relating to the SYSTEM command, enter
the command and at least one parameter to change. Here are two
examples of the keyword and positional formats:
misc>SYSTEM USERVERSION=A.A1.35
misc>SYSTEM A.A1.35 150:
7-12 Modifying Miscellaneous Configuration Elements
Note
Clearing MISC
Configuration
Changes
A changed USERVERSION, as in the previous example, is lost if the
MISC congurator 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 conguration changes made, enter the
CLEAR command at the MISC congurator prompt.
misc>CLEAR
Once a SYSGEN> KEEP is done, the changes become permanent and
CLEAR does not remove them.
Holding and Saving
Configuration
Changes
Using the MISC congurator commands described in the previous
sections changes the conguration specied in the SYSGEN
command line or global BASEGROUP command. These changes are
temporary and are lost if not properly saved.
Saving conguration changes is a two-step procedure. After you alter
a conguration, you must rst hold the changes before exiting the
congurator. Second, use the global module KEEP command to save
the changes.
To hold changes, enter the HOLD command at the MISC congurator
prompt:
misc>HOLD
You can work in a SYSGEN congurator, hold the changes, and
continue working in other SYSGEN congurators before saving the
changes.
To save the changes, rst hold all desired changes, exit to SYSGEN's
global module, and issue the KEEP command:
sysgen>KEEP newgroupname
For additional information on using the KEEP command, refer to
Chapter 4.
Modifying Miscellaneous Configuration Elements 7-13
Entering an MPE
Command from the
MISC Configurator
Exiting the MISC
Configurator
Use the colon (:) to introduce an MPE command while in the MISC
congurator. 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 congurator and
return to the SYSGEN Global module. EXIT may be abbreviated EX
or E. To end working in the MISC congurator, enter EXIT at the
MISC congurator prompt:
misc>EXIT
sysgen>
7-14 Modifying Miscellaneous Configuration Elements
8
Modifying System File Configurations
The SYSFILE congurator 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 congurator that permit the user to add, delete,
and replace objects through a series of related commands.
Note
In order for SYSFILE congurator changes to become permanent,
you must generate a boot tape. Update or install the system with
the newly created boot tape to implement the changes.
Example 8-1 demonstrates activating the SYSFILE congurator.
To access the SYSFILE congurator, enter the SYSFILE command
(abbreviated SY) at the SYSGEN prompt:
Entering the
SYSFILE
Configurator
d
a
sysgen>SY
** SYSFILE configurator commands **
c
aauto (aa)
cmsl (cm)
dsprog (ds)
rcat (rc)
rnmlib (rn)
aboot (ab)
dauto (da)
lcmsl (lc)
rcmsl (rcm)
rsprog (rs)
acmsl (ac)
dboot (db)
rauto (ra)
rdcc (rd)
show (sh)
asprog (as)
dcmsl (dc)
rboot (rb)
ripl (ri)
clear (cl)(c)
exit (ex)(e)
help (he)(h)
hold (ho)
Example 8-1. Activating the SYSFILE Configurator
b
For additional information on entering the SYSFILE congurator,
refer to Chapter 4.
Modifying System File Configurations 8-1
Using the SYSFILE
Configurator Help
Facility
d
The help facility enables you to identify quickly the function and
syntax of SYSFILE congurator commands and options.
The help facility operates similarly to the global help facility.
Example 8-2 demonstrates using the SYSFILE congurator's help
facility to list all available SYSFILE commands. To obtain the list of
commands, enter HELP at the SYSFILE congurator prompt:
a
sysfile>HELP
** SYSFILE configurator commands **
c
aauto (aa)
cmsl (cm)
dsprog (ds)
rcat (rc)
rnmlib (rn)
aboot (ab)
dauto (da)
lcmsl (lc)
rcmsl (rcm)
rsprog (rs)
acmsl (ac)
dboot (db)
rauto (ra)
rdcc (rd)
show (sh)
asprog (as)
dcmsl (dc)
rboot (rb)
ripl (ri)
clear (cl)(c)
exit (ex)(e)
help (he)(h)
hold (ho)
Example 8-2. SYSFILE Configurator HELP
8-2 Modifying System File Configurations
b
Example 8-3 demonstrates using the SYSFILE congurator's help
facility for listing all SYSFILE commands and their syntax. To
display the syntax for each available command at the current level,
enter HELP ALL:
d
a
sysfile>HELP ALL
c
commands (abb) parameter=value
-------------- --------------aauto (aa)
file
= filename
type
= DISC|TAPE|BOTH
aboot (ab)
image
= boot image name
file
= filename
type
= DISC|TAPE|BOTH
acmsl (ac)
seg
= segment-name
file
= filename
[mode
= S|C|P|U]
asprog (as)
prog
= program-name
file
= filename
cmsl (cm)
[sl
= sl-name]
dauto (da)
type
= DISC|TAPE|BOTH
dboot (db)
image
= boot-image-name,...
dcmsl (dc)
seg
= segment-name,...
dsprog (ds)
prog
= program-name,...
lcmsl (lc)
[seg
= segment-name]
rauto (ra)
file
= autoboot filename
type
= DISC|TAPE|BOTH
rboot (rb)
image
= boot-image-name
file
= filename
type
= DISC|TAPE|BOTH
rcat (rc)
name
= filename
rcmsl (rcm)
seg
= segment-name
file
= filename
[mode
= S|C|P|U]
rdcc (rd)
file
= filename
ripl (ri)
image
= IPL image name
file
= IPL file name
type
= DISC|TAPE|BOTH
rnmlib (rn)
file
= filename
rsprog (rs)
prog
= program-name
file
= filename
show (sh)
[file
= AUTO|BOOT|CATALOG|CMSL|DCC|IPL
NMLIB|SPROG|ALL]
[dest
= OFFLINE]
Example 8-3. SYSFILE Configurator HELP ALL
b
Modifying System File Configurations 8-3
d
To request help for a specic SYSFILE congurator command, enter
HELP commandname at the SYSFILE congurator 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. SYSFILE Configurator HELP ABOOT
b
The SYSFILE congurator commands perform ve actions (add,
delete, replace, list, and specify) on eight objects (autoboot image,
boot image, compatibility mode segmented library (CMSL), system
program, system catalog, network conguration (NETWORK
CONFIG), initial program loader (IPL) image, and native mode
library (NM LIBRARY)). In addition, the SYSFILE congurator
provides other commands, some of which are common to other
SYSGEN congurators: CLEAR, EXIT, HELP, HOLD, OCLOSE, and the
colon (:).
Table 8-1 shows a command matrix of the add, delete, replace, list,
and specify commands. The objects are listed from top to bottom,
and the actions are listed from left to right.
8-4 Modifying System File Configurations
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.
Note
Caution
The examples used to demonstrate SYSFILE congurator commands
may produce display screens that do not exactly match output from
your system. What SYSGEN displays depends entirely on how your
system is congured.
Do not use the SYSFILE> RSPROG command to rename
Hewlett-Packard supplied MPE/iX HP 3000 system les. A renamed
system le can corrupt your system during an update. This problem
can occur if you have third party software installed on your system
and you have renamed some system les to use this software.
Use the SHOW command in SYSFILE to ensure that all
Hewlett-Packard supplied system les have retained their original
name. System lenames in both columns should be identical. If
they are not identical, rename the les in the second column to the
lename in the rst column.
Modifying System File Configurations 8-5
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 congured.
CATALOG shows the system catalog in use.
CMSL shows the CMSL (compatibility mode segmented library) in
use.
DCC shows which le will be used for network conguration.
IPL shows the IPL images in use.
NMLIB shows the NM library names.
SPROG shows the specied system program names.
ALL shows all of the above information.
OFFLINE redirects the output of the SHOW command to SYSGEN's
listing le, SYSGLIST. Using OFFLINE does not immediately generate
a printout. 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.
To see current le information, enter the SHOW command and at least
one parameter:
sysfile>SH NMLIB
NM LIB
= NL.PUB.SYS
To show all the current system le information for system libraries,
programs and the message catalog, enter SHOW ALL or SHOW:
8-6 Modifying System File Configurations
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.MPEXL.SYS
TDIAG.MPEXL.SYS
EDBC.MPEXL.SYS
EDPROC.MPEXL.SYS
FILENAME
-------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.MPEXL.SYS
TDIAG.MPEXL.SYS
EDBC.MPEXL.SYS
EDPROC.MPEXL.SYS
TYPE
---disc
disc
disc
tape
tape
both
both
both
both
both
both
both
both
both
both
both
both
both
both
both
both
both
both
IPL FILE
--------ISL2.MPEXL.SYS
MMSAVE.MPEXL.SYS
FILENAME
-------ISL2.MPEXL.SYS
MMSAVE.MPEXL.SYS
TYPE
---tape ipl
disc ipl
Example 8-5. SYSFILE Configurator SHOW ALL Output
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
boot
b
Modifying System File Configurations 8-7
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
.
.
system
system
system
system
system
prog
prog
prog
prog
prog
prog
prog
prog
prog
prog
Example 8-5. SYSFILE Configurator SHOW ALL Output (continued)
The add commands (AAUTO, ABOOT, ACMSL, and ASPROG) add objects
to the list of les dumped onto SYSGEN's tape:
AAUTO adds an autoboot le to the list of les.
ABOOT adds a boot image to the list of les.
ACMSL adds a segment to a temporary copy of the CMSL, which
SYSGEN automatically manages.
ASPROG adds a system program or other le to the list of les.
Adding autoboot files
The AAUTO command (abbreviated AA) adds an autoboot le to the
list of les dumped onto SYSGEN's tape. The command has the
following parameters:
AAUTO (AA)
[FILE
[TYPE
=]
=
autobootlename
DISC ]
[ TAPE ]
[ BOTH ]
FILE species the le name that contains autoboot commands. If it
is not fully qualied with group and account name, it defaults to the
current group and account. If the specied le does not exist, an
error occurs, and the system issues a message.
Note
Always use fully qualied le names.
TYPE species the type of autoboot les to add. TYPE allows the
following types:
8-8 Modifying System File Configurations
b
DISC
Species that the le is applicable to a disk boot only.
TAPE
Species that the le is applicable to a tape boot only.
BOTH
Species 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 conguration. The command has the following
parameters:
ABOOT (AB)
[IMAGE
[FILE
[TYPE
=]
=]
=
[
[
bootimagename
lename
DISC ]
TAPE ]
BOTH ]
IMAGE species the name of a boot image. If the specied boot image
already exists, an error occurs.
FILE adds the le name of the boot image. If the le name is not
fully qualied, it defaults to the current group and account. If
SYSGEN is run from a dierent group and account when the tape
is made, unexpected results occur (for example, cannot find the
specified files). If the le to be added does not exist, an error
occurs.
TYPE species the type of boot images to add. TYPE allows the
following types:
DISC
Species that the le is applicable to a disk boot only.
TAPE
Species that the le is applicable to a tape boot only.
BOTH
Species that the le is applicable to both disk boot and tape
boot.
To add le information for the boot image, enter the ABOOT
command, le name, and at least one parameter:
sysfile>ABOOT START2.UTIL.SYS START2.UTIL.SYS TYPE=DISC
Modifying System File Configurations 8-9
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 species a new segment name with a maximum of eight
characters. If an existing segmentname is specied, an error occurs.
FILE species a le name to be added to the CMSL. The lename
parameter can be fully qualied with group and account. If not, it
defaults to the current group and account. If lename cannot be
found, an error occurs.
MODE indicates where the added SL segment is to reside. It expects
one of the four options listed below. Other entries cause errors.
Adding file names to
dump to tape
P
Declares a segment to be a permanently allocated user segment.
This parameter performs the same function as the ALLOCATE
command.
S
Declares a segment to be a permanently allocated system
intrinsic segment (in virtual memory).
C
Declares a segment to be a core-resident system intrinsic
segment.
U
Declares a segment to be a temporarily allocated user segment.
The ASPROG command (abbreviated AS) adds a system program or
other le to the list of les to be saved on tape. The command has
the following parameters:
ASPROG (AS) [PROG
[FILE
=] program-name
=] lename
PROG expects a system program name. If the specied program-name
already exists in the system program list, an error occurs.
FILE expects a le name to be used as the system program. If it is
not fully qualied with group and account name, it defaults to the
current group and account. If the specied lename does not exist,
an error occurs.
To add a program to tape, enter the program and le name:
sysfile>ASPROG FCOPY.PUB.SYS FCOPY.PUB.SYS
8-10 Modifying System File Configurations
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 specied 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 conguration.
Deleting autoboot
images
The DAUTO command (abbreviated DA) deletes the specied autoboot
type from the list of les dumped onto SYSGEN's tape. The
command has the following parameter:
DAUTO
[TYPE =
DISC ]
[ TAPE ]
[ BOTH ]
TYPE species the type of autoboot le deleted. The following types
are allowed:
DISC
Species that the le applies to disk only.
TAPE
Species that the le applies to tape only.
BOTH
Species that the le applies to both disk and tape.
Deleting an autoboot le, creating a SYSGEN tape, and updating
your system using the newly generated tape does not remove the disk
autoboot le from the system. Remove the disk le using the ISL
INSTALL command.
Deleting boot images
The DBOOT command (abbreviated DB) deletes a boot image le
name. If the boot image has an associated library, DBOOT also deletes
the library. DBOOT has the following parameter:
DBOOT (DB)
[IMAGE
=] bootimagename
IMAGE is a repeated parameter that species which boot image names
you want to delete. If a specied boot image name does not exist in
the conguration, a warning is issued.
Modifying System File Configurations 8-11
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 lename
Deleting compatibility
mode segments from a
SYSGEN tape
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, . . .
SEG is a repeated parameter that species the existing segment name.
If a nonexistent segment name is specied, an error occurs.
Use the LCMSL command to list the contents of the CMSL.
Removing system
programs from a
SYSGEN tape
The DSPROG command (abbreviated DS) removes system programs
or les from the system conguration. DSPROG has the following
parameter:
DSPROG (DS)
[PROG
=] programname, . . .
PROG is a repeated parameter that species the system program name
to be deleted. If a specied program name does not exist, an error
occurs.
To remove a program or le name, enter the command and name:
sysfile>DS FCOPY.PUB.SYS
Deleting a system program does not remove it from the disk. To
remove it from disk, an ISL INSTALL must be performed.
Replacing Objects
on the SYSGEN
Tape
The replace commands (RAUTO, RBOOT, RCAT, RCMSL, RDCC, RIPL,
RNMLIB, and RSPROG) replace or modify information in the list of
SYSGEN dump les.
RAUTO replaces an existing autoboot image or modies the autoboot
type.
RBOOT replaces an existing boot image or modies the boot type.
RCAT replaces the message catalog.
8-12 Modifying System File Configurations
RCMSL replaces a segment in the temporary copy of the CMSL.
RDCC replaces network conguration 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. The command
has the following parameters:
RAUTO (RA)
[FILE =] autobootlename]
[TYPE = DISC ]
[ TAPE ]
[ BOTH ]
FILE species a le name to replace the designated autoboot image.
If it is not fully qualied with group and account name, it defaults to
the current group and account. If the specied le does not exist, an
error occurs.
TYPE species the boot image type. The various types are dened as
follows:
DISC
Species that the le is applicable to a disk boot only.
TAPE
Species that the le is applicable to a tape boot only.
BOTH
Species that the le is applicable to both disk boot and tape
boot.
To modify or replace an autoboot image le name, enter the
command, fully qualied le name, and type:
sysfile>RAUTO lename TYPE=DISC
Use the SHOW command to display the autoboot image le names
maintained by the system.
Modifying System File Configurations 8-13
Replacing boot images
The RBOOT command (abbreviated RB) modies 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 species an existing boot image name to be modied or
replaced. If the specied boot image does not exist, an error occurs.
FILE species a le name to replace the designated boot image. If it
is not fully qualied with group and account name, it defaults to the
current group and account. If the specied le does not exist, an
error occurs.
TYPE species the boot image type. The various types are dened as
follows:
DISC
Species that the le is applicable to a disk boot only.
TAPE
Species that the le is applicable to a tape boot only.
BOTH
Species that the le is applicable to both disk boot and tape
boot.
To modify or replace a boot image le name, enter the command,
image name, and fully qualied le name. Here are two examples.
sysfile>RBOOT imagename TYPE=DISC
sysfile>RBOOT imagename lename DISC
Use the SHOW command to display the boot image le names
maintained by the system.
8-14 Modifying System File Configurations
Configuring a message
catalog
The RCAT command (abbreviated RC) congures 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 species a catalog le name. If the name is not fully qualied,
it defaults to the current group and account.
To replace the default catalog name CATALOG.PUB.SYS with a new
catalog name, enter RCAT and the fully qualied le name:
sysfile>RCAT lename.group.account
If the new message catalog le was not previously created, an error
occurs.
Note
Replacing a CMSL
segment
For information on how to modify an existing message catalog, refer
to the Message Catalogs Programmer's Guide (32650-60012).
The RCMSL command (abbreviated RCM) replaces a segment in the
CMSL. RCMSL has the following parameters:
RCMSL (RCM)
[SEG =] segment-name
[FILE =] lename
[MODE = S ]
[ C ]
[ P ]
[ U ]
SEG species a new segment name of maximum eight characters. If a
nonexistent segment name is specied, an error occurs.
FILE species a le name to be added to the CMSL. The lename
parameter can be fully qualied with group and account. If not, it
defaults to the current group and account. If the le name cannot be
found, an error occurs.
MODE indicates where the added SL segment is to reside. It expects
one of the four options listed below. Other input causes an error.
P
Declares a segment to be a permanently allocated user segment.
This parameter requests the same function as the ALLOCATE
command.
S
Declares a segment to be a permanently allocated system
intrinsic segment (in virtual memory).
C
Declares a segment to be a core-resident system intrinsic
segment.
U
Defaults if MODE is not specied.
Modifying System File Configurations 8-15
Use the LCMSL command to display the segments maintained in the
CMSL.
Replacing or defining a
network configuration
file
The RDCC command (abbreviated RD) denes the network
conguration le to be used. This command also checks for conicts
with SYSGEN's I/O conguration. 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.
RDCC has the following parameter:
RDCC (RD)
=] lename
[FILE
The FILE parameter identies the network conguration le. If
the name is not fully qualied, it defaults to the current group and
account. If no le paramter is entered, the network conguration le
is changed back to NMCONFIG.PUB.SYS.
To add the network conguration le information to the current
SYSGEN conguration information, enter the command and le
name. Then, follow this sample sequence:
sysfile>RDCC lename.group.account
sysfile>HOLD
(Cross-validation conflicts noted)
sysfile>EXIT
sysgen>IO
(Make I/O changes if necessary)
(Conflicts also noted here)
sysgen>KEEP NETWORK (Conflicts also noted here)
sysgen>TAPE
(Conflicts also noted here)
For additional information, refer to Chapter 5. For additional
information on remote congurations, refer to the Asynchronous
Serial Communications System Administrator's Reference Manual
(32022-61001) and the HP 3000/iX Network Planning and
Conguration Guide (36922-61023).
Replacing an IPL image
The RIPL command (abbreviated RI) replaces an existing IPL image
in the list of les dumped onto SYSGEN's tape. The command has
the following parameters:
2
3
2
3
RIPL (RI) IMAGE = imagename FILE = lename
IMAGE species an existing IPL image to be modied or replaced. If
the specied image does not exist, an error occurs and the system
issues a message.
FILE species a le name to replace the specied IPL image. If it is
not fully qualied with group and account name, it defaults to the
current group and account. If the specied le does not exist, an
error occurs and the system issues a message.
There can be only one disk and one tape IPL, each of which is
replaced by its image name. Both IPL les must reside on the tape.
8-16 Modifying System File Configurations
To replace an IPL image, enter the command and the image and le
names:
sysfile>RIPL imagename lename
Replacing the native
mode library
The RNMLIB command (abbreviated RN) replaces the system NM
library that resides in NL.PUB.SYS. The RNMLIB command has the
following parameters:
2
3
RNMLIB (RN) FILE = lename
FILE is the le name of the library to replace the current one. If the
le name is not fully qualied, it defaults to the current group and
account. If the le name does not exist, an error occurs.
To replace an existing NM library, enter the following command
format:
sysfile>RNMLIB lename.group.account
Replacing a system
program
The RSPROG command (abbreviated RS) replaces an existing system
program. RSPROG has the following parameters:
2
3
2
3
RSPROG (RS) PROG = programname FILE = lename
PROG species an existing program name. If the name entered does
not exist, an error occurs.
FILE species the le name to replace the specied system program.
If the le name is not fully qualied with group and account name, it
defaults to the current group and account. If the le name does not
exist, an error occurs.
Enter the command, an existing program name, and the fully
qualied le name to replace the system program:
sysfile>RSPROG programname.group.account lename.group.account
Use the SHOW command (SH SPROG) to display all the system
programs maintained by the conguration.
Caution
Do not use the SYSFILE> RSPROG command to rename
Hewlett-Packard supplied MPE/iX HP 3000 system les. A renamed
system le can corrupt your system during an update. This problem
can occur if you have third party software installed on your system
and you have renamed some system les to use this software.
Use the SHOW command in SYSFILE to ensure that all
Hewlett-Packard supplied system les have retained their original
name. System lenames in both columns should be identical. If
they are not identical, rename the les in the second column to the
lename in the rst column.
Modifying System File Configurations 8-17
Using a Segmented
Library File as CMSL
The CMSL command (abbreviated CM) species 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 qualied, it defaults to the current group and account. If an SL
name is not specied, the default is SL.PUB.SYS.
Enter the command and a fully qualied SL name to change the
default, SL.PUB.SYS, as shown in the following example.
sysfile>CMSL NEWSL.PUB.SYS
Listing CMSL
Contents
The LCMSL command (abbreviated LC) lists the contents of the CMSL
or a single segment in the CMSL. LCMSL has the following parameter:
2
3
LCMSL (LC) SEG = segmentname
The segment name designates which segment to list. If the segment
name is not specied, the entire contents of the CMSL is listed.
If SYSGEN cannot locate the segment name, an error is generated,
and the command is rejected by the segmenter.
To list the contents of a single segment, enter the command and the
segment name:
sysfile>LCMSL cminin
To list the entire CMSL, enter the command without a parameter.
Note
The LCMSL command locks whichever SL it is listing. If the CMSL
is SL.PUB.SYS, and no changes have been made (changes force a
temporary SL to be created), any program that uses the SL stops.
This can cause the system to appear to be down.
8-18 Modifying System File Configurations
Clearing SYSFILE
Configurator
Changes
If you desire to clear all SYSFILE conguration changes made, enter
the CLEAR command at the SYSFILE congurator 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 congurator commands described in the
previous sections changes the conguration specied in the SYSGEN
command line or global BASEGROUP command. These changes are
temporary and are lost if not properly saved.
Saving conguration changes is a two-step procedure. After you alter
a conguration, you must rst, hold the changes before exiting the
congurator. Second, use the global module KEEP command to save
the changes.
To hold changes, enter the HOLD command (abbreviated HO) at the
SYSFILE congurator prompt:
sysfile>HOLD
You can work in a SYSGEN congurator, hold the changes, and
continue working in another SYSGEN congurator before saving the
changes.
To save the changes, hold all desired changes, exit to SYSGEN's
global module, and issue the KEEP command (abbreviated KE or K):
sysgen>KEEP newgroupname
Entering an MPE
Command from the
SYSFILE
Configurator
Use the colon (:) to introduce an MPE command while in the
SYSFILE congurator. To issue an MPE command, enter the
command following the colon. For example:
sysfile>:SHOWTIME
THU, APR 20, 1989, 2:55PM
sysfile>
Modifying System File Configurations 8-19
Exiting the SYSFILE
Configurator
Use the EXIT command (abbreviated EX or E) to deactivate the
SYSFILE congurator and to return to the SYSGEN global module.
To exit the congurator, enter EXIT at the SYSFILE congurator
prompt:
sysfile>EXIT
sysgen>
8-20 Modifying System File Configurations
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
conguration, or for security reasons.
If done properly, a shutdown preserves all system and user les.
Before the shutdown occurs, backlogged reports can be printed, or
they can be saved to tape and replaced when the system is running
again.
The shutdown procedure usually consists of several steps, including
the following:
telling users well in advance of a planned shutdown
warning users a few minutes before the shutdown
preventing anyone from starting a new job or session, or printing
new reports
clearing the backlog of reports before the shutdown (This step
is unnecessary unless you need the space that these reports are
using.)
answering any console requests
shutting open communication lines
aborting remaining jobs and sessions
entering the =SHUTDOWN command
The next several sections describe procedures associated with
shutting down a system. Read through the remainder of this chapter
before attempting a shutdown based on these instructions. Become
familiar with the commands and options used in each process.
Examine the processes for areas that you may need to customize for
your system.
Halting System Activity 9-1
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.
When users log on to the computer, the message noties them
of the impending shutdown. They can then plan their schedules
accordingly.
Telling Users about
the Shutdown
Use the TELL command to alert users to the upcoming shutdown
approximately 15 minutes beforehand. Enter:
:TELL @S;Shutdown in 15 minutes.
Please log off.
This message reaches all active terminals, except those in quiet mode.
Limiting System Use
Use the LIMIT and JOBFENCE commands to prevent any new users
from logging on or any scheduled jobs from starting. Enter:
:LIMIT 0,0
:JOBFENCE 14
The command LIMIT 0,0 limits the number of concurrently running
jobs and sessions. The two parameters, in this case, 0,0, dene the
allowed number of jobs and sessions, respectively.
The command JOBFENCE 14 denes the minimum input priority that
a job or session must have to execute. The parameter 14 raises the
jobfence to the highest level.
9-2 Halting System Activity
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.)
or
:SHUTQ devname
(devname is the device name of the spooled device)
3. List the backlog of existing reports. Enter:
:LISTSPF
This lists all spool les. If the system responds NO SUCH FILE(S),
you have no spool les. Since output spool les are permanent
les, they will still be present when the system is restarted.
Warning Users Two
Minutes Before
Shutting Down the
System
The TELL command, mentioned in previous sections, does not send
its message to sessions in quiet mode. The WARN command, however,
sends its message to all sessions, including those in quiet mode.
Warn users two minutes before shutting down the system. Enter:
:WARN @S;SYSTEM SHUTDOWN IN 2 MINUTES.
LOG OFF.
Halting System Activity 9-3
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.
Shutting Down the
System
To shut down the system, enter:
4CTRL5 4A5
=SHUTDOWN
The following keywords can also be entered in the SHUTDOWN
command to document the shutdown:
SYSTEM
NETWORK
DTC
TERMINAL
TAPE
DISC
OTHER
You can use these options to indicate the reason that you are
shutting down the system. For example, if you shut down to clear a
dtc hang, use the DTC option.
4CTRL5 4A5
=SHUTDOWN DTC
The console responds by listing shutdown messages similar to these:
Shutdown
Shutdown
Shutdown
Spoolers
of operating system begins. (Shut 1)
of user processes begins (Shut 2)
of jobs & sessions begins. (Shut 3)
notified of a shutdown. (Shut 16)
.
.
.
Shutdown of system processes begins. (Shut 4)
Shutdown of system managers begins. (Shut 5)
Shutdown of operating system complete. (Shut 6)
9-4 Halting System Activity
A
Using the Access Port (AP)
This section describes the access port (AP) commands and provides
the procedures for enabling a remote console, for conguring a
system remote support modem port, and for performing the AP
self-test.
Configuring the
Console
Some of the terminal conguration parameters are important for
proper AP operation. Both terminals connected to ports T0 (system
console) and T1 (remote support modem port) should be congured
with the following parameter settings:
From the DATACOMM CONFIGURATION menu:
Parity/DataBits None/8
Chk Parity NO
EnqAck YES
CS(CB)Xmit NO
RecvPace Xon/Xoff
XmitPace NONE
From the TERMINAL CONFIGURATION menu:
LocalEcho OFF
SPOW(B) NO
Line/Page(D) LINE
ReturnDef 4Return5
(**necessary during control mode**)
Parameters not mentioned can be set to any value and do not aect
AP operation.
Note
The AP is designed to operate with the HP 700/92 terminal. There
have been no deliberate steps taken to preclude operation with
other terminals (for example, the AP does not check the terminal
identication and refuse to operate with anything else), but no other
terminals have been tested for proper operation. Use other terminals
at your own risk.
Using the Access Port (AP) A-1
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.
.
.
.
If the AP command parser does not recognize the two characters
entered as a command, the system displays an error message similar
to the following:
Illegal command, type HE for help.
Interpreting the
System Status Line
d
c
When in control mode, the AP displays the system status line across
the softkey labels of the system console. The system status line has
this format:
a
CODE: xxxx REMOTE:
A-2 Using the Access Port (AP)
< 1
> < 2
> < 3
> ACCESS FAULT:
yy
b
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 . Active indicates that a
remote console is currently being used. Inactive indicates
that a remote console is not currently being used.
3
May have one of two values: single or multiple . This
designates whether the AP allows a single attempt (single)
or multiple attempts (multiple ) to access the remote console.
yy
Displays the number of times someone tried to access the
remote console but failed to give the proper password.
The status line is updated with each change, such as when the
system cycles through its self-test.
Using the Access Port (AP) A-3
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
Congure 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.
ER
Enables access by a remote console.
ES
Enables display of system status line during console mode.
HE
Displays the help screen.
RS
Stops all processing, initiates SPU self-test, and loads
software from load device if enabled for autoboot.
SE
Transfers remote terminal from console/control mode to
session mode.
TA
Initiates access port self-test.
TC
Transfers processor execution to operating-system-specic
routine. Initiates a system soft reset.
TE
Sends messages (up to 80 characters) between local and
remote consoles.
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.
Enable access by a remote console terminal (disables session
access).
Enable display of system status line during console mode.
Display this screen.
Stop all processing, initiate SPU Self-Test, load software
from load device if enabled for autoboot.
Transfer remote terminal from console/control to session mode.
Initiate Access Port Self-Test.
Transfer processor execution to operating system specific routine.
Send message between local and remote console terminals.
In the preceding display, xxx is the number of the revision of the
operating rmware contained on the AP and m.d.y is the month, day
and year the rmware revision was released. These identications
are necessary to manage ROM updates in the eld if they become
necessary.
Returning from
Control Mode to
Console Mode
The access port command, CO, returns the console from control
mode to console mode. Once returned to console mode, the system
console operates in its normal session mode. This command does not
generate messages.
Using the Access Port (AP) A-5
Issuing the AP command, CA, allows either the local or remote
console operator to recongure the baud rate for the remote
support modem port, the setting of the T1 RATE line, and the
system identication. The AP accepts any conguration, making no
judgment on the validity.
Configuring the
Access Port
Using the CA command generates the following prompts:
CM>CA 4Return5
Current remote support modem port configuration:
Bit rate
Rate Select/CCITT 111
System identification:
9600 bits/sec
High rate (ON)
Joe's Sink and Pipe Shop
Do you wish to change the configuration? (Y/N): Y 4Return5
Enter your changes. <CR> retains the current value.
Current bit rate is 9600 bits/sec. Select the new bit rate.
(0=300, 1=1200, 2=2400, 3=4800, 4=9600): 4Return5
Rate Select (CCITT 111) is currently HIGH (ON). Choose the
new setting (H=high or ON, L=low or OFF): H 4Return5
Current System identification: Joe's Sink and Pipe Shop.
New identification (limited to 1 to 24 displayable characters
or space for none): Yi's Jug and Bottle Shop 4Return5
New configuration (takes effect at next remote connection):
Bit rate
Rate Select/CCITT 111
System identification:
9600 bits/sec
High rate (ON)
Yi's Jug and Bottle Shop
CM>
The baud rate for the remote console port can be set to 300, 1200,
2400, 4800, or 9600 bits per second. This should be equal to the
speed that is supported by your modem (usually 2400).
The remote console port rate can be turned on or o. ON is the high
voltage and OFF is the low voltage, within the denitions for control
lines for both RS-232c and V.28.
A-6 Using the Access Port (AP)
The system identication is a displayable character ASCII string (24
characters maximum) that is stored on the AP, for the AP's exclusive
use. The AP identication has absolutely nothing whatsoever to do
with any other system identication stored elsewhere in the SPU. No
other entity has access to it, and the AP has no access to any other
system identication.
Enter up to 24 characters as the system identication. Characters 00
hex through 1F hex are control characters and are not considered
displayable. Entering a space at the system identication prompt
deletes the previous identication string.
The new conguration is written to nonvolatile memory (NVM)
at the end of command processing. It is not used until the next
incoming call is answered and the conguration has been written to
NVM. If CA is executed by a remote user and the line is lost, the new
conguration is still not in eect and the remote user can redial and
pick up the process where the disconnection occurred.
For NVM failure, the conguration uses default parameters. These
values are 1200 bits per second, for the bit rate; rate select (CCITT
111) high; and system identication set to the null string.
If, during the conguration of the remote support modem, 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 "H" or "L" (APERR 12)
String was truncated to 24 characters. (APMSG 04)
Your selection is outside of the legal range.
(APERR 14)
Using the Access Port (AP) A-7
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.
Enabling Remote
Console Access
Using the ER command generates the following prompts:
CM>ER 4Return5
Current remote console access configuration:
Mode:
Password:
Password faults:
Multiple
The quick brown fox
10
Do you wish to change the configuration? (Y/N): Y 4Return5
Enter your changes. <CR> retains the current value.
Current mode:
Multiple
Select the new setting (S=single, M=multiple): 4Return5
Current password:
The quick brown fox
New password (1 to 24 displayable characters or space
if no password is to be required): 4Return5
Current password fault limit:
10
New number of password faults (Range: 0-99 or space.
Space or 0 will permit unlimited password faults.): 5 4Return5
New remote console access configuration:
Mode:
Password:
Password faults:
Multiple
The quick brown fox
5
Remote console access is now enabled.
CM>
The new access status settings do not take eect until you nally
answer the change query with NO.
A-8 Using the Access Port (AP)
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. (APERR 13)
Upon NVM failure, the following default values are used: remote
disabled, multiple access mode, maximum fault limit = 3, no
password required.
Sending Messages
to Both Consoles
The AP treats all displayable characters following the TE command
as a comment. They are displayed but not executed. This allows you
to enter a message of up to 80 characters at the master terminal that
can be viewed by both consoles. For example, entering:
CM>TE System backup begins in 5 minutes.
displays the message:
System backup begins in 5 minutes.
at the remote console.
Disabling Remote
Console Access
Entering DR disables remote access by the remote support modem
port to control and console modes.
If the command is successful, the system displays the message:
Remote console access disabled.
Note
The remote enabled light on the front panel goes out once remote
console access is terminated.
Using the Access Port (AP) A-9
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.
Connecting the
Remote Support
Modem to a Session
Port
This command is valid from the remote support modem port only.
Entering SE causes the remote support modem port to connect
through to a session port. If DTR is on, the remote support port's
modem remains connected. The remote support modem is able to
initiate a session using a normal connection protocol, as if a new
modem connection had just been established. To reenter control
mode, the remote support port modem must drop the connection and
redial.
Using this command and the port operation, a user at the Response
Center is able to use control, console, and session mode without any
intervention by the local operator. (The operator must enable remote
capability of the system.)
The following message is generated if the local console operator tries
to execute the SE command:
Command may not be executed by local user. (APERR 15)
Enabling the SPU
Hex Status Display
The ES command displays the system status line, including the front
panel LED codes, on console terminals during console mode. Console
terminal performance and software performance may be aected
when a remote console is connected to the system.
The operating system writes the LED display every 0.5 seconds.
For a 300-bit per second modem, 60 percent of the available
throughput is taken by the writing of the LED code. For a 1200-bit
per second modem, 15 percent of the line capacity is used.
A-10 Using the Access Port (AP)
To minimize the eect, 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.
Disabling the SPU
Hex Status Display
Entering DS disables the display of the system status line, including
the system front panel hex display codes on the console during
console mode. See the ES command for more details.
The system displays a message when the command is successful:
System status display during console mode is disabled.
Hard Resetting the
SPU
Note
Issuing the RS command causes the AP to reset the entire SPU,
halting all processing and I/O activity with the exception of itself
and a few operations that must maintain state even over resets.
The AP clears all data from the standard output (SO) and data
processing rst-in-rst-out (DP FIFO) buers. When the rst
character arrives from either buer, the AP returns the console from
control mode to console mode.
The AP command interpreter is active during the period between
command execution and the arrival of characters (on either buer
ports) from the system, though the control mode prompt (CM>) isn't
available.
Executing this command generates messages and prompts essential to
resetting the system.
Using the Access Port (AP) A-11
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).
The last three messages appear as a result of certain failures detected
by the AP during the reset process. These messages are key to
isolating the cause of the failure of the failed eld-replaceable unit.
Once the reset is complete, the system displays the following
message:
SPU hardware was successfully reset. (APMSG 02)
Transferring Control
(Soft Reset)
The TC command initiates a transfer of control, or soft reset, of the
system.
Should an error be encountered during a TC, the system displays
following error message:
Unable to verify assertion of TOC_SYS backplane signal
(APERR 04).
A-12 Using the Access Port (AP)
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. (APMSG 01)
If the self-test fails:
AP Self-Test failed subtest xx (APERR 05).
where xx is the number of the test causing the failure. If the self-test
hangs, the last number displayed is the failing subtest, provided that
the numbers have appeared in numerical order (which is the expected
sequence).
During the execution of self-test, some of the test numbers shown
above may have the mnemonics NC, NT1H, or NS1H appended to
them. Whether or not these appear depends upon the test hood
conguration present at the time of test execution.
Note
The master terminal after the completion of the self-test is the
terminal that was master when the test was initiated.
Using the Access Port (AP) A-13
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. The queues continue to accept
characters from the system. The XOFF is not passed to the system
port being used for the transfer.
Entering 4CTRL5 4Q5 causes the AP to resume passing characters from
its port queues to the consoles if this was previously stopped by
XOFF character. The XON is not passed to the system port being
used for the transfer.
The escape character 4CTRL5 4V5 nullies whatever character follows
it, except for XON and XOFF characters. Any character following a
4CTRL5 4V5 has no eect on AP operation.
Only one console can operate as the system console at a time. It is
referred to as the master. The other, usually the remote terminal,
can view data but cannot enter data until it takes control. 4Break5 is
used to take control back and forth between the system console and
an enabled remote console. When the remote console enters 4Break5, it
becomes the master console, and vice versa. In order to enter data at
the remote terminal, you must press 4Break5.
A-14 Using the Access Port (AP)
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.
Error Codes and Error
Messages
MESSAGE
Unable to verify assertion of RESET SYS backplane signal (APERR 01)
CAUSE
This message, displayed during execution of the RS command, means that the
backplane signal RESET_SYS- is not asserted when the AP attempts to reset the SPU.
This error might be caused by any one or a combination of four conditions.
Failure of the AP drive circuitry causes this error to be detected, and the SPU is not
reset.
The circuitry that permits the AP to read this line may have failed. If this is the
case, the error message is displayed, but the SPU is reset in the proper manner.
The CIO backplane may contain a short between the RESET_SYS- line and another
low impedance line that is driving a high-logic level.
Some other device connected to the RESET_SYS- line may be driving a high-logic
level that the AP cannot overdrive.
MESSAGE
RESET_SYS backplane signal asserted, but unable to verify SPU
deassertion of PPON backplane signal (APERR 02)
CAUSE
This message, generated during execution of the RS command, indicates that the
PPON backplane signal is not deasserted within 2 seconds after the RESET_SYS- line
is asserted.
This error may be caused by three conditions. If the receiver, which senses this state
of this line on the AP, has failed, the system displays the message. The SPU resets
normally. The AP also resets itself as soon as the RS command has completed, if this
is the cause of the failure.
If the wiring between the assembly that receives RESET_SYS- and the AP is
defective, neither the SPU nor AP resets.
If the portion of the power system that generates PPON is defective, the SPU does
not reset, and the AP probably does not reset.
MESSAGE
PPON not reasserted by SPU after RESET_SYS deassertion (APERR 03)
CAUSE
This message, displayed by the RS command, means that PPON has not reasserted
within 2 seconds after being deasserted. Once this occurs, the AP becomes
insensitive to being reset by the deassertion of PPON.
This error is most likely the result of a fault in the assembly that generates the
PPON signal.
Using the Access Port (AP) A-15
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.
Since idle self-test executes whenever the AP microprocessor has idle time, this
message may appear at any time, in any AP context, including during console mode
operation.
MESSAGE
AP failed subtest xx of prior idle Self-Test.
CAUSE
This message is displayed when a switch in modes is made after idle self-test has
failed previously.
MESSAGE
Permitted accesses to NVM
CAUSE
This message is displayed each time that the AP accesses NVM after the counter in
NVM indicates that the permitted number of accesses to the last block of NVM has
been exhausted. The AP should be replaced at the next visit by HP service
personnel. The NVM may survive for up to 20,000 more accesses after this message
begins to occur, or it may fail almost immediately.
MESSAGE
CRC error on NVM.
CAUSE
This message is displayed when the AP has exhausted the permitted number of
accesses to all blocks of NVM. The default settings for NVM parameters are used.
Notify your HP service personnel. The AP must be replaced.
MESSAGE
Illegal command, type HE for help. (APERR 10)
CAUSE
The rst two characters entered in a command line for the AP command interpreter
are not an AP command. Help displays all legal commands.
MESSAGE
Expecting "Y" or "N" (APERR 11)
CAUSE
The AP is expecting one of the letters Y or N, in either uppercase or lowercase, as
the reply to the query displayed on the screen.
MESSAGE
Expecting "H" or "L" (APERR 12)
CAUSE
The AP is expecting one of the letters H or L, in either uppercase or lowercase, as
the reply to the query displayed on the screen. H stands for high, and if chosen,
causes the specied signal to be set to the high voltage level, which is nominally +9
Volts referenced to ground. L stands for low, and if chosen, causes the specied signal
to be set to the low voltage level, which is nominally -9 volts referenced to ground.
A-16 Using the Access Port (AP)
exceeded.
(APERR 07)
(APERR 08)
(APERR 09)
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. (APERR 15)
CAUSE
This command is a valid AP command, but is intended for use from the remote
support modem port (port T1) only. No action has been taken.
MESSAGE
Expecting "S" or "M" (APERR 16)
CAUSE
The only permissible input at this time is the letter S for single or the letter M for
multiple. They may be entered either in uppercase or lowercase.
MESSAGE
Syntax error. (APERR 17)
CAUSE
Any error other than those covered by error messages APERR 18 and APERR 19
when using the DM, AM, DD, or AD commands, causes this error message.
MESSAGE
Illegal hexadecimal entry. (APERR 18)
CAUSE
If any of the hex parameters entered with the DM, AM, DD, or AD commands are not
valid hex numbers, this error message is be output.
MESSAGE
Illegal address or address range. (APERR 19)
CAUSE
Attempting to address outside the legal range of addresses with the DM, AM, DD, or AD
commands causes this error message to be given.
Using the Access Port (AP) A-17
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. (APMSG 02)
CAUSE
This message indicates that the AP did not enter the three possible error states. It
does not mean that the AP has somehow detected that the processor has restarted
or that it was cleared, for example. The AP has no way to determine the internal
state of any other assembly in the SPU.
MESSAGE
Console terminal not set to 9600 bits per second. Console port will
operate at xxxx bits per second. (APMSG 03)
CAUSE
The AP senses the setting of the console connected to local console port using
ENQ/ACK. The console should be operating at 9600 bits per second. If it is
operating at 4800, 2400, 1200, 600 or 300 bits per second, the AP senses this and
operates the port at this baud rate.
If the above message appears on the terminal screen, the AP and the terminal are
both set for the same baud rate. If the terminal is accidentally set for other than
9600, the above-referenced procedure should be followed to reset the terminal and
AP for 9600. If the terminal is set for 9600, the AP or the terminal is defective.
MESSAGE
String was truncated to 24 characters. (APMSG 04)
CAUSE
You can enter only up to 24 displayable characters in the answer to the query on the
screen. All characters past the twenty-fourth were discarded. No action is necessary
if the resulting truncated string is acceptable as the answer to the query. If the
resulting string is not acceptable, continue command execution until you are again
prompted for the string and enter the new string.
MESSAGE
AP configuration lost. Use CA and ER commands to recover. (APMSG 05)
CAUSE
If this message recurs after each reset, power on, or self-test execution, the AP is
defective.
A-18 Using the Access Port (AP)
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. This listing, similar
to the uninterrupted autoboot sequence shown in Chapter 2, halts at
the ISL prompt, waits for the user to enter the ISL START command,
and continues by listing the messages received until the operating
system is running.
Each of the other listings (UPDATE, INSTALL, and DUMP) begins at
the ISL prompt where the UPDATE, INSTALL, or DUMP command is
entered, and continues through the operation. Each listing ends at
the ISL prompt from the subsequent autoboot after each operation.
START Sequence
Refer to Chapter 3 for information on the steps involved in the
startup process. The following listing shows the Series 950 ISL START
(autoboot on) sequence received at the console. Sequences from other
installations may vary:
CM> TC
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.
Startup, Dump, and Shutdown Listings B-1
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.
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
(LDEV 1)
Initialize volume management completed.
Opening the native system library completed.
Initialize process management completed.
Initialize debug subsystem completed.
Initialize file system completed.
Initialize loader completed.
Initialize non-resident services completed.
Begin binding compatibility mode SL
Compatibility mode SL binding complete
Create port process has been completed.
Warning
- Protection of the system file `AUTOBOOT.MPEXL.SYS',
B-2 Startup, Dump, and Shutdown Listings
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.2 was configured but is not available.
The path 2/4.1 has already been configured.
The path 2/4.1.0 has already been configured.
The path 2/4.3.0 was configured but is not available.
The path 2/4.3.4 was configured but is not available.
The path 2/4.3.5 was configured but is not available.
The path 2/8.0.0 was configured but is not available.
The path 2/8.0.1 was configured but is not available.
The path 2/8.0.2 was configured but is not available.
The path 2/8.0.3 was configured but is not available.
The path 2/8.1.0 was configured but is not available.
The path 2/8.1.1 was configured but is not available.
The path 2/8.1.2 was configured but is not available.
The path 2/8.1.3 was configured but is not available.
The path 6/4.0.0 was configured but is not available.
The path 6/4.0.1 was configured but is not available.
The path 6/4.0.2 was configured but is not available.
The path 6/4.3.4 was configured but is not available.
The path 6/4.3.5 was configured but is not available.
The path 6/4.3.7 was configured but is not available.
Leaving - System I/O configuration.
Startup, Dump, and Shutdown Listings B-3
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
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
available
available
not-available
available
available
not-available
not-available
not-available
available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
not-available
MEMORY AVAILABLE FOR USE (bytes)
2/4.0.0
2/4.0.1
2/4.0.2
6/4.3.6
6/4.3.0
2/4.3.0
6/4.3.7
6/4.3.4
2/4.1.0
6/4.0.0
6/4.0.1
6/4.0.2
2/8.0.0
2/8.0.1
2/8.0.2
2/8.0.3
6/4.3.5
2/4.3.4
2/8.1.0
2/8.1.1
2/8.1.2
2/8.1.3
2/4.3.5
: 33554432
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
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Leaving - Mount
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
Volume is not
all volumes
B-4 Startup, Dump, and Shutdown Listings
available
available
available
available
available
available
available
available
available
available
available
available
for
for
for
for
for
for
for
for
for
for
for
for
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
mounting.
The
The
The
The
The
The
The
The
The
The
The
The
ldev
ldev
ldev
ldev
ldev
ldev
ldev
ldev
ldev
ldev
ldev
ldev
is
is
is
is
is
is
is
is
is
is
is
is
3
25
26
27
28
31
32
33
34
21
22
23
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.
SYSTEM LOG FILE #1 IS ON
Initializing Job & Session
Initiate Operator Log On
SESSION Scheduling Initialized
JOB Scheduling Initialized
Successfully launched diagnostic monitor process.
ACCT EXISTS, USER NAME DOESN'T. (CIERR 1438)
16:31/24/MISSING USER NAME DURING LOGON ON LDEV #20. (js 11)
MPE XL:
Startup, Dump, and Shutdown Listings B-5
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.
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.
** 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.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
ISL> DUMP
B-6 Startup, Dump, and Shutdown Listings
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.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.
density set at 6250 BPI on tape drive
tape is ready
Begin dump of Processor Internal Memory.
Processor Internal Memory dump complete.
Begin dump of main memory.
32 Megabytes of main memory will be dumped
................
Dump of memory save area complete.
................
Main memory dump complete.
Begin dump of secondary storage for ldev1
52 Megabytes of transient objects will be dumped for this device
....................................................
Secondary storage dump for ldev1 complete.
Begin dump of secondary storage for ldev2
7 Megabytes of transient objects will be dumped for this device
....
Secondary storage dump for ldev2 complete.
Dump completed - autoboot in progress.
Startup, Dump, and Shutdown Listings B-7
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.90
DUMPAREA protected, proceeding to ISL without memsave
ISL loaded
ISL Revision 2738 September, 1987
Cannot find an auto-execute file. AUTOBOOT ABORTED.
ISL>
B-8 Startup, Dump, and Shutdown Listings
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.
:LIMIT 0,0
:JOBFENCE 14
:SHOWOUT SP
NO SUCH FILE(S)
:WARN @S;SYSTEM SHUTDOWN IN 2 MINUTES.
:SHOWJOB JOB=@S
JOBNUM
#S669
STATE IPRI JIN
EXEC
20
JLIST
20
PLEASE LOG OFF.
INTRODUCED JOB NAME
WED 8:22A OPERATOR.SYS
1 JOBS (DISPLAYED)
0 INTRO
0 WAIT; INCL 0 DEFERRED
1 EXEC; INCL 1 SESSIONS
0 SUSP
JOBFENCE= 14; JLIMIT=0; SLIMIT=0
:WARN @S;SYSTEM SHUTDOWN IN 1 MINUTE. ALL USERS WILL&
BE LOGGED OFF AT THAT TIME.
:4CTRL5 4A5
=SHUTDOWN
Shutdown of operating system begins. (Shut 1)
Shutdown of user processes begins (Shut 2)
Shutdown of jobs and sessions begins. (Shut 3)
Spoolers notified of a shutdown. (Shut 16)
Shutdown of system processes begins. (Shut 4)
Shutdown of system managers begins (Shut 5)
Shutdown of operating system complete. (Shut 6)
Startup, Dump, and Shutdown Listings B-9
C
Reading Stable Storage and Nonvolatile Memory
Certain types of system errors and failures may indicate problems
with the stable storage or nonvolatile memory (NVM). In these cases,
your HP customer engineer may request that you note the contents
of certain locations in these storages. ISL provides two commands,
READSS and READNVM, that read the contents of storage addresses in
stable storage and nonvolatile memory (NVM).
Reading Stable
Storage Contents
Stable storage contains the boot path information along with
other critical le system parameters in a minimum area of 96
bytes of high-reliability memory. The storage maintains the
critical parameters even if the storage card is removed from the
backplane. After the initial memory controller is initialized, the
processor-dependent code (PDC) accesses stable storage to determine
the boot device and console selection process.
Reading Stable Storage and Nonvolatile Memory C-1
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.
The console path and alternate paths are stored in the same format
as the primary boot path. Unlike the primary boot path, the rst
byte of the rst word of the console and alternate boot paths is set to
hex 00. The autoboot and autosearch ags are not stored with these
paths.
C-2 Reading Stable Storage and Nonvolatile Memory
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.
NVM contains initialization information in a 92-byte block starting
at decimal byte address 36. NVM stores this information as shown in
gure C-2.
Reading Stable Storage and Nonvolatile Memory C-3
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.
ISL> READNVM 68
Address 68 contains 0x32363334
*** ISL Revision 2738 ***
The TIMESTAMP is in seconds since 1/1/70.
C-4 Reading Stable Storage and Nonvolatile Memory
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.
ISL> READNVM 124
Address 124 contains 0x030600AC
(The last six digits vary)
The rst two digits, 03, indicate that the pointer is positioned to the
third utility name location (decimal address 92) in the queue.
Read location 92 to nd the hexadecimal representation of the name:
ISL> READNVM 92
Address 92 contains 0x53544152
(53=S 54=T 41=A 52=R which spells out STAR)
Since each location is limited to four characters, additional characters
are located in the next word:
ISL> READNVM 96
Address 96 contains 0x54202020
(54=T 20=Blank which adds the last T for start)
Table C-1 lists the ISL utility names and the hexadecimal
representation for both uppercase and lowercase spellings.
Table C-1. Codes for ISL Utility Names.
Utility
Uppercase
Lowercase
START
53 54 41 52 54
73 74 61 72 74
UPDATE
55 50 44 41 54 45
75 70 64 61 74 65
INSTALL
49 4E 53 54 41 4C
4C
69 6E 73 73 61 6C
6C
DUMP
44 55 4D 50
64 75 6D 70
Reading Stable Storage and Nonvolatile Memory C-5
D
Default Configurations Used by INSTALL and UPDATE
The INSTALL utility on a factory system load tape replaces a
system's conguration les with a default conguration. These
defaults allow the system manager or system supervisor to boot
the system to a fully operational level. You should then alter
the functioning conguration to meet your system's needs using
SYSGEN.
START uses CONFIG as its default conguration group. Before a
system can actually use the START command default to start the
system, however, a functioning set of conguration les must reside
in the conguration group CONFIG.
Since multiple conguration groups reside on a factory system load
tape, CONFIG is empty on disk after an INSTALL until the system
manager copies an appropriate conguration group into it using
SYSGEN. The following is a list of appropriate conguration groups
depending upon which 900 Series system you are working with.
The next sections show portions of the default input and output
(I/O) congurations carried by:
Default Configurations Used by INSTALL and UPDATE D-1
Table D-1. Default Configurations for the 900 Series
GROUP NAME
SYSTEM DESCRIPTION
CARDS
CONF9X71
9X7 with 1 disk drive
SCSI
CONF9X72
9X7 with 2 disk drives
SCSI
CONF9X73
9X7 with 3 disk drives
SCSI
CONF9X74
9X7 with 4 disk drives
SCSI
CONF9X75
9X7 with 3 disk drives
2 DDS devices
SCSI
CONFG9X8
9X8LX or 9X8RX
SCSI
CONFG920
920
HP-IB
CONFG922
922 or 922LX or 922RX
HP-IB
CONFG925
925 or 925LX
HP-IB
CONFE925
925 with CIO expander bay
HP-IB
ALINK925
925 or 925LX
HP-FL
ALINE925
925 with CIO expander bay
CONFG932
932
HP-IB
ALINK932
932
HP-FL & HB-IB
CONFG935
935 with CIO expander bay
HP-IB
ALINK935
935 with CIO expander bay
HP-FL and HB-IB
CONFG948
948
HP-IB
ALINK948
948
HP-FL and HP-IB
CONFG949
949 with CIO expander bay
HP-IB
ALINK949
949 with CIO expander bay
HP-FL and HB-IB
CONFG950
950
HP-IB
ALINK950
950
HP-FL and HP-IB
CONFG955
955
HP-IB
ALINK955
955
HP-FL and HP-IB
CONFG958
958
HPIB
ALINK958
958
HP-FL and HP-IB
CONFG960
960
HP-IB
CONFSCS0
960
SCSI
ALINK960
960
HP-FL and HP-IB
CONFG980
980
HP-IB
ALINK980
980
HP-FL and HP-IB
D-2 Default Configurations Used by INSTALL and UPDATE
HP-FL and HB-IB
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.
For specic information on how to start the system with the default
conguration les, as well as possible additional default conguration
les, refer to the HP 3000 MPE/iX Installation, Update, and Add-On
Manual (36123-90001).
The conguration groups for the Series 935, CONFG935 and ALINK935,
apply only to systems with a CIO expander. If you are working on a
system without a CIO expander, you must modify the conguration
group using SYSGEN so that device entries match the system
conguration.
Copying Default
Configuration File
This section discusses renaming the default conguration les groups
used by the UPDATE and INSTALL utilities mentioned in Chapter 3.
Groups
Overview
The INSTALL utility replaces a system's conguration les with a
default conguration. These defaults allow the system manager or
system operator to boot the system to a fully operational level. They
may then alter the functioning conguration to meet their system's
needs.
The UPDATE utility optionally replaces a system's conguration les
with defaults. During an update, the system manager or system
operator has the choice of whether or not to use a conguration
stored on the system volume or to replace the current conguration
with the default.
Default Configurations Used by INSTALL and UPDATE D-3
Before a system can properly use its START command, a functioning
set of conguration les must reside in the conguration group
CONFIG. The START command uses CONFIG as its default conguration
group.
Since multiple conguration groups reside on a system load tape
(SLT), CONFIG is empty until the system manager copies an
appropriate conguration group into it.
Using SYSGEN to
Copy the Files
You must use SYSGEN to copy conguration groups. Using other
methods to copy conguration les removes key elements and
corrupts the les.
To copy a default conguration group into the conguration group
CONFIG, follow the instructions outlined below:
1. Activate SYSGEN.
d
Entering SYSGEN activates SYSGEN's global module.
:SYSGEN
a
SYSGEN version B.06.01 : catalog version B.06.02 FRI, MAY 20, 1988
Copyright 1987 Hewlett-Packard Co. All Rights Reserved
** First level command **
c
sysgen>
io
sysfile (sy)
log (lo)
misc (mi)
spu (sp)
basegroup (ba)
tape (ta)
keep (ke)
permyes (pe)
show (sh)
clear (cl)(c)
redo
exit (ex)(e)
help (he)(h)
oclose (oc)
b
2. Specify the base group on which to operate.
Specify the group that more closely matches your system. Enter:
sysgen>BASEGROUP basegroupname
3. Modify the conguration if necessary.
If your system requires a conguration other than that provided
by default, use the IO congurator to modify the current base
group to meet your system's requirements. Refer to the chapter
in this manual, that discusses the types of changes that you must
D-4 Default Configurations Used by INSTALL and UPDATE
make. After making any changes, hold them (issue the HOLD
command in each congurator used to make changes), and return
to SYSGEN's global module.
4. Save the conguration to disk as CONFIG.
After you have completed making changes, if any, save the
conguration to the CONFIG group. Enter:
sysgen>KEEP CONFIG
Default Configurations Used by INSTALL and UPDATE D-5
5. Generate a system load tape (SLT) if desired.
To create an SLT that contains the new conguration, use CONFIG
as the base group, and save it to tape, as discussed in Chapter 3.
6. Use the new conguration and restart the system.
If you modied the conguration 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. The system responds by listing shutdown messages:
Shutdown
Shutdown
Shutdown
Spoolers
Shutdown
Shutdown
Shutdown
of operating system begins. (Shut 1)
of user processes begins. (Shut 2)
of jobs & sessions begins. (Shut 3)
notified of a shutdown. (Shut 16)
of system processes begins. (Shut 4)
system manager begins. (Shut 5)
of operating system complete. (Shut 6)
a
b
8. Reset the system using RS or TC. Restart it by specifying
NORECOVERY.
ISL> START NORECOVERY
9. Prepare the system for normal production.
You may wish to check certain items to ensure that the system is
ready for production. These items can include:
jobfence parameters
limit parameters
LAN status
D-6 Default Configurations Used by INSTALL and UPDATE
E
Verifying Attached Devices
This section discusses using the initial system loader's IOMAP or ODE
utility to verify which devices are attached and congured to a
900 Series HP 3000 computer system.
Overview
SYSGEN provides utilities for listing the congured 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
congured path does not require an associated device.) The initial
system loader (ISL) provides the ODE utility for 9X8LX and 9X8RX
systems and for other systems the IOMAP utility for locating the
devices attached to a system.
A list of attached peripherals aids the system manager in assessing
a system's needs, deciding where (on which I/O paths) to add
or remove peripheral devices, resolving I/O path conicts (as
with SYSGEN and NMMGR), and restoring or copying a system's
conguration.
Displaying
Configured Devices
ODE and IOMAP are utilities that are located in the ISL boot directory
of a 900 Series HP 3000 computer system. They can be launched
only from ISL, which indicates that the system is down. You must
run ODE on 9X8LX and 9X8RX systems. You can run IOMAP on all
other systems.
Verifying Attached Devices E-1
When running with default options, IOMAP and ODE running
MAPPER perform the following operations:
displays the current conguration of the processor, including the
presence of coprocessor boards, analyzer cards, memory sizes of
cache and translation look-aside buer (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 identies every component (such as a module, bus
converter, adapter, device, or unit)
displays a table showing all congured components
performs self-test and/or loopback tests on all components with
self-test and/or loopback capabilities
does not test any devices (terminals, data communication lines, or
other serial devices) connected to external ports of the terminal
multiplexer
The test modes of IOMAP include identify-test, loopback test, and
self-test. Identify-test attempts to identify each component in every
I/O path or specied path. The information received includes
I/O path to the component, component name, component ID
number, rmware revision (if applicable), hardware revision (if
applicable), and an indication of which test modes are available for
the component.
The loopback test performs component-dependent loopback tests
where feasible. The result of this test is reported as pass, fail,
unimplemented, or untestable.
The self-test initiates the internal self-test of each component that
has a self-test routine. The result of this test is reported as pass, fail,
unimplemented, or untestable.
E-2 Verifying Attached Devices
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. 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. PLEASE LOG OFF.
Verifying Attached Devices E-3
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 dene the
allowed number of jobs and sessions, respectively.
The command JOBFENCE denes 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. Use the WARN command to alert all sessions
(including those in quiet mode) to the shutdown. Enter:
:WARN @S; SYSTEM LOSS IN 5 MIN. PLEASE LOG OFF.
e. Locate all jobs and sessions still in progress or scheduled.
Enter:
:SHOWJOB JOB=@J
:SHOWJOB JOB=@S
The command SHOWJOB displays the status information about
jobs or sessions.
f. Abort jobs and sessions still executing. Enter:
:ABORTJOB #Jnnn (#Jnnn is the number for each job)
:ABORTJOB #Snnn (#Snnn is the number for each session)
2. Reset the system. Enter:
:4CTRL5 4A5
=SHUTDOWN
3. Once the system issues the nal shutdown message:
Shutdown of operating system complete. (Shut 6)
Enter:
:4CTRL5 4B5
CM> RS
Reset messages appear at the console while the system runs its
self-test.
If autoboot is enabled on your system, interrupt it so that you
receive the ISL prompt (ISL>). Refer to Chapter 3 for information
on interrupting an autoboot sequence.
E-4 Verifying Attached Devices
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.
If loopback test is selected, be sure the loopback test hood is plugged
onto HPPB GPIO card, so that external loopback on the card is possible.
If sefltest or loopback test is selected for a LAN card, be sure the
T-connector is plugged onto the card. If selftest is selected for a
device with removable media, make sure that is media in the device.
You may enter break mode by pressing control-C or control-Y.
You may press control-X to erase what you just typed in.
.
.
.
Do you wish to modify any program parameters? [y,n] (n): N
c
Identify: Loop 1: All I/O components are being identified...
.
.
.
b
Verifying Attached Devices E-5
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.3
7978A/B mag tape unit
8
Memory Controller
12
Memory Controller
16
Memory Controller
Identify Loop 1 (1H) complete.
Type HW SW Revisions Tests
ID
Mod Mod Hdwr Firm Avail
---- ---- ---- ---- ---- ----0H
8H
4H 10H
0
0
2H
6 2733 ST LB
214H
214H
214H
214H
214H
6H
6H
2H
250H
180H
2H
178H
1H
1H
1H
2H
2H
2H
8H
8H
8H
3
2
6
0
6
4
4
4
2716
2716
2733
2733
0
0
0
ST
ST
ST LB
ST LB
LB
LB
LB
Do you want to exit this program and return to ISL? [y,n] (n): Y
IOMAP Exiting.
c
Example E-1. Example of IOMAP
b
This IOMAP is from a Series 925 system. The paths and other
information may vary, depending on the system and conguration.
Exiting IOMAP
After running IOMAP a prompt appears at the end of the listing:
Do you want to exit this program and return to ISL?
Answer YES to this question to exit IOMAP. Answering NO returns you
to the following prompt:
Do you wish to modify any program parameters?
E-6 Verifying Attached Devices
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. PLEASE LOG OFF.
Verifying Attached Devices E-7
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 dene the
allowed number of jobs and sessions, respectively.
The command JOBFENCE denes 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. Use the WARN command to alert all sessions
(including those in quiet mode) to the shutdown. Enter:
:WARN @S; SYSTEM LOSS IN 5 MIN. PLEASE LOG OFF.
e. Locate all jobs and sessions still in progress or scheduled.
Enter:
:SHOWJOB JOB=@J
:SHOWJOB JOB=@S
The command SHOWJOB displays the status information about
jobs or sessions.
f. Abort jobs and sessions still executing. Enter:
:ABORTJOB #Jnnn (#Jnnn is the number for each job)
:ABORTJOB #Snnn (#Snnn is the number for each session)
2. Reset the system. Enter:
:4CTRL5 4A5
=SHUTDOWN
3. Once the system issues the nal shutdown message:
Shutdown of operating system complete. (Shut 6)
Enter:
:4CTRL5 4B5
CM> SP
Reset messages appear at the console while the system runs its
self-test.
If autoboot is enabled on your system, interrupt it so that you
receive the ISL prompt (ISL>). Refer to Chapter 3 for information
on interrupting an autoboot sequence.
E-8 Verifying Attached Devices
4. Type the following to run ODE:
ISL>ODE
5. Initiate the MAPPER module:
ISL>RUN MAPPER
MAPPER displays the current conguration using the same
format as IOMAP (see example E-1 for an example display).
Exiting MAPPER
To exit MAPPER type:
CM> EXIT
Exiting ODE
To exit ODE type:
CM> EXIT
Verifying Attached Devices E-9
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 dene a
pathway, consisting of various interface components, from the system
to the device. Each pathway component, and the device itself, is
dened (or congured) by specifying the IO Congurator APATH
or ADEV command, the component's address, and the component's
identier.
This section also provides a procedure for conguring additional
other devices.
For additional information on the commands used in these
procedures, refer to Chapter 5.
Note
Series 917LX
through Series 977
Systems
The examples in this section refer to an assortment of identiers for
devices, device adapters, channel adapters and, in the case of Series
950 through 980 systems, bus converters. The specic identiers
that you would use in conguring your system depend on your
specic hardware. For more information refer to the documentation
shipped with your hardware or contact your Hewlett-Packard support
representative.
HP-FL and SCSI devices are supported on these systems. The
rst two conguration steps are the same for both devices. A third
step is not required for single-unit HP-FL devices but is required
for multi-unit HP-FL devices. The third step is required for SCSI
devices regardless of whether or not the device is multi-unit.
Adding Peripherals to a System F-1
HP-FL/SCSI Devices
The rst two conguration levels consist of the device adapter
address and the device address.
To congure a device adapter with a path of 48, for example, enter:
APATH 48,ID=nnnnn
Where nnnnn is a valid device adapter identier such as HP28616A
or HP28642A-SCSI.
HP-FL Devices
To congure 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 identier such as HP7937FL or HPC2474R.
If you are conguring an HP-FL device that is not a multi-unit
device, you are done.
SCSI Devices
For a SCSI device you must use the word PSEUDO as the device
identier 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. It is required for HP-FL devices only when they are
congured as multi-unit devices.
To congure a unit address of 3, for example, on the disk drive
congured above, enter:
ADEV 48.2.3,ID=nnnnn
where nnnnn is a valid device identier.
If the device is not a multi-unit device or if a multi-unit device is
being congured as a single unit, the device unit address of 0 is used
to complete the address. For example, to use the device congured
above as a single-unit device, enter the following:
ADEV 48.2.0,ID=nnnnn
where nnnnn is a valid device identier.
F-2 Adding Peripherals to a System
Series 920, 922, 932,
948, 958, 925, 935,
949 CIO Systems
Note
Channel Adapter
You can congure 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. For
example, to congure a channel adapter number of 4 you would
enter:
APATH 4,ID=nnnnn
where nnnnn is a channel adapter module identier such as
HP19744A, HPA1101A or HPA1741A.
Device Adapter
To congure a device adapter (with an address of 3 for example) to
the channel adapter module enter:
APATH PATH 4.3,ID=nnnn
where nnnnn is a device adapter identier such as HP27113A,
HP28616A or HP28642A.
HP-FL/HP-IB Devices
To congure a device (with an address of 1 for example) to the
device adapter:
ADEV PATH 4.3.1,ID=nnnnn
where nnnnn is a device identier such as HP7957A HP7937FL or
HPC2474R.
Note
SCSI Devices
For reasons relating to backward compatibility, optical disk library
(SCSI device) conguration for CIO does not utilize the following
PSEUDO device identier. Instead, optical disk libraries are congured
with a valid device identier similar to HP-FL and HP-IB devices.
For more information refer to the installation documentation for the
device.
For a SCSI interface you must use the word PSEUDO as the device
identier as follows:
PATH 4.3.1,ID=PSEUDO
Adding Peripherals to a System F-3
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 congured as multi-unit devices.
To congure a unit address of 3, for example, on the device
congured above, enter:
ADEV 4.3.1.3,ID=nnnnn
where nnnnn is a valid device identier.
If the device is not a multi-unit device or if a multi-unit device is
being congured as a single unit, the device unit address of 0 is used
to complete the address. For example, to use the device congured
above as a single-unit device, enter the following:
ADEV 4.3.1.0,ID=nnnnn
where nnnnn is a valid device identier.
Note
Series 920, 922, 932,
948, 958 NIO
Systems
Device Adapter
An expander bay is available for conguring additional devices on
series 925, 935, 949.
These machines support both CIO and NIO. This section deals with
NIO conguration.
The rst two conguration levels consist of the device adapter
address and the device address. A third level is required for SCSI
devices or multi-unit HP-FL devices.
To congure a device adapter with a path of 48, for example, enter:
APATH 48,ID=nnnnn
Where nnnnn is a valid device adapter identier such as HP28616A
or HP28642A-SCSI.
HP-FL Devices
To congure an HP-FL 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 identier such as HP7937FL or HPC2474R.
If you are conguring an HP-FL device that is not a multi-unit
device, you are done.
F-4 Adding Peripherals to a System
SCSI Devices
For a SCSI interface you must use the word PSEUDO as the device
identier 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 congure a unit address of 3, for example, on the device
congured above, enter:
ADEV 48.2.3,ID=nnnnn
where nnnnn is a valid device identier.
If the device is not a multi-unit device or if a multi-unit device is
being congured as a single unit, the device unit address of 0 is used
to complete the address. For example, to use the device congured
above as a single-unit device, enter the following:
ADEV 48.2.0,ID=nnnnn
where nnnnn is a valid device identier.
Series 950 Through
Series 980 Systems
Bus Converter
These systems require a four or ve-level address consisting of the
bus converter number, the channel adapter module number (interface
slot number), the device adapter number the device address, and
possibly a unit address. HP-FL, HP-IB and some SCSI devices are
supported.
To congure a bus converter number of 6:
APATH 6,ID=nnnnn
where nnnnn is a bus converter identier such as HPA1105A.
Channel Adapter
To congure a channel adapter module number of 4:
APATH 6/4,ID=nnnnn
where nnnnn is a channel adapter module identier such as
HP19744A.
Adding Peripherals to a System F-5
Device Adapter
To congure a device adapter with an address of 3 to the channel
adapter module identier:
ADEV PATH 6/4.3,ID=nnnnn
where nnnnn is a device adapter identier such as HP28616A.
HP-FL/HP-IB Devices
To congure a device with an address of 1 to the device adapter:
ADEV PATH 6/4.3.1,ID=nnnnn
where nnnnn is a device identier such as HP7937FL or HP7937H.
Note
SCSI Devices
For reasons relating to backward compatibility, optical disk library
(SCSI device) conguration for CIO does not utilize the following
PSEUDO device identier. Instead, optical disk libraries are congured
with a valid device identier similar to HP-FL and HP-IB devices.
For more information refer to the installation documentation for the
device.
For a SCSI device you must use the word PSEUDO as the identier:
PATH 6/4.3.1,ID=PSEUDO
Unit Identifier
The fth-level provides the unit address for multi-unit devices (such
as the Magneto Optical Device or a Cascade Disk Drive). It is
required for SCSI devices regardless of whether they are single or
multi-unit. It is required for HP-FL devices only when they are
congured as multi-unit devices.
To congure a unit address of 3, for example, on the device
congured above, enter:
ADEV 6/4.3.1.3,ID=nnnnn
where nnnnn is a valid device identier.
If the device is not a multi-unit device or if a multi-unit device is
being congured as a single unit, the device unit address of 0 is used
to complete the address. For example, to use the device congured
above as a single-unit device, enter the following:
ADEV 6/4.3.1.0,ID=nnnnn
where nnnnn is a valid device identier.
F-6 Adding Peripherals to a System
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
specic 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 reconguration to accommodate
HP-FL cards. The reconguration requires the primary, secondary,
and alternate boot paths to change also. Systems that are initially
congured to accommodate HP-FL cards may not require signicant
modication to accept additional HP-FL cards.
The instructions for conguring HP-IB devices may provide
assistance when used for HP-FL devices, but you must modify the
instructions and examples to t your particular HP-FL installation.
Appendix D lists the default congurations provided for use with
HP-FL systems.
Contact your HP representative before attempting to use HP-FL
cards in your system.
Adding Peripherals to a System F-7
Adding a Peripheral
to Any System
d
Adding a disk drive, tape drive, or printer to a system's conguration
includes the following steps:
enter SYSGEN
view the system's current conguration
activate the IO congurator
make the necessary I/O conguration changes
hold the changes
save the changes
verify the accuracy of the new conguration
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.02
a
FRI, May 20,
** First level command **
c
io
sysfile (sy)
log (lo)
misc (mi)
spu (sp)
basegroup (ba)
tape (ta)
keep (ke)
permyes (pe)
show (sh)
clear (lc)(c)
redo
exit (ex)(e)
help (he)(h)
oclose (oc)
sysgen>
b
2. Select the base group to modify.
If you desire to modify the default conguration groups, copy the
groups to other group names and modify the copies using the IO
congurator. Copying the groups preserves uncorrupted versions
of the default or current congurations.
To copy conguration groups, use the BASEGROUP command to
activate the desired conguration group. Use the KEEP command
to save the group of les to another group name. Refer to
Chapter 4 for more information on using the BASEGROUP and
KEEP commands.
F-8 Adding Peripherals to a System
After deciding which copied conguration group to modify, use
the global module BASEGROUP command to activate the group:
sysgen>BASEGROUP groupname
Use the I/O conguration contained in CONFG935 as an example
conguration for this exercise.
3. Activate the IO congurator.
d
Enter the global module command, IO, at the SYSGEN prompt
to activate the IO congurator:
sysgen>IO
a
** IO configurator commands **
c
aclass (ac)
dclass (dc)
lclass (lc)
maddress(ma)
mvol (mv)
adev (ad)
ddev (dd)
ldev (ld)
mclass (mc)
apath (ap)
dpath (dp)
lpath (lp)
mdev (md)
avol (av)
dvol (dv)
lvol (lv)
mpath (mp)
clear (cl)(c)
oclose (oc)
io>
exit (ex)(e)
redo
help (he)(h)
hold (ho)
b
4. Obtain I/O conguration listings.
Enter LCLASS, LDEV, and LPATH, at the IO congurator prompt to
get current I/O conguration listings:
io>LCLASS DEST=OFFLINE
io>LDEV DEST=OFFLINE
io>LPATH DEST=OFFLINE
io>OCLOSE
The OCLOSE command closes SYSGEN's listing le, SYSGLIST,
and prints the information in the le.
Refer to Chapter 5 for more information on using the LCLASS,
LDEV, LPATH, and OCLOSE commands.
5. Decide on which LDEV to add the drive.
View the LDEV command output. Choose any unused LDEV and
consider assigning it to the disk drive. For this example, use
LDEV 4.
Adding Peripherals to a System F-9
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 conguration 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. Class names may
not exceed eight characters and must begin with an alphabetic
character.
7. Add the path.
Since you are adding the drive to a newly installed HP-IB card,
you must dene the path down to the device adapter level. Use
the APATH command to dene the path.
For example, add the drive to a newly installed HP-IB card
(ID number, HP27113A). The HP Service Representative who
installed the card placed it in the CIO expander (CA 36) on
channel adapter 2, and device adapter slot 2. Enter:
io>APATH 36.2 HP27113A
Refer to Chapter 5 for additional information on using the APATH
command.
8. Add the device.
Use the ADEV command to add the device, including the device
address, to the path specied with the APATH command. Enter:
io>ADEV LDEV=4 PATH=36.2.0 ID=HP7937H CLASS=DISC
Refer to Chapter 5 for additional information on using the ADEV
command.
9. Hold all changes.
Enter the IO congurator HOLD command at the IO congurator
prompt:
io>HOLD
Refer to Chapter 5 for additional information on using the HOLD
command.
F-10 Adding Peripherals to a System
10. Exit the IO congurator.
Enter the EXIT command at the IO congurator 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 modied
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. Enter:
sysgen>TAPE
The system may place a tape request similar to the following:
?11:10/#S1/46/LDEV# FOR "SYSGTAPE" ON TAPE (NUM)?
If this message appears, respond:
4CTRL5
A
=REPLY pin,7
where pin is the PIN (in this instance 46) from the third location
in the tape request.
After all the les are stored, unload the tape, and write protect
it. Label the tape, and store it, in a secure location, with any
other backup materials.
13. Exit SYSGEN and reboot the system.
sysgen>EXIT
Note
Any disk device smaller than 400 Mbytes should not be installed as
the system disk (LDEV 1). A disk this size or smaller is too small
to run the operating system and its subsystems. A 400-Mbyte or
smaller disk, however, can be used as any other LDEV.
Adding Peripherals to a System F-11
In this procedure, the system manager chains (congures) a tape
drive to another congured device, (commonly referred to as a host
device). The host device doesn't have to be physically attached to
the system to congure the tape drive but when the tape drive is
connected, the host device must be present.
F-12 Adding Peripherals to a System
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.
Furthermore, they have been designed to appear similar to the
battery backup method which minimizes their eect on system
operation and management procedures.
UPS devices oer two principal advantages over the battery backup
method:
In a minimal UPS-based system, the degree of power failure
protection is equivalent to that provided by the battery backup
unit. You can, however, add more UPS devices to the system and
provide reserve power to selected peripherals. Depending upon
how much of the system is provided with UPS power, it can run a
partial or full workload non-stop through limited periods of AC
power failure.
The UPS contains a serial I/O communications interface that, in
conjunction with UPS Monitor/iX software, noties the system
operator of any problems. Like the battery backup hardware that
the UPS devices replace, a system-wide power failure recovery
message is broadcast to all active user terminals and to the console
upon the return of power following a failure. In addition to console
messages, the UPS Monitor/iX software also posts a variety of
status and warning messages to the system log les which you can
review and analyze to evaluate system performance.
UPS and UPS Monitor/iX Software G-1
Configuring a UPS
device
You can use one of two conguration 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 precongured in the default
conguration group supplied with the FOS tape. You perform this
procedure once, immediately after you install a new system. For
additional UPS devices, which are attached to a DTC serial I/O
port, you use NMMGR to supply all of the information necessary to
congure the device(s). (As the nal step in this second method, you
will cross-validate the conguration les with SYSGEN.)
On a Series 991 or 995, all UPS devices are attached to the system
via a DTC serial I/O port. As a result, you use NMMGR to
congure them in a procedure similar to conguring terminals, and
then cross-validate the conguration les with SYSGEN. Use this
procedure any time you need to congure UPS devices.
Note
To configure the first
UPS on a Series 9X8
Each UPS device, and only a UPS device, must have its device class
name set to HPUPSDEV during I/O conguration. Otherwise, the UPS
Monitor/iX software will not be able to initialize and communicate
with the UPS device(s) correctly.
After you have installed a new Series 9X8 system, you must \set" the
UPS conguration data supplied in default conguration group. To
congure the rst UPS, do the following:
1. Boot the system using the default conguration group.
2. At the MPE prompt, start the NMMGR program. Enter:
:RUN NMMGR.PUB.SYS
3. Press the Open Config softkey twice and wait while NMMGR
opens a conguration le.
4. Enter a node name and press the Save Data softkey.
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNN
5. Press the Go to DTS softkey to display the DTS conguration
screen.
6. Tab to the third eld and enter the physical path of the
LAN/Console I/O interface card, then press the Save Data
softkey.
7. Press the Go to UPS Port softkey and at the UPS Port screen,
verify that the LDEV number is correct, the Parity Checking
option is set to none, and the baud rate to 1200. Make any
changes to this screen if it is necessary to correct the values.
8. Press the Save Data softkey to save your UPS Port
conguration. (Note that the upper right corner of the screen
will change from Data: N to Data: Y.)
NNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNN
G-2 UPS and UPS Monitor/iX Software
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 conguration with the SYSGEN
conguration.
11. Once validation is complete, press Prior Screen three times
and at the Open Conguration File screen, press Exit Program
to exit NMMGR.
12. Reboot the system to make the new conguration eective.
13. Turn power to the DTC hardware o and then on again to
download the correct baud rate for the UPS port to the DTC
hardware. (On some systems, cycling the power to a DTC may
require you to unplug it and plug it in again.)
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
If you don't know the path of the Console/LAN interface card, start
SYSGEN's I/O congurator and at the io> prompt, use the LDEV
command to check the path:
Note
io>LDEV LDEV=20
The console will be on an I/O path of the form XX/XX.0, such as
56/56.0. The UPS device that you are conguring will have a path
of the form XX/XX.3 (for example, 56.3). Exit the I/O congurator
and Sysgen and use this information in step 6.
To configure a UPS
connected via a DTC
port
Use the following steps when you are conguring additional UPS
devices (i.e., those other than the rst one) on the Series 9X8 system
and for conguring all UPS devices on the Series 991 and 995
systems.
1. At the MPE prompt, start the NMMGR program. Enter:
:RUN NMMGR.PUB.SYS
2. Press the Open Config softkey twice and wait while NMMGR
opens a conguration le.
3. Press Go to DTS to enter the DTS congurator.
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNN
4. Press Go to DTC and choose the appropriate DTC congurator
for the system (DTC16ix, DTC16MX, DTC16, DTC48, etc.).
5. Choose an available LDEV number for the UPS you are
conguring, and determine which DTC port (DTC card number
and port number) the UPS is connected to.
6. Press the Config Card softkey to enter the DTC card
congurator.
NNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
UPS and UPS Monitor/iX Software G-3
7. Add each UPS by entering its logical device number in the Ldev
eld and UP10D12 in the Prole 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
conguration with the SYSGEN conguration.
9. Once validation is complete, press Prior Screen until
you see the Open Conguration File screen, and then press
Exit Program to exit NMMGR.
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
If you see a message that the NETXPORT subsystem has not
been validated, ignore it and exit the program.
10. Shut down the system.
11. Turn power to the DTC hardware o and then on again to
download the correct baud rate for the UPS port to the DTC
hardware. (On some systems, cycling the power to a DTC may
require you to unplug it and plug it in again.)
12. Reboot the system to make the new conguration eective.
To use UPS Monitor/iX
software
Once you have congured UPS devices on the system, they will
automatically be monitored by the UPS Monitor/iX software. This
software causes the UPS devices to emulate the traditional battery
backup method of system powerfail handling and recovery.
The UPS Monitor/iX process behaves in one of two ways, depending
on the system on which Release 5.0 of MPE/iX has been installed:
When installed on a system that has been congured with UPS
devices, UPS Monitor/iX runs continually while the system is
up to monitor all of the UPS devices for power failure and any
other hardware status conditions. It reports these conditions to the
system operator's console via console messages and records them in
the system log le.
When installed on an old system that does not use UPS devices,
UPS Monitor/iX is launched at startup, discovers that there are no
UPS devices on the system, and terminates itself. In this case, the
system uses the existing battery backup method of system power
failure protection.
Note
UPS monitoring is event number 148 in the system log les. The
default is ON (i.e. UPS hardware conditions are recorded in the les)
regardless of whether the system has UPS power fail protection or
not. In the latter case, when no UPS devices have been congured,
the system log les will receive and record two UPS-related messages
each time the system starts: one indicating that the UPS Monitor/iX
process has been launched and a second message which says that no
UPS devices are found in the I/O conguration.
G-4 UPS and UPS Monitor/iX Software
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.
In the \minimal" case, where only the SPU and any Remote Busses
receive UPS power (and assuming that disks are external to the
SPU), the system is most likely to appear to be dormant (like a
traditional battery backup method system) because the system
can not make progress once the disks lose power and spin down.
The system will simply enter its \idle loop", waiting for disk I/O
operations to complete, and that won't happen until AC power
returns and the disks spin up again.
But in expanded UPS coverage systems, where some or all of the
disks receive UPS power, the system may continue to run to some
extent. Again, it depends on what resources the system needs to
perform its workload. Batch jobs that only need CPU, memory, and
disk I/O can continue to run undisturbed. Processing that requires
tape or printer or terminal I/O will be blocked if those peripherals do
not have UPS power.
d
UPS Monitor/iX issues a warning message to the system console to
notify the operator that the particular UPS (identied by its LDEV
number) has reported to the system that its input AC power has
failed. In the following example, UPS Monitor/iX reports and power
failure and a recovery shortly thereafter:
:showtime
FRI, AUG 13, 1993, 11:27 AM
:
:11:27/50/UPS LDEV 102 reports loss of AC input power. (UPSERR 0033)
a
**RECOVERY FROM POWER FAIL**
11:27/50/UPS LDEV 102 reports AC input power restored. (UPSWRN 0036)
c
:
Example ?. Sample Console Messages from UPS Monitor/iX
b
UPS Monitor/iX also writes a system log le entry that denotes the
input power loss to the UPS device. Read ''To enable logging of UPS
activity'' and ''To review UPS activity recorded in the system log
le'', later in this chapter for more information.
UPS and UPS Monitor/iX Software G-5
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.
If AC power returns before the UPS battery becomes exhausted (up
to fteen minutes when starting with fully charged UPS batteries;
less if the batteries were already partially discharged), then the
system recovers from the AC power failure and resumes normal
operation. In this case, UPS Monitor/iX displays a message on the
system console, posts an entry in the system log les, and broadcasts
the following message to all active user terminals:
** RECOVERY FROM POWERFAIL **
If the UPS battery that powers the SPU becomes exhausted before
AC input power returns, then the system really does lose AC power
and crashes. In this case, when AC power does return and the UPS
turns on again, the system reboots just as if it used battery backup.
To enable logging of
UPS activity
The UPS Monitor/iX program posts UPS status and alarm messages
to the system log les. If system logging for the UPS Monitor/iX
(which is event number 148) is turned on, you can review the
messages to troubleshoot your system conguration and evaluate
system performance.
As the default, event 148 is ON. To verify that it is or, if necessary,
to turn it on, do the following:
1. At the MPE prompt, start SYSGEN by entering:
:SYSGEN
2. At the sysgen> prompt, start the LOG congurator by entering:
sysgen>LOG
3. To display which system logging events are enabled or disabled,
enter:
log>SHOW SLOG
You will see a list of information similar to the example shown on
the next page.
4. To turn UPS Monitor/iX logging on (if it is currently listed as
OFF), enter:
log>SLOG ON=148
5. To exit the LOG congurator and SYSGEN, enter the EXIT
command twice. You will see the MPE prompt displayed on your
screen.
G-6 UPS and UPS Monitor/iX Software
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 failure
ACD changes
Stream initiation
User logging
Process creation
Chgroup record
File open record
Maintenance request log
UPS Monitor Event Logging
Diagnostic Information
High Priority Machine Check
Low Priority Machine Check
Directory Open/Close Logging
CM File Close
Chdir
Process Adoption
File Owner Change
event #
------100
101
102
103
104
105
106
107
108
111
112
113
114
115
116
120
130
134
135
136
137
138
139
140
141
143
144
146
148
150
151
152
155
160
161
162
163
status
-----OFF
ON
OFF
OFF
OFF
OFF
ON
ON
OFF
ON
OFF
OFF
OFF
ON
ON
ON
0N
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
OFF
OFF
ON
ON
ON
OFF
OFF
OFF
OFF
OFF
Example ?. Sample System Log Configuration
b
UPS and UPS Monitor/iX Software G-7
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 [email protected]
Note the number of the last log le in the list (other than
LOGDCC). You will use it in step 5.
2. Start the system diagnostic utility. At the MPE prompt, enter:
:SYSDIAG
3. Run the LOGTOOL utility. Enter:
DUI >RUN LOGTOOL
4. To review the current logle, use the SWITCHLOG command to close
it and open a new one.
DUI >SWITCHLOG
5. List the UPS-related messages (which are recorded as system log
event number 148) in the log le that you want to review. For
example, if the last log le displayed with the LISTFILE command
was LOG00017, enter:
DUI >LIST LOG=17;TYPE=148
Or, if the last log le was LOG00017 and you then issued the
SWITCHLOG command, to see the most recent log le you would
enter:
DUI >LIST LOG=18;TYPE=148
In a moment, you will see the contents of the system log les for
event 148, which stores UPS-related messages. If event 148 was
disabled, you are informed that no messages are found.
G-8 UPS and UPS Monitor/iX Software
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. It
allows a remote console to be enabled and to switch between
console and session modes.
account
A collection of users and groups. Each account has a unique
name on the system. It is the method used to organize a system's
users and les and to allocate use of system resources such
as central processor time, online connect time, and le space.
Accounts are the principal billing entity for the use of these
resources. Every user must specify an account to access the
system.
account level security
The types of le access assigned by the system manager to the
account when it is created. The types of access are READ,
LOCK, APPEND, WRITE, and EXECUTE, abbreviated R,
L, A, W, and X respectively. They may be assigned to any
user (ANY), members of the account only (AC), or members of
the group only (GU). The types of le access permitted are the
rst level of system security. The account manager may further
restrict groups and users within an account by assigning them a
limited set of le access modes.
account librarian capability (AL capability)
A capability assigned by the account manager to a user within
the account. An account librarian is allowed special le access
modes to maintain specied les within the account.
Glossary-1
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 denes the user name and
assigns the appropriate capabilities and security restrictions for
the user.
account structure
The method of providing organization, security, and billing for
the system. It is used to allocate use of system resources such
as central processor time, online connect time, and le space.
The account is the principal billing entity for the use of system
resources.
alpha character
A character in the range of A through Z (or a through z).
alphanumeric character
A character in the range of A through Z, a through z, or 0
through 9.
alternate boot path
The path used for booting the system from a boot tape.
application
A set of computer instructions or programs that guide the
computer through a specic task or set of tasks. Examples of
applications include spreadsheets, word processing programs,
graphics, database management, and communications.
application program
A set of computer instructions that guides the computer through
a specic set of tasks. Applications include spreadsheets,
word processing, graphics, database management, and data
communication programs.
architecture
1) The unique set of machine instructions, registers, and other
components that provide the conceptual basis of a computer. 2)
In networking, a structured modular network design in which
dierent data communications tasks are assigned to dierent
layers or levels.
attribute
File access codes and special capabilities that enable the
computer to determine what functions it will or will not allow a
user, group, or account to perform.
Glossary-2
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 oine media, such
as magnetic tape. Backups protect data if a system problem
should occur.
batch access capability (BA Capability)
A default capability assigned to accounts and users that allows
users to submit batch jobs.
battery backup unit
A box within the SPU that contains a battery to supply power to
main memory during a power failure.
boot
The process of loading, initializing, and running an operating
system.
boot path
The pointers to the set of les that are used to bring up the
system from disk or tape. The primary boot path is used for
booting the system from disk resident software. The alternate
boot path is used for booting the system from a boot tape. The
console boot path is used to determine if the system can autoboot
without operator intervention.
boot tape
A tape created by backing up the system conguration with the
system generator (SYSGEN) utility program that is used to
reload the system conguration. Also referred to as a system load
tape. Equivalent to MPE V/E coldload tape.
capability
A method for determining what commands account members are
allowed to execute. Capabilities are assigned to accounts, groups,
and users to provide system security and access to the operating
system. Account capabilities are assigned by the system manager
when the account is created. The account manager then assigns
capabilities to groups and users within the account.
channel
A path within a data communications line through which data
ows.
Glossary-3
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 diering speeds and bandwidths
of the CTB and channel I/O buses.
channel I/O bus (CIB)
A device that provides a synchronous bi-directional data path
between the central bus (CTB) and I/O devices.
channel number
The number assigned to the device controller board in the I/O
card cage. It is used to calculate the logical address of the device,
or device reference table (DRT) number.
CIO adapter (CA)
The interface slot number containing the adapter for the CIO Bus
and central bus (CTB).
CIO expander
The channel input and output expander that provides eight
additional peripheral card slots to the SPU.
class
A user-dened collection of objects.
class name
1) A label that is either unique to, or associated with, one or
more devices in the system's I/O conguration, used to reference
a particular device or class of devices. Device class names may be
up to eight alphanumeric characters long, beginning with a letter.
A single logical device can have multiple device classnames.
The HP 2680 laser printer, for example, is referred to as EPOC
(electrophotographic output for computers),PP (page printer),
or SLP (system line printer). Directing output to any of these
class names sends the output to a laser printer. 2) An abstract
entity that can own objects in an HP SQL DBEnvironment. 3) A
set of one or more SQL or ISQL commands in a le that can be
executed with the ISQL START command.
command interpreter (CI)
A program that reads command lines entered at the standard
input device, interprets them, determines if they are valid, and if
so, executes them.
Glossary-4
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.
Compatibility mode allows current Hewlett-Packard customers to
move applications and data to the 900 Series HP 3000 system
without changes or recompilation.
conguration
1) The way in which computer and peripheral devices are
programmed to interact with each other. 2) The layout of the
computer system, including MPE table, memory, and buer sizes.
The conguration tells which peripheral devices are connected to
the computer and how they can be accessed.
connect time
The amount of time, in minutes, that a user, group, or account
has used the CPU for a session or job. It can be displayed by
executing the MPE REPORT command.
console
A terminal given unique status by the operating system. The
operator uses the console to monitor and manage jobs, sessions
and resources, respond to requests, and communicate with other
user terminals. It is used to boot the system and receive system
loader error messages, system error messages, and system status
messages.
console boot path
The path used to determine if the system can autoboot without
operator intervention.
console command
A command that is executable only from the system console at
the = prompt (generated by pressing 4CTRL5 and the 4A5 key at
the console keyboard). Console commands cannot be entered by
other users because 4CTRL5 4A5 has no meaning on a standard
terminal. The logical console, however, can be moved to a
standard terminal.
console logging
A system logging event. It records console commands in the
system log le.
Glossary-5
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 aect MPE commands. In
documentation this two-key sequence is shown as 4CTRL5 4Y5.
CPU time
The amount of time, in seconds, that a user, group, or account
has used the CPU. It can be displayed by executing the MPE
REPORT command.
crash
1) The unexpected shutdown of a program or system. If the
operating system crashes, it is called a system crash, and requires
the system to be rebooted. 2) A head crash or disk crash. This
occurs when the read/write heads on a disk drive (that normally
ride on a thin cushion of air above the disk) make physical
contact with the disk surface, destroying data and the disk track.
The extent of damage to the system depends on which disk was
involved and how much of the disk was corrupted. A crash of the
system disk is serious, since it contains the directory of user les
as well as operating system programs, the I/O conguration, and
the account structure.
create volumes capability (CV Capability)
The ability to dene and access non system domain disks with the
NEWSET command (private volumes with the NEWVSET command
for MPE V/E). Users and accounts assigned CV capability are
automatically given use volumes (UV) capability.
cumulative backup
A backup strategy where a full backup is done once a week and
partial backups on all other work days.
data communications
The transmission of information from one computer or terminal
to another. It is sometimes shortened to datacom.
data communications and terminal subsystems
The methodology used to connect all asynchronous devices to a
900 Series HP 3000, except for the system console.
default
A predened value or condition that is assumed, and used by the
operating system if no other value or condition is specied.
Glossary-6
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-dened 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). Input
and output spool les are identied by a number in the DFID
(device le identication) column of the SHOWIN and SHOWOUT
command displays. A device le can also refer to any non-disk
device, such as $STDIN and $STDLIST, the default input and
output device les for a terminal.
device independence
A characteristic of the operating system that allows users to
selectively redirect input or output from a program, session, or
job using the FILE command without regard to the nature of the
device. File equations created with the FILE command are in
eect only for the duration of the job or session in which they
were dened.
device subtype
A number ranging from 0 to 15 that denes a specic device
and its associated software driver. There can be several device
subtypes within one basic type. For example, a graphics terminal
and one without graphics capabilities can share the same device
type, but are assigned dierent subtype numbers.
device type
A number that denes a type of device. For example, 0 represents
a moving-head disk and 16 is the device type number assigned to
line printers.
diagnostician capability (DI Capability)
A capability usually assigned only to the Hewlett-Packard
customer engineer (CE). It allows the CE to conduct certain CPU
and diagnostic tests.
directory
A system table showing the group or account in which a le is
located. A directory may contain other information such as size of
the le, its creation date, any modication dates, le creator, or
le security information.
Glossary-7
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.
disk le
A le stored on disk.
disk I/O
The electromechanical process of transferring the code and data
that are stored on disk to and from main memory.
disk pack
A set of one or more disk platters stacked inside a plastic
cylindrical container.
disk sector
A section of a disk's surface. A le is stored in one or more
sectors.
distributed systems line (DS Line)
The communication line between two computers, controlled by
the distributed systems network.
distributed systems network (DSN)
A system of hardware and software data communications
products spanning multiple Hewlett-Packard product lines.
distributed terminal controller (DTC)
An intelligent controller with microprocessors to handle
workstation connection preprocessing and communications with
the system.
DRT number
Device reference table number. The physical I/O address of a
device controller, displayed in the second column of the I/O
Conguration Table listed during the SYSDUMP dialog. An
MPE V/E index into the DRT.
DUMP
A utility program that writes the current state of the system's
main memory and secondary storage to tape for analysis. DUMP
also, optionally, attempts a software reboot from disk.
Glossary-8
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.
extent
A group of one or more contiguous sectors on a volume used to
allocate permanent disk space. Extents can be variable length;
any number of extents can exist for a given le.
le
A group of related records that represents ASCII text (text les)
or binary data (such as executable code). Every le must have a
le name so the user can access the le's contents.
le code
A four-digit integer that identies the special function of a le.
Users can assign a le code between 0 and 1023 to a le they
create to classify it according to its purpose.
le equation
A method of equating a le name to a device or another le. The
FILE command is used to establish the relationship of the le to
the device. Generally used to direct the input to or output from a
program, job, or session to a particular device by referring to the
device class, such as TAPE or LP.
le identier
A number associating a name with a le system object. The le
identier is given to users to access objects via the le system.
le name
A string of up to eight alphanumeric characters, the rst of which
must be an alphabetic character. The le name is assigned when
the le is created or rst saved.
le number
An integer value assigned by the FOPEN intrinsic that is used to
refer to a le in a user program. File numbers zero through seven
are reserved for the operating system.
Glossary-9
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.
formal le designator
An alias le name that is used either programmatically or in a le
equation to refer to a le. The formal le designator is not the le
name found in the system le directory.
free space map
A map of allocated and available disk sectors on the volume set.
fully qualied le name
A complete le description that includes the le name, the group
to which the le belongs, and the account to which the the group
belongs. The fully qualied le name of the LETTER le in the PUB
group of the SYS account is expressed as LETTER.PUB.SYS.
function keys
Special keys on the terminal keyboard that are labelled
sequentially, F1, F2, F3, and so on, and that correspond to the
windows that appear at the bottom of the terminal screen.
Function keys perform various activities.
Fundamental Operating Software (FOS)
The programs, utilities, and subsystems supplied on the master
installation tape (MIT) for MPE.
group
Part of an account that is used to organize the account's les. All
les must be assigned to a group. Each group must have a unique
name within an account. Groups are the smallest entity for which
use of system resources is reported. A PUB group is designated for
each account when it is created. Additional groups are created
within the account, as needed, by the account manager.
group-level security
The le access modes, and the types of users to whom they are
available, as specied by the account manager when the group
is created. File access modes assigned to a group are limited to
those types permitted to the account.
Glossary-10
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.
help facility
An online utility providing information on all commands.
Information can be accessed by topic areas and tasks.
Hewlett-Packard Data-Link Control II (HP-DLC-II)
A standard that denes the elements and procedures for a
balanced, bit-oriented, Level II protocol of the Open Systems
Interconnection (OSI) model.
Hewlett-Packard Graphics Language (HP-GL)
The graphics instruction set for Hewlett-Packard lm recorders
and plotters.
Hewlett-Packard Interface Bus (HP-IB)
A channel consisting of an HP-IB cable connected to an HP-IB
interface card that is connected to the system's backplane. It
performs protocol translation between the CPU and HP-IB.
For the 900 Series HP 3000 system up to six devices can be
connected to a single HP-IB channel. Disk drives, tape drives,
and system printers are connected via an HP-IB which is HP's
implementation of the IEEE standard 488-1975 interface.
High Level Data-Link Control (HDLC)
Types of protocols that eliminate much of the handshaking (and
resultant time-consuming line turnarounds).
histogram
A graphical representation of data.
home directory
The default group, within an account, used as the current working
directory when none is specied at logon time.
home group
The group to which a user is automatically logged on to if no
other group is specied with the HELLO or JOB command. If no
home group is assigned, the user must always specify a group
when logging on. The account manager assigns the home group
when a user's name is rst dened.
Glossary-11
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.
incremental backup
A backup strategy where a full backup is done once a week and
partial backups are done on every other work day.
initial program load (IPL)
The initialization procedure that causes an operating system to
begin operation.
initial system loader (ISL)
The software used to bring up MPE/iX or to perform a memory
dump to tape. It provides a user interface to obtain information
about or to alter the bootpath.
input
1) The data to be processed. 2) The process of transferring data
from external storage to the computer.
input/output (I/O)
The process of, or equipment used in, transmitting information to
or from the computer.
input priority
A number in the range of 1 (lowest priority) to 14 (highest
priority) assigned to input jobs. The input priority can be
assigned by the system (default is 8) or by the user. Jobs with a
input priority less than or equal to the system outfence (default
7) are deferred.
INSTALL
The MPE/iX initial system loader (ISL) utility that performs a
system load from tape and builds essential operating system les
and data structures on disk. Equivalent to the MPE V/E RELOAD
operation.
interactive session
A session that allows users to enter commands and data at the
terminal and receive an immediate response. Interactive sessions
are useful for data entry and retrieval, text editing, or program
development where direct dialog with the computer is preferred.
Glossary-12
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.
I/O dependent code (IODC)
The portion of the operating system software that contains I/O
module dependent data and code used by Processor Dependent
Code (PDC) in conguring the I/O module and in booting the
system.
I/O path
The address of the interface hardware and the physical path to
reach a device. It is constructed top down from where the device
is physically attached to the system. The path is determined by
the CIO adapter module number, the device adapter (DA) slot
number, and the device address.
job
A method of submitting a single command to process multiple
operating system and utility commands. Once submitted, the job
executes independently of the user's session. Jobs are used to
compile source programs, modify les, or perform other functions
not requiring user interaction.
job limit
A limit set to manage the number of jobs executing on the
system. The system manager or operator can restrict system
usage by reducing the number of jobs allowed to run. If the
LIMIT command is used to set the job limit to 0 (zero), no
additional jobs can log onto the system.
keyword
A word assigned a specic meaning by the operating system, a
subsystem, a computer language, or a utility.
keyword parameters
Words that have special meaning to the command interpreter
and are used to modify the intent or eect of an MPE command.
Keyword parameters, unlike positional parameters, may
appear in any order after a command has been entered on
the command line. An entire keyword parameter group, such
as PASS=password, must be separated from other keyword
parameters by a semicolon (;).
Glossary-13
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 conned to a single location. For example,
connecting two or more computer systems within a single oce
together creates a LAN.
Local Area Network Interface Controller (LANIC)
A hardware card that ts into the backplane of the HP 3000
system and provides a physical layer for IEEE 802.3 local area
networks.
local network
The network to which the local node belongs.
local node
The system where you are physically located and logged on, and
at which you enter commands.
locked state
The status of an output spoolle when it is unavailable for
printing.
lockword
A word used as a security device on les. A lockword can be
assigned to a le when it is created or renamed, and must be
supplied to regain access to the le. The word can be from one
to eight alphanumeric characters long and must begin with an
alphabetic character.
log le
A le that maintains a record of events. Each event is recorded
in a separate log record, and is correlated with the job or session
causing the event.
logging
1) The process of recording all system modications to a tape
or disk le for the purpose of recovery or accountability. If the
system fails, the log le can be used to restore the system to its
Glossary-14
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.
logical device number
A number assigned to all hardware components of a computer
system and used for identication purposes.
logo
A method of terminating a session. To log o the system, enter
the BYE or EXIT command.
logon
A method of initiating a session. To log on to MPE/iX, enter the
HELLO command and a valid user and account name, plus a group
name if necessary, and any required passwords.
logon group
The group specied when logging on using the HELLO command.
The syntax is username.accountname, groupname . Once the
desired group is accessed, resident les can be referred to without
fully qualifying them.
logon identity
A security device used to verify users to the system. A logon
identity includes a valid user name and account name in the form
user.account .
logon prompt
A system prompt that indicates the computer is ready to initiate
a session.
logon session
An identication device used when logging on. The correct syntax
is sessionname,username.accountname .
master volume
The only volume needed to dene a volume set. It contains the
conguration data, the root directory, a free space map, le label
table, and a volume label with a unique volume set ID for the
volume set.
Glossary-15
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 conguration 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. Many application programs use menus to show
the options a user can select.
MPE/iX
Multi-Programming Executive with integrated POSIX. The
operating system for the 900 Series HP 3000 computers. MPE/iX
manages all system resources and coordinates the execution of all
programs running on the system.
multiple RIN capability (MR capability)
A capability assigned to accounts and users allowing a user
multiple RINs (resource identication numbers) so they can lock
more than one resource or device at a time. MR capability is
usually restricted to only a few users, since simultaneous resource
locking can lock (or hang) the entire system.
multiple RINs
The mechanism that allows an account, group, or user to lock
more than one resource at a time by specifying the multiple
RIN (MR) capability with the ALTACCT, ALTGROUP, or ALTUSER
commands.
native mode (NM)
The native run-time environment of MPE/iX. In native mode,
source code has been compiled into the native instruction set of
the 900 Series HP 3000 system.
network
A group of computer systems connected so that they can
exchange information and share resources.
network administrator capability (NA capability)
A capability that allows a user to manage the data
communications subsystem at a specied location.
Glossary-16
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.
node manager capability (NM capability)
A capability assigned to users allowing them to control
communications subsystems at their node.
node name
A string of up to 31 characters, not including control characters
or spaces, that uniquely identies a node on a local area network
(LAN).
non-shareable device capability (ND capability)
A capability assigned to accounts and users allowing account
members to own non-shareable devices such as unspooled tape
drives and line printers, serial disks, private volumes (on MPE
V/E), and foreign disks.
nonsystem volumes
Volumes that are member volumes of a volume set. They do not
need to be mounted for the operating system to run.
operating system
The software that allows the computer to operate. It consists of
programs such as basic le and I/O manipulators. All subsystems
run upon the operating system.
operator command
Commands executed only at the system console by the system
operator. Operator commands can be distributed to specic users
at the operator's discretion with the ALLOW, ASSOCIATE, and
JOBSECURITY commands.
OPERATOR.SYS
The user and account that MPE automatically logs on to at the
console when the system is started. OPERATOR.SYS may or may
not be assigned special capabilities. Unlike the system supervisor
(who is assigned OP capability), or the system manager (who is
assigned SM capability), there is no mnemonic that entitles the
operator to execute a special subset of commands. The operator's
power and responsibilities derive solely from control of the
system console and any capabilities assigned to it by the account
manager of the SYS account.
Glossary-17
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. Also, the process of transferring information from
the computer to a peripheral device.
output priority
A number in the range of 1 (lowest priority) to 13 (highest
priority) assigned to an output spool le either by the system (a
default value) or by a user. It is used to determine the order in
which les will be printed.
parameter
A value in a list of values that is passed to a procedure. The
parameter is used in calculations or operations in the procedure.
path
The course within a computer that a message takes, typically
through software protocol handlers.
peripheral
A hardware device attached to and controlled by a computer,
such as a terminal, tape drive, disk drive, or printer.
permanent le
A disk le with an entry in the system directory. To delete the
le, it must be erased from the system with the PURGE command
or with certain invocations of the FCLOSE intrinsic.
permanent space
Disk space reserved for use by permanent structures such as les,
the label table, or the free space map.
port
An outlet from the computer used to connect the computer to
peripheral devices. A cable runs between the outlet and the
device.
positional parameters
One or more terms appearing in a specic order on the command
line that modify the intent or eect of the command. If a
positional parameter is omitted, the user must supply a comma in
its place.
Glossary-18
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 suering 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. This capability, granted to system supervisors and
system managers, allows a job to be dispatched or a session to be
initiated, overriding the current jobfence or execution limit.
private volumes
MPE V/E removable disk volumes that are not included in the
system I/O conguration table and, therefore, must be brought
online with an explicit LMOUNT command. To access a private
volume, a user's logon group and account must be assigned to a
specic volume set with the VS parameter of the ALTGROUP and
ALTACCT commands. Private volumes are nonsystem domain
devices. Equivalent to MPE/iX mountable or nonsystem volumes.
privileged mode capability (PM capability)
A capability assigned to accounts, groups, or users allowing
unrestricted memory access, access to privileged CPU
instructions, and the ability to call privileged procedures.
process
The unique execution of a program or procedure by a particular
user at a particular time. If several users execute the same
program, each is a separate process. Similarly, if the same user
runs several programs, each execution is also considered a distinct
process.
process handling capability (PH capability)
A capability optionally assigned to accounts, groups, and users
allowing a currently executing process to create other processes.
PH capability also allows process suspension, interprocess
communication, and process deletion. Since the proliferation of
processes results in heavy system resource usage, PH capability is
typically restricted to only a few users.
Glossary-19
process identication 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.
program
A sequence of instructions that tells the computer how to perform
a specic task.
programmatic sessions capability (PS capability)
A capability allowing a user to execute the STARTSESS command
and to call the STARTSESS and ABORTSESS intrinsics.
prompt
The character(s) displayed at the terminal screen indicating that
the system is ready for a command. The default MPE command
interpreter's prompt is a colon (:). Other subsystems have
dierent prompts.
PUB group
A group created when an account is created whose les are
usually accessible to all users within the account.
PUB.SYS
The public group of the system account. PUB.SYS is the group
in which programs and applications available to all users of the
system reside.
quiet mode
A session mode in which messages sent from other jobs or sessions
to a terminal are not displayed. Users control quiet mode with
the SETMSG command. To determine who is running quietly,
execute the SHOWJOB command. Those sessions not receiving
messages are indicated by the word QUIET in the third column of
the listing. A WARN message from the system console overrides
quiet mode, and should be used for all critical communication,
such as informing the user of an impending system shutdown.
remote access
Communication with a computer from a physically separate
location.
remote mode
A mode in which a terminal transmits and receives data from a
remote (or host) computer.
Glossary-20
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.
required parameter
A parameter that is required when entering a command or calling
an intrinsic. In reference manuals, required parameters are
surrounded by braces ({}).
resource
Any device or item used by a computer, for example I/O devices,
disk les, or programs.
resource identication number (RIN)
A number identifying a user-dened resource. Users are normally
allowed to lock only a single RIN, which means they can have
exclusive access to one resource at a time, such as an I/O device,
a le, or a program.
resource sharing
The most signicant feature of a network. With resource sharing,
elements at each node are accessible from other nodes in the
network. These elements may include disk les, printers, magnetic
tapes, terminals, and other programs.
response center support (RCS)
An HP support agreement coverage that provides telephone
assistance with software usage and problems.
restore
The process of retrieving user les from SYSGEN (MPE/iX),
SYSDUMP (MPE V/E), and STORE tapes or from serial disk and
writing them to disk. Restoring is executed with the RESTORE
command.
Glossary-21
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.
sector
A portion of a track on a disk, and the smallest addressable piece
of the disk. MPE-formatted disks use 128-word sectors (256
bytes).
security
1) The provisions that prevent unauthorized users from entering
the system, accessing data, or using resources, programs, or
capabilities. 2) The provisions included in MPE to protect the
system from unauthorized use. MPE oers several methods of
creating a secure environment. The most basic level of security
includes organizing les into groups and users into accounts,
either of which may be assigned a password. Security also refers
to the ability to read, write, append, lock, and execute les,
optionally assigned to accounts by the system manager and to
groups and users by the account manager.
segmented library (SL)
A le structure containing code segments that are shareable,
general-use MPE, utility, and subsystem procedures not unique to
a particular process. The three levels of SLs are group library SL,
available to any user who can access the group; the public library
SL, accessible to account users; and the system library SL, used
by all system users.
session
A mode in which the HP 3000 system is used interactively by
entering commands and data through a terminal's keyboard and
receiving immediate responses to input. A session is initiated
with the HELLO command and is ended with the BYE command, or
a second HELLO command that logs the user o the rst session
and onto another session.
Glossary-22
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.
software
A set of programs, instructions, rules, and procedures concerned
with the operation of a computer.
spooling
An activity that permits the concurrent use of output devices
and batch job input. (SPOOL is an acronym for simultaneous
peripheral operations online.) If multiple users send output to a
nonshareable device, such as a tape drive or line printer, their
output is directed to spool les on disk. The output is printed on
a priority basis as the printer becomes available and the users can
proceed with other processing activities without waiting for the
printer. Multiple batch jobs can also be submitted concurrently.
The jobs are spooled to disk and executed according to the
priority level specied by its submitter with the JOB command.
spool queue
Disk space where spool les are kept.
START
An initial system loader (ISL) utility and its options that is
used to start the system from disk and to build the system data
structures. This utility is used to recover from a hang or failure
or to reboot the system after scheduled downtime. The START
RECOVERY option is equivalent to the MPE V/E WARMSTART
procedure, and the START NORECOVERY option is equivalent to the
MPE V/E COOLSTART procedure.
$STDIN
A system-dened le name that refers to the standard input
device used to initiate a session or job; usually a terminal
keyboard, card reader, or tape drive.
Glossary-23
$STDLIST
A system-dened 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. 2) A machine
instruction that tells the CPU to take information from a register
and put it in memory.
stream
To run batch jobs or data from a session or a job by using the
MPE STREAM command. Once a job is streamed, it will execute
as a separate process without requiring any further user input or
supervision.
subsystem
A software program that performs a specic function, such as
compiling programs, copying les, or editing text. Subsystems are
executed by entering a single command at the colon prompt. At
that point a dierent prompt is displayed, and a set of commands
specic to the subsystem become available to the user. The user
must explicitly exit the subsystem, usually by entering E or EXIT.
SYS account
A special account on the HP 3000 system, included with the
system when it is rst installed. It contains all MPE les
(stored in the segmented library), supported subsystems, utility
programs, and compilers.
system
A group of one or more CPUs that communicate through buses
without the use of data communications software.
system abort
An orderly system failure. MPE trys to clean up by closing les
and ushing buers when possible.
system conguration
The process of tailoring the operating system to accommodate the
current physical layout and workload of a particular installation.
The conguration is typically modied when new terminals,
another line printer, or a disk drive are added. The system also
can be recongured to assign new class names to existing devices,
change the size of system tables or virtual memory, modify system
logging, or alter any other conguration parameter.
Glossary-24
system console
1) A workstation given a unique status by the operating system.
It is used by the operator to execute specic 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. The console (and its associated
privileges and responsibilities) may be transferred to another
logical device with the CONSOLE command.
system control panel
A panel on the computer, containing control switches and status
indicator lights.
system-dened les
The les dened by MPE and made available to all users to
indicate standard input or output devices, special temporary les,
and les opened for output that do not perform an actual write
operation.
system disk
The disk volume mounted as logical device 1. It contains MPE,
I/O conguration information, the account structure and le
directory, and utilities and subsystems. It also contains an area
reserved for virtual memory and can be used to store user les.
system domain
An MPE V/E conguration for disk drives. System domain disks
contain only shareable les, and remain online until the system is
shut down. Because information about all system domain disks
is entered into the system volume table, a system domain disk
can be taken oine only by altering the I/O conguration during
the SYSDUMP dialog and coldloading the new conguration.
Equivalent to MPE/iX system volume.
system failure
An internally detected error from which recovery is not possible.
Rather than continue to operate, risking data integrity, the
operating system halts the computer.
system le directory
A directory maintained by MPE that records the name, group,
and account of each permanent le on the system. The directory
contains the size of each le, its location on the disk, who may
access it, and other information.
system generator (SYSGEN)
The MPE/iX utility used to create or modify system and I/O
congurations; add, remove, and replace program les and boot
les; replace system libraries; generate a full system backup; and
Glossary-25
create a boot tape to bring up an MPE/iX system with the new
conguration. 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 logging
The facility that records details of system resource requests in
a series of log les on disk. The system manager or operator
can select which system events to record such as job or session
initiation or termination, program termination, le closing, le
spooling completion, and system shutdown. I/O device failures
are recorded in the system log and are used to detect problems
before they interfere with overall system operation.
system manager
The person who manages the computer installation, is responsible
for creating accounts, and assigns capabilities and resource limits.
system manager capability (SM capability)
A capability assigned to the user name and account to which
the person designated as system manager logs on. The system
manager is responsible for the structure, security, and overall
operation of the system by establishing accounts and assigning
capabilities and resource-use limits to each. The system manager
assigns account manager and system supervisor capabilities to
specic users.
system processor unit (SPU)
The box in which all the processor boards and cards reside.
system startup
A method of loading the MPE operating system from either disk
or tape by bringing a subset of the MPE initiator program into
memory.
system supervisor capability (OP capability)
A capability assigned by the system manager to the system
supervisor's user name and account. The system supervisor
is responsible for performing backups, altering the system
conguration, and in general, tuning the computer so that it
continues to perform well and meet the needs of users.
Glossary-26
system volume
An MPE/iX system volume set. It contains a bootable system
image and system conguration 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.
terminal type
Hewlett-Packard's classication for terminal models and their
capabilities.
throughput
A measurement of a computer system's speed and productivity.
transaction
A logical unit of work.
transaction logging
A method of tracking each unit of work to facilitate recovery from
the abnormal end of transaction processing and system failures.
A transaction log le is automatically generated and maintained
by the transaction management facility. Files can be restored to
a consistent state by copying the contents of the log le into the
data le.
transient space
Disk space used for temporary processes such as stacks and
operating system data structures.
unit number
A part of an address used for devices. A number whose meaning
is software-dependent and device-dependent, but which is
often used to specify a particular disk drive in a device with a
multidrive controller.
UPDATE
1) The MPE/iX ISL utility that performs a system load from
tape. It replaces the current base system les on disk, and
optionally replaces conguration les. The ISL UPDATE CONFIG
option is equivalent to the MPE V/E COLDSTART procedure,
and the UPDATE NOCONFIG option is equivalent to the MPE V/E
UPDATE operation. 2) An MPE V/E coldload option that loads
all les in the PUB group of the SYS account from the backup
media. I/O conguration data, the directory, and user les are
loaded from the system disk. UPDATE is typically used to install
a new version of system software or to load MPE from another
Glossary-27
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 specic 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.
user level security
The le access modes permitted the user. User level security must
duplicate, or be a subset of, the le access permitted the user's
account and group.
user logging
A facility that enables users and subsystems to record additions
and modications to les. If necessary, user logging also provides
the means whereby recorded entries can be used to recover the
les themselves.
use volumes capability (UV capability)
A capability assigned at the account and user level allowing users
to access private disk volumes.
utility program
An operating system program that performs specic functions
such as le copying, sorting, merging, memory dump analysis, or
monitoring available disk space.
variable
A value that can be changed, as opposed to a constant, usually
represented by a letter or a group of alphanumeric characters.
volume
A single disk pack. Each volume is a member of a volume set and
contains a volume label, a label table, and a free space map.
volume class
A class used for the allocation and restriction of disk space. A
volume class is a logical subset or partition within a volume set
and can bridge any number of physical member volumes of a
volume set.
volume name
The name given to a volume set or volume class with the NEWSET
command. The name can be assigned only by a user with CV
(create volume) capability, usually the system manager or account
manager. The volume name is an ASCII character string of up
Glossary-28
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 identied and
referenced. MPE/iX recognizes both system volume sets and
nonsystem, or mountable, volume sets.
volume set information table (VSIT)
A part of a master volume of a volume set containing the volume
set conguration data.
volume testing
The verication that the system continues to operate when loaded
to each limit, the determination of what occurs when those limits
are exceeded, and the determination of what occurs when the
system is emptied after being in a full state.
VOLUTIL
The MPE/iX utility that provides volume initialization and
maintenance, volume label and membership inquiries, and volume
space and sector status. Equivalent to the MPE V/E VINIT
subsystem.
welcome message
A le containing a greeting and important system information. It
is created by the system operator and displayed each time a user
logs onto the system.
work le
A temporary le created when a text editor is invoked. A work
le is a copy (in memory) of a permanent disk le. Any changes
to the work le are lost unless the user saves the updated version
of the le.
write
To put information in a certain place.
write-enable
To remove a disk's write-protection, allowing the disk to be
written upon.
write-protect
To protect stored data so that it cannot be overwritten.
Glossary-29
Index
A
AAUTO
SYSFILE congurator command, 8-8
ABOOT
SYSFILE congurator command, 8-8, 8-9
ABORTJOB
MPE/iX command, E-4, E-8
access panel lock, 2-5
access port
conguring, 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 conguration data, 4-2
ACLASS
I/O Congurator command, 5-11
ACMSL
SYSFILE congurator command, 8-10
SYSFILE Congurator command, 8-8
activating the congurators
SYSGEN utility, 4-15
activating the I/O congurator, 5-5
adding a boot image to the SYSGEN tape, 8-8
adding an autoboot FILE to the SYSGEN tape, 8-8
adding a segment to a temporary copy of the CMSL, 8-8
adding classes in SYSGEN, 5-11
adding devices in SYSGEN , 5-11
adding le names to DUMP to TAPE, 8-10
adding I/O paths in SYSGEN , 5-11
adding objects to the SYSGEN tape, 8-8
ADEV
I/O Congurator command, 5-11
alternate boot path
example, 2-7
alternate boot paths, 5-2
analyser cards, E-1
APATH
Index-1
I/O Congurator command, 5-11
AP error messages
interpreting, A-15
AP help facility
using, A-5
AP informational messages
interpreting, A-15
AP. See access port, 2-2
ASPROG
SYSFILE congurator command, 8-8, 8-10
autoboot and autosearch
autoboot, 3-6
autosearch, 3-6
boot search, 3-6
manual, 3-6
AUTOBOOT command, 2-11, 3-6
autoboot le, 1-2, 2-13
listing current contents, 3-9
autoboot ag, 2-5
enabling and disabling, 3-6
autoboot images
deleting, 8-11
replacing, 8-13
autobooting a Series 925, 2-12
autobooting a system, 1-2
autoexecute le, 1-2, 2-5, 2-13
AUTOSEARCH command, 3-6
autosearch ag
enabling and disabling, 3-6
AVOL
I/O Congurator command, 5-11
B
Index-2
backing up the system, 3-30, 3-32, 3-34, 4-1
base conguration group, 4-1
see conguration group, 4-1
base group
specifying, 4-9
basegroup, 4-1
see conguration group, 4-1
BASEGROUP
SYSGEN command, 4-9, 6-7, F-8
base system les, 3-11
boot command options, 2-14
boot error codes, 2-15, 2-16
boot images
deleting, 8-11
replacing, 8-14
booting sequences, 1-2
booting the system, 2-12
boot path
CA module number for series 922-949, 2-8
DA slot number for series 922-949, 2-8
device address for series 922-949, 2-8
improper, 2-15
boot paths, 2-7, 5-2
alternate, 5-2
console, 5-2
primary, 5-2
boot tape, 1-2, 4-2
boot utilities. See ISL utilities, 3-11
bus converter, 2-9, 5-3
C
cache, E-1
CA module number, 2-8
central bus, 5-2
see CTB, 5-2
central bus (CTB), 2-8, 2-9
changing the I/O conguration online, 5-14
channel adapter, 5-2
channel adapter (CA), 2-8, 2-9
channel I/O bus, 5-2
channel I/O bus (CIB), 2-9
CIO bus, 5-2
classes
adding in SYSGEN , 5-11
CLEAR
LOG congurator command, 6-6
MISC congurator command, 7-13
SYSGEN command, 4-2, 4-17
clearing conguration changes, 6-6, 7-13
SYSGEN utility, 4-17
CMSL, 8-8
adding a segment to, 8-10
replacing a segment of, 8-15
see compatibility mode segment library, 8-8
codes for ISL utility names, C-5
command interpreter
using, A-2
commands
I/O congurator, 5-8
commands, access port
RS, 2-1
TC, 2-1
commands in SYSSTART le, 3-13
commands - I/O congurator
HELP, 5-5
LCLASS, 5-8
LDEV, 5-8
LPATH, 5-8
LVOL, 5-8
MADDRESS, 5-7
OCLOSE, 5-9
commands - I/O Congurator
ACLASS, 5-11
ADEV, 5-11
APATH, 5-11
AVOL, 5-11
DCLASS, 5-13
Index-3
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 congurator
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 congurator
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 congurator
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
SESSION, 7-10
SHOW, 7-4
STACK, 7-11
SYSTEM, 7-12
commands - MPE/iX
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
commands - MPE XL
REPLY, F-11
SHOWDEV, 5-4
Index-4
commands - SYSFILE congurator
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, 4-18, F-11
command syntax
SYSGEN utility, 4-8
compatibility mode segment library, 8-8
see CMSL, 8-8
CONFIG
UPDATE option, 3-27
CONFIG group, 4-2
CONFIG.SYS, 3-27, D-1
conguration
disk drives, F-1{11
HP-FL, F-1{11
HP-IB, F-1{11
retaining current, 3-30, 3-34
SCSI, F-1{11
conguration changes
clearing, 6-6, 7-13
holding, 7-13
saving, 7-13
conguration data, 4-1
account used to store, 4-2
erasing changes, 4-2
Index-5
modifying, 5-1
storing, 1-2
conguration les
copying, D-4
creating, 4-1
permanent, 4-1
temporary, 4-1
conguration group, 4-1
conguring a message catalog, 8-15
conguring job related limits, 7-7
conguring local devices, 5-1
conguring terminals, 1-2
conguring the console, A-1
conrming 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
control mode (CM), 2-2
co-processor, E-1
copying default conguration le groups, D-3
creating conguration les, 4-1
CTB, 5-2
see central bus, 5-2
CTRL B, 2-2
D
Index-6
DAUTO
SYSFILE congurator command, 8-11
DBOOT
SYSFILE congurator command, 8-11
DCLASS
I/O Congurator command, 5-13
DCMSL
SYSFILE congurator command, 8-11, 8-12
DDEV
I/O Congurator command, 5-13
default conguration groups
ALINE925, D-1, D-4
ALINK925, D-1, D-4
ALINK932, D-1
ALINK935, D-1, D-4
ALINK948, D-1
ALINK958, D-1
ALINK990, D-1
ALINK991, D-1
ALINK992, D-1
ALINK995, D-1
CONF9X71, D-1
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
dening a network conguration le, 8-16
dening system parameters, 1-2
deleting autoboot images, 8-11
deleting boot images, 8-11
deleting classes in SYSGEN , 5-13
deleting compatibility mode segments from a SYSGEN tape, 8-12
deleting devices in SYSGEN , 5-13
deleting global resource identication numbers, 7-7
deleting I/O paths in SYSGEN , 5-13
deleting objects from the SYSGEN tape, 8-11
detecting system independent errors, 4-19
determining I/O paths, 5-2
device adapter, 5-2
device adapter (DA), 2-9
device adapter (DA) slot number, 2-8
device address, 5-2
devices
listing, 2-11, 5-8
verifying, E-1
disk boots, 3-1
displaying autoboot and autosearch settings, 3-8
displaying current le information, 8-6
displaying fastsize value, 3-8
displaying local RINs, 7-8
displaying state of congurators
SYSGEN utility, 4-14
DPATH
I/O Congurator command, 5-13
DRIN
MISC congurator command, 7-7
DSPROG
SYSFILE congurator command, 8-11, 8-12
Index-7
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 Congurator 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 congurator, 6-7
entering an MPE command from the MISC congurator, 7-14
entering IOMAP, E-3
entering ODE, E-7
entering the I/O congurator, 5-5
entering the LOG congurator, 6-1
entering the MISC congurator, 7-1
entering the SYSFILE congurator, 8-1
entering the SYSGEN global module, 4-2
erasing conguration changes, 4-2
error codes, A-15
error messages, A-15
escape characters
entering, A-14
EXIT
LOG congurator command, 6-8
MISC congurator command, 7-14
SYSGEN command, 4-24
exiting IOMAP, E-6
exiting MAPPER, E-9
exiting MODE, E-9
exiting SYSGEN, 4-24
exiting the LOG congurator, 6-8
exiting the MISC congurator, 7-14
fastsize, 3-2, 3-8
le information
displaying, 8-6
rst level commands, using, 4-6
rst-time installation, 3-31, 3-33
formal le designators
$STDINX, 4-2
$STDLIST, 4-2
SYSGIN, 4-2
SYSGOUT, 4-2
full system backup , 4-1
G
H
I
generating a boot tape, 4-18
global resource identication numbers
deleting, 7-7
see GRINS, 7-7
GRIN, 7-7
see global resource identication 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 congurator, 5-5
MISC congurator, 7-2
SYSFILE congurator, 8-2
SYSGEN global module, 4-4
HELP facility
LOG congurator, 6-2
Hewlett-Packard Fiber-optic Link, F-1{11
Hewlett-Packard Interface Bus, F-1{11
HOLD
LOG congurator command, 6-7
MISC congurator command, 7-13
SYSGEN command, 4-17
holding conguration changes, 4-17, 6-7, 7-13
HP-FL, F-1{11
HP-IB, F-1{11
identify test, E-2
informational messages, A-18
initial program load (IPL), 2-1, 2-11
initial system loader, 2-1, 4-2
input/output dependent code (IODC), 2-1, 2-12, 3-1
input/output (I/O) congurator, 5-1
input/output (IO) congurator, 4-1
INSTALL, 2-1
ISL utility , D-3
using to recover system, 3-31
installing the operating system, 3-30
preliminary steps, 3-33
required steps, 3-33
INSTALL options, 3-32
INSTALL utility, 3-11, 3-30, D-1
interactively booting a system, 1-2
interrupting AUTOBOOT, 2-13
I/O
SYSGEN command, 5-5
IO
SYSGEN command, F-9
Index-9
I/O conguration
modifying, 5-1
I/O conguration changes
online, 5-14
I/O congurator, 5-1
help facility, 5-5
I/O congurator commands
HELP, 5-5
LCLASS, 5-8
LDEV, 5-8
LPATH, 5-8
LVOL, 5-8
MADDRESS, 5-7
OCLOSE, 5-9
I/O Congurator 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 congurator 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
IOCONFIG Utility, 5-14
IODC, 5-2
see I/O dependent code, 5-2
IODC See input/output dependent code, 2-1
IOMAP
exiting, E-6
functions, E-1
ISL command, E-4
ISL utility, E-1
IOMAP utility, 5-4
activating, E-3
I/O path
alternate boot path, 2-8
console boot path, 2-8
denition, 2-8
primary boot paths, 2-8
I/O paths, 2-7
determining, 5-2
Index-10
series 922-949, 2-8
IPL. See initial program load, 2-1
ISL, 2-1, 2-5, 3-1, 3-6
ALTPATH, 3-2, 3-7
AUTOBOOT, 2-12, 3-2
AUTOSEARCH, 3-2
boot utilities, 3-39
CLKUTIL, 3-9
commands, 3-1
CONSPATH, 3-2, 3-7
dened, 1-1
DISPLAY, 3-2, 3-8
DUMP, 3-11, 3-34, 3-35
ag status, 3-6
HELP, 3-2
INSTALL, 3-11, 3-30, D-1
IOMAP, 2-11, 3-8
LISTAUTOFL, 3-2, 3-9
LISTF, 3-2, 3-5
LS, 3-2
LSAUTOFL, 3-2, 3-9
options, 3-1
PRIMPATH, 3-2, 3-7
READNVM, 3-2, 3-9
READSS, 3-2, 3-9
see initial system loader, 4-2
START, 3-12, D-1
UPDATE, 3-11, 3-26
utilities, 1-1, 3-1
utility options, 3-41
ISL commands
IOMAP, E-4
ODE, E-8
START, 4-2, 5-4, D-3
ISL HELP facility
using, 3-3
ISL settings
example, 3-8
series 950-980, 3-9
ISL utilities
INSTALL, D-3
IOMAP, 5-4, E-1
listing, 3-5
START, 4-2
UPDATE, D-3
ISL utility, 2-1
ISL utility names
codes for, C-5
Index-11
J
K
L
Index-12
JOB
MISC congurator 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 conguration changes, 4-17
keyword parameters
SYSGEN utility, 4-8
LCLASS
I/O congurator command, 5-8
IO congurator command, F-9
LDEV
I/O congurator command, 5-8
IO congurator command, F-9
LDEV number, 5-8
see logical device number, 5-8
LIF. See logical interchange format, 2-13
LIMIT
MPE/iX command, E-3, E-7
LIMIT command, 9-2
limits
conguring job related, 7-7
setting session related, 7-10
listing autoboot and autosearch settings, 3-8
listing classes, 5-8
listing devices, 2-11, 5-8
listing paths, 5-8
listing RINS, 7-8
listing volumes, 5-8
LISTSPF command, 9-3
loading a system, 3-11
load listing, B-1
local devices
conguring, 5-1
LOG
SYSGEN command, 6-1
LOG congurator, 6-1
entering an MPE command from, 6-7
exiting, 6-8
HELP facility, 6-2
see logging congurator, 6-1
LOG congurator commands
CLEAR, 6-6
EXIT, 6-8
HELP, 6-2
HOLD, 6-7
OCLOSE, 6-3
SHOW, 6-3
SLOG, 6-5
ULOG, 6-6
logging
system, 6-1
user, 6-1
logging (LOG) congurator, 4-1, 6-1
see LOG congurator, 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 congurator command, 5-8
IO congurator command, F-9
LRIN
MISC congurator command, 7-8
LVOL
I/O congurator command, 5-8
M
MADDRESS
I/O congurator command, 5-7
I/O Congurator command, 5-12
MAPPER
exiting, E-9
master consoles
changing, A-14
MCLASS
I/O Congurator command, 5-12
MDEV
I/O Congurator command, 5-12
message catalog
conguring, 8-15
mid bus, 5-3
MISC
SYSGEN command, 7-1
MISC congurator, 7-1
entering an MPE command from, 7-14
exiting, 7-14
help facility, 7-2
see miscellaneous congurator, 7-1
MISC congurator command
CLEAR, 7-13
EXIT, 7-14
HOLD, 7-13
JOB, 7-7
LRIN, 7-8
OCLOSE, 7-8
RESOURCE, 7-9
SESSION, 7-10
STACK, 7-11
SYSTEM, 7-12
MISC congurator commands
DRIN, 7-7
Index-13
help, 7-2
SHOW, 7-4
miscellaneous (MISC) congurator, 4-1, 7-1
see MISC congurator, 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 congurations, 5-1
modifying paths in SYSGEN , 5-12
modifying system parameters, 1-2
MPATH
I/O Congurator 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
SHOWDEV, 5-4
MPE XL utilities
SYSGEN, D-4
MVOL
I/O Congurator command, 5-12
N
O
Index-14
NETCONTROL command, 9-4
network conguration le
dening, 8-16
replacing, 8-16
NOCONFIG
UPDATE option, 3-27
nonvolatile memory (NVM), 3-9, C-3
NOSTART
INSTALL option, 3-32
UPDATE option, 3-27
NSCONTROL command, 9-4
NVM. See nonvolatile memory, 3-9
OCLOSE
I/O congurator command, 5-9
IO congurator command, F-9
LOG congurator command, 6-3
MISC congurator command, 7-8
SYSGEN command, 4-14, 4-19
ODE
exiting, E-9
ISL command, E-8
ODE utility
activating, E-7
Online device conguration, 5-14
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
dened, 1-2
permanent conguration 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 congurator command, 8-12
RBOOT
SYSFILE congurator command, 8-12, 8-14
RCAT
SYSFILE congurator command, 8-12, 8-15
RCMSL
SYSFILE congurator command, 8-12, 8-15
RDCC
SYSFILE congurator command, 8-12, 8-16
recovery, system failure, 3-26, 3-29, 3-31
redirecting SYSGEN input and output, 4-22
re-installation, 3-31
reload (INSTALL), 3-31
remote console
disabling access, A-9
enabling access, A-8
remote line
disconnecting, A-10
remote support modem
connecting to a session port, A-10
removing conguration changes, 4-17
removing system programs from a SYSGEN tape, 8-12
repeated parameters
SYSGEN utility, 4-8
replacing a CMSL segment, 8-15
replacing a network conguration le, 8-16
replacing autoboot images, 8-13
replacing boot images, 8-14
replacing objects on the SYSGEN tape, 8-12
replacing operating system, 3-26
REPLY
MPE XL command, F-11
reset, 2-2
Index-15
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 congurator command, 7-9
resource allocations
setting, 7-9
resource identication numbers
deleting, 7-7
see RIN, 7-7
resources
allocating, 7-9
retaining current conguration, 3-30, 3-34
RIN, 7-7
listing, 7-8
see resource identication numbers, 7-7
RIPL
SYSFILE congurator command, 8-12
RNMLIB
SYSFILE congurator command, 8-12
RS, 2-2
access port command, 2-1
hard reset, 2-1
RSPROG
SYSFILE congurator command, 8-12
S
Index-16
saving conguration changes, 4-17, 6-7, 7-13
scheduling an INSTALL, 3-32
scheduling an UPDATE, 3-27
scripting PERMYES, 4-23
scrolling
allowing, A-14
halting, A-14
SCSI, F-1{11
self-test, 2-1, E-2
series 922-949, 2-11
series 950-980, 2-11
Series 920
default conguration, D-1
Series 922
default conguration, D-1
Series 922-949, 2-6
Series 922LX
default conguration, D-1
Series 922RX
default conguration, D-1
Series 925
default conguration, D-1
Series 925LX
default conguration, D-1
Series 932
default conguration, D-1
Series 935
default conguration, D-1
Series 948
default conguration, D-1
Series 949
default conguration, D-1
Series 950
default conguration, D-1
Series 950-980, 2-6
Series 958
default conguration, D-1
Series 960
default conguration, D-1
Series 980
default conguration, D-1
Series 990
default conguration, D-1
Series 991
default conguration, D-1
Series 992
default conguration, D-1
Series 995
default conguration, D-1
Series 9X7
default conguration, D-1
SESSION
MISC congurator command, 7-10
sessions
setting related limits, 7-10
setting resource allocations, 7-9
setting session related limits, 7-10
setting sizes of native mode and compatibility mode stacks , 7-11
setting strings and string parameters, 7-12
SHOW
LOG congurator command, 6-3
MISC congurator command, 7-4
SYSFILE congurator command, 8-6
SYSGEN command, 4-14
SHOWDEV
MPE XL command, 5-4
SHOWDEV command, 9-3
showing current le information, 8-6
showing current LOG values, 6-3
showing the state of congurators, 4-14
showing values of current congurable items, 7-4
SHOWJOB
MPE/iX command, E-4, E-8
Index-17
shutdown
abbreviated list of steps, 1-3
denition, 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 congurator 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. See also TC, 2-1
software clock, 3-9
specifying the base group, 4-9
spool queues
shutting, 9-3
SPU hex status display
disabling, A-11
enabling, A-10
stable storage, 3-7
contents, C-2
reading, 3-9, C-1
STACK
MISC congurator command, 7-11
stacks
setting sizes of compatibility mode, 7-11
setting sizes of native mode, 7-11
START
INSTALL option, 3-32
ISL command, 4-2, 5-4, D-3
ISL utility, 4-2
UPDATE option, 3-27
starting a system, 3-11
START listing, B-1
START options, 3-12
START sequence, B-1
startup
abbreviated list of steps, 1-1
autoboot vs. interactive, 1-2
denition, 1-1
overview, 2-1
startup listing, B-1
START utility, 3-12
status line display, A-3
$STDINX
formal le designator, 4-2
$STDLIST
formal le designator, 4-2
strings
setting, 7-12
strings parameters
Index-18
setting, 7-12
subparameters
SYSGEN utility, 4-8
support, 3-2
SYS account, 4-2
SYSFILE
SYSGEN command, 8-1
SYSFILE congurator, 4-20, 8-1
entering, 8-1
help facility, 8-2
see system le congurator, 8-1
SYSFILE congurator 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, D-1
I/O map, 3-8
SYSGEN commands
BASEGROUP, 4-9, 6-7, F-8
CLEAR, 4-2, 4-17
EXIT, 4-24
halting, 4-8
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, 4-18, F-11
SYSGEN global module
help facility, 4-4
SYSGEN IO congurator
LPATH command, 2-10
SYSGEN tape
deleting compatibility mode segments from, 8-12
deleting objects from, 8-11
Index-19
placing objects on, 8-12
removing system programs from, 8-12
SYSGEN utility, 1-2, D-4
activating, 4-2
activating the congurators, 4-15
clearing conguration changes, 4-17
conrming serious actions, 4-10
displaying state of congurators, 4-14
entering the I/O congurator, 5-5
entering the LOG congurator, 6-1
exiting, 4-24
generating a boot tape, 4-18
global module, 4-1
halting commands, 4-8
holding conguration changes, 4-17
keyword parameters, 4-8
positional parameters, 4-8
redirecting input and output, 4-22
repeated parameters, 4-8
saving conguration changes, 4-17
subparameters, 4-8
SYSFILE congurator, 4-20
using rst level commands, 4-6
SYSGEN Utility
command syntax, 4-8
SYSGIN
formal le designator, 4-2
SYSGOUT
formal le designator, 4-2
SYSMAP, 3-8
SYSSTART le, 3-13
example, 3-14
SYSSTART le modules, 3-16
SYSTEM
MISC congurator command, 7-12
system conguration
adding a disk drive, F-1{11
dened, 1-2
disk drives, F-1{11
PSEUDO id for SCSI interface, F-2
series 917LX through 977, F-1{2
series 920 through 949 CIO, F-3{4
series 920 through 958 NIO, F-4{5
series 950 through 980, F-5{11
system dependent errors, 4-19
system failure
recovery from, 3-26, 3-29, 3-31
system le (SYSFILE) congurator, 4-1, 8-1
see SYSFILE congurator, 4-1, 8-1
system generator (SYSGEN) utility
see SYSGEN utility, 1-2
system independent errors, 4-19
system initialization, 5-2
system load, 3-11
system load tape, D-4
Index-20
see SLT, D-4
system load tape (SLT), D-1
system logging, 6-1, 6-5
system main bus (SMB), 2-9
system parameters
dening, 1-2
modifying, 1-2
system reload (INSTALL), 3-31
system shutdown
overview, 9-1
system shutdown. See shutdown, 1-3
system startup. See startup, 1-1
system status line
interpreting, A-2
system testing, E-2
identify, E-2
loopback, E-2
self-test, E-2
T
U
TAPE
SYSGEN command, 4-18, F-11
tape boots, 3-1
TC, 2-1, 2-2
access port command, 2-1
See also transfer of control, 2-1
soft reset, 2-1
TELL command, 9-2, E-3, E-7
temporary conguration les, 4-1
terminals
conguring, 1-2
testing the access port, A-13
TLB, E-1
see translation look aside buer (TLB), E-1
transfer of control, 2-1, 2-2, A-12
transfer of control. See also soft reset, 2-1
translation look aside buer (TLB), E-1
ULOG
LOG congurator command, 6-6
UPDATE, 2-1
ISL utility, D-3
UPDATE options, 3-27
UPDATE utility, 3-11, 3-26
updating the operating system, 3-26
preliminary steps, 3-28
required steps, 3-28
user logging, 6-1, 6-6
using rst level (global module) commands, 4-6
using I/O congurator commands, 5-7
using SYSGEN to copy conguration les, D-4
using the help facility in SYSGEN's global module, 4-4
using the system generator (SYSGEN), 4-1
utilities
SYSGEN, 1-2
Index-21
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
">