HDTenEightyP/NetNews huggingface dataset:
From: DDIEHL@CARLETON.EDU ("Systems/Network Technician, x4281")
Newsgroups: comp.os.vms
Subject: Re: TT_AccPorNam field remains null on a SHOW USERS output ?
Date: 30 Dec 92 17:24:24 GMT
Distribution: world
Organization: The Internet

Carl@SOL1.GPS.CALTECH.EDU writes
>In article <gurman.725601335@umbra.gsfc.nasa.gov>, 
>gurman@umbra.gsfc.nasa.gov (Joseph B. Gurman) writes:
>>    For what it's worth, logged onto a VMS V5.5-2 system with UCX V2.0
>>via
>>Telnet, my TT_ACCPORNAM is (quotes included as delimiters) "Host:
>>128.183.57.149   Port: 47473" Your mileage may vary.
>
>Hmmm.  47473 doesn't sound much like any port name I've ever heard of. Maybe
>the "47473" is the beginning of the hexadecimal representation of the port
>name?  That'd be GGsomething.  Just a wild-assed guess.

47473 here is the number of the TCP port on the remote host.  While the port on
the local host is, of necessity, port 23 (the Well Known Service port for
telnet), the port on the remote host can be anything between 1024 (the top of
the reserved WKS range) and 2^16.  It is not unusual for port numbers under
certain implementations of TCP/IP to fall high in this range, although
barkochba.gsfc.nasa.gov (the DNS name for 128.183.57.149) is not responding to
queries right now, making it hard to tell which TCP/IP they are running.

				-Dave Diehl
				 Systems/Network Technician
				 Carleton College
From: rtravsky@news.uwyo.edu (Rich Travsky)
Newsgroups: comp.os.vms
Subject: Need VMS Gopher Client
Date: 21 Dec 92 08:26:42 MST
Distribution: world
Organization: Banzai Institute

How many VMS gopher clients are there? I'm aware of and have the
one from boombox at the University of Minnesota. Do any others
exist that I can access?   TIA,

+---------+    Richard Travsky  RTRAVSKY @ CORRAL . UWYO . EDU
|         |    Division of Information Technology
|     U W |    University of Wyoming   (307) 766 - 3663 / 3668
|      *  |    "Wyoming is the capital of Denver." - a tourist
+---------+    "One of those square states." - another tourist
Newsgroups: comp.os.vms
From: singer@rhodes.aero.org
Subject: Sparcstation x-server <> VMS x-clients ?
Organization: The Aerospace Corporation, El Segundo, CA. USA
Date: 24 Dec 92 11:25:56 PST

How do I solve the problem of incompatable fonts 
when using a Sparc station  as the X-server to VMS x-clients?
Newsgroups: comp.os.vms
Subject: Flaming and Such
Date: Mon, 28 Dec 1992 22:58:05 -0500

I for one am getting goddamn sick and tired of listening to all the 
flaming and criticism of people.  If you don't like someone's comments, 
do us *all* a favor and do it through E-Mail.  If someone says something 
totally stupid, *please* don't waste bandwidth to tell people that 
they said something stupid; tell *them*.
 
Maybe you don't like someone asking for a piece of information in 
a way that - in your opinion - they should know the information or 
know how to find it.  It is *not necessarily* a criminal offense for 
someone not to know a critical piece of information related to their 
work in question:
 
- Some people are too busy fighting fires to be able to take the time
  to do the experimentation to find out the answer.  This is known
  as the "when you're up to your ass in alligators it's hard to remember
  that you were supposed to be draining the swamp" theory.
 
- Some people ended up getting positions such as system manager or  
lead programmer *by default* i.e. nobody else wanted it or knew how 
to do the work.
 
- Some people end up having the position of System Manager dumped  
on them because management doesn't want to pay for another warm body 
so the work ends up being added to the list of things to do (and don't 
forget, for many shops, programmers are on salary and are not paid 
for overtime.)

- A lot of people don't have the knowledge or skills to do all the  
work they have to and are undergoing "on the job training" and don't 
know all the tricks yet.  You had to start from scratch, too.  Some 
people haven't even learned how to program a VCR or stop the clock 
from blinking 12:00.  They may be extremely competent managers of 
a department but totally neophyte system managers.
 
Can we have a little less flaming around here?
From: tillman@swdev.si.com ("Brian Tillman, Smiths Industries, VAX Support, x8425")
Newsgroups: comp.os.vms
Subject: RE: Monitor Cluster problem
Date: 21 Dec 92 19:11:47 GMT
Distribution: world
Organization: The Internet

