× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.