RE: Netserver Question

[William.Epperson@xxxxxxxxxxxxxxxxxxxxxxxx]

I had problems with connection to /QDLS even when M$ network username/password were the same as the i username/password.  I got around that by mapping
to the connection through an explicit mapped drive using the username/password function (Connect using a different username/password) while mapping
the drive.  It worked for us and I haven't had a problem since.  Like I said, even with the two being the same I still had issues.

Good luck,
Bill Epperson Jr.
Systems Communications Analyst
Memorial Health System
(719) 365-8831




                                                                                                                                              
             "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>                                                                                       
                                                                                                                                              
             Sent by: midrange-l-bounces@xxxxxxxxxxxx                                                                                              To
                                                                     "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>      
                                                                                                                                                   cc
             08/27/2009 09:13                                                                                                                 
                                                                                                                                              Subject
                                                                     RE: Netserver Question                                                   
                            Please respond to                                                                                                 
                  Midrange Systems Technical Discussion                                                                                       
                        <midrange-l@xxxxxxxxxxxx>                                                                                           
                                                                                                                                              
                                                                                                                                              
                                                                                                                                              



Is your userID in the system distribution directory?  QDLS requires
users to have system directory entry (WRKDIRE).
Is GUEST profile enabled in your Netserver configuration?  Perhaps
you're connecting as guest for some reason?
Is your network userid and password the same as your IBM-i user/pass?
If not, then I'd bet your access is by GUEST profile...  Is guest
profile in the directory?

QDLS sucks.

-Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Smith
Sent: Thursday, August 27, 2009 9:45 AM
To: Midrange Systems Technical Discussion
Subject: RE: Netserver Question

"Read/Write" is on the share definition.

Michael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Thursday, August 27, 2009 10:36 AM
To: Midrange Systems Technical Discussion
Subject: RE: Netserver Question

Check your share definition...  Perhaps it is a "read-only" share.

-Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Smith
Sent: Thursday, August 27, 2009 9:29 AM
To: Midrange Systems Technical Discussion
Subject: RE: Netserver Question

Executed #2, and reset the use count.

I was able to delete a file via OpsNav, but not through the Windows
Mapped Drive.

Michael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, August 27, 2009 10:25 AM
To: Midrange Systems Technical Discussion
Subject: RE: Netserver Question

What about step 2?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
"Michael Smith" <msmith@xxxxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
08/27/2009 09:38 AM
Subject:
RE: Netserver Question
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Moving away from QDLS is not an option at this time.

Michael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, August 27, 2009 9:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: Netserver Question

1 - Do whatever you can to move out of QDLS.  You can use other
directories like
CALL QCMD
MD '/mydirectory'
And then you can use iNav to create a share on that and map to that.
IBM
added something called the "IFS" or "Integrated File System" back in V3
I
believe.  Get to embrace it.
If you're stuck on QDLS because of either CPYTOPCD or CPYFRMPCD look at
CPYTOIMPF, CPYFRMIMPF, CPYTOSTMF, CPYFRMSTMF.

2 - Speaking of iNav, it has this nice feature to show you who has locks

on various stream files.
File systems, Integrated File Systems, QDLS (yuck), folder in question,
find file, right click on file, Properties, Use tab, see "In use:",
Details, etc.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
"Michael Smith" <msmith@xxxxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
08/27/2009 08:51 AM
Subject:
Netserver Question
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



We upgraded from V5R1 to V5R2... we are moving to V5R4 in September.



On V5R1, via a Windows mapped drive to /QDLS/PAYROLL... the user could
delete files, after the upgrade and PTF apply the user receives an error
dialog box "file in use".



I have check permissions on /QDLS, they are *RWX.



I realize that this will be an interim problem until V5R4, but any
suggestions on how to resolve the problem would be appreciated.



TIA.



Michael Smith

--
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.

--
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.

--
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.

--
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.