System Startup, Configuration, and Shutdown Reference Manual (32650-90892)

Chapter 2 33
Initiating System Activity
The Booting Process
Console IO Dependent Code (IODC) revision 4
Boot IO Dependent Code (IODC) revision 4
Soft Booted.
MMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
ISL booting START AUTO
,
.
,
In Example 2-5, autoboot must be turned on, and an autoboot file (also known as an
autoexecute file) must reside in the logical interchange format (LIF) directory for ISL to
autoboot. If not, you get the message Cannot find an autoexecute file. AUTOBOOT
ABORTED. For information on turning on autoboot, refer to Chapter 3 , “System Startup
Functions.” For information on replacing autoboot files using SYSGEN, refer to Chapter 8 ,
“Modifying System File Configurations.”
Interrupting an Autobooting System
Even with the autoboot sequence in effect, you can override it to select an alternate boot
medium (for example, a tape drive or another disk drive), to activate a different ISL utility,
or to enter a different set of options. This is accomplished by pressing any key within 10
seconds after receiving the message that autoboot has been enabled.
Example 2-4 provides a partial listing of an interrupted autoboot sequences for an N-Class
system. Other systems may display different messages and boot paths.
Example 2-4. Interrupting Autobooting an N-Class System.
TC
Execution of this command irrecoverably halts all system processing and
I/O activity and restarts the computer system.
Type Y to confirm your intention to restart the system: (Y/[N]) y
y
-> SPU hardware was successfully reset.
. . . .
Processor Speed State CoProcessor State Cache Size
Number State Inst Data