skip book previous and next navigation links
go up to top of book: HP OpenVMS System Manager's Manual, Volume 1:... HP OpenVMS System Manager's Manual, Volume 1:...
go to beginning of chapter: Customizing the Operating System Customizing the Operating System
go to previous page: Modifying Login Command Procedures to Customize User Environments Modifying Login Command Procedures to Customize User Environments
go to next page: Registering Images that Have System Version DependenciesRegistering Images that Have System Version Dependencies
end of book navigation links

Customizing Startup Databases with SYSMAN  



Startup databases contain information used to start up system software. For example, STARTUP.COM uses information in a startup database named STARTUP$STARTUP_VMS to start the OpenVMS operating system. It uses information in a startup database named STARTUP$STARTUP_LAYERED to start layered products. For more information about startup databases, see Understanding Startup Databases.

You can use the STARTUP command of the System Management utility (SYSMAN) to customize startup databases as follows:

The following sections describe these tasks.

Before performing these tasks, it helps to understand SYSMAN. For more information about SYSMAN, see Understanding SYSMAN. You should also understand startup databases, in particular, the layered product startup database. For information, see Understanding Startup Databases and Understanding the Layered Product Startup Database.

Understanding Startup Databases  

Three startup database files are provided with the operating system, in the location defined by the logical name SYS$STARTUP:

File Description
VMS$PHASES.DAT
Determines the order of the phases of startup in a sequential list. This file includes a series of four basic phases (INITIAL, CONFIGURE, DEVICE, and BASEENVIRON) needed to bring the operating system up to a basic working environment, followed by a series of phases for layered products. STARTUP.COM uses this list of phases for startup. Do not modify this file.
VMS$VMS.DAT
Equivalent to the logical name STARTUP$STARTUP_VMS. This file contains information about the files used to start the base operating system environment during system startup. Do not modify this file.

STARTUP$STARTUP_VMS is provided for your information only. Use SYSMAN to display information in this file. For more information, see Showing the Contents of a Startup Database.
VMS$LAYERED.DAT
Equivalent to the logical name STARTUP$STARTUP_LAYERED. This file contains information about files that start site-specific products and layered products. The system uses the information in this file to start layered products during system startup. Understanding the Layered Product Startup Database provides more information about this file.

Use SYSMAN to modify this file so that it contains information about all the layered product startup files you want to execute on your system.

If you have site-specific software that you want to manage separately from your layered products, you can use SYSMAN to create an additional startup database.

Understanding the Layered Product Startup Database  

The layered product startup database file (referred to by the logical name STARTUP$STARTUP_LAYERED) lists the files and command procedures that start site-specific products and layered products. It contains the following characteristics of each startup file:

Specifying the Current Startup Database  

With SYSMAN, the current database is the one that will be the target for the SYSMAN commands.

You can display or modify STARTUP$STARTUP_LAYERED or database files that you create. You can display STARTUP$STARTUP_VMS, but you should not modify it.

By default, the layered product database is the current database. To perform commands on another database, specify it as the current database by entering the STARTUP SET DATABASE command in the following format:STARTUP SET DATABASE database

where database specifies the name of the database.

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_LOCAL
%SYSMAN-I-NEWCOMPFIL, current component file is now STARTUP$STARTUP_LOCAL

Showing the Name of the Target Startup Database  

To display which database is the target database, enter the STARTUP SHOW DATABASE command.

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP SHOW DATABASE

Showing the Contents of a Startup Database  

To display the contents of the current database, enter the STARTUP SHOW FILE command. You can specify various qualifiers for this command to control the amount of information displayed. For more information, refer to the HP OpenVMS System Management Utilities Reference Manual.

Example

$  RUN SYS$SYSTEM:SYSMAN               
SYSMAN> STARTUP SHOW FILE/FULL

Adding Startup Files to a Startup Database  

