HDTenEightyP/NetNews huggingface dataset:
From: sysmgr@king.eng.umd.edu (Doug Mohney)
Newsgroups: comp.sys.dec
Subject: Re: Alpha Prices -- Any Idea out there??
Date: 10 Nov 92 17:51:08 GMT
Reply-To: sysmgr@king.eng.umd.edu
Organization: Computer Aided Design Lab, U. of Maryland College Park

In article <1992Nov10.171427.8022@PA.dec.com>, rjones@wsl.dec.com (Russ Jones) writes:
>Today we are announcing 7 systems, 2 workstations and 5 servers.  

		:-)

>The entry-level workstation is called the DEC 3000 Model 400 AXP Workstation 

OK, Why "DEC 3000" ? And what does "XP" stand for? X-rated Performance? 

Hm. Ya got DECstation 3100, a DECstation 5000. Now you have a "DEC 3000 model
" <mumble> "AXP." 

> and it has an entry level (list) price of $14,995 
>in the U.S.  That configuration includes 32MB of memory,

Not shabby. 

> a 426MB disk,

Aww, not 600MB? :)
 
>a HX Graphics adapter and a 17" Grayscale monitor.  

Can you or someone else give us the Real Deal on:

	o	Expansion slots
	o	SCSI and other ports off the back


                 Play in the intelluctual sandbox of Usenet 

  -- >                  SYSMGR@CADLAB.ENG.UMD.EDU                        < --
Newsgroups: comp.sys.dec
From: rjones@wsl.dec.com (Russ Jones)
Subject: Re: Alpha Prices -- Any Idea out there??
Organization: Digital Equipment Corporation
Date: Tue, 10 Nov 92 17:14:27 GMT

Steve,

Today we are announcing 7 systems, 2 workstations and 5 servers.  The entry-level workstation is called the DEC 3000 Model 400 AXP Workstation (was code named Sandpiper) and it has an entry level (list) price of $14,995 in the U.S.  That configuration includes 32MB of memory, a 426MB disk, a HX Graphics adapter and a 17" Grayscale monitor.  

-- 
Russ Jones
Unix Marketing
Digital Equipment Corporation, Palo Alto, CA
All opinions expressed are mine, and not necessarily those of my employer
Xref: sparky comp.sys.dec:5853 comp.unix.ultrix:8181
From: wdence@nswc-wo.nswc.navy.mil (Walter Dence)
Newsgroups: comp.sys.dec,comp.unix.ultrix
Subject: Sanitize End Sectors?
Date: 9 Nov 92 15:50:43 GMT
Organization: Naval Surface Warfare Center


     I need to send some files out.  I need to wipe the ends of the 
end-sectors with zeros (or circumflexes, or anything).  This is
in case there is any sensitive info carried over into them from
a previous disk volume that had sensitive info.

     There was a similar flap several months ago over Prodigy.

     Is there a DCL batch file or other utility to do this?

     Is there a FAQ for this newsgroup?

     Is there an Internet FTP site for DEC-VAX stuff?

     Does "High-Water Marking" have anything to do with this?
If a disk volume is set to "Overwrite-on-delete", will this fix
this problem.  Does the VAX environment have these features and are
they commonly used for this?

     Thanks,
     Walt Dence



=====================================================================
                       WALTER E. DENCE, JR.
                   Data Acquisition Specialist
                 Influence Mechanisms Branch, G95

Commander, Dahlgren Division                        
Naval Surface Warfare Center     Office:          (301) 394-1707/1960
Dahlgren Division Detachment     Fax:             (301) 394-4510/4727
White Oak, G95 (W. Dence)        DSN (AutoVoN):         290-1707/1960
10901 New Hampshire Ave.         MilNet: wdence@nswc-wo.nswc.navy.mil
Silver Spring, MD 20903-5000     Home:                 (301) 229-7394

         (This is personal opinion, not official opinion.)
=====================================================================
Newsgroups: comp.sys.dec
From: scowen@wfpc3.la.asu.edu (Paul A. Scowen)
Subject: Alpha chip yield problem?
Organization: Dept. of Physics & Astronomy, Arizona State University
Date: Wed, 11 Nov 1992 21:14:34 GMT

