HDTenEightyP/NetNews huggingface dataset:
From: sysrick@orion.spd.louisville.edu (Rick McTeague)
Newsgroups: comp.os.vms
Subject: Need: help with RZ23 disk drives
Date: 8 Apr 92 15:10:00 GMT
Organization: University of Louisville


 am attempting to use some DEC RZ23 disk drives with a system from "another
vendor". I'm having problems which I believe to be related to the fact that
the drives don't spin up on power-up - they wait for a start-drive command
on the SCSI bus, and my other system is, I guess, not doing that.

Any ideas on how I can get these drives (I have 7 of them currently unused)
to spin up on power on? And yes, I know the reason for not doing this...

Also, has anyone else out there had a problem with these drives becoming
*noisy*, like they have a bearing going bad in them? I talked to a DEC engineer
in their storage systems group last year and she said she hadn't heard of this
happening, except for an early batch of drives. I must have them all, because
I have 4 or 5 (out of 17) which make more noise than they should.

Thanks in advance,
Rick
-- 

Rick McTeague
Electrical Engineering Department, Speed Scientific School
University of Louisville, Louisville, KY 40292
(502) 588-7020

Internet: ramcte01@starbase.spd.louisville.edu

Disclaimer: I'm a stand-up comedian; if anyone takes me seriously, I'm
            doing something wrong!
-- 

Rick McTeague
Electrical Engineering Department, Speed Scientific School
University of Louisville, Louisville, KY 40292
(502) 588-7020

Internet: ramcte01@starbase.spd.louisville.edu

Disclaimer: I'm a stand-up comedian; if anyone takes me seriously, I'm
            doing something wrong!
From: dafj@aud2.aud.auc.dk
Newsgroups: comp.os.vms
Subject: Re: SWAPFILE needed anymore?
Date: 8 Apr 92 08:53:19 GMT
Article-I.D.: aud2.1992Apr8.085319.1
Organization: Aalborg University Center, Denmark

In article <635@pacvax.UUCP>, eaton@pacvax.pacersoft.com (Mark W. Eaton) writes:
> In article <1992Mar31.213851.16424@socrates.umd.edu>, mike@socrates.umd.edu (Mike Santangelo (UNIX/VMS Sysmgr)) writes:
>> 
>> There was a recent thread regarding the apparent lack of use
>> by VMS 5.x of the SWAPFILE.SYS.  
> 
> VMS has for some time now run quite happily without a SWAPFILE.SYS.  It uses
> PAGEFILE.SYS for both paging and swapping.  I don't recall how long it's been
> like this (V5.0?) but it's certainly not new.
> 
It seens like your system never has had to swap anything since deletion-day.
It's true that PAGEFILE.SYS can be used for both paging and swapping, but
the allocation-methods are quite different. I don't have the guts to delete
my SWAPFILE.SYS because I know, that being a univercity, we could suddenly
run into a massive use of memory, when all of the students discover that
their reports are due tomorrow :-). If we have to swap something I like
a special file for that purpose, because PAGEFILE.SYS is allways badly
fragmented.


> Rename your SWAPFILE.SYS to something innocuous, reboot, then delete it. You 
> can then use the extra disk space to enlarge PAGEFILE.SYS.
> 
See the above.

-- 
Just my opinion.

Have fun
--------------------------------------------------------------------------------
Flemming Jensen                               UUCP      : dafj@aud1.aud.auc.dk
University of Aalborg (AUD)                   Internet  : dafj@aud.auc.dk
Fredrik Bajersvej 5                           Telephone : + 45 9815 8522 - 4032
9220 Aalborg 0                                Telefax   : + 45 9815 6970
DENMARK                                       X.25      : 238302121245:dafj
--------------------------------------------------------------------------------
Newsgroups: comp.os.vms
From: gowen@walt.CS.MsState.Edu (Lon Gowen)
Subject: MX & UCX Question.
Organization: Mississippi State Univ.
Date: Mon, 13 Apr 1992 16:39:19 GMT

