|
Jay,
There really isn't any "trick" to it, and you don't appear to be doing
anything wrong. The error simply means that the FTP server can't find a
file with that name at that location.
I suggest verifying to make sure there aren't any blanks or other
unprintable characters in the filename. I've run across situations
where people have made a file named "text.TXTbbbb" (where "bbbb" are
blanks) by accident. Since you can't see the blanks, it can cause a lot
of confusion.
Aside from that -- my only suggestion would be that you're not really in
the directory you think you are. For example, if you're accessing from
Windows via a mapped drive, you may think that \\server\ptenctest2 is
the same as IFS path /ptenctest2, but it isn't necessarily -- you can
create a Windows Networking Share with the name ptenctest2 that's
located somewhere different in your IFS from /ptenctest2. So to verify
the file location, I recommend using something like WRKLNK or a Unix
shell instead of a mapped network drive to avoid confusion.
Good luck
-SK
On 11/13/2020 1:37 PM, Jay Vaughn wrote:
I thought for sure I was doing this right (and have done before)... but--
can anyone tell me why this cannot find the file on the remote i IFS?
I can assure you the file is there plain as day.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.