I was wondering if anyone from the DEC enclaves would be willing to refute or
otherwise rumours I've been hearing from research groups on both coasts that
the Alpha manufacturing process is turning up very bad yield rates (like less
than 5%) compared to normal yields closer to 25-30%.  The implied result of 
this type of problem is a rarer and therefore more expensive product.

These suggestions may be baseless, I was just curious if anyone at DEC could
clarify the position.  We have an explict interest here since we are projecting
purchase of 2 Alpha boxes in the new year.

-- 
-------------------------------------------------------------------------------
Paul A. Scowen				INTERNET: scowen@wfpc3.la.asu.edu
Department of Physics & Astronomy		  uk1@spacsun.rice.edu
Arizona State University		Tel:      (602) 965-0938
Tempe, AZ 85287-1504			FAX:      (602) 965-7954
-------------------------------------------------------------------------------
Newsgroups: comp.sys.dec
From: rjones@wsl.dec.com (Russ Jones)
Subject: Re: Alpha Prices -- Any Idea out there??
Organization: Digital Equipment Corporation
Date: Wed, 11 Nov 92 23:41:30 GMT

Auggggh, I forgot the telephone numbers for the new Alpha fax server:

    U.S. and Canada                 800-842-7027 (from any touchtone phone)
    Outside U.S. and Canada         415-694-3916 (from any fax machine)

In addition to the fax server, we now have most of the new infosheets up on 
gatekeeper for ftp accesss:

	gatekeeper@pa.dec.com
	internet address 1616.1.0.2

Look in pub/DEC/DECinfo/Infosheet.  There is an index file that identifies all
of the infosheets that are available online.  In particular, look for:

	dec-3000-400.txt
	dec-3000-400s.txt
	dec-3000-500.txt
	dec-3000-500s.txt
	dec-4000.txt
	dec-7000.txt
	dec-10000.txt
	dec-osf1-v1p2.txt

There are .ps files of the same.

More Alpha AXP information will be added over the next several days.	

-- 
Russ Jones
Unix Marketing
Digital Equipment Corporation, Palo Alto, CA
All opinions expressed are mine, and not necessarily those of my employer
Newsgroups: comp.sys.dec
From: steves@socrates.umd.edu (Steven Sonnenberg)
Subject: Wanted: Used RZ55
Summary: Wanted: RZ55
Keywords: rz55
Organization: University of Maryland University College
Date: Mon, 9 Nov 1992 15:46:06 GMT

I just dropped my RZ55 and it seems to have suffered an irrecoverable
head crash so I wnated to know:

a) Is it repairable? By whom?
b) Do you have one you'd like to sell? ($500)

-steve
+------------------------------------------------------------------------+
| Steve Sonnenberg   [Too busy to do anything fancy or cute, Sorry]      |
| Strategic Software Group, Ltd., 3402 Shelburne Rd, Baltimore, MD 21208 |
| E-mail:  steve@ssgltd.com  or  uunet!ssgltd!steve                      |
| Phone:  410-764-0454;  Fax: 410-358-2106;  Pager: 410-938-1612         |
+------------------------------------------------------------------------+
From: mm5l+@andrew.cmu.edu (Matthew Mashyna)
Newsgroups: comp.sys.dec
Subject: TK50 Help
Date: 13 Nov 92 06:33:35 GMT
Article-I.D.: andrew.Uf0xXTO00WA101vaJD
Organization: Psychology, Carnegie Mellon, Pittsburgh, PA

I have a bunch of TK50's from MicroVax IIRC's. Can I get a SCSI adapter
so I can use them with my DECstation 3100's ? If someone could tell me
what part's I need I'd really appreciate it.


Thanks in advance,


Matt


///////////////////////////////////////////////////////////////////////
// Matthew Mashyna        \\                                         //
// MM5L@andrew.cmu.edu    \\  "Who the Hell told you to do that ?"   //
// voice: (412) 268-7591  \\  --my Dad                               //
// FAX:   (412) 268-2798  \\                                         //
///////////////////////////////////////////////////////////////////////
// Manager of the Computing Facilities                               //
// Carnegie Mellon                                                   //
// Department of Psychology                                          //
// Pittsburgh, PA 15213                                              //
///////////////////////////////////////////////////////////////////////
Xref: sparky comp.sys.dec:5915 comp.os.vms:17877
From: supnik@human.enet.dec.com (Bob Supnik)
Newsgroups: comp.sys.dec,comp.os.vms
Subject: Re: alpha memory requirements (vs vax) ?
Date: 12 Nov 92 21:47:12 GMT
Followup-To: comp.sys.dec
Organization: Digital Equipment Corporation


