About LANSA's Multilingual support

Date: Archived
Product/Release: LANSA for the AS/400 (and LANSA for Windows).
Abstract: Changing partition multilingual attributes.
Submitted By: LANSA Technical Support

Reports of problems in the multilingual area are received regularly. The cause is invariably attributed to customers changing a partition's multilingual attributes back and forth. This issue is intended to clarify some basic concepts related to multilingual application development in LANSA. More information about the subject can be found in the "LANSA/AD Multilingual Application Design Guide".

It is very important for the customer to understand that enabling multilingual support in a partition must only be done (and sorry for stating the obvious) when the application to be developed will run in more than one language.

Multilingual Support: Restrictions and limitations:

  1. The multilingual facilities can only be activated in partitions that use the SAA/CUA standards option.
  2. When defining a new partition (or modifying an existing partition) to support multilingual applications a "default" language must be nominated.
  3. The partition will not be considered multilingual until a "default" language has been defined.
  4. When creating a new partition, and the option to copy system fields from another partition is chosen, only the non-multilingual field information will be copied as no languages have yet been defined for this partition. Use the export and import facility of LANSA to set up the multilingual information later.

After setting or changing the multilingual support option to YES, always change to this partition (if not already in this partition) using the option "Change partition being worked with" accessible from the "Housekeeping Menu". Always use the option "Work with partition multilingual attributes" accessible from the "Housekeeping Menu" to set up or fully review the multilingual attributes of the partition.

After electing to provide multilingual support within a partition, use the "Work with partition multilingual attributes" option from the "Housekeeping menu" to establish and/or review the definitions of languages supported within the partition. When using this facility define any number of languages (from any of the language groups) that are to be supported within the partition.

One of the languages defined must be nominated as the default language. The default language is an important language and has the following implications:

  1. When an application is invoked without nominating the required language, the default language will
    be used.
  2. Initial data dictionary, database and application development must be done in the default language. For instance, if a field description is specified via the data modeling extended file definition facilities, it is assumed that the description is in the default language.
  3. Until a default language has been defined for a multilingual partition, the partition will not be considered to be multilingual.

What if an existing partition that has been defined as non-multilingual wants to be changed to support multilingual mode?

After changing an existing partition definition to be multilingual and enrolling the initial language set and the default language (which reflects the language of details already in the dictionary) do the following:

  • Enter the partition in the default language.
  • For fields, use the "Review/Change" field definition option and make a "dummy" change to each field in the dictionary.
  • For Files, use the "Review/Change" database file attributes option and make a "dummy" change to each file definition.
  • For Functions, use the "Review/Change Functions" or the option "Function control table" option and make a "dummy" change.
  • For Processes, use the "Miscellaneous process details" option and make a "dummy" change. If the process uses "Special Entries", use the "Special entries" option on the process menu and make a "dummy" change.