1 INFO-VAX	Fri, 18 Aug 2000	Volume 2000 : Issue 461       Contents:. Re: /float qualifier and resulting performance 100 MB/sec on 500au  Re: 100 MB/sec on 500au  Re: 100 MB/sec on 500au  Re: 100 MB/sec on 500au  Re: 100 MB/sec on 500au  RE: 100 MB/sec on 500au  Re: ??== DCPS 1.8 available. amuesant# RE: ASCII control characters in DCL 7 Re: attachments lost when using set forward in VMS-mail . Re: bizarre disappearing mouse pointer problem. Re: bizarre disappearing mouse pointer problem. Re: bizarre disappearing mouse pointer problem Re: Caching RMS Block I/O  Computer Associates Advise-IT   CONDIST [was DCPS 1.8 available] DCPS and PCL only printers% Re: DCPS with raw-tcp: stack overflow  ESO software on VMS?!?!  Re: ESO software on VMS?!?!  Re: From VMS to NT Re: From VMS to NT Re: From VMS to NT Re: From VMS to NT Re: From VMS to NT Re: From VMS to NT Re: Gnome replacing CDE?2 Re: Here we go again - WTB/T/etc source listing CD2 Re: Here we go again - WTB/T/etc source listing CD2 Re: Here we go again - WTB/T/etc source listing CD RE: Hmmmm a strange question< Re: Hobbyist OpenVMS systems (was Re: dose vms run on intel)3 Installing a network adapter on an Alpha 1000 4/233 3 Installing a network adapter on an Alpha 1000 4/233  Re: Java support on OpenVMS?# Re: Ken Olson's "snake oil" comment # Re: Ken Olson's "snake oil" comment  Re: Mass adding of users?  Re: Mass adding of users?   Re: old vms directory structure?( RE: Online Manual for a mylex controller& OpenVMS / Alpha Web Server - Frontpage2 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 Web Forum   Portable GUIs (VMS+Windows-NT) ?  Portable GUIs (VMS+Windows-NT) ?$ Re: Portable GUIs (VMS+Windows-NT) ?$ RE: Portable GUIs (VMS+Windows-NT) ?! Re: Sony MO on VAXstation 4000/60 ! Re: Sony MO on VAXstation 4000/60 ! Re: Sony MO on VAXstation 4000/60 ! Re: Sony MO on VAXstation 4000/60 & Toshiba CD-ROM and VMS Hobbiest CD-ROM* Re: Toshiba CD-ROM and VMS Hobbiest CD-ROM Re: VAXSTATION 4000/90 Re: VAXSTATION 4000/90 Re: VMS on a notebook ?  Re: VMS Vs any other OS  Re: VMS Vs any other OS  Re: VMS Vs any other OS  Re: What quota was exceeded  Re: What quota was exceeded  Re: What quota was exceeded  Re: What quota was exceeded  Re: What quota was exceeded  Re: What quota was exceeded  Re: What quota was exceeded  Re: What quota was exceeded ( Re: Why couldn't linux read a vms drive?( Re: Why couldn't linux read a vms drive?( Re: Why couldn't linux read a vms drive?( Re: Why couldn't linux read a vms drive?( Re: Why couldn't linux read a vms drive?( Re: Why couldn't linux read a vms drive?( Re: Why couldn't linux read a vms drive?$ X terminals that speak DECnet or LAT( Re: X terminals that speak DECnet or LAT( Re: X terminals that speak DECnet or LAT( Re: X terminals that speak DECnet or LAT( Re: X terminals that speak DECnet or LAT  F ----------------------------------------------------------------------  % Date: Thu, 17 Aug 2000 20:35:14 -0400 * From: David A Froble <davef@tsoft-inc.com>7 Subject: Re: /float qualifier and resulting performance - Message-ID: <399C84C2.A7FFAA84@tsoft-inc.com>   9 "Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515" wrote:  > J >         Hey, great!  So on  our  VAX  66x0's  and  my VAXstation 4000/60J >     (both    NVAX   implimentations   perhaps?),   I   get   FALSE   forJ >     g_float_emulated and TRUE for h_float_emulated.  Nice bit of  trivia >     to know.  Thanks!   O Sounds like hardware trivia time.  Pretty sure the VAX 6000 models 610-660 were P n-vax based.  The VAXstation 4000 model 60 is/was I'm pretty sure based upon theN Mariah chip.  Not sure if there was anything between the Mariah and the n-vax,J don't think so.  The VAXstation 4000 model 90 has the first version of the n-vax.   Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  % Date: Fri, 18 Aug 2000 02:46:17 -0400  From: quayle@pobox.com Subject: 100 MB/sec on 500au. Message-ID: <399CA379.2728.135EE462@localhost>  E I just upgraded my network to include a 10/100 MB switch.  One of my   systems is a 500au (Alpha).   B When I first turn it on, the switch shows that it is connected at ? 100 MB/sec.  During the boot sequence, it changes to 10 MB/sec.   @ Is there a magic parameter I have to set to make it stay at 100?     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Fri, 18 Aug 2000 09:37:21 +0100 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>  Subject: Re: 100 MB/sec on 500au, Message-ID: <8nisk2$12qa@newton.cc.rl.ac.uk>  L <quayle@pobox.com> wrote in message news:399CA379.2728.135EE462@localhost...  C > When I first turn it on, the switch shows that it is connected at A > 100 MB/sec.  During the boot sequence, it changes to 10 MB/sec.  > B > Is there a magic parameter I have to set to make it stay at 100?  B The console variable EWc0_mode setting, preferably. Or you can use8 LANCP when it has booted. Lock it down to what you want.   ------------------------------  % Date: Fri, 18 Aug 2000 10:31:05 -0400  From: quayle@pobox.com  Subject: Re: 100 MB/sec on 500au/ Message-ID: <399D1069.13072.15087F11@localhost>   E > > When I first turn it on, the switch shows that it is connected at C > > 100 MB/sec.  During the boot sequence, it changes to 10 MB/sec.  > > D > > Is there a magic parameter I have to set to make it stay at 100? > D > The console variable EWc0_mode setting, preferably. Or you can use: > LANCP when it has booted. Lock it down to what you want.  B And to what do I set it?  It's currently "TWISTED-PAIR".  I can't F seem to find any documentation on these variables anywhere on the Web.     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  # Date: Fri, 18 Aug 2000 15:19:12 GMT / From: "Richard L. Dyson" <rick-dyson@uiowa.edu>   Subject: Re: 100 MB/sec on 500au) Message-ID: <399D0DA0.18A236DD@uiowa.edu>    quayle@pobox.com wrote:  > G > > > When I first turn it on, the switch shows that it is connected at E > > > 100 MB/sec.  During the boot sequence, it changes to 10 MB/sec.  > > > F > > > Is there a magic parameter I have to set to make it stay at 100? > > F > > The console variable EWc0_mode setting, preferably. Or you can use< > > LANCP when it has booted. Lock it down to what you want. > C > And to what do I set it?  It's currently "TWISTED-PAIR".  I can't H > seem to find any documentation on these variables anywhere on the Web.  = 	Recently, somone actually posted a list of settings, however F I can't find them at this moment.  When I had this problem (before theF settings were posted!) I found that when you used an incorrect settingH for the EW* settings, the console returned a short list of allowed ones!B That is how I found out about "Auto negotiate" as opposed to "Auto? detect", for example.  I think you want it to be something like    set ewc0_mode fastfd  F for Fast 100BaseTX, full-duplex.  If you can get away with it and yourF netorking equipment upstream is compatible with the card you have, the& auto_negotiate (sp?) mode is the best.  G p.s.  I just searched the OpenVMS FAQ posted today and I can't find any 0 thing about this in that great set of documents.   Regards, Rick --  H Richard L. Dyson                                    rick-dyson@uiowa.eduH  _   _      _____                http://www-pi.physics.uiowa.edu/~dyson/H | | | |    |_   _|   Systems Analyst                     O: 319/335-1879H | | | | of   | |     The University of Iowa            FAX: 319/335-17536 | \_/ |     _| |_    Department of Physics & Astronomy-  \___/     |_____|   Iowa City, IA 52242-1479    ------------------------------  % Date: Fri, 18 Aug 2000 16:23:11 +0100 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>  Subject: Re: 100 MB/sec on 500au+ Message-ID: <8njkd1$it4@newton.cc.rl.ac.uk>   M <quayle@pobox.com> wrote in message news:399D1069.13072.15087F11@localhost...   C > And to what do I set it?  It's currently "TWISTED-PAIR".  I can't H > seem to find any documentation on these variables anywhere on the Web.  C FAST or FASTFD. Console variables tend mostly to be documented with 9 the hardware documentation for the particlar model. Also:   G http://www.openvms.digital.com:8000/ssb71/6480/6480p004.htm#heading_4.6    ------------------------------  % Date: Fri, 18 Aug 2000 12:05:16 -0400 4 From: "Bochnik, William J" <BochnikWJ@bernstein.com>  Subject: RE: 100 MB/sec on 500auJ Message-ID: <2B37459189B0D211BE710000F8EF9D850566827A@nts0147.beehive.com>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C0092E.1CA4998E  Content-Type: text/plain;  	charset="iso-8859-1"    100 Mb settings: Fast -> 100mb half duplex  FastFD -> 100mb full duplex    -----Original Message-----0 From: quayle@pobox.com [mailto:quayle@pobox.com] Sent: August 18, 2000 10:31 AM To: Info-VAX@Mvb.Saic.Com   Subject: Re: 100 MB/sec on 500au    E > > When I first turn it on, the switch shows that it is connected at C > > 100 MB/sec.  During the boot sequence, it changes to 10 MB/sec.  > > D > > Is there a magic parameter I have to set to make it stay at 100? > D > The console variable EWc0_mode setting, preferably. Or you can use: > LANCP when it has booted. Lock it down to what you want.  B And to what do I set it?  It's currently "TWISTED-PAIR".  I can't F seem to find any documentation on these variables anywhere on the Web.     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com       ' ------_=_NextPart_001_01C0092E.1CA4998E  Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =  charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2651.65"> & <TITLE>RE: 100 MB/sec on 500au</TITLE> </HEAD>  <BODY>  ) <P><FONT SIZE=3D2>100 Mb settings:</FONT> 6 <BR><FONT SIZE=3D2>Fast -&gt; 100mb half duplex</FONT>8 <BR><FONT SIZE=3D2>FastFD -&gt; 100mb full duplex</FONT> </P>  3 <P><FONT SIZE=3D2>-----Original Message-----</FONT> / <BR><FONT SIZE=3D2>From: quayle@pobox.com [<A = D HREF=3D"mailto:quayle@pobox.com">mailto:quayle@pobox.com</A>]</FONT>8 <BR><FONT SIZE=3D2>Sent: August 18, 2000 10:31 AM</FONT>3 <BR><FONT SIZE=3D2>To: Info-VAX@Mvb.Saic.Com</FONT> : <BR><FONT SIZE=3D2>Subject: Re: 100 MB/sec on 500au</FONT> </P> <BR>  G <P><FONT SIZE=3D2>&gt; &gt; When I first turn it on, the switch shows =  that it is connected at</FONT>@ <BR><FONT SIZE=3D2>&gt; &gt; 100 MB/sec.&nbsp; During the boot =) sequence, it changes to 10 MB/sec.</FONT> # <BR><FONT SIZE=3D2>&gt; &gt;</FONT> G <BR><FONT SIZE=3D2>&gt; &gt; Is there a magic parameter I have to set =  to make it stay at 100?</FONT> <BR><FONT SIZE=3D2>&gt; </FONT> A <BR><FONT SIZE=3D2>&gt; The console variable EWc0_mode setting, = ! preferably. Or you can use</FONT> H <BR><FONT SIZE=3D2>&gt; LANCP when it has booted. Lock it down to what = you want.</FONT> </P>  A <P><FONT SIZE=3D2>And to what do I set it?&nbsp; It's currently = / &quot;TWISTED-PAIR&quot;.&nbsp; I can't </FONT> F <BR><FONT SIZE=3D2>seem to find any documentation on these variables = anywhere on the Web.</FONT>  </P> <BR>   <P><FONT SIZE=3D2>--Stan</FONT>  </P>  # <P><FONT SIZE=3D2>----------</FONT> I <BR><FONT SIZE=3D2>Stanley F. Quayle, P.E.&nbsp;&nbsp; N8SQ&nbsp;&nbsp; = 7 +1 614-868-1363&nbsp;&nbsp; Fax: +1 614 868-1671</FONT> E <BR><FONT SIZE=3D2>8572 North Spring Ct. NW, Pickerington, OH&nbsp; =  43147</FONT>- <BR><FONT SIZE=3D2>Preferred address:&nbsp; = 7 stan@stanq.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =  HREF=3D"http://www.stanq.com" = 1 TARGET=3D"_blank">http://www.stanq.com</A></FONT>  </P> <BR>   </BODY>  </HTML> ) ------_=_NextPart_001_01C0092E.1CA4998E--    ------------------------------  % Date: Fri, 18 Aug 2000 10:17:27 +0100 , From: aus@vim.uni-wuerzburg.de (Hans M. Aus)% Subject: Re: ??== DCPS 1.8 available. D Message-ID: <aus-1808001017270001@wvia71.virologie.uni-wuerzburg.de>  3 In article <aRAN7fr$McU1@mccdev.slac.stanford.edu>, D Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515) wrote:   ...  > J >         List of supported printers?  I  don't  have the SPD to hand.  Is8 >     there a particular printer you'd be interested in? >  >  >         -Ken  F I'm still looking for reliable replacements for our LN08 printers. TheJ new  Xerox N2000/3000 series printers seem like interesting possibilities.   --  B Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de   ------------------------------  % Date: Fri, 18 Aug 2000 10:54:01 +0200 + From: Andreas Nastke <nastke@gdp-group.com>  Subject: amuesant - Message-ID: <399CF9A9.AADB97F3@gdp-group.com>    The code was willing.  It considered your request,  but the chips were weak.   ------------------------------  % Date: Fri, 18 Aug 2000 11:12:53 -0300 1 From: "Boyle, Darren" <boyledj@bankofbermuda.com> , Subject: RE: ASCII control characters in DCLK Message-ID: <9F664D538536D411BD3200508B6FF01A8AE8AD@bdant027.bda.bobda.com>    Doesn't CVUI & CVSI do this ?? - Darren   > ----------4 > From: 	JF Mezei[SMTP:jfmezei.spamnot@videotron.ca]* > Sent: 	Thursday, August 17, 2000 9:18 PM > To: 	Info-VAX@Mvb.Saic.Com/ > Subject: 	Re: ASCII control characters in DCL  > K > I am trying to define a key to update the decwindows title to contain the " > current node, device, directory. > H > However, to be totally "independant", I should not rely on any symbols > being  > defined for it to work.  > 
 > So, in the  @ > $DEFINE/KEY/TERMINATE/NOECHO F6 WRITE SYS$OUTPUT etc etc etc,  > L > I would need to have a way to produce the escape character without relying
 > on symbols.  > K > Now, I know of ways around this (and someone posted a clever way of using  > two + > f$fao to do this). But it made me wonder:  > B > 	Would it be possible for the VMS engineers to add a special FAO > directive I > (similar to the ones generating a tab etc) which would generate the ESC J > character ? (or better yet, one which can generate any character given a > numeric value ?) >     F **********************************************************************C This message and any files transmitted with it are confidential and J may be privileged and/or subject to the provisions of privacy legislation.M They are intended solely for the use of the individual or entity to whom they L are addressed. If the reader of this message is not the intended recipient, B please notify the sender immediately and then delete this message.I You are notified that reliance on, disclosure of, distribution or copying  of this message is prohibited.   Bank of Bermuda F **********************************************************************   ------------------------------  % Date: Fri, 18 Aug 2000 08:59:44 +0200 ) From: "Anders Olsson" <anders@lib.kth.se> @ Subject: Re: attachments lost when using set forward in VMS-mail& Message-ID: <8nin8l$a8p$1@news.kth.se>   Hi! E I started this and Arne suggested that I should take the issue to the J MX-group. I did and then I forgot to tell about the outcome to this group.' My forward was working but only partly. 	 I had set $ MAIL> set forw somebody@someplace.se
 instead of) MAIL> set forw mx%"somebody@someplace.se"   E I will copy here the mail from Adam Maulis that solved things for me.n ----------------   Hello,    ! (I have no experience in MX 5.x.)o     >   SYSTEM > mailc >  >MAIL> sh forw/use=testpilot2 >TESTPILOT has mail forwarded to ANDERS@LIB.KTH.SE     This is not enough. (MX 4.2)       >  > G >I think that before you had to use an MX-syntax with quotationmarks intK >forwardaddresses. I dont use that since I have experienced that it wasntiL >necessary to get the forwarding to function anyway. In my systartup_vms.com >I have this linet >p+ >$ DEFINE/SYSTEM MAIL$INTERNET_TRANSPORT MXA     These are not enough. (MX 4.2)     Use:     VMS 6.2:< MAIL> set forward "MX%""ANDERS@LIB.KTH.SE""" /user=testpilot VMS 7.2:8 MAIL> set forward MX%"ANDERS@LIB.KTH.SE" /user=testpilot       Justification:    ? When MX Local deliver a message it looking for a forward entry.e? If MX Local found a MX%... style forward entry, requeue message- directly to SMTP agent. J If MX local found any other forward then try deliver with MAIL$.. functionG that call MX_MAILSHR that generates a new header. (Inserts a blank linet to the header).(     -- Adam Mauliso     Just my hint...a   -----------------------a    J I changed my forwardaddress in accordance with the above and now it works.
 Anders Olsson?   ------------------------------  # Date: Fri, 18 Aug 2000 09:26:41 GMTn1 From: browlands@nospam.dera.gov.uk (Ben Rowlands)u7 Subject: Re: bizarre disappearing mouse pointer problema# Message-ID: <399d0025.6752659@news>l  @ On 17 Aug 2000 17:39:10 GMT, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote:MG >  Ok, I'll be a little more direct.  I saw this problem myself, I theneH >  upgraded and ECOd the configuration, and I saw the problem was fixed.H >  As I applied a whole lot of stuff together (while rolling the OpenVMSI >  Alpha configuration forward), I don't know specifically what fixed it.  >tB >  Specific ECOs mentioning cursor-related fixes are mentioned in: >    VMS721_UPDATE-V0100 >    ALPMOTF03_U401  >    ALPMOTF08_U30122  > F >  Without specific details on the configuration (DECwindows, graphicsD >  controller, ECO level, etc), a specific answer is very difficult.  D Where can I find more details about the contents of these ECOs? (and what does ECO stand for?).  F I can supply as much information as needed, I just need to be told how to find it.e   ------------------------------  # Date: Fri, 18 Aug 2000 10:30:49 GMTq1 From: browlands@nospam.dera.gov.uk (Ben Rowlands)e7 Subject: Re: bizarre disappearing mouse pointer problem $ Message-ID: <399d0f12.10573774@news>   following the information on  : http://ftp.support.compaq.com/patches/.new/openvms.html...  @ On 17 Aug 2000 17:39:10 GMT, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote:nZ >In article <399c0cb5.30913941@news>, browlands@nospam.dera.gov.uk (Ben Rowlandsq) writes:B >  Specific ECOs mentioning cursor-related fixes are mentioned in: >    VMS721_UPDATE-V0100    has no mention of mouse problems   >    ALPMOTF03_U401h  @ isn't there, did you mean 'ALPMOTF03_U4012' (which is there, but' doesn't have any mention of my problem)-   >    ALPMOTF08_U30122    wasn't there at all.  F Is there some other source as to what these ECOs do, that has a proper  top level list of their purpose?   ------------------------------   Date: 18 Aug 2000 13:14:22 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)7 Subject: Re: bizarre disappearing mouse pointer problem 6 Message-ID: <8njcre$9a4$1@mailint03.im.hou.compaq.com>  W In article <399d0025.6752659@news>, browlands@nospam.dera.gov.uk (Ben Rowlands) writes:_E :Where can I find more details about the contents of these ECOs? (and  :what does ECO stand for?).   E   Please see the ECO (patch) information included in the OpenVMS FAQ.   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Thu, 17 Aug 2000 20:49:53 -0400r* From: David A Froble <davef@tsoft-inc.com>" Subject: Re: Caching RMS Block I/O- Message-ID: <399C8831.55089ECD@tsoft-inc.com>    Phil Tregoning wrote:t > 7 > David A Froble <davef@tsoft-inc.com> wrote in article4& > <399B69C9.8C18E98E@tsoft-inc.com>... > > M > > Your original post did say that any modifications of the code were not ann > > option.  I'd ask why?7 > @ > Well that is what I have been told. The application was custom8 > written under contract, and is based on some quite old= > software. Obviously it could be re-written and re-verified,e@ > (and if file formats change that would have to include all the< > other parts that use these files), but that would cost too< > much; i.e. more than any hardware or caching software fix.  I Well, it would depend upon several things.  If the I/O could be/is fairlyWD isolated, then modifications would be to replace/modify only the I/OO statements.  Say you had routines BLOCK_IO_OPEN, BLOCK_IO_CLOSE, BLOCK_IO_READ,0O and BLOCK_IO_WRITE (yes, overly simplified, but not too far off) then only youreG open, close, read, and write statements in the program would need to be.M modified.  The new routines could implement your read-ahead and write-behind,tO and whatever else you required.  If sharing isn't necessary, they wouldn't even  have to bother with locking.  M Technical issues aside, I still feel a few bucks for a decent caching product?E will probably be your best solution.  If a demo of such doesn't prove O satisfactory, then you can re-visit other alternatives.  Any decent vendor will-N provide a demo so you can prove your results before spending any cash.  Insist on this.  D Another point, after working with some old software to implement Y2KK modifications, my personal feeling is to stay as far away from some of this02 stuff as I can get.  Another reason for 'no mods'.   Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  # Date: Fri, 18 Aug 2000 12:57:27 GMTa/ From: "John Nixon" <jorlnixon@worldnet.att.net> & Subject: Computer Associates Advise-ITF Message-ID: <Xoan5.14570$4T.834936@bgtnsc07-news.ops.worldnet.att.net>  H (I am not sure what happened, but after sending this before, I could not findG it.  I then found it in my SENT folder, but it had gone to VMSNET.ALPHA02 instead of comp.os.vms.  I am re-posting it here).  G I am almost embarassed to ask this, but has anyone else bought Computer2 Associates ADVISE-IT/ "upgrade?" for Poly Center Performance Advisor?r  C Since we upgraded our Alpha to VMS 7.2-1 we have now exceeded DECPSD supported versions. I,K am trying to install AdviseIT, but I cannot even figure out how to read theo documentation off the CDJ from my VMS systems.  The docs are in HTML and PDF format.  They include a	 PDF_VIWERAL exe on the CD, but when I do a DIR/FUL for the file, it says "no such file". Many other files on the CDH do this also.  You can see the files with  a DIR command, but not with a /FUL.e   ------------------------------  % Date: Fri, 18 Aug 2000 02:43:22 -0400e From: quayle@pobox.com) Subject: CONDIST [was DCPS 1.8 available]e/ Message-ID: <399CA2CA.22920.135C3ABA@localhost>n  J >     manufacturing (or words to that effect) and will appear on the  next >     CONDIST.  > I used to access to the VAX and Alpha CONDIST, but none of my  contacts subscribe anymore.a  D Is it possible to buy a one-time set of the latest CONDIST, and how  do I go about ordering it?       --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671a1 8572 North Spring Ct. NW, Pickerington, OH  43147b= Preferred address:  stan@stanq.com       http://www.stanq.comI   ------------------------------  % Date: Fri, 18 Aug 2000 09:11:22 -0400d& From: Ken Robinson <ksrobin@erenj.com># Subject: DCPS and PCL only printersn7 Message-ID: <5.0.0.13.0.20000818090958.009c6410@clmail>i  E I am trying to set up a DCPS V1.7 queue that points to a printer that I understands PCL only (HP4si, no Postscript) using rawtcp. It doesn't look A like this can be done, since DCPS wants to print the banner usings Postscript.   	 DCPS V1.7_ OpenVMS VAX 7.1  UCX v5.0  & Any helpful hints will be appreciated.   Thanks in advance0 Ken Robinson ksrobin@erenj.comB   ------------------------------  % Date: Fri, 18 Aug 2000 19:05:29 +02008- From: "Sandrine Treheux" <satr@memo.ikea.com>.. Subject: Re: DCPS with raw-tcp: stack overflow, Message-ID: <8njqir$4c7$1@mailgate.ikea.com>   Hej,  L     If you don't want to upgrade DCPS to 1.8, just put the IP address and it will work fine.o   Br/SandrineA      % Matthias Koch a crit dans le messageo/ <39990DDC.5502FED1@bessel.mpip-mainz.mpg.de>...f >Hi! >rG >I used DCPS 1.7 together with a serial printer without problems. As we8G >have a LJ4050TN network printer now, I changed the configuration from:  > & >$ @sys$startup:dcps$execution_queue - >      LJ -h >      taylor::"serial/tta2:" -: >0 >to: >n& >$ @sys$startup:dcps$execution_queue - >      LJ -0& >      taylor::"ip_rawtcp/pri1:9100" - >e/ >The execution of dcps$startup.com results in ao >n! >%SYSTEM-F-STKOVF, stack overflowo >hG >The queue has been created but is stopped. A start /que results in the  >same error. >e >Any ideas?c >s >bye,-	 >Matthias    ------------------------------  # Date: Fri, 18 Aug 2000 08:54:24 GMT * From: helbig@astro.rug.nl (Phillip Helbig)  Subject: ESO software on VMS?!?!3 Message-ID: <mt2.0-15416-966588863@star.bris.ac.uk>S  E Fortunately, I'm a theorist.  That means I write most of my own code oD rather than using "standard" packages.  It is thus easier for me to G continue to work with VMS than many of my astronomical colleagues, who pF use mostly unix these days.  In the good old days, when everyone used D VMS, astronomers did as well.  For various reasons, astronomy (more F than the rest of physics) mostly moved to unix a few years ago.  Then I the chicken-and-egg problem arose: less people use VMS, so less packages sH are supported for it, so more people are forced to move etc.  Note that F what started it was the move to unix (marketing in academia!) and not 5 the lack of software---EVERYTHING used to run on VMS.s  C However, from time to time I find myself using ESO software such as_D p2pp, skycat, fims etc.  (These are supported for HPUX, Solaris and E Linux---no Tru64/Digital Unix/OSF/Ultrix/whatever, no aix, no SGI (a II fair number of astronomical institutes use these last three OSs, so they -E are somewhat at a disadvantage).)  The p2pp package is now in java.  e> Presumably (isn't platform-independence (whatever happened to H distributing standard-conforming source code?) the main point of java?) H this should run on VMS.  Has anyone actually tried this?  Why should or  should not it work?N  I I don't recall off the top of my head what source code is available, but -H I believe something (besides the old TCL/TK as opposed to java p2pp) is.E What are the chances of getting this to run on VMS?  Does ANYone run < this stuff on VMS?  G How much effort (full-time astronomical programmers) would be required AH to keep ALL common astronomical software packages running on VMS?  With + or without cooperation from the unix crowd?;  H What really depresses me is that some of the same people who encouraged D the move away from proprietary VMS are now encouraging, or at least H supporting, the move to even more proprietary Microsoft stuff.  And the C people who said it has to all be unix since only one system can be  G supported are now supporting a second system in the guise of Microsoft / stuff.  Sound familiar?2  4 How long will the newest version of IRAF run on VMS?  E Other than the odd institute, are there any significant VMS sites in o, astronomy?  Is STScI still heavily into VMS?  H Especially with the new generation of very large surveys it seems to me G that there are many applications to which VMS will be ideally suited.  eI Unfortunately, VMS has lost this market.  It could be reclaimed with not TH even a special deal (though that would be nice) but simply by informing I folks about what options are available---most people think of everything sH associated with VMS as it was ten years ago.  And I hear everyday about C astronomers who leave to go into industry, finance etc and land in &F really high-paid IT positions.  Imagine the advantage to VMS sales if & these were VMS instead of unix people.  F I'm travelling at the moment and reading news hardly at all.  (Things B would be easier if, as in the old days, I could count on an LK201 I everywhere I go---without it, MAIL and NEWSRDR work (one CAN type in the  G commands) but aren't as quick).  Thus, please email any responses to meaG at helbig@astro.rug.nl and quote this bit in your reply so that others 0H in the thread will as well.  (Even if I can't read my email right away,  it doesn't expire.).     --M Phillip Helbig                       Email .............. helbig@astro.rug.nl M Kapteyn Instituut                    Email ................. helbig@man.ac.ukPM Rijksuniversiteit Groningen          Tel. ................... +31 50 363 6647 M Postbus 800                          Fax .................... +31 50 363 6100iM NL-9700 AV Groningen                 Web ... http://www.astro.rug.nl/~helbig/l  5 My opinions are not necessarily those of my employer.    ------------------------------  # Date: Fri, 18 Aug 2000 12:13:57 GMT1' From: david20@alpha2.mdx.ac.uk (D.Webb) $ Subject: Re: ESO software on VMS?!?!3 Message-ID: <mt2.0-15988-966600835@star.bris.ac.uk>p  ` In article <mt2.0-15416-966588863@star.bris.ac.uk>, helbig@astro.rug.nl (Phillip Helbig) writes:F >Other than the odd institute, are there any significant VMS sites in - >astronomy?  Is STScI still heavily into VMS?u  F You might want to contact Chuck lane  (lane@duphy4.physics.drexel.edu)> author of the CRINOID PERL webserver software and PERL expert.B He seems to be very into Astronomy. He may be able to point you to/ other colleagues working in Astronomy with VMS.A  
 David Webb VMS and Unix team leader CCSS Middlesex University  6 [Mod. note: quoted text rearranged and trimmed -- mjh]   ------------------------------  % Date: Thu, 17 Aug 2000 21:03:08 -0400 * From: David A Froble <davef@tsoft-inc.com> Subject: Re: From VMS to NTn- Message-ID: <399C8B4C.8ADB2A7B@tsoft-inc.com>   ( Andrew Harrison SUNUK Consultancy wrote: > F > NT does not support dumb terminals to my knowledge so you have a few
 > choices. > A > 1.       Stay on OpenVMS and upgrade to Oracle 8i (8.1.5(6)) is  > apparentlyI >           available for OpenVMS. This will allow you to continue to usea > your >           existing terminals.   M Almost brings new meaning to the saying "The enemy of my enemy is my friend".  :-)s   Dave   -- n4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  % Date: Fri, 18 Aug 2000 12:20:40 +0100aB From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com> Subject: Re: From VMS to NTy* Message-ID: <399D1C07.D6112B46@uk.sun.com>   David A Froble wrote:.  * > Andrew Harrison SUNUK Consultancy wrote: > >rH > > NT does not support dumb terminals to my knowledge so you have a few > > choices. > >iC > > 1.       Stay on OpenVMS and upgrade to Oracle 8i (8.1.5(6)) is  > > apparentlyK > >           available for OpenVMS. This will allow you to continue to use* > > your! > >           existing terminals.- >-O > Almost brings new meaning to the saying "The enemy of my enemy is my friend".. > :-)  >u  F In this case yes, I don't have a problem with people using NT or Win32F when they are the appropriate tool for the job. Sadly for NT this doesF limit its applicability to some desktop systems and some very limitted server solutions.u  E I do have a problem with the idea of changing from a working platform H that does the job to a platform that may or may not do the job simply as some form of fashion statement.p  N I also have a problem with companies like Compaq, IBM and HP who wholeheartelyD support MS in their attempts to foist completely inadequate productsD and technology on a largely unsuspecting market when they themselvesC have access to and know intimately technology and products that aretE the opposite. Compaqs publication of their ludicrous NT TPC-C resultsfD based on a shared nothing DBMS architecture being one such unwelcome manifestation of this.  E Dell I excuse because its the only thing they know, the others shouldl2 be ashamed of themselves because they know better.  D Sadly that tends to make me regard the whole of Compaq with contemptB which is something that the members of the OpenVMS and Tru64 teamsI don't really deserve. I guess I suspect that the NT cancer has penetrated I all the way through the organisation which is probably being to paranoid.   H So you are right  "The enemy of my enemy is my friend" holds true thoughD sadly your Friend "Compaq" is in this case your enemy as well, funny old world isn't it.c   RegardsS Andrew Harrison  Enterprise IT Architectb   ------------------------------    Date: 18 Aug 2000 10:17:52 -0400/ From: jordan@lisa.gemair.com (Jordan Henderson)f Subject: Re: From VMS to NTi* Message-ID: <8njgig$rt1$1@lisa.gemair.com>  * In article <399D1C07.D6112B46@uk.sun.com>,D Andrew Harrison SUNUK Consultancy  <andrew.nospam@uk.sun.com> wrote: >David A Froble wrote: >b+ >> Andrew Harrison SUNUK Consultancy wrote:e >>	 >> [snip]0 >>P >> Almost brings new meaning to the saying "The enemy of my enemy is my friend". >> :-) >> >eG >In this case yes, I don't have a problem with people using NT or Win32eG >when they are the appropriate tool for the job. Sadly for NT this doeseG >limit its applicability to some desktop systems and some very limittedV >server solutions. >iF >I do have a problem with the idea of changing from a working platformI >that does the job to a platform that may or may not do the job simply asV  >some form of fashion statement. >OO >I also have a problem with companies like Compaq, IBM and HP who wholeheartelyrE >support MS in their attempts to foist completely inadequate productscE >and technology on a largely unsuspecting market when they themselves D >have access to and know intimately technology and products that areF >the opposite. Compaqs publication of their ludicrous NT TPC-C resultsE >based on a shared nothing DBMS architecture being one such unwelcomeo >manifestation of this.l >s  ? Oh?  Do you have the same contempt for Sun when they attempt tog? foist wholley inadequate JavaStations (the first round in 1996)  on their customers?m  @ I heard nothing but disappointment and disgust from those tryingA to deploy these devices, but Sun insisted that this was a desktop 	 solution.0  > Of course, Sun should have known better.  They knew that users; would be happier with the more flexible, better performing,n= Windows machines on the desktops, but they had rather a blindb spot here...  ? This sort of thing is exactly why I suspect you are a marketingh? or sales person, Andrew.  One of the big reasons that companiesA> tend to "hide" real, working engineers from customers in sales> situations is that real, working engineers tend to have rather< disarming honesty and openness.  This extends to telling the; WHOLE story, even avoiding lies of omission with regard to a6 shortcomings of their own products versus those of the competition.  ; Whenever I get into a debate on issues with you, I feel you > purposely elide all my good points (with not even the courtesy> to put in a "[snip]" showing that you have done this), so that< you can pounce upon something you feel you can attack.  It's< frustrating, and it's what I would expect of someone with an agenda.Q  9 Your posting history on Usenet, as revealed by deja.com, -> suggests to me that you are on a mission to denegrate OpenVMS,: Tru64, Alpha hardware, occasionally Windows and Linux and : more rarely competitive Unix (I've seen you make favorable9 comparisons with Solaris vs. HP/UX and AIX).  This is theR" pattern of someone on a mission.    : I guess I would expect that a working Engineer would, just9 occasionally, have something to say that would be helpful6: to people trying to use _Sun_ products in comp.os.solaris,, comp.sys.sun, etc.  But, I've never seen it.  ; Combine this with other evidence, like your admission that  7 you work in the same office with x-DEC salesmen who aren9 now Sun Salemen, that you are sighted doing sales supportb1 gives me a picture of a Sales/Marketing Engineer.   > I'm not _sure_ that you are some kind of Sun stealth marketing< resource, but it doesn't really matter if you have a charter: or not.  The effect is the same, you act like one and I'll treat you like one.n  8 As far as I'm concerned, Sun Marketing is not welcome in; comp.os.vms and I'll treat them with the contempt that theyI deserve.    F >Dell I excuse because its the only thing they know, the others should3 >be ashamed of themselves because they know better.o >aE >Sadly that tends to make me regard the whole of Compaq with contemptpC >which is something that the members of the OpenVMS and Tru64 teams J >don't really deserve. I guess I suspect that the NT cancer has penetratedJ >all the way through the organisation which is probably being to paranoid. >iI >So you are right  "The enemy of my enemy is my friend" holds true thoughiE >sadly your Friend "Compaq" is in this case your enemy as well, funnya >old world isn't it. >r >Regards >Andrew Harrison >Enterprise IT Architect >v >  >e   -Jordan Hendersono jordan@greenapple.comi   ------------------------------  % Date: Fri, 18 Aug 2000 09:53:44 -0600d1 From: Glen Martin <GLENMARK@utxvms.cc.utexas.edu>n Subject: Re: From VMS to NTa4 Message-ID: <399D07A8.727FADD6@utxvms.cc.utexas.edu>   David A Froble wrote:a   O > Almost brings new meaning to the saying "The enemy of my enemy is my friend".i > :-)c  E Hey, twice in a short time span that our SUNny friend has recommendedfF staying with an OpenVMS solution. As critical as he is of the Q and ofG VMS advocates, even he knows that companies should stay with a solution 
 that works...o   Glen   ------------------------------  % Date: Fri, 18 Aug 2000 17:22:32 +0100DB From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com> Subject: Re: From VMS to NT * Message-ID: <399D62C8.E1229DD7@uk.sun.com>   Jordan Henderson wrote:y  , > In article <399D1C07.D6112B46@uk.sun.com>,F > Andrew Harrison SUNUK Consultancy  <andrew.nospam@uk.sun.com> wrote: > >David A Froble wrote: > >e- > >> Andrew Harrison SUNUK Consultancy wrote:u > >> > >> [snip]e > >>R > >> Almost brings new meaning to the saying "The enemy of my enemy is my friend". > >> :-) > >> > >e > < huge rant snipped >i >a< > Combine this with other evidence, like your admission that9 > you work in the same office with x-DEC salesmen who arei; > now Sun Salemen, that you are sighted doing sales supporte3 > gives me a picture of a Sales/Marketing Engineer.o >c  > Sure its a big building 4 floors lots of people. Sadly for you: the guy who sits next to me is a Java developer and the in6 the next cubicle is a ex-DEC cluster support engineer.  9 There are sales people down the other end of the buildingC6 and some of them are ex DEC which is hardly suprising.  : > As far as I'm concerned, Sun Marketing is not welcome in  = > comp.os.vms and I'll treat them with the contempt that theyt
 > deserve. >l  < Really, perhaps you should treat the Compaq marketing people@ for example Kerry who by your definition is clearly in marketing= with the contempt you appear to hold all marketing people in.e  > I am not a marketeer or a sales person, but I have worked with= both and what is sadly obvious is that the people doing these > functions from the Compaq end are not at all good at it. It is? also amusing to note that you round on anyone you suspect to be ? a marketeer while most people in this group complain that therey isn't enough marketing.5  > Perhaps Compaq and Digital before them did have marketeers butA they were frightened off by the people in this group. It would if B your prejudices are shared by the rest of the group be a very very thankless task.n  ; The more clued on this group may have worked out that blindV< uncritical acceptance of the word according to Compaq hasn't> actually got them very far. If you want to extinguish any form; of dissent and just read the URL's that Kerry posts you and0: believe them implicitly then I would suggest you put me in your kill file.R   Regardsh Andrew Harrisonv Enterprise IT Architecti   ------------------------------  % Date: Fri, 18 Aug 2000 18:03:59 +0100 B From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com> Subject: Re: From VMS to NTc* Message-ID: <399D6C7F.84F25EBA@uk.sun.com>   Jordan Henderson wrote:   , > In article <399D1C07.D6112B46@uk.sun.com>,F > Andrew Harrison SUNUK Consultancy  <andrew.nospam@uk.sun.com> wrote: > >David A Froble wrote: > >r- > >> Andrew Harrison SUNUK Consultancy wrote:- > >> > >> [snip]  > >>R > >> Almost brings new meaning to the saying "The enemy of my enemy is my friend". > >> :-) > A > Oh?  Do you have the same contempt for Sun when they attempt topA > foist wholley inadequate JavaStations (the first round in 1996)e > on their customers?   B I don't think Sun tried to or did foist JavaStations on any of our> customers. Nor was it an inadequate device, Sun never intendid< it to be a general purpose desktop and never to my knowledgeC sold it as such, it was designed to be mainly used a single purpose @ desktop, very like the dumb terminals we were discussing earlier in this thread.s  G The fact that some people particularly Oracle wanted to try to convinceiA people that NC's could replace PC's in their entirety was never a B Sun view. We felt then as we do now that the myth of the universalA desktop probably running some form of MS OS ignored the fact thatFM for many people a full blown OS with local storage was overkill. JavaStations K were Sun's first attempt to try to deliver the kind of client for that kindu of user.O JavaStations have been deployed sucessfully in banks for bank teller terminals,o	 florists,hI call centers etc. These are environments where Win32 with all its baggageaI are not needed to host the single application that all the users operate.i  D Like it or not the JavaStation also made HP, MS, IBM, Compaq etc sitD up and think about trying to deliver zero admin clients, they havn'tD got there but they would never have started without the NC which the JavaStation is an example.  B It is strange that you seem unable to conduct a discussion without= attacking Sun even in a thread where someone who you think isc@ a Sun marketeer is actually supporting the retention of OpenVMS.  C It makes me think that you arn't really reading what I post you arec: simply flaming me because of the fact that I work for Sun.   Regardsa Andrew Harrison  Enterprise IT Architecti   ------------------------------  % Date: Fri, 18 Aug 2000 09:50:25 +0200t= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>n! Subject: Re: Gnome replacing CDE?f( Message-ID: <399CEAC1.B048C18@gtech.com>   Kevin Handy wrote:= > Any chance of getting a copy of gtk for VMS from somewhere?p > I would like to play with it.r  ; http://www.openvms.compaq.com/openvms/products/ips/gtk.htmls   Arne   ------------------------------   Date: 18 Aug 2000 10:45:10 GMT' From: david20@alpha2.mdx.ac.uk (D.Webb) ; Subject: Re: Here we go again - WTB/T/etc source listing CDf0 Message-ID: <8nj43m$lno$1@aquila.news.mdx.ac.uk>  X In article <v$H27NpUaBgz@eisner.decus.org>, kuhrt@eisner.decus.org (Marty Kuhrt) writes:L >In article <399B1800.1F675DBB@vrx.net>, Beyonder <beyonder@vrx.net> writes: >> "D.Webb" wrote: >>  D >>> Given that so many other operating systems are going open-sourceN >>> eg Solaris - see http://www.sun.com/software/solaris/source/overview.html.L >>> Isn't it time for Compaq to review the price of the VMS source listings. >> h< >> long overdue, unfortunately won't help me though. sigh... >> s@ >>> $2000 plus a $790/yr update cost is much much too expensive. >>   >> You're not kidding! >> y >> B.o >>   >oB >Really?  Last time I looked into the cost of getting sources for ; >NT, it was (IIRC) >$1 million in escrow, and even then your# >wouldn't have _all_ the sources.  v >o  J Microsoft are very protective of their code. At least two possible reasons for this spring to mind :-  K 1) Releasing the code would confirm the alleged aquisition of parts of thate/    code from other companies/operating systems.l  N 2) The standard of the rest of that code (embedded games ?, security holes ? )M    might be such that they might have trouble continuing to sell the product.a   :)    > >Linux, Sun and the other unices can give away source, because >"it's just unix", right?  e >   O Until recently Sun were at least as protective of their code as Compaq/Digital  " if not as protective as Microsoft.  M Apart from "free Unixes" such as Linux  most proprietary Unix vendors have in I the recent past (last 10 years or so) been very protective of their code.u      B >If I read the Solaris 8 "open source" page correctly, you can useE >the sources, but you have to license through Sun if you want to sell ? >anything you did with them.  There's no similar restriction intB >VMS.  Use the sources, write a product, then sell it; no "Compaq, >May I" involved.    >-@ >Of course, the model is slightly different.  With the exception@ >of VMS engineering, no one recompiles the VMS kernel.  The same& >can't be said for those in unixland.     K I have been on Internals courses and have read the I&DS. I would like to beuI able to get the source listings. But at those prices I can't justify themtL either as a personal expense or justify them to my bosses for the University to purchase./ Why do I want them ? What will I do with them ?u  6 Just general interest + a bit of crash dump analysis.     
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  % Date: Fri, 18 Aug 2000 13:19:18 +0000S$ From: Steve.Spires@yellowpages.co.uk; Subject: Re: Here we go again - WTB/T/etc source listing CDe/ Message-ID: <0025693F.0048E8C2.00@quegw01.btyp>-  = Contact:   Tel: 3063  -  VSSG, 1st Floor, Bridge Street Plazai    > But you see, that's not a REAL resume; no spelling mistakes...   ;-p    Steve Spires        1 system@SendSpamHere.ORG on 17/08/2000 10:36:36 PMt    To:        Info-VAX@Mvb.Saic.Com+ cc:         (bcc: Steve Spires/YellowPages) > From:      system@SendSpamHere.ORG, 17 August 2000, 10:36 p.m.  2 Re: Here we go again - WTB/T/etc source listing CD        K In article <399C5333.F6B565DC@vrx.net>, Beyonder <beyonder@vrx.net> writes:r >Larry Kilgallen wrote:  > A >> So what is wrong with the University buying the subscription ?  >>E >> For them to teach operating systems, I would think they would needF# >> diverse examples, not just Unix.- >-; >hahaahahaha.... hahahaah... oh, sorry, you were serious...i >cN >the university doesn't even know what "vms" is any more. it's all NT and some sparcs,-+ >even a few SGI machines. VMS? what's that?   = Many don't.  Many don't, IMHO, even teach "computer science".>  C Occasionally, I get a mail or FAX from a college/university studento> looking for a job after graduation.  The resumes are pathetic.         Wanda Whatdidilearn    2469 Anytimeand Places   Myhometown, XX 00000       Career Objectives   C   A career where I can use my vast knowledge of computer systems toiC   make lots of money but not have to really know anything of use tolD   anybody about computers, programming, or networking.  I am a self-D   starter and team-player with asperations to attain a management orD   supervisory position in the first six months of employment and get    company "perks" out the wazoo.       Experience     Past to Presentr  D   I am capable of personal hygene and I was able to make it to class   on-time several days a week.       Grade Point Averageo      [1]   4.0i       Special Knowledger  ?   The Alphabet and names of all of the characters on "Friends".        Programming Languages   A   Micro$oft Word, Micro$oft XL, Micro$oft Visual Basic, Micro$oftrB   C, Micro$oft Visual C, Micro$oft Visual C++, Micro$oft Exchange,A   Micro$oft Office, Micro$oft IIS, Micro$oft FrontPage, Micro$oftrB   Exploiter, Micro$oft HTML, Micro$oft Java, Micro$oft JavaScript,   Micro$oft Pig-Latinu       References  6   The Encyclopedia, Dictionary, Poor Richard's Almanac    ? [1]  Does not factor in classes which were not held in the gym.m   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM-   ------------------------------  + Date: Fri, 18 Aug 2000 18:05:18 +0000 (   )H3 From: Christopher Smith <chriss@Mufasa.pubserv.com> ; Subject: Re: Here we go again - WTB/T/etc source listing CDuJ Message-ID: <Pine.LNX.4.05.10008181800330.26314-100000@Mufasa.pubserv.com>  9 On Thu, 17 Aug 2000, Brian Schenkenberger, VAXman- wrote:a  M > In article <399C5333.F6B565DC@vrx.net>, Beyonder <beyonder@vrx.net> writes:C- > >even a few SGI machines. VMS? what's that?  > ? > Many don't.  Many don't, IMHO, even teach "computer science".m  F > Occasionally, I get a mail or FAX from a college/university student B > looking for a job after graduation.  The resumes are pathetic.     [Many amusing things snipped]s   >   Programming Languages  > C >   Micro$oft Word, Micro$oft XL, Micro$oft Visual Basic, Micro$oftnD >   C, Micro$oft Visual C, Micro$oft Visual C++, Micro$oft Exchange,C >   Micro$oft Office, Micro$oft IIS, Micro$oft FrontPage, Micro$ofteD >   Exploiter, Micro$oft HTML, Micro$oft Java, Micro$oft JavaScript, >   Micro$oft Pig-Latinr  B I agree completely that most of the "computer scientists" that are4 produced by universitys today are microshaft fodder.  F I do have to say, though, in my own defense as well as that of others,G that it's nearly impossible to get a company to look at you most of theSI time without crap like that on your resume. (allthough, putting it in thea0 "programming languages" section is amusing... ;)  J Anyway, the point is, I have some microshaft garbage on my resume too, butB only because of worries that some phb somewhere will see that it'sD "missing" and give the job to some idiot who's got it.  Please don'tD assume that anyone who puts that kind of stuff on their resume is an absolute idiot. :)   Chris   O ===============================================================================k@ "My two cents"			(http://rootworks.com/twocentsworth.cgi?128562)= Christopher Smith(chriss@pubserv.com)			Prgramer^W Programmera Prime Synergy of Champaign, IL. % ------------------------------------- I "Where a calculator on the ENIAC is equipped with 18,000 vacuum tubes andtH weighs 30 tons, computers in the future may have only 1,000 vacuum tubes; and weigh only 1.5 tons." -- Popular Mechanics, March 1949 sO -------------------------------------------------------------------------------a   ------------------------------  % Date: Fri, 18 Aug 2000 11:18:43 -0300-1 From: "Boyle, Darren" <boyledj@bankofbermuda.com> % Subject: RE: Hmmmm a strange questionjK Message-ID: <9F664D538536D411BD3200508B6FF01A8AE8AE@bdant027.bda.bobda.com>0  K I THINK that you will find it is to indicate the jobs in order for use whenoF splitting reports on continuos paper (remembering back to the good oldK days).  i.e.  You will get all A's then all B's then all C's etc.  That way-L if you go from C's to F's then you know you missed a report somewhere in theE output and you need to go through it and burst that one also.  I alsofF believe there is a way to change it, I'm sure I did it once but we are talking many moons ago.  - Darren   > ----------6 > From: 	Terry Marosites[SMTP:TMarosites@unitedad.com]* > Sent: 	Thursday, August 17, 2000 3:15 PM > To: 	Info-VAX@Mvb.Saic.Com$ > Subject: 	Hmmmm a strange question >  >  > Best read at width 132 >  > Hello all, > L >    We have some large printers and sometimes they start printing garbage (0 > Greek to us).  While trying to research where 3 > this Greek starts I noticed the banner like this:o >  > FFFFFFFFFFL > 22222222222222222222222222222222222222222222222222222222222222222222222222 > 22+ > 222222222222222222222222222     FFFFFFFFF?E > FFFFFFFFFF     2222222222222222222  Digital Equipment Corporation - 	 > OpenVMSm: > Alpha Version v7.1-2  22222222222222222222     FFFFFFFFF > FFFFFFFFFFL > 22222222222222222222222222222222222222222222222222222222222222222222222222 > 22+ > 222222222222222222222222222     FFFFFFFFFe > I > I also noticed that it changes. My first thought is, If it changes , itr > must6 > mean something , So what does the F and 2 stand for.J > The "F" part in the above example seems to be always a Character and the8 > other part (the 2s) a number (0-9). My 2nd thought is E > how do I change the  "Digital Equipment Corporation - OpenVMS Alpha"	 > Versionn6 > v7.1-2 " to something else preferably at print time. >  > Inquisitive Terry  a >  >     F **********************************************************************C This message and any files transmitted with it are confidential and J may be privileged and/or subject to the provisions of privacy legislation.M They are intended solely for the use of the individual or entity to whom they L are addressed. If the reader of this message is not the intended recipient, B please notify the sender immediately and then delete this message.I You are notified that reliance on, disclosure of, distribution or copying  of this message is prohibited.   Bank of BermudanF **********************************************************************   ------------------------------  % Date: Thu, 17 Aug 2000 21:31:43 -0400d* From: David A Froble <davef@tsoft-inc.com>E Subject: Re: Hobbyist OpenVMS systems (was Re: dose vms run on intel)t- Message-ID: <399C91FF.E5101607@tsoft-inc.com>t   "Zane H. Healy" wrote: > 5 > Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> wrote:hS > > :You'll also probably want to avoid VAX 4000's (note, I did not say VAXstation,MP > > :VAXstation 4000's are very nice).  Of course personally I'd love a VAX 4000! > > :to replace my MicroVAX 3 :^)1 > O > >   Um, those are Q-bus systems, and included in my earlier recommendation.../ > L > Exactly :^)  What can I say, I might not be the normal Hobbyist, as my MV3I > has both a KDA50 and a RLV12 controller in it and the drives to go withtF > those controllers.  So for me a VAX 4000 w/Q-Bus would be very nice. > J > For that matter I'm threatening to bring a VAXstation II/RC back on-lineM > just for the fun of it, since I finally have room to set it up with the bigeM > monitor.  My only question is, do I want to go with a RD54 HD, or switch iteM > to ESDI or SCSI :^)  And yes, since I also own a PWS433au, I'm a sick puppy<3 > for messing with crusty old systems like this :^)  >   >                           Zane  M Ok, since neither of you guys will do so, I'll stick my neck out on this one.o  " The best systems for hobbyist use:  E A 32 processor wildfire, if money isn't an problem, but for the rest:o  L VAXstation 4000 model 60.  A VLC is rather anemic, and will probably cost asO much, and is limited to 24 MB of memory.  The models 90, 90A and 96 are still a M bit pricy to just not available.  Why the VAXstation 4000?  Built in SCSI and P ethernet, can be a server or a workstation, and should have adequate performanceO for a hobbyist.  One problem, the memory is non-standard, and I'm not even suree  what type of memory is required.  N AlphaStation 200/255 systems.  For the same reasons as the model 60 above, and, these use regular 72 pin SIMM parity memory.  P While not as educational as a Q-bus system, the two systems mentioned can be hadO for very low prices. They are very easy to set up.  Most SCSI disks install anda work with no hassles.v  N The flight suit I use is 100% nomex.  Think I'll go flying and not worry about% any disagreements with the above. :-)t   Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  % Date: Fri, 18 Aug 2000 09:23:45 +0200 . From: "Heiko Mikala" <h.mikala@mittelmann.com>< Subject: Installing a network adapter on an Alpha 1000 4/233& Message-ID: <8nioa7$nio$1@news.kdt.de>  
 Hi everybody!o  S Yesterday the Digital network card in our Alpha Server 1000 4/233 quit working. NowyR we have to replace this card with a new one. Is it possible to use any PCI networkS adapter (10 MBit, Ethernet, BNC), or do we have to use an original Digital adapter?w. (We tried an SMC adapter, but it didn't work).  H Do we have to configure something on the Alpha to make the adapter work?  T Do we have to configure something in VMS (OpenVMS 7.1)? Change some settings in some+ configuration files or something like that?     - Thank you very much in advance for your help,y   Heiko.   ------------------------------  % Date: Fri, 18 Aug 2000 07:26:38 -0400h2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>< Subject: Installing a network adapter on an Alpha 1000 4/2336 Message-ID: <200008180726_MC2-B02A-1DF@compuserve.com>  G         You have to use a card for which a driver exists!  In practice,iE this means that you have to use a supported Digital/Compaq card.  TheeF supported cards differ with the version of VMS that you are using; the1 older the version, the fewer cards are supported.8  & Message text written by "Heiko Mikala" >Hi everybody!  F Yesterday the Digital network card in our Alpha Server 1000 4/233 quit working. NowJ we have to replace this card with a new one. Is it possible to use any PC= I> network J adapter (10 MBit, Ethernet, BNC), or do we have to use an original Digita= le adapter?. (We tried an SMC adapter, but it didn't work).  H Do we have to configure something on the Alpha to make the adapter work?  C Do we have to configure something in VMS (OpenVMS 7.1)? Change somes settings in some+ configuration files or something like that?I    . Thank you very much in advance for your help,<   ------------------------------  % Date: Fri, 18 Aug 2000 09:55:33 +0200h= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> % Subject: Re: Java support on OpenVMS?a) Message-ID: <399CEBF5.BEB4C447@gtech.com>M   Chuck Chopp wrote:4 > What amount of support exists in OpenVMS for Java? > D > Is there a Java VM?  If yes, what version of Java does it support? > J > Is anybody producing Java development tools for OpenVMS or does all JavaH > development have to be done on another platform and then the byte-code > gets moved to OpenVMS? > A > Is there any support for accessing system services and RTL's orsG > functions in user-written shareable images from Java apps on OpenVMS?S > I > Is there any JDBC support in OpenVMS to allow Java applications to have 7 > access to databases on OpenVMS or on other platforms?h  > Current version of VMS ships with JDK 1.1.8 - JDK 1.2.2 can be< downloaded from via WWW (I think it is still called a beta).  3 JDK includes the compiler and EVE is a great editore' so you should have everything you need.o  ? You can access anything on VMS, if you write a small piece of Cg< code and create a shrareable image from that and uses JNI to@ access it from Java. No Compaq are not supplying such a library.  ? A JDBC in pure Java should work fine on VMS. If the JDBC drivert; requires components that are not available for VMS, then itt
 is a problem.    Arne   ------------------------------  # Date: Fri, 18 Aug 2000 13:58:21 GMTg% From: hg/jb <shsrms@bellatlantic.net>d, Subject: Re: Ken Olson's "snake oil" comment0 Message-ID: <399D42EC.F72C74B8@bellatlantic.net>   JF Mezei wrote:l >  > David A Froble wrote:nP > > I had always knew that there was a shift in about 1980, give or take severalR > > years, where DEC stopped listening to the customers, and began in many ways to- > > tell the customer what was best for them.n > N > Didn't this coincide with a growth period when DEC began to hire ex-IBMers ?N > Whenever I heard news of DEC hiring an ex guy from IBM, I always though "bigN > mistake, the last think DEC needs is to become like IBM. If it wants to beat7 > IBM, it must avoid the pitfals that IBM was stuck in.sH Bingo! I forgot that! I knew the strategic planning stuff started in the 77/78k time frame but you are correct.n  E Now, how come we never seem to talk about the crew that left when Vaxs moved > to Tewksbury, and the crew that went to SEL (later Gould SEL)? bobn   ------------------------------  # Date: Fri, 18 Aug 2000 14:04:39 GMT % From: hg/jb <shsrms@bellatlantic.net>s, Subject: Re: Ken Olson's "snake oil" comment0 Message-ID: <399D4465.CB2FDEC5@bellatlantic.net>   "Terry C. Shannon" wrote:  > I > Yup, me too, 509th RRG USASA 1970-72. Guess we all got fed snake oil by  > McNamara and LBJ, eh?i > M > SAR, as in Jolly Green and Songbird TACREPS, etc? Very perilous stuff, gladr > you made it back!   G I was navy, so we had a dry bed on a DLG/frigate, sitting off haiphong.'B had some interesting times, but nothing like the political sniping insideE dec in late 70s early 80s.  The jupiter (hepahstus) affair changed mye; opinion of Gordon Bell, but as they say, that was business.m  E I recall the standdown on 31 March 68 as 1 april 68, I was on stationt@ on a carrier, so we thought it was an april fools joke.  Wasn't.F Had fun with the wrangling to get permission to return fire when photoG recce took ground fire..took weeks..JCS said the ground fire on the RF8r looked aC lot like 45 cal close range...fireball and smoke from pol depot - Ir thinko. it was north of danang - was pretty visible...   Thanks! you to, welcome home!r   bobd   ------------------------------  # Date: Fri, 18 Aug 2000 13:33:25 GMT % From: Uwe Zessin <zessin@my-deja.com>-" Subject: Re: Mass adding of users?) Message-ID: <8njdv4$p7j$1@nnrp1.deja.com>G  0 In article <8ngegv$c2g$1@aquila.news.mdx.ac.uk>,!   david20@alpha2.mdx.ac.uk wrote:FC > In article <399B0C9B.93F8F292@earthlink.net>, "David J. Dachtera"i% <djesys.nospam@earthlink.net> writes:y > >JF Mezei wrote: > >"A > >I suppose Dan Sugalski may have tuned out due to the static of 
 > >recent. > > E > >Still, I was just wondering whether VMS Perl has any UAF interface , > >modules akin to All-in-1's UAF "dataset". >d" > There is a VMS::USER perl Module >  > Alpha2:perldoc vms::user  8 If you need read + write access to the UAF you might try     Python for OpenVMS.o@ It cannot create or delete records (you still need AUTHORIZE for? that), but $GETUAI and $SETUAI (and a function to get a list ofw all usernames) are here:  A http://www.decus.de/~zessin/python/doc/refman/vms_sys_getuai.htmlnA http://www.decus.de/~zessin/python/doc/refman/vms_sys_setuai.html>   There are 2 UAF demoes at:9 http://www.decus.de/~zessin/python/doc/demo/toc_demo.htmln  F There are many other routines to deal with identifiers + proxies, too:: http://www.decus.de/~zessin/python/doc/refman/vms_sys.html  4 Version 1.5.2-V007 has been released on 14-AUG-2000.% It contains some important bug fixes.h  - Start at: http://www.decus.de/~zessin/python/o4 The [changes] link describes new features and fixes.  D Take some time if you want to play with this - it's a LARGE package!   --
 Uwe Zessin    & Sent via Deja.com http://www.deja.com/ Before you buy.h   ------------------------------  # Date: Fri, 18 Aug 2000 14:27:16 GMTe From: jgessling@yahoo.comt" Subject: Re: Mass adding of users?) Message-ID: <8njh3c$t3e$1@nnrp1.deja.com>r  ) In article <8n8t2m$sls$1@nnrp1.deja.com>,m    Don.Carlton@Citadel.edu wrote:E > I'm sure this has come up before but, can't find a reference in the C > archives. We are beginning a new semester soon and will be addingy > several hundred new students.r  @ Just stumbled onto this which might help.  The "product" command? has a facility for adding accounts.  It is in the command file:i" sys$update:pcsi$create_account.com< Looks like it could be used outside of a product install and< might help you out.  The documentation for using this is at:  : http://www.openvms.digital.com/doc/ssb71/5952/5952p003.htm  A Speaking of "product", I'm figuring out wether it could be useful @ to create packages for our internally written software so it canB easily be installed on our ever growing number of systems.  Anyone$ out there doing this?  Got any tips?   Thanks,  jim    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  # Date: Fri, 18 Aug 2000 06:22:25 GMTo% From: Uwe Zessin <zessin@my-deja.com>$) Subject: Re: old vms directory structure?n) Message-ID: <8nikmm$tgg$1@nnrp1.deja.com>n  6 In article <8nh98g$15n$1@mailint03.im.hou.compaq.com>,&   hoffman@xdelta.zko.dec.nospam wrote: >eH > In article <NkVm5.12743$4T.735781@bgtnsc07-news.ops.worldnet.att.net>,3 "John Furcht" <johnfurcht@worldnet.att.net> writes: B > :Can someone explain the directory tree on an old microvms (4.4)
 system.??? >rE >   VMS (as it was then called) V3 and later and MicroVMS and OpenVMS5@ >   all use a rooted file structure, with a cluster common beingB >   optionally available in V4 (SYSCOMMON), and the cluster commonA >   structure then being standard (V5$COMMON on V5 and VMS$COMMON ' >   on V6 and later) in later releases.   C No, I don't think that is correct. I am very sure it was [V4COMMON] A in VMS V4.x and became [VMS$COMMON] with V5.0 - I have never seen C a V5$COMMON - do you, perhaps, confuse this with SYSTARTUP_V5.COM ?   F >   Each SYS*.DIR system root (eg: SYS0.DIR) will have a SYSCOMMON.DIRE >   alias entry for the common root (SYSCOMMON.DIR, V5$COMMON.DIR, orMF >   VMS$COMMON.DIR) This means that it APPEARS that you have duplicateF >   files, but these files are really THE SAME FILES.  Deletion of anyH >   directory containing these common files is very bad, and will render >   the system unbootable.  @ If the RSX AME is installed, you will also have directories likeF [001004] on the disk which seem to be a 'copy' of [VMS$COMMON.SYSEXE].2 Those are THE SAME FILES, too! Do NOT delete them!   --
 Uwe Zessin    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Fri, 18 Aug 2000 10:14:42 +0200u6 From: "Dijk, Jeroen van" <Jeroen.vandijk@getronics.nl>1 Subject: RE: Online Manual for a mylex controllertM Message-ID: <2795B75EF003D311801A00A0C906B51187E477@cucexec.gbc.getronics.nl>    Thanks for your time.i I have got the answer in dutch. So if there someone that have the same question mail me and I will translate the answer and forward it.=   -----Original Message----- From: Dijk, Jeroen van =& Sent: donderdag 17 augustus 2000 14:54 To: Info-VAX@MVB.SAIC.COMe- Subject: Online Manual for a mylex controllerp    H Where can I find a manual how to configure a mylex controller under VMS.   -- Jeroen M.W. van Dijk  Getronics Business Continuity BV8 Error #152 - Windows not found: (C)heer (P)arty (D)ance.   ------------------------------  # Date: Fri, 18 Aug 2000 08:58:14 GMT  From: steliosc@my-deja.com/ Subject: OpenVMS / Alpha Web Server - Frontpage-) Message-ID: <8nitqv$7nd$1@nnrp1.deja.com>-  * Greetings creatures from the planet Earth!  B   Does anybody out there have any good ideas how to publish snazzyE sites on VMS? I have Frontpage / Flash / Dreamweaver etc. etc. skills-G bit so far I have had to laboriously set up HTML and CGI scripts in DCL E to get my scripts working on VMS using Cern Web Server. Now I want toeB go to the next level of snazziness and use the 'easy' tools with a decent back end (OpenVMS).          & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------   Date: 17 Aug 2000 21:58:01 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 1/5s6 Message-ID: <8nhn59$3ef$1@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part1T Posting-Frequency: monthly Last-modified: 17 Aug 2000 Version: VMS-FAQ-1.TXT(4)1     Changes since last edition ==========================  . Extensive reorganization of the existing text. More parts.,% Removal of the part-specific indexes.a2 Initial work to create a hardware FAQ as Part 5/5.3 First cut at providing details of TDF/Timezone/etc.k  @ Remove Y2K       Relocate a few pieces to SOFT5, to MGMT38, etc.= Update INTRO5    information on avoiding MIME and attachments2? Add MGMT38       INITIALIZE ACCVIO and ANSI tape label support?F8 Add MGMT39       How do I recover from INSVIRMEM errors?L Add MGMT40       How can I prevent a serial terminal line from initiating...? Add MGMT41       How does PCSI use the image BUILD_IDENT field?2F Update SOFT1     URL churn, new pointers, relocate Perl info to SOFT12L Add INTRO8       Who are the corporate contacts for OpenVMS business issues? Update MISC10    new URL9 Add ALPHA15      Will OpenVMS run on the Alpha XL series?tN Add ALPHA16      Describe Alpha instruction emulation and instruction subsets?+ Update SOFT5     cross-reference to ALPHA16   Update SOFT1     pointer to BASHD Update VAX8      relocate timezone info to MGMT40, SET TIME to TIME7L Add MGMT40       Managing Timezones, Timekeeping, UTC, and Daylight Savings?Q Add ALPHA17      What is the Accuracy of the Alpha Time of Year (BB_WATCH) Clock?yF Add TIME*        System Time, Time Servers, Daylight Savings Time, etcH Update MGMT29    add specific example of AlphaBIOS switch to SRM consoleK Update MGMT20    add reference to web browser FTP file extension processing 1 Update VAX1      correct pointers, reword sectionp; Update UTIL2     add keyword FAT for use as a search targett% Remove DOC7      superceded by MGMT25i# Update DECW6     eschew obfuscationo: Update MGMT24    add PowerStorm 300/350, change title, etc Update MISC2     add URL) Remove VAX6      replaced by TIME section*) Update VAX5      cross-reference to FILE6a( Update FILE6     cross-reference to VAX5: Add ALPHA18      So how do I open up the DEC 3000 chassis?( Add ALPHA19      What is byte swizzling?6 Add ALPHA20      Available Alpha SRM console commands?9 Add DECW15       How can I reset the warning bell volume?l* Update PROG4     cross-reference to PROG11) Update DCL4      New title, minor updates 7 Add MGMT45       How can I split up an OpenVMS Cluster? 4 Add VMS14        How can I submit OpenVMS Freeware? D Add MGMT46       What file checksum tools are available for OpenVMS?K Add SOFT11       Preventing a serial terminal line from initiating a login? 2 Add SOFT12       Where can I get Perl for OpenVMS?) Update VMS7      Add V7.2-1H1 part numbern  Update FILE7     US Designs info1 Add VMS15        Porting applications to OpenVMS?u  Update VMS12     New Hobbes textD Add MGMT48       What (and where) is the OpenVMS Management Station? Remove ALPHA4    Move to VMS169 Add VMS16        How do I join Compaq Solutions Alliance?lE Add SCSI1        Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI? C Add MGMT49       How to determine current disk fragmentation level? I Add MGMT50       SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES? @ Add DCL11        Use of RUN/DETACH, LOGINOUT, and logical names?A Add DCL12        How to use escape and control characters in DCL?:> Update DECW9     The JF Mezei Memorial Braces-Befuddlement Fix, Remove MGMT8     superceded by TIME* section% Remove DOC7      superceded by MGMT25s Relocate MGMT22  to SUPP3t Relocate MGMT29  to ALPHA21s Relocate MISC1   to WIRES1 Relocate MISC3   to SUPP4i Relocate MISC4   to WIRES2 Relocate MISC10  to SUPP5t Relocate MISC11  to SUPP6a Relocate MISC16  to WIRES3 Combine MISC8    into SUPP4  Relocate DECW7   to SUPP7  Relocate DECW8   to SUPP8        Overview ========E This is part 1/5 of the Frequently Asked Questions (FAQ) posting for m= the comp.os.vms and comp.sys.dec newsgroups.  (comp.os.vms isSC 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.)  9   The OpenVMS FAQ is archived in the following locations:-  "     http://www.openvms.compaq.com/9     ftp://ftp.digital.com/pub/Digital/dec-faq/OpenVMS.txt,1     ftp://ftp.digital.com/pub/Digital/dec-faq/vms :     ftp://rtfm.mit.edu/pub/usenet/news.answers/dec-faq/vms,     comp.answers and news.answers newsgroups  A   Other internet FAQs are generally available in these locations:r  ,     comp.answers and news.answers newsgroups%     ftp://rtfm.mit.edu/pub/usenet/...a  ?   User-created HTML versions of the OpenVMS FAQ are located at:e       http://www.kjsl.com/vmsfaq'     http://eisner.decus.org/vms/faq.htm3  I Please do NOT send technical questions to the Frequently Asked Questions iH (FAQ) editor -- well, please do not email any questions that do not alsoG include the answer(s).  Please post these questions to the appropriate dI newsgroup instead -- and see INTRO5 before posting.  To make suggestions aG for changes or additions to this FAQ list, please send mail to the FAQ hI editor at hoffman@xdelta.zko.dec.com.  Again, the FAQ editor is *not* in  ' a position to answer general questions.    Some general notes:-  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 dJ 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 theHD 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 ther
 contribution.t  A Although the editor of this FAQ is an employee of Compaq ComputerAA Corporation, this posting is not an official statement of Compaq.   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 rL 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 rG in the United States and other countries, licensed exclusively through eK X/Open Company Ltd.  Other names are properties of their respective owners.p     Table of Contents - Part 1/5 ____________________________   Introduction( ========================================* INTRO1.  What is the scope of comp.os.vms?= INTRO2.  What other newsgroups carry VMS-related information?o INTRO3.  What is INFO-VAX?< INTRO4.  How do I subscribe to or unsubscribe from INFO-VAX?F INTRO5.  How do I submit a question or a response?  What is etiquette? INTRO6.  What is DECUS?V= INTRO7.  What archives of comp.os.vms/INFO-VAX are available? D INTRO8.  Who are the corporate contacts for OpenVMS business issues?   General questions about OpenVMSs( ========================================. 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?v3 VMS7.   What OpenVMS CD-ROM products are available?r, 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?g? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?i? VMS12.  Are there any general-access OpenVMS systems available?F* VMS13.  What version of OpenVMS do I need?* VMS14.  How can I submit OpenVMS Freeware?( VMS15.  Porting applications to OpenVMS?0 VMS16.  How do I join Compaq Solutions Alliance?    ! Documentation and other resourcesl( ========================================: DOC1.   Where can I find online copies of OpenVMS manuals?- DOC2.   What online information is available?f2 DOC3.   What books and publications are available?5 DOC4.   How do I extract a HELP topic to a text file? 6 DOC5.   Does OpenVMS Marketing have an e-mail address?5 DOC6.   What OpenVMS-related WWW sites are available?wB 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?tD DOC11.  Where can new users find tutorial information about OpenVMS?   OpenVMS System Time:( ========================================8 TIME1.   A brief history of OpenVMS Timekeeping, please?3 TIME2.   How does OpenVMS VAX maintain system time?r' 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?b= TIME6.   How can I keep the OpenVMS system time synchronized?kD TIME7.   How can I configure TCP/IP Services NTP as a time provider?1 TIME8.   How can I drift the OpenVMS system time?i; TIME9.   Why does VAX need a SET TIME at least once a year?    Table of Contents - Part 2/5 ____________________________   System Management,( ========================================# MGMT1.  What is an installed image?w0 MGMT2.  Are there any known viruses for OpenVMS?1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?a4 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?a? MGMT7.  Why can't I do a SET TIME command?  Help Managing DTSS?sD MGMT8.  How do I change the timezone differential and time in batch?; MGMT9.  How do I change the node name of an OpenVMS System?ME 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?m3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSCt4 MGMT14. How do I install DECnet Phase IV on VMS 7.1?< MGMT15. How do I change the text in a user's UIC identifier?3 MGMT16. What are the OpenVMS version upgrade paths? G MGMT17. Why do I have negative number in the pagefile reservable pages?AC MGMT18. Do I have to update layered products when updating OpenVMS?r3 MGMT19. How do I change the volume label of a disk?s. 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?o: 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?i> MGMT28. How do I set a default IP route or gateway on OpenVMS?C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?d* 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?a1 MGMT34. How do I delete (timeout) idle processes?s. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?; MGMT36. How can I set up reverse telnet (like reverse LAT)? ? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?.6 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? 6 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?a8 MGMT47. Configuring Cluster SCS for path load balancing?; MGMT48. What (and where) is the OpenVMS Management Station? - MGMT49. Determining disk fragmentation level? @ MGMT50. SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?     Table of Contents - Part 3/5 ____________________________   MAIL( ========================================$ MAIL1.  How do I send Internet mail?J MAIL2.  How do I get IN% or MX% added automatically to Internet addresses?K MAIL3.  How do I automatically append a signature file to my mail messages?nA MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.yL 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?sJ 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?d6 MAIL9.  How do I send or read attachments in VMS MAIL?     Other Utilitiesn( ========================================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?e2 UTIL5.  How do I read IBM EBCDIC tapes on OpenVMS?     DCL and command usagem( ========================================. DCL1.   How do I run a program with arguments?/ DCL2.   How can I redefine control keys in DCL?i* DCL3.   How can I clear the screen in DCL?< DCL4.   Using REPLY/LOG from DCL?  Disabling Console OPCOMs?1 DCL5.   How do I generate a random number in DCL? % DCL6.   What does the MCR command do?S2 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?t, DCL11.  Use of RUN/DETACH and logical names?   File System and RMS ( ========================================" 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?-@ 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?:1 FILE7.  How do I write recordable CDs on OpenVMS?i7 FILE8.  What I/O transfer size limits exist in OpenVMS?c< FILE9.  Can I use ODBC to connect to OpenVMS database files?     Programmingr( ========================================: 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?vD 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?eH 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?c? PROG10. How do I get a unique system ID for licensing purposes?e? PROG11. What is an executable, shareable, system or UWSS image?r/ PROG12. How do I do a file copy from a program?h PROG13. What is a descriptor?s+ PROG14. How many bytes are in a disk block?a, PROG15. How many bytes are in a memory page?9 PROG16. How do I create a process under another username?CD 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?e0 PROG19. How can I open a file for shared access?   Table of Contents - Part 4/5 ____________________________  
 DECwindows( ========================================F DECW1.  How do I let someone else display something on my workstation?9 DECW2.  How do I create a display on another workstation?$F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?0 DECW4.  How do I get a log of a DECterm session?E DECW5.  Problem - the DELETE key deletes forward instead of backward!=- 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?  
 Miscellaneousm( ========================================- MISC1.  Looking for connector wiring pinouts?eE MISC2.  Where can I find information on escape and control sequences?OF MISC5.  Where can I find performance info and specs for older systems?C MISC6.  What does "failure on back translate address request" mean?u6 MISC7.  How to determine the network hardware address?G MISC8.  Why does my system halt when I powercycle the console terminal?s@ MISC9.  Why can't I use PPP and RAS to connect to OpenVMS Alpha?> MISC12. Does DECprint (DCPS) work with the LRA0 parallel port?9 MISC13. How do I check for free space on a (BACKUP) tape?y( 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?4 MISC18. What are the prefixes for the powers of ten?4 MISC19. OpenVMS Cluster (SCS) over DECnet?  Over IP?- MISC20. Correctly using license PAKs and LMF?s     Software( ========================================C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?e@ SOFT2.    Where can I find the UNIX <whatever> tool for OpenVMS?I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser?S+ SOFT4.    Where can I get Java for OpenVMS?TJ SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?1 SOFT6.    Obtaining user input in DCL CGI script?I1 SOFT7.    How do I get my own batch entry number?a0 SOFT8.    How do I convert to new CMS libraries?B SOFT9.    Where can I get new certificates for Netscape Navigator?3 SOFT10.   Why doesn't DCL symbol substitution work?tK SOFT11.   How can I prevent a serial terminal line from initiating a login?n+ SOFT12.   Where can I get Perl for OpenVMS?      Table of Contents - Part 5/5 ____________________________   Alpha and Alpha-based systems ( ========================================, 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?-< 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?Y0 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?yJ 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?P? ALPHA20.  What commands are available in the Alpha SRM console?aA ALPHA29.  How do I switch between AlphaBIOS/ARC and SRM consoles?i   VAX and VAX-based systemst( ========================================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?  ' 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?eH SUPP3.  Why does my system halt when I power-cycle the console terminal?? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?eA SUPP5.  Which video monitor works with which graphics controller?H8 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 deadt    ! SCSI-related Hardware information ( ========================================< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?    F Wiring-, Adapter-, Connector-, and Pinout-related Hardware information( ========================================- WIRES1. Looking for connector wiring pinouts?t: WIRES2. What connectors and wiring adapters are available?2 WIRES3. What is flow control and how does it work?    < ------------------------------------------------------------* INTRO1.  What is the scope of comp.os.vms?  E The comp.os.vms newsgroup is the primary newsgroup for discussion of pF Compaq's OpenVMS operating system and the computer systems on which itE runs.  Questions about layered products which run on OpenVMS are alsooC welcome, though many of them (in particular, language compilers andoC 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?n  D The vmsnet.* hierarchy, run by DECUS, contains several newsgroups ofI interest, including vmsnet.misc and vmsnet.alpha, the latter being mostlye; devoted to Alpha topics.  There's also vmsnet.sources (and cJ vmsnet.sources.d) to which sources for or pointers to freeware are posted.F See the separate "What is VMSNET" monthly posting for further details.  C The comp.sys.dec newsgroup carries discussions about Compaq systemsh, acquired from Digital Equipment Corporation.  < ------------------------------------------------------------ INTRO3.  What is INFO-VAX?  D INFO-VAX is a mailing list which is bidirectionally gatewayed to theC comp.os.vms newsgroup.  This means that postings to comp.os.vms geteL automatically sent to INFO-VAX subscribers and messages sent to the INFO-VAXK list are automatically posted to comp.os.vms.  INFO-VAX can be a useful way F to participate in the newsgroup if you can't access the group directly through a news reader.  H An important point to keep in mind is that propagation delays vary, bothD within the newsgroup and with INFO-VAX mailings.  It's possible thatI postings may not be delivered for several days and some may appear out ofN order.  < ------------------------------------------------------------< INTRO4.  How do I subscribe to or unsubscribe from INFO-VAX?  H The address for subscription requests, as well as notes intended for theO moderator, is Info-VAX-Request@Mvb.Saic.Com.  Subscription requests are handled N automatically by a mail server.  This mail server ignores the subject line andL processes each line of the message as a command.  The syntax for subscribing< and unsubscribing and setting digest or non-digest modes is:  M0 SUBSCRIBE INFO-VAX      (ADD is a valid synonym)G UNSUBSCRIBE INFO-VAX	(REMOVE, SIGNOFF, and SIGN-OFF are valid synonyms)t5 SET INFO-VAX DIGEST     (to receive in Digest format)a> SET INFO-VAX NODIGEST   (to receive each message individually)   K Case is irrelevant and attempts to fetch a copy of the mailing list will begJ rejected (I consider the information to be confidential).  Any message notI understood by the mailserver will be forwarded to a human (allegedly) fori 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. p  C If you are on the Internet in the UK, send a message containing the F word SUBSCRIBE (or UNSUBSCRIBE) to info-vax-request@ncdlab.ulcc.ac.uk.  < ------------------------------------------------------------F INTRO5.  How do I submit a question or a response?  What is etiquette?  J If you are using a news reader, post your question to comp.os.vms.  If youK want to submit through INFO-VAX, send the message to Info-VAX@mvb.saic.com.   J Before posting, please use available local resources, such as the manuals,L HELP and this FAQ first.  Also make a point of reading the release notes forJ the product you're using, generally placed in SYS$HELP.  Often you'll findM the answer, and will save time and effort for all concerned.  (And you won't   "annoy the natives"...)d  8 When posting, please consider the following suggestions:  E     1.  Include a valid e-mail address in the text of your posting or D         in a "signature" appended to the end.  Reply-to addresses in 	headers often get garbled.   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.  dM         Say what you've tried so far, so that effort isn't duplicated.  Keep uK         in mind that there's not yet a telepathy protocol for the Internet.SM         (The more detailed your description, the better that people can help o          you with your question.)  I     3.  If responding to a posting, include in your reply only as much ofSF         the original posting as is necessary to establish context.  AsE 	a guideline, consider that if you've included more text than you've  E 	added, you've possibly included too much.  Never include signatures   	and other irrelevant material.e  E     4.  Be polite.  If the question isn't worded the way you think isaC         correct or doesn't include the information you want, try too> 	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  B         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 nI         posting via email sent to INFO-VAX, please turn off MIME, vcard, ,I         attachments, and other mechanisms that assume anyone reading the IJ         post has the corresponding capability -- use the text-only option M         of your web browser, news reader, or mailer.  Usenet is traditionallySF 	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.oC 	If the message uses MIME or attachments or such, the text of your lE 	message will be buried in a large pile of gibberish, and some tools o? 	will send multiple copies of the text within a single posting.)  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/part1-H   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/emily-postnews/part1G   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/writing-style/part1TG   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/posting-rules/part1o  G This information will document the etiquette of newsgroups, as well as aF providing you with the knowledge the vast amount of newsgroup-related E information that is readily available to you, and where to find it...I  < 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 eK nefarious use of this same information.  Other sites will hopefully return ?J the favor, and not post information that will potentially compromise YOUR # site and YOUR computer environment.A  < ------------------------------------------------------------ INTRO6.  What is DECUS?t  D DECUS, the Digital Equipment Computer Users Society, is a World WideF organization of Information Technology professionals interested in theC products, services, and technologies of Compaq and related vendors.T     J Membership in the Chapter is free and provides participants with the meansI to enhance their professional development, forums for technical training,rG mechanisms for obtaining up-to-date information, advocacy programs, and G opportunities for informal disclosure and interaction with professional= colleagues of like interest.  M For further information, see the separate monthly "What is DECUS" posting, or H refer to the US DECUS WWW server at http://www.decus.org or the Canadian) DECUS WWW server at http://www.decus.ca/.n  < ------------------------------------------------------------= INTRO7.  What archives of comp.os.vms/INFO-VAX are available?8  : Everything posted since 1990 is archived and available at:   ftp://crvax.sri.com/info-vax/n   					[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 I@   Comoaq Corporate President to the OpenVMS Vice President (VP).     1     Michael Capellas     Compaq President and CEOr9                          Michael.Capellas[-at-]Compaq.Come  D     Bill Heil            VP, Business Critical Servers Business Unit2                          Bill.Heil[-at-]Compaq.Com  =     Don Harbert          VP, High Performance Server DivisionO4                          Don.Harbert[-at-]Compaq.Com  8     Rich Marcello        VP, Open Systems Software Group9                          Richard.Marcello[-at-]Compaq.Com   D   These folks will obviously respond best to cogently-worded OpenVMSG   corporate business issues.  These folks are NOT appropriate contacts GH   for any OpenVMS technical support issues or support requests, nor for ?   any other non-corporate-related, non-business-related issues.I9                                          [Atlant Schmidt]m  < ------------------------------------------------------------. 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 VMSoM 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 firstoN 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.a  L OpenVMS was designed entirely within Compaq (Digital Equipment Corporation).G The principal designers were Dave Cutler and Dick Hustvedt, with a wideeK 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 .E RSX-11M, and many concepts from RSX-11M were carried over to OpenVMS..  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 rC operating system. Current implementations run on Alpha systems fromC Compaq, and other vendors.   				[Paul Winalski]o 				[Arne Vajhj]u  G For more details on OpenVMS and its features, read the OpenVMS Software6 Product Description at:n  %   http://www.digital.com/info/SP2501/=%   http://www.digital.com/info/SP4187/I%   http://www.digital.com/info/SPHOME/u  A Additional information on the general features of various OpenVMSe@ releases, release dates, as well as the development project code, names of specific releases, is available at:  H   http://www.openvms.digital.com/openvms/os/openvms-release-history.html  J Additional historical information -- as well as pictures and a variety of > other trivia -- is available in the VAX 20th anniversary book:  9   http://www.openvms.digital.com/openvms/20th/vmsbook.pdfA  E For information on the FreeVMS project (also see the related softwaree$ licensing topics VMS9, ALPHA4), see:     http://www.freevms.org/d  < ------------------------------------------------------------7 VMS2.   What is the difference between VMS and OpenVMS?e  I VMS and OpenVMS are two names for the same operating system.  Originally,rD 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 thewG Alpha platform, it was renamed OpenVMS, for both VAX and Alpha, in part D to signify the high degree of support for industry standards such as5 POSIX, which provides many features of UNIX systems.    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 tL media and documentation which can be found on the Consolidated Distribution I and On-Line Documentation CD-ROMs.  Support for the POSIX package on moreNH recent OpenVMS releases is not available, various parts of POSIX such asI calls from the API are being integrated more directly into OpenVMS.  For n4 more information on POSIX for VMS see question SOFT2  C What became confusing is that the OpenVMS name was introduced firstlF 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 oE the name did not start to be actually used in the product until V6.0.i  G The proper names for OpenVMS on the two platforms are now "OpenVMS VAX" @ and "OpenVMS Alpha", the latter having superseded "OpenVMS AXP".   				[Arne Vajhj]L  < ------------------------------------------------------------* VMS3.   How do I port from VMS to OpenVMS?  9 You already did.  Wasn't that easy?  (See question VMS2.)l  < ------------------------------------------------------------* VMS4.   Which is better - OpenVMS or UNIX?  M This question comes up periodically, usually asked by new subscribers who are1M long-time UNIX users. Sometimes, it is ignored totally; other times, it leadsiN 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.z 					[leichter@lrw.com]m  F Seriously, OpenVMS and the better implementations of UNIX are all fineE operating systems, each with its strengths and weaknesses.  If you're E in a position where you need to choose, select the one that best fitscC your own requirements, considering, for example, whether or not thea@ layered products or specific OS features you want are available.   					[Steve Lionel]   < ------------------------------------------------------------= VMS5.   Is Compaq continuing funding and support for OpenVMS?    Yes.  ? Active development of new OpenVMS releases is underway, as wello as the continuation of support.   @ Please see the following URLs for details, roadmaps, and related information:      http://www.compaq.com/openvms/6   http://www.openvms.digital.com/OPENVMS/strategy.html:   http://www.openvms.digital.com/openvms/roadmap/index.htm.   http://www.openvms.digital.com/openvmstimes/   http://www.compaq.com/inform/h  < ------------------------------------------------------------' [VMS6 removed, replaced by Y2K section]   < ------------------------------------------------------------3 VMS7.   What OpenVMS CD-ROM products are available?r  $ 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.digital.com/info/SP2501/,%   http://www.digital.com/info/SP4187/n%   http://www.digital.com/info/SPHOME/=  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-ROMr?   QA-MT1AT-H8   OpenVMS Alpha V7.2-1 maintenance release CD-ROMc>   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 Alpha-   QT-3CRAA-C8   OpenVMS VAX   E OpenVMS VAX and OpenVMS Alpha source listings CD-ROM sets include thenI source listings of most of OpenVMS, and these CD-ROM sets are invaluable lG for any folks working directly with OpenVMS internals, as well as folksA@ interested in seeing examples of various programming interfaces.  4   QB-MT1AB-E8   OpenVMS Alpha Source Listings CD-ROM<   QT-MT1AB-Q8   OpenVMS Alpha Source Listings CD-ROM Updates2   QB-001AB-E8   OpenVMS VAX Source Listings CD-ROM:   QT-001AB-Q8   OpenVMS VAX Source Listings CD-ROM Updates  n< ------------------------------------------------------------, 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  G complete list. However, the rumor is NOT true that an attempt was made  C to write pieces of OpenVMS in every supported language so that the iG Run-Time Libraries could not be unbundled.  (APL, BASIC, COBOL and RPG t0 are just some of the languages NOT represented!)  I There are a large variety of small and not-so-small tools and DCL command I procedures that are used as part of the OpenVMS build, and a source code dK control system capable of maintaining over a hundred thousand source files nH 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, F compilers, a variety of layered products, and an OpenVMS Freeware kit F for a nominal fee.  The OpenVMS Freeware is also available separately.  ! For further information, link to:)  #   http://www.montagar.com/hobbyist/a  E Further information on DECUS and on DECUS membership is available at:.     http://www.decus.org/i  C To transfer a commercial OpenVMS license from one owner to another, D or to purchase a commercial license, you can contact Compaq ComputerA Corporation at 1-800-DIGITAL (in North America), or your local ort regional sales office.  E Commercial developers can join the CSA program, and can (potentially) C receive discounts on various software product licenses and software.D distributions, as well as on hardware purchases.  Please see ALPHA4. 					[Stephen Hoffman]6                                         [Scott Snadow]  < ------------------------------------------------------------= VMS10.  What is OpenVMS doing about the Euro currency symbol?f  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.digital.com/euro/  < ------------------------------------------------------------? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?c   Why?  Business reasons...n  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 productpA or package for OpenVMS would have to justify the port to "OpenVMSaD 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.h  C Because there are design features that required by OpenVMS that are F 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.s  C Because Alpha is faster than Intel IA32 systems -- if OpenVMS is toh? be ported, a port to a slower system is more difficult to sell.g  @ 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 OpenVMSuD arises from the stability of the underlying VAX and Alpha hardware, C and systems based on components such as ISA and random memory SIMMst might not be as stable.p  " But yes, it would be nice to have.  <                                            [Stephen Hoffman]  < ------------------------------------------------------------? VMS12.  Are there any general-access OpenVMS systems available?t   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.o  E                                      [Scott Squires, Steven Shamlian]h     o OpenVMS Galaxy Test Drivel  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/      < ------------------------------------------------------------* 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.s  %   http://www.digital.com/info/SPHOME/t  6 For a table of OpenVMS versions for various platforms, please see:   :   http://www.openvms.digital.com/openvms/supportchart.html  : 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 Y9 support for a particular series of Alpha microprocessors:d  $ Microprocessor | OpenVMS   | General%   Generation   | Version   | Commentsb  G   21064  EV4   : V1.0      : few systems; most EV4 req later; upg avail 5   21164  EV5   : V6.2      : subsequent upg availablet=   21164A EV56  : V6.2-1H3  : subsequent upg to V7.1 and lateraH   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 expectation-    < ------------------------------------------------------------* VMS14.  How can I submit OpenVMS Freeware?  ?   For the guidelines and submission info, please visit the URL:o  A     http://www.openvms.digital.com/openvms/freeware/cd_guide.htmlq  < ------------------------------------------------------------( VMS15.  Porting applications to OpenVMS?  C Porting can range from simple to rather complex, and depends on theg' features used on the original platform.n  A This section covers generic porting, and porting from OpenVMS VAXs@ 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 bB OpenVMS Alpha, on management differences, on upgrading privileged   code, and application migration:  '     http://www.openvms.compaq.com:8000/t&     http://www.openvms.compaq.com/doc/  : Details on the C programming environment are available at:  <     http://www.openvms.digital.com/commercial/c/c_index.html  : Details on porting VAX C to Compaq C are are available at:  =     http://www.openvms.digital.com/commercial/c/index_vax.htmn  + An OpenVMS Porting Library is available at:p  D     http://www.openvms.digital.com/openvms/products/ips/porting.html  A Information on the Enterprise Toolkit, a Visual-based developmentqE environment for developing applications for OpenVMS using a Microsoft  platform, is available at:  >     http://www.openvms.digital.com/commercial/et/et_index.html  L Details on DCE, CORBA, BridgeWorks, and COM/DCOM middleware is available at:  =     http://www.openvms.digital.com/commercial/middleware.htmle  1 Information on the COE standards is available at:O       http://diicoe.disa.mil/coe/   C A wide variety of programming development tools and middleware are tA available as commercial products (eg: DECset, IBM MQseries), and  C various tools are also available as shareware or Freeware.  Please -/ see other sections of this FAQ, and please see:   .     http://www.partner.compaq.com/www-catalog/  o< ------------------------------------------------------------0 VMS16.  How do I join Compaq Solutions Alliance?  G The Compaq Solutions Alliance (CSA) is a (free) program that is open totH and that supports software partners, consultants, and service providers:      http://www.compaq.com/csa/h  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.1  H The Compaq Solutions Alliance Technical Journal (CTJ) is "web-published" monthly, and available at:  %   http://www.intercontent.com/compaq/E  < ------------------------------------------------------------: 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 p, OpenVMS products are presently available at:  &   http://www.openvms.digital.com:8000/%   http://www.openvms.digital.com/doc/n,   http://www.openvms.digital.com/commercial/  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 iK with the documentation distribution.  BNU can display HTML, Bookreader, ands! documentation in other formats.  e  E MGBOOK, a viewer for Bookreader-format documentation is available for I character-cell terminals (eg. VTxxx) via the WKU VMS Freeware file serverg" -- see question SOFT1 for details. 					[Steve Lionel]O 					[Stephen Hoffman]    < ------------------------------------------------------------- DOC2.   What online information is available?o  M On your OpenVMS system, the HELP command can provide a wealth of information,cJ 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 further2	 pointers..  E OpenVMS Marketing runs a WWW server at http://www.compaq.com/openvms/wM (http://www.openvms.digital.com/).  Here, you will find product information, -K strategy documents, the contents of the latest OpenVMS Freeware CD-ROM and  
 much more.  G Product information for just about everything Compaq sells is availableaH from Digital's Internet servers.  If you're using a World-Wide-Web (WWW)H browser, use http://www.digital.com/info.html  For anonymous FTP access, log in to ftp.digital.com.    6 Software Product Descriptions (SPDs) are available at:  %   http://www.digital.com/info/SPHOME/p  L system performance data (see ALPHA5), product infosheets, release notes and  much more are also available.s   In addition,  /   http://www.digital.com/info/forms/search.htmlI  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. uD Various contract-access and non-contract access ECO (patch) kits are available at the URL:   %   http://search.service.digital.com/ b   For ftp access use r      ftp://ftp.service.digital.com/  I The Compaq Systems and Options Catalog (SOC) and the Interactive Catalog   are available at:s  1   http://www.digital.com/info/SOHOME/SOHOMEHM.HTMw!   http://www.systems.digital.com/S  G The Systems and Options Catalog is being replaced by Compaq QuickSpecs.f  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.digital.com/m  C Information on Compaq hardware, software, products and services is V, available through various telephone numbers:  G     1-800-AT-COMPAQ     : voice : Compaq (including DIGITAL and Tandem)s7                                   products and servicess9     1-800-DIGITAL	: voice : DIGITAL products and servicesn0     1-800-DEC-2717	: voice : The DECchip Hotline9     1-508-568-6868	: voice : (alternate number for above)y>     1-800-STORWORK      : voice : The Compaq StorageWorks team  G David Mathog offers two HTML documents which contain useful informationr about OpenVMS.  7   http://seqaxp.bio.caltech.edu:8000/www/vms_sheet.html ?   http://seqaxp.bio.caltech.edu:8000/www/vms_beginners_faq.htmle  9 The VAXarchive (hardware and software information) is at:t&   http://vax.sevensages.org/index.html  I Useful OpenVMS information and an extensive set of links is available at:p   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.htmle  C The Compaq inFORM magazine and OpenVMS Times newsletters have email, subscriptions available, see:t  !     http://www.compaq.com/inFORM/m0     http://www.openvms.digital.com/openvmstimes/  ) Also see the DFWCUG Longwords newsletter:e       http://www.dfwcug.org/    < ------------------------------------------------------------2 DOC3.   What books and publications are available?  C A bibliography of current and recent OpenVMS books is available at:-  ,   http://www.levitte.org/~ava/vms_book.htmlx  C The Butterworth-Heinemann Digital Press imprint offers a number of  * OpenVMS books.  A website is available at:     http://www.bh.com/  ; Information on specific OpenVMS books is also available at:i  3   http://www.openvms.digital.com/openvms/books.htmlm   Also see DOC10.h    < ------------------------------------------------------------E DOC4.   How do I extract the contents of a HELP topic to a text file?P  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 following  command:  7      $ HELP/OUT=filename.txt help-topic [help-subtopic]6  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 helpwE library), add /LIBRARY=libname after the HELP verb.  To see the namesl8 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 provideiK informal method to communicate directly with members of OpenVMS Marketing.)D  < ------------------------------------------------------------5 DOC6.   What OpenVMS-related WWW sites are available?i  F     http://www.openvms.digital.com/   (Sponsored by OpenVMS Marketing)C     http://www.montagar.com/          (Sponsored by DECUS - DFWLUG)s@     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)p  A The following web site is sponsored by "The Beave", and provides  C information that is directly relevent to system managers, security eC managers, and others interested in ensuring the continued security r of OpenVMS systems:u  3     http://www.vistech.net/users/beave/hack-vms-faqS  E Suggestions (indirectly) provided by the above include disabling the b> port 11 and 15 stats provided by IP packages such as Multinet.  < ------------------------------------------------------------ DOC7.   removed.  See MGMT25.C  < ------------------------------------------------------------B DOC8.   Where can I find info about undocumented OpenVMS features?  E After all this discussion about undocumented VMS features I started ao4 collection of some documentation :-)) about them on   5     http://axp623.gsi.de:8080/www/vms/qaa/undoc.htmlxo 						[zinser@axp603.gsi.de]   Also see the following:S  -     http://www.levitte.org/~ava/vms_tip.htmlx =                                                 [Arne Vajhj]   C Various examples of undocumented features are also available on them OpenVMS Freeware:n  ,     http://www.openvms.digital.com/freeware/  @ DOC9.   Where is documentation on the DECnet Phase IV protocols?< ------------------------------------------------------------  3 Specifications for DECnet Phase IV can be found at:p  ?     http://gatekeeper.dec.com/pub/DEC/DECnet/PhaseIV/index.htmlt  < ------------------------------------------------------------G DOC10.  Where can I learn about how the VMS executive works internally?p  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 nD are no longer accurate, it continues to provide a strong conceptual " description of OpenVMS internals.   I This book has been split into five pieces, each to be updated separately.-M The first such volume, published in early 1997, was "OpenVMS Alpha Internals eG and Data Structures: Scheduling and Process Control," which covers the sM Version 7.0 implementation of true multithreading and the changed scheduling e model it implies.n  F The internals books are available through Digital Press, an imprint ofC Butterworth-Heinemann. You can order by phone (from US and Canada, tF 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 e8 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.5OA 1 55558 059 9  VAX/VMS Internals and Data Structures: Version 5.2e   					[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-specificeH 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:s  '     http://www.openvms.digital.com:800/a  C Some of the OpenVMS books available from the Butterworth-Heinemann n2 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 Edition.        Patrick Holmay         ISBN 1 55558 203 6p          Introduction to OpenVMS        David W Bynon        ISBN 1 878956 61 2.  &        OpenVMS System Management Guide        Richard Berry        ISBN 1 55558 143 9o  )        Using DECwindows Motif for OpenVMSe        Margie Sherlock        ISBN 1 55558 114 5n  3        Writing Real Programs in DCL, Second Edition "        Hoffman and Anagnostopoulos        ISBN 1 55558 191 9n  1   For various features OpenVMS books, please see: 5     http://www.openvms.digital.com/openvms/books.htmlr  B   Various user-maintained websites are also available, including aD   beginner's FAQ, various user-written FAQs, a bibliography of booksD   on OpenVMS, and information on various other hardware and software	   topics:   -     http://www.levitte.org/~ava/vms_faq.htmlxn.     http://www.levitte.org/~ava/vms_book.htmlx4     http://seqaxp.bio.caltech.edu/www/vms_sheet.html<     http://seqaxp.bio.caltech.edu/www/vms_beginners_faq.html?     http://multivac.jb.man.ac.uk:8000/helbig/BOOKMARKS/VMS.HTMLo  D   Members of the DECUS DFWLUG maintain a website with many materialsE   available, including an Overview of OpenVMS, an Introduction to DCLi>   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 totA   OpenVMS Cluster Management.  These training materials have been B   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) for OpenVMS at:  ,     http://www.compaq.com/training/home.html  ?   An OpenVMS certification (testing) program is also available.m  (   The following URL has an OpenVMS Quiz:      http://www.jcameron.com/vms/     [End of Part 1/5]V Article 44245 of comp.os.vms:a. Path: mailint03.im.hou.compaq.com!not-for-mail2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)W Newsgroups: comp.os.vms,comp.sys.dec,vmsnet.alpha,vmsnet.misc,comp.answers,news.answersy; Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/5e Followup-To: posterl Date: 18 Mar 2000 01:57:57 GMT) Organization: Compaq Computer Corporation- Lines: 1934 & Approved: news-answers-request@mit.edu Distribution: worldd! Expires: 17 Aug 2000 00:00:00 GMTU6 Message-ID: <8aunr5$s0p$2@mailint03.im.hou.compaq.com>6 References: <8aunn5$s0p$1@mailint03.im.hou.compaq.com>' Reply-To: hoffman@xdelta.zko.dec.nospamn% NNTP-Posting-Host: xdelta.zko.dec.coma\ X-Trace: mailint03.im.hou.compaq.com 953344677 28697 16.32.80.251 (18 Mar 2000 01:57:57 GMT)3 X-Complaints-To: usenet@mailint03.im.hou.compaq.comr* NTP-Posting-Date: 18 Mar 2000 01:57:57 GMTJ Summary: This posting contains answers to frequently asked questions aboutJ         the OpenVMS operating system from Compaq Computer Corporation, and.         the computer systems on which it runs.6 Supercedes: <8568k0$h32$1@mailint03.im.hou.compaq.com> Xref: mailint03.im.hou.compaq.com comp.os.vms:44245 comp.sys.dec:10405 vmsnet.alpha:428 vmsnet.misc:86 comp.answers:5469 news.answers:25533c       Archive-name: dec-faq/vms/part2M Posting-Frequency: monthly Last-modified: 17 Aug 2000 Version: VMS-FAQ-2.TXT(4)     9 This is the OpenVMS Frequently Asked Questions Part 2/5. p@ Please see Part 1/5 for administrivia, indexing, archiving, etc.      < ------------------------------------------------------------8 TIME1.   A brief history of OpenVMS Timekeeping, please?  =   Why does OpenVMS regards November 17, 1858 as the beginningc   of time...  D   The modified Julian date adopted by the Smithsonian Astrophysical B   Observatory (SAO) for satellite tracking is Julian Day 2400000, *   which turns out to be 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 w@   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,  E   the 14 bits left over by keeping the Julian date in its own 36-bit tD   word would have been wasted.  SAO also needed the fraction of the B   current day (for which 18 bits gave enough accuracy), so it was A   decided to keep the number of days in the left 18 bits and the e5   fraction of a day in the right 18 bits of one word.w  A   Eighteen bits allows the truncated Julian day (the SAO day) to eA   grow as large as 262143, which from November 17, 1858, allowed -B   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 i   calculations.d  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 aE   honor of his father, Julius Caesar Scaliger (note that this Julian pB   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 TD   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 g"   from 4713 B.C. through 3267 A.D.  E   The starting year was before any historical event known to him.  IneE   fact, the Jewish calendar marks the start of the world as 3761 B.C.sG   Today his numbering scheme is still used by astronomers to avoid the eF   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/i     http://www.nist.gov//     http://www.bldrdoc.gov/timefreq/faq/faq.htmF)     http://www.boulder.nist.gov/timefreq/   E   are all good time-related resources, some general and some specific-
   to OpenVMS.-      < ------------------------------------------------------------3 TIME2.   How does OpenVMS VAX maintain system time?m  ?   VAX systems maintain an interval clock, and a hardware clock.s  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").   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 and,J   retrieved from the system image, to initialize the interval clock value #   that is stored in EXE$GQ_SYSTIME.t  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 mD   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 L8   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 pJ   problems in VAX systems do regularly get tracked back to a failed nicad    or lithium battery pack. 					[Stephen Hoffman]  < ------------------------------------------------------------' TIME3.   Why does my system time drift?   D   Memory errors, hardware problems, or most anything operating at orD   above IPL 22 or IPL 24 (clock IPL is system family dependent; codeB   executing at or above the clock IPL will block the processing ofE   clock interrupts), can cause the loss of system time.  Clock drift  E   can also be caused by normal (thermal) clock variations and even 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  B   will "loose" time, and the time value reported to the user with A   appear to have slowed down.  Correctable memory errors can be ao3   common cause of system time loss, in other words.o  G   Clock drift can also be (deliberately) caused by the activity of the u   DTSS or NTP packages.n  $   Also see ALPHA17, VAX8, and TIME8.  < ------------------------------------------------------------D TIME4.   Managing Timezones, Timekeeping, UTC, and Daylight Savings?  -   You will want to use the command procedure:n  #     SYS$MANAGER:UTC$TIME_SETUP.COM a  I   to configure the OpenVMS Timezone Differential Factor (TDF) on OpenVMS /H   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 t=   timezone rules needed or used by other software packages.  a  A   Please do NOT directly invoke the following command procedures:a  =     SYS$MANAGER:UTC$CONFIGURE_TDF.COM   ! do not directly use,=     SYS$MANAGER:UTC$TIMEZONE_SETUP.COM  ! do not directly usee  G   TCP/IP Services V5.0 and later use the OpenVMS TDF, UTC, and timezoneeF   support.  Earlier versions use a TDF mechanism and timezone databaseG   that is internal to the TCP/IP Services package.  Also on the earlierlG   versions, the TDF must be manually configured within TCP/IP Services,-6   in addition to the OpenVMS configuration of the TDF.  G   DECnet-Plus in V7.3 and later uses the OpenVMS TDF, UTC, and timezoneoH   support.  Earlier versions use a TDF TDF mechanism, timezone database,H   and automatic switch-over that is internal to the DECnet-Plus package.A   Also on earlier versions, the TDF must be configured within the-G   DECnet-Plus DECdtss package, in addition to the OpenVMS configurationt
   of the TDF.a  G   Application code using Compaq C (formerly DEC C) will use the OpenVMSdH   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 declarationi   _VMS_V6_SOURCE is declared.B     DCE DTSS TDF details TDB.b  E   In OpenVMS Alpha V6.1, V6.2, and V6.2-1Hx, the TDF value is written.D   to SYS$BASE_IMAGE.EXE.  With OpenVMS Alpha V7.0 and later and withF   OpenVMS VAX V6.0 and later, SYS$SYSTEM:SYS$TIMEZONE.DAT contains theG   TDF.  This means that OpenVMS Alpha systems will need to have the TDFp2   value reset manually on reboots prior to V7.0.    I   During OpenVMS Bootstrap, the SYSINIT module reads SYS$TIMEZONE.DAT to vI   acquire the TDF for use in the system global cell EXE$GQ_TDF.  This is tH   done to ensure that the system boots with a valid TDF. The UTC system F   services get the TDF from this cell. These services, as well as the I   Compaq C RTL, must have a valid TDF.  (Prior to OpenVMS V7.3, if eitheraG   DECnet-Plus or DECnet/VAX Extensions is configured and run, the imageoI   DTSS$SET_TIMEZONE.EXE is invoked and can override the TDF and timezone  K   rule settings from SYSINIT or from UTC$TIME_SETUP.COM -- this image runs rK   even if DTSS is disabled.  If the settings do not match, DTSS will reset G'   the values to match its definitions.)/  D   Prior to OpenVMS V7.3, daylight savings time switchover is handledE   automatically only when DCE DTSS or DECnet-Plus DTSS is in use.  InvA   V7.3, OpenVMS can be configured to automatically switch over to D   daylight savings time, and also generates an event that interestedF   applications can use to detect the switch-over between standard time   and daylight time.  G   The manual switchover between daylight savings time and standard time E   is correctly accomplished via the SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM-   command procedure procedure.  G   If you switch the TDF or daylight savings time setting, you will also H   want to restart or reconfigure any time-sensitive applications (those H   not using the time change event in V7.3 and later).  Examples of theseH   applications include the need to restart the NFS client and (yes) NTP.G   (NTP will want to try to "drift" the time (see TIME6), and will find lG   the daylight savings time switch-over to be far too large to "drift". F   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.a     Prior to V7.3, the command:-        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.-  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 aC   Reference Manual -- though the title would imply otherwise, this sF   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?e  F   This is an OpenVMS Alpha system prior to V7.0 and the startup is not   invoking the procedure:e  !    SYS$MANAGER:UTC$TIME_SETUP.COMe  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 a   OpenVMS V7.3.  (DCE TDF TBD.)r  K   If you should find either of the following two timezone-related database s)   files located in SYS$SPECIFIC:[SYSEXE]:h  +     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DATi/     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DATo  H   These two files are in an erroneous location and must be recreated in    the correct directory:       SYS$COMMON:[SYSEXE].     If the DCL command:o  *     DIRECTORY SYS$SYSTEM:SYS$TIMEZONE*.DAT  G   shows these files in SYS$SPECIFIC:[SYSEXE], then delete them and use n2   SYS$MANAGER:UTC$TIME_SETUP.COM to recreate them.  1   On OpenVMS versions prior to V7.3, if the file:g  $     SYS$STARTUP:DTSS$UTC_STARTUP.COM  9   is present on your system, then you may need to invoke:   -     SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COMs  @   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 youro>   system, then you may need to execute the following commands:  +     DELETE SYS$STARTUP:DTSS$UTC_STARTUP.COMe+     DEASSIGN/SYSTEM/EXEC SYS$TIMEZONE_RULE.g  < ------------------------------------------------------------= TIME6.   How can I keep the OpenVMS system time synchronized?r  F   To help keep more accurate system time or to keep your system clocksG   synchronized, TCP/IP Services NTP, DECnet-Plus DECdtss, DCE DTSS, andMF   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 otherh   authoritative site.r  C   There exists code around that processes the digital (ie: binary) VD   format time that is available via a modem call into the NIST clockC   (the Automated Computer Telephone Service (ACTS)), and code that k@   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 4@   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 formatsC   (IRIG-A, -B, -G), a binary signal containing the current time in iG   hours, minutes, seconds and days since the start of the current year.sG   IRIG can also contain the time of day as the number of seconds since nI   midnight.  Compaq Custom Systems and third-party vendors offer various p:   IRIG-based reader/generator modules for OpenVMS systems.  G   Differing time servers (DECnet-Plus DTSS, DCE DTSS, NTP, etc) do not .F   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 iI   another protocol, but one and only one time server package should have tJ   direct control over the management of and drifting of the local OpenVMS    system time.)o     Useful URLs:8     http://www.boulder.nist.gov/timefreq/service/nts.htm9     http://www.boulder.nist.gov/timefreq/service/acts.htma)     http://www.boulder.nist.gov/timefreq/v     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 NTPmE   clients via the NTP protocol.  Most systems are NTP clients, but...e  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), lG   the lower the strata (and the larger the number assigned the statum).   H   NTP explicity configured at stratum one provides time to NTP operatingG   at lower strata, and the provided time is acquired based on the local B   system time or via some locally-accessable external time source.  J   NTP at other (lower) strata both receive time from higher strata and canK   provide time to lower strata, and automatically adjust the local stratum.MJ   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 clock-I   is the LCL (local system clock).  If your system has an excellent clockrF   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 asmH   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:c       server 127.127.1.0 prefers     fudge 127.127.1.0 stratum 0r  G   For local-master functionality, the commands are very similiar.  Use:y       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 to-G   act as a backup NTP server, or potentially as the sole time server onyI   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.i  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 annK   NTP client to an NTP server (on TCP/IP Services versions prior to V5.0),  H   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:t  *     SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE  8   For current TCP/IP Services documentation, please see:  N http://www.openvms.digital.com:8000/72final/6526/6526profile_015.html#ntp_chap    < ------------------------------------------------------------1 TIME8.   How can I drift the OpenVMS system time?J  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 usinge8   the support for this provided directly within OpenVMS.  G   An example of the technique used (on OpenVMS VAX) to drift the systemg4   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 cD   the standalone BACKUP image, an ECO that replaces SYS.EXE, etc).    G   The SET TIME command is automatically issued during various standard oK   OpenVMS procedures such as SHUTDOWN, and it can also obviously be issued  H   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.p  H   This VAX TOY limit is the reason why OpenVMS VAX installation kits andI   standalone BACKUP explicitly prompt for the time during bootstrap, and -G   why the time value can "get weird" if the system crashes outside the aI   497 day window (if no SET TIME was issued to update the saved values), dK   and why the time value can "get weird" if a different SYS$SYSTEM:SYS.EXE l:   is used (alternate system disk, standalone BACKUP, etc).   [End of Part 1/5]   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 17 Aug 2000 22:01:01 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/5r6 Message-ID: <8nhnat$3eo$1@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part2  Posting-Frequency: monthly Last-modified: 17 Aug 2000 Version: VMS-FAQ-2.TXT(4)a    9 This is the OpenVMS Frequently Asked Questions Part 2/5. I@ Please see Part 1/5 for administrivia, indexing, archiving, etc.      < ------------------------------------------------------------# MGMT1.  What is an installed image?l  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 uH (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 oflK enhanced properties.  For example, when you issue the SET PASSWORD command,bI the image SYS$SYSTEM:SETP0.EXE is run.  That image needs to have elevatedl# privileges to perform its function.o  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 Programminge% Concepts Manual for further details.)a  M It's important to note that there is no such thing as "installing a shareablelH 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 alsolK that in many cases the need to grant privileges to an image can be replacedPG with the use of the "Protected Subsystems" feature that grants a rights-E identifier to an image.  See the OpenVMS Guide to System Security forh$ 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 systemaJ or the file system against hostile action by programs.  On these operatingK systems, any running program can subvert the operating system and take over$K the hardware, at which point it can do anything it wishes, including hidingI9 copies of itself in other programs or in the file system.e  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  F 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 thataJ 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 ofi email messages or web access.o  K It is possible for OpenVMS, etc., to be infected by viruses, but to do so, sI the program containing the virus must be run from a user account that hasnJ amplified privileges.  As long as the system administrator is careful thatK only trusted applications are run from such accounts (and this is generally + the case), there is no danger from viruses., 					[Paul Winalski] 					[Stephen Hoffman]  G To protect against viruses and other attempts at system interference orpO 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).e  % [Contributions to this list welcomed]h  < ------------------------------------------------------------1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?   5 ISO-9660 support was added in the following releases:l       OpenVMS VAX V6.0     OpenVMS AXP V1.5  @ An add-on ISO-9960 kit was also available for OpenVMS VAX V5.5, = V5.5-1, V5.5-2, and V5.5-2H4.  This requires the installation ? of the F11CD kit from the InfoServer CD, from the Consolidated DB Distribution CD under the InfoServer area, Customer Support Center? kit CSCPAT #1071012, or the F11CD ECO kit.  (Upgrades to V6 ande  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]l  > In most circumstances, you will not need nor will you want to = include an explicit /MEDIA_FORMAT specification.  For furtherX> information, please refer to the OpenVMS MOUNT Utility Manual.= Particularly note the information on the MOUNT /MEDIA_FORMAT i and /UNDEFINED_FAT qualifiers.  9 The MOUNT /UNDEFINED_FAT qualifier is of interest becausen= ISO-9660 media can be mastered on a wide variety of operating @ system platforms, and these platforms do not necessarily supportD the semantics needed for files containing predefined record formats.C The /UNDEFINED_FAT allows you to specify the default attributes forg6 files accessed from volumes using the ISO-9660 format.  + An example which works for most CD-ROMs is:o  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 MOUNTM> /UNDEFINED_FAT qualifier causes any file whose file attributes? are "undefined" to be returned with "stream" attributes with a T maximum record length 2048.a  @ On OpenVMS, the ISO-9660 format is (internally) considered to be= the ODS-3 file structure, while the High Sierra extensions tobA the standard are considered to be the ODS-4 file structure.  The  = Rock Ridge extensions are not currently available on OpenVMS.t   					[Jim Dunham]  					[Stephen Hoffman]  < ------------------------------------------------------------4 MGMT4.  How do I extract the contents of a PCSI kit?  ? A growing number of OpenVMS products are being provided in PCSI E (POLYCENTER Software Installation) kits which are installed using the F PRODUCT INSTALL command.  These are alternatives to or replacement forD VMSINSTAL kits which were BACKUP savesets.  PCSI kits are not BACKUP< savesets and are structured differently from VMSINSTAL kits.  H If you want to extract product files from a PCSI kit, create a directoryD into which the kit should be expanded and use the following command:  8     $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] -5       /DEST=[destination-directory] /FORMAT=REFERENCE   ? A PCSI kit file has a file specification of the following form:e  '     DEC-VAXVMS-FORTRAN-V0603-141-1.PCSI   G In this example, "FORTRAN" is the "prodname".  PCSI will expand the kitSD files into the directory you specify and subdirectories beneath suchI as [SYSEXE], [SYSLIB], etc., reflecting the eventual destination of fileshH found there.  Most of the actual product files (images, etc.) will be inG the subdirectories.  In the top-level directory will be a file with theSH file type PCSI$DESCRIPTION that specifies where various files should go.G For more details, see the POLYCENTER Software Installation Developer's  E Guide for OpenVMS, which can be found in the OpenVMS documentation ons- the Consolidated Online Documentation CD-ROM.$  < ------------------------------------------------------------; MGMT5.  I've forgotten the SYSTEM password - what can I do?e  C If you need to break into an OpenVMS system because you do not haveSF access to any privileged passwords, such as the password to the SYSTEMG username, you  will need physical access to the system console, and you$B 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 involvepF       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 thecJ       SYSBOOT> utility.  (SYSBOOT allows conversational changes to system I       parameters.)  The syntax for the conversational bootstrap varies byiI       system model -- this typically involves specifying a flag of 1, forh       example:           VAX:
           B/1n           B/R5:1           @GENBOO            Alpha:           b -flags 0,1  I       If your system has a non-zero system root (such as root SYSE, showntJ       here), you will have to use a console command such as the following:           VAX:           B/E0000001           B/R5:E0000001i7           @<console media procedure name varies widely>r           Alpha:           b -flags e,1     E       If your system has a hardware password (various systems supportiG       a password that prevents unauthorized access to the console), youaF       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 havesF       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:            SET/STARTUP OPA0:U         SET WINDOWSYSTEM 0         SET WRITESYSPARAMS 0         CONTINUE  H   4.  At the $ prompt, the system will now be accepting startup commandsF       directly from the console.  Type the following two DCL commands:  
         SPAWN-         @SYS$SYSTEM:STARTUPc  I       The result of these two commands will be the normal system startup,dD       but you will be left logged in on the console, running under aE       privileged username.  Without the use of the SPAWN command, your5       would be logged out when the startup completes.   E       If necessary, you can skip the invocation of the system startup E       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=newpassworde         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 toa%    the value you specified in Step 5.a  M    Some people will suggest a method using the UAFALTERNATE SYSGEN parameter.PL    This approach is not always reliable and is not recommended, as there canK    easily be an alternate user authorization file configured on the system.y  L    For further information on emergency startup and shutdown, as well as forJ    the official OpenVMS documentation on how to change the SYSTEM passwordL    from the console in an emergency, please see the OpenVMS System Manager's+    Manual in the OpenVMS documentation set.   K    You can also use the conversational bootstrap technique shown above (the M    steps through Step 3) to alter various system parameters.  At the SYSBOOT>n/    prompt, you can enter new parameters values:7        SHOW MAXPROCESSCNT 
      SET . 64 
      CONTINUEb  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?h  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  - 
 		my_ip_queuew  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 #8 in the Release Notes and the DCPS$STARTUP.TEMPLATE file.   					[Steve Reece]5                                         [Arne Vajhj]h  < ------------------------------------------------------------? MGMT7.  Why can't I do a SET TIME command?  Help managing DTSS?   D If you try to set the system time with the SET TIME command, and see one of the following messages:  # %SET-E-NOTSET, error modifying timee0 -SYSTEM-F-IVSSRQ, invalid system service request  # %SET-E-NOTSET, error modifying timeeL -SYSTEM-E-TIMENOTSET, time service enabled; enter a time service command to  update the time     O A: This occurs if the time on the local system is controlled by a time service  O software, for example the distributed time service software (DTSS) provided as SP part of the DECnet/OSI installation. The DTSS software communicates with one or M more time servers to obtain the current time. It entirely controls the local  L system time (for DECnet/OSI, there is a process named DTSS$CLERK for this); P therefore, the usage of the SET TIME command (and the underlying $SETTIM system  service) is disabled.t  N The first message is displayed on systems running DECnet/OSI V6.1 and earlier.N On systems with newer DECnet/OSI (DECnet-Plus) software, the second (and more  informative) message is given.  I You shouldn't have to change the time manually - you should be doing thisbM through the time server - but if you insist...  you'll have to shutdown DTSS:   	 $ MCR NCLI NCL> DISABLE DTSSa 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$STARTUPI  M You'll need a lot of privs : (CMKRNL,SYSPRV,OPER,SYSNAM,PRMMBX,NETMBX,LOG_IO,sE ALTPRI) and must be granted the NET$MANAGE identifer to shutdown and i
 restart DTSS.y 					[bol@adv.magwien.gv.at]  O If you wish to "permanently" disable DTSS on a system running DECnet-Plus, the lJ above NCL sequence must be performed each time the system is bootstrapped.  N 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=1a7         eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0F-7         entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1B17         streamUid  D6513A46-6135-11D3-8003-AA000400BD1B   K You can either configure the appropriate number of time servers, or you canaG disable DTSS, or you can ignore it and (if OPCOM is set to write to the J log via via the logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE) clean out OPERATOR.LOG regularly.M    : You can also simply disable the display of these messages:  M $ mcr ncl block event dispatcher outbound stream local_stream global filter --,     ((Node, DTSS), Too Few Servers Detected)  @                                                   [Wayne Sewell]  < ------------------------------------------------------------) MGMT8 removed. superceded by TIME sectionT  < ------------------------------------------------------------; MGMT9.  How do I change the node name of an OpenVMS System?l  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 the :   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 theo	   system.e  @     Update the SCSNODE in MODPARAMS.DAT, and then run AUTOGEN as7       far as the SETPARAMS phase.  (Do not reboot yet.)e@     Modify the DECnet node name.  (NETCONFIG is the DECnet Phase:       IV tool, and NET$CONFIGURE is the DECnet-Plus tool.);     Modify the IP node name.  (The UCX tool is UCX$CONFIG.)a@     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 any D       local node-conditional operations present in the site-specificA       system startup, etc.  (SEARCH for the node name, specifyingn       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 name        to the new node name.d@     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.u  E   If the system is configured in a VMScluster and you change *either*SE   the SCSNODE or the SCSSYSTEMID -- but *not* both values -- then yougG   will have to reboot the entire VMScluster.  (The VMScluster rememberse>   the mapping between these two values, and will assume that aE   configuration problem has occured if a mismatched pair appears, andnH   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 p$   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 allt?   over the place, in layered products, and in local software...c   					[Stephen Hoffman]  < ------------------------------------------------------------E MGMT10. What is the correct value for EXPECTED_VOTES in a VMScluster?d  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 sufficientaJ 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 preventkJ 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,GI 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, believingeC 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 are-J established, meaning user data is at risk of severe corruption only during the initial system bootstrap.o  G One can operate a VMScluster with one, two, or many voting nodes.  WithnH any but the two-node configuration, keeping a subset of the nodes activeA when some nodes fail can be easily configured.  With the two-nodeoH 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) thataH would be assigned to the quorum disk makes for faster transitions -- butL the use of a quorum disk does mean that either node in a two-node VMScluster6 configuration can operate when the other node is down.  K In a two-node VMScluster with a shared storage interconnect, typically eachAI node has one vote, and the quorum disk also has one vote.  EXPECTED_VOTESU 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 assignedsH 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,aF 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.DE The IPC handler can be used to clear a quorum hang, and to clear disk- mount verification hangs.6  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 quorumSG mechanism to make your life more difficult -- quorum was implemented tor' keep your data from getting scrambled. t 						[Stephen Hoffman]i  < ------------------------------------------------------------< 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 existing-I definition of the PHYSICALPAGES (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMSrH Alpha) parameter in the SYS$SYSTEM:MODPARAMS.DAT parameter database, useH a text editor to reset the value in the file to the new correct value as1 required, and then perform the following command:t  /   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACKC  I This AUTOGEN command will reset various system parameters based on recentLJ 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 beeH 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.r  I PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on OpenVMS Alpha) or cK (better and simpler) the entry can be removed from the MODPARAMS.DAT file, c5 to indicate that all available memory should be used.r   						[Stephen Hoffman]   < ------------------------------------------------------------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 theM. node with the tape drive, create SAVE-SET.FDL:   RECORD%         FORMAT                  fixedR$         SIZE                    8192   Then create BACKUP_SERVER.COM:     $ !eA   $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.b   $ !t   $ set noon   $ set rms/network=16   $ allocate mka500 tapedevg4   $ mount/nounload/over:id/block=8192/assist tapedev2   $ convert/fdl=SAVE-SET sys$net tapedev:save-set.   $ dismount/unload tapedevo
   $ stop/id=0e    A On the node where you want to do the backup, use the DCL command:l     $ backup -      srcfilespec -9      node"user pwd"::"task=backup_server"/block=8192/savea  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 aaE 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).Y 						[Stephen Hoffman]y  < ------------------------------------------------------------3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSC0  K The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSC are used to connect hM to storage controllers via the Diagnostics and Utility Protocol (DUP).  These(K 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:n       $ RUN SYS$SYSTEM:SYSMANt;       SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVER        On OpenVMS VAX:e       $ RUN SYS$SYSTEM:SYSGEN $       SYSGEN> CONNECT FYA0/NOADAPTER  M Alternatives to the DCL SET HOST/DUP command include the console >>> SET HOSTlA command available on various mid- to recent-vintage VAX consoles:i  8     Access to Parameters on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMSt  @     Access to Directory of tools on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECTt  4     Access to Parameters on a KFQSA DSSI controller:;       >>> SHOW UQSSP ! to get port_controller_number PARAMST:       >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  I These console commands are available on most MicroVAX and VAXstation 3xxxlE series systems, and most (all?) VAX 4xxx series systems.  For furtherSK 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. eL This manual specifically covers the hardware, which is something not covered2 by the standard OpenVMS VMScluster documentation.)   						[Stephen Hoffman]   < ------------------------------------------------------------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 Servicesi (often known as UCX).G  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.s  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 acK distribution kit, simply answer "NO" to the question asking you if you wantsL 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.e  F If you already have DECnet-Plus installed and wish to revert, you mustN reconfigure OpenVMS.  You cannot reconfigure the "live" system, hence you mustJ reboot the system using the V7.1 distribution CD-ROM.  Then select the DCL. ($$$ prompt) option.  Then issue the commands:  *     $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0:0     $$$ DEVINE/STSTEM PCSI$SPECIFIC DKA0:[SYS0.]@     $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]  K The above commands assume that the target system device and system root aredH "DKA0:[SYS0.]".  Replace this with the actual target device and root, asK appropriate.  The RECONFIGURE command will then issue a series of prompts. tM You will want to reconfigure DECnet-Plus off the system, obviously.  You willdM then want to use the PCSI command PRODUCT INSTALL to install the DECnet Phases+ IV kit from the OpenVMS distribution media.   G Information on DECnet support, and on the kit names, is included in thea4 OpenVMS V7.1 installation and upgrade documentation.   						[Stephen Hoffman]	  < ------------------------------------------------------------< 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 basedfM on identifiers present in the OpenVMS rightslist.  Documentation on this areaf= is included in the _Guide to OpenVMS System Security_ manual.S  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:S  3     UAF> add/ident/value=uic=[group,user] newuseridr  M The UIC user identifier text is assigned when the username is created, and isvN 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 ofeL this identifier is [groupnumber, 177777]. To add a missing group identifier, use an asterisk as follows:o  1     UAF> add/ident/value=uic=[group,*] newgroupidB  M You may find cases where an identifier is missing from time to time, as theretJ 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 utilitytN 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 avoideJ 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 security  manual for details.S  < ------------------------------------------------------------3 MGMT16. What are the OpenVMS version upgrade paths?v  8    Note: See "OpenVMS Alpha Terminology" section, below.  3    OpenVMS Alpha release upgrade (or update) paths:t  (      From V1.0, one can upgrade to V1.5.5      From V1.5, or V1.5-1H1, one can upgrade to V6.1.f(      From V6.1, one can upgrade to V6.2.1      From V6.1, or V6.2, one can upgrade to V7.0.tG      From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0, one can upgrade to V7.1.TB      From V6.2, one can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.F      From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2, to V7.2-1(      From V6.2, ... or V7.2, to V7.2-1H1?      From V7.1, one can update to V7.1-1H(1,2), ... to V7.2-1H1   >      Some typical OpenVMS Alpha upgrade (or update) paths are:9          V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2)o5          V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2)-          V6.1 -> V7.2-          V6.2 -> V6.2-1H3o          V6.2 -> V7.2-1m          V6.2-1H(1,2,3) -> V7.1 !          V6.2-1H(1,2,3) -> V7.2-1e          V7.1 -> V7.1-1H(1,2)n          V7.1 -> V7.1-2e          V7.1 -> V7.2-1a          V7.1-1H(1,2) -> V7.2-1s          V7.2 -> V7.2-1H1n  G      Note that OpenVMS Alpha V7.0 does not include support for hardwaresE      and/or configurations first supported in OpenVMS Alpha V6.2-1H1,aA      V6.2-1H2, or V6.2-1H3; one must upgrade to OpenVMS VAX V7.1.n  F      One cannot update directly to a V6.2-1Hx Limited Hardware ReleaseD      (LHR) from any release prior to the baseline V6.2 release.  TheG      same prohibition holds for performing updates directly to V7.1-1Hx F      from any release prior to V7.1 -- this is not supported, and doesE      not produce the expected results.  The LHR kits can, however, bemE      directly booted and can be directly installed, without regard toaC      any operating system that might be present on the target disk.s  F      OpenVMS Alpha updates for LHRs (through V7.1-1Hx) require the useF      of VMSINSTAL for the update.  These LHR releases use PCSI for theE      installation, but not for the update.  Non-LHR releases use PCSI !      for installs and upgrades.  o  F      OpenVMS Alpha V7.1-2 and later use PCSI for LHRs and for OpenVMS C      upgrades and for all OpenVMS ECO kit installations.  VMSINSTALeE      OpenVMS ECO kits are not used on OpenVMS Alpha V7.1-2 and later.eD      Prior to V7.1-2, VMSINSTAL-based ECO kits are used for OpenVMS.    %    OpenVMS VAX release upgrade paths:i  A      From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5. ?      From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.t;      From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.a=      From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1.e1      From V6.0, or V6.1, one can upgrade to V6.2.e1      From V6.1, or V6.2, one can upgrade to V7.0. 7      From V6.1, V6.2, or V7.0, one can upgrade to V7.1. D      From V6.1, one can upgrade to V7.2 (with VAXBACK ECO for V6.1).  0      Some typical OpenVMS VAX upgrade paths are:8          V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.0, or V7.1)          V5.5-2HW -> V5.5-2d=          V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)e)          V6.1 -> VAXBACK V6.1 ECO -> V7.2e          V6.2 -> V7.2e  E      Note that OpenVMS VAX V6.0 does not include support for hardwarelC      and/or configurations first added in OpenVMS VAX V5.5-2H4, one &      must upgrade to OpenVMS VAX V6.1.  G      Note that OpenVMS VAX V5.5-2HW is a pre-release version of V5.5-2.tB      Any system running it should be upgraded to V5.5-2, or later.    $    OpenVMS Cluster Rolling Upgrades:  F      Rolling Upgrades require multiple system disks.  Rolling upgradesL      permit the OpenVMS Cluster to remain available while individual systems1      are being upgraded to a new OpenVMS release.c  L      OpenVMS Cluster rolling upgrades for both OpenVMS VAX and OpenVMS AlphaG      may (will) have different, or additional upgrade requirements, andnC      have requirements around which versions of OpenVMS can coexistr3      in a OpenVMS Cluster than what is listed here.c  K      See the _OpenVMS <platform> Version <Version> Upgrade and Installationu;      Manual_, and the OpenVMS Software Product Descriptions   *        http://www.digital.com/info/SPHOME/  O      for further details on the rolling upgrade, and for support information.   I      The documentation for older releases of OpenVMS VAX includes variousmF      platform-specific manuals, manuals that include instructions that>      are specific to installing and upgrading on the platform.    7    OpenVMS and Layered Products -- Support Information:T  @      For information on Prior Version Support and Mature Product<      Support (including information on support end dates for7      OpenVMS and various layered products), please see:c  =        http://www.compaq.com/services/software/ss_mature.htmls  C      For information on supported versions of layered products, and 4      minimum required layered product versions, see:  B        http://www.openvms.digital.com/openvms/os/swroll/index.html  A      For information on the release history of OpenVMS, including >      information on the code names of various releases and the      major features:  M        http://www.openvms.digital.com/openvms/os/openvms-release-history.htmlu  D      Additional release history information, as well as a variety ofA      other trivia, is available in the VAX 20th anniversary book:c  >        http://www.openvms.digital.com/openvms/20th/vmsbook.pdf      OpenVMS Alpha Terminology:a  B      update:    Typically used for Limited Hardware Releases (LHR)A                 releases.  Performed via VMSINSTAL.  Applies onlyo@                 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 allnG                 files and features of previous LHRs in the same series.   F      upgrade:   Performed via PCSI.  Upgrades can typically be appliedE                 to a release-specific (and documented) range of priort!                 OpenVMS releases.S  F      install:   Performed via PCSI.  With an installation, no existingG                 version of the operating system is assumed present, norhI                 are any files from any copy of the operating system mightcK                 be present preserved, and the entire contents of the targetl=                 disk are destroyed via a disk initialization.o  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 operatingi>                 system files on the target disk are clobbered.  G      LHR:       Limited Hardware Release.  LHRs are specific to and areaD                 targeted at new hardware configurations, and are notF                 shipped to customers with support contracts.  At leastI                 one LHR kit must be specifically acquired when purchasinghI                 new hardware, new hardware that is not (yet) supported byIH                 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?t  E Seeing a negative number in the reservable pages portion of the SHOW aI MEMORY/FULL command can be normal and expected, and is (even) documented SD behaviour.  A pagefile with a negative number of reservable pages isK overcommitted, which is generally goodness assuming that every process withfL reserved pages does not try to occupy all of the reserved pagefile  space at the same time. m  L To understand how the pagefile reservation process works, think about  how aN traditional bank operates when accepting customer deposits and  making loans. L It's the same idea with the pagefile space. There is  less money in the bankM vault than the total deposits, because much of  the money has been loaned out H 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 bankingsI customers.  (Though there is  no deposit insurance available for pagefilea users.)E  L If all of the running applications try to use the reserved space, the systemG manager will need to enlarge the pagefile or add one or more additionalS
 pagefules.  L To determine if the pagefile is excessively overcommitted, watch for "doubleN overcommitment" -- when the reservable space approaches the  negatation of theG available total space -- and watch that the total  amount of free spaceuK available in the pagefile remains adequate.  If  either of these situationsb0 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 available E disk storage.  When multiple  pagefiles are present on recent OpenVMSuJ 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, see-H 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. VK Specifically, the required minimum versions for product support are listed.D  N Comprehensive Public Rollout Information, listing previous product versions asM well as currently shipping versions, has been compiled into a separate set ofcN 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,IJ 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:_=   http://www.openvms.digital.com/openvms/os/swroll/index.htmle   					[Stephen Hoffman]  < ------------------------------------------------------------3 MGMT19. How do I change the volume label of a disk?u  G   Dismount the disk, and mount it privately.  If the disk is mounted by4F   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 othera-   nodes that are bootstrapped from this disk.s  ?   Issue the SET VOLUME/LABEL command, specifying the new label.s  >   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 reflectv   the new disk volume label.  F   Locate any references in the system startup (typically including theJ   disk MOUNT commands) and any DISK$label references in application files,*   and change the references appropriately.  I   If this is a system disk (for the host or for a satellite), also check  I   the DECnet MOP or LANCP boot database, as well as any references to thes&   disk created by CLUSTER_CONFIG*.COM.  !   Remount the disk appropriately.C 					[Stephen Hoffman]:                                         [John E. Malmberg]  < ------------------------------------------------------------/ MGMT20.  How do I fix a corrupt BACKUP saveset?e  E   BACKUP savesets can be corrupted by FTP file transfers and by toolssC   such as zip (particularly when the zip tool has not been asked toeF   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]hD   directory).  The Freeware is available at various sites -- see theF   Freeware location listings elsewhere in the FAQ -- and other similar0   tools are also available from various sources.  E   In various cases (note that not all savesets use the default record +   size!), the following command might work:$  I     $ SET FILE/ATTRIBUTES=(RFM:FIX,MRS:32256,LRL:32256,RAT:NONE) file.bckR  K   Also see the "SITE VMS", /FDL, and various other file-attributes options tG   available in various FTP tools.  (Not all available FTP tools supportt   any or all of these options.)p  I   Browser downloads (via FTP) and incorrect (binary or ascii FTP transferoH   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):o       ftp://host/url?type=binary  H   You can also often configure the particular web browser to choose the E   appropriate transfer mode by default, based on the particular file -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.D   					[Stephen Hoffman]  < ------------------------------------------------------------- MGMT21.  How can I set up a shared directory?'  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.t  K The following also shows how to set up a resource identifier, which further/J allows the disk resources to be charged to the specified identifier ratherB than each individual user.  (If you don't want this, then omit theE attributes option on the identifier creation and omit the entry added  in the disk quota database.r  " Add an identifier using AUTHORIZE:3   ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifiere  ? Grant the identifier to each user in the group using AUTHORIZE:e+   GRANT/IDENTIFIER groupidentifier usernamea  A If disk quotas are in use, add an entry via SYSMAN for each disk:iF   DISKQUOTA ADD groupidentifier/PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:  J Set the shared directory to have an ACL similar to the following using theJ SET SECURITY (V6.0 and later) or SET ACL (versions prior to V6.0) command:(   (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W)O   (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE) ?   (IDENTIFIER=groupidentifier,ACCESS=READ+WRITE+EXECUTE+DELETE)s+   (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)g  K If there are files already resident in the directory, set their protectionstL similarly.  (The OPTIONS=DEFAULT, DEFAULT_PROTECTION, and CREATOR ACEs apply to directories.)  L The default protection mask is used to establish the default file protection@ mask, this mask does not prevent the users holding the specifiedK groupidentifier from accessing the file(s), as they can access the file via C the explicit identifier granting access that is present in the ACL.r  I For further information, see the OpenVMS Guide to System Security Manual,sL specifically the sections on ACLs and identifiers, and resource identifiers.  < ------------------------------------------------------------ MGMT22 relocated to SUPP3n  < ------------------------------------------------------------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.digital.com/wizard/7     http://www.openvms.digital.com/wizard/wiz_1020.html.  L   There are a variety of discussions of this and of related printing topics    in the Ask The Wizard area.p 					[Stephen Hoffman]  < ------------------------------------------------------------E MGMT24. Configure ELSA GLoria Synergy or PowerStorm 300/350 graphics?   E   On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the appropriate -;   GRAPHICS PCSI kit, and all prerequisite OpenVMS ECO kits:   "     VMS712_GRAPHICS-V0300 or later!     VMS72_GRAPHICS-V0100 or later "     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]3  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) )E   was once available, but has been superceded and is not recommended.rD   Use of V7.1-2 or later (and use of one the above GRAPHICS kits as +   required) is typically the best approach.p  D   OpenVMS V7.2-1H1 and later should directly support the controller.     ----     PowerStorm 300 : PBXGD-ACd   PowerStorm 350 : PBXGD-AEi  @   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: ,     DEC-AXPVMS-VMS712_P350-V0100--4 or later0     DEC-AXPVMS-VMS712_GRAPHICS-V0300--4 or later     For OpenVMS Alpha V7.2-1:e,     DEC-AXPVMS-VMS721_P350-V0100--4 or later0     DEC-AXPVMS-VMS721_GRAPHICS-V0300--4 or later     ----  D   Support for the ELSA GLoria Synergy and the PowerStorm 300 and 350E   controllers is expected to be integrated in the OpenVMS Alpha V7.3 d   and later releases.    					[Stephen Hoffman]  < ------------------------------------------------------------: MGMT25. How do I acquire OpenVMS patches, fixes, and ECOs?  N You can acquire and download kits containing OpenVMS fixes (ECOs) for various 
 releases via:5  $   http://search.service.digital.com/+   ftp://ftp.service.digital.com/public/vms/,'   http://ftp.digital.com.au/pub/ecoinfo0(   http://ftp/digital.com.au/cgi-bin/grep  3 You can subscribe to an email notification list at:o  :   http://www.service.digital.com/patches/mailing-list.html  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 or 2 individual notifications) directly from Compaq at:  =     http://www1.service.digital.com/patches/mailing-list.htmlp  B Examples and ECO kit installation instructions are included in the? cover letter.   For available ECO kits, cover letters and other5" 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.   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 n/   easy -- if you know the secret incantation...      From OpenVMS:i       $ RUN SYS$SYSTEM:SYSGENr"     SYSGEN> CONNECT FYA0/NOADAPTER     SYSGEN> ^Z=     $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>      ...S     PARAMS> STAT CONF C     <The software version is normally near the top of the display.>t     PARAMS> EXIT     ...a  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 PARAMS   
     KFQSA:  <         >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  G   For information on how to get out into the PARAMS subsystem, also seerH   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).r  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 namen2   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?l  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  J   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:s  O    0. Checkpoint the journal file.  This reduces the file size to the in-memory 8       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 locations       for safety.n 	aE 	$ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]         sN    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 all        nodes in the cluster e   	$ 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.  q  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]   < ------------------------------------------------------------> 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:i  4     $ TCPIP SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  '   For earlier TCP/IP Services versions:r  2     $ UCX SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  < ------------------------------------------------------------ MGMT29 relocated to ALPHA21s  < ------------------------------------------------------------C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?   C "Undeleteable" jobs are usually "undeleteable" for a reason -- thisnE can track back to insufficient process quotas, to a kernel-mode errortD 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 particularhD device supports firmware, ensure that the device firmware is currentG -- TQK50 controllers are known for this when working with old firmware.dG (That, and the infamous "MUA4224" firmware bug.)  If this device has a nD driver ECO kit available, acquire and apply it...  If the particular9 relevent host component has an ECO, acquire and apply it.S  D Useful tools include SDA (to see what might be going on) and DECamdsA (which increase and thus potentially fix quota-related problems).aB (nb: Applications with quota leaks will obviously not stay fixed.)  ? If the stuck application is BACKUP, ensure you have the currente@ BACKUP ECO and are directly following the V7.1 or (better) V7.2 ; process quota recommendations for operator BACKUP accounts.m  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 whomeversH 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.)i  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, theaD 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 gC mechanism to reset error counts once the error(s) have been logged.e  C As for an unsupported approach -- and be aware of the potential forn causing a system crash...   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 thetG device's UCB structure.  On VAX, the field is at an offset symbolicallytG defined as UCB$W_ERRCNT.  On Alpha, this field's offset is symbolically E defined as UCB$L_ERRCNT.  The former is a word in size; the latter iswE 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 williE see designations in {} separated by a /.  The first item in braces isoE to be used on the VAX and the second item should be used on an Alpha.  (ie.  {VAX/Alpha})   $ ANALYZE/SYSTEM2 SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBF SDA>  SHOW DEVICE <ddnc:>    ! device designation of device with error# SDA>  EVALUATE UCB+UCB${W/L}_ERRCNT-9 Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offset   1 Record the hexadecimal value 'hhhhhhhh' returned.   G You can now exit from SDA and $ RUN SYS$SHARE:DELTA or do what I prefer  to do, issue the following:e   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.  ForEI those unfamiliar with DELTA, it does not have a prompt and only one erroriI message -- Eh?  (Well, for sake of argument, there might be another errorlF 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?n   Now issue the command 1;Ml  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: 00010001b  . 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.rJ 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 carriagebH 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 asr* 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:c    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?v  6 For various SCSI-based MK-class magnetic tape devices:  6     $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2")     $ Comp_sup = %X00200000      $ Comp_ena = %X00400000e5     $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -a0         WRITE SYS$OUTPUT "Compression supported"5     $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_sup THEN - .         WRITE SYS$OUTPUT "Compression enabled"  < ------------------------------------------------------------? MGMT33. Can I copy SYSUAF to another version? To VAX? To Alpha?f  > The format of the SYSUAF.DAT, RIGHTSLIST, and associated files= are upward-compatible, and compatible across OpenVMS VAX and o9 OpenVMS Alpha systems.  (This compatibility is a a basic  < 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 -6 RIGHTSLIST files that will make this more interesting.  @ The same basic steps necessary for moving RIGHTSLIST and SYSUAF ? files to another node are rather similar to the steps involved sA in merging these files in an OpenVMS Cluster -- see the appendix eB of the OpenVMS Cluster documentation for details of merging files.C (You might not be merging the contents of two (or more) files, but r? you are effectively merging the contents of the files into the   target system environment.)r   Considerations:e  >   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 o>     on the contents of the NETPROXY.DAT during the OpenVMS VAX;     V6.1 upgrade and during the OpenVMS Alpha V6.2 upgrade.r:     This file is maintained in parallel with NETPROXY.DAT.  =   o the RIGHTSLIST identifier values and UIC values that end E?     up scattered around the target system must be rationalized t=     with the contents of the new RIGHTSLIST and SYSUAF files.D  < The lattermost case -- resolving the identifier values -- is= often the most interesting and difficult part.   If you find S> that an identifier value (or identifier name) from the source ? RIGHTSLIST collides with that of an identifier existing on the f? target system, you must first determine if the two identifiers h= perform the same function.  In most cases, they will not.  As)= such, you will have to find and chance all references to the n< 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 p> alphanumeric value for the identifier being displayed, you'll ? simply see the binary format for the identifier displayed, and T? no particular access will be granted.  And any DCL commands or t@ 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 associatedn7 with disks, ACLs, queues, and various other structures.-  < For a list of the various files shared in an OpenVMS Cluster< and that can be involved when relocating an environment from= one node to another (or merging environments into an OpenVMS a> Cluster), please see the SYLOGICALS.TEMPLATE file included in   OpenVMS V7.2 and later releases. 					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT34. How do I delete (timeout) idle processes?B  F   There is no such command integrated within OpenVMS, though there areI   (optional) timers available within certain terminal servers and similarPI   devices, and there is an integrated time-of-day mechanism that provides .   control over when a user can access OpenVMS.  K   As for available tools, there are DECUS, freeware, and third-party tools rJ   known variously as "idle process killers" or terminal timeout" programs.H   Examples include: Saiga Systems Hitman, Watchdog, MadGoat Watcher (via=   the MadGoat site or the OpenVMS Freeware), Kblock, and Zap.   ;   A related package (for DECwindows sessions) is xtermlock.   I   If the forgetful users are in an application menu environment, the menu,9   can potentially be extended to provide this capability.   < ------------------------------------------------------------. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?  H   If you are seeing more files backed up than previously, you are seeingF   the result of a change that was made to ensure BACKUP can perform anI   incrementation restoration of the files.  In particular, if a directory J   file modification date changes, all files underneath it are included in L   the BACKUP, in order to permit incremental restoration should a directory    file get renamed.-  8   Why has OpenVMS gone through the agony of this change?  H     When a directory is renamed, the modified date is changed.  When theH     restoration needs to restore the directory and its contents, and theK     restoration should not result in the restoration of the older directoryiD     name when a series of incremental BACKUPs are restored.  Thus anE     incremental BACKUP operation needs to pick up all of the changes.t  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 iK     OpenVMS versions (and ECO kits).  Use of this qualifier informs BACKUP aM     that you are aware of the limitations of the old BACKUP behaviour around t"     incremental disk restorations.  I   Consider performing an incremental restoration, to test the procedures. G   Attempting this is how we found out about the problem that was latentSF   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)?s  H   Though it may seem obvious, Telnet and LAT are quite different -- with*   differing capabilities and design goals.  E   Please see the documentation around the TCP/IP Services for OpenVMSSG   TELNET command CREATE_SESSION.  This command is the equivilent of thefG   operations performed in LTLOAD.COM or LAT$SYSTARTUP.COM.  There is noTH   TELNET equivilent to the sys$qio[w] control interface for LTDRIVER (asC   documented in the I/O User's Reference Manual) available, though sD   standard sys$qio[w] calls referencing the created TN device would    likely operate as expected.   < ------------------------------------------------------------? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?   D   DECevent and Compaq Analyze are avalable to customers with supportE   contracts.  The PAK is required only for the advanced functions of FE   DECevent, the basic bits-to-text translation of the error log does mB   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 uE   contract or warrantee, and the PAK enables the use of the advanced S@   error analysis and notification capabilities within DECevent.)  5   Please see the DECevent FAQ for additional details:p  A http://www.support.compaq.com/svctools/decevent/DECevent_FAQ.htmls  ?   The current version of the DECevent (Compaq Analyze) tool cana   be downloaded from:s  7 http://www.support.compaq.com/svctools/st-download.htmlr  < ------------------------------------------------------------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 uD 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 DCLAB INITIALIZE command is known to encounter access violation (ACCVIO) errors.N  C The available solutions include upgrades, or setting the date back.rE Direct initialization of the tape with the new headers (via $qio) is [G also clearly possible, though the limitation within the old MTAACP.EXE w2 magtape ACP image is not nearly so easy to bypass.  B                                                [Hoffman, Dachtera]  < ------------------------------------------------------------/ MGMT39. How do I recover from INSVIRMEM errors?t  ?   Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX releases, MC   VIRTUALPAGECNT and PGFLQUOTA limit the amount of virtual address $,   space that is available to each process.    E   Further limiting the amount of address space is the size of system CC   space (S0 and S1 space).  On OpenVMS Alpha versions prior to V7.0aD   and on all OpenVMS VAX releases, VIRTUALPAGECNT and MAXPROCESSCNT E   together determine the size of the page table data structures that -G   occupy large tracts of system space.  When no system virtual address oE   space is available for the stuff that needs it -- this includes theoC   page tables, non-paged pool, and various other structures -- thenxE   the values of VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.   G   In OpenVMS Alpha V7.0 and later, the page table data structures have -C   been moved out of S0 and S1 space and into page table space.  In -D   OpenVMS Alpha V7.2 and later, certain large data structures found E   in non-paged pool (eg: lock management structures) have been moved aB   into 64-bit space, thus freeing up room in non-paged pool and inG   S0 and S1 space (where non-paged pool resides) while also permitting S    much larger data structures.    < ------------------------------------------------------------I MGMT40. How can I prevent a serial terminal line from initiating a login?a  *   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 upaB   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 eK   16 bytes long, and is used as a counted string of 0-15 characters (ie, a tJ   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 y%   an image should be replaced or not.d  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 in M   the product descripton file (PDF) of a PCSI kit as the basis for performingrH   file conflict detection and resolution.  When a product is installed, I   PCSI modifies the build ident field of Alpha image headers to store an  K   encoded form of the generation number.  It also looks at the build ident aL   field of previously installed images to obtain the generation information K   for those files as input to the file conflict processing algorithm. (Only %   images have this field, obviously.)   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 gJ       last ten characters are a ten digit number with leading zeros, then G       the last ten characters are treated as a valid generation number.tI     - for V7.1-2 through V7.2-1, inclusive, if the above test fails, the  =       information is obtained from the PCSI product database.fL     - 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 dI       that the ECO kit will simply replace the image rather than assumingm$      the PCSI database is in error.  E   So, what will you see in the image identification displayed via thew   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 hD   "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 thatB'   have not yet been processed via PCSI.m  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, AL   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.h  < ------------------------------------------------------------@ MGMT42. How to configure allocation classes and Multi-Path SCSI?  K The HSZ allocation class is applied to devices, starting with OpenVMS V7.2.rL 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 thistJ 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 sE class to zero, and setting the PKB PAC to -1.  This will use the hosttG allocation class, and will leave the controller letter alone (that is, uL the DK controller letter will be the same as the SCSI port (PK) controller).H Note that this won't work if the HSZ is configured in multibus failover G mode.  In this case, OpenVMS requires that you use an allocation class h for the HSZ.  J When your configuration gets even moderately complex, you must pay carefulK attention to how you assign the three kinds of allocation class: node, porttI and HSZ/HSJ, as otherwise you could wind up with device naming conflicts l that can be painful to resolve.   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 rG device.  If you have two paths to $1$DKA100, for example by having two aI KZPBA controllers and two SCSI buses to the HSZ, you would have two UCBs  E in a multi-path set.  The path information is used by the multi-path  / software to distinguish between these two UCBs.e  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.n  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, mJ 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 mF more deterministic than negotiating the controller letter between the I nodes, and also parallels the solution used for this situation when DSSI a or SDI/STI storage was used.  I This information is also described in the Cluster Systems and Guidelines  + for OpenVMS Cluster Configurations manuals.h;                                                [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 thisiA   determination -- this is one of the reasons that a move to PCSId   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.   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 (form=   software that is installed via VMSINSTAL on V7.3 and later)b   in VMSINSTAL.HISTORY.t  ;   For products installed on OpenVMS VAX prior to V7.3 usinga@   VMSINSTAL, there is no reliable way to determine what products?   have been installed.  If the product provides a RELEASE_NOTESf=   file (as many do), you can look for the list of these filesh?   via DIRECTORY SYS$HELP:*.RELEASE_NOTES.  Again, this approacht@   is NOT reliable: some kits do not provide release notes, some C   system managers will install only the release notes, some system fE   managers will delete release notes, and release notes for multiple a   versions can be present.  E   On most packages, you can generally use ANALYZE/IMAGE on one of the,E   core images, looking at the image identification area.  Some of then,   product-specific mechanisms available are:  "     DQS   DQS$VERSION logical name     C     CC/VERSION     C++   CXX/VERSIONo    < ------------------------------------------------------------@ 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,tK   and there is no way to remove it.  You can, however, remote site-specificdB   tailoring that was added for a particular cluster configuration.  G   First: Create restorable image BACKUPs of each of the current system iH   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 system >   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 anyB   other roots, save them.a  E   Relocate the copies of the VMScluster common files onto each of thea   new system disks.r  D   Reset the console parameters and boot flags on each system for use   on a standalone node.i  D   Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters to 0 in SYSGEN   and in MODPARAMS.DAT.,  <   Clobber the VMScluster group ID and password using SYSMAN.  9   Reboot the systems seperately, and run AUTOGEN on each.c  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  I   http://www1.service.digital.com/svctools/decevent/md5-instructions.htmla  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.o  < ------------------------------------------------------------9 MGMT47.  Configuring Cluster SCS for path load balancing?i    G SCS: Systems Communication Services.  The protocol used to communicate rD 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 cF 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 oH 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:   *   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 VMSClustere9     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 VMSClustero:     systems that have SYSGEN parameter TMSCP_LOAD set to 1  +   VMS$VAXCLUSTER connects to VMS$VAXCLUSTERs>     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.s  *   SCS$DIR_LOOKUP connects to SCS$DIRECTORY7     This SYSAP is used to find SYSAPs on remote systemsa     MSCP and TMSCP n?     The Mass Storage Control Protocol and the Tape MSCP serversm=     are SYSAPs that provide access to disk and tape storage, p<     typically operating over SCS protocols.  MSCP and TMSCP ;     SYSAPs exist within OpenVMS (for OpenVMS hosts serving I8     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 SCSIt1     and other non-MSCP/non-TMSCP storage devices.y  I SCS CONNECTION: A SYSAP on one node establishes an SCS connection to its 1J 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 tF 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 i1 will then travel on the selected virtual circuit.t  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 EF 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 fF 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 eG system disk, and thus will always be the first DSSI bus discovered whene the OpenVMS system boots.n  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, eG permitting failover to occur should congestion or a problem arise -- a hH 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 n) a problem with a virtual circuit arises. l  E In the case of PEDRIVER, the driver handles load balancing among the gD available Ethernet and FDDI connections based on the lowest latency E path available to it.  Traffic will be routed through that path untile* an event occurs that requires a fail-over.  / In all OpenVMS versions, you can use the tools:a     SYS$EXAMPLES:LAVC$STOP_BUS     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 gH 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 lH 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.s  7 Prior to V7.2, the prefered path feature uses the tool:a     SYS$EXAMPLES:PREFER.MAR   A In OpenVMS V7.2 and later, you can use the following DCL command:s     SET PREFERED_PATH   F The prefered path mechanism does not disable nor affect SCS operations on the non-prefered path.TG                               [Kevin Jenkins, Verell Boaen, John Croll])  < ------------------------------------------------------------; MGMT48. What (and where) is the OpenVMS Management Station?   F   For information and current kits for the OpenVMS Management Station,D   a PC-based tool that permits you to manage an OpenVMS system, see:  8     http://www.openvms.digital.com/openvms/products/omt/  < ------------------------------------------------------------: MGMT49. How to determine current disk fragmentation level?  G   The Compaq OpenVMS Disk File Optimizer (DFO) defragmentation package sL   provides a fragmentation monitoring tool, and a DFO product authorization A   key (PAK) is not required for the fragmentation reporting tool:      $ DEFRAG SHOW/VOLUME ddcu:  G   The DFU tool available on the OpenVMS Freeware can generate a report     on the disk fragmentation:     DFU> REPORT ddcu:k    < ------------------------------------------------------------@ MGMT50. SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  ;   A message at the OpenVMS bootstrap such as the following:h  A %SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES_1C02.EXEa< %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 theret%   might be no support on any release.o  E   The execlet load failure and other similar bootstrap status values a@   can often be decoded using either of the following techniques:   $ exit %x910" %SYSTEM-W-NOSUCHFILE, no such file $d   $ x = f$message(%x910) $ show symbol xe*   X = "%SYSTEM-W-NOSUCHFILE, no such file" $I     [End of Part 2/5]   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 17 Aug 2000 22:03:00 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 3/5d6 Message-ID: <8nhnek$3hu$1@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part3t Posting-Frequency: monthly Last-modified: 17 Aug 2000 Version: VMS-FAQ-3.TXT(4)a      9 This is the OpenVMS Frequently Asked Questions Part 3/5. a@ Please see Part 1/5 for administrivia, indexing, archiving, etc.      E< ------------------------------------------------------------$ MAIL1.  How do I send Internet mail?  K The simplest answer on most OpenVMS V6.2 and later systems: just enter the  J 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 wJ specifically one that provides the Simple Mail Transport Protocol (SMTP).   P A number of implementations of TCP/IP are available for OpenVMS -- from Compaq, S from third parties, and even a free "support it yourself" form.   The MAIL program fP that comes with OpenVMS does not directly support the mail protocol used on the R Internet (though it does recognize SMTP addresses in V6.2 and later), but various R programs have been written that use MAIL's "foreign protocol" facility to provide V such support -- these tools are called transports.  To send mail through a transport, P place the transport specifier at the front, and (typically) quote the address.    S For example, IN%"hoffman@bogushost.compaq.com" -- you *must* include the quotation eR marks -- indicates that IN transport will be used to send the mail to the address V hoffman@bogushost.compaq.com.  Common names for the transport are IN%, MX%, and SMTP%.Q (MX is a widely used, free, mail handler; see question  SOFT1.  SMTP% is used by  T Compaq's TCP/IP Services product.)  Other systems may use some other name.  If none F of these prefixes work, please ask your system manager for assistance. 					[leichter@lrw.com]e 					[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 packageiB (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 MAILuJ will use the translation as the transport protocol, otherwise it will use ? the SMTP transport as is used by TCP/IP Services for OpenVMS.  u  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?A  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.a3 For earlier versions, see the following paragraphs.s  K The basic MAIL utility which is shipped with VMS does not have an intrinsicnG mechanism for adding signature files.  If you're using an enhanced mail G handling package (e.g PMDF), however, it may have provisions for adding-H 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 messagesnK and news postings.  There are several implementations of this for different H editors available on the net; for one example, see the MAIL_EDIT package
 available at I+   ftp://narnia.memst.edu/mail_edit_v1-4.zips  					[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'  $ ELSE $    COPY <signaturefile> 'P2' $ ENDIFU$ $ DEFINE/NOLOG SYS$INPUT SYS$COMMAND $ <editorname> 'P2'  $ 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).d 					[Arne Vajhj]  < ------------------------------------------------------------A MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.   M Several Unix mailers have been ported to VMS, some by the vendors of 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.  					[Jerry Leichter]   < ------------------------------------------------------------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 allNM 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 wanteG to forward to - say, IN%"fred@fred-host.xxx.com".  Take that string andhJ *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"""i  + If you do SHOW FORWARD, you should now see:p  = 	Your mail is being forwarded to IN%"fred@fred-host.xxx.com".a 					[leichter@lrw.com]   C Note that the MAIL$INTERNET_TRANSPORT feature doesn't yet work with F 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?o  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 does J 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]d  < ------------------------------------------------------------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 countsG differs from what's in your mail folder.  If this happens, go into MAILrI and repeat the READ/NEW command until you see no new mail messages.  TheneG enter the command one more time.  This will resynchronize the counters.r  < ------------------------------------------------------------@ 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:A  # 	EXTRACT/APPEND/ALL/MAIL mymail.mai$  < Move MYMAIL.MAI to the other system, then do this (in MAIL):   	SET FILE mymail.mai 	COPY/ALL foldername MAIL.MAIE  G This will place a copy of all of your messages in the given folder.  If I you wanted to maintain the separate folders, do separate EXTRACT commandstG (above) specifying different .mai files, then repeat the SET FILE, COPY 
 for each one.   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 intoO. 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 - 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/V4      http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/+      ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/d  K 2. If you're working from an X11 server use the OpenVMS version of NetscapetI    Navigator.  This option is ok for sending mail, but is not optimal for H    reading it, since Netscape will use POP and remove messages entirely A    the OpenVMS MAIL system, which is not generally what you want.   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 willrI    cause the message to appear as plain text in most mail programs.  SomeoD    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 directlyDI    into the SMTP port of your mail machine.  Examples of both methods aren    in: p:      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, then.;    use MUNPACK to break out and decode the attachments.        					[David Mathog]m  ; 4. With OpenVMS V7.2 and later, use the supplied MIME tool.y    < ------------------------------------------------------------$ MAIL1.  How do I send Internet mail?  K The simplest answer on most OpenVMS V6.2 and later systems: just enter the hJ Internet (SMTP) address at the "to" prompt in MAIL.  On most such systems,5 this will send your email to the specified recipient.h  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 GJ specifically one that provides the Simple Mail Transport Protocol (SMTP).   P A number of implementations of TCP/IP are available for OpenVMS -- from Compaq, S from third parties, and even a free "support it yourself" form.   The MAIL program sP that comes with OpenVMS does not directly support the mail protocol used on the R Internet (though it does recognize SMTP addresses in V6.2 and later), but various R programs have been written that use MAIL's "foreign protocol" facility to provide V such support -- these tools are called transports.  To send mail through a transport, P place the transport specifier at the front, and (typically) quote the address.    S For example, IN%"hoffman@bogushost.compaq.com" -- you *must* include the quotation  R marks -- indicates that IN transport will be used to send the mail to the address V hoffman@bogushost.compaq.com.  Common names for the transport are IN%, MX%, and SMTP%.Q (MX is a widely used, free, mail handler; see question  SOFT1.  SMTP% is used by  T Compaq's TCP/IP Services product.)  Other systems may use some other name.  If none F of these prefixes work, please ask your system manager for assistance. 					[leichter@lrw.com]A 					[Stephen Hoffman]   See also MAIL2.u  < ------------------------------------------------------------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 packagetB (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 "@"lJ character in it (a quoted string is not needed), MAIL will look to see if I the logical name MAIL$INTERNET_TRANSPORT is defined.  If it is, then MAILsJ will use the translation as the transport protocol, otherwise it will use ? the SMTP transport as is used by TCP/IP Services for OpenVMS.     B To alter this, for example, if you wanted IN% added, you'd define   MAIL$INTERNET_TRANSPORT as "IN".  < ------------------------------------------------------------K MAIL3.  How do I automatically append a signature file to my mail messages?r  I OpenVMS 7.0 adds the ability to automatically append signature files - inaE MAIL, use the SET SIGNATURE command to specify a signature file name.a3 For earlier versions, see the following paragraphs.b  K The basic MAIL utility which is shipped with VMS does not have an intrinsicsG mechanism for adding signature files.  If you're using an enhanced mail G handling package (e.g PMDF), however, it may have provisions for adding)H 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 messages K and news postings.  There are several implementations of this for differenteH editors available on the net; for one example, see the MAIL_EDIT package
 available at $+   ftp://narnia.memst.edu/mail_edit_v1-4.zip   					[bailey@genetics.upenn.edu]  F Define the logical MAIL$EDIT to a COM-file, which looks something like the following:   $ IF P1 .NES. "" $ THEN# $    COPY 'P1',<signaturefile> 'P2') $ ELSE $    COPY <signaturefile> 'P2' $ ENDIF $ $ DEFINE/NOLOG SYS$INPUT SYS$COMMAND $ <editorname> 'P2't $ 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).e 					[Arne Vajhj]  < ------------------------------------------------------------A MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.F  M Several Unix mailers have been ported to VMS, some by the vendors of specificoL 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.n 					[Jerry Leichter]   < ------------------------------------------------------------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.  Tod* 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 want G 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"""r  + If you do SHOW FORWARD, you should now see:T  = 	Your mail is being forwarded to IN%"fred@fred-host.xxx.com".I 					[leichter@lrw.com],  C Note that the MAIL$INTERNET_TRANSPORT feature doesn't yet work withoF 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?t  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 does(J 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]-  < ------------------------------------------------------------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 MAILaI and repeat the READ/NEW command until you see no new mail messages.  ThenFG enter the command one more time.  This will resynchronize the counters./  < ------------------------------------------------------------@ MAIL8.  How do I move all of my mail messages to another system?  N If you are moving to another OpenVMS system, perhaps the best way is to select each folder and do (in MAIL) a:t  # 	EXTRACT/APPEND/ALL/MAIL mymail.mait  < Move MYMAIL.MAI to the other system, then do this (in MAIL):   	SET FILE mymail.mai 	COPY/ALL foldername MAIL.MAIt  G This will place a copy of all of your messages in the given folder.  IfTI you wanted to maintain the separate folders, do separate EXTRACT commandseG (above) specifying different .mai files, then repeat the SET FILE, COPYf
 for each one.   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 intor. 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?s  C Not directly with the OpenVMS MAIL facility, but there are several d 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/e4      http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/+      ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/   K 2. If you're working from an X11 server use the OpenVMS version of NetscapenI    Navigator.  This option is ok for sending mail, but is not optimal forMH    reading it, since Netscape will use POP and remove messages entirely A    the OpenVMS MAIL system, which is not generally what you want.u  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 will I    cause the message to appear as plain text in most mail programs.  SomeKD    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 directlydI    into the SMTP port of your mail machine.  Examples of both methods are     in:  :      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, thenn;    use MUNPACK to break out and decode the attachments.    t   					[David Mathog]T  ; 4. With OpenVMS V7.2 and later, use the supplied MIME tool.f    < ------------------------------------------------------------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:),H give yourself PHY_IO and DIAGNOSE privileges, and run the .EXE.  You canA 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.  E The IDE DQDRIVER does not support the necessary IO$_DIAGNOSE function)D required for this capability.  An OpenVMS Engineer is rumoured to beC looking at adding the necessary support for the function code as a tG "midnight project", but unless/until this work is completed, audio CDs :D and other IDE widgets requiring "extended" function codes cannot be  accessed via DQDRIVERl  < ------------------------------------------------------------: UTIL2.  How do I access a MS-DOS floppy disk from OpenVMS?  E The Compaq Advanced Server (formerly known as PATHWORKS) for OpenVMS LG product includes an unsupported and undocumented utility called PCDISK,eA 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.rmi.de.o  H Engineering Software has a product called VAKSAT which will read, write,D and erase files on DOS diskettes.  Available for both VAX and Alpha.0 Contact ed@cityscape.co.uk for more information.  D MadGoat PC Exchange (PCX) is a utility for copying files to and fromD MS-DOS (FAT) format diskettes under VMS, using an RX23 (3.5"), RX26 I (3.5"), or RX33 (5.25") diskette drive.  For 3.5" diskettes, high-density-F disks can be read or written; double-density disks are read-only. Only- high-density disks are supported on the RX33.      http://www.madgoat.com/o  < ------------------------------------------------------------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 SoundtK System) than the earlier DEC 3000 AXP systems, and DECsound, as supplied bytH DECwindows Motif, doesn't support this board.  Compaq offers an optional) product, Multimedia Services for OpenVMS:%  %   http://www.digital.com/info/SP6424/n   J which provides a replacement DECsound for this card as well as many other > features (an AVI and MPEG player, video capture support, etc.)  B Ensoniq sound support is expected to be available in January 2000.  < ------------------------------------------------------------3 UTIL4.  Why is DECmigrate not working with Fortran?.  : OTS-F-INDATCOR internal data corrupted in Run-time Library  @ This error can arise with Fortran programs if you are running a < recent version of OpenVMS Alpha, and are using DECmigrate toA translate Fortran applications.  The DECmigrate Run-Time Library -A attempts to support mixed translated-native I/O to the same unit MA by sharing the native Fortran RTL's internal data structures, ands> in OpenVMS 7.2 these structures changed and the translated RTL was not updated accordingly.  B The best solutions for now involve using a copy of DEC$FORRTL.EXE A from OpenVMS 7.1, copying it to some directory, and then definingR? the logical name DEC$FORRTL to point to it before running your aA translated application.  Or rebuilding the application to use the-" available native Fortran compiler.2                                     [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 andmJ the DCL COPY command can be used to transfer text files around.  Check the IBM documentation for details.  F There exists various freeware around (TAPECOPY, ETAPE, TCOPY) that canG read and write EBCDIC tapes.  Visit the DECUS website software archives-C search engine (via http://www.decus.org/), and search for "EBCDIC".a3                                     [Steve Hoffman]S    < ------------------------------------------------------------. 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:  ' 	$ uudecode :== $disk:[dir]uudecode.exeo 	$ uudecode filespec  M The leading $ in the symbol definition is what makes it a foreign command. Ifi> the device and directory is omitted, SYS$SYSTEM: is assumed.    D Under OpenVMS V6.2 and later, DCL supports automatic foreign commandN 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 thevJ directories specified via DCL$PATH.  The first match found is invoked, andH under OpenVMS, the DCL$PATH support will cause a command procedure to be/ activated in preference to an executable image.   H For more information on foreign commands or on automatic foreign command' support, see the OpenVMS User's Manual.f   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,tN 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.COMa  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 as F 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.e   Also see DCL11.a 					[Stephen Hoffman]  < ------------------------------------------------------------/ DCL2.   How can I redefine control keys in DCL?   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 DELo for delete, are not modifiable.t  < ------------------------------------------------------------* 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:d  < ------------------------------------------------------------< 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 commandu@ 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/LOGl"   $ 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/DISABLEa  A Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) for information@C on configuring the behaviour of OPCOM, including the (default) use n? of the system console (OPA0:) as an operator terminial and the  @ specific contents and behaviour of the system operator log file 
 OPERATOR.LOG.  						[Arne Vajhj]  						[Stephen Hoffman]e  < ------------------------------------------------------------1 DCL5.   How do I generate a random number in DCL?o  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:s $l $ IF F$TYPE(__SEED) .EQS. "" $ THEN- $     ! seed the random number generator, ...a $     __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)' $aA $     __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + -t          (360000 * __HOUR)D $     ! the generator tends to do better with a large, odd seed, ... $     __SEED == (__SEED .OR. 1)_ $     ! clean up, ...- $     DELETEX/SYMBOL __NOW $     DELETEX/SYMBOL __HOUR- $     DELETEX/SYMBOL __MINUTEy $     DELETEX/SYMBOL __SECONDm $     DELETEX/SYMBOL __TICK  $ ENDIFa $i5 $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFF  $  $ __SEED == __SEED * 69069 + 1 $y7 $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)o $w $ RETURN$ 					[sharris@sdsdmvax.fb3.noaa.gov]  < ------------------------------------------------------------% DCL6.   What does the MCR command do?g  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:e   	$ FOO :== $FOOa
 	$ 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 iseJ 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.i  < ------------------------------------------------------------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 asK tie-in that provides the information to the SET PROMPT command as required.   K If you wish to display the default directory for instance, you will have to-L 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 thetM SET DEFAULT and SET PROMPT for you.  These DCL command procedures often use ar command such as:  !   $ set prompt='f$env("default")'i  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.)   E There are related tools available from various sources, including the  following web sites:  $   o ftp://ftp.hhs.dk/pub/vms/setpmt/  -   o ftp://ftp.tmesis.com/sys_service_hook.srcw  A   o James F. Duff has also made available a Macro32 tool known asdH     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, andcI examples from Arne Vajhoej, Brian Schenkenberger, James Duff, and others.n   				[Stephen Hoffman]r  < ------------------------------------------------------------< 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	         $M@         $! This procedure must be in the user's login directory.B         $! Requires a self-referential (not reverential :-) proxy:L         $!    UAF> add/prox <LocalNode>::<CurrentUser> <CurrentUser>/default?         $! Author: Stephen Hoffman, OpenVMS Engineering, Compaqa	         $          $ goto 'f$mode()'s         $INTERACTIVE: *         $ open/read/write chan 0::"task=x"         $ write chan "Hello"         $ read chan parameterr         $ close chan$         $ write sys$output parameter         $ exit         $BATCH:o         $OTHER:e         $NETWORK:g&         $ open/read/write chan sys$net         $ read chan parameterh-         $ write chan "''parameter' yourself!"-         $ close chan         $ exit  -   An example of a run of the above procedure:s           $ @x         Hello yourself!e	         $,    L DCL does not include support asynchronous I/O, thus a predetermined protocolH or a predetermined "turn-around" command sequence must be implemented inI order to avoid protocol deadlocks -- cases where both tasks are trying to J write or both tasks are trying to read.  The task that is writing messagesI to the network must write (or write and read) a predetermined sequence ofaJ 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.)o 					[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?m  :   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)s     $ show log opcom_pid2        "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE);                                            [Norm Lastovica]k  < ------------------------------------------------------------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 oreE   /ERROR on a RUN/DETACH command, then you must translate the logicalND   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.a  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 tI   want to see these particular logical names created, then please specify 8   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 tI   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 ?K   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 useoC   physical device and directory references on the RUN/DETACH of theiE   LOGINOUT image, when specifying this command file as /INPUT.)  AlsoNF   remember to check both security auditing and system accounting when /   troubleshooting problems with the RUN/DETACH.i     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] = 7t%     $ write sys$output "Hello''bell'"t     To write blinking text, use:       $ esc[0,7] = 27      $ text = "Blinking Text"1     $ write sys$output "''esc'[5m''text'''esc'[m"-  !   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 disk G and it may be possible to retrieve it.  The FLORIAN tool available fromtE the WKU Fileserver claims to be able to do this (see question SOFT1.)iF Other alternatives here include the DFU tool, available on the OpenVMS Freeware CD-ROM distribution.   G If you are setting up a user environment for yourself or for others, itoI is quite easy to use DCL to intercept the DELETE command, using a symbol:   '   $ DEL*ETE :== @SYS$LOGIN:MYDELETE.COMM  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 procedures G can retrieve the file(s) from the "trashcan" subdirectory, and can (and-K should) clean out the "trashcan" as appropriate.  (Realize that this DELETECH 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.l 					[Steve Lionel]   ! $ DIR/SIZ=ALL/GRAND [username...]-  6 Grand total of D1 directories, F1 files, B1/B2 blocks.  # $ DIR/SIZ=ALL/GRAND [-]username.DIRt  1 Grand total of 1 directory, 1 file, B3/B4 blocks.r   $ SHOW QUOTA3   User [username] has B5 blocks used, B6 available,n?   of B7 authorized and permitted overdraft of B8 blocks on disk   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+1o  M If the diskquota is out of synch, then the system-manager can make a rebuild.e 					[Arne Vajhj]  G Also be aware that the DIRECTORY/SIZE command can report larger values iD 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 nI 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.)c  < ------------------------------------------------------------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, K no matter what, there's really no substitute for RMS Journalling.  However,IJ you can achieve a good degree of data integrity by issuing a SYS$FLUSH RMSD call at appropriate times (if you're using RMS, that is.)  If you'reM using a high-level language's I/O system, check that language's documentationdF to see if you can access the RMS control blocks for the open file.  InC C you can use fflush followed by fsync.  Note that fsync, which wasSK undocumented for VAX C but is documented for DEC C, takes a file descriptorr as an argument, not a *FILE.  < ------------------------------------------------------------C FILE4.  What are the limits on file specifications and directories?]  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 -n K (n'th previous version) can be used in most contexts.  A file specificationuN may not have more than 8 directories and subdirectories - while it is possibleK to create subdirectories of greater depth, accessing them is problematic inV' most cases and this should be avoided. R  G Application developers should use OpenVMS-supplied routines for parsingaI file specifications - this ensures that changes in what is allowable willtG not tend to break your application.  Consider that various parts of the F file specification may contain quoted strings with embedded spaces andI other punctuation!  Some routines of interest are SYS$FILESCAN, SYS$PARSEMI and LIB$TRIM_FILESPEC.  For further information, see the OpenVMS Guide toY File Applications.  < ------------------------------------------------------------@ FILE5.  What is the largest disk volume size OpenVMS can access?  M One Terabyte (2**31 blocks of 2**9 bytes).  Prior to the release of V6.0, the K OpenVMS file system was limited to disk volumes of 8.5 GB (2**24 blocks) orl less.e  M On some systems, there are restrictions in the console program that limit theoJ size of the OpenVMS system disk.  Note that data disks are not affected byH console program limits.  For example, all members of the VAXstation 3100K series are limited to a system disk to 1.073 GB or less due to the console,-& though larger data disks are possible.  D Some SCSI disks with capacities larger than 8.6 gigabytes (GB) will G require the use of an OpenVMS ECO kit (eg: ALPSCSI04_062 or later) for tF 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 rJ display the full capacity of the drive -- and  "%sysinit-e-error mounting E system device status equals 000008C4" (8C4 -> "%SYSTEM-?-FILESTRUCT, -B unsupported file structure level") errors during bootstrap.  (One E workaround for the bootstrap when the bitmap is located far into the  D 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:o  %       OpenVMS Alpha V7.2-1, and laterh%       V7.2 UPDATE V1.0 ECO, and latere'       V7.1-2 UPDATE V1.0 ECO, and later '       V7.1-2 UPDATE V3.0 ECO, and later   <   o The newer DQDRIVER driver operates to disks up to 33 GB ?     without (known) problems, and effectively works with ratherdA     larger disks (up to circa 137 GB?) but is known to report an  ;     incorrect number of "cylinders" with disks above 33 GB.O  C Be aware that a known restriction in certain older versions of the P? Alpha SRM Console prevents booting most IDE drives larger than cC 8.455 GB, depending on exactly where the various files are located tB on the volume.  Updated SRM consoles for systems with SRM and IDE A drive support are (will be) available.  (OpenVMS Engineering has S? successfully bootstrapped 20GB IDE disks using the appropriate - SRM console version.)   O NOTE: All IDE-related disk sizes listed in this section are stated in  units of K "disk (base 10) gigabytes" (1GB = 10^9 bytes) and NOT in units of "softwareO5 (base 2) gigabytes" (1GB = 2^30 (1073741824.) bytes. p:                                           [Atlant Schmidt]   Also see VAX5.  < ------------------------------------------------------------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).  F The RMS formats -- sequential, relative, and indexed -- are limited byE the one terabyte maximum volume size.  RMS relative files are further D limited to a number of records that will fit in 32 bits -- 4 billionE records.   Sequential and indexed formats do not have a record limit.L   Also see PROG14. 					[Stephen Hoffman]  < ------------------------------------------------------------= FILE7.  How do I write recordable CD media (CD-R) on OpenVMS?   B Creation of CD-ROMs using recordable CD media (CD-R) under OpenVMSA typically involves one of two approaches: the use of the optionalUB CD-R (`Scribe') capabilities available for the InfoServer or otherD "offline" hardware packages, or the use of a host-based package such> as the CDWRITE13_VMS utility, an OpenVMS port of a Linux tool.  ; OpenVMS has no integrated support for recording CD-R media.a  6 OpenVMS can read both ODS2 and ISO9960 format CD-ROMs.  F InfoServer hardware configurations are no longer availble from Compaq,4 but may potentially be acquired through other means.  E The CDWRITE13_VMS package is one example of a host-based package thataC can be used to create CD-R media.  The contact for CDWRITE13_VMS isdE Dr. Eberhard Heuser-Hofmann.  One website that discusses this packageX 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:t  2   http://home.earthlink.net/~djesys/vms/cdrom.html  	 Also see:i  6   http://www.cd-info.com/CDIC/Technology/CD-R/vms.html  B   http://www.faqs.org/faqs/cdrom/cd-recordable/part1/preamble.html  E   http://www.tmesis.com/CDrom/     http://www.tditx.com/~odsiso/t  ;                                           [Stephen Hoffman]w  B U.S. Design offers a package that includes the tools necessary to B create a CD with either 9660 or ODS-2 format, for standalone CD-R D drives, for OpenVMS Alpha V7.1 and later.  Details are available at:     http://www.usdesign.com/;                                            [Harry Garonzik]o  < ------------------------------------------------------------7 FILE8.  What I/O transfer size limits exist in OpenVMS?e  G The maximum transfer size is an attribute of the particular I/O device, E controller and driver combination; there is no inherent limit imposedrE by OpenVMS (other than the fact that, today, byte counts and LBNs area generally limited to 32 bits).  C The maximum size of a device I/O request is limited by the value ineA UCB$L_MAXBCNT, which is set by the device driver based on variousmD 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 largelyhC historical.  Similarly, DSSI devices are limited to the same value, D this for hardware-specific reasons.  Transfers to HSC and HSJ deviceJ controllers via the CI are limited to 1,048,576 bytes.  Client MSCP-servedA devices are limited to 65535 bytes -- to help ensure that the I/OnD fragmentation processing happens on the client and not on the server system.   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 anda the device can handle it.a   Also see FILE4, FILE5   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 r% commercial databases via the network.i  ? 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 sete them up explicitly.e 					[eric@tardis.HQ.ileaf.com]x  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 Manualt$ 	OpenVMS Programming Concepts Manual9 	OpenVMS Programming Interfaces: Calling a System Routines 	OpenVMS Calling Standard   G In addition, if you are a subscriber to the Compaq Software InformationeJ 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]t  F Arne Vajhj has put together a collection of OpenVMS example programs. It can be found at:-   ftp://ftp.hhs.dk/pub/vms/- 					[Arne Vajhj]  B Additional information and examples for OpenVMS are available via:  (   http://www.openvms.digital.com/wizard/*   http://www.openvms.digital.com/freeware/   					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG2.  How do I get the arguments from the command line?L  G If you're writing a program and want to accept arguments from a foreignaF command, you can use LIB$GET_FOREIGN to get the command line and parseD it yourself, or if you're programming in C, use the normal argc/argv method.a  J To write an application which uses the normal DCL verb/qualifier/parameterF syntax for invocation, see the description of the CLI$ routines in the3 OpenVMS Callable Utility Routines Reference Manual.h  I It is possible to write an application which can be used both ways; if a cL 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  @ LIB$GET_FOREIGN to get the command line and do the manual parse.   See also question DCL1.S  < ------------------------------------------------------------= PROG3.  How do I get a formatted error message in a variable?   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$PUTMSGeI doesn't then try to display the message (unless you want it to.)  See theaE description of $PUTMSG in the System Services Reference Manual for anb# example of using an action routine.d  < ------------------------------------------------------------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.e  G Also see PROG11, particularly for pointers to the details on shareable h$ 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..B If you want to change the default disk within a program, then callJ LIB$SET_LOGICAL to change the logical SYS$DISK. You will need to call bothK LIB$SET_LOGICAL and SYS$SETDDIR to change both default disk and the default.
 directory! 					[Arne Vajhj]	h  < ------------------------------------------------------------M PROG6.  How do I create a shareable image transfer vector on an Alpha system?   K This is something that was greatly simplified for OpenVMS Alpha.  You don'txL need to create a separate transfer vector module; just use the SYMBOL_VECTORI statement in a linker options file.  For example, if your shareable image-J has two routines named FOO and BAR, the linker options file should contain the following line:i  - 	SYMBOL_VECTOR=(FOO=PROCEDURE, BAR=PROCEDURE)f  + The Linker manual has more details on this.e  < ------------------------------------------------------------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.  OneG OpenVMS VAX all OVR/REL/GBL psects were automatically exported into the-M shareable image's Global Symbol Table.  On OpenVMS Alpha you have to tell thefC linker that you want this done by means of the PSECT keyword in thea% 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.a  K By default, COMMON PSECTs in DEC Fortran for OpenVMS Alpha (as well as mostiL 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 COMMON-G to be in a shareable image but not write-shared by all processes on thei, 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.d  / For further information, see the Linker manual.a  < ------------------------------------------------------------< PROG8.  How do I convert between IEEE and VAX floating data?  G In OpenVMS V6.1 there is a routine CVT$CONVERT_FLOAT, documented in themE LIB$ Run-Time Library Reference Manual, which can perform conversionsQC between any two of the following floating datatypes: VAX (F,D,G,H),uK little-endian IEEE (single, double, quad), big-endian IEEE (single, double,f quad), CRAY and IBM System\370.   F DEC Fortran (all platforms) has a feature which will perform automaticK conversion of unformatted data during input or output.  See the DEC FortranaA documentation for information on "non-native data in I/O" and theO  CONVERT= OPEN statement keyword.  4 For further floating-point related information, see:  .   ftp://ftp.hhs.dk/pub/vms/collection/ieee.zip  < ------------------------------------------------------------= PROG9.  How do I get the argument count in a Fortran routine?f  E On VAX, many programmers would use a MACRO routine which accessed thehE AP register of the caller to get the address of the argument list andEF 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 Note that omitting arguments to Fortran routines is non-standard and islG unsupported.  It will work in many cases - read the DEC Fortran released! notes for additional information.   < ------------------------------------------------------------? PROG10. How do I get a unique system ID for licensing purposes?U  G Many software developers desire to use a unique hardware ID to "lock" aeF 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 lD for this purpose.  Compaq does not use hardware IDs in its licensingG methods and many users consider a hardware-based licensing scheme to bed9 a negative attribute when considering software purchases.-  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.  c@ 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.digital.com/wizard/  < ------------------------------------------------------------? PROG11. What is an executable, shareable, system or UWSS image?l  A    Executable code in OpenVMS typically resides in an image -- aneB    image is a file -- the file extension is typically .EXE -- thatA    contains this code.  Common types of images include executable @    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 ACL-        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 enhancedf?        privileges, even with the use of INSTALL with /PRIVILEGEr@        or a subsystem identifier.  These shareable images can beA        dynamically activated (a LINK that occurs at run-time) vial@        the LIB$FIND_IMAGE_SYMBOL run-time library (RTL) routine.=        (See `protected images' for information on `privilegedo        shareable images'.)  A    System images are intended to run directly on the VAX or Alphat>        hardware -- these are normally used for the kernel code+        that comprises an operating system. C  F    Protected images -- also refered to as User-Written System ServicesC        (UWSS), or as privileged shareable images -- are similiar inaA        some ways to a standard shareable images, but these images A        include a `change mode' handler, and execute in an `inner'CA        processor mode (privileged mode; executive or kernel), and(C        code executing in inner modes has implicit SETPRV privilege.oB        Must be INSTALLed with /PROTECT.  Note that inner-mode code?        has restrictions around calling library routines, aroundt?        calling various system services, and around calling codei6        located in other protected or shareable images.  A    Loadable images and device drivers are images that can be usedt>    to add code into the OpenVMS kernel.  Pseudo-device driversA    are a particularly convenient way to add executable code, withn>    associated driver-defined data structures, into the kernel.E    The pseudo-device driver includes the UCB and DDB data structures,t?    and a calling interface with support for both privileged andl?    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:t  *      http://www.openvms.compaq.com/wizard/   					[Stephen Hoffman]  < ------------------------------------------------------------/ PROG12. How do I do a file copy from a program?l  M There are several options available for copying files from within a program.  D 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).9   					[Stephen Hoffman]  < ------------------------------------------------------------ PROG13.  What is a descriptor?  K A descriptor is a data structure that describes a string or an array.  Each-I descriptor contains information that describes the type of the data beingaG referenced, the size of the data, and the address of the data.  It alsoeI includes a description of the storage used for the data, typically statich2 or dynamic.   Descriptors are passed by reference.  B The following are examples of creating and using descriptors in C:       #include <descrip.h>     #include <lib$routines.h>e     #include <stsdef.h>e     int RetStat;     char TxtBuf[TXTSIZ] %     struct dsc$descriptor StaticDsc = 0       { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL };#     struct dsc$descriptor DynDsc = m0       { 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 */ )     StaticDsc.dsc$w_length      = TXTSIZ;e2     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;g  %     /* release the dynamic storage */O'     RetStat = lib$sfree1_dd( &DynDsc );a(     if (!$VMS_STATUS_SUCCESS( RetStat ))       return RetStat;   G Static descriptors reference storage entirely under application programtJ control, and the contents of the descriptor data structure can be modifiedE as required (by the application).  OpenVMS routines do not modify thetH contents of a static descriptor, nor do they alter the address or lengthI values stored in the static descriptor.  (The term "static" refers to thetH descriptor data structure, and not necessarily to the storage referenced by the descriptor.)m  G Dynamic descriptors reference storage under the control of the run-timefH library, and the contents of a dynamic descriptor data structure -- onceE initialized -- can only be modified under control of run-time libraryCF routines.  The dynamic storage referenced by the dynamic descriptor isC allocated and maintained by the run-time library routines.  VarioustH OpenVMS routines do alter the contents of the descriptor data structure,K changing the value for the amount and the address of the storage associatedcH with the dynamic descriptor, as required.  Routines can obviously accessC and alter the contents of the storage referenced by the descriptor.e  I OpenVMS languages that include support for strings or arrays are expected I to use descriptors for the particular structure.  Most OpenVMS languages,-J 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 Programmingc8 Concepts_ manual, part of the OpenVMS documentation set.   					[Stephen Hoffman]  C Fortran defaults to passing integers by reference and characters byBD descriptor.  The following sites discuss mixing Fortran and C source code in the same application:X  =   http://www.hhs.dk/anonymous/pub/vms/misc/FORTRAN_C_CALL.COMr2   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.   B Under OpenVMS VAX and OpenVMS Alpha, the disk volume block size is1 consistent, with each block containing 512 bytes.s  D The minimum disk allocation granularity actually permissible (in theI ODS-2 and ODS-5 volume structures commonly used on OpenVMS) is determinedtE 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 volumenJ storage bitmap.  The allocation granularity is known as the volume clusterG factor -- the cluster factor is the number of blocks in a disk cluster,]B and it is the smallest number of blocks that can be allocated on a particular disk volume.o  B Prior to OpenVMS V7.2, the  maximum permissible size of the bitmapC requires larger cluster factors as volume sizes increase.  StartingfD 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 theoC File Header XAB) value can be used to find out how much of the last-? (XAB$L_EBK) block is used.  FFB and EBK are meaningful only forI@ 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, D which can be from one block up to (potentially) clusters of eighteen7 blocks or more, depending on the volume cluster factor.i  H OpenVMS assumes that the device driver and the underlying storage deviceE will present the file system with addressable units of storage of 512aE 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:v it is always 512 bytes.   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 systemeF page size can be determined using the sys$getsyi or f$getsyi PAGE_SIZEE item.  Programs with hardcoded constants for the memory page size (ordA page alignment) should always assume a page size of 64 kilobytes.a  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.s   					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG16. How do I create a process under another username?d  G Many server processes can operate within the context of the target usernF 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.a  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 processeF 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 OpenVMSiI V6.2 new features documentation, and in the OpenVMS V7.1 and later systemfI services documentation.  These system services exist and are supported in-  OpenVMS V6.2 and later releases.  I Typical mechanisms for creating a process under another username include:V  =     o personna services around a sys$creprc call.  See above.1>     o via DECnet task-to-task, using explicit specification of5       username and password, or using a DECnet proxy.-<       This creates a network-mode job under the target user.A       The network-mode job might do little more than a RUN/DETACHD<       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.)$C     o SUBMIT/USER, or the username argument on the sys$sndjbc call.hA       This creates a batch-mode job under the specified username.h?       The batch-mode job might do little more than a RUN/DETACH-,       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.d     o Via pseudo-terminals...v  J There are likely a few other mechanisms around...  There are various toolsG available from DECUS and other sources that allow various forms of userRJ 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?d  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.t  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 CLI : present in the process this (lack of) propogation is moot.  I To create a detached process with a CLI, you must specify LOGINOUT as theCG target image as discussed elsewhere in the FAQ, or only use these callsoH (and any other calls requiring a CLI) from images that are running in an0 "interactive", "batch", or "other" mode process.   					[Stephen Hoffman]  < ------------------------------------------------------------J PROG18.  Where can I obtain Bliss, and the libraries and supporting files?  < The Bliss language compilers and documentation are available& on the OpenVMS Freeware distributions.  A Bliss language source code that contains the following statement:N  $   LIBRARY 'SYS$LIBRARY:STARLET.L32';  ? or similar requires the presence of the Bliss libraries.  ThesewB 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 -t         SYS$LIBRARY:STARLET.REQ   E   LIB.L32 contains both the public and private interfaces to OpenVMS:o  1     $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 -=3         SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQt  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.R64a9     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]STARLET.L64 -m         SYS$LIBRARY:STARLET.R64i  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:     !k9   ! This is the OpenVMS VAX version of ARCH_DEFS.BLI, and <   ! contains the architectural definitions for conditionally;   ! compiling OpenVMS Bliss sources for use on VAX systems.t   !g   MACRO VAXPAGE = 1%;n   MACRO BIGPAGE = 0%;O  =   MACRO VAX =                     ! = 1 if compiled BLISS/VAXoA           %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAXi  <   MACRO EVAX =                    ! = 1 if compiled BLISS/E*   !e@   ! A more appropriate definition can only be used with versions=   ! of the Bliss compilers that understand the 32E/64E flags.aG   !       %BLISS(BLISS32E) OR %BLISS(BLISS64E)%; ! = 0 if compiled /VAXs8           NOT %BLISS(BLISS32V)%;  ! = 0 if compiled /VAX     MACRO ADDRESSBITS =iE           %BPADDR%;               ! = 32 or 64 based on compiler used-       					[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 they'   contents of a log file, for instance.(  8   A C source example that demonstrates how to do this is7   available in topic 2867 in the OpenVMS Ask The WizardF   area:r  *     http://www.openvms.digital.com/wizard/  ;   Depending on the environment, you may need to use C calls ;   such as fsync and fflush, and -- in specific cases -- theu   setvbuf(_IONBF) call.g   					[Stephen Hoffman]   [End of Part 3/5]d  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 17 Aug 2000 22:04:57 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/5e6 Message-ID: <8nhni9$3hv$1@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part4  Posting-Frequency: monthly Last-modified: 17 Aug 2000 Version: VMS-FAQ-4.TXT(4)g    9 This is the OpenVMS Frequently Asked Questions Part 4/5. e@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------F DECW1.  How do I let someone else display something on my workstation?  M On a workstation, you go into "Customize" menu of the session manager utilityh@ and select "Security".  When the pop-up box appears, you can putK node/user/tranport to allow who can launch an application to the display on  that workstation.i<                                              [Mike Raspuzzi]  M > Yah, but this doesn't seem to work with non-VMS systems.  What do I put in mI > for the transport?  I tried "TCPIP" just for kicks, but it didn't work.   &         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:i  & 	    # setenv DISPLAY myvax.domain:0.0  D       2) If you've verified 1) and things still aren't working, makeD          sure the Security settings on  the  VMS side will allow theD          connection:  Pull  down the "Options" menu in  the  SessionD          Manager, select "Security..."  near  the  bottom.   If  youD          don't  find  your  host  (and  username) listed on the leftD          under "Authorized Users", go to the  right side of the menuD          and   fill   in  the  three  fields,  "Node",   "Username",D          "Transport".  Then click on the Add botton, then the  ApplyD          and  OK  buttons  to  add  the  new  host  to  the security          database.  @           a) There are  various  transports: LOCAL, DECNET, LAT,@              TCPIP,  etc.   Select  the one appropriate  to  the<              client machine's connection to the VMS machine.  9 	  b) If the connection is DECNET, do *NOT* add :: to 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.t  @           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.s  @           e) There are a  various  3rd  party vendors who supply@              TCP/IP  packages for VMS, including but not limited@              to  TGV  (Multinet)  and  Wollongong  (Pathway  ?).@              Multinet  (and  DEC's  own  UCX) call the transport@              "TCPIP", Wollongong, at least in some incarnations,<              uses "WINTCP".  You need to use the appropriate@              vendor's package transport name  in the "Transport"              field.   D       3) If things _still_  aren't  working, make sure the transportD          you  want  has  been activated for DECwindows.  This  is  aD          system manager job, but you can do the ground work yourself8          before bothering the sysmgr.  Do the following:  4 	    $ DIR SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM  &          If that file exists, then do:  9 	    $ SEARCH SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM - (             $_    DECW$SERVER_TRANSPORTS  '          You sould find something like:R  9 	    $ decw$server_transports == "DECNET,LOCAL,LAT,TCPIP"n  D          If the transport you want,  e.g., TCPIP, isn't listed, haveD          your  system  manager  make  the  appropriate  changes  andD          restart DECwindows.  If the file doesn't exist, the  sysmgrD          will  have  to  create  it  by  copying  the  correspondingD          .TEMPLATE file  to  .COM  and  uncommenting  the  line that(          defines decw$server_transports.  @           a) If you're wanting  to  use  TCP/IP to connect, make@              sure  TCP/IP is available on the VMS host.   TCP/IP@              is _not_ native to VMS.  You  need  to  be  runningB              either Compaq's TCP/IP or a 3rd party vendor's TCP/IP@              product.   If  you're  not,  none of the above will              help.% 				    [Fairfield@Slac.Stanford.Edu](  K There is a log file created in SYS$MANAGER which tells you which transportsyL 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 besI very useful for tracking down what needs to be put in the Session Manager  Security entries.y 				    [rabinowitz@bear.com]o  < ------------------------------------------------------------9 DECW2.  How do I create a display on another workstation?o  @ $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node  ) for LAT the command might look like this:s  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.122u  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 supportedMD on OpenVMS VAX as a transport for DECwindows in a future OpenVMS VAX release." 					[raspuzzi@mrlat.enet.dec.com]  K There is a log file created in SYS$MANAGER which tells you which transportsiL 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 Managerb Security entries. =                                         [rabinowitz@bear.com]A  < ------------------------------------------------------------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/or  DECW$DISPLAY_TRANSPORT.i" 					[Fairfield@Slac.Stanford.Edu]  E An example of calling the underlying (and also undocumented) sys$qio e? programming interface for the WSDRIVER (WSAn:) is available at:   J   http://www.openvms.digital.com/freeware/srh_examples/DECUS_UNDOC_CLINIC/  < ------------------------------------------------------------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.l  M It should be noted that ALL the characters and escape sequences are captured,nO but if you display the log file on a DECterm you will get EXACTLY what you had.   					[fenster@star.enet.dec.com]  < ------------------------------------------------------------E DECW5.  Problem - the DELETE key deletes forward instead of backward!x  N This has to do with Motif's virtual bindings.  When a Motif application startsD up, it looks at the vendor string returned in the display connectionL information and attempts to match the string to a table of virtual bindings.  N You can override the default bindings in your decw$xdefaults.dat file. Here is9 the entry you would make to get the default VMS bindings.       *defaultVirtualBindings:\f  osfCancel	:		<Key>F11	\n\  osfLeft	:		<Key>Left	\n\y  osfUp		:		<Key>Up		\n\r  osfRight	:		<Key>Right	\n\p  osfDown	:		<Key>Down	\n\i   osfEndLine	:Alt		<Key>Right	\n\!  osfBeginLine	:Alt		<Key>Left	\n\t  osfPageUp	:		<Key>Prior	\n\  osfPageDown	:		<Key>Next	\n\e"  osfDelete	:Shift		<Key>Delete	\n\  osfUndo	:Alt		<Key>Delete	\n\   osfBackSpace	:		<Key>Delete	\n\   osfAddMode	:Shift		<Key>F8		\n\  osfHelp	:		<Key>Help	\n\o  osfMenu	:		<Key>F4		\n\  osfMenuBar	:		<Key>F10	\n\s  osfSelect	:		<Key>Select	\n\s!  osfActivate	:		<Key>KP_Enter	\n\i!  osfCopy	:Shift		<Key>DRemove	\n\[  osfCut		:		<Key>DRemove	\n\  osfPaste	:		<Key>Insert  	 To merge:-    	$ xrdb :== $decw$utils:xrdb.exe( 	$ xrdb -nocpp -merge decw$xdefaults.dat 					[Fred Kleinsorge]  < ------------------------------------------------------------- DECW6.  Why is DECwindows Motif not starting?2  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 yout 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 -I    not have a Compaq QVision video card.  This EISA graphics card should eF    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 u#    on the DEC 2000 series systems.)S  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 350s      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 disabledo(    the device autoconfiguration process.  ) If there is a G* graphics device present:t  I a) There may have been a severe error in the DECwindows startup. Type theeI    contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any information ona    errors starting the server.  I b) The system parameter WINDOW_SYSTEM is not set to 1.  This is a common  D    way for system managers to disable the DECwindows server startup.  E c) You may not have a valid Motif license.    To check for the Motif      license, type the commands:  !       LICENSE LIST DW-MOTIF/FULL t$       LICENSE LIST NET-APP-SUP*/FULL  F    and examine the information displayed.  Make sure that one of these)    licenses is present, valid and active.o   Also see DECW14b 					[Kleinsorge, Hoffman]  < ------------------------------------------------------------ DECW7 relocate to SUPP7h  < ------------------------------------------------------------ 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.t  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:a  : 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:a   $  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.m   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 tM FileView defaults, session manager defaults, the DECwindows login processing, L DECwindows log file processing, and various other DECwindows attributes, see the example file:r  .   SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE  C This example template file is typically copied over to the filenameaM SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_APPS_SETUP.COM and then modified to meetc site-specific requirements.r  M Additionally, various X tools such as xsetroot, bitmap and xrdb -- some theseeG can be useful in customizing the appearance of an application or of the[A DECwindows Motif display -- are provided in the DECW$UTILS: area.-  M When using DECwindows V1.2-4 and later on OpenVMS Alpha, the default desktop  G is the Common Desktop Environment (CDE).  You can select your prefered nI desktop (CDE or DECwindows Motif) when logging in, or you can change the t= default to the DECwindows Motif desktop using the DCL symbol TK decw$start_new_desktop in the DECwindows private application setup command iI procedure.  See SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE for further d7 details, and how to create DECW$PRIVATE_APPS_SETUP.COM.E  G Note that with DECwindows CDE, the root window is no longer visible by SH 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  E style manager selection "backdrop none", and use information such as ./ that in the OpenVMS FAQ to set the root window.f  E To add a new backdrop to the DECwindows CDE environment, the backdrop:J must first be in or be converted into X11 pixmap format.  (This conversionF is often possible using tools such as xv.)  Then (if necessary) createH the default backdrop directory SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS].I Place the X11 pixmap file containing the desired image into the backdropsIC 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.   I 					[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.o  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 to I synchronize the completion of asynchronous operations.  While it would betD 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 extremelyiA difficult to use OpenVMS features such as ASTs and sys$qio calls.r  K One restriction on the event flag: the event flag chosen must be from eventnI flag cluster zero.  When using the traditional lib$get_ef and lib$free_efpG calls to allocate and deallocate event flags, you must first explicitly H 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 calls J 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(u         m->AppCtx,         m->InputEF,h         m->InputIosb,h         the_callback, 1 );     if ( !((int) m->InputID ))	         {m         XtAppErrorMsg(             m->AppCtx,             "invalidDevice",             "XtAppAddInput",             "XtToolkitError",P"             "Can't Access Device",             (String *) NULL,              (Cardinal *) NULL );         ...- 					[Stephen Hoffman]  < ------------------------------------------------------------B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?  @ Congratulations, you have just stumbled into "dead rodent" mode.< This DECwindows environment -- where the keyboard arrow keys@ move the mouse cursor and where the [SELECT], [PREV], and [NEXT]B keys emulate the three mouse buttons -- allows rudimentary system 2 operations when the mouse is among the casualties.  A To enter or exit the "dead rodent" mode. press: [CTRL][SHIFT][F3]   < ------------------------------------------------------------2 DECW13. Why does half my DECwindows display blank?  > This is likely a result of receiving an OPCOM or other console< message on a system that shares the system console with the ( DECwindows graphics workstation display.  ? You can toggle off the console display window using <CTRL/F2>, .8 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.u  > On older releases, you can disable output using the following:  *   SET TERMINAL/PERMANENT/NOBROADCAST OPA0:   DEFINE/USER SYS$COMMAND OPA0:p   REPLY/DISABLE   * 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 loadedt    > 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 CURRENTn     SYSGEN> SET WINDOW_SYSTEM 1      SYSGEN> WRITE ACTIVE     SYSGEN> WRITE CURRENTt     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:e       $ MCR SYSMAN     SYSMAN> IO SHOW PREFIXK     SYSMAN> IO SET PREFIX=(DECW$,*)   * = list returned by the show command      SYSMAN> IO AUTO/LOGd     SYSMAN> EXITH 3) Ensure that the image SYS$SHARE:DECW$ICBM.EXE is installed in memory.+    If it is not installed, then install it:M  +     $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBMT  )     $ INSTALL REPLACE SYS$SHARE:DECW$ICBM.  #     $ EDIT SYS$MANAGER:SYCONFIG.COMw  0       $! The following line was added to install-       $! support for the Mach64 Graphics Card        $!+       $ INSTALL REPLACE SYS$SHARE:DECW$ICBM 
       $ ^Z       $ SHUTDOWN    REBOOT the system."  E If the system still complains that NO GRAPHICS DEVICES COULD BE FOUNDo then:m    4)   o Boot the system as normal      o Login as "system"      o Create the file:i=          $ SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT (W:RE)r7      o Add the following string on the very first line:            CLEAR_PFLAG = ISA_4BYTE      o Save the file      o Set the file protectionsl      o Reboot the system  
      EXAMPLE:A  9      $ create SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DATS        CLEAR_PFLAG = ISA_4BYTE	        ^Z   M      $ SET FILE/PROTECTION=(W:RE) SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT 
      $ REBOOT    Also see DECW6 					[Kleinsorge, Hoffman]  < ------------------------------------------------------------0 DECW15. How can I reset the warning bell volume?  A   With DECwindows CDE drivers and ECOs starting with ECOs for the G   DECwindows keyboard driver SYS$IKBDRIVER.EXE in OpenVMS Alpha V7.1-2  I   and V7.2-1 and with the SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1  G   and later, the DECwindows CDE controls will now correctly manage the  &   setting of the warning bell volume.   G   Unfortunately, the equivalent controls in the older DECwindows Motif nD   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:d  #     $ @decw$utils:decw$define_utilsn     $ xset b 1 100 100  A   The numerics are the volume, pitch, and duration, respectively.t  G   Why?   When OpenVMS first started supporting the PC-style keyboards, .I   the X Windows Server and the keyboard driver interface did not support eA   the pitch and duration, and neither did DECwindows Motif.  The IG   DECwindows keyboard driver was accordingly changed to use the volume  E   from the keyclick setting (keyclick is not available in a PC-style @J   keyboard) and the bell volume setting to control the pitch and duration.  E   DECwindows CDE does provide sliders for setting pitch and duration,AG   so the keyboard driver and X Windows Server were modified to provide nI   all of the information, and now the DECwindows CDE sliders work.  This TF   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.l  < ------------------------------------------------------------4 DECW16. How can I alter the DECwindows CDE backdrop?  C To select a separate backdrop to be displayed on each screen using V DECwindows CDE:   # 1. Click on the Appliction Manager. .    This is the drawer icon on the CDE toolbar. 2. Click on Desktop Tools = 3. Click on Set Default Screen and select the required screenn 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.A  >                                              [Geoff Kingsmill]  < ------------------------------------------------------------8 DECW17. How can I enable the DECwindows TCP/IP Transport  E   To configure the TCP/IP transport for DECwindows, first ensure that H   a TCP/IP package is installed and configured.  Then set the DCL symbolE   DECW$SERVER_TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COMtE   to the appropriate local value, based on the comments in that file.A  I   If you do not have a copy of SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM,RE   the use the following COPY command to create this file based on thei   provided template file:n  9     COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE -s9          SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COMv    < ------------------------------------------------------------ MISC1 relocated to WIRES1   < ------------------------------------------------------------E MISC2.  Where can I find information on escape and control sequences?o  G Information on escape and control sequences can be found in the OpenVMSnC I/O User's Reference Manual, in the section on the terminal driver.nB This section includes details on the general format and content of these sequences.  C Specific details on the escape and control sequences supported by aaA particular serial device are typically found in the documentation A provided with the specific device.  Information on the sequences -F supported by DECwindows DECterm terminal emulator are included in the  DECwindows documentation.a  G Examples of common escape and control sequences -- those typically usedWH 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 hH replaced by the sequence "<ESC>[" (without the quotes) particularly for E seven-bit operations, SS3 is decimal code 143 and can be replaced by yC "<ESC>O" particularly for seven-bit operations.  Older VT1xx series	F terminals and any other terminals operating with seven-bit characters ? should not be sent eight-bit operators such as <CSI> and <SS3>.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>ufI KP6=<SS3>v KP7=<SS3>w KP8=<SS3>x KP9=<SS3>y KPCOMMA=<SS3>l KPMINUS=<SS3>mFI KPPERIOD=<SS3>n ENTER=<SS3>M DNARROW=<CSI>B UPARROW=<CSI>A LFARROW=<CSI>DcH 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~ @ 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~-  = An example of working with escape sequences (in DCL) follows:c   $ esc5m = "*[5m" $ esc5m[0,8] = 27  $ esc0m = "*[0m" $ esc0m[0,8] = 2702 $ write sys$output esc5m + "blinking text" + esc0m  H Documentation on an ANSI terminal relatively similar to the VT525 series is available at:  4 ftp://ftp.boundless.com/pub/text/adds/docs/260_prog/4 ftp://ftp.boundless.com/pub/text/adds/docs/260_user/   Also see DECW9, DCL12.  < ------------------------------------------------------------ MISC3 relocated to SUPP4  < ------------------------------------------------------------ MISC4 relocated to WIRES2   < ------------------------------------------------------------F MISC5.  Where can I find performance info and specs for older systems?  
 See ALPHA5  < ------------------------------------------------------------C MISC6.  What does "failure on back translate address request" mean?i   The error message:  <   BCKTRNSFAIL, failure on the back translate address request  I indicates that the destination node is running DECnet-Plus, and that its aE naming service (DECnet-Plus DECdns, LOCAL node database, etc) cannot lE locate a name to associate with the source node's address.  In other wG words, the destination node cannot determine the node name for the nodeM. that is the source of the incoming connection.  G Use the DECNET_REGISTER mechanism (on the destination node) to registersD 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 LOCAL C namespace.  This can be a problem elsewhere, however.  Very rarely,iD a cache corruption has been known to cause this error.  To flush the cache, use the command:f  1 NCL> flush session control naming cache entry "*"   C Also check to see that you are using the latest ECO for DECnet-Plus   for the version you are running.  - DECnet-Plus can use the following namespaces: 2   o DECdns: DECnet-Plus distributed name services.;   o LocalFile: a local file containing names and addresses.-/   o DNS/Bind: the IP distributed name services.U   o The UCX local host file.   					[Stephen Hoffman]  < ------------------------------------------------------------5 MISC7. How to determine the network hardware address?I  A   Most Alpha and VAX systems have a console command that displaystF   the network hardware address.  Many systems will also have a stickerD   identifying the address, either on the enclosure or on the network   controller itself.  C   The system console power-up messages on a number of VAX and Alpha B   systems will display the hardware address, particularly on those>   systems with an integrated Ethernet network adapter present.  E   If you cannot locate a sticker on the system, if the system powerupvD   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 DEVICEW   >>> SHOW ETHER   >>> SHOW CONFIGC  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:h     >>> E/P/W/N:5 20001920  G   Look at the low byte of the six words displayed by the above command.aE   (The oldest VAX Q-bus systems -- such as the KA630 processor modulefD   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)dF   bootstrap requests (via DECnet Phase IV, DECnet-Plus, or LANCP), the1   MOM$SYSTEM:READ_ADDR.EXE tool can be requested:f     >>> B/R5:100 ddcuh   Bootfile: READ_ADDRs  I   Where ddcu is the name of the Ethernet controller in the above command.4J   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,MI   and (if the download is successful) READ_ADDR will display the hardwareo
   address.  G   If the system is running, you can use DECnet or TCP/IP to display thep6   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 laterc  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:i  >     http://www.openvms.digital.com/wizard/swdev/ethernVMS.html  E   To use the DECnet Phase IV configurator tool to watch for MOP SYSIDC%   activity on the local area network:l  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:f  E   $ NCP SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txthC   $ 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 SYSID-H   messages identifying items such as the controller hardware address andE   the controller type, and these messages are generated and multicasto   roughly every ten minutes.  E   Information on the DECnet MOP SYSID messages and other parts of theiF   maintenance protocols is included in the DECnet network architecture,   specifications referenced in section DOC9.  < ------------------------------------------------------------ MISC8 combined into SUPP4i  < ------------------------------------------------------------@ 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 hE   Microsoft Windows NT option to disable authentication during a RAS  G   connection apparently doesn't currently work -- RAS connections will lG   require authentication -- and this will thus prevent RAS connections. @                                                [Stephen Hoffman]  < ------------------------------------------------------------ MISC10 relocated to SUPP5n  < ------------------------------------------------------------> MISC12. Does DECprint (DCPS) work with the LRA0 parallel port?  = The parallel printing port LRA0: found on many OpenVMS Alpha e= systems is capable of some bidirectional communications, with 8 enough for basic operations with most parallel printers.  ? DECprint (DCPS) requires more than just the simple handshaking h> provided by the LRA0: port, therefore DCPS does not work with  the LRA0: port. 4                                      [Paul Anderson]  < ------------------------------------------------------------9 MISC13. How do I check for free space on a (BACKUP) tape?i  > You cannot know for certain, though you can certainly estimate the remaining capacity.C  ? 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 these  bad block replacements.   @ The capacity of tape media is not nearly as pre-determined, and ; the capacity can vary across different tape media (slightlyh: 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 -= the tape, the numbers of correctable and uncorrectable media CC errors that might occur, the numbers and sizes of the inter-record O> 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 approximatelyi@ 15% overhead, in terms of saveset size.  (eg: Assuming a 500 KB ' input, the total size would be 575 KB.)i     Assuming no compression:0    4 GB media / 575 KB saveset =  7294 savesets      Assuming 1:2 compression:T0    8 GB media / 575 KB saveset = 14588 savesets   C NB: There are no inter-record gaps on DAT tapes.  (When determiningNB media capacity, you have to consider these with nine-track magtapeE media.  Not with DAT (DDS).  However, the block structure underneath -G the variable length record recording is based on a block size of circa 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 tA inter-record gaps on DAT, larger savesets are still usually best.e  E The compression algorithms used on various devices are generally not  F documented -- further, there is no way to calculate the effective dataF compression ratio, the tape mark overhead, and similar given just the E data to be stored on tape -- short of actually trying it, of course.    C A typical compression ratio found with "everyday" data is somewhereO 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.MG                                           [Hoffman, Froehlin, Williams]   < ------------------------------------------------------------( MISC14. So what happened to sys$cmsuper?  ! There is no SYS$CMSUPR service.  n  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 :> 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.D:                                     [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 thatRA can generate and transmit messages to radio pagers.  Target Alert = (Target Systems; formerly the DECalert product) is another.   ? Networking Dynamics Corp has a product called Pager Plus.  The -< System Watchdog package can also send pages.  PMDF can route6 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.K  ? See SOFT1 for information on the available catalog of products.d  < ------------------------------------------------------------ MISC16 relocated to WIRES3  < ------------------------------------------------------------: MISC17. How do I reset the LAN (DECnet-Plus NCL) counters?   On recent OpenVMS releases:m  ;   LANCP> SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devname     < ------------------------------------------------------------4 MISC18. What are the prefixes for the powers of ten?  $         Power   Prefix  Abbreviation         10^-18  atto    a?         10^-15  femto   fe         10^-12  pico    pe         10^-09  nano    n          10^-06  micro   v         10^-03  milli   mt         10^-02  centi   cn         10^-01  deci    ds         10^+01  deca    da         10^+02  hecto   hi         10^+03  kilo    ku         10^+06  mega    Me         10^+09  giga    Gl         10^+12  tera    Tb         10^+15  peta    Pe         10^+18  exa     Ea    < ------------------------------------------------------------4 MISC19. OpenVMS Cluster (SCS) over DECnet?  Over IP?  = The OpenVMS Cluster environment operates over various networkn6 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 eB 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, uD 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.)e  @ The usual approach for multi-site OpenVMS Cluster configurationsG involves FDDI, Memory Channel (MC2), or a point-to-point remote bridge,RD brouter, or switch.  The connection must be transparent, and it mustC operate at 10 megabits per second or better (Ethernet speed), with f> 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?   @   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 setrC   of PAKs registered across all licensing databases present in the f   OpenVMS Cluster.  A   If your software license permits it, you can use the following n(   two commands to transfer license PAKs:       $ LICENSE COPY...f5     $ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,...d  A   To display the particular license(s) required (such as when youc=   receive a NOLICENSE error), use the following DCL sequence:v       $ SET PROCESS/PRIVILEGE=ALL-     $ REPLY/ENABLE7     $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGEw  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 hH   various products can check for and can be enabled by multiple license ?   PAKs.  You will want to deassign this logical name when done.a  '   Some of the more common license PAKs:w  B   DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*B   DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*)   TCP/IP Services:   UCX, or NET-APP-SUP*e9   OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USERa   OpenVMS VAX:       VAX-VMS#   OpenVMS Galaxy:    OPENVMS-GALAXY<-   Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP*<-   Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*S  E   Various NET-APP-SUP (NAS) license packages are available, each withPD   differing collections of products authorized.  See the various NASD   Software Product Description (SPD) documents for specific details.  %   http://www.digital.com/info/SPHOME/R  < ------------------------------------------------------------C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?I  A Details on many commercial OpenVMS products are available in the ~ catalog located at:e  ,   http://www.partner.compaq.com/www-catalog/     ----  ? An OpenVMS Freeware CD is distributed with OpenVMS, and is also[B available separately.  The contents of the OpenVMS Freeware CD is  also available online at:i  0         http://www.openvms.digital.com/freeware/         ftp://ftp.montagar.com/o'         ftp://mvb.saic.com/freewarev40/.$         http://freeware.acornsw.com/  F and at various other sites.  The website also includes various updatesF and new packages that become available after the CD-ROM distributions  are created.  4 Submissions to the OpenVMS Freeware can be made via:  ?         http://www.openvms.digital.com/openvms/freeware/cd.html.  E To acquire the OpenVMS Freeware CD-ROM distribution, you can order anLC OpenVMS distribution from Compaq (the Freeware is included)(see the H OpenVMS SPD for part numbers), or you can specifically order a Freeware + distribution from Compaq under part number:   
   QA-6KZAA-H8e  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-requestedrI OpenVMS tools on the Freeware CD include ZIP and UNZIP, GZIP, MMK (make),eG PINE, PERL, TAR, UUENCODE and UUDECODE.  Many other tools are available  on the Freeware.       ----  J Compaq also has a separate area containing various OpenVMS software tools  located at:   !   http://ftp.digital.com/pub/VMS/u     ----  ; Western Kentucky University (and madgoat) OpenVMS archives:e  ,   http://www2.wku.edu/fileserv/fileserv.html   http://www.madgoat.com/n;                                            [Hunter Goatley]      ----  @ The FILESERV packages are also available via anonymous FTP from:     Via anonymous FTP from:s'     ftp.wku.edu, under [.VMS.FILESERV].h/     ftp.process.com, under [.WKU.VMS.FILESERV].i5     ftp.spc.edu, under [.MACRO32.SAVESETS] and [.MX]. >     ftp.vms.stacken.kth.se, under [.MIRRORS.WKU.VMS.FILESERV].1     ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].l     ftp.riken.go.jp 3     ftp.vsm.com.au, under kits and kits/decwindows. /     ftp.vsm.com.au, via the WWW instead of FTP.e  F or via e-mail from FILESERV@WKUVX1.WKU.EDU. Send the commands HELP and>    DIR ALL in the body of a mail message for more information.     ----  L If you get the packages via WWW or FTP, they're in ZIP format which requiresJ the UNZIP (note: this is not Gnu gunzip!) tool to unpack.  You can get ZIP# and UNZIP from the following areas:   .   ftp://ftp.wku.edu/vms/unzip.exe        ! VAX0   ftp://ftp.wku.edu/vms/unzip.alpha_exe  ! Alpha*   ftp://ftp.wku.edu/vms/fileserv/UNZIP.ZIP/   http://www.decus.de:8080/www/vms/sw/zip.htmlxh,   http://home.earthlink.net/~djesys/zip.html.   http://home.earthlink.net/~djesys/unzip.html  E or you can request the FILESERV_TOOLS package from the e-mail server.k  D [Beware: The [000TOOLS...] pre-built versions of ZIP on the OpenVMS G Freeware V4 CD-ROM will erroneously return BILF errors on OpenVMS V7.2 ,D and later.  Use of the source on the Freeware V4 to rebuild the ZIP I image(s), or acquiring a pre-built ZIP image from one of the above areas rH can avoid this.  The pre-built version of ZIP on the Freeware V4 kit is C older than the included ZIP sources, and it contains a latent bug.]   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 submissionse to vmsnet.sources.     ----  K Arne Vajhj runs an OpenVMS WWW page, with software and other pointers, at:    http://www.levitte.org/~ava/     ----   Kermit is available at: $   http://www.columbia.edu/kermit/ or   ftp://kermit.columbia.edu/     ----   ZMODEM is available at:s!   ftp://ftp.cs.pdx.edu/pub/zmodema9 See the FILES file in that directory for further details.aF Note that this freeware version of ZMODEM will interoperate only with 6 ZMODEM software that is licensed from Omen Technology. (Also on Freeware CD)e 				[Steve Lionel]     ----  G A good source of software for DEC boxes (and anything else pretty much)tC is the DECUS library. online catalogs are available as well as somee4 software via ftp.decus.org; there's a gopher server    gopher://gopher.decus.org/ an FTP server:   ftp://ftp.decus.org/ and a WWW server:    http://www.decus.org/l  3 Some DECUS library CD-ROMs are available online at:D:     http://www.acornsw.com/www/acorn/cdrom-via-www.html or      gopher://gopher.acornsw.com/ 				[munroe@dmc.com]  H Phone for DECUS orders is 508-841-3502. Lots of good stuff from lots of 7 good folks, and copies on media (tapes, CDs) are cheap.  				[Everhart@Arisia.gce.com]*     ----  J    MPJZ's Hyper-Software-List for OpenVMS is Martin P.J. Zinser's list of     additional software.  I.      http://axp616.gsi.de:8080/www/vms/sw.html     ----  (    Chris Higgins's VMS Software List II 6      http://csvax1.ucc.ie/www/vms_sw_list/sw_list.html     ----  G    DECUS SIG Tape collections are available on Mark Berryman's system, d      ftp://mvb.saic.com/     ----  M    David Jones's DECthreads-based HTTP_SERVER World-Wide Web server for VMS. e<      http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html 					    [Hunter Goatly]     ----  )    Secure Shell (SSH) Server for OpenVMS: 5      http://kcgl1.eng.ohio-state.edu/~JONESD/ssh/DOC/   )    Secure Shell (SSH) Client for OpenVMS:n       http://www.free.lp.se/fish/  /    Information on OpenSSL (SSLeay) for OpenVMS: #      http://www.free.lp.se/openssl/O8                                             [Leo Demers]  D    Information on OpenSSL (SSLeay) and OSU Webserver interoperation:-      http://www.ourservers.net/openvms_ports/o     ----  G DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4 built for UCX.  V1.2-4sB 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 r is available from:    ftp://wvnvms.wvnet.edu/mosaic/     ----  ? Lynx (a character-cell World-Wide-Web reader) is available from."   ftp://ftp2.cc.ukans.edu/pub/lynx 					    [Steve Lionel]-     ----  = Netscape Navigator and Mozilla web browsers are available at:-@   http://www.openvms.digital.com/openvms/products/ips/index.html   http://www.mozilla.org/n     ----  F PGP (Phil Zimmerman's "Pretty Good Privacy") is available from variousH distribution sites, including those listed in the PGP FAQ.   Information. on an OpenVMS download of PGP is available at:   http://www.pgpi.com/(   http://zone.pspt.fi/pgp/platforms/vms/)   http://www.yrl.co.uk/~phil/pds/pds.html      ----  D An archive of DECwindows and X Windows software can be found at the  following sites:  1   http://www2.cenaath.cena.dgac.fr/ftp/index.html-2   http://www2.cenaath.cena.dgac.fr/ftp/decwindows/    ftp://axp.psl.ku.dk/decwindows   ftp://ftp2.cnam.fr/decwindowsp$   ftp://ftp.et.tudelft.nl/decwindows$   ftp://ftp.ctrl-c.liu.se/decwindows<   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html    (See also Freeware CD) 					    [Patrick Moreau]e     ----  I ImageMagick is an X11 package for display and interactive manipulation ofCE images.  The package includes tools for image conversion, annotation, I compositing, animation, and creating montages.  ImageMagick can read and -I write many of the more popular image formats (e.g. JPEG, TIFF, PNM, XPM, o Photo CD, etc.). e=   ftp://ftp.x.org/contrib/vms/ImageMagick/ImageMagick-3.3.zipy (Also on Freeware CD)f 					    [cristy@dupont.com]     ----   XV is available from:d    ftp://ftp.cis.upenn.edu/pub/xv'   ftp://ftp.digital.com/pub/graphics/xva   http://www.sanface.com/ 8   ftp://www-pi.physics.uiowa.edu/~dyson/xv-3_10a-vms.zip     ----  I Many software packages are available for displaying various bitmap files eJ (.JPG, .GIF, .BMP, etc) on OpenVMS.  Xloadimage, Xli, Xv, ImageMagick are G the most common tools used under OpenVMS.  Various web browsers such as H Mozilla (qv) can also display various file formats on OpenVMS.  You can 3 find some of these tools at the DECwindows Archive:   3   http://www.multimania.com/pmoreau/decw/index.html 4   http://www.multimania.com/pmoreau/decw/images.html;                                            [Patrick Moreau]h     ----  - GHOSTSCRIPT and GHOSTVIEW are available from: )   ftp://ftp.digital.com/pub/VMS/ghostview,  3 Version 2.3 of GhostView-VMS is now available from:s+   ftp://iphthf.physik.uni-mainz.de/pub/vms/d* 					   [plass@dipmza.physik.uni-mainz.de]	 Also see:P$   http://www.cs.wisc.edu/~ghost/gnu/     ----  @ XPDF, a viewer for PDF (Adobe Acrobat) files, is available from:   http://www.foolabs.com/xpdf/9                                             [Ki Suk Hahn]e  <   Beware: the XPDF on OpenVMS Freeware V4 is somewhat dated.     ----    L A Java-based PDF viewer is available from Adobe, and is known to operate on  recent OpenVMS Alpha releases:   http://www.adobe.com/      ----  H Various OpenVMS-related tools -- both freeware and shareware -- such as ! txt2pdf -- are available from at:h   http://www.sanface.com/c     ----  F The MPEG library version 1.1 is available for OpenVMS VAX and Alpha at3   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readmen0   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip 					    [Patrick Moreau]g     ----  4 List of FTP Mirror Sites for the DECWINDOWS archive:  A AXP.PSL.KU.DK             (Multinet)  Mirror of CENA DECW archivetA FTP.ET.TUDELFT.NL         (MadGoat)   Mirror of CENA DECW archivetA FTP2.CNAM.FR              (MadGoat)   Mirror of CENA DECW archivee  I ftp.x.org (in /contrib/vms)  not really a mirror, but I try to put all myo new ports at this site.d     ----  5 List of HTTP Mirror Sites for the DECWINDOWS archive:s  ;   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.htmll  = Some X clients from the OpenVMS Freeware CDROM are located in # [.DECWINDOWS.CDFREEWARE] directory.s 						[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.mM It contains now listings for over 30 ftp servers with >14 GB of VMS software.uH 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",UL and regex search is not supported (so FIND EMACS will work, but FIND *EMACS*< or FIND *EMACS*.* will not). The search is case-insensitive.I Those of you that know other ftp servers with VMS software that I haven't-D found, please let me know. (The program that build the databases canI recursively scan whole servers- as FTP.WKU.EDU, or just some directories-b as NIC.SWITCH.CH /pub/vms)H Sorry, this service is VERY SLOW [by Western standards], because it runsJ on a quite-busy oldie-but-goodie VAXStation 3400 with 20Mb and a RF71, and; the Internet link is only 256 Kpbs (sometimes unavailable).  						[stfp@roipb.cs.ipb.ro]     ----  9   The Levitte (extended :-) Family (and OpenVMS) website:      http://www.levitte.org/h      http://www.levitte.org/~ava/     ---t  E   Robert's OpenVMS Hobbyist Systems, including OpenVMS public domain a   software and various ports:s       http://www.ourservers.net/  <                                           [Robert Alan Byer]   ----     CalTech Software Archives:?     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/AAA_CONTENTS.TXTc     ----  *   DJE Systems Website (David J. Dachtera) 3     http://home.earthlink.net/~djesys/freeware/vms/E     ----     Web servers:     Apache web server:A       http://www.openvms.digital.com/openvms/products/ips/apache/u=       http://www.er6.eng.ohio-state.edu/~jonesd/apache/1_3_9/E     OSU WebserverI?       http://www.er6.eng.ohio-state.edu/www/doc/serverinfo.html-#       http://www.kjsl.com/archives/t1       email list: VMS-WEB-daemon-Request@KJSL.COM      ----  #   CD-R (CD-Recordable) media tools:?     please see FILE7     ----  "   Grace (WYSIWYG 2D plotting tool),     http://plasma-gate.weizmann.ac.il/Grace/     ----  K   POV-Ray ("Persistance of Vision" Raytracer) ray-tracing graphics package: G     http://www.ourservers.net/openvms_ports/povray/povray_contents.htmlu<                                           [Robert Alan Byer]     ----  !   Majordomo mailing list handler: B     http://www.openvms.digital.com/openvms/products/ips/majordomo/     ----  ;   PINE (OpenVMS tools for sending and receiving MIME mail): *     ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/3     http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/r  5   A MIME tool is available in OpenVMS V7.2 and later.   >   Also see the mmencode base64 encode and decode available at:9     http://nucwww.chem.sunysb.edu/htbin/software_list.cgi         ----  6 Menufinder (menu-driven system management environment)"    (currently free on OpenVMS VAX)'    http://www.itre.com/mf/download.htmle!    ftp://ftp.itre.com/menufinder/      ----   tcgmsg, pvm, mpi, linda:<   ftp://v36.chemie.uni-konstanz.de/tcgmsg_vms/tcgmsg_vms.zip     ----  E OpenVMS software that can control a Tripp-Lite Uninterruptable Power t Supply (UPS) is available from:l  ;     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/TCONTROL.ZIPm:                                             [David Mathog]  : OnliSafe Software for the PowerWare UPS is available from:E     http://www.powerware.com/2products/software/onlisafe/onlisafe.htm :                                             [Janis Cooper]  B UPShot web-based software for controlling a UPS is available from:(     http://www.tmesis.com/apc/beta.htmlxA                                             [Brian Shenkenberger]t       ----  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://www2.wku.edu/scripts/fileserv/fileserv.com?MLSEARCHv  <                                             [Phillip Helbig]     ----? AscToHTM attempts to convert any plain text file to HTML, whilea> AscToTab restricts itself to files that are plain text tables.5 (Versions are also availabe on the OpenVMS Freeware).P.     http://www.jafsoft.com/asctohtm/index.html.     http://www.jafsoft.com/asctotab/index.html1                                             [Jaf]i     ----  = Information on the SAMBA package (PC disk and print services)  is available at:8   http://ifn03.ifn.ing.tu-bs.de/ifn/sonst/samba-vms.html    http://samba.anu.edu.au/samba/  E To subscribe to the SAMBA-VMS mailing list e-mail listproc@samba.org e; with no subject line and the following single line of text:   #  subscribe samba-vms Your Full Name_  	 Also see:w   http://lists.samba.org/l     ----   Perl: See SOFT12     ----   XML:  8   Source code of an XML Parser is available from Oracle.     Also see:h  '     http://www.python.org/sigs/xml-sig/l  < ------------------------------------------------------------@ 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.P  @     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 withV?     OpenVMS V5.5 later.  The POSIX installation kit is included A     on the consolidated distribution CD-ROM kit, and installation '     kits are also available separately.N  D     The POSIX package is no longer supported on OpenVMS, components C     of the POSIX standard such as parts of the POSIX API are being -C     added into OpenVMS.  Versions of POSIX generally do not operatew3     on V7.x OpenVMS VAX and OpenVMS Alpha releases.n   C: rH   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 coexistnJ   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:w     and UCX$EXAMPLES: areas.  
 X Windows:%   Various Compaq X Windows utilities:w  G     xwd, xev, mosaic WWW browser, xrdb, bmtoa and atobm, xpr, ico, etc.e  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:w6   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,aB     the mx SMTP mail exchange package, X windows flight simulator,C     the mxrn X windows news reader, the OSU HTTPD WWW server, a WWWr=     gopher browser, etc. are all on the FreeWare V2.0 CD-ROM.k  	 IP tools:tE   DEC TCP/IP (UCX) contains tools such as ping, uuencode, smtp, snmp,SG   rcp, nfs, tnfs, etc.  OpenVMS V6.2 and UCX V3.3 and later can be usedZF   together in support of the /FTP, /RCP, /RLOGIN, /TELNET, and /TN3270%   qualifiers on various DCL commands.t  4     Also see the various C examples in UCX$EXAMPLES:   					[Stephen Hoffman]  	 vi clones   1   Both vile and elvis (vi clones) run on OpenVMS.V  $   The current version of vile is 7.1   It's available atp/ 	http://www.clark.net/pub/dickey/vile/vile.htmlv$ 	ftp://ftp.clark.net/pub/dickey/vile 	ftp://id.wing.net/pub/pgf/vile 2 	Versions of VILE are also on the OpenVMS Freeware   					[Thomas Dickey]     vim: vi improved      http://www.polarfox.com/vim/9                                         [Zoltan Arpadffy].  
 GNU tools:  I   Information on the GNU on VMS Project, which aims to port GNU software M   to VMS, is available at:       http://vms.gnu.ai.mit.edu/%     ftp://vms.gnu.ai.mit.edu/gnu-vms/W     Software info:  '     http://vms.gnu.ai.mit.edu/software/n     Software archive:n  .     ftp://vms.gnu.ai.mit.edu/gnu-vms/software/  
 GNV tools:  *   BASH (Bourne Again Shell) (part of GNV):   http://gnv.sourceforge.net/L     GCC:  I   A mirror for work performed at the Progis company in Germany in portinge?   GCC (GNU C) to OpenVMS Alpha and OpenVMS VAX is available at:   '     ftp://vms.gnu.org/progis_mirror/gcca  K   The latest (known to me) GCC version for VAX/VMS (binaries only) is 2.7.1d   from Pat Rankin's site.   &     ftp://ftp.caltech.edu/pub/rankin/   G                                     [Jason Armistead, Richard Levitte, :C                                     Arne Vajhoej, John E. Malmberg]t  I There are also updated header files for GCC on OpenVMS VAX that allow it F6 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:e  1   http://www.robomon.com/robocentral.htm (Heroix)i1   http://www.ki.com/products/clim/  (KI Products)s,   http://www.globalmt.com/ (Global Maintech)!   http://www.tditx.com/ (TechSys)e0   http://www.cai.com/products/commandit.htm (CA)3                                        [Kerry Main]t  A If you need to change the file modification date and are looking d> for a utility such as the UNIX touch tool, look at DFU on the > OpenVMS Freeware (DFU SET or simular), or use an existing DCL  commands such as:   5   SET FILE/PROTECT=(current_protection_mask) [...]*.*     @ A table listing translations between UNIX shell and OpenVMS DCL 8 commands was posted to comp.os.vms by Christopher Smith:     http://deja.com/getdoc.xp?.     AN=581596523.1&CONTEXT=953337549.952369155     --  3 The UNIX touch tool is available via various means:f  !   $ RENAME filename.ext;version *f7   http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCHM.   MadGoat FILE tool (see the MadGoat archives)(     use /REVISION_DATE or /CREATION_DATE)   The DFU tool (see the OpenVMS Freeware)r   The pair:e5     $ set file 'p1' /acl=(ident=[system],access=none)y=     $ set file 'p1' /acl=(ident=[system],access=none) /deletef   SET FILE/VERSION=0   The following hack:h&     $!   Command procedure SETDATE.COM     $!1     $!   Changes the DATES for an input file to ac     $!   file named OUTFILE.     $!     $assign/nolog 'p1' outfile(     $convert/fdl=sys$input 'p1' outfile:     date     creation   01-apr-2010     expiration 01-Apr-2012     revision   01-Apr-2011
     backup     ...s,   The following RMS system service sequence:     $open (with xabrdt)D(     set the desired values in the xabrdt
     $close  < ------------------------------------------------------------I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser?0  > OpenVMS Engineering is currently porting mozilla.org's browserF to OpenVMS -- OpenVMS baselevels are currently available for download.C Mozilla.org is the open source organization providing Netscape and eB other interested parties with a browser.  Netscape is expected to C commercialize this mozilla.org browser, add additional proprietary cG features, and release it as Netscape Communicator (version number TBD). G This Netscape Communicator will contain the features that the Internet .6 community expected to see in Netscape Communicator V5.  D Mozilla.org has announced that it will release a beta version of itsE browser in mid-Autumn 1999.  Soon after, Netscape may/will release a eG beta version of Netscape Communicator based on the mozilla.org browser.fF We expect the beta version of Netscape Communicator to be available onH OpenVMS about 1 month after its release by Netscape.  A customer qualityG version of this browser is scheduled for release by mozilla.org in lateaK December 1999; soon after, Netscape will release a customer quality versionaB of Netscape Communicator.  We expect to release a customer quality: version of Netscape Communicator on OpenVMS in early 2000.  1 The mozilla.org browser schedule is available at:   !   http://www.mozilla.org/project/W  > The latest information and current downloads are available at:  6   http://www.openvms.digital.com/openvms/products/ips/  H Please be aware that various certificates for V3.003 Netscape Navigator G are presently expired, or are starting to expire.  This can potentially-G cause problems for certificate-based access pending the acquisition of o new certifcates.   					[Sue Denham]  					[Stephen Hoffman]  < ------------------------------------------------------------+ SOFT4.    Where can I get Java for OpenVMS?g  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 .H   definition requires a floating point format (IEEE) that is not native E   to VAX, and this would require the emulation of all floating point 1H   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 rI   for OpenVMS VAX -- and specifically to the VAX VCG code generator that rH   is used by Compaq C on OpenVMS VAX systems -- in order to add support I   for passing IEEE-format floating point doubles around.  Alternatively, DJ   extensive changes to the Java source code to remove the assumption that -   the double is an IEEE floating point value..  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,a6   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.c  F   For additional information on Java for Alpha systems, please see theA   OpenVMS documentation (V7.2 and later), and the following site:o  0     http://www.digital.com/java/alpha/index.html  < ------------------------------------------------------------J SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?  F   VAX C V3.2 was released for OpenVMS VAX systems in 1991.  DEC C V4.0F   replaced VAX C V3.2 in 1993 as the Compaq C compiler for OpenVMS VAXF   systems.  Compaq C is the AMSI C compiler for OpenVMS Alpha systems.E   VAX C predates the ANSI C standards, and has various areas that aredJ   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 F   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.t  K   A current "C" license PAK allows access to both VAX C and Compaq C on theo   same OpenVMS VAX system.  M   Various Compaq C versions can be installed on OpenVMS VAX V5.5-2 and later. L   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, aI   but Compaq C RTL ECO kits are available to resolve problems found with h(   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 an E   existing C library routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)). E   (VAX C required explicit specification of an RTL shareable image ore$   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 theDG   external symbols against the symbols present in the DECC$SHR library.cF   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,.I   and the external routines share the same names as the library routines.bF   (This is not recommended, but there are applications around that useE   this technique.)  Thus the need to explicity specify whether or notiE   the "decc$" prefix should be prepended to the external symbol names.   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_ENTRIES-B       As mentioned above.  Failure to specificy this qualifier canA       cause the compiler to not add the prefixes for the names ofpE       the C library routines into the references placed in the object/E       module, which can in turn cause problems resolving the external3<       symbols in the library when the object code is linked.  $     /ASSUME=WRITABLE_STRING_LITERALSC       Some VAX C programs erroneously write to the string literals.KB       By default, Compaq C does not allow the constants to change.       /SHARE_GLOBALSA       Enables sharing ("shr") of globals and of extern variables.mG       Compaq C sets externs as non-shareable ("noshr"), VAX C as "shr".r       /EXTERN_MODE=COMMON_BLOCK =       VAX C assumes common block model for external linkages.n       /[NO]MEMBER_ALIGNMENT A       Refers to the padding placed between member elements withina?       a struct.  Disabling member alignment packs the data morep=       tightly into memory, but this packaging has performancee;       implications, both on OpenVMS VAX and particularly onb       OpenVMS Alpha systems.  E   Permit structure members to be naturally aligned whenever possible,pE   and avoid using /NOMEMBER_ALIGNMENT.  If you need to disable memberoA   alignment, use the equivilent #pragma to designate the specificlE   structures.  The alignment of structure members normally only comesiB   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 thewD   contents of the standard header libraries into directories such asG   SYS$SYSROOT:[DECC$LIB...], and provide various logical names that can G   be defined to control library searches.  With Compaq C versions such eH   as V6.0, the default operations of the compiler match the expectationsC   of most OpenVMS programmers, without requiring any definitions ofPG   site-specific library-related logical names.  (And logical names leftpE   from older DEC C versions can sometimes cause the compiler troubles    locating header files.)t  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  E   language RTLs ship with OpenVMS itself, and not with the compilers.   F   Example C code is available in SYS$EXAMPLES:, in DECW$EXAMPLES (whenF   the DECwindows examples are installed), in UCX$EXAMPLES (when CompaqE   TCP/IP Services is installed), on the Freeware CD-ROMs, and at web e   sites such as   *     http://www.openvms.digital.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 aG     tm_year.  This field will contain a value of 100 in the year 2000,  F     101 for 2001, etc., and the yearly incrementation of this field is     expected to continue./  G     The C epoch typically uses a longword (known as time_t) to contain /H     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.)r  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 savings J     time change might be).  This skew can be caused by incorrect handling J     of the "is_dst" setting in the application program, or by an incorrectH     OpenVMS UTC configuration on the local system.  (See section TIME4.)       Other common C++ issues:  G     Compaq C++ (a separate compiler from Compaq C) provides both symboltH     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 thefJ     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"	         {o(         extern int ExternSymbol(void *);-         extern int OtherExternSymbol(void *);-	         }-    G   Also see ALPHA16 for information on /ARCHITECTURE and /OPTIMIZE=TUNE.P   < ------------------------------------------------------------1 SOFT6.    Obtaining user input in DCL CGI script?C  E If you choose to use the GET method, then the form data is available q6 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 oE stdin. For a DCL CGI script running under the Netscape FastTrack web  ? server, you can read the data using the following READ command:c     $ READ SYS$COMMAND postdatae   to read the information in.i=                                                 [Colin Blake]m  @ 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?i  > To have a batch procedure retrieve its own batch entry number, use the following:  '   $ Entry = F$GETQUI("DISPLAY_ENTRY", -a0       "entry_number","display_entry","this_job")  E Remember that the entry numbers issued by the OpenVMS Job Controller iE are opaque longword values.  Don't assume you know the format of the  1 number, nor the range of numbers you might see...l>                                                 [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 librariesiC starting with V3.5-03 -- to ensure that earlier versions of CMS areoB unable to access the database once the "conversion" to V3.5-05 andG later is made, you must issue the following two commands when upgradingEB 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 npr< 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 compatibilityeE with tools that expect to find a 00CMS.CMS file (eg: various versions . 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        entrusthD http://www.equifaxsecure.com/servercert/rollover.html         thawteF https://www.verisign.com/server/prg/browser/root.html         verisign6                                           [Ken Chaney]  > To update certificates in Netscape Navigator V3.03 on OpenVMS, use the following:  8 Here's how to update your Root certificates in Netscape:  0 Thawte Server certificate which expired in 1998:  : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" 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:a  : 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 certificatesp, 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 suggestsh     using the name "VeriSign CA".  ;                                           [Vance Haemmerle]   < ------------------------------------------------------------3 SOFT10.   Why doesn't DCL symbol substitution work?e  F The DCL symbol substitution processing occurs only at the DCL prompt, E not within data and not within files.  If you wish to perform symbol  C substitution in this environment, you typically write a small file  E containing the command(s) and data to be invoked -- potentially only yC the data -- and you then invoke the created procedure or reference   the specified data.e  C In this case, use of a file containing nolinemode commands or othersC techniques might be useful -- you will want to ensure that the textoF 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 andaE the apostrophe.  In most cases, only the apostrophe is necessary.  InaG a few cases -- such as the DCL PIPE command -- you will may need to uselE the ampersand to get the substitution to work.  The following example B uses ampersand substitution to transfer the contents of the header into a logical name:  F   $ PIPE CC/VERSION | (READ SYS$PIPE hdr ; DEFINE/JOB/NOLOG hdr &hdr )  G A logical name (in the job logical name table; shared by all processes OG in the current job) was used as DCL symbols cannot be returned back outo, from a DCL PIPE or other spawned subprocess.    < ------------------------------------------------------------D SOFT11.   Preventing a serial terminal line from initiating a login?  *   In SYSTARTUP_VMS.COM, issue the command:  ,     SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:  @   This will prevent any unsolicited terminal input on ddcu:, andA   this unsolicited input is what triggers JOB_CONTROL to start up B   LOGINOUT on the terminal.  Once LOGINOUT starts up on the serial>   line, you can see interesting behaviour (eg: audits, processB   creations, etc) as LOGINOUT tries to "chat" with whatever device<   is hooked onto the remote end of the serial terminal line.  < ------------------------------------------------------------+ SOFT12.   Where can I get Perl for OpenVMS?   F OpenVMS support is included in the standard distribution of Perl, the I popular scripting language created by Larry Wall.  In addition to nearly :E all of the functionality available under Unix, OpenVMS-specific Perl  E modules provide interfaces to many native features, as well as 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 mH will find such things as download links, instructions, auxiliary tools, & and sample scripts -- is available at:  !      http://www.sidhe.org/vmsperle  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:   /      http://www.perl.com/CPAN/src/stable.tar.gzS  I You will need GUNZIP and VMSTAR (both available from the OpenVMS Freeware G CD, or from other sites) to unpack the archive; once you've done that, c- read the instructions in the README.vms file.-  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.html 2      http://www.openvms.compaq.com/freeware/perl5/  H During active Perl development cycles, test kits are sometimes found at: from:m  '      ftp://perl.newman.upenn.edu/perl5/t      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 eG OSU HTTP server, as well as more general tips, tricks, and patches for  % building and running Perl on OpenVMS:S  )      http://www.crinoid.com/crinoid.htmlxD  G There are OpenVMS-specific Perl modules that implement interfaces to a qH 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 n( relevant modules are all available from:  3      http://www.perl.com/CPAN/modules/by-module/VMSg  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:n       vmsperl-subscribe@perl.org  - The mailing list archives may be searched at:a  4     http://www.xray.mpe.mpg.de/mailing-lists/vmsperl;                                               [Craig Berry]n     [End of Part 4/5]   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 17 Aug 2000 22:07:12 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 5/5 6 Message-ID: <8nhnmg$3j0$1@mailint03.im.hou.compaq.com>   Archive-name: dec-faq/vms/part5p Posting-Frequency: monthly Last-modified: 17 Aug 2000 Version: VMS-FAQ-5.TXT(4)L      9 This is the OpenVMS Frequently Asked Questions Part 5/5. i@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------, ALPHA1.   What do the letters AXP stand for?  I While there are many fanciful "definitions" which have circulated widely,iH the truth is that AXP is not an abbreviation nor an acronym; the lettersC do not mean anything.  They are just three letters chosen to form at
 trademark.  E When it came time to chose a "marketing name" for the Alpha AXP line, I the company was in a quandary.  The internal "code name" for the project,wK Alpha, was widely known and would seem the ideal choice, but it was alreadyOJ 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 withaF two lists of possible names.  The first list was intended to evoke theC feeling of "extension to VAX", while the second list was to suggestsG "not a VAX".  Unfortunately, none of the choices offered were any good;jI for example, "VAX 2000" was found on the first list while the second listV< 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 lE very much like an Arabic word with decidely unfortunate connotations.tF Eventually, AXP was selected; the architecture would be referred to as= "Alpha AXP" whereas products themselves would use just "AXP".   G Use of the AXP term has been phased out in favour of using Alpha.  For iG example, "OpenVMS AXP" is now officially refered to as "OpenVMS Alpha".u  < ------------------------------------------------------------A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?E  I Very few.  As of OpenVMS V6.1, the VAX and Alpha platforms are very closeeB 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 Alpha D       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.=;       IEEE float types are also available on OpenVMS Alpha.   C     - Data alignment is extremely important for best performance ond?       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 foraA       character values and those smaller than 32 bits.  CompilersiB       will naturally align variables where they can and will issue3       warnings if they detect unaligned data items.   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 somewhateL       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.   K     - The page size on Alpha systems is variable, but is at least 8K bytes.eE       This can have some effect on applications which use the $CRMPSC B       system service as well as on the display of available memoryF       pages.  The page size is available from $GETSYI(SYI$_PAGE_SIZE).  K There are also a number of manuals which discuss migration to OpenVMS AlphatK available on the documentation CD-ROM media, both in the main documentationi* 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 later :     - 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:  4     http://www.digital.com/alphaserver/products.html+     http://www.digital.com/alphaserver/vax/	  D   The following sites contain information on various retired VAX and   Alpha products:.  9     http://www.digital.com/alphaserver/archive/index.html @     http://www.digital.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:i  2 	ftp://ftp.digital.com/pub/Digital/Alpha/firmware/D         ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html  F The files are structured similiar to those on the firmware CD, and are? separated by CD release.  For example, the contents of the V3.7n firmware CD are located at:   7 	ftp://ftp.digital.com/pub/Digital/Alpha/firmware/v3.7/c  E The latest and greatest firmware (if released since the last firmwareo CD) is located at:  : 	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.txtu  ;                                           [Stephen Hoffman]e  A To check the firmware loaded on recent OpenVMS Alpha systems, usee the command:  0   $ write sys$output f$getsyi("console_version")0   $ write sys$output f$getsyi("palcode_version")   SDA> CLUE CONFIG7                                           [Clair Grant]P   Also see ALPHA14.o    < ------------------------------------------------------------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 -I after that, it will use the terminal.  Older Alpha workstations generallyF# can't be booted without a keyboard.   K The usual settings for the console serial terminal (or PC terminal emulatorD acting as a serial console are:D  >   9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).  K The AlphaStation and AlphaServer series use the PC DIN serial connector forDE the "COM1" and "COM2" serial lines, see MISC1 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:  1   http://www.openvms.digital.com/freeware/multia/)  > Instructions are included IN the kits.  READ THE INSTRUCTIONS.  E Some of the restrictions involved when running OpenVMS on the Multia f> system include (but may well not be limited to) the following:  A   o The PCMCIA support was completely removed, because the Intel -B     chip on the Multia was not compatable with the Cirrus chip on      the Alphabook.  @     This means, of course, that you will not see and cannot use !     any PCMCIA cards on a Multia.   B   o The Multia uses shared interrupts, and as a result, a special B     ZLXp-E series graphics device driver -- one that does not use A     interrupts -- is needed.  This driver is provided in the kit..      o The serial lines don't work.  ?   o If you have a Multia with a PCI slot, you can't use any PCIn"     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.)A  B   o If things don't work for you, don't expect to see any OpenVMS 6     updates, nor SRM console updates, nor any support.   F The Multia images are not included on the OpenVMS Freeware V4.0 CD-ROMD kit, the kit that was distributed with OpenVMS V7.2.  (These images . became available after Freeware V4.0 shipped.)  ; Other sources of information for OpenVMS on Multia include:   <   http://home.earthlink.net/~djesys/vms/hobbyist/multia.html>   http://home.earthlink.net/~djesys/vms/hobbyist/mltianot.html=   http://home.earthlink.net/~djesys/vms/hobbyist/support.htmlw2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman];                                         [David J. Dachtera]   > OpenVMS Alpha is not supported on the AlphaPC 164LX and 164SX,> and the OpenVMS CPU-specific routines and images necessary to 2 bootstrap on these systems do not presently exist.   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 tC OpenVMS are the AlphaServer DS10 server and the AlphaStation XP900 .B workstation.  Other companies sell Alpha-powered systems and AlphaA motherboards, some of which will run (and can be purchased with) nB OpenVMS -- see the OpenVMS Software Product Description (SPD) for E details on the supported systems and configurations.  There are also iC many used AlphaStation, AlphaServer, and DEC 3000 models available  ? which are quite suitable.  For more experienced OpenVMS system S@ managers, the (unsupported) Multia can bootstrap OpenVMS -- see  ALPHA8 for details.s  @ Depending on the OpenVMS version and configuration, the OpenVMS 3 Software Product Description (SPD) is available at:o  %   http://www.digital.com/info/SP2501/ %   http://www.digital.com/info/SP4187/a%   http://www.digital.com/info/SPHOME/   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.h 					[Stephen Hoffman]  < ------------------------------------------------------------< ALPHA10.  Where can I get more information on Alpha systems?  5 Compaq operates an AlphaServer information center at:   %   http://www.digital.com/alphaserver/t  > Alpha Technical information and documentation is available at:  ,   http://www.support.compaq.com/alpha-tools/)      documentation/current/chip-docs.htmle  1   ftp://ftp.compaq.com/pub/products/alphaCPUdocs/e  .   ftp://ftp.digital.com/pub/DEC/Alpha/systems/  *   http://ftp.digital.com/pub/Digital/info/.      semiconductor/literature/dsc-library.html  #   Platform product documentation:  o7     http://www.digital.com/info/lists/key-server_AL.HTMa<     http://www.digital.com/info/lists/key-workstation_AL.HTM    / Information on Multia hardware is available at:h  2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman]  = 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 OpenVMSc@ Alpha primary bootstrap image APB.EXE.  These flags control the & particular behaviour of the bootstrap:     >>> BOOT -FL root,flagso        bit      descriptionM9      ---   ----------------------------------------------E  -       0    CONV      Conversational bootstrape3       1    DEBUG     Load SYSTEM_DEBUG.EXE (XDELTA)iP       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 setc'       10   ISL       LAD/LAST bootstrapI1       11   PALCHECK    Disable PAL rev check haltaA       12   DEBUG_BOOT  Transfer to intermediate primary bootstrapc+       13   CRDFAIL       Mark CRD pages bad A       14   ALIGN_FAULTS  Report unaligned data traps in bootstrape@       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) 0       18   RSM         Boot is controlled by RSM5       19   FOREIGN     Boot involves a "foreign" disk   H   If you want to set the boot flags "permanently" use the SET BOOT_FLAGS   command, e.g.             >>> 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 e; within the SRM system console.  These environment variables ; control the particular behaviour of the console program andR? the system hardware, the particular console interface presentedhB 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:i  :   AUTO_ACTION ("BOOT", "HALT", "RESTART", any other value ;   assumed to be HALT),  BOOT_DEV, BOOTDEF_DEV, BOOTED_DEV, e8   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.     = OpenVMS Galaxy firmware can add console environment variablesuB 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...e  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.txtT  2 Tips for using the Multia files with the AXPpci33:  ?   o You have to use the Multia kit and follow the directions ing?     ALPHA8, but do *not* load the Multia SRM firmware into the  @     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,  ?     you need to find an ISA Ethernet card supported by OpenVMS.H  @   o When the AXPpci33 board bootstraps, it will dump some stuff A     like a crash dump, but it will continue and -- so far -- thisa)     hasn't caused any particular hassles.;  C   o The system shutdown and reboot procedures do not work properly.   A   o The serial console is reported to not work, though the serialeB     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 l?     with the PS/2 mouse and keyboard connectors and a VGA card cE     (one that will work under DECwindows) and you can run DECwindows       on the system. e8                                       [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, meaning G   only one set of firmware (SRM or AlphaBIOS) can be loaded in flash atuG   a time.  Getting back to the SRM firmware when AlphaBIOS (or ARC) is a'   loaded can be a little interesting...a  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.c  I   To shuffle the files, copy the target SRM firmware file (as200_v7_0.exeuK   is current) to a blank, initialized, FAT-format floppy under the filename    A:\FWUPDATE.EXE   G   From the AlphaBIOS Setup screen, select the Upgrade AlphaBIOS option.l5   Once the firmware update utility gets going, enter:M        Apu-> update srm-  0            Answer "y" to the "Are you ready...?"        Apu-> quite  K   You've reloaded the flash.  Now powercycle the box to finish the process.t     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 thel)   Microsoft Windows NT operating system.p  D   For the list of boxes officially supported by OpenVMS, please see 1   the OpenVMS Software Product Description (SPD).   I   If you are very lucky, sometimes a particular unsupported Alpha box or fH   motherboard will resemble a supported box sufficiently closely and canE   thus mimic that system and bootstrap.  (No such family resemblancessF   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?   G   The Alpha architecture is upward- and downward-compatible, and newer  E   instructions are emulated on older platforms, for those cases whereiB   the compiler is explicitly requested to generate the newer Alpha   instructions.n  F   In particular, OpenVMS Alpha V7.1 and later include the instruction C   emulation capabilities necessary for the execution of newer Alpha .   instructions on older Alpha microprocessors.  G   Alpha instructions are available in groups (or subsets).  Obviously, lC   there is the base instruction set that is available on all Alpha sE   microprocessors.   Then, the following are the current instruction mE   extension groups (or subsets) that are available on some of variousm   recent Alpha microprocessors:e       byte/word extension (BWX):-       LDBU, LDWU, SEXTB, SEXTW, STB, and STW.t  3     floating-point and square root extension (FIX): H       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG, SQRTS, and SQRTT.       count extension (CIX):       CTLZ, CTPOP, and  CTTZ.A        multi-media extension (MVI):F       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4, MINUB8, MINUW4, +       PERR, PKLB, PKWB, UNPKBL, and UNPKBW.   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 h4   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 AJ   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.g    cI   Typically /OPTIMIZE=TUNE=GENERIC is the appropriate choice for tuning, pC   and the /ARCHITECTURE selects the minimum target architecture foru,   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.   F   Please see the OpenVMS Ask The Wizard area for the source code of a H   (non-privileged) tool that looks at the instruction subsets available H   on the particular Alpha microprocessor that the tool is run on.  This H   tool demonstrates the use of the Alpha AMASK and IMPLVER instructions.  < ------------------------------------------------------------J ALPHA17.  What is the Accuracy of the Alpha Time of Year (BB_WATCH) Clock?  J   The specification for maximum clock drift in the Alpha hardware clock isL   50 ppm, that's less than +/-.000050 seconds of drift per second, less thanJ   +/-.000050 days of drift per day, or less than +/-.000050 years of driftJ   per year, etc.   (eg: An error of one second over a day-long interval is*   roughly 11ppm, or 1000000/(24*60*60).)    M   The software-maintained system time can drift more, primarily due to other bK   system activity.  Typical causes of drift include extensive high-IPL codeoK   (soft memory errors, heavy activity at device IPLs, etc) that are causing:7   the processing of the clock interrupts to be blocked.      Also see VAX8, TIME6.p  < ------------------------------------------------------------3 ALPHA18.  So how do I open up the DEC 3000 chassis?   @ After removing those two little screws, tilt the back end of the1 top shell upwards -- then you can remove the lid.o  :                                            [Felix Kreisel]  < ------------------------------------------------------------! ALPHA19.  What is byte swizzling?   F   "Swizzling" is the term used to describe the operation needed to do A   partial word IO on a pre-ev6 system.  It involved shifting the nD   offset into an address space by 5 (or 7 for one older system), andE   ORing this into the base address.  It then required the size of thet/   operation to be ORed into the low order bits.e  G   That is, because EV4 and EV5 did not bring bits 0 and 1 off the chip,iI   to do programmed IO for bytes/words, the information on the size/offset-E   of the transfer was encoded into the address data.  The data itself?G   then had to be shifted into the correct "byte lane" (i.e. it's actual    position within a longword).  F   EV56 (though not EV5) had byte/word operations, but OpenVMS did not D   directly support this for IO.  EV6 systems (with the exception of D   the AlphaServer GS60 and AlphaServer GS140 series, for reasons of G   platform compatability) all support a flat byte addressable IO space.s  G   If device driver uses CRAM or IOC$WRITE_IO/IOC$READ_IO, then OpenVMS lF   will do the right thing without changing the driver -- OpenVMS will "   swizzle and unswizzle as needed.  F   To use byte/word operations on MEMORY, you need to tell the compilerD   to use the EV56 or EV6 architecture (/ARCHITECTURE=EV56).  Memory B   operations did not swizzle, but the compiler would do long/quad G   access, and extract/insert bytes as needed.  Using /ARCHITECTURE=EV56sH   allows smaller more efficient byte IO logic to memory.  Beware: a few E   Alpha systems have EV56, but do not support byte/word to I/O space.   H   If the application is directly doing IO access across a range of AlphaI   systems (like the graphics servers), then the driver will need to know dK   how to do swizzling for old platforms, and byte access for new platforms.d9                                         [Fred Kleinsorge]d  < ------------------------------------------------------------? ALPHA20.  What commands are available in the Alpha SRM console?   F In addition to the normal BOOT commands and such (see ALPHA11 for someE details) and the normal contents of the console HELP text, operationsTG such as I/O redirection and floppy disk access are possible at the SRM r console prompt:n  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.dat     >>> show conf > conf.date%    >>> cat env.dat > fat:env.dat/dva0/'    >>> cat conf.dat > fat:conf.dat/dva0l  B 3. You may use the SRM "ls" to display the contents of the floppy.      >>> ls fat:env.dat/dva0    >>> ls fat:conf.dat/dva0   @ 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 thathG the particular Alpha system is supported by OpenVMS (see the SPD), thattG all core I/O components (graphics, disk controllers, etc) in the systemiD are supported by OpenVMS (see the SPD), and that you have an OpenVMSG distribution, that you have the necessary license keys (PAKs), and that)+ you have the necessary SRM firmware loaded.c  F A typical sequence used for switching over from the AlphaBIOS graphics# console to the SRM console follows:h  3   1. Press <F2> to get to the AlphaBIOS setup menu.   #   2. Pick the "CMOS Setup..." item.e  9   3. Press <F6> to get to the "Advanced CMOS Setup" menu.c  ?   4. Change the "Console Selection" to "OpenVMS Console (SRM)".t  ;   5. Press <F10>, <F10>, then <Enter> to save your changes.o     6. Power-cycle the system.  I Most Alpha systems support loading both the AlphaBIOS/ARC console and theiF 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 haveeG a "half-flash" system, you must load the SRM firmware from floppy, frompD a network download, or from a firmware CD-ROM.  Following the normalE AlphaBIOS or ARC firmware update sequence to the APU prompt, and thenlB explictly select the target console.  In other words, power up theE system to the AlphaBIOS or ARC console, use the supplementary options C to select the installation of new firmware (typically from CD-ROM),1? and then rather than using a sequence which updates the currento	 firmware:A       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 ddcu $     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 orn= 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 NTT   and power-cycle the system.   C For information on acquiring firmware, see ALPHA6.  For information)E on OpenVMS license PAKs (for hobbyist use) see VMS9.  For information  on the Multia, see ALPHA8.  C Information on enabling and using the failsafe firmware loader for sE various systems -- this tool is available only on some of the various F Alpha platforms -- is available in the hardware documentation for the G system.  This tool is used/needed when the firmware has been corrupted,O and cannot load new firmware.   < ------------------------------------------------------------8 VAX1.   Please explain the back panel of the MicroVAX II  J The MicroVAX-series console bulkhead was used with the KA630, KA650, KA655 processors.   B There are three controls on the console bulkhead of these systems:  *   Triangle-in-circle-paddle: halt enable. -     dot-in-circle: halt (<break>) is enabled,o-                    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 behaviour"     arrow: normal operation.      face: language inquiry mode.)     t-in-circle: infinite self-test loop.   4   Eight-position-rotary: console baud rate selection4     select the required baud rate; read at power-up.  eJ There are several different bulkheads involved, including one for the BA23E and BA123 enclosures, and one for the S-box (BA2xx) series enclosure.iL The console bulkheads typically used either the MMJ serial line connection, H or the MicroVAX DB9 (not the PC DB9 pinout), please see the descriptions> of these in section MISC1.  For available adapters, see MISC4.  M Also present on the console bulkhead is a self-test indicator: a single-digitmK LED display. This matches the final part of the countdown displayed on the nN console or workstation, and can be used by a service organization to determineM the nature of a processor problem.  The particular countdown sequence varies  M by processor type, consult the hardware or owner's manual for the processor, AG or contact the local hardware service organization for information the TM self-test sequence for a particular processor module. Note that self-tests 2,(M 1 and 0 are associated with the transfer of control from the console program r" to the (booting) operating system.9                                         [Stephen Hoffman]   < ------------------------------------------------------------< 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,sH 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"sF contains the sign and exponent (and for other than H, some of the mostK significant fraction bits).  Each successive higher-addressed word contains-N 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 (butmJ 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,,% infinity, denormalized or NaN values.o  M For all formats, the fraction is normalized and the radix point assumed to beyJ 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.t  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]   < ------------------------------------------------------------5 VAX3.   Where can I find more info about VAX systems?-  " Compaq runs a VAX "InfoCenter" at:  )   http://www.digital.com/alphaserver/vax/s  1 Jim Agnew maintains a MicroVAX/VAXstation FAQ at:r  3   http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmla  , James Lothian maintains a VAX-11/750 FAQ at:  3   http://www.dcs.napier.ac.uk/~oose5002/750faq.htmla  " The VAXstation 3100 Owner's Guide:  7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmls  ; A field guide to PDP-11 (and VAX) Q-bus and UNIBUS modules f can be found at:  8   http://metalab.unc.edu//pub/academic/computer-science/+     history/pdp-11/hardware/field-guide.txt   9 Various VAX historical information (also see VMS1) can be 	 found at:,  +   http://telnet.hu/hamster/vax/e_index.htmlU  < ------------------------------------------------------------? VAX4.   Where can I find information on NetBSD for VAX systems?o  / Gunnar Helliesen maintains a NetBSD VAX FAQ at:    http://vaxine.bitcon.no/  < ------------------------------------------------------------H VAX5.   What system disk size limit on the MicroVAX and VAXstation 3100?  M System disks larger than 1.073 gigabytes (GB) -- 1fffff hexidecimal blocks --SL 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.)f  M Various of the SCSI commands used by the boot drivers imbedded in the consolepI PROM on all members of the VAXstation 3100 series use "Group 0" commands, I which allow a 21 bit block number field, which allows access to the firstoJ 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.o  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 forfI field retrofits -- this PROM upgrade allows the use of the "Group 1" SCSIeN commands, and thus larger system disks.  There was no similar PROM upgrade for the VAXstation 3100 series.o  ( Systems that are affected by this limit:G   o VAXstation 3100 series, all members.  No PROM upgrade is available.rB   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 lB     versions prior to V6.4 are affected.  A PROM upgrade for these-     specific systems is (was once) available.h  	 Also see:b7   http://www.whiteice.com/~williamwebb/intro/DOC-i.html    Also see FILE5.e 						[Stephen Hoffman]   < ------------------------------------------------------------  VAX6.  replaced by TIME section.  < ------------------------------------------------------------) VAX7.  What are the VMB boot flag values?Z  ? The following flags are passed (via register R5) to the OpenVMSS> VAX primary bootstrap image VMB.EXE.  These flags control the & particular behaviour of the bootstrap:  > The exact syntax is console-specific, recent VAX consoles tend to use the following:      >>> BOOT/R5:flags-  @   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.                                     ?                                                                a@    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.                     d< ------------------------------------------------------------A VAX8.   What is the Accuracy of VAX the Time of Year (TOY) Clock?u  A   The VAX Time-Of-Year (TOY) clock (used to save the time over a sA   reboot or power failure) is specified as having an accuracy of  ;   .0025%.  This is a drift of roughly 65 seconds per month.f  C   The VAX Interval Time is used to keep the running time, and this .F   has a specified accuracy of .01%.  This is a drift of approximately    8.64 seconds per day.   E   Any high-IPL activity can interfere with the IPL 22 or IPL 24 (thisPD   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"eA 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 to @ 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 -- thato6 enables one of the serial lines as the system console.  $ Also see ALPHA1, DECW13, and MGMT22.  < ------------------------------------------------------------/ VAX11.  What are the VAX processor (CPU) codes?e      CPU:    Platform:    -----   ---------%    KA600 : VAX 4000-50 (aka VAXbrick)l.    KA610 : MicroVAX I, VAXstation I (aka KD32)    KA620 : rtVAX (VAXeln)i%    KA630 : MicroVAX II, VAXstation II-'    KA640 : MicroVAX 3300, MicroVAX 3400 F    KA650 : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX III6    KA655 : MicroVAX 3800, MicroVAX 3900, MicroVAX III+    KA660 : VAX 4000-200, VAX 4    KA670 : VAX 4000-300y    KA675 : VAX 4000-400     KA680 : VAX 4000-500e    KA681 : VAX 4000-500A    KA690 : VAX 4000-600e    KA691 : VAX 4000-605A    KA692 : VAX 4000-700A    KA693 : VAX 4000-605A    KA694 : VAX 4000-705A    KA730 : VAX-11/730e    KA750 : VAX-11/750m!    KA780 : VAX-11/780, VAX-11/782o    KA785 : VAX-11/785c    KA800 : VAXrtau    KA820 : VAX 8200, VAX 8300"    KA825 : VAX 8250, VAX 8350h    KA85  : VAX 8500s    KA86  : VAX 8600f    KA865 : VAX 8650h    KA88  : VAX 8800     KA62A : VAX 6000-200A    KA62B : VAX 6000-300     KA64A : VAX 6000-400n    KA65A : VAX 6000-500     KA66A : VAX 6000-600q    KA7AA : VAX 7000-600A    KA7AB : VAX 7000-700O    KA7AC : VAX 7000-800h  < ------------------------------------------------------------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:t      http://www.compaq.com/support/  : Various hardware and system documentation is available at:  1   http://www.digital.com/lists/QB_archive_HD.html-;   http://www.europe.digital.com/info/CUHOME/BACK_ISSUES.HTMc?   http://www.compaq.com/support/techpubs/user_reference_guides/d1   http://www.adenzel.demon.nl/vaxes/microvax3100/ 2   http://www.adenzel.demon.nl/vaxes/infoserver150/  < ------------------------------------------------------------E SUPP2.  Where can I get hardware self-maintenance support assistance?d  C The Compaq Assisted Services program is available to customers thatbH wish to maintain their own systems (self-maintenance), but that require F some assistance with acquiring hardware diagnostics, hardware manuals,# and with hardware swaps and spares:c  %   http://www.digital.com/info/DAHOME/h%   http://www.digital.com/DAS-Catalog/l  < ------------------------------------------------------------G SUPP3. Why does my system halt when I power-cycle the console terminal?A  <   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 variousnB   VAX systems -- including most VAXstation, MicroVAX, and VAX 4000A   series -- it is typically interpreted as a HALT.  Alpha systemslC   will also often process a BREAK in a similar fashion, halting ther	   system.s  @   There is no uniform or generally-available way to disable thisA   behaviour on every VAX or Alpha system.  On some systems, BREAKuA   processing can be disabled in favor of [CTRL/P], or [CTRL/P] ist%   the only way to halt the processor.e  C   The most common way to avoid these halts is to disable the serial A   line console or to simply not power-cycle the console terminal.-G   There is certain important system state information that is displayed C   only on the console, OpenVMS expects to always have access to thed   system console.P     Also see MGMT5.c  < ------------------------------------------------------------? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?a  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 othereD 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.,i& 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 beeH 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 the=K DEC 2000 (DECpc 150 AXP), an AlphaServer series, an AlphaStation series, or E more recent Alpha system, it will probably  work with a PC peripheral H 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 particularrN configuration, save for those specific configurations the device is explicitly
 supported in.w9                                         [Stephen Hoffman]r    K Software Integrators sells a video adapter card called Gemini P1 which will I drive many of the older Compaq (DIGITAL-logo) fixed-frequency monitors onc 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 frequency.C specifications to be used with the VAXstations.  It may work with ao> VAXstation 2000 series, but I have not tried that combination.<                                           [John E. Malmberg]  I The protocol definition for the old DIGITAL keyboard and mouse interfacessJ 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 ManualiF (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.u     Also see SUPP5  < ------------------------------------------------------------A SUPP5.  Which video monitor works with which graphics controller?s  K   To determine the answer to the "will this monitor work with this graphicssF   controller?" question, please first locate the resolution(s) and theI   frequencies that are possible/supported at both ends of the video cable H   (on the monitor and the graphics controller, in other words), and thenG   determine if there are any matching settings available.  If there arefL   multiple matches, you will need to determine which one is most appropriate   for your needs.a  M   You will also need to determine if the video monitor or graphics controllersL   requires the 3 BNC signaling with the synchronization signals on the greenM   wire, or the 5 BNC signalling common on many PCs, or other connections such G   as the DB15 video connector or USB connector used on various systems.   I   If there are no matches, you will likely need to change the hardware at (   one or both ends of the "video cable".  J   The refresh frequencies for many devices have been posted to comp.os.vmsG   and/or other newsgroups.  Search the archives for details.  Also see:s       http://www.repairfaq.org/a<     http://plop.phys.cwru.edu/repairfaq/REPAIR/F_monfaq.html"     http://www.mirage-mmc.com/faq/H     http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html     Also see SUPP4.N  < ------------------------------------------------------------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 informationi/ on SCSI, device jumpers, etc., is available at:s     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 wheniL    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 beingOL    initialized.  Pressing ^F2 several times or unplugging and replugging theK    keyboard frequently fix this problem.  There is a patch available to fixsJ    this problem [contact the CSC for information - a CSCPAT number will be'    included here when available. - Ed.]   L c) A key that was working spontaneously stops working correctly. This may beN    either (a) or (b) or it may be bad firmware.  Ensure that you have the mostI    recent firmware installed on your CPU.  An old version of the DEC 3000 4    firmware had a bug that could cause this symptom.9                                         [Fred Kleinsorge]s  < ------------------------------------------------------------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 besF 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.K9                                         [Fred Kleinsorge]d1                                         [inazu_k]   < ------------------------------------------------------------< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?  3   Both of these controllers are Ultra2 low-voltage  &   differential (LVD) SCSI controllers.  < ------------------------------------------------------------- WIRES1. Looking for connector wiring pinouts?    DECconnect DEC-423 MMJ pinout:     1: Data Terminal Ready (DTR)   2: Transmit (TXD)    3: Transmit Ground (TXD-)    4: Receive Ground (RXD-)   5: Receive (RXD)   6: Data Set Ready (DSR)       +------------------+     | 1  2  3  4  5  6 |     +------------+    ++r                 +____+    / The PC-compatible DB9 connector pinout follows:t     1: Data Carrier Detect (DCD)   2: Received Data   3: Transmit Data   4: Data Terminal Ready (DTR)   5: Ground    6: Data Set Ready (DSR)a   7: Request To Send (RTS)   8: Clear To Send
   9: floatingt  C The MicroVAX DB9 console connector pinout predates the PC-style DB9 D pinout, and uses a then-common (older) standard pinout, and uses the# following EIA-232-standard signals:t     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.     = The BC16E-nn (where -nn indicates the cable length) cable key < impliicitly "flips over" (crosses-over) the signal wires, so1 all DECconnect MMJ connectors are wired the same.   
            // :            ----                                       ----:            |  |---------------------------------------|  |:            ----                                       ----:                                                         \\  0 The BC16-E-nn cross-over wiring looks like this:  ;             Terminal                                   Host :             MMJ                                        MMJ  =          DTR 1 --->-------------->----------------->--- 6 DSR =          TXD 2 --->-------------->----------------->--- 5 RXD 9              3 ---------------------------------------- 4 9              4 ---------------------------------------- 3 =          RXD 5 ---<--------------<-----------------<--- 2 TXDe=          DSR 6 ---<--------------<-----------------<--- 1 DTRg    	 Also see:   M  http://www.partner.compaq.com:9003/public/cheat_sheets/cables/padapters.htmlP%  http://www.airborn.com.au/rs232.html (  For adapters and connectors, see MISC4.  9                                         [Stephen Hoffman] 7                                         [Mike Thompson]h  < ------------------------------------------------------------: WIRES2. What connectors and wiring adapters are available?    J The H8571-B converts the (non-2000-series) MicroVAX DB9 to MMJ DECconnect.G The MicroVAX 2000 and VAXstation 2000 requires a BCC08 cable (which has 7 the 8-9 short) and the H8571-D for use with DECconnect.   G More recent Compaq (Compaq or DIGITAL logo) systems will use either the I DECconnect MMJ wiring or (on all recent system designs) the PC-compatiblel DB9 pinout.    DECconnect MMJ adapters:  3     Part:      Converts BC16E MMJ male to fit into:g  ,     H8575-A    EIA232 25 pin female (common)6     H8575-B    EIA232 9 pin male (MicroVAX II console)/     H8571-D    EIA232 25 pin male (modem-wired) 0     H8571-J    PC/AT 9 pin male (PC serial port)-     H8572-0    0BC16E MMJ male (MMJ extender)   6     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 asP' descriptions of the above-listed parts.   J The H8571-A and H8575-A are MMJ to DB25 (female) and are wired as follows:  	 Also see:uN  http://www.partner.digital.com:9003/public/cheat_sheets/cables/padapters.html9  http://www.networks.digital.com.au/dr/npgc/opdec-mn.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.t  " For wiring and pinouts, see MISC4.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.e  B In ASCII, XON is the [CTRL/Q] character, and XOFF is the [CTRL/S].  F XON/XOFF flow control is typically associated with asynchronous serialG line communications.  XON/XOFF is an in-band flow control, meaning that0+ the flow control is mixed in with the data.4  I CTS/RTS is another type of flow control, and is sometimes called hardwarerG flow control.  Out-of-band means that seperate lines/pins from the dataa3 lines (pins) are used to carry the CTS/RTS signals.p  G Both kinds of flow control are triggered when a threshold is reached in J the incoming buffer.  The flow control is suppose to reach the transmitterG in time to have it stop transmitting before the receiver buffer is fullpE and data is lost.  Later, after a sufficient amount of the receiver'soE buffer is freed up, the resume flow control signal is sent to get the  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,sE and drivers) *must not* be configured for XON/XOFF flow control.  ThenD incidence of these (unexpected) in-band characters will corrupt dataG packets.  Further, the serial line device drivers might normally remove-F the XON and XOFF characters from the stream for terminal applications,E but DECnet configures the driver to pass *all* characters through andeF 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 compression G is happening, it must reproduce the source stream exactly.  No addition > or elimination of null characters, and full data transparency.  I An Ethernet network is rather different than an asynchronous serial line. E Ethernet specifies the control of data flow on a shared segment using0B CSMA/CD (Carrier Sense Multiple Access, with Collision Detect)  AnF Ethernet station that is ready to transmit listens for a clear channelK (Carrier Sense).  When the channel is clear, the station begins to transmit:J by asserting a carrier and encoding the packet appropriately.  The stationG concurrently listens to its own signal, to permit the station to detect7G if another station began to transmit at the same time -- this is called8J 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 beginning-G to establish a transmit window size -- and a transmitter will only send G that much data before stopping and waiting for an acknowledgement.  ThedG acknowledgement is only sent when the receiver has confirmed the packet/D is valid.  (A well-configured DECnet generally avoids triggering any1 underlying (out-of-band) flow control mechanism.)Q=                                                [David Rabahy]/   [End of Part 5/5]t    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Fri, 18 Aug 2000 09:46:17 -0600 1 From: Glen Martin <GLENMARK@utxvms.cc.utexas.edu>s Subject: Re: OpenVMS Web Forum4 Message-ID: <399D05E9.28E18198@utxvms.cc.utexas.edu>   Mark Daniel wrote: >  > Glen Martin wrote: > E > > More as an experiment than anything else, I've set up a web-based,= > > discussion board for VMS-related topics. It is located attG > > http://techwind.com/cgi-bin/forumdisplay.cgi?action=topics&number=2l> > > (or go to http://techwind.com and follow the Forum links). > B > FWIW, dispersing the already thin VMS resources further might beH > counter-productive, comp.os.vms and relateds have done a good job overC > the years.  These with modern GUI news browsers and an occasionallB > archive with link and search capabilities (even Deja at a pinch)B > provides a reasonably workable and consolidated resource for VMS
 > queries.  H It is certainly not my desire to disperse resources, but simply to widenH available options by providing a less crowded venue. I see proliferationC of resources as a good thing. But, more than anything else, the new0@ Forum is an experiment with webboard software. Hoff mentions the? DECUS/DECnotes web gateway in another reply. A start, but a bittA cumbersome, especially for getting posting privileges (unless oneeD already has access to the DECnotes server). Neither my forum nor theH DECUS webboard really fill the void which I lamented in earlier postingsE about Sun's BigAdmin site. Here's hoping that the rumors mentioned byo Terry come to fruition...i  oH > I would even like to see the OpenVMS Wizard stealing his own thunder aH > little there, by making posts of Wizard-queries (with replies Hoff :^)E > as he or his Associate Wizards answer them, to the comp.os.vms newsc > group.  G Ah, I see that my thinly-veiled plan to reveal the Wizard's identity is- working. Bwaaa-haaa-haaa!   ;)   Glen   ------------------------------  % Date: Fri, 18 Aug 2000 11:51:54 +0200k# From: bz <bernd.zebedin@arcs.ac.at> ) Subject: Portable GUIs (VMS+Windows-NT) ?c* Message-ID: <399D073A.D05B0FB2@arcs.ac.at>  F I am looking for a mature Tool for development of cross-platform GUIs,H that can be run without major modifications both under OpenVMS and under Windows-NT.iG I have tested the VMS-port of Qt, but it seems to be faulty. Has anyonecD experience with porting Java-GUI-applications to VMS or with the ISAC Dialog Manager  or with any other multi-platform toolkit supportingr OpenVMS?   Grateful for any advice, bz.   ------------------------------  % Date: Fri, 18 Aug 2000 10:07:17 -0400e0 From: Jim Jennis <jjennis@discovery.fuentez.com>) Subject: Portable GUIs (VMS+Windows-NT) ?oD Message-ID: <3.0.5.32.20000818100717.009ef920@discovery.fuentez.com>   Hi VMS Colleagues,  : The following question was posted to Info-VAX yesterday...H >>I am looking for a mature Tool for development of cross-platform GUIs,J >>that can be run without major modifications both under OpenVMS and under
 >>Windows-NT. I >>I have tested the VMS-port of Qt, but it seems to be faulty. Has anyone=F >>experience with porting Java-GUI-applications to VMS or with the ISAE >>Dialog Manager  or with any other multi-platform toolkit supportingp
 >>OpenVMS? >> >>Grateful for any advice, bz.  J I faced this problem in a major integration effort with VMS in my previousG job (and also with our current customers) and found the availability of-G good mature tools for VMS to be very lacking. Nevertheless I did find anI very solid solution, and it MAY be of interest to others on the list so Ii/ decided to post the solution we have used here.u  H For cross platform VMS application development and integration, we use a# product from WRQ called Verastream.   ' http://www.wrq.com/products/verastream/n  = It is a very powerful, mature object oriented cross-platform,mB cross-database gui/application development tool kit. Runs on 25-30H different OS's (including OVMS and even OS/400) supports 25-30 differentF databases and about a dozen different inter-application communications
 protocols.  D It generates platform independent code that is REALLY write once runE anywhere (unlike Java which is usually "write once test everywhere").n  4 We use it on OVMS, Linux, Solaris, HP-UX, NT, 95/98.  I You can generate apps with Motif, Windows, Character based, WEB interface F and have a single source application that runs on any platform withoutA recompilation or source code changes. IMHO it is a great product.A  E You can write an application on VMS and run it on Linux, NT, Unix, oro vice-versa.V  J If anyone would like additional information, feel free to write me off the list.l   Regards,   Jim  M    8 --------------------------------------------------------7 FSC - Building Better Information Technology Solutions- 7       from the Production Floor to the Customer's Door.-8 --------------------------------------------------------5 Jim Jennis, Technical Director for Commercial Systemsd Fuentez Systems Concepts, Inc. 1 Discovery Place, Suite 2 Martinsburg, WV. 25401 USAe  # Phone: +001 (304) 263-0163 ext. 235o Fax:   +001 (304) 263-0702% Email: jjennis@discovery.fuentez.com s        jhjennis@shentel.neth& WEB: http://www.discovery.fuentez.com/   ------------------------------  % Date: Fri, 18 Aug 2000 11:11:01 -0400a2 From: "Jim Jennis" <jjennis@discovery.fuentez.com>- Subject: Re: Portable GUIs (VMS+Windows-NT) ?e/ Message-ID: <spqk458487v104@corp.supernews.com>e  0 "bz" <bernd.zebedin@arcs.ac.at> wrote in message$ news:399D073A.D05B0FB2@arcs.ac.at...H > I am looking for a mature Tool for development of cross-platform GUIs,J > that can be run without major modifications both under OpenVMS and under
 > Windows-NT.tI > I have tested the VMS-port of Qt, but it seems to be faulty. Has anyonenF > experience with porting Java-GUI-applications to VMS or with the ISAE > Dialog Manager  or with any other multi-platform toolkit supporting.
 > OpenVMS? >r > Grateful for any advice, bz. Hi VMS Colleagues,  J I faced this problem in a major integration effort with VMS in my previousL job (and also with our current customers) and found the availability of goodG mature tools for VMS to be very lacking. Nevertheless I did find a verysL solid solution, and it MAY be of interest to others on the list so I decided' to post the solution we have used here.a  H For cross platform VMS application development and integration, we use a# product from WRQ called Verastream.e  ' http://www.wrq.com/products/verastream/u  L It is a very powerful, mature object oriented cross-platform, cross-databaseB gui/application development tool kit. Runs on 25-30 different OS'sG (including OVMS and even OS/400) supports 25-30 different databases andfC about a dozen different inter-application communications protocols.t  D It generates platform independent code that is REALLY write once runE anywhere (unlike Java which is usually "write once test everywhere").h  4 We use it on OVMS, Linux, Solaris, HP-UX, NT, 95/98.  I You can generate apps with Motif, Windows, Character based, WEB interfacesF and have a single source application that runs on any platform withoutA recompilation or source code changes. IMHO it is a great product.T  E You can write an application on VMS and run it on Linux, NT, Unix, ori vice-versa.i  J If anyone would like additional information, feel free to write me off the list.    Regards,   Jim    ------------------------------  % Date: Fri, 18 Aug 2000 11:25:56 -0400C4 From: "Bochnik, William J" <BochnikWJ@bernstein.com>- Subject: RE: Portable GUIs (VMS+Windows-NT) ?aJ Message-ID: <2B37459189B0D211BE710000F8EF9D8505668279@nts0147.beehive.com>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C00928.B72D1220e Content-Type: text/plain;  	charset="iso-8859-1"   K It's not the best, but I think that TK for Perl is multi platform, and Perl- runs on a LOT of platforms.L   -----Original Message-----7 From: Jim Jennis [mailto:jjennis@DISCOVERY.FUENTEZ.COM]t Sent: August 18, 2000 10:07 AM To: Info-VAX@Mvb.Saic.Coma) Subject: Portable GUIs (VMS+Windows-NT) ?t     Hi VMS Colleagues,  : The following question was posted to Info-VAX yesterday...H >>I am looking for a mature Tool for development of cross-platform GUIs,J >>that can be run without major modifications both under OpenVMS and under
 >>Windows-NT.nI >>I have tested the VMS-port of Qt, but it seems to be faulty. Has anyonecF >>experience with porting Java-GUI-applications to VMS or with the ISAE >>Dialog Manager  or with any other multi-platform toolkit supportinge
 >>OpenVMS? >> >>Grateful for any advice, bz.  J I faced this problem in a major integration effort with VMS in my previousG job (and also with our current customers) and found the availability ofeG good mature tools for VMS to be very lacking. Nevertheless I did find aeI very solid solution, and it MAY be of interest to others on the list so I / decided to post the solution we have used here.o  H For cross platform VMS application development and integration, we use a# product from WRQ called Verastream.e  ' http://www.wrq.com/products/verastream/g  = It is a very powerful, mature object oriented cross-platform,wB cross-database gui/application development tool kit. Runs on 25-30H different OS's (including OVMS and even OS/400) supports 25-30 differentF databases and about a dozen different inter-application communications
 protocols.  D It generates platform independent code that is REALLY write once runE anywhere (unlike Java which is usually "write once test everywhere").   4 We use it on OVMS, Linux, Solaris, HP-UX, NT, 95/98.  I You can generate apps with Motif, Windows, Character based, WEB interfacetF and have a single source application that runs on any platform withoutA recompilation or source code changes. IMHO it is a great product.   E You can write an application on VMS and run it on Linux, NT, Unix, ord vice-versa.o  J If anyone would like additional information, feel free to write me off the list.1   Regards,   Jim  0    8 --------------------------------------------------------7 FSC - Building Better Information Technology Solutions-a7       from the Production Floor to the Customer's Door.e8 --------------------------------------------------------5 Jim Jennis, Technical Director for Commercial Systemsi Fuentez Systems Concepts, Inc. 1 Discovery Place, Suite 2 Martinsburg, WV. 25401 USAt  # Phone: +001 (304) 263-0163 ext. 235o Fax:   +001 (304) 263-0702% Email: jjennis@discovery.fuentez.com o        jhjennis@shentel.net & WEB: http://www.discovery.fuentez.com/    ' ------_=_NextPart_001_01C00928.B72D12200 Content-Type: text/html; 	charset="iso-8859-1"c  1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">w <HTML> <HEAD>H <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">H <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2651.65">3 <TITLE>RE: Portable GUIs (VMS+Windows-NT) ?</TITLE>r </HEAD>o <BODY>  ~ <P><FONT SIZE=2>It's not the best, but I think that TK for Perl is multi platform, and Perl runs on a LOT of platforms.</FONT> </P>  1 <P><FONT SIZE=2>-----Original Message-----</FONT>o <BR><FONT SIZE=2>From: Jim Jennis [<A HREF="mailto:jjennis@DISCOVERY.FUENTEZ.COM">mailto:jjennis@DISCOVERY.FUENTEZ.COM</A>]</FONT>6 <BR><FONT SIZE=2>Sent: August 18, 2000 10:07 AM</FONT>1 <BR><FONT SIZE=2>To: Info-VAX@Mvb.Saic.Com</FONT> A <BR><FONT SIZE=2>Subject: Portable GUIs (VMS+Windows-NT) ?</FONT>v </P> <BR>  ) <P><FONT SIZE=2>Hi VMS Colleagues,</FONT>i </P>  Q <P><FONT SIZE=2>The following question was posted to Info-VAX yesterday...</FONT> f <BR><FONT SIZE=2>&gt;&gt;I am looking for a mature Tool for development of cross-platform GUIs,</FONT>h <BR><FONT SIZE=2>&gt;&gt;that can be run without major modifications both under OpenVMS and under</FONT>+ <BR><FONT SIZE=2>&gt;&gt;Windows-NT.</FONT> g <BR><FONT SIZE=2>&gt;&gt;I have tested the VMS-port of Qt, but it seems to be faulty. Has anyone</FONT>fd <BR><FONT SIZE=2>&gt;&gt;experience with porting Java-GUI-applications to VMS or with the ISA</FONT>h <BR><FONT SIZE=2>&gt;&gt;Dialog Manager&nbsp; or with any other multi-platform toolkit supporting</FONT>( <BR><FONT SIZE=2>&gt;&gt;OpenVMS?</FONT>  <BR><FONT SIZE=2>&gt;&gt;</FONT>< <BR><FONT SIZE=2>&gt;&gt;Grateful for any advice, bz.</FONT> </P>  a <P><FONT SIZE=2>I faced this problem in a major integration effort with VMS in my previous</FONT>r_ <BR><FONT SIZE=2>job (and also with our current customers) and found the availability of</FONT>s_ <BR><FONT SIZE=2>good mature tools for VMS to be very lacking. Nevertheless I did find a</FONT>ea <BR><FONT SIZE=2>very solid solution, and it MAY be of interest to others on the list so I</FONT>eG <BR><FONT SIZE=2>decided to post the solution we have used here.</FONT>- </P>  _ <P><FONT SIZE=2>For cross platform VMS application development and integration, we use a</FONT>s; <BR><FONT SIZE=2>product from WRQ called Verastream.</FONT>- </P>   <P><FONT SIZE=2><A HREF="http://www.wrq.com/products/verastream/" TARGET="_blank">http://www.wrq.com/products/verastream/</A></FONT> </P>  T <P><FONT SIZE=2>It is a very powerful, mature object oriented cross-platform,</FONT>Z <BR><FONT SIZE=2>cross-database gui/application development tool kit. Runs on 25-30</FONT>` <BR><FONT SIZE=2>different OS's (including OVMS and even OS/400) supports 25-30 different</FONT>^ <BR><FONT SIZE=2>databases and about a dozen different inter-application communications</FONT>" <BR><FONT SIZE=2>protocols.</FONT> </P>  [ <P><FONT SIZE=2>It generates platform independent code that is REALLY write once run</FONT>lg <BR><FONT SIZE=2>anywhere (unlike Java which is usually &quot;write once test everywhere&quot;).</FONT>a </P>  K <P><FONT SIZE=2>We use it on OVMS, Linux, Solaris, HP-UX, NT, 95/98.</FONT>t </P>  ` <P><FONT SIZE=2>You can generate apps with Motif, Windows, Character based, WEB interface</FONT>^ <BR><FONT SIZE=2>and have a single source application that runs on any platform without</FONT>Y <BR><FONT SIZE=2>recompilation or source code changes. IMHO it is a great product.</FONT>r </P>  \ <P><FONT SIZE=2>You can write an application on VMS and run it on Linux, NT, Unix, or</FONT># <BR><FONT SIZE=2>vice-versa.</FONT>  </P>  a <P><FONT SIZE=2>If anyone would like additional information, feel free to write me off the</FONT>e <BR><FONT SIZE=2>list.</FONT>  </P>   <P><FONT SIZE=2>Regards,</FONT>  </P>  ! <P><FONT SIZE=2>Jim&nbsp; </FONT>t </P> <BR>  O <P><FONT SIZE=2>--------------------------------------------------------</FONT>eO <BR><FONT SIZE=2>FSC - Building Better Information Technology Solutions-</FONT>ah <BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from the Production Floor to the Customer's Door.</FONT>P <BR><FONT SIZE=2>--------------------------------------------------------</FONT>M <BR><FONT SIZE=2>Jim Jennis, Technical Director for Commercial Systems</FONT>A6 <BR><FONT SIZE=2>Fuentez Systems Concepts, Inc.</FONT>2 <BR><FONT SIZE=2>1 Discovery Place, Suite 2</FONT>. <BR><FONT SIZE=2>Martinsburg, WV. 25401</FONT> <BR><FONT SIZE=2>USA</FONT>i </P>  : <P><FONT SIZE=2>Phone: +001 (304) 263-0163 ext. 235</FONT>< <BR><FONT SIZE=2>Fax:&nbsp;&nbsp; +001 (304) 263-0702</FONT>= <BR><FONT SIZE=2>Email: jjennis@discovery.fuentez.com </FONT>tQ <BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jhjennis@shentel.net</FONT>n~ <BR><FONT SIZE=2>WEB: <A HREF="http://www.discovery.fuentez.com/" TARGET="_blank">http://www.discovery.fuentez.com/</A></FONT> </P>   </BODY>  </HTML>1) ------_=_NextPart_001_01C00928.B72D1220--<   ------------------------------   Date: 18 Aug 2000 10:25:03 GMT3 From: gartmann@immunbio.mpg.de (Christoph Gartmann)6* Subject: Re: Sony MO on VAXstation 4000/600 Message-ID: <8nj2tv$rr5$1@n.ruf.uni-freiburg.de>  h In article <8nhbme$rb0$1@slb7.atl.mindspring.net>, "Ray McClellan" <raymcclellan@mindspring.com> writes:J >I've just acquired a VAXstation 4000/60, primarily to learn VMS.  It cameL >with an installed copy of 7.1, but I would like to add additional drives soJ >I could maintain older versions of VMS if possible.  It has a 2.88 floppyJ >but no CD.  I am trying to get a 5.25" MO to talk to it with little luck.L >Just setting the device number and plugging it in gets the drive recognizedH >but trying to INITIALIZE or MOUNT a disk gets a "device offline" error.M >Trying to boot the device just for fun shows that the VAX goes out and talks B >to the drive, so I suspect the problem is in VMS setup somewhere. >  >$ sho dev d > A >Device                      Device           Error        Volumek >Free  Trans MntA > Name                       Status           Count         LabelX >Blocks Count CntP4 >DAD0:                       Online                0M >MRITS$DKA100:     Mounted            0      OPENVMS071     1021632   295   1-K >MRITS$DKA500:     Mounted alloc    0      TEST288               2735     1o >1) >MRITS$DKA600:     Online              11n >$) >$ mount /override=identification dka600:a# >%MOUNT-F-MEDOFL, medium is offlineX >  >$ sho dev dka600:/fuR >)K >Disk MRITS$DKA600:, device type SONY SMO-C501-00, is online, file-oriented 1 >    device, shareable, error logging is enabled.  > L >    Error count                   14                   Operations completed >24t? >    Owner process                 ""                 Owner UIC 	 >[RAYMCC]m5 >    Owner process ID        00000000        Dev ProtR >S:RWPL,O:RWPL,G:R,WJ >    Reference count                0                  Default buffer size >512 >n: >$   (Error count shows # of unsuccessful access attempts) >(I >The device is a 512 byte/ sector disk.  It came off of a PDP system with L >RSX-11.  The MO disk we are trying to read was written on another VAX 4000. >T7 >Of the many things I don't understand, here are a few:e >eL >1. This is an embedded SCSI controller, but are there any commands to setupL >for the specific device ie. WRITE VERIFY, DISCONNECT ON_OFF, SYNC MODE etc,* >ala other DEC SCSI controllers I've seen?   Not that I am aware of.i  L >2. Is there something I need to do in INSTALL?  Install HELP so far hasn't.   No, I don't think so.   H >3. Is it possible that this drive is just incompatible with the system?  J Yes, it is. But I would first check the dip-switches, jumpers and the likeG on the MO-drive. It is often possible to get drives to work with VMS by L modifying the drive configuration. As long as the drive has a 512 byte block structure there is hope.   Regards,    Christoph Gartmann   H -----------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +------------ http://www.immunbio.mpg.de/english/menue.html -----------+   ------------------------------  % Date: Fri, 18 Aug 2000 17:43:55 +0200p+ From: Arne Bergseth <Arne.Bergseth@dnv.com>h* Subject: Re: Sony MO on VAXstation 4000/60' Message-ID: <399D59BB.43F50060@dnv.com>    Hi,e  C Avoid using SCSI id 6 for any disk on your VAXstation 4000/60 sincehK that is in conflict with the SCSI id of the controller, and is the probablet# reason for all your strange errors.v  I When the machine is in console, mode before booting the operating system,DA you may get some information about the hardware configuration by:c >>> SHOW CONFIG  >>> SHOW DEVICEd  
 With regards,u
 Arne Bergsethe   Ray McClellan wrote:  K > I've just acquired a VAXstation 4000/60, primarily to learn VMS.  It came M > with an installed copy of 7.1, but I would like to add additional drives sotK > I could maintain older versions of VMS if possible.  It has a 2.88 floppy K > but no CD.  I am trying to get a 5.25" MO to talk to it with little luck.iM > Just setting the device number and plugging it in gets the drive recognized-I > but trying to INITIALIZE or MOUNT a disk gets a "device offline" error. N > Trying to boot the device just for fun shows that the VAX goes out and talksC > to the drive, so I suspect the problem is in VMS setup somewhere.e >B
 > $ sho dev dC >oB > Device                      Device           Error        Volume > Free  Trans Mnt B >  Name                       Status           Count         Label > Blocks Count Cnt5 > DAD0:                       Online                0hN > MRITS$DKA100:     Mounted            0      OPENVMS071     1021632   295   1L > MRITS$DKA500:     Mounted alloc    0      TEST288               2735     1 > 1o* > MRITS$DKA600:     Online              11 > $v* > $ mount /override=identification dka600:$ > %MOUNT-F-MEDOFL, medium is offline >  > $ sho dev dka600:/fu >fL > Disk MRITS$DKA600:, device type SONY SMO-C501-00, is online, file-oriented2 >     device, shareable, error logging is enabled. >3M >     Error count                   14                   Operations completedn > 24@ >     Owner process                 ""                 Owner UIC
 > [RAYMCC]6 >     Owner process ID        00000000        Dev Prot > S:RWPL,O:RWPL,G:R,WiK >     Reference count                0                  Default buffer sizel > 512e >n; > $   (Error count shows # of unsuccessful access attempts)a >iJ > The device is a 512 byte/ sector disk.  It came off of a PDP system withM > RSX-11.  The MO disk we are trying to read was written on another VAX 4000.p > 8 > Of the many things I don't understand, here are a few: >rM > 1. This is an embedded SCSI controller, but are there any commands to setupsM > for the specific device ie. WRITE VERIFY, DISCONNECT ON_OFF, SYNC MODE etc,p+ > ala other DEC SCSI controllers I've seen?tM > 2. Is there something I need to do in INSTALL?  Install HELP so far hasn't.iI > 3. Is it possible that this drive is just incompatible with the system?V >sD > I've looked through the FAQ's and many of the SCSI subjects in theN > newsgroup, but I think that I'm just missing something obvious.  Any info orF > points in the right direction would be greatly appreciated.  Thanks. >n > Ray McClellan    ------------------------------  % Date: Fri, 18 Aug 2000 11:58:13 -0400l2 From: rdeininger@mindspring.com (Robert Deininger)* Subject: Re: Sony MO on VAXstation 4000/60L Message-ID: <rdeininger-1808001158130001@user-2iveb26.dialup.mindspring.com>  T In article <399D59BB.43F50060@dnv.com>, Arne Bergseth <Arne.Bergseth@dnv.com> wrote:    E > Avoid using SCSI id 6 for any disk on your VAXstation 4000/60 sincecM > that is in conflict with the SCSI id of the controller, and is the probabler% > reason for all your strange errors.i  I But don't forget that there is a console command to change the id of the r SCSI controller.   -- s Robert Deininger rdeininger@mindspring.comt   ------------------------------  % Date: Fri, 18 Aug 2000 11:58:32 -0400M# From: Jim Agnew <agnew@hsc.vcu.edu>)* Subject: Re: Sony MO on VAXstation 4000/60+ Message-ID: <399D5D28.50538F75@hsc.vcu.edu>n  p one can configure the scsi id of the controller, so you can have 7 devices instead of 6.  adds one more disk!!!!  9 j.  i forgot exactly what the command was, but it may be n   SET SCSIA 7 andt   SET SCSIB 7  for the b bus...i   Arne Bergseth wrote: >  > Hi,m > E > Avoid using SCSI id 6 for any disk on your VAXstation 4000/60 sincenM > that is in conflict with the SCSI id of the controller, and is the probableh% > reason for all your strange errors.w > K > When the machine is in console, mode before booting the operating system,nC > you may get some information about the hardware configuration by:n > >>> SHOW CONFIGo > >>> SHOW DEVICE: >  > With regards,e > Arne Bergsethe >  > Ray McClellan wrote: > M > > I've just acquired a VAXstation 4000/60, primarily to learn VMS.  It came O > > with an installed copy of 7.1, but I would like to add additional drives soeM > > I could maintain older versions of VMS if possible.  It has a 2.88 floppy M > > but no CD.  I am trying to get a 5.25" MO to talk to it with little luck.)O > > Just setting the device number and plugging it in gets the drive recognized K > > but trying to INITIALIZE or MOUNT a disk gets a "device offline" error.lP > > Trying to boot the device just for fun shows that the VAX goes out and talksE > > to the drive, so I suspect the problem is in VMS setup somewhere.a > >r > > $ sho dev d: > > D > > Device                      Device           Error        Volume > > Free  Trans Mnt D > >  Name                       Status           Count         Label > > Blocks Count Cnt7 > > DAD0:                       Online                0 P > > MRITS$DKA100:     Mounted            0      OPENVMS071     1021632   295   1N > > MRITS$DKA500:     Mounted alloc    0      TEST288               2735     1 > > 1 , > > MRITS$DKA600:     Online              11 > > $M, > > $ mount /override=identification dka600:& > > %MOUNT-F-MEDOFL, medium is offline > >t > > $ sho dev dka600:/fu > >aN > > Disk MRITS$DKA600:, device type SONY SMO-C501-00, is online, file-oriented4 > >     device, shareable, error logging is enabled. > >eO > >     Error count                   14                   Operations completedi > > 24B > >     Owner process                 ""                 Owner UIC > > [RAYMCC]8 > >     Owner process ID        00000000        Dev Prot > > S:RWPL,O:RWPL,G:R,WwM > >     Reference count                0                  Default buffer sizer > > 512o > > = > > $   (Error count shows # of unsuccessful access attempts)- > >iL > > The device is a 512 byte/ sector disk.  It came off of a PDP system withO > > RSX-11.  The MO disk we are trying to read was written on another VAX 4000.t > >r: > > Of the many things I don't understand, here are a few: > >wO > > 1. This is an embedded SCSI controller, but are there any commands to setupnO > > for the specific device ie. WRITE VERIFY, DISCONNECT ON_OFF, SYNC MODE etc,d- > > ala other DEC SCSI controllers I've seen?aO > > 2. Is there something I need to do in INSTALL?  Install HELP so far hasn't.uK > > 3. Is it possible that this drive is just incompatible with the system?n > >MF > > I've looked through the FAQ's and many of the SCSI subjects in theP > > newsgroup, but I think that I'm just missing something obvious.  Any info orH > > points in the right direction would be greatly appreciated.  Thanks. > >i > > Ray McClellano   ------------------------------  # Date: Fri, 18 Aug 2000 17:28:23 GMT') From: chbarr@one.net (Charles Barilleaux)-/ Subject: Toshiba CD-ROM and VMS Hobbiest CD-ROMe, Message-ID: <399d71db.23652009@news.one.net>   Hi!s  M I am trying to get a VMS system up with an Alpha system I rescued. I'm trying3I to get a CD-ROM for it, and, so far, have come up with mostly things thatyM don't work. I did, however, find a Toshiba XM-4101B. My understanding is that.I this CD-ROM shipped with some AlphaServer models. Does anyone know if the;4 OpenVMS hobbiest CD-ROM will work with such a drive?   thanks,M Charles Barilleaux   ------------------------------   Date: 18 Aug 2000 17:44:34 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)3 Subject: Re: Toshiba CD-ROM and VMS Hobbiest CD-ROMa6 Message-ID: <8njsm2$erc$1@mailint03.im.hou.compaq.com>  X In article <399d71db.23652009@news.one.net>, chbarr@one.net (Charles Barilleaux) writes: :...Toshiba XM-4101B...rM :Does anyone know if the OpenVMS hobbiest CD-ROM will work with such a drive?N  F   Please see the OpenVMS FAQ -- OpenVMS will generally work with most F   any SCSI CD-ROM device that supports 512-byte block transfers.  (UseF   of 2048 byte blocks is typical of most CD-ROM drives, while support -   for 512 byte blocks is somewhat more rare.)e  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Thu, 17 Aug 2000 22:28:53 -0400T* From: David A Froble <davef@tsoft-inc.com> Subject: Re: VAXSTATION 4000/90t- Message-ID: <399C9F65.32CD27C6@tsoft-inc.com>    moi_is_me wrote: >  > Hi, C >   First, thanks to those whom responded to other questions i havet >   posted for the 4000/90 > ' >   Anyways, two more (quick) questions/ > C > Q1 - Where can i obtain the last firmware update for this machinet: >      (i've checked ComPaq, but didn't see it - dylexia?)  L First, I may be totally wrong, so don't be surprised if that's so.  I do notL think this, nor any/many other VAXs allowed firmware versions to be loaded. M What shipped with the system is usually what you get, except for any upgradesS, which I think required replacement of chips.  : > Q2 - What is the largest drive supported by this machine  P I've had 9.1 GB drives on one.  You can probably use the largest drive availableO today with VMS.  The console code will probably have problems after 4 GB or so,dN and may not report the correct size.  VMS may still be able to use the drive. P There may be a problem with drives that require more than 24 bits to address theF sectors.  Not real up to date on such, just remember some discussions.  P If you're not going over 4 GB, there should be no problems from size.  Some SCSI% drives do not work too well with VMS.>   Dave   -- Z4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------    Date: 18 Aug 2000 10:58:11 -05003 From: rivie@server.newlogan.teraglobal (Roger Ivie)O Subject: Re: VAXSTATION 4000/903> Message-ID: <slrn8pqnb8.1b80.rivie@server.newlogan.teraglobal>  C In article <399C9F65.32CD27C6@tsoft-inc.com>, David A Froble wrote:o >moi_is_me wrote:>D >> Q1 - Where can i obtain the last firmware update for this machine; >>      (i've checked ComPaq, but didn't see it - dylexia?)  >aM >First, I may be totally wrong, so don't be surprised if that's so.  I do not<M >think this, nor any/many other VAXs allowed firmware versions to be loaded.  N >What shipped with the system is usually what you get, except for any upgrades- >which I think required replacement of chips.   L While there may not have been firmeware updates available, the 4000/90 _did_H use Flash chips and the _were_ write-enabled by default. I found out the	 hard way.   N I had this project that involved playing with a bare NV5. To that end, I wroteK a small VAX FORTH. I used a 4000/90 to debug some of the NVAX-specific bitsfL of the code, but I did most of the debugging on a 4000/60. Consequently, theJ FORTH system had an I/O system capable of running on either the 4000/60 orJ the 4000/90. There was a bug in the 4000/90 detection code, so it used theI 4000/60 I/O system. Or attempted to. The problem is that there's flash in E 4000/90 where there's a UART in the 4000/60. And that flash magically F seemed to contain an ASCII space (perhaps part of a message), which isG magically the "erase chip" command for the flash in use. To make a long-! story short, I toasted the flash.F  6 On two systems before I figured out what was going on.  I Oh, I tried to fix it, but that just got me in more trouble. You see, theFF flash chips are right next to the power connector so it's difficult toG solder them back on once you've pulled them off to reprogram them. So IPG put sockets in (because you can go in through the space occupied by the2@ chip in the socket and don't have to try to go through the power connector).i  G Field Service was not amused when they came to work on the machines onep& day and found sockets under the flash. -- N
 Roger Ivie% TeraGlobal Communications Corporation.& 1770 North Research Park Way Suite 100 Logan, UT 84341A mailto:rivie@teraglobal.com/ phoneto:(435)787-0555r faxto:(435)787-05162    > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----A http://www.newsfeeds.com - The #1 Newsgroup Service in the World!:> -----==  Over 80,000 Newsgroups - 16 Different Servers! =-----   ------------------------------  # Date: Fri, 18 Aug 2000 16:31:13 GMT,% From: hg/jb <shsrms@bellatlantic.net>n  Subject: Re: VMS on a notebook ?0 Message-ID: <399D66BD.73F5A506@bellatlantic.net>  
 Thanks Peter,iE how did you get the image of vms hobbyist disk built into the system?c6 I am running an amd cpu, nt, charon, and when I try to boot dua1, I get a failure.I message is:  boot-f-Unknown processor   ?-06 halt inst pc 000050c7t   Peter Weaver wrote:n > @ > hg/jb wrote in message <3999C752.C06FEF4A@bellatlantic.net>...- > >think about charon vax on a fast notebook. * > >Might work...I have not tried it - YET. > >... > A > I have Charon-VAX running on a P150 with 32MB of memory runningiF > Win98SE. It works great as long as you aresc8 trying to do anything) > else on the machine when it is running.F   ------------------------------  % Date: Thu, 17 Aug 2000 23:19:53 -0400 * From: David A Froble <davef@tsoft-inc.com>  Subject: Re: VMS Vs any other OS- Message-ID: <399CAB59.532D198C@tsoft-inc.com>    Bill Todd wrote: > : > JF Mezei <jfmezei.spamnot@videotron.ca> wrote in message( > news:399C5D10.6CCC401C@videotron.ca... > > Bill Todd wrote:N > > > I have been under the impression that many people here wished to support > amJ > > > true VMS revitalization rather than simply a stabilization, and that > such0 > > > issues were therefore of general interest. > >aI > > And you have portrayed yourself as being one who firmly beleived that1 > CompaqH > > should just aim to solidify its remaining market niches and not risk
 > anything& > > to try to enlarge its marketshare. > K > While you're certainly under no obligation to have paid attention to whateM > I've said over time, by not having paid such attention you're equally in norF > position to comment on it.  But rather than suggest that you do your& > homework, I'll bring you up to date:  
 Ah, courtesy!   G > My first reaction to Compaq's lack of support for VMS, when it became0G > obvious to me shortly after getting acquainted with comp.os.vms about K > sixteen months ago, was indignation that they were ignoring - and in somerM > ways destroying - the value of such a major asset.  And I made that feelingo
 > clear here.o > K > After a period of time hearing others complain (but to all appearances do N > nothing else) and getting a better idea of the overall situation, I began toL > realize that the value of VMS, and its potential, might well not be at allI > obvious to Compaq - any more than it seemed to be obvious to DEC for soeK > long - and that the only likely way to bring it to their attention was to F > gather some kind of group support (since the long-term record of VMSL > customer effectiveness in changing the situation was shall we say dismal). > N > So I tried to explain how and why Compaq might not see the value of devotingN > resources to VMS with the hope of eliciting some kind of response suggestingJ > how the situation could be changed *from Compaq's viewpoint* in a mannerL > that would change their perception (i.e., stop just saying that Compaq wasK > screwing up, and instead understand their position and figure out what itgG > would take to change it - since persuasion hadn't enjoyed perceptibler > success for a decade or so).  L Since compaq is the current owner of VMS, and entirely in charge of how it'sO handled,  any approach other than trying to show them advantages in paying more H attention to VMS would be a waste of time and would fail.  Maybe not theL solution many would like, but it is Compaq's game, and you can only play theK cards you're dealt.  So, it's pretty obvious if you don't have a big enought- stick, then the carrot is your only recourse.t  I > (I suspect that approach is what put me in touch with a group of peoplerK > actually interested in doing something more than just piss and moan.  ButXM > since those interactions were private, they don't particularly apply here.)  > K > Recently, there's been the issue of VMS's supposed 'renaissance'.  On theiM > one hand, there's clearly been *some* change in Compaq's attitude:  they'retN > starting to take off VMS's most constrictive manacles and at least allow itsH > praises to be sung *within* the existing VMS community - as long as itL > doesn't cost much of anything (e.g., improving its Web presence - *within*M > the VMS sub-tree) or compete overtly with Compaq's other offerings.  On thetJ > other hand, they've given VMS negligible general advertising funding andN > made no other move signifying that they're willing to tie Compaq's future toH > VMS's (and thus make VMS a credible long-term OS choice for anyone notK > already committed to it), and I've been vocal in criticizing this lack of1E > *real* (money:  that's what's real in this game) support and in theRH > overexuberance of those who would see in Compaq's pitifully inadequateG > actions far more reason for optimism than seems warranted (unless alldF > they're looking for is reassurance that VMS isn't going to disappear > completely any time soon).  P There is movement, abet slower than many would find optimum.  There is also veryN little (well, size is a very relative term) VMS specific advertising.  I wouldN point out that what one see as inadequate, others may view as small steps thatK must be taken before bigger steps are possible.  The optimism isn't blind.  P However, I do share Bill's view that bigger steps now rather than possibly later would have been nice.   * >  And from your posts, it seemed apparentG > > that you were against Compaq betting any of its business or risking1
 > anythingA > > to try to recapture any of the marketshare it had lost due tow > non-competitivedJ > > practices (and since all of that business happens to be at a lower end > thanM > > the remaining few market niches, it comes out as you being against CompaqoH > > taking any serious steps (eg: spend money) on re-capturing lower-end > sales.A > > (eg: compete against NT/linux servers and high end desktops).  > K > If you'd paid attention, you would have seen that my criticism focused ontN > the likely ineffectiveness of efforts in such areas *before* re-establishingN > general credibility in the higher-end areas where VMS's remaining acceptanceI > gives it some chance of doing so - by returning to vigorous development L > (aimed at eliminating strategic functional limitations, many of which haveM > been discussed here recently and few of which are likely all that importantmE > to the existing customer base but are critical to expanding it) and H > initiating (since saying 'returning to' might be inappropriate) *real* > marketing efforts. > M > Without such preliminary steps, a sudden all-out assault on NT and Linux byrM > VMS could easily be seen as so insane a move that Compaq's stock could sinkcM > to levels low enough to encourage a take-over.  Even after such preliminaryrN > steps, it may well not be in Compaq's interest to do anything more than makeL > VMS reasonably available in the low end, rather than push it aggressively:4 > it has multiple other systems covering that space.  H As an example.  Does anyone really feel that VMS in the short term couldO challenge windoz as typewriter and calculator replacements?  Waste your efforts2E on this, and you won't just be perceived as crazy, you will be crazy.l  N However, an effort to provide more affordable VMS at the low end to be used inN places where it can thrive is a more worthy goal, and one that would help make# the statement that VMS is NOT dead.t  M There is a big difference in the two stated examples, even though the actions I required may be similar, reasonable goals will allow a chance of success,n( unreasonable goals will produce failure.   > > M > > To reclaim its stake as a scalable operating system, VMS must spend a lotn > ofD > > money to bring back applications and price itself competitively.  K Yep!  People buy solutions, and they shop for the best solution at the bestsO price.  Many times best price will help define what qualifies as best solution.,  H > VMS stands no chance whatsoever of reclaiming significant market shareL > unless it undertakes major new development (not currently under any publicJ > consideration) to retain its current, but rapidly diminishing, technicalM > superiority (to keep giving users biased toward other systems some tangiblebH > reason to consider it), ensures that the Unix/Linux compatibility workD > already mentioned is effective in building useful bridges to thoseJ > environments rather than just a 'check the box' feature, and gets *real*K > advertising support from Compaq to make both current and future strengths ; > widely visible, along with Compaq's long-term commitment.  > K > That's the minimum required to restore general credibility for VMS in itssM > *existing* strongholds (which will otherwise likely continue to erode:  who L > wants to be stuck with a dead-end OS, even if it will be around forever?).N > Once a good start has been made doing that, there'll be a base from which toL > try to expand by increasing availability of applications (whose developersL > would then likely have greater interest in porting them).  As for pricing,N > that's debatable:  my impression is that compared to these other issues it'sJ > relatively minor (or, to put it another way, that existing pricing wouldI > by-and-large be competitive if these other problems were fixed), though K > there are some low-end-specific areas in which *somewhat* more aggressive N > pricing likely would cost Compaq very little and provide at least some moral
 > support.  M And some pricing has changed.  If you compare a DS10L with VMS to a DS10L fornG Linux, the difference is in the neighborhood of $1,100, and unless I've H misunderstood includes the networking.  I believe this same software forM workgroup class systems would have cost over $3,000, maybe over $4,000 a yearSN ago.  A year ago a cluster license for this system would cost $12,000, and nowN costs $6,000, and a client version (cannot share/serve it's disks) is $1,500. K In the case of a DS10L, the cost of VMS does approach windoz, and while the E cluster license could be better, there has been significant movement.d  M > The real problem continues to be that Compaq shows absolutely no indicationdM > of willingness to consider any kind of aggressive action, regardless of itsiN > nature.  And as long as that's the case, VMS will continue to be a sluggish,K > half-submerged ship struggling to remain afloat, even though it may never  > actually sink. >  > - bill  H Well, not sinking is better than sinking, and a worthwhile goal itself. K However, I'd perfer some more aggressive goals.  In any case, slow movement L toward a more competitive and acceptable VMS is better than no movement, andN much better than regression.  Actually, I don't think no movement is possible.   Dave   -- e4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  # Date: Fri, 18 Aug 2000 14:11:38 GMTo% From: hg/jb <shsrms@bellatlantic.net>t  Subject: Re: VMS Vs any other OS0 Message-ID: <399D4606.219AB91E@bellatlantic.net>  & (off topic just a tick, pardon please)H This is really great, I haven't seen this much "fun" on the vms ng since
 Carl died.  F Realize of course, all of you are expressing opinions, sprinkling someA good VMS data and more, in this thread, AND really delving into a@ centralCC debate that ties back to the steps that lead to the demise of dec -o$ and I fear many other companies too.   Keep at it, I am enjoying!!l bobs     Rob Young wrote: > ^ > In article <399C5D10.6CCC401C@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > > Bill Todd wrote:O > >> I have been under the impression that many people here wished to support akN > >> true VMS revitalization rather than simply a stabilization, and that such/ > >> issues were therefore of general interest.o > > P > > And you have portrayed yourself as being one who firmly beleived that CompaqQ > > should just aim to solidify its remaining market niches and not risk anything.& > > to try to enlarge its marketshare. > B >         This isn't true at all.  Not to defend Bill , he does an= >         adequate job at that.  But just want to affirm thattF >         Bill is *keenly* interested in the >> GROWTH << of VMS.  (1) > - >         I know something you don't know ;-)a > % >                                 Rob  > I > (1)  You may not agree with all his methods or ideas.  But you wouldn't * >         agree with all of mine either...   ------------------------------  # Date: Fri, 18 Aug 2000 14:20:59 GMTo% From: hg/jb <shsrms@bellatlantic.net>t  Subject: Re: VMS Vs any other OS0 Message-ID: <399D4838.BF264F18@bellatlantic.net>  & "Brian Schenkenberger, VAXman-" wrote: > Y > In article <spk3elplr5j171@news.supernews.com>, dpm@myths.com (David P. Murphy) writes:l) > >Bill Todd <billtodd@foo.mv.com> wrote:e > >o* > >> David P. Murphy <dpm@myths.com> wrote > > ? > >>> It's a free newsgroup, they're welcome to post as long as  > >>>   they're polite.  > >eI > >> Your opinion, which you're welcome to.  I framed my comments as *my*rL > >> opinion, which I see no reason to change:  in my opinion, there comes aG > >> point where continuing output-only contributions become pollution.r > >dF > >how reminiscent of carl.os.vms:  one person deciding when "opinion"! >                     ^^^^^^^^^^^F) > :)  Now where have I heard that before?5 >  > >becomes "pollution".  > I > I think Bill should remove all the restraints and call everybody "shit-l4 > for-brains", then it would be more like old times. > O > >> The way I play usually reflects what the people I'm responding to deserve.u > >: > >And you're proud of that? > F > Sounds like Bill is suffering from a chronic case of Lydickia.  You,E > David, as well as many others here who've sufferred tongue-lashingseF > from the late Mr. CJL should know that seeking tollerance is nothing; > more than an invite to further this sort of intollerance. % Well said Brian, Very very well said.oE As one of the other posters mentioned on this thread or an off shoot, ; Carl used to really illustrate his point with bits of code.hH The poster mentioned that it got him more interested.  I have to say the same.tF I managed to take over my shops last VMS systems and learned much muchG more from the list and the hands on than I did when I worked for dec...rH nothing like a few mistakes and a lashing from Carl to set you straight!  D Now, what apps does VMS really need?  Are we talking MS compatible, G MS apps directly ported?  Are we talking samba capability/compatiblity?f  F Assuming that this thread is intended to allow folks to vent AND make F constructive suggestions on what we would like to see VMS do, what are the 
 specifics?? Does the CharonVax emulator have any impact on VMS?  On Compaq?0 bob    >  > --Q > VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMT   ------------------------------  % Date: Fri, 18 Aug 2000 10:34:41 +0100e, From: aus@vim.uni-wuerzburg.de (Hans M. Aus)$ Subject: Re: What quota was exceededD Message-ID: <aus-1808001034410001@wvia71.virologie.uni-wuerzburg.de>  H In article <399C3BFB.86412858@srv.net>, Kevin Handy <kth@srv.net> wrote:   ...t > @ > How do I figure out which quota is getting exceeded so I don't+ > have to keep randomally adjusting quotas?    $ !d $ ! WATCH_1_USER.COMN $ ! watches specified process for the quota remaining and highlights low lines9 $ ! Simon Maufe Digital Colorado Springs January 2nd 1993t= $ !                                                             H WATCH_1_USER.COM is a lifesaver for discovering which quota is exceeded.I The program might be available on DECUS or Freeware sources; if not, I'llaA send it to you. Simon left Digital several years ago but gave hisU, permission to distribute the program freely.   -- 7B Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de   ------------------------------  # Date: Fri, 18 Aug 2000 10:13:40 GMTu From: spolato@my-deja.com-$ Subject: Re: What quota was exceeded) Message-ID: <8nj28a$caq$1@nnrp1.deja.com>-  ' In article <399C3BFB.86412858@srv.net>,1"   Kevin Handy <kth@srv.net> wrote:B > I'm trying to do a compile (Large VaxBasic program on a VAX3100)$ > and am getting the unhelpful error >t$ > 	%SYSTEM-F-EXQUOTA, exceeded quota >bE > but I don't know which quota has been exceeded. I'vr tried boosting,@ > up all the user quotas for this account, but haven't fixed the > error yet. >e@ > How do I figure out which quota is getting exceeded so I don't+ > have to keep randomally adjusting quotas?e >tG Have a look at the Pgflquo limit in the user authorization file (in thewB most of cases this is the quota limit I must adjust for my users).G Be aware of the related value of VIRTUALPAGECNT sysgen parameter and ofs the page file size.t  
 Sandro Polatoi    & Sent via Deja.com http://www.deja.com/ Before you buy.-   ------------------------------  % Date: Fri, 18 Aug 2000 09:52:07 -0400  From: DAVID_WHITE@phl.com>$ Subject: Re: What quota was exceeded= Message-ID: <OF908CA64B.289B4719-ON8525693F.004BECD5@phl.com>:  I We are trying to solve a similar problem where a user's process quota are5J being exceeded.  Once the process fails the quota's are reset.  Is there aE way to capture the quota's when the process fails and before they aree reset?      \                                                                                             \                     aus@vim.uni-wu                                                          \                     erzburg.de            To:     Info-VAX@Mvb.Saic.Com                     \                     (Hans M. Aus)         cc:                                               \                                           Subject:     Re: What quota was exceeded          \                     08/18/00 05:34                                                          \                     AM                                                                      \                                                                                             \                                                                                                     H In article <399C3BFB.86412858@srv.net>, Kevin Handy <kth@srv.net> wrote:   ...  >e@ > How do I figure out which quota is getting exceeded so I don't+ > have to keep randomally adjusting quotas?n   $ !t $ ! WATCH_1_USER.COMH $ ! watches specified process for the quota remaining and highlights low lines 9 $ ! Simon Maufe Digital Colorado Springs January 2nd 1993s $ !   H WATCH_1_USER.COM is a lifesaver for discovering which quota is exceeded.I The program might be available on DECUS or Freeware sources; if not, I'lltA send it to you. Simon left Digital several years ago but gave hise, permission to distribute the program freely.   --B Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de   ------------------------------  % Date: Fri, 18 Aug 2000 17:12:10 +0100s, From: aus@vim.uni-wuerzburg.de (Hans M. Aus)$ Subject: Re: What quota was exceededD Message-ID: <aus-1808001712100001@wvia71.virologie.uni-wuerzburg.de>  = In article <OF908CA64B.289B4719-ON8525693F.004BECD5@phl.com>,g DAVID_WHITE@phl.com wrote:  K > We are trying to solve a similar problem where a user's process quota are L > being exceeded.  Once the process fails the quota's are reset.  Is there aG > way to capture the quota's when the process fails and before they ared > reset? >  >    David,  I I watch the display as the user runs his application; its usually obviousiH what's going wrong. All you have to know is the PID of the user with the problem.   --  B Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de   ------------------------------   Date: 18 AUG 2000 15:59:31 GMT6 From: greenwoodde@feda34.fed.ornl.gov (Dave Greenwood)$ Subject: Re: What quota was exceeded2 Message-ID: <18AUG00.15593199@feda34.fed.ornl.gov>   DAVID_WHITE@phl.com wrote: >  tK > We are trying to solve a similar problem where a user's process quota aresL > being exceeded.  Once the process fails the quota's are reset.  Is there aG > way to capture the quota's when the process fails and before they arei > reset?  D I have a C program that watches another process's quotas, displayingD current, min and original values for each monitored quota.  When theA monitored process fails, the C program still displays the minimumoC quota values.  The original version is from the same CJL whose name E has appeared in another current thread or two.  I'll be glad to emailoA the source to anyone who wants it.  (The recently posted .COM may'A also display the min value - I haven't looked at it to find out.)    Dave --------------9 Dave Greenwood                Email: Greenwoodde@ORNL.GOVaH Oak Ridge National Lab        %STD-W-DISCLAIMER, I only speak for myself   ------------------------------  # Date: Fri, 18 Aug 2000 16:27:20 GMTn/ From: "Richard L. Dyson" <rick-dyson@uiowa.edu>e$ Subject: Re: What quota was exceeded) Message-ID: <399D1D98.353F8923@uiowa.edu>p  ; In article <OF908CA64B.289B4719-ON8525693F.004BECD5@phl.coml >, DAVID_WHITE@phl.com wrote:u > K > We are trying to solve a similar problem where a user's process quota areaL > being exceeded.  Once the process fails the quota's are reset.  Is there aG > way to capture the quota's when the process fails and before they areT > reset?  G The simpel COM procedure posted here is good.  I recall a DECUS sessionhB where this topic was used to show a nice feature of the AMDS AvailE product.  You could use it to graphically to watch a single process'soF various UAF processes.  When the "temperature" bar pegged at 100%, you9 could then tell which one of the quota's was the culprit.   D It is a lot more overhead and work to get it running than the simpleF QUOTA.COM just posted though.  But if you were already an AMDS fanatic it might be the way to go...   Rick -- sH Richard L. Dyson                                    rick-dyson@uiowa.eduH  _   _      _____                http://www-pi.physics.uiowa.edu/~dyson/H | | | |    |_   _|   Systems Analyst                     O: 319/335-1879H | | | | of   | |     The University of Iowa            FAX: 319/335-17536 | \_/ |     _| |_    Department of Physics & Astronomy-  \___/     |_____|   Iowa City, IA 52242-1479o   ------------------------------  % Date: Fri, 18 Aug 2000 10:45:08 -0600  From: Kevin Handy <kth@srv.net>h$ Subject: Re: What quota was exceeded' Message-ID: <399D6814.78A219EB@srv.net>m  * I would appreciate getting a copy of this.   Dave Greenwood wrote:  >  > DAVID_WHITE@phl.com wrote: > >eM > > We are trying to solve a similar problem where a user's process quota are N > > being exceeded.  Once the process fails the quota's are reset.  Is there aI > > way to capture the quota's when the process fails and before they arel
 > > reset? > F > I have a C program that watches another process's quotas, displayingF > current, min and original values for each monitored quota.  When theC > monitored process fails, the C program still displays the minimum:E > quota values.  The original version is from the same CJL whose name.G > has appeared in another current thread or two.  I'll be glad to emaildC > the source to anyone who wants it.  (The recently posted .COM maynC > also display the min value - I haven't looked at it to find out.)  >  > Dave > --------------; > Dave Greenwood                Email: Greenwoodde@ORNL.GOVeJ > Oak Ridge National Lab        %STD-W-DISCLAIMER, I only speak for myself   ------------------------------  % Date: Fri, 18 Aug 2000 10:46:09 -0600e From: Kevin Handy <kth@srv.net>n$ Subject: Re: What quota was exceeded' Message-ID: <399D6851.47A4D7D2@srv.net>    Thanks. That was the one.c   spolato@my-deja.com wrote: > ) > In article <399C3BFB.86412858@srv.net>,V$ >   Kevin Handy <kth@srv.net> wrote:D > > I'm trying to do a compile (Large VaxBasic program on a VAX3100)& > > and am getting the unhelpful error > >t+ > >       %SYSTEM-F-EXQUOTA, exceeded quotas > >cG > > but I don't know which quota has been exceeded. I'vr tried boostinghB > > up all the user quotas for this account, but haven't fixed the > > error yet. > >dB > > How do I figure out which quota is getting exceeded so I don't- > > have to keep randomally adjusting quotas?c > > I > Have a look at the Pgflquo limit in the user authorization file (in thebD > most of cases this is the quota limit I must adjust for my users).I > Be aware of the related value of VIRTUALPAGECNT sysgen parameter and of  > the page file size.h   ------------------------------  % Date: Fri, 18 Aug 2000 02:27:03 -0400r From: quayle@pobox.com1 Subject: Re: Why couldn't linux read a vms drive?n/ Message-ID: <399C9EF7.25060.134D4694@localhost>t  ? > I don't know if Linux has the ability to read ODS-2 or ODS-5.t  E Not yet.  I believe ODS-2 support is on the list of things to do for d the Linux on VAX effort.     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671n1 8572 North Spring Ct. NW, Pickerington, OH  43147e= Preferred address:  stan@stanq.com       http://www.stanq.come   ------------------------------  % Date: Thu, 17 Aug 2000 23:31:50 -0500c) From: "John E. Malmberg" <wb8tyw@qsl.net> 1 Subject: Re: Why couldn't linux read a vms drive?e/ Message-ID: <sppfprkp87v163@corp.supernews.com>g   Is that all you want?l   Here:o  C http://forthnet.linuxberg.com/conhtml/preview/017-013-007-088C.htmle   Here are a few other links:h  4 http://www.openvms.digital.com/freeware/ODS2-READER/  - http://www.openvms.digital.com/freeware/ODS2/r  $ Read the license terms carefully :-)   -JohnI wb8tyw@qsl.network  K Let see, now known for LINUX, you can get at least one DCL emulator, DECNet1E Phase IV, ODS-2, and someone reported recently that LAT is available.    ------------------------------  % Date: Fri, 18 Aug 2000 09:48:56 +0200,= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>f1 Subject: Re: Why couldn't linux read a vms drive?6) Message-ID: <399CEA68.6A6A5D0C@gtech.com>r   Beyonder wrote:1G > I mentioned this briefly in another post. but I thought I'd break off # > the thread into a seperate thing.b > J > Linux has support for all sorts of volumes of just about every major OS. > J > Linux supports just about every filesystem known to man. It can read and > write justD > about every hard drive from every OS on the planet. HPFS, NT, Dos,G > Win95/98, even Apple (MAC), OS/2, Solaris, SCO, BSD, and even Amiga !i > G > If it has this much power, and all the code is there to look at, I'vel > beenG > wondering why can't Linux at least READ a Vax or Alpha (VMS) volume ?eH > It should be technically possible, the ground work should all be there > already, butE > I don't really know, see, I haven't been able to look at the sourcee > listings yet  F ODS2-readers has been written. ODS-5 is not that different from ODS-2.( The format are relative well documented.  B So here we have a nice task just waituing for an enthusiatic Linux programmer to implement !E   Arne   ------------------------------   Date: 18 Aug 2000 11:28:37 GMT' From: david20@alpha2.mdx.ac.uk (D.Webb) 1 Subject: Re: Why couldn't linux read a vms drive? 0 Message-ID: <8nj6l5$lvv$1@aquila.news.mdx.ac.uk>  K In article <399CA839.796E64AF@vrx.net>, Beyonder <beyonder@vrx.net> writes: F >I mentioned this briefly in another post. but I thought I'd break off" >the thread into a seperate thing. > I >Linux has support for all sorts of volumes of just about every major OS.d >SI >Linux supports just about every filesystem known to man. It can read ande >write justcC >about every hard drive from every OS on the planet. HPFS, NT, Dos,eF >Win95/98, even Apple (MAC), OS/2, Solaris, SCO, BSD, and even Amiga ! >:F >If it has this much power, and all the code is there to look at, I've >beenvF >wondering why can't Linux at least READ a Vax or Alpha (VMS) volume ?G >It should be technically possible, the ground work should all be therea
 >already, but D >I don't really know, see, I haven't been able to look at the source
 >listings yete >(blatant plug!) >  >B.a >p   You might want to look at   $ http://linux-decnet.sourceforge.net/   ands   http://ndupeux.free.fr/phprms/  I and there might also be something off the http://www.free-vms.org/ pages.   : Though I'm not sure what the current state of free-vms is.    
 David Webb VMS and Unix team leader CCSS Middlesex university   ------------------------------  # Date: Fri, 18 Aug 2000 13:41:19 GMT ! From: Beyonder <beyonder@vrx.net>d1 Subject: Re: Why couldn't linux read a vms drive? ' Message-ID: <399D3D1A.14D76DBF@vrx.net>    Arne Vajhj wrote:  * > The format are relative well documented. >oD > So here we have a nice task just waituing for an enthusiatic Linux > programmer to implement !g  K Well I'm enthusiastic about it, all I need is access to the source listings3 (heh). (that was a joke! sort of...)B   B.   ------------------------------    Date: 18 Aug 2000 10:43:42 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) 1 Subject: Re: Why couldn't linux read a vms drive?>+ Message-ID: <O1ZedLwUzPTJ@eisner.decus.org>   [ In article <sppfprkp87v163@corp.supernews.com>, "John E. Malmberg" <wb8tyw@qsl.net> writes:e  M > Let see, now known for LINUX, you can get at least one DCL emulator, DECNet>G > Phase IV, ODS-2, and someone reported recently that LAT is available.   G Wow, this Linux thing has started emulating a _real_ operating system !    ------------------------------   Date: 18 Aug 2000 14:25:05 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)1 Subject: Re: Why couldn't linux read a vms drive?"6 Message-ID: <8njh01$cpi$1@mailint03.im.hou.compaq.com>  I   There is absolutely no technical reason why any system cannot read any kG   other system's file system -- though some systems will make accessingmE   "foreign" file systems more difficult and some provide for it.  Butn   you probably knew that.r  G   Now as to whether or not the results will be useful, that is another wF   question.  There are record and data and character conversion issuesC   involved, as well as expectations around the libraries and tools iG   available.  With OpenVMS, for instance, RMS is layered on top of the oB   file system (XQP) and provides for a rather extensive (complex, D   flexible, lots-o-knobs) interface for working with the basic file H   system support that is provided by the XQP.  Other systems may or may H   not have a standard/integrated API similar to RMS, or may require thatI   the existing API be matched to that of RMS and the XQP (and the on-disk    structure).  e  I   Some systems will have one sequential file format, RMS provides a raft lF   of differing sequential file formats -- and each requiring at least H   some level of separate handling, if full compatibily is desired.  (AndJ   the mapping between these formats can be really "fun" -- please see the H   ADF stuff over in the TCP/IP Services NFS Client for an "introduction"   to what I mean here.)c  K In article <399D3D1A.14D76DBF@vrx.net>, Beyonder <beyonder@vrx.net> writes:u :Arne Vajhj wrote:X :(+ :> The format are relative well documented.- :>E :> So here we have a nice task just waituing for an enthusiatic Linuxr :> programmer to implement ! :WL :Well I'm enthusiastic about it, all I need is access to the source listings  K   That would be the hard way -- you will want to work with the on-disk datanL   structures and such as a start, then work your way to the source listings.K   Direct access to files is an entertaining project, with the requirements _H   of mapping the various record structures across heterogeneous systems.  M   I'd suggest the existing tools for accessing ODS-2 that are present on the  M   OpenVMS Freeware, and (most importantly) starting by acquiring the existing J   VMS File System Internals (McCoy) book.  That book is specific to ODS-2,K   but the salient difference between ODS-2 and ODS-5 (on-disk!) involves a eH   few changes to constants, as well as supplementing the FI2DEF on-disk <   structure with (when needed) the FI5DEF on-disk structure.   :(heh).. :(that was a joke! sort of...)  H   Without intending this to be rude, you might want to consider what theL   particular reception your remarks might encounter among the various folks J   in the audience.  As a specific instance, I will look for and will read J   postings that are written by certain some folks -- simply because these G   folks regularly have interesting insights, humorous perspectives, or AK   useful feedback or comments -- even if I am not interested in the thread tJ   itself.  In other cases, folks reading this or any other newsgroups can M   and do add the less useful or less interesting threads into the newsreader oJ   "kill-file" -- completely ignoring subsequent discussions in the thread.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Fri, 18 Aug 2000 07:12:06 -0700t- From: Randy Winfrey <dnsrw@ccvms.concord.edu> - Subject: X terminals that speak DECnet or LAT-9 Message-ID: <05043480.1eda3149@usw-ex0109-069.remarq.com>H  0 Does anyone still manufacture an X terminal that9 communicates via DECnet or LAT. Jupiter used to sell one,m but they don't anymore.l   Thanks,r   Randyw           * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifule   ------------------------------   Date: 18 Aug 2000 15:05:07 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)1 Subject: Re: X terminals that speak DECnet or LAT 6 Message-ID: <8njjb3$d2t$1@mailint03.im.hou.compaq.com>  i In article <05043480.1eda3149@usw-ex0109-069.remarq.com>, Randy Winfrey <dnsrw@ccvms.concord.edu> writes: 1 :Does anyone still manufacture an X terminal that   :communicates via DECnet or LAT.  G   You can load the EWS software (on the OpenVMS Freeware website) onto  H   various older VAXstation systems, and turn the box into an X Terminal.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 18 Aug 2000 15:36:41 GMT / From: "Richard L. Dyson" <rick-dyson@uiowa.edu> 1 Subject: Re: X terminals that speak DECnet or LAT2) Message-ID: <399D11B9.75B6E252@uiowa.edu>t   Randy Winfrey wrote: > 2 > Does anyone still manufacture an X terminal that; > communicates via DECnet or LAT. Jupiter used to sell one,A > but they don't anymore.   H I researched this some long ago and we settled on Tektronix X Terminals.E (XP4xx line).  They did DECWindows over DECnet as well as having LAT,SE telnet, and CTERM VT340 emulators.  They can also run DECWindows overgD TCP/IP and used XDMCP for your Unix (& Multinet?) friends.  They hadC OpenVMS VAX and Alpha server software and up to 21" dual-head boxesm= that can connect to most X-type and some WinDoze servers too.   I However, Tek sold everything to NCD (which used to make X terms, but did -H not support OpenVMS in the past), including the people :).  NCD sells a C NC4xx line and I have a couple of them too.  They may not sell thisD model1D anymore.  It depends on how much performance you are looking for.  IG see they still list the NC200 and now a NC900.  I don't know if that is:B OpenVMS compatible or not.  Things still work for my XP421s and my NC421sC with the old Tek OpenVMS server and the NCD version.  Once, the NCD. producteB manager contacted me about what OpenVMS users would want for mediaE distribution (they only had TK50 at that time!!!).  I begged for CDs,  buthH they wanted to see if 4mm would be OK... At that time (6+ months ago) heD assured me (for whatever that is worth!) they were going to continue OpenVMS support.  & Here is one place to start looking at:  * 	http://www.ncd.com/products/hardware/ncs/  E I would recommend contacting a sales rep and asking questions to themu as to what is available now.  A Let us know if you find anything worthwhile.  At least I would beT curious G about an update to the X Terminal market.  Mine will eventually die andr- need to be replaced with something someday...r   Regards, Rick --  H Richard L. Dyson                                    rick-dyson@uiowa.eduH  _   _      _____                http://www-pi.physics.uiowa.edu/~dyson/H | | | |    |_   _|   Systems Analyst                     O: 319/335-1879H | | | | of   | |     The University of Iowa            FAX: 319/335-17536 | \_/ |     _| |_    Department of Physics & Astronomy-  \___/     |_____|   Iowa City, IA 52242-1479d   ------------------------------    Date: 18 Aug 2000 18:53:09 +0200* From: eplan@kapsch.net (Peter LANGSTOEGER)1 Subject: Re: X terminals that speak DECnet or LATt* Message-ID: <399d69f5$1@news.kapsch.co.at>  [ In article <399D11B9.75B6E252@uiowa.edu>, "Richard L. Dyson" <rick-dyson@uiowa.edu> writes:  >Randy Winfrey wrote:I >>  3 >> Does anyone still manufacture an X terminal that < >> communicates via DECnet or LAT. Jupiter used to sell one, >> but they don't anymore.  I Is this really absolutely neccessary ? Now that OpenVMS offers good TCPIPp9 features it may be not worth to pay for these add-ons ....  I >I researched this some long ago and we settled on Tektronix X Terminals.pF >(XP4xx line).  They did DECWindows over DECnet as well as having LAT,F >telnet, and CTERM VT340 emulators.  They can also run DECWindows overE >TCP/IP and used XDMCP for your Unix (& Multinet?) friends.  They hadl   TCPware also offers an XDMCP.d  D >OpenVMS VAX and Alpha server software and up to 21" dual-head boxes> >that can connect to most X-type and some WinDoze servers too. > J >However, Tek sold everything to NCD (which used to make X terms, but did ; >not support OpenVMS in the past), including the people :).o  7 NCD did support OpenVMS a long time and maybe still do.kI They even supported the boot of the NCD X-Terminals from a OpenVMS systemo via MOP (and BOOTP/TFTP).t  H And finally they really made an add-on XDMCP for OpenVMS well before PSC0 did it for TCPware or DEC refused to make one !!   >[snip]_' >Here is one place to start looking at:o >e+ >	http://www.ncd.com/products/hardware/ncs/y > F >I would recommend contacting a sales rep and asking questions to them >as to what is available now.-+ > http://www.ncd.com/products/hardware/ncs/iB >Let us know if you find anything worthwhile.  At least I would be >curiousH >about an update to the X Terminal market.  Mine will eventually die and. >need to be replaced with something someday...  8 I second this. I even need to suggest this to myself ;-)   just my 0.02 -- g< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888o< FBFV/Information Services           E-mail  eplan@kapsch.netF <<< KAPSCH AG  Wagenseilgasse 1     PSImail PSI%(0232)281001141::EPLANH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"N "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998   ------------------------------   Date: 18 Aug 2000 17:28:08 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)1 Subject: Re: X terminals that speak DECnet or LATs6 Message-ID: <8njrn8$env$1@mailint03.im.hou.compaq.com>  W In article <399d69f5$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes:.I :And finally they really made an add-on XDMCP for OpenVMS well before PSCl1 :did it for TCPware or DEC refused to make one !!-  <   XDMCP is in TCP/IP Services V5.1, currently in field test.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   End of INFO-VAX 2000.461 ************************47A4D7D2@srv.net>    Thanks. That was the one.c   spolato@my-deja.com wrote: > ) > In article <399C3BFB.86412858@srv.net>,V$ >   Kevin Handy <kth@srv.net-GԢ| sI_0-M\]a2b".2XTAuW##ٖQrvMfDw-C@[Y#HSgwrs	)8n;G\!\|=H;.{oW+Yhҏ޾~cZlsis>ܜ!~^]^QneN
*["Ϙ\pV!d
{H&
w Q6ӫga,<˩zո|~v>2Yw;ӹX['Ev9l<W,I?pT`lfh4o9=<H
0#Q)NϬ_ysko/;`Pmp/#$ҾF*z"=IƬ4NO.8V s07'ۍ8h
AGl#R.:#bQD]ȘXJV4K'^Wnua.4^zQyrmK3Zd~ߗg|BEa̋ˁg{reMnz[ҡL}dkk苵»m"%,fDP^<$?Cd3a}2#wg7dNXvXvX K%u	ºa].AXM98-D0DT`|8Ɖ~W!\s Ngfsb׀< |,'_ o_s>(sޛ}B_u:KWL55==	\m{&m0͍_?A/.꿠D1z11zPuu}N[NdA.ggJ=:|/ o#vy0E?uv#{ g>JY?3 _N"/r+[Ndk/[a+!SA$[J	|3e#F