×
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.
Eric -
I also forgot to mention that only 13488, 1200 and 1208 are supported, at
least on V5R4. CCSID's 1202, 1203, 1204 are not supported.
It appears that it may be necessary for me to write a program which uses the
QlgTransformUCSData() [Transform UCS Data] API to convert the data:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/qlgtrans.htm
Regards,
Steve
"DeLong, Eric" wrote in message
news:mailman.6182.1340749306.2513.midrange-l@xxxxxxxxxxxx...
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
