HDTenEightyP/NetNews huggingface dataset:
From: system@PIB1.PHYSIK.UNI-BONN.DE (Peter Kobe)
Newsgroups: comp.os.vms
Subject: NEWSRDR
Date: 22 Dec 92 08:42:07 GMT
Distribution: world
Organization: The Internet
X-Unparsable-Date: Tue, 22 Dec 1992 09:39:12 MEZ

W. Moeller (moeller@GWDGV1.DNET.GWDG.DE)
wrote:
> I'm have posted VMS_UNSHARE.COM to vmsnet.sources.

 So I connected to our NEWS Server unsing  M.Madison's NEWSRDR 
and got a mismatch. 
The first announcement is 316 new articles found.
Selecting the vmsnet.sources group gives no article
What did I do wrong or what is wron with the server? 
Here is a Photo of that session:

%PHOTO-I-STARTED, PHOTO V1.0-003, recording started 22-DEC-1992 09:20:42
PIB3_$ ipnews
IP-News Reader on PIB1 Up and Running
%NEWS-I-CONNECTING, connecting to NNTP server news.rhrz.uni-bonn.de
200 news NNTP server version 1.5.11 (10 February 1991) ready at Tue Dec 22 08:21
:48 1992 (posting ok).
%NEWS-I-UPDATING, locating unread articles; please wait...

      3 new articles in newsgroup vmsnet.alpha
      5 new articles in newsgroup vmsnet.networks.tcp-ip.cmu-tek
    316 new articles in newsgroup vmsnet.sources


News> group vmsnet.sources
%NEWS-I-GRPSET, current newsgroup now vmsnet.sources, articles [233,0], 0 unseen
News>
%PHOTO-I-STOPPED, recording terminated 22-DEC-1992 09:21:33 PHOTO.LOG;1

Thanks for any hint

Peter
=====================================================================
Peter Kobe			Internet: system@pib1.physik.uni-bonn.de
Physikalisches Institut	          HEPNET: 13562::SYSTEM
Universitaet Bonn	             Tel: (49) 228 73 3222
D 53 Bonn		             FAX: (49) 228 73 7869 
Nussallee 12
From: FZC@CU.NIH.GOV ("Kevin Mitnick")
Newsgroups: comp.os.vms
Subject: Request for sources
Date: 23 Dec 92 02:44:47 GMT
Distribution: world
Organization: The Internet

Can someone E-Mail me the sources to VMS?

Thanks, Kevin
From: burress@twics.co.jp (Tim Burress)
Newsgroups: comp.os.vms
Subject: Re: Alternative callable editors in MAIL?
Date: 29 Dec 92 06:18:47 GMT
Organization: TWICS, Tokyo, Japan

Many, many thanks to everyone who helped me with this problem, especially Bruce
Wright and Dave Cantor.  The procedure was exactly as Bruce specified in his
messages, including the required installation of the shareable image in order to
accomodate DECUS UUCP.

One thing I noticed was that it is apparently a requirement that a transfer
vector be specified, at least for software written in VAX-C.  Without it I
consistently got the "Key not found in tree" error, no matter what I named
the routine, but perhaps this has to do with the way C defines the attributes
of its routines?

Anyway, it works fine, and Dave Cantor's hint about defining MAIL$EDIT as
CALLABLE_XYZ saved me a lot of trouble, since I can set that up for the users
as part of the captive login.  Otherwise I'd be reminding people to use the
SET EDITOR command for years...

-- 

Tim Burress                                     Internet:  burress@twics.co.jp
TWICS Co., Ltd.
1-21 Yotsuya, Shinjuku-ku, Tokyo 160 Japan
From: epp@mala.bc.ca (Lorne Epp)
Newsgroups: comp.os.vms
Subject: Re: TPU:  proc to delete trailing spaces
Date: 23 Dec 92 20:49:01 -0700
Organization: Malaspina College

