HP 3000 Manuals HP 3000 Manuals
Starting the System
This section discusses using the initial system loader utility, START,
that activates the operating system.
START is the ISL utility used most often, whether to boot the system from
disk after a reset, to automatically reboot after the completion of the
UPDATE, INSTALL, or DUMP utility, or to bring up the operating system
after a shutdown.
START execution differs depending on the previously executed boot
command. For example, a START after an INSTALL executes differently than
a START after a shutdown or reset. START after an INSTALL may initialize
the system member volumes. A START option after an INSTALL or UPDATE
does not restart jobs.
There are, primarily, six load and start utilities for the operating
system.
* START or START RECOVERY
* START NORECOVERY
* UPDATE or UPDATE NOCONFIG
* UPDATE CONFIG
* INSTALL
* DUMP
Using START and its options
The ISL command for the START utility is START. The utility has several
options:
START [;GROUP=cgn] [;LOGON=acct] [{;RECOVERY }] [{;SINGLE-DISC}]
[{;NORECOVERY}] [{;MULTI-DISC }]
[{;SINGLE-USER}] [{;SYSSTART }]
[{;MULTI-USER }] [{;NOSYSSTART}]
Specify START alone or with alternate options. Separate the options from
the command and other options with a blank or semicolon.
Using the ISL START command without listing any options:
ISL> START
is the same as specifying the following default options:
ISL> START GROUP=bootup LOGON=OPERATOR.SYS RECOVERY&
MULTI-USER MULTI-DISC SYSSTART
NOTE bootup contains the CONFIG file that was used by the previous START
NORECOVERY command. RECOVERY starts the system, but sets the fence
at 14 which prevents any jobs or sessions from automatically
starting.
These default options instruct the system to boot from disk, to use the
configuration information last used to boot the system, attempts to log
on as OPERATOR.SYS (if the OPERATOR user has been created), to restart
all jobs and allow all users access to the system, to bring up all
volumes present on the system, and to execute commands found in the
SYSSTART file, SYSSTART.PUB.SYS.
Enter an alternate option through a keyword parameter, or several
alternate options in groups of keyword parameters. The following command
line shows an example of using multiple alternate options:
ISL> START GROUP=CONFG950 LOGON=JOHN.SMITH NORECOVERY&
SINGLE-USER SINGLE-DISC
Executing commands during system startup
The file SYSSTART.PUB.SYS executes automatically at system startup if the
SYSSTART parameter is specified in the START command. This file can be
used to set up the normal user environment automatically when the system
starts up. The contents of this file should include command parameters
appropriate for your environment, such as the standard limits for jobs
and sessions, spooler start commands, stream device identification,
outfence priorities, event logging, and so on. These commands are then
performed automatically for you whenever the system is restarted.
A SYSSTART file can contain selected MPE commands (and their parameters)
that the system manager is allowed to execute except networking commands.
(Networking commands should be executed from a job that is streamed from
SYSSTART, or from a logon UDC for OPERATOR.SYS.) You can use the
following commands in a SYSSTART file:
ACCEPT HEADOFF REFUSE
ALLOCATE HEADON STARTSESS
ALLOW JOBFENCE STARTSPOOL
ALTLOG JOBPRI STOPSPOOL
COMMENT JOBSECURITY STREAM
CONSOLE LDISMOUNT STREAMS
DEALLOCATE LIMIT SUSPENDSPOOL
DISALLOW LMOUNT TELL
DISCRPS LOG TELLOP
DOWN MRJECONTROL TUNE
DOWNLOAD OUTFENCE UP
VMOUNT
Create a SYSSTART file with any text editor. A properly formatted
SYSSTART file is composed of five modules, labeled and placed in the
following order: startup, warmstart, coolstart, update, and reload.
Notice that each module must be separated by one or more asterisks. The
following SYSSTART file sample is an example of the type of commands you
might want to include in a SYSSTART file. It is not intended to suggest
entries for your system's SYSSTART file.
_______________________________________________________
| |
| |
| STARTUP |
| STREAMS 10 |
| ALLOW @.@;COMMANDS=REPLY |
| ALLOCATE COBOLII.PUB.SYS |
| LIMIT 8,16 |
| JOBFENCE 6 |
| OUTFENCE 6 |
| OUTFENCE 12;LDEV=14 |
| FILE T;DEV=TAPE |
| *** |
| WARMSTART |
| STREAMS 10 |
| ALLOW @.@;COMMANDS=REPLY |
| ALLOCATE COBOLII.PUB.SYS |
| LIMIT 8,16 |
| JOBFENCE 6 |
| OUTFENCE 6 |
| OUTFENCE 12;LDEV=14 |
| FILE T;DEV=TAPE |
| *** |
| COOLSTART |
| STREAMS 10 |
| ALLOW @.@;COMMANDS=REPLY |
| ALLOCATE COBOLII.PUB.SYS |
| LIMIT 8,16 |
| JOBFENCE 6 |
| OUTFENCE 6 |
| OUTFENCE 12;LDEV=14 |
| FILE T;DEV=TAPE |
| *** |
| UPDATE |
| LIMIT 1,1 |
| JOBFENCE 14 |
| OUTFENCE 14 |
| STARTSESS 20;MANAGER.SYS/PASSWORD;HIPRI;NOWAIT |
| *** |
| RELOAD |
| LIMIT 1,1 |
| JOBFENCE 14 |
| OUTFENCE 14 |
| STARTSESS 20;MANAGER.SYS/PASSWORD;HIPRI;NOWAIT |
| |
_______________________________________________________
Example 3-4. A Properly Formatted SYSSTART File
The STARTUP module is executed whenever the SYSSTART file is accessed.
Place commands and parameters specific to an operation under the
appropriate heading. If, for instance, you do not wish users to be able
to log on immediately following an UPDATE (START) or INSTALL (START),
insert commands in the update and install modules to limit the jobs and
sessions and raise the jobfence. Table 3-2 describes how each module
is executed.
Table 3-2. Execution of SYSSTART File Modules
---------------------------------------------------------------------------------------------
| | |
| Boot Utility Used | SYSSTART Module Executed |
| | |
---------------------------------------------------------------------------------------------
| | |
| ANY | startup |
| | |
---------------------------------------------------------------------------------------------
| | |
| START (RECOVERY) | warmstart |
| | |
---------------------------------------------------------------------------------------------
| | |
| START (NORECOVERY) | coolstart |
| | |
---------------------------------------------------------------------------------------------
| | |
| UPDATE (START) | update |
| | |
---------------------------------------------------------------------------------------------
| | |
| INSTALL (START) | reload |
| | |
---------------------------------------------------------------------------------------------
The SYSSTART file must be created by MANAGER.SYS and needs to reside on
LDEV 1 to function properly. Once the file is created, use the following
commands to copy the file to the appropriate location:
HELLO MANAGER.SYS
FILE SYSSTART;DEV=1
FCOPY FROM=tempfilename;TO=*SYSSTART;NEW
If an error exists in the SYSSTART file, the startup process ignores it
and continues execution.
Starting a 900 Series HP 3000
The following steps comprise a procedure for booting MPE/iX on a 900
Series HP 3000 computer system using START following a reset.
To start the system, perform the following steps:
[REV BEG]
1. Power on all attached peripheral devices, and ensure that the
system disks are powered on.[REV END]
2. Place the console in control mode. Enter:
CTRL B
The console control mode prompt (CM>) should appear on the console
screen.
3. Reset the system using AP commands, boot from the primary path,
and enter the START command at the ISL prompt.
/need begin>[REV BEG]
_________________________________________________________________
NOTE If you have a 99X system, you must transfer to the service
processor before you reset the system.
_______________________________________
| |
| |
| CM> SP |
| |
_______________________________________
_________________________________________________________________
[REV END]
Examples 3-5 and 3-6 demonstrate the messages received at the
console of the 900 Series systems.
NOTE The components of the system startup messages on all of the systems
are similar; however, the messages can vary in I/O path
descriptions depending on the system.
____________________________________________________________________________
| |
| |
| CM> RS |
| |
| 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 |
| SPU hardware was successfully reset. (APMSG 02) |
| |
| Processor Dependent Code (PDC) revision 3.2 |
| |
| Console path = 4.2.0.0.0.0.0 |
| Primary boot path = 4.1.0.0.0.0.0 |
| Alternate boot path = 4.5.3.0.0.0.0 |
| |
| Enter boot path, command, or ?> 4.1 |
| |
| Booting. |
| |
| Console IO Dependent Code (IODC) Revision 4 |
| Boot IO Dependent Code (IODC) Revision 4 |
| |
| Interact with IPL (Y or N)?> Y |
| |
| HARD Booted. |
| |
| MMSAVE Version 2.2 |
| DUMPAREA found, save main memory to disc |
| ISL loaded |
| |
| ISL Revision A.00.28 July 15, 1993 |
| |
| ISL> START |
| MPE/iX launch facility |
| Initialize_genesis - Version : <<870204.1552>> |
| TUE, JUN 27, 1990, 4:15:24 AM (y/n)? Y |
| [TMUX_DAM] 15 7 12 14 |
| Initialize genesis completed. |
| Create Console Messages kso completed. |
| Initialize memory manager completed. |
| Initialize resident kernel completed. |
| |
____________________________________________________________________________
Example 3-5. Example of a Hard Reset from a Series 935 System
________________________________________________________________________________
| |
| |
| Initialize volume management and mount the System Disk |
| Initialize volume management completed. |
| Opening the native system library completed |
| Initialize loader completed. |
| I/O boot path managers frozen in memory completed. |
| Vsm make no longer resident completed. |
| Initialize process management completed. |
| Initialize debug subsystem completed. |
| Initialize file system completed. |
| Initialize temporary UID/GID Databases completed. |
| Initialize non-resident services completed. |
| Begin binding compatibility mode SL |
| Compatibility mode SL binding complete |
| Create port process has been completed. |
| |
| The following is a list of the boot options - |
| last boot command: START last configuration group: CONFIG |
| current boot command START current configuration group: CONFIG |
| last configuration group actually used by START: CONFIG |
| logon = OPERATOR.SYS |
| RECOVERY MULTI-USER |
| MULTI-DISK SYSSTART |
| |
| Begin launching additional processors: |
| . |
| . |
| . |
| Entering - System I/O configuration. |
| The path 4 has already been configured. |
| The path 4.1 has already been configured. |
| The path 4.1.0 has already been configured. |
| The path 4.2 has already been configured. |
| The path 4.2.0 has already been configured. |
| The path 4.5.3 was configured but is not available. |
| The path 4.5.4 was configured but is not available. |
| The path 4.5.5 was configured but is not available. |
| The path 4.5.6 was configured but is not available. |
| The path 4.6.0 was configured but is not available. |
| The path 4.6.5 was configured but is not available. |
| The path 4.6.6 was configured but is not available. |
| The path 4.6.7 was configured but is not available. |
| Leaving - System I/O configuration. |
| |
________________________________________________________________________________
Example 3-5. Example of a Hard Reset from a Series 935 System (continued)
_____________________________________________________________________________________
| |
| |
| SYSTEM I/O AT BOOT TIME |
| |
| ldev: 1 HP7937H configured available 4.1.0 |
| ldev: 2 HP7937H configured available 4.1.1 |
| ldev: 3 HP7937H configured available 4.1.3 |
| ldev: 4 HP7937H configured available 4.1.4 |
| ldev: 5 HP7937H configured not-available 4.6.5 |
| ldev: 6 HP2566A configured available 4.5.7 |
| ldev: 7 HP7980A configured available 4.5.0 |
| ldev: 10 HP7980A configured not-available 4.5.3 |
| ldev: 19 HP2680A configured not-available 4.5.5 |
| ldev: 20 HP2392A configured available 4.2.0 |
| ldev: 28 HP2688A configured not-available 4.5.6 |
| ldev: 29 HP2688A configured not-available 4.5.4 |
| |
| MEMORY AVAILABLE FOR USE (bytes): 3554432 |
| |
| Entering - Mount all volumes |
| Mounting MASTER on LDEV 1 |
| Mounting MEMBER on LDEV 2 |
| Mounting MEMBER on LDEV 3 |
| Mounting MEMBER on LDEV 4 |
| |
| START AGGREGRATE RECOVERY of MPEXL_SYSTEM_VOLUME_SET |
| SYSTEM RECOVERY COMPLETED for MPEXL_SYSTEM_VOLUME_SET |
| USERLOG RECOVERY COMPLETED for MPEXL_SYSTEM_VOLUME_SET |
| NO PARALLEL PROCESSES FOR MOUNT_ALL_VOLUMES |
| -- Time spent in MOUNT_ALL_VOLUMES 15 |
| Leaving - Mount all volumes |
| The current boot command has been saved on the system master. |
| NMLG FILE NUMBER 20 ON. |
| 14:04/23/DCC STARTUP - ENTER - version C0104504 compiled 930712 |
| 14:04/23/ WARNING: I/O config from last START RECOVERY will be used (DCCWARN |
| =100) |
| [NETWORK_DUMP_SURR] Version A.00.47.03A |
| 14:04/23/DCC STARTUP - OK |
| 14:05/40/NRJE CANNOT CONFIGURE LDEV 12 INTO THE I/O SYSTEM |
| 14:05/40/40DEVICE IS ALREADY CONFIGURED |
| 14:05/40/NRJE CANNOT CONFIGURE VIRTUAL READER FOR WSID: R20 |
| System State: Initializing Mode. |
| Reply Information Table has been initialized! |
| System State: Multiuser Mode. |
| 14:05/1/Spooling of initally spooled devices is complete. |
| 14:05/1/Set-up of Spooling Subsystem is complete. |
| Initializing Job & Session |
| Startup processing has begun. |
| |
_____________________________________________________________________________________
Example 3-5. Example of a Hard Reset from a Series 935 System (continued)
_____________________________________________________________________
| |
| |
| ============================================================ |
| STARTUP startup block processing |
| ============================================================ |
| SESSION Scheduling Initialized |
| ALLOW @.@;COMMANDS=LOG |
| JOB Scheduling Initialized |
| limit 10,60 |
| jobfence 7 |
| startspool lp |
| streams 10 |
| outfence 7 |
| 16:52/38/Output spooler, LDEV #6: The File System reported |
| a warning while acquiring |
| the spooled device. The spooler will continue. |
| 16:52/38/Output spooler, LDEV #6: Started. |
| Startup processing is complete. |
| |
| Initiate Operator Log On |
| Successfully launched diagnostic monitor process. |
| Warning - Protection of the system file |
| 'AUTOBOOT.MPEXL.SYS', failed. |
| |
| 16:54/36/INVALID PASSWORD FOR "OPERATOR.SYS,OPS" DURING |
| LOGON ON LDEV #20. (js 65) |
| ENTER ACCOUNT PASSWORD: |
| MPE XL: |
| |
_____________________________________________________________________
Example 3-5. Example of a Hard Reset on a Series 935 System (continued)
_________________________________________________________________
| |
| |
| CM> TC |
| |
| Processor Dependent Code (PDC) revision 3.2 |
| |
| Console path = 2/4.1.0.0.0.0.0 |
| Primary boot path = 2/4.0.0.0.0.0.0 |
| Alternate boot path = 6/4.3.0.0.0.0.0 |
| |
| 32 MB of memory configured and tested. |
| |
| Soft Booted--memory state is valid |
| |
| Autoboot from primary path enabled. |
| To override, press any key within 10 seconds. |
| |
| 10 seconds expired--proceeding with autoboot |
| |
| |
| Console IO Dependent Code (IODC) revision 4 |
| Boot IO Dependent Code (IODC) revision 4 |
| |
| Booted. |
| MMSAVE Version 2.2 |
| DUMPAREA protected, proceeding to ISL without memsave |
| ISL loaded |
| |
| ISL Revision A.00.28 July 15, 1993 |
| |
| Cannot find an auto-execute file. AUTOBOOT ABORTED. |
| |
| ISL> START |
| |
| |
| MPE/iX launch facility |
| Initialize_genesis - Version : <<870204.1552>> |
| |
| THU, MAY 24, 1990, 4:28:32 PM (y/n)? |
| |
_________________________________________________________________
Example 3-6. Example of a Soft Reset on a Series 950 System
________________________________________________________________________________
| |
| |
| [TMUX_DAM] 15 7 12 14 |
| Initialize genesis completed. |
| Create Console Messages kso completed. |
| Initialize memory manager completed. |
| Initialize resident kernel completed. |
| beginning recovery |
| setup complete - beginning recovery of free space map and |
| label table |
| completed recovery of free space map and label table |
| completed recovery of files |
| begin posting of recovered files |
| recovery completed |
| NEW and TEMP files deallocated for |
| MPEXL_SYSTEM_VOLUME_SET:MEMBER1 LDEV1 |
| Initialize volume management completed. |
| Opening the native system library completed. |
| Initialize process management completed. |
| Initialize debug subsystem completed. |
| Initialize file system completed. |
| Initialize loader completed. |
| Initialize non-resident services completed. |
| Begin binding compatibility mode SL |
| Compatibility mode SL binding complete |
| Create port process has been completed. |
| Warning - Protection of the system file |
| `AUTOBOOT.MPEXL.SYS', failed |
| Protection of system files has been completed. |
| |
| The following is a list of the boot options - |
| last boot command: INSTALL last configuration group: CONFIG |
| current boot command: START current configuration group: CONFIG |
| logon = OPERATOR.SYS |
| NORECOVERY MULTI-USER |
| MULTI-DISK SYSSTART |
| |
| Entering - System I/O configuration. |
| The path 2 has already been configured. |
| The path 2/4 has already been configured. |
| The path 2/4.0 has already been configured. |
| The path 2/4.0.0 has already been configured. |
| The path 2/4.0.2 was configured but is not available. |
| The path 2/4.1 has already been configured. |
| The path 2/4.1.0 has already been configured. |
| The path 2/4.3.0 was configured but is not available. |
| The path 2/4.3.4 was configured but is not available. |
| The path 2/4.3.5 was configured but is not available. |
| |
________________________________________________________________________________
Example 3-6. Example of a Soft Reset on a Series 980 System (continued)
________________________________________________________________
| |
| |
| The path 2/8.0.0 was configured but is not available. |
| The path 2/8.0.1 was configured but is not available. |
| The path 2/8.0.2 was configured but is not available. |
| The path 2/8.0.3 was configured but is not available. |
| The path 2/8.1.0 was configured but is not available. |
| The path 2/8.1.1 was configured but is not available. |
| The path 2/8.1.2 was configured but is not available. |
| The path 2/8.1.3 was configured but is not available. |
| The path 6/4.0.0 was configured but is not available. |
| The path 6/4.0.1 was configured but is not available. |
| The path 6/4.0.2 was configured but is not available. |
| The path 6/4.3.4 was configured but is not available. |
| The path 6/4.3.5 was configured but is not available. |
| The path 6/4.3.7 was configured but is not available. |
| Leaving - System I/O configuration. |
| |
| |
| SYSTEM I/O AT BOOT TIME |
| |
| ldev: 1 HP7937H configured available 2/4.0.0 |
| ldev: 2 HP7937H configured available 2/4.0.1 |
| ldev: 3 HP7933H configured not-available 2/4.0.2 |
| ldev: 6 HP2567A configured available 6/4.3.6 |
| ldev: 7 HP7980A configured available 6/4.3.0 |
| ldev: 8 HP7978B configured not-available 2/4.3.0 |
| ldev: 10 HP7980A configured not-available 6/4.3.7 |
| ldev: 19 HP2680A configured not-available 6/4.3.4 |
| ldev: 20 HP2392A configured available 2/4.1.0 |
| ldev: 21 HP7937H configured not-available 6/4.0.0 |
| ldev: 22 HP7937H configured not-available 6/4.0.1 |
| ldev: 23 HP7937H configured not-available 6/4.0.2 |
| ldev: 25 HP7937H configured not-available 2/8.0.0 |
| ldev: 26 HP7937H configured not-available 2/8.0.1 |
| ldev: 27 HP7933H configured not-available 2/8.0.2 |
| ldev: 28 HP7933H configured not-available 2/8.0.3 |
| ldev: 29 HP2688A configured not-available 6/4.3.5 |
| ldev: 30 HP2688A configured not-available 2/4.3.4 |
| ldev: 31 HP7937H configured not-available 2/8.1.0 |
| ldev: 32 HP7937H configured not-available 2/8.1.1 |
| ldev: 33 HP7935H configured not-available 2/8.1.2 |
| ldev: 34 HP7935H configured not-available 2/8.1.3 |
| ldev: 39 HP2688A configured not-available 2/4.3.5 |
| |
| MEMORY AVAILABLE FOR USE (bytes) : 33554432 |
| |
________________________________________________________________
Example 3-6. Example of a Soft Reset on a Series 980 System (continued)
________________________________________________________________________________
| |
| |
| Entering - Initialize system member volumes |
| Leaving - Initialize system member volumes |
| Entering - Mount all volumes |
| |
| VOLUME ALREADY MOUNTED ON LDEV 1 (AVR 10) |
| A volume has been mounted on ldev 1 |
| |
| LONER VOLUME MOUNTED ON LDEV 2 (AVR 11) |
| A volume has been mounted on ldev 2 |
| |
| |
| Warning - Volume is not available for mounting. The ldev is 3 |
| Warning - Volume is not available for mounting. The ldev is 25 |
| Warning - Volume is not available for mounting. The ldev is 26 |
| Warning - Volume is not available for mounting. The ldev is 27 |
| Warning - Volume is not available for mounting. The ldev is 28 |
| Warning - Volume is not available for mounting. The ldev is 31 |
| Warning - Volume is not available for mounting. The ldev is 32 |
| Warning - Volume is not available for mounting. The ldev is 33 |
| Warning - Volume is not available for mounting. The ldev is 34 |
| Warning - Volume is not available for mounting. The ldev is 21 |
| Warning - Volume is not available for mounting. The ldev is 22 |
| Warning - Volume is not available for mounting. The ldev is 23 |
| Leaving - Mount all volumes |
| The current boot command has been saved on the system master. |
| NMLG FILE NUMBER 0 ON. |
| [PSI_DUMP_SURR] Version A.00.01.026 |
| 16:30/11/DCC STARTUP - ENTER - version C0005105 compiled 880322 |
| 16:30/11/DCC warning 128-1, (Startup) can not open NMCONFIG, |
| status FF09008F. |
| 16:30/18/DCC ERROR 14-1, Configuration file open error 001000B4. |
| 16:30/11/DCC STARTUP - ERROR |
| System State: Initializing Mode. |
| Reply Information Table has been initialized! |
| System State: Multiuser Mode. |
| SYSTEM LOG FILE #1 IS ON |
| Initializing Job & Session |
| Initiate Operator Log On |
| SESSION Scheduling Initialized |
| JOB Scheduling Initialized |
| Successfully launched diagnostic monitor process. |
| ACCT EXISTS, USER NAME DOESN'T. (CIERR 1438) |
| 16:31/24/MISSING USER NAME DURING LOGON ON LDEV #20. (js 11) |
| MPE XL: |
| |
________________________________________________________________________________
Example 3-6. Example of a Soft Reset on a Series 980 System (continued)