HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.internals
Subject: re: AXP
From: allebrandi@inland.com (Tom Allebrandi)
Date: 9 Nov 92 13:26:22 CST
Organization: Inland Steel Company; East Chicago, IN

In article <27A00A11_00076BD8.0096334CAD64E4C0$203_3@UK.AC.KCL.PH.IPG>, SYSMGR@IPG.PH.KCL.AC.UK writes:
> "It doesn't stand for anything". Well, we can all speculate.
> 

I was speculating about this over the weekend...

> A:  Alpha, or Advanced.
> 

Yep.

> X:  The marketing types know that all things being equal, putting an X
>     in the name makes it sell better. It's, as they say, seXy.
> 
>     In this case it alo provides a link back to the much loved VAX: in
>     that case it was supposed to mean eXtension ...
> 

Actually, since the privileged instructions in the processor are tailored
to the operating system by creating a PALcode set, how about

	eXtensible

> P:  Processor, or power. Advanced seX Power? Amazing the way you can think
>     like a marketing droid when you want to :-) :-) :-)

Yep.

--- Tom
Tom Allebrandi             | Mail guru   - DECUS UUCP Development Team
Inland Steel Research Labs | NFS grunt   - CMU/Tek-IP
East Chicago, IN           | Chairperson - VMSnet Working Group, DECUS VAX SIG
219 399 6306               | Internet:  allebrandi@inland.com
DECUServe: allebrandi      | UUCP:      ...!uunet!inland!allebrandi
From: "Brian J. Schenkenberger, VAXman"
Newsgroups: vmsnet.internals
Subject: Re: AXP
Date: Tue, 10 Nov 1992 11:56 EDT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

-  AXP

>> "It doesn't stand for anything". Well, we can all speculate.

Seems to me that if it's a product coming from DEC it should stand for:

        Another eXpensive Product...

Along this line of thinking, I can forsee an entire product line...

OpenVMS  Another eXpensive Product...
PathWorks  Another eXpensive Product...
VMScluster  Another eXpensive Product...
DECservice  Another eXpensive Product...  ;-)

BJS-
Newsgroups: vmsnet.internals
Subject: Re: DECUS gathering
From: Ehud Gavron 602-570-2546 <GAVRON@IT.SUNQUEST.COM>
Date: Mon, 9 Nov 1992 11:10:55 -0700 (MST)
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Date sent:  9-NOV-1992 11:10:14

Mats writes:
>I wish you would wear your suit, I'd love to se you in a suit :-)

You can see me wearing a suit just like everyone else can -
pay me to consult for you ;-)

(You get to see me being obsequious too, if you do that!)

>--
>  Mats Akerberg, System Manager (mats@efd.lth.se),(MATS@SELDC52) on Earn/Bitnet
>  Lund Institute of Technology ,School of Electrical Engineering and
>  Computer Sciences. Snail: Box 118  S-221 00 Lund Sweden
>  Phone: + 46 46-109847 FAX: + 46 46-104013

Cheers,

Ehud

--
Ehud Gavron        (EG76)
gavron@vesta.sunquest.com                                       This was sent
"The world bores you when you're cool."                         from an Alpha
From: SYSMGR@IPG.PH.KCL.AC.UK
Newsgroups: vmsnet.internals
Subject: re: AXP
Date: Fri,  6 NOV 92 11:11:34 BST
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

"It doesn't stand for anything". Well, we can all speculate.

A:  Alpha, or Advanced.

X:  The marketing types know that all things being equal, putting an X
    in the name makes it sell better. It's, as they say, seXy.

    In this case it alo provides a link back to the much loved VAX: in
    that case it was supposed to mean eXtension ...

P:  Processor, or power. Advanced seX Power? Amazing the way you can think
    like a marketing droid when you want to :-) :-) :-)

                Nigel Arnot

                NRA%ipg.ph.kcl.ac.uk@nsfnet-relay.ac.uk   (internet)
                NRA%uk.ac.kcl.ph.ipg@ukacrl.bitnet        (bitnet)

PS ICL computers once named an O/S George after the chief programmer. Eventually
   they had to invent an "official" explanation. Now, that one's tricky!
Newsgroups: vmsnet.internals
Subject: RE: re: idle terminal...
From: don@zl2tnm.gen.nz
Date: 5 Nov 92 22:44:44 +1300
Organization: The Wolery