In article <1992Dec23.062138.3034@hubcap.clemson.edu>, rsimms@hubcap.clemson.edu (Robert Simms) writes:
> Together with a friend, I came up with the following procedure
> that I keep in my tpu$command file:
> 
> procedure eve_erase_trailing_spaces
>    local count, kill_range;
>    count := 0;
>    loop exitif 0 = search_quietly ( (span(" ")@ kill_range) & line_end,
> 						forward);
>         position (kill_range);
>         erase (kill_range);
>         count := count +1;
>    endloop;
>    if count = 0
>    then
>       message('No trailing spaces found.');
>    else
>       message('Trailing spaces removed from '+str(count)+' lines.');
>    endif;
> endprocedure;
> 

You could have got away with:

    procedure eve_erase_trailing_spaces
	eve$trim_buffer( current_buffer );
    endprocedure
    
----------------------------------------------------------------------
Lorne Epp                                               epp@mala.bc.ca
From: gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546)
Newsgroups: comp.os.vms
Subject: Re: VAX c
Date: 26 Dec 92 04:08:00 GMT
Reply-To: gavron@ACES.COM
Organization: ACES Consulting Inc.
News-Software: VAX/VMS VNEWS 1.4-b1

In article <Bzt6EF.Est@dale.cts.com>, glippert@dale.cts.com (George Lippert) writes...
#Ehud Gavron 602-570-2000 x. 2546 (gavron@spades.aces.com) wrote:
#> In article <1992Dec24.173709.16437@mailer.cc.fsu.edu>, cliff@evax9.eng.fsu.edu writes...
#> >Is there a way to get VAX C to flush the VMS file buffers? 
#>
#> 	fflush(stream)
# 
#Not according to DEC Support.  After trying this, and having it clearly not
#work, DEC Support confirmed that fflush() only flushes to the RMS buffers -
#NOT to the actual device.
# 
#So how do I make sure that the buffer gets onto disk? (in my case), I asked.
#They told me that there is an "unsupported and undocumented" function that I
#could call.  Thanks, but no thanks, I said.

I didn't realize I'd have to hold your hand through this.  You
wanted it out of VAX C, I showed you how.  Now you want it out
of RMS and you won't even look up SYS$FLUSH.  Shame on you.

#--
#George A. Lippert           work:          glippert@dale.cts.com
#Titan Satellite Systems     home: zucchini!glippert@dale.cts.com (NeXTmail ok)
#San Diego, CA                                            
#------------------------------------------------------------------------------

P.S. If you can't figure out how to go from a stream ID (FILE *) to
     a FAB, please play with the listings just a tad more.

Ehud

--
Ehud Gavron        (EG76)     
gavron@vesta.sunquest.com
Yow!  I just went below the poverty line!
From: pyron@skndiv.dseg.ti.com (Dillon Pyron)
Subject: Re: What is XPDRIVER for?
Reply-To: pyron@skndiv.dseg.ti.com
Organization: TI/DSEG VAX Support
Date: Wed, 30 Dec 1992 19:02:36 GMT


In article <1hs7k7INNnqs@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
>In article <1992Dec29.185622.1038@cmkrnl.com>, jeh@cmkrnl.com writes:
>>You can see what's on the Q-bus by
>>
>>	$ run sys$system:sysgen
>>	SYSGEN> SHOW/UNIBUS
>>	SYSGEN> SHOW/CONFIG
>
>WHOA!  WHOA!  TIME-OUT!  WAIT A MINUTE!  The SHOW/UNIBUS command is
>*DANGEROUS*.  It talks to all the devices on the bus in a way that's
>uncoordinated with anything else VMS is doing with them.  To quote from the
>online help for SYSGEN:
>
>SHOW
>
>  /UNIBUS
>
>   /UNIBUS
>
>    Tests every word in UNIBUS I/O space and returns a list of addresses
>    that respond and the value that was read. Note that this command is
>    useful for debugging UNIBUS autoconfigure problems, but it is not
>                                                        -------------
>    recommended for use on a running system. All unibus adapters are the
>    ----------------------------------------
>    default, /ADAPTER=adapter-spec can be  specified.  Requires  CMKRNL
>    privilege.
>
>(emphasis mine).  Using this command can crash your system.  Wait 'til you're
>ready to reboot before using it, if at all possible.

