Read PDF Getting Started with OpenVMS System Management (HP Technologies)

Free download. Book file PDF easily for everyone and every device. You can download and read online Getting Started with OpenVMS System Management (HP Technologies) file PDF Book only if you are registered here. And also you can download or read online all Book PDF file that related with Getting Started with OpenVMS System Management (HP Technologies) book. Happy reading Getting Started with OpenVMS System Management (HP Technologies) Bookeveryone. Download file Free Book PDF Getting Started with OpenVMS System Management (HP Technologies) at Complete PDF Library. This Book have some digital formats such us :paperbook, ebook, kindle, epub, fb2 and another formats. Here is The CompletePDF Book Library. It's free to register here to get Book file PDF Getting Started with OpenVMS System Management (HP Technologies) Pocket Guide.
Getting Started with OpenVMS System Management (HP Technologies),, ( isbn , ean ), by Miller D.
Table of contents



Top Authors

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. If this is the first installation on this system, no default device is indicated, as in this example. 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 MKA, a tape device, a message similar to the following is displayed:. Specify the Volume Label: If you select a device that can be used, the procedure then informs you of the volume label currently assigned to 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. 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. Specify On-Disk Structure Level: A brief summary follows.

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-5 supports file names that are longer, have a wider range of legal characters, and allow for mixed-case file names. ODS-5 supports hard links to files, access dates, and files whose names differ only by case. 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.

Only ODS-5 supports hard links. 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. 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 IH1. On OpenVMS I64 installations, the procedure next asks whether you want to create or validate boot options. 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 If a boot option exists, you can change boot flags after the installation completes for information about changing boot flags, see Section.

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. COM after the installation completes. Be sure to add all members to both lists.

Passwords must be at least 8 characters in length but must not exceed 31 characters. 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. 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. COM to run automatically when your newly installed system is first booted. If you answer YES to the cluster question, the display is similar to the following:.

However, in this case you must explicitly configure the node into the cluster after the installation is completed. The next prompt asks whether you plan to use DECnet. If you are not using DECnet, or if you enter 0. If this is a standalone system , the default of is acceptable. The following is a sample display:. 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. 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 zone desired. 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? 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:. You can enter one or more words or partial 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:. The procedure now provides information about and prompts you to enter the time differential factor TDF. The procedure supplies a default for TDF, which is generally the correct response.

HP OpenVMS Version 8.3-1H1 for Integrity Servers Upgrade and Installation Manual

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 procedure:. 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:. Register Licenses Optional at this time: You register licenses later by following the directions in Section.

To register your licenses now, be sure you have the following before proceeding:. 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. 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:.

COM procedure, which displays the following options menu:. After you register all your licenses, exit the License Management procedure by entering 99 at the prompt. Install Windowing, Networking, and Related Products: 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. You may install any of the optional software products separately after the OpenVMS installation completes.

Prior to Version 8. The OpenVMS installation procedure installs this kit automatically. You cannot have both installed on your system at the same time. You can also choose to install neither DECnet product; however, certain products that depend on DECnet might be adversely affected. Choose Descriptive Help Text Optional: First, the procedure asks whether you want detailed descriptions:. If you answer YES, the procedure displays additional explanatory text with each prompt.

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. For each kit successfully validated, you see a message similar to the following:. Any signed PCSI kits that you install susbsequently including any signed kits on the distribution media are validated. The procedure displays a message such as the following, indicating that it is ready to install the operating system:. If you want all the default values, press Enter.

If you want to select options individually, answer NO. 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 support the needs of your users. 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?

After you select all the options you want, you can view your selections and make changes if necessary. 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. 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. 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. 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 selections and make changes if necessary, then installs the product, provides informational messages, and returns you to the original menu. If you answer NO, the installation continues as described with the sample script beginning with "Execution phase starting 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:. 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 installation or upgrade will proceed normally and the message is not present when the system reboots with its actual node name.

Final Installation Confirmation and Information Messages: The installation continues, displaying the products that have been installed and relevant information. 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:. 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. If you answered YES in step 8, the installation procedure determines whether a boot entry already exists for the system disk in this example, DKB If an entry is found , a message similar to the following is displayed:.

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:. 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:. If no existing entry is found , a boot option is created and the procedure displays the validation text, as in the following example:.

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. Shut Down the System: Unless you want to perform other operations prior to booting the new system disk, choose the shutdown option 9 on the OpenVMS 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. After you complete the installation and shut down the system, you can boot your new operating system disk, as explained in Section. After you have successfully installed the OpenVMS operating system, the next step is to make the new system disk the default boot device. For booting the OpenVMS Alpha system disk, first designate the new system disk as the default boot device by performing the steps in Section. Then, to boot the disk, perform the steps in Section.

