× 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 Friday 14 November 2003 22:24, Stone, Joel wrote:
> When I run CPYTOIMPF and output to a stream file, the data is all
> garbled. I think that the problem is the CCSID value.  This may also be
> called the "code page".
>
> It is creating the file with a code page = 37.  A file that is OK
> (readable characters in Wordpad) has a code page of 437.

Code page & CCSID are similar, but CCSID refers to files on the iSeries 
and code page to stream or PC files. In later versions of OS/400 there is 
a STMFCODPAG parm to CPYTOIMPF which can be set as required. Prior to 
that there are a few tricks you can use. The one I find the easiest is to 
use a QShell command, touch, to create a 'placeholder' file of the right 
code page, which CPYTOIMPF (or CPYTOSTMF) replaces. In CL you could do 
this with
QSH CMD('touch -C 437 /path/to/new/filename.csv')
before issuing your CPYTOIMPF. The CPY & MOV CL commands also have a code 
page option that you can use afterwards, but I think touch is more 
efficient - I'm sure others will correct me if I'm wrong on that.

Regards, Martin
-- 
martin@xxxxxxxxxx  AIM/Gaim: DBG400dotNet  http://www.dbg400.net   /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open    \ /
Source free test environment tools and others (file/spool/misc)     X
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news  / \

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.