|
Make sure that the share is not defined as "Read Only"... Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-297-2863 or ext. 1863 -----Original Message----- From: Ruedi Graetzer [mailto:GRAETZR@xxxxxxxxx] Sent: Friday, February 25, 2005 9:52 AM To: midrange-l@xxxxxxxxxxxx Subject: RE: IFS NTFS cannot copy No I try to copy it to a "normal" directory in the IFS. I recognized followings: copying from Win Server 2003 directory to AS/400 IFS directory --> doesn't' work. copying from Win Server 2003 directory to local client (C:\) and then to AS/400 IFS directory --> doesn't' work. If I open the word file with word, change a character in the document and save it back to c:\ after that, I can copy it from the local client C:\ drive (directory) to AS/400 IFS directory ! ! ! Regards Ruedi Dimminaco AG Ruedi Graetzer P.O. Box Zürichstrasse 12 CH-8134 Adliswil, Switzerland Phone: +41 1 712 32 82 Mobile: +41 79 308 49 40 Fax: +41 1 712 33 05 >>> michael@xxxxxxxxxxxxxxxxxx 25.02.2005 15:40:26 >>> Are you copying to the QDLS folder in the IFS? That has the 8.3 naming convention restriction. > -------- Original Message -------- > Subject: IFS NTFS cannot copy > From: "Ruedi Graetzer" <GRAETZR@xxxxxxxxx> > Date: Fri, February 25, 2005 3:55 am > To: midrange-l@xxxxxxxxxxxx > > Hello > My Windows 2K workstation has one active drive to a windows 2003 server and one to the integrated file system on iSeries (V5R2). > > I would like to copy a word-file from the Windows Server 2003 drive to the IFS drive. > I always get the message "cannot copy (filename) the network request is not supported" > (I got some information about reparse points...?) > > Thanks for your tips & hints > > Regards Ruedi > > > Dimminaco AG > Ruedi Graetzer > P.O. Box > Zürichstrasse 12 > CH-8134 Adliswil, Switzerland > Phone: +41 1 712 32 82 > Mobile: +41 79 308 49 40 > Fax: +41 1 712 33 05 > > > -- > 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.
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.