HP OpenVMS Systems
HP OpenVMS systems
Evolving business value
Content starts here HP OpenVMS Integrity supported I/O options - Updated February 14, 2011
OpenVMS version 8.4 frequently asked questions
- 1.- What's new in this version
- 2.- What changes will be required of applications in going from OpenVMS v8.3 or v8.3-1H1 to OpenVMS v8.4?
- 3.- I have a cell-based Integrity server (running HP-UX, Linux, Windows) today. Can I run OpenVMS on it?
- 4.- What does OpenVMS version 8.4 support?
- 5.- What new Blades management capabilities are available?
- 6.- How is HP OpenVMS for Integrity servers offered?
- 7.- What is the licensing policy for the Operating Environments and Layered Products for OpenVMS?
- 8.- What are the new flexible policies called iCAP, TiCAP, and PPU that are now available with HP OpenVMS version 8.3-1H1?
- 9.- My application runs on a VAX system today. How do I get to HP Integrity servers?
- 10.- How can I find out the status of my third party application porting to OpenVMS?
- 11.- What are the plans (roadmap) for OpenVMS from here on?
- 12.- Can I trade in my existing VAX system and AlphaServer system licenses for HP Integrity server licenses?
- 13.- Where can I find more information on the services that HP provides for OpenVMS?
- 14.- Will all HP Layered Products for OpenVMS on AlphaServer systems be available on OpenVMS for HP Integrity servers?
- 15.- How do processors and cores compare performance-wise on AlphaServer systems versus HP Integrity servers with dual-core processors?
- 16.- I am having difficulty finding OpenVMS resources. What can I do?
- 17.- What kind of partitioning support is be provided?
- 18.- I ported my UNIX® applications to OpenVMS. Will there be any difference when porting to OpenVMS on HP Integrity servers?
- 19.- Can I do a board swap to upgrade my AlphaServer system to an HP Integrity server?
- 20.- How well will my applications perform on Integrity servers as compared with my AlphaServer system environment?
- 21I don't have the source code for an application that is critical to my environment. Will a translator or emulator be available?
- 22.- I have non-IEEE floating point binary data stored on disk that will need to be accessed by my applications on HP Integrity servers. Since HP Integrity servers only supports IEEE floating point operations, will I need to convert all of my data?
- 23.- Some of my applications are written in AlphaServer system assembler (MACRO-64). What do I do?
- 24.- Some of my applications are written in PL/1. Will they port to OpenVMS for HP Integrity servers?
- 25.- I currently run several 32-bit applications on VAX systems. Will there be any emulation mode to run VAX system applications on Integrity servers? If not, what is my solution? I prefer not to go from VAX system code to AlphaServer system code and then to HP Integrity server code.
- 26.- What threads interfaces does OpenVMS on HP Integrity servers support?
- 27.- What server architectures are supported in OpenVMS mixed-architecture clusters?
- 28.- How can HP help me to integrate HP Integrity servers into my current AlphaServer OpenVMS environment?
- 29.- Will all of the operating system features on which I've come to rely on in OpenVMS for AlphaServer systems be available on HP Integrity servers?
- 30.- Does HP offer advanced training on OpenVMS?/
- 31.- Does HP offer programming courses on OpenVMS?
- 32.- Why should I take OpenVMS training from HP?
2. What changes will be required of applications in going from OpenVMS v8.3 or v8.3-1H1 to OpenVMS v8.4?
OpenVMS v8.4 includes no changes that will require updates to applications that have been qualified on v8.3.
3. I have a cell-based Integrity server (running HP-UX, Linux, Windows) today. Can I run OpenVMS on it?
In general, you should be able to load OpenVMS in one or more partitioned cells. However, it is important to check to be sure of system compatibility. Earlier versions of HP Integrity servers do not support OpenVMS.
OpenVMS v8.4 supports the following servers:
Current OpenVMS versions by server
|HP Integrity rx1620 Server||8.3-1H1, 8.3, 8.2-1|
|HP Integrity rx2620 Server||8.3-1H1, 8.3, 8.2-1|
|HP Integrity rx2660 server||8.3-1H1, 8.3, 8.4|
|HP Integrity rx3600 Server||8.3-1H1, 8.3, 8.4|
|HP Integrity rx4640 Server||8.3-1H1, 8.3, 8.2-1|
|HP Integrity rx6600 Server||8.3-1H1, 8.3, 8.4|
|HP Integrity rx7620 server||8.3-1H1, 8.3, 8.2-1|
|HP Integrity rx7640 Server||8.3-1H1, 8.3, 8.4|
|HP Integrity rx8620 server||8.3-1H1, 8.3, 8.2-1|
|HP Integrity rx8640 Server||8.3-1H1, 8.3, 8.4|
|HP Integrity Superdome||8.3-1H1, 8.3, 8.2-1, 8.4|
|HP BladeSystem c-Class BL860c||8.3-1H1, 8.3 plus patch kit, 8.4|
|HP BladeSystem c-Class BL870c||8.3-1H1, 8.4|
|HP BladeSystem c-Class BL860c i2||8.4|
|HP BladeSystem c-Class BL870c i2||8.4|
|HP BladeSystem c-Class BL890c i2||8.4|
|HP Integrity rx2800 i2 Server||8.4|
|All HP AlphaServer systems||8.3, 8.2, 8.4|
For a complete description refer to the OpenVMS v8.4 Software Product Description.
OpenVMS 8.4 supports an extensive range of Blades management tools based on HP corporate Systems insight Manager (SIM). A family of software providers enables system managers to interrogate components of Blades such as CPU, memory, Management Processor etc. Moreover, the provisioning feature delivers the ability to Load OpenVMS onto a blade with one click from inside the HP SIM GUI interface The rx2660, rx3600 and rx6600 Integrity systems also benefit from these new capabilities with this release.
The use of SIM (which is free) ensures a common management interface or 'pane of glass' to virtually every HP server, reducing management training effort and complexity.
For more information please read the white paper, HP OpenVMS on HP Integrity server blades for HP BladeSystem c-Class.
This capability is particularly effective and efficient in implementing consolidation initiatives.
OpenVMS version 8.4, like version 8.3-1H1 before it, simplifies software procurement, installation and management with pre-packaged Operating Environments (OEs). The OEs provide the most popular software products in packages that are simple to order, use, and maintain. Starting v8.4, the three-tier OE model which consists of FOE, EOE and MCOE is replaced with a two-tier OE model – BOE and HA-OE. Choose the OE that meets your business needs:
- OpenVMS Integrity server Base Operating Environment (BOE) delivers manageability and interoperability features. It is an Internet-ready, feature-rich solution for the price-sensitive customer. Customers have been requesting low-cost OpenVMS solutions for some time. With the new Base OE, OpenVMS computing is significantly more cost-effective.
- OpenVMS Integrity server High Availability Operating Environment (HA-OE) includes all the Base OE components, and adds features for the best possible performance, reliability, and availability. If uptime is all important to your business, this is the OE for you.
The complete description of OpenVMS v8.4 can be found in the Software Product Description document.
OpenVMS on HP Integrity server (BL8x0c i2 server blades and rx2800 i2 servers) is licensed per socket, i.e., Per Socket license (PSL). OpenVMS on HP Integrity servers software is licensed on a per core licensing (PCL) basis. PSL is priced based on the number of sockets on the system. PCL is a straightforward way to price software according to the number of processor cores on which it is running. PSL/PCL licensing is available for all OpenVMS Operating Environment software and for the majority of OpenVMS Layered Products. These methods of licensing software supports the granularity needed for virtualization.
Customers only need to purchase software and processors as necessary for their compute tasks. Our virtualization licensing policy lets customers pay for just the amount of computing resources they need and per socket licensing and per core licensing offers the necessary level of granularity. More processors and more per socket/per core licenses can easily be added later if needed.
8. What are the new flexible policies called iCAP, and TiCAP that are now available with HP OpenVMS version 8.4?
As part of its virtual server environment (VSE) HP has enabled the following two flexible licensing programs that are available in OpenVMS on HP Integrity servers with the release of OpenVMS version 8.4. By employing one or more of these capabilities (as appropriate) users may achieve both increased available headroom when needed and a reduced total cost of having that headroom readily accessible.
- Instant Capacity (iCAP) systems are purchased with at least one active and a number of deactivated iCAP CPUs that may be permanently turned on when required. The corresponding number of OpenVMS xOE licenses must be purchased at the appropriate time for all active CPUs.
- Temporary Instant Capacity (TiCAP) licenses temporarily activate iCAP CPUs for as long as the customer specifies. Upon activation the license for the OE installed on each TiCAP CPU is automatically granted.
Additional information on virtualization can be found at the white paper, Virtualization and HP OpenVMS.
Porting applications from VAX systems to HP Integrity servers will involve work similar to what would have been done to port applications from VAX systems to AlphaServer systems. Although the port of most VAX system applications to AlphaServer systems and now to HP Integrity servers is fairly straightforward, there are certain architectural differences in the platforms that require changes to the applications. The key areas with differences are data alignment, H_FLOAT data types, data granularity, page sizes, and exception handling. HP recommends that you refer to the Migrating an Application from OpenVMS VAX to OpenVMS Alpha book and apply the recommendations from that book as you port your applications from VAX systems to Integrity servers. In addition, HP recommends that you review the white paper, Making the transition from HP OpenVMS VAX to OpenVMS on HP Integrity servers.
A complete set of Transition Modules are available for use in transitioning applications to OpenVMS for HP Integrity servers from both AlphaServer and VAX systems.
HP Services stands ready to assist you in this endeavor.
In addition, please refer to FAQ#28 below for information on clustering VAX systems with HP Integrity servers for development purposes only.
There are now well over 1,000 ISV applications qualified and being sold for OpenVMS on HP integrity servers. In addition, many more are currently being ported, tested, and made ready for production use. Many of these are new to OpenVMS, thus extending the reach of HP OpenVMS.
Every day more applications are being ported to OpenVMS for HP Integrity servers. For the latest status please go to the HP OpenVMS Application Status Report.
We have a number of programs that are designed to help your application provider understand the value of porting to HP Integrity servers and for helping them to do so. HP strongly recommends that our customers work closely with their application providers to ensure that the application providers are fully aware of your needs and requirements with respect to porting their applications to OpenVMS for HP Integrity servers. If you have concerns about a particular software provider, please send us a note with "ISV CONCERN" in the subject line.
HP OpenVMS Rolling Roadmaps.
The roadmap is usually updated every three months. Generally, a new version of OpenVMS is released every 12 to 18 months.
12. Can I trade in my existing VAX system and AlphaServer system licenses for HP Integrity server licenses?We have introduced an exciting new Industry leadership cross-platform license trade-in policy. Customers may trade in their existing OpenVMS AlphaServer or VAX licenses toward the purchase of new OpenVMS on Integrity server licenses. For licenses under support (the product has rights to new versions under their support contract), they can be traded in for a new license for the equivalent product at no charge.
The customer must commit to continue support for the new licenses.
When a system is being traded in and the customer is setting up a new environment, HP allows a parallel usage period of the hardware. Parallel usage of software licenses is allowed for the period of time during which the customer migrates their environment. Information on license transfer can be found at Information and Policies for Alpha and VAX systems.
HP Services Web site.
14. Will all HP Layered Products for OpenVMS on AlphaServer systems be available on OpenVMS for HP Integrity servers?
Most OpenVMS layered products have been, or will shortly be ported to OpenVMS for Integrity servers. However, a small number of layered products are being retired or put into maintenance mode, and are not being ported to Integrity servers.
For a complete status list of all layered products, see the Software Public Rollout Reports for OpenVMS.
15. How do processors and cores compare performance-wise on AlphaServer systems versus HP Integrity servers with dual-core processors?
We have found that the HP Integrity servers with dual-core processors tend to perform considerably better than comparable AlphaServer systems.
However, as is the case with all performance comparisons, results will be highly dependent on application, workload, configuration, and other variables. HP recommends that you test your applications on a variety of appropriate HP Integrity servers and AlphaServer systems so that you will be better prepared to make the right choice.
For more detailed information, please refer to our performance comparison white paper, HP OpenVMS on HP AlphaServer and HP Integrity systems.
A wide variety of options exist for organizations that are seeking OpenVMS resources. HP Managed Services has a vast store of resources to assist you, whether you are looking for a single OpenVMS resident expert, full outsourcing, or something in between. In addition, a worldwide network of user groups that maintain lists of experts can be found through Encompass.
Hard Partitioning is available and behaves exactly like OpenVMS Alpha hard partitions.
Soft Partitioning as available with OpenVMS Alpha Galaxy is not currently available with OpenVMS 8.4 Integrity. This capability is available with the introduction of HP Integrity Virtual Machines (HPVM) on OpenVMS V8.4.
18. I ported my UNIX applications to OpenVMS. Will there be any difference when porting to OpenVMS on HP Integrity servers?
If you have already ported your UNIX application to OpenVMS on AlphaServer systems, moving it to OpenVMS on HP Integrity servers is straightforward and not likely to be any different than moving any other OpenVMS applications from AlphaServer systems to Integrity servers.
Inherent in OpenVMS for Integrity servers is the same UNIX portability capability that is available on OpenVMS for AlphaServer systems. UNIX applications can be ported to Integrity servers with essentially the same effort that would be required to move a UNIX application to OpenVMS AlphaServer systems.
We continue to enhance our UNIX portability capabilities with each new OpenVMS release.
No. AlphaServer systems and Integrity servers are different architectures. However, we have a broad variety of programs that are designed to help you make the transition when your plans call for doing so. At the same time, keep in mind that your current AlphaServer system and your new Integrity server will cluster together seamlessly, thus preserving and enhancing your investment.
20. How well will my applications perform on Integrity servers as compared with my AlphaServer system environment?
Recently, HP engineers ran tests to compare the performance of applications running on OpenVMS AlphaServer and OpenVMS Integrity server systems. In addition, customers are now testing their applications on HP Integrity servers running OpenVMS in the HP OpenVMS Customer Lab.
The results of these tests strongly indicate that OpenVMS users can obtain substantial performance improvements on the Integrity server platform. Moreover, as OpenVMS itself continues to undergo investment and enhancement, the changes in the operating system can also enhance application performance. These platform improvements-coupled with the price/performance benefits of Integrity systems and the proven high value of OpenVMS-provide a convincing argument for choosing these products for the next generation of your server infrastructure.
For more detailed information, please refer our performance comparison white paper, HP OpenVMS on HP AlphaServer and HP Integrity systems.
21. I don't have the source code for an application that is critical to my environment. Will a translator or emulator be available?
A binary translator is available to address this situation. The HP OpenVMS Migration Software for Alpha to Integrity Servers (OMSAIS) product converts AlphaServer system executables to Integrity server executable code. OMSAIS translates almost all user mode images. Although some manual conversion is usually required, most of the code is translated automatically. For more information, please visit the HP OMSAIS home page.
HP OMSAIS provides the following functionality:
- Translation of executables and shareable OpenVMS AlphaServer system images into functional equivalent images that run on Integrity servers.
- A run-time environment for translated image execution which also includes a way to run old code that was not discovered (or did not exist) at translate time. This run-time environment is packaged as an integral part of OpenVMS on Integrity servers.
- Open-ended translation of almost all user-mode images (including images created by DECmigrate) from the AlphaServer system to the Integrity server. The translated binary images execution environment contains a fallback interpreter for both AlphaServer system and VAX system code, which will also support optional reproduction of subtle old-architecture details.
- Supports interoperability between Integrity-native and translated images.
- Provides explicit messages that state reasons with code change recommendations where feasible if translation is not possible.
- Supports the following run-time libraries:
- DEC C/C++ runtime libraries for OpenVMS on AlphaServer systems
- VAX C runtime libraries for OpenVMS on VAX systems
- FORTRAN runtime libraries
- COBOL runtime libraries
- PASCAL runtime libraries
- Mathematical libraries
- Relevant system run-time libraries
HP OMSAIS limitations
HP OMSAIS applies the following restrictions to applications represented in AlphaServer system-native binary code that will be translated to code for Integrity servers:
- Only user-mode applications
- No privileged or undocumented AlphaServer system instructions
- No self-modifying or other dynamically generated code, which will be handled in simulator mode on the fallback interpreter for AlphaServer system code
- No system memory space reference
- No use of undocumented interfaces into the operating system
- No user-written system services
- No applications that use DECWindows/X-Windows graphical user interface will be supported
- No applications written in Ada or PL/1
22. I have non-IEEE floating point binary data stored on disk that will need to be accessed by my applications on HP Integrity servers. Since HP Integrity servers only support IEEE floating point operations, will I need to convert all of my data?
Compilers from HP support non-IEEE formats and will automatically convert the data as needed at runtime when applications are compiled using the appropriate floating point "switch." If performance is crucial you may want to convert all of your non-IEEE floating point data to IEEE in order to avoid the necessity for runtime conversion.
For more information, see the OpenVMS floating point white paper.
HP recommends that you convert your AlphaServer system assembler code to C. If you must write part of your application in Assembler you will need to convert your AlphaServer system assembler code to Integrity server assembler code.
24. Some of my applications are written in PL/1. Will they port to OpenVMS for HP Integrity servers?
HP no longer owns the PL/1 compiler, and therefore did not port the PL/1 compiler to the Intel® Itanium® processor family. HP recommends that customers and partners convert their applications from PL/1 to some other language if they wish to compile and execute those applications on the Itanium processor family. HP's Consulting and Integration Services organization can provide services for translating PL/1 applications to some other language.
Another possible option to run OpenVMS Alpha PL/1 based applications on Integrity is to use the Binary Translator (http://h71000.www7.hp.com/openvms/products/omsva/omsais.html) in combination with the Kednos Enterprises PLI_RTL_AV product. For information on this possible option, please see: http://www.kednos.com/
25. I currently run several 32-bit applications on VAX systems. Will there be any emulation mode to run VAX system applications on Integrity servers? If not, what is my solution? I prefer not to go fromVAX system code to AlphaServer system code and then to HP Integrity server code.
HP recommends that you first review our white paper, Making the transition from HP OpenVMS VAX to HP OpenVMS on Integrity servers.
You have two options for getting your VAX system code to Integrity servers:
- Port VAX system code directly to Integrity servers.
- Translate your code. (It is a two step process to translate the images, but it only has to be done one time.)
If you do not have the sources you can use HP OpenVMS Migration Software for VAX to Alpha Systems (OMSVA, also known as DECmigrate) to port to AlphaServer systems, and then use HP OMSAIS to port to Integrity servers. An AlphaServer system is only required to create an image that will be used with the binary translator. Therefore, your options to avoid purchasing an AlphaServer system just for this purpose are:
- Rent an AlphaServer system.
- Use one of the AlphaServer systems deployed elsewhere in your organization.
- Engage HP Services.
For more information about OMSVA, please visit the HP OMSVA home page.
If you have the sources and you want to port your VAX applications to Integrity servers, read Migrating an Application from OpenVMS on VAX systems to AlphaServer systems. Although this document does not address porting to Integrity servers, much of what was required to port an application from VAX systems to AlphaServer systems will also apply when porting an application from VAX systems to Integrity servers.
Please note, there is no requirement to convert a 32-bit application to 64-bit. 32-bit applications will run on OpenVMS on Integrity servers.
A complete set of Transition Modules are available for use in transitioning applications to OpenVMS for HP Integrity servers from both AlphaServer and VAX systems.
OpenVMS supports four threads interfaces: D4, 1C, CMA, and TIS. Although all four of these interfaces are supported on Integrity servers, we strongly recommend that you use the POSIX 1C interface as the other interfaces are provided for backward compatibility.
If you have written your own threading or context switching packages, HP recommends that you utilize the KP features available for OpenVMS on HP Integrity servers. For more information, see Documentation in presentation form for KP services as they apply to OpenVMS on Integrity servers.
OpenVMS fully supports mixed-architecture clusters for AlphaServer systems and Integrity servers.
Support of a VAX server with an Integrity server system in a mixed-architecture cluster (with or without AlphaServer systems included) is not a formally supported configuration for production environments. This type of configuration, however, can be used temporarily as an interim step for the purposes of development and migration, as applications are moved from VAX to either an AlphaServer or Integrity server platform. Should a problem arise while using this type of configuration, the customer will be advised to either revert back to their VAX-AlphaServer cluster environment, or remove the VAX from the cluster that contains Integrity server systems.
OpenVMS will also continue to support mixed-architecture clusters of VAX systems and AlphaServer systems.
28. How can HP help me to integrate HP Integrity servers into my current AlphaServer OpenVMS environment?
In general, this can be as straightforward as adding a new node to an already existing AlphaServer system cluster, except the node is an Integrity server. The current versions of HP OpenVMS support mixed-architecture clusters consisting of AlphaServer systems and Integrity servers.
Information on license transfer can be found at Information and Policies for Alpha and VAX systems.
Most applications will require only recompile, re-link, test, and go.
HP also has a variety of resources to assist you. As part of the Alpha RetainTrust program, HP provides a set of complementary services to help ensure that your transition occurs smoothly. For example, we and many of our business partners provide consulting services that offer various levels of depth and breadth of transition planning services. These services, such as Transition Consulting Workshops and Customer Consultancies include consultations with experts who can provide you with implementation guidance and recommendations specific to your environment and circumstance.
In addition, HP provides documentation in the form of guides, checklists, white papers, and more, to help with your planning efforts, as well as associated tools and methodologies to assist with your transition. Most of the tools can be found at the following URL:
29. Will all of the operating system features on which I've come to rely in OpenVMS for AlphaServer systems be available on HP Integrity servers?
YES. We have delivered a full port of the operating system beginning with version 8.2. Therefore, all of the features from clustering to security to UNIX portability to scalability, and more that were available on OpenVMS on AlphaServer systems prior to porting to HP Integrity servers, are available on HP Integrity servers.
Yes, HP has a comprehensive set of courses that start at the beginning and move towards advanced knowledge of OpenVMS. In particular, we offer two courses that cover the new versions of OpenVMS (Technical Updates and Internal Differences). For more information, see www.hp.com/learn/openvms.
Yes, HP has a comprehensive set of courses covering programming topics. These courses are typically offered in private classes according to customer demand. More information on the programming curriculum can be found on www.hp.com/learn/openvms. To request a private class, select your country from the drop-down menu and contact HP in your country.
HP is a top source for OpenVMS training because of our
- Deep knowledge—We develop OpenVMS, we design its functionality, and we control its evolution. As a result, you benefit from access to the best experts available.
- Timing— You have immediate access to the latest and greatest enhancements in OpenVMS.
- Experience—Twenty-five years of experience delivering high tech education and applying what we learn from the thousands of OpenVMS students we train annually.
- Classes specially designed for each member of your team—From novice to experienced veteran; from system administrator to application developer.
- Wide variety of training methods—Traditional instructor-led delivery at our education centers, your location, or using our online, remotely assisted instructor led (RAIL) training. We also offer customized learning solutions tailored to your particular needs.