I have a hopefully simple question concerning MX V3.1.  I just installed MX
on my VAXstation 4000/60 running VMS V5.5, and my TCP/IP package is
UCX V1.3 (don't laugh too much).  My question is do I need some other
special software in order to use MX.  I tried doing the familiar MAIL
using SMTP, but MAIL says that I need SYS$LIBRARY:SMTP_MAILSHR.EXE, which
doesn't exist.  This may be a FAQ, but I would still appreciate any hints
as to what I am doing wrong.

Thanks in advance!

Lon Gowen, PhD
gowen@cs.msstate.edu
From: oberman@ptavv.llnl.gov
Newsgroups: comp.os.vms
Subject: Re: FLIGHT for VMS ftp site ?
Date: 7 Apr 92 21:46:41 GMT

In article <00958B0C.148DE640@convax.iar.nrc.ca>, system@convax.iar.nrc.ca (Jim.Jordan) writes:
> Newsgroup:						April-6-92
> 
> 	The latest DECUS library SW catalog lists an X-Windows FLIGHT Simulation
> package for VMS (V00533). Does anyone have this available for anonymous ftp
> or know of a site where this is available ?
> 
> 	This software would be of interest to some of the aeronautical types
> here at the Flight Research Lab.
 
I will probably live to regret this, but it is available from icaen.llnl.gov in
the [.FLIGHT] directory. It's a saveset, so either grab it in BINARY and
reblock it with FILE or something similar or get it with MultiNet which does
everything for you. TWG and others may also support this standard. See if mode
VMS is available on your FTP. It's fixed length, 32256 byte blocks.

Have fun, everyone.

R. Kevin Oberman			Lawrence Livermore National Laboratory
Internet: oberman1@llnl.gov		(510) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.
Newsgroups: comp.os.vms
From: mdchaney@bronze.ucs.indiana.edu (M Darrin Chaney)
Subject: Re: UCX TCP/IP
Organization: Indiana University
Date: Thu, 16 Apr 92 17:29:07 GMT

In article <1992Apr14.161923.7110@eco.twg.com> reece@eco.twg.com (Reece R. Pollack) writes:
>
>In article <A3319E3EE040357A@SNYMORVA.BITNET>, DREWWE@snymorva.BITNET (Bill Drew -- Serials Librarian) writes:
>|>Can anyone tell me why UCX TCP/IP does not have a TN3270 capability?
>|>It seems riduculous for someone to write TCP/IP protocol software
>|>without implementing TN3270.

Maybe it's just me, but I don't find this to be anywhere near as
ridiculous as a vendor who sells machines that require a specific type
of terminal to be usable.

And, no, DEC machines _don't_ require a VTxxx to be usable.  I've used
an LA36 before.  Do _that_ on an IBM.

>|>There are a large number of sites that
>|>can only be reached using TN3270.

Maybe they should change vendors...

>|>I have noquarrels with the telnet
>|>and ftp portions.
>
>UCX V1.3 is lacking in *lots* of areas, and TN3270 is only one of them. Why?
>The usual reasons...too small a staff, not enough time, high maintenance
>demands. V2.0, which is supposed to include a broader set of applications
>is at least a year late.
>
>There are a number of complete TCP/IP implementations for VMS, including
>the one we sell. You may want to consider switching vendors.

I'm not going to say much here, except that while UCX lacks in a few
areas, most of the holes have been plugged by free software.  You can
get most of the missing things if you look around long enough.  To me,
the major one is SMTP mail, which is provided by Matt Madison's MX
mailer.

If you consider the price difference, it may be worth it to you to get
UCX.  For my machine, UCX was free, so it was worth the price :)  I've
managed to collect the other pieces that I needed, so it's a fine
product to me.

	Darrin
-- 

mdchaney@iubacs mdchaney@bronze.ucs.indiana.edu mdchaney@rose.ucs.indiana.edu

"It's a marvel of vegetable containment..."
From: moeller@gwdgv1.dnet.gwdg.de ("GWDGV1::MOELLER")
Newsgroups: comp.os.vms
Subject: RE: Accounting and vector processors
Date: 6 Apr 92 18:46:24 GMT
Distribution: world
Organization: The Internet

