[Digital logo]
[HR]

OpenVMS System Manager's Manual


Previous | Contents

You can also define logical names, and then override them by using the /SOURCE and /DESTINATION qualifiers on the PRODUCT command.


Note

If you do not deassign logical names after they are used, they can cause unexpected results in future operations of the POLYCENTER Software Installation utility. Digital recommends that you use the /SOURCE and /DESTINATION qualifiers.

Logical name PCSI$SOURCE defines the location of the software kits you want to install. Logical name PCSI$DESTINATION defines the location where you want to install the software. For example, if the software is located in DISK1:[KITS] and you want to install it in DISK2:[APPLICATIONS], use the following commands:

$ DEFINE PCSI$SOURCE DISK1:[KITS] 
$ DEFINE PCSI$DESTINATION DISK2:[APPLICATIONS] 

You can override the logical name definitions by using /SOURCE and /DESTINATION qualifiers on the PRODUCT command to specify a different source and destination.

If you do not define PCSI$DESTINATION, the utility installs the software product in SYS$COMMON:[VMS$COMMON] and directories under it.

3.9.1.2 Installing Prerequisite Software

Install any prerequisite software or perform any prerequisite tasks. This information should be in the software product's installation instructions or release notes.

Note that the POLYCENTER Software Installation utility will perform this automatically if the kits are available.

3.9.1.3 Identifying Postinstallation Procedures

Note any postinstallation procedures. This information should also be in the software product's installation instructions or release notes.

3.9.2 Extracting a Product's Release Notes

To read a product's release notes, extract the notes to a file. For example, use either of the following commands to copy the CMS product release notes to a text file:

$ PRODUCT EXTRACT RELEASE_NOTES CMS/FILE=CMS_RELNOTES.TXT
$ PRODUCT EXTRACT RELEASE_NOTES CMS/SOURCE=WORK_DISK:[KITS]/FILE=CMS_RELNOTES.TXT

If you do not specify a file name, the release notes are written to a file named DEFAULT.PCSI$RELEASE_NOTES in the current directory. It is not necessary to install a software product before you use the POLYCENTER Software Installation utility to extract its release notes.

3.9.3 Installing a Product

To start an installation, enter the PRODUCT INSTALL command. For example:

$  PRODUCT INSTALL CMS

To install more than one product at a time, enter a list of product names separated by commas. You can use asterisk (*) wildcard characters in the product names. For example:

$  PRODUCT INSTALL CMS/VERSION=3.4,LSE,COB*/VERSION=5.0

Table 3-9 lists some of the features you can control with command qualifiers. A complete list is in the OpenVMS System Management Utilities Reference Manual and in online help.

Table 3-9 Features You Can Request During an Installation
Feature Qualifier
Supply answers from a PCF /CONFIGURATION=INPUT= pcf-name
Create a new PCF /CONFIGURATION=OUTPUT= pcf-name¹
Specify where to install the files /DESTINATION= location
Display full descriptions of all product installation options and information /HELP
Display log messages on your terminal /LOG
Include a remark in the product database /REMARK
Specify where the distribution kit is located /SOURCE
Specify configuration variables /CONFIGURATION= keyword²
Specify a work area for temporary files /WORK= device


¹The F17 (defer) and F18 (write) keys have no effect when you use the PRODUCT INSTALL command.
²Can be either current or producer. For details, see the OpenVMS System Management Utilities Reference Manual.

3.9.3.1 Using an Existing PCF

Section 3.8.4 describes how to create a PCF before installing a product. To use this existing PCF during the installation, use the /CONFIGURATION=INPUT qualifier with PRODUCT INSTALL. For example, to install CMS and use configuration choices recorded in the PCF named DEC-VAXVMS-CMS.PCSI$CONFIGURATION:

$ PRODUCT INSTALL/CONFIGURATION=INPUT=DEC-VAXVMS-CMS.PCSI$CONFIGURATION -
_$ CMS/VERSION=3.4

3.9.3.2 Creating a New PCF During the Installation

