NAME

vaxops − VAX-11/780 console operations

DESCRIPTION

The procedures described here include the major operational sequences involved in running UNIX on the VAX-11/780 system.  The following notation is used:

1.  Special characters are enclosed in <> (e.g., <ctl> represents the “control” key, and <cr> stands for the “carriage return” key). 

2.  Items within {}s are mandatory substitutions. 

DAILY PROCEDURES

Disk Boot

This procedure can be used only on a system with a floppy disk updated for use with UNIX.  If the floppy disk has not been so updated, the sequences shown below under UNIX Floppy Update must be performed. 

When the system is first turned on, the console prompt >>> is printed.  If UNIX has been shut down, but not halted (see Bringing the System Down), the operator must type <ctl>p to get into console mode.  After the prompt, type H<cr> to halt the system. 

With the system halted, any of the console commands may be executed as described below under Console Operation.

To boot the stand-alone shell (sash) the operator types B<cr>.  The following is an example of this operation as seen on the console, picking up after the <ctl>p:

>>>H<cr>
HALTED AT nnnnnnnn

>>>B<cr>
CPU HALTED
INIT SEQ DONE
HALT INST EXECUTED
HALTED AT nnnnnnnn
LOAD DONE, nnnnnnnn BYTES LOADED

$$

The $$ prompt indicates that the stand-alone shell (sash) is ready to accept commands. If it is desired to run stand-alone fsck(1M) (or other stand-alone functions), this is the time to do it. The commands have the form /stand/program where program can be any name from a limited list of UNIX commands found in the directory /stand.  To perform a file system consistency check, type:

$$ /stand/fsck /dev/rp0

To bring up UNIX, the operator must type unix<cr>.  The system will come up through init 1 (see init(8)).

This is the appropriate time to do file system backups, and fsck(1M) should be executed if it was not executed in the stand-alone section of the boot. One must never operate the system with a defective file system.

After successful completion of fsck(1M) and setting the date and time (see date(1)), the operator can bring the system to multi-user operation by executing init 2. 

Bringing the System Down

The shutdown procedure is designed to gracefully turn off all processes and bring the system back to single user state with all buffers flushed.  To do this the operator can execute shutdown(1M) or the following sequence of commands:

killall
sync
init 1
fsck (optional)

The system may then be halted by typing the <ctl>p and H<cr> sequence. 

System Dumps

After a system crash, the following procedure should be used to get a system dump on tape. 

1.  Mount a tape with write ring and bring it on-line. 

2.  Enter console mode with <ctl>p. 

3.  After the >>> prompt, halt the system with H<cr>. 

4.  Issue the following command sequence, each command followed by <cr>:

E R0/N:F (Examine R0 thru R15)

E SP (Get the stack pointer for the next command)

E/V @/N:3F (Examine virtual memory beginning at the address from the previous instruction, and continuing for the next 63 locations; i.e., examine the stack)

ST 400 (Start execution at 400, i.e., dump to tape)

5.  Before returning to UNIX, execute the stand-alone fsck(1M).

System Faults

On occasion, the UNIBUS or its devices fail in such a manner as to flood the console with error messages and suspend operations on UNIBUS devices.  It may be possible under these conditions to bring the system down gracefully from an internal point-of-view, by inhibiting UNIBUS interrupts and running a normal shutdown.  The following sequence can be executed:

<ctl>p
>>>H
>>>E 20006004(Look at UBA control register)
>>>D ∗ 1(Clear the UBA)
>>>C(Return to UNIX)

You should now be able to login as root and run a normal shutdown sequence.  Reboot the system by normal means, ensuring fsck(1M) is performed.

INSTALLATION BOOT PROCEDURES

Tape Boot

The floppy disk delivered with the VAX-11/780 does not have tape-boot capability.  The user must type in the following program to read the first record on tape drive 0.  Type <cr> at the end of each input line:

>>>H
>>>U
>>>I

INIT SEQ DONE

>>>D 20000 20008FD0
>>>D + D0502001
>>>D + 3204A001
>>>D + C003C08F
>>>D + A0D40424
>>>D + 8FD00C
>>>D + C0800000
>>>D + 8F320800
>>>D + 10A0FE00
>>>D + C007D0
>>>D + C039D004
>>>D + 400
>>>S 20000(Start tape load)

HALT INST EXECUTED
HALTED AT 0002002F

>>>S 2(Execute boot program loaded from tape)

From this point the loader initiates a question and answer sequence to control the remainder of the load process. 

Disk Boot

The floppy disk delivered with the VAX-11/780 does not have UNIX disk-boot capability.  The user must type in the following program to read the first block on disk drive 0.  Type <cr> at the end of each line. 

>>>H
>>>LINK(Save the following sequence on the floppy)
(The prompt should change to <<<)
<<<H
<<<U
<<<I
<<<D 20000 00009FDE     (Boot program for MBA 0, drive 0)
<<<D + D0512001
<<<D + D004A101
<<<D + 0400C113
<<<D + 10008F32
<<<D + D40424C1
<<<D + 8FD00CA1
<<<D + 80000000
<<<D + 320800C1
<<<D + A1FE008F
<<<D + 28C1D410
<<<D + 14C1D404
<<<D + C139D004
<<<D + 00000400
<<<S 20000
<<<S 2
<<<<ctl>C(Exit LINK mode)
>>>

You are now ready to boot UNIX.  Each time it is necessary to boot (or reboot) UNIX, simply follow the sequence:

>>>P<cr> (Execute the commands saved in floppy link file; the console should echo each command in the file.)

$$ unix<cr> (Load and execute /unix)

UNIX Floppy Update

To update the console floppy for UNIX operation, one must have brought UNIX up by one of the initial-load procedures described above.  The following sequence can then be executed. 

# cd /stand/conflp
# sh update

Update prints commentary during the update operation indicating the files that are being replaced or added.  Finally, a new table of contents is printed and the available space is indicated. 

CONSOLE OPERATION

The following is condensed from Chapter 2 of the VAX-11/780 Hardware Handbook, DEC, 1978. 

The following are the standard console commands.  The most abbreviated form is shown in parentheses. 

<ctl>P Causes console to exit Program I/O mode (talking to the VAX-11/780 program).  This does not halt the VAX CPU. 

<ctl>U Deletes the current input line. 

<del> Deletes the previous character. 

<ctl>C Interrupts printout. 

(HE)LP Prints “help” file of which this is a part. 

(E)XAMINE {address}
Displays 8-digit hexadecimal address and its contents. See “help” file for qualifiers.

(D)EPOSIT {address} {data}
Enters data to address.

(I)NITIALIZE Initializes CPU. 

(U)NJAM Unjams the SBI. 

(SH)OW Displays console and CPU state. 

(H)ALT Halts execution of VAX CPU instructions. 

(S)TART {address}
Initializes CPU, enters address to PC, issues CONTINUE to CPU, and puts console into Program I/O mode. 

(C)ONTINUE Starts execution of VAX CPU instructions. 

(SE)T (T)ERMINAL (P)ROGRAM
Puts console into Program I/O mode. 

@{file} Causes the named floppy file to be printed and executed. 

WARNINGS

Only <ctl>p can be executed from Program I/O mode.  It does not stop the VAX CPU from running.  Only HALT can be executed while the VAX CPU is running and not in Program I/O mode; therefore, the sequence to stop the VAX-11/780 while running UNIX (Program I/O mode) is:

<ctl>p
>>>H<cr>

FILES

/etc/shutdown
/stand/∗

SEE ALSO

fsck(1M), shutdown(1M), filesave(8), init(8), tapeboot(8). 

May 16, 1980  —  VAX-11/780 only