In article <009631D4.196251A0.31400@WKUVX1.BITNET>, Hunter Goatley <goathunter@WKUVX1.BITNET> writes:
> There is a way to avoid these too.  I had to do this once for software
> that I didn't want $DELPRCed, $FORCEXed, *or* suspended.  Set the
> following bits in the PCB:
> 
>         PCB$V_SUSPEN            !Suspend is pending
>         PCB$V_DELPEN            !Delete is pending
>         PCB$V_FORCPEN           !FORCEX is pending

Neat.

        =TOYVAX=> stop "_TWA6:"
        =TOYVAX=> set proc "_TWA6:"/susp
        %SET-E-NOTSET, process _TWA6:, PID=00001216, not suspended
        -SYSTEM-W-NONEXPR, nonexistent process
        =TOYVAX=> sh proc "_TWA6:"
        %SYSTEM-F-SUSPENDED, process is suspended

That should confuse 'em.  


Don Stokes, ZL2TNM (DS555)                       don@zl2tnm.gen.nz (home)
Network Manager, Computing Services Centre           don@vuw.ac.nz (work)
Victoria University of Wellington, New Zealand             +64-4-495-5052
Newsgroups: vmsnet.internals
Subject: Re: Virtual disk make a nice test device
From: "Brian J. Schenkenberger, VAXman"
Date: Mon, 9 Nov 1992 08:51 EDT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

>Glenn Everhart's VDDRIVER allows you to create "disk" devices with contiguous
>files.  Virtual disks come in handy for all sorts of testing.  They make good
>test devices for new versions of BACKUP, VERIFY etc.

Yes!  I have a DECUS copy of VDDRIVER and used to use it until my disk space
bacame  'limited'.  Therefore, there were very limited chunks of contiguous
space left to make the VD disk container file.  That problem went away recently
when I acquired another broken XT2190 with a drive motor. (FOC) Reworked the
motor and now I have Plenty o' free disks space! ...for a while anyway... ;-)
The RX23 was also a free-b.  So, I figured that this was as good a time as any
to put it through the ropes.

Also,  the pseudodisk (PDA0) could be used for test cases with code munging
file and volume structures.  For those that may not know how:  Simply connect
the driver with SYSGEN and then peruse the STABACKIT.COM file for the little
macro ditty to configure/size the pseudodrive.

The real issue here -- don't play around on disks with valued data.  _IF_ you
must, be sure your backups are good and current!!!

BJS-
From: munroe@dmc.com (Dick Munroe)
Newsgroups: vmsnet.internals
Subject: Re: What does AXP stand for ...
Date: 7 Nov 92 11:05:59 EST
Organization: Doyle, Munroe Consultants, Inc., Hudson, MA

