Using LANSA V11.0 with DBCS languages does not execute correctly
|Date:||20 September 2006|
|Product/Release:||LANSA for iSeries V11.0|
|Abstract:||Important notes for DBCS languages in LANSA V11.0|
|Submitted By:||LANSA Technical Support|
Due to IBM's changes on V5R3, the system value QIGC has now been modified from its default value.
Until V5R3, to install a secondary language on the IBM iSeries(tm) family of servers system, it was required that the primary language installed for the IBM OS/400 also be a DBCS language. Starting with V5R3, that restriction is removed. The primary language can be a SBCS language in order to install a secondary language that supports DBCS.
In PSP SF98076, iSeries Memorandum to Users, information about the system value QIGC is as follows:
"Prior to this release, the system value QIGC (DBCS version installed indicator) was set on if a DBCS version of OS/400 was installed. In V5R3, any NLV can support DBCS, so this value will always be set to on. If you have applications that check this value, you should update them to use the job level DBCS indicator. You can find more information about this indicator in the Retrieve Job Information (QUSRJOBI) API."
For more details see: search for QIGC at http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp
As of V11.0 LANSA has complied with the recommendation and have altered how LANSA identifies a DBCS system via the QUSRJOBI. This may affect LANSA on iSeries with partitions using a combination of non-DBCS and DBCS languages. The QIGC value is no longer a valid indicator of executing on a machine with DBCS capability. The valid way is now to check the current job information for the DBCS capable flag from the QUSRJOBI API.
It is recommended you do not adjust the language id for each user as this can indeed have impacts on how applications will work. The language id should be appropriate for who the user actually is and what language they are executing in.
The correct solution is to have a DBCS Build profile with a DBCS language id and this profile is only used for doing the final DBCS build and not used for anything else.