HDTenEightyP/NetNews huggingface dataset:
From: murphy@npri6.npri.com (David P. Murphy)
Newsgroups: comp.os.vms
Subject: Re: Editing large files with TPU
Date: 28 Aug 92 17:54:58 GMT
Distribution: world
Organization: NPRI, Alexandria VA

>> Wasn't the record-length limitation to 960 characters lifted (for all
>> practical purposes -- new limit is large) as of VMS version 5.5?
>> 
>>sethg@dcatlas.dot.gov (Seth Grimes)

 >I don't _think_ so...there was nothing in the V5.5, nor the V5.5-1,
 >release notes that refers to lifting this restriction...
 >
 >fairfield@slacvx.slac.stanford.edu (Dr. Kenneth H. Fairfield)

i just read, wrote, and just generally edited a file with lines up to
4000 bytes long in version V02-006 of TPU, linked 12-OCT-1991.
i am running VMS V5.5.

ok
dpm
-- 
murphy@npri6.npri.com 602 Cameron St. Alexandria, VA 22314 (703) 683-9090

              When every one is dead the Great Game is finished.  Not before.
                              --- Hurree Babu, "Kim"
From: eesb1mm@dct.ac.uk (Info freako)
Newsgroups: comp.os.vms
Subject: Re: Zoo on Unix..
Date: 28 Aug 92 13:27:43 +0100
Organization: Dr. Fish's Answering Machine

In article <01GO1RU47QR6001DMZ@EKU.BITNET>, STUBRBEE@EKU.BITNET (Oooooooops) writes:
> Dudes,
>      I have been trying to get zoo to compile on our UN*X system.  Apparently
> my make file doens't work.  Could someone explain to me how to compile it and
> send me the make file?   Thanx...
> 
> David Barbee

Well, a friend of mine downloaded the sources from uk.ac.lancaster.pd-software

(which has now changed to uk.ac.hensa.micros) on Janet. I think it has a 

BITNET address but I don't know it... I think it was in the mainframe/tools/z...

It had sources for VAX/VMS, Un.X and ibm PC in the files....

     Hope this helps,

	Malcolm.

	P.S There is also a site at Kent university (uk.ac.hensa.unix I *think*)

	which might also contain the files....
--------

Malcolm Macarthur

	Janet: eesb1mm@uk.ac.dct.cc.vaxb
	Internet: s0mm@exnet.co.uk
From: leichter@lrw.com (Jerry Leichter)
Newsgroups: comp.os.vms
Subject: RE: Linking C programs
Date: 28 Aug 92 15:46:09 GMT
Organization: The Internet


	I have seen many postings on this list regarding linking a C object
	against the sharable image, VAXCTRL.EXE. This involves creating a
	linker option file (.OPT), and specifying this option file on the
	command line when linking to create a much smaller executable image. I
	have used this method for some time now, and it works quite well...

	A short time ago, I saw a response to one of these questions which
	pointed out where the REAL problem is, and why we need to do this in
	the first place.  It was pointed out that since the CRTL wasn't in the
	sharable image library, IMAGELIB.OLB, and therefore, we must provide a
	pointer to it implicitly. Well, why not put it there?? To do this,
	just add it to the image library:
 
	        $ SET DEF SYS$LIBRARY
	        $ LIB/SHARE IMAGELIB SYS$SHARE:VAXCRTL.EXE
 
	Now you have to remove the logical name pointer to VAXCRTL.OLB. Do a
	SH LOG LNK* <enter>. There will be a reference that looks something
	like this:
 
	        LNK$LIBRARY = "SYS$LIBRARY:VAXCRTL"
 
	If you have curses and/or g_float support, it may be LNK$LIBRARY_1 or
	_2.  be sure to DEASS/SYS the logical name that points to VAXCRTL.
	Also, you might also wish to remove/comment out the entry which
	defines it in the startup command procedure so that if the system is
	rebooted, users will not go back to linking against the regular
	library.

	If anyone out there might have any comments or warnings on this please
	let me know... As yet, I have not seen/heard of any problems by doing
	this...