In article <1992Nov5.113540.1@uwovax.uwo.ca>, brent@uwovax.uwo.ca (Brent Sterner) writes...
> 
>   Just curious about memory demands for alpha.  I'm running a VAX 4500
>with 128 MB memory.  Of that, SHO MEM tells me "38393 pages are permanently
>allocated to VMS".  How big is VMS on an alpha system?  
> [text deleted]

In general, code expansion from VAX to Alpha is typical for RISC processors:
perhaps 1.8 to 1:  but there is wide variation.  As mentioned in a previous
note, compiler techniques such as inlining, loop unrolling, etc all increase
the size of the program text to improve performance.

Data expansion from VAX to Alpha should be negligible, unless the program
contains a lot of packed and unaligned data which gets properly aligned
during recompilation.  Note that the decision to align data or leave it
unaligned is controllable at compile time, but aligned data produces much
better performance.

As for VMS itself, several factors are at work.  Some of VMS requirements
are not in bytes but in pages.  For example, the minimum process needs
a certain number of pages for stack, stack guard, etc;  these were 512 bytes
on a VAX but are 8192 bytes on an Alpha.  In addition, to improve performance,
VMS on Alpha allows (under user control) the entire operating system to be
loaded resident, without paging.  Consequently, the minimum memory requirement
for Alpha VMS systems is currently 32MB, and that much or more is included
in the minimum configuration for all announced systems.

Bob Supnik	>Supnik@human.enet.dec.com
		>All opinions expressed are those of a hardline microcoder
		>and do not reflect those of Digital Equipment Corporation
From: schwartz@feh.scs.uiuc.edu (Dwight A. Schwartz)
Newsgroups: comp.sys.dec
Subject: Re: Alpha Prices -- Any Idea out there??
Date: 12 Nov 92 19:17:08 GMT
Organization: UIUC Chemistry Department

In article <1992Nov10.203541.28218@aosg.gsf.dec.com> reeves@decvax.dec.com writes:

>
>Well, looking at the one under my desk, I see:
>
> . ISDN with a "don't use this or you go to prison" sticker

	Sorry if this seems a waste of bandwidth, but I was wondering what 
this "don't use" comment means?

Dwight

Dwight
---------------------------------------------------------------------------
Dwight A. Schwartz ---- "Help!  I've fallen asleep and I can't get up!" -VL
University of Illinois Department of Chemistry | Box 10-1 Noyes Laboratory
505 S. Mathews Ave. | Urbana, IL   61801-3664 | 217-333-3776 | 217-244-2355
i-net: schwartz@feh.scs.uiuc.edu | bitnet: schwartz@uiucscs_--____-___-_-__
---------------------------------------------------------------------------
Newsgroups: comp.sys.dec
From: murphy@burfle.dco.dec.com (Rick Murphy)
Subject: Re: Alpha Prices -- Any Idea out there??
Reply-To: murphy@burfle.dco.dec.com
Organization: Digital Equipment Corporation, Landover MD
Date: Thu, 12 Nov 1992 22:04:05 GMT


The "don't use this or you go to prison" sticker refers to an ACTUAL STICKER
that is required over the phone jack by British Telecom authorities stating
that it's illegal to connect the system to their telephone network.
	-Rick

--
Rick Murphy, WA1SPT/4			Washington Open Systems Resource Center
Domain:  murphy@burfle.dco.dec.com -or- murphy@dco.dec.com
Bang:    decwrl!burfle.enet!murphy	"Somewhere between 30 and Death"
Ding:  (301) 918-5883				-bumper sticker.
Disclaimer: This nonsense came from an AI program written in TECO. Ignore it.
From: ben@yenta.alb.nm.us (Ben Klausner)
Newsgroups: comp.sys.dec
Subject: Scanner files in RDB
Keywords: scanner vax 4000 rdb storage
Date: 7 Nov 92 18:40:21 GMT
Organization: Department of Redundancy Department