If you did not create a PCF before the installation, you can create one during the installation. Use the /CONFIGURATION=OUTPUT=pcf-name qualifier with PRODUCT INSTALL. For example:

$ PRODUCT INSTALL/CONFIGURATION=OUTPUT=CMSV3.DAT CMS/VERSION=3.0

As you respond to questions about the options for CMS Version 3.0, your responses are recorded in the PCF named CMSV3.DAT in your current default directory.

For more information about product configuration files, see Section 3.8.1 and Section 3.8.4.

3.9.4 Responding to Installation Questions

During an installation, you can request a full description of product options or an explanation to any single question. You can also accept the default value to any single question or to an entire subset of questions.

3.9.4.1 Requesting an Explanation to Questions

To request a full description of all product options and information, use the /HELP qualifier with PRODUCT INSTALL. To request help about an individual question, press the Help key or PF2 in response to the question. The POLYCENTER Software Installation utility displays a description (if one is available) and a summary of disk and memory requirements for the option.

The following example uses the Help key:

$ PRODUCT INSTALL UCX
   .
   .
   .
Optional example files may be installed... [YES] [Help]
The example files include client server programming examples.
Block Size -      Total:    507  Optional:      0  Required:    507
Global Pages -    Total:      0  Optional:      0  Required:    0
Global Sections - Total:      0  Optional:      0  Required:    0
Optional example files may be installed... [YES] [Return]
   .
   .
   .

The amount of information varies; some products provide more information than others, and some products provide no information.

3.9.4.2 Accepting Default Answers

Default answers come from one of three places:

If you specify an input PCF and it contains an answer for an option, the default answer from the PCF is used. Depending on the entry in the PCF, the default answer may or may not be allowed to change.

If no input PCF exists, or if the input PCF does not contain an answer for an option, the default answer comes from either the PDB or the PDF. If the PDB is present and contains the option, then the default answer comes from the PDB. If the PDB is not present (a new installation) or does not contain the option (a new option), then the default comes from the PDF. Default answers that come from either the PDB or PDF may be changed.

To answer an option, either press Return to accept the default answer, or supply your own answer and then press Return.

Some products contain a subset of questions or options. During an installation procedure, you can accept the default values for an entire subset or you can answer each option in the subset.

When you select an option that has suboptions, the POLYCENTER Software Installation utility will ask:

Do you want the defaults for all options? [YES]
If you answer YES, you will not be asked about the subitems. Instead, the utility will use the defaults for the subitems. If you answer NO, the utility asks you about each subitem.

3.9.5 Confirming Your Answers

After you respond to questions about product options, the POLYCENTER Software Installation utility can display a summary of your answers. For example:

Do you want to review the options? [YES] [Return]
DEC TCP/IP Services for OpenVMS
    Optional example files may be installed...: NO
    Optional NFS files may be installed...: NO      
    Optional applications may be installed...: YES

The POLYCENTER Software Installation utility then asks:

Are you satisfied with these options? [YES] [Return]

If you are not, answer NO to this question. You can then either enter your answers again or exit the installation procedure:

Do you want to change any options? [YES] NO [Return]
 
%PCSIUI-I-USERABORT, operation terminated by user
 

By answering NO to this question, you can end the installation procedure. The product is not installed; your system remains unchanged.

3.9.5.1 Updating DCL Help Text