Ed Wilts <Ed.Wilts@BCSystems.Gov.BC.CA> writes:
> We will soon be adding a couple of vector processors to our 9420.  What I don'
t
> know about them yet is to tell which processes have used them (and for how
> long) and which ones didn't.  Is their a record in the accounting file or
> anything useful like that?

There is one "vector time" accounting field, which essentially counts
the number of CPU quanta during which the vector processor has been accessed.

Unfortunately, the hardware does not measure the amount of vector utilization,
so a program that does a few vector instructions now and then can't be told
from one that's using the vector processor efficiently. For billing purposes,
this might not matter because "it's the user's fault" when a program is
vectorized poorly.

Wolfgang J. Moeller, GWDG, D-3400 Goettingen, F.R.Germany | Disclaimer ...
PSI%(0262)45050352008::MOELLER      Phone: +49 551 201516 | No claim intended!
Internet: moeller@gwdgv1.dnet.gwdg.de   | This space intentionally left blank.
From: julian@dxcern.cern.ch (Julian Bunn)
Newsgroups: comp.os.vms
Subject: Re: Possible SYSMAN trojan horse (VMS)
Date: 10 Apr 92 11:36:12 GMT
Organization: CERN European Laboratory for Particle Physics

In article <1992Apr8.163357.5983@dayton.saic.com> ake@dayton.saic.com (Earle Ake) writes:
>
>	This warning came across my desk today from our security people.  I
>have typed it in verbatim.
>
>
>SUBJ: COMPUTER VIRUS WARNING
>1.  A POTENTIAL TROJAN HORSE EXISTS WHICH INFECTS THE SYSMAN.EXE
>UTILITY ON VAX/VMS SYSTEMS.
>2.  THE SYSMAN.EXE TROJAN HORSE WILL PROVIDE A KNOWLEDGEABLE USER
>WITH A BACK DOOR INTO THE VMS OPERATING SYSTEM AND INCREASE USER'S
>PRIVILEGES.
>3.  DETECTION METHODS:
>          A. CHECK FOR A LIBRARY ENTRY -
>SYSDOLLAR SIGNLIBRARY:OBJ.EXE
>          B. THE LENGTH OF SYSDOLLAR SIGNSYSTEM:SYSMAN.EXE EQUALS
>             166 BLOCKS
>          C. EXECUTE THE FOLLOWING VMS COMMAND:
>       DOLLAR SIGNANALYZE/IMAGE SYSDOLLAR SIGNSYSTEM:SYSMAN.EXE
>                 CHECK THE IMAGE IDENTIFICATION INFORMATION SECTION.
>                 MAKE SURE FIELD IMAGE NAME EQUALS SYSMAN, NOT VA6
>4.  NOTE:  ANY OF THE ABOVE COULD INDICATE THE PRESENSE OF THE SYSMAN
>           TROJAN HORSE.
>

  This SYSMAN Trojan was discovered on around a dozen VAXes at CERN
in November 1991. At that time the CERT were given full details. Other
VAXes in Europe were also affected. A very powerful check, as mentioned
above, is a SYSMAN image size of 166 blocks, and a file called OBJ.EXE
in SYS$LIBRARY. The rogue SYSMAN will copy itself to any system which
is the target of a "set environment/node" command (which succeeds).

  It certainly allows any non-privileged user to gain full system
privileges, if that user knows the "trick" (which I won't detail on the
net!).

  I'm surprised at the bizarre route the information Earle includes
must have taken to arrive in such a garbled form, but it looks like
a perverted version of advice we originally circulated to HEP system
managers at the time.

Julian Bunn /CERN
From: DMC@ADMIN.DRAKE.EDU (Dennis M. Conroy, Dial Center)
Newsgroups: comp.os.vms
Subject: Question on VAX SMS/CMS/MMS/DECram/Disk Striping
Date: 9 Apr 92 16:18:59 GMT
Article-I.D.: ADMIN.920409111900.106a
Organization: The Internet


    We are considering implementing some or all of the following
    DEC Packages:
    1) VAX Storage Library System (SLS)
    2) VAXset Package (or a sub-set)
        A. VAX LSE/SCA (Language Sensitive Editor/Source Anal)
        B. VAX PCA (Performance and Coverage Analyzer)
        C. VAX DEC/CMS (Code Management System)
        D. VAX DEC/MMS (Module Management System)
        E. VAX DEC/Test Manager
    3) DECram
    4) VAX Disk Striping Driver
    5) VAX Software Project Manager

    Any advice/opinion/caution/etc. you might offer on these items
    to help in our decision would be appreciated.  Of special interest
    is the Storage Library System. As usual, this has been around forever
    and is now a priority, so time is of the essence!.  Please forward
    editorials direct to me and I will summarize to the net.