Periodically, someone proposes this.  Usually, the posting proposing it asks
why, after doing this, C programs fail to work properly.

There is an old (day-1) bug in the Linker which makes this fail to work.
I can never remember the exact bug, but the effect it has is that references
to stdin and friends are not resolved consistently:  You end up with multiple
instances of the pre-declared data structures defining the standard input and
output files.  I/O to them will not work correctly.

As part of the changeover for the VAX C RTL to the DEC C RTL, I gather this
bug was supposed to finally be fixed.  I seem to recall a vague reference to
a bug fix that sounded as if it could be related in the V5.5 Release Notes.
So it's POSSIBLE that this will work in recent VMS versions.  It definitely
will NOT work in older VMS versions.

Of course, the other problem - that you will then have names like "OPEN"
defined in your system-wide copy of IMAGELIB, which may cause all sorts of
amusing problems for programmers in other languages - remains.  DEC C will
presumably do things like:

	#define fopen DECC$FOPEN

in stdio.h.  ANSI requires that the name "fopen" be meaningful even if stdio.h
isn't included (though such use is discouraged), or the programmer adds

	#undef fopen

so the problem won't go away completely.  My guess would be that, if you
insist on playing games like this, you'll be stuck with searching some
other library explicitly.
							-- Jerry

Newsgroups: comp.os.vms
From: marshall@force.ssd.lmsc.lockheed.com (Bob Marshall)
Subject: Copying passwords between UAFs
Reply-To: marshall@force.ssd.lmsc.lockheed.com
Organization: LMSC, Sunnyvale, California
Date: Thu, 27 Aug 92 18:49:49 GMT

Does anyone have a utility that will copy encrypted passwords between
two different UAFs? I have a program that I wrote which will do it as
long as the usernames in both UAFs match, but it won't work in the case
where the usernames do not match. I vaguely remember that the encrypted
password is a combination of the username and the plaintext password,
so I can understand why it doesn't work when the usernames don't match.

=============================================================================
Bob Marshall                     \\     "It ain't age
Lockheed Missiles & Space Co.     \\     That makes me look this way
Sunnyvale, CA                      \\    It ain't the years, boys,
marshall@force.ssd.lmsc.lockheed.com\\   It's the miles"
"I tell the truth 'cept when I lie"  \\     - Chris LeDoux
=============================================================================
From: ARNOLD@ARNOLD.COM ("Stephen L. Arnold")
Newsgroups: comp.os.vms
Subject: Re: Looking for DEC PathWorks Lists/Discussion
Date: 2 Sep 92 15:18:10 GMT
Article-I.D.: Arnold.01GOB05HMHUW8WVYXH
Distribution: world
Organization: Arnold Consulting

Frank (Chip) Dyer <DYERFDF@HSDWL.UTC.COM> writes:
> Forgive me if this is the wrong place to ask.
Not too bad, if you only ask once.

> I am looking for an interest group of DEC's PathWorks (for DOS).  The only
> list I have found (a LISTSERV, PCSA-L) does not seem to be around anymore.
Pony up $75 to join DECUServe for a year and check out the PATHWORKS
notes conference.  It's a rather different model for group communication
than an Internet or LISTSERV list, but much less noise and much faster
response to questions.  You must log into DECUServe to participate, but
free access is available via Tymnet (at least currently) and
Internet/TELNET, or you can dial direct to Massachusetts.

Regards,
"Steve"   Stephen L. Arnold, Ph.D., Principal, Arnold Consulting
Address   4138 Iroquois Drive, Madison, Wisconsin  53711-3701  U.S.A.
Telephone +1 (608) 238-7835             Pager     +1 (608) 277-4053
Internet   Arnold@Arnold.Com            BITNET     ARNOLD@WISCPSL
Newsgroups: comp.os.vms
From: churchwell@vms.ocom.okstate.edu (Kimberly B. Churchwell)
Subject: Re: Time recommendations for DAT cleaning
Organization: OSU College of Osteopathic Medicine
Date: Fri, 28 Aug 1992 15:06:45 GMT

