HDTenEightyP/NetNews huggingface dataset:
From: vsmith@TECHNET.NM.ORG
Newsgroups: comp.os.vms
Subject: ACCVIO--virtual address space
Date: 5 Nov 92 21:50:30 GMT
Reply-To: vsmith@TECHNET.NM.ORG
Organization: New Mexico Technet   Albuquerque, NM

I am encountering an ACCVIO in a program which has been running 
successfully for 4+ years.  After analyzing the run and reading 
_System Messages and Recovery Procedures_, I believe the problem is
probably "an attempt . . . to make the user stack larger than the 
user's virtual address space permits" (p. 17).  If that is the case, 
the manual states two fixes, one of which is "increase the virtual 
address space available to the process in which the image is 
executed."  (The other fix does not seem usable in this instance.)

Our system manager is out and I can't find the particular FM I 
should read for information regarding this change.  Can someone 
point me to it?

Thanks -- 

Victoria        
 ==**--==**--==**--==**--==**-**-**==--**==--**==--**==--**==--**==
   Victoria A. Smith                   New Mexico Technet, Inc.
   Internet : vsmith@technet.nm.org    Albuquerque, NM  87109
 ==**--==**--==**--==**--==**-**-**==--**==--**==--**==--**==--**==
From: frank@rover.uchicago.edu (Frank - Hardware Hacker - Borger)
Newsgroups: comp.os.vms
Subject: Re: Hooking VT's up with 4-wire phone line?
Date: 11 Nov 92 16:29:00 GMT
Article-I.D.: rover.11NOV199210292003
Reply-To: frank@rover.uchicago.edu
Organization: Joint Center for Radiation Therapy
News-Software: VAX/VMS VNEWS 1.41

In article <1992Nov11.144500.12261@CERIS.Purdue.EDU>, collier@CERIS.Purdue.EDU (Dick Collier) writes...
>From article <1992Nov10.123242.5994@slcs.slb.com>, by brydon@asl.slb.com 
>(Harvey Brydon (918)250-4312) writes:
>... (much deleted)
>In using this wiring scheme I have routinely had excellent performance
>over distances in the range of 100-150 feet at 9,600 baud.  

	We've got runs going near 500 feet at 9,600 with no problems.
>I'm not sure
>what the upper limit of either speed or distance is -- obviously, as one
>increases, the other decreases.  (The limits might be obvious to an
>electrical engineer, which I am not.)

	The limit is basically the longer cable limiting the rise and
	fall time of the pulses. Also the resistance of the cable becomes
	a factor that is dependant on what the input impedance of the
	terminal is.

	We have a small test signal. It's basically a plain ascii text
	file containing nothing but upper case u's, (octal 125.) If you
	can reliably dump that down the line, you should be ok. It gen-
	erates a 4800Hz square wave. 

	Just about anybody can snarf a scope somewhere to look at the signal
	as it comes out of the computer and at the other end. Long as you
	still get +/-4 volts or so at the long end, you should be ok.

   Frank R. Borger - Physicist    __       Internet:  Frank@rover.uchicago.edu
Michael Reese - Univ. of Chicago |___      Phone : 312-791-8075 fax : 567-7455
  Center for Radiation Therapy   | |_) _   I'ts a recession when your neighbor
                                   | \|_)  losses his job; it's a depression
    "Birthplace of Softball"          |_)  when you loose yours. - H. Truman
Newsgroups: comp.os.vms
From: sysgaertner@cygnus.frm.maschinenbau.th-darmstadt.de (M. Gaertner, FRM, TH Darmstadt, Germany)
Subject: Fatal bugcheck while booting 8600 into cluster
Date: Wed, 11 Nov 1992 11:31:27 GMT
Reply-To: sysgaertner@cygnus.frm.maschinenbau.th-darmstadt.de
Organization: Fachbereichsrechner Maschinenbau, TH Darmstadt, Germany

Hello everybody,
we now have a problem and even our field-tech. can't help anymore.
Ok, our configuration:
1 * 6310, CI, name CYGNUS
1 * HSC 50, several disks (SW-Version HSC V410), CI (of course)
1 * 8600, with CI780 and all hardware status OK (checked by field!), BOOTES
Several workstations with NI-connect (CARINA, CANIS, AURIGX)