When you install a layered product that updates DCL Help text, the PRODUCT INSTALL command requires exclusive access to the DCL Help library file, SYS$HELP:HELPLIB.HLB. For example, if a user is accessing HELP while an installation is trying to update the help library, you see several messages and are asked to respond to several questions. These messages and questions appear in the following order:

  1. The system displays the following messages if the PRODUCT INSTALL command fails to obtain exclusive access to the help library after waiting for two minutes:
    %PCSI-I-PRCOUTPUT, output from subprocess follows ... 
    %LIBRAR-F-OPENIN, error opening disk:[SYS0.SYSCOMMON.] 
       [SYSHLP]HELPLIB.HLB;1 as input 
    -RMS-E-FLK, file currently locked by another user 
     
    %PCSI-E-MODREPLFLK1, error replacing module module-name in 
       library disk:[SYS0.SYSCOMMON.][SYSHLP]HELPLIB.HLB 
    -PCSI-E-MODREPLFLK2, library update failed because it is 
       currently accessed by one or more users 
    -PCSI-E-MODREPLFLK3, after the file is closed, answer YES 
       at the prompt to retry the update
     
    
  2. Either retry the library update operation or terminate the installation:

    3.9.6 Performing the Installation as a Batch Job

    To run the POLYCENTER Software Installation utility as a batch job, include PRODUCT commands in a command procedure file and then submit the file to a batch queue. In the command procedure, include the /CONFIGURATION qualifier to specify an existing PCF so the POLYCENTER Software Installation utility can respond to questions about product options and configuration choices. If you do not specify /CONFIGURATION, the defaults are used.

    Example 3-2 shows how a product might be installed using a command procedure. The example sets and restores VERIFY, and times the installation.

    Example 3-2 Sample Command Procedure for Installing a Product


     
    $ SAVE_PROC_VERIFY = F$ENVIRONMENT("VERIFY_PROCEDURE") 
    $ SAVE_IMAGE_VERIFY = F$ENVIRONMENT("VERIFY_IMAGE") 
    $ SET VERIFY 
    $ ON ERROR THEN GOTO ERROR_EXIT 
    $ START_TIME = F$TIME() 
    $ WRITE SYS$OUTPUT "START TIME -- ''START_TIME'" 
    $ PRODUCT INSTALL CHESSMASTER - 
        /CONFIGURATION=PRODUCER - 
        /HELP - 
        /LOG 
    $ERROR_EXIT: 
    $ END_TIME = F$TIME() 
    $ TEMP = F$VERIFY(SAVE_PROC_VERIFY,SAVE_IMAGE_VERIFY) 
    $ WRITE SYS$OUTPUT "  --------------------------------" 
    $ WRITE SYS$OUTPUT "  END TIME -- ''END_TIME'" 
    $ WRITE SYS$OUTPUT "  START TIME -- ''START_TIME'" 
    $ WRITE SYS$OUTPUT "  --------------------------------" 
    $ EXIT 
    

    3.10 Performing Other Operations on Installed Software Products

    You can perform other operations on installed software products (for example, reconfiguring choices made during the installation, recording changes in volume label, or copying the software to a new location or to different media). You might also want to convert a kit to a new format, display product information, display the contents of a sequentially packaged product kit, or extract any file from a sequentially packaged kit.

    3.10.1 Reconfiguring an Installed Product

    After you install a product, you can change the configuration choices made during the installation. This is called reconfiguration. You choose the options you want; the POLYCENTER Software Installation utility makes all the necessary changes.

    To change the configuration choices for an installed product, use the PRODUCT RECONFIGURE command. The product kit must be present in the user's default directory or specified by the /SOURCE qualifier or by the PCSI$SOURCE logical name.

    3.10.2 Recording a Change in Volume Label in the Product Database

    To record a changed volume label in the product database, enter the PRODUCT REGISTER VOLUME command. You will be prompted for the old volume label and the name of the device where the volume is mounted.

    This command replaces all occurrences of the old volume label with the new volume label. (The POLYCENTER Software Installation utility reads the new label from the disk.)

    Note that PRODUCT REGISTER VOLUME changes the information in the product database only; it does not change the label on the volume. To rename a volume, use the DCL command SET VOLUME. Then use PRODUCT REGISTER VOLUME to record the new name.

    You can also use the PRODUCT REGISTER VOLUME command to record a change in the physical or logical device name.

    3.10.3 Copying a Software Kit to a New Location

    You can use the POLYCENTER Software Installation utility to copy product distribution kits from one location to another. If you transfer a kit from tape to disk, you can change the format from a sequential copy to a reference copy.

    To copy a software kit from one location to another, use the PRODUCT COPY command. Specify the current location with the /SOURCE qualifier and the new location with the /DESTINATION qualifier. For example:

    $ PRODUCT COPY/SOURCE=WORK_DISK:[KITS]/DESTINATION=LOCAL_DISK:[KIT_INSTALL] CMS
    

    3.10.4 Converting a Software Kit from One Format to Another

    You can convert a software kit from reference format (on disk or CD--ROM) to sequential format or from sequential format to reference format by using the /FORMAT qualifier with PRODUCT COPY.

    For example, to convert CMS from sequential format to reference format, enter the following command:

    $ PRODUCT COPY/FORMAT=REFERENCE/SOURCE=MUA1:/DESTINATION=LOCAL_DISK:[KIT_INSTALL] CMS
    

    3.10.5 Retrieving Product Information

    All of the information stored by the product database (PDB) can be accessed by using the SHOW OBJECT, SHOW PRODUCT, and SHOW HISTORY commands. This section describes how to use these commands to retrieve information from the PDB.

    3.10.5.1 Displaying Information About Objects

    To display information about the managed objects (for example, files, accounts, and directories) associated with the products installed on your system, use the SHOW OBJECT command. Table 3-10 lists questions that can be answered with SHOW OBJECT.

    Table 3-10 SHOW OBJECT Command: Displaying Managed Object Information
    Question Command
    What files or other objects did this product create? PRODUCT SHOW OBJECT * /PRODUCT= product-name
    What product created this file or other object? PRODUCT SHOW OBJECT object-name/FULL

    3.10.5.2 Displaying Information About the Products

    You can obtain information about products installed on your system with the SHOW PRODUCT and SHOW HISTORY commands. Table 3-11 lists some of the questions that can be answered with these commands.

    Table 3-11 SHOW PRODUCT and SHOW HISTORY Commands: Displaying Product Information
    Question Command
    Which products have been installed? PRODUCT SHOW HISTORY */OPERATION=INSTALL
    PRODUCT SHOW PRODUCT *
    Product interdependencies: Is product A referenced by product B? PRODUCT SHOW PRODUCT A/FULL
    PRODUCT SHOW PRODUCT */REFERENCED_BY= B
    Which user installed a product? PRODUCT SHOW HISTORY product-name /FULL
    Which products were installed before March 31, 1996? PRODUCT SHOW HISTORY */BEFORE=31-MAR-1996
    Were any software patches applied to a product? PRODUCT SHOW PRODUCT product-name/FULL

    3.11 Removing Installed Software Products and Kits

    When you use the POLYCENTER Software Installation utility to remove an installed product, all of the files, accounts, and other objects that were created for the product when it was installed are removed from your system and from the product database.

    To remove an installed product, enter PRODUCT REMOVE. For example:

    $ PRODUCT REMOVE CMS
    


    Chapter 4
    Starting Up and Shutting Down the System

    This chapter describes various ways to start up and shut down your system.

    To initiate startup of your system, you boot it. Many systems have unique booting commands. For detailed booting instructions for your system, see the following manuals:

    Information Provided in This Chapter

    This chapter describes the following tasks:
    Task Section
    Booting with modified system parameter values Section 4.2
    Assigning port allocation classes with SYSBOOT Section 4.3
    Booting in an emergency Section 4.4
    Booting with controlled startup Section 4.5
    Solving booting problems Section 4.6
    Writing a new boot block on the system disk Section 4.7
    Performing an orderly shutdown with SHUTDOWN.COM Section 4.8.1
    Customizing SHUTDOWN.COM to perform site-specific operations Section 4.8.3
    Performing an orderly shutdown with SYSMAN Section 4.8.4
    Performing an emergency shutdown with the OPCCRASH.EXE program Section 4.8.5
    Performing an emergency shutdown using console commands Section 4.8.6

    This chapter explains the following concepts:
    Concept Section
    Booting and startup processes Section 4.1.1
    Nonstop boot: the most common booting operation Section 4.1.2.1
    Conversational boot: for special booting functions Section 4.1.2.2
    System startup and STARTUP.COM Section 4.1.3
    System shutdown procedures Section 4.8
    The order of shutdown events Section 4.8.2

    4.1 Understanding Booting and System Startup

    Booting is the process of loading system software from the system disk into processor memory. When you boot your system, it automatically performs a series of tasks to start up your system. These tasks are collectively known as system startup.

    You must have installed the operating system before you boot the system for the first time.

    Booting procedures vary for different computers. For example, computers with console storage devices use a boot command procedure. You can copy and edit this command procedure to specify the location of the system disk. Other computers have an internal memory device that provides the name of the system disk.

    On Alpha systems, you cannot boot from a magnetic tape device.

    4.1.1 Booting and Startup Processes

    Together, the booting and startup processes comprise the following steps:

    1. You enter the BOOT command. The boot block, a fixed location on disk, points to the primary bootstrap image, which is loaded from disk into main memory.
      On VAX systems, the primary bootstrap image is VMB.EXE.
      On Alpha systems, the primary bootstrap image is APB.EXE.
      The primary bootstrap image allows access to the system disk by finding the secondary bootstrap image, SYS$SYSTEM:SYSBOOT.EXE, and loading it into memory.
    2. SYSBOOT.EXE loads the system parameters stored in the default parameter file into memory. (For more information on the default parameter file and loading of system parameters at boot time, see Section 4.2.)
      If you are performing a conversational boot, the procedure stops and displays the SYSBOOT> prompt. (For information on conversational booting, see Section 4.1.2.2.) Otherwise, SYSBOOT.EXE loads the operating system executive into memory and transfers control to the executive.
    3. When the executive finishes, it executes the SWAPPER process.
    4. The SWAPPER creates the SYSINIT process.
    5. Among other actions it performs, SYSINIT creates the STARTUP process.
    6. STARTUP executes SYS$SYSTEM:STARTUP.COM (unless you indicated another file using SYSMAN, SYSGEN, or conversational boot). STARTUP.COM executes a series of other startup command procedures, including SYSTARTUP_VMS.COM. (For more information on STARTUP.COM, see Section 4.1.3. For more information on other startup procedures, see Section 5.2.1.)
      The current values of system parameters are written back to the default parameter file.
    7. The boot process finishes, and you can log in to the operating system.

    4.1.2 Types of Booting Operations

    You can perform the following types of booting operations:
    Type Purpose For More Information
    Nonstop boot To boot without stopping to perform special operations. Use this kind of boot in most cases. Section 4.1.2.1
    Conversational boot To perform special boot operations---for example, to change system parameters before booting. Section 4.1.2.2

    4.1.2.1 Nonstop Boot: The Most Common Booting Operation

    The most common boot operation is a nonstop boot from the system disk. You perform a nonstop boot after changing certain system parameters or installing certain layered products, or after a standalone backup.

    Follow the instructions for a nonstop boot in either of the following manuals:

    4.1.2.2 Conversational Boot: For Special Booting Functions

    A conversational boot is used in programming research and development environments where you must alter operating conditions for experimentation, testing, and debugging. Use a conversational boot to perform the following operations:
    Operation For More Information
    Boot after showing or modifying individual system parameter values.¹ Section 4.2.1
    Boot using system parameter values from an alternate parameter file.¹ Section 4.2.2
    Boot with default values for system parameters; for example, when modified system parameter values have caused the system to become unbootable.¹ Section 4.4.1
    Boot without running startup or login procedures; for example, when modified startup or login procedures have caused the system to become unbootable. Section 4.4.2
    Boot without the user authorization file; for example, when the user authorization file has been modified so that you cannot log in. Section 4.4.3
    Boot with an alternate site-independent startup procedure. Section 4.5.1
    Boot with a minimum startup. Section 4.5.3
    Display startup procedure commands while booting. Section 4.5.4


    ¹In most cases, Digital recommends that you use AUTOGEN to modify system parameters. In special cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, see |hotspot#353|.


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

    [HR]

      6017P006.HTM
      OSSG Documentation
      22-NOV-1996 14:21:24.76
    

    Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

    Legal