×
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.
13490 and 13491 are also not supported -
Looks like API time...
- sjl
Eric wrote:
Make that 13490, if you're needing Unicode 2.0
Eric wrote:
http://www-01.ibm.com/software/globalization/ccsid/ccsid_registered.html
Looks like UTF-16 LE is at CCSID 1202...
I wrote:
We have a home-grown ETL process on our iSeries (V5R4) which builds various
extract files from our inventory and sales systems.
If I create iSeries database file MYFILE using CCSID(13488) and then
CPYTOIMPF FROMFILE(MYFILE) TOSTMF('MYFOLDER/MYFILE.TXT') RCDDLM(*CR)
DTAFMT(*FIXED)
This appears to create a stream file which is encoded as UTF-16 BE with no
BOM.
However, the BI folks have indicated that they want us to send them the data
encoded as UTF-16 LE with no BOM, and I am not quite sure how to accomplish
this...
- sjl
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.
midrange.com
