| Previous | \Contents | ^Index |
A Encompass, the Enterprise Computing Association, is a user group F comprised of information technology professionals that are interested C in the Enterprise-oriented products, services, and technologies of D Compaq and of the former DIGITAL. Encompass offers newsletters, the G Encompass website, and offers various gatherings and related services, 9 including symposia events and local users group meetings.
B Encompass is a descendent of the organization known as DECUS, the ) Digital Equipment Computer Users Society.
G For more information on Encompass, please visit the Encompass web site:
H The organization comprised of customers of Hewlett-Packard Company (HP) A that is probably most analogous to the Encompass organization is Interex:
G Like Encompass, Interex offers various services and events of interest E to folks that presently work with and/or that wish to learn about HP C products and offerings. Please see the Interex website for details. f 1.5 OpenVMS Support, Questions and Comments?
B The following section includes contacts for OpenVMS Feedback, and ; information on how to obtain technical support information. S 1.5.1 Corporate contacts for OpenVMS Business Issues?
G The following folks are the HP corporate contacts for OpenVMS business H issues, listed in descending order from Carleton (Carly) Fiorina to the 7 Vice President of the OpenVMS Engineering organization:
A These folks will quite obviously respond best to cogently-worded = OpenVMS corporate-level business issues. These folks are not D appropriate contacts for technical support issues nor for technical ; support requests, nor for any other non-corporate-related, non-business-related issues. = 1.5.2 OpenVMS Ambassadors?
The OpenVMS Ambassadors H are senior HP engineers with advanced technical knowledge and advanced D training in OpenVMS, with detailed knowledge of current and future I OpenVMS releases and product plans, and with contacts directly with the G HP and ISV hardware and software engineering organizations developing I OpenVMS and OpenVMS hardware platforms, as well as layered products and I tools. Further, Ambassadors are experienced with integrating HP OpenVMS A and application-specific products and ISV applications to solve specific business requirements.
3 OpenVMS Ambassadors are based throughout the world.
E Your HP sales representative or HP reseller will be able connect you # with your local OpenVMS Ambassador. Z 1.5.3 Contact for OpenVMS Marketing Issues and Questions?
: Please see Section 3.5. S 1.5.4 Contact URLs for OpenVMS Technical Issues?
@ For technical issues and technical support, please contact your H software support organization, or your local HP Customer Support Center ? or HP Reseller. In North America, you can call 1-800-HP-INVENT.
E Please remember to review and to bookmark the following support URLs:
B OpenVMS, originally called VMS (Virtual Memory System), was first F conceived in 1976 as a new operating system for the then-new, 32-bit, H virtual memory line of computers, eventually named VAX (Virtual Address eXtension).
H The first VAX model, the 11/780, was code-named "Star", hence H the code name for the VMS operating system, "Starlet", a name ? that remains to this day the name for the system library files (STARLET.OLB, etc.).
H VMS version X0.5 was the first released to customers, in support of the D hardware beta test of the VAX-11/780, in 1977. VAX/VMS Version V1.0 ; shipped in 1978, along with the first revenue-ship 11/780s.
D OpenVMS was designed entirely within HP and specifically within the E former Digital Equipment Corporation (DIGITAL). Two of the principal A designers were Dave Cutler and Dick Hustvedt, though with a wide B variety of other contributors. OpenVMS was conceived as a 32-bit, A virtual memory successor to the RSX-11M operating system for the F PDP-11. Many of the original designers and programmers of OpenVMS had B worked previously on RSX-11M, and many concepts from RSX-11M were carried over to OpenVMS.
F OpenVMS VAX is a 32-bit, multitasking, multiprocessing virtual memory E operating system. Current implementations run on VAX systems from HP and other vendors.
G OpenVMS Alpha is a 64-bit multitasking, multiprocessing virtual memory H operating system. Current implementations run on Alpha systems from HP, and other vendors.
B OpenVMS has also been ported to the Intel IA-64 architecture, and D specifically to HP Integrity systems using microprocessors from the B Intel Itanium Processor Family. This implementation of OpenVMS is @ officially known as "HP OpenVMS for Integrity Servers" E and more commonly as "OpenVMS I64", and it operates in the F native Itanium IA-64 architecture and 64-bit environment. OpenVMS I64 B provides support for applications requiring 32- or 64-bit virtual B addressing capabilities entirely within the native 64-bit Itanium E execution environment. (For details on this and related terminology, ? please see Section 14.4.5.)
F For more details on OpenVMS and its features, please read the OpenVMS Software Product Description at:
B Additional information on the general features of various OpenVMS G releases, release dates, as well as the development project code names & of specific releases, is available at:
F Additional historical information---as well as pictures and a variety @ of other trivia---is available in the VAX 20th anniversary book:
H For information on the FreeVMS project, and on hobbyist and educational versions of OpenVMS, please see:
h Also please see the related software licensing topics Section 2.8.4, h Section 2.8.1, and Section 2.15. i 2.2 What is the difference between VMS and OpenVMS?
= VMS and OpenVMS are two names for the same operating system. F Originally, the operating system was called VAX-11/VMS; it changed to B VAX/VMS at around VAX/VMS V2.0. When the VMS operating system was G ported to the Alpha platform, it was renamed OpenVMS, for both VAX and E Alpha (and for the Itanium Processor Family), in part to signify the C high degree of support for industry standards such as POSIX, which ' provides many features of UNIX systems.
H For those versions with POSIX, an OpenVMS license allows you to install G and run POSIX for OpenVMS at no additional charge; all you need is the ? media and documentation which can be found on the Consolidated F Distribution and On-Line Documentation CD-ROMs. Support for the POSIX H package on more recent OpenVMS releases is not available, various parts G of POSIX such as calls from the API are being integrated more directly F into OpenVMS. For more information on POSIX for VMS see question SOFT2
H What became confusing is that the OpenVMS name was introduced first for G OpenVMS AXP V1.0 causing the widespread misimpression that OpenVMS was H for Alpha AXP only, while "regular VMS" was for VAX. In fact, F the official name of the VAX operating system was changed as of V5.5, G though the name did not start to be actually used in the product until V6.0. i 2.3 What's in a Name? Terminology and Products?
H The proper names for OpenVMS on the various platforms are "OpenVMS G VAX", "OpenVMS Alpha", and "OpenVMS I64". Use E of "OpenVMS AXP" and of "VAX/VMS" are deprecated.
F The VAX and Alpha terms are largely interchangeably used as the names E of platforms, of processor or microprocessor implementations, and of ' the respective computing architectures.
G Somewhat confusing to long-time OpenVMS users, Intel IA-32, IA-64, and F EM64T, and AMD AMD64 are the names of various computing architectures F and of architectural extensions. Only. These are not the names of any & implementations, nor of any platforms.
Intel Itanium H is the name of a family of microprocessor implementations of the Intel I IA-64 architecture, as Intel Pentium and Xeon are the names of families G of microprocessor implementations of Intel IA-32 and (potentially) of the EM64T extensions.
I64 1 is the generic name for the various HP Integrity C platforms supported by HP OpenVMS for Integrity Servers (and more F commonly as "OpenVMS I64"); for the platforms supported by > OpenVMS I64. (For additional related terminology, please see 5 Section 14.4.5.) D 2.3.1 How do I port from VMS to OpenVMS?
i You already did. Wasn't that easy? Please see Section 2.2 for details. [ 2.4 Which is better, OpenVMS or UNIX?
F This question comes up periodically, usually asked by new subscribers F amd new posters who are long-time UNIX or Linux users. Sometimes, the G question is ignored totally; other times, it leads to a long series of E repetitive messages that convince no one and usually carry little if F any new information. Please do everyone a favor and avoid re-starting ! this perpetual, fruitless debate.
G That said, OpenVMS and the better implementations of UNIX are all fine H operating systems, each with its strengths and weaknesses. If you're in H a position where you need to choose, select the one that best fits your G own requirements, considering, for example, whether or not the layered = products or specific OS features you want are available, and D considering the expected cost-of-ownership over the lifetime of the system installation. k 2.5 Is HP continuing funding and support for OpenVMS?
Yes.
G Active development of new OpenVMS releases is underway, as well as the continuation of support.
A Please see the following URLs for details, roadmaps, and related information:
g$ Various distributions are available.
C For the most current information on the available part numbers and H current products (OpenVMS distribution kits, media, documentation, etc) F and the most current associated licensing information, please see the G current OpenVMS Software Product Description (SPD) document, available at:
j The CD-ROMs listed in Table 2-1 contain just the OpenVMS Alpha G operating system. The operating system distribution kits are bootable, A and can be used to run BACKUP from the optical media, as well as * performing an installation or upgrade.
| Part | &Description |
|---|---|
| QA-MT1AG-H8 | D OpenVMS Alpha V6.2-1H3 hardware release CD-ROM; also requires QA-MT1AA-H8.6.2 |
| QA-MT1AR-H8 | 5 OpenVMS Alpha V7.1-2 maintenance release CD-ROM |
| QA-MT1AT-H8 | 5 OpenVMS Alpha V7.2-1 maintenance release CD-ROM |
| QA-MT1AU-H8 | 5 OpenVMS Alpha V7.2-2 maintenance release CD-ROM |
| QA-MT3AA-H8 | @ OpenVMS Alpha and VAX products and documentation on CD-ROM |
| QA-MT3AE-H8 | 3 OpenVMS Alpha and VAX documentation on CD-ROM |
F OpenVMS I64 is distributed on DVD-ROM media, and is bootable. OpenVMS G I64 licensing is implemented on a per-processor-socket basis, with the E classic license tiers based on the numbers of processor sockets that G can be present. Further, three general product and licensing groupings D are optionally available with OpenVMS I64, the Foundation Operating C Environment (FOE), the Enterprise Operating Environment (EOE), and B (as/when/if available) the Mission Critical Operating Environment (MCOE). G Seperate per-product licenses are generally also available for various < of the products within the Operating Environment groups.
| Part | &Description |
|---|---|
| BA322AA#??? | OpenVMS I64 FOE Product |
| BA323AA#??? | OpenVMS I64 EOE Product |
| BA324AA#??? | OpenVMS I64 MCOE Product |
< The product suffix required for the order numbers listed in Table 2-2 can be found in Table 2-3.
| Suffix | &Description |
|---|---|
| A18 | $ OpenVMS I64 FOE V8.2 DVD media |
| AJR | OE media kit on DVD media |
| 0D1 | Factory installation |
H The OpenVMS VAX and OpenVMS Alpha source listings CD-ROM sets listed in u Table 2-4 include the source listings of most of OpenVMS, and these G CD-ROM sets are invaluable for any folks working directly with OpenVMS E internals, as well as folks interested in seeing examples of various programming interfaces.
| Part | &Description |
|---|---|
| QB-MT1AB-E8 | 3 OpenVMS Alpha Source Listings kit and license |
| QT-MT1AB-Q8 | + OpenVMS Alpha Source Listings Updates |
| QB-001AB-E8 | 1 OpenVMS VAX Source Listings kit and license |
| QT-001AB-Q8 | ) OpenVMS VAX Source Listings Updates |
| BA422AA | 1 OpenVMS I64 source listings kit and license |
F Additional OpenVMS packages and technologies including NetBeans, XML, " SOAP, UDDI, JDK, Perl, Tomcat, SSL D and such are discussed within the OpenVMS e-Business Infrastructure Package SPD 80.58.xx. @ Again, please see the OpenVMS SPD and the documents and parts 4 referenced there for the most current information. ` 2.6.1 Where can I download OpenVMS and Layered Product Kits?
@ HP customers with commercial licenses and support contracts can B download software product distribution kits from the following HP website:
E You can also find pointers to the Software Rollout Report and to the / OpenVMS SPD listings via the above SQP website.
B Information on obtaining and transfering licenses is available in † Section 2.6 and Section 2.8.4, while information on the OpenVMS = Hobbyist licensing program and on obtaining hobbyist product J distribution kits is in Section 2.8.1. ^ 2.7 In what language is OpenVMS written?
2 OpenVMS is written in a wide variety of languages.
H In no particular order, OpenVMS components are implemented using Bliss, A Macro, Ada, PLI, VAX and DEC C, Fortran, UIL, VAX and Alpha SDL, H Pascal, MDL, DEC C++, DCL, Message, and Document. And this is certainly H not a complete list. However, the rumor is NOT true that an attempt was H made to write pieces of OpenVMS in every supported language so that the F Run-Time Libraries could not be unbundled. (APL, BASIC, COBOL and RPG 0 are just some of the languages NOT represented!)
B There are a large variety of small and not-so-small tools and DCL E command procedures that are used as part of the OpenVMS build, and a A source code control system capable of maintaining over a hundred E thousand source files across multiple parallel development projects, and overlapping releases. l 2.8 Obtaining and Transfering OpenVMS licenses?
A The following sections describe hobbyist and educational license F programs, as well as information on commercial licenses and transfers.
E For information on the available commercial OpenVMS licenses and for g information on license transfers, please see Section 2.8.4. OpenVMS m Hobbyist licenses are discussed in Section 2.8.1. For information on the E licensing implementation, troubleshooting licensing problems, on the C License Unit Requirements Table (LURT), and other related details, k please see Section 5.39. For configuring and troubleshooting LMF, see 2 Section 12.5. Q 2.8.1 Questions asked by Hobbyist OpenVMS licensees?
C If you are a member of an HP-recognized user group (eg: Encompass, F Enterex, DECUS), and are considering acquiring and using a VAX, Alpha A or (soon) IA-64 system for hobbyist (non-commercial) use, (free) C license product authorization keys (PAKs) for OpenVMS VAX, OpenVMS > Alpha, (soon) OpenVMS I64, and layered products are available.
D In addition to the license keys, OpenVMS VAX and Alpha distribution G CD-ROM distribution kits are available with OpenVMS, DECwindows Motif, B DECnet and TCP/IP networking, compilers, and a variety of layered H products. (A hobbyist distribution for OpenVMS I64 is expected.) (While D the hobbyist CD-ROM distributions are intended for and tailored for A OpenVMS Hobbyists, the contents and capabilities of the Hobbyist G installation kits included within the OpenVMS Hobbyist distribution do A not differ from the standard distribution installation kits. The G products are chosen to reflect the most popular products and the space available on the media.)
@ If you have questions on what else is authorized by the license D agreement and on what other distribution media is available to you, ? well, please read the applicable software license agreement(s).
( For further information, please link to:
G On the OpenVMS Hobbyist license registration form at the above website E (as of August 2004), you are offered the choice of the "OpenVMS H VAX" license(s), the "OpenVMS Alpha" license(s), and the C "Layered Products" licenses. You will want the operating E system license for your particular OpenVMS platform and you F will want the "Layered Products" licenses. You will want to 8 select and to acquire two sets of license PAKs.
F For vendors wishing to license products specifically for hobbyist use F (and to not issue hobbyist PAKs), the program provides hobbyists with ! the license PAK OPENVMS-HOBBYIST.
? If you plan to use a hardware emulator (eg: VAX emulator) on a G Microsoft Windows platform, make sure you have an OpenVMS distribution E kit that can be installed and/or booted with the particular emulator B package you plan to use. For additional information on emulators, _ please see Section 13.14 and particularly please see the emulator-related documentation. J 2.8.2 OpenVMS Educational and CSLG licenses?
F For information on OpenVMS licenses for educational customers, please H see the HP Campus Software License Grant (CSLG) license program and the $ OpenVMS Educational license program:
bE Commercial software developers can join the HP DSPP program, and can E (potentially) receive discounts on various software product licenses = and software distributions, as well as on hardware purchases.
H The DSPP program is the descendent of the DIGITAL ISVN and DIGITAL ASAP E programs and the Compaq CSA program, and the analogous developer and partner programs at HP.
g Please see Section 2.15 for additional details on the DSPP program.
A For information on the OpenbVMS Hobbyist and OpenVMS Educational O license programs, please see Section 2.8.1. Q 2.8.4 How do I obtain or transfer an OpenVMS license?
G To transfer a commercial OpenVMS license from one owner to another, or G to purchase a commercial license, you can contact HP at regional sales office or reseller.
< For information on the hobbyist license program, please see 2 Section 2.8.1.
| Previous | YNext | \Contents | ^Index |