=;The OpenVMS Frequently Asked Questions (FAQ)D

The OpenVMS Frequently Asked Questions (FAQ)



 o \ ^  
PreviousContentsIndex

e

1.4 What OpenVMS user group(s) are available?



AEncompass, the Enterprise Computing Association, is a user group Fcomprised of information technology professionals that are interested Cin the Enterprise-oriented products, services, and technologies of DCompaq and of the former DIGITAL. Encompass offers newsletters, the GEncompass website, and offers various gatherings and related services, 9including symposia events and local users group meetings.

BEncompass is a descendent of the organization known as DECUS, the )Digital Equipment Computer Users Society.

GFor more information on Encompass, please visit the Encompass web site:



HThe organization comprised of customers of Hewlett-Packard Company (HP) Athat is probably most analogous to the Encompass organization is Interex:



GLike Encompass, Interex offers various services and events of interest Eto folks that presently work with and/or that wish to learn about HP Cproducts and offerings. Please see the Interex website for details.f

1.5 OpenVMS Support, Questions and Comments?



BThe 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?



EThe HP corporate contact for OpenVMS business issues is Ann McQuaid, Athe HP General Manager directly in charge of OpenVMS and OpenVMS HEngineering, while feature requests and other related matters should be 9routed to MaryJane Vazquez, the OpenVMS Business Manager.

FAnn and MaryJane will quite obviously respond best to cogently-worded BOpenVMS corporate-level business issues or requests. With all due Brespect to all involved, neither Ann nor MaryJane are appropriate Acontacts for technical support matters nor for technical support Hrequests, nor for any other non-corporate-related, non-business-related Bissues---these questions are best routed to the local or regional Ccustomer support center; to the support, technical and engineering teams.

FTo reach Ann or MaryJane via electronic mail, place a dot between the =first and the surname, and append the expected HP.COM domain.=

1.5.2 OpenVMS Ambassadors?



The OpenVMS AmbassadorsH 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.

3OpenVMS Ambassadors are based throughout the world.

EYour 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.4.S

1.5.4 Contact URLs for OpenVMS Technical Issues?



GFor formal technical issues and technical support, please contact your Hsoftware support organization, or your local HP Customer Support Center ?or HP Reseller. In North America, you can call 1-800-HP-INVENT.