In article <01GO2J049GZ4A0UN5W@TAYLORU>, PGMOGUSH%TAYLORU@UICVM.UIC.EDU
(Peggy Mogush) writes:
> Does anyone have any recommendations for amount of hours/data between cleanings
> for Winchester 4mm FlashDAT drives? I checked the hardware users guide for
> recommendations on tapes to use but none for how often.

Dunno about Winchester drives, but the manual for our Hewlett-Packard
35480A DAT drive recommends cleaning the heads after each 25 hours of
use, or when the "caution" signal shows.
-- 
Kimberly B. Churchwell, Prog./Analyst, Okla. State U.  | TANSTAAFL, but
Osteopathic College--churchwell@vms.ocom.okstate.edu   | even so, I never
BIX--kchurchwell  AOL--KChurchwel  CIS--72170,1552     | quit hoping.
From: mark@infocomm.com
Newsgroups: comp.os.vms
Subject: Re: TZ30 performance
Date: 30 Aug 92 22:21:57 PDT
Organization: INFO COMM - Computer Consulting, Redwood City, Ca

In article <1992Aug27.122358.89@chmeds.ac.nz>, gordon@chmeds.ac.nz writes:
> We are in the midst of replacing a microVAX II with a VAXstation 4000-60.
> That's a real win in general, but tape performance isn't.
> 
> The microVAX has a TK-50, and on a straight backup of sys$help gets 18.5 
> disk blocks/second to tape.  The VAXstation has a TZ30 and only gets 4.1 disk 
> blocks/second to tape.  
> 
>[...]
> Has anyone else measured the performance of a TZ30? Has anyone got better
> performance? With the present perormance an image backup will become more than 
> a week's work!

I have indeed measured the performance, of the TZ30 vs the TK50.  They are
actually essentially the same performance with the TZ30 about 5% faster at
transferring raw data.  Both of these devices are capable of BLAZING along 
at an amaizing 40-45kb/sec using large block sizes (32kb).

Here are some approximate numbers for the same test on various other tape
devices:

	Device:		Max Measured Transfer Rate:
	=============================================
	TK50		42kb/sec
	TZ30		44kb/sec
	Exabyte 8200	245kb/sec
	Exabyte 8500	495kb/sec
	DAT		179kb/sec
	
Depending on the file structure of your disk volumes, (how many small files,
etc.) VMS BACKUP is capable of driving all of these devices at reasonably 
close to full speed on a VAXstation 4000-60.  

I just tested this claim and used a Satellite VS3100-38 to backup the files 
from SYS$HELP on my system disk (VS4000-60 boot node) to a TZ30.  

Total File Data backed up:	25.95mb
Tape Block Size:		32kb
Backup Time:			769 seconds
Total Data Written:		29.16mb
 (including backup overhead data)
File Data Transfer Rate:	34.55kb/sec
Raw Data Transfer Rate:		38.82kb/sec

Achieving the maximal backup throughput is completely dependent on the proper 
combination of account AND SYSGEN parameters AND available system memory 
resources.

--
Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, Ca
PHONE:	(415)369-9366	UUCP:  decwrl!infopiz!mark or uunet!lupine!infopiz!mark
DOMAIN:	mark@infocomm.com
From: murphy@npri6.npri.com (David P. Murphy)
Newsgroups: comp.os.vms
Subject: Re: Unknown error message - SS$_NOMORENODES
Date: 23 Aug 92 21:58:28 GMT
Organization: NPRI, Alexandria VA


>The problem is occuring on a MicroVax II, under VMS 5.4-2 and a DELQA
>interface.  The VMS error  message SS$_NOMORENODES is being returned
>from a QIO operation to the Ethernet device.  I cannot find out what
>this error is.  I've checked the VMS 5.4 documentation, and some of
>the VMS 5.5 documentation, to no avail.
>
>Henry W. Miller (HENRYM@SACUSR.MP.USBR.GOV)

i believe you are referring to SS$_NOMORENODE, the "-W-" condition
returned to the caller by sys$getsyi() and sys$getsyiw() when
"wildcarding" the nodeid.  in other words, a function is looping
calls to getsyi() to find all the nodes in the cluster, and this
value has been returned as a signal that all nodes have been examined:
time to break out of the loop.