Substitute the device name of the system disk for target-drive. For example, if the system disk has the device name DKA, enter the following command and press Enter:. If the system disk is connected to a hierarchical storage device HS x , the format for specifying that drive is different.

To boot the system disk, enter the following command and press Enter:. When the system starts booting, the initial informational messages displayed are similar to the following:. For more information about this and special booting operations, see Section. 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 second countdown. If you have not configured your system with a boot option for your disk , follow these steps:. Press Enter or any other key. You might see text that instructs you to "hit any key to cold reboot.

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. 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.

For example, if the target disk is DKA0, then fs0: The blk devices are block devices. Multiple blk devices exist for each volume that has a bootable partition or diagnostic partition. Diagnostic partitions are intended and reserved for use by HP Services. A display similar to the following appears, followed by the prompt for user name and password:. 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.

When you boot OpenVMS from a new system disk, a special startup procedure runs that does the following:. Reboots your system with the new parameters see Section. 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 now, as explained in Section.

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. Note that, depending on your responses and the particular cluster configuration, some prompts are not displayed. This is the name you specified in step 12 of the installation procedure. Enter the DECnet node address; for example, 2. This is the address you specified in step 13 of the installation procedure.

Enter the cluster password. Enter Y if you want local disks to be served to the cluster mandatory for local area and mixed-interconnect configurations. However, if you are adding a two-system DSSI configuration to an existing cluster in which case you might not need a quorum disk , you can answer N.

Refine your editions:

If you enter Y, the system asks for the name of the quorum disk. Enter the device name of the quorum disk. If your configuration fits either scenario, you can answer NO N to this question. The OpenVMS Alpha system should automatically reboot after the shutdown; the installation is finished. However, if the Alpha system does not reboot automatically, reboot the system manually.

For example, if the system disk is on an RZ25 disk drive with a unit number of 1, enter the following command and press Enter:. 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. 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. The following two sections explain how to log in to the SYSTEM account from a character-cell terminal and from a workstation.

Press Enter or click OK with your mouse. At this point, you can create a DECterm session or initiate other management functions. This chapter describes which tasks you should perform prior to beginning an upgrade. In addition to reviewing the information in this chapter, you might need to refer to the following sources of information as well. DAT , and related operations. 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. Instead, you must first upgrade to Version 7.

Similarly, before upgrading your OpenVMS Alpha system, you must have the appropriate Alpha licenses 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. A PAK does not provide license or new version rights. For information about checking for appropriate versions of software on your system and for certain products requiring that you manually remove older versions, see Section.

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. Before you shut down the operating system that you plan to upgrade, follow these steps to remove DECram for OpenVMS if you have already shut down your operating system, you must reboot before continuing.

If the resulting display shows that DECram is not found on the system, skip to step 3; otherwise, proceed to step 2. Once this command has completed successfully, you are finished; you do not need to perform the next steps. If the product removal fails, go on to step 3. If files are found, use the commands in step 4 to remove them.

If no files are found, skip to step 5. Before you shut down the operating system that you plan to upgrade, follow these steps to remove TDC V2. If the resulting display shows that TDC is not found on the system, no action is required; if TDC is found, proceed to step 2. By default, the upgrade procedure deletes files that were archived as filename. If you do not want these files deleted, you can rename them before you perform the upgrade. Alternatively, you can have the upgrade procedure save them by responding to the prompts, as described in Section.

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. 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. If you have any special protections and access control lists ACLs , you need to reapply them to reestablish the security environment you currently have. To check whether this is the case, enter the following commands if 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:. 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 DKA, you would use commands similar to the following:. Output from the first command should list a single file. Output from the 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.

