1 INFO-VAX	Sat, 30 Dec 2000	Volume 2000 : Issue 728       Contents:6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..." Re: FTP is waiting to long! ( Re: Happy Holidays - From Rich Marcelllo( Re: Happy Holidays - From Rich Marcelllo Re: My Hardware WishList2 OpenVMS Frequently Asked Questions (FAQ), Part 1/52 OpenVMS Frequently Asked Questions (FAQ), Part 2/52 OpenVMS Frequently Asked Questions (FAQ), Part 3/52 OpenVMS Frequently Asked Questions (FAQ), Part 4/52 OpenVMS Frequently Asked Questions (FAQ), Part 5/5 OSU ssh compilation problem???
 relocation Re: relocation" Sending messages to an application Re: tcpip show host error  Re: tcpip show host error  Re: tcpip show host error 1 ~~~Search for computer help (within text) Free!!!   F ----------------------------------------------------------------------  # Date: Fri, 29 Dec 2000 19:17:31 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) ? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 0 Message-ID: <009F552A.8B64D0B5@SendSpamHere.ORG>  k In article <92ih7r$dn8$2@mailint03.im.hou.compaq.com>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  > n >In article <hshubs-C414D0.23525128122000@news.mindspring.com>, Howard S Shubs <hshubs@mindspring.com> writes:8 >:In article <92fjfh$a5$1@mailint03.im.hou.compaq.com>, & >:hoffman@xdelta.zko.dec.nospam wrote: >:N >:>  "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands L >:>  because the system does little error checking.  An incorrect vector or K >:>  misspelled device name, for example, will damage the I/O database and  : >:>  could cause the system to fail."  -SysMan Essentials. >:Q >:Sure, however I don't see anything wrong with the idea of a second null device.  > G >  If you are interested, I'll see if I can adjust the existing volume  E >  shadowing support to permit the shadowing (mirroring) of multiple  H >  null devices, though served path failover would require an MSCP-awareG >  null device driver or the use of the upcoming QIOserver support. :-)   I Cool!  Can we have it such that a disk can be shadowed to a NLAn: device? I Then VMS's volume shadowing would be as effective as a third-party shadow  product I used to work on.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------    Date: 29 Dec 2000 14:34:30 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) ? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." + Message-ID: <ZLLfTGfDxkhi@eisner.decus.org>   p In article <009F552A.8B64D0B5@SendSpamHere.ORG>, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) writes:m > In article <92ih7r$dn8$2@mailint03.im.hou.compaq.com>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  >>o >>In article <hshubs-C414D0.23525128122000@news.mindspring.com>, Howard S Shubs <hshubs@mindspring.com> writes: 9 >>:In article <92fjfh$a5$1@mailint03.im.hou.compaq.com>,  ' >>:hoffman@xdelta.zko.dec.nospam wrote:  >>: O >>:>  "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands  M >>:>  because the system does little error checking.  An incorrect vector or  L >>:>  misspelled device name, for example, will damage the I/O database and ; >>:>  could cause the system to fail."  -SysMan Essentials.  >>: R >>:Sure, however I don't see anything wrong with the idea of a second null device. >>H >>  If you are interested, I'll see if I can adjust the existing volume F >>  shadowing support to permit the shadowing (mirroring) of multiple I >>  null devices, though served path failover would require an MSCP-aware H >>  null device driver or the use of the upcoming QIOserver support. :-) > K > Cool!  Can we have it such that a disk can be shadowed to a NLAn: device?   F Just be careful which copy is viewed as the master when rebuilding the shadow set !  N ==============================================================================N Great Inventors of our time: Al Gore -> Internet; Sun Microsystems -> ClustersN ==============================================================================   ------------------------------  % Date: Fri, 29 Dec 2000 15:14:50 -0600 / From: Chris Scheers <chris@applied-synergy.com> ? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 3 Message-ID: <3A4CFECA.706AC5AD@applied-synergy.com>    Hoff Hoffman wrote:  > M >   Though I suspect a general solution will be difficult to achieve at best, K >   I am certainly interested in suggestions around how we can improve upon L >   the current integrity checks within the existing CONNECT/LOAD support...  C As you point out, having SYSGEN refuse connections to the NL device  would cause problems.   A It seems that the correct solution would be to have SYSGEN refuse 9 connections to NLDRIVER (and any other "pseudo" driver?).   A In any case, I don't really see a problem with the current SYSGEN G setup.  Anyone who uses SYSGEN CONNECT better know what they are doing.   F OTOH, if there really is a use for multiple null devices, a request toB enhance NLDRIVER to support multiple units would seem appropriate.  G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com     Fax: 817-237-3074    ------------------------------  % Date: Fri, 29 Dec 2000 16:58:45 -0600 * From: "Mark E. Levy" <levy@sysman-inc.com>? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." - Message-ID: <3A4D1725.22346B4@sysman-inc.com>    > G >   If you are interested, I'll see if I can adjust the existing volume E >   shadowing support to permit the shadowing (mirroring) of multiple I >   null devices, though served path failover would require an MSCP-aware H >   null device driver or the use of the upcoming QIOserver support. :-)  E Ah, yes! A shadowed null device! That's just what OpenVMS needs to be C truly fault tolerant. Having a null device go offline can cause all H sorts of headaches. Being able to fail over to another null device would solve that problem.   A I haven't yet considered what to do when the first null device is 0 repaired and needs to be merged back in, though.   ;-)   	 Mark Levy " System Management Associates, Inc.   ------------------------------    Date: 30 Dec 2000 08:53:02 +0800, From: Paul Repacholi <prep@prep.synonet.com>? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 0 Message-ID: <87k88iafwx.fsf@k9.prep.synonet.com>  ; Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:   M > > Cool!  Can we have it such that a disk can be shadowed to a NLAn: device?  > H > Just be careful which copy is viewed as the master when rebuilding the > shadow set !  B Don't forget you take a huge performance hit if you copy the wrong way for catchup.  @ Oh, and make sure it can be spooled correctly. We'll let you off. FastPath and IO_Perform till the next release.  . I have serious worries about that last name...  P > ==============================================================================P > Great Inventors of our time: Al Gore -> Internet; Sun Microsystems -> Clusters*            Microsoft -> Enterprise Systems  P > ==============================================================================   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Sat, 30 Dec 2000 00:28:55 -0500 , From: Howard S Shubs <hshubs@mindspring.com>? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." > Message-ID: <hshubs-C582C6.00285530122000@news.mindspring.com>  I In article <009F54F8.DBDBB9C2@SendSpamHere.ORG>, system@SendSpamHere.ORG   wrote:  K >Then write your own null driver.  Fairly simple.  You don't need much more J >than a simple shell of a driver with basic FDT handlers all returning viaI >FINISHIOC with some status you desire -- typcally, SS$_NORMAL.  In fact, J >you can write your own null device driver and provide no-ops for serveralK >other $QIO functions besides those handled by the VMS NL device -- namely,  >reads and writes.  L IIRC, reads return EOF, modifications return UNSUPPORTED, and writes return  SUCCESS. --   Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  % Date: Sat, 30 Dec 2000 00:32:17 -0500 , From: Howard S Shubs <hshubs@mindspring.com>? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." > Message-ID: <hshubs-E0869E.00321730122000@news.mindspring.com>  7 In article <92ih7r$dn8$2@mailint03.im.hou.compaq.com>,  $ hoffman@xdelta.zko.dec.nospam wrote:  G >  If you are interested, I'll see if I can adjust the existing volume  E >  shadowing support to permit the shadowing (mirroring) of multiple  H >  null devices, though served path failover would require an MSCP-awareG >  null device driver or the use of the upcoming QIOserver support. :-)   M That sounds mildly obscene.  A Shadowed null device?  NSA0:?  If you go that  J way, we might have to see an HSNnn controller which prevents the need for ! host-based null device shadowing.   O Oh yes, I can see it now.  To go with the old WRITE-ONLY MEMORY device, we can  O get a RAID-5 NULL device!  Yes, now you can lose a null device and ... er, not  O lose data?  Er, losing a null device in a RAID set would require you to -keep-   data, no? <GRIN> --   Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  % Date: Sat, 30 Dec 2000 00:34:37 -0500 , From: Howard S Shubs <hshubs@mindspring.com>? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." > Message-ID: <hshubs-343F75.00343730122000@news.mindspring.com>  @ In article <87k88iafwx.fsf@k9.prep.synonet.com>, Paul Repacholi  <prep@prep.synonet.com> wrote:  A >Oh, and make sure it can be spooled correctly. We'll let you off / >FastPath and IO_Perform till the next release.   L Now there's another interesting idea: spooling a printer to a null device.  N Sounds like something the BOFH would do to save himself the hassel of working  on the line printer. --   Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------    Date: 30 Dec 2000 08:43:28 +0800, From: Paul Repacholi <prep@prep.synonet.com>$ Subject: Re: FTP is waiting to long!0 Message-ID: <87ofxuagcv.fsf@k9.prep.synonet.com>  6 "Bochnik, William J" <BochnikWJ@bernstein.com> writes:  M > Something must be up with his client install - on our system, when I try to H > connect to a machine that is up, but no ftp service running, I get the > following: > , > %FTP-E-NETERR, I/O error on network device6 > -SYSTEM-F-REJECT, connect to network object rejected  7 This is the symtom you often get if TCPwrapper is used,  and your host is not 'allowed'.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------    Date: 30 Dec 2000 02:37:39 +0800, From: Paul Repacholi <prep@prep.synonet.com>1 Subject: Re: Happy Holidays - From Rich Marcelllo 0 Message-ID: <87k88jaxak.fsf@k9.prep.synonet.com>  / wspencer@ap.nospam.org (Warren Spencer) writes:    ... L > In my quest for "most popular person in this newsgroup", I'd also like to * > offer this:  OpenVMS ain't a desktop OS.  ? Horse shit. What does VMS engineering have on their desk? Don't + equate some marketroids ideas with reality.   D Start off with NASA using 8400s as single user workstation, desktop?  " > Maybe it was going to be at one L > time (or perhaps not), but I don't see it now.  All the high-end features F > that make it so scalable and reliable differentiate it from Windows.  B And it works. That is what can differentiat it from the pack. But,@ a system that 'just works' is often on a death path if it is notD in people face. They never see it, know nothing about it. They don't; need to BECAUSE it isn't falling in a heap every 5 minutes.    G > I'd  hate to see the OpenVMS team re-direct their efforts to desktop  N > applications.  There are significantly larger and more strategic challenges I > that need to be addressed in a wired world, like IFD (Immense Freakin'  K > Databases) and IFUB:  ten million interactive users pounding on your web  $ > site (Immense Freakin' User Base).  A VMS engineering has done everything needed for the best 'desktop' @ OS in existence. Bar some odd cases. The stupid, and meaningless> distinction is mainly a handwave from the unix/gateshit corner@ of the world. Their answer to shortcomings in their fundementals= has been to 'throw it over the wall'. VMS has never had this.   > What it has had is a persistant lack of vision and guts on the? part of upper managment and the marketing/product people to get  out and make a stink.   > I'm not at all suprised that app vendors put VMS at the bottom? of their list. Not because it is inadaquate, but because no one  asks for it.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  # Date: Fri, 29 Dec 2000 23:10:00 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>1 Subject: Re: Happy Holidays - From Rich Marcelllo < Message-ID: <cR836.33559$1t.1492149@typhoon.ne.mediaone.net>  9 "Paul Repacholi" <prep@prep.synonet.com> wrote in message * news:87k88jaxak.fsf@k9.prep.synonet.com...1 > wspencer@ap.nospam.org (Warren Spencer) writes:  >  > ... J > > In my quest for "most popular person in this newsgroup", I'd also like to, > > offer this:  OpenVMS ain't a desktop OS. > A > Horse shit. What does VMS engineering have on their desk? Don't - > equate some marketroids ideas with reality.  > F > Start off with NASA using 8400s as single user workstation, desktop? > # > > Maybe it was going to be at one D > > time (or perhaps not), but I don't see it now.  All the high-end featuresH > > that make it so scalable and reliable differentiate it from Windows. > D > And it works. That is what can differentiat it from the pack. But,B > a system that 'just works' is often on a death path if it is notF > in people face. They never see it, know nothing about it. They don't= > need to BECAUSE it isn't falling in a heap every 5 minutes.  > H > > I'd  hate to see the OpenVMS team re-direct their efforts to desktopD > > applications.  There are significantly larger and more strategic
 challengesJ > > that need to be addressed in a wired world, like IFD (Immense Freakin'L > > Databases) and IFUB:  ten million interactive users pounding on your web& > > site (Immense Freakin' User Base). > C > VMS engineering has done everything needed for the best 'desktop' B > OS in existence. Bar some odd cases. The stupid, and meaningless@ > distinction is mainly a handwave from the unix/gateshit cornerB > of the world. Their answer to shortcomings in their fundementals? > has been to 'throw it over the wall'. VMS has never had this.  >   E The stupid and meaningless distinction is apps availability. Once the L StarOffice port to VMS is done, the OS might be more attractive as a desktopH environment. As it is, in the absence of personal productivity apps, VMS< leaves a lot to be desired for day to day non-technical use.   ------------------------------    Date: 30 Dec 2000 02:54:24 +0800, From: Paul Repacholi <prep@prep.synonet.com>! Subject: Re: My Hardware WishList 0 Message-ID: <878zozawin.fsf@k9.prep.synonet.com>  # Marc <Banfill@softhome.net> writes:    > Paul Repacholi wrote:A > = > > "David J. Dachtera" <djesys.nospam@earthlink.net> writes:  > >eA > > Hell no... Do you REALLY won't to cart a load of crap around?u > >LB > > But, with a SMOP, a Samsung UP2000 could run any of the above. > ! > what is SMOP?  A super Mop? *g*   > A 'Small Matter Of Programming' Use the same tone of voice you& use for 'user friendly' or 'improved'.  ? > > With a greater MOP, the UP1000 could as well. Changing fromo$ > > an Alpha to a K& would be fun... > 9 > I always thought you used a MOP to clean your floor? :)o  : Hell, can you imagine what you'd have to do to get it done with BootP?n   -- q< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.e@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------   Date: 29 Dec 2000 20:24:28 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 1/5-6 Message-ID: <92irts$f4j$1@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part1S Posting-Frequency: monthly Last-modified: 29 Dec 2000 Version: VMS-FAQ-1.TXT(5)"     Changes since last edition ==========================% Correct various examples of link-rot.dD Many (but not all) digital.com URLs are now available at compaq.com.C Remove erroneously duplicated material lurking in the MAIL section.s; Alter various uses of angle brackets, in deference to HTML.e Update various index referencesl  B Update ALPHA8    reports of a success booting OpenVMS on LX series& Update ALPHA21   Fix bogus index entryG Add    ALPHA22   OpenVMS on the Personal Workstation -a and -au series?t@ Add    ALPHA23   OpenVMS and Personal Workstation IDE bootstrap?I Add    ALPHA24   Which terminal device name is assigned to the COM ports?t( Update DECW6     DECW$IGNORE_WORKSTATION Update DOC8      Update URLeD Update FILE5     add details around support of large(r) SCSI-2 disks- Remove MGMT7     contents relocated to TIME10e$ Update MGMT23    Add cross-reference  Update MGMT25    repair link rot  Update MGMT48    repair link rot? Add    MGMT51    How can I customize the DCPS device control... A Add    MGMT52    Why do $GETDEV MOUNTCNT and SHOW DEVICE mount... A Add    MGMT53    What software is needed for Postscript printers?eM Add    MGMT54    Does volume shadowing require a non-zero allocation classes?oH Add    MGMT55    How can I reset the TCP/IP Services default IP gateway?B Add    MGMT56    How do I remove a PCSI-installed patch (ECO) kit?I Add    MGMT57    SYSINIT-E, error mounting system device, status=0072832C ( Update MISC2     de-angle, add ReGIS URL. Update MISC20    Add LMF$DISPLAY_OPCOM_MESSAGEK Add    MISC21    Third-party disk/tape/controllers/SCSI/systems on OpenVMS?L Update PROG8     add a URLG Add    PROG20    How can I have common sources for messages, constants?BC Update SOFT1     Correct attribution, various additions and updatesA; Update SOFT3     Point only to the Mozilla schedule websiteo$ Remove SOFT11    duplicate of MGMT40 Add    SOFT13    DECmigrate...D Add    SOFT14    Access to OpenVMS Netscape Navigator documentation?( Update TIME1     modified half-witticism: Add    TIME10    relocate and update the contents of MGMT7B Add    TIME11    Details of the VAX and Alpha system time-keeping?B Update UTIL1     Various updates related to playing audio CD media; Update UTIL4     Current Fortran RTL kit contains fixed _TVt8 Add    UTIL6     How can I patch an OpenVMS Alpha image?C Update DCL1      focus on zip, add TCPIP$DEFINE_COMMANDS reference.l8 Update WIRES1    add some more pinouts, update some URLs" Update VAX1      add more KA codes     Overview ========E This is part 1/5 of the Frequently Asked Questions (FAQ) posting for m= the comp.os.vms and comp.sys.dec newsgroups.  (comp.os.vms isfC bidirectionally-gatewayed to the INFO-VAX mailing list - see INTRO3r> for further details.)  It contains answers to frequently askedB questions about Compaq's OpenVMS operating system and the computer> systems on which it runs.  (Please see INTRO5 before posting.)  9   The OpenVMS FAQ is archived in the following locations:t  "     http://www.openvms.compaq.com/.     ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/,     comp.answers and news.answers newsgroups  A   Other internet FAQs are generally available in these locations:=  ,     comp.answers and news.answers newsgroups%     ftp://rtfm.mit.edu/pub/usenet/...r  ?   User-created HTML versions of the OpenVMS FAQ are located at:s       http://www.kjsl.com/vmsfaq'     http://eisner.decus.org/vms/faq.htm.  I Please do NOT send technical questions to the Frequently Asked Questions eH (FAQ) editor -- well, please do not email any questions that do not alsoG include the answer(s).  Please post these questions to the appropriate cI newsgroup instead -- and see INTRO5 before posting.  To make suggestions EG for changes or additions to this FAQ list, please send mail to the FAQ tI editor at hoffman@xdelta.zko.dec.com.  Again, the FAQ editor is *not* in i' a position to answer general questions.c   Some general notes:a  L The term "VMS" is synonymous with "OpenVMS".  "Alpha", "AlphaGeneration" or G "AXP" generally refers to any system or product based on or related to aJ Compaq's Alpha processor architecture.  OpenVMS manual names mentioned areC those as of V7.2 -- names may be different in other editions of thee documentation set.  H World-Wide Web Universal Resource Locator (URL) notation is used for FTP
 addresses.  F Many people have contributed to this list, directly or indirectly.  InG some cases, an answer has been adapted from one or more postings on the-D comp.os.vms newsgroup.  Our thanks to all of those who post answers.H The name (or names) at the end of an entry indicate that the informationD was taken from postings by those individuals; the text may have beenG edited for this FAQ.  These citations are only given to acknowledge theh
 contribution.   A Although the editor of this FAQ is an employee of Compaq ComputerhA Corporation, this posting is not an official statement of Compaq.v  L AlphaGeneration, AlphaServer, AlphaStation, Alpha AXP, AXP, DEC, DECstation,J DECsystem, OpenVMS, ULTRIX, VAX and VMS are trademarks of Compaq.  Compaq M and the names of Compaq products are trademarks and/or registered trademarks eL and/or service marks of Compaq Computer Corporation.  OSF/1 is a registered K trademark of the Open Software Foundation.  UNIX is a registered trademark tG in the United States and other countries, licensed exclusively through oK X/Open Company Ltd.  Other names are properties of their respective owners.+     Table of Contents - Part 1/5 ____________________________   Introduction( ========================================* INTRO1.  What is the scope of comp.os.vms?= INTRO2.  What other newsgroups carry VMS-related information?  INTRO3.  What is INFO-VAX?< INTRO4.  How do I subscribe to or unsubscribe from INFO-VAX?F INTRO5.  How do I submit a question or a response?  What is etiquette? INTRO6.  What is DECUS?o= INTRO7.  What archives of comp.os.vms/INFO-VAX are available? D INTRO8.  Who are the corporate contacts for OpenVMS business issues?   General questions about OpenVMS ( ========================================. VMS1.   What is OpenVMS?  What is its history?7 VMS2.   What is the difference between VMS and OpenVMS?=* VMS3.   How do I port from VMS to OpenVMS?* VMS4.   Which is better - OpenVMS or UNIX?= VMS5.   Is Compaq continuing funding and support for OpenVMS?=3 VMS7.   What OpenVMS CD-ROM products are available?=, VMS8.   In what language is OpenVMS written?2 VMS9.   How do I obtain or transfer a VMS license?= VMS10.  What is OpenVMS doing about the Euro currency symbol? ? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?-? VMS12.  Are there any general-access OpenVMS systems available?a* VMS13.  What version of OpenVMS do I need?* VMS14.  How can I submit OpenVMS Freeware?( VMS15.  Porting applications to OpenVMS?0 VMS16.  How do I join Compaq Solutions Alliance?    ! Documentation and other resourcesa( ========================================: DOC1.   Where can I find online copies of OpenVMS manuals?- DOC2.   What online information is available?u2 DOC3.   What books and publications are available?5 DOC4.   How do I extract a HELP topic to a text file?s6 DOC5.   Does OpenVMS Marketing have an e-mail address?5 DOC6.   What OpenVMS-related WWW sites are available?-B DOC8.   Where can I find info about undocumented OpenVMS features?@ DOC9.   Where is documentation on the DECnet Phase IV protocols?G DOC10.  Where can I learn about how the VMS executive works internally?-D DOC11.  Where can new users find tutorial information about OpenVMS?C DOC12.  How to access the OpenVMS Netscape Navigator documentation?    OpenVMS System Time ( ========================================8 TIME1.   A brief history of OpenVMS Timekeeping, please?3 TIME2.   How does OpenVMS VAX maintain system time?0' TIME3.   Why does my system time drift?hD TIME4.   Managing Timezones, Timekeeping, UTC, and Daylight Savings?5 TIME5.   How to troubleshoot TDF problems on OpenVMS? = TIME6.   How can I keep the OpenVMS system time synchronized?eD TIME7.   How can I configure TCP/IP Services NTP as a time provider?1 TIME8.   How can I drift the OpenVMS system time?e; TIME9.   Why does VAX need a SET TIME at least once a year? @ TIME10.  Why can't I do a SET TIME command?  Help managing DTSS?: TIME11.  Details of the VAX and Alpha system time-keeping?   Table of Contents - Part 2/5 ____________________________   System Managementa( ========================================# MGMT1.  What is an installed image?D0 MGMT2.  Are there any known viruses for OpenVMS?1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS? 4 MGMT4.  How do I extract the contents of a PCSI kit?; MGMT5.  I've forgotten the SYSTEM password - what can I do? 9 MGMT6.  How do I connect a PostScript printer via TCP/IP?-? MGMT7.  Why can't I do a SET TIME command?  Help Managing DTSS?mD MGMT8.  How do I change the timezone differential and time in batch?; MGMT9.  How do I change the node name of an OpenVMS System?FE MGMT10. What is the correct value for EXPECTED_VOTES in a VMScluster?.< MGMT11. Why doesn't OpenVMS see the new memory I just added?9 MGMT12. How do I write a BACKUP saveset to a remote tape?l3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSCt4 MGMT14. How do I install DECnet Phase IV on VMS 7.1?< MGMT15. How do I change the text in a user's UIC identifier?3 MGMT16. What are the OpenVMS version upgrade paths? G MGMT17. Why do I have negative number in the pagefile reservable pages? C MGMT18. Do I have to update layered products when updating OpenVMS?-3 MGMT19. How do I change the volume label of a disk?R. MGMT20. How do I fix a corrupt BACKUP saveset?, MGMT21. How can I set up a shared directory?8 MGMT23. Why do I get extra blank pages on my HP Printer?C MGMT24. How do I configure ELSA GLoria Synergy graphics on OpenVMS?i: MGMT25. How do I acquire OpenVMS patches, fixes, and ECOs?. MGMT26. How do I rename a DSSI disk (or tape?)1 MGMT27. How do I move the queue manager database?o> MGMT28. How do I set a default IP route or gateway on OpenVMS?C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process? * MGMT31. How do I reset the error count(s)?A MGMT32. How do I find out if the tape drive supports compression?)? MGMT33. Can I copy SYSUAF to another version? To VAX? To Alpha? 1 MGMT34. How do I delete (timeout) idle processes?a. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?; MGMT36. How can I set up reverse telnet (like reverse LAT)?+? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?H6 MGMT38. INITIALIZE ACCVIO and ANSI tape label support?/ MGMT39. How do I recover from INSVIRMEM errors?pI MGMT40. How can I prevent a serial terminal line from initiating a login?e6 MGMT41. How does PCSI use the image BUILD_IDENT field?@ MGMT42. How to configure allocation classes and Multi-Path SCSI?@ MGMT43. How can I tell what software (and version) is installed?@ MGMT44. Where can I get Fibre Channel Storage (SAN) information?. MGMT45. How can I split up an OpenVMS Cluster?; MGMT46. What file checksum tools are available for OpenVMS?l8 MGMT47. Configuring Cluster SCS for path load balancing?; MGMT48. What (and where) is the OpenVMS Management Station?i- MGMT49. Determining disk fragmentation level? @ MGMT50. SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?F MGMT51. How can I customize the DCPS device control for a new printer?D MGMT52. Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts differ?8 MGMT53. What software is needed for Postscript printers?D MGMT54. Does volume shadowing require a non-zero allocation classes?? MGMT55. How can I reset the TCP/IP Services default IP gateway? 9 MGMT56. How do I remove a PCSI-installed patch (ECO) kit?i@ MGMT57. SYSINIT-E, error mounting system device, status=0072832C     Table of Contents - Part 3/5 ____________________________   MAIL( ========================================$ MAIL1.  How do I send Internet mail?J MAIL2.  How do I get IN% or MX% added automatically to Internet addresses?K MAIL3.  How do I automatically append a signature file to my mail messages?iA MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.pL MAIL5.  How can I forward my mail?  Can I forward it to an Internet address?9 MAIL6.  How can I forward my mail to a list of addresses? J MAIL7.  MAIL keeps saying I have new messages, but I don't.  What do I do?; MAIL8.  How do I extract all of my mail messages to a file?.6 MAIL9.  How do I send or read attachments in VMS MAIL?     Other Utilities0( ========================================4 UTIL1.  How do I play an audio CD on my workstation?: UTIL2.  How do I access a MS-DOS floppy disk from OpenVMS?L UTIL3.  How do I play sound files on an AlphaStation?  DECsound doesn't work3 UTIL4.  Why is DECmigrate not working with Fortran?.2 UTIL5.  How do I read IBM EBCDIC tapes on OpenVMS?/ UTIL6.  How can I patch an OpenVMS Alpha image?.     DCL and command usagee( ========================================. DCL1.   How do I run a program with arguments?/ DCL2.   How can I redefine control keys in DCL?r* DCL3.   How can I clear the screen in DCL?< DCL4.   Using REPLY/LOG from DCL?  Disabling Console OPCOMs?1 DCL5.   How do I generate a random number in DCL? % DCL6.   What does the MCR command do? 2 DCL7.   How do I change the OpenVMS system prompt?< DCL8.   Can I do DECnet task-to-task communication with DCL?6 DCL9.   How can I get the width setting of a terminal?/ DCL10.  How can I substitute symbols in a PIPE?d, DCL11.  Use of RUN/DETACH and logical names?8 DCL12.  How to use escape and control characters in DCL?   File System and RMSn( ========================================" FILE1.  How can I undelete a file?B FILE2.  Why does SHOW QUOTA give a different answer than DIR/SIZE?B FILE3.  How do I make sure that my data is safely written to disk?C FILE4.  What are the limits on file specifications and directories?h@ FILE5.  What is the largest disk volume size OpenVMS can access?E FILE6.  What is the maximum file size, and the RMS record size limit?l1 FILE7.  How do I write recordable CDs on OpenVMS?r7 FILE8.  What I/O transfer size limits exist in OpenVMS? < FILE9.  Can I use ODBC to connect to OpenVMS database files?     ProgrammingU( ========================================: PROG1.  How do I call <routine_name> from <language_name>?9 PROG2.  How do I get the arguments from the command line?n= PROG3.  How do I get a formatted error message in a variable?tD PROG4.  How do I link against SYS$SYSTEM:SYS.STB on an Alpha system?8 PROG5.  How do I do a SET DEFAULT from inside a program?M PROG6.  How do I create a shareable image transfer vector on an Alpha system?tH PROG7.  How do I turn my Fortran COMMON into a shareable image on Alpha?< PROG8.  How do I convert between IEEE and VAX floating data?= PROG9.  How do I get the argument count in a Fortran routine?h? PROG10. How do I get a unique system ID for licensing purposes? ? PROG11. What is an executable, shareable, system or UWSS image?j/ PROG12. How do I do a file copy from a program?o PROG13. What is a descriptor? + PROG14. How many bytes are in a disk block?a, PROG15. How many bytes are in a memory page?9 PROG16. How do I create a process under another username?nD PROG17. Why do lib$spawn, lib$set_symbol fail in detached processes?I PROG18. Where can I obtain Bliss, and the libraries and supporting files? 0 PROG19. How can I open a file for shared access?> PROG20. How can I have common sources for messages, constants?   Table of Contents - Part 4/5 ____________________________  
 DECwindows( ========================================F DECW1.  How do I let someone else display something on my workstation?9 DECW2.  How do I create a display on another workstation? F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?0 DECW4.  How do I get a log of a DECterm session?E DECW5.  Problem - the DELETE key deletes forward instead of backward!u- DECW6.  Why is DECwindows Motif not starting?l3 DECW9.  How do I set the title on a DECterm window?eB DECW10. How do I customize DECwindows, including the login screen?4 DECW11. Why doesn't XtAppAddInput() work on OpenVMS?B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?2 DECW13. Why does half my DECwindows display blank?B DECW14. %DECW-W-NODEVICE, No graphics device found on this system?0 DECW15. How can I reset the warning bell volume?2 DECW16. How can alter the DECwindows CDE backdrop?8 DECW17. How can I enable the DECwindows TCP/IP Transport    
 Miscellaneouse( ========================================G MISC2.    Where can I find information on escape and control sequences?nE MISC6.    What does "failure on back translate address request" mean?r8 MISC7.    How to determine the network hardware address?I MISC8.    Why does my system halt when I powercycle the console terminal?aB MISC9.    Why can't I use PPP and RAS to connect to OpenVMS Alpha?@ MISC12.   Does DECprint (DCPS) work with the LRA0 parallel port?; MISC13.   How do I check for free space on a (BACKUP) tape?E* MISC14.   So what happened to sys$cmsuper?< MISC15.   How can I send radio pages from my OpenVMS system?< MISC17.   How do I reset the LAN (DECnet-Plus NCL) counters?6 MISC18.   What are the prefixes for the powers of ten?6 MISC19.   OpenVMS Cluster (SCS) over DECnet?  Over IP?/ MISC20.   Correctly using license PAKs and LMF?.D MISC21.   Third-party disk/tape/controllers/SCSI/widgets on OpenVMS?     Software( ========================================C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?r@ SOFT2.    Where can I find the UNIX <whatever> tool for OpenVMS?I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser?t+ SOFT4.    Where can I get Java for OpenVMS?NJ SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?1 SOFT6.    Obtaining user input in DCL CGI script?Y1 SOFT7.    How do I get my own batch entry number?a0 SOFT8.    How do I convert to new CMS libraries?B SOFT9.    Where can I get new certificates for Netscape Navigator?3 SOFT10.   Why doesn't DCL symbol substitution work?tK SOFT11.   How can I prevent a serial terminal line from initiating a login?M+ SOFT12.   Where can I get Perl for OpenVMS?p4 SOFT13.   Where can I get DECmigrate (VEST and TIE)?     Table of Contents - Part 5/5 ____________________________   Alpha and Alpha-based systemsw( ========================================, ALPHA1.   What do the letters AXP stand for?A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?VF ALPHA5.   Seeking performance information for Alpha (and VAX) systems?E ALPHA6.   Where can I get updated console firmware for Alpha systems?hD ALPHA7.   How do I boot an AlphaStation without monitor or keyboard?= ALPHA8.   Will OpenVMS run on a Multia? AlphaPC 164LX? 164SX?sC ALPHA9.   What is the least expensive system that will run OpenVMS? < ALPHA10.  Where can I get more information on Alpha systems?, ALPHA11.  What are the APB boot flag values?7 ALPHA12.  What are Alpha console environment variables?e0 ALPHA13.  Will OpenVMS run on a NoName AXPpci33?D ALPHA14.  How do I reload SRM firmware on a half-flash Alpha system?2 ALPHA15.  Will OpenVMS run on the Alpha XL series?G ALPHA16.  Describe Alpha instruction emulation and instruction subsets? J ALPHA17.  What is the Accuracy of the Alpha Time of Year (BB_WATCH) Clock?3 ALPHA18.  So how do I open up the DEC 3000 chassis?e! ALPHA19.  What is byte swizzling?a? ALPHA20.  What commands are available in the Alpha SRM console? A ALPHA21.  How do I switch between AlphaBIOS/ARC and SRM consoles? @ ALPHA22.  OpenVMS on the Personal Workstation -a and -au series?9 ALPHA23.  OpenVMS and Personal Workstation IDE bootstrap? B ALPHA24.  Which terminal device name is assigned to the COM ports?     VAX and VAX-based systemsl( ========================================8 VAX1.   Please explain the back panel of the MicroVAX II< VAX2.   What is the layout of the VAX floating point format?2 VAX3.   Where can I find more info on VAX systems?? VAX4.   Where can I find information on NetBSD for VAX systems?nH VAX5.   What system disk size limit on the MicroVAX and VAXstation 3100?* VAX7.   What are the VMB boot flag values?> VAX9.   Which serial port is the console on the MicroVAX 3100?> VAX10.  How can I set up an alternate console on a VAXstation?  ' Hardware and Software Support resourcesA( ========================================B SUPP1.  Where can I get software and hardware support information?E SUPP2.  Where can I get hardware self-maintenance support assistance?dH SUPP3.  Why does my system halt when I power-cycle the console terminal?? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?eA SUPP5.  Which video monitor works with which graphics controller?c8 SUPP6.  Where can I get information on storage hardware?< SUPP7.  Problem - My LK401 keyboard unexpectedly autorepeatsI SUPP8.  Problem - My LK411 sends the wrong keycodes or some keys are deady    ! SCSI-related Hardware informatione( ========================================< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?, SCSI2.  Resolving DRVERR fatal device error?    F Wiring-, Adapter-, Connector-, and Pinout-related Hardware information( ========================================- WIRES1. Looking for connector wiring pinouts?e: WIRES2. What connectors and wiring adapters are available?2 WIRES3. What is flow control and how does it work?    < ------------------------------------------------------------* INTRO1.  What is the scope of comp.os.vms?  E The comp.os.vms newsgroup is the primary newsgroup for discussion of rF Compaq's OpenVMS operating system and the computer systems on which itE runs.  Questions about layered products which run on OpenVMS are also C welcome, though many of them (in particular, language compilers andwC database systems) have more specific newsgroups.  If a question has_. some relationship to OpenVMS, it belongs here.  < ------------------------------------------------------------= INTRO2.  What other newsgroups carry VMS-related information?   D The vmsnet.* hierarchy, run by DECUS, contains several newsgroups ofI interest, including vmsnet.misc and vmsnet.alpha, the latter being mostlye; devoted to Alpha topics.  There's also vmsnet.sources (and pJ vmsnet.sources.d) to which sources for or pointers to freeware are posted.F See the separate "What is VMSNET" monthly posting for further details.  C The comp.sys.dec newsgroup carries discussions about Compaq systems , acquired from Digital Equipment Corporation.  < ------------------------------------------------------------ INTRO3.  What is INFO-VAX?  D INFO-VAX is a mailing list which is bidirectionally gatewayed to theC comp.os.vms newsgroup.  This means that postings to comp.os.vms get L automatically sent to INFO-VAX subscribers and messages sent to the INFO-VAXK list are automatically posted to comp.os.vms.  INFO-VAX can be a useful way F to participate in the newsgroup if you can't access the group directly through a news reader.  H An important point to keep in mind is that propagation delays vary, bothD within the newsgroup and with INFO-VAX mailings.  It's possible thatI postings may not be delivered for several days and some may appear out ofo order.  < ------------------------------------------------------------< INTRO4.  How do I subscribe to or unsubscribe from INFO-VAX?  H The address for subscription requests, as well as notes intended for theO moderator, is Info-VAX-Request@Mvb.Saic.Com.  Subscription requests are handled N automatically by a mail server.  This mail server ignores the subject line andL processes each line of the message as a command.  The syntax for subscribing< and unsubscribing and setting digest or non-digest modes is:  t0 SUBSCRIBE INFO-VAX      (ADD is a valid synonym)G UNSUBSCRIBE INFO-VAX	(REMOVE, SIGNOFF, and SIGN-OFF are valid synonyms) 5 SET INFO-VAX DIGEST     (to receive in Digest format)o> SET INFO-VAX NODIGEST   (to receive each message individually)  yK Case is irrelevant and attempts to fetch a copy of the mailing list will beyJ rejected (I consider the information to be confidential).  Any message notI understood by the mailserver will be forwarded to a human (allegedly) fore manual processing.  				[Mark.Berryman@Mvb.Saic.Com]  > If you are on Bitnet, send a mail message containing the text L "SUBSCRIBE INFO-VAX" to LISTSERV@(nearest listserv system).  To unsubscribe,L send a message containing the text "SIGNOFF INFO-VAX" to the *SAME* listserv	 address. e  C If you are on the Internet in the UK, send a message containing the F word SUBSCRIBE (or UNSUBSCRIBE) to info-vax-request@ncdlab.ulcc.ac.uk.  < ------------------------------------------------------------F INTRO5.  How do I submit a question or a response?  What is etiquette?  J If you are using a news reader, post your question to comp.os.vms.  If youK want to submit through INFO-VAX, send the message to Info-VAX@mvb.saic.com.6  J Before posting, please use available local resources, such as the manuals,L HELP and this FAQ first.  Also make a point of reading the release notes forJ the product you're using, generally placed in SYS$HELP.  Often you'll findM the answer, and will save time and effort for all concerned.  (And you won't   "annoy the natives"...).  8 When posting, please consider the following suggestions:  E     1.  Include a valid e-mail address in the text of your posting or1D         in a "signature" appended to the end.  Reply-to addresses in 	headers often get garbled.a  F     2.  If you are submitting a question, please be as specific as youJ         can.  Include relevant information such as processor type, productF 	versions (OpenVMS and layered products that apply), error message(s),M         DCL command(s) used, and a short, reproducible example of problems.  bM         Say what you've tried so far, so that effort isn't duplicated.  Keep -K         in mind that there's not yet a telepathy protocol for the Internet.aM         (The more detailed your description, the better that people can help            you with your question.)  I     3.  If responding to a posting, include in your reply only as much ofeF         the original posting as is necessary to establish context.  AsE 	a guideline, consider that if you've included more text than you've uE 	added, you've possibly included too much.  Never include signatures w 	and other irrelevant material.d  E     4.  Be polite.  If the question isn't worded the way you think istC         correct or doesn't include the information you want, try top> 	imagine what the problem might be if viewed from the poster's< 	perspective.  Requests for additional information are often> 	better sent through mail rather than posted to the newsgroup.  J     5.  If you have a problem with Compaq (or any other vendor's) product,F         please use the appropriate support channel.  Don't assume that? 	newsgroup postings will get read, will be responded to by the RB         appropriate developers, or will be later followed up on...  I     6.  If you are posting from a web browser, news reader or if you are  I         posting via email sent to INFO-VAX, please turn off MIME, vcard, oI         attachments, and other mechanisms that assume anyone reading the  J         post has the corresponding capability -- use the text-only option M         of your web browser, news reader, or mailer.  Usenet is traditionally F 	a text-only medium, and many comp.os.vms participants will use tools C 	that have this support disabled, or that do not have this support.iC 	If the message uses MIME or attachments or such, the text of your aE 	message will be buried in a large pile of gibberish, and some tools o? 	will send multiple copies of the text within a single posting.V  J Before posting your question to the comp.os.vms newsgroup or sending your L message to the INFO-VAX list, also please take the time to review available H etiquette information, such as that included in the following documents:  @   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/primer/part1=   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/faq/part1nH   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/emily-postnews/part1G   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/writing-style/part1 G   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/posting-rules/part1o  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 ***.  I Rather, please report these problems directly to Compaq.  (Why?  So that  J Compaq has a change to resolve and distribute a fix before other customer L sites can be affected.  Most folks in the newsgroups are honest and deserve M to know about potential security problems, but a few folks can and will make oK nefarious use of this same information.  Other sites will hopefully return  J the favor, and not post information that will potentially compromise YOUR # site and YOUR computer environment.o  < ------------------------------------------------------------ INTRO6.  What is DECUS?.  D DECUS, the Digital Equipment Computer Users Society, is a World WideF organization of Information Technology professionals interested in theC products, services, and technologies of Compaq and related vendors.      J Membership in the Chapter is free and provides participants with the meansI to enhance their professional development, forums for technical training,7G mechanisms for obtaining up-to-date information, advocacy programs, andaG opportunities for informal disclosure and interaction with professionaln colleagues of like interest.  M For further information, see the separate monthly "What is DECUS" posting, or?H refer to the US DECUS WWW server at http://www.decus.org or the Canadian) DECUS WWW server at http://www.decus.ca/.=  < ------------------------------------------------------------= INTRO7.  What archives of comp.os.vms/INFO-VAX are available?I  : Everything posted since 1990 is archived and available at:   ftp://crvax.sri.com/info-vax/c   					[Arne Vajhj]  < ------------------------------------------------------------D INTRO8.  Who are the corporate contacts for OpenVMS business issues?  <   The following folks are the Compaq corporate contacts for ?   OpenVMS business issues, listed in descending order from the  @   Comoaq Corporate President to the OpenVMS Vice President (VP).     1     Michael Capellas     Compaq President and CEOo9                          Michael.Capellas[-at-]Compaq.Como  D     Bill Heil            VP, Business Critical Servers Business Unit2                          Bill.Heil[-at-]Compaq.Com  =     Don Harbert          VP, High Performance Server Divisiono4                          Don.Harbert[-at-]Compaq.Com  8     Rich Marcello        VP, Open Systems Software Group9                          Richard.Marcello[-at-]Compaq.Coma  D   These folks will obviously respond best to cogently-worded OpenVMSG   corporate business issues.  These folks are NOT appropriate contacts uH   for any OpenVMS technical support issues or support requests, nor for ?   any other non-corporate-related, non-business-related issues. 9                                          [Atlant Schmidt]h  < ------------------------------------------------------------. VMS1.   What is OpenVMS?  What is its history?  N OpenVMS, originally called VMS (Virtual Memory System), was first conceived inL 1976 as a new operating system for the then-new, 32-bit, virtual memory lineN of computers, eventually named VAX (Virtual Address eXtension).  The first VAXI model, the 11/780, was code-named "Star", hence the code name for the VMSaM operating system, "Starlet", a name that remains to this day the name for thesI system library files (STARLET.OLB, etc.).  VMS version X0.5 was the firstsN released to customers, in support of the hardware beta test of the VAX-11/780,D in 1977.  VAX/VMS Version V1.0 shipped in 1978, along with the first revenue-ship 11/780s.E  L OpenVMS was designed entirely within Compaq (Digital Equipment Corporation).G The principal designers were Dave Cutler and Dick Hustvedt, with a wideoK variety of other contributors.  OpenVMS was conceived as a 32-bit, virtual oJ memory successor to the RSX-11M operating system for the PDP-11.  Many of K the original designers and programmers of OpenVMS had worked previously on vE RSX-11M, and many concepts from RSX-11M were carried over to OpenVMS.l  F OpenVMS VAX is a 32-bit, multitasking, multiprocessing virtual memory H operating system. Current implementations run on VAX systems from Compaq and other vendors.  G OpenVMS Alpha is a 64-bit multitasking, multiprocessing virtual memory lC operating system. Current implementations run on Alpha systems froma Compaq, and other vendors.   				[Paul Winalski]s 				[Arne Vajhj]d  G For more details on OpenVMS and its features, read the OpenVMS Softwaret Product Description at:r  !   http://www.compaq.com/info/spd/t:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  A Additional information on the general features of various OpenVMSo@ releases, release dates, as well as the development project code, names of specific releases, is available at:  G   http://www.openvms.compaq.com/openvms/os/openvms-release-history.htmld  J Additional historical information -- as well as pictures and a variety of > other trivia -- is available in the VAX 20th anniversary book:  8   http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  E For information on the FreeVMS project (also see the related softwarea$ licensing topics VMS9, ALPHA4), see:     http://www.freevms.org/=  < ------------------------------------------------------------7 VMS2.   What is the difference between VMS and OpenVMS?h  I VMS and OpenVMS are two names for the same operating system.  Originally,eD the operating system was called VAX-11/VMS; it changed to VAX/VMS atE around VAX/VMS V2.0.  When the VMS operating system was ported to theSG Alpha platform, it was renamed OpenVMS, for both VAX and Alpha, in part D to signify the high degree of support for industry standards such as5 POSIX, which provides many features of UNIX systems. r  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 iL media and documentation which can be found on the Consolidated Distribution I and On-Line Documentation CD-ROMs.  Support for the POSIX package on moreeH recent OpenVMS releases is not available, various parts of POSIX such asI calls from the API are being integrated more directly into OpenVMS.  For r4 more information on POSIX for VMS see question SOFT2  C What became confusing is that the OpenVMS name was introduced firstoF for OpenVMS AXP V1.0 causing the widespread misimpression that OpenVMSF was for Alpha AXP only, while "regular VMS" was for VAX.  In fact, theI official name of the VAX operating system was changed as of V5.5, though PE the name did not start to be actually used in the product until V6.0.l  G The proper names for OpenVMS on the two platforms are now "OpenVMS VAX"?@ and "OpenVMS Alpha", the latter having superseded "OpenVMS AXP".   				[Arne Vajhj]n  < ------------------------------------------------------------* VMS3.   How do I port from VMS to OpenVMS?  9 You already did.  Wasn't that easy?  (See question VMS2.)h  < ------------------------------------------------------------* VMS4.   Which is better - OpenVMS or UNIX?  M This question comes up periodically, usually asked by new subscribers who are M long-time UNIX users. Sometimes, it is ignored totally; other times, it leads N to a long series of repetitive messages that convince no one and usually carryD little if any new information.  Please do everyone a favor and avoid- re-starting this perpetual, fruitless debate.. 					[leichter@lrw.com]r  F Seriously, OpenVMS and the better implementations of UNIX are all fineE operating systems, each with its strengths and weaknesses.  If you're=E in a position where you need to choose, select the one that best fitsoC your own requirements, considering, for example, whether or not the @ layered products or specific OS features you want are available.   					[Steve Lionel]o  < ------------------------------------------------------------= VMS5.   Is Compaq continuing funding and support for OpenVMS?b   Yes.  ? Active development of new OpenVMS releases is underway, as well3 as the continuation of support.   @ Please see the following URLs for details, roadmaps, and related information:      http://www.compaq.com/openvms/5   http://www.openvms.compaq.com/OPENVMS/strategy.htmlrD   http://www.openvms.compaq.com/openvms/roadmap/openvms_roadmaps.htm-   http://www.openvms.compaq.com/openvmstimes/l   http://www.compaq.com/inform/t  < ------------------------------------------------------------' [VMS6 removed, replaced by Y2K section]o  < ------------------------------------------------------------3 VMS7.   What OpenVMS CD-ROM products are available?L  $ Various distributions are available.  B For information on the available part numbers and current productsF (OpenVMS distribution kits, media, documentation, etc) and associated K licensing information, please see the OpenVMS Software Product Description   (SPD), available at:  !   http://www.compaq.com/info/spd/A:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  F The following CD-ROMs contain just the OpenVMS Alpha operating system.> These are bootable, and can be used to run BACKUP from CD-ROM.  >   QA-MT1AP-H8   OpenVMS Alpha V6.1-1H2 hardware release CD-ROM>   QA-MT1AG-H8   OpenVMS Alpha V6.2-1H3 hardware release CD-ROM>   QA-MT1AD-H8   OpenVMS Alpha V7.1-1H1 hardware release CD-ROM?   QA-MT1AR-H8   OpenVMS Alpha V7.1-2 maintenance release CD-ROMO?   QA-MT1AT-H8   OpenVMS Alpha V7.2-1 maintenance release CD-ROMs>   QA-MT1AU-H8   OpenVMS Alpha V7.2-1H1 hardware release CD-ROM  J The following are the consolidated ECO distribution kit subscriptions, andH these provide sites with eight updates of the current ECO kits per year:     QT-3CQAA-C8   OpenVMS Alphah   QT-3CRAA-C8   OpenVMS VAX-  E OpenVMS VAX and OpenVMS Alpha source listings CD-ROM sets include therI source listings of most of OpenVMS, and these CD-ROM sets are invaluable iG for any folks working directly with OpenVMS internals, as well as folksa@ interested in seeing examples of various programming interfaces.  4   QB-MT1AB-E8   OpenVMS Alpha Source Listings CD-ROM<   QT-MT1AB-Q8   OpenVMS Alpha Source Listings CD-ROM Updates2   QB-001AB-E8   OpenVMS VAX Source Listings CD-ROM:   QT-001AB-Q8   OpenVMS VAX Source Listings CD-ROM Updates   < ------------------------------------------------------------, VMS8.   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, I Macro, Ada, PLI, VAX and DEC C, Fortran, UIL, VAX and Alpha SDL, Pascal, NG MDL, DEC C++, DCL, Message, and Document.  And this is certainly not a lG complete list. However, the rumor is NOT true that an attempt was made iC to write pieces of OpenVMS in every supported language so that the sG Run-Time Libraries could not be unbundled.  (APL, BASIC, COBOL and RPG  0 are just some of the languages NOT represented!)  I There are a large variety of small and not-so-small tools and DCL commandsI procedures that are used as part of the OpenVMS build, and a source code -K control system capable of maintaining over a hundred thousand source files IH across multiple parallel development projects, and overlapping releases.  < ------------------------------------------------------------2 VMS9.   How do I obtain or transfer a VMS license?  H If you are a DECUS member and are considering acquiring and using a VAX G or Alpha system for hobbyist (non-commercial) use, (free) licenses for bB OpenVMS VAX and OpenVMS Alpha are available to DECUS members.  In D addition to the license, VAX and Alpha distribution CD-ROM kits are H available with OpenVMS, DECwindows Motif, DECnet and TCP/IP networking, - compilers, and a variety of layered products.   ! For further information, link to:y  #   http://www.montagar.com/hobbyist/t  E Further information on DECUS and on DECUS membership is available at:i     http://www.decus.org/y  E For information on licenses for educational customers, see the CompaqaA CSLG license program and the OpenVMS Educational license program:]     http://www.openvmsedu.com/  C To transfer a commercial OpenVMS license from one owner to another,eD or to purchase a commercial license, you can contact Compaq ComputerA Corporation at 1-800-DIGITAL (in North America), or your local ory regional sales office.  E Commercial developers can join the CSA program, and can (potentially) C receive discounts on various software product licenses and software-D distributions, as well as on hardware purchases.  Please see ALPHA4.   					[Stephen Hoffman]6                                         [Scott Snadow]  < ------------------------------------------------------------= VMS10.  What is OpenVMS doing about the Euro currency symbol?   B For information on the current status and plans for support of the? European Monetary Union's Euro currency symbol in OpenVMS, see:r  %   http://www.openvms.compaq.com/euro/c  < ------------------------------------------------------------? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?t   Why?  Business reasons...l  B Because there is a belief that there would be no market to justifyA the effort and the expense involved in porting OpenVMS to systemsrA using the Intel IA32 architecture.  (Each maintainer of a productgA or package for OpenVMS would have to justify the port to "OpenVMSsD IA32", akin to a port from OpenVMS VAX to OpenVMS Alpha.  The effort8 involved in porting OpenVMS from VAX to Alpha was huge.)  B Because every one of the core applications would have to be portedB from Alpha to IA32, and then customer and third-party applications would also have to be ported.i  C Because there are design features that required by OpenVMS that aretF not available on IA32, features that would require redesigning OpenVMSB to operate in the environment, making ports rather more difficult.; ASTs and interlocked operators are obvious prerequirements.e  C Because Alpha is faster than Intel IA32 systems -- if OpenVMS is tos? be ported, a port to a slower system is more difficult to sell.d  @ Because Intel is expecting to replace IA32 processors with IA64.  B Because hobbyists have been easily able to acquire OpenVMS systems( and the DECUS hobbyist OpenVMS licenses.  @ Because OpenVMS already operates on Compaq and third-party AlphaF systems; specific features in support of third-party vendor-customizedD bootstrap capabilities for use on third-party systems are present in( OpenVMS Alpha V7.1-2 and later releases.  C Because there are assumptions that some of the stability of OpenVMShD arises from the stability of the underlying VAX and Alpha hardware, C and systems based on components such as ISA and random memory SIMMsg might not be as stable.d  " But yes, it would be nice to have.  <                                            [Stephen Hoffman]  < ------------------------------------------------------------? VMS12.  Are there any general-access OpenVMS systems available?,   Yes.  
   o Hobbes  ?       Hobbes is a MicroVAX 3100 Model 40 for which free access o>       and accounts are available to OpenVMS enthusiasts. This C       system has BASIC, Pascal, Fortran, and C compilers installed.dD       If you would like an account on Hobbes, please see the FAQ at:  $         http://www.hobbesthevax.com/  5       This system is strictly for non-commercial use.g  E                                      [Scott Squires, Steven Shamlian]b     o OpenVMS Galaxy Test Driveh  B       Compaq currently offers an OpenVMS Galaxy Test Drive system,F       based on an AlphaServer 4100 series configured as two instances @       of the OpenVMS operating system.  For details, please see:  /         http://www.testdrive.compaq.com/galaxy/t     o Compaq CSA Test Drive:  &       http://www.testdrive.compaq.com/   < ------------------------------------------------------------* VMS13.  What version of OpenVMS do I need?  6 For information on supported platforms, please see the2 OpenVMS Software Product Description (SPD) for the' particular OpenVMS version of interest.   !   http://www.compaq.com/info/spd/s:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  6 For a table of OpenVMS versions for various platforms, please see:h  9   http://www.openvms.compaq.com/openvms/supportchart.htmlt  : For information on the Multia, related Alpha single-board : computers, or other officially unsupported systems, please see ALPHA8 and ALPHA13.p  < The following is a rule-of-thumb for Alpha platform support.; The table contains the earliest OpenVMS Alpha release with s9 support for a particular series of Alpha microprocessors:s  $ Microprocessor | OpenVMS   | General%   Generation   | Version   | Commentsf  G   21064  EV4   : V1.0      : few systems; most EV4 req later; upg availt5   21164  EV5   : V6.2      : subsequent upg availableo=   21164A EV56  : V6.2-1H3  : subsequent upg to V7.1 and lateroH   21264  EV6   : V7.1-2    : subsequent upg typically to V7.2-1 or laterH   21264A EV67  : V7.1-2    : subsequent upg typically to V7.2-1 or laterE   xxxxxx EV68  : V7.2-1    : believed/probable; currently expectationo    < ------------------------------------------------------------* VMS14.  How can I submit OpenVMS Freeware?  ?   For the guidelines and submission info, please visit the URL:t  @     http://www.openvms.compaq.com/openvms/freeware/cd_guide.html  B   To order a Freeware CD-ROM kit, request part number QA-6KZAA-H8.  < ------------------------------------------------------------( VMS15.  Porting applications to OpenVMS?  C Porting can range from simple to rather complex, and depends on the ' features used on the original platform.e  A This section covers generic porting, and porting from OpenVMS VAXW@ to OpenVMS Alpha.  (Porting from OpenVMS VAX to OpenVMS Alpha is@ often quite simple and involves little more than rebuilding fromF source, though a few applications using features specific to VAX will ( require some additional effort to port.)  A Several manuals on porting from OpenVMS VAX to OpenVMS Alpha are -B available in the OpenVMS documentation set, including information A on porting VAX Macro32 assembler code to the Macro32 compiler on pB OpenVMS Alpha, on management differences, on upgrading privileged   code, and application migration:  %   http://www.openvms.compaq.com:8000/P$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/   : Details on the C programming environment are available at:  9   http://www.openvms.compaq.com/commercial/c/c_index.html   : Details on porting VAX C to Compaq C are are available at:  :   http://www.openvms.compaq.com/commercial/c/index_vax.htm  + An OpenVMS Porting Library is available at:   A   http://www.openvms.compaq.com/openvms/products/ips/porting.html   A Information on the Enterprise Toolkit, a Visual-based developmentoE environment for developing applications for OpenVMS using a Microsofti platform, is available at:  ;   http://www.openvms.compaq.com/commercial/et/et_index.htmlu  L Details on DCE, CORBA, BridgeWorks, and COM/DCOM middleware is available at:  :   http://www.openvms.compaq.com/commercial/middleware.html  1 Information on the COE standards is available at:-     http://diicoe.disa.mil/coe/   C A wide variety of programming development tools and middleware are VA available as commercial products (eg: DECset, IBM MQseries), and pC various tools are also available as shareware or Freeware.  Please u/ see other sections of this FAQ, and please see:s  ,   http://www.partner.compaq.com/www-catalog/  a< ------------------------------------------------------------0 VMS16.  How do I join Compaq Solutions Alliance?  G The Compaq Solutions Alliance (CSA) is a (free) program that is open toaH and that supports software partners, consultants, and service providers:     http://www.compaq.com/csa/  H CSA provides members with discounts on hardware, porting assistance, and many other benefits.  H For those familiar with the program, the DIGITAL Association of SoftwareG and Application Parterns (ASAP) program has been incorporated into CSA.o  H The Compaq Solutions Alliance Technical Journal (CTJ) is "web-published" monthly, and available at:  3   http://csa.compaq.com/CompaqTechnicalJournal.htmlg  < ------------------------------------------------------------: DOC1.   Where can I find online copies of OpenVMS manuals?  D The Compaq OpenVMS and layered product documentation is copyrighted 	 material.p  C HTML format on-line product documentation sets for specific Compaq  , OpenVMS products are presently available at:  %   http://www.openvms.compaq.com:8000/e$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/q  F Documentation is offered on separately orderable CD-ROM media through J a subscription to the Consolidated On-Line Documentation (ConOLD) product M (see VMS7.)  ConOLD manuals are readable with BNU, a viewer that is supplied sK with the documentation distribution.  BNU can display HTML, Bookreader, ande! documentation in other formats.  s  E MGBOOK, a viewer for Bookreader-format documentation is available foriI character-cell terminals (eg. VTxxx) via the WKU VMS Freeware file servero" -- see question SOFT1 for details. 					[Steve Lionel]o 					[Stephen Hoffman]    < ------------------------------------------------------------- DOC2.   What online information is available?c  M On your OpenVMS system, the HELP command can provide a wealth of information,oJ not only on DCL commands but on system services (HELP System_Services) andJ Run-Time Library routines (HELP RTL_Routines).  The introduction displayedK when you type the HELP command with no additional keywords provides furtherp	 pointers.w  E OpenVMS Marketing runs a WWW server at http://www.compaq.com/openvms/mL (http://www.openvms.compaq.com/).  Here, you will find product information, K strategy documents, the contents of the latest OpenVMS Freeware CD-ROM and e
 much more.  L Software Product Descriptions (SPDs) for most every OpenVMS-related product  Compaq sells is available via:  !   http://www.compaq.com/info/spd/.  L System performance data (see ALPHA5), product infosheets, release notes and  much more are also available.    In addition,     http://search.compaq.com/   H provides a handy method to search all of Compaq's public web servers for information of any kind.  G Compaq's Customer Services organization also hosts an Internet server. tD Various contract-access and non-contract access ECO (patch) kits are available at the URL:c  7   http://ftp.digital.com.au/pub/ecoinfo/ecoinfo/top.htm %   http://search.service.digital.com/ s   For ftp access use        ftp://ftp.service.digital.com/  E The Compaq Systems and Options Catalog (SOC) archive is available at:l  1   http://www.digital.com/info/SOHOME/SOHOMEHM.HTMc  G The Systems and Options Catalog has been replaced by Compaq QuickSpecs:h  @   http://www.compaq.com/products/quickspecs/productbulletin.html  I The Compaq DSNlink electronic product support network (a good source for VH reporting problems, obtaining patches and ECOs, scanning Compaq support @ databases, searching for example programs, etc) is available at:  (   http://www.support.compaq.com/dsnlink/  H Compaq's Business Link provides product information, prices and permits  online ordering:  &    http://www.businesslink.compaq.com/  E The services provided by BusinessLink are being replaced by other andoB country-specific mechanisms, please see the above URL for details.  C Information on Compaq hardware, software, products and services is d, available through various telephone numbers:  G     1-800-AT-COMPAQ     : voice : Compaq (including DIGITAL and Tandem)e7                                   products and servicesl9     1-800-DIGITAL	: voice : DIGITAL products and services,0     1-800-DEC-2717	: voice : The DECchip Hotline9     1-508-568-6868	: voice : (alternate number for above)w>     1-800-STORWORK      : voice : The Compaq StorageWorks team  G David Mathog offers two HTML documents which contain useful informationm about OpenVMS.  7   http://seqaxp.bio.caltech.edu:8000/www/vms_sheet.html ?   http://seqaxp.bio.caltech.edu:8000/www/vms_beginners_faq.html-  9 The VAXarchive (hardware and software information) is at:n&   http://vax.sevensages.org/index.html  I Useful OpenVMS information and an extensive set of links is available at:s   http://www.levitte.org/~ava/  @ A wide variety of Compaq VAX, Alpha, platform and other product B documentation (some introductory, some technical) is available at:  0   http://www.digital.com/lists/master-index.html7   http://www.compaq.com/support/techpubs/qrg/index.html   C The Compaq inFORM magazine and OpenVMS Times newsletters have emailn subscriptions available, see:-  !     http://www.compaq.com/inFORM/-/     http://www.openvms.compaq.com/openvmstimes/-  ) Also see the DFWCUG Longwords newsletter:-       http://www.dfwcug.org/    < ------------------------------------------------------------2 DOC3.   What books and publications are available?  C A bibliography of current and recent OpenVMS books is available at:a  ,   http://www.levitte.org/~ava/vms_book.htmlx  C The Butterworth-Heinemann Digital Press imprint offers a number of b* OpenVMS books.  A website is available at:     http://www.bh.com/  ; Information on specific OpenVMS books is also available at:o  2   http://www.openvms.compaq.com/openvms/books.html   Also see DOC10.a    < ------------------------------------------------------------E DOC4.   How do I extract the contents of a HELP topic to a text file?2  J To extract all the text of a HELP topic (and its subtopics) to a text fileE for perusal with a text editor, printing out, etc., use the followinge command:  7      $ HELP/OUT=filename.txt help-topic [help-subtopic]-  B If the help text you want is not in the standard help library (forC example, it's help for a utility such as MAIL that has its own helpnE library), add /LIBRARY=libname after the HELP verb.  To see the namesp8 of help library files, do a directory of SYS$HELP:*.HLB.  < ------------------------------------------------------------6 DOC5.   Does OpenVMS Marketing have an e-mail address?  F Yes - if you can't get the answers to questions elsewhere, if you haveJ comments or complaints about OpenVMS, send mail to openvms-info@compaq.comI (This address is NOT a support channel, and is solely intended to provideLK informal method to communicate directly with members of OpenVMS Marketing.)   < ------------------------------------------------------------5 DOC6.   What OpenVMS-related WWW sites are available?-  F     http://www.openvms.compaq.com/    (Sponsored by OpenVMS Marketing)C     http://www.montagar.com/          (Sponsored by DECUS - DFWLUG)o@     http://www.levitte.org/~ava/      (Sponsored by Arne Vajhj)B     http://www.saiga.com/             (Sponsored by Saiga Systems)?     http://www.tachysoft.com/	      (Sponsored by Wayne Sewell)oD     http://www.progis.de/openvms.htm  (Sponsored by proGIS Software)A     http://www.jcameron.com/vms/      (Sponsored by Jeff Cameron)V  A The following web site is sponsored by "The Beave", and provides dC information that is directly relevent to system managers, security eC managers, and others interested in ensuring the continued security d of OpenVMS systems:n  3     http://www.vistech.net/users/beave/hack-vms-faq   E Suggestions (indirectly) provided by the above include disabling the  > port 11 and 15 stats provided by IP packages such as Multinet.  < ------------------------------------------------------------ DOC7.   removed.  See MGMT25.-  < ------------------------------------------------------------B DOC8.   Where can I find info about undocumented OpenVMS features?  E After all this discussion about undocumented VMS features I started ai4 collection of some documentation :-)) about them on   4     http://www.decus.de:8080/www/vms/qaa/undoc.htmlx 						[zinser@axp603.gsi.de]G                                                 [HORN@exchng1.shsu.edu]e   Also see the following:a  -     http://www.levitte.org/~ava/vms_tip.htmlxo=                                                 [Arne Vajhj]u  C Various examples of undocumented features are also available on the  OpenVMS Freeware:o  +     http://www.openvms.compaq.com/freeware/o  @ DOC9.   Where is documentation on the DECnet Phase IV protocols?< ------------------------------------------------------------  3 Specifications for DECnet Phase IV can be found at:w  ?     http://gatekeeper.dec.com/pub/DEC/DECnet/PhaseIV/index.htmla  < ------------------------------------------------------------G DOC10.  Where can I learn about how the VMS executive works internally?a  H The OpenVMS Internals and Data Structure manual (IDSM) explains how the F OpenVMS executive works. The book covers the operating system kernel: B process management; memory management; the I/O subsystem; and the H mechanisms that transfer control to, from, and among these. It gives an I overview of a particular area of the system, followed by descriptions of bF the data structures related to that area and details of the code that  implements the area.  H The first edition of the OpenVMS Alpha internals book describes Version H 1.5.  Although there have been several releases of  OpenVMS Alpha since G Version 1.5 (V6.1, V6.2, V7.0, V7.1, etc) and many details in the book nD are no longer accurate, it continues to provide a strong conceptual " description of OpenVMS internals.   I This book has been split into five pieces, each to be updated separately.tM The first such volume, published in early 1997, was "OpenVMS Alpha Internals cG and Data Structures: Scheduling and Process Control," which covers the  M Version 7.0 implementation of true multithreading and the changed scheduling p model it implies.l  F The internals books are available through Digital Press, an imprint ofC Butterworth-Heinemann. You can order by phone (from US and Canada, lF 1-800-366-2655, or from elsewhere, 781-904-2500). You can also fax an G order to 1-800-446-6520 or 781-933-6333. The order form and additional  8 information are available on their web site www.bh.com .   ISBN           Title  F 1 55558 156 0  OpenVMS Alpha Internals: Scheduling and Process ControlE 1 55558 120 X  OpenVMS AXP Internals and Data Structures: Version 1.5pA 1 55558 059 9  VAX/VMS Internals and Data Structures: Version 5.2t   					[Ruth Goldenberg]  < ------------------------------------------------------------D DOC11.  Where can new users find tutorial information about OpenVMS?  P First, see if your local site has information on this topic.  Each site can haveM site-specific features and configuration.  Some sites will have site-specifictH new user's documentation, covering various site-specific things that areG difficult or impossible for the general OpenVMS documentation to cover.i  L Various introductory manuals are available in the OpenVMS documentation set,J including the OpenVMS User's Guide.  The OpenVMS manuals -- including the ) OpenVMS User's Guide -- are available at:   %   http://www.openvms.compaq.com:8000/h$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/-  C Some of the OpenVMS books available from the Butterworth-Heinemann  2 Digital Press imprint (http://www.bh.com) include:  ,        Introduction to OpenVMS, 5th Edition,        Lesley Ogilvie Rice        ISBN 1 55558 194 3e  /        The OpenVMS User's Guide, Second Editiont        Patrick Holmayo        ISBN 1 55558 203 6a          Introduction to OpenVMS        David W Bynon        ISBN 1 878956 61 2   &        OpenVMS System Management Guide        Richard Berry        ISBN 1 55558 143 9   )        Using DECwindows Motif for OpenVMS         Margie Sherlock        ISBN 1 55558 114 5s  3        Writing Real Programs in DCL, Second Editionl"        Hoffman and Anagnostopoulos        ISBN 1 55558 191 9e  1   For various features OpenVMS books, please see:o4     http://www.openvms.compaq.com/openvms/books.html  B   Various user-maintained websites are also available, including aD   beginner's FAQ, various user-written FAQs, a bibliography of booksD   on OpenVMS, and information on various other hardware and software	   topics:?  -     http://www.levitte.org/~ava/vms_faq.htmlxe.     http://www.levitte.org/~ava/vms_book.htmlx4     http://seqaxp.bio.caltech.edu/www/vms_sheet.html<     http://seqaxp.bio.caltech.edu/www/vms_beginners_faq.html?     http://multivac.jb.man.ac.uk:8000/helbig/BOOKMARKS/VMS.HTMLr  D   Members of the DECUS DFWLUG maintain a website with many materialsE   available, including an Overview of OpenVMS, an Introduction to DCLt>   and the TPU Editor, Advanced DCL Command Procedures, OpenVMSH   Operations: Batch, Print, Tape, an Introduction to OpenVMS Management,C   to OpenVMS User Management, to OpenVMS Network Management, and topA   OpenVMS Cluster Management.  These training materials have beenaB   presented at various DECUS symposia, and can be downloaded from:  *     http://www.montagar.com/openvms_class/  @   Compaq offers training information and Technical Resource Kits+   (TRKs) and other Training for OpenVMS at:l  ,     http://www.compaq.com/training/home.html0     http://www.openvms.compaq.com/wbt/index.html  ?   An OpenVMS certification (testing) program is also available.   (   The following URL has an OpenVMS Quiz:      http://www.jcameron.com/vms/  E   CCSS Interactive Learning has OpenVMS training materials available:-     http://www.CCSScorp.com/      AcerSoft Training information:     http://www.acersoft.com/     MindIQ training information:     http://www.mindiq.com/  < ------------------------------------------------------------? DOC12.  Access to the OpenVMS Netscape Navigator documentation?   =   The documentation URLs embedded into the browser itself may1:   not operate correctly in all cases, and (for reasons not;   worthy of repeating here) redirects may not be available.e  0   You can manually access the documentation via:3     http://www.openvms.compaq.com:88/netscape/help/e  < ------------------------------------------------------------8 TIME1.   A brief history of OpenVMS Timekeeping, please?  =   Why does OpenVMS regards November 17, 1858 as the beginningV   of time...  D   The modified Julian date adopted by the Smithsonian Astrophysical D   Observatory (SAO) for satellite tracking is Julian Day 2400000.5, 6   which turns out to be midnight on November 17, 1858.  @   SAO started tracking satellites with an 8K (nonvirtual) 36-bit?   IBM 704 in 1957 when Sputnik went into orbit. The Julian day o@   was 2435839 on January 1, 1957. This is 11225377 octal, which C   was too big to fit into an 18-bit field. With only 8K of memory, lE   the 14 bits left over by keeping the Julian date in its own 36-bit tD   word would have been wasted.  SAO also needed the fraction of the B   current day (for which 18 bits gave enough accuracy), so it was A   decided to keep the number of days in the left 18 bits and the a5   fraction of a day in the right 18 bits of one word./  A   Eighteen bits allows the truncated Julian day (the SAO day) to oA   grow as large as 262143, which from November 17, 1858, allowed iB   for 7 centuries. Possibly, the date could only grow as large as @   131071 (using 17 bits), but this still covers 3 centuries and B   leaves the possibility of representing negative time.  The 1858 D   date preceded the oldest star catalogue in use at SAO, which also G   avoided having to use negative time in any of the satellite tracking .   calculations.   D   The original Julian Day (JD) is used by astronomers and expressed D   in days since noon January 1, 4713 B.C.  This measure of time was E   introduced by Joseph Scaliger in the 16th century.  It is named in tE   honor of his father, Julius Caesar Scaliger (note that this Julian aB   Day is different from the Julian calendar that is named for the     Roman Emperor Julius Caesar!).  F   Why 4713 BC?  Scaliger traced three time cycles and found that they C   were all in the first year of their cyle in 4713 B.C.  The three rD   cycles are 15, 19, and 28 years long.  By multiplying these three C   numbers (15 * 19 * 28 = 7980), he was able to represent any date c"   from 4713 B.C. through 3267 A.D.  E   The starting year was before any historical event known to him.  In E   fact, the Jewish calendar marks the start of the world as 3761 B.C. G   Today his numbering scheme is still used by astronomers to avoid the  F   difficulties of converting the months of different calendars in use    during different eras.     The following web sites:  F     http://www.openvms.compaq.com/openvms/products/year-2000/leap.html  #     http://www.eecis.udel.edu/~ntp/p     http://www.nist.gov//     http://www.bldrdoc.gov/timefreq/faq/faq.htmd)     http://www.boulder.nist.gov/timefreq/ /     http://www.tondering.dk/claus/calendar.html   E   are all good time-related resources, some general and some specifico
   to OpenVMS.w  % 					[Stephen Hoffman, Dale Dellutri]e    < ------------------------------------------------------------3 TIME2.   How does OpenVMS VAX maintain system time?i  ?   VAX systems maintain an interval clock, and a hardware clock.   H   The VAX hardware clock is called the TOY ("Time Of Year") clock.  The F   register associated with the clock is called the TODR ("Time Of Day 
   Register").w  J   The TOY clock -- as used -- stores time relative to January first of theL   current year, starting at at 00:00:00.00.  It is a 100 Hz, 32-bit counter,D   incremented every 10ms, and thus has a capacity of circa 497 days.  H   OpenVMS (on the VAX platform) stores system date information -- and inJ   particular, the current year -- in the system image, SYS$SYSTEM:SYS.EXE.   G   The TOY is used, in conjunction with the base date that is stored andiJ   retrieved from the system image, to initialize the interval clock value #   that is stored in EXE$GQ_SYSTIME.y  M   Once the interval clock is loaded, the system does not typically reference wH   the TOY again, unless a SET TIME (with no parameters) is issued.  The J   interval clock value is updated by a periodic IPL22 or IPL24 (depending I   on the specific implementation) interrupt.  (When these interrupts are aD   blocked as a result of the activity of higher-IPL code -- such as J   extensive driver interrupt activity or a hardware error or a correctableI   (soft) memory error -- the clock will "loose" time, and the time value h8   reported to the user with appear to have slowed down.)  J   On most (all?) VAX systems, the battery that is associated with the TOY I   clock can be disconnected and replaced if (when) it fails -- TOY clock oJ   problems in VAX systems do regularly get tracked back to a failed nicad    or lithium battery pack. 					[Stephen Hoffman]  < ------------------------------------------------------------' TIME3.   Why does my system time drift?/  D   Memory errors, hardware problems, or most anything operating at orD   above IPL 22 or IPL 24 (clock IPL is system family dependent; codeB   executing at or above the clock IPL will block the processing ofE   clock interrupts), can cause the loss of system time.  Clock drift  E   can also be caused by normal (thermal) clock variations and even bye$   the expected level of clock drift.  C   When clock interrupts are blocked as a result of the activity of bD   high-IPL code -- such as extensive driver interrupt activity or a C   hardware error or a correctable (soft) memory error -- the clock tB   will "loose" time, and the time value reported to the user with A   appear to have slowed down.  Correctable memory errors can be ai3   common cause of system time loss, in other words.n  G   Clock drift can also be (deliberately) caused by the activity of the s   DTSS or NTP packages.e  $   Also see ALPHA17, VAX8, and TIME8.  < ------------------------------------------------------------D TIME4.   Managing Timezones, Timekeeping, UTC, and Daylight Savings?  -   You will want to use the command procedure:   #     SYS$MANAGER:UTC$TIME_SETUP.COM    I   to configure the OpenVMS Timezone Differential Factor (TDF) on OpenVMS vH   V6.0 and later.  Select the BOTH option.  This configures the OpenVMS C   TDF settings, though it may or may not configure the TDF and the k=   timezone rules needed or used by other software packages.  u  A   Please do NOT directly invoke the following command procedures::  =     SYS$MANAGER:UTC$CONFIGURE_TDF.COM   ! do not directly usew=     SYS$MANAGER:UTC$TIMEZONE_SETUP.COM  ! do not directly user  G   TCP/IP Services V5.0 and later use the OpenVMS TDF, UTC, and timezoneeF   support.  Earlier versions use a TDF mechanism and timezone databaseG   that is internal to the TCP/IP Services package.  Also on the earlier G   versions, the TDF must be manually configured within TCP/IP Services,a6   in addition to the OpenVMS configuration of the TDF.  G   DECnet-Plus in V7.3 and later uses the OpenVMS TDF, UTC, and timezoneoH   support.  Earlier versions use a TDF TDF mechanism, timezone database,H   and automatic switch-over that is internal to the DECnet-Plus package.A   Also on earlier versions, the TDF must be configured within the G   DECnet-Plus DECdtss package, in addition to the OpenVMS configuration-
   of the TDF.-  G   Application code using Compaq C (formerly DEC C) will use the OpenVMS H   UTC and TDF mechanisms when the C code is compiled on OpenVMS V7.0 andJ   later (and when the macro _VMS_V6_SOURCE is NOT defined).  Compaq C doesH   NOT use the OpenVMS UTC and TDF mechanisms when the C code is compiledI   on OpenVMS releases prior to V7.0, or when the preprocessor declarationa   _VMS_V6_SOURCE is declared.w     DCE DTSS TDF details TDB.o  E   In OpenVMS Alpha V6.1, V6.2, and V6.2-1Hx, the TDF value is written-D   to SYS$BASE_IMAGE.EXE.  With OpenVMS Alpha V7.0 and later and withF   OpenVMS VAX V6.0 and later, SYS$SYSTEM:SYS$TIMEZONE.DAT contains theG   TDF.  This means that OpenVMS Alpha systems will need to have the TDFt2   value reset manually on reboots prior to V7.0.    I   During OpenVMS Bootstrap, the SYSINIT module reads SYS$TIMEZONE.DAT to nI   acquire the TDF for use in the system global cell EXE$GQ_TDF.  This is  H   done to ensure that the system boots with a valid TDF. The UTC system F   services get the TDF from this cell. These services, as well as the I   Compaq C RTL, must have a valid TDF.  (Prior to OpenVMS V7.3, if either-G   DECnet-Plus or DECnet/VAX Extensions is configured and run, the imageuI   DTSS$SET_TIMEZONE.EXE is invoked and can override the TDF and timezone pK   rule settings from SYSINIT or from UTC$TIME_SETUP.COM -- this image runs NK   even if DTSS is disabled.  If the settings do not match, DTSS will reset c'   the values to match its definitions.)M  D   Prior to OpenVMS V7.3, daylight savings time switchover is handledE   automatically only when DCE DTSS or DECnet-Plus DTSS is in use.  IntA   V7.3, OpenVMS can be configured to automatically switch over to D   daylight savings time, and also generates an event that interestedF   applications can use to detect the switch-over between standard time   and daylight time.  G   The manual switchover between daylight savings time and standard timeSE   is correctly accomplished via the SYS$EXAMPLES:DAYLIGHT_SAVINGS.COMs   command procedure procedure.  G   If you switch the TDF or daylight savings time setting, you will alsonH   want to restart or reconfigure any time-sensitive applications (those H   not using the time change event in V7.3 and later).  Examples of theseH   applications include the need to restart the NFS client and (yes) NTP.G   (NTP will want to try to "drift" the time (see TIME6), and will find cG   the daylight savings time switch-over to be far too large to "drift".pF   Hence the NTP restart.)  You can also use the (undocumented) TCP/IP $   Services (prior to V5.0) commands:  4     SET TIME/DIFF=[positive or negative TDF integer]     GENERATE TIME   1   to reset the value of the logical name UCX$TDF.n     Prior to V7.3, the command:f        MCR DTSS$SET_TIMEZONE MODIFY  J   can be used to modify the settings of the SYS$TIMEZONE_DAYLIGHT_SAVING, G   SYS$TIMEZONE_DIFFERENTIAL, and SYS$TIMEZONE_NAME system logical namesz!   based on the SYS$TIMEZONE_RULE.   F   For information on ZIC and related tools used to manage the OpenVMS E   Timezone database, please see the DEC C Run-time Library Utilities  C   Reference Manual -- though the title would imply otherwise, this mF   particular manual is part of the OpenVMS documentation set, and not :   part of the Compaq C (formerly DEC C) documentation set.  < ------------------------------------------------------------5 TIME5.   How to troubleshoot TDF problems on OpenVMS?-  F   This is an OpenVMS Alpha system prior to V7.0 and the startup is not   invoking the procedure:E  !    SYS$MANAGER:UTC$TIME_SETUP.COM-  D   This is an OpenVMS system prior to V6.0, where there is no OpenVMS   TDF nor UTC available.  D   The version of the application does not use the OpenVMS TDF.  ThisF   includes TCP/IP Services prior to V5.0, applications using Compaq C D   built on or targeting OpenVMS prior to V7.0, and systems using theC   DECnet-Plus DTSS mechanisms prior to the release associated with o   OpenVMS V7.3.  (DCE TDF TBD.)   K   If you should find either of the following two timezone-related database  )   files located in SYS$SPECIFIC:[SYSEXE]:t  +     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DAT /     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DATb  H   These two files are in an erroneous location and must be recreated in    the correct directory:       SYS$COMMON:[SYSEXE].     If the DCL command:s  *     DIRECTORY SYS$SYSTEM:SYS$TIMEZONE*.DAT  G   shows these files in SYS$SPECIFIC:[SYSEXE], then delete them and use  2   SYS$MANAGER:UTC$TIME_SETUP.COM to recreate them.  1   On OpenVMS versions prior to V7.3, if the file:i  $     SYS$STARTUP:DTSS$UTC_STARTUP.COM  9   is present on your system, then you may need to invoke:o  -     SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COMn  @   to recreate the timezone files correctly.  Invoke this commandB   immediately after [re]executing SYS$MANAGER:UTC$TIME_SETUP.COM.)  E   If SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM is not present on yourn>   system, then you may need to execute the following commands:  +     DELETE SYS$STARTUP:DTSS$UTC_STARTUP.COM9+     DEASSIGN/SYSTEM/EXEC SYS$TIMEZONE_RULE.o  < ------------------------------------------------------------= TIME6.   How can I keep the OpenVMS system time synchronized?i  F   To help keep more accurate system time or to keep your system clocksG   synchronized, TCP/IP Services NTP, DECnet-Plus DECdtss, DCE DTSS, andsF   other techniques are commonly used.  If you do not have IP access toA   a time-base, then you could use dial-up access to NIST or othert   authoritative site.u  C   There exists code around that processes the digital (ie: binary) iD   format time that is available via a modem call into the NIST clockC   (the Automated Computer Telephone Service (ACTS)), and code that v@   grabs the time off a GPS receiver digital link, or a receiver D   (effectively a radio and a codec) that processes the time signals E   from radio station WWV, WWVH, WWVB, or similar.  (Processing these p@   time protocols often involves little more than reading from anB   EIA232 (RS232) serial line from the receiver, something that is @   possible from most any language as well as directly from DCL.)  C   One example of acquring a time-base involves the IRIG time formatmC   (IRIG-A, -B, -G), a binary signal containing the current time in mG   hours, minutes, seconds and days since the start of the current year. G   IRIG can also contain the time of day as the number of seconds since dI   midnight.  Compaq Custom Systems and third-party vendors offer various  :   IRIG-based reader/generator modules for OpenVMS systems.  G   Differing time servers (DECnet-Plus DTSS, DCE DTSS, NTP, etc) do not dF   coexist particularly well, particularly if you try to use all these H   together on the same node.  Please pick and use just one.  (If needed,G   you can sometimes configure one package to acquire its timebase from oI   another protocol, but one and only one time server package should have lJ   direct control over the management of and drifting of the local OpenVMS    system time.)      Useful URLs:8     http://www.boulder.nist.gov/timefreq/service/nts.htm9     http://www.boulder.nist.gov/timefreq/service/acts.htmm)     http://www.boulder.nist.gov/timefreq/e     http://www.time.gov/  < ------------------------------------------------------------D TIME7.   How can I configure TCP/IP Services NTP as a time provider?  C   An NTP time provider provides its idea of the current time to NTP E   clients via the NTP protocol.  Most systems are NTP clients, but...r  F   NTP has a heirarchy of layers, called strata.  The further away fromG   the actual NTP time source (Internet time servers are at stratum 1),  G   the lower the strata (and the larger the number assigned the statum).i  H   NTP explicity configured at stratum one provides time to NTP operatingG   at lower strata, and the provided time is acquired based on the local B   system time or via some locally-accessable external time source.  J   NTP at other (lower) strata both receive time from higher strata and canK   provide time to lower strata, and automatically adjust the local stratum.TJ   The highest stratum is one, and the lowest available stratum is fifteen.  H   The TCP/IP Services NTP package can operate at any stratum, and can be>   configured as a peer, as a client, or as a broadcast server.  I   With TCP/IP Services V5.0 and later, the only supported reference clockSI   is the LCL (local system clock).  If your system has an excellent clock/F   or if the system time is being controlled by some other time serviceI   (such as DTSS or GPS), you can configure NTP to use the system clock as H   its reference source.  This will mimic the master-clock functionality,F   and will configre NTP as a stratum 1 time server.  To do this, enter+   the following commands in TCPIP$NTP.CONF:a       server 127.127.1.0 preferl     fudge 127.127.1.0 stratum 0o  G   For local-master functionality, the commands are very similiar.  Use:l       server 127.127.1.0     fudge 127.127.1.0 stratum 8m  F   The difference between these two is the stratum, and the omission ofE   the prefer keyword.  Specifying a higher stratum allows the node tosG   act as a backup NTP server, or potentially as the sole time server onfI   an isolated network.  The server will become active only when all otheriF   normal synchronization sources are unavailable.  The use of "prefer"J   causes NTP to always use the specified clock as the time synchronization	   source.t  I   With the TCP/IP Services versions prior to V5.0, the NTP management is nG   rather more primitive.  To configure the local OpenVMS system from an2K   NTP client to an NTP server (on TCP/IP Services versions prior to V5.0), fH   add the following line to the sys$specific:[ucx$ntp]ucx$ntp.conf file:       master-clock 1  E   Also, for TCP/IP Services prior to V5.0, see the NTP template file:f  *     SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE  8   For current TCP/IP Services documentation, please see:  '     http://www.openvms.compaq.com:8000/g&     http://www.openvms.compaq.com/doc/    < ------------------------------------------------------------1 TIME8.   How can I drift the OpenVMS system time?w  J   With DECdts and TCP/IP Services NTP, the system time value is "drifted" H   (rather than changed), to avoid the obvious problems that would arise I   with "negative time changes".  The same basic clock drifting technique  K   is used by most (all?) time servers operating on OpenVMS, typically usinga8   the support for this provided directly within OpenVMS.  G   An example of the technique used (on OpenVMS VAX) to drift the system 4   time is the SETCLOCK tool on the OpenVMS Freeware.  L   For information on the use of the EXE$GL_TIMEADJUST and EXE$GL_TICKLENGTH J   cells on OpenVMS Alpha, see _OpenVMS AXP Internal and Data Structures",    located on page 348.  < ------------------------------------------------------------; TIME9.   Why does VAX need a SET TIME at least once a year?i  K   Because the VAX Time Of Year (TOY) has a resolution of 497 days, the VAX 7L   system time is stored using both the TOY and the OpenVMS VAX system image J   SYS.EXE.  Because of the use of the combination of the TOY and SYS.EXE, J   you need to issue a SET TIME command (with no parameters) at least once J   between January 1st and about April 11th of each year, and whenever you K   change system images (due to booting another OpenVMS VAX system, booting sD   the standalone BACKUP image, an ECO that replaces SYS.EXE, etc).    G   The SET TIME command is automatically issued during various standard wK   OpenVMS procedures such as SHUTDOWN, and it can also obviously be issued 0H   directly by a suitably privileged user.  Issuing the SET TIME command J   resets the value stored in the TOY, and (if necessary) also updates the K   portion of the time (the current year) saved in the SYS.EXE system image.r  H   This VAX TOY limit is the reason why OpenVMS VAX installation kits andI   standalone BACKUP explicitly prompt for the time during bootstrap, and -G   why the time value can "get weird" if the system crashes outside the nI   497 day window (if no SET TIME was issued to update the saved values), aK   and why the time value can "get weird" if a different SYS$SYSTEM:SYS.EXE c:   is used (alternate system disk, standalone BACKUP, etc).  < ------------------------------------------------------------A TIME10.   Why can't I do a SET TIME command?  Help managing DTSS?   D If you try to set the system time with the SET TIME command, and see one of the following messages:  # %SET-E-NOTSET, error modifying time 0 -SYSTEM-F-IVSSRQ, invalid system service request  # %SET-E-NOTSET, error modifying time K -SYSTEM-E-TIMENOTSET, time service enabled; enter a time service command too update the timee    N A: This occurs if the time on the local system is controlled by a time serviceN software, for example the distributed time service software (DTSS) provided asO part of the DECnet/OSI installation. The DTSS software communicates with one oruL more time servers to obtain the current time. It entirely controls the localK system time (for DECnet/OSI, there is a process named DTSS$CLERK for this);mO therefore, the usage of the SET TIME command (and the underlying $SETTIM systema service) is disabled.o  N The first message is displayed on systems running DECnet/OSI V6.1 and earlier.M On systems with newer DECnet/OSI (DECnet-Plus) software, the second (and morel informative) message is given.  I You shouldn't have to change the time manually - you should be doing thishM through the time server - but if you insist...  you'll have to shutdown DTSS:e  	 $ MCR NCL- NCL> DISABLE DTSSb NCL> DELETE DTSS  L This will shutdown DTSS$CLERK. You may then change the system time as usual." To restart the DTSS software, type   @SYS$STARTUP:DTSS$STARTUP-  M You'll need a lot of privs : (CMKRNL,SYSPRV,OPER,SYSNAM,PRMMBX,NETMBX,LOG_IO,,D ALTPRI) and must be granted the NET$MANAGE identifer to shutdown and
 restart DTSS. ?                                         [bol@adv.magwien.gv.at]   N If you wish to "permanently" disable DTSS on a system running DECnet-Plus, theJ above NCL sequence must be performed each time the system is bootstrapped.  M If DTSS is running and no time servers are configured, you can (and will) seet, the following messages at regular intervals:  8 %%%%%%%%%%%  OPCOM   2-SEP-1999 19:41:20.29  %%%%%%%%%%%" Message from user SYSTEM on UNHEDI> Event: Too Few Servers Detected from: Node LOCAL:.mynode DTSS,-         at: 1999-09-02-19:41:20.296-04:00Iinfr         Number Detected=0,         Number Required=1r7         eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0Fn7         entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1B)7         streamUid  D6513A46-6135-11D3-8003-AA000400BD1Be  K You can either configure the appropriate number of time servers, or you can-G disable DTSS, or you can ignore it and (if OPCOM is set to write to theaJ log via via the logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE) clean out OPERATOR.LOG regularly.C  : You can also simply disable the display of these messages:  M $ mcr ncl block event dispatcher outbound stream local_stream global filter - ,     ((Node, DTSS), Too Few Servers Detected)  @                                                   [Wayne Sewell]  H If you wish to disable the automatic TDF adjustment for daylight savingsB time (on OpenVMS versions prior to V7.3), you can use the command:  ,   ncl> set dtss automatic TDF change = false  F or alternatively, you can set the local timezone to one that does not 8 include the automatic daylight savings time change-over.  < ------------------------------------------------------------; TIME11.   Details of the VAX and Alpha system time-keeping?l  &   VAX hardware time-keeping details...     TOY clockh   ---------vG   This is battery backed up hardware timing circuitry used to keep the tD   correct time of year during rebooting, power failures, and system C   shutdown.  This clock only keeps track of months, days, and time. G   The time is kept relative to January 1st, at 00:00:00.00 of the year     the clock was initiailized.      EXE$GQ_SYSTIME   --------------K   This is the OpenVMS VAX system time cell.  This cell contains the number tK   of 100ns intervals since a known reference.  This cell is incremented by p2   100000 every 10ms by an hardware interval timer.     EXE$GQ_TODCBASE7   ---------------dI   This cell contains the time and date the system time was last adjusted hM   by EXE$SETTIME.  It uses the same format as EXE$GQ_SYSTIME.  On adjustment aM   of the system time a copy of EXE$GQ_SYSTIME is stored in this cell in both eM   memory and on disk.  This cell is used to get the year for the system time.V  
   EXE$GL_TODRv
   ------------K   This cell contains the time and date the system time was last adjusted bynO   EXE$SETTIME. It uses the same format as the time of year clock. On adjustmentaL   of the system time this cell gets saved back to both memory and disk.  TheG   contents of this cell are used to test the validity of the TOY clock.   L   The system parameters SETTIME and TIMEPROMPTWAIT determine how the system    time will be set.T     IF SETTIME = 0J   THEN the contents of the TOY clock are compared to those of EXE$GL_TODR.  >         IF the TOY clock is more than a day behind EXE$GL_TODR/         THEN the TOY clock is presumed invalid.M  7         IF the TOY clock is within a day of EXE$GL_TODRi6         THEN the system time is calculated as follows:  O         EXE$GQ_SYSTIME = EXE$GQ_TODCBASE + ((TOY_CLOCK - EXE$GL_TODR) * 100000)o  ,   IF SETTIME = 1 or the TOY clock is invalidL   THEN the value of TIMEPROMPTWAIT determines how to reset the time of year.           IF TIMEPROMPTWAIT > 0iM         THEN the user is prompted for the time and date, for a length of time 0         equal to TIMEPROMPTWAIT microfortnights.           IF TIMEPROMPTWAIT = 0nA         THEN the time of year is the value of EXE$GL_TODR + 10ms.s  '         IF TIMEPROMPTWAIT < 0to proceeda         until they do so.s  C         THEN the user is prompted for the time and date and unable t  J   When booting a CD-ROM containing an OpenVMS VAX system, the system will I   typically be deliberately configured prompt the user to input the time s@   -- this is necessary in order to boot with the correct time.    H   If either TIMEPROMPTWAIT or SETTIME are set to zero, OpenVMS VAX will J   use the TOY clock to get the time of year, and the year will be fetched H   from the CD-ROM.  The value of the year on the CD-ROM media (saved in K   the SYS.EXE image) will most likely be that of when the CD-ROM was made, eI   and cannot be changed.  Unless the current year happens to be the same  K   year as that on the CD-ROM, most likely the year will be off.  (Further,  H   with the calculation of Leap Year also being dependent on the current ?   year, there is a possibility that the date could be off too.)       (   Alpha hardware time-keeping details...  &   Battery-Backed Watch (BB_WATCH) Chip&   ------------------------------------G   This is battery backed up hardware timing circuitry used to keep the  D   correct time of year during rebooting, power failures, and system G   shutdown.  This clock keeps track of date and time in 24 hour binary l	   format.u     EXE$GQ_SYSTIME   --------------M   This is the OpenVMS Alpha system time cell.  This cell contains the number lH   of 100ns intervals since November 17, 1858 00:00:00.00.  This cell is A   incremented by 100000 every 10ms by an hardware interval timer.p     EXE$GQ_SAVED_HWCLOCK   --------------------M   This cell is used by OpenVMS Alpha to keep track of the last time and date sF   that EXE$GQ_SYSTIME was adjusted.  It keeps the same time format as H   EXE$GQ_SYSTIME.  The value in this cell gets updated in memory and on 0   disk, every time EXE$GQ_SYSTIME gets adjusted.  e  G   - The system parameters SETTIME and TIMEPROMPTWAIT determine how the h     system time will be set.  I   - If SETTIME = 0 then EXE$INIT_HWCLOCK reads the hardware clock to set       the system time.           - IF TIMEPROMPTWAIT > 0nJ           THEN the value of TIMEPROMPTWAIT determines how long the user isL           prompted to enter the time and date.  If time expires and no time D           has been entered the system acts as if TIMEPROMPTWAIT = 0.           - IF TIMEPROMPTWAIT = 0SA           THEN the system time is calculated from the contents of$#           EXE$GQ_SAVED_HWCLOCK + 1.b           - IF TIMEPROMPTWAIT < 0oG           THEN the user is prompted for the time and date and unable to 4           continue until the information is entered.  J   Unlike the VAX, the Alpha hardware clock tracks the full date and time, H   not just the time of year.  This means it is possible to boot from theH   CD-ROM media without entering the time at the CD-ROM bootstrap.  (ThisD   provided that the time and date have been initialized, of course.)     [End of Part 1/5]e  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 29 Dec 2000 20:29:04 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/5S6 Message-ID: <92is6g$f4j$2@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part2- Posting-Frequency: monthly Last-modified: 29 Dec 2000 Version: VMS-FAQ-2.TXT(5)n    9 This is the OpenVMS Frequently Asked Questions Part 2/5. s@ Please see Part 1/5 for administrivia, indexing, archiving, etc.      < ------------------------------------------------------------# MGMT1.  What is an installed image?v  N The term "install" has two distinct meanings in OpenVMS.  The first relates toN "installing a product", which is done with either the SYS$UPDATE:VMSINSTAL.COMI command procedure or the POLYCENTER Software Installation (PCSI) utility  H (PRODUCT command).  The second meaning relates to the use of the INSTALL( utility, which is what concerns us here.  H The INSTALL utility is used to identify to OpenVMS a specific copy of anG image, either executable or shareable, which is to be given some set ofrK enhanced properties.  For example, when you issue the SET PASSWORD command,iI the image SYS$SYSTEM:SETP0.EXE is run.  That image needs to have elevatedi# privileges to perform its function.   J The other important attribute is /SHARED.  This means that shareable partsG of the image (typically read-only code and data) are loaded into memorytH only once and are shared among all users on a system.  Executable imagesH can be installed /SHARED as well as shareable library images.  (The termE "shareable" has dual meanings here, too.  See the OpenVMS Programmingy% Concepts Manual for further details.)r  M It's important to note that there is no such thing as "installing a shareablePH image with privileges".  The INSTALL utility will let you do it, but theL privileges you specify will be ignored.  To have a callable routine run withL enhanced privileges that are not available to its caller, you must constructI your routines as "user-written system services" and install the shareable H image with the /PROTECT qualifier.  See the OpenVMS Programming ConceptsG Manual for more information on user-written system services.  Note alsotK that in many cases the need to grant privileges to an image can be replacedsG with the use of the "Protected Subsystems" feature that grants a rightsqE identifier to an image.  See the OpenVMS Guide to System Security for-$ information on Protected Subsystems.  < ------------------------------------------------------------0 MGMT2.  Are there any known viruses for OpenVMS?  N Viruses are very common on PCs because the PC operating systems such as MS-DOSM and MacOS do not implement any sort of scheme to protect the operating systemhJ or the file system against hostile action by programs.  On these operatingK systems, any running program can subvert the operating system and take overxK the hardware, at which point it can do anything it wishes, including hidings9 copies of itself in other programs or in the file system.   J This is unlikely on OpenVMS, Unix, and MVS for three reasons.  First, the G operating system runs in a privileged mode in memory that is protected rF against modification by normal user programs.  Any old program cannot D take over the hardware as it can on PC operating systems.  Secondly,C OpenVMS, Unix, and MVS have file systems that can be set up so thatmJ non-privileged programs cannot modify system programs and files on disk.  H Both of these protection schemes mean that traditional PC virus schemes I don't work on these OSes.  Third, typical applications and configurationslG tend to prevent the uncontrolled execution of untrusted code as part ofi email messages or web access.u  K It is possible for OpenVMS, etc., to be infected by viruses, but to do so, iI the program containing the virus must be run from a user account that hastJ amplified privileges.  As long as the system administrator is careful thatK only trusted applications are run from such accounts (and this is generally + the case), there is no danger from viruses.s 					[Paul Winalski] 					[Stephen Hoffman]  G To protect against viruses and other attempts at system interference ortO misuse, follow the recommendations in the "OpenVMS Guide to System  Security". rJ You may also want to consider optional software products which can monitorJ your system for intrusion or infection attempts.  Computer Associates (CA)% offers various products in this area.n  H Rocksoft offers the Veracity data integrity tool (for info, send mail to demo@rocksoft.com).i  % [Contributions to this list welcomed]o  < ------------------------------------------------------------1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?c  5 ISO-9660 support was added in the following releases:t       OpenVMS VAX V6.0     OpenVMS AXP V1.5  @ An add-on ISO-9960 kit was also available for OpenVMS VAX V5.5, = V5.5-1, V5.5-2, and V5.5-2H4.  This requires the installation/? of the F11CD kit from the InfoServer CD, from the Consolidated $B Distribution CD under the InfoServer area, Customer Support Center? kit CSCPAT #1071012, or the F11CD ECO kit.  (Upgrades to V6 and0  later are strongly recommended.)  > By default, OpenVMS senses the specific type of media.  If you> are working with dual-format media -- media that uses both the@ ODS-2 and ISO-9660 formats on the same CD-ROM -- then MOUNT will@ first detect and then default to the ODS-2 format.  If you wish @ to override this and explicitly mount the media using ISO-9660,  use the command:  =     $ MOUNT/MEDIA_FORMAT=CDROM  device-name[:] [volume-label]e  > In most circumstances, you will not need nor will you want to = include an explicit /MEDIA_FORMAT specification.  For furtherS> information, please refer to the OpenVMS MOUNT Utility Manual.= Particularly note the information on the MOUNT /MEDIA_FORMAT T and /UNDEFINED_FAT qualifiers.  9 The MOUNT /UNDEFINED_FAT qualifier is of interest becausea= ISO-9660 media can be mastered on a wide variety of operating-@ system platforms, and these platforms do not necessarily supportD the semantics needed for files containing predefined record formats.C The /UNDEFINED_FAT allows you to specify the default attributes for 6 files accessed from volumes using the ISO-9660 format.  + An example which works for most CD-ROMs is:   G     $ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=STREAM:2048 DUA0: FREEWAREa  @ This particular MOUNT command forces access to the CD-ROM media = using the ISO-9660 volume structure, and the use of the MOUNTo> /UNDEFINED_FAT qualifier causes any file whose file attributes? are "undefined" to be returned with "stream" attributes with a   maximum record length 2048.   @ On OpenVMS, the ISO-9660 format is (internally) considered to be= the ODS-3 file structure, while the High Sierra extensions totA the standard are considered to be the ODS-4 file structure.  The v= Rock Ridge extensions are not currently available on OpenVMS.    					[Jim Dunham]t 					[Stephen Hoffman]  = For details on ODS-1 and ODS-2 file specifications, see Kirbyn< McCoy's VMS File System Internals Manual from Digital Press, and see:  .   http://pdp-11.trailing-edge.com/www/ods1.txt  C The OpenVMS Freeware V5.0 CD-ROM (and later) is expected to include9< a set of ODS-2 specifications located in the directory ODS2.  < ------------------------------------------------------------4 MGMT4.  How do I extract the contents of a PCSI kit?  ? A growing number of OpenVMS products are being provided in PCSI-E (POLYCENTER Software Installation) kits which are installed using the F PRODUCT INSTALL command.  These are alternatives to or replacement forD VMSINSTAL kits which were BACKUP savesets.  PCSI kits are not BACKUP< savesets and are structured differently from VMSINSTAL kits.  H If you want to extract product files from a PCSI kit, create a directoryD into which the kit should be expanded and use the following command:  8     $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] -5       /DEST=[destination-directory] /FORMAT=REFERENCEt  ? A PCSI kit file has a file specification of the following form:t  '     DEC-VAXVMS-FORTRAN-V0603-141-1.PCSIi  G In this example, "FORTRAN" is the "prodname".  PCSI will expand the kitlD files into the directory you specify and subdirectories beneath suchI as [SYSEXE], [SYSLIB], etc., reflecting the eventual destination of files(H found there.  Most of the actual product files (images, etc.) will be inG the subdirectories.  In the top-level directory will be a file with thesH file type PCSI$DESCRIPTION that specifies where various files should go.G For more details, see the POLYCENTER Software Installation Developer's aE Guide for OpenVMS, which can be found in the OpenVMS documentation onu- the Consolidated Online Documentation CD-ROM.   < ------------------------------------------------------------; MGMT5.  I've forgotten the SYSTEM password - what can I do?.  C If you need to break into an OpenVMS system because you do not haveoF access to any privileged passwords, such as the password to the SYSTEMG username, you  will need physical access to the system console, and youdB will need to perform a conversational reboot.  Here are the steps:  ?   1.  Halt the system.  Exactly how this is done depends on thesE       specific system model: Depending on the model, this can involve F       pressing the <HALT> button, entering <CTRL/P> on the console, or.       pressing the <BREAK> key on the console.  G   2.  At the >>> console prompt, use a console command to boot into the J       SYSBOOT> utility.  (SYSBOOT allows conversational changes to system I       parameters.)  The syntax for the conversational bootstrap varies by:I       system model -- this typically involves specifying a flag of 1, forr       example:           VAX:
           B/10           B/R5:1           @GENBOOD           Alpha:           b -flags 0,1  I       If your system has a non-zero system root (such as root SYSE, showneJ       here), you will have to use a console command such as the following:           VAX:           B/E0000001           B/R5:E0000001 7           @<console media procedure name varies widely>n           Alpha:           b -flags e,1     E       If your system has a hardware password (various systems supportiG       a password that prevents unauthorized access to the console), you,F       will need to know theis password and will need to enter it usingF       the LOGIN command at the console.  If you get an "Inv Cmd" errorG       trying to perform a conversational bootstrap, and you do not have F       the hardware console password for the console LOGIN command, youF       are stuck -- you will need to call for hardware service in orderF       to reset the hardware console password.  The syntax used for the(       console password mechanism varies.  G   3.  Once at the SYSBOOT> prompt, request that OpenVMS read the systemAH       startup commands directly from the system console, that the windowH       system (if any) not be started, and that OpenVMS not record these A       particular parameter changes for subsequent system reboots:t           SET/STARTUP OPA0:t         SET WINDOWSYSTEM 0         SET WRITESYSPARAMS 0         CONTINUE  H   4.  At the $ prompt, the system will now be accepting startup commandsF       directly from the console.  Type the following two DCL commands:  
         SPAWN          @SYS$SYSTEM:STARTUPr  I       The result of these two commands will be the normal system startup,1D       but you will be left logged in on the console, running under aE       privileged username.  Without the use of the SPAWN command, you 5       would be logged out when the startup completes.a  E       If necessary, you can skip the invocation of the system startup_E       temporarily, and perform tasks such as egistering license PAKs e<       or various other "single-user" maintenance operations.  >   5.  Use the following commands to reset the SYSTEM password:  A         SET DEFAULT SYS$SYSTEM:  ! or wherever SYSUAF.DAT residesm          RUN SYS$SYSTEM:AUTHORIZE+         MODIFY SYSTEM /PASSWORD=newpasswordt         EXIT  F       These steps will change the SYSTEM password to the specified new!       newpassword password value.h  I    Reboot the system normally -- the SYSTEM password should now be set toi%    the value you specified in Step 5.   M    Some people will suggest a method using the UAFALTERNATE SYSGEN parameter. L    This approach is not always reliable and is not recommended, as there canK    easily be an alternate user authorization file configured on the system.X  L    For further information on emergency startup and shutdown, as well as forJ    the official OpenVMS documentation on how to change the SYSTEM passwordL    from the console in an emergency, please see the OpenVMS System Manager's+    Manual in the OpenVMS documentation set.   K    You can also use the conversational bootstrap technique shown above (theaM    steps through Step 3) to alter various system parameters.  At the SYSBOOT>./    prompt, you can enter new parameters values:t        SHOW MAXPROCESSCNTe
      SET . 64 
      CONTINUE   H    The "." is a shorthand notation used for the last parameter examined.   					[Stephen Hoffman]  < ------------------------------------------------------------9 MGMT6.  How do I connect a PostScript printer via TCP/IP?l  H Using UCX as the TCP/IP stack, it is possible to setup queues using the F UCX$TELNETSYM in order to print to postscript printers.  This assumes J however that the printer itself can convert whatever is passed to it into I something intelligible.  As an example, if the printer has an IP address O@ of 123.456.789.101 and jobs should be passed to port 9100 then :G $ INITIALIZE/QUEUE/ON="123.456.789.101:9100"/PROCESSOR=UCX$TELNETSYM  -n
 		my_ip_queuen  D The port number of 9100 is typical of HP JetDirect cards but may be ( different for other manufacturers cards.  F As a better alternative, DCPS Version 1.4 and later support IP queues B using either Compaq TCP/IP Services for OpenVMS software or Cisco I Multinet for OpenVMS.  The usage of this type of interface is documented r8 in the Release Notes and the DCPS$STARTUP.TEMPLATE file.   					[Steve Reece]5                                         [Arne Vajhj]e  < ------------------------------------------------------------ MGMT7 moved to TIME10.  < ------------------------------------------------------------) MGMT8 removed. superceded by TIME section-  < ------------------------------------------------------------; MGMT9.  How do I change the node name of an OpenVMS System?7  D   The first step is to get a BACKUP of the system disk before makingD   any changes -- use the system disk backup procedures as documentedA   in the OpenVMS System Management Manual, making sure to use theh:   procedures and commands appropriate for the system disk.  D   Changing the node name involves a number of steps -- the node nameE   tends to be imbedded in a number of different data files around the 	   system.e  @     Update the SCSNODE in MODPARAMS.DAT, and then run AUTOGEN as7       far as the SETPARAMS phase.  (Do not reboot yet.)T@     Modify the DECnet node name.  (NETCONFIG is the DECnet Phase:       IV tool, and NET$CONFIGURE is the DECnet-Plus tool.);     Modify the IP node name.  (The UCX tool is UCX$CONFIG.)t@     Modify the host node name on the various queues in the queue@       database.  (each queue has a host name, and it defaults toD       the SCS node name of the queue's host system.  See the command*       INIT/QUEUE/ON=node for information.)C     Modify the node name saved in any application databases, or anyFD       local node-conditional operations present in the site-specificA       system startup, etc.  (SEARCH for the node name, specifyingi       all types of files.)B     Rename the SYS$NODE_oldnodename rightslist identifier to match<       the new name.  (Do not change the binary value of this       identifier.)C     Reset any license PAKs that are restricted to the old node named       to the new node name.b@     If the node name is part of a disk volume label, see MGMT19.@     Reboot the node or -- if in a VMScluster -- reboot the whole@       VMScluster.  (This tends to catch any errors immediately.)  G   There are likely a few other areas where the nodename will be stored.:  E   If the system is configured in a VMScluster and you change *either*VE   the SCSNODE or the SCSSYSTEMID -- but *not* both values -- then you$G   will have to reboot the entire VMScluster.  (The VMScluster remembersn>   the mapping between these two values, and will assume that aE   configuration problem has occured if a mismatched pair appears, and/H   will refuse to let a node with a mismatched pair join the VMScluster.)  H   To calculate the correct SCSSYSTEMID value, multiply the DECnet Phase H   IV area number by 1024, and add the DECnet Phase IV node number.  For I   example, the SCSSYSTEMID value for a DECnet node with address 19.22 is i$   19478.  ((19 * 1024) + 22 = 19478)  F   I expect I may have missed one or two configuration tools (or more!)G   that are needed at your site -- the node name tends to get stored allA?   over the place, in layered products, and in local software...t   					[Stephen Hoffman]  < ------------------------------------------------------------E MGMT10. What is the correct value for EXPECTED_VOTES in a VMScluster?l  F The VMScluster connection manager uses the concept of votes and quorumH to prevent disk and memory data corruptions -- when sufficient votes areK present for quorum, then access to resources is permitted.  When sufficienteJ votes are not present, user activity will be blocked.  The act of blockingF user activity is called a "quorum hang", and is better thought of as aG "user data integrity interlock".  This mechanism is designed to prevent J a partitioned VMScluster, and the resultant massive disk data corruptions.  K On each OpenVMS node in a VMScluster, one sets two values in SYSGEN: VOTES,hI and EXPECTED_VOTES.  The former is how many votes the node contributes toTJ the VMScluster.  The latter is the total number of votes expected when the  full VMScluster is bootstrapped.  G Some sites erroneously attempt to set EXPECTED_VOTES too low, believingoC this will allow when only a subset of voting nodes are present in a J VMScluster.  It does not.  Further, an erroneous setting in EXPECTED_VOTESI is automatically corrected once VMScluster connections to other nodes arerJ established, meaning user data is at risk of severe corruption only during the initial system bootstrap.u  G One can operate a VMScluster with one, two, or many voting nodes.  WithtH any but the two-node configuration, keeping a subset of the nodes activeA when some nodes fail can be easily configured.  With the two-node-H configuration, one must use a primary-secondary configuration (where theH primary has all the votes), a peer configuration (where when either node@ is down, the other hangs), or (preferable) a shared quorum disk.  F Use of a quorum disk does slow down VMScluster transitions somewhat --E the addition of a third voting node that contributes the vote(s) thatiH would be assigned to the quorum disk makes for faster transitions -- butL the use of a quorum disk does mean that either node in a two-node VMScluster6 configuration can operate when the other node is down.  K In a two-node VMScluster with a shared storage interconnect, typically each I node has one vote, and the quorum disk also has one vote.  EXPECTED_VOTESA is set to three.  F Using a quorum disk on a non-shared interconnect is unnecessary -- theG use of a quorum disk does not provide any value, and the votes assignedoH to the quorum disk should be assigned to the OpenVMS host serving access to the disk.  D For information on quorum hangs, see the OpenVMS documentation.  ForE information on changing the EXPECTED_VOTES value on a running system, F see the SET CLUSTER/EXPECTED_VOTES command, and see the OpenVMS systemF console documentation for the processor-specific console commands usedC to trigger the IPC (Interrrupt Priority Level %x0C; IPL C) handler.sE The IPC handler can be used to clear a quorum hang, and to clear diska mount verification hangs.i  F The quorum scheme is a set of "blade guards" deliberately implemented F by OpenVMS Engineering to provide data integrity -- remove these bladeG guards at your peril.  OpenVMS Engineering did not implement the quorumoG mechanism to make your life more difficult -- quorum was implemented too' keep your data from getting scrambled. i 						[Stephen Hoffman]   < ------------------------------------------------------------< MGMT11. Why doesn't OpenVMS see the new memory I just added?  I When adding memory to an OpenVMS system, one should check for an existingyI definition of the PHYSICALPAGES (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMSrH Alpha) parameter in the SYS$SYSTEM:MODPARAMS.DAT parameter database, useH a text editor to reset the value in the file to the new correct value as1 required, and then perform the following command:e  /   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK5  I This AUTOGEN command will reset various system parameters based on recent J system usage (FEEDBACK), and it will reset the value for the PHYSICALPAGESD parameter to the new value.  It will also reboot the OpenVMS system.   H PHYSICALPAGES and PHYSICAL_MEMORY can also be used to deliberately lowerG the amount of memory available for use by OpenVMS.  This ability can befH useful in a few specific circumstances, such as testing the behaviour ofG an application in a system environment with a particular (lower) amounts of system memory available.O  I PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on OpenVMS Alpha) or oK (better and simpler) the entry can be removed from the MODPARAMS.DAT file, n5 to indicate that all available memory should be used.o   						[Stephen Hoffman]c  < ------------------------------------------------------------9 MGMT12. How do I write a BACKUP saveset to a remote tape?t  G How to do this correctly was described at DECUS a long time ago. On theh. node with the tape drive, create SAVE-SET.FDL:   RECORD%         FORMAT                  fixedD$         SIZE                    8192   Then create BACKUP_SERVER.COM:     $ !vA   $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.n   $ !i   $ set noon   $ set rms/network=16   $ allocate mka500 tapedevc4   $ mount/nounload/over:id/block=8192/assist tapedev2   $ convert/fdl=SAVE-SET sys$net tapedev:save-set.   $ dismount/unload tapedeva
   $ stop/id=0e    A On the node where you want to do the backup, use the DCL command:D     $ backup -      srcfilespec -9      node"user pwd"::"task=backup_server"/block=8192/save-  H The only thing that doesn't completely work here is multi-reel savesets.G Since the tape is being written through RMS and the magtape ACP, BACKUPfE won't see the reel switch and will split an XOR group across the reellE boundary. As far as I remember, BACKUP will be willing to read such arE multi-reel save set (directly, not over the net) since the XOR blockstF are simply ignored on read, but it definitely wouldn't be able to do a" recovery across the reel boundary.  F Unfortunately BACKUP can't read tapes over the network because the RMSD file attributes on a network task access look wrong (variable length	 records).S 						[Stephen Hoffman]o  < ------------------------------------------------------------3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSC   K The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSC are used to connect rM to storage controllers via the Diagnostics and Utility Protocol (DUP).  TheseGK commands require that the FYDRIVER device driver be connected.  This devicenL driver connection is typically performed by adding the following command(s) * into the system startup command procedure:       On OpenVMS Alpha:r       $ RUN SYS$SYSTEM:SYSMANt;       SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVERr       On OpenVMS VAX:a       $ RUN SYS$SYSTEM:SYSGENr$       SYSGEN> CONNECT FYA0/NOADAPTER  M Alternatives to the DCL SET HOST/DUP command include the console >>> SET HOSTlA command available on various mid- to recent-vintage VAX consoles:p  8     Access to Parameters on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMSe  @     Access to Directory of tools on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECT   4     Access to Parameters on a KFQSA DSSI controller:;       >>> SHOW UQSSP ! to get port_controller_number PARAMSc:       >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  I These console commands are available on most MicroVAX and VAXstation 3xxxoE series systems, and most (all?) VAX 4xxx series systems.  For furtherCK information, see the system documentation and -- on most VAX systems -- sees the console HELP text.  J EK-410AB-MG, _DSSI VAXcluster Installation and Troubleshooting_, is a goodL resource for setting up a DSSI VMScluster on OpenVMS VAX nodes. (This manualJ predates coverage of OpenVMS Alpha systems, but gives good coverage to allJ hardware and software aspects of setting up a DSSI-based VMScluster -- andO most of the concepts covered are directly applicable to OpenVMS Alpha systems. uL This manual specifically covers the hardware, which is something not covered2 by the standard OpenVMS VMScluster documentation.)   						[Stephen Hoffman]r  < ------------------------------------------------------------4 MGMT14. How do I install DECnet Phase IV on VMS 7.1?  N On OpenVMS V7.1, all DECnet binaries were relocated into separate installationH kits -- you can selectively install the appropriate network: DECnet-PlusK (formerly known as DECnet OSI), DECnet Phase IV, and Compaq TCP/IP Services  (often known as UCX).y  L On OpenVMS versions prior to V7.1, DECnet Phase IV was integrated, and thereN was no installation question.  You had to install the DECnet-Plus (DECnet OSI)K package on the system, after the OpenVMS upgrade or installation completed.   J During an OpenVMS V7.1 installation or upgrade, the installation procedureF will query you to learn if DECnet-Plus should be installed. If you areG upgrading to V7.1 from an earlier release or are installing V7.1 from anK distribution kit, simply answer "NO" to the question asking you if you want5L DECnet-Plus.  Then -- after the OpenVMS upgrade or installation completes --L use the PCSI PRODUCT INSTALL command to install the DECnet Phase IV binaries? from the kit provided on the OpenVMS software distribution kit.u  F If you already have DECnet-Plus installed and wish to revert, you mustN reconfigure OpenVMS.  You cannot reconfigure the "live" system, hence you mustJ reboot the system using the V7.1 distribution CD-ROM.  Then select the DCL. ($$$ prompt) option.  Then issue the commands:  *     $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0:0     $$$ DEVINE/STSTEM PCSI$SPECIFIC DKA0:[SYS0.]@     $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]  K The above commands assume that the target system device and system root are H "DKA0:[SYS0.]".  Replace this with the actual target device and root, asK appropriate.  The RECONFIGURE command will then issue a series of prompts.  M You will want to reconfigure DECnet-Plus off the system, obviously.  You willtM then want to use the PCSI command PRODUCT INSTALL to install the DECnet Phase + IV kit from the OpenVMS distribution media.E  G Information on DECnet support, and on the kit names, is included in thei4 OpenVMS V7.1 installation and upgrade documentation.   						[Stephen Hoffman]f  < ------------------------------------------------------------< MGMT15. How do I change the text in a user's UIC identifier?  M The text translations of the numeric User Identification Code (UIC) are basedrM on identifiers present in the OpenVMS rightslist.  Documentation on this aread= is included in the _Guide to OpenVMS System Security_ manual.   J To control the identifiers shown for a user's UIC, you use AUTHORIZE. EachJ user has an associated group identifier, and an identifier specific to the. user.  And each user should have a unique UIC.  F To alter the text of a user or group identifier, use commands such as:       $ RUN SYS$SYSTEM:AUTHORIZE+     UAF> rename/ident oldgroupid newgroupid *     UAF> rename/ident olduserid  newuserid  L If you should find yourself missing an identifier for a particular user, you7 can add one for the user's UIC using a command such as:d  3     UAF> add/ident/value=uic=[group,user] newuserid   M The UIC user identifier text is assigned when the username is created, and is N the text of the username.  The UIC group group identifier is assigned when theH first username is created in the UIC group, and the text is based on theM account name specified for the first user created in the group.  The value ofFL this identifier is [groupnumber, 177777]. To add a missing group identifier, use an asterisk as follows:t  1     UAF> add/ident/value=uic=[group,*] newgroupid   M You may find cases where an identifier is missing from time to time, as thereeJ are cases where the creation of a UIC group name identifier might conflictF with an existing username, or a user identifier might conflict with anM existing group identifier.  When these conflicts arise, the AUTHORIZE utilityrN will not create the conflicting group and/or user identifier when the username is created.r  K You can can add and remove user-specified identifiers, but you should avoid J changing the numeric values associated with any existing identifiers.  YouL should also avoid reusing UICs or identifiers when you add new users, as anyL existing identifiers that might be present on objects in the system from theM old user will grant the same access to the new user.  Please see the securityv manual for details.d  < ------------------------------------------------------------3 MGMT16. What are the OpenVMS version upgrade paths?   8    Note: See "OpenVMS Alpha Terminology" section, below.  3    OpenVMS Alpha release upgrade (or update) paths:y  (      From V1.0, one can upgrade to V1.5.5      From V1.5, or V1.5-1H1, one can upgrade to V6.1.t(      From V6.1, one can upgrade to V6.2.1      From V6.1, or V6.2, one can upgrade to V7.0.eG      From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0, one can upgrade to V7.1. B      From V6.2, one can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.F      From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2, to V7.2-1(      From V6.2, ... or V7.2, to V7.2-1H1?      From V7.1, one can update to V7.1-1H(1,2), ... to V7.2-1H1-  >      Some typical OpenVMS Alpha upgrade (or update) paths are:9          V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2)o5          V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2)-          V6.1 -> V7.2-          V6.2 -> V6.2-1H3o          V6.2 -> V7.2-1m          V6.2-1H(1,2,3) -> V7.1 !          V6.2-1H(1,2,3) -> V7.2-1e          V7.1 -> V7.1-1H(1,2)n          V7.1 -> V7.1-2e          V7.1 -> V7.2-1a          V7.1-1H(1,2) -> V7.2-1s          V7.2 -> V7.2-1H1n  G      Note that OpenVMS Alpha V7.0 does not include support for hardwaresE      and/or configurations first supported in OpenVMS Alpha V6.2-1H1,aA      V6.2-1H2, or V6.2-1H3; one must upgrade to OpenVMS VAX V7.1.n  F      One cannot update directly to a V6.2-1Hx Limited Hardware ReleaseD      (LHR) from any release prior to the baseline V6.2 release.  TheG      same prohibition holds for performing updates directly to V7.1-1Hx F      from any release prior to V7.1 -- this is not supported, and doesE      not produce the expected results.  The LHR kits can, however, bemE      directly booted and can be directly installed, without regard toaC      any operating system that might be present on the target disk.s  F      OpenVMS Alpha updates for LHRs (through V7.1-1Hx) require the useF      of VMSINSTAL for the update.  These LHR releases use PCSI for theE      installation, but not for the update.  Non-LHR releases use PCSI !      for installs and upgrades.  o  F      OpenVMS Alpha V7.1-2 and later use PCSI for LHRs and for OpenVMS C      upgrades and for all OpenVMS ECO kit installations.  VMSINSTALeE      OpenVMS ECO kits are not used on OpenVMS Alpha V7.1-2 and later.eD      Prior to V7.1-2, VMSINSTAL-based ECO kits are used for OpenVMS.    %    OpenVMS VAX release upgrade paths:i  A      From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5. ?      From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.t;      From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.a=      From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1.e1      From V6.0, or V6.1, one can upgrade to V6.2.e1      From V6.1, or V6.2, one can upgrade to V7.0. 7      From V6.1, V6.2, or V7.0, one can upgrade to V7.1. D      From V6.1, one can upgrade to V7.2 (with VAXBACK ECO for V6.1).  0      Some typical OpenVMS VAX upgrade paths are:8          V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.0, or V7.1)          V5.5-2HW -> V5.5-2d=          V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)e)          V6.1 -> VAXBACK V6.1 ECO -> V7.2e          V6.2 -> V7.2e  E      Note that OpenVMS VAX V6.0 does not include support for hardwarelC      and/or configurations first added in OpenVMS VAX V5.5-2H4, one &      must upgrade to OpenVMS VAX V6.1.  G      Note that OpenVMS VAX V5.5-2HW is a pre-release version of V5.5-2.tB      Any system running it should be upgraded to V5.5-2, or later.    $    OpenVMS Cluster Rolling Upgrades:  F      Rolling Upgrades require multiple system disks.  Rolling upgradesL      permit the OpenVMS Cluster to remain available while individual systems1      are being upgraded to a new OpenVMS release.c  L      OpenVMS Cluster rolling upgrades for both OpenVMS VAX and OpenVMS AlphaG      may (will) have different, or additional upgrade requirements, andnC      have requirements around which versions of OpenVMS can coexistr3      in a OpenVMS Cluster than what is listed here.c  K      See the _OpenVMS <platform> Version <Version> Upgrade and Installationu;      Manual_, and the OpenVMS Software Product Descriptions   &        http://www.compaq.com/info/spd/?        OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.e  O      for further details on the rolling upgrade, and for support information.  fI      The documentation for older releases of OpenVMS VAX includes variouseF      platform-specific manuals, manuals that include instructions that>      are specific to installing and upgrading on the platform.    7    OpenVMS and Layered Products -- Support Information:   ?      For information on Prior Version Support (PVS) and Mature  A      Product Support (including information on support end dates o;      for OpenVMS and various layered products), please see:m  =        http://www.compaq.com/services/software/ss_mature.html B        http://www.compaq.com/services/software/ss_pvs_se_amap.htmlB        http://www.compaq.com/services/software/ss_mps_pvs_eur.html  C      For information on supported versions of layered products, anda4      minimum required layered product versions, see:  A        http://www.openvms.compaq.com/openvms/os/swroll/index.html   A      For information on the release history of OpenVMS, including,>      information on the code names of various releases and the      major features:  L        http://www.openvms.compaq.com/openvms/os/openvms-release-history.html  D      Additional release history information, as well as a variety ofA      other trivia, is available in the VAX 20th anniversary book:e  =        http://www.openvms.compaq.com/openvms/20th/vmsbook.pdfa      OpenVMS Alpha Terminology:d  B      update:    Typically used for Limited Hardware Releases (LHR)A                 releases.  Performed via VMSINSTAL.  Applies only @                 to the OpenVMS release that the LHR is based on,F                 or to an intermediate LHR.  (eg: V7.1-1H2 applies onlyD                 to V7.1-1H1 and to V7.1, not to any other releases.)C                 LHRs within a series are cumulative, containing all G                 files and features of previous LHRs in the same series.n  F      upgrade:   Performed via PCSI.  Upgrades can typically be appliedE                 to a release-specific (and documented) range of priors!                 OpenVMS releases.-  F      install:   Performed via PCSI.  With an installation, no existingG                 version of the operating system is assumed present, nor I                 are any files from any copy of the operating system mightsK                 be present preserved, and the entire contents of the target =                 disk are destroyed via a disk initialization.r  J      preserve:  Performed via PCSI.  Otherwise similar to an installation,H                 this option skips the disk reinitialization.  User filesI                 on the target disk are preserved.  Any existing operating->                 system files on the target disk are clobbered.  G      LHR:       Limited Hardware Release.  LHRs are specific to and areoD                 targeted at new hardware configurations, and are notF                 shipped to customers with support contracts.  At leastI                 one LHR kit must be specifically acquired when purchasingiI                 new hardware, new hardware that is not (yet) supported byoH                 any mainline (non-LHR) release.  LHRs have an "H" in theH                 OpenVMS version string, indicating a "Hardware" release.    @   For minimum OpenVMS versions for various platforms, see VMS13.  < ------------------------------------------------------------G MGMT17. Why do I have negative number in the pagefile reservable pages?e  E Seeing a negative number in the reservable pages portion of the SHOW iI MEMORY/FULL command can be normal and expected, and is (even) documented eD behaviour.  A pagefile with a negative number of reservable pages isK overcommitted, which is generally goodness assuming that every process withML reserved pages does not try to occupy all of the reserved pagefile  space at the same time. m  L To understand how the pagefile reservation process works, think about  how aN traditional bank operates when accepting customer deposits and  making loans. L It's the same idea with the pagefile space. There is  less money in the bankM vault than the total deposits, because much of  the money has been loaned outwH to other customers of the bank.  And the behaviour parallels that of theM pagefile down to the problems that a  "run on the bank" can cause for bankingRI customers.  (Though there is  no deposit insurance available for pagefileo users.)n  L If all of the running applications try to use the reserved space, the systemG manager will need to enlarge the pagefile or add one or more additionalS
 pagefules.  L To determine if the pagefile is excessively overcommitted, watch for "doubleN overcommitment" -- when the reservable space approaches the  negatation of theG available total space -- and watch that the total  amount of free space K available in the pagefile remains adequate.  If  either of these situationsc0 arises, additional pagefile storage is required.  G Additional pagefile information: Additional pagefiles can typically be cJ created and connected on a running OpenVMS system.  New processes and  newN applications will tend to use the new pagefile, and existing  applications canL be restarted to migrate out of the more congested  pagefiles.  Pagefiles areN generally named PAGEFILE.SYS, and multiple  pagefiles are generally configuredM on separate disk spindles to spread  the paging I/O load across the available E disk storage.  When multiple  pagefiles are present on recent OpenVMS-J versions, each pagefile file  should be configured to be approximately the( same total size as the  other pagefiles.  K For additional information on pagefile operations and related commands, seerH the system management and performance management manuals in the  OpenVMS documentation set. 					[Stephen Hoffman]  < ------------------------------------------------------------C MGMT18. Do I have to update layered products when updating OpenVMS?   K The Software Public Rollout Reports for OpenVMS list the current and futureML availability of Compaq's software products shipping on the Software ProductsG Library kits (CDROM consolidations) for OpenVMS Alpha and OpenVMS VAX. eK Specifically, the required minimum versions for product support are listed.o  N Comprehensive Public Rollout Information, listing previous product versions asM well as currently shipping versions, has been compiled into a separate set of:N reports.  The product information is grouped to show Operating System support.  G You may or may not be able to use older versions of local applications,DJ third-party products, and various Compaq layered products with more recentJ versions of OpenVMS.  User-mode code is expected to be upward compatible. N Code executing in a privileged processor mode -- typically either executive orN kernel mode -- may or may not be compatible with more recent OpenVMS versions.  " These reports are updated monthly.   Please see:o<   http://www.openvms.compaq.com/openvms/os/swroll/index.html   					[Stephen Hoffman]  < ------------------------------------------------------------3 MGMT19. How do I change the volume label of a disk?X  G   Dismount the disk, and mount it privately.  If the disk is mounted by F   more than one node in an OpenVMS Cluster, dismount it from all otherE   nodes.  If this disk is an OpenVMS system disk, shut down all otherl-   nodes that are bootstrapped from this disk.   ?   Issue the SET VOLUME/LABEL command, specifying the new label.y  >   On OpenVMS V6.0 and later, issue the following PCSI command:  2     $ PRODUCT REGISTER VOLUME <old-label> <device>  G   To reset the label information stored in the PCSI database to reflect    the new disk volume label.  F   Locate any references in the system startup (typically including theJ   disk MOUNT commands) and any DISK$label references in application files,*   and change the references appropriately.  I   If this is a system disk (for the host or for a satellite), also check  I   the DECnet MOP or LANCP boot database, as well as any references to thet&   disk created by CLUSTER_CONFIG*.COM.  !   Remount the disk appropriately.V 					[Stephen Hoffman]:                                         [John E. Malmberg]  < ------------------------------------------------------------/ MGMT20.  How do I fix a corrupt BACKUP saveset?n  E   BACKUP savesets can be corrupted by FTP file transfers and by toolsuC   such as zip (particularly when the zip tool has not been asked to F   save and restore OpenVMS file attributes or when it does not supportF   OpenVMS file attributes), as well as via other means of corruptions.  D   If you have problems with the BACKUP savesets after unzipping themF   or after an FTP file transfer, you can try restoring the appropriate$   saveset attributes using the tool:  *     $ @RESET_BACKUP_SAVESET_ATTRIBUTES.COM  C   This tool is available on the OpenVMS Freeware (in the [000TOOLS]tD   directory).  The Freeware is available at various sites -- see theF   Freeware location listings elsewhere in the FAQ -- and other similar0   tools are also available from various sources.  E   In various cases (note that not all savesets use the default recordt+   size!), the following command might work:"  I     $ SET FILE/ATTRIBUTES=(RFM:FIX,MRS:32256,LRL:32256,RAT:NONE) file.bck   K   Also see the "SITE VMS", /FDL, and various other file-attributes options cG   available in various FTP tools.  (Not all available FTP tools supportu   any or all of these options.)L  I   Browser downloads (via FTP) and incorrect (binary or ascii FTP transfer H   modes) are notorious for causing RMS file corruptions and particularlyL   BACKUP saveset corruptions.  You can sometimes help encourage the browser =   to select the correct FTP transfer type code (via RFC1738):-       ftp://host/url?type=binary  H   You can also often configure the particular web browser to choose the E   appropriate transfer mode by default, based on the particular file pH   extensions, using a customization menu available in most web browsers.H   You can select that the specific file extentions involved use the FTP I   binary transfer mode, which will reduce the number of corruptions seen.t   					[Stephen Hoffman]  < ------------------------------------------------------------- MGMT21.  How can I set up a shared directory?e  H To set up a shared directory -- where all files created in the directoryH are accessable to the members of specified group of users -- you can use/ an access control list (ACL) and an identifier.e  K The following also shows how to set up a resource identifier, which furthercJ allows the disk resources to be charged to the specified identifier ratherB than each individual user.  (If you don't want this, then omit theE attributes option on the identifier creation and omit the entry added  in the disk quota database.r  " Add an identifier using AUTHORIZE:3   ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifieru  ? Grant the identifier to each user in the group using AUTHORIZE:n+   GRANT/IDENTIFIER groupidentifier usernamef  A If disk quotas are in use, add an entry via SYSMAN for each disk:rF   DISKQUOTA ADD groupidentifier/PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:  J Set the shared directory to have an ACL similar to the following using theJ SET SECURITY (V6.0 and later) or SET ACL (versions prior to V6.0) command:(   (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W)O   (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE) ?   (IDENTIFIER=groupidentifier,ACCESS=READ+WRITE+EXECUTE+DELETE)e+   (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)c  K If there are files already resident in the directory, set their protectionsdL similarly.  (The OPTIONS=DEFAULT, DEFAULT_PROTECTION, and CREATOR ACEs apply to directories.)  L The default protection mask is used to establish the default file protection@ mask, this mask does not prevent the users holding the specifiedK groupidentifier from accessing the file(s), as they can access the file via-C the explicit identifier granting access that is present in the ACL.v  I For further information, see the OpenVMS Guide to System Security Manual,eL specifically the sections on ACLs and identifiers, and resource identifiers.  < ------------------------------------------------------------ MGMT22 relocated to SUPP3o  < ------------------------------------------------------------8 MGMT23. Why do I get extra blank pages on my HP Printer?  I   For information on configuring telnet print symbiont, on device control1J   libraries such as SYSDEVCTL.TLB, and for ways of dealing with the extra L   blank pages that can arise on various HP printers, please see the OpenVMS =   Ask The Wizard area, starting particularly with topic 1020:m  )     http://www.openvms.compaq.com/wizard/a6     http://www.openvms.compaq.com/wizard/wiz_1020.html  L   There are a variety of discussions of this and of related printing topics    in the Ask The Wizard area.V     Also see MGMT51. 					[Stephen Hoffman]    < ------------------------------------------------------------E MGMT24. Configure ELSA GLoria Synergy or PowerStorm 300/350 graphics?.  E   On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the appropriate  ;   GRAPHICS PCSI kit, and all prerequisite OpenVMS ECO kits:r  "     VMS712_GRAPHICS-V0300 or later!     VMS72_GRAPHICS-V0100 or later1"     VMS712_GRAPHICS-V0300 or later     ----  *   The ELSA GLoria Synergy is the PBXGK-BB.  @   On OpenVMS Alpha V7.2-1, the files necessary for this graphics>   controller are located in the distribution CD-ROM directory:       DISK$ALPHA0721:[ELSA.KIT]i  0   Also check for any available (later) ECO kits.  E   An earlier kit (ALP4D20T01_071) (for V7.1, V7.1-1H1, and V7.1-1H2) eE   was once available, but has been superceded and is not recommended.dD   Use of V7.1-2 or later (and use of one the above GRAPHICS kits as +   required) is typically the best approach.i  D   OpenVMS V7.2-1H1 and later should directly support the controller.     ----     PowerStorm 300 : PBXGD-AC    PowerStorm 350 : PBXGD-AEf  @   For support of the PowerStorm 300 and PowerStorm 350 graphics D   controllers, acquire and install the following available ECO kits:     For OpenVMS Alpha V7.1-2:R,     DEC-AXPVMS-VMS712_P350-V0100--4 or later0     DEC-AXPVMS-VMS712_GRAPHICS-V0300--4 or later     For OpenVMS Alpha V7.2-1: ,     DEC-AXPVMS-VMS721_P350-V0100--4 or later0     DEC-AXPVMS-VMS721_GRAPHICS-V0300--4 or later     ----  D   Support for the ELSA GLoria Synergy and the PowerStorm 300 and 350E   controllers is expected to be integrated in the OpenVMS Alpha V7.3 -   and later releases.    					[Stephen Hoffman]  < ------------------------------------------------------------: MGMT25. How do I acquire OpenVMS patches, fixes, and ECOs?  N You can acquire and download kits containing OpenVMS fixes (ECOs) for various 
 releases via:o  $   http://search.service.digital.com/+   ftp://ftp.service.digital.com/public/vms/V'   http://ftp.digital.com.au/pub/ecoinfoS(   http://ftp/digital.com.au/cgi-bin/grep  3 You can subscribe to an email notification list at:.  ;   http://www.service.digital.com/patches/mailing-list.shtml-  5 A quarterly distribution is also available on CD-ROM:K      QT-3CQAA-C8      OpenVMS Alpha   QT-3CRAA-C8      OpenVMS VAX  > For a list of OpenVMS ECO kits recently released, you can use:  B     http://Eisner.DECUS.org/conferences/OpenVMS-patches_new_1.HTML  ? You can also sign up for ECO kit email notifications (Digest orp2 individual notifications) directly from Compaq at:  =     http://www1.service.digital.com/patches/mailing-list.htmlu  B Examples and ECO kit installation instructions are included in the? cover letter.   For available ECO kits, cover letters and otherm" associated documentation, look in:  4     ftp://ftp.service.digital.com/public/vms/axp/...4     ftp://ftp.service.digital.com/public/vms/vax/...  G Do NOT attempt to install a VMSINSTAL-based OpenVMS ECO kit on OpenVMS rF Alpha V7.1-2 and later.  While VMSINSTAL itself remains available, it H is not used for OpenVMS Alpha ECO kits starting in OpenVMS Alpha V7.1-2.= OpenVMS Alpha V7.1-2 and later use PCSI for OpenVMS ECO kits.a  0 See MGMT46 for information on ECO kit checksums.   					[Stephen Hoffman]  < ------------------------------------------------------------. MGMT26. How do I rename a DSSI disk (or tape?)  C   If you want to renumber or rename DSSI disks or DSSI tapes, it's a/   easy -- if you know the secret incantation...e     From OpenVMS:c       $ RUN SYS$SYSTEM:SYSGENp"     SYSGEN> CONNECT FYA0/NOADAPTER     SYSGEN> ^Z=     $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>r     ...      PARAMS> STAT CONFoC     <The software version is normally near the top of the display.>o     PARAMS> EXIT     ...   F   From the console on most 3000- and 4000-class VAX system consoles...>   (Obviously, the system must be halted for these commands...)       Integrated DSSI:  A         >>> SET HOST/DUP/DSSI[/BUS:[0:1]] dssi_node_number PARAMSi  
     KFQSA:  <         >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  G   For information on how to get out into the PARAMS subsystem, also seeeH   the >>> HELP at the console prompt for the SET HOST syntax, or see theG   HELP on SET HOST /DUP (once you've connected FYDRIVER under OpenVMS).   F   Once you are out into the PARAMS subsystem, you can use the FORCEUNID   option to force the use of the UNITNUM value and then set a uniqueF   UNITNUM inside each DSSI ISE -- this causes each DSSI ISE to use theD   specfied unit number and not use the DSSI node as the unit number.G   Other parameters of interest are NODENAME and ALLCLASS, the node names2   and the (disk or tape) cluster allocation class.  H   Ensure that all disk unit numbers used within an OpenVMS Cluster disk G   allocation class are unique, and all tape unit numbers used within ane8   OpenVMS Cluster tape allocation class are also unique. 					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT27. How do I move the queue manager database?   P   To move the location of the queue database, the SYS$QUEUE_MANAGER.QMAN$QUEUES L   and SYS$QUEUE_MANAGER.QMAN$JOURNAL files, to a disk that is fast(er), has M   plenty of free space, and that is not heavily used.  If the queue database UJ   is on a (busy) OpenVMS system disk, you can and probably should move it .   off the system disk to another disk spindle.     To move the queue database:   O    0. Checkpoint the journal file.  This reduces the file size to the in-memoryf8       database size.  This will cause the noted delay.     	$ mcr JBC$COMMAND 	JBC$COMMAND> DIAG 0 7      1. Stop the queue manager   	$STOP/QUEUE/MANAGER/CLUSTER  O    2. Backup the .QMAN$QUEUES and .QMAN$JOURNAL files from the present locationt       for safety.  	eE 	$ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]          N    3. Create a new directory for the queue database.  Insure that this disk isN       accessible to all nodes that can run the queue manager.  If the /ON listK       for the queue manager is "/ON=(*)", the disk must be available to alle       nodes in the cluster t   	$ CREATE/DIR fast_disk:[qman]  H    4. Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the new directory  E 	$ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  fast_disk:[qman]u  '    5.  Delete the old queue database.  i  4 	$DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  <    6. Restart the queue manager pointing to the new location  & 	$START/QUEUE/MANAGER fast_disk:[qman]   					[Dave Sweeney]t  < ------------------------------------------------------------> MGMT28. How do I set a default IP route or gateway on OpenVMS?  2 If you have TCP/IP Services, then use the command:  %   For TCP/IP Services V5.0 and later:f  4     $ TCPIP SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  '   For earlier TCP/IP Services versions:E  2     $ UCX SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  < ------------------------------------------------------------ MGMT29 relocated to ALPHA21r  < ------------------------------------------------------------C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?a  C "Undeleteable" jobs are usually "undeleteable" for a reason -- thissE can track back to insufficient process quotas, to a kernel-mode errorhD in OpenVMS or a third-party device driver, or to other odd problems.  D These undeletable jobs typically become of interest because they are@ holding onto a particular resource (eg: tape drive, disk drive, A communications widget) that you need to use...  If the particular D device supports firmware, ensure that the device firmware is currentG -- TQK50 controllers are known for this when working with old firmware.lG (That, and the infamous "MUA4224" firmware bug.)  If this device has a  D driver ECO kit available, acquire and apply it...  If the particular9 relevent host component has an ECO, acquire and apply it.t  D Useful tools include SDA (to see what might be going on) and DECamdsA (which increase and thus potentially fix quota-related problems).tB (nb: Applications with quota leaks will obviously not stay fixed.)  ? If the stuck application is BACKUP, ensure you have the currente@ BACKUP ECO and are directly following the V7.1 or (better) V7.2 ; process quota recommendations for operator BACKUP accounts.e  H If the firmware and ECO levels are current, the best approach is to takeI a system crashdump, and pass a copy of the dump file it along to whomevernH is maintaining the device driver for the particular device/widget/driverK involved, with any details on how you got into this situation.  (The reboot E involved with taking the crashdump will obviously clear the problem.)   D There was some kernel-mode code (typically for OpenVMS VAX) that canF reset the device ownership field, but that is rather obviously only anE interim solution -- the real fix is avoiding the loss of the IRP, the D process quota leak, or whatever else is "jamming up" this particular
 process... 					[Stephen Hoffman]  < ------------------------------------------------------------* MGMT31. How do I reset the error count(s)?  F The system reboot is the only supported approach, but it is obviously E undesirable in various situations -- there is presently no supported tC mechanism to reset error counts once the error(s) have been logged.   C As for an unsupported approach -- and be aware of the potential ford causing a system crash...o  F To reset the error count, one needs to determine the system address ofE the error count field.  For a device, this is at an offset within the G device's UCB structure.  On VAX, the field is at an offset symbolically G defined as UCB$W_ERRCNT.  On Alpha, this field's offset is symbolicallyeE defined as UCB$L_ERRCNT.  The former is a word in size; the latter ispE a longword.  (Could it be that Alpha devices are more error prone? ;)c  F You now need to locate the system address of the UCB$%_ERRCNT field ofE the device you wish to reset.  Enter SDA.  In the following, you willrE see designations in {} separated by a /.  The first item in braces islE to be used on the VAX and the second item should be used on an Alpha.h (ie.  {VAX/Alpha})   $ ANALYZE/SYSTEM2 SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBF SDA>  SHOW DEVICE <ddnc:>    ! device designation of device with error# SDA>  EVALUATE UCB+UCB${W/L}_ERRCNT-9 Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offset   1 Record the hexadecimal value 'hhhhhhhh' returned.a  G You can now exit from SDA and $ RUN SYS$SHARE:DELTA or do what I prefer  to do, issue the following:i   SDA> SPAWN RUN SYS$SHARE:DELTA  I On both VAX and Alpha, the DELTA debugger will be invoked and will ident-sG ify itself.  On Alpha, there will be an Alpha instruction decoded.  ForiI those unfamiliar with DELTA, it does not have a prompt and only one error I message -- Eh?  (Well, for sake of argument, there might be another errortF produced on the console if you're not careful -- aka. a system crash!)  * If you are on a VAX, enter the command: [W* If you are on Alpha, enter the command: [L  H These set the prevailing mode to word and longword respectively.  Remem-% ber the UCB${W/L)_ERRCNT differences?p   Now issue the command 1;Ms  DELTA will respond with 00000001  I You're now poised to ZAP the error count field.  To do so you need to en-nH ter the system address and view its contents.  The format of the command to do this is of the form:   <IPID>:<hhhhhhhh>/  I For an IPID, use the IPID of the SWAPPER process.  It is always: 00010001-  . Thus, to ZAP the error count, you would enter:   00010001:hhhhhhhh/  I When you enter the / SDA will return the content of the address hhhhhhhh.sJ This should be the error count (in hexadecimal) of the device in question.I If it is not, you did something wrong and I'd suggest you type a carriagetH return and then enter the command EXIT to get out of DELTA.  Regroup and! see where your session went awry.t  I If you entered your address correctly and the error count was returned asy* in the following example, you can proceed.  J 00010001:80D9C6C8/0001                          ! output on VAX    1 error  J 00010001:80D9C6C8/00000001                      ! output on Alpha  1 error    H You can now ZAP the error count by entering a zero and typing a carriage return.  For example:e    J 00010001:80D9C6C8/0001 0<cr>                    ! output on VAX    1 errorJ 00010001:80D9C6C8/00000001 0<cr>                ! output on Alpha  1 error  0 Now type the command EXIT and a carriage return.<                                       [Brian Schenkenberger]  < ------------------------------------------------------------A MGMT32. How do I find out if the tape drive supports compression?   6 For various SCSI-based MK-class magnetic tape devices:  6     $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2")     $ Comp_sup = %X00200000      $ Comp_ena = %X00400000u5     $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -v0         WRITE SYS$OUTPUT "Compression supported"5     $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_sup THEN -p.         WRITE SYS$OUTPUT "Compression enabled"  < ------------------------------------------------------------? MGMT33. Can I copy SYSUAF to another version? To VAX? To Alpha?e  > The format of the SYSUAF.DAT, RIGHTSLIST, and associated files= are upward-compatible, and compatible across OpenVMS VAX and p9 OpenVMS Alpha systems.  (This compatibility is a a basic s< requirement of mixed-version OpenVMS Cluster configurations A and OpenVMS upgrades -- for specific support information, please -: see the OpenVMS Cluster rolling upgrade and mixed-version ? requirements.)  That said, it's the contents of the SYSUAF and e6 RIGHTSLIST files that will make this more interesting.  @ The same basic steps necessary for moving RIGHTSLIST and SYSUAF ? files to another node are rather similar to the steps involved sA in merging these files in an OpenVMS Cluster -- see the appendix hB of the OpenVMS Cluster documentation for details of merging files.C (You might not be merging the contents of two (or more) files, but e? you are effectively merging the contents of the files into the a target system environment.)s   Considerations:D  >   o applications often hold SYSUAF or RIGHTSLIST open, meaning@     a system reboot is often the best way to activate new files.  >   o the meanings of the RESTRICTED and CAPTIVE flags settings .     on the UAF entries have changed over time.  ?   o the new NET$PROXY.DAT file that is initially created based h>     on the contents of the NETPROXY.DAT during the OpenVMS VAX;     V6.1 upgrade and during the OpenVMS Alpha V6.2 upgrade.r:     This file is maintained in parallel with NETPROXY.DAT.  =   o the RIGHTSLIST identifier values and UIC values that end +?     up scattered around the target system must be rationalized +=     with the contents of the new RIGHTSLIST and SYSUAF files.   < The lattermost case -- resolving the identifier values -- is= often the most interesting and difficult part.   If you find C> that an identifier value (or identifier name) from the source ? RIGHTSLIST collides with that of an identifier existing on the a? target system, you must first determine if the two identifiers r= perform the same function.  In most cases, they will not.  Ase= such, you will have to find and chance all references to the s< identifier value(s) (or name(s)) to resolve the "collision".  > If you encounter a collision, changing both of the identifier > binary values (or names) involved in the collision to new and ? unique values can prevent security problems if you should miss  ? a couple of identifiers embedded somewhere on the target system-= during the whole conversion process -- rather than the wrong  > alphanumeric value for the identifier being displayed, you'll ? simply see the binary format for the identifier displayed, and d? no particular access will be granted.  And any DCL commands or P@ such that reference the old alphanumeric name will fail, rather 7 than silently (and potentially erroneously) succeeding.s  < Similar requirements exist for UIC values, as these too tend: to be scattered all over the system environment.  Like the= binary identifier values, you will find UIC values associatedV7 with disks, ACLs, queues, and various other structures.-  < For a list of the various files shared in an OpenVMS Cluster< and that can be involved when relocating an environment from= one node to another (or merging environments into an OpenVMS p> Cluster), please see the SYLOGICALS.TEMPLATE file included in   OpenVMS V7.2 and later releases. 					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT34. How do I delete (timeout) idle processes?.  F   There is no such command integrated within OpenVMS, though there areI   (optional) timers available within certain terminal servers and similarAI   devices, and there is an integrated time-of-day mechanism that providesn.   control over when a user can access OpenVMS.  K   As for available tools, there are DECUS, freeware, and third-party tools cG   known variously as "idle process killers" (IPK) or terminal timeout" iG   programs.  Examples include: Saiga Systems Hitman, Watchdog, MadGoat 1F   Watcher (via the MadGoat site or the OpenVMS Freeware), Kblock, the ?   Networking Dynamics tool known as Assassin, and the Zap tool.r  ;   A related package (for DECwindows sessions) is xtermlock.l  I   If the forgetful users are in an application menu environment, the menul9   can potentially be extended to provide this capability.   < ------------------------------------------------------------. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?  H   If you are seeing more files backed up than previously, you are seeingF   the result of a change that was made to ensure BACKUP can perform anI   incrementation restoration of the files.  In particular, if a directorynJ   file modification date changes, all files underneath it are included in L   the BACKUP, in order to permit incremental restoration should a directory    file get renamed.   8   Why has OpenVMS gone through the agony of this change?  H     When a directory is renamed, the modified date is changed.  When theH     restoration needs to restore the directory and its contents, and theK     restoration should not result in the restoration of the older directory D     name when a series of incremental BACKUPs are restored.  Thus anE     incremental BACKUP operation needs to pick up all of the changes.   0   What can you do to improve BACKUP performance?  H     Use the documented commands in the manual for performing incrementalJ     BACKUPs.  Use the documented incremental procedures.  Don't try to use6     incremental commands in a non-incremental context.  J     Also consider understanding and then using /NOALIAS, which will likelyJ     be a bigger win than will anything to do with the incremental BACKUPs,L     particularly on system disks and any other disks with directory aliases.  ,   Can you get the old BACKUP behaviour back?  E     Yes, please see the /NOINCREMENTAL qualifier available on recent cK     OpenVMS versions (and ECO kits).  Use of this qualifier informs BACKUP aM     that you are aware of the limitations of the old BACKUP behaviour around a"     incremental disk restorations.  I   Consider performing an incremental restoration, to test the procedures.VG   Attempting this is how we found out about the problem that was latent F   with the old scheme -- the old incremental BACKUP scheme would have J   missed restoring any files under a renamed directory.  Hence the change.  <   See the OpenVMS V6.2 release notes for additional details.  < ------------------------------------------------------------; MGMT36. How can I set up reverse telnet (like reverse LAT)?c  H   Though it may seem obvious, Telnet and LAT are quite different -- with*   differing capabilities and design goals.  E   Please see the documentation around the TCP/IP Services for OpenVMSsG   TELNET command CREATE_SESSION.  This command is the equivilent of theXG   operations performed in LTLOAD.COM or LAT$SYSTARTUP.COM.  There is nomH   TELNET equivilent to the sys$qio[w] control interface for LTDRIVER (asC   documented in the I/O User's Reference Manual) available, though ]D   standard sys$qio[w] calls referencing the created TN device would    likely operate as expected.A  < ------------------------------------------------------------? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?H  D   DECevent and Compaq Analyze are avalable to customers with supportE   contracts.  The PAK is required only for the advanced functions of mE   DECevent, the basic bits-to-text translation of the error log does lB   not require a license PAK.  Ignore the prompt, in other words.  E   (The PAK should be available to you if you have a hardware support SE   contract or warrantee, and the PAK enables the use of the advanced  @   error analysis and notification capabilities within DECevent.)  5   Please see the DECevent FAQ for additional details:d  A http://www.support.compaq.com/svctools/decevent/DECevent_FAQ.htmla  ?   The current version of the DECevent (Compaq Analyze) tool cant   be downloaded from:u  7 http://www.support.compaq.com/svctools/st-download.html-  < ------------------------------------------------------------6 MGMT38. INITIALIZE ACCVIO and ANSI tape label support?  C A change was made (back in 1988) to (as it was then known) VAX/VMS .D V5.1-1 that added support for the then-new ANSI X3.27-1987 magnetic F tape label standard.  Prior to the ANSI X3.27-1987 standard, the date F field in the ANSI HDR1 record permits dates only as far as the end of D Year 1999.  With ANSI X3.27-1987, dates through Year 1999 and dates & from Years 2000 to 2099 are permitted.  B Versions of INIT.EXE and MTAACP.EXE from VAX/VMS releases prior to> V5.1-1 will potentially have problems properly processing ANSI? magnetic tapes when Y2K and later dates are involved -- the DCLEB INITIALIZE command is known to encounter access violation (ACCVIO) errors.r  C The available solutions include upgrades, or setting the date back.[E Direct initialization of the tape with the new headers (via $qio) is nG also clearly possible, though the limitation within the old MTAACP.EXE e2 magtape ACP image is not nearly so easy to bypass.  B                                                [Hoffman, Dachtera]  < ------------------------------------------------------------/ MGMT39. How do I recover from INSVIRMEM errors?Q  ?   Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX releases, OC   VIRTUALPAGECNT and PGFLQUOTA limit the amount of virtual address l,   space that is available to each process.    E   Further limiting the amount of address space is the size of system eC   space (S0 and S1 space).  On OpenVMS Alpha versions prior to V7.0aD   and on all OpenVMS VAX releases, VIRTUALPAGECNT and MAXPROCESSCNT E   together determine the size of the page table data structures that yG   occupy large tracts of system space.  When no system virtual address oE   space is available for the stuff that needs it -- this includes thexC   page tables, non-paged pool, and various other structures -- then E   the values of VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.-  G   In OpenVMS Alpha V7.0 and later, the page table data structures have -C   been moved out of S0 and S1 space and into page table space.  In  D   OpenVMS Alpha V7.2 and later, certain large data structures found E   in non-paged pool (eg: lock management structures) have been moved aB   into 64-bit space, thus freeing up room in non-paged pool and inG   S0 and S1 space (where non-paged pool resides) while also permitting e    much larger data structures.    < ------------------------------------------------------------I MGMT40. How can I prevent a serial terminal line from initiating a login?   *   In SYSTARTUP_VMS.COM, issue the command:  ,     SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:  @   This will prevent any unsolicited terminal input on ddcu:, andA   this unsolicited input is what triggers JOB_CONTROL to start uphB   LOGINOUT on the terminal.  Once LOGINOUT starts up on the serial>   line, you can see interesting behaviour (eg: audits, processB   creations, etc) as LOGINOUT tries to "chat" with whatever device<   is hooked onto the remote end of the serial terminal line.  < ------------------------------------------------------------6 MGMT41. How does PCSI use the image BUILD_IDENT field?  K   The (undocumented) build ident field in an OpenVMS Alpha image header is oK   16 bytes long, and is used as a counted string of 0-15 characters (ie, a eJ   an .ASCIC string with count in byte 0) and was originally introduced to K   provide information for use by VMSINSTAL patch kits to determine whether  %   an image should be replaced or not.e  H   Starting with OpenVMS Alpha V7.1-2, OpenVMS Engineering uses the PCSI F   utility to package and install ECO kits for OpenVMS.  PCSI uses the I   generation attribute (a 32-bit unsigned integer) specified for files incN   the product description file (PDF) of a PCSI kit as the basis for performingH   file conflict detection and resolution.  When a product is installed, I   PCSI modifies the build ident field of Alpha image headers to store an tK   encoded form of the generation number.  It also looks at the build ident -L   field of previously installed images to obtain the generation information K   for those files as input to the file conflict processing algorithm. (Only %   images have this field, obviously.)e  J   PCSI interprets the build ident field of a previously installed image as
   follows:  I     - if the string length is 15, the 5th character is a hyphen, and the  J       last ten characters are a ten digit number with leading zeros, then G       the last ten characters are treated as a valid generation number.sI     - for V7.1-2 through V7.2-1, inclusive, if the above test fails, the  =       information is obtained from the PCSI product database. L     - in releases after V7.2-1 and with current PCSI ECO kits, if the above K       test fails, an invalid generation number is treated as 0000000000 so aI       that the ECO kit will simply replace the image rather than assuminge$      the PCSI database is in error.  E   So, what will you see in the image identification displayed via thes   ANALYZE/IMAGE command?  D   For an image that has been built as part of an OpenVMS EngineeringG   system build, you will generally see a build ID string in the format >D   "X6TE-SSB-0000" -- X6TE is the build number for the OpenVMS Alpha D   V7.2-1 release.  This id format is used within the OpenVMS system C   build, and can generally only be seen associated with images thato'   have not yet been processed via PCSI.h  J   During the installation of V7.2-1, PCSI will modify the image header to J   have a build ident string of "X6TE-0050120000".  During installation of I   an ECO kit containing this image with a generation number of 50130052, iL   for example, PCSI would determine that 50130052 is greater than 50120000, J   and will replace the existing image on the target disk with the version '   of the image included in the ECO kit.g  < ------------------------------------------------------------@ MGMT42. How to configure allocation classes and Multi-Path SCSI?  K The HSZ allocation class is applied to devices, starting with OpenVMS V7.2.eL It is considered a port allocation class (PAC), and all device names with a J PAC have their controller letter forced to "A".  (You might infer from theI the text in the "Guidelines for OpenVMS Cluster Configurations" that this J is something you have to do, though OpenVMS will thoughtfully handle this  renaming for you.)  I You can force the device names back to DKB by setting the HSZ allocation tE class to zero, and setting the PKB PAC to -1.  This will use the hostcG allocation class, and will leave the controller letter alone (that is, wL the DK controller letter will be the same as the SCSI port (PK) controller).H Note that this won't work if the HSZ is configured in multibus failover G mode.  In this case, OpenVMS requires that you use an allocation class h for the HSZ.  J When your configuration gets even moderately complex, you must pay carefulK attention to how you assign the three kinds of allocation class: node, porteI and HSZ/HSJ, as otherwise you could wind up with device naming conflicts   that can be painful to resolve.e  I The display-able path information is for SCSI multi-path, and permits theeG multi-path software to distinguish between different paths to the same  G device.  If you have two paths to $1$DKA100, for example by having two  I KZPBA controllers and two SCSI buses to the HSZ, you would have two UCBs  E in a multi-path set.  The path information is used by the multi-path  / software to distinguish between these two UCBs.   L The display-able path information describes the path; in this case, the SCSIL port.  If port is PKB, that's the path name you get.  The device name is no L longer completely tied to the port name; the device name now depends on the G various allocation class settings of the controller, SCSI port or node.   I The reason the device name's controller letter is forced to "A" when you TL use PACs is because a shared SCSI bus may be configured via different ports M on the various nodes connected to the bus.  The port may be PKB on one node, eJ and PKC on the other.  Rather obviously, you will want to have the shared L devices use the same device names on all nodes.  To establish this, you willH assign the same PAC on each node, and OpenVMS will force the controller G letter to be the same on each node. Simply choosing "A" was easier and bF more deterministic than negotiating the controller letter between the I nodes, and also parallels the solution used for this situation when DSSI e or SDI/STI storage was used.  I This information is also described in the Cluster Systems and Guidelines s+ for OpenVMS Cluster Configurations manuals.i;                                                [John Croll]a  < ------------------------------------------------------------@ MGMT43. How can I tell what software (and version) is installed?  A   There is unfortunatly no consistent nor single way to make thismA   determination -- this is one of the reasons that a move to PCSIh   installations is underway.  B   On OpenVMS Alpha, you can use VMSINSTAL.HISTORY and PRODUCT SHOW@   PRODUCT to determine what packages have been installed via the)   VMSINSTAL and PCSI tools, respectively.o  A   To see which OpenVMS Alpha ECO kits have been applied, look in e>   VMSINSTAL.HISTORY on OpenVMS Alpha prior to V7.1-2, and use >   PRODUCT SHOW PRODUCT/FULL on OpenVMS Alpha V7.1-2 and later.  ;   On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT and (for =   software that is installed via VMSINSTAL on V7.3 and later)    in VMSINSTAL.HISTORY.n  ;   For products installed on OpenVMS VAX prior to V7.3 using @   VMSINSTAL, there is no reliable way to determine what products?   have been installed.  If the product provides a RELEASE_NOTESt=   file (as many do), you can look for the list of these filesw?   via DIRECTORY SYS$HELP:*.RELEASE_NOTES.  Again, this approachg@   is NOT reliable: some kits do not provide release notes, some C   system managers will install only the release notes, some system aE   managers will delete release notes, and release notes for multiple i   versions can be present.  E   On most packages, you can generally use ANALYZE/IMAGE on one of thenE   core images, looking at the image identification area.  Some of the ,   product-specific mechanisms available are:  "     DQS   DQS$VERSION logical name     C     CC/VERSION     C++   CXX/VERSION     < ------------------------------------------------------------@ MGMT44. Where can I get Fibre Channel Storage (SAN) information?  8   http://www.openvms.compaq.com/openvms/fibre/index.html  < ------------------------------------------------------------. MGMT45. How can I split up an OpenVMS Cluster?  @   Review the VMScluster documentation, and the System ManagementB   documentation.  The following are the key points, but are likely.   not the only things you will need to change.  K   OpenVMS Cluster support is directly integrated into the operating system,lK   and there is no way to remove it.  You can, however, remote site-specificrB   tailoring that was added for a particular cluster configuration.  G   First: Create restorable image BACKUPs of each of the current system aH   disks.  If something gets messed up, you want a way to recover, right?  G   Create standalone BACKUP kits for the OpenVMS VAX systems, and create @   or acquire bootable BACKUP kits for the OpenVMS Alpha systems.  G   Use CLUSTER_CONFIG or CLUSTER_CONFIG_LAN to remove the various systemC>   roots and to shut off boot services and VMScluster settings.  D   Create as many architecture-specific copies of the system disks asD   required.  Realize that the new systems will all likely be bootingC   through root SYS0 -- if you have any system-specific files in anya   other roots, save them.i  E   Relocate the copies of the VMScluster common files onto each of thei   new system disks.o  D   Reset the console parameters and boot flags on each system for use   on a standalone node.b  D   Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters to 0 in SYSGEN   and in MODPARAMS.DAT.k  <   Clobber the VMScluster group ID and password using SYSMAN.  9   Reboot the systems seperately, and run AUTOGEN on each.a  B   Shut off MOP services via NCP or LANCP on the boot server nodes.  G   Permanent seperation also requires the duplication of shared files.   <   The following files are typically shared within a cluster:  J   Filename:              default directory (in common root) and file type:/     SYSUAF                      SYS$SYSTEM:.DAT-/     SYSUAFALT                   SYS$SYSTEM:.DAT-/     SYSALF                      SYS$SYSTEM:.DAT?/     RIGHTSLIST                  SYS$SYSTEM:.DAT /     NETPROXY                    SYS$SYSTEM:.DATn/     NET$PROXY                   SYS$SYSTEM:.DAT /     NETOBJECT                   SYS$SYSTEM:.DATr/     NETNODE_REMOTE              SYS$SYSTEM:.DATeL     QMAN$MASTER                 SYS$SYSTEM: (this is a set of related files)/     LMF$LICENSE                 SYS$SYSTEM:.LDB 0     VMSMAIL_PROFILE             SYS$SYSTEM:.DATA/     VMS$OBJECTS                 SYS$SYSTEM:.DATr0     VMS$AUDIT_SERVER            SYS$MANAGER:.DAT0     VMS$PASSWORD_HISTORY        SYS$SYSTEM:.DATA0     NETNODE_UPDATE              SYS$MANAGER:.COM0     VMS$PASSWORD_POLICY         SYS$LIBRARY:.EXE@     LAN$NODE_DATABASE           SYS$SYSTEM:LAN$NODE_DATABASE.DAT  :   Information on changing node names is included in MGMT9.    < ------------------------------------------------------------; MGMT46. What file checksum tools are available for OpenVMS?o  F The undocumented DCL command CHECKSUM is the usual means, and providesJ a rather simple-minded checksum suitable to detect basic file corruptions.E For information and an OpenVMS version of the MD5 checksum tool, see:h  H   http://www.service.digital.com/svctools/decevent/md5-instructions.html  H The OpenVMS Alpha ECO (patch) kit checksums available at the ECO website8 are determined using the following DCL command sequence:  "   CHECKSUM kitname.pcsi-dcx_axpexe   SHOW SYMBOL CHECKSUM$CHECKSUMe  A See MGMT25 for information on acquiring OpenVMS ECO (patch) kits.n  < ------------------------------------------------------------9 MGMT47.  Configuring Cluster SCS for path load balancing?a    G SCS: Systems Communication Services.  The protocol used to communicate dD between VMSCluster systems and between OpenVMS systems and SCS-basedF storage controllers.  (SCSI-based storage controllers do not use SCS.)  I PORT: A communications device, such as DSSI, CI, Ethernet or FDDI.  Each eF CI or DSSI bus is a different local port, named PAA0, PAB0, PAC0 etc. : All Ethernet and FDDI busses make up a single PEA0 port.    F VIRTUAL CIRCUIT: A reliable communications path established between a H pair of ports.  Each port in a VMScluster establishes a virtual circuit & with every other port in that cluster.  7 All systems and storage controllers establish "Virtual  H Circuits" to enable communications between all available pairs of ports.  F SYSAP: A "system application" that communicates using SCS.  Each SYSAPE communicates with a particular remote SYSAP.  Example SYSAPs include:o  *   VMS$DISK_CL_DRIVER connects to MSCP$DISK8     The disk class driver is on every VMSCluster system.;     MSCP$DISK is on all disk controllers and all VMSClustero9     systems that have SYSGEN parameter MSCP_LOAD set to 1-  *   VMS$TAPE_CL_DRIVER connects to MSCP$TAPE8     The tape class driver is on every VMSCluster system.;     MSCP$TAPE is on all tape controllers and all VMSCluster :     systems that have SYSGEN parameter TMSCP_LOAD set to 1  +   VMS$VAXCLUSTER connects to VMS$VAXCLUSTERa>     This SYSAP contains the connection manager, which manages <     cluster connectivity, runs the cluster state transition <     algorithm, and implements the cluster quorum algorithm. <     This SYSAP also handles lock traffic, and various other %     cluster communications functions.i  *   SCS$DIR_LOOKUP connects to SCS$DIRECTORY7     This SYSAP is used to find SYSAPs on remote systemsm     MSCP and TMSCP v?     The Mass Storage Control Protocol and the Tape MSCP serversC=     are SYSAPs that provide access to disk and tape storage, s<     typically operating over SCS protocols.  MSCP and TMSCP ;     SYSAPs exist within OpenVMS (for OpenVMS hosts serving A8     disks and tapes), within CI- and DSSI-based storage >     controllers, and within host-based MSCP- or TMSCP storage >     controllers.  MSCP and TMSCP can be used to serve MSCP and=     TMSCP storage devices, and can also be used to serve SCSId1     and other non-MSCP/non-TMSCP storage devices.n  I SCS CONNECTION: A SYSAP on one node establishes an SCS connection to its rJ counterpart on another node.  This connection will be on ONE AND ONLY ONE " of the available virtual circuits.     ----  E When there are multiple virtual circuits between two OpenVMS systems nF it is possible for the VMS$VAXCLUSTER to VMS$VAXCLUSTER connection to I use any one of these circuits.  All lock traffic between the two systems v1 will then travel on the selected virtual circuit.d  H Each port has a "LOAD CLASS" associated with it.  This load class helps G to determine which virtual circuit a connection will use.  If one port PF has a higher load class than all others then this port will be used.  H If two or more ports have equally high load classes then the connection E will use the first of these that it finds.  Normally all CI and DSSI rF ports have a load class of 14(hex), the Ethernet/FDDI port has a load  class of A(hex).  @ For instance, if you have multiple DSSI busses and an FDDI, the G VMS$VAXCLUSTER connection will chose the DSSI bus as this path has the tG system disk, and thus will always be the first DSSI bus discovered whena the OpenVMS system boots.i  H To force all lock traffic off the DSSI and on to the FDDI, an adjustmentF to the load class value is required, or the SCS port must be disabled.  K Note that with PE ports, you can typically immediately re-enable the path, dG permitting failover to occur should congestion or a problem arise -- a  H running average of the path latency is checked when the virtual circuit K is formed, and at periodic intervals (circa every three seconds), and when  ) a problem with a virtual circuit arises. a  E In the case of PEDRIVER, the driver handles load balancing among the pD available Ethernet and FDDI connections based on the lowest latency E path available to it.  Traffic will be routed through that path untilu* an event occurs that requires a fail-over.  / In all OpenVMS versions, you can use the tools:0     SYS$EXAMPLES:LAVC$STOP_BUS o   SYS$EXAMPLES:LAVC$START_BUS   B These tools permit you to disable or enable all SCS traffic on the on the specified paths.-  E You can also use a prefered path mechanism that tells the local MSCP lH disk driver (DUDRIVER) which path to a disk should be used.  Generally, E this is used with dual-pathed disks, forcing I/O traffic through one nH of the controllers instead of the other.  This can be used to implement 9 a crude form of I/O load balancing at the disk I/O level.T  7 Prior to V7.2, the prefered path feature uses the tool:e     SYS$EXAMPLES:PREFER.MAR   A In OpenVMS V7.2 and later, you can use the following DCL command:      SET PREFERED_PATHt  F The prefered path mechanism does not disable nor affect SCS operations on the non-prefered path.GG                               [Kevin Jenkins, Verell Boaen, John Croll]e  < ------------------------------------------------------------; MGMT48. What (and where) is the OpenVMS Management Station?r  E   For information and current kits for the OpenVMS Management StationnG   (OMS), a PC-based tool that permits you to manage an OpenVMS system, t
   please see:   9     http://www.openvms.compaq.com/openvms/products/argus/p  < ------------------------------------------------------------: MGMT49. How to determine current disk fragmentation level?  G   The Compaq OpenVMS Disk File Optimizer (DFO) defragmentation package iL   provides a fragmentation monitoring tool, and a DFO product authorization A   key (PAK) is not required for the fragmentation reporting tool:i     $ DEFRAG SHOW/VOLUME ddcu:  G   The DFU tool available on the OpenVMS Freeware can generate a report h   on the disk fragmentation:     DFU> REPORT ddcu:t    < ------------------------------------------------------------@ MGMT50. SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  ;   A message at the OpenVMS bootstrap such as the following:.  A %SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES_1C02.EXEe< %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000910  @   indicates that the particular OpenVMS release does not contain>   support for the target platform.  In this case, OpenVMS doesB   not recognize Alpha family 1C member 02 as a supported platform.A   A later version of OpenVMS might support the platform, or there %   might be no support on any release.S  E   The execlet load failure and other similar bootstrap status values I@   can often be decoded using either of the following techniques:   $ exit %x910" %SYSTEM-W-NOSUCHFILE, no such file $O   $ x = f$message(%x910) $ show symbol xh*   X = "%SYSTEM-W-NOSUCHFILE, no such file" $o  < ------------------------------------------------------------F MGMT51. How can I customize the DCPS device control for a new printer?  E   To customize DCPS for an otherwise unsupported printer, you can tryy   the following sequence:h  H   o Extract the most closely-associated setup modules from the existing E     device control library, DCPS$DEVCTL.TLB.  (For instance, you can eE     probably extract and use the HP LaserJet 4000 series definitions oD     for the HP LaserJet 4050 series.  Each printer will vary, pleaseF     consult the printer documentation for specifics and requirements.)  :   o rename each extracted setup module to a corresponding:       LPS$$UNRECOGNIZED_*e  G   o Insert all of the above-renamed setup modules into a newly-created n7     device control library specific to the new printer:p       $ LIBRARY/TEXT/CREATE -t/           SYS$COMMON:[SYSLIB]HP4050_DEVCTL.TLB u           LPS$$UNRECOGNIZED*  H     The above assumes the filename HP4050_DEVCTL.TLB, alter as required.  H   o Set up your DCPS startup procedures to include a search-list logical     name such as:   1      $ DEFINE/SYSTEM/EXECUTIVE DCPS_HP4050_LIB  - )          SYS$LIBRARY:HP4050_DEVCTL.TLB, -s$          SYS$LIBRARY:DCPS$DEVCTL.TLB  I   o Supply DCPS_HP4050_LIB as the library parameter in the queue startup oG     for this printer, this is the P3 parameter to the command procedure,)     SYS$STARTUP:DCPS$EXECUTION_QUEUE.COM.i  G   o The HP4050_DEVCTL library may/will need to be recreated and modulestF     re-edited and replaced with each DCPS upgrade, particularly if anyG     modules are updated in the original library.  You will also want to D     determine if the upgraded version of DCPS directly supports the      particular printer.o     Also see MGMT23.D                                          [Ken Fairfield, with typos G                                          introduced by Stephen Hoffman]S  < ------------------------------------------------------------D MGMT52. Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts differ?  C   MOUNTCNT returns the local mount count, while SHOW DEVICE returnsi   the cluster-wide mount count.t  :                                          [Stephen Hoffman]  < ------------------------------------------------------------8 MGMT53. What software is needed for Postscript printers?  F   The NorthLake PrintKit (http://www.nls.com/) and DECprint SupervisorI   (DCPS; http://www.openvms.compaq.com/openvms/Print/print_sw_prods.html)nC   are common choices for support of Postscript printers on OpenVMS.   < ------------------------------------------------------------D MGMT54. Does volume shadowing require a non-zero allocation classes?  C   Yes, use of host-based volume shadowing requires that the disk(s) 8   involved be configured in a non-zero allocation class.  >   Edit SYS$SYSTEM:MODPARAMS.DAT to include a declaration of anA   non-zero allocation class, such as setting the host allocation l   class to the value 7:A     ALLOCLASS = 7A  &   Then AUTOGEN the system, and reboot.  B   You should now be able to form the shadow set via a command such   as the following:K  >     MOUNT dsa1007: /SHADOW=($7$dkb300:,$7$dkb500:) volumelabel  D   When operating in an OpenVMS Cluster, this sequence will typicallyB   change the disk names from the SCSNODE prefix (scsnode$dkann) toE   the allocation-class prefix ($7$dkannn).  This may provide you withoF   the opportunity to move to a device-independent scheme using logicalD   name constructs such as the DISK$volumelabel logical names in yourB   startup and application environments; an opportunity to weed out   physical device references. ;                                               [Veli Korkko]p  < ------------------------------------------------------------? MGMT55. How can I reset the TCP/IP Services default IP gateway?-  E   Either via TCPIP$CONFIG (V5 and later) or UCX$CONFIG (pre-V5) menu,(   or via the TCP/IP command:       Pre-V5:r=       $ UCX SET ROUTE/GATEWAY=x.x.x.x/DEFAULT_ROUTE/PERMANENTt       V5 and later: ?       $ TCPIP SET ROUTE/GATEWAY=x.x.x.x/DEFAULT_ROUTE/PERMANENT   < ------------------------------------------------------------9 MGMT56. How do I remove a PCSI-installed patch (ECO) kit?d  1 You cannot PRODUCT REMOVE a PCSI patch (ECO) kit.   E In order to do this, PCSI would have to have copies of all the other MI version of the files from all other patches and products that previously PE were installed.  This can clearly involve a large number of files and B a large archive of old file versions and a substantial quantity ofC disk space.  While removal is clearly theoretically possible, it is  not currently implemented.  D The following is the supported mechanism to remove a PCSI patch kit.  @ (1) Execute a PRODUCT SHOW PRODUCE <product-name. /FULL command.C     The "MAINTENANCE" column (132 col width) shows the patches that .     have been installed.  Keep a copy of this.  @ (2) Re-install the prior FULL version of the product.  This willA     remove all patch kits, setting to product back to "original" h     condition.  @ (3) Re-install all the patches in the list from step 1, *EXCEPT*4     those which you have determined you do not want.  8 The above information also applies to PCSI PARTIAL kits.  < ------------------------------------------------------------@ MGMT57. SYSINIT-E, error mounting system device, status=0072832C  >   This message can arise during an OpenVMS system bootstrap...  E   %MOUNT-F-DIFVOLMNT, different volume already mounted on this device-  ;   For details and further information, use the DCL command:m  #     $ HELP/MESSAGE /STATUS=%X72832Co   [End of Part 2/5].  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 29 Dec 2000 20:31:27 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 3/5 6 Message-ID: <92isav$f4j$3@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part3e Posting-Frequency: monthly Last-modified: 29 Dec 2000 Version: VMS-FAQ-3.TXT(5)g      9 This is the OpenVMS Frequently Asked Questions Part 3/5. h@ Please see Part 1/5 for administrivia, indexing, archiving, etc.       < ------------------------------------------------------------$ MAIL1.  How do I send Internet mail?  K The simplest answer on most OpenVMS V6.2 and later systems: just enter the OJ Internet (SMTP) address at the "to" prompt in MAIL.  On most such systems,5 this will send your email to the specified recipient.e  L That said, there is no one answer to this question.  Internet mail is built J upon the TCP/IP protocols, which are not directly supported by OpenVMS -- K support requires the installation of a package that understands TCP/IP and  J specifically one that provides the Simple Mail Transport Protocol (SMTP).   P A number of implementations of TCP/IP are available for OpenVMS -- from Compaq, J from third parties, and even a free "support it yourself" form.   The MAILL program  that comes with OpenVMS does not directly support the mail protocolJ used on the  Internet (though it does recognize SMTP addresses in V6.2 andH later), but various  programs have been written that use MAIL's "foreignE protocol" facility to provide  such support -- these tools are callediM transports.  To send mail through a transport,  place the transport specifiers2 at the front, and (typically) quote the address.    H For example, IN%"hoffman@bogushost.compaq.com" -- you *must* include theM quotation  marks -- indicates that IN transport will be used to send the mail M to the address  hoffman@bogushost.compaq.com.  Common names for the transport P are IN%, MX%, and SMTP%. (MX is a widely used, free, mail handler; see question O SOFT1.  SMTP% is used by  Compaq's TCP/IP Services product.)  Other systems mayEM use some other name.  If none  of these prefixes work, please ask your systemi manager for assistance.e 					[leichter@lrw.com]  					[Stephen Hoffman]   See also MAIL2.F  < ------------------------------------------------------------J MAIL2.  How do I get IN% or MX% added automatically to Internet addresses?  E For older OpenVMS releases, you can acquire the MAILSHR_PATCH package B (there's one each for VAX and Alpha) from the WKU FILESERV server  (see question SOFT1.).  H As of OpenVMS V6.2, this is not necessary -- simply enter the SMTP emailK address directly.  If the address specified to MAIL contains an embeded "@"-J character in it (a quoted string is not needed), MAIL will look to see if I the logical name MAIL$INTERNET_TRANSPORT is defined.  If it is, then MAILsJ will use the translation as the transport protocol, otherwise it will use ? the SMTP transport as is used by TCP/IP Services for OpenVMS.  ,  B To alter this, for example, if you wanted IN% added, you'd define   MAIL$INTERNET_TRANSPORT as "IN".  < ------------------------------------------------------------K MAIL3.  How do I automatically append a signature file to my mail messages?c  I OpenVMS 7.0 adds the ability to automatically append signature files - incE MAIL, use the SET SIGNATURE command to specify a signature file name.-3 For earlier versions, see the following paragraphs.t  K The basic MAIL utility which is shipped with VMS does not have an intrinsic G mechanism for adding signature files.  If you're using an enhanced maileG handling package (e.g PMDF), however, it may have provisions for addingtH signature files to all messages it handles - check the documentation forF details.  In addition, it's common practice to use an editor to handleK addition of `quotation marks' (e.g. >) and signature files to mail messagesEK and news postings.  There are several implementations of this for differentwH editors available on the net; for one example, see the MAIL_EDIT package
 available at e+   ftp://narnia.memst.edu/mail_edit_v1-4.zip   					[bailey@genetics.upenn.edu]  F Define the logical MAIL$EDIT to a COM-file, which looks something like the following:   $ IF P1 .NES. "" $ THEN# $    COPY 'P1',<signaturefile> 'P2'S $ ELSE $    COPY <signaturefile> 'P2' $ ENDIF $ $ DEFINE/NOLOG SYS$INPUT SYS$COMMAND $ <editorname> 'P2'o $ EXIT  L Where <signaturefile> is the name of the signature-file (including directoryM and disk) and <editorname> is EDIT/EDT or EDIT/TPU (or your favorite editor).t 					[Arne Vajhj]  < ------------------------------------------------------------A MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.   M Several Unix mailers have been ported to VMS, some by the vendors of specificPL TCP/IP packages, some by users who have made them freely available.  See theF documentation for your TCP/IP package, and refer to question SOFT1 for5 information about the availability of the free ports.a 					[Jerry Leichter]e  < ------------------------------------------------------------L MAIL5.  How can I forward my mail?  Can I forward it to an Internet address?  M You can use the SET FORWARD command within MAIL to specify where you want allmM your mail forwarded to.  Use SHOW FORWARD to see your current forwarding.  ToC* cancel all forwarding, type SET NOFORWARD.  L You can forward your mail to an Internet address, but you have to be carefulL because of the way MAIL handles special characters, such as quotation marks.M First, determine the address you would use to send mail to the place you wanttG to forward to - say, IN%"fred@fred-host.xxx.com".  Take that string andcJ *double all the quotation marks*, producing IN%""fred@fred-host.xxx.com"".L Finally, wrap quotation marks around the outside and use the the result with SET FORWARD:  1 	MAIL>SET FORWARD "IN%""fred@fred-host.xxx.com"""r  + If you do SHOW FORWARD, you should now see:   = 	Your mail is being forwarded to IN%"fred@fred-host.xxx.com".  					[leichter@lrw.com]e  C Note that the MAIL$INTERNET_TRANSPORT feature doesn't yet work witheF SET FORWARD in that you'll still have to use the syntax above with the quotation marks.  < ------------------------------------------------------------9 MAIL6.  How can I forward my mail to a list of addresses?S  H VMS MAIL does not support forwarding a message to more than one address.L (Older versions of MAIL allowed you to specify such forwarding, but it never worked correctly.)  M Many of the TCP/IP mail packages support forwarding to mailing lists, as doescJ the free MX mail handling system and the DELIVER mail "extender".  See the8 documentation of your TCP/IP package and question SOFT1. 					[leichter@lrw.com]s  < ------------------------------------------------------------J MAIL7.  MAIL keeps saying I have new messages, but I don't.  What do I do?  G The count of new mail messages is kept separately from your mail foldercI in SYS$SYSTEM:VMSMAIL_PROFILE.DATA.  It sometimes happens that this counthG differs from what's in your mail folder.  If this happens, go into MAILiI and repeat the READ/NEW command until you see no new mail messages.  ThentG enter the command one more time.  This will resynchronize the counters.s  < ------------------------------------------------------------@ MAIL8.  How do I move all of my mail messages to another system?  N If you are moving to another OpenVMS system, perhaps the best way is to select each folder and do (in MAIL) a:t  # 	EXTRACT/APPEND/ALL/MAIL mymail.mai   < Move MYMAIL.MAI to the other system, then do this (in MAIL):   	SET FILE mymail.mai 	COPY/ALL foldername MAIL.MAI   G This will place a copy of all of your messages in the given folder.  IfiI you wanted to maintain the separate folders, do separate EXTRACT commandsYG (above) specifying different .mai files, then repeat the SET FILE, COPY 
 for each one.i  H If you are moving to a non-OpenVMS system, the EXTRACT command above canI be used to create a file which you can then copy - how you import it into . your mailer is an exercise left to the reader.  < ------------------------------------------------------------6 MAIL9.  How do I send or read attachments in VMS MAIL?  I Is there any way to send or read mail with files as attachments from VMS?   C Not directly with the OpenVMS MAIL facility, but there are several h other options:  H 1. Install PINE, available commercially from Innosoft or free from Andy F    Harper.  With PINE you can both send and receive MIME messages, if .    you have the appropriate viewers available.      http://www.innosoft.com/ 4      http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/+      ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/-  K 2. If you're working from an X11 server use the OpenVMS version of NetscapetI    Navigator.  This option is ok for sending mail, but is not optimal for H    reading it, since Netscape will use POP and remove messages entirely A    the OpenVMS MAIL system, which is not generally what you want.m  B 3. MPACK/MUNPACK.  To send a MIME mail, construct the message withH    attachments manually using MPACK.  You cannot send the resulting fileD    directly through MAIL because an extra  blank header line will beI    inserted between your message and the OpenVMS MAIL headers, which willzI    cause the message to appear as plain text in most mail programs.  Some D    TCP/IP stacks provide a work around for this problem, and if thatK    doesn't work, you should generally be able to force the message directlyRI    into the SMTP port of your mail machine.  Examples of both methods are-    in: 0:      http://seqaxp.bio.caltech.edu/pub/SOFTWARE/mmail.com   K    To read a MIME mail message, open it in MAIL, extract it to a file, thenL;    use MUNPACK to break out and decode the attachments.    T   					[David Mathog]a  ; 4. With OpenVMS V7.2 and later, use the supplied MIME tool.     < ------------------------------------------------------------4 UTIL1.  How do I play an audio CD on my workstation?  8 If you've installed the DECwindows examples, you'll findD DECW$CDPLAYER.C, .DAT, .EXE, .UIL, and .UID.  Copy the .UID and .DATL files to DECW$USER_DEFAULTS: (typically SYS$LOGIN:), define the logical nameH DECW$CD_PLAYER to be the device name of your CD-ROM drive (eg. DKA400:),G give yourself PHY_IO and DIAGNOSE privileges, and run the .EXE.  (These H privileges are required, as the access to the CD-related extensions willK require the use of the privilege-protected IO$_DIAGNOSE I/O function code.)GI You can also install the image with these privileges.  See the source foroB additional details - note that the comments regarding the need forD SYSGEN CONNECT are no longer applicable (at least as of VMS V5.5-2).  F There's also SYS$EXAMPLES:CDROM_AUDIO.C and .EXE, a non-Motif program,F available on OpenVMS VAX, and DECW$EXAMPLES:DECW$CDPLAYER.* on OpenVMS VAX and OpenVMS Alpha.  A The standard OpenVMS IDE DQDRIVER does not support the necessary  H IO$_DIAGNOSE function required for access to audio CD media (on OpenVMS G versions prior to V7.3), but an updated DQDRIVER device driver (source  J code and all) with this capability and with the source code of an updated = CD audio player is available on the OpenVMS Freeware website eH (www.openvms.compaq.com/freeware/dqdriver/), and these updates are also 3 expected to be included on Freeware V5.0 and later.   < ------------------------------------------------------------: UTIL2.  How do I access a MS-DOS floppy disk from OpenVMS?  E The Compaq Advanced Server (formerly known as PATHWORKS) for OpenVMS EG product includes an unsupported and undocumented utility called PCDISK, A and this tool can read and write various MS-DOS format diskettes.   H ProGIS in Germany sells a product called VMove which supports DOS files C on many different device types.  For more information, send mail toU info@progis.de.   H Engineering Software has a product called VAKSAT which will read, write,D and erase files on DOS diskettes.  Available for both VAX and Alpha.0 Contact ed@cityscape.co.uk for more information.  D MadGoat PC Exchange (PCX) is a utility for copying files to and fromD MS-DOS (FAT) format diskettes under VMS, using an RX23 (3.5"), RX26 I (3.5"), or RX33 (5.25") diskette drive.  For 3.5" diskettes, high-density F disks can be read or written; double-density disks are read-only. Only- high-density disks are supported on the RX33.-     http://www.madgoat.com/$  < ------------------------------------------------------------L UTIL3.  How do I play sound files on an AlphaStation?  DECsound doesn't work  I The new AlphaStation systems use a different sound board (Microsoft Sound]K System) than the earlier DEC 3000 AXP systems, and DECsound, as supplied bytH DECwindows Motif, doesn't support this board.  Compaq offers an optional) product, Multimedia Services for OpenVMS:r  !   http://www.compaq.com/info/spd/c   J which provides a replacement DECsound for this card as well as many other > features (an AVI and MPEG player, video capture support, etc.)  ( Ensoniq sound support is also available.  < ------------------------------------------------------------3 UTIL4.  Why is DECmigrate not working with Fortran?   : OTS-F-INDATCOR internal data corrupted in Run-time Library  @ This error can arise with Fortran programs if you are running a < recent version of OpenVMS Alpha, and are using DECmigrate toA translate Fortran applications.  The DECmigrate Run-Time Library TA attempts to support mixed translated-native I/O to the same unit eA by sharing the native Fortran RTL's internal data structures, ands> in OpenVMS 7.2 these structures changed and the translated RTL was not updated accordingly.  A You can copy DEC$FORRTL.EXE from OpenVMS 7.1, copying it to some EB spare directory, and then defining the logical name DEC$FORRTL to G point to it before running your translated application.  Or rebuilding eA the application to use the available native Fortran compiler.  OrlD you can apply the current Fortran RTL kit, which has a fix for this.   See SOFT13.y2                                     [Steve Lionel]  < ------------------------------------------------------------2 UTIL5.  How do I read IBM EBCDIC tapes on OpenVMS?  I IBM boxes can read ANSI-labeled ASCII magtapes.  Fixed-length records andhJ the DCL COPY command can be used to transfer text files around.  Check the IBM documentation for details.  K There exists various freeware around (TAPECOPY, ETAPE, TCOPY, MTEXCH) that dK can read and write EBCDIC tapes.  Visit the DECUS website software archives C search engine (via http://www.decus.org/), and search for "EBCDIC". 3                                     [Steve Hoffman]    One source for ETAPE is:  (   http://www.ualr.edu/ftp/vms/ETAPE_SRC/  7 OpenVMS Freeware V5.0 is expected to include this tool.o5                                     [Fletcher Hearns] 1                                     [Dale Miller]o  < ------------------------------------------------------------/ UTIL6.  How can I patch an OpenVMS Alpha image?   &   Using the OpenVMS Freeware tool ZAP:  .     www.openvms.compaq.com/freeware/rms_tools/  ?   tell ZAP to read a block (bucket) of information based on the <   virtual block number (VBN), using X for hexadecimal.  Dump?   yourself into the OpenVMS debugger with R2 pointing into the s<   buffer, EXAMINE/INSTRUCTION as needed, alter the buffer as@   required, GO to get out of the debugger and back into ZAP, and3   use the ZAP W command to write the updated block.i  >   OpenVMS Freeware V5.0 is expected to have an updated version   of the ZAP tool.    < ------------------------------------------------------------. DCL1.   How do I run a program with arguments?  K The RUN command does not accept arguments.  To pass arguments to a program, > you must use what is called a "foreign command".  For example:  ! 	$ unzip :== $disk:[dir]unzip.exeS 	$ unzip -?t  H The leading $ in the equivilence name for the symbol definition is what G makes the DCL symbol a foreign command. If the device and directory are   omitted, SYS$SYSTEM: is assumed.  D Under OpenVMS V6.2 and later, DCL supports automatic foreign commandG definition via the logical name DCL$PATH:.  An example of a definition i of this logical name is:  >     $ DEFINE DCL$PATH SYS$DISK:[],ddcu:[mytooldir],SYS$SYSTEM:  N DCL will first look for a command in the DCL command table, and if no match isN found and if DCL$PATH is defined, it will then look for command procedures andG executable images with filenames matching the command specified, in thecJ directories specified via DCL$PATH.  The first match found is invoked, andH under OpenVMS, the DCL$PATH support will cause a command procedure to be/ activated in preference to an executable image.   H For more information on foreign commands or on automatic foreign command' support, see the OpenVMS User's Manual.p   See also question PROG2.  L If you want to create a detached process that takes arguments from a commandJ line, it must be run under the control of a command line interpreter (CLI)E (typically DCL).  This is done by placing the command line in a file, N specifying SYS$SYSTEM:LOGINOUT.EXE as the image to run and the command file as the input.  For example:    	$ OPEN/WRITE CMD TEMP_INPUT.COM$ 	$ WRITE CMD "$ MYCOMMAND arguments" 	$ CLOSE CMD9 	$ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM   N Various OpenVMS library calls (such as lib$spawn(), cli$dcl_parse(), and the CK library system() call) require access to a command line interpreter such asLF DCL to perform requested actions, and will not operate if a CLI is not
 available.  J When a CLI is not available, these calls typically return the error statusL SS$_NOCLI.  And as mentioned above, invoke the image LOGINOUT to cause a CLIH (such as DCL) to be mapped into and made available in the context of the target process.o  G For examples of how TCP/IP Services sets up its foreign commands (whichlI includes tools such as uuencode and uudecode), please see the DCL command-0 procedure SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM.   Also see DCL11.p 					[Stephen Hoffman]  < ------------------------------------------------------------/ DCL2.   How can I redefine control keys in DCL?P  C The DCL DEFINE/KEY command allows you to define function and keypadPF keys, but not control keys.  Also, keys you define with DEFINE/KEY areD not recognized inside applications.  Many applications which use the: SMG$ routines for input have a similar DEFINE/KEY feature.  G The terminal driver line-editing control keys, including the use of DEL- for delete, are not modifiable.A  < ------------------------------------------------------------* DCL3.   How can I clear the screen in DCL?  0 The simplest way is the TYPE/PAGE NLA0: command.  > You can set up a symbol to clear the screen in your LOGIN.COM:   $ CLS :== TYPE/PAGE NLA0:   < ------------------------------------------------------------< DCL4.   Using REPLY/LOG from DCL?  Disabling Console OPCOMs?  @ Your terminal must be enabled as an operator terminal before theA REPLY/LOG command can be used, but a DCL procedure (batch commandi@ file, system startup, etc) does not have an associated terminal.B To make this work, use the following sequence to enable the OPA0: B console as the operator terminal, then the REPLY/LOG command will  be accepted:  "   $ DEFINE/USER SYS$COMMAND _OPA0:
   $ REPLY/LOGN"   $ DEFINE/USER SYS$COMMAND _OPA0:   $ REPLY/ENABLE  H To disable the system console terminal (OPA0:) as an operator terminal,  use the following command:  "   $ DEFINE/USER SYS$COMMAND _OPA0:   $ REPLY/DISABLEs  A Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) for informationlC on configuring the behaviour of OPCOM, including the (default) use  ? of the system console (OPA0:) as an operator terminial and the r@ specific contents and behaviour of the system operator log file 
 OPERATOR.LOG.  						[Arne Vajhj]  						[Stephen Hoffman]v  < ------------------------------------------------------------1 DCL5.   How do I generate a random number in DCL?d  B Here's my random number generator for inclusion into the OVMS FAQ;@ just do a GOSUB RAND and the global symbol RANDOM will contain aF randomly generated number.  The user/programmer can feed the generator0 a ceiling value (__CEIL) or a new seed (__SEED).  D $! RAND - returns a positive random number ("RANDOM") between 0 and  $!        __CEIL - 1.[ $ RAND:n $c $ IF F$TYPE(__SEED) .EQS. "" $ THEN- $     ! seed the random number generator, ...e $     __NOW = F$CVTIME()& $     __HOUR = 'F$EXTRACT(11,2,__NOW)'( $     __MINUTE = 'F$EXTRACT(14,2,__NOW)'( $     __SECOND = 'F$EXTRACT(17,2,__NOW)'& $     __TICK = 'F$EXTRACT(20,2,__NOW)' $ A $     __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + -i          (360000 * __HOUR)D $     ! the generator tends to do better with a large, odd seed, ... $     __SEED == (__SEED .OR. 1)- $     ! clean up, ...- $     DELETEX/SYMBOL __NOW $     DELETEX/SYMBOL __HOURM $     DELETEX/SYMBOL __MINUTEt $     DELETEX/SYMBOL __SECONDv $     DELETEX/SYMBOL __TICK  $ ENDIFr $f5 $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFFe $e $ __SEED == __SEED * 69069 + 1 $e7 $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)F $f $ RETURN$ 					[sharris@sdsdmvax.fb3.noaa.gov]  < ------------------------------------------------------------% DCL6.   What does the MCR command do?L  D The MCR command runs the specified image, with a default filespec ofH SYS$SYSTEM:.EXE, and passes any (optional) command line arguments in the2 same manner as a foreign command.  In other words:   	$ MCR FOO BAR   is equivalent to:a   	$ FOO :== $FOO,
 	$ FOO BAR  F It derives from the RSX operating system from which VMS evolved and isI still often used as a shortcut for activating images.  The MCR command is J different from the MCR command line interpreter, which is provided as partI of the optional VAX-11 RSX product that provides RSX emulation under VMS.k  < ------------------------------------------------------------2 DCL7.   How do I change the OpenVMS system prompt?  M You can use the SET PROMPT command for this purpose.  SET PROMPT sets the DCLE prompt to the specified string.x  K When you want to display variable information, you will need to establish a K tie-in that provides the information to the SET PROMPT command as required.t  K If you wish to display the default directory for instance, you will have totL establish a tie between the SET DEFAULT command and the SET PROMPT commands,N as there is no direct way to get the default directory as the DCL prompt.  YouM can easily acquire or create a set of DCL command procedures that perform theaM SET DEFAULT and SET PROMPT for you.  These DCL command procedures often use ai command such as:  !   $ set prompt='f$env("default")'   L More advanced users could implement a system service or other intercept, andF use these tools to intercept the directory change and reset the promptN accordingly.  (This approach likely involves some kernel-mode programming, andG requires write access to various undocumented OpenVMS data structures.)A  E There are related tools available from various sources, including the  following web sites:  $   o ftp://ftp.hhs.dk/pub/vms/setpmt/  -   o ftp://ftp.tmesis.com/sys_service_hook.src   A   o James F. Duff has also made available a Macro32 tool known asaH     TIME_PROMPT, a tool that sets the prompt to the current system time.  D   o Many folks have contributed DCL procedures to perform this task.>     Visit the newsgroup archives for information and examples.  H Information in this section has been acquired from various postings thatG have discussed this topic in the comp.os.vms newsgroup in the past, andVI examples from Arne Vajhoej, Brian Schenkenberger, James Duff, and others.a   				[Stephen Hoffman]/  < ------------------------------------------------------------< DCL8.   Can I do DECnet task-to-task communication with DCL?   Yes, you can do this with DCL.  H The OpenVMS DECnet documentation shows various simple examples using theJ task object and the TYPE command to trigger the execution of a DCL commandJ procedure on a remote node.  A slightly more advanced example of using DCLJ for DECnet task-to-task -- a procedure that acts as both the client and asD the server as appropriate, and that uses a basic form of half-duplex communications -- is included:           $! x.com	         $-@         $! This procedure must be in the user's login directory.B         $! Requires a self-referential (not reverential :-) proxy:L         $!    UAF> add/prox <LocalNode>::<CurrentUser> <CurrentUser>/default?         $! Author: Stephen Hoffman, OpenVMS Engineering, Compaqa	         $a         $ goto 'f$mode()'n         $INTERACTIVE: *         $ open/read/write chan 0::"task=x"         $ write chan "Hello"         $ read chan parameterw         $ close chan$         $ write sys$output parameter         $ exit         $BATCH:n         $OTHER:/         $NETWORK:/&         $ open/read/write chan sys$net         $ read chan parameterM-         $ write chan "''parameter' yourself!"i         $ close chan         $ exit  -   An example of a run of the above procedure:u           $ @x         Hello yourself!t	         $M    L DCL does not include support asynchronous I/O, thus a predetermined protocolH or a predetermined "turn-around" command sequence must be implemented inI order to avoid protocol deadlocks -- cases where both tasks are trying to J write or both tasks are trying to read.  The task that is writing messagesI to the network must write (or write and read) a predetermined sequence ofeJ messages, or it must write a message that tells the reader that it can nowL start writing messages.  (This is the essence of a basic half-duplex network protocol scheme.)r 					[Stephen Hoffman]  < ------------------------------------------------------------6 DCL9.   How can I get the width setting of a terminal?  *   $ width = f$getdvi(terminal,"DEVBUFSIZ")  < ------------------------------------------------------------/ DCL10.  How can I substitute symbols in a PIPE?[  :   Use ampersand substitution, not apostrophe substitution.  G     $ pipe show system | search sys$input opcom | (read sys$input pid ;-C            pid=f$element(0," ",pid) ; define/system opcom_pid &pid)u     $ show log opcom_pid2        "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE);                                            [Norm Lastovica]R  < ------------------------------------------------------------7 DCL11.  Use of RUN/DETACH, LOGINOUT, and logical names?.  6   With a command to create a detached process such as:  <     $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM  C   If you are trying to use a logical name as the /INPUT, /OUTPUT orpE   /ERROR on a RUN/DETACH command, then you must translate the logicalaD   name specifications to physical references before passing them, orF   the definitions must reside in a logical name table that is visible    to the newly-created process.   H   Also note that LOGINOUT only creates the SYS$LOGIN, SYS$LOGIN_DEVICE, J   and SYS$SCRATCH logical names if it is processing a login that is based H   on the contents of a SYSUAF record -- without access to the associatedI   SYSUAF record, this information is not available to LOGINOUT.  (If you CI   want to see these particular logical names created, then please specifyc8   the /AUTHORIZE qualifier on the RUN/DETACHED command.)  I   If you do not specify LOGINOUT as the image, then there is no easy way nL   to get these logical names.  Also, any logical names that are used in the G   target image file specification must also be in a logical name table  I   accessable (by default) by the newly-created detached process.  Shared  I   tables include the group (if the process is in the same UIC group) and rK   the system table.  (If the target process is to be in another UIC group,  F   a suitablly privileged user or application can create the necessary B   logical name(s) directly in the other group logical name table.)  D   When in doubt, create a short DCL command file as input, and use aE   SHOW LOGICAL and similar commands to examine the context.  (And userC   physical device and directory references on the RUN/DETACH of the E   LOGINOUT image, when specifying this command file as /INPUT.)  AlsocF   remember to check both security auditing and system accounting when /   troubleshooting problems with the RUN/DETACH.S     Also see DCL1.  < ------------------------------------------------------------8 DCL12.  How to use escape and control characters in DCL?  6   To write a message and then the bell character, use:       $ bell[0,7] = 7y%     $ write sys$output "Hello''bell'"      To write blinking text, use:       $ esc[0,7] = 27-     $ text = "Blinking Text"1     $ write sys$output "''esc'[5m''text'''esc'[m"i  !   Also see sections DECW9, MISC2.   < ------------------------------------------------------------" FILE1.  How can I undelete a file?  G OpenVMS doesn't have an "undelete" function.  However, if you are quickpH to write-protect the disk (or if you can guarantee that no new files getC created or existing files extended), your data is still on the disksG and it may be possible to retrieve it.  The FLORIAN tool available fromnE the WKU Fileserver claims to be able to do this (see question SOFT1.)pF Other alternatives here include the DFU tool, available on the OpenVMS Freeware CD-ROM distribution.D  G If you are setting up a user environment for yourself or for others, ittI is quite easy to use DCL to intercept the DELETE command, using a symbol:   '   $ DEL*ETE :== @SYS$LOGIN:MYDELETE.COMl  J The DELETE symbol will cause the procedure to be invoked whenever the userF enters the DELETE command, and it can copy the file(s) to a "trashcan"K subdirectory before issuing a "real" DELETE on the files.  Other proceduresrG can retrieve the file(s) from the "trashcan" subdirectory, and can (and K should) clean out the "trashcan" as appropriate.  (Realize that this DELETE H symbol can interfere with DELETE/GLOBAL and other similar DCL commands.) 					[Stephen Hoffman]  < ------------------------------------------------------------B FILE2.  Why does SHOW QUOTA give a different answer than DIR/SIZE?  E DIR/SIZE doesn't take into account the size of file headers which are J charged to your quota.  Also, unless you use DIR/SIZE:ALL, you'll see onlyF the "used" size of the file, not the allocated size which is what getsK charged against your quota.  Also, you may have files in other directories.t 					[Steve Lionel]e  ! $ DIR/SIZ=ALL/GRAND [username...]b  6 Grand total of D1 directories, F1 files, B1/B2 blocks.  # $ DIR/SIZ=ALL/GRAND [-]username.DIRv  1 Grand total of 1 directory, 1 file, B3/B4 blocks.H   $ SHOW QUOTA3   User [username] has B5 blocks used, B6 available,o?   of B7 authorized and permitted overdraft of B8 blocks on disks  F If the user has no files in other directories and all file-headers are. only 1 block, then the following should apply:     B5=B2+B4+F1+1_  M If the diskquota is out of synch, then the system-manager can make a rebuild.  					[Arne Vajhj]  G Also be aware that the DIRECTORY/SIZE command can report larger values -D than might otherwise be expected when used to evaluate files and/or H directories that are alias links -- such as the system roots on OpenVMS G system disks -- as the command reports a total that is cumulative over  I all of the files and directories examined, without regard for which ones (M might be alias entries and which are not.  (In other words, a DIRECTORY/SIZE  M of an entire OpenVMS system disk will report a disk useage value larger than eL the (usually more accurate) value reported by the SHOW DEVICE command.  ThisP as a result of the alias entries linking each SYS$SYSDEVICE:[SYSCOMMON]SYS*.DIR K directory file and the SYS$SYSDEVICE:[000000]VMS$COMMON.DIR file together.)-  < ------------------------------------------------------------B FILE3.  How do I make sure that my data is safely written to disk?  E If your application must absolutely guarantee that data is available,nK no matter what, there's really no substitute for RMS Journalling.  However, J you can achieve a good degree of data integrity by issuing a SYS$FLUSH RMSD call at appropriate times (if you're using RMS, that is.)  If you'reM using a high-level language's I/O system, check that language's documentationrF to see if you can access the RMS control blocks for the open file.  InC C you can use fflush followed by fsync.  Note that fsync, which wasIK undocumented for VAX C but is documented for DEC C, takes a file descriptoro as an argument, not a *FILE.  < ------------------------------------------------------------C FILE4.  What are the limits on file specifications and directories?l  G A file specification has an aggregate maximum size of 255 characters atCN present.  The node and device specification may be up to 255 characters each -L file name and file types may be up to 39 characters each.  File versions areK from 1 through 32767, though 0 (latest version), -0 (oldest version) and -niK (n'th previous version) can be used in most contexts.  A file specificationGN may not have more than 8 directories and subdirectories - while it is possibleK to create subdirectories of greater depth, accessing them is problematic in)' most cases and this should be avoided. n  G Application developers should use OpenVMS-supplied routines for parsingmI file specifications - this ensures that changes in what is allowable willTG not tend to break your application.  Consider that various parts of the F file specification may contain quoted strings with embedded spaces andI other punctuation!  Some routines of interest are SYS$FILESCAN, SYS$PARSErI and LIB$TRIM_FILESPEC.  For further information, see the OpenVMS Guide to  File Applications.  < ------------------------------------------------------------@ FILE5.  What is the largest disk volume size OpenVMS can access?  D One Terabyte (2**31 blocks of 2**9 bytes).  Prior to the release of D V6.0, the OpenVMS file system was limited to disk volumes of 8.38 GB( (2**24 blocks, 16777216 blocks) or less.  M On some systems, there are restrictions in the console program that limit theoJ size of the OpenVMS system disk.  Note that data disks are not affected byH console program limits.  For example, all members of the VAXstation 3100K series are limited to a system disk to 1.073 GB or less due to the console, & though larger data disks are possible.  D Some SCSI disks with capacities larger than 8.6 gigabytes (GB) will G require the use of an OpenVMS ECO kit (eg: ALPSCSI04_062 or later) for eF new SCSI device drivers.  Failure to use this ECO can cause "rounding E errors" on the SCSI disk device capacity -- OpenVMS will not use nor nJ display the full capacity of the drive -- and  "%sysinit-e-error mounting E system device status equals 000008C4" (8C4 -> "%SYSTEM-?-FILESTRUCT, -B unsupported file structure level") errors during bootstrap.  (One E workaround for the bootstrap when the bitmap is located far into the cD disk is the use of INIT/INDEX=BEGIN.)  The problem here involves theG particular extensions and fields used for larger capacity disks within  F the SCSI specifications and within the various intepretations of same. 					[Stephen Hoffman]   For IDE disk drives:  >   o Versions of DQDRIVER *BEFORE* X-15 topped out at 8.455 GB.-     Fixed drivers (>="X-15") were shipped in:i  %       OpenVMS Alpha V7.2-1, and latere%       V7.2 UPDATE V1.0 ECO, and later '       V7.1-2 UPDATE V1.0 ECO, and latert'       V7.1-2 UPDATE V3.0 ECO, and later   <   o The newer DQDRIVER driver operates to disks up to 33 GB ?     without (known) problems, and effectively works with rathereA     larger disks (up to circa 137 GB?) but is known to report an w;     incorrect number of "cylinders" with disks above 33 GB./  6   See ALPHA23 for additional IDE DQDRIVER information.  C Be aware that a known restriction in certain older versions of the t? Alpha SRM Console prevents booting most IDE drives larger than tC 8.455 GB, depending on exactly where the various files are located rB on the volume.  Updated SRM consoles for systems with SRM and IDE A drive support are (will be) available.  (OpenVMS Engineering has -? successfully bootstrapped 20GB IDE disks using the appropriate e SRM console version.)e  C NOTE: All IDE-related disk sizes listed in this section are stated oB in units of "disk (base 10) gigabytes" (1GB = 10^9 bytes) and NOT D in units of "software (base 2) gigabytes" (1GB = 2^30 (1073741824.)  bytes. _:                                           [Atlant Schmidt]  D Be aware that larger disks that are using an extension of SCSI-2 -- D disks that are using a mode page field that the SCSI specifications E normally reserved for tape devices -- to permit a larger disk volume  D size will require a SCSI driver update for OpenVMS, and this change F is part of V7.1-2 and later, and also part of ALPSCSI07_062 and later.F (These larger disks disks will typically report a DRVERR, or will see I the volume size "rounded down".)  SCSI disks larger than 16777216 blocks  F cira 8.455 GB (base ten); 8GB (base two) require this ECO, or require ) the use of OpenVMS Alpha V7.1-2 or later.      Also see VAX5.  < ------------------------------------------------------------E FILE6.  What is the maximum file size, and the RMS record size limit?F  D RMS can store individual files of a size up to the maximum supportedG volume size.  Under OpenVMS V6.0 and later, the volume size and the RMS3D maximum file size limit is 2**31 * 512 bytes -- one terabyte (1 TB).  F The RMS formats -- sequential, relative, and indexed -- are limited byE the one terabyte maximum volume size.  RMS relative files are further D limited to a number of records that will fit in 32 bits -- 4 billionE records.   Sequential and indexed formats do not have a record limit.$   Also see PROG14. 					[Stephen Hoffman]  < ------------------------------------------------------------= FILE7.  How do I write recordable CD media (CD-R) on OpenVMS?d  B Creation of CD-ROMs using recordable CD media (CD-R) under OpenVMSA typically involves one of two approaches: the use of the optionaluB CD-R (`Scribe') capabilities available for the InfoServer or otherD "offline" hardware packages, or the use of a host-based package such> as the CDWRITE13_VMS utility, an OpenVMS port of a Linux tool.  ; OpenVMS has no integrated support for recording CD-R media.n  6 OpenVMS can read both ODS2 and ISO9960 format CD-ROMs.  F InfoServer hardware configurations are no longer availble from Compaq,4 but may potentially be acquired through other means.  E The CDWRITE13_VMS package is one example of a host-based package thatAC can be used to create CD-R media.  The contact for CDWRITE13_VMS isoE Dr. Eberhard Heuser-Hofmann.  One website that discusses this packageo is located at:  A   http://www.geocities.com/SiliconValley/Lakes/9999/vmscdwri.htmlT  4 Also see the newest linux-cdwrite package, XCDROAST.  = Additional information is available via David J. Dachtera at:n  &   http://www.djesys.com/vms/cdrom.html  	 Also see:e  6   http://www.cd-info.com/CDIC/Technology/CD-R/vms.html  B   http://www.faqs.org/faqs/cdrom/cd-recordable/part1/preamble.html  m   http://www.tmesis.com/CDrom/     http://www.tditx.com/~odsiso/d  ;                                           [Stephen Hoffman]   B U.S. Design offers a package that includes the tools necessary to B create a CD with either 9660 or ODS-2 format, for standalone CD-R D drives, for OpenVMS Alpha V7.1 and later.  Details are available at:     http://www.usdesign.com/;                                            [Harry Garonzik]m  < ------------------------------------------------------------7 FILE8.  What I/O transfer size limits exist in OpenVMS?i  G The maximum transfer size is an attribute of the particular I/O device,oE controller and driver combination; there is no inherent limit imposedpE by OpenVMS (other than the fact that, today, byte counts and LBNs area generally limited to 32 bits).  C The maximum size of a device I/O request is limited by the value in-A UCB$L_MAXBCNT, which is set by the device driver based on variousCD factors.  (Also check the setting of the MAXBUF system parameter for6 buffered I/O transfers, and check the process quotas.)  D Currently, SCSI drivers limit I/O transfers to FE00(16) bytes, 65024K bytes (decimal).  The reasons for this transfer size limitation are largelytC historical.  Similarly, DSSI devices are limited to the same value, D this for hardware-specific reasons.  Transfers to HSC and HSJ deviceJ controllers via the CI are limited to 1,048,576 bytes.  Client MSCP-servedA devices are limited to 65535 bytes -- to help ensure that the I/OeD fragmentation processing happens on the client and not on the server system.L  H Parts of the OpenVMS I/O subsystem are optimized for data transfers lessF than 64KB, because (obviously) most I/O operations are (substantially)G less than that.  OpenVMS can handle larger transfers, if the driver and  the device can handle it."   Also see FILE4, FILE5a  4                                         [John Croll]  < ------------------------------------------------------------< FILE9.  Can I use ODBC to connect to OpenVMS database files?  < Yes, you can use various available third-party packages that; permit remote ODBC clients to access RMS files and various a% commercial databases via the network.   ? For RMS, consider acquiring one of the packages available from n> EasySoft, Attunity Connect (formerly known as ISG Navigator), 4 Oracle (DB  Integrator), SolutionsIQ, and Synergex.   < For specific commercial databases (other than RMS), contact , the database vendor directly for assistance.    < ------------------------------------------------------------: PROG1.  How do I call <routine_name> from <language_name>?  F Most OpenVMS system services and RTL routines pass string arguments byD descriptor.  Languages which support native string data types createK descriptors automatically; those which do not (eg., C) require that you set- them up explicitly.- 					[eric@tardis.HQ.ileaf.com]   F There is a lot of information available on how to call system servicesH and Run-Time Library routines, including examples in numerous languages. The best references are:   	Your language's User Manual' 	OpenVMS Programming Environment Manual $ 	OpenVMS Programming Concepts Manual9 	OpenVMS Programming Interfaces: Calling a System Routine  	OpenVMS Calling Standarde  G In addition, if you are a subscriber to the Compaq Software Information J Network (available to those with a software support contract), the supportH database contains hundreds of worked examples of calling system servicesJ and RTL routines, including the one that seems to trip up almost everyone, SMG$CREATE_MENU. 					[Steve Lionel]a  F Arne Vajhj has put together a collection of OpenVMS example programs. It can be found at:    ftp://ftp.hhs.dk/pub/vms/g 					[Arne Vajhj]  B Additional information and examples for OpenVMS are available via:  '   http://www.openvms.compaq.com/wizard/o)   http://www.openvms.compaq.com/freeware/r   					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG2.  How do I get the arguments from the command line?t  G If you're writing a program and want to accept arguments from a foreignpF command, you can use LIB$GET_FOREIGN to get the command line and parseD it yourself, or if you're programming in C, use the normal argc/argv method.a  J To write an application which uses the normal DCL verb/qualifier/parameterF syntax for invocation, see the description of the CLI$ routines in the3 OpenVMS Callable Utility Routines Reference Manual.   I It is possible to write an application which can be used both ways; if a aL DCL verb isn't used to invoke the image, the application parses the command H line itself.  One way to do this is to call CLI$GET_VALUE for a required= parameter.  If it is not present (or you get an error), call p@ LIB$GET_FOREIGN to get the command line and do the manual parse.   See also question DCL1.   < ------------------------------------------------------------= PROG3.  How do I get a formatted error message in a variable?e  D Use the SYS$PUTMSG system service with an action routine that storesG the message line(s) in the variable of your choice.  Be sure the actioncK routine returns a "false" (low bit clear) function value so that SYS$PUTMSGeI doesn't then try to display the message (unless you want it to.)  See thecE description of $PUTMSG in the System Services Reference Manual for ani# example of using an action routine.u  < ------------------------------------------------------------D PROG4.  How do I link against SYS$SYSTEM:SYS.STB on an Alpha system?  G LINK/SYSEXE is the OpenVMS Alpha equivalent of linking against SYS.STB.a  G Also see PROG11, particularly for pointers to the details on shareable u$ images and shareable image creation.  < ------------------------------------------------------------8 PROG5.  How do I do a SET DEFAULT from inside a program?  H The problem is that SYS$SETDDIR only changes the default directory - NOTI the default disk. The default disk is determined by the logical SYS$DISK.oB If you want to change the default disk within a program, then callJ LIB$SET_LOGICAL to change the logical SYS$DISK. You will need to call bothK LIB$SET_LOGICAL and SYS$SETDDIR to change both default disk and the default 
 directory! 					[Arne Vajhj]	R  < ------------------------------------------------------------M PROG6.  How do I create a shareable image transfer vector on an Alpha system?   K This is something that was greatly simplified for OpenVMS Alpha.  You don'tuL need to create a separate transfer vector module; just use the SYMBOL_VECTORI statement in a linker options file.  For example, if your shareable imageLJ has two routines named FOO and BAR, the linker options file should contain the following line:   - 	SYMBOL_VECTOR=(FOO=PROCEDURE, BAR=PROCEDURE)l  + The Linker manual has more details on this.n  < ------------------------------------------------------------H PROG7.  How do I turn my Fortran COMMON into a shareable image on Alpha?  M You need to add SYMBOL_VECTOR=(<common-name>=PSECT) to your options file.  OnrG OpenVMS VAX all OVR/REL/GBL psects were automatically exported into theoM shareable image's Global Symbol Table.  On OpenVMS Alpha you have to tell the C linker that you want this done by means of the PSECT keyword in theE% SYMBOL_VECTOR options file statement.f  N This has several advantages over OpenVMS VAX.  First, you don't have to worry F about the address of the psect when you try to create a new, upwardly H compatible version of the shareable image. Second, you can control which= psects, if any, are made visible outside the shareable image.N  K By default, COMMON PSECTs in DEC Fortran for OpenVMS Alpha (as well as most L other OpenVMS Alpha compilers) are NOSHR.  On VAX, the default was SHR whichG required you to change the attribute to NOSHR if you wanted your COMMONlG to be in a shareable image but not write-shared by all processes on the , system.  If you do want write-sharing, use:  	CDEC$ PSECT common-name=SHRM in the Fortran source code (the CDEC$ must be begin in column 1) or a linker qK options file PSECT_ATTR statement to set the COMMON PSECT attribute to SHR.e  / For further information, see the Linker manual.o  < ------------------------------------------------------------< PROG8.  How do I convert between IEEE and VAX floating data?  G In OpenVMS V6.1 and later, the routine CVT$CONVERT_FLOAT is documented cG in the LIB$ Run-Time Library Reference Manual, and can perform floatingrG point conversions between any two of the following floating datatypes: sJ VAX (F,D,G,H), little-endian IEEE (single, double, quad), big-endian IEEE 5 (single, double, quad), CRAY and IBM System\370, etc.h  F DEC Fortran (all platforms) has a feature which will perform automaticK conversion of unformatted data during input or output.  See the DEC FortranMA documentation for information on "non-native data in I/O" and theO  CONVERT= OPEN statement keyword.  B There are floating-point conversion source code packages available for various platforms.  4 For further floating-point related information, see:  9   http://www.hhs.dk/anonymous/pub/vms/collection/ieee.zip     < ------------------------------------------------------------= PROG9.  How do I get the argument count in a Fortran routine?U  E On VAX, many programmers would use a MACRO routine which accessed the'E AP register of the caller to get the address of the argument list anduF hence the argument count.  This was not guaranteed to work on VAX, butH usually did.  However, it doesn't work at all on OpenVMS Alpha, as thereH is no AP register.  On Alpha systems, you must use a language's built-inD function to retrieve the argument count, if any.  In Fortran this isA IARGCOUNT, which is also available in DEC Fortran on OpenVMS VAX.f  G Note that omitting arguments to Fortran routines is non-standard and istG unsupported.  It will work in many cases - read the DEC Fortran releasef! notes for additional information.   < ------------------------------------------------------------? PROG10. How do I get a unique system ID for licensing purposes?i  G Many software developers desire to use a unique hardware ID to "lock" asF given copy of their product to a specific system.  Most VAX and Alpha G systems do not have a unique hardware-set "system ID" that can be used rD for this purpose.  Compaq does not use hardware IDs in its licensingG methods and many users consider a hardware-based licensing scheme to ber9 a negative attribute when considering software purchases.a  J Compaq OpenVMS uses a software-based system called the License Management H Facility (LMF).  This provides for software keys (Product Authorization G Keys or PAKS) which support capacity and user-based license checking.  r@ Compaq offers an LMF PAK Generator to CSA members -- see ALPHA4.  J However, if a hardware-based method is required, the most common method isF based on an Ethernet adaptor hardware address.  Sample source code for" implementing this is available at:  '   http://www.openvms.compaq.com/wizard/9  < ------------------------------------------------------------? PROG11. What is an executable, shareable, system or UWSS image?   A    Executable code in OpenVMS typically resides in an image -- annB    image is a file -- the file extension is typically .EXE -- thatA    contains this code.  Common types of images include executablee@    images, shareable images, system images, and protected (UWSS)
    images.  @    Executable images are programs that can be directly executed.A       These images can grant enhanced privileges, with an INSTALLi@       of the image with /PRIVILEGE, or can grant enhanced accessA       with the specification of a subsystem identifier on the ACLe        associated with the image.  B    Shareable images contain code executed indirectly, these images>        are referenced from executable images and/or from other=        shareable images.  These images can not grant enhancedT?        privileges, even with the use of INSTALL with /PRIVILEGEi@        or a subsystem identifier.  These shareable images can beA        dynamically activated (a LINK that occurs at run-time) viaT@        the LIB$FIND_IMAGE_SYMBOL run-time library (RTL) routine.=        (See `protected images' for information on `privilegedn        shareable images'.)  A    System images are intended to run directly on the VAX or Alpha >        hardware -- these are normally used for the kernel code+        that comprises an operating system.    F    Protected images -- also refered to as User-Written System ServicesC        (UWSS), or as privileged shareable images -- are similiar in A        some ways to a standard shareable images, but these imagesiA        include a `change mode' handler, and execute in an `inner'kA        processor mode (privileged mode; executive or kernel), and C        code executing in inner modes has implicit SETPRV privilege.3B        Must be INSTALLed with /PROTECT.  Note that inner-mode code?        has restrictions around calling library routines, arounde?        calling various system services, and around calling coden6        located in other protected or shareable images.  A    Loadable images and device drivers are images that can be usedt>    to add code into the OpenVMS kernel.  Pseudo-device driversA    are a particularly convenient way to add executable code, witht>    associated driver-defined data structures, into the kernel.E    The pseudo-device driver includes the UCB and DDB data structures,s?    and a calling interface with support for both privileged andr?    unprivileged access to the driver code via sys$qio[w] calls.   >    A cookbook approach to creating OpenVMS shareable images is1    available at the (admittedly overly long) URL:I  *      http://www.openvms.compaq.com/wizard/   					[Stephen Hoffman]  < ------------------------------------------------------------/ PROG12. How do I do a file copy from a program?a  M There are several options available for copying files from within a program. LD Obvious choices include using lib$spawn(), system(), sys$sndjbc() orM sys$creprc() to invoke a DCL COPY command.  Other common alternatives includehJ using the callable convert routines and the BACKUP application programming interface (V7.1 and later).O   					[Stephen Hoffman]  < ------------------------------------------------------------ PROG13.  What is a descriptor?  K A descriptor is a data structure that describes a string or an array.  EachrI descriptor contains information that describes the type of the data beingeG referenced, the size of the data, and the address of the data.  It also I includes a description of the storage used for the data, typically staticq2 or dynamic.   Descriptors are passed by reference.  G The following are examples of creating and using descriptors in C, witheL the use of the angle brackets normally expected by the C include statements * deliberately altered in deference to HTML:       #include {descrip.h}     #include {lib$routines.h}      #include {stsdef.h}-     int RetStat;     char TxtBuf[TXTSIZ] %     struct dsc$descriptor StaticDsc =R0       { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL };#     struct dsc$descriptor DynDsc = y0       { 0, DSC$K_DTYPE_T, DSC$K_CLASS_D, NULL };     int DynDscLen = 255;0     $DESCRIPTOR( ConstDsc, "This is a string" );  /     /* finish setting up a static descriptor */a)     StaticDsc.dsc$w_length      = TXTSIZ;V2     StaticDsc.dsc$a_pointer     = (void *) TxtBuf;  0     /* finish setting up a dynamic descriptor */2     RetStat = lib$sget1_dd( &DynDscLen, &DynDsc );*     if ( !$VMS_STATUS_SUCCESS( RetStat ) )       return RetStat;l  %     /* release the dynamic storage */a'     RetStat = lib$sfree1_dd( &DynDsc );T(     if (!$VMS_STATUS_SUCCESS( RetStat ))       return RetStat;   G Static descriptors reference storage entirely under application programaJ control, and the contents of the descriptor data structure can be modifiedE as required (by the application).  OpenVMS routines do not modify the H contents of a static descriptor, nor do they alter the address or lengthI values stored in the static descriptor.  (The term "static" refers to themH descriptor data structure, and not necessarily to the storage referenced by the descriptor.)/  G Dynamic descriptors reference storage under the control of the run-timewH library, and the contents of a dynamic descriptor data structure -- onceE initialized -- can only be modified under control of run-time librarycF routines.  The dynamic storage referenced by the dynamic descriptor isC allocated and maintained by the run-time library routines.  Various1H OpenVMS routines do alter the contents of the descriptor data structure,K changing the value for the amount and the address of the storage associated-H with the dynamic descriptor, as required.  Routines can obviously accessC and alter the contents of the storage referenced by the descriptor.t  I OpenVMS languages that include support for strings or arrays are expected I to use descriptors for the particular structure.  Most OpenVMS languages,tJ such as Fortran and BASIC, use descriptors entirely transparently.  Some, H like DEC C, require the programmer to explicitly create and maintain the descriptor.   K For further information on string descriptors, see the _OpenVMS Programming 8 Concepts_ manual, part of the OpenVMS documentation set.   					[Stephen Hoffman]  C Fortran defaults to passing integers by reference and characters by D descriptor.  The following sites discuss mixing Fortran and C source code in the same application:d  =   http://www.hhs.dk/anonymous/pub/vms/misc/FORTRAN_C_CALL.COMc2   ftp://ftp.hhs.dk/pub/vms/misc/FORTRAN_C_CALL.COM6                                         [Arne Vajhoej]  < ------------------------------------------------------------, PROG14.  How many bytes are in a disk block?  G A disk block is the minimum unit of disk storage allocation in OpenVMS.O  B Under OpenVMS VAX and OpenVMS Alpha, the disk volume block size is1 consistent, with each block containing 512 bytes.   D The minimum disk allocation granularity actually permissible (in theI ODS-2 and ODS-5 volume structures commonly used on OpenVMS) is determined E on a per-volume basis, and is typically based on a combination of the-G total number blocks on the disk volume and the total size of the volumedJ storage bitmap.  The allocation granularity is known as the volume clusterG factor -- the cluster factor is the number of blocks in a disk cluster,iB and it is the smallest number of blocks that can be allocated on a particular disk volume.r  B Prior to OpenVMS V7.2, the  maximum permissible size of the bitmapC requires larger cluster factors as volume sizes increase.  StartingcD with V7.2, the bitmap can be larger, and cluster factors as small as one block can be used.  B The number of bytes in a file can be determined by multiplying theD number of blocks allocated for the file times the number of bytes inA a block.  For sequential files (only), the FFB (XAB$W_FFB, in thetC File Header XAB) value can be used to find out how much of the lastt? (XAB$L_EBK) block is used.  FFB and EBK are meaningful only fore@ sequential files, and only in a limited context -- partial blockF allocations are not permitted.  For other file formats, the EOF marker is not meaningful.  C Disk allocations always occur only in units of the cluster factors,rD which can be from one block up to (potentially) clusters of eighteen7 blocks or more, depending on the volume cluster factor.o  H OpenVMS assumes that the device driver and the underlying storage deviceE will present the file system with addressable units of storage of 512oE bytes in size, or the appearance of same.  Various third-party CD-ROMsF devices, for instance, support only 2048 byte blocks, and such devices: are incompatible with the standard OpenVMS device drivers.  B To determine the number of bytes required for a file from DCL, oneB option uses the f$file_attributes item EOF, multiplied by the size@ of a block in bytes (512).  This does not account for the unusedB space in the last block of a sequential file, but it also does not8 have to differentiate sequential files from other files.   					[Stephen Hoffman]  < ------------------------------------------------------------, PROG15. How many bytes are in a memory page?  B A memory page is the minimum unit of memory allocation in OpenVMS.C With OpenVMS VAX, the memory page size matches the disk block size:y it is always 512 bytes.N  F With OpenVMS Alpha, the memory page size is variable, and it can rangeE from 8192 bytes (8 kilobytes) up to 64 kilobytes.  The current systemcF page size can be determined using the sys$getsyi or f$getsyi PAGE_SIZEE item.  Programs with hardcoded constants for the memory page size (oryA page alignment) should always assume a page size of 64 kilobytes.i  D On OpenVMS Alpha, a 512 byte area of memory -- equivilent in size to9 an OpenVMS VAX memory page -- is refered to as a pagelet.    					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG16. How do I create a process under another username?e  G Many server processes can operate within the context of the target user-F using privileges, using calls such as sys$chkpro and (more commonly inH this context) sys$check_access as needed to determine if access would beC permitted for the specified user within the current security model.t  H With OpenVMS V6.2 and later, the persona system services (SYS$PERSONA_*)J can be used to assume the persona of the specified user -- these allow theF server to operate as the specified user, in a controlled fashion.  TheG persona services can be used as a "wrapper" around a sys$creprc processcF creation call, as well -- this will create a seperate process entirely under the assumed persona.  E Information on the persona system services is included in the OpenVMSeI V6.2 new features documentation, and in the OpenVMS V7.1 and later systemiI services documentation.  These system services exist and are supported ina  OpenVMS V6.2 and later releases.  I Typical mechanisms for creating a process under another username include:   =     o personna services around a sys$creprc call.  See above.a>     o via DECnet task-to-task, using explicit specification of5       username and password, or using a DECnet proxy.n<       This creates a network-mode job under the target user.A       The network-mode job might do little more than a RUN/DETACHo<       of an image passed in via task-to-task -- task-to-taskB       communications are fully available using strictly DCL-to-DCL=       processing, or using a compiled language and DCL, etc.)oC     o SUBMIT/USER, or the username argument on the sys$sndjbc call.hA       This creates a batch-mode job under the specified username. ?       The batch-mode job might do little more than a RUN/DETACHe,       of an image passed in via a parameter..     o the UIC argument on the sys$creprc call.B       This mimics the UIC of the target user, and is certainly not+       the prefered mechanism for this task.T     o Via pseudo-terminals...E  J There are likely a few other mechanisms around...  There are various toolsG available from DECUS and other sources that allow various forms of userMJ impersonation, as well.  These tools will require version-dependent kernelF code and enhanced privileges for some of (or all of) their operations.   					[Stephen Hoffman]  < ------------------------------------------------------------E PROG17.  Why do lib$spawn, lib$set_symbol fail in detached processes?e  F The processing within run-time library (RTL) calls such as lib$attach,B lib$disable_ctrl, lib$do_command, lib$enable_ctrl, lib$get_symbol,C lib$run_program, lib$set_symbol, lib$set_logical, and lib$spawn, is H dependent on and requires the presence of a command language interpreterH (CLI), such as DCL.  Without a CLI present in the current process, theseI calls will fail with a "NOCLI, no CLI present to perform function" error.   7 Detached processes typically do not have a CLI present.,  H In place of lib$spawn, sys$creprc can often be used.  The context of theF parent process (symbols and logical names) will not be propogated intoC the subprocess when sys$creprc is used, though when there is no CLIe: present in the process this (lack of) propogation is moot.  I To create a detached process with a CLI, you must specify LOGINOUT as the G target image as discussed elsewhere in the FAQ, or only use these callsmH (and any other calls requiring a CLI) from images that are running in an0 "interactive", "batch", or "other" mode process.   					[Stephen Hoffman]  < ------------------------------------------------------------J PROG18.  Where can I obtain Bliss, and the libraries and supporting files?  < The Bliss language compilers and documentation are available& on the OpenVMS Freeware distributions.  A Bliss language source code that contains the following statement:l  $   LIBRARY 'SYS$LIBRARY:STARLET.L32';  ? or similar requires the presence of the Bliss libraries.  TheserB libraries are created on the target system using the Bliss require8 files, and are built using the following Bliss commands:  8   STARLET.L32 contains the public interfaces to OpenVMS:  5     $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L32 -d         SYS$LIBRARY:STARLET.REQ   E   LIB.L32 contains both the public and private interfaces to OpenVMS:t  1     $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 - 3         SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQ-  4   The equivilent files for Bliss64 are created with:  5     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]LIB.L64 -e3         SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64t9     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]STARLET.L64 -c         SYS$LIBRARY:STARLET.R64o  D Some Bliss code may also require the OpenVMS VAX architecture flags.B The following is the equivilent of the Alpha ARCH_DEFS.BLI module:     !o9   ! This is the OpenVMS VAX version of ARCH_DEFS.BLI, anda<   ! contains the architectural definitions for conditionally;   ! compiling OpenVMS Bliss sources for use on VAX systems.    !i   MACRO VAXPAGE = 1%;    MACRO BIGPAGE = 0%;d  =   MACRO VAX =                     ! = 1 if compiled BLISS/VAX A           %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAX-  <   MACRO EVAX =                    ! = 1 if compiled BLISS/E*   !t@   ! A more appropriate definition can only be used with versions=   ! of the Bliss compilers that understand the 32E/64E flags.oG   !       %BLISS(BLISS32E) OR %BLISS(BLISS64E)%; ! = 0 if compiled /VAXo8           NOT %BLISS(BLISS32V)%;  ! = 0 if compiled /VAX     MACRO ADDRESSBITS =CE           %BPADDR%;               ! = 32 or 64 based on compiler useds       					[Stephen Hoffman]  < ------------------------------------------------------------0 PROG19. How can I open a file for shared access?  9   When creating a file, it is often useful to allow other 8   applications and utilities -- such as TYPE -- to share;   read access to the file.  This permits you to examine theh'   contents of a log file, for instance.r  8   A C source example that demonstrates how to do this is7   available in topic 2867 in the OpenVMS Ask The Wizarde   area:t  )     http://www.openvms.compaq.com/wizard/c  ;   Depending on the environment, you may need to use C callso;   such as fsync and fflush, and -- in specific cases -- the-   setvbuf(_IONBF) call.-   					[Stephen Hoffman]  < ------------------------------------------------------------> PROG20. How can I have common sources for messages, constants?  B   Use the GNM tools on the OpenVMS Freeware to have common sourcesB   for MSG (message) files and SDML (Document) documentation files.A   Use the DOCUMENT command to convert the SDML documentation intoE?   the necessary formats (Text, Postscript, HTML, etc).  Use the C   MESSAGE/SDL tool (latent in OpenVMS) to create an SDL file based  D   on the messages.  Then use the SDL tool (available on the OpenVMS G   Freeware) to convert the SDL file into language-specific definitions.dE   (There is also a converter around to convert SDL into SDML, if you yF   want to get pictures of the data structures for your documentation.)   [End of Part 3/5]b  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 29 Dec 2000 20:32:59 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/5a6 Message-ID: <92isdr$f4j$4@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part4t Posting-Frequency: monthly Last-modified: 29 Dec 2000 Version: VMS-FAQ-4.TXT(5)s    9 This is the OpenVMS Frequently Asked Questions Part 4/5. e@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------F DECW1.  How do I let someone else display something on my workstation?  M On a workstation, you go into "Customize" menu of the session manager utility @ and select "Security".  When the pop-up box appears, you can putK node/user/tranport to allow who can launch an application to the display on  that workstation.w<                                              [Mike Raspuzzi]  M > Yah, but this doesn't seem to work with non-VMS systems.  What do I put in cI > for the transport?  I tried "TCPIP" just for kicks, but it didn't work.e  &         You need a checklist of sorts:  D       1) Make sure  that  you've  specified  the X-windows "display"D          correctly  on  the remote side.  For DECNET it's  somethingD          like NODE::0.0, for TCP/IP it's Node.Domain:0.0, etc.  On aA          unix system, define the DISPLAY environment variable so:a  & 	    # setenv DISPLAY myvax.domain:0.0  D       2) If you've verified 1) and things still aren't working, makeD          sure the Security settings on  the  VMS side will allow theD          connection:  Pull  down the "Options" menu in  the  SessionD          Manager, select "Security..."  near  the  bottom.   If  youD          don't  find  your  host  (and  username) listed on the leftD          under "Authorized Users", go to the  right side of the menuD          and   fill   in  the  three  fields,  "Node",   "Username",D          "Transport".  Then click on the Add botton, then the  ApplyD          and  OK  buttons  to  add  the  new  host  to  the security          database.  @           a) There are  various  transports: LOCAL, DECNET, LAT,@              TCPIP,  etc.   Select  the one appropriate  to  the<              client machine's connection to the VMS machine.  9 	  b) If the connection is DECNET, do *NOT* add :: to thec              node name!i  @           c) If the connection is TCPIP, "Username" _must_ be an@              asterisk (*) because the  TCP/IP protocol used does-              not provide the remote username.s  @           d) If the connection is TCPIP, it's best to use a full@              domain name, e.g.,  Node.Subd.Domain.  However, you@              _may_  have  to use the IP address  itself,  rather@              than  the  domain  name  (EWS  requires  this).   I@              generally  add two entries for each TPCIP host, the@              first using the  domain  name,  the  second  the IP              address.   @           e) There are a  various  3rd  party vendors who supply@              TCP/IP  packages for VMS, including but not limited@              to  TGV  (Multinet)  and  Wollongong  (Pathway  ?).@              Multinet  (and  DEC's  own  UCX) call the transport@              "TCPIP", Wollongong, at least in some incarnations,<              uses "WINTCP".  You need to use the appropriate@              vendor's package transport name  in the "Transport"              field.   D       3) If things _still_  aren't  working, make sure the transportD          you  want  has  been activated for DECwindows.  This  is  aD          system manager job, but you can do the ground work yourself8          before bothering the sysmgr.  Do the following:  4 	    $ DIR SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM  &          If that file exists, then do:  9 	    $ SEARCH SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM -e(             $_    DECW$SERVER_TRANSPORTS  '          You sould find something like:s  9 	    $ decw$server_transports == "DECNET,LOCAL,LAT,TCPIP"e  D          If the transport you want,  e.g., TCPIP, isn't listed, haveD          your  system  manager  make  the  appropriate  changes  andD          restart DECwindows.  If the file doesn't exist, the  sysmgrD          will  have  to  create  it  by  copying  the  correspondingD          .TEMPLATE file  to  .COM  and  uncommenting  the  line that(          defines decw$server_transports.  @           a) If you're wanting  to  use  TCP/IP to connect, make@              sure  TCP/IP is available on the VMS host.   TCP/IP@              is _not_ native to VMS.  You  need  to  be  runningB              either Compaq's TCP/IP or a 3rd party vendor's TCP/IP@              product.   If  you're  not,  none of the above will              help.% 				    [Fairfield@Slac.Stanford.Edu]   K There is a log file created in SYS$MANAGER which tells you which transportsrL are loaded, and also tell you what connect attempts were rejected, including: showing what the presented credentials were.  This file isN SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number ifK you have multiple servers on the workstation.  I have found this file to be I very useful for tracking down what needs to be put in the Session Managert Security entries.u 				    [rabinowitz@bear.com]   < ------------------------------------------------------------9 DECW2.  How do I create a display on another workstation?m  @ $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node  ) for LAT the command might look like this:C  6 $ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=REMOTE_NODE   for DECnet:   2 $ SET DISPLAY /CREATE /TRANSPORT=DECNET /NODE=NODE  
 for TCP/IP  9 $ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=128.12.4.122y  D Note that LAT is typically used for X terminals but can be used fromI OpenVMS to OpenVMS systems on OpenVMS Alpha V6.1 (if you have setup the XsK server to allow the LAT transport - check the docs).  LAT will be supported D on OpenVMS VAX as a transport for DECwindows in a future OpenVMS VAX release." 					[raspuzzi@mrlat.enet.dec.com]  K There is a log file created in SYS$MANAGER which tells you which transportsaL are loaded, and also tell you what connect attempts were rejected, including: showing what the presented credentials were.  This file isN SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number ifK you have multiple servers on the workstation.  I have found this file to bebI very useful for tracking down what needs to be put in the Session Managera Security entries.i=                                         [rabinowitz@bear.com]e  < ------------------------------------------------------------F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?  H Use the undocumented SHOW DISPLAY/SYMBOL, and then reference the symbolsC DECW$DISPLAY_NODE,  DECW$DISPLAY_SCREEN, DECW$DISPLAY_SERVER and/orl DECW$DISPLAY_TRANSPORT.A" 					[Fairfield@Slac.Stanford.Edu]  E An example of calling the underlying (and also undocumented) sys$qio u? programming interface for the WSDRIVER (WSAn:) is available at:   I   http://www.openvms.compaq.com/freeware/srh_examples/DECUS_UNDOC_CLINIC/o  < ------------------------------------------------------------0 DECW4.  How do I get a log of a DECterm session?  L If you are working from a Decterm, you can use the AutoPrint feature. ChooseD the "Printer..." menu item from the "Options" menu, set the printingH destination to the name of the file you want, and set "Auto Print Mode". You are now free to continue.d  M It should be noted that ALL the characters and escape sequences are captured,rO but if you display the log file on a DECterm you will get EXACTLY what you had.n  					[fenster@star.enet.dec.com]  < ------------------------------------------------------------E DECW5.  Problem - the DELETE key deletes forward instead of backward!a  N This has to do with Motif's virtual bindings.  When a Motif application startsD up, it looks at the vendor string returned in the display connectionL information and attempts to match the string to a table of virtual bindings.  N You can override the default bindings in your decw$xdefaults.dat file. Here is9 the entry you would make to get the default VMS bindings.       *defaultVirtualBindings:\i  osfCancel	:		<Key>F11	\n\  osfLeft	:		<Key>Left	\n\h  osfUp		:		<Key>Up		\n\s  osfRight	:		<Key>Right	\n\   osfDown	:		<Key>Down	\n\O   osfEndLine	:Alt		<Key>Right	\n\!  osfBeginLine	:Alt		<Key>Left	\n\m  osfPageUp	:		<Key>Prior	\n\  osfPageDown	:		<Key>Next	\n\s"  osfDelete	:Shift		<Key>Delete	\n\  osfUndo	:Alt		<Key>Delete	\n\   osfBackSpace	:		<Key>Delete	\n\   osfAddMode	:Shift		<Key>F8		\n\  osfHelp	:		<Key>Help	\n\t  osfMenu	:		<Key>F4		\n\  osfMenuBar	:		<Key>F10	\n\   osfSelect	:		<Key>Select	\n\e!  osfActivate	:		<Key>KP_Enter	\n\o!  osfCopy	:Shift		<Key>DRemove	\n\r  osfCut		:		<Key>DRemove	\n\  osfPaste	:		<Key>Insert  	 To merge:-    	$ xrdb :== $decw$utils:xrdb.exe( 	$ xrdb -nocpp -merge decw$xdefaults.dat 					[Fred Kleinsorge]  < ------------------------------------------------------------- DECW6.  Why is DECwindows Motif not starting?u  F First check to see if there is a graphics device, usually a G* device.E (eg: On a DEC 2000 model 300, use the command SHOW DEVICE GQ)  If your do not find a graphics device:  D a) OpenVMS has failed to find the appropriate IRQ information for anJ    EISA graphics card (on the DEC 2000 series) such as the Compaq QVision,J    and did not autoconfigure it.  Run the correct ECU (for Tru64 UNIX and F    OpenVMS) and reboot.  This is necessary only on EISA-based systems.  I b) You have an EISA-based system (such as the DEC 2000 model 300) and do yI    not have a Compaq QVision video card.  This EISA graphics card should iF    have Compaq printed on it, and identifies itself as a CPQ3011 or a F    CPQ3111.  If it is not one of these two EISA devices, then OpenVMS D    does not support it.  (There are no other supported EISA graphicsI    controllers, and EISA graphics are normally used with DECwindows only  #    on the DEC 2000 series systems.)s  C c) You have a PCI-based system and do not have a supported graphicsi>    controller -- examples of supported controllers include the        PowerStorm 3D30      PowerStorm 4D20      PowerStorm 300t      PowerStorm 350w      ELSA GLoria Synergy  D    See MGMT24 for information on some of these graphics controllers.  C d) You have booted the system minimally, or have otherwise disabledl(    the device autoconfiguration process.  ) If there is a G* graphics device present:M  I a) There may have been a severe error in the DECwindows startup. Type thesI    contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any information onm    errors starting the server.  I b) The system parameter WINDOW_SYSTEM is not set to 1.  This is a common oD    way for system managers to disable the DECwindows server startup.  E    If you really do not want a workstation system to bootstrap as and I    to represent itself as a workstation to DECwindows, add the following .     definition to SYLOGICALS.COM:  6      $ DEFINE/SYSTEM/EXEC DECW$IGNORE_WORKSTATION TRUE  E c) You may not have a valid Motif license.    To check for the Motif d    license, type the commands:  "      $ LICENSE LIST DW-MOTIF/FULL %      $ LICENSE LIST NET-APP-SUP*/FULL   F    and examine the information displayed.  Make sure that one of these)    licenses is present, valid and active.a   Also see DECW14  					[Kleinsorge, Hoffman]  < ------------------------------------------------------------ DECW7 relocate to SUPP7c  < ------------------------------------------------------------ DECW8 relocated to SUPP8  < ------------------------------------------------------------3 DECW9.  How do I set the title on a DECterm window?t  0 If you are creating a new DECterm window, check ) HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES.o  H If you want to change the title of an existing window, use the followingJ control sequences, where <esc> is the ANSI escape code, value decimal 27, - and <text label> is what you want to display:   : To set the DECterm title, send <esc>]21;<text label><esc>\: To set the icon label, send    <esc>]2L;<text label><esc>\  ? To set both the DECterm title and icon to the full device name:L   $  esc[0,7] = 27E $  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE")l8 $  write sys$output esc+ "]21;" + fulldevnam + esc + "\"8 $  write sys$output esc+ "]2L;" + fulldevnam + esc + "\"  F You can also change the title and the icon using the Options-Window... menu.-   Also see MISC2, DCL12.  < ------------------------------------------------------------B DECW10. How do I customize DECwindows, including the login screen?  L To customize various DECwindows Motif characteristics including the defaultsL used by the SET DISPLAY command, the DECwindows login screen background logoG used (the default is the DIGITAL or Compaq logo), various keymaps, the sM FileView defaults, session manager defaults, the DECwindows login processing,aL DECwindows log file processing, and various other DECwindows attributes, see the example file:t  .   SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE  C This example template file is typically copied over to the filenameiM SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_APPS_SETUP.COM and then modified to meetS site-specific requirements.   M Additionally, various X tools such as xsetroot, bitmap and xrdb -- some theserG can be useful in customizing the appearance of an application or of the]A DECwindows Motif display -- are provided in the DECW$UTILS: area.   M When using DECwindows V1.2-4 and later on OpenVMS Alpha, the default desktop RG is the Common Desktop Environment (CDE).  You can select your prefered  I desktop (CDE or DECwindows Motif) when logging in, or you can change the  = default to the DECwindows Motif desktop using the DCL symbol nK decw$start_new_desktop in the DECwindows private application setup command nI procedure.  See SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE for further %7 details, and how to create DECW$PRIVATE_APPS_SETUP.COM.   G Note that with DECwindows CDE, the root window is no longer visible by  H default.  The root window is hidden behind the "backdrop" window of the E current CDE workspace.  To make the root window visible, use the CDE sE style manager selection "backdrop none", and use information such as E/ that in the OpenVMS FAQ to set the root window.I  E To add a new backdrop to the DECwindows CDE environment, the backdrop J must first be in or be converted into X11 pixmap format.  (This conversionF is often possible using tools such as xv.)  Then (if necessary) createH the default backdrop directory SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS].I Place the X11 pixmap file containing the desired image into the backdrops C directory, ensure that it has a filename extension of .PM.  (The xv-E default filename extension for the X11 pixmap file is .XPM, while CDEhF expects only to see files with .PM.)  Now invoke the CDE style managerF and select a new backdrop.  You will find your image will be placed at+ the end of the list of backdrops available.o  v 					[Stephen Hoffman]  < ------------------------------------------------------------4 DECW11. Why doesn't XtAppAddInput() work on OpenVMS?  J XtAppAddInput() does work on OpenVMS.  The MIT definition of the X Windows: call XtAppAddInput() includes platform-specific arguments.  J On platforms where C is the typically the primary programming language forE the platform, the file descriptor mask is one of the arguments to the  XtAppAddInput() call.t  I On OpenVMS, the platform-specific arguments to this call include an eventtI flag and an IOSB, as these are the traditional OpenVMS constructs used toSI synchronize the completion of asynchronous operations.  While it would besD easier to port non-OpenVMS C code that calls XtAppAddInput() over toH OpenVMS if the arguments included the C file descriptor, this would makeK the call unusable from other OpenVMS languages, and would make it extremelytA difficult to use OpenVMS features such as ASTs and sys$qio calls.t  K One restriction on the event flag: the event flag chosen must be from event-I flag cluster zero.  When using the traditional lib$get_ef and lib$free_efzG calls to allocate and deallocate event flags, you must first explicitly9H call lib$free_ef to free up some event flags in event flag cluster zero.K Please see the event flag documentation for specific details on these callsnJ and for specific event flags that can be freed in event flag cluster zero.  F Here is some example code that covers calling this routine on OpenVMS:       m->InputID = XtAppAddInput(Q         m->AppCtx,         m->InputEF,          m->InputIosb,x         the_callback, 1 );     if ( !((int) m->InputID ))	         {-         XtAppErrorMsg(             m->AppCtx,             "invalidDevice",             "XtAppAddInput",             "XtToolkitError", "             "Can't Access Device",             (String *) NULL,              (Cardinal *) NULL );         ...t 					[Stephen Hoffman]  < ------------------------------------------------------------B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?  @ Congratulations, you have just stumbled into "dead rodent" mode.< This DECwindows environment -- where the keyboard arrow keys@ move the mouse cursor and where the [SELECT], [PREV], and [NEXT]B keys emulate the three mouse buttons -- allows rudimentary system 2 operations when the mouse is among the casualties.  A To enter or exit the "dead rodent" mode. press: [CTRL][SHIFT][F3]   < ------------------------------------------------------------2 DECW13. Why does half my DECwindows display blank?  > This is likely a result of receiving an OPCOM or other console< message on a system that shares the system console with the ( DECwindows graphics workstation display.  ? You can toggle off the console display window using [CTRL/F2], e8 and you can enable a serial console per ALPHA7 or VAX10.  > Also see the console message window application available with@ recent DECwindows versions -- recent DECwindows versions (V1.2-3> and later) will enable this window by default.  For details on< this console message window, see the DECW$CONSOLE_SELECTION 7 option in SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE.w  > On older releases, you can disable output using the following:  *   SET TERMINAL/PERMANENT/NOBROADCAST OPA0:   DEFINE/USER SYS$COMMAND OPA0:e   REPLY/DISABLEp  * Also see VAX9 and MGMT22, as well as DCL4.  < ------------------------------------------------------------B DECW14. %DECW-W-NODEVICE, No graphics device found on this system?   To resolve the following error:r  :  %DECW-W-NODEVICE, No graphics device found on this systemA    -DECW-I-NODECW, DECwindows graphics drivers will not be loadede    > 1) Ensure that the SYSGEN parameter WINDOW_SYSTEM is set to 1:  #     $ MCR SYSGEN SHOW WINDOW_SYSTEMd  8    If it is not set to a value of 1, issue the commands:       $ MCR SYSGEN     SYSGEN> USE CURRENT      SYSGEN> SET WINDOW_SYSTEM 1      SYSGEN> WRITE ACTIVE     SYSGEN> WRITE CURRENT      SYSGEN> EXIT     $ REBOOT  E 2) Check the SYSMAN IO PREFIX LIST to ensure that the DECW$ prefix is I    included in the existing list.  If it is not, you will need to add it:h       $ MCR SYSMAN     SYSMAN> IO SHOW PREFIXK     SYSMAN> IO SET PREFIX=(DECW$,*)   * = list returned by the show command      SYSMAN> IO AUTO/LOG      SYSMAN> EXITH 3) Ensure that the image SYS$SHARE:DECW$ICBM.EXE is installed in memory.+    If it is not installed, then install it:e  +     $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBM   )     $ INSTALL REPLACE SYS$SHARE:DECW$ICBMn  #     $ EDIT SYS$MANAGER:SYCONFIG.COM   0       $! The following line was added to install-       $! support for the Mach64 Graphics Carde       $!+       $ INSTALL REPLACE SYS$SHARE:DECW$ICBMe
       $ ^Z       $ SHUTDOWN    REBOOT the system.f  E If the system still complains that NO GRAPHICS DEVICES COULD BE FOUNDS then:G    4)   o Boot the system as normal      o Login as "system"      o Create the file:A=          $ SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT (W:RE)_7      o Add the following string on the very first line:e           CLEAR_PFLAG = ISA_4BYTE      o Save the file      o Set the file protections       o Reboot the system  
      EXAMPLE:   9      $ create SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DATo        CLEAR_PFLAG = ISA_4BYTE	        ^Zi  M      $ SET FILE/PROTECTION=(W:RE) SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DATi
      $ REBOOT    Also see DECW6 					[Kleinsorge, Hoffman]  < ------------------------------------------------------------0 DECW15. How can I reset the warning bell volume?  A   With DECwindows CDE drivers and ECOs starting with ECOs for theaG   DECwindows keyboard driver SYS$IKBDRIVER.EXE in OpenVMS Alpha V7.1-2  I   and V7.2-1 and with the SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1 rG   and later, the DECwindows CDE controls will now correctly manage the  &   setting of the warning bell volume.   G   Unfortunately, the equivalent controls in the older DECwindows Motif RD   interface are not compatible and can no longer manage the warning    bell volume.  C   If you need to manage the volume with DECwindows Motif, consider .   using the following approach:S  #     $ @decw$utils:decw$define_utils      $ xset b 1 100 100  A   The numerics are the volume, pitch, and duration, respectively.o  G   Why?   When OpenVMS first started supporting the PC-style keyboards, aI   the X Windows Server and the keyboard driver interface did not support -A   the pitch and duration, and neither did DECwindows Motif.  The tG   DECwindows keyboard driver was accordingly changed to use the volume nE   from the keyclick setting (keyclick is not available in a PC-style hJ   keyboard) and the bell volume setting to control the pitch and duration.  E   DECwindows CDE does provide sliders for setting pitch and duration, G   so the keyboard driver and X Windows Server were modified to provide AI   all of the information, and now the DECwindows CDE sliders work.  This SF   change is unfortunately incompatible with the old scheme used on theF   pre-CDE desktops, and the volume controls are now incompatible with 7   the current keyboard drivers.  Hence the use of xset.V  < ------------------------------------------------------------4 DECW16. How can I alter the DECwindows CDE backdrop?  C To select a separate backdrop to be displayed on each screen using j DECwindows CDE:   # 1. Click on the Appliction Manager.w.    This is the drawer icon on the CDE toolbar. 2. Click on Desktop Toolsl= 3. Click on Set Default Screen and select the required screena 4. Click on the Style Manager.B    This is the one containing the mouse and ttt on the CDE toolbar 5. Now change the background.i  >                                              [Geoff Kingsmill]  < ------------------------------------------------------------8 DECW17. How can I enable the DECwindows TCP/IP Transport  E   To configure the TCP/IP transport for DECwindows, first ensure thatnH   a TCP/IP package is installed and configured.  Then set the DCL symbolE   DECW$SERVER_TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM]E   to the appropriate local value, based on the comments in that file.o  I   If you do not have a copy of SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM,pE   the use the following COPY command to create this file based on the    provided template file:-  9     COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE -o9          SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COMy    < ------------------------------------------------------------ MISC1 relocated to WIRES1   < ------------------------------------------------------------G MISC2.    Where can I find information on escape and control sequences?e  G Information on escape and control sequences can be found in the OpenVMSyC I/O User's Reference Manual, in the section on the terminal driver.dB This section includes details on the general format and content of these sequences.  C Specific details on the escape and control sequences supported by adA particular serial device are typically found in the documentationeA provided with the specific device.  Information on the sequences uF supported by DECwindows DECterm terminal emulator are included in the  DECwindows documentation.b  G Examples of common escape and control sequences -- those typically usedtH by the OpenVMS screen management package -- can be found in the OpenVMS $ system file SYS$SYSTEM:SMGTERMS.TXT.  H The following refers to the function keys on the VTxxx series terminals,I and compatibles.  In the following, {CSI} is decimal code 155 and can be AH replaced by the sequence "{ESC}[" (without the quotes) particularly for E seven-bit operations, SS3 is decimal code 143 and can be replaced by eC "{ESC}O" particularly for seven-bit operations.  Older VT1xx series\F terminals and any other terminals operating with seven-bit characters ? should not be sent eight-bit operators such as {CSI} and {SS3}.K  + PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}SnA KP0={SS3}p KP1={SS3}q KP2={SS3}r KP3={SS3}s KP4={SS3}t KP5={SS3}u\I KP6={SS3}v KP7={SS3}w KP8={SS3}x KP9={SS3}y KPCOMMA={SS3}l KPMINUS={SS3}meI KPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}D-H RTARROW={CSI}C FIND={CSI}1~ INSERT={CSI}2~ REMOVE={CSI}3~ SELECT={CSI}4~I PREV={CSI}5~ NEXT={CSI}6~ F6={CSI}17~ F7={CSI}18~ F8={CSI}19~ F9={CSI}20~e@ F10={CSI}21~ F11={CSI}23~ F12={CSI}24~ F13={CSI}25~ F14={CSI}26~M HELP={CSI}28~ DO={CSI}29~ F17={CSI}31~ F18={CSI}32~ F19={CSI}33~ F20={CSI}34~h  = An example of working with escape sequences (in DCL) follows:    $ esc5m = "*[5m" $ esc5m[0,8] = 27s $ esc0m = "*[0m" $ esc0m[0,8] = 27d2 $ write sys$output esc5m + "blinking text" + esc0m  H Documentation on an ANSI terminal relatively similar to the VT525 series is available at:  6   ftp://ftp.boundless.com/pub/text/adds/docs/260_prog/6   ftp://ftp.boundless.com/pub/text/adds/docs/260_user/  < Also see the various documentation and manuals available at:     http://www.vt100.net/Q  @ Information on the ReGIS graphics character set is available at:  <   http://www.cs.utk.edu/~shuford/terminal/dec_regis_news.txt   Also see DECW9, DCL12.  < ------------------------------------------------------------ MISC3 relocated to SUPP4  < ------------------------------------------------------------ MISC4 relocated to WIRES2   < ------------------------------------------------------------ MISC5 relocated to ALPHA5   < ------------------------------------------------------------E MISC6.    What does "failure on back translate address request" mean?e   The error message:  <   BCKTRNSFAIL, failure on the back translate address request  I indicates that the destination node is running DECnet-Plus, and that its cE naming service (DECnet-Plus DECdns, LOCAL node database, etc) cannot iE locate a name to associate with the source node's address.  In other RG words, the destination node cannot determine the node name for the nodes. that is the source of the incoming connection.  G Use the DECNET_REGISTER mechanism (on the destination node) to registereD or modify the name(s) and the address(es) of the source node.  Check* the namespace on the source node, as well.  B Typically, the nodes involved are using a LOCAL namespace, and theA node name and address settings are not coherent across all nodes.EC Also check to make sure that the node is entered into its own LOCALtC namespace.  This can be a problem elsewhere, however.  Very rarely,FD a cache corruption has been known to cause this error.  To flush the cache, use the command:   1 NCL> flush session control naming cache entry "*"   C Also check to see that you are using the latest ECO for DECnet-Plus-  for the version you are running.  - DECnet-Plus can use the following namespaces:-2   o DECdns: DECnet-Plus distributed name services.;   o LocalFile: a local file containing names and addresses.-/   o DNS/Bind: the IP distributed name services.o   o The UCX local host file.   					[Stephen Hoffman]  < ------------------------------------------------------------8 MISC7.    How to determine the network hardware address?  A   Most Alpha and VAX systems have a console command that displayshF   the network hardware address.  Many systems will also have a stickerD   identifying the address, either on the enclosure or on the network   controller itself.  C   The system console power-up messages on a number of VAX and Alpha B   systems will display the hardware address, particularly on those>   systems with an integrated Ethernet network adapter present.  E   If you cannot locate a sticker on the system, if the system powerupoD   message is unavailable or does not display the address, and if theB   system is at the console prompt, start with the console command:  
   >>> HELP  E   A console command similar to one of the following is typically usedo"   to display the hardware address:     >>> SHOW DEVICE    >>> SHOW ETHER   >>> SHOW CONFIGi  D   On the oldest VAX Q-bus systems, the following console command canD   be used to read the address directly off the (DELQA, DESQA, or the=   not-supported-in-V5.5-and-later DEQNA) Ethernet controller:f     >>> E/P/W/N:5 20001920  G   Look at the low byte of the six words displayed by the above command. E   (The oldest VAX Q-bus systems -- such as the KA630 processor moduleTD   used on the MicroVAX II and VAXstation II series -- lack a consoleD   HELP command, and these systems typically have the primary networkF   controller installed such that the hardware address value is located+   at the system physical address 20001920.)h  F   If the system is a VAX system, and another VAX system on the networkC   is configured to answer Maintenance and Operations Protocol (MOP)yF   bootstrap requests (via DECnet Phase IV, DECnet-Plus, or LANCP), the1   MOM$SYSTEM:READ_ADDR.EXE tool can be requested:R     >>> B/R5:100 ddcu    Bootfile: READ_ADDR   I   Where ddcu is the name of the Ethernet controller in the above command.,J   The primarly local DELQA, DESQA, and DEQNA Q-bus controllers are usuallyK   named XQA0.  An attempt to MOP download the READ_ADDR program will ensue,tI   and (if the download is successful) READ_ADDR will display the hardwaref
   address.  G   If the system is running, you can use DECnet or TCP/IP to display theh6   hardware address with one of the following commands.  B     $ MCR NCP SHOW KNOWN LINE CHARACTERISTICS    ! DECnet Phase IV  >     $ MCR NCL SHOW CSMA-CD STATION * ALL STATUS  ! DECnet-Plus  @     $ UCX SHOW INTERFACE/FULL    ! TCP/IP versions prior to V5.0  A     $ TCPIP SHOW INTERFACE/FULL  ! TCP/IP versions V5.0 and later   G   A program can be created to display the hardware address, reading thetF   necessary information from the network device drivers.  An example CF   program for reading the Ethernet hardware address (via sys$qio callsE   to the network device driver(s)) is available at the following URL:.  =     http://www.openvms.compaq.com/wizard/swdev/ethernVMS.html   E   To use the DECnet Phase IV configurator tool to watch for MOP SYSIDT%   activity on the local area network:t  B   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLED  E   Let the DECnet configurator run for at least 20 minutes. Then issue    the following commands:e  E   $ NCP SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txteC   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED-  E   The resulting file (named filename.txt) can now be searched for theuG   information of interest.  Most DECnet systems will generate MOP SYSIDpH   messages identifying items such as the controller hardware address andE   the controller type, and these messages are generated and multicast    roughly every ten minutes.  E   Information on the DECnet MOP SYSID messages and other parts of themF   maintenance protocols is included in the DECnet network architecture,   specifications referenced in section DOC9.  < ------------------------------------------------------------ MISC8 combined into SUPP4r  < ------------------------------------------------------------B MISC9.    Why can't I use PPP and RAS to connect to OpenVMS Alpha?  G   OpenVMS Alpha PPP does not presently support authentication, and the rE   Microsoft Windows NT option to disable authentication during a RAS sG   connection apparently doesn't currently work -- RAS connections will oG   require authentication -- and this will thus prevent RAS connections.i@                                                [Stephen Hoffman]  < ------------------------------------------------------------ MISC10 relocated to SUPP5.  < ------------------------------------------------------------@ MISC12.   Does DECprint (DCPS) work with the LRA0 parallel port?  = The parallel printing port LRA0: found on many OpenVMS Alpha  = systems is capable of some bidirectional communications, withp8 enough for basic operations with most parallel printers.  ? DECprint (DCPS) requires more than just the simple handshaking I> provided by the LRA0: port, therefore DCPS does not work with  the LRA0: port.v4                                      [Paul Anderson]  < ------------------------------------------------------------; MISC13.   How do I check for free space on a (BACKUP) tape?   > You cannot know for certain, though you can certainly estimate the remaining capacity.-  ? Tape media is different than disk media, as disks have a known r= and pre-determined fixed capacity.  Modern disks also appear n> logically perfect, based on bad block revectoring support and ; the extra blocks hidden within the disk structure for these  bad block replacements.t  @ The capacity of tape media is not nearly as pre-determined, and ; the capacity can vary across different tape media (slightly": different media lengths or different foil markers or other> variations, for instance) and even on the same media over time@ (as bad spots in the media arise).  Tapes can vary the amount of? recording media required, depending on the remaining length of a= the tape, the numbers of correctable and uncorrectable media oC errors that might occur, the numbers and sizes of the inter-record R> gaps and related tape structure overhead, the particular media@ error recovery chosen, the tape density, the efficiently of any > data compression in use, and the storage overhead required by ( BACKUP, tar, and other similar commands.  ? BACKUP using with the default settings results in approximatelyC@ 15% overhead, in terms of saveset size.  (eg: Assuming a 500 KB ' input, the total size would be 575 KB.)n     Assuming no compression:0    4 GB media / 575 KB saveset =  7294 savesets      Assuming 1:2 compression:P0    8 GB media / 575 KB saveset = 14588 savesets   C NB: There are no inter-record gaps on DAT tapes.  (When determining-B media capacity, you have to consider these with nine-track magtapeE media.  Not with DAT (DDS).  However, the block structure underneath  G the variable length record recording is based on a block size of circa iF 124 KB.  Further, writing doubles filemarks and such can cause a loss C of up to the underlying block size.  Thus even though there are no  A inter-record gaps on DAT, larger savesets are still usually best.C  E The compression algorithms used on various devices are generally not  F documented -- further, there is no way to calculate the effective dataF compression ratio, the tape mark overhead, and similar given just the E data to be stored on tape -- short of actually trying it, of course. e  C A typical compression ratio found with "everyday" data is somewhereM around 1:1.8 to 1:2.  D NB: OpenVMS often uses the term COMPACTION for compression control, - as in the qualifier /MEDIA_FORMAT=COMPACTION.SG                                           [Hoffman, Froehlin, Williams]t  < ------------------------------------------------------------* MISC14.   So what happened to sys$cmsuper?  ! There is no SYS$CMSUPR service.  .  A The typical wisdom for getting into supervisor access mode (from pA user mode) is to execute a routine in executive mode (via a call C> to SYS$CMEXEC and the appropriate privilege) and then issue a > SYS$DCLAST with the ASTADR parameter pointing to your routine > entry point and the ACMODE parameter specified as PSL$C_SUPER.  @ Alternatively, you can reset mode in the call stack return path = and unwind from executive or kernel out into supervisor mode.t:                                     [Brian Schenkenberger]  < ------------------------------------------------------------< MISC15.   How can I send radio pages from my OpenVMS system?  B There are third-party products available to send messages to radioA paging devices (pagers), communicating via various protocols suchY) as TAP (Telocator Alphanumeric Protocol).   C RamPage (Ergonomic Solutions) is one of the available packages that-A can generate and transmit messages to radio pagers.  Target Alerta= (Target Systems; formerly the DECalert product) is another.  v? Networking Dynamics Corp has a product called Pager Plus.  The rB System Watchdog package can also send pages.  The Process SoftwareE package PMDF can route specific email addresses to a paging service, t as well.  @ Many commercial paging services provide email contact addresses @ for their paging customers -- you can simply send email directly
 to the pager.w  ? See SOFT1 for information on the available catalog of products.n  < ------------------------------------------------------------ MISC16 relocated to WIRES3  < ------------------------------------------------------------< MISC17.   How do I reset the LAN (DECnet-Plus NCL) counters?   On recent OpenVMS releases:u  ;   LANCP> SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devnameu    < ------------------------------------------------------------6 MISC18.   What are the prefixes for the powers of ten?  $         Power   Prefix  Abbreviation         10^-18  atto    aP         10^-15  femto   fi         10^-12  pico    pl         10^-09  nano    nY         10^-06  micro             10^-03  milli   m5         10^-02  centi   cD         10^-01  deci    dh         10^+01  deca    da         10^+02  hecto   h,         10^+03  kilo    kA         10^+06  mega    Mn         10^+09  giga    Ge         10^+12  tera    Td         10^+15  peta    Pa         10^+18  exa     Eh    < ------------------------------------------------------------6 MISC19.   OpenVMS Cluster (SCS) over DECnet?  Over IP?  = The OpenVMS Cluster environment operates over various networkf6 protocols, but the core of clustering uses the System : Communications Services (SCS) protocols, and SCS-specific : network datagrams.  Direct (full) connectivity is assumed.  = An OpenVMS Cluster DOES NOT operate over DECnet, nor over IP.W  & No SCS protocol routers are available.  B Many folks have suggested operating SCS over DECnet or IP over theC years, but SCS is too far down in the layers, and any such project rB would entail a major or complete rewrite of SCS and of the DECnet B or IP drivers.  Further, the current DECnet and IP implementationsA have large tracts of code that operate at the application level, dD while SCS must operate in the rather more primitive contexts of the D system and particularly the bootstrap -- to get SCS to operate over E a DECnet or IP connection would require relocating major portions of  B the DECnet or IP stack into the kernel.  (And it is not clear thatC the result would even meet the bandwidth and latency expectations.)N  @ The usual approach for multi-site OpenVMS Cluster configurationsG involves FDDI, Memory Channel (MC2), or a point-to-point remote bridge,eD brouter, or switch.  The connection must be transparent, and it mustC operate at 10 megabits per second or better (Ethernet speed), with s> latency characteristics similar to that of Ethernet or better.< Various sites use FDDI, MC2, ATM, or point-to-point T3 link.    < ------------------------------------------------------------/ MISC20.   Correctly using license PAKs and LMF?l  @   If you have multiple LMF$LICENSE.LDB databases in your OpenVMS@   Cluster, then each and every PAK must be installed in each and@   every license database present in an OpenVMS Cluster.  Even ifA   you use /EXCLUDE or /INCLUDE, you need to have a consistent setaC   of PAKs registered across all licensing databases present in the     OpenVMS Cluster.  A   If your software license permits it, you can use the following o(   two commands to transfer license PAKs:       $ LICENSE COPY...s5     $ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,...   A   To display the particular license(s) required (such as when you =   receive a NOLICENSE error), use the following DCL sequence:-       $ SET PROCESS/PRIVILEGE=ALL-     $ REPLY/ENABLE7     $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE-  F   This logical name will cause all license failures to generate OPCOM F   messages, and this will hopefully show which license(s) you need -- C   there may well also be additional license failures displayed, as uH   various products can check for and can be enabled by multiple license ?   PAKs.  You will want to deassign this logical name when done.g  '   Some of the more common license PAKs:C  B   DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*B   DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*)   TCP/IP Services:   UCX, or NET-APP-SUP*e9   OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USERo   OpenVMS VAX:       VAX-VMS#   OpenVMS Galaxy:    OPENVMS-GALAXYy-   Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP*a-   Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*d  E   Various NET-APP-SUP (NAS) license packages are available, each withlD   differing collections of products authorized.  See the various NASD   Software Product Description (SPD) documents for specific details.  #     http://www.compaq.com/info/spd/   H   To determine which license PAK is failing (via a license check failure"   OPCOM message), use the command:  <     $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE TRUE  C   Realize that defining this logical name will cause license checksaF   that are otherwise hidden (unimplemented, latent, or part of a checkF   for any of a series of licenses) to become visible.  In other words,G   expect to see some spurious license check calls when you define this.d  < ------------------------------------------------------------D MISC21.   Third-party disk/tape/controllers/SCSI/widgets on OpenVMS?  I   A wide variety of third-party widgets -- SCSI and IDE disks and tapes, mC   graphics controllers, etc -- are available for various platforms.p  E   If you purchase third-party "generic" SCSI or IDE storage devices, 0E   you and your device vendor will be responsible for the testing and sG   the support of the devices.  I would tend to expect that Compaq will cD   address non-standards-compliance problems within OpenVMS (changes F   that will also not prevent operations with other supported devices, A   of course), but you and/or the device vendor and/or the device .F   manufacturer are responsible for finding and fixing problems in the ;   particular third-party device and or controller involved.r  D   In particular, realize that neither SCSI nor IDE is a particularlyB   standard interface, these interfaces tend to be a collection of C   optionally-implemented and standardized interface features.  You eD   should not and can not simply assume that all SCSI nor IDE storageD   devices are interchangeable.  If you want to try to use a generic B   SCSI device, use V6.2 or later, or (better) V7.1-2 or later.  If;   you wish to try to use IDE, use OpenVMS V7.1-2 or later. y  B   On older OpenVMS releases, see the disk capacity limits (FILE5).  C   With SCSI disks on older releases, ensure that you have the ARRE sB   and ARWE settings configured correctly (disabled).  (If not, you&   will see DRVERR fatal drive errors.)  E   Based on the displays of the (undocumented) SYS$ETC:SCSI_INFO tool;-1   this tool is present in OpenVMS V6.2 and later:-  E     Issuing 6-byte MODE SENSE QIOW to get current values for page 01hr*            Page Code ................. 01h@            Page Name ................. Read-Write Error Recovery*            Saveable .................. Yes)            Size ...................... 10t>            Hex Data .................. E6 08 50 00 00 00 08 00,                                        00 00  E     The E6 indicates that the AWRE and ARRE bits are set, and this iseE     not acceptable on OpenVMS versions prior to V6.2.  Further along s.     in the SCSI_INFO display, if you also see:  H     Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h*            Page Code ................. 01h@            Page Name ................. Read-Write Error Recovery*            Saveable .................. Yes)            Size ...................... 10o>            Hex Data .................. C0 08 50 00 00 00 08 00,                                        00 00  C     The C0 value means that the AWRE and ARRE values can be changedaC     on this particular SCSI device.  (This is not always the case.) E     Use RZDISK from the OpenVMS Freeware, and reset the E6 flag byte sE     to hexadecimal 26 (or whatever the remaining mask when you removet     bits C0) on page one.e  B   Each SCSI and IDE host contains non-trivial SCSI and IDE driver E   software, and each device contains equally non-trivial firmware -- iE   taken together with the mechanical and electronic components, this eB   software and firmware will determine whether or not a particular#   device will function as expected.-  E   Also note that various devices -- such as various SCSI CD-R devices-H   -- can implement and can require vendor-specific protocol extensions, C   and these extensions can require modifications to OpenVMS or the >B   addition of various utilities.  In various of these cases, theseE   devices perform functions that will require them to use SCSI or IDErF   commands that are (hopefully) architecturally-compatible SCSI or IDE2   command extensions.  (Also see UTIL1 and FILE7.)  A   In order for OpenVMS to officially support a particular device, G   integration and testing work is mandated.  There can be no certainty mH   that any particular device will operate as expected in any particular B   configuration without first performing this (non-trivial) work.   F   It is quite possible to find two devices -- both entirely compliant D   with applicable standards or interface documents -- that will not    interoperate.t  B   The same general statement holds for OpenVMS bootstrapping on anA   unsupported VAX or Alpha platform.  It might or might not work.eE   In particular, please see the OpenVMS Software Product Description -D   (SPD) for the list of platforms supported by OpenVMS.  OpenVMS is F   not supported on the Personal Workstation -a series, on the Digital E   Server series platforms, on the AlphaServer 2100 series 5/375 CPU,  D   on the Multia, and on a variety of other platforms.  (You might orC   might not see success booting OpenVMS on any of these platforms.)k 					[Stephen Hoffman]  < ------------------------------------------------------------C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?   A Details on many commercial OpenVMS products are available in the - catalog located at:-  ,   http://www.partner.compaq.com/www-catalog/     ----  C An OpenVMS Freeware CD-ROM is distributed with OpenVMS, and is alsotA available separately (QA-6KZAA-H8).  The contents of the OpenVMS  3 Freeware CD-ROM media are also available online at:E  /         http://www.openvms.compaq.com/freeware/l         ftp://ftp.montagar.com/ '         ftp://mvb.saic.com/freewarev40/c$         http://freeware.acornsw.com/  F and at various other sites.  The website also includes various updatesF and new packages that become available after the CD-ROM distributions  are created.  4 Submissions to the OpenVMS Freeware can be made via:  7         http://www.openvms.compaq.com/openvms/freeware/-  E To acquire the OpenVMS Freeware CD-ROM distribution, you can order an-C OpenVMS distribution from Compaq (the Freeware is included)(see thedH OpenVMS SPD for part numbers), or you can specifically order a Freeware + distribution from Compaq under part number:M  
   QA-6KZAA-H8f  D The Freeware CD-ROM set contains a large assortment of freeware, andH is a good starting point if looking for utilities.  Many of the packagesI listed below are also on the Freeware CD.  Some of the most oft-requestedlI OpenVMS tools on the Freeware CD include ZIP and UNZIP, GZIP, MMK (make),hG PINE, PERL, TAR, UUENCODE and UUDECODE.  Many other tools are availablew on the Freeware.  K The UUENCODE and UUDECODE tools and various other tools are also available nC as part of TCP/IP Services package.  (Use the DCL command procedureSI SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM available on V5.0 and later to set $D up the necessary DCL foreign command symbols used for these and for 1 various other tools provided by TCP/IP Services.)e     ----  J Compaq also has a separate area containing various OpenVMS software tools  located at:o  !   http://ftp.digital.com/pub/VMS/r  J This area is not consistently maintained, and these tools may (or may not H be) the most current versions of the tool.  Please check for more recent: versions before downloading and using any particular tool.     ----  ; Western Kentucky University (and madgoat) OpenVMS archives:S  ,   http://www2.wku.edu/fileserv/fileserv.html   http://www.madgoat.com/=;                                            [Hunter Goatley]}     ----  @ The FILESERV packages are also available via anonymous FTP from:     Via anonymous FTP from:-'     ftp.wku.edu, under [.VMS.FILESERV].}/     ftp.process.com, under [.WKU.VMS.FILESERV].X5     ftp.spc.edu, under [.MACRO32.SAVESETS] and [.MX].0>     ftp.vms.stacken.kth.se, under [.MIRRORS.WKU.VMS.FILESERV].1     ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].S     ftp.riken.go.jp03     ftp.vsm.com.au, under kits and kits/decwindows.n/     ftp.vsm.com.au, via the WWW instead of FTP.5  F or via e-mail from FILESERV@WKUVX1.WKU.EDU. Send the commands HELP and>    DIR ALL in the body of a mail message for more information.     ----  L If you get the packages via WWW or FTP, they're in ZIP format which requiresJ the UNZIP (note: this is not Gnu gunzip!) tool to unpack.  You can get ZIP# and UNZIP from the following areas:n  .   ftp://ftp.wku.edu/vms/unzip.exe        ! VAX0   ftp://ftp.wku.edu/vms/unzip.alpha_exe  ! Alpha*   ftp://ftp.wku.edu/vms/fileserv/UNZIP.ZIP/   http://www.decus.de:8080/www/vms/sw/zip.htmlx     http://www.djesys.com/zip.html"   http://www.djesys.com/unzip.html  E or you can request the FILESERV_TOOLS package from the e-mail server.-  D [Beware: The [000TOOLS...] pre-built versions of ZIP on the OpenVMS G Freeware V4 CD-ROM will erroneously return BILF errors on OpenVMS V7.2 oD and later.  Use of the source on the Freeware V4 to rebuild the ZIP I image(s), or acquiring a pre-built ZIP image from one of the above areas  H can avoid this.  The pre-built version of ZIP on the Freeware V4 kit is C older than the included ZIP sources, and it contains a latent bug.]l  H Another source of free software is the vmsnet.sources newsgroup (and theJ corresponding vmsnet.sources.d discussion group).  See the monthly postingG "vmsnet.sources archives" for a list of sites which archive submissionsr to vmsnet.sources.     ----  K Arne Vajhj runs an OpenVMS WWW page, with software and other pointers, at:n   http://www.levitte.org/~ava/     ----   Kermit is available at:f$   http://www.columbia.edu/kermit/ or   ftp://kermit.columbia.edu/     ----   ZMODEM is available at: !   ftp://ftp.cs.pdx.edu/pub/zmodemo9 See the FILES file in that directory for further details.dF Note that this freeware version of ZMODEM will interoperate only with 6 ZMODEM software that is licensed from Omen Technology. (Also on Freeware CD)h 				[Steve Lionel]     ----  G A good source of software for DEC boxes (and anything else pretty much)sC is the DECUS library. online catalogs are available as well as somee4 software via ftp.decus.org; there's a gopher server    gopher://gopher.decus.org/ an FTP server:   ftp://ftp.decus.org/ and a WWW server:P   http://www.decus.org/i  3 Some DECUS library CD-ROMs are available online at:a:     http://www.acornsw.com/www/acorn/cdrom-via-www.html or      gopher://gopher.acornsw.com/ 				[munroe@dmc.com]  H Phone for DECUS orders is 508-841-3502. Lots of good stuff from lots of 7 good folks, and copies on media (tapes, CDs) are cheap.A 				[Everhart@Arisia.gce.com]s     ----  J    MPJZ's Hyper-Software-List for OpenVMS is Martin P.J. Zinser's list of     additional software.  h.      http://axp616.gsi.de:8080/www/vms/sw.html     ----  (    Chris Higgins's VMS Software List II 6      http://csvax1.ucc.ie/www/vms_sw_list/sw_list.html     ----  G    DECUS SIG Tape collections are available on Mark Berryman's system, d      ftp://mvb.saic.com/     ----  M    David Jones's DECthreads-based HTTP_SERVER World-Wide Web server for VMS. g<      http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html 					    [Hunter Goatly]     ----  )    Secure Shell (SSH) Server for OpenVMS: 5      http://kcgl1.eng.ohio-state.edu/~JONESD/ssh/DOC/s  )    Secure Shell (SSH) Client for OpenVMS:d       http://www.free.lp.se/fish/  /    Information on OpenSSL (SSLeay) for OpenVMS: #      http://www.free.lp.se/openssl/o8                                             [Leo Demers]  D    Information on OpenSSL (SSLeay) and OSU Webserver interoperation:-      http://www.ourservers.net/openvms_ports/      ----  G DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4 built for UCX.  V1.2-4dB includes Spyglass Enhanced Mosaic, which supports many "Netscape" B enhancements.    Netscape Navigator is also available for OpenVMS.     ----  I A port of Mosaic 2.7-4 which supports UCX, Multinet and SOCKETSHR/NETLIB d is available from:    ftp://wvnvms.wvnet.edu/mosaic/     ----  ? Lynx (a character-cell World-Wide-Web reader) is available frome"   ftp://ftp2.cc.ukans.edu/pub/lynx 					    [Steve Lionel]x     ----  = Netscape Navigator and Mozilla web browsers are available at: ?   http://www.openvms.compaq.com/openvms/products/ips/index.html6   http://www.mozilla.org/3     ----  F PGP (Phil Zimmerman's "Pretty Good Privacy") is available from variousH distribution sites, including those listed in the PGP FAQ.   Information. on an OpenVMS download of PGP is available at:   http://www.pgpi.com/(   http://zone.pspt.fi/pgp/platforms/vms/)   http://www.yrl.co.uk/~phil/pds/pds.html-     ----  ? An archive of the CENA DECwindows, X Windows, and VMS software v- packages can be found at the following sites:i     http://decwarch.free.fr/2   http://www2.cenaath.cena.dgac.fr/ftp/decwindows/    ftp://ftp2.cnam.fr/decwindows/%   ftp://ftp.ctrl-c.liu.se/decwindows/ 2   ftp://ftp.vms.stacken.kth.se/mirrors/decwindows/)   http://www.multimania.com/pmoreau/decw/t  +   http://www2.cenaath.cena.dgac.fr/ftp/vms/    (See also Freeware CD) 					    [Patrick Moreau]p     ----  I ImageMagick is an X11 package for display and interactive manipulation ofnE images.  The package includes tools for image conversion, annotation,nI compositing, animation, and creating montages.  ImageMagick can read and eI write many of the more popular image formats (e.g. JPEG, TIFF, PNM, XPM, d Photo CD, etc.). e   http://www.imagemagick.org/v (Also on Freeware CD)t 					    [cristy@dupont.com]     ----   XV is available from:     ftp://ftp.cis.upenn.edu/pub/xv'   ftp://ftp.digital.com/pub/graphics/xv    http://www.sanface.com/ 8   ftp://www-pi.physics.uiowa.edu/~dyson/xv-3_10a-vms.zip     ----  I Many software packages are available for displaying various bitmap files nJ (.JPG, .GIF, .BMP, etc) on OpenVMS.  Xloadimage, Xli, Xv, ImageMagick are G the most common tools used under OpenVMS.  Various web browsers such asnH Mozilla (qv) can also display various file formats on OpenVMS.  You can 3 find some of these tools at the DECwindows Archive:t  3   http://www.multimania.com/pmoreau/decw/index.html,4   http://www.multimania.com/pmoreau/decw/images.html;                                            [Patrick Moreau]c     ----  - GHOSTSCRIPT and GHOSTVIEW are available from:L)   ftp://ftp.digital.com/pub/VMS/ghostview (   Also available on the Freeware CD-ROM.  3 Version 2.3 of GhostView-VMS is now available from:i+   ftp://iphthf.physik.uni-mainz.de/pub/vms/C* 					   [plass@dipmza.physik.uni-mainz.de]	 Also see: $   http://www.cs.wisc.edu/~ghost/gnu/     ----  @ XPDF, a viewer for PDF (Adobe Acrobat) files, is available from:   http://www.foolabs.com/xpdf/9                                             [Ki Suk Hahn]   <   Beware: the XPDF on OpenVMS Freeware V4 is somewhat dated.     ----    L A Java-based PDF viewer is available from Adobe, and is known to operate on  recent OpenVMS Alpha releases:   http://www.adobe.com/      ----  H Various OpenVMS-related tools -- both freeware and shareware -- such as ! txt2pdf -- are available from at:c   http://www.sanface.com/n     ----  F The MPEG library version 1.1 is available for OpenVMS VAX and Alpha at3   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readmea0   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip 					    [Patrick Moreau]b     ----  4 List of FTP Mirror Sites for the DECWINDOWS archive:  A AXP.PSL.KU.DK             (Multinet)  Mirror of CENA DECW archiveAA FTP.ET.TUDELFT.NL         (MadGoat)   Mirror of CENA DECW archivePA FTP2.CNAM.FR              (MadGoat)   Mirror of CENA DECW archiveP  I ftp.x.org (in /contrib/vms)  not really a mirror, but I try to put all myV new ports at this site.A     ----  5 List of HTTP Mirror Sites for the DECWINDOWS archive:G  ;   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.htmle  = Some X clients from the OpenVMS Freeware CDROM are located inN# [.DECWINDOWS.CDFREEWARE] directory.a 						[Patrick Moreau]     ----  H I have written and installed on INFO.CS.PUB.RO an 'Archie' clone for VMS7 software. Telnet to that machine, and login as VMSARCI.cM It contains now listings for over 30 ftp servers with >14 GB of VMS software.nH The most useful commands are LIST, which generates a list of scanned ftpG servers, and FIND <string>, whichs looks for a file containing "string"sI in the name; the search modes are only "substring" [default] and "exact",pL and regex search is not supported (so FIND EMACS will work, but FIND *EMACS*< or FIND *EMACS*.* will not). The search is case-insensitive.I Those of you that know other ftp servers with VMS software that I haven't-D found, please let me know. (The program that build the databases canI recursively scan whole servers- as FTP.WKU.EDU, or just some directories-- as NIC.SWITCH.CH /pub/vms)H Sorry, this service is VERY SLOW [by Western standards], because it runsJ on a quite-busy oldie-but-goodie VAXStation 3400 with 20Mb and a RF71, and; the Internet link is only 256 Kpbs (sometimes unavailable).i 						[stfp@roipb.cs.ipb.ro]     ----  9   The Levitte (extended :-) Family (and OpenVMS) website:n     http://www.levitte.org/h      http://www.levitte.org/~ava/     ---p  E   Robert's OpenVMS Hobbyist Systems, including OpenVMS public domain n   software and various ports:h       http://www.ourservers.net/  <                                           [Robert Alan Byer]   ----     CalTech Software Archives:?     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/AAA_CONTENTS.TXT      ----  *   DJE Systems Website (David J. Dachtera) '     http://www.djesys.com/freeware/vms/p     ----     Web servers:     Apache Webserver:eI       http://www.openvms.compaq.com/openvms/products/ips/apache/csws.htmle@       http://www.openvms.compaq.com/openvms/products/ips/apache/=       http://www.er6.eng.ohio-state.edu/~jonesd/apache/1_3_9/      OSU Webserverr?       http://www.er6.eng.ohio-state.edu/www/doc/serverinfo.htmlS#       http://www.kjsl.com/archives/t1       email list: VMS-WEB-daemon-Request@KJSL.COMe     Purveyor Webserver:R1       email list: listserv@cjis.ci.lincoln.ne.us a9          no subject, one line message: SUBSCRIBE PURVEYOR)     ----  #   CD-R (CD-Recordable) media tools:      please see FILE7     ----  "   Grace (WYSIWYG 2D plotting tool),     http://plasma-gate.weizmann.ac.il/Grace/     ----  K   POV-Ray ("Persistance of Vision" Raytracer) ray-tracing graphics package: G     http://www.ourservers.net/openvms_ports/povray/povray_contents.htmll<                                           [Robert Alan Byer]     ----  !   Majordomo mailing list handler:EA     http://www.openvms.compaq.com/openvms/products/ips/majordomo/0     ----  ;   PINE (OpenVMS tools for sending and receiving MIME mail):e*     ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/3     http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/s  5   A MIME tool is available in OpenVMS V7.2 and later.I  >   Also see the mmencode base64 encode and decode available at:9     http://nucwww.chem.sunysb.edu/htbin/software_list.cgiR        ----  7 Menufinder (menu-driven system management environment): '    http://www.itre.com/mf/download.html !    ftp://ftp.itre.com/menufinder/.     ----   tcgmsg, pvm, mpi, linda:<   ftp://v36.chemie.uni-konstanz.de/tcgmsg_vms/tcgmsg_vms.zip     ----  E OpenVMS software that can control a Tripp-Lite Uninterruptable Power h Supply (UPS) is available from:   ;     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/TCONTROL.ZIPe:                                             [David Mathog]  : OnliSafe Software for the PowerWare UPS is available from:E     http://www.powerware.com/2products/software/onlisafe/onlisafe.htmh:                                             [Janis Cooper]  B UPShot web-based software for controlling a UPS is available from:(     http://www.tmesis.com/apc/beta.htmlxB                                             [Brian Schenkenberger]       ----  F Examples of using the OpenVMS Foreign MAIL interface are available at:@   http://www.hhs.dk/anonymous/pub/vms/collection/foreignmail.zip1   http://www.hhs.dk/anonymous/pub/vms/nbl/nbl.zipe  :                                             [Arne Vajhoej]     ----  = For tools to manage or to search your OpenVMS MAIL file, see: =    http://www2.wku.edu/scripts/fileserv/fileserv.com?MLSEARCHe  <                                             [Phillip Helbig]     ----? AscToHTM attempts to convert any plain text file to HTML, whilen> AscToTab restricts itself to files that are plain text tables.5 (Versions are also availabe on the OpenVMS Freeware).c.     http://www.jafsoft.com/asctohtm/index.html.     http://www.jafsoft.com/asctotab/index.html1                                             [Jaf]t     ----  = Information on the SAMBA package (PC disk and print services)t is available at:8   http://ifn03.ifn.ing.tu-bs.de/ifn/sonst/samba-vms.html   http://www.samba.org/   E To subscribe to the SAMBA-VMS mailing list e-mail listproc@samba.org r; with no subject line and the following single line of text:-  #  subscribe samba-vms Your Full Namep  	 Also see:V   http://lists.samba.org/p     ----   Perl: See SOFT12     ----   XML:  8   Source code of an XML Parser is available from Oracle.     Also see:7  '     http://www.python.org/sigs/xml-sig/     ?   An XML parser is available as part of OpenVMS V7.3 and later.p     ----  ' GTK+ (The GIMP GUI Tookit) for OpenVMS:f  =   http://www.openvms.compaq.com/openvms/products/ips/gtk.html-     ----  D OpenVMS Porting Library now available - for easier porting of C/C++ " applications from UNIX to OpenVMS:  A   http://www.openvms.compaq.com/openvms/products/ips/porting.htmlr     ----   Mlucas (specialized FFT):n  *   ftp://hogranch.com/pub/mayer/README.html1                                [Robert Deininger]A     ----  G Tools to monitor the terminals and the activity of other OpenVMS users  I (in addition to existing auditing capabilities in OpenVMS) are available..D Peek and Spy (Networking Dynamics) and Contrl (Raxco) are two of theH commercial packages, while the freeware Supervisor package is available  on OpenVMS VAX.u  $   http://www.networkingdynamics.com/   http://www.raxco.com/i     ----   Python for OpenVMS:m     http://www.python.org/'   http://decus.decus.de/~zessin/python/w    < ------------------------------------------------------------@ SOFT2.    Where can I find the UNIX <whatever> tool for OpenVMS?   POSIX:B   POSIX-compliant, Compaq-supported versions of POSIX routines and   utilities:  C     lex, yacc, grep, tar, uuencode, uudecode, rcs, man, cpio, make,uA     awk, ar, mail, etc., the POSIX shell, the POSIX C programminge     interface, etc.r  @     POSIX utilities can be used from within the POSIX shell, and4     via the DCL `POSIX/RUN POSIX$BIN:tool.' command.  A     POSIX is a separately-installed package, and is licensed withi?     OpenVMS V5.5 later.  The POSIX installation kit is includedDA     on the consolidated distribution CD-ROM kit, and installation '     kits are also available separately.i  D     The POSIX package is no longer supported on OpenVMS, components C     of the POSIX standard such as parts of the POSIX API are being .C     added into OpenVMS.  Versions of POSIX generally do not operaten3     on V7.x OpenVMS VAX and OpenVMS Alpha releases.e   C:  H   Common C system and library routines are present in the DEC C run-timeH   library, which is available for V5.5 and later, and is shipped in V6.1I   and later.  DEC C is the upgrade for VAX C, DEC C and VAX C can coexistsJ   on the same system OpenVMS VAX system, and both compilers can be enabled   via the "C" license PAK.  K     Also see SYS$EXAMPLES:, and (if either is installed) the DECW$EXAMPLES:t     and UCX$EXAMPLES: areas.  
 X Windows:%   Various Compaq X Windows utilities:f  G     xwd, xev, mosaic WWW browser, xrdb, bmtoa and atobm, xpr, ico, etc.   B     In DECW$UTILS: in DECwindows Motif V1.2-3 and later.  Also see0     DECW$EXAMPLES: for example X and C programs.  ! Miscellaneous tools and examples:r6   Various unsupported OpenVMS tools and code examples:  D     DWAUTH (X Windows SYSUAF authorize-like tool), various versions	C     of grep, fgrep, yacc, vmstar, uuencode, gawk, etc.  html tools,.B     the mx SMTP mail exchange package, X windows flight simulator,C     the mxrn X windows news reader, the OSU HTTPD WWW server, a WWWu=     gopher browser, etc. are all on the FreeWare V2.0 CD-ROM.K  	 IP tools: E   DEC TCP/IP (UCX) contains tools such as ping, uuencode, smtp, snmp,rG   rcp, nfs, tnfs, etc.  OpenVMS V6.2 and UCX V3.3 and later can be usedhF   together in support of the /FTP, /RCP, /RLOGIN, /TELNET, and /TN3270%   qualifiers on various DCL commands.   4     Also see the various C examples in UCX$EXAMPLES:   					[Stephen Hoffman]  	 vi clones/  1   Both vile and elvis (vi clones) run on OpenVMS..  $   The current version of vile is 7.1   It's available atw/ 	http://www.clark.net/pub/dickey/vile/vile.htmlt$ 	ftp://ftp.clark.net/pub/dickey/vile 	ftp://id.wing.net/pub/pgf/vileR2 	Versions of VILE are also on the OpenVMS Freeware   					[Thomas Dickey]     vim: vi improved      http://www.polarfox.com/vim/9                                         [Zoltan Arpadffy]   
 GNU tools:  I   Information on the GNU on VMS Project, which aims to port GNU software p   to VMS, is available at:       http://vms.gnu.ai.mit.edu/%     ftp://vms.gnu.ai.mit.edu/gnu-vms/e     Software info:  '     http://vms.gnu.ai.mit.edu/software/i     Software archive:.  .     ftp://vms.gnu.ai.mit.edu/gnu-vms/software/  
 GNV tools:  *   BASH (Bourne Again Shell) (part of GNV):   http://gnv.sourceforge.net/n     GCC:  I   A mirror for work performed at the Progis company in Germany in porting ?   GCC (GNU C) to OpenVMS Alpha and OpenVMS VAX is available at:a  '     ftp://vms.gnu.org/progis_mirror/gcc   K   The latest (known to me) GCC version for VAX/VMS (binaries only) is 2.7.1w   from Pat Rankin's site.   &     ftp://ftp.caltech.edu/pub/rankin/   G                                     [Jason Armistead, Richard Levitte,  C                                     Arne Vajhoej, John E. Malmberg]   I There are also updated header files for GCC on OpenVMS VAX that allow it s6 to work with TCP/IP Sockets and the Compaq C C RTL at:  (   ftp://ftp.qsl.net/pub/wb8tyw/gcc281_u/  :                                         [John E. Malmberg]    = Some of the available console management options for OpenVMS:t  1   http://www.robomon.com/robocentral.htm (Heroix)o1   http://www.ki.com/products/clim/  (KI Products)t,   http://www.globalmt.com/ (Global Maintech)!   http://www.tditx.com/ (TechSys)C0   http://www.cai.com/products/commandit.htm (CA)3                                        [Kerry Main]r  A If you need to change the file modification date and are looking s> for a utility such as the UNIX touch tool, look at DFU on the > OpenVMS Freeware (DFU SET or simular), or use an existing DCL  commands such as:-  5   SET FILE/PROTECT=(current_protection_mask) [...]*.*     @ A table listing translations between UNIX shell and OpenVMS DCL 8 commands was posted to comp.os.vms by Christopher Smith:     http://deja.com/getdoc.xp?.     AN=581596523.1&CONTEXT=953337549.952369155     --  3 The UNIX touch tool is available via various means:r  !   $ RENAME filename.ext;version *b7   http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCH .   MadGoat FILE tool (see the MadGoat archives)(     use /REVISION_DATE or /CREATION_DATE)   The DFU tool (see the OpenVMS Freeware)    The pair: 5     $ set file 'p1' /acl=(ident=[system],access=none)c=     $ set file 'p1' /acl=(ident=[system],access=none) /deleteH   SET FILE/VERSION=0   The following hack:l&     $!   Command procedure SETDATE.COM     $!1     $!   Changes the DATES for an input file to ao     $!   file named OUTFILE.     $!     $assign/nolog 'p1' outfile(     $convert/fdl=sys$input 'p1' outfile:     date     creation   01-apr-2010     expiration 01-Apr-2012     revision   01-Apr-2011
     backup     ...S,   The following RMS system service sequence:     $open (with xabrdt),(     set the desired values in the xabrdt
     $close  < ------------------------------------------------------------I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser?a  C Mozilla.org is the open source organization providing Netscape and hB other interested parties with a browser.  Netscape is expected to C commercialize this mozilla.org browser, add additional proprietary eG features, and release it as Netscape Communicator (version number TBD).vG This Netscape Communicator will contain the features that the Internet 36 community expected to see in Netscape Communicator V5.  B OpenVMS Engineering is currently porting Mozilla.org's web browserH to OpenVMS -- OpenVMS baselevels of the browser are currently available  for download.  w  5 The Mozilla.org web browser schedule is available at:   !   http://www.mozilla.org/project/m  > The latest information and current downloads are available at:  5   http://www.openvms.compaq.com/openvms/products/ips/t  E See section SOFT9 for information on various certificates for V3.003 p= Netscape Navigator; certificates that have presently expired.l 					[Sue Denham]s 					[Stephen Hoffman]  < ------------------------------------------------------------+ SOFT4.    Where can I get Java for OpenVMS?.  D   Java is available on and is included with OpenVMS Alpha, starting F   with the OpenVMS Alpha V7.2 and later releases.  Java download kits :   are available for OpenVMS Alpha V7.1 and later releases.  G   Java is not available on OpenVMS VAX.  As for why: the Java language gH   definition requires a floating point format (IEEE) that is not native E   to VAX, and this would require the emulation of all floating point oH   operations within Java applications.  Further, the C source code used D   to implement for Java itself is heavily dependent on passing IEEE H   floating point values around among the many internal subroutines, and G   adding support for VAX would entail changes to the Compaq C compiler sI   for OpenVMS VAX -- and specifically to the VAX VCG code generator that cH   is used by Compaq C on OpenVMS VAX systems -- in order to add support I   for passing IEEE-format floating point doubles around.  Alternatively,  J   extensive changes to the Java source code to remove the assumption that -   the double is an IEEE floating point value.l  F   There are currently no plans to make a version of Java available forI   OpenVMS VAX.  (A prototype version of Java was created for OpenVMS VAX,u6   and performance was found to be inadequate at best.)  H   If Java2 or other environment lifts the requirements for IEEE floatingK   point as part of the language definition, this decision may be revisited.t  F   For additional information on Java for Alpha systems, please see theA   OpenVMS documentation (V7.2 and later), and the following site:-  /     http://www.compaq.com/java/alpha/index.html   < ------------------------------------------------------------J SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?  F   VAX C V3.2 was released for OpenVMS VAX systems in 1991.  DEC C V4.0F   replaced VAX C V3.2 in 1993 as the Compaq C compiler for OpenVMS VAXF   systems.  Compaq C is the AMSI C compiler for OpenVMS Alpha systems.E   VAX C predates the ANSI C standards, and has various areas that areaJ   not compliant with ANSI C requirements.  Compaq C is an ANSI C compiler,H   and can also compile most VAX C code when /STANDARD=VAXC is specified.I   Versions of this compiler between V3.2 and V6.0 (exclusive) were known v   as either DEC C or DIGITAL C.b  F   Both compilers can be installed at the same time on the same OpenVMSD   VAX system, allowing a migration from VAX C to DEC C, and allowingF   the same DEC C code to be used on OpenVMS VAX and OpenVMS Alpha.  In0   1999, the C compiler version is Compaq C V6.0.  B   The system manager can choose the system default C compiler whenF   Compaq C is installed on a system with VAX C, and a C programmer canK   explicitly select the required compiler for a any particular compilation.a  K   A current "C" license PAK allows access to both VAX C and Compaq C on thec   same OpenVMS VAX system.  M   Various Compaq C versions can be installed on OpenVMS VAX V5.5-2 and later.lL   OpenVMS VAX releases such as V5.5-2 and V6.0 will require the installationK   of a Compaq C RTL kit, a kit that is included with the Compaq C compiler.wI   OpenVMS VAX versions V6.1 and later do not require a seperate RTL kit, rI   but Compaq C RTL ECO kits are available to resolve problems found with f(   the C RTL on various OpenVMS releases.  E   Wwith Compaq C, for automatic resolution of the standard C library rD   routines by the LINKER utility, use the /PREFIX qualifier, such asG   /PREFIX=ALL_ENTRIES.  If a particular application program replaces an E   existing C library routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)). E   (VAX C required explicit specification of an RTL shareable image orn$   C object library during the link.)  H   When the /PREFIX is requested, the compiler generates a "decc$" prefixI   on the specified symbols.  This prefix allows the LINKER to resolve theoG   external symbols against the symbols present in the DECC$SHR library. F   The DECC$SHR library is included in the IMAGELIB.OLB shareable imageH   library, and IMAGELIB is searched by default when any program (writtenE   in any language) is LINKed.  Because the standard C library routineoF   names are very likely to match application routines written in otherF   languages, a prefix "decc$" is added to the C symbol names to assureD   their uniqueness; to prevent symbol naming conflicts.  C programs,E   however, can sometimes have private libraries for various purposes,AI   and the external routines share the same names as the library routines. F   (This is not recommended, but there are applications around that useE   this technique.)  Thus the need to explicity specify whether or notsE   the "decc$" prefix should be prepended to the external symbol namesd   by the compiler.  F   The qualifiers, and most (all?) with associated pragmas, that may be<   of interest when migrating VAX C code to Compaq C include:       /PREFIX=ALL_ENTRIESwB       As mentioned above.  Failure to specificy this qualifier canA       cause the compiler to not add the prefixes for the names oflE       the C library routines into the references placed in the objectOE       module, which can in turn cause problems resolving the externalL<       symbols in the library when the object code is linked.  $     /ASSUME=WRITABLE_STRING_LITERALSC       Some VAX C programs erroneously write to the string literals.pB       By default, Compaq C does not allow the constants to change.       /SHARE_GLOBALSA       Enables sharing ("shr") of globals and of extern variables.-G       Compaq C sets externs as non-shareable ("noshr"), VAX C as "shr".o       /EXTERN_MODE=COMMON_BLOCK0=       VAX C assumes common block model for external linkages.I       /[NO]MEMBER_ALIGNMENTlA       Refers to the padding placed between member elements within/?       a struct.  Disabling member alignment packs the data morer=       tightly into memory, but this packaging has performancee;       implications, both on OpenVMS VAX and particularly ong       OpenVMS Alpha systems.  E   Permit structure members to be naturally aligned whenever possible,/E   and avoid using /NOMEMBER_ALIGNMENT.  If you need to disable member A   alignment, use the equivilent #pragma to designate the specificmE   structures.  The alignment of structure members normally only comesUB   into play with specific unaligned data structures -- such as theF   sys$creprc quota itemlist -- and with data structures that are usingD   data that was organized by a system using byte or other non-member   alignment.  I   Versions of Compaq C such as V6.0 include the capability to extract theoD   contents of the standard header libraries into directories such asG   SYS$SYSROOT:[DECC$LIB...], and provide various logical names that can G   be defined to control library searches.  With Compaq C versions such  H   as V6.0, the default operations of the compiler match the expectationsC   of most OpenVMS programmers, without requiring any definitions ofnG   site-specific library-related logical names.  (And logical names left/E   from older DEC C versions can sometimes cause the compiler troublesn   locating header files.)   D   Compaq C V5.6 and later include a backport library, a mechanism byF   which Compaq C running on older OpenVMS releases can gain access to G   newer RTL routines added to the RTL in later OpenVMS releases -- the oE   language RTLs ship with OpenVMS itself, and not with the compilers.   F   Example C code is available in SYS$EXAMPLES:, in DECW$EXAMPLES (whenF   the DECwindows examples are installed), in UCX$EXAMPLES (when CompaqE   TCP/IP Services is installed), on the Freeware CD-ROMs, and at web     sites such asJ  )     http://www.openvms.compaq.com/wizard/c     Other common C issues:  F     The localtime() function and various other functions maintain the C     number of years since 1900 in the "struct tm" structure member aG     tm_year.  This field will contain a value of 100 in the year 2000, oF     101 for 2001, etc., and the yearly incrementation of this field is     expected to continue.m  G     The C epoch typically uses a longword (known as time_t) to contain fH     the number of seconds since midnight on 1-Jan-1970.  At the current J     rate of consumption of seconds, this longword is expected to overflow J     (when interpreted as a signed longword) circa 03:14:07 on 19-Jan-2038 J     (GMT), as this time is circa 0x7FFFFFFF seconds since the C base date.G     (The most common solution is to ensure that time_t is an unsigned.)p  H     If C does not correctly handle the display of the local system time,J     then check the UTC configuration on OpenVMS -- the most common symptomI     of this is a skew of one hour (or whatever the local daylight savingstJ     time change might be).  This skew can be caused by incorrect handling J     of the "is_dst" setting in the application program, or by an incorrectH     OpenVMS UTC configuration on the local system.  (See section TIME4.)       Other common C++ issues:  G     Compaq C++ (a separate compiler from Compaq C) provides both symbolXH     mangling and symbol decoration.  Some of the details of working withG     longer symbol names and the resulting symbol name mangling in mixeddE     language environments are listed in the shareable image cookbook,-E     and in the C++ documentation.  Symbol name decoration permits the J     overloading of functions (by adding characters to the external symbol J     for the function to indicate the function return type and the argumentI     data types involved), and mixed-language external references can and IL     often do need to disable this decoration via the extern "C" declaration      mechanism:         extern "C"	         {P(         extern int ExternSymbol(void *);-         extern int OtherExternSymbol(void *); 	         }t    G   Also see ALPHA16 for information on /ARCHITECTURE and /OPTIMIZE=TUNE.t   < ------------------------------------------------------------1 SOFT6.    Obtaining user input in DCL CGI script?   E If you choose to use the GET method, then the form data is available s6 in the DCL symbol QUERY_STRING, in URL-encoded format.  E If you use the POST method, then you need to read the form data from VE stdin. For a DCL CGI script running under the Netscape FastTrack web  ? server, you can read the data using the following READ command:,     $ READ SYS$COMMAND postdatal   to read the information in. =                                                 [Colin Blake]   @ The following describes the use of DCL command procedures as CGI  scripts with the OSU web server:  2 http://www.levitte.org/~ava/cgiscripts_other.htmlx>                                                 [Leif Jansson]  < ------------------------------------------------------------1 SOFT7.    How do I get my own batch entry number?,  > To have a batch procedure retrieve its own batch entry number, use the following:  '   $ Entry = F$GETQUI("DISPLAY_ENTRY", -o0       "entry_number","display_entry","this_job")  E Remember that the entry numbers issued by the OpenVMS Job Controller wE are opaque longword values.  Don't assume you know the format of the a1 number, nor the range of numbers you might see... >                                                 [Peter Weaver]  < ------------------------------------------------------------0 SOFT8.    How do I convert to new CMS libraries?  E A change was made to the format of the CMS database for CMS librariesaC starting with V3.5-03 -- to ensure that earlier versions of CMS areaB unable to access the database once the "conversion" to V3.5-05 andG later is made, you must issue the following two commands when upgradingnB from V3.5-03 and prior.  (The only differences between CMS versionA V3.5-03 and CMS version V3.5-05 involve changes to ensure that nps< earlier version of CMS can access the "converted" database.)  B To perform the "conversion", issue the following commands for each CMS library present:  ,     $ RENAME disk:[directory]00CMS.* 01CMS.**     $ COPY NLA0: disk:[directory]00CMS.CMS  B The new file 00CMS.CMS must have the same security settings as theG 01CMS.CMS file, and is created solely to ensure continued compatibilityfE with tools that expect to find a 00CMS.CMS file (eg: various versionsm. of the Language-Sensitive text editor LSEDIT).  < ------------------------------------------------------------B SOFT9.    Where can I get new certificates for Netscape Navigator?  @ The URLs that I found for adding/updating root certificates are:  E http://www.entrust.net/customer/generalinfo/import.htm        entrustVD http://www.equifaxsecure.com/servercert/rollover.html         thawteF https://www.verisign.com/server/prg/browser/root.html         verisign6                                           [Ken Chaney]  > To update certificates in Netscape Navigator V3.03 on OpenVMS, use the following:  8 Here's how to update your Root certificates in Netscape:  0 Thawte Server certificate which expired in 1998:  : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" tabr8 3) Select "Thawte Server CA" in the list of certificates, 4) Select "Delete Certificate" and then "OK". 5) Go to http://www.thawte.com/serverbasic.crtL 6) Follow the instructions on the popup dialog box to accept the certificateH    This mostly involves hitting the "Next" button and clicking an acceptI    button and then naming the resulting certificate.  I named it the sameh    name as the original.  ; VeriSign/RSA Server certificate which expired Dec 31, 1999:o  : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" tab E 3) Select "Verisign/RSA Secure Server CA" in the list of certificatese, 4) Select "Delete Certificate" and then "OK"> 5) Go to https://www.verisign.com/server/prg/browser/root.htmlL 6) Follow the instructions on the popup dialog box to accept the certificateH    This mostly involves hitting the "Next" button and clicking an acceptG    button and then naming the resulting certificate.  Verisign suggestso     using the name "VeriSign CA".  ;                                           [Vance Haemmerle]1  < ------------------------------------------------------------3 SOFT10.   Why doesn't DCL symbol substitution work?l  F The DCL symbol substitution processing occurs only at the DCL prompt, E not within data and not within files.  If you wish to perform symbol _C substitution in this environment, you typically write a small file  E containing the command(s) and data to be invoked -- potentially only  C the data -- and you then invoke the created procedure or reference E the specified data.l  C In this case, use of a file containing nolinemode commands or otherCC techniques might be useful -- you will want to ensure that the text.F editor you use does not attempt to use screen mode or similar, as thisD is not generally considered adventageous within a command procedure.  . Tools such as FTP have alternatives: COPY/FTP.  E DCL symbol substitution occurs in two passes, using the ampersand andrE the apostrophe.  In most cases, only the apostrophe is necessary.  In-G a few cases -- such as the DCL PIPE command -- you will may need to use E the ampersand to get the substitution to work.  The following exampletB uses ampersand substitution to transfer the contents of the header into a logical name:  F   $ PIPE CC/VERSION | (READ SYS$PIPE hdr ; DEFINE/JOB/NOLOG hdr &hdr )  G A logical name (in the job logical name table; shared by all processes oG in the current job) was used as DCL symbols cannot be returned back outt, from a DCL PIPE or other spawned subprocess.    < ------------------------------------------------------------D SOFT11.   Preventing a serial terminal line from initiating a login?  *   In SYSTARTUP_VMS.COM, issue the command:  ,     SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:  @   This will prevent any unsolicited terminal input on ddcu:, andA   this unsolicited input is what triggers JOB_CONTROL to start uptB   LOGINOUT on the terminal.  Once LOGINOUT starts up on the serial>   line, you can see interesting behaviour (eg: audits, processB   creations, etc) as LOGINOUT tries to "chat" with whatever device<   is hooked onto the remote end of the serial terminal line.  < ------------------------------------------------------------+ SOFT12.   Where can I get Perl for OpenVMS?d  F OpenVMS support is included in the standard distribution of Perl, the I popular scripting language created by Larry Wall.  In addition to nearly  E all of the functionality available under Unix, OpenVMS-specific Perl  E modules provide interfaces to many native features, as well as accessrF to Oracle, Ingres, and Sybase databases via the Perl DBI available on  OpenVMS.  G A website useful for getting started with Perl on OpenVMS -- where you CH will find such things as download links, instructions, auxiliary tools, & and sample scripts -- is available at:  !      http://www.sidhe.org/vmsperlt  E If you have a C compiler, the best way to obtain Perl is to download  D and build it yourself.  The latest production quality source kit is  available from:   /      http://www.perl.com/CPAN/src/stable.tar.gzo  I You will need GUNZIP and VMSTAR (both available from the OpenVMS Freeware.G CD, or from other sites) to unpack the archive; once you've done that,  - read the instructions in the README.vms file.l  G Binary distributions for most Alpha and VAX environments are available  H on the OpenVMS Freeware CD-ROM and from various websites, including the 
 following:  /      http://www.sidhe.org/vmsperl/prebuilt.htmla2      http://www.openvms.compaq.com/freeware/perl5/  H During active Perl development cycles, test kits are sometimes found at: from:h  '      ftp://perl.newman.upenn.edu/perl5/i      ftp://ftp.sidhe.org/f  H Watch the mailing list (see below) for details on experimental releases.  I Charles Lane maintains pages on how to write CGI scripts in Perl for the  G OSU HTTP server, as well as more general tips, tricks, and patches for  % building and running Perl on OpenVMS:o  )      http://www.crinoid.com/crinoid.htmlxr  G There are OpenVMS-specific Perl modules that implement interfaces to a  H subset of the VMS System Services. With these modules, you can get (and J often set) device, job, queue, user, system, and performance information. F The lock manager, RMS indexed files, screen management utilities, and G Intracluster Communication Services are also accessible via Perl.  The s( relevant modules are all available from:  3      http://www.perl.com/CPAN/modules/by-module/VMS   F To subscribe to the OpenVMS Perl mailing list (a discussion forum for A both user support and new development), send an email message to:y       vmsperl-subscribe@perl.org  - The mailing list archives may be searched at:   4     http://www.xray.mpe.mpg.de/mailing-lists/vmsperl;                                               [Craig Berry]n  < ------------------------------------------------------------4 SOFT13.   Where can I get DECmigrate (VEST and TIE)?  @   The DECmigrate image translation tool, a tool that translates >   OpenVMS VAX images for use on OpenVMS Alpha is available at:  <      http://www.support.compaq.com/amt/decmigrate/index.html  '   This tool is not currently supported.o     See UTIL4.   [End of Part 4/5]p  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 29 Dec 2000 20:34:33 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 5/5e6 Message-ID: <92isgp$f4j$5@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part5  Posting-Frequency: monthly Last-modified: 29 Dec 2000 Version: VMS-FAQ-5.TXT(5)a    9 This is the OpenVMS Frequently Asked Questions Part 5/5. a@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------, ALPHA1.   What do the letters AXP stand for?  I While there are many fanciful "definitions" which have circulated widely,iH the truth is that AXP is not an abbreviation nor an acronym; the lettersC do not mean anything.  They are just three letters chosen to form aC
 trademark.  E When it came time to chose a "marketing name" for the Alpha AXP line, I the company was in a quandary.  The internal "code name" for the project,KK Alpha, was widely known and would seem the ideal choice, but it was alreadyhJ in common use by a number of other companies and could not be trademarked.G A well-known "name search" firm was hired and was asked to come up with F two lists of possible names.  The first list was intended to evoke theC feeling of "extension to VAX", while the second list was to suggest G "not a VAX".  Unfortunately, none of the choices offered were any good;rI for example, "VAX 2000" was found on the first list while the second listp< contained "MONDO" (later to be used for a kids' soft drink).  J Shortly before announcement, a decision was made to name the new line ARA,H for Advanced RISC Architecture.  However, an employee in Israel quickly K pointed out that this name, if pronounced in the "obvious" manner, sounded  E very much like an Arabic word with decidely unfortunate connotations.aF Eventually, AXP was selected; the architecture would be referred to as= "Alpha AXP" whereas products themselves would use just "AXP".   G Use of the AXP term has been phased out in favour of using Alpha.  For yG example, "OpenVMS AXP" is now officially refered to as "OpenVMS Alpha".B  < ------------------------------------------------------------A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?   I Very few.  As of OpenVMS V6.1, the VAX and Alpha platforms are very close B to "feature parity".  Most applications can just be recompiled and& run.  Some differences to be aware of:  A     - The default double-precision floating type on OpenVMS AlphakD       is VAX G_float, whereas on VAX it is usually D_float.  D_float@       is available on Alpha, but D_float values are converted toA       G_float for computations and then converted back to D_floatiE       when stored.  Because the G_float type has three fewer fractionoE       bits than D_float, some applications may get different results.m;       IEEE float types are also available on OpenVMS Alpha.e  C     - Data alignment is extremely important for best performance ond?       Alpha.  This means that data items should be allocated ataC       addresses which are exact multiples of their sizes.  Quadwordo?       alignment will offer the best performance, especially forcA       character values and those smaller than 32 bits.  CompilerssB       will naturally align variables where they can and will issue3       warnings if they detect unaligned data items.s  E     - Compaq C is the only C compiler Compaq offers on OpenVMS Alpha.nA       It is compatible with DEC C on OpenVMS VAX, but is somewhat$L       different from the older VAX C compiler most people are familiar with.D       Read up on the /EXTERN_MODEL and /STANDARD qualifiers to avoid       the most common problems.e  K     - The page size on Alpha systems is variable, but is at least 8K bytes.iE       This can have some effect on applications which use the $CRMPSC B       system service as well as on the display of available memoryF       pages.  The page size is available from $GETSYI(SYI$_PAGE_SIZE).  K There are also a number of manuals which discuss migration to OpenVMS AlphaiK available on the documentation CD-ROM media, both in the main documentationt* and in the archived documentation section.  F On more recent OpenVMS Alpha versions, OpenVMS Alpha has begun to add F features and support not available on OpenVMS VAX.  Salient new areas  include the following:  7     - 64-bit addressing in OpenVMS Alpha V7.0 and laterS:     - Multi-host SCSI support (SCSI TCQ) in V6.2 and later&     - PCI support (platform-dependent).     - OpenVMS Galaxy support in V7.2 and later  < ------------------------------------------------------------& [ALPHA3 removed, information obsolete]  < ------------------------------------------------------------> [ALPHA4 relocated to VMS16, and out of Alpha hardware section]  < ------------------------------------------------------------F ALPHA5.   Seeking performance information for Alpha (and VAX) systems?  F   Compaq makes a wide range of performance documents available through.   its FTP and WWW Internet servers (see DOC2).  F   The following contain information on current Alpha and VAX products:  2     http://www.compaq.com/alphaserver/servers.html4     http://www.compaq.com/alphaserver/vax/index.html  D   The following sites contain information on various retired VAX and   Alpha products:u  8     http://www.compaq.com/alphaserver/archive/index.html?     http://www.compaq.com/alphaserver/performance/perf_tps.htmlo     Also see CPU2000:o  $     http://www.spec.org/osg/cpu2000/8     http://www.spec.org/osg/cpu2000/results/cpu2000.html    < ------------------------------------------------------------D ALPHA6.  Where can I get updated console firmware for Alpha systems?    = Firmware updates for Compaq Alpha systems are available from:c  ?     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/index.htmle5     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/ @     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html  J The latest and greatest firmware -- if updated firmware has been released C after the most recent firmware CD was distributed -- is located at:k  =     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/m  J Please send your comments and feedback to alpha_server@service.digital.com  F For information on creating bootable floppies containing the firmware,6 and for related tools, please see the following areas:  C   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkboot.txtiF   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkbootarc.txtE   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkntboot.txtt  ;                                           [Stephen Hoffman]6  A To check the firmware loaded on recent OpenVMS Alpha systems, use- the command:  0   $ write sys$output f$getsyi("console_version")0   $ write sys$output f$getsyi("palcode_version")   SDA> CLUE CONFIG7                                           [Clair Grant]o   Also see ALPHA14.L    < ------------------------------------------------------------D ALPHA7.   How do I boot an AlphaStation without monitor or keyboard?  H The AlphaStation series will boot without a keyboard attached.  To use aN serial terminal as the console, issue the console command SET CONSOLE SERIAL -H after that, it will use the terminal.  The DEC 3000 model 300 series hasC a jumper on the motherboard for this purpose.  Various older Alpha  D workstations generally will not (automatically) bootstrap without a F keyboard connected, due to the self-test failure that arises when the  (missing) keyboard test fails.  K The usual settings for the console serial terminal (or PC terminal emulatorb acting as a serial console are:   >   9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).  K The AlphaStation and AlphaServer series use the PC DIN serial connector forjE the "COM1" and "COM2" serial lines, see MISC1 for details and pinout.o  < ------------------------------------------------------------< ALPHA8.  Will OpenVMS run on a Multia? AlphaPC 164LX? 164SX?  F Yes, there are a set of unsupported images that permit recent OpenVMS H Alpha versions to bootstrap on the Multia UDB system.  These images and J the associated instructions are available at the OpenVMS Freeware website:  0   http://www.openvms.compaq.com/freeware/multia/  > Instructions are included IN the kits.  READ THE INSTRUCTIONS.  E Some of the restrictions involved when running OpenVMS on the Multia m> system include (but may well not be limited to) the following:  A   o The PCMCIA support was completely removed, because the Intel  B     chip on the Multia was not compatable with the Cirrus chip on      the Alphabook.  @     This means, of course, that you will not see and cannot use !     any PCMCIA cards on a Multia.   B   o The Multia uses shared interrupts, and as a result, a special B     ZLXp-E series graphics device driver -- one that does not use A     interrupts -- is needed.  This driver is provided in the kit.e      o The serial lines don't work.  ?   o If you have a Multia with a PCI slot, you can't use any PCIr"     card that requires interrupts.  @   o The SRM console on this system is very old and very fragile.D     (This SRM console was designed only and strictly for diagnostic ?     use, and was not particularly tested or used with OpenVMS.)   B   o If things don't work for you, don't expect to see any OpenVMS 6     updates, nor SRM console updates, nor any support.   F The Multia images are not included on the OpenVMS Freeware V4.0 CD-ROMD kit, the kit that was distributed with OpenVMS V7.2.  (These images . became available after Freeware V4.0 shipped.)  ; Other sources of information for OpenVMS on Multia include:   <   http://home.earthlink.net/~djesys/vms/hobbyist/multia.html>   http://home.earthlink.net/~djesys/vms/hobbyist/mltianot.html=   http://home.earthlink.net/~djesys/vms/hobbyist/support.html 2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman];                                         [David J. Dachtera]/  E OpenVMS Alpha is not supported on the AlphaPC 164LX and 164SX series,iC though there are folks that have gotten certain of the LX series toh@ load SRM and bootstrap OpenVMS.  (The Aspen Durango II variant.)@ One problem was reported: IDE bootstraps fail; SCSI is required.   Also see ALPHA13.R  < ------------------------------------------------------------B ALPHA9.  What is the least expensive system that will run OpenVMS?  ? The cheapest systems presently offered by Compaq that will run tC OpenVMS are the AlphaServer DS10 server and the AlphaStation XP900 "B workstation.  Other companies sell Alpha-powered systems and AlphaA motherboards, some of which will run (and can be purchased with) iB OpenVMS -- see the OpenVMS Software Product Description (SPD) for E details on the supported systems and configurations.  There are also iC many used AlphaStation, AlphaServer, and DEC 3000 models available  ? which are quite suitable.  For more experienced OpenVMS system -@ managers, the (unsupported) Multia can bootstrap OpenVMS -- see  ALPHA8 for details.   @ Depending on the OpenVMS version and configuration, the OpenVMS 3 Software Product Description (SPD) is available at:I  !   http://www.compaq.com/info/spd/i:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  F When purchasing a system, ensure that the system itself is supported, D that the system disk drive is supported or closely compatible, that B the CD-ROM drive is supported or is closely compatable and that itF also specifically supports 512 byte block transfers, and particularly D ensure that video controller is supported.  Use of supported Compaq H hardware will generally reduce the level of integration effort involved.  ; A CD-ROM drive is required for OpenVMS Alpha installations.C 					[Stephen Hoffman]  < ------------------------------------------------------------< ALPHA10.  Where can I get more information on Alpha systems?  5 Compaq operates an AlphaServer information center at:w  $   http://www.compaq.com/alphaserver/  > Alpha Technical information and documentation is available at:  ,   http://www.support.compaq.com/alpha-tools/)      documentation/current/chip-docs.html/  1   ftp://ftp.compaq.com/pub/products/alphaCPUdocs/h  .   ftp://ftp.digital.com/pub/DEC/Alpha/systems/  *   http://ftp.digital.com/pub/Digital/info/.      semiconductor/literature/dsc-library.html  #   Platform product documentation:  a#     http://www.compaq.com/info/spd/-7     http://www.digital.com/info/lists/key-server_AL.HTMr<     http://www.digital.com/info/lists/key-workstation_AL.HTM  / Information on Multia hardware is available at:   2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman]  A Information on current and future Alpha microprocessor designs isO$ also available from AlphaPowered at:  1   http://www.alphapowered.com/alpha_tomorrow.html +   http://www.alphapowered.com/timeline.html:.   http://www.alphapowered.com/ev7-and-ev8.html  = The NetBSD folks maintain some Alpha hardware information at:   /   http://www.netbsd.org/Ports/alpha/models.html-  < ------------------------------------------------------------, ALPHA11.  What are the APB boot flag values?  ? The following flags are passed (via register R5) to the OpenVMSi@ Alpha primary bootstrap image APB.EXE.  These flags control the & particular behaviour of the bootstrap:     >>> BOOT -FL root,flags         bit      description 9      ---   ----------------------------------------------,  -       0    CONV      Conversational bootstrapo3       1    DEBUG     Load SYSTEM_DEBUG.EXE (XDELTA)wP       2    INIBPT    Stop at initial system breakpoints if bit 1 set (EXEC_INIT)>       3    DIAG      Diagnostic bootstrap (loads diagboot.exe)D       4    BOOBPT    Stop at bootstrap breakpoints (APB and Sysboot)F       5    NOHEADER  Secondary bootstrap does not have an image header(       6    NOTEST    Inhibit memory test8       7    SOLICIT   Prompt for secondary bootstrap file@       8    HALT      Halt before transfer to secondary bootstrap)       9    SHADOW    Boot from shadow set '       10   ISL       LAD/LAST bootstrap 1       11   PALCHECK    Disable PAL rev check haltmA       12   DEBUG_BOOT  Transfer to intermediate primary bootstraps+       13   CRDFAIL       Mark CRD pages badRA       14   ALIGN_FAULTS  Report unaligned data traps in bootstrapt@       15   REM_DEBUG   Allow remote high-level language debugger@       16   DBG_INIT    Enable verbose boot messages in EXEC_INITM       17   USER_MSGS   Enable subset of verbose boot messages (user messages)u0       18   RSM         Boot is controlled by RSM5       19   FOREIGN     Boot involves a "foreign" diskl  H   If you want to set the boot flags "permanently" use the SET BOOT_FLAGS   command, e.g.P            >>> SET BOOT_OSFLAGS 0,1    < ------------------------------------------------------------7 ALPHA12.  What are Alpha console environment variables?   = Alpha systems have a variety of variables with values set up  ; within the SRM system console.  These environment variablesc; control the particular behaviour of the console program andd? the system hardware, the particular console interface presentedsB to the operating system, various default values for the operating < system bootstrap, and related control mechanisms -- in other> words, "the environment variables provide an easily extensible. mechanism for managing complex console state."  < The specific environment variables differ by platform and by: firmware version -- the baseline set is established by the Alpha Architecture:   :   AUTO_ACTION ("BOOT", "HALT", "RESTART", any other value ;   assumed to be HALT),  BOOT_DEV, BOOTDEF_DEV, BOOTED_DEV,  8   BOOT_FILE, BOOTED_FILE, BOOT_OSFLAGS, BOOTED_OSFLAGS, :   BOOT_RESET ("ON", "OFF"), DUMP_DEV, ENABLE_AUDIT ("ON", 1   "OFF"), LICENSE, CHAR_SET, LANGUAGE, TTY_DEV.  g  = OpenVMS Galaxy firmware can add console environment variablesAB beginning with such strings as LP_* and HP_*, and each particular > console implementation can (and often does) have various sorts9 of platform-specific extensions beyond these variables...4  C The contents of a core set of environment variables are accessable -B from OpenVMS using the f$getenv lexical and the sys$getenv system B service. (These calls are first documented in V7.2, but have been B around for quite a while.)  Access to arbitary console environment> variables is rather more involved, and not directly available.9                                         [Stephen Hoffman]o  < ------------------------------------------------------------0 ALPHA13.  Will OpenVMS run on a NoName AXPpci33?  < Information on bootstrapping OpenVMS (using Multia files) on9 the (unsupported) NoName AXPpci33 module is available at:a  /   http://www.jyu.fi/~kujala/vms-in-axppci33.txt-  2 Tips for using the Multia files with the AXPpci33:  ?   o You have to use the Multia kit and follow the directions in ?     ALPHA8, but do *not* load the Multia SRM firmware into the b@     AXPpci33.  Rather, download and use the latest firmware for :     the AXPpci33 from the Compaq firmware website instead.  (   o 64 MB memory is generally necessary.  A   o you cannot use any PCI cards, and if you plan on networking, l?     you need to find an ISA Ethernet card supported by OpenVMS.   @   o When the AXPpci33 board bootstraps, it will dump some stuff A     like a crash dump, but it will continue and -- so far -- thisa)     hasn't caused any particular hassles.c  C   o The system shutdown and reboot procedures do not work properly.   A   o The serial console is reported to not work, though the serialsB     ports apparently do work.  The status of the parallel port is      unknown.  A   o Rumour has it that you have one of the AXPpci33 motherboards e?     with the PS/2 mouse and keyboard connectors and a VGA card dE     (one that will work under DECwindows) and you can run DECwindows n     on the system. a8                                       [Robert Alan Byer]  < ------------------------------------------------------------D ALPHA14.  How do I reload SRM firmware on a half-flash Alpha system?  I   Some of the AlphaStation series systems are "half-flash" boxes, meaningbG   only one set of firmware (SRM or AlphaBIOS) can be loaded in flash at"G   a time.  Getting back to the SRM firmware when AlphaBIOS (or ARC) is a'   loaded can be a little interesting...f  I   That said, this usually involves shuffling some files, and then getting-H   into the AlphaBIOS firmware update sequence, and then entering "update   srm" at the apu-> prompt.f  I   To shuffle the files, copy the target SRM firmware file (as200_v7_0.exetK   is current) to a blank, initialized, FAT-format floppy under the filenamee   A:\FWUPDATE.EXE:  G   From the AlphaBIOS Setup screen, select the Upgrade AlphaBIOS option. 5   Once the firmware update utility gets going, enter:         Apu-> update srmb  0            Answer "y" to the "Are you ready...?"        Apu-> quitp  K   You've reloaded the flash.  Now powercycle the box to finish the process._     Also see ALPHA6.  < ------------------------------------------------------------2 ALPHA15.  Will OpenVMS run on the Alpha XL series?  4   No.  OpenVMS does not support the Alpha XL series.  D   OpenVMS can not, will not, and does not bootstrap on the Alpha XL C   series.  The Alpha XL series was targeted for use (only) with the )   Microsoft Windows NT operating system.   D   For the list of boxes officially supported by OpenVMS, please see 1   the OpenVMS Software Product Description (SPD).o  #     http://www.compaq.com/info/spd/r<     OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  I   If you are very lucky, sometimes a particular unsupported Alpha box or oH   motherboard will resemble a supported box sufficiently closely and canE   thus mimic that system and bootstrap.  (No such family resemblancespF   exist for the XL.)  If you are  exceedingly lucky, somebody here in H   OpenVMS Engineering will have put together a bootstrap kit -- such as H   that for the Multia.  (No Miata-like OpenVMS bootstrap kit exists for 
   the XL.)  < ------------------------------------------------------------G ALPHA16.  Describe Alpha instruction emulation and instruction subsets?a  G   The Alpha architecture is upward- and downward-compatible, and newer eE   instructions are emulated on older platforms, for those cases whereeB   the compiler is explicitly requested to generate the newer Alpha   instructions.u  F   In particular, OpenVMS Alpha V7.1 and later include the instruction C   emulation capabilities necessary for the execution of newer Alpha..   instructions on older Alpha microprocessors.  G   Alpha instructions are available in groups (or subsets).  Obviously, SC   there is the base instruction set that is available on all Alpha -E   microprocessors.   Then, the following are the current instruction -E   extension groups (or subsets) that are available on some of variousf   recent Alpha microprocessors:-       byte/word extension (BWX):-       LDBU, LDWU, SEXTB, SEXTW, STB, and STW.   3     floating-point and square root extension (FIX):-H       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG, SQRTS, and SQRTT.       count extension (CIX):       CTLZ, CTPOP, and  CTTZ.         multi-media extension (MVI):F       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4, MINUB8, MINUW4, +       PERR, PKLB, PKWB, UNPKBL, and UNPKBW.a  H   The typical instruction subset that provides the biggest win -- and ofH   course, your mileage may vary -- is typically the instruction set thatM   is provided by the EV56 and later; specifically, the byte-word instruction /4   subset.  To select this subset, use the following:    -      /ARCHITECTURE=EV56/OPTIMIZE=TUNE=GENERICs    D   The /ARCHITECTURE controls the maximum instruction subset that theF   compiler will generally use, while the /OPTIMIZE=TUNE controls both G   the instruction-level scheduling and also the instructions generated tJ   inside loops -- any code resulting from /OPTIMIZE=TUNE that is specific H   to an instruction subset will be generated only inside loops and will I   also be "protected" by an AMASK-based tesst that permits the execution /E   of the proper code for the particular current Alpha microprocessor..     I   Typically /OPTIMIZE=TUNE=GENERIC is the appropriate choice for tuning,  C   and the /ARCHITECTURE selects the minimum target architecture fork,   general use throughout the generated code.  J   Code generated for later architectures and instruction subsets will run I   on older Alpha systems due to the emulation, but if /ARCHITECTURE is a iI   significant benefit, then the emulation might be a performance penalty.   F   Please see the OpenVMS Ask The Wizard area for the source code of a H   (non-privileged) tool that looks at the instruction subsets available H   on the particular Alpha microprocessor that the tool is run on.  This H   tool demonstrates the use of the Alpha AMASK and IMPLVER instructions.  < ------------------------------------------------------------J ALPHA17.  What is the Accuracy of the Alpha Time of Year (BB_WATCH) Clock?  J   The specification for maximum clock drift in the Alpha hardware clock isL   50 ppm, that's less than +/-.000050 seconds of drift per second, less thanJ   +/-.000050 days of drift per day, or less than +/-.000050 years of driftJ   per year, etc.   (eg: An error of one second over a day-long interval is*   roughly 11ppm, or 1000000/(24*60*60).)    M   The software-maintained system time can drift more, primarily due to other  K   system activity.  Typical causes of drift include extensive high-IPL code K   (soft memory errors, heavy activity at device IPLs, etc) that are causingw7   the processing of the clock interrupts to be blocked.n     Also see VAX8, TIME6.t  < ------------------------------------------------------------3 ALPHA18.  So how do I open up the DEC 3000 chassis?(  @ After removing those two little screws, tilt the back end of the1 top shell upwards -- then you can remove the lid.8  :                                            [Felix Kreisel]  < ------------------------------------------------------------! ALPHA19.  What is byte swizzling?-  F   "Swizzling" is the term used to describe the operation needed to do A   partial word IO on a pre-ev6 system.  It involved shifting the sD   offset into an address space by 5 (or 7 for one older system), andE   ORing this into the base address.  It then required the size of thed/   operation to be ORed into the low order bits.r  G   That is, because EV4 and EV5 did not bring bits 0 and 1 off the chip,oI   to do programmed IO for bytes/words, the information on the size/offsettE   of the transfer was encoded into the address data.  The data itself G   then had to be shifted into the correct "byte lane" (i.e. it's actualc   position within a longword).  F   EV56 (though not EV5) had byte/word operations, but OpenVMS did not D   directly support this for IO.  EV6 systems (with the exception of D   the AlphaServer GS60 and AlphaServer GS140 series, for reasons of G   platform compatability) all support a flat byte addressable IO space.   G   If device driver uses CRAM or IOC$WRITE_IO/IOC$READ_IO, then OpenVMS eF   will do the right thing without changing the driver -- OpenVMS will "   swizzle and unswizzle as needed.  F   To use byte/word operations on MEMORY, you need to tell the compilerD   to use the EV56 or EV6 architecture (/ARCHITECTURE=EV56).  Memory B   operations did not swizzle, but the compiler would do long/quad G   access, and extract/insert bytes as needed.  Using /ARCHITECTURE=EV56fH   allows smaller more efficient byte IO logic to memory.  Beware: a few E   Alpha systems have EV56, but do not support byte/word to I/O space.o  H   If the application is directly doing IO access across a range of AlphaI   systems (like the graphics servers), then the driver will need to know 4K   how to do swizzling for old platforms, and byte access for new platforms. 9                                         [Fred Kleinsorge]t  < ------------------------------------------------------------? ALPHA20.  What commands are available in the Alpha SRM console?   F In addition to the normal BOOT commands and such (see ALPHA11 for someE details) and the normal contents of the console HELP text, operationspG such as I/O redirection and floppy disk access are possible at the SRM u console prompt:s  I 1. Format a FAT floppy, and insert it into the AlphaStation floppy drive.S  6 2. Perform the following at AlphaStation SRM Console :      >>> show * > env.datS    >>> show conf > conf.datP%    >>> cat env.dat > fat:env.dat/dva0-'    >>> cat conf.dat > fat:conf.dat/dva0W  B 3. You may use the SRM "ls" to display the contents of the floppy.      >>> ls fat:env.dat/dva0    >>> ls fat:conf.dat/dva0n  @ 4. You can now transfer the FAT-format floppy to another system.  < ------------------------------------------------------------@ ALPHA21. How do I switch between AlphaBIOS/ARC and SRM consoles?  G The specific steps required vary by system.  You must first ensure thataG the particular Alpha system is supported by OpenVMS (see the SPD), thatuG all core I/O components (graphics, disk controllers, etc) in the system D are supported by OpenVMS (see the SPD), and that you have an OpenVMSG distribution, that you have the necessary license keys (PAKs), and that + you have the necessary SRM firmware loaded.u  F A typical sequence used for switching over from the AlphaBIOS graphics# console to the SRM console follows:i  3   1. Press <F2> to get to the AlphaBIOS setup menu.7  #   2. Pick the "CMOS Setup..." item.e  9   3. Press <F6> to get to the "Advanced CMOS Setup" menu.d  ?   4. Change the "Console Selection" to "OpenVMS Console (SRM)".   ;   5. Press <F10>, <F10>, then <Enter> to save your changes.l     6. Power-cycle the system.  I Most Alpha systems support loading both the AlphaBIOS/ARC console and thepF SRM console at the same time, but systems such as the AlphaStation 255D are "half-flash" systems and do not support the presence of both theE AlphaBIOS/ARC and SRM console firmware at the same time.  If you have-G a "half-flash" system, you must load the SRM firmware from floppy, from D a network download, or from a firmware CD-ROM.  Following the normalE AlphaBIOS or ARC firmware update sequence to the APU prompt, and thenoB explictly select the target console.  In other words, power up theE system to the AlphaBIOS or ARC console, use the supplementary options/C to select the installation of new firmware (typically from CD-ROM),/? and then rather than using a sequence which updates the currentf	 firmware:m       Apu-> update
       -or-     Apu-> update ARC     Apu-> verify     Apu-> quit     Power-cycle the system  @ Use the following sequence to specifically update (and load) SRM, from AlphaBIOS/ARC on a "half-flash" system:       Apu-> update SRM     Apu-> verify     Apu-> quit     Power-cycle the system  @ Use the following sequence to specifically update (and load) the8 AlphaBIOS/ARC console from SRM on a "half-flash" system:       >>> b -fl 0,A0 ddcur$     BOOTFILE: firmware_boot_file.exe       Apu-> update ARC     Apu-> verify     Apu-> quit     Power-cycle the system  A Once you have the SRM loaded, you can directly install OpenVMS ora= Tru64 UNIX on the system.  Do not allow Windows NT to write ah@ "harmless" signature to any disk used by OpenVMS, Tru64 UNIX, orA Linux, as this will clobber a key part of the disk.  (On OpenVMS,oB you can generally recover from this "harmless" action by using the WRITEBOOT tool.)  D If you have a "full-flash" system and want to select the SRM consoleD from the AlphaBIOS or ARC console environment, select the "Switch toI OpenVMS or Tru64 UNIX console" item from the "set up the system" submenu. D Then power-cycle the system.  If you have a "full-flash" system withB the SRM console and want to select AlphaBIOS/ARC, use the command:      >>> set os_type NTI   and power-cycle the system.s  C For information on acquiring firmware, see ALPHA6.  For informationrE on OpenVMS license PAKs (for hobbyist use) see VMS9.  For informationr on the Multia, see ALPHA8.  C Information on enabling and using the failsafe firmware loader for oE various systems -- this tool is available only on some of the varioussF Alpha platforms -- is available in the hardware documentation for the G system.  This tool is used/needed when the firmware has been corrupted,P and cannot load new firmware.D  < ------------------------------------------------------------@ ALPHA22.  OpenVMS on the Personal Workstation -a and -au series?  F Though OpenVMS is not supported on the Personal Workstation -a series F platforms, OpenVMS might or might not bootstrap on the platform.  (If H you attempt this, you must ensure that all graphics and I/O controllers ( in the system are supported by OpenVMS.)  < ------------------------------------------------------------9 ALPHA23.  OpenVMS and Personal Workstation IDE bootstrap?b  C OpenVMS will boot and is supported on the Personal Workstation -au  C series platforms, though OpenVMS will require a SCSI CD-ROM if the -C Intel Saturn I/O (SIO) IDE chip is present in the configuration -- tE only the Cypress IDE controller chip is supported by OpenVMS for IDE e bootstraps.n  = If you have an -au series system, you can determine which IDEh, chip you have using the SRM console command:     SHOW CONFIGURATION  B If you see "Cypress PCI Peripheral Controller", you can bootstrap A OpenVMS from IDE storage.  If you see "Intel SIO 82378", you will C need to use and bootstrap from SCSI.  (A procedure to load DQDRIVERb@ on the Intel SIO -- once the system has bootstrapped from a SCSIC device -- is expected to be included as part of the contents of ther/ DQDRIVER directory on Freeware V5.0 and later.)   < ------------------------------------------------------------B ALPHA24.  Which terminal device name is assigned to the COM ports?  >   COM2 is normally TTA0:.  COM1 is normally TTB0: if the AlphaA   workstation is booted with the SRM console environment variableB@   set to graphics, and is OPA0: if the console is set to serial.  < ------------------------------------------------------------8 VAX1.   Please explain the back panel of the MicroVAX II  J The MicroVAX-series console bulkhead was used with the KA630, KA650, KA655 processors.-  B There are three controls on the console bulkhead of these systems:  *   Triangle-in-circle-paddle: halt enable. -     dot-in-circle: halt (<break>) is enabled, -                    and auto-boot is disabled.r2     dot-not-in-circle: halt (<break>) is disabled,,                    and auto-boot is enabled.  5   Three-position-rotary: power-up bootstrap behaviourd     arrow: normal operation.      face: language inquiry mode.)     t-in-circle: infinite self-test loop.-  4   Eight-position-rotary: console baud rate selection4     select the required baud rate; read at power-up.  iJ There are several different bulkheads involved, including one for the BA23E and BA123 enclosures, and one for the S-box (BA2xx) series enclosure. L The console bulkheads typically used either the MMJ serial line connection, H or the MicroVAX DB9 (not the PC DB9 pinout), please see the descriptions> of these in section MISC1.  For available adapters, see MISC4.  M Also present on the console bulkhead is a self-test indicator: a single-digiteK LED display. This matches the final part of the countdown displayed on the uN console or workstation, and can be used by a service organization to determineM the nature of a processor problem.  The particular countdown sequence varies  M by processor type, consult the hardware or owner's manual for the processor,  G or contact the local hardware service organization for information the mM self-test sequence for a particular processor module. Note that self-tests 2,eM 1 and 0 are associated with the transfer of control from the console program e" to the (booting) operating system.9                                         [Stephen Hoffman]P  < ------------------------------------------------------------< VAX2.   What is the layout of the VAX floating point format?  K The VAX floating point format is derived from one of the PDP-11 FP formats, H which helps explain its strange layout.  There are four formats defined:H F 32-bit single-precision, D and G 64-bit double-precision and H 128-bitI quadruple precision.  For all formats, the lowest addressed 16-bit "word"lF contains the sign and exponent (and for other than H, some of the mostK significant fraction bits).  Each successive higher-addressed word containsaN the next 16 lesser-significant fraction bits.  Bit 15 of the first word is theF sign, 1 for negative, 0 for positive.  Zero is represented by a biasedM exponent value of zero and a sign of zero; the fraction bits are ignored (but-J on Alpha, non-zero fraction bits in a zero value cause an error.)  A valueK with biased exponent zero and sign bit 1 is a "reserved operand" - touchingtI it causes an error - fraction bits are ignored.  There are no minus zero,c% infinity, denormalized or NaN values.e  M For all formats, the fraction is normalized and the radix point assumed to be J to the left of the MSB, hence 0.5 <= f < 1.0.  The MSB, always being 1, isK not stored.  The binary exponent is stored with a bias varying with type ino' bits 14:n of the lowest-addressed word.-  L   Type    Exponent bits    Exponent bias    Fraction bits (including hidden)L   ==========================================================================4    F           8                128               244    D           8                128               564    G          11               1024               534    H          15              16384              113  D The layout for D is identical to that for F except for 32 additional fraction bits.  J Example:  +1.5 in F float is hex 000040C0 (fraction of .11[base 2], biased exponent of 129) 					[Steve Lionel]k  < ------------------------------------------------------------5 VAX3.   Where can I find more info about VAX systems?a  " Compaq runs a VAX "InfoCenter" at:  (   http://www.compaq.com/alphaserver/vax/  1 Jim Agnew maintains a MicroVAX/VAXstation FAQ at:m  3   http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmle  , James Lothian maintains a VAX-11/750 FAQ at:  3   http://www.dcs.napier.ac.uk/~oose5002/750faq.htmlo  " The VAXstation 3100 Owner's Guide:  7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmle  ; A field guide to PDP-11 (and VAX) Q-bus and UNIBUS modules   can be found at:  8   http://metalab.unc.edu//pub/academic/computer-science/+     history/pdp-11/hardware/field-guide.txts  9 Various VAX historical information (also see VMS1) can bee	 found at:w  +   http://telnet.hu/hamster/vax/e_index.htmlO  < ------------------------------------------------------------? VAX4.   Where can I find information on NetBSD for VAX systems?t  / Gunnar Helliesen maintains a NetBSD VAX FAQ at:    http://vaxine.bitcon.no/  < ------------------------------------------------------------H VAX5.   What system disk size limit on the MicroVAX and VAXstation 3100?  M System disks larger than 1.073 gigabytes (GB) -- 1fffff hexidecimal blocks --eL are not supported on any member of the VAXstation 3100 series and on certainH older members of the MicroVAX 3100 series, and are not reliable on theseJ affected systems.  (See below to identify the affected systems -- the moreE recent members of the MicroVAX 3100 series systems are NOT affected.)   M Various of the SCSI commands used by the boot drivers imbedded in the console I PROM on all members of the VAXstation 3100 series use "Group 0" commands,RI which allow a 21 bit block number field, which allows access to the first J 1fffff hexidecimal blocks of a disk.  Any disk references past 1fffff willL wrap -- this wrapping behaviour can be of particular interest when writing aN system crashdump file, as this can potentially lead to system disk corruptionsA should any part of the crashdump file be located beyond 1.073 GB.   N More recent systems and console PROMs use "Group 1" SCSI commands, which allow a 32 bit block number field.  L There was a similar limitation among the oldest of the MicroVAX 3100 series,M but a console boot PROM was phased into production and was made available fortI field retrofits -- this PROM upgrade allows the use of the "Group 1" SCSIlN commands, and thus larger system disks.  There was no similar PROM upgrade for the VAXstation 3100 series.o  ( Systems that are affected by this limit:G   o VAXstation 3100 series, all members.  No PROM upgrade is available.iB   o MicroVAX 3100 models 10 and 20.  No PROM upgrade is available.E   o MicroVAX 3100 models 10e and 20e.  Only systems with console VMB oB     versions prior to V6.4 are affected.  A PROM upgrade for these-     specific systems is (was once) available.o  	 Also see:C7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmlo   Also see FILE5.m 						[Stephen Hoffman]e  < ------------------------------------------------------------  VAX6.  replaced by TIME section.  < ------------------------------------------------------------) VAX7.  What are the VMB boot flag values?T  ? The following flags are passed (via register R5) to the OpenVMSs> VAX primary bootstrap image VMB.EXE.  These flags control the & particular behaviour of the bootstrap:  > The exact syntax is console-specific, recent VAX consoles tend to use the following:r     >>> BOOT/R5:flagsr  @   Bit     Meaning                                               @   ---     -------                                               N                                                                               @    0      RPB$V_CONV                                            @           Conversational boot. At various points in the         @           system boot procedure, the bootstrap code             @           solicits parameter and other input from the           @           console terminal.  If the DIAG is also on then        @           the diagnostic supervisor should enter "MENU"         @           mode and prompt user for the devices to test.           @    1      RPB$V_DEBUG                                           @           Debug.  If this flag is set, VMS maps the code        @           for the XDELTA debugger into the system page          @           tables of the running system.                         @                                                                 @    2      RPB$V_INIBPT                                          @           Initial breakpoint. If RPB$V_DEBUG is set, VMS        @           executes a BPT instruction immediately after          @           enabling mapping.                                     ?                                                                i@    3      RPB$V_BBLOCK                                          @           Secondary boot from the boot block.  Secondary        @           bootstrap is a single 512-byte block, whose LBN       @           is specified in R4.                                   @                                                                 @    4      RPB$V_DIAG                                            @           Diagnostic boot.  Secondary bootstrap is image        @           called [SYSMAINT]DIAGBOOT.EXE.                        @                                                                 @    5      RPB$V_BOOBPT                                          @           Bootstrap breakpoint. Stops the primary and           @           secondary bootstraps with a breakpoint                @           instruction before testing memory.                      @    6      RPB$V_HEADER                                          @           Image header. Takes the transfer address of the       @           secondary bootstrap image from that file's            @           image header.  If RPB$V_HEADER is not set,            @           transfers control to the first byte of the            @           secondary boot file.                                  @                                                                 @    7      RPB$V_NOTEST                                          @           Memory test inhibit. Sets a bit in the PFN bit        @           map for each page of memory present.  Does not        @           test the memory.                                      @                                                                 @    8      RPB$V_SOLICT                                          @           File name. VMB prompts for the name of a              @           secondary bootstrap file.                             @                                                                 @    9      RPB$V_HALT                                            @           Halt before transfer.  Executes a HALT                @           instruction before transferring control               @           to the secondary bootstrap.                           @                                                                 @   10      RPB$V_NOPFND                                          @           No PFN deletion (not implemented; intended to         @           tell VMB not to read a file from the boot device      @           that identifies bad or reserved memory pages,         @           so that VMB does not mark these pages as valid        @           in the PFN bitmap).                                   @                                                                 @   11      RPB$V_MPM                                             @           Specifies that multi-port memory is to be used        @           for the total EXEC memory requirement.  No local      @           memory is to be used.  This is for tightly-coupled    @           multi-processing.  If the DIAG is also on, then       @           the diagnostic supervisor enters "AUTOTEST" mode.     @                                                                 @   12      RPB$V_USEMPM                                          @           Specifies that multi-port memory should be used in    @           addition to local memory, as though both were one     @           single pool of pages.                                 @                                                                 @   13      RPB$V_MEMTEST                                         @           Specifies that a more extensive algorithm be used     @           when testing main memory for hardware                 @           uncorrectable (RDS) errors.                           @                                                                 @   14      RPB$V_FINDMEM                                         @           Requests use of MA780 memory if MS780 is              @           insufficient for booting.  Used for 11/782            @           installations.                                        @                                                                 @   <31:28> RPB$V_TOPSYS                                          @           Specifies the top level directory number for          @           system disks with multiple systems.                     l< ------------------------------------------------------------A VAX8.   What is the Accuracy of VAX the Time of Year (TOY) Clock?t  A   The VAX Time-Of-Year (TOY) clock (used to save the time over a oA   reboot or power failure) is specified as having an accuracy of  ;   .0025%.  This is a drift of roughly 65 seconds per month.i  C   The VAX Interval Time is used to keep the running time, and this  F   has a specified accuracy of .01%.  This is a drift of approximately    8.64 seconds per day.t  E   Any high-IPL activity can interfere with the IPL 22 or IPL 24 (this D   depends on the VAX implementation) clock interrupts -- activities B   such as extensive device driver interrupts or memory errors are    known to slow the clock.     Also see ALPHA17, TIME6.  < ------------------------------------------------------------> VAX9.   Which serial port is the console on the MicroVAX 3100?  G Just to keep life interesting, the MicroVAX 3100 has some "interesting"sA console ports behaviours based on the setting of the BREAK enableaC switch.  When the console is not enabled to respond to BREAK, MMJ-1ID is the console port.  MMJ-3 will (confusingly) output the results ofC the selftest in parallel with MMJ-1. When the console is enabled toy@ respond to BREAK, MMJ-3 becomes the console port, and MMJ-1 willD (confusingly) output the results of selftest in parallel with MMJ-3.  < ------------------------------------------------------------> VAX10.  How can I set up an alternate console on a VAXstation?  A Most VAXstation systems have a switch -- often labeled S3 -- that 6 enables one of the serial lines as the system console.  $ Also see ALPHA1, DECW13, and MGMT22.  < ------------------------------------------------------------/ VAX11.  What are the VAX processor (CPU) codes?u      CPU:    Platform:    -----   ---------)    KA41-A : MicroVAX 3100 Model 10 and 20t*    KA41-B : VAXserver 3100 Model 10 and 20    KA41-C : InfoServer+    KA41-D : MicroVAX 3100 Model 10e and 20es,    KA41-E : VAXserver 3100 Model 10e and 20e+    KA42-A : VAXstation 3100 Model 30 and 40-+    KA42-B : VAXstation 3100 Model 38 and 48n$    KA43-A : VAXstation 3100 Model 76)    KA45   : MicroVAX 3100 Model 30 and 40n$    KA46   : VAXstation 4000 Model 60"    KA47   : MicroVAX 3100 Model 80    KA48   : VAXstation 4000 VLCi(    KA49-A : VAXstation 4000 Model 90/90A$    KA49-B : VAXstation 4000 Model 95$    KA49-C : VAXstation 4000 Model 96"    KA50   : MicroVAX 3100 Model 90"    KA51   : MicroVAX 3100 Model 95    KA52   : VAX 4000 Model 100    KA53   : VAX 4000 Model 105    KA54   : VAX 4000 Model 106"    KA55   : MicroVAX 3100 Model 85"    KA56   : MicroVAX 3100 Model 96    KA57   : VAX 4000 Model 108"    KA58   : MicroVAX 3100 Model 88"    KA59   : MicroVAX 3100 Model 98    KA85   : VAX 8500    KA86   : VAX 8600    KA88   : VAX 8800&    KA600  : VAX 4000-50 (aka VAXbrick)/    KA610  : MicroVAX I, VAXstation I (aka KD32)r    KA620  : rtVAX (VAXeln)    KA62A  : VAX 6000-200    KA62B  : VAX 6000-300&    KA630  : MicroVAX II, VAXstation II(    KA640  : MicroVAX 3300, MicroVAX 3400G    KA650  : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX III     KA64A  : VAX 6000-4007    KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III+c    KA65A  : VAX 6000-500'    KA660  : VAX 4000-200, VAX 4 upgrade-    KA66A  : VAX 6000-600    KA670  : VAX 4000-300    KA675  : VAX 4000-400    KA680  : VAX 4000-500    KA681  : VAX 4000-500Al    KA690  : VAX 4000-600    KA691  : VAX 4000-605Ac    KA692  : VAX 4000-700A     KA693  : VAX 4000-605Ak    KA694  : VAX 4000-705A     KA730  : VAX-11/730    KA750  : VAX-11/750"    KA780  : VAX-11/780, VAX-11/782    KA785  : VAX-11/785    KA7AA  : VAX 7000-600    KA7AB  : VAX 7000-700    KA7AC  : VAX 7000-800    KA800  : VAXrta    KA820  : VAX 8200, VAX 8300    KA825  : VAX 8250, VAX 8350    KA865  : VAX 86506                                      [Antonio Carlini]  < ------------------------------------------------------------B SUPP1.  Where can I get software and hardware support information?  D Contact Compaq Customer Support.  Services and information, manuals,A guides, downloads, and various other information is available at:n      http://www.compaq.com/support/  : Various hardware and system documentation is available at:  ?   http://www.compaq.com/support/techpubs/user_reference_guides/,1   http://www.adenzel.demon.nl/vaxes/microvax3100/I2   http://www.adenzel.demon.nl/vaxes/infoserver150/  < ------------------------------------------------------------E SUPP2.  Where can I get hardware self-maintenance support assistance?a  C The Compaq Assisted Services program is available to customers thatnH wish to maintain their own systems (self-maintenance), but that require F some assistance with acquiring hardware diagnostics, hardware manuals,# and with hardware swaps and spares:r  %   http://www.digital.com/info/DAHOME/i%   http://www.digital.com/DAS-Catalog/   < ------------------------------------------------------------G SUPP3. Why does my system halt when I power-cycle the console terminal?e  <   Various VAX and Alpha consoles are designed to process the.   BREAK signal, treating it as a HALT request.  @   A BREAK is a deliberately-generated serial line framing error.  F   When a serial line device such as a terminal powers up (or sometimesD   when powering down) it can generate framing errors.  These framing2   errors are indistingushable from a BREAK signal.  ?   When a BREAK is received on a serial line console for variousiB   VAX systems -- including most VAXstation, MicroVAX, and VAX 4000A   series -- it is typically interpreted as a HALT.  Alpha systemstC   will also often process a BREAK in a similar fashion, halting thes	   system.-  @   There is no uniform or generally-available way to disable thisA   behaviour on every VAX or Alpha system.  On some systems, BREAKoA   processing can be disabled in favor of [CTRL/P], or [CTRL/P] isd%   the only way to halt the processor.i  C   The most common way to avoid these halts is to disable the serial A   line console or to simply not power-cycle the console terminal.sG   There is certain important system state information that is displayeddC   only on the console, OpenVMS expects to always have access to the    system console.t     Also see MGMT5.i  < ------------------------------------------------------------? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?T  F Older Compaq keyboards (those with the DIGITAL logo and the RJ modularF jacks), older Compaq mice (those with the DIGITAL logo and with the RJI modular jacks, or with a DIN connector with pins in a configuration other=D than the PC-standard DIN connector pin orientation), and older videoD monitors (with RGB synch-on-green video signaling) all use signalingJ formats and/or communications protocols that differ from the PC standards,H and are not (easily) interchangable nor (easily) compatible with typicalK PC peripheral device controllers.  LK201, LK401, VSXXX, VR260, VR290, etc., & are incompatible with most PC systems.  F Newer Compaq keyboards (those with with PC-style DIN plugs, and CompaqF or DIGITAL logo), newer Compaq mice (with PC-pin DIN plugs, and CompaqB or DIGITAL logo), and newer video monitors (multi-synch) are oftenE interchangeable with "industry standard" PC systems, and can often berH used with most PC peripheral device controllers. LK461, LK471, PC7XS-CA,8 VRC16, VRC21, etc., are compatible with most PC systems.  K Rule of thumb: if the peripheral device component was sold for use with theeK DEC 2000 (DECpc 150 AXP), an AlphaServer series, an AlphaStation series, oriE more recent Alpha system, it will probably  work with a PC peripheralaH controller.  If the peripheral device component was sold for use with anJ VT420 or older terminal, most VAX, most VAXstation, and most Alpha systemsJ with names in the format `DEC <four-digit-number>', it probably won't work on a PC.  N Note that the above is a general guideline, and should not be read to indicateM that any particular peripheral device will or will not work in any particularSN configuration, save for those specific configurations the device is explicitly
 supported in.-9                                         [Stephen Hoffman]o    K Software Integrators sells a video adapter card called Gemini P1 which willfI drive many of the older Compaq (DIGITAL-logo) fixed-frequency monitors on  a PC system:     http://www.si87.com/    J The Digital part number 29-32540-01 converts the output from the RGB cableJ (3 BNC, synch-on-green) that comes with the VAXstation 3100 and VAXstation) 4000 series to a female SVGA D connector.f  ? This will allow PC Multisync monitors with the needed frequencymC specifications to be used with the VAXstations.  It may work with ar> VAXstation 2000 series, but I have not tried that combination.<                                           [John E. Malmberg]  I The protocol definition for the old DIGITAL keyboard and mouse interfaces J is buried at the back of the QDSS section in the old VAXstation II manual,G specifically, in the back of the VCB02 Video Subsystem Technical ManualrF (EK-104AA-TM).  The keyboard wiring and protocol is in appendix B, andE occupies circa 44 pages.  The mouse is in appendix C, circa 12 pages.t     Also see SUPP5  < ------------------------------------------------------------A SUPP5.  Which video monitor works with which graphics controller?n  K   To determine the answer to the "will this monitor work with this graphicssF   controller?" question, please first locate the resolution(s) and theI   frequencies that are possible/supported at both ends of the video cablehH   (on the monitor and the graphics controller, in other words), and thenG   determine if there are any matching settings available.  If there areRL   multiple matches, you will need to determine which one is most appropriate   for your needs.   M   You will also need to determine if the video monitor or graphics controllersL   requires the 3 BNC signaling with the synchronization signals on the greenM   wire, or the 5 BNC signalling common on many PCs, or other connections such-G   as the DB15 video connector or USB connector used on various systems.   I   If there are no matches, you will likely need to change the hardware at-(   one or both ends of the "video cable".  J   The refresh frequencies for many devices have been posted to comp.os.vmsG   and/or other newsgroups.  Search the archives for details.  Also see:h       http://www.repairfaq.org/x<     http://plop.phys.cwru.edu/repairfaq/REPAIR/F_monfaq.html"     http://www.mirage-mmc.com/faq/H     http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html2     http://saturn.tlug.org/sunstuff/ffmonitor.html     Also see SUPP4.   < ------------------------------------------------------------8 SUPP6.  Where can I get information on storage hardware?  < Information on various Compaq OpenVMS and other disk storage; hardware and controllers, and related technical informations/ on SCSI, device jumpers, etc., is available at:t     http://theref.aquascape.com/  < ------------------------------------------------------------< SUPP7.  Problem - My LK401 keyboard unexpectedly autorepeats  # There are several modes of failure:s  K a) Pressing 2 and 3 keys at the same time causes one key to autorepeat when L    released.  Check the hardware revision level printed on the bottom of theL    keyboard.  If the revision level is C01, the keyboard firmware is broken.K    Call field service to replace the keyboard with any revision level other     than C01.  I b) Pressing certain keys is always broken.  Typical sympypoms are: delete N    always causes a autorepeat, return needs to be pressed twice, etc.  This isI    frequently caused by having keys depressed while the keyboard is being L    initialized.  Pressing ^F2 several times or unplugging and replugging theK    keyboard frequently fix this problem.  There is a patch available to fixBJ    this problem [contact the CSC for information - a CSCPAT number will be'    included here when available. - Ed.]   L c) A key that was working spontaneously stops working correctly. This may beN    either (a) or (b) or it may be bad firmware.  Ensure that you have the mostI    recent firmware installed on your CPU.  An old version of the DEC 3000 4    firmware had a bug that could cause this symptom.9                                         [Fred Kleinsorge]I  < ------------------------------------------------------------I SUPP8.  Problem - My LK411 sends the wrong keycodes or some keys are dead   N Check the firmware revision on the keyboard.  Hardware revision B01 introducedM an incompatability with the device driver which causes the keyboard to not be F recognized correctly.  There is a patch available to fix this problem:H [AXPDRIV06_061] - the fix is also included in OpenVMS V6.2.  The rev A015 keyboard, and the LK450 should work without problems. 9                                         [Fred Kleinsorge] 1                                         [inazu_k]   < ------------------------------------------------------------< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?  3   Both of these controllers are Ultra2 low-voltage  &   differential (LVD) SCSI controllers.  < ------------------------------------------------------------, SCSI2.  Resolving DRVERR fatal device error?  >   If this is on an OpenVMS version prior to V6.2, see the AWRE1   and ARRE information included in section FILE5.   < ------------------------------------------------------------- WIRES1. Looking for connector wiring pinouts?P   DECconnect DEC-423 MMJ pinout:     1: Data Terminal Ready (DTR)   2: Transmit (TXD)r   3: Transmit Ground (TXD-)    4: Receive Ground (RXD-)   5: Receive (RXD)   6: Data Set Ready (DSR)       +------------------+     | 1  2  3  4  5  6 |     +------------+    ++                  +____+    / The PC-compatible DB9 connector pinout follows:e     1: Data Carrier Detect (DCD)   2: Received Data   3: Transmit Data   4: Data Terminal Ready (DTR)   5: Grounda   6: Data Set Ready (DSR)    7: Request To Send (RTS)   8: Clear To Send
   9: floating   C The MicroVAX DB9 console connector pinout predates the PC-style DB9 D pinout, and uses a then-common (older) standard pinout, and uses the# following EIA-232-standard signals:a     1: Protective Ground   2: Transmited Data   3: Received Data   4: Request To Send (RTS)   5: Data Terminal Ready (DTR)   6: Data Set Ready (DSR)d   7: Signal Ground8   8: Shorted to pin 9 on MicroVAX and VAXstation 2000...3   9:    ...series systems, otherwise left floating.     = The BC16E-nn (where -nn indicates the cable length) cable key < impliicitly "flips over" (crosses-over) the signal wires, so1 all DECconnect MMJ connectors are wired the same.u  
            //l:            ----                                       ----:            |  |---------------------------------------|  |:            ----                                       ----:                                                         \\  0 The BC16-E-nn cross-over wiring looks like this:  ;             Terminal                                   Hoste:             MMJ                                        MMJ  =          DTR 1 --->-------------->----------------->--- 6 DSRi=          TXD 2 --->-------------->----------------->--- 5 RXD 9              3 ---------------------------------------- 439              4 ---------------------------------------- 3 =          RXD 5 ---<--------------<-----------------<--- 2 TXD =          DSR 6 ---<--------------<-----------------<--- 1 DTR      The BN24H looks like this:            MMJ       RJ45              1---------8            2---------2            3---------1            4---------3D           5---------6            6---------7    The BN24J looks like this:            MMJ       RJ45              1---------7e           2---------6o           3---------3            4---------1            5---------2            6---------8   	 Also see:   M  http://www.partner.compaq.com:9003/public/cheat_sheets/cables/padapters.html %  http://www.airborn.com.au/rs232.htmlp(  For adapters and connectors, see MISC4.  9                                         [Stephen Hoffman] 7                                         [Mike Thompson]-6                                         [William Webb]  < ------------------------------------------------------------: WIRES2. What connectors and wiring adapters are available?    J The H8571-B converts the (non-2000-series) MicroVAX DB9 to MMJ DECconnect.G The MicroVAX 2000 and VAXstation 2000 requires a BCC08 cable (which has 7 the 8-9 short) and the H8571-D for use with DECconnect.o  G More recent Compaq (Compaq or DIGITAL logo) systems will use either thenI DECconnect MMJ wiring or (on all recent system designs) the PC-compatibled DB9 pinout.i   DECconnect MMJ adapters:  3     Part:      Converts BC16E MMJ male to fit into:n  2     H8571-C  25 pin DSUB Female to MMJ, Unfiltered.     H8571-D  EIA232 25 pin male (modem-wired) 0     H8571-E  25 pin DSUB Female to MMJ, Filtered/     H8571-J  PC/AT 9 pin male (PC serial port)  4     H8572-0  BC16E MMJ double-female (MMJ extender) +     H8575-A  EIA232 25 pin female (common)  5     H8575-B  EIA232 9 pin male (MicroVAX II console) l4     H8575-D  25 Pin to MMJ W/EOS and ESD Protection *     H8577-AA 6 pin Female MMJ to 8 pin MJ 4     BC16E-** MMJ cable, available in various lengths    D Numerous additional adapters and cables are available from the _OPENK DECconnect Building Wiring Components and Applications Catalog_, as well ase' descriptions of the above-listed parts.-  J The H8571-A and H8575-A are MMJ to DB25 (female) and are wired as follows:  	 Also see:p4  http://www.openvms.compaq.com/wizard/padapters.html  L Jameco offers a USB-A to PS/2 Mini DIN 6 Adapter (as part 168751), for thoseC folks wishing to (try to) use PS/2 Keyboards via USB-A connections..  " For wiring and pinouts, see MISC4.9                                         [Stephen Hoffman]s6                                         [Eric Dittman]  < ------------------------------------------------------------2 WIRES3. What is flow control and how does it work?  % XON/XOFF is one kind of flow control.n  B In ASCII, XON is the [CTRL/Q] character, and XOFF is the [CTRL/S].  F XON/XOFF flow control is typically associated with asynchronous serialG line communications.  XON/XOFF is an in-band flow control, meaning that0+ the flow control is mixed in with the data.0  I CTS/RTS is another type of flow control, and is sometimes called hardware4G flow control.  Out-of-band means that seperate lines/pins from the data 3 lines (pins) are used to carry the CTS/RTS signals.r  G Both kinds of flow control are triggered when a threshold is reached in0J the incoming buffer.  The flow control is suppose to reach the transmitterG in time to have it stop transmitting before the receiver buffer is full E and data is lost.  Later, after a sufficient amount of the receiver's5E buffer is freed up, the resume flow control signal is sent to get the0 transmitter going again.  F DECnet Phase IV on OpenVMS VAX supports the use of asynchronous serialI communications as a network line.  The communication devices (eg. modems,BE and drivers) *must not* be configured for XON/XOFF flow control.  TheiD incidence of these (unexpected) in-band characters will corrupt dataG packets.  Further, the serial line device drivers might normally removerF the XON and XOFF characters from the stream for terminal applications,E but DECnet configures the driver to pass *all* characters through and0F requires that all characters be permitted.  (The communication devicesF must pass through not only the XON and XOFF characters, they must passE *all* characters including the 8-bit characters.  If data compression4G is happening, it must reproduce the source stream exactly.  No addition7> or elimination of null characters, and full data transparency.  I An Ethernet network is rather different than an asynchronous serial line. E Ethernet specifies the control of data flow on a shared segment using0B CSMA/CD (Carrier Sense Multiple Access, with Collision Detect)  AnF Ethernet station that is ready to transmit listens for a clear channelK (Carrier Sense).  When the channel is clear, the station begins to transmittJ by asserting a carrier and encoding the packet appropriately.  The stationG concurrently listens to its own signal, to permit the station to detectcG if another station began to transmit at the same time -- this is calledbJ collision detection.  (The collision corrupts the signal in a way that canH reliably be detected.)  Upon detecting the collision, both stations willB stop transmitting, and will back off and try again a little later.H (You can see a log of this activity in the DECnet NCP network counters.)  G DECnet provides its own flow control, above and beyond the flow control I of the physical layer (if any).  The end nodes handshake at the beginningbG to establish a transmit window size -- and a transmitter will only sendrG that much data before stopping and waiting for an acknowledgement.  ThetG acknowledgement is only sent when the receiver has confirmed the packet-D is valid.  (A well-configured DECnet generally avoids triggering any1 underlying (out-of-band) flow control mechanism.)l=                                                [David Rabahy]t   [End of Part 5/5]r  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 29 Dec 2000 21:10:38 GMTf( From: merritt.robert@sbe.saskatoon.sk.ca' Subject: OSU ssh compilation problem???e) Message-ID: <92iuk8$vtf$1@nnrp1.deja.com>    I have   -openssl 093  $ -vms 7.1-2 on a alpha 2000 model 300  7 -DIGITAL TCP/IP Services for OpenVMS Alpha Version V4.2 0   on a DEC 2000 Model 300 running OpenVMS V7.1-2  ' -DEC C V6.0-001 on OpenVMS Alpha V7.1-2   / I am trying to compile the OSU SSH server using  @build_ssh_servera or mmk ally   the error I get is:O   $ @BUILD_SSH_SERVER.COM;1c/ $ is_cmd_proc = (f$environment("DEPTH") .gt. 0)C* $ if is_cmd_proc then sv_vfy = f$verify(1)' $ if is_cmd_proc then @ssl_location.comt> %DCL-I-SUPERSEDE, previous value of SSLLIB has been superseded> %DCL-I-SUPERSEDE, previous value of SSLINC has been superseded	 $ exit 01e3 $ if f$trnlnm("ssllib") .eqs. "" then define ssllib 7 soft:[network.http.ssleay.openssl-0_9_4.axp.exe.crypto] ? $ if f$trnlnm("sslinc") .eqs. "" then define sslinc sslinclude:-' $ is_axp = (f$getsyi("CPU") .ge. "128")P? $ if is_axp .or. f$trnlnm("DECC$CC_DEFAULT") .eqs. "/DECC" thenl* define/nolog pthread_libs pthread_libs_axpE $ if is_axp .and. f$search("sys$share:pthread$rtl.exe") .nes. "" thenI) define/nolog pthread_libs pthread_libs_v7 E $ if is_axp .and. f$search("sys$share:pthread$rtl.exe") .nes. "" thent0 kt_enable = "/THREADS_ENABLE=(UPCALLS,MULTIPLE)" $ show translation ssllibn:   SSLLIB = "DKA0:[OPENSSL.ALPHA_LIB]"  (LNM$PROCESS_TABLE) $ show translation sslinc 8   SSLINC = "DKA0:[OPENSSL.INCLUDE]"  (LNM$PROCESS_TABLE)< $ if f$trnlnm("pthread_libs") .nes. "" then show translation pthread_libs7   PTHREAD_LIBS = "PTHREAD_LIBS_V7"  (LNM$PROCESS_TABLE) + $ IF F$GETSYI("CPU") .GE. 128 .OR. F$TRNLNMo! ("DECC$CC_DEFAULT") .EQS. "/DECC"s THEN prefix_all = "/prefix=all"GH $ cc /NOLIST/OBJECT=SSHRSA_RPC.OBJ sshrsa_rpc/include=sslinc /prefix=all  @     new = RSA_generate_key(bits, e, (openssl_cb) callback, "" );% ....................................^tH %CC-W-PTRMISMATCH, In this statement, the referenced type of the pointer; value "(openssl_cb)callback" is "function (int, int, pointetH r to void) returning void", which is not compatible with "function (int,& int, pointer to char) returning void".@ at line number 225 in file DKA0:[SSHANDSSL.VMSSSH]SSHRSA_RPC.C;1  =     result = PEM_read_RSAPrivateKey ( kf, &key, NULL, NULL );a .............^H %CC-E-TOOMANYARGS, In this statement, "PEM_read_RSAPrivateKey" expects 3 arguments, but 4 are supplied.@ at line number 360 in file DKA0:[SSHANDSSL.VMSSSH]SSHRSA_RPC.C;1  D     status = PEM_write_RSAPrivateKey ( kf, key, NULL, NULL, 0, NULL, NULL );n .............^G %CC-E-TOOMANYARGS, In this statement, "PEM_write_RSAPrivateKey" expects  6l arguments, but 7 are supplied.@ at line number 391 in file DKA0:[SSHANDSSL.VMSSSH]SSHRSA_RPC.C;1  D             reply->key_id = PEM_read_RSAPrivateKey ( kf, &key, NULL, NULL );h ............................^gH %CC-E-TOOMANYARGS, In this statement, "PEM_read_RSAPrivateKey" expects 3 arguments, but 4 are supplied.@ at line number 775 in file DKA0:[SSHANDSSL.VMSSSH]SSHRSA_RPC.C;1 $o    5 any ideas what I might have mised (flags switches???)t     Sent via Deja.com  http://www.deja.com/   ------------------------------  % Date: Fri, 29 Dec 2000 13:19:02 -0600l0 From: Ashutosh Dhodapkar <dhodapka@ece.wisc.edu> Subject: relocationnL Message-ID: <Pine.LNX.4.21.0012291317160.11677-100000@localhost.localdomain>  B I needed some help on relocation of binaries. basically, i want toG relocate a binary so that it occupies virtual address 0x00 however i amrD unable to do this on the alpha system that we have. any help will be appreciated.   thanks.t ashutosh   ------------------------------   Date: 29 Dec 2000 20:17:20 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: relocationr6 Message-ID: <92irgg$f3h$1@mailint03.im.hou.compaq.com>   In article <Pine.LNX.4.21.0012291317160.11677-100000@localhost.localdomain>, Ashutosh Dhodapkar <dhodapka@ece.wisc.edu> writes:-  C :I needed some help on relocation of binaries. basically, i want torH :relocate a binary so that it occupies virtual address 0x00 however i amE :unable to do this on the alpha system that we have. any help will be)
 :appreciated.q  J   Depending on exactly what you are up to here, there may be (are?) other J   options, and there may be (are?) other considerations.  In other words, K   you might find that providing some background on why you want to do this tJ   and/or on what problem(s) you are working to resolve might prove useful.G   (The OpenVMS Alpha version might also be useful, depending on exactlyi   what you are up to...)  H   That said, if you simply want to have code or data located at virtual I   address zero in the image virtual address space -- something that I do sF   not generally recommend, as it can make debugging more difficult -- F   there are LINKER directives available that will be of interest.  In D   particular, please see the documentation of the CLUSTER directive *   that is included in the LINKER manual...  D   If you want to relocate existing OpenVMS Alpha executable code in I   virtual memory, well, that effort and the associated fix-up operations /E   would be another and rather different discussion.  (You will end up I   learning rather more about image activation and image fixup processing,tG   and about procedure descriptors, and learning about the need to flush-E   the instruction cache before executing the freshly-relocated code.)   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Fri, 29 Dec 2000 19:40:57 -0500e- From: JF Mezei <jfmezei.spamnot@videotron.ca>-+ Subject: Sending messages to an applicationb, Message-ID: <3A4D2F12.1AE716B4@videotron.ca>  J Most GUI platforms, even my old trusted PSION 3 (not actuall a GUI) have aN mechanism whereas one application can send a message to another application toL tell it to open/close a file. (or start that application with a file to open by default).  J For instance, while reading an email, you can view an attachement with theL proper application, and if the application is already started, it just opens> the new file, thus providing much faster service to the user).    M VMS , as an OS, doesn't have that built-in. But does X-windows have this type  of feature ?   ------------------------------  # Date: Fri, 29 Dec 2000 19:18:08 GMTa* From: Doran Werling <rwscsinc@my-deja.com>" Subject: Re: tcpip show host error) Message-ID: <92io19$qbd$1@nnrp1.deja.com>t  . In article <92hnod$liv$1@reader1.imaginet.fr>,A   "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr> wrote:) > Bonjour  tous ! >  > When issuing a >o >     $ tcpip show host  > 4 > I get the list of my LOCAL database, followed by : >h. >     %TCPIP-W-NORECORD, information not found. >     -NONAME-E-NOMSG, Message number 0764960A >  > When issuing > $ >     $ tcpip show host www.x9000.fr > 4 > I get the correct BIND database entry from the DNS+ > which is is held by my Internet Provider.- >-= > When I try to ping www.x9000.fr, ping finds the ip address,r8 > but falls in timeout. However, I can ping this address > from outside my lan. >o; > I'm connected through a CISCO 1401 router performing NAT.h >   > Any hint will be appreciated ! >n > Merci et bonne anne > Jean-Francois Marchalx > X9000 - LYON (FR)R >6 >1D I have seen this problem before with the remote node being unable to, return the ping packet. I would check for ..  <      www.x9000.fr  having it's default gateway properly set.  E     If www.x9000.fr is in a different subnet, check the configuration-  of the router.-   Regards,
 Doran Werling  RW/SCS Inc.P     Sent via Deja.comV http://www.deja.com/   ------------------------------    Date: 30 Dec 2000 02:47:00 +0800, From: Paul Repacholi <prep@prep.synonet.com>" Subject: Re: tcpip show host error0 Message-ID: <87d7ebawuz.fsf@k9.prep.synonet.com>  @ "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr> writes:   Last first..= > When I try to ping www.x9000.fr, ping finds the ip address,-8 > but falls in timeout. However, I can ping this address > from outside my lan.  ; That is no big deal. It means the firewall is blocking ICMP)9 Echo Request/Reply. This is a common fix to stop problemsR" from 'Ping Flooding' and the like.  4 > I get the list of my LOCAL database, followed by : > . >     %TCPIP-W-NORECORD, information not found. >     -NONAME-E-NOMSG, Message number 0764960A >  > When issuing > $ >     $ tcpip show host www.x9000.fr > 4 > I get the correct BIND database entry from the DNS+ > which is is held by my Internet Provider.   8 This indicates you are not allowed to do a zone transfer6 from the DNS server. Again, not uncommon, though it is6 a bit unusual to prevent transfers to inside the zone.  : You may want to consider changing the way your ISP handles? your DNS, and put at least a secondary DNS inside the firewall.i   -- a< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.a@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------    Date: 30 Dec 2000 02:46:17 +0800, From: Paul Repacholi <prep@prep.synonet.com>" Subject: Re: tcpip show host error0 Message-ID: <87g0j7aww6.fsf@k9.prep.synonet.com>  @ "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr> writes:   Last first..= > When I try to ping www.x9000.fr, ping finds the ip address, 8 > but falls in timeout. However, I can ping this address > from outside my lan.  ; That is no big deal. It means the firewall is blocking ICMPi9 Echo Request/Reply. This is a common fix to stop problems " from 'Ping Flooding' and the like.  4 > I get the list of my LOCAL database, followed by : > . >     %TCPIP-W-NORECORD, information not found. >     -NONAME-E-NOMSG, Message number 0764960A >  > When issuing > $ >     $ tcpip show host www.x9000.fr > 4 > I get the correct BIND database entry from the DNS+ > which is is held by my Internet Provider.-  8 This indicates you are not allowed to do a zone transfer6 from the DNS server. Again, not uncommon, though it is6 a bit unusual to prevent transfers to inside the zone.  : You may want to consider changing the way your ISP handles? your DNS, and put at least a secondary DNS inside the firewall.    -- o< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  # Date: Fri, 29 Dec 2000 19:31:54 GMTo From: support@callowco.com: Subject: ~~~Search for computer help (within text) Free!!!< Message-ID: <KE536.610$94.71759@e420r-atl2.usenetserver.com>  ! Search this group within text at:    www.callowco.com/helpdesk.aspW  ? Note; You must use internet explorer to view the page correctly-. Thank you for trying it.  support@callowco.com   ------------------------------   End of INFO-VAX 2000.728 ************************