When running VMS5.4-2 everything works fine. Now we did the upgrade
to VMS5.5-1 and the problems begin.
When we boot the 8600 as the first system in the cluster, it will get some
timeouts on the CI but comes up. Booting the others then works fine.
Now, booting all other cpu's and then trying to boot the 8600 always
results in a fatal bugcheck.
See the procedure:
>>> b
     VAX/VMS Version V5.5-1 ...
%CNXMAN, Using remote access method for quorum disk
%PAA0, Path #1, Has gone from GOOD to BAD - REMOTE NODE CYGNUS
%PAA0, Path #1, Has gone from GOOD to BAD - REMOTE NODE HSC004

Waiting to form or join a VAXcluster system
%VAXCLUSTER-I-LOADSECB, loading the cluster security database
%CNXMAN, Using local access method for quorum disk
%CNXMAN, established "connection" to quorum disk
%MSCPLOAD-I-LOADMSCP, loading the MSCP disk server
%CNXMAN, Sending VAXcluster membership request to system CARINA 
%CNXMAN, Now a VAXcluster member - system BOOTES

... (goes on, OPCOM will be started and logfile initialized)

%%%%%%%% OPCOM....
Operator status for operator BOOTES::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;7
...
...

%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR  00000038/0000004c/00000040

%CNXMAN, Lost connection to system CYGNUS
%PAA0, port is reinitializing (49 retries Left), Check the error log
%CNXMAN, lost connection to system CYGNUS
%CNXMAN, lost connection to system AURIGX
%CNXMAN, lost connection to system CANIS

***** FATAL BUGCHECK... CLUEXIT
...
Current Process = Null

(and the usual bugcheck-procedure)

The field-tech. is telling us, the hardware is OK, and is was, before te 
upgrade.
What's the problem here, any hints?
Thanks for help

-----------------------------------------------------------------------------

                      M. Gaertner
                TH Darmstadt, W. Germany
	     Rechnergruppe FB 16-Maschinenbau
      SYSGAERTNER@CYGNUS.FRM.MASCHINENBAU.TH-DARMSTADT.DE
      Phone: Germany, (0)6151/16 5145
Newsgroups: comp.os.vms
Subject: Re: Hooking VT's up with 4-wire phone line?
From: don@zl2tnm.gen.nz (Don Stokes)
Date: 14 Nov 92 02:32:24 GMT
Distribution: world
Organization: The Wolery

collier@CERIS.Purdue.EDU (Dick Collier) writes:
> In using twisted-pair telephone cable for RS-232 data communications it is
> important that the two signal wires (those connected to pins 2 & 3) not be 
> the two wires in a single pair.  Doing so leads to cross-talk between the
> transmit and receive signals, which decreases reliability, maximum line 
> length and maximum transmission speed.  Instead, have each pair carry a
> signal line and a ground.

Correct, and if you're going for a really long run, try for shielded cable.
 
> In many hardware systems (combination of host and terminal) it is 
> unnecesary to use both pins 1 & 7.  Some manufacturers cross-connect
> these pins within their equipment.  For others, shorting pins 1 & 7 in the
> DB-25 connectors works well. ( However, beware of ground loops! )  The
> advantage of this is that it leaves one conductor available for use as an
> RS-232 hardware control signal, usually RTS.  

Do *NOT* use pin 1 in the data signalling.  Pin 1 should only be used to 
attach a shield.  The shield should be grounded (to pin 1 and/or the
connector shell) at *one* *end* *only*.  If you're not sure, don't connect
it.