Anders Ostling (anos@ineab.ikea.se) writes:

>I have a problem at a customer site with the cluster setup (at least I
>think so). When I/they are trying to use MONITOR CLUSTER, we get an
>error message saying something like (I'm at home now)
>
>	MONITOR-E-NODEINIERR, error during node initialization

In order to use MONITOR CLUSTER, you need to have the VPM object (object #51) 
installed properly on each cluster node.  You also need enough job logical name 
table space (JTQUOTA in the UAF) to handle one logical name for each cluster 
node.  These logical names are of the form:

DPM$RQST_xxxxxxxx_n

where xxxxxxxx is the PID of the job's main process and n is a count (from 1 to 
N, where N=number of cluster nodes).  The equivalence string for each of these 
logical names is the name of a mailbox through which the monitor data is sent.

If you are low on job name table quota, you won't be able to use MONITOR 
CLUSTER.

-----------------------------+--------------------------------
 Brian Tillman               | Internet: tillman@swdev.si.com
 Smiths Industries, Inc.     |           tillman_brian@si.com
 4141 Eastern Ave., MS129    | Hey, I said this stuff myself.
 Grand Rapids, MI 49518-8727 | My company has no part in it.
-----------------------------+--------------------------------
From: gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546)
Newsgroups: comp.os.vms
Subject: Re: Apending a file at the end of mail.
Date: 21 Dec 92 17:50:00 GMT
Reply-To: gavron@ACES.COM
Organization: ACES Consulting Inc.
News-Software: VAX/VMS VNEWS 1.4-b1

In article <01GSK4HGLSY800036I@MSUS1.MSUS.EDU>, TS117%BSU.DECNET@MSUS1.BITNET (TANDI SUNARTO) writes...
#Ehud,
# 
#Since I am a new user on VAX system, could you please elaborate your
#explanation on how to append a file at the end of mail, for example :
#tell me how to create an initiliazation file, and other stuff.

This is in the FAQ list, so you might want to pick that up for more
details.  (Info on how to get the FAQ list is in the FAQ list ;-)

login.com:
	$ mail == "mail/edit=(send,reply=extract,forward)"
	$ define mail$edit "mycomfiles:mail$edit.com"
	$ define mail_signature sys$login:signature.txt

mycomfiles:mail$edit.com:
	$ def/user sys$input 'f$trnlnm("sys$output")'
	$ edit/edt/output='p2'/command=mycomfiles:mailedtsys.edt 'p1'
	$ exit

mycomfiles:mailedtsys.edt:
	c; er -l 32000(62asc -2l) er ex
	I
	
	^Z
	inc mail_signature
	f beg
	c; IDate sent: ^

#Thanks for any of your help.

	Welcome ;-)

#Tandi
#TS117@VAX1.BEMIDJI.MSUS.EDU

	Ehud

--
Ehud Gavron        (EG76)     
gavron@spades.aces.com

Remember: If your DECUS MC representative won't listen when you speak,
	  he represents himself.  That's time to elect a new one.  
Newsgroups: comp.os.vms
From: larry@eco.twg.com (Lawrence B. Henry III)
Subject: Re: SHOW/UNIBUS (was: What is XPDRIVER for?
Reply-To: larry@eco.twg.com
Organization: The Wollongong Group (East Coast Operations)
Date: Wed, 30 Dec 92 23:31:03 GMT


In article <1992Dec30.100239.1043@cmkrnl.com>, jeh@cmkrnl.com writes:
|>I know about the theoretical problems, but I've been doing 
|>SYSGEN> SHOW/UNIBUS commands on live systems (kinda hard to do it on a dead
|>one, but you know what I mean :-) for something like ten years
|>without a *single* problem.  
|>
|>There are some very old Unibus (and possibly Q-bus) devices that have 
|>"read-once" status bits in their CSRs -- once you read them they clear 
|>themselves -- or with other side effects on read operations.  However even
|>these are not going to be a problem unless SYSGEN's read gets done just ahead
|>of a read that the device's driver needs to do.  Since the driver's read of
|>status bits would normally happen in an interrupt service routine, and since
|>the ISR is going to do everything it has to do before any process-level code
|>(like SHOW/UNIBUS) happens, it really isn't something to lose sleep over.
|>
|>> Using this command can crash your system.  
|>
|>Calling all readers:  Has ANYONE out there ever seen this actually happen?  
|>If so, what devices were on the bus?

Jamie,
	I have seen old DZ-11's (UNIBUS) lose characters when you do 
a show/unibus.. Long time ago on a VAX 11/780 running who knows what 
version of VMS...

-Larry.
From: gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546)
Newsgroups: comp.os.vms
Subject: Re: TT_AccPorNam field remains null on a SHOW USERS output ?
Date: 28 Dec 92 11:08:00 GMT
Reply-To: gavron@ACES.COM
Organization: ACES Consulting Inc.
News-Software: VAX/VMS VNEWS 1.4-b1

