System Startup

System startup refers to the procedure for starting the computer software, the operating system, and other programs. The system startup involves the following procedures:

turning on the computer (perform only if system has been powered off)
resetting the system
booting the system
starting the system

This section briefly describes the procedures for starting a system that you have previously shut down.

Step 1. Turning the computer on.




	NOTE: Perform this step only if the system has been powered off.

Turning on the computer is the first step in starting the system. Press the ON/OFF button to turn the system on.

Step 2. Resetting the system.

You can reset the system by performing a hard reset or by performing a soft reset.




	CAUTION: The Power-on button performs a hard reset, but it should only be used as a last resort.

Hard reset

A hard reset performs a self-test of the system that clears and resets the system's memory.

At the console, enter Ctrl B.
At the CM> prompt enter, RS Return.

Respond Y to the following prompt:

   Type Y to confirm your intention to restart the system (Y/[N]):Y

Soft reset

A soft reset performs a nondestructive self-test of the system that does not reset the system's memory.

At the console, enter Ctrl B.
At the CM> prompt, enter TC Return.

Respond Y to the following prompt:

   Type Y to confirm your intention to execute this command (Y/[N]): Y

Step 3. Booting the system

There may be instances which require you to perform a system boot. System configuration and recovering your system's operating system (FOS) and software applications are instances when you might need to boot your system.




	NOTE: Keep in mind that these tasks should be performed only by system management trained personnel or a Hewlett-Packard Service Representative as these procedures may result in loss of user data if it is performed inappropriately.

After performing a system powerup, a similar screen appears on the console screen:

Figure 2-4 Initial Menu

   ---------------------------------------------------------------------

   PDC - Processor Dependent Code  - Version x.x

   (c) Copyright 1990-1993, Hewlett-Packard Company, All rights reserved

   ----------------------------------------------------------------------

   0 Bytes of memory configured an tested.

   Primary boot path:    0/0/0/0/0/0/0.0.0.0.0.0.0  (dec)

   Alternate boot path:  0/0/0/0/0/0/0.0.0.0.0.0.0  (dec)

This screen is followed by the Main Menu.

Figure 2-5 Main Menu

   --Main Menu-----------------------------------------------------



     Command                       Description

     -------                       -----------

     BOot [PRI|ALT|<path>]         Boot from specified path

     PAth [PRI|ALT|CON][<path>]    Display or modify a path

     SEArch [DIsplay|IPL] [<path>] Search for boot devices

     COnfiguration menu            Displays or sets boot values

     INformation menu              Displays hardware information

     SERvice menu                  Displays service commands

     DIsplay                       Redisplay the current menu

     HElp [<menu>|<command>]       Display help for a menu or command

     RESET                         Restart the system



   ----

   Main Menu: Enter command or menu >

Booting from the Primary Path

If you need to boot from the disk enter the following at the Main Menu prompt:

   Main Menu: Enter command or menu > BO Return

   Interact with IPL (Y or N)?> y Return




	NOTE: Booting from the primary path is the system default, therefore when `BO` is typed at the prompt, `BO PRI` is assumed.

The system will respond with a screen similar to the following:

   Booting...

   Boot IO Dependent Code (IODC) revision 4

   .

   .

   .

   ISL>

Booting from the Alternate Path

If you need to boot from tape do the following at the Main Menu prompt:

   Main Menu: Enter command or menu > BO ALT Return

   Interact with IPL (Y or N)?> y Return

The system will respond with a screen similar to the following:



   Booting...

   Boot IO Dependent Code (IODC) revision 4

   .

   .

   .

   ISL>

Step 4. Starting the system

The START command can be used to start the system after a shutdown, a reconfiguration, or a system fail.

Start the system.
- When starting the system after a shutdown or recovering from a system failure, type the following at the >ISL prompt:
  ISL>START RECOVERY Return
  The RECOVERY option allows for the recovery of the jobs and spool files that were on the system before it stopped.
- When starting the system after it has been reconfigured, type the following at the >ISL prompt:
  ISL>START NORECOVERY Return
  The NORECOVERY option ensures that the changes made to the reconfiguration files take effect.
Log on as system manager.
At the end of the start procedure if the MPE/iX: prompt appears, log on as MANAGER.SYS.
MPE/iX: HELLO MANAGER.SYS;HIPRI Return
If the system prompt (:) appears, you are probably logged on to OPERATOR.SYS.
Allow users to log on.
Set the job and session limits so that others may log on:
:LIMIT 10,30 Return
Allow jobs to process.
Lower the jobfence so that jobs may process:
:JOBFENCE 1 Return
Allow reports to print.
Lower the outfence so that reports may print:
:OUTFENCE 1 Return
Restart job streaming.
Restart the job stream facility and the spooler by entering the following:
:STREAMS 10 Return
Allow spool files to print.
Start the spooler so that spool files may be created.
:SPOOLER START Return

Summary for starting the system

The following is a summary of the procedures for getting the system running after a system shutdown:

Reset the system:

   Ctrl B



   CM>RS Return



   or



   CM>TC Return

