By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,288 Members | 1,290 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,288 IT Pros & Developers. It's quick & easy.

SEARCH / KNOWN discovery question

P: n/a
Hi,
I understand that the dbm cfg parameter "DISCOVER" controls whether
Search or Known discovery is applicable. Additionally, Search discovery
provides a superset of Known discovery. I completely understand the
scenario where SEARCH is applicable and where KNOWN is applicable.

My question is very basic:
From a server's perspective, what extra is being done at the server to

support SEARCH discovery? Are some extra proceeses / threads started
for "SEARCH" that are not started for "KNOWN"?

In DB2 v7 documentation, I read that If discover = SEARCH when DB2ADMIN
starts, then search discovery connection managers for each of the
protocols specified in "discover_comm" (admin cfg parameter) are
started. In addition, connection managers for each of the protocols
specified in the DB2COMM registry variable are started. This allows the
administration server to handle search discovery requests from clients.
If discover = KNOWN when DB2ADMIN starts, then only the connection
managers specified in the DB2COMM registry variable are started.
I do not think that this is applicable to v8 as there is no
"discover_comm" parameter in admin cfg.

As basic as this may seem to you all, I am still searching.

Thanks...........anurag

Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.