In article <1992Dec27.233720.1@woods.ulowell.edu>, sabotkap@woods.ulowell.edu writes...
#From a terminal hardwired to the system (ours is VMS 5.4), the server/port
#field is left blank (see below).  An attempt at using
#f$getdvi("TT","TT_AccPorNam") also returns an empty string.
# 
# Username  Node   Process Name    PID     Terminal
# SABOTKA  CIRRUS  SABOTKA       202060C2  TTA0:
#                                           ^ (hardwired terminal)

Yes, hardwired terminals have no remote access information.  You're
expected to be able to track down the wires :)

#When logged in from a server, or remote system, the server/remote port
#information is sometimes left blank:
# 
# Username  Node   Process Name    PID     Terminal
# SABOTKA  CIRRUS  P. Sabotka    20206DCB  LTA2633: (FOG::NETWORK)
#                                                   ^ (we can't always get this)

I should think not.  LTAnnn should not show a DECnet style address.

#When logged in from a non-hardwired terminal, when during login is the 
#TT_AccPorNam information obtained ?

Before SYLOGIN gets control is enough that you need to know.

#It seems a SET TERMINAL/INQUIRE in our SYLOGIN.COM is responsible for 
#getting this field,

Nope.  If the information is available, it is there long before
SYLOGIN.

#but at other times, an otherwise normal login will not retreive this 
#information.

Coincidence.

#My motives: We have a captive account which we would like to monitor by 
#            writing the login time, and any server/remote port information 
#            to a log file.  
# 
#I apologise for going a bit overboard with info about this problem, but I 
#would rather explain it fully to any potential comp.os.vms.know-it-alls
#who would flame me for lack of information  8-).

Enough information was NOT given.  Show us some REAL examples of a
terminal logged in via DECnet or LAT that has no remote port information.
Until then, just write it out to a file from sylogin.  SET TERM/INQ
in SYLOGIN is a reason for you to be shot, by the way...

#Any help would be appreciated.
#Pete
# 
#-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v^-v-^
#Pete Sabotka, Meteorology Dept.           sabotkap@woods.ulowell.edu
#University of Massachusetts - Lowell      "I lost a buttonhole..." S. Wright
#^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v-^-v^-v-^

	Ehud

--
Ehud Gavron        (EG76)     
gavron@vesta.sunquest.com
.  Like I always say -- nothing can beat the BRATWURST
 here in DUSSELDORF!!
From: MORRIS@PATRICK-PIMS.AF.MIL ("Jay Morris")
Newsgroups: comp.os.vms
Subject: Another note about the 0 message
Date: 22 Dec 92 13:17:00 GMT
Distribution: world
Organization: The Internet

A while back we had a discussion about how to get mail to show message number
0.  I just did it by accident and discovered something else.  While message 0 
shows, you can read the message but not do anything else.  I tried to del, 
extract, and print, and each time it told me I wasn't reading a message.  Since
0 is nothing (oh God, here comes all the mail from the mathematucuans) I guess
I wasn't reading anything.

Trivia for the day.

j
morris@patrick-pims.af.mil
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Reading TK-70 tapes after /REWIND
Date: 22 Dec 1992 06:02:24 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 <01GSKWNYOHZ6004HMW@GW.AGR.CA>, YOUNG@SKRSSA.AGR.CA ("Saskatoon Res. Stn. -- System Manager") writes:
>Hello Info-vax people!
>
>	I have a user that owns a TK-70 tape that has many savesets on it, 
>with the last saveset mistakenly written with the /REWIND qualifier!  He 
>really wants to keep all savesets on the tape.  This was obviously a mistake.  
>
>We know that the first and second original savesets have likely been 
>overwritten, however would like to retrieve the remaining savesets from the 
>tape.  To date I have had no success getting past the first saveset on the 
>tape that was put on using the /REWIND.  There is alot of data left on the 
>tape, and I would really like to be able to get at it.  
>
>Does anyone have any experience with this problem or ideas on a solution? 

First the good news:  I've had experience with that situation.
Now the bad news:  There's no solution (probably).

