| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2028.1 | | DECWIN::JMSYNGE | James M Synge, VMS Development | Thu Jan 11 1990 09:46 | 9 |
| Poor man's routing is not supported by the X protocol, nor by our
implementations.
The only protocols I know of which support poor man's routing are DAP
(File transfer) and MAIL. And DAP's support seems more like a nice
side effect than something which require's significant support (at
least on VMS).
James
|
| 2028.2 | Notes 2.1 also supports PMR | BLOCKP::neth | Craig Neth | Thu Jan 11 1990 11:25 | 0 |
| 2028.3 | | PSW::WINALSKI | Careful with that VAX, Eugene | Fri Jan 12 1990 18:23 | 7 |
| RE: .1
MAIL and FAL support poor man's routine due to historical accident. The feature
was required back in the DECnet Phase 2 days, before DNA got a routing layer.
The feature was never taken out of the MAIL and FAL network objects.
--PSW
|
| 2028.4 | It's easy if they're on the same LAN | GOFER::HARLEY | Confidentially... I AM A WABBIT!! | Sat Jan 13 1990 11:30 | 5 |
| Are both nodes on the same LAN? If they are, you don't need to use PMR,
just make sure that each node has the other one defined in their
Netnode_Remote databases.
/Harley
|
| 2028.5 | Yes you can do this | YUPPY::CONNOLLY | NORTON owners club member | Mon Jan 15 1990 09:37 | 6 |
| re .4
Yes, we use this quite successfully in London between our workstations
(area 62) and the bootnode/compute engine/x-client (area 41).
Gerry
|
| 2028.6 | how do I define node in my "network database" | HANNAH::OSMAN | see HANNAH::IGLOO$:[OSMAN]ERIC.VT240 | Thu Nov 15 1990 13:17 | 13 |
|
I want to run a DECwindows client on node RANI which is area 55, and display
the windows on my screen on node OSMAN, which is a VS2000 running EWS, and
is a hidden node in area 62.
If OSMAN were vms, I'd know how to say
$ mcr ncp set ndoe rani address 55.xxx
$ mcr ncp define node rani address 55.xx
But given that OSMAN is EWS, how do I do it ?
/Eric
|
| 2028.7 | | KELSON::GULDENSCHUH | Success lies in achieving the top of the food chain. | Thu Nov 15 1990 14:19 | 8 |
| Is RANI on the same LAN as OSMAN? If so, just
RANI> SET DISPLAY/CREATE/NODE=OSMAN
If not, you'll have to use the VT1000/VT1200 DECW$DWT_DECNET thru OSMAN's
host node.
/s/ Chuck
|
| 2028.8 | please explain more about this DECW$DWT_DECNET thing ! | HANNAH::OSMAN | see HANNAH::IGLOO$:[OSMAN]ERIC.VT240 | Thu Nov 15 1990 15:24 | 31 |
|
The EWS node OSMAN is booted from node LEVEL, which is in area 55. OSMAN
is hidden area 62. Actually, LEVEL is part of the HANNAH cluster, and the
hidden area 62 that OSMAN is in is seen by HANNAH.
So, if I just run a DECwindows application from my DECterm, the default is
that the application is running on LEVEL with its windows appearing
on OSMAN.
That combination works fine.
The trouble crops up when I set host from LEVEL to RANI, which happens
to also be in area 55 but is *not* part of the HANNAH cluster.
From RANI, I attempt this:
$ set display/create/node=osman
$ run sys$system:decw$clock ! for example
I always get
% client is not authorized
even though I authorized RANI::OSMAN on the OSMAN workstation in "customize
security".
If this DECW$DWT_DECNET thing helps, please tell me more about it.
Thanks.
/Eric
|
| 2028.9 | Use Node Address 55.673 Instead of RANI in Your Security Database See Users Manual | JEANNE::KEELER | Gary N. Keeler 235-8634 | Thu Nov 15 1990 15:49 | 1 |
|
|
| 2028.10 | got hidden area working, thanks. | HANNAH::OSMAN | see HANNAH::IGLOO$:[OSMAN]ERIC.VT240 | Thu Nov 15 1990 16:41 | 12 |
|
The trick turned out to merely be to customize security the number
55.673
instead of the node name
RANI
Thanks.
/Eric
|