ok
dpm
-- 
murphy@npri6.npri.com 602 Cameron St. Alexandria, VA 22314 (703) 683-9090

              When every one is dead the Great Game is finished.  Not before.
                              --- Hurree Babu, "Kim"
From: olin@cheme.tn.cornell.edu (Steve Thompson)
Newsgroups: comp.os.vms
Subject: Re: DEC File Optimizer for VMS
Date: 3 Sep 92 14:07:40 GMT
Reply-To: olin@cheme.tn.cornell.edu
Organization: Cornell University School of Chemical Engineering

In article <1992Sep2.165101.1869@bvc.edu>, kraftjoel@bvc.edu writes:
>	I was wondering if there are many people using the DEC File
>	Optimizer for VMS??  Since it was added to CSLG last spring,
>	we need to take a serious look at it.  I am personally a bit
>	(okay a LOT) weary of release of version 1.0A (especially
>	from DEC).  I would appreciate hearing the goods and the bads.

I have been running it on a VAX 4000 model 500 with about 11GB disk in
production mode for about 3 months. No problems at all - set it and
forget it.

Steve

---------------------------------------------------------------------------
Steve Thompson, System Mangler   Internet: thompson@cheme.tn.cornell.edu
School of Chemical Engineering   Bitnet:   thompson@crnlchme
Olin Hall, Cornell University    Phone:    (607) 255 5573
Ithaca NY 14853
---------------------------------------------------------------------------
From: dragon@NSCVAX.PRINCETON.EDU (Mighty Firebreather)
Newsgroups: comp.os.vms
Subject: RE: VMSINSTALLable and those .A files HELP!!!
Date: 1 Sep 92 15:58:42 GMT
Distribution: world
Organization: The Internet


	Matthew Harttree <Harttree@vax1.elon.edu> writes:

>AW geez ....  Here I go makin a fool of myself again....
>
>If this is on the FAQ I'm blind. but....
>
>I keep getting requests to install certain software from various
>ftp sites.  They come in various formats.  Most I can handle with ease.
>Backup, Make, etc...
>
>I notice that many call for VMSINSTALL and are distributed in a format as
>follows:
>
>program.A
>program.B
>program.C
>
>I know INSTALL well (I think) and I believe VMSINSTALL and INSTALL
>are two different things.  We are running cmu and MX and they came in
>this format.  My boss did the installation and I cant find a trace of
>the product.
>
>How does one setup and install such packages that come in the above format??
>If it is a public domain program, could someone provide me with a FTP
>pointer.
>

	You install these things the same way that you install VMS upgrades 
and layered products:

$ @SYS$UPDATE:VMSINSTAL 'product' 'load_device'

e.g. to install CMU-TEK TCP/IP V6.6 from magnetic tape you would say:

$ @SYS$UPDATE:VMSINSTAL CMUTEK066 MUA0:

	If you omit the parameters, you will be prompted.  This usually 
must be done from the SYSTEM account.

	The instructions for the product you are installing usually include 
the proper command line to use.


*************************************************************************
*                                                                       *
*                        Here, there be dragons!                        *
*                      dragon@nscvax.princeton.edu                      *
*                                                                       *
*                                                Richard B. Gilbert     *
*************************************************************************
From: marshall@force.ssd.lmsc.lockheed.com (Bob Marshall)
Newsgroups: comp.os.vms
Subject: Re: VMSINSTALLable and those .A files HELP!!!
Date: 31 Aug 92 15:59:05 GMT
Reply-To: marshall@force.ssd.lmsc.lockheed.com
Organization: LMSC, Sunnyvale, California

In article <1992Aug31.105359.20797@lester.appstate.edu>, HARTTREE@vax1.elon.edu (Matthew Harttree) writes:
>I keep getting requests to install certain software from various
>ftp sites.  They come in various formats.  Most I can handle with ease.
>Backup, Make, etc... 
>
>I notice that many call for VMSINSTALL and are distributed in a format as
>follows:
>
>program.A
>program.B
>program.C
>
>I know INSTALL well (I think) and I believe VMSINSTALL and INSTALL 
>are two different things.  We are running cmu and MX and they came in 
>this format.  My boss did the installation and I cant find a trace of 
>the product.  