A "feature" of TK50s is that they won't read past a parity error.  When you
wrote the saveset with the /REWIND qualifier, it put an end-of-file mark at the
end of the saveset.  That end-of-file mark almost certainly overlaps subsequent
data in such a way as to produce a parity error (I don't know why; it's just a
property of TK50s).

Now, in the (extremely unlikely) case where you *DON'T* get a parity error, you
can either write your own program or use a combination of SET MAGTAPE/SKIP and
DUMP to advance past the end-of-volume mark (two successive end-of-file marks)
on the tape, and, if you've mounted the tape /FOREIGN with appropriate values
for /BLOCKSIZE and /RECORDSIZE, you can COPY the rest of the
partially-overwritten saveset to disk, and you can, after using SET MAG/SKIP
and DUMP or equivalent, use BACKUP/NOREWIND to retrieve the data from
subsequent savesets.

E-mail me for details if you *DON'T* get a parity error, or if you need more
detailed instructions for trying to skip past the end-of-volume mark.
--------------------------------------------------------------------------------
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.
From: powers@ELROS.STG.TRW.COM
Newsgroups: comp.os.vms
Subject: RE:  Getting rid of SMB_SECURITY once and for all ?
Date: 31 Dec 92 03:29:00 GMT
Organization: The Internet


Rick Murphy (murphy@dco.dec.com) reminds us:
> The "default" X Window System security scheme on UNIX systems is host-based
> only; anyone logged in to your workstation has access to the display.
> On VMS, the authorization information includes the username of the user.
> Thus, there aren't the same security risks - unless you're sharing your
> password :-)

The whole point about the original post was dismantling the VMS security
scheme from the ground down. I can appreciate a person from DEC reminding
us that VMS and Eunuchs differ in profound ways.  But, the original poster
wanted to make DECwindows/X-windows on a VMS system Eunuchs-like -- totally
unprotected, free-for-all, and anything goes -- contrary to its design.

My point is that DECwindows and DECwindows/Motif have certain security
restrictions.  These restrictions are there for a very good reason, and this is
designed in to the software at the roots.  The restrictions are not annoying
if they are understood.  If someone who is responsible for a computer decides
to deliberately circumvent a basic, fundamental, essential part of a
software design, any software design, without understanding the consequences,
there will be hell to pay for this sooner or later.

Those of us old fuddy-duddies still around know that you can defeat the
design and purpose of any software.  But this is a game best played by
individuals who have very large private bank accounts and who don't need to
hold down a job with an employer.

      Lester Powers
      powers@elros.stg.trw.com
From: ts117@VAX1.BEMIDJI.MSUS.EDU (TANDI SUNARTO)
Newsgroups: comp.os.vms
Subject: Unable to delete file
Date: 24 Dec 92 07:34:02 GMT
Distribution: world
Organization: The Internet

Hi, everybody !

I couldn't delete a file in my directory, eventhough I have set the
protection of owner to RWED, yet I keep reeiving insufficient privelege
or file protection violation message.

What should I do ?

Tandi.
TS117@VAX1.BEMIDJI.MSUS.EDU
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: VAX c
Date: 26 Dec 1992 07:32:26 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 <24DEC199220084219@spades.aces.com>, gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546) writes:
=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? 
=# 
=#I've got a program that reads data in for the tta2: port and then writes it to 
=#a file. The problem is that the data doesn't get written to the file until the 
=#buffer is full, and that may not happen but once every day or two.  
=
=	fflush(stream)
=
=	example:
=	fflush(stdout);

Sorry, Ehud, but this doesn't do what Cliff wants.  It merely flushes the C I/O
RTL buffers, handing the stuff to RMS.  Unfortunately, it doesn't also cause
RMS to issue a $FLUSH, at least not under VMS v5.4-2.
--------------------------------------------------------------------------------
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.
From: DEREK@U.WASHINGTON.EDU
Newsgroups: comp.os.vms
Subject: Re: RE: How to make only one file readable?
Date: 24 Dec 92 01:01:00 GMT
Distribution: world
Organization: The Internet

Arne Vajhxj wrote:

>BTW - I think W:E is the default protection for directories.

Only if you "make it so".  A directory's protection is, by default,
inherited from the parent directory.

-Derek S. Haining
 University Computing Services
 University of Washington
 Seattle, Washington  98195 
 (206) 543-5579

 DEREK@MAX.BITNET
 DEREK@MAX.U.WASHINGTON.EDU

