| |
 |
|
Hard Partition Business Practices
|
|
|
|
Are there any special software requirements to enable hard partitioning?
|
 |
|
|
Yes. The AlphaServer GS140 system only supports hard partitions using Tru64 UNIX V4.0F or later.
The AlphaServer GS160/GS320 systems support a mixed operating system environment within a partitioned
system using Tru64 UNIX V4.0G or V5.1 or greater and OpenVMS V7.2-1H1 or greater.
|
|
What is a mixed Operating System environment on hard partitioned systems?
|
|
|
|
When a AlphaServer GS160/GS320 system is hard partitioned, you can run Tru64 UNIX on some partitions
and OpenVMS on other partitions on that single system.
|
|
Are there any special licensing requirements for the Operating System?
|
|
|
|
No, standard Operating System Base and SMP License still apply. However, if you are setting up a mixed
operating system environment, you will require one Operating System Base License for both Tru64 UNIX
and OpenVMS, and at least one SMP License (Tru64 UNIX or OpenVMS) for each additional CPU on that system.
|
|
Are there any special licensing requirements for hard partitions?
|
|
|
|
No, for Tru64 UNIX and OpenVMS, all partitions are licensed under the Operating System Base License. No additional hardware partition licenses are required.
|
|
Does the Tru64 UNIX Hard Partition License provide rights to a specified version?
|
|
|
|
Tru64 UNIX Hardware Partition Licenses are no longer required.
|
|
Are there special license requirements for any other product?
|
|
|
|
No, other products will continue to be licensed as they are today. For example, a Traditional License
provides the right to use a given software product on all hard partitions within a single system,
and a Concurrent Use License permits a specified number of uses on a single system or VMSCluster configuration.
Note, however, in a mixed operating system environment, each different operating system requires
its own layered product licenses. These licenses may be used on all partition on that system running
the specified operating system. Traditional Licenses continue to be based on the system class for the given system.
|
|
Can I run multiple versions of the same product on different hard partitions within a single system?
|
|
|
|
Yes, however, you must be licensed for the latest version in use. If licensed for the latest version in
use, then the license permits use of all previous versions.
|
|
Will I need a license database for each hard partition?
|
|
|
|
For Tru64 UNIX a separate license database is required for each hard partition. For OpenVMS,
a separate license database is required for each hard partition or VMSCluster configuration.
|
|
Do I need to enter the Operating System Base License PAK into the license database for each partition on a system?
|
|
|
|
Yes, for each partition that is running the same operating system.
|
|
Do I enter all the SMP License PAKs into each license database as well?
|
|
|
|
You enter only the number of SMP License PAKs that are required to support the number of CPUs in a
given partition. If there are 4 CPUs, for example, the first CPU requires the Operating System Base
License PAK, and the remaining 3 CPUs require an SMP License PAK.
|
|
Does this mean I will have one or more SMP license that will not be entered into a license database for
any hard partition after the first?
|
|
|
|
Yes, however, the License PAK/License Certificate document for the SMP License is never the less required
as proof of license for that system. An SMP License is still required for all CPUs after the first
on the system.
|
|
For layered products, do I need to enter the License PAKs into each license database on that system?
|
|
|
|
For layered product Traditional Licenses, the PAKs may be entered into each license database on that
system running the same operating system. Concurrent Use License PAKs must be entered on the license
database where the license will be used. PAKs representing multiple concurrent uses may be entered
into each license database on the system running the same operating system. However, you are required
to modify the number of license units so that your actual usage will not exceed your license usage.
|
|
Can I run an OpenVMS Galaxy environment in a hard partitioned system?
|
|
|
|
Yes, you may run an OpenVMS Galaxy environment in any OpenVMS hard partition.
|
| |
|
|
OpenVMS Galaxy Business Practices for Alpha and VAX systems
|
|
|
|
How is OpenVMS Galaxy Software Architecture on OpenVMS (OpenVMS Galaxy) licensed?
|
|
|
|
OpenVMS Galaxy is licensed on a cpu basis. An OpenVMS Galaxy license is required for each and every
cpu in an OpenVMS Galaxy computing environment.
|
|
Does use of OpenVMS Galaxy change license requirements for any other product?
|
|
|
|
No, other products will continue to be licensed as they are today.
|
|
Is it true that when multiple instances are created using OpenVMS Galaxy, that I will need
an LMF data base for each of these instances?
|
|
|
|
That depends. If multiple instances within a system are clustered together using OpenVMS Galaxy
technology, then you will only need a single LMF data base for each cluster. Otherwise,
you will need a separate LMF data base for each instance.
|
|
If I have multiple LMF data bases on a single system, does that mean I need to purchase additional
licenses for OpenVMS and for the layered products?
|
|
|
|
No, you may use a single license for each product for the entire system. For all license types
you may load the License PAKs into each data base in the Galaxy system. For Concurrent Use licenses,
however, you are required to "modify down" the number of license units so that your actual usage
will not exceed your licensed usage.
|
|
Are OpenVMS Galaxy licenses transferable from one system to another?
|
|
|
|
Yes, OpenVMS Galaxy is a Category 2 product and may be transferred (redesignated) from one system to
another. However, you need to keep in mind that all cpus in a single system must be licensed for OpenVMS
Galaxy. Hence, the transfer of the license would typically occur if you were also transferring the
cpu board.
|
|
Can I run multiple versions of the same product on different instances within a single system?
|
|
|
|
Yes, however, you must be licensed for the most current version in use.
|
|
If a system, for example, is configured with 3 instances, each with its own LMF data base, can I set up
a cluster to an external system with one of those license data bases?
|
|
|
|
Yes, however, you may need to take certain precautions. For Concurrent Use licenses you will need to
make sure that the total number of actual uses does not exceed the number of licensed uses as mentioned
above. For Traditional licenses only one of the systems may use the product at any point in time.
If a Traditional license is used on all instances within a system, and one of those instances is
clustered to another system, then the license for the clustered instance should be assigned to that
instance to prevent use on the other system.
|
|
Does OpenVMS Galaxy also allow me to cluster multiple systems together?
|
|
|
|
No. A cluster of two or more systems requires an OpenVMS Cluster license for each system.
|
| |
|
|
General License Questions for Alpha and VAX systems
|
|
|
|
How do I purchase new versions of HP software?
|
|
|
|
If you want to make sure that you receive all the updates to a given product you should purchase a service contract which provides software updates and rights to use these updates. Otherwise, you may purchase an Update License for each new version provided that you already have the appropriate underlying license, e.g., a Traditional License.
|
|
If I bought my software from a Business Partner, how do I know that I am properly licensed?
|
|
|
|
An Authorized Reseller is required to have their customers agree to HP's license terms. If you have not agreed to or seen any such terms, you should check with the Business Partner from whom you purchased the software.
|
|
Does HP offer a site license?
|
|
|
|
HP accomodates the needs of customers who make large purchases in a number of different ways including standard discounts, discount curves, and specially priced volume options for certain software. Customers who have specific needs should contact their local HP contact (see Contacts).
|
|
What are HP's most common license types?
|
|
|
HP's most common standard license types for VAX and Alpha systems are:
- the Operating System Base which provides batch and file services for Tru64 UNIX and OpenVMS.
- the Traditional and Concurrent Use Licenses which provide interactive use for HP's tools, utilities, applications, as well as for the operating systems.
|
|
Can I trade-in my Traditional or ClusterWide Licenses for Concurrent Use Licenses?
|
|
|
|
Yes. HP has an offering called Trade Up To User (TUTU) which provides you with an equivalent value of Concurrent Use (or Personal Use if offered) upon the trade-in of your Traditional or ClusterWide License.
|
|
Do the terms on the back of the License PAK or Software License Certificate apply to me?
|
|
|
|
These terms are printed on the back of the License PAK or Software License Certificate to make it easy for customers to have access to HP's license terms and conditions for VAX and Alpha systems. The terms are part of your contract only if referred to as such in your purchasing agreement with either HP or with a HP Authorized Reseller. Otherwise, the license terms in your purchasing agreements with either HP or a HP Authorized Reseller apply.
|
|
What are the main differences between HP's standard license offerings for VAX and Alpha systems and its PC-style (shrinkwrap) licenses?
|
|
|
There are three main differences:
- HP's standard license offerings for VAX and Alpha systems are non-transferable (although HP will Relicense certain software products). HP's PC-style offerings are customer-transferable, however, restrictions may apply to certain products.
- Customers receive a License PAK or Software License Certificate upon an order for a standard license. Customers receive a License Agreement upon the order for a PC-style license.
- HP's standard license offerings for VAX and Alpha systems are provided under signed license agreement. PC-Style offerings utilize the "shrinkwrap" form of licensing common in the industry today.
|
|
How is PATHWORKS licensed?
|
|
|
|
PATHWORKS is a product that is provided under PC-style licensing, however, delivers a License PAK or Software License Certificate.
|
|
What is a Software Product Description (SPD) and where can I get one?
|
|
|
|
The Software Product Description is a document that describes the functionality of a given software product or a set of products within the same product family. In addition, the SPD contains other information such as ordering, hardware and software requirements, and licensing. When a product has non-standard license terms, they will appear in the licensing section of the SPD. Look in this InfoCenter under Reference material: Software Product Descriptions.
|
|
If my computer breaks, am I allowed to move my license and software to another computer while the first one is being fixed?
|
|
|
|
Yes, the license key may be installed (registered, enabled, and loaded) onto the backup system, however, only for the time that the first system is not operational. Once the first system is operational, then the license key must be removed (unloaded, disabled, and deleted) from the backup system.
|
|
I have some licenses that are subject to a "rating." Where can I get a list of the ratings of the various system models?
|
|
|
|
ClusterWide Licenses, which are no longer offered, are subject to a rating. Look in this InfoCenter under Reference material, VAX License Rating Table, to see what ratings apply.
|
|
One of my applications requires an old version of the operating system. How can I ensure I have the rights to run the version current at the time of license purchase and all prior versions?
|
|
|
|
Simply purchase the license for the HP current version. This license permits use of the HP current version and all prior versions.
|
|
If I am running an old version of the operating system and want to add users, what licenses should I purchase?
|
|
|
Please purchase the following:
|
Customer running:
|
Purchases:
|
| OpenVMS VAX V5.5 |
QL-XUL**-B* |
| OpenVMSVAX V6.0-6.1 |
QL-09S**-B* |
| OpenVMS VAX V6.2 or greater |
QL-MT3**-3* |
| OpenVMS Alpha V1.5 or greater |
QL-MT3**-3* |
|
Tru64 UNIX any version |
QL-MT7**-3* |
|
| |
|
|
Upgrading and Moving Software for Alpha and VAX to Different Systems
|
|
|
|
Does my software license allow me to move software between different systems?
|
|
|
|
Traditional and Concurrent Use Licenses permit you to move the software between different systems provided the license is valid for the new system. You may NOT move the Operating System Base License between different systems. Restrictions may apply to certain products and certain other licenses.
|
|
How do I know the license is valid for the new system?
|
|
|
|
For Traditional Licenses you can check the System Chart. Concurrent Use Licenses are valid for either an OpenVMS or a Tru64 UNIX platform. If your license key for the Concurrent Use License works on a given system, it is very likely that you have the correct license.
|
|
What software licenses can I trade-in when upgrading my hardware?
|
|
|
|
If you want to move your HP-licensed software product to another system that is in a higher System Class or that is a different platform (e.g. VAX OpenVMS to Alpha Tru64 UNIX), then any license that may be moved can be traded-in towards the purchase of the appropriate license for the new system.
|
|
How do I prove that I bought the license so that I can trade it in for another license?
|
|
|
|
HP accepts various proofs of licenses for VAX and Alpha software such as the License PAK, Software License Certificate, and the invoice listing the software license. In addition, customers of HP Authorized Resellers can show a valid sublicense agreement.
|
|
Can I trade-in my operating system license for another one on Alpha systems?
|
|
|
|
Yes. For Alpha systems, HP provides the customer with the ability to trade-in one operating system for another, e.g., OpenVMS for Tru64 UNIX. The previous license remains in effect for an additional six months.
|
|
I recently purchased an additional board for my computer to upgrade it from a VAX 7710 to a VAX 7720. Do I need to purchase any additional licenses?
|
|
|
|
Yes, you must upgrade the Operating System Base License by purchasing an SMP extension to this license. An SMP Extension is required for each additional board. However, other products that are sold under System Class Structure do not need to be upgraded in this case since the VAX 7710 and VAX 7720 are in the same "Enterprise" System Class, and the same license may be used on any system model within a given System Class.
|
| |
|
|
Selling and Buying Used Alpha and VAX Hardware and Software
|
|
|
|
If I sell my old hardware, can I sell my software as well?
|
|
|
Software may be sold under certain condions:
- Only the operating system and other Category 1 products may be sold (See the Transferable Software List.)
- The seller must apply to Digitial for a Relicense to transfer the license for this software to the buyer. Upon HP approval of this Relicense, the seller may sell the software to the buyer.
|
|
Can I use the license key that came from the buyer with the used hardware and software I recently purchased?
|
|
|
|
No. HP's terms and conditions for VAX and Alpha software do not permit the seller of used systems and software to provide the new buyer with license keys. The seller must apply to HP for a Relicense of the software and turn-in the existing keys to HP. Upon approval of the application, the seller's license is terminated and HP issues a new license key (also referred to as a License PAK or Software License Certificate) to the buyer.
|
| |
|
|
|
If I lost my license key (PAK), how can I get a replacement?
|
|
|
|
The procedures for license key replacement vary by country. Contact the appropriate contact for your country (see Contacts).
|
|
Where can I find the instructions for installing my license key?
|
|
|
|
You may refer to the operating system license management utility manual.
|
|
If after reading the manual I still have problems installing license key, whom can I contact?
|
|
|
|
See Contacts to locate an HP contact for your country.
|
|
What is a license management database?
|
|
|
|
A license management database contains data about certain attributes of a given license, such as Producer Name and Authorization Number (for HP's License Management Facility for VAX and Alpha software). Once a license key has been entered into the data base, the license manager will permit use of that product.
|
|
Can the license key be installed in more than one license management database at a time?
|
|
|
|
If the system on which the software is licensed malfunctions, the license key may be loaded on a second system temporarily for the period of the malfunction. Also, HP provides for the license key to be registered (but not loaded) on a second system to prepare for the event of a failure, and may be loaded at the time of the failure. If a license key is enabled for use on two systems simultaneously, then two licenses are required.
|
printable version