DMC@ADMIN.DRAKE.EDU
Dennis M. Conroy, VAX System Manager
Drake University Administrative Computing
515-271-2802
2407 Carpenter, Des Moines, Ia  50311
From: bethge@wums.wustl.edu
Newsgroups: comp.os.vms
Subject: DECwindows screen blanker 
Date: 6 Apr 92 11:20:57 -0600
Organization: Washington University School of Medicine

How does one unblank the screen after the screen saver has blanked it? As
I interpret the FM, XResetScreenSaver should do the trick, but it doesn't
work for me. Neither does XForceScreenSaver or XSetScreenSaver. What am I
missing? I am running VMS V5.4 DECwindows on a VAXstation 2000.

Paul Bethge
Bethge@WUMS.wustl.edu
From: ARNE@ko.hhs.dk (Arne Vajhxj)
Newsgroups: comp.os.vms
Subject: Re: I need help using F$GETQUI
Date: 17 Apr 92 15:13:00 GMT
Organization: The Internet

> I have a question using F$GETQUI.  I would like to check all the jobs in a
> specific queue to make sure all the jobs which should be there are present.
> In the examples for F$GETQUI, there is a good example of pulling out all of
> the job names in all of the queues.
> 
> My question is:  Is there a way to look at all of the job names on
> JUST ONE QUEUE?  As I understand the manual (yes, I've been reading it :-),
> to use the ALL_JOBS flag, I must use the DISPLAY_JOB function.  To use
> DISPLAY_JOB, I must use DISPLAY_QUEUE with a wildcard.  Thus, it appears
> to me that it can not be done.  BUT, since this is the first time I've
> used F$GETQUI, there is the outside chance that I could be wrong (GASP!).

Yes and no. You do need to make a DISPLAY_QUEUE with a wildcard, but you
do not need to have a wildcard in the queue-name, because there exist
a special wildcard-flag. See the small example below:

$ set process/priv=oper
$ stop/queue/reset 'p1'
$ tmp=f$getqui("")
$ tmp=f$getqui("DISPLAY_QUEUE","QUEUE_NAME",p1,"WILDCARD")
$ loop:
$    entry=f$getqui("DISPLAY_JOB","ENTRY_NUMBER",,"ALL_JOBS")
$    if entry .eqs. "" then goto endloop
$    delete/entry='entry'
$    goto loop
$ endloop:
$ start/queue 'p1'
$ exit

Hope this helps.

                                                          Arne Vajhxj

Arne Vajhxj                             local DECNET:  KO::ARNE
Computer Department                     PSI:           PSI%238310013040::ARNE
Business School of Southern Denmark     Internet:      ARNE@KO.HHS.DK
From: goathunter@wkuvx1.bitnet
Newsgroups: comp.os.vms
Subject: Re: New Zip and UnZip for VMS soon....
Date: 15 Apr 92 07:19:47 CDT
Distribution: world
Organization: Western Kentucky University, Bowling Green, KY

In article <FA4356C7E000B988@SCU.BITNET>, ABPATEL@SCUACC.SCU.EDU (Mickey Patel) writes:
> 
> 	Can anyone tell  me as to when is the New ZIP and UNZIP is to be
> released? I heard that it was supposed to be released in Mid_April.
> If someone has already got it could you let me know as to how?

UnZip v4.2 was released about three weeks ago.  Zip v2.0 was supposed
to be released the first week of April, but that has been delayed.  I
still plan to package the two together and post them to vmsnet.sources
(as well as make them available from my file server) as soon as the
new version of Zip is released.

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251
From: harvey@indyvax.iupui.edu
Newsgroups: comp.os.vms
Subject: Re: SUMMARY: How to SET FORWARD to multiple users
Date: 16 Apr 92 14:16:40 -0500

In article <KENW.92Apr15125956@skyler.arc.ab.ca>, kenw@skyler.arc.ab.ca (Ken Wallewein) writes:
> In article <1992Apr14.230239.28787@cco.caltech.edu> carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
>> In article <KENW.92Apr13161603@skyler.arc.ab.ca>, kenw@skyler.arc.ab.ca (Ken Wallewein) writes:
	[...Ken's original question about why DEC prohibited mail forwarding
	to a distribution list in VMSmail in VMS 5.0 deleted, and Carl's reply
	explaining why, deleted.]
>
>   Thanks for clearing that up.  I don't recall it being stated clearly at
> the time the functionality was withdrawn.

Nope, I couldn't find any mention of it in the VMS 5.0 Release Notes, nor in
the VMS Mail Utility Manual.  The feature was never documented or supported,
so calling it "withdrawn functionality" is really stretching it a bit...

>                                            In a side message, Ehud has said
> something which seems related.  It involved the difficulty for a sending
> process to determine the exact number of recipients, when forwarding to a
> distribution list is being done on a remote node.
>
>   It doesn't strike me that DEC tried very hard to address the problem in
> any other way; several possibilities come to mind.

The feature was never documented or supported, so why should they?

Patching up the MAIL-11 protocol with a bunch of special features to ensure
delivery to distribution lists doesn't make a lot of sense because there are
already better ways to deal with distribution lists, viz., use MAIL-11 as a
local delivery protocol only and layer store-and-forward and distribution list
support on top of it.

> any other way; several possibilities come to mind.  It almost looks as
> though DEC wanted to push users toward a more expensive product.

Your options range from $0 (get DELIVER from DECUS) up.  It's your pocketbook
and your decision, so please stop whining :-)