The problem here is that I've seen so many Field Circus guys do this that even
I think that "Well, maybe it's safe nowadays".

Kids, don't try this at home, and don't let the "pros" try it either  :-)
--
Dillon Pyron                      | The opinions expressed are those of the
TI/DSEG Lewisville VAX Support    | sender unless otherwise stated.
(214)462-3556 (when I'm here)     |
(214)492-4656 (when I'm home)     |"Pacts with the devil are not legally
pyron@skndiv.dseg.ti.com          |binding!"
PADI DM-54909                     |-Friar Tuck   _Robin Hood:The Hooded Man_

Newsgroups: comp.os.vms
From: billb@crpmks.uucp (Bill Bochnik (Info Systems))
Subject: Re: How to prevent the DEC login screen on VMS workstation?
Reply-To: billb@crpmks.UUCP (Bill Bochnik (Info Systems))
Organization: Ciba-Geigy Corporation
Date: Thu, 31 Dec 1992 00:37:17 GMT

In article <1992Dec30.114610.4960@tc.cornell.edu> olin@vger.cheme.cornell.edu writes:
>In article <2347@sousa.tay.dec.com>, anderson@funyet.enet.dec.com (Paul Anderson) writes:
>>You can eliminate the big "digital" logo by defining the logical name
>>DECW$LOGIN_BACKGROUND to be the name of a command procedure that will display
>>an image on the background behind the login box.
>>
>>For example, DEFINE /SYSTEM DECW$LOGIN_BACKGROUND "SYS$MANAGER:BACKGROUND.COM"
>>
>>BACKGROUND.COM could contain an XV command, for example.  If it does nothing
>>useful, I would imagine you would get a plain background but the big logo would
>>still be gone.
>
>Pray tell me how to define DECW$DISPLAY when you're at an X-terminal and
>not a workstation. I had heard that the translation of SYS$ERROR held
>the display device, but this seems not to be the case (VMS 5.5-1).
>

When you have the login prompt (username/password) on the screen, you are 
executing a program on a Vax in your network.  The DEFine has to be done on 
that Vax.
-- 
Bill Bochnik			| It's hard to be a James Bond in an Abbott
Systems Analyst 		|	and Costello world.
Ciba-Geigy Corporation		| Signed and sealed, they deliver oblivion.
philabs!crpmks!billb		| It's worse than that, he's dead Jim.
From: leichter@lrw.com (Jerry Leichter)
Newsgroups: comp.os.vms
Subject: re: C pointer question
Date: 27 Dec 92 21:02:43 GMT
Distribution: world
Organization: The Internet

Sigh.  In an earlier flamey message, I wrote that the two pieces of code,

	void foo(char a[])
	{
	bar(a);
	}

	and

	void foo(char a[])
	{
	bar(&a);
	}

were identical.  Wrong, Leichter, wrong.  If you're going to flame, just
flame, don't throw in a quick remark without thinking it through (which is
unlikely in the midst of flaming.)

As Neil Readwin has already pointed out to me in a private message (and I'm
sure plenty more people will be pointing it out, too), in fact, the function
"void foo(char a[])" is indistiguishable from "void foo(char *a)" - one of C's
more annoying little hacks.  Despite the appearance of the declaration, "a"
ends up typed as "pointer to char", NOT as "array of char".  (ANSI Standard,
Section 3.7.1 (under Semantics):  "A decla- ration of a parameter as 'array of
type' shall be adjusted to 'pointer to type'.")  So the two definitions ARE
different:  The first passes "a"'s value (foo's argument, of type "char *");
the second passes a pointer to "a" itself (of type "char **").

As to the original program that this arose in, the author wrote:

	bar wants a char *, foo is passed a char *.

If bar wants a char *, then the first piece of code is correct.  The second
passes a char **.  Since it was the second (type-incorrect) code that was
alleged to actually work, my opinion of the level of programming involved here
remains unchanged.

(For those who like chapter and verse:  My original comment that, if "a"
really has type "array of T", then "a" is not an lvalue, is correct according
to the ANSI Standard, Section 3.2.2.1:  "Except when it is the operand of the
sizeof operator or the unary & operator ... an lvalue that has type 'array of
type' is converted to an expression that has type 'pointer to type' ... [that]
is not an lvalue."  The exception for unary "&" allows "a" and "&a" to be
almost equivalent.  (Technically, the first has type "pointer to T" while the
second has type "pointer to array of T".  The values are the same, but the
difference in type will be visible as a different scaling value if you add an
integer to these pointers.  This is actually a change from K&R C, where the
exception did not "officially" exist, and where "&a" if allowed was taken to
mean EXACTLY the same thing as "a" itself.))
							-- Jerry
From: CADS_COLE@GALLUA.BITNET (Kevin Cole; Washington DC)
Newsgroups: comp.os.vms
Subject: Re: UCX TELNET name.name.name portnumber -- How?
Date: 21 Dec 92 20:44:13 GMT
Organization: Gallaudet Research Institute

In article <&821H8lfjb@atlantis.psu.edu>, BJJ@ECL.PSU.EDU (Bryan J Jensen)
writes: 
> In <1992Dec21.092203.1@gallua> CADS_COLE@GALLUA.BITNET writes:
> 
>> I notice that I cannot type:
>> 
>>        telnet name.name.name portnumber
>> 
>> (It complains that it can't find a host record.)  But I can type:
>> 
>>        telnet name.name.name
>> and    telnet number.number.number.number portnumber
> 
> What you, as a user, can do is use the last form you listed.
> 
> What your system manager can do is install a newer version of UCX,
> this bug was fixed by one of the later UCX 1.3 patches.

Thanks.  We're running 1.3 at the moment.  As for using the last format I have 
shown, it works, but GOPHER doesn't receive a numeric address when you select a
TELNET-type menu entry, which is why I wanted to know if there was a way to add
code to GOPHER that would translate the thing, or perhaps force some extra goo
onto the command line that GOPHER generates, that would solve the problem. 
-- 

 ========== U.S. Mail =============================== E-Mail =================
 Kevin Cole      <Flatline>           |  Bitnet: CADS_COLE@GALLUA.BITNET
 Gallaudet Research Institute  (GRI)  |  Internet: KJCOLE@GALLUX.GALLAUDET.EDU
 Washington, D.C.  20002-3625         |  UUCP: ...!psuvax!gallua.bitnet!kjcole
 (202) 651-5575  x4592                |  The WELL:   kjcole
Newsgroups: comp.os.vms
From: cantor@star.enet.dec.com (Dave Cantor)
Subject: Re: Alternative callable editors in MAIL?
Organization: Digital Equipment Corporation
Date: Sat, 26 Dec 1992 18:55:03 GMT



In article <1992Dec25.234751.5910@ais.com>, bruce@ais.com (Bruce C. Wright) writes...
>In article <34147@twics.co.jp>, burress@twics.co.jp (Tim Burress) writes:
[...]
>> So my question is whether there is a procedure for installing a different
>> callable editor, and having MAIL use that one instead of EDT.  I know it's a
>> longshot, but the alternative is using the callable mail routines to write my
>> own mailer, and it's not how I planned to spend my holiday.
> 
>You can very often set things up so that almost any editor can be used as
>a callable editor in MAIL.  For example, suppose you have a locally-written
>editor named XYZ -- what you need to do to make it callable from MAIL is:
[...]
>    2)  Have a procedure named XYZ$EDIT in the sharable image.  The
>	arguments should look like the callable EDT interface routine
>	named EDT$EDIT, although I think you can just get by with 2
>	arguments for callable MAIL (input_file, output_file).  Note
>	that the arguments are passed by descriptor!!  This procedure
>	should start up the editor on input_file and write it to
>	output_file when done.  You'll probably want to do the image
>	`properly' with a transfer vector and so forth, this often 
>	makes things simpler to deal with when things change.

If the editor is named XYZ, then the entry point needs to be named
XYZ$XYZ, not XYZ$EDIT.   (The entry points for some popular editors
are TPU$TPU, LSE$LSE, and TECO$TECO.)

>
[...]
>    5)	Within MAIL, do a SET EDITOR XYZ (and DON'T set the MAIL$EDIT
>	logical name, that will override the SET EDITOR command when MAIL
>	starts up and the users will need to do an explicit SET EDITOR
>	every time they get into MAIL).

You can also use

    $ DEFINE MAIL$EDIT CALLABLE_XYZ

>[...]

-- --
 Dave C.                          cantor@star.enet.dec.com
 Digital Equipment Corp., Nashua, NH  03062, USA
  The views expressed herein are my own, except where attributed to 
  someone else.  They are neither the opinion of, nor the responsibility 
  of, Digital Equipment Corporation.
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.os.vms
Subject: Re: Getting rid of SMB_SECURITY once and for all ?
Date: 23 Dec 92 18:36:47 GMT
Organization: St. Peter's College, US

In article <1h8f4bINNehh@manuel.anu.edu.au>, bear@nuc.anu.edu.au (Bernhard Fabricius) writes:
> (basically because there are too many users who re-direct DECW$USER_DEFAULTS
> from SYS$LOGIN, so it would take too long!), I was wondering if there is a way
> to tell the server not to check "Security" at all, ie let all connections in,
> or possible have a list of "secure hosts" (like the nodes in our cluster, for
> crying out loud!) which can always get in regardless of the contents of the
> user's SMB_SECURITY file ?

  I think you want SYS$MANAGER:DECW$SERVER_ACCESS_ALLOWED.DAT. You list the
usual security triples in there (like * * *). Of course, note that this means
that I could put up a fake login box on your workstation from the comfort of
my own home 8-), so you might want to restrict it to specified hosts/users.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
From: gezelter@rlgsc.com
Newsgroups: comp.os.vms
Subject: Re: VAX c
Date: 26 Dec 92 15:00:30 GMT
Organization: Robert Gezelter Software Consultant, Flushing, NY

In article <Bzt6EF.Est@dale.cts.com>, glippert@dale.cts.com (George Lippert) writes:
> Ehud Gavron 602-570-2000 x. 2546 (gavron@spades.aces.com) wrote:
>> In article <1992Dec24.173709.16437@mailer.cc.fsu.edu>, cliff@evax9.eng.fsu.edu writes...
>> >Is there a way to get VAX C to flush the VMS file buffers? 
>>
>> 	fflush(stream)
> 
> Not according to DEC Support.  After trying this, and having it clearly not
> work, DEC Support confirmed that fflush() only flushes to the RMS buffers -
> NOT to the actual device.
> 
> So how do I make sure that the buffer gets onto disk? (in my case), I asked.
> They told me that there is an "unsupported and undocumented" function that I
> could call.  Thanks, but no thanks, I said.
> 
> --
> George A. Lippert           work:          glippert@dale.cts.com
> Titan Satellite Systems     home: zucchini!glippert@dale.cts.com (NeXTmail ok)
> San Diego, CA                                            
> ------------------------------------------------------------------------------
-- 
George,
 
I will admit that the following solution is a bit of hitting a 
small ant hill with a large explosive, but ...
 
When the time expires, close the file. Then re-open it in append 
mode. This will ensure that all of your buffers are flushed out 
to the disk.
 
If I remember correctly from the original post, the application 
in question is not a high bandwidth application. The periodic 
close/reopen cycle should not appreciably increase your CPU 
consumption.
 
I hope that the above is helpful. If I have been unclear, or if I 
can be of further assistance, please feel free to contact me via 
Email or phone.
 
- Bob
+--------------------------------------------------------------------------+
| Robert "Bob" Gezelter                       E-Mail:  gezelter@rlgsc.com  |
| Robert Gezelter Software Consultant         Voice:   +1 718 463 1079     |
| 35-20 167th Street, Suite 215               Fax:       (on Request)      |
| Flushing, New York  11358-1731                                           |
| United States of America                                                 |
+--------------------------------------------------------------------------+
From: DWING@UH01.Colorado.EDU ("Leave the cone man alone.")
Newsgroups: comp.os.vms
Subject: Re: HELP!!! Security problem for gurus.
Date: 28 Dec 92 17:21:17 GMT
Distribution: world
Organization: The Internet

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

>Yup.  READALL is a terribly misnamed priv.  IHNSHO, DEC should've called the
>priv BACKUP, since that's what it's for.  

You know what would happen then:

  Programmer:  I need to create a detached process.
  System Mgr:  Well, then you need DETACH privilege.  Let me give it to you.
  Programmer:  I also need to use BACKUP to copy some files to tape.
  System Mgr:  Well, then you need BACKUP privilege.  Let me give it to you.

(For less-astute readers, DETACH is *not* needed to create a detached process.)

-Dan Wing, dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet (DGW11)
 Systems Administrator, University Hospital, Denver

Newsgroups: comp.os.vms
From: fogelinc@Cyanamid.COM (Carl Fogelin)
Subject: Re: Detecting directory of invoked .com
Reply-To: fogelinc@Cyanamid.COM
Organization: American Cyanamid Company
Date: Wed, 23 Dec 1992 18:16:31 GMT

>In <1992Dec23.160636.27010@tigger.jvnc.net> fogelinc@nmr1.Cyanamid.COM writes:
>
>> In a DCL program, I would like to be able to determine what directory the
>> invoked .com file is located in.  I seem to remember a similar thread about
>> 6 - 8 months ago, so I hope someone remembers the solution.
>
>Try:   f$parse(f$env("procedure"),,,"directory")

This was exactly what I needed.  I'd like to thank:

    Richard Critz              critz@star.enet.dec.com
    Malcolm Dunnett            dunnett@mala.bc.ca
    Ulli 'Framstag' Horlacher  orakel@rz.uni-ulm.de

for their immediate help.

Ok Carl and Ehud, feel free to vilify me.  I should have seen this in TFM or $HELP.

On a related note, is there any way from within an executable to determine the
name of the DCL command program which invoked said executable?  If it makes a
difference, my executable was programmed in C.  Again thanks.
     
---------------------------------------------------------------------------
 Carl Fogelin (fogelincc@cyanamid.com)     "All opinions are strictly mine" 
   "Sushi!   That's what my ex-wife called me.  Cold fish." -- Blade Runner
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: MOVE for Vms anywhere ?
Date: 21 Dec 1992 08:11:54 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <1992Dec21.063118.11928@cnplss5.cnps.philips.nl>, NL0242T@NLZCL (Oscar van Eijk) writes:
>> >> The original question was not well-posed, since the querant didn't bother to
>> >> tell us exactly what this "MOVE" command was supposed to do.
>> >
>> >I doubt that; till now you're the only one who didn't seem to understand that.
>> 
>> You think so?  Then why did someone recommend "RENAME" when what the querant
>> wanted was "BACKUP"?  You really ought to read more of the thread before
>> mouthing off.
>
>I don't just think so, I'm sure.

In that case, you just don't know what the hell you're talking about.

>What I was looking for was a MOVE command that
>works like a Unix 'move' command.

Then one has to ask "Which version of Unix are you talking about?"

>If a Unix 'move' command doesn't move accross
>devices;

And under System-V, it didn't.

>then RENAME was what I was looking for. Since I didn't know that, 
>BACKUP/DELETE is more useful,

So how were we to know whether or not you knew that Unix isn't an operating
system, but is, in fact, an entire suite of mutually incompatible operating
systems?

>but everybody (almost) understood I was refering
>to the Unix 'move' command. What else did you expect?

WHICH Unix "mv" (not move) command?  Under some systems (e.g., System-V), mv
works like RENAME;  under others, it does something similar to (though not the
same as) what you can get from BACKUP.

Now, we had to guess as to which feature was more important to you:
	1)  Can work across filesystems; or
	2)  Leaves at most ONE file resident on two filesystems if you interrupt
	    it in the middle.
Since some people (other than myself) suggested RENAME, while others suggested
BACKUP, it's pretty obvious that your question was rather ambiguous.
--------------------------------------------------------------------------------
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.