Document revision date: 19 July 1999

Boot the system disk manually as follows:

IF ...	THEN ...
the OpenVMS Alpha operating system is running,	go to step 1.
the OpenVMS Alpha operating system is not running,	go to step 4.

1. Log in to the SYSTEM account.
2. Enter the following command and press the Return key:

   $ @SYS$SYSTEM:SHUTDOWN

3. Answer the questions displayed by the system. When the procedure asks if an automatic reboot should be performed, press the Return key for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE

4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)
5. Enter the BOOT command in the following format:

   BOOT device-name

   
   Substitute the device name of the system disk for device-name. For example, to boot from a drive with a device name of DKA400, enter the following command and press the Return key:

   >>> BOOT DKA400

   
   To boot from the network, enter the following command and press the Return key:

   >>> BOOT ESA0

A conversational boot is most commonly used in research and development environments and during software upgrades. Perform a conversational boot to stop the boot process before it completes. The boot process stops after it loads SYS$SYSTEM:SYSBOOT.EXE and displays the SYSBOOT> prompt. At the SYSBOOT> prompt, you can enter specific OpenVMS System Generation utility (SYSGEN) commands to do the following:

• Examine system parameter values
• Change system parameter values
• Specify another parameter file
• Specify another system startup command procedure
• Select the default system parameter file if you modified system parameters to values that render the system unbootable
• Specify a minimum startup

There are several ways to perform a conversational boot. The following procedure is the most direct:

IF ...	THEN ...
the OpenVMS Alpha operating system is running,	go to step 1.
the OpenVMS Alpha operating system is not running,	go to step 4.

1. Log in to the SYSTEM account.
2. Enter the following command and press the Return key:

   $ @SYS$SYSTEM:SHUTDOWN

3. Answer the questions displayed by the system. When the procedure asks if an automatic reboot should be performed, press the Return key for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE

4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)
5. To begin the conversational boot, enter the BOOT command in the following format:

   BOOT -FLAGS 0,1 [device-name]

   
   Substitute the device name of the drive from which you want to boot for device-name. For example, if the system disk has a device name of DKA400, enter the following command and press the Return key:

   >>> BOOT -FLAGS 0,1 DKA400

   
   If you do not specify a device name, the system boots from the boot device assigned when you entered the SET BOOTDEF_DEV command.

6. At the SYSBOOT> prompt, you can enter any of the SYSGEN commands listed in Table A-1. For more information about these SYSGEN commands, see the OpenVMS System Management Utilities Reference Manual.
7. When you finish using the SYSGEN commands, enter the CONTINUE command to complete the boot process.

   Table A-1 SYSGEN Commands Used in the SYSBOOT Procedure

   Command	Description
   CONTINUE	Resumes the boot procedure.
   DISABLE CHECKS	Inhibits checking of parameter values specified with the SET command.
   ENABLE CHECKS	Permits checking of parameter values specified with the SET command.
   HELP	Displays a summary of the SYSBOOT commands on the terminal screen.
   SET parameter-name	Establishes the value of a system parameter.
   SET/STARTUP	Sets the name of the system startup command procedure.
   SHOW [parameter]	Displays active, current, default, maximum, and minimum values for specific parameters. (Use qualifiers to display characteristics of parameters grouped by categories.)
   USE [file-spec]	Specifies a parameter file to be used as a source of values. You must enter the entire file specification, including device and directory; you cannot specify a logical name.

For examples of using conversational booting, see Section A.1.4 and Section A.1.9.

A.1.4 Booting with Minimum Startup

In certain cases, you might want to boot your system without performing the full sequence of startup events. For example, if a startup event prevents you from logging in, you might want to boot the system without executing the startup so that you can log in and fix the problem. You can use the conversational boot to specify a minimum startup.

Boot the system with minimum startup as follows:

1. Perform a conversational boot by entering the following command at the console prompt:

   >>> BOOT -FLAGS 0,1 [device-name]

2. Enter the following command and press the Return key:

   SYSBOOT> SET STARTUP_P1 "MIN"

3. Enter the following command to continue booting:

   SYSBOOT> CONTINUE

4. After the system boots, log in and enter the following commands to invoke SYSMAN and clear the STARTUP_P1 parameter you set in step 2:

   $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET STARTUP_P1 "" SYSMAN> PARAMETERS WRITE CURRENT

The XDelta utility (XDELTA) is a debugging tool that system programmers use. The procedure for booting all Alpha computers with XDELTA is the same.

The following table describes the valid values you can specify when booting with XDELTA:

