|
The Help for 11.0.1.2276 says that "When the client and server are both on the same computer, an empty string is returned" but that's not completely correct. When the client is an EVENT, it returns 'NA'. Does that mean 'Not Applicable'? Likely answer: "Gosh, what do you think, Breck?" <g> And here is another stupid question: Does it return 'NA' for SERVICE connections as well? ( I don't have any of those that last long enough to see :) SELECT * FROM sa_conn_properties() WHERE PropName = 'NodeAddress'; Number,PropNum,PropName,PropDescription,Value 1000000107,193,'NodeAddress','Client node address','NA' 1000000021,193,'NodeAddress','Client node address','NA' 177,193,'NodeAddress','Client node address','' Comment Text Removed
|
|
I can confirm that result for 11.0.1.2376, and it's the same with 9.0.2.3886. And even for good old 7.0.4.3541 sa_conn_info() shows NA for an event's connection. Looks like it's always been there. So that might be the right time to request a documentation update (I don't have to point to to DCX, I suppose). Have you seen what it shows for a SERVICE connection? ( I'm too lazy to test :) 2
I can confirm that internal connections, such as events, show NodeAddress as NA and that means Not Applicable. @Breck: Web service requests show the NodeAddress as being the TCP/IP address of the client. I have sent a request to the doc team to update the info re. NA values. 1
FYI: Any of the connection properties relating to communication (e.g. CommLink, CommProtocol, Compression, ...) will all return "NA" if the request is running as part of an event or other internally generated process. @Breck: I must admit that I don't know what "SERVICE connection" means. So I didn't test that. |