We are building an application that calls for storing scan images of hand-
written documents on line. Because of corporate constraints, we have been
told to do this on a VAX with an RDB database. Unfortunately, no one at DEC
seems to know much about this, even though they do sell scanners. Does
anyone know:

		1: Can scan images be stored a records in an RDB database?

		2: How much storage does an 8.5"x11" page require, at the minimum
		resolution required to allow a human to read the page when it is 
		reprinted?

		3: What is the lowest end DEC terminal that will display a scan
		image?

		4: I understand that DEC does have some sort of document management
		system. Is this worth looking at?

All replies appreciated. E-Mail responses will be read faster. Thanks.


-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  inet: ben@yenta.alb.nm.us                    | My opinions are my own.
  CI$:  76337,1730                             | Who else would want them?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Xref: sparky comp.sys.dec:5884 comp.unix.ultrix:8232
From: woodford@fourier.ece.cmu.edu (Paul Woodford)
Subject: Re: Alpha Prices -- Any Idea out there??
Organization: Electrical and Computer Engineering, Carnegie Mellon
Date: Tue, 10 Nov 1992 20:31:48 GMT

Congratulations are due to DEC.  Nice performance at nice prices.  Just wish
we had that much money...

Paul "this is a stickup - hand over $14,995 + shipping" Woodford
Newsgroups: comp.sys.dec,comp.os.vms
From: brent@uwovax.uwo.ca (Brent Sterner)
Subject: RePHRASE: alpha memory requirements (vs vax) ?
Organization: University of Western Ont, London
Date: Thu, 5 Nov 1992 17:03:59 GMT

In article <1992Nov5.113540.1@uwovax.uwo.ca>, brent@uwovax.uwo.ca (Brent Sterner) writes:
>    Just curious about memory demands for alpha.  I'm running a VAX 4500
> with 128 MB memory.  Of that, SHO MEM tells me "38393 pages are permanently
> allocated to VMS".  How big is VMS on an alpha system?  (Perhaps someone with
> an alpha could post the last line from SHO MEM, though it might be misleading
> if there is a lot of dbugging code still in place.  Perhaps someone inside
> DEC has a non-debugging system they could use.)  Is there a rule of thumb for
> typical programs ("alpha memory needs"/"vax memory needs" ~= "constant")?
> Does a typical user (VAXC or FORTRAN) program require more or less memory on
> an alpha system?

	REPHRASE:  It has (already) been pointed out to me that small
	systems may not take as much memory; I suspect my installed
	images are largely responsible for the number I'm seeing here.

	The generic question stands, however.  Does the memory requirement
	for an alpha system map 1:1 to that of a comparable VMS system?
	(Probably not.)  What ratio should we expect, roughly?

	Thanks again.  b.
--
Brent Sterner                       Manager, Academic Technical Support
Fast:       <BRENT@uwovax.uwo.ca>   <129.100.2.13>
Telephone:  (519)661-2151 x 6036    Fax:   (519)661-3486
Slow:  Computing & Communications Services, Natural Sciences Building
       The University of Western Ontario, London, Ontario, Canada  N6A 5B7
From: jg@crl.dec.com (Jim Gettys)
Newsgroups: comp.sys.dec
Subject: Re: Alpha speed?
Date: 13 Nov 92 02:56:48 GMT
Organization: DEC Cambridge Research Lab

