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




I'm wondering if someone can help me with the syntax for changing to a
local directory on our AS/400?  When I check the directory through
Windows Network Neighborhood, I have a directory located in \\QSPS\AFON

This is actually a UNC path, which contains the name of a server, and the share on that server. There's no directory in the path that you've posted (though it's possible that you have an IFS path called "AFON", if you named the share the same way that you named the directory.)


When I use the FTP command in the AS/400, how do I change to this local directory? When I just type LCD, it tells me that the current local working directory is QGPL.

Assuming that /AFON is the name of a folder in your IFS, you first need to use the IFS file naming convention instead of the traditional lib/obj naming convention. To tell FTP that you want to do that, type:

   LOCSITE NAMEFMT 1

(LOCSITE means that you want to change the naming format on the local side only. If you want to change it on both the local and remote sides, it's just "NAMEFMT 1" without the word "LOCSITE")

Can someone please give me the proper syntax for moving into the AFON
directory?

To change the local directory, you use LCD.  So you'd type:

   LCD /AFON

That'll change it to the AFON directory of the IFS -- but it won't work if you dont' change the naming format, because it'll be looking for a library named "/AFON" which of course won't exist.


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.