QNTC discovery process

["Clapham, Paul" <pclapham@xxxxxxxxxxxxx>]

I recently configured our network to use the QNTC file system, so that our
iSeries system could access files on a particular W2K server. The systems
are in the same domain, and there's a network user with the same password
that's authorized to access those files. So on the iSeries I typed

WRKLNK '/qntc/server-name/share-name/*'

and it came back with a display of the files in that share. Only problem
was, it took about five hours to do that. Apparently it had to examine every
computer in the domain, which is a continent-wide WAN with nearly 600
systems.

I found an IBM document (technical document 21405625) which explains this
process, and I found several entries in this list's archives alluding to it
as well, but nothing that specifically addressed my problem. Which is: Why
does this extensive discovery process happen when I specify the server name?
Or alternatively, how can I prevent it from happening? This is particularly
inconvenient since the results of the discovery process don't survive IPL,
which we do weekly.

Or is it only WRKLNK that has this feature? If I just do MKDIR
'/qntc/server-name/share-name' will QNTC just examine that one server? I
realize that I could test this myself, but I haven't found any way to reset
QNTC so I only get to do one test per week.

PC2