Conference bulova::decw_jan-89_to_nov-90

Dennis,

   I do the following on our cluster CI nodes and it works like a champ. Note
that normally, each CI cluster member does not have a LAT service defined, only
the cluster alias service.

$DEF DECW$INSTALL_XTERMINAL true
$@sys$manager:decw$startup
$mc latcp create service /ident="VT1000 host service"


-Ken

>    -SYSTEM-F-NOLOGNAM, no logical name match
>    %DECW-W-ATT_FAIL, failed to attach transport TCPIP

I can't help you with the LAT problem, but getting a "no logical name
match" error from UCX is a symptom of the network not being started.
(The logical name it can't find is BG0:)

Have you put @SYS$STARTUP:UCX$STARTUP in SYS$MANAGER:SYSTARTUP_V5.COM?

    Starting UCX fixed the TCP/IP Transport problem but the LAT problem is
    still happening same as mentioned in .0.  I thought it might have been
    a timing issue around when LAT gets started on the system versus
    DECwindows but moving the LAT startup has no effect.
    
    Thanks

	
    I have the same problem with TCP/IP. We have two installations of
    UCX1.2 which are running very successfully, but both of them don't know
    the logical BG0: mentioned below. I get the same error message when
    starting DECwindows, even if UCX is running.
    
    Thomas Wagenblast
    
## >    -SYSTEM-F-NOLOGNAM, no logical name match
## >    %DECW-W-ATT_FAIL, failed to attach transport TCPIP
## 
## I can't help you with the LAT problem, but getting a "no logical name
## match" error from UCX is a symptom of the network not being started.
## (The logical name it can't find is BG0:)

    Hi folks,
    
    1.) I am all set with TCP/IP now. There was a strange effect:
        - I tried to SET DISPLAY to my own VMS machine via TCP/IP. In UCX
          the node is defined in lower case with an alias IN UPPER CASE.
        - It doesn't work if I enter the node name into the security menu.
          The security menu converts the node name to UPPER CASE, maybe 
          UCX doesn't handle the alias correctly here...
        - It only works if I enter "*" for the node name.
    2.) LAT still doesn't work. Error message in DECW$SERVER_0_ERROR.LOG:
    		%DECW-W-ATT_FAIL, failed to attach transport LAT
    		-SYSTEM-F-NOLOGNAM, no logical name match
    
    Any hints?
    Thomas Wagenblast

    Re: .0
    
    I know this isn't the answer you want: LAT is not supported (yet) for
    use as a transport when connecting TO a VMS server.  It is supported
    for going from a VMS client to a VT1000 server.
    
    I don't know when support will be provided for the LAT transport being
    used as a transport by the VMS server.
    
    James

    After reading the previous and prior to getting everything hooked up
    and working, I was really confused.  Now that I have the VAXstation
    3100, DECstation 3100, and VT1000 hooked up and working, every seems to
    make some sense.  For others who are still confused, I'll try to
    summarize here how LAT, TCP/IP, and DECwindows all work together on the
    VT1000.
    
    Processing on the VT1000 can be broken into 2 parts.  Outbound
    connections and inbound connections.
    
    Outbound connections can be accomplished using 3 methods.
    
    1) LAT connections to any system running LAT on the network.  This is
    exactly like a terminal connected to a terminal server or a PC running
    LAT.  The VT1000 opens a window on the terminal and communicates with a
    host on the network using LAT and looks like a VTxxx terminal.
    
    2) TCP/IP terminal connection to any ULTRIX system running TCP/IP or
    VMS system with VMS/ULTRIX Connection installed.  Again, a terminal
    window is opened on the VT1000 and the terminal communicates with hosts
    on the network that accept TCP/IP TELNET connections.
    
    3) Finally, and most confusing until I started it up.  After you have
    configured the VT1000 to download fonts from a system on the network,
    you can request a LAT X session to be started on a host on the network. 
    You receive the DIGITAL logo and Username/Password screen identical to
    a workstation.   After logging into the system, you have the same
    session manager screens as if you were logged into the workstation
    graphics head directly.  If you do a $ SHOW DISPLAY you will see that
    the NODE name is LAT_08002Bxxxxxx where 08002Bxxxxxx is the ethernet
    address and LAT node name of the VT1000.  The transport is LAT.
    
    OK, now for incoming connections - DECwindows/Xwindows clients
    connecting to the server image on the VT1000.  You can receive
    DECwindows clients from VMS or ULTRIX nodes in the network with either
    TCP/IP as the transport or LAT as the transport.
    
    TCP/IP transport.  From an ULTRIX system or VMS system with UCX, you
    can run an application (client) and direct the display to the VT1000.
    On VMS $ SET DISPLAY/CREATE/NODE=<IP node name>/TRANSPORT=TCPIP
    On ULTRIX # SETENV DISPLAY <IP node name>:0
      or -display <IP node name>:0
    This is no different from sending clients to the VT1000 than any other
    workstation with TCP/IP as a transport.
    
    LAT transport.  I have only tried this from VMS to date.  Once I
    decoded the LAT node name it was easy.  From VMS you enter the
    following:
    
    $ SET DISPLAY/CREATE/NODE=LAT_08002Bxxxxxx/TRANSPORT=LAT
    
    DECwindows applications run after this command appear on the VT1000. 
    
    Beware that you need fonts loaded from a system on the network to run
    most applications under TCP/IP and LAT transports.
    
    General notes:  Performance of applications on the VT1000 appear to be
    much slower than the same application and same transport on other
    servers (VS3100, PC DECwindows, DS3100) I'm not sure if this will
    improve with the FCS microcode.
    
    Font downloading takes too long.  Again, I'm not sure where the delay
    is but a couple of minutes to load fonts (VT1000 is locked during
    this time) is too long.  Also happens when I enter APPLY and again when
    I enter OK.  Why twice.
    
    Reloading fonts every time you quit the local window manager or VMS
    session manager seems to be inefficient?

>    Font downloading takes too long.  Again, I'm not sure where the delay
>    is but a couple of minutes to load fonts (VT1000 is locked during
>    this time) is too long.  Also happens when I enter APPLY and again when
>    I enter OK.  Why twice.
   
   OK is usually equivalent to pressing APPLY, followed by a DISMISS (which
   isn't usually in most dialog boxes).  So you should probably just press
   OK.
   
   James