|
Adam, one requirement that has tripped me up is that the user accessing QDLS through a share must be registered in the system directory. A variety of factors can come into play, for example, Netserver "Guest" access might be the profile that is used to access the share if the users PC username and password are not identical to the as400 user/passwd. In this case, the "guest" profile would need to be registered in the system directory. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: Adam Lang [mailto:aalang@xxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, September 02, 2003 2:46 PM To: Midrange Systems Technical Discussion Subject: Re: Error copying documents "> Please understand that often the new file from a GUI application may be > called something like "New copy of oldfile.txt". That, does not fit into > the 8.3 scheme forced by QDLS. That's just one of the many limitations of > that directory." I'm copying the files FROM the as/400 to a windows PC via network share. I can't pick a different directory because the files I need to copy down off the AS/400 are there. ;) ----- Original Message ----- From: <rob@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, September 02, 2003 3:15 PM Subject: Re: Error copying documents > There are just too many limitations to the QDLS file system. I strongly > suggest picking a different directory. You can set up shares on these > other directories. > > Do you get this same error when you try to do this on a different > directory, not under QDLS? > > Please understand that often the new file from a GUI application may be > called something like "New copy of oldfile.txt". That, does not fit into > the 8.3 scheme forced by QDLS. That's just one of the many limitations of > that directory. > > Rob Berendt > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > Benjamin Franklin _______________________________________________ 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.