A-L for more information about this command. Use the following procedure:. Analyze the system disk for inconsistencies and errors in the file structure by entering the following command: Ignore the following message: If you find any other errors on the system disk, repair the errors by entering the following command:. Repeat steps 1 and 2 until no errors other than the one shown in step 1 are returned. 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 , 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. 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. To see how much space you have on the system disk, enter the following command:.


  1. Corrente Quinta, No. 37 from Toccate, canzone ... di cimbalo et organo, Vol. II.
  2. Fogo em dois corações (Sabrina) (Portuguese Edition).
  3. 6 editions of this work?

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. OpenVMS allows you to relocate certain system files mostly authorization files off the system disk. 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.


  1. Getting Started with OpenVMS System Management (HP Technologies).
  2. Portent.
  3. iPad: A Guide and the Tricks you didn’t know.
  4. ?
  5. Jim Raptor and The Time Machine.

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. 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. EXE, might not exist on your system, depending on certain configuration settings.

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:. 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.

Verify and modify if necessary system parameters. Tuning, Monitoring, and Complex Systems. 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.

DAT file are lost during the upgrade. Enter numeric values as integers, without commas for example, Enter alphabetic characters in lowercase or uppercase. 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:. DAT file was created then.

This file has comments and possibly duplicated entries that were created during that upgrade. DAT can become unnecessarily large and potentially confusing. DAT before you upgrade again. DAT as necessary for each root. DAT file is available, it is used. DAT file is available. 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:. This runs very quickly and should not affect the performance of your system while it executes.

COM procedure; however, the data captured might not fully reflect the typical workload on your system. If you wrongly assume the feedback is valid, the parameter settings might vary significantly from your expectations. You must read the report and decide whether the calculated values are acceptable. 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. Be sure your system is set to boot by default from the disk you intend to upgrade. COM to add shadowed system disks in a multiple-member shadow set to the EFI boot device list and dump device list.

For more information about setting boot options and using this utility, see Section. Perform the steps described in this section to change one of your existing shadowed system disks to a nonshadowed disk. Shut down all systems booted from the shadowed system disk. After the boot completes, go to Section. 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. 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.

Bestselling Series

A backup copy might be the only route to recovery. The minimal time required to make a backup is a very wise investment. Use the menu system to enter the DCL environment option 8. 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: To back up the system disk to a magnetic tape, enter the following commands, where MTA0: If any discrepancies are detected, the Backup utility displays an error message indicating the discrepancies. Shut down the system by selecting option 9 on the menu. Continue the preupgrade tasks as follows, depending on whether you are upgrading in a standalone or OpenVMS Cluster environment: Review the checklist at the beginning of this chapter to verify that you have performed the necessary tasks. 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. For information about valid upgrade paths, see Section. Any node in the cluster that is running an older version of OpenVMS must be upgraded appropriately before you can add a Version 8. Alternatively, any OpenVMS Alpha or 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. Two types of cluster upgrades are available: 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. 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 the cluster reboots, each computer will run the upgraded version 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.

Getting Started with OpenVMS System Management

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. 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. Shut down all systems by entering the following command on each system satellite node s first, then the boot nodes:. When the procedure asks whether an automatic system reboot should be performed, enter N NO. For more information about halting your Integrity server, see Section. For information about halting your Alpha computer, see Section.

After the upgrade is complete, you are instructed to reboot each computer in the OpenVMS Cluster environment before beginning other postupgrade procedures. 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. The following restrictions apply to rolling upgrades. 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. 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 the remaining OpenVMS Cluster members.

Any attempt to access the target 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. You cannot perform a rolling upgrade if all systems boot from a single system disk.

HP OpenVMS systems documentation

Perform a concurrent upgrade instead. The upgrade procedure affects the queuing system as follows:. 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. To prepare for a rolling upgrade, follow these steps: Log in to any node where the target disk is mounted as a data disk rather than as the system disk.

Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. Note that you can ignore messages from nodes where the specified data disk is being used as the system disk. Verify that the data disk has been dismounted successfully by entering the following commands:.

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, indicates that the disk most likely is the system disk.

Use the following command to shut down any nodes that boot from the system disk you are upgrading shut down satellite nodes first:. 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 console of a system that is still a cluster member.

Enter the commands at the console:. To adjust quorum, enter the commands shown in the following example. The IPC facility is not available in this case. 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.

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. 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. Enter the DCL environment by choosing option 8 on the menu. Perform the upgrade again by choosing the upgrade option 1 on the menu and following the procedures described in this chapter. Detailed instructions on the other methods are available in the appendixes, as noted in the corresponding sections that follow. 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.

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: For upgrades, your OpenVMS boot flags must be set to 0,0. The following sections describe how to upgrade from the operating system media. Choose the upgrade option 1 on the menu, as in the following example:. Next the procedure asks for the name of the target disk.

