G This document contains answers to many common questions on the OpenVMS F operating system, and covers OpenVMS, and OpenVMS running on Itanium, Alpha, and VAX hardware.
C This document is available in various formats, and the text-format > version of this FAQ is generally the easiest format to search.
, Revision/Update Information OpenVMS V8.2
. Revision/Update Information: Revision Date/January 2005
| @ Contents | 4: Index |
E This is the OpenVMS Frequently Asked Questions (FAQ) posting for the / comp.os.vms and comp.sys.dec usenet newsgroups.
ˆ Please send your suggestions for changes, additions, or corrections directly to FAQ Editor |
n Please do not send technical questions to the FAQ Editor > . The FAQ Editor B is not in a position to answer general questions, nor to G provide general product support. Rather, please post your questions to E the appropriate newsgroup, or please contact your preferred hardware 1 and/or software support organization(s) directly. A Your understanding in this matter is greatly appreciated. |
If you believe any particular discussion worthy of inclusion in a future edition of the FAQ and particularly once you have or know both the question and the answer, please then send the entire discussion along to the FAQ Editor for potential inclusion.
H Do note that the FAQ Editor g takes URL link continuity seriously, and strives to maintain current links. This is, however, a large task, and it is only becoming more difficult. URL link continuity is also something that you can assist with, of course. If you should find a dead link or a stale URL pointer, please notify the FAQ Editor œ . If you have or can find the current, correct or updated URL, of course, that greatly assists the FAQ Editor . in maintaining the most current set of links.
Thank you!
g Please consider reading Section 1.3 before posting to the comp.os.vms E or any other newsgroups. (What you post can come back to haunt you.) |
yMany people have contributed to this FAQ, directly and/or indirectly. In many cases, part or all of an answer included in the FAQ has been adapted from one or more postings from the comp.os.vms or other newsgroup---this though individual citations and specific quotations are generally not included in this FAQ. (The FAQ Editor > wishes to thank to all of those folks who post answers to the C newsgroups, and that have contributed to the contents of this FAQ.)
G The following is an incomplete list of the folks that have contributed F directly or indirectly to the contents of the OpenVMS FAQ. Additions, A corrections, and updates to this list of contributors and to the > contents of the FAQ itself are welcome, and all omissions and C misspellings are unintentional. Thanks to each of the contributors G here, and to all of the folks that have participated in the FAQ and in the newsgroups.
D Paul Anderson, Jason Armistead, Zoltan Arpadffy, John AtoZ, Bailey, B Jeremy Begg, Colin Blake, Ken Blaylock, Kenneth Block, Bol, Craig B Berry, Mark Berryman, Jim Becker, Verell Boaen, Bol, Jim Brankin, A Richard Brodie, Robert Alan Byer, Jeff Campbell, Scott Campbell, H Antonio Carlini, Keith Cayemberg, Ken Chaney, Cristy, John Croll, David F J. Dachtera, Robert Deininger, Dale Dellutri, Leo Demers, Sue Denham, C Thomas Dickey, Eric Dittman, Jim Dunham, Eric, Glenn Everhart, Ken C Fairfield, Yaacov Fenster, Gunther Froehlin, Harry Garonzik, Derek D Garson, John Gillings, Andy Goldstein, Clair Grant, Hunter Goatley, A Ruth Goldenberg, Vance Haemmerle, Ki Suk Hahn, SHarris, Fletcher G Hearns, Phillip Helbig, Hein van den Heuvel, Stephen Hoffman, Eberhard F Heuser-Hofmann, Sue Holt, Horn, Jaf, Leif Jansson, Kevin Jenkins, Don G Jones, Henry Juengst, inazu_k, Geoff Kingsmill, Fred Kleinsorge, Felix F Kreisel, Veli Korkko, Ruslan R. Laishev, Norm Lastovica, p_lee, Jerry G Leichter, Richard Levitte, Steve Lionel, Kerry Main, John E. Malmberg, H David Mathog, Dale Miller, Dick Munroe, Patrick Moreau, Morrison, otis, A George Pagliarulo, Keith Parris, Plass, pvhp, David Rabahy, Stan B Rabinowitz, Mike Raspuzzi, Steve Reece, Ian Ring, Aaron Sakovich, C Warren Sander, Mark Schafer, Brian Schenkenberger, Atlant Schmidt, B Wayne Sewell, Steven Shamlian, Sue Skonetski, Scott Snadow, Scott G Squires, stfp, Dave Sweeney, Mike Thompson, Arne Vajhøj, Martin E Vorländer, Peter Weaver, William Webb, Williams, Paul Winalski, Uwe Zinser.
© Again, any omission from this list and any errors or misspellings are entirely unintentional. Please notify the FAQ Editor F of any omissions, corrections, or updates that might be needed within H this list. And thanks to each of these individuals for their assistance @ and for their contributions, and particularly for sharing their expertise. A
B The OpenVMS FAQ is archived in (at least) the following locations:
? Other internet FAQs are generally available in these locations:
G This FAQ is available in ASCII text, Postscript, Bookreader, and HTML, D and potentially in other file formats. Certain formats, such as the F Adobe Acrobat PDF conversion from the Postscript format, are provided > downstream from the FAQ text formatting, and are provided and maintained by others.
As the HTML-format FAQ is not a single monolithic (and accordingly large) HTML file, it is the most difficult format to search using the most common standard (platform-local) tools. Accordingly, the FAQ Editor F recommends downloading, using and searching the ASCII text FAQ format.
E The OpenVMS FAQ is maintained in DECdocument SDML format and all FAQ ? maintenance and the primary output file format conversions are A performed on OpenVMS systems. For information on the DECdocument + product, please contact Touch Technologies. >
D For the folks that are familiar with older editions of this FAQ and @ specifically for those folks looking for the older section name F keywords, please see the index entries located under FAQ Sections F (Old). These older section names include the prefixes DCL, DECW, H DOC, FILES, MISC, MGMT, INTRO, SOFT, VMS, etc., followed by the section number. 1
D Corrections and suggestions are welcome. Should you believe you can B provide better stewardship of this FAQ, or should you have strong H feelings over the content, structure, organization or implementation of B the FAQ, do realize you may be offered the editorship. The editor C maintains this document as a free service to the OpenVMS community.
E While the information contained here is believed correct, the use of G any and all information acquired from this document is entirely at the E risk of the user(s). If your system should crash or your data should H become corrupted or the answer(s) found here should be found erroneous, 1 that is solely your risk and your responsibility.
H Though the editor of this FAQ is an employee of Hewlett-Packard Company H (HP), this posting and the information contained within this FAQ are is = not an official statement of HP, nor a commitment by HP. All ? information, comments or opinions included, cited or otherwise E referenced here may or may not reflect the stated opinions of HP, of # the editor, or of any other entity.
All trademarks, registered trademarks, servicemarks and registered servicemarks used or referenced here are the properties of their respective owner(s) or holders. Please route any corrections, requests or related updates to the FAQ Editor
E The redistribution, reposting and/or the web-serving of complete and D unaltered copies of this FAQ document is permitted. Other uses only with prior permission.
( The master copy of this FAQ is posted at
B Translations of this FAQ into various languages may be available, @ please contact the maintainer(s) of any translated document for F assistance or feedback involving the particular translated edition of this FAQ.
ª If you have no other OpenVMS URLs bookmarked, you will want to be familiar with the URLs listed in Table 1-1:
| URL | #Contents |
|---|---|
| H Core OpenVMS Information, including roadmaps and release schedules | |
| L http://www.hp.com/go/openvms/ | |
| 4 OpenVMS and Core Layered Product Documentation | |
| 3 ' http://www.hp.com/go/openvms/doc/ | |
| = Core OpenVMS Support Search Engine URLs, FTP Patch Area | |
| J http://askq.compaq.com/ (Natural Language Search Assistant) | |
| @ http://www.itrc.hp.com/ | |
| 8 , ftp://ftp.itrc.hp.com/openvms_patches/ | |
| The OpenVMS Freeware | |
| 8 , http://www.hp.com/go/openvms/freeware/ | |
| * The OpenVMS Hobbyist License Program | |
| 1 % http://www.openvmshobbyist.org/ | |
¼ There are a huge number of newsgroups available, some of which discuss topics of interest to folks using OpenVMS operating system. Key among these are the comp.os.vms 3 newsgroup and the vmsnet.* heirarchy of newsgroups. S 1.2.1 What is the scope of the comp.os.vms newsgroup?
" The comp.os.vms —newsgroup is the primary newsgroup for discussion of the HP OpenVMS operating system and the computer systems on which it runs. Questions about layered products which run on OpenVMS are also welcome, though many of them (in particular, language compilers and database systems) have more specific newsgroups. If a question has some relationship to OpenVMS, it belongs in comp.os.vms. R 1.2.2 What newsgroups carry VMS-related information?
@ The vmsnet.* hierarchy is operated by the Encompass users group H (formerly known as DECUS), and contains various newsgroups of interest, ' including vmsnet.misc and vmsnet.alpha.
F Sprechen Sie Deutsch? Besuchen Sie bitte den newsgroup de.comp.os.vms.
H The comp.sys.dec newsgroup carries general discussions about various HP G computer systems, and specifically systems that were acquired by HP as E part of the acquisition of Compaq, systems which had previously been C acquired by Compaq as part of the acquisition of Digital Equipment Corporation (DIGITAL).
B Also of interest are resources and conferencing systems including F Encompasserve (formerly known as DECUServe), Ken Farmer's OpenVMS.Org forums, # and the Compaq Working Group folks:
J' Extensive archives of INFO-VAX mailings " and comp.os.vms & postings are archived and available at / SRI: # ftp://crvax.sri.com/info-vax/
Google 3 also has extensive newsgroup archives available at
Fc INFO-VAX is a mailing list which is bidirectionally gatewayed to the comp.os.vms F newsgroup. This means that postings to comp.os.vms ‘ get automatically sent to INFO-VAX subscribers and messages sent to the INFO-VAX list are automatically posted to comp.os.vms. D INFO-VAX can be a useful way to participate in the newsgroup if you D can't access the newsgroup directly through a newsreader. Note that E INFO-VAX is a closed mailing list, which means that only subscribers f may post to it. Please see Section 1.2.4.1 for information on how to A subscribe, and how you can subscribe such that you can post from B multiple addresses but still receive no more than one copy of the mailings.
F Please remember that propogation delays can and do vary, meaning that H mailings and postings may be delayed or even lost. It is quite possible C that postings may not be delivered for several days, and that some / postings will appear out of the expected order.
a For details on the available archives, please see Section 1.2.3. Y 1.2.4.1 How do I subscribe to or unsubscribe from INFO-VAX?
) The address for subscription requests is D Info-VAX-Request[at]Mvb.Saic.Com. Subscription requests are handled E automatically by a mail server. This mail server ignores the subject 9 line and processes each line of the message as a command.
A The syntax for subscribing and unsubscribing, as well as setting , various parameters on your subscription, is:
|
" 1 SUBSCRIBE INFO-VAX (ADD is a valid synonym) H UNSUBSCRIBE INFO-VAX (REMOVE, SIGNOFF, and SIGN-OFF are valid synonyms) 6 SET INFO-VAX DIGEST (to receive in Digest format) ? SET INFO-VAX NODIGEST (to receive each message individually) D SET INFO-VAX NOMAIL (to establish an email address for posting, 7 though not receiving, mail.) H SET INFO-VAX MAIL (to establish an email address for both posting / and receiving mail.) |
G The mail server is not case-sensitive; case is irrelevant. Attempts to = fetch copies of the mailing list are rejected for reasons of F confidentiality. Any message not understood by the mailserver will be returned entirely unprocessed.
F The INFO-VAX moderator can be contacted directly at the email address Mark.Berryman[at]Mvb.Saic.Com.
H If you are on Bitnet, send a mail message containing the text SUBSCRIBE D INFO-VAX to LISTSERVE[at][nearest-Listserv-system). To unsubscribe, @ send a message containing the text SIGNOFF INFO-VAX to the same Listserv system.
D If you are on the Internet in the UK, send a message containing the G word SUBSCRIBE or UNSUBSCRIBE to info-vax-request[at]ncdlab.ulcc.ac.uk. Q 1.3 What is [n]etiquette?
F Before posting or emailing a question, please use the available local H resources, such as the OpenVMS manuals, the HELP, and the resources and H information in and referenced by this FAQ. Please use these first. Also D please specifically read the release notes and (if appropriate) the C cover letter for the product you are using. (The release notes are E generally placed in SYS$HELP:.) Quite often, these simple steps will E allow you to quickly find the answer to your own question---and more G quickly than waiting for a response to question posted to a newsgroup, H too. These steps will save you time, and will also help ensure you have F a good reputation with the folks that might be included to answer one E of your future questions, a question not covered in these resources. H Put another way, if you do not want your questions to be ignored in the A future---and please remember that the folks in the newsgroups do ? not have to answer your questions---you won't want to D "annoy the natives" by asking a question that has already E been answered far more times more than you might have realized, or a G question whose answer is readily available had you made a small effort.
8 When posting, please consider the following suggestions:
B Before posting your question to the comp.os.vms 1 newsgroup or sending your message to the INFO-VAX ? list, also please take the time to review available etiquette ? information, such as that included in the following documents:
G This information will document the etiquette of newsgroups, as well as F providing you with the knowledge the vast amount of newsgroup-related E information that is readily available to you, and where to find it...
= Please do not post security holes or system crashers E Rather, please report these problems directly to HP. Why? So that HP C has a chance to resolve and distribute a fix before other customer sites can be affected. B Most folks in the newsgroups are honest and deserve to know about ? potential security problems, but a few folks can and will make C nefarious use of this same information. Other sites will hopefully = return the courtesy, and will not post information that will G potentially compromise your site and your computer environment. |
| Next | \Contents | ^Index |