HDTenEightyP/NetNews huggingface dataset:
From: lane@duphy4.physics.drexel.edu
Newsgroups: comp.os.vms
Subject: Re: Problems with EXABYTE tape drive
Date: 26 Jan 93 19:05:41 GMT
Distribution: all
Organization: Drexel University Physics

In article <1993Jan26.144354.15050@das.harvard.edu>, chen@speed.uucp (Lilei Chen) writes:
> Yesterday I talked to the dealer who sold us the EXABYTE drives.  First he
> tried to tell me that nothing was wrong with our drives and we were not
> using them properly.  But after I told him how I tracked down the problem
> to the firmware of the drive, he admitted that there was certain version
> of the firmware which has the described sizing problem and the EPROMs in
> our drives are obsolete although the drives were manufactured in April 1991.
> This bogus firmware will report END OF TAPE to the host way before the real
> physical end of tape.  Now comes the outrageous part, he will charge us
> $200 for each update of the firmware!!!  It seems that the next problem
> is inevitable.
> 

I've had much better luck in getting upgrade information by dealing 
directly with exabyte. 

You also need to look at the controller board that is connected to the
exabyte...I found that our CMD SCSI controller board needed a firmware upgrade
to make its error handling "acceptable".  CMD sent out the firmware 
for free ('way to go, CMD!) and helped a lot in getting compatible firmware
on the SCSI controller and exabyte drive.  

Exabyte has a BBS [ 303/442-4323 8b no parity] that has a lot of firmware
and other technical info.  From what was posted on it, it looks like there
are folks out there who "log on" to their exabyte drives and download data
from from them ;-)

Look on your drive for firmware version numbers...there should be a sticker
that has model #, serial # and versions.  The following information is for
EXB-8200, check with Exabyte for the 8500.

From the date you give it sounds like you could have MXPROM 2618 and SVPROM
C034. The most recent MXPROM I have listed here is 2640 (92.03.05) which
"includes minor fixes and feature enhancements"  The SVPROM C034 should be
current (both of these as of this past summer). 

Exabyte was selling firmware upgrade kits for $125. 

But before you upgrade, I *strongly* suggest you contact whoever made your
SCSI interface card, and see which firmware versions they work with. 
-- 

 Drexel University       \V                     --Chuck Lane
----------------->--------*------------<--------lane@duphy4.hepnet
     (215) 895-1545      / \  Particle Physics  lane@duphy1.bitnet
FAX: (215) 895-5934        /~~~~~~~~~~~         lane@duphy4.physics.drexel.edu
Newsgroups: comp.os.vms
From: houseman@hopper.ACS.Virginia.EDU (Carl Houseman)
Subject: Re: ?modifying mail profile?
Keywords: mail profile modify question
Organization: UVA. FREE Public Access UNIX! 
Distribution: comp.os.vms
Date: Thu, 28 Jan 1993 00:21:56 GMT

In article <andrea.728156651@pX1.stfx.ca> andrea@pX1.stfx.ca (John Andrea) writes:
>3. How does one get listed in the mail profile ?

When someone sends them mail the first time their mail profile is created.

I solve your problem with a .COM file and do 

   $ SUBMIT/USER=newuser/NOLOG SETMAIL.COM

where SETMAIL.COM contains:

   $ mail
   set mail_direct [.mail]
   set queue lqp_queue
   set form mail_form
   set cc
   set editor tpu
   $ exit

(you need CMKRNL priv for this, make sure the user has RE access to
SETMAIL.COM, and can execute batch jobs in the queue pointed to by SYS$BATCH).

This also creates a mail profile for the user.  It has a drawback of giving
them a "last noninteractive login" time.

>John Andrea
>andrea@essex.stfx.ca
>VAX System Manager, St. F. X. University, Antigonish, NS  CANADA

Carl Houseman
houseman@hopper.acs.virginia.edu
GENICOM Engineering, Waynesboro, VA
From: rm55+@pitt.edu (Rudolph T Maceyko)
Newsgroups: comp.os.vms
Subject: Re: Help defining keys ...
Date: 22 Jan 93 17:26:15 GMT
Organization: University of Pittsburgh

In article <1jp8luINN7g6@aludra.usc.edu> judson@aludra.usc.edu (Tom Judson) writes:
>
>On my VAXstation, the comma key is suppossed to echo a '<' and the
>period key a '>'.  But, they just print out comma and period.
>
>* I used the "Keyboard" menu option to select "Comma Key Sends ,<"
>  but that did not help.

I had that problem, too.

