×
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.
Make that 13490, if you're needing Unicode 2.0
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Tuesday, June 26, 2012 5:21 PM
To: Midrange Systems Technical Discussion
Subject: RE: Creating UTF-16 LE Unicode files for BI system
http://www-01.ibm.com/software/globalization/ccsid/ccsid_registered.html
Looks like UTF-16 LE is at CCSID 1202...
Hth,
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of sjl
Sent: Tuesday, June 26, 2012 5:16 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Creating UTF-16 LE Unicode files for BI system
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
midrange.com