> Store-and-forward mailers do this kind of thing routinely.  Is there
> anything inherent in functioning of a synchronous-delivery mailer that
> makes it "hard"?

Yes!  ...drum roll...  Because they _aren't_ store-and-forward!  Let's face
it, if you want _reliable_ delivery to a large distribution list in a large
network, the user doesn't want to sit there waiting at their terminal for a
week until, say, nsfnet-relay.ac.uk decides to accept the mail for the last
user in the list.  Store-and-forward is the only practical way to reliably
deliver mail in large networks.

> /kenw
> --
> /kenw
>
> Ken Wallewein                                                   A L B E R T A
> kenw@noah.arc.ab.ca                                           R E S E A R C H
> (403)297-2660                                                   C O U N C I L
--
James Harvey
harvey@iupui.edu (preferred) or harvey@indiana.edu
Remember, there are only 2,816 shopping days left until January 1st, 2000!
From: reece@eco.twg.com (Reece R. Pollack)
Newsgroups: comp.os.vms
Subject: Re: Foreign commands
Date: 14 Apr 92 00:43:22 GMT
Reply-To: reece@eco.twg.com (Reece R. Pollack)
Organization: The Wollongong Group (East Coast Operations)


In article <1992Apr8.031218.6990@nsisrv.gsfc.nasa.gov>, alex@drax (Alex Measday) writes:
|>Like another poster, we've got a lot of C programs we've ported from UNIX
|>to VMS.  We figured out that we needed to define the programs as foreign
|>commands in order to pass command line arguments to them.  Our next questions
|>are:
|>
|>    - Is there a way to run a foreign command as a detached process?

To use the foreign command interface, you need a DCL CLI (Command Language
Interpreter). You create a detached process with a CLI by using the following
DCL command:

	$ RUN/DETACHED SYS$SYSTEM:LOGINOUT.EXE -
	     /INPUT=file.com -
	     /OUTPUT=file.log

The 'file.com' command procedure will be executed after the login.com procedure.
It should contain the definition of the foreign command, and its invocation.


|>    - If a program is linked "/DEBUG", is it possible to run the program
|>      via a foreign command without having it come up in the debugger?

Nope. Relink the program without the /DEBUG option.

