1. Manuals
  2. Brands
  3. Digital Equipment Manuals
  4. Desktop
  5. digital VAX 8200
  6. Operation manual

Digital Equipment digital VAX 8200 Operation Manual

Openvms systems
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
OpenVMS Systems Operations Guide:
VAX 8200 and VAX 8300 Systems
EK–V8283–OG. A01
Digital Equipment Corporation

Advertisement

Table of Contents
loading

Related Manuals for Digital Equipment digital VAX 8200

Summary of Contents for Digital Equipment digital VAX 8200

  • Page 1 OpenVMS Systems Operations Guide: VAX 8200 and VAX 8300 Systems EK–V8283–OG. A01 Digital Equipment Corporation...
  • Page 2 February, 1993 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.

  • Page 3: Table Of Contents

    Contents About This Guide Console Subsystem Introduction ........1–1 Console Terminal .
  • Page 4 iv Contents System Shutdown Procedures Orderly Shutdown with SHUTDOWN.COM ... . . 3–1 Emergency Shutdown with CRASH Commands ... 3–1 System Backup Procedures Introduction .

  • Page 5: About This Guide

    About This Guide This document is a quick reference guide of basic systems operations for VAX 8200 and VAX 8300 systems. It summarizes such system tasks as booting and console operation as they relate to VAX 8200 and VAX 8300 systems.

  • Page 7: Console Subsystem

    Console Subsystem 1.1 Introduction The console subsystem provides the means to control and monitor system operations and to examine and deposit data in memory or processor registers. The console subsystem consists of the following: • Console terminal • Control panel •...

  • Page 8: Control Panel

    1–2 Console Subsystem Figure 1–1 shows the control panel. Refer to Tables 1–1 to Table 1–4 for descriptions of the two keylock switches, the three indicator lights, and the restart push button. Figure 1–1 Control Panel Standby Enable Battery Secure Fault Update Halt...

  • Page 9: Lower Keylock Switch Settings

    Console Subsystem 1–3 Table 1–2 Lower Keylock Switch Settings Setting Meaning Update When the lower keylock switch is set to Update, the corresponding indicator light glows red. You can change data in the Electrically Erasable Programmable Read-Only Memory (EEPROM) using the EEPROM utility. Halt When the lower keylock switch is set to Halt, the corresponding indicator light glows yellow.

  • Page 10: Restart Push Button Functions

    1–4 Console Subsystem Table 1–4 Restart Push Button Functions Upper Keylock Lower Keylock Switch Setting Switch Setting Restart Button Function Enable Autostart Runs self-test and reboots the OpenVMS operating system Enable Update or Halt Runs self-test Stand by or Secure Any position Disabled...

  • Page 11: Console Dual-Diskette Drive

    Console Subsystem 1–5 1.4 Console Dual-Diskette Drive The RX50, a dual-diskette drive, is located on the front of the system cabinet. The diskette drive is mounted vertically on some processors and horizontally on others. On a vertical drive, the left diskette drive is referred to as CSA1, and the right diskette drive as CSA2.

  • Page 12: Inserting A Diskette Into Csa2

    1–6 Console Subsystem 3. If there is a diskette in the drive, remove it gently, taking care not to touch any exposed platter surfaces. Place the diskette in a paper envelope. 4. Remove the diskette to be inserted from its paper envelope; do not touch any exposed platter surfaces.

  • Page 13: Console Command Language

    Console Subsystem 1–7 1.5 Console Command Language The console subsystem runs in two different modes: program mode and console mode. Program mode When the console subsystem is in program mode, the OpenVMS operating system is running and the dollar sign prompt ( $ ) is displayed. You can enter DCL commands, run programs, and receive system messages.

  • Page 14: Most Commonly Used Console Mode Commands

    1–8 Console Subsystem Table 1–5 Most Commonly Used Console Mode Commands Command Definition BOOT Executes a console command procedure that loads a VAX software program into memory. The console command procedure then transfers control to the program in memory and puts the console subsystem in program mode. During the installation procedure, use the abbreviation, B, for the BOOT command.

  • Page 15: System Boot Procedures

    System Boot Procedures 2.1 Introduction Booting is the process of loading system software from the system disk into the processor’s memory. VAX 8200 and VAX 8300 systems use the BOOT command and boot command procedures to perform this operation. The method selected to boot the system depends on whether the system disk is on a local drive or on an HSC drive.

  • Page 16: Boot Command Procedures

    2–2 System Boot Procedures NOTE If you plan to boot from a UDA50 supported device, you must keep in mind when you configure the system that the maximum unit number that can be booted is 15 (hexadecimal F). 2.2 Boot Command Procedures A boot command procedure does the following: •...
  • Page 17 System Boot Procedures 2–3 1. Make sure that the console RX50 is in console diskette drive CSA1. 2. To connect the console drive to the system, enter the following commands and press Return after each one: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN>...

  • Page 18: The Boot58 Program

    2–4 System Boot Procedures 2.3 The BOOT58 Program You can use the BOOT58 program, which is located on the console RX50, to boot the OpenVMS operating system from an HSC drive. You also can use the BOOT58 program to boot the OpenVMS operating system from a local drive when the boot block on the system disk becomes corrupted.
  • Page 19 System Boot Procedures 2–5 Table 2–1 (Continued) BOOT58 Commands Command Function EXAMINE [loc-qual] Displays the contents of the specified location. [,size-qual] location The location is interpreted according to the location and size qualifiers. The location qualifier can be expressed as follows: general register internal processor register physical memory...

  • Page 20: Booting From A Local Drive

    2–6 System Boot Procedures 2.4 Booting from a Local Drive There are several ways to boot the system from a local drive. You can perform an automatic boot from the default boot device designated in the EEPROM. You also can perform a manual boot. In either case you do not need a boot command procedure.

  • Page 21: Manual Boot

    System Boot Procedures 2–7 2.4.2 Manual Boot When you want to boot from a drive other than the one designated in the EEPROM, do a manual boot. To perform a manual boot from a local drive, use the following procedure: 1.

  • Page 22: Creating Auxiliary Boot Command Procedures

    2–8 System Boot Procedures • DU41 is the boot name for the RA80 series disk drive. DU is the device code for an RA80 series disk drive, 4 is the VAXBI node identification number, and 1 is the unit number. NOTE If the boot block on the system disk becomes corrupted, boot from a local drive attached to the KDB50 disk controller using...
  • Page 23 System Boot Procedures 2–9 3. Use the Exchange Utility to copy KDBBOO.CMD from the console RX50 to your current directory on the system disk. Enter the following command and press Return: $ EXCHANGE COPY CSA1:KDBBOO.CMD *.* 4. Edit KDBBOO.CMD. Enter the following command and press Return: $ EDIT KDBBOO.CMD KDBBOO.CMD contains the following text: ! KDBBOO.CMD : Boot command file to boot a VAX 8200 from a KDB50...
  • Page 24 2–10 System Boot Procedures 6. Edit KDBBOO.GEN. Enter the following command and press Return: $ EDIT KDBBOO.GEN a. In the first line of the command procedure, change the name KDBBOO.CMD to KDBBOO.GEN. b. Delete the comment character ( ! ) that appears before the D/G 5 command and replace r with the number of the correct root directory from which to boot.

  • Page 25: Using Auxiliary Boot Command Procedures

    System Boot Procedures 2–11 2.4.4 Using Auxiliary Boot Command Procedures You should boot the OpenVMS operating system using an auxiliary boot command procedure when the boot block on the local system disk becomes corrupted. To boot using an auxiliary boot command procedure, use the following procedure: 1.

  • Page 26: Writing A New Boot Block On A Local System Disk

    2–12 System Boot Procedures 2.4.5 Writing a New Boot Block on a Local System Disk This section discusses using the Writeboot utility (WRITEBOOT) to write a boot block on a local system disk. NOTE The LOG_IO privilege is required to use WRITEBOOT. To write a boot block on the local system disk, do the following: 1.
  • Page 27 System Boot Procedures 2–13 The Writeboot utility may display one or more of the following error messages: You lack LOG_IO privilege Explanation: This message means you do not have the correct privilege to use the Writeboot Utility. You lack READ and/or WRITE access to TARGET DEVICE: DISMOUNT and REMOUNT Explanation: This message means that access to the target device is limited.

  • Page 28: Booting From An Hsc Drive

    2–14 System Boot Procedures 2.5 Booting from an HSC Drive The first time you boot the OpenVMS operating system, use the procedure described in Section 2.5.1. Then create default boot command procedures, DEFBOO.CMD and DEFBOO.GEN, as described in Section 2.6. Use these boot command procedures to perform subsequent boots as described in Section 2.6.1 and Section 2.6.2..
  • Page 29 System Boot Procedures 2–15 6. To start the BOOT58 program, enter the following command and press Return: >>> B/R5:800 CSA1 7. Deposit the VAXBI node number into register 1, using the following format: BOOT58> D/G 1 node-number For example, if the VAXBI is node number 6, enter the following command and press Return: BOOT58>...
  • Page 30 2–16 System Boot Procedures For example, if you are booting the OpenVMS operating system from SYS2, enter the following command and press Return: BOOT58> D/G 5 20000000 11. To boot the system disk, enter the following command and press Return: BOOT58>...

  • Page 31: Creating Default Boot Command Procedures

    System Boot Procedures 2–17 2.6 Creating Default Boot Command Procedures To boot the system, you can enter the BOOT command and specify the boot name for a particular drive. You also can create default boot command procedures that boot the system automatically. There are two default boot command procedures: DEFBOO.CMD and DEFBOO.GEN.
  • Page 32 2–18 System Boot Procedures 6. Use the Exchange utility to copy CIBOO.CMD and CIBOO.GEN to the system disk. Enter the following commands and press Return after each one: $ EXCHANGE COPY CSA1:CIBOO.CMD *.* $ EXCHANGE COPY CSA1:CIBOO.GEN *.* 7. The code in CIBOO.CMD and CIBOO.GEN is nearly identical. CIBOO.CMD contains the following text: !CIBOO.CMD :Boot command file to boot a VAX 8200/8300 from an HSC disk.
  • Page 33 System Boot Procedures 2–19 Delete the comment character ( ! ) that appears before the D/G 3 command and replace u with the unit number of the HSC drive from which you will boot the OpenVMS operating system. Use hexadecimal notation. d.

  • Page 34: Booting With Defboo.cmd

    2–20 System Boot Procedures 2.6.1 Booting with DEFBOO.CMD You can cause the system to boot using DEFBOO.CMD when you do any of the following: NOTE The default boot device must be the local drive, CSA1. To change the designation of the default boot device in the EEPROM, see the hardware documentation for your system.

  • Page 35: Conversational Boot

    System Boot Procedures 2–21 2.7 Conversational Boot A conversational boot is used most commonly in research and development environments or 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 36 2–22 System Boot Procedures The procedure displays several questions that you must answer to complete the shutdown. When the procedure asks if an automatic system reboot 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 4.

  • Page 37: Hsc Drive

    System Boot Procedures 2–23 2.7.2 HSC Drive To perform a conversational boot from a system disk on an HSC drive, use the following procedure: 1. Make sure the console RX50 is in console diskette drive CSA1. 2. Set the top keylock switch to Enable and the bottom keylock switch to Halt.

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

    2–24 System Boot Procedures 2.8 Booting from a Different Directory on the System Disk The OpenVMS operating system is installed on the system disk in the root directory named [SYS0]. You can use VMSKITBUILD, described in the Guide to Setting Up a VMS System, to add a copy of the OpenVMS operating system to another root directory on the system disk.
  • Page 39 System Boot Procedures 2–25 For example, if the directory is named [SYSC], enter the following command and press Return: $ RENAME DEFBOO.CMD SYSCBOO.CMD 6. Use the Exchange utility to copy SYSnBOO.CMD to the console RX50. Use the following format: $ EXCHANGE COPY SYSnBOO.CMD CSA1:SYSnBOO.CMD For example, if the file name is SYSCBOO.CMD, enter the following command and press Return: $ EXCHANGE COPY SYSCBOO.CMD CSA1:SYSCBOO.CMD...
  • Page 40 2–26 System Boot Procedures 6. Use the command procedure you created to boot from the different directory. For example, to boot from [SYSC], enter the following command and press Return: BOOT58> @ SYSCBOO.CMD...

  • Page 41: Booting From Sysf During An Upgrade

    System Boot Procedures 2–27 2.9 Booting from SYSF During an Upgrade To boot from [SYSF], create and then invoke the command procedure named SYSFBOO.CMD, as follows: 1. Make sure that the console RX50 is in console diskette drive CSA1. 2. To connect the console drive, enter the following commands and press Return after each one: $ RUN SYS$SYSTEM:SYSGEN SYSGEN>...
  • Page 42 2–28 System Boot Procedures To boot from [SYSF] during an upgrade, use the following procedure: 1. Make sure the console RX50 is in console diskette drive CSA1. 2. Set the upper keylock switch to Enable and the lower keylock switch to Halt.

  • Page 43: System Shutdown Procedures

    System Shutdown Procedures 3.1 Orderly Shutdown with SHUTDOWN.COM To use the SHUTDOWN command procedure, log in to the SYSTEM account and enter the following command: $ @SYS$SYSTEM:SHUTDOWN To halt the system after the procedure completes, press Ctrl/P. 3.2 Emergency Shutdown with CRASH Commands NOTE Use CRASH commands only if the system is hung and you cannot log in to the SYSTEM account to use SHUTDOWN or OPCCRASH.
  • Page 44 3–2 System Shutdown Procedures >>> E/I 0 >>> E/I 1 >>> E/I 2 >>> E/I 3 >>> E/I 4 >>> E P >>> D P 041F0000 >>> D/G F FFFFFFFF >>> C CRASH commands display a fatal bugcheck message as well as additional messages and information.
  • Page 45 System Shutdown Procedures 3–3 Example 3–1 Sample CRASH Command Sequence Ctrl/P ?02 External Halt PC = 801A208D >>>E/I 0 00000000 7FFE7CE0 >>>E/I 1 00000001 7FFE9D88 >>>E/I 2 00000002 7FFED04E >>>E/I 3 00000003 0001FAC8 >>>E/I 4 00000004 80631200 >>>E P 04030004 >>>D P 041F0000 >>>D/G F FFFFFFFF >>>>C...

  • Page 47: System Backup Procedures

    System Backup Procedures 4.1 Introduction Use Standalone BACKUP to make a complete backup of the system disk. Standalone BACKUP is a version of the 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 48: Using Standalone Backup

    4–2 System Backup Procedures — If your system disk is fixed, back it up to a disk or magnetic tape. Then restore the files to the original system disk. Digital recommends that you use standalone BACKUP to back up your system disk.

  • Page 49: Installing Standalone Backup On The System Disk

    System Backup Procedures 4–3 4.3 Installing Standalone BACKUP on the System Disk You can install standalone BACKUP in any available root directory on the system disk from [SYS1] to [SYSE]. However, Digital has established [SYSE] as the standard directory for standalone BACKUP. To install standalone BACKUP in [SYSE], use the following procedure: 1.
  • Page 50 4–4 System Backup Procedures 4. Press Ctrl/P. 5. Enter the BOOT command in the following format: >>> B/R5:E0000000 [ddnu] where ddnu is the boot name of the drive holding the system disk. A boot name has the following format: ddnu where: •...
  • Page 51 System Backup Procedures 4–5 You need a special boot command procedure to boot standalone BACKUP from a system disk on an HSC drive. Digital recommends that you modify an existing boot command procedure. Ideally, this should be the default boot command procedure, DEFBOO.CMD. You can choose any unique name in the form xxxBOO.CMD for the command procedure you create.
  • Page 52 4–6 System Backup Procedures After you copy XEFBOO.CMD to the console RX50, you can use it to boot standalone BACKUP from a system disk on an HSC drive. To boot standalone BACKUP from SYSE on an HSC drive, use the following procedure: 1.
  • Page 53 System Backup Procedures 4–7 9. When standalone BACKUP finishes booting, it displays an identification message followed by the dollar sign prompt ( $ ): %BACKUP-I-IDENT, Standalone BACKUP V5.4; the date is 19-JUN-1990 15:00...

  • Page 54: Installing Standalone Backup On Floppy Diskettes

    4–8 System Backup Procedures 4.5 Installing Standalone BACKUP on Floppy Diskettes Digital recommends that you keep standalone BACKUP on floppy diskettes in case the system disk becomes damaged. You should have received standalone BACKUP on floppy diskettes as part of your OpenVMS distribution kit.
  • Page 55 System Backup Procedures 4–9 5. The procedure displays the following messages. Press Return (for YES) after each question. SYSGEN CONNECT CONSOLE was used to make the console device available. The standalone kit requires five floppy diskettes. The first four floppy diskettes contain the standalone OpenVMS system files, the last floppy diskette contains the BACKUP application image.
  • Page 56 4–10 System Backup Procedures 8. Insert the floppy diskette labeled S/A BKUP RX50 1/5 in the console diskette drive. When you are ready to continue, type Y and press Return. 9. The procedure mounts the floppy diskette, copies a set of system files, and displays a number of informational messages.

  • Page 57: Booting Standalone Backup From Floppy Diskettes

    System Backup Procedures 4–11 4.6 Booting Standalone BACKUP from Floppy Diskettes If the system disk containing standalone BACKUP should become unusable, you can boot standalone BACKUP from the RX50 floppy diskettes containing standalone BACKUP (either the set you received with your distribution kit or the set you created yourself, as described in Section 4.5).
  • Page 58 4–12 System Backup Procedures As you boot standalone BACKUP, place those floppy diskettes (five, in this example) successively in the console drive, as follows: 1. Make sure the console RX50 is in console diskette drive CSA1. 2. Set the upper keylock switch to ENABLE and the lower keylock switch to HALT.
  • Page 59 System Backup Procedures 4–13 7. Remove the console RX50 and insert the floppy diskette labeled S/A BKUP RX50 1/4 in console diskette drive CSA1. When you are ready to continue, type Y (for YES) and press Return. The procedure displays the following message: Resuming load operation on volume ’SYSTEM_1’, please stand by...
  • Page 60 4–14 System Backup Procedures Check the list of devices. If the list is incomplete, make sure that all the drives are connected properly to the system. See your hardware manuals for details. 13. The procedure displays the following messages: Please remove the volume "SYSTEM_4" from the console device. Insert the standalone application volume and enter "YES"...

  • Page 61: Backing Up The Console Rx50

    System Backup Procedures 4–15 4.7 Backing Up the Console RX50 Make a backup copy of the console RX50 to protect against corruption or loss of the original. First use CONSCOPY.COM to transfer the files on the console RX50 to a directory on the system disk. Then use CONSCOPY.COM to restore the files to a new floppy diskette.
  • Page 62 4–16 System Backup Procedures 6. The procedure asks for the name of the virtual disk that you want the files to be saved on. Press Return to select the default (SYS$DISK:CONSOLE.DSK). For example: Enter file name of virtual disk [default SYS$DISK:CONSOLE.DSK]: 7.
  • Page 63 System Backup Procedures 4–17 3. Press Return. The procedure displays the following messages: A SAVE operation involves copying the console medium to an RT-11 virtual volume, which is a Files-11 file that is an image of the RT-11 console volume. A RESTORE operation involves copying the entire contents of a virtual volume to a console medium.

This manual is also suitable for:

Digital vax 8300

Table of Contents