 |
» |
|
|
|
After you have installed or upgraded the OpenVMS
operating system, you must perform several important tasks to prepare
the system for operation. Section 7.1 includes a checklist that you can use to
make sure you perform all the postinstallation or postupgrade tasks
necessary for your system. Use the checklist in Table 7-1 to ensure that you perform all necessary postinstallation
or postupgrade tasks. Unless indicated otherwise, these tasks are
applicable as both postinstallation and postupgrade tasks. Table 7-1 Postinstallation and Postupgrade Checklist | | Task | Section |
|---|
| For a newly
installed system disk, you can back up the disk. (At this point, you
could reinstall OpenVMS onto the disk instead.) For a
newly upgraded system disk, if it is not going
to be a shadow set member, back up the system disk as a safeguard
before proceeding with the next steps. If your newly upgraded system
disk is going to be a shadow set member, you can re-form it in a later
step. As an optional precaution, you can back up the system disk
as well. | Section 7.2 | | Register any
licenses that were not registered during the installation; for an
upgrade, register any new licenses. | Section 7.3 | | New
installations only (optional): Set system parameters to
enable volume shadowing. | Section 7.4 | | If you set system
parameters to enable volume shadowing or removed hardcoded BAP system
parameters, run AUTOGEN and reboot. | Section 7.5 | | If you want to
form a shadow set for a newly installed system disk, you can do this
now or later. If you upgraded a disk in a volume shadowing environment,
re-form the shadow set. | Section 7.6 | | New
installations, some upgrades: Perform the following tasks
that generally apply to new installations only but could also apply
after an upgrade: | | | | | Create proxy files,
if required. | Section 7.7.1 | | | | Set up the queue manager
and start the default batch and print queues. | Section 7.7.2 | | | | Configure a multihead system,
if applicable. | Section 7.7.3 | | | | Configure DECnet if
it was installed. After an upgrade, perform only if DECnet was added
during the upgrade. | Section 7.7.4 | | | | Configure TCP/IP Services
for OpenVMS if it was installed. After an upgrade, configure TCP/IP
Services only if it was added during the upgrade. | Section 7.7.5 | | | | If you are using neither
DECnet nor TCP/IP Services, install and configure third-party networking
software, if necessary. Networking software is required to download
patches and for certain layered products. | Section 7.7.6 | | Initialize or
configure the following products, as needed: | | | | | Initialize CDSA. | Section 7.8.1 | | | | Configure Availability Manager. | Section 7.8.2 | | | | Configure Kerberos. | Section 7.8.3 | | | | Configure SSL for OpenVMS. | Section 7.8.4 | | | | On Integrity servers using
services that depend on WBEM Services for OpenVMS, configure WBEM
Services for OpenVMS. | Section 7.8.5 | | | | On Integrity servers using
services that depend on WBEM Providers, configure WBEM Providers for
OpenVMS. | Section 7.8.6 | | | | On Integrity servers that
use Instant Capacity (iCAP) or Temporary Instant Capacity (TiCAP), configure
the iCAP software. | Section 7.8.7 | | | | On Integrity servers that
use Pay per use (PPU), configure the PPU software. | Section 7.8.8 | | | | On Integrity servers that
use HP SIM services, configure HP SIM. | Section 7.8.9 | | | | Initialize and run the Performance
Data Collector base software (TDC_RT). | Section 7.8.10 | | | | Prepare your OpenVMS system
and your PC to run OpenVMS Management Station, and follow procedures
in Appendix G. | Section 7.8.11 | | | | Install OpenVMS Debugger
clients on a PC. | Section 7.8.12 | | Create or edit
a system-specific or clusterwide login welcome message SYS$MANAGER:WELCOME.TXT
(optional). | Section 7.9 | | Upgrades
only: Examine command procedures for which the upgrade
may have provided new template files. | Section 7.10 | | Add and remove
operating system files (optional). | Section 7.11 | | If necessary,
compress the system libraries using LIBDECOMP.COM (optional, HP recommends
keeping libraries in expanded format). | Section 7.12 | | Download and
apply any relevant OpenVMS or networking patches that are available
(optional but recommended). | Section 7.13 | | New
installations, some upgrades: Install and configure layered
products. | Section 7.14 | | New
installations, some upgrades: Create print queues. | Section 7.15 | | Update SYSTARTUP_VMS.COM
to have layered products, print queues, and other products or devices
start at boot. | Section 7.16 | | Installations
and possibly upgrades: Create user accounts. | Section 7.17 | | Run the User Environment Test Package (UETP) to test the system (optional). | Section 7.18 | | Back up the system
disk and start a systematic routine for backing up the application,
data, and user disks. | Section 7.19 | | If the system disk was pulled out of the shadow set and all the appropriate
postupgrade steps recommended in this chapter thus far were performed
on that disk, then re-form the shadow set once again. | Section 7.20 | | Upgrades
only: Reboot cluster members, if applicable. | Section 7.21 | | Tune your operating
system: After the system has run for at least 24 hours with users
or a typical application workload on the system, run AUTOGEN to collect
feedback. If necessary, modify the MODPARAMS.DAT file. | Section 7.22 Section 7.23 |
Unless your newly installed or upgraded system
disk will be part of a shadow set, HP recommends that you back up
the system disk before performing the tasks described in this chapter.
If you encounter problems while performing any of these tasks, having
a backup copy of the system disk ensures that you can restore it to
a known condition without having to repeat the installation or upgrade. If your system disk will be part of a multiple-member
shadow set, then a backup is not necessary. Either form or re-form
the shadow set, as described in Section 7.6; this creates a backup copy of the newly
installed or upgraded system disk through the shadow copy operation.
Remember to dismount any added shadow set members after the shadow
copy has completed, complete any steps described in this chapter that
you need to perform and, when you are finished, re-form the shadow
set. If your newly installed or upgraded system disk
will not be in a shadow set, back up the system disk by performing
the following steps. (For a newly installed system disk, it might
be just as easy to reinstall the operating system.) Shut
down the system (as described in Section A.7.2). Boot
the operating system media, as described in Section 3.2. Use
the OpenVMS operating system menu to enter the DCL environment (option
8). Mount
the system device and the target device on which you are making the
backup copy. (If you are backing up to tape, skip to the next step.)
For example, if your system disk is on DKA0: and the target device
is on DKA100:, you might use the following commands (colons are required).
The /OVERRIDE qualifier used in this example enables you to mount
the system disk without entering its volume label. The /FOREIGN qualifier
is required for the target disk when you use the BACKUP /IMAGE command.
$$$ MOUNT /OVERRIDE=IDENTIFICATION DKA0:
$$$ MOUNT /FOREIGN DKA100:
$$$ BACKUP /IMAGE /LOG DKA0: DKA100: |
To
back up the system disk to a magnetic tape, enter the following commands,
where MTA0: is the magnetic tape drive and label is the volume label. Note that the BACKUP command automatically
mounts the tape and begins the backup to it. $$$ INITIALIZE MTA0: label
$$$ MOUNT /OVERRIDE=IDENTIFICATION DKA0:
$$$ BACKUP /IMAGE /LOG DKA0: MTA0:label.BCK |
The /IMAGE qualifier causes the Backup utility to produce a functionally
equivalent copy of the system disk, which is also bootable. The /LOG
qualifier causes the procedure to display the specification of each
save set file being processed. To compare the backed up files to
the source files, use the /VERIFY qualifier. If any discrepancies
are detected, the Backup utility displays an error message. Log
out from the DCL environment. Shut
down the system by selecting option 9 on the menu. Boot
from the disk on which you either upgraded or installed OpenVMS.
In addition to backing up the system disk now
before you customize it, you should back up your system disk again
after you successfully complete your customization tasks and install
layered products. For more complete information about backup operations,
including a description of an alternative method that does not require
booting from the operating system media and that enables you to back
up a shadowed disk without disabling the shadow set, see Appendix E. For more information
about the Backup utility, see the HP OpenVMS System Management Utilities Reference Manual: A-L. If you did not register your OpenVMS licenses
during the installation, you must do so before you can use the OpenVMS
operating system. You must also register the licenses for OpenVMS
layered products. If your operating system came preinstalled, you
must register licenses. The licenses are not preinstalled. If you
plan to form a volume shadow set for your newly installed system disk,
you must enter and load the VOLSHAD license. If you have upgraded your operating system, register
any new OpenVMS or layered product licenses. For OpenVMS I64 systems, a single OE license grants
the right to use all the components bundled in the purchased OE.
Each OE is offered with Per Core Licenses (PCLs). For information about registering licenses, see
the following documents: HP OpenVMS License Management Utility Manual HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the HP OpenVMS Version 8.3 Release Notes HP Operating Environments for OpenVMS for
Integrity Servers Software Product Description (SPD 82.34.xx).
To register licenses, use the OpenVMS License utility as follows: Start the OpenVMS License
utility by entering the following command at the OpenVMS system prompt.
(You can also use the LICENSE REGISTER command.) The utility displays a
menu screen similar to the following. Select the REGISTER option
(press Enter or enter 1 at the prompt), and enter
each license key until you have successfully registered all required
PAKs. VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. Exit this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1] |
After each license is
successfully registered, the procedure asks whether the license should
be loaded. Answer YES. After you have registered
and loaded all your licenses, exit the License Management procedure
by entering option 99.
If you plan to form a shadowed system disk, you
must add system parameters to the SYS$SYSTEM:MODPARAMS.DAT file.
Add the following lines to the bottom of the MODPARAMS.DAT file: SHADOWING=2 !Enable volume shadowing
SHADOW_SYS_DISK=1 !Enable shadowing of the system disk
SHADOW_SYS_UNIT=n !Optional: default is 0, which creates DSA0
SHADOW_MAX_COPY=4 !Allow up to 4 shadow copies or merges going on at the same time
ALLOCLASS=x !This number must be non-zero;
!it must be used if local non-FC devices are going to be
!shadow set members |
If a nonzero ALLOCLASS value is already in use
for your system, do not change the ALLOCLASS value. For more information
about these and other system parameters you can set for volume shadowing,
see the HP Volume Shadowing for OpenVMS manual. For more information
about setting ALLOCLASS for clusters, see the HP OpenVMS Cluster Systems manual. If you modified MODPARAMS.DAT to enable or modify
shadowing parameters (see Section 7.4), then run AUTOGEN and reboot
the system by performing the following steps. This makes the changes
take effect. Run
AUTOGEN by entering the following command: $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES NOFEEDBACK |
After
AUTOGEN completes, display or print the SYS$SYSTEM:AGEN$PARAMS.REPORT
file and review it. This file lists changes being made to SYSGEN
parameters or changes that AUTOGEN wanted to make but could not because
of a hardcoded or maximum value that was specified in MODPARAMS.DAT. If
other changes need to be made to MODPARAMS.DAT based on a review of
the AGEN$PARAMS.REPORT file, make them now and then resume at step
1. Once
you are satisfied with the parameter settings, enter the following
AUTOGEN command: $ @SYS$UPDATE:AUTOGEN GENPARAMS SETPARAMS NOFEEDBACK |
This command makes the parameter changes permanent
so that they are used on subsequent reboots. Reboot
the system by entering the following command:
For more information about AUTOGEN, see HP OpenVMS System Management Utilities Reference Manual: A-L. If you have upgraded a disk in a volume shadowing
environment, you must now re-form the shadow set. If you want to
form a shadow set for a newly installed system disk, you can do this
now or later. To do so requires that the VOLSHAD license has been
entered and loaded. In addition, you must set several system parameters,
as explained in Section 7.4, and then you must run AUTOGEN and reboot the system, as explained
in Section 7.5. Forming the shadow set with the newly installed
or upgraded disk as the master causes the other disks in the shadow
set to be updated with a copy of the disk. (In a single-member shadow
set, although no other disks exist to be updated, the shadow set can
be used to facilitate replacement of a failed drive.) After forming the shadow set, dismount one of
the shadow set members and keep it as a backup. After you perform
the steps recommended in this chapter, you can place another volume
into the shadow set instead of doing the final backup, or re-add the
volume that was dismounted. Form the shadow set as follows: Enter
the SHOW DEVICE D command to display a list of disks available on
your system. For example: $ SHOW DEVICE D
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$11$DKB100: (NODE1) Online 0
$11$DKB200: (NODE1) Mounted 0 I640831H1 918150 1 31 |
Enter
a command in the following format: MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label where: DSAn: is the virtual unit name of the shadow set, where n is a unique number from 0 to 999. upgraded-disk: is the name of the shadowed system disk on which you just upgraded
or installed OpenVMS. new-member: is the name of the disk you want to add as a member of the shadow
set. volume-label is the volume label of the shadow set you just upgraded or the disk
you are creating.
| | | |  | NOTE: When you form the shadow set, the contents of
the new member are replaced by the contents of the disk you upgraded.
Specifying the /CONFIRM qualifier reminds you of this fact, confirming
that you are specifying the correct name of a disk that either is
blank or contains files you no longer need. | | | | |
Example$ MOUNT/CONFIRM/SYSTEM DSA54: /SHADOW=($11$DKB200:,$11$DKB100:) I640831H1
%MOUNT-F-SHDWCOPYREQ, shadow copy required
Virtual Unit - DSA54 Volume label I64A0831H1
Member Volume label Owner UIC
$11$DKB100: (NODE1) SCRATCH [100,100]
Allow FULL shadow copy on the above member(s)? [N]: YES |
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: Create
network proxy authorization files (Section 7.7.1). Set
up the queue manager, configure shared files (when multiple system
disks are present), and start the default batch and print queues (Section 7.7.2). Configure
your multihead system, if applicable (Section 7.7.3). Configure
DECnet if it was installed or added during an upgrade (Section 7.7.4). Configure
TCP/IP Services for OpenVMS if it was installed or added during an
upgrade (Section 7.7.5). If
neither DECnet nor TCP/IP Services for OpenVMS is being used, install
and configure third-party networking software, if necessary (Section 7.7.6). Update
SYSTARTUP_VMS.COM to have networking software (and, optionally, any
other additional products you have installed) start at boot (Section 7.16).
For instructions on customizing the system, review
the following documentation: 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 this chapter. 7.7.1 Creating 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
startup: 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. 7.7.2 Setting 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 Section 7.14), 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
for new installations, enter the following commands at the DCL prompt.
As already noted, do not specify the recommended START QUEUE command
(with the /NEW_VERSION qualifier). The /NEW_VERSION qualifier causes
your system to overwrite queue database files on a system where the
queue manager has been started previously. $ 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. 7.7.3 Configuring a Multihead System (Optional) | |
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 steps: | | | | | NOTE: The DECwindows Motif software must already be on the system
before you can perform the following steps. If it is not, install
the software and reboot the system before you perform the steps. | | | | |
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
_To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM |
Restart
the DECwindows server by entering the following command: $ @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. 7.7.4 Configuring DECnet | |
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. For OpenVMS I64
systems, the DECnet end node license is included with the Foundation
Operating Environment (FOE) and so need not be registered and loaded.
However, if you want your system to take advantage of the advanced
features of DECnet (such as routing, DTSS server, DNS server), you
must register and install the DECnet-Plus extended license. If you
have not yet done this, perform the steps described in Section 7.3. 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 procedure. If you installed DECnet Phase IV, see the DECnet for OpenVMS Guide to Networking manual for information about configuring
this software using the NETCONFIG command procedure. 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: | Interactive mode: | 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 both DECnet Phase IV and 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 Section 7.16. 7.7.6 Installing 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 product documentation. Initialize or configure any of the following products
as necessary, following the instructions in the sections indicated: 7.8.1 Initializing CDSA (Optional) | |
The Common Data Security Architecture (CDSA) software
is installed, configured, and initialized automatically with the operating
system installation or upgrade. CDSA is required for Secure Delivery
purposes and other security features; otherwise, use of CDSA is not
required. Note that if you installed a new CDSA kit without
upgrading the base operating system, you must enter the following
command to initialize CDSA prior to its first use. Enter the command
from an account that has both SYSPRV and CMKRNL privileges (for example,
the SYSTEM account).
$ @SYS$STARTUP:CDSA$UPGRADE |
The following is an example of the output you
might see: Module uninstalled successfully.
.
.
.
CDSA-I-Init, CDSA has previously been initialized on this system.
CDSA-I-Init, Re-initializing CDSA.
CDSA-I-Init, Initializing CDSA
MDS installed successfully.
.
.
.
CDSA-I-Init, CDSA Initialization complete
CDSA-I-Init, Initializing Secure Delivery
Install completed successfully.
Install completed successfully.
Module installed successfully.
Module installed successfully.
CDSA-I-Init, Secure Delivery Initialization complete |
|
| | | | | NOTE: Do not attempt to explicitly remove CDSA from
your system. The PRODUCT REMOVE command is not supported for CDSA
although there appears to be an option to remove CDSA. CDSA is installed
with the operating system and is tightly bound with it. Attempts
to remove it might not work as expected and can create undesirable
side effects. An attempt to remove it results in a message similar
to the following:%PCSI-E-HRDREF, product HP I64VMS CDSA V2.3 is referenced by HP I64VMS OPENVMS V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
For more information about CDSA, see HP Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture. 7.8.2 Configuring the Availability Manager Base Software (Optional) | |
The Availability Manager base kit is installed
automatically with the operating system. However, use of Availability
Manager is not required. If you do not plan to use Availability Manager
or any products that depend on it, skip to the next section. The files in the Availability Manager base kit
make up what is called the Data Collector. The Data Collector is
used to collect data for the Availability Manager and DECamds products.
To display the data, you need to install an Availability Manager
Data Analyzer kit on an OpenVMS or Windows-based node in the local
LAN. The kit is included in the OpenVMS upgrade media, or you can
obtain it from the following website: http://www.hp.com/products/openvms/availabilitymanager The base kit files are the same files that have
been provided with the OpenVMS installation kit since Version 7.2.
The only change for OpenVMS Version 8.2 and higher is that these
files are now installed as a required product rather than being an
optional software product in the operating system kit. Procedures
for configuring and using these files remain unchanged. For more information about how to configure and
use the files in the Availability Manager base kit, see the section
"Performing Postinstallation Tasks" in the Availability Manager installation
instructions for OpenVMS (HP Availability Manager Installation
Instructions). This and other Availability Manager documents
are available at: http://www.hp.com/products/openvms/availabilitymanager | | | | | NOTE: Do not attempt to explicitly remove the Availability
Manager from your system. The PRODUCT REMOVE command is not supported
for Availability Manager although there appears to be an option to
remove Availability Manager. The Availability Manager base software
is installed with the operating system and is tightly bound with it.
Attempts to remove it might not work as expected and can create undesirable
side effects. An attempt to remove it results in a message similar
to the following:%PCSI-E-HRDREF, product HP I64VMS Availability Manager V8.3-1H1 is referenced by HP I64VMS OPENVMS V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
7.8.3 Configuring Kerberos (Optional) | |
The Kerberos for OpenVMS software, which is based
on MIT Kerberos, is installed automatically with the operating system.
However, use of Kerberos is not required. If you do not plan to
use Kerberos or any products that depend on Kerberos, skip to the
next section. To configure Kerberos, perform the following steps
from a privileged OpenVMS user account (for example, SYSTEM). Run
the following command procedure to configure the Kerberos clients
and servers: $ @SYS$STARTUP:KRB$CONFIGURE.COM |
Add
the following line to your SYLOGIN command procedure or to the LOGIN.COM
of each user who will use Kerberos: $ @SYS$MANAGER:KRB$SYMBOLS |
Edit
SYS$MANAGER:SYSTARTUP_VMS.COM to remove the exclamation point from
the KRB$STARTUP.COM line so that it appears as shown in the following
example. (Note that SYSTARTUP_VMS.COM has HP TCP/IP Services for
OpenVMS starting before Kerberos. This is required.) $ @SYS$STARTUP:KRB$STARTUP.COM |
For additional setup and configuration information,
see the HP Open Source Security for OpenVMS, Volume 3: Kerberos manual. This
document contains links to the MIT Kerberos documentation and is available
from the OpenVMS Version 8.3-1H1 kit. | | | | | NOTE: Do not attempt to explicitly remove Kerberos from
your system. The PRODUCT REMOVE command is not supported for Kerberos
although there appears to be an option to remove Kerberos. Kerberos
is installed with the operating system and is tightly bound with it.
Attempts to remove it might not work as expected and can create undesirable
side effects. An attempt to remove it results in a message similar
to the following:%PCSI-E-HRDREF, product HP I64VMS Kerberos V3.1 is referenced by HP I64VMS
OPENVMS V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
7.8.4 Configuring SSL for OpenVMS (Optional) | |
The HP SSL for OpenVMS software is installed automatically
with the operating system. However, use of SSL is not required.
If you do not plan to use SSL or any products that depend on it, skip
to the next section. The SSL$STARTUP.COM command procedure has been
added to VMS$LPBEGIN-050 to enable SSL to start automatically. Add the following line to SYS$MANAGER:SYSHUTDOWN.COM: $ @SYS$STARTUP:SSL$SHUTDOWN.COM |
If you are upgrading and have an earlier version
of SSL installed, copy your SSL$STARTUP.TEMPLATE file (located in
SYS$STARTUP) to SSL$STARTUP.COM in the SYS$STARTUP directory. Several other post-installation and post-upgrade
tasks are required, as described in the SSL release notes, available
in SYS$HELP:SSLnnn.RELEASE_NOTES, where nnn is the version of the SSL software, such as 013. For more information about SSL, see HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS.
| | | | | NOTE: Do not attempt to explicitly remove SSL from your system. The
PRODUCT REMOVE command is not supported for SSL although there appears
to be an option to remove SSL. SSL is installed with the operating
system and is tightly bound with it. Attempts to remove it might
not work as expected and can create undesirable side effects. An
attempt to remove it results in a message similar to the following:%PCSI-E-HRDREF, product HP I64VMS SSL V1.3 is referenced by HP I64VMS OPENVMS V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
7.8.5 Configure WBEM Services for OpenVMS (Optional) | |
WBEM Services for OpenVMS is installed automatically
with OpenVMS. As with other similar products, an OpenVMS upgrade does
not automatically include WBEM Services for OpenVMS if it is not already
installed on the target system disk. In this case, you must install
the product separately using the PCSI PRODUCT INSTALL command. If
you do not plan to use WBEM Services for OpenVMS or any products that
depend on it, simply do not configure the software; if you have already
configured the software, you can choose not to start it. You must configure WBEM Services for OpenVMS to
obtain the services provided by HP SIM (Version 5.2 or later)
and products such as Instant Capacity, Pay per use, and gWLM. To provide services over the network, HP recommends using
TCP/IP Services for OpenVMS and SSL (for security purposes). Before configuring WBEM Services for OpenVMS, configure TCP/IP
Services for OpenVMS. (For information about configuring TCP/IP Services
for OpenVMS, see Section 7.7.5. To configure WBEM Services for OpenVMS on a system on which
WBEM Services for OpenVMS has never been installed and configured,
follow the steps described in “Section 7.8.5.1.” If you are configuring the product
on a system on which it has been configured previously, see Section 7.8.5.2. For more information about HP WBEM products, see
the following website: http://www.hp.com/go/wbem | | | | | NOTE: HP recommends that you do not remove the WBEM
Services for OpenVMS product even if you do not have a need for it.
If you attempt to use the PRODUCT REMOVE command to remove this product,
you might see a message similar to the following. This message is
automatically displayed for any product that is required with OpenVMS.
The consequences of removing WBEM Services for OpenVMS might not be
as severe as implied by the message unless other software is using
the product on your server.%PCSI-E-HRDREF, product HP I64VMS WBEMCIM V2.61 is referenced by HP I64VMS OPENVMS V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
7.8.5.1 Configuring WBEM Services for OpenVMS (Where Not Configured
Previously)To configure WBEM Services for OpenVMS on a system
for the first time, follow these steps: Enter
the following command $ RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG |
This command invokes the utility that configures
and initializes the environment for WBEM Services for OpenVMS. After
displaying the initial configuration utility banner, the utility informs
you where it will store the configuration files and repository and
asks if you want to change the location. The configuration files and repository will be placed in the following location:
SYS$SPECIFIC:[WBEM_Services].
Do you want to change this location (Yes/No) [No]?: |
| | | | | NOTE: The repository, a compiled version of the Common
Information Model (CIM) class schema, requires an ODS-5 formatted
disk (the repository uses UNIX-style file names, which are not supported
on ODS-2 formatted disks). If the default location is on an ODS-2
formatted disk, you must change the location to an ODS-5 disk. | | | | |
When you accept the default location, the utility
informs you that all configuration questions have been answered and
asks whether you want to continue, as shown in the following example.
If you choose to continue, the utility creates the CIMServer repository
tree in the location indicated earlier. The CIMServer is the WBEM
Services for OpenVMS process that runs on the system to support certain
applications. It also creates the following command files: | SYS$STARTUP:WBEM_Services$Startup.com | | SYS$STARTUP:WBEM_Services$Shutdown.com | | SYS$SYSROOT:[WBEM_SERVICES]WBEM_Services$Define_Commands.com |
The SYS$STARTUP:WBEM_Services$Startup.com file defines system
logicals for the WBEM Services for OpenVMS environment. All configuration questions have been answered.
Do you want to continue (Yes/No) [YES]?:
%WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins...
%WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete.
This utility creates:
SYS$STARTUP:WBEM_Services$Startup.com
which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM.
This utility creates:
SYS$STARTUP:WBEM_Services$Shutdown.com
which should be added to SYS$STARTUP:SYSHUTDWN.COM.
This utility creates:
SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com
which users who use this product can add to their login.com. |
The
utility asks whether to start the CIMServer: Do you want to start the CIMServer now (Yes/No) [Yes]?: |
CIMServer must be running so
that your system can use such applications as Instant Capacity, Pay
per use, and gWLM. You can start CIMServer now, or you can perform
other postinstallation or postupgrade tasks first and then start CIMServer.
If you choose to start CIMServer now, the utility displays the progress
and operating system information, as in the following example: %RUN-S-PROC_ID, identification of created process is 21A00599
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
Host: boston.hp.com
Name: OpenVMS
Version: V8.3-1H1
UserLicense: Unlimited user license
Number of Users: 1 users
Number of Processes: 29 processes
OSCapability: 64 bit
LastBootTime: Jul 31, 2007 10:52:55 (-0400)
LocalDateTime: Aug 3, 2007 10:14:58 (-0400)
SystemUpTime: 256923 seconds = 2 days, 23 hrs, 22 mins, 3 secs |
To
ensure that CIMServer starts automatically at each reboot, add the
following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file: $ @SYS$STARTUP:WBEM_Services$Startup.com To have CIMServer shut down automatically with
the operating system, add the following line to the SYS$MANAGER:SYSSTARTUP:SYSHUTDWN.COM
file: $ @SYS$STARTUP:WBEM_Services$Shutdown.com All users who use this product should also add
the following line to their LOGIN.COM file: $ @SYS$STARTUP:WBEM_Services$Define_Commands.com In an OpenVMS Cluster, each
member that runs WBEM Services for OpenVMS needs its own repository.
Therefore, you must perform the WBEM Services for OpenVMS configuration
procedure on each of those cluster members.
7.8.5.2 Configuring WBEM Services for OpenVMS (Where Configured Previously)To configure WBEM Services for OpenVMS on a system
where it has been configured previously, follow these steps: Enter
the following command $ RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG |
This command starts the utility that configures
and initializes the environment for WBEM Services for OpenVMS. If the WBEM Services for OpenVMS product (Version
2.0) available with OpenVMS I64 Version 8.3 is already configured
on your system, the following error message and the recommended remedial
actions appear: %WBEMCONFIG-E-SYSCOMMONLOGICAL, WBEM_VAR can no longer be defined to point to
a location in SYS$COMMON. The repository files in WBEM_VAR should not be shared
with other cluster members.
Follow these manual steps to move the repository out of the SYS$COMMON
area and complete the post installation configuration tasks:
o Delete the sys$common:[WBEM_Services.var...] directory tree.
o Deassign the WBEM_VAR system logical.
o Run this procedure again. |
Perform the recommended steps, as in the following example: $ DELETE SYS$COMMON:[WBEM_SERVICES.VAR]*.*;*
$ DELETE SYS$COMMON:[WBEM_SERVICES]VAR.DIR;*
$ DEASSIGN/SYS WBEM_VAR
$ RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG |
After you start the configuration procedure, go
to Section 7.8.5.1 and follow
the steps described there, starting with step 2. After
displaying the initial configuration utility banner, the utility informs
you where it will store the configuration files and repository and
asks if you want to change the location. The configuration files and repository will be placed in the following location:
SYS$SPECIFIC:[WBEM_Services].
Do you want to change this location (Yes/No) [No]?: |
The repository is a compiled
version of the CIM class schema. This example assumes you accept the
current location. As shown in the following
example, the utility informs you that all configuration questions
have been answered and asks whether you want to continue. If the utility determines that the repository schema
has not changed, the utility informs you and continues. The utility
does not need to upgrade the repository. If the utility determines that the current repository
needs upgrading, or if the utility does not find a repository (perhaps
WBEM Services for OpenVMS had been installed but not configured),
the utility displays a message informing you that the repository will
be upgraded or created and that this will take 10 to 15 minutes depending
on your processor and disk I/O speed. In the following example, the
utility needs to create the repository tree. The utility also creates the SYS$STARTUP:WBEM_Services$Startup.com,
SYS$STARTUP:WBEM_Services$Shutdown.com, and SYS$SYSROOT:[WBEM_SERVICES]WBEM_Services$Define_Commands.com
command files. The SYS$STARTUP:WBEM_Services$Startup.com file defines
system logicals for the WBEM Services for OpenVMS environment. All configuration questions have been answered.
Do you want to continue (Yes/No) [Yes]?:
%WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins...
%WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete.
This utility creates:
SYS$STARTUP:WBEM_Services$Startup.com
which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM.
This utility creates:
SYS$STARTUP:WBEM_Services$Shutdown.com
which should be added to SYS$STARTUP:SYSHUTDWN.COM.
This utility creates:
SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com
which users who use this product can add to their login.com. |
The
utility now asks you whether to start the CIMServer: Do you want to start the CIMServer now (Y/N) {Y}?: |
CIMServer must be running so
that your system can use such applications as Instant Capacity, Pay
per use, and gWLM. You can start CIMServer now, or you can perform
other postinstallation or postupgrade tasks first and then start CIMServer.
If you choose to start CIMServer now, the utility displays the progress
and operating system information, as in the following example: %RUN-S-PROC_ID, identification of created process is 21A00599
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
Host: boston.hp.com
Name: OpenVMS
Version: V8.3-1H1
UserLicense: Unlimited user license
Number of Users: 1 users
Number of Processes: 29 processes
OSCapability: 64 bit
LastBootTime: Jul 31, 2007 10:52:55 (-0400)
LocalDateTime: Aug 3, 2007 10:14:58 (-0400)
SystemUpTime: 256923 seconds = 2 days, 23 hrs, 22 mins, 3 secs |
To
ensure that CIMServer starts automatically at each reboot, add the
following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file: $ @SYS$STARTUP:WBEM_Services$Startup.com To have CIMServer shut down automatically with
the operating system, add the following line to the SYS$MANAGER:SYSSTARTUP:SYSHUTDWN.COM
file: $ @SYS$STARTUP:WBEM_Services$Shutdown.com All users who use this product should also add
the following line to their LOGIN.COM file: $ @SYS$STARTUP:WBEM_Services$Define_Commands.com In an OpenVMS Cluster, each
member that will run WBEM Services for OpenVMS needs its own repository.
Therefore, you must perform the WBEM Services for OpenVMS configuration
procedure on each of those cluster members.
7.8.6 Configure WBEM Providers for OpenVMS (Optional) | |
WBEM
Providers for OpenVMS is installed automatically with OpenVMS. As
with other similar products, an OpenVMS upgrade does not include WBEM
Providers for OpenVMS if it is not currently installed on the target
system disk. In this case, you must install the product separately
using the PCSI PRODUCT INSTALL command. You must configure WBEM Providers for OpenVMS
to obtain the services provided by HP SIM (Version 5.2 or later) . WBEM Providers for OpenVMS requires
WBEM Services for OpenVMS. To configure WBEM Providers for OpenVMS, follow
the directions provided in the HP WBEM Providers Installation
and Adminstrator's Guide, available in the SYS$COMMON:[WBEMPROVIDERS.DOCUMENTATION]
directory on your OpenVMS system disk. For the latest information,
see the following website and select the appropriate link: http://h71000.www7.hp.com/openvms/system_management.html | | | | | NOTE: HP recommends that you do not remove the WBEM
Providers for OpenVMS product even if you do not have a need for it.
If you attempt to use the PRODUCT REMOVE command to remove this product,
you might see a message similar to the following. This message is
automatically displayed for any product that is required with OpenVMS;
the consequences of removing WBEM Providers for OpenVMS might not
be as severe as implied by the message unless other software (such
as HP SIM) is using the
product on your Integrity server.%PCSI-E-HRDREF, product HP I64VMS WBEMPROVIDERS V1.5 is referenced by HP I64VMS OPENVMS V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
7.8.7 Configure the Instant Capacity Software (Optional) | |
Instant Capacity (iCAP) software is supported
on cell-based Integrity servers. For support of this software,
as well as Temporary Instant Capacity (TiCAP) , you must
configure WBEM Services for OpenVMS. If you choose to use Instant Capacity, Temporary
Instant Capacity, or Global Instant Capacity, configure the software
by entering the following command: $ @SYS$MANAGER:ICAP$CONFIG.COM |
For more information about configuring and using
Instant Capacity, see the HP Instant Capacity User’s
Guide on the following website: http://docs.hp.com/en/hplex.html#Utility%20Pricing 7.8.8 Configure the Pay per use Software (Optional) | |
Pay per use (PPU) software is supported on cell-based
Integrity servers leased from HP Finance. For support of this
software, you must configure WBEM Services for OpenVMS. If you choose to use Pay per use, configure the
software by entering the following command: $ @SYS$MANAGER:PPU$CONFIG.COM |
For more information about configuring and using
Pay per use, see the HP Pay per use User’s Guide on the following website: http://docs.hp.com/en/hplex.html#Utility%20Pricing 7.8.9 Configure HP SIM (Optional) | |
To enable HP SIM support of OpenVMS on your system,
follow the directions provided in the HP WBEM Providers
Installation and Adminstrator's Guide, available
in the SYS$COMMON:[WBEMPROVIDERS.DOCUMENTATION] directory on your
OpenVMS system disk. For the latest information, see the documentation
provided at the following website: http://h18002.www1.hp.com/products/servers/management/hpsim/download.html 7.8.10 Initializing and Running the Performance Data Collector Base
Software (Optional) | |
The Performance Data Collector for HP OpenVMS
(TDC) collects and manages configuration and performance data for
analysis by other applications. TDC_RT Version 2.2 is a run-time
only (base) variant of the TDC software that is installed automatically
with the OpenVMS operating system for use on specific operating system
platforms. Use of the TDC_RT software is not required. If
you do not plan to use TDC_RT or any products that depend on it, you
can skip to the next section. TDC_RT does not run automatically when the system
starts, but any suitably privileged user can start the software manually.
This section includes information about system parameters, privileges
and quotas, startup, and installation in OpenVMS Clusters. | | | | | NOTE: Do not attempt to explicitly remove TDC_RT from
your system. The PRODUCT REMOVE command is not supported for TDC_RT
although there appears to be an option to remove it. TDC_RT is installed
with the operating system and is tightly bound with it. HP or third-party
applications might require TDC_RT. Attempts to remove it might not
work as expected and can create undesirable side effects. An attempt
to remove it results in a message similar to the following:%PCSI-E-HRDREF, product HP TDC_RT V2.3 is referenced by HP I64VMS OPENVMS
V8.3-1H1
The two products listed above are tightly bound by a software dependency.
If you override the recommendation to terminate the operation, the
referenced product will be removed, but the referencing product will have
an unsatisfied software dependency and may no longer function correctly.
Please review the referencing product’s documentation on requirements.
Answer YES to the following question to terminate the PRODUCT command.
However, if you are sure you want to remove the referenced product then
answer NO to continue the operation.
Terminating is strongly recommended. Do you want to terminate? [YES] |
| | | | |
7.8.10.1 User Privileges and QuotasUsers of TDC_RT require various privileges, depending
on the types of data to be collected. Online help is available when
running the collector application and specifies the privileges required
to collect each type of data. Enabling the following set of privileges
enables collection of all data items: CMKRNL, LOG_IO, NETMBX, PHY_IO,
SYSLCK, SYSPRV, WORLD. Users of the product also require working set
quotas (WSQUO) greater than 7000 pagelets. TDC_RT provides a startup file that should be
launched during system startup. The startup file defines several
logical names required for use of the product, but the startup file
does not actually start the data collector. Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$STARTUP:TDC$STARTUP |
To directly run TDC$STARTUP.COM, SYSNAM privilege
is required. 7.8.10.3 Compatibility with Prior ReleasesNote the following about prior releases of TDC
software. TDC Version 1.n For users of some third-party system-management applications, TDC
Version 1.n was distributed by web download.
Applications developed using TDC Version 1.n will not work with TDC Version 2.2 software until they are rebuilt
using the TDC Version 2.2 Software Developer’s Kit (SDK). You
can obtain this SDK kit from the following website: http://www.hp.com/products/openvms/tdc/ Data files created using TDC Version 1.n cannot be read by TDC_RT Version 2.2. Data files created using TDC_RT
Version 2.2 cannot be read using TDC Version 1.n. When TDC_RT Version 2.1 or any newer version of TDC is installed,
files associated with TDC Version 1.n are
not removed. In any case, TDC_RT Version 2.1 (or later) and TDC Version
1.n can safely coexist on a system. You
can remove the older TDC files by uninstalling TDC (use the DCL command
PRODUCT REMOVE). TDC Version 2.2 on an earlier version of OpenVMS If you upgrade to OpenVMS Version 8.3-1H1 from an earlier
version of OpenVMS on which TDC Version 2.2 was installed, files shared
by TDC_RT Version 2.2 and TDC Version 2.2 are updated; these files
are the documentation and support files listed in SYS$COMMON:[TDC]README.TXT
as common to all kit variants. Unless the TDC and TDC_RT kits share
the same baselevel number (for example, 102), image files installed
with TDC Version 2.2 are retained in their installed locations. Most
likely, the downloaded TDC Version 2.2 software will be more recent
(higher baselevel number) than the TDC_RT Version 2.2 software installed
with OpenVMS Version 8.3-1H1. The TDC Version 2.2 SDK (if installed)
and any additional documentation files installed with TDC Version
2.2 are retained. Running SYS$STARTUP:TDC$STARTUP.COM causes the most recent TDC/TDC_RT
Version 2.2 images to be used at runtime, regardless of whether they
were installed with TDC Version 2.2 or with TDC_RT Version 2.2. You can remove TDC Version 2.2 without affecting the integrity
of the TDC_RT Version 2.2 installation if their baselevel numbers
differ.
As of OpenVMS Version 8.2, TDC and TDC_RT use
the same naming scheme for image files. A build number is tagged
to the image file names. For example, if the version of TDC_RT that
ships with your operating system is Version 2.2-60 (where 60 is the
build number), then the files that are installed will have names such
as TDC$APISHR$I_V830-0060.EXE, where $I denotes
I64), V830 denotes the
version of OpenVMS (8.3), and 0060 is the build number. The SYS$STARTUP:TDC$STARTUP.COM
startup file, which is also identical for both TDC and TDC_RT, uses
this build number to determine which image files to use. When a subsequent
installation is performed with software that has higher build numbers,
the TDC$STARTUP.COM startup file uses the image files with the highest
build number appropriate for the current platform. To run the collector application, users can enter
the TDC command at the DCL prompt. But first, because the TDC command
is not included in the system command table SYS$LIBRARY:DCLTABLES.EXE,
each user must add the command to their table by entering the following
command at the DCL prompt: $ SET COMMAND SYS$COMMON:[TDC]TDC$DCL |
Each user can add this SET command to their LOGIN.COM
file. However, because elevated privileges are required for most
data collection operations, it might not be appropriate to add this
command to SYS$MANAGER:SYLOGIN.COM. To start the collector application, enter the
TDC command: For more information about running the application,
see the file SYS$COMMON:[TDC]TDC_README.TXT. Release notes are located
in the file SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT. See both of these
files before running the collector application. 7.8.10.5 Installation in OpenVMS ClustersTDC_RT is installed in SYS$COMMON:[TDC] by default.
Included are only those files required to run the data collector
with the particular operating system version it was distributed with.
Once TDC_RT is installed and SYS$STARTUP:TDC$STARTUP.COM has been
run on each cluster member, then all cluster members in a single-version,
single-architecture OpenVMS Cluster should be able to run the software. For mixed-version and mixed-architecture clusters,
you should obtain and install a complete Performance Data Collector
kit (TDC Version 2.2) from the following website: http://www.hp.com/products/openvms/tdc The complete kit provides an SDK and run-time
environments for all supported OpenVMS configurations. It supports
installation on a clusterwide basis in mixed-version and mixed-architecture
OpenVMS Clusters. 7.8.11 Preparing to Use OpenVMS Management Station (Optional) | |
If you installed the OpenVMS Management Station
software on your system (either by accepting all default values or
by selecting the component manually during the installation or upgrade
procedure), you must perform several tasks on your OpenVMS system
and your PC before you can use OpenVMS Management Station. These
tasks include the following: Starting OpenVMS Management
Station on other nodes Verifying that you have
the proper memory, disk space, media, and the required software to
install and run OpenVMS Management Station on your PC Installing the client
software on your PC Defining DECnet nodes
(after a new installation only)
For complete information about preparing your
OpenVMS system and your PC to run the OpenVMS Management Station server
and client software, see Appendix G. 7.8.12 Installing OpenVMS Debugger Clients on a PC (Optional) | |
The latest version of the OpenVMS Debugger runs
on OpenVMS I64 systems.
The debug server runs on OpenVMS, while a debug client, which is
the user interface to the server, runs on OpenVMS and on Microsoft® Windows® 95, Windows 98, Windows NT®, Windows 2000, Windows XP®, and Windows Vista®. There is no special installation procedure for the components
that run on OpenVMS. The installation guide and kit for the OpenVMS
debugger client is located on the Layered Products CD that comes with
the OpenVMS binary CD set. The directory on the CD is DEBUG_CLIENTS011.
The KIT.DIR subdirectory contains the following files: For installation instructions, see the INSTALLATION_INFO.PS
or INSTALLATION_INFO.TXT file in the DOCUMENTATION subdirectory. You can use SYS$WELCOME to display a system-specific
welcome message at login. The message could inform users of scheduled
down time, recent updates to the system, whom to contact about system
problems, and so forth. A template file is provided by the operating
system. To create your own SYS$WELCOME file, do the following: Copy
the template file using the following command: $ COPY SYS$MANAGER:WELCOME.TXT SYS$SPECIFIC:[SYSMGR]WELCOME.TXT |
For a clusterwide welcome message,
you can copy the file to SYS$COMMON:[SYSMGR]. Replace
the text in SYS$SPECIFIC:[SYSMGR]WELCOME.TXT with text specific to
your system. Edit
SYS$MANAGER:SYSTARTUP_VMS.COM to remove the exclamation point (!)
from the line that defines SYS$WELCOME.
If you do not want to use a node-specific welcome
file, you can optionally define the logical in SYS$MANAGER:SYSTARTUP_VMS.COM
to display a message, such as in the following example: $ DEFINE SYS$WELCOME “Welcome to node HOMER” |
For more information about creating login welcome
messages, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. The upgrade procedure retains the site-specific
versions of the following files located in the [VMS$COMMON] directory: [SYSMGR]LAT$SYSTARTUP.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYSTARTUP_VMS.COM [SYSMGR]TFF$SYSTARTUP.COM [SYS$STARTUP]ESS$LAST_STARTUP.DAT
The upgrade procedure might provide new templates
for some of these files with the .TEMPLATE file extension. The new
templates might include features that are not in your site-specific
files. Check the templates against your site-specific files and edit
your files as necessary. If you decide after the installation or upgrade
to change which OpenVMS operating system files you want installed
on your system, you can use the menu system contained on the OpenVMS
operating system media to add or remove files. | | | | | IMPORTANT: Unless you have a specific need to exclude operating
system files from your system disk, HP strongly recommends that you
accept the defaults and install all files that are part of OpenVMS.
In general, limited disk space is not a good reason to exclude files;
problems encountered when needed files are missing can cost much more
than the cost of a larger disk. | | | | |
| | | | | NOTE: You can obtain information about individual system
files by entering the HELP SYSTEM_FILES command at the dollar sign
prompt ($). | | | | |
To add or remove operating system files: Mount
and boot the OpenVMS operating system media. Choose
option 1 on the menu. Choose
the PRESERVE option. Enter
the name of the device that contains the system disk and answer the
questions. After
you answer the question “Do you want detailed descriptions?,”
information regarding reconfiguring or reinstalling is displayed.
Read the instructions, then choose the desired entry on the menu
of options.
The following is a sample display: |
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS I64 Version 8.3-1H1
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete recovery data
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 1
***********************************************************
.
.
.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE] PRESERVE
.
.
.
Version 8.3-1H1 of the OpenVMS operating system is already installed
on the target disk. You may choose one of the following actions:
o Reconfigure the OpenVMS platform.
This action will allow you to change your selections of which
of the windowing and network products you included with your
OpenVMS operating system installation.
o Reconfigure the OpenVMS operating system.
This action will allow you to change your choices about which
options you included for the OpenVMS operating system.
o Reinstall the OpenVMS operating system.
This action will cause ALL operating system files to be replaced.
You can also change your choices about which options you included
for the OpenVMS operating system.
Reinstall will take longer than Reconfigure. Reinstall may be
appropriate if you suspect that files in the operating system,
or in the windowing and network products have become corrupted.
If you want to reinstall any of the windowing and network products,
choose "Install or upgrade layered products" from the main menu.
If you want to change your choices about which options you included
for any of the windowing and network products, choose "Reconfigure
installed products" (option 5) from the main menu.
Please choose one of the following:
1) Reconfigure the OpenVMS platform.
2) Reconfigure the OpenVMS operating system.
3) Reinstall the OpenVMS operating system.
4) Return to the Main Menu (abort the upgrade/installation).
Enter choice or ? for help: (1/2/3/4/?) 2
The following product has been selected:
HP I64VMS VMS V8.3-1H1 Operating System
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product
and for any products that may be installed to satisfy software dependency
requirements.
HP I64VMS OPENVMS V8.3-1H1: OpenVMS and related products Platform
COPYRIGHT 1976, 30-AUG-2007
Hewlett-Packard Development Company, L.P.
Do you want the defaults for all options? [YES] NO |
|
Answer NO to this question as shown, and select
the options you want, as described in step
19 of the installation procedure in Section 3.3.3. (Example 3-1 shows a list of the
component options.) After you respond to the prompts, the display
continues and the installation procedure completes. The following
is a continuation of the sample display: Do you want to review the options? [NO]
Execution phase starting ...
The following product will be reconfigured:
HP I64VMS VMS V8.3-1H1
Portion done: 0%...10%...20%...30%...40%...50%...60%...80%...90%...100%
The following product has been reconfigured:
HP I64VMS VMS V8.3-1H1
.
.
. |
For detailed instructions on how to remove the
OpenVMS operating system from your disk, see Appendix H. The libraries included with the OpenVMS I64 operating
system kit are installed in expanded (uncompressed) format. HP recommends
keeping the libraries in expanded format. Compressing them can hinder
system performance. You can use the command procedure SYS$UPDATE:LIBDECOMP.COM
to decompress, compress, or list the sizes of the system libraries. For more information about the utility, you can
request help by entering the following command: $ @SYS$UPDATE:LIBDECOMP HELP |
You can list the sizes and format (reduced or
expanded) of the libraries by using the following command: $ @SYS$UPDATE:LIBDECOMP LIST |
For complete information about expanding and reducing
system library files and using LIBDECOMP.COM, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. HP recommends installing any relevant OpenVMS
and networking patches that are available. Most patches are optional,
but some layered products might require one or more patches on the
system before their software is installed. For more information about
patches that might be required on your system, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes, HP OpenVMS Version 8.3 Release Notes, and the documentation provided for the relevant layered products. As of Version 8.3 of OpenVMS, patch files are
validated using the Secure Delivery feature. Each patch file includes
an associated digital signature file (also referred to as a manifest)
that is used to validate the patch file. This validation involves
authenticating the originator (HP, in this case) and verifying the
contents of the file. | | | | | NOTE: HP strongly recommends backing up your system disk before installing
patches. | | | | |
To download and install OpenVMS patches, do the
following: Create a directory on a nonsystem disk called [PATCHES]
and set default to that directory. Go to the following location (entering
the letters in the case indicated) and down load the appropriate patches
to the [PATCHES] directory: ftp://ftp.itrc.hp.com/openvms_patches/i64/V8.3-1H1 The patches are downloaded as compressed files. To decompress
them, use the RUN command, as in the following example: $ RUN VMS831H1I_MX2-V0100.ZIPEXE |
This decompresses the patch into an installable file. Install the decompressed patches as described in the patch
release notes.
Alternatively, you can access the ITRC site from your OpenVMS
system and down load the patches as described in the following steps: Create
a directory on a nonsystem disk called [PATCHES] and set default to
that directory. Enter
the following command at the system prompt: Log
in as an anonymous user (user name: anonymous). The password is your
email address. Once
you are logged in, enter the bin command at the
FTP> prompt to get into binary mode, as in the following example.
Binary mode is necessary for downloading patches correctly. Enter
commands in this and the following steps in the exact case shown (lowercase
or uppercase). FTP> bin
200 Type is set to I. |
Enter
the command PASSIVE ON, as in the following example: FTP> passive on
Passive is on. |
To access the directory containing
the V8.3-1H1 operating system patches, enter the following command,
using the exact case indicated for each letter: FTP> cd openvms_patches/i64/V8.3-1H1
250 CWD command successful. |
To access the directory containing patches for
layered products such as TCP/IP Services or DECnet, enter the following
command :
FTP> cd openvms_patches/layered_products/i64
250 CWD command successful. |
Search
for the patch you want by using the ls command,
specifying a few unique letters of the patch name in uppercase (all
patch names are in uppercase) surrounded by asterisks. For example,
to look for a patch named VMS831H1I_MX2-V0100, enter the following
command: FTP> ls *MX2*
227 Entering Passive Mode (192,151,52,14,235,168)
150 Opening ASCII mode data connection for file list.
VMS831H1I_MX2-V0100.ZIPEXE
VMS831H1I_MX2-V0100.txt
226 Transfer complete.
47 bytes received in 00:00:00.00 seconds (45.90 Kbytes/s) |
The .ZIPEXE file is the patch installation file;
the .TXT file is the patch release notes (also included in the .ZIPEXE
file). If
the patch is an UPDATE patch or a TCP/IP patch, which can be very
large files, you might want to enter the hash command
as shown in the following example so that in the next step you can verify that the download is happening as expected (hash displays # symbols on the screen as the file is being
downloaded). FTP> hash
Hash mark printing on (1024/hash mark). |
When
you find the patch file, use the get command to
download the file, as in the following example. Remember that case
is significant and all patch file names are in uppercase. FTP> get VMS831H1I_MX2-V0100.ZIPEXE
227 Entering Passive Mode (192,6,165,75,248,228)
150 Opening BINARY mode data connection for VMS831H1I_MZX2-V0100.ZIPEXE
(36218732 bytes).
#########################################################################
.
.
.
#########################################################################
#########
226 Transfer complete.
local: USER5:[PATCHES]VMS831H1I_MX2-V0100.ZIPEXE;1
remote: VMS831H1I_MX2-V0100.ZIPEXE
2238464 bytes received in 00:00:01.29 seconds (1.65 Mbytes/s) |
Repeat
steps 8 through 10 until you have downloaded all the patches you need. When
you are finished, press Ctrl/Z to
exit FTP and return to the DCL prompt. The patches are downloaded as compressed files. To decompress
them, use the RUN command, as in the following example: $ RUN VMS831H1I_MX2-V0100.ZIPEXE |
This decompresses the patch into an installable
file. Install
the decompressed patches as described in the patch release notes.
The OpenVMS operating system kit includes several
layered products. These include the System Integrated Product (SIP)
kits for the following products that are installed automatically: Availability Manager (base) for OpenVMS (required) CDSA for OpenVMS (required) Kerberos for OpenVMS (required) SSL for OpenVMS (required) Performance Data Collector base software, TDC_RT (required) WBEM Services for OpenVMS WBEM Providers for OpenVMS
These layered products also include the SIP kits
for the following products that you can install optionally as part
of the OpenVMS operating system installation: DECwindows Motif for OpenVMS DECnet Phase IV for OpenVMS TCP/IP Services for OpenVMS
These layered products are included in the operating
system media and can be installed using either the steps shown in
this section or the alternative procedure described in Section 7.14.1. Other layered products—whether
provided by HP on other CDs in the operating system distribution,
in the Software Product Library CD set, or on a CD provided by a third-party
company—should be installed using the steps shown in Section 7.14.1. In addition to the SIPs, the OpenVMS I64 OE DVD
includes kits for various products that are part of the OpenVMS OEs.
HP does not support installing these OE product kits while booted
from the OE DVD. To install these OE products, you must use the procedure
described in Section 7.14.1. As of Version 8.3, most PCSI kits included on
the OpenVMS distribution media are signed using Secure Delivery.
Signed PCSI kits that are installed from the OpenVMS I64 operating
system distribution media are validated. Signed PCSI kits that you install
subsequently are validated (including signed kits on the distribution
media).
| | | | | NOTE: To use menu option 3, the target system must have the identical
version of the OpenVMS operating system as the operating system media.
If you need to install layered products on a target system that has
a different version of the operating system, use the alternative procedure. | | | | |
To use option 3 of the operating system menu,
follow these steps: Before
you install any layered products, be sure you back up the system disk. If
you are not already booted from the operating system media, shut down
the system and boot the operating system media. For instructions
on how to shut down the OpenVMS I64 system, see Section A.7. To
view a list of products that can be installed, choose option 2 on
the menu. If the layered product that you want to install is not
listed in the display, install the product by using the alternative
procedure described in Section 7.14.1, or see the documentation you received
with the layered product. Note that HP does not support VMSINSTAL,
PRODUCT INSTALL, or other PRODUCT commands from the DCL option on
the operating system menu. To
install layered products, choose option 3 on the menu. For more instructions,
see Section 1.4.3. After
the installation completes, shut down the system by selecting option
9 on the menu. When you boot the target system, the layered products
you installed will be present.
For additional information about installing layered
products, see the HP OpenVMS System Manager's Manual. 7.14.1 Alternative Procedure | |
Use this alternative procedure to install the
following products: Layered products on a target system that has a different
operating system version than that of the operating system media (CD/DVD) Layered products that require VMSINSTAL (indicated
in the directories by save-set file names with file types of .A, .B,
and so on) SIP kits (as an alternative to using menu option 3
of the operating system menu on the media) Products on the Layered Products, Freeware, System
Tools, and e-Business Integration and Infrastructure CDs Third-party software products (such as database products,
accounting software, and so forth)
For a list of layered products you can install,
see the Software Product Descriptions included with your operating
system kit. Note that some products require a license key (PAK) from
HP. Follow these steps: Before
you install all your layered products, be sure you back up the system
disk. In addition, ensure that a license has been loaded for the
software. Note also that most layered products require changes to
SYSGEN parameters or AUTHORIZE values, and to system files such as
SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM. For more information,
see the following: Installation guides for
these layered products HP OpenVMS System Manager's Manual, Volume 1: Essentials Section 7.23 in this manual Section 7.16 in this manual
After
your target system disk runs AUTOGEN and boots (if necessary), mount
the OpenVMS operating system media. For example, if the device with
the operating system media is DKA400:, use the following command: $ MOUNT/OVERRIDE=IDENTIFICATION DKA400 |
Locate
the directories and files containing the available layered products.
For example, if the device name is DKA400:, enter the following command: $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT] |
You can use the PRODUCT FIND command to locate
kits by using the PCSI utility. For example: $ PRODUCT FIND * /SOURCE=DKA400:[*.KIT] |
To
install layered products that require VMSINSTAL (indicated in the
directories by save-set file names with file types of .A, .B, and
so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the
device name and directory at the prompt. For example: $ @SYS$UPDATE:VMSINSTAL
* Where will the distribution volumes be mounted: DKA400:[DIAA032.KIT] |
To install layered products that require the PCSI
utility (indicated in the directories by file names with file types
of .PCSI or .PCSI$COMPRESSED), use the PRODUCT INSTALL command to
specify the device name and directory. Following is an example of
the PRODUCT INSTALL command on an I64 system: $ PRODUCT INSTALL FORTRAN /SOURCE=DKB400:[I64_FORT075.KIT] |
If you have a large number of print queues to
add and you need to get the system in use quickly, you can set up
one print queue per area or work group and then add the other print
queues later, after the user accounts are added (Section 7.17). For more information
about adding print queues, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. After installing and configuring any layered products
and adding new print queues, you should update the SYSTARTUP_VMS.COM
file to start these products and print queues. For more about updating
the SYSTARTUP_VMS.COM file, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. During installation, DEFAULT and SYSTEM accounts
are created automatically. You should create additional user accounts
now. If you plan to have HP service representatives test your system
or if you plan to run testing software such as UETP, you must create
accounts for each representative and a SYSTEST (standalone system)
or SYSTEST_CLIG (OpenVMS Cluster system) account to run UETP. For complete information about creating and managing
user accounts and about creating accounts for HP service representatives
and UETP, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. The User Environment Test Package (UETP) is a
software package that tests whether the OpenVMS operating system is
installed correctly. It tests the hardware, including disk drives,
tape drives, CD drives, line printers (if any), network cards, and
so forth. Running UETP is optional; HP recommends that you run UETP
after an installation or if new hardware was added as part of an upgrade. Before using UETP, you must create a SYSTEST (standalone
system) or SYSTEST_CLIG (OpenVMS Cluster system) account. You should
also create an account for HP service representatives to use. You
can use the CREATE_SPECIAL_ACCOUNTS.COM file to create these accounts,
as explained in HP OpenVMS System Manager's Manual, Volume 1: Essentials. For complete information about using UETP, see
the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. After you customize the OpenVMS operating system to your
satisfaction and perform the other steps recommended thus far in this
chapter that are relevant to your system, protect your work by making
a standalone backup copy of the system disk to tape. To do so, follow
the instructions in Section 7.2. If you are going to be saving to disk, specify a disk that will
not be (or is not) part of a shadow set. For complete information about backup operations,
including a description of an alternative method that does not require
booting from the operating system media, see Appendix E. HP also recommends creating a systematic routine
for backing up the application, data, and user disks. For more information,
see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. If your system disk participates in a volume shadowing
environment, re-form the shadow set again to generate another shadow
copy onto the other disks in the set. To do so, follow the instructions
in Section 7.6. If you are performing a rolling upgrade in an
OpenVMS Cluster environment and have completed all the postupgrade
tasks required thus far for your upgraded system disk, reboot each
system that boots from that system disk. For more information about booting your system,
see Appendix A for OpenVMS I64 systems. At this point, your system is ready for general
use. When you install or upgrade the OpenVMS operating
system, the system executes the AUTOGEN.COM procedure to set the values
of system parameters and the sizes of the page, swap, and dump files
according to the system configuration. After running your system for at least 24 hours
with users or a typical application workload on the system, run the
AUTOGEN.COM procedure again to tune the system properly. Run AUTOGEN
as follows. (In an OpenVMS Cluster, you must follow these steps to
run AUTOGEN on each cluster node.) Run
AUTOGEN in feedback mode, examine AGEN$PARAMS.REPORT, and reboot the
system. To run AUTOGEN in feedback mode, use the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK |
To view AGEN$PARAMS.REPORT
on your screen, enter the following command: $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT |
You can print this file or examine it using the
EDIT/READ_ONLY command. If the report includes a message similar to the
following, you might need to modify the size of the page, swap, or
dump file: %AUTOGEN-W-DSKSPC, The disk on which DKA0:[SYS0.SYSEXE]PAGEFILE.SYS
resides would be over 95% full if it were modified to hold 20000 blocks. |
For more information about AGEN$PARAMS.REPORT,
see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. Run
AUTOGEN again in feedback mode two work days later and examine AGEN$PARAMS.REPORT,
and then reboot the system. (For information about the importance
of having a current AGEN$FEEDBACK.DAT file, see Section 4.6.) HP
recommends that you run AUTOGEN from the SAVPARAMS phase through the
TESTFILES phase weekly thereafter until the system stabilizes (that
is, until AUTOGEN finds nothing that needs to be adjusted). Make
sure you run AUTOGEN when your system is running under a typical workload.
Examine AGEN$PARAMS.REPORT to determine the need for additional changes. | | | | | IMPORTANT: If you start AUTOGEN without specifying the execution-mode
parameter (FEEDBACK, NOFEEDBACK, or CHECK_FEEDBACK), AUTOGEN uses
the feedback information in its calculations. However, if the feedback
information reflects system up time of less than 24 hours, or if the
feedback information is more than 30 days old, AUTOGEN includes warnings
in the AGEN$PARAMS.REPORT file to alert you to potential problems
with the feedback data. If you wrongly assume the feedback is valid,
the parameter settings might vary significantly from your expectations. If you specify FEEDBACK (or NOFEEDBACK), AUTOGEN
uses (or does not use) the feedback regardless of the data’s
reliability. AUTOGEN proceeds through the SETPARAMS phase (if you
specified SETPARAMS, SHUTDOWN, or REBOOT as the end phase) and sets
system parameters to the values it computed. If you specify CHECK_FEEDBACK, AUTOGEN checks
the validity of the feedback data. If AUTOGEN determines the feedback
is suspect, then AUTOGEN ignores the feedback when computing parameter
values. It stops at the TESTFILES phase and issues a warning in the
report that parameters have not been changed. You must read the report
and decide whether the calculated values are acceptable. You can
either use them (by running the AUTOGEN SETPARAMS phase) or rerun
AUTOGEN with valid feedback data. | | | | |
After
the system has stabilized, HP recommends that you run AUTOGEN at least
monthly to save feedback information for future use. Use the following
command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS |
If you do not maintain current feedback information
for AUTOGEN, you will not have the needed information the next time
you upgrade your system. As a result, you may have to reboot and
rerun AUTOGEN several times to make your upgraded system operational.
For more information about running AUTOGEN, see
the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. Based on your examination of AGEN$PARAMS.REPORT,
you might need to modify parameter values in MODPARAMS.DAT. Read
the notes in Section 7.23.1.
These notes apply to modifications being made after a new installation
and after an upgrade. If you are modifying system parameters after
an upgrade, also see Section 7.23.2. 7.23.1 General Notes About Modifying System Parameters | |
When modifying system parameters, note the following: In general, let AUTOGEN
calculate system parameters. You can hardcode values (such as GBLPAGES=value), but doing so overrides AUTOGEN and might not allow
it to set an optimal value based on observed usage. Whenever possible, use
MIN_parameter values (such as MIN_GBLPAGES) to
set the minimum value that can be set for a parameter by AUTOGEN.
AUTOGEN increases the value if necessary. It also adjusts related
parameters unless they are hardcoded, in which case information is
provided in the AGEN$PARAMS.REPORT file. Use MAX_parameter values to set a maximum value when it is necessary to limit a parameter
to a known maximum value (this is rarely necessary). Enter numeric values as
integers without commas (for example, 10000). Enter alphabetic characters
in lower or uppercase. HP recommends that you
include comments in the MODPARAMS.DAT file indicating who changed
the value, when it was done, and why it was done. An exclamation
point (!) serves as a comment starter and can appear anywhere on a
line. The following example illustrates the modifications recommended
in the preceding bulleted items: ! the following changes made by K.Newcomb on 9/20/03
!
SWAPFILE=0 ! don’t re-size the SWAPFILE on AUTOGEN runs
MIN_gblsections=750 ! required for DECwindows MOTIF
MIN_NPAGEDYN=2750000 ! set npagedyn to a min of 2.75 million |
For more information about the MODPARAMS.DAT file
and about using AUTOGEN in general, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. 7.23.2 Modifying System Parameters After an Upgrade | |
Review the file SYS$SYSTEM:MODPARAMS.DAT. The
upgrade procedure created a new version of this file. The old version
is named SYS$SYSTEM:MODPARAMS.DAT_OLD. The new MODPARAMS.DAT file
contains all the parameters in the old file, plus various parameters
that the upgrade procedure added to ensure that all necessary system
parameters are properly propagated from the earlier version of OpenVMS.
The upgrade procedure also adds comment lines to explain the source
of the parameters in each section of the new MODPARAMS.DAT file. Note that the old MODPARAMS.DAT is included in
the new MODPARAMS.DAT each time an upgrade is performed. Because
of this, if MODPARAMS.DAT is not reviewed and cleaned up after each
upgrade, it might eventually contain many levels of duplicated parameters.
For this reason, you should review MODPARAMS.DAT after each upgrade.
This enables you to eliminate any duplication. You can also take
this opportunity to modify any parameters, if necessary. Based on your examination of AGEN$PARAMS.REPORT,
you might need to modify parameter values in MODPARAMS.DAT. The following subsections are examples of instances
where you need to modify parameters in MODPARAMS.DAT. 7.23.2.1 System File SizesAUTOGEN sets the following files at sizes appropriate
for your system: If you have special workloads or configurations,
you can specify different sizes for these files by performing the
following steps: Log
in to the SYSTEM account. Enter
the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES |
If
the file sizes displayed need to be adjusted, add symbols to the MODPARAMS.DAT
file (described in detail in the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems), and repeat step 2 until you are satisfied with the file sizes. When
you are satisfied with the file sizes, enter the following command
to ensure that the modified system files are installed when the system
is rebooted: $ @SYS$UPDATE:AUTOGEN GENPARAMS SETPARAMS |
7.23.2.2 OpenVMS Cluster ParametersIf you are upgrading an OpenVMS Cluster system,
note the following: The upgrade procedure
creates a new MODPARAMS.DAT for each system root on your system disk.
Normally, there is one root for each computer that boots from the
system disk. You must review and adjust each of these MODPARAMS.DAT
files individually. The MODPARAMS.DAT file
for the system on which you are running is located in the SYS$SYSROOT:[SYSEXE]MODPARAMS.DAT
file. The MODPARAMS.DAT files for other roots on the same system
disk can be found in SYS$SYSDEVICE:[SYSx.SYSEXE]MODPARAMS.DAT,
where x represents the root number; for example,
SYS0, SYS1, SYS2, and so forth. (Valid root numbers might include
hexadecimal digits—SYSA, SYSB, and so forth.) Be sure the EXPECTED_VOTES
value is correct. This value is the sum of all votes in the cluster.
For example, if there are five computers in the cluster and each
has one vote, the value is 5.
|
Printable version
