[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference tuxedo::dce-products

Title:DCE Product Information
Notice:Kit Info - See 2.*-4.*
Moderator:TUXEDO::MAZZAFERRO
Created:Fri Jun 26 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:10003

1833.0. "DCE 2.0 eft - getcellinfo fails" by COMICS::HOWLAND () Fri Apr 19 1996 13:47

T.RTitleUserPersonal
Name
DateLines
1833.1Need patch kitTUXEDO::FARRELLJacqueline Proulx FarrellMon Apr 22 1996 14:1411
1833.2GETCELLS.EXE probs. on VMS-ALPHAFOUNDR::BLANCHARDWed Apr 23 1997 17:4623
    I've recently installed DCE on a Alpha VMS (v7.0) system, using UCX (
    think it was version 4, don't really recall, but it is recent) , it
    also has DECnet running.
    
    UCX is up and running (ping, telnet etc. all work) and the "_ack"
    parameter is disabled.  There are no error messages.
    
    When I configure DCE to be a server all goes well, provided I don't
    allow DCE to search for cells (The DCE com file runs
    SYS$SYSTEM:DCE$GETCELLS.EXE to accomplish this).  On my other VAX
    systems I can "run getcells.exe" and it returns results, however on the
    Alpha system the getcells.exe goes off into never-never land and does
    not return.  I can control-C out of it.
    
    Anyone have any idea around what getcells.exe uses to gather cell
    information?  I assume it does UCX calls to go out and do its tasks? 
    What should I look for, I've tried everything?
    
    Thanks for any ideas.
    
    
    Dennis
    
1833.3check netmaskTUXEDO::CHUBBThu Apr 24 1997 10:4213
    'getcells', at least on Unix, uses broadcast RPC's to send out a
    request for all cells to report themselves back to the originator.  The
    originator build a list from the responses and presents the list to the
    user.
    
    My only advice is to make sure you have you netmask set correctly.  If
    you were on a network with netmask 255.255.0.0 but you had set your
    machine to 255.255.255.0 then best case you wouldn't hear back from
    some of the machines.  If the reverse was true, and you were trying to
    broadcast to more machines than were on your LAN then perhaps it could
    hang, but that's just speculation.
    
    -- brandon