Owner`s manual

ManualsBrandsVax ManualsHousehold AppliancesX-003B

VAX 6000 Series Owner’s Manual

Order Number EK–600EB–OM.002

This manual is intended for the system manager or

system operator and covers the daily operations of a

VAX 6000 series system.

digital equipment corporation

maynard, massachusetts

Summary of content (241 pages)

PAGE 1
VAX 6000 Series Owner’s Manual Order Number EK–600EB–OM.002 This manual is intended for the system manager or system operator and covers the daily operations of a VAX 6000 series system.
PAGE 2
First Printing, October 1990 Revised, November 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.
PAGE 3
Contents Preface xi Chapter 1 The VAX 6000 Series System 1.1 1.2 1.3 1.4 1.5 1.6 System Characteristics . System Architecture . . . Sample System . . . . . . System Front View . . . . System Rear View . . . . Supported Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
Chapter 4 Booting 4.1 4.2 4.3 4.4 4.5 4.6 4.6.1 4.6.2 4.7 4.7.1 4.7.2 4.8 4.9 4.9.1 4.9.2 How Booting Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regular Boot Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot Device Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Boot Processor Selection . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
.10.2 Examples . . . . . . . . . . . . 5.11 FIND . . . . . . . . . . . . . . . . . 5.12 HALT . . . . . . . . . . . . . . . . . 5.13 HELP . . . . . . . . . . . . . . . . . 5.14 INITIALIZE . . . . . . . . . . . . 5.15 REPEAT . . . . . . . . . . . . . . . 5.16 RESTORE EEPROM . . . . . 5.17 SAVE EEPROM . . . . . . . . . 5.18 SET Commands . . . . . . . . . 5.18.1 SET BOOT . . . . . . . . . . . 5.18.2 SET CPU . . . . . . . . . . . . 5.18.2.1 Syntax and Qualifiers 5.18.2.2 Examples . . . . . . . . . . 5.18.
PAGE 6
.9 6.10 Troubleshooting During Booting . . . . . . . . . . . . . . . . . . . . . . . 6–18 Forcing a Boot Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20 Appendix A Compact Disk Drive Instructions A.1 A.2 A.3 A.4 Controls and Indicators . . . Loading a Compact Disk . . Unloading a Compact Disk Cleaning Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Appendix F Control Flags for Booting Appendix G Console Commands Appendix H Console Error Messages (Model 400 and Higher) Appendix I Console Error Messages for Model 300 Appendix J Boot Status and Error Messages (Models 500 and 600) J.1 J.2 J.3 J.4 Ethernet Boot Messages . . . . Local Disk Boot Messages . . Local Tape Boot Messages . . CI and DSSI Boot Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
Figures 1–1 1–2 1–3 1–4 1–5 1–6 2–1 2–2 2–3 2–4 2–5 2–6 2–7 2–8 2–9 3–1 3–2 3–3 3–4 3–5 3–6 4–1 4–2 4–3 4–4 4–5 4–6 4–7 5–1 5–2 5–3 5–4 6–1 6–2 6–3 viii Sample System Footprint . . . . . . . . . . . . . . . . System Architecture . . . . . . . . . . . . . . . . . . . . Sample System . . . . . . . . . . . . . . . . . . . . . . . System Front View . . . . . . . . . . . . . . . . . . . . . System Rear View . . . . . . . . . . . . . . . . . . . . . Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
6–4 6–5 6–6 6–7 6–8 6–9 A–1 A–2 A–3 B–1 B–2 D–1 Self-Test Results: NODE #, TYP, and STF . . Self-Test Results: BPD and ETF . . . . . . . . . Self-Test Results: ILV and Mb . . . . . . . . . . . Self-Test Results: Identification Line . . . . . . Self-Test Results: TYP, STF, and XBI Lines . Troubleshooting Booting . . . . . . . . . . . . . . . . RRD Compact Disk Drive . . . . . . . . . . . . . . Loading a Compact Disk . . . . . . . . . . . . . . . Disk Caddy Parts . . . . . . . . . . . . . . . . . . . . .
PAGE 10
5–5 5–6 5–7 5–8 5–9 5–10 5–11 5–12 5–13 5–14 5–15 5–16 5–17 5–18 6–1 A–1 B–1 C–1 D–1 D–2 D–3 E–1 F–1 F–2 G–1 H–1 H–2 H–3 H–4 I–1 I–2 x BOOT Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . DEPOSIT Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . . EXAMINE Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . FIND Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . INITIALIZE Command Qualifiers . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Preface Intended Audience This manual is written for the system manager or system operator who has had training in VAX systems and system management tasks and is running a VAX 6000 series system. Document Structure This manual uses a structured documentation design. There are many topics, organized into small sections for efficient reference. Each topic begins with an abstract. You can quickly gain a comprehensive overview by reading only the abstracts.
PAGE 12
messages for Model 400 and higher systems. Appendix I has console error messages for Model 300 systems, and Appendix J contains boot status and error messages for Model 500 and 600 systems. • A Glossary and Index provide additional reference support. Conventions Used in This Document The icons shown below are used in illustrations for designating part placement in VAX 6000 series systems. A shaded area in the icon shows the location of the component or part being discussed.
PAGE 13
Table 1 (Cont.
PAGE 14
Table 2 (Cont.
PAGE 15
Table 3 (Cont.
PAGE 16
Table 3 (Cont.
PAGE 17
Chapter 1 The VAX 6000 Series System The VAX 6000 series computer system is designed for growth and can be configured for many different applications. Like other VAX systems, the VAX 6000 series system can support many users in a time-sharing environment.
PAGE 18
1.1 System Characteristics All VAX 6000 series systems share the same characteristics as shown in the tables. Figure 1–1 shows a system footprint. Figure 1–1: Sample System Footprint 154 CM (60.5 IN) 154 CM (60.5 IN) 104 CM (41.5 IN) 56 CM (22 IN) DISK CABINET SYSTEM CABINET TAPE CABINET 78 CM (30.5 IN) 53 CM (21 IN)* REAR CLEARANCE 1 M (39 IN) TAPE CABINET SYSTEM CABINET DISK CABINET WIDTH* 1.9 M (74 IN) .9 M (36 IN) DEPTH 2.
PAGE 19
The values listed in Table 1–1 relate to the system cabinet only. In-cabinet storage will increase electrical requirements. Table 1–1: Electrical Characteristics Electrical1 Hz Without VAXBI With VAXBI 2.5 KVA 3.5 KVA 60 7.0 A (208 V) 9.7 A (208 V) 50 3.5 A (416 V) 3.8 A (380 V) 4.8 A (416 V) 5.
PAGE 20
1.2 System Architecture The high-speed XMI bus is used to interconnect processors, memory modules, and I/O adapters.
PAGE 21
The XMI is the 64-bit system bus that interconnects the processors, memory modules, and I/O adapters. The XMI bus uses the concept of a node. A node is a single functional unit that consists of one or more modules. The XMI has three types of nodes: processor nodes, memory nodes, and I/O adapters. A processor node is a single-board scalar processor or a scalar/vector processor pair. Multiprocessing is supported on VAX 6000 systems. Up to six scalar processors can be used in most systems.
PAGE 22
1.3 Sample System Figure 1–3 shows a sample VAX 6000 system. The system cabinet can have an optional console load device and optional in-cabinet disk drives. The system includes a console terminal and printer, an accessories kit, and a documentation set, which includes this manual. The system may have additional storage devices and may be a member of a VAXcluster.
PAGE 23
Table 1–3: System Components Component Function System cabinet Houses system components and optional storage Console load device Software distribution; stores and transfers data Console terminal Manages system and its resources Console printer Provides hardcopy of console transactions Documentation See the Preface for a full list of documentation related to VAX 6000 series systems Storage cabinet Provides additional storage capacity Your Digital customer service engineer has installed your sys
PAGE 24
1.4 System Front View The control panel and optional console load device and disk control panel are on the front of the system cabinet, accessible with the doors closed. With the front door open, Digital customer service engineers can access the power regulators, the XMI card cage and optional VAXBI card cages, the cooling system, and the optional battery backup unit.
PAGE 25
WARNING: The inside of the system cabinet is not designed to be accessed by the customer. The information in this chapter is for your information only. The cabinet doors are to be opened only by Digital customer service engineers. These components are visible from the inside front of the cabinet (see Figure 1–4 for their location): • Control panel • XMI power regulators • XMI card cage • Cooling system One of the two blowers is visible from the front of the cabinet.
PAGE 26
1.5 System Rear View With the rear door open, Digital customer service engineers can access the power sequencer module (XTC); the power regulators; the I/O bulkhead space behind the card cages; Ethernet and console terminal connectors; cooling system; power and logic box; battery backup unit and disks, if present; and the AC power controller.
PAGE 27
WARNING: The inside of the system cabinet is not designed to be accessed by the customer. The information in this chapter is for your information only. The cabinet doors are to be opened only by Digital customer service engineers.
PAGE 28
1.6 Supported Adapters VAX 6000 systems provide interfaces to other buses and to the Ethernet. Systems can be clustered and storage can be added and shared among systems. The system supports the following adapters: CIXCD, DEC LANcontroller 400 (DEMNA), DEMFA, DWMBB, DWMVA, KDM70, and KFMSA.
PAGE 29
Table 1–4 describes the adapters supported by the system. Note that some adapters require more than one slot on the XMI. Table 1–4: Adapters Adapter XMI Slots CIXCD 1 CI port interface; pler. DEMFA 1 FDDI (fiber optic) port interface; connects a system to a local area network. DEMNA 1 Ethernet port interface; connects a system to a local area network. DWMBB 1 XMI-to-VAXBI interface, a two-module set. The DWMBB/ A is in the XMI card cage; the DWMBB/B is installed in the VAXBI card cage.
PAGE 30
1–14 VAX 6000 Series Owner’s Manual
PAGE 31
Chapter 2 System Components This chapter describes system components, noting their locations and functions. Sections include: • Console load devices Ethernet-based compact disk server Tape drive • Power system • XMI card cage • I/O connections • Cooling system • Options WARNING: The inside of the system cabinet is not designed to be accessed by the customer. The information in this chapter is for your information only.
PAGE 32
2.1 Console Load Devices Figure 2–1 shows VAX 6000 console load devices and their adapters.
PAGE 33
The console load device is used for: • Installing or updating software • Loading diagnostics • Loading the standalone backup program • Interchanging user data Any of the following can serve as the console load device: • Ethernet-based compact disk (CD) server • TF or TK tape drive in the system cabinet • TF magazine tape subsystem in a storage cabinet System Components 2–3
PAGE 34
2.1.1 Ethernet-Based Compact Disk Server The InfoServer is a console load device. During system installation the InfoServer can be used to boot the VAX Diagnostic Supervisor and standalone backup; it is not needed to load or initialize the system following installation.
PAGE 35
The InfoServer, an Ethernet-based compact disk (CD) server, is part of a local area network. The CD server functions as a read-only storage device for any system on the Ethernet. The CD server is used to access CD-ROMs for software installation, diagnostics, and on-line documentation. The DEMNA adapter1 and DEMFA adapter provide an interface to the Ethernet-based CD server. Both adapters are in the XMI card cage.
PAGE 36
2.1.2 In-Cabinet Tape Drive The system cabinet can have a TF or TK tape drive at the upper left of the cabinet. Either tape drive serves as a console load device.
PAGE 37
Three tape drives serve as console load devices. The operation of the TK70 tape drive is similar to that of the TF85 tape drive (see Appendix B for information on how to use the tape drive). The TF857 tape drive also serves as a console load device. The TF857 is a magazine tape subsystem in the SF2xx storage array. Both the TF85 and TF857 tape drives are DSSI devices and require the KFMSA adapter.
PAGE 38
2.2 Power System The power system consists of an AC power controller with circuit breaker, the power and logic box, three power regulators, and an optional battery backup unit. Figure 2–5: Power System (Rear View) POWER REGULATORS POWER AND LOGIC UNIT BATTERY BACKUP UNIT (OPTIONAL) AC POWER CONTROLLER msb-0308A-91 You can see most of the power system from the rear of the cabinet. The AC power controller with circuit breaker (see Section 3.6) is in the lower right corner.
PAGE 39
The XMI power supply is made up of three power regulators.1 The power supply provides sufficient power for any combination of modules (see Table 2–2.) Table 2–1: AC Power Controller Input Voltage Nominal Input Voltages Model No. Hz Phase H405-E 60 208 V 3 H405-F 50 380 V 3 50 416 V 3 Table 2–2: Power Supply Available DC Voltage +5V Available XMI Current 124.0 A +3.3V 80.0 A +12V 4.0 A –12V 2.5 A –5.2V 20.0 A –2V 7.
PAGE 40
2.3 XMI Card Cage The 14-slot XMI card cage houses processors, memories, and adapters. The XMI high-speed system bus interconnects the modules; it has a maximum bandwidth of 100 Mbytes per second and supports up to six processors.
PAGE 41
The system bus, the XMI, allows several transactions to occur simultaneously, making efficient use of the bus bandwidth. The bus includes the XMI backplane, the electrical environment of the bus, the protocol that nodes use on the bus, and the logic to implement this protocol. The 14-slot XMI card cage is located in the upper third of the cabinet on the right side, as viewed from the front of the cabinet.
PAGE 42
2.4 I/O Connections I/O connections are installed on the bulkhead connections tray and the I/O panel. The I/O tray is located in the rear of the cabinet, above the cooling system and below the power regulators, and covers the XMI backplane. The I/O panel is just below the right-hand side of the I/O tray and houses the Ethernet and console terminal ports.
PAGE 43
The I/O bulkhead connections tray is located in the rear of the cabinet, above the cooling system and I/O panel, and below the power regulators. It is hinged at the bottom, and folds out and down for servicing the card cages and backplanes. The I/O panel is on the right side below the tray. The I/O tray and panel have 30 panel units designed to accommodate a variety of I/O connectors. The Ethernet and console terminal connectors are at the bottom of the I/O panel.
PAGE 44
2.5 Cooling System The cooling system consists of a fan, two blower units, and an airflow path through the XMI card cage (and VAXBI card cages, if present).
PAGE 45
The cooling system is designed to keep system components at an optimal operating temperature. It is important to keep the front and rear doors free of obstructions, leaving a clear space of 39.4 inches (1 meter) from the cabinet to maximize air intake. The blowers, located in the lower half of the cabinet, draw air in through the doors and push air up through the card cages. The air is directed through a duct to cool the console load device if there are no VAXBI card cages in the system.
PAGE 46
2.6 Options Other system options in addition to the console load device include the VAXBI card cages and power regulators, battery backup unit, and in-cabinet disks.
PAGE 47
Options include the VAXBI I/O interface, battery backup unit, and incabinet disks. The VAXBI card cages are located in the upper third of the cabinet on the left side, as viewed from the front of the cabinet. The disks and battery backup unit are located beneath the blowers and are rackmounted. The first of these two options to be installed is placed adjacent to the AC power controller.
PAGE 48
Chapter 3 Controls and Indicators This chapter introduces system controls and indicators.
PAGE 49
3.1 Control Panel The control panel, at the upper left of the cabinet front, contains the upper and lower key switches, status lights, and a Restart button. The upper and lower switches are operated by a key.
PAGE 50
The control panel is at the upper left of the cabinet. You use the control panel when powering on the machine or changing the operating mode of your system. The upper and lower switches are operated by a key. Two keys are shipped with each system. The key has a toothed hollow barrel and fits into the slotted circle of each switch. Each key works on both switches. Labels for the control panel’s upper and lower key switches can be in English or in international symbols.
PAGE 51
3.2 Upper Key Switch The control panel’s upper key switch regulates power going into the system and determines use of the console terminal. The four switch positions are Off, Standby, Enable, and Secure.
PAGE 52
Table 3–2: Upper Key Switch Position Effect Light Color O (Off) Removes all power, except to the battery backup charger and optional storage. No light Standby Supplies power to XMI backplane, blowers, and incabinet console load device. Red Enable Supplies power to whole system; console terminal is enabled. Used for console mode or restart, and to start self-test. Yellow Secure (Normal Position) Prevents entry to console mode; position used while machine is executing programs.
PAGE 53
3.3 Lower Key Switch The control panel’s lower key switch controls system operation. The three positions for this switch are Update, Halt, and Auto Start.
PAGE 54
When the upper key switch is in the Secure position, the lower key switch has the effect of Auto Start, regardless of its setting. (See Section 3.2.) Table 3–3: Lower Key Switch Position Effect Light Color Update Enables writing to CPUs and adapters. Halts boot processor in console mode on power-up or when Restart button is pressed. Used for updating parameters stored in EEPROMs (upper key switch must be set to Enable). Prevents an auto restart.
PAGE 55
3.4 Restart Button The Restart button begins self-test, reboot, or both, depending on the position of the upper and lower key switches.
PAGE 56
The upper key switch controls the effect of the Restart button. When the upper key switch is in the Enable position, the Restart button is operative. If the upper key switch is not in the Enable position, the Restart button is ignored. Table 3–4: Restart Button Upper Key Switch Lower Key Switch Restart Button Function Enable Update or Halt Runs self-test, then halts. Enable Auto Start Runs self-test and attempts a reboot. If the reboot fails, control returns to the console.
PAGE 57
3.5 Status Indicator Lights The control panel has three status indicator lights: Run, Battery, and Fault. These lights indicate the operating status of the system.
PAGE 58
Three status indicator lights on the control panel show the state of system execution (Run), the presence of a battery backup unit (Battery), and hardware errors (Fault). Figure 3–5 shows a system that is in operation, with a fully charged battery backup unit installed. Table 3–5 describes the conditions indicated by the status indicator lights.
PAGE 59
3.6 Circuit Breaker The circuit breaker is on the AC power controller, which is at the bottom right corner at the back of the cabinet.
PAGE 60
Figure 3–6 shows the AC power controller, which is at the rear of the cabinet. Circuit Breaker The circuit breaker controls power to the entire system, including the power regulators, blowers, and in-cabinet options. Current overload causes the circuit breaker to move automatically to the Off position, so that power to the system is turned off. For normal operation, the circuit breaker must be in the On position, which is fully pressed in.
PAGE 61
Chapter 4 Booting This chapter describes how to boot the system.
PAGE 62
4.1 How Booting Works The boot program reads the virtual memory boot program (VMB) from the boot device. VMB in turn boots the operating system.
PAGE 63
Table 4–1: Boot Procedure Step Procedure 1 You enter BOOT command from the console terminal in console mode. The BOOT command specifies the boot device and the path needed to reach it. 2 System reinitializes and performs self-test. 3 Boot primitive is invoked from console ROM on the boot processor. Boot primitive reads the bootblock from the specified boot device and transfers control to the bootblock. 4 The bootblock contains code and a pointer to VMB.
PAGE 64
4.2 Boot Devices The system can be booted from one of four boot devices: the system console load device, a local system disk, a disk connected to the system through a CIXCD adapter, or by Ethernet from a remote disk on another system.
PAGE 65
Table 4–2: Boot Devices Device Location Console load device Tape drive in the upper left corner of the system cabinet, a TF857 tape drive in an SFxxx cabinet, or an Ethernet-based CD server. All are used for booting standalone backup or diagnostics. See Section 2.1. Local disk Disk connected to the system through a KDM70 or KFMSA adapter. Regular boot procedure specifies such a disk as default boot device for individual systems that are not VAXclustered or networked.
PAGE 66
4.3 Regular Boot Procedure With the system in console mode, you issue a BOOT command. You can give a complete specification in which the qualifiers determine the boot device, or you can use a nickname.
PAGE 67
Figure 4–3 shows the components of the BOOT command. The /XMI node number you enter corresponds to an adapter; if you have an optional VAXBI, the /XMI node number will correspond to a DWMBB adapter and you must then use the /BI qualifier to specify the node number of the boot device on that VAXBI. When using the /R5:n qualifier, see Appendix F for the values of n. The /R3:r qualifier is used with VMS when you boot from a shadow set, where r is two unit numbers.
PAGE 68
4.4 Boot Device Selection You can boot the operating system in a number of ways. Table 4–3 lists some examples. Table 4–3: Sample BOOT Commands Boot Procedure BOOT Command Boot from in-cabinet console load device BOOT CSA1 Boot VAX/DS from an in-cabinet console load device BOOT /R5:10 CSA1 Boot from local RA disk BOOT /XMI:m DUww Section 5.6 Boot from local RF disk BOOT /XMI:m /DSSI_NODE:y /PORT:z DIww Section 5.6 Boot from HSC disk BOOT /XMI:m /R5:v/NODE:sstt DUww Section 4.
PAGE 69
You can issue a complete boot specification, or you can use a nickname that has been defined for a complete boot specification. Issuing BOOT alone will boot from whatever has been set as the default boot. When you use the BOOT CSA1 command, you designate the in-cabinet TF or TK tape drive as your boot device. Boot device mnemonics are listed in Table 4–4.
PAGE 70
4.5 Boot Processor Selection One processor is selected as the boot processor, and all other processors become secondary processors. This determination is made by the system at power-up or initialization, and can be altered by using console commands. Figure 4–4: Determining the Boot Processor SECONDARY PROCESSORS BOOT PROCESSOR 1. PROCESSORS RUN SELF-TEST 2. PROCESSORS DETERMINE BOOT PROCESSOR 3.
PAGE 71
Each processor has an image of the console program and boot code in ROM, but there is only one console terminal and a single system control panel. One processor is designated as the boot processor (or primary processor) and becomes the primary communicator to the console program. The signals from the console terminal and system control panel are bused on the XMI and are driven by the boot processor. At power-up or initialization of the system, the console program in each processor begins parallel execution.
PAGE 72
4.6 Booting from an HSC Disk 4.6.1 VAXcluster Boot Overview This section describes booting VMS from a VAXcluster. ULTRIX is booted in the same way, except that R5 bits must be specified (see Appendix F).
PAGE 73
When you boot VMS from a VAXcluster, you need to gather the following information: • Node number of the HSC controller(s) • Device address of the disk unit that will execute boot • Location of the system root The node number of an HSC controller is a 2-digit hexadecimal number. The device type is of the form DU0 (see Section 5.6). The location of the system root is a hexadecimal number that indicates the system to be booted. Figure 4–5 shows a sample VAXcluster configuration.
PAGE 74
4.6.2 Sample VAXcluster Boot This section shows a sample boot from a system to be booted in the VAXcluster configuration shown in Figure 4–5. Example 4–1: Sample VAXcluster Boot ! >>> SHOW CONFIGURATION Type Rev 1+ KA65A (8080) 0006 2+ KA65A (8080) 0006 3+ KA65A (8080) 0006 6+ MS65A (4001) 0084 7+ MS65A (4001) 0084 8+ MS65A (4001) 0084 9+ MS65A (4001) 0084 D+ CIXCD (0C05) 1652 E+ DEMNA (0C03) 0600 ! ! ! ! ! ! Enter command. Find the XMI address of the CIXCD, which is the VAXcluster interface.
PAGE 75
! " # $ % & SHOW CONFIGURATION displays the positions of modules. The first column identifies each module’s node, slot location, and self-test status. The second column entries are the device names; the third, the device type codes. The last column shows the revision level of each module. The CIXCD is located at XMI node D. Enter this value D in the BOOT command as the argument to the /XMI qualifier. In the BOOT command, the system root is the argument to the /R5 qualifier.
PAGE 76
4.7 Booting from an Ethernet-Based Compact Disk Server 4.7.1 CD Server Boot Command This section shows a sample boot on a Model 500 system from an Ethernet-based compact disk (CD) server. The first step is issuing the boot command.
PAGE 77
Example 4–2 (Cont.): Sample Ethernet-Based CD Server Boot * * * * * * ! " # $ % % Initializing adapter Specified boot adapter initialized successfully "Request Program" MOP message sent - waiting for service from remote node Remote service link established Reading boot image from remote node Passing control to transfer address SHOW CONFIGURATION displays the positions of the modules. The DEMNA is located at XMI node E. Enter this value E in the BOOT command as the argument to the /XMI qualifier.
PAGE 78
4.7.2 Selecting an Ethernet Service The second step of booting over the Ethernet with a CD server is selecting the service that boots VMS.
PAGE 79
! " # $ % The Ethernet Initial System Load Function menu is displayed. The system prompts you for a function ID value. Enter 3 to select a service. The Service options menu is displayed. Enter 1 to display the available Ethernet servers and services. In this example one server, ESS_ 08002B150589, is found on the Ethernet. Next, the Service Name Format is displayed, followed by the services. Service #1, VMS054, is used to boot VMS. Enter 1 to select service #1. The operating system banner appears.
PAGE 80
4.8 Ethernet Boot Overview To boot VMS over the Ethernet, you use the Network Control Program (NCP). The system supports booting over the Ethernet, both trigger booting and booting initiated by the system as a target node.
PAGE 81
The Ethernet is used to boot in two ways. Figure 4–6 and Figure 4–7 illustrate these methods. A trigger boot initiates a BOOT command from a command system, which sends the command over the Ethernet to the executor system, which causes a boot in the target system (the VAX 6000 series system). The target system loads its boot program from the boot device that is designated as the default. (The default can be a local disk or the Ethernet.
PAGE 82
4.9 Sample Target-Initiated Ethernet Boot To perform a target-initiated boot over the Ethernet: (1) gather information at the target node, (2) enter the information into the Network Control Program volatile database on the executor node, and (3) issue a BOOT command from the target node. Example 4–4 through Example 4–6 show this procedure. 4.9.1 Step 1, Gather Information at Target Node This section presents an example of booting over the Ethernet, in a target-initiated boot from a VAX 6000 series system.
PAGE 83
The first step in an Ethernet boot is to gather the information from your system that you need in the Ethernet boot. ! " Use the SHOW ETHERNET command to find the address of your system on the Ethernet and write it down. You load this address into the executor system’s volatile database in the next step (Section 4.9.2). The system reports the hardware Ethernet address for the DEMNA. The DEMNA is at XMI node E. The system also reports the FDDI hardware address for the DEMFA adapter.
PAGE 84
4.9.2 Step 2, Enter Information into Executor’s NCP Volatile Database The second step of booting over an Ethernet is entering the target node information into the Network Control Program (NCP) volatile database on the executor system. Example 4–5: Step 2, Entering Target Node Information $ MCR NCP ! ! ! ! ! ! ! NCP> NCP> NCP> NCP> NCP> set set set set node node node node TARGET TARGET TARGET TARGET On the executor system, at the DCL prompt, run NCP. NCP prompt appears.
PAGE 85
Example 4–5 (Cont.): Step 2, Entering Target Node Information NCP> NCP> sho line MNA-0 char ) ! Prompt returns; show ! line characteristics. Line Volatile Characteristics as of DD-MMM-YYYY 00:00:01 Line = MNA-0 Receive buffers Controller Protocol Service timer Hardware address Device buffer size = = = = = = 6 normal Ethernet 5000 08-00-2B-06-01-00 1498 ) On the executor system, under VMS or the executor’s operating system, run NCP, the Network Control Program, on an appropriate privileged account.
PAGE 86
4.9.3 Step 3, Boot from the Target Node The third step in Ethernet booting is to issue the BOOT command from the target node. Example 4–6: Step 3, Booting from the Target Node >>> BOOT /XMI:E EX0 ! Enter BOOT command Initializing system #123456789 0123456789 0123456789 0123456789 012345# F E D C B A 9 8 7 6 5 4 3 2 1 A + . . . A + . . . . . . . . . . . . . . . . . . M + . . . M + . . . M + . . . M + . . . . . . . . . . . . .
PAGE 87
Enter the BOOT command from the console terminal in console mode. Use the XMI node number that you found in Step 1, Section 4.9.1, describing the path of the Ethernet controller.1 Because the target VAX 6000 series system has been registered in the NCP volatile database of the executor system, the Ethernet boot completes. The executor system determines the location of the boot program. 1 If your system has a VAXBI and a DEBNI or DEBNA Ethernet adapter, you must enter an additional /BI:n node qualifier.
PAGE 88
Chapter 5 Console The console program for the VAX 6000 series follows VAX console standards as described in Chapter 11, VAX Console Subsystems, of the VAX Systems Hardware Handbook — VAXBI Systems. This chapter describes the console, its functions, and its language. Examples are given for each console command and its qualifiers.
PAGE 89
5.1 Description of Console The console subsystem consists of a console terminal, console program located in ROM on the CPU modules, and dedicated memory. The console program runs on all processors and is automatically entered when the boot processor encounters a restart condition or when an operator invokes console mode on the console terminal.
PAGE 90
Table 5–1: Console Parts and Functions Part Function Console terminal Used for input, entering console commands. Console printer Provides a hardcopy record of console sessions. Console terminal port Connects the console terminal to the system. Console program Software interface; translates console commands to the processors; resides in ROM on each processor.
PAGE 91
5.2 Console Functions Using the console program, you can examine and modify the system memory and registers, boot or restart an operating system, designate a primary processor, disable a vector processor, and return to program mode.
PAGE 92
You use the console terminal to control the system manually, correct errors, determine the status of machine registers and counters, determine the contents of storage, and revise the contents of storage. Following self-test or a SET CPU console command, one processor in a multiprocessor system is designated as the primary or boot processor. The location of the primary processor is determined at startup or when the system is reset. The primary processor performs a bootstrap or warm restart of the system.
PAGE 93
5.3 Console Mode To enter console mode from program mode, turn the upper key switch on the front control panel to the Enable position and type CTRL/P at the console terminal. Figure 5–2: Console Switch When in Console Mode 0 FRONT Standby Run Enable Battery Secure Fault Update Halt Auto Start Restart msb-0174A-91 The console terminal can operate in two modes: program mode and console mode.
PAGE 94
Halt selected. If you type CTRL/P when the upper key switch is in the Secure position, the CTRL/P is passed on to the operating system, and the operating mode does not change. CTRL/P interrupts program mode on the boot processor. The secondary processors continue operating in program mode until they must wait for resources locked by the primary processor. Some I/O devices also require the attention of the primary processor.
PAGE 95
5.4 Console Command Language Control Characters Eleven ASCII control characters have special meaning when you type them on the console terminal running in console mode. See Table 5–3. Table 5–3: Console Control Characters Character Function BREAK Increments the console baud rate, if enabled. CTRL/C Causes the console to abort processing of a command. CTRL/O Causes the console to discard output to the console terminal until the next CTRL/O is entered. CTRL/P In console mode, acts like CTRL/C .
PAGE 96
CTRL/O stops output to the console terminal until you enter the next CTRL/O. CTRL/O is echoed as ^O followed by a carriage return and is not echoed when you reenable output. Output is also reenabled when the console prompts for a command, issues an error message, enters program mode, or when you type CTRL/P or CTRL/C. CTRL/P works like CTRL/C and is echoed as ^P, if the console terminal is in console mode.
PAGE 97
5.5 Console Command Language Syntax The console command language has syntax rules for forming commands. Commands contain up to 80 characters, can be abbreviated, and accept qualifiers. Tabs and spaces are compressed. Numbers are in hexadecimal notation. Table 5–4: Console Command Language Syntax Command Parameter Attribute or Action Length 80 characters maximum. Abbreviation Varies with the command; usually the shortest unique combination of letters.
PAGE 98
The console program accepts commands up to 80 characters long. This does not include the terminating carriage return or any characters you delete as you enter the command. A command longer than 80 characters causes an error message of the form: ?0036 Command too long. You can abbreviate commands and some qualifiers by dropping characters from the end of the word. You must enter the minimum number of characters to identify the keyword unambiguously.
PAGE 99
5.6 BOOT The BOOT command initializes the system and begins the boot program. See Section 4.1 for information on how booting works on a VAX 6000 series system. The examples are explained in Section 5.6.2. For details on the SET BOOT command, see Section 5.18.1. 5.6.1 BOOT Command Examples and Qualifiers Examples 1. >>> BOOT ! Boots from the special boot ! specification named DEFAULT. 2. >>> BOOT/XMI:C DU0 ! Boots from a disk with hex unit no. 0 con! nected via a KDM70 controller at XMI node C. 3.
PAGE 100
6. 7. >>> BOOT /XMI:E /DSSI_NODE:4 /PORT:1 DI5 ! Boots from a disk with unit number 5 connected by the ! KFMSA adapter and the controller at DSSI node 4, port 1. >>> BOOT /XMI:E /DSSI_NODE:5 /PORT:2 MI3 ! Boots from a TF tape on a DSSI. Table 5–5: BOOT Command Qualifiers Qualifier Function /X[MI]:number Specifies the XMI node number of the node that connects the boot device.
PAGE 101
5.6.
PAGE 102
The BOOT command syntax is: B[OOT][/qualifier] [] BOOT command qualifiers are summarized in Table 5–5. The qualifier includes a variable which is a node number, a value to be loaded into a register, or the name of a file when using the /FILENAME qualifier. A variable is a required argument to the qualifier. If you do not specify a variable, you receive an error message in the form: ?0021 Illegal command In the syntax can be a string of the form ddnn.
PAGE 103
5.7 CLEAR EXCEPTION The CLEAR EXCEPTION command is used to clear error states in registers. Examples 1. >>> EXAMINE 21800000 ! Attempt to examine a non?0029 Machine check accessing memory. ! existent address produces ! a machine check and sets >>> CLEAR EXCEPTION ! some error bits. XBE0 = 000000C0 ! Register values before XFADR0 = 61900008 ! CLEAR EXCEPTION clears XBEER0 = 01240001 ! the error bits. PCSTS = 000008C0 >>> 2.
PAGE 104
The CLEAR EXCEPTION command syntax is: CL[EAR] EX[CEPTION] This command is used to clear error states that remain from a previous command, a sequence of commands, or a console action. The console displays what is currently in the registers shown in the examples and then clears write-one-to-clear bits in the XBER, XBEER, and CPU-specific registers. In most cases the console program cleans up the error state.
PAGE 105
5.8 CONTINUE The CONTINUE command begins processing at the point where it was interrupted by a CTRL/P console command. Programs continue processing at the address currently in the program counter of the processors. Example $ ^P ! Stops processing on boot procesor; ! processor enters console mode. ! ?0002 External halt (CTRL/P, break, or external halt) PC = 801DBAA6 ! System responds with error message; PSL = 04C38201 ! system has halted with address ISP = 80B15200 ! 801DBAA6 in the program counter (PC).
PAGE 106
The CONTINUE command takes no arguments. Its syntax is: C[ONTINUE] CONTINUE causes the processor to resume program mode, executing at the address currently in the program counter (PC). This address is the address that was in the PC when the primary processor received the CTRL/P input to interrupt processing and change to console mode. The system displays the hexadecimal PC and the hex values for PSL and –SP (see Appendix H).
PAGE 107
5.9 DEPOSIT The DEPOSIT command stores data in a specified address. 5.9.1 Syntax and Qualifiers Table 5–6: DEPOSIT Command Qualifiers Qualifier Meaning /B Defines data size as a byte. /G Defines the address space as the general register set, R0 through R15. /I Defines the address space as the internal processor registers, accessed through MTPR and MFPR instructions. /L Defines data size as a longword; initial default.
PAGE 108
The DEPOSIT command syntax is: D[EPOSIT] [/qualifier]
where /qualifier is a value from Table 5–6, and the variable is a hexadecimal value to be stored. The value must fit in the data size to be deposited. The variable
is a 1- to 8-digit hexadecimal value or one of the following: • PSL, the processor status longword. You cannot use any address space qualifier with PSL. • PC, the program counter. The address space is set to /G. • SP, the stack pointer.
PAGE 109
5.9.2 Examples Examples 1. >>> D/P 27 0 ! ! Deposits the value of 0 to physical address 27. 2. >>> D/N:8 R0 FFFF ! Loads registers R0-R8 with FFFF. 3. >>> DEPOSIT/P/B/N:1FF 0 0 ! ! ! Deposits zeros to the first 512 bytes of physical memory beginning with address 0. 4. >>> DEPOSIT/VE V12 0 ! ! Deposits zero into all 64 elements of vector register V12. 5. >>> DEPOSIT VLR 1 ! ! Deposits one in the Vector Length Register. 6.
PAGE 110
The DEPOSIT command directs data into the specified address. If you do not specify any address space or data size qualifiers, the defaults are the last address space or data size specified in a DEPOSIT or EXAMINE command. After processor initialization, the default address space is physical memory, the default data size is longword, and the default address is zero. If the specified value is too large to fit in the data size, the console program ignores the command and issues an error message.
PAGE 111
5.10 EXAMINE The EXAMINE command displays the contents of a specified address. The qualifiers are identical to the DEPOSIT command’s qualifiers. 5.10.1 Syntax and Qualifiers Table 5–7: EXAMINE Command Qualifiers Qualifier Meaning /B Defines data size as a byte. /G Defines the address space as the general register set, R0 through R15. /I Defines the address space as the internal processor registers, cessed through MTPR and MFPR instructions. /L Defines data size as a longword; initial default.
PAGE 112
The EXAMINE command syntax is: E[XAMINE] [/qualifier] [
] where /qualifier is a value from Table 5–7, and
is a 1- to 8-digit hexadecimal value or one of the following: • PSL, the processor status longword. You cannot use any address space qualifier with PSL. • PC, the program counter. The address space is set to /G. • SP, the stack pointer. The address space is set to /G. • Rn, the general purpose register n. The register number is in decimal. The address space is set to /G.
PAGE 113
5.10.2 Examples Examples 1. >>> E/N:8 R0 ! Examines registers R0-R8. 2. >>> EXAMINE/P/B/N:1FF ! Examines the first 512 bytes. 3. >>> EXAMINE/N:5/W/P - ! ! ! Examines the previous word in the physical address space and the next five words. 4. >>> E/I 3E ! ! Examines the system ID register. System responds with output. ! ! Examines the Vector Length Register. ! ! ! ! Examines the vector indirect register at hex address 440. /M is used to access vector indirect registers. I 5.
PAGE 114
VE VE VE VE VE VE VE VE VE VE VE VE VE VE VE VE VE V00:1E V00:20 V00:22 V00:24 V00:26 V00:28 V00:2A V00:2C V00:2E V00:30 V00:32 V00:34 V00:36 V00:38 V00:3A V00:3C V00:3E 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 00000002 VE VE VE VE VE VE VE VE VE VE VE
PAGE 115
5.11 FIND The FIND command causes the console program to search main memory starting at address zero for a page-aligned 256-Kbyte block of good memory (that has no errors) or for a restart parameter block (RPB). If the block is found, its address plus 512 is left in the stack pointer. If the block is not found, an error message is issued. Examples 1. >>> FIND/MEMORY >>> ! Searches for a 256-Kbyte memory ! block; returns prompt when found. 2.
PAGE 116
The FIND command syntax is: F[IND] [/qualifier] where /qualifier is either /MEMORY or /RPB. The FIND command searches main memory to find a page-aligned 256-Kbyte block of good memory or a restart parameter block. If you do not use a qualifier, the FIND command searches for a restart parameter block, as if you used a /RPB qualifier. There is a wait, while the system searches all memory. This may take up to 2 minutes for each 32 Mbytes of memory.
PAGE 117
5.12 HALT The HALT command is a null command for the system operating in console mode. The command is accepted, but no action is taken since the processor has already halted in order to enter console mode. Example >>> HALT ?0026 Halted ! ! ! ! ! You enter the HALT command. System responds with error message that indicates the system already is halted.
PAGE 118
The HALT command syntax is: HALT where the command takes no arguments. On other VAX systems, the HALT command stops the processors. However, on VAX 6000 series systems, HALT has no effect, because the boot processor is already halted as a requisite condition for console mode. See the STOP command, Section 5.21.
PAGE 119
5.13 HELP The HELP command provides basic information on the console commands, when the console terminal is in console mode. Examples 1. >>> HELP BOOT CLEAR_EXCEPTION CONTINUE DEPOSIT EXAMINE SelfTest_Output FIND HALT HELP INITIALIZE REPEAT RESTORE_EEPROM SAVE_EEPROM SET CTRL_Characters SHOW START STOP TEST UNJAM UPDATE Z ! For more information, type HELP . 2. >>> HELP FIND FIND Searches memory for the specified item. Qualifiers /MEMORY /RPB 3.
PAGE 120
The syntax for the HELP command is: HELP [] where is one of the entries listed in the main HELP printout. The HELP command operates when the console program error messages are set in English mode (see Section 5.18.3). To see a list of all HELP files available, enter HELP or HELP HELP at the console prompt, followed by a carriage return. The system responds with a list of available HELP files.
PAGE 121
5.14 INITIALIZE The INITIALIZE command performs a reset. You can initialize the entire system, a specified XMI node (except memory), or a specified VAXBI node. Examples 1. >>> INITIALIZE 1 ! Initializes node 1 on the XMI. ! No self-test results are displayed. 2. >>> I/B:2 E ! Initializes node 2 on a VAXBI ! where E is the node on the XMI ! that goes to node 2 on the VAXBI. 3. >>> I ! Resets the entire system. #123456789 0123456789 0123456789 0123456789 012345# F .
PAGE 122
Table 5–9: INITIALIZE Command Qualifiers Qualifier Meaning /B[I]: Can be used only if the specified XMI node is a DWMBB/A. This qualifier resets the single adapter at node on the specified VAXBI. None If no XMI node number is given and a /BI qualifier is omitted, the system resets all nodes on the XMI (and optional VAXBI) and prints out self-test results.
PAGE 123
5.15 REPEAT The REPEAT command reexecutes the command that you pass as its argument. You can use the REPEAT command with any command except itself. The key combination CTRL/C stops the REPEAT command. Example >>> REPEAT E/P 10 ! ! ! ! Continuously displays the contents of physical memory at address location 10. To stop the display, enter a CTRL/C.
PAGE 124
The REPEAT command syntax is: R[EPEAT] where is any command other than REPEAT. REPEAT works as a continuous repeat. The command you pass as an argument to the REPEAT command continues to be executed until you stop the process with CTRL/C.
PAGE 125
5.16 RESTORE EEPROM The RESTORE EEPROM command can be used if your system has a TK tape drive1 as a console load device. This command copies the TK tape’s EEPROM image to the EEPROM of the boot processor. Example ! ! ! ! Lower key switch must be in Update position. Load the TK tape with EEPROM contents. When the yellow light on the TK70 drive stays on, enter RESTORE command. >>> RES E ?006E EEPROM Revision = x.xx/y.yy ?0070 Tape image Revision = x.xx/y.
PAGE 126
2. Put the control panel’s lower key switch in the Update position (see Section 3.3). 3. Put the control panel’s upper key switch in the Enable position, and type CTRL/P at the console terminal to put the terminal in console mode (see Section 5.3). 4. Move to the processor whose EEPROM contents you wish to restore. Normally, all EEPROM contents will be the same. If you are restoring the contents of the boot processor, proceed to the next step.
PAGE 127
5.17 SAVE EEPROM The SAVE EEPROM command can be used if your system has a TK tape drive1 as a console load device. This command copies the EEPROM contents of the boot processor to the TK tape. Examples 1. >>> SAVE EEPROM ! ! ! ! ! Load a TK tape. When the yellow light on the TK drive stays on, the tape is ready. Enter SAVE command. System prompts user to proceed. Enter a Y to continue. Proceed with save to tape? (Y or N) >>> Y ?006C EEPROM saved to tape successfully.
PAGE 128
the beginning of the tape. See Appendix B for information on the tape drive operation. 2. Put the control panel’s upper key switch in the Enable position, and type CTRL/P at the console terminal to put the terminal in console mode (see Section 5.3). 3. If you wish to save the contents of a secondary processor’s EEPROM, first make it the boot processor using the SET CPU command. (See Section 4.5 and Section 5.18.2.) 4. At the prompt, enter SAVE EEPROM.
PAGE 129
5.18 SET Commands SET commands allow you to change the configuration parameters on the boot device, primary processor, memory, and terminal, and to modify the output of the error messages. To store the new parameters in the processor’s EEPROM, the control panel’s lower key switch must be in the Update position. Some SET commands take effect immediately, but the changes will be lost at the next node or system reset if the EEPROM is not updated.
PAGE 130
This section describes the following SET commands: • SET BOOT • SET CPU • SET LANGUAGE • SET MEMORY • SET TERMINAL If you issue a set command and the control panel’s lower key switch is not in the Update position, you may receive the following error message: ?0040 Key switch must be at "Update" to update EEPROM. Despite the error message, the change completes and remains until the primary processor or system is reset.
PAGE 131
5.18.1 SET BOOT The SET BOOT command allows you to store a BOOT command by a nickname for easy reference. Then you can reference the full BOOT command by the nickname. The lower key switch on the control panel must be set to Update. Examples 1. ! Turn key switch to Update. >>> SET BOOT DIAG /XMI:D DU0 >>> ! This creates a saved boot specification called DIAG ! that boots the disk unit 0 from XMI node D. ! SHOW BOOT command displays all saved BOOT specifications.
PAGE 132
The SET BOOT command syntax is: SE[T] B[OOT] [] where is a 1- to 4-character name for the boot specification you are saving. The string is any legal set of BOOT command parameters and qualifiers that do not reference another saved boot specification. If you omit , you delete the saved boot specification (if any) associated with . The lower key switch on the control panel must be set to the Update position.
PAGE 133
5.18.2 SET CPU The SET CPU command allows you to specify a particular processor as the primary processor or designate its eligibility to become the primary processor. You can also disable a vector processor module. 5.18.2.1 Syntax and Qualifiers Table 5–10: SET CPU Command Qualifiers Qualifier Meaning /E[NABLED] /ALL Processor is included in the system configuration and is enabled to leave console mode. With the /ALL qualifier all processors are enabled to leave console mode.
PAGE 134
The SET CPU command syntax is: SE[T] C[PU] [/qualifier] [] where is the XMI node number of the processor to be affected. If you omit , the system uses the current processor. If you omit all qualifiers, the SET CPU command immediately causes the specified processor to become the primary processor. The console terminal is then connected to the new primary processor, and the next console prompt is generated by the designated processor.
PAGE 135
5.18.2.2 Examples Examples 1. >>> SET CPU/PRIMARY 1 ! The processor at XMI node 1 may become the ! primary processor at the next system reset. 2. >>> SE CPU 1 ! ! ! ! 3. >>> SET CPU/NOVECTOR_ENABLED 4 Processor at XMI node 1 immediately becomes the new primary processor. The next system prompt is generated from the processor at node 1. ! The vector processor attached ! to the scalar processor at node 4 ! is disabled.
PAGE 136
Table 5–11: SET CPU Command Qualifiers’ Effect After a System Reset Qualifier BPD Value at Next Reset1 /NEX[T_PRIMARY] B for boot processor; must be chosen the boot processor at the next system reset. All other CPUs show as D. /NOE[NABLED] D for disable; processor is not included in the configuration. /NOP[RIMARY] D for disable; can be only a secondary processor. /P[RIMARY] B if selected as the boot processor; E if it is a secondary processor.
PAGE 137
5.18.3 SET LANGUAGE The SET LANGUAGE console command changes the output format of the console error messages. The default is English error messages, as shown in Appendix H. Examples 1. ! ! >>> SET LANGUAGE INTERNATIONAL ! ! ! >>> CONTINUE ! $ ! $ ^P ! ?0002 ! ! ! Lower key switch must be in Update position to store change in EEPROM. All error messages now appear as numeric code only, with no English explanation. Continue in program mode. A CTRL/P changes to console mode.
PAGE 138
The SET LANGUAGE command syntax is: SE[T] LANG[UAGE] where is a required value from Table 5–12. The SET LANGUAGE command suppresses English explanations of a command. The default setting is to provide complete information with the error message.
PAGE 139
5.18.4 SET MEMORY The SET MEMORY command is used to override the system default for interleaving memory. The command takes effect after the next system reset. Examples 1. 2. >>> SET MEMORY/I:(9+7+6+5, 8, A) ! Explicitly specifies what is created ! as the system memory configuration. ! Four memories are in one set, and 8 and A ! are each in an interleave set of their own. ! Used to exclude a memory from the configuration.
PAGE 140
The console program automatically interleaves the memory modules to give the largest possible set. The SET MEMORY command allows you to override the default. This command modifies the configuration stored in the EEPROM. The new configuration takes effect the next time the system is reset or powered up. An interleave set consists of memory modules in one-, two-, four-, or eightway configurations. Up to eight interleave sets can be configured.
PAGE 141
5.18.5 SET TERMINAL The SET TERMINAL command sets the characteristics that are stored for the console terminal. Example >>> SHOW TERMINAL /SCOPE /SPEED: 1200 ! Enter SHOW TERMINAL. /BREAK ! System responds with ! the parameters stored for ! /SCOPE, /SPEED, and /BREAK. >>> SET TERM/HARDCOPY /SPEED:9600 ! ! ! >>> SHOW TERM ! /HARDCOPY /SPEED: 9600 /BREAK ! ! SET TERM changes system parameters. Enter the command. System displays the parameters you set.
PAGE 142
The SET TERMINAL command syntax is: SE[T] T[ERMINAL] [/qualifiers] The character format for the SET TERMINAL command is always eight bits—no parity, one stop bit. This command immediately changes the specified parameter. The new value is stored in the EEPROM if you have the lower key switch set to Update. The EEPROM defaults are /SCOPE, /SPEED:1200, and /BREAK.
PAGE 143
5.19 SHOW The SHOW command displays the current value of parameters specified in a SET command and other configuration information about the system. Examples 1. >>> SHOW ALL Type 1+ KA65A 9+ MS65A D+ CIXCD E+ DEMNA Rev 0006 0084 1652 0601 (8080) (4001) (0C05) (0C03) ! Lists all system parameters, ! beginning with the system ! configuration. Current Primary: 1 /NOENABLED/NOVECTOR_ENABLED/NOPRIMARYF 2. E D C B A ! Shows the status of CPUs ! Models 400 and 500 only 9 8 7 . . . . . A1 . . . . .
PAGE 144
The SHOW command syntax is: SH[OW]