To add a file to the layered product startup database, use the STARTUP ADD command. The /MODE qualifier specifies the mode of execution for the file. The /PHASE qualifier specifies the phase within system startup when the file is to be executed. For information about the layered product startup phases, see Understanding the Layered Product Startup Database.

Do not use this command to modify STARTUP$STARTUP_VMS; this command procedure starts the operating system. The STARTUP MODIFY command requires read and write access to the startup database.

When adding layered product startup files using SYSMAN, be sure that all requisite components occur in a previous phase.

Enter the STARTUP ADD command with appropriate qualifiers. For information about the valid qualifiers, refer to the SYSMAN section of the HP OpenVMS System Management Utilities Reference Manual: M--Z

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP SHOW DATABASE
%SYSMAN-I-DATANAME, STARTUP database is STARTUP$STARTUP_LAYERED
SYSMAN> STARTUP ADD FILE/MODE=DIRECT/PHASE=LPMAIN FOR$LPMAIN_043_STARTUP.COM

Changing Information Associated with a Startup File  

Once a file is included in the layered product startup database, you can modify the information associated with the file by entering the STARTUP MODIFY command. (The command requires read and write access to the startup database.)


NoteDo not use STARTUP MODIFY to modify STARTUP$STARTUP_VMS.

You can specify any of the following qualifiers to specify the information that is to be changed:

For information about the qualifiers for this command, refer to the HP OpenVMS System Management Utilities Reference Manual: M--Z.

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP ADD/MODE=DIRECT/PHASE=LPMAIN FOR$LPMAIN_043_STARTUP.COM
SYSMAN> STARTUP SHOW FILE/NODE
SYSMAN> STARTUP MODIFY FILE FOR$LPMAIN_043_STARTUP.COM/NODE=ZNODE

Deleting a Record from a Startup Database  

Deleting a record from a startup database prevents a product from starting up. To delete a record, use the STARTUP REMOVE FILE command. This command leaves the startup file intact, but the file is not used in system startup. (The command requires read and write access to the startup database.)


NoteDo not use STARTUP REMOVE FILE to modify STARTUP$STARTUP_VMS.

To delete a record from a startup database, enter a STARTUP REMOVE FILE command in the following format:STARTUP REMOVE FILE filespec

where filespec specifies the name of the startup file to be removed.

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP SHOW FILE/FULL
SYSMAN> STARTUP REMOVE FILE FOR$LPMAIN_043_STARTUP.COM
SYSMAN> STARTUP SHOW FILE/FULL
SYSMAN> EXIT

Preventing a Startup File from Executing  

To temporarily prevent a startup file from executing, enter the STARTUP DISABLE command. You can specify the /NODE qualifier to disable the startup file on certain nodes.

This command requires read and write access to the startup database. Do not use this command to modify STARTUP$STARTUP_VMS.

To delete a record from a startup database, enter the STARTUP DISABLE command as follows:STARTUP DISABLE FILE filespec

where filespec specifies the name of the startup file to be disabled.

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP SHOW FILE
SYSMAN> STARTUP DISABLE FILE FOR$LPMAIN_043_STARTUP.COM/NODE=ZURICH

Allowing a Previously Disabled Startup File to Execute  

If you have disabled a startup file from executing, you can enable it again by using the STARTUP ENABLE command. You can specify the /NODE qualifier to enable the startup file on certain nodes.

This command requires read and write access to the startup database. Do not use this command to modify STARTUP$STARTUP_VMS.

To enable a previously disabled file, enter the STARTUP ENABLE FILE command in the following format:STARTUP ENABLE FILE filespec

where filespec specifies the name of the file to be enabled.

Example

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP ENABLE FILE FOR$LPMAIN_043_STARTUP.COM/NODE=ZURICH

go to previous page: Modifying Login Command Procedures to Customize User Environments Modifying Login Command Procedures to Customize User Environments
go to next page: Registering Images that Have System Version DependenciesRegistering Images that Have System Version Dependencies