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



On Thursday 25 April 2002 9:02 pm, Vernon Hamberg wrote:
> Just found a way to simplify (IMO) downloading file members. It depends
> on using NAMEFMT 1, which is IFS path naming. When you use this,
> physical files are handled like folders or directories. Once you change
> directory to the "file", you just use the member name in the get or put
> statement.
>
>  From your client (MS-DOS prompt, whatever)
>
> quote site namefmt 1
> cd /qsys.lib/yourlib.lib/yourfile.file
> get yourmbr.mbr yourmbr.ext
>
> If yourfile.file is a source file, you don't need to specify ascii for
> transfer type - it automatically converts to ascii.
>
>
> Vern Hamberg

Hi Vernon

It's even easier than that. You don't usually need to bother with the
namefmt as OS/400 detects & sets the convention needed according to the
directory name used. From a session started with the default namefmt 0:

ftp> cd /qsys.lib/mrowelib.lib/qrpglesrc.file
250-NAMEFMT set to 1.
250 "/QSYS.LIB/MROWELIB.LIB/QRPGLESRC.FILE" is current directory.

It certainly works from OS/400 or Linux ftp sessions, so I'm assuming
it'll work in DOS too.

Regards, Martin
--
martin@dbg400.net  jamaro@firstlinux.net  http://www.dbg400.net        /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open        \ /
Source free test environment tools and others (file/spool/misc)         X
[this space for hire]  ASCII Ribbon Campaign against HTML mail & news  / \


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.