Boot from primary path. Interact with IPL.
At the ISL> prompt type, START RECOVERY Return.
If necessary, log on as MANAGER.SYS and supply passwords.
Set job and session limits so that others may log on:
:LIMIT 10,30 Return
Lower the jobfence so that jobs may process:
:JOBFENCE 1 Return
Lower the outfence so that reports may print:
:OUTFENCE 1 Return
Turn on the streaming device so that the user may stream jobs:
:STREAMS 10 Return
Turn on the spooler so that spool files may be printed.
:SPOOLER START Return

To automate system preparation for use

Every time that you turn on the system, or every time that you boot the system, certain commands need to be entered to prepare the system for normal use. For example, the facility that enables the streaming of jobs must be set with the STREAMS command. Rather than entering these commands individually each time you boot the system, you can have them execute automatically at reboot by listing them in a special file. This file must be created by MANAGER.SYS and must have the name SYSSTART.PUB.SYS to be effective.

When your system was installed, a SYSSTART file may have been created for you. If so, it probably contains the following commands:

   STARTUP

   SPOOLER LP;START

   STREAMS 10

   OUTFENCE 7

To create a SYSSTART file or to modify the commands in an existing SYSSTART file, enter the following commands:

Log on as MANAGER.SYS.
Enter the editor
:EDITOR Return
If the file exists on your system, bring it into the editor and add additional lines as desired:
/T SYSSTART Return /L ALL Return /A nn Return nn_
If the file does not exist on your system, create it by entering the following commands.
/AD D Return 1_
The following sample commands can be added as desired. The entry STARTUP must be the first line in the file. There is no required sequence to the other commands. It is not necessary to include all of these other commands. Create a file that is appropriate for your environment.
1 startup Return 2 spooler lp;start Return 3 streams 10 Return 4 limit 60,60 Return 5 outfence 7 Return 6 jobfence 6 Return 7 //
The following list provides an explanation of typical entries:
STARTUP
Identifies the situations in which the commands in this file will be executed. All commands following STARTUP are executed on any start or reboot of the system.
SPOOLER LP;START
Starts the printer spooler.
STREAMS 10
Defines the streams device used to stream jobs in the system. Usually, the streams device is configured as device 10.
LIMIT 60,60
Identifies the maximum number of jobs and sessions that will be allowed to execute at the same time. The first number specifies the maximum number of jobs. The second number specifies the maximum number of sessions. These limits must be set to 0 when the system is needed for maintenance, such as a configuration change. This command in the SYSSTART file would reset the limits to the standard settings when the system is rebooted. The standard settings for job and session limits depend on how many users you have on your system.
OUTFENCE 7
Defines the print priority at which a spool file will print. The outfence ranges from 1 to 14. An outfence of 14 allows no spool files to print without system manager intervention. The outfence is often set to 14 during rebooting or system maintenance when the printer should be idle. The outfence is usually set to 7 for normal operation.
JOBFENCE 6
Similar to the outfence, defines the priority at which a job can be run. The jobfence also ranges from 1 to 14. The jobfence is often set to 14 to keep other users from logging on to the system during system maintenance. It is usually set to 6 for normal operation.
Once the desired entries have been added, save the file with the KEEP command and name it SYSSTART.PUB.SYS.
/KEEP SYSSTART.PUB.SYS Return
If this is an update to an existing file, you will be prompted that the file already exists. Press Y to overwrite the existing file.
Exit the Editor:
/ E Return

From this point, the commands in your SYSSTART file will execute automatically with a restart or reboot of the system. To keep this file from executing, rename the file.

   RENAME SYSSTART.PUB.SYS EXSTART.PUB.SYS

To reinstate it, rename the file back to SYSSTART.PUB.SYS.

To check the status of peripherals

Use the SHOWDEV command to display the status of devices such as terminals, tape drives, and printers.

   :SHOWDEV Return

   LDEV  AVAIL      OWNERSHIP      VOLID      DEN   ASSOCIATION

     1   DISC

     2   DISC

     3   DISC

     7   TAPE

    10   JOBTAPE

    20   CONSOLE

   113   LP

   114   UNAVAIL   SPOOLER OUT

Terminal problems?

Did your terminal screen suddenly turn off?

Some terminals have a feature that causes the screen to turn itself off automatically after several minutes of user inactivity. If this happens, press any key on the keyboard to reactivate the screen.

Is the keyboard not responding?

Sometimes the terminal screen and keyboard seem to "freeze up" and become unresponsive. There may be a problem with the power source, or you may have what is called a hung terminal.

Several hung terminals could mean serious system problems. If there is such an occurrence on your system, call your Hewlett-Packard representative immediately. Here are some remedies for a hung terminal.

Method 1: Wait a few minutes.

Wait a few minutes.
Press Return several times.

Method 2: Check the cable connections.

Check that the terminal is plugged into its power source.
Check to see if the terminal is turned on.
Check that the terminal is connected to the computer system.
- Make sure that the cable is connected firmly at the back of the terminal.
- Trace the cabling back to its connection in the serial port. Make sure that the cable is connected firmly in the serial port socket.

Method 3: Check that the terminal is not in Ctrl S.

Press Ctrl Q.

