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


  1.  Home
  2. MIDRANGE-L
  3. August 2006

Re: Replacing a file to QDLS
Could it be the patch level of Windows that the two users are using? I know that there have been compatibility problems with WinXP and QDLS 

Here's info on the one I know of:
  http://tinyurl.com/n5qk3
The other possibility is authority... Make sure they're enrolled in the system distribution directory (WRKDIRE) this is a peculiarity of QDLS. It sounds like you've already chedked other authority possibilities.
Frankly, you should be working on eliminating QDLS and using the root filesystem. It's 2006. The 8.3 filename paradigm has been dead for more than a decade now. QDLS is, it can't handle multi-threaded jobs, it has problems with compatibility with newer operating systems, it has a very bizarre security model. It's time to upgrade! 

---
Scott Klement  http://www.scottklement.com

On Tue, 1 Aug 2006, Kendall Kinnear wrote:


I'm having a problem with updating a file in a QDLS directory using
NetServer. There is a file "xxx.txt" in directory "\QDLS\YYYY". I have
one user who can replace the file using DOS copy and another user who
cannot (i.e. copy c:/dir/xxx.txt i:/xxx.txt). Both users have all data
and object rights to the file and the directory. The directory is mapped
as the "I:" drive on both PCs. Neither ID is disabled. I don't get any
security events logged. Both users can see and read the file in Windows
Explorer. By the way this is a V5R1 system. It looks like it should be
working but I'm missing something.

I've run out of ideas to check, can anyone direct me?

Kendall Kinnear
System i5 Architect
Stonebridge

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.