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



Inline

At 06:28 AM 4/27/02 +0100, you wrote:
>On Saturday 27 April 2002 12:27 am, Vernon Hamberg wrote:
> > Take a look at CHGFTPA on your system and see what the value is. It's
> > *HOMEDIR on our machine, so it points to an IFS folder, therefore
> > NAMEFMT has to be 1. Not knowing this, when I tried to CD to a file
> > using the library naming format, it failed.
> >
> > If NAMEFMT is 0 (library style) and you CD /, it will change to NAMEFMT
> > 1 automatically.
> >
> > BTW, you cannot change to NAMEFMT 0 if your current directory is in the
> > IFS (not SQYS.LIB)
>
>At work one box is *HOMEDIR and the other is *CURLIB. I don't bother with
>a namefmt for either. I also tried on Netshare400 which I'm assuming is
>*CURLIB (can't get through to it at present to confirm) as ftp always
>puts me in my library to start with. I don't do transfers in namefmt 0
>format, so that maybe explains why I don't get a failure switching to it.
>Are there any advantages to using 0 instead of 1? 1 is more like
>'regular' ftp (IMO) so I stick with it.

NAMEFMT 0 is good for QSYS.LIB stuff, since you don't have to type so much
and the syntax is easier. But that's why I liked that I could go all the
way to the member in NAMEFMT 1 - less typing, less need for repeating my
command due to error.

Of course, if you're transferring one file, it makes no difference.

>Regards, Martin
>--



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.