1. Manuals
  2. Brands
  3. Digital Equipment Manuals
  4. Desktop
  5. VAX 6000 Series
  6. Operation manual

Digital Equipment VAX 6000 Series Operation Manual

Openvms systems operations guide: vax 6000 systems
Hide thumbs Also See for VAX 6000 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation
OpenVMS Systems Operations Guide:
VAX 6000 Systems
EK–V6000–OG. A01
Digital Equipment Corporation

Advertisement

Table of Contents
loading

Related Manuals for Digital Equipment VAX 6000 Series

Summary of Contents for Digital Equipment VAX 6000 Series

  • Page 1 OpenVMS Systems Operations Guide: VAX 6000 Systems EK–V6000–OG. A01 Digital Equipment Corporation...
  • Page 2 The following are trademarks of Digital Equipment Corporation: CI, DEC, HSC, MSCP, OpenVMS, VAX, VAX 6000, VAXBI, VAXcluster, VMS, VT300, and the DIGITAL logo.

  • Page 3: Table Of Contents

    Contents About This Guide System Overview Introduction ........1–1 System Cabinet .
  • Page 4 iv Contents System Boot Procedures Booting from a Local Disk Drive ..... . 4–1 Booting from an HSC Disk Drive ..... . 4–2 Performing a Conversational Boot .
  • Page 5 Contents v Tables 1–1 Upper Keyswitch Settings ......1–5 1–2 Lower Keyswitch Settings ......1–5 1–3 Restart Button Functions .

  • Page 7: About This Guide

    About This Guide This document is a quick reference guide to basic VAX 6000 systems operations. It summarizes in one place basic information concerning such system tasks as booting and console operation as they relate to VAX 6000 systems. Intended Audience This guide is designed primarily for the following: •...

  • Page 9: Introduction

    System Overview 1.1 Introduction VAX 6000 systems are designed for growth and can be configured for many different applications. Each model in the VAX 6000 series: • Supports multiple users in a time-sharing environment • Supports a full range of VAX applications and operating systems •...

  • Page 10: System Cabinet

    1–2 System Overview 1.2 System Cabinet Figure 1–1 shows a typical VAX 6000 system cabinet configuration. Figure 1–1 Typical System System Optional Cabinet Storage Device VT300 Series Terminal LA75 Printer Manuals and Software GSF_000030_10_MPS The system cabinet may house a console load device, an XMI card cage (which contains the processors, memories, and I/O adapters), two optional VAXBI card cages, optional disk drives, and the system control panel.

  • Page 11: Console Terminal

    System Overview 1–3 1.3 Console Terminal The system console can be either a video or hardcopy terminal. The console provides the operator with the means to control and monitor system operations. You can also keep a record of an installation or upgrade either by using a hardcopy console terminal or by attaching a printer to the console video terminal (if it has that capability).

  • Page 12: Keyswitches

    1–4 System Overview Figure 1–2 Operator Control Panel Standby Enable Battery Secure Fault Update Halt Auto Start Restart GSF_000030_04_MPS 1.4.1 Keyswitches The upper keyswitch of the control panel controls system power on and power off operations. The lower keyswitch controls access to the console terminal and enables or disables automatic restart after a power failure.

  • Page 13: Upper Keyswitch Settings

    System Overview 1–5 Table 1–1 Upper Keyswitch Settings Position Effect Light Color Shuts off all power except to the battery backup. No light Standby Supplies power only to the power supply, blower, and memory. Used for system maintenance. Enable Supplies power to the whole system. You can Yellow use the console terminal in console mode, or use the Restart button.

  • Page 14: Restart Button Functions

    1–6 System Overview 1.4.2 Restart Button Depending on the position of the keyswitches, pressing the Restart button boots the system, runs self-tests, or does both. Table 1–3 describes various keyswitch settings and the corresponding function of the Restart button. NOTE The upper keyswitch must be in the Enable position for the Restart button to function.

  • Page 15: Status Indicators

    System Overview 1–7 1.4.3 Status Indicators There are three status indicator lights on the control panel: Run, Battery, and Fault. Table 1–4 describes the functions of these lights. Table 1–4 Status Indicator Lights Light Color State Meaning Green System is executing operating system instructions.

  • Page 16: System Architecture

    1–8 System Overview 1.5 System Architecture 1.5.1 Processor Nodes A processor node is a single-board scalar processor or a scalar/vector processor pair. The central processor unit (CPU) is comprised of two chips, one of which is a floating-point accelerator. A write-back cache subsystem improves system performance.

  • Page 17: System Operation

    System Operation 2.1 System Power-Up Power up the system by pushing in the handle on the H405 power controller. Then monitor the LED indications on the H7206 power and logic unit. The nine LEDs visible through the slot on the H7206 panel provide fault indications for the power regulators and for certain other faults such as overtemperature.

  • Page 18: System Boot

    2–2 System Operation Table 2–1 (Continued) H7206 Diagnostic LEDs Condition Color Meaning H7214 or H7242 installed incorrectly XMI-1 module in the XMI-2 card cage Fault (airflow, interlock, overtemperature) 2.2 System Boot The boot program reads the virtual memory boot program (VMB) from the boot device.

  • Page 19: System Shut-Down

    System Operation 2–3 2.3 System Shut-Down To halt the system after the procedure completes, press Ctrl/P. 2.3.1 Emergency Shutdown with CRASH Commands NOTE Use this emergency shutdown procedure only if the system is hung and you cannot log in to SYSTEM to use SHUTDOWN or OPCCRASH.
  • Page 20 2–4 System Operation 5. The system displays a fatal bugcheck message, and other messages, similar to the following: **** FATAL BUG CHECK, VERSION = 5.4 INVEXCEPTN, Exception while above ASTDEL or on interrupt stack CRASH CPU: 02 PRIMARY CPU: 02 ACTIVE/AVAILABLE CUP MASKS: 00000016/00000016 CURRENT PROCESS = NULL REGISTER DUMP...

  • Page 21: Console Commands

    Console Commands 3.1 Console Modes The console subsystem runs in two modes: program mode and console mode. Mode Console Function Program OpenVMS operating system controls the console subsystem. The Run light on the control panel glows. In program mode, you can enter DCL commands, run programs, and receive system messages.

  • Page 22: Command Language Syntax

    3–2 Console Commands Table 3–1 Console Control Characters Character Function Increments the console baud rate, if enabled. BREAK Causes the console to abort processing of a command. Ctrl/C Causes console to discard output to the console terminal until the Ctrl/O next is entered.
  • Page 23 Console Commands 3–3 Table 3–2 (Continued) Console Command Parameters Command Parameter Attribute or Action Qualifier(s) Can appear after the command keyword or after any symbol or number in the command; are preceded by a slash ( / ). Numbers Most appear in hexadecimal format. No characters Treated as a null command;...

  • Page 24: Console Command Summary

    3–4 Console Commands 3.4 Console Command Summary Table 3–3 lists the console commands. Table 3–4 describes the console commands used in this supplement. For more information on the console subsystem and the console commands, refer to the documentation supplied with the system. Table 3–3 Console Command List BOOT REPEAT...

  • Page 25: Boot Command Description

    Console Commands 3–5 3.5 BOOT Command Description The BOOT command syntax is: B[oot][/qualifier] [<parameter>] 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.

  • Page 26: Sample Console Session

    3–6 Console Commands 3.6 Sample Console Session #123456789 0123456789 0123456789 0123456789 012345# NODE # V- -P 256 Mb Console = V1.00 RBDs = V1.00 EEPROM = 1.00/1.00 SN = SG01234567 >>> EX/N:3 R0 G 00000000 FFFFFFFF G 00000001 E0140648 G 00000002 00000000 G 00000003 00000010...
  • Page 27 Console Commands 3–7 At power-up, the system performs self-test and displays the results. The TYP line in the sample self-test display indicates that XMI slot 5 is a vector processor attached to the scalar processor at node 4. The dashed lines indicate that the vector processor (V-) and the scalar processor (-P) are paired.

  • Page 29: System Boot Procedures

    System Boot Procedures 4.1 Booting from a Local Disk Drive To boot the system from a local disk, enter the BOOT command in the following format: >>> BOOT [/R5:a] /XMI:b /BI:c [/R3:d] DUu Table 4–1 lists the BOOT command qualifiers. Table 4–1 Boot Command Qualifiers (Local Disks) Qualifier Function...

  • Page 30: Booting From An Hsc Disk Drive

    4–2 System Boot Procedures Example: The following command specifies to boot from a local disk with a unit number of 1. The disk is connected to VAXBI node 2 of XMI node 3. >>> BOOT/XMI:3/BI:2 DU1 4.2 Booting from an HSC Disk Drive To boot the system from an HSC disk drive, use the following procedure: 1.

  • Page 31: Boot Command Qualifiers (Hsc Disks)

    System Boot Procedures 4–3 Table 4–2 Boot Command Qualifiers (HSC Disks) Qualifier Function /R5:a Deposits a value (a) into R5. This value affects the execution of VMB.EXE. The /R5 qualifier is optional. /XMI:b Specifies the XMI node number (b) of the node being accessed. Defaults to the lowest numbered I/O device.

  • Page 32: Performing A Conversational Boot

    4–4 System Boot Procedures 4.3 Performing a Conversational Boot A conversational boot is most commonly used in research and development environments and during software upgrades. Perform a conversational boot when you want to stop the boot process before it completes. The boot process stops after it loads SYS$SYSTEM:SYSBOOT.EXE and displays the SYSBOOT>...

  • Page 33: Automatic Restart

    System Boot Procedures 4–5 4. To begin the conversational boot, enter the following command at the console-mode prompt (>>>): >>> BOOT /R5:1 /XMI:a /BI:b [/R3:c] [/NODE:d] DUu where: • a is the XMI node number of the system disk. • b is the VAXBI node number of the system disk.

  • Page 34: Warm Start

    4–6 System Boot Procedures 4.4.1 Warm Start If you set the lower keyswitch on your VAX 6000 series console to Auto Start, the system will restart automatically under the following conditions: • When the system power comes on after a power failure •...

  • Page 35: Booting From [Sysf] During An Upgrade

    System Boot Procedures 4–7 4.5 Booting from [SYSF] During an Upgrade In the future, you might want to upgrade to the most recent version of the OpenVMS operating system. During the upgrade procedure you must boot from the [SYSF] directory. To boot from [SYSF], do the following: 1.

  • Page 36: Booting From A Different Directory On The System Disk

    4–8 System Boot Procedures 4.6 Booting from a Different Directory on the System Disk The OpenVMS operating system is installed in the system root directory named [SYS0]. You can use VMSKITBLD, as described in the Guide to Setting Up a VMS System, to add a copy of the OpenVMS operating system to another system root directory on the system disk.
  • Page 37 System Boot Procedures 4–9 • e is the HSC node number of the node being accessed. The /NODE qualifier is not necessary if you are booting from a local disk. The HSC node number is in hexadecimal. You can deposit a maximum of two HSC node numbers (if two HSCs are available).

  • Page 38: Using Set Boot

    4–10 System Boot Procedures 4.7 Using SET BOOT Instead of entering the whole BOOT command every time you boot the system, you can equate the command to a ‘‘nickname.’’ Nicknames can be up to four characters long. To give a BOOT command a nickname, enter the SET BOOT command in the following format: >>>...

  • Page 39: If The System Does Not Boot

    System Boot Procedures 4–11 4.8 If the System does not Boot If the system does not boot because a hardware problem occurs, a question mark ( ? ) usually precedes the error message displayed on the console terminal. Examples of hardware problems are a read error on a disk drive or a console tape cartridge, or a machine check error.

  • Page 41: System Backup Procedures

    System Backup Procedures 5.1 Introduction Use standalone BACKUP to make a complete backup of the system disk. Standalone BACKUP is a subset of the OpenVMS Backup Utility that runs without the support of the entire OpenVMS operating system. You should back up the system disk for the following reasons: •...

  • Page 42: Using Standalone Backup

    5–2 System Backup Procedures 5.2 Using Standalone BACKUP Depending on the distribution media you received, standalone BACKUP exists either on a tape cartridge or a compact disc. You can install standalone BACKUP on the system disk (which Digital recommends because booting standalone BACKUP from the system disk saves time) using either of these media.
  • Page 43 System Backup Procedures 5–3 Answer the questions. When the procedure asks if an automatic system boot should be performed, press Return for NO. When the procedure is finished, it displays the following message: SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM 3.
  • Page 44 5–4 System Backup Procedures 5.2.3 Installing Standalone BACKUP on a Tape Cartridge You should have received standalone BACKUP on the tape cartridge or compact disc included in your distribution kit. Digital recommends that you keep a copy of standalone BACKUP on another tape cartridge in case the system disk, original distribution compact disc, or original distribution tape cartridge becomes damaged, or in case you need to make extra copies.
  • Page 45 System Backup Procedures 5–5 7. After you enter the name of the target device, the procedure displays several informational messages and the following message: Please place the scratch tape cartridge in drive _MUC6: This volume will receive the volume label SYSTEM. Enter "YES"...
  • Page 46 5–6 System Backup Procedures 5.2.4 Booting Standalone BACKUP from a Tape Cartridge If the system disk containing standalone BACKUP should become unusable, you can boot standalone BACKUP from a tape cartridge. Booting standalone BACKUP from a tape cartridge takes approximately 15 minutes.
  • Page 47 System Backup Procedures 5–7 6. If the console tape cartridge is in the console drive, remove it. Insert the tape cartridge that contains standalone BACKUP. When you are ready to continue, enter Y and press Return. Standalone BACKUP displays a message similar to the following: Resuming load operation on volume ’SYSTEM’, please stand by...

  • Page 48: Booting Standalone Backup From A Remote Compact Disc

    Ethernet based InfoServer system equipped with RRD40 compact disc drives. To make sure your VAX 6000 series system has this capability, review all relevant cover letters and the OpenVMS Release Notes.
  • Page 49 find which systems are generating specific messages. 6. To boot standalone BACKUP on a VAX 6000 series system from across the Ethernet, enter the following command, specifying the XMI and VAXBI values displayed previously by the SHOW ETHERNET command.
  • Page 50 EEPROM = 1.00/1.00 SN = NIO128 Loading system software. (Note that ROM version numbers will be different for VAX 6000 series systems with upgraded console ROMs.) 8. After the system displays its self-test message, it prompts you for a file name, as follows: Filename: 9.
  • Page 51 System Backup Procedures 5–11 11. Continue the procedure by entering 3 (for Function ID item number 3, Choose Service) and then pressing Return: Enter a function ID value: 3 The next display is as follows: Service options: 1 = Find Service 2 = Enter Known Service Name =>...
  • Page 52 5–12 System Backup Procedures 13. To boot standalone BACKUP from the OpenVMS Version 5.4 distribution compact disc, enter 2 and then press Return: Servers found:: 1 VMS054 DIS_08002b150589 08-00-2b-15-05-89 Enter a number =>2 14. The procedure asks you for the date and time. Enter the date and time using the 24-hour clock format and press Return.

  • Page 53: Index

    Index ANALYZE/CRASH command, 2–4 Cold start, 4–6 Automatic restart, 4–5 Compact disc cold start, 4–6 booting standalone BACKUP warm start, 4–6 from, 5–8 Console control panel, 1–3 sample session, 3–6 to 3–7 Backing up the system disk, 5–1 Console commands BACKUP command, 5–1 abbreviation of, 3–3 Backup Utility (BACKUP), 5–2...
  • Page 54 2 Index DEPOSIT console command, 3–4 Power-up procedure, 2–1 Program mode, 3–1 Ethernet using to boot standalone /R3 qualifier, 4–1, 4–2 BACKUP, 5–8 /R5 qualifier, 4–1, 4–2 EXAMINE console command, 3–4 Remote compact disc booting standalone BACKUP from, 5–8 Restart button, 1–6 RRD40 compact disc drive Hardware problem booting standalone BACKUP...
  • Page 55 Index 3 SYSBOOT.EXE, 4–4 qualifier used for, 4–1 System disk designating as default boot device, 4–6 Warm start, 4–6 Write-protection tape cartridge, 5–5 VMB (virtual memory boot), 2–2 VMSKITBLD, 4–8 Volume shadowing BOOT command qualifier used /XMI qualifier, 4–1, 4–2 for, 4–2...

Table of Contents