If you enter a question mark? If you select a device that is not available or that cannot be used for some other reason, the system displays information indicating why the device cannot be used. If the selected target disk includes. 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: A sample display follows. See also the example in Section. 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 other than the OpenVMS operating system, then the upgrade procedure displays a message similar to the following:. After you specify the target disk and, if applicable, check for recovery data, the procedure informs you of the volume label currently assigned to the target disk you specified and asks whether you want to keep that label.

As shown in the following example, if you choose not to keep the label, you are prompted for a new label. You can accept the default label assigned by the system or specify a different volume label. If a disk that has the same label as the system disk is mounted, various OpenVMS components will not function as intended or a node might crash during boot.

If you change the volume label for a disk in an OpenVMS Cluster, be sure to change the command that mounts the disk on other nodes in the cluster; otherwise, the disk will not mount on those nodes once they are rebooted. If the target disk is currently initialized with ODS-5, the upgrade continues without displaying information about the disk structure.

You are not asked whether to convert the system disk's structure or whether to enable hard links. If your disk was initialized with ODS-5, and hard links was not enabled but now you want to enable hard links, you can enable them prior to the upgrade by using the following commands as shown:.

ODS-5 supports file names that are longer and have a wider range of legal characters. If you choose not to change to ODS-5, the upgrade continues and the target disk is mounted. If you choose to change to ODS-5, you are given the option to enable hard links. The upgrade then continues. This operation can take from 5 to 10 minutes to an hour or more, depending on the complexity of the system disk configuration, the number of layered products installed, and the number of user files.

During the process, messages similar to the following are displayed:. On OpenVMS I64 upgrades, the procedure next asks whether you want to create or validate boot options. If your system disk will normally be booted on this system and this device, and if you want the upgrade procedure to assist you in setting up or validating boot options on the EFI console in the EFI Boot Manager menu, answer YES.

The procedure creates and validates a new boot option if one does not exist, or it validates existing boot options, just before the upgrade completes. If a boot option exists, you can change boot flags after the upgrade completes for information about changing boot flags, see Section. If you do not want the procedure to assist you in setting up or validating boot options on the EFI console, answer NO.

HP recommends that you allow the procedure to assist you in setting up and validating boot options. COM after the upgrade completes. When upgrading from versions of OpenVMS prior to 8. COM procedure to run automatically when your upgraded system is first booted. However, correct cluster membership information is required by the upgrade procedure.

Note that you can run run this procedure manually to configure or reconfigure your system as a member of an OpenVMS Cluster. For local time zone support to work correctly, the time zone that accurately describes the location you want to be considered as your default time zone must be set. If the installation procedure determines that time zone information is incomplete, it prompts you to set the correct default time zone and TDF for your system.

For information about setting the time zone information, see Section. As noted by the procedure, you can change the default values for these products later in the installation procedure. Required versions of some of the windowing and networking products might already be installed on the system.

If so, you will see a message to this effect, as seen for most of the products in the previous example. For some of the windowing and networking products, earlier versions might be installed that still work on OpenVMS Version 8. In this case, you will see a message indicating the software is already installed and asking whether you want to install the newer version. You can keep the currently installed version or upgrade to the newer version supplied with OpenVMS Version 8.

If you choose to keep the currently installed version, you should verify what level of support for this version is available from HP. Some windowing and networking products might have versions installed that do not work on OpenVMS Version 8. In this case, you are not given a choice to upgrade—the software is upgraded automatically.

The following sections describe the remaining steps that you need to perform to complete the upgrade. Each target file includes an associated digital signature file also referred to as a manifest that is used for Secure Delivery validation. By default, the OpenVMS upgrade deletes files that were archived as filename.

If you do not want to delete these files, you can save them by performing one of the following actions:. When the script asks whether you want the defaults for all options, answer NO. This script is shown in the example in Section. Step through the options and answer NO to the option for deleting files archived by remedial kits. This action saves all such files. Files that you do not rename are deleted. As you begin the upgrade procedure, the procedure asks whether you want all the default values meaning all the files and subgroups of files for each component included in the operating system.

During an upgrade, the PCSI utility defines default values as the values that you selected when you last installed or upgraded the OpenVMS operating system on your system. Therefore, before you respond to the prompt, note the following:. If you accept the default values, you receive the same components that you selected when you last installed or upgraded the system instead of all the components currently available plus any new components that were not in the previous version of the OpenVMS operating system.