Pin 1 is defined as chassis ground.  It _may_ (although shouldn't) be
attached directly to the signal ground.  Manufacturers will have made the
decision whether or not pin 1 & 7 should be shorted for reasons known
mainly to them -- don't try to second guess them with long lines involved;
ground loops are crash & burn territory.....

> In only two cases have I have observed interferences.  Both were when the
> cable was routed adjacent to equipment which generated large, variable
> electro-magnetic fields, a fume-hood motor in one case and an elevator
> motor in the other.  In both cases, re-routing the cable solved the
> interference problems. 

I've seen "RS232" cables run 200m across a factory and run at 19k2, by use
of the above techniques.  

--
Don Stokes, ZL2TNM (DS555)                        don@zl2tnm.gen.nz (home)
Network Manager, Computing Services Centre            don@vuw.ac.nz (work)
Victoria University of Wellington, New Zealand              +64-4-495-5052
Newsgroups: comp.os.vms
Subject: Re: What's the difference between 5.5-2HW and Remastered 5.5-2HW?
From: hansher@bclcl1.im.battelle.org (Kevin Hansher, Battelle Computing Center)
Date: 10 Nov 92 07:55:51 EST
Organization: Battelle, Columbus, OH

In article <1992Nov09.133435.12417@DIALix.oz.au>, dent@DIALix.oz.au (Andrew Dent) writes:
> We received ours installed on a 4000/100 and were informed the HW version is
> REQUIRED for the new hardware.
>  

I responded earlier directly to the original poster but I guess I will also
respond here...especially on your second question.  Regarding the kits, it
appears to me that the two kits (update and remastered) are for two different
purposes.  The update kit would be for those sites needing to "update" VMS.
The remastered kit is for those sites working from scratch for various reasons.
This is my best guess.  I used the "update" kit to upgrade from VMS 5.5-1,
but if I remember right (been a while since reading the notes) it can
be used anywhere from VMS 5.5 onwards.  Also it is highly recommended from
DEC that if you have VMS 5.5-2HW installed for new hardware that you update
to the real VMS 5.5-2 as soon as possible as it has additional patches that
were not in the "HW" release.  Also, "knock on wood", VMS 5.5-2 has been
very stable here for the past several weeks...we had to upgrade as soon as
it was released to install some new hardware into our cluster.

> How are people coping with the SET/SHOW DEFAULT bug documented in the
> release notes?

Ok, I'll bite on this one also, as this was a major concern for me when I
first read it also.  However, it turns out that this has always worked this
way; at least for many versions of VMS.  If you don't believe it, try it on
a previous version - I didn't believe it at first either.  Anyway, I called
CSC to see what was going on and they said they don't know why in the world
that it was documented the way it was in the release notes, but confirmed
again that this behavior has always existed.  It is not a CHANGE in
behavior.

-- 
------------------------------------------------------------------------------
Kevin Hansher			Symposium Session Quality Coordinator -
Battelle		        U.S. DECUS VMS Systems SIG
505 King Avenue	                Internet:	hansher@bclcl1.im.battelle.org
Columbus,  OH  43201		Voice: 614-424-4008  Fax:  614-424-5263
From: ESPHIGGINS@ESPRIT.UCG.IE ("Dr.Paul Higgins, CIM Research Unit, UCG, Ireland. Voice: +353-91-24411 Ext: 3122")
Newsgroups: comp.os.vms
Subject: Printer Drivers for the Apple Laser Writer (Postscript) Printer
Date: 8 Nov 92 17:01:00 GMT
Article-I.D.: esprit.01GQWZXZPDC40009EO
Distribution: world
Organization: The Internet

Date sent:  8-NOV-1992 17:00:23.72

 RE: Serial port printer driver for Apple Laser Writer (Postscript)

I am looking for a printer driver for an Apple Mac System 7 which will use a
serial port while the Ethernet is running. The printer is a local printer and
not on the network. 

Is there a driver which will use the Serial port or Modem port
while connected to a network?

Thanks in advance ....

P.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% Paul Higgins                            %                                   %
%%                                         %       CIM Research Unit           %
%% Email: esphiggins@esprit.ucg.ie         %       University College Galway   %
%% PSI  : PSI%027246054000556::esphiggins  %       Galway                      %
%% Voice: +353-91-24411 Ext. 3122          %       Ireland                     %
%% Fax  : +353-91-62894                    %                                   %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
From: DWING@UH01.Colorado.EDU ("would rather be skiing ...")
Newsgroups: comp.os.vms
Subject: Re: Task to task decnet problem
Date: 10 Nov 92 15:22:42 GMT
Distribution: world
Organization: The Internet

Carl J Lydick, CARL@SOL1.GPS.CALTECH.EDU, writes:

>In article <1dkkscINNptf@manuel.anu.edu.au>, bear@nuc.anu.edu.au (Bernhard
> Fabricius) writes:
>=A very simple (but not very elegant) way of doing this would involve letting
>=the "4.7" nodes' menu system send a mail-message to a special PCX account on
>=the "5.4-1" node. A low-prio background job on the "5.4-1" node then checks (at
>=regular intervals) if there is any new mail for the PCX account and runs PCX
>=with the requested file-name when there is. (You could put the requested
>=file-name in the "Subject" field of the mail-message).
[...]
>=This is quick and dirty, but very secure. (And your users need never know...)
>
>You've *GOT* to be kidding.  Anybody with TMPMBX priv and knowledge of the
>MAIL-11 protocol can forge network mail.

In the VMS V5.5-2 release notes there is a mention that the outgoing 
mail-11 agent turns on SYSPRV before sending mail.  Section 2.8.7.  This is
a new feature in VMS V5.5-2.

  MAIL now enables system privileges when it opens a DECnet connection
  to a remote mail server. The system manager can restrict outgoing
  access on the mail server object by using the following NCP command:
  [...]
  This command prevents unauthorized users from placing connections on
  the mail server object.

Note that it doesn't come 'out of the box' this way -- it'll have to be secured 
at each site.  (At least, that's how I read the release notes).  

-Dan Wing, dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet (DGW11)
 Systems Administrator, University Hospital, Denver
From: leichter@lrw.com (Jerry Leichter)
Newsgroups: comp.os.vms
Subject: re: How do I send a control-c to another process?
Date: 11 Nov 92 21:34:57 GMT
Distribution: world
Organization: The Internet


	Here's my situation: I have a 2 process system. The parent process
	is a graphical user interface written in C/Motif. This controls
	a fortran program that used to be command-line driven. The old fortran
	program used to trap control-c's. How can I get the gui to send a 
	control-c to the child? The unix function kill(SIGINT,pid) does
	not support the same fuctionality under vms as it does under Unix.

You don't explain how the parent process controls the FORTRAN program.

If it creates a pseudo-terminal and uses that to start the FORTRAN program,
then you can simply send a CTRL/C to the pseudo-terminal.

If it uses mailboxes, directly or through the VAX C pipe emulation; or the
pipe driver that came with the old VAX Shell; there's no way to do what you
want.  CTRL/C AST's are a product of the terminal driver.  No controlling
terminal, no CTRL/C AST's.  You'd have to re-design the inter-process
communication.  (The several ways this kind of thing is done on VMS.  One
simple one is to have another mailbox for interrupt requests.  The controlled
program posts a QIO (not QIOW) to that mailbox early on, requesting an AST
when the QIO completes.  When the controlling process needs to send an
interrupt, it writes an appropriate message to the interrupt mailbox.  This
causes the waiting QIO to complete, posting an AST to the process - which
then does whatever is necessary.
							-- Jerry

Newsgroups: comp.os.vms
From: larry@shiva.eco.twg.com (Lawrence B. Henry III)
Subject: Re: QIO failing with ACCVIO (WIN-TCP)
Reply-To: larry@eco.twg.com
Organization: The Wollongong Group (East Coast Operations)
Date: Thu, 5 Nov 92 23:19:03 GMT


In article <9211042022.AA20329@relay2.UU.NET>, ddj@gradient.UUCP writes:
|>Path: eco.twg.com!psinntp!sgigate!sgiblab!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!ucbvax!gradient.UUCP!ddj
|>From: ddj@gradient.UUCP
|>Newsgroups: comp.os.vms
|>Subject: QIO failing with ACCVIO (WIN-TCP)
|>Message-ID: <9211042022.AA20329@relay2.UU.NET>
|>Date: 4 Nov 92 20:22:21 GMT
|>Sender: daemon@ucbvax.BERKELEY.EDU
|>Distribution: world
|>Organization: The Internet
|>Lines: 43
|>
|>I have a network application that runs under VMS, and can use CMU,
|>Fusion, UCX, and DECnet transports.  After a "quick and easy" port
|>to TWG's WIN-TCP package, I started to get errors from the
|>SYS$QIO(... IO$_READVBLK...) call.
|>
|>The call comes back immediately with a status of ACCVIO.  This does
|>not happen right away -- the program succeeds in opening and exchanging
|>packets over two or three network ports to various servers, but when
|>it reaches the third (or fourth) port it fails.
|>
|>The worst part is that the problem does not occur when the program
|>is run from VMS DEBUG.  There is only one place in the program where
|>this call is made, and the arguments all look valid (and in fact the
|>call works properly for a couple dozen packets before the fourth
|>socket is opened).
|>
|>The program uses UDP packets (except for the decnet transport),
|>and is run as a detached process, with a bytlim of about 32k and
|>a file limit of about 30.  It is normally started at boot time,
|>with system privs.  However it still fails when I run it from
|>a terminal.
|>
|>1) What could be different between run/nodebug (or not compiled
|>for debugging), and running under the debugger?
|>
|>2) Is there any way to print the failed address, etc, when the
|>access violation is passed in the system call return value (as
|>opposed to getting the fault directly)?
|>
|>3) Has anyone else run into anything like this problem before?
|>What can be done to avoid it?  Is there a limit in the TWG network
|>ACP that would prevent a process from creating more than two or
|>three sockets and starting receives on them all?
|>
|>4) Is there a tool that can watch the quotas of a program while
|>it is running?
|>
|>Thanks in advance!
|>
|>	Dave Johnson
|>	ddj@gradient.com (or uunet!gradient!ddj)
|>	
|>
|>
Dave,
	Why don't you post this question to our news group 
