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

Conference lassie::ucx

Title:DEC TCP/IP Services for OpenVMS
Notice:Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:ucxaxp.ucx.lkg.dec.com::TIBBERT
Created:Thu Nov 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5568
Total number of notes:21492

1808.0. "UCX$C_SOCK_NAME or INET$C_SOCK_NAME? 0 or 4?" by HDLITE::NEWMAN (Chuck Newman, 508/467-5499 (DTN 297), MRO1-2/K5) Wed Mar 01 1995 19:27

T.RTitleUserPersonal
Name
DateLines
1808.1Example CodeHAGELN::MyTHM. T. HollingerThu Mar 02 1995 05:0322
1808.2another questionCSC32::J_HENSONDon't get even, get ahead!Wed Dec 18 1996 17:0123
1808.3address in future release of doc?CSC32::J_HENSONDon't get even, get ahead!Fri Feb 14 1997 15:2824
>>              <<< Note 1808.1 by HAGELN::MyTH "M. T. Hollinger" >>>
>>                               -< Example Code >-

>>Hmm, yes, I see that statement in the document.  It's misleading.  Actually,
>>p3 is simply the local IP address you want to bind; you don't need any
>>constant to identify it at all.

			.
			.
			.

>>I'm not sure why UCX$C_SOCK_NAME is mentioned, nor where you would put its
>>value in this structure.

Sorry to dredge up the past, but I just took a beating from a customer
over this.

May I assume that this issue will be addressed in a future release of
the documentation, and that it will always work as it does now?  If
not, I will be glad to elevate this.

Please advise.

Jerry
1808.4Documentation ErrorUCXAXP::MYTHM. T. HollingerWed Feb 19 1997 18:159
Yes, we have no plans to change the behavior.  The statement in the
documentation is misleading, as I said before.  Thanks for the reminder;
I'll ask the writers to get the correction in for V4.2 if they haven't
already.
    
Even if we wanted to change the behavior of the UCX API in this regard,
there are enough existing applications we wouldn't dare break them.
    
        - MyTH