HP OpenVMS Systems Documentation
OpenVMS System Manager's Manual
5.2.5 Modifying SYLOGICALS.COM to Define Systemwide Logical Names
A systemwide logical name applies to the entire system. It is defined in the system logical name table and can be used by any process in the system. A clusterwide system logical name applies to every node in the cluster at a system level. It is defined in the clusterwide system logical name table of every node and can be used by any process in the system.
In general, system managers edit the SYLOGICALS.COM command procedure to define site-specific logical names that take effect at system startup. However, this is not the appropriate command procedure for defining clusterwide logical names, which is, rather, SYSTARTUP_VMS.COM. Refer to "Preparing a Shared Environment" in OpenVMS Cluster Systems for more information.
As supplied by Compaq, SYLOGICALS.COM contains commands that assign systemwide logical names on a MicroVAX system that is not in an OpenVMS Cluster environment. If your system is not a standalone MicroVAX system, you can ignore the procedure at the beginning of the template file and add systemwide logical name assignments to the end of the file.
You can add commands to create your own site-specific systemwide logical names. In addition, if you want to change default definitions for the following system logical names, you can include the definitions in SYLOGICALS.COM. Table 5-2 lists some commonly defined logical names.
Compaq recommends that you define logical names for system components (for example, public disks and directories) in executive mode, using the /EXECUTIVE_MODE qualifier with the ASSIGN or DEFINE command. This type of logical name, known as a trusted logical name, is available during system operations such as the activation of privileged mode images (LOGINOUT, Mail, and so on).
For detailed information about logical name assignments and the privilege modes (executive, kernel, supervisor, and user), refer to the OpenVMS User's Manual.
In this example, any user on the system (and any program running on the
system) could use the name FINANCE_DISK (the logical name) in place of
DRAC$DRA2: (the physical device name). Similarly, you can refer to the
system disk (SYS$SYSDEVICE:) as SYSDSK.
SYSECURITY.COM runs prior to starting the security audit server process. You can add commands to this file to mount or define any disks that you want to hold security auditing log files or local security archive files. For more information about security auditing, see Section 20.7.
To inhibit the automatic startup of auditing, edit the SYS$MANAGER:SYLOGICALS.COM command procedure to add the following line:
Then you can initiate auditing during another phase of system startup, perhaps at the end of SYSTARTUP_VMS.COM, by editing the command file to add the following line:
For information about editing SYSTARTUP_VMS.COM, see Section 5.2.7.
To perform any site-specific command not performed by another startup command procedure, you can add or modify commands in the general-purpose, site-specific startup command procedure, SYSTARTUP_VMS.COM.
To modify SYSTARTUP_VMS.COM, perform the following steps:
184.108.40.206 Mounting Public Disks
A public volume is a disk that any process on the system can access. To make disks available for public use, you must perform the following tasks:
Add MOUNT commands in the following format to the command procedure:
The /SYSTEM qualifier makes the disk available for systemwide access.
Note that, by default, the system creates the following logical name when you use the MOUNT command:
In many cases, using the default logical name will meet your needs.
When mounting disks in a startup command procedure, do not specify the /CLUSTER qualifier, even in a VAXcluster or an OpenVMS Cluster environment. Each node executes its own startup command procedure, so each node mounts disks for itself.
For more information about public volumes, see Section 9.1.4 and
Section 9.5. For more information about the MOUNT command, refer to
the MOUNT section of the OpenVMS System Management Utilities Reference Manual.
If you have any disks that must be mounted early in startup, you can
add MOUNT commands to SYCONFIG.COM. For example, your site might
require that certain files be available before SYSTARTUP_VMS.COM
executes. For more information about SYCONFIG.COM, see Section 5.2.4.
To establish the device characteristics of the terminals and printers on the system, use a series of SET commands in your startup command procedure. For more information about the commands you use to set up devices, see Section 8.6.1 and Section 8.8.1.
If your configuration is simple, you can add the commands to
SYSTARTUP_VMS.COM. If your configuration requires a large number of
commands, create a separate command procedure (for example,
DEVICE_SETUP.COM) and execute it from SYSTARTUP_VMS.COM. When the
device setup command procedure finishes executing, control returns to
You should add commands to SYSTARTUP_VMS.COM to perform the following tasks:
If your configuration is simple, you can add these commands to SYSTARTUP_VMS.COM. On systems with a large number of queues, you might want to include the commands in a separate file named, for example, STARTQ.COM, and include a command in SYSTARTUP_VMS.COM to invoke the queue startup command procedure. The autostart feature simplifies queue startup, and allows you to start queues with fewer commands. Compaq recommends you use autostart queues whenever possible to simplify queue startup. For more information about autostart queues, see Section 14.1.3.
You can install commonly used programs as known images to reduce the I/O overhead in activating those images and to assign attributes or privileges to the images. Use the Install utility (INSTALL) to install known images, which you must reinstall each time the system boots.
STARTUP.COM includes a series of INSTALL commands that install certain system programs as known images. You should include any site-specific INSTALL commands in SYSTARTUP_VMS.COM to install images each time the system boots.
For information about installing known images, see Section 17.9.
The following example shows a command sequence you might include in SYSTARTUP_VMS.COM for installing additional known images:
220.127.116.11 Installing Resident Images (Alpha Only)
Resident images must be installed each time the system boots. You can
add commands to SYSTARTUP_VMS.COM to automatically perform this task.
Section 17.9.6 explains how you can use the Install utility (INSTALL) to
install resident images on Alpha systems.
You run the System Dump Analyzer utility (SDA) each time the system boots to analyze the system crash dump in case the system failed the last time it was running. You can do this by adding command lines to SYSTARTUP_VMS.COM.
For details, see Section 16.11 and the OpenVMS VAX System Dump Analyzer Utility Manual and the OpenVMS Alpha System Dump Analyzer Utility Manual.
The following commands, executed in SYSTARTUP_VMS.COM, invoke SDA, save and analyze the crash dump, and print a listing file:
18.104.22.168 Purging the Operator Log File
Each time you reboot the system, you create a new version of the operator log file, OPERATOR.LOG. You should devise a plan for regular maintenance of the versions of this file. Add the following command to SYSTARTUP_VMS.COM to purge all but the last two versions of the operator log file:
For more information about the operator log file, see Section 20.6.1.
Your site might have batch jobs that you want to submit at system startup time. To submit such batch jobs, add SUBMIT commands in the following format to SYSTARTUP_VMS.COM:
The following example submits a batch job to run a command procedure each time the system boots. The job is submitted at a high priority to make sure the job is scheduled before any batch jobs users might submit. If possible, submit startup batch jobs at high priority in this way before you start the batch queue.
Usually, the last command in SYSTARTUP_VMS.COM announces to all terminals that the system is up and running:
Before the procedure exits, you can provide site-specific definitions for one or both of the logical names SYS$ANNOUNCE and SYS$WELCOME. Whenever a user logs in, the user's terminal screen displays the messages associated with SYS$ANNOUNCE and SYS$WELCOME.
You can define SYS$ANNOUNCE to print an announcement at the beginning of the login procedure for each user. The text prints immediately after a successful dial-in, Ctrl/Y, or carriage return is received. It also prints on LAT terminals when a user connects to a service using the CONNECT command. The text can contain up to 63 characters. For longer messages, precede the name of a text-containing file with an at sign (@) so that the login command procedure prints the entire file as an announcement.
Or you might prefer to print a file by including the following command:
You can define SYS$WELCOME to display a welcome message whenever a user logs in. The text prints immediately after the user enters the correct password. The text can contain up to 63 characters. For longer messages, precede the name of a text-containing file with an at sign (@) so that the login command procedure displays the entire file as a welcoming announcement.
If you prefer to display the contents of a file containing a message, you could use the following line in the procedure:
If you do not explicitly define SYS$WELCOME, the terminal displays a standard welcome message similar to the following one:
You can add the DECnet node name to this message by including a translation of the logical name SYS$NODE. When DECnet starts, it creates the logical name assignment for SYS$NODE.