qFor informal (free) support resources, see the newsgroups including comp.os.vms (news://comp.os.vms/ ¤), see the ITRC discussion forums, the James support database search engine (search assistant tool) ( 6http://www2.itrc.hp.com/service/james/CPQhome.do D), and see sections of this document including the platform support winformation in Section 14.4, sources of software and hardware support in fSection 14.15, information on third-party devices and unsupported mhardware in Section 14.25, and the many other sections of this document.

EPlease remember to review and to bookmark the following support URLs:




C

Chapter 2
General Information


A

If you are searching for something here, please (consider using the text-format FAQ.

`

2.1 What is OpenVMS? What is its history?



BOpenVMS, originally called VMS (Virtual Memory System), was first Fconceived in 1976 as a new operating system for the then-new, 32-bit, Hvirtual memory line of computers, eventually named VAX (Virtual Address eXtension).

HThe first VAX model, the 11/780, was code-named "Star", hence Hthe 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.).

HVMS version X0.5 was the first released to customers, in support of the Dhardware 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.

DOpenVMS was designed entirely within HP and specifically within the Eformer Digital Equipment Corporation (DIGITAL). Two of the principal Adesigners were Dave Cutler and Dick Hustvedt, though with a wide Bvariety of other contributors. OpenVMS was conceived as a 32-bit, Avirtual memory successor to the RSX-11M operating system for the FPDP-11. Many of the original designers and programmers of OpenVMS had Bworked previously on RSX-11M, and many concepts from RSX-11M were carried over to OpenVMS.

FOpenVMS VAX is a 32-bit, multitasking, multiprocessing virtual memory Eoperating system. Current implementations run on VAX systems from HP Dand other vendors, as well as on hardware emulators; for additional \information on emulators, please see Section 13.12 and

GOpenVMS Alpha is a 64-bit multitasking, multiprocessing virtual memory Hoperating system. Current implementations run on Alpha systems from HP, and other vendors.

BOpenVMS has also been ported to the Intel IA-64 architecture, and Dspecifically to HP Integrity systems using microprocessors from the BIntel Itanium Processor Family. This implementation of OpenVMS is @officially known as "HP OpenVMS for Integrity Servers"Eand more commonly as "OpenVMS I64", and it operates in the Fnative Itanium IA-64 architecture and 64-bit environment. OpenVMS I64 Bprovides support for applications requiring 32- or 64-bit virtual Baddressing capabilities entirely within the native 64-bit Itanium Eexecution environment. (For details on this and related terminology, ?please see Section 14.4.5.)

FFor more details on OpenVMS and its features, please read the OpenVMS Software Product Description at:



BAdditional information on the general features of various OpenVMS Greleases, release dates, as well as the development project code names &of specific releases, is available at:



FAdditional historical information---as well as pictures and a variety @of other trivia---is available in the VAX 20th anniversary book:



;For information on the FreeVMS project, and on hobbyist and- educational versions of OpenVMS, please see:



hAlso please see the related software licensing topics Section 2.8.4, ˆSection 2.8.1, and Section 2.15, and (for developers working on Zcommercial applications for OpenVMS) Section 2.8.3.i

2.2 What is the difference between VMS and OpenVMS?



=VMS and OpenVMS are two names for the same operating system. FOriginally, the operating system was called VAX-11/VMS; it changed to BVAX/VMS at around VAX/VMS V2.0. When the VMS operating system was Gported to the Alpha platform, it was renamed OpenVMS, for both VAX and EAlpha (and for the Itanium Processor Family), in part to signify the Chigh degree of support for industry standards such as POSIX, which 'provides many features of UNIX systems.

HFor those versions with POSIX, an OpenVMS license allows you to install Gand run POSIX for OpenVMS at no additional charge; all you need is the ?media and documentation which can be found on the Consolidated FDistribution and On-Line Documentation CD-ROMs. Support for the POSIX Hpackage on more recent OpenVMS releases is not available, various parts Gof POSIX such as calls from the API are being integrated more directly Finto OpenVMS. For more information on POSIX for VMS see question SOFT2

HWhat became confusing is that the OpenVMS name was introduced first for GOpenVMS AXP V1.0 causing the widespread misimpression that OpenVMS was Hfor Alpha AXP only, while "regular VMS" was for VAX. In fact, Fthe official name of the VAX operating system was changed as of V5.5, Gthough 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?



HThe proper names for OpenVMS on the various platforms are "OpenVMS GVAX", "OpenVMS Alpha", and "OpenVMS I64". Use Eof "OpenVMS AXP" and of "VAX/VMS" are deprecated.

FThe VAX and Alpha terms are largely interchangeably used as the names Eof platforms, of processor or microprocessor implementations, and of 'the respective computing architectures.

GSomewhat confusing to long-time OpenVMS users, Intel IA-32, IA-64, and FEM64T, and AMD AMD64 are the names of various computing architectures Fand of architectural extensions. Only. These are not the names of any &implementations, nor of any platforms.

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

I641 is the generic name for the various HP IntegrityC 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?



iYou already did. Wasn't that easy? Please see Section 2.2 for details.[

2.4 Which is better, OpenVMS or UNIX?



FThis question comes up periodically, usually asked by new subscribers Fand new posters who are long-time UNIX or Linux users. Sometimes, the Gquestion is ignored totally; other times, it leads to a long series of Erepetitive messages that convince no one and usually carry little if Fany new information. Please do everyone a favor and avoid re-starting !this perpetual, fruitless debate.

GThat said, OpenVMS and the better implementations of UNIX are all fine Hoperating systems, each with its strengths and weaknesses. If you're in Ha position where you need to choose, select the one that best fits your Gown requirements, considering, for example, whether or not the layered =products or specific OS features you want are available, and Dconsidering the expected cost-of-ownership over the lifetime of the system installation.

GIf you are asking this question, you are probably comparing OpenVMS to BUNIX. It was once certainly true that OpenVMS and UNIX were quite Gdifferent. In more recent times, there are tools and C APIs on OpenVMS Gthat directly provide or that easily support porting UNIX programs and Ecommands, and there are equivalent packages bringing various OpenVMS *features and mechanisms to UNIX platforms.

EIf you seek UNIX tools on OpenVMS rather than the more philosophical Gdiscussion found in this section, please see the GNV package and other lGNU discussions in Section 13.2.6, and please see the plethora of C calls Hcurrently available in the HP C Run-Time Library documentation, briefly Adiscussed over in Section 13.2.1.k

2.5 Is HP continuing funding and support for OpenVMS?



Yes.

GActive development of new OpenVMS releases is underway, as well as the continuation of support.

APlease see the following URLs for details, roadmaps, and related information:

g

2.6 What OpenVMS distribution kits are available?



$Various distributions are available.

CFor the most current information on the available part numbers and Hcurrent products (OpenVMS distribution kits, media, documentation, etc) Fand the most current associated licensing information, please see the Gcurrent OpenVMS Software Product Description (SPD) document, available at:



jThe CD-ROMs listed in Table 2-1 contain just the OpenVMS Alpha Goperating system. The operating system distribution kits are bootable, Aand can be used to run BACKUP from the optical media, as well as *performing an installation or upgrade.

c   &                          
Table 2-1 OpenVMS Alpha Media Kits
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


FOpenVMS I64 is distributed on DVD-ROM media, and is bootable. OpenVMS GI64 licensing is implemented on a per-processor-socket basis, with the Eclassic license tiers based on the numbers of processor sockets that Gcan be present. Further, three general product and licensing groupings Dare optionally available with OpenVMS I64, the Foundation Operating CEnvironment (FOE), the Enterprise Operating Environment (EOE), and B(as/when/if available) the Mission Critical Operating Environment (MCOE).GSeperate per-product licenses are generally also available for various <of the products within the Operating Environment groups.

d   &              
Table 2-2 OpenVMS I64 Order Numbers
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.

d  ! &              
Table 2-3 OpenVMS I64 Media Suffix
Suffix Description
A18 $ OpenVMS I64 FOE V8.2 DVD media
AJR  OE media kit on DVD media
0D1  Factory installation


DThe OpenVMS VAX, OpenVMS Alpha and OpenVMS I64 source listings sets preferenced in Table 2-4 include the source listings of most of EOpenVMS, and these machine-readable distributions are invaluable for Hany folks working directly with OpenVMS internals, as well as for folks =interested in seeing examples of various OpenVMS programming interfaces.

m   &                          
Table 2-4 OpenVMS Source Listings Kits
Part Description
 QB-MT1AB-E8 3 OpenVMS Alpha Source Listings kit and license
 QT-MT1AB-Q8 + OpenVMS Alpha Source Listings Updates
BA422AA 1 OpenVMS I64 Source Listings kit and license
 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


FAdditional OpenVMS packages and technologies including NetBeans, XML, "SOAP, UDDI, JDK, Perl, Tomcat, SSLDand 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.

HFor information on non-commercial software distributions for use by and Tfor OpenVMS Hobbyists, please see Section 2.8.1.`

2.6.1 Where can I download OpenVMS and Layered Product Kits?



@HP customers with commercial licenses and support contracts can Bdownload software product distribution kits from the following HP website:



EYou can also find pointers to the Software Rollout Report and to the /OpenVMS SPD listings via the above SQP website.

BInformation 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 Jdistribution kits is in Section 2.8.1.^

2.7 In what language is OpenVMS written?



2OpenVMS is written in a wide variety of languages.

HIn no particular order, OpenVMS components are implemented using Bliss, AMacro, Ada, PLI, VAX and DEC C, Fortran, UIL, VAX and Alpha SDL, HPascal, MDL, DEC C++, DCL, Message, and Document. And this is certainly Hnot a complete list. However, the rumor is NOT true that an attempt was Hmade to write pieces of OpenVMS in every supported language so that the FRun-Time Libraries could not be unbundled. (APL, BASIC, COBOL and RPG 0are just some of the languages NOT represented!)

BThere are a large variety of small and not-so-small tools and DCL Ecommand procedures that are used as part of the OpenVMS build, and a Asource code control system capable of maintaining over a hundred Ethousand source files across multiple parallel development projects, and overlapping releases.l

2.8 Obtaining and Transfering OpenVMS licenses?



AThe following sections describe hobbyist and educational license Fprograms, as well as information on commercial licenses and transfers.

EFor information on the available commercial OpenVMS licenses and for ginformation on license transfers, please see Section 2.8.4. OpenVMS mHobbyist licenses are discussed in Section 2.8.1. For information on the Elicensing implementation, troubleshooting licensing problems, on the CLicense Unit Requirements Table (LURT), and other related details, kplease see Section 5.39. For configuring and troubleshooting LMF, see 2Section 12.4.Q

2.8.1 Questions asked by Hobbyist OpenVMS licensees?



CIf you are a member of an HP-recognized user group (eg: Encompass, FEnterex, DECUS), and are considering acquiring and using a VAX, Alpha Aor (soon) IA-64 system for hobbyist (non-commercial) use, (free) Clicense product authorization keys (PAKs) for OpenVMS VAX, OpenVMS HAlpha, and (reportedly) OpenVMS I64, and layered products are available.

DIn addition to the license keys, OpenVMS VAX and Alpha distribution GCD-ROM distribution kits are available with OpenVMS, DECwindows Motif, BDECnet and TCP/IP networking, compilers, and a variety of layered Hproducts. (A hobbyist distribution for OpenVMS I64 is expected.) (While Dthe hobbyist CD-ROM distributions are intended for and tailored for AOpenVMS Hobbyists, the contents and capabilities of the Hobbyist Ginstallation kits included within the OpenVMS Hobbyist distribution do Anot differ from the standard distribution installation kits. The Gproducts 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 Dagreement 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:



GOn the OpenVMS Hobbyist license registration form at the above website E(as of August 2005), you are offered the choice of the "OpenVMS HVAX" license(s), the "OpenVMS Alpha" license(s), and the C"Layered Products" licenses. You will want the operating Esystem license for your particular OpenVMS platform and you Fwill want the "Layered Products" licenses. You will want to 8select and to acquire two sets of license PAKs.

FFor 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 GMicrosoft Windows platform, make sure you have an OpenVMS distribution Ekit that can be installed and/or booted with the particular emulator Bpackage you plan to use. For additional information on emulators, _please see Section 13.12 and particularly please see the emulator-related documentation.




 o Y \ ^  
PreviousNextContentsIndex