ICU unicode message

AllisonD

Well Known Member
We're bringing up 812 in our sandbox and have converted data to unicode. We're trying to run a UBE on the Server but it fails and we see the following;

xmlrequest.cpp1260
ICU0000017 - ICU CodePage for 37 is ibm-37.

Is this just informational telling us that the converter is using ibm-37 for translations or is this an error message of some sort. I'm leaning towards it being informational after alot of ICU documentation but I want to be sure. Right now we can run UBE's locally on the 812 deployment server but not on the Enterprise Server which is an iSeries 810. Any and all input very much appreciated.
 
oh, you are going to learn to hate unicode

:>

For the iSeries:
In P93081 the setting need to be - IBM-37 EBCDIC-Latin 1 or Western Euro

After inserting the record - make sure you mark it as ACTIVE (Row Exit button).

HOWEVER - if you do this for all reports (including the one you are 'developing') you will get 'unicode junk' when you run them 'locally' or on the Deployment Server (DS).

In P93081 the settings need to be:
*PUBLIC *ALL REPORTNAME VersionID IBM-37 EBCDIC-Latin 1 or Western Euro AV Active
USERNAME *ALL Developer's Report Dev's Vers CP1252 WIN-Latin 1, Western European AV Active

In concept - you make it 'by default' all report/versions run under the Enterprise Server's (ES's) encoding. Secondly, you set it up that specific Versions of the report, Specific User Groups or Specific Users will use CP1252 (what we call english, not jibberish)

This way - the reports run properly on the server - and/or Intel, as long as you are running the right Version on either platform.

Holler if the description is still clowdy - I haven't had my full intake of gummy-bears, and I'm a bit light headed... california driving - here I come!

(db)
 
Daniel,



Thanks for the insight, and the 'hate lessons' are indeed coming fast
and furious. We can do so much more with these machines these days but
boy does it come with a price. Thanks for lowering the mental cost a
little. BTW, keep a sharp eye out on those CA. roads...my dad stalks
them regularly. :-0



From: [email protected] [mailto:[email protected]]
On Behalf Of DRBohner
Sent: Wednesday, March 21, 2007 7:13 PM
To: [email protected]
Subject: Re: ICU unicode message



oh, you are going to learn to hate unicode


For the iSeries:
In P93081 the setting need to be - IBM-37 EBCDIC-Latin 1 or Western Euro


After inserting the record - make sure you mark it as ACTIVE (Row Exit
button).

HOWEVER - if you do this for all reports (including the one you are
'developing') you will get 'unicode junk' when you run them 'locally' or
on the Deployment Server (DS).

In P93081 the settings need to be:
*PUBLIC *ALL REPORTNAME VersionID IBM-37 EBCDIC-Latin 1 or Western Euro
AV Active
USERNAME *ALL Developer's Report Dev's Vers CP1252 WIN-Latin 1, Western
European AV Active

In concept - you make it 'by default' all report/versions run under the
Enterprise Server's (ES's) encoding. Secondly, you set it up that
specific Versions of the report, Specific User Groups or Specific U!
sers will use CP1252 (what we call english, not jibberish)

This way - the reports run properly on the server - and/or Intel, as
long as you are running the right Version on either platform.

Holler if the description is still clowdy - I haven't had my full intake
of gummy-bears, and I'm a bit light headed... california driving - here
I come!

(db)

Daniel Bohner Independant E1 Developer | Consultant Member - iConsortium
www.ExistingLight.Net | [email protected] | Phone 208.250.1917
JDE XE - 8.11 | AS/400 - M$
 
Back
Top