Value	System Response
0	Normal, nonstop boot (default).
1	Begins a conversational boot and then displays the SYSBOOT prompt.
2	Includes XDELTA but does not take the initial breakpoint.
3	Displays the SYSBOOT prompt and includes XDELTA but does not take the initial breakpoint.
6	Includes XDELTA and takes the initial breakpoint.
7	Includes XDELTA, displays the SYSBOOT prompt, and takes the initial breakpoint at system initialization.

The following is an example of booting with XDELTA from the console prompt:

>>> BOOT -FLAGS 0,7

For more information about using XDELTA, see the OpenVMS Delta/XDelta Debugger Manual.

A.1.6 Booting from a Different Directory

By default, the OpenVMS Alpha operating system is installed in the system root directory [SYS0]. However, if you have created a cluster system disk, you can use the SYS$MANAGER:CLUSTER_CONFIG.COM procedure to add a copy of the operating system to a different root directory. (See the OpenVMS System Manager's Manual for more information about using the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.)

To boot from a different directory (for example, [SYS3]), enter the BOOT command as follows:

>>> BOOT -FLAGS 3,0 DKA200

A.1.7 Booting with a PMAZB or PMAZC TURBOchannel Adapter

PMAZB and PMAZC TURBOchannel adapters are adapters that are software-compatible with the integrated SCSI ports on DEC 3000 Alpha series systems.

The DEC 3000 Alpha series system consoles implement the SHOW CONFIGURATION console command, which displays information about the TURBOchannel options and the built-in adapters in the system. When a PMAZB or PMAZC adapter is installed in the TURBOchannel, the SHOW CONFIGURATION command displays the "PMAZB-AA" or "PMAZC-AA" string, the TURBOchannel slot number, and the device status.

The DEC 3000 Alpha series consoles also implement the SHOW DEVICE command, which displays information about the devices in the system. Because the integrated SCSI adapter is built into every DEC 3000 Alpha series system, the SHOW DEVICE console command can display the SCSI devices connected to the integrated SCSI ports. However, the SHOW DEVICE console command cannot display the SCSI devices connected to the PMAZB or PMAZC SCSI ports.

To make the console display the devices connected to the PMAZB or PMAZC SCSI ports, enter the following command at the console prompt, where x is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed:

>>> TEST TCx CNFG

This command displays the devices that are connected to each SCSI port of the PMAZB or PMAZC adapter. The device controller letters are either A or B, based upon the PMAZB or PMAZC ports to which the devices are connected. Do not confuse these devices with any DKAxxx or DKBxxx devices displayed by the SHOW DEVICE command, which shows SCSI devices on the integrated SCSI ports only.

To boot from a device connected to a PMAZB or PMAZC adapter, enter the boot command as follows:

>>> BOOT "X/DKYzzz"

The following conventions are used:

• X is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed.
• DK is the device code of the boot device.
• Y is either A or B, depending on the SCSI port of the PMAZB or PMAZC adapter that contains the boot device.
• zzz is the SCSI unit number of the boot device.

The OpenVMS Alpha operating system does not distinguish between the PMAZB or PMAZC adapter and the integrated SCSI adapter. The operating system views them as identical adapters. Because the operating system searches for I/O adapters in backplane slot number order, device controller letters are assigned that correspond to the backplane order of the TURBOchannel options, followed by the integrated adapters. This is different from console SCSI device naming, which always designates SCSI devices on the integrated SCSI ports as either "A" or "B" port devices.

Example

On a DEC 3000 Model 500 Alpha system with no TURBOchannel options installed, the OpenVMS Alpha operating system names the integrated SCSI ports PKA0 and PKB0, and the devices connected to the ports inherit the controller letter from the port controller letter (A or B). However, if a PMAZB or PMAZC adapter is installed in the TURBOchannel, the operating system names the PMAZB or PMAZC SCSI ports PKA0 and PKB0 and names the integrated SCSI ports PKC0 and PKD0. The devices connected to the ports inherit the controller letter from the port controller letter (A, B, C, or D).

A.1.8 Booting Over the Network with an Alternate TURBOchannel Adapter

You can use an alternate TURBOchannel adapter to boot a DEC 3000 series Alpha computer (with the TURBOchannel option) over the network in an InfoServer or OpenVMS Cluster environment. Examples of alternate TURBOchannel adapters are the PMAD (which connects to the Ethernet) and the DEFTA (which connects to the FDDI).

To boot from a TURBOchannel device connected to one of these alternate adapters, enter the boot command as follows:

>>> BOOT "n/ESA0"

The value for n is the TURBOchannel slot number for the device, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. In the following example, the TURBOchannel slot number (listed under the "TCINFO" column) is 0:

>>> SHOW CONFIG DEC 3000 - M300 Digital Equipment Corporation VPP PAL X5.56-80800101/OSF PAL X1.34-80800201 - Built on 18-DEC-1996 11:376 TCINFO DEVNAM DEVSTAT ------ -------- -------- CPU OK KN16-AA -V3.2-S6CD-I151-sV2.0-DECchip 21064 P3.0-150 ASIC OK MEM OK MEM OK 6 CXT OK 5 NVR OK SCC OK NI OK ISDN OK 4 SCSI OK 0-PMAD-AA TC0

A.1.9 Booting in an Emergency

If a system problem prevents your system from booting, you might need to perform an emergency boot operation. Table A-2 summarizes these emergency boot operations, and the sections that follow describe each boot operation in more detail.

Table A-2 Emergency Boot Procedures

Operation	When to Use
Booting with default system parameters	When parameter values in the parameter file have been modified so that the system is unbootable
Booting without startup and login procedures	If an error in the startup or login procedures prevents you from logging in
Booting without the user authorization file	If you have forgotten the password and cannot log in to a privileged account

A.1.9.1 Booting with Default System Parameters

If the current values stored in the parameter file have been incorrectly modified, these incorrect values might cause the system to become unbootable. With a conversational boot operation, you can reset the active values for all system parameters to the default value. (In most cases, Compaq recommends that you use AUTOGEN to modify system parameters. In certain cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, see the OpenVMS System Manager's Manual.) The default values allow you to boot the system temporarily so you can correct the problem.

How to Perform This Task

1. Perform a conversational boot by entering the following command at the console prompt:

   >>> BOOT -FLAGS 0,1 [device-name]

2. At the SYSBOOT> prompt, enter the following command:

   SYSBOOT> USE DEFAULT

   
   This command specifies that default values should be used for all parameters.

3. Enter the following command to continue booting:

   SYSBOOT> CONTINUE

4. When the system finishes booting, determine which changed parameter caused the problem and reset the parameter value. If you specified the value for the parameter in the AUTOGEN parameter file MODPARAMS.DAT, fix the value in that file and run AUTOGEN. For more information, see the OpenVMS System Manager's Manual.
5. Shut down and reboot the system.

Example

SYSBOOT> USE DEFAULT SYSBOOT> CONTINUE Username: SYSTEM Password: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET NPAGEDYN 2999808 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ EDIT SYS$SYSTEM:MODPARAMS.DAT . . . [Insert the following line in MODPARAMS.DAT:] MIN_NPAGEDYN = 2999808 . . . $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT

A.1.9.2 Booting Without Startup and Login Procedures

If the system does not complete the startup procedures or does not allow you to log in, bypass the startup and login procedures. The startup and login procedures provided by Compaq should always work. However, if you introduce an error when modifying the startup or login procedures, it is possible to accidentally lock yourself out of the system.

How to Perform This Task

1. Perform a conversational boot by entering the following command at the console prompt:

   >>> BOOT -FLAGS 0,1 [device-name]

2. Enter the following command at the SYSBOOT> prompt:

   SYSBOOT> SET/STARTUP OPA0:

3. Enter the following command to continue booting:

   SYSBOOT> CONTINUE

4. When the system is booted, the operator console displays the DCL command prompt ($). You are logged in.
5. Enter the following DCL command:

   $ SET NOON

   
   This command directs the operating system to ignore any errors that might occur. If you do not enter this command and you invoke an error, the system will log you out.

6. Correct the error condition that caused the login failure. (That is, make the necessary repairs to the startup or login procedures, or to the SYSUAF.DAT file.)
   Invoke a text editor to correct the startup or login file. Note that some system consoles might not supply a screen-mode editor. You can also copy a corrected file and delete the incorrect version by using the RENAME and DELETE commands.
7. Invoke SYSMAN and enter the following commands to reset the startup procedure:

   $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $

8. Perform a normal startup by entering the following command:

   $ @SYS$SYSTEM:STARTUP

Example

SYSBOOT> SET/STARTUP OPA0: SYSBOOT> CONTINUE $ SET NOON $ SET DEFAULT SYS$SYSROOT:[SYSEXE] $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ @SYS$SYSTEM:STARTUP

	privacy and legal statement
6522PRO_011.HTML