4.5.2 Multilingual Imports into Non-Multilingual Partitions
Some save files are multilingual files and can only be imported into a multilingual partition. (See Yes in in 4.5.1 Imports with the LANSA IBM i Software.)
If the partition that you wish to import a multilingual Save File into is not defined as multilingual then before you start the import, you must change the partition to multilingual. Following are the steps to do this:
1. Temporarily suspend all development work in the partition.
2. From the Housekeeping Menu, use the Create or change system partition definitions option. Select the partition and then change the partition to Multilingual support to YES.
3. From the Housekeeping Menu, use the Work with partition multilingual attributes option. Add language ENG (English) as a valid language.
4. Perform the required import into the partition and wait for all import jobs to complete.
5. Change the partition definition back to Multilingual support NO. (Important Note: The job may fail with message DCM0858 indicating the language selected is not available - this is normal).
6. Sign off and then sign on again before resuming development.
The partition will remain non-multilingual.
Note that it is recommended that all partitions are multilingual. New partitions will be automatically created as multilingual on Japanese and French language machines. For information, refer to When is it necessary to use Multilingual Support? in the Multilingual Guide.
Warning:
If you are using Visual LANSA for development, changing the partition on the IBM i from non-multilingual to multilingual, and back to non-multilingual, can cause your non-multilingual Visual LANSA development environment to change to multilingual (English).
To check if this has occurred, start your Visual LANSA development environment and start the Host Monitor. Allow all changes to propagate to Visual LANSA. Exit the Visual LANSA development environment and Host Monitor and then log on to Visual LANSA again. If during log on the language is ENG instead of NAT, this problem has occurred. To fix the problem, exit Visual LANSA and do a partition refresh, using language NAT.
Do this before doing any further imports to the Visual LANSA environment.