1 INFO-VAX	Wed, 03 Oct 2001	Volume 2001 : Issue 549       Contents:& Re: Apache and Username authentication& Re: Apache and Username authentication Re: Ben Rosen the real culprit?  Re: Ben Rosen the real culprit?  Re: Ben Rosen the real culprit?  Re: Ben Rosen the real culprit?  Re: Ben Rosen the real culprit? 6 Re: BIG differences in Vax vs ALpha compile/link times6 Re: BIG differences in Vax vs ALpha compile/link times6 Re: BIG differences in Vax vs ALpha compile/link times6 Re: BIG differences in Vax vs ALpha compile/link times6 Re: BIG differences in Vax vs ALpha compile/link timesE Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter E Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter E Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter E Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter  DECnet 7.3 with VMS 7.2 on VAX" Re: DECnet 7.3 with VMS 7.2 on VAX Re: Defining a logical in C - Re: DLT IV Tapes - How long should they last? - Re: DLT IV Tapes - How long should they last? - Re: DLT IV Tapes - How long should they last? - Re: DLT IV Tapes - How long should they last? ! DS20 Used With Cpq Warranty $4000  Re: FAQ September 2001 edition4 Re: Fw: Best Way to do Interprocessing Communication Re: Good bye VAX-6400's  Re: Help with UNZIP.EXE 2 Help! OpenVMS 7.3 and COGNOS Powerhouse 7.10.E1???P Re: I WILL QUIT USING VMS WHEN THE MILITARY DOES - IN 2015 OR MAYBE LONGER! LONG Re: imherited cluster help Re: imherited cluster helpC Re: Itanium and Bi-endianism (was: Re: Ben Rosen the real culprit?)   Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas  Re: Letter from Michael Cappelas, Re: Locate Filename containing logical block, Re: Locate Filename containing logical block, Re: Locate Filename containing logical block, Re: Locate Filename containing logical block Re: NT or w2k on alpha 1200 ?  Re: NT or w2k on alpha 1200 ?  Re: NT or w2k on alpha 1200 ?  ODS-2 for FreeBSD 8 Re: ODS2 available -- reads ODS-2 disks on Windows, UNIX2 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" Re: OpenVMS, Apache and hackers..." Re: OpenVMS, Apache and hackers..." Re: OpenVMS, Apache and hackers..." Re: OpenVMS, Apache and hackers..." Re: OpenVMS, Apache and hackers...6 Problem With VMS Backup Save-Set Spanning Tape Volumes Public domain VMS clustering ?" Re: Public domain VMS clustering ? Re: PWIP does not start  Re: PWIP does not start  Re: Question on VMS Virus  Re: Quota Setting  Re: Ram Disk for VMS?  Re: Ram Disk for VMS?  Re: Ram Disk for VMS?  Re: Ram Disk for VMS? < Re: RMS ISAM internals question: IRC$V_RU_UPDATE & RU_DELETE VAX SET BOOT doc?  Re: VAX SET BOOT doc?  VMS 7.3 versus 7.2-2 Re: VMS 7.3 versus 7.2-25 Re: VMScluster using fibrechannel and memory channel? / Re: Warranty on ES45 reduced from 3 years to 1? / Re: Warranty on ES45 reduced from 3 years to 1? / Your Article - The Journalistic Portal for Copy   F ----------------------------------------------------------------------  $ Date: Tue, 2 Oct 2001 16:37:50 -0400+ From: "Rick Barry" <barry@star.zko.dec.com> / Subject: Re: Apache and Username authentication 1 Message-ID: <Xzpu7.953$YP.25575@news.cpqcorp.net>   : "Michael Austin" <miaustin@bellsouth.net> wrote in message' news:3BB9D0F5.F5D5DA6A@bellsouth.net... H > Does anyone have an example of a access.conf config file for Apache onD > OpenVMS to password protect certain pages using OS authentication? > 	 > Thanks,  > Michael Austin >  >   I In your httpd.conf file, you'll need to allow .htaccess file overrides in " the directory you want to protect:   <Directory /your-path/>      AllowOverride AuthConfig </Directory>  B In the <your-path> directory, create the following .HTACCESS file:     AuthType Basic-     AuthName "OpenVMS Authentication Testing"      AuthUserOpenVMS On     require valid-user  
 Rick Barry CSWS Project Team  Compaq Computer Corporation 
 Nashua, NH   ------------------------------  % Date: Tue, 02 Oct 2001 16:46:55 -0400 - From: Michael Austin <miaustin@bellsouth.net> / Subject: Re: Apache and Username authentication - Message-ID: <3BBA27BF.B773E17A@bellsouth.net>   0 I should have started at the bottom... Thanks!!!   Rick Barry wrote:   < > "Michael Austin" <miaustin@bellsouth.net> wrote in message) > news:3BB9D0F5.F5D5DA6A@bellsouth.net... J > > Does anyone have an example of a access.conf config file for Apache onF > > OpenVMS to password protect certain pages using OS authentication? > >  > > Thanks,  > > Michael Austin > >  > >  > K > In your httpd.conf file, you'll need to allow .htaccess file overrides in $ > the directory you want to protect: >  > <Directory /your-path/>  >     AllowOverride AuthConfig > </Directory> > D > In the <your-path> directory, create the following .HTACCESS file: >     AuthType Basic/ >     AuthName "OpenVMS Authentication Testing"  >     AuthUserOpenVMS On >     require valid-user >  > Rick Barry > CSWS Project Team  > Compaq Computer Corporation  > Nashua, NH   ------------------------------   Date: 3 Oct 2001 01:32:35 GMT & From: peter@abbnm.com (Peter da Silva)( Subject: Re: Ben Rosen the real culprit?% Message-ID: <9pdprj$7v7@web.nmti.com>   = In article <1cHt7.52600$vq.10254596@typhoon.ne.mediaone.net>, 3 Terry C. Shannon <terryshannon@mediaone.net> wrote: K > > Or maybe it's all true that Curly and Carly think that they can take on ' > > IBM with their winning combination?   G > I've only spoken with one of the above, but that sure seems to be the ! > sentiments of Michael Capellas.   % Let's hope they do as well as Unisys.   G Yes, really. Unisys is still in business, and still selling Sperry- and   Burroughs- compatible computers.   --  +  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything." L                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------   Date: 3 Oct 2001 01:39:38 GMT & From: peter@abbnm.com (Peter da Silva)( Subject: Re: Ben Rosen the real culprit?% Message-ID: <9pdq8q$83q@web.nmti.com>   , In article <3BB7D087.D609816A@videotron.ca>,/ JF Mezei  <jfmezei.spamnot@videotron.ca> wrote: I > Consider that unless proven otherwise, Tru64 is as good as dead. Once a P > customer accepts that, he also accepts that full migration to another platformA > will be necessary at which point endianness becomes irrelevant.     I think endianness is overrated.  M I have been heavily involved in porting a major (millions of LOC) application E from 16-bit little endian and 36-bit 1s-complement hardware to 32-bit K big-endian to 64-bit little-endian... with detours to 32-bit little-endian  G and back to 32-bit big-endian... with some of the development on 16-bit H big-endian and 16-bit word-oriented machines. Word size is a much biggerJ issue than byte order, if you've paid any attention at all to portability.  J The big issues, really, are API mismatches. Particularly when they've beenI written to a standard as badly subject to the telephone effect as some of  the ones I've seen.    --  +  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything." L                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------   Date: 3 Oct 2001 01:30:57 GMT & From: peter@abbnm.com (Peter da Silva)( Subject: Re: Ben Rosen the real culprit?% Message-ID: <9pdpoh$7uv@web.nmti.com>   ' In article <9p739h$693$1@joe.rice.edu>, * Jerry Leslie <leslie@clio.rice.edu> wrote:, >   "HP New York layoffs announced tomorrow?) >    170 Unix boffins under threat [...]"   G > That sure seems an odd group to whack if HPUX/IA64 is the future unix  > of the merged HP/Compaq.  I That depends on how much of the new UNIX is Tru64, and how much is HP/UX.   J Going to a little-endian IA64 would make it easier to interoperate between NT and NewNix.   --  +  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything." L                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------  # Date: Wed, 03 Oct 2001 03:28:53 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>( Subject: Re: Ben Rosen the real culprit?= Message-ID: <VBvu7.68454$vq.12908838@typhoon.ne.mediaone.net>   3 "Peter da Silva" <peter@abbnm.com> wrote in message  news:9pdprj$7v7@web.nmti.com... ? > In article <1cHt7.52600$vq.10254596@typhoon.ne.mediaone.net>, 5 > Terry C. Shannon <terryshannon@mediaone.net> wrote: J > > > Or maybe it's all true that Curly and Carly think that they can take on) > > > IBM with their winning combination?  > I > > I've only spoken with one of the above, but that sure seems to be the # > > sentiments of Michael Capellas.  > ' > Let's hope they do as well as Unisys.  > I > Yes, really. Unisys is still in business, and still selling Sperry- and " > Burroughs- compatible computers. >   G Yep, one of the first Big Mergers. "Power of Two," they called it, long E before they began running those strange ads in which human heads were  replaced with monitors.    ------------------------------  # Date: Wed, 03 Oct 2001 03:33:10 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>( Subject: Re: Ben Rosen the real culprit?= Message-ID: <WFvu7.68493$vq.12912073@typhoon.ne.mediaone.net>   3 "Peter da Silva" <peter@abbnm.com> wrote in message  news:9pdpoh$7uv@web.nmti.com... ) > In article <9p739h$693$1@joe.rice.edu>, , > Jerry Leslie <leslie@clio.rice.edu> wrote:. > >   "HP New York layoffs announced tomorrow?+ > >    170 Unix boffins under threat [...]"  > I > > That sure seems an odd group to whack if HPUX/IA64 is the future unix  > > of the merged HP/Compaq. > K > That depends on how much of the new UNIX is Tru64, and how much is HP/UX.  >   J True. Technically it would make more sense to relabel Tru64 as HP-UX, thenJ use $$$ from the Itanium Porting Fund to help ISVs migrate their incumbent HP-UX apps to the "new" HP-UX.  L The easier approach would be to graft TruCluster and Tru64 RAS features ontoK HP-UX. Problem is, HP-UX is IIRC the last of the old-line monolithic kernel L UNIX implementations. Gonna have to upgrade it to a modular kernel sometime;% this might be a good time to do so...    ------------------------------   Date: 2 Oct 2001 15:37:30 -0700 / From: rcyoung@aliconsultants.com (Robert Young) ? Subject: Re: BIG differences in Vax vs ALpha compile/link times = Message-ID: <91437ce6.0110021437.392fbfa6@posting.google.com>   E All the suggestions to date have "helped" at the DEC C level, but the ; BIGGEST PROBLEM is apparently hiding in another area that I 
 uncovered....   < It turns out the the compile/links were going through an Rdb@ PRECOMPILER on BOTH Vax and Alpha to convert embedded SQL to theF correct "c" calls. When one takes the "c" code that is generated afterE the Precompiler, and runs it through DEC C/linker by itself, the time C on Alpha is only 14 minutes. That means it is taking 1 1/4 HOURS in C the precompiler (on Alpha only) to create the final "c" code files.   F I checked with Oracle, and apparently the Alpha PRECOMPILER is using aF Compaq "GEM" product (whatever that is....they were not too specific).% Oracle DOES NOT use the "GEM" on Vax.   ? With regards to the actual DEC C compile/link...the suggestions B offered did in fact improve this part of the job, and all the help( that was offered is greatly appreciated.  B Does anyone else know what they are referring to as being a Compaq	 "GEM"????    ------------------------------  # Date: Tue, 02 Oct 2001 23:44:12 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)? Subject: Re: BIG differences in Vax vs ALpha compile/link times 1 Message-ID: <gjsu7.965$YP.25450@news.cpqcorp.net>   o In article <91437ce6.0110021437.392fbfa6@posting.google.com>, rcyoung@aliconsultants.com (Robert Young) writes:   = :It turns out the the compile/links were going through an Rdb A :PRECOMPILER on BOTH Vax and Alpha to convert embedded SQL to the G :correct "c" calls. When one takes the "c" code that is generated after F :the Precompiler, and runs it through DEC C/linker by itself, the timeD :on Alpha is only 14 minutes. That means it is taking 1 1/4 HOURS inD :the precompiler (on Alpha only) to create the final "c" code files.  I   Within Oracle Rdb, you can split up some of the actions of the SQL$PRE  J   processing, and you can maintain various intermediate modules after the L   SQL$PRE pass.  (You generally need to maintain a subset of these modules, H   if you have any expectation of performing source code debugging.  MoreI   specifically, you need to maintain the generated C "source code" module G   after the pre-processing pass, since that is what the C compiler and  J   then the LINKER operates on and is thus the "source code" that you wouldG   expect to see when you debug the code.  There are other intermediate  L   files within SQL$PRE, though the file extensions escape me at the moment.)  G :I checked with Oracle, and apparently the Alpha PRECOMPILER is using a G :Compaq "GEM" product (whatever that is....they were not too specific). & :Oracle DOES NOT use the "GEM" on Vax.  F   GEM is the code generator used by all of the Compaq Alpha compilers.G   (Interpreters -- particularly Java -- don't tend to use it, however.)   0   VCG is the code generator used on OpenVMS VAX.  F   The SQL$PRE module (within Oracle Rdb on OpenVMS Alpha) uses GEM to E   generate its own object code, and it also generates C "source code" ;   for inclusion into one or more subsequent C compilations.   D   The Compaq C compiler then uses the GEM code generator, of course.  C :Does anyone else know what they are referring to as being a Compaq 
 :"GEM"????  G   GEM would be used to generate the intermediate database access code,  C   the stuff that the (generated) C "source code" module calls into. I   This output is the object code that (eventually) services the embedded  H   SQL requests when the application is eventually processed through the    OpenVMS LINKER and then run.  D   That this is a GEM problem is interesting and certainly appears anD   incomplete answer -- while there could certainly be problems with E   GEM here, there could also be problems with the SQL$PRE processing. G   (I've used Oracle Rdb and embedded SQL for some time now and haven't  C   noticed massive differences in SQL$PRE processing.  Maybe you are 0   doing something rather different than I am...)  A   Which version of Oracle (classic) or Oracle Rdb is in use here?   E   Older versions of Oracle Rdb did have a version of GEM containing a G   known bug, specifically a version of GEM with the ability to generate H   overly-long load-locked store conditional Alpha instruction sequences.F   The Alpha code sequences generated by this older version of GEM was E   incompatible with EV6 (21264) and later processors.  (This bug was  H   fixed some time ago in GEM, and the corrected version of GEM was then G   incorporated into Compaq C, Oracle Rdb, and various other packages.   C   See the 21264 directory on the OpenVMS Freeware V4.0 website for     further details on this.)   G   Can you characterize the pre-processing performance differences on a     simple embedded SQL module?   A   Can you characterize differences in the run-time environment?     G   (I've seen massive slow-downs with Oracle Rdb builds, slowdowns that  F   were due to insufficient quotas and/or insufficient system parameterD   configurations and/or insufficient system physical memory or otherB   hardware restrictions.  I once saw Oracle Rdb build performance E   approach infinite time when I started the third build in parallel,  D   but I'd actually run out of available system resources -- the Rdb G   builds had begun paging heavily, and were also filling up the system  I   pagefile.  Performance suffered.  Greatly.  Once I added more physical n!   memory, builds got far faster.)h  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 02 Oct 2001 18:50:23 -0500e/ From: Chris Scheers <chris@applied-synergy.com>r? Subject: Re: BIG differences in Vax vs ALpha compile/link timeso3 Message-ID: <3BBA52BF.689381FA@applied-synergy.com>r   Robert Young wrote:r > / > Two systems: Vax 4000-600 & Alphaserver 2100ar > E > Compaq/DEC C compiler on both.  V6.4 on Alpha, V6.0 on Vax. We just H > installed the Alpha this weekend so that is the reason for the version > mismatch.g > H > Vax (VMS 7.1, ?MHz, 128Mb memory, RF-74 DSSI drives)compiles and linksE > program in 14 minutes. On Alpha (VMS 7.3, 250MHz-2 processor, 512MbaH > memory, RZ29D-VWs)it takes 90 minutes for same EXACT code, same linker > file, etc. > G > Code is written/compiled/linked first on Vax, then copied on Alpha touF > be recompiled/linked there so we have versions for both platforms at > this time. > E > Any suggestions/recommendations would be helpful where we could getS > the0F > work on Alpha done faster? It seems that the discrepancy is just too > large ) > between the systems. Thanks in advance.R >  > Respond to email if possible    : Keep in mind that the Alpha compiler does a LOT more work.  E Comparing between a VAXstation 4000-90 and an AlphaStation 255/233, If@ have seen some compiles take 10 times the CPU time on the Alpha.  F If your quotas are such that you are not doing excessive paging duringH compiles, I don't think that there is much more optimization you can do.  
 Good luck!  G -----------------------------------------------------------------------o$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com     Fax: 817-237-3074a   ------------------------------  $ Date: Wed, 3 Oct 2001 01:24:57 +01001 From: "Chris Townley" <news@townleyc.demon.co.uk>e? Subject: Re: BIG differences in Vax vs ALpha compile/link times A Message-ID: <1002069908.3844.0.nnrp-07.d4e45fa5@news.demon.co.uk>M  ? "Hoff Hoffman" <hoffman@xdelta.zko.dec.nospam> wrote in messagen+ news:Vl6u7.898$YP.24250@news.cpqcorp.net....? > In article <91437ce6.0110011336.3fcc1364@posting.google.com>,a1 rcyoung@aliconsultants.com (Robert Young) writes:e0 > :Two systems: Vax 4000-600 & Alphaserver 2100a > :c@ > :Compaq/DEC C compiler on both.  V6.4 on Alpha, V6.0 on Vax... >P > :Vax ...compiles and linksI > :program in 14 minutes. On Alpha ... it takes 90 minutes for same EXACTf > :code, same linker file, etc.  > ..H > :Code is written/compiled/linked first on Vax, then copied on Alpha toG > :be recompiled/linked there so we have versions for both platforms at 
 > :this time.7 >2G >   Consider clustering, as you can operate off the same source pool...c >nI This is a subject dear to my heart, but possibly too dear for my company.5  E We have a MV 3190 which is our main development machine, with all theCJ tools.Main bulk of (sadly called legacy) software written in Compaq Basic,H with a few modules in C or macro. Application is around 4,700 modules atK last count. However we only have one UK site running VAX - rest on a couple I of clustered 4100 Alphas. Germany on Alpha, while France are on a VAX 400uG cluster. Alpha builds are done on a Alpha Server 400/233 (ISTR) after asA massive DECNET copy. Both nodes are currently on VMS 6.2 awaiting 9 approval to upgrade production machines to 7.1 and a bit.t  L I have looking at tightening the coupling, but the network is not up to thatJ much, so I would love to cluster them to enable shared storage, but am notK sure about the cost implications - the application is still considered as arI Legacy app, even if it does take 95% or more of customer orders and still H handles are 4 largest branches - rest are on a 'new' Vintage Oracle/Unix! system that stinks - Vivaldi AOM.s  G The VAX is licensed for pretty much everything, whilst the Alpha has an H unlimited VMS license, plus DECNET, UCX and Compaq Basic/C and not a lot else.r  G So what would be the hardware and software licensing implications be ina clustering ?  G I have also considered the possibility of an additional 100 base/T  neteH link, but not sure if I could stick such into the MV 3100 - I presume it would be possible on the alpha.m     --
 Chris Townley. chris@townleyc.demon.co.uk townleyc@spicers.ltd.ukx   ------------------------------  # Date: Wed, 03 Oct 2001 01:45:25 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)? Subject: Re: BIG differences in Vax vs ALpha compile/link timesp1 Message-ID: <V4uu7.967$YP.25553@news.cpqcorp.net>e  u In article <1002069908.3844.0.nnrp-07.d4e45fa5@news.demon.co.uk>, "Chris Townley" <news@townleyc.demon.co.uk> writes:eF :We have a MV 3190 which is our main development machine, with all theH :tools... Alpha builds are done on a Alpha Server 400/233 (ISTR) after aB :massive DECNET copy. Both nodes are currently on VMS 6.2 awaiting: :approval to upgrade production machines to 7.1 and a bit. ..H :The VAX is licensed for pretty much everything, whilst the Alpha has anI :unlimited VMS license, plus DECNET, UCX and Compaq Basic/C and not a lotr :else. :?H :So what would be the hardware and software licensing implications be in
 :clustering ?e  E   Assuming you have a decent network connection between the box, you  F   need the cluster license and reasonably consistent OpenVMS versions.E   I regularly use a clustered VAXstation 4000 model 60 series and an  G   AlphaServer 1200 series for running builds.  Most of the development  H   work and most of the development builds occur on the AlphaServer (and H   the main disks are connected there), and (when a rebuild is required) E   I use the VAXstation as a build engine (via the MSCP-served disks).   H :I have also considered the possibility of an additional 100 base/T  netI :link, but not sure if I could stick such into the MV 3100 - I presume it   :would be possible on the alpha.  H   While the MicroVAX 3100 series tends to not be particularly expandableG   and configurations are largely limited to (slow) Ethernet, PCI-based DH   Fast Ethernet widgets and GbE widgets are available for various Alpha C   systems.  (Since I use the VAXstation as a build engine, I am not E   normally waiting on its build performance.  But the VAXstation doesaD   serve nicely for this purpose, even with the MSCP-served disks and    the Slow Ethernet connection.)  H   I did have to modify my builds to honor a logical name that referencesG   the platform-specific objects and images directories.  (I'll soon be  K   off modifying that area of the build procedures again, but I digress. :-)-  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 02 Oct 2001 16:49:44 -0400r- From: JF Mezei <jfmezei.spamnot@videotron.ca>oN Subject: Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter, Message-ID: <3BBA2861.C31D693A@videotron.ca>   Alan Greig wrote:h@ > Well that and the further uncertainty caused by the HP merger.D > Probably accounts for a large part of the downturn at a guess. ButG > Compaq will never admit that. Although close scrutiny of the officialrE > figures they release at the end of the month should provide a clue.o  K Consider that Compaq has been very good at hiding VMS revenus and making it<E look like Compaq's profits came from the wintel business ("enterpriseoM servers"). I have no doubts that they will present their numbers to make whatp counts look good.   K And since Compaq is now a lame duck company waiting to be eaten by HP, doesoL anyone expect Compaq to do anything special in terms of sales except see its numbers go down ?a   ------------------------------  % Date: Tue, 02 Oct 2001 22:45:54 +0200 & From: John McLean <mcleanj@dplanet.ch>N Subject: Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter* Message-ID: <3BBA2782.C8D37664@dplanet.ch>   "Terry C. Shannon" wrote:: > =?  1 > "John Nebel" <nebel@csdco.com> wrote in messagecB > news:Pine.OSF.4.21.0110021006250.1447-100000@athena.csdco.com... > >> > > What are "C-level folks"?a > =p   > CEO, CIO, CFO, CTO    G Are these the same kind of folk that The Register talked about in their.4 article "UK plc wastes =A317bn a year on IT" (at URL4 http://www.theregister.co.uk/content/7/21952.html) ?  C "An initial estimate of the money being wasted - based on a similar F report in the US - was =A311 billion; however KPMG was so amazed at UK? managers' ignorance that it upped the figure to =A317 billion."o    H As an example, one of the reasons for the waste was stated as "The BoardG doesn't have a clue about IT procurement. As such IT is seen as a cost, G but rarely is it looked at as an ongoing form of assets like stocks andn shares for example."  D I suppose that one of the C's pays for IT purchases but this article< certainly questions their competence to make such decisions.     John McLeanh   ------------------------------  % Date: Tue, 02 Oct 2001 17:05:41 -0400-- From: JF Mezei <jfmezei.spamnot@videotron.ca> N Subject: Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter+ Message-ID: <3BBA2C1C.F201448@videotron.ca>3   "Terry C. Shannon" wrote: M > If I was a customer who was having second thoughts about disaster tolerancecL > (maybe it doesn't cost too much after all!) I'd be calling the Himalaya or# > VMScluster folks and perhaps IBM.k  L Investing in a platform/vendor whose future is uncertain is silly for a very1 important system that needs to stay up for years.A  N If you're already on VMS, then it is smart to stay on it until you get an easyN way to port without losing functionality. But if you're already on Unix or NT, it is silly to move to VMS.a  L Note that many vendors now make claims of clustering. And Fujitsu even makes3 TV ads that say it can stay up 99.999% of the time.    ------------------------------  # Date: Tue, 02 Oct 2001 21:07:26 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>N Subject: Re: Compaq revenue goes down $1 Billion, warns of loss in 3rd Quarter= Message-ID: <i0qu7.67357$vq.12613287@typhoon.ne.mediaone.net>.  3 "John McLean" <mcleanj@dplanet.ch> wrote in message1$ news:3BBA2782.C8D37664@dplanet.ch...     "Terry C. Shannon" wrote:u >c1 > "John Nebel" <nebel@csdco.com> wrote in message B > news:Pine.OSF.4.21.0110021006250.1447-100000@athena.csdco.com... > >  > > What are "C-level folks"?e >e > CEO, CIO, CFO, CTO    G Are these the same kind of folk that The Register talked about in theirn2 article "UK plc wastes 17bn a year on IT" (at URL4 http://www.theregister.co.uk/content/7/21952.html) ?  C "An initial estimate of the money being wasted - based on a similar D report in the US - was 11 billion; however KPMG was so amazed at UK= managers' ignorance that it upped the figure to 17 billion."u    B Could be, the ones I've encountered of late don't seem to fit that+ description, though. Your mileage may vary.    ------------------------------  $ Date: Tue, 2 Oct 2001 18:37:27 -0400* From: "Stanley F. Quayle" <stan@stanq.com>' Subject: DECnet 7.3 with VMS 7.2 on VAX . Message-ID: <3BBA0967.30364.6C60E9E@localhost>  @ I upgraded DECnet/OSI from 7.2 to 7.3 on a VAX that has VMS 7.2 < installed.  Now, no matter what I do, DECnet will not start.  F Was this a bad idea?  Can I back up to DECnet 7.2?  Or must I install  VMS 7.3?     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671m1 8572 North Spring Ct. NW, Pickerington, OH  43147j= Preferred address:  stan@stanq.com       http://www.stanq.come   ------------------------------  # Date: Tue, 02 Oct 2001 22:58:46 GMT03 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk>n+ Subject: Re: DECnet 7.3 with VMS 7.2 on VAXu/ Message-ID: <3BBA4647.9BD93D20@cableinet.co.uk>a   "Stanley F. Quayle" wrote: > A > I upgraded DECnet/OSI from 7.2 to 7.3 on a VAX that has VMS 7.2o> > installed.  Now, no matter what I do, DECnet will not start. > G > Was this a bad idea?  Can I back up to DECnet 7.2?  Or must I installm
 > VMS 7.3? >   D did you VMSINSTAL or PRODUCT INSTALL DECNet? I can't remember if theE VAX install has been converted to PCSI. If it has, PRODUCT REMOVE theoF the 7.3 and reinstall 7.2 might work. Possibly your configuration data could be toast.t  F Then again, you do have backups, don't you? Why not restore the system' disk from a backup before the upgrade? n  6 Whatever you do, take a backup of what you've got now.  C You might however also want to research the problem with the DECNetl startupeE since the upgrade, and also whether what you have done is supported. h2 Posting real error messages here might be a start.   regardsu   --   Tim.Llewellyn@cableinet.co.uk  e  C Standard disclaimer applies. My views in no way represent those of t! my employers or service provider.    ------------------------------  % Date: Tue, 02 Oct 2001 16:39:05 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>i$ Subject: Re: Defining a logical in C, Message-ID: <3BBA25E2.125A9CF3@videotron.ca>   Bob Koehler wrote:K >    You should get errors with many System Service and RMS (SYS$) calls ifaK >    you don't supply all the arguments, but trailing optional arguments in D >    RTL calls (LIB$ and such) should not require 0.  Do you have an >    example of such a failure?o  J I don't have an example offhand. But I distinctly remember (perhaps in theH VAX-C days) having a problem with missing optional arguments at the end,M resulting an in aaccess violation, and that it was solved by adding the 0s atfQ the end to fill the argument list. And I have taken to doing so out of habit now.e  M The one that comes to mind is QIO on TT devices. But it has been a long time."   ------------------------------   Date: 2 OCT 2001 17:28:37 GMTa4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)6 Subject: Re: DLT IV Tapes - How long should they last?5 Message-ID: <2OCT01.17283789@thuria.waisman.wisc.edu>m  E In a previous article, "Peter Weaver" <peter.weaver@stelco.ca> wrote:eJ ->I lost the original posting due to age, but this subject was raised hereK ->today when a comparison was made between DLT and 9840 tapes. I found thisr ->link;eN ->http://www.backupcentral.com/cgi-bin/netbackup-fom?_recurse=1&file=20#file_1< ->53 that states DLT tapes should last for 1,000,000 passes.  F That doesn't equate to the number of times you can read/write/rewind aF tape in the drive though. DLT's are "serpentine" devices and make manyE passes for each end-to-end tape run. As I recall they have 128 tracks F and the head can read two at a time. Still, 1,000,000/128 is a quite aE lot (even hard to believe). I remember a figure of 10,000 passes when  they were first introduced.4   ------------------------------  % Date: Tue, 02 Oct 2001 23:24:29 +0200 < From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>6 Subject: Re: DLT IV Tapes - How long should they last?( Message-ID: <3BBA308D.8A6B6B72@home.com>  . Aren't the tracks layed out as on a VHS tape ?6 That is, diaganaly across the tape. And the drive usesC an spinning tilted head, just as in the VHS "drive". So the head(s)h@ is(are) passing by the tape many times (maybe 128) for any given< position, but the tape it self just make one go from one end
 to the other.t   Jan-Erik Sderholm.n   Carl Karcher wrote:m > G > In a previous article, "Peter Weaver" <peter.weaver@stelco.ca> wrote:hL > ->I lost the original posting due to age, but this subject was raised hereM > ->today when a comparison was made between DLT and 9840 tapes. I found thisu	 > ->link;tP > ->http://www.backupcentral.com/cgi-bin/netbackup-fom?_recurse=1&file=20#file_1> > ->53 that states DLT tapes should last for 1,000,000 passes. > H > That doesn't equate to the number of times you can read/write/rewind aH > tape in the drive though. DLT's are "serpentine" devices and make manyG > passes for each end-to-end tape run. As I recall they have 128 tracksnH > and the head can read two at a time. Still, 1,000,000/128 is a quite aG > lot (even hard to believe). I remember a figure of 10,000 passes when  > they were first introduced.    ------------------------------  % Date: Tue, 02 Oct 2001 22:29:30 -0500r1 From: "David J. Dachtera" <djesys.nospam@fsi.net>j6 Subject: Re: DLT IV Tapes - How long should they last?' Message-ID: <3BBA861A.2510FE22@fsi.net>i  
 Mal wrote: > f > "Todd Nelson" <toddnelson_@hotmail.com> wrote in message news:<trgk8o9mbg3353@corp.supernews.com>... > P > > We do use cleaning tapes regularly --> not just when the yellow blinky light
 > > comes on.e > >f > D > If I remember correctly you're NOT supposed to do this, aren't theG > cleaning tapes mildly abrasive? therefore you can end up rubbing away7? > the tape heads, and then you get loads of tape errors........i  E I would think that you'd have to use the cleaning tape once a day foreB several months before you'd do any appreciable damage to the head.* They're pretty tough, relatively speaking.    -- o David J. Dachtera. dba DJE Systemss http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/e   ------------------------------  % Date: Tue, 02 Oct 2001 22:32:35 -0500k1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 6 Subject: Re: DLT IV Tapes - How long should they last?' Message-ID: <3BBA86D3.366144FE@fsi.net>4   Jan-Erik Sderholm wrote:5 > 0 > Aren't the tracks layed out as on a VHS tape ?8 > That is, diaganaly across the tape. And the drive uses7 > an spinning tilted head, just as in the VHS "drive". h  F You're thinking helical scan. DLT technology is serpentine, similar to QIC.   -- - David J. Dachtera- dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------  $ Date: Tue, 2 Oct 2001 23:08:50 -04000 From: "Island Computers" <dbturner@islandco.com>* Subject: DS20 Used With Cpq Warranty $4000/ Message-ID: <trkvr7j1pnvc04@news.supernews.com>a   We have a USED system just in   8 A couple of minor "dings" but nothing obvious - honestly   We are asking $4000d   Configured as follows:  + DS20 6/500 500Mhz System (Dual CPU Capable)o 512MB Memory 4 x DS-RZ1CB-VW 4Gb Disk( KZPAC-AA SCSI RAID Ultra Wide Controller DE500-BA 10/100 Ethernet CardY
 1.44MB Floppy  32x SCSI CD-ROM with Controllerp  ) A great hobbyist system or .....???!!?!!?r   No VMS Licenses included   -- We sell Alpha systems & partsa http://www.islandco.com4 sales@islandco.com Island Computers US Corp.s 2700 Gregory Streets Savannah GA 31404c Tel: 912 447 6622s Fax: 912 201 0096i ICQ#: 130698221,   ------------------------------  % Date: Tue, 02 Oct 2001 22:48:17 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>s' Subject: Re: FAQ September 2001 editionh& Message-ID: <3BBA8A81.AD177E6@fsi.net>   Hoff Hoffman wrote:  > l > In article <3BB90FDE.1454CE9F@ipl.demon.co.nospam.uk>, Steve Reece <SYSTEM@ipl.demon.co.nospam.uk> writes:I > :Last time I looked the VMS web site had an edition of the VMS FAQ from J > :about the 10th Sep 2001 on it but I've been unable to find a plain text > :version of this release.e > :UH > :Looking at the VMS website a moment or two ago, the September releaseK > :seems to have been replaced by the April release again so I'm confused!!  > : < > :Did I miss it in the newsgroup or did events overtake it? > G >   No such FAQ edition exists and no such edition has even shipped off F >   my disk.  (The update is underway at present, but not ready to go.E >   I've picked up text and created sections for Encompass and on thea- >   OpenVMS Itanium in weeks since CETS2001.)c > F >   I do not know why the dates on the OpenVMS website copy of the FAQ >   changed.  G Directory dates for the freeware CD paths are in the Sep-2001 range. V4h! is substantially older than that.a   -- x David J. Dachteras dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/u   ------------------------------  # Date: Tue, 02 Oct 2001 21:47:47 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)= Subject: Re: Fw: Best Way to do Interprocessing Communication 1 Message-ID: <7Cqu7.962$YP.25664@news.cpqcorp.net>i  c In article <002801c14afb$c19cccd0$8149130a@WWS006>, "Martin Hoogenboom" <martinh@xs4all.nl> writes:o> :I think Event Flags were also lost. Oke, its simple and smallB :communication, but it works and if your'e only wating for another :process's signal ....  K   And you will almost invariably get cornered by the use of event flags as mK   the application requirements expand.  I've been tripped up by the use of tJ   event flags as a communications mechanism on more occasions than I wish H   to count -- and when you get cornered by the limits of the event flag B   mechanism, things can really get interesting in the source code.  K   I've learned that the inclusion of a generic communications interface is cI   critical for applications communications -- if I can get a package, all.H   the better.  In any event, you will want to avoid embedding knowledge G   of underlying mechanisms (event flags, shared memory, various networkiH   protocols, etc) throughout the application code, as the communicationsH   requirements will almost certainly change (and will usually increase)    over the years.t  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  $ Date: Tue, 2 Oct 2001 14:57:54 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>   Subject: Re: Good bye VAX-6400's$ Message-ID: <3bba0e54$1@news.si.com>  * >Got any extra you'd consider selling? 8-) >k> >I've got a rack mount TU58-CA with both drive pucks gone. 8-(  K I'm not sure who's got 'em.  Some guy in the manufacturing area.  I'll haved	 to check.  --A Brian Tillman                   Internet: tillman_brian at si.comaA Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to preventa< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Tue, 02 Oct 2001 22:27:08 -0500a1 From: "David J. Dachtera" <djesys.nospam@fsi.net>   Subject: Re: Help with UNZIP.EXE' Message-ID: <3BBA858C.7946006C@fsi.net>s   Paul Repacholi wrote:  > 5 > "David J. Dachtera" <djesys.nospam@fsi.net> writes:- > F > > The entire "Zip/Unzip for OpenVMS: Secrets Revealed!" presentationE > > can be viewed on-line or downloaded (.PDF, .PS, .PPT) starting at.& > > http://www.djesys.com/vms/support/ > A > > Too bad CETS-2001 panned it. Obviously, this info. need to ben > > further disseminated.r > B > Lucky CETS-2001 panned it, or the unwash mass of us would not be > *allowed* to read it...4  : Um, well, actually I posted it circa. Fall '99 DECUS time.   *SIGH*  G Expect an updated version sometime this winter. I just revised parts ofD3 it for a CARTS LUG meeting this Wed.'s, 4-Oct-2001.e   -- e David J. Dachterat dba DJE Systemsa http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/q   ------------------------------  # Date: Wed, 03 Oct 2001 01:10:50 GMTe' From: fraley@usfca.edu (Michael Fraley)o; Subject: Help! OpenVMS 7.3 and COGNOS Powerhouse 7.10.E1???o; Message-ID: <slrn9rkpdt.b8.fraley@cumquat.ca.sprintbbd.net>o  E Is anyone running COGNOS Powerhouse 7.10.E1 or higher on OpenVMS 7.3?uJ We can't get confirmation of compatibility from COGNOS... they say "try it( and see if it works". Can anyone advise?   -- t     Michael Fraley   fraley@usfca.edu   http://www.usfca.edu/~fraley   ------------------------------  % Date: Tue, 02 Oct 2001 22:35:29 -0500-1 From: "David J. Dachtera" <djesys.nospam@fsi.net>0Y Subject: Re: I WILL QUIT USING VMS WHEN THE MILITARY DOES - IN 2015 OR MAYBE LONGER! LONGn' Message-ID: <3BBA8781.69FB145E@fsi.net>D   Paul Sture wrote:d > P > In article <L45u7.63375$vq.11577764@typhoon.ne.mediaone.net>, Terry C. Shannon > wrote:7 > > "John McLean" <mcleanj@dplanet.ch> wrote in messagen( > > news:3BB8DB94.1C60B87F@dplanet.ch... > > >" > > >p > > > "Terry C. Shannon" wrote:  > > 	 > > > > >n > > > > P > > > > It gets worse. Seems that the next US aircraft carrier (due 2007/2008 orL > > > > so), CVN such-and-such, will sport a Windoze-based battle management > > system.oO > > > > I am sure that rivals and potential enemies of the USA are delighted byi > > this > > > > Stupid Strategy Trick. > > >g< > > > Now that's what I call a Microsoft fRight sTimulator ! > > >l > >e" > > No doubt. I can see it now.... > >aD > > DO YOU WANT TO ACTIVATE THE PHALYNX CLOSE-IN AIR DEFENSE SYSTEM? > >aM > > DO YOU *REALLY* WANT TO ACTIVATE THE PHALYNX CLOSE-IN AIR DEFENSE SYSTEM?  > > 
 > > ETC... > >eM > > And the last thing the guys and gals in the Combat Information Center sawt
 > > was... > >h" > > CLIPPIT THE DANCING PAPERCLIP. > > L > Oh, there is something worse than the paperclip, hard as it may seem, it's! > their rendition of Shakespeare.e  $ Alas, poor Billy, I knew him well...   -- e David J. DachteraB dba DJE Systemsl http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/I   ------------------------------  $ Date: Tue, 2 Oct 2001 23:25:26 +02006 From: "Paul Blenderman" <Paul.Blenderman@micronas.com># Subject: Re: imherited cluster helpl- Message-ID: <9pdb97$c3h$1@seebuck.freinet.de>/  H Especially because you used "cluster" in the subject: take a look at the SYSMANB utility's SET ENVIROMENT /NODE or /CLUSTER and DO commands. WithinL the cluster you would in general not even have to enter a username/password.   Paul Blendermand
 Micronas GmbH, Freiburg, Germanyv  * "ron" <ron@cyberping.com> wrote in message. news:rctt7.3331$bb7.87950@news.easynews.com...* > I have inherited VMS and need some help. >e > I need to be able :- >-5 > rsh from one box to sever others boxes and do a set  > of commands. ><8 > for security reasons I don't want to leave my username > and password visible.  >lJ > How can I setup something that prompts me once for user/pass then parses > that to all the rsh commands.d >n > eg.w > rsh box1 "sh users"3 > rsh box2 "sh users"t > rsh box3 "sh users"h >o > Any help greatly appreciated.e >@ >c   ------------------------------  # Date: Tue, 02 Oct 2001 22:31:31 GMTa3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk>"# Subject: Re: imherited cluster help / Message-ID: <3BBA3F32.87326CBC@cableinet.co.uk>k   Paul Blenderman wrote: > J > Especially because you used "cluster" in the subject: take a look at the > SYSMAND > utility's SET ENVIROMENT /NODE or /CLUSTER and DO commands. WithinN > the cluster you would in general not even have to enter a username/password. >  > Paul Blendermanh > Micronas GmbHi > Freiburg, Germanyu  E sure, but that seems quite a dangerous solution for someone who can't H even write a small .COM to read the password without echo then loop thru a list of nodes doing an rsh.8  C If I had a VMS prompt I might even be gullible enough to write it. e   regardsV   > , > "ron" <ron@cyberping.com> wrote in message0 > news:rctt7.3331$bb7.87950@news.easynews.com..., > > I have inherited VMS and need some help. > >a > > I need to be able :l > > 7 > > rsh from one box to sever others boxes and do a set. > > of commands. > > : > > for security reasons I don't want to leave my username > > and password visible.F > >1L > > How can I setup something that prompts me once for user/pass then parses! > > that to all the rsh commands.: > >. > > eg.e > > rsh box1 "sh users"- > > rsh box2 "sh users"  > > rsh box3 "sh users"r > >i! > > Any help greatly appreciated.t > >k > >u   -- R Tim.Llewellyn@cableinet.co.uk  u  C Standard disclaimer applies. My views in no way represent those of e! my employers or service provider.S   ------------------------------  # Date: Wed, 03 Oct 2001 01:55:59 GMTr2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)L Subject: Re: Itanium and Bi-endianism (was: Re: Ben Rosen the real culprit?)1 Message-ID: <Peuu7.968$YP.25651@news.cpqcorp.net>n  <   Ah, a discussion that seems to go on without endian... :-)  N In article <9pdq8q$83q@web.nmti.com>, peter@abbnm.com (Peter da Silva) writes:- :In article <3BB7D087.D609816A@videotron.ca>,n0 :JF Mezei  <jfmezei.spamnot@videotron.ca> wrote:J :> Consider that unless proven otherwise, Tru64 is as good as dead. Once aI :> customer accepts that, he also accepts that full migration to another cK :> platform will be necessary at which point endianness becomes irrelevant.  :t! :I think endianness is overrated.t  B   That depends on the endianness of the data you are dealing with.E   XDR and htonl and such certainly have their place, particularly if  /   you are sharing data of differing endianness.e   ..  H   Based on the information I have, Itanium systems can operate entirely I   bi-endian, with the prefered endianness apparently fully selectable at fH   run-time on a per-process basis.  (I don't really have the inclinationH   to try adding RUN/DETACH/ENDIAN=BIG into OpenVMS right now, but adding0   /ENDIAN=LITTLE might be a good easter egg. :-)    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 02 Oct 2001 16:28:47 -0400l- From: JF Mezei <jfmezei.spamnot@videotron.ca>s) Subject: Re: Letter from Michael Cappelast, Message-ID: <3BBA2379.6FE6DEAA@videotron.ca>   Larry Kilgallen wrote:C > Paul, you are really out of it if you did not realize that Compaq@" > is still stuck on Wintel PCs :-)  L While washing my navel in the shower this morning, I started to wonder about this whole merger business.   L When Compaq bought Digital, there were high hopes that Compaq would maximizeF the potential of Digital's enterprise systems to complement its WintelM offererings.  But in hindsight, Compaq bought the service division as well asrI Digital's very loyal customer base and never had intentions of leveraging&  stuff like Alpha, VMS and Tru64.  J Compaq's core business has the storage and the wintel servers. The rest isD either not profitable, not core or doesn't bring anything new to HP.  K Carly said that they would focus on industry standard solutions. We alreadyAM know that Tru64 is dead, and so far, nothing was said about VMS other that by,? porting to IA64, they are not yet ready to announce VMS' death.a  J My conclusion is that HP is buying Compaq to eliminate a competitor in theM wintel business. HP stood to gain customers who were disenchanted by Compaq'soI handling of Alpha, VMS and Tru64, but by buying Compaq, they ensured thatoM these customers would go to Sun or IBM. So from the "enterprise" side, it cana be argued that HP loses.  M Now, if HP is spending megabucks to get Compaq's wintel business. The logicaldT conclusion is that HP wants to grow its wintel business and make it more profitable.  H At least Pfeiffer pretended that he was buying Digital to give Compaq anN "enterprise" business. HP doesn't even make that statement. It would thereforeJ seem to me that HP is interested in developping itw wintel business and is$ willing to spend megabucks to do so.  N There is therefore no reason to hope that HP will be a saviour and rescue VMS.I It will be business as usual with VMS ignored and tolerated as long as itc' doesn't steal any business from Wintel.=   ------------------------------  % Date: Tue, 02 Oct 2001 16:57:58 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>f) Subject: Re: Letter from Michael Cappelasi, Message-ID: <3BBA2A4E.573C785D@videotron.ca>   Warren Spencer wrote:sM > I hope one day CEO's can learn to write letters devoid of such ambiguities.e$ > Unlikely in my lifetime, I'm sure.  H There is a clear plan. But it is just not politically correct to make itK public. Meanwhile, they use wishy washy language to attempt to give us some-) reassurance that things are looking rosy.    ------------------------------  $ Date: Tue, 2 Oct 2001 16:56:40 -0400' From: "Bill Todd" <billtodd@foo.mv.com> ) Subject: Re: Letter from Michael Cappelas ( Message-ID: <9pd9ib$n1q$1@pyrite.mv.net>  7 "Peter LANGSTOEGER" <eplan@kapsch.net> wrote in messages" news:3bb9a368@news.kapsch.co.at...   ...g  K > And don't forget that INTEL pays them ~93% of the ad only because of thisf logo. D > So, 100% for Alphas vs. 7% for the INTELs. This makes it extremely	 plausiblepC > why the Q marketing/advertizing folks choose to do it this way...e  I Not entirely:  after all, does it make more sense to spend $7 marketing ayF product that produces only about enough profit to cover that $7 (i.e.,L breaks about even) or to spend $100 on a product that returns better than anF order of magnitude more in profit?  Devote your entire business to theJ former, and you break even; devote it to the latter, and you make out likeH crazy, at least up to the point where the market is saturated (and givenK Alpha's share of the market, saturation seems likely to be a long way off).:  F The only way it makes sense is to prepare for a future that you firmlyL believe will be exclusively Wintel, in which case doing whatever it takes toL build market share now *may* be reasonable - though even then it's not clearL why one would pass up the opportunity to make some additional cash along the way.   - bill   ------------------------------  % Date: Tue, 02 Oct 2001 23:05:52 +0200b& From: John McLean <mcleanj@dplanet.ch>) Subject: Re: Letter from Michael Cappelas * Message-ID: <3BBA2C30.AF5CCFC7@dplanet.ch>   Sue Skonetski wrote: >  > Dear Newsgroup,  > L > I have just received this and thought you might want to see it.  Please be6 > aware that not everyone (Compaq) may have seen this. >  > September 28, 2001 >  > Dear Customer: >    etc.  F Sorry Sue, you seem to get a negative response over most Compaq thingsF that you post here.  Many of us actually feel sorry for you because of# the difficult situation you are in.   A Perhaps it could be eased if you could tell Compaq management thet
 following:  F (a) we in c.o.v. are technically-savvy, not gullible people who accept marketing drivel.!A (b) we are not PC users who believe that Microsoft is a wonderfula companywH (c) many of us are older than Michael Capellas and have worked in IT for longer than he hasG (d) most of us seem to understand the potential uses for VMS far better  than Compaq's marketing folkG (e) we would like Compaq to stop using the word "commitment" until sucheF time that Compaq's actions cause us to stop equating their use of that word with "fantasy"@E (f) we would much prefer factual information about VMS, regardless ofpI whether it is positive or negative, so that we can plan for the future.     F In exchange, we will try to support VMS to increase its sales, as much8 as we can do within the bounds of honesty and integrity.   Fair deal ?e     John McLean    ------------------------------  $ Date: Tue, 2 Oct 2001 17:10:56 -0400+ From: "Chris Moore" <mc.moore@sympatico.ca>e) Subject: Re: Letter from Michael Cappelasn: Message-ID: <N_pu7.9432$4l5.1592525@news20.bellglobal.com>  J An excellent summation David.  Sadly, I have to agree with you completely.K I have just read an article that compares the HP-CPQ mess to the debacle ofeC Excite and @Home, which has just now ended in Chapter 11.  Too manysB parallels in the (mis)management approaches of these to be ignored    4 "David Mathog" <mathog@caltech.edu> wrote in message% news:3BB894F8.5B1417B3@caltech.edu...a > Sue Skonetski wrote: >h > > Dear Newsgroup,  > >.K > > I have just received this and thought you might want to see it.  Please  be8 > > aware that not everyone (Compaq) may have seen this. > >o > > September 28, 2001 > >o > > Dear Customer, >- > <SNIP>I > If he really cared about either the company or its customers this wouldz have- > said "I'm resigning effective immediately".aL > Since it's MC it would have taken 2000 words but that should have been the
 > message. > I > The document that Sue forwarded to us is unfortunately another steamingr pile oflD > Compaq err, platitudes, some tiny fraction of which may or may not actuallyC > bear a slight resemblance to reality.   This sickening thing usespH > "plan-of-record" three times.  They  have to qualify like that because theyL > have provided so many false and misleading statements and "plans" over theE > years that they must now  specify which set of half truths and liesr they'ren* > referring to in any given communication. >c: > Below are several "clear statements" _I_ can make today: >a; > 1.  I don't believe anything that Compaq management says.dL > 2.  I have zero faith that Compaq can or will deliver on any of its stated > commitments.J > 3.  I believe we have more than enough evidence already that neither the CEO ofB > HP nor the CEO of Compaq is able to run a major computer company
 successfully. K > 4.  I believe even more strongly that neither of these two individuals isaL > capable of merging  two failing entities into a single successful concern.L > 5.  I suspect that, aside from company management,  the only beneficiaries of1 > the merger will be HP and Compaq's competitors.iI > 6.  I think it probable that after the merger the whole enterprise will- simplyC > collapse in an orgy of mismanagement and corporate culture shock. I > 7.  I think the debacle will be so extreme that it may even destroy the- piecesG > that should have  been spun off into viable separate companies:  HP'sT	 printers,l > Tandem, and VMS. >n >w
 > Regards, >: > David Mathog > mathog@caltech.edu >b   ------------------------------  % Date: Tue, 02 Oct 2001 22:40:21 -0500v1 From: "David J. Dachtera" <djesys.nospam@fsi.net>n) Subject: Re: Letter from Michael Cappelas ' Message-ID: <3BBA88A5.E2FF2009@fsi.net>d   Paul Sture wrote:a > ? > In article <3BB8DE75.529B050E@dplanet.ch>, John McLean wrote:s > > Sue Skonetski wrote: > > >  > > > Dear Newsgroup,o > > >0 > >e > > ..... (snip) > >dQ > > > As our track record over multiple decades clearly proves, we understand theiF > > > importance of your commitment to our mission critical platforms. > >-L > > Another fragment of credibility gone.  Compaq has been around since 1982H > > (ie. about 2 decades) and only ever dealt with PC's until about 1996G > > when Tandem was purchased.  Hands up all those people who associateD! > > mission-critical with PC's ??i > > M > I'll second that. If you look at the corporate home page, it clearly statesaH > that Compaq was founded in February 1982. Not 2 decades yet, let aloneG > "multiple decades". I searched in vain for a reference to HP's longernM > history, but no, it was clearly signed as a Compaq letter (even a referencekF > to DEC/Digital/Tandem would have sufficed to justify the statement). > N > And watching the soccer this weekend, they are _still_ blasting the airwavesJ > with PC adverts - with a PIII logo in the bottom left hand corner, would- > you believe, so even _that_ is out of date.-  F Remember what happened to the last Compaq product that got any kind of> advertising in Europe or the UK? (Hint: Think OpenVMS, Alpha).   -- o David J. Dachtera- dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/H   ------------------------------  % Date: Tue, 02 Oct 2001 22:42:22 -0500.1 From: "David J. Dachtera" <djesys.nospam@fsi.net>u) Subject: Re: Letter from Michael Cappelasn' Message-ID: <3BBA891E.4BB6C51A@fsi.net>    JF Mezei wrote:o >  > Larry Kilgallen wrote:E > > Paul, you are really out of it if you did not realize that Compaq $ > > is still stuck on Wintel PCs :-) > 8 > While washing my navel in the shower this morning, ...  ( That's more than I needed to know, JF...   *HORK* *HURL* *CHOKE* *GAG*0   -- c David J. DachteraU dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/e   ------------------------------  # Date: Wed, 03 Oct 2001 03:37:16 GMTe4 From: "Terry C. Shannon" <terryshannon@mediaone.net>) Subject: Re: Letter from Michael Cappelass= Message-ID: <MJvu7.68523$vq.12915234@typhoon.ne.mediaone.net>C  < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3BBA88A5.E2FF2009@fsi.net...a > Paul Sture wrote:2 > >rG > > And watching the soccer this weekend, they are _still_ blasting thee airwavesL > > with PC adverts - with a PIII logo in the bottom left hand corner, would/ > > you believe, so even _that_ is out of date.r >.H > Remember what happened to the last Compaq product that got any kind of@ > advertising in Europe or the UK? (Hint: Think OpenVMS, Alpha). >   E Yes, the peecee ads featuring the Presario and the ever-popular IntelEE Xylophone Orchestra have reared their ugly heads on US teevee as well 4 (they're running several times a night on Fox News).  ? Could this mean that the Presario will share the fate of Alpha?L   ------------------------------  $ Date: Mon, 1 Oct 2001 22:45:49 +0100/ From: "Gerald Marsh" <gerald@cyfer.demon.co.uk>e5 Subject: Re: Locate Filename containing logical blockmB Message-ID: <1002050322.19712.0.nnrp-02.9e984c92@news.demon.co.uk>   Or.../  L Dig up the old DECUS FIND utility - It still works under VMS7.2 on Alpha butA (IRC) is rather heavy on memory usage. I think it attempts to map+ INDEXF.SYS!P   The command is something like:% FIND/LBN=n/DISPLAY=(OWN,CRE) <device>u  H Send me an email if you want the URL but it's probably on a freeware CD.   Keep up the good work!   Gerald.t     -- Gerald Marsh   Email: gerald@cyfer.demon.co.ukO  3 "John McLean" <mcleanj@dplanet.ch> wrote in message $ news:3BB8DCCA.84FE0289@dplanet.ch... >  >r# > norm.raphael@jamesbury.com wrote:i > >s/ > > I have a shadowset on RZ28-M's that logs ang7 > > unrecoverable media error on logical block 00334339s6 > > whenever I do a full backup from another system in5 > > the cluster to which its members are mscp-served.  > > : > > Is there a way to tell which file contains that block? > >a, > > (Analyze/READ does not show any errors.) >s >dI > You might get some idea if you look at the contents of the disk at thata > point. >sA > Try DUMP/BLOCK=(START:334339,COUNT:1)  <disk_id>  (eg. DKA200:)s > J > If you use the physical device instead of a filename, you should get the > logical block. >-D > Change the value of COUNT to see a few more blocks if you want to. >m >i
 > John McLeanm   ------------------------------  $ Date: Tue, 2 Oct 2001 16:34:51 -0400  From: norm.raphael@jamesbury.com5 Subject: Re: Locate Filename containing logical blockc4 Message-ID: <C2256AD9.007106DF.00@jklh21.valmet.com>  E The current speculation is that this block is an alternate homeblock.nF It is not in a file, but is read by BACKUP/IMAGE, producing the error.N It is marked Force-error, but unless the disk is restored it will not go away.9 Any support or refutation of this speculation is welcome.o        2 gerald@cyfer.demon.co.uk on 10/01/2001 05:45:49 PM  * Please respond to gerald@cyfer.demon.co.uk   To:   Info-VAX@mvb.saic.comV cc:o6 Subject:  Re: Locate Filename containing logical block         Or...   L Dig up the old DECUS FIND utility - It still works under VMS7.2 on Alpha butA (IRC) is rather heavy on memory usage. I think it attempts to map  INDEXF.SYS!e   The command is something like:% FIND/LBN=n/DISPLAY=(OWN,CRE) <device>   H Send me an email if you want the URL but it's probably on a freeware CD.   Keep up the good work!   Gerald.      -- Gerald Marsh   Email: gerald@cyfer.demon.co.ukr  3 "John McLean" <mcleanj@dplanet.ch> wrote in messages$ news:3BB8DCCA.84FE0289@dplanet.ch... >s > # > norm.raphael@jamesbury.com wrote:3 > >u/ > > I have a shadowset on RZ28-M's that logs an 7 > > unrecoverable media error on logical block 00334339t6 > > whenever I do a full backup from another system in5 > > the cluster to which its members are mscp-served.- > >-: > > Is there a way to tell which file contains that block? > > , > > (Analyze/READ does not show any errors.) >j >:I > You might get some idea if you look at the contents of the disk at thatg > point. >9A > Try DUMP/BLOCK=(START:334339,COUNT:1)  <disk_id>  (eg. DKA200:)g >nJ > If you use the physical device instead of a filename, you should get the > logical block. >wD > Change the value of COUNT to see a few more blocks if you want to. >e >p
 > John McLean.   ------------------------------   Date: 2 Oct 2001 18:18:21 -0700d1 From: keithparris_NOSPAM@yahoo.com (Keith Parris) 5 Subject: Re: Locate Filename containing logical blocki= Message-ID: <cf15391e.0110021718.77d60f91@posting.google.com>   ! norm.raphael@jamesbury.com wrote:tG > The current speculation is that this block is an alternate homeblock.   E If this is the case, the failing LBN will be in one of the allocationoF areas for the INDEXF.SYS file itself, since the backup home blocks are mapped as part of that file.C -------------------------------------------------------------------pC Keith Parris | parris at encompasserve dot org | VMS consulting on:IC Clusters, Disaster Tolerance, Internals, Performance, Storage & I/O=   ------------------------------  % Date: Wed, 03 Oct 2001 07:01:44 +0200s& From: John McLean <mcleanj@dplanet.ch>5 Subject: Re: Locate Filename containing logical block-* Message-ID: <3BBA9BB8.B563DAD7@dplanet.ch>  C Did you dump the logical block and a few blocks around it as per my ; posting yesterday ?  Was it anything vaguely recognisable ?n  H How many files are on this disk ?  It may sound like a dumb question butH if there are a relatively small number you could dump all the headers toB a file and take a look.  I know of some large disks that have only5 contained about 20 files but had only 10% free space.>   John McLeanl    ! norm.raphael@jamesbury.com wrote:o > G > The current speculation is that this block is an alternate homeblock. H > It is not in a file, but is read by BACKUP/IMAGE, producing the error.P > It is marked Force-error, but unless the disk is restored it will not go away.; > Any support or refutation of this speculation is welcome.e > 4 > gerald@cyfer.demon.co.uk on 10/01/2001 05:45:49 PM > , > Please respond to gerald@cyfer.demon.co.uk >  > To:   Info-VAX@mvb.saic.coml > cc:e8 > Subject:  Re: Locate Filename containing logical block >  > Or...n > N > Dig up the old DECUS FIND utility - It still works under VMS7.2 on Alpha butC > (IRC) is rather heavy on memory usage. I think it attempts to mapH
 > INDEXF.SYS!d >   > The command is something like:' > FIND/LBN=n/DISPLAY=(OWN,CRE) <device>r > J > Send me an email if you want the URL but it's probably on a freeware CD. >  > Keep up the good work! > 	 > Gerald.d >  > -- > Gerald Marsh > ! > Email: gerald@cyfer.demon.co.uka > 5 > "John McLean" <mcleanj@dplanet.ch> wrote in messagem& > news:3BB8DCCA.84FE0289@dplanet.ch... > >i > > % > > norm.raphael@jamesbury.com wrote:p > > >y1 > > > I have a shadowset on RZ28-M's that logs anI9 > > > unrecoverable media error on logical block 00334339H8 > > > whenever I do a full backup from another system in7 > > > the cluster to which its members are mscp-served.a > > >g< > > > Is there a way to tell which file contains that block? > > >f. > > > (Analyze/READ does not show any errors.) > >a > > K > > You might get some idea if you look at the contents of the disk at thate
 > > point. > > C > > Try DUMP/BLOCK=(START:334339,COUNT:1)  <disk_id>  (eg. DKA200:)o > >dL > > If you use the physical device instead of a filename, you should get the > > logical block. > > F > > Change the value of COUNT to see a few more blocks if you want to. > >o > >  > > John McLeans   ------------------------------  # Date: Tue, 02 Oct 2001 20:27:26 GMT1' From: Zelmo Kitowski <Zelmo@^Hkiwi.net>.& Subject: Re: NT or w2k on alpha 1200 ?? Message-ID: <Xns912E890609B9D9874JK325999HR657893@24.9.139.141>r   I'm interested, now curious.    ) Alan Greig <a.greig@virgin.net> wrote in t0 news:3j69pts8ncsflker1a10tunveodu9uafuc@4ax.com:  B > On 3 Sep 2001 16:20:53 -0700, nothome@spammers.are.scum (Malcolm > Dunnett) wrote:m > G >>   For us mere mortals it seems a version more recent than beta ( wass1 >>   it Release Candidate 1? ) is not to be had.   > A > It has ben reported several times that copies of the Gold final0E > release were made available within Microsoft and that there are ftpc% > sites where this could be obtained.$ >  >> >  > -- > Alan   ------------------------------  # Date: Tue, 02 Oct 2001 20:31:59 GMTp4 From: "Terry C. Shannon" <terryshannon@mediaone.net>& Subject: Re: NT or w2k on alpha 1200 ?= Message-ID: <3vpu7.67331$vq.12585404@typhoon.ne.mediaone.net>i  L Win2K Professional for Alpha Build 2128 can be had if you know where to look	 for it...h  4 "Zelmo Kitowski" <Zelmo@^Hkiwi.net> wrote in message9 news:Xns912E890609B9D9874JK325999HR657893@24.9.139.141...y > I'm interested, now curious. >$* > Alan Greig <a.greig@virgin.net> wrote in2 > news:3j69pts8ncsflker1a10tunveodu9uafuc@4ax.com: >gD > > On 3 Sep 2001 16:20:53 -0700, nothome@spammers.are.scum (Malcolm > > Dunnett) wrote:o > > I > >>   For us mere mortals it seems a version more recent than beta ( was 2 > >>   it Release Candidate 1? ) is not to be had. > >mC > > It has ben reported several times that copies of the Gold finalyG > > release were made available within Microsoft and that there are ftpb' > > sites where this could be obtained.  > >v > >> > >  > > -- > > Alan >e   ------------------------------  # Date: Wed, 03 Oct 2001 04:05:23 GMT , From: Adam Stouffer <astouffer@adelphia.net>& Subject: Re: NT or w2k on alpha 1200 ?( Message-ID: <3BBA8E4D.766F@adelphia.net>   Terry C. Shannon wrote:  > N > Win2K Professional for Alpha Build 2128 can be had if you know where to look > for it...3 >   / So can we narrow it down to a site or a person?        Adam   ------------------------------  % Date: Tue, 02 Oct 2001 21:42:07 -0400 . From: Chuck McCrobie <mccrobie@cablespeed.com> Subject: ODS-2 for FreeBSD. Message-ID: <3BBA6CEF.4C957B8A@cablespeed.com>  H After reading the posts from Hunter Goatley about the ODS-2 reader, I'veE decided to dust off my NATIVE FreeBSD ODS-2 file system (read-only). sF Its in working order, but needs improvement.  I plan on donating it toH the FreeBSD project under the BSD license, so if anyone wishes to try itB / use it in a product, please contact me.  Source is available andF binaries can be had.  Currently, it supports FreeBSD I386 v3.3 and 4.?  D I've started some work on an RMS library for FreeBSD which correctlyB handles the record structures and potentially file organizations. F However, since this is a hobby project, not much has been done on it. E Perhaps some enterprising programmer can modify the ODS-2 reader from = Mr. Goatley and friends for use with this file system driver.o  G Sorry, its for FreeBSD only :(  (Maybe portable to other Unix flavors -aC A Windows NT/2000/XP file system driver is possible, but that would C require incentive ;)  Just to be complete, there is a product which B wraps a FreeBSD file system with the Windows NT file system driverH stuff, so it might be less complicated to use this file system driver to$ wedge in an NT file system driver...  - If anyone is interested, please contact me...r   Chuck McCrobie   -- : --L   ------------------------------  $ Date: Tue, 2 Oct 2001 15:17:43 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>eA Subject: Re: ODS2 available -- reads ODS-2 disks on Windows, UNIXm$ Message-ID: <3bba12f9$1@news.si.com>  H >Well, that seems to be the big question about ASPI in general.  An ASPIK >interface is needed, and you can find some out there, but legally, I don'tMG >think they're supposed to be redistributed (at least, I'm not going toe	 >try it).   J The README file that comes with WNASPI32.DLL says it can be redistributed,! but not as part of anything else.t  K At any rate, since I have CDex on my PC, I used it and WOW!  So cool!  It's., nice to be able to examine VMS CDs on my PC. --A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to preventb< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  # Date: Tue, 02 Oct 2001 21:28:53 GMTm2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 1/5t1 Message-ID: <pkqu7.957$YP.25608@news.cpqcorp.net>y   Archive-name: dec-faq/vms/part1  Posting-Frequency: quarterly Last-modified: 2 Oct 2001t Version: VMS-FAQ-1.TXT(7)      Changes since last edition ==========================, Numerous URL and minor text updates, plus...: Add DOC13        What OpenVMS mailing lists are available?F Add DOC14        What is this Ask The Wizard website I've heard about?/ Update INTRO8    reflect organizational changest3 Add ITAN1        OpenVMS is porting to Intel IA-64? ; Add ITAN2        Where can I get Intel Itanium information?e6 Add MAIL10       How can I block SMTP mail relay spam?A Add MISC22       How do I convert?  Disk Blocks?  KB, MB, GB, TB?tG Update MGMT3     VMS File System Internals book reportedly out of print  Update MGMT14    sub/STS/SYS/ * Update MGMT16    Add V7.3 to upgrade pathsB Add MGMT61       Explain disk (or tape) allocation class settings?F Add MGMT62       How to prevent users from choosing obvious passwords?8 Add MGMT63       Volume Shadowing MiniCopy vs MiniMerge?7 Add MGMT64       Why is BACKUP not working as expected? * Add PROG22       Dealing with Endian-ness?7 Add PROG23       How to resolve LINK-I-DATMISCH errors?f Update SOFT1     XPDF, etc Update SOFT4     Tomcat, etc5 Update SOFT5     sequence points, argument evaluation 9 Add TIME13       Customizing your TDF (Timezone) Setting? < Add VMS17        memory management, resource management, ...    E This is part 1/5 of the Frequently Asked Questions (FAQ) posting for  = the comp.os.vms and comp.sys.dec newsgroups.  (comp.os.vms is C bidirectionally-gatewayed to the INFO-VAX mailing list - see INTRO3 > 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.)       Table of Contents - Part 1/5 ____________________________     OVERVIEW( ========================================C OV1.     Overview of the OpenVMS FAQ, Updates, Editor, Contact InfoP   Introduction( ========================================* INTRO1.  What is the scope of comp.os.vms?= INTRO2.  What other newsgroups carry VMS-related information?l 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 Encompass (DECUS)? = INTRO7.  What archives of comp.os.vms/INFO-VAX are available?eD INTRO8.  Who are the corporate contacts for OpenVMS business issues?   General questions about OpenVMSg( ========================================. 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?i3 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?e? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?e? VMS12.  Are there any general-access OpenVMS systems available? * 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?H VMS17.  memory management, resource management, process scheduling, etc?    ! Documentation and other resourceso( ========================================: DOC1.   Where can I find online copies of OpenVMS manuals?- DOC2.   What online information is available?o2 DOC3.   What books and publications are available?5 DOC4.   How do I extract a HELP topic to a text file?76 DOC5.   Does OpenVMS Marketing have an e-mail address?5 DOC6.   What OpenVMS-related WWW sites are available?sB 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?eD DOC11.  Where can new users find tutorial information about OpenVMS?C DOC12.  How to access the OpenVMS Netscape Navigator documentation?d1 DOC13.  What OpenVMS mailing lists are available? = DOC14.  What is this Ask The Wizard website I've heard about?t   OpenVMS System Times( ========================================8 TIME1.   A brief history of OpenVMS Timekeeping, please?3 TIME2.   How does OpenVMS VAX maintain system time? ' TIME3.   Why does my system time drift? D TIME4.   Managing Timezones, Timekeeping, UTC, and Daylight Savings?5 TIME5.   How to troubleshoot TDF problems on OpenVMS?p= TIME6.   How can I keep the OpenVMS system time synchronized? D TIME7.   How can I configure TCP/IP Services NTP as a time provider?1 TIME8.   How can I drift the OpenVMS system time? ; TIME9.   Why does VAX need a SET TIME at least once a year?o@ TIME10.  Why can't I do a SET TIME command?  Help managing DTSS?4 TIME11.  Details of the OpenVMS system time-keeping?D TIME12.  UTC vs GMT vs vs UT1/UT1/UT2 TDF?  What are these acronyms?1 TIME13.  Customizing your TDF (Timezone) Setting?<   Table of Contents - Part 2/5 ____________________________   System Management.( ========================================# MGMT1.  What is an installed image?y0 MGMT2.  Are there any known viruses for OpenVMS?1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?n4 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?h; MGMT9.  How do I change the node name of an OpenVMS System?sE 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?e3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSC 4 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?aC MGMT18. Do I have to update layered products when updating OpenVMS?a3 MGMT19. How do I change the volume label of a disk?l. 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?b: 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?t> MGMT28. How do I set a default IP route or gateway on OpenVMS?C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?k* 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?.. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?; MGMT36. How can I set up reverse telnet (like reverse LAT)?e? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?o6 MGMT38. INITIALIZE ACCVIO and ANSI tape label support?/ MGMT39. How do I recover from INSVIRMEM errors?.I MGMT40. How can I prevent a serial terminal line from initiating a login?C6 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? 8 MGMT47. Configuring Cluster SCS for path load balancing?; MGMT48. What (and where) is the OpenVMS Management Station?e- 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?9 MGMT56. How do I remove a PCSI-installed patch (ECO) kit?e@ MGMT57. SYSINIT-E, error mounting system device, status=0072832C/ MGMT58. Performing SET HOST/MOP in DECnet-Plus?y' MGMT59. Resolving License PAK Problems?s   Table of Contents - Part 3/5 ____________________________   MGMT (Continued)( ========================================  , MGMT60. Changing the OpenVMS Version Number?9 MGMT61. Explain disk (or tape) allocation class settings?-= MGMT62. How to prevent users from choosing obvious passwords?t/ MGMT63. Volume Shadowing MiniCopy vs MiniMerge?c. MGMT64. Why is BACKUP not working as expected?     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?lA MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.iL 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?k6 MAIL9.  How do I send or read attachments in VMS MAIL?- MAIL10. How can I block SMTP mail relay spam?a     Other Utilitiese( ========================================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?s2 UTIL5.  How do I read IBM EBCDIC tapes on OpenVMS?/ UTIL6.  How can I patch an OpenVMS Alpha image?c     DCL and command usage ( ========================================. DCL1.   How do I run a program with arguments?/ DCL2.   How can I redefine control keys in DCL?t* 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?s% DCL6.   What does the MCR command do?W2 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?h, DCL11.  Use of RUN/DETACH and logical names?8 DCL12.  How to use escape and control characters in DCL?   File System and RMSy( ========================================" 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?e@ 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?u= FILE7.  How do I write recordable CD media (CD-R) on OpenVMS? 7 FILE8.  What I/O transfer size limits exist in OpenVMS?D< FILE9.  Can I use ODBC to connect to OpenVMS database files?     Programmingh( ========================================: PROG1.  How do I call <routine_name> from <language_name>?9 PROG2.  How do I get the arguments from the command line?-= PROG3.  How do I get a formatted error message in a variable?mD 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?rH 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?o? PROG10. How do I get a unique system ID for licensing purposes? ? PROG11. What is an executable, shareable, system or UWSS image? / PROG12. How do I do a file copy from a program?  PROG13. What is a descriptor? + PROG14. How many bytes are in a disk block?d, PROG15. How many bytes are in a memory page?9 PROG16. How do I create a process under another username?rD 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?o0 PROG19. How can I open a file for shared access?> PROG20. How can I have common sources for messages, constants?C PROG21. How do I activate the OpenVMS Debugger from an application?J! PROG22. Dealing with Endian-ness? . PROG23. How to resolve LINK-I-DATMISCH errors?   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?tF 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!a- DECW6.  Why is DECwindows Motif not starting? 3 DECW9.  How do I set the title on a DECterm window? B 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?dE MISC6.    What does "failure on back translate address request" mean? 8 MISC7.    How to determine the network hardware address?B 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?S* 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?sD MISC21.   Third-party disk/tape/controllers/SCSI/widgets on OpenVMS?: MISC22.   How do I convert?  Disk Blocks?  KB, MB, GB, TB?     Software( ========================================C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?l@ SOFT2.    Where can I find the UNIX <whatever> tool for OpenVMS?I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser? + SOFT4.    Where can I get Java for OpenVMS? J SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?1 SOFT6.    Obtaining user input in DCL CGI script?r1 SOFT7.    How do I get my own batch entry number?-0 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? + SOFT12.   Where can I get Perl for OpenVMS?,4 SOFT13.   Where can I get DECmigrate (VEST and TIE)?     Table of Contents - Part 5/5 ____________________________   Alpha and Alpha-based systemsk( ========================================, ALPHA1.   What do the letters AXP stand for?A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?,F ALPHA5.   Seeking performance information for Alpha (and VAX) systems?E ALPHA6.   Where can I get updated console firmware for Alpha systems?eD ALPHA7.   How do I boot an AlphaStation without monitor or keyboard?= ALPHA8.   Will OpenVMS run on a Multia? AlphaPC 164LX? 164SX? C ALPHA9.   What is the least expensive system that will run OpenVMS?o< 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?-0 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?tJ 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?=! ALPHA19.  What is byte swizzling?d? ALPHA20.  What commands are available in the Alpha SRM console?nA ALPHA21.  How do I switch between AlphaBIOS/ARC and SRM consoles?d@ 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 systemsk( ========================================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?eH 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?/ VAX11.  What are the VAX processor (CPU) codes?I   Intel Itanium-based systemsS( ========================================* ITAN1.  OpenVMS is porting to Intel IA-64?2 ITAN2.  Where can I get Intel Itanium information?  ' Hardware and Software Support resources ( ========================================B SUPP1.  Where can I get software and hardware support information?E SUPP2.  Where can I get hardware self-maintenance support assistance?iH 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?uA SUPP5.  Which video monitor works with which graphics controller?y8 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 deade= SUPP9.  Which DE500 variant works with which OpenVMS version?r    ! SCSI-related Hardware information=( ========================================< 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?): WIRES2. What connectors and wiring adapters are available?2 WIRES3. What is flow control and how does it work?  
 Networking( ========================================. NET1.  How to connect OpenVMS to the Internet?) NET2.  How to connect OpenVMS to a Modem?r  < ------------------------------------------------------------@ OV1.  Overview of the OpenVMS FAQ, Updates, Editor, Contact Info    9   The OpenVMS FAQ is archived in the following locations:p  "     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/...)  ?   User-created HTML versions of the OpenVMS FAQ are located at:a       http://www.kjsl.com/vmsfaq'     http://eisner.decus.org/vms/faq.htmm  I Please do NOT send technical questions to the Frequently Asked Questions oH (FAQ) editor -- well, please do not email any questions that do not alsoG include the answer(s).  Please post these questions to the appropriate oI newsgroup instead -- and see INTRO5 before posting.  To make suggestions  G for changes or additions to this FAQ list, please send mail to the FAQ oH editor at the address listed in the sig file.  Again, the FAQ editor is 0 *not* in a position to answer general questions.   Some general notes:n  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 rJ Compaq's Alpha processor architecture.  OpenVMS manual names mentioned areC those as of V7.2 -- names may be different in other editions of the  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 theTD 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 the 
 contribution.F  A Although the editor of this FAQ is an employee of Compaq ComputermA Corporation, this posting is not an official statement of Compaq.a  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 tL 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 eG in the United States and other countries, licensed exclusively through =K X/Open Company Ltd.  Other names are properties of their respective owners.T      < ------------------------------------------------------------* INTRO1.  What is the scope of comp.os.vms?  E The comp.os.vms newsgroup is the primary newsgroup for discussion of  F Compaq's OpenVMS operating system and the computer systems on which itE runs.  Questions about layered products which run on OpenVMS are alsotC welcome, though many of them (in particular, language compilers anduC 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 mostlyn; devoted to Alpha topics.  There's also vmsnet.sources (and  J 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.  G Sprechen Sie Deutsch? Besuchen Sie bitte den newsgroup de.comp.os.vms. p  L The comp.sys.dec newsgroup carries general discussions about various Compaq K computer systems, and specifically systems that were acquired by Compaq as T? part of the acquisition of Digital Equipment Corporation (DEC).   < ------------------------------------------------------------ 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 waysF 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 ofi 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 handledtN 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)  oK Case is irrelevant and attempts to fetch a copy of the mailing list will be J rejected (I consider the information to be confidential).  Any message notI understood by the mailserver will be forwarded to a human (allegedly) forr 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. V  C If you are on the Internet in the UK, send a message containing thetF 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.l  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 n "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 orcD         in a "signature" appended to the end.  Reply-to addresses in 	headers often get garbled.o  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.  aM         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.2M         (The more detailed your description, the better that people can help n          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 mE 	added, you've possibly included too much.  Never include signatures i 	and other irrelevant material.e  E     4.  Be polite.  If the question isn't worded the way you think is.C         correct or doesn't include the information you want, try to > 	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 SB         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 II         posting via email sent to INFO-VAX, please turn off MIME, vcard, hI         attachments, and other mechanisms that assume anyone reading the nJ         post has the corresponding capability -- use the text-only option M         of your web browser, news reader, or mailer.  Usenet is traditionallyGF 	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.cC 	If the message uses MIME or attachments or such, the text of your  E 	message will be buried in a large pile of gibberish, and some tools .? 	will send multiple copies of the text within a single posting.o  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/part1RH   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/part1   G This information will document the etiquette of newsgroups, as well as eF providing you with the knowledge the vast amount of newsgroup-related E information that is readily available to you, and where to find it...s  < 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 lK nefarious use of this same information.  Other sites will hopefully return sJ the favor, and not post information that will potentially compromise YOUR # site and YOUR computer environment.i  < ------------------------------------------------------------# INTRO6.  What is Encompass (DECUS)?A  G Encompass, the Enterprise Computing Association, is a Compaq user group D consisting of information technology professionals interested in theG products, services, and technologies of Compaq Computer Corporation andWJ related vendors. Encompass reaches out to experts and engineers alike, andJ brings them together to promote awareness of and provide solutions for theL real IT problems and challenges your business faces every day. The EncompassL mission is to help you and your organization be more successful by providing. an open, objective knowledge exchange network.  G For more information on Encompass, please visit the Encompass web site:      http://www.encompassus.org/n  4                                         [Jim Becker]  J Encompass is a descendent of the organization known as DECUS, the Digital ! Equipment Computer Users Society.   < ------------------------------------------------------------= INTRO7.  What archives of comp.os.vms/INFO-VAX are available?t  : Everything posted since 1990 is archived and available at:   ftp://crvax.sri.com/info-vax/    					[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 h@   Comoaq Corporate President to the OpenVMS Vice President (VP).     1     Michael Capellas     Compaq President and CEO 9                          Michael.Capellas[-at-]Compaq.Comg  2     Mike Winkler         VP, Global Business Units5                          Mike.Winkler[-at-]Compaq.ComP  =     Howard Elias         VP, Business Critical Solution Group 5                          Howard.Elias[-at-]Compaq.Com   =     Rich Marcello        VP, High Performance Server Division.9                          Richard.Marcello[-at-]Compaq.Com?  8     Mark Gorham          VP, Open Systems Software Group4                          Mark.Gorham[-at-]Compaq.Com  D   These folks will obviously respond best to cogently-worded OpenVMSD   corporate-level business issues.  These folks are NOT appropriate G   contacts for any OpenVMS technical support issues nor for any OpenVMS G   technical support requests, nor for any other non-corporate-related, pF   non-business-related issues.  (For technical issues, please contact D   the local Compaq Customer Support Center or your Compaq Reseller.)  < ------------------------------------------------------------. 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 VMS M operating system, "Starlet", a name that remains to this day the name for the I system library files (STARLET.OLB, etc.).  VMS version X0.5 was the firstiN 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.H  L OpenVMS was designed entirely within Compaq (Digital Equipment Corporation).G The principal designers were Dave Cutler and Dick Hustvedt, with a wide K variety of other contributors.  OpenVMS was conceived as a 32-bit, virtual  J 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 tE RSX-11M, and many concepts from RSX-11M were carried over to OpenVMS.t  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  C operating system. Current implementations run on Alpha systems fromb Compaq, and other vendors.  F Work to port OpenVMS to systems based on the Intel IA-64 architecture E (specifically to the Itanium Processor Family) is presently underway.o   				[Paul Winalski]  				[Arne Vajhj]   G For more details on OpenVMS and its features, read the OpenVMS Softwarei Product Description at:.  !   http://www.compaq.com/info/spd/m:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  A Additional information on the general features of various OpenVMSd@ 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.htmla  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 softwares$ licensing topics VMS9, ALPHA4), see:     http://www.free-vms.org/  < ------------------------------------------------------------7 VMS2.   What is the difference between VMS and OpenVMS?   I VMS and OpenVMS are two names for the same operating system.  Originally,nD 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 the=C Alpha platform, it was renamed OpenVMS, for both VAX and Alpha (andnF for the Itanium Processor Family), in part to signify the high degree E of support for industry standards such as POSIX, which provides many = features of UNIX systems.   H For those versions with POSIX, an OpenVMS license allows you to install G and run POSIX for OpenVMS at no additional charge; all you need is the wL media and documentation which can be found on the Consolidated Distribution I and On-Line Documentation CD-ROMs.  Support for the POSIX package on more H recent OpenVMS releases is not available, various parts of POSIX such asI calls from the API are being integrated more directly into OpenVMS.  For e4 more information on POSIX for VMS see question SOFT2  C What became confusing is that the OpenVMS name was introduced firsteF 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  E the name did not start to be actually used in the product until V6.0.s  G The proper names for OpenVMS on the two platforms are now "OpenVMS VAX"a@ and "OpenVMS Alpha", the latter having superseded "OpenVMS AXP".   				[Arne Vajhj]F  < ------------------------------------------------------------* VMS3.   How do I port from VMS to OpenVMS?  9 You already did.  Wasn't that easy?  (See question VMS2.)e  < ------------------------------------------------------------* VMS4.   Which is better - OpenVMS or UNIX?  M This question comes up periodically, usually asked by new subscribers who areoM long-time UNIX users. Sometimes, it is ignored totally; other times, it leadsaN 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.s 					[leichter@lrw.com].  F Seriously, OpenVMS and the better implementations of UNIX are all fineE operating systems, each with its strengths and weaknesses.  If you'rerE in a position where you need to choose, select the one that best fitsaC your own requirements, considering, for example, whether or not the @ layered products or specific OS features you want are available.   					[Steve Lionel]i  < ------------------------------------------------------------= VMS5.   Is Compaq continuing funding and support for OpenVMS?e   Yes.  ? Active development of new OpenVMS releases is underway, as wellP as the continuation of support.e  @ Please see the following URLs for details, roadmaps, and related information:      http://www.compaq.com/openvms/5   http://www.openvms.compaq.com/OPENVMS/strategy.htmlCD   http://www.openvms.compaq.com/openvms/roadmap/openvms_roadmaps.htm-   http://www.openvms.compaq.com/openvmstimes/a   http://www.compaq.com/inform/h  < ------------------------------------------------------------' [VMS6 removed, replaced by Y2K section]s  < ------------------------------------------------------------3 VMS7.   What OpenVMS CD-ROM products are available?o  $ 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-ROMw?   QA-MT1AT-H8   OpenVMS Alpha V7.2-1 maintenance release CD-ROMa>   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 Alphay   QT-3CRAA-C8   OpenVMS VAXy  E OpenVMS VAX and OpenVMS Alpha source listings CD-ROM sets include theEI source listings of most of OpenVMS, and these CD-ROM sets are invaluable 3G for any folks working directly with OpenVMS internals, as well as folksl@ 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  h< ------------------------------------------------------------, 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, -G MDL, DEC C++, DCL, Message, and Document.  And this is certainly not a IG complete list. However, the rumor is NOT true that an attempt was made dC to write pieces of OpenVMS in every supported language so that the nG 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 commandnI procedures that are used as part of the OpenVMS build, and a source code iK control system capable of maintaining over a hundred thousand source files aH 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 dB 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.e  ! For further information, link to:i  #   http://www.montagar.com/hobbyist/   F On the hobbyist license registration form (as of August 2001), you areG offered the choice of the "OpenVMS VAX" license(s), the "OpenVMS Alpha"-C license(s), and the "Layered Products" licenses.  You will want theeF operating system license for your particular OpenVMS platform AND you * will want the "Layered Products" licenses.  E For information on licenses for educational customers, see the CompaqcA CSLG license program and the OpenVMS Educational license program:h     http://www.openvmsedu.com/  C To transfer a commercial OpenVMS license from one owner to another,dD or to purchase a commercial license, you can contact Compaq ComputerA Corporation at 1-800-DIGITAL (in North America), or your local oru regional sales office.  E Commercial developers can join the CSA program, and can (potentially) C receive discounts on various software product licenses and softwarecD 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?r  B For information on the current status and plans for support of the? European Monetary Union's Euro currency symbol in OpenVMS, see:   %   http://www.openvms.compaq.com/euro/i  < ------------------------------------------------------------? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?d   Why?  Business reasons...   B Because there is a belief that there would be no market to justifyA the effort and the expense involved in porting OpenVMS to systems A using the Intel IA32 architecture.  (Each maintainer of a productsA or package for OpenVMS would have to justify the port to "OpenVMS'D 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.w  C Because there are design features that required by OpenVMS that arenF 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.n  C Because Alpha is faster than Intel IA32 systems -- if OpenVMS is too? be ported, a port to a slower system is more difficult to sell.r  @ 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 OpenVMSiD arises from the stability of the underlying VAX and Alpha hardware, C and systems based on components such as ISA and random memory SIMMsn might not be as stable.h  " But yes, it would be nice to have.  <                                            [Stephen Hoffman]  < ------------------------------------------------------------? VMS12.  Are there any general-access OpenVMS systems available?v   Yes.  
   o Hobbes  ?       Hobbes is a MicroVAX 3100 Model 40 for which free access t>       and accounts are available to OpenVMS enthusiasts. This C       system has BASIC, Pascal, Fortran, and C compilers installed./D       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.e  E                                      [Scott Squires, Steven Shamlian]u     o OpenVMS Galaxy Test Drive   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/s     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.o  !   http://www.compaq.com/info/spd/p:   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:-  9   http://www.openvms.compaq.com/openvms/supportchart.htmlA  : For information on the Multia, related Alpha single-board : computers, or other officially unsupported systems, please see ALPHA8 and ALPHA13.   < The following is a rule-of-thumb for Alpha platform support.; The table contains the earliest OpenVMS Alpha release with n9 support for a particular series of Alpha microprocessors:r  $ Microprocessor | OpenVMS   | General%   Generation   | Version   | Commentss  G   21064  EV4   : V1.0      : few systems; most EV4 req later; upg availi5   21164  EV5   : V6.2      : subsequent upg availablei=   21164A EV56  : V6.2-1H3  : subsequent upg to V7.1 and laterpH   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 expectationn    < ------------------------------------------------------------* VMS14.  How can I submit OpenVMS Freeware?  ?   For the guidelines and submission info, please visit the URL:i  @     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 thes' features used on the original platform.h  A This section covers generic porting, and porting from OpenVMS VAX @ 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 eB OpenVMS Alpha, on management differences, on upgrading privileged   code, and application migration:  %   http://www.openvms.compaq.com:8000/s$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/u  : 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:e  9   http://www.openvms.compaq.com/ebusiness/Technology.html-  A Information on the Enterprise Toolkit, a Visual-based development?E environment for developing applications for OpenVMS using a Microsofty platform, is available at:  ;   http://www.openvms.compaq.com/commercial/et/et_index.htmlv  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:S     http://diicoe.disa.mil/coe/h  C A wide variety of programming development tools and middleware are SA available as commercial products (eg: DECset, IBM MQseries), and tC various tools are also available as shareware or Freeware.  Please 1/ see other sections of this FAQ, and please see:-  &   http://www.compaq.com/csa/directory/  l< ------------------------------------------------------------0 VMS16.  How do I join Compaq Solutions Alliance?  G The Compaq Solutions Alliance (CSA) is a (free) program that is open toiH 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.n  H The Compaq Solutions Alliance Technical Journal (CTJ) is "web-published" monthly, and available at:  3   http://csa.compaq.com/CompaqTechnicalJournal.htmll  < ------------------------------------------------------------H VMS17.  memory management, resource management, process scheduling, etc?  J   So you have been instructed to write a school research paper on OpenVMS,I   and you need technical content on the OpenVMS Virtual Memory System, on I   any memory segmentation, on OpenVMS Resource Management, on the OpenVMSp2   File System, on the OpenVMS user interface, etc.  E   Invariably, your professor/instructor/teacher will ask you a serieseG   of questions.  Most commonly, the questions will request descriptions I   of one or more of the following items, and at varying levels of detail:   %     o process scheduling algorithm(s)o        o Interprocess comunications  2     o Process or system synchronization constructs  <     o Memory management and/or virtual memory implementation        o RMS or XQP file structures       o Resource managementv       o History of Compaq OpenVMSe  E     o History of Compaq and/or of Digital Equipment Corporation (DEC)A    N   Any particular presentation or research paper, and particularly a scholasticL   presentation, can have many different potential target audiences, and veryJ   different presentation levels.  Further, the usual underlying reason forM   scholastic presentations and scholastic research projects really has littleuL   to do with the subject matter, it is a task specifically intended to teachO   the student(s) (eg: you) how to perform the research.  The instructor alreadysN   knows most of (all of?) the information that you have been asked to collect.  M   For low-level (more technical) details on OpenVMS, the book you want is the J   Internals and Data Structures Manual (IDSM), available in your school orK   computing center library, and the IDSM can also be purchased.  AdditionaleJ   low-level details of the Alpha microprocessor are available in the AlphaM   Architecture Reference Manual documentation that is available for download.lK   (A pointer to the Alpha technical documentation is elsewhere in the FAQ.)e  J   For higher-level (less technical) details, the OpenVMS documentation setN   is available on-line.   The Programming Concepts and the File Systems manualJ   are probably the best manuals to start with, depending on the particular(   level of detail the research requires.  K   And please understand the hesitation of various folks to provide you withiJ   a completely-written research report on your topic.  Why?  We might haveH   to work with you after you graduate -- you need to know how to performA   at least basic research on your own, regardless of the topic.  l  < ------------------------------------------------------------: DOC1.   Where can I find online copies of OpenVMS manuals?  D The Compaq OpenVMS and layered product documentation is copyrighted 	 material.   C HTML format on-line product documentation sets for specific Compaq -, OpenVMS products are presently available at:  %   http://www.openvms.compaq.com:8000/r$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/e  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 rK with the documentation distribution.  BNU can display HTML, Bookreader, ande! documentation in other formats.  i  E MGBOOK, a viewer for Bookreader-format documentation is available forrI character-cell terminals (eg. VTxxx) via the WKU VMS Freeware file servero" -- see question SOFT1 for details. 					[Steve Lionel]  					[Stephen Hoffman]    < ------------------------------------------------------------- DOC2.   What online information is available?-  M On your OpenVMS system, the HELP command can provide a wealth of information,eJ 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 furthern	 pointers.p  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 -
 much more.  L Software Product Descriptions (SPDs) for most every OpenVMS-related product  Compaq sells is available via:  !   http://www.compaq.com/info/spd/S  L System performance data (see ALPHA5), product infosheets, release notes and  much more are also available.r   In addition,     http://search.compaq.com/b  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. .D Various contract-access and non-contract access ECO (patch) kits are available, see section MGMT25.  E The Compaq Systems and Options Catalog (SOC) archive is available at:a  J   http://www.compaq.com/products/quickspecs/soc_archives/SOC_Archives.html  G The Systems and Options Catalog has been replaced by Compaq QuickSpecs:e  @   http://www.compaq.com/products/quickspecs/productbulletin.html  I The Compaq DSNlink electronic product support network (a good source for  H 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 andDB country-specific mechanisms, please see the above URL for details.  C Information on Compaq hardware, software, products and services is n, available through various telephone numbers:  G     1-800-AT-COMPAQ     : voice : Compaq (including DIGITAL and Tandem)n7                                   products and services 9     1-800-DIGITAL	: voice : DIGITAL products and servicesM0     1-800-DEC-2717	: voice : The DECchip Hotline9     1-508-568-6868	: voice : (alternate number for above)->     1-800-STORWORK      : voice : The Compaq StorageWorks team  G David Mathog offers two HTML documents which contain useful informationa about OpenVMS.  1   http://seqaxp.bio.caltech.edu/www/soft_doc.htmli  9 The VAXarchive (hardware and software information) is at: &   http://vax.sevensages.org/index.html  I Useful OpenVMS information and an extensive set of links is available at:w   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 emails subscriptions available, see:,  !     http://www.compaq.com/inFORM/c/     http://www.openvms.compaq.com/openvmstimes/r  ) Also see the DFWCUG Longwords newsletter:e       http://www.dfwcug.org/  @ Back issues of the old Digital Technical Journals (DTJs) are at:  7     http://www.research.compaq.com/wrl/DECarchives/DTJ/      ----  + An OpenVMS Programming FAQ is available at:n  D     http://www.pdv-systeme.de/users/martinv/VMS_Programming_FAQ.html  9                                        [Martin Vorlnder]    ----  & A Customer VAX to Alpha upgrade diary::     http://www3.sympatico.ca/n.rieck/docs/alpha_diary.html     ----  B Scanned versions of old DIGITAL hardware manuals are available at:  ,   http://www.montagar.com/~patj/dec/hcps.htm    < ------------------------------------------------------------2 DOC3.   What books and publications are available?  C A bibliography of current and recent OpenVMS books is available at:e  ,   http://www.levitte.org/~ava/vms_book.htmlx  C The Butterworth-Heinemann Digital Press imprint offers a number of a* OpenVMS books.  A website is available at:     http://www.bh.com/  ; Information on specific OpenVMS books is also available at:m  2   http://www.openvms.compaq.com/openvms/books.html   Also see DOC10.c    < ------------------------------------------------------------E DOC4.   How do I extract the contents of a HELP topic to a text file?c  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 followingm command:  7      $ HELP/OUT=filename.txt help-topic [help-subtopic]e  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 help E library), add /LIBRARY=libname after the HELP verb.  To see the namesS8 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 provideSK informal method to communicate directly with members of OpenVMS Marketing.)s  < ------------------------------------------------------------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)'@     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) D     http://www.progis.de/openvms.htm  (Sponsored by proGIS Software)A     http://www.jcameron.com/vms/      (Sponsored by Jeff Cameron)h  A The following web site is sponsored by "The Beave", and provides tC information that is directly relevent to system managers, security kC managers, and others interested in ensuring the continued security o of OpenVMS systems:s  3     http://www.vistech.net/users/beave/hack-vms-faq-  E Suggestions (indirectly) provided by the above include disabling the t> port 11 and 15 stats provided by IP packages such as Multinet.  < ------------------------------------------------------------ DOC7.   removed.  See MGMT25.E  < ------------------------------------------------------------B DOC8.   Where can I find info about undocumented OpenVMS features?  E After all this discussion about undocumented VMS features I started a 4 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]a   Also see the following:c  -     http://www.levitte.org/~ava/vms_tip.htmlxi=                                                 [Arne Vajhj]   C Various examples of undocumented features are also available on the- OpenVMS Freeware:-  +     http://www.openvms.compaq.com/freeware/h  < ------------------------------------------------------------@ DOC9.   Where is documentation on the DECnet Phase IV protocols?  E Documentation and Specifications for DECnet Phase IV can be found at:   0     http://www.openvms.compaq.com/wizard/decnet/  < ------------------------------------------------------------G DOC10.  Where can I learn about how the VMS executive works internally?   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  F 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 DD 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.OM The first such volume, published in early 1997, was "OpenVMS Alpha Internals mG and Data Structures: Scheduling and Process Control," which covers the tM Version 7.0 implementation of true multithreading and the changed scheduling a model it implies.A  F The internals books are available through Digital Press, an imprint ofC Butterworth-Heinemann. You can order by phone (from US and Canada,  F 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 48 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.5yA 1 55558 059 9  VAX/VMS Internals and Data Structures: Version 5.2    					[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-specificnH new user's documentation, covering various site-specific things that areG difficult or impossible for the general OpenVMS documentation to cover.-  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/o$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/a  C Some of the OpenVMS books available from the Butterworth-Heinemann i2 Digital Press imprint (http://www.bh.com) include:  ,        Introduction to OpenVMS, 5th Edition,        Lesley Ogilvie Rice        ISBN 1 55558 194 3   /        The OpenVMS User's Guide, Second Editiond        Patrick Holmayr        ISBN 1 55558 203 6c          Introduction to OpenVMS        David W Bynon        ISBN 1 878956 61 2a  &        OpenVMS System Management Guide        Richard Berry        ISBN 1 55558 143 9s  )        Using DECwindows Motif for OpenVMSp        Margie Sherlock        ISBN 1 55558 114 5n  3        Writing Real Programs in DCL, Second Editiont"        Hoffman and Anagnostopoulos        ISBN 1 55558 191 9l  1   For various features OpenVMS books, please see: 4     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:a  -     http://www.levitte.org/~ava/vms_faq.htmlxs.     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  D   Members of the DECUS DFWLUG maintain a website with many materialsE   available, including an Overview of OpenVMS, an Introduction to DCLh>   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 toeA   OpenVMS Cluster Management.  These training materials have beenwB   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:t  ,     http://www.compaq.com/training/home.html0     http://www.openvms.compaq.com/wbt/index.html  ?   An OpenVMS certification (testing) program is also available.c  (   The following URL has an OpenVMS Quiz:      http://www.jcameron.com/vms/  E   CCSS Interactive Learning has OpenVMS training materials available:e     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 mayc:   not operate correctly in all cases, and (for reasons not;   worthy of repeating here) redirects may not be available.o  0   You can manually access the documentation via:3     http://www.openvms.compaq.com:88/netscape/help/n  < ------------------------------------------------------------1 DOC13.  What OpenVMS mailing lists are available?      See:/     http://www.levitte.org/~ava/vms_forum.htmlx      ,   OpenVMS Freeware archive announcement list     FSupdate@goatley.com#   Two-way echo of vmsnet.internals:       VMSnet-Internals@goatley.com&   OpenVMS Alpha Internals discussions:     Alpha-IDS@goatley.com (*)m   BLISS discussionsu     BLISSters@goatley.com (*) 8   Process Software MultiNet mailing list (news gateway):     Info-MultiNet@process.comn7   Process Software TCPware mailing list (news gateway):n     Info-TCPware@process.com4   Process Software PMDF mailing list (news gateway):J     Info-PMDF@process.com                 PMDF mailing list (news gateway)<   Discussion list for SRI's CHARON-VAX VAX emulator package:      CHARON-VAX-Users@process.com)   Info-Zip's Zip & UnZip discussion list:i     Info-Zip@wku.edu  K   To subscribe to any of the lists, the command SUBSCRIBE should be sent int=   the body of a mail message to the -request address like so:e       list-request@hostl     For example:  !     BLISSters-request@goatley.comy  M   (*) The Alpha-IDS and BLISSters lists have been dormant for some time, but n   they do still exist.    6                                       [Hunter Goatley]  ;   RADIUS-VMS, a RADIUS server for OpenVMS discussion forum:M         radius-vms@dls.netB         Send subscription requests to (MadGoat MX-List processor):*                 radius-vms-request@dls.net  >   Forum for Internet Service Providers (ISPs) running OpenVMS:         vms-isps@dls.netB         Send subscription requests to (MadGoat MX-List processor):(                 vms-isps-request@dls.net  9                                       [Ruslan R. Laishev]d  F   An Info-WASD mailing list for users of Mark Daniel's WASD web serverH   for OpenVMS VAX and Alpha exists.  Information about this list server >   and details on how to subscribe to the list can be found at:       http://wasd.vsm.com.au/t  3                                       [Jeremy Begg]   < ------------------------------------------------------------> DOC14.   What is this Ask The Wizard website I've heard about?  @ The Compaq OpenVMS Ask The Wizard (ATW) website is available at:)     http://www.openvms.compaq.com/wizard/o  < A zip archive of questions and answers can be downloaded at:3     http://www.openvms.compaq.com/wizard/wizard.zipf    < ------------------------------------------------------------8 TIME1.   A brief history of OpenVMS Timekeeping, please?  =   Why does OpenVMS regards November 17, 1858 as the beginning    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 r@   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, rE   the 14 bits left over by keeping the Julian date in its own 36-bit oD   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 m5   fraction of a day in the right 18 bits of one word.e  A   Eighteen bits allows the truncated Julian day (the SAO day) to eA   grow as large as 262143, which from November 17, 1858, allowed cB   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.u  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  E   honor of his father, Julius Caesar Scaliger (note that this Julian qB   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  D   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 o"   from 4713 B.C. through 3267 A.D.  E   The starting year was before any historical event known to him.  InCE   fact, the Jewish calendar marks the start of the world as 3761 B.C.cG   Today his numbering scheme is still used by astronomers to avoid the aF   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/d     http://www.nist.gov/)     http://www.boulder.nist.gov/timefreq/w/     http://www.tondering.dk/claus/calendar.htmleG     http://es.rice.edu/ES/humsoc/Galileo/Things/gregorian_calendar.htmla  E   are all good time-related resources, some general and some specificd
   to OpenVMS.   % 					[Stephen Hoffman, Dale Dellutri]o    < ------------------------------------------------------------3 TIME2.   How does OpenVMS VAX maintain system time?   ?   VAX systems maintain an interval clock, and a hardware clock.o  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").O  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 andnJ   retrieved from the system image, to initialize the interval clock value #   that is stored in EXE$GQ_SYSTIME.l  M   Once the interval clock is loaded, the system does not typically reference  H   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 eD   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  8   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 tJ   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?O  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 aE   can also be caused by normal (thermal) clock variations and even bya$   the expected level of clock drift.  C   When clock interrupts are blocked as a result of the activity of -D   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 am3   common cause of system time loss, in other words.-  G   Clock drift can also be (deliberately) caused by the activity of the     DTSS or NTP packages.f  $   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 S  I   to configure the OpenVMS Timezone Differential Factor (TDF) on OpenVMS uH   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 n=   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 useV=     SYS$MANAGER:UTC$TIMEZONE_SETUP.COM  ! do not directly usec  G   TCP/IP Services V5.0 and later use the OpenVMS TDF, UTC, and timezone/F   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,r6   in addition to the OpenVMS configuration of the TDF.  G   DECnet-Plus in V7.3 and later uses the OpenVMS TDF, UTC, and timezoneSF   support, and displays its timezone prompts using UTC$TIME_SETUP.COM.C   Earlier versions use a TDF TDF mechanism, timezone database, and sD   automatic switch-over that is internal to the DECnet-Plus package.A   Also on earlier versions, the TDF must be configured within thesG   DECnet-Plus DECdtss package, in addition to the OpenVMS configurationy
   of the TDF.u  G   Application code using Compaq C (formerly DEC C) will use the OpenVMSlH   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 declarationt   _VMS_V6_SOURCE is declared.c     DCE DTSS TDF details TDB.   E   In OpenVMS Alpha V6.1, V6.2, and V6.2-1Hx, the TDF value is written6D   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 TDFn2   value reset manually on reboots prior to V7.0.    I   During OpenVMS Bootstrap, the SYSINIT module reads SYS$TIMEZONE.DAT to cI   acquire the TDF for use in the system global cell EXE$GQ_TDF.  This is -G   done to ensure that the system boots with a valid TDF (a value which ?J   may be zero). The UTC system services get the TDF from this cell. These K   services, as well as the Compaq C RTL, must have a valid TDF.  (Prior to -M   OpenVMS V7.3, if either DECnet-Plus or DECnet/VAX Extensions is configured MK   and run, the image DTSS$SET_TIMEZONE.EXE is invoked and can override the nL   TDF and timezone rule settings from SYSINIT or from UTC$TIME_SETUP.COM -- I   this image runs even if DTSS is disabled.  If the settings do not matchyJ   (due to inconsistencies in timezone specification in UTC$TIME_SETUP.COM B   and NET$CONFIGURE.COM), DTSS will reset the values to match its    definitions.)f  D   Prior to OpenVMS V7.3, daylight savings time switchover is handledE   automatically only when DCE DTSS or DECnet-Plus DTSS is in use.  InrA   V7.3, OpenVMS can be configured to automatically switch over tolD   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 timelE   is correctly accomplished via the SYS$EXAMPLES:DAYLIGHT_SAVINGS.COMl   command procedure procedure.  G   If you switch the TDF or daylight savings time setting, you will alsooH   want to restart or reconfigure any time-sensitive applications (those I   not using the time differential factor (TDF) change event available in  G   V7.3 and later).  Examples of these applications include the need to .I   restart the NFS client and (yes) NTP. (NTP will want to try to "drift" eL   the time (see TIME6), and will find the daylight savings time switch-over L   to be far too large to "drift". 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.5     Prior to V7.3, the command:D        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 names?!   based on the SYS$TIMEZONE_RULE.a  E   The following are other TDF-related logical names used/available onaG   OpenVMS systems, with typical Daylight Savings and Standard Settings n(   for the US Eastern Time (ET) timezone.       $daylight_time: /     $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE EDTo8     $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0400 EDT"K     $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P true  ! Not 'EDT'O<     $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant       $standard_time:p/     $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE ESTe8     $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0500 EST"K     $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P false ! Not 'EST'n<     $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant  9     $ DEFINE/SYSTEM/EXECUTIVE UCX$NFS_TIME_DIFFERENTIAL -iF         'f$integer(f$element(0," ",f$logical("notes$timezone"))/-100)'  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 6C   Reference Manual -- though the title would imply otherwise, this  F   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?o  F   This is an OpenVMS Alpha system prior to V7.0 and the startup is not   invoking the procedure:   !    SYS$MANAGER:UTC$TIME_SETUP.COMa  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 i   OpenVMS V7.3.  (DCE TDF TBD.)e  K   If you should find either of the following two timezone-related database  )   files located in SYS$SPECIFIC:[SYSEXE]:h  +     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DATo/     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DATe  H   These two files are in an erroneous location and must be recreated in    the correct directory:       SYS$COMMON:[SYSEXE].     If the DCL command:n  *     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:a  $     SYS$STARTUP:DTSS$UTC_STARTUP.COM  9   is present on your system, then you may need to invoke:.  -     SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM(  @   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 yourc>   system, then you may need to execute the following commands:  +     DELETE SYS$STARTUP:DTSS$UTC_STARTUP.COM +     DEASSIGN/SYSTEM/EXEC SYS$TIMEZONE_RULE.-  < ------------------------------------------------------------= TIME6.   How can I keep the OpenVMS system time synchronized?t  F   To help keep more accurate system time or to keep your system clocksG   synchronized, TCP/IP Services NTP, DECnet-Plus DECdtss, DCE DTSS, andaF   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 other-   authoritative site.-  C   There exists code around that processes the digital (ie: binary) lD   format time that is available via a modem call into the NIST clockC   (the Automated Computer Telephone Service (ACTS)), and code that y@   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 r@   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 XG   hours, minutes, seconds and days since the start of the current year.pG   IRIG can also contain the time of day as the number of seconds since  I   midnight.  Compaq Custom Systems and third-party vendors offer various l:   IRIG-based reader/generator modules for OpenVMS systems.  G   Differing time servers (DECnet-Plus DTSS, DCE DTSS, NTP, etc) do not hF   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  I   another protocol, but one and only one time server package should have MJ   direct control over the management of and drifting of the local OpenVMS    system time.)e     Useful URLs:8     http://www.boulder.nist.gov/timefreq/service/nts.htm9     http://www.boulder.nist.gov/timefreq/service/acts.htm )     http://www.boulder.nist.gov/timefreq/      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 NTPrE   clients via the NTP protocol.  Most systems are NTP clients, but...   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), aG   the lower the strata (and the larger the number assigned the statum).e  H   NTP explicity configured at stratum one provides time to NTP operatingG   at lower strata, and the provided time is acquired based on the localeB   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. J   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 clocknI   is the LCL (local system clock).  If your system has an excellent clockaF   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 asgH   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:e       server 127.127.1.0 prefer1     fudge 127.127.1.0 stratum 0   G   For local-master functionality, the commands are very similiar.  Use:t       server 127.127.1.0     fudge 127.127.1.0 stratum 8,  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 ongI   an isolated network.  The server will become active only when all other F   normal synchronization sources are unavailable.  The use of "prefer"J   causes NTP to always use the specified clock as the time synchronization	   source.n  I   With the TCP/IP Services versions prior to V5.0, the NTP management is  G   rather more primitive.  To configure the local OpenVMS system from an K   NTP client to an NTP server (on TCP/IP Services versions prior to V5.0), iH   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:   *     SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE  8   For current TCP/IP Services documentation, please see:  '     http://www.openvms.compaq.com:8000/ &     http://www.openvms.compaq.com/doc/    < ------------------------------------------------------------1 TIME8.   How can I drift the OpenVMS system time?v  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 nK   is used by most (all?) time servers operating on OpenVMS, typically usingt8   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?-  K   Because the VAX Time Of Year (TOY) has a resolution of 497 days, the VAX aL   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 rD   the standalone BACKUP image, an ECO that replaces SYS.EXE, etc).    G   The SET TIME command is automatically issued during various standard  K   OpenVMS procedures such as SHUTDOWN, and it can also obviously be issued eH   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.n  H   This VAX TOY limit is the reason why OpenVMS VAX installation kits andI   standalone BACKUP explicitly prompt for the time during bootstrap, and 2G   why the time value can "get weird" if the system crashes outside the eI   497 day window (if no SET TIME was issued to update the saved values), PK   and why the time value can "get weird" if a different SYS$SYSTEM:SYS.EXE  :   is used (alternate system disk, standalone BACKUP, etc).  < ------------------------------------------------------------A TIME10.   Why can't I do a SET TIME command?  Help managing DTSS?t  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 timer0 -SYSTEM-F-IVSSRQ, invalid system service request  # %SET-E-NOTSET, error modifying timeoK -SYSTEM-E-TIMENOTSET, time service enabled; enter a time service command to. update the times    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 orsL 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); O therefore, the usage of the SET TIME command (and the underlying $SETTIM system  service) is disabled.s  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 mored informative) message is given.  I You shouldn't have to change the time manually - you should be doing thistM through the time server - but if you insist...  you'll have to shutdown DTSS:e  	 $ MCR NCLv NCL> DISABLE DTSSS 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$STARTUPg  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.i?                                         [bol@adv.magwien.gv.at]o  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) see-, 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:00Iinfi         Number Detected=0,         Number Required=1/7         eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0Fh7         entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1Br7         streamUid  D6513A46-6135-11D3-8003-AA000400BD1B   K You can either configure the appropriate number of time servers, or you canuG disable DTSS, or you can ignore it and (if OPCOM is set to write to thelJ log via via the logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE) clean out OPERATOR.LOG regularly.t  : You can also simply disable the display of these messages:  M $ mcr ncl block event dispatcher outbound stream local_stream global filter -h,     ((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.  < ------------------------------------------------------------5 TIME11.   Details of the OpenVMS system time-keeping?   &   VAX hardware time-keeping details...     TOY clock    ---------pG   This is battery backed up hardware timing circuitry used to keep the .D   correct time of year during rebooting, power failures, and system C   shutdown.  This clock only keeps track of months, days, and time.BG   The time is kept relative to January 1st, at 00:00:00.00 of the year D   the clock was initiailized.c     EXE$GQ_SYSTIME   --------------K   This is the OpenVMS VAX system time cell.  This cell contains the number )K   of 100ns intervals since a known reference.  This cell is incremented by w2   100000 every 10ms by an hardware interval timer.     EXE$GQ_TODCBASE7   ---------------tI   This cell contains the time and date the system time was last adjusted EM   by EXE$SETTIME.  It uses the same format as EXE$GQ_SYSTIME.  On adjustment nM   of the system time a copy of EXE$GQ_SYSTIME is stored in this cell in both iM   memory and on disk.  This cell is used to get the year for the system time.n  
   EXE$GL_TODRn
   -----------.K   This cell contains the time and date the system time was last adjusted byeO   EXE$SETTIME. It uses the same format as the time of year clock. On adjustmentlL   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.g  L   The system parameters SETTIME and TIMEPROMPTWAIT determine how the system    time will be set.i     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.   7         IF the TOY clock is within a day of EXE$GL_TODR 6         THEN the system time is calculated as follows:  O         EXE$GQ_SYSTIME = EXE$GQ_TODCBASE + ((TOY_CLOCK - EXE$GL_TODR) * 100000)e  ,   IF SETTIME = 1 or the TOY clock is invalidL   THEN the value of TIMEPROMPTWAIT determines how to reset the time of year.           IF TIMEPROMPTWAIT > 0PM         THEN the user is prompted for the time and date, for a length of time 0         equal to TIMEPROMPTWAIT microfortnights.           IF TIMEPROMPTWAIT = 0 A         THEN the time of year is the value of EXE$GL_TODR + 10ms.(  '         IF TIMEPROMPTWAIT < 0to proceedF         until they do so.   C         THEN the user is prompted for the time and date and unable e  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 I@   -- 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, ZI   and cannot be changed.  Unless the current year happens to be the same EK   year as that on the CD-ROM, most likely the year will be off.  (Further, EH   with the calculation of Leap Year also being dependent on the current ?   year, there is a possibility that the date could be off too.)E      (   Alpha hardware time-keeping details...  &   Battery-Backed Watch (BB_WATCH) Chip&   ------------------------------------G   This is battery backed up hardware timing circuitry used to keep the SD   correct time of year during rebooting, power failures, and system G   shutdown.  This clock keeps track of date and time in 24 hour binary a	   format.t     EXE$GQ_SYSTIME   --------------M   This is the OpenVMS Alpha system time cell.  This cell contains the number  H   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.h     EXE$GQ_SAVED_HWCLOCK   --------------------M   This cell is used by OpenVMS Alpha to keep track of the last time and date rF   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.  S  G   - The system parameters SETTIME and TIMEPROMPTWAIT determine how the       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 = 0IA           THEN the system time is calculated from the contents of #           EXE$GQ_SAVED_HWCLOCK + 1.R           - IF TIMEPROMPTWAIT < 0aG           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.)    >   IA-64 (Itanium) hardware time-keeping details to be added...    < ------------------------------------------------------------D TIME12.  UTC vs GMT vs vs UT1/UT1/UT2 TDF?  What are these acronyms?  F   The results of an international compromise -- though some would say F   an international attempt to increase confusion -- UTC is refered to H   as "Coordinated Universal Time" (though not as CUT) in English and as <   "Temps Universel Coordinn" (though not as TUC) in French.  F   Universal Time UT0 is solar time, UT1 is solar time corrected for a E   wobble in the Earth's orbit, and UT2 is UT1 corrected for seasonal eC   rotational variations in rotation due to the Earth's solar orbit.s  E   GMT -- Greenwich Mean Time -- is UT1.  GMT is the time at the (old)oE   Royal Greenwich Observatory (in Greenwich), not to be confused withsD   the Royal Greenwich Observatory located at Herstmonceux Castle in    Sussex, England.  H   UTC is based on an average across multiple atomic clocks, and is kept K   within 0.9 seconds of GMT, through the insertion (or removal) of seconds.cF   In other words, UTC matches GMT plus or minus up to 0.9 seconds, but   UTC is not GMT.y  G   TDF is the Timezone Differential Factor, the interval of time betweennE   the local time and UTC.  Areas that celebrate daylight savings timetH   (DST) will see periodic changes to the TDF value, when the switch-overJ   between daylight savings time and standard time occurs.  The switch-overF   itself is entirely left to local governmental folks, and can and hasI   varied by political entity and politics, and the switch-over has variedg-   over the years even at the same location.  d  G   If your local OpenVMS system time is off by one hour (or whatever thehG   local DST change) for some or all applications, you probably need to m   reset your local TDF.v  D   Further discussions of history and politics, the Royal Observers' G   outbuildings, and the compromise that left the English with the Time eF   Standard (the Prime Meridian) and the French with the standards for F   Distance and Weight (the Metric System) are left to other sources.     Some of these sources:        ftp://elsie.nci.nih.gov/pub/1     http://physics.nist.gov/GenInt/Time/time.html      http://nist.time.gov/r  < ------------------------------------------------------------1 TIME13.  Customizing your TDF (Timezone) Setting?e  I   Individual, local, and regional differences on the use (or the lack of  7   use) of Daylight Savings Time (DST) are quite common.   G   If you need to add (or remove) daylight savings time for your area or-G   otherwise alter the rules for your local area, you will probably end c7   up creating a variation to an existing timezone rule.   F   The necessary zone line to add for WhereEverLand will probably look    something like this:  ? # Zone  NAME            GMTOFF  RULES/SAVE      FORMAT  [UNTIL] 9 Zone    WhereEver       2:00    -               WhereEveru  6   The OpenVMS source file for the timezone rules here:  ,     SYS$COMMON:[SYS$ZONEINFO.SYSTEM.SOURCES]  E   You'll then want to ZIC this to create your own timezone definiton.n  F   ZIC is documented in the OpenVMS Documentation Set, in the Compaq C G   Run-Time Library Reference Manual.  (Despite the name of the manual, sE   it is part of the OpenVMS documentation set and not the C manuals.)e  H   Once you have created the new rule, use SYS$MANAGER:UTC$TIME_SETUP.COMC   to select the new timezone -- with V7.3 and later, this tool will E   notice the new timezone and will offer it, on earlier releases, youaG   may/will have to hack the tool somewhat.  (Don't even think of tryingaJ   to define the TZ or other time-related logical names directly yourself.)  J   For various timezone rules, see the tar.gz files (these are gzipped tar    archives) available at:         ftp://elsie.nci.nih.gov/pub/   [End of Part 1/5]m  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 02 Oct 2001 21:31:02 GMTi2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/5t1 Message-ID: <qmqu7.958$YP.25685@news.cpqcorp.net>o   Archive-name: dec-faq/vms/part2  Posting-Frequency: quarterly Last-modified: 2 Oct 2001  Version: VMS-FAQ-2.TXT(7)t    9 This is the OpenVMS Frequently Asked Questions Part 2/5. o@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------# MGMT1.  What is an installed image?e  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 of K enhanced properties.  For example, when you issue the SET PASSWORD command,lI the image SYS$SYSTEM:SETP0.EXE is run.  That image needs to have elevatedC# privileges to perform its function.e  J The other important attribute is /SHARED.  This means that shareable partsG of the image (typically read-only code and data) are loaded into memory-H 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 Programmingi% Concepts Manual for further details.)   M It's important to note that there is no such thing as "installing a shareable H 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 shareableAH image with the /PROTECT qualifier.  See the OpenVMS Programming ConceptsG Manual for more information on user-written system services.  Note alsoEK that in many cases the need to grant privileges to an image can be replaced G with the use of the "Protected Subsystems" feature that grants a rights E identifier to an image.  See the OpenVMS Guide to System Security forX$ 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 systemeJ or the file system against hostile action by programs.  On these operatingK systems, any running program can subvert the operating system and take overcK the hardware, at which point it can do anything it wishes, including hidingy9 copies of itself in other programs or in the file system.t  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 sF 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 thattJ 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 configurations-G tend to prevent the uncontrolled execution of untrusted code as part ofa email messages or web access.e  K It is possible for OpenVMS, etc., to be infected by viruses, but to do so, nI the program containing the virus must be run from a user account that hasgJ amplified privileges.  As long as the system administrator is careful thatK only trusted applications are run from such accounts (and this is generallye+ the case), there is no danger from viruses.: 					[Paul Winalski] 					[Stephen Hoffman]  G To protect against viruses and other attempts at system interference orsN misuse, follow the recommendations in the "OpenVMS Guide to System Security". J 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.   H Rocksoft offers the Veracity data integrity tool (for info, send mail to demo@rocksoft.com).i  % [Contributions to this list welcomed]d  < ------------------------------------------------------------1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?n  5 ISO-9660 support was added in the following releases:d       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 installationS? 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 andM  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]o  > In most circumstances, you will not need nor will you want to = include an explicit /MEDIA_FORMAT specification.  For furtherN> information, please refer to the OpenVMS MOUNT Utility Manual.= Particularly note the information on the MOUNT /MEDIA_FORMAT u and /UNDEFINED_FAT qualifiers.  9 The MOUNT /UNDEFINED_FAT qualifier is of interest because2= ISO-9660 media can be mastered on a wide variety of operating1@ 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 fore6 files accessed from volumes using the ISO-9660 format.  + An example which works for most CD-ROMs is:r  G     $ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=STREAM:2048 DUA0: FREEWARE   @ This particular MOUNT command forces access to the CD-ROM media = using the ISO-9660 volume structure, and the use of the MOUNT > /UNDEFINED_FAT qualifier causes any file whose file attributes? are "undefined" to be returned with "stream" attributes with a s maximum record length 2048.i  @ On OpenVMS, the ISO-9660 format is (internally) considered to be= the ODS-3 file structure, while the High Sierra extensions tooA the standard are considered to be the ODS-4 file structure.  The s= Rock Ridge extensions are not currently available on OpenVMS.-   					[Jim Dunham]- 					[Stephen Hoffman]  = For details on ODS-1 and ODS-2 file specifications, see Kirby ? McCoy's VMS File System Internals Manual (published by Digital d. Press, but potentially out of print), and see:  .   http://pdp-11.trailing-edge.com/www/ods1.txt9   http://www.openvms.compaq.com/freeware/freeware50/ods2/a    < ------------------------------------------------------------4 MGMT4.  How do I extract the contents of a PCSI kit?  ? A growing number of OpenVMS products are being provided in PCSIhE (POLYCENTER Software Installation) kits which are installed using the1F 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=REFERENCEe  ? A PCSI kit file has a file specification of the following form:i  '     DEC-VAXVMS-FORTRAN-V0603-141-1.PCSIs  G In this example, "FORTRAN" is the "prodname".  PCSI will expand the kitcD files into the directory you specify and subdirectories beneath suchI as [SYSEXE], [SYSLIB], etc., reflecting the eventual destination of filesvH 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 the0H file type PCSI$DESCRIPTION that specifies where various files should go.G For more details, see the POLYCENTER Software Installation Developer's  E Guide for OpenVMS, which can be found in the OpenVMS documentation onk- the Consolidated Online Documentation CD-ROM.t  < ------------------------------------------------------------; 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 haveEF access to any privileged passwords, such as the password to the SYSTEMG username, you  will need physical access to the system console, and youfB will need to perform a conversational reboot.  Here are the steps:  ?   1.  Halt the system.  Exactly how this is done depends on the E       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 theaJ       SYSBOOT> utility.  (SYSBOOT allows conversational changes to system I       parameters.)  The syntax for the conversational bootstrap varies byEI       system model -- this typically involves specifying a flag of 1, forc       example:           VAX:
           B/1            B/R5:1           @GENBOOu           Alpha:           b -flags 0,1  I       If your system has a non-zero system root (such as root SYSE, shown,J       here), you will have to use a console command such as the following:           VAX:           B/E0000001           B/R5:E0000001o7           @<console media procedure name varies widely>o           Alpha:           b -flags e,1     E       If your system has a hardware password (various systems supportaG       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 havefF       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 system H       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:l           SET/STARTUP OPA0:o         SET WINDOW_SYSTEM 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:STARTUP   I       The result of these two commands will be the normal system startup,eD       but you will be left logged in on the console, running under aE       privileged username.  Without the use of the SPAWN command, youc5       would be logged out when the startup completes.W  E       If necessary, you can skip the invocation of the system startupoE       temporarily, and perform tasks such as egistering license PAKs  <       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 residest          RUN SYS$SYSTEM:AUTHORIZE+         MODIFY SYSTEM /PASSWORD=newpasswordr         EXIT  F       These steps will change the SYSTEM password to the specified new!       newpassword password value.e  I    Reboot the system normally -- the SYSTEM password should now be set tol%    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.-  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.o  K    You can also use the conversational bootstrap technique shown above (thesM    steps through Step 3) to alter various system parameters.  At the SYSBOOT> /    prompt, you can enter new parameters values:c        SHOW MAXPROCESSCNTs
      SET . 64r
      CONTINUEt  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?w  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 r@ 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_queuei  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 d8 in the Release Notes and the DCPS$STARTUP.TEMPLATE file.  I For general and additional (non-Postscript) IP printing information, see:i4   http://www.openvms.compaq.com/wizard/ topic (1020)   http://www.wotsit.org/ 					[Steve Reece]5                                         [Arne Vajhj]l  < ------------------------------------------------------------ MGMT7 moved to TIME10.  < ------------------------------------------------------------) MGMT8 removed. superceded by TIME section   < ------------------------------------------------------------; MGMT9.  How do I change the node name of an OpenVMS System?s  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 theo:   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.   @     Update the SCSNODE in MODPARAMS.DAT, and then run AUTOGEN as7       far as the SETPARAMS phase.  (Do not reboot yet.)N@     Modify the DECnet node name.  (NETCONFIG is the DECnet Phase:       IV tool, and NET$CONFIGURE is the DECnet-Plus tool.)E     Modify the IP node name.  (The TCP/IP Services tool is UCX$CONFIGME       prior to V5.0, and is TCPIP$CONFIG in V5.0 and later releases.) @     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 anyeD       local node-conditional operations present in the site-specificA       system startup, etc.  (SEARCH for the node name, specifyinga       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 namer       to the new node name.c@     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.a  E   If the system is configured in a VMScluster and you change *either*VE   the SCSNODE or the SCSSYSTEMID -- but *not* both values -- then yourG   will have to reboot the entire VMScluster.  (The VMScluster remembers.>   the mapping between these two values, and will assume that aE   configuration problem has occured if a mismatched pair appears, anddH   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  $   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 allo?   over the place, in layered products, and in local software...    					[Stephen Hoffman]  < ------------------------------------------------------------E MGMT10. What is the correct value for EXPECTED_VOTES in a VMScluster?i  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 sufficientiJ 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 preventmJ 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,cI and EXPECTED_VOTES.  The former is how many votes the node contributes torJ 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, believingtC this will allow when only a subset of voting nodes are present in atJ VMScluster.  It does not.  Further, an erroneous setting in EXPECTED_VOTESI is automatically corrected once VMScluster connections to other nodes areeJ established, meaning user data is at risk of severe corruption only during the initial system bootstrap.-  G One can operate a VMScluster with one, two, or many voting nodes.  WithMH any but the two-node configuration, keeping a subset of the nodes activeA when some nodes fail can be easily configured.  With the two-nodetH 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) thatSH 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.  J If you choose to use a quoum disk, a QUORUM.DAT file will be automaticallyH created when OpenVMS first boots and when a quorum disk is specified -- I well, the QUORUM.DAT file will be created when OpenVMS is booted without h, also needing the votes from the quorum disk.  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_VOTES  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 assignedaH 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 diski mount verification hangs.c  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 quorum-G mechanism to make your life more difficult -- quorum was implemented to ' keep your data from getting scrambled. d   						[Stephen Hoffman]d  < ------------------------------------------------------------< 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 existinghI definition of the PHYSICALPAGES (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMSvH 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:   /   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACKe  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 beiH useful in a few specific circumstances, such as testing the behaviour ofG an application in a system environment with a particular (lower) amountn of system memory available.n  I PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on OpenVMS Alpha) or rK (better and simpler) the entry can be removed from the MODPARAMS.DAT file,  5 to indicate that all available memory should be used.y   						[Stephen Hoffman]d  < ------------------------------------------------------------9 MGMT12. How do I write a BACKUP saveset to a remote tape?i  G How to do this correctly was described at DECUS a long time ago. On ther. node with the tape drive, create SAVE-SET.FDL:   RECORD%         FORMAT                  fixedR$         SIZE                    8192   Then create BACKUP_SERVER.COM:     $ ! A   $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.T   $ !i   $ set noon   $ set rms/network=16   $ allocate mka500 tapedevu4   $ mount/nounload/over:id/block=8192/assist tapedev2   $ convert/fdl=SAVE-SET sys$net tapedev:save-set.   $ dismount/unload tapedeve
   $ stop/id=0e    A On the node where you want to do the backup, use the DCL command:i     $ 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, BACKUP E won't see the reel switch and will split an XOR group across the reel E boundary. As far as I remember, BACKUP will be willing to read such atE multi-reel save set (directly, not over the net) since the XOR blocks-F 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).m 						[Stephen Hoffman]v  < ------------------------------------------------------------3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSCc  K The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSC are used to connect fM to storage controllers via the Diagnostics and Utility Protocol (DUP).  ThesesK commands require that the FYDRIVER device driver be connected.  This devicetL driver connection is typically performed by adding the following command(s) * into the system startup command procedure:       On OpenVMS Alpha:S       $ RUN SYS$SYSTEM:SYSMANn;       SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVER        On OpenVMS VAX:e       $ RUN SYS$SYSTEM:SYSGENi$       SYSGEN> CONNECT FYA0/NOADAPTER  M Alternatives to the DCL SET HOST/DUP command include the console >>> SET HOSToA command available on various mid- to recent-vintage VAX consoles:o  8     Access to Parameters on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMSu  @     Access to Directory of tools on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECTS  4     Access to Parameters on a KFQSA DSSI controller:;       >>> SHOW UQSSP ! to get port_controller_number PARAMS-:       >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  I These console commands are available on most MicroVAX and VAXstation 3xxxnE series systems, and most (all?) VAX 4xxx series systems.  For furtherhK information, see the system documentation and -- on most VAX systems -- see  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.  L This manual specifically covers the hardware, which is something not covered2 by the standard OpenVMS VMScluster documentation.)   Also see MGMT58. 						[Stephen Hoffman]t  < ------------------------------------------------------------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).   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.e  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 arK distribution kit, simply answer "NO" to the question asking you if you want L 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.   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     $$$ DEFINE/SYSTEM 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 areLH "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 willmM then want to use the PCSI command PRODUCT INSTALL to install the DECnet Phaset+ IV kit from the OpenVMS distribution media.   G Information on DECnet support, and on the kit names, is included in thep4 OpenVMS V7.1 installation and upgrade documentation.   						[Stephen Hoffman]e  < ------------------------------------------------------------< 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 basedOM on identifiers present in the OpenVMS rightslist.  Documentation on this areag= is included in the _Guide to OpenVMS System Security_ manual.a  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 newgroupido*     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:h  3     UAF> add/ident/value=uic=[group,user] newuseridm  M The UIC user identifier text is assigned when the username is created, and ishN 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 of L this identifier is [groupnumber, 177777]. To add a missing group identifier, use an asterisk as follows:f  1     UAF> add/ident/value=uic=[group,*] newgroupid-  M You may find cases where an identifier is missing from time to time, as therenJ 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 utility N will not create the conflicting group and/or user identifier when the username is created.   K You can can add and remove user-specified identifiers, but you should avoid0J 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 securityt manual for details.a  < ------------------------------------------------------------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:)  (      From V1.0, one can upgrade to V1.5.5      From V1.5, or V1.5-1H1, one can upgrade to V6.1.j(      From V6.1, one can upgrade to V6.2.1      From V6.1, or V6.2, one can upgrade to V7.0. G      From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0, one can upgrade to V7.1.eB      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-10      From V6.2, ... or V7.2, to V7.2-1H1, to 7.3G      From V7.1, one can update to V7.1-1H(1,2), ... to V7.2-1H1, to 7.3i  >      Some typical OpenVMS Alpha upgrade (or update) paths are:?          V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)p;          V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)v          V6.2 -> V6.2-1H3t          V6.2 -> V7.2-1b          V6.2 -> V7.3o          V6.2-1H(1,2,3) -> V7.1 !          V6.2-1H(1,2,3) -> V7.2-1O          V7.1 -> V7.1-2t          V7.1 -> V7.2-1           V7.1-1H(1,2) -> V7.1-2n          V7.1-1H(1,2) -> V7.2-1D          V7.2 -> V7.2-1H1G          V7.2 -> V7.3   G      Note that OpenVMS Alpha V7.0 does not include support for hardware E      and/or configurations first supported in OpenVMS Alpha V6.2-1H1,.A      V6.2-1H2, or V6.2-1H3; one must upgrade to OpenVMS VAX V7.1.e  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-1HxiF      from any release prior to V7.1 -- this is not supported, and doesE      not produce the expected results.  The LHR kits can, however, be-E      directly booted and can be directly installed, without regard toyC      any operating system that might be present on the target disk.   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.  v  F      OpenVMS Alpha V7.1-2 and later use PCSI for LHRs and for OpenVMS C      upgrades and for all OpenVMS ECO kit installations.  VMSINSTALiE      OpenVMS ECO kits are not used on OpenVMS Alpha V7.1-2 and later. D      Prior to V7.1-2, VMSINSTAL-based ECO kits are used for OpenVMS.    %    OpenVMS VAX release upgrade paths:S  A      From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5.o?      From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.n;      From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.r=      From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1. 1      From V6.0, or V6.1, one can upgrade to V6.2.i1      From V6.1, or V6.2, one can upgrade to V7.0.S7      From V6.1, V6.2, or V7.0, one can upgrade to V7.1.bD      From V6.1, one can upgrade to V7.3 (with VAXBACK ECO for V6.1).  0      Some typical OpenVMS VAX upgrade paths are:;          V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.1, V7.2, V7.3)e          V5.5-2HW -> V5.5-2w=          V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)e6          V6.1 -> V6.1 with VAXBACK ECO -> (V7.2, V7.3)          V6.2 -> V7.2t          V6.2 -> V7.3e  E      Note that OpenVMS VAX V6.0 does not include support for hardware-C      and/or configurations first added in OpenVMS VAX V5.5-2H4, oneV&      must upgrade to OpenVMS VAX V6.1.  G      Note that OpenVMS VAX V5.5-2HW is a pre-release version of V5.5-2.nB      Any system running it should be upgraded to V5.5-2, or later.  E      If you attempt a direct upgrade from OpenVMS VAX V6.1 to V7.2 orrH      later without having first applied the VAXBACK ECO kit to your V6.1/      system, you will receive an error message:t  ;        %BACKUP-E-INVRECTYP, invalid record type in save setm  F      and the upgrade will fail.  Acquire and apply the VAXBACK ECO kitF      for OpenVMS VAX V6.1.  OpenVMS VAX V6.2 and later do not require ?      an application of an ECO for an upgrade to V7.2 and later.e    $    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.o  L      OpenVMS Cluster rolling upgrades for both OpenVMS VAX and OpenVMS AlphaG      may (will) have different, or additional upgrade requirements, andeC      have requirements around which versions of OpenVMS can coexista3      in a OpenVMS Cluster than what is listed here.u  K      See the _OpenVMS <platform> Version <Version> Upgrade and Installationt;      Manual_, and the OpenVMS Software Product Descriptionsu  &        http://www.compaq.com/info/spd/?        OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.n  O      for further details on the rolling upgrade, and for support information.  mI      The documentation for older releases of OpenVMS VAX includes variouswF      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 iA      Product Support (including information on support end dates n;      for OpenVMS and various layered products), please see:h  =        http://www.compaq.com/services/software/ss_mature.htmlAB        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, and 4      minimum required layered product versions, see:  A        http://www.openvms.compaq.com/openvms/os/swroll/index.htmle  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:   =        http://www.openvms.compaq.com/openvms/20th/vmsbook.pdft      OpenVMS Alpha Terminology:D  B      update:    Typically used for Limited Hardware Releases (LHR)A                 releases.  Performed via VMSINSTAL.  Applies onlyn@                 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 alloG                 files and features of previous LHRs in the same series.e  F      upgrade:   Performed via PCSI.  Upgrades can typically be appliedE                 to a release-specific (and documented) range of priorh!                 OpenVMS releases.-  F      install:   Performed via PCSI.  With an installation, no existingG                 version of the operating system is assumed present, noroI                 are any files from any copy of the operating system mightVK                 be present preserved, and the entire contents of the targetS=                 disk are destroyed via a disk initialization.i  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 operatingm>                 system files on the target disk are clobbered.  G      LHR:       Limited Hardware Release.  LHRs are specific to and are D                 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?I  E Seeing a negative number in the reservable pages portion of the SHOW sI MEMORY/FULL command can be normal and expected, and is (even) documented aD behaviour.  A pagefile with a negative number of reservable pages isK overcommitted, which is generally goodness assuming that every process with L reserved pages does not try to occupy all of the reserved pagefile  space at the same time.    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 outdH 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 pagefilen users.)l  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 additional)
 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 spacesK available in the pagefile remains adequate.  If  either of these situations-0 arises, additional pagefile storage is required.  G Additional pagefile information: Additional pagefiles can typically be  J 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 availableSE 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, seeoH 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?O  K The Software Public Rollout Reports for OpenVMS list the current and future L availability of Compaq's software products shipping on the Software ProductsG Library kits (CDROM consolidations) for OpenVMS Alpha and OpenVMS VAX. hK Specifically, the required minimum versions for product support are listed.i  N Comprehensive Public Rollout Information, listing previous product versions asM well as currently shipping versions, has been compiled into a separate set ofPN 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, J 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:i<   http://www.openvms.compaq.com/openvms/os/swroll/index.html   					[Stephen Hoffman]  < ------------------------------------------------------------3 MGMT19. How do I change the volume label of a disk?i  G   Dismount the disk, and mount it privately.  If the disk is mounted bynF   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 other -   nodes that are bootstrapped from this disk.h  ?   Issue the SET VOLUME/LABEL command, specifying the new label.u  >   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 reflecte   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 eI   the DECnet MOP or LANCP boot database, as well as any references to thei&   disk created by CLUSTER_CONFIG*.COM.  !   Remount the disk appropriately.f 					[Stephen Hoffman]:                                         [John E. Malmberg]  < ------------------------------------------------------------/ MGMT20.  How do I fix a corrupt BACKUP saveset?D  E   BACKUP savesets can be corrupted by FTP file transfers and by tools:C   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]DD   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, a SET FILE/ATTRIBUTES command can also be used.  -H   As the parameters of this command must be varied as the target BACKUP <   saveset attributes vary, this approach is not recommended.  K   Also see the "SITE VMS", /FDL, and various other file-attributes options hG   available in various FTP tools.  (Not all available FTP tools supportu   any or all of these options.)a  I   Browser downloads (via FTP) and incorrect (binary or ascii FTP transferEH   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):U  G     ftp://host/urlname.ext;type=i   ! request ftp image/binary transferAE     ftp://host/urlname.ext;type=a   ! request ftp ascii/text transfers  H   You can also often configure the particular web browser to choose the E   appropriate transfer mode by default, based on the particular file  H   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.h   					[Stephen Hoffman]  < ------------------------------------------------------------- MGMT21.  How can I set up a shared directory?1  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.a  K The following also shows how to set up a resource identifier, which furtherfJ 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 addedi in the disk quota database.t  " Add an identifier using AUTHORIZE:3   ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifieri  ? Grant the identifier to each user in the group using AUTHORIZE:u+   GRANT/IDENTIFIER groupidentifier usernamer  A If disk quotas are in use, add an entry via SYSMAN for each disk:pF   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)u?   (IDENTIFIER=groupidentifier,ACCESS=READ+WRITE+EXECUTE+DELETE)V+   (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)g  K If there are files already resident in the directory, set their protections.L 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 viapC the explicit identifier granting access that is present in the ACL.p  I For further information, see the OpenVMS Guide to System Security Manual,(L 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 control J   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):   )     http://www.openvms.compaq.com/wizard/   L   There are a variety of discussions of this and of related printing topics    in the Ask The Wizard area.s     Also see MGMT51. 					[Stephen Hoffman]    < ------------------------------------------------------------E MGMT24. Configure ELSA GLoria Synergy or PowerStorm 300/350 graphics?o  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:   "     VMS712_GRAPHICS-V0300 or later!     VMS72_GRAPHICS-V0100 or laterO"     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]V  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) SE   was once available, but has been superceded and is not recommended.tD   Use of V7.1-2 or later (and use of one the above GRAPHICS kits as +   required) is typically the best approach.s  D   OpenVMS V7.2-1H1 and later should directly support the controller.     Additional information:V@     http://www.openvms.compaq.com/wizard/ topics (3419), (5448).     ----     PowerStorm 300 : PBXGD-ACo   PowerStorm 350 : PBXGD-AEo  @   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:u,     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     ----  #   PowerStorm 3D30, PowerStorm 4D20:V7     http://www.openvms.compaq.com/wizard/ topic (2041).E     ----  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.d   					[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:t  $   http://search.service.digital.com/*   ftp://ftp.support.compaq.com/public/vms/8     (formerly ftp://ftp.service.digital.com/public/vms/)(   http://ftp.digital.com.au/pub/ecoinfo/)   http://ftp/digital.com.au/cgi-bin/grep/e  3 You can subscribe to an email notification list at:y  :   http://www.support.compaq.com/patches/mailing-list.shtml  5 A quarterly distribution is also available on CD-ROM:       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 orV2 individual notifications) directly from Compaq at:  =     http://www1.service.digital.com/patches/mailing-list.htmlf  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  F 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.c  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  /   easy -- if you know the secret incantation...n     From OpenVMS:p       $ RUN SYS$SYSTEM:SYSGENV"     SYSGEN> CONNECT FYA0/NOADAPTER     SYSGEN> ^Z=     $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>      ...:     PARAMS> STAT CONFeC     <The software version is normally near the top of the display.>/     PARAMS> EXIT     ...l  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 PARAMSe  
     KFQSA:  <         >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  G   For information on how to get out into the PARAMS subsystem, also seepH   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).a  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 name 2   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 an 8   OpenVMS Cluster tape allocation class are also unique. 					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT27. How do I move the queue manager database?r  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 pJ   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-memorys8       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 location        for safety.L 	 E 	$ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]    i    iN    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 allb       nodes in the cluster i   	$ 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]   '    5.  Delete the old queue database.  -  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]L  < ------------------------------------------------------------> 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:p  4     $ TCPIP SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  '   For earlier TCP/IP Services versions:n  2     $ UCX SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  < ------------------------------------------------------------ MGMT29 relocated to ALPHA21t  < ------------------------------------------------------------C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?   C "Undeleteable" jobs are usually "undeleteable" for a reason -- thisrE 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 particulareD device supports firmware, ensure that the device firmware is currentG -- TQK50 controllers are known for this when working with old firmware. G (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.   D Useful tools include SDA (to see what might be going on) and DECamdsA (which increase and thus potentially fix quota-related problems).SB (nb: Applications with quota leaks will obviously not stay fixed.)  ? If the stuck application is BACKUP, ensure you have the currentt@ BACKUP ECO and are directly following the V7.1 or (better) V7.2 ; process quota recommendations for operator BACKUP accounts.f  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 whomeverpH is maintaining the device driver for the particular device/widget/driverK involved, with any details on how you got into this situation.  (The rebootiE involved with taking the crashdump will obviously clear the problem.)m  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, thepD 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 IC mechanism to reset error counts once the error(s) have been logged.h  C As for an unsupported approach -- and be aware of the potential forh 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 theiG device's UCB structure.  On VAX, the field is at an offset symbolicallymG defined as UCB$W_ERRCNT.  On Alpha, this field's offset is symbolicallylE defined as UCB$L_ERRCNT.  The former is a word in size; the latter isyE a longword.  (Could it be that Alpha devices are more error prone? ;)e  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 will-E see designations in {} separated by a /.  The first item in braces isgE to be used on the VAX and the second item should be used on an Alpha.v (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}_ERRCNTs9 Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offsetm  1 Record the hexadecimal value 'hhhhhhhh' returned.   G You can now exit from SDA and $ RUN SYS$SHARE:DELTA or do what I preferM to do, issue the following:o   SDA> SPAWN RUN SYS$SHARE:DELTA  I On both VAX and Alpha, the DELTA debugger will be invoked and will ident-aG ify itself.  On Alpha, there will be an Alpha instruction decoded.  ForTI those unfamiliar with DELTA, it does not have a prompt and only one erroreI message -- Eh?  (Well, for sake of argument, there might be another erroroF 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?-   Now issue the command 1;M-  DELTA will respond with 00000001  I You're now poised to ZAP the error count field.  To do so you need to en-tH 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: 00010001i  . 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.aJ 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 carriagelH return and then enter the command EXIT to get out of DELTA.  Regroup and! see where your session went awry.-  I If you entered your address correctly and the error count was returned asl* 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:d    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?c  6 For various SCSI-based MK-class magnetic tape devices:  6     $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2")     $ Comp_sup = %X00200000t     $ Comp_ena = %X00400000e5     $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -i0         WRITE SYS$OUTPUT "Compression supported"5     $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN - .         WRITE SYS$OUTPUT "Compression enabled"  < ------------------------------------------------------------? MGMT33. Can I copy SYSUAF to another version? To VAX? To Alpha?   > The format of the SYSUAF.DAT, RIGHTSLIST, and associated files= are upward-compatible, and compatible across OpenVMS VAX and -9 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 r6 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 eA in merging these files in an OpenVMS Cluster -- see the appendix aB of the OpenVMS Cluster documentation for details of merging files.C (You might not be merging the contents of two (or more) files, but t? you are effectively merging the contents of the files into the e target system environment.)i   Considerations:   >   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 u>     on the contents of the NETPROXY.DAT during the OpenVMS VAX;     V6.1 upgrade and during the OpenVMS Alpha V6.2 upgrade.E:     This file is maintained in parallel with NETPROXY.DAT.  =   o the RIGHTSLIST identifier values and UIC values that end n?     up scattered around the target system must be rationalized A=     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 f> 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 S= perform the same function.  In most cases, they will not.  Asi= such, you will have to find and chance all references to the -< 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 i? no particular access will be granted.  And any DCL commands or a@ such that reference the old alphanumeric name will fail, rather 7 than silently (and potentially erroneously) succeeding.-  < 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 associated 7 with disks, ACLs, queues, and various other structures.s  < 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 a> Cluster), please see the SYLOGICALS.TEMPLATE file included in   OpenVMS V7.2 and later releases.  = Procedures to extract the contents of a (potentially corrupt)r< queue database are provided on the OpenVMS Freeware (V5) and9 can be used to combine two queue databases together whilea. shuffling files between OpenVMS Cluster hosts.  ? For related discussions of splitting a cluster into two or for C; removing a node from cluster (political divorce, etc), see: C   http://www.openvms.compaq.com/wizard/ topics (203), (767), (915).  					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT34. How do I delete (timeout) idle processes?o  F   There is no such command integrated within OpenVMS, though there areI   (optional) timers available within certain terminal servers and similarbI   devices, and there is an integrated time-of-day mechanism that provides1.   control over when a user can access OpenVMS.  K   As for available tools, there are DECUS, freeware, and third-party tools 1G   known variously as "idle process killers" (IPK) or terminal timeout" -G   programs.  Examples include: Saiga Systems Hitman, Watchdog, MadGoat oF   Watcher (via the MadGoat site or the OpenVMS Freeware), Kblock, the ?   Networking Dynamics tool known as Assassin, and the Zap tool.b  ;   A related package (for DECwindows sessions) is xtermlock.d  I   If the forgetful users are in an application menu environment, the menu-9   can potentially be extended to provide this capability.e  < ------------------------------------------------------------. 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 directorypJ   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.M  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 directorynD     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 -K     OpenVMS versions (and ECO kits).  Use of this qualifier informs BACKUP rM     that you are aware of the limitations of the old BACKUP behaviour around o"     incremental disk restorations.  I   Consider performing an incremental restoration, to test the procedures.MG   Attempting this is how we found out about the problem that was latentOF   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)?d  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 OpenVMS G   TELNET command CREATE_SESSION.  This command is the equivilent of thetG   operations performed in LTLOAD.COM or LAT$SYSTARTUP.COM.  There is noeH   TELNET equivilent to the sys$qio[w] control interface for LTDRIVER (asC   documented in the I/O User's Reference Manual) available, though eD   standard sys$qio[w] calls referencing the created TN device would    likely operate as expected.u  < ------------------------------------------------------------? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?C  D   DECevent and Compaq Analyze are avalable to customers with supportE   contracts.  The PAK is required only for the advanced functions of dE   DECevent, the basic bits-to-text translation of the error log does hB   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 -E   contract or warrantee, and the PAK enables the use of the advanced o@   error analysis and notification capabilities within DECevent.)  5   Please see the DECevent FAQ for additional details:o  A http://www.support.compaq.com/svctools/decevent/DECevent_FAQ.htmlo  ?   The current version of the DECevent (Compaq Analyze) tool cans   be downloaded from:   7 http://www.support.compaq.com/svctools/st-download.htmld  < ------------------------------------------------------------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 DCLtB INITIALIZE command is known to encounter access violation (ACCVIO) errors.4  C The available solutions include upgrades, or setting the date back. E Direct initialization of the tape with the new headers (via $qio) is  G also clearly possible, though the limitation within the old MTAACP.EXE ]2 magtape ACP image is not nearly so easy to bypass.  B                                                [Hoffman, Dachtera]  < ------------------------------------------------------------/ MGMT39. How do I recover from INSVIRMEM errors?I  ?   Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX releases, PC   VIRTUALPAGECNT and PGFLQUOTA limit the amount of virtual address t,   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.0-D   and on all OpenVMS VAX releases, VIRTUALPAGECNT and MAXPROCESSCNT E   together determine the size of the page table data structures that oG   occupy large tracts of system space.  When no system virtual address jE   space is available for the stuff that needs it -- this includes the C   page tables, non-paged pool, and various other structures -- then E   the values of VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.l  G   In OpenVMS Alpha V7.0 and later, the page table data structures have uC   been moved out of S0 and S1 space and into page table space.  In aD   OpenVMS Alpha V7.2 and later, certain large data structures found E   in non-paged pool (eg: lock management structures) have been moved nB   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?m  *   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 uprB   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 lK   16 bytes long, and is used as a counted string of 0-15 characters (ie, a VJ   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 h%   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 inrN   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 eK   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. (Onlyt%   images have this field, obviously.)B  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 aJ       last ten characters are a ten digit number with leading zeros, then G       the last ten characters are treated as a valid generation number.AI     - for V7.1-2 through V7.2-1, inclusive, if the above test fails, the h=       information is obtained from the PCSI product database.dL     - 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  I       that the ECO kit will simply replace the image rather than assumingR$      the PCSI database is in error.  E   So, what will you see in the image identification displayed via theu   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 thatg'   have not yet been processed via PCSI.e  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,  L   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.o  < ------------------------------------------------------------@ MGMT42. How to configure allocation classes and Multi-Path SCSI?  K The HSZ allocation class is applied to devices, starting with OpenVMS V7.2.yL 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 thisqJ 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 rE class to zero, and setting the PKB PAC to -1.  This will use the hostrG allocation class, and will leave the controller letter alone (that is,  L 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 r 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, port I and HSZ/HSJ, as otherwise you could wind up with device naming conflicts   that can be painful to resolve.i  I The display-able path information is for SCSI multi-path, and permits the-G 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 nI 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 p/ software to distinguish between these two UCBs.u  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  L 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, rJ 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 sF more deterministic than negotiating the controller letter between the I nodes, and also parallels the solution used for this situation when DSSI s or SDI/STI storage was used.  I This information is also described in the Cluster Systems and Guidelines l+ for OpenVMS Cluster Configurations manuals.e;                                                [John Croll]l  < ------------------------------------------------------------@ MGMT43. How can I tell what software (and version) is installed?  A   There is unfortunatly no consistent nor single way to make thisUA   determination -- this is one of the reasons that a move to PCSIe   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.T  A   To see which OpenVMS Alpha ECO kits have been applied, look in t>   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 (foru=   software that is installed via VMSINSTAL on V7.3 and later)o   in VMSINSTAL.HISTORY.i  ;   For products installed on OpenVMS VAX prior to V7.3 usingi@   VMSINSTAL, there is no reliable way to determine what products?   have been installed.  If the product provides a RELEASE_NOTESe=   file (as many do), you can look for the list of these filesh?   via DIRECTORY SYS$HELP:*.RELEASE_NOTES.  Again, this approachs@   is NOT reliable: some kits do not provide release notes, some C   system managers will install only the release notes, some system iE   managers will delete release notes, and release notes for multiple y   versions can be present.  E   On most packages, you can generally use ANALYZE/IMAGE on one of theiE   core images, looking at the image identification area.  Some of thec,   product-specific mechanisms available are:  "     DQS   DQS$VERSION logical name     C     CC/VERSION     C++   CXX/VERSIONa    < ------------------------------------------------------------@ 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,eK   and there is no way to remove it.  You can, however, remote site-specificCB   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 systemt>   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:h  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 gD     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  B   o To customize the processing of file extensions within DCPS (toI     enable or disable graybar output, for instance), use the information n     available in:S  ;       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT   %     to create your own site-specific:s  3       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DATn     Also see MGMT23.D                                          [Ken Fairfield, with typos G                                          introduced by Stephen Hoffman]h  < ------------------------------------------------------------D MGMT52. Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts differ?  C   MOUNTCNT returns the local mount count, while SHOW DEVICE returnst   the cluster-wide mount count.s  :                                          [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)cC   are common choices for support of Postscript printers on OpenVMS.c  < ------------------------------------------------------------D MGMT54. Does volume shadowing require a non-zero allocation classes?  C   Yes, use of host-based volume shadowing requires that the disk(s)d8   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 s   class to the value 7:s     ALLOCLASS = 7n  &   Then AUTOGEN the system, and reboot.  B   You should now be able to form the shadow set via a command such   as the following:t  >     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 withtF   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.i;                                               [Veli Korkko]s  < ------------------------------------------------------------! MGMT55. section duplicated MGMT28a  < ------------------------------------------------------------9 MGMT56. How do I remove a PCSI-installed patch (ECO) kit?   1 You cannot PRODUCT REMOVE a PCSI patch (ECO) kit.A  E In order to do this, PCSI would have to have copies of all the other SI version of the files from all other patches and products that previously pE were installed.  This can clearly involve a large number of files andUB a large archive of old file versions and a substantial quantity ofC disk space.  While removal is clearly theoretically possible, it isn 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 thatT.     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" t     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:e  #     $ HELP/MESSAGE /STATUS=%X72832Cl  < ------------------------------------------------------------/ MGMT58. Performing SET HOST/MOP in DECnet-Plus?   &   First, do MCR NCL SHOW MOP CIRCUIT *  /   Let's say you have a circuit known as FDDI-0.l8   Here is an example of the SET HOST/MOP command syntax:  ;     $ SET HOST/MOP/ADDRESS=08-00-2B-2C-5A-23/CIRCUIT=FDDI-0d     Also see MGMT13.  < ------------------------------------------------------------' MGMT59. Resolving License PAK Problems?   E   The PAK release date, the PAK termination date, and the PAK versionsG   are the usual culprits when a license product authorization key (PAK)k   check failure occurs.s  H   The PAK termination date is the date when the license PAK will expire.  I   The PAK release date is the date of the most recent release date of theoH   software package that will be permitted by the particular license PAK.C   (The release date check is analogous to a product version check.) C   The PAK version indicates the most recent product version that isp   permitted by the license.   E   Having multiple license PAKs registered (and active) can also causeoC   problems if an expired PAK gets loaded.  You will want to DISABLEe.   license PAKs you do not wish to have loaded.  F   Other problems include a failure to register each PAK in all licenseH   databases throughout a multiple-system-disk cluster, with a consistentE   set of /INCLUDE lists specified across each of the duplicated PAKs.t  K   Additionally, you could have an invalid LMF$LICENSE logical name defined.IK   (If no LMF$LICENSE logical name is defined, the standard license databaseG1   named SYS$SYSTEM:LMF$LICENSE.LDB will be used.)L  J   You can display license failures by defining the following logical name:  2     DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE  K   Enable your terminal as a license operator (REPLY/ENABLE=LICENSE), defineoF   the LMF$DISPLAY_OPCOM_MESSAGE logical name, and then try the failingH   operation again.  You should see one or more OPCOM messages displayed.  I   If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name defined, you canYF   (will?) see spurious license check failures -- various products willJ   check for multiple licenses, and a few products will check for PAKs thatL   either have not yet been or will not be issued.  Once you figure out whichB   license has failed, you will want to deassign this logical name.  E   Note: that there is no license check failure does NOT indicate that E   the particular product or operation is permissible per the license.   I   To register a license PAK on a DECwindows system when DECwindows cannot K   start (because of an expired license or other licensing problem), follow ML   the steps outlined in section MGMT5 up through step 4 (inclusive).  Using J   the console -- analogous to what is done in step 5 to access the OpenVMSD   AUTHORIZE utility -- use the console to register the license PAKs.       [End of Part 2/5]t  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 02 Oct 2001 21:32:52 GMTr2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 3/5 1 Message-ID: <8oqu7.959$YP.25678@news.cpqcorp.net>a   Archive-name: dec-faq/vms/part3n Posting-Frequency: quarterly Last-modified: 2 Oct 2001M Version: VMS-FAQ-3.TXT(7)     9 This is the OpenVMS Frequently Asked Questions Part 3/5.  @ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------, MGMT60. Changing the OpenVMS Version Number?  D   Fool your friends, baffle your enemies, run the OpenVMS version of   your choice!     OpenVMS Alpha:&     $ SET DEFAULT SYS$COMMON:[SYS$LDR]     $ RUN SYSVER     REPLACE V9.9	     WRITEe
     $ EXIT     OpenVMS VAX:&     $ set default SYS$COMMON:[SYS$LDR])     $ copy SYS.EXE SYS.EXE_IN-CASE-I-FAILn     $ patch SYS.EXEA"     define sys$gq_version=800044b8     set mode ascii     !examine sys$gq_versionI     !examine sys$gq_version+4n%     deposit sys$gq_version   = "V9.9"a%     deposit sys$gq_version+4 = "    " 
     update     exit
     $ Exit  )   Then reboot the system at your leisure.y  < ------------------------------------------------------------9 MGMT61. Explain disk (or tape) allocation class settings?.  H   The allocation class mechanism provides the system manager with a way F   to configure and resolve served and direct paths to storage devices D   within a cluster.  Any served device that provides multiple paths H   should be configured using a non-zero allocation class, either at the G   MSCP (or TMSCP) storage controllers, at the port (for port allocationtF   classes), or at the OpenVMS MSCP (or TMSCP) server.  All controllersE   or servers providing a path to the same device should have the samen>   allocation class (at the port, controller, or server level).  H   Each disk (or tape) unit number used within a non-zero disk (or tape) G   allocation class must be unique, regardless of the particular device  I   prefix.  For the purposes of multi-path device path determination, any eG   disk (or tape) device with the same unit number and the same disk (orfH   tape) allocation class configuration is assumed to be the same device.  I   If you are reconfiguring disk device allocation classes, you will want rG   to avoid the use of allocation class one ($1$) until/unless you have oI   Fibre Channel storage configured.  (Fibre Channel storage specifically d;   requires the use of allocation class $1$.  eg: $1$DGA0:.)   < ------------------------------------------------------------= MGMT62. How to prevent users from choosing obvious passwords?   C   To prevent users from selecting obvious passwords on OpenVMS, you H   will want to use the reserved password (password screening) mechanism.A   Effectively, you merge your list of reserved passwords into theeC   existing reserved words database maintained by OpenVMS.  (You canoA   also then require all users to reset their passwords -- via thehD   pre-expired password mechanism -- thus forcing users to select newF   passwords.)  For details on the password screening mechanism, of theH   reserved password database (VMS$PASSWORD_DICTIONARY.DATA), and detailsF   of how to merge your list of prohibited passwords into the database,C   please see the associated chapter in the OpenVMS security manual.vE   For details of the password expiration mechanism, see the AUTHORIZEh    command qualifier /PWDEXPIRED.  A   You can also implement a site-specific password filter with theiF   information provided in the back of the OpenVMS Programming ConceptsB   manual.  The password filter permits you to establish particularC   and site-specific password requirements.  For details, please see C   the system parameter LOAD_PWD_POLICY and the programming concepts ?   manual, and see the examples in SYS$EXAMPLES:.  (Examples andsF   documentation on V7.3 and later reflect both platforms, the examples>   are found only on OpenVMS VAX kits on earlier releases.  TheC   capabilities have existed on both the VAX and Alpha platforms forr   some time now.)   D   To verify current passwords, you can also use a technique known toH   system crackers as the "dictionary attack" -- the mechanism that makesF   this attack somewhat more difficult on OpenVMS is the hashing scheme?   used on OpenVMS, and the file protections used for the SYSUAFv>   authorization database.  Given a dictionary of words and the?   unprotected contents of the SYSUAF file, a search for obvious C   passwords can be performed.  Interestingly, a "dictionary attack" B   also has the unfortunate side-effect of exposing the password toA   the user -- while this is clearly the goal of a system cracker,aB   authorized privileged and non-privileged system users should notC   know nor have access to the (cleartext) passwords of other users.y  G   Accordingly, OpenVMS does not store the cleartest password.  Further,VI   OpenVMS uses a password hashing algorithm, not an encryption algorithm. I   This means that storage of a cleartext password is deliberated avoided,iC   and the cleartext value is deliberately very difficult to obtain.a>   The hash is based on a Purdy Polynomial, and the hash itselfC   includes user-specific values in addition to the password, valuesdA   that make the results of the password hash unique to each user.   B   Regardless of the use of a password hashing scheme, if a copy ofE   your password file should become available to a system cracker, youS@   will want to force all users to use new passwords immediately.  F   If you should require a user to verify a password, use the username,D   the user's salt value (this value is acquired via $getuai) and theG   user's specified cleartext password, and compare the resulting hashed-J   value (using a call to $hash_password) against the saved hashed passwordI   value (this value also acquired via $getqui).  For reasons of security,SG   avoid saving a cleartext password value in any data files, and do not A   maintain the cleartext password in memory longer than required.a  E   Kerberos authentication (client and server) is available on OpenVMS-F   V7.3 and later.  Integration of Kerberos support into various Compaq,   and into third-party products is expected.  E   If you are simply looking for OpenVMS access and the SYSTEM and allrD   other privileged passwords are forgotten or otherwise unavailable,@   please see section MGMT5 and/or the OpenVMS documentation set.  C   Also please see the C2 guidelines in the OpenVMS security manual.   < ------------------------------------------------------------/ MGMT63. Volume Shadowing MiniCopy vs MiniMerge?-  E Mini-Merges have been supported for many years on VMS, as long as youR@ had MSCP controllers (i.e. HSC, HSJ, or HSD) which supported the7 Volume Shadowing Assist called 'Write History Logging'._  A If you want mini-merges on HSG80 (Fibre Channel) controllers, the @ latest info I've seen (the "Fibre Channel in a Disaster-Tolerant% OpenVMS Cluster System" whitepaper atp? http://www.openvms.compaq.com/openvms/fibre/fc_hbvs_dtc_wp.pdf)y@ indicates that this will require ACS 8.7 and VMS 7.3-1, assuming things go according to plan.  C Since there have already been responses in this thread referring tod> the Mini-Copy capability, and I don't know if you really meant< Mini-Merge or Mini-Copy, it might be helpful to describe the, difference between Mini-Merge and Mini-Copy.  ? A Shadowing Full Copy occurs when you add a disk to an existingSD shadowset using a MOUNT command; the entire contents of the disk areB effectively copied to the new member (using an algorithm that goesC through in 127-block increments and reads one member, compares withp@ the target disk, and if the data differs, writes the data to theD target disk and loops back to the read step, until the data is equal for that 127-block section).  E If you warn VMS ahead of time (at dismount time) that you're planningHF to remove a disk from a shadowset but re-add it later, VMS will keep aD bit-map tracking what areas of the disk have been modified while theB disk was out of the shadowset, and when you re-add it later with aC MOUNT command VMS only has to update the areas of the returned diskeE that the bit-map indicates are now out-of-date.  VMS does this with aeC read source / write target algorithm, which is much faster than theE? shenanigans the Full Copy does, so even if 100% of the disk has 0 changed, a Mini-Copy is faster than a Full Copy.  D A Shadowing Merge is initiated when a VMS node in the cluster (whichB had a shadowset mounted) crashes or otherwise leaves unexpectedly,@ without dismounting the shadowset first.  In this case, VMS mustF ensure that the data is identical, since Shadowing guarantees that theA data on the disks in a shadowset will be identical.  In a regulareE Merge operation, Shadowing uses an algorithm similar to the Full Copy D algorithm (except that it can choose either of the members' contentsA as the source data, since both are considered equally valid), andt@ scans the entire disk.  Also, to make things worse, for any readD operations in the area ahead of what has been merged, Shadowing willE first merge the area containing the read data, then allow the read too occur.  B A Merge can be very time-consuming and very I/O intensive, so some= controllers have Shadowing Assists to make it faster.  If thetE controllers support Write History Logging, the controllers record the$D areas (LBNs) that are the subject of Shadowing writes, and if a nodeB crashes, the surviving nodes can query the controllers to find outB what exact areas of the disk the departed node was writing to justC before the crash, and thus Shadowing only needs to merge just those B few areas, so this tends to take seconds as opposed to hours for a regular Merge.7                                          [Keith Parris]H  < ------------------------------------------------------------. MGMT64. Why is BACKUP not working as expected?  '   First, PLEASE READ THE BACKUP MANUAL.   0   Second, PLEASE GET THE CURRENT BACKUP ECO KIT.  E   BACKUP has a very complex interface, and there are numerous commandwE   examples and extensive user documentation available.  For a simplerpA   user interface for BACKUP, please see the documentation for them   BACKUP$MANAGER tool.  4   As for recent BACKUP changes, oddities, bugs, etc:  K   o A change made in OpenVMS V6.2 WILL cause more files to be included into-K     a file-based BACKUP saveset using /SINCE=BACKUP as all files underneathcM     any directory with a sufficiently recent (selected) date will be includediH     in the saveset.  This change was deliberate and intentional, and wasI     mandated by the need to provide a functional incremental restoration.t  I     Without the inclusion of these apparently-extra files, an incremental )     saveset can NOT be reliably restored.e  I   o As part of the OpenVMS V6.2 change, the /SINCE command -- without thenG     specification of the =BACKUP keyword -- selected more files than it$D     should have.  This is a bug.  This bug has been remedied  in theL     OpenVMS BACKUP source code and in some of (all of?) the BACKUP ECO kits.  -   When working with BACKUP, you will want to:k  G   o Get the current BACKUP ECO kit and install it BEFORE you attempt ton     troubleshoot any problems.  F   o Learn about the /NOINCREMENTAL (new) and /NOALIAS (V6.2 and later)E     command qualifiers.  The former qualifier returns to the pre-V6.2cF     behaviour of the /SINCE file selection mechanism, while the latterF     (specified with /IMAGE) reduces the replication of files on systemF     disks and other disks with file alias and directory alias entries.G     Both of these can reduce the numbers of files that will be selectedd'     and thus included into the saveset.R  ,   When working with the BACKUP callable API:  G   o Build your applications with the most current BACKUP API available.lF     Changes made to the V7.1-2 and V7.2 API were incompatible with the@     V7.1 and V7.2-1 and later APIs, and this incompatibility wasF     repaired via a BACKUP ECO kit.  Do NOT build your application withE     the versions of the BACKUP API that shipped with V7.1-2 and V7.2, E     as these are incompatible with the BACKUP API constants that wereS     used on other versions.        < ------------------------------------------------------------$ MAIL1.  How do I send Internet mail?  K The simplest answer on most OpenVMS V6.2 and later systems: just enter the tJ Internet (SMTP) address at the "to" prompt in MAIL.  On most such systems,5 this will send your email to the specified recipient..  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 calledeM transports.  To send mail through a transport,  place the transport specifierE2 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 mailtM 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 systemt manager for assistance.e 					[leichter@lrw.com]d 					[Stephen Hoffman]   See also MAIL2.   < ------------------------------------------------------------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 packagegB (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 MAILLJ will use the translation as the transport protocol, otherwise it will use ? the SMTP transport as is used by TCP/IP Services for OpenVMS.  i  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?t  I OpenVMS 7.0 adds the ability to automatically append signature files - in E MAIL, use the SET SIGNATURE command to specify a signature file name.d3 For earlier versions, see the following paragraphs.k  K The basic MAIL utility which is shipped with VMS does not have an intrinsicoG mechanism for adding signature files.  If you're using an enhanced mail G handling package (e.g PMDF), however, it may have provisions for addingoH 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 messagesyK and news postings.  There are several implementations of this for different I editors available on the net; for one example, see the MAIL_EDIT package.u,   ftp://ftp.process.com/vms-freeware/narnia/    					[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'r $ ELSE $    COPY <signaturefile> 'P2' $ ENDIF $ $ DEFINE/NOLOG SYS$INPUT SYS$COMMAND $ <editorname> 'P2'l $ 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).l 					[Arne Vajhj]  < ------------------------------------------------------------A MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.y  M Several Unix mailers have been ported to VMS, some by the vendors of specific L 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.i 					[Jerry Leichter]u  < ------------------------------------------------------------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 all M your mail forwarded to.  Use SHOW FORWARD to see your current forwarding.  To * 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 wantrG to forward to - say, IN%"fred@fred-host.xxx.com".  Take that string and-J *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"""c  + If you do SHOW FORWARD, you should now see:l  = 	Your mail is being forwarded to IN%"fred@fred-host.xxx.com".s 					[leichter@lrw.com](  C Note that the MAIL$INTERNET_TRANSPORT feature doesn't yet work withsF 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 doestJ 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]l  < ------------------------------------------------------------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 folder$I in SYS$SYSTEM:VMSMAIL_PROFILE.DATA.  It sometimes happens that this count-G differs from what's in your mail folder.  If this happens, go into MAIL I and repeat the READ/NEW command until you see no new mail messages.  ThenlG enter the command one more time.  This will resynchronize the counters.e  < ------------------------------------------------------------@ 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:i  # 	EXTRACT/APPEND/ALL/MAIL mymail.maiF  < Move MYMAIL.MAI to the other system, then do this (in MAIL):   	SET FILE mymail.mai 	COPY/ALL foldername MAIL.MAId  G This will place a copy of all of your messages in the given folder.  IfbI you wanted to maintain the separate folders, do separate EXTRACT commands G (above) specifying different .mai files, then repeat the SET FILE, COPY 
 for each one.e  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 intoc. 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?i  C Not directly with the OpenVMS MAIL facility, but there are several l 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/h4      http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/+      ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/t  K 2. If you're working from an X11 server use the OpenVMS version of Netscape,I    Navigator.  This option is ok for sending mail, but is not optimal forGH    reading it, since Netscape will use POP and remove messages entirely A    the OpenVMS MAIL system, which is not generally what you want.i  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 willoI    cause the message to appear as plain text in most mail programs.  SomedD    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 directlybI    into the SMTP port of your mail machine.  Examples of both methods aret    in: a:      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, thenh;    use MUNPACK to break out and decode the attachments.       C    MPACK/MUNPACK tools are also available on OpenVMS Freeware V5.0: @       http://www.openvms.compaq.com/freeware/freeware50/mpack15/   					[David Mathog]r  ; 4. With OpenVMS V7.2 and later, use the supplied MIME tool.l    < ------------------------------------------------------------. MAIL10.  How can I block SMTP mail relay spam?  E   Use the anti-spam capabilities present in the TCP/IP Services V5.1 l   and later SMTP servers.g     Use a firewall.w  E   On earlier TCP/IP Services releases, some simple DCL can reportedly G   prevent relay SMTP spam.  Use the UCX command SHOW SERVICE SMTP/FULL wG   to find the directory containing the UCX$SMTP_RECV_STARTUP.COM file, r   and insert the following DCL:a  	 $       !s $       ! Block spam. 	 $       ! F $       MY_ADDRESS_LONG[0,32]=F$INTEGER(F$TRNLNM("SYS$REM_NODE")-"::")H $       MY_ADDRESS=F$FAO("!UB.!UB.!UB.!UB",F$CVUI(0,8,MY_ADDRESS_LONG),-C          F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-r(          F$CVUI(24,8,MY_ADDRESS_LONG))'"4 $       MY_ADDRESS_REVERSE=F$FAO("!UB.!UB.!UB.!UB",-D          F$CVUI(24,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-C          F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(0,8,MY_ADDRESS_LONG))'"-I $       WRITE SYS$OUTPUT F$TIME()+" "+F$TRNLNM("SYS$REM_NODE")+MY_ADDRESSM: $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.INPUTS.ORBS.ORG $       IF $STATUS.EQ.1  $       THEN5 $         WRITE SYS$OUTPUT "SPAM from relay rejected"u $         EXIT
 $       ENDIFt? $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.SPAMSOURCES.ORBS.ORGh $       IF $STATUS.EQ.1  $       THEN7 $         WRITE SYS$OUTPUT "SPAM source relay rejected"M $         EXIT
 $       ENDIFp	 $       !w $       ! Run receiver.m	 $       !h, $       run sys$system:ucx$smtp_receiver.exe $       goto exitS  3                                     [Henry Juengst]   < ------------------------------------------------------------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.)tI You can also install the image with these privileges.  See the source for B 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 eJ code and all) with this capability and with the source code of an updated = CD audio player is available on the OpenVMS Freeware website  H (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 hG product includes an unsupported and undocumented utility called PCDISK, A and this tool can read and write various MS-DOS format diskettes.i  H ProGIS in Germany sells a product called VMove which supports DOS files C on many different device types.  For more information, send mail to  info@progis.de.r  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-densityaF disks can be read or written; double-density disks are read-only. Only- high-density disks are supported on the RX33.s     http://www.madgoat.com/t  < ------------------------------------------------------------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 byGH DECwindows Motif, doesn't support this board.  Compaq offers an optional) product, Multimedia Services for OpenVMS:a  !   http://www.compaq.com/info/spd/a   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?a  : 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 iA attempts to support mixed translated-native I/O to the same unit  A by sharing the native Fortran RTL's internal data structures, andO> 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  B spare directory, and then defining the logical name DEC$FORRTL to G point to it before running your translated application.  Or rebuilding PA the application to use the available native Fortran compiler.  OraD you can apply the current Fortran RTL kit, which has a fix for this.   See SOFT13.N2                                     [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 and J 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  K can read and write EBCDIC tapes.  Visit the DECUS website software archiveslC search engine (via http://www.decus.org/), and search for "EBCDIC". 3                                     [Steve Hoffman]i   One source for ETAPE is:  (   http://www.ualr.edu/ftp/vms/ETAPE_SRC/  7 OpenVMS Freeware V5.0 is expected to include this tool.u5                                     [Fletcher Hearns]t1                                     [Dale Miller]e  < ------------------------------------------------------------/ 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 t<   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.exe  	$ unzip -?o  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 arev  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   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 thePJ 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.d  H For more information on foreign commands or on automatic foreign command' support, see the OpenVMS User's Manual.    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.COMe  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 asOF 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.i  G For examples of how TCP/IP Services sets up its foreign commands (which I includes tools such as uuencode and uudecode), please see the DCL commandi0 procedure SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM.   Also see DCL11.o 					[Stephen Hoffman]  < ------------------------------------------------------------/ DCL2.   How can I redefine control keys in DCL?i  C The DCL DEFINE/KEY command allows you to define function and keypad F 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 DELe for delete, are not modifiable./  < ------------------------------------------------------------* 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:u  < ------------------------------------------------------------< 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 commande@ 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/LOGt"   $ 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/DISABLE-  A Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) for informationaC on configuring the behaviour of OPCOM, including the (default) use  ? of the system console (OPA0:) as an operator terminial and the w@ specific contents and behaviour of the system operator log file 
 OPERATOR.LOG.a 						[Arne Vajhj]W 						[Stephen Hoffman]o  < ------------------------------------------------------------1 DCL5.   How do I generate a random number in DCL?h  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.E $ RAND:  $% $ IF F$TYPE(__SEED) .EQS. "" $ THEN- $     ! seed the random number generator, ...  $     __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) + --          (360000 * __HOUR)D $     ! the generator tends to do better with a large, odd seed, ... $     __SEED == (__SEED .OR. 1)p $     ! clean up, ...e $     DELETEX/SYMBOL __NOW $     DELETEX/SYMBOL __HOURe $     DELETEX/SYMBOL __MINUTEg $     DELETEX/SYMBOL __SECONDy $     DELETEX/SYMBOL __TICK  $ ENDIFs $o5 $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFFa $h $ __SEED == __SEED * 69069 + 1 $ 7 $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)e $d $ RETURN$ 					[sharris@sdsdmvax.fb3.noaa.gov]  < ------------------------------------------------------------% DCL6.   What does the MCR command do?e  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:p   	$ 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.e  < ------------------------------------------------------------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 DCL  prompt to the specified string.M  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.d  K If you wish to display the default directory for instance, you will have tooL 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 the-M SET DEFAULT and SET PROMPT for you.  These DCL command procedures often use at 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.)w  E There are related tools available from various sources, including thel following web sites:  $   o ftp://ftp.hhs.dk/pub/vms/setpmt/  -   o ftp://ftp.tmesis.com/sys_service_hook.srcr  A   o James F. Duff has also made available a Macro32 tool known asiH     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, andbI examples from Arne Vajhoej, Brian Schenkenberger, James Duff, and others.e   				[Stephen Hoffman]d  < ------------------------------------------------------------< 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	         $0@         $! 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, Compaqs	         $s         $ goto 'f$mode()'          $INTERACTIVE:1*         $ open/read/write chan 0::"task=x"         $ write chan "Hello"         $ read chan parametere         $ close chan$         $ write sys$output parameter         $ exit         $BATCH:w         $OTHER:i         $NETWORK:t&         $ open/read/write chan sys$net         $ read chan parameter -         $ write chan "''parameter' yourself!"          $ close chan         $ exit  -   An example of a run of the above procedure:D           $ @x         Hello yourself!Y	         $N    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 toSJ 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 ofSJ 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.)T 					[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?r  :   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,nC no matter what, there's really no substitute for RMS Journaling andzF host- or controller-based shadowing.  However, you can achieve a good H degree of data integrity by issuing a SYS$FLUSH RMS call at appropriate D times (if you're using RMS, that is.)  If you're using a high-level E language's I/O system, check that language's documentation to see if cG you can access the RMS control blocks for the open file.  In C you can :G use fflush followed by fsync.  Note that fsync, which was undocumented  E for VAX C but is documented for DEC C, takes a file descriptor as an   argument, not a *FILE.  I For details on disk bad block handling on MSCP and on SCSI disk devices,  - please see Ask The Wizard (ATW) topic (6926).i  < ------------------------------------------------------------C FILE4.  What are the limits on file specifications and directories?c  G A file specification has an aggregate maximum size of 255 characters at N 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 -nsK (n'th previous version) can be used in most contexts.  A file specificationLN may not have more than 8 directories and subdirectories - while it is possibleK to create subdirectories of greater depth, accessing them is problematic inm' most cases and this should be avoided.    G Application developers should use OpenVMS-supplied routines for parsingTI file specifications - this ensures that changes in what is allowable willsG not tend to break your application.  Consider that various parts of theaF file specification may contain quoted strings with embedded spaces andI other punctuation!  Some routines of interest are SYS$FILESCAN, SYS$PARSEoI and LIB$TRIM_FILESPEC.  For further information, see the OpenVMS Guide to  File Applications.  F Performance of larger directory files improves (greatly) with OpenVMS I V7.2 and later -- operations on directory files of 128 blocks and larger oF were rather slower on earlier OpenVMS releases due to the smaller sizeE of the directory cache and due to the directory I/O processing logic.r  F For fastest directory deletions, consider a reverse deletion -- deleteH from the last file in the directory to the first.  This reversal speeds G the deletion operation by avoiding unnecessary directory I/O operationscI as the files are deleted. Tools such as DFU can be used for this purpose,s? as can various available reverse-DELETE DCL command procedures.d  < ------------------------------------------------------------@ FILE5.  What is the largest disk volume size OpenVMS can access?  H One Terabyte (TB; 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 thesJ 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,n& though larger data disks are possible.  E Some SCSI disks with capacities larger than 8.58 gigabytes (GB) will eG require the use of an OpenVMS ECO kit (eg: ALPSCSI04_062 or later) for sF 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  J display the full capacity of the drive -- and  "%sysinit-e-error mounting E system device status equals 000008C4" (8C4 -> "%SYSTEM-?-FILESTRUCT, 0B unsupported file structure level") errors during bootstrap.  (One E workaround for the bootstrap when the bitmap is located far into the OD 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:C  %       OpenVMS Alpha V7.2-1, and latern%       V7.2 UPDATE V1.0 ECO, and latera'       V7.1-2 UPDATE V1.0 ECO, and latert'       V7.1-2 UPDATE V3.0 ECO, and laterN  <   o The newer DQDRIVER driver operates to disks up to 33 GB ?     without (known) problems, and effectively works with ratherdA     larger disks (up to circa 137 GB?) but is known to report an  ;     incorrect number of "cylinders" with disks above 33 GB.T  6   See ALPHA23 for additional IDE DQDRIVER information.  C Be aware that a known restriction in certain older versions of the (? Alpha SRM Console prevents booting most IDE drives larger than EC 8.455 GB, depending on exactly where the various files are located 'B 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 1 SRM console version.).  C NOTE: All IDE-related disk sizes listed in this section are stated ED in units of "disk (base ten) gigabytes" (1 GB = 10^9 bytes) and NOT G in units of "software (base two) gigabytes" (1 GB = 2^30 (1073741824.) 3 bytes.   See MISC21.:                                           [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 iD 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 cF cira 8.455 GB (base ten); 8GB (base two) require this ECO, or require ) the use of OpenVMS Alpha V7.1-2 or later.e   Also see VAX5, MISC21.  < ------------------------------------------------------------E FILE6.  What is the maximum file size, and the RMS record size limit?-  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 RMSED maximum file size limit is 2**31 * 512 bytes -- one terabyte (1 TB).  D "Use a volume set to provide a large, homogeneous public file space.G You must use a volume set to create files that are larger than a single F physical disk volume. (The file system attempts to balance the load onF the volume sets, for example, by creating new files on the volume that  is the least full at the time.)"  G "You can add volumes to an existing volume set at any time. The maximumi* number of volumes in a volume set is 255."  F The RMS formats -- sequential, relative, and indexed -- are limited byE the one terabyte maximum volume size.  RMS relative files are furtherfD 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.n   Also see PROG14, MISC21. 					[Stephen Hoffman]  < ------------------------------------------------------------= FILE7.  How do I write recordable CD media (CD-R) on OpenVMS?r  J At its simplest: get LDDRIVER from the Freeware.  Get CDRECORD or CDWRITE.J (CDRECORD and CDWRITE are freely available, though versions are not on theK Freeware V5.0 distribition; the URLs are referenced later in this section).3I Build the contents of the disk on the LD device partition.  Then use the nM CDRECORD or CDWRITE tool to record the contents of the LD partition directly s onto the CD-R or CD-RW media.  r  L While folks have had success getting PC-based CD-R/CD-RW tools to work with B OpenVMS partitions, it is far easier and more reliable to use the $ OpenVMS-based versions of the tools.  I More details: Creation of CD-ROMs using CD-Recordable media (CD-R) under  I OpenVMS typically involves one of two approaches: the use of the optional-C CD-R (`Scribe') capabilities available for the InfoServer or other  J "offline" hardware packages (PC-based packages will be included in this), I or the use of a host-based package such as the CDWRITE13_VMS utility, an   OpenVMS port of a Linux tool.c  E OpenVMS presently has no integrated support for recording CD-R media.u  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 thateC can be used to create CD-R media.  The contact for CDWRITE13_VMS is E Dr. Eberhard Heuser-Hofmann.  One website that discusses this packagen is located at:  A   http://www.geocities.com/SiliconValley/Lakes/9999/vmscdwri.html,  4 Also see the newest linux-cdwrite package, XCDROAST.  = Additional information is available via David J. Dachtera at:   &   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  t   http://www.tmesis.com/CDrom/     http://www.tditx.com/~odsiso/e  ;                                           [Stephen Hoffman]   B U.S. Design offers a package that includes the tools necessary to F create a CD or DVD-R with either 9660 or ODS-2 format, for standalone @ CD-R or DVD-R drives, for recent OpenVMS versions.  Details are 
 available at:e     http://www.usdesign.com/;                                            [Harry Garonzik]d    < ------------------------------------------------------------7 FILE8.  What I/O transfer size limits exist in OpenVMS?   G The maximum transfer size is an attribute of the particular I/O device, E controller and driver combination; there is no inherent limit imposednE by OpenVMS (other than the fact that, today, byte counts and LBNs arex 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 various?D 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 largely C historical.  Similarly, DSSI devices are limited to the same value,sD 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/O-D fragmentation processing happens on the client and not on the server system.h  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 andh the device can handle it.o   Also see FILE4, FILE5i  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  % commercial databases via the network.-  ? For RMS, consider acquiring one of the packages available from o> 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 setb them up explicitly.r 					[eric@tardis.HQ.ileaf.com]u  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 Manualm$ 	OpenVMS Programming Concepts Manual9 	OpenVMS Programming Interfaces: Calling a System RoutineE 	OpenVMS Calling Standarda  G In addition, if you are a subscriber to the Compaq Software InformationcJ 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:l   ftp://ftp.hhs.dk/pub/vms/e 					[Arne Vajhj]  B Additional information and examples for OpenVMS are available via:  '   http://www.openvms.compaq.com/wizard/i)   http://www.openvms.compaq.com/freeware/-   					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG2.  How do I get the arguments from the command line?p  G If you're writing a program and want to accept arguments from a foreign F 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.   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.r  I It is possible to write an application which can be used both ways; if a  L 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 t@ 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?a  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 action-K routine returns a "false" (low bit clear) function value so that SYS$PUTMSGfI doesn't then try to display the message (unless you want it to.)  See the E description of $PUTMSG in the System Services Reference Manual for ane# 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.n  G Also see PROG11, particularly for pointers to the details on shareable -$ 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.gB 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 defaultg
 directory! 					[Arne Vajhj]	d  < ------------------------------------------------------------M PROG6.  How do I create a shareable image transfer vector on an Alpha system?t  K This is something that was greatly simplified for OpenVMS Alpha.  You don'toL need to create a separate transfer vector module; just use the SYMBOL_VECTORI statement in a linker options file.  For example, if your shareable imageaJ has two routines named FOO and BAR, the linker options file should contain the following line:o  - 	SYMBOL_VECTOR=(FOO=PROCEDURE, BAR=PROCEDURE)n  + The Linker manual has more details on this.i  < ------------------------------------------------------------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.  OnpG OpenVMS VAX all OVR/REL/GBL psects were automatically exported into thehM shareable image's Global Symbol Table.  On OpenVMS Alpha you have to tell theaC linker that you want this done by means of the PSECT keyword in theg% SYMBOL_VECTOR options file statement.   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.o  K By default, COMMON PSECTs in DEC Fortran for OpenVMS Alpha (as well as mostnL 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 COMMONiG 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 eK options file PSECT_ATTR statement to set the COMMON PSECT attribute to SHR.i  / For further information, see the Linker manual.s  < ------------------------------------------------------------< 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 sG in the LIB$ Run-Time Library Reference Manual, and can perform floatingrG point conversions between any two of the following floating datatypes: dJ VAX (F,D,G,H), little-endian IEEE (single, double, quad), big-endian IEEE 5 (single, double, quad), CRAY and IBM System\370, etc.   F DEC Fortran (all platforms) has a feature which will perform automaticK conversion of unformatted data during input or output.  See the DEC FortraniA documentation for information on "non-native data in I/O" and thei  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.zipt    < ------------------------------------------------------------= PROG9.  How do I get the argument count in a Fortran routine?c  E On VAX, many programmers would use a MACRO routine which accessed therE AP register of the caller to get the address of the argument list andiF 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.g  G Note that omitting arguments to Fortran routines is non-standard and isoG unsupported.  It will work in many cases - read the DEC Fortran releasea! notes for additional information.B  < ------------------------------------------------------------? PROG10. How do I get a unique system ID for licensing purposes?e  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 nD for this purpose.  Compaq does not use hardware IDs in its licensingG methods and many users consider a hardware-based licensing scheme to beM9 a negative attribute when considering software purchases.c  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.  s@ 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/u  < ------------------------------------------------------------? PROG11. What is an executable, shareable, system or UWSS image?f  A    Executable code in OpenVMS typically resides in an image -- an5B    image is a file -- the file extension is typically .EXE -- thatA    contains this code.  Common types of images include executable1@    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 INSTALL @       of the image with /PRIVILEGE, or can grant enhanced accessA       with the specification of a subsystem identifier on the ACLs        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 enhanced ?        privileges, even with the use of INSTALL with /PRIVILEGE @        or a subsystem identifier.  These shareable images can beA        dynamically activated (a LINK that occurs at run-time) viab@        the LIB$FIND_IMAGE_SYMBOL run-time library (RTL) routine.=        (See `protected images' for information on `privilegedt        shareable images'.)  A    System images are intended to run directly on the VAX or Alphao>        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 ineA        some ways to a standard shareable images, but these imagessA        include a `change mode' handler, and execute in an `inner'eA        processor mode (privileged mode; executive or kernel), and,C        code executing in inner modes has implicit SETPRV privilege. B        Must be INSTALLed with /PROTECT.  Note that inner-mode code?        has restrictions around calling library routines, aroundG?        calling various system services, and around calling codes6        located in other protected or shareable images.  A    Loadable images and device drivers are images that can be used->    to add code into the OpenVMS kernel.  Pseudo-device driversA    are a particularly convenient way to add executable code, withm>    associated driver-defined data structures, into the kernel.E    The pseudo-device driver includes the UCB and DDB data structures, ?    and a calling interface with support for both privileged ando?    unprivileged access to the driver code via sys$qio[w] calls.i  >    A cookbook approach to creating OpenVMS shareable images is1    available at the (admittedly overly long) URL:e  *      http://www.openvms.compaq.com/wizard/   					[Stephen Hoffman]  < ------------------------------------------------------------/ PROG12. How do I do a file copy from a program?u  M There are several options available for copying files from within a program. xD Obvious choices include using lib$spawn(), system(), sys$sndjbc() orM sys$creprc() to invoke a DCL COPY command.  Other common alternatives include J using the callable convert routines and the BACKUP application programming interface (V7.1 and later).M   					[Stephen Hoffman]  < ------------------------------------------------------------ PROG13.  What is a descriptor?  K A descriptor is a data structure that describes a string or an array.  EachFI descriptor contains information that describes the type of the data beingbG referenced, the size of the data, and the address of the data.  It alsoaI includes a description of the storage used for the data, typically statich2 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}l     int RetStat;     char TxtBuf[TXTSIZ]n%     struct dsc$descriptor StaticDsc =p0       { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL };#     struct dsc$descriptor DynDsc = '0       { 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 */e)     StaticDsc.dsc$w_length      = TXTSIZ;o2     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;   %     /* release the dynamic storage */t'     RetStat = lib$sfree1_dd( &DynDsc );s(     if (!$VMS_STATUS_SUCCESS( RetStat ))       return RetStat;   G Static descriptors reference storage entirely under application program.J control, and the contents of the descriptor data structure can be modifiedE as required (by the application).  OpenVMS routines do not modify thewH contents of a static descriptor, nor do they alter the address or lengthI values stored in the static descriptor.  (The term "static" refers to thelH descriptor data structure, and not necessarily to the storage referenced by the descriptor.)s  G Dynamic descriptors reference storage under the control of the run-time/H library, and the contents of a dynamic descriptor data structure -- onceE initialized -- can only be modified under control of run-time librarysF routines.  The dynamic storage referenced by the dynamic descriptor isC allocated and maintained by the run-time library routines.  VariousrH 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]  I Also note that the lib$spawn and the C system call will fail in a CAPTIVEtD login environment.  The lib$spawn call can be gotten to work in this9 environment with the specification of the TRUSTED flag.  g  < ------------------------------------------------------------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:e  $   LIBRARY 'SYS$LIBRARY:STARLET.L32';  ? or similar requires the presence of the Bliss libraries.  These B 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 --         SYS$LIBRARY:STARLET.REQ   E   LIB.L32 contains both the public and private interfaces to OpenVMS:m  1     $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 -P3         SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQu  4   The equivilent files for Bliss64 are created with:  5     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]LIB.L64 - 3         SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64 9     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]STARLET.L64 -u         SYS$LIBRARY:STARLET.R64a  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, andl<   ! contains the architectural definitions for conditionally;   ! compiling OpenVMS Bliss sources for use on VAX systems.-   !-   MACRO VAXPAGE = 1%;    MACRO BIGPAGE = 0%;u  =   MACRO VAX =                     ! = 1 if compiled BLISS/VAXeA           %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAXh  <   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. G   !       %BLISS(BLISS32E) OR %BLISS(BLISS64E)%; ! = 0 if compiled /VAX 8           NOT %BLISS(BLISS32V)%;  ! = 0 if compiled /VAX     MACRO ADDRESSBITS = E           %BPADDR%;               ! = 32 or 64 based on compiler usedT       					[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 thep'   contents of a log file, for instance.a  8   A C source example that demonstrates how to do this is9   available in topic (2867) in the OpenVMS Ask The Wizard-   area:   )     http://www.openvms.compaq.com/wizard/W  ;   Depending on the environment, you may need to use C callsn;   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 theiC   MESSAGE/SDL tool (latent in OpenVMS) to create an SDL file based iD   on the messages.  Then use the SDL tool (available on the OpenVMS G   Freeware) to convert the SDL file into language-specific definitions.nE   (There is also a converter around to convert SDL into SDML, if you  F   want to get pictures of the data structures for your documentation.)  < ------------------------------------------------------------C PROG21. How do I activate the OpenVMS Debugger from an application?    #include <lib$routines.h>i #include <ssdef.h> #include <string.h>b   main()     { #     char ascic_debug_commands[128];r)     char *dbgcmd = "*show calls;go;exit";   +     strcpy( ascic_debug_commands, dbgcmd ); :     ascic_debug_commands[0] = (char) strlen( dbgcmd ) - 1;  1     lib$signal(SS$_DEBUG,1,ascic_debug_commands);v  
     return 1;S     }s  < ------------------------------------------------------------# PROG22.   Dealing with Endian-ness?t  G   OpenVMS on VAX, OpenVMS on Alpha and OpenVMS on Intel IA-64 platformsiF   (as well as all Microsoft Windows implementations and platforms) allE   support and all use the little-endian byte ordering.  Certain Alpha H   microprocessors and Certain Intel Itanium processors can be configured    to operate in big-endian mode.  E   With little-endian byte order, the least significant byte is alwaysrB   the first byte; the byte at the lowest address.  With big-endianF   byte ordering, the byte storage order in memory is dependent on the C   size of the data (byte, word, longword) that is being referenced.   F   Endian-ness is a problem has been solved many times before.  Some ofB   the typical solutions include htonl/htons and ntohl/ntohs in the?   standard C library and the TCP/IP Services XDR (eXternal DataaI   Representation) libraries.  One of the more recently introduced networkeI   formats, and one that is seeing extensive press and marketing coverage,h	   is XML.g    < ------------------------------------------------------------0 PROG23.   How to resolve LINK-I-DATMISCH errors?  F   The message LINK-I-DATMISCH is informational, and indicates that theH   version of the specified shareable image found in the system shareableH   image directory does not match the version of the shareable image thatG   was originally loaded into IMAGELIB.OLB, one of the OpenVMS librariesb#   typically searched by the LINKER.C  H   From a privileged username, you can usually completely repair this via   the following DCL command:  C   $ LIB/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:LIBRTL.EXEa  E   This command assumes that the shareable image that was found in the3E   SYS$SHARE: area is valid and upward-compatiable, and that the imageiF   has simply replaced an older version without also updating IMAGELIB.     [End of Part 3/5]e    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 02 Oct 2001 21:35:22 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/5i1 Message-ID: <uqqu7.960$YP.25635@news.cpqcorp.net>c   Archive-name: dec-faq/vms/part4. Posting-Frequency: quarterly Last-modified: 2 Oct 2001h Version: VMS-FAQ-4.TXT(7)h    9 This is the OpenVMS Frequently Asked Questions Part 4/5.  @ 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 utilityg@ 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 ong that workstation. <                                              [Mike Raspuzzi]  M > Yah, but this doesn't seem to work with non-VMS systems.  What do I put in eI > for the transport?  I tried "TCPIP" just for kicks, but it didn't work.R  &         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:                csh:* 	      # setenv DISPLAY myvax.domain:0.0               sh and ksh:a9               $ DISPLAY=myvax.domain:0.0 ; export DISPLAYp  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 the               node name!   @           c) If the connection is TCPIP, "Username" _must_ be an@              asterisk (*) because the  TCP/IP protocol used does-              not provide the remote username.   @           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.h  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 -l(             $_    DECW$SERVER_TRANSPORTS  '          You sould find something like:o  9 	    $ decw$server_transports == "DECNET,LOCAL,LAT,TCPIP"   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]t  K There is a log file created in SYS$MANAGER which tells you which transportseL 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 Managerc Security entries.  				    [rabinowitz@bear.com]s  < ------------------------------------------------------------9 DECW2.  How do I create a display on another workstation?-  @ $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node  ) for LAT the command might look like this:u  6 $ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=REMOTE_NODE   for DECnet:i  2 $ SET DISPLAY /CREATE /TRANSPORT=DECNET /NODE=NODE  
 for TCP/IP  9 $ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=128.12.4.122n  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 X K server to allow the LAT transport - check the docs).  LAT will be supportedaD on OpenVMS VAX as a transport for DECwindows in a future OpenVMS VAX release. 					[Mike Raspuzzi]  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 beeI very useful for tracking down what needs to be put in the Session Managers Security entries.e=                                         [rabinowitz@bear.com]   < ------------------------------------------------------------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/ore DECW$DISPLAY_TRANSPORT.l" 					[Fairfield@Slac.Stanford.Edu]  E An example of calling the underlying (and also undocumented) sys$qio p? programming interface for the WSDRIVER (WSAn:) is available at:u  I   http://www.openvms.compaq.com/freeware/srh_examples/DECUS_UNDOC_CLINIC/n  < ------------------------------------------------------------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.c  M It should be noted that ALL the characters and escape sequences are captured,tO but if you display the log file on a DECterm you will get EXACTLY what you had.- 					[Yaacov Fenster]o  < ------------------------------------------------------------E DECW5.  Problem - the DELETE key deletes forward instead of backward!T  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.d      *defaultVirtualBindings:\   osfCancel	:		<Key>F11	\n\  osfLeft	:		<Key>Left	\n\r  osfUp		:		<Key>Up		\n\e  osfRight	:		<Key>Right	\n\l  osfDown	:		<Key>Down	\n\c   osfEndLine	:Alt		<Key>Right	\n\!  osfBeginLine	:Alt		<Key>Left	\n\t  osfPageUp	:		<Key>Prior	\n\  osfPageDown	:		<Key>Next	\n\ "  osfDelete	:Shift		<Key>Delete	\n\  osfUndo	:Alt		<Key>Delete	\n\   osfBackSpace	:		<Key>Delete	\n\   osfAddMode	:Shift		<Key>F8		\n\  osfHelp	:		<Key>Help	\n\$  osfMenu	:		<Key>F4		\n\  osfMenuBar	:		<Key>F10	\n\h  osfSelect	:		<Key>Select	\n\b!  osfActivate	:		<Key>KP_Enter	\n\,!  osfCopy	:Shift		<Key>DRemove	\n\   osfCut		:		<Key>DRemove	\n\  osfPaste	:		<Key>Insert  	 To merge:b    	$ xrdb :== $decw$utils:xrdb.exe( 	$ xrdb -nocpp -merge decw$xdefaults.dat 					[Fred Kleinsorge]  < ------------------------------------------------------------- DECW6.  Why is DECwindows Motif not starting?n  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 youf 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 lI    not have a Compaq QVision video card.  This EISA graphics card should cF    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.)   C c) You have a PCI-based system and do not have a supported graphicse>    controller -- examples of supported controllers include the        PowerStorm 3D30      PowerStorm 4D20      PowerStorm 300       PowerStorm 350e      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 disabledy(    the device autoconfiguration process.  ) If there is a G* graphics device present:   I a) There may have been a severe error in the DECwindows startup. Type theBI    contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any information on     errors starting the server.  I b) The system parameter WINDOW_SYSTEM is not set to 1.  This is a common SD    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 c    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.n  B d) Check that the DECW$PRIVATE_SERVER_SETUP.COM is correct for the-    graphics controller in use.  For instance:   =      From the 9FX Vision 330 Owners Guide, EK-V330G-OG pg 2-9I  E      Place the following in DECW$PRIVATE_SERVER_SETUP.COM (copy from  G      .TEMPLATE, if needed).  Have the file in SYS$SPECIFIC:[SYSMGR] or d*      in SYS$COMMON:[SYSMGR] as apropriate.  )        $ DECW$XSIZE_IN_PIXELS == <xvalue>3)        $ DECW$YSIZE_IN_PIXELS == <yvalue>O<        $ DEFINE/SYSTEM DECW$SERVER_REFRESH_RATE <rate in Hz>   Also see DECW14  					[Kleinsorge, Hoffman]  < ------------------------------------------------------------ DECW7 relocate to SUPP7T  < ------------------------------------------------------------ DECW8 relocated to SUPP8  < ------------------------------------------------------------3 DECW9.  How do I set the title on a DECterm window?   0 If you are creating a new DECterm window, check ) HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES.i  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")-8 $  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.i   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  M FileView defaults, session manager defaults, the DECwindows login processing,eL DECwindows log file processing, and various other DECwindows attributes, see the example file:1  .   SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE  C This example template file is typically copied over to the filenameeM SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_APPS_SETUP.COM and then modified to meet* site-specific requirements."  M Additionally, various X tools such as xsetroot, bitmap and xrdb -- some these G can be useful in customizing the appearance of an application or of themA 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  G is the Common Desktop Environment (CDE).  You can select your prefered lI desktop (CDE or DECwindows Motif) when logging in, or you can change the  = default to the DECwindows Motif desktop using the DCL symbol rK decw$start_new_desktop in the DECwindows private application setup command aI procedure.  See SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE for further i7 details, and how to create DECW$PRIVATE_APPS_SETUP.COM.o  G Note that with DECwindows CDE, the root window is no longer visible by mH 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 nE style manager selection "backdrop none", and use information such as n/ that in the OpenVMS FAQ to set the root window.e  E To add a new backdrop to the DECwindows CDE environment, the backdropfJ 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 xviE default filename extension for the X11 pixmap file is .XPM, while CDE F 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.p  e 					[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.f  I On OpenVMS, the platform-specific arguments to this call include an event-I flag and an IOSB, as these are the traditional OpenVMS constructs used tooI synchronize the completion of asynchronous operations.  While it would beeD 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 extremelypA difficult to use OpenVMS features such as ASTs and sys$qio calls.o  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_efeG calls to allocate and deallocate event flags, you must first explicitlyuH 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 callscJ 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(n         m->AppCtx,         m->InputEF,          m->InputIosb,d         the_callback, 1 );     if ( !((int) m->InputID ))	         {          XtAppErrorMsg(             m->AppCtx,             "invalidDevice",             "XtAppAddInput",             "XtToolkitError", "             "Can't Access Device",             (String *) NULL,              (Cardinal *) NULL );         ...a 					[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]e  < ------------------------------------------------------------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], P8 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.r  > On older releases, you can disable output using the following:  *   SET TERMINAL/PERMANENT/NOBROADCAST OPA0:   DEFINE/USER SYS$COMMAND OPA0:    REPLY/DISABLEa  * 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:   :  %DECW-W-NODEVICE, No graphics device found on this systemA    -DECW-I-NODECW, DECwindows graphics drivers will not be loaded     > 1) Ensure that the SYSGEN parameter WINDOW_SYSTEM is set to 1:  #     $ MCR SYSGEN SHOW WINDOW_SYSTEM(  8    If it is not set to a value of 1, issue the commands:       $ MCR SYSGEN     SYSGEN> USE CURRENTl     SYSGEN> SET WINDOW_SYSTEM 1i     SYSGEN> WRITE ACTIVE     SYSGEN> WRITE CURRENTe     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:        $ MCR SYSMAN     SYSMAN> IO SHOW PREFIXK     SYSMAN> IO SET PREFIX=(DECW$,*)   * = list returned by the show commandr     SYSMAN> IO AUTO/LOGh     SYSMAN> EXITH 3) Ensure that the image SYS$SHARE:DECW$ICBM.EXE is installed in memory.+    If it is not installed, then install it:   +     $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBME  )     $ INSTALL REPLACE SYS$SHARE:DECW$ICBMN  #     $ EDIT SYS$MANAGER:SYCONFIG.COMh  0       $! The following line was added to install-       $! support for the Mach64 Graphics Cardr       $!+       $ INSTALL REPLACE SYS$SHARE:DECW$ICBMy
       $ ^Z       $ SHUTDOWN    REBOOT the system.   E If the system still complains that NO GRAPHICS DEVICES COULD BE FOUNDr then:     4)   o Boot the system as normal      o Login as "system"      o Create the file: =          $ SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT (W:RE)d7      o Add the following string on the very first line:            CLEAR_PFLAG = ISA_4BYTE      o Save the file      o Set the file protections       o Reboot the system  
      EXAMPLE:M  9      $ create SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DATT        CLEAR_PFLAG = ISA_4BYTE	        ^Z   M      $ SET FILE/PROTECTION=(W:RE) SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT	
      $ REBOOTd   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 thesG   DECwindows keyboard driver SYS$IKBDRIVER.EXE in OpenVMS Alpha V7.1-2 oI   and V7.2-1 and with the SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1  G   and later, the DECwindows CDE controls will now correctly manage the h&   setting of the warning bell volume.   G   Unfortunately, the equivalent controls in the older DECwindows Motif -D   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:u  #     $ @decw$utils:decw$define_utilsT     $ 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, oI   the X Windows Server and the keyboard driver interface did not support  A   the pitch and duration, and neither did DECwindows Motif.  The  G   DECwindows keyboard driver was accordingly changed to use the volume eE   from the keyclick setting (keyclick is not available in a PC-style XJ   keyboard) and the bell volume setting to control the pitch and duration.  E   DECwindows CDE does provide sliders for setting pitch and duration,cG   so the keyboard driver and X Windows Server were modified to provide eI   all of the information, and now the DECwindows CDE sliders work.  This hF   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.s  < ------------------------------------------------------------4 DECW16. How can I alter the DECwindows CDE backdrop?  C To select a separate backdrop to be displayed on each screen using n DECwindows CDE:s  # 1. Click on the Appliction Manager. .    This is the drawer icon on the CDE toolbar. 2. Click on Desktop ToolsC= 3. Click on Set Default Screen and select the required screeni 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.R  >                                              [Geoff Kingsmill]  < ------------------------------------------------------------8 DECW17. How can I enable the DECwindows TCP/IP Transport  E   To configure the TCP/IP transport for DECwindows, first ensure thatyH   a TCP/IP package is installed and configured.  Then set the DCL symbolE   DECW$SERVER_TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COMlE   to the appropriate local value, based on the comments in that file.   I   If you do not have a copy of SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM,dE   the use the following COPY command to create this file based on theh   provided template file:F  9     COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE --9          SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COMd    < ------------------------------------------------------------ MISC1 relocated to WIRES1t  < ------------------------------------------------------------G MISC2.    Where can I find information on escape and control sequences?   G Information on escape and control sequences can be found in the OpenVMSxC I/O User's Reference Manual, in the section on the terminal driver.lB This section includes details on the general format and content of these sequences.  C Specific details on the escape and control sequences supported by a	A particular serial device are typically found in the documentation A provided with the specific device.  Information on the sequences oF supported by DECwindows DECterm terminal emulator are included in the  DECwindows documentation.o  G Examples of common escape and control sequences -- those typically used:H 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 dH replaced by the sequence "{ESC}[" (without the quotes) particularly for E seven-bit operations, SS3 is decimal code 143 and can be replaced by -C "{ESC}O" particularly for seven-bit operations.  Older VT1xx seriessF terminals and any other terminals operating with seven-bit characters ? should not be sent eight-bit operators such as {CSI} and {SS3}.n  + PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}SoA 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}mnI KPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}DtH 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~Q@ 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~i  = An example of working with escape sequences (in DCL) follows:u   $ esc5m = "*[5m" $ esc5m[0,8] = 27d $ esc0m = "*[0m" $ esc0m[0,8] = 27I2 $ 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/e  @ Information on the ReGIS graphics character set is available at:  <   http://www.cs.utk.edu/~shuford/terminal/dec_regis_news.txt   Also:e  -   http://www.boundless.com/Text_Terminals/VT/    Also see DECW9, DCL12.  < ------------------------------------------------------------ MISC3 relocated to SUPP4  < ------------------------------------------------------------ MISC4 relocated to WIRES2e  < ------------------------------------------------------------ MISC5 relocated to ALPHA5w  < ------------------------------------------------------------E MISC6.    What does "failure on back translate address request" mean?n   The error message:  <   BCKTRNSFAIL, failure on the back translate address request  I indicates that the destination node is running DECnet-Plus, and that its OE naming service (DECnet-Plus DECdns, LOCAL node database, etc) cannot eE locate a name to associate with the source node's address.  In other FG words, the destination node cannot determine the node name for the noder. 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.)C Also check to make sure that the node is entered into its own LOCALYC namespace.  This can be a problem elsewhere, however.  Very rarely, D 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.e/   o DNS/Bind: the IP distributed name services.n   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 displays F   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 Alpha7B   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 powerupcD   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 used "   to display the hardware address:     >>> SHOW DEVICEl   >>> 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:s     >>> E/P/W/N:5 20001920  G   Look at the low byte of the six words displayed by the above command.1E   (The oldest VAX Q-bus systems -- such as the KA630 processor modulelD   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.)   F   If the system is a VAX system, and another VAX system on the networkC   is configured to answer Maintenance and Operations Protocol (MOP)CF   bootstrap requests (via DECnet Phase IV, DECnet-Plus, or LANCP), the1   MOM$SYSTEM:READ_ADDR.EXE tool can be requested:y     >>> B/R5:100 ddcu    Bootfile: READ_ADDRf  I   Where ddcu is the name of the Ethernet controller in the above command.eJ   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,_I   and (if the download is successful) READ_ADDR will display the hardwareS
   address.  G   If the system is running, you can use DECnet or TCP/IP to display the 6   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 latere  G   A program can be created to display the hardware address, reading the F   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:t  =     http://www.openvms.compaq.com/wizard/swdev/ethernVMS.htmli  E   To use the DECnet Phase IV configurator tool to watch for MOP SYSIDi%   activity on the local area network:   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.txt-C   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED   E   The resulting file (named filename.txt) can now be searched for theoG   information of interest.  Most DECnet systems will generate MOP SYSIDfH   messages identifying items such as the controller hardware address andE   the controller type, and these messages are generated and multicastA   roughly every ten minutes.  E   Information on the DECnet MOP SYSID messages and other parts of thedF   maintenance protocols is included in the DECnet network architecture,   specifications referenced in section DOC9.  < ------------------------------------------------------------ MISC8 combined into SUPP3   < ------------------------------------------------------------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 sE   Microsoft Windows NT option to disable authentication during a RAS sG   connection apparently doesn't currently work -- RAS connections will bG   require authentication -- and this will thus prevent RAS connections.o@                                                [Stephen Hoffman]  < ------------------------------------------------------------ MISC10 relocated to SUPP5i  < ------------------------------------------------------------@ MISC12.   Does DECprint (DCPS) work with the LRA0 parallel port?  = The parallel printing port LRA0: found on many OpenVMS Alpha d= systems is capable of some bidirectional communications, withI8 enough for basic operations with most parallel printers.  ? DECprint (DCPS) requires more than just the simple handshaking p> provided by the LRA0: port, therefore DCPS does not work with  the LRA0: port.T4                                      [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.n  ? Tape media is different than disk media, as disks have a known r= and pre-determined fixed capacity.  Modern disks also appear  > logically perfect, based on bad block revectoring support and ; the extra blocks hidden within the disk structure for theser 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 t= the tape, the numbers of correctable and uncorrectable media  C errors that might occur, the numbers and sizes of the inter-record  > 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 approximatelyP@ 15% overhead, in terms of saveset size.  (eg: Assuming a 500 KB ' input, the total size would be 575 KB.)A     Assuming no compression:0    4 GB media / 575 KB saveset =  7294 savesets      Assuming 1:2 compression: 0    8 GB media / 575 KB saveset = 14588 savesets   C NB: There are no inter-record gaps on DAT tapes.  (When determininguB media capacity, you have to consider these with nine-track magtapeE media.  Not with DAT (DDS).  However, the block structure underneath CG the variable length record recording is based on a block size of circa EF 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.S  E The compression algorithms used on various devices are generally not NF 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. F  C A typical compression ratio found with "everyday" data is somewhere  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.oG                                           [Hoffman, Froehlin, Williams]I  < ------------------------------------------------------------* MISC14.   So what happened to sys$cmsuper?  ! There is no SYS$CMSUPR service.     A The typical wisdom for getting into supervisor access mode (from LA user mode) is to execute a routine in executive mode (via a call B> 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.R:                                     [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 such ) as TAP (Telocator Alphanumeric Protocol).]  C RamPage (Ergonomic Solutions) is one of the available packages that5A can generate and transmit messages to radio pagers.  Target Alert = (Target Systems; formerly the DECalert product) is another.  o? Networking Dynamics Corp has a product called Pager Plus.  The 2B System Watchdog package can also send pages.  The Process SoftwareE package PMDF can route specific email addresses to a paging service,   as well.  @ Many commercial paging services provide email contact addresses @ for their paging customers -- you can simply send email directly
 to the pager.o  E Some people implement the sending of pages to radio pagers by sendingoD commands to a modem to take the "phone" off the "hook", and then theC paging sequence, followed by a delay, and then the same number that A a human would dial to send a numeric page.  (This is not entirely ? reliable, as the modem lacks "call progress detection", and thebE program could simply send the dial sequence when not really connectedn: to the paging company's telephone-based dial-up receiver.)  ? See SOFT1 for information on the available catalog of products.c  < ------------------------------------------------------------ MISC16 relocated to WIRES3  < ------------------------------------------------------------< MISC17.   How do I reset the LAN (DECnet-Plus NCL) counters?   On recent OpenVMS releases:   ;   LANCP> SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devnamep    < ------------------------------------------------------------6 MISC18.   What are the prefixes for the powers of ten?  $         Power   Prefix  Abbreviation         10^-18  atto    au         10^-15  femto   ft         10^-12  pico    pe         10^-09  nano    nu         10^-06  micro   -         10^-03  milli   m-         10^-02  centi   c6         10^-01  deci    dn         10^+01  deca    da         10^+02  hecto   hb         10^+03  kilo    ku         10^+06  mega    M          10^+09  giga    GM         10^+12  tera    Ta         10^+15  peta    P.         10^+18  exa     EC    < ------------------------------------------------------------6 MISC19.   OpenVMS Cluster (SCS) over DECnet?  Over IP?  = The OpenVMS Cluster environment operates over various networkk6 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.E  & 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 tB 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, sD 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.)f  @ The usual approach for multi-site OpenVMS Cluster configurationsG involves FDDI, Memory Channel (MC2), or a point-to-point remote bridge,MD brouter, or switch.  The connection must be transparent, and it mustC operate at 10 megabits per second or better (Ethernet speed), with c> 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 seteC   of PAKs registered across all licensing databases present in the e   OpenVMS Cluster.  A   If your software license permits it, you can use the following E(   two commands to transfer license PAKs:       $ LICENSE COPY... 5     $ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,...}  A   To display the particular license(s) required (such as when youn=   receive a NOLICENSE error), use the following DCL sequence:        $ SET PROCESS/PRIVILEGE=ALLa     $ REPLY/ENABLE7     $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGEo  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 SH   various products can check for and can be enabled by multiple license ?   PAKs.  You will want to deassign this logical name when done.9  '   Some of the more common license PAKs:1  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*u9   OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USER    OpenVMS VAX:       VAX-VMS#   OpenVMS Galaxy:    OPENVMS-GALAXYc-   Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP*e-   Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*:  E   Various NET-APP-SUP (NAS) license packages are available, each withoD   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 MISC21.   Third-party disk/tape/controllers/SCSI/widgets on OpenVMS?  I   A wide variety of third-party widgets -- SCSI and IDE disks and tapes, eC   graphics controllers, etc -- are available for various platforms.a  E   If you purchase third-party "generic" SCSI or IDE storage devices, aE   you and your device vendor will be responsible for the testing and dG   the support of the devices.  I would tend to expect that Compaq will tD   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 eF   manufacturer are responsible for finding and fixing problems in the ;   particular third-party device and or controller involved.c  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. E  B   On older OpenVMS releases, see the disk capacity limits (FILE5).  F   With SCSI disks on releases prior to V6.2, ensure that you have the D   ARRE and ARWE settings configured correctly (disabled).  (If not, @   you will see DRVERR fatal drive errors and error log entries.)  C   Some SCSI disks set the medium type byte as part of the SCSI sizeaA   field -- this is a SET CAPACITY extension to SCSI specs.  This  -   problem also applies to VAX V7.1 and later.a  F   Disks with SCSI disk sizes past 8.58 GB and/or with the SET CAPACITYA   extension require ALPSCSI07 ECO or the OpenVMS Alpha V7.1-2 or s2   later release.  (See FILE5 for further details.)  E   Based on the displays of the (undocumented) SYS$ETC:SCSI_INFO tool;t1   this tool is present in OpenVMS V6.2 and later:n  E     Issuing 6-byte MODE SENSE QIOW to get current values for page 01hu*            Page Code ................. 01h@            Page Name ................. Read-Write Error Recovery*            Saveable .................. Yes)            Size ...................... 10p>            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 is E     not acceptable on OpenVMS versions prior to V6.2.  Further along o.     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 ...................... 10 >            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 changedeC     on this particular SCSI device.  (This is not always the case.)cE     Use RZDISK from the OpenVMS Freeware, and reset the E6 flag byte tE     to hexadecimal 26 (or whatever the remaining mask when you removeY     bits C0) on page one.   B   Each SCSI and IDE host contains non-trivial SCSI and IDE driver E   software, and each device contains equally non-trivial firmware --  E   taken together with the mechanical and electronic components, this lB   software and firmware will determine whether or not a particular#   device will function as expected.i  E   Also note that various devices -- such as various SCSI CD-R deviceseH   -- can implement and can require vendor-specific protocol extensions, C   and these extensions can require modifications to OpenVMS or the KB   addition of various utilities.  In various of these cases, theseE   devices perform functions that will require them to use SCSI or IDEEF   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,eG   integration and testing work is mandated.  There can be no certainty aH   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.a  B   The same general statement holds for OpenVMS bootstrapping on anA   unsupported VAX or Alpha platform.  It might or might not work.uE   In particular, please see the OpenVMS Software Product Description FD   (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, rD   on the Multia, and on a variety of other platforms.  (You might orC   might not see success booting OpenVMS on any of these platforms.)l 					[Stephen Hoffman]  < ------------------------------------------------------------: MISC22.   How do I convert?  Disk Blocks?  KB, MB, GB, TB?  B The granularity of disk storage allocation is called a disk block.C Groups of disk blocks are organized together into the smallest unit-@ of storage that can be allocated, and this unit is called a diskB cluster.  The number of blocks in a cluster is the cluster factor,7 and is established when the disk volume is initialized.n  C Each individual disk block is composed of five hundred twelve (512)tC bytes, or one-half kilobyte.  Each byte is comprised of eight bits.aD A bit represents the smallest unit of information, typically refered to as a one or a zero.  D OpenVMS tends to uses base two notation for disk storage, while diskD storage capacity specifications from most storage vendors (including- Compaq) will generally use base ten notation.-  E An OpenVMS disk block is 512 bytes in size; this is one-half kilobyte- in base two notation.-  C The following table describes the prefix, the abbreviation, and thea> associated base ten (marketing) and base two (OpenVMS) values.  4             Base Ten                        Base TwoB             -----------------------------   ----------------------B   Kilobyte  (KB)  10**3              1000   2**10             1024B   Megabyte  (MB)  10**6           1000000   2**20          1048576B   Gigabyte  (GB)  10**9        1000000000   2**30       1073741824B   Terabyte  (TB)  10**12    1000000000000   2**40    1099511627776B   Petabyte  (PB)  10**15 1000000000000000   2**50 1125899906842624    F The base ten representation of the 2**40 value is 1099511627776, whichF is obviously rather ugly.  When viewed as a base eight or base sixteenC (octal or hexadecimal, respectively) value, the value is far nicer.pD Specifically, the value is 10000000000 and 40000000 when represented' in octal and hexadecimal, respectively.   H Notational note: Within the OpenVMS FAQ, a Kilobit is represented by the7 appreviation Kb, while a Kilobyte is represented as KB.v  H To convert OpenVMS disk blocks to (base two) kilobytes (KB; 1024 bytes),H simply divide by two.  To convert blocks to (base two) megabytes, divideH by 2048.  Blocks to (base two) gigabytes (GB), divide by 2097152.  TheseE particular divisions can also be performed using bitshifts: to dividefF a value by two, shift the binary value rightwards by one bit position.  A To convert OpenVMS disk blocks to (base ten) kilobytes, divide bys approximately 1.953125.r  B And for those rummaging around deep in SYSGEN, a microfortnight is approximately one second.   < ------------------------------------------------------------C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?e  A Details on many commercial OpenVMS products are available in the a catalog located at:u  &   http://www.compaq.com/csa/directory/     ----  C An OpenVMS Freeware CD-ROM is distributed with OpenVMS, and is also2A available separately (QA-6KZAA-H8).  The contents of the OpenVMS B3 Freeware CD-ROM media are also available online at:r  /         http://www.openvms.compaq.com/freeware/          ftp://ftp.montagar.com/e'         ftp://mvb.saic.com/freewarev40/i  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/n  E To acquire the OpenVMS Freeware CD-ROM distribution, you can order anoC OpenVMS distribution from Compaq (the Freeware is included)(see theuH OpenVMS SPD for part numbers), or you can specifically order a Freeware + distribution from Compaq under part number:l  
   QA-6KZAA-H8   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-requestedrG OpenVMS tools on the Freeware CD include ZIP and UNZIP and GZIP (please G see SOFT14), MMK (make), PINE, PERL, TAR, UUENCODE and UUDECODE.  Many -* other tools are available on the Freeware.  K The UUENCODE and UUDECODE tools and various other tools are also available RC as part of TCP/IP Services package.  (Use the DCL command procedure I SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM available on V5.0 and later to set aD up the necessary DCL foreign command symbols used for these and for 1 various other tools provided by TCP/IP Services.)u     ----  B OpenVMS software (formerly at Western Kentucky University (WKU) is< now available via Madgoat and via Process Software archives:  +   http://www.process.com/openvms/index.htmls   http://www.madgoat.com/ ;                                            [Hunter Goatley]-     ----  @ The FILESERV packages are also available via anonymous FTP from:     Via anonymous FTP from:s'     ftp://ftp.process.com/vms-freeware/a/     ftp.process.com, under [.WKU.VMS.FILESERV].(>     ftp.vms.stacken.kth.se, under [.MIRRORS.WKU.VMS.FILESERV].1     ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].c     ftp.riken.go.jp 3     ftp.vsm.com.au, under kits and kits/decwindows.i/     ftp.vsm.com.au, via the WWW instead of FTP.e  C or via e-mail from FILESERV@PROCESS.COM. Send the commands HELP andn>    DIR ALL in the body of a mail message for more information.     ----  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 submissions  to vmsnet.sources.     ----  K Arne Vajhj runs an OpenVMS WWW page, with software and other pointers, at:e   http://www.levitte.org/~ava/     ----   Kermit is available at:"$   http://www.columbia.edu/kermit/ or   ftp://kermit.columbia.edu/     ----   ZMODEM is available at:t!   ftp://ftp.cs.pdx.edu/pub/zmodemt9 See the FILES file in that directory for further details.eF Note that this freeware version of ZMODEM will interoperate only with 6 ZMODEM software that is licensed from Omen Technology. (Also on Freeware CD)  				[Steve Lionel]     ----  G A good source of software for DEC boxes (and anything else pretty much)-C is the DECUS library. online catalogs are available as well as some-4 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:    http://www.decus.org/S  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.o 				[Everhart@Arisia.gce.com]      ----  G    DECUS SIG Tape collections are available on Mark Berryman's system,        ftp://mvb.saic.com/     ----  D    David Jones's DECthreads-based HTTP_SERVER World-Wide Web server     for OpenVMS. <      http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html 					    [Hunter Goatly]     ----  )    Secure Shell (SSH) Server for OpenVMS:e5      http://kcgl1.eng.ohio-state.edu/~JONESD/ssh/DOC/e  )    Secure Shell (SSH) Client for OpenVMS:        http://www.free.lp.se/fish/  /    Information on OpenSSL (SSLeay) for OpenVMS: #      http://www.free.lp.se/openssl/D8                                             [Leo Demers]       The SSH terminal client FISH:       http://www.free.lp.se/fish/  E    Information on OpenSSL (SSLeay) and OSU Web server interoperation:e-      http://www.ourservers.net/openvms_ports/      ----  G DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4 built for UCX.  V1.2-4pB 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   is available from:    ftp://wvnvms.wvnet.edu/mosaic/     ----  ? Lynx (a character-cell World-Wide-Web reader) is available fromp"   ftp://ftp2.cc.ukans.edu/pub/lynx 					    [Steve Lionel]      ----  = Netscape Navigator and Mozilla web browsers are available at: ;   http://www.openvms.compaq.com/ebusiness/Technology.html      http://www.mozilla.org/f     ----  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.htmlt     ----   GNU Privacy Guard (GPG, GnuPG):   K Search the comp.os.vms newsgroup archives for information regarding GnuPG; iJ the source code, binaries for various platforms, and documentation are all
 available at:-     http://www.gnupg.org/-  A The OpenVMS source code and OpenVMS Alpha images can be found at:c  ?   http://seqaxp.bio.caltech.edu/pub/SOFTWARE/GNUPG1_0_4_VMS.ZIPN  J As of this time, the port only runs on OpenVMS Alpha, but an investigation: of an OpenVMS VAX port is reportedly under consideration.   5                                      [Aaron Sakovich]E     ----  ? An archive of the CENA DECwindows, X Windows, and VMS software n- packages can be found at the following sites:.     http://decwarch.free.fr/    ftp://ftp2.cnam.fr/decwindows/%   ftp://ftp.ctrl-c.liu.se/decwindows/n2   ftp://ftp.vms.stacken.kth.se/mirrors/decwindows/)   http://www.multimania.com/pmoreau/decw/    (See also Freeware CD) 					    [Patrick Moreau]s     ----  I ImageMagick is an X11 package for display and interactive manipulation of E images.  The package includes tools for image conversion, annotation,VI compositing, animation, and creating montages.  ImageMagick can read and fI write many of the more popular image formats (e.g. JPEG, TIFF, PNM, XPM, l Photo CD, etc.). -   http://www.imagemagick.org/d (Also on Freeware CD)s 					    [cristy@dupont.com]     ----   XV is available from:b    ftp://ftp.cis.upenn.edu/pub/xv   http://www.sanface.com/t8   ftp://www-pi.physics.uiowa.edu/~dyson/xv-3_10a-vms.zip     ----  I Many software packages are available for displaying various bitmap files  J (.JPG, .GIF, .BMP, etc) on OpenVMS.  Xloadimage, Xli, Xv, ImageMagick are G the most common tools used under OpenVMS.  Various web browsers such asOH Mozilla (qv) can also display various file formats on OpenVMS.  You can 3 find some of these tools at the DECwindows Archive:P  3   http://www.multimania.com/pmoreau/decw/index.html 4   http://www.multimania.com/pmoreau/decw/images.html;                                            [Patrick Moreau]r     ----  7 GHOSTSCRIPT (gs) and GHOSTVIEW (gv) are available from:m4   http://www.openvms.compaq.com/freeware/freeware50/+   Also available on the Freeware V5 CD-ROM.P     Also see:v&     http://www.cs.wisc.edu/~ghost/gnu/     ----  @ XPDF, a viewer for PDF (Adobe Acrobat) files, is available from:9   http://www.openvms.compaq.com/freeware/freeware50/xpdf/c   http://www.foolabs.com/xpdf/+   Also available on the Freeware V5 CD-ROM.p  B                                             [Ki Suk Hahn, Hoffman]  D   Beware: the XPDF tool included on OpenVMS Freeware V4.0 is dated, B   and has been found to have various bugs.  Use the Freeware V5.0 $   version of the XPDF kit, or later.  L A Java-based PDF viewer is available from Adobe, and is known to operate on  recent OpenVMS Alpha releases:   http://www.adobe.com/c     ----  H Various OpenVMS-related tools -- both freeware and shareware -- such as ! txt2pdf -- are available from at:e   http://www.sanface.com/v     ----  F The MPEG library version 1.1 is available for OpenVMS VAX and Alpha at3   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readme 0   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip 					    [Patrick Moreau]n     ----  4 List of FTP Mirror Sites for the DECWINDOWS archive:  A AXP.PSL.KU.DK             (Multinet)  Mirror of CENA DECW archiverA FTP2.CNAM.FR              (MadGoat)   Mirror of CENA DECW archivel  I ftp.x.org (in /contrib/vms)  not really a mirror, but I try to put all mye new ports at this site.E     ----  5 List of HTTP Mirror Sites for the DECWINDOWS archive:b  ;   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.htmln  = Some X clients from the OpenVMS Freeware CDROM are located int# [.DECWINDOWS.CDFREEWARE] directory.e 						[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.nM It contains now listings for over 30 ftp servers with >14 GB of VMS software.mH The most useful commands are LIST, which generates a list of scanned ftpG servers, and FIND <string>, whichs looks for a file containing "string"(I in the name; the search modes are only "substring" [default] and "exact", L 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'tzD found, please let me know. (The program that build the databases can= recursively scan whole servers or just specific directories).S  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).u 						[stfp@roipb.cs.ipb.ro]     ----  9   The Levitte (extended :-) Family (and OpenVMS) website:R     http://www.levitte.org/       http://www.levitte.org/~ava/     ---   E   Robert's OpenVMS Hobbyist Systems, including OpenVMS public domain .   software and various ports:        http://www.ourservers.net/  <                                           [Robert Alan Byer]   ----     CalTech Software Archives:?     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/AAA_CONTENTS.TXTS     ----  *   DJE Systems Website (David J. Dachtera) '     http://www.djesys.com/freeware/vms/o     ----     Web Servers:8     Apache Web server (Compaq Secure Web Server (CSWS)):=       http://www.openvms.compaq.com/ebusiness/Technology.html.=       http://www.er6.eng.ohio-state.edu/~jonesd/apache/1_3_9/      OSU Web server?       http://www.er6.eng.ohio-state.edu/www/doc/serverinfo.html #       http://www.kjsl.com/archives/e1       email list: VMS-WEB-daemon-Request@KJSL.COMe     WASD Web serverl"       http://wasd.vsm.com.au/wasd/     Purveyor Web server:1       email list: listserv@cjis.ci.lincoln.ne.us  9          no subject, one line message: SUBSCRIBE PURVEYORs     ----  #   CD-R (CD-Recordable) media tools:      please see FILE7     ----  "   Grace (WYSIWYG 2D plotting tool),     http://plasma-gate.weizmann.ac.il/Grace/     ----  G   The POV-Ray ("Persistance of Vision" Raytracer) ray-tracing graphics s/   package is available on the OpenVMS Freeware.w     ----  !   Majordomo mailing list handler:i;     http://www.openvms.compaq.com/ebusiness/Technology.htmla     ----  ;   PINE (OpenVMS tools for sending and receiving MIME mail):p*     ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/3     http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/K  5   A MIME tool is available in OpenVMS V7.2 and later.a  >   Also see the mmencode base64 encode and decode available at:9     http://nucwww.chem.sunysb.edu/htbin/software_list.cgiu        ----  7 Menufinder (menu-driven system management environment):F'    http://www.itre.com/mf/download.htmli     ----   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   Supply (UPS) is available from:f  ;     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/TCONTROL.ZIPi:                                             [David Mathog]  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.zip   :                                             [Arne Vajhoej]  = For tools to manage or to search your OpenVMS MAIL file, see:,?   http://vms.process.com/scripts/fileserv/fileserv.com?MLSEARCH <                                             [Phillip Helbig,;                                             Hunter Goatley]-     ----? AscToHTM attempts to convert any plain text file to HTML, while,> AscToTab restricts itself to files that are plain text tables.5 (Versions are also availabe on the OpenVMS Freeware).r.     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)h is available at:8   http://ifn03.ifn.ing.tu-bs.de/ifn/sonst/samba-vms.html   http://www.samba.org/b  E To subscribe to the SAMBA-VMS mailing list e-mail listproc@samba.org n; with no subject line and the following single line of text:M  #  subscribe samba-vms Your Full Namei  	 Also see:h   http://lists.samba.org/s     ----   Perl: See SOFT12     ----   XML:  8   Source code of an XML Parser is available from Oracle.     Also see:   '     http://www.python.org/sigs/xml-sig/b    ?   An XML parser is available as part of OpenVMS V7.3 and later.f     ----  ' GTK+ (The GIMP GUI Tookit) for OpenVMS:m9   http://www.openvms.compaq.com/ebusiness/Technology.htmle     ----  D OpenVMS Porting Library now available - for easier porting of C/C++ " applications from UNIX to OpenVMS:9   http://www.openvms.compaq.com/ebusiness/Technology.htmle     ----   Mlucas (specialized FFT):   *   ftp://hogranch.com/pub/mayer/README.html1                                [Robert Deininger]a     ----  G Tools to monitor the terminals and the activity of other OpenVMS users 5I (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.h  $   http://www.networkingdynamics.com/   http://www.raxco.com/d     ----   Python for OpenVMS:t     http://www.python.org/'   http://decus.decus.de/~zessin/python/n   Various packages: 6   http://richj.home.mindspring.com/richware/index.html:   http://www3.sympatico.ca/n.rieck/links/cool_vax_vms.html     ----  / TSM (Terminal Server Manager) is available via:T  O   http://www.compaq.com/support/digital_networks_archive/servers/tsm/index.htmlg4   http://www.openvms.compaq.com/freeware/freeware50/F   (Beware: The TSM saveset on the Freeware V5.0 disk media is busted.)     ----  K Information on the Kermit tool ("file transfer, terminal emulation, script s= programming, and character-set conversion") is available via:   !   http://www.columbia.edu/kermit/      ----   TCL for OpenVMS:  ?   ftp://sapodilla.rsmas.miami.edu/pub/VMS-tcl/tcl8.0p2-tk8.0p2/-     ----  E make, gmake, mmk and other build tools are available on the Freeware.r     ----  B An OpenVMS port of the ht://Dig web search engine is available at:     ftp://ftp.pdv-systeme.de/vms/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, A     awk, ar, mail, etc., the POSIX shell, the POSIX C programming      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 with:?     OpenVMS V5.5 later.  The POSIX installation kit is includedoA     on the consolidated distribution CD-ROM kit, and installationo'     kits are also available separately.r  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 uC     added into OpenVMS.  Versions of POSIX generally do not operatea3     on V7.x OpenVMS VAX and OpenVMS Alpha releases.i   C: nH   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 coexistRJ   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:e     and UCX$EXAMPLES: areas.  
 X Windows:%   Various Compaq X Windows utilities:.  G     xwd, xev, mosaic WWW browser, xrdb, bmtoa and atobm, xpr, ico, etc.a  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: 6   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,rB     the mx SMTP mail exchange package, X windows flight simulator,C     the mxrn X windows news reader, the OSU HTTPD WWW server, a WWWc=     gopher browser, etc. are all on the FreeWare V2.0 CD-ROM.L  	 IP tools: E   DEC TCP/IP (UCX) contains tools such as ping, uuencode, smtp, snmp,lG   rcp, nfs, tnfs, etc.  OpenVMS V6.2 and UCX V3.3 and later can be used.F   together in support of the /FTP, /RCP, /RLOGIN, /TELNET, and /TN3270%   qualifiers on various DCL commands.m  4     Also see the various C examples in UCX$EXAMPLES:   					[Stephen Hoffman]  	 vi clonesr  1   vile, vim and elvis (vi clones) run on OpenVMS.e  $   The current version of vile is 7.1   It's available atd/ 	http://www.clark.net/pub/dickey/vile/vile.htmlm2 	Versions of VILE are also on the OpenVMS Freeware       vim: vi improved      http://www.polarfox.com/vim/9                                         [Zoltan Arpadffy]w  
 GNU tools:  B   Information on the GNU on VMS (GNV) Project, which aims to port 7   GNU software (BASH, etc) to OpenVMS, is available at:t       http://gnv.sourceforge.net/      Software info:  '     http://vms.gnu.ai.mit.edu/software/      Software archive:h  .     ftp://vms.gnu.ai.mit.edu/gnu-vms/software/     GCC:  I   A mirror for work performed at the Progis company in Germany in portings?   GCC (GNU C) to OpenVMS Alpha and OpenVMS VAX is available at:e  '     ftp://vms.gnu.org/progis_mirror/gcco-     http://www.levitte.org/~ava/vms_gnu.htmlxs  K   The latest (known to me) GCC version for VAX/VMS (binaries only) is 2.7.1a   from Pat Rankin's site.   &     ftp://ftp.caltech.edu/pub/rankin/   G                                     [Jason Armistead, Richard Levitte, dC                                     Arne Vajhoej, John E. Malmberg]u  I There are also updated header files for GCC on OpenVMS VAX that allow it 	6 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:r  #   http://www.robomon.com/  (Heroix)s1   http://www.ki.com/products/clim/  (KI Products)G,   http://www.globalmt.com/ (Global Maintech)    http://www.tditx.com/ (TECsys)0   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  > 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:r  5   SET FILE/PROTECT=(current_protection_mask) [...]*.*O    @ 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:s  !   $ RENAME filename.ext;version *-7   http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCHn.   MadGoat FILE tool (see the MadGoat archives)(     use /REVISION_DATE or /CREATION_DATE)   The DFU tool (see the OpenVMS Freeware)    The pair:f5     $ set file 'p1' /acl=(ident=[system],access=none)v=     $ set file 'p1' /acl=(ident=[system],access=none) /deletes   SET FILE/VERSION=0   The following hack:c&     $!   Command procedure SETDATE.COM     $!1     $!   Changes the DATES for an input file to a'     $!   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     ...t,   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?l  C Mozilla.org is the open source organization providing Netscape and MB other interested parties with a browser.  Netscape is expected to C commercialize this mozilla.org browser, add additional proprietary nG features, and release it as Netscape Communicator (version number TBD).tG This Netscape Communicator will contain the features that the Internet  6 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.  l  5 The Mozilla.org web browser schedule is available at:r     http://www.mozilla.org/w  > The latest information and current downloads are available at:  9   http://www.openvms.compaq.com/ebusiness/Technology.html   E See section SOFT9 for information on various certificates for V3.003 e= Netscape Navigator; certificates that have presently expired.i 					[Sue Denham]n 					[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 aH   definition requires a floating point format (IEEE) that is not native E   to VAX, and this would require the emulation of all floating point  H   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  I   for OpenVMS VAX -- and specifically to the VAX VCG code generator that SH   is used by Compaq C on OpenVMS VAX systems -- in order to add support I   for passing IEEE-format floating point doubles around.  Alternatively, MJ   extensive changes to the Java source code to remove the assumption that -   the double is an IEEE floating point value.a  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,p6   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.   I   If you are having problems with Display Postscript, you need to upgradeeG   your Java kit -- 1.2.2-3 and later remove the requirement for Display E   Postcript extensions, and Java 1.2.2-3 is required with DECwindows b   V1.2-6 and later.e  F   For additional information on Java for Alpha systems, please see theA   OpenVMS documentation (V7.2 and later), and the following site:p  /     http://www.compaq.com/java/alpha/index.htmlm  H   Compaq Secure Web Server (CSWS) includes CSWS_JAVA, which provides theK   following Apache Tomcat technologies: JavaServer Pages 1.1, Java Servlet II   2.2, and MOD_JK.  (CSWS is based on the Apache web server.  See SOFT1.)     < ------------------------------------------------------------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 ANSI C compiler for OpenVMS Alpha systems.E   VAX C predates the ANSI C standards, and has various areas that arekJ   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 t   as either DEC C or DIGITAL C.a  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.e  K   A current "C" license PAK allows access to both VAX C and Compaq C on thev   same OpenVMS VAX system.  M   Various Compaq C versions can be installed on OpenVMS VAX V5.5-2 and later.tL   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. I   OpenVMS VAX versions V6.1 and later do not require a seperate RTL kit, wI   but Compaq C RTL ECO kits are available to resolve problems found with i(   the C RTL on various OpenVMS releases.  E   Wwith Compaq C, for automatic resolution of the standard C library  D   routines by the LINKER utility, use the /PREFIX qualifier, such asG   /PREFIX=ALL_ENTRIES.  If a particular application program replaces anXE   existing C library routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)).wE   (VAX C required explicit specification of an RTL shareable image orb$   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 therG   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 routine F   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,cI   and the external routines share the same names as the library routines.wF   (This is not recommended, but there are applications around that useE   this technique.)  Thus the need to explicity specify whether or notlE   the "decc$" prefix should be prepended to the external symbol namesv   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_ENTRIESbB       As mentioned above.  Failure to specificy this qualifier canA       cause the compiler to not add the prefixes for the names ofnE       the C library routines into the references placed in the object,E       module, which can in turn cause problems resolving the externalz<       symbols in the library when the object code is linked.  $     /ASSUME=WRITABLE_STRING_LITERALSC       Some VAX C programs erroneously write to the string literals.TB       By default, Compaq C does not allow the constants to change.       /SHARE_GLOBALSA       Enables sharing ("shr") of globals and of extern variables.wG       Compaq C sets externs as non-shareable ("noshr"), VAX C as "shr".B       /EXTERN_MODE=COMMON_BLOCK =       VAX C assumes common block model for external linkages.l       /[NO]MEMBER_ALIGNMENT/A       Refers to the padding placed between member elements withinn?       a struct.  Disabling member alignment packs the data more =       tightly into memory, but this packaging has performanceu;       implications, both on OpenVMS VAX and particularly onf       OpenVMS Alpha systems.  E   Permit structure members to be naturally aligned whenever possible, E   and avoid using /NOMEMBER_ALIGNMENT.  If you need to disable memberaA   alignment, use the equivilent #pragma to designate the specificsE   structures.  The alignment of structure members normally only comesaB   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 thetD   contents of the standard header libraries into directories such asG   SYS$SYSROOT:[DECC$LIB...], and provide various logical names that canuG   be defined to control library searches.  With Compaq C versions such sH   as V6.0, the default operations of the compiler match the expectationsC   of most OpenVMS programmers, without requiring any definitions of G   site-specific library-related logical names.  (And logical names leftxE   from older DEC C versions can sometimes cause the compiler troublesl   locating header files.)h  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 pE   language RTLs ship with OpenVMS itself, and not with the compilers.s  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 n   sites such ast  )     http://www.openvms.compaq.com/wizard/      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 /G     tm_year.  This field will contain a value of 100 in the year 2000, nF     101 for 2001, etc., and the yearly incrementation of this field is     expected to continue.k  G     The C epoch typically uses a longword (known as time_t) to contain wH     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.)f  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 savings0J     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.)  F     When sharing variables with other languages, here is some example      Compaq C code...  	       ...        #pragma extern_model savea(       #pragma extern_model strict_refdef!       extern int   VMS$GL_FLAVOR;e"       #pragma extern_model restore	       ...e  5     and here is some associated example Bliss code...   	       ...        EXTERNAL          VMS$GL_FLAVOR,e
       ....       Other common C++ issues:  G     Compaq C++ (a separate compiler from Compaq C) provides both symbolsH     mangling and symbol decoration.  Some of the details of working withG     longer symbol names and the resulting symbol name mangling in mixediE     language environments are listed in the shareable image cookbook,aE     and in the C++ documentation.  Symbol name decoration permits theoJ     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  L     often do need to disable this decoration via the extern "C" declaration      mechanism:         extern "C"	         {6(         extern int ExternSymbol(void *);-         extern int OtherExternSymbol(void *);s	         }O  G   Also see ALPHA16 for information on /ARCHITECTURE and /OPTIMIZE=TUNE.   F   See PROG17 for information on the C system and the lib$spawn call in   CAPTIVE environments.X  F   Constructs such as the order of incrementation or decrementation andB   the order of argument processing within an argument list are allG   implementation-defined.  This means that C coding constructs such as:        i = i++;     a[i] = i++;a     foo( i, i++, --i);  F   are undefined and can have (adverse) implications when porting the CE   code to another C compiler or to another platform.  In general, anysE   combination of ++, --, =, +=, -=, *=, etc operators that will causel@   the same value to be modified multiple times (between what theD   ANSI/ISO C standard calls "sequence points") produce undefined and"   implementation-specific results.  G   Within C, the following are the "sequence points": the ";" at the endnE   of a C statment, the ||, &&, ?:, and comma operators, and a call to.D   a function.  Note specifically that = is NOT a sequence point, andD   that the individual arguments contained within a function argumentE   list can be processed from right to left, from left to right, or atA   any random whim.  F   Compaq C for OpenVMS VAX (formerly DEC C) and VAX C do differ in the   related processing.   F   So you are looking for OpenVMS-specific definitions (include files)?  I   UCBDEF.H, PCBDEF.H and other OpenVMS-specific definitions -- these are  G   considered part of OpenVMS and not part of the C compiler kit -- are  1   available on all recent OpenVMS Alpha releases.:  L   To reference the version-dependent symbol library sys$share:sys$lib_c.tlb,9   use a command similar to the following for compilation:p  (     CC sourcea+SYS$LIBRARY:SYS$LIB_C/LIB  A   You can also define DECC$TEXT_LIBRARY to reference the library.   K   You will want to review the Programming Concepts manual, and specificallyr"   take a quick look at Chapter 21.  D   And some general background: the STARLET definitions (and thus theJ   sys$starlet_c.tlb library) contain the symbols and the definitions that H   are independent of the OpenVMS version.  The LIB definitions (and thusJ   sys$lib_c) contain symbols and definitions that can be dependent on the I   OpenVMS version.  You won't need to rebuild your code after an OpenVMS nJ   upgrade if you have included definitions from STARLET.  The same cannot J   be said for some of the definitions in LIB -- you might need to rebuild E   your code.  (The UCB structure can and has changed from release to C   release, for instance.)s  H   Recent versions of C automatically search sys$starlet_c.tlb.  Explicit-   specification of sys$lib_c.tlb is required.   F   Also see the Ask The Wizard website (www.openvms.compaq.com/wizard/)$   topics (2486), (3803), and (1661).   < ------------------------------------------------------------1 SOFT6.    Obtaining user input in DCL CGI script?o  E If you choose to use the GET method, then the form data is available a6 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 UE stdin. For a DCL CGI script running under the Netscape FastTrack web  ? server, you can read the data using the following READ command:s     $ READ SYS$COMMAND postdata    to read the information in. =                                                 [Colin Blake]p  @ 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", - 0       "entry_number","display_entry","this_job")  E Remember that the entry numbers issued by the OpenVMS Job Controller uE are opaque longword values.  Don't assume you know the format of the  1 number, nor the range of numbers you might see...g>                                                 [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 libraries C starting with V3.5-03 -- to ensure that earlier versions of CMS are-B unable to access the database once the "conversion" to V3.5-05 andG later is made, you must issue the following two commands when upgradingtB 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 np < 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 compatibilitylE with tools that expect to find a 00CMS.CMS file (eg: various versionsi. 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        entrustuD http://www.thawte.com/                                        thwateF 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" tab 8 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 same     name as the original.  ; VeriSign/RSA Server certificate which expired Dec 31, 1999:e  : 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 certificatesv, 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 suggestsf     using the name "VeriSign CA".  ;                                           [Vance Haemmerle]   < ------------------------------------------------------------3 SOFT10.   Why doesn't DCL symbol substitution work?v  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 iC substitution in this environment, you typically write a small file eE containing the command(s) and data to be invoked -- potentially only mC the data -- and you then invoke the created procedure or reference n the specified data.c  C In this case, use of a file containing nolinemode commands or othersC techniques might be useful -- you will want to ensure that the texteF 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 and E the apostrophe.  In most cases, only the apostrophe is necessary.  IniG a few cases -- such as the DCL PIPE command -- you will may need to useSE the ampersand to get the substitution to work.  The following exampleSB 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  G in the current job) was used as DCL symbols cannot be returned back outA, from a DCL PIPE or other spawned subprocess.    < ------------------------------------------------------------ SOFT11.   Duplicates MGMT40.  < ------------------------------------------------------------+ SOFT12.   Where can I get Perl for OpenVMS?   F OpenVMS support is included in the standard distribution of Perl, the I popular scripting language created by Larry Wall.  In addition to nearly iE all of the functionality available under Unix, OpenVMS-specific Perl pE modules provide interfaces to many native features, as well as access F 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 kH 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 OD and build it yourself.  The latest production quality source kit is  available from:y  /      http://www.perl.com/CPAN/src/stable.tar.gzI  I You will need GUNZIP and VMSTAR (both available from the OpenVMS FreewaregG CD, or from other sites) to unpack the archive; once you've done that, E- read the instructions in the README.vms file.i  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.htmlt2      http://www.openvms.compaq.com/freeware/perl5/  H During active Perl development cycles, test kits are sometimes found at: from:G        ftp://ftp.sidhe.org/i  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 a% building and running Perl on OpenVMS:l  )      http://www.crinoid.com/crinoid.htmlxe  G There are OpenVMS-specific Perl modules that implement interfaces to a vH 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 d( relevant modules are all available from:  3      http://www.perl.com/CPAN/modules/by-module/VMSs  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:o       vmsperl-subscribe@perl.org  - The mailing list archives may be searched at:h  4     http://www.xray.mpe.mpg.de/mailing-lists/vmsperl;                                               [Craig Berry]h  < ------------------------------------------------------------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.s     See UTIL4.  < ------------------------------------------------------------? SOFT14.   Where can I get Zip, Unzip, self-extracting zip, etc?   A   Many packages are provided in ZIP, GZIP, or BZIP format, which EA   requires you to acquire the associated unzip tool to unpack it.m5   You can get ZIP and UNZIP from the following areas:n  =   http://www.openvms.compaq.com/freeware/freeware50/000tools/g:   http://www.openvms.compaq.com/freeware/freeware50/bzip2/=   http://www.openvms.compaq.com/freeware/freeware50/info-zip/t=   http://www.openvms.compaq.com/freeware/freeware40/000tools/ 4   ftp://ftp.process.com/vms-freeware/unzip.alpha_exe2   ftp://ftp.process.com/vms-freeware/unzip.vax_exe/   http://www.decus.de:8080/www/vms/sw/zip.htmlxT    http://www.djesys.com/zip.html"   http://www.djesys.com/unzip.html  G   or you can request the FILESERV_TOOLS package from the e-mail server.e  F   [Beware: The [000TOOLS...] pre-built versions of ZIP on the OpenVMS B   Freeware V4 (http://www.openvms.compaq.com/freeware/freeware40/)G   CD-ROM will erroneously return BILF errors on OpenVMS V7.2 and later.oG   Use of the source on the Freeware V4 to rebuild the ZIP image(s), or YH   acquiring a pre-built ZIP image from one of the above areas can avoid F   this.  The pre-built version of ZIP on the Freeware V4 kit is older ?   than the included ZIP sources, and it contains a latent bug.]s  F   Directions for using sfx (self-extracting zip) are available in the    unzip kit available at:e  ?     http://www.openvms.compaq.com/freeware/freeware50/unzip542/i     Specifically:a  K     http://www.openvms.compaq.com/freeware/freeware50/UNZIP542/UNZIPSFX.TXTa  D   If you want to build the zip images for yourself (eg: for an older5   OpenVMS version), pull over the entire contents of:   L     http://www.openvms.compaq.com/freeware/freeware50/unzip542/vms-binaries/     and invoke LINK.COM.   [End of Part 4/5]m  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 02 Oct 2001 21:37:07 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 5/5i1 Message-ID: <7squ7.961$YP.25670@news.cpqcorp.net>u   Archive-name: dec-faq/vms/part5r Posting-Frequency: quarterly Last-modified: 2 Oct 2001  Version: VMS-FAQ-5.TXT(7)h    9 This is the OpenVMS Frequently Asked Questions Part 5/5. t@ 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,eH 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 ae
 trademark.  E When it came time to chose a "marketing name" for the Alpha AXP line,iI the company was in a quandary.  The internal "code name" for the project,oK Alpha, was widely known and would seem the ideal choice, but it was already J 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 withcF two lists of possible names.  The first list was intended to evoke theC feeling of "extension to VAX", while the second list was to suggesteG "not a VAX".  Unfortunately, none of the choices offered were any good;eI for example, "VAX 2000" was found on the first list while the second list < 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 CE very much like an Arabic word with decidely unfortunate connotations.eF Eventually, AXP was selected; the architecture would be referred to as= "Alpha AXP" whereas products themselves would use just "AXP".b  G Use of the AXP term has been phased out in favour of using Alpha.  For rG example, "OpenVMS AXP" is now officially refered to as "OpenVMS Alpha".c  < ------------------------------------------------------------A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?t  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 AlphaeD       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_float E       when stored.  Because the G_float type has three fewer fractionrE       bits than D_float, some applications may get different results.r;       IEEE float types are also available on OpenVMS Alpha.   C     - Data alignment is extremely important for best performance on ?       Alpha.  This means that data items should be allocated at C       addresses which are exact multiples of their sizes.  Quadwordo?       alignment will offer the best performance, especially forsA       character values and those smaller than 32 bits.  CompilersaB       will naturally align variables where they can and will issue3       warnings if they detect unaligned data items.o  E     - Compaq C is the only C compiler Compaq offers on OpenVMS Alpha. A       It is compatible with DEC C on OpenVMS VAX, but is somewhatsL       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.a  K     - The page size on Alpha systems is variable, but is at least 8K bytes.gE       This can have some effect on applications which use the $CRMPSCDB       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 AlpharK available on the documentation CD-ROM media, both in the main documentationn* 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 latern:     - 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:z  8     http://www.compaq.com/alphaserver/archive/index.html?     http://www.compaq.com/alphaserver/performance/perf_tps.html-     Also see CPU2000:   $     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:   ?     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/index.htmlo5     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:l  =     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/   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.txt F   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkbootarc.txtE   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkntboot.txtw  G The SROM firmware loader expects an ODS-2 formatted floppy, see mkboot.gD As for which image to use, the ROM image uses a header and the file F extension .ROM, and the SROM bootable floppy cannot use the .ROM file.  ;                                           [Stephen Hoffman]e  A To check the firmware loaded on recent OpenVMS Alpha systems, user the command:  0   $ write sys$output f$getsyi("console_version")0   $ write sys$output f$getsyi("palcode_version")   SDA> CLUE CONFIG7                                           [Clair Grant]      Also see ALPHA14.t    < ------------------------------------------------------------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 yD 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 emulator- acting as a serial console are:h  >   9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).  H AlphaServer 4100 and derivative series platforms, and AlphaServer GS80, B GS160, and GS320 series system consoles are capable of 57600 baud.D See the COM2_BAUD console environment variable, and ensure that you ) have current SRM firmware version loaded.   K The AlphaStation and AlphaServer series use the PC DIN serial connector fordF the "COM1" and "COM2" serial lines, see WIRES1 for details and pinout.  < ------------------------------------------------------------< 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:  ;   http://www.openvms.compaq.com/freeware/freeware50/multia/i  > Instructions are included IN the kits.  READ THE INSTRUCTIONS.  E Some of the restrictions involved when running OpenVMS on the Multia  > system include (but may well not be limited to) the following:  A   o The PCMCIA support was completely removed, because the Intel eB     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.t  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.h      o The serial lines don't work.  ?   o If you have a Multia with a PCI slot, you can't use any PCIs"     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  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:s  0   http://www.djesys.com/vms/hobbyist/multia.html2   http://www.djesys.com/vms/hobbyist/mltianot.html1   http://www.djesys.com/vms/hobbyist/support.html 2   http://www.netbsd.org/Ports/alpha/multiafaq.html2   http://www.brouhaha.com/~eric/computers/udb.html   					[Stephen Hoffman];                                         [David J. Dachtera]s  E OpenVMS Alpha is not supported on the AlphaPC 164LX and 164SX series, C though there are folks that have gotten certain of the LX series toL@ load SRM and bootstrap OpenVMS.  (The Aspen Durango II variant.)@ One problem was reported: IDE bootstraps fail; SCSI is required.   Also see ALPHA13.e  < ------------------------------------------------------------B ALPHA9.  What is the least expensive system that will run OpenVMS?  ? The cheapest systems presently offered by Compaq that will run  C 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) tB OpenVMS -- see the OpenVMS Software Product Description (SPD) for E details on the supported systems and configurations.  There are also  C many used AlphaStation, AlphaServer, and DEC 3000 models available t? which are quite suitable.  For more experienced OpenVMS system  @ managers, the (unsupported) Multia can bootstrap OpenVMS -- see  ALPHA8 for details.e  @ Depending on the OpenVMS version and configuration, the OpenVMS 3 Software Product Description (SPD) is available at:   !   http://www.compaq.com/info/spd/t:   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.v  7 CD-ROM drive compatibility information is available at:e.   http://sites.inka.de/pcde/dec-cdrom-list.txt 					[Stephen Hoffman]  < ------------------------------------------------------------< ALPHA10.  Where can I get more information on Alpha systems?  5 Compaq operates an AlphaServer information center at:e  $   http://www.compaq.com/alphaserver/  > Alpha Technical information and documentation is available at:  ,   http://www.support.compaq.com/alpha-tools/)      documentation/current/chip-docs.htmla  1   ftp://ftp.compaq.com/pub/products/alphaCPUdocs/C  .   ftp://ftp.digital.com/pub/DEC/Alpha/systems/  *   http://ftp.digital.com/pub/Digital/info/.      semiconductor/literature/dsc-library.html  #   Platform product documentation:  t#     http://www.compaq.com/info/spd/r     Alpha Systems Update:t1     http://www.compaq.com/alphaserver/fb_acu.htmlW  / Information on Multia hardware is available at:v  2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman]  A Information on current and future Alpha microprocessor designs ism$ also available from AlphaPowered at:  1   http://www.alphapowered.com/alpha_tomorrow.htmle+   http://www.alphapowered.com/timeline.htmle.   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 OpenVMS @ Alpha primary bootstrap image APB.EXE.  These flags control the & particular behaviour of the bootstrap:     >>> BOOT -FL root,flags         bit      descriptiona9      ---   ----------------------------------------------r  -       0    CONV      Conversational bootstrapt3       1    DEBUG     Load SYSTEM_DEBUG.EXE (XDELTA) P       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 setr'       10   ISL       LAD/LAST bootstrapo1       11   PALCHECK    Disable PAL rev check haltvA       12   DEBUG_BOOT  Transfer to intermediate primary bootstrapo+       13   CRDFAIL       Mark CRD pages badrA       14   ALIGN_FAULTS  Report unaligned data traps in bootstrapw@       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)i0       18   RSM         Boot is controlled by RSM5       19   FOREIGN     Boot involves a "foreign" diskw  H   If you want to set the boot flags "permanently" use the SET BOOT_FLAGS   command, e.g.e            >>> SET BOOT_OSFLAGS 0,1    < ------------------------------------------------------------7 ALPHA12.  What are Alpha console environment variables?t  = Alpha systems have a variety of variables with values set up d; within the SRM system console.  These environment variablese; control the particular behaviour of the console program andl? the system hardware, the particular console interface presentednB 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, a8   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.  s  = OpenVMS Galaxy firmware can add console environment variableseB 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...P  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]   < ------------------------------------------------------------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:   /   http://www.jyu.fi/~kujala/vms-in-axppci33.txtm  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 l@     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, r?     you need to find an ISA Ethernet card supported by OpenVMS.n  @   o When the AXPpci33 board bootstraps, it will dump some stuff A     like a crash dump, but it will continue and -- so far -- this )     hasn't caused any particular hassles.u  C   o The system shutdown and reboot procedures do not work properly.t  A   o The serial console is reported to not work, though the serialwB     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 p?     with the PS/2 mouse and keyboard connectors and a VGA card sE     (one that will work under DECwindows) and you can run DECwindows -     on the system.  8                                       [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, meaningeG   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 D'   loaded can be a little interesting...l  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.d  I   To shuffle the files, copy the target SRM firmware file (as200_v7_0.exeaK   is current) to a blank, initialized, FAT-format floppy under the filename    A:\FWUPDATE.EXEa  G   From the AlphaBIOS Setup screen, select the Upgrade AlphaBIOS option. 5   Once the firmware update utility gets going, enter:i        Apu-> update srma  0            Answer "y" to the "Are you ready...?"        Apu-> quitb  K   You've reloaded the flash.  Now powercycle the box to finish the process.i     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 thei)   Microsoft Windows NT operating system.s  D   For the list of boxes officially supported by OpenVMS, please see 1   the OpenVMS Software Product Description (SPD).i  #     http://www.compaq.com/info/spd/y<     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  H   motherboard will resemble a supported box sufficiently closely and canE   thus mimic that system and bootstrap.  (No such family resemblancesoF   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?e  G   The Alpha architecture is upward- and downward-compatible, and newer -E   instructions are emulated on older platforms, for those cases wherenB   the compiler is explicitly requested to generate the newer Alpha   instructions.e  F   In particular, OpenVMS Alpha V7.1 and later include the instruction C   emulation capabilities necessary for the execution of newer Alphaa.   instructions on older Alpha microprocessors.  G   Alpha instructions are available in groups (or subsets).  Obviously, tC   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 various/   recent Alpha microprocessors:e       byte/word extension (BWX):-       LDBU, LDWU, SEXTB, SEXTW, STB, and STW./  3     floating-point and square root extension (FIX):pH       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG, SQRTS, and SQRTT.       count extension (CIX):       CTLZ, CTPOP, and  CTTZ.w        multi-media extension (MVI):F       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4, MINUB8, MINUW4, +       PERR, PKLB, PKWB, UNPKBL, and UNPKBW.r  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 t4   subset.  To select this subset, use the following:    -      /ARCHITECTURE=EV56/OPTIMIZE=TUNE=GENERICr    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 sJ   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 tE   of the proper code for the particular current Alpha microprocessor.t    tI   Typically /OPTIMIZE=TUNE=GENERIC is the appropriate choice for tuning, rC   and the /ARCHITECTURE selects the minimum target architecture forw,   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  I   significant benefit, then the emulation might be a performance penalty.m  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 isJ   roughly 11ppm, or 1000000/(24*60*60).)   Put another way, this is .005%,?   which is around 130 seconds per month or 26 minutes per year.n  M   The software-maintained system time can drift more, primarily due to other  K   system activity.  Typical causes of drift include extensive high-IPL codefK   (soft memory errors, heavy activity at device IPLs, etc) that are causinga7   the processing of the clock interrupts to be blocked.      Also see VAX8, TIME6.o  < ------------------------------------------------------------3 ALPHA18.  So how do I open up the DEC 3000 chassis?c  @ After removing those two little screws, tilt the back end of the1 top shell upwards -- then you can remove the lid.-  :                                            [Felix Kreisel]  < ------------------------------------------------------------! ALPHA19.  What is byte swizzling?   K "Swizzling" is the term used to describe the operation needed to do partialsN longword (i.e. byte or word) accesses to I/O space on those systems that don'tN support it directly. It involved shifting the offset into an address space by L 5 (or 7 for one older system), and ORing this into the base address. It thenF required the size of the operation to be ORed into the low order bits.  N That is, because the EV4 and EV5 CPUs did not bring bits 0 and 1 off the chip,O to do programmed I/O for bytes/words, the information on the size/offset of the J transfer was encoded into the address data. The data itself then had to beG shifted into the correct "byte lane" (i.e. its actual position within ah
 longword).  O The EV56 CPU supports the byte/word instructions however only some EV56 systemshM support byte/word accesses to I/O space. Even on an EV56 system that supportskM byte/word accesses to I/O space, the relevant OpenVMS routines do not support  byte/word access to I/O space.  M EV6 systems (with the exception of the AlphaServer GS60 and AlphaServer GS140dO series, for reasons of platform compatability) support a flat, byte addressablen
 I/O space.  N If a device driver uses CRAM or IOC$WRITE_IO/IOC$READ_IO, then OpenVMS will doF the right thing without changing the driver - OpenVMS will swizzle and unswizzle as needed.  O To use byte/word operations on MEMORY, you need to tell the compiler to use theRH EV56 or EV6 architecture (/ARCHITECTURE=EV56). Memory operations did notM swizzle, but the compiler would do long/quad access, and extract/insert bytesfL as needed. Using /ARCHITECTURE=EV56 allows smaller, more efficient byte/word access logic to memory..  M If the application is directly doing I/O space access across a range of Alpha M systems (like the graphics servers), then the driver will need to know how to/B do swizzling for old platforms, and byte access for new platforms.  G                                         [Fred Kleinsorge, Derek Garson]t  < ------------------------------------------------------------? ALPHA20.  What commands are available in the Alpha SRM console?o  F In addition to the normal BOOT commands and such (see ALPHA11 for someE details) and the normal contents of the console HELP text, operations-G such as I/O redirection and floppy disk access are possible at the SRM t console prompt:e  I 1. Format a FAT floppy, and insert it into the AlphaStation floppy drive.o  6 2. Perform the following at AlphaStation SRM Console :      >>> show * > env.dat9    >>> show conf > conf.datp%    >>> cat env.dat > fat:env.dat/dva0p'    >>> cat conf.dat > fat:conf.dat/dva0(  B 3. You may use the SRM "ls" to display the contents of the floppy.      >>> ls fat:env.dat/dva0    >>> ls fat:conf.dat/dva0s  @ 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 thatnG the particular Alpha system is supported by OpenVMS (see the SPD), thattG all core I/O components (graphics, disk controllers, etc) in the systemtD are supported by OpenVMS (see the SPD), and that you have an OpenVMSG distribution, that you have the necessary license keys (PAKs), and thate+ you have the necessary SRM firmware loaded.m  F A typical sequence used for switching over from the AlphaBIOS graphics# console to the SRM console follows:5  3   1. Press <F2> to get to the AlphaBIOS setup menu.   #   2. Pick the "CMOS Setup..." item.s  9   3. Press <F6> to get to the "Advanced CMOS Setup" menu.   ?   4. Change the "Console Selection" to "OpenVMS Console (SRM)".V  ;   5. Press <F10>, <F10>, then <Enter> to save your changes.i     6. Power-cycle the system.  I Most Alpha systems support loading both the AlphaBIOS/ARC console and the-F 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 havehG a "half-flash" system, you must load the SRM firmware from floppy, fromwD a network download, or from a firmware CD-ROM.  Following the normalE AlphaBIOS or ARC firmware update sequence to the APU prompt, and then/B explictly select the target console.  In other words, power up theE system to the AlphaBIOS or ARC console, use the supplementary optionslC to select the installation of new firmware (typically from CD-ROM),r? and then rather than using a sequence which updates the currente	 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 ddcuw$     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 ori= Tru64 UNIX on the system.  Do not allow Windows NT to write a.@ "harmless" signature to any disk used by OpenVMS, Tru64 UNIX, orA Linux, as this will clobber a key part of the disk.  (On OpenVMS,-B 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 information E on OpenVMS license PAKs (for hobbyist use) see VMS9.  For informations on the Multia, see ALPHA8.  C Information on enabling and using the failsafe firmware loader for hE various systems -- this tool is available only on some of the variousoF Alpha platforms -- is available in the hardware documentation for the G system.  This tool is used/needed when the firmware has been corrupted,r and cannot load new firmware.g  F The full list of AlphaBIOS key sequences -- these sequences are neededE when using an LK-series keyboard with AlphaBIOS, as AlphaBIOS expectss a PC-style keyboard:            F1   Ctrl/A          F2   Ctrl/B          F3   Ctrl/C          F4   Ctrl/D          F5   Ctrl/E          F6   Ctrl/F          F7   Ctrl/P          F8   Ctrl/R          F9   Ctrl/T         F10   Ctrl/U      Insert   Ctrl/V      Delete   Ctrl/W   Backspace   Ctrl/H      Escape   Ctrl/[      Return   Ctrl/M    LineFeed   Ctrl/J%    (Plus) +   upselect (some systems)l'   (Minus) -   downselect (some systems)l         TAB   down arrow    SHIFT+TAB  up arrow  < ------------------------------------------------------------@ 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?   C OpenVMS will boot and is supported on the Personal Workstation -au OC series platforms, though OpenVMS will require a SCSI CD-ROM if the FC Intel Saturn I/O (SIO) IDE chip is present in the configuration -- AE only the Cypress IDE controller chip is supported by OpenVMS for IDE n bootstraps.r  = If you have an -au series system, you can determine which IDE , 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 williC need to use and bootstrap from SCSI.  (A procedure to load DQDRIVERe@ on the Intel SIO -- once the system has bootstrapped from a SCSIC device -- is expected to be included as part of the contents of thes/ DQDRIVER directory on Freeware V5.0 and later.)t  < ------------------------------------------------------------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 variablen@   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.l  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. 2     dot-not-in-circle: halt (<break>) is disabled,,                    and auto-boot is enabled.  5   Three-position-rotary: power-up bootstrap behaviour3     arrow: normal operation.      face: language inquiry mode.)     t-in-circle: infinite self-test loop.t  4   Eight-position-rotary: console baud rate selection4     select the required baud rate; read at power-up.  pJ 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 WIRES1.  For available adapters, see WIRES2.  M Also present on the console bulkhead is a self-test indicator: a single-digit K LED display. This matches the final part of the countdown displayed on the  N console or workstation, and can be used by a service organization to determineM the nature of a processor problem.  The particular countdown sequence varies eM by processor type, consult the hardware or owner's manual for the processor, SG or contact the local hardware service organization for information the sM 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]2  < ------------------------------------------------------------< 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,rH 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"oF contains the sign and exponent (and for other than H, some of the mostK significant fraction bits).  Each successive higher-addressed word containseN 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 (buthJ 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" - touching I it causes an error - fraction bits are ignored.  There are no minus zero,e% infinity, denormalized or NaN values.u  M For all formats, the fraction is normalized and the radix point assumed to becJ 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 ine' 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]o  < ------------------------------------------------------------5 VAX3.   Where can I find more info about VAX systems?n  " Compaq runs a VAX "InfoCenter" at:  (   http://www.compaq.com/alphaserver/vax/  1 Jim Agnew maintains a MicroVAX/VAXstation FAQ at:   3   http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmli  " The VAXstation 3100 Owner's Guide:  7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmlp  ; A field guide to PDP-11 (and VAX) Q-bus and UNIBUS modules D can be found at:  8   http://metalab.unc.edu//pub/academic/computer-science/+     history/pdp-11/hardware/field-guide.txtI  9 Various VAX historical information (also see VMS1) can bee	 found at::  +   http://telnet.hu/hamster/vax/e_index.htmle  < ------------------------------------------------------------? VAX4.   Where can I find information on NetBSD for VAX systems?   / Gunnar Helliesen maintains a NetBSD VAX FAQ at:r   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 -- L 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.)i  M Various of the SCSI commands used by the boot drivers imbedded in the consolerI PROM on all members of the VAXstation 3100 series use "Group 0" commands,eI which allow a 21 bit block number field, which allows access to the firstuJ 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.u  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 for I field retrofits -- this PROM upgrade allows the use of the "Group 1" SCSIaN commands, and thus larger system disks.  There was no similar PROM upgrade for the VAXstation 3100 series.-  ( Systems that are affected by this limit:G   o VAXstation 3100 series, all members.  No PROM upgrade is available.BB   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  B     versions prior to V6.4 are affected.  A PROM upgrade for these-     specific systems is (was once) available.e  	 Also see:g7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmlo   Also see FILE5.0 						[Stephen Hoffman]o  < ------------------------------------------------------------  VAX6.  replaced by TIME section.  < ------------------------------------------------------------) VAX7.  What are the VMB boot flag values?s  ? The following flags are passed (via register R5) to the OpenVMS,> 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:-     >>> BOOT/R5:flagso  @   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.                                     ?                                                                h@    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.                     y< ------------------------------------------------------------A VAX8.   What is the Accuracy of VAX the Time of Year (TOY) Clock?   A   The VAX Time-Of-Year (TOY) clock (used to save the time over a lA   reboot or power failure) is specified as having an accuracy of I;   .0025%.  This is a drift of roughly 65 seconds per month.   C   The VAX Interval Time is used to keep the running time, and this nF   has a specified accuracy of .01%.  This is a drift of approximately    8.64 seconds per day.e  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"oA console ports behaviours based on the setting of the BREAK enablenC switch.  When the console is not enabled to respond to BREAK, MMJ-1aD is the console port.  MMJ-3 will (confusingly) output the results ofC the selftest in parallel with MMJ-1. When the console is enabled tor@ 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 -- thatM8 enables one of the serial lines as the system console.    A Various members of the DEC 3000 series Alpha systems also have a rB similarly-labled S3 switch for selection of the alternate console.    $ Also see ALPHA7, DECW13, and MGMT22.  < ------------------------------------------------------------/ VAX11.  What are the VAX processor (CPU) codes?s      CPU:    Platform:    -----   ---------)    KA41-A : MicroVAX 3100 Model 10 and 20p*    KA41-B : VAXserver 3100 Model 10 and 20    KA41-C : InfoServer+    KA41-D : MicroVAX 3100 Model 10e and 20e-,    KA41-E : VAXserver 3100 Model 10e and 20e+    KA42-A : VAXstation 3100 Model 30 and 40s+    KA42-B : VAXstation 3100 Model 38 and 48n$    KA43-A : VAXstation 3100 Model 76)    KA45   : MicroVAX 3100 Model 30 and 40S$    KA46   : VAXstation 4000 Model 60"    KA47   : MicroVAX 3100 Model 80    KA48   : VAXstation 4000 VLC (    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)     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 IIIn    KA64A  : VAX 6000-4007    KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III+o    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-500A5    KA690  : VAX 4000-600    KA691  : VAX 4000-605A     KA692  : VAX 4000-700As    KA693  : VAX 4000-605A-    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]  < ------------------------------------------------------------* ITAN1.  OpenVMS is porting to Intel IA-64?  @ Yes, OpenVMS is being ported to the Intel IA-64 architecture; to4 systems based on the Intel Itanium Processor Family.  < ------------------------------------------------------------2 ITAN2.  Where can I get Intel Itanium information?  @ Intel Itanium Processor Family Architecture, Hardware, software,' and related materials are available at:   2     ftp://download.intel.com/design/IA-64/manuals/4     ftp://download.intel.com/design/IA-64/Downloads/       See:I       ftp://download.intel.com/design/IA-64/Downloads/archSysSoftware.pdf B       ftp://download.intel.com/design/IA-64/Downloads/24870101.pdf  F   The Intel Extensible Firmware Interface (EFI) console documentation:2     http://www.pentium.de/technology/efi/index.htm       < ------------------------------------------------------------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:m      http://www.compaq.com/support/  : Various hardware and system documentation is available at:  ?   http://www.compaq.com/support/techpubs/user_reference_guides/A1   http://www.adenzel.demon.nl/vaxes/microvax3100/f2   http://www.adenzel.demon.nl/vaxes/infoserver150/  C TSM (Terminal Server Manager), DEChub, DECserver, etc. information:o  9   http://www.compaq.com/support/digital_networks_archive/o      < ------------------------------------------------------------E SUPP2.  Where can I get hardware self-maintenance support assistance?s  F The Compaq Assisted Services (CAS) program (a direct descendent of theH program once known as DECmailer) is available to customers that wish to I maintain their own system(s) (self-maintenance), but that wish some level H of assistance in acquiring hardware diagnostics and hardware manuals forF the system(s), and that wish to have access to spares and module-level5 repairs for customer-performed hardware module swaps:   $   http://www.compaq.com/CAS-Catalog/  < ------------------------------------------------------------G SUPP3. Why does my system halt when I power-cycle the console terminal?i  <   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 various=B   VAX systems -- including most VAXstation, MicroVAX, and VAX 4000A   series -- it is typically interpreted as a HALT.  Alpha systems C   will also often process a BREAK in a similar fashion, halting the 	   system.   @   There is no uniform or generally-available way to disable thisA   behaviour on every VAX or Alpha system.  On some systems, BREAKlA   processing can be disabled in favor of [CTRL/P], or [CTRL/P] is2%   the only way to halt the processor.-  C   The most common way to avoid these halts is to disable the serialiA   line console or to simply not power-cycle the console terminal.aG   There is certain important system state information that is displayediC   only on the console, OpenVMS expects to always have access to thev   system console.      Also see MGMT5.'  < ------------------------------------------------------------? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?s  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 otheruD 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.,n& 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 bemH 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 theoK DEC 2000 (DECpc 150 AXP), an AlphaServer series, an AlphaStation series, or E more recent Alpha system, it will probably  work with a PC peripheral1H 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]     K Software Integrators sells a video adapter card called Gemini P1 which willsI drive many of the older Compaq (DIGITAL-logo) fixed-frequency monitors ona 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.   ? This will allow PC Multisync monitors with the needed frequencyeC specifications to be used with the VAXstations.  It may work with ap> 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 Manual)F (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.      Also see SUPP5  < ------------------------------------------------------------A SUPP5.  Which video monitor works with which graphics controller?   K   To determine the answer to the "will this video monitor or this LCD panel I   work with this graphics controller?" question, please first locate the  H   resolution(s) and the frequencies that are possible/supported at both J   ends of the video cable (on the display and on the graphics controller, I   in other words), and then determine if there are any matching settings aH   available.  If there are multiple matches, you will need to determine /   which one is most appropriate for your needs.t  M   You will also need to determine if the video monitor or graphics controllereL   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:x       http://www.repairfaq.org/e"     http://www.mirage-mmc.com/faq/H     http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html2     http://saturn.tlug.org/sunstuff/ffmonitor.html/     http://hawks.ha.md.us/hardware/monitor.html      Also see SUPP4.d  < ------------------------------------------------------------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 information / on SCSI, device jumpers, etc., is available at:      http://theref.aquascape.com/  < ------------------------------------------------------------< SUPP7.  Problem - My LK401 keyboard unexpectedly autorepeats  # There are several modes of failure:   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 beingrL    initialized.  Pressing ^F2 several times or unplugging and replugging theK    keyboard frequently fix this problem.  There is a patch available to fix J    this problem [contact the CSC for information - a CSCPAT number will be'    included here when available. - Ed.]i  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]f  < ------------------------------------------------------------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 beoF 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]d1                                         [inazu_k]   < ------------------------------------------------------------= SUPP9.  Which DE500 variant works with which OpenVMS version?   E   Ensure you have a version of the Alpha SRM console with support for H   the DE500 series device.  Apply ALL mandatory ECO kits for the OpenVMSF   version in use, and also apply the CLUSIO, ALPBOOT, and ALPLAN kits,:   and apply any available ALPCPU ECO kit for the platform.  
   DE500-XA'    auto-detection, no auto-negotiation, @    OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 and later and ECO,    Device hardware id 02000011 and 02000012.$    Component part number 54-24187-01  
   DE500-AA$    auto-detection, auto-negotiation,F    OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1 and later and ECO,    Device hardware id 02000020 and 20000022.$    Component part number 54-24502-01  
   DE500-BA$    auto-detection, auto-negotiation,C    OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and ALPCPU ECOs, oro      V7.1-1H1 or later and ECO.n=    Device hardware id 02000030 (check connector, vs DE500-FA) -      (other values on old Alpha SRM firmware) $    Component part number 54-24602-01  -   DE500-FA (100 megabit fibre optic Ethernet)      OpenVMS V7.1-1H1 and later>     Device hardware id 02000030 (check connector, vs DE500-BA)7       (other values possible on old Alpha SRM firmware)r%     Component part number 54-24899-01   G   To check the DE500 device hardware id from OpenVMS, use the following 
   command:       $ ANALYZE/SYSTEM     SDA> SHOW LAN/DEVICE=EWcu:  &   The "hardware id" will be displayed.  H   To set the DE500 speed via the Alpha SRM console environment variable:  &    EWx0_MODE setting           Meaning?    --------------------------  -------------------------------- 9    Twisted-Pair                10 Mbit/sec, nofull_duplex 7    Full Duplex, Twisted-Pair   10 Mbit/sec, full_duplexf9    AUI                         10 Mbit/sec, nofull_duplex 9    BNC                         10 Mbit/sec, nofull_duplex :    Fast                        100 Mbit/sec, nofull_duplex8    FastFD (Full Duplex)        100 Mbit/sec, full_duplex=    Auto-Negotiate              Negotiation with remote devicet  0   To override the console setting and use LANCP:       $ RUN SYS$SYSTEM:LANCP      LANCP> SET DEV EWA0/SPEED=10-     LANCP> SET DEV EWA0/SPEED=100/full_duplexe  K   Fast Ethernet (100Base, 100 megabit) controllers such as the DE500 seriesaM   have a pair of connections available -- while traditional Ethernet (10Base,nH   10 megabit) is inherently a half-duplex protocol, Fast Ethernet can beJ   configured to use one or both of the available connections, depending onK   the controller.  Fast Ethernet can thus be half- or full-duplex dependinglI   on the configuration and the capabilities of the network controller and-F   the Ethernet network plant.  Some Fast Ethernet controllers can alsoJ   operate at traditional Ethernet speeds, these controllers are thus often,   refered to as 10/100 Ethernet controllers.    < ------------------------------------------------------------< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?  3   Both of these controllers are Ultra2 low-voltage e&   differential (LVD) SCSI controllers.  < ------------------------------------------------------------, SCSI2.  Resolving DRVERR fatal device error?  =   If this is on an OpenVMS version prior to V6.2, please see -;   the AWRE and ARRE information included in section MISC21.a    < ------------------------------------------------------------- WIRES1. Looking for connector wiring pinouts?t   DECconnect DEC-423 MMJ pinout:     1: Data Terminal Ready (DTR)   2: Transmit (TXD)D   3: Transmit Ground (TXD-)a   4: Receive Ground (RXD-)   5: Receive (RXD)   6: Data Set Ready (DSR)s      +------------------+D    | 1  2  3  4  5  6 |-    +------------+    ++-                 +____+    / The PC-compatible DB9 connector pinout follows:s     1: Data Carrier Detect (DCD)   2: Received Data   3: Transmit Data   4: Data Terminal Ready (DTR)   5: Ground0   6: Data Set Ready (DSR)    7: Request To Send (RTS)   8: Clear To Send
   9: floatingK  C The MicroVAX DB9 console connector pinout predates the PC-style DB9oD pinout, and uses a then-common (older) standard pinout, and uses the# following EIA-232-standard signals:      1: Protective Ground   2: Transmited Data   3: Received Data   4: Request To Send (RTS)   5: Data Terminal Ready (DTR)   6: Data Set Ready (DSR)    7: Signal Ground8   8: Shorted to pin 9 on MicroVAX and VAXstation 2000...3   9:    ...series systems, otherwise left floating.   E   When pin 8 is shorted to pin 9, this is a BCC08 (or variant) cable.1  = The BC16E-nn (where -nn indicates the cable length) cable key6< impliicitly "flips over" (crosses-over) the signal wires, so1 all DECconnect MMJ connectors are wired the same.   
            // :            ----                                       ----:            |  |---------------------------------------|  |:            ----                                       ----:                                                         \\  0 The BC16-E-nn cross-over wiring looks like this:  ;             Terminal                                   HostA:             MMJ                                        MMJ  =          DTR 1 --->-------------->----------------->--- 6 DSRV=          TXD 2 --->-------------->----------------->--- 5 RXD09              3 ---------------------------------------- 4 9              4 ---------------------------------------- 30=          RXD 5 ---<--------------<-----------------<--- 2 TXD0=          DSR 6 ---<--------------<-----------------<--- 1 DTR0     The BN24H looks like this:            MMJ       RJ457             1---------87           2---------27           3---------17           4---------35           5---------6A           6---------77   The BN24J looks like this:            MMJ       RJ45              1---------72           2---------6            3---------3            4---------1            5---------2            6---------8n  	 Also see:-  4  http://www.openvms.compaq.com/wizard/padapters.html%  http://www.airborn.com.au/rs232.html?   http://www.stanq.com/cable.html)  For adapters and connectors, see WIRES2.   9                                         [Stephen Hoffman]-7                                         [Mike Thompson]h6                                         [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 hasSC the 8-9 short, see WIRES1) and the H8571-D for use with DECconnect.4  G More recent Compaq (Compaq or DIGITAL logo) systems will use either theeI DECconnect MMJ wiring or (on all recent system designs) the PC-compatible- DB9 pinout.-   DECconnect MMJ adapters:  3     Part:      Converts BC16E MMJ male to fit into:w  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) h5     H8575-B  EIA232 9 pin male (MicroVAX II console) n4     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 as ' descriptions of the above-listed parts.n  J The H8571-A and H8575-A are MMJ to DB25 (female) and are wired as follows:  	 Also see:e4  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.a  9                                         [Stephen Hoffman] 6                                         [Eric Dittman]  < ------------------------------------------------------------2 WIRES3. What is flow control and how does it work?  % XON/XOFF is one kind of flow control.   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 that + the flow control is mixed in with the data.n  I CTS/RTS is another type of flow control, and is sometimes called hardwareoG flow control.  Out-of-band means that seperate lines/pins from the data 3 lines (pins) are used to carry the CTS/RTS signals.o  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 fullmE and data is lost.  Later, after a sufficient amount of the receiver's E buffer is freed up, the resume flow control signal is sent to get ther 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, E and drivers) *must not* be configured for XON/XOFF flow control.  ThehD incidence of these (unexpected) in-band characters will corrupt dataG packets.  Further, the serial line device drivers might normally removeyF the XON and XOFF characters from the stream for terminal applications,E but DECnet configures the driver to pass *all* characters through andnF 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 compressioniG is happening, it must reproduce the source stream exactly.  No additionn> or elimination of null characters, and full data transparency.  I An Ethernet network is rather different than an asynchronous serial line.dE Ethernet specifies the control of data flow on a shared segment usingeB 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 transmitoJ by asserting a carrier and encoding the packet appropriately.  The stationG concurrently listens to its own signal, to permit the station to detecteG if another station began to transmit at the same time -- this is calledwJ 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 beginningrG to establish a transmit window size -- and a transmitter will only sendiG that much data before stopping and waiting for an acknowledgement.  The G acknowledgement is only sent when the receiver has confirmed the packetnD is valid.  (A well-configured DECnet generally avoids triggering any1 underlying (out-of-band) flow control mechanism.)c=                                                [David Rabahy]   < ------------------------------------------------------------. NET1.  How to connect OpenVMS to the Internet?  A Some tutorial information and tips for connecting OpenVMS systemso! to the Internet are available at:   !   http://www.tmesis.com/internet/   < ------------------------------------------------------------) NET2.  How to connect OpenVMS to a Modem?t  <   http://www.openvms.compaq.com/wizard/ topics (81), (1839),   (2177), (3605), etcr   [End of Part 5/5]   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 2 Oct 2001 13:46:34 -0500h- From: Kilgallen@SpamCop.net (Larry Kilgallen)h+ Subject: Re: OpenVMS, Apache and hackers... 3 Message-ID: <qyWdiWud8WrZ@eisner.encompasserve.org>V  h In article <d7791aa1.0110020933.4d659580@posting.google.com>, bob@instantwhip.com (Bob Ceculski) writes:  M > i know palmer and capellas and all the other brilliant (cough! cough!) ceoseQ > of the past tied your hands on various vms projects as many in software support-P > have told me ... but purveyor would have been a lot better product than apacheK > from my experiences ... true apache is more popular but is popular alwayst > better (can anyone say IIS)?  < Popular sells.  With WASD and OSU servers already available,8 VMS needed something with a "brand name".  Apache is it.7 Personally I think there are lots of better programmingl6 languages than Perl, but adopting Apache forced Compaq4 to put effort into the _standard_ languages for CGI.3 This makes it easier to switch your web server from 2 some other operating system to VMS.  That is good.   ------------------------------  % Date: Tue, 02 Oct 2001 22:09:56 +0200t2 From: martin@radiogaga.harz.de (Martin Vorlaender)+ Subject: Re: OpenVMS, Apache and hackers... ; Message-ID: <3bba1f14.524144494f47414741@radiogaga.harz.de>o  . Larry Kilgallen (Kilgallen@SpamCop.net) wrote:, > bob@instantwhip.com (Bob Ceculski) writes:* > > ... but purveyor would have been a lotJ > > better product than apache from my experiences ... true apache is more> > > popular but is popular always better (can anyone say IIS)? > > > Popular sells.  With WASD and OSU servers already available,: > VMS needed something with a "brand name".  Apache is it.   IMHO, it's not only popularity.m  ) Apache's modular approach has its merits.c6 Current example (or better, slightly future panorama):  B Tired of CodeRed and Nimda requests filling your Apache log files?C Some guy has written a mod_rewrite "program" which sorts those out.-@ That means, as soon as CSWS 1.2 appears, you can have it on VMS.  9 > Personally I think there are lots of better programmingM8 > languages than Perl, but adopting Apache forced Compaq6 > to put effort into the _standard_ languages for CGI.5 > This makes it easier to switch your web server from/4 > some other operating system to VMS.  That is good.  N It's amazing what hooks Apache provides - using mod_perl and Apache::Registry,K you can program with Perl right in the bowels of the webserver. And this isaG not an individual case: there are *lots* of Apache:: modules available.o  B I wouldn't want to live on an isolated software island; would you?   cu,C   Martin -- dD                         | Martin Vorlaender  |  VMS & WNT programmer1  VMS is today what      | work: mv@pdv-systeme.deeE  Microsoft wants        |    http://www.pdv-systeme.de/users/martinv/ 8  Windows NT 8.0 to be!  | home: martin@radiogaga.harz.de   ------------------------------  $ Date: Tue, 2 Oct 2001 16:23:52 -0400+ From: "Rick Barry" <barry@star.zko.dec.com>n+ Subject: Re: OpenVMS, Apache and hackers...i1 Message-ID: <Qmpu7.951$YP.25644@news.cpqcorp.net>h  5 "Bob Ceculski" <bob@instantwhip.com> wrote in messaget7 news:d7791aa1.0110020556.1ef9da25@posting.google.com...c8 > "Rick Barry" <barry@star.zko.dec.com> wrote in message- news:<_b3u7.884$YP.24054@news.cpqcorp.net>...i9 > > "Bob Ceculski" <bob@instantwhip.com> wrote in messageE; > > news:d7791aa1.0109300827.7393e183@posting.google.com... > > > > Michael Austin <miaustin@bellsouth.net> wrote in message. > >  news:<3BB60C15.94A3B64D@bellsouth.net>... [snip] > E > rick, has the broken pipe problem killing apache when using tcpware-F > or multinet fixed yet ... we tried apache under tcpware and ended upE > having to restart every 5 minutes ... not good ... and i have heardoC > nothing from compaq or process that says it has been resolved ...e  F As far as I know, there are no open issues with CSWS running on eitherD TCPware of Multinet. If any problems do pop up, we work with Process Software to correct them.n  B Regarding the OPER privilege, there is no requirement for elevatedG privileges to run CGI scripts. There may have been a kink or two in the L original release of Apache 1.3.x, but as far as CSWS versions are concerned,# you should need only TMPMBX/NETMBX.P  F One of the reasons we chose Apache was its popularity, in terms of itsL community of open source developers, web developers, and web administrators.K It has been tremendously popular with our customers and ISVs. That's not to I say that Purveyor doesn't do its job well. It's a successful product, but L business reasons made us move in the direction of Apache and it's worked outJ very well. If you're happy with Purveyor, then by all means stick with it.  H >have told me ... but purveyor would have been a lot better product than apacheJ >from my experiences ... true apache is more popular but is popular always >better (can anyone say IIS)?a  0 That's a good one. Did you hear the one about...  
 Rick Barry CSWS Project Teamb Compaq Computer Corporation 
 Nashua, NH   ------------------------------  % Date: Tue, 02 Oct 2001 16:41:40 -0400n- From: Michael Austin <miaustin@bellsouth.net>E+ Subject: Re: OpenVMS, Apache and hackers...o- Message-ID: <3BBA2683.5732798E@bellsouth.net>l   Larry Kilgallen wrote:  j > In article <d7791aa1.0110020933.4d659580@posting.google.com>, bob@instantwhip.com (Bob Ceculski) writes: >tO > > i know palmer and capellas and all the other brilliant (cough! cough!) ceosvS > > of the past tied your hands on various vms projects as many in software support R > > have told me ... but purveyor would have been a lot better product than apacheM > > from my experiences ... true apache is more popular but is popular always   > > better (can anyone say IIS)? >5> > Popular sells.  With WASD and OSU servers already available,: > VMS needed something with a "brand name".  Apache is it.9 > Personally I think there are lots of better programming 8 > languages than Perl, but adopting Apache forced Compaq6 > to put effort into the _standard_ languages for CGI.5 > This makes it easier to switch your web server from 4 > some other operating system to VMS.  That is good.  f ...to the point that I have dropped unix-developed Perl Code into my apache environment and had it run correctly.  Pretty cool.   Michael Austin' Rdb/Oracle DBA Consultant... need one??d   ------------------------------  % Date: Tue, 02 Oct 2001 16:44:06 -0400C- From: Michael Austin <miaustin@bellsouth.net>A+ Subject: Re: OpenVMS, Apache and hackers...1- Message-ID: <3BBA2716.64DBC126@bellsouth.net>5   Martin Vorlaender wrote:  0 > Larry Kilgallen (Kilgallen@SpamCop.net) wrote:. > > bob@instantwhip.com (Bob Ceculski) writes:, > > > ... but purveyor would have been a lotL > > > better product than apache from my experiences ... true apache is more@ > > > popular but is popular always better (can anyone say IIS)? > >n@ > > Popular sells.  With WASD and OSU servers already available,< > > VMS needed something with a "brand name".  Apache is it. >r! > IMHO, it's not only popularity.l >h+ > Apache's modular approach has its merits.n8 > Current example (or better, slightly future panorama): >-D > Tired of CodeRed and Nimda requests filling your Apache log files?E > Some guy has written a mod_rewrite "program" which sorts those out.rB > That means, as soon as CSWS 1.2 appears, you can have it on VMS. >-  N Yea,  I am up to 25,000 in the last 2-3 weeks.  Having a dynmic IP helps as it resets every once in a while.t   Michael Austin   >r; > > Personally I think there are lots of better programmingt: > > languages than Perl, but adopting Apache forced Compaq8 > > to put effort into the _standard_ languages for CGI.7 > > This makes it easier to switch your web server fromn6 > > some other operating system to VMS.  That is good. >DP > It's amazing what hooks Apache provides - using mod_perl and Apache::Registry,M > you can program with Perl right in the bowels of the webserver. And this is I > not an individual case: there are *lots* of Apache:: modules available.  >nD > I wouldn't want to live on an isolated software island; would you? >a > cu,:
 >   Martin > --F >                         | Martin Vorlaender  |  VMS & WNT programmer3 >  VMS is today what      | work: mv@pdv-systeme.defG >  Microsoft wants        |    http://www.pdv-systeme.de/users/martinv/l: >  Windows NT 8.0 to be!  | home: martin@radiogaga.harz.de   ------------------------------  # Date: Wed, 03 Oct 2001 04:37:33 GMT - From: "Richard L. Dyson" <rickdyson@home.com>a? Subject: Problem With VMS Backup Save-Set Spanning Tape Volumes:( Message-ID: <3BBA960B.C0B951B6@home.com>  M I have been asked to lend a hand in trying to restore some data from a multi-tG tape DAT backup (4 volumes I believe) where we may have a spot part wayi through  tape #1 that can't be read.C  G Is it going to be possible to plow through the bad spot and continue ons throughr5 the other 3 tapes, etc.?  Or will we just be screwed?n  L I don't actually have any hard details yet, just a phone conversation asking for L assistance. :)  I have not had this kind of bad luck myself, so I don't have any N first hand experience on whether or not we can get much from the tapes or not.  M Anyone else been there?  So far, I just know it was a VAX-based system with ae- 120m DAT drive and 4 tapes in the save-set...   . Is this a topic covered in any of the manuals?   Rick   ------------------------------  % Date: Tue, 02 Oct 2001 20:54:55 -0400-- From: JF Mezei <jfmezei.spamnot@videotron.ca>-' Subject: Public domain VMS clustering ? , Message-ID: <3BBA61DC.3E3A4756@videotron.ca>  M Hoff said something interesting in another thread about building applications-J with a generic layer for inter-process communications to allow for changes6 over time (was discussin how event flags have limits).  L This got me to think. Wouldn't it be great is some of the VMS specific stuffO were to become "public domain" and used by the industry as de-facto standards ?   I For instance, what if the SCS protocols, including the ICC (intra cluster L comms) were to become available to anyone, in the same way as Java, wouldn'tK it eventually allow clusters to be formed with multiple different operatings	 systems ?t  L Imagine if IBM were to adopt the VMS clustering protocols, and you'd be ableL to cluster a VMS system with an MVS system or integrate a Sun cluster with a VMS cluster.  L It would bring VMS into the limelight and outline the fact that VMS is still the leader in clustering.m   ------------------------------  # Date: Wed, 03 Oct 2001 03:16:03 GMT-3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk> + Subject: Re: Public domain VMS clustering ?r/ Message-ID: <3BBA8295.DCD9844A@cableinet.co.uk>0   JF Mezei wrote:  > O > Hoff said something interesting in another thread about building applications(L > with a generic layer for inter-process communications to allow for changes8 > over time (was discussin how event flags have limits). > N > This got me to think. Wouldn't it be great is some of the VMS specific stuffQ > were to become "public domain" and used by the industry as de-facto standards ?C  D Wasn't the Sun Fortran compiler's compatibility with VAX fortran non	 stantdard H extensions one of the reasons they (Sun) cleaned up in academia a decade
 or more back?t  * Anyway, did you look at any NT internals?    > K > For instance, what if the SCS protocols, including the ICC (intra cluster N > comms) were to become available to anyone, in the same way as Java, wouldn'tM > it eventually allow clusters to be formed with multiple different operatingl > systems ?n > N > Imagine if IBM were to adopt the VMS clustering protocols, and you'd be ableN > to cluster a VMS system with an MVS system or integrate a Sun cluster with a > VMS cluster.  C well, I guess Tru64 and linux and HP/UK would be a step forward, ton demonstrate the possibilities.# But then, why not keep it in house.    > N > It would bring VMS into the limelight and outline the fact that VMS is still > the leader in clustering.D  4 Wouldn't some decent marketting be more appropriate?   regards  -- S Tim.Llewellyn@cableinet.co.uk  s  C Standard disclaimer applies. My views in no way represent those of  ! my employers or service provider.E   ------------------------------  $ Date: Tue, 2 Oct 2001 22:25:44 -04003 From: "Brad McCusker" <Brad.McCuskerSP@Mcompaq.com>?  Subject: Re: PWIP does not start1 Message-ID: <HLuu7.970$YP.25590@news.cpqcorp.net>,  , Ditto Peter's statements about two postings.  ; See my statements over in vmsnet.networks.desktop.pathworksuJ which predict that you need to define PWRK$KNBDAEMON_DEVICE, and, I'll bet it needs to beI defined to EIA0:, but, I'll leave it to you to determine which device youe want to use....o    + "Mike" <janicmx@yahoo.com> wrote in messagel7 news:31886a6f.0110012209.1eb62f16@posting.google.com...t@ > OpenVMS 7.2-1, Pathworks 6.0D, TCPIP 5.0A-ECO3  on Alpha 4100: > G > PWRK$ROOT:[LOGS]PWRK$KNBDAEMON_host.LOG contains the following lines:p > & >   bind_a_port(137): t_bind failed: 8 >   Port binding failedf >  > Any help/idea ?  >f > TIA, Mikea   ------------------------------   Date: 2 Oct 2001 20:52:23 -0700r From: janicmx@yahoo.com (Mike)  Subject: Re: PWIP does not start= Message-ID: <31886a6f.0110021952.476f06c2@posting.google.com>o   My NIC is DE500.   Tx, Mikes "Jean-Fran?is Marchal" <jean-francois.marchal@x9000.fr> wrote in message news:<9pcgh3$bpe$1@reader1.imaginet.fr>... ' > What is your network interface card ?c: > If you don't know, what is its name in a $ SHOW DEVICE ? >  > Jean-Franois Marchala > X9000 - LYON (FR)  > : > "Mike" <janicmx@yahoo.com> a crit dans le message news:4 > 31886a6f.0110012209.1eb62f16@posting.google.com...B > > OpenVMS 7.2-1, Pathworks 6.0D, TCPIP 5.0A-ECO3  on Alpha 4100: > >cI > > PWRK$ROOT:[LOGS]PWRK$KNBDAEMON_host.LOG contains the following lines:t > >N( > >   bind_a_port(137): t_bind failed: 8 > >   Port binding failed8 > >c > > Any help/idea ?o > >s
 > > TIA, Mikei   ------------------------------  # Date: Tue, 02 Oct 2001 18:54:08 GMTa3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk> " Subject: Re: Question on VMS Virus/ Message-ID: <3BBA0CF3.66612CAB@cableinet.co.uk>t   "Doc.Cypher" wrote:o  a > L > I wouldn't mind a copy of the source code for the worm to see if it really0 > was as poorly constructed as the book implies.  t> I know someone who might still have a hardcopy listing (it was print/deleted).aC Might just run into them sometime soon too. Will see. Probably bestnF forgotten however. I remember the anti-dote was pretty simple, it usedC a hardcoded file name rather than a logical to snoop for usernames.t  r -- t Tim.Llewellyn@cableinet.co.uk  e  C Standard disclaimer applies. My views in no way represent those of h! my employers or service provider.n   ------------------------------  # Date: Tue, 02 Oct 2001 21:44:22 GMT 6 From: "Andy Bustamante" <a_c_bustamante@earthlink.net> Subject: Re: Quota SettingF Message-ID: <Wyqu7.14196$b66.1258481@newsread1.prod.itd.earthlink.net>  G Ask the process nicely how much it needs.  See " help lex F$GETJPI" fornL details.  I started life as sys$examples:working_set.com and I've tweaked itI slighty.  One of these days I will get around to cleaning this up but forr now:     $ SET NOVERh1 $!      CHECK_IMG.COM                   ACB 12/95h $!K $!      THIS COMBINES THE FUNCTIONALLITY OF "BCK PROC /WARN /WORK AND /VIRTrI $!      FOR .IMG FILE TUNING AS WELL AS ADDING SYSGEN PARAMETER CHECKING. 1 $!      WARNINGS ARE GENERATED WHERE APPROPRIATE. : $!      THIS WILL CHECK IMAGES WITH YOUR LOGIN GROUP ONLY. $! $ WRITE SYS$OUTPUT ""  $!@ $!                                              ! GET SYS PARAMSC $   DEFINE SYS$OUTPUT PHNX$TEMP:CHECK_IMG.TMP_'F$GETSYI("SCSNODE")'p= $   CITY_UIC = F$GETJPI ("","GRP")              ! LOGIN GROUP-* $   SYSVIRT  = F$GETSYI ("VIRTUALPAGECNT")  $   SYSWSMAX = F$GETSYI("WSMAX")B $ TOP:                                          ! GET PROCESS INFO $     PID = F$PID (LIST_PTR) $     GRP = F$GETJPI(PID,"GRP")-G $!   IF GRP .NES. 'CITY_UIC' THEN GOTO TOP      ! PROCESS MATCHES LOGIN  GROUP?1 $   IF PID .EQS. "" THEN GOTO PROC_TAF          !  $!< $      PRCNAM   = F$FAO ("!15AS",  F$GETJPI (PID, "PRCNAM"))' $      IF PRCNAM .EQS. "" THEN GOTO TOPl' $      ENQLM    = F$GETJPI(PID,"ENQLM")d) $      ENQCNT   = F$GETJPI (PID,"ENQCNT")n' $      ASTLM    = F$GETJPI(PID,"ASTLM")9) $      ASTCNT   = F$GETJPI (PID,"ASTCNT")>) $      WSDEFAULT= F$GETJPI(PID,"DFWSCNT"):) $      WSQUOTA  = F$GETJPI(PID,"WSQUOTA")e* $      WSEXTENT = F$GETJPI(PID,"WSEXTENT")( $      WSSIZE   = F$GETJPI(PID,"WSSIZE")( $      WSPEAK   = F$GETJPI(PID,"WSPEAK")* $      VIRTPEAK = F$GETJPI(PID,"VIRTPEAK")+ $      PGFLQUOTA= F$GETJPI(PID,"PGFLQUOTA")x, $!      GLOBALPAGES = F$GETJPI(PID,"GPGCNT")- $!      PROCESSPAGES = F$GETJPI(PID,"PPGCNT")S- $!      PAGEFAULTS = F$GETJPI(PID,"PAGEFLTS") , $!      PAGES   = GLOBALPAGES + PROCESSPAGES $!= $     LSTRING = F$FAO ("!#(5UW)",4,ENQLM,ENQCNT,ASTLM,ASTCNT)fE $     WSTRING = F$FAO ("!#(7UL)",5,WSDEFAULT,WSQUOTA,WSEXTENT,WSSIZE,o WSPEAK)p7 $     VSTRING = F$FAO (" VIRT PEAK:!#(8UL)",1,VIRTPEAK)k) $     IMGLIM = (VIRTPEAK*100) / PGFLQUOTA ' $     SYSLIM = (VIRTPEAK*100) / SYSVIRTa& $     WSIMG  = (WSPEAK*100) / WSEXTENT& $     WSSYS  = (WSPEAK*100) / SYSWSMAX4 $     VPIMG = F$FAO ("  VIRT IMG%:!#(4UW)",1,IMGLIM)4 $     VPSYS = F$FAO ("  VIRT SYS%:!#(4UW)",1,SYSLIM)< $!     GBLPAGES = F$FAO(" |GBL PAGES:!#(8UL)",1,GLOBALPAGES)A $!     PROCPAGES =   F$FAO(" |PROC PAGES:!#(8UL)",1,PROCESSPAGES)o9 $!     TOTPAGES =  F$FAO(" |TOTAL PAGES:!#(8UL)",1,PAGES)e $     IWARNING = "        "t $     SWARNING = ""p* $   IF WSIMG .GE. 90 .OR. IMGLIM .GE. 95 -"         THEN IWARNING = "  *IMG* "* $   IF WSSYS .GE. 90 .OR. SYSLIM .GE. 90 -"         THEN SWARNING = "  *GEN* " $,; $  WRITE SYS$OUTPUT PRCNAM , LSTRING, WSTRING, IWARNING,  - :                     VSTRING, VPIMG, VPSYS, "    ",SWARNING $  GOTO TOPe $! $ PROC_TAF:x $   DEASSIGN SYS$OUTPUTy7 $   SORT PHNX$TEMP:CHECK_IMG.TMP_'F$GETSYI("SCSNODE")'- 6          PHNX$TEMP:CHECK_IMG.TMP_'F$GETSYI("SCSNODE")' $! $!# $   NOW = F$EXTRACT (0,17,F$TIME())  $   WRITE SYS$OUTPUT ""W3 $   WRITE SYS$OUTPUT "   ", F$trnlnm("PHNX$CITY"),-y= "                                                       ",NOWn $   WRITE SYS$OUTPUT ""e $   WRITE SYS$OUTPUT -H "                ---ENQ--- ---AST--- -----------WORKING SET------------" $ WRITE SYS$OUTPUT -F "PROCESS         LIM  FREE LIM  FREE  DEF   QUOTA  EXTENT  SIZE   PEAK WARN"a $ WRITE SYS$OUTPUT -L "--------------- ---- ---- ---- ---- ------ ------ ------ ------ ------ ---- ---" $! $!; $ OPEN REPORT PHNX$TEMP:CHECK_IMG.TMP_'F$GETSYI("SCSNODE")'  $ RPT_LOOP:c" $   READ /ERROR=TAF REPORT RPTLINE- $   WRITE SYS$OUTPUT F$EXTRACT (0,78,RPTLINE) A $   WRITE SYS$OUTPUT "               ", F$EXTRACT (78,67,RPTLINE)n $   WRITE SYS$OUTPUT ""  $  GOTO RPT_LOOP $! $ TAF:= $  SYSWSMAX =  F$FAO ("WORKING SET MAX: !#(8UL)",1, SYSWSMAX)h; $  SYSVIRT =   F$FAO ("VIRTUALPAGECNT:  !#(8UL)",1,SYSVIRT)bD $  SYSGBLPAGES = F$FAO ("GBLPAGES: !#(8UL)",1, F$GETSYI("GBLPAGES"))G $  SYSGBLPAGFIL = F$FAO ("GBLPAGFIL: !#(8UL)",1, F$GETSYI("GBLPAGFIL"))z $  WRITE SYS$OUTPUT -R& "-------------------------------SYSGEN) PARAMETERS------------------------------"t$ $  WRITE SYS$OUTPUT  "   ", SYSWSMAXL $  WRITE SYS$OUTPUT  "   ", SYSVIRT, "   ", SYSGBLPAGES, "   ", SYSGBLPAGFIL $  WRITE SYS$OUTPUT "" $  WRITE SYS$OUTPUT -tL "--------------------------------------------------------------------------- ---" $  WRITE SYS$OUTPUT -e?   "*IMG* - WSPEAK >= 90% WSEXT OR VIRT PEAK IS >= 95% PGFLQUOTAe (ILOAD)" $  WRITE SYS$OUTPUT -iD   "*GEN* - WSPEAK >= 90% WSMAX OR VIRT PEAK IS >= 90% VIRTUALPAGECNT	 (SYSGEN)"t $ WRITE SYS$OUTPUT -L "--------------------------------------------------------------------------- ---" $  CLOSE REPORTi6 $  PURGE PHNX$TEMP:CHECK_IMG.TMP_'F$GETSYI("SCSNODE")' $  WRITE SYS$OUTPUT "" $ EXIT     -- Andy Bustamanteo Remove the ASCII 95s to replya      ) <paul.beaudoin@hsbc.com> wrote in messagen? news:OF5B13F196.251D22D7-ON80256AD9.0044AD36@systems.uk.hsbc...  >MK > After many years of managing my own home VMS system and working with real H > system managers and following the 'quota rule of thumb' (if it doesn'tK > work, make it bigger) I have been asked for a more scientific approach to L > setting quotas. The simple question of why do you set any particular quota@ > to any particular setting seems to involve more dead chickens, incantationsJ > and  black magic than the rest of VMS.  Surely the best OS on the planet isE > not ultimately dependant on (un)educated guesswork! Any pointers to C > educational materials, cookbooks or even just good advice is mostj > gratefully received. >p > Thanks >  > Paul >a >s >d >sF > ********************************************************************D >  This message and any attachments are confidential to the ordinaryD >  user of the e-mail address to which it was addressed and may also@ >  be privileged. If you are not the addressee you may not copy,: >  forward, disclose or use any part of the message or itsE >  attachments and if you have received this message in error, pleaseoD >  notify the sender immediately by return e-mail and delete it from >  your system.0 >c? >  Internet communications cannot be guaranteed to be secure ornC >  error-free as information could be intercepted, corrupted, lost,2@ >  arrive late or contain viruses. The sender therefore does notA >  accept liability for any errors or omissions in the context ofwA >  this message which arise as a result of Internet transmission.a >aE >  Any opinions contained in this message are those of the author and @ >  are not given or endorsed by the HSBC Group company or office> >  through which this message is sent unless otherwise clearlyB >  indicated in this message and the authority of the author to so5 >  bind the HSBC entity referred to is duly verified.S > F > ******************************************************************** >e   ------------------------------  # Date: Tue, 02 Oct 2001 18:09:00 GMTt- From: goathunter@goatley.com (Hunter Goatley)e Subject: Re: Ram Disk for VMS?0 Message-ID: <3bba028f.57287875@news.process.com>  N On 2 Oct 2001 06:17:52 -0700, ratkinson@tbs-ltd.co.uk (Robert Atkinson) wrote:  u >rcyoung@aliconsultants.com (Robert Young) wrote in message news:<91437ce6.0110011926.2902d555@posting.google.com>...aG >> Isn't there some "free" Ram disk software for OpenVMS...maybe on thetF >> freeware cd or in a utility directory?? I keep thinking I have seenG >> something somewhere....but I am getting old and feeble minded and doi# >> not know where I saw it anymore!O >V >There is a RanDriver atG >ftp://ftp.process.com/vms-freeware/fileserv/ramdriver.zip but It lookst& >like it has not been ported to Alpha. >nE Correct.  AFAIK, no free RAM driver has been ported from VAX to AlphauA (there were a couple of other VAX RAM drivers out there, but I'vefK forgotten the names).  The driver above is the one I used way back when....y   Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/e9 goathunter@goatley.com     http://www.goatley.com/hunter/b   ------------------------------  # Date: Tue, 02 Oct 2001 19:33:33 GMT - From: goathunter@goatley.com (Hunter Goatley)u Subject: Re: Ram Disk for VMS?0 Message-ID: <3bba1658.62352317@news.process.com>  P On Tue, 02 Oct 2001 18:09:00 GMT, goathunter@goatley.com (Hunter Goatley) wrote:  F >Correct.  AFAIK, no free RAM driver has been ported from VAX to AlphaB >(there were a couple of other VAX RAM drivers out there, but I'veL >forgotten the names).  The driver above is the one I used way back when.... >iD Glenn Everhart reminded me of his drivers that do this.  Here's what Glenn had to say:g  K >Actually, my frdriver or zrdriver (renamed it some times) that uses a host_M >process for things like remote disk, virtual disk on container file, virtualrK >disk on encrypted container, and various flavors of shadowing/journalling,aK >has a host that just builds a big array in its process space and uses that L >for a disk. Thus the actual storage is in memory, but the memory is part of >theL >host process, so the actual usage depends on working set. That was the hostJ >I first wrote to debug the thing, but it does work and I believe works on" >Alpha. Certainly the driver does.  M >The thing is NOT a speed demon since it copies data to/from user buffers viaoI >driver buffers and goes thru the entire startio to iopost rigamarole formH >every packet. For scratch storage though it could be moderately useful.L >There are times you don't want to be hitting a real disk when writing smallM >files, and since the thing is "just a process", it plays "nice" with all theaJ >other processes. That is, it really gets paged, really timeshares, and so >on.     Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/ 9 goathunter@goatley.com     http://www.goatley.com/hunter/p   ------------------------------  $ Date: Tue, 2 Oct 2001 21:58:31 +0200" From: "Hans Vlems" <hvlems@iae.nl> Subject: Re: Ram Disk for VMS?( Message-ID: <9pd670$n2s$1@news.IAEhv.nl>  8 It could be that you saw it in SYS$UPDATE:STABACKIT.COM.B That DCL procedure contains a very small driver (called PDDRIVER).K Extract the code (assembler) and look for the DCL immediately following thenC MACRO32 source because there you'll find the commands that you need ) to assemble, link and install the driver.AI This is tested on VAX only, I have no idea whether this works on AXP, buts I don't think so.e  
 Hans Vlems  : Robert Young <rcyoung@aliconsultants.com> wrote in message7 news:91437ce6.0110011926.2902d555@posting.google.com....F > Isn't there some "free" Ram disk software for OpenVMS...maybe on theE > freeware cd or in a utility directory?? I keep thinking I have seennF > something somewhere....but I am getting old and feeble minded and do" > not know where I saw it anymore!   ------------------------------  # Date: Tue, 02 Oct 2001 20:52:06 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)  Subject: Re: Ram Disk for VMS?0 Message-ID: <00A02EEB.084FAC36@SendSpamHere.ORG>  ` In article <3bba1658.62352317@news.process.com>, goathunter@goatley.com (Hunter Goatley) writes:Q >On Tue, 02 Oct 2001 18:09:00 GMT, goathunter@goatley.com (Hunter Goatley) wrote:l >lG >>Correct.  AFAIK, no free RAM driver has been ported from VAX to Alpha C >>(there were a couple of other VAX RAM drivers out there, but I'vedM >>forgotten the names).  The driver above is the one I used way back when....  >>E >Glenn Everhart reminded me of his drivers that do this.  Here's whath >Glenn had to say: >lL >>Actually, my frdriver or zrdriver (renamed it some times) that uses a hostN >>process for things like remote disk, virtual disk on container file, virtualL >>disk on encrypted container, and various flavors of shadowing/journalling,L >>has a host that just builds a big array in its process space and uses thatM >>for a disk. Thus the actual storage is in memory, but the memory is part ofp >>thecM >>host process, so the actual usage depends on working set. That was the hosthK >>I first wrote to debug the thing, but it does work and I believe works on # >>Alpha. Certainly the driver does." >lN >>The thing is NOT a speed demon since it copies data to/from user buffers viaJ >>driver buffers and goes thru the entire startio to iopost rigamarole forI >>every packet. For scratch storage though it could be moderately useful.kM >>There are times you don't want to be hitting a real disk when writing small N >>files, and since the thing is "just a process", it plays "nice" with all theK >>other processes. That is, it really gets paged, really timeshares, and sol >>on.t >e >r >Hunterm >------i: >Hunter Goatley, Process Software, http://www.process.com/: >goathunter@goatley.com     http://www.goatley.com/hunter/    K I took a look at GKN's RAMDRIVER again and it shouldn't be too much effort M? to port it to Alpha.  I'll take a stab at it if nobody objects.s --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             wJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesp   ------------------------------  $ Date: Tue, 2 Oct 2001 22:12:08 -0400  From: John Santos <JOHN@egh.com>E Subject: Re: RMS ISAM internals question: IRC$V_RU_UPDATE & RU_DELETE-6 Message-ID: <1011002220733.25191A-100000@Ives.egh.com>  ) On Tue, 2 Oct 2001, norm lastovica wrote:M   > one starting point:: >  > $ sea sys$share:lib.req IRC$Vu   [...].  A Thanks, Norm.  It didn't occur to me that there might be commentsg  in the system definitions files!   Use the source, Luke...o   -- h John Santosh Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Tue, 02 Oct 2001 23:00:31 GMTt2 From: "frank brown" <frank.brown@ci.seattle.wa.us> Subject: VAX SET BOOT doc?3 Message-ID: <jGru7.236$iH2.14537@news-west.eli.net>n  H OK I know it's a firmware question, it's not really VMS, but I'm gettingB frustrated searching the Q's online docs for this simple question:  K I need to set the default console value for R5 on my clustered VAX 4300s sofK auto-reboot will load correctly.  Is this done using SET BOOT or DEPOSIT or-  what?  An example would be cool.   -Frank Brown Seattle Fire Dept. http://www.inwa.net/~frog/   ------------------------------  # Date: Tue, 02 Oct 2001 23:58:34 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: VAX SET BOOT doc?1 Message-ID: <Kwsu7.966$YP.25674@news.cpqcorp.net>g  h In article <jGru7.236$iH2.14537@news-west.eli.net>, "frank brown" <frank.brown@ci.seattle.wa.us> writes:I :OK I know it's a firmware question, it's not really VMS, but I'm gettingaC :frustrated searching the Q's online docs for this simple question:. :6L :I need to set the default console value for R5 on my clustered VAX 4300s soL :auto-reboot will load correctly.  Is this done using SET BOOT or DEPOSIT or! :what?  An example would be cool.i  4   On the VAX 4000 model 300 series system console...  
   >>> HELP     >>> SET BFLG nnnns     >>> SET BOOT ddcu-     >>> SET HALT hhhh-  H   Where nnnn is the value to load into R5, and ddcu is the target deviceJ   for the default bootstrap.  hhhh is the halt action, typically set to 1 G   to boot on power up, to 2 to restart, and set to 3 to halt.  Various nH   MicroVAX systems will also accept keywords on SET HALT, such as HALT, G   RESTART, RESTART_REBOOT, and REBOOT.  HELP will generally tell you...s  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 02 Oct 2001 15:17:32 -0600s$ From: Lee Y T Mah <lytmah@cha.ab.ca> Subject: VMS 7.3 versus 7.2-2,) Message-ID: <3BBA2EEC.8B86A75F@cha.ab.ca>t  F I am looking at setting up a cluster with the following configuration:F   Data Center 1: Two ES40's and a SAN with two HSG80's supporting 47 x 36GB drives.F   Data Center 2: Two ES40's and a SAN with two HSG80's supporting 47 x 36GB drives.E   A quorum node, possibly located in either Data centre, or remote tod either data centre. B This cluster will gradually be brought into an existing production cluster of four AS1200's at F VMS 7.1-2, using HSJ40/50's and on CI/FDDI/Ethernet, with the eventual aim to drop the AS1200's.OC Can anyone with similar experience provide recommendations as which 1 version to use for the new cluster, 7.3 or 7.2-2?    TIA.   -- Lee   ; Lee Y T Mah                        Capital Health Authority ? Email: lytmah@cha.ab.ca            Information Systems, RAH CSCA4 Phone:  (780) 477-4725, 477-4233   10240 Kingsway NW? Fax:      (780) 491-5119, 491-5619    Edmonton, AB, CAN  T5H3V9    ------------------------------  $ Date: Tue, 2 Oct 2001 17:38:58 -0400  From: norm.raphael@jamesbury.com! Subject: Re: VMS 7.3 versus 7.2-2 4 Message-ID: <C2256AD9.0076A09B.00@jklh21.valmet.com>  / We are sort of having the same discussion here.T= It looks like you should go to the latest version V7.3 unless > you have an application or applications that are not qualified= on V7.3, but are qualified on V7.2, or you read the patch andN+ release notes for V7.2-2 and find a gotcha. 8 Remember that you can have no more than 2 version in anyA VMScluster at the same time, and different versions are supported A only for migration (you are supposed to get all nodes to the same"E version as soon as practical).  If you can be on the latest supportedJ! version you should be better off.         * lytmah@cha.ab.ca on 10/02/2001 05:17:32 PM  " Please respond to lytmah@cha.ab.ca   To:   Info-VAX@mvb.saic.comF cc:    ( Subject:  VMS 7.3 versus 7.2-2        F I am looking at setting up a cluster with the following configuration:F   Data Center 1: Two ES40's and a SAN with two HSG80's supporting 47 x 36GB drives.F   Data Center 2: Two ES40's and a SAN with two HSG80's supporting 47 x 36GB drives.E   A quorum node, possibly located in either Data centre, or remote toS either data centre. B This cluster will gradually be brought into an existing production cluster of four AS1200's atLF VMS 7.1-2, using HSJ40/50's and on CI/FDDI/Ethernet, with the eventual aim to drop the AS1200's. C Can anyone with similar experience provide recommendations as which 1 version to use for the new cluster, 7.3 or 7.2-2?!   TIA.   -- LeeA  ; Lee Y T Mah                        Capital Health AuthorityF? Email: lytmah@cha.ab.ca            Information Systems, RAH CSCF4 Phone:  (780) 477-4725, 477-4233   10240 Kingsway NW? Fax:      (780) 491-5119, 491-5619    Edmonton, AB, CAN  T5H3V9L   ------------------------------   Date: 2 Oct 2001 13:41:46 -070001 From: keithparris_NOSPAM@yahoo.com (Keith Parris)*> Subject: Re: VMScluster using fibrechannel and memory channel?< Message-ID: <cf15391e.0110021241.5c5576b@posting.google.com>  e Alan Greig <a.greig@virgin.net> wrote in message news:<4o86rtc3tqsud2dqpl7aloq7kejshfsjok@4ax.com>...SE > Can you recall (or have you investigated) if the locking throughput'F > with multiple Gigabit Ethernet interfaces installed can be increased@ > beyond that of MC? I can't recall if that was discussed in the > presentation or not.  F Verell's 'CI Performance' presentation {CI as in Cluster InterconnectsE in general, not just the star coupler variety) did show the effect of-E multiple Fast Ethernet channels with the new path-selection algorithm F in VMS 7.3, IIRC, but not multiple Gigabit Ethernet paths. (Presumably> this was because his results showed that today's Fast EthernetF adapters are actually faster than today's Gigabit Ethernet adapter for locking traffic.)   D As I recall, it was a different one of his presentations that showedD the weaknesses of the pre-7.3 load-sharing algorithm in PEDRIVER andF described how the new packet transmit algorithm in 7.3 allows PEDRIVERF to better utilize multiple LAN adapters, whether they be Fast Ethernet or Gigabit Ethernet.  @ You can find all of Verell's presentations from DFW Days 2001 at( http://vmsone.com/dfwdays/Presentations/C -------------------------------------------------------------------SC Keith Parris | parris at encompasserve dot org | VMS consulting on:-C Clusters, Disaster Tolerance, Internals, Performance, Storage & I/OW   ------------------------------   Date: 2 Oct 2001 20:18 CDT' From: carl@gerg.tamu.edu (Carl Perkins)E8 Subject: Re: Warranty on ES45 reduced from 3 years to 1?, Message-ID: <2OCT200120185834@gerg.tamu.edu>   paul@sture.ch writes...*O }In article <3bb8b284$0$19390$e4fe514c@newszilla.xs4all.nl>, Wilko Bulte wrote:On }> In <69Kt7.14283$xG6.5530020@typhoon.ne.mediaone.net> "Terry C. Shannon" <terryshannon@mediaone.net> writes: }> }[snip]- }> -I }> >Finally came across some Sun Blades. They were in an Internet cafe inR( }> >Amsterdam, down by Leidseplein (sp). }> S }> Spelled just fine Terry ;-) }> "  }But how do we pronounce it? :-) }___ }Paul Sture9 }Switzerland   Poorly?.   ("Led Zeppelin"?)o   --- Carl   ------------------------------  # Date: Wed, 03 Oct 2001 03:26:43 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>8 Subject: Re: Warranty on ES45 reduced from 3 years to 1?= Message-ID: <Tzvu7.68433$vq.12907140@typhoon.ne.mediaone.net>   4 "Carl Perkins" <carl@gerg.tamu.edu> wrote in message& news:2OCT200120185834@gerg.tamu.edu... > paul@sture.ch writes...rJ > }In article <3bb8b284$0$19390$e4fe514c@newszilla.xs4all.nl>, Wilko Bulte wrote:L > }> In <69Kt7.14283$xG6.5530020@typhoon.ne.mediaone.net> "Terry C. Shannon"# <terryshannon@mediaone.net> writes:u > }>	 > }[snip]o > }>K > }> >Finally came across some Sun Blades. They were in an Internet cafe ins* > }> >Amsterdam, down by Leidseplein (sp). > }>  > }> Spelled just fine Terry ;-) > }>" > }But how do we pronounce it? :-) > }___
 > }Paul StureT > }Switzerland > 	 > Poorly?  >  > ("Led Zeppelin"?)r  L Guess it depends on whether or not you've dallied in a coffee shop or "smart) shop" before visiting the Leidseplein....e   ------------------------------  $ Date: Wed, 3 Oct 2001 02:31:59 +01003 From: "Ian Richards" <ian.richards@yourarticle.net>s8 Subject: Your Article - The Journalistic Portal for Copy9 Message-ID: <iss.2968.3bba6a75.19e6f.1@mx2.east.saic.com>    Hello   L Since the launch of www.yourarticle.net there has been a considerable uptakeG of registration from Editors, Journalists, PR Agencies, Corporate PressuL Offices and Authors throughout North America, Europe, Asia and the Pacific.   H The web site has now been further enhanced with the latest technology toI facilitate ease of use in both downloading and uploading articles and nowfI thanks to sponsorship its completely FREE TO USE - Just register on line.   ; If you haven't already registered take a moment to do so atcC www.yourarticle.net and benefit from the foremost global portal fortG journalistic copy.   Its completely FREE OF CHARGE, whether you're just*L looking for content or wish to upload an article or press release for others to view or use.-  ( We hope you find Your Article of benefit   Ian Richards   www.yourarticle.netG      M Please forward this email to a colleague if you think it would be of interest. to themn    K If you have received this email in error or wish to have your email addressr8 removed from our data base, please send a blank email toI remove@yourarticle.net and your email address will be immediately removeds from our data base.o   ------------------------------   End of INFO-VAX 2001.549 ************************king I have seenG >> something somewhere....but I am getting old and feeble minded and doi# >> not know where I saw it anymore!O >V >There is a RanDriver atG >ftp://ftp  REGUP       -  V@ )ETaC1`"60ȑC2ȓ+Ґ!#Rlqƌ3kDFE>!JDyr
 B\`4ҦGTQ* L	Ն]*ٳh愱S8JRd<+o_0n}Դ]llǐĐȘ!dCqa^MF]騭as*tbEs@"Z&d	%L'kov}VDd0ޣw;]5yuNtwHκ׬'[{(_]&wbu߃/'ǘkxFG4So\b*eCF2NA$NCURg\FS=YC)fX`k0#{q]el	^z`<g$zY 	hoBZVJgVL2 , 
02019970311JVN01 0100
00