vmsnet.networks.tcp-ip.wintcp or send me mail directly.. we will be more than
happy to address any questions you might have concerning our QIO interface
or socket library..

-Larry.
The Wollongong Group.
From: GREENWOODDE@FEDC06.FED.ORNL.GOV (Dave Greenwood)
Newsgroups: comp.os.vms
Subject: SUN as Xwindows server from VMS
Date: 10 Nov 92 19:15:38 GMT
Distribution: world
Organization: The Internet

One of our people is trying to use a SUN workstation as an Xwindows server to
a VMS client.  After the SET DISPLAY and CREATE/TERMINAL he gets the following
message on the SUN:

A command window has exited because its child exited.
Its child's process id was 258 and it exited with return code 10.
A command window has exited because its child exited.
Its child's process id was 277 and it exited with return code 10.
olwm: Warning: An invalid pixmap was named as an icon pixmap

I assume only the last line is of interest.  Does anyone know what this means?
And, of more interest, how to specify a valid icon pixmap?  We're using
VMS 5.4-3, MultiNet 3.1D, DECwindows 2.0.  I don't know about the SUN. 

Thanks for any help,
Dave
--------------
Dave Greenwood                   Internet: Greenwoodde@ORNL.GOV
Oak Ridge National Lab           Bitnet:   Greenwoodde%ORNL.GOV@LBL.BITNET
PO Box 2009, MS 8073             Voicenet: (615) 574-0711
Oak Ridge TN 37831-8073          %STD-W-DISCLAIMER, I don't speak for nobody
From: JIM@ANACIN.NSC.VCU.EDU (Brainwave Surfer)
Newsgroups: comp.os.vms
Subject: Old DEC stuff to good home.
Date: 10 Nov 92 18:43:47 GMT
Distribution: world
Organization: The Internet

