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


  1.  Home
  2. MIDRANGE-L
  3. September 2003

Re: IFS file append

Steven

If you have QShell installed, this is easy. The command is basically

cat *.* > allfiles.txt

This will replace the contents of allfiles.txt, if it exists. To append to it, use

cat *.* >> allfiles.txt

Remember the 8.3 filename limitations in QDLS.

And this is case-sensitive.

This can be run from a CL with something like

QSH CMD('cat /QDLS/VERN/*.TXT > /QDLS/VERN/allfiles.txt')

Here VERN is a first-level folder. I wanted only the .TXT files. And I am creating or replacing the output file.

Note the forward slashes (Unix-style). We're Unix dweebs now! ;-)

The output file does not need to be in /QDLS - you can put it anywhere in the IFS, and then you have not the same 8.3 limits on the file name.

At 03:49 PM 9/4/2003 +0100, you wrote:
All,

Could anyone help with the following problem that I have,

I have a folder in the IFS under QDOC which has multiple documents in , I
need to take all these documents and create 1 document from them, and FTP
this document to an external system.

Sounds simple , and would be a piece of cake if the files existed as normal
AS400 files.
The filenames differ on a daily basis , as do the number of files and I am
looking to automate this task.

An MAPPEND command within an FTP script would be ideal but this does not
exist.

Any Ideas please.

Regards

Steven Gray
Senior Analyst
ARVAL PHH



As an Amazon Associate we earn from qualifying purchases.

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