Or better yet thread safe vs. non-thread safe.....not sure where my head
was.....
Michael Crump
Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302
765.741.7696
765.741.7012 f
Motivation
If a pretty poster and a cute saying are all it takes to motivate you,
you probably have a very easy job. The kind robots will be doing soon.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Crump, Mike
Sent: Wednesday, May 28, 2008 1:17 PM
To: Midrange Systems Technical Discussion
Subject: RE: Mapped Network Drive
I'm wondering if you are seeing symptoms regarding multi-threaded and
not multi-threaded....
From the memo to users for V5R4....
3.48 iSeries NetServer changes affecting thread behavior
A Microsoft Windows file-serving client (such as Microsoft Windows
operating systems, Linux/Samba, or the iSeries QNTC file system) that
accesses a
non-threadsafe file system using the iSeries NetServer might receive
access
denied type errors.
As of V5R4, iSeries NetServer services file shares in a multithreaded
job by
default. The threaded activity for all sessions in a subsystem runs in
the
pool of threads in the QZLSFILET job for that subsystem.
A client that is running in a threaded environment will receive
access-denied
type errors when it attempts to access a non-threadsafe file system
(such as
QDLS, QNetWare, or QSYS.LIB access of save files); similarly, the client
will also receive errors when attempting to map a drive to a
non-threadsafe
file system. For a listing of file systems that are not threadsafe, see
"File system considerations for multithreaded programming" in the
Multithreaded applications topic in the iSeries Information Center.
Michael Crump
Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302
765.741.7696
765.741.7012 f
Motivation
If a pretty poster and a cute saying are all it takes to motivate you,
you probably have a very easy job. The kind robots will be doing soon.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Wednesday, May 28, 2008 10:46 AM
To: Midrange Systems Technical Discussion
Subject: RE: Mapped Network Drive
John,
NetServer was up and running. Going through the troubleshooting
section, I didn't find anything "newsworthy" to try.
As a last ditch (desperation) effort, I stopped iSeries NetServer on the
offending system. Then restarted it using the "Reset and Start" option
in iNav. Life is now wonderful (except, of course, that I'm using the
QDLS folder).
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US)
Sent: Wednesday, May 28, 2008 8:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: Mapped Network Drive
Is NetServer up & running?
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzahl/rzahlu
sergoal.htm
Is the Guest User Profile enabled? (See Administer iSeries NetServer in
above link)
--
John A. Jones, CISSP
Sr. Analyst, Global Information Security
Jones Lang LaSalle, Inc.
Voice: +1.630-455.2787
FAX: +1.312.601.1782
Email: john.jones@xxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Wednesday, May 28, 2008 8:29 AM
To: Midrange-L (midrange-l@xxxxxxxxxxxx)
Subject: Mapped Network Drive
I am having an "issue" with mapping the QDLS folder (don't give me any
grief about that, please). I have two 520 systems both at V5R4. One
system maps QDLS fine. The other system, however, refuses to map it
even though it did map a couple of weeks ago. Whether I use Windows
Explorer or iNav, I get an error that "Access to the specified share is
denied."
Since one system maps fine, I checked the security. Both have *Public
*RWX access. The system for which the mapping worked did not ask me for
a user id and password, but the failing system does. Even using QSECOFR
doesn't work, although it gives me a different error (dialog box):
"Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all previous
connections to the server or shared resource and try again." I am not
sure that I understand this message, but it sounds like it thinks I
already have a connection to the folder. But, when I run "Disconnect
network drive..." in Windows Explorer, it does not show up; though, when
I try to use Explorer's "Map Network Drive..." function and look at the
drop down list in the 'Folder' element, I do see the folder.
For what it's worth, I had to disconnect the network drives for both
systems yesterday to re-assign drive letters. One system, as I said,
re-connected fine using another letter (X). Tried using Q and Y for the
second system with the same results. I even tried stopping the file
share in iNav (worked) and re-starting the share (again, worked), but I
still could not map the folder to a network drive. Also, I am running
Windows XP with SP2 on my PC.
Thanks.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
--
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 email is for the use of the intended recipient(s) only. If you
have
received this email in error, please notify the sender immediately and
then
delete it. If you are not the intended recipient, you must not keep,
use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of
transmitting
software viruses, but we advise you to carry out your own virus checks
on
any attachment to this message. We cannot accept liability for any loss
or damage caused by software viruses. The information contained in this
communication may be confidential and may be subject to the
attorney-client
privilege. If you are the intended recipient and you do not wish to
receive
similar electronic messages from us in the future then please respond to
the
sender to this effect.
--
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.
midrange.com