The current 21064 Alpha chip built in the current fab process will run at up to 
200MHZ (and we've never said anything else, to my knowledge).

It is, however, a dual issue processor, which means that it may be able to
start more than one instruction in a single clock cycle; at 200MHZ, it can theoretically 
achieve a PEAK instruction execution rate of 400 million instructions/second (if an good
mix of instructions happen to be available; there are restrictions on what
types of instructions can issue with other types of instructions); so
a combination of these functional unit conflicts, memory latencies
and other situations tha t can stall the processor bring the speed well down from
these peak speeds for most real applications.  See the 21064 chip specification;
you can get copies from gatekeeper.dec.com or crl.dec.com via anonymous FTP.

So a 150MHZ Alpha system can execute up to 300 million instructions/second.
We announced 5 different machines, which run between at clock rates
of between 133MHZ and 200MHZ.

So their PEAK instruction execution rates vary between 266 and 400 million
instructions/second.  In the benchmark data, you will see a yet larger
range of speeds; this is due to different second level cache speeds and sizes on the
different models (the 21064 has a first level, on-chip, cache). 

Hope this clarifies more than it confuses.

-- 
Digital Equipment Corporation
Cambridge Research Laboratory
Newsgroups: comp.sys.dec
From: ajc@pa.dec.com (AJ Casamento)
Subject: Re: Alpha Prices -- Any Idea out there??
Organization: Digital Equipment Corporation
	<1992Nov10.175108.28116@eng.umd.edu>
Date: 10 Nov 92 16:50:54




In article <1992Nov10.175108.28116@eng.umd.edu> sysmgr@king.eng.umd.edu 
(Doug Mohney) writes:



>> Can you or someone else give us the Real Deal on:

>>	   o	Expansion slots
>>	   o	SCSI and other ports off the back


>>		    Play in the intelluctual sandbox of Usenet 

>>   -- >                  SYSMGR@CADLAB.ENG.UMD.EDU                      < --


Doug,

  You've already seen the write up on the DEC 3000 Model 400 desktop system.
The deskside version of the product (code named Flamingo) is the DEC 3000 Model
500. If you look into your imagination (not too far back) and picture a sort of
wider BA23 enclosure, you'll find:

	o A 150MHz cpu
	o Memory expansion up to 1GB (using 16Mbit DRAMs)
	o Up to 6 half height SCSI devices internal (including two removable
	  media devices) running on a separate SCSI bus from the external port
	o An integral HX frame buffer (does NOT consume a TURBOchannel slot)
	o Six configurable TURBOchannel option slots
	o Your choice of 10bT or AUI for ethernet
	o ISDN
	o An RS423 printer/comm port (MMJ)
	o Keyboard mouse cable
	o An RS232 (25pin Dsub) synch/asynch comm port (this can be console)
	o An external SCSI port (this is a completely separate SCSI bus from 
	  the internal controller)
	

  I don't think I've left out any of the configuration stuff. The TURBOchannel
options that are configurable are slots 0-5. Slot 6 is baseboard I/O and slot
8 is the integral HX.

I hope that helps answer some of your configuration questions.

				Thanx,
				  AJ


      **********************************************************************
      * AJ Casamento			"The question is not whether or    *
      * Digital's TRI/ADD Program	 not the opinions are mine; but    *
      * 529 Bryant Ave. PAG-2		 rather, which of my personalities *
      * Palo Alto, CA 94301-1616	 do they belong to?"		   *
      * 415.617.3460							   *
      * ajc@pa.dec.com  						   *
      **********************************************************************
Xref: sparky comp.sys.dec:5827 comp.os.vms:17618
Newsgroups: comp.sys.dec,comp.os.vms
Subject: Re: RePHRASE: alpha memory requirements (vs vax) ?
From: dan@ttisms.com
Date: 6 Nov 92 19:00:11 PDT
Organization: Touch Technologies Inc., San Diego CA

In article <1992Nov5.130359.1@uwovax.uwo.ca>, brent@uwovax.uwo.ca (Brent Sterner) writes:
> In article <1992Nov5.113540.1@uwovax.uwo.ca>, brent@uwovax.uwo.ca (Brent Sterner) writes:
>>    Just curious about memory demands for alpha.  I'm running a VAX 4500
>> with 128 MB memory.  Of that, SHO MEM tells me "38393 pages are permanently
>> allocated to VMS".  How big is VMS on an alpha system?  (Perhaps someone with
>> an alpha could post the last line from SHO MEM, though it might be misleading
>> if there is a lot of dbugging code still in place.  Perhaps someone inside
>> DEC has a non-debugging system they could use.)  Is there a rule of thumb for
>> typical programs ("alpha memory needs"/"vax memory needs" ~= "constant")?
>> Does a typical user (VAXC or FORTRAN) program require more or less memory on
>> an alpha system?

Hi,

Our tests have shown that ALPHA code uses about 3 times the address
space that VAX code does.  This is typical of RISC systems I am
told...especially when compilers (like the GEM backend used by Digital)
in-line routines and optimize for systems that issue multiple
instructions per clock-cycle.

Dan E. (A few months experience on Alpha)
From: lee@hsh.com (Lee Havemann)
Newsgroups: comp.sys.dec
Subject: Now that Alpha is here......
Date: 12 Nov 92 19:59:16 GMT
Organization: HSH Associates