If you want to include or exclude any components differently than you did in the last installation or upgrade, you must answer NO and then respond to the prompts for each option, even those that you are not changing. If you want to review the current defaults first, answer NO. Then answer YES when the procedure asks whether you want to view the values. If you review the defaults and are satisfied, answer YES to the prompt asking whether you are satisfied with the values.

If you want to make changes, answer NO to that question and then answer YES when the procedure asks whether you want to reenter the values. Whether you choose all the default values or select individual files, the procedure allows you to view your selections and make changes. If you are not sure whether you want certain component options, you can request help by entering a question mark?

You should review the list of options and compare them with the requirements for your procedure. Note also that certain components depend upon the installation of other components. 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 that product. If you decide after the upgrade to change which OpenVMS operating system components you want installed on your system, you must reconfigure the installation as described in Section.

When you have answered all the prompts and selected the components you want installed, the procedure allows you to review your selections and make changes, and then displays information about the various components and products that were installed, as shown in the following sample display in which the review is not chosen. The "fixup" allows them to be correctly removed. The installation or upgrade will proceed normally and the messages will not be present when the system reboots with its real node name. At this point in an OpenVMS I64 upgrade, the procedure creates and validates boot options if you chose to have the procedure do so see Section.

If you answered NO , the following message is displayed. The procedure then informs you that the upgrade is complete and prompts you to press Return Enter to continue, at which point it returns you to the OpenVMS main menu. If you answered YES , the procedure determines whether a boot entry already exists for the system disk in this example, DKB If multiple entries are found and if they are all SCSI devices, the procedure displays the following message and then notifies you that the upgrade is complete:.

If no existing entry is found , a boot option is created and the procedure displays validation text as in the following example:. The upgrade procedure is now complete. Unless you want to perform any other operations prior to booting the upgraded disk, shut the system down by choosing the shutdown option 9 on the menu:. After an OpenVMS Alpha system shuts down, you can make the newly upgraded system disk the default boot device, if necessary, and then boot the system disk.

If you are doing a concurrent or rolling upgrade in an OpenVMS Cluster environment, do not boot any other cluster members now. Once you have completed all required postupgrade tasks, you can reboot and then use other cluster members. After you have installed or upgraded the OpenVMS operating system, you must perform several important tasks to prepare the system for operation. Unless indicated otherwise, these tasks are applicable as both postinstallation and postupgrade tasks. For a newly installed system disk, you can back up the disk. At this point, you could reinstall OpenVMS onto the disk instead.

For a newly upgraded system disk, if it is not going to be a shadow set member, back up the system disk as a safeguard before proceeding with the next steps. If your newly upgraded system disk is going to be a shadow set member, you can re-form it in a later step. As an optional precaution, you can back up the system disk as well. Configure DECnet if it was installed. After an upgrade, perform only if DECnet was added during the upgrade.

Networking software is required to download patches and for certain layered products. COM optional, HP recommends keeping libraries in expanded format. Alpha upgrades only optional: Reinstall optional DECevent software which is automatically removed during an upgrade.

Unless your newly installed or upgraded system disk will be part of a shadow set, HP recommends that you back up the system disk before performing the tasks described in this chapter. If you encounter problems while performing any of these tasks, having a backup copy of the system disk ensures that you can restore it to a known condition without having to repeat the installation or upgrade.

If your system disk will be part of a multiple-member shadow set, then a backup is not necessary. Remember to dismount any added shadow set members after the shadow copy has completed, complete any steps described in this chapter that you need to perform and, when you are finished, re-form the shadow set. By using our website you agree to our use of cookies. Dispatched from the UK in 3 business days When will my order arrive? Home Contact Us Help Free delivery worldwide. He defines areas of OpenVMS System Management and describes why each is important and how it fits into the larger management task.

So, wherever possible, Miller points out to his readers the parallel to other systems. Thus it refers the reader to other books for the detailed management steps. Product details Format Paperback pages Dimensions x x Bestsellers in Operating Systems. Designing Distributed Systems Brendan Burns. Kubernetes - Up and Running Joe Beda. Terraform - Up and Running Yevgeniy Brikman. Mastering Docker - Russ McKendrick. Practical Monitoring Mike Julian. Countdown to a Moon Launch Jonathan H. Joel on Software Avram Joel Spolsky. Operating Systems William Stallings.