You'll notice (if you have an LK-401; I don't know about others) that
the "<>" key is present between the left shift key and "z".  It works.
But if you want SHIFT-, and SHIFT-. to work as well:

Make sure you have the right keyboard set.  The "System Default" is 
apparently not LK-401, which is what I have.  In my set up, I would choose
the Keyboard Type from the Session Manager Options menu.

Also, setting DECterm Keyboard Options "Angle Brackets Key Sends '~"
and "Comma Key Sends ,<" makes SHIFT-, and SHIFT-. work, but not the
"<>" key!  (Under "System Default" Session Manager Keyboard setting.)

I hope this helps!

Later,
Rudy


-- 

Rudy Maceyko <rm55+@pitt.edu>                     University of Pittsburgh/CIS
From: gharpure@vtpwr2.psl.ee.vt.edu (Vasudev Gharpure)
Newsgroups: comp.os.vms
Subject: Re: How can I change my Username
Date: 28 Jan 93 16:19:00 GMT
Organization: Power Systems Lab, Electrical Engg., Virginia Tech
News-Software: VAX/VMS VNEWS 1.41

In article <1993Jan26.235253.2644@merrimack.edu>, finocchiaroj@merrimack.edu writes...
>I was wondering if there is a way that I can change my username by bypassing
>the system managers protected privliages.

	If you really want a fight with someone, don't start it on their home ground.

Vasudev
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Mailbox access
Date: 27 Jan 1993 13:21:16 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 <20303.2b5bb282@ul.ie>, 9120092@ul.ie writes:
>This is primerily caused by VMS which takes a mailboxes
>name and places the pointer to that device in the PCB. So when a mailbox
>is created instead of being "My-Mailbox" and being open for group
>access it is infact "My-PID.My-Mailbox" which tends to throw a spanner
>in the works for me as I can not get around that protection.

Where the pointer to the device might be is totally irrelevent.  You're rather
bizarre construct above is quite meaningless.

>I think IO$Write_Attention gets involved some where but I'm not sure.

You're completely wrong about this.  Well, then, why don't you try reading the
manual?  Or even the on-line help?

>Am I right about the mailbox protection. any suggestions on getting
>around it?

No, you're completely wrong.  You don't even have a clue as to what you're
talking about.  As to getting around it, have a look at the documentation to
the $CREMBX system service.  Pay close attention to the fifth argument.

