HP OpenVMS Systems Documentation
OpenVMS System Manager's Manual
3.9.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.
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:
3.9.4 Converting a Software Kit from One Format to Another
For example, to convert CMS from sequential format to reference format, enter the following command:
3.9.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.
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-8 lists questions that can be answered with SHOW OBJECT.
22.214.171.124 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-9 lists some of the questions that can be answered with these commands.
3.10 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:
|Deferring memory testing on AlphaServer 4100 computers||Section 4.1.2|
|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:
|Booting and startup processes||Section 4.1.1|
|Nonstop boot: the most common booting operation||Section 126.96.36.199|
|Conversational boot: for special booting functions||Section 188.8.131.52|
|System startup and STARTUP.COM||Section 4.1.4|
|System shutdown procedures||Section 4.8|
|The order of shutdown events||Section 4.8.2|
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
To speed up the time between system power-on and user login, you can now defer a portion of memory testing on AlphaServer 4100 computers. When you choose this option, the console tests a minimum amount of memory and leaves the rest for the operating system to test.
|FULL (off)||The console does all the testing.|
|NONE||32 MB of memory are tested before booting.|
|PARTIAL||256 MB of memory are tested before booting.|
If you set MEMORY_TEST to NONE or PARTIAL, OpenVMS tests any remaining untested memory on an as-needed basis at either or both of the following times:
When you change the value of MEMORY_TEST, you must issue the INIT console command before the new value takes effect. Therefore, you need to follow these steps from the console before booting:
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 184.108.40.206|
|Conversational boot||To perform special boot operations---for example, to change system parameters before booting.||Section 220.127.116.11|
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:
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. 1||Section 4.2.1|
|Boot using system parameter values from an alternate parameter file. 1||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. 1||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|
Immediately after your system boots, it runs the site-independent command procedure SYS$SYSTEM:STARTUP.COM to start up the system and control the sequence of startup events. This section describes STARTUP.COM.
Do not modify SYS$SYSTEM:STARTUP.COM. This file is deleted and replaced each time you upgrade your system to the next version of the operating system. Leaving STARTUP.COM intact prevents you from inadvertently altering any commands in the file, which in turn could cause the startup procedure to fail.
Although you should not modify STARTUP.COM, sometimes you may want to control site-independent startup when booting your system. For information, see Section 4.5.
For information about site-specific startup command procedures, see
4.1.5 Messages Indicating Booting and Startup Progress
The OpenVMS system is now executing the system startup procedure.
The OpenVMS system is now executing the site-specific system startup commands.
%SET-I-INTSET, login interactive limit=64, current interactive value = 0 19-APR-2000 15:00:00.00 SYSTEM job terminated at 19-APR-2000 15:00:00.00 Accounting information: Buffered I/O count: 133 Peak working set size: 401 Direct I/O count: 12 Peak pagefile size: 2379 Page faults: 325 Mounted volumes: 0 Charged CPU time: 0 00:00:55.23 Elapsed time: 0 00:01:31.24
Using a conversational boot, you can modify system parameter values as follows:
|Task||For More Information|
|Boot after showing or modifying individual system parameter values||Section 4.2.1|
|Boot with an alternate system parameter file||Section 4.2.2|
|Boot with default values for system parameters||Section 4.4.1|
|Active values||System parameter values stored in memory and used by the active system.|
|Current values||System parameter values stored in the default parameter file. When the system boots, it sets active values for system parameters using the current values.|
|+On VAX systems, the default system parameter file is SYS$SYSTEM:VAXVMSSYS.PAR.|
|++On Alpha systems, the default system parameter file is SYS$SYSTEM:ALPHAVMSSYS.PAR.|
|Default values||System parameter values stored in the default list and used by default.|
For more information about system parameters, see Section 15.1.