I have two Rainbow 100's and 2 Pro 380's, all with some s/w.  Keyboards,
Monitors all there, also, but have not tried them all to see if they work.

Please pick up in Richmond, VA area, and can have entire lot for 150 bucks,
with some documentation, or can break it up.  

Jim Agnew

         /^^^\   \ /   Jim Agnew         | AGNEW@RUBY.VCU.EDU  (Internet)
        /      >  ||   Neurosurgery,     | AGNEW@VCUVAX        (Bitnet)
   /\_/     '   \  /   MCV-VCU           | This disc will self destruct in
 /________________>    Richmond, VA, USA | five seconds.  Good luck, Jim..."
From: petem@sdipl1.sdi.oz.au (Peter J. MASON)
Newsgroups: comp.os.vms
Subject: Re: Need example code for server symbiont (SMB routines)
Date: 10 Nov 92 00:02:58 GMT

dbk@pslu1.psl.wisc.edu (Don Katz) writes:

>I was wondering if anyone has C or Fortran source for a server
>symbiont that they would be willing to share with me. 

It may be a bit distant from what you want, but I could pass you PASCAL
code for a "network file transfer symbiont", written ages ago (VMS 4.2)
at another place of employment. If you get no satisfaction elsewhere
then let me know.

Newsgroups: comp.os.vms
From: gvrod@isuvax.iastate.edu (R Eldridge, VMS FOREVER)
Subject: Re: Software (VAX Fortran) installation problem
Reply-To: gvrod@isuvax.iastate.edu
Organization: Iowa State University, Ames, Iowa
Date: Thu, 5 Nov 1992 15:58:11 GMT