Are you saying you can't find VMSINSTALL? I'm not surprised, since there
is only one "L" in VMSINSTAL. Look in SYS$UPDATE:VMSINSTAL.COM. This is
a leftover from pre-VMS 4.0 days, when the filename portion of the
filespec was limited to nine characters.

=============================================================================
Bob Marshall                     \\     "It ain't age
Lockheed Missiles & Space Co.     \\     That makes me look this way
Sunnyvale, CA                      \\    It ain't the years, boys,
marshall@force.ssd.lmsc.lockheed.com\\   It's the miles"
"I tell the truth 'cept when I lie"  \\     - Chris LeDoux
=============================================================================
Newsgroups: comp.os.vms
From: robert@cpvax.lonestar.org
Newsgroups: comp.os.vms
Subject: Re: Undocumented MAIL qualifier
Date: 26 Aug 92 20:57:20 GMT
Organization: Texas Utilities, Glen Rose TX

> n8846069@henson.cc.wwu.edu (Barry) writes:
>> There is an undocumented MAIL qualifier I have seen
>> people use to extract an image file from a message.
>> EXTRACT/FOREIGN is the usage they used.

The command isn't exactly undocumented.  It is documented in DEC's X.25 product.

Or Maybe it's documented in a file cabinet of an unused lavatory with the
sign "Beware of the Wombat". 8-}

-- 
-------------------------------------------------------------------------
Robert Eden    817-897-0491                             Glen Rose, TX
Comanche Peak Steam Electric Station            robert@cpvax.lonestar.org
               ^^^^^^^^^^^^^^^^^^^^^ politicese for a nuke plant
-------------------------------------------------------------------------
From: hornlo@okra.millsaps.edu (Larry Horn)
Newsgroups: comp.os.vms
Subject: Re: Undocumented MAIL qualifiers
Date: 29 Aug 92 10:40:43 GMT
Article-I.D.: okra.0095FCE6.07E1BD80.6679
Distribution: world
Organization: The Internet

>> >but *please* don't ask for automatic naming during extraction [in MAIL]
[...]
>> Well, this is something that you get with the BACKUP command (and of course

Since I've received several comments saying essentially the same thing,
here's why I sent what I sent.  My first gut reaction is not "how convenient
for me" but "how much will this make my telephone ring" <grin>.

I did reply to the original post rather quickly, but I still feel there's a
conceptual difference even though technically they have the same effect.
Perhaps it's because I'm exposed to a high turnover of naive users (students)
who more often that not get themselves in trouble with things like this.

The *primary* purpose of BACKUP is to move (in a broad sense) collections
of files around.  Anyone using BACKUP comes to it with the mindset (I hope)
that he/she has to be careful about duplicating file names; after all,
BACKUP is a FILE manipulation utility.  That's what you *expect* of it.

But MAIL is *primarily* a MESSAGE manipulation utility and I don't think
that users typically conceive of messages as having names.  Having a
message with a name would be an unusual, unexpected case.

I guess the first thing I imagined was someone doing

	$mail/fore login.com "@dis_lists:students"/subj="Extract ME!"

where the LOGIN.COM was something like "$DEL *.*;*".

Maybe I'm warped; maybe I shouldn't read and reply to mail after being
up too long (like now).  Oh, well.

- ---------------------------------- signed: 29-AUG-1992 05:38 C*T (USA) --- -
    Larry Horn / Millsaps College / Jackson, MS / hornlo@okra.millsaps.edu
- -------------------------------------------------------------------------- -
From: gleeve@galaxy.dnet
Newsgroups: comp.os.vms
Subject: image accounting
Date: 2 Sep 92 12:42:22 GMT
Distribution: world
Organization: The Internet

If disk space used by image accounting is an issue, I might suggest
that recording people's input keystrokes might provide an alternative
that would be seen as acceptable, given that no charge is being made
for cpu use etc.
   RAXCO sells a package that can do this with reasonably low overhead.
I don't know if Supervisor Series can or not,but I have also modified
photo in the past to run silently from sylogin to do this sort of
recording. It is of course FAR more efficient to record only input 
keystrokes than both input and output...disk tends to fill very
slowly, save on terminals where asynchronous communication exists. On
those you generally want to turn these things off while they are 
actually transmitting.
   Another alternative is periodic opening of new accounting files
and compressing the old ones (or removing them to tape if they don't
HAVE to be online). The recently released ZIP package (which I have
and will ensure gets into the tools section of the next sig tapes)
does a nice job of packaging VMS files up, tightly compressed yet fairly
easily accessed.)
   I also have found that adding sections to the sys$system searchlist
