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



All,

I have a QSH script written which takes the contents of all files in a
specified folder in QDLS and combines them all to create 1 file. This file I
then FTP to an external server.

When looking at the contents of any of the files each line ends with 0D0A
(CR followed by LF ASCII)
When I run my script within QSH (cat filename >> file) and examine the
contents of the file each end of line ends with 0D25 ( CR followed by LF
EBCIDIC)

Now the FTP command states that it automatically converts AS400 files from
EBCIDIC to ASCII , however when I ftp the IFS file the end of line stays at
0D25. The EBCIDIC version.

My questions are,

a. Why does the QSH initially change from ASCII to EBCIDIC?
b. Why does the FTP not change the file from EBCIDIC to ASCII?
c. The combined file that I create and FTP out ,how can I keep this in the
original format of my single files? i.e. no conversion. 

> Regards
> 
> Steven Gray
> Senior Analyst
> ARVAL PHH
> 
> *    Post Dept 73
>           PHH Centre
>         Windmill Hill
>         Whitehill Way
>           Swindon  
>         SN5 6PE
>           England
> *    0870 419 4639
> Fax: 0870 419 4386
> 
> 

_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed Scanning 
Services - powered by MessageLabs. For further information visit 
http://www.mci.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.