|
I'm thinking these should be two separate threads: QNTC and NFS. They
are separate.
QNTC
If I do a WRKLNK '/QNTC' I too will see a lot of DDIR's. They will match
the name of PC's that exist within our network. Your system may, or may
not, have ever tried connecting to them. There is an option in QNTC to go
out and poll your network for these machines or not. There are pro's and
con's to doing so. I'll be darned if I can remember where this is.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1018146
NFS:
NFS supports both serving and consuming.
For serving you should run this before attempting to end tcp
EXPORTFS OPTIONS('-U -A')
ENDNFSSVR SERVER(*ALL)
And all current versions of IBM i require you to end tcp BEFORE the ENDSBS
*ALL or stuff will be left hanging.
For consuming you should run the appropriate UNMOUNT
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Jim Franz <franz9000@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/07/2014 04:53 PM
Subject: determine where mapping definition exists for /QNTC
directories
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
We have a large list of DDIR in /QNTC.
Cannot find a product or app (so far) that created these.
a WRKLNK display (opt 5) of the directory does reveal more info.
a WRKLNK display (opt 8) attributes does not display info related to the
what server these live on.
Win Explorer spends just keeps spinning getting list of directories (we
always cancel
This could be some baggage from programmers long ago, or something current
in our variety of products that have Win clients and servers interacting
with the Power i.
Last night the ENDTCPSVR *ALL failed to end all the NFS server components
-
no error message, just 8 hrs before we cancelled the job.
Not an option to kill this without understanding it first.
V7R1
Jim Franz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.