--
Reece R. Pollack
Senior Software Engineer
The Wollongong Group, Inc.
From: braun@phy.duke.edu (Richard Braun)
Newsgroups: comp.os.vms
Subject: vms scripts?
Date: 8 Apr 92 22:18:06 GMT

Can anybody help with a problem I have?
At the lab I work at we use a microvax 3200 for data acquisition
and we would like to have a script of all screen input/output.
In the past this was done by running everything from a DECwriter
terminal; which made nice big piles of paper.  It would be better
just to write it all to a file (which would make searches easier
and take up less room.)  However the only option I have found so
far is SET HOST/LOG which doesn't quite cut it since to stop the
script file and look at it I would have to kill all my DAQ 
subprocesses.

I have run out of help from the local VAXperts, so if anyone knows
of such a utility...  I think that the UNIX 'script' command does
exactly what I have outlined; is there a VMS analog?


Richard T. Braun 
braun@phy.duke.edu        Just another struggling grad student.
-- 
  ==========================================================================
	Richard T. Braun		               1-(919)-684-8288
	422 TUNL                                      
        Duke University Dept. of Physics 	      braun@tunl.duke.edu       
Newsgroups: comp.os.vms
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Subject: Re: Pagefile Fragmented
Reply-To: carl@SOL1.GPS.CALTECH.EDU
Organization: HST Wide Field/Planetary Camera
Date: Thu, 16 Apr 1992 08:17:45 GMT

In article <1992Apr15.120707.492@hccwmv2>, david@hccwmv2 writes:
>We have a MicroVAX II with 9Meg of memory running VMS 5.4-3.  We have
>three large pagefiles which are mostly free and yet very fragmented.
>Here are the stats:
>
>Total   Reserve   Free    Holes   Largest
>20000   10087     15107   374     735
>34992   18902     24059   996     702
>12392    5747      7880   242     1102

Large pagefiles?  LARGE pagefiles? What yo've got are NOT "large" page files. 
They are SMALL pagefiles.  On my system, the DEFAULT page file quota is 34816
pages. That means that your whole set of pagefiles has enough space for TWO
processes, on my system.  What's the page file quota on your system?  Please
note that you're using ~50% of each of your page files.  These files are most
definitely NOT "large" by any reasonable defintion of the term.

>We were also previously getting a "Pagefile Critically Fragmented" 
>message.
>
>Could this fragmentation be caused by the Proactive Memory Reclaimation
>feature?  Is there any thing we can do to prevent this fragmentation?

Try making bigger pagefiles.  For a start, try doubling the size of each.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXes 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.
Xref: sparky comp.os.vms:8349 comp.sys.dec:2571
From: brodie@fps.mcw.edu
Newsgroups: comp.os.vms,comp.sys.dec
Subject: CONDIST discrepencies in media!
Date: 14 Apr 92 23:43:35 CST
Organization: Medical College of Wisconsin,  Milwaukee, WI

I have a nasty gripe about CONDIST  (DEC, are you listening?   I need
this one to go to the engineers!).


My current issue of CONDIST has the latest and greatest TSM
(terminal server manager) product--   V1.5.   [just released
a few months ago].

On the SAME condist issue (the same DISC, even), is MCCSMS021
(DECmcc site management station software, V2.1).    DECmcc,
includes with it a lot of things, *including* TSM.

Guess what?     DECmcc installs its OWN copy of the TSM
distribution media, and lo and behold, it's V1.4!

Needless to say, this kind of ticks me off.   I had TSM V1.5 running.
I then later installed DECmcc.   Now I gotta go grab TSM *again*
and re-install it because DECmcc isn't keeping up, it seems.

This shows (to me) that there is some lack of communication within
the different groups in DEC that distribute software, especially
when it comes to products that are inter-related.

arghhhhhhhhhhhhhhhhhhhhhhhhh.
-- 
Kent C. Brodie - Sr. Systems Manager		InterNet:  brodie@fps.mcw.edu
Faculty Physicians & Surgeons			uucpNet:   fps.mcw.edu!brodie
Medical College of Wisconsin			MaBellNet: +1 414 266 5080

"Never give money to a preacher who has a better car than you do."  -anonymous