Newsgroups: comp.os.vms
From: eric@sejnet.sunet.se (Eric Thomas)
Subject: Re: Flames......
Reply-To: ERIC@SEARN.SUNET.SE
Organization: SUNET, Stockholm, Sweden
Date: Fri, 1 Jan 1993 09:49:49 GMT

In article <01GSTG6J3RJ6003NZ9@VAXF.COLORADO.EDU>, MARK@AHECAS.Colorado.EDU ("Mark Montanez, System Programmer/Manager, AHEC") writes:
> Is anyone else out there *TIRED* of Mr. Ly*DICK*'s infantile out bursts on this
> list....
> 
> Carl... if you feel the need to cuss someone out... do it via private
> e-mail.... I'm *sure* you know how.... and keep the list for what it's
> for..... solving problems... like *YOU THINK* that you do so well.....

Like most of the people reading this list, I am interested in answers to VMS
questions. I really don't give a damn whether or not Carl has offended you. If
you can't cope with it, you can sign off or use a kill file. Why can't all the
"Carl is so unnice :(((" besserweissers like you follow their own advice and
use private mail to debate this issue? You aren't going to change Carl or to
convince anyone that he is an idiot, and if you think the world cares to hear
that you don't like him, you're the one stroking his ego.

> Prove how smart you are with your solutions... not with you smart-ass flames...
> or better yet... if your *SO* smart... you don't need this list.... so just drop
> out... and leave us to our (in your opinion) easy insignificant problems.....
> 
> Carl... find a good tharapist!!!

Say, why don't you follow your own advice (again) and leave the list to people
who may not be as wise and intelligent as you are but can at least form their
own opinions of the various posters without your distinguished assistance. You
are the one who seems to be in need of a therapist - not to mention a good
spelling checker.

  Eric
From: RICHARDE@UV2.EGLIN.AF.MIL ("Eric F. Richards")
Newsgroups: comp.os.vms
Subject: Dumb question of the week
Date: 22 Dec 92 18:38:00 GMT
Distribution: world
Organization: The Internet

I have a sequential mail file with messages in it that I want to copy/move
to a "normal" ISAM mail file.  Am I missing something obvious in the FM
on how to do this?  It doesn't seem possible short of mailing the messages
back to myself (which keeps me from seeing the original To:, Subj: lines).

If it can't be done with the MAIL user interface, has anyone written
anything using callable MAIL to do this?


Thanks in advance,

Eric F. Richards
Tybrin Corp
Eglin AFB, FL
richarde@eglin.af.mil
904/882-9795


Newsgroups: comp.os.vms
From: brydon@asl.slb.com (Harvey Brydon (918)250-4312)
Subject: Re: Writeback Cache and other trivia
Reply-To: brydon@dsn.SINet.slb.com
Organization: Schlumberger/Anadrill Sugar Land, TX
Date: Wed, 23 Dec 92 14:29:10 GMT

In article <1h9lpjINN1c9@gap.caltech.edu>, in an incredibly polite manner,
carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
>In article <1992Dec22.220607.8221@news.acns.nwu.edu>,
>jweiss@casbah.acns.nwu.edu (Jerry Weiss) writes:
>=During a regular test of my backup procedures (ie: my system crashed and
>=when it came back up a few things didn't work ;-( )
>
>[generally good stuff deleted...]
>
>=Any there other files in VMS (not counting 3rd party software) that
>=require special attention?
>
>For vanilla VMS, at least through v5.4-2, JBCSYSQUE.DAT is the only special
>file, if you're concerned mostly about rebooting and having everything work
>right.  If your real security-conscious, there are a couple of other files
>(OPERATOR.LOG, and at least one AUDIT file) that you've got to worry about.

You left out the ACCOUNTNG.DAT files.  These are never backed up to
incremental backups because they are typically opened at boot time and never
closed.  Since they are continuously open, you can't do the usual stuff with
the file header (anything with "SET FILE", "SET PROT", etc.)  but you can mark
them as modified by renaming them to themselves.  Give this a try.  It is
directly from the incremental backup command procedure I use:

$ set proc /priv=(sysprv,bypass)
$ rename /log sys$sysdevice:[sys*.sysmgr]accountng.dat; *.*;*
$ if f$search("sys$system:jbcsysque.dat") .nes. "" then -
  rename /log sys$system:jbcsysque.dat;* *.*;*
$
$ backup /ignore=interlock ...

_______________________________________________________________
Harvey Brydon         | Internet:   brydon@dsn.SINet.slb.com
Dowell Schlumberger   | P.O.T.S.:   (918)250-4312
 Backup my system disk?  Okay, where's the reverse switch?