T.R | Title | User | Personal Name | Date | Lines |
---|
3041.1 | /tran=tcpip is only for UCX | STAR::ORGOVAN | Vince Orgovan | Thu Jul 05 1990 19:39 | 19 |
| The DECwindows supplied TCP/IP transport with VMS V5.3 works
only with DEC's Ultrix Connection (UCX) product. Running
DECwindows applications with third party TCP/IP packages is
possible, provided that the third party also supplies a
DECwindows transport image that maps the DECwindows read
and write requests into calls for their private TCP/IP
programming interface.
I know that Wollongong ships a DECwindows TCP/IP module
with their WIN/TCP product. To use it, you do something like
$ set display/create/node=SUN/transport=wintcp
which causes their decw$transport_wintcp.exe image to be
activated. I don't know whether Excelan ships a DECwindows
transport with their product or not.
So your customer either needs to talk to the Excelan folks
or use UCX.
|
3041.2 | thanks for the explanation | CSC32::B_BRADACH | | Fri Jul 06 1990 13:36 | 5 |
| Thanks for the quick response, I appreciate the explanation
I will relay this to customer.
bernie
csc/cs
|
3041.3 | sun => vms display problems | LEXIS::JJOHNSON | Badges?!? We don't need no stinkin badges! | Tue Jul 17 1990 14:37 | 29 |
| Hi,
I was at a customer site last week to install a VAX 4000. They are
primarily a U*X shop with both Sun's and DECstations.
We were running UCX V1.2 on the 4000 and two VS3100's clustered
togather.
We had very little problem getting DECwindows applications to display
on the Sun's but we had no luck at all trying to get Sun applications
to come up on the VAXstations. We also couldn't get the DS3100 to
display on the VS3100, they all came back with
xtoolkit error "can't open display"
Both sides could telnet and ftp to each other. We tried all kinds of
security settings in the customize security box from node username ,
node uid and finally * * to no avail. Note we were listing tcpip as the
transport. Both sides had each others node and address in the hosts
file.
Their X expert seems to think that the VMS systems are not listening on
port 6000 which as he said was the port used by default for
applications. They tried to telnet through port 6000 and could not but
they could telnet through port 23 (telnet's default).
Any help and/or suggestions would be appreciated.
Jim
|
3041.4 | You must create DECW$PRIVATE_SERVER_SETUP.COM | STAR::VATNE | Peter Vatne, VMS Development | Tue Jul 17 1990 15:09 | 6 |
| I believe you are missing the step where you define the transports
that the server will listen on. Take a look a the directions in:
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE
This is all explained in the VMS V5.3 Installation Guide.
|
3041.5 | Right & Thanks | LEXIS::JJOHNSON | Badges?!? We don't need no stinkin badges! | Thu Jul 19 1990 16:15 | 12 |
|
Hi,
You are/were exactly correct.
All we had was the bookreader CD and all I could find were the CPU
specific installation guides which didn't have any DECwindows
customization info. I appreciate your time.
Thanks,
Jim
|