Conference 7.286::multia

774.0. "Lat-X sessions to a cluster service name" by COMICS::JUDD (Geoff Judd. UK TSC. Viables, Basingstoke) Thu May 08 1997 10:07

Hi,
  When you try to create a Lat-X session to a cluster LAT service it fails with
error :

The following error occurred while attempting to start an X session on STANDBY
over LAT
Network routine connect() failed, error=EINVAL
If you have enabled logging (via the Control Panel), please check the log for
any additional information.

However if a Lat-X session is created to the node name services all is OK.
I have a customer reporting this problem and I can also reproduce it. The
customer can create KEAterm sessions to the cluster service and can create Lat-X
sessions from a VXT2000.

The customer is running V3.2 of Multia.

The LAT setup on the VMS node is :

he service STANDBY does exist:

Node Name:   NWSRT1                         LAT Protocol Version:      5.2
Node State:  On
Node Ident:  SYS$ANNOUNCE

Incoming Connections:  Enabled              Incoming Session Limit:   None
Outgoing Connections:  Disabled             Outgoing Session Limit:   None
Service Responder:     Disabled

Circuit Timer (msec):        80             Keepalive Timer (sec):      20
Retransmit Limit (msg):       8             Node Limit (nodes):       None
Multicast Timer (sec):       60             CPU Rating:                  0
Maximum Unit Number:       9999

User Groups:     0

Service Groups:  0

Service Name     Status      Rating  Identification
NWSRT1           Available     69 D
STANDBY          Available     69 D

Has anyone else seen this problem and know how to fix it.

Thanks in advance,

Geoff Judd.                                                                     
          

    DO they have the PCX$SERV network object defined??
    
    PCX$SERVER     0  SYS$SYSTEM:PCX$SERVER.COM  PCX$SERVER$S
    
    Does the file SYS$SYSTEM:PCX$SERVER.COM exist and at V5.00 or greater??
    
    Jim Z
    

Hi,
  Yes on our internal system on which I can reproduce the problem I do have the
PCX$SERVER object defined and the version of the PCX$SERVER.COM is V5.00.

Thanks,

Geoff.

I think PCX$SERVER is not used when opnening a LAT-X-SESSION. I can also
reproduce the problem here with our cluster.

I can open a LAT-X-Session from my VXT to our cluster ZUR01 without any
problems. On the MULTIA (3.2 / Xserver V2.2.451) it fails with the same error
message.

A LAT-X-Session to one specific node of the cluster is no problem. And I think
in the early VXT-times we had the same problem there. I would open an IPMT to
find out, if it is an expected behaviour or a bug.

andre 

Andre,

      Thanks for trying it out. I am in the process of writing the IPMT now.

Geoff.