rajar@herky.cs.uiowa.edu (Chandrashekar Rajaraman) writes:
>Hi,
>
>I am fairly new to the VAX/VMS environment, and
>am installing VAX Fortran Version 5.8 using VMSINSTAL.
>I get the following message when I select the option to
>install language and command libraries:
>
>------
>*URGENT* message from user SYSTEM ...
>DCL HELP IN USE. Please exit help NOW. Product installation
>in progress.
>
>1 terminal has been notified.
>------
>
>The installation does not proceed after this.
>
>I cannot figure out how DCL HELP is in use. The installation
>guide does not mention any programs that must not be running
>during installation. 
>
>I have tried performing
>the installation with the system just booted up, but
>that does not help.
>

this usually means that someone else is running HELP when you are
installing FORTRAN. the fact that you are getting the message is
confusing, unless someone else is using the same username as you are,
but then it should say "2 terminals have been notified". very confusing.
i've installed FORTRAN V5.8 without problems.

make sure that only you are logged in to the system and that you are
logged in as SYSTEM. 
___
rod eldridge
vms systems support      | gvrod@isuvax.iastate.edu
iowa state university    | gvrod@isuvax.bitnet
From: micky_wong@vnet.ibm.com (Micky Wong)
Date: Fri, 6 Nov 92 12:16:25 EST
Newsgroups: comp.os.vms
Subject: Need help on Vnews

A netter on soc.culture.china asked me the following question via
E-mail:
"As far as 'kill file concerned', now I am using Vnews on Vax/Vms to
brows news. Could you tell me how to make 'kill file' under my
condition ?"

Since I have no knowledge of DEC's VAX/VMS system, would any netter
who knows how to setup kill-file or to activate mail filters on the
Vnews, please come to aid.

Your help will be much appreciated.

Reply-To: Micky_Wong@vnet.ibm.com
Organization: IBM Canada Laboratory
Disclaimer: This posting represents the poster's views, not those of IBM
News-Software: Usenet 3.0
X-X-From: Micky_Wong@vnet.ibm.com
X-Spool-Tags: Micky_Wong@vnet.ibm.com
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: VMSMAIL: %MAIL-E-NOTISAM (file organization changed)
Date: 13 Nov 1992 17:08:41 GMT
Organization: HST Wide Field/Planetary Camera
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <1992Nov13.082902.15273@dxcern.cern.ch>, aimar@dxbt00.cern.ch (Alberto Aimar SL/BT tel 2564) writes:
>In article <1durl3INNkrp@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
>
>|>Of course, should you wish to reply to Aimar, you needn't bother.  Our boy
>|>genius has managed to set up a mail forwarding loop for himself.
>
>Come on, I know I haven't set any mail forwarding loop.

Well, when I tried responding to you by e-mail, the message was bounced after
being handed back and forth between two machines about 20 times.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.