Yes, that was my understanding too, although I think it may use
WinServer or the Windows Master Browser concept instead of polling the
machines directly. I remember that it used to take forever to do WRKLNK
'/QNTC' the first time; since then they've made changes to how it
discovers Windows shares, and part of that is using MKDIR '/QNTC/xyz'.
On your 2nd point, I was able to use MKDIR '/QNTC/server/share/pdow',
then WRKLNK option 7 to rename that to pdow2, and it does indeed rename
it, as I observed from the Windows side using Win Explorer. And after
the rename, I was able to use WRKLNK option 5 to display the contents of
My guess is that the initial access using WRKLNK '/QNTC' stores the
polled information somewhere, and that a MKDIR command issued from the
iSeries puts its result directly into that somewhere instead of waiting
for the polling to find it, and that subsequent WRKLNKs or EDTFs look at
"somewhere" to get to the QNTC folders. And that somewhere along the
line, that "somewhere" got corrupted.
We tried stopping & starting Netserver, which apparently provides the
QNTC service, but it did not help. Possibly an IPL would do it, but
that's not going to happen anytime in the near future.
*Peter Dow* /
Dow Software Services, Inc.
On 11/14/2012 6:07 AM, Vernon Hamberg wrote:
I'll take a couple guesses here.
The directories in QNTC are usually named by discovery - that is, a poll
is made of Windows machines on the network that looks for file shares.
If you create one of those directories by hand, using the MKDIR command,
you have to use the share name - no "renaming" at that point.
So I think that when you renamed it on the i, it still had a reference
to the original name - that is my assumption.