[Digital logo]
[HR]

OpenVMS System Manager's Manual


Previous | Contents

To make HSC and DSSI devices accessible, do one of the following:


4.5.4 Booting While Displaying Startup Procedure Commands

In some cases---for example, when you are trying to test a startup command procedure, or when troubleshooting startup problems---it is helpful to display the startup commands as they are executed.

How to Perform This Task

  1. Follow the instructions for performing a conversational boot in one of the following manuals:
  2. At the SYSBOOT> prompt, enter the following command:
    SYSBOOT> SET STARTUP_P2 "YES"
    
  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_P2 parameter you set in step 2:
    $ RUN SYS$SYSTEM:SYSMAN
    SYSMAN> PARAMETERS USE CURRENT
    SYSMAN> PARAMETERS SET STARTUP_P2 ""
    SYSMAN> PARAMETERS WRITE CURRENT
    

    Example

     
    [perform a conversational boot] 
    SYSBOOT> SET STARTUP_P2 "YES"
    SYSBOOT> CONTINUE
    [system completes booting]                                
    Username: [Return]
    Password: [Return]
     
    $ RUN SYS$SYSTEM:SYSMAN
    SYSMAN> PARAMETERS USE CURRENT
    SYSMAN> PARAMETERS SET STARTUP_P2 ""
    SYSMAN> PARAMETERS WRITE CURRENT
    

    4.5.5 Displaying Startup Procedure Commands with SYSMAN

    In addition to performing a conversational boot to display startup procedures, you can use SYSMAN to display startup status with the STARTUP SET OPTIONS command. The advantage of using SYSMAN is that you can obtain verification and logging for multiple nodes at a time.

    SYSMAN startup logging redefines STARTUP_P2 to specify:

    The STARTUP SET OPTIONS command provides the options shown in Table 4-2.

    Table 4-2 Startup Logging Options
    Option Function
    /VERIFY=FULL Displays every line of DCL executed by component startup procedures and by STARTUP.COM.
    /VERIFY=PARTIAL Displays every line of DCL executed by component startup procedures, but does not display DCL executed by STARTUP.COM.
    /OUTPUT=FILE
    /OUTPUT=CONSOLE
    Creates SYS$SPECIFIC:[SYSEXE]STARTUP.LOG, which contains all of the output generated by startup procedures. Alternatively, you can display the output on the console.
    /CHECKPOINTING Displays informational messages describing the time and status of each startup phase and component file.

    How to Perform This Task

    1. At the DCL prompt ($), enter the following command:
      $ RUN SYS$SYSTEM:SYSMAN
      
    2. At the SYSMAN> prompt, enter the following command:
      SYSMAN> STARTUP SET OPTIONS/[qualifier]
      

      Qualifiers can be any of the options specified in Table 4-2. These options take effect the next time you boot the system.

    Example

    $ RUN SYS$SYSTEM:SYSMAN
    SYSMAN> STARTUP SET OPTIONS/VERIFY=FULL/OUTPUT=FILE/CHECKPOINTING
    

    This example requests startup logging with:

    To show the current startup options, enter the following command:

    SYSMAN> STARTUP SHOW OPTIONS
    

    For more information, see the OpenVMS System Management Utilities Reference Manual.

    4.6 Solving Booting Problems

    A hardware or software malfunction can prevent the operating system from booting when you enter the BOOT command.

    Hardware Problems

    A read error on a disk drive or console medium, or a machine check error, might indicate a hardware malfunction. When a hardware problem occurs, a question mark (?) usually precedes the error message that is displayed on the system console terminal. You should then do one or both of the following:

    Software Problems

    If the operating system is loaded into memory but the STARTUP.COM command procedure does not execute, a software malfunction has probably occurred. Suspect this condition if a message similar to following does not appear:

    The OpenVMS system is now executing the system startup procedure. 
    

    Perform one or both of the following actions to correct the situation:

    4.7 Writing a New Boot Block on the System Disk

    Block 0 on a system disk is the boot block. It contains the size and location of the primary bootstrap image, which is used to boot the system.

    On VAX systems, the primary bootstrap image is VMB.EXE.

    On Alpha systems, the primary bootstrap image is APB.EXE.

    Certain processors must read the boot block to obtain the location of the primary bootstrap image. Processors that read a boot block include the following:

    To determine if your system reads the boot block, check one of the following manuals:

    If you suspect that the boot block on the system disk is invalid, you can write a new boot block using the Writeboot utility (WRITEBOOT). The following actions might cause a boot block to become invalid:

    You must have LOG_IO privilege to use the Writeboot utility.

    How to Perform This Task

    On VAX systems, follow these steps to use the Writeboot utility:

    1. To start the Writeboot utility, enter the following command:
      $ RUN SYS$SYSTEM:WRITEBOOT
      
    2. The procedure displays the following message:
      Target system device (and boot file if not VMB.EXE):?
      
      On VAX systems, VMB.EXE is the default bootstrap image. Enter a response in the following format:
      device:[VMS$COMMON.SYSEXE]VMB.EXE;  
      

      Use the device name format described in the upgrade and installation documentation for your processor. If you want to boot using a bootstrap image other than the default, you must specify the full file specification of the image, including device and directory.
    3. The procedure displays the following message:
      Enter VBN of boot file code (default is one): 
      

      Ordinarily, the boot code is located at virtual block number (VBN) 1 of the bootstrap image. Press Return to accept the default value of 1.
    4. The procedure displays the following message:
      Enter load address of primary bootstrap in HEX (default is 200): 
      

      The load address is the location in memory (specified in hexadecimal notation) to which the system loads the bootstrap image. Ordinarily you copy the bootstrap image to address 200. Press Return to accept the default value of 200.
    5. The Writeboot utility writes the information you specified to the boot block (block 0) on the system disk.

    On Alpha systems, follow these steps to use the Writeboot utility:

    1. To start the Writeboot utility, enter the following command:
      $ RUN SYS$SYSTEM:WRITEBOOT
      

      The procedure asks you whether you want to write the VAX portion of the boot block:
      Update VAX portion of boot block (default is Y): 
      
    2. Enter NO.
    3. The utility displays the following prompt:
      Update Alpha portion of boot block (default is Y): 
      

      Press Return to accept the default value of Y.
    4. The utility prompts you for the Alpha bootstrap image:
      Enter Alpha boot file: 
      
      On Alpha systems, APB.EXE is the default bootstrap image. Enter a response in the following format:
      device:[VMS$COMMON.SYSEXE]APB.EXE;  
      

      where device specifies the device name of the system disk.
    5. The Writeboot utility writes the information you specified to the boot block (block 0) on the system disk.

    On VAX and Alpha systems, the Writeboot utility might display one or more of the following error messages:

    Example

    On VAX systems, the following example writes a boot block on a system disk:

    $ RUN SYS$SYSTEM:WRITEBOOT
    Target system device (and boot file if not VMB.EXE):? DUA0:[VMS$COMMON.SYSEXE]VMB.EXE
    Enter VBN of boot file code (default is one):[Return]
    Enter load address of primary bootstrap in HEX (default is 200): [Return] 
     
     
    

    On Alpha systems, the following example writes a boot block on a system disk:

    $ RUN SYS$SYSTEM:WRITEBOOT
    Update VAX portion of boot block (default is Y): N
    Update Alpha portion of boot block (default is Y): [Return]
    Enter Alpha boot file: DUA0:[VMS$COMMON.SYSEXE]APB.EXE; 
     
     
    

    4.8 Shutting Down the System

    The operating system provides the following shutdown procedures:
    Procedure Purpose For More Information
    SHUTDOWN.COM An orderly shutdown procedure. This procedure shuts down the system while performing housekeeping functions such as disabling future logins, stopping the batch and output queues, dismounting mounted volumes, and stopping user processes. Section 4.8.1
    OPCCRASH.EXE An emergency shutdown program. Run the OPCCRASH emergency shutdown program if you are unable to perform an orderly shutdown with SHUTDOWN.COM. Section 4.8.5
    Shutdown using console commands Emergency shutdown commands. Use these console shutdown commands only if OPCCRASH.EXE fails. Section 4.8.6

    4.8.1 Performing an Orderly Shutdown with SHUTDOWN.COM

    Use SYS$SYSTEM:SHUTDOWN.COM to shut down the system in an orderly fashion. See Section 4.8.2 for the order of shutdown events.

    Do not modify SHUTDOWN.COM. To perform site-specific operations during shutdown, see Section 4.8.3.

    Ordinarily, you shut down the system from the SYSTEM account, which includes all privileges by default. To execute SHUTDOWN.COM, you must have either the SETPRV privilege or all of the following privileges:

    You can cancel a shutdown without any side effects by pressing Ctrl/Y before SHUTDOWN.COM displays the following message:

    %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. 
    

    If you press Ctrl/Y after this display, certain system components might have already been shut down, and you will need to recover manually. For example, you might have to manually restart processes, mount disks, or reboot the system.

    How to Perform This Task

    1. Log in to the system manager's account (SYSTEM), or any privileged account, and enter the following command:
      $ @SYS$SYSTEM:SHUTDOWN.COM
      

      This command invokes the orderly shutdown procedure. The procedure prompts you with a series of questions and messages. The default responses appear in brackets at the end of each question. Press Return to select the default response.
    2. The system displays the following question:
      How many minutes until final shutdown [0]? 
      

      Enter an integer. If you have defined the system logical name SHUTDOWN$MINIMUM_MINUTES, its integer value is the minimum value that you can enter. For example, if the logical name is defined as 10, you must specify at least 10 minutes to final shutdown or an error message is returned. If you do not enter a value, SHUTDOWN.COM uses the logical name value.

      Caution

      The default is 0 minutes. If you have not defined the logical name SHUTDOWN$MINIMUM_MINUTES, and you do not enter a value, the system will be shut down immediately after you answer the last question.

    3. The system displays the following question:
      Reason for shutdown [standalone]: 
      

      Enter a one-line reason for shutting down the system. For example, "Monthly preventive maintenance."
    4. The system displays the following question:
      Do you want to spin down the disk volumes [No]? 
      

      Enter YES or NO (Y or N). Note, however, that you cannot spin down the system disk. Also, many disks, particularly SCSI disks, do not spin down in response to this option.
    5. The system displays the following question:
      Do you want to invoke the site-specific shutdown procedure [Yes]? 
      

      If you have entered site-specific commands in SYSHUTDWN.COM, press Return to accept the default answer, YES. For more information, see Section 4.8.3.2.
    6. The system displays the following question:
      Should an automatic system reboot be performed [No]? 
      

      By default, the system does not automatically reboot. However, if you respond YES, the system attempts to reboot automatically when the shutdown is complete. For example, you would specify YES if you are rebooting the system after modifying values for nondynamic system parameters with SYSMAN or SYSGEN. (When you change nondynamic system parameters, you must reboot the system for the new values to take effect.)
    7. The system displays a question similar to the following:
      When will the system be rebooted [later]? 
      

      If you entered YES in step 6, the default answer to this question is "[shortly via automatic reboot]".
      Press Return to take the default, or enter the expected reboot time in the format you want users to see. For example, you could specify IMMEDIATELY, or IN 10 MINUTES, or a time such as 2 P.M. or 14:00. If you do not know when the system will be available again, press Return to specify "later" as the time when the system will reboot.
    8. The procedure prompts you to specify one or more shutdown options, as follows (if your system is not a member of an OpenVMS Cluster environment, the procedure lists only the REBOOT_CHECK and SAVE_FEEDBACK options):
      Shutdown options (enter as a comma-separated list): 
       REMOVE_NODE         Remaining nodes in the cluster should adjust quorum 
       CLUSTER_SHUTDOWN    Entire cluster is shutting down 
       REBOOT_CHECK        Check existence of basic system files 
       SAVE_FEEDBACK       Save AUTOGEN feedback information from this boot 
       DISABLE_AUTOSTART   Disable autostart queues 
      Shutdown options [NONE] 
      

      Specify the options you want to use. Choose from the following:
      Option Description
      REMOVE_NODE Causes other nodes in the cluster to decrease the value of the EXPECTED_VOTES system parameter. (This parameter is automatically increased each time a node joins the cluster.) Specifying REMOVE_NODE will not decrease the EXPECTED_VOTES below the quorum value.

      Use this option if the node you are shutting down will be out of the cluster a considerable period of time.

      CLUSTER_SHUTDOWN Synchronizes the shutdown of a cluster; only when the shutdown of each node has progressed to a certain point will the shutdown be completed.

      Use this option on each node in the cluster to synchronize the shutdown.

      REBOOT_CHECK Verifies the presence of files necessary to reboot the system after shutdown completes.

      The procedure checks for the necessary files and notifies you if any are missing. Replace missing files before proceeding.

      SAVE_FEEDBACK Records feedback data collected from the system since it was last booted and creates a new version of the AUTOGEN feedback data file, which AUTOGEN can use the next time it runs.

      For detailed information on using the AUTOGEN feedback mechanism, see Section 14.4.1.

      DISABLE_AUTOSTART Specifies the time interval between the DISABLE AUTOSTART/QUEUES command and system shutdown. For more information, see Section 13.7.1.9.

    Example

    $ @SYS$SYSTEM:SHUTDOWN
             SHUTDOWN -- Perform an Orderly System Shutdown
     
    How many minutes until final shutdown [0]: 10
    Reason for shutdown: [Standalone] MONTHLY PREVENTIVE MAINTENANCE
    Do you want to spin down the disk volumes [No]? [Return]
    Do you want to invoke the site-specific shutdown procedure [Yes]? [Return]
    Should an automatic system reboot be performed [No]? [Return]
    When will the system be rebooted [later]? 12:30
    Shutdown options (enter as a comma-separated list): 
     REMOVE_NODE         Remaining nodes in the cluster should adjust quorum 
     CLUSTER_SHUTDOWN    Entire cluster is shutting down 
     REBOOT_CHECK        Check existence of basic system files 
     SAVE_FEEDBACK       Save AUTOGEN feedback information from this boot 
     DISABLE_AUTOSTART   Disable autostart queues
    Shutdown options [NONE] [Return]
    SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0:   12:00:00.20
    AVALON will shut down in 10 minutes; back up 12:30. Please log off node AVALON.
    MONTHLY PREVENTIVE MAINTENANCE
    %SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:01:00.15  %%%%%%%%%%%
    Operator status for operator _AVALON$OPA0:
    CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, OPER1, OPER2,
    OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,
    OPER12
    %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.
    %SET-I-INTSET, login interactive limit = 0 current interactive value = 17
    %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down.
     
    SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0:   12:05:00.20
    AVALON will shut down in 5 minutes; back up 12:30. Please log off node AVALON.
    MONTHLY PREVENTIVE MAINTENANCE
    17 terminals have been notified on AVALON.
    SHUTDOWN message on AVALON from user SYSTEM at _AVALON$OPA0:   12:06:55.28
    AVALON will shut down in 3 minutes; back up 12:30. Please log off node AVALON.
    MONTHLY PREVENTIVE MAINTENANCE
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:07:12.30  %%%%%%%%%%%
    Message from user DECnet on AVALON
    DECnet event 2.0, local node state change
    From node 2.161 (AVALON), 16-MAY-1996 12:07:22.26
    Operator command, Old state = On, New state = Shut
    SHUTDOWN message on AVALON user SYSTEM at _AVALON$OPA0:   12:08:12.56
    AVALON will shut down in 2 minutes; back up 12:30. Please log off node AVALON.
    MONTHLY PREVENTIVE MAINTENANCE
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:08:12:30  %%%%%%%%%%%
    Message from user JOB_CONTROL on AVALON 
    -SYSTEM-S-NORMAL, normal successful completion
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:08:42.30  %%%%%%%%%%%
    Message from user DECNET on AVALON 
    DECnet shutting down
    %SYSTEM-I-STOPQUEUES, The queues on this node will now be stopped.
    SHUTDOWN message on AVALON from user SYSTEM at _AVALON$OPA0:   12:09:12.56
    AVALON will shut down in 1 minute; back up 12:30. Please log off node AVALON.
    MONTHLY PREVENTIVE MAINTENANCE
    SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0:   12:10:00.20
    AVALON will shut down in 0 minutes; back up 12:30. Please log off node AVALON.
    MONTHLY PREVENTIVE MAINTENANCE
    17 terminals have been notified on AVALON
    %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.
    %SHUTDOWN-I-STOPUSER, All user processes will now be stopped.
    %SHUTDOWN-I-REMOVE, All installed images will now be removed.
    %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:09:42.30  %%%%%%%%%%%
    Message from user System on AVALON 
    _AVALON$OPA0:, AVALON shutdown was requested by the operator.
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:10:02.44  %%%%%%%%%%%
    Logfile was closed by operator _AVALON$OPA0: 
    Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;8
    %%%%%%%%%%%  OPCOM, 16-MAY-1996 12:10:32.20  %%%%%%%%%%%
    Operator _AVALON$OPA0: has been disabled, username SYSTEM
            SYSTEM SHUTDOWN COMPLETE
    

    On VAX systems, the following message is also displayed:

    USE CONSOLE TO HALT SYSTEM 
    

    Halt the system after you see this message.

    4.8.2 Understanding the Order of Shutdown Events

    The following events occur as the shutdown proceeds. The procedure displays the corresponding messages on the terminal.

    1. At decreasing time intervals, SHUTDOWN.COM broadcasts, to all users on the system, a message requesting users to log out.
    2. SHUTDOWN.COM defines the system logical name SHUTDOWN$TIME to be the absolute time of shutdown. For example, if you execute SHUTDOWN.COM, and at 12:00 you specify the value 10 in response to the first question, SHUTDOWN defines the logical name to be 12:10 on that day. To see if a shutdown is in progress or to determine the actual time of shutdown, you can enter the command SHOW LOGICAL SHUTDOWN$TIME. This feature is useful if you miss a shutdown broadcast message.
    3. At 6 minutes or less before system shutdown, the terminal from which you invoked SHUTDOWN becomes an operator's console. SHUTDOWN disables all future nonoperator logins and shuts down the DECnet network if it is running. At this point, users logged in to the system with the SET HOST command lose their sessions.
    4. One minute before shutdown, SHUTDOWN.COM stops batch and output execution queues and stops the queue manager.
    5. At the absolute time of shutdown, SHUTDOWN.COM invokes the site-specific shutdown command procedure SYS$MANAGER:SYSHUTDWN.COM, if you requested it.
    6. SHUTDOWN.COM stops all remaining user processes; however, system processes continue. Ancillary control processes (ACPs) might delete themselves when their mounted volumes are finally dismounted.
    7. On multiprocessor systems, SHUTDOWN.COM stops the secondary processors.
    8. SHUTDOWN.COM removes all installed images.
    9. SHUTDOWN.COM dismounts all mounted volumes and, if you requested it, spins down the disks. If you defined SHUTDOWN$VERBOSE, the procedure lists each disk as it is dismounted.
      The procedure does not spin down the system disk, nor does it dismount or spin down the quorum disk (if one exists on your system).
    10. SHUTDOWN.COM closes the operator log file.
    11. SHUTDOWN.COM runs the program SYS$SYSTEM:OPCCRASH.EXE to shut down the system.
    12. If you requested an automatic reboot, the system reboots, provided you set the necessary controls. You requested an automatic reboot if you answered YES to the following question:
      Should an automatic system reboot be performed [No]? 
      

      If you did not request an automatic reboot, a message similar to the following appears on the system console:
      SYSTEM SHUTDOWN COMPLETE 
      

      On VAX systems, the following message is also displayed:
      USE CONSOLE TO HALT SYSTEM  
      

      Halt the system after you see this message.

    4.8.3 Customizing SHUTDOWN.COM to Perform Site-Specific Operations

    In addition to choosing shutdown options when you execute SHUTDOWN.COM, you can customize SHUTDOWN.COM to meet the needs of your site in the following ways.
    Method For More Information
    Defining logical names Section 4.8.3.1
    Modifying the site-specific shutdown command procedure Section 4.8.3.2

    4.8.3.1 Defining Logical Names

    Before executing SHUTDOWN.COM, you can define the following logical names to control the operations of the command procedure:
    Logical Name Description
    SHUTDOWN$DECNET_MINUTES Defines the number of minutes remaining before DECnet is shut down; must be defined with the /SYSTEM qualifier. The default is 6 minutes.
    SHUTDOWN$DISABLE_AUTOSTART Specifies the number of minutes between the time autostart is disabled for queues and the time the system is shut down. For more information, see Section 13.7.1.9.
    SHUTDOWN$INFORM_NODES Specifies a list of OpenVMS Cluster nodes to be notified when the system is shutting down. This logical name is described in detail in this section.
    SHUTDOWN$MINIMUM_MINUTES Defines the minimum number of minutes you can specify as number of minutes to shutdown. For example, if your users require 30 minutes' notice before a system shutdown, define this logical name to be 30.
    SHUTDOWN$QUEUE_MINUTES Defines the number of minutes remaining before shutdown when queues are shut down; must be defined with the /SYSTEM qualifier. The default is 1 minute.
    SHUTDOWN$TIME Defines the absolute time of shutdown.
    SHUTDOWN$VERBOSE If defined to any string, specifies that the shutdown command procedure is to list each disk as it is dismounted.


    Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

    [HR]

      6017P008.HTM
      OSSG Documentation
      22-NOV-1996 14:21:27.67
    

    Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

    Legal