CTRL S may have been pressed. This would prevent the terminal screen from scrolling. By pressing CTRL Q, scrolling will start again. If scrolling does not resume, try the next method.

Method 4: Check that your terminal is in the correct mode.

Look at the bank of terminal keys at the top of your keyboard. In the middle of the row of keys marked F1 through F8, locate and press the one labeled System.
This should change the softkeys displayed at the bottom of your terminal screen. Locate and press the softkey, F4, labeled {{Modes}}.
This changes the softkey display. Look at the softkey labeled {{BLOCK MODE}}. Make sure that the {{BLOCK MODE}} key does not contain an asterisk (*) in the label. If it does, press F3 to toggle the asterisk "off."
Look at the softkey labeled {{AUTO LF}}. Make sure that the {{AUTO LF}} key does not contain an asterisk (*) in the label. If it does, press F3 to toggle the asterisk "off."
Locate and check the {{REMOTE MODE}} label. Make sure that an asterisk (*) does appear in the label. If not, press F4 to toggle the asterisk "on."
Press Return several times to see if the system prompt appears.

Method 5: Perform a terminal "soft reset".

Press Shift Reset.
Press Return several times.

If your terminal hang occurred while you were in the middle of work on the system, do the following:

Press Shift Reset.
Press Return several times.
At the system prompt, type ABORT Return.

This terminates whatever process you were working on and may free your terminal.

Method 6: Perform a terminal hard reset.

Press Shift Ctrl Reset simultaneously.

A hard reset might erase your current work.

Method 7: Turn the terminal off and back on




	CAUTION: The following procedure should not be performed on the system's console. If you are using the console, refer to the next section entitled, "Console problems?".

Turn the terminal off and then back on again.

Method 8: Abort your session

Have the system administrator abort your session.

If you are the system administrator, do the following from the system console:

Enter the following:
SHOWJOB JOB=@S Return

A screen similar to the following appears:

   JOBNUM   STATE    IPRI   JIN   JLIST   INTRODUCED   JOBNAME



   #S22     EXEC             20   20      TUE 8:46P    JOANN.YUKI

   #S43     EXEC            105   105     WED 9:32A    MANAGER.SYS



   2 JOBS (DISPLAYED):

       0 INTRO

       0 WAIT; INCL 0 DEFERRED

       2 EXEC; INCL 2 SESSIONS

       0 SUSP

   JOBFENCE= 7; JLIMIT= 2; SLIMIT= 15

Identify your session number, identified under JOBNUM as #Snn.
Enter the following:
ABORTJOB #Snnn Return
Replace nnn with the session number of the hung terminal.
After the session abort message appears on the user's terminal screen, and the log off message has been displayed on the console, have the user press Return several times.
If the logon prompt (MPE XL:) does not appear on the user's terminal, enter the ABORTJOB command again.

Console problems?

An unresponsive console is a more serious problem than an unresponsive terminal. You cannot monitor or control the system when the console is "hung."

Is the console not responding?

If the console is hung, try the first six methods of the "Terminal problems?" section.

If after attempting these methods the console is still hung, check the following:

Is the console receiving messages from other users?

Check to see if another user on the system can send a message to the console. Have someone using a working terminal do the following to send a message to the console:

Type a message using the TELLOP command.
TELLOP Let's try this! Return
When this message appears on the console screen, press Return to get the colon prompt.

Are there too many pending console requests?

Too many pending console requests can cause the console to appear hung. Check to see if there are any pending console requests using the RECALL command.

Hold down the Ctrl key and press A.
At the = prompt, type RECALL Return.
Respond to pending requests one at a time, using the REPLY command.

No response to Ctrl A?

If there is no = prompt, abort input and output to the console from another working terminal.

At the working terminal, log on to an account with SM capability.
:HELLO MANAGER.SYS Return
Enter the following:
ABORTIO 20 Return
You must have SM capability to use this command.
Repeat this command a few times until you see the following message:
NO I/O TO ABORT FOR DEVICE nn
Press Return several times to get to the system prompt.

Switch console control to a working terminal

It may be necessary to abort your original console session. To do so, you must switch the console controls to a working terminal. You must have, or be allowed, SM capability to do the following procedures:

Log on to another working terminal as MANAGER.SYS.
At the prompt, enter CONSOLE Return. This determines the current LDEV number of the console. The system console is normally LDEV 20.
Enter SHOWME Return. This determines the LDEV number of the terminal that you are using.
Enter CONSOLE nn Return where nn is replaced by the LDEV number of the terminal that you are currently using. For example, if you were to move the console from LDEV 20 to the terminal that you are using (LDEV 31), you would type the following:
CONSOLE 31 Return
Verify that the console has been moved by typing CONSOLE Return.
Enter SHOWJOB JOB=MANAGER.SYS Return to determine the session number that you were using on the original console.
At the prompt, enter ABORTJOB JOB=#Snn Return to abort your original session at the console.
When the log off message displays on this terminal, go back to the original console, and press Return several times.
Log on to the original console by entering HELLO MANAGER.SYS;HIPRI Return.
Move the console control back to the original console. For example, if the console was identified as 20, you would enter CONSOLE 20.