In article <0096327C4DA39CA0.00002096@xbrix.UUCP>, xbrix!thalabi@csri.toronto.edu writes:
> What does AXP stand for in `OpenVMS AXP (Alpha)'?
> 

Larry Kilgallen speculated that AXP stands for Alpha (the X and P are silent).
-- 
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma.				FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.
Newsgroups: vmsnet.internals
Subject: Virtual disk make a nice test device
From: "(Jon Pinkley, Westinghouse (216)486-8300 x1335)"
Date: Mon, 9 Nov 1992 04:24:28 -0500
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

>I uncovered this accidentally when playing on my uV2K cluster to which
>I recently attached a RX23-AA.  At the time I thought it a bit useless
>since the 3.5 floppy can hold very little data (~2500 blocks);  however,
>it's a great commodity when you need to play with code that is modifying
>file and/or volume data.  I highly recommend to anyone working on such
>code to get themselves a floppy for their system.
>
>BJS-

Glenn Everhart's VDDRIVER allows you to create "disk" devices with contiguous
files.  Virtual disks come in handy for all sorts of testing.  They make good
test devices for new versions of BACKUP, VERIFY etc.

Glenn, what is the latest and greatest version of VDDRIVER and ASNVD?

Jon Pinkley jon@clevax.wec.com  ...uunet!tron!clevax!jon (216)486-8300 x1335
Newsgroups: vmsnet.internals
Subject: RE: re: idle terminal...
From: Hunter Goatley <goathunter@WKUVX1.BITNET>
Date: Mon, 09 Nov 1992 10:30:18 CST
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Ehud Gavron 602-570-2546 <GAVRON@IT.SUNQUEST.COM> writes:
>
>       A week ago I posted code to periodically increment the process
>       I/O count so that idle job killers wouldn't kill it.
>
>       Hunter et all offered clever ditties to set the delete pending
>       and exit pending flags, preventing those from being applied.
>
>       HOWEVER, all those require explicit code be run by the user
>       before termination can occur.  In the event that the user was
>       disconnected (terminal, non vtas) or killed (batch job termination)
>       then that process is STUCK until $cmkrnl intervention.
>
Yes, I was following the thread (and taking it farther) that was
moving away from the idle terminal stuff.  My comments were mostly for
those detached processes you want to protect.

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251
From: mark@infocomm.com
Newsgroups: vmsnet.internals
Subject: RE: Need help clearing FH2$V_ALM_AIP
Date: 5 Nov 92 11:38:08 PDT
Distribution: world,local
Organization: INFO COMM - Computer Consulting, Redwood City, Ca

In article <5NOV199210212070@carat.arizona.edu>, jms@carat.arizona.edu (Ducks? Why do they have ducks?) writes:
> PPS: DOES ANYONE OUT THERE READ THAT STUFF I STICK IN DIGITAL REVIEW? 
> Could I have a little feedback, fer crissake?  Jeez, it's like writing
> into a black hole.

Yes, but doesn't money come back out of the hole? :-)

--
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: gjc@mitech.com (George J. Carrette)
Newsgroups: vmsnet.internals
Subject: Re: Dream extensions for MACRO-32
Date: 5 Nov 92 09:38:57 GMT
Organization: Mitech Corporation, Concord MA

In article <1992Nov2.020339.1171@mwk.uucp>, gleason@mwk.uucp writes:
>   Now that MACRO-32 is more a compiler than an assembler ...

Lord, give me strength!

> What fantasy extensions would you make, to make MACRO-32 better
> for your work?

All you need is a serious, -real- MACRO capability. The ability to
invoke LIB$FIND_IMAGE_SYMBOL from inside a macro.

Then, given that, I would cause my macros to invoke a small LISP interpreter,
such as SIOD. Then I could have macros that were powerful enough to
be a compiler for any language that I felt like generating that day.

Of course, it would also be nice if communication between the
compiler back-end (i.e. MACRO-32) and my middle-front-end stuff
was more structured than mere ascii representation of a stream
of statements.

Historical note: 

The LISP compilers at MIT started out as -assemblers-. For what was
called LAP, lisp assembly programs. Stuff like this:

 (.ENTRY MYPROG)
 (MOVE R0 (@R5))
 (JSR FOOBAR)

To make this into a compiler all you had to do was add macroexpansion
and a database capability (keep track of compiler assumptions etc).

-gjc
From: "GWDGV1::MOELLER" <moeller@gwdgv1.dnet.gwdg.de>
Newsgroups: vmsnet.internals
Subject: RE: odd XQP behaviour
Date: Fri, 06 Nov 1992 11:20:57 +0100
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Nigel Arnot <NRA%ipg.ph.kcl.ac.uk@nsfnet-relay.ac.uk> writes:
> Some of you may have noticed my recent posting to info-vax about VMS failing
> to allocate a pagefile on a slightly fragmented disk, and what to do about
> it. For those who didn't, the problem was that SYSGEN CREATE was failing to
> allocate an 80000 block pagefile on a disk with around 200000 blocks free
> in fragments of size over 6000 blocks. What it was doing was building a
> file out of about four decent-sised fragments, and then filling the header
> with all sorts of mostly tiny fragments presumably out of the extent cache.

This is documented behaviour of the CBT (contiguous best try) allocation
option, which SYSGEN is using. It will look for suitable extents only
a limited number of times, then revert to the "standard" practice.

> I have now found another funny: the same problem in reverse. A user ran
> a FORTRAN program that generates two output files: the first stays small,
> the second ends up at around 3000 blocks, both are opened 'NEW' (ie empty)
> and filled with sequential writes.

Just recently I've seen the same with DECPs (VPA's new name) .CPD files,
which get pre-allocated at different (large) sizes every day; this *may*
have something to do with the availability of free extents, but I've no
real clue yet. This is on VMS 5.4-3.

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: JWILKINSON@HMCVAX.CLAREMONT.EDU (James Wilkinson)
Newsgroups: vmsnet.internals
Subject: Re: Undocumented SMG$ locator routine
Date: 5 Nov 92 08:22:53 GMT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List


    davism@KCGL1.eng.ohio-state.edu :
    [...]
    If anyone out there running 5.5-2 in field test could speak to whether the
    SMG$READ_LOCATOR call is documented and/or fixed, I'd appreciate it.

Lots of SMG$ routines were fixed in V5.5-2, but still no mention of
SMG$READ_LOCATOR.  Note that this routine has two additional arguments -
a timeout argument (5th) and a parse routine (6th).  The parse routine
receives the keyboard id, locator response (string), row, column and keycode.
You might be able to use the parse routine to make things behave more the way
you want them to.

If you are using this routine at a time when you expect the user to use the
mouse for input, this routine works fine.  I wish I could read a mouse event
from an SMG$ application which is dynamic in nature - eg., time gets updated
once per second, etc.  The ANSI sequence of asking for locator information
and waiting for the response is quite restrictive for such applications.  I
have at times wondered if one couldn't query the mouse driver for mouse button
press events.  That way an application could receive asynchronous notification,
much as an Xwindows application would.

SMG$ does have a few things which are quite useful in the DECterm environment
which aren't documented, besides SMG$READ_LOCATOR.  Try using any of the user
renditions when writing text to a display - you get a limited set of colors.

JaW

jwilkinson@hmcvax.claremont.edu
From: brydon@dsn.sinet.slb.com
Newsgroups: vmsnet.internals
Subject: RE: AXP
Date: 10 Nov 92 17:41:21 GMT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Brian J. Schenkenberger (SCHENKENBERG@Monmouth-ETDL1.Army.MIL - ?) sez:
>-  AXP
>
>>> "It doesn't stand for anything". Well, we can all speculate.
>
>Seems to me that if it's a product coming from DEC it should stand for:
>
>        Another eXpensive Product...
>
>Along this line of thinking, I can forsee an entire product line...
>
>OpenVMS  Another eXpensive Product...
>PathWorks  Another eXpensive Product...
>VMScluster  Another eXpensive Product...
>DECservice  Another eXpensive Product...  ;-)

I think you may be pleasantly surprised.  DEC seems to be quite serious about
being quite competitive with the Alpha.

[I find this kind of comment from somebody in the military to be amusing...]
_______________________________________________________________
Harvey Brydon         | Internet:   brydon@dsn.SINet.slb.com
Dowell Schlumberger   | P.O.T.S.:   (918)250-4312
   Wait State:  What happens while the computer boots.
Newsgroups: vmsnet.internals
Subject: re: idle terminal...
From: Ehud Gavron 602-570-2546 <GAVRON@IT.SUNQUEST.COM>
Date: Mon, 9 Nov 1992 9:09:19 -0700 (MST)
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Date sent:  9-NOV-1992 09:05:26

        A week ago I posted code to periodically increment the process
        I/O count so that idle job killers wouldn't kill it.

        Hunter et all offered clever ditties to set the delete pending
        and exit pending flags, preventing those from being applied.

        HOWEVER, all those require explicit code be run by the user
        before termination can occur.  In the event that the user was
        disconnected (terminal, non vtas) or killed (batch job termination)
        then that process is STUCK until $cmkrnl intervention.

        Lastly on the issue of NODELETE and FORCEX...  there is nothing
        stopping anyone from creating an exit handler which unwinds past
        the $exit and the $forcex.  It takes a bit of code out of $unwind
        plus some stack fixup (and you have to dismiss the ast frame) but
        it works.  If it weren't Sunquest proprietary I'd post it.

        I'm still looking for a better solution than mine, that requires
        NO user intervention at logout... however until I find one, a
        repeating tqe in p1 space works for me :)

        Ehud

--
Ehud Gavron        (EG76)
gavron@vesta.sunquest.com                                       This was sent
"The world bores you when you're cool."                         from an Alpha

MONDAY 8:00PM LOBBY OF THE HILTON - MILLER IN EHUD SHIRT - EHUD IN CMU SHIRT
From: GAVRON@IT.SUNQUEST.COM (Ehud Gavron 602-570-2546)
Newsgroups: vmsnet.internals
Subject: Re:  DECUS gathering
Date: 9 Nov 92 15:49:52 GMT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Date sent:  9-NOV-1992 08:49:28


>I will be wearing my "I'm Ehud Gavron.  Who the hell are you?" T-shirt.
>
>-bruce

        I'll be wearing my upside-down-lettering CMU-TEK TCP/IP shirt.

        Ehud

--
Ehud Gavron        (EG76)
gavron@vesta.sunquest.com                                       This was sent
"The world bores you when you're cool."                         from an Alpha
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: vmsnet.internals
Subject: Re: DECUS gathering
Date: 9 Nov 1992 22:29:31 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 <921109111055.1f9f@IT.SUNQUEST.COM>, Ehud Gavron 602-570-2546 <GAVRON@IT.SUNQUEST.COM> writes:
>Date sent:  9-NOV-1992 11:10:14
>
>Mats writes:
>>I wish you would wear your suit, I'd love to se you in a suit :-)
>
>You can see me wearing a suit just like everyone else can -
>pay me to consult for you ;-)
>
>(You get to see me being obsequious too, if you do that!)

Obsequious? Ehud? Sounds like it might be worth it for everybody at DECUS to
get together and hire him for an hour or so.
--------------------------------------------------------------------------------
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: vmsnet.internals
Subject: VD: as test device
From: raxco!galaxy.dnet!gleeve@uunet.UU.NET
Date: Mon, 9 Nov 92 09:29:00 -0500
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Re: Jon Pinkley's (kind) remarks about vddriver...
The latest & greatest was in fdvdkit.zoo in the S92 tapes in
[vax92a.gce92a.net92a]fdvdkit.zoo. Some later stuff and fqdriver.mar
(a somewhat better fddriver.mar version) are in that directory also
as separate files. Recent mods have mainly been in adding some new
device geometries to the assign - VD image and setting it up so
the device type gets set then instead of leaving dt$_FD1 in there
for all disks. I use VD: drivers all the time for testing file
structure hacks. It's also easy to change driver name to vdbdriver
so I have two layers of them with separate drivers when I want to
do weird hacking that involves munging driver tables. The lower
and unmodified driver makes sure the rest of my system's disk space
doesn't get scribbled on if something I do to a vdbdriver unit
causes it to start clobbering its unit. Since the size and geometry
of the VD: units can be easily controlled, I can be a little more
sure those can't have any effect on my stuff.
   The recent hacks that cover setting the allocation class in the
driver (thanks, Jon!) will be on the F92 tapes. They're real small
but might be handy.
   Still, floppies are also handy where I want a removable and
system-mountable device that I can test. I recently did a little hacking
on passing ownership of mounted volumes around. A short hack that
just changes the device owner UCB pointer does allow access, but
dismount requires the mounted volume list to be messed with, and
I haven't taken the time to find where that list header is to see
about moving it around. The little hack lets me say something like
$claimdevice devname:/pid:nnnnnnn  to move the ownership of devname:
to the process whose EPID is nnnnnnn, provided somebody else has
it privately owned already. I'll post it if anyone is interested.
Glenn
Everhart@Raxco.com
Newsgroups: vmsnet.pdp-11
Subject: RLV11
From: <cz@silver.lcs.mit.edu>
Date: Fri, 6 Nov 92 19:49:38 -0500
Organization: The Internet
Return-Path: <pat+@transarc.com>

The RLV11 sure DOES support the RL02 drives. I have an RLV11 running a RL01/02
at the house. What made the RLV21 so much better was two things:

1) The RLV11 was an 18 bit DMA card. It had no ability to perform DMA read/
write on a 22 bit system. Therefore, it was useless in a system with over 256KB
The RLV21 supports 22 bit DMA. Note: The RXV21 also only supported 18 bit DMA,
but DEC wrote some wacky driver that mapped stuff into it's address space in
a 22 bit system. They never did that for the RLV11, or the RKV11. The RXV11
didn't need this because it was an interrupt only device.

2) The RLV21 is a single board. DEC couldn't fit the old RLV11 on one board,
so they had two, that had to be connected by the CD BUS interface. Why they
did this is beyond me, but (I think) the only other periph that used CD inter
connect was the VTV11 (or was it the VS11) color graphics frob. (Also 11/73
//83//93 memory PMI)

CZ
From: bruce@camb.com (Barton F. Bruce)
Newsgroups: vmsnet.pdp-11
Subject: Re: Plessey memorySKIP
Date: 7 Nov 92 04:19:39 EDT
Organization: Cambridge Computer Associates, Inc.

In article <CMM.0.90.0.720790069.bqt@Bern.DoCS.UU.SE>, bqt@bern.docs.uu.se (Johnny Billquist) writes:
> Hi, I have a question about some memory I have for the 11/70.
> I have four memory boards, which was plugged into an 11/70, but

Anyone buying an 11/70 these days is totally scrapping those memory
boxes (so a dealer should sell them for very little) and installing
ALL 4 megs in the CPU box using Setasi's kit that DEC also sells.
It is ~$10k, but gives you an incredibly fast machine. Not a few % but
serveral tymes faster.

The older low density cards needed 4 boxes to do 4 meg, but the newer ones
let you get 4 meg in a single box.