RE: Another weird v5r4 Client Access problem for JapaneseWindowsMachines

Thanks much Chuck. I'll recommend we go to 2924 at the next upgrade and blame you if anything goes wrong.

Just kidding. I'll make the recommendation when we go to V61.

Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Saturday, July 25, 2009 12:05 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Another weird v5r4 Client Access problem for JapaneseWindowsMachines

Burns, Bryan wrote:

<<SNIP>>

What's your primary language? Our is 2984 ENGLISH DBCS which is
often overlooked by business partners until I point it out. Our
secondary languages are 2962 Japanese Kanji DBCS and 2924
ENGLISH. The necessity for these is beyond me and I've wondered
whether we still need them but that's been our OS for 10 years at
least. With these languages installed, it's possible to change
the code page within the client properties tab. Also, I'd like
to point out that IBM provides a DBCS version of the client.

<<SNIP>>

FWiW: Since some V5R# [v5r3?] all languages ship as DBCS capable,
whereby QIGC system value is '1' [and the sysval becomes read-only]
for every language. Since that release [as I understand, was the
intent that] there should be no reason any longer for NLV2984 as
primary language solely to enable any secondary DBCS languages.

Regards, Chuck