You can customize the system to meet your site-specific needs.
In addition, if your Integrity server is part of an OpenVMS Cluster
environment, you must prepare the cluster environment and configure
the cluster. The following subsections describe the customization
tasks you can perform at this time. In general, these tasks apply
to new installations only; however, in some cases, they apply to
upgrades. The tasks are as follows:
For instructions on customizing the system, review the following
The release notes, for notes and restrictions
that might be relevant to your customization plans
The HP OpenVMS System Manager's Manual, for instructions
on customizing and using your system
Note that other customization tasks are described later in
Network Proxy Authorization Files
After a new installation of OpenVMS that includes DECnet,
or after an upgrade in which you have added DECnet, create your
network proxy authorization files. These files include security
authorization information for users using network proxy accounts.
If you do not create these network authorization files before starting
up your system, you might see messages such as the following during
Message from user SYSTEM on HOMER
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
The NET$PROXY.DAT file is the primary network proxy authorization
file. The other network authorization file to be created is NETPROXY.DAT.
To create the network proxy authorization files, enter the following commands:
$ SET DEFAULT SYS$COMMON:[SYSEXE]
$ MC AUTHORIZE CREATE/PROXY
$ SET DEFAULT SYS$LOGIN
For more information about network proxy accounts and files,
see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. For more information
about the Authorize utility, see the HP OpenVMS System Management Utilities Reference Manual: A--L.
Up the Queue Manager and Default Queues
The initial installation of OpenVMS does not create the queue
manager or any queues. HP recommends that you create the queue
manager and your default batch and print queues now. When you install
layered products (as described in “Installing and Configuring
Layered Products (New Installations, Some Upgrades)”), some of these products expect such queues
to be present or try to create queues themselves.
To set up the queue manager and a batch queue, enter the following
commands at the DCL prompt:
$ START QUEUE /MANAGER /NEW_VERSION
$ INITIALIZE /QUEUE /START /BATCH SYS$BATCH
As noted, the queue manager starts automatically the next
time you boot your OpenVMS system. To have the SYS$BATCH queue
start automatically, edit the line in the SYS$STARTUP:SYSTARTUP_VMS.COM
file that starts the SYS$BATCH queue by removing the exclamation
mark (!) and, if present, the extra dollar sign ($). The following
example shows the line before and after editing. In that section,
you can also define a default system print queue (SYS$PRINT).
Before: $!$ START /QUEUE SYS$BATCH
After: $ START /QUEUE SYS$BATCH
For more information about starting and creating queues, see
the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
Configuring a Multihead
A multihead configuration consists of a single system (such
as an HP AlphaServer ES40) that supports multiple graphics options.
A graphics option consists of a graphics controller (card) and
a graphics display interface (monitor).
Your system can be configured automatically for multihead
use if you copy the private server setup template file to a command
procedure file type (.COM). The DECwindows Motif server loads this
command procedure on startup or restart.
To set up your system for multihead support, perform these
After installing the DECwindows Motif software
on your system, log in to your system.
Copy the private server setup template file to a new
.COM file by entering the following command:
$ COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE
Restart the DECwindows server by entering the following
$ @SYS$STARTUP:DECW$STARTUP RESTART
For more information about customizing your DECwindows environment
using the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file, see the
most recent version of the DECwindows Motif for OpenVMS Installation Guide and Managing DECwindows Motif for OpenVMS Systems.
If you installed DECnet, or if you added DECnet during an
upgrade, you must now configure DECnet. Follow the instructions
provided for the version of DECnet you installed. To use either
version of DECnet, you must first register and load the license
for the product. If you have not yet done this, perform the steps
described in “Registering Your
If you installed DECnet-Plus for OpenVMS software, see the DECnet-Plus for OpenVMS Release Notes and the HP
DECnet-Plus for OpenVMS Installation and Configuration manual
for information about how to configure this software using the NET$CONFIGURE
If you installed DECnet Phase IV, see the DECnet for OpenVMS Guide to Networking manual
for information about configuring this software using the NETCONFIG
Once you have configured DECnet Phase IV, edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM
so that the software starts when the system reboots. (This step
is not required if you are running DECnet Phase V.) You can have
the software start interactively or in batch mode by making one
of the following changes:
Before: $!$ START/NETWORK DECNET
After: $ START/NETWORK DECNET
|Batch mode:|| |
Before: $!$ SUBMIT SYS$MANAGER:STARTNET.COM
After: $ SUBMIT SYS$MANAGER:STARTNET.COM
|IMPORTANT: If you intend to run DECnet Phase IV with
a TCP product, DECnet must start first. In this case, HP recommends
starting DECnet using interactive mode.|
For information about editing STARTUP-VMS.COM, see “Updating SYSTARTUP_VMS.COM to Start Layered
Products and Print Queues”.
and Configuring Third-Party Networking Software
You need networking software to download patches and as a
requirement for certain layered products. If you are using neither
DECnet nor TCP/IP Services for OpenVMS, you should install and configure
third-party networking software now. See the appropriate vendor’s