× 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 5/4/05, Raul A. Jager W. <raul@xxxxxxxxxx> wrote:
> HI!
> 
> I will like to export a directory and to be able to create or modify
> files from a Linux PC or from a green screen, I tried to set the CCSID
> in the export file, I only get the system to set that number in the
> created file, but I think there is some translation missing.
> 
> When I create a file (using EDTF) it defaults to CCSID 284, when I use
> vi (in Linux) the file has the CCSID from the EXPORT file, but unless it
> is 850, I can not read the file in the AS (EDTF)
> 
> The EXPORT has:
> /home/Raul    ACCESS=az7      \
>       #HOSTOPT HOSTNAME=az7, DataFileCodePage=850
> 
> Is there some way to set the export so the files created with EDTF will
> be readable from the PC? or do I need to change something in the AS?

Hi Raul

Which release of OS/400 are you on? I'm sure I used to have problems
like this on V5R1 but things are much better at V5R2. Our default
CCSID is 285 (UK) and I have the same DataFileCodePage=850 setting as
you. I can open/edit files with code pages/CCSIDs of 850 and 285 (as
well as others like 437) both in vim on my Linux systems and EDTF on
the iSeries. I prefer to create files as 850 for compatibilty all the
same (usually by QSH CMD('touch -C 850 /path/to/file') before
populating it.

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.