Conference iosg::all-in-1

2664.0. "Remote DDS and ALPHAs" by VMSNET::C_ESTES () Wed May 07 1997 13:01

    Good morning or afternoon,
    
    
    Please explain to me what goes on when an ALPHA is using remote DDS. I
    have a customer that cannot get this to work to save his soul and I
    cannot seem to help him. I set this up on a system here in Atlanta
    without a problem.
    
    After successfully getting the manager's entry and the useragent in DDS
    the manager still cannot access it. When we go into EM we get the
    dds-e-netiofail, network aborted logical link. I cannot resolve this
    error. Looked at some of the netserver.log files located in
    [mb$.dds.scr] it was complaining about process needed SYSLCK priv.
    Looked at the ALL-IN-1 account and it had syslck priv both as default
    and authorized. Looked at the oa$main image and it is installed with
    syslck priv as is dds$shar.exe and dds$lstn.exe. 
    
    Talked to another specialist and they seemed to think that mbmanager or 
    ddsnet acounts needed syslck priv. Added this to no avail.
    
    Looked at the logicals defined in the table dds$config and they had to
    correct information. 
    
    Any help you can give me will be greatly appreciated. Alot of man hours
    has gone on this customer and he/we still cannot get it right.
    
    Thanks,
    
    Cheryl Estes  
                                       

        The only other thing I can add is that the UA name must be "OA$" +
        "AXP node name or cluster alias" + "ALLIN1".
        
        Dave Zaniewski

    HI Dave,
    
    The useragent name is oa$kita2$allin1, where kita2 is the name of the
    Alpha. 
    
    Thanks,
    Cheryl

    syslck error from the DDS Listener is usually symptomatic of the image
    not being installed correctly. Is the remote target a cluster? 
    
    Netiofail/aborted logical link could be a mis-config; make sure the
    DDS node number specified when you execute dds$startup is correct.
    
    Dave