Now that the new Alpha Vaxes are out, does anyone have a spare KA655 and memory
they care to part with (cheap? :-)

Some of us can't afford to be on the leading (bleeding?) edge of technology....
-- 

 Lee Havemann, Sys_op       HSH Associates          (201) 838-3330 
 Internet: lee@hsh.com    Compuserve: 70410,3507    AOL: HSH Assoc
 "Any opinions expressed are not necessarily those of anyone else, 
  including myself."
From: yzarn@lhdsy1.lahabra.chevron.com (Philip Yzarn de Louraille)
Newsgroups: comp.sys.dec
Subject: Re: ALPHA AXP SYSTEM PERFORMANCE SUMMARY
Keywords: Alpha, AXP, SPEC
Date: 12 Nov 92 01:38:16 GMT
Organization: Chevron Oil Field Research, La Habra, CA.

In article <1992Nov10.154528.27839@ryn.mro4.dec.com> bhandarkar@wrksys.enet.dec.com (Dileep Bhandarkar) writes:
>SPEC performance summary for products announced today:
>
>DEC 10000 Model 610 AXP, @200 MHz
>
>	SPECmark89 	184.14
>	SPECint89       104.52
>	SPECfp89        268.60
>
>	SPECint92	106.54
>	SPECfp92	200.36
>
>
>DEC 7000 Model 610 AXP, @182 MHz
>
>	SPECmark89	167.43
>	SPECint89	 95.06
>	SPECfp89	244.18
>
>	SPECint92	 96.58
>	SPECfp92	182.11
>
>
>DEC 4000 Model 610 AXP, @160 MHz
>
>	SPECmark89	136.23
>	SPECint89	 83.73
>	SPECfp89	188.45
>
>	SPECint92	 83.51
>	SPECfp92	143.10
>
>
>DEC 3000 Model 500 AXP, @150 MHz
>
>	SPECmark89	121.50
>	SPECint89	 73.47
>	SPECfp89	169.89
>
>	SPECint92	 74.30
>	SPECfp92	126.0
>
>
>DEC 3000 Model 400 AXP, @133 MHz
>
>	SPECmark89	108.14
>	SPECint89	 65.80
>	SPECfp89	150.6
>
>	SPECint92	 65.32
>	SPECfp92	112.2

Which OS were these obtained on? VMS or OSF/1? 
-- 
  Philip Yzarn de Louraille                 Internet: yzarn@chevron.com
  Research Support Division                 Unix & Open Systems
  Chevron Information & Technology Co.      Tel: (310) 694-9232
  P.O. Box 446, La Habra, CA 90633-0446     Fax: (310) 694-7709
From: fwj@reg.triumf.ca (JONES,FRED_W.)
Newsgroups: comp.sys.dec
Subject: Re: DECWINDOW,IRIS AND XWINDOWS
Date: 13 Nov 92 06:27:00 GMT
Article-I.D.: reg.12NOV199222270478
Organization: TRIUMF: Tri-University Meson Facility
NNTP-Posting-Host: reg.triumf.ca
News-Software: VAX/VMS VNEWS 1.41

glenn@cloud1.met.fsu.edu writes...
>I am trying to setup my display on a vaxstation model76 using
>vax/vms 5.5 to show a xwindow display on a silicon graphics
>workstation (4d/35) using 4.0.1. os. since i am using
>decwindows on a vms machine and not ultrix ,the set environment
>variable DISPLAY is set by using 'set display/create/node=....'
>i have been unsucessfull in display and xlib window on the
>iris by runing the code on the vax-vms. 
>the iris has permitted access to the vax node by use of the
>xhost command.
> 
> any suggesstions? or do i have to get an ultrix workstation?

Just a guess...

You didn't mention what transport you are trying to use.
The default transport for the VMS  SET DISPLAY command is
usually DECNET, and unless your Iris is running Decnet
the connection will be refused.  [To see the transport
method, type SHOW DISPLAY].

If you have Multinet or UCX or some other TCPIP running on
your VAX, you can try:
  SET DISPLAY/CREATE/NODE=.../TRANSPORT=TCPIP
Your DECWindows installation may also have to be configured to
support this transport method.

Frederick Jones
fwj@reg.triumf.ca
Xref: sparky comp.sys.dec:5804 comp.os.vms:17517