that live on other disks is fairly useful, just so the pieces moved
off the boot disk are not needed till after boot. Compilers, word
processors, and the like are good candidates.
   If the chief concern is security, though, few techniques of monitoring
give the bang for the buck that recording input keystrokes do.
Glenn Everhart
(Everhart@raxco.com)

Newsgroups: comp.os.vms
From: ORAKEL@rzmain.rz.uni-ulm.de (Framstag)
Subject: Re: Looking for Newsreader software
Organization: University of Ulm, Germany
Date: Sat, 29 Aug 1992 12:02:38 GMT
X-News-Reader: VMS NEWS 1.23

In <fogarty-280892120537@126.10.4.104> fogarty@erevax.com writes:

> 	I am looking for a friendly version of a Newsreader to install on an 8350
> running 5.4 in a non-windowing enviornment. I am also looking for a verion
> compatible with Motif if possible. I can interface from my MAC but I want
> to provide the general user community access from the VAX. Thanks for any
> hints as to quality and location.

since your adress seems not to be valid I post me answer here rather than a
direct mail to you:


<<< RCPT To:<fogarty@erevax.com>
<<< DATA
550 erevax.com.tcp... 550 Host unknown
550 <fogarty@erevax.com>... Host unknown


VMS NEWS (*) by Bernd Onasch

is a VAX/VMS fullscreen news-reader (nntp-client) with tcp/ip-support
for CMU/tek, Excelan (EXOS), MultiNet (TGV), Process Software, UCX and
Wollongong (TWG).

DECnet support for ANUnews is implemented too, but not tested so far.

Some features are:

     - full screen modus with up/down scrolling

     - all functions are accessible with cursor-
       and keypad keys as well with typed commands
       in DCL style

     - programmable (keypad-) function key

     - integrated help and mail facility

     - idiot proofed syntax-checking POST mechanism

     - EDT, TPU/EVE and LSE support (callable)

VMS NEWS needs a DEC-VT terminal (or compatible) for interactive usage,
but runs also in batchmodus.

VMS NEWS comes as a selfextracting, selfcompiling (needs a VAX C Compiler,
V2.4-3.1) DCL-share-file. It is not necessary to install it with special
priviledges.

VMS NEWS runs very stable, we haven't got any crash within the last months
(thousends of calls).

VMS NEWS is obtainable via anonymous ftp:

ftpvms.ira.uka.de       canonical name = irav1.ira.uka.de
irav1.ira.uka.de        inet address = 129.13.10.1

     FTP$DIR:[000000.NEWS]NEWS120.ZIP

or directly via mail from the author.


(*) VMS stands for Very Mad Students Software Productions


Remark:

I'm NOT the author, only his PR agent - Frams Commercial Agency Inc. ;-)

For technical questions about VMS NEWS please mail directly to
Bernd Onasch:
	        ONASCH@ira.uka.de 
		ONASCH@informatik.uni-karlsruhe.de


\  Ulli 'Framstag' Horlacher    \   psi%0262450502601::rzmain::orakel    \
 \  Student consultant VAX/VMS and networks    \  orakel@dulruu51.bitnet  \
  \  Rechenzentrum  Universitaet Ulm  Germany   \     orakel@rz.uni-ulm.de \
   \  "With mainframes you just can do nonsense, with PCs not even that."   \