HP OpenVMS Version 8.3-1H1 for Integrity Servers Upgrade and Installation Manual
HP Part Number: BA322-90077
Published: October 2007
Edition: 1.0
© Copyright 2007 Hewlett-Packard Development Company, L.P
Legal Notice
Confidential computersoftware. Valid license fromHP requiredfor possession,use or copying. Consistent with FAR 12.211and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The informationcontained hereinis subject to change without notice. The only warrantiesfor HPproducts and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP
shall not be liable for technical or editorial errors or omissions contained herein.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Java, the coffee cup logo, and all Java based marks are trademarks or registered trademarks of Sun Microsystems in the United States or other
countries.
Kerberos is a trademark of the Massachusetts Institute of Technology.
Microsoft, Windows,Microsoft NT, and MicrosoftXP are U.S. registered trademarks of Microsoft Corporation. Microsoft Vista is either a registered
trademark or trademark of Microsoft Corporation in the United States and/or other countries.
UNIX is a registered trademark of The Open Group.
The HP OpenVMS documentation set is available on CD-ROM.
Table of Contents
Preface..............................................................................................................................17
About this document............................................................................................................................17
Intended Audience................................................................................................................................17
When to Use This Manual....................................................................................................................17
New and Changed Information in this Edition....................................................................................17
Document Organization.......................................................................................................................19
Typographical Conventions..................................................................................................................20
Related Information..............................................................................................................................21
Publishing History................................................................................................................................22
HP Encourages Your Comments..........................................................................................................23
How to Order Additional Documentation...........................................................................................23
1 Getting Started.............................................................................................................25
1.1 Key Terms........................................................................................................................................25
1.2 Getting to Know Your Integrity Server...........................................................................................26
1.2.1 Entering Commands at Integrity Server Console Interfaces...................................................26
1.2.2 Integrity Server Tools..............................................................................................................26
1.2.3 Virtual Connect (VC) on HP BladeSystem c-Class Enclosures...............................................27
1.2.4 Cell-Based Server Terminology...............................................................................................27
1.2.5 Getting Started: Main Steps After You Unpack Your Integrity Server...................................27
1.3 Examining Software and Hardware Components .........................................................................28
1.3.1 Hardware Components...........................................................................................................28
1.3.2 Software Components.............................................................................................................29
1.3.3 OpenVMS for Integrity Servers Operating Environment DVD..............................................29
1.3.4 Firmware on Integrity Server Systems....................................................................................29
1.3.4.1 Checking Firmware Version ...........................................................................................29
1.3.4.2 Creating a Firmware Update CD....................................................................................30
1.3.4.3 Updating Your Firmware from the Firmware Update CD.............................................31
1.3.5 Device-Naming Conventions..................................................................................................31
1.4 Using the Operating System Menu.................................................................................................32
1.4.1 Using the Install, Upgrade, or Reconfigure OpenVMS Option (1).........................................33
1.4.1.1 INITIALIZE Option.........................................................................................................34
1.4.1.2 PRESERVE Option..........................................................................................................34
1.4.2 Using the Display Layered Products Option (2).....................................................................35
1.4.3 Using the Install or Upgrade Layered Products Option (3)....................................................36
1.4.4 Using the Show Installed Products Option (4)........................................................................38
1.4.5 Using the Reconfigure Installed Products Option (5).............................................................39
1.4.6 Using the Remove Installed Products Option (6)...................................................................40
1.4.7 Using the Patches and Recovery Data Option (7)...................................................................41
1.4.8 Using the Execute DCL Option (8)..........................................................................................42
1.4.9 Using the Shutdown Option (9)..............................................................................................42
1.5 Making the Install/Upgrade/Backup Selection ..............................................................................43
2 Preparing to Install in an OpenVMS Cluster Environment.......................................45
2.1 Preinstallation Tasks for OpenVMS Cluster Environments............................................................45
2.2 Review OpenVMS Cluster Information..........................................................................................45
2.3 Mixed-Version Support in OpenVMS Cluster Systems..................................................................45
2.4 OpenVMS Cluster Information You Need......................................................................................47
2.5 Dismounting the Target System Disk Elsewhere in the Cluster.....................................................48
Table of Contents 3
2.6 Beginning the Installation...............................................................................................................48
3 Installing the OpenVMS Operating System..............................................................49
3.1 Installation Tasks.............................................................................................................................49
3.2 Booting the OpenVMS Operating System Media...........................................................................49
3.2.1 Booting the OpenVMS I64 OE DVD.......................................................................................50
3.2.1.1 Booting from the Local Drive..........................................................................................50
3.2.1.2 Booting Over the Network Using the InfoServer utility.................................................51
3.2.1.3 Booting Using HP SIM Provisioning..............................................................................51
3.2.1.4 Booting Using vMedia.....................................................................................................52
3.3 Installing the OpenVMS Operating System onto a System Disk....................................................52
3.3.1 Differences Between OpenVMS I64 and Alpha Installations.................................................52
3.3.2 Responding to Prompts During the Installation.....................................................................52
3.3.3 Installing OpenVMS Using Option 1 of the Operating System Menu...................................53
3.4 Booting the New OpenVMS System Disk.......................................................................................72
3.4.1 Booting the OpenVMS I64 System Disk..................................................................................72
3.4.2 Next Steps................................................................................................................................73
3.5 Joining an OpenVMS Cluster..........................................................................................................74
3.6 Running AUTOGEN.......................................................................................................................75
3.7 Rebooting After AUTOGEN...........................................................................................................75
3.8 Logging In to the SYSTEM Account................................................................................................76
3.8.1 Logging In from a Character-Cell Terminal............................................................................76
3.8.2 Logging In from a Workstation...............................................................................................76
3.9 Postinstallation Tasks......................................................................................................................76
4 Before Upgrading the OpenVMS Operating System...............................................77
4.1 Preupgrade Tasks............................................................................................................................77
4.2 Documentation to Review Before Upgrading Your System...........................................................77
4.3 Notes, Cautions, and Restrictions...................................................................................................78
4.3.1 Upgrade Paths.........................................................................................................................78
4.3.2 Update License Requirements.................................................................................................78
4.3.3 Components You Choose Not to Install..................................................................................78
4.3.4 Licenses and Layered Products...............................................................................................79
4.4 Saving Archived Files from Being Deleted by the Upgrade...........................................................79
4.5 Preparing the System Disk..............................................................................................................79
4.5.1 Checking the Directory Structure and Preserving Your Security Protections........................79
4.5.2 Checking the SYSCOMMON Directories................................................................................79
4.5.3 Examining the System Disk....................................................................................................80
4.5.4 Checking the Size of the System Disk.....................................................................................80
4.5.5 Returning Authorization and AGEN$INCLUDE Files to the System Disk...........................81
4.5.5.1 Authorization Files..........................................................................................................81
4.5.5.2 AGEN$INCLUDE Files...................................................................................................82
4.5.6 Verifying System Parameters..................................................................................................82
4.6 Ensuring You Have a Recent FEEDBACK.DAT File.......................................................................83
4.7 Shadowing Environment................................................................................................................84
4.7.1 Setting the Boot Device...........................................................................................................85
4.7.2 Creating a Nonshadowed Target Disk....................................................................................85
4.8 Backing Up the System Disk...........................................................................................................85
4.9 Finishing Preupgrade Tasks............................................................................................................86
5 Preparing to Upgrade in an OpenVMS Cluster Environment.................................87
5.1 Preupgrade Tasks for OpenVMS Cluster Environments................................................................87
5.2 Review OpenVMS Cluster Information .........................................................................................87
4 Table of Contents
5.3 Mixed-Version Support in an OpenVMS Cluster Environment.....................................................88
5.4 Adding a New System to an OpenVMS Cluster.............................................................................89
5.5 Types of Upgrades...........................................................................................................................89
5.5.1 Concurrent Upgrade...............................................................................................................89
5.5.1.1 How a Concurrent Upgrade Works................................................................................89
5.5.1.2 Preparing Your System for a Concurrent Upgrade.........................................................89
5.5.2 Rolling Upgrade......................................................................................................................90
5.5.2.1 How a Rolling Upgrade Works.......................................................................................90
5.5.2.2 Notes and Restrictions....................................................................................................90
5.5.2.3 Preparing Your System for a Rolling Upgrade...............................................................91
6 Upgrading the OpenVMS Operating System...........................................................95
6.1 Upgrade Tasks.................................................................................................................................95
6.2 Booting the OpenVMS Operating System Media...........................................................................95
6.2.1 Booting the OpenVMS I64 OE DVD.......................................................................................95
6.2.1.1 Booting from the Local Drive..........................................................................................96
6.2.1.2 Booting Over the Network Using the InfoServer Utility................................................97
6.2.1.3 Booting Using HP SIM Provisioning..............................................................................97
6.2.1.4 Booting Using vMedia.....................................................................................................97
6.3 Performing the Upgrade..................................................................................................................97
6.3.1 Upgrading the System Using Option 1 of the Operating System Menu................................97
6.3.2 Choosing INITIALIZE or PRESERVE.....................................................................................98
6.3.3 Specifying the Target Disk.......................................................................................................98
6.3.4 Selecting Reinstallation and Reconfiguration Options...........................................................99
6.3.5 Checking for Recovery Data..................................................................................................100
6.3.6 Specifying the Volume Label.................................................................................................101
6.3.7 Specifying the On-Disk Structure Level................................................................................101
6.3.8 Choosing Whether to Allow the Procedure to Create and Validate Boot Options ..............103
6.3.9 Warning About Removal of the DECRAM Command.........................................................104
6.3.10 Setting OpenVMS Cluster Membership Information..........................................................104
6.3.11 Updating Time Zone Information.......................................................................................104
6.3.12 Upgrading Windowing, Networking, and Related Products.............................................105
6.4 Completing the Upgrade...............................................................................................................106
6.4.1 Choosing Descriptive Help Text............................................................................................106
6.4.2 Removing Older Versions of ENCRYPT...............................................................................106
6.4.3 Secure Delivery Validation....................................................................................................107
6.4.4 Saving Archived Files............................................................................................................107
6.4.5 Selecting Product Component Options.................................................................................107
6.4.6 Component and Product Installation Confirmation Messages.............................................109
6.4.7 Upgrade Creates and Validates Boot Options ......................................................................110
6.4.8 Upgrade Completes and Returns to OpenVMS Operating System Menu...........................111
6.4.9 Shutting Down the System....................................................................................................112
6.5 What to Do After Shutdown..........................................................................................................112
7 After Installing or Upgrading the OpenVMS Operating System..........................113
7.1 Postinstallation and Postupgrade Tasks........................................................................................113
7.2 Backing Up Your System Disk.......................................................................................................115
7.3 Registering Your Licenses..............................................................................................................116
7.4 Set System Parameters for Volume Shadowing (New Installations Only; Optional)...................117
7.5 Running AUTOGEN to Set System Parameter Changes..............................................................118
7.6 Forming the Shadow Set................................................................................................................118
7.7 Customizing the System (New Installations, Some Upgrades)....................................................119
7.7.1 Creating Network Proxy Authorization Files.......................................................................120
Table of Contents 5
7.7.2 Setting Up the Queue Manager and Default Queues ...........................................................120
7.7.3 Configuring a Multihead System (Optional)........................................................................121
7.7.4 Configuring DECnet .............................................................................................................121
7.7.5 Configuring HP TCP/IP Services for OpenVMS...................................................................122
7.7.6 Installing and Configuring Third-Party Networking Software............................................122
7.8 Initializing or Configuring Other Installed Components.............................................................122
7.8.1 Initializing CDSA (Optional).................................................................................................123
7.8.2 Configuring the Availability Manager Base Software (Optional).........................................124
7.8.3 Configuring Kerberos (Optional)..........................................................................................125
7.8.4 Configuring SSL for OpenVMS (Optional)...........................................................................126
7.8.5 Configure WBEM Services for OpenVMS (Optional)...........................................................127
7.8.5.1 Configuring WBEM Services for OpenVMS (Where Not Configured Previously)......128
7.8.5.2 Configuring WBEM Services for OpenVMS (Where Configured Previously).............129
7.8.6 Configure WBEM Providers for OpenVMS (Optional)........................................................131
7.8.7 Configure the Instant Capacity Software (Optional)............................................................132
7.8.8 Configure the Pay per use Software (Optional)....................................................................132
7.8.9 Configure HP SIM (Optional)...............................................................................................132
7.8.10 Initializing and Running the Performance Data Collector Base Software (Optional).........133
7.8.10.1 User Privileges and Quotas.........................................................................................133
7.8.10.2 Startup File...................................................................................................................133
7.8.10.3 Compatibility with Prior Releases...............................................................................134
7.8.10.4 Running TDC_RT........................................................................................................134
7.8.10.5 Installation in OpenVMS Clusters...............................................................................135
7.8.11 Preparing to Use OpenVMS Management Station (Optional)............................................135
7.8.12 Installing OpenVMS Debugger Clients on a PC (Optional) ...............................................135
7.9 Creating a System-Specific Login Welcome Message (Optional).................................................135
7.10 Examining Your Command Procedures (Upgrades Only)..........................................................136
7.11 Adding and Removing Operating System Files (Optional)........................................................136
7.12 Compressing the System Libraries (Optional, OpenVMS I64: Not Recommended)..................138
7.13 Installing Patches (Optional but Recommended)........................................................................139
7.14 Installing and Configuring Layered Products (New Installations, Some Upgrades).................141
7.14.1 Alternative Procedure..........................................................................................................142
7.15 Creating Print Queues (New Installations, Some Upgrades)......................................................143
7.16 Updating SYSTARTUP_VMS.COM to Start Layered Products and Print Queues.....................143
7.17 Creating Accounts (New Installations, Some Upgrades)............................................................143
7.18 Testing the System with UETP (Optional)...................................................................................143
7.19 Backing Up the Customized System Disk and Initiating Systematic Backups...........................143
7.20 Reforming the Shadow Set as Final Postupgrade Backup..........................................................144
7.21 Rebooting Cluster Members (Upgrades Only)............................................................................144
7.22 Running AUTOGEN to Tune the System....................................................................................144
7.23 Modifying System Parameters.....................................................................................................145
7.23.1 General Notes About Modifying System Parameters.........................................................145
7.23.2 Modifying System Parameters After an Upgrade...............................................................146
7.23.2.1 System File Sizes..........................................................................................................146
7.23.2.2 OpenVMS Cluster Parameters.....................................................................................146
A Configuring OpenVMS I64 Hardware Operation and Boot Operations, and
Booting and Shutting Down Your System...................................................................149
A.1 Configuration and Management Utilities for HP Integrity Servers ............................................149
A.1.1 Overview of Utilities and Console Options.........................................................................150
A.1.2 Configuration and Management Utilities on Cell-Based Servers........................................152
A.1.3 Using the Delete or Backspace Key with Integrity Server Utilities......................................152
A.2 Selecting Your OpenVMS Console for the Integrity Server System.............................................152
A.2.1 Selecting Your OpenVMS Console (Not Applicable to rx2600 Integrity Servers)...............154
6 Table of Contents
A.2.1.1 Using the EFI Boot Manager to Select the OpenVMS Console....................................155
A.2.1.2 Using the EFI Shell to Select the OpenVMS Console...................................................156
A.2.2 Selecting Your OpenVMS Console on rx2600 Integrity Servers...........................................157
A.3 Overview of Using EFI.................................................................................................................161
A.3.1 General Notes About Using EFI...........................................................................................162
A.4 Enabling or Disabling Hyper-Threading on Dual-Core Processors............................................164
A.5 Configuring and Managing OpenVMS Booting on Integrity Servers .........................................164
A.5.1 Checking the ACPI Configuration for Booting OpenVMS in an nPartition........................165
A.5.2 Setting Boot Options for Your System Disk.........................................................................165
A.5.2.1 Adding a Boot Option and Setting Boot Flags ............................................................166
A.5.2.1.1 Using EFI to Set Automatic Booting of Your System Disk...................................168
A.5.2.2 Displaying EFI Boot Entries and Mapped OpenVMS Devices....................................168
A.5.2.3 Setting EFI Boot Option Countdown Timer (Timeout)................................................169
A.5.2.4 Saving and Restoring EFI Settings...............................................................................169
A.5.3 Writing a New Boot Block....................................................................................................170
A.5.4 Alpha and Equivalent Integrity Server System Boot Commands........................................172
A.6 Booting Operations.......................................................................................................................172
A.6.1 Overview of Booting on a Cell-Based Server ......................................................................173
A.6.1.1 Booting the nPartition Hardware.................................................................................173
A.6.1.2 Booting OpenVMS I64 on an nPartition.......................................................................174
A.6.2 Booting the OpenVMS I64 OE DVD from the Local Drive..................................................174
A.6.2.1 Alternate Method of Using EFI to Boot the DVD........................................................175
A.6.3 Booting the OpenVMS I64 OE DVD from the InfoServer....................................................178
A.6.4 Booting an Image of the OpenVMS I64 OE DVD Using HP SIM Provisioning...................178
A.6.5 Booting an Image of the OpenVMS I64 OE DVD Using vMedia.........................................178
A.6.6 Booting from a Fibre Channel Device..................................................................................178
A.6.7 Booting Manually from the Local System Disk....................................................................178
A.6.8 Performing a Conversational (Interactive) Boot...................................................................179
A.6.9 Booting with Minimum Startup...........................................................................................180
A.6.10 Booting with the XDelta Utility (XDELTA)........................................................................180
A.6.11 Booting from a Different Root Directory............................................................................181
A.6.12 Emergency Booting.............................................................................................................181
A.6.12.1 Booting with Default System Parameters...................................................................181
A.6.12.2 Booting Without Startup and Login Procedures........................................................182
A.6.12.3 Booting Without a User Authorization File...............................................................183
A.7 Halt and Shutdown Procedures...................................................................................................184
A.7.1 Halting the Integrity Server to Recover from Hangs and Crashes......................................184
A.7.2 Shutting Down the System...................................................................................................185
A.7.2.1 Orderly Shutdown........................................................................................................185
A.7.2.2 Emergency Shutdown with OPCCRASH.EXE............................................................185
A.8 Troubleshooting Procedures.........................................................................................................186
A.8.1 If the System Does Not Boot.................................................................................................186
A.8.1.1 For Hardware Problems...............................................................................................186
A.8.1.2 For Software Problems.................................................................................................186
A.8.2 Detecting and Responding to System Problems..................................................................186
B Setting Up and Performing Network Booting.........................................................189
B.1 About the OpenVMS InfoServer Utility........................................................................................189
B.2 Setting Up Your System as an InfoServer Client...........................................................................191
B.2.1 Determining the Local Network I/O Card to Be Used .........................................................191
B.2.2 Adding the Network Boot Option to the EFI Boot Manager................................................192
B.2.3 Verifying the Network I/O Device Is Bootable by EFI..........................................................193
B.3 Setting Up the InfoServer Server...................................................................................................193
B.4 Setting Up the BOOTP Boot Server and TFTP Server ..................................................................196
Table of Contents 7
B.5 Booting OpenVMS I64 from the InfoServer..................................................................................199
B.6 Troubleshooting InfoServer Boot Problems..................................................................................201
C Using HP SIM and vMedia to Install and Upgrade OpenVMS...........................203
C.1 HP SIM Provisioning of OpenVMS..............................................................................................203
C.1.1 About HP SIM and Provisioning..........................................................................................203
C.1.2 Prerequisites for HP SIM Provisioning................................................................................204
C.1.3 Setting Up InfoServer Support.............................................................................................205
C.1.4 Setting Up vMedia................................................................................................................207
C.1.5 Setting Up HP SIM and the Windows Server to Provision OpenVMS................................214
C.1.5.1 Installing the OpenVMS Provisioning Plug-in for HP SIM.........................................214
C.1.5.2 Discovering and Identifying Your New Provisioning Client MPs ..............................214
C.1.6 Provisioning OpenVMS........................................................................................................217
C.1.6.1 Provisioning OpenVMS Through the InfoServer.........................................................218
C.1.6.2 Provisioning OpenVMS Through vMedia...................................................................226
C.2 Using vMedia Independently of HP SIM.....................................................................................232
C.2.1 Prerequisites for Using vMedia to Install or Upgrade OpenVMS.......................................233
C.2.2 Using vMedia to Install or Upgrade OpenVMS...................................................................234
D Setting Up and Booting Fibre Channel Storage Devices......................................241
D.1 Booting on a Fibre Channel Storage Device on OpenVMS I64 Systems......................................241
D.1.1 Checking the Firmware Version...........................................................................................241
D.1.2 Obtaining the IPF Offline Diagnostics and Utilities.............................................................242
D.1.3 Configuring and Booting FC Boot Device............................................................................242
D.1.4 Configuring Additional Nodes to Boot into a Cluster Using a Shared Disk.......................245
E Backing Up and Restoring the System Disk.............................................................247
E.1 Reasons for Backing Up the System Disk.....................................................................................247
E.2 Suggested Procedures...................................................................................................................247
E.3 OpenVMS Cluster Caution...........................................................................................................247
E.4 Backing Up the System Disk.........................................................................................................248
E.4.1 Getting Started......................................................................................................................248
E.4.2 Mounting Devices.................................................................................................................248
E.4.3 Performing the System Disk Backup....................................................................................248
E.4.4 Changing the Disk Volume Cluster Size...............................................................................249
E.4.5 Logging Out, Shutting Down, and Rebooting......................................................................249
E.5 Restoring the System Disk............................................................................................................249
E.5.1 Getting Started......................................................................................................................249
E.5.2 Mounting Devices.................................................................................................................250
E.5.3 Performing the System Disk Restore....................................................................................250
E.5.4 Logging Out, Shutting Down, and Rebooting......................................................................250
E.6 Alternative Backup and Restore Procedure (Minimum OpenVMS Environment)......................251
E.6.1 Preparing an Alternate System Disk.....................................................................................251
E.6.2 Using the Alternate System Disk..........................................................................................252
F Installing the OpenVMS Internationalization Data Kit...........................................255
G Preparing to Use OpenVMS Management Station...............................................257
G.1 Preparing Your OpenVMS System...............................................................................................257
G.1.1 Setting Up in a Mixed-Architecture Cluster Environment..................................................257
G.1.2 Starting the Server on Other Nodes.....................................................................................259
8 Table of Contents
G.1.3 Error Log Information..........................................................................................................259
G.1.4 Updating the Printer and Storage Database.........................................................................259
G.1.5 Editing the System Files.......................................................................................................259
G.1.6 Controlling the Printer and Storage Environment...............................................................260
G.1.7 Keeping Your Printer Environment Up to Date...................................................................260
G.1.7.1 When Is the Database Updated?..................................................................................261
G.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually?................................................261
G.1.7.3 What Are the Requirements for Running TNT$UTILITY.COM?................................261
G.1.8 Keeping Your Storage Environment Up to Date..................................................................262
G.1.9 Enabling Disk Quotas...........................................................................................................262
G.1.10 Caching Storage Configuration Data..................................................................................262
G.1.11 Running Third-Party TCP/IP Stacks...................................................................................262
G.1.12 Determining and Reporting Problems...............................................................................263
G.1.13 Removing the OpenVMS Management Station Server......................................................263
G.2 Preparing Your PC........................................................................................................................263
G.2.1 Required Memory and Disk Space.......................................................................................263
G.2.2 Distribution Files..................................................................................................................263
G.2.3 Required Software................................................................................................................263
G.2.4 Time Required for Installation.............................................................................................263
G.2.5 Copying the Client File to the PC.........................................................................................263
G.2.6 Installation Directory............................................................................................................264
G.2.7 Installation Procedure..........................................................................................................264
G.2.8 Recovering from Errors........................................................................................................264
G.3 After Installing the Client Software on Your PC..........................................................................264
G.4 Defining TCP/IP Nodes................................................................................................................264
G.5 Removing Version 2.1 of the OpenVMS Management Station Client..........................................264
G.6 Removing OpenVMS Management Station.................................................................................264
G.7 Getting Started with OpenVMS Management Station.................................................................265
H Removing the OpenVMS Operating System..........................................................267
I Alternative Ways to Initialize the System Disk..........................................................269
I.1 Alternative Method of Initialization..............................................................................................269
I.2 Removing the Diagnostic Partition File ........................................................................................270
Glossary.........................................................................................................................271
Index...............................................................................................................................281
Table of Contents 9
10
List of Figures
D-1 Fibre Channel Host and SAN Storage Controller Configuration...............................................245
11
12
List of Tables
1-1 Definitions of Terms......................................................................................................................25
1-2 Getting OpenVMS Started on Integrity Servers............................................................................28
2-1 Preinstallation Checklist................................................................................................................45
2-2 Warranted Cluster Support...........................................................................................................46
2-3 Supported Migration Pairs............................................................................................................46
3-1 Installation Checklist.....................................................................................................................49
3-2 Prompts for OpenVMS Cluster Configurations............................................................................74
4-1 Preupgrade Checklist....................................................................................................................77
4-2 Logical Names for Relocated Authorization Files........................................................................81
5-1 Preupgrade Checklist for OpenVMS Cluster Environments........................................................87
5-2 Warranted Cluster Support...........................................................................................................88
5-3 Supported Migration Pairing........................................................................................................88
6-1 Upgrade Checklist.........................................................................................................................95
7-1 Postinstallation and Postupgrade Checklist................................................................................114
A-1 Alpha and Integrity Server EFI Command Equivalents.............................................................172
A-2 SYSGEN Commands Used in the SYSBOOT Procedure.............................................................179
A-3 Emergency Boot Procedures........................................................................................................181
B-1 InfoServer Booting: Differences Between Alpha and I64 Systems..............................................189
B-2 Procedure for Enabling InfoServer Network Booting.................................................................190
13
14
List of Examples
3-1 Component Options and Suboptions............................................................................................68
B-1 Setting Up the Boot Server and Client.........................................................................................198
15
16
Preface
About this document
This document explains how to install, or upgrade to, Version 8.3-1H1 of the OpenVMS for
Integrity servers (OpenVMS I64) operating system. Also included are the prerequisites for
installing and upgrading your software and the required and optional tasks you can perform
after you complete the software installation or upgrade.
Intended Audience
This manual is intended for anyone responsible for installing or upgrading the OpenVMS I64
operating system, and for the startup, shutdown, and backup operations required on Integrity
servers running this software.
When to Use This Manual
Use this manual if you need to install or upgrade the OpenVMS operating system software
yourself or if you need to perform certain startup, shutdown, or backup operations. If you received
factory-installed software (FIS) with your Integrity server, see the release notes provided with
the software, and use this manual for any information not covered in those release notes.
New and Changed Information in this Edition
The following information is new or revised for OpenVMS Version 8.3–1H1:
• Support for the latest HP Integrity servers supporting Intel® Itanium® Dual-Core processors,
including the HP Integrity BL860c Server Blade
Some of these servers do not include a built-in CD/DVD drive. You can use an external USB
CD/DVD drive (you must supply this drive and the required cable; they are not included
with the Integrity servers). However, OpenVMS Version 8.3–1H1 supports provisioning
and virtual media (vMedia) devices to allow you to boot, install, or upgrade OpenVMS over
the network. For an up-to-date list of servers supported by this release of OpenVMS, see
the HP OpenVMS Alpha Version 8.3 and HP OpenVMS I64 Version 8.3-1H1 Software Product
Description (SPD 82.35.xx).
• Management support, including provisioning, providers, and WBEM infrastructure
OpenVMS on HP Integrity rx3600 and rx6600 servers and on HP Integrity BL860c Server
Blades can be managed from HP Systems Insight Manager (HP SIM) Version 5.2 or later.
HP SIM (an HP implementation of WBEM) provides simplified, centralized management
of multiple servers and platforms through a web-based, unified interface. HP SIM is
supported on OpenVMS from Microsoft Windows® ProLiant servers. The Windows server
requires an OpenVMS plug-in for HP SIM (the plug-in is available from the web; for more
information, see Section C.1.5.1 (page 214)). To be managed by HP SIM, your Integrity server
requires HP WBEM (Web-Based Enterprise Management) Services for OpenVMS and the
HP WBEM Providers forOpenVMS. TheseWBEM products areinstalled automaticallywith
OpenVMS but you must configure them manually. (Configuration instructions for these
products are provided in Section 7.8.5 (page 127) and Section 7.8.6 (page 131), respectively.)
The WBEM products enable HP SIM to retrieve information about the OpenVMS operating
system on your Integrity server and to manage the operating system. For network
functionality, the WBEM products also require HP TCP/IP Services for OpenVMS and HP
SSL.
With provisioning support, you can use HP SIM to install or upgrade OpenVMS quickly
and easily on one or more servers in the network, much in the same way as HP-UX supports
About this document 17
provisioning. Such support facilitates installing or upgrading OpenVMS on Integrity servers
that do not include a CD/DVD drive.
Provisioning is supported with HP SIM Version 5.1 or later. You use HP SIM to initiate the
provisioning, after which the installation or upgrade process occurs automatically in the
background. To provide provisioning over the network, you can use HP SIM in two ways:
— In conjunction withthe InfoServersoftware utility (and TCP/IP Services for OpenVMS),
you create a service for a bootable image of OpenVMS (a container file) stored at a
location on the network accessible to the InfoServer. In this use of HP SIM, you can
provision multiple servers (up to 8) simultaneously.
— In conjunction with vMedia, you create an ISO image of the OpenVMS Operating
Environment (OE) DVD, store the image on the server where HP SIM is running, and
use HP SIM to connect vMedia to that image. Using vMedia, you can provision one
server at a time. Currently, provisioning does not support booting from a shadowed
system disk.
For more information about HP SIM, see the Information Library on the following website:
http://www.hp.com/go/hpsim
For information about configuring WBEM Services for OpenVMS and WBEM Providers for
OpenVMS, see Section 7.8.5 (page 127) and Section 7.8.6 (page 131). For information about
setting up and performing provisioning, see Appendix C (page 203).
• Support for virtual media (vMedia)
The vMedia device is the first in a series of virtual-disk capabilities included in the current
generation of management-processor (MP, Integrity iLO 2) hardware. vMedia consists of
two primary components: firmware in MP hardware that emulates a USB DVD and Java™
code that runs on a remote PC and performs I/O to the PC’s local CD/DVD drive. vMedia
can provide you with a virtual CD/DVD drive that connects over the network to your
Integrity server, just as if they are physically connected. You can use vMedia for initial
system installation on a system without a built-in DVD, or remote installation on a system
physically located elsewhere. It also allows you to install layered products, either remotely
or on systems without a built-in DVD. For information about setting up and performing
vMedia provisioning, see Appendix C (page 203).
• Support for Virtual Connect (VC) on HP BladeSystem c-Class enclosures
HP Virtual Connect (VC) is a set of interconnect modules and embedded software available
for HP BladeSystem c-Class enclosures. VC simplifies the setup and administration of server
connections. Where most server interconnect choices come with compromises such as too
many cablesor too much to manage, VC reduces the number of network cablesand simplifies
management while adding the unique ability to wire everything once, then add, replace or
recover servers in minutes instead of hours or days. VC is enabled with a choice of Ethernet
and Fibre Channel modules designed for the HP BladeSystem. The built-in HP Virtual
Connect manager defines a server connection profile for each server bay—even before a
server is installed. This profile establishes the Media Access Control (MAC) addresses for
all Network Interface Controllers (NICs), the World Wide Names (WWNs) for all Host Bus
Adapters (HBAs), and the SAN boot parameters. The profile holds them constant so that
even if the server is changed, the configuration and connection profile stay constant. When
a new server takes its place, the same profile is assigned.
For more information about VC, select the Virtual Connect networking link at the following
website:
http://www.hp.com/go/bladesystem/virtualconnect
In addition, see the HP Virtual Connect for c-Class BladeSystem User's Guide, available at the
following location:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00865618/c00865618.pdf
18
• Support for a VGA console and USB keyboard as console devices for booting
With VGA support, you can now connect a monitor, keyboard, and mouse directly to
connectors provided for that purpose on your Integrity server panel. You no longer need
to use a serial console, including PC/terminal emulator or character-cell terminal as a console.
On systems that do not include an embedded graphics device, you might be able to select
a graphics option card in a PCI slot to be the graphics console. Check your Integrity server
hardware documentation for details. OpenVMS also supports multiple VGA devices on the
same Integrity server. XDELTA boot and conversational (interactive) boot are not supported
over a VGA console. VGA console support for OpenVMS is available for most Integrity
servers. For more information, see Section A.2 (page 152).
• Support of new time zones
Eight new time zones have been added to this release:
— America/Atikokan
— America/Blanc-Sablon
— America/North_Dakota/New_Salem
— Europe/Guernsey
— Europe/Isle_of_Man
— Europe/Jersey
— Europe/Podgorica
— Europe/Volgograd
For information about setting the local time zone for your computer, seeSection 3.3.3
(page 53). The new time zones are not shown in the examples provided in this manual.
•
Document Organization
This manual is organized as follows:
• Chapter 1 (page 25) defines key terms and provides information about hardware and
software components. Review this chapter before performing any installation or upgrade.
• Chapter 2 (page 45) provides preliminary information.
• Chapter 3 (page 49) explains how to install the OpenVMS I64 operating system.
• Chapter 4 (page 77) describes how to prepare your system for an upgrade.
• Chapter 5 (page 87) supplements Chapter 4 (page 77) with additional tasks you must
perform before upgrading an OpenVMS Cluster system.
• Chapter 6 (page 95) describes how to upgrade the operating system.
• Chapter 7 (page 113) describes the tasks you must perform after installing or upgrading the
operating system.
• Appendix A (page 149) provides an overview of the utilities available with HP Integrity
servers, and explains how to configure the system console, how to configure boot options,
and how to boot the OpenVMS operating system.
• Appendix B (page 189) explains how to set up and perform network booting for installations
and upgrades using the InfoServer utility, a software application available on certain
OpenVMS Alpha and OpenVMS I64 systems.
• Appendix C (page 203) explains how to set up and perform provisioning (installations and
upgrades) of OpenVMS on one or more Integrity servers in a network using HP SIM. In
addition, this appendix explains how to use vMedia to install or upgrade OpenVMS on an
Integrity server in the network.
• Appendix D (page 241) explains how to boot the Fibre Channel storage device.
• Appendix E (page 247) explains how to back up and restore the system disk.
Document Organization 19
• Appendix F (page 255) discusses the OpenVMS internationalization data kit (VMSI18N) and
how to install it.
• Appendix G (page 257) explains how to prepare your OpenVMS system and your PC to run
the OpenVMS Management Station server and client software.
• Appendix H (page 267) explains how to remove the OpenVMS operating system from your
disk.
• Appendix I (page 269) explains alternate methods of initializing an OpenVMS I64 system
disk and includes information about diagnostic partitions on OpenVMS I64 system disks.
• The Glossary (page 271) defines key terms used in this manual.
Typographical Conventions
The following conventions are used in this manual:
MeaningConvention
Ctrl/X
PF1X
Enter
…
.
.
.
( )
[ ]
|
A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while
you press another key or a pointing device button.
A sequence such as PF1X indicates that you must first press and release the key labeled
PF1 and then press and release another key (x) or a pointing device button.
In examples, a key name in bold indicates that you press that key.
A horizontal ellipsis in examples indicates one of the following possibilities:− Additional
optional arguments in a statement have been omitted.− The preceding item or items can
be repeated one or more times.− Additional parameters, values, or other information can
be entered.
A vertical ellipsis indicates the omission of items from a code example or command
format; theitems are omitted because they are not important to the topicbeing discussed.
In command format descriptions, parentheses indicate that you must enclose choices in
parentheses if you specify more than one. In installationor upgrade examples, parentheses
indicate the possible answers to a prompt, such as: Is this correct? (Y/N) [Y]
In command format descriptions, brackets indicate optional choices. You can choose one
or more items or no items. Do not type the brackets on the command line. However, you
must include the brackets in the syntax for OpenVMS directory specifications and for a
substring specification in an assignment statement. In installation or upgrade examples,
brackets indicate the default answer to a prompt if you press Enter without entering a
value, as in: Is this correct? (Y/N) [Y]
In commandformat descriptions,vertical bars separate choiceswithin bracketsor braces.
Within brackets, the choices are optional; within braces, at least one choice is required.
Do not type the vertical bars on the command line.
20
{ }
bold type
italic type
UPPERCASE TYPE
Example
In command format descriptions, braces indicate required choices; you must choose at
least one of the items listed. Do not type the braces on the command line.
Bold type represents the name of an argument, an attribute, or a reason. In command
and scriptexamples, bold indicates user input. Bold type also representsthe introduction
of a new term.
Italic type indicates important information, complete titles of manuals, or variables.
Variables include information that varies in system output (Internal error number), in
command lines (/PRODUCER=name), and in command parameters in text (where dd
represents the predefined code for the device type).
Uppercase type indicates a command, the name of a routine, the name of a file, or the
abbreviation for a system privilege.
This typefaceindicates code examples, command examples, and interactive screen displays.
In text, this type also identifies website addresses, UNIX command and pathnames,
PC-based commands and folders, and certain elements of the C programming language.
MeaningConvention
–
numbers
Related Information
Before installing, upgrading, or using the OpenVMS operating system on your computer, be
sure you have access to the following documents. Some of the documents listed here are from
an earlier OpenVMS version documentation set. They have not been revised, they remain valid
for OpenVMS Version 8.3-1H1.
• Cover Letter for HP OpenVMS Version 8.3-1H1 for Integrity Servers and any other cover letters
included with your kit.
• HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes, which
describes enhancements and new features included in this release of the OpenVMS I64
operating system and provides important supplementary information about the OpenVMS
I64 operating system.
• HP OpenVMS License Management Utility Manual, which explains how to use the License
Management Facility (LMF), the license management tool for the OpenVMS operating
system. The manual describes licensing requirements and the tasks required to manage
licenses.
• HP OpenVMS Version 8.3 Release Notes, which provides important supplementary information
about the OpenVMS I64 system that might still be valid for the OpenVMS 8.3-1H1 release.
• HP OpenVMS Cluster Systems and Guidelines for OpenVMS Cluster Configurations, if you plan
to install your system in an OpenVMS Cluster environment.
• The mostrecent version of the DECwindowsMotif for OpenVMS Installation Guide and Managing
DECwindows Motif for OpenVMS Systems (if you plan to install and customize DECwindows
Motif for OpenVMS software).
• HP Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture, which
provides information about CDSA software.
• HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS, which provides
information about HP SSL software.
• HP Open Source Security for OpenVMS, Volume 3: Kerberos, which provides information about
Kerberos software.
• HP Availability Manager Installation Instructions, which provides information about Availability
Manager software and is available at the following website:
http://www.hp.com/products/openvms/availabilitymanager
A hyphen at the end of a command format description, command line, or code line
indicates that the command or statement continues on the following line.
All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal
radixes—binary, octal, or hexadecimal—are explicitly indicated.
• For documentation related to the Performance Data Collector (TDC), see the following
website:
http://www.hp.com/products/openvms/tdc/
• The following networking software documents (if you plan to install and configure
DECnet-Plus for OpenVMS, DECnet Phase IV for OpenVMS,or TCP/IP Services for OpenVMS
software):
— HP TCP/IP Services for OpenVMS Installation and Configuration
— DECnet-Plus for OpenVMS Installation and Configuration
Documentation for these networking products is included on the OpenVMS Version 8.3
Online Documentation CD. Hardcopy documentation must be purchased separately.
Related Information 21
• For documentation related to Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP),
and Pay per use (PPU), see the HP Instant Capacity User’s Guide and HP Pay per use User’s
Guide on the following website:
http://docs.hp.com/en/hplex.html#Utility%20Pricing
• HP SIM documentation is available in the Information Library on the following website:
http://www.hp.com/go/hpsim
• HP gWLM documentation is available in the Information Library on the following website
(select the Information Library link and then the Manuals, Release Notes, Manpages link
and see the Version A.01.01 manuals):
http://www.hp.com/go/gwlm
Information about gWLM and documentation for installing the gWLM agent on OpenVMS
I64 systems, including release notes, is available at the following website:
http://h71000.www7.hp.com/openvms/integrity/integrity_gwm.html
• The hardware manuals that are supplied with your Integrity server computer. These manuals
provide detailed information about your system hardware, including the operation of the
system unit, the drives, and the monitor.
During the course of installing, upgrading, or using the OpenVMS operating system on your
computer, you could refer to the following documents as well:
• HP OpenVMS License Management Utility Manual, whichcontains detailed information about
registering your software licenses.
• HP OpenVMS System Manager's Manual and the HP OpenVMS System Management Utilities
Reference Manual, which contain information about system management operations and
utilities that you might need to use when you install, upgrade, customize, and maintain
your OpenVMS system. The HP OpenVMS System Management Utilities Reference Manual:
M-Z provides complete information about using the PCSI utility PRODUCT command to
add or remove files, install other software, and related operations.
• HP Volume Shadowing for OpenVMS, which you might need if you are installing or upgrading
the OpenVMS operating system on a shadowed system disk.
• HP OpenVMS Management Station Installation Guide, which provides information about getting
started, setting up, and using OpenVMS Management Station.
For additional information about HP OpenVMS products and services, see the following website:
http://www.hp.com/go/openvms
For information about managing nPartitions on midrange or Superdome servers, see the nPartition
Administrator's Guide (previously titled HP System Partitions Guide: Administration for nPartitions).
For the latest hardware documentation for HP Integrity servers, see the following website:
http://docs.hp.com/en/hw.html
Publishing History
The document printing date and part number indicate the document’s current edition. The
printing date will change when a new edition is printed. Minor changes may be made at reprint
without changing the printing date. The document part number will change when extensive
changes are made. Document updates may be issued between editions to correct errors or
document product changes. To ensure that you receive the updated or new editions, you should
subscribe to the appropriate product support service. See your HP sales representative for details.
You can find the latest version of this document on line at:
22
http://www.docs.hp.com.
Manufacturing Part
Number
Systems
HP Encourages Your Comments
HP welcomes your comments on this manual.
Please send comments to either of the following addresses:
Internet: openvmsdoc@hp.com
Postal Mail:
Hewlett-Packard Company
OpenVMS Documentation Group
ZKO3-4/Y02
110 Spit Brook Road
Nashua, NH 03062-2698
How to Order Additional Documentation
Visit the following World Wide Web address for information about how to order additional
documentation:
http://www.hp.com/go/openvms/doc/order
Publication DateEdition NumberSupported VersionsSupported Operating
October, 20071.0Version 8.3-1H1OpenVMS I64BA322–90077
HP Encourages Your Comments 23
24
1 Getting Started
This chapter defines key terms and describes preliminary procedures you must perform before
installing or upgrading your OpenVMS system.
NOTE: Throughout this book, examples are taken from OpenVMS I64 installations or upgrades
except where stated otherwise. OpenVMS DCL commands are in uppercase, while HP Integrity
servers console commands are in lowercase.
1.1 Key Terms
Table 1-1 lists a few key terms you need to know before you install or upgrade the system.
Table 1-1 Definitions of Terms
DefinitionTerm
HSx device
InfoServer
A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS
Cluster system environment share disks. The disk on which you install orupgrade the operating
system can be connected to one of these systems (for example, an HSV or HSG).
A general-purpose disk storage server. For OpenVMS Alpha systems, the InfoServer may be
an independent hardware device or, beginning with OpenVMS Version 8.3, it may be a utility
(software application) on an OpenVMS system. On OpenVMS I64 systems, the InfoServer is
only available as a software application on an OpenVMS system.
The InfoServer hardware can serve CDs only (it does not support DVDs); thus, this hardware
device cannotserve the OpenVMS I64 operating environment (OE) DVD. TheInfoServer utility
can serve both DVDs and CDs (for OpenVMS I64 andOpenVMS Alpha systems, respectively).
The systems connected to the same LAN can use the InfoServer utility to boot the OpenVMS
operating system from a virtual drive (instead of the local drive). For more information about
the InfoServer utility, see the HP OpenVMS Version 8.3 New Features and Documentation Overview.
local drive
operating system
media
provisioning
source drive
system disk
target drive
virtual media
(vMedia)
A drive on your computer system, such as a CD, DVD, or disk drive (hard drive), that is
connected directly to the computer. If you have a standalone computer, it is likely that all
drives connected to the computer system are local drives.
The OpenVMS Alpha operating system CD or the OpenVMS for Integrity servers Operating
Environment DVD (OE DVD) included with an OpenVMS distribution kit, which contains
the OpenVMS operating system and the installation and other procedures described in this
manual.
Using HPSystems Insight Manager (HP SIM), the processof installingor upgrading OpenVMS
on one or more Integrity servers automatically. HP SIM initiates the process and the installation
or upgrade automatically continues in the background.
The drive that holds the operating system media during an upgrade or installation. This can
be a local drive or an InfoServer virtual drive. The drive contains the OpenVMS Alpha operating
system CD or the OpenVMS for Integrity servers Operating Environment DVD, or a copy of
it.
The disk from which OpenVMS is typically booted. During an installation or upgrade, this is
the target disk because it receives files from the source drive. After installation or upgrade,
the target drive is booted and becomes the system disk.
The drive that holds the target system disk during the upgrade or installation. Note: the target
drive must be a hard drive, not a CD or DVD.
A virtual-disk capability included with Integrated Lights Out (iLO) 2 Management Processor
(MP) on Integrity servers. vMedia provides virtual devices that mimic physical hardware
devices. For example, it can provide a virtual CD/DVD drive that emulates the DVD drive on
a PC and connects over the network to your Integrity server as if it were physically connected.
You can use vMedia to install OpenVMS on Integrity servers that do not include a built-in
DVD drive or that are physically located elsewhere. vMedia can provide the network service
for HP SIM provisioning, or it can be used independently of HP SIM.
1.1 Key Terms 25
1.2 Getting to Know Your Integrity Server
The OpenVMS operating system is now supported on a wide variety of HP Integrity servers,
including the following:
• Entry-class servers, which include members of the rx16nn, rx26nn, rx36nn, rx46nn, and
rx66nn series and the BladeSystems Integrity BL860c Server Blade
• Midrange servers, which include members of the rx76nn and rx86nn series
• High-end servers (Superdome)
For an up-to-date list of servers supported by the current release of OpenVMS, see the HP
OpenVMS Alpha Version 8.3 and HP OpenVMS I64 Version 8.3-1H1 Software Product Description
(SPD 82.35.xx).
The hardware, firmware, and software supported might vary significantly from system to system.
Integrity servers are available in many different configurations. The hardware, utilities, and
hardware configuration procedures might differ significantly across models, and even across
versions of the same model. This manual provides basic information about the firmware,
hardware, and utilities offered on Integrity servers. This information is not meant to replace the
hardware documentation. For the most up-to-date and relevant information for your particular
model, see the hardware documentation for your Integrity server. The hardware documentation
includes model-specific illustrations to guide you. The latest version of documentation for your
server can be found online at:
http://docs.hp.com/en/hw.html
http://www.hp.com/support/itaniumservers
For the latest information about firmware, software requirements, and special considerations
for your Integrity server, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features
and Release Notes.
1.2.1 Entering Commands at Integrity Server Console Interfaces
When entering commands for the Integrity server, if you press Delete on a VTxxx terminal (or
press the key you have mapped to send the DEL/RUBOUT character code in your terminal
emulator), the last character typed might not be deleted. The firmware on Integrity servers where
that unexpected behavior occurs uses Ctrl/H to delete the last character typed. On such Integrity
servers, you can remap your terminal to use Ctrl/H instead of DEL/RUBOUT, as described in
Section A.1.3 (page 152).
1.2.2 Integrity Server Tools
Integrity servers include multiple interfaces for working with various aspects of the server or
server complex. The Management Processor (MP) is available on most Integrity servers. Many
entry-class Integrity servers now come with the Integrated Lights Out (iLO) MP (Integrity iLO
2 MP), which provides a complete remote console experience, including a web-based graphical
user interface and the functionality provided by vMedia. MP and Integrity iLO provide a service
interface that allows access to all hardware and, in a complex, all nPartitions. The MP is always
available, even when the main power source is turned off (MP can operate on standby power).
On cell-based servers (such as rx7620, rx8620, and Superdome), MP is available whether or not
nPartitions are configured or booted in the server complex. You can navigate from MP to and
from the operating system (if it is booted).
The Extensible Firmware Interface (EFI) provides support for operating system loaders and
allows you to configure the firmware and control the booting environment. EFI is accessible only
when the operating system is not booted. On cell-based servers, each nPartition has a separate
EFI console interface. EFI provides support for managing nPartitions. The EFI interface is available
from an nPartition console only when the nPartition is in an active state but has not booted an
operating system.
26 Getting Started
You can move from the EFI interface to MP and back again. Similarly, you can move from MP
to the operating system and back.
1.2.3 Virtual Connect (VC) on HP BladeSystem c-Class Enclosures
HP Virtual Connect (VC) is a set of interconnect modules and embedded software available for
HP BladeSystem c-Class enclosures. VC simplifies the setup and administration of server
connections. Where most server interconnect choices come with compromises such as too many
cables or too much to manage, VC reduces the number of network cables and simplifies
management while adding the unique ability to wire everything once, then add, replace or
recover servers in minutes instead of hours or days.
VC is enabled with a choice of Ethernet and Fibre Channel modules designed for the HP
BladeSystem. The built-in HP Virtual Connect manager defines a server connection profile for
each server bay—even before a server is installed. This profile establishes the Media Access
Control (MAC) addresses for all Network Interface Controllers (NICs), the World Wide Names
(WWNs) for all Host Bus Adapters (HBAs), and the SAN boot parameters. The profile then holds
them constant so that even if the server is changed, the configuration and connection profile stay
constant. When a new server takes its place, the same profile is assigned.
For more information about VC, select the Virtual Connect networking link at the following
website:
http://www.hp.com/go/bladesystem/virtualconnect
In addition, see the HP Virtual Connect for c-Class BladeSystem User's Guide, available at the
following location:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00865618/c00865618.pdf
1.2.4 Cell-Based Server Terminology
A cell-basedserver—such as the HP rx7620, rx8720, or Superdome server—is a hardware complex
that can run one or more operating systems and that supports dividing hardware resources into
nPartitions. Thus, it enables you to configure a complex into one large system or into several
smaller systems.
All processors and memory are contained in cells, each of which can be assigned for exclusive
use by an nPartition. An nPartition defines a subset of the server hardware resources that is used
as an independent system environment. An nPartition has its own EFI system boot interface and
each nPartition boots and reboots independently. Each nPartition provides both hardware and
software isolation so that hardware or software faults in one nPartition do not affect other
nPartitions within the same server complex.
By usingHP software-based nPartition management tools, you can configurenPartition definitions
for a server without physically modifying the server hardware configuration. The main
administration tools for nPartitions are the Partition Manager, which provides a graphical
interface, and the nPartition Commands, which provides a command-line interface. Versions of
these interfaces are provided on HP-UX, Linux®, and Microsoft® Windows® systems. The
nPartition Commands tool is also available on Linux systems. MP and EFI can also perform
nPartition administrative tasks. Slightly different tool sets and capabilities are available on
different server models. For more information, see your hardware documentation. In addition,
see the nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administration
for nPartitions).
1.2.5 Getting Started: Main Steps After You Unpack Your Integrity Server
When you unpack your Integrity server, the main steps for getting OpenVMS up and running
are those listed in Table 1-2. As indicated in the third column, some of the instructions are
provided in this manual. However, for the most up-to-date information specific to your Integrity
1.2 Getting to Know Your Integrity Server 27
server model and version, alwaysrefer to the hardware documentation provided for your Integrity
server.
Table 1-2 Getting OpenVMS Started on Integrity Servers
DocumentationActionStep
1
your server, connect to the MP serial port.
2
Services for OpenVMS.
3
4
From the EFI Shell interface or EFI Boot Manager menu, select
the device for the OpenVMS console.
Power on your Integrity server, insert the OpenVMS I64
distribution media (DVD) into the drive, cycle power, and then
use the EFI boot menu to boot from the DVD.
Section A.2 (page 152)Connect your console cable to the serial port; if MP is present on
Hardware manualOptionally, configure MP to accept connections over TCP/IP
Section A.2 (page 152); if you ordered
your server preinstalled, console
selections are already made but you
might need to change them
For howto poweron and recycle power,
see the hardware documentation; for
instructions on booting the DVD, see
Section 3.2.1 (page 50)
After the initial boot, you need not use EFI to configure boot options. You can configure EFI boot
options while OpenVMS is running by using the OpenVMS I64 Boot Manager
(SYS$MANAGER:BOOT_OPTIONS.COM), as explained in Section A.5.2 (page 165). This utility
is easier to use than EFI and allows you to configure the most pertinent options for your system.
In addition, the OpenVMS installation (and upgrade) procedure can assist you in establishing
and validating boot options for your system disk.
1.3 Examining Software and Hardware Components
Before you begin an installation or upgrade, be sure you have all the required hardware and
software components, as described in the following sections.
1.3.1 Hardware Components
For hardware components, verify the following::
• Be sure the hardware is installed and verified for proper operation. For detailed information,
see the hardware manuals you received with your computer.
For initial installations on Integrity servers, your console terminal requires a standard
PC-to-PC file transfer cable (also known as a null modem cable; 9-pin female connectors at
each end) to connect a PC, laptop, or similar device that includes terminal emulation software;
alternatively, you can use a VGA monitor and USB keyboard (and USB mouse). For
information about setting up your system console, see Section A.2 (page 152).
• Be sure you know how to turn on and operate the components of your system, including
the system unit, console, monitor, drives, terminals, and printers. If necessary, read the
hardware manuals that came with these components.
• Make sure you record the installation procedure. You need a transcript if a problem occurs
during installation. If you are using terminal emulation software, set the software to log the
session. Otherwise, set up your system to record the installation procedure on either a
hardcopy terminal or a printer attached to the console terminal. (See your hardware manuals
for more details about connecting those components to your system.)
28 Getting Started
1.3.2 Software Components
For software components, verify the following:
• Be sure you have all the items listed on the bill of materials contained in the distribution kit.
If your distribution kit is incomplete, notify HP Customer Support and request priority
shipment of any missing items.
• Before installing the OpenVMS operating system software, review all cover letters and
release notes.
1.3.3 OpenVMS for Integrity Servers Operating Environment DVD
Included in your OpenVMS I64 kit is the OpenVMS for Integrity Servers OE DVD, which you
use to install the operating system or to perform operations such as backing up the system disk.
The DVD is labeled similar to the following:
HP OpenVMS Version 8.3-1H1 for Integrity Servers Operating EnvironmentDVD label
I640831H1Volume label
The DVD label is the printed label on the OE DVD. The volume label is the machine-readable
name that the OpenVMS I64 operating system uses to access and identify the DVD.
1.3.4 Firmware on Integrity Server Systems
HP Integrity servers include several firmware components (varying with system type), any of
which might need updating. For the minimum versions recommended, see the HP OpenVMS
Version 8.3-1H1 for Integrity Servers New Features and Release Notes. HP recommends that you sign
up for Subscriber's Choice so that you can automatically receive email notices regarding the
latest firmware updates. Make sure you register all your products to receive the appropriate
firmware update notices. You can sign up for Subscriber's Choice at the following website:
http://itrc.hp.com
To update entry-class Integrity server firmware, follow the instructions provided in this section;
for cell-based servers (midrange and high-end), contact HP Customer Support.
To update your firmware, perform the following steps:
1. Determine the current firmware versions on your Integrity server (see Section 1.3.4.1
(page 29)).
NOTE: To receive notification of new firmware releases for the Integrity server you own,
you can subscribe (free of charge) for drivers and software alerts, as instructed in
Section 1.3.4.1 (page 29).
2. Create a firmware update CD on any system equipped with a CD or CD/DVD-recordable
drive (see Section 1.3.4.2 (page 30)).
3. Update the firmware on your Integrity server (see Section 1.3.4.3 (page 31)).
1.3.4.1 Checking Firmware Version
To determine the firmware version in place on your Integrity server, you can use the Extensible
Firmware Interface (EFI) info fw command at the EFI Shell prompt, as in the following example.
(For cell-based servers, check the firmware at the nPartition console.)
Shell> info fw
You can also use the EFI Boot Manager to obtain firmware information. With MP, you can use
the MP sysrev command.
1.3 Examining Software and Hardware Components 29
NOTE: The info fw command at the EFI> Shell prompt cannot be used while OpenVMS is
running. You can use the MP interface to check firmware on your system while OpenVMS is
running.
NOTE: EFI Shell commands are not case sensitive. However, in this manual, EFI and other
Integrity server interface commands are displayed in lowercase to help distinguish them from
OpenVMS DCL commands.
For more information about the latest firmware for your Integrity server, check the HP OpenVMS
Version 8.3-1H1 for Integrity Servers New Features and Release Notes. In addition, see the information
and resources provided on the HP Support website by following these steps:
1. Go to the following website:
http://www.hp.com/support/itaniumservers
2. Select the appropriate server in the provided list.
The HP Support page that appears provides a list of tasks and services to choose. To
automatically receive drivers and support alerts from HP (free of charge), select “Signup:
drivers and support alerts” from the list of services (you might need to select “See more...”
to access the signup link), and fill out the forms as instructed.
For more information about firmware for your Integrity server, select “Download drivers
and software” from the list of tasks, and continue with the next step.
3. On the “Download drivers and software” page, select “Cross operating system (BIOS,
Firmware, Diagnostics, etc.)”.
4. On the resulting page, locate the appropriate firmware (look for the latest update; previous
versions might also be listed), and select the link for the firmware in the “Description”
column.
5. Select the “Release Notes” tab and read the information about the latest version of firmware
available and the instructions on determining the version of firmware in place on your
Integrity server. Compare your installed version with firmware versions listed in the release
notes.
1.3.4.2 Creating a Firmware Update CD
To create a firmware update CD for your entry-class Integrity server, you need a CD-recordable
drive and software, plus a blank CD-R or CD-RW disk. (For updating firmware on a cell-based
server, you must contact HP Customer Support.)
NOTE: The following instructions are for recording a DVD on an OpenVMS system. You can
record the DVD on any system or PC, such as a Microsoft Windows computer, a Linux system,
or an HP-UX system.
1. Follow steps 1 through 3 from the preceding section.
2. Locate the appropriate ISO-image firmware file. (Look for the latest update; previous versions
might also be listed along with the latest.) Select the link for that file and read the instructions
for the file included in the release notes, and then download the ISO-image firmware
(zip-compressed) file to your system. (To access the release notes, see step 5 in the preceding
section.)
3. Unzip the firmware file into the corresponding .ISO file. The .ISO file is a block copy of the
firmware disk for the Integrity server system. On OpenVMS systems, you can obtain the
INFO-ZIP utility from an OpenVMS Freeware CD and use the UnZip utility provided with
INFO-ZIP. OpenVMS Freeware CDs are packaged with the OpenVMS for Integrity Servers
OE DVD, and the files on the Freeware CDs are available online at the following website:
www.hp.com/go/openvms/freeware
30 Getting Started
The following example shows the command for unzipping an .ISO image of the latest
firmware for an rx2600 system (the file name changes with each update of the firmware
available on the website):
$ UNZIP PF_CPEAKSYS0nnn.ZIP
Archive: SYS$SYSROOT:[SYSMGR]PF_CPEAKSYS0nnn.ZIP
inflating: PF_CPEAKSYS0nnn.ISO
4. Record the data on the CD, specifying the .ISO file as the source for the CD. For instructions
on doing this, enter the following command:
$ @SYS$MANAGER:CDRECORD HELP
NOTE: OpenVMS software includes the CD recording tool CDRECORD. For online help,
enter the @SYS$MANAGER:CDRECORD HELP command at the OpenVMS DCL prompt
as shown previously. For CDRECORD source files, check the OpenVMS Open Source Tools
CD supplied with your OpenVMS I64 OE DVD. For more information about the software,
visit the following website:
http://h71000.www7.hp.com/opensource/opensource.html
1.3.4.3 Updating Your Firmware from the Firmware Update CD
You update the firmware of an entry-class Integrity server from the firmware update CD created
in the preceding section. For instructions, see the release notes provided for the firmware you
downloaded.
IMPORTANT: To update Integrity server firmware on cell-based servers, contact HP Customer
Support.
1.3.5 Device-Naming Conventions
When you perform specific operations, you are asked to specify a device name for the source
drive and one for the target drive. When specifying those device names, note the following
naming conventions:
• When the source drive is a local CD or DVD drive, the device name is similar to the following:
DQA0 (IDE drive) or DNA0 (USB drive)
For a device name, such as DQA0:, note the following conventions:
— DQ is the device code.
— A is the device controller designation.
— 0 is the unit number of the device.
• When the target drive is a local disk, the device name is similar to the following:
DKA0:
• When the source drive is a virtual DVD drive served by the InfoServer, the device name is
typically the following:
DAD1:
• On OpenVMS systems configured in certain OpenVMS Cluster or HSx environments, the
device naming convention is similar to the following:
DUA20.14.0.2.0
The values you specify identify components such as the boot device, controller, unit number
of the boot device, HSx controller node number, and channel numbers. Because these values
vary depending on your specific hardware configuration, see the owner, operator, and
technical service manuals that came with your computer for detailed information.
1.3 Examining Software and Hardware Components 31
1.4 Using the Operating System Menu
The following sections describe how to use the operating system menu to install, upgrade, and
modify your system disk, and perform other related tasks.
The OpenVMS operating system main menu displaysautomatically when you boot the OpenVMS
operating system from the operating system media (for instructions on how to boot from the
operating system media, see Section 3.2 (page 49)). From the menu, you can choose options to
perform any of the following tasks:
• Install or upgrade the operating system from the operating system media.
• Display a list of products that can be installed from the operating system media.
• Install or upgrade layered products from the operating system media.
• Show which products are installed on your system.
• Reconfigure layered products installed on your system.
• Remove products.
• Find, install, and remove patches, and display and remove recovery data.
• Enter the DCL environment from which you can perform preinstallation or maintenance
tasks, such as mounting or showing devices and backing up or restoring files on the system
disk.
• Shut down the system.
The following is a sample display of the OpenVMS main menu:
OpenVMS I64 Operating System, Version 8.3-1H1
(c) Copyright 1976-2007 Hewlett-Packard Development Company, L.P.
Installing required known files...
Configuring devices...
***************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
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/?)
Review the following sections to understand how the menu works. Then you can choose
appropriate menu options when you are asked to do so before, during, and after an installation
or upgrade.
32 Getting Started
1.4.1 Using the Install, Upgrade, or Reconfigure OpenVMS Option (1)
Select option 1 on the operating system main menu to install, upgrade, or reconfigure your
OpenVMS software. Selecting option 1 implements a PCSI utility concept called a platform. The
OpenVMS platform contains:
• The OpenVMS operating system
• Kerberos, Common Data Security Architecture (CDSA), Secure Sockets Layer (SSL),
Performance Data Collector (TDC) (base), Availability Manager (base), WBEM Services
for OpenVMS, and WBEM Providers for OpenVMS, all of which are installed automatically
with OpenVMS
• The optional DECwindows Motif for OpenVMS, DECnet-Plus, DECnet Phase IV, and
TCP/IP Services for OpenVMS products
NOTE: For use of Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP), and Pay per
use (PPU) (supported on cell-based Integrity servers), and for support of such products as gWLM
and HP Systems Insight Manager (HP SIM), you must install TCP/IP Services for OpenVMS.
SSL for OpenVMS is required and is installed automatically.
Including the optional products in the OpenVMS platform allows you to install or upgrade these
products along with the OpenVMS operating system.
When you choose to upgrade the system disk, and the OpenVMS software on the disk is the
same version, you are given options to reinstall or to reconfigure the OpenVMS system or
reconfigure the OpenVMS platform.
Before installing or upgrading OpenVMS, see the information in the following chapters, as
appropriate:
• Chapter 2: “Preparing to Install in an OpenVMS Cluster Environment” (page 45)
• Chapter 3: “Installing the OpenVMS Operating System” (page 49)
• Chapter 4: “Before Upgrading the OpenVMS Operating System” (page 77)
• Chapter 5: “Preparing to Upgrade in an OpenVMS Cluster Environment” (page 87)
• Chapter 6: “Upgrading the OpenVMS Operating System” (page 95)
NOTE: Before installing or upgrading OpenVMS on a target drive in an OpenVMS Cluster,
make sure the target system disk is not mounted elsewhere in the cluster. The target system disk
must be dismounted clusterwide (except on the system from which the installation or upgrade
is being performed) and must remain so during the installation or upgrade.
When you select option 1 on the operating system main menu, the system asks whether you
want to preserve or initialize the system disk. The display is similar to the following:
There are two choices for Installation/Upgrade:
INITIALIZE - Removes all software and data files that were
previously on the target disk and installs OpenVMS I64.
PRESERVE -- Installs or upgrades OpenVMS I64 on the target disk
and retains all other contents of the target disk.
* Note: You cannot use PRESERVE to install OpenVMS I64 on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE]
1.4 Using the Operating System Menu 33
1.4.1.1 INITIALIZE Option
When you specify the INITIALIZE option, the following operations take place:
• All software and data files that already exist on the target disk are removed. The software
can only be recovered from a backup of the disk, so make sure that you either have a backup
or will not need the data again.
• The operating system is installed.
Specify the INITIALIZE option and perform a full installation under any of the following
conditions:
• If your computer is new (it has never had any version of any operating system running on
it, including factory-installed software).
• If your computer is already running a version of the OpenVMS operating system and you
want to overwrite the entire contents of the system disk (the operating system, application
software, and user files).
• If you want to keep an existing system disk and install OpenVMS on a different disk.
• If you are running the OpenVMS operating system but cannot upgrade. For example, if you
changed the names of system directories on the system disk, the upgrade procedure will
not work correctly. Therefore, unless you restore the system disk to its original directory
structure, you must reinstall the operating system using the INITIALIZE option.
NOTE: During initialization of an OpenVMS I64 target system disk, the installation process
creates a diagnostic partition, visible only at the console prompt. For more information about
this partition and options you can take, see Appendix I (page 269).
For systems that support the Instant Capacity (iCAP) feature, CPU status (how many cores are
available and how much time they have remaining) is not affected by initialization of the system
disk. Such information is stored in NVRAM on the Integrity server.
1.4.1.2 PRESERVE Option
When you specify the PRESERVE option, the following operations take place:
The OpenVMS operating system is not already
installed on the target disk
The OpenVMS operating system is installed on
the target disk
NOTE: If you intend to choose the PRESERVE option (because there are certain files on the
disk that you want to retain), HP recommends that you first make a backup copy of your system
disk. If there is any problem during the installation or upgrade that might affect the integrity of
the disk, you will have the backup copy as a safeguard.
If you choose the PRESERVE option and choose a target disk that already contains the OpenVMS
Version 8.3-1H1 software, you are provided with the option to either reconfigure or reinstall the
OpenVMS operating system:
• Reconfigure the operating system if you want to change the options you chose to include
when the operating system was installed.
• Reinstall the operating system if you think that your system files might have become
corrupted.
For additional configuration information, see Section 7.11 (page 136).
THEN ...IF ...
• The operating system is installed.
• All other contents of the target disk are retained.
The operating system is upgraded, as follows:
• Old operating system files and new filesare merged or replaced.
• All other contents of the target disk are retained.
34 Getting Started
1.4.2 Using the Display Layered Products Option (2)
Use option 2 to display layered products that can be installed.
NOTE: Although option 2 displays any patch kits available from the OpenVMS distribution
media, HP recommends using option 7 to display patch kits; option 7 enables you to specify
locations to search in addition to the standard location.
When you select option 2 on the operating system main menu, the following information is
displayed:
• The version of OpenVMS and versions of the required components and optional products
that can be installed or upgraded when you select option 1 on the main menu.
• The layered product kits that are available for installation when you select option 3 on the
operating system main menu. The DECwindows graphical user interface and HP networking
products are shown again, along with other layered products.
NOTE: The two lists of products (the products that can be installed or upgraded and the layered
product kits available for installation) might be the same or very similar. Generally, products
that can be installed or upgraded along with the OpenVMS operating system should be installed
or upgraded with the OpenVMS operating system.
The following is an example of a display. WBEMCIM is the file name used in the PCSI kit for
the WBEM Services for OpenVMS product, which is available on OpenVMS I64 systems only.
CIM stands for the Common Information Model, which differentiates the current OpenVMS
WBEM product from the original one that is based on the Simple Network Maintenance Protocol
(SNMP). The version numbers in this example do not necessarily reflect the version numbers of
the products actually shipped with OpenVMS Version 8.3-1H1.
The following versions of the OpenVMS operating system,
required components and optional other products
are available on the OpenVMS distribution media (CD/DVD).
They can be installed by selecting option 1:
HP I64VMS VMS version V8.3-1H1
HP I64VMS AVAIL_MAN_BASE V8.3-1H1
HP I64VMS CDSA version V2.3-306
HP I64VMS KERBEROS version V3.1-152
HP I64VMS SSL V1.3-284
HP I64VMS TDC_RT version V2.3-1
HP I64VMS WBEMCIM version V2.61-A070728
HP I64VMS WBEMPROVIDERS version V1.5-31
HP I64VMS DWMOTIF version V1.6
HP I64VMS DECNET_PLUS version V8.3-1H1
HP I64VMS DECNET_PHASE_IV version V8.3-1H1
HP I64VMS TCPIP version V5.6
The following Layered Product kits are available on the OpenVMS
Distribution media (CD/DVD). They can be installed by selecting
option 3. If they are already installed, they can be reconfigured
by selecting option 5, or removed by selecting option 6.
----------------------------------- ----------- ----------
PRODUCT KIT TYPE KIT FORMAT
----------------------------------- ----------- ----------
HP I64VMS AVAIL_MAN_BASE V8.3-1H1 Full LP Compressed
HP I64VMS CDSA V2.3-306 Full LP Compressed
HP I64VMS DECNET_PHASE_IV V8.3-1H1 Full LP Compressed
HP I64VMS DECNET_PLUS V8.3-1H1 Full LP Compressed
HP I64VMS DWMOTIF V1.6 Full LP Compressed
1.4 Using the Operating System Menu 35
HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 Full LP Compressed
HP I64VMS KERBEROS V3.1-152 Full LP Compressed
HP I64VMS SSL V1.3-284 Full LP Compressed
HP I64VMS TCPIP V5.6 Full LP Compressed
HP I64VMS TDC_RT V2.3-1 Full LP Compressed
HP I64VMS WBEMCIM V2.61-A070728 Full LP Compressed
HP I64VMS WBEMPROVIDERS V1.5-31 Full LP Compressed
----------------------------------- ----------- ----------
12 items found
Press Return to continue...
1.4.3 Using the Install or Upgrade Layered Products Option (3)
Use option 3 on the operating system main menu for normal installations or upgrades of the
layered products.
NOTE: Although option 3 installs any patch kits available from the OpenVMS distribution
media, HP recommends using option 7 to install patch kits; option 7 enables you to install patch
kits that are not located in the standard location. In addition, option 7 saves recovery data; when
you use option 7 to remove patch kits, only kits with recovery data are removed.
You can use option 1 to install or upgrade the DECwindows graphical user interface and HP
networking products along with the OpenVMS operating system.
When you select option 3, the PCSI utility allows you to choose whether to install layered products
or to register layered products that are on the target disk but are not in the Product Database. If
you attempt to reinstall the same version of a product that is already installed, the product is
reinstalled. Note that any patches that were applied to the product are removed. If you want to
reconfigure, select the reconfigure option (5) on the main menu.
As of Version 8.3, most of the software kits included on the OpenVMS distribution media are
signed using Secure Delivery. When you use option 3 of the OpenVMS I64 operating system
menu, these kits are validated by the PCSI utility. You can install kits created before the secure
delivery process was enabled in OpenVMS Version 8.3. (However, after you install or upgrade
to OpenVMS Version 8.3 or later, signed kits that you install subsequently are validated, including
any signed kits included on the distribution media.) The DCL command PRODUCT SHOW
HISTORY displays the validation status of these kits as unsigned rather than as a validated kit.
As shown in the following example, you are also prompted for a target disk and asked whether
you want brief or detailed descriptions. The procedure presents a list of products and allows
you to select any or all of these products. Alternatively, you can exit without installing or
upgrading any products.
NOTE: The layered products listed include the required CDSA, Kerberos, SSL, TDC, Availability
Manager, WBEM Services for OpenVMS, and WBEM Providers for OpenVMS. Also included
are theoptional DECwindows, DECnet Phase IV, DECnet-Plus, and TCP/IPServices for OpenVMS
products. Support of such features as Instant Capacity (iCAP), Temporary Instant Capacity
(TiCAP), and Pay per use (PPU), and for products such as gWLM and HP SIM, requires TCP/IP
Services for OpenVMS. When you use HP SIM to provision OpenVMS on an Integrity server,
TCP/IP Services for OpenVMS is installed automatically.
You can install (or upgrade to) the new implementation of TCP/IP Services for OpenVMS (Version
5.6) as part of the OpenVMS upgrade. If you want to install Version 5.6 separately, choose the
following product, selecting the appropriate option as in the example that follows.
HP I64VMS TCPIP V5.6
***********************************************************
36 Getting Started
The procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
Do you want to INSTALL or REGISTER? (INSTALL/REGISTER/?) [INSTALL] INSTALL
***********************************************************
If you choose to install or upgrade DECwindows Motif,
please note the following:
o If you did not select the OpenVMS DECwindows server support
and workstation files options, DECwindows Motif will not run.
You must add these options to use DECwindows Motif.
If you choose to install or upgrade DECnet-Plus or DECnet Phase IV,
please note the following:
o If you did not select the OpenVMS DECnet option, neither version
of DECnet will run. You must add this option to use DECnet.
If you want to install a patch kit, please use main menu option 7.
Press Return to continue...
You must enter the device name for the target disk on which
the layered product(s) installation will be performed.
Enter device name for target disk: [DKB300] (? for choices) DKB300
DKB300: is labeled V82SYS.
The install operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing "?".
Do you always want detailed descriptions? (Yes/No) [No] NO
1 - HP I64VMS AVAIL_MAN_BASE V8.3-1H1 Layered Product
2 - HP I64VMS CDSA V2.3-306 Layered Product
3 - HP I64VMS DECNET_PHASE_IV V8.3-1H1 Layered Product
4 - HP I64VMS DECNET_PLUS V8.3-1H1 Layered Product
5 - HP I64VMS DWMOTIF V1.6 Layered Product
6 - HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 Layered Product
7 - HP I64VMS KERBEROS V3.1-152 Layered Product
8 - HP I64VMS SSL V1.3-284 Layered Product
9 - HP I64VMS TCPIP V5.6 Layered Product
10 - HP I64VMS TDC_RT V2.3-1 Layered Product
11 - HP I64VMS WBEMCIM V2.61-A070728 Layered Product
12 - HP I64VMS WBEMPROVIDERS V1.5-31 Layered Product
13 - All products listed above
? - Help
E - Exit
Choose one or more items from the menu separated by commas: 9
1.4 Using the Operating System Menu 37
NOTE: When you boot the OpenVMS operating system media and select the option to install
layered products, the installation procedure for the selected layered product(s) does not run the
Installation Verification Procedure (IVP) for layered products. Because the operating system is
booted from the media and the layered products are installed on a different device (the target
drive), the IVPs cannot execute correctly. However, you can run the IVP for each layered product
after you boot the target system (see the layered product installation documents for information
about running the IVP).
1.4.4 Using the Show Installed Products Option (4)
Use option 4 on the operating system main menu to display a list of products that have been
installed on a selected target disk by the PCSI utility. Products that were installed by VMSINSTAL
or other installation methods do not appear in this display unless they have been registered in
the PCSI utility’s product database.
The following is a sample display of the prompts and information that appear when you select
option 4. WBEM Services for OpenVMS and WBEM Providers for OpenVMS are available on
OpenVMS I64 systems only. The version numbers in this example do not necessarily reflect the
version numbers of the products actually shipped with OpenVMS Version 8.3-1H1.
You must enter the device name for the system disk for which
you want to display installed products.
If you enter an invalid device or one which is not a system disk
an error will occur.
(Enter "^" and press Return to return to main menu.)
Enter device name for system disk: [DKB300] (? for choices) DKB300
%MOUNT-I-MOUNTED, V82SYS mounted on _DKB300:
The default is an 80-column display that does not include
Maintenance (patches) or Referenced by information.
Do you want the full, 132-column display? (Yes/No) [No] NO
------------------------------------- ------------ -----------PRODUCT KIT TYPE STATE
------------------------------------- ------------ -----------HP I64VMS AVAIL_MAN_BASE V8.3-1H1 Full LP Installed
HP I64VMS CDSA V2.3-306 Full LP Installed
HP I64VMS DECNET_PLUS V8.3-1H1 Full LP Installed
HP I64VMS DWMOTIF V1.6 Full LP Installed
HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 Full LP Installed
HP I64VMS KERBEROS V3.1-152 Full LP Installed
HP I64VMS OPENVMS V8.3-1H1 Platform Installed
HP I64VMS TCPIP V5.6 Full LP Installed
HP I64VMS VMS V8.3-1H1 Oper System Installed
HP I64VMS SSL V1.3-284 Full LP Installed
HP I64VMS TDC_RT V2.3-1 Full LP Installed
HP I64VMS WBEMCIM V2.61-A070728 Full LP Installed
HP I64VMS WBEMPROVIDERS V1.5-31 Full LP Installed
------------------------------------- ------------ ------------
12 items found
Do you wish to display product history? (Yes/No) [No] YES
----------------------------------- ----------- ----------- -------------------PRODUCT KIT TYPE OPERATION DATE AND TIME
----------------------------------- ----------- ----------- -------------------HP I64VMS AVAIL_MAN_BASE V8.3-1H1 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS CDSA V2.3-306 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS DECNET_PLUS V8.3-1H1 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS DWMOTIF V1.6 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS KERBEROS V3.1-152 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS OPENVMS V8.3-1H1 Platform Install 25-SEP-2007 18:04:23
38 Getting Started
HP I64VMS TCPIP V5.6 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS VMS V8.3-1H1 Oper System Install 25-SEP-2007 18:04:23
HP I64VMS SSL V1.3-284 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS WBEMCIM V2.61-A070728 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS WBEMPROVIDERS V1.5-31 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS TDC_RT V2.3-1 Full LP Install 25-SEP-2007 18:04:23
HP I64VMS AVAIL_MAN_BASE V8.3 Full LP Remove 25-SEP-2007 18:04:23
HP I64VMS CDSA V2.2 Full LP Remove 25-SEP-2007 18:04:23
HP I64VMS DECNET_PHASE_IV V8.3 Full LP Remove 25-SEP-2007 18:04:23
HP I64VMS DWMOTIF V1.6 Full LP Remove 25-SEP-2007 18:04:23
HP I64VMS OPENVMS V8.3 Platform Remove 25-SEP-2007 18:04:23
HP I64VMS VMS V8.3 Oper System Remove 25-SEP-2007 18:04:23
HP I64VMS KERBEROS V3 Transition Remove 25-SEP-2007 18:04:23
HP I64VMS KERBEROS V3 Transition Reg Product 25-SEP-2007 17:20:44
HP I64VMS CDSA V2.1 Full LP Install 27-AUG-2004 21:07:15
HP I64VMS DECNET_PHASE_IV V8.2 Full LP Install 27-AUG-2004 21:07:15
HP I64VMS DWMOTIF V1.5 Full LP Install 27-AUG-2004 21:07:15
HP I64VMS OPENVMS V8.3 Platform Install 27-AUG-2004 21:07:15
HP I64VMS TCPIP V5.4-18 Full LP Install 27-AUG-2004 21:07:15
HP I64VMS VMS V8.3 Oper System Install 27-AUG-2004 21:07:15
----------------------------------- ----------- ----------- --------------------
26 items found
Press Return to continue...
NOTE: The products listed in the product history vary from system to system, depending on
the actual history of the system. For definitions of the kit types, see the HP POLYCENTER Software
Installation Utility Developer’s Guide.
1.4.5 Using the Reconfigure Installed Products Option (5)
Use option 5 to reconfigure layered products, including the DECwindows graphical user interface
and HP networking products. This allows you to change the product choices you made during
a previous installation or upgrade.
You can reconfigure a product only if all of the following conditions are true:
• The product is available for installation while your system is booted from the operating
system media. For information about displaying products that are available for installation,
see Section 1.4.2 (page 35) (option 2 on the main menu).
• The product is installed. For information about displayinginstalled products, see Section 1.4.4
(page 38) (option 4 on the main menu).
• The version of the product that is available for installation is the same as the version of the
product that is installed.
When you select option 5 on the operating system main menu, the procedure prompts you for
a target disk name and asks whether you want brief or detailed descriptions about the
reconfiguration options. The procedure then lists the products you can configure. You can select
any or all of these products, or you can exit without reconfiguring products.
The following is a sample display of the prompts and information that might appear when you
select option 5. The version numbersin this example do not necessarily reflect the version numbers
of the products actually shipped with OpenVMS Version 8.3-1H1.
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
1.4 Using the Operating System Menu 39
You must enter the device name for the target disk on which
the layered product(s) reconfiguration will be performed.
Enter device name for target disk: [DKB300] (? for choices) DKB300
DKB300: is labeled V82SYS.
The reconfigure operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing "?".
Do you always want detailed descriptions? (Yes/No) [No] NO
1 - HP I64VMS AVAIL_MAN_BASE V8.3-1H1 Layered Product
2 - HP I64VMS CDSA V2.3-306 Layered Product
3 - HP I64VMS DECNET_PHASE_IV V8.3-1H1 Layered Product
4 - HP I64VMS DECNET_PLUS V8.3-1H1 Layered Product
5 - HP I64VMS DWMOTIF V1.6 Layered Product
6 - HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 Layered Product
7 - HP I64VMS KERBEROS V3.1-152 Layered Product
8 - HP I64VMS SSL V1.3-284 Layered Product
9 - HP I64VMS TCPIP V5.6 Layered Product
10 - HP I64VMS TDC_RT V2.3-1 Layered Product
11 - HP I64VMS WBEMCIM V2.61-A070728 Layered Product
12 - HP I64VMS WBEMPROVIDERS V1.5-31 Layered Product
13 - All products listed above
? - Help
E - Exit
Choose one or more items from the menu separated by commas:
1.4.6 Using the Remove Installed Products Option (6)
Option 6 allows you to remove products that were installed or registered with the PCSI utility.
(This option removes complete products. To remove patches, use option 7, as described in
Section 1.4.7 (page 41).)
IMPORTANT: Do not remove the following system-integrated products (SIPs): Availability
Manager, CDSA, Kerberos, SSL, TDC_RT, WBEM Services for OpenVMS (WBEMCIM), and
WBEM Providers for OpenVMS. These products are tightly bound with the operating system.
Attempts to remove any of these products might not work as expected and can create undesirable
side effects.
When you select option 6, you are prompted for a target disk name and whether you want brief
or detailed descriptions about the remove options. The procedure then lists the products you
can remove. You can select any or all of these products, or you can exit without removing any
products.
The following is a sample display of the prompts and information that appear when you select
option 6. The version numbers in this example do not necessarily reflect the version numbers of
the products actually shipped with OpenVMS Version 8.3-1H1.
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
40 Getting Started
You must enter the device name for the target disk on which
the layered product(s) removal will be performed.
Enter device name for target disk: [DKB300:] (? for choices) DKB300
DKB300: is labeled V82SYS.
The remove operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing "?".
Do you always want detailed descriptions? (Yes/No) [No] NO
1 - HP I64VMS AVAIL_MAN_BASE V8.3 Layered Product
2 - HP I64VMS CDSA V2.3-306 Layered Product
3 - HP I64VMS DECNET_PHASE_IV V8.3 Layered Product
4 - HP I64VMS DECNET_PLUS V8.3 Layered Product
5 - HP I64VMS DWMOTIF V1.6 Layered Product
6 - HP I64VMS DWMOTIF_SUPPORT V8.3 Layered Product
7 - HP I64VMS KERBEROS V3.1-152 Layered Product
8 - HP I64VMS SSL V1.3-284 Layered Product
9 - HP I64VMS TCPIP V5.6 Layered Product
10 - HP I64VMS TDC_RT V2.3-1 Layered Product
11 - HP I64VMS WBEMCIM V2.61-A070728 Layered Product
12 - HP I64VMS WBEMPROVIDERS V1.5-31 Layered Product
13 - All products listed above
? - Help
E - Exit
Choose one or more items from the menu separated by commas:
1.4.7 Using the Patches and Recovery Data Option (7)
Select option 7 to install or undo patches and to perform related operations. When you select
option 7, the following options submenu appears:
This procedure can perform one of the following operations:
1) Install one or more patches
2) Undo recent patches for which there is recovery data
3) Show recovery data
4) Delete recovery data
5) Find patch kits
Enter CHOICE or X to return to main menu: (1/2/3/4/5/X)
Note the following about these options:
• When you choose submenu option 1, the following information is displayed:
NOTE: Some patch kits cannot be correctly installed by this
procedure; this includes patch kits for versions of
OpenVMS prior to V8.3. Patches for OpenVMS V8.3 and
later install correctly. For patches to other products,
check with the patch kit provider, or install the patch
from the running system.
Options 2 through 5 (undo, show, delete, and find) will work
correctly for all patch kits.
• When you choose submenu option 1, 2, 3, or 4, you are prompted for the target device on
which to perform the operation:
You must enter the device name for the target disk on which
the operation will be performed.
1.4 Using the Operating System Menu 41
Enter device name for target disk: (? for choices) [DKB300]
• When you choose submenu option 1, you are prompted to choose detailed or brief
descriptions, as follows:
The patch operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing ?.
Do you always want detailed descriptions? (Yes/No) [No]
• For each of the submenu options (1 through 5), you are prompted for the patch kit source.
You can specify alternate locations. You can use wildcards when you specify the location.
The prompt and introductory information are displayed as follows:
This procedure will look for patch kits in
SYS$SYSDEVICE:[KITS.*]
If you want to add an additional location, enter the
device and directory specification and press return.
Wildcards are allowed. For example:
dka100:[dir1]
dkb0:[dir1,dir2]
dka200:[dir1,*]
dkb300:[dir1...]
Enter the single letter "D" to reset the default location.
If you do not want to add an additional location, just press return
without entering anything.
Enter additional location, D, or just press Return:
After you provide the necessary information, a PCSI /PRODUCTcommand automatically performs
the operation you requested. If you chose options 1, 2, or 4 from the submenu, the PCSI utility
prompts you for additional input and displays additional information.
1.4.8 Using the Execute DCL Option (8)
When you select option 8, you get access to a subset of DCL commands (such as SHOW DEVICE,
MOUNT, and BACKUP) to perform specific preinstallation and maintenance operations. Note,
however, that this is a restricted DCL environment in that certain DCL commands (such as
PRODUCT) and certain utilities (such as VMSINSTAL) do not function as expected because you
are booting from read-only or write-locked media, and because a full system startup has not
been performed.
A triple dollar sign prompt ($$$) indicates that you are in this restricted DCL environment, as
in the following example:
$$$ SHOW DEVICE
To exit the DCL environment and return to the main menu, enter the LOGOUT command.
1.4.9 Using the Shutdown Option (9)
When you select option 9 on the operating system main menu, your system shuts down and you
are returned to the console prompt (P00>>> on Integrity servers). The system displays a message
similar to the following (this example shows the message from an OpenVMS I64 system):
Shutting down the system
SYSTEM SHUTDOWN COMPLETE
**** Primary HALTED with code HWRPB_HALT$K_REMAIN_HALTED
42 Getting Started
**** Hit any key to cold reboot ****
P00>>>
1.5 Making the Install/Upgrade/Backup Selection
Now that you have reviewed key terms, examined hardware and software requirements, and
learned how to use the menu system included on the OpenVMS operating system media, you
can do the following:
THEN GO TO...IF ...
You want to install the operating system in an OpenVMS Cluster
environment
You want to install the operating system in a nonclustered environment
You want to upgrade the operating system in an OpenVMS Cluster
environment
You want to upgrade the operating system in a standalone environment
Chapter 2(page 45), and then Chapter 3
(page 49). Perform postinstallationtasks
described in Chapter 7 (page 113).
Chapter 3 (page 49). Perform
postinstallation tasks described in
Chapter 7 (page 113).
Chapter 4 (page 77), Chapter 5
(page 87), and then Chapter 6
(page 95). Perform postupgrade tasks
described in Chapter 7 (page 113).
Chapter 4(page 77), and then Chapter 6
(page 95). Perform postupgrade tasks
described in Chapter 7 (page 113).
Appendix E (page 247).You want only to back up or restore your system disk
1.5 Making the Install/Upgrade/Backup Selection 43
44
2 Preparing to Install in an OpenVMS Cluster Environment
This chapter contains information to review and steps to perform before installing OpenVMS in
an OpenVMSCluster environment. If you arenot installing your operating system in an OpenVMS
Cluster environment, go to Chapter 3 (page 49) for information about installing your system.
2.1 Preinstallation Tasks for OpenVMS Cluster Environments
Use the checklist in Table 2-1 to ensure that you perform all necessary tasks prior to installing
your system in an OpenVMS Cluster environment.
Table 2-1 Preinstallation Checklist
SectionTask
□
documentation.
□
migration support in OpenVMS Cluster systems.
□
an installation.
□
cluster.
2.2 Review OpenVMS Cluster Information
Before you install the operating system in an OpenVMS Cluster environment, review any relevant
OpenVMS Cluster information contained in the following documents.
OpenVMS Version 8.3-1H1 Documents
• The Cover Letter for HP OpenVMS Version 8.3-1H1 for Integrity Servers
• The Software Product Descriptions included with your distribution kit
• HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes
OpenVMS Version 8.3 Documents
Section 2.2 (page 45)Review relevant OpenVMSoperating systemand OpenVMSCluster
Section 2.3 (page 45)Familiarize yourself with mixed-version, mixed-architecture, and
Section 2.4 (page 47)Have information ready to provide at the system prompt during
Section 2.5 (page 48)Make sure the target system disk is not mounted elsewhere in the
Chapter 3 (page 49)Begin the installation.□
Information in the following documents remains valid exceptwhere superseded by theOpenVMS
Version 8.3-1H1 documents listed previously.
• HP OpenVMS Version 8.3 Release Notes
• HP OpenVMS Version 8.3 New Features and Documentation Overview
Earlier OpenVMS Documents
Information in the following documents remains valid exceptwhere superseded by theOpenVMS
documents listed previously.
• HP OpenVMS Cluster Systems
• Guidelines for OpenVMS Cluster Configurations
Be sure to consult your network or system manager as well.
2.3 Mixed-Version Support in OpenVMS Cluster Systems
HP provides two levels of support for mixed-version and mixed-architecture OpenVMS Cluster
systems: warranted support and migration support.
2.1 Preinstallation Tasks for OpenVMS Cluster Environments 45
Warranted support means that HP has fully qualified the two specified versions coexisting in
an OpenVMS Cluster and will address all problems identified by customers using this
configuration.
Migration support means that HP has qualified the versions for use together in configurations
that are migrating in a staged fashion to a newer version of OpenVMS VAX, OpenVMS Alpha,
or OpenVMS I64. Problem reports submitted against these configurations will be answered by
HP. However, in exceptional cases, HP may request that you move to a warranted configuration
as part of the solution. Migration support helps customers move to warranted OpenVMS Cluster
pairs. For the minimum version supported for an upgrade to OpenVMS Version 8.3-1H1, see
Section 4.3.1 (page 78).
Warranted cluster support is provided for the combinations shown in Table 2-2. (OpenVMS VAX
systems are not supported with OpenVMS I64 systems in the same cluster.)
Table 2-2 Warranted Cluster Support
Warranted in these combinationsOperating system
OpenVMS Alpha Version 8.3
OpenVMS I64 Version 8.3-1H1
OpenVMS Alpha Version 8.3 and OpenVMS I64 Version 8.3-1H1 or 8.3
or
OpenVMS Alpha Version 8.3 and OpenVMS VAX Version 7.3
OpenVMS I64 Version 8.3-1H1 or 8.3 and OpenVMS Alpha Version 8.3
or
OpenVMS I64 Version 8.3-1H1 and OpenVMS I64 Version 8.3
NOTE: Only two architectures are supported in the same OpenVMS Cluster.
System disks are architecture specific and can be shared only by systems of the same architecture.
An Alpha and I64 system, or an Alpha and VAX system, cannot boot from the same system disk.
However, cross-architecture satellite booting is supported between an Alpha and VAX system.
When you configure an OpenVMS Cluster to take advantage of cross-architecture booting, make
sure that at least one system from each architecture is configured with a disk that can be used
for installations and upgrades. For more information, see the Guidelines for OpenVMS Cluster
Configurations and HP OpenVMS Cluster Systems.
Table 2-3 shows the supported migration pairs.
Table 2-3 Supported Migration Pairs
Operating system
OpenVMS I64 Version 8.3-1H1
Supported with either of these
migrating to OpenVMS I64 Version
8.3-1H1
OpenVMS I64 Version 8.3
OpenVMS I64 Version 8.2-1
For more information, see the OpenVMS Technical Software Support Service website at:
http://www.hp.com/go/openvms/support
In addition, see the OpenVMS Operating System Support Chart at:
http://www.hp.com/go/openvms/supportchart
Before introducing an OpenVMS Version 8.3-1H1 system into an existing OpenVMS Cluster,
you might need to install certain patch kits (also known as remedial kits) on cluster members
running earlier versions of OpenVMS. For a complete list of required patch kits, see the HP
46 Preparing to Install in an OpenVMS Cluster Environment
Supported with either of these migrating
to OpenVMS Alpha Version 8.3
OpenVMS Alpha Version 8.2
OpenVMS Alpha Version 7.3-2
OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the HP OpenVMS
Version 8.3 Release Notes.
For informationabout supporting the TDC_RT software in OpenVMS Clusters, see Section 7.8.10.5
(page 135).
2.4 OpenVMS Cluster Information You Need
If during the installation you answer YES to the system prompt asking whether your system will
be a member of an OpenVMS Cluster, you need to provide the following information after you
boot the system disk:
ExplanationRequired Information
Type of configuration
DECnet node name and node
address
Allocation class value
Whether you want a quorum disk
Configuration types (CI, DSSI, SCSI, local area, or mixed-interconnect) are
distinguished by the interconnect device that the VAX, Alpha, or Integrity server
computers in the OpenVMS Cluster use to communicate with one another. Note
that HP Integrity servers do not support CI, DSSI, or MEMORY CHANNEL
devices.
To obtain the DECnet node name and node address for the computer on which
you are installing the OpenVMS operating system, consult the network or system
manager. If you install DECnet-Plus for OpenVMS (Phase V) software and do
not plan to use DECnet Phase IVfor OpenVMS addresses, then you do notneed
to provide this information.
During the installation procedure, you might be asked for the allocation class
value (ALLOCLASS) of the computeron whichyou are installing the OpenVMS
operating system. For example:
Enter a value for this_node ALLOCLASS parameter:
Note that in an OpenVMS Cluster environment,the allocation class value cannot
be zero if the node serves DSSIor CI disks to othercluster members, or if volume
shadowing will be used on this system or in the cluster. In either case, the
ALLOCLASS value must be a number from 1 to 255.
After you enter the allocation class value, the installation procedure uses it to
automatically set the value of the ALLOCLASS system parameter.
HP recommends that you thoroughly review the chapter on cluster storage
devices in the HP OpenVMS Cluster Systems manual. This manual also includes
the rules for specifying allocation class values.
To help you determine whether you need a quorum disk in the cluster, see the
HP OpenVMS Cluster Systems manual.
Location of the page and swap files
Systems that will be a MOP
server1, disk server, or tape server
Cluster group number and cluster
password
1 Servers that use the Maintenance Operations Protocol (MOP).
2 Cluster group number and password are required by any cluster nodes that use the local area network for cluster
2
communications. In a cluster that uses mixed interconnects, if any of the interconnects require the cluster number
and password, then you must set the cluster number and password for all nodes.
On a nonclustered system, the page and swap files are on one or more local
disks, but on a clustered system, the files might be on one or more local or
clustered disks. See the HP OpenVMS Cluster Systems manual to help you
determine where the page and swap files will belocated for the system on which
you are installing the OpenVMS operating system software.
If you are going to set up either a local area or a mixed-interconnect cluster, you
need to make these determinations.
If you are going to set up a local area or mixed-interconnect cluster that is
LAN-based (Gigabit Ethernet), use the following rules to determine the cluster
group number and password:
• Cluster group number—A number in the range from 1 to 4095 or 61440 to
65535.
• Cluster password—Must be from 1 to 31 alphanumeric characters in length
and can include dollar signs ($) and underscores(_).
2.4 OpenVMS Cluster Information You Need 47
2.5 Dismounting the Target System Disk Elsewhere in the Cluster
Before installing OpenVMS on a target drive in an OpenVMS Cluster, make sure the target system
disk is not mounted elsewhere in the cluster. The target system disk must be dismounted
clusterwide (except on the system from which the installation is being performed) and must
remain so during the installation. For instructions on dismounting cluster disks, see Section 5.5.2.3
(page 91).
2.6 Beginning the Installation
After you have completed all the tasks in this chapter, go to Chapter 3 (page 49) to begin the
installation.
48 Preparing to Install in an OpenVMS Cluster Environment
3 Installing the OpenVMS Operating System
This chapter explains how to install the OpenVMS I64 Version 8.3-1H1 operating system. It
includes sample output similar to what you might see during an installation and explains how
to respond to the prompts.
If you purchased a system with the operating system preinstalled, then most of the information
in this chapter does not apply. The first time you power up your preinstalled system, you are
prompted to enter only the information necessary to customize your installation. See the
documentation provided with your system.
This chapter includes the procedures for booting the OpenVMS operating system kit. Information
about setting up and booting Itanium-based systems is located in Appendix A (page 149)If you
are installing OpenVMS for the first time, see this appendix..
NOTE: Before you install the OpenVMS operating system, ensure that the correct version of
firmware is running in your computer. For I64 system firmware, see Section 1.3.4 (page 29).
This chapter is organized into sections and steps that describe the major tasks for installing
OpenVMS, in the order in which these tasks must be performed. Section 3.1 (page 49) includes
a checklist that you can use to make sure you perform all the installation tasks described in this
chapter.
3.1 Installation Tasks
Use the checklist in Table 3-1 to ensure that you perform all necessary installation tasks.
Table 3-1 Installation Checklist
SectionTask
Section 3.2 (page 49)Boot the OpenVMS operating system media.□
Section 3.3 (page 52)Install the OpenVMS operating system onto a system disk.□
Section 3.4 (page 72)Boot the OpenVMS system disk.□
Section 3.5 (page 74)Join the OpenVMS Cluster (optional).□
Section 3.6 (page 75)Run AUTOGEN.□
□
should occur automatically).
Section 3.7 (page 75)Reboot theoperating system after AUTOGEN completes (this
Section 3.8 (page 76)Log in to the SYSTEM account.□
Chapter 7 (page 113)Perform postinstallation tasks, as necessary.□
3.2 Booting the OpenVMS Operating System Media
The OpenVMS Version 8.3-1H1 operating system includes procedures and tools (such as the
PCSI utility) that enable you to install the operating system easily. These tools are available once
you boot the system properly.
3.1 Installation Tasks 49
3.2.1 Booting the OpenVMS I64 OE DVD
You can boot the OpenVMS I64 OE DVD in any of the following ways. This section gives detailed
instructions on booting from the local DVD drive. Detailed instructions on the other methods
are available in the appendixes, as noted in the corresponding sections to follow.
• From your local DVD drive (Section 3.2.1.1 (page 50))
• From a virtual DVD drive served over the network by the InfoServer utility (Section 3.2.1.2
(page 51))
• From an image on a PC or Windows server in the network accessed through the HP SIM
interface (Section 3.2.1.3 (page 51))
• From an image on a PC or Windows server in the network using virtual media (vMedia)
through a browser connected to your Integrity server iLO 2 MP port (Section C.2 (page 232))
The latter two options can be used for entry-class Integrity servers that support such means (note
that you can use these options when a local DVD drive is not available on your Integrity server).
For more information about booting operations, see Section A.6 (page 172).
Before you can boot your OpenVMS DVD, make sure your console is configured correctly. You
can use a VGA graphics device, serial device,or network interface for the console. For information
about configuring your system console, see Section A.2 (page 152).
NOTE: When using a VGA console and installing from vMedia or a USB DVD drive with the
keyboard plugged into a USB hub, the keyboard might not be operational. If so, simply unplug
the hub and plug it back in.
HP recommends that you load and use the most current system firmware. For more information
about system firmware, see Section 1.3.4 (page 29) and the HP OpenVMS Version 8.3-1H1 for
Integrity Servers New Features and Release Notes. For information about other required and optional
tasks to be performed before or after booting the system, see Appendix A (page 149).
CAUTION: To boot your OpenVMS I64 operating system on a cell-based server (Superdome
servers, or midrange servers such as rx8620 and rx7620), note the following:
• The ACPI configuration must be set correctly. For more information, see Section A.5.1
(page 165).
• The nPartition on which OpenVMS I64 is booted must have all memory configured as
interleaved memory (memory that can be mapped across more than one cell). For more
information about cell memory and general notes on nPartition booting, see Section A.6.1
(page 173) and see your hardware documentation.
3.2.1.1 Booting from the Local Drive
Boot the OpenVMS I64 OE DVD from a local DVD drive by performing the steps included in
this section. To boot the DVD on a cell-based server, a DVD device must be accessible by the
nPartition on which OpenVMS is being installed.
1. Make sure your Integrity server is powered on. If your system has an attached external
device, make sure it is turned on and operational.
2. Insert the DVD into the drive.
3. Cycle power.
50 Installing the OpenVMS Operating System
4. From the main EFI boot menu (for cell-based servers, this must be the EFI boot menu for
the nPartition on which OpenVMS is to be booted), select the appropriate item from the
boot options list. Note that the EFI boot menu is timed; press any key to stop the countdown
timer.
For some systems, the boot option to select is the Internal Bootable DVD option. If that option
is not listed in your EFI boot menu, move to the Boot From a File menu and select the
Removable Media Boot option, if present.
Alternatively (and this method is recommended for cell-based servers), boot the DVD drive
from the EFI Shellprompt by entering the command shown in the following example, where
fsn: corresponds to the Integrity server DVD drive (such as fs0:). Note that if you have
navigated to a particular file system, the EFI Shell prompt reflects that file system; for
example, if the current file system is fs0:, the EFI Shell prompt is fs0:>.
Shell> fsn:\efi\boot\bootia64.efi
To determine which device is the bootable DVD drive, examine the list of mapped devices
and look for an fs device listing that includes the letters “CDROM”, as in the following line.
In this line, fsn is the file system associated with the drive, which is usually fs0: (instead of
"fsn", you might see something similar to "V8.3-1H1"; instead of Ata, you might see Scsi,
depending on the server model):
fsn : Acpi(HWP0002,400)/Pci(4|1)/Ata(Primary,Master)/CDROM(Entry0)
You can use the following command to display the mapping of various EFI device names
to OpenVMS device names, where fsn is the device you want to check (such as fs0:):
Shell> fsn:\efi\vms\vms_show dev -fs
On most Integrity servers, the DVD drive is DQA0: (IDE) or DNA0: (USB). On systems that
include a SCSI bus, such as the Superdome server, the DVD drive is DKA0:. For more
information about the vms_show command, see the HP OpenVMS System Management
Utilities Reference Manual.
NOTE: By default, certain versions of EFI might interpret the Delete (or Backspace) key
differently than do OpenVMS Alpha systems or Microsoft Windows computers. In such
cases, press Ctrl/H to delete the last character entered. For more information, see Section A.1.3
(page 152).
When the DVD boots properly, the OpenVMS operating system banner is displayed, followed
by the operating system menu. You can now install your OpenVMS I64 operating system onto
the target disk; see Section 3.3 (page 52). If the methods documented in this section do not succeed
in booting the DVD, see Section A.6.2.1 (page 175).
NOTE: When booting OpenVMS from the installation DVD for the first time on any OpenVMS
I64 system with a SAN storage device, you might experience a delay in EFI initialization because
the entire SAN is scanned. Depending on the size of the SAN, this delay might range from several
seconds to several minutes.
3.2.1.2 Booting Over the Network Using the InfoServer utility
To use the InfoServer utility to boot from the network, certain configuration steps are required
initially (one time only); see Appendix B (page 189). The instructions on booting over the network
from a virtual DVD are also included in Appendix B (page 189).
3.2.1.3 Booting Using HP SIM Provisioning
To use HP SIM provisioning to boot an image of the OpenVMS OE DVD, certain configuration
steps are required initially (one time only). For these steps and the booting instructions, see
Appendix C (page 203).
3.2 Booting the OpenVMS Operating System Media 51
3.2.1.4 Booting Using vMedia
To use vMedia to boot an image of the OpenVMS OE DVD, certain configuration steps are
required initially (one time only); see Section C.1.4 (page 207). For instructions on booting with
vMedia, see Section C.2 (page 232).
3.3 Installing the OpenVMS Operating System onto a System Disk
After booting the operating system media, you can create an operating system disk by using
option 1 of the menu provided by the operating system media. The procedure for installing an
OpenVMS I64 system is similar to that for installing OpenVMS Alpha operating systems.
Exceptions are summarized in Section 3.3.1 (page 52) and are noted in the installation instructions
in Section 3.3.3 (page 53).
3.3.1 Differences Between OpenVMS I64 and Alpha Installations
If you have not installed an OpenVMS I64 system before and are familiar with OpenVMS Alpha
installations, the main differences between installations of these two systems onto a system disk
include the following:
• Output from the installation procedure is nearly identical for both Alpha and I64 except, of
course, the operating system names as well as names of products included with the
installation. For example, the OpenVMS I64 windowing and networking product names are
all displayed as HP I64VMS product-name, such as HP I64VMS KERBEROS, while
OpenVMS Alpha product names are displayed in any of three different ways, depending
on the product and version:
— HP product-name, such as HP AXPVMS KERBEROS
— DEC product-name, such as DEC AXPVMS DWMOTIF
— CPQ product-name, such as CPQ AXPVMS CDSA
• The default target system disk and volume labels are unique for each system.
• The OpenVMS I64 procedure does not ask whether your system will be an instance in an
OpenVMS Galaxy; OpenVMS I64 does not support OpenVMS Galaxy.
• The OpenVMS Alpha operating system includes several components that are not included
with the OpenVMS I64, such as C Object Libraries and software support for translating
images.
• When installing OpenVMS I64 onto the system disk the first time, you are advised to set up
the system with a boot option for the system disk (and to set it as the default boot device);
you can allow the installation procedure to assist you in setting up and validating a boot
entry. Whereas on Alpha systems you can configure boot devices only by shutting down
the system and entering commands at the console, on I64 systems you can configure boot
devices either before you shut down the system (using the installation procedure or, once
OpenVMS is running, using the OpenVMS I64 Boot Manager utility) or after you shut down
the system (using EFI Utilities for OpenVMS or EFI itself).
3.3.2 Responding to Prompts During the Installation
At different points during the installation, you must respond to prompts that ask you to supply
specific information. This manual and the help text available during the installation procedure
tell you how to obtain most of this information and how to make decisions when responding to
specific prompts.
To repeat an explanation provided by the installation procedure, type a question mark (?) at the
prompt. To change or correct a response made to an earlier question, enter the caret (^) character
as many times as needed. Note that entering this character might take you back more than one
question. To return to the main menu, press Ctrl/Y, which aborts the installation.
HP recommends that you review the following summary before you begin the installation so
that you understand beforehand the types of information you need to provide.
52 Installing the OpenVMS Operating System
During the installation, the procedure prompts you for the following information:
• The names of the source drive, target drive, and LAN device (if booting is served by an
InfoServer).
• Whether you want to select the INITIALIZE or PRESERVE option (as described in
Section 1.4.1 (page 33)).
• A volume label for the target disk (if you choose not to use the default volume label).
• A password for the SYSTEM account.
• Whether you want to form or join an OpenVMS Cluster system and, if so, what kind (as
described in Section 2.4 (page 47)).
• DECnet node name and address (or values for the system parameters, SCSNODE and
SCSSYSTEMID).
NOTE: If you install the DECnet-Plus for OpenVMS software, but you want to use addresses
compatible with DECnet Phase IV software, you still need to provide this information. These
settings identify your system by name and number in a DECnet or cluster environment.
Note that if you supply a DECnet Phase IV address, the procedure automatically calculates
the SCSSYSTEMID value. If necessary, consult the network or system manager to obtain
this information.
• Information listed on Product Authorization Keys (PAKs) for your OpenVMS licenses. To
register your licenses, you must enter the information listed on the PAK for each license.
You may register your licenses after installing OpenVMS.
• Optional operating system components that you want to install. You can install all
components (by default), or you can select specific components from this list:
— DECwindows Motif for OpenVMS (a graphical user interface)
If you install this product, you must also include the DECwindows Server Support
component. If you are not installing DECwindows as part of the OpenVMS installation
now, but you plan to install it later, install the DECwindows Server Support component
now.
— OpenVMS Management Station
If you need to create a kit to install the PC component of the OpenVMS Management
Station software, then you must include the OpenVMS Management Station Software
PC files component.
— TCP/IP Services for OpenVMS
— Either DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS (but not both)
If you install either DECnet implementation, you must also include the Support for
DECnet component. If you are not installing DECnet-Plus or DECnet Phase IV now,
but you plan to install one of them later, you should install the Support for the
DECnet-Plus or DECnet Phase IV component now. (The same support component
applies to both implementations of DECnet.)
For a list of component options included with the OpenVMS operating system, see
Example 3-1 (page 68).
3.3.3 Installing OpenVMS Using Option 1 of the Operating System Menu
After booting the OpenVMS operating system media, install the OpenVMS operating system by
following these steps:
3.3 Installing the OpenVMS Operating System onto a System Disk 53
1. Select Option 1 on the Menu: When you boot the OpenVMS operating system CD or DVD
(as instructed in Section 3.2 (page 49)), the initial HP copyright message and other messages
are displayed, followed by the operating system main menu that is shown in the following
example. Choose option 1 to install the operating system, as shown. Note that after the initial
copyright message, a few minutes might pass before the OpenVMS operating system menu
appears.
.
.
Installing required known files...
Configuring devices...
****************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
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
The OpenVMS operating system kit might contain patch kits. If it does, information similar
to the following is displayed:
The following PATCH kits are present on the OpenVMS I64
distribution media.
----------------------------------- ----------- --------- PRODUCT KIT TYPE KIT FORMAT
----------------------------------- ----------- --------- DEC I64VMS TCPIP_ECO V5.n-nnn Patch Compressed
----------------------------------- ----------- ----------
1 item found
Please consult the OpenVMS I64 Upgrade and Installation Manual,
the Release Notes, and the Cover Letter to determine if any or
all of these patches may be required for your system.
If you have not already done so, determine whether you need to install any patches.
The initial display from the procedure also includes information about how to respond to
prompts (as described in Section 3.3.2 (page 52)):
***********************************************************
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return>key. Type:
54 Installing the OpenVMS Operating System
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
2. Create the System Disk: The procedure allows you to begin creating the system disk. First
it displays the following information, followed by the prompt asking whether you want to
initialize or preserve the disk:
There are two choices for Installation/Upgrade:
INITIALIZE - Removes all software and data files that were
previously on the target disk and installs OpenVMS I64.
PRESERVE -- Installs or upgrades OpenVMS I64 on the target disk
and retains all other contents of the target disk.
* NOTE: You cannot use preserve to install OpenVMS I64 on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE] INITIALIZE
Respond to the INITIALIZE or PRESERVE prompt as follows:
THEN ...IF ...
Your disk is new
You want to remove all files from an existing system disk
You want to retain OpenVMS files on an existing disk
Type INITIALIZE and press Enter.
Type INITIALIZE and press Enter.
Press Enter to accept the default (PRESERVE);
go to Chapter 6 (page 95).
NOTE: You cannot install OpenVMS ona disk where another operating system is installed.
For example, you cannot take a UNIX disk, select the PRESERVE option, and then install
OpenVMS on the disk. The UNIX disk is not structured in the formatthat OpenVMS requires.
During initialization of an OpenVMS I64 target system disk, the installation process creates
a diagnostic partition, visible only at the console prompt. For more information about this
partition and the options you can take, see Appendix I (page 269).
3. Specify the System Disk (Target Disk): The procedure next asks you for the name of the
target disk. If you do not know the name of the disk, enter a question mark (?). The procedure
displays a list of devices on your system. Select the appropriate disk and respond to the
prompt. For example:
You must enter the device name for the target disk on which
OpenVMS I64 will be installed.
Enter device name for target disk: (? for choices) DKB400
If this is the first installation on this system, no default device is indicated, as in this example.
A default device name is listed if this is not the first installation (for example, [DKB400] or,
for a Fibre Channel disk device, [$1$DGA567]).
If you select a device that is not available or that cannot be used for some other reason, the
procedure displays information indicating why the device cannot be used. For example, if
you enter MKA500, a tape device, a message similar to the following is displayed:
MKA500 is not a disk device
3.3 Installing the OpenVMS Operating System onto a System Disk 55
4. Specify the Volume Label: If you select a device that can be used, the procedure then informs
you of the volume label currently assignedto this device and asks whether you want to keep
that label. If you choose not to keep that label, you are prompted for a new label, as shown
in the following example. The OpenVMS operating system uses the volume label to identify
and reference the disk. Make sure the label you use is unique; problems occur if the same
label is used by different disk volumes.
DKB400: is now labeled V82_nnn.
Do you want to keep this label? (Yes/No) [Yes] NO
Enter volume label for target system disk: [I64SYS] I640831
You can keep the label already assigned to the disk, accept the default label assigned by the
system (for I64 systems, I64SYS), or specify a different volume label (with a limit of 12
characters that can include A to Z, 0 through 9, the dollar sign ($), hyphen (-), and underscore
(_) characters).
NOTE: OpenVMS requires that the volume labels for all disks on your system or OpenVMS
Cluster have unique labels. If a disk having the same label as the system disk is mounted,
various OpenVMS components do not function as intended or a node might crash during
boot.
5. Specify On-Disk Structure Level: After you enter the volume label for the target system
disk, when you selected INITIALIZE, you are askedwhether youwant to initializethe target
system disk with On-Disk Structure Level 2 (ODS-2) or Level 5 (ODS-5).
The target system disk can be initialized with On-Disk Structure
Level 2 (ODS-2) or Level 5 (ODS-5). (? for more information)
OpenVMS I64 systems include WBEM Services for OpenVMS; the WBEM data
repository requires an ODS-5 disk. If you choose to initialize the
target system disk with ODS-5 the repository can be on the system
disk; otherwise you will need to provide an additional ODS-5 disk.
(? for more information.
Do you want to initialize with ODS-2 or ODS-5? (2/5/?)
For details about ODS-2 and ODS-5 file systems, see the HP OpenVMS System Manager's
Manual, Volume 1: Essentials. A brief summary follows.
NOTE: HP recommends that your system disk be initialized in ODS-5 format, unless you
plan to use software that requires ODS-2.
Note also that although WBEM Services for OpenVMS can be installed on an ODS-2 disk,
the WBEM Services for OpenVMS data repository requires an ODS-5 disk. A system disk
in ODS-5 format can store everything; if you choose to have your disk in ODS-2 format, the
procedure asks you to provide an ODS-5 disk for the data repository.
• ODS-2
ODS-2 allows for compatibilitywith OpenVMSVAX and Alpha systemsthat useODS-2
disks (as well as OpenVMS I64 systems using ODS-2 disks). Choose ODS-2 if you do
not need the new features of ODS-5 disks, including the support of applications ported
from other operating systems (such as UNIX, Linux, and MS Windows).
• ODS-5
— ODS-5 supports file names that are longer, have a wider range of legal characters,
and allow for mixed-case file names. This feature permits use of file names similar
to those in a Microsoft Windows or UNIX® environment.
— ODS-5 supports hard links to files, access dates, and files whose names differ only
by case.
56 Installing the OpenVMS Operating System
— ODS-5 volumes cannot be mounted on any version of OpenVMS prior to Version
7.2.
— Systems running OpenVMS VAX Version 7.2 and higher can mount ODS-5 volumes,
but cannot create or access files having extended names. (Lowercase file names are
seen in uppercase on OpenVMS VAX systems.)
Select ODS-2 or ODS-5 by entering 2 or 5 at the prompt.
6. Enable Hard Links (ODS-5 Only): If you selected ODS-5, the procedure asks whether you
want to enable hard links (if you selected ODS-2, skip to the next step). When you install
OpenVMS I64, the procedure advises you that WBEM Services for OpenVMS does not
require hard links, as shown in the following example. Enter YES or NO to indicate your
choice.
Hard links can be enabled on ODS-5 disks. WBEM Services for OpenVMS
does not require hard links. (? for more information)
Do you want to enable hard links? (Yes/No/?) YES
Both ODS-2 and ODS-5 support aliases, which are additional names for a file or directory.
Only ODS-5 supports hard links. One of the main differences with hard links enabled is the
way the DCL DELETE command works. With hard links enabled, if you enter the DELETE
command to delete a file that has one or more aliases associated with it, the command only
deletes the alias by which the file is being accessed. The actual file continues to exist and is
accessible by any remaining alias. The file is deleted only when the last remaining alias is
deleted. Without hard links enabled, the DELETE command deletes both the alias by which
the file is being accessed and the file itself. Any other aliases remain but the file is no longer
accessible because it is no longer present. Thus, the remaining aliases are unusable. If enabling
hard links has any drawbacks, they are minor and probably of concern only in rare
circumstances. For example, if disk quotas are in effect, though owners of a file can delete
any links to a file in a directory they can access, hard links in other users’ directories might
cause a file to be retained, and the file size continues to be charged against that owner’s disk
quota.
In general, be aware that enabling hard links does change the file system’s behavior and
that applications and management practices should respond accordingly (instead of being
alias-specific, for example).
For more information about hard links, see the HP OpenVMS System Manager's Manual,
Volume 1: Essentials.
7. Confirm Target System Disk Choices: The procedure displays your target system disk
choices and asks you to confirm that they are correct. In the following example, the choices
made were to initialize the disk with ODS-5 and with hard links. The volume label is
I640831H1.
You have chosen to install OpenVMS I64 on a new disk.
The target system disk, DKB400:, will be initialized
with structure level 5 (ODS-5).
Hard links WILL be enabled.
It will be labeled I640831H1.
Any data currently on the target system disk will be lost.
Is this OK? (Yes/No) YES
Initializing and mounting target....
%EFI-I-VOLINIT, FAT volume DIAGNOSTICS has been initialized
Creating page and swap files....
8. Configure and Validate Boot Options : On OpenVMS I64 installations, the procedure next
asks whether you want to create or validate boot options.
3.3 Installing the OpenVMS Operating System onto a System Disk 57
Boot options in the EFI Boot Manager boot option menu can provide a
convenient way to boot your system. The installation procedure can
automatically create a new boot option (if none exists) or validate
existing boot options.
Do you want to create or validate boot options? (Yes/No) [Yes] YES
If your newly installed system disk will normally be booted on this system and this device,
and if you want the installation procedure to assist you in setting up or validating boot
options on the EFI console in the EFI Boot Manager menu, answer YES. The installation
procedure creates and validates a new boot option if one does not exist, or validates existing
boot options, just before the installation completes (see step 21).
When you answer YES and no boot option exists, the procedure allows you to set OpenVMS
boot flags (VMS_FLAGS), as shown in the following example. Enter the OpenVMS flags
(for example, 0,1), or press Enter to set no flags (the default). If a boot option exists, you can
change boot flags after the installation completes (for information about changing boot flags,
see Section A.5.2 (page 165)).
You can set VMS_FLAGS or accept the default, 0,0.
Enter the value for VMS_FLAGS: (n.n) [0,0]
If you do not want the installation procedure to assist you in setting up or validating boot
options on the EFI console, answer NO.
HP recommends that you allow the installation procedure to assist you in setting up and
validating boot options.
NOTE: If your newly installed system disk is a Fibre Channel device, HP recommends
that you add it as a boot option in the EFI boot menu. If you do not allow the installation
procedure to add the device to the boot menu, you can add it by using the OpenVMS I64
Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) after the installation
completes. (To add Fibre Channel devices to the EFI boot menu, use the OpenVMS I64 Boot
Manager utility instead of EFI.)
HP recommends using the OpenVMS I64 Boot Manager utility to add shadowed system
disks in a multiple-member shadow set to the EFI boot device list and dump device list. Be
sure to add all members to both lists.
For information about the OpenVMS I64 Boot Manager utility, see Section A.5.2 (page 165).
For more information about configuring and booting Fibre Channel devices, see Appendix D
(page 241).
9. Specify SYSTEM Account Information (Initialized Disks Only): If you are initializing the
target disk, you are prompted for SYSTEM account information. Before you respond to the
prompt asking you to enter a password for the SYSTEM account, note the following:
• Passwords must be at least 8 characters in length (but must not exceed 31 characters).
Valid characters for the password include A through Z, 0 through 9, the dollar sign ($),
and underscore (_). Passwords must contain at least one alphabetic character (A through
Z). The system converts all characters to uppercase, so the case of characters you enter
does not matter.
• Press Enter after you enter the password. (The password does not display as you type
it.)
• After you enter the password, the procedure checks to make sure it meets the
requirements for a valid password.
• Reenter the password for verification.
The following is a sample display:
You must enter a password for the SYSTEM account.
58 Installing the OpenVMS Operating System
The password must be a minimum of 8 characters in length, and
may not exceed 31 characters. It will be checked and verified.
The system will not accept passwords that can be guessed easily.
The password will not be displayed as you enter it.
Password for SYSTEM account:
Re-enter SYSTEM password for verification:
If you reenter the password incorrectly or if the procedure determines that the password is
too easy for another user to guess, the procedure displays an error message and allows you
to specify a valid password.
10. Declare OpenVMS Cluster Membership: The procedure now asks whether your system
will be part of an OpenVMS Cluster. The display is similar to the following:
Will this system be a member of an OpenVMS Cluster? (Yes/No)
You should answer YES if the system will be a member of an OpenVMS Cluster. Answering
YES to this question causes SYS$MANAGER:CLUSTER_CONFIG.COM to run automatically
when your newly installed system is first booted. The CLUSTER_CONFIG procedure asks
a series of questions about the cluster. Your response to this question determines how the
VAXCLUSTER system parameter is set. (The VAXCLUSTER system parameter is set for
OpenVMS I64 systems as well as Alpha and VAX systems; it is not specific to OpenVMS
VAX systems.) For more information, see the Guidelines for OpenVMS Cluster Configurations
manual.
If you answer YES to the cluster question, the display is similar to the following:
When your new system is first booted you will be required to answer
additional questions in order to configure the OpenVMS Cluster.
If you answer NO to the cluster question, the system can still be a member of an OpenVMS
Cluster. However, in this case you must explicitly configure the node into the cluster after
the installation is completed. For more information, see Section 3.5 (page 74).
For more information about cluster configuration, see the HP OpenVMS Cluster Systems
manual.
11. Set SCSNODE System Parameter: The procedure now asks you to specify a value for the
first of two system parameters, the SCSNODE parameter. (Step 13 describes the output and
prompts for the second system parameter, SCSSYSTEMID.) SCSNODE is a name that can
be from one to six letters or numbers; it must include at least one letter. If this system is part
of an OpenVMS Cluster, SCSNODE must be unique within the cluster. If you are using
DECnet Phase IV for OpenVMS or DECnet-Plus for OpenVMS with DECnet Phase IV
addresses, then SCSNODE must be the same as your DECnet node name.
The following is an example of the display and a valid response:
For your system to operate properly, you must set two parameters:
SCSNODE and SCSSYSTEMID.
SCSNODE can be from 1 to 6 letters or numbers. It must contain at
least one letter.
If you plan to use DECnet, SCSNODE must be the DECnet Phase IV
node name, or the DECnet-Plus (Phase V) node synonym.
If you have multiple OpenVMS systems, the SCSNODE on each system
must be unique.
Enter SCSNODE: I64CSI
12. Declare Use of DECnet; Setting SCSSYSTEMID System Parameter: The next prompt asks
whether you plan to use DECnet. It also informs you that the SCSYSYSTEMID system
3.3 Installing the OpenVMS Operating System onto a System Disk 59
parameter is based on the DECnet Phase IV address. SCSSYSTEMID must also be unique
within an OpenVMS Cluster.
If you plan to use DECnet, SCSSYSTEMID must be set based on the
DECnet Phase IV address.
Do you plan to use DECnet (Yes/No) [YES]: YES
If you answer YES, the information about the DECnet Phase IV addresses is displayed along
with a prompt for a DECnet Phase IV address. Enter a valid DECnet Phase IV address, as
in the following example:
DECnet Phase IV addresses are in the format
DECnet_area_number.DECnet_node_number
DECnet_area_number is a number between 1 and 63.
DECnet_node_number is a number between 1 and 1023.
If you plan to use DECnet WITHOUT Phase IV compatible addresses,
enter 0.0.
Enter DECnet (Phase IV) Address [1.1]: 63.180
A display such as the following informs you of the value assigned to SCSSYSTEMID:
SCSSYSTEMID will be set to 64692.
This was calculated as follows:
(DECnet_area_number * 1024) + DECnet_node_number
If you are not using DECnet, or if you enter 0.0 as the DECnet Phase IV address, you are
prompted to enter a SCSSSYSTEMID in the range of 1 to 65535. If this is a standalone system,
the default of 65534 is acceptable. However, if this system is part of an OpenVMS Cluster,
you must enter a SCSSYSTEMID that is unique within the cluster. The following is a sample
display:
The system cannot calculate SCSSYSTEMID from an address that is not
compatible with DECnet Phase-IV.
You will have to choose a value for SCSSYSTEMID.
If you plan to use LAT software, you may have to add /NODECNET to any
CREATE LINK commands in SYS$MANAGER:LATSYSTARTUP.COM.
Please choose a SCSSYSTEMID between 1 and 65535. If you have multiple
OpenVMS systems, the SCSSYSTEMID on each system must be unique.
Enter SCSYSTEMID [65535]: 12345
60 Installing the OpenVMS Operating System
13. Set Local Time Zone: Now the procedure asks you to configure the local time zone. For
local time zone support to work correctly, the installation procedure must set the time zone
that accurately describes the location you want to be your default time zone. Usually, this
is the time zone in which your system is running. In addition, the procedure asks you to set
the OpenVMS time differential factor (TDF).
The procedure displays the main time zone menu. You can select the time zone in either of
two ways:
• Select the number in the main time zone menu that best represents the time zonedesired.
(If multiple time zones exist for the selection you make, you must select the exact time
zone from another menu.)
• Use a search option that allows you to bypass the time zone menu and search by name
(partial or full).
If you select one of the numbers in the time zone menu, the corresponding time zone is
selected. At any prompt, you can enter a question mark (?) for help information.
NOTE: An asterisk (*) next to a number indicates that more than one time zone exists for
that selection. If you select such a number, an additional menu displays choices that allow
you to select the appropriate time zone. For example, if you choose the United States (US)
time zone from the main time zone menu, a second menu displays the specific time zones
within the United States.
The following example shows how you would select the Eastern time zone for the United
States by using the menu number:
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu
0* GMT
1* AFRICA 17) EST 33) IRAN 49) PORTUGAL
2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC
3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT
4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC
5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK
6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE
7* AUSTRALIA 23) GB 39) MET 55) TURKEY
8* BRAZIL 24) GMT-0 40* MEXICO 56) UCT
9* CANADA 25) GMT 41* MIDEAST 57) UNIVERSAL
10) CET 26) GMT0 42) MST 58* US
11* CHILE 27) GMTPLUS0 43) MST7MDT 59) UTC
12) CST6CDT 28) GREENWICH 44) NAVAJO 60) W-SU
13) CUBA 29) HONGKONG 45) NZ-CHAT 61) WET
14) EET 30) HST 46) NZ 62) ZULU
15) EGYPT 31) ICELAND 47* PACIFIC
16) EIRE 32* INDIAN 48) POLAND
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 58
US Time Zone Menu "*" indicates a menu
0* RETURN TO MAIN TIME ZONE MENU
1) ALASKA 5) EAST-INDIANA 9) MICHIGAN 13) SAMOA
2) ALEUTIAN 6) EASTERN 10) MOUNTAIN
3) ARIZONA 7) HAWAII 11) PACIFIC-NEW
4) CENTRAL 8) INDIANA-STARKE 12) PACIFIC
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 6
You selected US /EASTERN as your time zone.
Is this correct? (Yes/No) [YES]:
To use the search option instead of menu numbers to select the time zone, enter an equals
sign (=) at the menu prompt instead of a number. You can enter one or more words or partial
3.3 Installing the OpenVMS Operating System onto a System Disk 61
words immediately after the equals string, or you can enter the equals sign alone, in which
case the procedure prompts you for the words or partial words of the time zone you want
to select. After you enter that information, the procedure displays all matching time zones,
and you can then select the appropriate one.
The following example shows how you would select the Eastern time zone for the United
States by using the search option:
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu
0* GMT
1* AFRICA 17) EST 33) IRAN 49) PORTUGAL
2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC
3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT
4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC
5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK
6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE
7* AUSTRALIA 23) GB 39) MET 55) TURKEY
8* BRAZIL 24) GMT-0 40* MEXICO 56) UCT
9* CANADA 25) GMT 41* MIDEAST 57) UNIVERSAL
10) CET 26) GMT0 42) MST 58* US
11* CHILE 27) GMTPLUS0 43) MST7MDT 59) UTC
12) CST6CDT 28) GREENWICH 44) NAVAJO 60) W-SU
13) CUBA 29) HONGKONG 45) NZ-CHAT 61) WET
14) EET 30) HST 46) NZ 62) ZULU
15) EGYPT 31) ICELAND 47* PACIFIC
16) EIRE 32* INDIAN 48) POLAND
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: =EAST
Search for Time Zone by Full or Partial Name
"*" indicates a menu
1) BRAZIL / EAST
2) CANADA / EAST-SASKATCHEWAN
3) CANADA / EASTERN
4) CHILE / EASTERISLAND
5) MIDEAST / RIYADH87
6) MIDEAST / RIYADH88
7) MIDEAST / RIYADH89
8) PACIFIC / EASTER
9) US / EAST-INDIANA
10) US / EASTERN
Press "Return" to redisplay this menu,
enter "=" to search for a new zone,
enter "0" to return to the Main Time Zone Menu, enter "?" for help, or
Select the number above that best represents the desired time zone: 10
You selected US / EASTERN as your time zone.
Is this correct? (Yes/No) [YES]:
The procedure then prompts you for the TDF.
For more information about local time zone support, see the HP OpenVMS System Manager's
Manual, Volume 1: Essentials.
14. Set Time Differential Factor (TDF): The procedure now provides information about and
prompts you to enter the time differential factor (TDF). The TDF is the difference between
your system time and Coordinated Universal Time(UTC), which is an international standard
(similar to Greenwich Mean Time) for measuring time of day. The procedure supplies a
default for TDF, which is generally the correct response. If the time zone you selected supports
daylight saving time, the procedure asks you whether daylight saving time is currently in
effect. The following example shows TDF information and prompts displayed by the
62 Installing the OpenVMS Operating System
procedure:
Configuring the Time Differential Factor (TDF)
Default Time Differential Factor for standard time is -5:00.
Default Time Differential Factor for daylight saving time is -4:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most respects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
This time zone supports daylight saving time.
Is this time zone currently on daylight saving time? (Yes/No): YES
Enter the Time Differential Factor [-4:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00
Is this correct? [Y]:
For more information about TDF support, see the HP OpenVMS System Manager's Manual,
Volume 1: Essentials. Once OpenVMS has been installed and booted from the system disk,
you can determine whether your system is set for daylight saving time by using the following
DCL command to display the translation for the daylight saving time logical:
$ SHOW LOGICAL *TIMEZONE*
"SYS$TIMEZONE_DAYLIGHT_SAVING"="1"
.
.
.
15. Register Licenses (Optional at this time): After setting the TDF, the procedure asks whether
you want to register any Product Authorization Keys (PAKs), as in the following display:
If you have Product Authorization Keys (PAKs) to register,
you can register them now.
Do you want to register any Product Authorization Keys? (Yes/No) [Yes]
You can register the PAKs now by responding YES to the prompt, or later by responding
NO. You register licenses later by following the directions in Section 7.3 (page 116).
To register your licenses now, be sure you have the following before proceeding:
• A copy of the Product Authorization Key (PAK) for each license that you are registering.
• The HP OpenVMS License Management Utility Manual, which contains complete, detailed
information about the licensing procedure.
For the OpenVMSI64 operatingsystem, a single Operating Environment (OE) license grants
the right to use all the components bundled in the purchased OE. Each OE is offered with
Per Core Licenses (PCLs). One PCL is required for each active processor core in the system
or hard partition. (If additional processor cores are added later to the system or hard partition,
each requires an additional PCL.) The License Management utility supports these OpenVMS
I64 licensingpractices. The OpenVMS UnlimitedUser License is included with the Foundation
Operating Environment (FOE) and, therefore, is included with the other OEs available. For
more information, see the HP Operating Environments for OpenVMS for Integrity Servers
Software Product Description (SPD 82.34.xx).
For more information about licensing terms and policies, contact your local HP sales office,
or see the HP software licensing information at the following location:
3.3 Installing the OpenVMS Operating System onto a System Disk 63
http://h18000.www1.hp.com/products/software/info/terms/swl_sld.html
When you answer YES to the prompt to register your licenses now, the installation procedure
launches the SYS$UPDATE:VMSLICENSE.COM procedure, which displays the following
options menu:
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]
Select the REGISTER option and enter each license key until you have successfully registered
all required PAKs. After you register all your licenses, exit the License Management procedure
by entering 99 at the prompt.
16. Install Windowing, Networking, and Related Products: The procedure now asks whether
you want to install the optional DECwindows GUI (DECwindows Motif for OpenVMS) and
networking software (DECnet and TCP/IP) included with OpenVMS. The software that you
choose to install (including the required software) is installed along with the OpenVMS
operating system. You can change the default values for these products later in the installation
procedure.
NOTE: The following display shows what you might see during an OpenVMS I64
installation. Some of the products listed are supported on OpenVMS I64 systems only.
The following products are part of the OpenVMS installation;
they will be installed along with the OpenVMS operating sytem:
o Availability Manager (base) for OpenVMS I64
o CDSA for OpenVMS I64
o KERBEROS for OpenVMS I64
o SSL for OpenVMS I64
o Performance Data Collector (base) for OpenVMS I64
o WBEM Services for OpenVMS (WBEMCIM)
o WBEM Providers for OpenVMS (WBEMPROVIDERS)
You can also install the following optional products along with the
OpenVMS operating system:
o DECwindows Motif for OpenVMS I64
o DECnet-Plus for OpenVMS I64
o DECnet Phase IV for OpenVMS I64
o HP TCP/IP Services for OpenVMS
If you want to change your selections, you can do so later in the
installation by answering "NO" to the following question:
"Do you want the defaults for all options?"
Do you want to install DECwindows Motif for OpenVMS I64 V1.6? (Yes/No) [Yes] Y
If you want to install the OpenVMS graphical user interface and you have the hardware
that supports it and the license to use it, answer YES; otherwise, answer NO.
64 Installing the OpenVMS Operating System
You may install any of the optional software products separately after the OpenVMS
installation completes.
NOTE: Beginning with OpenVMS Version 8.3, DECwindows client files are made available
through the DWMOTIF_SUPPORT kit. (Prior to Version 8.3, the client files were included
directly with the OpenVMS operating system kit.) The OpenVMS installation procedure
installs this kit automatically. The DWMOTIF_SUPPORT kit name is listed during the
installation.
The OpenVMS installation menu offers the choice to install DECnet-Plus for OpenVMS or
DECnet Phase IV for OpenVMS networking software. You cannot have both installed on
your system at the same time. You can also chooseto install neither DECnet product; however,
certain products that depend on DECnet might be adversely affected.
If you have installed DECnet-Plus and TCP/IP on your system, you can run DECnet
applications over your TCP/IP network. For more information about DECnet over TCP/IP,
see the DECnet-Plus for OpenVMS Network Management manual.
The software products display is similar to the following:
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. HP strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is also provided as an option.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCP/IP.
Do you want to install DECnet-Plus for OpenVMS I64 V8.3-1H1? (Yes/No) [YES]
If you answer NO to the DECnet-Plus prompt, you are prompted to install DECnet Phase
IV:
Do you want to install DECnet Phase IV for OpenVMS I64 V8.3-1H1? (Yes/No) [Yes]
Finally, you are asked whether you want to install TCP/IP Services for OpenVMS:
Do you want to install HP TCP/IP Services for OpenVMS V5.6?
(Yes/No) [Yes] Y
3.3 Installing the OpenVMS Operating System onto a System Disk 65
NOTE: For support of Instant Capacity (iCAP) and Pay per use (PPU) functionality
(supported on cell-based Integrity servers), and for support of such products as gWLM and
HP SIM, you must install TCP/IP Services for OpenVMS. When you use HP SIM to provision
OpenVMS on an Integrity server, TCP/IP Services for OpenVMS is installed automatically.
17. Choose Descriptive Help Text (Optional): After you respond to the prompt for TCP/IP
Services for OpenVMS, the final stages of the installation proceed. First, the procedure asks
whether you want detailed descriptions:
The installation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing ?.
Do you always want detailed descriptions? (Yes/No) [No]
If you answer YES, the procedure displays additional explanatory text with each prompt.
As of Version 8.3, most PCSI kits included on the OpenVMS distribution media are signed
using Secure Delivery. Each target file includes an associated digital signature file that is
used for Secure Delivery validation. This validation involves authenticating the originator
(HP, in this case) and verifying the contents of the target file. (The digital signature file is
also referred to as a manifest; it has the same file name as the target file plus _ESW appended
to the file extension, as in filename.PCSI$COMPRESSED_ESW.) When you install OpenVMS
I64 Version 8.3-1H1 from the distribution media, the procedure validates any signed PCSI
kits that are being installed. For each kit successfully validated, you see a message similar
to the following:
Performing product kit validation ...
%PCSI-I-VALPASSED, validation of
DKB400:[KITS.CDSA]HP-I64VMS-CDSA-Vnnnn-nnn-n.PCSI$COMPRESSED;1 succeeded
.
.
.
Any signed PCSI kits that you install susbsequently (including any signed kits on the
distribution media) are validated. In addition, the DCL command PRODUCT SHOW
HISTORY displays the validation status of installed products.
18. Select Product Component Options (Accept All Defaults or Select Individually): The
procedure displays a message such as the following, indicating that it is ready to install the
operating system:
The following product has been selected:
HP I64VMS OPENVMS V8.3-1H1 Platform (product suite)
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and
for any products that need to be installed to satisfy software dependency
requirements.
HP I64VMS OPENVMS V8.3-1H1: OPENVMS and related products Platform
COPYRIGHT 1976, 13-JUN-2007
Hewlett-Packard Development Company, L.P.
Do you want the defaults for all options? [YES]
When selecting options, note the following:
• If you want all the default values, press Enter.
If you want to select options individually, answer NO. The procedure then prompts
you for each option and suboption shown in Example 3-1 (page 68).
66 Installing the OpenVMS Operating System
• Review the list of options and compare them with the requirements for your system.
If you are selecting components individually, be sure that you include all components
necessary to supportthe needsof yourusers. Note also that certain components depend
on the installation of other components.
• If you are not sure whether you want certain options, request help by entering a question
mark (?) at the prompt for that option.
• After you select all the options you want, you canview your selections and make changes
(if necessary).
• OpenVMS Management Station software is automatically installed on your OpenVMS
system disk when you accept all the default values. If you do not accept the default
values, you must select the OpenVMS Management Station component (server and
client files) if you plan to use this product. After the installation is complete, you can
prepare your OpenVMS system and your PC to run OpenVMS Management Station
by following the procedures described in Appendix G (page 257).
• If you decide after the installation to changewhich OpenVMS operating system options
you want installed on your system, you must reconfigure the installation as described
in Section 1.4.1.2 (page 34) and Section 7.11 (page 136).
• After you boot the new system disk and log in, you can obtain information about
individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($).
NOTE: Unless you have specific reasons to do otherwise, HP recommends that you accept
the defaults and install all OpenVMS options. OpenVMS and layered products have various
dependencies on many of these options. Even if you think you do not need certain options,
some OpenVMS or layered product operations might not work correctly if other OpenVMS
options are not installed.
Note also that, for OpenVMS I64 installations, the availability of certain options depends
on the OE you have purchased. For example, OpenVMS Management Station is available
with the Enterprise Operating Environment (EOE) and the Mission Critical Operating
Environment (MCOE).
If you answer YES to accept the defaults for all options, the procedure displays a message
similar to the following, the contents of which depend on the products you chose to install.
If you answer NO, the procedure prompts you for each option and suboption.
Availability Manager (base) for OpenVMS I64
CDSA for OpenVMS I64
KERBEROS for OpenVMS I64
SSL for OpenVMS I64
Performance Data Collector for OpenVMS
WBEM Services for OpenVMS (WBEMCIM)
HP I64VMS WBEMCIM V2.61-A070728: HP WBEM Services for OpenVMS
Copying WBEM Services for OpenVMS Release Notes to SYS$HELP
....There are post-installation tasks you must complete.
WBEM Providers for OpenVMS (WBEMPROVIDERS)
HP I64VMS DWMOTIF V1.6: DECwindows Motif
If a Language Variant is installed, refer to the Installation Guide.
19. Finish Installation onto System Disk – Review and Confirm Options: When you have
answered all the prompts and selected the options you want installed, the procedure displays
information about the products you have selected. The procedure allows you to review your
3.3 Installing the OpenVMS Operating System onto a System Disk 67
selections and make changes if necessary, then installs the product, provides informational
messages, and returns you to the original menu.
First, you are asked whether you want to review the options:
Do you want to review the options? [NO]
If you answer YES, the procedure displays all the selected options and suboptions, similar
to Example 3-1. If you answer NO, the installation continues as described with the sample
script (beginning with "Execution phase starting ...") that follows.
Example 3-1 Component Options and Suboptions
DECdtm Distributed Transaction Manager
Support for DECnet-Plus or DECnet for OpenVMS
Programming Support
Debugger Utility
Image Dump Utility
Macro libraries
Macro-32 Migration Compiler
TLB intermediary form of STARLET
C Header Files
VMS text libraries of Ada declarations
RMS Journaling Recovery Utility
System Programming Support
Delta Debugger
System Dump Analyzer Utility
Miscellaneous Symbol Table Files
OpenVMS Management Station Software -- PC files
Utilities
Phone Utility
XPG4 Internationalization Utilities
World Wide PostScript Printing Subsystem
Bliss Require Files
Example Files
Message Facility Files (HELP/MESSAGE)
Translated Image Support
UETP Files
DECwindows Server Support
Delete any obsolete OpenVMS files
Delete files archived by OpenVMS remedial kits
The component options listed in Example 3-1 are included within the OpenVMS Version
8.3-1H1 operating system. Depending on the products you chose to install with the operating
system, additional components are included as well. After the procedure displays all selected
options and suboptions, you are prompted as follows:
Are you satisfied with these options? [YES]
If you answer NO to this question, you are allowed to selectively configure options and
suboptions, even if you did not do so previously. When you finish, you are asked again
whether you are satisfied with the options you selected. When you answer YES to indicate
you are satisfied with the selections, the installation begins installing OpenVMS onto the
target disk. The following is a sample display:
Execution phase starting ...
The following products will be installed to destinations:
HP I64VMS AVAIL_MAN_BASE V8.3-1H1 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS CDSA V2.3-306 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS DECNET_PLUS V8.3-1H1 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS DWMOTIF V1.6 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS KERBEROS V3.1-152 DISK$I64SYS:[VMS$COMMON.]
68 Installing the OpenVMS Operating System
HP I64VMS OPENVMS V8.3-1H1 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS SSL V1.3-284 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS TCPIP V5.6 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS TDC_RT V2.3-1 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS VMS V8.3-1H1 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS WBEMCIM V2.61-A070728 DISK$I64SYS:[VMS$COMMON.]
HP I64VMS WBEMPROVIDERS V1.5-31 DISK$I64SYS:[VMS$COMMON.]
Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% HP TCP/IP Services for OpenVMS.
%
Portion done: 100%
Depending on the options you selected, certain messages such as the preceding TCP/IP
message might be displayed at this point.
20. Final Installation Confirmation and Information Messages:The installation continues,
displaying the products that have been installed and relevant information. The version
numbers in this example do not necessarily reflect the version numbers of the products
actually shipped with OpenVMS Version 8.3-1H1.
The following products have been installed:
HP I64VMS AVAIL_MAN_BASE V8.3-1H1 Layered Product
HP I64VMS CDSA V2.3-306 Layered Product
HP I64VMS DECNET_PLUS V8.3-1H1 Layered Product
HP I64VMS DWMOTIF V1.6 Layered Product
HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 Layered Product
HP I64VMS KERBEROS V3.1-152 Layered Product
HP I64VMS OPENVMS V8.3-1H1 Platform (product suite)
HP I64VMS SSL V1.3-284 Layered Product
HP I64VMS TCPIP V5.6 Layered Product
HP I64VMS TDC_RT V2.3-1 Layered Product
HP I64VMS VMS V8.3-1H1 Operating System
HP I64VMS WBEMCIM V2.61-A070728 Layered Product
HP I64VMS WBEMPROVIDERS V1.5-31 Layered Product
HP I64VMS OPENVMS V8.3-1H1: OPENVMS and related products Platform
HP I64VMS KERBEROS V3.1-152
Configure and set up Kerberos
If Kerberos will be run on this system, but has not been
used previously, you need to perform the following steps.
o Run the Kerberos configuration procedure:
@SYS$STARTUP:KRB$CONFIGURE.COM
o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:KRB$STARTUP
o Add the following line to SYS$MANAGER:SYLOGIN.COM:
$ @SYS$MANAGER:KRB$SYMBOLS
Press RETURN to continue:
HP I64VMS SSL V1.3-284: SSL for OpenVMS I64 V1.3 (Based on OpenSSL 0.9.7e)
There are post-installation tasks that you must complete
after upgrading from previous SSL versions
including verifying startup command procedures and logical names.
3.3 Installing the OpenVMS Operating System onto a System Disk 69
Refer to SYS$HELP:SSL013.RELEASE_NOTES for more information.
HP I64VMS TDC_RT V2.3-1: The Performance Data Collector (base) for OpenVMS
Users of this product require the following privileges:
(CMKRNL,LOG_IO,WORLD,PHY_IO,SYSPRV,SYSLCK)
Users of this product require the following process resource limits:
WSQUO minimum 7000
A read-me file is available in SYS$COMMON:[TDC]TDC_README.TXT
Release notes are available in SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT
HP I64VMS TCPIP V5.6 : HP TCP/IP Services for OpenVMS.
Check the release notes for current status of the product.
21. Installation Creates and Validates Boot Options : At this point in an OpenVMS I64
installation, the procedure creates and validates boot options if you chose to have the
procedure do so (see step 8).
• If you answered NO in step 8, the following message is displayed:
If there is an existing boot option that was used to boot this
system disk, you may be able to use it. Otherwise, you will have
to use the EFI Shell the first time that you boot the newly
installed system. After booting, use the OpenVMS I64 Boot Manager
to create a Boot Option. To do this log in to a privileged
account and execute this command:
$ @SYS$MANAGER:BOOT_OPTIONS
The procedure then informs you that the installation is complete and prompts you to
press Return (Enter) to continue, at which point it returns you to the OpenVMS main
menu. You can select option 8 (“Execute DCL commands and procedures”) on the
OpenVMS main menu and enter the command at the DCL triple dollar sign prompt
($$$) to start the OpenVMS I64 Boot Manager utility.
• If you answered YES in step 8, the installation procedure determines whether a boot
entry already exists for the system disk (in this example, DKB400:):
— If an entry is found, a message similar to the following is displayed:
The EFI Boot Manager menu includes the following boot option(s)
for DKB400:
EFI Boot Options list: Timeout = 0 secs.
----------------------------------------------------------------------
01. DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) "OpenVMS on DKB400: PKA0.1"
---------------------------------------------------------------------1 entries found.
In this example, one boot option is found. If multiple entries are found and if they
are all SCSI devices, the procedure displays the following message and then notifies
you that the installation is complete:
Please use the OpenVMS I64 Boot Manager to ensure that you
have a valid boot option for the system you have just installed.
When one entry is found, or when multiple Fibre Channel entries are found, the
procedure validates the boot options, as in the following example, in which the
found entry fails to boot and is then fixed and validated:
70 Installing the OpenVMS Operating System
Validate EFI Boot Options list: Timeout = 0 secs.
------------------------------------------------------------------ 1 OpenVMS on DKB400: PKA0.1
DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0)
efi$bcfg: Option Failed. Fixing Boot Entry automatically.
efi$bcfg: Entry 1 Boot0001 removed.
efi$bcfg: DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) (Boot0001) Option
successfully added
----------------------------------------------------------------------1 entries validated.
— If no existing entry is found, a boot option is created and the procedure displays
the validation text, as in the following example:
efi$bcfg: DKB400: (Boot0003) Option successfully added
The Boot Option is called OpenVMS on DKB400:;
it is the first entry in the Boot Options menu, and is
configured (by default) to boot from SYS0.
VMS_FLAGS are set to -fl 0,30000
22. Installation Completes and Returns to OpenVMS Menu: The installation procedure is
now complete. The procedure displays information about the special startup procedure that
runs when the newly installed system is first booted. It then prompts you to press Return
(Enter) to continue. After you do so, you are returned to the OpenVMS operating system
menu. The following is a sample display:
The installation is now complete.
When the newly installed system is first booted, a special
startup procedure will be run. This procedure will:
o Configure the system for standalone or OpenVMS Cluster operation.
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
Process I64VMS_INSTALL logged out at 25-SEP-2007 14:45:49.54
Press Return to continue...
****************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
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/?)
3.3 Installing the OpenVMS Operating System onto a System Disk 71
23. Shut Down the System: Unless you want to perform other operations prior to booting the
new systemdisk, choose the shutdown option (9) on theOpenVMS main menu to shut down
the operating system, as shown in the following example. If you want to install layered
products that have not been installed yet, HP recommends doing so during the
postinstallation phase, as described in Section 7.14 (page 141).
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 9
Shutting down the system
SYSTEM SHUTDOWN COMPLETE
After you complete the installation and shut down the system, you can boot your new
operating system disk,as explained in Section 3.4.1 (page 72).If youare installing OpenVMS
I64, make sure you remove the DVD from the drive before booting the system disk.
3.4 Booting the New OpenVMS System Disk
After you have successfully installed the OpenVMS operating system, the next step is to make
the new system disk the default boot device. For OpenVMS I64 systems, this step may already
have been done (see step 21 of the installation procedure in Section 3.3.3 (page 53)), in which
case you can boot the OpenVMS I64 system disk by performing the steps in Section 3.4.1 (page 72).
3.4.1 Booting the OpenVMS I64 System Disk
The following steps explain how to boot your new OpenVMS I64 system disk. For more
information about this and special booting operations, see Section A.6 (page 172). You can also
use vMedia to boot an OpenVMS system disk; see Section C.2 (page 232).
NOTE: Make sure you remove the DVD from the DVD/CD drive before booting the system
disk.
The actions you take to boot the system disk depend on whether you have configured your
system with a boot option for your system disk:
• If you have configured your system with a boot option for your system disk, your system
disk is displayed as a boot option in the EFI Boot Manager menu. Select your system disk
and press Enter. If your system disk is the first option in the EFI Boot Manager menu, it
might boot automatically after the 10-second countdown.
• If you have not configured your system with a boot option for your disk, follow these
steps:
1. Press Enter or any other key. (You might see text that instructs you to "hit any key to
cold reboot.") The machine displays several boot-related messages and then displays
the EFI Boot Manager menu.
2. Go to the EFI Shell prompt by selecting the EFI Shell [Built-in] option from the EFI Boot
Manager menu. (This might be selected automatically if you do not make a selection
before the EFI countdown completes.) A display similar to the following appears. An
explanation of the two types of devices shown (blk and fs) follows the example.
72 Installing the OpenVMS Operating System
Loading.: EFI Shell [Built-in]
EFI Shell version 1.10 [14.61]
Device mapping table
fs0 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig8FCF6F11-...
fs1 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part4,Sig8FCF6F10-...)
blk0 : Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,Master)
blk1 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)
blk2 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig8FCF6F11-...)
blk3 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part2,Sig8FCF6F10-...)
blk4 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,Sig8FCF6F11-...)
blk5 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part4,Sig8FCF6F10-...)
blk6 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part5,Sig8FCF6F10-...)
Shell>
fs
blk
fs The fs devices are file-structured logical partitions on physical disks that
are included with your Integrity server system. One or more fs device
exists for each volume with a bootable partition or diagnostic partition.
Generally, fs0: corresponds to the target disk on which you installed
OpenVMS I64 (unless the DVD was not removed, in which case fs1:
corresponds to the target disk). For example, if the target disk is DKA0,
then fs0: most likely corresponds to the target disk. On the other hand,
if the target disk is a DKA100 or DKB200 or similar, the corresponding
EFI device depends on what partitions are configured on the target disk.
blk The blk devices are block devices. Multiple blk devices exist for each
volume that has a bootable partition or diagnostic partition. These devices
may include the DVD device as well as the diagnostic partitions on
OpenVMS system disks. Diagnostic partitions are intended and reserved
for use by HP Services. (For more information about this partition, see
Appendix I (page 269).)
3. To boot the OpenVMS I64 system disk, enter the following command at the EFI Shell
prompt, where fsn: is the device associated with the system disk (probably fs0:):
Shell> fsn:\efi\vms\vms_loader.efi
The OpenVMS I64 operating system now starts booting. A display similar to the
following appears, followed by the prompt for user name and password:
HP OpenVMS Industry Standard 64 Operating System, Version 8.3-1H1
(c) Copyright 1976-2006 Hewlett-Packard Development Company, L.P.
Note that HP Integrity servers maintain a system event log (SEL) within system console
storage, and OpenVMS I64 automatically transfers the contents of the SEL into the
OpenVMS error log. On certain machines, during a successful boot operation while
using a console, you might see a message indicating that the Baseboard Management
Controller (BMC) SEL is full. You can safely continue when the BMC SEL is full by
following the prompts; OpenVMS processes the contents of the SEL.
3.4.2 Next Steps
When you boot OpenVMS from a new system disk, a special startup procedure runs that does
the following:
• Gives you the opportunity to configure the system for standalone or OpenVMS Cluster
operation (see Section 3.5 (page 74)).
• Runs AUTOGEN to evaluate your hardware configuration, estimate typical workloads, and
set system parameters (see Section 3.6 (page 75)).
• Reboots your system with the new parameters (see Section 3.7 (page 75)).
After the system is rebooted with the new parameters, you can log into your SYSTEM account,
as explained in Section 3.8 (page 76). On Integrity servers, if you did not allow the OpenVMS
installation procedure to create a boot option for your system disk, you can set up such an option
3.4 Booting the New OpenVMS System Disk 73
now, as explainedin Section A.5 (page 164). Appendix A (page 149) includes additional information
regarding setting up and booting HP Integrity servers.
3.5 Joining an OpenVMS Cluster
If you answered YES to the question about joining an OpenVMS Cluster, the system now asks
a series of questions about your configuration (such as CI, DSSI, SCSI, local area, or mixed
interconnect). If you answered NO to this question, the system immediately runs AUTOGEN,
as described in Section 3.6 (page 75). If you answered NO, you can still set up or join an OpenVMS
Cluster after the installation is completed by manually running the cluster configuration utility.
You can do this by entering the following command:
$ @SYS$MANAGER:CLUSTER_CONFIG_LAN
For more information about cluster configuration, see the HP OpenVMS Cluster Systems manual
or the Guidelines for OpenVMS Cluster Configurations manual.
Table 3-2 lists the OpenVMS Cluster prompts and suggested responses. These prompts appear
if you answered YES to the question about joining an OpenVMS Cluster or if you manually run
SYS$MANAGER:CLUSTER_CONFIG_LAN.COM. Note that, depending onyour responses and
the particular cluster configuration, some prompts are not displayed.
Table 3-2 Prompts for OpenVMS Cluster Configurations
How to RespondQuestion
Enter Y.Will this node be a cluster
member (Y/N)?
What is the node's DECnet node
name?
What is the node's DECnet node
address?
number:
Enter this cluster's password:
for verification:
Will MYNODE be a disk server
(Y/N)?
Enter a value for MYNODE’s
ALLOCLASS parameter.
Does this cluster contain a
quorum disk (Y/N)?
1 Cluster group number and password are required by any cluster nodes that use the local area network. In a cluster
1
that uses mixed interconnects, if any of the interconnects require the cluster number and password, then you must
set the cluster number and password for all nodes.
Enter the DECnet node name (for example, MYNODE). The DECnet node name
can be from one to six alphanumeric characters in length and cannot include
dollar signs ($) or underscores (_). This is the name you specified in step 12 of
the installation procedure.
Enter the DECnet node address; for example,2.2. This is the addressyou specified
in step 13 of the installation procedure.
Enter a number in the range of 1 to 4095 or 61440 to 65535.Enter this cluster's group
1
Enter the cluster password. The password must be from 1 to 31 alphanumeric
characters in length and can include dollar signs ($) and underscores (_).
Reenter the password.Reenter this cluster's password
Enter Y if you want local disks to be served to the cluster (mandatory for local
area and mixed-interconnect configurations). See the HP OpenVMS Cluster Systems
manual for information about served cluster disks.
In an OpenVMS Cluster environment, the allocation class value cannot be zero
if volume shadowing will be used on this system. The ALLOCLASS value must
be a number from 1 to 255.
HP recommendsthat youthoroughly review the chapter on cluster storage devices
in the HP OpenVMS Cluster Systems manual. This manual also includes the rules
for specifying allocation class values.
For SCSI, local area, and mixed-interconnect configurations, enter Y or N,
depending on your configuration. If you enter Y, the system asks for the name
of the quorum disk. Enter the device name of the quorum disk. For information
about quorum disks, see the HP OpenVMS Cluster Systems manual.
74 Installing the OpenVMS Operating System
3.6 Running AUTOGEN
At this point, the system automatically runs AUTOGEN to evaluate your hardware configuration
and estimate typical workloads. AUTOGEN then sets system parameters, the sizes of page, swap,
and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and your
system reboots, the installation procedure is complete.
The installation procedure displays messages similar to the following:
AUTOGEN will now be run to compute the new system parameters. The system
will then shut down and reboot, and the installation or upgrade will be
complete.
After rebooting you can continue with such system management tasks as:
Decompressing the System Libraries (not necessary on OpenVMS I64)
Configuring networking software (TCP/IP Services, DECnet, other)
Using SYS$MANAGER:CLUSTER_CONFIG.COM to create an OpenVMS Cluster
Creating FIELD, SYSTEST, and SYSTEST_CLIG accounts if needed
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages that
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-SYSGEN, parameters modified
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
NOTE: After booting and running AUTOGEN, several messages are displayed at DECwindows
startup. For information about these messages and how to avoid them, see the HP DECwindows
Motif for OpenVMS Release Notes.
3.7 Rebooting After AUTOGEN
After AUTOGEN finishes, the system automatically shuts down and displays messages similar
to the following:
The system will automatically reboot after the shutdown and the
installation will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
on node I64CSI
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
.
3.6 Running AUTOGEN 75
.
.
After shutdown of an OpenVMS I64 system, it reboots automatically only if you have set the
system disk boot option accordingly; otherwise, you must boot the system manually, as described
in Section 3.4.1 (page 72).
When the system reboots, it displays informational messages and accounting information
indicating that your OpenVMS operating system has finished booting and is now ready for use.
For example:
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 25-SEP-2007 14:51:23.47
Accounting information:
Buffered I/O count: 2177 Peak working set size: 6848
Direct I/O count: 1358 Peak page file size: 179552
Page faults: 1805 Mounted volumes: 0
Charged CPU time: 0 00:00:13.37 Elapsed time: 0 00:01:06.20
3.8 Logging In to the SYSTEM Account
The following two sections explain how to log in to the SYSTEM account from a character-cell
terminal and from a workstation.
3.8.1 Logging In from a Character-Cell Terminal
Log in from a character-cell terminal by entering the user name SYSTEM followed by the
password. The display is similar to the following:
OpenVMS I64 Operating System, Version 8.3-1H1
Username: SYSTEM
Password:
.
.
.
OpenVMS I64 Operating System, Version 8.3-1H1
If you forget your password for an OpenVMS I64 SYSTEM account, follow the instructions in
Section A.6.12 (page 181) to perform an emergency startup.
3.8.2 Logging In from a Workstation
If you installed the DECwindows Motif for OpenVMS software on your workstation, do the
following after the login window is displayed on your screen:
1. Enter the user name SYSTEM, press Tab, and then enter the password.
2. Press Enter or click OK with your mouse.
3. At this point, you can create a DECterm session or initiate other management functions. For
information about creating a DECterm session, see the DECwindows Motif for OpenVMS
Applications Guide.
3.9 Postinstallation Tasks
After you have successfully installed the OpenVMS operating system and logged in to the
SYSTEM account, you must perform certain postinstallation tasks before you can use the system.
For complete information, see Chapter 7 (page 113).
76 Installing the OpenVMS Operating System
4 Before Upgrading the OpenVMS Operating System
This chapter describes which tasks you should perform prior to beginning an upgrade. Section 4.1
(page 77) includes a checklist that you can use to make sure you perform all the tasks described
in this chapter.
4.1 Preupgrade Tasks
Use the checklist in Table 4-1 to ensure that you perform all necessary tasks prior to upgrading
your system.
Table 4-1 Preupgrade Checklist
SectionTask
Section 4.2 (page 77)Review relevant documentation.□
□
• Upgrade paths to Version 8.3-1H1
• Update license requirements
• Components you choose not to install
• Upgrade issues after the system disk directory structure has
been changed
• Licenses and possible reinstallation requirements for layered
products
□
environment.
Section 4.3 (page 78)Review notes, cautions, and restrictions about the following:
Section 4.4 (page 79)Save files that you do not want deleted by the upgrade procedure.□
Section 4.5 (page 79)Prepare the system disk.□
Section 4.6 (page 83)Ensure that you have a recent FEEDBACK.DAT file.□
Section 4.7 (page 84)Perform required actions before upgrading in a volume shadowing
Section 4.8 (page 85)Back up the current system disk.□
Section 4.9 (page 86)Shut down the system.□
4.2 Documentation to Review Before Upgrading Your System
In addition to reviewing the information in this chapter, you might need to refer to the following
sources of information as well.
OpenVMS Version 8.3-1H1 Documents
• The Cover Letter for HP OpenVMS Version 8.3-1H1 for Integrity Servers
• The Software Product Descriptions included with your distribution kit
• HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes
OpenVMS Version 8.3 Documents
Information in the following documents remains valid exceptwhere superseded by theOpenVMS
Version 8.3-1H1 documents listed previously.
• The Software Product Descriptions included with your distribution kit
• HP OpenVMS Version 8.3 Release Notes
• HP OpenVMS Version 8.3 New Features and Documentation Overview
4.1 Preupgrade Tasks 77
Earlier OpenVMS Version Documents
Information in the following documents remains valid exceptwhere superseded by theOpenVMS
documents listed previously.
• HP OpenVMS Cluster Systems
• Guidelines for OpenVMS Cluster Configurations
• HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems
(specifically, the chapter entitled “Managing System Parameters”), for information about
using AUTOGEN, modifying the system parameters file (MODPARAMS.DAT), and related
operations
• HP OpenVMS System Management Utilities Reference Manual, for information about using
system management utilities such as SYSMAN and ANALYZE/DISK_STRUCTURE
• HP OpenVMS Guide to System Security, for information about reestablishing your security
environment after the upgrade
4.3 Notes, Cautions, and Restrictions
This section provides important information that can affect the success of your upgrade. Review
the cautions, restrictions, and notes carefully before you begin the upgrade.
4.3.1 Upgrade Paths
You can upgrade directly to OpenVMS I64 Version 8.3-1H1 from only the following versions of
OpenVMS I64:
• Version 8.3
• Version 8.2-1
4.3.2 Update License Requirements
IMPORTANT: Before upgrading to OpenVMS I64 Version 8.3-1H1, you must have the appropriate
OE license loaded on your system.
HP software licenses grant the right to use the current version of a product or any previous
version of the product at the time of purchase.
NOTE: When you initially purchase the OpenVMS software and license, HP provides a Product
Authorization Key (PAK) that is required to enable the License Management Facility (LMF) to
register the license and to validate and authorize subsequent use of the product. A PAK does
not provide license or new version rights. For more information about licensing and the License
Management Facility, see the HP OpenVMS License Management Utility Manual.
If you need an Update License, please contact your HP Sales representative.
4.3.3 Components You Choose Not to Install
If you choose not to install optional OpenVMS networking software (DECnet or TCP/IP) or the
DECwindows/Motif GUI during the upgrade, the upgrade procedure removes these products
from the system disk. Note that TCP/IP Services for OpenVMS is installed automatically when
OpenVMS is installed by HP SIM provisioning.
78 Before Upgrading the OpenVMS Operating System
NOTE: Unless you have specific reasons to do otherwise, HP recommends that you accept the
defaults and install all OpenVMS options. OpenVMS and layered products have various
dependencies on many of these options. Even if you think you do not need certain options, some
OpenVMS or layered product operations might not work correctly if other OpenVMS options
are not installed.
Note also that, for OpenVMS I64 installations, the availability of certain options depends on the
OE you have purchased. For example, OpenVMS Management Station is available with the
Enterprise Operating Environment (EOE) and the Mission Critical Operating Environment
(MCOE).
4.3.4 Licenses and Layered Products
The upgrade procedure is designed so that you do not need to reinstall most layered products
after the upgrade. However, you might need to reinstall certain layered products because of
product-specific installation procedures.
The upgrade procedure leaves your OpenVMS license and layered product licenses intact. You
do not need to reinstall these licenses after you upgrade.
4.4 Saving Archived Files from Being Deleted by the Upgrade
By default, the upgrade procedure deletes files that were archived as filename.type_OLD by
OpenVMS remedial kits. If you do not want these files deleted, you can rename them before you
perform theupgrade. Alternatively, you can have the upgrade procedure save them by responding
to the prompts, as described in Section 6.4.4 (page 107).
4.5 Preparing the System Disk
The following sections describe how to prepare the system disk for the upgrade. Operations
include the following:
• Checking for appropriate directory structure and preserving your security protections
• Checking the SYSCOMMON directories
• Examining the system disk
• Checking the size of the system disk
• Returning authorization and AGEN$INCLUDE files to the system disk
• Verifying system parameters
4.5.1 Checking the Directory Structure and Preserving Your Security Protections
If you changed the directory structure on your system disk, the upgrade procedure does not
work correctly. Restore your system disk to a standard directory structure before you attempt
an upgrade.
The OpenVMS upgrade procedure provides new files and directories in the directory
[VMS$COMMON...]. If you have any special protections and access control lists (ACLs), you
need to reapply them to reestablish the security environment you currently have. For more
information about creating and maintaining a secure environment, see the HP OpenVMS Guide
to System Security manual.
4.5.2 Checking the SYSCOMMON Directories
For the upgrade to be successful, the SYSCOMMON directoriesin all system roots must be aliases
(or hard links) for the VMS$COMMON directory. To check whether this is the case, enter the
following commandsif you are booted from the system disk that you are upgrading, and compare
the displayed file identifiers to ensure that they are all the same:
4.4 Saving Archived Files from Being Deleted by the Upgrade 79
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[SYS*]SYSCOMMON.DIR
If you did not boot from the system disk that you are upgrading, mount the disk to be upgraded
and specify the actual device name in the command. For example, if the system disk to be
upgraded is mounted on DKA100, you would use commands similar to the following:
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[SYS*]SYSCOMMON.DIR
Output from the first command should list a single file. Output fromthe second command should
list one file for each system root on the disk. Check whether the file ID is the same for all of the
listed files and take action as follows:
• If all the file IDs are the same, continue with the procedure described in the next section.
• If all the file IDs are not the same, this system disk does not have the directory structure that
OpenVMS requires, and the upgrade will not succeed. For assistance on resolving this,
contact your software support representative.
4.5.3 Examining the System Disk
Examine and repair (if necessary) the system disk using the ANALYZE/DISK_STRUCTURE
command. (See the HP OpenVMS System Management Utilities Reference Manual: A-L for more
information about this command.) Use the following procedure:
1. Analyze the system disk for inconsistencies and errors in the file structure by entering the
following command:
$ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE
Ignore the following message:
%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
2. If you find any other errors on the system disk, repair the errors by entering the following
command:
$ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE
Repeat steps 1 and 2 until no errors (other than the one shown in step 1) are returned.
4.5.4 Checking the Size of the System Disk
It is difficult to determine in advance how many blocks of disk space you need for the upgrade.
It depends on how many files you have on the target disk already and on how many components
you select during the upgrade procedure. However, the following information will help:
• The maximum amount of disk space you need is approximately 675,000 blocks, but your
system might use substantially less.
• After you select the components you want installed on the system for the upgrade, the
upgrade procedure calculates whether you have enough disk space, displaying the number
of available blocks and the number required for the upgrade. If the procedure determines
that your disk does not have enough space to perform the upgrade, it displays a message
to alert you and allows you to terminate the upgrade so you can create more disk space and
try the upgrade again.
NOTE: If the files on your system disk are badly fragmented, you might not be able to
complete an upgrade, even when the amount of disk space appears to be sufficient. HP
recommends that you back up and restore the system disk prior to upgrading. Restoring
the system disk from an image backup defragments the disk. For information about backing
up and restoring your system disk, see Appendix E (page 247).
To see how much space you have on the system disk, enter the following command:
$ SHOW DEVICE SYS$SYSDEVICE
80 Before Upgrading the OpenVMS Operating System
4.5.5 Returning Authorization and AGEN$INCLUDE Files to the System Disk
If you place authorization and AGEN$INCLUDE files on disks other than the system disk, the
upgrade procedure will not find these files. This is because the other disks are not mounted
during the upgrade. In addition, the logical names you set up to point to these files are not defined
during the upgrade. The following sections explain how to make these files available to the
upgrade procedure.
4.5.5.1 Authorization Files
OpenVMS allows you to relocate certain system files (mostly authorization files) off the system
disk. You do this by copying the files to another location and then defining logical names as
documented in the file SYS$MANAGER:SYLOGICALS.TEMPLATE. The logical names are
defined in SYS$STARTUP:SYLOGICALS.COM.
When you boot your system from the OpenVMS operating system media, the logical names
pointing to these files are not defined, and the disks where they are located are not mounted.
Because of this, the upgrade cannot access the relocated files, possibly resulting in an incorrect
or incomplete upgrade. The upgrade might finish without error, but the files might not be in
place as expected.
Before upgrading your system, check the definitions of these logical names on your system. (If
a file has not been relocated, the corresponding logical name might not be defined. This is
acceptable.) If any logical name points to a location or file name other than the location and file
name listed in Table 4-2, return the file to the default location and file name. To prevent the
system from referencing the files located off the system disk, either delete the associated logical
name (using the DCL command DEASSIGN/SYSTEM/EXEC), or shut down the operating system
and reboot fromthe operatingsystem media. After the upgrade and before booting the operating
system, you can move these files back to their original locations off the system disk, using the
DCL option (8) from the OpenVMS operating system menu.
NOTE: Some files listed in Table 4-2, such asSYS$SYSTEM:VMS$PASSWORD_HISTORY.DATA
and SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE, might not exist on your system, depending
on certain configuration settings. For information about these files, see the HP OpenVMS Guide
to System Security manual.
Table 4-2 Logical Names for Relocated Authorization Files
Location and File NameLogical Name
SYS$SYSTEM:LAN$NODE_DATABASE.DATLAN$NODE_DATABASE
SYS$SYSTEM:LMF$LICENSE.LDBLMF$LICENSE
SYS$SYSTEM:NETNODE_REMOTE.DATNETNODE_REMOTE
SYS$MANAGER:NETNODE_UPDATE.COMNETNODE_UPDATE
SYS$SYSTEM:NETOBJECT.DATNETOBJECT
SYS$SYSTEM:NETPROXY.DATNETPROXY
SYS$SYSTEM:NET$PROXY.DATNET$PROXY
SYS$SYSTEM:RIGHTSLIST.DATRIGHTSLIST
SYS$SYSTEM:SYSUAF.DATSYSUAF
SYS$SYSTEM:SYSUAFALT.DATSYSUAFALT
SYS$SYSTEM:SYSALF.DATSYSALF
SYS$SYSTEM:VMSMAIL_PROFILE.DATAVMSMAIL_PROFILE
SYS$MANAGER:VMS$AUDIT_SERVER.DATVMS$AUDIT_SERVER
4.5 Preparing the System Disk 81
Table 4-2 Logical Names for Relocated Authorization Files (continued)
4.5.5.2 AGEN$INCLUDE Files
If you use the AGEN$INCLUDE feature in SYS$SYSTEM:MODPARAMS.DAT to include files
containing additional parameter settings, and the files that are being included are not on the
system disk, then do the following before upgrading:
1. Move the files to the system disk.
2. Update the AGEN$INCLUDE entries to reflect the new locations of these files. For these
entries, do not use logical names that you defined in SYS$STARTUP:SYLOGICALS.COM
or elsewhere for your normal startup procedure. When you boot the system from the
OpenVMS operating system media for an upgrade, your normal startup procedure is not
run, and so these logical names are not defined for the upgrade. In addition, when you first
boot the upgraded system, a special startup procedure is used.
After the upgrade is complete, you can move these included files back to their original locations.
If you do so, remember to re-set the AGEN$INCLUDE entries in
SYS$SYSTEM:MODPARAMS.DAT.
Location and File NameLogical Name
SYS$SYSTEM:VMS$OBJECTS.DATVMS$OBJECTS
SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATAVMS$PASSWORD_DICTIONARY
SYS$SYSTEM:VMS$PASSWORD_HISTORY.DATAVMS$PASSWORD_HISTORY
SYS$LIBRARY:VMS$PASSWORD_POLICY.EXEVMS$PASSWORD_POLICY
4.5.6 Verifying System Parameters
Verify (and modify if necessary) system parameters. (For information about verifying and
modifying system parameters, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning,
Monitoring, and Complex Systems .) During an upgrade, AUTOGEN initially generates parameter
values based on parameter defaults. However, during the GETDATA phase, AUTOGEN modifies
parameter values based on entries stored in SYS$SYSTEM:MODPARAMS.DAT. In addition,
AUTOGEN analyzes feedback information stored in the AGEN$FEEDBACK.DAT file and, if
the data is valid, adjusts any related parameter values accordingly. (AUTOGEN considers data
as valid if the system has been up at least for 24 hours and the feedback is no more than 30 days
old.) To ensure that your feedback data is up to date, follow the instructions in Section 4.6
(page 83).
82 Before Upgrading the OpenVMS Operating System
IMPORTANT: Any system parameters that you modified and did not enter in the
SYS$SYSTEM:MODPARAMS.DAT file are lost during the upgrade. To retain these parameters,
enter their names and the values that you have in use for them in
SYS$SYSTEM:MODPARAMS.DAT. When AUTOGEN runs after the upgrade, it uses the values
in SYS$SYSTEM:MODPARAMS.DAT.
For example, if the current value of GBLPAGES is 30000, and you modified GBLPAGES by 128
pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.DAT:
MIN_GBLPAGES=30128 !Increased by 128 by PLM for product z 12/12/04
AUTOGEN compares the computed value of GBLPAGES with this MIN_ value (30128). If the
computed value is less than the specified MIN_ value, AUTOGEN increases the value of
GBLPAGES to the MIN_ value. Each time AUTOGEN runs, it makes the same comparison and
adjusts the value of GBLPAGES, but never below the minimum indicated by MIN_GBLPAGES.
IMPORTANT: If you modify system parameters, note the following:
• In general, you should allow AUTOGEN to 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, useMIN_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 you need to limit a parameter to a known maximum value.
• Enter numeric values as integers, without commas (for example, 10000). Enter alphabetic
characters in lowercase 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 is an example
illustrating 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 using AUTOGEN as recommended, see Section 7.22 (page 144).
If your system was upgraded previously, a new SYS$SYSTEM:MODPARAMS.DAT file was
created then. This file has comments and possibly duplicated entries that were created during
that upgrade. If you upgrade again, SYS$SYSTEM:MODPARAMS.DAT can become unnecessarily
large and potentially confusing. HP recommends that you edit and reorganize
SYS$SYSTEM:MODPARAMS.DAT before you upgrade again.
NOTE: On a cluster system disk, the MODPARAMS.DAT file should exist in
SYS$SYSROOT:[SYSEXE] for each root. You must edit MODPARAMS.DAT as necessary for each
root.
4.6 Ensuring You Have a Recent FEEDBACK.DAT File
Before upgrading your system, HP recommends thatyou have a recent AGEN$FEEDBACK.DAT
file. This file is in SYS$SPECIFIC:[SYSEXE] (that is, in [SYSx.SYSEXE], where x is the root; for
example, SYS0 or SYS1). In OpenVMS Cluster systems, this file should exist in each node’s
4.6 Ensuring You Have a Recent FEEDBACK.DAT File 83
SYS$SPECIFIC directory. When the system (or each system in a cluster) is rebooted after the
upgrade, AUTOGEN runs. If a recent AGEN$FEEDBACK.DAT file is available, it is used. The
data in this file helps AUTOGEN set system parameters for your specific applications and
workload.
NOTE: If you do not have a current AGEN$FEEDBACK.DAT file, AUTOGEN might calculate
system parameters that do not reflect your system's requirements. In that case, multiple cycles
of running AUTOGEN and rebooting might be necessary before all layered products can be
started. In some cases, successful startup can require additional entries in MODPARAMS.DAT.
This should not be necessary if a current AGEN$FEEDBACK.DAT file is available.
If you do not have the AGEN$FEEDBACK.DAT file on your system, HP recommends that you
create a current AGEN$FEEDBACK.DAT file during a time when your system is running under
a typical workload. To ensure the greatest data reliability, the system should be running for more
than 24 hours but less than 30 days. Enter the following command:
$ RUN SYS$SYSTEM:AGEN$FEEDBACK.EXE
This runs very quickly and should not affect the performance of your system while it executes.
You can also specify the SAVE_FEEDBACK option when you execute the
SYS$SYSTEM:SHUTDOWN.COM procedure; however, the data captured might not fully reflect
the typical workload on your system.
IMPORTANT: If you start AUTOGEN without specifying the execution-mode parameter
(FEEDBACK, NOFEEDBACK, or CHECK_FEEDBACK),AUTOGEN usesthe feedbackinformation
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.
4.7 Shadowing Environment
Because you cannot upgrade the operating system on a shadowed system disk (the upgrade will
fail), you need to disable shadowing of the system disk and perform other operations before you
can upgrade the operating system.
There are several methods for creating a nonshadowed target disk. This chapter describes how
to change one of your existing shadowed system disks in a multiple-member shadow set to a
nonshadowed disk that you can use as your target disk for the upgrade.
If you have a larger configuration with disks that you can access physically, you might want to
use a copy of the system disk as your target disk. HP Volume Shadowing for OpenVMS describes
two methods you can use to create this copy (using volume shadowing commands or BACKUP
commands) and how to disable volume shadowing.
84 Before Upgrading the OpenVMS Operating System
4.7.1 Setting the Boot Device
Be sure your system is set to boot by default from the disk you intend to upgrade.
For OpenVMS I64 systems, HP recommends using the OpenVMS I64 Boot Manager utility
(SYS$MANAGER:BOOT_OPTIONS.COM) to addshadowed systemdisks in a multiple-member
shadow set to the EFI boot device list and dump device list. Be sure to add all members to both
lists. For more information about setting boot options and using this utility, see Section A.5.2
(page 165).
4.7.2 Creating a Nonshadowed Target Disk
Perform the steps described in this section tochange one of your existingshadowed system disks
to a nonshadowed disk.
IMPORTANT: If you simply use a MOUNT/OVERRIDE=SHADOW_MEMBERSHIP command
to mount the volume to be upgraded, volume shadowing can overwrite the newly upgraded
disk with information from a prior volume that has not been upgraded.
1. Shut down all systems booted from the shadowed system disk.
2. Perform a conversational (interactive) boot (see Section A.6.8 (page 179)) on the system disk
you have chosen for your target disk.
For OpenVMS I64 systems, enter the following command at the EFI Shell prompt, where
fsn: is the device associated with the system disk (such as fs1:):
Shell> fsn:\efi\vms\vms_loader.efi -flags 0,1
3. At the SYSBOOT> prompt, enter the following command to disable volume shadowing of
the system disk:
SYSBOOT> SET SHADOW_SYS_DISK 0
4. Enter the CONTINUE command to resume the boot procedure. For example:
SYSBOOT> CONTINUE
5. After the boot completes, go to Section 4.9 (page 86).
You now have a nonshadowed system disk that you can use for the upgrade.
4.8 Backing Up the System Disk
HP strongly recommends that you make a backup copy of the system disk and, if your
configuration allows it, upgrade the backup copy. Then, if there are problems, you still have a
working system disk.
NOTE: OpenVMS Engineering has encountered cases where recovery from a failed upgrade
has been difficult, expensive, or impossible because no backup of the preupgrade system disk
was available. Various hardware or software failures or a power failure can make a partially
upgraded system disk unusable. A backup copy might be the only route to recovery. The minimal
time required to make a backup is a very wise investment.
To back up the system disk, follow these steps:
1. Shut down the system (see Section A.7.2 (page 185)).
2. Boot the operating system media, following the instructions in Section A.6 (page 172).
3. Use the menu system to enter the DCL environment (option 8).
4. Mount the system device and the target device on which you will make 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. The
/OVERRIDE qualifier used in this example allows you to mount the system disk without
4.8 Backing Up the System Disk 85
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:
5. To backup 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
6. To back up to a device other than a magnetic tape drive, enter the BACKUP command. For
example, if your system disk is on DKA0: and your target disk is on DKA100:, use the
following command (the colons are required):
$$$ BACKUP /IMAGE /LOG DKA0: DKA100:
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 indicating the discrepancies.
7. Log out from the DCL environment.
8. Shut down the system by selecting option 9 on the menu.
For more complete information about backup operations, including a description of an alternative
method thatdoes not require bootingfrom the operating system media, see Appendix E (page 247).
For more information about the Backup utility, see the HP OpenVMS System Management Utilities
Reference Manual: A-L.
4.9 Finishing Preupgrade Tasks
Continue the preupgrade tasks as follows, depending on whether you are upgrading in a
standalone or OpenVMS Cluster environment:
THEN ...IF ...
You are upgrading a
standalone system
You are upgrading an
OpenVMS Cluster system
1. Review the checklist at the beginning of this chapter to verify that you have
performed the necessary tasks.
2. Log in to the SYSTEM account.
3. Enter the following command:
$ @SYS$SYSTEM:SHUTDOWN
4. When the procedure asks whether an automaticsystem rebootshould be performed,
enter N (NO).
5. Go to Chapter 6 (page 95) to begin the upgrade procedure.
1. Review the checklist at the beginning of this chapter to verify that you have
performed the necessary tasks.
2. Go to Chapter 5 (page 87).
86 Before Upgrading the OpenVMS Operating System
5 Preparing to Upgrade in an OpenVMS Cluster
Environment
This chapter describes how to prepare to upgrade in an OpenVMS Cluster environment. If you
are not upgrading in an OpenVMS Cluster environment, go to Chapter 6 (page 95).
5.1 Preupgrade Tasks for OpenVMS Cluster Environments
NOTE: Be sure you have performed the preupgrade tasks described in Chapter 4 (page 77)
before you upgrade your OpenVMS Cluster system.
Use the checklist in Table 5-1 to ensure that you perform all necessary tasks prior to upgrading
your system in an OpenVMS Cluster environment.
Table 5-1 Preupgrade Checklist for OpenVMS Cluster Environments
SectionTask
□
documentation.
□
migration support in OpenVMS Cluster systems.
□
OpenVMS Cluster, choose one of two options for upgrading.
Perform the preliminary tasks required for the type of upgrade:
□
◦ Concurrent upgrade
◦ Rolling upgrade
5.2 Review OpenVMS Cluster Information
When you upgrade the operating system in an OpenVMS Cluster environment, be sure you
review any relevant OpenVMS Cluster information contained in the following documents.
OpenVMS Version 8.3-1H1 Documents
• The Cover Letter for HP OpenVMS Version 8.3-1H1 for Integrity Servers
• The Software Product Descriptions included with your distribution kit
• HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes
Section 5.2 (page 87)Review relevant OpenVMSoperating systemand OpenVMSCluster
Section 5.3 (page 88)Familiarize yourself with mixed-version, mixed-architecture, and
Section 5.4 (page 89)If you are adding a new OpenVMS computer system to an existing
Section 5.5 (page 89):
◦ Section 5.5.1 (page 89)
◦ Section 5.5.2 (page 90)
Chapter 6 (page 95)Begin the upgrade.□
OpenVMS Version 8.3 Documents
Information in the following documents remains valid exceptwhere superseded by theOpenVMS
documents listed previously.
• HP OpenVMS Version 8.3 Release Notes
• HP OpenVMS Version 8.3 New Features and Documentation Overview
Earlier OpenVMS Documents
Information in the following documents remains valid exceptwhere superseded by theOpenVMS
documents listed previously.
• HP OpenVMS Cluster Systems
• Guidelines for OpenVMS Cluster Configurations
5.1 Preupgrade Tasks for OpenVMS Cluster Environments 87
5.3 Mixed-Version Support in an OpenVMS Cluster Environment
HP provides two levels of support for mixed-version and mixed-architecture OpenVMS Cluster
systems: warranted support and migration support.
Warranted support means that HP has fully qualified two specified versions coexisting in an
OpenVMS Cluster and will address all problems identified by customers using these
configurations.
Migration support means that HP has qualified the versions for use together in configurations
that are migrating in a staged fashion to a newer version of OpenVMS. Problem reports submitted
against these configurations will be answered by HP. However, in exceptional cases, HP may
request that you move to a warranted configuration as part of the solution. Migration support
helps customers move to warranted OpenVMS Cluster pairs.
Warranted cluster support is provided for the combinations shown in Table 5-2.
Table 5-2 Warranted Cluster Support
Warranted in these combinationsOperating system
OpenVMS Alpha Version 8.3
OpenVMS I64 Version 8.3-1H1
OpenVMS Alpha Version 8.3 and OpenVMS I64 Version 8.3-1H1 or 8.3
or
OpenVMS Alpha Version 8.3 and OpenVMS VAX Version 7.3
OpenVMS I64 Version 8.3-1H1 or 8.3 and OpenVMS Alpha Version 8.3
or
OpenVMS I64 Version 8.3-1H1 and OpenVMS I64 Version 8.3
NOTE: Only two architectures are supported in the same OpenVMS Cluster: OpenVMS I64
and OpenVMS Alpha, or OpenVMS Alpha and OpenVMS VAX, but not OpenVMS I64 and
OpenVMS VAX.
System disks are architecture specific and can be shared only by systems of the same architecture.
An Alpha and I64 system, or an Alpha and VAX system, cannot boot from the same system disk.
However, cross-architecture satellite booting is supported between an Alpha and VAX system.
When you configure an OpenVMS Cluster to take advantage of cross-architecture booting, make
sure that at least one system from each architecture is configured with a disk that can be used
for installations and upgrades. For more information, see the Guidelines for OpenVMS Cluster
Configurations and HP OpenVMS Cluster Systems manuals.
Table 5-3 shows the supported migration pairings.
Table 5-3 Supported Migration Pairing
Operating system
OpenVMS I64 Version 8.3-1H1
Supported with either of these
migrating to OpenVMS I64 Version
8.3-1H1
OpenVMS I64 Version 8.3
OpenVMS I64 Version 8.2-1
For information about valid upgrade paths, see Section 4.3.1 (page 78).
For more information, see the OpenVMS Technical Software Support Service website at:
http://www.hp.com/go/openvms/support
In addition, see the following website for the OpenVMS Operating System Support Chart at:
http://www.hp.com/go/openvms/supportchart
88 Preparing to Upgrade in an OpenVMS Cluster Environment
Supported with either of these migrating
to OpenVMS Alpha Version 8.3
OpenVMS Alpha Version 7.3-2
OpenVMS Alpha Version 8.2
Before introducing an OpenVMS Version 8.3-1H1 system into an existing OpenVMS Cluster,
you might need to install certain patch kits (also known as remedial kits) on cluster members
running earlier versions of OpenVMS. In a mixed-architecture cluster, you need to install an
LMF patch on any OpenVMS Version 7.3-2 Alpha members. For a complete list of required patch
kits, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and
the HP OpenVMS Version 8.3 Release Notes.
For information about supporting the Performance Data Collector base software (TDC_RT) in
OpenVMS Clusters, see Section 7.8.10.5 (page 135).
5.4 Adding a New System to an OpenVMS Cluster
To add a new OpenVMS Version 8.3-1H1 I64 system to an existing OpenVMS Cluster
configuration, all existing Alpha nodes in the cluster must be running OpenVMS Alpha Version
8.3, and all existing OpenVMS I64 nodes must be running OpenVMS I64 Version 8.3 or later.
Any node in the cluster that is running an older version of OpenVMS must be upgraded
appropriately before you can add a Version 8.3-1H1 node.
Alternatively, any I64 node that needs to be upgraded can be removed temporarily from the
cluster and added back after it has been upgraded. This allows you to form a supported cluster
immediately, adding nodes back into the cluster as they are upgraded. Note that, depending on
the number of nodes being added, you might need to adjust the EXPECTED_VOTES system
parameter to reflect the number of voting nodes and any quorum disk votes (if a quorum disk
is being used). In addition, for any node being removed from the cluster, you should specify the
REMOVE_NODE option during system shutdown so that the quorum for the remaining nodes
is correctly adjusted.
5.5 Types of Upgrades
Two types of cluster upgrades are available: a concurrent upgrade and a rolling upgrade. The
type of upgrade you use depends on whether you want to maintain the availability of the cluster
during the upgrade and whether you have more than one system disk. Review this chapter and
then perform the preliminary tasks for the upgrade procedure (concurrent or rolling) that best
suit your configuration.
5.5.1 Concurrent Upgrade
This section describes the following:
• How a concurrent upgrade works
• Preparing your system for a concurrent upgrade
5.5.1.1 How a Concurrent Upgrade Works
During a concurrent upgrade, you must shut down the entire cluster and upgrade each system
disk. No one can use the cluster until you upgrade each system disk and reboot each computer.
When thecluster reboots, each computerwill run the upgradedversion of the OpenVMS operating
system.
If all systems in the OpenVMS Cluster environment are booted from one system disk, you must
perform a concurrent upgrade.
5.5.1.2 Preparing Your System for a Concurrent Upgrade
To prepare for a concurrent upgrade, follow these steps:
5.4 Adding a New System to an OpenVMS Cluster 89
1. Log in locally to the SYSTEM account.
If you have more than one system disk, make sure that you have performed the preupgrade
tasks on each system disk that you are upgrading. Make sure the target system disk is not
mounted on any other node in the cluster and remains dismounted during the upgrade. It
should be mounted only on the system that is performing the upgrade. (For information
about dismounting disks, see Section 5.5.2.3 (page 91).) Then go to Chapter 6 (page 95) and
perform an upgrade on each system disk. You do not have to reboot the operating system
media for each upgrade. You only need to choose option 1 on the menu for each upgrade.
2. Shut down all systems by entering the following command on each system (satellite nodes
first, then the boot nodes):
$ @SYS$SYSTEM:SHUTDOWN
3. When the procedure asks whether an automatic system reboot should be performed, enter
N (NO).
4. Choose the CLUSTER_SHUTDOWN option.
5. When the shutdown procedure is finished on all nodes, halt each system by either pressing
Ctrl/P or Halt. For more information about halting your Integrity server, see Section A.7.1
(page 184).
6. If you have only one system disk for your cluster, go to Chapter 6 (page 95) to begin the
upgrade procedure.
After the upgrade is complete, you are instructed to reboot each computer in the OpenVMS
Cluster environment before beginning other postupgrade procedures.
5.5.2 Rolling Upgrade
This section describes the following:
• How a rolling upgrade works
• Notes and restrictions
• Preparing your system for a rolling upgrade
5.5.2.1 How a Rolling Upgrade Works
A rolling upgrade allows you to have a mixed-version cluster. During a rolling upgrade, you
keep some of the computers in the cluster running and available while you upgrade others (you
must have more than one system disk). You upgrade each system disk individually, allowing
old and new versions of the operating system to run together in the same cluster.
5.5.2.2 Notes and Restrictions
The following restrictions apply to rolling upgrades. For additional compatibility issues and
restrictions information, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features
and Release Notes and the HP OpenVMS Version 8.3 Release Notes.
• The system being upgraded does not attempt to access any disk that is being accessed by
one or more of the remaining OpenVMS Cluster systems.
• The remaining OpenVMS Cluster systems do not attempt to access the target disk of the
system being upgraded.
If the target disk being upgraded is locally attached to the system performing the upgrade,
then it is not accessible to the remaining OpenVMS Cluster systems. (The OpenVMS system
booted from the operating system media does not MSCP serve local disks.) HP recommends
that, whenever possible, you perform the upgrade on a local disk or that you perform a
concurrent upgrade.
During the upgrade, be sure that the target disk you select, as well as any disk you access
from the DCL menu option, is either a local disk or one that is not being accessed by any of
90 Preparing to Upgrade in an OpenVMS Cluster Environment
the remaining OpenVMS Cluster members. Make sure the target system disk is not mounted
on any other node in the cluster and remains dismounted during the upgrade. It should be
mounted only on the system that is performing the upgrade. (For information about
dismounting disks, see Section 5.5.2.3 (page 91).)
NOTE: Any attempt toaccess thetarget system disk from the remaining OpenVMS Cluster
members will corrupt the target disk. Even if the target system disk is mounted only by a
remaining cluster member and no file access is performed, the target disk will probably be
corrupted. If a disk is corrupted in this way, the only supported recovery is to restore the
backup copy of the corrupted disk.
• HP recommends that all Alpha computers in a cluster run the same (preferably the latest)
version of the OpenVMS Alpha operating system, and that all Integrity servers run the same
version of the OpenVMS I64 operating system.
• You cannot perform a rolling upgrade if all systems boot from a single system disk. Perform
a concurrent upgrade instead.
• The upgrade procedure affects the queuing system as follows:
— The queuing system is not active on the system you are upgrading; do not attempt to
execute a START/QUEUE/MANAGER command.
— You cannot create a queue database on the operating system CD/DVD (because it is not
writable).
— The queue manager process on other nodes in the cluster can continue to run during
the upgrade if the queue database is not on the disk being upgraded.
5.5.2.3 Preparing Your System for a Rolling Upgrade
To prepare for a rolling upgrade, follow these steps:
1. Log in to any node where the target disk is mounted as a data disk rather than as the system
disk. (That disk must be the one on which you already performed the preupgrade tasks
described in Chapter 4 (page 77).)
2. Check the votes and make adjustments to maintain the proper quorum so the cluster can
continue to operate throughout the upgrade. (HP OpenVMS Cluster Systems describes this
procedure in detail.)
3. Use the DCL command DISMOUNT/CLUSTER to dismount the data disk. (You can also
perform this operation using the SYSMAN utility.)
Note that you can ignore messages from nodes where the specified data disk is being used
as the system disk.
4. Verify that the data disk has been dismounted successfully by entering the following
commands:
$ MCR SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO SHOW DEVICE disk-name
Examine the display to be sure the disk is not mounted on any nodes as a data disk. Noting
the value listed in the Trans Count field can help you make that determination: A value of
less than 50 indicates that the disk is mounted as a data disk rather than as the system disk;
a much larger value (for example, 300) indicates that the disk most likely is the system disk.
5. If the disk is still mounted on any nodes as a data disk, use the SYSMAN utility to dismount
the disk; otherwise, exit the SYSMAN utility.
5.5 Types of Upgrades 91
6. Use the following command to shut down any nodes that boot from the system disk you
are upgrading (shut down satellite nodes first):
$ @SYS$SYSTEM:SHUTDOWN
a. When the procedure asks whether an automatic system reboot should be performed,
enter N (NO).
b. Choose the REMOVE_NODE option.
If a proper quorum is not maintained at any time during the upgrade procedure, the shutdown
procedure hangs the cluster. If the cluster hangs during a shutdown, you can use the Interrupt
Priority C (IPC) facility to adjust quorum from the system consoleof a system that is still a cluster
member.
From anOpenVMS Alpha cluster member, press Ctrl/P. The IPC facility displayshelp information
about IPC commands. Enter the commands at the console:
$ Ctrl/P
>>> D SIRR C
>>> C
Interrupt Priority C
Commands:
C device Cancel Mount Verification
Q Adjust Quorum
CTRL-Z Exit IPC
CTRL-P Prompt for Crash
IPC> Q
IPC> Ctrl/Z
From an OpenVMS I64 cluster member, pressing Ctrl/P puts the system directly into the IPC
facility, which displays help information about IPC commands. To adjust quorum, enter the
commands shown in the following example. Note that if systems are booted with XDELTA,
pressing Ctrl/P brings the OpenVMS I64 system into XDELTA. The IPC facility is not available
in this case.
$ Ctrl/P
Interrupt Priority C
Commands:
C device Cancel Mount Verification
Q Adjust Quorum
CTRL-Z Exit IPC
CTRL-P Prompt for Crash
IPC> Q
IPC> Ctrl/Z
You can also adjust quorum using Availability Manager or DECamds. The method is equivalent
to that used by IPC except you do not have to use the console (this assumes the Data Analyzer
is running on a system outside the OpenVMS Cluster, which is recommended). For more
information, see the “Adjust Quorum” section in the Availability Manager User’s Guide or the
DECamds User’s Guide. The Availability Manager User’s Guide is available at:
http://www.hp.com/products/openvms/availabilitymanager
92 Preparing to Upgrade in an OpenVMS Cluster Environment
After the shutdown procedure is finished on all nodes, go to Chapter 6 (page 95) to begin the
upgrade procedure.
CAUTION: During the upgrade it is very important that the system disk being upgraded is
accessed only by the node on which the upgrade is being performed. If the disk can be accessed
from other nodes in the cluster, for example, through an HSC or HSJ device, you must ensure
that this does not happen. Even if the disk is only mounted and no file access is performed, the
disk can still become corrupted.
Ensure that any users who might mount disks know that they must not access the system disk
being upgraded. Also make sure that any procedures that might mount the disk do not run
during the upgrade. If you have automatic procedures that periodically check and remount disks,
it would be wise to disable them during the upgrade.
5.5 Types of Upgrades 93
94
6 Upgrading the OpenVMS Operating System
This chapter explains how to upgrade the OpenVMS operating system from a local CD or DVD
drive and includes information about reinstalling or reconfiguring your system.
This chapter is organized into sections that describe the major tasks for upgrading OpenVMS,
in the order in which these tasks must be performed. Section 6.1 (page 95) includes a checklist
that you can use to make sure you perform all the upgrade tasks described in this chapter.
6.1 Upgrade Tasks
Use the checklist in Table 6-1 to ensure that you perform all necessary upgrade tasks.
Table 6-1 Upgrade Checklist
SectionTask
Section 6.2.1 (page 95)Boot the OpenVMS operating system media.□
□
OpenVMS operating system, respond to the prompts, and shut
down the system when the upgrade completes.
□
for your upgraded system disk, add a boot option now, if desired.
□
upgrade you are performing.)
Section 6.3 (page 97), Section 6.4 (page 106)Use option 1 of the operating system menu to upgrade your
Section A.5.2 (page 165)If you did not allow the upgrade procedure to create a boot option
Section 6.5 (page 112)Reboot your system. (The steps vary according to the type of
Chapter 7 (page 113)Perform postupgrade tasks, as necessary.□
6.2 Booting the OpenVMS Operating System Media
The OpenVMS operating system includes procedures that allow you to easily upgrade the
operating system using the PCSI utility. These tools are available once you boot the system
properly.
You can use a VGA graphics device, serial device, or network interface for the console. For
information about configuring your system console, see Section A.2 (page 152).
NOTE: When using a VGA console and upgrading from vMedia or a USB DVD drive with the
keyboard plugged into a USB hub, if the keyboard is not responding, simply unplug the hub
and plug it back in.
6.2.1 Booting the OpenVMS I64 OE DVD
You can boot the OpenVMS I64 OE DVD in any of the following ways. This section gives detailed
instructions on booting from the local DVD drive. Detailed instructions on the other methods
are available in the appendixes, as noted in the corresponding sections that follow.
• From your local DVD drive (Section 6.2.1.1 (page 96))
• From a virtual DVD drive served over the network by the InfoServer utility (Section 6.2.1.2
(page 97))
• From an image on a PC or Windows server in the network accessed through the HP SIM
interface (Section 6.2.1.3 (page 97))
• From an image on a PC or Windows server in the network using vMedia through a browser
connected to your Integrity server iLO 2 MP port (Section 6.2.1.4 (page 97))
The latter two options can be used for entry-class Integrity servers that support such means; they
can be used when a local DVD drive is not available. For more information about booting
operations, see Section A.6 (page 172).
6.1 Upgrade Tasks 95
6.2.1.1 Booting from the Local Drive
To boot a local OpenVMS I64 OE DVD, follow these steps. To boot the DVD on a cell-based
server, a DVD device must be accessible by the nPartition that OpenVMS is being installed on.
1. Make sure your Integrity server is powered on. If your system has an attached external
device, make sure it is turned on and operational.
2. Insert the DVD into the drive you want to use.
3. Cycle power.
4. From the main EFI boot menu (for cell-based servers, this must be the EFI boot menu for
the nPartition on which OpenVMS is to be booted), select the appropriate item from the
boot options list. Note that the EFI boot menu is timed; press any key to stop the countdown
timer.
For some systems, the boot option to select is the Internal Bootable DVD option. If that option
is not listed in your EFI boot menu, move to the Boot From a File menu and select the
Removable Media Boot option, if present.
Alternatively (and this method is recommended for cell-based servers), boot the DVD drive
from the EFI Shellprompt by entering the command shown in the following example, where
fsn: corresponds to the Integrity server DVD drive (such as fs0:). Note that if you have
navigated to a particular file system, the EFI Shell prompt would reflect that file system; for
example, if the current file system is fs0:, the EFI Shell prompt would be fs0:>.
Shell> fsn:\efi\boot\bootia64.efi
To determine which device is the bootable DVD drive, examine the list of mapped devices
and look for an fs device listing that includes the letters “CDROM”, as in the following line,
where fsn is the file system associated with the drive, which is usually fs0: (instead of "fsn",
you might see something similar to "V8.3-1H1"; instead of Ata, you might see Scsi, depending
on the server model):
fsn : Acpi(HWP0002,400)/Pci(4|1)/Ata(Primary,Master)/CDROM(Entry0)
You can use the following command to display the mapping of various EFI device names
to OpenVMS device names, where fsn is the device you want to check (such as fs0:):
Shell> fsn:\efi\vms\ms_show dev -fs
On most Integrity servers, the DVD drive is DQA0: (IDE) or DNA0: (USB). On systems that
include a SCSI bus, such as the Superdome server, the DVD drive is DKA0:. For more
information about the vms_show command, see the HP OpenVMS System Management
Utilities Reference Manual.
NOTE: By default, certain versions of EFI might interpret the Delete (or Backspace) key
differently than do OpenVMS Alpha systems or Microsoft Windows computers. In such
cases, press Ctrl/H to delete the last character entered. For more information, see Section A.1.3
(page 152).
When the DVD boots properly, the OpenVMS operating system banner appears, followed by
the operating system menu. You can now upgrade your OpenVMS I64 operating system on the
target disk (see Section 6.3 (page 97)). If the methods documented in this section do not succeed
in booting the DVD, see Section A.6.2.1 (page 175).
96 Upgrading the OpenVMS Operating System
NOTE: When booting OpenVMS from the installation DVD for the first time on any OpenVMS
I64 system with a SAN storage device, you might experience a delay in EFI initialization because
the entire SAN is scanned. Depending on the size of the SAN, this delay might range from several
seconds to several minutes.
6.2.1.2 Booting Over the Network Using the InfoServer Utility
To use the InfoServer utility to boot from the network, certain configuration steps are required
initially (one time only); see Appendix B (page 189). The instructions on booting over the network
from a virtual DVD drive are also included in Appendix B (page 189).
6.2.1.3 Booting Using HP SIM Provisioning
To use HP SIM provisioning to boot an image of the OpenVMS OE DVD, certain configuration
steps are required initially (one time only). For these steps and the booting instructions, see
Appendix C (page 203). For upgrades, your OpenVMS boot flags must be set to (0,0).
6.2.1.4 Booting Using vMedia
To use vMedia to boot an image of the OpenVMS OE DVD, certain configuration steps are
required initially (one time only); see Section C.1.4 (page 207). For instructions on booting with
vMedia, see Section C.2 (page 232).
6.3 Performing the Upgrade
The following sections describe how to upgrade from the operating system media.
6.3.1 Upgrading the System Using Option 1 of the Operating System Menu
After you boot the operating system DVD (OpenVMS I64 OE DVD), the HP copyright banner
and several messages appear, followed eventually by the operating system main menu. Choose
the upgrade option (1) on the menu, as in the following example:
Installing required known files...
Configuring devices...
.
.
.
****************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
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
6.3 Performing the Upgrade 97
6.3.2 Choosing INITIALIZE or PRESERVE
The procedure displays the following information and prompts:
***********************************************************
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return>key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
There are two choices for installation/upgrade:
Initialize - removes all software and data files that were
previously on the target disk and installs OpenVMS I64.
Preserve -- installs or upgrades OpenVMS I64 on the target disk
and retains all other contents of the target disk.
* NOTE: You cannot use preserve to install OpenVMS I64 on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE])
For an upgrade, press Enter (or Return) to accept the default (PRESERVE).
6.3.3 Specifying the Target Disk
Next the procedure asks for the name of the target disk. If you enter a question mark (?), the
system displays a list of devices on your system. Select the appropriate disk and respond to the
prompt. For example:
You must enter the device name for the target disk on which
OpenVMS I64 will be installed.
Enter device name for target disk: [DKB300] (? for choices) DKB400
If you selecta device that is not available or that cannot be usedfor some other reason, the system
displays informationindicating why the devicecannot be used. For example, if you enter MKA500,
a tape device, a message similar to the following is displayed:
98 Upgrading the OpenVMS Operating System
MKA500 is not a disk device
CAUTION: If the selected target diskincludes .EXE or .COM files installed by a previous upgrade
or installation in one or more system-specific root directories in SYS$COMMON, the upgrade
procedure tells you that when you boot from a root that contains any of these files, they are used
instead of the files provided by the newer version of OpenVMS. This can make the upgraded
system unbootable or cause errors after booting. Unless an HP representative has advised you
to keep one or more of these files where they are, you must delete, rename, or move these files
from the system-specific root directory. The procedure lists the names and locations of these
files. Record these if you are not using a hardcopy terminal. The procedure gives you the option
of terminating the upgrade so that you can do what is necessary for these files: select option 8
(“Execute DCL commands and procedures”) on the OpenVMS main menu and enter the
appropriate DCL commands.
6.3.4 Selecting Reinstallation and Reconfiguration Options
If you are using the OpenVMS Version 8.3-1H1 operating system media and you selected a target
disk that already has Version 8.3-1H1 installed, you are presented with several configuration
options. A sample display follows. See also the example in Section 7.11 (page 136).
Version 8.3-1H1 of the OpenVMS operating system is already installed
on DKB400:.
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 a "?" for more information.
If you enter a question mark (?), the following information is displayed:
o Reconfigure the OpenVMS platform.
This action will allow you to change your selections of which
products you installed along with the OpenVMS operating system
installation.
This will NOT change any options in the OpenVMS operating system,
nor will it reinstall any operating system files.
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.
This will NOT change any options for the products you installed
along with the OpenVMS operating system installation, nor will
it reinstall or upgrade any of them.
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.
This will NOT change any options for the products you installed
along with the OpenVMS operating system installation, nor will
it reinstall or upgrade any of them.
Reinstall will take longer than Reconfigure. Reinstall may be
6.3 Performing the Upgrade 99
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 or upgrade any of the products you installed
along with the OpenVMS operating system installation, choose "Install
or upgrade layered products" (option 3) from the main menu.
If you want to change your choices about which options you included
for any of the products you installed along with the OpenVMS operating
system installation, choose "Reconfigure installed products" (option 5)
from the main menu.
Next the menu is redisplayed:
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/?)
For additional configuration information, see Section 7.11 (page 136).
6.3.5 Checking for Recovery Data
If you specify the /SAVE_RECOVERY_DATA qualifier with the PRODUCT INSTALL command,
the PCSI utility saves information that can be used for removing patches and mandatory update
kits at a later time. Use the PRODUCT UNDO PATCH command to remove the patches and kits.
The upgrade procedure now checks the disk for recovery data saved by the PCSI utility. Any
recovery data must be removed before the upgrade can continue because this data becomes
invalid after the upgrade. If no recovery data is present, the upgrade continues. If recovery data
is present and all the data found applies only to the OpenVMS operating system, the upgrade
procedure deletes the data and continues. (The procedure does not display the deletion of the
files because earlier patches to OpenVMS are always removed as part of the upgrade.) If any of
the recovery data applies to products otherthan the OpenVMS operating system, then the upgrade
procedure displays a message similar to the following:
The target system has recovery data from PRODUCT operations which
used the /SAVE_RECOVERY_DATA qualifier. This data must be deleted
to continue the OpenVMS upgrade.
Please examine the following display.
If you wish to delete this data and continue the OpenVMS upgrade,
answer YES to the question "Do you want to continue?"
If you do not wish to delete this data, answer NO. A NO answer
will preserve the recovery data and abort the OpenVMS upgrade.
The following patch recovery data has been selected:
RECOVERY DATA SET 001 created 25-JUL-2007 15:23:39.69
-------------------------------------- ---------------------------------
PATCH APPLIED TO
-------------------------------------- ---------------------------------
JAK VMS RM1 V1.0 JAK VMS RMTEST V1.0
-------------------------------------- ---------------------------------
* If you continue, recovery data for the patches listed above will be deleted.
* The deletion of recovery data does not affect the installation status of
* patches applied to products that are not participating in this operation.
* However, continuing with this operation prevents you from uninstalling
100 Upgrading the OpenVMS Operating System
Loading...