Now, if protection is *NOT* the problem (why didn't you bother to post the
status returned by VMS when you tried to open the mailbox?  The status returned
by VMS couldn't *POSSIBLY* tell us anything about your problem, now could it?),
then you're probably running afoul of the fact that the logical name for the
mailbox (assuming it's a temporary mailbox;  I'd hate to think that you might
have PRMMBX priv) is, by default, placed in your job logical name table, which
is not easily accessible to processes outside of your own job.  If that's the
problem, then you'll have to find some other way for the process that creates
the mailbox to communicate the name of the mailbox to the other process.
--------------------------------------------------------------------------------
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.
Newsgroups: comp.os.vms
From: coar@Nephi.Enet.DEC.Com (Rodent of Unusual Size)
Subject: Re: re: Re: HELP!!! Security problem for gurus. [Directories]
Summary: It's in there..
Keywords: ACLEVEL, access mode, security, protection, file system
Organisation: Employed by (*NOT* speaker for) DEC, Boxborough, MA, U.S.A.
Organization: Digital Equipment Corp.
Distribution: comp
Date: Fri, 22 Jan 1993 20:16:35 GMT


In article <9212290242.AA00964@uu3.psi.com>, leichter@lrw.com (Jerry Leichter) writes...
> 
>(ODS-II has several other "spec'ed but never implemented" features, including
>a hashed file type and something I gather will finally appear in VMS V6:
>Access-mode restricted files (i.e., files that can only be accessed from
>inner-mode code, regardless of the usual protections on the file).

    The access-mode restriction is in there now, and has worked since at least
    1984.  Unfortunately, file accesses are generally performed by RMS, which
    runs in executive mode, so the only really useful settings involve kernel
    restrictions.  It was possible to set up a write-only file this way..

    Back in them olde days, the checks for the access mode field were rather
    orphaned; you could change the access-mode protection on a file and BYPASS
    wouldn't let someone at it.

    A lot of things changed in this area around the time of late VMS V4 or VMS
    V5.0.  The situation with BYPASS and READALL was corrected, and
    BYPASS will now let you access files regardless of the contents of the
    ACLEVEL field.  The nesting of write-access as a proper superset of
    read-access appears to have been implemented at the same time; you can no
    longer write to a file that has read access denied to your access mode.
    In addition, the mode-checking seems to have been changed to check against
    PRVMOD rather than CURMOD, so protecting a file against user, supervisor,
    and executive-mode access is now meaningful.

    Unfortunately, this entire area is semi-documented, and not supported.
    The behaviour is not exactly right, but I'm not going to spend the time at
    the moment to figure out the details of the deviations.  If you're
    interested, the thing to check out is the ATR$C_ACLEVEL file attribute in
    the file system chapter of the I/O Abuser's Guide.  I have an antique
    BLISS-32 programme that frobs the field.

>It's not clear to me what BACKUP would do with a hacked directory entry.  It
>might complain, making the hacked files VERY visible during the next system
>incremental.

    Hacked directory entries are processed silently and as-is on image
    backups, but not for non-image activities.  (I hacked a directory long ago
    with PATCH /ABSOLUTE to produce filenames with spaces, escape sequences,
    and other oddities.  DIRECTORY displayed them verbatim, but BACKUP had a
    fit.)

>							-- Jerry

    #ken    :-)}	Jeratol the Chaotic

Coar@Nephi.Enet.DEC.Com	 | All opinions herein contained, stated or implied,
Coar@DECUS.Org		 | are solely those of the author.  And he's fullovem.
Coar@Eisner.DECUS.Org	 | `... it was mine art, ... that made gape the pine 
Massachusetts, USA       | and let thee out.'  - Prospero (_The Tempest_)
From: hasan%dvax.dnet@UNIVAX.FHDA.EDU (HASAN@ADMIN.FHDA.EDU)
Newsgroups: comp.os.vms
Subject: C example using SMG$CREATE_MENU
Date: 27 Jan 93 18:24:32 GMT
Organization: The Internet


	Hello All,

	I am trying to write a program in VAX C v3.2, which uses
	SMG (Screen Management) routines.

	I am getting "SMG-INVARG" error, every time I use the
        SMG$CREATE_MENU routine.

        Would it be possible for me to look at a C example which
	anyone of you have written that uses SMG$CREATE_MENU ?

	Any help in this matter will be greatly appreciated.

	Thanks,


		 //================================\\
		||        Syed Mahmood Hasan       ||
                ||                                 ||
                ||        Systems Programmer       ||
                ||                                 ||
                ||        HASAN@ADMIN.FHDA.EDU     ||
                ||                                 ||
		||    Foothill-De Anza Community   ||
		||         College District        ||
      		||      Los Altos,  California     ||
                ||                                 ||
		||         (408) 864-8242          ||
		 \\================================//
From: vance@lpl.arizona.edu (Vance Haemmerle x4021)
Newsgroups: comp.os.vms
Subject: Re: VAX FORTRAN
Date: 28 Jan 93 22:53:02 GMT
Distribution: world,local
Organization: Lunar & Planetary Laboratory, Tucson AZ.

In article <1k8ennINN52q@gap.caltech.edu> carl@SOL1.GPS.CALTECH.EDU writes:
>Well, Ken, there's a problem here.  You see, SYS$SNDJBC[W] wants, as some of its
>arguments, pointers to arrrays containing filename, form name, and queue name. 
>It does *NOT* want descriptors for these.  That means that the arguments have
>to be the addresses of arrays, not the addresses of descriptors.  Now, since I
>was posting from home without benefit of manuals, I had to rely on my memory,
>and I couldn't for the life of me remember how to get the dsc$a_pointer field
>out of a VAX FORTRAM character string descriptor (nor could I remember how to
>use a WRITE statement to copy the contents of a string into a BYTE array).  So
>I initialized the arrays the best way I could remember.

  You can use the built-in %REF() function to pass the address of a
  character in FORTRAN.  (In case anyone was wondering).

Example:


  CHARACTER*80 LINE, HFILE
       .
       .
       .
C  Replace unprintable characters with '.' using SYS$FAO
	CALL SYS$FAO('!AF',LEN,HFILE,%VAL(80),%REF(LINE))
                                              ^^^^^^^^^^ address of character
					                 string

--
 Vance Haemmerle                              vance@arizona.edu
 Support Systems Analyst, Senior              vance%toyvax@arizona.edu
 Lunar & Planetary Lab                        vance@alumni.caltech.edu
 University of Arizona
From: ISENHOUR@FNAL.FNAL.GOV (John L. Isenhour)
Newsgroups: comp.os.vms
Subject: (none)
Date: 20 Jan 93 17:24:23 GMT
Organization: The Internet

REMOVE ISENHOUR@FNALO.FNAL.GOV
REMOVE ISENHOUR@FNALA.FNAL.GOV
REMOVE ISENHOUR@FNALC.FNAL.GOV
REMOVE ISENHOUR@FNALF.FNAL.GOV
REMOVE ISENHOUR@FNALNM.FNAL.GOV
REMOVE ISENHOUR@FNALNO.FNAL.GOV
REMOVE ISENHOUR@FNALNA.FNAL.GOV
REMOVE ISENHOUR@FNALNB.FNAL.GOV
REMOVE ISENHOUR@FNALNC.FNAL.GOV
REMOVE ISENHOUR@FNALND.FNAL.GOV
REMOVE ISENHOUR@FNALNE.FNAL.GOV
REMOVE ISENHOUR@FNALNF.FNAL.GOV
REMOVE ISENHOUR@FNALNG.FNAL.GOV
REMOVE ISENHOUR@FNALNH.FNAL.GOV
REMOVE ISENHOUR@FNALNI.FNAL.GOV
REMOVE ISENHOUR@FNALNJ.FNAL.GOV
REMOVE ISENHOUR@FNALNK.FNAL.GOV
REMOVE ISENHOUR@FNALNL.FNAL.GOV
REMOVE ISENHOUR@FNALNN.FNAL.GOV

Newsgroups: comp.os.vms
From: ORAKEL@rzmain.rz.uni-ulm.de (Framstag)
Subject: Re: WANTED: VMS calculator program
Organization: University of Ulm, Germany
Date: Wed, 27 Jan 1993 19:28:09 GMT
X-Copyright1: Fuer Veroeffentlichungen AUSSERHALB des Newssystemes gelten MEINE Geschaeftsbedingungen.
X-Copyright2: Nichtbeachtung wird in der Regel zivil- und strafrechtliche Folgen nach sich ziehen.
X-News-Reader: VMS NEWS 1.25beta

In <20301.2b5ad225@ul.ie> 9118187@ul.ie writes:

> I'm looking for a VMS calculator program. Does anyone know if such a program
> exists?

scientific calculator with DCL interface is on:

info.rz.uni-ulm.de  pub/VMS/misc/icalc


\  Ulli 'Framstag' Horlacher       \     psi%(0262)45050260103::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."  \
Newsgroups: comp.os.vms
From: vli@mpr.ca (Vincent Li)
Subject: Sixel graphics & RETOS
Keywords:  Sixel, RETOS
Organization: MPR Teltech Ltd., Burnaby, B.C., Canada
Date: Sat, 23 Jan 93 04:52:27 GMT

VMS gurus (and non-gurus alike),
   This one got us stumped bad:
   We are running VMS 5.5-1 on Vaxstation 3100 and Vaxstation 4000. We got
RETOS installed on both machines exactly the same way, but it worked on the
3100 and stack dumped on the 4000! Actually, it did work on the 4000 with
the default device (as far as we can trace), but not if we give it
/device=LN03 or /device=LA120, among other devices. Is there something about
peculiar about the 4000 or are we actually missing something? What should
we look for? We checked and all the files seems to be in their proper place
and all the logicals & symbols defined properly for both machines, or so
we think. Is RETOS simply no longer supported by DEC?
Thanks.

-- Vince

---------------------------------------
vli@mprgate.mpr.ca        |-) It works well under pressure: Another thing
                          |-] you can say about your pillow. -- Mr Boffo
Newsgroups: comp.os.vms
From: finlayson@persis.enet.dec.com (Mark A. Finlayson)
Subject: Re: PCA limitation / Unix "strip" for VMS
Keywords: PCA,strip
Reply-To: finlayson@persis.enet.dec.com (Mark A. Finlayson)
Organization: Digital Equipment Corporation, Nashua, NH
Date: Mon, 25 Jan 1993 16:17:18 GMT



In article <418@ittc.wec.com>, fitch@ittc.wec.com (Ken Fitch) writes:
|> The DECset Performance & Coverage Analyzer (PCA) is having trouble
|> digesting an executable with a large number of debug symbols.
|> When run it gives the message:
|> 
|> =================================================================
|> /user/krf/appr_bm> run testexec_pca
|> 
|>         VAX PCA Collector Version V4.0-80
|> 
|> PCAC> g
|> %PCA-E-INCDST, incorrect DST nesting in module RPDINIT. Datafile not set.
|> %PCA-I-NODATACOL, exiting with no data collection phase
|> =================================================================
|> 
|> (Note that the pathname prompt simply betrays my Unix orientation.)

I'm not a PCA developer and can't give you an authoritative answer but
usually the incorrect DST nesting message indicates that there's something
wrong with the DSTs for that module.  I don't know what is causing your
specific problem, but you can usually work around these by compiling the
modules in question with /NODEBUG (RPDINIT in your case).

Mark Finlayson

My opinions are not the opinions of Digital Equipment Corporation
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Moderated List????
Date: 22 Jan 1993 11:57:50 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 <2140@bdrc.bdrc.bd.com>, woody@bdrc.bd.com (Woody Muller) writes:
>>For what it's worth:
>>        Ehud has left the newsgroup.
>
>How sad.  But what about all the people *you've* chased away from this
>forum, Carl?  There are lots of folks on Usenet with varied interests
>and environments, people who have no desire to have your kind of mile-
>deep and yard-wide knowledge.  These people have questions, and they
>also have answers to questions in other subjects.

Well, I try not to flame people who have at least a LITTLE understanding of
what they're doing.  I have flamed (and will continue to flame) people who post
questions of the form:
	This doesn't work (vague description of that "this" might be, and *NO*
	indication whatever of how it failed to work.
>Sometimes these people browse through a group and ask a question.  Maybe
>it's not that good a question.  And like some high-school bully (like
>the ones that may have pushed you around years ago) you inflict abuse
>on some poor soul who does not deserve it.

That's where you and I differ.  I think someone too bloody stupid to realize
that if he wants help, he needs to tell us EXACTLY what he did and EXACTLY what
happened, deserves to be flamed.  Unlike you, I'm not a mindreader, and
consider such posts more fit for alt.paranormal or talk.religion.newage.

>You think your mile-deep
>and yard-wide knowledge gives you a license to flame, but a jerk is a
>jerk is a jerk.  You're playing king of the vms molehill.

Well, you seem to be an expert on jerks, being one yourself.

>You have fostered an environment of confrontation and abuse, Carl, and
>a lot of knowledgeable people who dislike confrontation and abuse 
>stay quiet.  The "newbies" you are so fond of bullying are a 
>completely new crop of news browsers from the "newbies" you bullied
>away from the group a few months ago -- and there will be more next
>month.  That's the way of the net.browsers -- remember, this newsgroup
>goes beyond the INFO-VAX mailing list.  Live with it.

I refuse to live complacently with abject stupidity, no matter how much you may
wish to wallow in it.
--------------------------------------------------------------------------------
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: blacka@logica.co.uk (Andrew Black)
Newsgroups: comp.os.vms
Subject: re: new mail count error 
Date: 26 Jan 93 13:43:43 GMT
Distribution: world

leichter@lrw.com (Jerry Leichter) writes:

> .... How about SET NEW_MAIL_COUNT 

A more basic solution would be to stop the count getting  wrong in the
first place.   I believe this is because the mail count is stored in a
different place ( SYS$SYSTEM:VMSMAIL_PROFILE.DATA) from the messages
themselves (MAIL.MAI).

I have thought it useful to have two users with the same SYS$LOGIN
directory - for example a less privileged account for dial in use 
so you can read your mail but not do anything that needs CMKRNL!
; they share the same MAIL.MAI but different VMSMAIL_PROFILE
entries.  This does wonders for ones new mail counts ;-)



----------------------------------------------------------------
Andrew Black                    blacka@logica.co.uk
Logica Finance, London
-----------------------------------------------------------------
From: georgetl@cnsvax.uwec.edu
Newsgroups: comp.os.vms
Subject: VMSTAR help
Date: 22 Jan 93 16:08:39 -0600
Organization: University of Wisconsin Eau Claire

I'm having problems with the version of VMSTAR on our system.  It's probably
a simple error, but the answer eludes me.  What happens is when I try to
untar a file, the program only recognizes the first file in the archive and
proceeds to untar ONLY that file.  I know the file isn't corrupt, just that
VMSTAR won't for the life of me recognize the other files.  Any help would be
great.

 ------------------------------------------------------------------------------
| Todd L. George           | "In the begining there was nothing, and God said  |
|  University of Wisconsin |  Let there be Light.  And there was still nothing |
|   Eau Claire             |  , but you could see it!"                         |
|------------------------------------------------------------------------------|
| Georgetl@cnsvax.uwec.edu    | "You shouldn't have done that Maximillian      |
| Georgetl@uwec.bitnet        |  he was a good man!"                           |
|------------------------------------------------------------------------------|