Conference lassie::ucx

5418.0. "problem unregistering a service, UCX 4.1" by HYDRA::DONSBACH (Jeff Donsbach, Software Partner Engineering, DTN 297-6862) Mon Apr 07 1997 18:18

    
    I got the following question from a software partner that I have
    no clue about, so that is why I'm here. I tried doing a little
    preliminary searching and to my untrained eye, this problem looks
    like it might be somehow related to the issue(s) in 3707.* and 2147.*.
    But I know very little about ONC/RPC programming so I'm not sure.
    I'd appreciate it if an expert could give me some thoughts on this.
    
    Thanks,
    -Jeff
    Here is the question from the partner:
    
    -------
    Hello,
    
    I am running OpenVMS 7.1 with UCX 4.1 - ECO Level 2.
    
    Problem :
    
     A server can register with both the TCP and UDP protocols and when the
    server shuts down it then issues a pmap_unset. The UDP protocol is
    unregistered correctly by the UCX Portmapper but the TCP entry is still
    listed.
    
     The problem that I and my customers see is that the UCX portmapper
    keeps track
    of the servers "PID" number and associates the number with the TCP
    entry. Now if
    the server tries starting under a different "DECterm or PID",
    the portmapper denies access.
    
     The only way to remove the entry is shutdown the portmapper.
     On typical ONC/RPC platforms such as Unix both the TCP and UDP entries
     are removed.
    
     Is there is a fix ???
    

    
    I have never seen this problem.  It doesn't make sense that the UDP
    service would unset and the TCP one fail to do so, unless the
    application didn't send the unset for it.
    
    On OpenVMS, we are more security-minded.  Hence, an application which
    registers a service cannot have its registration superseded by another
    process with a different PID.
    
    If you can provide example source demonstrating the problem and submit
    it with an IPMT, it will be addressed.

    I'll ask the partner for a code example and file the qar/ipmt as
    soon as I get it...
    
    Thanks,
    -Jeff D.
    

    
    The partner can't provide a code example right now. I guess I'm on
    my own to reproduce the problem.
    
    One bit of info I think I forgot to mention in .0 is that the
    partner is registering his service with both UDP and TCP via
    ONC/RPC.
    
    Is ONC/RPC part of UCX, or is it a layer on top of it that is a
    separate product? If so, maybe I'm in the wrong place to begin
    with....
    
    Thanks,
    Jeff
    

    It's part of UCX, implemented as a set of callable library routines.